Mine is -100mv on blu.spark and Ashwin's CM13. Never had any problems with this voltage.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm always using - 100 undervolt.
Sent from my ONE E1003 using Tapatalk
I'm stable at - 95
-100 was unstable for my OPX
Working on Swell-V8... I'm quite happy with this setup
It depends on individual phone. Subjective
Here is my setup. Using Boeffla's kernel and his app. Also, with this uv profile there are no more overheatings. The phone stays quite cold even on gaming and stuff like that.
-75mV overall. 100 was a bit unstable, maybe 90 could work but this way I'm completely safe.
As I already said, I'm on -100, but I still have high heating... 55°c when playing Minecraft for 20 minutes.
RJDTWO said:
Working on Swell-V8... I'm quite happy with this setup
Click to expand...
Click to collapse
Did you undervolt to an overall value or different for different frequency?In OOS, I had freezing even with - 25 mV.
saurabh40629 said:
Did you undervolt to an overall value or different for different frequency?In OOS, I had freezing even with - 25 mV.
Click to expand...
Click to collapse
Different for frequency
RJDTWO said:
Different for frequency
Click to expand...
Click to collapse
How do you do that? Once i tried, hit one wrong voltage, and phone never booted to system.
saurabh40629 said:
How do you do that? Once i tried, hit one wrong voltage, and phone never booted to system.
Click to expand...
Click to collapse
Patience. You find the lowest for each in 25mv increments and from there tune them. It's tedious. Obviously if you enter a random voltage then it don't work. If you don't entirely unfetdtand PLEASE read up on it or you will fry your phone
Currently at -100 to -125mv on Boeffla. No fc's or reboots since I started using these voltages.
-100mV on BluSpark kernel, no freezes, no reboots.
If you use Kernel Auditor, "Boot on system start" gets activated several seconds after the phone has started, so you can revert any errors in normal cases.
I can go -60mV, no more on bluespark v128.
If i go more than -60mV, i get reboots sometimes after 12hours or after 2-3 days
Related
whats up forums? I'm just wondering about the longest UP time you guys have on your Xperia X10. For me the 2.1 stock rom lasts up to 140 hours before the phone becomes laggy and bombards me with FC's. After upgrading to the FreeX10 beta4 Froyo release, the phone will last about 2 days without any major issues (after that I will get random reboots)... Currently, I'm on wolfbreak's latest rom and the phone's never been this smooth and snappy before. it has been 3 days and counting. (no FC, no reboots)How about your phones? How long can your phone go without rebooting?
Mine i shut down every 3 days cuz of work. We arent allowed to have nice phones on shifts lol. But if its longer i dont usually have an issue. But if i do the only thing i get is my phone stays at 3g and or phone is too laggy to run. but it's not that often that it happens.
Sent from XDA Premium from my X10a rooted running 2.2.1 CM Rom from Rendeiro2005
i switched to launcher pro and the lag seems to be less frequent =)
Here is my best uptime, back when I was on Zs' beta4 with sysctl and setCpu profiles.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PS. I've voted for 23-72, but I should of vote for 72-100! So count me there.
G-FACE said:
Here is my best uptime, back when I was on Zs' beta4 with sysctl and setCpu profiles.
PS. I've voted for 23-72, but I should of vote for 72-100! So count me there.
Click to expand...
Click to collapse
totally jinxed it for myself. phone froze this morning had to restart. btw what setCPU profiles are u using? is there a HUGE noticeable performance difference?
eizonuts said:
totally jinxed it for myself. phone froze this morning had to restart. btw what setCPU profiles are u using? is there a HUGE noticeable performance difference?
Click to expand...
Click to collapse
My settings were:
Main screen was: Max 768, Min 245, scaling ondemnd
And 3 profiles:
screen off - priority 85, Max 245, Min 245, scaling ondemand
battery <29% - priority 60, Max 384, Min 245, scaling ondemand
charging - priority 50, Max 998, Min 245, scaling performance
Howdy all..
I have a couple of questions about battery usage relating to screen power consumption.
First some background on the.phone
Aussie i9100t
Cm7.1 with its base kernel (wolverine)
Stock radio kf2
Now, if j sit down and read tapatalk or Facebook for 15 minutes ill burn 5% battery (even with the new Samsung 2000mah battery I just bought)
I have the brightness set to manual and as low as it will go, it actually seems way too. Right for minimum settings to be honest.
Just wondering if anyone has some suggestions on where too look for issues
Edit, just a note, I've had 2x i9100's prior to this model and I'm pretty positive they weren't this bad
Cheers
Kyle
Try a different radio, if your browsing on 3g....if on wifi try a different kernel like siyah
Thanks for the reply.
I gave siyah a go yesterday for 12 hours but found a similar result with the stock battery.
Dunno hey, just find it quite strange that the last 2 sgs2s I've had were not like this..
Couple of screenshots..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kyl3 said:
Couple of screenshots..
Click to expand...
Click to collapse
Try new siyah 2.6.6i with ondemand as default. Worked great for me.. My battery is almost dead in pic bcz i tried ics for a few min but it killed battery as u can see ;( back on siyah and gone a hour of listening to music and xda browsing battery went from 15% to 12% lol stock battery also auto brightness on
Sent from my GT-I9100 using xda premium
Thanks for that mate, do you find lag when scrolling with siyah? I got it a bit, maybe selected the wrong governor or something ...
kyl3 said:
Thanks for that mate, do you find lag when scrolling with siyah? I got it a bit, maybe selected the wrong governor or something ...
Click to expand...
Click to collapse
Nope.. I use setcpu for uv and oc and used tegrak oc app to uv gpu and change governor to cfq which i believe is better (in my opinion)
Sent from my GT-I9100 using xda premium
Im using SiyahKernal and I'm curious about undervolting.
I want a safe/ok combo that will be smoothish and fastish but good for battery.
I'm currently running the cpu at 900mhz using extweaks.
Any suggestions? what're your settings?
Undervolting takes time and patience.
Start with -25 first and test if it is stable for a day or two.
If it is, move on to the next step.
Personally I didn't undervolt yet because it seemed to lower my average benchmark scores. Overclocked to 1704 and get 63k average in quadrant!!! (Not that it really matters in daily use...)
Yes do it in steps. The only danger is too low a voltage will cause a reboot when idle if theres not enough power to keep going.
I got mine to -100 for every step, stable. This means Samsung were generous with their voltages IMHO, but OEM's generally are. HTC are the same.
rootSU said:
Yes do it in steps. The only danger is too low a voltage will cause a reboot when idle if theres not enough power to keep going.
I got mine to -100 for every step, stable. This means Samsung were generous with their voltages IMHO, but OEM's generally are. HTC are the same.
Click to expand...
Click to collapse
Thats amazing! how was your battery?
So the only danger is a reboot? no damage? apart from the obvious loss of work unsaved or game etc.
Not really bothered about benchmarking. just battery life with at least an 'ok' performance. i can easily set it up later when i need performance.
Just really love this phone and am mosty working all day.
Not really for undervolting. Its over volting that causes damage. Battery is ok. Not amazingly better. Cell Standby is killing me.
rootSU said:
Not really for undervolting. Its over volting that causes damage. Battery is ok. Not amazingly better. Cell Standby is killing me.
Click to expand...
Click to collapse
yeah cell standby is a big hog. it drains more than 45% of my battery every charge
Only posted yesterday on Jayce Ooi's Paradise
How to undervolt Samsung Galaxy S3?
http://www.jayceooi.com/2012/06/20/how-to-undervolt-samsung-galaxy-s3/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i was messing with the stweaks to uv etc....now when im using cpu spy, i noticed that the clock speed is staying at max, whether it be 1.6ghz when over clocked, or 1.4 when not overclocking or even 1ghz when power save is on. the phone refuses to go on any other frequency. not even deep sleep.
ive reset stweaks, un installed it, uninstalled all other over clock apps i had. nothing changed, i even re flashed siyah kernel. but the cpu refuses to go back to normal. did i mess up my cpu permenantly???? help please. running latest omega rom btw
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh lord, don't freak out.
What's your CPU governor? "performance" ? If so change it.
did a factory reset. once the screen is on it goes into max clock speed with no apps running in the background. the phone deep slept for about a minute. any suggestions?
Skander1998 said:
Oh lord, don't freak out.
What's your CPU governor? "performance" ? If so change it.
Click to expand...
Click to collapse
ive never changed my governor from pegasusq
so i've wiped everything, from data, preload, sd card, dalvik cache, battery stats, re flashed the omega rom. and currently using the stock kernel. phone is fresh with no bloatware. even removed the sd card. took off wifi and data. eventually the phone took about 7 minutes before it finally deep slept with the screen off. it continued to idle at max cpu setting even when the screen was off. after 9 mins. it idled with the screen on at 200mhz.
could this kind of instability be caused from UV and the stress tests before? if thats the case, what should i do? just leave the phone running for a couple of hours? does this mean the cpu is damaged (sorry for panicking) but i have 2 weeks left on my warranty. should i restore original firmware and carry it back to the shop?
Use BetterBatteryStats to see what is keeping the phone awake. Media scanner can cause this at times, I'd leave the phone running for 45 minutes then wait to see if it calms down.
So I open an app like the play store or chrome in the screenshots and get 100% load for 10 seconds or more. I noticed this behavior on different roms and kernels/governors.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's only 51% maxed out would be BOTH CPUs at 100% so really your concern is?
Sent from my Nexus 10 using XDA Premium HD app
Because it's a waste of energy.
reborn90, sorry for the off topic question but what are those system widgets (CPU, Disk I/O .. etc)?
Perfmon its the app
Sent from my Nexus 10 using xda app-developers app
reborn90 said:
Because it's a waste of energy.
Click to expand...
Click to collapse
Without accounting for exactly what the CPU is doing you really can't make this assertion.
Me neither, that's why I ask. It just looks buggy when the cpu starts scaling to max frequency (for a long time) because a new app is started.
reborn90 said:
Me neither, that's why I ask. It just looks buggy when the cpu starts scaling to max frequency (for a long time) because a new app is started.
Click to expand...
Click to collapse
Try a different governor, or maybe increase/decrease the refresh rate of your resource monitor? (BTW, scaling to max speed on load is actually better for battery life in some cases, as the task energy required can be sometimes be lower when you burn more juice but complete a given task in a shorter period of time).
The cpu (core) load shoud be independent from the governor, apart from the current frequency of course. I still have the feeling that it is some kind of "phantom load" but actually I have no idea. I switched from an ASOP rom to CM10.1 and I haven't seen the problem yet. :fingers-crossed:
reborn90 said:
The cpu (core) load shoud be independent from the governor, apart from the current frequency of course.
Click to expand...
Click to collapse
Its true that load wouldnt be caused by the governor, but the governor you run does affect how load is handled and whether there averages more or less load on the system. By running at a higher speed the system load is decreased because the processor is going through its tasks much faster. If the governor is keeping the speed lower while doing a task then the system load will be much higher because the CPU cant complete things as fast. So load and governor are linked together, but it is the tasks being run that cause any of the load in the first place.
Since the problem hasnt come back since switching to CM10.1 it was probably something in the system that got bugged and caused this behavior.
Yes I agree, but in this particular case I have maximal frequency and core load. It's much better now with cm10.1. :good: