yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] R-TEAM:
Hi,

nice kernel - as always ;)

Runs smooth and stable by now.

But -*sniff*- no 1100Mhz step ..........

Thanks anyway for an amazing kernel (and i hope still for an 1100Mhz step :P )

Regards

R-TEAM
[Nexus S Android Development] naneek:
Any chance you can fix the 0mb bug in v15.5 because deep idle fixes my battery drain issues and on v16 I have them again
[Nexus S Android Development] qtwrk:
you can get to 1.1 Ghz by set LiveOC to 110%;)
[Nexus S Android Development] SA-07:
Hahahaha yep ;) It's liveoc time
[Nexus S Android Development] migz012788:
Good day. How can i do live oc?? Is there any apps for changing live oc??
[Nexus S Android Development] maniac2403:
You can use NSTools from the market for LiveOC.
[Nexus S Android Development] SA-07:
Yep! Setcpu works for voltages as well
[Nexus S Android Development] b1337:
that does not remove the flicker for me, its all good i will live :)
[Nexus S Android Development] y3mita:
Flicker will always b there!
[Nexus S Android Development] nexusphone:
@mathkid95

Did you remove the cosmetic 100% battery tweak?
[Nexus S Android Development] b1337:
Damn u flicker!! :p
[Nexus S Android Development] android_nexus:
Many people miss not having Deep Idle. But the dev does his own thing. We can be thankful for the sharing. That's the lot.
[Nexus S Android Development] jcolinzheng:
mathkid95: Please kindly explain how cpuidle works, why you include it, or point us to its documentation, ideally in the original post. In particular, I'd like to learn why it may be favorable to Deep Idle.

Thanks!
[Nexus S Android Development] R-TEAM:
Hi,

arggg .... ... ;)

As i have (i thinked post #2305 here) explained, i need the 1100Mhz step NOT to get 1100Mhz :)

I need it to overclock more by 120% LiveOC, but the next step (1000 -> 1200) is to big and give me an to high endFreq (1440Mhz with LiveOC 120% )

An step from 1100Mhz give me then 1320Mhz and would be ideal ;)

Regards

R-TEAM
[Nexus S Android Development] deani77:
Nice battery performance using CM9 Kang by Fuzz and V16 kernel...

Sent from my CM9 Nexus S
[Nexus S Android Development] FoulDroid:
Same here ... set to 96% but charging 100% :confused:
[Nexus S Android Development] android_nexus:
Just cosmetic tweak, be assured ;)
[Nexus S Android Development] :
Anyone interested in the logic behind deep idle's removal, it is because it has been deprecated by arm's own CPU idle. Visit my battery thread, fourth post, read the arm pdf

For kernel benchmarks and more, see HERE
[Nexus S Android Development] hedpe:
hi mathkid, a couple things:

The link to source is broken on the main page, but I found it through your github profile.

When you publish releases (e.g., v16.0), could you also post the git hash that corresponds to the release, or tag it in github? I tried looking at your commit logs, but couldn't find any notes on version releases.

