yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
What I've done is set my screen timeout to 5 minutes, and i find i no longer need touch wake.
[Nexus S Android Development] :
Good news, bluetooth is fixed. See above for the cause. I needed some obscure cmdline parameter in the mkbootimg scipt.

So here is v0.9.2 http://d-h.st/o4i (still EXPERIMENTAL)

- Fixed bluetooth.

- Enabled CFQ IO scheduler

I've had a random reboot reported with the smartass governor, so perhaps my frequency scaling tweaks are the cause. I'll have a look at how steve.garon did it.
[Nexus S Android Development] caliban2:
What tweaks? Internal or the ones we can set via nstools? Because I'm not using your settings and it still rebooted.
[Nexus S Android Development] :
Just the tunables, the same ones that you can tweak with NSTools. Actually, I think I have the settings sorted for smartass now, to prevent the min going up to 200 on reboots. I've just rebooted once without a power cable, once with, and min remained at 100 both times. I think there might be a bug in the smartass code, so I'll have a good look at it when I get the time.

What settings do you prefer?

Next thing, I'm going to see about adding morfic's colors, but I'm definitely not releasing that publicly without permission first, and if he says no, then it's not happening.

Oh, and I forgot to mention that I enabled CFQ. It's a good alternative if you're not a fan of deadline or noop. In fact I got amazing IO results with simple kernel 1.20 by terry hau, on CFQ. That's the stock configuration google prefers, and it's hard to imagine they failed to test that properly. In fact, when I did the governor/scheduler combos benchmark, if you add up all the scores, irrespective of the governor, CFQ wins.

EDIT: morfic has given the green light to use his colors. Win!
[Nexus S Android Development] caliban2:
My settings: http://xdaforums.com/showthread.php?p=28591213

Just ignore the stuff this kernel doesn't have.

Bluetooth seems to be fine with 0.9.2. Can't test right now, but at least it enables again.

Well, in that case I'll give cfq a try.
[Nexus S Android Development] :
Regardless of whether people think it's a good idea to release eight versions per day...

Here is v0.9.3: http://d-h.st/CTI (EXPERIMENTAL)

-Added morfic's colours! Yay, love those colours, thanks morfic for kind permission to make public.

-Using steve.garon's smartassv2 values, as these allow 100 min on reboots. (totally baffles the **** out of me, there's probably a good reason, I'll have to stare at the code for a long time before I figure it out.)

The thing we're looking out for now is whether the random reboots are still present. Please let me know and upload your last kmsg if possible. If there's no issues reported for a few days, I'll call that my first proper stable and hit the v1 landmark!
[Nexus S Android Development] tycruickshank:
Just started running slim 4.2 and your latest kernel 0.9.3 and I must say it is quite a nice combo. Everything feels very snappy and quick. I'll report back on battery life and if I get any reboots in a couple days. Cheers!!
[Nexus S Android Development] Icecoldmeat:
But on the normal nexus S we can't see difference in colours, right?
[Nexus S Android Development] y3mita:
Trinity colors? YUMMY me likes it. Thanks man
[Nexus S Android Development] :
Which is normal? It works for amoled, idk for slcd.
[Nexus S Android Development] caliban2:
No voodoo colours for SLCD - we don't need them, our screen is fine as it is. :p
[Nexus S Android Development] Jamalsid:
Don't suppose you have any other mirrors do you? Can you attache the kernel to your posts or it too big?
[Nexus S Android Development] caliban2:
Btw, cfq is really great, adds that little extra performance. No quantum leap of course, the sys was already fast with deadline, but it's there.

min-cpu 100 seems to stay now on reboot, I'm still using my own smartass-values.

With 0.9.3 I got an uptime of 11 hours before flashing latest nightly (including 7 hours standby on charger), now let's see if it survives the next 24 hours.
[Nexus S Android Development] :
My uptime is 12 and a half hours so far...
[Nexus S Android Development] Muvolt:
Air kernel with 65fps?
[Nexus S Android Development] doc_v15:
using marmite 4.3 for 20hrs with MIUI JB 4.1 Rom

Smartass/CFQ, smooth, fast, no reboot, got 2036 Quadrant score!

Thanks bedalus!
[Nexus S Android Development] Imppy:
I got like 40 % android is on 4.3? Is this only a cosmetic issue?
[Nexus S Android Development] :
I'm reasonably sure it's a ROM issue
[Nexus S Android Development] :
I'm pretty sure someone asked if i would add touchwake. I won't, but I'm happy to explain how to do it if you pm
[Nexus S Android Development] migz012788:
Best i/o scheduler combo for smartassv2? I use my ns on gaming :)
[Nexus S Android Development] linuxxp:
Anybody with Slim Beam 2.1 and bedalusKERNEL 4.3 with these problems?
[Nexus S Android Development] gmorel4:
Ohhh okay. It really freaked me out when I went home and saw them in the mirror.
[Nexus S Android Development] JokerAce:
Do

