yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] kiden:
Wise words.

From my own tinkering:

If left overnight, w/o high Android OS on Slim Bean 2.7, Kernel v4.8 drains (w/ data off) 1 percent every 2 hours.

If left overnight w/ high Android OS on Slim Bean 2.7, that same Kernel drains 4 percent every hour in the same conditions.

In trying out 5.1 I was seeing similar results with the few hours I left it running. I got similar results as 4.8 w/ high Android OS, even though I had the settings that gave me low Android OS on 4.8.

When I have more time, I'll run it again with BBS. I couldn't find anything helpful last time.

---------- Post added at 12:23 PM ---------- Previous post was at 12:23 PM ----------

Yep. This is bugging me! I want to find out where its coming from! Hahaha.
[Nexus S Android Development] alen1901:
I know how we can test if media scanner couses high AndOS. Someome with that problem should wipe whole sdcard. I mean, use your phone like you usually do with your apps etc, but dont put anything on sdcard. Keep it clean. Also turn off Google now and location things. If android OS is still high, scanner is not foulty.

Sent from SpeedMachine i9023
[Nexus S Android Development] Erythnul:
When you run it with BBS, post up some screenshots (especially kernel and partial wakelocks, obviously, but anything that you think is interesting) or send them directly to me, I'll have a look at it too, see if I can find something.

If nothing pops out, there's always DDMS to fall back on to determine what's going on. I've used it in the past to find a buggy app causing buffer overflows. If you plan to do this, I'll help. You will need the Android SDK installed and proper drivers, but it should be easy enough once set up. The hard part there is interpretation, even moreso than with BBS.

@Daniel.Stevens: I'd like to ask you the same thing, your battery drain is huge and something seems to be constantly wakelocking it, time to get to the bottom of this and get some BBS screenshots ;)
[Nexus S Android Development] polobunny:
I think you've misread me. I wasn't blaming media scanner, just citing an example of something that oftens gets stuck and causes problems without people suspecting it.
[Nexus S Android Development] kiden:
Speaking of... I think my media scanner is stuck. On 5.1 According to BBS, most of my partial wakelocks are due to: Media Scanner Service

How do I fix that?

(Already formatted SDCard, still seeing it)
[Nexus S Android Development] polobunny:
Corrupt media file, bad data on the SD.

When you formatted the SD did you do a quick format or a full format? The later is important.

But in the event you have a corrupt media file (usually an mp3!) you have to go by elimination because I'm not aware of a way to know which file is giving you the error. If you have a folder with lots of music in it, remove it from your SD and see how that goes. If drain is gone, then at least you know it's in this folder.

So from then on, you can drop just a few of your files in a folder and see how that goes. If drain is still not there, then more files, and so on. At some point you'll get your drain back and you can work from there. :)
[Nexus S Android Development] kiden:
I formatted it using the phone itself. And actually, the usage is lower. There was an initial spike, but it looks good so far.

Im going to do a full format on my pc. Then re-download slim bean and marmite and wipe all and flash. Just to start clean. Lets see what happens from there.

Also, now that I think about it, I have had bad experiences with my Macbook and copying items onto my phone, its corrupted files before. I'm going to use my PC to copy stuff over and see if that gives me issues.
[Nexus S Android Development] :
Do as polobunny says!
[Nexus S Android Development] polobunny:
I don't believe the phone does any sort of error correction when formatting, I think it's just a quick format (erasing the FAT), although I could be wrong.

As for the problematic mp3s, it's not necessarily about which computer you copy the files from but rather the files themselves. Some mp3 encoders insert erroneous tag data and the media scanner process chokes on them and dies. Then it restarts again and start the scanning and dies again. And so on.

Nobody really knows why the design of the media scanner is to simply die instead of skipping the file, but that's how things are so we have to deal with it. :p

Edit: Bedalus, the corrupt mp3 problem isn't about the copying of the file but rather the file itself. Important note here. No matter if everything copied right when the file is problematic itself, and some of those files even make computer players crash, depending on which tags are being read by the player and it's tolerance to misformed ID3.
[Nexus S Android Development] kiden:
Okay, I'm formatting already, I'm only going to copy what i need.