You might be aware of this (as I'm just snagging your dev code), but I am getting an error building the kernel configured with the herring_defconfig config file, and using commit 4bcb8f149401364f19fa36c78cde0b46763ce6d0.

I am getting an error related to an implicit declaration:

fs/ext4/page-io.c: In function 'ext4_end_io_nolock':
fs/ext4/page-io.c:121: warning: implicit declaration of function 'inode_dio_done'
fs/ext4/page-io.c: At top level:
fs/ext4/page-io.c:130: error: expected identifier or '(' before 'return'
fs/ext4/page-io.c:131: error: expected identifier or '(' before '}' token

This seems to be related to your newest commit.
[Nexus S Android Development] Flukzr:
I read the pdf, didn't really understand most of it. If someone could put it in layman's terms so anyone not familliar with cpu arhitecture or kernels could understand.

I mean does arm's cpuidle do a better job than deepidle, at this point? Does it gave any advantages to the end-user, or is it simply ARM's take on power management issue?
[Nexus S Android Development] :
Jury still out on whether CPU idle or deep idle saves power. Check my battery thread in a few days.

For kernel benchmarks and more, see here: http://goo.gl/mpeHI
[Nexus S Android Development] chiefy009:
Hi I am moving over to Nexus S tomorrow and I wondered can I flash this kernel with Miui V4 rom ?
[Nexus S Android Development] maniac2403:
I don't see why not.
[Nexus S Android Development] y3mita:
Yep, I've read people using this kernel with Miui... works fine.
[Nexus S Android Development] angiest:
I've been using v16 with CM9 v2 for a day or two, and so far absolutely no green flash. As far as Voodoo, I am running with whatever the defaults are.
[Nexus S Android Development] SA-07:
I didn't push a parenthesis change and I just fixed it myself.

Go into the file try to investigate yourself. Its a simple parenthesis removal
[Nexus S Android Development] SA-07:
When I get home I'll fix the source link
[Nexus S Android Development] sperelli:
+1 for the whole statement.
[Nexus S Android Development] qtwrk:
what is cosmetic tweak ? is there possible to make it back to limited charge ?:confused:

by the way , i feel without deep idle , battery dies quicker.

i didn't test it on purpose , yesterday after flashed 16.0 CFS , one night about 7 hours , took 6%, 7% , and back on 15.5 CFS time , it only took 2%
[Nexus S Android Development] tchaari:
Really confusing deep idle. Sometimes members state that it is depricated, useless and the source of many issues. Others prove that it really saves power. The discussion about deep idle is becoming hot between bedalus (the benchmarks man) and Ezekeel (the developer of deep idle) :D

http://xdaforums.com/showthread.php?t=1478406&page=6

Very interesting to read ;)
[Nexus S Android Development] nodstuff:
Deep idle isn't utilised when your phone is idle, its in deep sleep then.

Deep idle being removed had nothing to do with your results unless you were using GPS, Bluetooth or music.

So I'm afraid your test is wrong.

Also cosmetic means it just LOOKS like it is at 100%, whatever you set blx to it will show 100% in UI bit will in reality be what you set it to.
[Nexus S Android Development] b1337:
getting pretty tired of telling people this myself
[Nexus S Android Development] android_nexus:
Please explain it particularly
[Nexus S Android Development] qtwrk:
I always check my phone before I close my eyes, all same except background apps, I will keep record tonight

Then if it only make it looks like 100%, then what is point of it?

Sent from Google Nexus S using xda premium while eating Ice Cream Sandwich
[Nexus S Android Development] qtwrk:
Well, once upon the time, there is somebody who tells you something like this

And not everyone gets latest information about everything

Sent from Google Nexus S using xda premium while eating Ice Cream Sandwich
[Nexus S Android Development] s1l3nt:
just came by to say that this kernel is awesome i always use this one no matter what rom i'm using
[Nexus S Android Development] SA-07:
Thanks :D
[Nexus S Android Development] cpom1:
what settings you using mathkid? im loving this kernel man. its just too awesome. not one reboot! :D
[Nexus S Android Development] SA-07:
I'm using 1300/400 ondemand... deadline io sched
[Nexus S Android Development] bendirkss:
mathkid what rom you using?
[Nexus S Android Development] chalan30:
16 bfs on aokp milestone 3. not too shabby...

