12/29/2011, 01:54 AM
|
#43 (permalink) |
|
Member
![]() |
Are you making a new profile? You need to save changes into a profile.
Mine: 128Mhz: 800mV 245Mhz: 800mV 368Mhz: 800mV 768Mhz: 825mV 806Mhz: 850mV 1Ghz: 875mV 1.2Ghz: 950mV 1.4Ghz: 1050mV 1.5Ghz: 1125mV 1.6Ghz: 1200mV 1.8Ghz: 1250mV 1.9Ghz: 1325mV Last edited by kill_Dano; 12/29/2011 at 02:02 AM. |
12/29/2011, 02:26 AM
|
#44 (permalink) |
|
Member
![]()
Posts: 795
|
yes.
I do the following advanced settings cpu frequencies cpu voltage change value e.g. 1.4 to 1249mv swipe back apply settings swipe back save as new profile when I look at the profile details or go back to voltage settings it still says 1250mv. do I need dev mode on or beta access to preware? |
12/29/2011, 10:56 AM
|
#45 (permalink) | |
|
Member
![]()
Posts: 30
|
Quote:
|
|
12/31/2011, 05:04 AM
|
#46 (permalink) | |
|
Member
![]()
Posts: 795
|
Quote:
Tried un-installing and reinstalling UberKernel but no change. (
|
|
01/03/2012, 02:53 PM
|
#50 (permalink) | |
|
Developer
![]() |
Quote:
-- Rod
__________________
WebOS Internals and Preware Founder and Developer You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful. All donations go back into development. www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals |
|
02/08/2012, 09:28 AM
|
#52 (permalink) |
|
Member
![]() |
great article on XDA developers: In Depth Nexus S Battery Study Brings About Surprising Conclusions | xda-developers
"No gain to be had from undervolting either ARM or INT voltages. I tested this to the extreme." I wonder if the result is applicable to our Pre 3 as well. Personnaly, I don't see any battery gain from underwolting, my pre battery life has always been fine! |
02/08/2012, 10:43 AM
|
#53 (permalink) |
|
Member
![]()
Posts: 795
|
Interesting read and the guys clearly put in a lot of effort. Still i'd be surprised if something isn't amiss in the setup. Chip makers wouldn't go to all that effort of setting different voltages for different speeds if it wasn't needed.
Looks like there are a few things need to be double checked before the result stands. 1) Effect of CPU load. ARM chips are really aggressive at turning off unused blocks when not being used. 2) Possibility that the UV settings weren't being enabled properly. |
![]() |
|
| Thread Tools | |
| Display Modes | |
|
|



