I've seen other threads in passing mention issues with bluetooth but no detailed responses as to whether it's likely to be hardware issues common to Huawei, or something that has been fixed in later updates.
The symptoms: Not every time, but regularly enough to be annoying, bluetooth audio will revert to phone loud speaker, even with bluetooth shown as enabled and the device connected. correctly. This has happened with headphones and car receiver (both cheap and cheerful Chinese stuff). Often if I toggle bluetooth off and on again audio will switch to the headphones for a second or two, then back to speaker. If I go into bluetooth settings and disable media audio and then re-enable, it usually then works for the remaining time I have the bluetooth device connected.
When it's in this state, the play/pause button on the bluetooth device still works, showing that there is still a connection - so the issue seems to be audio routing.
Has anyone had this problem in the past and now found that it doesn't happen after an update? (Change log for one of the newer updates not yet available on my model C782 ,mention bluetooth).
Or has anyone who switched to a treble ROM found that the problem is gone (suggesting software) or remains (suggesting hardware or chipset issues).
Considering a rebrand to C432 to get the more recent updates, but would be good to know if that's likely to solve the bluetooth issues.
Thanks
Do you have development settings enabled? Found out that having it disabled solved my problems with fallback to phone speaker. If i enable it, the problem comes back. Even with not changing any parameters in the settings. I'm now on c432 137 and the problem has been there from the release...
L.R.G. said:
Do you have development settings enabled? Found out that having it disabled solved my problems with fallback to phone speaker. If i enable it, the problem comes back. Even with not changing any parameters in the settings. I'm now on c432 137 and the problem has been there from the release...
Click to expand...
Click to collapse
Actually yes I do! (for adb access while trying to get HiSuite to work). I'll try turning it off and see if that fixes it - thanks
gonzo99 said:
Actually yes I do! (for adb access while trying to get HiSuite to work). I'll try turning it off and see if that fixes it - thanks
Click to expand...
Click to collapse
Any update on this - did disabling developer settings help?
I have same issue too. Does it help to disable the mode?
bkakus said:
I have same issue too. Does it help to disable the mode?
Click to expand...
Click to collapse
It did seem to help but hasn't solved it entirely. Neither have the two major updates I've had in 6 months....
It happens intermittently so I've learnt to live with it, but it's still annoying when it happens.
I think that is more a PIE problem.
I was using the Essential PH-1 for the past 3 months (reverted back to my Mate 9 on Oreo) and my Essential would once in a while
do that. I typically wear a BT headset, plantronics 5200 series, and once in a while, I would hear the beep beep as it reverted back
to the phone, requiring me to press the speaker icon to put it back on the headset. It SHOWS the headset connected to BT, but would
just switch from the BT headset to the speaker.
I also wear a Samsung G3 Frontier watch, and once in a while, it would switch from the Essential, to the watch, requiring the same
process of pressing the on screen speaker to switch it back to the headset.
NEVER had that problem on my Mate9, running Oreo.
Hope that helps, that it might not be the phone, but the OS.
Not a Pie problem, because mine isn't on Pie yet.
I have had the exact same problem for a longer period of time. Huawei contacted me saying it was solved, but it wasn't. The latest contact with huawei official said that I should send my phone in for repair. Annoying when I know that several others have the same exact problem.
Maybe it's coincidence, but mine seems to disconnect at similar locations. Maybe that's just a function of me having a boring routine, but it happens almost like clockwork on my drive home from work.
I've seen in other threads that freezing the app (via root) Power Genius solves this problem.
Bobomo said:
Maybe it's coincidence, but mine seems to disconnect at similar locations. Maybe that's just a function of me having a boring routine, but it happens almost like clockwork on my drive home from work.
Click to expand...
Click to collapse
I've noticed the same thing. It seems to be more likely to disconnect at certain locations on my drive. I wonder if being near other bluetooth or wifi networks has anything to do with it.
This happens (I think) because EMUI kills off background processes needed for bluetooth music playback (in the name of battery optimization). It happens when your music player is in the background (or your screen is off), and the more apps/processes running, the more likely EMUI is to kill something off.
If rooted, use either Titanium Backup or Service Disabler to get rid of Power Genius, which is the app responsible for Huawei's battery optimization. There are zero negative consequences in my experience with the MediaPad M5.
If you aren't rooted, there's a way to uninstall system apps via ADB, but I don't think it works for this.
I've disabled Power Genius via adb and it has not helped.
yurkyurk said:
I've disabled Power Genius via adb and it has not helped.
Click to expand...
Click to collapse
Try rebooting, after disabling it.
But also, I haven't personally seen someone claim to successfully disable it via adb.
Related
I've been having an audio issue on this phone and it's getting quite irritating.
If I use the stock Music app or the Google Play Music app to listen to music and turn the screen off, eventually the audio gets cut out. The only way to fix it is by closing the music app entirely and reopening it. But once I turn the screen off, the issue comes back.
Someone on the OnePlus One forum had the same issue on their HAM2, but they said it went away. I've had my phone for almost month now and it's still here. I've tried the normal power saving mode, and both music apps don't show up in the protected apps list.
There's also a Bluetooth audio issue. Once connected to a Bluetooth device, the music skips around.
Anyone else have this/these issue(s)?
ScoobSTi said:
I've been having an audio issue on this phone and it's getting quite irritating.
If I use the stock Music app or the Google Play Music app to listen to music and turn the screen off, eventually the audio gets cut out. The only way to fix it is by closing the music app entirely and reopening it. But once I turn the screen off, the issue comes back.
Someone on the OnePlus One forum had the same issue on their HAM2, but they said it went away. I've had my phone for almost month now and it's still here. I've tried the normal power saving mode, and both music apps don't show up in the protected apps list.
There's also a Bluetooth audio issue. Once connected to a Bluetooth device, the music skips around.
Anyone else have this/these issue(s)?
Click to expand...
Click to collapse
I've ordered a HAM2 but don't have it yet, but this is really an Android issue (there's still a BT skipping issue in KK 4.4 when playing music from an SD card in devices with an SD card slot). Some users with different phones have reported success in stopping the skipping by going into BT settings and choosing "visability timeout" and moving that setting to "never timeout." Good luck.
mke1973 said:
I've ordered a HAM2 but don't have it yet, but this is really an Android issue (there's still a BT skipping issue in KK 4.4 when playing music from an SD card in devices with an SD card slot). Some users with different phones have reported success in stopping the skipping by going into BT settings and choosing "visability timeout" and moving that setting to "never timeout." Good luck.
Click to expand...
Click to collapse
Weird, my previous 3 year old phone with 4.4.4 didn't have this issue. All the music was on the SD card too.
I'll try the BT later and see if it still happens.
ScoobSTi said:
Weird, my previous 3 year old phone with 4.4.4 didn't have this issue. All the music was on the SD card too.
I'll try the BT later and see if it still happens.
Click to expand...
Click to collapse
In another forum, a person for whom the visibility input fix didn't work, who believed his issue was with another app running in background and using system resources posted that he used safe mode and lost the BT skipping issues (and confirmed his issue was app related). It's always a pain to try to determine if an app is causing issues if you've got a new device and installed a lot of apps at once. I've had to do that a couple of times and felt like pulling my hair out until I found the offending culprit.
mke1973 said:
In another forum, a person for whom the visibility input fix didn't work, who believed his issue was with another app running in background and using system resources posted that he used safe mode and lost the BT skipping issues (and confirmed his issue was app related). It's always a pain to try to determine if an app is causing issues if you've got a new device and installed a lot of apps at once. I've had to do that a couple of times and felt like pulling my hair out until I found the offending culprit.
Click to expand...
Click to collapse
I guess if finding out which app is the culprit becomes too difficult and a factory reset is needed, it won't be too bad as Google Play will automatically reinstall the apps.
However my priority is music from the SD card, and it'll be impossible to listen to anything if this doesn't get fixed.
YES I have this problem all the time and It's starting to make me mad
I had problems with audio both streaming through bluetooth and Chromecast. Bluetooth would stutter and skip frequently (rebooting fixed it temporarily), and music would just stop on the Chromecast at the end of the current song after turning my screen off (also fixed for a short while by rebooting). I returned the phone because of these issues. I'm hoping that 4.4 will fix these problems and I can buy another one.
Gir357 said:
YES I have this problem all the time and It's starting to make me mad
Click to expand...
Click to collapse
Someone on a different device and forum solved this by going to Settings > Apps > All > Google Play Music > Uninstall updates.
I did Force stop > clear cache > clear data > uninstall updates, and updated again through Play Store but the issue still exists. It's so frustrating. Can't listen to music on the train or in the car unless I leave the screen on, which is dumb.
ScoobSTi said:
Someone on a different device and forum solved this by going to Settings > Apps > All > Google Play Music > Uninstall updates.
I did Force stop > clear cache > clear data > uninstall updates, and updated again through Play Store but the issue still exists. It's so frustrating. Can't listen to music on the train or in the car unless I leave the screen on, which is dumb.
Click to expand...
Click to collapse
It hasn't really been acting up the last couple of days. However before that I couldn't listen for 2 minutes without it cutting out.
Oh well. Problem solved itself, I hope it stays like that.
EDIT: I'm going to try streaming through bluetooth to see if I have any problems, as a lot of others were complaining about it.
Gir357 said:
It hasn't really been acting up the last couple of days. However before that I couldn't listen for 2 minutes without it cutting out.
Oh well. Problem solved itself, I hope it stays like that.
EDIT: I'm going to try streaming through bluetooth to see if I have any problems, as a lot of others were complaining about it.
Click to expand...
Click to collapse
Interesting, the people on our boat on the OnePlus One forums said the same thing. I wonder if I should just let the error happen and see if it fixes itself instead of trying to avoid it by leaving the screen on.
And please do! I completely forgot to test the bluetooth problem.
I had the skipping thing and what I did to get rid of it was turn "off" the smart battery saver, and set it to normal.
Cuts the battery time, but good grief, even with it off, I get 2 days EASY.
ScoobSTi said:
Interesting, the people on our boat on the OnePlus One forums said the same thing. I wonder if I should just let the error happen and see if it fixes itself instead of trying to avoid it by leaving the screen on.
And please do! I completely forgot to test the bluetooth problem.
Click to expand...
Click to collapse
So I have been using my "Big Blue Live" bluetooth speaker for the past couple of days. I've probably listened to a couple hours worth of music and it hasn't skipped once. I don't have a bluetooth compatible car to test car compatibility in, otherwise I would do that too. But I don't have any skipping problems.
HOWEVER I remember I was coming back home from a trip and I wanted to listen to the radio from Chicago so I downloaded an app and hooked it up to the car via bluetooth (it was a rental) and IT was cutting out....that may have just been a problem with the app though.
I have a Verizon Samsung Note 2. It is NOT rooted, running stock ROM 4.4.2.
I have been having issues with bluetooth devices having audio cutting in & out issues. Here is the odd thing, it doesn't loose connection & it doesn't happen with everything I connect it to via bluetooth.
I can connect with both my vehicles & no issues.
I have 2 LG headsets & a JUMBLR bluetooth, that the audio with cut in & out after 3-5 minutes of playing. I can restart the device & it will work, but with the same result.
I have a Jabrees bluetooth device that will stream audio just fine, no issues.
I am at a loss as to how to correct this & am looking for some input.
Thx in advanced!!
weave423 said:
I have a Verizon Samsung Note 2. It is NOT rooted, running stock ROM 4.4.2.
I have been having issues with bluetooth devices having audio cutting in & out issues. Here is the odd thing, it doesn't loose connection & it doesn't happen with everything I connect it to via bluetooth.
I can connect with both my vehicles & no issues.
I have 2 LG headsets & a JUMBLR bluetooth, that the audio with cut in & out after 3-5 minutes of playing. I can restart the device & it will work, but with the same result.
I have a Jabrees bluetooth device that will stream audio just fine, no issues.
I am at a loss as to how to correct this & am looking for some input.
Thx in advanced!!
Click to expand...
Click to collapse
I'm not sure if this will help or not, but you might try an app that basically keeps your phone's cpu from dropping down into the lower mhz range when you're not actively using the phone. (I'm guessing you probably lock the screen when playing music).
An app like Wake Lock Power Manager might work, found here: https://play.google.com/store/apps/details?id=eu.thedarken.wl.
I actually stopped using Wake Lock Power Manager and switched to an app called Blank Screen ( here : https://play.google.com/store/apps/details?id=com.mirwanda.blankscreen) . I'm not totally sure... but I think that when you only have the screen go blank with this app... that it allows the cpu to keep performing as if the phone still has the screen on.... which may keep the cpu from dropping down into power saving range. I've never run any tests to confirm this theory, so I could be totally wrong.... However it works though, it seems to help prevent the stuttering problem I was having.
I also try to remember to long press my home button to close all running apps, then go to task manager to clear memory before starting up my music. Using the Blank Screen app and taking these extra steps seems to have solved the stuttering for me. It might not work for you, but won't hurt anything to try.
I will try it.
What other don't understand is why doesn't it do it when I'm streaming through my car & the screen is off?
weave423 said:
I will try it.
What other don't understand is why doesn't it do it when I'm streaming through my car & the screen is off?
Click to expand...
Click to collapse
Yeah... I'm not sure what would cause that either. A quick Google search shows that a lot of other people report having Bluetooth problems with KitKat 4.4.2, so you're not alone with the problems. Maybe the quality of the antennas on the LG headsets & JUMBLR are not as good as the antennas in the car and other device. I also wonder if something is trying to sync or run in the background on the headsets... and maybe it doesn't do this with the car??
You could try turning off auto sync on the phone to see if this might help. You could also try to Disable (Turn Off) different apps through the "Manage Apps" feature under phone's settings to see if this might help.
Another easy thing to try would be to clear the phone's "Cached Data" to see if this might help-- (I read somewhere on the Internet where someone said this helped them). You can do this by going into phone settings / storage / then touch on Cached Data and clear it.
Also... here's a post where someone says that they had duplicate Google Contacts that were syncing issues/ that ultimately was causing their Bluetooth problems ( http://forum.xda-developers.com/showthread.php?t=2646592&page=2 ). They say that by going into Google Contacts and deleting the duplicates, that it fixed the syncing problem and the Bluetooth issues. (You could do this by going to Google Contacts at https://contacts.google.com, the go to "Find Duplicates," and either merge or delete any duplicate contacts that it shows).
You could also try rebooting the phone into Safe Mode to see if the Bluetooth works better. If so, this may indicate that an app you installed could be causing the Bluetooth problems. To get into Safe Mode, Power off the phone, and then Press the Power button again to turn it back on... but also press the Volume Down button at the boot up splash screen and continue to hold volume down until the phone boots up completely. This should boot it into Safe Mode and you'll see Safe Mode in the bottom left of the screen. If Bluetooth works better in Safe Mode, then you can just reboot the phone and it will go back into Normal mode...then try disabling or uninstalling different apps and see if the Bluetooth works better.
I have a Moto Z Force (Droid), and got the OTA update for Nougat about a week ago (build NCL25.86-11). Since the update, I've had a lot of problems:
* Wifi issues: Right now my phone can't see any of the 10 or so access points near my house.
* Bluetooth Audio issues: Frequent skips listening to audio over bluetooth (every several minutes)
* Background Sync issues: Hangouts no longer syncs in the background, and Facebook seems to have occasional syncing issues. I get no Hangouts notifications at all (until I open the app), and my Facebook notifications are sometimes missing or delayed.
I think I may be having battery life issues with my Incipio battery Moto Mod, but I'm not sure about that.
Also, I can't remember if I tried this before the Nougat update, but when I'm using bluetooth and use voice commands to play music, all further bluetooth media plays back at extremely low (nearly inaudible) volume, even with bluetooth volume turned all the way to max, and I have to disconnect and reconnect to bluetooth to get normal volume on anything again.
I've tried multiple reboots, and a cache wipe. I'm pretty close to doing a factory reset, but was wondering if anyone else is experiencing these issues.
I am definitely seeing the Bluetooth audio skip - I downloaded my album off google play and had the same effect (verifies it isnt data connection). Skips and stutters on all audio - Pandora, Google Play, etc...
I have noticed WiFi issues - drops connection and comes back up
also getting zero notifications on apps.
Another issue I am seeing is the screen locking and becoming unresponsive - couple threads I have seen suggest this is caused by certain apps - so I am having to boot in safe mode and turn them on one at a time - friggin painstaking.
Definitely starting to miss my Note 5
By now I've no 7, but did you try to do a factory reset? I had similar problems with LG devices when upgrading vom 5 to 6. A factory reset resolved them completely. No fun to so so but ...
I've only experienced the Bluetooth issues. They went away after a reboot though.
Sent from my XT1650 using Tapatalk
I have absolutely no Bluetooth, cannot see or be seen by any other device. I'm exchanging it tomorrow.
Looks like my Wifi issue is not a Moto Z specific issue - it's happening exactly as described in this Nexus/Nougat forum post:
Code:
https://productforums.google.com/forum/#!topic/nexus/Qbeb7ZP0wOw
Perform a factory reset, then see where you are. Factory resets aren't as bad as the "old" days. You can pick your backup image date from the Google Welcome menu screens as you set the phone back up. If you use Nova launcher, import your saved desktop back up.
I've had the Bluetooth Audio skips as well. I also cannot use my camera about 75% of the time. It gives me the Camera error, Please restart the Camera app. I did a FDR and issues are still present.
Sent from my XT1650 using Tapatalk
wifi is slow used to get 218 megs down now only 136 down
I can add an other Bluetoorh issue. When I'm listening to podcasts while the phone is connected to the audio system of my car and I get interrupted by a phone call (which is also routed to the audio system of my car) after the call ends audio play back resumes for about half a second and the stops. I've to start it manually on the phone to resume. The podcast app (https://play.google.com/store/apps/details?id=com.bambuna.podcastaddict) is in paused state.
I'm definitely seeing WiFi drops and battery drain and heat issues with my Tumi battery mod. Also seeing screen freezes requiring a power button reset. Am getting very close to factory resetting.
I'm having problems going from WiFi to data. If I boot up the phone, it establishes a data connection. After Wifi is turned on, data permanently turns off and can't be reconnected without restarting the phone.
Note that I am using the phone overseas with a domestic (Japanese) sim card. Just last week however, I was using a Moto Z Droid Play and had no problems whatsoever. The standard Moto Z Droid has more Lte bands as well, so this shouldn't be happening.
I'm assuming it's a problem with WiFi to Lte handover related to Nougat?
TokyoGuy said:
I'm having problems going from WiFi to data. If I boot up the phone, it establishes a data connection. After Wifi is turned on, data permanently turns off and can't be reconnected without restarting the phone.
Note that I am using the phone overseas with a domestic (Japanese) sim card. Just last week however, I was using a Moto Z Droid Play and had no problems whatsoever. The standard Moto Z Droid has more Lte bands as well, so this shouldn't be happening.
I'm assuming it's a problem with WiFi to Lte handover related to Nougat?
Click to expand...
Click to collapse
Rather than restarting, toggle airplane mode.
Sent from my XT1650 using Tapatalk
PiousInquisitor said:
Rather than restarting, toggle airplane mode.
Actually that doesn't work. I tried it numerous times, along with disabling mobile data and then enabling it. I'm going to wipe the phone tonight and do a fresh start to see if that solves the problem.
Click to expand...
Click to collapse
Fix for wrong default APN Settings for O2 on Android 7.0 Nougat
After Upgrade to Android 7.0 mobile data did not work on german O2 Network.
After some research i found the right APN Option:
MVNO-Type have to be changed from IMSI auf „Keine“
Source: Giga.de - Android 5.0 Lollipop-Bugs & Probleme: Lautlosmodus, WLAN, Videowiedergabe & mehr [Ãœbersicht]
After that change another apn appeared called "O2 Internet", selecting it and LTE started to work as expected.
Hope that's help someone.
And here I was thinking this was the smoothest update on any Android phone I've received. I have no issues at all, didn't factory reset either. I also listen to podcast all the time over bluetooth, and never once did it skip. Maybe it's google music issues?
Also battery life has gotten much better.
Bluetooth disconnected issues for me via car Bluetooth since update.
any one having problems with sound cutting out on the phone only way to get sound back is by rebooting ?????????
I think the issues I'm seeing are due to overheating. Seems to happen after the battery pack charging kicks in at 80%. Anyone else notice this?
For the BT skipping/noise, turn off BT and turn it back on. That fixes it for me.
Don't know what's triggering it, though.
I use Spotify in my car and have set it to manually manage and allow it to run in the background..
However, the audio always cuts off to after a while after the screen goes off.
When I wake the phone I see Spotify still playing (audio via fone now, but this means it's kept running in background which is good) and Bluetooth remains connected to the device. It's like the android system just stops sending audio via Bluetooth after a while
Does anyone know how to solve this? My only workaround now is to keep the phone awake via an app like Google maps...
I'm on mate 10 pro. 8.0.0.131 c636
Sent from my BLA-L29 using Tapatalk
Same for me with deezer app and car audio which hadn't any disconnects on my other mobiles. No help though....
I tried to change the codec in developer options, which didn't change. I hadn't any bluetooth cutoff since then (couple of days now). Maybe coincidence.
I have discovered the same problem just today (my mate pro is fairly new). It is clearly a software bug. It also fails to update the track name on my car stereo - still shows the first track name even several tracks in.
To get it playing again I turned Bluetooth on and off. Quite annoying. I hope it gets fixed.
happens on my P10, happens on my mate10 pro as well.
It's not a bug, just unintuitive EMUI.
Fix Launch settings for Spotify and add the app on the "Ignore battery optimization"-list under Special Access menu.
It can be difficult to find. Search for "Special" and it will pop up, or click
Settings/Apps & notifications/Apps/Settings/Special Access/ignore battery optimization/
vembryrsig9 said:
It's not a bug, just unintuitive EMUI.
Fix Launch settings for Spotify and add the app on the "Ignore battery optimization"-list under Special Access menu.
It can be difficult to find. Search for "Special" and it will pop up, or click
Settings/Apps & notifications/Apps/Settings/Special Access/ignore battery optimization/
Click to expand...
Click to collapse
I did try this and it still doesn't work.
I don't think it's an issue with the app itself as this also happens on stock music app on stock launcher.
Audio cuts out, plays via the phone speakers so the app itself isn't being optimized or shutdown.. Seems like the Bluetooth function is though
Sent from my BLA-L29 using Tapatalk
I set spotify up with battery optimisation off and with manual launch in battery settings as part of my initial set up. That is not the cause of this Bluetooth problem, unfortunately.
Mine cuts off regardless of app and screentime... so even if i am playing music behind navigation, the bluetooth audio still pushes via the phone after a while
bluetooth still showing connected to the device.
The issue seems resolved for me, but don't know exactly what fixed it.
The only 2 things I did was to manually manage all apps(battery settings), prevent almost all apps from running in background except the audio apps (music/Spotify, and other impt widgets.. Which was already done previously)
And reset defaults on developer mode (not that i changed anything)
See if u guys have any luck with this
Sent from my BLA-L29 using Tapatalk
Hey guys,
Greetings from a Mediapad owner. (EMUI should have it's own subforum)
I first experienced this issue, or a similar issue for myself a few days ago - audio would cut out with the screen off, and would be choppy at best with the screen on (but my music player in the background). The music player itself would stay open, and as soon as I put in the foreground, audio would resume from where it left off (i.e. playback would be paused while the app was in the background).
I am also looking for insight. My suspicion is that EMUI's launch feature is responsible for killing an Android system process related to media, bluetooth, and/or battery optimization in this instance. Launch only allows you to specify preferences for user apps; system apps are managed automatically by Launch no?
Here is the insight I can provide:
This issue went away for me as soon as I plugged in a charger. Connected to a charger, EMUI's battery optimization is apparently less aggressive.
After trying random things, I once again attempted to stream music in the background without a charger plugged in. Eventually, the issue fixed itself. I am not sure if I did anything to accomplish that, however there are two things that may have contributed:
As with another poster above, I tried to change the bluetooth driver in Developer Settings. I was unsuccessful and there was no change for a while after.
The other thing I did, is I found what I think is the standard Android battery usage screen that EMUI hides from us, and I played around with it. This screen showed me that "Android System" was not set to ignore battery optimization. I tried to change that and couldn't. Really, I didn't change anything, but in this process it is possible that an Android system app relating to battery optimization may have been reopened after having been killed off?
The only way I know how to access that screen btw, is to download an app titled 'pNutsAnySettings' and then click on the tile with the battery percentage on it.
I had exactly the same issue with my Mate 10 pro in my car. Audio would cut off from car and continue playing on the phone but the car said it was still connected to the phone. I had the same kind of issue with my Garmin Forerunner watch which would constantly disconnect throughout the day meaning I missed smart notifications.
I found on another thread (Cant remember what one) that if you have root, use Titanium Backup to freeze the Power Genius app. Since doing this a few weeks ago I have not had the issue again in the car and my Garmin now stays connected all day and night
djclark25 said:
I found on another thread (Cant remember what one) that if you have root, use Titanium Backup to freeze the Power Genius app. Since doing this a few weeks ago I have not had the issue again in the car and my Garmin now stays connected all day and night
Click to expand...
Click to collapse
I read that same thing as well - but freezing the Power Genius app (via Xposed Edge Pro) didn't help in my case. Maybe it would have if I had rebooted, or something.
In any event, I believe that freezing the Power Genius app partially if not fully disables EMUI's launch feature, which I generally like...
This problem returned for me last night. I turned bluetooth off and back on again. That fixed it.
My mate 10 Pro does this too. 2011 Camaro SS with MyLink conversion. I go into BY, hit the info icon and disconnects the media playback then reconnect it. Works for a few days. Comes back. No clue why
(Unrooted stock btw)
Update: I finally disabled Power Genius and rebooted. No more pesky issues and if anything my battery life has improved. Only differences I observe (on my Mediapad): there are no longer 'app usage' battery stats inside the EMUI settings app (I can access them by other means), and Launch now needs to be managed through the Settings app (rather than the App Info screen).
thref23 said:
Update: I finally disabled Power Genius and rebooted. No more pesky issues and if anything my battery life has improved. Only differences I observe (on my Mediapad): there are no longer 'app usage' battery stats inside the EMUI settings app (I can access them by other means), and Launch now needs to be managed through the Settings app (rather than the App Info screen).
Click to expand...
Click to collapse
What app now
leo72793 said:
What app now
Click to expand...
Click to collapse
The app you need to freeze or disable is Power Genius. It's a component of EMUI. It won't show up in your main app list, but if you are rooted you can use an app like Titanium or Service Disabler to do the trick. If you aren't rooted - this is a prime example of why people root.
If that's what you were asking?
Since I've tried everything i could to solve this issue, searched all forum/reddit/google for 14 hours, I'm asking for help here as a last resort.
Symptoms:
When i receive a phone call i tap on green to accept, the watch act as everything is fine (jumps to in call screen, starts to count...etc) but actually the phone doesn't accept it, just keeps ringing.
If i accept the call afterwards on the phone itself, everything works fine watch acts as a BT headset automatically.
Remarks:
Disabling+Enabling "bluetooth phone function" on the watch solves the problem temporaly, probably until next notification/sync.
-Amazfit Verge 3.2.2.0 3.2.3.0
-HTC U Ultra (tried with both stock Android 8.0 and LineageOS 9.0)
-Amazfit Watch (2.7.0.1) app permissions are enabled (call logs, camera, contacts, location, storage, telephone)
-Android Battery optimisation disabled for: Amazfit Watch, Amazmod, Bluetooth, Call management, Contacts, Phone, Phone services
-Amazfit Watch/Amazmod notification: As battery opt. above, but i've even tried it with adding everything (including all system apps)
-Enabled: Android settings/Google/Vocie/Allow Bluetooth request with device locked
-Tried it with and without Amazmod
-Watch factory reset, apps reinstall are done
Update: I did more testing, and the answer call does work if I wait at least 4-5 seconds before tapping the accept button.
It is probably an issue of both sides: the phone needs some time to accept the watch as a BT headphone, while the watch does not have any check/redundancy for accepting call during this phase.
DraX8 said:
Since I've tried everything i could to solve this issue, searched all forum/reddit/google for 14 hours, I'm asking for help here as a last resort.
Symptoms:
When i receive a phone call i tap on green to accept, the watch act as everything is fine (jumps to in call screen, starts to count...etc) but actually the phone doesn't accept it, just keeps ringing.
If i accept the call afterwards on the phone itself, everything works fine watch acts as a BT headset automatically.
Remarks:
Disabling+Enabling "bluetooth phone function" on the watch solves the problem temporaly, probably until next notification/sync.
-Amazfit Verge 3.2.2.0
-HTC U Ultra (tried with both stock Android 8.0 and LineageOS 9.0)
-Amazfit Watch (2.7.0.1) app permissions are enabled (call logs, camera, contacts, location, storage, telephone)
-Android Battery optimisation disabled for: Amazfit Watch, Amazmod, Bluetooth, Call management, Contacts, Phone, Phone services
-Amazfit Watch/Amazmod notification: As battery opt. above, but i've even tried it with adding everything (including all system apps)
-Enabled: Android settings/Google/Vocie/Allow Bluetooth request with device locked
-Tried it with and without Amazmod
-Watch factory reset, apps reinstall are done
Click to expand...
Click to collapse
Maybe problem that you using a lot of unofficial apps, software and ect.? By the way for me working fine, i'm with stock ROM, today got new update 3.2.3.0 where was fixed some bugs
xdauser2019 said:
Maybe problem that you using a lot of unofficial apps, software and ect.? By the way for me working fine, i'm with stock ROM, today got new update 3.2.3.0 where was fixed some bugs
Click to expand...
Click to collapse
Thank you for your reply/suggestion.
I tried it with clean watch+phone, no changes at all. New update did not helped either.
Meanwhile i got some testing time with it, and found out i have to wait before i accept a call.
After 5-6 vibrations on the watch i can accept the call with success, i would guess this bug is due to the phone needs some time to set the device as bluetooth headphone.
Probably the watch SW does not have any checks is it done already, also no redundancy for answering a call (sending the OK signal a few times for example, if that is possible).
make sure that in the bluetooth, you have the voice profile enabled for the watch connection
1immortal said:
make sure that in the bluetooth, you have the voice profile enabled for the watch connection
Click to expand...
Click to collapse
Thank you for the suggestion, it was enabled already.
Meanwhile i could do some testing, updated the OP also as:
I did more testing, and the answer call does work if I wait at least 4-5 seconds before tapping the accept button.
It is probably an issue of both sides: the phone needs some time to accept the watch as a BT headphone, while the watch does not have any check/redundancy for accepting call during this phase.
Click to expand...
Click to collapse
Do you think it is possible to solve this issue with Amazmod? Implementing some kind of redundancy or check for the phone watch app?
DraX8 said:
Thank you for your reply/suggestion.
I tried it with clean watch+phone, no changes at all. New update did not helped either.
Meanwhile i got some testing time with it, and found out i have to wait before i accept a call.
After 5-6 vibrations on the watch i can accept the call with success, i would guess this bug is due to the phone needs some time to set the device as bluetooth headphone.
Probably the watch SW does not have any checks is it done already, also no redundancy for answering a call (sending the OK signal a few times for example, if that is possible).
Click to expand...
Click to collapse
I recommend you to test without any amazmod and ect., problem can be with 3rd parties software, apps. If you still have problem when you using everything from manufactors: stock rom on smartphone/smartwatch and everything is updated, i recommend you to connect with Amazfit support https://en.amazfit.com/support.html or https://us.amazfit.com/contact (this is US support, but they taking advice for all costumers, keep patience checking, often is disconnected). I don't have this porblem, coz if say honest i don't talk right now over watch. But maybe need to test someday too. By the way for me need to wait a little bit too when watch will be vibrate after ring smartphone, it's all, if i'm not wrong, problem of Amazfit watches. With other manufactor i did not had this problem. But if say honest time between ring and vibrate is about 1-2 second in my situation
xdauser2019 said:
I recommend you to test without any amazmod and ect., problem can be with 3rd parties software, apps. If you still have problem when you using everything from manufactors: stock rom on smartphone/smartwatch and everything is updated, i recommend you to connect with Amazfit support https://en.amazfit.com/support.html or https://us.amazfit.com/contact (this is US support, but they taking advice for all costumers, keep patience checking, often is disconnected). I don't have this porblem, coz if say honest i don't talk right now over watch. But maybe need to test someday too. By the way for me need to wait a little bit too when watch will be vibrate after ring smartphone, it's all, if i'm not wrong, problem of Amazfit watches. With other manufactor i did not had this problem. But if say honest time between ring and vibrate is about 1-2 second in my situation
Click to expand...
Click to collapse
I did, factory reset on both watch and phone stock rom (then LineageOS 9.0 on phone), the same issue.
Wrote to official support also today, no reply yet thou.
I also have a second of lag when the watch starts to ring, but i have to wait over that a few seconds to be able to really answer the call.
It is usable now with waiting 4-5 seconds, i just have to not forget it and answer the call too fast...