yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Black Coffee:
Could someone please tell me how to check whether the "Deep Idle" is enabled or not ? If it is disabled by default, Please guide me with the method & app to be used to enable it.. Thanks in advance.. !
[Nexus S Android Development] bdpyo:
+ 1

Thanks. :)
[Nexus S Android Development] thoth77:
General Filename

For set cpu (Governor, Voltage, Frequency), that filename is general

You don't need to rename it
[Nexus S Android Development] skinniezinho:
Only a question (asked almost the same to franco through pm but he may be busy).

I edited the file like this:

(it's +- -50mV to the stock values)

I move the file as you say, change permissions and reboot (in franco kernel) it hangs...if I go to recovery and flash morfic's kernel it boots ok.

I even did this from scratch with morfic's kernel and it boots ok,if I flash franco kernel it hangs on the animation...

The thing is that I can't confirm running voltagens in Morfics Kernel...proton will only say 100mv in the "existing voltage" part, and setcpu doesn't show the voltage part.The only thing that gives me a clue that this file is applied is the lowest mhz being 200MHz instead of 400MHz on the "stock TUV kernel"..

Any suggestion?
[Nexus S Android Development] thoth77:
Fraquencies, Voltages

Franco says in OP "I managed to undervolt my device by 50mv in this three frequencies: 1000, 800 and 400"

The values that I suggest is based on it

The freqencies in Fraco Kernel, 1 more "1100mHz"

This is table of stock voltages

1440mhz: 1440 mV

1300mhz: 1390 mV

1200mhz: 1330 mV

1100mhz: 1290 mV

1000mhz: 1250 mV

800mhz: 1200 mV

400mhz: 1050 mV

200mhz: 950 mV

100mhz: 950 mV

I don't know the frequencies and voltages in Trinity kernel
[Nexus S Android Development] skinniezinho:
Well, revised the file and took 50mV in the 1000,800 and 400MHz:

Finally it is working!althought switching them "on the fly" using setcpu to other value (even if it is the same value) blocks my phone and then it restarts,but it is ok form e now =)

edit: working too on the latest 1.10.21 MIUI
[Nexus S Android Development] ragnarokx:
Is there a way to also set scheduler using this method?

Sent from my Google Nexus S
[Nexus S Android Development] Cybergr:
So i have to edit the file /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table and just increase the mv by 50 on the following frequencies 1000,800 and 400??Or just decrease by 50mv?!
[Nexus S Android Development] thoth77:
sorry

I don't know about it
[Nexus S Android Development] ciwek90:
im using BrainMaster MIUI ROM...if i flash this kernel..i want to know weather the deepidle tweak is enable by default or i need to do something? really confuse here.... :confused:
[Nexus S Android Development] franciscofranco:
If people would read the first post everything would be so easy. Yes it's enabled by default and it's the last time I'm answering this question, it's in the damn changelog.
[Nexus S Android Development] Cybergr:
When I use Trinity kernel I can have a stable 1.44 ghz overclock...I mean I can run all the benchmarking apps without any stuck and restart..With all other kernels including this one when I overclock up to 1.44 ghz I get stuck and my device reboots..!!

Someone has any clue on this..!?

I even played a little with the voltages, increasing the voltage for 1.440 ghz from 1440 mv to 1475 mv..

PS: Tried to run antutu with 1300ghz default gov. and min clock 100 and my nexus s freezed and rebooted..strange cause 1300 was stable for me on all kernels I tried..
[Nexus S Android Development] skinniezinho:
You don't have to do nothing, unless you know what is undervolting and understand what are the benefits and the risks.

If you knew what is undervolting you wouldn't ask that question.

It's to decrease.please read some wiki articles =)

WTF, now that I am using MIUI PT I have the BLN problem...

Will ask in the MIUI forum, because with english MIUI I had no problem.
[Nexus S Android Development] senfoo:
wow

this kernel made a huge jump in speed for bugless pete's rom!

so far so good, will check to see how battery life goes...
[Nexus S Android Development] Cybergr:
I know exactly the risks and the benefits when i play with the voltages when i over-volting or under-volting my handset..My question before wasn`t only for under volting but doesn`t matter really..!!

I am just trying to figure out how i can get a stable 1.44 Ghz on these kernel like on Trin1ty one!!
[Nexus S Android Development] skinniezinho:
Franco, guess ciwek90 meant, how would he check that deep idle is working (even knowing that you have it enabled on the kernel).