bleh meant to post in ns4G...
[Nexus S Android Development] mainfram3:
I flashed v16.0 last night with a full battery. Without tunning any settings I found my battery at 22% this morning :(

Going back to 15.5 or 14.5 where I got the best battery life yet.
[Nexus S Android Development] AsianXL:
What kind of UV settings are you guys using for v16?
[Nexus S Android Development] sperelli:
what's the latest hopefully last verdict?
[Nexus S Android Development] android_nexus:
There is no doubt that deep idle works for saving battery? Hmm... I've heard that Matr1x' deep idle very stable unlike the other kernels. I think re-implementing that sounds really good.
[Nexus S Android Development] :
I'm afraid we are still debating it. More battery tests coming soon.

For kernel benchmarks and more, see here: http://goo.gl/mpeHI
[Nexus S Android Development] qtwrk:
+1

Sent from Google Nexus S using xda premium while eating Ice Cream Sandwich
[Nexus S Android Development] sperelli:
in the meanwhile i'll go back to 14.5.

on 16.0 is good, but 14.5 was better at least for me..
[Nexus S Android Development] nodstuff:
Did you even read my post?

DEEP IDLE ISN'T UTILISED WHEN YOUR PHONE IS IDLE.

Removal of deep idle is NOT the cause of your battery drain.

No matter what you think, it is not the cause.

It only saves battery when you play music, use GPS or Bluetooth.

NOT when your phone is idle overnight.

This has been said millions of times yet people still think it saves power when the phone is idle

It doesn't, the phone is in deep sleep then which is more power saving than deep idle.

Deep idle has no effect on your battery when your phone is on your locker overnight doing nothing unless Bluetooth streaming is active, GPS is active or if you are listening to music.

END. OF. STORY.
[Nexus S Android Development] darth7:
IM having better battery life than ever. Thanks.

Enviado desde mi Ice Cream Nexus Sandwich usando Tapatalk
[Nexus S Android Development] qtwrk:
http://xdaforums.com/showthread.php?p=18299324

My ****y English didn't see anything related to music, Bluetooth or GPS or something

Could you point me out where or how did you find that conclusion?

Sent from Google Nexus S using xda premium while eating Ice Cream Sandwich
[Nexus S Android Development] Harbb:
What nodstuff said is exactly correct. It is all implicitly stated by Ezekeel in the Deep Idle thread. He says that SLEEP is implemented (and used), and he purposely used audio playback to benchmark (it's a task that the CPU can cache, stop for a moment and then continue with no degradation of the task at hand). If you are losing lots of battery life while the phone is not being used, there is something on your phone preventing the SLEEP state from coming on or staying on. This effectively has nothing to do with deep idle or cpuidle.
[Nexus S Android Development] centroi:
what do you think??? let's try??

http://xdaforums.com/showthread.php?t=1475280
[Nexus S Android Development] xontax:
@sperelli sorry if i'm rude but aren't you emboid it at some point with your benchmarkings? I don't think you can compare ROMs this way, but this is just me :D
[Nexus S Android Development] :
did you mean me? I can't understand your spelling. Ask again please

For kernel benchmarks and more, see HERE
[Nexus S Android Development] b1337:
Try what?

---------- Post added at 06:02 PM ---------- Previous post was at 05:57 PM ----------

youve heard wrong quit posting this, youve been told many times now, if you cant figure it out work on your english!!
[Nexus S Android Development] centroi:
@b1337 , 4.0.4

---------- Post added at 05:36 PM ---------- Previous post was at 05:31 PM ----------

tried and working, lets see tonight
[Nexus S Android Development] 93ae8074:
Let us know about CPU time consumption by Android OS. ;)
[Nexus S Android Development] centroi:
no problem, tomorrow I'll put screenshot of that, but, lot of people in original post, experimented better battery life

ahm, maybe in my phone there's not the best test base and given results that will not be especially goods, I'm restoring all my phone like before of rom change, about 250 apps, and lot of background running apps and other mods, but, to compare for me is better, and know if this change affects
[Nexus S Android Development] centroi:
coome back to 4.0.3, 4.0.4 works ok, notably faster than 4.0.3 and lower battery usage, os android process takes minimum battery usage, but, screeenlock does not work, search button neither, trying apps for lockscreen in market broke home button function, need to wipe, and no nandroid was done before that, restore the 4.0.3 waiting for issues been solved
[Nexus S Android Development] caliban2:
You're going to wait a long time for screenlock and search button being fixed - they aren't broken, they're working fine.
[Nexus S Android Development] 93ae8074:
Really? Mmm, anyway 4.0.5 is gonna hit streets in march. :)
[Nexus S Android Development] centroi:
?¿?¿ hoping for it
[Nexus S Android Development] SA-07:
Can't wait :)
[Nexus S Android Development] android_nexus:
Ezekeel is contesting with bedalus. We cannot hastily conclude