Yep, I'm doing a full format now! Going to start from scratch. Lets see what happens.
[Nexus S Android Development] :
bfqbenchmark (all one word: for searching later, if required)

https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdHdpWk5HQ2lFQmZBcUJUQjA2SnZicUE

I spent nearly a couple of hours testing BFQ, and I'm not happy with it. It showed a very small improvement in java memory writes, but worse performance in almost every other aspect I measured. I suspect Slim Bean 2.8 may ship with it, because I supply kernels for tchaari, and BFQ was in the version I sent him. So if anyone feels like playing with it for themselves, that's an option.

I tested both governors with stability test (classic mode runs in the background) keeping the system loaded, in an attempt to see if BFQ would be better under these circumstances. However, since it wasn't (and was supposed to be) I didn't bother with the second phase, which would have been without stability test.

I've altered a couple of things in the kernel, and will upload a 5.2 after I remove BFQ (phew, no need to eat my own vom)
[Nexus S Android Development] :
I see what you're saying. It's not a problem of the physical medium, but of files' metadata.
[Nexus S Android Development] polobunny:
TL;DR: BFQ still boring

Edit: And yes exactly. I believe there's a ridiculously long discussion about the media scanner not picking up media files on Android on Google Groups. People pretty much pointed out that the media scanner dies on certain characters or encodings and thus does not index the rest of the files. Sometimes simply rewriting the tags with a more accept charset fixes it, although other times you'll need to modify the tags content themselves. Very crappy to learn that this stuff is bundled with every version Android and you just hope you don't have any less conventional mp3 in your library...
[Nexus S Android Development] kiden:
Wow. Well dang. Any ideas why this would happen on one kernel and not on another?
[Nexus S Android Development] Daniel.Stevens:
I´ll try to squeeze it in but I have a few stressfull days ahead of me and I really need my phone to work so that I can work *lol*
[Nexus S Android Development] Erythnul:
Don't worry about it, no rush at all. Personal life obviously takes precedence ;)

Media scanner usually spikes a bit after fresh install/cache wipe, in my experience. However, unless it gets stuck, it shouldn't be wakelocking for very long after the first initial bump (naturally, this first bump also depends on the amount/type of media files). Getting stuck isn't kernel dependant, but can be caused by messed up media files/corruptions. Anyway, please keep sharing any findings with us, more data is always a good thing :)
[Nexus S Android Development] KrisMurdrum:
Is this another example of Google giving the non-English alphabet languages the finger?

