yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
I see that there's been 26 downloads of the MTP version, and 60 of the IDLE2 version, since I uploaded them. It's nice that people are so willing to test out experimental features. Keep the bug reports coming!

Has anyone tested the MTP version since yesterday? What was the battery usage like while the screen was off? Any inexplicably long periods of being awake?
[Nexus S Android Development] CrackerTeg:
Um. I have no idea which one I just downloaded and installed. All I know is that my phone is flying coupled with rasbean.

Nevermind. I just looked and its the idle2 version. I don't know what's with me these days. Lol
[Nexus S Android Development] Imppy:
4.45?
[Nexus S Android Development] CrackerTeg:
4.4.6
[Nexus S Android Development] TG2708:
do you have the link to the inverted gapps?
[Nexus S Android Development] CrackerTeg:
Look in the themes forum. I started a thread with them but had it locked. The link is still good.
[Nexus S Android Development] mishamosher:
Been trying 4.4.6 MTP version on a i9020A, and bettery is doing fine. Two hours of screen on plus wifi plus bluetooth plus browsing eated 25%. 5 hours of music, soft gameplay, and some document reading eated 25% also.

In the first case, the most consumpting in the battery stats was Screen, in the second case was Android OS.

Beside of all the before mentioned, nothing else happened (not long awake periods, hangs, etc)

Tried on August 25th nightly of CM10, with 07 29 GApps, clean install (all wiped).

---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------

And forgot to mention... using SmartAssV2, MTP, 1.2 GHz OC, BLN and BLD
[Nexus S Android Development] gummie:
Where is the new MTP version for all custom ROM? All I see were MTP version for OTA.
[Nexus S Android Development] :
http://goo.gl/HvUrp

The above link takes you to a google docs spreadsheet where all versions will be posted. The link you want is currently in cell C5
[Nexus S Android Development] :
Cool. But I'm still confused about where this OS bug is coming from. It's never affected me. Are there any other users who have never had this bug? Or switched ROMs and the bug is gone?
[Nexus S Android Development] xjerlzx:
hmm...

v4.4.x gives me very bad battery and some random reboots with no ksmg.... (never tried 4.4.6)

so i went back to v3.4.39 for now... till i have the time to experiment again =X
[Nexus S Android Development] caliban2:
Compared to 4.4.6-idle2 I'm getting way better batt-life on standby with 4.4.6-mtp.

One thing puzzles me though, the time_ticks. In betterbatterystats, under "alarms" -> "android":

android (): Wakeups: 21
Alarms: 9, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 135, Intent: android.intent.action.TIME_TICK
Alarms: 5, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 14, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 12, Intent: android.content.syncmanager.SYNC_ALARM

Those with good batt-life, what's your value there?
[Nexus S Android Development] jojoost:
Deleted for the almighty, all-knowing, all-whatever-you-can-think-of-mighty Caliban2
[Nexus S Android Development] caliban2:
Everybody giving you an answer to this question will be projecting HIS needs and habits on you. Which is pointless, don't you think? Unless you have no habits and needs of your own, of course. Try it out yourself.

And have you noticed that there's a little bit of talk about batt-drain going on in this thread?! And what does this sort of question have to do in a kernel-thread anyway?!
[Nexus S Android Development] jojoost:
OK, sorry. I edited my post for your needs!
[Nexus S Android Development] gabling23:
I'm not able to use the metod described in the op to create an init.d script on rasjellybean rom.. What could be the cause?

Sent with Tapatalk 2
[Nexus S Android Development] CrackerTeg:
It's ROM related. Since it's an initial build, I don't expect everything to work flawlessly. I unchecked the set with init.d box in nstools and just let it go after boot complete.
[Nexus S Android Development] mishamosher:
Seems that it haz to be MTP, switched to IDLE2 version of 4.4.6 and Android OS is as low as 2~12 %. Did a reinstall and also a wipe of the OS before trying IDLE2 kernel, been running around 8 hours so far and its keeping stable for me, even with OC. Battery lasts a little more now, a gain of 2~5 % over MTP.

Anything that I can do to leave a better feedback, just let me know !
[Nexus S Android Development] dkm911:
Great performance and battery-life in 4.4.6! And seems Android OS draining has gone, only accounting for 4% after 13hrs use.

Er... Any plan to fix the CRT animation issue? Although it doesn't happen each time, still a little bit annoying. :)
[Nexus S Android Development] caliban2:
Perfect, that's exactly the opposite of my experience. Dafuq is causing this drain?! :what:
[Nexus S Android Development] :
My Android OS use is down to 2%