It's like BLN, you have it enabled on your kernel, but we have to install BLN Control in order to test that it is working.
[Nexus S Android Development] ciwek90:
im sorry for my noobies....but that what makes me confuse bcoz in BM MIUI Thread said need to delete pm.sleep_mode=1 in the build.prop to activate the deepidle....that is why im asking...thank you for quick reply...i will try without delete the build.prop...will come back later to review..i notice this kernel don't have voodoo or am i blind? hehe :p
[Nexus S Android Development] franciscofranco:
Delete that **** from the build.prop, otherwise you'll run into some problems.Yes this kernel has Voodoo stuff already.
[Nexus S Android Development] civicdrivr:
I just flashed this kernel and so far its great. I've got it set to 200/1200 smartassv2 and no reboots or bsods so far.

But the BLN app gives me the liblights error. I'm running CM7 N230 and I did check to make sure the .bin file was in the firmware directory (but I'm not sure if that was MIUI only?). I've reinstall the BLN Pro app and it still shows the same error. From my understanding, BLN is activated by default in the kernel but that doesnt work for me either.

Sent by carrier pigeon
[Nexus S Android Development] ro_explorer:
I really appreciate your work and I greatly respect you but you are talking nonsense here ... sorry to say that.

"overnight" should be read as "when I'm not using my phone".

I personally love mountain biking ... and during the summer I go in the mountains with my MTB. Of course, the phone is always in my pocket. Belive me when I say that I'll NEVER go in the mountains for one or 2 days with a device that is burning so much power by doing nothing.

Of course, it is a different story on daily city use ... but let's not miss the point :) ...
[Nexus S Android Development] raulillo88:
Don't you want feedbacks? This is an issue, I think, but with this support I don't use this kernel anymore

Enviado desde mi Nexus S usando Tapatalk
[Nexus S Android Development] raulillo88:
Enviado desde mi Nexus S usando Tapatalk
[Nexus S Android Development] franciscofranco:
Ok, I misunderstood your "overnight" notion, I'm sorry for that. I was just checking my sources and I don't know what might be causing that difference in "standby" consuption between the 24/10 kernel you like, and the latest stable/test releases.

I have a "job" for you then, can you disable deep_idle and tell me if there is any difference with both kernels and then report back? Thank you :)
[Nexus S Android Development] polobunny:
My company got some new phones for out photographers and the bosses. They got 2 Nexus S and 1 HTC Panache....

I want to root them. :D
[Nexus S Android Development] ro_explorer:
Sure .. will do that. Give me few days to check this and I'll report the results. I hope you're not in a big rush.

I'll use as reference the Oct 24 kernel (currently running on the phone) and in couple of days I'll switch to whatever last stable version will be available then.
[Nexus S Android Development] franciscofranco:
Not in a rush what-so-ever, take your time, thank you I'm sure it will be valuable for everyone.
[Nexus S Android Development] martinsjt:
Hello Franco,

I agree with ro_explorer my bedtime is the perfect time to test the kernel doing nothing as I'm not interacting with the phone.

So I charge the thing before go to bed and in the morning I have a pretty good idea about the kernel energy consumption in the void ;).

For me the best realese, energy wise, is the 6 November although i no longer have the 24 and 27 to test.

I Use SuperOSR 2.2.4 and to test without apps interference I used a barebone version of the ROM.

http://wiki.cyanogenmod.com/wiki/Barebones

Best.
[Nexus S Android Development] mike216:
25,27,08, get very good deepidle. In airplane mode I loose like 1,2% over 8-9 hours but recent deepidle versions by you and ezekeel seems like its not going into deepidle

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] franciscofranco:
Deep_idle is only when there is background activity like music during screen off, for everything else, normal idle is used.
[Nexus S Android Development] mike216:
Then the other possibility is that on these earlier versions the stats are not accurate and we think were getting better battery?

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] phone_user:
On 15 Nov test version, there is no background activity like music during screen off, but my idle_stats shows these

idle state total (average)

===================================================

IDLE 132390ms (2ms)

DEEP IDLE (TOP=ON) 0ms (0ms)

DEEP IDLE (TOP=OFF) 13708ms (26ms)

