yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] BenHeng:
I've reenabled gnow yesterday because I like some of its features... and it chewed up my battery in 8hours. Re disabled it after this 8hours and my phone survived 2more with 4%...

If it helps you to know that ;)

On the other hand I got some issue with my init.d scrypt. Should I post it there (since user here already gave advices on that) or should i find a more appropriate topic?

Envoyé depuis mon Nexus S avec Tapatalk
[Nexus S Android Development] :
Looks like an improvement on sdcard reads and writes. These are a significant bottleneck, but database io does take a hit. I suppose I'll have to eat my vom now, and test it.
[Nexus S Android Development] anshumandash:
I have not tried 5.1 so far. But I have gone back to 4.8.7 to avoid Android OS drain. Now the Android OS usage is about 4-8%. This is good. I am on BB5. I know some people with same setup are not getting this issue. Below are my observations on Android OS battery drain.

- Android OS CPU usage time impacts the battery usage %. Android OS wakelocks don't have that much impact or does not increase the % battery usage that significantly.

- 4 hours of phone idle, marmite 4.8.7 results in Android OS CPU usage of 1-1.5 mins and 4-6% battery usage by Android OS

- 4 hours of phone idle, marmite V5/5.0.x results in Android OS CPU usage of 30-35 mins and 55-65% battery usage by Android OS

- Better battery stats does not show anything significant as this is CPU usage and not wake locks. (I am not sure if my assumption is correct about battery stats)
[Nexus S Android Development] mutantlx:
5.1 is so smooth compared to 5.02.

Im using on demand at 1.2 GHz.
[Nexus S Android Development] Daniel.Stevens:
So far (after "finally" giving up hope that it was something else and flashing back to 4.8.3 and letting my phone sit for ca. 2 hours) my Android OS usage is at 4% and I have 96% battery left.

With the same configuration and marmite v5/5.0.2/5.1 I would have had an Android-OS usage of somewhere around 60-80% and only 72% battery left...

What the hell is that ?!?
[Nexus S Android Development] :
I don't know. I've not got this Android OS bug, and I know a lot of users never had it. I don't think it's related to the kernel, but I could be wrong. It's difficult to say when the symptoms appear uncorrelated to anything in particular. If you've already tried disabling Google Now and Google Location & Search, you could try backing up your important stuff from your sdcard and then formatting it.
[Nexus S Android Development] Oodie:
Ohh ! Why didn't i see this before .

( Note to myself - i should visit general section time to time )

seems really interesting . Go bedalus :D :D
[Nexus S Android Development] apatal:
Glad to see you guys coming to terms about this. I've been a fan of both your work here and it would have been a shame if development we're discontinued due to this misunderstanding.

I still don't get the marmite reference though. :D

Sent from my Nexus S
[Nexus S Android Development] apatal:
No I didn't! :D

But if any one needs a quick way to do a full-wipe or just dalvik-wipe, you can use the files below, which are flashable in recovery and created by brainmaster. Cheers!
[Nexus S Android Development] :
Just for everyone else:

bedalus emailed to apologise and we had a discussion and I said there was no need to remove the links or get the thread locked and that the release wasn't an issue as far as I was concerned, it was just slightly unfortunate the way that it occurred.

I said that everyone makes mistakes and I wasn't making a big deal out of it, I was just stating how I felt.

I also said I was happy to assist if he needed assistance in the future.
[Nexus S Android Development] :
UPDATE: Download link is back up in the OP.

To do: I probably need some sort of naming system to keep track of the versions. Also, I need to push my local version back to the public repo.
[Nexus S Android Development] apatal:
Flashed it this morning and everything seems fine for now. BLN is working great. I'll post more observations later as I take it through its paces and report issues I may encounter. For now, looking good and looking forward to further development! ;)

p.s. Don't you think it's time we move the thread to the NS Development forums as thalamus has already given his blessing for the project? :)
[Nexus S Android Development] :
I suppose it's possible later on. For now this isn't really development. I know enough about code to successfully merge the BLN in, but so far I haven't actually written any code myself. Thanks for testing it out! :) What phone are you on?
[Nexus S Android Development] apatal:
i9023.

Ran antutu earlier while on performance and got a score of 3110. The bar graph it's slightly lower than Nexus S but so far, I haven't noticed any real negative manifestation of this supposedly low scoring setup.

I did get a random reboot earlier but I'm hoping it's just a glitch, something that it needed to get out of its system, and that everything will be smooth sailing from now on.

I'm on the latest rascream, btw, with brains master's tweaks.

Sent from my Nexus S
[Nexus S Android Development] :
Cool. Keep an eye on those reboots. I remember many people blamed BLN for instability. These claims were never substantiated so there's just as much chance it was purely random. Remember my version of the kernel updating script does not wipe cache or dalvic-cache, so that might be the first thing to try if you have problems.

As for performance, I'll do a statistical comparison between this and thalamus' original version.

UPDATE: New version available with voodoo-color (and sound was there already!) :D
[Nexus S Android Development] :
If you post the output of cat /proc/last_kmsg I'll take a look and see what caused it.
[Nexus S Android Development] :
Hi Oodie! Long time no death threats! :D
[Nexus S Android Development] :
UPDATE: Added BLX

Decided I can't live without it.

For some people it's a cosmetic mod that allows the battery to show 100%

For me, I set it to 90% to stop the charging process early. This is more like the intended use, which is to extend the lifetime of the battery unit itself by stopping the charge process long before the battery starts to struggle with taking on extra charge.

I'm going to see if I can live without touchwake by setting my screen timeout to five minutes. I always click my power button to sleep the screen anyway, so having a longer screen timeout should solve the problem of unwanted sleeping.
[Nexus S Android Development] mixtapes08:
Add bld too :)

Sent from my Nexus S®
[Nexus S Android Development] ironia.:
piece to piece...will be very closed to cyann kernal with updated thalamus base?
[Nexus S Android Development] climhz:
can you make download links for each version
[Nexus S Android Development] :
Ah yes, my once again sleep deprived mind. You know what? I don't miss BLD. In fact after a year of using it by habit, you would think that I would notice my buttons still illuminated, but i was using my phone for hours quite happily before i realised... I'm going to continue living without it and be happy.
[Nexus S Android Development] :
Idk if arifhn has updated his recently. Does he have a thread here for it?
[Nexus S Android Development] :
Ok... I'll do them in the version history

UPDATE: Done. Also, cleaned up the OP and added more marmite.
[Nexus S Android Development] mixtapes08:
I think its prety good when watching movies. Bld is 1 of my favorit3 kernel mods implemented on ns. Anyway goodluck with this bro just let me know if you need another tester :)

Sent from my Nexus S®
[Nexus S Android Development] wmdunn:
Thank you for adding voodoo color!
[Nexus S Android Development] :
That's very good news! No problems for me either so far, keep those fingers crossed. We wait to hear from other testers...
[Nexus S Android Development] DaXmax:
Time to build 4.1 kernel, since the sources is out (not the blobs)?
[Nexus S Android Development] :
All the proprietary drivers too?
[Nexus S Android Development] Articudos:
No binaries yet. Just checked.:/
[Nexus S Android Development] DaXmax:
Nope, blobs not yet released but kernel sources and makefile is there.
[Nexus S Android Development] :
Hmm, I'm waiting for drivers. I've got more than enough on my plate while I'm trying to improve DI efficiency. Once it's working well, I'll see if I can rebase the kernel.
[Nexus S Android Development] sdhanjal15:
Hey bedalus....can you post a screenshot of you settings...a bit confused on setting this up
[Nexus S Android Development] :
@testers, any of you received or made calls? Any issues?

Also, I'm now working on a build where instead of fixing the frequency min and max at 400 MHz, it will only set the max, then call the performance governor. I'm using printk to debug! It's almost like I know what I'm doing :p
[Nexus S Android Development] :
I don't change anything, it's set up the way I want it when it boots. Can you be more specific about the problem you're having?
[Nexus S Android Development] sdhanjal15:
Not any problems...just wanna know hoe you set your nstools or whatever you use.
[Nexus S Android Development] Randomwalker:
Tried v1.4 on CM9 and ICS 4.0.4, no problems so far. Received on short call, no issues. DI works but won't set in during music playback.
[Nexus S Android Development] Blackcrx:
Made and received calls with no issues. No COD or SOD as of right now
[Nexus S Android Development] caliban2:
Deep idle is not the same as deep sleep. :rolleyes:

Had a few phone calls today (1-10 minutes) and no problems. Also no SoD.
[Nexus S Android Development] Randomwalker:
I know. I am talking about the idle stats in NStools or the CM9 settings. Neither ON nor OFF will increase while playing (my) music. Idle will increase slightly.

I was under the impression that DI was especially interesting for screen off music playback.