a

fix

permission

in

CWM

---------- Post added at 08:38 PM ---------- Previous post was at 08:38 PM ----------

Nice :cool:
[Nexus S Android Development] linuxxp:
Yes. I answered in other thread. After flashing each kernel I'm using "fix permissions". After last fix permission disappear only first problem. The second problem looks like reboot but in Reboot Logger has no record for reboot and not affect the up time. I think that is ROM issue and I stop write here about it.
[Nexus S Android Development] JokerAce:
Hopefully someone using the same ROM as you can answer you. Most of us are running this kernel just marmitely fine with the ROM we use personally.
[Nexus S Android Development] N3RO815:
With this Kernel Miui Rom will not boot. What’s wrong? I flashed the Kernel and fix permissions. :(
[Nexus S Android Development] xjerlzx:
Its a ROM issue I believe no issues on slim bean 2.0.
[Nexus S Android Development] polobunny:
Someone needs to make an init.d CPU + mods scripts maker. Just an app where you can tick what you want to appear in your init.d and their values.

Like NSTools, except better. Kinda lazy about managing my CPU settings via init.d and a text editor. :p
[Nexus S Android Development] sdhanjal15:
Nothing?
[Nexus S Android Development] FirePoncho86:
I'm not getting the option for deepidle...Im on v4.2
[Nexus S Android Development] Blackcrx:
what rom are you using? i'm having that problem also, using codename 3.3.2

i just reverted back to marmite 4.2 bigmem to see if the android os drain is still there. if not i assume it is the kernel. if so i will try matrix 22.5 for try and isolate the rom

i'm going to miss that extra swag tho. haha
[Nexus S Android Development] polobunny:
No $#@! Sherlock. Read the first post in the thread. Yes, the one with the changelog.
[Nexus S Android Development] eng.stk:
v4.3 is so smooth Bedalus, props ;)

On JellyBro i get a lot of Android OS using battery too. Maybe a ROM+marmite issu, don't know...

Don't know if it happens always, but the phone get's a little warm sometime. With air or matrix, seems like this doesn't happen.

I'm using EOS3 for crespo now, I will try to test if this behaviour happens too.
[Nexus S Android Development] FirePoncho86:
Thank you for your brief and courteous response. I had overlooked the DI was not re-implemented, I read the changelog. I was reading quickly over v4.1, and I saw "Added" 3 times, I assumed DI was there. But really, I do thank you for the sarcasm over my tiny mistake.

---------- Post added at 12:09 PM ---------- Previous post was at 12:07 PM ----------

I'm on CNA 3.3.2 on Marmite 4.2 with Bigmem: we have the same setup lol. I am experiencing ~15% Android os drain, how about you?
[Nexus S Android Development] Blackcrx:
Haha, maybe CNA is the problem. I just loaded marmite 4.2 30mins ago and fully charged the battery to reset the stats. already it shows 10mins of keep awake from Android OS.

Time to try matrix 22.5 to full isolate the issues

funny thing is that no one has reported this issues over at the CNA thread.
[Nexus S Android Development] gummie:
Is there by any means a way to Enable BLN with just flashing file, script or via terminal? Without installing anykind of app just to savor the feature.

Also Im on stock ROM using 4.3 is there also a way to set min-max cpu frequency, governor and i/o scheduler without installing an application to set it on boot? I'm pretty sure that doing it on init.d doesn't do the magic.
[Nexus S Android Development] gmorel4:
I'm running Marmite v4.3 with CNA 3.3.2, and am getting about 19% battery drain from Android OS. 13s Keep awake and CPU total of 16m 4s
[Nexus S Android Development] FirePoncho86:
Report back with matr1x results! Let's get to the bottom of this.

I used to run CNA 3.3.0 with Bedalus 3.5, I had regular (a few percent) android os drain...maybe it's a combo of Marmite and newer CNA?
[Nexus S Android Development] Blackcrx:
will do boss.

maybe someone can install better battery stats app. i have never used it but i heard it helps isolate battery drain

sorry bedalus for hijacking your thread like this
[Nexus S Android Development] asphantix:
No. You can set BLN via script but it will reset with the next boot unless you set it as an init.d script which will be executed when both rom and kernel support init.d. In this case the stock OTA doesn't support init.d.

