yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] got2best:
Can any 1 please help! I am getting so tired of this! .. is this normal battery drain because this is insane.. I did bat wipe.. this is the 5th charge cycle.. and note I was listening to music through Bluetooth headphones.. but I still fell this drain is insane.. I am running latest test kernal.. lazy governor with Max frequency on.. 400-1000 MHz nscolleb and I am in a i9023.. please help :(
[Nexus S Android Development] polobunny:
Are you sure deep idle is enabled and running fine (cam bug)? You can check the stats with NSTools.
[Nexus S Android Development] got2best:
Yep its enabled. And I did the cam thing everytime I restart my phone.. and I checked stats and it showed its working.. see picture
[Nexus S Android Development] franciscofranco:
Well you are using bluetooth on, listening to music, with data enabled and screen on for a good part of the time, what did you expect?
[Nexus S Android Development] polobunny:
What programs appear in the battery stats? It's not impossible something is sucking the juice.

Edit: Yeah just noticed the screen. It's been on for a whole hour out of 2...
[Nexus S Android Development] got2best:
That's what I was wondering.. if that's normal drain just for listening to music over Bluetooth.. and the app that's in battery drain is the music app.. so this battery loss is normal?
[Nexus S Android Development] coloxim:
Wow...only with UV? For is impossible this results ..

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] polobunny:
Hard to tell, you've had the display taking 59% of the battery there...

Removing the battery calibration error (the sudden drop when you rebooted) and calculating without the screen on for so long during the time you were listening to music, your line would look a bit like the red line. Don't look at the meters on the left, these are flawed since I cut the image.

That's around a 12% drop for your music listening, which seems pretty on par with what you'd expect from a kernel at stock volts, using bluetooth.

Only UV, ondemand 98% 15000, but lazy gives me very similar results too. deepidle off by the way.
[Nexus S Android Development] Heretic Infidel:
I just did the simpelest test to man that doesn't require hours of patience.

I used battery monitor widget hisory to look at the mA consumed while in sleep mode. Just turned on deep idle, waited 1 hour with it doing nothing, the turned deep idle off and waited 1 hour.

The facts

Deep Idle = ON

Usage : 33 - 55 mA

Deep Idle = OFF

Usage : 18 - 20 mA

This is with the 16/11 rom, CM 7.1, and KF1 radio.

Battery temp is a constant 22 C.

The conclusion is simple.
[Nexus S Android Development] coloxim:
I use o demand like you...you haven't freeze?

do you UV gpu too?

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] polobunny:
No I didn't get any freeze with these settings so far. I was amazed to see how much 400MHz could be lowered. I was previously using 400MHz min and 1000MHz max but I've recently switched to 200MHz min to save a bit more. Seems to work out well.

I haven't touched INT voltages, only ARM so far. I'll try touching INT later, when I think of a good way of testing out the stability.

I haven't tried to LiveOC either, lots of stuff to do but so little time. :p
[Nexus S Android Development] jhalmeida:
Hum got 2 restarts with 16th test kernel. Since mornig ok but (do not know if this is the problem) with battery below 20 % got two restarts!
[Nexus S Android Development] ro_explorer:
This is my feedback with the latest test, deep idle enabled

Actually you can see when I flashed the latest test :) ... The over night drain it's with the first Nov 16 test with the didle disabled.

Sent from my green robot ...
[Nexus S Android Development] Cybergr:
Ok..here is my report and thoughts regarding 16.11.11 test kernel.

SETUP

Rom : Oxygen 2.3.2

Kernel : Franco`s 16.11.11

Radio : I9023XXKF1

UV - OV : Defaults Voltages from Kernel

Deep idle - Deep Sleep : On - Defaults by kernel

BLN : Yes 10000 ms

Screenoff_max freq : off

Live OC : No

Governor : Lazy

Frequencies : Min 400 - Max 1000

Wifi : On most of the time

Data : off

2g/3g : Only 2g

Battery drain seems equal but better of 13.11.11 stable kernel.I went to sleep at 04:00 and wake up at 11:30, battery went down from 73% to 68%.

From 11:30 till ~19:00 o`clock that i plugged my Nexus S to the charger i stress my device to the max with some heavy usage including downloading and installing a lot of apps, some gaming (and tegra gaming),xda tapatalk app, music,calls/voip calls and normal messaging.

When gaming though i noticed a really heavy battery draining but i suppose that is normal cause all off those games are battery drainers, cause of their really heavy 3d graphics environment. ( Backbreaker THD, Backbreaker 2, Shadowgun, Fruit Ninja THD and Samurai II:Vegeance )

Performance as always excellent.

