yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Erythnul:
*mumbles things about stupid Android battery reporting* Could be you had a soft reboot in between, but none of the other screens seem to indicate that.

However, now the shots are completely different from what they were, PMS went from 20 mins wakelock to 7 mins (which seems more accurate, except for the fact that drain is still high). I'm beginning to think we may have more luck with DDMS, but I'll need to run some tests on my own first to see how to properly explain how to use it, and how to get an information dump that isn't pages long and impossible to interpret. The only reason I knew how to interpret my own DDMS logs (real-time) was because I knew exactly what I had installed and when I noticed weird behaviour I was quickly able to link that to an app misbehaving because I was able to guess that that would be how it worked :P

I doubt that re-charging and doing a new BBS cycle will clear up anything else, but it's worth a shot. I'll also check out what those kworker things are, they're pretty new to me.

EDIT: Quick look at the kworker processes seems to imply that it has something to do with waking the device, and yours seems to be slightly higher than mine over a similar time period. However, those are seconds, shouldn't be this much of an impact.. *confused* Seems to me that the kworker process might have something to do with this though, something might be using it to wake the phone more than it should, without showing itself properly.

Yikes, good luck with that! Take your time, I'm also kind of busy (as you guys are noticing by my response time, I reckon :P) If you could send up an entire array of screenshots, like Daniel just did, that would be awesome! I'd be able to compare both of your info :)

In the meantime, I'll get to writing up a DDMS tutorial, in case your scxreenshots are just like . It'll be really hard to explain though, so be patient with me ;) I'll see if I can reinstall the old app that was causing my issues back then (if they haven't fixed it yet) and show you exactly how I did it back then. After that, hopefully, you'll be able to see for yourself why your phone is misbehaving ;) (If that doesn't help, I'll be completely stumped, however, so this is truly a last resort :/)

Looks like a combination of bad signal (huge drain) and quite a bit of music, but still a high OS drain.. Could be caused partly by the lack of signal, but I can't say for sure. Point them to BBS and have them give that a shot. It's really weird, but whatever is causing this must be found! So odd, that it's not showing up in BBS.. I'll get to work on the next step.. DDMS (and little to no work today, I guess) here I come ;)
[Nexus S Android Development] muller37:
my android os usage has gone from 38% to 12% and maps usage from 18% to not registering in stats by un-installing maps and re-installing maps from play store.

Not sure if this is a coincidence or something screwy happening after installing gapps on CNA.

Can anyone else try this to see if its linked?
[Nexus S Android Development] 4tticuz:
Do you guys with that weird OS bug did a full wipe changing from 4.1.1 to 4.1.2?

Helped for me...

Maybe it is kinda stupid, but I wiped everything 3 times even format system...

Just give it a try and use androids possibility of backuping ;)
[Nexus S Android Development] Daniel.Stevens:
After a couple of friends recommended that already I´m going to abort my experiments with slimbean and marmite v5 (and above) and am just downloading rasbean jelly ... Everyone tells me it´s "the fastest of em all", but the download sure takes a while *lol*

Let´s see if the problem still exists with that rom + marmite ;0)

