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
Related
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.
MIT student proves by A + B that T-Mobile G2x has hardware issues related to overheating / shutdown / battery
http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
Let's share this and be social.
Here are some other references for this same post.
#OccupyLg
LG: http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
XDA-Developers: http://forum.xda-developers.com/showthread.php?t=1433445
T-Mobile: http://support.t-mobile.com/thread/16431
I would assume a hot reboot would work as well if you don't want to install an app killer
Sent from my LG-P999 using xda premium
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
jcbofkc said:
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
Click to expand...
Click to collapse
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
psychoace said:
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
Click to expand...
Click to collapse
If (big if) the overheating observed is due to heat from the battery charging leaching into the phone, wouldn't a quick and easy fix/test be a piece of aluminum foil between the battery and the phone?
Sent from my LG-P999 using Tapatalk
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Prod1702 said:
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Click to expand...
Click to collapse
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
FYI if it does it on all roms then its a hardware issue and software change wont fix it...
Sent from my LG-P999 using xda premium
I also had the dreaded sod at least once every couple of days.
However, after I installed eb kang with faux oc/uv profile with set cpu, I have had no problems since.
I guess its ymmv...
Sent from my LG-P999 using XDA App
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
gggirlgeek said:
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
Click to expand...
Click to collapse
I don't think anyone is saying this problem effects everyone. It's just with all the bad units out there with this problem, this is probably why it's happening. Right now I'm trying to run some profiles in setcpu to see if it improves my phones sleep. It's only been one day so I will see by the end of the week how this fares
Sent from my LG-P999 using xda premium
Cm7, morfic Trinity kernel, go launcher ex oc'ed to 1.4 ghz. Perfect! No issues!
Sent from my LG-P999 using xda premium
erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
Posts like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Prod1702 said:
Things like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Click to expand...
Click to collapse
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
mt3g said:
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I think the term overheating is thrown around too loosely here without more of a description. There's the type of overheating that causes our phones to shut off and stay off until the battery is pulled. There is also the type of overheating that occurs when you plug in an HDMI cable, which may or may not cause your device to die.
I'd assume those two types of overheating are the same, as they result in the same thing: dead device that won't turn on without a battery pull. And the phone gets hot as fsck. Hot as in you'd be scared to keep it in your pocket because (1) it'll burn your leg and (2) you are scared the battery will explode.
Those two types are overheating are different from your phone merely heating up upon use. I'm talking about charging the phone while navigating via GPS at full brightness or playing a graphically intense gaming. That magnitude of that heat is normal. And I'm guessing that's what all your devices have experienced.
And as all the devices get thinner, that battery's going to sit closer and closer to your hand, which equals more heat. And as the glass technology gets thinner (gorilla glass 2.0), your face will probably feel the heat to a greater degree as well.
---------- Post added at 04:18 PM ---------- Previous post was at 04:13 PM ----------
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
It's true, it's not android, it's LG.
And to all the people thinking that undervolting and underclocking your phone will fix everything, it won't. Android already underclocks the CPU when it's not in use. SetCPU does nothing in this instance. The only instance they'll see a difference is if they have some sort of rogue app that's maintaining a wake lock. You just can't beat terrible design (referring to the MIT guy's findings). Sometimes it'll work, sometimes you just lose.
LG majorly screwed up with this and I hope that their mobile efforts in the future fail for their lack of follow through.
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Just wanted to say that this thread has been really helpful to me. Every time I've flashed a custom kernel, my phone has always, within the first 2 nights of installation, turned off in the middle of the night while on the charger. So I've always been stuck with the stock kernel. But then the suggestion to use SetCPU to lower the speed while the screen is turned off worked for me. So far no SOD and my phone has survived Faux's kernel and charging overnight without a battery pull and without overheating.
Now I can try out custom kernels and find all new ways to destroy my battery by doing things I'm not knowledgable enough to be doing!
lotherius said:
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Click to expand...
Click to collapse
hmm.. I dont doubt you, but I think doing that would not be any different.
BECAUSE, the charger is not constantly charging at 1A rate. If you notice, the phones ramps down the input current after a certain percentage ~90%, and trickles it up to 100. Once at 100, the charging is supposed to be stopped. I've charged mine with my bluetooth 500ma charger, and I didnt see a difference in heat temps; only charging time took longer.
As far as heat, Lion batteries should be able to handle 1C charge (1 x charge capacity) with no problems in heat. That means even at 1.5A charge, it should be OK.
Regarding overclocking, undervolting and overheating. There is a variation of parameters across every silicon wafer; among the 25 or so wafers in a wafer lot; and from wafer lot to wafer lot. This is referred to as the "spread" and parts at the extremes are called "corner parts". Most parts should be in the middle of things, not all. With newer parts and small silicon process geometries, the margins are typically smaller - hopefully improving as the fab gets experience with the new process.
A hardware developer should get corner parts to check their PCBA layout and FW, to see if they have design margin. In the case of DDR (RAM), the voltage, circuit layout and DDR interface timing (from Tegra, in this case) should be checked across some tolerance and with the corner parts. "Fast" parts can draw more current during operation that nominal parts, possible heating up the voltage regulators nearby.
In a good hardware design, everything should work across part variation and the specified operating temperature for the system. When we start playing with the clocking frequency and voltages, there is the risk of FW crashing and HW flipping out. The symptoms can include system shut down (lost), resets, heating, bad effects on other systems (battery, voltage regulator circuits, etc.).
This is why some of us (like me) have little luck Set CPU and others can change it to extreme. What none of us know is how close to the design limits the G2X is - the system and the components like Tegra, the FW control. If due design diligence was not done, the sensitivity to part variation and our hacking is greater than normal.
I am sort of stuck on froyo since I must have BLN on my phone. What is the possibility of BLN ever being ported to a GB kernel? Are there any kernel devs left?
bln was kinda abandoned because of its unpredictable nature. I had it working on froyo with whatever kernel it is that has it but out of nowhere it stopped behaving. others never had it working at all. it wasn't written for the infuse and it has bugs on this phone. I dunno. maybe it can be done. Linux bozo is still around, he just hasn't released anything lately. not really anything to release until we see att source code.
you can use tasker to light the flash on notifications though. but its quite bright, eats batteries and can be distracting.
Yeah, BLN a little glitchy at times but generally works well on my phone. I tried tasker and led lights both killed battery. That is my only gripe about the slate form factor, no led notifications. They could actually put an led under the glass if they wanted to.
Yeah, on GB it pretty much isn't gonna happen, as it's not worth it. Even on froyo, the implementation was iffy. Basically, any implementation will require that you lose deep sleep because of the wakelock required to send commands to the the controller to turn the backlights on/off. This is why the froyo version would allow you to touch the cap keys with the screen off and they would light up. I tried to solve it without a wakelock happening, but always ran into race conditions, and therefore, boom goes the phone.
Linux, thanks for the info. Good to see your still with us!
I'm running boosts miui and it has bln
Sent from my SGH-I997 using XDA App
jmatt78 said:
I'm running boosts miui and it has bln
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
Does it actually work? If so what kernel are you using?
jz3 said:
Does it actually work? If so what kernel are you using?
Click to expand...
Click to collapse
The only kernel you can use with MIUI/CM7 is the one it comes with.
Sent from my SGH-I997
jayson94538 said:
The only kernel you can use with MIUI/CM7 is the one it comes with.
Sent from my SGH-I997
Click to expand...
Click to collapse
That was LB's kernel so BLN a no go.
LinuxBozo said:
Yeah, on GB it pretty much isn't gonna happen, as it's not worth it. Even on froyo, the implementation was iffy. Basically, any implementation will require that you lose deep sleep because of the wakelock required to send commands to the the controller to turn the backlights on/off. This is why the froyo version would allow you to touch the cap keys with the screen off and they would light up. I tried to solve it without a wakelock happening, but always ran into race conditions, and therefore, boom goes the phone.
Click to expand...
Click to collapse
Did I9000/Captivate BLN hold a wakelock? Everyone kept on raving about how little drain BLN caused, but if it held a wakelock it would be awful for battery.
I know on the I9100/I777 no one has pulled off BLN without holding a long wakelock.
Either way - too much work for too little reward. If BLN for gingerbread hadn't been a stability nightmare it might be there - but even after multiple attempts, it was never possible to make it behave in a stable manner.
Entropy512 said:
Did I9000/Captivate BLN hold a wakelock? Everyone kept on raving about how little drain BLN caused, but if it held a wakelock it would be awful for battery.
I know on the I9100/I777 no one has pulled off BLN without holding a long wakelock.
Either way - too much work for too little reward. If BLN for gingerbread hadn't been a stability nightmare it might be there - but even after multiple attempts, it was never possible to make it behave in a stable manner.
Click to expand...
Click to collapse
I don't know the development details but I had a captivate and early kernels did sometimes behave like the infuse did. also developers insisted that it didn't drain battery but I don't know how they were figuring that, they may have been going off how much the light them selves draw but many bln kernels I used did have a notable drop in battery life. I think it was just pride from the developers that couldn't think of a reason it would drain batteries because people did complain at first and the devs said no way you're wrong.
I think the later kernels did better in behavior and battery life but I guess you'd have to get in contact with some i9000 developers to figure that out. maybe the controller or drivers are different I simply don't know.
Dani897 said:
I don't know the development details but I had a captivate and early kernels did sometimes behave like the infuse did. also developers insisted that it didn't drain battery but I don't know how they were figuring that, they may have been going off how much the light them selves draw but many bln kernels I used did have a notable drop in battery life. I think it was just pride from the developers that couldn't think of a reason it would drain batteries because people did complain at first and the devs said no way you're wrong.
I think the later kernels did better in behavior and battery life but I guess you'd have to get in contact with some i9000 developers to figure that out. maybe the controller or drivers are different I simply don't know.
Click to expand...
Click to collapse
The driver architecture is very different from I9000/Cappy to the I9100. Infuse is closer to I9000/Cappy I think.
Easy to confirm if you have one of the said devices:
Charge to full
Reboot device
Reset timers in CPU Spy
Activate a BLN notification using the test function of BLN control, let it sit a while
Wake it up, check deep sleep percentages and kernel wakelock history in BetterBatteryStats. (Note, back when BLN first went into the I9000/Cappy, BBS didn't display kernel wakelocks.)
I did just the opposite - I held back BLN on the I777 for over a month because of the fact that it held wakelocks. People kept begging for it so now I have a release that has a warning in giant red letters that an active BLN notification will drain your battery.
Entropy512 said:
The driver architecture is very different from I9000/Cappy to the I9100. Infuse is closer to I9000/Cappy I think.
Easy to confirm if you have one of the said devices:
Charge to full
Reboot device
Reset timers in CPU Spy
Activate a BLN notification using the test function of BLN control, let it sit a while
Wake it up, check deep sleep percentages and kernel wakelock history in BetterBatteryStats. (Note, back when BLN first went into the I9000/Cappy, BBS didn't display kernel wakelocks.)
I did just the opposite - I held back BLN on the I777 for over a month because of the fact that it held wakelocks. People kept begging for it so now I have a release that has a warning in giant red letters that an active BLN notification will drain your battery.
Click to expand...
Click to collapse
captivate went to my brother. been thinking about getting another though. if it weren't for the pentile matrix screen making text hard to read and the low Res TV out it would've been perfect. the infuse looks cheaper/ is uglier and despite the HDMI only hardware accelerated videos actually use it. it wasn't worth the upgrade.
the i777 is basically perfect but I promised myself the next new phone I Get will have lte and be an international flagship, not just one or the other.
Any idea when BLN will return to the Infuse?
I was wondering which CPU settings / governor everyone else is using on their Skyrocket. I'm running the official CM9 nightlies, and am currently using a 1188/384mhz combo with the conservative governor. Battery life is OK, but isn't as great as it was with Sky ICS. I'm wondering if anyone has any suggestion on how to improve it.
Thanks!
i suggest you use the app set cpu. with it you can make profiles that change your cpu level depending on factors like if your screen is off or if your phone is charging. it really helps with battery life
https://play.google.com/store/apps/details?id=com.mhuang.overclocking&hl=en
it all about the $$$$
lets see what it will cost me i have a thrill, a sr , do i need another phone ..yes!! but i also need other things too. like food and gas it all about do i have extra capital to drop an a new toy. my partner at work still has a unrooted g1 it makes me sad.
Try testing this:
http://forum.xda-developers.com/showthread.php?t=1721235
I currently have mine on 192/1512 will see how it goes testing it for a full day but so far its a little less draining than the original (at least for me).
This is my first Android phone (2nd device overall), I love it, it was my free upgrade option from AT&T, on number 2, the first, I completely bricked trying to upgrade to GB stock..... After I got the taste of flashing ROM's, thanks to TRusselo and his ninja skill, I find myself oriented towards the leaner ones because of memory issues, I run V6 Supercharger , SlimICS :victory:, with JRummy's ROM Toolbox Pro :good: (gotta support the kicka$$ apps), TB, blah blah blah.
My major complaint is that my Cap runs hot, I have OS Monitor on it because I got tired of not knowing the threshold. It bothers me that my phone gets over 110 degrees Fahrenheit , I've even had a brief history of random reboots I attribute to heat when I ran the ICSSGS 4.0.3 ROM (Awesome stuff, but once I bit into Slim, it was over). Is there a way to manage the heat or get a case for the phone that helps to manage the temperature? Or am I S.O.L unless I keep a frozen gel pack nearby?
BTW, first post, I surf the posts often and since I didn't see any questions about overheating for this particular Samsung model thought I'd give this a shot
My gets hot to I think it has to do with the kernel
Sent from my SGH-I897 using xda app-developers app
Mine runs really hot too, mine gf has a cappy and they run the same everything most of the time, but mine is the only one that gets stupid hot. Would love it to be fixed but I think its probably a manufacturing issue. Problem is it wears on the battery. 10-20 of use and you will burn your ear if you want to talk on the phone . The metal back certainly doesn't help either.
Primary reason why your cappy gets hot is because of overclocking if you're clock is high the process of the CPU is high and pay the price of higher battery consume. I'm on 1200 OC and it get's hot hen I'm playing HD games. I suggest that you stay on 1Ghz.
takeoutttt said:
Primary reason why your cappy gets hot is because of overclocking if you're clock is high the process of the CPU is high and pay the price of higher battery consume. I'm on 1200 OC and it get's hot hen I'm playing HD games. I suggest that you stay on 1Ghz.
Click to expand...
Click to collapse
I have the max set at 1Ghz, min 600Mhz, Performance, SIO, I'm sure the fact that the temperature outside being over 100 F doesn't help at al. I have overclocked it before and it started smoldering, not literally, just felt like it.
I've literally taken damp cloth's and set them underneath the phone on occasion to see if that will help, it definitely does, so does setting the gel ice pack under it, so I have found ways around it. I would probably only trade this phone for one of the S3's, but this phone has definitely earned the top place among my favorite devices all time. It's just as tough as a Blackberry, and easier to use than an iPhone.
That's why LOL, 600MHz minimum and 1000MHz max, with performance gov, that keeps it at max clock all the time XD take that off OMG...
b-eock said:
That's why LOL, 600MHz minimum and 1000MHz max, with performance gov, that keeps it at max clock all the time XD take that off OMG...
Click to expand...
Click to collapse
I'm still a NUB, lol, I don't deny it, but I'm all about learning the way of the Droid.... I added some of the Devil Helly Bean Add-On apk's into the Slim Bean, so I have my high points, just have the low ones just as often..
takeoutttt said:
Primary reason why your cappy gets hot is because of overclocking if you're clock is high the process of the CPU is high and pay the price of higher battery consume. I'm on 1200 OC and it get's hot hen I'm playing HD games. I suggest that you stay on 1Ghz.
Click to expand...
Click to collapse
I have never knowingly oc my phone, it would get hot on GB even before I rooted and went to cm. 10-20 mins of web browsing brings my temps up to about 41 C (106 f) I am pretty new to this, where to I check my clock settings?
I'm running helly bean nightly s
I have switched batteries with my gf cappy so I'm pretty sure its not a battery issue
Maybe a bad/defective battery is the cause of the problem since there is no overclockin...???
Sent from my SAMSUNG-SGH-I777 using xda premium
master2828 said:
I have never knowingly oc my phone, it would get hot on GB even before I rooted and went to cm. 10-20 mins of web browsing brings my temps up to about 41 C (106 f) I am pretty new to this, where to I check my clock settings?
I'm running helly bean nightly s
I have switched batteries with my gf cappy so I'm pretty sure its not a battery issue
Click to expand...
Click to collapse
With a metal back of cappy, it will easily heat up because it conducts heat in the metal. Based on my experience it is cause by the user usage depending on how high is the voltage/clock require of each app used to maintain it's smoothness and reached it's maximum clock. You can see your usage at Settings>Battery.
You can use CPU Spy or Voltage Control to see your OC and adjust it. You can check also in Settings> Performance >Processor.
---------- Post added at 02:36 AM ---------- Previous post was at 02:28 AM ----------
brttwilliams said:
I'm still a NUB, lol, I don't deny it, but I'm all about learning the way of the Droid.... I added some of the Devil Helly Bean Add-On apk's into the Slim Bean, so I have my high points, just have the low ones just as often..
Click to expand...
Click to collapse
Yeah, you'll learn in time, just try to search and read throughout the forums. I suggest that you lower your min to 100/200 and max to 1000/1200,
use smartassv2 and sio governor. This settings saves me some battery and to extent that still smooth, slick and good ui/gaming/app performance.
If you're on DEVIL KERNEL, go to recovery>devil>governor profile> tick SMOOTH.
brttwilliams said:
I'm still a NUB, lol, I don't deny it, but I'm all about learning the way of the Droid.... I added some of the Devil Helly Bean Add-On apk's into the Slim Bean, so I have my high points, just have the low ones just as often..
Click to expand...
Click to collapse
Wasn't doggin' you dude, Just letting you know that could be the cause of your problem. Awhile ago I might have flamed you, I have matured and get that not everyone reads (not this situation), and I have to get used to that. People make mistakes, I know I do even if I wanna act like I don't. I am just helping around here now since I have gotten as much knowledge as the some of the users that joined XDA and other hacking forums in the beginning because I was always searching to find out ways to do it on my own, asking for help with stuff that no one talked about. So I am glad that I was able to help you in a way, sorta.
b-eock said:
Wasn't doggin' you dude, Just letting you know that could be the cause of your problem. Awhile ago I might have flamed you, I have matured and get that not everyone reads (not this situation), and I have to get used to that. People make mistakes, I know I do even if I wanna act like I don't. I am just helping around here now since I have gotten as much knowledge as the some of the users that joined XDA and other hacking forums in the beginning because I was always searching to find out ways to do it on my own, asking for help with stuff that no one talked about. So I am glad that I was able to help you in a way, sorta.
Click to expand...
Click to collapse
Thank you both, b and takeout.... I know neither of you were doggin me, b-eock. I've been one of the behind the scenes types but I've seen a few of your posts, I know you know what you're talking about, I definitely appreciate the guidance. Truth be told, I know I'm still a nub here, but I know my way well enough, after you break something a few times, its only natural to pick up a few tricks along the way.
Yeah you'll learn something here just have the patience, experiment, test things out yourself to conclude and rather soon it'll be your hobby reading
And also help others out too.
Sent from my SGH-I897 using xda premium
my gets hot sometimes too. im on helly bean latest 08/08/12 version, also battery gets sucked down quick, barely get 8 hrs and i do virtually nothing. ics cm9 was great on battery.
VashTS said:
my gets hot sometimes too. im on helly bean latest 08/08/12 version, also battery gets sucked down quick, barely get 8 hrs and i do virtually nothing. ics cm9 was great on battery.
Click to expand...
Click to collapse
I know my battery is going quick on the SlimBean 2.0 ROM, but the heat issue still happens, I have noticed with my OS monitoring tool that it gets hotter if you have programs running constantly in background using up high CPU %. I was able to isolate a few of the programs as things I could remove, overall it does still run hot, but it's not as bad.
I use the free version of the OS Monitor on Play Store, you can set it to run under root and to autostart when the device is turned on.
Picked up an 1800 mah battery and my batty life is great! Going to bed with 40ish percent left
Haha, well let me know where you snagged that from
Sent from my SGH-I897 using xda premium
try Smartassv2 gov and change your min from 600 to 100, then note the temps, or run a log of them.
typically my phone runs about 35° C (95° F) and that is with an otterbox commuter case on the phone. When the gps is on in the car, I use a vent mount to keep it at 40° or less, and never have to take the case off.
I read that higher temps, example 45°, really shorten battery life, and you wiil only get 200 charge cycles instead of 500 from the battery.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
brttwilliams said:
Haha, well let me know where you snagged that from
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Amazon, was a great purchase, got an oem battery, there is a huge thread in the accessories section about the 1800 mah epic 4G battery that fits in the cappy