What happened to this?
[Nexus S Android Development] Flying Fox:
Maybe you used your phone for calls? Maybe some synchronization or other active apps....
[Nexus S Android Development] franciscofranco:
Well, I found out that when using the cpu_idle backport deep_idle wasn't really used, and those were the versions that people report better battery life... I'm merely stating reports, I haven't actually tried to run my phone without deep_idle to see if there is a difference.
[Nexus S Android Development] ellesshoo:
Could you provide a link to the version you think is the best? I am willing to test your theory.
[Nexus S Android Development] mike216:
Front page

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] mike216:
Well ill disable it and report back!

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] Cybergr:
This is CyberGR`s Nexus S speaking...

Please Franco stop humiliating me, i repeat, stop HUMILIATING me!!

My owner believes that i can`t fly but now he barely can hold me

into his hands..!!

So please stop before i fly to Portugal in no time and mess your room up!!

For god shake a little bit of respect on me..Thats all i am asking!! :mad:

This is CyberGR speaking...

Sorry Franco my Nexus S just went crazy...sorry about that mate!!:o

I offered you a beer just to forget what it said!!CHEERS..!!! :rolleyes:

Oww...and don`t even think to respect that ******..Keep it up!! :D

PS : Excellent work on your last stable 13.11.11 Kernel CFS as always..

Blazing fast and no problems for the moment in combination with Oxygen 2.3.2 Rom!!I am very happy with the results!!
[Nexus S Android Development] 1PATRIK:
Waiting for the results! After those I can think about changing kernel to older one, that gets better battery life.
[Nexus S Android Development] got2best:
I am wondering about this.. I know this horrible battery. But please note that I just did bat stats wipe.. and I want to know why when I restarted my phone the battery percentage drooped like 10%
[Nexus S Android Development] ro_explorer:
Do you think I can not see right the battery status reported by a known monitoring tool ? :) ... check attached .. the first day from my battery saving quest :) .. this is with light usage.

By deleting the battery stats the phone turned itself to some default battery readings, which meant 10% less than the real capacity. You should see something like a flattening tendency of the battery graph toward the lower percentage (re-adjustments).
[Nexus S Android Development] ro_explorer:
I've answered to your PM.
[Nexus S Android Development] polobunny:
An issue i've had for super long, so long that I don't recall when it appeared. When the screen is off and I press one of the softkey buttons, the softkeys will all light up and stay on unless I hit the power button once. Not sure it's related to ROM or kernel, but who knows, maybe someone else can chime in on this?
[Nexus S Android Development] thedudejdog:
It's related to touchwake. If you disable touchwake it'll stop that.
[Nexus S Android Development] polobunny:
Touchwake is disabled. I thought it was that too, but I've never used touchwake and I disabled it manually. :confused:
[Nexus S Android Development] Cybergr:
Have u tried to flash another kernel version with the standard wipe cache/dalvik (use Morfic`s dalvik wiper .zip) method and see what happens?!From the previous versions i can suggest u trying the 08/11/11 ver.!

(or just disable touch&look <----- just kidding on this one ;) )
[Nexus S Android Development] polobunny:
Well, nevermind guys, guess it got re-enabled somehow at some point in time and I thought I had it off. Everything is fine now. :|
[Nexus S Android Development] thedudejdog:
So, you can also confirm it's

a touchwake bug?
[Nexus S Android Development] brenix:
I'm curious if there is something else in the cpu_idle backport that could be effecting this?? I haven't tried disabling deep idle, but I did try adding/reverting the cpu_idle backport back in and reverting the test older deep idle configuration commit and I must say the battery drain appears to be a lot slower/better. Of course the idle_stats does not show anything so I cannot confirm whether deep idle is really being used or not..

I'd be interested to see what ro_explorer's test results may be.. I might try a couple other things, but I thought I would share some of my testing..
[Nexus S Android Development] frenccw:
Not sure if this is kernel related, but recently i've been losing network connection around once a day randomly. Can't call out, no mobile data, can't turn on airplane mode. Only rebooting solves it.

I think it started around the same time i flashed 13/11. (I've been consistently upgrading this kernel since its beginnings and didn't have this issue)
[Nexus S Android Development] ragnarokx:
Getting about 2 random freezes a day on the newest kernel version, going to revert to an older version. No modified settings, brainmasters MIUI.