To everyone with the Android-OS issue: I´m sorry that I won´t be able to help with that issue anymore but I really need my phone (for work) and my backup-phone is already grading my nerves ;0(
[Nexus S Android Development] granets:
hope it helps. I get more than 30 hours with rascarlo and marmite 5.x with moderate usage. Just make sure you disable google's location services and you should be very happy. Also I have the habbit of disabling unused built in apps. (gtalk, email, talkback etc. )
[Nexus S Android Development] alen1901:
You didnt flash cna gapps didnt you? :p Guys, install someother navigation, Google maps are allways eating battery.sometime they will show in recent apps even if you didnt open them ever. Gmaps allways have opened service in background, even if you force close it. Check settings->apps->services. Damn Google. :p

Sent from SpeedMachine i9023
[Nexus S Android Development] Daniel.Stevens:
I´m going to give it a try but I can´t disable those services/apps since I use them quite frequently... But I get 3-4% battery drain with slimbean 2.7 and marmite 4.8.3 with everything enabled so if it´s true what everybody keeps telling me I should at least get my usual 25 hours out of rasbean and it should be a lot smoother/faster than slimbean...
[Nexus S Android Development] dinuvali:
That, or you can get the Autostarts app or similar to have the OS prevent Maps from autostarting and it works very well.
[Nexus S Android Development] alen1901:
Doesnt some maps service goes up again? I use autostart app. I will try that some time. :D

Sent from SpeedMachine i9023
[Nexus S Android Development] atxbang56:
so?

Sent from my AwEsOmE Nexus S

Samsung Nexus S

Android 4.1.1 Jelly Bean

ROM : MIUI 2.10.12 by MIUI France

Kernel : Marmite v5.0.3 ( CFQ / SmartAssV2, 1.2 GHz)
[Nexus S Android Development] caliban2:
Can't complain about anything. :)
[Nexus S Android Development] alen1901:
I think 5.2 has 407mb of RAM

Sent from SpeedMachine i9023
[Nexus S Android Development] caliban2:
It has, but those missing 6mb won't change a fast ROM into a laggy one. They may (!!!) reduce the number of active apps by one, but even that depends on how mem-hungry they are.
[Nexus S Android Development] alen1901:
I say, everything equal and above 400mb is great.

Sent from SpeedMachine i9023
[Nexus S Android Development] atxbang56:
MIUI is a ramhungry rom especially miui launcher so more ram you have, better it is

Sent from my AwEsOmE Nexus S

Samsung Nexus S

Android 4.1.1 Jelly Bean

ROM : MIUI 2.10.12 by MIUI France

Kernel : Marmite v5.0.3 ( CFQ / SmartAssV2, 1.2 GHz)
[Nexus S Android Development] alen1901:
So, you can either use older kernel with more RAM, or buy a new phone with more RAM. :p

Sent from SpeedMachine i9023
[Nexus S Android Development] JokerAce:
So far so goodddddddddddddddddddddddddddddddd with marmite_v5.2
[Nexus S Android Development] xjerlzx:
Well done bedalus!

-slim 2.6 , 4.8.3, pimped my ROM (no kernel)
[Nexus S Android Development] cyrus_e:
Hey Bedalus. Been running your kernel for a couple of months now. Everything was smooth until the less few updates, mainly the v5s.

Installed v.5.1 yesterday, and I get reboots 4-5 minutes into a game. I even got a reboot this morning while on Facebook app, following a couple of boot loops :eek:

I'm on latest CM10 Nightly, with SmartAssV2 1.2 Oc'd.

Here's my last_kmsg. Please help!!
[Nexus S Android Development] Erythnul:
Alright, so after checking into my so-called "last resort" method I found that it's just a way to look at the logcat, though it is in real-time and while the screen is off etc, it might not be the best for our purposes after all, as you can easily extract the logcat in other ways. Guess it was just my roundabout way of doing something that should've been obvious :( I kind of liked it though, a stream of information of problems as they are happening can be useful, I suppose. Oh well, anyone interested should probably just get a logcat instead of using DDMS. Sorry about the confusion, guys :/

Does anyone know if I'm correct in assuming that an error recorded in the logcat is not at kernel level, but is always a ROM/app problem?
[Nexus S Android Development] caliban2:
Look at my sig - CM is not the problem. Neither is smartass, I'm using it too. That leaves OC, your setup (how long since your last full wipe?) and any mods you might be applying. CM + marmite is fine, problem is on your end.
[Nexus S Android Development] polobunny:
I'm thinking the voltage change bedalus did might not go well with a lot of people phone. :/
[Nexus S Android Development] caliban2:
Might be, but in that case try without OC first to make sure it's not caused by something else. Running the thing out of specs and crying for help is just a waste of everybody's time. And in his case there's a number of other possible bug-sources, CM had some severe changes lately (change to 4.1.2, stuff in nightly 1017, new gapps).
[Nexus S Android Development] polobunny:
Just using any CM nightly is a chance there's bugs. I still recall CM7.2 being buggy for the Nexus S, even though it was called stable. :p
[Nexus S Android Development] leap_ahead:
Bedalus check oc settings pls. 1.2 freeze phone sometimes
[Nexus S Android Development] cyrus_e:
No other mods. Just CM Nightly with Bedalus. I do recall never getting a reboot before the voltage re-adjustments...

Well I just upgraded to v5.2 and played around in a game for a few minutes and no reboots yet. Will report back if I do.

And I always do full wipes when I upgrade rom AND Kernel. Titanium Backup Pro FTW.
[Nexus S Android Development] atxbang56:
I'm waiting for the new nexus but not LG's one.I hope Samsung will build one

Sent from my AwEsOmE Nexus S

Samsung Nexus S

Android 4.1.1 Jelly Bean

ROM : MIUI 2.10.12 by MIUI France

Kernel : Marmite v5.2 ( CFQ / SmartAssV2, 1.2 GHz)
[Nexus S Android Development] spider623:
I had to open my mouth, after upgrading from 5.0.2 to 5.2 I got the drain on miui

Sent from my Nexus S

---------- Post added at 12:21 AM ---------- Previous post was at 12:20 AM ----------

Your rom is 4.1.2 lol

Sent from my Nexus S
[Nexus S Android Development] Naa Laa:
Which MIUI version are you using?

5.2 works perfect with MIUI v4 from miui.us (except for so called "Android OS" bug :confused: )
[Nexus S Android Development] :
There's a lot of lazy bug reporting happening. There's a link on how to help with debugging in the OP.

I'll see about adding custom voltage for OC, but I've been at a wedding today. Just got home!
[Nexus S Android Development] CrackerTeg:
I'm going to go with my customary, nothing here. Latest rasbean and marmite 5.1. Kinda miss the extra ram from 5.0.I forget but I haven't really noticed it missing. Bed, keep working your magic brother.
[Nexus S Android Development] kiden:
Here is a few! Tell me if this is what you need, I can always take more... BUT I THINK I FOUND IT! I was looking in the wrong place.

Recap:

After a clean format of the SD card, multiple wipes and a reinstall of Slim Bean 2.7. 4.8, low Android OS, 5.1 high Android OS, higher battery drain. Today I noticed that formatting the SDCard helped with battery life, but didn't get me all the way there.

Under kernel wakelocks, I see that the BLN was keeping it awake for 36 min, which is about what CPUspy reported it was running in 100mhz instead of deep sleep. I'm no expert, but it looks like the BLN was keeping the device awake while the lights were going off.

I'm going to disable BLN, and see if that makes a difference.
[Nexus S Android Development] caliban2:
Right, now mine is acting up too.

Looks like wlan, but those sound-chip messages are new to me as well... It rebooted twice in standby, log is from the second one. Last full wipe was for yesterday's nightly, so I'm not sure another one will help.

http://db.tt/PD5D2ewm
[Nexus S Android Development] atxbang56:
you're right I forgot to change it

Sent from my AwEsOmE Nexus S

Samsung Nexus S

Android 4.1.1 Jelly Bean

ROM : MIUI 2.10.12 by MIUI France

Kernel : Marmite v5.2 ( CFQ / SmartAssV2, 1.2 GHz)
[Nexus S Android Development] amitabhr:
Great Kernel. Issue with MTP though.

Great Kernel. Installed marmite_4G_v5.2 (on CNA 3.6.0) a few days back and its got great battery life + no lags.

Am facing an issue with MTP though. I used usb switcher to switch to MTP mode and it worked fine but after another reboot i can no longer get either MTP or USB Storage to work. Nothing shows up on my laptop now. Tried switching a few times between both modes etc but no go.

Any one else having similar problem with MTP ?
[Nexus S Android Development] Daniel.Stevens:
That´s it for me.. for now.. ;0)

Just a quick update: rasbean Jelly didn´t do it for me at all...

So I went back to SlimBean 2.7.0 and tried marmite 4.8.7 I formatted/wiped everything 5 times, installed the rom and the kernel and didn´t stuff any old pictures/stuff onto my SD.

Furthermore I didn´t use Appmonster to get my Apps back but installed everything fresh from the play store.

No zRam, samepage merging, sd-boost or oc this time... G-Now, Talk, eMail push, Location&Search (GPS when needed) are active.

My phone runs smoother than ever (even without oc to 200(forced)/1200 etc.) My sd is as fast as it never was with the sd boost at 2048 (I can tell by how fast the pictures appear in the lower right corner after i took them) and I have a 2% per hour battery usage WITH using WhatsApp, G-Talk and screentime...

I think I will use the combination for a while and put my "I need the newest stuff"-attitude to bed for a healthy (hopefully long) sleep ;0)