EDIT: Just restarted music playback and now DI is working. Will be monitoring it for a while. Also received another short call w/o any problems.
[Nexus S Android Development] caliban2:
Just tried. After a 3:59-song I get 4:04@400 MHz and ~210.000 ms for top-off. Add a few seconds for resetting stats before disabling screen and checking stats after the song -> looks to me like deepidle does its job.
[Nexus S Android Development] Randomwalker:
Seems like I can replicate this behaviour: After coming off boot DI won't work during music playback, if I then pause playback, screen off and then resume playback, DI time will increase.

This is on stock ICS 4.0.4 (waiting for JB to drop :-)).
[Nexus S Android Development] :
Is this immediately after booting? It may be that your phone isn't actually idle... it's still finishing off some boot processes. Once the device settles, it will spend more time in deep idle. Try it and let me know.
[Nexus S Android Development] Randomwalker:
Will idle set in after a while during playback? Because on my first try playback lasted for over an hour.

It definitely was not immediately after booting up especially on the 2nd try and DI was accumulating before starting music. But I am already into the 2nd reboot to confirm.
[Nexus S Android Development] roshga:
is mirroring the latest 1.3b version possible? for some reason getting "request timed out" error.
[Nexus S Android Development] Randomwalker:
OK, on my 3rd try I was no longer able to replicate. Don't know to have done anything differently.
[Nexus S Android Development] Daniel.Stevens:
I already did that multiple times ;0) Every time I go near v5 or above it messes up the Android-OS usage. With CNA 3.6.6 and slim bean 2.6.0 and 2.7.0 The only constant is the kernel....

I fixed permissions like crazy, wiped caches, clean flashed EVERYTHING (format boot/system/sd/data/ battery etc.)

I never had the Android-OS bug before either ;0)

I´ll stay with 4.8.3 for now since that is the most stable version (at least for me)

Thank you ;0)
[Nexus S Android Development] KrisMurdrum:
What does Better Battery Stats say under Partial Wake locks?

Carved into the void with my Magic Rune Stone
[Nexus S Android Development] alen1901:
I would like to flash 5.1 stable but with extra RAM juice. :p kidding, im still testing 5.0.2 with 413mb od RAM, no problem after that 1st reboot.

EDIT: android OS 10% after phone sleeping 8hours, android system 6%. Locations and Google now disabled.

Sent from SpeedMachine i9023
[Nexus S Android Development] anshumandash:
I know what you are saying. Honestly it is difficult to correlate as many are not having this issue, but some are having. On my phone I can use any version of 4.8.x without Android OS issue, but cannot use any V5 version. Just to test, I tried a different kernel (Non Marmite) yesterday, and did not get any Android OS issue.

The only change I see in 5 compared to 4.8 is that high resolution timers are disabled. Is it that some phones are having Android OS issue due to this? I am not an expert and don't even know what high resolution timer is. :silly:

Also want to ask everyone facing Android OS issue, if they ever tried enabling MTP in the past? In my case, I tried it immediately after flashing V5 and the same day observed Android OS issue. Currently neither MTP works nor I am able to use any of the V5s, but not sure if it has anything to do with this.

I have tried re flashing the ROM multiple times with format cache & dalvik, fixed permission multiple times etc. I don't use google now & location services, maps etc are not even installed. I have minimal apps with only emails with sync enabled.
[Nexus S Android Development] dekaru01:
In case you can see the attached image (tapatalk sometimes screws image upload for me), can any of you please tell me which kernel this is? Bedalus?

I just wanna be sure, because it's by far the most stable and reboot-free marmite I've ever used. And yeah, can't remember which one it is (too much flashing).

By the way, is it impossible to add the kernel version number to that kernel info? Would make my life much easier if it were possible.

Anyway, thanks for the great work Bedalus.
[Nexus S Android Development] :
It's v5
[Nexus S Android Development] kwibis:
Running 5.1 and no os problems here. Had it with the previous version!

Sent from my Nexus S
[Nexus S Android Development] :
I've got a long to-do list now.

Read all the posts since Sunday in case there are outstanding issues, and kmsges to read.

Benchmark bfq and cfq thoroughly. EDIT: DONE!

Add custom voltage for 1.2ghz

See if Android OS bug is really a kernel issue or not.
[Nexus S Android Development] caliban2:
Running 5.1 and also no problems with android-os and -system. Was a "problem" (just wrong reporting?) on ICS, but never on JB. I never had Google now turned on, it's utterly useless here in Europe.
[Nexus S Android Development] anshumandash:
I will flash one of the 5.x and report back on what better battery stats reporting on partial wake locks.
[Nexus S Android Development] caliban2:
Also check alarms in BBS.
[Nexus S Android Development] :
Post-birthday post catchup:

It's not the bigmem patch, it's that the gallery/youtube/camera can't handle the extra RAM versions that I sometimes drop in the thread. Use the usual one from the version matrix. Future "reasonably nice" versions will have 411MB to avoid breaking certain camera features (i.e. rotating icons)

I think I've just worked out that this must be some woman from a TV show.

I think this is solved in the latest version. Can you comfirm? EDIT:

Okay! All is well.

Erythnul has lots of experience in solving battery issues, so it may be worth sending him a PM, or post using the template from the OP.

I will look at this soon.

I'll be doing this test asap, and I've already built it into the kernel I'm running, which made me very nauseous.

I don't support BLN / ROM integration, you'll have to cope with init.d scripts. Fortunately the are two or three links in the OP to make scripting easy.

I'll take a look at these asap. But as others have said, whether or not OC is stable on your phone depends on pure luck really.

I'll take a look asap.

I've been drinking for 16 years! (two of which were just getting-away-with-it....)

I'll take a look, but again, success with OC is pure luck.

In arch/arm/mach-s5pv210/mach-herring.c

#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_MFC0 (13312 * SZ_1K) // (11Mb 11264) (13MB 13312)
#define S5PV210_VIDEO_SAMSUNG_MEMSIZE_MFC1 (13312 * SZ_1K) // 11MB will work on Slim Bean

will give you 411MB and fully functioning camera app. A value of 10240 will give you 10MB, but will break the icons in the camera app.

Cool, I'll take a look.

This always happens when I think I've released a stable. I'll take a look :p

Thanks, that was the persuasion I needed to consider this version of BFQ seriously.

Yep, please keep us posted.

abcdefg (just so I can search for this post later for convenience)
[Nexus S Android Development] micha3lvd:
I've noticed when I leave my 3g on my android-OS goes way up... it even reached like 35% in like 15min..

Im using Marmite v5.1 + Slim Bean 2.7 settings stock..

everything is fine with 2g on btw..
[Nexus S Android Development] benoit2600:
Kernel Panic ! :victory:

Finally a useful last_ksmg log : http://pastebin.com/Ny5wFYfK

the complete log : http://dl.dropbox.com/u/141920/last_kmsg_kernel-panic

It happened on my kernel, but as you can see in the github commit, there is no big change compare your 5.1 kernel ( only some frequencies, and re-added deadline)

I will study it when I'll come home, but you may have an idea why it's happen.

during the kernel panic I use the xda app, with smartassV2 and deadline scheduler.
[Nexus S Android Development] anshumandash:
I never thought about the 3g piece while reporting Android OS issues. I use 3g all the time as I don't use wifi at all. Haven't tried 2g as well.
[Nexus S Android Development] caliban2:
Another FYI for bedalus:

https://github.com/cyanogenmod/andr...mmit/c57ef84caa825c4907f2b01590e82a6be1740af5

https://github.com/cyanogenmod/andr...mmit/59e8adb435a8c45e2ad6ff06949a5b4ecbd4fe5d

PS:

I'm not sure yet, but beginning with today's nightly (1017) CM might have introduced some more stuff that requires adapting custom-kernels... My vid-playback died (players, youtube, browsers, sw and hw-decoding), a simple reboot fixed it. Never happened this way before (working for a few vids and then poof). Also opera suddenly takes some thinking-pauses now and then when scrolling large pages (it uses hw-acceleration).

From the change log I can see there have been more commits to kernel than just the two above and bfq-stuff, so maybe... Or it's the ROM itself, after all it's a nightly… ^^ Will reflash later and test without marmite.
[Nexus S Android Development] muller37:
my android os is currently at 38% with wifi on and 3G off, location and now disabled.

i9023 on v5.1 with CNA 3.6.6.
[Nexus S Android Development] polobunny:
I doubt bedalus wants to support someone else kernel, even if it's based from his. He pulled deadline because the performance wasn't consistent by the way, and also because he doubted it could be unstable.
[Nexus S Android Development] caliban2:
Mine is currently at 4% with WiFi off and 3G on (shaky, switches back and forth between 2G and 3G), location (not GPS) enabled and now off.

