Related
Hey guys,
I have been trying to solve this on my own for two days now, but I would like to consult the forum now.
So, I was running Pink Sense 1.8 for about 2 weeks with setCPU profiles and was getting satisfactory battery life. I had re-calibrated the battery info maybe 2 weeks before flashing the Pinky ROM (as described here: http://forum.xda-developers.com/showthread.php?t=755903).
All of a sudden, without any app installation or change to either the ROM or software/hardware settings I started getting horrible battery life. The battery would drain completely for less than 6 hours with GPS, 3G, and WiFi off.
*Another strange thing (which I don't know if it was related to my battery issue or not) was that when I would plug the charger it would turn the screen on but switch to the default clock app instead of the HTC sense homescreen. If I pressed home or back it would disappear. This would happen randomly and not always.
So, I figured it's time to jump ROMs and I decided on LeeDroid. I wiped cache, etc. and flashed the ROM. Out of the box the battery life was again pretty crappy (the battery was virtually disappearing in front of my eyes). I found some threads where it was suggested to disable market notifications and that slowed the battery drain a bit but it's still crappy.
I just charged it fully, 3G and WiFi off, and was with the screen off for 99% of the time and it still drained 18% battery in 1hour and 25 mins.
So, my question is - what the hell is going on???
Should I wipe battery info? Should I install a non-WiFi n rom? What more can I do?
I would really appreciate help and advice.
p.s. I am running the latest radio too.
wich radio have you the .23 drains the batery with my desire try with the .30_2
the battery life is better.
did you try reboot your phone maybe your optical joystick dead and drain your battery.
load any new apps recently?
cr1960 said:
load any new apps recently?
Click to expand...
Click to collapse
As I said, the problem appeared with absolutely no new apps installed and persists after flashing a new ROM.
How do I know if my optical joystick is dead? It still works if that's what you mean (although I don't like using it).
I will try flashing the 30_2 radio, thanks for that suggestion.
slyn4ice said:
How do I know if my optical joystick is dead? It still works if that's what you mean (although I don't like using it).
Click to expand...
Click to collapse
If it works he's not dead
after flashing your radio and if the battery still drain check if the rom you use has his own rules for the cpu freq. if you are in that case don't use cpufreq or something like that because of conflicts.
PS: Sory for my bad english
Sithlord31 said:
If it works he's not dead
after flashing your radio and if the battery still drain check if the rom you use has his own rules for the cpu freq. if you are in that case don't use cpufreq or something like that because of conflicts.
PS: Sory for my bad english
Click to expand...
Click to collapse
Thanks, I just flashed the 17_2 radio. It doesn't look like LeeDroid has any requirements for cpu frequencies. I will post an update after an hour.
slyn4ice said:
Thanks, I just flashed the 17_2 radio. It doesn't look like LeeDroid has any requirements for cpu frequencies. I will post an update after an hour.
Click to expand...
Click to collapse
There seems to be no change with 17_2 radio. 15% drop for 1h45m. I will go through a charge/recharge cycle and if nothing has changed I will flash the 30_2 radio.
Some people had the same effect. It happens when you flash your ROM while the phone is connected to power/charging. The battery stats simply get messed up.
An easy indication for this is if you charge the phone fully while powered on, LED is green, as soon as you unplug the charger the battery drops to some 90%.
The fix is easy too. If the phone is fully "charged" while on, disconnect the charger and switch it off. Then plug the charger in again. The LED should turn orange again and the remaining percentage will be charged. Wait until you have a green LED and your problems are hopefully gone.
Look out for the battery calibrating thread here for more info.
Hope that helps...
Mac
mmaacc said:
Some people had the same effect. It happens when you flash your ROM while the phone is connected to power/charging. The battery stats simply get messed up.
An easy indication for this is if you charge the phone fully while powered on, LED is green, as soon as you unplug the charger the battery drops to some 90%.
The fix is easy too. If the phone is fully "charged" while on, disconnect the charger and switch it off. Then plug the charger in again. The LED should turn orange again and the remaining percentage will be charged. Wait until you have a green LED and your problems are hopefully gone.
Look out for the battery calibrating thread here for more info.
Hope that helps...
Mac
Click to expand...
Click to collapse
Thanks for the suggestions. I always thought it would be better to flash with the ac adapter plugged.
I have tried the method you described above but it hasn't really solved any of the problems.
The battery drain is now at least manageable - i had 50% drop while sleeping for 6 hours (at least it didn't drain it completely). I am going to flash the 30_2 radio and try again.
slyn4ice said:
Thanks for the suggestions. I always thought it would be better to flash with the ac adapter plugged.
I have tried the method you described above but it hasn't really solved any of the problems.
The battery drain is now at least manageable - i had 50% drop while sleeping for 6 hours (at least it didn't drain it completely). I am going to flash the 30_2 radio and try again.
Click to expand...
Click to collapse
If you have access to a spare battery, maybe you can try that too?
Normally when I have unexplained problems with the phone, the last drastic step I would take is to wipe everything, data/app/cache. Do a nandroid backup first so that if that doesn't solve your problem you could always get back all your setups.
You could also try Titanium to help save your setup. But I would be careful with what I restore. The last thing I would want is to get the messed up setting back in.
I have noticed also whenever I flash a new rom, the battery seems to get worse. So I would always do a recalibration. The proper step is here:
http://forum.xda-developers.com/showthread.php?t=755903 (and wipe the battery status on the last power up before using).
Lastly, I would use as stock as possible first to see if it is things that I introduce that cause the problem.
pehkblui said:
If you have access to a spare battery, maybe you can try that too?
Normally when I have unexplained problems with the phone, the last drastic step I would take is to wipe everything, data/app/cache. Do a nandroid backup first so that if that doesn't solve your problem you could always get back all your setups.
You could also try Titanium to help save your setup. But I would be careful with what I restore. The last thing I would want is to get the messed up setting back in.
I have noticed also whenever I flash a new rom, the battery seems to get worse. So I would always do a recalibration. The proper step is here:
http://forum.xda-developers.com/showthread.php?t=755903 (and wipe the battery status on the last power up before using).
Lastly, I would use as stock as possible first to see if it is things that I introduce that cause the problem.
Click to expand...
Click to collapse
I think I can definitely confirm the radio is the problem. There is barely any battery drain in airplane mode (1% drain per hour with WiFi on). I am back to 32.43.00.32U_5.09.00.20 but it seems to drain battery faster than before.
Now that I think back, this battery problem started when i switched to the newer 32.47.00.32U_5.10.05.23 radio. No matter what I do now though even after rolling back to older radios it's still a problem. Damn it.
slyn4ice said:
I think I can definitely confirm the radio is the problem. There is barely any battery drain in airplane mode (1% drain per hour with WiFi on). I am back to 32.43.00.32U_5.09.00.20 but it seems to drain battery faster than before.
Now that I think back, this battery problem started when i switched to the newer 32.47.00.32U_5.10.05.23 radio. No matter what I do now though even after rolling back to older radios it's still a problem. Damn it.
Click to expand...
Click to collapse
Don´t know (because i never updated radios above .20 and have no problems with battery)...but...maybe flash a original ruu rom...and root again
maybe this help...with kind regards..Alex
Alex-V said:
Don´t know (because i never updated radios above .20 and have no problems with battery)...but...maybe flash a original ruu rom...and root again
maybe this help...with kind regards..Alex
Click to expand...
Click to collapse
that doesn't help, ive tried it already
TieT said:
that doesn't help, ive tried it already
Click to expand...
Click to collapse
Ok, I have awesome news! Thanks to user "lenik" on modaco forums I got some extra RIL settings (radio settings) he found for Softbank (my cellphone company here in Japan). Here are the settings:
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.fast.dormancy.timeout=3
ro.ril.enable.sbm.feature=1
He said the first two should be found on most ROMs, while the last two are probably carrier specific for SoftBank. Anyways, I just downloaded the latest LeeDroid ROM, modified /system/build.prop file (none of the above settings were in there) to include the above settings and ... got a 5% drop in battery for 10 hours on standby (wifi off, setCPU set to 245Mhz when screen is off). This is unbelievable.
Anyways, here are lenik's blog posts about it:
http://lazydroid.com/2010/06/battery-life-improved/
http://lazydroid.com/2010/06/back-to-1-21-...ry-consumption/
I hope this helps other people out there!
slyn4ice said:
Ok, I have awesome news! Thanks to user "lenik" on modaco forums I got some extra RIL settings (radio settings) he found for Softbank (my cellphone company here in Japan). Here are the settings:
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.fast.dormancy.timeout=3
ro.ril.enable.sbm.feature=1
He said the first two should be found on most ROMs, while the last two are probably carrier specific for SoftBank. Anyways, I just downloaded the latest LeeDroid ROM, modified /system/build.prop file (none of the above settings were in there) to include the above settings and ... got a 5% drop in battery for 10 hours on standby (wifi off, setCPU set to 245Mhz when screen is off). This is unbelievable.
Anyways, here are lenik's blog posts about it:
http://lazydroid.com/2010/06/battery-life-improved/
http://lazydroid.com/2010/06/back-to-1-21-...ry-consumption/
I hope this helps other people out there!
Click to expand...
Click to collapse
VERY nice results! Do you think that these RIL settings should work on any network/carrier?
It's very odd because today I noticed my battery performance dropping large, BUT before it was always great. I am also on LeeDrOiD 2.1, and while at home, with WiFi + BT on AND connected to my router + handsfree, I lose only about 3-4% an hour.
Today when I left the house and went shopping, I was in the store for 1.5 hrs and I had lost near 15%! I had even turned off Wifi so it wasn't trying to scan APs. Very very strange...
Anyways, I want to maybe try these RIL settings if it will work on any carrier. Does anyone know if I can edit build.prop while in recovery, or do I have to edit it in the ROM .zip then reflash the entire ROM?
Thanks for the post and hunting down a solution slyn4ice, I'm glad that it has helped you out big time!
*** EDIT *** - After looking more into my JuicePlotter graphs, I notice that the battery life gets killed when I am using APN / 3G / HSPA network. I would have thought Wifi would take more power, but that seems not to be so. I DID have "Network Mode" set to "WCDMA only" (in Mobile Network Settings) because I heard it might save battery not having to switch back and forth from EDGE to 3G, but I guess that didn't help...I've since switched it back, but need a lot of charging before I can test again.
Does anyone else notice that when they're on 3G/H the battery drops MUCH quicker than if you were connected to Wifi instead? This is just my last hurdle towards a PERFECT ROM!
Thanks in advance all!
3G uses waaay more power than WiFi. After all, the data usually travels long distances and needs to be amplified. This effect is pronounced especially if in the limit zones of 2G/3G coverage and you have 3G preferred, the phone boosts the power to maximum to maintain 3G.
Gsm Auto (PRL) prefers 2G if 3G coverage is too low. WCDMA Preferred tries to maintain 3G connection even if it means sacrificing battery life.
If you are constantly in good coverage zones, no problem, but to the people living on the edges of proper 3G coverage it meas a big hit to battery life, especially if the mobile data is used. This partly explains why some get superb battery life and others far worse.
Jgruar said:
3G uses waaay more power than WiFi. After all, the data usually travels long distances and needs to be amplified. This effect is pronounced especially if in the limit zones of 2G/3G coverage and you have 3G preferred, the phone boosts the power to maximum to maintain 3G.
Gsm Auto (PRL) prefers 2G if 3G coverage is too low. WCDMA Preferred tries to maintain 3G connection even if it means sacrificing battery life.
If you are constantly in good coverage zones, no problem, but to the people living on the edges of proper 3G coverage it meas a big hit to battery life, especially if the mobile data is used. This partly explains why some get superb battery life and others far worse.
Click to expand...
Click to collapse
Amazing explanation and reaffirmation of my thoughts Jgruar (JuicePlotter confirms it). I guess from my old WinMo days, I always remember Wifi being the power hog. I actually did change it back to GSM/Auto since that was the only change I made lately, but I thought I'd chime in while my device was charging back up, hoping for a reply just like that!
Thanks a bunch!
scar45 said:
VERY nice results! Do you think that these RIL settings should work on any network/carrier?
It's very odd because today I noticed my battery performance dropping large, BUT before it was always great. I am also on LeeDrOiD 2.1, and while at home, with WiFi + BT on AND connected to my router + handsfree, I lose only about 3-4% an hour.
Today when I left the house and went shopping, I was in the store for 1.5 hrs and I had lost near 15%! I had even turned off Wifi so it wasn't trying to scan APs. Very very strange...
Anyways, I want to maybe try these RIL settings if it will work on any carrier. Does anyone know if I can edit build.prop while in recovery, or do I have to edit it in the ROM .zip then reflash the entire ROM?
Thanks for the post and hunting down a solution slyn4ice, I'm glad that it has helped you out big time!
*** EDIT *** - After looking more into my JuicePlotter graphs, I notice that the battery life gets killed when I am using APN / 3G / HSPA network. I would have thought Wifi would take more power, but that seems not to be so. I DID have "Network Mode" set to "WCDMA only" (in Mobile Network Settings) because I heard it might save battery not having to switch back and forth from EDGE to 3G, but I guess that didn't help...I've since switched it back, but need a lot of charging before I can test again.
Does anyone else notice that when they're on 3G/H the battery drops MUCH quicker than if you were connected to Wifi instead? This is just my last hurdle towards a PERFECT ROM!
Thanks in advance all!
Click to expand...
Click to collapse
From what I understand you need to update RIL settings in the ROM and then flash the modified ROM. I just edited the /system/build.prop file in the Leedriod zip file and saved (didn't resign or anything). Flashed the ROM through ROM Manager recovery (I also tried flashing it through the normal recovery but it failed on the "verifying image" stage - I guess because I didn't resign the archive).
As far as the options themselves - only the last two should be carrier specific. I haven't researched anything about them, so I have absolutely no idea what they actually do. "lenik" just copied them from an official Softbank ROM.
God, i just checked JuicePlotter and i dropped 1% for 1h10m (everything off except the radio + setCPU to ~400Mhz when screen off). This is just crazy ... awesome ))))
Is the setting rom specific, or will it work om opendesire?
Sent from my HTC Desire using XDA App
slyn4ice said:
Ok, I have awesome news! Thanks to user "lenik" on modaco forums I got some extra RIL settings (radio settings) he found for Softbank (my cellphone company here in Japan). Here are the settings:
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.fast.dormancy.timeout=3
ro.ril.enable.sbm.feature=1
He said the first two should be found on most ROMs, while the last two are probably carrier specific for SoftBank. Anyways, I just downloaded the latest LeeDroid ROM, modified /system/build.prop file (none of the above settings were in there) to include the above settings
Click to expand...
Click to collapse
LeeDroid ROM (LeeDrOiD_V2.1_A2SD+_.zip) build.prop includes:
ro.ril.enable.a52=0
ro.ril.enable.a53=1
but no:
ro.ril.fast.dormancy.timeout=3
ro.ril.enable.sbm.feature=1
Just checked.
So I've had this problem for awhile now with the wifi disconnecting itself during standby. The other day I decided to start fresh and went did a complete wipe and reflashed CM (10.1 RC).
The problem did not present itself during the 1st or 2nd day, however yesterday I noticed the wifi signal bar went grey for a second and reconnected. So I checked my radio version and noticed it was a few months behind, downloaded the latest and flashed it. Problem didn't show up until the next day where the wifi signal briefly turned grey and reconnected.
Wifi settings are set to always stay on when screen is off and I've tried almost every combo of settings in the wifi menu to stop it. This is fairly annoying since when I have wifi turned on I do not get texts since I use GV. Yes, I can turn off wifi and use my phone's internet, but I have bad signal here and the speeds are extremely slow.
I'm not sure what the problem could be, I always thought it was a bad flash the first time I did it and it was a bug. I thought wiping everything and flashing an RC would fix the problems.
Any thoughts on what could be causing it? I'm on stock CM with no custom kernels.
Hey guys I have searched and searched for a remedy for my problem, first off here is what I am running on my i9250:
ROM: Beanstalk 1.190
Kernel: KUBO-AK r46
Baseband: I9250UGLL1
Now the problem is this, all data (wifi and cell data) randomly disconnects when my battery is anywhere lower than 50% and gets increasingly annoying the lower it gets. I do not have any powersaving features enabled and yes I have changed the advanced settings in Wifi (Keep wifi on during sleep: checked to Always, Avoid poor connections: Unchecked, wifi freq band: 2.4ghz only, wifi optimization: unchecked; i guess that is a powersaving feature as well)
Still the problem persists. The other problem is, it happens to my cell data as well, when I wake the phone up (when it is under 50% or so) I see that only then the cell data starts to reconnect, and then I get all my whatsapp messages and emails all at once. (same goes with the wifi) Keep in mind though, when I have the phone plugged in and charging the wfi or cell data are active when the screen is switched off. The problem only occurs when the battery is below 50%.
Is there anything I can do about this, it gets really annoying because I have to wake the phone up and keep the screen on, in order to get messages. I know there is a widget that keeps the wifi active regardless of the battery level, but what about the phone data when I am out and about. I need to stay connected especially with emails and whatsapp because that is how clients stay in contact with me and it sucks when they send messages and I get nothing and they have to wait for me to check or wake up my phone for the data connection to re-establish whether it be on wifi or data.
Anyone knows how to fix this problem?
No one?
Have you tried changing your kernel? Sometime kernels can have weird affects on your device.
İ think this is one of kernel problems. Battery section is controlling by kernel. Find a kernel and use smartassv2 with sio.
Yes, I swapped around a few kernels and same effect. I really am at a loss.
amd-dude said:
Yes, I swapped around a few kernels and same effect. I really am at a loss.
Click to expand...
Click to collapse
it happens to me as well, not sure about the 50%, but when I am at home with 3G and wifi on very often if i turn on the phone the signal bars are grey and not blue and it seems that connectionwas lost during sleep and is being turned on again
btw, I am on stock 4.2.2
Try to format /system. And reflash. İf its not work, flash stock rom and flash custom rom. İm not sure if it will work.
Believe me, I have tried every wipe and every rom/kernel combo that is humanly possible
Then problem is hardware thats what I thought. Unfortunately. Technical support helps.
Hi,
Have you guys noticed our phones tend to drain battery much much faster on 3G than WiFi? I have yet to measure the drains accurately yet but I think the difference is huge. I can drain the entire battery in 2-3 hours with data on and active data transfer.
For example, stream some music on TuneIn on wifi and then on data (3G/H+). On data, the phone gets really hot and sometimes even with an AC charger plugged in the battery can barely hold charge (with screen also on). On Wi-Fi the phone stays cool and battery consumption seems to be much less.
I feel like it's ok for data to use a bit more power but I feel like this much of a difference is not normal. I have WCDMA preferred in mobile options, and it is displaying H+ in the status bar. I am assuming it isn't using LTE or looking for an LTE signal... How can I make sure of this? Is the LTE a different radio/chip that can be turned off separately?
I'm on CM10.1.2 with Wind Kernel 2.5.
what do u think requires more power receiving a signal from 30 meters away or a cell phone tower
having said that if your rom is pulling more than usual from data connection you can try switching to cdma only mode, also i think the stronger signal you are getting the less power it uses but im not sure on that, i think if u are in a basement or something it will pull more power.
or try switching roms
it is not the "phone" unless your phone is defective
try a differant rom if that doesn't work try a differant baseband if that doesn't work phone is probly defective or partially defective
first thing is try a stock based rom
btw i think the only time wifi will take more power than 3g/4g data is if you are sending huge amounts of data over it or have it on constantly scanning for networks, or have a rom that makes wifi stay on fullspeed while sleeping
KronicSkillz said:
what do u think requires more power receiving a signal from 30 meters away or a cell phone tower
having said that if your rom is pulling more than usual from data connection you can try switching to cdma only mode, also i think the stronger signal you are getting the less power it uses but im not sure on that, i think if u are in a basement or something it will pull more power.
or try switching roms
it is not the "phone" unless your phone is defective
try a differant rom if that doesn't work try a differant baseband if that doesn't work phone is probly defective or partially defective
first thing is try a stock based rom
btw i think the only time wifi will take more power than 3g/4g data is if you are sending huge amounts of data over it or have it on constantly scanning for networks, or have a rom that makes wifi stay on fullspeed while sleeping
Click to expand...
Click to collapse
I'm just trying to gauge if people are seeing the same thing as I am. I haven't switched basebands in a while. Any further informative comments are welcome.
Flyview said:
I'm just trying to gauge if people are seeing the same thing as I am. I haven't switched basebands in a while. Any further informative comments are welcome.
Click to expand...
Click to collapse
i can guarentee you thats not normal
what have u tried? have u even tried reflashing cm 10.1.2?
KronicSkillz said:
i can guarentee you thats not normal
what have u tried? have u even tried reflashing cm 10.1.2?
Click to expand...
Click to collapse
No I haven't, I kind of just assumed it had to be normal. The phone gets hot just like when you're talking on the phone for a while so I thought it made sense.
I have some preliminary numbers (didn't let the test run long). If you want to replicate this, get Android System Tuner, and set up a widget to show "Average mA since last measure". Turn brightness to minimum and set the display to not turn off, start streaming TuneIn radio, unplug the phone (to reset "last measure), and let the battery go down at least 5%.
-360mA - wifi on streaming music, screen low brightness (20%/hour)
-760mA - 3g on streaming music, screen low brightness (note that's 41.5%/hour!)
-400mA - 3g on streaming music, screen off (22%/hour)
These preliminary numbers would suggest WiFi uses almost nothing, since the screen seems to be about 360mA, whereas the difference between WiFi and data is 400mA!
Flyview said:
No I haven't, I kind of just assumed it had to be normal. The phone gets hot just like when you're talking on the phone for a while so I thought it made sense.
I have some preliminary numbers (didn't let the test run long). If you want to replicate this, get Android System Tuner, and set up a widget to show "Average mA since last measure". Turn brightness to minimum and set the display to not turn off, start streaming TuneIn radio, unplug the phone (to reset "last measure), and let the battery go down at least 5%.
-360mA - wifi on streaming music, screen low brightness (20%/hour)
-760mA - 3g on streaming music, screen low brightness (note that's 41.5%/hour!)
-400mA - 3g on streaming music, screen off (22%/hour)
These preliminary numbers would suggest WiFi uses almost nothing, since the screen seems to be about 360mA, whereas the difference between WiFi and data is 400mA!
Click to expand...
Click to collapse
if it was me before i bothered with any of this i would have redownloaded and wipe/reflash rom, i just had my phone streaming music on 3g and it didn't even get warm
i don't mind helping you but please rule out the easy obvious steps first
KronicSkillz said:
if it was me before i bothered with any of this i would have redownloaded and wipe/reflash rom, i just had my phone streaming music on 3g and it didn't even get warm
i don't mind helping you but please rule out the easy obvious steps first
Click to expand...
Click to collapse
I will try that tonight. I wanted a baseline too...
Could you please check what baseband you're running (I'm on V20e)? Does flashing CM10.1.2 change the baseband?
Flyview said:
I will try that tonight. I wanted a baseline too...
Could you please check what baseband you're running (I'm on V20e)? Does flashing CM10.1.2 change the baseband?
Click to expand...
Click to collapse
ive never had to flash my own baseband everywhere i read people say only do it if you have issues and ive never had issues, the rom/kernel i'm using is in my sig
there is a baseband archive in the developement section if it comes down to trying differant basebands although i'm not the person to talk to about that as i've never done it, i'm sure if you end up doing that asking on that thread would be your best bet as you will probably get responses from people who have done it before.
here i'll even link it:
basebands
this is a last resort and be very careful when flashing these
KronicSkillz said:
if it was me before i bothered with any of this i would have redownloaded and wipe/reflash rom, i just had my phone streaming music on 3g and it didn't even get warm
i don't mind helping you but please rule out the easy obvious steps first
Click to expand...
Click to collapse
Yeah I would have to second that, those mA are way too high. I am @ < 100 mA on H+ streaming off slacker now that is with stock, but when I was on cm10.1 I would have to say it was about the same. The ONLY time my phone gets warm is on GPS & charging, and my phone is over clocked to 1728 all the time.
Sent from my LG-P930 using xda app-developers app
KronicSkillz said:
ive never had to flash my own baseband everywhere i read people say only do it if you have issues and ive never had issues, the rom/kernel i'm using is in my sig
there is a baseband archive in the developement section if it comes down to trying differant basebands although i'm not the person to talk to about that as i've never done it, i'm sure if you end up doing that asking on that thread would be your best bet as you will probably get responses from people who have done it before.
here i'll even link it:
basebands
this is a last resort and be very careful when flashing these
Click to expand...
Click to collapse
Thanks. I've changed basebands before with packages from that thread. That's why I'm asking if flashing CM will override those.
What basebands are you guys on?
Sent from my LG-P930 using Tapatalk 2
Flyview said:
Thanks. I've changed basebands before with packages from that thread. That's why I'm asking if flashing CM will override those.
What basebands are you guys on?
Sent from my LG-P930 using Tapatalk 2
Click to expand...
Click to collapse
i'm honestly not sure if rom flashing changes baseband my gut instinct would be sometimes yes sometimes no but i'm honestly not sure, i dont even look at baseband unless i'm having problems with my radio signal and i never have.
ur problem is probly caused by you changing yours.
my baseband is: apq8060/mdm9200
have u tried what i suggested and flash a stock based rom to see if that fixes the error, then if you want to go back to cm10.1 u should be able to as long as you dont mess with basebands again
it's possible this doesn't fix the error if the stock rom doesn't flash a baseband, i'm honestly not sure if it will but it might
be careful that you don't flash one that reflashes a locked bootloader, most of the stock based roms on the developement forums have it disabled
KronicSkillz said:
i'm honestly not sure if rom flashing changes baseband my gut instinct would be sometimes yes sometimes no but i'm honestly not sure, i dont even look at baseband unless i'm having problems with my radio signal and i never have.
ur problem is probly caused by you changing yours.
my baseband is: apq8060/mdm9200
have u tried what i suggested and flash a stock based rom to see if that fixes the error, then if you want to go back to cm10.1 u should be able to as long as you dont mess with basebands again
it's possible this doesn't fix the error if the stock rom doesn't flash a baseband, i'm honestly not sure if it will but it might
be careful that you don't flash one that reflashes a locked bootloader, most of the stock based roms on the developement forums have it disabled
Click to expand...
Click to collapse
Thanks, that's what I'll be trying today. I was on V20e (newest Bell one from that thread). Yesterday I tried V20c, V10j. All are pretty much the same in terms of power usage as I tested them yesterday. I will try a stock-ish ICS today and test there.
BTW, I tried the streaming test on a Nexus 4.
-550mA screen on lowest brightness streaming 3G (compared to -760mA for mine)
-360mA screen off streaming 3G (compared to -500mA for mine)
So the differences aren't THAT drastic, but still.
So here's some updates:
I flashed V20f mod V2 by HoNo (a stripped down and CWM flashable V20f stock image from Bell).
At first, I thought everything was fixed, as I was seeing battery use at about 500mA with screen on lowest brightness, streaming over 3G. However, I think this was due to the battery being low and the battery % dropping slower when it's under 15% (Android Tuner free uses battery % and battery capacity to estimate current draw).
I charged the phone overnight, then I flashed my CWM backup of CM10.1.2. The good thing is it kept the V20f baseband (and firmware) from flashing the V20f rom. That confirms that CM10.1.2 and CWM backups don't save/flash baseband.img and firmware.img. However, again, I was seeing 700+mA draw. There might be better idle usage with the new baseband, but it might be placebo.
I went back to a CWM restore of the V20f rom and tested again on the ICS-based stock-ish rom. Battery consumption is still high (700+mA streaming on data and screen on lowest brightness).
Could one of you guys please try running the same test I am? Here's how:
0) Ensure your battery is in the range of 50-90%
1) Download Android Tuner Free (AT)
2) Download TuneIn
3) Add a AT widget (1x1 text option) to a homescreen
4) Tap the widget, go to settings, widgets, widget content, central value, choose "avg mA since last measure"
5) Go back to AT settings, battery, calibration, battery capacity, enter 1830.
6) Start to stream music from a radiostation on TuneIn
7) Set screen timeout to 5 or 10min
8) Set brightness to minimum
9) Plug phone in
10) Unplug phone (this resets the "avg mA since last measure")
11) Watch the central value as your battery drops for 10-20minutes. Since drain is an estimate based on % dropping it will jump around a bit but level off the more time you let it run.
12) Don't do other stuff on the phone so you aren't using the CPU more than for this test
I updated to mm a few days ago (flashed tar, then twrp, then su), and ever since, I've been having radio issues. Crackling on bt headsets, low quality voice calls (where it's difficult to make out what's being said), lte won't pick up right away - just stays on 3g in strong lte areas, and wifi disconnects whenever phone is sleeping.
Wifi settings have already been changed to stay awake while sleeping, and smart network switch and scanning are both off. I've also updated prl and profile, and reset radios.
It might also be worth noting that battery has seen no improvement, and anecdotally may even be worse - lose about 8%/hour at night if not plugged in. Doze doesn't seem to working for me I guess.
Anything else I can try before a full reset?
Also, should I repost this in the general s6 help forums for more visibility? Not sure what the rules are about that...
I am also having major issues on bluetooth headsets since upgrading. Podcasts and such are skipping all over the place and going in and out. Does not happen on wired headset/speaker. This did not happen on 5.1.1