yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] faux123:
Geek Talk below:

Android has 2 types of power management and they are supposed to work together. Linux kernel has built-in power management, let's call it "traditional" for our case. Google then patched in their own power management on top of called early suspend/late resume.

traditional route:

suspend:

cpu idle -> PM suspend

resume:

cpu interrupt -> PM resume

Android route:

early suspend:

screen off -> early suspend -> cpu idle -> PM suspend

late resume:

cpu interrupt -> PM resume -> late resume -> screen On

In beta 9, I was trying to test the early suspend/late resume route ONLY, so I disabled traditional PM. In the final version, I have re-enabled traditional PM.

Tradional PM for our devices suspends the following:

SDCard, Memory (I am not sure this one is actually working), GPIO, Light Sensors

Android PM for our devices suspends the following:

GPUs (my 023 kernels only), MHL (the usb-hdmi thingy), HDMI chips, USB chips

The problem with current SelfKang Alpha9 is that something in the ROM is generating a "phatom" load which keeps activating the 2nd CPU with nothing to do (or in my r1 version, it keeps cpu0 @ max frequency for a while even though the load is well below 20%). So the traditional PM is NEVER activated (this can be confirmed by dmesg logs where you will NEVER see traditional PM log messages, ONLY my Early suspend/late resume messages). The re-enabled traditional PM is FIGHTING with whatever the ROM is doing thus generating a tug of war during screen off. This war is NOT free however, it will generate additional current draw for it. I was contemplating about NOT re-enable the traditional PM for CM builds, but the problem is I have NO IDEA when the next selfkang version will be out (since I will be taking a break from Sensation to catch up with my other projects) and if they fixed the ROM issue, then my kernel will not be optimal for that new version and I DON'T want to be tied based on CM7's own schedules (which is unknown). I have measure the additional current draw to be somewhere between 25~50ma more than before.

Hopefully, the next selfkang will fix the deep sleep issue.
[HTC Sensation] premkang:
Shockingly I understood all that on first reading, appreciate you taking time to explain.

Can I bother you with one further question, am I better using release kernel or beta 9 considering the current draw differences if I'm not having any other problems with the beta release?

Prem

:D
[HTC Sensation] Gillion:
Faux before you leave the sensation, Thanks for your work.
[HTC Sensation] Part Four:
Yes it is.
[HTC Sensation] Gillion:
The default kernel that comes with CM7/A9 has horrible battery life.

Period.

I switched from the default CM7/A9 kernel on my 4G unit to a faux 0.2.3 kernel.

With 0.2.3/B9 I get a decent battery drain and manage 12 hours easily. However, I also got 12 hours and more with my ARHD SENSE 3.0 ROM.

Frankly I should be getting more battery life from CM7 than a ARHD.

I updated my CM7/A9 to faux kernel 0.2.3.R1 and as expected battery life has fallen because of faux's previous detailed rational... so I reverted to the Beta 9 version...

Simply put the CM7 ROM itself must be worked on by the CM7 team.

I believe faux has done all he can. But you and I already know the lead CM7 maintainer for the Sensation device, kmobs, is disinterested right now... and I doubt the other "backup" maintainers have to time or the willingness.

We started with such a high back in September but somebody decided to let the helium out the balloon... sigh
[HTC Sensation] aNYthing24:
So if I understand correctly, beta 9 is best for battery life with the current Alpha of CM7?
[HTC Sensation] emanon:
I'm getting same battery with r1 and b9
[HTC Sensation] t0ny0:
Im afraid you are probably right about the downhill of cm pñ sensation..

I realized that a few days ago, so im thinking that its time for me to sell and get me the new nexus once its out..
[HTC Sensation] runderekrun:
This. A hundred times this. Never have got anything more than decent battery life on cm7. And that's if I don't turn on my phone.
[HTC Sensation] aNYthing24:
Yeah, I'm idling pretty well with r/r1.
[HTC Sensation] qiuness:
I just lost 50% in 8 Hours which is way more then i was getting with .20

I`ll try to reset the battery stats and see if that helps matters. If not, i`ll revert to .20 until CM work on their ROM

