PowerSaverKernel - Usb battery drain bugs solved [UPDATED 2011/08/07] - G1 Android Development

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.

Related

[KERNEL][GB][EXPERIMENTAL] Entropy's Daily Driver (Video Fix 3/4/2012)

OK, since up to now few custom kernels have been released for Gingerbread, much of it due to fear of having to deal with the same stuff gtg465x has had to deal with for Infusion 2.0, I've had enough people ask what kernel I'm running to decide I'll post a compiled binary.
This kernel is my daily driver, it is what I have used for the past few days. I am posting it as-is with no support given. Flash it at your own risk, the only endorsement I give it is that I'm happy with its current state.
I'm on business travel at the moment so don't have time to do any support. Don't PM me with questions on how to flash this or bug reports. If you don't know how to flash a backup made with SGS Kernel Flasher, this kernel is not for you.
This kernel was built by taking the following three branches from my git repo and merging them into each other:
charginghacks
voodoo_sound
uv_only
As such, it has most mainline kernel fixes listed in my git repo thread.
It also has a preliminary implementation of Voodoo Sound initially committed by Bedwa. Based on talking with Supercurio, the apparently missing feature "speaker tuning" is only applicable to the Nexus S - if anything, some other devices may have this enabled when it shouldn't be. However, I have seen one or two reports that dock audio redirection may have issues which I need to investigate.
It has voltage control implemented but no overclocking. Be careful, this implementation from Netarchy allows you to overvolt in addition to undervolting. You could really fry something.
It also has an experimental battery charging algorithm. It should charge a battery faster from deep discharge (but slowing down near topoff, and in fact topping off slower than stock), and has so far successfully held my battery at around 85-90% state of charge when running Navigation in a car dock at full brightness. (It adjusts charge current downwards as battery voltage increases, to avoid worrying about whether charge termination will work properly when under load.) It's experimental, it could fry your battery, it might be wearing mine extra fast (but I doubt it personally) - if I've screwed up I get a significant discount on accessories.
So again - this is as-is, with no support provided as I don't have anywhere close to the amount of free time gtg has for supporting Infused.
Some time down the line I may formally release a supported kernel, but right now is not the time.
Two things to note that applies to all kernels with working CurrentWidget support at this time:
1) We have no way of measuring battery discharge current that I know of, just charge current. If you know of a GalaxyS device with working discharge reporting, please point me to a kernel that implements it.
2) On our device, the values reported by the kernel are 1.83 times the real charge current. I've debated fixing this, but it would break anyone who has already implemented scaling in userland, and it's behaving just like stock Froyo did.
Updates, see post at
http://forum.xda-developers.com/showpost.php?p=17890956&postcount=108 for 9/26,
and http://forum.xda-developers.com/showpost.php?p=18665215&postcount=225 for 10/22,
and http://forum.xda-developers.com/showpost.php?p=18997360&postcount=242 for 11/2,
and http://forum.xda-developers.com/showpost.php?p=19832752&postcount=306 for 11/27 (created 11/27 but posted 11/29)
3/4/2012 is just a fix for video decoding in newer firmwares
Edit: Also, if coming to this kernel from Infusion, reset all your voltage and OC settings back to stock. The voltage control mechanism in Netarchy-style kernels like this one is different from that in Infusion, the difference could cause weird things to happen. For this matter, you should reset voltage/OC settings back to stock before flashing ANY new kernel unless the kernel dev specifically instructs you to do something before flashing.
This kernel, like any kernel for Samsung-stock-derived ROMs, is NOT compatible with CM7/MIUI. (I just realized I say this on my GSII thread, but not here.) Flash this on CM7/MIUI and you'll softbrick. The only thing this has that CM7/MIUI kernels don't is charginghacks anyway...
No HDMI support - It will crash if you plug in an MHL adapter when running a UCKI3 or later leak, will do nothing on UXKG3
Entropy512 said:
OK, since up to now few custom kernels have been released for Gingerbread, much of it due to fear of having to deal with the same stuff gtg465x has had to deal with for Infusion 2.0, I've had enough people ask what kernel I'm running to decide I'll post a compiled binary.
This kernel is my daily driver, it is what I have used for the past few days. I am posting it as-is with no support given. Flash it at your own risk, the only endorsement I give it is that I'm happy with its current state.
I'm on business travel at the moment so don't have time to do any support. Don't PM me with questions on how to flash this or bug reports. If you don't know how to flash a backup made with SGS Kernel Flasher, this kernel is not for you.
This kernel was built by taking the following three branches from my git repo and merging them into each other:
charginghacks
voodoo_sound
uv_only
As such, it has most mainline kernel fixes listed in my git repo thread.
It also has a preliminary implementation of Voodoo Sound initially committed by Bedwa. LinuxBozo has identified some likely code deficiencies so it is likely not fully working. I never used VS heavily enough to judge this properly.
It has voltage control implemented but no overclocking. Be careful, this implementation from Netarchy allows you to overvolt in addition to undervolting. You could really fry something.
It also has an experimental battery charging algorithm. It should charge a battery faster from deep discharge (but slowing down near topoff, and in fact topping off slower than stock), and has so far successfully held my battery at around 85-90% state of charge when running Navigation in a car dock at full brightness. (It adjusts charge current downwards as battery voltage increases, to avoid worrying about whether charge termination will work properly when under load.) It's experimental, it could fry your battery, it might be wearing mine extra fast (but I doubt it personally) - if I've screwed up I get a significant discount on accessories.
So again - this is as-is, with no support provided as I don't have anywhere close to the amount of free time gtg has for supporting Infused.
Some time down the line I may formally release a supported kernel, but right now is not the time.
Click to expand...
Click to collapse
Ty much entropy
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Options! im going to give this a run for a few days thanks brah.
Sent from my SAMSUNG-SGH-I997R using XDA App
This is great. I love seeing development pick up again. I'll have to give this a shot as well as bedwas kernel. And I hope for the sake of all you devs that the noobs start to learn how to treat the forum. Keep up the great work!
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Very nice. Will give it a shot. I am in the car 8 hours a day streaming music via bt.. talking on the phone and using navigation. Battery is always an issue this may do the trick.
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
thanks entropy - gonna try it out.
waiting to hear some feedback from some of u that have downloaded this, would really love to try this out but i want to make sure everything seems A-ok. I'll be coming from bionix infinity if that makes any difference.
It does make a diff being that bionix infinity is a froyo based rom. i havent released the gingerbread. version yet.
Great? No: GREATEST!
I have installed it yesterday, and I noticed the phone more fast and responsive than usual. I also noticed the battery consumption now looks lighter: much better than before. And no rainbow at all.
You and GTG should work for Samsung development. If you do, we can say we're in good hands.
Your work is much appreciated.
Greetings from Rio.
P.S.: My phone uses Infused V2 Beta 3, And there's no rainbow, no freezing, thanks to you, Bozo and our friend GTG. Owe you!
Probably a dumb question but can a Gingerbread based Kernel work on a Froyo O/S such as the Froyo version of Infused?
I am unable to use GB due to the issues many people have with the compass in GB.
http://code.google.com/p/android/issues/detail?id=16741
http://forum.xda-developers.com/showthread.php?t=1109921
and thousands of other hits on this issue in Google.
The charging stuff would be awesome. I was rather disappointed to see that navigation +screen with a car charger would drain the battery. That seems like a basic problem with using it as on-dash navigation. (And they sell a freaking car dock for that.)
There should not be any significant differences in terms of battery life compared to other gingerbread kernels - undervolting will give you a slight improvement. Undervolting buys you a little bit but not too much (unless you're lucky and have a CPU that can undervolt by 100 mV at more at the lower voltages)
My battery tweaks ONLY affect charging on AC, and don't do anything when off the charger
I'd really like to claim super-awesome-battery-improvements, but the reality is that when kernel devs claim this, 95% of the time they're BSing. (Exception: Gingerbread vs. Froyo, but that's the whole kernel + userland package)
Did another long drive today - again, held at around 85-90%. I'll try to dig up a currentwidget screenshot from last week.
Attaching some screenshots of CurrentWidget logs.
One is a log taken while driving with nav on full brightness. Look at how it periodically bumps charge current up to 700 mA - it looks like nav with full brightness needs just a shade over 600 mA. The voltages that trigger state changes are such that this translates to around 85-90% battery.
One is a log taken while charging my new 3500 mAh extended battery from 59%. (I forgot to log the voltages... Sorry.)
You'll see that it starts at 800 mA, then drops to 700 as voltage rises, then 600 (stock), then 550 (below stock, be nice to the battery), then it exits constant-current mode and enters constant voltage mode (battery voltage stays just under 4.2 volts, and current drops until charge terminates.) If you look at the spikes during the CV phase of charging you'll see why I worry about charge termination under load - those spikes are because CPU usage counts against the charge current limit.
So far I can confirm similar results after 1 day of usage. Entropy your work with the battery tweaks is amazing. Ty so much. BTW where did you get your extended Battery?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
2sl0w said:
So far I can confirm similar results after 1 day of usage. Entropy your work with the battery tweaks is amazing. Ty so much. BTW where did you get your extended Battery?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Click to expand...
Click to collapse
eBay - check the Accessories forum, there's a discussion on it there.
The battery cover that comes with it is pretty weak. Two people have received ones that were cracked on arrival including myself. I'm going to try and get a replacement from the vendor, otherwise figure out how to fix/strengthen the cracks.
Entropy will this work with cm7?
Sent from my SGH-I997 using XDA App
bryanb86 said:
Entropy will this work with cm7?
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
No
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Entropy512 said:
Attaching some screenshots of CurrentWidget logs.
One is a log taken while driving with nav on full brightness. Look at how it periodically bumps charge current up to 700 mA - it looks like nav with full brightness needs just a shade over 600 mA. The voltages that trigger state changes are such that this translates to around 85-90% battery.
One is a log taken while charging my new 3500 mAh extended battery from 59%. (I forgot to log the voltages... Sorry.)
You'll see that it starts at 800 mA, then drops to 700 as voltage rises, then 600 (stock), then 550 (below stock, be nice to the battery), then it exits constant-current mode and enters constant voltage mode (battery voltage stays just under 4.2 volts, and current drops until charge terminates.) If you look at the spikes during the CV phase of charging you'll see why I worry about charge termination under load - those spikes are because CPU usage counts against the charge current limit.
Click to expand...
Click to collapse
Where do I get a battery like your 3500 one?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
WeezyFBaby17 said:
Where do I get a battery like your 3500 one?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Click to expand...
Click to collapse
Ebay.
Sent from my SAMSUNG-SGH-I997R using XDA App
00mred00 said:
Ebay.
Sent from my SAMSUNG-SGH-I997R using XDA App
Click to expand...
Click to collapse
Specifically, go over to http://forum.xda-developers.com/showthread.php?t=1175568

What is undervolting and how can it save my battery life?

I have a Nexus S with CM7.1 and I am using the Glados Kernel v1.10 BFS.... I have my clock speed from 100-1000 on conservative... my questions are, what does this do? How do I do it? And how much battery life can I usually save? I searched it up, and I haven't really found too much stuff in depth. Thanks
Sent from my Nexus S
I'm not sure anyone's even done any extensive testing, but I can tell you that kernels such as the Trinity SEUV kernel have a serious increase in batt life.
I'm talking 8+ hrs extra probably, at least. Now each person is different, so light users like myself will benefit more, but the difference is definitely noticeable.
That being said, it depends on the kernel you use, and how often you use your phone.
nickmv said:
I'm not sure anyone's even done any extensive testing, but I can tell you that kernels such as the Trinity SEUV kernel have a serious increase in batt life.
I'm talking 8+ hrs extra probably, at least. Now each person is different, so light users like myself will benefit more, but the difference is definitely noticeable.
That being said, it depends on the kernel you use, and how often you use your phone.
Click to expand...
Click to collapse
In the building I go to school in has nearly no service. I get edge at most when I find a spot, I had GPS on, brightness mid and all the same clock speeds.... my Vibrant got more battery life with the same clock speed on CM7, I had 27 when I left, I usually get 60something on my Vibrant. So what should I do, and how can I underclothing my device using setcpu?
Sent from my Nexus S
unvervolting , as you can see from this word , under --- voltage
battery output juice to hardware such as CPU , screen , antenna ... etc
let me make an exemple , let's assume one battery has "1500" juice , if you output 50 juices per hour , then you can last about 30 hours , follow me ?
unvervolting reduces this output juice , let's say , down to 45 juice (you can not reduce too much due to stability and something like that) , then you battery can last about 33.33 hours , this additional 3.33 hours comparing to 30 hours , is extra battery life you got by undervolting .
of course this is not exactly how it works , but more or less, i think you can take the idea of it.
duration of your battery is very much depending on your usage.
3G data connection and GPS are battery killer , i have brainmaster's MIUI + franco kernel , 100% battery = 2 hours 3G data = 1.5 hours GPS navagation.
Oops wrong thread
qtwrk said:
unvervolting , as you can see from this word , under --- voltage
battery output juice to hardware such as CPU , screen , antenna ... etc
let me make an exemple , let's assume one battery has "1500" juice , if you output 50 juices per hour , then you can last about 30 hours , follow me ?
unvervolting reduces this output juice , let's say , down to 45 juice (you can not reduce too much due to stability and something like that) , then you battery can last about 33.33 hours , this additional 3.33 hours comparing to 30 hours , is extra battery life you got by undervolting .
of course this is not exactly how it works , but more or less, i think you can take the idea of it.
duration of your battery is very much depending on your usage.
3G data connection and GPS are battery killer , i have brainmaster's MIUI + franco kernel , 100% battery = 2 hours 3G data = 1.5 hours GPS navagation.
Click to expand...
Click to collapse
At what level should I start undervolting? I have it at 800mhz with 1125MV on lazy, is that fine to start with? I keep rising it each time it crashes on me( I started from 1025, worked my way up when I got random freezes). Do you recommend another kernel or something? I want the most power with the most performance. I heard Trinity was good but I may need to revert back to stock because the thread advised me to flash from stock for the most promising experience.
Sent from my Nexus S
Smokexz said:
At what level should I start undervolting? I have it at 800mhz with 1125MV on lazy, is that fine to start with? I keep rising it each time it crashes on me( I started from 1025, worked my way up when I got random freezes). Do you recommend another kernel or something? I want the most power with the most performance. I heard Trinity was good but I may need to revert back to stock because the thread advised me to flash from stock for the most promising experience.
Sent from my Nexus S
Click to expand...
Click to collapse
Here are my settings, once again, good starting point.
http://forum.xda-developers.com/showpost.php?p=19258876&postcount=1889
Some users reported that they had to bump 100 and 200MHz to 900mv and 400MHz to 950mv. To each their own, we all have different phones.
i have been doing affect of various variables including uv on battery life...
by changing one variable at the time..
in my testin.. undervolting actually made battery drain worse...
http://caleb1783.tistory.com/258
polobunny said:
Here are my settings, once again, good starting point.
http://forum.xda-developers.com/showpost.php?p=19258876&postcount=1889
Some users reported that they had to bump 100 and 200MHz to 900mv and 400MHz to 950mv. To each their own, we all have different phones.
Click to expand...
Click to collapse
Sent from Divinus Nexus S...
I'm sorry, but I fail to see where exactly you've proven that undervolting gives a higher battery drain in those tests.
Your methodology isn't scientific enough, although decently documented you have different usage patterns depending on the day. Sometimes you're playing a game and browsing the internet, others you're just idling all day.
On the undervolt test with Franco 25112011 kernel, your undervolt isn't even stable, leading to a reboot during a game and a battery stats "bug". Your screen was on 26 minutes more. Just the fact your undervolt isn't stable will make your battery drain faster. There's not only reboots and force closes as symptoms to an unstable undervolt.
The good way to test it would be by using a much more controlled environment and test patterns. Airplane mode can be used so as not to suffer from a bad reception or receive text messages/calls, a task (or multiple tasks) can be ran for a very specific amount of time, no user input other than starting the task and stopping the task should be done and the undervolt should be deemed stable.
Anyway, I can and will vouch for undervolting components, whether on a smartphone or a computer. I'm sure Trinity kernel users would agree too.
Smokexz said:
At what level should I start undervolting? I have it at 800mhz with 1125MV on lazy, is that fine to start with? I keep rising it each time it crashes on me( I started from 1025, worked my way up when I got random freezes). Do you recommend another kernel or something? I want the most power with the most performance. I heard Trinity was good but I may need to revert back to stock because the thread advised me to flash from stock for the most promising experience.
Sent from my Nexus S
Click to expand...
Click to collapse
personally , i don't use undervolting , because it doesn't really effect too much on battery life
i didn't actually try , but i think undervolting could give you maximo extra few hours of battery life .
i'm using franco kernel , and 100 - 1000 with lazy governor
you minim should be 100 , 800 is not necessary
and for 1 GHz CPU , handle normal processing is enough
and i do think , that screen takes more juices than CPU ...
----------------------------------
i suggest you should try my way , buy an extra battery piece , then you won't worry about battery life any more ...
like me , i have to use phone very carefully back the time i didn't have second battery , sometimes i got out home about 8:00 AM ,and got back like 8:00 PM , when i back home , battery is nearly dead ... less than 10% .... = =
but now , i have second battery , i can use my phone whatever and whenever i want ...
i am in Spain , battery cost me 8 euros , if you can't find Nexus S battery , you can also buy Samsung i900's battery.
watch out , i900 , not i9000 , it's same battery , can be pluged-in in battery slot.
so , why did you waste days and days to search , to test , to set , to ask in order to get more battery if you can solve this problem with only 8 euors ???
but ... for real , these undervolting or overclock or underclock or what , does give you , hmm , how to say ? sense of fufillment , it's kinda good ^^
Some people enjoy travelling light, not having extra peripherals in their pockets and such. I already have enough stuff with my phone, keys and money clip without wanting to bring a battery somewhere in my dressy pants.
I read somewhere (and i think it was in this forum) that for the Nexus S the profile in SetCPU should be ondemand or conservative. I'm running Koush's Alpha 12, SetCPU "ondemand" and JuiceDefender Ultimate on "balanced". I've been on that for a week or so. I think the battery life is better than what i had running stock. I'm okay when the phone can make it through a day (like 16 hours) with normal use. I charge it at night anyway.
n00bfuscator said:
I read somewhere (and i think it was in this forum) that for the Nexus S the profile in SetCPU should be ondemand or conservative. I'm running Koush's Alpha 12, SetCPU "ondemand" and JuiceDefender Ultimate on "balanced". I've been on that for a week or so. I think the battery life is better than what i had running stock. I'm okay when the phone can make it through a day (like 16 hours) with normal use. I charge it at night anyway.
Click to expand...
Click to collapse
well , i think it depends on what kernel you use
some kernel's author would suggest what's best for his kernel.
also juicedefener or something , it's most likely by automatically shut down your unnecessary functions like GPS BT WIFI 2G/3G ...etc in order to save battery life.
i have been trying some of them , doesn't gimme much effect , probably it's just psychologic effect, you know , people would see what they want to see , also i have seen one application (Antutu something , i don't remember exact name) that reduces power output to hardware in order to save battery life , i think only that kinda applications can acutally save power...
---------- Post added at 09:03 PM ---------- Previous post was at 08:59 PM ----------
polobunny said:
Some people enjoy travelling light, not having extra peripherals in their pockets and such. I already have enough stuff with my phone, keys and money clip without wanting to bring a battery somewhere in my dressy pants.
Click to expand...
Click to collapse
i know , i do that when i have time , it does gimme sense of fulfillment , just like watch your work to be done .
it isn't about results , it's about journey you have been through
i don't know man , battery's size is just about 4.5 x 3.5 x 0.5 cm ... you really don't have that space for battery ... ?
qtwrk said:
well , i think it depends on what kernel you use
some kernel's author would suggest what's best for his kernel.
also juicedefener or something , it's most likely by automatically shut down your unnecessary functions like GPS BT WIFI 2G/3G ...etc in order to save battery life.
i have been trying some of them , doesn't gimme much effect , probably it's just psychologic effect, you know , people would see what they want to see , also i have seen one application (Antutu something , i don't remember exact name) that reduces power output to hardware in order to save battery life , i think only that kinda applications can acutally save power...
---------- Post added at 09:03 PM ---------- Previous post was at 08:59 PM ----------
i know , i do that when i have time , it does gimme sense of fulfillment , just like watch your work to be done .
it isn't about results , it's about journey you have been through
i don't know man , battery's size is just about 4.5 x 3.5 x 0.5 cm ... you really don't have that space for battery ... ?
Click to expand...
Click to collapse
Left pocket has my keys, my money clip with my cards and a pack of gum. Right pocket has my phone. Can't put anything worthy in back pockets, even less in dress pants.
What are common issues in installing Trinity over a kernel? I have Glados kernel so what would the side effects be?
Sent from my Nexus S
Smokexz said:
What are common issues in installing Trinity over a kernel? I have Glados kernel so what would the side effects be?
Sent from my Nexus S
Click to expand...
Click to collapse
it depends , look over your older kernel isntall zip file , check out if they put any files in directions (/system/lib , /system/modules , /system/vendor ...etc) , if so , delete them manually or check your new kernel zip file if it will overwrite the same named file ,in that case you don't have to detele these same named file because they will automatically be overwritten, otheriwse you do have to delete thoes file which won't be deleted or overwritten automatically.
...
i always just directly flash it ... if comes problem i just reinstall the ROM in order to get clean system and then flash the kernel.
some kernel like GLADOS and FRANCO has script to clear older files
but , anyway , back up before install any thing that could effect on system.
---------- Post added 14th December 2011 at 12:02 AM ---------- Previous post was 13th December 2011 at 11:58 PM ----------
polobunny said:
Left pocket has my keys, my money clip with my cards and a pack of gum. Right pocket has my phone. Can't put anything worthy in back pockets, even less in dress pants.
Click to expand...
Click to collapse
= = bro , doesn't your cloth have pocket ?
well , if you have protective case and screen protector on your phone , you can just put battery together with it
and you can put battery with your keys and other things.
qtwrk said:
it depends , look over your older kernel isntall zip file , check out if they put any files in directions (/system/lib , /system/modules , /system/vendor ...etc) , if so , delete them manually or check your new kernel zip file if it will overwrite the same named file ,in that case you don't have to detele these same named file because they will automatically be overwritten, otheriwse you do have to delete thoes file which won't be deleted or overwritten automatically.
...
i always just directly flash it ... if comes problem i just reinstall the ROM in order to get clean system and then flash the kernel.
some kernel like GLADOS and FRANCO has script to clear older files
but , anyway , back up before install any thing that could effect on system.
---------- Post added 14th December 2011 at 12:02 AM ---------- Previous post was 13th December 2011 at 11:58 PM ----------
= = bro , doesn't your cloth have pocket ?
well , if you have protective case and screen protector on your phone , you can just put battery together with it
and you can put battery with your keys and other things.
Click to expand...
Click to collapse
Yeah I just did that and it broke the wifi. I went to factory settings and installed Trinity, going through my normal routine tomorrow and going to see how long the battery life goes, apparently the performance is great at 880mhz and the voltage is pretty low.
Sent from my Xoom
qtwrk said:
it depends , look over your older kernel isntall zip file , check out if they put any files in directions (/system/lib , /system/modules , /system/vendor ...etc) , if so , delete them manually or check your new kernel zip file if it will overwrite the same named file ,in that case you don't have to detele these same named file because they will automatically be overwritten, otheriwse you do have to delete thoes file which won't be deleted or overwritten automatically.
...
i always just directly flash it ... if comes problem i just reinstall the ROM in order to get clean system and then flash the kernel.
some kernel like GLADOS and FRANCO has script to clear older files
but , anyway , back up before install any thing that could effect on system.
---------- Post added 14th December 2011 at 12:02 AM ---------- Previous post was 13th December 2011 at 11:58 PM ----------
= = bro , doesn't your cloth have pocket ?
well , if you have protective case and screen protector on your phone , you can just put battery together with it
and you can put battery with your keys and other things.
Click to expand...
Click to collapse
I sometimes have a dress shirt or a polo with an additional pocket. Nevertheless I like to travel light, buying a second battery, while a good idea, is a poor solution to an unoptimized system.
too much undervolting can and will cause more battery drain. there is a fine line that can be crossed from battery savings to battery loss. after a certain point, the phone will end up working harder to get where/what it needs because there isnt enough voltage, leading to the loss.
Smokexz said:
Yeah I just did that and it broke the wifi. I went to factory settings and installed Trinity, going through my normal routine tomorrow and going to see how long the battery life goes, apparently the performance is great at 880mhz and the voltage is pretty low.
Sent from my Xoom
Click to expand...
Click to collapse
you must know
this minim is for screen luck status , when you are using your phone , system/CPU will automatically change it to adapt your processing , but when you screen is off , CPU should be running at minim in order to save juices

[Q] Which kernel is best for Stock ICS?

Hi, first to defend myself, I did search and found that everybody says good things for every kernel. So every kernel is best for Stock ICS?
I got confused. Yes I'am total noob and recently learned how to root and flash custom rom's.
I just want to hear your opinion for best kernel running on Stock ICS.
I need kernel that is good for the battery but also snappy for the system. I don't play games and I use my phone for calls, reading news, working on excel files, google maps, mail and taking pictures.
My phone is Nexus S GT-I9020T on Wind network.
IMO ezekeel kernels
Has lats of featured including voodoo color
http://forum.xda-developers.com/showthread.php?p=20520270
Sent from my Nexus S using xda premium
Thank you. Is this kernel stable?
Im just trying to set it up as we speak, will let you know how stable it appears once I figure it out
Stuck on trying to flash an unsecure boot image at the moment.
*shrugs* The stock kernel?
Unless you want the functions third party kernels bring to the table, I don't see a good enough reason to swap the stock kernel for another.
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel. Also I read that there are restarting issues with IMO ezekeel kernels. Yes I know that probably the most stable it's the stock kernel, but there is problem with battery, I had more juice with GB and CMD 7. That's why Google paused ICS update on Nexus. But probably I will stick with Stock Kernel because for me it's better to have less battery for now instead random restarts. I hate when my phone it's not in perfect state.
Just managed to get ezekeels CFS on there and I get the reboot bug after going to standby.
Looking for updates but the thread is huge. Yet to try BFS.
darko.baruh said:
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel. Also I read that there are restarting issues with IMO ezekeel kernels. Yes I know that probably the most stable it's the stock kernel, but there is problem with battery, I had more juice with GB and CMD 7. That's why Google paused ICS update on Nexus. But probably I will stick with Stock Kernel because for me it's better to have less battery for now instead random restarts. I hate when my phone it's not in perfect state.
Click to expand...
Click to collapse
You can try and turn off deep idle for your reboots.
Solves the problem 99% of the time (totally made up stat that could actually be true)
But actualy that function (deep idle) it's the most impotant thing in the kernel. It gives more battery time. Other thing are just fancy. More battery and no hickups, I dont need overclocking because I dont play games.
Sent from my Nexus S using Tapatalk
darko.baruh said:
But actualy that function (deep idle) it's the most impotant thing in the kernel. It gives more battery time. Other thing are just fancy. More battery and no hickups, I dont need overclocking because I dont play games.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Deep idle gives more battery time under certain conditions (screen off but not completely idle, playing music for instance). It won't really give you more battery time if your phone is actually idle with the screen off.
But according to this http://forum.xda-developers.com/showthread.php?t=1297535 I understood differently. Maybe you are right, I'am still noob to all of this.
darko.baruh said:
That's what I was thinking. With Glados kernel I had problems with restarting after the screen turns of, also with Matr1x kernel.
Click to expand...
Click to collapse
Same here but not bad at least for me just one reboot since i installed yesterday when he posted. 2.1 kernel I never got any reboots
Sent from my Nexus S using xda premium
darko.baruh said:
But according to this http://forum.xda-developers.com/showthread.php?t=1297535 I understood differently. Maybe you are right, I'am still noob to all of this.
Click to expand...
Click to collapse
The first post that you linked actually just confirms what I said.
Ezekeel said:
Since this is just theory and Morfic noted that his experience seems to indicate otherwise and that limiting the CPU frequency does actually decrease the battery drain, I put this theory to the test and logged the battery charge over 10h of FLAC playback in Airplane mode with the screen switched off.
Click to expand...
Click to collapse
1) Playing FLAC (not idle)
2) Screen off
Pre-requisites are met.
So as I understood the battery consumption is reduced only if you listen music, because you can't do anything else when the screen is off. And the deep idle is working only in standby mode (screen off).
darko.baruh said:
So as I understood the battery consumption is reduced only if you listen music, because you can't do anything else when the screen is off. And the deep idle is working only in standby mode (screen off).
Click to expand...
Click to collapse
Deep idle only shows savings if there is tasks running while the screen is off VS the same situation without deep idle.
So for someone doing commuting (like simms22 for example) and listening to music for around an hour, they'll lose less battery with deep idle than without.
You won't actually save battery if your phone is actually idle with deep idle enabled.
It's not some kind of magical function that makes your phone use less battery doing tasks with the screen on, deep idle disables certain components of the phone while executing tasks with the screen off, instead of having it "at full speed" as if the screen was on.
Now I understood. Thank you very much.
darko.baruh said:
Now I understood. Thank you very much.
Click to expand...
Click to collapse
No problem. I think Deep Idle is probably the mod by Ezekeel surrounded by the most misconceptions.
Most new users want it absolutely but don't seem to know why.
On His Glados kernel I noticed that Android OS was using 20%-21% of the battery and on the stock kernel 30%-31%.
Android System was using around 14% and on the stock around 19%.
Ok, have you decided to give the Glados 2.2 another go? I believe I have finally tweaked it so that it is stable for me.
Before I was getting restarts within 30 seconds of the screen turning off. I have cornered this (on my phone at least) to a problem with NSTools auto-setting the lower frequency to 100mhz. Changing it back to 200mhz and I have yet to see the system restart itself. Im not overclocked, because I dont see the point as everything is fairly snappy with this new kernel. I dont really play games on it so Im not fussed.
I did used NSTools and the frequency was set to 200mhz and I had system restarting on screen off. Using stock ICS with Glados 2.2
Also I had green annoying flickr on locking and unlocking the screen.

Battery Drain

Sorry for making many thread, But I'm curious.
ANd need some help
How normal is this? ...
Idle: 216/216 Screen off
No Data No Wifi No GPS No bluetooth No sync
And I'm getting drain like this? What's happening?!?!
Or are the readings just wrong?
i was about to make a thread but saw this and thought id fill in it.
Well my g2x has been quite dissappointing lately..
When i first got it, the battery life wasnt that bad. Even had data/refresh and Auto brightness and it would last almost all day.
But the past couple of months its been unbearable. I would have to charge my phone at any oppurtunity, even at work. After 100% charge i would check 30min later and it would be already at 83%.
I'm on the latest CM7 nightly, and have also tried juice defender (no use)
Im contemplating on just doing a CLEAN install of the nightly but i dont want to start all over again because its a pain.
Any input? Or is it just the crappy battery?
LReyes66 said:
i was about to make a thread but saw this and thought id fill in it.
Well my g2x has been quite dissappointing lately..
When i first got it, the battery life wasnt that bad. Even had data/refresh and Auto brightness and it would last almost all day.
But the past couple of months its been unbearable. I would have to charge my phone at any oppurtunity, even at work. After 100% charge i would check 30min later and it would be already at 83%.
I'm on the latest CM7 nightly, and have also tried juice defender (no use)
Im contemplating on just doing a CLEAN install of the nightly but i dont want to start all over again because its a pain.
Any input? Or is it just the crappy battery?
Click to expand...
Click to collapse
It could be the battery. Your case is different from mine..
My battery is tested with Battery Monitor Widget, and it says my battery is about 1540mAh.
The thing I'm confused about is the battery drain.. It's quite high. 200mAh + at 216mhz
Try clean install, don't use any of those scripts (like V6 SuperCharger), those are wakelock city.
Now, go into spare parts and check your partial wakelocks and uninstall apps that have huge wakelocks, facebook is a battery hog.
clean install of cm7?
or clean wipe of phone back to factory then root/install cm7?
Clean install of the rom you're using.
Sent from my LG-P999 using XDA
I was having horrible battery drainage also. I replaced the usb cable and ac charger and it made a huge difference. Faux kernel also helped alot. I get a little over 8 hrs with moderate to heavy use.
EDIT: wait that wasn't even related to the op but the other scenario.
Sent from my LG-P999
Yeah, I tried a clean install...
After clean install, the only app I installed was this. And boom high usage.
all wipe first and flash or agian.
Wipe user data, /system, and dalvik cache. PM me if you're unsure where they are.
Sent from my amazing LG G2x running Bionix Reloaded v1.4
I have the same issue on my G2x. I have replaced battery with a 1800mAH and a 3500mAH extended. But the drain is the same with every one of them.
Have tried FAUX's kernel with SetCPU and the recommended settings, but to no avail.
Did a clean install (wiped user/factory reset, dalvik, cache and did a format /system) of RG2x-MIUI v2.3.16 - SWIPE NOTIFICATIONS-Powered by Faux123 CM v0.4.8 yesterday.
Battery drains at the rate of 10% every hour when idle. Even with minimal usage (15mins call time, few txt, light browsing over 4G), the battery won't last more than 4-5hrs
One thing I am curious about, do you have to run a combination of kernel+ROM over a period of time to see if the battery performs any better or are the results instant?
Most people get better battery life on OTA based roms than CM7/AOSP. So MIUI may not provide enough juice for you, but try Bionix Reloaded and tell us the difference in battery.
Sent from my amazing LG G2x running Bionix Reloaded v1.4
I has Bionix Reloaded before yesterday. The battery life was about the same, but the main issue that I was facing with Bionix was the switch from data-Wifi. For some reason, data had precedence over WiFi.
I can give it one more shot. Maybe a clean install would rectify that issue. DO you recommend any kernel/tweaks/setCPU settings etc with Bionix or just use it as such?
For the meanwhile, I have turned off GPS and using SetCPU 816/389 inscreen and 389/389 Off to see if there is any improvement.
I really don't care about the fancy part as long as I get battery life.
I recommend Faux's undervolted kernel, make sure its the one for GB btw. As for SetCPU settings (I uses CPU Master), I keep it at 216-816 most of the time, only raising it if I need it (such as Facebook, browsing, heavy games). I have the governor set to Performance.
Also, I don't have a screen off profile (but did have it set before) at 216-503 with Powersave governor, and my battery lasts more now that I took off the profile. The Tegra 2 has HW governors that more efficiently save battery than SW ones do. Not all CPUs are like this, so we are in for a treat.
Sent from my amazing LG G2x running Bionix Reloaded v1.4
Will give it a shot right now. Just to be sure about the kernel, we are talking abt this one:
[ GINGERBREAD: ]
[ Start @ 1.1 GHz, Pre Overclock / Under Volt, Max @ 1.55 GHz ]
The File ==> LGE Pre-OC/UV Kernel Version 013 With EXT4 <==
from http://forum.xda-developers.com/showthread.php?t=1102720
That's not my problem. O;
My problem is that When the battery is 100%, no matter what task I DO, it only drains -2...
But with the same setting, at 30% battery, my battery drains from -300 to -1000
BachanPandey said:
Will give it a shot right now. Just to be sure about the kernel, we are talking abt this one:
[ GINGERBREAD: ]
[ Start @ 1.1 GHz, Pre Overclock / Under Volt, Max @ 1.55 GHz ]
The File ==> LGE Pre-OC/UV Kernel Version 013 With EXT4 <==
from http://forum.xda-developers.com/showthread.php?t=1102720
Click to expand...
Click to collapse
Yes, that's the one. Flash away!
Sent from my amazing LG G2x running Bionix Reloaded v1.4

Rooting 3a - Doesn't seem worth it

Owned a OnePlus X - I rooted that phone because the manufacturer stopped making updates for it.
Owned a Pixel 1 - I rooted that one, and a while it was nice, it was annoying having to manually update once a month.
Does anyone else think it's not worth rooting just because it's of how much support Google already gives on its lineup of phones? I also checked the ROMs section of XDA, and there doesn't appear to be very many ROMs for this device anyway.
What do you guys think? I'm a big advocate for rooting, but only when the good outweighs the bad. Right? What do you personally use root access for?
You don't need to root to have a custom rom running. You just need a unlock bootloader and TWRP to flash roms, root is optional.
ttocs99 said:
You don't need to root to have a custom rom running. You just need a unlock bootloader and TWRP to flash roms, root is optional.
Click to expand...
Click to collapse
This is true, but you still don't get OTA updates. Doesn't change anything I wrote above. But what you said is accurate, and I'm glad you pointed it out. Because some people may not know the difference between rooting and simply unlocking your bootloader.
I use J4N's Pixel edge mod. Now when I squeeze my phone, the flashlight comes on instead of the default action. I also use smali patcher to keep my location private to all apps. Don't need permanent root, but I use ElementalX app and flash the kernel Flar2 makes for our device also.
Due to rooting, I don't take updates immediately. I usually take them when big changes or fixes are done, like the recent updates to Vulkan on our phone.
For example, I ran Sept update until mid Dec when I flashed Dec update and the recent ElementalX 3.11 kernel. (Sept was A11 launch and either Nov or Dec had some Vulkan API updates)
Uzephi said:
I use J4N's Pixel edge mod. Now when I squeeze my phone, the flashlight comes on instead of the default action. I also use smali patcher to keep my location private to all apps. Don't need permanent root, but I use ElementalX app and flash the kernel Flar2 makes for our device also.
Due to rooting, I don't take updates immediately. I usually take them when big changes or fixes are done, like the recent updates to Vulkan on our phone.
For example, I ran Sept update until mid Dec when I flashed Dec update and the recent ElementalX 3.11 kernel. (Sept was A11 launch and either Nov or Dec had some Vulkan API updates)
Click to expand...
Click to collapse
This is actually really good to know. Seems like a lot of the OT updates that Google pushes out are just simple security or patches.
Question about ElementalX. I installed a custom kernel on an older phone of mine, a lot of people raved about how great it was. From my experiences, however, it seemed like just a placebo effect. Do you actually notice anything with ElementalX? Hope that doesn't come off rude or anything.
pojr said:
This is actually really good to know. Seems like a lot of the OT updates that Google pushes out are just simple security or patches.
Question about ElementalX. I installed a custom kernel on an older phone of mine, a lot of people raved about how great it was. From my experiences, however, it seemed like just a placebo effect. Do you actually notice anything with ElementalX? Hope that doesn't come off rude or anything.
Click to expand...
Click to collapse
I understand the weariness. I use EX due to the wakelock blocker and the minor fixes to optimize the kernel does make a slight difference in idle battery life. Overnight I only lose 1% battery on EX compared to 5-6% on stock. I don't notice any battery savings during use though compared to stock.
Edit: with EXKM app and EX kernel, you can get sensor readings also. I always have my CPU temp in my notification panel for quick access to it. I beta test a game and give feedback on how much their optimizations have improved. Like last iteration of the beta, my phone was reaching 52°C compared to the live app nearly overheating my phone at 67°C. All with a quick pull down of my notification tray.
Obviously that is a very minor and unique use case.
Edit 2: one other magisk module I forgot to say I use is AccA. Which is a battery charging module. I have it set to stop charging my phone at 81% and shut off my phone at 30% if discharging. I keep my battery at those levels to help prolong it's life as usually over 80% drastically shortens the battery life of your phone. Whether that's proven with this phone is yet to be seen. I personally haven't seen battery degradation in the 18 months I've had the phone so far.
Uzephi said:
I understand the weariness. I use EX due to the wakelock blocker and the minor fixes to optimize the kernel does make a slight difference in idle battery life. Overnight I only lose 1% battery on EX compared to 5-6% on stock. I don't notice any battery savings during use though compared to stock.
Edit: with EXKM app and EX kernel, you can get sensor readings also. I always have my CPU temp in my notification panel for quick access to it. I beta test a game and give feedback on how much their optimizations have improved. Like last iteration of the beta, my phone was reaching 52°C compared to the live app nearly overheating my phone at 67°C. All with a quick pull down of my notification tray.
Obviously that is a very minor and unique use case.
Edit 2: one other magisk module I forgot to say I use is AccA. Which is a battery charging module. I have it set to stop charging my phone at 81% and shut off my phone at 30% if discharging. I keep my battery at those levels to help prolong it's life as usually over 80% drastically shortens the battery life of your phone. Whether that's proven with this phone is yet to be seen. I personally haven't seen battery degradation in the 18 months I've had the phone so far.
Click to expand...
Click to collapse
It seems like you've paid a lot of attention to it, and it sounds like having a custom kernel is effective enhancing the battery. I'm not sure if the average person would notice it though unless they were really paying attention to it. As someone who doesn't care that much about kernels, I don't see much of a benefit to rooting other than maybe AdAway and that Pixel Edge mod (that does se pretty cool).
The only thing I have ever used root for has been for Substratum. Now that some ROMs have custom theming options, I find root itself to be an added headache not worth the hassle. I would really love to test out ElementalX, but there is no straight boot.img install option, and I can't justify rooting just to install it.

Categories

Resources