Thx bedalus (and of course all the other members who tried/are still trying to figure out the Android-OS/battery bug) ;0)
[Nexus S Android Development] :
Let us know how you get on. It's difficult to resist the urge to flash.
[Nexus S Android Development] :
There's been a commit in android-3.0/common: https://android.googlesource.com/kernel/common/+/e9babf3472a0bb1bf31f8a3df173d683a86d2da3

...that I thought I'd merged but I hadn't. It's to do with timekeeping. The final error in your log is

dhd_bus_init: clock state is wrong. state = 1

I should have merged in this commit already. Honestly, missing it was quite a poor oversight, considering it's been there for three weeks, and I've seen it in at least three other repos.

I'll merge it in, but while this might solve some problems, I doubt it will solve all of them.

EDIT: Actually, there are a lot of wifi commits in android3.4/common, but they seem to have dried up in 3.0/common. That's odd. I wonder if I ought to try backporting these commits, because you've also got this sort of thing:

CFG80211-ERROR) wl_construct_reginfo : get chanspecs failed with -23

...in your kmsg. There's a commit in 3.4/common that seems to address that issue: https://android.googlesource.com/kernel/common/+/f27ac4647f2276be767407ca9e0583f69d8c749d
[Nexus S Android Development] melvinchng:
So which version has less drain? 4.8? I feel it drain quite a lot in 5.2