p.s: i`m watching fauxClock (just opened that and wifi, thats all) and i can see both Cores jumping from 192mhz to 1.56Ghz ever second. Also Faux Clock is getting superuser permissions every 2-3 Seconds.. Thats weird.
[HTC Sensation] Part Four:
When you follow up a statement with the word "period" spelled out, that's supposed to be the end of your statement. Period.
[HTC Sensation] Gillion:
LOL !!!

Good one.

Amen for flexibility.
[HTC Sensation] Part Four:
Doesn't look like you're running CM7 there.
[HTC Sensation] jabbermacy:
Use .072 or system tuner pro, .075 has huge issues; yeah, my battery life is really not great.

I _did_ have the 'android system' hogging resources before, but I also use Powermax -- when enabled (wifi/3g killed) it seems to settle down, then 'cell' takes the lead in power use. Is this 'system resource hog' issue related only to the radio???
[HTC Sensation] Vineares:
I think that's LunarUI theme.
[HTC Sensation] Vineares:
Getting some really good idle battery life with HylerSensation.
[HTC Sensation] aNYthing24:
Correct. It's CM7 with Lunar UI.
[HTC Sensation] Part Four:
You definitely need to calm down, because I'm getting reboots even when not UV'ing.
[HTC Sensation] faux123:
I wonder why some phones do not play well with JRCU...

BTW, don't go away just yet... I am building a NoHz version just for you.. check it out and give feedback... stay tuned...

Edit:

Here you go, NoHz RCU @ 1.78 GHz http://www.multiupload.com/VFP2KTX3TN Please try and give feedback.
[HTC Sensation] hev88:
Fast nohz is cool but i have to admit JRCU is really growing on me. My device has never had a problem with either but that being said thanks for the b!tch!n kernels :)
[HTC Sensation] Part Four:
Awesome, thank you my man. Will post feedback after some testing.
[HTC Sensation] sinisin:
So I was playing Modern Combat 2. Had cranked up the CPU to 1.78. Locked CPU1 online. It locked up, hard rebooted and then refused to boot up. Got stuck on CM boot screen. I'll also be trying the NoHz. Grr. Had to reflash everything. From scratch. My dumb ass deleted all my backups to make new ones and hadn't made them yet.
[HTC Sensation] Pvt WhoOkid:
Having such a great battery life on cm7 alpha 9 with this new kernel. :-) thank you!
[HTC Sensation] KlashbeN:
R1 seems to be working great on MIUI. no bootloops so far :)
[HTC Sensation] gs111:
I've been running all the betas up till now... I loaded R1 last night, but my battery drain was terrible (CM7-A9). Back to Faux-b9 kernel, and it went back to normal.
[HTC Sensation] Part Four:
NoHz is working great for me. No more rebooting. Thanks!
[HTC Sensation] faux123:
Cool,

SelfKang10 should be dropped anytime. Hopefully they fixed the PM issue on the ROM side.
[HTC Sensation] GideonX:
Faux, did you happen to bring this PM issue up to any of the CM7 maintainers?
[HTC Sensation] gol_n_dal:
I was going to ask the same thing, you beat me to it ;-)

For me it's CM7A9 and Faux 2.3b9 at the moment.

@Faux: Many thanks for the effort on Sensation and enjoy your Holiday to other Android Islands. It's been a nice Kernel progression from start to now. Hopefully at odd times you'll come back to visit the Sensation island.
[HTC Sensation] marcjw:
It's only been 6 hrs since I applied r1 on my alpha9 but so far the battery usage has been outstanding, just 6%. (I don't modify anything; I just drop it in.) Even though my use has been fairly light this morning I still think that number is better than any of the betas I used before this one.

Nice work Faux!
[HTC Sensation] MarkE08:
Switched Over to NoHz

Got another soft reset on r1-JRCU. Screen was off but I was SSH'd to my phone. I got the disconnected error message on putty and the phone showed the boot logo a couple seconds later.

Giving the NoHz a shot.

I'm using Faux's recommended settings via FauxClock .75.

Edit 1: So far so good! Not sure if this is related but HSPA+ and the data connection in general seem way more stable.
[HTC Sensation] Part Four:
Yeah. I don't know why, but my phone likes the NoHz kernel much more.
[HTC Sensation] Superfrag:
I flashed the 1.56Ghz kernel. When I went in CM Performance settings to change the governor to smartassv2, I only found the default governors. Is it not there, or do I have to flash another kernel?
[HTC Sensation] faux123:
SmartAssV2 is currently not compatible with aSMP dual core yet...
[HTC Sensation] jjdoctor:
....... Sorry wrong thread...
[HTC Sensation] faux123:
NoHz versions added to OP
[HTC Sensation] septix:
Any recommended settings for this, or same as the other?
[HTC Sensation] hompsar:
What are the differences between Joe and NoHz?

Avatar Fight: hompsar

Gamertag: hompsar

PSN: OGhomp
[HTC Sensation] faux123:
Check op for explanations. If you are happy with a version just stay with it. There are virtually no difference between them.
[HTC Sensation] sinisin:
Major use=major heat on 0.2.3 NoHz. Gonna try Thermal Patch. Never heated up like this on any previous kernels.

Sent from where ever I was when I posted this
[HTC Sensation] aNYthing24:
Does anyone get a slight lag scrolling through the app drawer time to time? Just wondering if it's only me. Using the on demand governor clocked at 1.08 GHz.
[HTC Sensation] hompsar:
I'm extremely satisfied with the Joe kernel RC1. If it ain't broke don't fix it.

Avatar Fight: hompsar

Gamertag: hompsar

PSN: OGhomp
[HTC Sensation] MarkE08:
I use FauxClock and everytime I get that laggy app drawer, I check FauxClock and notice the CPU control 'down clock' to the screen off settings. I fix it and presto-all is well again.

-Mark
[HTC Sensation] soggyflakes:
whats a safe undervolt to use? right now im set to 1.08/192 and voltage for 192 is at 850mv

whats the lowest i can go to to save as much battery as possible. Im on r1 1.56 btw..

i hope someone understands what im asking, i think i just made myself a little dumber after re reading but its late and i need to go to sleep
[HTC Sensation] faux123:
The safest undervolt value is -25mv (this one I can pretty much say for sure). Every phone is different, some can undervolt more than others, so only you can answer your own question ;)
[HTC Sensation] gol_n_dal:
Which version of FauxClock ? I had some issues with 0.7.5 and reverted back to 0.7.2. Seems to work for my environment.
[HTC Sensation] sp5it:
18mAh drop in 10hours with r2 on ARHD 4.1.5 in aeroplane mode.

Mike
[HTC Sensation] kboeckx:
Wrong thread?
[HTC Sensation] moshe22:
Lol
[HTC Sensation] qiuness:
alright... even with the latest R1 i had 50% battery drop in 2 hours so i switched to NoHz -> charged the phone to 99% -> deleted battery stats and now i`m at 95% after 2.5 Hours.

