Related
I think I may have a simple yet very inefficient method of ensuring stable overclock at higher frequencies. I have been messing around with many different OC kernels (along with many different roms ), and have noticed the same situation. While charging, all overclock speeds beyond 633 are pretty stable. It may take a few attempts to reach a certain speed (as the phone might reboot), but once successful its all golden!
I'd previously though instabilities were due to the fact that these kernels were undervolted and thus, after a certain frequency, needed more juice to function properly, but when I removed the charger. My god...it still ran! Just as effectively for extended periods of time.
The only problem was the phone would either reboot or hang if the screen was powered-off and idle/sleep for more than 1-3 secs. So I tried using SetCpu's profiles to lower the clock speed to various speeds below 633 during sleep. Yet to no avail. The phone would always freeze/reboot when it attempted to clock back up.
So if someone were to develop an app that would implement a toggle feature, or make modifications to the current kernels to disable sleep for test purposes I believe that might help. I am far too inexperienced a programmer to dev this but know there was a command under reference called "Partial Wake Lock" that can disable cpu sleep.
Also I realize, if implemented as is, this will destroy battery life. But with a good toggle switch it can be treated as an Overdrive mode!!!
Forgot to mention that while charging and clocked beyond 633 it always awoke with no problems.
My phone will clock to 710 before freezing up but it's crazy unstable. It seems to behave well at 652 with a freeze up roughly every 6-7 hours. I've never tried it that high with the charger though. Seems interesting.
extended batteries also reduce overclocking, my 2600mah battery peaks at 595, where as the official battery gets me to 633
-------------------------------------
Sent from my HTC Magic
I have exactly the same issue. My G1 runs stable on 672, while plugged in into
the charger. Even using GPS for navigation, browsing and so on, everything works great. As soon as the charger is plugged out and the phone goes into sleep it reboots.
I end up in changing the frequencies on demand with setCPU. When i need more speed, e.g. browsing the web, i set it manually to 672. And before putting it in my pocket i reduce to 614. Even on battery i can use 672.
Also tried profiles in SetCPU but this did not help.
BTW. Using 5.0.8t4, same was on t3
Damian
Nagoki said:
I think I may have a simple yet very inefficient method of ensuring stable overclock at higher frequencies. I have been messing around with many different OC kernels (along with many different roms ), and have noticed the same situation. While charging, all overclock speeds beyond 633 are pretty stable. It may take a few attempts to reach a certain speed (as the phone might reboot), but once successful its all golden!
I'd previously though instabilities were due to the fact that these kernels were undervolted and thus, after a certain frequency, needed more juice to function properly, but when I removed the charger. My god...it still ran! Just as effectively for extended periods of time.
The only problem was the phone would either reboot or hang if the screen was powered-off and idle/sleep for more than 1-3 secs. So I tried using SetCpu's profiles to lower the clock speed to various speeds below 633 during sleep. Yet to no avail. The phone would always freeze/reboot when it attempted to clock back up.
So if someone were to develop an app that would implement a toggle feature, or make modifications to the current kernels to disable sleep for test purposes I believe that might help. I am far too inexperienced a programmer to dev this but know there was a command under reference called "Partial Wake Lock" that can disable cpu sleep.
Also I realize, if implemented as is, this will destroy battery life. But with a good toggle switch it can be treated as an Overdrive mode!!!
Click to expand...
Click to collapse
The speeds will be different on different phones due to the hardware even slightly different depending on where the phone was made mine can go to 720mhz while others 614mhz which means unless another way of overclocking is found then we won't have a stable overclock for a while :/
mejorguille said:
My phone will clock to 710 before freezing up but it's crazy unstable. It seems to behave well at 652 with a freeze up roughly every 6-7 hours. I've never tried it that high with the charger though. Seems interesting.
Click to expand...
Click to collapse
Lemme know how that goes. I've noticed higher clock frequencies are much more stable while charging.
Jedipottsy said:
extended batteries also reduce overclocking, my 2600mah battery peaks at 595, where as the official battery gets me to 633
-------------------------------------
Sent from my HTC Magic
Click to expand...
Click to collapse
That's strange. Maybe its a voltage difference between batteries that makes its more unstable.
vassloff said:
I have exactly the same issue. My G1 runs stable on 672, while plugged in into
the charger. Even using GPS for navigation, browsing and so on, everything works great. As soon as the charger is plugged out and the phone goes into sleep it reboots.
I end up in changing the frequencies on demand with setCPU. When i need more speed, e.g. browsing the web, i set it manually to 672. And before putting it in my pocket i reduce to 614. Even on battery i can use 672.
Also tried profiles in SetCPU but this did not help.
BTW. Using 5.0.8t4, same was on t3
Damian
Click to expand...
Click to collapse
I believe when the phone is charging the operating system either suspends or extends idle/sleep when the screen backlight is off. This would explain why it reboots on battery and not while plugged in. Also the SetCpu profiles would work if only overclocking wasn't so unstable.
xillius200 said:
The speeds will be different on different phones due to the hardware even slightly different depending on where the phone was made mine can go to 720mhz while others 614mhz which means unless another way of overclocking is found then we won't have a stable overclock for a while :/
Click to expand...
Click to collapse
That is true, but if we can help the relative stability of each clock rate past 528 by using simple methods (i.e. overclocking while charging), we can simply aim to improve its reliability until a better way to overclock is found.
In this thread you will find a set a patches I've applied to pershoot's
kernel2635 source (https://github.com/pershoot/kernel-2635.git) in a
attempt to compile my own kernels and to fix the long standing and not cared of usb
battery drain bug (able to eat your battery in less than 2hrs).
A (outdated) list of the applied patches is:
001-fix_msm_clock_warning.patch
002_fix_msm_nand_warning.patch
003-2.6.35.13-sched-bfs-404.patch this is by Con Kolivas http://ck.kolivas.org/patches/bfs/2.6.35/
004-bfs_fix.patch
006-msm_evlog_fix.patch
007-hw3d_refdata.fix
008-htc_pwrsink_refdata.patch
009-board_trout_sapphire_fix.patch
010-eventpoll_fix.patch
011-dm-crypt_fix.patch
012-mt9t013_fix.patch
013-msm_smd_fix.patch
014-pm_fix.patch
016-mddi_refdata_fix.patch
017-lowmemorykiller_fix.patch
022-adb_2.6.29_forward_porting.patch
023-htc_battery.patch
024-msm72k_udc.patch
025-patch-2.6.35.11-12
026-BFQ-v2.patch
027-BFQ-v2-r1.patch
028-smd_rpcrouter.patch
029-audpp_missed_DMA.patch
030-msm_serial_hs.patch
031-irq_pm.patch
032-smd_tty.patch
033-linux-2.6.38.y.git-524429c31b486c05449666b94613f59f729c0a84.patch
034-10mb_32A.patch (MT1.2/Old 32a memory map)
035-9aa258a27b6183e8e80241e4820883eaed23139f.patch (Magic Plus (32a) extra 10MB ram)
036-kmalloc_b0937124b376946a5c93504f34ac932dffb23e3e.patch
037-2.6.36_lowmemorykiller+fudgeswap.patch
038-minfree_stats-bb4a7baa64d9a56124e1f13510e9688aeed0cc10.patch
039-msm72k_udc_fix_msm.git-1aa53ebd36088a60fcf4a498f763358598a477b9.patch
040-synaptics_warning_fix.patch
041-BFS-401-2388fb7aee855019c4a7560efb54cc7550a09743.patch
042-BFS-rr_interval_335f482a0274a640ae6ab1a0036a3b263de575b6.patch
043-i2c_msm_a146e17dd81a2e4eaf67928c945038f521409384.patch
044-BFS-1000Hz.patch
045-patch-2.6.35.12-13
046-zram.patch
047-vzalloc_for_zram_linux-2.6.38.y.git-e1ca7788dec6773b1a2bce51b7141948f2b8bccf.patch
049-pmem_c21c461ce3e32d26abebe6243039824839748dc5.patch
050-gingerbread_gadget_update.patch
051-adb_2.6.29_forward_porting.patch
052-msm72k_udc.patch
053_msm72k_udc_warning_fix.patch
054-ae9bd4d574b7b8480aee162273d58d0c3840510a.patch
055-ARM-zImage.patch
056-wifi-3e6f7025178699b354e0e9fd94331f47ebb82763.patch
057-arm-mm-cache-ecce0382ee54a765abcdc982e01a5fd30099f52d.patch
058-autogroup patches
059-patch-2.6.35.13-14
060-cpufreq_stat_fix.patch
configs for 2708, ebi0 and ebi1
Please refer to the attached patches.zip files for the latest
patch series.
Main features of this kernel are:
BFS (in the BFS versions)
BFQv2r1
Overclocking
various fixes and minor enhancements
autogroup patches (in the autogroup versions)
BUG 1 (adb):
Patches 1-2, 4-17 are rather trivial stuff as they just silence some warnings.
Patch 22 is the one that seems to fix or reduce the "usb battery drain bug"
in the sense that after applying this patch I was not able to trigger the bug
again and I've tried several times the last days. The same result was reported
by a few courageous testers that risked to install one of my precompiled kernels
and whom I would like to thank for their collaborative effort.
The steps used to trigger the bug were:
plug in usb
start adb session
remove usb plug
check if a sticky android os entry is in the battery stats (a sure sign of incipient drain)
The patch reverts f_adb.c to be more similar to how it was in kernel 2.6.29-msm.
Similar code could also be found in HTC's 2.6.35 sources for the Incredible S
at http://dl4.htc.com/RomCode/Source_and_Binaries/vivo-2.6.35-g89aa373.tar.gz
so it could also be a alternative to use this code base for future G1 kernels.
Attached you'll find also the config I used to build the kernels posted
in the ezGingerbread thread and in Enomther's thread.
I hope this patch fixes this bug also for you as it did for me
making me a happy G1 user again.
I would thank to all who collaborated to this effort with facts
or with their wise words and advices.
BUG 2 (drain after reboot with usb connected):
After studying more and more bug N°2 and thanks to the comments of the posters who sent me in the right direction
I've made a good progress. It is very early to call it a conclusive solution yet, but I was able to reboot my phone
with usb connected and after 3 hrs it is fully charged.
What did the trick was to disable:
CONFIG_SERIAL_MSM
in the kernel. I don't know what it was there for but at least
on my G1 I've tested all basic functions:
phone call
sms
data
wifi
BT
adb
music
GPS
and every thing seems to work. More test are needed tough,
there are also some minor leftovers to fix (more on this
in the next days).
For the bold a new kernel to test (tested on enomther's rom,
so I don't know if it will work on other roms).
You'll also find a VERY EXPERIMENTAL
anykernel/autokernel flashable zip archive with
EBI0/EBI1/2708+ kernels. Use it AT YOUR OWN RISK
and kindly report success or failure while flashing.
I cannot test it on all device/ROM combinations
so it may or may not work for you.
MAKE A BACKUP BEFORE USING IT so if something
goes wrong you can restore your previous rom.
I can give you very limited support due to missing
free time nonetheless patches are welcome!
Autokernel with BFS v0.401 and 1000Hz Kernel timer resolution for Froyo (discontinued):
auto-boot-2.6.35.13-farmatito-pershoot-ds-BFS+-20110428.zip
http://www.multiupload.com/8CKICMRK6B
MD5SUM 999770a413cbe93be75e00b1529f2300
Autokernel with BFS v0.404 for Gingerbread (experimental):
auto-boot-2.6.35.13-farmatito-pershoot-ds-BFS+-20110518.zip
http://www.multiupload.com/YRXWMK1AY3
MD5SUM c1373c915c8bfe3ebb470e839756a735
Standard Autokernel for Froyo (discontinued):
auto-boot-2.6.35.13-farmatito-pershoot-ds+-20110428.zip
http://www.multiupload.com/LLMKG4TRTO
MD5SUM ee3f5c53b4871076f123491c9dc388e2
Standard Autokernel for Gingerbread (stable):
auto-boot-2.6.35.13-farmatito-pershoot-ds+-20110505.zip
http://www.multiupload.com/0SJ77OM4HA
MD5SUM61a8bb913ca43a355e1eef3152b008db
Standard Autokernel for Gingerbread
with autogroup patches and memory compaction (experimental):
auto-boot-2.6.35.14-farmatito-pershoot-ds+-20110802.zip
http://www.multiupload.com/3NJ7Q0Y4TN
MD5SUM 27536ef42348dd92bb006cd8511df5d9
This kernels are unsupported they worked for me and I hope
they work for you, feel free to report problems and I will try to
fix them depending on my free time and skills.
USE AT YOUR OWN RISK. NO WARRANTY.
Enjoy
Changelog
v 20110425:
fixes to the installer automagic.
v 20110428:
BFS v0.401 + 1000Hz kernel timer resolution (BFS-version only) + rr_interval tuning.
i2c_msm HTC update
updated to 2.6.35.13
V 20110505:
revert kernel timer resolution to 100Hz
revert rr_interval tuning (BFS version)
update android gadget to gingerbread version.
V 20110518:
BFS v0.404 in the BFS versions
V 20110612
Compensate for rounding on odd-frequency clocksources
zImage fixes
Enable Memory Compaction
wifi - Don't make disabled irqs wake the device
cache-l2x0: Correct l2x0 initialization
autogroup patches
V 20110802
update to 2.6.35.14 (autogroup version only)
I'm glad to see someone working to fix the USB bug, I hope it will be squashed in pershoots official builds eventually as well
Good work! Will try it out.
A while back everything on my screen froze (time and battery level not updated) but otherwise the phone worked 100%, however the battery lasted 2 days and 20 hours (68hrs with wifi on, 3G on, 614 overclock, browsing and gmail, etc). Weird
Forgive me if my question feels like a noob but exactly how should we apply this zip file.....should I flash it?.... OR....it has to be installed through adb (or terminal emulator?)
I read the OP but couldnt make about the methos of installing it....(kinda stupid of me I know...
Is it OK to use your kernel instead of this patch?....do they have same effect?
dilwaladoctor said:
Forgive me if my question feels like a noob but exactly how should we apply this zip file.....should I flash it?.... OR....it has to be installed through adb (or terminal emulator?)
I read the OP but couldnt make about the methos of installing it....(kinda stupid of me I know...
Is it OK to use your kernel instead of this patch?....do they have same effect?
Click to expand...
Click to collapse
The patches in the zip need to be applied to the kernel sources, built and then
a anykernel zip installer must be created. Then you can flash it.
You can try also a precompiled kernel if it is compatible with your rom.
So best is to take a nandroid backup in case things go bad.
I suggest you to wait that it is included by the devs of the rom you use
if they see it fit.
Well done for keeping at it
My testing is as follows
Using the ezGingerbread binary on a clean ezGingerbread install with gapps+facebook but no wifi or sim:
The USB connection in use is just a wire to my macbook.
0) battery validation: boot system from battery only and leave for extended time.. I was at 83% after 13h.. this indicates no particular extra drain thus this test passed
1) basic test: boot while phone charging on macbook, after system is fully loaded unplug from USB, replug, unplug again.. this case the phone was drained in under 13h thus indicates the USB drain is present test failed
2) adv. test: boot phone on batter such as test 0, after test 0 drained to say 79% charge with usb slightly, the unplug usb again and leave.. hours later indicated no significant drain test passed.
3) adv. test 2: now at 60% after test2 plug into usb reboot and unplug after fully loaded.. such as in test1 drain quickly continued test failed.
Thus we seem to have a form of USB drain that is not in the 2.6.34.* kernels, however it may be possible on this kernel to avoid it by booting the phone on its own power (I did not test booting the phone on the A/C adapter, least not yet and more testing is needed to be sure there is no other oddities)
@ezterry :
so if understand it correctly it is booting/rebooting with
usb plugged in that still fails?
Do you see the same stuck "android os" entry in battery stats?
If not, than maybe it is a different bug, so more patching is needed.
UPDATE:
test:
plug in usb
reboot
wait a little while phone is charging
unplug usb
go to battery stats:
there you'll see "android os" entry
hit a few times refresh
"android os" %value decreases and after a few more refresh hits it disappears.
I think that if there is battery drain in this case it is not the same bug.
Will check the phone later to see how it behaves:
16.59 84%
18.18 77%
20.42 68%
16 % / 4hrs = 4% /1hrs (in idle state)
Looks not so bad to me... but definitely would not last
48+ hours as my battery usually lasts.
In my opinion this is not the same bug tough, because
what I and other users were experiencing was a very
fast battery drain after disconnecting from a adb
session. The latter bug is indeed fixed.
After more testing with this bug N° 2 triggered the power
consumption with my extended battery is stable at about
4%/hr. I've looked at the most likely candidates
htc_battery.c
msm72k_udc.c
but I've not spotted differences between 2.6.34.8 and 2.6.35.11
that could explain the different behaviour.
Hints and help is welcome.
Can some one explain that USB drain problem?
I already had change my battery but it hasn't make any difference...
My G1 can only work for 4h and them the battery is over.
That patch can fix it?
How do I flash it?
VAMCAVALO said:
Can some one explain that USB drain problem?
I already had change my battery but it hasn't make any difference...
My G1 can only work for 4h and them the battery is over.
That patch can fix it?
How do I flash it?
Click to expand...
Click to collapse
Check out post for and five on this page.
Sheesh
Lol
Sent from my Dream/Sapphire using XDA App
VAMCAVALO said:
Can some one explain that USB drain problem?
I already had change my battery but it hasn't make any difference...
My G1 can only work for 4h and them the battery is over.
That patch can fix it?
How do I flash it?
Click to expand...
Click to collapse
There's a few ways to improve you battery life. I went crazy myself, and finally got it working great.
#1 If you're still using the original battery in your G1, it's probably time to replace it.
#2 Some roms do better with battery life, some don't.
#3 Be careful what radio you use. The radio 2.22.27.08 is probably better for USA users, while 2.22.28.25 is better for other countries.
#4 Trying disabling stuff you don't use. Turn off Auto-sync, if you don't need constant updates for E-Mail and contacts backup. You most likely don't. Disabling background data helps, but you'll need to enable it to use any data. Disabling Data under network settings has no effect in how your phone functions, but does decrease battery drain.
#5 Try changing the clock speed of your phone. Most good roms come with built in overclock, and you can change the min CPU frequency to lower then 245 Mhz. Be careful in how much you lower it, cause anything that happens on your phone will kick in the Max CPU frequency, and suck battery power.
#6 Make sure everything is working, like the camera. For months I was going crazy on my battery drain, and just recently discovered my camera wasn't working. Turns out, the camera cable was slightly disconnected. This can easily happen, since the cable sits right under the battery. Took phone apart, plugged it back in, and now battery lasts for 2 days.
#7 Of course, make sure no services are running in the background. Running applications in the background can force your hones CPU to run at max speed.
As for the USB drain bug, basically when you plug your phone in to your PC, it can drain the crap out of your battery. So charging your phone with your PC is a bad idea, and you'll have to reset it to avoid it draining so fast.
Dukenukemx said:
There's a few ways to improve you battery life. I went crazy myself, and finally got it working great.
#1 If you're still using the original battery in your G1, it's probably time to replace it.
#2 Some roms do better with battery life, some don't.
#3 Be careful what radio you use. The radio 2.22.27.08 is probably better for USA users, while 2.22.28.25 is better for other countries.
#4 Trying disabling stuff you don't use. Turn off Auto-sync, if you don't need constant updates for E-Mail and contacts backup. You most likely don't. Disabling background data helps, but you'll need to enable it to use any data. Disabling Data under network settings has no effect in how your phone functions, but does decrease battery drain.
#5 Try changing the clock speed of your phone. Most good roms come with built in overclock, and you can change the min CPU frequency to lower then 245 Mhz. Be careful in how much you lower it, cause anything that happens on your phone will kick in the Max CPU frequency, and suck battery power.
#6 Make sure everything is working, like the camera. For months I was going crazy on my battery drain, and just recently discovered my camera wasn't working. Turns out, the battery cable was slightly disconnected. This can easily happen, since the cable sits right under the battery. Took phone apart, plugged it back in, and now battery lasts for 2 days.
#7 Of course, make sure no services are running in the background. Running applications in the background can force your hones CPU to run at max speed.
As for the USB drain bug, basically when you plug your phone in to your PC, it can drain the crap out of your battery. So charging your phone with your PC is a bad idea, and you'll have to reset it to avoid it draining so fast.
Click to expand...
Click to collapse
Thank you for the answer!
#1 I already replaced the battery
#2 I am using the Laszlo Froyo and it's know for your not so good battery performance.
#3 I from Brazil but using 2708 radio...should I change it?
#4 Only 2G and all unnecessary stuff its out.
#5 I use the laszlo built-in CPU settings at Extras>Performance at 176-528 ondemand.. it is OK?
#6 I'm sorry but I didn't understand your problem at this point. Which battery
cable? Mine camera it's OK right now..
#7 I'm pretty sure that I know there is no app in background but there is some way to check this out?
a) And I tried to flash today the 2.6.35.11 kernel to see if it help because with laszlo rom, my G1 became really nice again but the battery sometimes make me not that happy.
b) When I charge at PC (often), the only thing I need to do is to reboot after unplug, right?
Thank you very much
VAMCAVALO said:
#3 I from Brazil but using 2708 radio...should I change it?
#5 I use the laszlo built-in CPU settings at Extras>Performance at 176-528 ondemand.. it is OK?
#6 I'm sorry but I didn't understand your problem at this point. Which battery
cable? Mine camera it's OK right now..
#7 I'm pretty sure that I know there is no app in background but there is some way to check this out?
Click to expand...
Click to collapse
#3 You'll have to experiment to see which radio works best for you. I used 2825 before realizing that I never tried 2708. For me, 2708 was way better, but what works best for me might not be best for everyone. Since radios are made for specific regions.
#5 I'm also using Laszlo CPU settings like you are. BTW, same rom but my battery lasts for 2 days.
#6 I worded that incorrectly. I meant to say that my camera cable was lose, and the camera wasn't working. I didn't know this, cause I didn't use the camera for months. I fixed it, and now my battery life is 10x better. The cable for the camera sits under the battery, and can easily be pulled lose by dropping the phone.
#7 Aftermarket apps from the market provide the best way to check. Though if you're sure, then don't bother. It's not hard to see if an app is running still.
a) I'm using the kernel that came with Laszlo rom, but I've found that ezBiffTestKernel20110222-2708_S.zip works great for most roms.
b) Yea reboot after you unplug it. My battery has been doing so well lately, that I can wait till I get to my car to charger it. Using my car charger to avoid charging with the PC. [/QUOTE]
Dukenukemx said:
#3 You'll have to experiment to see which radio works best for you. I used 2825 before realizing that I never tried 2708. For me, 2708 was way better, but what works best for me might not be best for everyone. Since radios are made for specific regions.
#5 I'm also using Laszlo CPU settings like you are. BTW, same rom but my battery lasts for 2 days.
#6 I worded that incorrectly. I meant to say that my camera cable was lose, and the camera wasn't working. I didn't know this, cause I didn't use the camera for months. I fixed it, and now my battery life is 10x better. The cable for the camera sits under the battery, and can easily be pulled lose by dropping the phone.
#7 Aftermarket apps from the market provide the best way to check. Though if you're sure, then don't bother. It's not hard to see if an app is running still.
a) I'm using the kernel that came with Laszlo rom, but I've found that ezBiffTestKernel20110222-2708_S.zip works great for most roms.
b) Yea reboot after you unplug it. My battery has been doing so well lately, that I can wait till I get to my car to charger it. Using my car charger to avoid charging with the PC.
Click to expand...
Click to collapse
#3 I will try 2825 so!
#5 Holy ****! Two days I can only get leaving the phone on eternal standby...
#6 Now I understand, but my camera and other functions are normal right now.
#7 I'm sorry, but what is aftermarket apps?
a) 2.6.35.11 it's know to be a better kernel on the battery performance. Right now I'm testing 35.10 and I need to wipe my battery stats because I think it can be one of the problems.
b) Ok, that is not a problem because I charge at PC lot of times, so now I will reboot after unplugging.
Well, after all of this, if nothing works, should I change my battery again? I already changed at December 10 but it is a generic one.
TKS
I just flashed the kernel and I've had good results regarding the battery drain. No more high % "AndroidOS" under the battery stats.
The only thing I found to be weird is the touch screen. It seems like the responsiveness while scrolling through the settings, homescreen, and app drawer is laggy and unresponsive. It sometimes doesn't even scroll when I move my finger across the screen. Also pulling the notification bar is very difficult as I really have to slowly drag it down.
I currently am using the newest kernel released, the 04/03 one, on CyanogenMod nightly 307 on my G1. My old kernel was the "ezBiffTestKernel20101106-2708_S.zip"
Thanks for your work on the battery drain problem.
good223 said:
I just flashed the kernel and I've had good results regarding the battery drain. No more high % "AndroidOS" under the battery stats.
The only thing I found to be weird is the touch screen. It seems like the responsiveness while scrolling through the settings, homescreen, and app drawer is laggy and unresponsive. It sometimes doesn't even scroll when I move my finger across the screen. Also pulling the notification bar is very difficult as I really have to slowly drag it down.
I currently am using the newest kernel released, the 04/03 one, on CyanogenMod nightly 307 on my G1. My old kernel was the "ezBiffTestKernel20101106-2708_S.zip"
Thanks for your work on the battery drain problem.
Click to expand...
Click to collapse
Could be due to the use of BFS, maybe I'll post a kernel without it in the next days, as I'm testing other changes
right know.
farmatito said:
Could be due to the use of BFS, maybe I'll post a kernel without it in the next days, as I'm testing other changes
right know.
Click to expand...
Click to collapse
Ah ok, but what exactly is BFS? I did a quick google search and I came across this article "http://techfreaks4u.com/blog/posts/kernel-linux-kernel-with-bfs/", but I still don't quite understand how it affects our phones.
Could you explain it in a simpler way?
First two zips froze at the G1 screen using DangerSPL & proper radio, though all of them work fine using the 2.22.27.08/2.22.28.25 radio & appropiate SPL.
The phone doesn't sleep either.
Will test performance more thoroughly tomorrow.
good223 said:
Ah ok, but what exactly is BFS? I did a quick google search and I came across this article "http://techfreaks4u.com/blog/posts/kernel-linux-kernel-with-bfs/", but I still don't quite understand how it affects our phones.
Could you explain it in a simpler way?
Click to expand...
Click to collapse
It divides cpu time more or less in equal parts to all running tasks, so all (the more cpu intensive and less intensive) have
the possibility to run in a given time period, the contra is that
the more cpu intensive tasks may slow down a little.
Please excuse me for my ignorance, but I don't know much about these kinds of topics.
I wanted to know if anybody could be kind enough to explain the dangers and negatives of an overclocked CPU and an undervolted kernel?
I know their benefits because of some research I did, but I could never find a concrete answer explaining the negatives and dangers.
I've heard some horror stories of overheating handsets that get so hot that internal components fry, heard about damaged radios that need to be replaced, and loss of signal. But I'm not entirely sure if those instances are correlation instead of causation.
Any insight would be greatly appreciated. Thank you!
-Chris
Sent from my HTC Sensation 4G using XDA App
The general issue that applies to both modifications is that you are using the chips outside their specifications. Their whole behavior might no longer be as expected.
This is usually happening at such low level and in a so small range that it doesn't affect normal use.
Overclocking will definitely produce more heat. That's why people that overclock pcs to insane levels use non-standard cooling like dry ice or even liquid nitrogen.
As you can't change the way your phone will transport heat, there's only very limited room for overclocking.
The phone is designed to switch itself off if it gets too hot, however this is not something one should rely on.
Not sure about any specific risks of undervolting, but the general issues will definitely apply. Noone can guarantee for stuff to work as expected when you run components outside the specifications, as they were tested to run safe only inside the specs as supplied by the manufacturer.
It can cause permanent CPU damage which can lead to you bricking your phone, but the chances of that aren't that great. Usually if you undervolt too much, your phone will just reboot.
Stability is the biggest issue. It can put the components too far out of their comfort zone.
Unstable, unexpected behaviour and/or (in very strange cases drastically) reduced life expactancy. However, if you do undervolt your cpu, the only/main issue becomes unstable.
In my experience (lot of pc overclocking), you will notice when your material can't keep up with the settings and if you change it (back), no problems will occur.
aNYthing24 said:
It can cause permanent CPU damage which can lead to you bricking your phone, but the chances of that aren't that great. Usually if you undervolt too much, your phone will just reboot.
Click to expand...
Click to collapse
So would you say it's worth the risk to flash a ROM that has an overclocked CPU and undervolted kernel? I'm so scared to damage my device
Sent from my HTC Sensation 4G using XDA App
LPChris47 said:
So would you say it's worth the risk to flash a ROM that has an overclocked CPU and undervolted kernel? I'm so scared to damage my device
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Yes I would, in a way the lower voltage cancels out the higher voltage, and even produces less heat overall. There are no dangers of undervolting AFAIK, saving battery is good, although if you set the volt extremely low the phone will freeze up. Devs put the volt at a good level but most of the time you can lower it by a notch or increase it for no reason. If this phone ever gets 2GHz clock that would be a danger to run at, because the voltage would be insane.
It seems alot of people dont know the proper way to undervolt their phones, so I'm gonna try to help out! This is my first attempt at a guide, and i tend to ramble so just tell me if it makes no ****-for-sense
Undervolting is great, it allows us to change the voltage in our phones while we use it! this can really increase battery life and reduce heat in the phone. but if its not done right, it causes many more problems than it fixes.
When you are following this guide you WILL have issues! This is not a generic disclaimer, it is the TRUTH! the goal here is to find out where your phone stops working, and you cant do that without causing it to STOP WORKING.
once again: THIS WILL MAKE YOUR PHONE FREEZE, IT WILL HAVE AWFUL BATTERY LIFE, AND IT WILL MAKE BAD THINGS HAPPEN
But after its all done it should work much better
To start off, too much or too little voltage in the phone causes any number of things including:
Reboots (Screen Off and Screen On)
Lagging
Phone Overheating (Hot to the touch)
Reduced Battery Life (this includes the phone using more power, as well as reducing the battery's ability to hold a charge)
'Strange' issues with things shutting off/not working (WIFI, Bluetooth, your favorite app, ect...)
Many other 'weird' things
If you are having any of the above issues, and you are using a custom kernel, they may be caused by inproper undervolting.
THIS CAN BE THE CASE EVEN IF YOU HAVE NOT DONE ANY UNDERVOLTING YOURSELF!!!
Most custom kernels have undervolting build into them, and even 'stock voltage' versions allow overclocking, and those frequencies have no 'safe' voltage associated with them.
How to Properly Undervolt your Phone:
*this assumes you have no idea where to start, if you have some past experience, USE IT!!!*
First, Undervolting a phone the right way is not a quick job, like most things in life the more time you put into it the better your end result will be. For me i like to take an ENTIRE WEEK OR MORE to get all my settings down right. whenever you decide to do this, expect any and all of the issues i listed above to happen while you are trying to find the right settings.
Step 1: Starting Fresh
Disable all overclocking, undervolting, AND PROFILES on the ROM, you need to get the stock speeds working before you try to push the phone to its limit.
This will be your baseline. Use the phone like you normally do, text, call, surf the web, even let it sit in your pocket for a while. Do this for as long as you need to to be sure that everything is stable.
If you have any issues during this stage. STOP! add +25mv to every frequency across the board and start over. Do this up to 3 times if necessary, if after you have added +75mv to your stock voltage and you are still having issues, it is most likely something else in the rom causing the issue (rogue app, wrong kernel version, phone was dropped in the toilet too many times...) try to fix that first, or just try to ignore the issue, its up to you.
Otherwise, if everything is stable, Continue to step 2!
Step 2: Start Lowering Voltages
Lower all of the voltages by -25mv across the board. (If your phone needed any voltage added over stock to be stable, skip this step.)
This is where you begin testing the waters. Once again use the phone like normal, including some screen off time, as well as some CPU intensive tasks (playing music while websurfing, gaming, ect.)
If your phone is still stable after a good amount of time, then do it again. Your looking for the moment when things start to go wrong.
When you notice your first random reboot, or you start to feel the phone getting hot, or not responding STOP! you found the limit of your phone. Go back to the last working voltages you have and use them for step 3.
The more time you spend at this step the better your overall result will be! if you dont get any symptoms in an hour, they might show up later in the day, or overnight. Just take your time and have some patience.
Step 3: Lowering Voltages Independently
Now that you have a stable working phone. you can start lowering voltages one by one!
Starting with the lowest frequency, lower the voltage by -25mv.
Run this for a while, until you feel it is stable. Then move to the next highest voltage and do the same.
*If you have any issues, undo ONLY that frequency!!! Write down that frequency somewhere. you are done with it! you know that frequency is stable, and you shouldn't need to touch it again!!!
Keep doing this till you get to your stock maximum frequency, then continue to step 4!
*NOTE:* if any 2 voltages have more than a 100mv difference (125mv difference on Morfic's Kernels) between them, you need to raise the others around it to be equal or less than that. For exampe:
if at 1ghz, the phone is at 1000mv and at 1.2ghz the phone is at 1150mv. the higher one needs to be lowered (set 1.2ghz to 1125mv). if that is not stable for you then you must raise the lower one higher (set 1ghz to 1025mv).
Step 4: OVERCLOCKING!
At this point you should have a completely stable phone with no overclocking, grats! Now you get to start raising the frequency.
starting with the next highest frequency, set it to its stock voltage. if this is more than 100mv (125mv for Morfic's kernels) more than the previous frequency, set it to 100mv (125 for morfic) more than that.
run this until it is stable, and keep reducing it as much as you feel until you find instability. set it one step higher and move on to the next highest frequency.
if, after setting the voltage to 100mv (or 125mv) more than the last one, it is not stable, you need to raise the lower frequency's voltage up. sometimes this can cause a chain reaction that makes you raise 3, 4, or even all of the other frequencies up, if this happens you need to decide if that frequency is worth it to raise all the other frequencies to the next level.
If all is running good, proceed to step 5!
Step 5: The part where you hate me
(this step is optional, its just something i do to help with stability)
Now that you have a fully overclocked phone that is running as low of a frequency as it can safely, raise all of the voltages up by +25mv!
yes yes, i know, it sounds retarted to just undo that hard work and all that time you just put into finding the perfect voltages, but just hear me out.
Even if you spent a week on each step, did everything perfectly and tested everything you ever do on your phone and it is all completely stable. one day you are going to do something that will push the phone, which is running at its limit. so by adding 25mv to everything you are giving yourself some insurance. you may loose some battery life (i honestly don't ever notice a change with only 25mv) but when your phone alarm goes off in the morning to get you up for class, or you get that call you got that job you wanted, just be happy its not frozen on the table, or black screened in your pocket.
There you go! you should now have a stable phone with great battery life, and now you can stop bugging the devs about 'that strange reboot that is still there' or 'how every time you use his kernel you get black screens'
To Long; Didn't read Version:
If your having issues with your phone and you think its related to UV, and your much too busy/lazy/cool to read the above, try this: (Results will most likely be worse...)
Set (all of) your lowest voltages to 775mv (or 750 if you think your phone can do it)
Set your 1ghz voltage around 1000mv (give or take 50-100mv)
Set the highest speed to no more than 100mv below its stock seting.
Set the rest of all the speeds below 1ghz on a line between it and the lowest, and after 1ghz on a line between it and the highest. ex(From Morfic's T15 Kernel):
{
"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"
}
Post any questions or feedback you have, ill try to answer it as best i can!
Truly a great guide. I agree mostly with the last part, my alarm stopped ringing two days in a row, so I added 25 mv across the board, and it works perfectly. Thank you on behalf of the community, everyone will appreciate this guide for sure.
Helped fix an overheating problem!
Sent from my LG-P999 using XDA
This is done using setcpu?
Sent from my LG-P999 using XDA
imoumni said:
This is done using setcpu?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Any CPU managing app. I use CPU Master but there's lots more options out there. I don't use SetCPU because it took nearly a year to update.
Sent from my amazing LG G2x running Bionix Reloaded v1.4
Klathmon said:
*NOTE:* if any 2 voltages have more than a 100mv difference (125mv difference on Morfic's Kernels) between them, you need to raise the others around it to be equal or less than that. For exampe:
at 1ghz, the phone is at 1000mv if at 1.2ghz the phone is at 1200mv. the higher one needs to be lowered (set 1.2ghz to 1175mv). if that is not stable for you then you must raise the lower one higher (set 1ghz to 1025mv).
Click to expand...
Click to collapse
First off, thanks for this guide. I do rely on my phone's alarm clock pretty regularly so I'll have to start setting another alarm clock while I do this. Also, consider posting this in Android General to reach a larger audience.
My only question: I understand what you're saying, but I think your example may be incorrect. 1200mV - 1000mV = 200mV difference, so you would need to change one or the other by 75 to 100mV, right?
This is done using setcpu?
Click to expand...
Click to collapse
It can be done with any app that works with this phone.
I use an app called "System Tuner Pro" because it allows you to add voltage from stock settings (my phone seems to like a minimum voltage of 775 vs the 750 that most kernels start with) and im not sure any more but i think its free...
r4d14n7 said:
My only question: I understand what you're saying, but I think your example may be incorrect. 1200mV - 1000mV = 200mV difference, so you would need to change one or the other by 75 to 100mV, right?
Click to expand...
Click to collapse
thanks, yeah thats what i meant to say
All Fixed
Klathmon said:
It can be done with any app that works with this phone.
I use an app called "System Tuner Pro" because it allows you to add voltage from stock settings (my phone seems to like a minimum voltage of 775 vs the 750 that most kernels start with) and im not sure any more but i think its free...
thanks, yeah thats what i meant to say
All Fixed
Click to expand...
Click to collapse
No problemo. Looks like System Tuner is free but the Pro version is $3.99. How is it on resources? That's the only thing that worries me about these jack-of-all-trades apps.
r4d14n7 said:
No problemo. Looks like System Tuner is free but the Pro version is $3.99. How is it on resources? That's the only thing that worries me about these jack-of-all-trades apps.
Click to expand...
Click to collapse
it keeps a service running all the time, but is very CPU friendly, and wont hog resources. So far it hasn't been a problem for me at all.
and just for full disclosure; the dev is a close friend of mine, so i may be a bit biased
EDIT: added a quick "help im lazy" version for people that dont want to put the time/effort into doing it the right way.
Sent from my LG-P999 using Tapatalk
thanks for this
Thank you, this was very helpful!
Thanks for taking the time to make a great post.
I just started to OC/UV my G2X. I will use this as a guide.
-Thanks again
a noob question, Whats the difference between an app (eg, setcpu, pimpmycpu etc etc) lowering the voltage for you and "one doing it via your guide"
cricketAC said:
a noob question, Whats the difference between an app (eg, setcpu, pimpmycpu etc etc) lowering the voltage for you and "one doing it via your guide"
Click to expand...
Click to collapse
not really sure what you mean, to the best of my knowledge, no programs out there automatically undervolt for you. you use those programs to reduce or increase the voltage in each frequency yourself.
Hope that helps
Klathmon said:
not really sure what you mean, to the best of my knowledge, no programs out there automatically undervolt for you. you use those programs to reduce or increase the voltage in each frequency yourself.
Hope that helps
Click to expand...
Click to collapse
sorry, my bad. I just flash faux kernel. I thought all frequencies worked at the same voltages (silly me!) lol. Thatswhy when i saw there were different voltages for every frequency, i thought this guide was about that. (i.e i thought faux already did it for us in his kernel). lol
If my phone is stable at the current voltages that came with faux kernel, should i still try lowering them?
How much of a battery life can i get if i lower them by -25mv?
Lets say, i flash another kernel in the future and then reflash any oc/uv later on. Do i have to do these steps again or just simply input the (uv)values which i get after doing it right now?
cricketAC said:
sorry, my bad. I just flash faux kernel. I thought all frequencies worked at the same voltages (silly me!) lol. Thatswhy when i saw there were different voltages for every frequency, i thought this guide was about that. (i.e i thought faux already did it for us in his kernel). lol
If my phone is stable at the current voltages that came with faux kernel, should i still try lowering them?
How much of a battery life can i get if i lower them by -25mv?
Lets say, i flash another kernel in the future and then reflash any oc/uv later on. Do i have to do these steps again or just simply input the (uv)values which i get after doing it right now?
Click to expand...
Click to collapse
its up to you. personally, i would follow the "if its not broken, dont fix it" rule. if your happy with the current battery life, and you like the stability, no need to change it. But if you really want to go for broke, and squeeze every last bit of battery life out of this phone, then by all means go for it (you can ALWAYS undo it all) although -25mv most likely wont make much of a difference.
and to the second question, as long as its the same kernel, the same values should be alright, but each kernel is different. (i can get -50mv more on faux123's kernels, but i get better battery life on Morfic's even with the higher voltage)
Since we all have the same phone couldn't we all use the exact same voltages? and are the ones pictured yours?
noxary said:
Since we all have the same phone couldn't we all use the exact same voltages? and are the ones pictured yours?
Click to expand...
Click to collapse
Voltage depends on the chip (CPU) you have - every chip is different. you need to try playing with it according to what your chip can endure.
Klathmon said:
its up to you. personally, i would follow the "if its not broken, dont fix it" rule. if your happy with the current battery life, and you like the stability, no need to change it. But if you really want to go for broke, and squeeze every last bit of battery life out of this phone, then by all means go for it (you can ALWAYS undo it all) although -25mv most likely wont make much of a difference.
and to the second question, as long as its the same kernel, the same values should be alright, but each kernel is different. (i can get -50mv more on faux123's kernels, but i get better battery life on Morfic's even with the higher voltage)
Click to expand...
Click to collapse
If I end up squeezing every bit of juice, wouldn't that make my charger life short?
This guide needs a sticky!
Thank you for taking the time to write this.
I don't want to jump to any conclusions, but it does kinda make sense. I am seeing what "appears" to be a pretty solid increase in battery life during browsing and bulk transfers. I was able to download 3.5gb of data over wifi at about 1MB/s (around 1hr of nonstop transfer, data for Horn and NOVA3) and only knock off 17% of the battery with only 2bars. I am currently at 3:35/5:47 screen-on for the day and still have 68% left. The nonstop pulling is worse than regular browsing, and at this pace getting to the 8hrs of browsing seems like an actual possibility. As I am running on Balance with CleanROM 3.4.4 at the moment, switching to powersave could probably eek out addition gains.
IF YOU BLOW SOMETHING UP DO NOT BLAME ME...ETC ETC ETC
If anyone wants to check this out, and see if it's just fluke, here is what I have tried.
..pre-post revision...I started out doing the changes manually via terminal, but found some resources on XDA and the play store to make it a bit easier, so I am linking that stuff instead. A user has a pretty good guide for the Thunderbolt that I retested with and it works fine.
Just follow the steps here Solved: WiFi TXpower app error issue with missing iwconfig file to get the iwconfig file, and the links for the WIFI TXpower app.
I used Root explorer, so renaming the iwconfig.txt, moving it to xbin, and changing perms was trivial. As for WIFI Txpower, I have been running on 4db(398 DBM) with no really noticeable problems. I imagine it may have a steeper dropoff based on distance, but the plastic strip on the TF700 really fixed the range issue.
..UPDATE: I have noticed that when you turn the device on after a wifi sleep event, it seems to come back up full blast. So my estimates may be off by quite a bit, as I didn't check it between downloads and browsing sessions. Tom make the settings stick, there may need to be some modifications to the init scripts. I just wanted to get this info into the hands of more people to poke at, and determine if this is something worth adding to Aroma for our TF700 roms.
Day one with lots of power switching back to lower levels. Balanced mode with stock _that at interactive + row. Auto brightness.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Looks promising
Thanks for reporting this -- and thanks for trying.
Which interface name does it report in your case -- I get a wlan0 interface name instead of the eth0 reported in the original thread. I just picked wlan0, as it stays there even if I pick "Auto".
EDIT: I used Root Explorer succesfully -- no trouble remounting /system as R/W, so the one fluke I found may reside in the original thread.
Yes, it should be wlan0 for the wireless. The biggest problem is that after the interface goes to sleep (screen timeout), it will come back up at full burn, and you have to turn it down again. It will need to be cook into the ifup scripts to make it survive.
helfrez said:
Yes, it should be wlan0 for the wireless. The biggest problem is that after the interface goes to sleep (screen timeout), it will come back up at full burn, and you have to turn it down again. It will need to be cook into the ifup scripts to make it survive.
Click to expand...
Click to collapse
thanks for the tip! seems to be the real deal!
i had a test and notice only the 4 and 11 seem to line up with our tf700's ... is same for you?
stock @ 1496dBm
[email protected]
[email protected]
others don't seem to change on mine?... and no button for getting back to stock(full power)...
Yes I think we really just need to call true power via dbm to be accurate. The wifi power app was a quick way for people to validate what I was experiencing. I want to do some more playing around over the weekend and maybe a mod for cleanrom to handle the sleep issue. I am seeing a pretty significant drop in power drain while browsing and doing anything with wifi. I am having to force usage patterns to drain the battery versus just firing up a browser or online game.
snypa said:
thanks for the tip! seems to be the real deal!
i had a test and notice only the 4 and 11 seem to line up with our tf700's ... is same for you?
stock @ 1496dBm
[email protected]
[email protected]
others don't seem to change on mine?... and no button for getting back to stock(full power)...
Click to expand...
Click to collapse
You can use the command line to change the parameters. Use "iwconfig wlan0 txpower 1"to get down to 100dbm. Which works great as lo g as you are near the router.
"iwconfig wlan0 txpower 15" brings you back to 1496dbm
I am running this now with lowest settings for almost 24h.
I am not seeing any improvements in battery life.
jupppo said:
I am running this now with lowest settings for almost 24h.
I am not seeing any improvements in battery life.
Click to expand...
Click to collapse
It currently resets on (at least wifi) sleep, so you shouldn't be seeing any improvement unless you kept your poor 700 awake all those 24 hours.
The criterion is the "screen on" time, which may well be longer with the mod in place and active. Don't forget to activate it every time you wake up the 700.
I'm not sure when it was incorporated, but I know the 'Wi-Fi optimization' option in the advanced Wi-Fi settings effectively does this dynamically. If I recall correctly, it showed up after the last stable release but I've certainly noticed a big difference in battery life since I keep my Wi-Fi on always.. and no need to iwconfig depending on how much traffic you're planning on pushing! Anyway, it would be under Settings -> Wi-Fi -> (Menu) -> Advanced -> Wi-Fi optimization and that seems to do the same sort of thing and takes into consideration some of the weird PM issues related to the hotspot AP code. Just my two cents though..
MartyHulskemper said:
It currently resets on (at least wifi) sleep, so you shouldn't be seeing any improvement unless you kept your poor 700 awake all those 24 hours.
The criterion is the "screen on" time, which may well be longer with the mod in place and active. Don't forget to activate it every time you wake up the 700.
Click to expand...
Click to collapse
Yes thank you, but that was mentioned earlier already and I took it into consideration and switched back on every use.
I have 6h screen time with reduced tx settings as well as without.
Really no effect here. I also reduced to 100dbm.
jhannah01 said:
I'm not sure when it was incorporated, but I know the 'Wi-Fi optimization' option in the advanced Wi-Fi settings effectively does this dynamically. If I recall correctly, it showed up after the last stable release but I've certainly noticed a big difference in battery life since I keep my Wi-Fi on always.. and no need to iwconfig depending on how much traffic you're planning on pushing! Anyway, it would be under Settings -> Wi-Fi -> (Menu) -> Advanced -> Wi-Fi optimization and that seems to do the same sort of thing and takes into consideration some of the weird PM issues related to the hotspot AP code. Just my two cents though..
Click to expand...
Click to collapse
The Wi-Fi optimization option is not available in stock roms. I think that this is essentially what the non-Asus roms are doing with their wifi. The problem is that none of the non-Asus roms have made it to the 100% functionality mark, compared to something like CleanROM. If the day arises that they do, I would drop the stock rom in a NY minute, but until then, they are not complete replacements for me.
That being said, will you conserve power via wifi when running a aosp rom with these adjustments, probably not, but the aosp roms have never given me the battery life of CleanROM to begin with so it balanced out. I am having no problems breaking 8hrs screen on time with a stock rom and wifi adjustments.
jupppo said:
Yes thank you, but that was mentioned earlier already and I took it into consideration and switched back on every use.
I have 6h screen time with reduced tx settings as well as without.
Really no effect here. I also reduced to 100dbm.
Click to expand...
Click to collapse
What rom are you using? If you are not on a stock rom like CleanROM, see my previous post.
helfrez said:
What rom are you using? If you are not on a stock rom like CleanROM, see my previous post.
Click to expand...
Click to collapse
Latest CleanROM version. iwconfig is working and new settings gets confirmed, but I have 0 power savings from it.
jupppo said:
Latest CleanROM version. iwconfig is working and new settings gets confirmed, but I have 0 power savings from it.
Click to expand...
Click to collapse
No disrespect intended, but I doubt it is zero. It may be minimal and contingent on usage, which is why the feature is available in aosp roms. I doubt this is the optimal way of using it. What I can say is with my usage patterns I was getting an average of about 5-6hrs absolute tops on balanced with stock _ that kernel and auto brightness, and now I can normally get over 7of heavy browsing consistently.
YMMV
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
helfrez said:
No disrespect intended, but I doubt it is zero. It may be minimal and contingent on usage, which is why the feature is available in aosp roms. I doubt this is the optimal way of using it. What I can say is with my usage patterns I was getting an average of about 5-6hrs absolute tops on balanced with stock _ that kernel and auto brightness, and now I can normally get over 7of heavy browsing consistently.
YMMV
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Whether it is 0 or 1% doesn't really matter for me. What matters is that is practically has no impact. I tried on 2 transformers now (one with CROMI and one with stock).
So it would be interesting to see the difference and see why your prime has significant power savings and others not
Unless there is some movement I will throw iwconfig from my tablets.
Anyway, thanks for trying.
jupppo said:
Whether it is 0 or 1% doesn't really matter for me. What matters is that is practically has no impact. I tried on 2 transformers now (one with CROMI and one with stock).
So it would be interesting to see the difference and see why your prime has significant power savings and others not
Unless there is some movement I will throw iwconfig from my tablets.
Anyway, thanks for trying.
Click to expand...
Click to collapse
I'm not using a Prime this is the TF700 Infinity forums. And feel free to toss it from your tablet though every other none stock rom includes it for a reason. If you have nothing further to add other than "my smartassv2 cfq hundkernel undervolted overclocked device doesn't magically have 10hrs of screen on time", please dismiss yourself from this thread. All devices are not made equal, and maybe your particular device(s) are not effected by these changes.
What is a fact is that different people have different experiences with these devices, some perform better than others in different situations. What I can state is that I am able to consistently get over the previous 6hr average, with my specific device, by babysitting the txpower.
I posted this information FYI and YMMV, so can we just leave it at that. If it is irrelevant, and doesn't work for anyone, the thread will age off of the page by itself. Thanks
Welp, that escalated quickly.