Sent from my Google Nexus S
[Nexus S Android Development] polobunny:
I have absolutely no idea. I disabled it and rebooted and now all is fine. I'm guessing something might be interfering with it somewhere. I'll report back if I find anything juicy.
[Nexus S Android Development] tylercarter:
Same thing happened to me once. Just toggle airplane mode and it should go away.
[Nexus S Android Development] mike216:
Franco I turned deepidle off and battery dramatically improved while sleeping?

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] franciscofranco:
Indeed, I got that two times already...I'm still trying to figure out why, I got no idea so far.

As I thought, I'm testing it as it is too.
[Nexus S Android Development] frenccw:
Just don't try and make a phone call. I did that and the dialer was stuck and i couldn't toggle airplane mode.
[Nexus S Android Development] got2best:
I only got that 1 time I think.. but when i press gtalk it re-connects to data.. and starts working... Idk if maybe my phone was doing something else... just thought I might put this out there... I haven't had the problem of having to put it in airplane mode.
[Nexus S Android Development] ShadowVlican:
i'm also randomly losing my network connection
[Nexus S Android Development] franciscofranco:
Yes, I know, happened with me too, trying to find the culprit as we speak.
[Nexus S Android Development] Zorrich:
I had this problem too when i flashed anything greater than the November 8 release. It did not go away until i completely wipe phone and did a fresh install of oxygen, then flashed November 13 release. Haven't had the issue in two days since. Luck? Coincidence? Not sure. Will post if it returns. Figured I'd share my experience.
[Nexus S Android Development] got2best:
I apologize I guess I was just re-reporting a bug that was already known and being worked on..
[Nexus S Android Development] franciscofranco:
Thank you! I started to have the issue when I updated my phone to the latest Oxygen release, without full wiping my phone. If the problem persists after this new round of local testing I'll wipe this **** for good. Thanks for the input.
[Nexus S Android Development] Cybergr:
Franco happened to me only once on latest Oxygen 2.3.2 after a fresh install of both Rom + 13.11.2011 Kernel..I am using latest Oxygen for +, - 2 days now with your Kernel and had only 1 signal dump.It`s not a big deal for me but never happened me with one of ur kernels in the past!
[Nexus S Android Development] franciscofranco:
New testing version up to make sure the gsm/data loss problem is fixed.
[Nexus S Android Development] frenccw:
It's happening to me on NS Collabs 1.50. Did not flash any new roms or upgrades in between flashing kernels
[Nexus S Android Development] y3mita:
Franco, been using latest stable BFS kernel on a fresh install of Carbon Co2 by Jonathon Grigg and no reboots, no radio dumps, the only problem not really a problem is battery life is not that great! I still find NOV 09 build the best for battery life!
[Nexus S Android Development] waterface:
Hey guys, been away for a while. This thread is on FIRE! I have had good battery life with 13.11 all in all, around 16-18h average with medium-hard usage, but now I'm curious to test 24.10 again after ro_explorer's feedback. I have 25.10 but not 24.10 in my "collection". Anyone can please post a link to download 24.10?
[Nexus S Android Development] JmPTaz09:
I'm getting this problem lately and it doesn't seem to matter what kernel I'm on.. Franco, Ezekel and Kalimocha (stock CM7)... I am running CM7 nightlies but it seems to be happening on other roms as well, so who knows... it will just get stuck on the upward arrow like it's sending data but the down arrow won't come up... usually I wait it out and it will start working again, or else you'd have to reboot.

edit: just saw you posted about a test kernel to address the issue; hope you figure it out!
[Nexus S Android Development] al_madd:
Using cfs or bfs?
[Nexus S Android Development] y3mita:
Solution here? http://xdaforums.com/showpost.php?p=19387767&postcount=2224
[Nexus S Android Development] frenccw:
I am using CFS mate. Flashed latest test build will report if i find any oddities.
[Nexus S Android Development] Cybergr:
Flashed 16.11.11 test more than an hour ago..So far no problem with signal drops but to early for conclusions.Gonna report final thoughts tomorrow or if somethings strange happens.

This latest test has 15.11 colors fix too?
[Nexus S Android Development] Maximilian Mary:
Maybe it's not what you're flashing, but how. Try a different recovery, and/or a cold boot before and after flashing.
[Nexus S Android Development] mike216:
Please explain what you mean about a cold boot beforeand after

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] mike216:
Sorry

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] Cybergr:
If u start your device from a power off state it`s called - cold boot..Now in the other hand if u choose to restart your device via software, in our case Android OS it`s called - warm boot.

In other words if u flash a kernel for ex. via recovery don`t choose restart device, but hit on power off and then start it from the power on button.