http://xdaforums.com/showthread.php?t=1478406&page=8
[Nexus S Android Development] SA-07:
Can someone make a quick boot.img of v16.0 cfs/bfs for me? Thanks!
[Nexus S Android Development] Serious_Beans:
Any plans to add KSM? used your kernel today, had a pretty decent day with battery life, so far so good, thanks!
[Nexus S Android Development] nexusphone:
init.d support, also flashable :)
[Nexus S Android Development] SA-07:
Thanks!!!! :)
[Nexus S Android Development] Po0yAn:
It would be nice to have a cold color version. I used to use matr1x first but after v13 and seeing no progress in fixing the green flicker I moved on to Steve's kernel with cold color. on ics Voodoo is not as good as it used to be IMO, just change the default settings for a little bit,and the green screen is there.

Mathkid, Any plans of adding cold colors to your kernel?

neXus S i9020T - AOSP+ - SG Kernel - 100/1320 MHz
[Nexus S Android Development] sspikey:
when you say

Do I raise these in the "ARM" voltage or "INT" voltage under NS tools?
[Nexus S Android Development] gouthamsn:
Liveoc Min ferquency

Hi All,

When I try to use liveoc my phone hangs.

I have noticed the following:

for 105 - min needs to be 200Mhx

for 110 - min needs to be 400Mhz

The int voltage I am using for 400 is 1000mV and ARM voltage of 975.

As the stock int voltage for 100Mhz is 1000mV and ARM for 100Mhz is 950mV, hence it would only mean a little more battery drain than being on stock, which is fine by me.

But just wanted to know if setting the min to 400Mhz, would it cause a problem? Reduce life of my phone etc etc? I do know there is a deep sleep state. Would this compensate the min being set to 400Mhz? What exactly happens to the clock speed on Deep Sleep.

Thanks for any info that can be provided.
[Nexus S Android Development] mindwalkr:
Installed v16 yesterday on my Nexus S i9023

So far the battery life seems to be worse than stock. Using ondemand max 1000000 min 100000.. everything stock as per Matrix's release settings.. didn't change anything after flashing the kernel.

Wasn't the cpu idle supposed to help with music playing with screen off since it's now replacing the deprecated deep idle ? Well, using Battery Monitor Widget I go from 70-80 mA (stock kernel) to 120-130 mA (Matrix) when playing music while commuting.

Still a few hours with the kernel so I'm also keeping an eye on CPU Spy to see what frequencies are being used and whether the phone goes to sleep or not...
[Nexus S Android Development] Harbb:
I got some weird results with this new kernel, thus cpuidle. I'm testing it again tonight to understand whether it was my fault or there is something bad going on with it.
[Nexus S Android Development] tchaari:
What type of results are you having? I am continously monitoring your spreadsheet ;)
[Nexus S Android Development] jabbeboy:
Anyone that has the same issue i have?? It takes about 3minutes to boot up my phone... first time i hangs at the google logo for about 2 minutes. Than it reboots and takes 1 minute
[Nexus S Android Development] DarkhShadow:
You must have something else on the phone or you settings are bad, boots up within 30-60 seconds for me

Sent from my ice cream powered Nexus S
[Nexus S Android Development] deani77:
Was on CM9 and Matr1x v16 kernel... Working great...

Sent from my CM9 Nexus S
[Nexus S Android Development] spupuz:
which governor? which scheduler? live oc?
[Nexus S Android Development] deani77:
Governor: Lulzactive (tweak for balance)... scheduler: deadline and no liveOC

Sent from my CM9 Nexus S
[Nexus S Android Development] caliban2:
Had some troubles with v16:

