yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] mike216:
I believe he has made some great looking color modifications to look great on our super amoled display!

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] frenccw:
Nope, no Live OC. Stock voltages. Haven't happened on latest built yet. :rolleyes:
[Nexus S Android Development] mike216:
If you liveoc your going to have to bump your voltages up some

If your 110 and up definitely bump them up. When you liveoc your buss speed is also increased so you need more power for stability

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] Lalaca:
Um, I did say I was using undervolt together with Live OC just fine before the two versions mentioned.

There were users mentioning freezes like I was experiencing, so asked because I thought the causes might be similar.

Whatever, I'll figure it out later.
[Nexus S Android Development] morfic:
I had reports of unresponsive touch screen on TEUV kernel build with the GPIO save/restore patch by Ezekeel, this does not happen w/o this patch in.

TEUV is a undervolted kernel by default.
[Nexus S Android Development] ro_explorer:
Well ... Good Morning to everyone (at least for you .. I only had like 5 hours of sleep :( ) ...

Anyway, back on track: EXCELLENT WORK FRANCO ! ... ~1% drop in 5 hours .. this must be the record :)

So ... let me repeat the setup so I will not have to repeat it again after few more posts :)

- device - i9023

- kernel - nov 17 - cfs

- STOCK 2.3.6 rom (the original odexed one) with root access and CWM installed.

- modem XXKF1

- no UV - standard voltages

- no OC: liveOC = 100

- governor: conservative (so the screen off freq. is irrelevant, being active only in lazy gov.)

- 100 - 1000 frequency range

- BLN ON

- deep idle - ON

- no task killers

- low-mem settings - 4, 8, 16, 32, 48, 64 MB (set-up by me ... I have the best long-term behavior with these numbers)

- data on, 3g-auto, wifi used only when high-speed data is required, sync on

- bluetooth ON (I always keep it like this)

I've partially load the battery before going to sleep and it went up to ~71% ... in the morning (5 hours later) it was at ~70% ... attached snapshot will reinforce this statement.

Idle stats are showing a lot of deep idle (top=on).

What can I say .. if the rest of the tasks will be performed well I think I'll keep this kernel for a long time (with ICS around the corner I don't expect it to be such a long wait).

Franco, on my salary I'll buy you another beer ... now I'm broke :).

Oh .. and let's not forget about Ezekeel ... excellent work on deep_idle fixes ...
[Nexus S Android Development] mike216:
Good mornings ro-explorer thanks for the unlock minfree find by setting permissions correctly, very good stats,goodnight (eastcoast )

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] ro_explorer:
Mike ... I bet that there are at max a handful of people seeing that file permission fix stuff :) ...

Anyway, glad to hear it worked for you also.
[Nexus S Android Development] ciwek90:
im now on GLaDOS kernel...and i want to try this kernel. So, what should i do? just wipe cache and dalvik only (like normal way) or need to delete init.d folder or script before wipe and flash this kernel? thanks!
[Nexus S Android Development] ro_explorer:
Do not wipe anything .. just flash. The flash process itself will take care of cleaning up whatever it needs (including init.d folder, dalvik and cache partition).
[Nexus S Android Development] kevinngck1:
Excellent report! Which version are you using?? csf or bfs?? Ondemand or lazy???
[Nexus S Android Development] ro_explorer:
I've updated my post to include the CFS version spec.

As for the governor ... is there in your quote :P.
[Nexus S Android Development] ciwek90:
Thanks! :D
[Nexus S Android Development] Lalaca:
Thanks morfic.

That was the patch introduced to fix the battery drain with deep idle, right? Explains why those versions are experiencing that behaviour.

And of course, I know of TEUV. It's my favourite kernel. ;)
[Nexus S Android Development] Sykkr0:
Same here, all stock (Live OC = 100 and default voltages).. No freezes so far with the 17NOV kernel, though! :D
[Nexus S Android Development] Heretic Infidel:
I would like for everyone to give a little clap for franco & ezekeel.

I have updated to the newest kernel and Woe and Behold!

The facts :

2 hours of testing

Stats from History tab of battery monitor widget

I9023

CM7.1

Deep idle = ON

400/1000

no UV/LOC

Battery @ 40 - 38%

the average battery usage is:!

20 to 40mA

The graph is pretty much flatlining. I would call this new kernel a succes ^^

I will continue testing, running the battery down then do a recharge to 100 and test again.

No reboots or other funky stuff
[Nexus S Android Development] MultiCulti:
heavy usage with just short brakes for my nexus :D during the day

