undervolting w/system tuner and cymbaline kernel - AT&T Samsung Galaxy S II Skyrocket SGH-I727

Wanted to verify I undervolted correctly since this is my first time messing with system tuner, I wouldn't be posting but it seemed too simple.. which usually means I did something wrong. After flashing sky ics and applying updates, etc. I let the phone settle all day and charge up to full battery. Updated system tuner, went to voltage tab
Previous recommendations were to UV to -75 mV so I tapped the -12.5mV option six times. Then I exited system tuner. Not sure if I did it correctly, or if I have to reboot for changes to set in? Oh and just before I undervolted I wiped cache and dalvik and flashed the latest cymbaline kernel. My battery's already gone down 2% since I started typing this..but I'll assume everything just needs to settle.

ryancnap said:
Wanted to verify I undervolted correctly since this is my first time messing with system tuner, I wouldn't be posting but it seemed too simple.. which usually means I did something wrong. After flashing sky ics and applying updates, etc. I let the phone settle all day and charge up to full battery. Updated system tuner, went to voltage tab
Previous recommendations were to UV to -75 mV so I tapped the -12.5mV option six times. Then I exited system tuner. Not sure if I did it correctly, or if I have to reboot for changes to set in? Oh and just before I undervolted I wiped cache and dalvik and flashed the latest cymbaline kernel. My battery's already gone down 2% since I started typing this..but I'll assume everything just needs to settle.
Click to expand...
Click to collapse
Make sure to check system tuner after your restart and see if the voltage table are the same as you changed i cant remember if you have to change the boot settings for cpu settings to on boot complete. cymbaline drains battery faster then stock even with uv it will just mitigate it some. If the tables are the same you might want to do a stress test if it passes then your fine.

