yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] calvin150:
One issue

Hello -

First of all, great job on this kernel and also on getting so many updated releases out for people to test! They're coming so fast, there is no way I can get through the charge cycles to fully test the battery as I get itchy fingers for the next one!

One issue I am experiencing is that fairly frequently (i.e. perhaps 50% of the time) when I turn the screen on (particularly after it's been off for a while - but that may be coincidence), when I unlock the lock screen (default CM7 fancy one), the phone will freeze half way through the unlock animation and reboot.

Things I can tell you:

I thought initially this may be due to under volting but I've put this back to normal and it still happens.

I'm using HyperSensation rom (latest version)

I've cleared Cache and Dalvik Cache

I'm using Faux clock (0.75) now but same thing happens with System Tuner.

I have the CPU set to conservative and screen on 192/1188, screen off 192/384. I'm currently trying pushing these up to 384min for screen on and 192/756 for screen off as I'm wondering if this is the issue. If this resolves it I'll let you know.
[HTC Sensation] marcjw:
No where in your post did you mention what version you are running. Fyi...
[HTC Sensation] faux123:
If no issues remain for B7... I will consider it as final for AOSP.... I am getting amazing battery drain myself... avg 25~50ma draw. It can definitely last over 24 or more hours with normal use with these kind of drain :D

BTW, once 023 kernel is released, I WILL TAKE A VACATION from SENSATION and catch up with my other projects. You guys have been spoiled by me :D
[HTC Sensation] emanon:
Try changing the governor to ondemand.

\Regards,
[HTC Sensation] calvin150:
Good point my mistake - I'm running beta 7 at the moment but have experienced this at least on betas 4,5,6 and 7.
[HTC Sensation] hev88:
It has my vote. Moderate use for about 3 hours and im at 98%.

Kernel is legen...

wait for it...

dary.

Legendary! :)
[HTC Sensation] scm_crash:
I'm giving it a try right now... Just booted B7 right now.
[HTC Sensation] Bluewall:
I can't get this low mA you guys have...always like 80mA for the best when screen off... but more often like 100 mA

MIUI with the beta 7, screen off 192-384 and UV to -100mv :D
[HTC Sensation] ldelossa.ld:
how is your battery life? I'm nervous to go that far down, but i will if it's a big improvement
[HTC Sensation] Bluewall:
I have weird battery life lol

I don't touch so much my phone when i work, always in standby. Then after, when my work day is finish it's like about 90%-85% So use it, music to go home, checking twitter, facebook etc and at this moment, battery drop SO fast to like 65-60%
[HTC Sensation] aNYthing24:
7 has been pretty smooth so far. Nice work.
[HTC Sensation] hompsar:
Using newest beta. Undervolt -100. 192/384 and 192/1064. Seems very nice. Time will tell.

Avatar Fight: hompsar

Gamertag: hompsar

PSN: OGhomp
[HTC Sensation] scm_crash:
OK... Been running B7 on Alpha 9 with no problems at all. Not one force close, not one reboot! Woot!

I'm also running it on Chainfire 3D. Graphics are really smooth. Everything is VERY responsive. Just for S&G I tested it with and without Chainfire 3D using CF-bench and got much better results with CF3D. Aside from that, I'd say this is a total winner.

Running the GPU I/O Fraction at 50 OnDemand.

Voltage Control at -25mv

Screen On at 1.566Ghz/192MHz, OnDemand.

Screen Off at 310MHz/192

Anything I can do to optimize anything or am I about as good as it gets?

Edit: Just changed my CPU Screen on to 1026/384.
[HTC Sensation] adclem:
Very good results, 11 hours of moderate use and still at 66%.

Settings are 1026/384, 756/192, -75 and 50
[HTC Sensation] Spr33y:
Can anyone tell me how to change GPU I/O Fraction? I can't find the init file that faux mentioned a ton of pages back.