Signal strength pretty good.

Radio dumps : 1 ( had to enter pin code again )

Freezes : 1 had to pull battery out cause touch screen was in -responsive at lock screen.Never happened again, maybe was related of the fact that i am on a fresh ROM install and i still need to setup all the apps-games that i need.

Hope i didn`t forgot to mention anything but if i done so i will report it later.

All in all i have to say that we are near to the perfection!! ;)
[Nexus S Android Development] franciscofranco:
Stable release is up. It contains every deep_idle patches up to this moment.
[Nexus S Android Development] ro_explorer:
How about the min-free settings ? still locked ? :P

I'm gonna try it anyway :). And the night is just beginning for me, I'll report the drain while doing nothing.
[Nexus S Android Development] kalinusa:
FOR THOSE WHO DO NOT BELIEVE HERE ARE THE SCREEN SHOTS!

!!! this is with the Test kernel from a few hours ago but I will test with the latest and I have the feeling it will be the same. This started happening few releases ago.

IT IS NOT THE WIFI

How come the Ezekeel kernel is working fine.

There is something iffy about this and nobody is paying attention

Wifi is a University AP

OPEN (no WEP/WAP etc)

I am right in front of the AP.

Notice how the Franco kernel does not enter Deep Idle when the WiFi is ON. Again, this is only on the university Wifi, at home or on 3G is fine.

The Ezekeel kernel has NO problem with either WiFi.
[Nexus S Android Development] franciscofranco:
**** I forgot, sorry. I'll unlock them next time I release it. Btw, can't you just enforce your minfree settings via terminal with root permission?
[Nexus S Android Development] franciscofranco:
@kalinusa

Can you try with steve.garon kernel please?
[Nexus S Android Development] skinniezinho:
Guess the network problems in the stable kernels may be due to some conflicts with some roms/configs.

I guess mine stopped with 13Nov kernel, but I applied it in 3 different roms (MIUI Stock, MIUI 2.5.2 by KelLMSKing , Oxygen).

Only remember having network problems with KelLMSKing, not only two network drops but people telling me that they sent sms (and I didn't received it).

For now and for test purposes I will only use stock MIUI.

Flashed the 17Nov kernel
[Nexus S Android Development] akshayf:
Everyone is not a franco like you, franco.... :-)
[Nexus S Android Development] ro_explorer:
At first I got "permission denied" and I saw that /sys/module/lowmemorykiller/parameters/minfree was read-only even for root.

After changing the permissions for that file to rw-r-r I was able to set whatever minfree I like :) ... So, as long as I can get access to that file in a way or another, from my point of view you can leave the settings "locked" :)

The nov 17th kernel is working OK after first few minutes :) ... I'll see the behavior over night.
[Nexus S Android Development] kalinusa:
Here it is. I tried steve.garon's latest experimental kernel

I guess SpyCPU does not show the bars but the times are correct.

Basically it tells me no DEEP IDLE

Franco, do you have any ideas?

I have tried CM latest nightly, and then MIUI roms.
[Nexus S Android Development] ro_explorer:
Deep sleep and deep idle are 2 completely separated things.
[Nexus S Android Development] Maximilian Mary:
You won't get deep idle stats by looking at cpu spy. Deep idle != deep sleep.
[Nexus S Android Development] Ezekeel:
We should print that on a shirt and give them out for free. Maybe then people will understand. ;)
[Nexus S Android Development] kalinusa:
Ok I actually understand.

Then Ezekeel's kernel gives me DEEP SLEEP on Wifi ON, while Franco does not.

So what is the deal with the Deep Sleep???

Steve.garon also NO deep sleep with Wifi On.

As for Deep Idle, do I check this through the NSTools??? cause I get there

Idle = xxxxx some amount

Deep idle top/on off = ZERO
[Nexus S Android Development] frenccw:
Ughhh damn you franco for making me flash kernels almost everyday. Can't help this addiction!
[Nexus S Android Development] casca:
So with deep idle enabled, it consumes more energy than it saves lol.

Just what myself and others reported some posts back.

Well, like I've said, I've made a fresh install once again with Oxygen 2.3.2 and I wont touch the kernel from the actual rom (made by Adamg). So far, I've got my normal battery drain back and tomorrow I'll probably make the end of the day still with battery left like I usually did before all of the deep-idle stress testing and flashing.

I'll keep following the thread for news and I'll help in what I can, but I won't flash anything without making "another" nandroid backup first :)

Let's keep doing the brainstorm :D something will come out for sure.
[Nexus S Android Development] ro_explorer:
What's going o here is not a brainstorm :) .. here is an open discussion: users are reporting issues, developers are trying to understand what users are saying and after that they are trying to implement that :) ... the brainstorm is between the developers I guess :) ....
[Nexus S Android Development] casca:
Sorry, but not true mate! :p

We, simple users are also doing some brainstorming, are we not?

Although in a simple way, but it's the only one we can... flashing,experiencing,logging,debating what happened, if it should happen and why it happened! :p

when the developers read our posts, they come up with analysis and their brainstorming only occurs after ours :D
[Nexus S Android Development] franciscofranco:
Me and steve.garon are using PM:FAST as the default power management "engine", which makes wifi to consume a little extra energy but the signal is much stronger. PM:MAX is the oposite. I don't know if Ezekeel is using MAX or FAST, but I'm pretty sure that's the explanation. And like it's been said before Deep Sleep is NOT Deep Idle.
[Nexus S Android Development] ro_explorer:
Ok then .. I'll go your way.

Will report i the morning with the battery results and in the afternoon with the "daily average usage". We can brainstorm after that :) ...

Meanwhile .. I'll go do some brainstorming of my own, by using a pillow :)
[Nexus S Android Development] kalinusa:
Hey Ezekeel, just wanted to let you know that whatever you changed from 1.7 Test to 1.7 Final it made it behave exactly like the problem I am describing with the Franco's kernel

Wifi ON (only at the univeristy) = NO DEEP SLEEP

Now I get the same behaviour as his. 100mhz usage. No deep sleep :(((

***CORRECTION DEEP SLEEP IS GONE IN BOTH STATES, wifi=on or off.

Sooo I have not idea what to make out of this???

As for Deep Idle, NStools says ON but the Stat has numbers only under IDLE...deep idle top = ZERO ZERO

Can anybody explain how can I see the stats for Deep Idle?
[Nexus S Android Development] franciscofranco:
It's not a problem, read my reply few posts back.
[Nexus S Android Development] qtwrk:
13 NOV version , i feel battery is dying much quicker ...

hope 17 NOV has improved this

also , could you please provided older version in that ftp host? because sometimes ...you know , new version has this or that problem , just in case in need to flash back older version . thanks
[Nexus S Android Development] kalinusa:
Thanks for the good reply.

Several questions:

1. Why does it happen only on my University wifi. Do different APs respond differently to the FAST vs MAX?

2. So if CPU Spy reports 100Mhz constantly, this will be sliiiiighly more power than Deep Sleep? I could swear that in Deep Sleep I get much better power drain.

3. How do I check the Deep Idle stat since CPU Spy is not useful?

thank you. your reply has been very useful.
[Nexus S Android Development] some_random:
have you opened and closed the camera?

to make deep idle actually work you will most likely need to open and close the camera because talk opens it when your phone boots and it doesn't close it properly so it causes it to stay out of deep idle...

let me know how it goes when you open and close your camera and then turn your phones screen off and leave it for a couple of minutes WITHOUT CHARGE because a charger will also prevent deep idle
[Nexus S Android Development] Cybergr:
Use NStools to check DeepIdle stats!
[Nexus S Android Development] kalinusa:
Thanks mate!! the camera thing did it. Finally I am getting Deep Idle other than ZERO.

Sooo this is like a known bug with android and the kernel cannot fix it. I guess this means I need to open the camera every time I reboot?
[Nexus S Android Development] franciscofranco:
No, I dont suport old versions.
[Nexus S Android Development] some_random:
correct.. you can fix it by flashing the google talk version without video chat.. which if you want to do I can find you the link otherwise yea you just have to open camera every time you reboot the phone... my thanks button awaits you :P
[Nexus S Android Development] laidick:
should i enable deep-idle?

Hi,

Providing that I don't play music while screen off, I don't use bluetooth devices, is it still recommended to enable deep idle?

does it also benefit to any background jobs like gmail sync, rss news feeds, or whatsapp etc...?

Thanks.
[Nexus S Android Development] some_random:
it shouldn't be harmful but I mean if your not going to use it features then it might be worth disabling it. you can do that through the app nstools (just search for it on the market)
[Nexus S Android Development] XxSilent22xX:
Still using test kernel 16 no radio dumps since the first one 24 hours ago everything seems fine.

EDIT: just realized kernel 17 is up going to give that ago and report tomorrow.

Sent from my Nexus S
[Nexus S Android Development] spyderman33:
just flashed 11.17 kernel and the screen goes green when it dims before turning off... WTF?

I fixed permissions and nothing... Its like a green tint before it shuts off...

I wiped cache and dalvik and flashed morphic dalvik wiper before flashing it...

Any ideas?
[Nexus S Android Development] some_random:
Yes 17 should be even better as I have been told that it includes the latest bug fixes for deep idle only updated 5 hours ago so fresh and ready to test :-D
[Nexus S Android Development] laidick:
Thanks.

Now I am using

17Nov CFS version.

Deep Idle : ON

LiveOC: 105

Governer: Lazy

Freq: 400-1000

Max Screen Off Freq : ON

Volt(arm/int) : STOCK

ROM: Kel MIUI 2.6.2

See if how it goes.

By the way, having the above setting, is it normal that when I am CHARGING the phone and screen OFF, the CPU will always stay in max freq? (I saw this in CpuSpy, DeepSleep time is 0%, max) and DeepIdle always 0? (saw in NSTool)

Everything normal when unplugged the charger.
[Nexus S Android Development] some_random:
Yep pretty sure this is normal because when your charging the phone doesn't go to sleep or deep idle and because max freq dictates that whenever the screen is off but the phone is still awake the frequency is max you end up with a lot of time at the max frequency but that's normal
[Nexus S Android Development] al_madd:
Are using cyanogenmod?

Well...I solved it by fresh install new ROM
[Nexus S Android Development] franciscofranco:
Quoting morfic about the colors:
[Nexus S Android Development] spyderman33:
Nope, using Kel Miui..

---------- Post added at 03:47 AM ---------- Previous post was at 03:33 AM ----------

How do I do this? A newby at the NS..

Nevermind found it

"Just set the minimum screen dim level value to 10. That fixed it for me. It is located under settings, display, advanced mode."

This worked for me... Setting it to 10...
[Nexus S Android Development] got2best:
Ok so after flashing 17 Nov ... I got black screen when some1 tried to call me... I know this because I went to look at my phone and it would turn on.. so I pulled battery and turned it on.. as soon as it turned on I had a voicemail left 30sec ago... and another time it took 5 power button pushes till the screen turned on and then I went and plugged it into power and it immediately froze... just wanted to report my problems.. maybe they can help? :) ..

Info:

i9023

Nscolleb

17 Nov kernal

Live oc 100

Governor lazy

Max frequency on..

If I left anything out let me know :)

Thanks for all ur hard work!
[Nexus S Android Development] Lalaca:
To the people having phone freezes, where the screen can be turned on and off with the power button but the touchscreen and capacitive buttons don't respond:

Are you using Live OC? If yes, with or without undervolting?

Up until 16 Nov test2, I have been using the following:

echo "1200 1175 1000 875 875" > /sys/class/misc/customvoltage/arm_volt
echo "1050 1050 1050 1050 950" > /sys/class/misc/customvoltage/int_volt
echo "110" > /sys/class/misc/liveoc/oc_value

With the above values, 16-test2 freezes at completely random intervals. Wondering if it was problems with voltage, I tweaked CPU to this:

echo "1225 1175 1025 900 900" > /sys/class/misc/customvoltage/arm_volt

Still random freezes.

17 Nov however, boot loops at either the boot logo or stops in the middle of boot animation, if I keep Live OC on. No problems booting with undervolt.

Currently I have removed the script, and testing at stock voltages (both ARM and INT) with Live OC only.

I suppose my next test should be if stock INT with Live OC causes boot loops. Dunno why all of a sudden my phone is not liking the combination of active mods.

Edit: Running a CM7 gigglebread kang from 10/31 on a 9020T (AMOLED).
[Nexus S Android Development] ciwek90:
yup! thanks mate!

awesome!! i used to love your kernel for my O1...now..might love this one! Thanks! :D
[Nexus S Android Development] as6:
better thread

I use your kernel since the last version and everything works fine for me except that I'm missing LiveOC.

I came from Matr1x which is also a great kernel. The main reason why I changed is that the Matr1x thread is no more readable for me. On every page the same question which are already answered in the OP.

So thanks for the great kernel the very good changelog and a perfect OP.

We should try to get this thread free of these stupid question. I'm sure there will become more of these questions because you make a great kernel and it will become very popular. So lets answer these questions only with links or things like: read OP, see changelog, use google or something else.

Thank you
[Nexus S Android Development] derekwilkinson:
matr1x for life!!!!!!

:eek::eek::eek::eek::eek::eek::eek:
[Nexus S Android Development] JmPTaz09:
I still can't get BLN to work on Brainmaster's rom either... I made sure the cypress file was in the place Brainmaster said to put it in but it still doesn't work... doesn't bother me much though, cuz this kernel is nice and quick and stable so far.
[Nexus S Android Development] franciscofranco:
I got this kernel in a nice place, I'm happy with it so one of the next steps is to add liveoc and make some testing with it.

About BLN I'll research a bit more, its strange that it works for some and not with others. Lets see.
[Nexus S Android Development] morfic:
In a screenshot a few pages back the bln app complaint about liblights, are you installing one that works with your kernel?

Those who switch kernels from one that installed it will have working bln. Fresh installs wouldn't have it if you don't already install it.

Just a thought.
[Nexus S Android Development] civicdrivr:
Thanks. Other then the BLN issue this kernel is running great. On Matr1x 8, 8.5 and 9 I would get quite a few rebooted/freezes thoughout the day. I haven't gotten a single reboot on this. I'm loving it.

Sent by carrier pigeon
[Nexus S Android Development] iamvincentwong:
I´m also running on KelLMSKing MIUI with franco.Kernel.

Appreciate your effort. It's really a great kernel.

Discovered one thing yesterday, the phone rebooted once when I turned off the screen around an hour, it rebooted automatically for three times with the 19.10.2011 kernel.

No reboot issue with 18.10 kernel.

I have updated the latest kernel to see the reboot issue still exist or not.

One more suggestion for the kernel improvement,

It took more time for preparing USB storage after the phone was switched on or reboot, when comparing with matr1x kernel. Could you do some tweak on it? Thank you!:D
[Nexus S Android Development] skinniezinho:
Maybe that's why I had BLN working on MIUI English...I had your kernel installed,and then switched to Franco Kernel.

Now I fresh installed miui pt and franco kernel and didn't have bln.

Just flashed your kernel, BLN Working.Flash Franco Kernel and BLN Works!

You made my day!

Franco you could post this "temporary fix" in the first page for users with BLN problems.

It doesn't take much longer..5 ou 6 seconds?when switched for the first time..when rebooted it is faster..
[Nexus S Android Development] ro_explorer:
How come the voltages in this kernel are so off compared with matr1x kernel?

More than that, if I'm trying to lower the voltages, even by a small amount, the phone will freeze.

Anyway, I'll give it a shot with the defaults settings to see how it behaves.
[Nexus S Android Development] skinniezinho:
read the last pages.I had the same issue.
[Nexus S Android Development] franciscofranco:
I'm using the default voltages that come with the CM kernel. It works fine for me.

About the undervolting issue with SetCPU and Proton I'm gonna work on that just now, I'm gonna make sure the OV/UV interface isn't broken after I'm done with it.

@morfic

Yeah I thought about that too, thanks for that!
[Nexus S Android Development] thedudejdog:
I'm seeing less than 1% battery lost over 2 hours of idle. That's insane. -1mA drain.
[Nexus S Android Development] JmPTaz09:
Changing voltages with setcpu works just fine for me on the last two builds, just the first one was screwy for me at least
[Nexus S Android Development] caleb1783:
yeah. setcpu working fine for me

proton doesnt work though... could be because of 1.1ghz...

testing smartass2 w 800/200..

itz as smooth as 1.2 imho...

Sent from Divinus Nexus S...
[Nexus S Android Development] Jonathon Grigg:
The issues with Proton are definitely due to the additional 1.1ghz step, as a bad mistake in my early app development life I basically hard coded in the 8 frequency setup used in Netarchy kernels as that's all that there was out, but now similar code is used in different kernels it doesn't work. I'm really busy but I do plan a rewrite (which is half done) to fix this at some stage in the future.

Sent from my Nexus S
[Nexus S Android Development] bgdxv:
Does this kernel include the commit from stock CM7 kernel that makes battery charge up to 100% ? Thanks
[Nexus S Android Development] ro_explorer:
You know what ? .. when I woke up this morning, I had 2% battery loss after 8 hours ... this with 3G enabled, Wi-Fi always ON and 2 push e-mail accounts active. I didn't saw this kind of battery life since froyo + speedmod kernels on my GalaxyS :) .... Giving this, I really do not mind to use whatever setup you are putting in :).

If is not broken, do not fix it ! :)

Amazing work so far.

My setup: Freq range : 100MHz - 1.2GHz, SmartassV2 gov, everything else with default values in the kernel. The rom is STOCK 2.3.6
[Nexus S Android Development] skinniezinho:
Don't know if it has that commit or not, but it charges up to 100%.
[Nexus S Android Development] caleb1783:
charges upto 100% !

Sent from Divinus Nexus S...
[Nexus S Android Development] mixtapes08:
What is SAMOLED TWEAK.? I find it interesting to know...

Device: Nexus S

Rom: Latest MIUI

Kernel: Latest GlaDos cfs

Baseband: I9023XXKD1