beamed in from my Nexus S on Oxygen using my brain
[Nexus S Android Development] Lalaca:
Well, at this point, I'm not sure to facepalm or sigh in relief, but my earlier issue regarding boot looping appears to have been successfully resolved by raising the INT voltages to:

echo "1075 1075 1075 1075 975" > /sys/class/misc/customvoltage/int_volt

This is an addition of 25mV across the board. Whether this will also help resolve the random freezes and SODs remains to be seen.

The GPIO save/restore patch that was introduced in 16-test2 and 17 Nov to fix the battery drain in deep idle seem to have affected the sensitivity(?) of the bus voltages when raising bus speeds (via Live OC, or simply using TEUV). morfic has already reported this issue to Ezekeel in the GLaDOS thread.

During my tests for boot looping, I attempted to keep my undervolted ARM/INT (both together and separately) values and Live OC, while disabling deep idle through an init.d script. Only the ARM-only undervolt managed to boot repeatedly without problems. The script apparently kicks in too late in disabling deep idle, which is enabled by default in franco's kernel. This (deep idle on by default) may not be the case with TEUV, which I guess might alleviate the freezes and SODs, for the obvious trade-off of not having deep idle.
[Nexus S Android Development] jeffkhlam:
just FYI, Using 17 Nov cfs and nscollab .42, quadrant score is 40xx. Highest ever. LiveOC 110. Rest are default values.
[Nexus S Android Development] ro_explorer:
Ohhhh NOOOOOOO ... not again ... please ...
[Nexus S Android Development] jeffkhlam:
as i said, just FYI. i know its not important but there are always some people asking about it. 40xx is highest i get from all the franco kernels.
[Nexus S Android Development] ro_explorer:
For My Information (and I think I'm not alone in this) the quadrant general score is 120% irrelevant.

If you want to give us something really useful, put the CPU (and eventually GPU) score ... nothing else.
[Nexus S Android Development] got2best:
Sorry for the ot question.. I just wanted to ask quickly.. are battery stats stored on the battery or on the phone?
[Nexus S Android Development] jeffkhlam:
not in the battery for sure.
[Nexus S Android Development] some_random:
battery stats are stored in the rom
[Nexus S Android Development] ro_explorer:
For the battery stats check:

/data/system/batterystats.bin
[Nexus S Android Development] aiacone:
Big Franco, THNX again for yur good work! I'm using 13/11: all is perfect and, because Best in enemy of Good,...

A question about 17/11: I purchased Voodoo Control Plus to control my super amoled panel colours. Does your implementation conflict with? How can I disable?
[Nexus S Android Development] franciscofranco:
No conflict at all, I just tweaked the default values, nothing more ;)
[Nexus S Android Development] roshga:
So if in the past we have set different values we should just click the default button?
[Nexus S Android Development] FloHimself:
Posted this somewhere before:
[Nexus S Android Development] franciscofranco:
Dunno about that, my nexus isnt an amoled version so a I dont know about those procedures.
[Nexus S Android Development] hilton502:
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/lazy/screenoff_maxfreq

if i do that as ups,can it longer standby time? save power?:confused::confused:
[Nexus S Android Development] roshga:
Oh i.c..

I just can't be sure if the values has changed or not... can you write values that you have set?
[Nexus S Android Development] franciscofranco:
https://github.com/franciscofranco/Nexus-S/commit/8453af2402940c42e7dbd6a0969677b7c21b2015
[Nexus S Android Development] y3mita:
Weirdest thing just happened!! My phone starting going back as if I were hitting the back button on its own!! It's either alive or hacked??
[Nexus S Android Development] got2best:
Sorry for this weird OT question again.. but I was wondering since the stats are on the phone is it bad to have 2 batteries.. I recently purchased a battery off ebay.. stock OEM battery nothing special same as original and was wondering if that would mess up stats. Any1know? Thank u!
[Nexus S Android Development] hilton502:
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/lazy/screenoff_maxfreq

if i do that as ups,can it longer standby time? save power?
[Nexus S Android Development] Heretic Infidel:
And a new update. did a full charge. First hour is -2mA and following is a constant -20mA

Deep Idle = ON

No OC

as before.

Good work Franco & ezekeel
[Nexus S Android Development] aiacone:
Gamma hack, from Franco's github:

+int hacky_v1_offset[3] = {-26, -30, -33}: correponds to punchy setting on Voodoo control plus;

-int hacky_v1_offset[3] = {-14, -17, -18}; the other values I can read.

But what is implemented?
[Nexus S Android Development] roshga:
Found out the values after uninstalling voodoo >> reboot >> installing again