Thanks in advance!
[HTC Sensation] scm_crash:
If you're using FauxClock, you'll be able to slide the screen left and right... Slide it right 2 screens.
[HTC Sensation] Spr33y:
Wow.. did not know FauxClock had different screens. Fail. Thanks!
[HTC Sensation] aNYthing24:
Sigh...phone just died randomly with beta 7...had to do a battery pull. I don't know what's going on.
[HTC Sensation] faux123:
Doh... so close... :(
[HTC Sensation] adclem:
14 hours and still at 40%, awesome kernel faux!!
[HTC Sensation] hompsar:
I've been on 63% for almost 2 hours now.

Avatar Fight: hompsar

Gamertag: hompsar

PSN: OGhomp
[HTC Sensation] emanon:
Man I haven had a single reboot issue with beta7. are you sure it is related to kernel. I'm using fauxclock and all faux's setting except my screen on max 1566 and using ondemand. beta7 is been very smooth and good battery too...

\Regards,
[HTC Sensation] aNYthing24:
I don't know. Last alpha of CM7, beta 7 of 0.2.3, and I use System Tuner to manage my CPU settings. 1.08 GHz/192 MHz, uV of -75, but it hasn't caused any stability issues. It only happened once with this version so I'll see if it happens again. Otherwise the kernel's been great.
[HTC Sensation] emanon:
sometimes too much undervolt will cause it to reboot. try changing the min 192 voltage to 12.5 or 25 higher. that worked for me previously might help in your case.

\Regards,
[HTC Sensation] aNYthing24:
I left the 192 MHz voltage at 812.5 mV. And my issue isn't rebooting. The phone just turned off and wouldn't turn on until I did a battery pull.
[HTC Sensation] Smokuevo:
Wheres fauxclock? Sorry?
[HTC Sensation] geoffcorey:
Google is your friend...
[HTC Sensation] MarkE08:
So Far So Good!

Other than the occasional FC with FauxClock, beta7 has been solid. Great job Faux123!!!111

aNYthing24, my NookColor had the SoD (Sleep of Death) problem. I was only able to solve it after doing a factory reset, reinstalling CM7 and starting from scratch (not using backups). I'm not sure if this is applicable in your case, just thought I'd throw it out there :)

MarkE
[HTC Sensation] faux123:
I will let beta 7 simmer a bit before calling it final.. just to make sure aNYthing24 is an isolated case .... :cool:
[HTC Sensation] kboeckx:
B7 is running ok here but B3 was in my opinion better.
[HTC Sensation] Splder:
so i set GPU I/O fraction to 50

but i have no clue what GPU I/O fraction is :P

could someone explain to me what it is and by setting it to 50 what iv done :P

my current settings are

ondemand

when screen on max:1350 min:192

when screen off max:310 min:192

global voltage -100mV

ondemand GPU I/O fraction 50
[HTC Sensation] gol_n_dal:
Faux,

Did you change the lower voltage levels of the Kernel. Mine is running at 800000 mV (-100 mV) for 192 to 432. The previous low was 812500 mV and it wouldn't go below that.

Saying that it's working fine for me, admittedly I'm UC'd a fair amount, I'll crank it right up and check the various Benchmark tools. Sure I have done this with no issues but I'll check again. I might just be a luck one though on the UV. Performance isn't up to others though (EDIT: running the same ROM/Kernel). Oh well swings and roundabouts.

