Hi Everyone
I had my XiaoMi Mi 8 since Aug 2018 (brought in China).
My XiaoMi Mi 8 phone is running the original/stock Chinese ROM, with latest updates whenever availiable.
Google Play Store was not availiable when I brought the device, but I have found ways to install Google Apps on it.
I have fully working Gmail/Google Maps/Google Calendar etc on it.
Sept 2019 I brought a Mobvoi TicWatch Pro smart watch that is running Wear OS.
I've tried setting up/linking them but failed.
I've link the phone and watch via Bluetooth
I've download Wear OS app on my Mi 8 which is the app that you need to setup/link the watch and the phone.
I've got to the point where on the phone ask you "Choose which Google Account to copy to your watch", I've select an account, click Next
then the screen is just stuck on that screen that won't go any further (not crashed as the loading blue circle is keep going round)
I have tried many time but it got stuck everytime at this same place.
Since then, to a point I gave up, and tried to setup on an older phone OnePlus 3 (brought in the UK).
The setup went smoothly without any hitch.
I have used the smart watch with OnePlus 3 til today.
It wasn't ideal because OnePlus 3 is an old phone, the battery life is very short now.
And I use smart watch to record my hiking/exercises, which sometime have to be multidays outdoor without charging between.
So, now its Xmas and I have a bit more time to look at this problem.
I wonder if anyone have both Mi 8 and a Wear OS smart watch that experienced problem setting up on it?
I have search a bit on the internet and some says that the Wear OS don't like the phone's Chinese ROM
Would a Global ROM solve this issue?
Any advice/suggestion welcome.
Many Thanks in advance & Merry Xmas
Andy
If no one else is having the same problem
Would flashing a Global ROM solve this kind of problem?
Many Thanks
Andy
I'm not sure if this has to do with recent updates to Android Auto or if it's specific to the make and model of my device (I got the new phone around the same time as the latest AA updates were released), but I'm now experiencing endless frustrations with constant connection failures between my phone and my Jeep's Uconnect 8.4 head unit again. I went through a similar thing, as did many others, around this time last year and the year before. It's infuriating.
Most of the time, when I plug my phone into the vehicle's USB port, the Android auto icon appears on the display of the head unit for a moment or two and then disappears. There's a notification in the shade on my phone that says something like "Connecting to Android Auto" or "Starting Android Auto." But then it never really starts.
Occasionally I try clearing the data, storage and cache from the Android Auto app and sometimes Google Play Services. Sometimes I'll also have to go into the Uconnect settings menu and tell my head unit to "Forget device." Every so often, as long as I then turn off the ignition and then restart the vehicle and then reboot my phone, this will bring me back to the Android auto setup screen and I'll be able to use Android auto for a single drive cycle. as soon as I cut the engine and unplug my phone, it's over. When I get back into the vehicle I'm back where I started: with the head unit seemingly able to recognize that an Android Auto device is connected for a moment and then Android Auto just quits out.
It's insane. Seems like Google can't just get this right. As soon as they release a build that works, they follow up with an update that completely breaks functionality.
Anyone else have a similar experience and, hopefully, have suggestions and how to resolve this nonsense?
Used my iPhone with my 2018 Challenger for a year and it worked perfectly. Switched to a Note 20 Ultra last month and it worked for about 2 weeks. Same issue you're experiencing. I'm going back to iPhone.
I've found that my phone has *the most annoying bug* with Android Auto - AA will work absolutely fine when you connect the phone, but then freezes / stops responding as soon as the phone's screen timeout expires and the phone auto-locks.
AA doesn't freeze, when using the same cable and same car, if I swap the phone to being my OnePlus 8 Pro - which suggests this is definitely a Find X3 Pro issue
(I'm on the 15 firmware, and at the moment can't get it to update, no matter what I do)
@stuclark
I'm on a UK unlocked device and mine won't update either . Still on A15.
That said I tested AA for 2 X 30min trips ( WFH still ) and did NOT have this bug .
I have seen it mentioned in Oppo advert threads on Facebook , they responded each time saying they were aware and working on it . So far I do not put much faith in their updates though.
mgbosshogg said:
@stuclark
I'm on a UK unlocked device and mine won't update either . Still on A15.
That said I tested AA for 2 X 30min trips ( WFH still ) and did NOT have this bug .
I have seen it mentioned in Oppo advert threads on Facebook , they responded each time saying they were aware and working on it . So far I do not put much faith in their updates though.
Click to expand...
Click to collapse
Thanks for the reply - I guess we'll wait to see what the firmware update brings (I've tried uninstalling and re-installing AA, but that doesn't downgrade me to an older version I can use). I'll have a go on facebook and the ColorOS forums
@stuclark . Probably worth opening ticket on chat / Twitter DM with them so they are aware. The more the better.
Not surprisingly, the answer from Oppo is:
It's an Android Auto bug. It will be fixed when they release a new version. Until then, set the screen to stay on whilst the phone is charging (in developer options)
Yup. Welcome to Oppo.
Seems the bug has been present for the year the X2 has been out. So dont hold your breath on a fix.
For me it worked to shut down the always on display function
stuclark said:
I've found that my phone has *the most annoying bug* with Android Auto - AA will work absolutely fine when you connect the phone, but then freezes / stops responding as soon as the phone's screen timeout expires and the phone auto-locks.
AA doesn't freeze, when using the same cable and same car, if I swap the phone to being my OnePlus 8 Pro - which suggests this is definitely a Find X3 Pro issue
(I'm on the 15 firmware, and at the moment can't get it to update, no matter what I do)
Click to expand...
Click to collapse
Try turning off always on display, worked for me.
Good evening I live in France and I test Android auto because some of you have problems with the application and I wanted to know if it was the same with my X3 pro. I use the app for over an hour and don't notice any worries. Good luck to all
P.S: I'm under the latest oppo update with the A17
uzumakinaruto69 said:
Good evening I live in France and I test Android auto because some of you have problems with the application and I wanted to know if it was the same with my X3 pro. I use the app for over an hour and don't notice any worries. Good luck to all
P.S: I'm under the latest oppo update with the A17
Click to expand...
Click to collapse
Thanks for your answer - Android Auto does indeed seem better under A17 than the previous (UK certainly) A15 release.
It also helps to turn off third party navigation apps, such as Sygic or Waze - these seem to exacerbate the Android Auto issues with this phone (but work perfectly on other devices)
Images on the lock screen, crash the Android Auto. It is an OS problem. Here is what to do, till the problem is solved :
-Go to Settings, Security, Smart Lock and and your car a trusted device. That way you have your phone unlocked while driving and fingerprint disappears.
(You can also remove fingerprint from lock screen by going to Settings, Passwords & Biometrics, Fingerprint, Screen-off unlock and select off, but then you have to wake up your phone before being able to use fingerprint)
-Go to Settings, ..Always-On Display, Always-On Display and disable it. (You can also select Always-On Display with battery saver, which turns off image after some seconds, but on those seconds, the Andriod Auto is crashed)
Hello everyone.
I was using UleFone Power 3 (Android 7.1.1) with my RCD330+ without any problems (on VW Golf Mk6 2011 year).
However, phone became old and started developing issues, so I was forced to buy new one.
A few weeks ago I purchased Realme GT Master Edition which runs Android 11.
However, now I am having problems since day one with the phone and RCD330+.
When using Waze, the display on RCD completely freezes for 30-40 seconds every 3-5 minutes. You can pass a few intersections with Waze still showing you frozen far behind. Everything is frozen - map, speed display, etc.
After ~30-40 seconds, it unfreezes and is displayed all fine again for next 3-5 minutes where it freezes again and all repeats.
Could anyone please help me toubleshoot where the problem is?
Only the phone has changed, no configuration changes were done in RCD330+, USB cable also remained the same.
RCD330+ firmware version 5614
Android Auto version 7.6.621703-release
Waze release 4.82.5.1
Another question - what's the best tool to use to switch off Bluetooth after device is being disconnected from USB?
Thank you
I'm having the same problem and I managed to reduce a little bit the freezing. And don't know if it'd work for you.
Enable developers options and go almost to the bottom, under applications there's an option called "Limite de procesos en segundo plano" which might be something like "Limit backgroud processes" and set it to MAX 4 instead of Standard.
It helped quite a bit. Please let me know if you find something else.
Hello everyone,
DEVICE
Xiaomi Mi 9T Pro / Redmi K20 Pro
Custom ROM : Pixel Experience Android 13 ("PixelExperience_raphael-13.0-20221120-1632-OFFICIAL.zip")
Used Apps : Youtube / Youtube Music (I also tried with other media sources on internet) & Maps / Waze
ISSUE
Launching Waze or clicking "Start" the route in Google Maps while playing
a media makes my phone freeze for 1s every 2 to 3s.
This makes listening to music impossible while following the GPS.
(The sound also freezes with the screen)
EXPECTED RESULT
Smartphone not freezing / non-"stuttering" sound.
HOW TO REPLICATE THE BUG
Open Youtube Music and start playing music.
Open Waze (Instantly freezing the sound at regular intervals) or Google Maps, plan a route, then press "Start".
I don't think I've ever needed to play music while opening a Maps or Waze route before so i don't think it is due to an update (I was on PixelExperience 12 the first time I encountered the bug)
Since this summer, I need it regularly, and it is impossible to use both applications simultaneously without the music cutting out at regular intervals which is very annoying.
The problem still occurs even after closing / force closing the 3 applications.
The only way i found to get my music back is to reboot my phone. With this I can use both for a few minutes before the problem comes back.
I hope someone will understand my problem and will be able to help me.
EDIT March 25, 2023 : I have found that the problem does not occur with Mappy, but I still don't know why...
EDIT April 13, 2023 : After a clean flash of the new Pixel Experience Plus version "PixelExperience_Plus_raphael-13.0-20230405-0231-OFFICIAL.zip" from April 5, 2023, everything is back to normal...
I can use Waze again now !
Thanks.
Nyaooom