Related
Downloaded the new Google Maps update praying it would fix the FC's no dice. Are all Cyanogen ROM users having this problem? Having one more problem, my phone will notify me of E-mail; but when I go to my email it isn't showing my latest email. I have to refresh it to have it show up. Not Gmail but my Comcast account? Any help would be most appreciated.
Thanks
Just FYI to anyone with this same problem, I just rooted my eris for the first time 2 days ago. Maps nav was freezing on my non-rooted 2.1 in the same exact way. Something seems to be wrong with maps in general...but I'm not sure if it's just with the eris. But I do know that maps worked within the 3-4 previous updates. Can anyone provide a way to "downgrade" maps to an update that is a little older? I think this might provide everyone with a temp solution until they provide us with an update that works with the eris...just an idea
i think i read somewhere that some people tried to downgrade maps but it still FC'd on them...
Macrodroid just posted that he had success with downgrading his maps, check his EverVolv or Macrom thread.
Sent from my MacRom MR7 using Tapatalk
The only issue I've had is when i received a call during navigation. While it was rerouting, I received a FC. Starting it again and didn't have any issues.
Downloaded the apk that Mac posted last night. I drive 50 miles to work every morning. It force closed and rebooted my phone after 20 minutes. This occurs while driving down the interstate (not while making lots of turns). Going on a trip soon, might just have to download Zach's xtr rom. I've used it in the past month and navigation worked fine.
If anybody finds a way to deterministically crash the Eris using Maps/Nav, let us know; it would be very helpful for testing purposes. Note that you don't need to be driving around for a crash to occur (although it is conceivable that will help cause the bug to occur) - the Nav app will cause a crash sometimes with your Eris just sitting motionless on a desk.
I've observed a couple of full Android restarts so far (phone connected to the PC with Nav running and "logcat" running), and so far the things I've noticed are:
- the problem is hard to reproduce. Sometimes a crash will happen in 10 minutes, sometimes in 1 hour... sometimes not after several hours. (This is the the problem with "I tried Nav for 30 minutes and everything seemed fine" reports - it isn't easy to prove that a specific fix has actually worked, 'cuz it might be hours before the bug rears it's ugly head).
- All the cases where I've seen an (Android) crash so far (v5713/gapps 20110613), I saw a SIGSEGV (null pointer fault) of the "system_server" process - the same "null string passed to strlen() via libdvm.so" error that has been previously noted elsewhere (e.g. in Tazz' thread and some time ago in other CM7 ROMs (Hero CDMA) ). This obviously will cause a full Android layer restart, but strictly speaking is not exactly a Maps/Nav issue... but probably something about the way that the new Maps/Nav behaves that makes the occurrence of this bug favorable.
I'm still looking at this, but not making much progress. The only thing that I (seem) to have noticed is that turning on checkJNI in the zygote causes Nav to hang (ANR) so that Android offers a FC to the user. I suppose this could be a completely separate bug - the main thread seems to hang waiting for something in the GL.
e.g.
Code:
adb shell stop
adb shell setprop dalvik.vm.checkjni true
adb shell start
... then do your testing.
My mothers Eris was experiencing a similar issue as was my TB. a full wipe did the trick for me using the latest available CM versions and gapps for both phones. No issues thus far... fingers crossed.
Rick
bftb0,
Back when I was trying to figure out the Maps/Nav issues, I had requested people get the kernel log of a crash. I posted here what was interesting to me from someone that had posted one and then later decided to look at the source code and follow the routines mentioned. I remember looking it over but don't think I ever posted what I'd found or was thinking and can't find any notes about it right now. Might look into that again to see if the source holds any clues.
MongooseHelix said:
bftb0,
Back when I was trying to figure out the Maps/Nav issues, I had requested people get the kernel log of a crash. I posted here what was interesting to me from someone that had posted one and then later decided to look at the source code and follow the routines mentioned. I remember looking it over but don't think I ever posted what I'd found or was thinking and can't find any notes about it right now. Might look into that again to see if the source holds any clues.
Click to expand...
Click to collapse
I looked at the link you provided - if you thought that somehow the kernel module for WiFi was a source of trouble, you could certainly just move /system/lib/modules/wlan.ko out of the modules folder and reboot (for testing purposes - obviously in the long run you want to have WiFi capability).
My own testing is moving me in a different direction, though. So far, all the Android crashes that I have seen so far have been segfaults of the "system_server" process. I just watched one a couple of minutes ago, using both logcat and strace simultaneously.
The stack trace at the segfault of system_server in the logcat (if it is actually to be believed) looks something like
Code:
strlen() [libc.so] <- segfault here
??? [libdvm.so]
??? [libdvm.so]
??? [libdvm.so]
dvmLockObject() [libdvm.so]
??? [libdvm.so]
dvmMterpStd() [libdvm.so]
dvmInterpret() [libdvm.so]
dvmCallMethodV() [libdvm.so]
libdvm is the Dalvik VM parser - which you would think/hope would be extremely robust code (and thus makes me wonder if the stack backtrace above the strlen() call is just nonsense - the debugger is not guaranteed to get it correct).
here's the last couple of lines from an strace of system_server as it was crashing:
Code:
11:51:40 sched_setscheduler(157, SCHED_OTHER, { 0 }) = 0
11:51:40 ioctl(10, 0xc0186201, 0xbedce340) = 0
11:51:48 sched_setscheduler(157, SCHED_OTHER, { 0 }) = 0
11:51:48 getpriority(PRIO_PROCESS, 157) = 20
11:51:48 recv(606568, 0x81, 1, MSG_CTRUNC|MSG_EOR|MSG_WAITALL|MSG_ERRQUEUE|MSG_DONTWAIT|MSG_FIN|0xfffb0000) = 1
11:51:48 sched_setscheduler(157, SCHED_OTHER, { 0 }) = 0
11:51:48 ioctl(10, 0xc0186201 <unfinished ...>
11:52:04 +++ killed by SIGSEGV +++
Ugh... not very informative, frankly.
This might be a fairly difficult thing to pin down - after a little bit of testing, I've noticed that it is easier to cause this particular type of crash with a phone experiencing a decent (but reasonable) load than a lightly loaded phone - as if it is more likely to occur during a low resource condition, or is due to a timing/timeout issue. I have some difficulty getting it to occur on a "stripped" GSB 3.7 (Odex) ROM, where I removed almost everything non-essential, and didn't load any apps; but on my GSB 3.7 (Odex) "daily driver" ROM, it happens more frequently, and especially if I try and make the phone jump through other hoops while Maps/Nav is running.
... still looking...
bftb0
[ Edit ] 10 minutes after I made this post I flashed my "stripped down" GSB v3.7 Odex ROM, and set it up to watch it with Nav running. It crashed about 24 minutes later. I guess I should recant what I said above about load dependencies.
Just for kicks I reinstalled 2.1 (ota version) it didn't force close but the map quit updating my location. I had the latest maps installed and once again it crashed/stopped responding after ~20 minutes.
Just for kicks I restored a fairly old version of maps - v5127 a.k.a. "5.1.0" to my GSB v3.7 Odex ROM.
It crashed my phone (an Android restart, rather than a kernel reboot) within 10 minutes of starting up Nav.
Because all of these "crashes" seem to be in the system_server process, rather than the Maps/Nav app, I'm not convinced that the problems are due to the Maps app - we certainly were not experiencing restarts on older versions of GSB way back when maps 5.1.0 came on the scene. (Although we were experiencing the "GPS signal lost" after 20 minutes bug)
I don't know what to think at this time; maybe there is more than one bug involved. Perhaps I should try the non-odexed GSB version to see if it behaves any differently.
bftb0
I went driving around yesterday and was using navigation and had it crap out a few times. One time it said that acore had crashed. Two other times it just locked up for about 30 seconds and then I saw the cyanogen animation. Sort of like a partial reboot because it was really fast.
Sent from my GSB v3.6 ODEXed using XDA App
bftb0 said:
Because all of these "crashes" seem to be in the system_server process, rather than the Maps/Nav app, I'm not convinced that the problems are due to the Maps app ...
bftb0
Click to expand...
Click to collapse
I see what you're getting at but if the crashes are not Maps related why would non-CM7 phones also freeze up? Since this is happening on xtr and stock ROMs also is it possible that something in Maps is causing the system_server process to crash?
PieceKeepr said:
I see what you're getting at but if the crashes are not Maps related why would non-CM7 phones also freeze up? Since this is happening on xtr and stock ROMs also is it possible that something in Maps is causing the system_server process to crash?
Click to expand...
Click to collapse
My best guess is that there is more than one bug involved. Personally, I've observed three different behaviors, from most frequent to least frequent:
1- Android layer restart (always a system_server segmentation fault)
2- Full reboot (kernel restart)
3- Maps ANR (App Not Responding)
#1 is absolutely, positively a bug in the system_server code; plainly stated, native code should never segfault. What is odd about this is that having Maps running seems to cause this fault to occur - it doesn't seem to happen when Maps/Nav is not running. What is extremely challenging about diagnosing this is that (if the debuggerd stack traces are to be believed) it appears that it is the Dalvik VM code itself (libdvm.so) that makes the fatal call into libc.so - a simple strlen() call that gets a null pointer. That seems to imply that figuring this out requires understanding:
- how an unrelated app (Maps/Nav) is affecting java code of the system_server
- how the Dalvik compiler/optimizer/interpreter could possibly have a bug
Note that (again, if the debuggerd stack traces of the system_server crash appearing in the logcat are to be believed) if there really is a Dalvik VM bug involved, I suppose that also means that occurence of the bug could be dependent on:
- JIT on vs. off
- Optimizer settings (and odex'ed vs. non-odex'ed ROMs)
Perhaps this explains some of the variability in the various reports; most of my experiences with the bug(s) have been with the GSB 3.7 Odex ROM (JIT on, no compcache or dithering, various VM heap sizes).
I full-wipe installed GSB 3.7 non-odexed yesterday, and am going to do some more testing.
As for crash cases #2 and #3 - I haven't experienced enough of them to say anything meaningful.
bftb0
PS Over the weekend, I drove about 3 hours on both Sat and Sun, and I didn't want my phone blowing up on me, so I rolled back my phone to celb 4.1 (Froyo) and used Nav continously. The version of Maps in that celb backup was 5127 (aka "5.1.0"). I experienced the "GPS Signal Lost after 20 minutes" bug - which I expected - but using GPS status would allow Nav to re-acquire signal. But, no other trouble. The reason that I mention this is that this same *very old* version of Maps (5127) can readily cause the system_server process to crash in GSB v3.7 Odex. This kind of data is what leads me to believe that (at least for the "Android soft-restart" bug expression) while Maps/Nav can *cause the problem to occur*, this particular bug actually is not in the Maps app itself.
Anyway, that's a few of my observations; no solutions unfortunately.
More testing to come.
I have experienced all of those, but not in that order. Rearranged by frequency for me they would be ...
3- Maps ANR (App Not Responding)
1- Android layer restart
2- Full reboot (kernel restart)
I am on GSB 3.6 ODEXed (3.7 was sluggish for me and I was getting odd and random app force closes so I rolled back).
Settings:
CPU - Ondemand, 710/245
Compcache - disabled
JIT - off
Surface dithering - off
Purging of assets - off
Lock home in memory - off
VM heap size - 32mb (default)
V6 Supercharger - multitasking or sometimes Balanced 1 with launcher HTK
By far the most common problem for me was the Maps ANR. I did get the Full reboot, and several Android layer restarts before I started playing with settings. Unfortunately I don't remember what I started with and can't say what all I did. I was running Maps 3.6.2 (I'm pretty sure) at the time and I kept getting the Maps ANR. I found a copy of Maps 5.5.0 I had forgot about in MyBackup Pro so I wiped Maps data, then uninstalled before restoring just the Maps 5.5.0 apk.
Since then I have only had one problem, which happened two days ago. I had been using Navigation for about an hour and a half, maybe approaching two hours, by the time I reached my third destination. It showed me I had reached my destination but it froze. None of the app buttons were responsive so I tried the phone soft buttons and found they were unresponsive as well. Then the phone did an Android layer restart. At the time the phone was VERY HOT to the point of being uncomfortable to hold in your hand. I have never seen my phone that hot before. It was plugged in at the time because the battery had gotten low so I was charging it.
My wife's Eris is running xtrSense 5.0.1 and I took it out and tried it a while back. It never did a full reboot or an Android layer restart but Maps ANR occurred within five minutes. I tried several times and got the same result each time.
Hopefully some others who have experienced problems will see this and chime in. Maybe if we can narrow down specific occurrences with stock and other ROMs it will help decipher this. Thanks bftb0 for breaking this down into categories and for your work on the problem. If there is any data I can capture and provide let me know.
All -
I've been testing latest map version on a number of roms as of late and offer a few observations:
I have consistently experienced Android layer restart and full reboot on GSB roms, stock settings, versions 3.4 through current. I experienced a reboot on Condemned soul's version 14 rom only once. I have not ever experienced a navigation reboot on OMGB 1.1, Evervolv,3, or 666th Sense (March OTA based rom).
The only ROM I have run that has not resulted in a map ANR is OMGB 1.1, but GPS signal is lost within a minute on that rom. Navigation continues to wait for a signal but does not force close.
Condemned soul's v14, Evervolv 3, and 666th Sense all display the same behavior: navigation runs for between 2-10 minutes and map display freezes while voice navigation continues running as a separate service. Eventually a FC is offered and navigation can be easily resumed from the notification bar. It will FC within another 10-20 minutes.
I've been doing some testing and trying a few tweaks - all dead ends and none of them have worked, but I'll repeat them here in case they are of any use to this group:
First, I tried flashing old versions of gapps to roll back the com.google.android.maps.jar file to see if there was anything there affecting navigation. At first I thought it was working differently, but alas the old jar (if they are actually even different) files really behaved the same -- they locked up the navigation moving map while partially allowing the navigation voice(s) to continue.
After repeated testing, It *seems* that the moving map is hanging up for me in the SAME PLACES. Now this is all very subjective since I cannot pay all that much attention while driving, but when I leave my office for home it seems that the maps hangs at the first right turn, 1/2 mile or 2 minutes away. If I restart it, it will continue for another 10 minutes or so until after a major highway merge.
So, I began to notice the dual-voice navigation some others have mentioned and deduced that one voice is TTS and one is google's backup non-TTS navigation sounds. I suspected, perhaps, that TTS might be crashing or being force closed by the system. A little routing around and I found that if you uninstall TTS that navigation simply will not load but will FC immediately. I also found that you can disable TTS by removing/renaming the libttspico.so file. This way, you can actually force the second navigation voice - its rather pleasant but does not pronounce street names, just says "turn left" etc.
This did not fix the problem either. But it did allow me to rule out that the phone was temporarily losing GPS signal leading to the FC. Without TTS, navigation alerts you that GPS signal was lost with a chime sound. Maps was not hanging on a lost GPS signal. since voice directions continue despite visual map hanging.
So this leads me to my next observation. Without the distracting TTS voice I notice that the maps seems to hang precisely at a point where I am supposed to be alerted to an upcoming change. For instance, after making my first right leaving the office, it hangs when (1) I turn right forcing the map to pan and draw the route for the next leg AND SIMULTANEOUSLY (2) when the GPS wants to tell me the next direction "In a half mile, turn right on to the ramp"
I also thought that there may be a memory problem - like GB is trying to kill one of the Navigation related processes. As far as I can tell, navigation requires that the navigation map, a separate navigation voice service, and PICO TTS all be running at the same time on top of a launcher, maps, email, and other services. I tried tweaking V6 supercharger to gaming settings with no luck.
klobkelosh said:
...First, I tried flashing old versions of gapps to roll back the com.google.android.maps.jar file to see if there was anything there affecting navigation. At first I thought it was working differently, but alas the old jar (if they are actually even different) files really behaved the same -- they locked up the navigation moving map while partially allowing the navigation voice(s) to continue...
Click to expand...
Click to collapse
If the jar files are the same, they should have the same md5sum so it might be worthwhile to compare them and see if each jar has matching checksums.
*POSSIBLE* Navigation Fix
I may have found a fix. I was able to navigate on my daily commute without a FC or reboot (that's not happened in a while). BUT I need your help in testing it more to be sure it is not a fluke. I'll also be testing over coming days
The attached file is NOT a flashable zip. Extract the com.google.android.maps.jar file and push it to /system/framework replacing the gapps gb version. If you use root explorer/es file manager be sure to set permissions to rwrr.
This jar version is from the May 2011 MDPI gapps package. It is nearly double the filesize of the gb version so clearly not the usual framework.
Hope this works in the long run....
I'm driving from Paducah, KY to Oscoda, MI. Should be a good test, I hope this works
Hi there...
Today! i had flashed every Custom Rom here in this X10 Mini Pro Android Thread.
On every ROM instead of the Stock Rom i have random reboots.
I tryed every way....back to Stock....wipe twice and reboot, different SD Card etc....etc...
The last ROM today was [ROM 16-07-2011] Andread 2.2.9 Pro v7f and still the same...
Connect my Phone to my PC and install market apps....reboot...
The Phone lies on my table....i will unlock.....reboot....
I now don't know what to do.....only one idea...use Stock ROM (no way) or sell the Phone and wait for tne X10 Mini Pro 2...
The Dev's here in this Forum make really great work! I hope i'm an exception...
same here. im back on stock for a month now. i thought i am the only one with this problem
im sick of rebooting just when you need your phone.
Sadly its a lot to do with the se kernel not being dessigned perfectly I believe (tell me if I'm wrong) as the way they link things is bad but for me on cm7 15.0 its fine had 2 since v15 came out and I flashed same day if it makes a difference i m on a.106 if that's correct bb I know its the new a one not c I can't remember full name
Sent from my U20i using XDA App
I have never ever experienced rebooting with any rom. Even though many people have reported it in many roms. I never have a single reboot.
I guess that all phones suffer different side-effects when roms are installed. For instance, my sd card doesn't work in any of the Gingerbread roms (2.3) but it works fine for everyone else. And the SD card works perfectly fine in (2.3.4). It's very very strange, it seems everyone's device acts differently.
I am truely sorry that you are experiencing this issue, maybe someone else can help you. It might be just an error for you only like with my SD card problem.
Hope you solve it
Regards
Com.Chakotey said:
Hi there...
Today! i had flashed every Custom Rom here in this X10 Mini Pro Android Thread.
On every ROM instead of the Stock Rom i have random reboots.
I tryed every way....back to Stock....wipe twice and reboot, different SD Card etc....etc...
The last ROM today was [ROM 16-07-2011] Andread 2.2.9 Pro v7f and still the same...
Connect my Phone to my PC and install market apps....reboot...
The Phone lies on my table....i will unlock.....reboot....
I now don't know what to do.....only one idea...use Stock ROM (no way) or sell the Phone and wait for tne X10 Mini Pro 2...
The Dev's here in this Forum make really great work! I hope i'm an exception...
Click to expand...
Click to collapse
check the smalband version. meybe thats it
I agree that there seems to be differing effects of installing a custom rom, device by device.
I too had the sdcard issue with gingerbread, intermittently. Sometimes following the same process when installing a rom can result in a different level of stability.
Currently i'm using froyocomb 1.3, but have not been able to get past the app install issues.
Overall my experience with custom roms has been good, but right now i'm stuck between a not working froyocomb, a sonybread or cm7 v15 with poor camera, or waiting 2 hours for 6.01 to boot and not feeling to optimistic. (though in reality i'm spoilt for choice by all the hard working devs out there)
I would suggest looking up an older cm6 i found them much more reliable (can't remember which one sorry)
batwingnz said:
or waiting 2 hours for 6.01 to boot and not feeling to optimistic
Click to expand...
Click to collapse
well in CM6 v6.01 booting is normal beacuse the bug have ben fixed.it takes max 5-10 min maybe even 2-5min.
zomfg i'm a retard, didn't see it in changelog. 6.01 here i come.
batwingnz said:
zomfg i'm a retard, didn't see it in changelog. 6.01 here i come.
Click to expand...
Click to collapse
hehe it happens and after you install rom use my qick hotfix for 123 keys posted allmost on the end of thread
I also have random reboots with ALL roms I've tried. Latest now is Cyanocomb v1.3 and I get random reboots (although this ROM is the one with LEAST reboots for me (perhaps once a week?))
Think I will buy the Motorola Droid 3 when it comes out, hopefully it will stop reboots
PTGamer said:
check the smalband version. meybe thats it
Click to expand...
Click to collapse
Mhhh my Baseband is M76XX-TSNCJOLYM-53404015
I think thats the right? Isn't it?
Com.Chakotey said:
Mhhh my Baseband is M76XX-TSNCJOLYM-53404015
I think thats the right? Isn't it?
Click to expand...
Click to collapse
Is there a debug/logging tool that can help us diagnose WHY our devices reboot?
E.g. like mini dump files and windows debug kit minidump viewer pointing to sys files that probably caused the crash?
svyr said:
Is there a debug/logging tool that can help us diagnose WHY our devices reboot?
E.g. like mini dump files and windows debug kit minidump viewer pointing to sys files that probably caused the crash?
Click to expand...
Click to collapse
thats a very good idea!!
there is 'logcat'. you can pipe the output to a file and try to force the random reboot. You possibly need a large sdcard - and I recommend to be veryvery careful when piping it into a file - if you write it into your phone memory, it may not come up ^^
there are also several apps like "alogcat". but this does not store regularily - at least every 15 minutes. - thus after the crash there is no log from the crash. But yyou can also try that. maybe you find another app. but piping may be the solution.
btw I do not provide a howto, you have to know how to do that or must look for an app that helps you - I can't really recommend one, but there are a lot
Snoopo said:
there is 'logcat'. you can pipe the output to a file and try to force the random reboot. You possibly need a large sdcard - and I recommend to be veryvery careful when piping it into a file - if you write it into your phone memory, it may not come up ^^
there are also several apps like "alogcat". but this does not store regularily - at least every 15 minutes. - thus after the crash there is no log from the crash. But yyou can also try that. maybe you find another app. but piping may be the solution.
btw I do not provide a howto, you have to know how to do that or must look for an app that helps you - I can't really recommend one, but there are a lot
Click to expand...
Click to collapse
thanks, I'll look into it when I have some spare time... Heh, it would be good if there was an existing/simple way configurable to write service and system logs bypassing the system buffering (or maybe to the console on the pc side), but I'm guessing I'm dreaming... I'll look into logcat then (possibly with a spare mini-sd card, since partial writes to fat32 partitions might not go well?), maybe it'll turn out to be easier to set up than you somewhat made it sound .
I like to add that I like using QtADB
when being USB-connected. THis tool also has a possibility to filter logcat per few clicks
otherwise you can also use all adb functionality like
"adb logcat" to see logs but you need to filter self
Snoopo said:
I like to add that I like using QtADB
when being USB-connected. THis tool also has a possibility to filter logcat per few clicks
otherwise you can also use all adb functionality like
"adb logcat" to see logs but you need to filter self
Click to expand...
Click to collapse
thanks for that. Don't really mind either it or normal ADB.
Heh, unfortunately I don't see anything interesting in the log...
Aside from maybe it being littered with messages of the sort:
... Kill com.gau.golauncherex.notification (pid 18332): provider com.android.providers.contacts.CallLogProvider in dying process android.process.acore
... Sending signal. PID: 18332 SIG: 9
...
21:06:33.451 Info ActivityManager 1908 Process gpc.myweb.hinet.net.TaskManager (pid 10187) has died.
21:06:33.451 Info ActivityManager 1908 Low Memory: No more background processes.
...
21:02:32.198 Warning ActivityManager 1908 Scheduling restart of crashed service com.google.android.apps.maps/com.google.googlenav.friend.android.LocationFriendService in 5000ms
where android seems to kill off apps and even services for a good measure. (or they crash?)
Memory fluctuates between about 60 and 30mb depending on the open processes, and it seems like having opera mobile opened with 5+ tabs and gmail and im+ and maybe market all at once ends up killing most of those to free up memory and maybe not die. That to me mostly means - tough luck your phone is sh!t and you should've bought a phone with more than 192mb (128mb?) ram? (or maybe - gee I wonder how I make it stop killing processes and services and what happens if it experiences a really low memory problem (<15-20mb) and can't kill processes and crash services.
Unfortunately I was unable to replicated a restart on my unit, if anyone has an idea of what to do to crash their phone let me know and I'll try it.
Generally mine reboots if I try to do too many things (market, opera, im+, etc), but now opera just closes instead of everything rebooting. (admittedly it's not an ideal outcome either, but somewhat better than a restart)
The worst I could get so far is (no idea what it means either):
21:33:54.832 Warning InputManagerService 1908 Window already focused, ignoring focus gain of: [email protected]
21:33:56.357 Error ATK 18965 Start manully kill! <---ehwhat?
21:33:56.357 Error ATK 18965 gpc.myweb.hinet.net.TaskManager
21:33:56.357 Warning ActivityManager 1908 Scheduling restart of crashed service net.jaqpot.netcounter/.service.NetCounterService in 5000ms
21:33:56.357 Error ATK 18965 net.jaqpot.netcounter
21:33:56.357 Warning ActivityManager 1908 Scheduling restart of crashed service com.android.music/.dl.DownloadManager$DownloadManagerService in 14988ms
21:33:56.357 Error ATK 18965 com.android.music
21:33:56.357 Error ATK 18965 com.android.mms
21:33:56.685 Warning GoWidgetManager 18272 invoke resume Widget err, widget id = -101
21:33:56.685 Warning InputManagerService 1908 Got RemoteException sending setActive(false) notification to pid 18965 uid 10092
21:33:59.306 Warning KeyCharacterMap 18272 No keyboard for id 0
21:33:59.306 Warning KeyCharacterMap 18272 Using default keymap: /system/usr/keychars/qwerty.kcm.bin
21:34:08.807 Error ConnectivityService 1908 Attempt to connect to WIFI failed.
21:34:08.807 Error ConnectivityService 1908 not failing over to mobile type 0 because Mobile Data Disabled
21:34:12.846 Warning AndroidMusic 19177 Need to wait for MusicPreferences to be created
21:34:13.066 Warning AndroidMusic 19177 MusicPreferences still not made, creating on UI thread
svyr said:
thanks for that. Don't really mind either it or normal ADB.
Heh, unfortunately I don't see anything interesting in the log...
Aside from maybe it being littered with messages of the sort:
... Kill com.gau.golauncherex.notification (pid 18332): provider com.android.providers.contacts.CallLogProvider in dying process android.process.acore
... Sending signal. PID: 18332 SIG: 9
...
21:06:33.451 Info ActivityManager 1908 Process gpc.myweb.hinet.net.TaskManager (pid 10187) has died.
21:06:33.451 Info ActivityManager 1908 Low Memory: No more background processes.
...
21:02:32.198 Warning ActivityManager 1908 Scheduling restart of crashed service com.google.android.apps.maps/com.google.googlenav.friend.android.LocationFriendService in 5000ms
where android seems to kill off apps and even services for a good measure. (or they crash?)
Memory fluctuates between about 60 and 30mb depending on the open processes, and it seems like having opera mobile opened with 5+ tabs and gmail and im+ and maybe market all at once ends up killing most of those to free up memory and maybe not die. That to me mostly means - tough luck your phone is sh!t and you should've bought a phone with more than 192mb ram? (or maybe - gee I wonder how I make it stop killing processes and services and what happens if it experiences a really low memory problem (<15-20mb) and can't kill processes and crash services.
Unfortunately I was unable to replicated a restart on my unit, if anyone has an idea of what to do to crash their phone let me know and I'll try it.
Generally mine reboots if I try to do too many things (market, opera, im+, etc), but now opera just closes instead of everything rebooting. (admittedly it's not an ideal outcome either, but somewhat better than a restart)
The worst I could get so far is (no idea what it means either):
21:33:54.832 Warning InputManagerService 1908 Window already focused, ignoring focus gain of: [email protected]
21:33:56.357 Error ATK 18965 Start manully kill! <---ehwhat?
21:33:56.357 Error ATK 18965 gpc.myweb.hinet.net.TaskManager
21:33:56.357 Warning ActivityManager 1908 Scheduling restart of crashed service net.jaqpot.netcounter/.service.NetCounterService in 5000ms
21:33:56.357 Error ATK 18965 net.jaqpot.netcounter
21:33:56.357 Warning ActivityManager 1908 Scheduling restart of crashed service com.android.music/.dl.DownloadManager$DownloadManagerService in 14988ms
21:33:56.357 Error ATK 18965 com.android.music
21:33:56.357 Error ATK 18965 com.android.mms
21:33:56.685 Warning GoWidgetManager 18272 invoke resume Widget err, widget id = -101
21:33:56.685 Warning InputManagerService 1908 Got RemoteException sending setActive(false) notification to pid 18965 uid 10092
21:33:59.306 Warning KeyCharacterMap 18272 No keyboard for id 0
21:33:59.306 Warning KeyCharacterMap 18272 Using default keymap: /system/usr/keychars/qwerty.kcm.bin
21:34:08.807 Error ConnectivityService 1908 Attempt to connect to WIFI failed.
21:34:08.807 Error ConnectivityService 1908 not failing over to mobile type 0 because Mobile Data Disabled
21:34:12.846 Warning AndroidMusic 19177 Need to wait for MusicPreferences to be created
21:34:13.066 Warning AndroidMusic 19177 MusicPreferences still not made, creating on UI thread
Click to expand...
Click to collapse
ps this is a bit ridiculous... Instead of rebooting, it seems after upgrading to sonybread4 rom, it now keeps killing all non-foreground processes. It's more or less a single task OS now
All, I'm currently still having issues where the phone is awake quite a lot of the time when screen is off (Stock 4.3.91 ATT). Logcat constantly is showing e/netlinkevent (UDEV_LOG not found) , and e/netlinklistener ignoring non-kernal netlink multicast message constantly popping up. A few people have asked regarding this before but no answers have been submitted yet - are there ANY rom's (GB) out there that do not have this issue?
Thanks for your time.
alien ROM, never seen it before or its way down the list
note I have NOT signed into motoblur.
you can confirm whats going on by using betterbatterymanager (on XDA not market), it will give you stats of what proc is taking up how much wakelock
Thanks - I do use Better battery Stats also and shows alarm manager as being main culprit. Any chance I could get you to look at the logcat for alien confirm that you dont have the netlistener in red popping up every 1-10 seconds?
don't see it for 30 seconds
i used the filter 'netlinkevent' (no quotation marks) nothing as well.
I bet you its some motoblur thing
alarmmanager is a catch-all service that other programs can use as a timer, its not just for alarms, so it could be anything you've installed that wants to auto update or check data
ok have tried the following roms: alien v3 (Stock no theme, stock kernal) This still had the same netlink messages. I did try aura's latest rom (blurred version) - this was also the same. However when I ran the deblurred version one of the 2 messages disappeared - I still have the e/netlinkevent coming up, but the e/netlinklistener was gone. All of these roms are fresh installs after wipes and the only apps installed/configured are android system info (to see the log). Any that still have blur on have not had the blur account signed into...
So any ideas? Whathe best rom/kernal configuration for battery life/performance outthere.
I'm just getting started on learning how to develop Android applications and noticed the same thing. I setup my IDE while the phone was running 2.2, and I don't remember seeing anything like this... but I can't say for certain. I'm runing the recently released ATT / Moto Android 2.3.4 (4.5.91.MB860.ATT.en.us). The messages never stop... have to believe it is affecting battery life.
See the image for a SS of LogCat. I killed every running application / service I could to no avail.
spiritofsaron.org/jason/udev_log_logcat.png
i think its because we are using android system info to look at the log - if you use alogcat to view the log in real time - no messages - annoying as i have spent DAYS flashing roms trying to get one without it as opposed to changing my log program...
benchallenger said:
All, I'm currently still having issues where the phone is awake quite a lot of the time when screen is off (Stock 4.3.91 ATT). Logcat constantly is showing e/netlinkevent (UDEV_LOG not found) , and e/netlinklistener ignoring non-kernal netlink multicast message constantly popping up. A few people have asked regarding this before but no answers have been submitted yet - are there ANY rom's (GB) out there that do not have this issue?
Thanks for your time.
Click to expand...
Click to collapse
Came accross http://forum.xda-developers.com/showthread.php?t=1200536 which covers the same issue.
Runs nonstop VIA adb logcat on alien 3 here.
Sent from my Inspire 4G
In many cases, people who have battery drain issues have a tendency to end up being found to be using a known battery draining app or configuration. To help these people, I'm going to try to start a list here. I will, in the case of known rogue apps, include the reporting date so people can try updates to see if drain is fixed. (For example, Facebook is rarely a culprit any more, but it was the #1 most common battery eater in 2010.) The primary focus here will be things that shouldn't drain your battery but do.
Firmware bugs:
The UCKK6 OTA update contains a number of issues with wifi and bluetooth. Among these is that an oddball feature of our Wifi/Bluetooth chipset goes nuts and wakes up the phone once per second intermittently. Rebooting temporarily fixes it, turning off wifi temporarily fixes it, only permanent fix is to ditch UCKK6. http://forum.xda-developers.com/showthread.php?t=1409513 for more details - Appears as a variant of the Android OS "bug" - this is the only one that is actually 100% a firmware bug. International XWKK5 is also affected.
LAN Environment (WiFi):
Broadcast LAN traffic can wake your wifi chip often. This also manifests as the Android OS "bug", but it's a small problem with the firmware base (XXKI3 and UCKK6 are known to be affected) and mostly a network problem. Examples I've seen so far include:
Windows Client Backup
UPnP (DLNA) SSDP
Dropbox Lan Sync Discovery Protocol
Buggy piece-of-**** routers that spam lots of ARP requests continuously - The 2Wire routers that are required for UVerse access apparently fit in this category.
You are more likely to have the above issue on some firmware bases than others. For example, XXKI3 disables all of the chip's packet filters, making it vulnerable to this sort of thing. UCKH7 and XWKL1 don't, leading to significantly improved life on "dirty" networks. UCKK6 almost surely also has the same problem.
Configuration issues:
Hotmail calendar sync
Misconfigured Microsoft Exchange servers - 1) is a special case of this. At least one person has reported that calendar sync to a non-Hotmail account was problematic for them, but email sync was OK
A bad Exchange configuration - the client apparently goes nuts if it can't contact the server
BLN - On Galaxy S II devices, there is no stable BLN implementation that does not hold a wakelock when a notification is active. This means that an active BLN notification will drain about 4-5%/hour. I say this in bold letters in my kernel thread, but somehow people still don't realize it...
Rogue apps:
Words with Friends (October 2011)
Skype (October 2011) - Particularly insidious, as it does not directly hold a wakelock. However, it causes lots of background network activity, and this activity keeps your phone awake. Since most of the time is spent wakelocked in the network stack, Skype drain shows as Android OS.
Any IM app that works similarly to Skype is likely to have the same issues.
AP Mobile Widget on stock AT&T ROMs - this one also blows through your data allotment quickly if you don't have unlimited data
AT&T Smart WiFi can sometimes hold excessive wakelocks - this is why AT&T bloat is bad for you.
The Obvious:
3D or animation/action-intensive games
The Rare:
Apps that occasionally go nuts, but not frequently
Facebook - I've had it wakelock me once, and also, Facebook chat may have triggered my first obvious "AOS bug" episode once - so far, it's been responsible for drain once this month
StartingAlertService - some sort of Calendar notification related bug
The False Blame:
GPS Status and Toolbox - may appear to be high-drain but is actually not draining - this is an Android battery reporting bug - see http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491 for more details. Thank you for the info and the great app rhornig.
If you're having battery drain issues, I suggest the following:
Install BetterBatteryStats. The XDA edition from the author's thread on these forums is free. (Market version is paid.)
Also, having CPUSpy to see deep sleep percentages is VERY useful
BBS now shows kernel wakelocks - make sure to check these. If you have an older version that doesn't show kernel wakelocks, use the instructions below.
Get ADB up and running (Google it, and if you're on Windows, Googling Droid Explorer may help)
Using ADB, do the following:
Code:
adb shell cat /proc/wakelocks > wakelocks.txt
adb shell dmesg > dmesg.txt
Zip em' up and post em' here for analysis.
Edit: Specifically, to get a good baseline measurement of idle drain - make sure to have CPUSpy installed for this procedure:
Charge phone to full
Reboot
Reset timers in CPUSpy, otherwise the percentages and bars will be wacky
Let the phone sit for a while - Overnight is best. Then provide data:
Deep sleep percentage
Time the phone was sitting
Percentage battery drained
I don't need screenshots of the above, just the numbers. Screenshots use up massive amounts of thread space
Grab /proc/wakelocks as mentioned above and post it, OR use BetterBatteryStats 1.4 or above to pull kernel wakelocks.
Note: If you're at or below 1%/hour idle drain, not much point of posting your wakelocks.
If you have high wlan_wake, wlan_rx_wake, or svnet-dormancy wakelock times, then you have an app eating data or one of the wifi wakeup bugs described above. Install Shark for Root - https://market.android.com/details?id=lv.n3o.shark
Start it, and change parameters from:
Code:
-vv -s 0
to
Code:
-vv -s 68
This tells it to only capture the first 68 bytes of each packet, which is all we need for this purpose. This provides two benefits: A smaller capture, and privacy for you. (It captures packet headers but not contents)
Then start a capture and let it sit for a bit.
Note that your drain will be higher during the capture than normal - we're collecting data here, not directly nuking the drain.
After a while where you are positive you are encountering drain, stop Shark and then pull the .pcap file - load it in Wireshark on your PC or post it here. If you post it here, MAKE SURE you have a truncated capture as instructed above!
Thank you sir. Will do in a few.
Sent from my SAMSUNG-SGH-I777 using XDA App
Words with friends is an insane battery drainer. I had a screen on time of 4 hours and 15 minutes with 35% battery use and Words with friends had a 45 min cpu usage and was 26% of the battery drain...There is no way that should be so close to the screen usage. CRAZY.
chase10784 said:
Words with friends is an insane battery drainer. I had a screen on time of 4 hours and 15 minutes with 35% battery use and Words with friends had a 45 min cpu usage and was 26% of the battery drain...There is no way that should be so close to the screen usage. CRAZY.
Click to expand...
Click to collapse
I spent a while testing that app before finding out it is a phone-wide issue. Emailed the dev today but we'll see how it goes. Not a small dev anymore.
Yea I hope they fix it...I love playing it but it kills my battery. If that app didnt run I may have like 5 hours of screen time on a single charge if not more. I looked at many of the reviews of it and many of them mention the battery killing it does.
Just discovered an interesting feature built in to the stock rom. Go to task manager > storage and you'll see it©.
The tower defense game Sentinel 3 will put a HEAVY drain on your battery.
Sent from my SGH-I777 using xda premium
gtg465x said:
Just discovered an interesting feature built in to the stock rom. Go to task manager > storage and you'll see it©.
Click to expand...
Click to collapse
Huh? What happens?
Apparently an app I come to love and use on all my devices is Battery Monitor Widget. According to to someone's post from the BBS thread and due to my own investigation. BMW will cause a lot of wake time up to 970 awakes over a 12 HR period. That is a lot time consuming battery and resources.
rebooted my phone reset cpu spy and going to leave it not charging and I will abd into the phone and get the demesg and other file and post here.. been losing 30% over night on about 8 hours which I know is way off... no skype I have wifi data sync and gps on as well as syncing a google account twitter tango and facebook.... which I understand might be alot but shouldn't this phone be able to handle all that? I also live in a basement with poor service but right next to the router... getting a microcell on Friday which I hope helps. My AOS is around 65% in battery status and suspend and events/0 are definitely running more than one minute every 10 hours, more like 20 minutes at least every charge, and my phone is lasting 11 hours give or take with minimal to no use
penskyc said:
rebooted my phone reset cpu spy and going to leave it not charging and I will abd into the phone and get the demesg and other file and post here.. been losing 30% over night on about 8 hours which I know is way off... no skype I have wifi data sync and gps on as well as syncing a google account twitter tango and facebook.... which I understand might be alot but shouldn't this phone be able to handle all that? I also live in a basement with poor service but right next to the router... getting a microcell on Friday which I hope helps. My AOS is around 65% in battery status and suspend and events/0 are definitely running more than one minute every 10 hours, more like 20 minutes at least every charge, and my phone is lasting 11 hours give or take with minimal to no use
Click to expand...
Click to collapse
Suspend and events/0 at 1 minute every 10h aren't too bad. AOS at 65 is a bit high.
Unless one of the above apps you use is implemented badly, your phone should be able to handle the above. I have Google and Facebook and get great drain. I haven't heard reports of Twitter causing problems.
Tango is an unknown - it's in a similar class to Skype so could be driving excessive idle network traffic.
To the person who posted that a game drained their battery - well, that should be pretty obvious. I guess I'll add it to the first post later, but I'm primarily focusing on the "non-obvious" stuff - things that SHOULDN'T drain your battery but do.
Tango is all good had it installed on my phone forever my batt life is amazing. It doesnt require a sign in. Look out for anything that make you sign in besides google as far as im concerned
Sent from my SAMSUNG-SGH-I777 using xda premium
Entropy512 said:
In many cases, people who have battery drain issues have a tendency to end up being found to be using a known battery draining app or configuration. To help these people, I'm going to try to start a list here. I will, in the case of known rogue apps, include the reporting date so people can try updates to see if drain is fixed. (For example, Facebook is rarely a culprit any more, but it was the #1 most common battery eater in 2010.) The primary focus here will be things that shouldn't drain your battery but do.
Configuration issues:
Hotmail calendar sync
Misconfigured Microsoft Exchange servers - 1) is a special case of this. At least one person has reported that calendar sync to a non-Hotmail account was problematic for them, but email sync was OK
Rogue apps:
Words with Friends (October 2011)
Skype (October 2011) - Particularly insidious, as it does not directly hold a wakelock. However, it causes lots of background network activity, and this activity keeps your phone awake. Since most of the time is spent wakelocked in the network stack, Skype drain shows as Android OS.
Any IM app that works similarly to Skype is likely to have the same issues.
The Obvious:
3D or animation/action-intensive games
If you're having battery drain issues, I suggest the following:
Install BetterBatteryStats. The XDA edition from the author's thread on these forums is free. (Market version is paid.)
If BBS doesn't show any significant wakelocks, and no apps show as hogs in Settings->About Phone->Battery, do the following:
Get ADB up and running (Google it, and if you're on Windows, Googling Droid Explorer may help)
Using ADB, do the following:
Code:
adb shell cat /proc/wakelocks > wakelocks.txt
adb shell dmesg > dmesg.txt
Zip em' up and post em' here for analysis.
Click to expand...
Click to collapse
Can you please take a look at this one to see if there is anything out of order?
Much appreciated!
Entropy512 said:
Suspend and events/0 at 1 minute every 10h aren't too bad. AOS at 65 is a bit high.
Unless one of the above apps you use is implemented badly, your phone should be able to handle the above. I have Google and Facebook and get great drain. I haven't heard reports of Twitter causing problems.
Tango is an unknown - it's in a similar class to Skype so could be driving excessive idle network traffic.
To the person who posted that a game drained their battery - well, that should be pretty obvious. I guess I'll add it to the first post later, but I'm primarily focusing on the "non-obvious" stuff - things that SHOULDN'T drain your battery but do.
Click to expand...
Click to collapse
what I meant to say about the suspend and events/0 is that i wish i was getting a minute every 10h, it is more like 20minutes.. I just finished my over night test, I put the phone down at 11:09 with 69% battery left, waking up just now with 30% at 8:16, did not touch the phone once.. should have been asleep the whole time.. also my suspend is at 31minutes (BBS) and my events/0 is at 30minute (BBS), i also reset my cpu spy. deep sleep 5:49 hours, 200mhz 1:29 hours and 800mhz 1:21 hours (14%)
and lastly, here is my dmesg and wakelocks... so yea this looks pretty horrible to me!
I actually went to the at&t store to exchange this phone yesterday cause I am convinced something is wrong with it, no one really seems to be getting the severe drainahe and stats that i am getting, so I assumed it has to be the phone, well its 2 weeks old and the guy wouldnt take it cause he needed proof there is a battery problem.. Also I went back to stock yesterday before i was going to exchange my phone and the issue seemed to be happening aswell no matter where I was and what apps were installed, hoping these files will figure something out! thanks for your help!
There's alot of careless and sloppy developers out there that has no concern on users battery. Android support Push notification since froyo and it's only implemented in a few apps like tango. Why? Go to the appstore the same exact IM and video chat apps uses push notification, but not on the android version. Instead you have to log in all day clogging your Ram and battery. As of now the only IM client I use it's Google Talk screw Skype oovoo ect or any other apps that has no push. BTW Facebook it's another mess, soon Ill be deleting and using the browser.
Sent from my SAMSUNG-SGH-I777 using xda premium
penskyc said:
what I meant to say about the suspend and events/0 is that i wish i was getting a minute every 10h, it is more like 20minutes.. I just finished my over night test, I put the phone down at 11:09 with 69% battery left, waking up just now with 30% at 8:16, did not touch the phone once.. should have been asleep the whole time.. also my suspend is at 31minutes (BBS) and my events/0 is at 30minute (BBS), i also reset my cpu spy. deep sleep 5:49 hours, 200mhz 1:29 hours and 800mhz 1:21 hours (14%)
and lastly, here is my dmesg and wakelocks... so yea this looks pretty horrible to me!
Click to expand...
Click to collapse
It seems to be the same issue as everybody else is having, getting excessive network traffic waking up the phone. Either you do a network capture of the packets and identify it by the highest common port which comes in (complicated), or you turn off each service off one by one. In the last case I'd start with the network location service (Kill it with Titanium) as that was known to be a *****.
AndreiLux said:
It seems to be the same issue as everybody else is having, getting excessive network traffic waking up the phone. Either you do a network capture of the packets and identify it by the highest common port which comes in (complicated), or you turn off each service off one by one. In the last case I'd start with the network location service (Kill it with Titanium) as that was known to be a *****.
Click to expand...
Click to collapse
so you think I should freeze each app one by one and let chill for an hour and see if there is drainage or not? is ot just processes or apps? cause I would never know to do something about network service unless u said something.. BTW I did, and i still lost 4% battery in an hour of idle.. so thats not it.. what about using this the other way you were talking about
http://www.vbsteven.be/blog/android-debugging-inspectin-network-traffic-with-tcpdump/
penskyc said:
so you think I should freeze each app one by one and let chill for an hour and see if there is drainage or not? is ot just processes or apps? cause I would never know to do something about network service unless u said something.. BTW I did, and i still lost 4% battery in an hour of idle.. so thats not it.. what about using this the other way you were talking about
http://www.vbsteven.be/blog/android-debugging-inspectin-network-traffic-with-tcpdump/
Click to expand...
Click to collapse
Exactly. By services I just mean running apps I guess. You can do it as in that guide too, but its hard to later find out which App listens to which port on Android...
AndreiLux said:
Exactly. By services I just mean running apps I guess. You can do it as in that guide too, but its hard to later find out which App listens to which port on Android...
Click to expand...
Click to collapse
ok, so I did try this to an extent, i would disable 4 apps at a time for the most part, only apps, none of the red items like wifi manager and stuff like that (even though i did try that at a different date)
I had no success.. I went back to stock, uninstalled all bloatware, at&t live TV, my account, bar scanner, all that bs, right now I have BBS, Cpu Spy and titanium, only apps that are not stock and are in the list of installed apps. I am still getting this issue!! could it be that I have poor service (though this never affected the iphone this badly) I lose 40% overnight though and it seems odd to me that would be because of low service..
GO.Keyboard and GO Contacts ( especially GO Contacts) was draining my battery at a phenominal pace. GO Contacts was using more battery than the display
Sent from my SAMSUNG-SGH-I777 using XDA App
EDIT: Should you experience this issue on a stock kernel while there are no wakelocks generated by any apps, a fix has been developped by HomerSp and can be found here. All custom kernels available on XDA integrate it as far as I know. You will find plenty of information about the fix in this thread, however please note no app can solve this because this is a kernel issue. Should you have applied the fix and the issue persists, try doing a factory reset to start fresh.
Got the edge yesterday (SM-G925F version) and rooted it immediately (after receiving OTA), so I'm not sure if it's a bug or rooting that's causing it. I already tried disabling edge screen, and factory reset, but it had no effect.
The standby drain is about 1.5%/h with no deep-sleep. For comparison my old Nexus 6 was draining 1.4%/h with stock kernel and about 0.2%/h with Faux123 kernel as seen on screenshots. I'm pretty sure it's going to be great once the device goes in deep-sleep, but couldn't find any particular culprit except the OS itself!?
Anyone experienced this and managed to solve it?
I read in the root thread that the lack of deep sleep is due to root itself. If you can show me how to check for deep sleep on a non rooted device id be happy to check for you.
I didn't root my phone, and last night I lost 20% over night during sleep
If my calculation is correct I lost almost 3% per hour while my phone not in use
I guess my phone don't know how to sleep properly
mrnovanova said:
I read in the root thread that the lack of deep sleep is due to root itself. If you can show me how to check for deep sleep on a non rooted device id be happy to check for you.
Click to expand...
Click to collapse
You can use most CPU apps, even though they won't be able to change CPU settings because of lack of root, they will show you CPU times, and most importantly offline mode. I use my own app for that, allowing to track battery history as well and also showing CPU times. You can try the following apps which will definitely show you deep-sleep: 3C CPU Manager or System Tuner or 3C Toolbox, all 3 are free (with ads).
In 3C CPU Manager, in first tab, called CPU, you'll see a 'Sleep' meter on top of the 3 graphs. That will indicate actual sleep time, versus run time. Mine is (was) showing nothing (eg 0 deep-sleep). In second tab called Times, you can check each CPU frequencies time used, it should show offline time, if not that means no deep-sleep! Screenshots were attached in OP.
MrHardplastic said:
I didn't root my phone, and last night I lost 20% over night during sleep
If my calculation is correct I lost almost 3% per hour while my phone not in use
I guess my phone don't know how to sleep properly
Click to expand...
Click to collapse
This seems to suggest this has nothing to do with rooting in the first place. I've only got one rooted app on my device, as always and never seen this caused by root. I've seen it caused by bugged ROMs, bugged kernels and more rarely by recovery issues, but not with my setup.
Anyway, I just rebooted less than an hour ago, and just realized it's going into deep-sleep now! Didn't change recovery which eliminate this as the culprit. Was only developping some new notification for the edge screen all afternoon. Didn't uninstall anything or changed any particular settings either except Edge screen feeds, disabling all feeds except notification and my own new feeds. Maybe that helped?
Also activated the panel left of the home screen with minimal news feeds, tech and science, but I don't see how it would relate to this.
3c said:
You can use most CPU apps, even though they won't be able to change CPU settings because of lack of root, they will show you CPU times, and most importantly offline mode. I use my own app for that, allowing to track battery history as well and also showing CPU times. You can try the following apps which will definitely show you deep-sleep: 3C CPU Manager or System Tuner or 3C Toolbox, all 3 are free (with ads).
In 3C CPU Manager, in first tab, called CPU, you'll see a 'Sleep' meter on top of the 3 graphs. That will indicate actual sleep time, versus run time. Mine is (was) showing nothing (eg 0 deep-sleep). In second tab called Times, you can check each CPU frequencies time used, it should show offline time, if not that means no deep-sleep! Screenshots were attached in OP.
This seems to suggest this has nothing to do with rooting in the first place. I've only got one rooted app on my device, as always and never seen this caused by root. I've seen it caused by bugged ROMs, bugged kernels and more rarely by recovery issues, but not with my setup.
Anyway, I just rebooted less than an hour ago, and just realized it's going into deep-sleep now! Didn't change recovery which eliminate this as the culprit. Was only developping some new notification for the edge screen all afternoon. Didn't uninstall anything or changed any particular settings either except Edge screen feeds, disabling all feeds except notification and my own new feeds. Maybe that helped?
Also activated the panel left of the home screen with minimal news feeds, tech and science, but I don't see how it would relate to this.
Click to expand...
Click to collapse
Did you use cf auto root? That's how I rooted my tmo 32gb edge and it hasn't been in deep sleep since last Tuesday. I didn't install that ota update people are talking about and have no idea that there was an update and I didn't install or mess with the recovery at all after root and my phone still stays awake.
3c said:
You can use most CPU apps, even though they won't be able to change CPU settings because of lack of root, they will show you CPU times, and most importantly offline mode. I use my own app for that, allowing to track battery history as well and also showing CPU times. You can try the following apps which will definitely show you deep-sleep: 3C CPU Manager or System Tuner or 3C Toolbox, all 3 are free (with ads).
In 3C CPU Manager, in first tab, called CPU, you'll see a 'Sleep' meter on top of the 3 graphs. That will indicate actual sleep time, versus run time. Mine is (was) showing nothing (eg 0 deep-sleep). In second tab called Times, you can check each CPU frequencies time used, it should show offline time, if not that means no deep-sleep! Screenshots were attached in OP.
This seems to suggest this has nothing to do with rooting in the first place. I've only got one rooted app on my device, as always and never seen this caused by root. I've seen it caused by bugged ROMs, bugged kernels and more rarely by recovery issues, but not with my setup.
Anyway, I just rebooted less than an hour ago, and just realized it's going into deep-sleep now! Didn't change recovery which eliminate this as the culprit. Was only developping some new notification for the edge screen all afternoon. Didn't uninstall anything or changed any particular settings either except Edge screen feeds, disabling all feeds except notification and my own new feeds. Maybe that helped?
Also activated the panel left of the home screen with minimal news feeds, tech and science, but I don't see how it would relate to this.
Click to expand...
Click to collapse
If offline means sleep then she sleeps like a newborn.
To make things more weird, I just dumped the currently held wakelocks, and at first sight it appears there is no actively held wakelock keeping the device alive. Which implies a kernel issue, but that is beyond my expertise. Needs some further research.
(Terminal emulator, disconnect USB, "sleep 30 && cat /d/wakeup_sources", turn off screen, wait a minute, turn it back on, and you get a wakelock list with 0 active wakelocks - that's shouldn't even be possible)
Either way I maintain that recovery should have nothing to do with this (binary status though, perhaps?)
FWIW, we've been discussing this a lot over in the T-M section, and the recovery seems to fix it. We've also found that a clean install from Smart Switch seems to be helpful.
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/help/rooting-deep-sleep-t3079385
Thanks for all of your work Chainfire!
Yeap all you guys have to do is flash ur stock recovery and deep sleep will be back...... For some reason this root is getting rid of our recovery all together just flash the stock recovery and deep sleep will be fine
dc/dc said:
FWIW, we've been discussing this a lot over in the T-M section, and the recovery seems to fix it. We've also found that a clean install from Smart Switch seems to be helpful.
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/help/rooting-deep-sleep-t3079385
Thanks for all of your work Chainfire!
Click to expand...
Click to collapse
Too many posts there of people CAPsing random gospel in red letters to make it more of the truth.
Some further (preliminary, non-extensive, quick) testing seems to indicate that it is indeed the binary status flag rather than the recovery itself that triggers this.
- After CFAR you end up with an official recovery (not necessarily from the matching firmware you were using)
- Binary status: custom, deep sleep issue
- Use root to pull that recovery from the device, trim it so it ends with the correct signature, tar it, flash it via ODIN
- Binary status: official, deep sleep works
- Use root to pull that same recovery again, blank out the signature, push it back (not via ODIN, just DD), reboot into recovery, then back to Android
- Binary status: custom, deep sleep issue is back again
Further testing still required for any real conclusions can be drawn. If this is true (end I certainly hope I end up being wrong) this means custom recoveries like TWRP (which also trigger the custom binary status) would also cause the deep sleep issue. It is the question if the problem is inside the stock kernel, and whether this is intentional (which would be very disturbing indeed) - guess checking out the kernel sources would be in order. On the other hand, it also seems like flashing any properly signed kernel will treat the symptom, it doesn't necessarily need to be the one matching your firmware (maybe not even exact model ?).
This recovery for the N925T is based on cyanogen mod with the ability to install zips but not backup and also DOESN'T have the deep sleep issue (supposedly)
Going to test myself tomorrow before work. Will edit with link
Edit: http://forum.xda-developers.com/showthread.php?p=60072372
^ already posted lol
Chainfire said:
Some further (preliminary, non-extensive, quick) testing seems to indicate that it is indeed the binary status flag rather than the recovery itself that triggers this.
- After CFAR you end up with an official recovery (not necessarily from the matching firmware you were using)
- Binary status: custom, deep sleep issue
- Use root to pull that recovery from the device, trim it so it ends with the correct signature, tar it, flash it via ODIN
- Binary status: official, deep sleep works
- Use root to pull that same recovery again, blank out the signature, push it back (not via ODIN, just DD), reboot into recovery, then back to Android
- Binary status: custom, deep sleep issue is back again
Further testing still required for any real conclusions can be drawn. If this is true (end I certainly hope I end up being wrong) this means custom recoveries like TWRP (which also trigger the custom binary status) would also cause the deep sleep issue. It is the question if the problem is inside the stock kernel, and whether this is intentional (which would be very disturbing indeed) - guess checking out the kernel sources would be in order. On the other hand, it also seems like flashing any properly signed kernel will treat the symptom, it doesn't necessarily need to be the one matching your firmware (maybe not even exact model ?).
Click to expand...
Click to collapse
https://github.com/eousphoros/android_kernel_samsung_exynos7420 If you want kernel source with some git history.
eousphoros said:
https://github.com/eousphoros/android_kernel_samsung_exynos7420 If you want kernel source with some git history.
Click to expand...
Click to collapse
It is interesting that you have noted you do not see the issue with a kernel compiled from source and a custom recovery. Is that kernel using the exact Samsung sources, or a transplant between CM and Samsung, or?
I'm not seeing any clearly relevant code in the kernel sources, though if it is deliberate they could have left it out (also I only looked really quickly, I don't have much time at the moment to dedicate to this). If the problem is even inside the kernel, that is. Note that binary official status is communicated between the bootloader and the kernel / KNOX via the cordon= and connie= in /proc/cmdline, if anyone else is looking.
Deep sleep issue is also present with the official TWRP (at least, in 20 minutes of testing there hasn't been deep sleep yet).
Chainfire said:
It is interesting that you have noted you do not see the issue with a kernel compiled from source and a custom recovery. Is that kernel using the exact Samsung sources, or a transplant between CM and Samsung, or?
I'm not seeing any clearly relevant code in the kernel sources, though if it is deliberate they could have left it out (also I only looked really quickly, I don't have much time at the moment to dedicate to this). If the problem is even inside the kernel, that is. Note that binary official status is communicated between the bootloader and the kernel / KNOX via the cordon= and connie= in /proc/cmdline, if anyone else is looking.
Click to expand...
Click to collapse
Linode 3.10.61 -> android 3.10 -> samsung sources is the merge order for those kernel sources i posted. One interesting thing I noted is the custom kernel is signed after the build process is done.
Also keep in mind im not even close to stock right now. Custom recovery, custom boot, most of the bloat from ms, ig, fb removed. Removed stock gapps, etc. So im probably not a good study case.
So I'm rooted, and installed stock recovery (SM-G925I) and deep sleep has come back, but since last night (~11hours total) it has only been in deep sleep for 24% of the time (around 2hrs 45mins) and it drained 15% battery in the first 6 hours, which is really really ****.
I checked better battery stats for kernel wakelocks/partial wakelocks, and it is saying that "PowerManagerService.Wakelocks" are accounting for ~75% of this... anyone have any idea how to reduce that?
Chainfire said:
Deep sleep issue is also present with the official TWRP (at least, in 20 minutes of testing there hasn't been deep sleep yet).
Click to expand...
Click to collapse
I can confirm testing the unofficial TWRP for Tmo S6 Edge that I do indeed get deep sleep. Also custom kernel.
---------- Post added at 11:44 PM ---------- Previous post was at 11:43 PM ----------
eousphoros said:
Linode 3.10.61 -> android 3.10 -> samsung sources is the merge order for those kernel sources i posted. One interesting thing I noted is the custom kernel is signed after the build process is done.
Also keep in mind im not even close to stock right now. Custom recovery, custom boot, most of the bloat from ms, ig, fb removed. Removed stock gapps, etc. So im probably not a good study case.
Click to expand...
Click to collapse
This man is a S6 Edge Genius
Again, a custom kernel. More pointers at the kernel being the culprit.