Just use NSTools.
[Nexus S Android Development] Blackcrx:
bad news marmite and CNA users.

flashed matrix and charged to full. 30mins on time, android os had 5% drain only. where as before i had marmite 4.2 and 4.3 draining from 20%+

so i thought it might have been cache or dalvik related since bedalus said his kernel doesn't wipe it, but 4.3 if i recall wiped didn't it?
[Nexus S Android Development] polobunny:
If you simply knew how many "tiny mistakes" people make daily about the same things. Unsurprisingly, most if not all people questions about kernels are answered in this thread and many other threads if they bother to use the search function or read the first post/latest post from the author.

You'll forgive me hopefully and never forget anymore to properly read the changelogs. ;)
[Nexus S Android Development] Naa Laa:
Are you flashing the correct marmite kernel?

If you are using MIUI JB (08/17) then flash v4.3 or else for MIUI ICS (08/10 or prior) flash v1.5b -- see the OP
[Nexus S Android Development] Blackcrx:
update: an hour of martix and CNA 3.3.2

android os is at 4% battery usage and 30seconds of cpu time as compared to when using marmite 4.2/4.3 it was 20%+ battery usage

seems like android os drain is only present with marmite 4.2 and 4.3 when using CNA 3.3.2

any ideas bedalus?
[Nexus S Android Development] N3RO815:
Yes I use Miui JB and flashed 4.3. After 10 minutes it still shows the Bootlogo.
[Nexus S Android Development] mpjoe2000:
i should be stupid if called this a battery drain
[Nexus S Android Development] Blackcrx:
wow! you barely use your phone. but then again, we all use our phones differently

my phone has been on for a little over 2hours and i have already logged more screen time than you in 13hours. also my wifi isn't enabled all day either.

also in your pics your android os is only showing cpu time where as mine is showing cpu and keep awake time.
[Nexus S Android Development] Muvolt:
I can't believe that so many people care so much about extra battery life without giving attention to performance...
[Nexus S Android Development] Naa Laa:
Are you able to boot MIUI JB without flashing any custom kernel?
[Nexus S Android Development] Blackcrx:
for me it goes hand in hand. if my phone does not last a full day with me i am willing to sacrifice a little performance to make sure i dont have to look for a charger mid day or late day
[Nexus S Android Development] jojoost:
Someone willing to tell me if 3.5 is stable with DI on?
[Nexus S Android Development] sossio18:
CM10 plus marmite 4.3

Good battery life IMHO

Inviato dal mio Nexus S
[Nexus S Android Development] asphantix:
had no reboot with the stock ota rom
[Nexus S Android Development] FirePoncho86:
lol I wont forget, and I still gave you thanks cause you did help!

---------- Post added at 06:18 PM ---------- Previous post was at 06:17 PM ----------

Damn! I love marmite, and I love this kernel too!

I'll stay on marmite, even with the drain, I'll try v4.1 and see if there is android os drain.

---------- Post added at 06:27 PM ---------- Previous post was at 06:18 PM ----------

This is battery with V4.2 and CNA 3.3.2

I have 15 mins of screen on, 3g+data on. Gnow with all its battery sucking services on.
[Nexus S Android Development] :
Sorry. I meant to reply to this earlier. I'm 100% satisfied with the colour I've got now. If you're not happy, use voodoo to adjust RGB
[Nexus S Android Development] gummie:
Any who's using Stock OTA (JRO03E) + Marmite 4.3 here? Did you ever tried to use Antutu Bechmarking Tool? Antutu detects that my CPU uses 100-1200MHz frequency, it also reflects on the overall request, 1200 Points on CPU. But when check the CPU activity on CPU Spy it says the 1200 frequency is not being used at all. I'm totally not sure what is happening, its kinda good by I want definitive explanation. I hope I'm not being swagged by my own device, LOL.
[Nexus S Android Development] JokerAce:
Base on my ROM and kernel combi, I am having 25% for Android OS, CPU time 37 mins 58s at 11h 19m 52s on battery. Using Diagnosis App to detect what keeps running, I found system_server consistently up. Perhaps system_server is definitely always up, someone correct me.
[Nexus S Android Development] :
Thanks for checking back. I'm fully prepared to accept that thalamus was correct, and that there is some issue in the mainline patches that is responsible. I'll look into it.
[Nexus S Android Development] :
Lol that's awesome, swagger has made the kernel pretend it has more GHz than it really does, the cocky little devil...
[Nexus S Android Development] Drizzy xS:
I got the os drain as well Bedalus using 4.3 and cna it was about 20 percent then I switched to matrix and it went right back down again.
[Nexus S Android Development] JokerAce:
LOL I have the same thing as you. And I used an init.d script to set my stuffs. Android Settings>performance>processor shows me 1000 Mhz as max tho :confused::confused:
[Nexus S Android Development] Naa Laa:
Can you please share the new RGB values used in new Morfic colors? Thanks!
[Nexus S Android Development] polobunny:
Shouldn't you be asking that in morfic's thread? :confused:
[Nexus S Android Development] :
Morfic's RGB values won't get you anywhere, because he's changed the calculation for the gamma. (At least I think so. I think I saw a commit of his recently.)
[Nexus S Android Development] gummie:
Funny thing is I didn't even enable that Kernel Feature.