- system would be really slow sometimes, as if CPU was maxed out.

- freezes on bootanim when turning the phone on (-> batt-pull)

Did a full wipe because of this, but today it happened again. I always restore user-apps via titanium and never had any troubles with it on glados-kernel. So now I simply switched back to glados 2.9 and 3 reboots without freezing - sys should be fine then.

Matr1x: smartassv2, noop

Glados: lazy, deadline, didle on, max-freq on

Both kernels: cfs, touchwake on, bln on, rest as is.

So, if with glados these bugs will stay away, question with matr1x will be: kernel itself? Gov? Scheduler?

Anyone getting this as well or having an idea? :)
[Nexus S Android Development] Zivonche:
Mathkid

I just learn today the importance of the right pairing between Governer and Schaduler.

i search this cause i had a huge lag in "incoming call" screen on.

since i am using your Matrix Kernel i would like you to advice me with the best combintion for lag free and smothness

i am using LiveOC 120% 200-1200

Thank you very much
[Nexus S Android Development] jabbeboy:
Okeey. Weird. ,, Maybe i will reflash the kernel and se if the problem still is there..

This is the most battery efficient kernel to ICS right?
[Nexus S Android Development] :
BREAKING NEWS!!! mathkid95 name-dropped over power saving kernel in this article about my battery benchmarks:

http://www.xda-developers.com/andro...gs-about-surprising-conclusions/#commentbelow

Although, a question mark still hangs over my work. Please read Ezekeel's arguments my the thread for a more complete picture.
[Nexus S Android Development] tchaari:
The answer is in this good benchmark :

http://xdaforums.com/showthread.php?p=22127033
[Nexus S Android Development] Zivonche:
First :

It says MATHKID prefer ondemand governer but not what schaduler he prefer

Second:

it doesnt say for what propose he choose this, could be for battery and not for performance or other reason

thats why i am asking here
[Nexus S Android Development] zalho:
wifi problem

Hi.

I've installed the kernel v16.0 CFS and now i can't turn on my Wifi??

What should i do?
[Nexus S Android Development] darth7:
same here, take forever to boot.

Enviado desde mi Ice Cream Nexus Sandwich usando Tapatalk
[Nexus S Android Development] :
mathkid95 told me personally that he prefers this governor.

Check my work here:

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

Shows that a good match for ondemand is noop or deadline
[Nexus S Android Development] angiest:
Turn off Wifi and reboot. If it won't turn on after that, reflash the kernel.
[Nexus S Android Development] grotesque02:
I downgrade kernel from 16 to 14.5, but I see now nova launcher and the "telephone network" is slow, and the app like extended controls is slow to enable/disable wifi, mute/ring/vibrate, etc.

I clean dalvik cache before this downgrade, what I have to do?
[Nexus S Android Development] cheech87:
I'd like to report a bug with bln. Not 100% sure if this is related to the bln implementation in your kernel, so let me know if I should post this elsewhere.

With nstools service DEselected, and with no current notifications, if > 1 emails come in at once (in the email app, not gmail), bln fails to light up. When exactly one email comes in, it works fine.

Also what I find is it does not work all the time with nstools service ON. in particular, if it is on, and you reboot, then I get the same behavior as above. For some reason, toggling nstools service to ON fixes the problem.

This problem existed before the existence of the nstools service feature. rom: codename android 1.3.2, kernel v16.0 bfs.

Any insight would be appreciated!
[Nexus S Android Development] AeroEchelon:
Currently I am running Cyanogenmod 9 v2.1 and was happy to find that DEEP IDLE was built into their stock kernel and compatible with the ROM. I was reporting DEEP IDLE TOP = OFF stats with that kernel.

However, after flashing the Matr1x kernel v15.0 I can at best only get TOP=ON results ... is there any patch to get TOP = OFF stats showing again?

