I under clocked my phone to save battery life but doesn't seem to be working. I'm down to 702MHz Max and no battery life difference. Its as if I'm not underclocking. Please help.
{
"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"
}
Sent from my MB886 using XDA Premium HD app
It is my understanding that, in order to conserve power, the processor spends most of its time running at its lowest possible frequency. When required, the processor will ramp up until the higher frequency is no longer required and drops back down to its minimum speed. Underclocking would help if your cpu was working at max speed of 1.5 Ghz most of the time.
audit13 said:
It is my understanding that, in order to conserve power, the processor spends most of its time running at its lowest possible frequency. When required, the processor will ramp up until the higher frequency is no longer required and drops back down to its minimum speed. Underclocking would help if your cpu was working at max speed of 1.5 Ghz most of the time.
Click to expand...
Click to collapse
It shouldn't be.... Hey slider is that for half that speed.
Sent from my Atrix HD using xda premium
What can I do to make it save power?
Sent from my MB886 using XDA Premium HD app
The Android Attorney said:
What can I do to make it save power?
Sent from my MB886 using XDA Premium HD app
Click to expand...
Click to collapse
greenify it is free on play store
Related
I just wanna ask if this is normal?
When I hold the screen for a while it can burn out my fingers.
Its freaky hot.
The temperature is 59 degrees celsius.
{
"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"
}
Sent from my GT-I9000 using XDA App
Nope, its too high. Normal should be 32-36 and some times the temp may go a little high during charging. But never this high.
The obvious reason is ur Overclocking. Some phones are not built for it. STOP Ocing to 1.6. Try a reasonable 1.3 or the best 1.2GHz
You're gonna burn your battery and your phone into the ground if you don't scale that back.
It is usually best to try and keep your phone under 40c whevever possible, and never above 45c for too long.
Can the phone still run - yes
Is it wise for long periods of time - absolutely not!...
Sent from my GT-I9000 using xda premium
DonVito2020 said:
The obvious reason is ur Overclocking. Some phones are not built for it. STOP Ocing to 1.6. Try a reasonable 1.3 or the best 1.2GHz
Click to expand...
Click to collapse
Or simply use the 1GHz standard CPU frequency for which the device was designed.
Overclocking without really knowing what problems this may cause....
Thank You guys.
I will try to keep the temperature in normal levels.
Thanks for the support.
I cnt change the cpu scaling setting to anything but the default perfrmance i want to switch it to on demand but it doesn't have the option or allow me to switch it.... what's going on? Tried 2 dif kernels.
{
"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"
}
Sent from my LG-P990 using XDA Premium App
eraldo said:
I cnt change the cpu scaling setting to anything but the default perfrmance i want to switch it to on demand but it doesn't have the option or allow me to switch it.... what's going on? Tried 2 dif kernels.
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
It is useless. Our kernels only have performance and powersave, and accordingto big kernel specialists there is no visible difference between those two. In CM7 kernel scaling support was even dropped if I'm correct.
Striatum_bdr said:
It is useless. Our kernels only have performance and powersave, and accordingto big kernel specialists there is no visible difference between those two. In CM7 kernel scaling support was even dropped if I'm correct.
Click to expand...
Click to collapse
yes you are correct
our tegra devices uses the tegra 2 build in governor at least on this kernel
you can put in as much governors as you want it will still be using its own governor
the settings doesn't do anything on our devices so just ignore it
Hmm i wasn't aware of that, ok cheers guys.
Sent from my LG-P990 using XDA Premium App
I have a problem that is >
when I overclock my incredible s to 2ghz it will hang and it will reboot or in some times I had remove battery .
I test it with all the roms and kernals that support 2ghz and not only 2ghz
also 1920 ghz will become hang too
does anybody have the same problem?
what can I do for it ?
I have a suggestion, if it hangs and rebooted at 2ghz... don't overclock that high.
Maximum recommended overclock is 1.5ghz
I know that but I wanna know that it is my phone problem or not?
Because if the others have the same problem the devs didn't set 2ghz to their kernal
Sent from my Incredible S using xda premium
sif2010 said:
I know that but I wanna know that it is my phone problem or not?
Because if the others have the same problem the devs didn't set 2ghz to their kernal
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
no, it's not only your phone problem, but I higly recommend you to stop killing it, 1.5GHz would be enough at this moment.
It is possible to oc that high however stability is low. I believe the only rom that let me do it was discontinued a while ago it was developed by newtoroot and I could effectively clock to 2.1 using tiamat 1.12. It was quite unnecessary as higher benchmarks were achieved with lower settings.
{
"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"
}
Sent from my HTC Incredible S
Processors aren't exactly the same. Some can reach 2ghz, some can't. However, there is no obvious reason to do so. Yours is perfectly fine, just keep it under 1.5 ghz
thank you guys for your suggestion and helping .
you are killing your Incs... 2GHz!!!
1.5GHz would be enough for your using and running all the app.
{
"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"
}
BEFORE
Sent from my Nexus 7 using xda premium
RaydenEris said:
BEFORE
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Sent from my Nexus 7 using xda premium
So was it better at least battery wise before root?
Just simply rooting doesn't do jack squat. Any change in performance or battery life is just a coincidence/fluke.
Galaxy Nexus GSM
I'm rooting tomorrow .....I just wanted to show a base line test .... I drained the battery when I got it.. ..and then charged to 100 percent. ...this is a record of my first full battery cycle and benchmark results
Sent from my Nexus 7 using xda premium
before I fully charged, quadrant reported my device running At 1300 now I can't get past 1200 but it does read a Max CPU of 1300 I thought this was a 1200 device. ... we'll see what the devs can do. if any ANY of the guys from the epic4g touch come to this thread I have super high hopes .
And yes you are correct rooting alone doesn't do anything for performance. ...now custom kernels one the other hand...
nxt said:
Just simply rooting doesn't do jack squat. Any change in performance or battery life is just a coincidence/fluke.
Galaxy Nexus GSM
Click to expand...
Click to collapse
This. It does nothing by itself. It adds two files that don't do anything unless called upon by another app.
hey guys,
recently I discovered brilliant app ( Intel® Performance Viewer ) which can monitor cpu core usage and freqs in real-time. As I was always concerned about my Z4's underperforming 810 chip, I decided to test cpu in different apps. So heres one - M&B WARBAND which is emulated and requires a lot of horse power. I also spawned around 200 troops to harden the task. As you can see I got 5 FPS while Big Chip (A57) is literally sleeping. Naturally, A53 is struggling at getting playable framerate. Same thing happens in Antutu, GeekBench, PPSSPP, and in every power demanding apps( games, emulators and etc).
WTF is wrong with 810 CPU guys? or should I blame Sony for trash governors which can't figure out when they should activate all cores?
{
"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"
}
Just hope they fix this in marshmallow.
Sent from my E6533 using XDA Free mobile app
Can anyone test this again in MM? Would be greatly appreciated.
neestea said:
Can anyone test this again in MM? Would be greatly appreciated.
Click to expand...
Click to collapse
It's functioning much much better. There's another thread that shows benchmarks.
Sent from my E6533 using XDA Free mobile app
big.Little on this device runs HMP
The most powerful use model of big.LITTLE architecture is heterogeneous multi-processing (HMP), which enables the use of all physical cores at the same time. Threads with high priority or computational intensity can in this case be allocated to the "big" cores while threads with less priority or less computational intensity, such as background tasks, can be performed by the "LITTLE" cores.[10][11] source from Wikipedia.