yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] kodora:
When it happened to me I was using touchpal keyboard and go sms. What ROM are you using? It could be a ROM problem.. I´m on rasjellybean. I am asking you all this to try sort the problem out, since bedalus already saw one of my last_kmsg and he concluded it wasn´t kernel related..
[Nexus S Android Development] polobunny:
Flashed 4.5.4. Colors once reset are alright. Luminosity is a tad on the dark side (red and green too dark), did not notice much difference regarding gamma. Closer to neutral however as I see it, a bit too lacking in contrast still. Grey has a noticeable cold feel (once again with defaults).

As for idle drain, we'll see as time passes tomorrow while I'm at work. I know what to expect from just testing 4.5.3 today and my usage is very replicable... Keep it in my pocket. :P
[Nexus S Android Development] :
It's a CFS. BFS causes problems.

Here: http://goo.gl/iJXWI

When I did those tests I used two different kernels, six different governors, and I think six different schedulers, and ten tests for every combo. It was a **** load of tests. The aim was to figure out whether there was a best scheduler to combine with a governor. Several months have gone by, so I don't remember specific details, and I no longer think that my results were 100% on the money.... But what I do remember is that when you look at all the results as one giant scheduler benchmark, CFQ wins, with deadline close behind.

Also, in the considerably more focussed test I did (a few posts back where I uploaded the spreadsheet) again, CFQ and deadline were pretty much tied.
[Nexus S Android Development] :
@testers --- can you do me a favour and start some music on shuffle, then load antutu and start a full benchmark, then turn your screen off. Wait a bit, then see if deep idle stopped accumulating?
[Nexus S Android Development] :
Throughput benchmarks only tell you so much. Throughput is one thing, but the main thing which affects system responsiveness under normal I/O loadings is request latency. Tap benchmark is the only one which I can think of which measures request latency.

I'm not sure what benchmark rates CFQ higher than deadline on flash though, that's not what I found when I compared them. I might do some more tests and see if CFQ improved since 2.6.35.13 (which is the last kernel I tested it on), but I'm not holding my breath.
[Nexus S Android Development] JokerAce:
Thanks. Can I say that under heavy load, deadline has higher latency than BFQ?

I tested Air Kernel and BedalusKernel, both favored CFQ. And thus far, CFQ seems well.

:O CFQ and Deadline tied :mad:

My usage wise is, I read and browse alot, plus occasional gaming. And the game I play are quite RAM intensive (e.g. dungeon defenders). So, would BFQ, CFQ, or Deadline be a better choice base on my usage?

Anyway, I noticed my phone can't go 1.2 mhz.. It just reboots and reboots under heavy load. Sad me.
[Nexus S Android Development] caliban2:
i see, simulation of a perfectly normal every-day-situation... yes, deepidle is broken after this test and needs a reboot.
[Nexus S Android Development] :
Not necessarily, but it might be more inconsistent if there was a lot of concurrent reads and writes going at the same time. But then, those kinds of loads are unusual on a phone anyway.
[Nexus S Android Development] N@th_OC:
I made your test and yes deep idle stopped accumulating.

I have reset the DI stat before the test And after, DI was still to zero.

Edit: Yes a reboot is needed to make Deep idle work again.
[Nexus S Android Development] Randomwalker:
For me TOP=ON stops accumulating, too. TOP=OFF didn't work anyway.

Also requires a reboot to fix.
[Nexus S Android Development] 309041291a:
What a the battery like?
[Nexus S Android Development] :
Just did some very unscientific tests on different I/O schedulers, Deadline, CFQ, BFQ.

I found that Deadline and CFQ are pretty much matched.

CFQ is slightly faster at sequential single file operations and is more consistent than deadline overall but slightly worse at database manipulations and with parallel reads and writes.

BFQ is slightly faster than deadline but slower than CFQ at file operations, but much poorer at database write operations. It is faster than CFQ and deadline at parallel reads and writes. It is also the most consistent out of the three with a considerably lower standard deviation on each iteration.

Deadline has the lowest latency, followed by CFQ and then BFQ, although there only a few microseconds in it.

After those findings, I tested boot time. Boot time was measured from the time vold started to the time MediaStoreImporter finished checking the media library. (adb logcat -v time will give you timestamps on the logcat output.)

I did 3 runs with each, and because the deviation was only a couple of seconds, I decided that would be accurate enough for the purpose.

Fastest was deadline, with an average of 1:28, followed by CFQ at 1.32 and BFQ at 1.58(!). So, you can see there is very little between deadline and CFQ, but BFQ increases the boot time substantially.