Thanks!
[Nexus S Android Development] bigmem:
running the AndroidMe v1.2.3 ICS ROM and v16 has by far given me the best batery life but i get random reboots, not had this prom with other kernals.

tried the varibles of changeing io and govners round but same issue :(

even went back and did full wipe data and cash wipe and fresh install of ROM and kernel, even tried different ROM's with v16 but still same issue, please help
[Nexus S Android Development] SA-07:
Raise voltages by +15 across the board
[Nexus S Android Development] SA-07:
I need someone to make me another boot.img with init.d

Pm me email id if you can
[Nexus S Android Development] bigmem:
ok gonna sound like a noob but todate not played around with the cpu clocking or volts. so on the nstools what am i increasing exactly theres a tick in default voltages,

thanks
[Nexus S Android Development] SA-07:
Arm voltages. Increase all of them by 15
[Nexus S Android Development] bigmem:
i went and increast the int volts as well, will that have an adverse effect?
[Nexus S Android Development] SA-07:
Probably not. But if you get reboots reduce all the ints back to stock matrix voltages
[Nexus S Android Development] bigmem:
thanks alot :) yours is the first kernel that doesnt have the andriod os staying awake and kiling battery with CPU uptime
[Nexus S Android Development] :
I thought Deep Idle =/= CPU idle? From my experiences, deep idle has had more effect on battery savings than CPU idle...
[Nexus S Android Development] caliban2:
So nobody having these issues then, hm? http://xdaforums.com/showthread.php?p=22312011

I've been running glados since and they didn't occur again. Mind you, this is the same system, only kernels switched.

Batt-life is a bit worse though, so I'll flash back matr1x and see which of the different settings causes the instabilities.

Edit:

"A bit worse" means it's just not as good. Not "CPU idle yay, didle nay"! :p Rather caused by different gov or kernel version (3.0.8 vs 3.0.19).
[Nexus S Android Development] jabbeboy:
Tried to wipe dalvik cache and then reflash the kernel, but the slooow reboot continues to stay there, even the google logo boot rebooten ones before it accually came to the boot animation...

Not good, thinkin to go back to glados 2.9 again, nothing wrong with the battery, just thinks glados is a little better
[Nexus S Android Development] caliban2:
How about wiping \cache as well?
[Nexus S Android Development] darth7:
done that, still the same.

Enviado desde mi Ice Cream Nexus Sandwich usando Tapatalk
[Nexus S Android Development] caliban2:
Might be connected to my boot freezes.

Flashed matr1x a few hours ago and while I didn't notice any slowdowns, I just did a manual reboot: freeze on bootanim followed by a self reboot.

Something's wrong... ^^

Fixed permissions this time, so it's not that.
[Nexus S Android Development] jabbeboy:
Yes, wiped both dalvik cache and cache, non fixin the problem.

Also i dont really like the cpuidle, now im at 20% and have 1 day , 2 hours, but then i had deep idle it was a max 1 day 12 hours, and dont think i can get any better than that... So im gonna try flashin in 14.5 cfs insteed of the 16.0
[Nexus S Android Development] centroi:
somebody is using lazy governor??

I experimented the best battery life with lazy (and sio), 3% at 8h (during night) trying diferents combos: ondemand- deadline 10% 1h (200-800) / lulzactive - sio 8% 7h / smartassV2 -sio 13% 7h / , and tonight is turn for conservative-noop

lazy is a little bit slow, I prefer lulzactive

all at v16.0 without using the phone

and you?
[Nexus S Android Development] caliban2:
Smartassv2 with noop here. Just a tad better for batt than glados with lazy, deadline, didle and max-freq. Also it gives me better performance than lulz.

I'd really like to see how v16 does with didle. ^^

But if you read my previous posts you'll see I have some minor stability problems...
[Nexus S Android Development] SA-07:
Have any of you people who are complaining even read the FAQ?
[Nexus S Android Development] caliban2:
Yes, and I found it boring. :p nothing in there I didn't know already nor applying to my problem. So why are you asking? And is this all you got as an answer?