On a side note, I had to go back to Fauxclock 0.7.2 as 0.7.5 didn't seem to UV my system, can't remember which kernel I tried this with :-(( Possibility I screwed up the Fauxclock install though.

---------- Post added at 11:05 AM ---------- Previous post was at 10:48 AM ----------

Faux,

One quick question:

Is it the Kernel that controls when the phone switches off based on the battery mV that or is it at a lower level in the phone ? Or even at a higher level, e.g. ROM.

Any thoughts, if not NP.
[HTC Sensation] RellikZephyr:
I'm using System Tuner, and I can't seem to find where I can change Gpu I/O setting. Am I missing something? Or does it not have it?

Thanks

Rellikzephyr
[HTC Sensation] gol_n_dal:
Use Fauxclock:

http://rootzwiki.com/showthread.php?5315-APP-0.7.5-BETA-Snapdragon-Dual-Core-OC-Control

I'm using 0.7.2. Just side-swipe the panel to get the UV and GPU screens.
[HTC Sensation] gs111:
I had a random reboot with b7 last night. I had it undervolted to -. 50, so I brought it closer to stock.... We'll see what happens today.
[HTC Sensation] gs111:
Actually, I should add the good news to this...

Battery life was great!

- 9am - 100% battery, off charger.

- Till 4:30pm... wifi, some browsing, 2 calls.

- 4:30-5 on car charger, some navigation and podcast listening. Didn't gain much on percentage.

- for the evening, games, navigation, 90 minute movie. Lots of browsing.

- 11pm - back on charger, and phone was at 11%.

Overall, I thought that was great battery life, much longer than I would have seen with stock cm7 kernel.
[HTC Sensation] MarkE08:
Same here

I had a soft-reboot occur last night as well. I was switching between apps (K9 mail, battery widget, and the browser I think) very quickly and the screen became unresponsive. I tried to bring down the notification bar and it didn't respond. About 10 seconds later my boot screen came up and I was back to the lock screen in like 20 seconds (love the new CM7 boot times). I wasn't able to grab a logcat but here are my settings:

CM7.1 Alpha9

Faux123's kernel 0.23b7

FauxClock v0.75 192/1.088 ondemand & 192/310 off screen

Stock volts & GPU IO @ 50 ondemand.

I am trying +12.5mV to see if that stabilizes things. If that doesn't help, I'll try and isolate the problem and report back.

-Mark
[HTC Sensation] septix:
Can some one upload fauxclock. apk to mediafire? Keep getting a .htm file when downloading.
[HTC Sensation] MarkE08:
I had the same issue when downloading from my phone. I verified the file size in astro (133.75K), added the '.apk' extension to the file name, clicked it again, open with app installer and installed :)

-Mark
[HTC Sensation] mrg02d:
I have found that my phone becomes extremely unstable whenever I let fauxclock control things.

Also, I was having random freezes when UVing. I no longer UV and no longer have screen freezes.

I HIGHLY doubt that UV by some 50 MILLIVOLTS (not VOLTS, but 1/1000 volts) is going to help with battery life and heating.

I have tried -75mV for days and see no better (or worse) battery life or solution to heating.

Think about it...Current times voltage = power. 1V times 1000mA = 1Watt.

We are talking about 100mV *250mA = 0.025W of power saved. Thats nothing at all. Certainly not worth destabilizing your phone over. I believe my freezes were from UVing, and nothing else. So for those that like to push it, and are UVing by 100mV, you would only be saving 0.025W if drawing 250mA of current. (About the typical draw for simple apps) Even going nuts and drawing 1A (1000mA) only sees a difference of 0.1W

Someone explain the logic in UVing...My background is in electrical engineering, so I may be missing something that is related to programming or software.

EDIT: I want to make sure that people dont take this the wrong way. I am not trying to step on anyone's toes here. I just feel, from my 1 dimensional perspective, that UVing may be headed down the same path as auto task killers. If anyone has real data to back up the benefits of UVing...Im always up for a good read!

Matt
[HTC Sensation] Gillion:
The concept of under-volting and under-clocking works in tandem.

The objective is to sparingly use the mAh/runtime of the battery especially during standby

You need to calculate in terms of watt hours or amp hours... and you will see that collectively, (conservation of energy) that running your CPU/GPU and other phone systems a little bit under may in fact save some power over a 6 - 24 hour period.

Fact is... since I started using faux kernels + under volting and unde rclocking instead of stock, I get 12 to 17 hours run time as opposed to the stock times of 6 to 8 hours respectively.

That is to say... for EVERY HOUR that I collectively use less power... even if it is tiny... on paper... contributes to the battery lasting longer.
[HTC Sensation] kboeckx:
B8

Faux,

Will try B8 today ...

How do you get your amperage so low ? I'm not getting any lower than 50mA
[HTC Sensation] faux123:
When you load my B8, it will idle @ those amperage or lower.. ;) No additional gimmicks required.. just use it normally.
[HTC Sensation] septix:
faux, thanks for the awesome job. Really love your work! Keep it up!
[HTC Sensation] c19932:
faux! before you release the final 023 version, could you allow the lowest CPU voltages to be lowered? (around 725mV). I understand that some other people can not run at such low voltages, but mine can. you can always set the default to higher and let people like me experiment with lower voltages :) please consider, thanks
[HTC Sensation] mrg02d:
My CPU settings dont stick after a reboot. Is this a kernel, or CM7 ROM issue? Yes, I clicked the set on boot box. ;) (Ive set settings in both cpu master and CM7 cpu settings.)

