I have just gotten a Desire 10 Pro due to my old Nexus 6 biting the dust recently. I currently use a Asus ZenWatch 3, which worked great with the Nexus but I've hit a problem with the new phone. When its on battery mode, if I turn the screen off, about 10 minutes after this it will cause the watch to disconnect from the phone. Not sure if this is a bluetooth disconnect or the phone is somehow killing the Android Wear app. I've tried to turn off Boost+, set everything that I can seem to find with bluetooth or Android wear to not be optimised but its still doing it.
It doesn't happen when the phone is plugged into the charger, just when its on battery? Any ideas of what I need to do. I would also love to get rid of boost+ but I cant work out how to disable this (guess i need to hit adb).
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
Hello,
The display on my K20 pro is broken, but the device still works (receives calls and notifications).
According to the service lab the battery got swollen and killed the panel from the inside.
It will take 2-3 for replacements to arrive from China.
1. During this time is there a way for me to screen cast my phone somewhere using ADB commands?
I have a lot of important things on the phone I need access to (I'm not using any cloud services by choice)
and can't wait 2-3 weeks...
2. Does anyone know a legit replacement part store with EU stock that get here in 4-5 days?
I found this:
Mirror Android screen with ADB connection wirelessly | MetaHackers.pro
Most of the time, when developer need to showcase their android apps, or mirroring their Android phone onto a screen, they usually use third party apps to do that. Did you know that you can mirror your android phone in your linux desktop through wireless ADB without relying on any
metahackers.pro
Surely that means there must be an easier way to do it over USB?
I will give it a try anyway.
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.