My p6 will see most some of my Bluetooth devices (laptop, tablet, TV, earbuds) . It pairs with the earbuds, but everything else it will try and pair, usually does not. If and when hen it does pair, that pairing is dropped dropped within 5 secs. Cleared BT cache, rebooted. No joy. It will show no paired devices.
Network reset.
Clear system cache.
Hard reboot.
Do not factory reset; find to root cause as it will likely reoccur otherwise, eventually.
It may be a 3rd party app, try in safe mode.
Try rolling back associated apks to their factory load versions if updated.
Double check permissions and settings.
blackhawk said:
Network reset.
Clear system cache.
Hard reboot.
Do not factory reset; find to root cause as it will likely reoccur otherwise, eventually.
It may be a 3rd party app, try in safe mode.
Try rolling back associated apks to their factory load versions if updated.
Double check permissions and settings.
Click to expand...
Click to collapse
Thanks. Tried everything but the "roll back " . It will remain paired with ear buds and car, but laptop, desktop,tablet and phone all disconnect immediately
Tool Belt said:
Thanks. Tried everything but the "roll back " . It will remain paired with ear buds and car, but laptop, desktop,tablet and phone all disconnect immediately
Click to expand...
Click to collapse
You play with bt settings in Developer options?
Is power management active? This doesn't fit power management's profile for erratic behavior but maybe it got "smarter".
Played with BT in developer. I will give power a try, but I don't understand why the buds and car are seemingly 0k. I haven't the chance to be in the car for an extended period.
Tool Belt said:
Played with BT in developer. I will give power a try, but I don't understand why the buds and car are seemingly 0k. I haven't the chance to be in the car for an extended period.
Click to expand...
Click to collapse
Think about the clues.
Are the other devices configured properly?
Check Event Viewer in Windows for error messages, it might tell you why this is happening.
Try some Google searches for similar issues, it can be other devices and OS versions. Many issues span both. With a newer device this strategy works many times.
To see if power management is active Developer options>standby apps, all buckets should show as active, otherwise power management is running. It can't be disabled here though.
Power checks out. I tried to send a file from the tablet. Phone showed the attachment, file failed. Was able to send a file to tablet using "nearby device"
Tool Belt said:
Power checks out. I tried to send a file from the tablet. Phone showed the attachment, file failed. Was able to send a file to tablet using "nearby device"
Click to expand...
Click to collapse
Do it to the PC and see what error messages Event Viewer shows.
Sent file from lap top to P6. P6 paired and accepted. Closed send window on LT and P6 dropped connection. Sent another file and did not click finish on LT and P6 remains connected and LT acts as trusted device for Smart Lock. The purpose here is not having to get frustrated with the FP sensor while at home. Using Trusted Location enables an area with nearly a half mile radius
It's not just bluetooth, it has to do with the Wifi+Bluetooth implementation. You can reliably crash System Settings after a factory reset if you type a wifi password wrong on the same network more than once, or if you attempt to connect to the same network with an incorrect password too many times. Attached "proof" (not really proof but). Once it crashes it'll restart setup but won't let you continue past Network Setup.
I could not get my Android Wear watch (Fossil Gen4) to connect. It was seen once and tried to but the bluetooth stack crashed. Even after a reboot, settings reset, forgot the device, and factory reset the watch it would not work.
My Pixel buds connected via fast pair and "worked", but the phone refused to identify them as Pixel Buds and I could not use the dedicated settings app. Same thing with my Galaxy Buds Live, the Samsung Wearable app would not find the buds even when connected.
MichRT said:
It's not just bluetooth, it has to do with the Wifi+Bluetooth implementation. You can reliably crash System Settings after a factory reset if you type a wifi password wrong on the same network more than once, or if you attempt to connect to the same network with an incorrect password too many times. Attached "proof" (not really proof but). Once it crashes it'll restart setup but won't let you continue past Network Setup.
I could not get my Android Wear watch (Fossil Gen4) to connect. It was seen once and tried to but the bluetooth stack crashed. Even after a reboot, settings reset, forgot the device, and factory reset the watch it would not work.
My Pixel buds connected via fast pair and "worked", but the phone refused to identify them as Pixel Buds and I could not use the dedicated settings app. Same thing with my Galaxy Buds Live, the Samsung Wearable app would not find the buds even when connected.
Click to expand...
Click to collapse
This sounds similar to my problems. Try and contact support (took 50 minutes for a call back) and get it into their system.
Tool Belt said:
This sounds similar to my problems. Try and contact support (took 50 minutes for a call back) and get it into their system.
Click to expand...
Click to collapse
I'm sorry you're dealing with it I've since factory reset the device and haven't tried crashing anything, so things seem to be working so far. I have an RMA P6 on the way already due to terrible screen tint issues on my phone. Took over 3hrs (1hr waiting for chat to be available, 1hr in line on chat, 1hr on chat)
I may try a reset when I am bored. Gr8 you have a new one coming
Related
I have the Gear S and the Note 4 (both through T-Mobile). I have noticed that when I move out of bluetooth range of my phone, the watch connects remotely so that I can take calls on the watch, but when I come back within bluetooth range of the phone the watch will not automatically reconnect via bluetooth. It remains connected remotely (even when the phone and the watch are sitting right next to one another). Am I doing something wrong, or am I just going to have to reestablish the bluetooth connection manually?
Illusive Man said:
I have the Gear S and the Note 4 (both through T-Mobile). I have noticed that when I move out of bluetooth range of my phone, the watch connects remotely so that I can take calls on the watch, but when I come back within bluetooth range of the phone the watch will not automatically reconnect via bluetooth. It remains connected remotely (even when the phone and the watch are sitting right next to one another). Am I doing something wrong, or am I just going to have to reestablish the bluetooth connection manually?
Click to expand...
Click to collapse
It not gonna reconnect right away. Blue tooth would have to be scanning non stop. Then people will complain about battery dying fast. Also it takes about 10 min for it to search and connect depending on your phone.
BAD ASS NOTE 4 + BAD ASS GEAR S
Thanks a lot. That explanation actually makes a lot of sense.
That's not quite how Bluetooth works, however this fix for this issue is straight forward.
Un install Samsung Gear from your phone. Reset your Gear S, install Samsung Gear, reconnect phone and restore data.
Bluetooth should re connect within seconds after you walk away from your phone.
This broke because of an issue in an update patch to the Samsung Gear software. The patch does not upgrade the software properly, and a re installation is required.
I had the same issue with my Note Edge and Gear S.
Fixed now though.
I had the same issue and re installed yesterday and it connected. What I found to be annoying was I had to completely delete Samsung app store from note or I couldn't install apps from Sammy. It would download then during install process it would fail with error code -112 . It may have something to do with when I fix permission in recovery but it only started doing that after latest update. It's annoying but I guess the temp solution is easy to fix
I have similar problem with bluetooth. When I turn off bluetooth and then turning on the Gear won't to connect. On the phone request pair code for bluetooth appears, but on Gear appears: GT-I9301I is attepting to connect to your Gear. To connect to GT-I9301I, the gear will be reset to its factory settings..When the device is reset, it connect properly and everything work fine until I turn bluetooth off. Then again want to reset the device. My Gear is SM-R750A and phone is GT-I9301I. I try to re-install Gear Manager, reset phone, reset Gear, but still have tis problem.
jay_dremix said:
I have similar problem with bluetooth. When I turn off bluetooth and then turning on the Gear won't to connect. On the phone request pair code for bluetooth appears, but on Gear appears: GT-I9301I is attepting to connect to your Gear. To connect to GT-I9301I, the gear will be reset to its factory settings..When the device is reset, it connect properly and everything work fine until I turn bluetooth off. Then again want to reset the device. My Gear is SM-R750A and phone is GT-I9301I. I try to re-install Gear Manager, reset phone, reset Gear, but still have tis problem.
Click to expand...
Click to collapse
I have made a thread describing how to fix this....In a nut shell you need to completely uninstall gear mgr and galaxy apps and delete the apps in gear manager under the manage apps then click all which is beside the updates tab. Also uninstall all updates to galaxy apps. This will fix issue. here is the xda thread link. Follow it to a t and you will be good l. Let me know your outcome.
TechnRom said:
I have made a thread describing how to fix this....In a nut shell you need to completely uninstall gear mgr and galaxy apps and delete the apps in gear manager under the manage apps then click all which is beside the updates tab. Also uninstall all updates to galaxy apps. This will fix issue. here is the xda thread link. Follow it to a t and you will be good l. Let me know your outcome.
Click to expand...
Click to collapse
I try this, but didn't work. I think the problem is Bluetooth of the phone, becouse I paired Gear S with two different phone and work fine. Also when I try to pair phone with bluetooth in car it appears same problem - connect only first time. Is there any way to re-install the Bluetooth or to change driver or something like that.
Try deleting data in app manager for anything bluetooth related. Factory reset phone if that doesn't work. If you are on a custom rom reinstall rom and see if that helps, research if a different kernel works better. Good luck
Turn off "Use Remote Connection" in the Gear S app settings on your phone. Problem solved
Actually, ignore my previous response, that did not solve the issue.
What did, however, was unpairing then reparing the Gear S to my phone. No problems since
BleahBleah said:
That's not quite how Bluetooth works, however this fix for this issue is straight forward.
Un install Samsung Gear from your phone. Reset your Gear S, install Samsung Gear, reconnect phone and restore data.
Bluetooth should re connect within seconds after you walk away from your phone.
This broke because of an issue in an update patch to the Samsung Gear software. The patch does not upgrade the software properly, and a re installation is required.
I had the same issue with my Note Edge and Gear S.
Fixed now though.
Click to expand...
Click to collapse
I had the same issue and used the suggestion above and it didn't work.
I uninstalled on the device, reset gear, then reinstalled on device and reconnected...bluetooth did connect. I walked away came back and the gear didn't reconnect automatically. I had to reconnect from the phone side. THIS SUCKS!!!
Anyone have any other suggestions? i have gear s and NOTE 3 (android 5.0)
Illusive Man said:
I have the Gear S and the Note 4 (both through T-Mobile). I have noticed that when I move out of bluetooth range of my phone, the watch connects remotely so that I can take calls on the watch, but when I come back within bluetooth range of the phone the watch will not automatically reconnect via bluetooth. It remains connected remotely (even when the phone and the watch are sitting right next to one another). Am I doing something wrong, or am I just going to have to reestablish the bluetooth connection manually?
Click to expand...
Click to collapse
Had same issue with my Note 3. I was on some modified ROM and it was cousing all the trouble. Switched to this one http://forum.xda-developers.com/galaxy-note-3/development/rom-aryamod-v1-tw-lollipop-t2990920 and everything works like charm. Alllso love the ROM. :good:
Note 5 and Gear S not reconnecting automatically
My New Note 5 has the same problem, not reconnecting after phone and watch are back together. I have to manually flip on phone use in bluetooth settings. This is still after factory resetting phone and watch. Is there any updated fixes
Cebudukas said:
Had same issue with my Note 3. I was on some modified ROM and it was cousing all the trouble. Switched to this one http://forum.xda-developers.com/galaxy-note-3/development/rom-aryamod-v1-tw-lollipop-t2990920 and everything works like charm. Alllso love the ROM. :good:
Click to expand...
Click to collapse
Besides the Rom change any other fixes, I have a note 5 with the same issue
i had this problem after the last update. all i did was to unpair it from my phone and then pair it again works perfect now..
Facing the problem after an update, resetting the watch doesn't help. Cant reset phone as lot of stuff on it. Cant take a complete backup. stuck with this now. Any solutions.
If I restart bluetooth share the watch connects. Any work around for this issue .
gear s cyanogenmod os unable to connect to galaxy s4
Hello
I have installed cyanogenmod 12.1 in my gear s. Now trying to pair the gear s by installing samsung gear app in mobile (S4) but mobile is unable to find my gear s. then i tried android wearable app. In android wearable it detects the gear s but for long time unable to sync the data. I also found that bluetooth gets disconnected (either from gear s or S4 that unable to understand). Please help how do i pair my S4 with gear s. DO i have to install any software in gear s?
Hello someone managed to solve even me notes 3 and gear s when disconnected with the bluetooth will not re connects
Hey everyone!
I picked up a Gear S about a week ago and until today, I've had no problems. I took the watch off charge this morning and everything was working as fine, used some apps etc, no issues. Then I checked my phone for updates and saw that the Gear Manager app had an update and I installed it. Since then, the screen on my Gear S has been constantly turning on and off. It will turn for about 9 seconds, then switch off and back on 2 seconds later. Turning the screen on manually works but everything is pretty much frozen. I can periodically get as far as the pedometer (because there's an icon for it on the home screen) or to the Apps menu but no further and then the screen will switch itself off.
I'm not sure whether an update to the Gear Manager app should affect the watch itself but I know that when I wiped my phone a few days ago and went to set up the Manager again, it factory reset the watch so I assume there is a direct connection between the software. I've tried disabling both Bluetooth and the remote connection to check if Gear Manager is causing the screen to behave strangely but it's still turning on and off. It's impossible to do a soft reset through the Gear S itself as the screen switches off before I can get to settings and I've tried doing a hard reset but nothing works.
I tried searching on Google for anyone having similar issues and the only thread I can find was posted on Android Central (yesterday I think) with a few people saying that they're having the same problem which makes me thing that the update to Gear Manager is the issue.
Edit: The only screen that doesn't seem to be affected is the PIN lock screen. Screen switches off there as normal and does not come back on.
Edit 2: I've never reset the Gear S before (and I only noticed the factory reset mentioned above after it was finished) but when I attempt to do a hard reset, the watch just reboots as normal without anything happening and all info / data is still there. I presume this really shouldn't be the case?
UPDATE: I'm an idiot / Samsung's instructions on how to do a hard reset are awful.
I decided to Google how to do a hard reset and discovered that when in the Recovery Menu, you need to hold down the Power button to choose an option (Samsung's instructions just tell you to press the Power button until you highlight what you want and I assumed it would automatically choose that after a few seconds because the phone would restart for me). Watch is now factory reset and so far the screen issue appears to be resolved. Another four hours of transferring music it is then.
@BOZG can you post a link to that thread?
I have the Same problem. Sometimes changing a clock face or installing/uninstalling a program seems to make it stop. I have yet to find a good consistent solution. Restarts etc. don't help. Hard reset will fix it but last time I just changed settings on and off and powered the phone on and off and eventually it stopped.
It seems related to when the phone is connected remotely over a cell network. I have the AT&T unlocked with a T-Mobile regular line, not the wearable line since I have a 5 for $100 business plan and the 5th line was not being used. Doubt that makes a difference though.
Followup:
Just now I had the watch off and charged to 100%. Powered up with phone off. Same issue. Watch face loads, the hands change to the current time, then it slides down the screen and looks like a reload because when it comes back up the time isn't correct. The hands reset to the right time. This happens a few times. I power the phone up. Bluetooth connects. I open the gear manager on the phone and it stops.
Will try to repost if that's repeatable. I hope they fix it because it burns quite a bit of battery when it happens. It gets warm so it's running the CPU a lot whatever it is.
allow to power down
BOZG said:
Hey everyone!
I picked up a Gear S about a week ago and until today, I've had no problems. I took the watch off charge this morning and everything was working as fine, used some apps etc, no issues. Then I checked my phone for updates and saw that the Gear Manager app had an update and I installed it. Since then, the screen on my Gear S has been constantly turning on and off. It will turn for about 9 seconds, then switch off and back on 2 seconds later. Turning the screen on manually works but everything is pretty much frozen. I can periodically get as far as the pedometer (because there's an icon for it on the home screen) or to the Apps menu but no further and then the screen will switch itself off.
I'm not sure whether an update to the Gear Manager app should affect the watch itself but I know that when I wiped my phone a few days ago and went to set up the Manager again, it factory reset the watch so I assume there is a direct connection between the software. I've tried disabling both Bluetooth and the remote connection to check if Gear Manager is causing the screen to behave strangely but it's still turning on and off. It's impossible to do a soft reset through the Gear S itself as the screen switches off before I can get to settings and I've tried doing a hard reset but nothing works.
I tried searching on Google for anyone having similar issues and the only thread I can find was posted on Android Central (yesterday I think) with a few people saying that they're having the same problem which makes me thing that the update to Gear Manager is the issue.
Edit: The only screen that doesn't seem to be affected is the PIN lock screen. Screen switches off there as normal and does not come back on.
Edit 2: I've never reset the Gear S before (and I only noticed the factory reset mentioned above after it was finished) but when I attempt to do a hard reset, the watch just reboots as normal without anything happening and all info / data is still there. I presume this really shouldn't be the case?
Click to expand...
Click to collapse
I left mine to use up all the battery,then when it switched off, i left for 2 days and when i switched back on... all fine again.
theroblog.com said:
@BOZG can you post a link to that thread?
I have the Same problem. Sometimes changing a clock face or installing/uninstalling a program seems to make it stop. I have yet to find a good consistent solution. Restarts etc. don't help. Hard reset will fix it but last time I just changed settings on and off and powered the phone on and off and eventually it stopped.
It seems related to when the phone is connected remotely over a cell network. I have the AT&T unlocked with a T-Mobile regular line, not the wearable line since I have a 5 for $100 business plan and the 5th line was not being used. Doubt that makes a difference though.
Followup:
Just now I had the watch off and charged to 100%. Powered up with phone off. Same issue. Watch face loads, the hands change to the current time, then it slides down the screen and looks like a reload because when it comes back up the time isn't correct. The hands reset to the right time. This happens a few times. I power the phone up. Bluetooth connects. I open the gear manager on the phone and it stops.
Will try to repost if that's repeatable. I hope they fix it because it burns quite a bit of battery when it happens. It gets warm so it's running the CPU a lot whatever it is.
Click to expand...
Click to collapse
samsung gear s screen on and off..looping
There you go. Not much to read there though as it's just me and OP. The problem re-emerged for me after a few days again so I was forced to do another hard reset to actually use the watch. I noticed it when I woke up in the morning and noticed that another update had been pushed to the Gear app. That's twice now that this has happened shortly or immediately after the Gear app was updated.
I haven't been able to uninstall an app / change clock face to see if it works as the watch is completely unusable when it happens to me. The Gear app registers that it's connected but it's impossible to change anything from there either and if I turn the watch off and back on again, the Gear app will no longer connect.
petethepete2000 said:
I left mine to use up all the battery,then when it switched off, i left for 2 days and when i switched back on... all fine again.
Click to expand...
Click to collapse
Not sure if I've actually tried letting the battery drain. I'll try that the next time it happens (if it happens).
I had the same problem after the update, a reboot didn't solve the problem. Eventually the battery drained. After a recharge most is fine but I never know which watch face will suddenly appear.
Same issue again. Didn't see the Gear app updating but there was an update released the day before. Going to switch off auto-updates and see if it definitely the problem. Just seems too coincidental that this problem starts right after an update is released for the Gear App.
petethepete2000 said:
I left mine to use up all the battery,then when it switched off, i left for 2 days and when i switched back on... all fine again.
Click to expand...
Click to collapse
Started doing it again yesterday so let the battery die and charged it fully and it didn't help. Left it on the box overnight and brought it to a Samsung Service Centre this morning and of course it was working again when I took it out of the box! Left it with them anyway so I'll see what happens.
I've had my Gear S a few weeks and it has also started doing this, I will give some of the suggestions here a go.....
EDIT: So opening the Gear Manager App once Bluetooth was connected brought my Gear S back to life. Phew!
It's only entered this state after I turned it off at night and then turned it back on in the morning - so it had been off roughly 8 hours. Upon turning it on the screen would cycle from the right time and notification numbers and the wrong time and wrong notification numbers too off again.
@ BOZG - Just wondering if you got your S back yet and if so, were they able to tell you what was causing this on/off problem. Mine just started doing it yesterday.
Also, how did you find the "Samsung Service Centre"?
holding the screen seems to cause it...
Had to send mine to Samsung for a new charging cradle and they updated the software to latest, when i got it back it seemed fine. Then i was messing about with it and was holding the screen to my chest for a while and that seemed to cause it to happen. It seems to be the screens gets too much activation and it flips out. I think this is what started the problem last time it happened.1
Switching to power saving mode seems to fix it for me... have to wait until it gets low on battery and when the low bat warning comes on, switch then... leave for a bit then switch back to normal.
I called Samsung Thursday and they sent me a UPS label and told me to send the watch, charging cradle and AC charging cord back in for service. She told me it takes about 7-14 days. We shall see.
Happy to have found this. </rant>I'm starting to get enough of this Samsung stuff. I had the note 2 and now I have the note 4 and gear S. That is mote then 1000 euro of equipment. And today when I tried the restore to fix this, both the phone and the watch rebooted. Crazy that they can not build good software and hardware for this price. </rant>
To me it seems that is freezes somehow when this happens. It kept jumping back to 22:10 time and changed to the watch-face and settings keep rolling back. It seems to happen to me, when the watch is off for some hours. The samsung way... no update to fix this.
solved for me
hi first of all sorry if i do any mistakes because English is not my language
i had similar problem and i found the solution at least in my case . THE PROBLEM IS NOT WITH THE GEAR S
all was ok using 4.4.2 kitkat on my note 3 before few months i upgrade with lollipop 5 official from sammobile via odin
from that moment the problems begin with the reconnection of the gear with the note
long time to connect and no auto reconnection only manual by turning off-on the bluetooth
i was boring to do format to the note3 so i left it as it
few weeks ago probably of gear manager update the gear start freezing and the screen turning on and off
first i do a factory reset and the gear was ok for a while but after it do the same but the next time the screen was not ok the colors was different so i send to service in Athens
the service in Athens is very fast and very helpful , is one of the reasons that i will difficult go with other manufacture , so they return me the gear saying that they change the motherboard and now there is new imei
but the gear that they send me was brand new except the band and the box. BUT after some time the same problem ..... i call them and they tell me to send it back so i send it and i receive it again but this time the say that the watch is ok
GUESS NOW .... i turn it on and after a while of the connection with my note AGAIN the same problem the screen on and off and freezing plus was overheat underneath
i was ready to call them and to say few words but they was closed ..... then i search the net and i found this post and i thing probably is not the gear the problem ,no hardware problem, i decide to do a test
i download the last working rom to my phone 4.4.2 and magically the problem disappears .... but now there is a software update on my phone lollipop 5 so i do the update and i was ready if the phone cause again the same problem
to return and stay with 4.4.2 But now all is ok the problem solved .... now is more of 24h and all are ok
i hope this will work for you also
Same problem
I have the same issue exactly - Note 4 with latest lollipop upgrade - it is very frustrating......I don't particularly want to have to move back an OS just to use the watch !
JALUK said:
I have the same issue exactly - Note 4 with latest lollipop upgrade - it is very frustrating......I don't particularly want to have to move back an OS just to use the watch !
Click to expand...
Click to collapse
Ok but doing a downgrade and all working ok you can do update again.... i am not with 4.4.2 i went to the latest 5.0 for me now and all are ok.
Maybe something was wrong with the update procedure.
UPDATE
the touch function of the 2nd gear stop working so i send it back and they send me new device
for a few days all was ok . But today when i restart the phone while the gear was disconnected the problem with screen turning on repeatedly appears again .
for sure is not problem of the gear , this is the 3rd device in my hands, something is wrong with the gear manager software .
i have also reconnection problems .... if the phone is far away and they lost Bluetooth connection the most of the times i must reconnect manually , the gear say disconnected but the note think is still connected
I wonder has anyone tried to reset the watch as a stand alone device and see if the problem happens? I know you might lose a lot of the blue tooth functionality but I think I will test it and see if the problem still happens.
How is bluetooth doing?
I preordered it a couple of weeks ago but I am a little bit worried about. I still can withdraw the order.
I have Sony's SBH54, Bose QC35 and a Peugeot 2008 car stereo, just to explain the case.
Thanks for the help.
Bhonder said:
How is bluetooth doing?
I preordered it a couple of weeks ago but I am a little bit worried about. I still can withdraw the order.
I have Sony's SBH54, Bose QC35 and a Peugeot 2008 car stereo, just to explain the case.
Thanks for the help.
Click to expand...
Click to collapse
Has anyone said there is issues with Bluetooth? I don't have Bluetooth in my car anymore but I had issues sending some files
Sent from my Sony Xperia XZ1 using XDA Labs
It has been reported by one fellow on the Sony's forum but he was the only one. He talked about car stereo on a bmw x1.
Curiously, symptoms was similar to the nexus' oreo Bluetooth problem.
I suggested him to get in touch with the car dealer but when I found the nexus thread I became a little bit worried: I have to drive a lot for commuting and I need noise cancellation at work, hence car stereo and qc35.
I had a Z5 and recently bought the XZ1. I use bluetooth on my car stereo on a daily basis and never had issues with the Z5.
The XZ1 however, is a hit and miss. It would connect fine but sometimes it either won't display media information or I won't be able to use media controls on my car stereo. Most of the time it would work just fine.
A solution which worked has been setting AVCRP to version 1.4 by developer options under the Bluetooth section.
QC35 are still to be tested because they've been sent to service, but car stereo and Sony SBH54 are fine.
I've already reported the solution to Sony's tech support.
XZ1 compact here.
No problems with my QC35, also no problem with my old car's bluetooth handsfree system (2005).
4rz0 said:
XZ1 compact here.
No problems with my QC35, also no problem with my old car's bluetooth handsfree system (2005).
Click to expand...
Click to collapse
Old things used to be built better.
Thanks for the QC35 check.
I have noticed delays connecting initially to devices but fine after. I have noticed connection issues though with the new "near bluetooth" protocol. I can't connect to a Roomba Braava Jet at all.
Just found this, trying to test as we speak.
https://talk.sonymobile.com/t5/Xperia-XZ1/Streaming-Bluetooth-audio-in-car/td-p/1264728/page/2
I have no problems using my xz1 with my srs-x11 and my peugeot 208 Bluetooth system. Mine works fine
XZ1 Compact Bluetooth complete failure
I have issues with all Bluetooth devices I regularly used with my previous phone. That includes a few portable bluetooth speakers like Ion Plunge or Philips PixelPop (connects but music does not play, hit or miss, had to forget and reconnect the devices manually almost every time), 3 different brand car bluetooth handsfrees including Volkswagen Go! bluetooth system, Opel Vauxhall integrated bluetooth, Renault Traffic integrated bluetooth. On car bluetooth either information is not displayed on the screen or device cannot be controlled from the car controls, sometimes when autoconnected to Volkswagen Go I see mute sign on the screen when my phone is not muted and music supposed to be playing. So much frustration considering that I got used to not having any issues with my old iPhone that I personally hated for many other reasons.
In case you guys haven't seen yet, there's various fixes coming with android's november update that should address most, if not all of those issues.
EDIT: I stand corrected, the mentioned updates are for the Nexus/Pixel devices, though I'm sure they'll be integrated into the Xperia device's software as well eventually.
I don't know where to put this, but this is the first thread that shows up on Google so I'll put it here.
I have had nothing but issues pairing my phone to the radio on my Hyundai Elantra. The headunit would report that it pairs successfully, but my XZ1 compact would never actually connect. Eventually "ELANTRA" would appear in my phone and the only Bluetooth feature available is Contact Sharing.
A few weeks ago some random method of me pairing and unpairing got it to work and I left it alone. I recently had to wipe my phone and start over, so I had to figure out how to pair this stupid thing again. I took note of what I did so I could share for others (and for myself when I have to wipe my phone in the future).
Delete all stored devices on your phone and headunit, and then go through the pairing process again. At the moment you successfully type in the Bluetooth pin code and hit pair, kill the power to the headunit. In my case, the radio lady was in the middle of saying "pairing complete" when I turned the key off.
The phone should switch from "Pairing" to "connecting", at which point you can turn the key back on. It should finish pairing and connect.
Hopefully this helps someone
I have a plantronics BT headset paired to my XZ1 compact and it kept disconnecting and reconnecting the next second. Sometimes the BT would show that is is connected but when i make a call, it isn't connected to the BT headset. I emailed support and follow their instructions below and still have the same problem, anybody experiencing the same? Hope there is a solution to fix this problem soon.
Thank you for contacting the Sony Xperia support centre.
With regards to your query, kindly be advised to switch your phone to the safe mode, under the safe mode, please reset your Plantronics BT earphone and pair with the phone again.
If the device performance improves in safe mode, it’s likely that one or more downloaded applications are affecting the device negatively. You can exit safe mode and restart the device to uninstall the application or applications you suspect are causing the problem. If the problem is recent and you’re not sure which application is causing the problem, you can start by uninstalling the most recently downloaded application.
To enable Safe mode
1. While the phone is on, press and hold down the power key.
2. In the pop up window, touch and hold Power off until the Reboot to safe mode message appears.
3. Tap OK to reboot in safe mode.
To exit Safe mode
• When in Safe mode, restart the phone.
If the issue still persist under the safe mode, kindly be advised to perform a software repair by using the Xperia Companion.
To do this, you will need to install Xperia Companion from the Sony Xperia website. Please perform a backup first if your phone is able to on. Please follow the steps below to do this:
1. Go to http://www.sonymobile.com/global-en/
2. Select Support
3.Click on Xperia companion
4.Look for " connect to your computer
5.Click on" Download for windows "
System requirements:
• Broadband connection
• Intel Pentium 4 or equivalent AMD processor
• 5 GB free hard disk space
• 2 GB RAM
• 1 available USB 2.0 or USB 3.0 port and USB cable
• Microsoft Windows 7, Windows 8(8.1 or Windows 10
• OSX 10.8 (Mountain Lion) or above
Note! There will be no support for Windows XP or Vista
To do a Backup, click on the "Backup" icon and follow the steps accordingly.
1) Click Backup to start
2) Xperia Companion will prompt you to name a new backup set. If an existing backup is available the data will added to the existing backup set. Click OK, to save the file name
3) Xperia Companion is able to backup personal data and media. Click the arrow to expand the My Data selection. Click Next to start the backup.
My data – Contacts & Call log, Calendar, Text messages and Others
Camera – Photos and Videos
Music – Music
4) Xperia Companion will request a password to be set for the backup files. This is optional unless the device is encrypted. If encrypted this will be mandatory. Click Next to progress.
5) Once the application has complied a backup the progress will automatically move onto the next window. Xperia Companion will notify that the backup has been successful. Click to Done to complete the process.
To do a Software Repair, just click on the "Software Repair" icon and follow the steps accordingly.
1) Click Software Repair to start
2) Xperia Companion will advise of Google Theft Protection risks. You must acknowledge that you know your details before process to the next step. Tick Yes to progress and then click Next.
3) You will be warned that all your local stored data will be removed. Tick I understand follow by clicking Next to progress.
4) Xperia Companion will download the Update Engine application. This application will run in background and you will not see the service. The service will progress automatically. The progress will vary depending on internet speeds. Once the Update Engine has been installed, you will be requested to connect your device. You must follow the steps for Xperia Companion to detect the device.
5) When the device has been detected the application will automatically move to the next step. Click Next to progress. When the repair has been completed, Xperia Companion will progress and confirm a successful repair. Click Done to complete the process.
Thank you for contacting the Sony Xperia support centre.
With regards to your query, we suggest you to forget the Bluetooth pairing and clear data of the Bluetooth app by going Settings > Apps & notification > Apps info > tap on 3 vertical dots on top right hand corner > Show system > Bluetooth > Force stop > OK > Storage > Clear cache and clear data and try again.
If problem persists, we suggest you to try reset network settings and try again and monitor it.
To clear all connection data
1. Find and tap Settings > Network & Internet.
2. Tap the menu button (three vertical dots) > Network settings reset > RESET SETTINGS.
Like the others I also have problem with the Bluetooth after updating to Android 9 on my XZ1.
The problem is on my car Head unit, I can play song thorugh Bluetooth without any problems but when I receive a phone call or make a call although Bluetooth is still turned on but the voice come from the phone and sometimes it switches between the head unit and the phone repeatedly so I have to turn the Bluetooth off and answer the phone. About Bluetooth Avrcp which is on 1.6, some said if you put it on 1.4 might fix the problem but it didn't. And I also checked the avrcp For Android 8 is also on 1.6 and I never had such problems on Android 8. This all happened after updating to 9.
It's been months I'm searching for a solutions and I'd be grateful if someone could help.
Anyone having problems with constant disconnects with android auto?
I have latest UK firmware installed along with the latest android auto and waze on my phone.
I can connect fine , sometimes I can drive 30 minutes without a disconnect, other times it is 5 minutes.
The only way I can get it working again is if I unplug the phone from the car and reconnect.
Then this happens again.
I have not made a journey yet where the phone has not disconnected at least once.
My old phone (nokia 8) never had this problem.
Im using a good quality USB cable.
Any ideas of which settings I need to change to help this issue?
Try using the phone manager app's battery settings to set Android Auto and Waze to manage manually as to me it seems that the battery management's the issue.
Sent from my Mate 20 Pro using Tapatalk
Works fine for me, using Waze/Spotify most of the time. Using default battery optimization for Android auto.
I'm using a Huawei cable.
You could try to the one coming with the phone to test.
Hi ,
Thanks for the replies.
Im using the cable that came with the phone in my car and it still has the same problem.
I changed the settings to manage manually, but again I plugged the phone in to my car and it stopped working after 5 minutes. I had to unplug and start again before the car would see the phone again.
There are 3 sets of settings in the manage manually option. did you change any of these?
Should say that im plugging into a vauxhall Astra 2017 car with the latest software installed on my car.
Thanks again for any help.
I've only had my UK Mate 20 Pro for about 3 weeks now, but I too am having issues with Android Auto. Initially I was getting disconnects, I think this was due to the handset trying to ask me how I wanted the USB connection to be treated - charge only, transfer files, MIDI device etc. It didn't seem to matter what I chose, it always flicked back to charge only. Or, it could have been down to the third party always-on-display app(s) that I was trialling and have since deleted.
The disconnects now seem to have stopped and it's more stable for me - I don't know why, it could due to the above deletions or a recent EMUI update (I'm on 9.0.0.210), or maybe Android Auto updated?
I now have different issues with AA, in that when I connect the handset and the Android Auto home screen comes up, there's no play button showing for my Audiobook app (Listen Audiobook Player), when I click into the app and click the play button it stays on 'getting your selection' forever and nothing plays. Incidentally I can start playing a book on my handset, but AA doesn't notice that anything's changed and stays on the 'getting your selection' screen.
The only way I have found to return functionality to normal is to restart the phone and enter my pass code - this takes me back to the phone desktop and a different error message which says 'android auto can't find any supported devices to use' (or something similar), when I unplug and re-plug all works as it should again - this is all a bit of a pain to do whilst driving, or requires me to park up.
Additionally I have noticed similar issues when switching audio apps i.e. to Spotify and then to an audiobook etc., It doesn't seem to go smoothly like it used to on my S8+
I'm using a 2017 Vauxhall Astra also ?
Ive sent a message to customer services to see if they can offer any help.
Dont know if we will have to wait for a firmware update to sort this out?
Same every single time. Did a 120 mile trip today and had to disconnect and reconnect 7 times
andywright1982 said:
Same every single time. Did a 120 mile trip today and had to disconnect and reconnect 7 times
Click to expand...
Click to collapse
Do an factory reset and try it again. See if it works.
Verstuurd vanaf mijn LYA-L29 met Tapatalk
Hi, Can you all please share the model of your car ? Maybe the issue is also connected to the car, not only the M20Pro. Thank you.
My car is a vauxhall astra.
I know it is not the car at fault as my last phone which was a Nokia 8 running android pie worked fine without any disconnections.
pau1777 said:
My car is a vauxhall astra.
I know it is not the car at fault as my last phone which was a Nokia 8 running android pie worked fine without any disconnections.
Click to expand...
Click to collapse
Same car. Used a samsung a9 yesterday and worked flawlessly.
Done a factory reset on the mate and still ****s up. If it wasnt such a good camera I would be getting a different phone
I tried it on a Mercedes CLS, just for a short run. It worked fine. With non-official Huawei Cable. Just basic USB-C. Maybe I need to try for a long run to be sure about it.
Anyone tried it on a Volvo XC40-60-90 ?
Disconnects
Did you find a solution to this? my device also suffers from constant disconnects and sets the USB method to charge only and as soon as you change it just goes straight back. battery management is set to manual and all apps and phone are up to date. using it on a Vauxhall insignia 66 plate with OEM cable.
Hey guys,
The problem seems to be with a nearly full battery.
When the battery is >=92% the connection of AA drops very often.
Is anyone here with EMUI 10 to test if it's more stable?
EDIT: I've missed that today is the launch of the beta so forget my question.
Edit2: some links for the same topic.
https://support.google.com/androidauto/thread/15209528?hl=en
https://www.android-hilfe.de/forum/android-auto.3315/android-auto-verbindungsprobleme-bei-akku-ladung-ueber-90.920529.html
Currently on stock, non-rooted rom. Just restored from my smart switch backup but something was changing my ringer mode (from sound to vibrate) at random times. So, I downloaded NiceCatch in order to identify what process is doing it. When it occured, I checked NiceCatch and it says it was the AS.AudioService.onSetStreamVolume process that set ringer mode to vibrate then back to sound. Sometimes it sticks to vibrate only and I often miss calls. Any ideas how to stop this? I've already checked Bixby Routines, DND, Easy Mute, and SmartThings. They're all turned off and their not scheduled to turn on. This was not happening before the smart switch backup (I've reset the phone because I was having touch issues, turns out it was just the screen protector.)
Try clearing the system cache.
SmartSwitch can transfer the problems along to the new load. Don't use it if you can't ID the issue.
Never trust SmartSwitch as a stand alone backup for critical data as it can fail you miserably.
Done clearing the cache partition in recovery. I've also disabled all DND permissions from all apps in the settings. Let's see if it still happens. I'll post the screenshot here again from nicecatch if it still happens. If this still keeps happening, I guess I have no choice but to start from scratch. What a pain.
Yeah, I've learned not to trust smart switch ever again. Quite sad, in my opinion, it was actually better than google's backup and restore. Can you recommend some backup and restore apps? Best one I've used is Nandroid backup from TWRP. But it is only for phones with custom recovery though.
blackhawk said:
Try clearing the system cache.
SmartSwitch can transfer the problems along to the new load. Don't use it if you can't ID the issue.
Never trust SmartSwitch as a stand alone backup for critical data as it can fail you miserably.
Click to expand...
Click to collapse
Helium but it's sort of a pain. Never did a restore with it.
I just make redundant backups and load 'em the hard way. I used SmartSwitch to transfer homepage settings on my N10+'s although I accidentally included apps. I'm using Android 9 on one and the newest is running on 10.
SmartSwitch worked well... who knows?
Regardless I know not to trust SmartSwitch
As the name suggests, this is part of the Android Audio Service and it is a perfectly legitimate part of the OS. Unfortunately, the cause is going to be nigh on impossible to find out without a stack trace as the service is being called by something else and NiceCatch won't tell you that. onSetStreamVolume is a function that is called when something is adjusting the volume, be it an app or some hardware interaction. An audio/video app or another part of the OS can make this call. Hardware could be the volume buttons, inserting or removing headphones (or a faulty headphone socket thats mimicking insertion or removal) or a third party device connected to the phone such as Bluetooth headphones or a smart watch. Try disconnecting any Bluetooth headphones and smart watches and see if it happens without them connected. Disable any related apps for those devices too and see if it still occurs (update them if available). Since you have NiceCatch you must have Good Lock and that offers you SoundAssistant. If that's installed, try disabling and updating it and seeing what happens. Disable/update any audio/video apps and see if it occurs. My best guess is that because used Smart Switch, you may have restored an app thats no longer compatible thats making erroneous calls to the function. Thats all I can think of right now. It seems you have a lot of trial and error to do!
richhaynes said:
As the name suggests, this is part of the Android Audio Service and it is a perfectly legitimate part of the OS. Unfortunately, the cause is going to be nigh on impossible to find out without a stack trace as the service is being called by something else and NiceCatch won't tell you that. onSetStreamVolume is a function that is called when something is adjusting the volume, be it an app or some hardware interaction. An audio/video app or another part of the OS can make this call. Hardware could be the volume buttons, inserting or removing headphones (or a faulty headphone socket thats mimicking insertion or removal) or a third party device connected to the phone such as Bluetooth headphones or a smart watch. Try disconnecting any Bluetooth headphones and smart watches and see if it happens without them connected. Disable any related apps for those devices too and see if it still occurs (update them if available). Since you have NiceCatch you must have Good Lock and that offers you SoundAssistant. If that's installed, try disabling and updating it and seeing what happens. Disable/update any audio/video apps and see if it occurs. My best guess is that because used Smart Switch, you may have restored an app thats no longer compatible thats making erroneous calls to the function. Thats all I can think of right now. It seems you have a lot of trial and error to do!
Click to expand...
Click to collapse
Spot on.
Little doubt SmartSwitch is capable of doing this. Most times it just won't reload the app. Or it may have transfer another hidden setting?
3rd party apps can alter hidden user settings on stock phones that do not revert back even if you uninstall the app. This is rare but it happens. Saw a Google book reader app do this. Had to reinstall it, change the display setting, then finally uninstall it for good. With some patience and persistence many times you can track a hidden settings issue down and avoid a reload.
I prefer a doing clean load especially if malware caused the need for a reset. A Android load can lasts for years if you load it right and leave it be.
It's worth doing it right the first time...
blackhawk said:
Spot on.
Little doubt SmartSwitch is capable of doing this. Most times it just won't reload the app. Or it may have transfer another hidden setting?
3rd party apps can alter hidden user settings on stock phones that do not revert back even if you uninstall the app. This is rare but it happens. Saw a Google book reader app do this. Had to reinstall it, change the display setting, then finally uninstall it for good. With some patience and persistence many times you can track a hidden settings issue down and avoid a reload.
I prefer a doing clean load especially if malware caused the need for a reset. A Android load can lasts for years if you load it right and leave it be.
It's worth doing it right the first time...
Click to expand...
Click to collapse
Smart Switch isn't as smart as its title suggests. For about 80% of the apps I have installed, it only backs up the APK for the app but not the app data itself. Yes it will install all my apps on mass but I still have to set each app up individually afterwards. That makes it a useless solution. I might as well install them all fresh from the Play Store so that they are up to date too. There are some third party apps that get data backed up along with all the Samsung apps but I find virtually all games reset unless the game itself saves a cloud backup. I've never had any apps be faulty after a restore but I've only done it twice personally and I've heard plenty of horror stories from others to know its bad.
As for OP, it could be a strange setting on a smartwatch that triggers it. I can silent my phone from my watch and if it developed a bug then it could cause a situation like OPs. I'm still betting on it being a dodgy Smart Switch restore but it will take days for OP to pinpoint what actually caused it.
richhaynes said:
As the name suggests, this is part of the Android Audio Service and it is a perfectly legitimate part of the OS. Unfortunately, the cause is going to be nigh on impossible to find out without a stack trace as the service is being called by something else and NiceCatch won't tell you that. onSetStreamVolume is a function that is called when something is adjusting the volume, be it an app or some hardware interaction.
Click to expand...
Click to collapse
Ahh okay. This will be tough to trace then. I wonder if this can be traced via system tracing in developer's option. It did include system tracing for audio. I don't know what program does it need though in order to read the logs.
richhaynes said:
An audio/video app or another part of the OS can make this call. Hardware could be the volume buttons, inserting or removing headphones (or a faulty headphone socket thats mimicking insertion or removal) or a third party device connected to the phone such as Bluetooth headphones or a smart watch. Try disconnecting any Bluetooth headphones and smart watches and see if it happens without them connected.
Click to expand...
Click to collapse
Also, I did have my screen replaced recently. I did it myself, it was a reglassed screen from China (Screen with frame). Works perfectly fine though. I tested all the functions on Samsung's testing menu thing (*#0#*). All functions seem to be working fine. Except for the Grip Sensor. It doesn't seem to work correctly. It used to say "Release" when the phone was not being held and "Working" when the phone was held. Not really sure what this Grip sensor does. While being inside the phone, I also replaced the thermal pad with Thermal Grizzly's Kryonaut (Non conductive thermal paste). Though I doubt this would cause this to happen. It improved thermals indeed compared to stock.
Anyways, after the screen replacement (before the backup and restore in smart switch), I had no issues with the ringer mode. It only started occuring after the restore on smart switch.
As for the bluetooth, I use the Xiaomi Mi Band 6. Including its Mi Fit app. I tried uninstalling the app to see if the issue still occurs. It still does. So I guess it wasn't due to this app.
richhaynes said:
Disable any related apps for those devices too and see if it still occurs (update them if available). Since you have NiceCatch you must have Good Lock and that offers you SoundAssistant. If that's installed, try disabling and updating it and seeing what happens.
Click to expand...
Click to collapse
Yes, I have disabled several apps to test if the issue was gone. I also tried updating them to their newest version. Unfortunately, it still occurs from time to time. I also have SoundAssistant installed. But even though I cleared its data and cache, the problems still continues. I guess it wasn't due to this either.
richhaynes said:
Disable/update any audio/video apps and see if it occurs. My best guess is that because used Smart Switch, you may have restored an app thats no longer compatible thats making erroneous calls to the function. Thats all I can think of right now. It seems you have a lot of trial and error to do!
Click to expand...
Click to collapse
Oh okay. But upon backup and restore, I never updated the phone though (November 2021 Security Patch). So I doubt there is some compatibility problems. Maybe smart switch is just buggy. I also did some research about this issue and it turns out, it also occurs to other samsung models (S21). This seems to be a bug from smart switch that samsung hasn't fixed yet. I guess if all else fails, I have no choice but to completely start from scratch. It'll surely be a pain though because I use a lot of apps.
Thanks for the tips though. I really appreciate your reply.
I've used system tracing but not for the audio component so I'm not exactly sure what its output would be. The system traces can be viewed through Android Studio and can be very technical. If your used to debugging kernel logs you will be at home as they can be just as cryptic!
One wild thing that I'm thinking now is that the headphone socket got damaged when you replaced your screen and its triggering as if you plugged in your headphones. I'm not sure how that would result in your phone going in to vibrate but it would certainly trigger activity within the Audio Service as it contains code to check the volume limiter which is specifically for headphones. Its a possibility to consider but a wild one at that.
The grip sensor is a sensor that notifies anything that needs to know when your holding your phone. Its one of the things Samsung Health uses to guess when your asleep or not. I dont know how Sammy actually do it but I'm guessing its going to be from slight current changes on the edge of the digitizer as you grip your phone but thats a wild guess too! As for the test, the release message is a message to tell you that you need to release it not to say your currently holding it. Its a bit strange to us because you think it would say gripped or ungripped or something but its messages for a human or robotic tester, not for us.
I've not heard about Smart Switch being an issue on the S21 but I didn't get that model so I've not really read much on the issues it suffers from. Unfortunately Smart Switch is just not reliable as a backup solution. Use it to backup you content and settings but don't rely on it for backing up your apps. You need root otherwise its a manual job I'm afraid.
richhaynes said:
I've used system tracing but not for the audio component so I'm not exactly sure what its output would be. The system traces can be viewed through Android Studio and can be very technical. If your used to debugging kernel logs you will be at home as they can be just as cryptic!
Click to expand...
Click to collapse
Ahh alright. My understanding of Android software isn't really that great. I'm only self learning. I guess its better to start clean.
richhaynes said:
One wild thing that I'm thinking now is that the headphone socket got damaged when you replaced your screen and its triggering as if you plugged in your headphones. I'm not sure how that would result in your phone going in to vibrate but it would certainly trigger activity within the Audio Service as it contains code to check the volume limiter which is specifically for headphones. Its a possibility to consider but a wild one at that.
Click to expand...
Click to collapse
Headphones are completely working though. Both left and right, including the volume up, down, play/pause controls on the earphones. Headphone detection is working fine. If there was a problem with the headphone jack, there would be no sound coming out from my phone speakers or atleast it would be intermittent. But thats not what really happens on my phone.
richhaynes said:
The grip sensor is a sensor that notifies anything that needs to know when your holding your phone. Its one of the things Samsung Health uses to guess when your asleep or not. I dont know how Sammy actually do it but I'm guessing its going to be from slight current changes on the edge of the digitizer as you grip your phone but thats a wild guess too! As for the test, the release message is a message to tell you that you need to release it not to say your currently holding it. Its a bit strange to us because you think it would say gripped or ungripped or something but its messages for a human or robotic tester, not for us.
Click to expand...
Click to collapse
The grip sensor is located on the frame of the phone. It has a touch sensor chip located on the charging board module. It makes contact with contacts on the frame. I first thought it was for the wifi/cellular antennas, but then I noticed that antenna cable traces on the charging board PCB led to a signal amplifier chip which then leads to contact pins connecting to the speaker/wireless charging coil plastic piece (which probably serves as the antenna). My grip sensor is probably not working because the pin was not making contact with the frame part. Probably 'cause of corossion or some dirt. Maybe I need to scratch up the part where the pin connector touches the frame. I'll try to get this fixed soon if I ever need to open up the phone again. I kinda already sealed it up with a new water resistant seal. Its gonna be a pain to remove and replace again just for the grip sensor.
richhaynes said:
I've not heard about Smart Switch being an issue on the S21 but I didn't get that model so I've not really read much on the issues it suffers from. Unfortunately Smart Switch is just not reliable as a backup solution. Use it to backup you content and settings but don't rely on it for backing up your apps. You need root otherwise its a manual job I'm afraid.
Click to expand...
Click to collapse
Yeah. I decided I'm gonna start again from scratch. Instead of doing all the trouble finding out whats causing this problem. It went bonkers again last night and early morning. I give up. I decided to reset the phone and reinstall all of the apps. Its going to take a while for sure. I would still back up my current data using smart switch though. Just in case it still occurs even after a full factory reset.
Be aware the issue may return if you don't find the root cause. It's likely a 3rd party app or a settings issue. It's always better to find the root cause. Malware is also a possibility in which case a reload will kill it.
You can use ApkExport to make installable app copies in the future, no need for Playstore then on reloads. Available on Playstore.
blackhawk said:
Be aware the issue may return if you don't find the root cause. It's likely a 3rd party app or a settings issue. It's always better to find the root cause. Malware is also a possibility in which case a reload will kill it.
You can use ApkExport to make installable app copies in the future, no need for Playstore then on reloads. Available on Playstore.
Click to expand...
Click to collapse
Already done factory resetting the phone. And freshly installed all the same apps from the play store (also individually set them up). I also only used smart switch to restore my contacts and messages. Did not use it to restore settings and apps. All good so far. No more annoying ringer mode switching. So that confirms it then, it was indeed a bug in smart switch.
Aries2376 said:
Already done factory resetting the phone. And freshly installed all the same apps from the play store (also individually set them up). I also only used smart switch to restore my contacts and messages. Did not use it to restore settings and apps. All good so far. No more annoying ringer mode switching. So that confirms it then, it was indeed a bug in smart switch.
Click to expand...
Click to collapse
Lol, SmartSwitch is a Pandora's box of trouble.
I would also use the backup feature in Contacts to create an export backup file. This is important to have.
Its back again. Huhu.
Seems to occur less frequently now though. Tried doing setting up some automation on sound assistant to see if it was the one thats changing the ringer mode. But its process can clearly be seen by Nicecatch. This is really starting to bug me. I've already done a factory reset and reinstalled all my apps fresh from the play store.
I've tried plugging a headset with volume control and tried changing the ringer volume over there. It still says audioservice but the process is different. Its the checkforRingerModeChange process. Not the onSetStreamVolume.
Update: I've decided to open the phone again and fix the grip sensor. Grip sensor probe is marked Red. It connects to the lower portion of the aluminum frame. Those "antenna bands" on the aluminum frame are not actually antenna bands. They are plastic molded spacers to separate a piece of aluminum (sky blue) from the side aluminum frame. The lower piece of aluminum is then connected to the probes of the grip sensor IC (located on charging board and as well as on the top of the motherboard). There are also two grip sensors. One at the top and one at the bottom. But on the test menu, only the test for the bottom one is present. (Newer models have test for top and bottom grip sensors). When I touch the bottom probe, grip sensor test becomes "working". Therefore there is no problem on grip sensor circuits. Problem is on brand new frame I installed, I had to scratch the part where the probe makes contact on the frame and viola, grip sensor works now (I also scratched the top grip sensor probe contact). Yellow marked ones are wifi/cellular/gps antennas. They're present as well at the top.
I wonder if the grip sensor was the one triggering AudioService.onSetStreamVolume. I'll just wait and see if it still occurs after this.
2nd update: Its still here.
3rd update: Updated to March 2022 update. Issue completely gone.
Glad for you but I've never used smart switch and my m30 already saw the endo of the updatos, amigo!