Good thing this is replicated even at Custom ROM, thanks mate.

@bedalus any Idea what is happening? I'm happy to provide logs and stuff just tell me what it is. I cant see any problem with this for now but we still don't have idea what triggers this and if this has a direct impact on the device itself.
[Nexus S Android Development] FirePoncho86:
The weird thing is, even with the Android OS drain, Marmite 4.2 was giving me better battery life than 4.1. I can confirm that 4.1 isn't using as much android os. The CPU total is 3mins for 1h15 mins of screen on for 4.1. The CPU total was 24mins for 15mins of screen on for 4.2.
[Nexus S Android Development] :
EDIT: This procedure MIGHT fix something but it might not, and also, I don't know what that 'something' is.

1) Copy the contents of your SD card to a computer

1) Copy the contents of your SD card to a computer

2) Did you read step 1? It's there twice in case you missed it.

3) Last chance to read step 1

4) In CWM format everything including your SD card

5) Re-install your ROM

6) Re-install marmite_v4.3

7) Copy your photos, download folder, CWM recoveries folder, music, titanium backup folder etc. back to the device

8) Don't copy any old **** you don't need any more

9) Reboot and set all your preferences, restore your apps etc. Avoid restoring crap you don't need

10) Wait and see.

I'll qualify the above procedure with "THIS PROCEDURE WILL NOT WORK AND YOU WILL WASTE A LOT OF TIME"

i.e. It's probably pointless.
[Nexus S Android Development] Naa Laa:
That's what I thought as I tried using the RGB values you have in post 2 of this thread (Try these settings in Voodoo: raise all gamma to 20, then set RGB to 189-185-214) but they don't look anything like the Trinity kernel.