Matt
[HTC Sensation] farfromovin:
Running 1.78GHz 0.1.2 on CM7 Alpha and it's super fast, hasn't crashed yet but it's only been about 3 hours...
[HTC Sensation] BrokenWall:
Faux123, my test you gave me has been running stable the entire time since I flashed it last night or early early this morning.

min is 192 and max is 1780 as default with ondemand, been great
[HTC Sensation] faux123:
Thanks for the feedback bro. Not all phones were created equal :( You, myself and a few others can run perfectly @ 1.782, but from the responses I got, it seemed majority cannot. I have created a compromise, lowering the clock by 2 steps to 1.67 GHz but boosted its L2 Cache frequencies to compensate for the lower CPU clock. Now looks like everyone is able to use the new middle version.

Now with OC issues out of the way, I can look at other items.

Just a general info dump regarding CM7:

CM7 itself is based on android 2.3.5, but the binary blobs (HTC proprietary libs) are still based on the original 2.3.3 ROM base. This is the BEAUTY of CM7, they are able to use older vendor binary blobs and still able to bring you the latest, greatest AOSP experience.
[HTC Sensation] mrg02d:
Hey guys, I noticed something strange...

I am on CM7 with fauxs 1.6Ghz cm7 kernel. I ran quadrant several times with cpu set to 1.6Ghz performance. I got a steady 3300+

I then went down to 1.5Ghz Ondemand and got a 3600+?!

Seems to me that the scores should go DOWN and not UP?

EDIT: I know all too well about quadrants BS, but this has never happened to me before...

Matt
[HTC Sensation] jacksparr0w:
Hi Matt, I would say you have nothing to worry about. As you said this is most likely just another form of quadrant BS. Try using CF-bench this gives consistent results.

Also CF-bench supports dual core and from what I have read quadrant does not, or if it does it is not optimized.
[HTC Sensation] mrg02d:
Yeap, CF bench gives me a constant 7035+ with 1.5Ghz and Ondemand, and a 7300 with 1.6Ghz Ondemand. That beats the SGS2 with plenty! Even stock frequency beats the SGS2. :D

Im sure the SGS2 people are planning a counter-strike as we all speak..;)

Matt
[HTC Sensation] jacksparr0w:
Hahaha they just may be doing that, I think I will sneek on the other side of the fence real quick to see what is brewing. :D
[HTC Sensation] jlevy73:
I will say that with CM7 and Faux's new kernel the Sensation is definitely flying. However, benchmark wise, the SGS2 wins and does so handily (I have both so I know). At 1.6ghz, CF-Bench is 8790 on my SGS2. At 1.782ghz, CF-Bench on my Sensation is 7920.

Sorry, back on-topic :)
[HTC Sensation] lightforce:
cant run 1.78 at all constant crashing. Trying 1.67 now
[HTC Sensation] Shaquiel Harris:
Meh, i don't want to oc right now, kills battery usually but your kernels are good. Ill flash and just downclock to 1ghz.
[HTC Sensation] Sammydr10:
Do these kernels come AUTOMATICALLY OverClocked???

If so, how do i get back to StockClock running the kernel?
[HTC Sensation] mrg02d:
Cpu master.
[HTC Sensation] kazam13:
Revised( 2nd shot reportings).

ROM- CM7

@1.67 Ghz

Tweeks- None other then Faux123