Accidentally sent from my Google Nexus S
[Nexus S Android Development] :
Have you tried restarting your computer? If that fails you'll have to try a different USB port, and if that fails, you'll have to wipe the USB registry entries.
[Nexus S Android Development] caliban2:
Stop it with all this "mea culpa"- stuff, will ya? :p It's not necessary.

Could make sense, but now I'm asking myself: If it's been out for 3 weeks, what took it so long to crash?
[Nexus S Android Development] :
Blinking uses the processor. If you turn blinking off, and set the final state to on, it won't use the CPU. So you can still use BLN.
[Nexus S Android Development] BenHeng:
Same problem as ever: there's some incrashable black magic in the Marmite

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] caliban2:
Peut-être. Marmite bien sûr a un je-ne-sais-quoi... ^^
[Nexus S Android Development] doc_v15:
Guys, you need to have the JB build prop for battery saving, it really works,

http://xdaforums.com/showthread.php?t=1786121
[Nexus S Android Development] atxbang56:
5.0.3 is the best on MIUI for now

Sent from my AwEsOmE Nexus S

Samsung Nexus S

Android 4.1.2 Jelly Bean

ROM : MIUI 2.10.12 by MIUI France

Kernel : Marmite v5.2 ( CFQ / SmartAssV2, 1.2 GHz)
[Nexus S Android Development] azrealsoh:
Why my phone have random reboots with 1.2ghz? Can't find the voltage setting in nstool. :/
[Nexus S Android Development] :
I combed through the android-3.4/common commits from Dmitry who also does bcmdhd for 3.0, and found one interesting one about deadlocks, and a couple of other minor fixes that seemed justifiable, so I've added them all in, and I'm running it now without problems.

