Related
For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?
supadupadoug said:
For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?
Click to expand...
Click to collapse
Flash community kernel your getting sod or try removing your Oc UV settings
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Ok thanks. What is sod by the way???
supadupadoug said:
Ok thanks. What is sod by the way???
Click to expand...
Click to collapse
Sleep of death
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
oh lol im learning slowly but fa showly.
supadupadoug said:
oh lol im learning slowly but fa showly.
Click to expand...
Click to collapse
All good
Infusion kernel is great kernel but your settings are going to be trial an error play around with.UV that's usually the probably with sod
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Question about uv. is less best ie -25? and what does disabling the various clock speeds do?
Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.
Thanks I will give that a try. to oc really isn't my goal just to improve battery life. Right now seems to be working ok @12k with frequency uv @75-50
jdbeitz said:
Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.
Click to expand...
Click to collapse
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)
You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation
supadupadoug said:
You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation
Click to expand...
Click to collapse
No prob. Buddy glad to have ya
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Entropy512 said:
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)
Click to expand...
Click to collapse
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.
Dani897 said:
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.
Click to expand...
Click to collapse
Not a clue - I only know what netarchy has done, not what he plans on doing.
The architecture of voltage/CPU frequency control is significantly different in GB kernels than Froyo. In general it's cleaner, so a lot of the issues with rapid frequency changes might go away in GB. For example, there's some code in the base kernel that's supposed to facilitate rapid voltage changes (not exactly sure how... the only documentation people outside of Samsung have for the MAX8998 is kernel source code.)
Well guys I have some news. I continued use with set cpu no oc just uv on freq above 624 @ -75 and I kept my screen off profile set to 644 max powersave scaling, and my battery life has been outstanding i check emails frequently been texting all morning and playing wwf and im @ 70% after 4 hrs of use. I know I read % doesn't mean much compared to some volts ratio but I think this is worth mentioning. And for my purposes the goal has been achieved in extending battery life and still having exceptional performance.
Oh and I wanted to add that my phone recharges much faster especially with the screen off with these setting. Maybe nothing new to you but def a plus for a(us) neewb's reading.
Hi there!
I'm not allowed yet to post in the development section, so I decided to put my question here... Please don't shoot me
I have read many threads from the Development Section (when got the time), tested a few Roms and Kernels. All of the developers are doing a great job, every day (my donations are going to eugene373, mathkid95 & peter alfonso).
I had no idea how a Nexus S can "move" with a custom Rom or Kernel.
I'm kinda new in this "root affair" with my phone, and i found a superb combination between Bugless Beast Rom & Matr1x 15 Kernel. For that i have posted some screen shots.
In order to achieve those results, i used LiveOC to 105 but i didn't changed the voltages. Oh, and Lulzactive/Sio. When i put the phone to charge, i had a freeze, and a battery pull was needed.
So, can someone tell me if i need to change the voltages too for that combination to be stable? If so, which are the best voltages?
Thank all of you in advance!
P.S.: I use i9023 LCD. With eugene373's Speedy 7 & stock ICS i had no reboots or freezes, but the battery is not that great. Although, the phone is unbelievably fast.
They're decent results, the i9023's screen generally uses more power due to the backlight. Matr1x kernel is undervolted and some phones don't like it. For LiveOC i would DEFINITELY pump up the voltages (say +25mV across the board, except 100mhz and 200mhz as matr1x has them stock). Keep messing around with the voltages until you find the lowest voltage that is happily stable and not overheating.
Your phone may be fine, though. But as the frequency goes up AND matr1x is already undervolted, you'll probably be better off taking it up to 110% and finding somewhere stable there since i believe the minimum voltage change is 25mV.
Thank you very much for your answer.
I'll will try to do what you adviced me, but I'm a little bit afraid not to mess up things because I'm just a begginer, as I said...
Best of luck!
You'll be fine mate, just don't push it too hard until you know what your phone is capable of and make sure heat isn't a problem. Some chips just aren't as lenient as others, but yours seems to take undervolting fairly well which is a good sign.
Also, as you're bumping it up and testing, don't check set on boot. Unless you have a current working nandroid at least.
Sent from my Nexus S 4G using xda premium
Harbb said:
They're decent results, the i9023's screen generally uses more power due to the backlight. Matr1x kernel is undervolted and some phones don't like it. For LiveOC i would DEFINITELY pump up the voltages (say +25mV across the board, except 100mhz and 200mhz as matr1x has them stock). Keep messing around with the voltages until you find the lowest voltage that is happily stable and not overheating.
Your phone may be fine, though. But as the frequency goes up AND matr1x is already undervolted, you'll probably be better off taking it up to 110% and finding somewhere stable there since i believe the minimum voltage change is 25mV.
Click to expand...
Click to collapse
i think your statment about screen is not completely right.
yes , based on SA screen functionality , it's saves more power then Super Clear LCD screen because SA lights its up by itself , but SC LCD screen needs additional light lay.
but that also depends on color , SA runs brilliant color costs same , or even more juices as SC LCD , but it do save power when shows dark color like black.
this is why android 2.3 status bar color has changed from grey to black , also default wallpaper for Nexus S is dark color.
------------
to OP , about voltages , you only have to change it when you OC and your phone become unstable , live OC usually are able up to 115% or 120% , if you don't OC over 1.0 G but use live OC up to 1.15 G or 1.2 G , you won't be needing change voltage.
but if you use both OC and liveOC , for example by Matr1x, CPU can set up to 1.46G and 115% of LiveOC , max to 1.67 G , in that case you may need change voltage...
yes... this is max i've done , i was afraid that i would get CPU fried...
I said generally for the amoleds, I'm very aware of how they work. Unless you're staring at an all white screen all day it is quite rare for it to use more power. This is why it is a great technology for mobile phones.
Anywho, it certainly needs additional voltage with liveoc. Please don't misinform others. At 110%, 1GHz becomes 1.1GHz which is plenty to cause instability on many cpus. This is especially true with matr1x and other undervolted kernels.
with all due respect , but i think little bite OC doesn't really need change voltage , because usually , generally , mostly , kernel default setting is enough...
When you live oc an undervolted kernel yes you do need to raise voltages
Regardless if you regular oc or not because if you live oc by 10% you are ocing by 10%. Its not complicated.
Harbb is right.
I know, I'm a tester for matr1x and in being a tester that means I have to test all aspects of it and put it under different strains, overclocking etc.
To the OP:
Live oc by 110% and if you have problems with reboots then raise voltages by 25mv as harbb said already.
And he also gave good advice regarding unchecking the set at boot option in nstools.
Disregard all other comments.
Thank you Harbb and Nodstuff!
Very good advices, I've followed them and seems to work ok so far. Seems like I didn't read that much as I thought, because I didn't know that the Matr1x kernel is undervolted. I have to read more infos from here, wish I'd had the time... I was just looking for a good combination between a Rom and a Kernel, because I had terrible battery life on stock ICS. Now I'm pretty happy with the combo mentioned above, thank you again for your help.
I wish you all the best and good luck!
I'm using the Faux Kernel on my Skyrocket. I'm using Set CPU for speed control, under-clocking for more battery life.
I head the terms UC, OC, UV and OC. When I use Set CPU, I assume that when I set maximum CPU speeds, I'm under-clocking. But what is under-volting? Is that different? Is there an advantage to doing both?
Harry
There is an advantage to undervolting you need either fauxs app or systemmtuner to do so.
Undervolting is giving the cpu less power and asking it to do the same amount of work it was doing before
Sent from my GT-P7500 using xda premium
That sounds a bit more dangerous in terms of doing damage to the phone or having reboots etc. when you are giving the circuity less power than it was designed.
For those who chose to undervolt for power savings, it is usually done in conjunction with under-clocking, or is it a one or the other type thing?
Not really, under volting is not as dangerous as over volting (used to also achieve higher overclocks). Over volting can actually damage hardware if you provide too much juice.
Under volting just reduces the voltage, if its not enough the app freezes or worse the phone reboots. If that happens, bump it up one more step (+12500) and you should be fine. Find where you can go low but still be stable (for me it happens to be -87500) you will save more battery.
Dixit
all good correct info. I highly recommend fauxclock, its very user friendly. I have my phone undervolted -100mV and underclocked to 1.2 and I'm getting 13 hours heavy usage with around 5 hours on screen time, with NO juice defender. For this phone, that's pretty good
icenight89 said:
all good correct info. I highly recommend fauxclock, its very user friendly. I have my phone undervolted -100mV and underclocked to 1.2 and I'm getting 13 hours heavy usage with around 5 hours on screen time, with NO juice defender. For this phone, that's pretty good
Click to expand...
Click to collapse
My exact setup. -100mV UV, and 1.188 gHz UC. Went from 100% to 0% in 1 day 7.5 hours with 3 hours of screen on time. No juice defender either. I think its pretty food. Using faux 009u, btw.
Sent from my SAMSUNG-SGH-I727 using XDA
Only issue I got with Fauxclock is that it saves the CPU clocks I set (say 1.298ghz max) but it doesnt actually save the voltage after a reboot. I look at the VDD table and its still stock.
So only way to get it to work is to manually edit the VDD table itself. Not sure if this is by default that fauxclock doesnt actually save the voltages after a reboot.
Dixit
Don't see fauxclock in the application store, sorry, Google Play Station.
Thats cause its not in the Google Play. Its a separate app at this location
http://rootzwiki.com/topic/4550-app09-beta-snapdragon-dual-core-oc-control/
Dixit
Got it, thanks. And the under-volting is so easy with Fauxclock, I've set it down 100.
So I've got SetCPU doing the CPU speed, and Faux for the voltage. Seems a bit redundant, since Faux also does CPU speeds, but SetCPU has some cool configuration settings where you can actually have multiple settings for CPU speed based on various conditions such as battery life remaining, processor temperature, time of day, phases of the moon . So I guess I have to keep them both. Hope they don't interfere with each other.
Fauxclock has very basic CPU clock settings, it was created just for that faux compatible kernels so the original developer didnt spend weeks on it. It was just a simple and fast and effective GUI to set min/max clocks and also voltages (global scale). You can however set one other clock which is the "screen off" clock, but thats about it.
harry_fine said:
Got it, thanks. And the under-volting is so easy with Fauxclock, I've set it down 100.
So I've got SetCPU doing the CPU speed, and Faux for the voltage. Seems a bit redundant, since Faux also does CPU speeds, but SetCPU has some cool configuration settings where you can actually have multiple settings for CPU speed based on various conditions such as battery life remaining, processor temperature, time of day, phases of the moon . So I guess I have to keep them both. Hope they don't interfere with each other.
Click to expand...
Click to collapse
they will, use one or the other. U can manually change global vdd table and use setcpu, or forego advanced profiles in setcpu, but u can't/shouldn't use both
FauxClock force closes on launch for me..
EDIT: Getting a Faux kernal fixed that. Wow I feel dumb.
Shadeslayers said:
FauxClock force closes on launch for me..
Click to expand...
Click to collapse
Are u using faux kernel?
Any tips or thread about how to manually change global vdd table so that I can use SetCPU for the profiles and adjust voltage manually?
Is there a risk to that? If I set it and the phone won't boot, it sticks!
use Gideon UV/OC script and change vdd as u see fit. If it doesn't work u can always flash Gideon stock back
icenight89 said:
use Gideon UV/OC script and change bed as u see fit. If it doesn't work u can always flash Gideon stock back
Click to expand...
Click to collapse
What exactly is the difference between flashing Gideon's script or just using FauxClock? Thanks!
fauxclock gives u dynamic min/Max and voltage control as per user settings. Gideon is pre-set and makes use of init.d script. u can change it, but every change requires a reboot
Hi, I'm on the latest version of virtuous w/ sebstians kernel, and I'm wondering if there are any better kernel options to improve battery life with out sacrificing smoothness? I also seem to have an occasional issue, when I touch the screen it doest respond the first time. This is not constant but still a little frustrating at times. Is this a problem caused by the kernel? Thanks all....
as for saving battery, i dont know about a different kernel but you could try underclocking and undervolting. the smoothness is unchanged for me and the battery should last quite a bit more even if your overclocking the battery is good. check out setting the voltage values down here http://forum.xda-developers.com/showthread.php?t=1329402
im using bricked kernel on an insertcoin rom if that makes any difference. i even have the cpu set at 810/ 1.29 min/max still incredibly smooth and great on battery. use system tuner to do this. if the phone becomes unstable and reboots the values are set back to default so not a problem till you find values you can work with.
your responsiveness maybe that you set the cpu too low when screen if off? could be that or rom based. not sure
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