Related
ive read that we arent suppose to use set cpu on these new roms because htc power manager is built in. im using damage 2.0.7.2 . where is this power manager at i cant find it?, i know duh, what am i missing is it possible to change it like set cpu?
this guys running set cpu on a nexus claims 50% battery after 13 hours of heavy use
http://htc-phones.net/tag/power-manager
so can set cpu be used on these new roms or not someone with some brains tell me the deal once and for all please thanks
if i'm not mistaken.. htc power manager is only in sense roms.
HTC's PM is integrated in to the kernel, it's not an application that you run... which is why it works better. The only 2.1 rom out there that would even be capable of turning off HTC's PM would be Fresh Toast (well now darch's new one too) but we left it on in Fresh Toast for the time being because it works better. The only benefit to setcpu is if the phone is overclocked because it allows you to manually throttle it down if you prefer. New version of Fresh Toast will have an adjustable overclock so setcpu will actually be beneficial in that release when it comes.
flipzmode said:
HTC's PM is integrated in to the kernel, it's not an application that you run... which is why it works better. The only 2.1 rom out there that would even be capable of turning off HTC's PM would be Fresh Toast (well now darch's new one too) but we left it on in Fresh Toast for the time being because it works better. The only benefit to setcpu is if the phone is overclocked because it allows you to manually throttle it down if you prefer. New version of Fresh Toast will have an adjustable overclock so setcpu will actually be beneficial in that release when it comes.
Click to expand...
Click to collapse
ok thank you for that clarification.... cant wait for the new fresh toast
Bad--Dog said:
this guys running set cpu on a nexus claims 50% battery after 13 hours of heavy use
Click to expand...
Click to collapse
dude thats a fake base on my experience .. yea it dose help but not 13 hr and only 50% battery... my phone right now it say its almost full and its on battery for 1d 1h 39m. but it was on charger most of the day because i was home and it still says 1d 1h 39min on batt...... idk why it say that but if you need a pic or a video ill show you what mine say.....
but like i said it helps having set cpu and all the apps he states but not like he says ... come on 13h life and only 50% batt ... maybe he has a extended batt..
Meaning, does the battery life take a dip when you overclock to 1.5ghz. Does it get any hotter? Is heat an issue at all on this thing? Also, any performance or battery changes from installing the tiamet kernel itself? I'm in the wifi xoom btw.
Strangely enough battery life seems to be about the same. Heat has not been an issue mainly due to having the dual core, however its something you always want to keep an eye on.
Battery life is affected most by the screen. Screen> Network connections > CPU > RAM
There was a thread that someone made a while back about the things that affected battery life the most. If I can find It ill send it your way. After seeing the charts I figured Id try changing some settings.
things I did:
1. Set my max cpu freq to 1.19 min to 488 same for all my cpu tunner profiles ( I wanted to have my phone running the same all the time)
2. Lower'd my screen settings. I didnt need a pocket flashlight EVERYTIME I unlocked my phone.
3. Turned off un needed network connections. Its not hard to turn them back on when you need them.
4. I then looked for things that were running but were not needed by anything ( google maps are used by a few apps so dont disable it haha) I used Uninstaller for root users to get rid of some things.
After all these steps my battery life went WAY up. I have been doing the same thing on my Xoom now and my batt lasts the same at 1.5 as it did at 1.
I still get VERY respectable battery life at 1.5ghz, I can easily get through the day with normal usage. Yesterday night in fact, I left the house with maybe 75% battery life, used my tablet quite a lot throughout the evening(left the house around 9, went to sleep around 1am) and used it all morning basically constantly from 7am to around noon and came home with 9% battery left.
No problems here either. Woke up around 8:30 yesterday and used it all day sometimes pretty heavy. Finally had to plug it in around 6:30. I'm home all day with a broken hip and femur, so I've been putting it through the paces. Running @ 1.5ghz with interactive gov.
Chris
+1 on 1.5GHz having little effect on battery life. I didn't have to change anything else, either.
thats all great to hear! I suppose ill start looking into rooting my wifi xoom tomorrow then. Thanks for the help!
Im very happy with the battery life on this thing. I expected 4 hours max after a few weeks of use/charges. I never thought that it would keep up with anything Apple, Lets face it.. Apple knows how to make stuff run forever. But I was plesently suprised. Xoom +1000
yeah, the battery is good, but i won't know any damage to the cpu when overclocked ?
I wouldn't worry about any CPU damage- too many people have reported success (and no reports of failure).
Anyone else notice with the tiamat kernel that their xoom becomes very unstable overclocked at 1.5 using setCPU? Mine was essentially a soft brick at 1.5 constant rebooting and never able get pass the unlock screen, I had to rewipe with bootloader. I can do 1.2 no problem but don't even want to try going higher.
All of our chips have variations, so the overclock isn't universally guaranteed. That being said, I've been using the Tiamat kernel @1.5GHz since it was released with no problems.
Should have stated that mine is the wifi model, but yea thanks for info.
Here was that post I was looking for on this stuff. http://forum.xda-developers.com/forumdisplay.php?f=946
OK, since up to now few custom kernels have been released for Gingerbread, much of it due to fear of having to deal with the same stuff gtg465x has had to deal with for Infusion 2.0, I've had enough people ask what kernel I'm running to decide I'll post a compiled binary.
This kernel is my daily driver, it is what I have used for the past few days. I am posting it as-is with no support given. Flash it at your own risk, the only endorsement I give it is that I'm happy with its current state.
I'm on business travel at the moment so don't have time to do any support. Don't PM me with questions on how to flash this or bug reports. If you don't know how to flash a backup made with SGS Kernel Flasher, this kernel is not for you.
This kernel was built by taking the following three branches from my git repo and merging them into each other:
charginghacks
voodoo_sound
uv_only
As such, it has most mainline kernel fixes listed in my git repo thread.
It also has a preliminary implementation of Voodoo Sound initially committed by Bedwa. Based on talking with Supercurio, the apparently missing feature "speaker tuning" is only applicable to the Nexus S - if anything, some other devices may have this enabled when it shouldn't be. However, I have seen one or two reports that dock audio redirection may have issues which I need to investigate.
It has voltage control implemented but no overclocking. Be careful, this implementation from Netarchy allows you to overvolt in addition to undervolting. You could really fry something.
It also has an experimental battery charging algorithm. It should charge a battery faster from deep discharge (but slowing down near topoff, and in fact topping off slower than stock), and has so far successfully held my battery at around 85-90% state of charge when running Navigation in a car dock at full brightness. (It adjusts charge current downwards as battery voltage increases, to avoid worrying about whether charge termination will work properly when under load.) It's experimental, it could fry your battery, it might be wearing mine extra fast (but I doubt it personally) - if I've screwed up I get a significant discount on accessories.
So again - this is as-is, with no support provided as I don't have anywhere close to the amount of free time gtg has for supporting Infused.
Some time down the line I may formally release a supported kernel, but right now is not the time.
Two things to note that applies to all kernels with working CurrentWidget support at this time:
1) We have no way of measuring battery discharge current that I know of, just charge current. If you know of a GalaxyS device with working discharge reporting, please point me to a kernel that implements it.
2) On our device, the values reported by the kernel are 1.83 times the real charge current. I've debated fixing this, but it would break anyone who has already implemented scaling in userland, and it's behaving just like stock Froyo did.
Updates, see post at
http://forum.xda-developers.com/showpost.php?p=17890956&postcount=108 for 9/26,
and http://forum.xda-developers.com/showpost.php?p=18665215&postcount=225 for 10/22,
and http://forum.xda-developers.com/showpost.php?p=18997360&postcount=242 for 11/2,
and http://forum.xda-developers.com/showpost.php?p=19832752&postcount=306 for 11/27 (created 11/27 but posted 11/29)
3/4/2012 is just a fix for video decoding in newer firmwares
Edit: Also, if coming to this kernel from Infusion, reset all your voltage and OC settings back to stock. The voltage control mechanism in Netarchy-style kernels like this one is different from that in Infusion, the difference could cause weird things to happen. For this matter, you should reset voltage/OC settings back to stock before flashing ANY new kernel unless the kernel dev specifically instructs you to do something before flashing.
This kernel, like any kernel for Samsung-stock-derived ROMs, is NOT compatible with CM7/MIUI. (I just realized I say this on my GSII thread, but not here.) Flash this on CM7/MIUI and you'll softbrick. The only thing this has that CM7/MIUI kernels don't is charginghacks anyway...
No HDMI support - It will crash if you plug in an MHL adapter when running a UCKI3 or later leak, will do nothing on UXKG3
Entropy512 said:
OK, since up to now few custom kernels have been released for Gingerbread, much of it due to fear of having to deal with the same stuff gtg465x has had to deal with for Infusion 2.0, I've had enough people ask what kernel I'm running to decide I'll post a compiled binary.
This kernel is my daily driver, it is what I have used for the past few days. I am posting it as-is with no support given. Flash it at your own risk, the only endorsement I give it is that I'm happy with its current state.
I'm on business travel at the moment so don't have time to do any support. Don't PM me with questions on how to flash this or bug reports. If you don't know how to flash a backup made with SGS Kernel Flasher, this kernel is not for you.
This kernel was built by taking the following three branches from my git repo and merging them into each other:
charginghacks
voodoo_sound
uv_only
As such, it has most mainline kernel fixes listed in my git repo thread.
It also has a preliminary implementation of Voodoo Sound initially committed by Bedwa. LinuxBozo has identified some likely code deficiencies so it is likely not fully working. I never used VS heavily enough to judge this properly.
It has voltage control implemented but no overclocking. Be careful, this implementation from Netarchy allows you to overvolt in addition to undervolting. You could really fry something.
It also has an experimental battery charging algorithm. It should charge a battery faster from deep discharge (but slowing down near topoff, and in fact topping off slower than stock), and has so far successfully held my battery at around 85-90% state of charge when running Navigation in a car dock at full brightness. (It adjusts charge current downwards as battery voltage increases, to avoid worrying about whether charge termination will work properly when under load.) It's experimental, it could fry your battery, it might be wearing mine extra fast (but I doubt it personally) - if I've screwed up I get a significant discount on accessories.
So again - this is as-is, with no support provided as I don't have anywhere close to the amount of free time gtg has for supporting Infused.
Some time down the line I may formally release a supported kernel, but right now is not the time.
Click to expand...
Click to collapse
Ty much entropy
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Options! im going to give this a run for a few days thanks brah.
Sent from my SAMSUNG-SGH-I997R using XDA App
This is great. I love seeing development pick up again. I'll have to give this a shot as well as bedwas kernel. And I hope for the sake of all you devs that the noobs start to learn how to treat the forum. Keep up the great work!
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Very nice. Will give it a shot. I am in the car 8 hours a day streaming music via bt.. talking on the phone and using navigation. Battery is always an issue this may do the trick.
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
thanks entropy - gonna try it out.
waiting to hear some feedback from some of u that have downloaded this, would really love to try this out but i want to make sure everything seems A-ok. I'll be coming from bionix infinity if that makes any difference.
It does make a diff being that bionix infinity is a froyo based rom. i havent released the gingerbread. version yet.
Great? No: GREATEST!
I have installed it yesterday, and I noticed the phone more fast and responsive than usual. I also noticed the battery consumption now looks lighter: much better than before. And no rainbow at all.
You and GTG should work for Samsung development. If you do, we can say we're in good hands.
Your work is much appreciated.
Greetings from Rio.
P.S.: My phone uses Infused V2 Beta 3, And there's no rainbow, no freezing, thanks to you, Bozo and our friend GTG. Owe you!
Probably a dumb question but can a Gingerbread based Kernel work on a Froyo O/S such as the Froyo version of Infused?
I am unable to use GB due to the issues many people have with the compass in GB.
http://code.google.com/p/android/issues/detail?id=16741
http://forum.xda-developers.com/showthread.php?t=1109921
and thousands of other hits on this issue in Google.
The charging stuff would be awesome. I was rather disappointed to see that navigation +screen with a car charger would drain the battery. That seems like a basic problem with using it as on-dash navigation. (And they sell a freaking car dock for that.)
There should not be any significant differences in terms of battery life compared to other gingerbread kernels - undervolting will give you a slight improvement. Undervolting buys you a little bit but not too much (unless you're lucky and have a CPU that can undervolt by 100 mV at more at the lower voltages)
My battery tweaks ONLY affect charging on AC, and don't do anything when off the charger
I'd really like to claim super-awesome-battery-improvements, but the reality is that when kernel devs claim this, 95% of the time they're BSing. (Exception: Gingerbread vs. Froyo, but that's the whole kernel + userland package)
Did another long drive today - again, held at around 85-90%. I'll try to dig up a currentwidget screenshot from last week.
Attaching some screenshots of CurrentWidget logs.
One is a log taken while driving with nav on full brightness. Look at how it periodically bumps charge current up to 700 mA - it looks like nav with full brightness needs just a shade over 600 mA. The voltages that trigger state changes are such that this translates to around 85-90% battery.
One is a log taken while charging my new 3500 mAh extended battery from 59%. (I forgot to log the voltages... Sorry.)
You'll see that it starts at 800 mA, then drops to 700 as voltage rises, then 600 (stock), then 550 (below stock, be nice to the battery), then it exits constant-current mode and enters constant voltage mode (battery voltage stays just under 4.2 volts, and current drops until charge terminates.) If you look at the spikes during the CV phase of charging you'll see why I worry about charge termination under load - those spikes are because CPU usage counts against the charge current limit.
So far I can confirm similar results after 1 day of usage. Entropy your work with the battery tweaks is amazing. Ty so much. BTW where did you get your extended Battery?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
2sl0w said:
So far I can confirm similar results after 1 day of usage. Entropy your work with the battery tweaks is amazing. Ty so much. BTW where did you get your extended Battery?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Click to expand...
Click to collapse
eBay - check the Accessories forum, there's a discussion on it there.
The battery cover that comes with it is pretty weak. Two people have received ones that were cracked on arrival including myself. I'm going to try and get a replacement from the vendor, otherwise figure out how to fix/strengthen the cracks.
Entropy will this work with cm7?
Sent from my SGH-I997 using XDA App
bryanb86 said:
Entropy will this work with cm7?
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
No
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Entropy512 said:
Attaching some screenshots of CurrentWidget logs.
One is a log taken while driving with nav on full brightness. Look at how it periodically bumps charge current up to 700 mA - it looks like nav with full brightness needs just a shade over 600 mA. The voltages that trigger state changes are such that this translates to around 85-90% battery.
One is a log taken while charging my new 3500 mAh extended battery from 59%. (I forgot to log the voltages... Sorry.)
You'll see that it starts at 800 mA, then drops to 700 as voltage rises, then 600 (stock), then 550 (below stock, be nice to the battery), then it exits constant-current mode and enters constant voltage mode (battery voltage stays just under 4.2 volts, and current drops until charge terminates.) If you look at the spikes during the CV phase of charging you'll see why I worry about charge termination under load - those spikes are because CPU usage counts against the charge current limit.
Click to expand...
Click to collapse
Where do I get a battery like your 3500 one?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
WeezyFBaby17 said:
Where do I get a battery like your 3500 one?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Click to expand...
Click to collapse
Ebay.
Sent from my SAMSUNG-SGH-I997R using XDA App
00mred00 said:
Ebay.
Sent from my SAMSUNG-SGH-I997R using XDA App
Click to expand...
Click to collapse
Specifically, go over to http://forum.xda-developers.com/showthread.php?t=1175568
Sorry for making many thread, But I'm curious.
ANd need some help
How normal is this? ...
Idle: 216/216 Screen off
No Data No Wifi No GPS No bluetooth No sync
And I'm getting drain like this? What's happening?!?!
Or are the readings just wrong?
i was about to make a thread but saw this and thought id fill in it.
Well my g2x has been quite dissappointing lately..
When i first got it, the battery life wasnt that bad. Even had data/refresh and Auto brightness and it would last almost all day.
But the past couple of months its been unbearable. I would have to charge my phone at any oppurtunity, even at work. After 100% charge i would check 30min later and it would be already at 83%.
I'm on the latest CM7 nightly, and have also tried juice defender (no use)
Im contemplating on just doing a CLEAN install of the nightly but i dont want to start all over again because its a pain.
Any input? Or is it just the crappy battery?
LReyes66 said:
i was about to make a thread but saw this and thought id fill in it.
Well my g2x has been quite dissappointing lately..
When i first got it, the battery life wasnt that bad. Even had data/refresh and Auto brightness and it would last almost all day.
But the past couple of months its been unbearable. I would have to charge my phone at any oppurtunity, even at work. After 100% charge i would check 30min later and it would be already at 83%.
I'm on the latest CM7 nightly, and have also tried juice defender (no use)
Im contemplating on just doing a CLEAN install of the nightly but i dont want to start all over again because its a pain.
Any input? Or is it just the crappy battery?
Click to expand...
Click to collapse
It could be the battery. Your case is different from mine..
My battery is tested with Battery Monitor Widget, and it says my battery is about 1540mAh.
The thing I'm confused about is the battery drain.. It's quite high. 200mAh + at 216mhz
Try clean install, don't use any of those scripts (like V6 SuperCharger), those are wakelock city.
Now, go into spare parts and check your partial wakelocks and uninstall apps that have huge wakelocks, facebook is a battery hog.
clean install of cm7?
or clean wipe of phone back to factory then root/install cm7?
Clean install of the rom you're using.
Sent from my LG-P999 using XDA
I was having horrible battery drainage also. I replaced the usb cable and ac charger and it made a huge difference. Faux kernel also helped alot. I get a little over 8 hrs with moderate to heavy use.
EDIT: wait that wasn't even related to the op but the other scenario.
Sent from my LG-P999
Yeah, I tried a clean install...
After clean install, the only app I installed was this. And boom high usage.
all wipe first and flash or agian.
Wipe user data, /system, and dalvik cache. PM me if you're unsure where they are.
Sent from my amazing LG G2x running Bionix Reloaded v1.4
I have the same issue on my G2x. I have replaced battery with a 1800mAH and a 3500mAH extended. But the drain is the same with every one of them.
Have tried FAUX's kernel with SetCPU and the recommended settings, but to no avail.
Did a clean install (wiped user/factory reset, dalvik, cache and did a format /system) of RG2x-MIUI v2.3.16 - SWIPE NOTIFICATIONS-Powered by Faux123 CM v0.4.8 yesterday.
Battery drains at the rate of 10% every hour when idle. Even with minimal usage (15mins call time, few txt, light browsing over 4G), the battery won't last more than 4-5hrs
One thing I am curious about, do you have to run a combination of kernel+ROM over a period of time to see if the battery performs any better or are the results instant?
Most people get better battery life on OTA based roms than CM7/AOSP. So MIUI may not provide enough juice for you, but try Bionix Reloaded and tell us the difference in battery.
Sent from my amazing LG G2x running Bionix Reloaded v1.4
I has Bionix Reloaded before yesterday. The battery life was about the same, but the main issue that I was facing with Bionix was the switch from data-Wifi. For some reason, data had precedence over WiFi.
I can give it one more shot. Maybe a clean install would rectify that issue. DO you recommend any kernel/tweaks/setCPU settings etc with Bionix or just use it as such?
For the meanwhile, I have turned off GPS and using SetCPU 816/389 inscreen and 389/389 Off to see if there is any improvement.
I really don't care about the fancy part as long as I get battery life.
I recommend Faux's undervolted kernel, make sure its the one for GB btw. As for SetCPU settings (I uses CPU Master), I keep it at 216-816 most of the time, only raising it if I need it (such as Facebook, browsing, heavy games). I have the governor set to Performance.
Also, I don't have a screen off profile (but did have it set before) at 216-503 with Powersave governor, and my battery lasts more now that I took off the profile. The Tegra 2 has HW governors that more efficiently save battery than SW ones do. Not all CPUs are like this, so we are in for a treat.
Sent from my amazing LG G2x running Bionix Reloaded v1.4
Will give it a shot right now. Just to be sure about the kernel, we are talking abt this one:
[ GINGERBREAD: ]
[ Start @ 1.1 GHz, Pre Overclock / Under Volt, Max @ 1.55 GHz ]
The File ==> LGE Pre-OC/UV Kernel Version 013 With EXT4 <==
from http://forum.xda-developers.com/showthread.php?t=1102720
That's not my problem. O;
My problem is that When the battery is 100%, no matter what task I DO, it only drains -2...
But with the same setting, at 30% battery, my battery drains from -300 to -1000
BachanPandey said:
Will give it a shot right now. Just to be sure about the kernel, we are talking abt this one:
[ GINGERBREAD: ]
[ Start @ 1.1 GHz, Pre Overclock / Under Volt, Max @ 1.55 GHz ]
The File ==> LGE Pre-OC/UV Kernel Version 013 With EXT4 <==
from http://forum.xda-developers.com/showthread.php?t=1102720
Click to expand...
Click to collapse
Yes, that's the one. Flash away!
Sent from my amazing LG G2x running Bionix Reloaded v1.4
I have GT p6200 running Carbon ROM KitKat 4.4.4
And since I updated room ICS I've been having this overheating problem
When I was on ICS the tablet didnt get hot while using WiFi
But when I moved to KitKat I started facing this problem
But if it's not the WiFi could it be the CPU governor ??
Now mine is set on user space
If so what's the default CPU settings for this ROM
Thnx
Root97 said:
I have GT p6200 running Carbon ROM KitKat 4.4.4
And since I updated room ICS I've been having this overheating problem
When I was on ICS the tablet didnt get hot while using WiFi
But when I moved to KitKat I started facing this problem
But if it's not the WiFi could it be the CPU governor ??
Now mine is set on user space
If so what's the default CPU settings for this ROM
Thnx
Click to expand...
Click to collapse
This is your 3rd post you have posted as they all happen at the same time on the same rom i would have said all of them on the same tread as
Post 1 http://forum.xda-developers.com/galaxy-tab-plus/general/battery-drain-kitkat-t2835925
Since I updated to KitKat 4.4.4 carbon ROM
I've been facing battery drain while using WiFi mostly not during sleep
I tried doing everything I could to stop it
Disabling Google play services from time to time... Using greenify
Freeing up ram ...battery saving mode
Disabling wake up for apps from app ops
Now I use it for 2 hours and it uses 40 percent of the battery with the lowest brightness though
Please give me suggestions or fixes
Thnx
Post 2 http://forum.xda-developers.com/galaxy-tab-plus/general/wifi-toggle-stuck-t2835929
I'm using carbon ROM KitKat 4.4.4 and the ROM is really smooth and great except for this problem that showed up lately
Sometimes when I turn on WiFi it get stuck and totally freeze until I reboot the device
Is there a way to fix this
And I use xposed modules by the way
Could they have an affect ?
I only use greenify, clear recent apps, clipboard and XAD modules
Thnx
Post 3 http://forum.xda-developers.com/galaxy-tab-plus/general/overheat-problem-t2835913
I have GT p6200 running Carbon ROM KitKat 4.4.4
And since I updated room ICS I've been having this overheating problem
When I was on ICS the tablet didnt get hot while using WiFi
But when I moved to KitKat I started facing this problem
But if it's not the WiFi could it be the CPU governor ??
Now mine is set on user space
If so what's the default CPU settings for this ROM
Thnx
Post 3 Default CPU governor settings for this ROM is on demand
Looking at Post 1 & 3 Both of these have to do with the battery Heat
overclocking generates more heat but under-clocking generates less heat (i have not extensively used this feature but asking in the dev forum or if Google'd the governor settings of the ROM might help to see what it does)
high battery temp you less battery capacity e.g 4 amp becomes 3.2 amp BUT low battery temp more battery capacity e.g 4 amp becomes 4.8 amp
also motherboards like to be cool 50 degrees F to 95 degrees F or 10 degrees C to 35 degrees C this is the ideal working temp
anything more or less than that would cause a waste of either performance and/or battery capacity
my tab has worked from 11 degrees through all the way to 60 degrees C battery temp please note i live in South Africa i go to cold places and it gets really hot some times so use these values as only a rough indication
my tabs idle temp is 15 to 25 light work 25 to 35 gaming 35 to 40 degrees C this is a thumb suck of my normal temp can be more or less (just pulled my tab out of my pocket 23 degrees C and while typing this sentence increased to 24 degrees C currently it is 8 degrees C 81% humidity inside a building )
can i ask that you post your battery temp? as temp is relative (i am using antutu benchmark x widget that displays temp and batterylogger)
also the heat could/maybe be causing your WiFi to get suck not on or off
please see it changing the govenor fixes this