Still remember the burn when Google told me I had to "use a real alphabet from A to Z" when I tried using Icelandic characters in my password. (first time I was not able to do so since the early '00)

Carved into the void with my Magic Rune Stone
[Nexus S Android Development] ebs512:
I dont have a lot of time before my next class, marmite will be bb's new default kernel, I have had testers test on 9020 but still need a tester for 9023 to get back to me ASAP, 9020 works and crespo4g works, need a tester for 9023 HMU its built just need you to download and flash bb6 beta WITHOUT flashing a different kernel, need to see if it boots up and I need to know what it says in the About Phone section under Kernal thanks
[Nexus S Android Development] polobunny:
That I have no idea. Why would it get influenced by the kernel is out of my knowledge.

I don't believe it's intentional though, unlike the password thing.
[Nexus S Android Development] :
v5.2 is here: http://goo.gl/HvUrp

-Stable

-CM users should probably upgrade, everyone else can skip this version.

-Compatibility with CM VYSNC modifications minor update to prevent 'microlags'

-PVR linx shared memory area disabled. (This may have been causing the PVR driver to crash. Then again, maybe it had nothing to do with it. kalimochAz did it, so I'm basically copying him. Probably worth a shot anyway!)

Yes, I went from 5.1 to 5.2 with no incremental updates! Why can't I? :D

EDIT: Can someone test on the CM version that it says 'bedalus_CM' for me please? Thanks!
[Nexus S Android Development] BenHeng:
would love to do it. However, I couldn't find anywhere a link to download this bb6 beta. Let me know if you still need someone to test (i took the liberty to add you on gmail with the adress you gave earlier to get in touch faster)
[Nexus S Android Development] polobunny:
Because that's not how versioning works! :D

Shouldn't you be away and not compiling kernels? lol
[Nexus S Android Development] :
x.y.z

X=new features

Y=Stable versions, or at least what I think are stable versions :p Maybe I should just call them sensible versions.

Z=all sorts of crap. Who knows? Maybe I reprogram the kernel to only show the part of the screen under the bit where your finger touches it.

Actually I have a wedding to go to tomorrow, so I should be planning how to get Jenny across the country with as little tantrums as possible.
[Nexus S Android Development] polobunny:
Oh that would be like a flashlight fingertip!

If jenny is the daughter and she's old enough to hold a phone, Angry Birds can help you for a good 30 minutes. Then you're on your own. :p
[Nexus S Android Development] caliban2:
Can't believe you still do that... :p

Yes, it's there.
[Nexus S Android Development] :
I don't know if you'll believe this, but my phone froze whilst I was looking at your post.
[Nexus S Android Development] :
"More birds Daddy!"

"No Jenny. Finished birds. Share phone with Daddy. Daddy needs to flash kernels."

"Whaaa!"

Edit: actually I probably won't be flashing kernels while driving. Unless I can show Els how to do it via vnc on the netbook. Oh my God. Imagine trying to follow satnav, placate a screaming toddler whilst simultaneously trying to regain one's phone and hold the steering wheel, and verbally instruct someone on how to build kernels.
[Nexus S Android Development] capoooro:
I was on 5.1, now on 5.2. Always on strawberry.

The android os bug is there... but I'm convinced that it don't affect the real battery life.

Your kernel it's awesome:)
[Nexus S Android Development] kiden:
Okay just finished formatting the sdcard and everything else and reflashing Slim Bean with 5.1. So far no high Android OS usage. Lets see what happens once it can settle for longer.
[Nexus S Android Development] :
Looks like kiden is trying this! Look forward to the results!
[Nexus S Android Development] deani77:
Anybody have alternative download site for CM version. Look like my share IP provided by telco had been block by Dev-Host
[Nexus S Android Development] aladin6:
Man, what is the secret of your kernels :D ? What do you implement into them :cyclops:! that's very very fast and stable! AWESOME in the true sense of the word! Thank you bedalus, you're the best :good::good:
[Nexus S Android Development] ebs512:
just another update for the crespo section, 9023,9020, crespo4g all working with the default marmite kernel, will update to the latest release in bb before we drop bb6
[Nexus S Android Development] CrackerTeg:
He puts magic in it along with small bits of awesome.
[Nexus S Android Development] alen1901:
Had SoD with 5.0.2 413mb, no kmsg, now im on 5.1, will test it, than i go to 5.2 etc. ;)

Sent from SpeedMachine i9023
[Nexus S Android Development] androidforeve:
Sorry no screen shot but on 5.00 my Android os was 9 percent on 5.2 its 23 percent is this normal? Maybe let it settle in
[Nexus S Android Development] kiden:
Okay, I tried it out. Interesting results.

Under BBS, no more partial wake locks from the media scanner. This is good. So looks like I may have had some issue with the media scanner.

Android OS started out at 4% at first. I let the phone sit, and as time went by, it slowly started going up. After a couple of hours it was at 12% (it was rising over time... 4, 9, 11) and battery drain was above normal. Battery went down by about 6% in an hour or so. However this is improvement, usually it would have been at 30% or so by now. Looking through BBS partial wakelocks did not show anything interesting.

I just flashed 4.8, without changing anything. Android OS is at 4%. I'll let it sit for a while and see if it climbs up as well. 4.8 usually stays right around there for me.

What is a normal level for Android OS usage to be at? Just wondering.
[Nexus S Android Development] androidforeve:
Actually os is dropping as it's settling in
[Nexus S Android Development] kiden:
For you guys wondering why I care so much,

its cause with v4.8 this is the kind of battery life that I get on my Nexus S:

Edit: That last section, where you see it was awake when the screen was off quite a bit, was me testing the high AndroidOS usage when Location is turned on. If that had been off, it would have drained much slower. Either way, superb battery life. All I did was switch to 2G when not actively using the phone. Oh and in airplane mode when in an area with no signal.
[Nexus S Android Development] polobunny:
We need bbs logs to help you though.

Edit: will Google now disabled, no bln and all that you should get under 15% android os.
[Nexus S Android Development] kiden:
Okay. I'll give it another go sometime this week. Midterms this week and I gotta stop messing with my phone and start studying!
[Nexus S Android Development] azrealsoh:
My Android os just 5%, 5.1 with PA2.8 Rom :) Google now -off-
[Nexus S Android Development] sdhanjal15:
Happy with this...

