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?
Related
Alright everyone,
Some details about my phone before we begin-
I am a moderate user. I play some games, check emails, text and that's about it.
My phone is NOT rooted and obviously I am not running a custom rom, or a alternate launcher, and I haven't really modified many if at all any settings.
So, that being said I am experience some sever kernel wake lock issues form bam_dmux_wakelock for the past week or so. As you see in my picture, 6 out of my 7 hours of up time (off charger) has been kept from deep sleep, therefore destroying my battery time.
Today I have maybe 30-40 minutes total of screen on time, but not nearly the 6 hours of non deep sleep time.
I've turned off "okay google" detection, disabled wifi when screen is off, restricted background data for youtube, disabled google + (I don't use social media) and my brightness is on auto mode, typically around 35% when the screen is on.
If google can see this I would like to offer them a huge F you for changing the permission architecture so that gplay apps cant detected whats causing the wake-lock without root. They are pretty much forcing us to root our phones to access features locked meanwhile continuing to call android "Open Source"
Can anyone give me a recommendation on what are my options? Or should I really just root my phone, which I don't want to do (I have in the past but I haven't needed too with the G3 since it has everything I want without root)
I don't think it's Google's fault if LG makes a sucks kernel. Anyway, bam_dmux seems to be related to radios. Could it be that during those wake locks you were in an area where there is weak signal? Are you still experiencing this error after a reboot of the phone?
keithleyson said:
I don't think it's Google's fault if LG makes a sucks kernel. Anyway, bam_dmux seems to be related to radios. Could it be that during those wake locks you were in an area where there is weak signal? Are you still experiencing this error after a reboot of the phone?
Click to expand...
Click to collapse
I've reset the phone multiple times, and have also cleared the cache from the bootloader as well. I don't have a weak signal in my area; also the radio interface is a separate wake lock code from bam_dmux. From what I read bam_dmux has to do with google background services.
Bump
JetForceF22 said:
I've reset the phone multiple times, and have also cleared the cache from the bootloader as well. I don't have a weak signal in my area; also the radio interface is a separate wake lock code from bam_dmux. From what I read bam_dmux has to do with google background services.
Click to expand...
Click to collapse
Google location service may be running in the background to much too long.
gee2012 said:
Google location service may be running in the background to much too long.
Click to expand...
Click to collapse
I don't see a google location service only the Verizon Location Agent; there are two other services called "LocationServices" under All in my application manager, and they are both listed at being 0.00 bytes in size (?) I force stopped those anyways along with the verizon location agent which restarted anyways. I also have location completely off in my quick menu from the pull down bar, I only turn it on when I'm using GPS.
Usually I can resolve my own issues, but this time I need some help.
My 360 disconnects from my phone often (about 20 times a day). Sometimes it will reconnect immediately, sometimes I have to toggle bluetooth, sometimes I have to reboot both phone and watch.
On one occasion, my phone forgot the watch all by itself, like it wasn't even there. I had to factory reset the watch in order to reconnect.
I've tested thoroughly and can confirm this is only happening while my phone is connected to my home wifi. While on data or other wifi networks (both 2.4 and 5 ghz bands), the issue is non-existent.
My phone (Moto X 2014) is running 5.1 stock and rooted. I greenify Facebook only. I use Tasker but do not have any wifi-specific profiles set.
The watch is running 5.1.1 and I'm using the latest Android Wear. I tried rolling back a few versions but no change.
My router is running the latest firmware (Verizon router provided with Fios), and I've tried broadcasting in different channels.
Kind of at my wits end, here. I would appreciate any suggestions. Thanks!
Well, it happened again last night - out of nowhere I received a pairing request from my watch. The phone had just forgotten it, and I wasn't able to re-pair without performing a reset of the watch.
Steps taken since then:
1. Set wifi to channel 1
2. Set wifi to 802.11/n
3. Uninstalled Wear Mini Launcher (provides notification when phone and watch disconnect... I suspect it might be causing issues)
I've been at work and connected to wifi for 2 hours, no problems. At home, I'd have disconnected twice by now.
Argh!
Hi
Did you sort this issue?
I've noticed it on my Moto 360/ Moto X 2014 as well.
When I connect both wifi and bluetooth and then disable Bluetooth my phone complains that Android Wear has disconnected and to tap the alert to reconnect, which I do but I'm not sure if it does anything.
Then I've noticed my watch will drop wifi connection every now and then but after a bit of messing around in the settings I found an option under Wifi settings/ Advanced called Power Save which I've adjusted to the longest time possible (180 minutes), it was previously set to 30 minutes and I'm guessing the watch was disconnecting from my Wifi network when it hit this.
I've only just done this though so I don't know if it'll solve the frequent disconnect issues, however i'll still have to reconnect the Watch after 180 minutes.
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
Hi All,
I've had my OP3 for a little over six months now, and while my experience has been fairly positive, there have been a couple issues that I find myself getting frustrated over. I am looking to see if anyone has had any fixes for any of these (more common) problems, whether it be settings, tweaks, or other ROM's.
1. Location - The location accuracy is really bad. I live in NYC and drive for two hours a day, keep Waze open to avoid traffic jams, spend a lot of time in the city during the weekend, and it is very unreliable. If walking, it can be off by an entire block, going in the wrong direction; when driving, it's intermittent and can fail to get a location for periods at a time. Might be a hardware limitation?
2. Doze - Notifications from apps get delayed until wake, sometimes dozens at a time. I've disabled Doze, Aggressive Doze in Greenify, and battery optimization on individual apps, have tried stock and Freedom OS to no avail. Maybe I'm doing something wrong?
3. SMS - A lot of SMS messages sent to me are dropped and never received, and a lot of MMS I try to send fail to send. I have used stock messages and bought Textra, and have no idea why this happens. Been on AT&T for a decade now so it's not a carrier thing. Have ended up using other modes of messaging as SMS is unreliable.
4. Mic - Poor background noise reduction in telephone calls. Especially when driving with the windows up, people on the other side of the call hear a lot of background noise and echoes from their own voice. This makes sense as their voice is on the car speaker, but even at lowest volume, it is worse than any phone I've had previously. Might be limited by the hardware, but because echo-reduction can be a software-fix I figured I'd mention it anyway.
5. Vibration - it's weak. If I don't have audio on, I probably wont notice even if it's right in front of me. I use the Xposed tweak to not much improvement. Not as important as the others but it is what it is.
The phone otherwise is awesome - very snappy, great battery life, super fast charging, solid screen, but the things above make me hesitant to recommend. Any help at all (even your ROM/Kernel if you don't have some of these problems) would be appreciated.
Dyphen said:
Hi All,
I've had my OP3 for a little over six months now, and while my experience has been fairly positive, there have been a couple issues that I find myself getting frustrated over. I am looking to see if anyone has had any fixes for any of these (more common) problems, whether it be settings, tweaks, or other ROM's.
1. Location - The location accuracy is really bad. I live in NYC and drive for two hours a day, keep Waze open to avoid traffic jams, spend a lot of time in the city during the weekend, and it is very unreliable. If walking, it can be off by an entire block, going in the wrong direction; when driving, it's intermittent and can fail to get a location for periods at a time. Might be a hardware limitation?
2. Doze - Notifications from apps get delayed until wake, sometimes dozens at a time. I've disabled Doze, Aggressive Doze in Greenify, and battery optimization on individual apps, have tried stock and Freedom OS to no avail. Maybe I'm doing something wrong?
3. SMS - A lot of SMS messages sent to me are dropped and never received, and a lot of MMS I try to send fail to send. I have used stock messages and bought Textra, and have no idea why this happens. Been on AT&T for a decade now so it's not a carrier thing. Have ended up using other modes of messaging as SMS is unreliable.
4. Mic - Poor background noise reduction in telephone calls. Especially when driving with the windows up, people on the other side of the call hear a lot of background noise and echoes from their own voice. This makes sense as their voice is on the car speaker, but even at lowest volume, it is worse than any phone I've had previously. Might be limited by the hardware, but because echo-reduction can be a software-fix I figured I'd mention it anyway.
5. Vibration - it's weak. If I don't have audio on, I probably wont notice even if it's right in front of me. I use the Xposed tweak to not much improvement. Not as important as the others but it is what it is.
The phone otherwise is awesome - very snappy, great battery life, super fast charging, solid screen, but the things above make me hesitant to recommend. Any help at all (even your ROM/Kernel if you don't have some of these problems) would be appreciated.
Click to expand...
Click to collapse
Oxygen os?
Manav__25 said:
Oxygen os?
Click to expand...
Click to collapse
Yeah, and then FreedomOS CE to see if it would make any difference on these. So far nothing - stayed on MM though, if N helps with any of these maybe I update.
Dyphen said:
Yeah, and then FreedomOS CE to see if it would make any difference on these. So far nothing - stayed on MM though, if N helps with any of these maybe I update.
Click to expand...
Click to collapse
Maybe you should update to latest oxygen os
I recently bought a Mate 20 (not Pro, Lite, or X), mainly because of the dual GPS feature. But now I have noticed, and reproduced, that when tracking my activity, the phone will the GPS signal when I don't move for several minutes (in the first instance it was about 5 minutes, the second time 26 minutes before the signal was lost).
The GPS signal will not come back after this, even when moving again, except for very short timespans (5-10 seconds, twice over several hours).
This behavior does not occur if not moving at all: You have to move, then stop moving for several minutes, and then GPS signal is lost.
The GPS signal was not blocked by anything, I was on the outside. I also did disable all power-saving features, but the problem does not seem to be connected to any particular tracking app: I was running 4 apps simultaneously, and neither was able to record a position after not moving).
So it seems like the firmware turns off GPS reception once it determines that the phone isn't moving anymore - without any notification, and while GPS is still turned on in the settings (and it stays on in the settings even though the firmware blocks actual GPS reception.
Is there any way to stop this behavior, so that GPS will always try to receive a signal even if I don't move for hours?
*Please do not post anything like "did you do all updates", "do a factory reset" and other general tips like these.