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
Related
I sometimes have issues with receiving data signals on my G2. Sometimes my phone won't ring until the last few seconds resulting in me missing a call, or wont ring at all. I use google voice which requires a data connection in adition to cell tower connection. I also have to reset my phone maybe once every week or so because my data connection won't work at all. This usually happens when I disable wifi and then enable tethering. Would flashing a radio help? I'm using CM7 Nightlies.
legato89 said:
I sometimes have issues with receiving data signals on my G2. Sometimes my phone won't ring until the last few seconds resulting in me missing a call, or wont ring at all. I use google voice which requires a data connection in adition to cell tower connection. I also have to reset my phone maybe once every week or so because my data connection won't work at all. This usually happens when I disable wifi and then enable tethering. Would flashing a radio help? I'm using CM7 Nightlies.
Click to expand...
Click to collapse
Flashing an updated radio could help. Just make sure you get the correct one and know how to flash it!
I'm on nightly 100 and have no issues. But I'm also on the latest radio as well. Just remember, nightlys are still considered experimental
I think i have the latest radio from reading the radio threads. 26.03.02.26., but even after flashing the latest Nightly the same issue occoured where I'll receive a call at the last ring and not have enough time to answer it. Also my battery life is pretty terrible. I left my phone on overnight starting at 100% and when I awoke it was down to 51, 1/3 cell standby, 1/3 phone idle, and 1/3 bluetooth (but my headset is off). I am thinking of flashing pershoots kernel and see how well it works.
legato89 said:
I think i have the latest radio from reading the radio threads. 26.03.02.26., but even after flashing the latest Nightly the same issue occoured where I'll receive a call at the last ring and not have enough time to answer it. Also my battery life is pretty terrible. I left my phone on overnight starting at 100% and when I awoke it was down to 51, 1/3 cell standby, 1/3 phone idle, and 1/3 bluetooth (but my headset is off). I am thinking of flashing pershoots kernel and see how well it works.
Click to expand...
Click to collapse
That's really odd. I have Radio 26.08.04.30 Which I believe is the latest. The kernel could have something to do with it as well. I'm running Pershoot's latest kernel found at Droid Basement. Let me know what happens after you flash the latest kernel and radio!
I bought myself Arc S, it came loaded with .62 firmware. On my initial run, battery ran for about a day, later on for two or maybe even three days. Then I started to work in another country. As far as I remember, battery life was the same, even though the network was not (where I work now is 2G only, in my home country 3G). Then one day messed around with a Xperia S apps, did a stupid mistake and started to get force closes with launcher. I had to repair software.
Since the software reinstallation, my battery life degraded to less than a day without even touching it. Therefore I installed Battery Monitor Widget, to see, what is going on. I noticed, that battery drainage is about 70-110 ma in average, as far as I know, it should be much lower (under 30ma?). I have to say, that I tested this with .62, .42 firmware and it's all the same. When I turn phone to airplane mode, energy consumption lowers to under 5ma - which is normal i guess.
It began to bug me even more, as we bought small alarm clock with radio. I noticed, that when this alarm clock is on, despite from 2 other phones our room, my Arc S is the only phone, which makes this kind of searching-for-signal or calling speaker interference (noise coming out of speaker). My phone does that all the time, even in idle mode. This can be also heard when we have our TV on on. So, if I don't want to hear that, I have to unplug the alarm clock or put my phone into airplane, which sucks.
I asked a guy next building, if he has the same problems with Arc S, and he says that his phone can live up to 5 days with one charge (is connected to the same network provider), so I guess it is not network related?
I wonder, is there a possibility, my phone's radio is broken somehow? Or it was faulty, and firmware reinstall somehow broke it to the end? So that is draining battery all the time - looking for signal? Any way to fix this? Flashing different base bands did not help, tried that already...anybody knows a fix for this, apart from returning it to my provider - since I'm 4 months away from my country
Anybody heard for any similar problem with Arc S?
Thanks in advance! (if needed, I can also post battery usage screenshot, but I think it's not much of a help)
lyteo said:
Then I started to work in another country. As far as I remember, battery life was the same, even though the network was not (where I work now is 2G only, in my home country 3G)
Click to expand...
Click to collapse
That seems like the issue here if I'm understanding you correctly. If you don't have 3G service where you currently are, and you did not turn off 3G, your phone will constantly try and find a 3G signal.
Airplane mode fixing the issue makes this seem even more likely. Try disabling 3G and see if it helps.
Problem is, that's what I did almost instantly when I came here, I set it to GSM only. One thing I noticed right now, when I check into About phone, under Mobile network type, my Arc S has: UNKNOWN, where my friends HTC says EDGE. Maybe here lies a problem? Why my phone can't detect network type?
Incredibly, I found the reason for my drainage and signal search. When I came into that country where I work now, my provider offered me to turn off data transfer (provider turns it off for me). Of course I did not want any unintended data transfer, so I turned it off by sending sms to service number. After I reinstalled software (that was my first reboot here), phone couldn't find network type for that reason, and was searching for it all the time. Yesterday I allowed data transfer by sms again, phone found EDGE network, can't hear any more noise on our alarm clock and battery drainage is about 4% per 8,5 hour. Excellent
I hope this helps anyone out there with drainage problems.
I think you can also turn off/disable data transfer/traffic with the Data traffic widget, if you want to avoid using data.
xperia arc s
hold up, i dont understand. so im pretty sure i have the same problem. get about 17 hours with berely using my phone on any rom/kernal/firmware. even with data turned off, betterbatterystats shows 'noor unknown signal' and 'no data conection'? i sued to able to get 3 or more days out of my phone??
I think there is an application, which might be keeping the phone alive.
dout it, still drains after a complete rom wipe
I've been having some ongoing issues with a replacement phone I received Monday, 10/2. Specifically with WiFi always being on, even when its not supposed to be. Attached are some screen shots that I hope, show what I'm talking about. I've tried various kernals, but the problem seems to remain. When I do have the Wifi enabled and connected to my Wireless, my signal is crap. I've been in the *#0011# menu and turned off WiFi Power Save mode(yes I know the screen shot shows its on). I do have a dual band wireless system and have tried disabling the 5ghz band, assigning a static IP, and have tested with other wifi systems. Only consistent is my phone.
I am on 4.3 MJB Bootloader, Modem, OS from upndwn4par. I have tried other variations of modems, OS's, and kernals. I'm thinking this phone is just fubar'd somehow (It is a refurb ) but wanted to get some other suggestions.
I also have very bad battery drain, which I didn't have in my original phone. Im hoping the battery drain is caused by whatever is keeping my WiFi on.
EDIT: After more searching I found in the WiFi settings menu to disable "Always Allow Scanning". Stopped the WiFi from being on. Still hasn't changed the severe battery drain or weak signal
There were lots of comments (and still are) about how wifi is a battery killer on android wear. I'm not seeing this to be the case at all, when it's working like it's supposed to.
Since 5.1.1 my battery use has been around 3% and hour with all features on. Turning off bluetooth on my phone, with a 2/3 wifi signal on the watch, I'm seeing 2.5 to 3%.
Quick drain happens when walking around the edge of bluetooth range, as the watch switches back and forth between bluetooth and wifi. It seems that as long as it's not finding bluetooth, battery use is normal at worst for me.
I know that the moto 360 will switch to a state of only checking for updates occasionally to save battery, but I don't see this happening. Notifications are coming to the phone, and shortly afterward on the watch. I have not seen a time when a notification was delayed more than a few seconds.
The downside to wifi-only use: some apps that communicate with a phone app don't work. My watchmaker face doesn't update the phone battery level. Google voice commands fail too often, maybe half of the time.
I think google should change the frequency of attempting to reestablish bluetooth connection while on wifi.
Has anyone else tried this? Either turn off your phone's bluetooth, or make sure it is well out of range.
I'll give it a go tomorrow at the office and report back.
Sent from my Xperia Z3
Thanks to a heads up by DarkRazorZ, I learned wifi can be turned on in airplane mode. Will be looking to see if this makes any more difference.
Watch maker has been my biggest battery drain. It also makes the drop down menu laggy and impossible to use.
Yeah, I had that problem with watchmaker. I use intelligent and it seems to work well. Other people report facet works too.
I concur. Wi-Fi uses a lot less battery than Bluetooth, with an acceptable lag - 1-2 seconds on notifications. Bluetooth seems like a big battery drain on the phone and on the watch.
Sent from my Xperia Z3+
I checked this thread first, but it's old and was dominated by WiFi discussion.
I've had this problem in various forms going back to at least OOS 3.1.3 (I think).
I'm in the US on AT&T. I'm currently on OOS 3.1.6 (better battery life for me), stock kernel, rooted, XPosed: (Flat Style Bar Indicators, Flat Style Colored Bars, Gravity Box, Settings Editor) Greenify. I'm not using any over-aggressive greenify options.
I have frozen several system apps aligned to Freedom OS.
NFC is turned off/frozen.
When I stream music via WiFi through BT, to a speaker or headphones, I have no issues at all.
When I stream music via Cell Data (AT&T LTE) to my 2013 Toyota truck, I get what seems like random "skips" in the BT stream. This happens with Spotify, I Heart Radio, and GPS Nav apps. I don't know for certain, but sometimes it's as if the skip happens when I change cell towers. It will also happen if the screen is dark and I double-tap to wake.
Once it starts, it doesn't stop, and "skips" about every 8-10 seconds unless I change the input to something else. Going back to BT, sometimes it's fixed until the next cell tower switch. Sometimes killing the app and wiping it from memory fixes it. Sometimes changing the APN fixes it. Sometimes clearing Dalvik/Cache fixes it for a day or so.
I've erased the phone from my truck several times and re-paired it.
I've changed the OS version multiple times (dirty flash).
I'd prefer to stick with OOS but, I can't get this sorted out.
Two questions:
1) Is there any BT setting or Cell setting I can manually adjust to counteract this effect?
2) If not, I know there are ROMs with updated modems/radios. Would that help, and if so, which ones should I try?