I flashed CM 10.2 (the stable build) a few days ago and I've noticed that the cell signal has been much worse than before when I was on stock. Im getting 1 bar in areas where I used to get to get 3 or more. I've read in other threads that google changed the bar measurement with 4.3, but I'm also experiencing severe battery drain with 20% of my cell idle time being "no signal". I didn't have this problem before 10.2. Has anyone else experienced this and/or found a solution?
Related
Here is my situation:
I flashed CyberGR v.11 with air kernel (weekly 05/08/12) yesterday.
I woke up today with a dead phone. I realized it was out of battery (I went to bed with around 30%).
Throughout the day today, i noticed whenever I wake up the phone, the signal would go from no bars to full bars. I went to settings>battery and checked the "History details" and saw that during sleep, the mobile network signal colour is either red or yellow.
So that explained why i woke up with a dead phone. Searching for signal KILLS battery.
Today CyberGR v.12 came out, so i decided to flash that rom (with a clean install from CyberGR's instructions) but this time with morfic's t12 56hz kernel. I thought maybe it was because i had deep idle on when i had air kernel, but instead of testing with deep idle off, i decided to update to v.12 since it came out and tried a kernel without deep idle. Nothing changed.
I'm on ondemand, and have tried up to min 400mhz to see if that it'll keep my phone from losing signal when it sleeps, but it didn't help.
I also tried changing my radio from KI1 (which, from user experience from this thread says is most ideal for my network WIND mobile) to KF1, but that didn't help either.
I have the i9020T from WIND that i got in january. I did not have problems when i was using BM's 3.0 ICS and gummy 1.0.4 (both with air kernel and DI on), but i did have initial problems with those two roms when i first flashed them. I would randomly lose signal throughout the day, but after a day or so it wouldn't lose connection.
Also, i've been getting a lot of radio_dump_[date and time].bin files in my sdcard since this issue surfaced.
I am fairly new to android (this is my first device) and if anyone could help me fix this issue, it would be greatly appreciated.
Thanks for reading my long post!
Intermittent faults are really difficult to diagnose. Do you get the exact same issues with all radios?
I've tested the KI1, KD1, KF1, KB3.
It actually got worse with the other radios. Before, my phone used to reconnected with my network when i woke it from sleep automatically, but now it doesn't do that and it can't even search for available networks.
Also tested with matrix 19.5 and the new stable air kernel, but to no avail...
I have an issue I’m trying to resolve on my Roger’s SII.
I’m running aokp milestone 6 with instigatorx’s kernel v4.0b and everything was running nice and smooth without issues. But I wasn’t getting the best signal so I updated my radio.
I updated my radio to the Roger’s stock ICS radio from the Embryo 4.1 post (http://forum.xda-developers.com/showthread.php?t=1754473) and have noticed a huge decrease in battery life (basically watch the battery percentage tick down). I also noticed my phone is now getting really warm to the touch.
I flashed the Roger’s stock ICS radio from Seanzscreams and same issue.
I flashed back to the GB radio in the Embryo post and same issue.
So I’m not sure what I screwed up but it’s annoying when you’re phone won’t last a day or even ½ day.
Anyone have any suggestions?
I’ll keep searching in the meantime for a solution….
Thanks.
**EDIT**
Turning on Airplane Mode stops the phone from discharging rapidly and my battery stats indicate that Phone is consuming the most power. Not sure if that helps.
Anyone else noticed this? In areas of med to low LTE signal (-109 dBm), there are times when something locks up inside the radio and Signal Strength under Status will never change again no matter where I move the phone. During this funky mode, the battery is dropping rapidly during idle... Maybe 10% per hour. Something is wrong. During this same time android battery history shows yellow medium signal and voice calls work fine. There is also no runaway process cpu ussage or awake time. The only thing wrong and drawing too much juice is radio. If I toggle airplane mode or toggle wifi off/on the problem is solved for a while. I have VRALF2 firmware.
same problems here
Scrappy1 said:
Anyone else noticed this? In areas of med to low LTE signal (-109 dBm), there are times when something locks up inside the radio and Signal Strength under Status will never change again no matter where I move the phone. During this funky mode, the battery is dropping rapidly during idle... Maybe 10% per hour. Something is wrong. During this same time android battery history shows yellow medium signal and voice calls work fine. There is also no runaway process cpu ussage or awake time. The only thing wrong and drawing too much juice is radio. If I toggle airplane mode or toggle wifi off/on the problem is solved for a while. I have VRALF2 firmware.
Click to expand...
Click to collapse
I have the same problem. Have went through many sim cards and factory resets. After 5 phone I finally have one that holds the signal a little better and does not go into this "funky mode". With the previous 4 (white 32gig) verizon phone I would burn through a battery in 6 hours at work. It would start with a drop in signal strengh at around -93 or so. Nothing would fix it. I finally got a blue 32gig and it seems to hold the signal to around -99. I don't know if I got a better batch of phones. But it seems to help me get through a day at work.
Scrappy1 said:
Anyone else noticed this? In areas of med to low LTE signal (-109 dBm), there are times when something locks up inside the radio and Signal Strength under Status will never change again no matter where I move the phone. During this funky mode, the battery is dropping rapidly during idle... Maybe 10% per hour. Something is wrong. During this same time android battery history shows yellow medium signal and voice calls work fine. There is also no runaway process cpu ussage or awake time. The only thing wrong and drawing too much juice is radio. If I toggle airplane mode or toggle wifi off/on the problem is solved for a while. I have VRALF2 firmware.
Click to expand...
Click to collapse
That's not normal. Where I work I get 3g primarily but also 4g in the front of the building.....in the far back I get 1x. I have had my phone totally drop data for a while (like the radio sleeps or something) but never had the radio stick between 4g and 3g. I also live right on the edge of a 4g/3g line and my dbm right now is 111 on 4g LTE......If this was normal I would have had the situation your having since my signal is basically identical to yours. I would return it or at the very least contact Samsung. I'm sure Samsung will tell you to send it in for repair.
I have very weak signal at my house also. S3 switches from LTE to 3G and 1X and sometimes loosing signal completely downstairs but upstairs usually I get solid LTE with around -99dBm and ~10Mbps transfers. During this network jumping my battery drains very fast also but I never had my radio constantly locked at one frequency or signal strength. And I can directly compare signal reception to my wife's Fascinate and S3 loses this competition badly. Fascinate never completely lost signal at our house and it rarely jumps to 1X.
I did a factory reset yesterday and so far so good... I''ll update as time goes on.
As far as signal strength goes in general,my wife's Droid Charge always pulls in a few more LTE dBm's than my GS3. Based on general public feedback, GS3 is below average on signal and radio issues. It's too bad because the rest of the phone is above average.
It's been 2 days after the factory reset and no problems with battery drain or radio lock up.
The only app that I could maybe try and blame is Elixir 2's create widget feature for signal strength. This always returned bogus values and may have embedded itself at an unholy level. Simply uninstalling elixir 2 didn't fix it.
If anyone still cares... I found my radio lockup and battery drain issues returned only after I reinstalled Better Battery Stats. I again removed it and will see if I stay good.
So My OPO Runs Lollipop for the last three months, and battery life was never great.
I've heard that kernels can fix it and give me 8-10 hours screen on time.
flashed franco, metallized, tyr, tgm and changed the profiles with kernel auditor but it just doesn't do anything except make the phone run slower.
does anyone have this issue too?
P.S
I'm currently running cm12.1 nightly and metallized Nev8 and struggle to get 4 hours SOT
Itay2108 said:
So My OPO Runs Lollipop for the last three months, and battery life was never great.
I've heard that kernels can fix it and give me 8-10 hours screen on time.
flashed franco, metallized, tyr, tgm and changed the profiles with kernel auditor but it just doesn't do anything except make the phone run slower.
does anyone have this issue too?
P.S
I'm currently running cm12.1 nightly and metallized Nev8 and struggle to get 4 hours SOT
Click to expand...
Click to collapse
Same here, exodus made it a little better. My average screen usage is 4hours then the battery is a nearly zero (having lg watch r always connected to the phone)
Tried BlissPop, CM unoffical by jgcap, cm12 nightly, all result in the same. I also switched from chrome to opera to reduce battery usage, it gives me ~30min more screen on time.
Since I'm playing Hearthstone the battery life is 19-20hours, because Hearthstone drains so much.
Hello,
I have a 2GB Mi4 (LTE edition).
I've found out that 3g data connection keeps the phone awake for about 33% of the time (checked in Wakelock Detector). As a result, the battery drains fast.
The issue disappears if I switch to 2g-only connection or to wifi. I don't have 4g available here, so I can't test that.
This happens on any MIUI-based Marshmallow rom, including Xiaomi.eu.
The wakelock isn't associated with any particular app or service in Wakelock Detector, so it took me a while to figure out that it was related to 3g. Of course I'm testing with a clean rom.
On the other hand, I've noticed that Kitkat-based MIUI doesn't have this problem.
This is 100% reproducible for me, but I haven't found anyone mentioning it in the forum.
Could you please confirm the issue?
Thanks.