---------- Post added at 07:20 AM ---------- Previous post was at 07:01 AM ----------

Forgot to say that in many cases of `cold boot` is preferred to remove the battery too..Like when you want to upgrade your PC for ex. u cut off the cable from the Power Supply Unit something similar happens when u update ur ROM or Kernel..u cut off any power contact and u start from 0.
[Nexus S Android Development] casca:
Hello Francisco (Poland,here we go!)

Just for the record, I'm running your 15.11 test release since yesterday untill now and I haven't found any GSM data connection loss on it.

Nevertheless, I'll flash 16.11 right away to help with the testing.

I'm also going to disable deep idle to check the battery behavior.

Regards

Nelson
[Nexus S Android Development] frenccw:
Another strange bug i've been encountering lately: Upon unlocking phone, all soft keys/touchscreen stops responding. Only hardware buttons work so i can only increase/decrease volume, lock/unlock phone and the screen is lit but not responsive.

Could be a touchwake bug but i havent heard anyone reporting it on ezekeel's thread. Anyone here ever experience this?
[Nexus S Android Development] Zorrich:
Think I jinxed myself, haha. Lost signal last night sometime while sleeping. Will try your test build and let you know.
[Nexus S Android Development] casca:
That one I haven't experienced. I've had a strange one also a few test kernels ago, but it was related with BLN, wiped cache + dalvik and flashed it again and it became ok though.
[Nexus S Android Development] thegtfusion:
Having bad battery life with 13 nov CFS kernel.

See in screenshot.. 10% in 45 minutes :O.

Im in oxygen 2.3.2
[Nexus S Android Development] casca:
I've disabled deep idle, and I actually think you guys are correct...it seems the phone is not draining so much battery while keeping in idle with the screen off.

so in resume, oxygen 2.3.2, test kernel 16.11, deep idle off, max freq on
[Nexus S Android Development] ro_explorer:
So .... long story short ... attached is the battery over the last 38 hours (and still 33% remaining) with a light+ usage. Kernel used: Oct 24th. This will be my reference benchmark.

I'm switching now to the latest available version (apparently nov 16th test) and I'll go with it for the next 24 hours or so with DEEP IDLE OFF.

Will report back soon :).
[Nexus S Android Development] roshga:
lol are you kidding?

your phone was awake with screen on for almost the whole 45 minutes, of course you'll lose 10% battery...

Using the phone - Reduce battery

Not using the phone - Reduse less battery.

seems like people here got so excited of the last improvements that they forgot that devices actually need battery to work..
[Nexus S Android Development] RonnieRuff:
I have quite a few Windows Certs and have been managing IT teams for 15 years. A cold boot and or disconnecting from power is not needed or recommended when upgrading Windows OSs.

I am not an Android dev at all and I have heard this a number of times. If Android restarts like Windows this practice is of no benefit. Surely does no harm.
[Nexus S Android Development] laidick:
Amazing battery

using kel miui 2.6.2

Franco 13 Nov

also, I was never been successfully live oc before. But somehow this version I can liveoc a little bit to 105% with all default voltage.

Using lazy 420-1050

Off deep idle

Off screen off Max frequency

Rock stable now,no signal loss, blazing fast, with medium phone usage for few hours.

Thanks fransco.
[Nexus S Android Development] waterface:
Could you, or anyone, please provide a link to download 24.10 kernel?

Thanks a lot in advance.
[Nexus S Android Development] ro_explorer:
:)

http://www.megaupload.com/?d=O815VQQW
[Nexus S Android Development] waterface:
Thanks! But it says 25.10. Is that the one?
[Nexus S Android Development] ro_explorer:
Yes. Nov24th release was generated as nov25 file. You can check the thread in the 25th page area.
[Nexus S Android Development] waterface:
Oh I see. I was lazier than ezekeel's governor, I didn't check.

Thanks a lot man
[Nexus S Android Development] franciscofranco:
Be aware, I don't support older versions.