I'll upload the versions now. If reboots continue, I will release some debug versions again.
[Nexus S Android Development] atxbang56:
you can't adjust voltage with this kernel I think

Sent from my AwEsOmE Nexus S

Samsung Nexus S

Android 4.1.2 Jelly Bean

ROM : MIUI 2.10.12 by MIUI France

Kernel : Marmite v5.0.3 ( CFQ / SmartAssV2, 1.2 GHz)
[Nexus S Android Development] anshumandash:
For some time, I had gone back to 4.8.7 and stayed away from the Android OS drain. Today I had sometime, so I flashed 5.2. During the first hour, Android OS started with 54%. While it is generally the Cell Standby which shows up as highest %, in case of 5.x it is the Android OS. It started reducing with time. Now it is around 16-18%. But I don't see any additional battery drain due to Android OS. It wasn't this good with 5.0.x. I have attached few screen shots including some from BBS. I think it is just normal now and there is nothing to worry. Today just to test this, I did not use my phone much other than few calls. In the attached screen shots, within 6 hours I I had about 40 mins of voice calls.

If you see in some time, the Android OS % increases again. But with all this, moderate use, 8 hours 28 mins and I still have 73% battery. What else I will ever need? :D I think 5.2 is a great kernel.
[Nexus S Android Development] superng888:
I'm on slimbean-2.7.0 and previously with you 4.8 kernel i had major battery drain but after i flashed version 5.2 , i had awesome battery live and the rom is still snappy with no overclocks at all! gotta say thanks dev :highfive:
[Nexus S Android Development] :
v5.3: http://goo.gl/HvUrp

This provides a couple of minor fixes.

3.0.47-rc1 was just released, and I've added custom voltage for OC, which I will upload in the thread for testing.
[Nexus S Android Development] :
http://d-h.st/K7q

That's a Non 4G CM version (don't have time right now to switch to AOSP config)

For anyone on CM base or strawberry to test 3.0.47. Also has custom voltage for 1.2GHz step. Does not have custom voltage for other steps.
[Nexus S Android Development] cyrus_e:
Thank you! Will definitely help out on the testing for custom voltages!!
[Nexus S Android Development] :
v5.3 doesn't have custom voltage. The test version above does, but only for cm base
[Nexus S Android Development] caliban2:
I'll take this one then. (Don't expect any OC-testing from me though. ^^)
[Nexus S Android Development] cyrus_e:
Ok! Just flashed the test version. I'm running nightly from wednesday.

For some reason I can't access your voltage graph in the google spreadsheet anymore (view only doesn't let me click on the link...)

Would you like me to try out the higher voltages for 1.2ghz, and if so, please tell me what ranges you would like!
[Nexus S Android Development] :
For some people, increasing the arm and/or int volts at 1.2ghz will improve stability. For others, they may need to lower it.

Try messing with it when your battery is down to 20% because it'll reassure you that you voltage is stable even when your battery is drained
[Nexus S Android Development] cyrus_e:
No problem! At 88% now, will increase voltages (since I did not get reboots with your kernel before the undervolting in v4.8.3) and run heavy games until I reach 20%, then I will start playing around.

Will report back!
[Nexus S Android Development] jimdem:
Oops! Something went wrong! I've installed the 5.3 and while everything seemed fine, it rebooted when I switched wifi off. I don't know if it's related. Anyway, here is the last_kmsg ;) http://db.tt/1l8SMJra

Model: i9023. I'm using AOKP jb b4 ondemand/cfq no overclock no mods.

UPDATE: It seems that actually it's a wifi related issue. Again, when i tried to turn it off the device rebooted.

UPDATE2: I flashed 5.2 and everything is ok. So it is 5.3's issue.