This seams fine, but i don't want to get my hopes up :)
[HTC Sensation] MarkE08:
0.75, if I remember correctly 0.72 kept asking for root permissions.
[HTC Sensation] JoeSzymkowicz:
TMOUS, kmobs CM7 a9, 10.14.9035.01_M radio. Getting bootloop with NoHz 2.3r1; running fine on JRCU 2.3r1.
[HTC Sensation] Vineares:
Tmous. Got reboots with jrcu with CM7 9 and hypersensation. Running fine now with nohz and hyper
[HTC Sensation] faux123:
So weird indeed! :rolleyes::eek::confused:
[HTC Sensation] Gillion:
Faux... I would love if you can give me some guidance here.

One of the problems I noticed with CM7 A9 is the constant on/off cycle of CPU CORE 1.

I have observed this happening even when I am using the conservative governor... and no apps opened from a cold reboot.

The tool I used to watch the processors switch on and off was System Tuner by 3C

I am using Faux kernel 0.2.3_R

Now I am in the process of trying an experiment that I wouldn't mind if other people try as long as you know how and tell me what happens on your end.

But please do so at you own risk.

I do not know what instabilities will arise from this.

The main objective of this experiment is to prevent CPU core 1 from running. This effectively runs the CPU as a single core device with only core 0 active irrespective of load or governor.