i9023 on v5.1 and CM nightly 20121017.
[Nexus S Android Development] muller37:
my OS usage went up after updating to CNA 3.6.6. Could the OS bug be rom specific?
[Nexus S Android Development] benoit2600:
Yes, I understand, but there is very little modification in my kernel, so I think it could happens on bedalus kernel too, that why I post the lask_ksmg here. I will understand if he doesn't want to check the file, but I can't keep it for myself if his last commit + mine could affect bedalus kernel 's stability.
[Nexus S Android Development] :
People have reported this mainly with cna, but not exclusively.
[Nexus S Android Development] Articudos:
I think so too.:)

8% android os here. Rasbeanjelly oct 11 version.:)

Marmite v5.1
[Nexus S Android Development] polobunny:
10% Android OS here (high because my phone has only been in standby today so far, or nearly), marmite v5, cm-10-20121011.0549-crespo.

Something conflicting somewhere between kernel & rom.
[Nexus S Android Development] kiden:
Okay, so I tried it out on 4.8 and with Location and Google Now off, 4% Android OS, as soon as either of those is on, it jumps to 23% and destroys my battery life haha. This is on Slim Bean 2.7.

As soon as my phone is charged up, I'm going to try the newest stable with location and google off, and see what kind of Android OS usage I get.
[Nexus S Android Development] polobunny:
Do you have any tweaks applied in Slim Bean tweaks section? Since beddy uses it, it shouldn't pose a problem. Unless something was changed, or it's not a ROM issue per se.
[Nexus S Android Development] :
Yep, I see what you mean, and I'll have a new version ready soon.
[Nexus S Android Development] kiden:
Do you mean the init.d tweaks? Yeah, the fix permissions and zipalign apks on boot. Oh and the sd card speed boost.
[Nexus S Android Development] polobunny:
Yep these. Wondering if it's not something that is conflicting. Stock seems fine, CM seems fine, CNA some reports of high android usage, and you with Slim Bean.

Edit: Would you mind disabling these and seeing how that goes? I don't believe bedalus uses them, although I could be wrong. You know just in case one of these tweaks stays stuck and that's why you get a high android os usage. :)
[Nexus S Android Development] kiden:
Well, on 4.8 with those on, I had no problems. (As long as I kept location off.)

Above 4.8 with those same settings, I get the high android OS usage.

Its reproducible with just flashing back and forth 4.8 and >4.8, and not changing any settings. Makes me think its something in the kernel because It comes/goes just based on which version of the kernel I'm running.

But I've turned them off, Im going to try 5.1 see if I get High Android OS on that one.
[Nexus S Android Development] polobunny:
I understand, but it doesn't mean it's not something conflicting between a difference in the kernel and a tweak in the ROM. Doesn't mean one is right and the other is wrong, but if the issue doesn't happen on stock ROM or most roms... :p
[Nexus S Android Development] alen1901:
I have cna and zipalign on boot activated. Android OS 10% max. I dont think scripts would couse that. I would suggest to all of you not to pay attention to that right now. If your battery is still good with high android os, there is no problem, many reportings of this aware problem is going nowhere. :D

Sent from SpeedMachine i9023
[Nexus S Android Development] kiden:
Well, whenever the Android OS is high, my CPU reports it doesn't stay in Deep Sleep all the time and goes into 100mhz instead. This eats up battery really quick.

So I turned the tweaks off, and flashed 5.1 and cleared out my battery stats. My android OS was upto 34% and battery was draining pretty quick.

I rebooted into recovery, flashed 4.8 again, and cleared battery stats. Android OS stays at 4% and battery drain is back to slow awesomeness.

Same behavior I've been experiencing with anything above 4.8.

I'm running slim bean 2.7 w/ GNow installed, but turned off. Few Apps installed.
[Nexus S Android Development] polobunny:
Then again, no one has any clue what's causing that because so far nobody's trying anything except the usual wipe + flash and wipe + flash and so on. Might not be zipalign itself that does it, but not unlike the media scanner process getting stuck it's not impossible something else is getting stuck. ;)

I don't believe there's always "no problem" if the android OS use is high but battery is good. There's a difference between misinterpreting the battery stats (which are arguably very easy to misinterpret) and a real problem not affecting battery life too bad. Both may look similar at a quick glance or to someone misinformed but the later is a real reason to worry.
[Nexus S Android Development] caliban2:
Yeah, right, we get it - "something" doesn't work with 5.1 on your phone and ROM, and with 4.8 it does. How about you using betterbatterystats to find out which process keeps your phone awake with 5.1?!
[Nexus S Android Development] polobunny:
Thanks for trying!

So no go on the init.d tweaks from you. Aaaaaaand back to hypothesis.