I'll get the ammeter out when my daughter is in bed, then I'll check the amps of IDLE2 v0.370. If good, then release!
[Nexus S Android Development] Blackcrx:
That's what k want to know too. The android OS drain is killing me. For whatever reason it only happens with marmite
[Nexus S Android Development] caliban2:
-> Bedalus' blinking BLN then, maybe?
[Nexus S Android Development] Blackcrx:
I disabled blink for BLN
[Nexus S Android Development] :
I'm still leaning towards the ROMs / apps / user settings / SDCard as the cause of the Android OS bug. I use BLN blinking and don't see any Android OS drain.

Anyway, I've just done an ammeter test, the drain is just as low as with IDLE2 v0.360, and I'm happy to release. I'm just need to build and upload. Shouldn't take too long.

In v0.370 wifi must be toggled on then off (then back on if you need it!) or IDLE2 will not work.
[Nexus S Android Development] :
v4.4.7 is here: http://goo.gl/HvUrp

Remember to toggle wifi on and off.

The command for displaying statistics has changed. Follow the link in the OP or the downloads page to the IDLE2 explanation for the new command.

Note: There is no new MTP version, because nothing else has changed apart from the IDLE2 code, which isn't in the MTP version.
[Nexus S Android Development] :
My android system / os drain is definitely gone, but idle time is still isn't that good. Lost about 15% overnight and was awake for quite a bit when I left my phone without charging (about 8 hours). Screenie attatched

Got about 3 hours screen time with this run, which isn't that bad :/
[Nexus S Android Development] FirePoncho86:
Off topic but..

You have a daughter? You have a family, a job and an amazing kernel with frequent updates? Bedalus, you're a wizard!

Sent from my Jelly powered Nexus.
[Nexus S Android Development] TG2708:
Hey bedalus which ROM do you use with your kernel?
[Nexus S Android Development] italia0101:
Quick question .... is it fixed at 800mhz due to instability with 400mhz?
[Nexus S Android Development] jojoost:
Dont ask it, or else caliban2 will take care of you... ta ta taaaaaah
[Nexus S Android Development] TG2708:
Who is this Caliban2? but I just felt the need to ask because the ROM a developer chooses are usually the best one to go to with the kernel he made.
[Nexus S Android Development] jojoost:
I asked the same question you did, and he got mad at me because I did so.. but I advise Codename Android!
[Nexus S Android Development] TG2708:
O OK thanks for the heads up. I personally uses cm10 crespo maintainers revision version and all I can say its very smooth with the kernel he uses.
[Nexus S Android Development] xjerlzx:
Http://imageshack.us/photo/photo/171/screenshot2012090209231.png/

Http://imageshack.us/photo/photo/405/screenshot2012090209230.png/

This is just sick, !!!!!!!

v3.4.39
[Nexus S Android Development] JokerAce:
Do you mean I place the whole phone into the alcohol and then let it dry in a bin of cat litter? Wanted to ask this a long time ago.

1. Never read properly

1.1 Never change permission
​

1.2 Never remove NStools "run on boot"
​

2. Never follow instructions to the letter and dot

3. ROM don't support init.d
[Nexus S Android Development] kkkhattak:
After every reboot we should perform this step for IDLE2 to working?
[Nexus S Android Development] jojoost:
No, you will have a lot of battery drain.. Just do it

---===:::Greetzz, jojoost:::===---
[Nexus S Android Development] :
You can buy a pressurized can of isopropyl alcohol (over 95% concentration) and spray the affected areas. If the whole phone is soaked, personally i would dismantle it, then spray, then thoroughly dry, then reassemble.
[Nexus S Android Development] :
That was the case with Deep Idle, but in IDLE2 I think 400MHz seemed to work perfectly. thalamus has raised it to 800MHz because it is preventing some sort of issue introduced between v0.360 and v0.370 where another part of the code wanted to set 800 MHz, so conflicted with the 400 MHz setting. It's only a problem if wifi doesn't get toggled on and off.
[Nexus S Android Development] :
Yes, after every reboot.
[Nexus S Android Development] :
For people interested in what ROM I use, there's a bit of history to that specific question.

I maintained a page of kernel benchmarks a while ago: here

After that I did ROM benchmarks: here

...and lots of people wanted to know what ROM I used, because I'd tested everything. Ultimately, the conclusion that I came to was that the performance of ROMs is pretty much equivalent, so long as the developer knows what they are doing and does not introduce conflicting tweaks.

At that point I decided to try to discover which threads had the best 'User eXperience' and came up with the UX benchmarks: http://xdaforums.com/showthread.php?p=24977641#post24977641