A reboot will restore normal operation as I have not been convinced this is script worthy as yet.

So far with this "trick" I am seeing my mA requirements fall even as low as 59mA

​

Step 1
Open Terminal and run the su command

Step 2
When your prompt changes from $ to # go to Step 3
(Please allow super user to have root access)

Step 3

echo "0" > /sys/devices/system/cpu/cpu1/online & chmod 444 /sys/devices/system/cpu/cpu1/online

Step 3 send a 0 (off) to the file named "online" this will keep CPU1 silent... but it will change again if left alone for too long... so I had to make the file read only.

When Online is made read only you prevent the kernel/rom from being able to write a 1 (on) to the file.

This process of making the file read only is done by changing its mode from 644 to 444

644 means RW R- R- (read write for the first block, read only for second and third)

444 means R- R- R- (read only, read only, read only.)

similarly

666 meand Rw RW RW (read write, read write, read write)

I hope this helps... as I finished typing this my current drain went down to 20mA.

I am partialy aware that the CM7 ROM has an issue in being inefficient in how it manages both cores... so bare with me... I am fairly new to this ROM moding/tweaking thing.
[HTC Sensation] faux123:
Yeah, I've been saying about this "phantom load" issue with CM7 A-9. I don't know the exact cause for this, but I do agree that this is one of the main causes of battery drain experienced by many users using the A-9.

Your experiment looks solid and I like your idea of changing permission to prevent further tweaking... The phone should work with your hack in place (albeit, you've effectively turned your phone into a single core phone). I am interested in your experiment and your result / analysis :D

Edit: Spelling corrected!
[HTC Sensation] Part Four:
I think you mean "phantom" load. Not "phatom."
[HTC Sensation] sinisin:
So even after I flashed thermal patch on 0.2.3 NoHz I was still getting major heat from processors under heavy use. Flashed 0.2.0 and no issue with heat at all. Hmm. Oh well. Still a faux kernel fan!

Sent from where ever I was when I posted this
[HTC Sensation] faux123:
Make sure thermald is actually running. Do a ps in terminal and look for /system/bin/thermald
[HTC Sensation] Vineares:
Stupid question I'm sure but would using a non-stock battery have something to do with the jrcu/nohz nonsense?
[HTC Sensation] Gillion:
This is my most recent current drain profile since I started the test.

​

I am curiously happy about the -40 mA drain....

The drain jumped to -95mA when I turned on wifi in order to upload these pics

Graphical profile

​

I am hoping this represents something positive and significant for the coders among you.

Please assist in shedding some light on a few things.

The cell standby and the phone idle process... the large percentage... is this good ?

(i am assuming it is)

THE BLUE LINE BELOW THE GRAPH SHOWS WHEN THE DEVICE IS AWAKE AND FOR ALL THOSE TIMES I HAVE THE SCREEN ON.

The device can be awake with screen off.
[HTC Sensation] faux123:
I have anker battery and stock battery. I have zero issues with jrcu and nohz. This is a mystery to me as well that an rcu system behaves differently with different phones running the same base ROM..
[HTC Sensation] sinisin:
Yeah its running.

Sent from where ever I was when I posted this
[HTC Sensation] Vineares:
When I get home I'll test jrcu with my stock battery for giggles. I use my 2 ankers for day to day use.
[HTC Sensation] Gillion:
@Faux : Your kernel is A10 ready right ? right ? Righhttt ?
[HTC Sensation] faux123:
Yeap... running it now... CPU1 is a little bit quieter than before still not as quiet as sense ROMs
[HTC Sensation] Superfrag:
Oh okay. Cause you mentioned it on the OP, and that got me confused.. :o
[HTC Sensation] faux123:
New InteliOnDemand governor with built-in profile is coming soon :D (I am running it right now :D )
[HTC Sensation] Gillion:
Is it possible that you can build an experimental kernel where one can

a. send a boot time command like in Linux from grub/

b. hard code the kernel to silence cpu core 1 ?

just for testing purposes ?

I am still gonna do my tests.
[HTC Sensation] ksnexusone:
This was brought up before but I didnt see any explanation of the difference between RCU and Fast Nohz.
[HTC Sensation] hev88:
First post :)
[HTC Sensation] sir*mez:
Please re-read the first post again.
[HTC Sensation] trail1091:
can we share ur joy tomorrow:D
[HTC Sensation] Gillion:
Faux it seems that your kernel goes up to full speed way more than it should on A10. I don't see why the CPU needs to scale up to 1.026GHz and stay there. I did the check on a fresh install no apps. Even second. Core is less chatty, First core likes to stay at full speed at all times using the ondemand gov. I switched to conservative and as expected it behaves. All it does is scale more slowly. Ondemand is very aggressive. I also shut down core 1 but core 0 wont scale low and stay put until needed. Hope ur new government scales nicely.
[HTC Sensation] mrg02d:
Reminds me of the government we have here in the USA. ;)

