Why is it that whenever I use a faux kernel my battery temp is at 52.70 fareheit.and when I use a bricked kernel my battery temperature is 77.18 fareheit.I have read and see that a lot of people that run bricked kernels are running battery temperatures of 32-40 fareheit.could it be because I running a bricked kernel on a sense Rom and there using a bricked kernel on a aosp,aokp,nonsense Rom.I don't understand I'm trying to run a bricked kernel at preferably lower temperatures.any help or information on this would be appreciated. Thanks...
Sent from my HTC Sensation 4G using xda app-developers app
Can you please share were did you find the information?
40 Fahrenheit is about 4.5 Celsius and you can have that battery temp when using your phone in a fridge LOL
77 Farenheit is 25 Celsius, which is normal for the battery
Hi I run bricked kernel, i never
Had a problem with overheating, ive also ran faux, tamcore, shebastion, none have ever over heated on me! IM not sure why your having problems overheating? Perhaps its your battery giving you trouble. Maybe look into that because the kernels never caused over heating. Hope this helps! Good luck
Sent from my Sensation using xda premium
I have had other members on her tell me that they run bricked kernels and.I have asked mote than one person what there battery temperatures usually run st and 3 different people told me that they are running bricked kernels and ones batt temp was 34 and another persons was 40 fareheit batt temp because at that time I was running a faux kernel and my batt temp was 52.70 fareheit.I know its not my battery because when I change right back to a faux kernel it goes back down to 52.70 fareheit.when I had Gingerbread 2.3.4 on my phone when I bought it new my battery temp was always 76.81 fareheit so I know my phones alright its not overheating I was just wondering how the heck those other people where getting there phones battery temp down to 34-42 fareheit with bricked kernels that all. Thanks...
Sent from my HTC Sensation 4G using xda app-developers app
I dont know but I do know I'm running bricked now and IM running cool temp. No overheating. However IM underclocked for battery saving. But even when I over clocked for performance it never ran hot on bricked.
Sent from my Sensation using xda premium
What temp is your battery temp?
Sent from my HTC Sensation 4G using xda app-developers app
i'm using faux and my battery temp always around 10 celsius. and i know that is wrong.
I use faux kernel since v7. The battery temps are between 8º - 19º Celsius in summer and lower in winter. This temperatures are with a sleep mobile, obviusly.
Possible wrong information feom the battery. Just think - you have 25 celsius in your room, yet battery has 4.5 - that's just nonsense.
Sent from my customized HTC Sensation with TTP 2
Faux always shows me temps below room temperature too.
Flash any other kernel and the temp goes up 30 degrees F. So there is some odd error in Faux for reading temp. Great kernels otherwise though!
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
Related
So I have Myns latest Rom and I was wondering about adding Setcpu to the Rom. My question is this. For those of you that have this rom, how is your battery life? Do you use Setcpu? Is it compatible with this rom? Should I leave it as is? I dont want to overclock, I just want to underclock when display is off to save battery. Any expert advice?
What kernel would you guys recommend? Again I dont want to make my phone faster, I just want decent battery life, and I know there are a couple of tweaks I can do. ( and yes I already know about the brightness, wifi etc)
Getting bad battery life too huh? I'm new to this rom and I'm trying out a couple combos. I have setcpu to underclock using smartass. I changed my kernal to one with more havs. I'll report my findings.
Sent from my PC36100 using XDA App
Newklearx3 said:
Getting bad battery life too huh? I'm new to this rom and I'm trying out a couple combos. I have setcpu to underclock using smartass. I changed my kernal to one with more havs. I'll report my findings.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
No I really havent gotten through a whole day with this Rom, so I cant say I have had bad battery life. I just wanted to know what you guys are doing and using out there.
Jess813 said:
No I really havent gotten through a whole day with this Rom, so I cant say I have had bad battery life. I just wanted to know what you guys are doing and using out there.
Click to expand...
Click to collapse
I haven't gone a whole day either. But I will today. I will let you know how my battery does.
Sent from my PC36100 using XDA App
Im using Netarchys 4.3.1 toastmod CFS HAVS nosbc and I can average 15hours with standard use, 24+ hours if i ignore my phone all together.
I use SetCPU and Juice Defender (it turns off data when my screen is off) and i easily get a day of battery life, my minimum is 12 hours and that is if I am constantly using it
I have been using Myn's 2.2 with the netarchy 4.3.1-cfs-havs-nosbc kernal for a few weeks. I have Setcpu profiles to overclock ondemand at 1152 until my battery gets to 30% then runs at 998 after. Also have it underclock at 245 when the screen is off. I can easily get a full day with several texts, a few hours of surfing, a few phone calls and maybe an hour of games (Angry Birds, Let's Golf). Usually plug it in at the end of the day with at least 20% battery left.
Just curious what everyone is getting for battery life on the gb Rom? seems like i have been getting about 11hours at the most and 9 hours normally on barely any talk time with the phone and little texting almost nothing cause im at work for 9 hours. Basically.from 6am to 5pm is all i can squeeze. Btw running the screen at the lowest brightness and even clocked the cpu at 800 mhz
Sent from my SGH-T959V using XDA App
Oh damn, I just keep seeing bad things about the new GB ROM (bricks and everything). :T I haven't flashed it myself yet, but with that minimal kind of use, I could've gotten over 24 hours on Bionix.
Not a pro here, but maybe you can try calibrating your battery?
bkoon1218 said:
Oh damn, I just keep seeing bad things about the new GB ROM (bricks and everything). :T I haven't flashed it myself yet, but with that minimal kind of use, I could've gotten over 24 hours on Bionix.
Not a pro here, but maybe you can try calibrating your battery?
Click to expand...
Click to collapse
Try to calibrate your battery. Stay away from flashing GB right now. It will screw your bootloader up for future reference. The bootloader in it is bunk.
I flashed it with open it works great i did notice it changes stock voltage on the cpu to 1325 which most likely caused the drain issue. I can get into recovery though.
Sent from my SGH-T959V using XDA App
I already flashed thru heimdall before the warning came out about bootloaders. So far it's running pretty good. I need an oc/uv kernel though cuz I noticed battery runs warm at times.
Sent from my SGH-T959V using XDA Premium App
Its running warm from the voltages used on the cpu in the kernel dl tagrak pay for it and changed the value of 1325 on the core voltage to 1275 stock or 1250 which i run at currently
Sent from my SGH-T959V using XDA App
Hello, I would just like to hear some opinions on what your kernel experience has been like. I would like to know about how performance and battery life have been, as well as any glitches or bugs you've seen with either kernel. Also I would like to know what you've clocked your processor to and with what means.
I will be using ARHD 4.1.3 so if you have used your kernel with this rom that will help a lot.
ps: I am aware that with Faux kernels you can use the Daemon Controller app to control your clock speed, but I was wondering what the best means of controlling the clock speed with Bricked is.
Post away!
lainemac said:
Hello, I would just like to hear some opinions on what your kernel experience has been like. I would like to know about how performance and battery life have been, as well as any glitches or bugs you've seen with either kernel. Also I would like to know what you've clocked your processor to and with what means.
I will be using ARHD 4.1.3 so if you have used your kernel with this rom that will help a lot.
ps: I am aware that with Faux kernels you can use the Daemon Controller app to control your clock speed, but I was wondering what the best means of controlling the clock speed with Bricked is.
Post away!
Click to expand...
Click to collapse
System tuner works very happily with Bricked.
faux is better
I like faux because:
1) Has, generally, more features
2) Works well with Daemon Controller--less resources on CPU/workload on batt than SystemTuner
does it help with the power button/screen flash issue?
I use bricked because faux kernals tend to make my phone extremely hot
sent from a guy living in a van down by the river
I would have to say Bricked because I have tried them all and as far as reliability and performance.
Sent from my HTC Sensation 4G using xda premium
Honestly? I think both kernels are excellent. Both devs are amazing at what they do and I've happily used both of their kernels in my wife's and my own Sensations.
My wife's Sensation has Faux 0.2.3r3, while mine has Bricked 1.5.
As for clock speed control, I generally stick with FauxClock to work with Faux's kernel. I use SetCPU and init.d scripts to control Bricked clock speed and voltage respectively. I'm just not a fan of System Tuner.
Both phones are set at 384/1188 wake and 192/432 sleep. I raise the clock on mine when I feel like playing some FPse.
I have used both bricked and faux kernels. Here are my observations: Faux is faster but has bad idle battery life. I actually get better awake battery life using faux. Bricked seems to be slower but I get amazing idle battery life.
I have used bricked 1.4r2 and faux 2.3b4, 2.3b16, 2.3r3, and 2.4b6.
Bricked had never steered me wrong. Been using shows kernels since I started with arhd. Faux kernels seem rushed and always in need of a fix. (just my opinion)
I just oc daemon to control my kernel.
I was using 0.91 for the longest time until I broke down and decided to try 1.4r and it is working beautifully. But try then both out. To each his own.
I think both kernels are great. But I think more developers use Bricked. Currently I use Bricked because it updates more often and I can download test builds.
Sent from my HTC Sensation Z710e using XDA App
I used faux kernel before (with ARHD 3.6.5) and bricked kernel right now. Both of them are good. And in my experience, idle battery consumption is slightly better in bricked kernel than faux. But they are not different a lot if you often turn on the lcd to use apps, games or other else.
i tested bricked faux and tiamat on the FpSE playstation emulator and running stock 1.188 mhz only tiamat played gran turismo smoothly using the "lagfree" governor, so i use tiamat now.
and in the benchmark id have to say bricked performed better that faux
In my experience, Bricked has been more stable (I had freezes with various Faux kernels) but assuming both are working 100%, Faux has been slightly faster while Bricked is better on battery life.
Will you guys swear at me a lot of I say that stock is the best so far? 2.3.5 I mean
Sent from my HTC Sensation Z710e using XDA App
I've been using bricked. Always works perfectly. Never had any issues.
Sent from my HTC Sensation Z710e with Beats Audio using xda premium
Faux's thread is gone and there is no faux's kernel for sensation any more.
yep, bummer...not sure why faux left the building!
faux is still there. It's the HTC Stock kernel in the developer section.
Sent from my HTC Sensation 4G using XDA App
iammer said:
I have used both bricked and faux kernels. Here are my observations: Faux is faster but has bad idle battery life. I actually get better awake battery life using faux. Bricked seems to be slower but I get amazing idle battery life.
I have used bricked 1.4r2 and faux 2.3b4, 2.3b16, 2.3r3, and 2.4b6.
Click to expand...
Click to collapse
This is exactly it. I've used both Faux 0.2.3r3 as well as 0.2.4 release; and Bricked v1.5.
Faux has worse idle battery life but better awake battery life. Bricked has better idle battery life but shorter awake battery life.
Hi, couple questions:
I recently flashed the newest miui rom with trinity kernel superwiped, wiped dalvik cache fixed permissions even followed instructions on first page about saving battery. im using set cpu 1118 -192 ondemand
1. been through 3 power cycles still only getting hardly 5 hours with heavy usage. i have everything turned off except mobile data. no rogue apps i dont play any games. could this be my radio?
2.i flashed newest firmware without cid (one of these users made one that you could flash without supercid flashed correctly however everytime i restart it stays on htc white screen and i have remove zip and reflash rom. what could this be?
3.ive done tons of research on keeping battery usage at a minimum yet i cant figure out whats eating my battery away. im nearly convinced its the firmware that i havent been able to get to the home screen. yes everyone says "no problem here" can someone help?
Sent from my MIUI.us Sensation 4G using xda premium
Souns like your rom and kernal arent playing well together. Did you use a custom kernel on the one that comes with the rom?
Also, are you ovrclcking the cpu 100% of the time? That happened to me just this morning. Somehow my cpu got set to max and the governor was keeping it at full speed at all times.
Sent from my Sensation using XDA App
i havent changed the kernel, i just left the trinity one that comes with the rom.
as far as the cpu im kinda confused i just set it to 1118 to 192 on setcpu. how do i know if its going at 100% and how would i turn that down? i appreciate your feedback
Sent from my MIUI.us Sensation 4G using xda premium
System Tuner is a free aspp that will show you the load on both cores.
Get that and go to the cpu tab. Watch it for a minute and see it either core is maxing out constantly. It should drop to min if you are you sitting there not doing anything.
The next step is seeing if you have a persistant app that chewing battery
Sent from my Sensation using XDA App
---------- Post added at 10:11 PM ---------- Previous post was at 09:57 PM ----------
Oh...and if you are maxing out a core constantly, check the governor. (Can be checked right from that CPU screen in System Tuner)
My problem this morning wasn't the kernel or ROM. It was the governor. For some reason the supposedly smart governor was maxing out the CPU constantly. I just switched to conservative as the governor and boom....battery drain when from 10% per hour this morning to 1% per hour the rest of the day.
Nice! Im familiar with system tuner but no one has ever put it like that for me. Thanks a bunch for your help bro i had a feeling those ondemand governors were kinda ify. i was thinking about putting the governor on powersave but it puts both clocks on the bare minimum and i wasnt sure if thats the safest thing to do.
Sent from my MIUI.us Sensation 4G using xda premium
I have to try this, the battery is horrible in my Sensation. I am using the Android Revolution HD™ 6.1.0 ROM so within the Daemon Controller I will try to set my Wake Gov to Conservative. Lets see what happens.
mj_techno said:
I have to try this, the battery is horrible in my Sensation. I am using the Android Revolution HD™ 6.1.0 ROM so within the Daemon Controller I will try to set my Wake Gov to Conservative. Lets see what happens.
Click to expand...
Click to collapse
Yea im still having problems the battery drains like crazy ive had it on conservative for a while 168-792 and its still draining hard. it puzzles me b/c i have an anker battery and im still barely pulling 5 hours
Sent from my MIUI.us Sensation 4G using xda premium
I'm running cm9 night lies with bricked kernel 3.0 v1.1 over locked to 1.782.my phone temp is 78 dregs.How high of temp is to high.the phones operating good.I updated cm9 earlier and before I was using a faux kernel over locking it to 1.728 and the phone temp was at 53 dregs.and when I updated my cm9 because it comes out with a new update everyday the rim would nit boot up with the faux kernel that U was using so U change d to a bricked.I even clears out and flashed the phone and reinstalled the faux kernel twice but it still would not work.any help would be much appreciate d.
Sent from my HTC Sensation using XDA
What's that the temperature of? The CPU? The outside case? Fahrenheit or Celsius?
Its the CPU Fahrenheit.
Sent from my HTC Sensation using XDA
If it doesnt reach 100F its no problem
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Yes, as said in post 4...unless you're playing a very demanding game, that can get the phone really hot.
DLittle2012 said:
I'm running cm9 night lies with bricked kernel 3.0 v1.1 over locked to 1.782.my phone temp is 78 dregs.How high of temp is to high.the phones operating good.I updated cm9 earlier and before I was using a faux kernel over locking it to 1.728 and the phone temp was at 53 dregs.and when I updated my cm9 because it comes out with a new update everyday the rim would nit boot up with the faux kernel that U was using so U change d to a bricked.I even clears out and flashed the phone and reinstalled the faux kernel twice but it still would not work.any help would be much appreciate d.
Sent from my HTC Sensation using XDA
Click to expand...
Click to collapse
Consider yourself lucky. No matter what rom/kernel/clockspeeds I use I get in the 40s with screen on, 60s when Web browsing and up to 70 when really stressed. It gets noticeably hot obviously. I'm inclined to think mines defective. All temps in Celsius. Yikes.