...but that project had some serious flaws, which I couldn't resolve, so I gave up on it. However, if you are a regular visitor to the forums, and spend time getting to know the various threads, you can see which ROMs consistently get good feedback. There's a certain logic to following the 'wisdom of crowds', however, nothing will perfectly suit everybody, because everyone has different requirement. Some people are keen on features, some people want stock.
[Nexus S Android Development] kwibis:
So you're just running a kernel no rom? :beer: just kidding, what rom do you currently run and are you satisfied?
[Nexus S Android Development] :
I'll use any ROM that has a brightness slider in the notification toggles.
[Nexus S Android Development] sperelli:
That's Wisdom!

hi there, I'm on CM10 Nightlies + marmite4.4.6.

i typed the string in terminal emulator and it answers: no such files or directory.

from which position should i retry?
[Nexus S Android Development] :
the last bit is error_stats

It changed to statistics in 4.4.7

Once IDLE2 is proven to be at its most power saving configuration, those stats will be completed disabled.
[Nexus S Android Development] Icecoldmeat:
Bedalus I want to thank you for all your work (benchmarks, comparisons, kernel, etc.), because I am moving to the Galaxy Nexus. I hope to see you there sometime. My mom has my Nexus S now, with still your kernel on it :)
[Nexus S Android Development] :
Nice! Hope to see you around :)
[Nexus S Android Development] FirePoncho86:
I'm posting this here because my problem may have to do with this. I'm using 4.2 with the bigmem patch. The bigmem patch is supposed to help camera issues, right? So last night, I took a picture using power shutter (which in in cna), oddly, the picture didn't save. Right after that, my power button was being selected when I wasn't pressing it, and after that my power button completely stopped working. Like I said, I'm only posting this here because the bigmem patch has to do with camera, and my power button is what I used to take a picture. Anybody have a similar experience?

