Related
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
OK, so I know there has been a lot of b*tching about the Tbolt battery life, especially if you are running Gingerbread and a Sense 2.1 or 3.0 ROM (I am running BAMF 3.0 R4.9). I just may have solved this issue when you can connect to a WiFi access point!
Using a program called Tasker, I have created specific profiles that actually help save my battery as well as do a lot of other things to make life easier. The learning curve is somewhat steep for non-Tech geeks, but it's not too difficult after you get the hang of it. (I think the only version of Tasker in the market is pay for use, but you can get a free trial from the Dev's website directly.)
On to how I can get a 22+ hour standard TBolt battery:
1st new profile:
-Called "WiFi"
-Context = WiFi Connected (Any SSID)
-Task = NET>WiFi Sleep>Never
2nd new profile:
-Called "Dim Screen"
-Context = Power Source Any, click "Invert" button (so when the phone is not charging).
-Task = Display>Display Brightness>Set to "20" and check "Immediate Effect" (you can certainly change it to something higher, but you may not get nearly the same battery life).
On WiFi, I can get almost 23 hours of battery. On 4G, I can get upwards of 8 hours, 3G I have yet to test.
Since LTE was just turned on near where I live, I noticed that my TBolt was making WiFi sleep while it sat in my pocket not in use, therefor switching to 4G/LTE and draining the battery. The brightness obviously helps when I am not plugged in no matter if I am 3G/4G/WiFi.
I have some other useful profiles setup. Like I have the phone screen go to Auto Brightness and into the Sense Dock Mode when the phone is charging. My favorite is the Car Dock Profile... when the phone goes into my Car Dock, the Bluetooth turns on, GPS goes on, and Google Music Starts.
I am a big fan of Tasker now... there are a lot of possibilities with the program!
WorldOfJohnboy said:
OK, so I know there has been a lot of b*tching about the Tbolt battery life, especially if you are running Gingerbread and a Sense 2.1 or 3.0 ROM (I am running BAMF 3.0 R4.9). I just may have solved this issue when you can connect to a WiFi access point!
Using a program called Tasker, I have created specific profiles that actually help save my battery as well as do a lot of other things to make life easier. The learning curve is somewhat steep for non-Tech geeks, but it's not too difficult after you get the hang of it. (I think the only version of Tasker in the market is pay for use, but you can get a free trial from the Dev's website directly.)
On to how I can get a 22+ hour standard TBolt battery:
1st new profile:
-Called "WiFi"
-Context = WiFi Connected (Any SSID)
-Task = NET>WiFi Sleep>Never
2nd new profile:
-Called "Dim Screen"
-Context = Power Source Any, click "Invert" button (so when the phone is not charging).
-Task = Display>Display Brightness>Set to "20" and check "Immediate Effect" (you can certainly change it to something higher, but you may not get nearly the same battery life).
On WiFi, I can get almost 23 hours of battery. On 4G, I can get upwards of 8 hours, 3G I have yet to test.
Since LTE was just turned on near where I live, I noticed that my TBolt was making WiFi sleep while it sat in my pocket not in use, therefor switching to 4G/LTE and draining the battery. The brightness obviously helps when I am not plugged in no matter if I am 3G/4G/WiFi.
I have some other useful profiles setup. Like I have the phone screen go to Auto Brightness and into the Sense Dock Mode when the phone is charging. My favorite is the Car Dock Profile... when the phone goes into my Car Dock, the Bluetooth turns on, GPS goes on, and Google Music Starts.
I am a big fan of Tasker now... there are a lot of possibilities with the program!
Click to expand...
Click to collapse
I'm gonna say you might want to try a MUCH more modern ROM. I'm having very little trouble eeking 18 hours out of mine under moderate use, and well over a day if I'm not messing with it much. It will typically consume around 1.7% per hour unused, LTE on.
WorldOfJohnboy said:
OK, so I know there has been a lot of b*tching about the Tbolt battery life, especially if you are running Gingerbread and a Sense 2.1 or 3.0 ROM (I am running BAMF 3.0 R4.9). I just may have solved this issue when you can connect to a WiFi access point!
Using a program called Tasker, I have created specific profiles that actually help save my battery as well as do a lot of other things to make life easier. The learning curve is somewhat steep for non-Tech geeks, but it's not too difficult after you get the hang of it. (I think the only version of Tasker in the market is pay for use, but you can get a free trial from the Dev's website directly.)
On to how I can get a 22+ hour standard TBolt battery:
1st new profile:
-Called "WiFi"
-Context = WiFi Connected (Any SSID)
-Task = NET>WiFi Sleep>Never
2nd new profile:
-Called "Dim Screen"
-Context = Power Source Any, click "Invert" button (so when the phone is not charging).
-Task = Display>Display Brightness>Set to "20" and check "Immediate Effect" (you can certainly change it to something higher, but you may not get nearly the same battery life).
On WiFi, I can get almost 23 hours of battery. On 4G, I can get upwards of 8 hours, 3G I have yet to test.
Since LTE was just turned on near where I live, I noticed that my TBolt was making WiFi sleep while it sat in my pocket not in use, therefor switching to 4G/LTE and draining the battery. The brightness obviously helps when I am not plugged in no matter if I am 3G/4G/WiFi.
I have some other useful profiles setup. Like I have the phone screen go to Auto Brightness and into the Sense Dock Mode when the phone is charging. My favorite is the Car Dock Profile... when the phone goes into my Car Dock, the Bluetooth turns on, GPS goes on, and Google Music Starts.
I am a big fan of Tasker now... there are a lot of possibilities with the program!
Click to expand...
Click to collapse
how do you get the GPS to enable? I've tried to set up my GPS to come when I open maps, navigation or anything that needs gps enable but I get "sorry that action is unavailable on this device."
Llama also does what Tasker does. And its free. I find that Llama works better too. I can get near 24 hours with everything stock.
loonatik78 said:
I'm gonna say you might want to try a MUCH more modern ROM. I'm having very little trouble eeking 18 hours out of mine under moderate use, and well over a day if I'm not messing with it much. It will typically consume around 1.7% per hour unused, LTE on.
Click to expand...
Click to collapse
Modern? The ROM I have is running Gingerbread and is full Sense 3.0 (which appears to be a big battery hog). When I was on a GB Sense 2.1 ROM from the same Dev, I was getting better battery. The only thing that may improve the battery any more on GB/Sense 3.0 would be a new and improved Kernel, though I think I am on one of the more stable ones.
warmonster said:
how do you get the GPS to enable? I've tried to set up my GPS to come when I open maps, navigation or anything that needs gps enable but I get "sorry that action is unavailable on this device."
Click to expand...
Click to collapse
You are right, my bad... it throws up a disclaimer that GPS enabling is not available on any 2.3 ROM because of the Pop-up. They suggest using Cyanogen (sp) if you want to use the feature on a 2.3 ROM.
andydumi said:
Llama also does what Tasker does. And its free. I find that Llama works better too. I can get near 24 hours with everything stock.
Click to expand...
Click to collapse
Potato, Patahto. I like Tasker and found it really granular once I started playing with it. I don't mind paying for an app that is well Developed and supported. (If you like Llama that much, you should use the donate version to "thank" the Dev team!) The 23hrs is an estimated capacity right now as Battery Left is still calibrating.
WorldOfJohnboy said:
Modern? The ROM I have is running Gingerbread and is full Sense 3.0 (which appears to be a big battery hog). When I was on a GB Sense 2.1 ROM from the same Dev, I was getting better battery. The only thing that may improve the battery any more on GB/Sense 3.0 would be a new and improved Kernel, though I think I am on one of the more stable ones.
Click to expand...
Click to collapse
I think he is refering to roms based off the 2.11 leak. battery life in that Ruu is much better than any other previous ruu. Any roms based off it will give you more life by default. The bamf 4.9 Rom is kinda old when your talking about custom roms and it isn't based on the 2.11 ruu.
Sent from my ADR6400L using xda premium
WorldOfJohnboy said:
Modern? The ROM I have is running Gingerbread and is full Sense 3.0 (which appears to be a big battery hog). When I was on a GB Sense 2.1 ROM from the same Dev, I was getting better battery. The only thing that may improve the battery any more on GB/Sense 3.0 would be a new and improved Kernel, though I think I am on one of the more stable ones.
Click to expand...
Click to collapse
You say BAMF 3.0 R4.9 is your ROM. This ROM is old, based upon the 2.01 GB leak (which is about 4 leaks ago), which was terribly flawed in many ways, and isn't even being developed by BAMF anymore. The newer kernels won't even work right on that ROM because aspects of the WiFi and camera have been changed in later leaks.
You're application of Tasker is probably one of the ONLY rational uses of such an app. Using it for such things as turning GPS on and off is pointless, and redundant, because Android already does that as long as you have GPS enabled. Having it enabled doesn't use any power unless you're using apps that abuse it, such as some of the traffic update apps that constantly update your position.
Power management apps aren't quite as useless as task killer apps, but for the purposes I see people use them for, they're not doing you many favors. I'm generally not a fan of these apps and I strongly recommend against task killers because the result of their use simply increases the amount of NAND reads the CPU must make, which is the most power intensive operation that CPU performs.
Newer ROMs, such as the RUU 2.10 and 2.11 based ROMs, are significantly better on battery life than the older ones, especially when used with the radios from the 1.70 OTA, 2.07 RUU, 2.10 RUU, and 2.11 RUU. I'd make the jump to a more modern ROM before I tried manipulating an older one to perform. Or, move up to a newer one and do the same thing and see what you get. In any event, there's good room for improvement.
I tried several ways to conserve battery and finally decided that it just isn't worth it to me to have to stop running game apps, to have to set the phone up a specific way, to carefully monitor what each app does etcetera. I went out Tuesday and bought a extended battery from a Verizon store. With discount I paid $25.00 for the battery and cover. I am now getting right around twenty five hours total battery life off one charge and I have watched videos, played games, played music, and did whatever else I could think of to kill that battery. I am ecstatic with it. Now when I am out overnight mountain climbing with the missus granted I will undoubtedly kill some apps. Wouldn't do to run into BigFoot, Smokey the Bear, and Jason Vorhies with a dead battery and no chocolate bars ( since she for some reason feels I should diet) now would it?
ps. I made sure it had antennaes on the cover. It has more than my original cover does. And the clerk had no clue why i was even asking about the antenaes on the cover
TDubKong said:
I tried several ways to conserve battery and finally decided that it just isn't worth it to me to have to stop running game apps, to have to set the phone up a specific way, to carefully monitor what each app does etcetera. I went out Tuesday and bought a extended battery from a Verizon store. With discount I paid $25.00 for the battery and cover. I am now getting right around twenty five hours total battery life off one charge and I have watched videos, played games, played music, and did whatever else I could think of to kill that battery. I am ecstatic with it. Now when I am out overnight mountain climbing with the missus granted I will undoubtedly kill some apps. Wouldn't do to run into BigFoot, Smokey the Bear, and Jason Vorhies with a dead battery and no chocolate bars ( since she for some reason feels I should diet) now would it?
ps. I made sure it had antennaes on the cover. It has more than my original cover does. And the clerk had no clue why i was even asking about the antenaes on the cover
Click to expand...
Click to collapse
Reps are pretty clueless, in general. They're sales people and that's about it. That's what cracks me up when I see these goofy "corporate memos" that supposedly when out to stores with stuff like RUU and radio version numbers on them. Like the geek behind the counter actually knows any of that???
loonatik78 said:
Reps are pretty clueless, in general. They're sales people and that's about it. That's what cracks me up when I see these goofy "corporate memos" that supposedly when out to stores with stuff like RUU and radio version numbers on them. Like the geek behind the counter actually knows any of that???
Click to expand...
Click to collapse
Yea tell me about it. At the Verizon kiosk in Costco I actually argued with the guy because he was spouting off about the Specs on AT&T phones being better than what were on the Thunderbolt. Saying how much better AT&T was and all this stuff. I listened for only a few minutes before I realized he was an imbecile. He was just throwing out things that made him sound like he knew what he was talking about. And yea you read that right. This brain fart of a human being was promoting AT&T from a Verizon kiosk
TDubKong said:
Yea tell me about it. At the Verizon kiosk in Costco I actually argued with the guy because he was spouting off about the Specs on AT&T phones being better than what were on the Thunderbolt. Saying how much better AT&T was and all this stuff. I listened for only a few minutes before I realized he was an imbecile. He was just throwing out things that made him sound like he knew what he was talking about. And yea you read that right. This brain fart of a human being was promoting AT&T from a Verizon kiosk
Click to expand...
Click to collapse
Further proving Einstein's point... The difference between genius and stupidity is that genius has it's limits.
loonatik78 said:
You say BAMF 3.0 R4.9 is your ROM. This ROM is old, based upon the 2.01 GB leak (which is about 4 leaks ago), which was terribly flawed in many ways, and isn't even being developed by BAMF anymore. The newer kernels won't even work right on that ROM because aspects of the WiFi and camera have been changed in later leaks.
Click to expand...
Click to collapse
If you can point me to a ROM that has full Sense 3.0 and the latest GB leak, please point me in that direction.
You're application of Tasker is probably one of the ONLY rational uses of such an app. Using it for such things as turning GPS on and off is pointless, and redundant, because Android already does that as long as you have GPS enabled. Having it enabled doesn't use any power unless you're using apps that abuse it, such as some of the traffic update apps that constantly update your position.
Click to expand...
Click to collapse
Considering I do use a bunch of Apps that can use GPS (Foursquare, Weather, and my Car Dock=Car Home) and I don't always need GPS on to do what I do in them, I choose to have GPS inactive as to not chew up more battery than is necessary.
Power management apps aren't quite as useless as task killer apps, but for the purposes I see people use them for, they're not doing you many favors. I'm generally not a fan of these apps and I strongly recommend against task killers because the result of their use simply increases the amount of NAND reads the CPU must make, which is the most power intensive operation that CPU performs.
Click to expand...
Click to collapse
I have never and will never use a task killer. Tasker is basically a way to create a 'macro' or series of them to help do things without having to click 18 different things on your phone. Apples to oranges.
Newer ROMs, such as the RUU 2.10 and 2.11 based ROMs, are significantly better on battery life than the older ones, especially when used with the radios from the 1.70 OTA, 2.07 RUU, 2.10 RUU, and 2.11 RUU. I'd make the jump to a more modern ROM before I tried manipulating an older one to perform. Or, move up to a newer one and do the same thing and see what you get. In any event, there's good room for improvement.
Click to expand...
Click to collapse
As I said, if there is a viable full Sense 3.0 ROM with the latest RUU out there, please let me know what it is. Until that happens, I will use Tasker to fix the flaws that exist in my current RUU/ROM.
loonatik78 said:
You say BAMF 3.0 R4.9 is your ROM. This ROM is old, based upon the 2.01 GB leak (which is about 4 leaks ago), which was terribly flawed in many ways, and isn't even being developed by BAMF anymore. The newer kernels won't even work right on that ROM because aspects of the WiFi and camera have been changed in later leaks.
Click to expand...
Click to collapse
Really...newer kernels don't work with BAMF 3.0 RC4.9??? That's funny because I'm running Ziggy's latest on BAMF 3.0 RC4.9 with working WiFi and camera, front and back.
Out of all the 3.0, 2.1/3.0 ROM's this is the only one that I have never missed a call because I could not answer the phone because of the end only call bug.
It might be an older ROM but it's still one of the best for this phone.
UberBAMF, Adrynalyne's side-project BAMF, both of the Gingeritis ROMs, Th3ory's ROMs, Synergy... Where the Ziggy kernel came from. Maybe I'm wrong and 4.9 uses the 2.07 base. I've used nothing but 2.07 and newer Chingy ROMs for the last 2 months as daily drivers and I've never once seen this "end call only" bug.
Ziggy's kernels aren't freely available so I don't consider it an available custom kernel.
loonatik78 said:
UberBAMF, Adrynalyne's side-project BAMF, both of the Gingeritis ROMs, Th3ory's ROMs, Synergy... Where the Ziggy kernel came from. Maybe I'm wrong and 4.9 uses the 2.07 base. I've used nothing but 2.07 and newer Chingy ROMs for the last 2 months as daily drivers and I've never once seen this "end call only" bug.
Ziggy's kernels aren't freely available so I don't consider it an available custom kernel.
Click to expand...
Click to collapse
Anyone that downloads Gingeritis, or Synergy has full access to Ziggy's kernels. I would call that freely available. Either which way they still work on BAMF 3.0 RC4.9.
As for the ROM's you listed not one of them are a full Sense 3.0 ROM like RC4.9.
If you have never had the end only call bug consider yourself lucky because there are theads on both themikmik and team BAMF about this bug.
Sent from my ADR6400L using XDA App
End-call only bug is real. In 2 months of running bamf (currently on uber 3), I've encountered it once. Others have been plagued with it. Basically, when someone calls, it only displays the large "end call" button.
Sent from my ADR6400L using XDA App
bp328i said:
Anyone that downloads Gingeritis, or Synergy has full access to Ziggy's kernels. I would call that freely available. Either which way they still work on BAMF 3.0 RC4.9.
As for the ROM's you listed not one of them are a full Sense 3.0 ROM like RC4.9.
If you have never had the end only call bug consider yourself lucky because there are theads on both themikmik and team BAMF about this bug.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
I hardly call Ziggy's kernel freely available by any stretch of the imagination. That's like saying iOS is free to anyone to use. Not really if you ONLY get it with this product or that! Ziggy also flouts the GPL like it's no big deal, so obtaining his source is nigh impossible. He's got one of the least available kernels that exists.
Sense 3.0 is eye candy. Like live wallpaper, its cool for a day, that's about it. And Rosie launcher is weak. I mean, if that's your thing, cool. It's your phone. But AOSP roms are far beyond BAMF, and far more stable. Shift B2 is the best rom I've run on my Bolt, hands down. With G+ loaded I get between 18-22 hours moderate use. Without G+ I can get a little over 28 hours. This is all 3G, as our towers havent been upgraded yet here in BFE. I understand the desire for battery life on stock battery. I pocket mine for 8 hours a day, so extended battery is unappealing. I underclock to 768 and my phone is still more responsive than it was with sense at 1.4.
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.
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.
Many of us have long weekends away in the Summer with no source of power. Can anyone point me to some tips for getting the most out of a single charge. I'm going to keep as many things turned off (wifi, BT, GPS), screen as dim as possible, switch to 2G and no data unless I need them, is there anything else. I have a boeffla kernel so I guess maybe some underclocking and so on, but I don't feel knowledgeable about that!
patp said:
Many of us have long weekends away in the Summer with no source of power. Can anyone point me to some tips for getting the most out of a single charge. I'm going to keep as many things turned off (wifi, BT, GPS), screen as dim as possible, switch to 2G and no data unless I need them, is there anything else. I have a boeffla kernel so I guess maybe some underclocking and so on, but I don't feel knowledgeable about that!
Click to expand...
Click to collapse
Diable every radio is not needed + underclocking will help. Reduce GPU to 200 Mhz, CPU to about 1.4 GHz and disable autosync of data, swtitch to 2G.
Also why don't you bring a powerbank with you in case of emergency
patp said:
Many of us have long weekends away in the Summer with no source of power. Can anyone point me to some tips for getting the most out of a single charge. I'm going to keep as many things turned off (wifi, BT, GPS), screen as dim as possible, switch to 2G and no data unless I need them, is there anything else. I have a boeffla kernel so I guess maybe some underclocking and so on, but I don't feel knowledgeable about that!
Click to expand...
Click to collapse
How about turning the damn thing off? You're at a festival, so enjoy the music and the atmosphere, turn the phone back on once in the morning and once in the evening just in case someone needs to get hold of you. Otherwise it doesn't really matter how much you try to minimise battery use, you're not going to get through a weekend.
patp said:
Many of us have long weekends away in the Summer with no source of power. Can anyone point me to some tips for getting the most out of a single charge. I'm going to keep as many things turned off (wifi, BT, GPS), screen as dim as possible, switch to 2G and no data unless I need them, is there anything else. I have a boeffla kernel so I guess maybe some underclocking and so on, but I don't feel knowledgeable about that!
Click to expand...
Click to collapse
Young kids of today have no idea.
Seriously if you are at a festival and you are worried about your phone lasting you are doing it all wrong. One thing experience has taught me is that you organise your....ahem, supplies beforehand.
A much greater risk is your phone getting lost smashed or stolen. I am sure the land mass of Glastonbury is by now made of 50% trampled phones.
So turn your phone of, put it away, purchase a battery pack relax and have a good time.
I'm 48 you know!
It went well, phone lasted four days with minimal use for texting, photos and the odd call. We had four smartphones with the odd top up from a 10000MAh power bank and all finished with charge. The best performer was a little Huawai, then a Moto G, then my OPO, then a Samsung Atrix.
I totally agree that it's best to minimize phone use at a festival, but pre-mobile I remember many a Glaso constantly failing to meet up with mates. It's a lot easier these days.
patp said:
Many of us have long weekends away in the Summer with no source of power. Can anyone point me to some tips for getting the most out of a single charge. I'm going to keep as many things turned off (wifi, BT, GPS), screen as dim as possible, switch to 2G and no data unless I need them, is there anything else. I have a boeffla kernel so I guess maybe some underclocking and so on, but I don't feel knowledgeable about that!
Click to expand...
Click to collapse
You can disable hotplugging and only have one core running which will help save battery. The best thing to do when going for long days is to keep your brightness low. Good luck!
patp said:
Many of us have long weekends away in the Summer with no source of power. Can anyone point me to some tips for getting the most out of a single charge. I'm going to keep as many things turned off (wifi, BT, GPS), screen as dim as possible, switch to 2G and no data unless I need them, is there anything else. I have a boeffla kernel so I guess maybe some underclocking and so on, but I don't feel knowledgeable about that!
Click to expand...
Click to collapse
Since you are already using Boeffla kernel, I am sure you will underclock the CPU and GPU to power save modes. You need to switch off google location services. Install a software that can take log of your device's wakelocks and you might want to disable those applications. Xposed is still in Alpha but AMPLIFY on Xposed was a great wakelock fix. You can install GREENIFY from PlayStore to make sure apps are hibernated when not been used.
Qrze said:
You can disable hotplugging and only have one core running which will help save battery. The best thing to do when going for long days is to keep your brightness low. Good luck!
Click to expand...
Click to collapse
10k35h said:
Since you are already using Boeffla kernel, I am sure you will underclock the CPU and GPU to power save modes. You need to switch off google location services. Install a software that can take log of your device's wakelocks and you might want to disable those applications. Xposed is still in Alpha but AMPLIFY on Xposed was a great wakelock fix. You can install GREENIFY from PlayStore to make sure apps are hibernated when not been used.
Click to expand...
Click to collapse
You guys didn't actually read the thread, did you...