CF-overall 7316 (first time I seen 1674 MHz following results).

Quadrant 3433

Linpack- 87.00 Avg out of 5 consistent runs.

AnTutu- 6028 out of 1 run.

No issues with lag/FC.

Thanks Faux123.
[HTC Sensation] raycaster3:
+1! Thank goodness we have ppl like you to break it down for us and make things simple to comprehend. Knowledge is definitely POWER!

Just a general info dump regarding CM7:

CM7 itself is based on android 2.3.5, but the binary blobs (HTC proprietary libs) are still based on the original 2.3.3 ROM base. This is the BEAUTY of CM7, they are able to use older vendor binary blobs and still able to bring you the latest, greatest AOSP experience.[/QUOTE]

Sent from my HTC Pyramid
[HTC Sensation] BrokenWall:
I know this is nice. I would love if I could get a 1.8Ghz core, OC GPU, 1.6Ghz L2, upped bus speed, and maybe a RAM bump

I think my phone could run it fine.
[HTC Sensation] drewtang:
I am noticing a little bit of wake lag on the new kernel, not using any OC apps, no settings changed...
[HTC Sensation] jassycliq:
Thanks so much Faux123 :D Your kernels are awesome :D

I've been running your Sensation kernels since they came out and am pleased with the battery life and performance of them.

I just want to thank you for your dedication and hard work you pour into your kernels, you can really tell the difference from other kernels.
[HTC Sensation] faux123:
Wake lag is a CM issue ;)
[HTC Sensation] jlevy73:
I like the sound of this kernel. My phone also doesn't have issues at the higher clock speed. An increase in bus speed would be nice. Where would you get the extra RAM from, the GPU? That's really the only place I can think of grabbing it since 128MB is dedicated. However, SGS2 devs tried taking some of the RAM from the GPU and started seeing issues, especially the camera and camcorder. Even as little as 32MB killed 1080P recording although 720P still worked.
[HTC Sensation] emanon:
Thanks for B8 update, installing now...

\

EDIT: WOW better with every beta, this one seems smooth also and battery is awesome... Thanks...
[HTC Sensation] kristofpetho:
Faux, excellent work - as always. Can you tell me what settings you use with Current Widget? My log show usage around 100-150 mAh when idling...

Thanks

Edit: nevermind... Now, with beta 8 I am also getting as low as -18mA!!!! WOW!!! :eek:
[HTC Sensation] mrg02d:
Not exactly...

Now here is how semiconductors work....

To turn on a transistor (either a MOSFET or a BJT) you need current. Current either charges the capacitance in a MOSFET to the point that the MOSFET turns on, or current turns on a BJT via its base. So, the faster that we try to turn on and off a transistor, the more current we need.

Frequency is what we ought to be focusing on, not UVing the processor. Higher frequencies will require more current to turn on the transistors that make up the processor.

So you guys know, Ive had my standby current down to 4mA before. And I DONT UV at all! What I do is keep my data turned off when near WIFI and keep my GPS off when not in use.

UVing is NOT the answer. It cannot be, unless you can do so by VOLTS. Higher frequency will require more current to turn on and off the transistors faster. I have first hand experience with this and power electronics.

A combo of lower frequency and control over what is running will fix your battery issues.

Matt
[HTC Sensation] atlp99:
To those who are getting soft reboots or black screens locking up with this kernal on the CM7 alpha 9, did you try a9 with the stock kernal?

I have had issues with both soft rebooting and black screen lock ups on a9 on the stock kernal. Especially when running GPS navigation (in addition to the phone heating up), I was wondering if this kernal would help these issues.
[HTC Sensation] gs111:
I've run recent CM7 alphas with different kernels... I've gotten reboots with Tiamat kernel, and with the 0.2.3 beta kernels. I had NO reboots with the stock kernel, and also none with the standard v0.2.0 faux kernel.

I've used the stock kernel only minimally though...

With v0.2.3 beta7, I've only had the one reboot. I've used the phone all day today without any issues.
[HTC Sensation] scm_crash:
Wait... You mean don't use FauxClock to undervolt?