RGB:

185

212

325

gamma:

-26

-30

-33

(punchy settings)
[Nexus S Android Development] Jonathon Grigg:
I have the exact same issue, fear not its most likely a touch panel issue like mine. I've been told there is probably something wrong with my touch sensor which covers the entire front of the screen (I occasionally get patches on the screen which don't respond until I lock/unlock as well, it's all tied in) and the way to fix it is to send it in for repairs. They replace the front panel and it should be fixed. Others have had this issue and they told me similar things.

Franco, sorry for the off topic but I thought I'd help out here :) and fear not, this behaviour occurs on any kernel I have tried for long enough, its not some bug.

Sent from my Nexus S
[Nexus S Android Development] y3mita:
Thanks a lot JG ;) btw... I tried your carbon ROM but recently switched to latest Oxygen to keep trying best combo ROM-Kernel... and Franco if you do not mind my off-topic question to him...

JG I read you were working on your own kernel based off _thalamus.... Are you using your carbon core as your daily?
[Nexus S Android Development] HeavenlyWinds:
Great on KelLMSKing MIUI, better than NOV-13. No Bugs.
[Nexus S Android Development] vis80k:
oxygen 2.3.2. Flashed franco 17.11 kernel, then something I never experienced with franco happened... SOD!!

Wonder why... can anyone enlighten me on what might be causing this?
[Nexus S Android Development] chinopski:
ro_explorer settings

got a reboot using latest kernel and ro_explorer's settings

hopefully it wont happen again. still under observation

overall, great kernel mr. franco. thanks!
[Nexus S Android Development] some_random:
Flashed 17th last night heres my setup

- device - i9020

- kernel - nov 17 - cfs

- CM nightly #257 (because I have heard reports that 259 is unstable)

- radio XXKF1

- no UV - standard voltages

- no OC: liveOC = 100

- governor: lazy

- 100 - 1000 frequency range

- BLN ON

- deep idle ON

- max freq OFF

- no task killers

- data on, 3g-auto, wifi used only when high-speed data is required, sync on

Battery has been great so far the drain is much better than previous kernels I have tried no SoD's or random reboots and I have had no data drops so the radio is behaving how it should be as well..

needs more testing as I have only had it for a little over 12 hours now but so far so good nice work franco :D
[Nexus S Android Development] ro_explorer:
Another day had passed and the phone is acting great. 100% stability and great battery life.

Sent from my green robot ...
[Nexus S Android Development] some_random:
what happened as the photo says
[Nexus S Android Development] ro_explorer:
That was one of the stability tests. That was that sort of usage which will take your battery from full to empty in about 4-5 hours :) ... Luckily I did it only for about half hour.

Here it's the detail of that moment:

Sent from my green robot ...
[Nexus S Android Development] uansari1:
So what's the consensus? Are we better off leaving deep idle enabled all the time for best battery life?
[Nexus S Android Development] ro_explorer:
The answer is : "definitely YES"

Sent from my green robot ...
[Nexus S Android Development] XxSilent22xX:
Running kernel 17 for 24 hours happy to report everything is running buttery smooth :) Thanks Franco!

Sent from my Nexus S
[Nexus S Android Development] skinniezinho:
Finally took some time to look at my phone.

It seems that with this kernel I'm back to the old days =) zero % loss in the night in airplane mode!

Latest MIUI

Deep Idle on

Undervolt 50mv (in the 100-200MHz it is more undervolted)

200-1000 lazy

Congrats Francisco!Great Job!
[Nexus S Android Development] some_random:
with the new 17th kernel that is a certain yes
[Nexus S Android Development] hachoo:
No stability issues so far. Still figuring out whether conservative or lazy governor is better. The lazy governor is a little laggier and less responsive IMO, so I'm sticking with conservative for now.
[Nexus S Android Development] skitapa:
400, 1000 lazy. Bln off, touch wake off and buttons off. Screen of max on.

Love the new 17, good battery. The big dip is me making a rom backup in cwm. Good job Francisco :-)
[Nexus S Android Development] Cybergr:
It`s supposed to be the opposite i think!

:rolleyes:
[Nexus S Android Development] waterface:
Running latest Oxygen, had two reboots in my first hour of testing 17Nov kernel. Strange, probably wouldn't have happened again with another wipe/flash. Nonetheless, I just thought I'd test with Oxygen's default kernel first, and see how "bad" battery was...and it's not bad at all. It's also the first charge cycle, maybe it'll improve.

I even used the Torch app for some ten minutes! :)
[Nexus S Android Development] Cybergr:
I read that many users had some random reboots with whatever kernel version under Oxygen 2.3.2..So i had a look under Oxygen original thread here in XDA and i noticed the same thing..random reboots on Oxygen 2.3.2 not so many though..This is something unusual for Oxygen noticed for the simplicity and stability.

As for me, i am under Oxygen 2.3.2 and 17.11.11 CFS kernel..I used this combo for more than 30 hours and got brilliant battery life, 1 reboot this morning and 1 signal dump yesterday evening..I will stick with this combo a little bit more and maybe i will revert to Oxygen 2.3.1 cause never got a single reboot with whatever francos kernel on that ver.
[Nexus S Android Development] theadb:
Testing for the past day and no radio dumps, restarts or bsods. So far so good...

Does this charge to 100%?
[Nexus S Android Development] frenccw:
Hey guys just reporting that i am still having mobile connection loss issues with the latest kernel. The worst part about it is that when i am connected to wi-fi, i the connection appears "green" but in actual fact i am disconnected and people could not contact me. (And vice versa i can't call out)

Right now, i'm gambling that Deep Idle is somewhat related to this so i'm disabling it and putting it on a test run. Will post results in a few days!
[Nexus S Android Development] franciscofranco:
I started to use devnull, their almost pure AOSP 2.3.5 version, and it's been more than stable to me. This latest 2.3.2 is a little unstable.
[Nexus S Android Development] Cybergr:
I will stick with Oxygen 2.3.1 Kang cause i found it to be really fast and stable, or maybe give a try with Devnull as u said that is more than stable.

Too pity though i have to reconfigure everything..
[Nexus S Android Development] mike.b93:
running with franco kernel 17.11. for 18h now and i got 40% of the battery left.

Screen is on full brightness. Live wallpaper, wlan, browsing, gaming and so on. I really use my phone.

I never got that great battery life everybody's talking about xD :) But it's totally okay if I have to plug in the phone every night.

Oxygen is the most stable and the fastest Rom i've tested so far. I've tested CM7 and NSCollab. I especially love how everything is pure Android.

Very very powerful Rom :)
[Nexus S Android Development] phone_user:
Adding "/system/etc/init.d/" function to DevNull v1.1 with dsixda's Android Kitchen

Intact, only adding that

Download

devnull-1.1_init.d.zip

+ deodexed

Download

devnull_1.1_init.d_deodexed.zip
[Nexus S Android Development] waterface:
Well then for my random reboot, it may have been the ROM. I guess I'll try again. I have never tried devnull, I'll give it a go. Damn it, I'll never stop flashing...

By the way, real quick, has a permanent fix been found for the CAM bug so that one doesn't need to open/close the cam app or replace GTalk with the video-less version?
[Nexus S Android Development] ragnarokx:
Lazy is supposed to be the best for battery, but I also use conservative because it is just all-around smoother.

Same exact thing happened to me yesterday. Disabled WiFi, saw I had no connection, then rebooted and got a buttload of text messages.
[Nexus S Android Development] hachoo:
with deep idle on, the battery life on v17 is unbelievable. The graph looks very flat with conservative governor (1050/105).
[Nexus S Android Development] franciscofranco:
I do think thats deep_idle related, I reported the same thing and other users got that with Galdos kernel as well.
[Nexus S Android Development] some_random:
no, not really... the only other thing you could try is to get a scrip to run on start up to open the camera which I have heard works

for me it doesn't really bother me too much that I have to open cam on start up I just have to remember to actually do it :P
[Nexus S Android Development] Maximilian Mary:
Is anyone who is having data issues running stock voltages and stock (100%) live_oc?
[Nexus S Android Development] got2best:
Not here.. currently UV but still no.
[Nexus S Android Development] ro_explorer:
New symptom ...

I've tried to set the wifi sleep policy to never and it worked for a while but I just observed 5 minutes ago that even if wifi was on, I had no connectivity whatsoever. Turning the wifi on and off again solved the issue.

If I'm keeping the sleep policy to"when screen off" everything is fine.

I didn't had any 3g data off yet.

Sent from my green robot ...
[Nexus S Android Development] franciscofranco:
Can you try without deep_idle please.
[Nexus S Android Development] franciscofranco:
I have gsm/data loss during the night with 110% live_oc and deep_idle activated.
[Nexus S Android Development] caleb1783:
thats odd..

i m using oxygen 2.3.2 w liveoc 110 and lazy offscreenmax on.

uved as well. stable and fast as ever... no radio dumps as well. could it be modem version problem?

i am using kf1..

Sent from Divinus Nexus S...
[Nexus S Android Development] brenix:
No radio dumps or loss of service/signal here. Also using kf1 radio..
[Nexus S Android Development] Jonathon Grigg:
I've been chopping and changing kernels to try the latest deep idle stuff, mainly because I've been too busy to update things myself. Still undecided on it though. Sorry Franco :)

Sent from my Nexus S
[Nexus S Android Development] phone_user:
If the situation has come this far, please try GPA19 please. Never losing gsm/data, I have experienced many roms

17 NOV cfs battery use during the night

device : 9020

rom : GPA19 23-10-11

deep-idle enabled, lazy, liveoc 110, 440~1100 MHz , screenoff_maxfreq ON
[Nexus S Android Development] notabene:
My night of 9023, with MIUI BM, and 17.11 franco, 105LiveOC, -25mV UV, lost 2% AMAZING JOB! Finally I can say, that this is best version, for me.. Trying from the first ones..
[Nexus S Android Development] r5xscn:
Same here. No signal after 14 hours on battery. Suddenly the phone restarted, and Use 2G only checkbox not checked (before was checked).

Battery live on franco.Kernel.17112011-cfs is great, 1% for 8 hours (when sleeping).

Nexus S I9023 Stock ROM 2.3.6. KF1 DeepIdle on, BLN on, and BatteryLifeExtender on. No Live OC.
[Nexus S Android Development] ro_explorer:
Tried that .. the issue is happening only with deep_idle enabled.
[Nexus S Android Development] notabene:
I don't have any issue with signal loss or wifi not transferring data :) Maybe its due LiveOC?
[Nexus S Android Development] Heretic Infidel:
Ok, did some more testing since friday.

I am currently at 23% charge after charging to 100% friday at 18:00. Mostly had my 2G on as 3g is terribly spotty inside the house.

The mA used is :

-20mA with 2g

-40mA with 3g on.

This means that yes, in 4 hours, i will have had 2 days on a single charge with Deep Idle Enabled! woop woop^^

I did have a random reboot in the middle of the night, reason unconfirmed.
[Nexus S Android Development] LordPhong:
Just had signal loss overnight and I'm not using liveoc or uv.
[Nexus S Android Development] frenccw:
No signal loss reported after turning of Deep Idle for 24 hrs, but boy has the battery life taken a significant hit!
[Nexus S Android Development] krex:
Is there way to set 1.4Ghz cpu and 200 busspeed with this kernel?

Thanks!
[Nexus S Android Development] franciscofranco:
No, there isn't, sorry.
[Nexus S Android Development] some_random:
you could set liveoc to 140... that would get you to 1.4ghz and then you would have to up your voltages accordingly

however I don't know what the busspeed on this rom is to start with but wouldn't liveoc overclock that as well? correct me if I'm wrong
[Nexus S Android Development] Maximilian Mary:
200, and yes.

That world give you a bus clock of 280.

Best of luck! :D
[Nexus S Android Development] mike216:
That's really high you better make sure you don't have save settings in nstools
[Nexus S Android Development] some_random:
I didn't say it was a good idea he just asked if he could get this kernel to 1.4ghz
[Nexus S Android Development] thedudejdog:
I think he said with a 200mhz bus ;)
[Nexus S Android Development] some_random:
yeah well I tried didn't I :P
[Nexus S Android Development] mike216:
I wasn't at all being critical I was just saying to remember about the voltages if going that high
[Nexus S Android Development] phone_user:
I've experienced gsm/data loss only with bfs kernel mainly on CM-based roms in the past. Your latest issue may have to do with bfs tweaks to cfs?
[Nexus S Android Development] franciscofranco:
Hmm that could be one reason indeed. I'll investigate thanks.

EDIT: Ezekeel's kernel uses BFS tweaks on CFS like me so I guess that's unlikely.
[Nexus S Android Development] frenccw:
I'm using a CFS NS Collab rom (based on CM) so i don't think that's the issue.

Strange issue: No connection loss with Deep Idle disabled but the connection icon turns grey very frequently. However, mobile and data connection remains active ie. can makes call out and use Whatsapp/Market. Turns green again if i access google apps like Market. :eek: Not a big deal since everything still works
[Nexus S Android Development] some_random:
but is your gmail still push. are you getting emails that are sent even when your on that grey icon?
[Nexus S Android Development] frenccw:
Hmm not sure i'll try that out the next time it happens.
[Nexus S Android Development] some_random:
ok because I had this happen to me and it looked like my emails weren't coming though and that would be a problem because I need my push emails. so if you could confirm that would be awesome