Sent from my Jelly powered Nexus.
[Nexus S Android Development] superng888:
Awesome kernel :laugh: im running marmite 4.4.7 with cm10 31st Aug version and i noticed no lag with this kernel. It seriously mind bombing to see no lags in swiping, statusbar dragging and in opening application. But i cant seem to get MTP working on windows 7 :(
[Nexus S Android Development] alen1901:
Your power button is probably broken. Try with other ROM/kernel to be sure.

Sent from SpeedMachine i9023

---------- Post added at 04:08 PM ---------- Previous post was at 04:06 PM ----------

v4.4.7 doesnt have mtp. It has idle2 instead.

Sent from SpeedMachine i9023
[Nexus S Android Development] sperelli:
probably I had not been clear.

the command line I input doesn't give anything in return.

where's my fault?

thx
[Nexus S Android Development] :
In the above command, 'statistics' works for v4.4.7

You're on an earlier version, so use 'error_stats' like this

cat /sys/kernel/debug/idle2/error_stats
[Nexus S Android Development] :
Make sure you download the correct version. v4.4.6 is the latest version with MTP. If you are on the Stock OTA ROM make sure you download the correct MTP version.
[Nexus S Android Development] :
Unfortunately this does sound like you are describing a broken switch. Still under Warranty?
[Nexus S Android Development] Imppy:
Hey bedulas...what is the default schedule/governor settings used in 4.4.7? I'm testing it on ROM chocolate and see how it goes! It seems pretty speedy so far...will test battery
[Nexus S Android Development] caliban2:
I have MTP working with 4.4.7. Didn't try if there's a difference between mtp and mass storage regarding idle2 though - bit busy today. ^^
[Nexus S Android Development] doc_v15:
Man...I hope that every android devices has your tweaks in their kernel! makes life easier! Thanks Bedalus!
[Nexus S Android Development] rrohanjs:
hey bedalus, i read thalamus' note on wiping cache etc, what i want to ask is how important is fixing permissions after flashing a kernel ?
[Nexus S Android Development] FirePoncho86:
I'll try flashing other ROMs/kernels to be sure. I've heard of the power button problem, but never thought it would happen to me :(

My birthday was August 31, my warranty expired on august 31, 2012. The button broke on September 1, 2012.

Someone is trying to troll me.
[Nexus S Android Development] :
MTP kills IDLE2.

If you flashed over an MTP enabled kernel, you still have MTP.

If you want IDLE2 to work, you need to re-flash your ROM (with no wipe). This is the best way to ensure the correct boot.img is flashed to the boot partition. Then flash v4.4.7
[Nexus S Android Development] :
If it's only one day out, you might get some sympathy from samsung. Get in touch with them
[Nexus S Android Development] :
I have no idea under what specific circumstances that permissions go wrong, but some permissions are set in the kernel, and the sets of files/folders requiring special permissions can vary between ROMs.

I believe you can circumnavigate all issues whenever you flash a new ROM by booting once, before rebooting to recovery to flash a custom kernel.
[Nexus S Android Development] caliban2:
Yeah, I already figured it came from 4.4.6-mtp's boot.img.

Looks like MTP breaks C3-state, not idle2 as a whole. I just did a little experiment, saved the stat-file from all day (mass storage enabled), enabled MTP, let it rest for a few minutes, saved file2, re-enabled mass storage - rest - file3. C1 & C2 kept increasing with MTP, C3 didn't. After re-enabling mass storage, C3 is increasing again.

So I'd say the two can coexist, giving the user a choice. (Necessary? How is usb-speed with mass storage these days?)

(And of course giving you an earful from users who are not able to read instructions, complaining that on their phone idle2 isn't working and your kernel is crap, please fix yesterday... ;) )
[Nexus S Android Development] :
Hmm, I'd have to get the ammeter out to ensure this is the case, but if so, that is very useful information! :D Much appreciated.

In fact, I may have worked out how to do an any-kernel version of MTP. If it works, this means I can in fact release just one version for all ROMs including Stock OTA with IDLE2 and MTP coexisting peacefully...? That would be ideal. :fingers-crossed:
[Nexus S Android Development] :
v4.4.8 is here: http://goo.gl/HvUrp

IDLE2 version only. A minor update: fixes init.d in the case where the ROM doesn't have support in its own kernel; IDLE2 stats are disabled. If you like the stats, stick with v4.4.7 for now. Nothing major or particularly important has changed.
[Nexus S Android Development] caliban2:
Can't wait to see if it checks out with the ampmeter, but here are the files anyway.

In case it doesn't check out, the stats are to blame for the false alarm, not me! :angel:
[Nexus S Android Development] jimdem:
4.4.7 and 4.4.8 are super. The 'freeze' issue I had with 4.4.5 is gone completely. Thanks ;)
[Nexus S Android Development] micha3lvd:
So basicly whenever you've flashed a previous kernel of yours, which did had MTP enabled you need to reflash your ROM to make it work? Because looking at my stats IDLE2 is working fine.. or i'm just reading my results the wrong way xD
[Nexus S Android Development] sperelli:
Thx bedalus.

That's what I got on 4.4.7 ... what about it?

EDIT: attached stats' screenshot.
[Nexus S Android Development] Imppy:
Is the high android system sometimes due to switching kernel?
[Nexus S Android Development] dosesdoyle:
Do we still need to toggle wifi to enable IDLE2?
[Nexus S Android Development] :
Yes, toggle wifi is still needed.

Now, I've built an any-kernel version with MTP (!) and I'm amp-meter testing currently it. If it has the expected drain dBu, then I'll be very happy because it means I only have to build and upload one kernel! (...and any-kernel method is better anyway because you keep your ROMs ramdisk, so compatibility is fully assured.)
[Nexus S Android Development] FirePoncho86:
I will! Do you think they would say anything about my phone being rooted? Should I return to stock?
[Nexus S Android Development] :
Haha, yes, always cover your back!

The good news is that you are absolutely right! You deserve big thanks for your observational talent because you've just made developing this a lot easier!

Will upload the version I built now.
[Nexus S Android Development] :
Here is v4.4.9: http://goo.gl/HvUrp

It has MTP and IDLE2 and should flash equally well on all ROMs. If you have flashed any of my previous MTP versions you should backup your init.d scripts, and reflash your ROM (to ensure the correct ramdisk; DO NOT WIPE/FORMAT ANYTHING!).

For IDLE2 to work, wifi must be toggled on then off. This bug may be resolved in future releases.

Please note, IDLE2 stats are disabled in this release. This is for improved efficiency! Don't worry, it is working! I'm watching my amp-meter as I write this. If you don't know what an amp-meter (or ammeter for short) does: http://www.youtube.com/watch?v=gPuXpfZ-uzc

I need reports of the following:

-Does MTP work as expected?

-Does is work on Stock OTA?

-Does battery drain with music playing (+screen off) seem improved?

-Does anyone have the Android OS bug (+which ROM you use)?

-Does anyone have the unusually long awake periods (+did battery take a dive)?

The higher the standard of your report, the better, particularly if you are reporting a bug: please state your ROM; phone model; exact kernel version; system uptime; screen on time; other relevant usage stats.
[Nexus S Android Development] :
I sent it to a Samsung certified repair facility. Even though I reported that I used a custom ROM, they still fixed it for free! And I bought mine off ebay second hand!

I think you should return to Stock though just in case.
[Nexus S Android Development] caliban2:
Nope, MTP not working on 4.4.9, jumps back to mass storage as soon as it's connected to PC. Can't say anything about the rest yet, obviously.

Maybe you should put it somewhere that it's either "MTP and half-broken idle2" OR "mass storage and fully working idle2"...?
[Nexus S Android Development] :
Caliban noticed the same thing. It appears MTP and IDLE2 can coexist, so long as you remember to switch MTP off when not using it.

Thalamus has pushed an update, so I'll try to release another incremental update, and I'll bring the stats back for now. Also, i need to fix whatever stopped MTP from working in the any-kernel script, which will be tricky for "a bear of very little brain."
[Nexus S Android Development] sperelli:
Begging for an answer, Bedalus... :laugh:
[Nexus S Android Development] granets:
4.4.9 looks very good

Nice HighBigMem, finally got to 400Mb :)
[Nexus S Android Development] leap_ahead:
Hi bedalus i am back to your kernel ...

for me the 4.4.6 mtp working good.. with idle2 version i have lag on crt off animation ...
[Nexus S Android Development] :
I think thalamus fixed the statistical calculation after v0.360
[Nexus S Android Development] :
The crt animation lag with the IDLE2 is a strange issue. I think I might be able to fix it. Will try when I release v.4.4.10 later this morning
[Nexus S Android Development] dkm911:
Really looking forward to the CRT fixed version!! :good:
[Nexus S Android Development] italia0101:
Does anyone know what the Audio_out2 wakelock is
[Nexus S Android Development] ColdKiller93:
I'm using 1.5b ICS version with SlimICS 4.2. The Kernel provides the best batterylife i've ever seen on my phone, but is there any way to prevent reboots while listening to music? I experienced this phenomenom whenever I have deepIdle turned on and listening to music. Is there any recommended setting I could use to get rid of these reboots?

My settings: min/max: 200/1000Mhz

scheduler: deadline

governor: ondemand

DeepIdle: On

I didn't change anything else.
[Nexus S Android Development] superng888:
Cant wait for the next version to be out XD :silly:
[Nexus S Android Development] _yaz_:
everybody seems to care about mtp a/o idle2 but let me mention that blx does not work in any vesrion i've tried from the 4.4 series. init.c support is missing as well. what do I make wrong ?
[Nexus S Android Development] caliban2:
Give the man a cigar, i can confirm init.d not working on 4.4.9. BLN disabled and ondemand instead of smartass the whole day, never noticed it. not my best test-day I guess... :p BLX is set to 100 though, that's not standard, right?
[Nexus S Android Development] peepee999:
Pls has anyone used this kernel with baked bean? How is battery life with it.
[Nexus S Android Development] towelboy:
Has anyone encountered an issue where after leaving your phone overnight causes the network to lose signal? I tried fresh network and it could not get any signal so I had to reboot.
[Nexus S Android Development] _yaz_:
100% is the blx default but whatever is set it targets this ... :confused:
[Nexus S Android Development] miklosbard:
idle2 .380 is out, but be aware that the first link(atm it is in the OP I think) is a version with a bug in it, so look in the posts for the last link that was posted by _thalamus

edit: I just realized that you probably don't care about the link since you need the source, not the actual kernel, sry for spam
[Nexus S Android Development] MrBigWaffles:
Yep same problem. Really annoying

It only happens if you toggle 3G on.

It has come to the point that I just leave data off.
[Nexus S Android Development] micha3lvd:
Just wanted to report the battery results after full day of running 4.4.9

ROM: Epsilon Hybrid 1.2.0

KERNEL: Marmite v4.4.9

SETTINGS: Default (Ondemand 200 - 1000 deadline), MTP off, toggled wifi on/off on first boot

Screen on time: 2h

Wi-Fi ON all the time (left wifi ON even when not connected to a WiFi hotspot.. (not so long, max 30-40minutes)

And as you can see, a lot of Android OS drain..

if you need any more details please ask =]
[Nexus S Android Development] FirePoncho86:
Well, I would report back..but It seems my NS is bricked...
[Nexus S Android Development] italia0101:
Is it normal for the awake time to be 26m but only 6m of screen on....

Could it be Google now ? I love it to much to turn it off
[Nexus S Android Development] :
It might not be bricked. It might just be the power button. Head over to morfic's thread (Der Kernel) and get hold of simms22, I think he has had a useless power button for a while, and probably knows how to get around it.