Στάλθηκε από το Nexus S μου χρησιμοποιώντας Tapatalk 2
[Nexus S Android Development] caliban2:
Rebooting-time... :) It's definitely wlan that's acting up, but not only... Oo :p

To give you the picture:

For 2 or 3 weeks CM has a feature to disable wifi after a certain amount of time in standby. If wifi is set to "never keep active" or "only keep active if charging", you can choose how long it is to be kept on in standby (if the connection is idle), standard is 15min. If it gets switched off and you wake the phone up, so get's wifi. Am I making sense? ^^

Okay, I've had 3 reboots since you released 3.0.47-rc1, the last one when I disabled wifi manually. It's been in standby for a few minutes, I checked a mail and then turned wifi off -> freeze -> reboot. That's the last-kmsg attached.

The prior 2 reboots happened on it's own, while it was sitting on the desk, with wifi generally on. I'm only estimating, but it could've very well in standby for the 15 minutes mentioned above (after which wifi is turned off).

After the last reboot I tried to reproduce by on/off-switching manually, but nothing went wrong. So maybe it needs a certain amount in standby before things go wrong, testing that now. The source either lies in marmite v5.2 or CM nightly 1018. And let me add that nightlies 1018 and 1019 don't have anything in their changelog that me little know-nothing would connect to this. ^^

Log: http://db.tt/ocjBm0Oz

EDIT:

After it's been in standby for about 10 minutes, I tried again turning wifi off manually -> poof. http://db.tt/v7LwewU4
[Nexus S Android Development] gregorypeg1000:
I had a reboot also on 5.3 ,slimbean 2.7.
[Nexus S Android Development] micha3lvd:
had a reboot while toggling wifi.. gotta go to work so will post last ksmg later
[Nexus S Android Development] joeyddr:
Same here turned wifi on it was fine but when shutting it reboot... i cant post the ksmg at the moment im at work.
[Nexus S Android Development] BenHeng:
Got a reboot too! Maybe WiFi related but not sure if it's kernel related but I do read "kernel panic" in the kmsg.

http://www.mediafire.com/?wjvfu22fwg8cjlm

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] JokerAce:
We have been stable for too long, it's time we hit the wave again. Here we go again, get to work together guys!
[Nexus S Android Development] spider623:
Guys this is crazy, after I had the drain I fully charge the phone remove the cable and restarted the device and guess what, the drain is gone, but this error is crazy it comes and lives when ever it wants :banghead:
[Nexus S Android Development] aladin6:
Me too...
[Nexus S Android Development] FlatEric0074:
Had a reboot after installing the 3.0.47rc1 for cm, could pull the last_kmsg. using cm10 jellybro from 16.10. on i9023.

Gesendet von meinem Nexus S mit Tapatalk 2
[Nexus S Android Development] coluichepensa:
I installed the 5.2 cm and works fine. No reboots and good battery life. I combined it with the last stawberry rom. I can say it's a great combination.

Inviato dal mio Nexus S con Tapatalk 2
[Nexus S Android Development] caliban2:
Got a reboot with v5.2 (switched back from test, why is in my previous post). Was browsing play store when it crashed directly to bootanim -> bootloop, no last_kmsg. Not near a PC, so also no log what happened during the loop.

Gonna try 5.3 now, not that I have high hopes. ^^ CM is behaving like a diva...
[Nexus S Android Development] polobunny:
I'm at 112 hours uptime with the config in my signature. I had a reboot when I started using it but nothing after... I'm really thinking most of our instabilities are due to CM nightly more than anything...
[Nexus S Android Development] caliban2:
Ahm, no. You can't compare our setups.

You're on an old nightly and an old marmite, 20121017 changed everything.

@Bedalus:

It's only an hour now, but so far 5.3_cm is playing fair. Maybe it's better to see how it does in the long run before you start trying to fix things. :)

Edit:

Forget it, few posts down you'll find a log.
[Nexus S Android Development] polobunny:
I know, but the PVR bug is still there AFAIK. Other bugs are another thing though.