Related
Hello all,
Most of the time when I connect my Note to my MINI with MINI Connected (Nav, Pandora interface, Vehicle diagnostic interface, etc), it reboots the phone. It's not instant, sometimes the music will start playing, the car will confirm that the phone directory is updated, and I might even receive a message, but it usually reboots at some point. Once it reboots it usually is ok for the rest of the trip, even after disconnecting and leaving the car.
Yesterday, it started rebooting after disconnecting as well; once again, not every time...just did it yesterday at the mall and this morning when leaving my car for work.
This morning after it rebooted when leaving the car for work, I turned off the voice talk "Connect on Bluetooth" option to see if that does anything, but I thought I'd check to see if anyone has heard anything else.
Thanks!
Update:
So yesterday I rooted my Note and loaded Titanium backup and froze some services I thought might be causing issues. NOGO there.
I also repaired the phone as my primary (which syncs the phonebook) phone and with media audio. NOGO.
Next I repaired with just audio. NOGO
This morning I repaired as a secondary phone (no phonebook). So far so good. On the ride home today I'll pair as primary phone again and see if it stays.
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.
I got my Xiaomi Redmi 3 in the middle of october 2016. Since then i've been using it every day. It had minor problems, like music app sometimes turns off by itself, data connection didn't want to turn on only with phone restart, but nothing major, that couldn't be temporarily fixed. But a few days ago i just wanted to browse instagram, i opened the app, and it just turned off instantly. So i tried reinstalling it. Nothing changed. I then tried to install an older version of the app. Still no change. So i decided to leave it be. I was talking to my father, that it should be reflashed because there is something wrong with it. He just pressed regular restart on it, but after that the phone died. I mean it died. It does not respond to charging, connecting to usb, pressing any existing combination of the three buttons. The screen and the status LED does not light up even for a bit. I tried to reflash it anyway with methods specifically for this situation, but it doesn't work either. In the flash tool installation of the rom just does not start. I think it's because my pc does not accept the driver, even from the official website, it just says in the device manager, that it's Android and it has that little yellow triangle. So it is visible for my PC through USB but no driver is accepted. What should i do?
Replace to new phone or carry your phone to customer service, but hey it's xiaomi
This wont help with your phone, but just wanted to leave a note for others. I was having the same issue with the Instagram app. I reinstalled the app, wiped caches, upgraded my ROM, downgraded the app, every tried a entriely differnet ROM. Nothign worked. Instagram would just crash a few seconds after opening. Really weird.
Heres how i fixed it: go to Airplane mode, open the app, logout, turn off airplane mode, log back in.
rarely fc it's okay. but when got often it's a major issue. might be emmc needs to be fixed
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
Backstory
So I was using pixel experience (android version 10) on my Note4x but every time I had to charge the phone, I had to plug in the charger and it would give some haptic feedback and turn the screen on but would not start charging, but restarting the phone with it plugged in would start the charging.
Then yesterday, I restarted it yesterday to start charging and then it showed the google animation and asked for my pattern and and then it showed the google logo but it just got stuck there. After 30 minutes or so, I restarted it again and again but it just kept getting stuck there at that point. And it wasn't even charging, the battery died and it wasn't even booting up even when plugged in.
I plugged it in for the night and in the morning it booted up with full battery but got stuck again at the google logo.
At this point, I got fed up with Pixel Experience and installed the recovery img of MIUI 11 from the TWRP recovery.
And it started the setup but was showing a little message " Find Device Storage Corrupted. Your device is unsafe now " on the bottom and on WiFi setup screen it wasn't showing any connections. and then later in the setup, it asked for the Mi Account details but pressing any button instantaneously responded with " Couldn’t check device Security info, check again in a few minutes ".
I then installed the MIUI 11 fastboot ROM using my computer but it got stuck in the same setup process.
I was stuck there for quite a while but then I later discovered that if you press the forget password button and skip, it lets you boot into the OS.
Issues
Now I'm into my mobile, its working, but
1. WiFi isnt turning on in the dropdown notifications and in settings if you turn it on, it turns off after a few seconds.
2. Fingerprint scanner just immediately refuses to work
3. The camera takes like 5, 6 seconds to jump into the viewfinder and 2, 3 seconds to switch from front to back or back to front camera.
Any sort of help would be appreciated.
rafay_pk said:
Backstory
So I was using pixel experience (android version 10) on my Note4x but every time I had to charge the phone, I had to plug in the charger and it would give some haptic feedback and turn the screen on but would not start charging, but restarting the phone with it plugged in would start the charging.
Then yesterday, I restarted it yesterday to start charging and then it showed the google animation and asked for my pattern and and then it showed the google logo but it just got stuck there. After 30 minutes or so, I restarted it again and again but it just kept getting stuck there at that point. And it wasn't even charging, the battery died and it wasn't even booting up even when plugged in.
I plugged it in for the night and in the morning it booted up with full battery but got stuck again at the google logo.
At this point, I got fed up with Pixel Experience and installed the recovery img of MIUI 11 from the TWRP recovery.
And it started the setup but was showing a little message " Find Device Storage Corrupted. Your device is unsafe now " on the bottom and on WiFi setup screen it wasn't showing any connections. and then later in the setup, it asked for the Mi Account details but pressing any button instantaneously responded with " Couldn’t check device Security info, check again in a few minutes ".
I then installed the MIUI 11 fastboot ROM using my computer but it got stuck in the same setup process.
I was stuck there for quite a while but then I later discovered that if you press the forget password button and skip, it lets you boot into the OS.
Issues
Now I'm into my mobile, its working, but
1. WiFi isnt turning on in the dropdown notifications and in settings if you turn it on, it turns off after a few seconds.
2. Fingerprint scanner just immediately refuses to work
3. The camera takes like 5, 6 seconds to jump into the viewfinder and 2, 3 seconds to switch from front to back or back to front camera.
Any sort of help would be appreciated.
Click to expand...
Click to collapse
Your problem is simply that you installed Pixel Experience 10. The same happened to me last Christmas. The solution was as simple as installing any global stable Miui 8 (it must be marshmallow, for instance Miui 8.2.10.0, which was the last global stable marshmallow) via fastboot, clean installation. At least for me it worked. After that, the issue will be solved and you will be able to install any other Miui version or custom rom. Good luck.
---------- Post added at 01:00 PM ---------- Previous post was at 12:51 PM ----------
By the way. I don't know why, but this kind of issues happens after being using some Android 10 rom. Of course there may be people who haven't experienced such issues after having been using Android 10 custom roms. As far as I know, this remains to be a mistery.