Bruno2123 said:
Make sure to check system tuner after your restart and see if the voltage table are the same as you changed i cant remember if you have to change the boot settings for cpu settings to on boot complete. cymbaline drains battery faster then stock even with uv it will just mitigate it some. If the tables are the same you might want to do a stress test if it passes then your fine.
Click to expand...
Click to collapse
Yep reboot resets the values. It already seems like battery's draining faster, but that could just be me. Gonna leave this setup go for a day or two though on minimal usage, UVed to -87.5 now, and see how it goes. Then I'll try seanz modded UCLF5 kernel (which I believe doesn't have support for UV) and post results here. Thanks for the help though.

ryancnap said:
Yep reboot resets the values. It already seems like battery's draining faster, but that could just be me. Gonna leave this setup go for a day or two though on minimal usage, UVed to -87.5 now, and see how it goes. Then I'll try seanz modded UCLF5 kernel (which I believe doesn't have support for UV) and post results here. Thanks for the help though.
Click to expand...
Click to collapse
Yeh no unvolting or overclocking with the UCLF5 but it still gives great battery life with how its setup, i want to try that setup with cymbaline with unvolt and see if i can get close to the same battery life just waiting for reeds scripts hope his life clears up soon

Related

Need help with pimpmycpu on ASOP 1.20

I just flashed AOSP 1.20 last night and also flashed the 1.4 ext3 kernel. I have never used pimpmycpu before. The battery life is drastically erratic and does not last long. Does anyone know what the settings are for better battery life with this rom and pimpmycpu? Also can all the settings in pimpmycpu be used? With my vibrant and set cpu usually only one speed could be used for max and the min was easy to set. I can find no way to set the min. Any and all help is greatly appreciated.
im guessing ur using fauxs he said go back to kernel 0.1.1 i think it is the one before the battery driver updates and u wont see drastically changing numbers on ur battery meter also with pimp my cpu u dont need to undervolt his kernel cuz his is -50uv across the board, to overclock long press the desired frequency and to undervolt short press (just press like normal)
there still trying to figure out the battery drivers but yea there definitly wonky, like i said just flash to the kernel previous to the battery updates, if u scroll down his page u see everything he updated and for what version

Battery Drain

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

Battery overheating

When I play graphic intensive games like Where's My Water or Cut The Rope, my battery temperature goes up rapidly. Within 4 or 5 levels it's in the mid 40s C. (The first time it went all the way up to 53 C before I looked at it.)
Is this normal?
If not, would you suspect a bad battery? (I got the phone used.)
FWIW, I'm running ARHD 6.6.3. Behavior is the same under the stock kernel and under SebastianFM's kernel.
Thanks in advance for any help.
Same problem.
I'm having the same problem too. Would appreciate it if someone could post a solution here!
iscarechyu said:
I'm having the same problem too. Would appreciate it if someone could post a solution here!
Click to expand...
Click to collapse
Well the battery doesn't CAUSE overheating, the processors do. Always. ICS roms, the newer ones anyway don't overheat the phone as much, turn of your syncs, mobile network and decrease the brightness of the phone. Your phone will always overheat pretty much no matter what you are doing on it if it is charging.
benjdm said:
When I play graphic intensive games like Where's My Water or Cut The Rope, my battery temperature goes up rapidly. Within 4 or 5 levels it's in the mid 40s C. (The first time it went all the way up to 53 C before I looked at it.)
Is this normal?
If not, would you suspect a bad battery? (I got the phone used.)
FWIW, I'm running ARHD 6.6.3. Behavior is the same under the stock kernel and under SebastianFM's kernel.
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to change the governer...and don't over clock the processors..actually 1.2ghz would do....so try changing the governer...or try faux kernel (keep the governer to intellidemand) ...I use faux kernel and also I play a lot...phone heats up but not that much...it reached max of 40 C
sent from my blazing fast pyramid through sonic waves
ganeshp said:
Try to change the governer...and don't over clock the processors..actually 1.2ghz would do....so try changing the governer...or try faux kernel (keep the governer to intellidemand) ...I use faux kernel and also I play a lot...phone heats up but not that much...it reached max of 40 C
sent from my blazing fast pyramid through sonic waves
Click to expand...
Click to collapse
I'll try re-flashing ARHD 6.6.3 and install Faux kernel this time. The governor is part of a separate app, right? I can't find a governor to set otherwise.
The battery still heats up when I set a max CPU frequency of 1.148 GHz. I'll post my results with Faux kernel and with replacing the battery (with an Anker 1900 mAh one.)
benjdm said:
I'll try re-flashing ARHD 6.6.3 and install Faux kernel this time. The governor is part of a separate app, right? I can't find a governor to set otherwise.
The battery still heats up when I set a max CPU frequency of 1.148 GHz. I'll post my results with Faux kernel and with replacing the battery (with an Anker 1900 mAh one.)
Click to expand...
Click to collapse
The governor sort of controls how the CPU speed will run on your kernel. You can change the governor using an app like SetCPU or System Tuner. BTW faux does tend to run a bit warmer, in my experience, but it's nothing to worry about if you know that you're running apps that are a bit heavy on the CPU.
benjdm said:
I'll try re-flashing ARHD 6.6.3 and install Faux kernel this time. The governor is part of a separate app, right? I can't find a governor to set otherwise.
The battery still heats up when I set a max CPU frequency of 1.148 GHz. I'll post my results with Faux kernel and with replacing the battery (with an Anker 1900 mAh one.)
Click to expand...
Click to collapse
I had the same problem , and im now currently running ARHD.
First time i try stock kernel and everything was burning, tryed to change with sebastian kernel with stock cpu speed and nothing change (and so a hard battery drain), they suggest me re-flashing Sebastian kernel and now everything is ok, temperature is not going up..
im currently running Faux kernel, all stock, and everything is awsome, try it.
see ya
Lollaz
Read this form and flash the 3.12 firmware
any help send feed back
http://forum.xda-developers.com/showthread.php?t=1610232
it manager musa91
I Super-wiped, formatted dalvik cache (I didn't see it in the Superwipe messages), re-installed ARD 6.6.3 with SebastianFM kernel, re-installed the radio, and put in the Anker battery. With System Tuner limiting the CPU max to 1.148 MHz and Governor set to Powersave, my battery hardly heated up at all while playing a game. The game's graphics did stutter though.
Now trying the on-demand governor to see if I can play without stuttering and without overheating the battery. My suspicion is that the improvement is due to re-doing the flashes or replacing a damaged battery.
musa91 said:
Read this form and flash the 3.12 firmware
any help send feed back
http://forum.xda-developers.com/showthread.php?t=1610232
it manager musa91
Click to expand...
Click to collapse
DO NOT DO THIS!!!!!!!
This fix only works for Ondroid rom. And then it has mixed results as to effectiveness.
But ARHD requires firmware 3.32 to work. If you try 3.12 you are likely to get bootlooping.
Musa, you know this only works on Ondroid. You should not be recomending firmware twaeks for other roms you havent tested it on.
benjdm said:
I Super-wiped, formatted dalvik cache (I didn't see it in the Superwipe messages), re-installed ARD 6.6.3 with SebastianFM kernel, re-installed the radio, and put in the Anker battery. With System Tuner limiting the CPU max to 1.148 MHz and Governor set to Powersave, my battery hardly heated up at all while playing a game. The game's graphics did stutter though.
Now trying the on-demand governor to see if I can play without stuttering and without overheating the battery. My suspicion is that the improvement is due to re-doing the flashes or replacing a damaged battery.
Click to expand...
Click to collapse
For future refference you dont have to reflash your rom to switch kernels.
Just wipe dalvik and cache and flash the new kernel. The first boot after than will take a few minutes but then it will be fine.
Its MUCH easier tgan redoing the whole rom.
Skipjacks said:
For future refference you dont have to reflash your rom to switch kernels.
Just wipe dalvik and cache and flash the new kernel. The first boot after than will take a few minutes but then it will be fine.
Its MUCH easier tgan redoing the whole rom.
Click to expand...
Click to collapse
I was trying to re-do everything because I didn't know what the problem was.
benjdm said:
I was trying to re-do everything because I didn't know what the problem was.
Click to expand...
Click to collapse
That plan certainly has its place too! Ive relied on numerous times in various subjects.
I like to call it the Noahs Ark fix. When everything else fails, destroy the world and start over!
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
More testing: I tried putting the old battery back in. Within 3 levels of gameplay the battery heated up to 40C. The new battery hasn't hit 30C no matter what I do. I think it's fairly conclusive the used battery that came with the phone is defective (whether from use, mis-use, or original defect, I have no idea.)
benjdm said:
More testing: I tried putting the old battery back in. Within 3 levels of gameplay the battery heated up to 40C. The new battery hasn't hit 30C no matter what I do. I think it's fairly conclusive the used battery that came with the phone is defective (whether from use, mis-use, or original defect, I have no idea.)
Click to expand...
Click to collapse
Nope incorrect my friend. Any batteries that ate not from HTC themselves won't tell the correct temperature because they do not have full battery calibration like it is with the stock ones.
Sent from my HTC Sensation Z710e using XDA
sensation lover said:
Nope incorrect my friend. Any batteries that ate not from HTC themselves won't tell the correct temperature because they do not have full battery calibration like it is with the stock ones.
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
Well, darn it
benjdm said:
Well, darn it
Click to expand...
Click to collapse
dont hold me to this but you could try getting the htc evo 3d battery or the sensation xe which I think are 1720mah, their callibration should work.
I contacted Anker to see if they had any software or anything for reading temperature. They said they did not and offered to take the battery back (kudos.) I'm keeping the battery.
Underclocking the CPU to 1 GHz seems to be helping quite a bit. Also, something changed with the battery sensing. The Anker battery went from indicating 25C all the time to indicating 11.5-12C all the time. When I put the stock battery back in, it's reading 17C while charging and somewhat above that while playing games, but nowhere near as high as before.
I wonder what's going on...

Racing to 1000 [Q]

Hey XDA,
I'm running PixelRom 1.7.2 and Trinity TEUV and my phone is almost always running at 1000Mhz, which is causing terrible battery life. Even if I'm just idling at my launcher, it will go that high... Anybody know how to get it to stay at lower frequencies? Oh and my governor is Ondemand and scheduler is Deadline. Hope someone can help...
FirePoncho86 said:
Hey XDA,
I'm running PixelRom 1.7.2 and Trinity TEUV and my phone is almost always running at 1000Mhz, which is causing terrible battery life. Even if I'm just idling at my launcher, it will go that high... Anybody know how to get it to stay at lower frequencies? Oh and my governor is Ondemand and scheduler is Deadline. Hope someone can help...
Click to expand...
Click to collapse
teuv runs at 880mhz.
its possible that an app or a background process is active. try this free app from the market, its called diagnosis https://play.google.com/store/apps/details?id=eu.thedarken.diagnosis&hl=en
I thought it did too, but NsTools and CPU spy both give me: 100Mhz, 200Mhz, 400Mhz, 800Mhz, 1000Mhz, and 1096Mhz. I will try the tool from the market (yes, I still calls it the market)
FirePoncho86 said:
I thought it did too, but NsTools and CPU spy both give me: 100Mhz, 200Mhz, 400Mhz, 800Mhz, 1000Mhz, and 1096Mhz. I will try the tool from the market (yes, I still calls it the market)
Click to expand...
Click to collapse
1096... thats not teuv, that the t11 kernel. heres the latest teuv http://goo.gl/5JwMT im using this one at the moment
My thanks good man, that was the one I was looking for, now I feel quite silly :3
Right now, just at my launcher, cpu is switching from 92% to 100% usage :s
FirePoncho86 said:
My thanks good man, that was the one I was looking for, now I feel quite silly :3
Right now, just at my launcher, cpu is switching from 92% to 100% usage :s
Click to expand...
Click to collapse
if you just booted, it should(for about 2-4 minutes) then it should drop. unless you have an active live wallpaper, an app thats not written very well, or a process thats gone wild. try that app i linked, let it run for a few hours, maybe you can find the cause.
My phone had been on for a few hours...
Also, I flashed TEUV, and I don't think my phone handles it very well (TEUV has GPU overclock). Once I booted, it gave me a black screen and said: (Application) has stopped working for every app on startup. This happened twice, so I went back to Matr1x and battery is still terrible...
FirePoncho86 said:
My phone had been on for a few hours...
Also, I flashed TEUV, and I don't think my phone handles it very well (TEUV has GPU overclock). Once I booted, it gave me a black screen and said: (Application) has stopped working for every app on startup. This happened twice, so I went back to Matr1x and battery is still terrible...
Click to expand...
Click to collapse
sounds like a bad download of teuv.
Bad download? I flashed it properly and it booted fine, until after the "optimizing applications" screen
is this the first charge since you flash the kernel? If it is, let the battery run out, charge it full and take a look at it again. I find that ICS really take a full charge to stablize its battery... my first charge after flashing a new kernel has always use a lot more battery than the second charge.
Alright, I'll try that... Also I went back to aosp+ because I really like it.
Also, android system is always using 20% cpu, even on idle..
I remember performing some tests with frequencies and deep idle - I wanted to find out the minimum frequency required to run music player screen-off with few concurrent processes. I remember reading how 400mhz is the optimal frequency for deep idle but cpu spy would always report it cruising at 1ghz and cross referenced with nstools DI stats, it was supposedly in deep idle. With DI off and bumping up the frequency to 800mhz, 1ghz took up the majority of operation time. Long story short, whatever combination I tested did not garner desirable results. That was a couple weeks ago, though. I've since given up on figuring it out.
Wait, are you having the same problem as me?Ive lost 5% battry just by having the screen on for 9 minutes...

[Q]i9023 once reboot during boot (Matr1x 20, stock rom)

Hy guys!
I own an i9023, and I'm a frequent reader of XDA's Nexus S section. A week ago I've decided to change the stock kernel. I choose the newest Matr1x kernel, i found this the most sympathetic, after reading through several [kernel] threads. So i tried the 19.5 BFS/CFS, and now my device is on 20.0 CFS with stock rom 4.0.4. I've installed NSTools too. And using smartassV2/noop 100/1000 DIDLE, and no OC, and default voltages too.
I am absolutely statisfied with the kernel, it is much smoother than stock, and has a great battery life, and gets better with every update. At least in case 19.5 to 20
But here is my problem:
Almost in every boot, my phone reboots once during boot. After it is rebooted, works like a charm, no freezes, nor reboots. Fast, reliable, anything you want.
I noticed the device boots without any problem after flashing kernel, before applying any NSTools settings, or if I use resetnstools.zip.
So i am thinking, maybe NSTools can be the source of this reboot.
Here is my NSTools settings:
All tewaks off, 97%, noop.
CPU: smartassV2, 100/1000
liveOC: 100%, 800, 1000
DIDLE: ON
SmartassV2: awake ideal 1000, sleep ideal 100, sleep wakeup 600, min load 70, max 85, ramp down 200, up 200, down rate 49000, up 48000
volt: default
Settings: set on boot
So any idea what is causing this reboot? Or this is normal? I think it is not, but it even could be
Thanks the answer.
Matr1x is undervolted by default. Try upping them a bit or reverting to stock voltages.
Harbb said:
Matr1x is undervolted by default. Try upping them a bit or reverting to stock voltages.
Click to expand...
Click to collapse
This. My phone hates undevolting and I had to return all the voltage settings to the stock Nexus settings if I want to use his kernel. Since I changed them, I've had no reboots or freezes.
Thanks the fast answer Harbb and chronophase1!
Looks like mine hates the UV too Raised the voltages a bit (didn't changed the INT, and that ARM, what was already on Nexus S default), look like good at first look. But requires further testing, to say the problem is gone. Thanks again.
Yeah. All phones aren't the same sadly. If it makes you feel any better, I've been running the kernel for almost 100 hours straight and no issues. Before, every time I hit about 95 hours up time the damn thing would freeze with the UV settings. So I'm still running the test but so far so good on my end.
Looks like the problem is solved. After several voltage settings, I had to return to default Nexus S voltages, even on 1Ghz. The reboot during boot disappeared.
I lost the UV, but I gained OC, now stable on 1.2GHz/1350mv/1150mv. And battery is still good, hope it will remain that way.
Did you change the INT VOLT settings first? Or did you revert all to the stock levels.
I suspect reverting only INT VOLT to the Stock levels will fix those problems. If anybody is willing to try that would be nice ) (I only experienced reboot once with default Matr1x values so no point in my trying)

Categories

Resources