BTW, so far so good. Still no FCs or crashes. No reboots or anything. And it was able to make it through the night without freezing and woke me up at 6am like it should. (Sounds stupid, but I had a lot of issues with ARHD and making it through the night.)

When the screen is off, the battery lasts forever. When the screen is on, though, battery drops quickly. I'll try B8 as soon as I get off the phone. :)
[HTC Sensation] atlp99:
I have stuck to the stock kernals so far and Alpha 7 is just about perfect for me, but a8 was a little flaky and a9 is down right unusable (I need GPS navigation about once a month) GPS locks the phone up with a black screen requiring a battery pull to restart after about 10-15 min of use.

The phone also gets hotter than it has ever gotten before when this happens so it might be an over heating issue, which got me thinking about this kernal.
[HTC Sensation] kboeckx:
Follow this procedure to flash kernels:

Before flashing the new kernel:

* Wipe Cache

* Wipe dalvik cache (in advanced options on recovery menu)

Flash your favorite kernel

After flashing the new kernel:

* Fix permissions (in advanced options on recovery menu)

Then reboot and enjoy.

I never had any issue when following this procedure.
[HTC Sensation] cstark27:
B8 stays "running' 100%. Didn't monitor clocks...didn't see any apps with high CPU or high sensor usage. Also, in idle with Pandora running, it would only get to ~-230mv. Up to -14 with nothing running. I went back to b7 for now. Down to -70mv with Pandora running, and not staying 100% running.

Cwr 5.0.2.0

Hypersensation v0.5f

0173 ril

10.14.9035 radio
[HTC Sensation] Fihlvein:
It is also worth checking logcat if vm heap size is causing soft reboots. Mine did, had to increase from 32M to 48M. Also many other CM7 phones recently changed default to 48M.

Sent from my CM7 powered HTC Sensation. Typos possible.
[HTC Sensation] marcjw:
Was running alpha9 with b7 kernel for the past couple days and everything, especially battery, was terrific. Hoping b8 is as well. d/ling now.

---------- Post added at 05:12 PM ---------- Previous post was at 05:03 PM ----------

Never had to fix permissions. The rest of the advice is spot on.
[HTC Sensation] scm_crash:
On B8 Alpha 9...

Is this possible? Charged to 100%, then unplugged the phone and made a 20 min phone call. Been off the charger for 35 minutes and the battery still says 100%.

:confused:

Does this mean I need to run the battery all the way down? Or is the battery life really that good?
[HTC Sensation] scm_crash:
Here's a screen shot.
[HTC Sensation] Gillion:
So your saying my longer run times are wholly due to my under-clocking to 1.02Ghz ?

I want to try running at 800Mhz... but i run sense roms... when i do... one word LAG !!!!

:p

Only so low and no more i guess
[HTC Sensation] aNYthing24:
No problems with beta 8 so far.
[HTC Sensation] faux123:
Found a few coding derps... ugh... need more caffeine!
[HTC Sensation] aNYthing24:
Haha, I'm glad you said that. Phone just randomly rebooted when I was scrolling through my apps.
[HTC Sensation] scm_crash:
Ahhhh... Coding derps... The difference between a ; and a : make a world of difference. :D

I don't know how to code at the level of a kernel, but I'm a web developer, and I can tell you that coding derps and the ones that piss you off the most... 2 letters in a variable name being switched, or forgetting to terminate a line, or (my favorite) using the wrong array index.

Either way, I still haven't run into any issues on b8.
[HTC Sensation] faux123:
Looks very promising :D

Sometimes you get so caught up in 1 particular area of your code, you overlook the obvious :( I kept looking at the suspend/resume relationships, so instead of looking for the driver architecture flaws, I took the device architecture design for granted and assumed it was fine.

After looking at it for 2 straight days, I couldn't find why the suspend/resume code didn't work... Then I took a break this afternoon and looked at it from a fresh perspective and the driver architectural flaw was immediately obvious... :(

I have made the changes and reviewed my logic again.. looks good so far... I will test it internally for a while before I release as Open Beta...