Smartass clocked at 1.2. Played a lot of games...BTW...everyone should go get the game "boost 2"(so much fun!!!!
[Nexus S Android Development] Skyline969:
I've been having reboots all day today (kernel 5.1 and 5.2 throughout the day). Where can I find the last_kmsg file for diagnosis? I've tried looking at / and /etc, but I didn't see it.
[Nexus S Android Development] JokerAce:
Right after a reboot, go to terminal emulator and type these:

1. su

2. cat /proc/last_kmsg > /mnt/sdcard/last_kmsg.txt

---------- Post added at 10:49 AM ---------- Previous post was at 10:48 AM ----------

Tested. It mentions your name
[Nexus S Android Development] spider623:
About the drain it must be a cm base rom error since i don't have it on miui but i did on aosp and pa
[Nexus S Android Development] Skyline969:
Thanks. Will do next time it reboots. However, I've gone to 4.8 for stability for the time being.
[Nexus S Android Development] Daniel.Stevens:
I charged my backup phone and installed bbs+marmite 5.2 on my Nexus... (Wiped caches, fixed permissions)

Any special settings in bbs ?

I just let it sit for a while and see what that does to my "Android-OS"-Problem ;0)

Edit: After about 30 min. my phone dropped from 98% to 90% (Android-OS climbed from 6% to 16%) and this is what shows under "kernel wakelock".. I´m off to work now and will stuff it into my desk drawer for the rest of the day... Let me know what you need from me ;0) (Dumps, screenshots etc.)

Edit2: After ca 60 min. Android-OS is up to 27% battery is down to 84%
[Nexus S Android Development] jark99:
Everyone kept asking for this, so here's my picture of better battery stats, anyone know how to fix this?

Sent from my Nexus S
[Nexus S Android Development] Daniel.Stevens:
Ahem.. As far as I can tell you have a 3% per hour battery drain. What do you want to fix there ?!? That´s normal.. I have about 9% or above per hour... That´s why I asked for a fix/someone to look at it ;0) I barely get to 8-9 hours of use with the phone just "sitting" there... You can use it for 21 hours and still have 25% battery left *lol*
[Nexus S Android Development] Articudos:
Interpret BBS dump yourself!:)

Here is guide

http://xdaforums.com/showthread.php?t=1827676

(Posting twice...:p)
[Nexus S Android Development] Erythnul:
Thanks for the screenshot, unfortunately, this one wasn't much help yet ;) I'll also need a shot of the Partial Wakelocks section. Also, please enable root functions on BBS (After taking the screenshot) (It's in settings -> advanced settings, see the link in my sig if you need more info). It's not essential, but useful in the long run :)

