MIUI 7 and Android Wear problem - Moto 360

Phone is Redmi Note 2, smartwatch is Moto 360.
Devices are paired but Bluetooth keeps disconnecting after a while - on smartwatch i have an icon of a cloud with strikethrough. Restarting and re-pairing helps but also - for a while.
I know this is MIUI problem because on unnofficial AOSP this problem does not exists.
Reported this in the bugs section on official MIUI forum but maybe someone knows some workaround. They don't seem to care much :/
Clean install of MIUI 5.10.15
Please help!

Related

New Body app and Watch faces not working

I've updated to the new Connect app, and the app on the phone works fine, but none of the new features will sync to the watch. I've tried restarting the watch, resetting the watch, uninstalling and reinstalling both Android Wear and the update to the Connect app (on a Moto X, so I can't fully uninstall Connect).
Anybody seeing this? Maybe I need to do all that in a particular order?
I am having the exact same issue. Using a Moto X 2014. The app updated and works on thr phone but none of the new features will sync
In the same boat as well...
Same with me. Running lg g3. I've read the issue is the phone that your 360 is connected with. Some people paired their 360 with a different phone and then the new watch faces finally appeared. But once they would try to pair their 360 back to their current phone, the watch faces would still not show.
No problem here on my Nexus 5
you won't see anything different on the phone after the motorola connect update in terms of the Body app. However, if you go into the start menu on the watch itself, you should see moto body features such as calories, steps, heart activity, and heart rate. hope this is helpful.
Won't work on my S4 either, tried everything. Bummer!!!
Works fine with my s4. Try restarting phone?
ditto
Same issue on my moto x 2013. Can't do anything to get them to show up. Done everything short of a hard reset on the phone
same here, nexus 5 on lollipop
I had the same problem. I use it with my Nexus 5 running an AOSP Lollipop Build.
Solved it by uninstalling the Motorola Connect App and reinstalling. After that everything new appeared on the 360.
Hope this helps :good:
mc-paulo said:
I had the same problem. I use it with my Nexus 5 running an AOSP Lollipop Build.
Solved it by uninstalling the Motorola Connect App and reinstalling. After that everything new appeared on the 360.
Hope this helps :good:
Click to expand...
Click to collapse
Many thanks this worked for me. I was dreading having to do a factory reset.
Edbogue

[Q] navigation not working on 360

Since i bought moto 360 navigation won't work. I tried to reset my watch many times. I even reinstalled Conect apk and Android Wear many times. Also I deleted Chach for booth aplications. But i keep geting notification on my moto 360: check your phone to continue!?!?!
I use galaxy s4 running official kitkat, i updated my 360 to 5.0.1. and i'm using latest google maps (9.2.0) on my s4.
So I was wondering did anyone expiriens same problem? and is there a way to fix this bug?
THX in advanced

[HELP!] "Unfortunately Bluetooth share has stopped"

Somebody HELP!!!!!!!!
I'm running Resurrection Remix LP v5.5.8 on my T-Mobile Galaxy S4 (SGH-M919). I love this ROM, but I'm having a persistent problem with Bluetooth crashing, within minutes of starting up. This a consistent problem, not even remotely intermittent - happens every single time I try to turn on Bluetooth - it shuts itself off, refuses to turn back on again, and on occasion, gives me the error message "Unfortunately Bluetooth share has stopped."
I have tried clearing the Bluetooth share app cache and data to restart - it will then turn back on, but soon turns back off.
The problem was bad enough that I took RR off my phone and tried some other ROMs, including basic CM12.1. I came back to RR because the other ROMs had more critical issues, but they did help me eliminate causes of my problem, in that I didn't have Bluetooth issues with them like I do with RR, and I was still running all the same apps, same devices I was trying to attach, etc.
I've also played with several of the settings in the Kernel Aduitor, including completely shutting off the task killer. No difference - problem persists.
I also tried some of the apps on Google Play that say they're supposed to cure problems like this. Fixed nothing.
Please help. Is there an alternative something that I can flash - Bluetooth driver, different kernel, something, that can fix this issue once and for all?
Got the same problem. Android V6 RR Remix. Any suggestions?
Seems to be a consistent MM ROM issue, currently. Some seem to work better than others on some phones.
Keeping bluetooth working on the S4 seems to be "dark arts". Cyanogenmod has historically had much problems with this too. Some nightlies are okay, then others cause BT to crash. Some don't work at all.
Anyone have any resolution to this issue? I'm having the exact same symptom, but I'm on a different phone.
Note II / T-889, Conch Republic. Might've been from a radio update I did a while back, trying different ones now.
denverjoe72 said:
Keeping bluetooth working on the S4 seems to be "dark arts". Cyanogenmod has historically had much problems with this too. Some nightlies are okay, then others cause BT to crash. Some don't work at all.
Click to expand...
Click to collapse
You might give this AOKP 6 MM ROM a try:
http://forum.xda-developers.com/showthread.php?t=3391994
Users are reporting that after a week of testing the Bluetooth seems to be working rather well.
Sent from my SGH-M919 using XDA-Developers mobile app

Issue Bluetooth car very annoying

Hi,
I have xiaomi mi 10T Pro Global - miui 12.1.5 Global (Android 11)
My big problem is listening to music in the car.
It keeps pausing every couple of seconds and then reconnects.
I looked for some information on the internet. They proposed: put in airplane mode, reboot and format the cell, which I just did. I have not found any benefit.
Now I wait 7 days to have the unlock code sent to me, but it seems drastic as what.
Do you have any advice to help me?
On my Mi10T Pro the OTA update from Android 10 had all sorts of problems and I had to Factory Reset to get it going. Now it mostly works well, including bluetooth completely stable on headphones and car.
chisnz said:
On my Mi10T Pro the OTA update from Android 10 had all sorts of problems and I had to Factory Reset to get it going. Now it mostly works well, including bluetooth completely stable on headphones and car.
Click to expand...
Click to collapse
very lucky you don't update to android 11. A very buggy update

Miui 12.5 issue?

Hi I have recently bought a second hand redmi note 8 pro to use with a drone I have also recently purchased.
everything has been working fine. Until last night 21/07/21 I had a notification of the new miui 12.5 update. which I left to do its thing. The issue is the screen does not respond to touch. it appears to boot up ok gets to the screen shown. I have had it on fastboot screen and also wiped all data (can't seem to get mi assistance to work.)
Has anyone else had the update/ issue?
How would you recommend proceeding.
I have the same problem (Redmi Note 8 Pro Global - MI firmware). After updating from 12.0.8, the touchscreen stopped working.
I had to roll back through the fastboot. I also tried to flash version 12.5.1.0 via fastboot - the problem persists.
The phone had a replacement display module, but with an original one.
There is an idea to try to flash it with a version for Indonesia or China, but so far I have not tested it.
Issue with SIM selection for calling on MIUI 12.5 Global - Redmi Note 8 Pro​
Anyone experiencing this bug with default SIM for call?
The Google Dialer will ask for which SIM to call on reboot even tho I already set it as SIM1 or SIM2 in the Settings.
The workaround is manually reselecting the SIM but only effective till next reboot.
Same exclusive Xiaomi Update Fail Forget about help or information from the official Support.
Connect a mouse with a USB-C to USB Adapter and backup your personal data.
I have exact same issue on this update. I also replaced the screen some time ago. I belive it's android 11 problem, because CFWs like PE doesn't work too. ROMs with Android 10 also seems weird to me, because digitizer keeps "jumping" and clicking random places. Android 9 - all works perfectly fine. I am going to find out which partition is used to use touchscreen and check if it's possible to flash it over PE ROM to solve the problems.
I have some problems after updating to MIUI 12.5.1:
1. Have to repeat the procedure twice for uploading any picture from gallery to anywhere on Internet. It doesn't work in first attempt.
2. Fingerprint sensor shows many errors off & on. 3-4 attempts to open the phone. Tried re-registering my fingers.
3. Option of Completely Hide Notch gone
4. While playing Facebook videos, sound continues, video stops.
Too annoying these bugs are.
AlphaBravo said:
I have some problems after updating to MIUI 12.5.1:
1. Have to repeat the procedure twice for uploading any picture from gallery to anywhere on Internet. It doesn't work in first attempt.
2. Fingerprint sensor shows many errors off & on. 3-4 attempts to open the phone. Tried re-registering my fingers.
3. Option of Completely Hide Notch gone
4. While playing Facebook videos, sound continues, video stops.
Too annoying these bugs are.
Click to expand...
Click to collapse
5. Battery drain ("...even on miui 12.5 battery drain too much high...")
Compass.
slashimi said:
I have exact same issue on this update. I also replaced the screen some time ago. I belive it's android 11 problem, because CFWs like PE doesn't work too. ROMs with Android 10 also seems weird to me, because digitizer keeps "jumping" and clicking random places. Android 9 - all works perfectly fine. I am going to find out which partition is used to use touchscreen and check if it's possible to flash it over PE ROM to solve the problems.
Click to expand...
Click to collapse
Just now,i found that the user Wai_Yan
slashimi said:
I have exact same issue on this update. I also replaced the screen some time ago. I belive it's android 11 problem, because CFWs like PE doesn't work too. ROMs with Android 10 also seems weird to me, because digitizer keeps "jumping" and clicking random places. Android 9 - all works perfectly fine. I am going to find out which partition is used to use touchscreen and check if it's possible to flash it over PE ROM to solve the problems.
Click to expand...
Click to collapse
Yes, the great manufacturer has kept its information behind the mountain. I have just found a contribution to this in the mi community.
It only briefly mentions that repairs should be made with an official display. I also do not understand why Xiaomi makes such a secret of it and does not give the reasons. Link
I have installed the Global 12.0.5 Stable QGGEUXM and I am also aware of these display anomalies.
Do you have any results in the project?
Boo-Kah-Kee said:
Just now,i found that the user Wai_Yan
Yes, the great manufacturer has kept its information behind the mountain. I have just found a contribution to this in the mi community.
It only briefly mentions that repairs should be made with an official display. I also do not understand why Xiaomi makes such a secret of it and does not give the reasons. Link
I have installed the Global 12.0.5 Stable QGGEUXM and I am also aware of these display anomalies.
Do you have any results in the project?
Click to expand...
Click to collapse
I've tested all partitions but any of them seems to be changing display driver. So sorry, no luck there, I think we're stuck with android 9. It looks like it is hard-coded into firmware.
slashimi said:
I've tested all partitions but any of them seems to be changing display driver. So sorry, no luck there, I think we're stuck with android 9. It looks like it is hard-coded into firmware.
Click to expand...
Click to collapse
I noticed a break in a layer of the display within 14 days of use. There was no heavy use or pressure on the display. Xiaomi - K.O.
How to bring back the option of "Completely Hide the Notch" in MIUI 12.5.1?
I have just realised I didn't update. I was having lots of trouble fixing this. I think my reply from xiaomi was wait for the next update this might fix it.
Thank you to Boo-Kah-Kee, I never knew you could plug a mouse in.
anyway I eventually got it back to the prievious rom by following this Video.
No more updates it works fine.

Categories

Resources