BTW, the closet I could get to his color is by using 135-135-215 and raising all gamma to 20
[Nexus S Android Development] :
AnTuTu is an enjoyable app. (Apart from it killing Deep Idle, Grrr. Nevermind, it won't kill IDLE2 :D)

To me, it looks like it is requesting the maximum available frequency before it begins benchmarking. I think this might be a kernel bug, because it shouldn't be able to override the user policy. But if they've programmed it to be able to do that, that would be quite annoying. I'll see if I can find out which case it is.

EDIT: Looking at AnTuTu > Menu > History

(sic.) shows where the author has a typo in his changelog. I hope he doesn't code like that. :p j/k

But it does seem like there may just be some compatibility issue at the moment... so probably not a kernel problem.
[Nexus S Android Development] FirePoncho86:
Im a coward, step 4 haunts me to this day. I did it once accidentally. Lost a video of my girlfriend in a cat fight :'(

But, for the sake of marmite, I'll try it! But I need some free time....earliest I can do it is monday :(
[Nexus S Android Development] alen1901:
Im on CNA 3.3.1 and bedalus 3.5 kernel. Android OS using few % to max 5%. It got to be some kernel tweaks or your setups.

Sent from SpeedMachine i9023
[Nexus S Android Development] Blackcrx:
I actually reverted back to 3.4.39 for fun to see if I get the same android os drain.
[Nexus S Android Development] FirePoncho86:
I'm kinda getting it now on 4.1...
[Nexus S Android Development] xjerlzx:
V4.3, has a bad battery drain... v4.2 despite having high andrio os %, it was giving me a very decent battery life =[
[Nexus S Android Development] N3RO815:
Yes Miui JB works fine with Stock Kernel or Air Kernel.
[Nexus S Android Development] gummie:
Hmmm I used Antutu before this update and all ROM at JB but its the first that this thing happened. Previous Kernel, CM10 has the right CPU clock.
[Nexus S Android Development] Blackcrx:
3.4.39 runs like a champ. 2mins of CPU time. Not awake time.

Might just keep this kernel around for fun.
[Nexus S Android Development] Naa Laa:
Probably, the file is corrupt. Maybe try to download the kernel again and flash it.

I don't have any issues booting MIUI JB with version 4.3
[Nexus S Android Development] doc_v15:
After ENABLINg swagger in v4.3, I cant open my gallery.

What happened is, I click the gallery icon, it opened up for 1 sec and then suddenly closed. Tried it for many times, but its the same.

Anyone experiencing that too in v4.3 with swagger enabled?

---------- Post added at 12:31 PM ---------- Previous post was at 12:30 PM ----------

Try CFQ/SmartassV2
[Nexus S Android Development] anshumandash:
I am running 4.3 on Black Bean ROM and have no issues of Android OS or any other unusual battery drain.

I tried running the Swagger enable commands on the terminal window of my phone, but got an error "No such directory found". What am I doing wrong? Do I need to have a Linux box for this command to work?
[Nexus S Android Development] hinata75:
I have noticed that when using marmite 4.3 with a stock AOSP JRO03L ROM the CRT fix does not work on my i9023. Has anyone got the same issue?
[Nexus S Android Development] :
My uptime is 53 hours, and my Android OS usage is 30 mins.
[Nexus S Android Development] :
I uploaded a version without the biggermem patch, then uploaded one with it instead. If you got the first one, you may need to redownload
[Nexus S Android Development] :
Can you flash a different kernel and see if the problem goes away?
[Nexus S Android Development] :
Just got some advice from thalamus. If you are having the Android OS thing, get the paid version of system panel app, stick it in monitoring mode for a day. Let's see what processes are actually involved. Report back if you can.
[Nexus S Android Development] xjerlzx:
I used ur method to fix android os and it worked! On v4.2 but 4.3 still drains more battery. So I'm not using it for now....
[Nexus S Android Development] XxSilent22xX:
Awesome kernel bedalus! Thanks for your hard work :)

Sent from my Nexus S
[Nexus S Android Development] kwibis:
Would better battery stats do the same job?
[Nexus S Android Development] JokerAce:
How about diagnosis? http://xdaforums.com/showthread.php?t=1411074
[Nexus S Android Development] gummie:
Just got Air Kernel on Stock JB and it has same result, its definitely Antutu's problem. I got all my eye on them now :cyclops:
[Nexus S Android Development] FirePoncho86:
You formatted /sdcard?

---------- Post added at 09:07 AM ---------- Previous post was at 08:56 AM ----------

I'm on it, I'll report back in a couple of hours.
[Nexus S Android Development] ismailham:
I followed the steps to solve battery drain and it worked :) thx bedalus:o, drain went from 30% to 11%
[Nexus S Android Development] xjerlzx:
Yea formated everything that could be formated
[Nexus S Android Development] Blackcrx:
ah that sucks. I have a lot of music on my phone. its going to take a while to move everything on and off my sd card
[Nexus S Android Development] JokerAce:
Use MTP. :)
[Nexus S Android Development] caliban2:
Still nothing bad to report about 4.3. (Granted, I formatted SD a long time ago, few days after JB got released)

Bedalus, this is getting boring. Can't you post another test-kernel which is a bit buggy? :p ;)
[Nexus S Android Development] linuxxp:
I have a big battery drain on "Android OS". I followed the steps and did a full wipe and installed Slim Beam and marmite_4.3. Then copy only the photos. The result is shown in the pictures:
[Nexus S Android Development] FirePoncho86:
Try Marmite 4.2.

Also, I'm almost done running system panel for a day. I have alot on Android OS usage..but I'm getting more screen on time than usual...strange..

I'll post screenies later
[Nexus S Android Development] :
This is very bad. Try format everything again, use a different ROM, but don't copy anything to your phone.

EDIT: I'm not sure if there might be some issue in moving away from ICS, that something on the SDCard that is holding something used by the OS is incompatible, and is causing extra access... I can't really imagine exactly. But a format should get rid of it.

However, if the problem comes back, it might indicate that there is in fact some other issue which occurs after a certain amount of uptime: a maintenance process gone haywire perhaps. In this case, the info from System Panel will be useful. I've been running it all day too, although I have not had this particular problem, and I can see no bad behaviour from any process.
[Nexus S Android Development] gabling23:
One question: if I have got an init.d script that set the governor and the scheduler and I use set cpu to change governor or scheduler, which one will be the one that really set the governor or the scheduler?

Sent with Tapatalk 2
[Nexus S Android Development] :
Init.d scripts are executed quite early in the boot process I think, then an app will be executed later on once the OS is up... I think setCPU will have the final say.