I agree with Daniel.Stevens on this one, almost 22 hours of battery life is decent (unless you've had no screen on time at all, I suppose, but I doubt that). If the maps drain really bothers you, check out the following settings (assuming you're on 4.1.1, if you're on 4.1.2 these settings can all be found under the quick links under your account settings):

Settings -> Location: Turn off location services and Search Location access (You can leave GPS on, if you want, it won't drain unless it's used. Turn everything off for extra anti-drain security, I guess)

Open Maps, go to Settings -> Location and turn off location reporting and all other location settings.

If it still drains: Disable or uninstall Maps (yes, it's a drastic option, but Maps will never truly stop draining, even though its impact is minimal.)

I understand why you care so much, and being able to get good battery life is important to all of us. I agree that the screenshot you posted is the way it should be, but it's also the way most of us are getting it (I also advise charging when your battery is at ~50%, this will keep it from degrading, as it won't be cycling fully, but I'll assume that that screenshot was for demonstration purposes ;)).

Anyway, I really want to help you, however, you're making it very hard. Repeatedly, I and others have asked for screenshots to see what might be causing this drain. I believe you when you say there's nothing interesting in kernel or partial wakelocks, but without seeing it for myself, it's hard to move on to the next step, as it's drastically more work for all parties involved, rather than simply looking at a screenshot. So Please, upload some screenshots! If we all agree there's no issue there, we can move on and fully analyse this phenomenon as its happening.

Also, Android OS % depends heavily on your usage. If you let the phone only idle, with no screen on time, it will be much higher than usual, whereas if you use the phone "normally" (about 1-3 hours screen on time per day, I'd reckon), your Android OS % should be pretty low.
[Nexus S Android Development] Daniel.Stevens:
Here you go.. Thank you for taking the time to figure out what´s wrong with my phone (I already enabled the root function after starting bbs for the first time)

Edit: 2 hours in and already down to 80% battery...
[Nexus S Android Development] infernalMan:
i've give to you the 3000th thanks for this :D
[Nexus S Android Development] atxbang56:
does v5.2 contains extra ram?

because I'm running MIUI and extra ram helps a lot. the phone runs better with v5.0.3 than 5.1 so I ask if 5.2 is good as 5.0.3 ?

sorry for my english

thx for your hard work bedalus, your work make my "digital phone life" awesome day by day.

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] :
Did any CM users experience "microlags" that are now gone in v5.2? I tried out strawberry and a special version of slim bean that tchaari built for me, and thought the lags were very obvious. Are they gone?
[Nexus S Android Development] Erythnul:
Well, that's definitely weird. Even though the pms (that just sounds wrong, but oh well ;)) says 20 mins awake, practically nothing's showing up in the partials.. I'd also like a few screenshots of the following (sorry to be annoying, but I want to be complete before I say "BBS doesn't cover this :/"):

-Deeper battery stats (tap the graph in normal battery stats)

-following BBS tabs: Other, Alarms and Process

Also, I notice that BBS is saying "Since boot" as the reference. Did you reboot in between? If so, this messes up the stats. Even if you didn't, please set the reference to "Since unplugged", this possibly gives a more complete/accurate view of the locks in place. (if this significantly alters the wakelocks pages, also please re-do those screenshots ;))

I hope we can get to the bottom of this, but it's looking less hopeful at the moment. Maybe you and kiden are suffering the same issue, it could be some app causing problems at such a level that BBS can't catch it, but only DDMS may be able to show what's going on. Ah well, next batch of screenshots will hopefully tell the full story ;)

Edit: Dang, almost forgot: What's your screen on time with this? Probably pretty low, but just checking ;)
[Nexus S Android Development] :
I found this in the 4g thread, erythnul, would you take a look?
[Nexus S Android Development] Daniel.Stevens:
Absolutely no annoyance at all.. I´m just happy that you are willing to help me and others with the same problem to solve it ;0) Thank you !!!!

(Now down to 77% after 2 hours)

P.s.: I don´t know why it says from 91% to 79%. I unplugged it with 98% and had no reboot... If you want me to start over again just tell me to. Will do almost anything to figure this out... (btw.: Yesterday I had a 3-4% per hour battery drain with marmite 4.8.3 and I was actually using the phone. eMails, WhatsApp, GTalk, Calls etc.)

I have to do some work now so I´ll let the phone just sit here for a couple of hours and check back with fresh screenshots later.. ;0)
[Nexus S Android Development] kiden:
Thanks! It was for demonstration purposes. :)

And I will test again and make sure to take a screenshot of what BBS shows in partial wakelocks!

Once I have time. Still studying for calc 2. *shudder*.
[Nexus S Android Development] granets:
I recommend you guys try rascarlo's rasbean jelly. best rom hands down. And it flies with some marmite on top :)