Aggressive, chatty, unnecessary.

EDIT:Faux, if we flash the modded thermal config. file, might we expect to see lower temperatures?

Matt
[HTC Sensation] korrel2008:
Faux i have only one question, you say youre releasing a new kernel soon, i hope you mean within a day or three bcause a kernel needs time to sattle down? So you can see how it behaves?
[HTC Sensation] mrg02d:
Hey faux, I just flashed the Fast Nohz 1.56Ghz kernel and am seeing my CPU go up to 1.78Ghz instead of 1.56Ghz...Woops?

Matt
[HTC Sensation] hanlence:
Nice, scored a new high in quadrant with 0.2.3r in A10

ROM: CM 7.1.0-SelfKANG10

Kernel: 0.2.3r (1.5GH) NoHz

Edit: ok, maybe the 1.78GHz issue boost the score.
[HTC Sensation] Part Four:
Quadrant isn't a good benchmark tool for our phones, and that's not a particularly high score anyway. Stick with CF Bench.
[HTC Sensation] mrg02d:
Its alright when you take the results to be relative. Thats what the benchmarks are for, anyways. If one setup maxed at say 3200 and then a new setup maxed at 3800, then its safe to say you saw an increase in performance.

Matt
[HTC Sensation] hanlence:
exactly. the highest i got with 0.2.0 is around 3300+, so, there is around 15% increased i believe.

i bet you agree that the CM7 is much faster than sense, and that is why we can see the score increases from 2200+ to 3300+ (both OC to 1.5Ghz)
[HTC Sensation] faux123:
Due to recent issues with battery drain for 023 kernels, I have moved up the time table for 024 Open Beta (I was going to take a vacation from sensation but I kept getting dragged back due to battery issues).

Remember, OPEN BETA is NOT for everyone and your FEEDBACK is very important to the rest of the kernel users, so please report as accurately as possible.

Treat the OPEN BETA as CM7 nightlies, which means I will accept reports of issues here, but I WILL NOT respond to any requests for features.

When reporting

ALWAYS state

: [ ROM: Alpha 10 ] [ kernel 024 build-01 ]!

So here it is:

1.56 GHz NoHz => http://www.multiupload.com/BP8NUGFEBQ <=