So, tl;dr: Use whichever I/O sched you like, I suspect BFQ is slower to boot due to the poor database write performance. If that bug could be resolved, it would be the best I/O scheduler to use.
[Nexus S Android Development] :
Thanks @brave testers for confirming. It's going to be important for DI to work without ever failing, otherwise the 800MHz fixed freq tweak will eat all the battery! I'm working on a fix.

Thanks thalamus for his continued expert input!
[Nexus S Android Development] caliban2:
v1.1 is really aggressive about resetting min-cpu to 200. Bedalus, I'm too lazy to read it up in your benchmarks ^^ - is there a big difference between 100/200 when it comes to battery drain?
[Nexus S Android Development] caliban2:
There are two possibilities why you only get top-on:

- you have Bluetooth enabled or GPS in use (just enabling GPS doesn't prevent top-off)

- your rom is missing the mod which disables Bluetooth quick-switch (I can't remember which sys-apk needs to be decompiled to disable it). Which rom are you using anyway?

Talk being the cause was a very long time ago (wasn't it the version capable of vid-chat?) and it's been fixed. At least it doesn't cause problems on my sys.
[Nexus S Android Development] Randomwalker:
I definitely have BT in use as I listen to music (see test) via a BT headset.

ROM is CM9 nightly 05/07 (includes BT fix AFAIK).
[Nexus S Android Development] caliban2:
Yeah, rom is okay. Disable Bluetooth and see if top-off registers.
[Nexus S Android Development] Randomwalker:
After a few reboots, it worked. Will repeat the Music+AntuTu test. Thanks!
[Nexus S Android Development] :
Yes, when you are at 100 your bus clocks down, so it's very power saving as frequency is the main factor in power drain.

The 200mhz thing is an nstools bug, just use an init.d script and disable nstools' restore settings function.
[Nexus S Android Development] caliban2:
Good. Strange thing is you needed a couple of reboots though. This should be (and is) an on-the-fly-thing, no reboot needed. :confused:

Aw, damn. I like nstools. ^^

Will do. Maybe the guy who wrote nstools is still around... *fingers crossed*
[Nexus S Android Development] Randomwalker:
Well, maybe it's because I first tried turning BT off after breaking DI (via AnTuTu+Music for a 2nd time). When taht didn't work I rebooted twice with BT off. That still didn't restore DI (ON or OFF). After a third reboot I switched BT back on. After that ON registered again and after disabling BT OFF registered. So it actually was the first time I switched off BT while DI was working and within the same "session".

TL;DR: Maybe the reboots needed are not relevant.

Anyway, redoing the test with working DI OFF broke it again. Reboot needed to fix it.
[Nexus S Android Development] :
I think what i need is some sort method to detect if deep idle has done a whoops, then somehow reinitialize it. Easy... :what:
[Nexus S Android Development] sdhanjal15:
Aokp by euroskank
[Nexus S Android Development] hiphopboy:
2 time hang screen and auto restart with 4.5.4 ! i don't think this build is ok
[Nexus S Android Development] :
Thanks for testing everybody!

Unfortunately my overnight IDLE2 drain was much greater than the previous night.

I'll keep pulling the wires and see if i can nail the issue.
[Nexus S Android Development] caliban2:
Marmite 4.5.3 breaks today's cm10-nightly (20120919), doesn't boot: google-logo, then just a black screen. Guess they changed smth, boots fine without marmite.
[Nexus S Android Development] peepee999:
This my battery stats with marmite 4.5.3 with black bean-4

Bedalus is this good?
[Nexus S Android Development] alen1901:
Yeah its good. I get 4hours screen on time with 20% left.

Sent from SpeedMachine i9023
[Nexus S Android Development] kodora:
I believe now that this is a ROM problem.. We can only wait for an update and check if it is fixed.. Btw, I have been a few hours now w/o any reboot! :cyclops: You can also go to recovery and try "fix permissions" but for me that has been a kind of placebo solution.
[Nexus S Android Development] kwibis:
LOL How can you work with your phone while it's looking like that. Guess everybody's taste is different.
[Nexus S Android Development] kodora:
Just sharing my latest stats: I´m on rasbeanjelly and marmite v4.5.3
[Nexus S Android Development] caliban2:
Dafuq is up with all those screens lately?! :banghead:

Post them in general section if you must, but not here. We all use our phone differently, have different setups (apps, sync), different network-surroundings, etc etc - YOUR stats are pretty much useless!!!

(except when it comes to specific stuff like excessive android.os-drain, excessive time-ticks with idle2 and so on, but currently that's not the topic)
[Nexus S Android Development] peepee999:
Lol i like it that way.
[Nexus S Android Development] polobunny:
So far from half a day testing, 4.5.4 seems to be taking twice the battery during idle than 4.5.3. That translates to around 1% per hour vs 0.5% per hour with a very similar usage (AKA none). Twice make it sound much more extreme than it is though.

Deal breaker? No, clearly not. 1% per hour is still very good. That's with mobile data and wifi off by the way. But most people phone spend more time idle than not during a day, so every ounce of idle saving you can get is important I imagine. :)
[Nexus S Android Development] Articudos:
@bedalus

Maybe you have clue about this problem:

I dropped my phone and found little blue spot(I guess pixel blown away).

but few minutes later, spot disappeared and having flickering (not green) when I turn off screen.(4.5.3, 4.5 both.. with rasbean)

Is there way to solve this problem..?
[Nexus S Android Development] polobunny:
Apparently people are having issues with Jellybro not booting even with stock kernel, so might not be marmite related!
[Nexus S Android Development] caliban2:
There were two cm10-roms yesterday, both 0918. First one worked fine, second didn't boot at all. Today's (0919) is fine again. Yesterday's jellybro (=last one) seems to be based on the second, by the time it has been compiled it can't contain the fix from today's cm10.
[Nexus S Android Development] polobunny:
Yeah, I was simply stating it didn't seem to be a marmite issue not to scare less knowledgeable users way. :)
[Nexus S Android Development] :
Yep. Did another attempt but kept it to myself today. Still doesn't work properly. Grr.

This seems to be a feature of ROMs with the latest Google source code. Sounds like your phone was seeing stars for a minute. It's probably fine. Restore to an older nandroid to see if the screen-off flicker has gone. Actually, I wonder if google fixed the animation problem for i9023, and now we have a new problem due to the previous kernel hack that fixed that problem.... I'll remove it and see.

Yep, sounds like CM got a reticent build. Not a kernel issue! :D
[Nexus S Android Development] caliban2:
Sorry, beg to differ here. ^^

Yes, CM had one bad build (2nd 0918), but it's fixed now (0919), running it all day with cm-kernel and it's fine. Marmite breaks it though.

You might want to have a look at this commit (and the earlier two it belongs to): http://review.cyanogenmod.com/#/c/23544/
[Nexus S Android Development] :
Aha, thanks very much. I wonder if this will cause problems with AOSP ROMs. I'll put it in and build a test version.
[Nexus S Android Development] polobunny:
Got 2 reboots with 4.5.3 using rom in my signature. First one was a reboot to CM splash screen then to Google with padlock logo and back to CM splash then to booted. Second one was a freeze, soft keys responding but nothing on screen. Using kernel defaults (ondemand/deadline right?). Couldn't pull a last kmsg because of the last time I had to pull the battery. Both were experienced while using my phone with app Rage reader. :/
[Nexus S Android Development] :
Ah, no it breaks AOSP compatibility. CM causing trouble again. I'll wait and see if someone like morfic can work around it.
[Nexus S Android Development] :
I'm going to test and upload v4.6 with no IDLE2, with CFQ as default, and with high res timers disabled. I think this stable release will be, uh, more stable than the previous stable... :p

Should be up some time in the next 24 hours.

Edit: Already the weird screen-off flash is gone, which is nice.
[Nexus S Android Development] polobunny:
Still running 4.5.3 but this time using CFQ. Played a game for a good while, surfed some rage comics and no reboot so far. Crossing fingers.
[Nexus S Android Development] :
v4.6 is here: http://goo.gl/HvUrp

-Stable

-CFQ

The changes are minimal, but I'll explain my rationale anyway. CFQ has very slightly worse throughput than deadline, but according to my long-rigorous-boring tests it does in fact offer better consistency than deadline. I've had a few freezes with deadline, that after a while seem to resolve themselves; it's as if my phone is just 'not playing' for a minute, but snaps out of it on its own. On CFQ I've never had that problem. I think Google offer it as the default scheduler for a reason! I may completely remove deadline in the future if a sufficiently long time passes without any of these long freezes.

-Disabled high resolution timers

This is necessary for IDLE2 to work, but since I cannot fix IDLE2 I've disabled them. I have a feeling that they cause problems. This isn't based on anything scientific. I just remember in the ICS version, disabling them seemed to completely solve reboots.

-Fixed weird screen-off flash

This was caused by a previous hack to fix the broken crt animation on the slcd i9023. Amoled versions never had that issue.

If slcd i9023 users are reporting about the crt-animation, can you please feedback which ROM you are using.
[Nexus S Android Development] matatr0n:
v4.6 isnt bootig with cm-10-20120920-NIGHTLY-crespo, it stucks after the google-logo
[Nexus S Android Development] leap_ahead:
for me is boot ...rom is at my signature
[Nexus S Android Development] spupuz:
pls can you posth the link here directly?
[Nexus S Android Development] leap_ahead:
i have the problem with crt ...not working ...
[Nexus S Android Development] :
Which is worse, the broken crt animation, or the screen-off flash?

DoubleX may need to update to the latest google source code.
[Nexus S Android Development] leap_ahead:
Broken Crt Animation ...
[Nexus S Android Development] kkkhattak:
I can't open the download page from phone?Can somebody provide a link please.?
[Nexus S Android Development] :
removed
[Nexus S Android Development] asphantix:
I was never affected by any screen off flash on my i9023 stock ota

Crt broken here
[Nexus S Android Development] :
CM nightlies are not currently supported
[Nexus S Android Development] asphantix:
Uhm, I don't really get that poll :confused: The screen off animation was fine in 4.5.3. No flicker at all and a CRT animation like expected.
[Nexus S Android Development] :
Ah, I see what's going on here. The hack required to fix the broken crt animation on SLCD i9023 causes a screen-off flash on amoled i9020.

Ignore the poll. I need to think about what to do.

EDIT: There's a way of checking what device the kernel is running on, then the hack can be applied selectively. I need to remember where I saw it.

EDIT: Found it. Building test version now.
[Nexus S Android Development] caliban2:
Which, btw, reeeaaally blows. Big time. :sly: :p
[Nexus S Android Development] :
Having trouble with accessing google docs?

all versions: http://goo.gl/B0p8Z
[Nexus S Android Development] :
CM have brought in a kernel tweak that depends on a ROM tweak. If I'm going to support CM nightlies, it means I have to build and upload another three separate versions. I can't be bothered with that.
[Nexus S Android Development] polobunny:
I have the feeling you'll have to figure out something to support CM10 nightlies without building a billion versions for people to still follow marmite dev. Will test 4.6 and report later today. :)
[Nexus S Android Development] TG2708:
Which kernel works for rasbeanjelly, stock ota or all other ROMs?
[Nexus S Android Development] :
Use 'all other roms'

Stock OTA is for the version of android google would send you OTA (Over The Air). It's sometimes known as stock JB or just stock for short. If you have flashed anything other than stock, use 'all other roms'
[Nexus S Android Development] :
Thanks for the support. There may be a way to do it. I'll ask some other ROM developers for their take on it.
[Nexus S Android Development] caliban2:
I know, I know...

But before people get the wrong idea: this doesn't just affect nightlies, but all upcoming monthly-builds, release candidates and stables as well. Plus all kangs.

Just keep in mind that should there be a possible way to make marmite working again, you always have a somewhat knowledgeable beta-tester in yours truly. ;)
[Nexus S Android Development] :
http://d-h.st/XyL

Would someone on a custom ROM and slcd i9023 please test and see if crt is fixed in the above version? Thanks!
[Nexus S Android Development] Articudos:
Hmm...any clues...?

------------------------------

BTW, for the crespo gsm, Anykernel type isn't helpful?(I mean, boot.img type for NS4G, and anykernel type for NS3G.... so you can do less job..;))
[Nexus S Android Development] leap_ahead:
2 min to flash !
[Nexus S Android Development] asphantix:
Does not boot ^^
[Nexus S Android Development] :
I already answered that question I think
[Nexus S Android Development] :
Okay, I'll build one for you to test
[Nexus S Android Development] leap_ahead:
ok is working now !!
[Nexus S Android Development] :
You're on stock ota aren't you? Try this one: http://d-h.st/Qth
[Nexus S Android Development] :
God damn. I'm getting better at this kernel dev stuff.
[Nexus S Android Development] asphantix:
Damn, I forgot about that :silly:

Thanks, flashed this file and it works.Beloved CRT-animation works flawless.
[Nexus S Android Development] :
DO NOT FLASH if you are not on the latest CM nightly. It won't work on AOSP, Stock OTA, 4G, and may not even work on the latest CM nightly. It's a test version!

TEST VERSION: http://d-h.st/6Jc

You can try this and see if it works on the latest nightly. I don't know if I made all the required changes or not.
[Nexus S Android Development] caliban2:
You know, you really ARE getting good at this. No wait, you've been good from the beginning. So you're getting even better. :)

Boots fine. Now we have to wait if it does something funny.
[Nexus S Android Development] Articudos:
Aha, my eyes were trolling...;)

Hmm...But turning on screen is little bit slow..

BTW,

Anykernel cannot fix boot loop in official miui and cm nightlies..?
[Nexus S Android Development] mustatir:
Can i flash on paranoidandroid?
[Nexus S Android Development] towelboy:
I can confirm it is working on lastest cm10!
[Nexus S Android Development] gregorypeg1000:
Bedalus,i was wοndering if you can add an 1.1ghz step in you kernel.
[Nexus S Android Development] peepee999:
I still have the crt problem
[Nexus S Android Development] gregorypeg1000:
Just had a freeze and reboot on 4.6 . Here's tha last_kmsg http://pastebin.com/C1JDyVKi
[Nexus S Android Development] polobunny:
Isn't that your current kmsg? You need last_kmsg.
[Nexus S Android Development] gregorypeg1000:
It is the last_kmsg file in /proc .Isn't that the one i need?
[Nexus S Android Development] polobunny:
That's the one you need, but the one you supplied stops very early after the boot. Pretty much before you did anything with the phone...
[Nexus S Android Development] leap_ahead:
On 4.6 i have high android os
[Nexus S Android Development] polobunny:
I noticed my battery drain to be slightly higher on 4.6 than 4.5.3. After checking my battery stats it seems Android OS is eating a bit more than what I usually have, at nearly 8% (while it was at 4% or so usually, and it's at 8% but I didn't charge completely so the battery stats weren't reset and I played a game yesterday so it would likely be higher than 8% on the true consumption for today only). Some bigger than normal keep awake times too.

4.6 battery drain seems similar to 4.5.4 overall, if only so slightly less. Favorite so far still 4.5.3 and with CFQ it looked stable. Deadline gave me a few reboots in a very short time, although it could be a pure coincidence knowing that CM10 kangs aren't exactly stable material.
[Nexus S Android Development] migueldbr:
same here
[Nexus S Android Development] :
Any kernel breaks Mtp

Sorry, no.

Can you include your ROM and phone Model

Hmm. Me too. I must have meddled too much with something!
[Nexus S Android Development] :
For people still having the crt problem, please tell me your phone model and ROM. Make sure you re-download v4.6 because i fixed it 10 hours ago
[Nexus S Android Development] :
http://d-h.st/Z0D

The above version will not work on 4G or Stock OTA

Any testers willing to see if high Android OS bug has gone? Please use the kernel as you normally would, and after a few hours see if Android OS is abnormally high. Also, please check crt animation is correct on i9023

EDIT: I'll condescend to uploading separate CM Nightly compatible versions, but only for my stable versions. From now on, incremental/testing updates will only be for non4G All ROM version, who outnumber other users by at least 5 to 1.
[Nexus S Android Development] hiphopboy:
i'm ready :)
[Nexus S Android Development] polobunny:
Are you sure about other roms being so popular? You know cm nightly means nightly, stable, kangs and all based roms... That seems like a good chunk of the people. :S

So can CM users test that new version you posted or that's a no no?

Edit: Flashed 4.6 os fix. We'll see how it fares tomorrow.
[Nexus S Android Development] deani77:
Flash it now on PA 2.13... CRT effect working on my SLCD on latest OSfix kernel
[Nexus S Android Development] leap_ahead:
crt is ok here too ..androis os fixed !!
[Nexus S Android Development] peepee999:
Same here

---------- Post added at 07:39 AM ---------- Previous post was at 07:34 AM ----------

Going back to 4.5
[Nexus S Android Development] _yaz_:
confirmed. consumption is significantly higher. however, i haven't exprienced the extreme peaks at phone calls having had with the earlier versions. so, all in all, 4.6 is not so bad for my routine use. testing now the fixed version.

sure, you did. but, imho, the right way.

i don't think so. both do what they should. deadline may become inappropriate when the stack is full with parallel processes, cfq just slows down the hurry while arranging the queue to the fair order. that's it. having completed lots of tests i always return to ondemand/cfq as the most reliable combo.

@bedalus

in an early comment you suggested to re-flash the rom if changing from your mtp-kernel to a non-mpt one. does it hold true, yet ?
[Nexus S Android Development] asphantix:
the high android OS bug is also present on stock rom with v4.6
[Nexus S Android Development] :
We'll see when i split cm nightly into separate download
[Nexus S Android Development] :
If you change to another kernel that uses the any-kernel script, yes, flash ROM again first. No wipe needed.
[Nexus S Android Development] :
Are you sure? What about when the phone is idle?