Version 0.2.4 (Beta, ETA Don't even ask..., Official CM7 Alpha2+)

< 01 >

NoHz RCU (for battery test)

Intelligent OnDemand Governor (battery saving CPU governor)

-- Built-in Screen Off profile (like SmartAss)

-- Built-in Thermal Management (like thermald) <== NOT YET implemented

-- Built-in Web Browsing detection <== NOT YET implemented

-- Allow tweaks of screen-off policies via sysfs interface <== NOT YET implemented

PLL clock training with higher frequencies for better stability (stability enhancements)
[HTC Sensation] bduvel:
Well i still have a screenshot of a browsermark of 100.811 points (more then iPad2 on iOS5 and Galaxy Nexus with ICS) with stockbrowser on Alpha 7.

Now i just got 76000 with faux kernel and 1500mhz, but atleast flash is working for me again (tho after leaving page it still kinda destroys stock browser)

Opera does indeed work better. thanks for tips

gonna try that one now ;) thanks!!
[HTC Sensation] JoeSzymkowicz:
I don't see the new governor in 2.4b1. Anyone else missing it?
[HTC Sensation] faux123:
It's just OnDemand heavily patched and made default. I didn't make it a separate name.
[HTC Sensation] marcjw:
My battery performance has been terrific for almost all of your alphas so I'm surprised to see this at the top of your list. But what the hell, I'm game. I'll get started with your new one tonight after work.
[HTC Sensation] Gillion:
Sorry we dragged you back in.

Yeah gonna test out your new kernel now.

But compared to the stock Bumblebee A10 kernel, you previous 0.2.3.R1 was stuck at full speed (1.026 GHz for me) almost all the time.

This love of full speed did not change when I "locked out" the second CPU core.

It will frequently drop the 192, but it simply wont stay even when the phone is practically fully idle.

Apparently the changes made to A10 have made 0.2.3 look like a bad behaving child (as you predicted when it came to the issue of Traditional PM versus Android PM)

If we could:

A. Run the on_demand governor to scale more appropriately

B. Get rid of the unnecessary Core #1 "pulse beat"

I think that would solve some serious power management issues.

Then again... im no kernel hacker... but I will try to help with my observations.

Now !

I'M OFF TO MY LAB WITH THE BETA 1 :D
[HTC Sensation] stardust240781:
[ ROM: Alpha 10 ] [ kernel 024 build-01 ]

I usually overclock with system tuner pro. with your new kernel the settings i made are not there after reboot. Either i check init.d or on boot. I have to do all settings again.

I'm afraid I can't test anymore today because I have to watch FC Bayern vs. SSC Napoli now ;-)
[HTC Sensation] kboeckx:
I'm flashing right now ... I've seen weird things with SelfKang A10 and kernel 0.23

We are getting there ... I can feel it.

Thx.
[HTC Sensation] aNYthing24:
Thanks for the continued support faux. Out of curiosity, what will the Built-in Web Browsing detection feature do when it's implemented?
[HTC Sensation] Gillion:
[ROM: CM7.1.0 A10] [Kernel: Faux 0.2.4 B1]

So far so good.

Flashed it 20 minutes ago... then left the phone alone and went to take a walk.

Came back around 5 minutes later and woke up the phone... to be pleasantly surprised by -20mA

I then went to SysTuner and observed the CPU behavior:

1. I observer a greater variety of the available lower frequencies during scaling. Kernel 0.2.3.R1 would jump from 192 to 1.026GHz in on leap... and often would stay,

2. This kernels stays at the lowest frequency more often. However it still likes to go to 1.026GHz often... I suspect that the sys tuner graphs may be the reason. Will try using fauxclock to watch cpu behavior as it doesn't draw graphs

3. I also observed the near total silence of the second core. It only activated once during the whole 5 minutes I stared at the screen. This i think is good.

Lets hope these observations are repeatable and gets better.
[HTC Sensation] DonJuan692006:
[ ROM: Alpha 10 ] [ kernel 024 build-01 ]

Watched the clocks with FauxClock for about 2 minutes and noticed CPU1 stayed clocked at 384 about 80% of the time even with CPU0 clocking 192.
[HTC Sensation] sir*mez:
I just noticed that. I have the same here.
[HTC Sensation] Part Four:
Same here. A bit off-topic but, hey faux, is Flash Player working for you?
[HTC Sensation] Gillion:
Just lock out cpu core 1

http://xdaforums.com/showpost.php?p=18959888&postcount=4702
[HTC Sensation] |ChauMein|:
Flash seems to be working for me. I've only tested on youtube though.
[HTC Sensation] Gillion:
I am beginning to think we don't need core 1. But I'm still testing. Fauxclock should say offline for core 1