Hi,
I was not able to find similar thread, so here we go.
We might all be aware of previous issues with Poco F1 and AA, many were blaming the notch and Xiaomi promised to have it fixed with Pie release.
Anyway , even after the upgrade I'm facing some issues with the Android Auto and my stock Poco F1.
Setup :
Stock Poco F1 with latest available update (Android Pie). Latest Android Auto from apkmirror.
LeEco Le Max 2 with LineAge OS 13/14 (Android 6) works flawlessly with same setup and same car.
Main issues :
Waze does not detect the location change. Image stays at location you started the app.. Map is shown, seems some online date is still getting in, but .. not OK.
Tried to clean the cache, removing the app, installing it again. Nothing changed, if I use app without AA it works fine. Using latest version from google play.
Google Maps works flawlessly.
Spotify - continues to show no internet connection. If I start manually Spotify on my phone it does work ok on AA.
I have to disconnect the phone, start the app and reconnect to the car and then it works fine. If I don't start Spotify manually it would not work.
I have granted all possible permissions to Android Auto, Waze and Spotify .. unfortunately nothing changed the issues above.
In the same time with my old phone LeEco Le Max 2 with LineAge OS (android 6) and latest AA from apkmirror everything works out of the box.
You simple connect the phone do next, next , grant permissions and it works out of the box.
With Poco I did same thing , also manually added all possible permissions , but still have the issues described above.
What I did so far :
- Tried different AA versions from apkmirror
- Removed and reinstalled AA.
- Waze and Spotify did receive a few updates for the last couple of weeks, so I'm using latest versions.
- Tried with my old phone (it works fine) -
- Cleaning Waze, Spotify Cache
Anyone with ideas or experience of fixing the AA on Poco F1 ?
Are you running AA on your phone, or through your car?
kbagrows said:
Are you running AA on your phone, or through your car?
Click to expand...
Click to collapse
AA does start automatically on the phone once it's connected to the car.
Having the same issues right here.
Poco F1 with latest Android Pie, latest AA from Apkmirror and Audi 2018 car.
Me too same problem on my Poco F1. worked at start....now it doesn't!
find solutions
go to settings --> manage apps --> find waze and disable the battery saver (saver restrictions to none )
this work for me in pocophobe f1
Related
Hi everyone, I'm starting to think that Xiaomi wanted to be like that...I'm using 9.6.22.0 MIUI...
...and my F1 doesn't accept as smart unlock device nothing else than Xiaomi devices (tried mi band 2 it's working), impossible to be recognized handfree devices (tried 2) or bt adapter (tried 3). In all this the funny thing is that Google app recognise and normally permit to add as smart unlock any bt device, but then, no way F1 bt smartlock app, simply don't "see" anything except Xiaomi device
I saw that MIUI in the past has this sad feature....and that it was something about commercial Xiaomi choice.
By the way does someone have the same pb ?
If yes, how did you solve it ?
Thx in advance !
I'm having the same exact problem. My F1 doesn't give me the opportunity to unlock with any bluetooth device. I go to "Unlock with Bluetooth Device" and walk through all steps, and it never "sees" any services to allow me to do this. Very annoying - I like unlocking it automatically when in the car.
Same thing here. It worked fine once, before I reflashed 10.2.2 PEJMIXM. My car stereo is added to smart lock but I still need to enter the pin. No sign of my car device under Unlock with bluetooth device. THis is quite sad, as I remember having similar issues on Miui 8 (Smart Lock wasn´t even implemented). I thought that by now Xiaomi would have addressed the issue. I was hoping not to have to flash a custom rom...
till developers support this beast and it is able to run any game on playstore at med - high graphics.
Hello,
Guys i have a problem with the notifications on my Amazfit Pace (international version).
This happens very but very often. Whenever i receive a notification my amazfit app disconnects and reconnects immediately therefore the notification is not pushed to the watch. I tried all of the following:
1. I have tried every single version of Amazfit App and nothing seems to work.
2. I have unlocked the bootloader and installed Pacefied v2.6.4.1 (stable) and the problem still occurs.
3. I have Huawei Mate 10 Lite with EMUI 8.0 . I have tried EVERYTHING (ignore battery optimisation and manual launch of background processes etc..). Nothing seems to work.
This problem doesnt allow Amazmod to work fine on my watch and i am restricted. The problem also occurs with WatchDroid.
HOWEVER, i tried the AMF Notification system for my Pace and works perfectly. I get all notifications on my watch, no disconnections at all, however , i just dont like the interface of it!
Any ideas?
It is an issue with firmware/Amazfit app. You have to wait for new versions, or only use "standard notifications" (either in AmazMod or use Amazfit for notifications).
lfom said:
It is an issue with firmware/Amazfit app. You have to wait for new versions, or only use "standard notifications" (either in AmazMod or use Amazfit for notifications).
Click to expand...
Click to collapse
Thank you so much for your reply! Do you know any other members of experiencing the same problem?
I have tried to use only Amazfit without amazmod or any other service and the problem occurs. I have also tried to use amazmod only with the amazfit application to be off and again I experience the same issue. This happens for over a year now since I bought the watch
Try stock firmware with latest Amazfit from PlayStore, or stock CN firmware with latest Amazfit from Mi.com: I have Pace running AmazeROM (which is basically stock CN) connected to a phone with EMUI 8.0 too, and it much better since a few versions of Amazfit ago...
lfom said:
Try stock firmware with latest Amazfit from PlayStore, or stock CN firmware with latest Amazfit from Mi.com: I have Pace running AmazeROM (which is basically stock CN) connected to a phone with EMUI 8.0 too, and it much better since a few versions of Amazfit ago...
Click to expand...
Click to collapse
Do you have any problems with it? I had pacefied and and now I am using AmazIT which I still have the same problem... Do you have the same problem that I have as well? Disconnecting for no reason?
Guys any news?
No problems here using EMUI 8.0 and latest CN Amazfit and firmware (2.6.5.0). You must use only one kind of notifications: either standard (no replies) or custom (with replies). Do not try to use AmazMod when Amazfit app is syncing with phone or it may make the service freeze.
AmazMod only is supported in stock firmware, if you use a custom ROM then you are on your own trying to fix any problems...
I have this exact issue and it's driving me nuts.
I have a Pace A1602, ROM verison 2.6.5.0v1.1, unlocked, running PACEficator Project | WOS 2.6.5.0 ROM.
I don't use AmazMod or the other mod. I use the standard Amazfit app for sending notifications.
Very often, my watch disconnects, then instantly connects again. When I check my phone, it has a new message that should have been pushed to the phone.
How do I go about fixing this?
chaozz said:
I have this exact issue and it's driving me nuts.
I have a Pace A1602, ROM verison 2.6.5.0v1.1, unlocked, running PACEficator Project | WOS 2.6.5.0 ROM.
I don't use AmazMod or the other mod. I use the standard Amazfit app for sending notifications.
Very often, my watch disconnects, then instantly connects again. When I check my phone, it has a new message that should have been pushed to the phone.
How do I go about fixing this?
Click to expand...
Click to collapse
It's not a problem with the watch, but with the phone: some phones have interferences between WiFi and BT, notably some Huawei and Samsung phones. Or you didn't configure it correctly and Amazfit is being killed while in the background, this usually happens with Android 8.0+, MIUI and EMUI.
It's a Huawei phone. What is the best way to go about this? Disabling WiFi is not really an option, for obvious data cost reasons.
Also, I used this same phone without any issues with a Pebble 2 SE. Never any disconnects.
chaozz said:
It's a Huawei phone. What is the best way to go about this? Disabling WiFi is not really an option, for obvious data cost reasons.
Click to expand...
Click to collapse
First, disable WiFi for a while to test if it's the problem. If you confirm it is, try connecting to a 5GHz WiFi network. If it doesn't happen, your only choice it to write to Huawei and Huami about the issue, Huami is aware of the problem (it is plaguing a lot of Samsung users, it is not their fault but they may be able to add a workaround in Amazfit app).
Guys in my opinion its not a wifi issue since i have an amazfit bip and it works perfectly with the mifit app and Notify. It happens only with amazfit app and pace. I believe (without being a programmer) it has to do with the notification system of the watch. Maybe its because we own mid range phones. If you use AMF notification system on pace it works perfectly. I have tried WatchDroid as well and it has the same problems with the amazfit app as well.
This is H0_EEA firmware(OS01) not H0(OS00) firmware
Here is file
- update notes (same as global mq1 firmware's update notes)
1. Update Google Security Patch to 2020-06-05
2. Update brand element related content
3. Updated bootup animation
4. Updated SharkSpace, GamerStudio
5. Addressed mic malfunction issue
6. Optimized camera auto focus at close range
Thanks you bro.
I just updated it anybody have any problems with it so far?
Is there one for BS2 Pro "DLT-H0"?
2dogs16 said:
I just updated it anybody have any problems with it so far?
Click to expand...
Click to collapse
Yea I do. After I installed it my bluetooth devices keep disconnecting regulary. If I don't restart the phone I can't even connect some of my devices like my headphones because it rapidly connects and disconnects. My Galaxy watch also gets disconnected randomly. Besides from that not really.
The fingerprint sensor got faster though!
Bit I STILL can't use smart unlock via bluetooth devices. The list doesn't get populated so I have to use fingerprint all the time
Also YouTube Vanced gets killed randomly if I use background play. Already checked power saving options.
Black Shark 2 pro new update
I'm still having the strange phone problems calls can't hear me
Looking at the official BS2 forums the closing of background apps regardless of the power saving options is a new bug since I am also affected. My Galaxy watch keeps getting disconnected probably due to the accessory service being closed and any background music or video app gets closed as well.
You can't reach the official forums anymore! I wonder why ?
I think this phone global developer bad. Now they deleted their own forum. :crying:
Hello,
I have a Mi 11 Lite 5G and a Mi Watch and no notifications, or sometimes, and do not understand why.
Are you with the same issue ?
Pascal536 said:
Hello,
I have a Mi 11 Lite 5G and a Mi Watch and no notifications, or sometimes, and do not understand why.
Are you with the same issue ?
Click to expand...
Click to collapse
Hi,
I also have the same issue. I have a mi Band 4 and have issues with the notifications. After about 5-7 days, the bands permission to access the notifications is reset on it's own to no access. When I try to enable it, it is already set to allow. I have to revoke and grant permission again for it to work.
Had no issues with the Poco F1 and the same band for more than a year.
After tinkering right now, I got to this screen and I am doing it all. Just checked, but on the Poco, only auto start was enabled. Will see in a few days if this resolves the issue
Hi.
Just an update. For me, the above settings solved the notification issues. Now everything works as it should.
In the meantime I installed a notification patch from a different thread so maybe it helped too...
Here's also that file and a link to that thread
Issue with notifications after the 12.5.1 update
Since the last MIUI update I am experiencing an issue with notification. When using a video player (like Plex, VLC, YouTube Vanced), I usually see a notification icon when using background playback. This is now gone. Also, and this is the main...
forum.xda-developers.com
Hope it works for you too
Hi guys
i have the XQ-CQ54 model with android 12 and i'm experiencing a lot of crashes with Android Auto. Tried everything including factory reset. Problem appears both on USB connection and wireless and appears on all cars i've tried it on (about 4 this far of different brands and models).
Anyone else with this?
might be app related ,5 iv is very new and might need a new android auto update to work better i would advise reporting that to google so they can have that feedback .
I would try it on my car but my infotainment is a little bit older so i cant get to reproduce the same effect.
viper. said:
might be app related ,5 iv is very new and might need a new android auto update to work better i would advise reporting that to google so they can have that feedback .
I would try it on my car but my infotainment is a little bit older so i cant get to reproduce the same effect.
Click to expand...
Click to collapse
i've tried various versions of android auto, they all crash... but they don't on my Samsung S20FE with same Android OS version (12)
Latest thing i tried was making sure power management is off for both AA and Spotify. We'll see if that makes a difference...
Yet again s20fe is not new on the market ,i know what you are saying but i still feel bugs might need some time to be polished on 5 iv as they dont have same hardware .
You can try to test it in safe mode...tho i am not sure if android auto is disabled or not in safe mode
tried changing battery management settings for apps, i'll see if that makes a difference.
andost said:
tried changing battery management settings for apps, i'll see if that makes a difference.
Click to expand...
Click to collapse
nope, didn't... still crashes...
which firmware version are you running on the CQ54? and which version of Android Auto?
I have an XQ-CQ72 on 64.0.H.11.9, with Android Auto 8.6.124944 and don't have any issues
I have a 5 iv running Android 12 and Android Auto works flawlessly.
It didn't when I first tried it. My previous phone was a S22 and Android Auto worked flawlessly. On swapping the phone to the 5 iv, Android Auto couldn't hold a connection and produced error messages. After checking all the appropriate settings I couldn't find anything untoward. Past experience has shown at this point try a different usb cable....and with a different cable Android Auto started working and has continued to work flawlessly ever since.
I have come across this "sensitivity" to the usb cable before, with an older Huawei phone.
I would suggest trying a different usb cable, if you haven't already, as it may make a difference.
dhj1949er said:
I have a 5 iv running Android 12 and Android Auto works flawlessly.
It didn't when I first tried it. My previous phone was a S22 and Android Auto worked flawlessly. On swapping the phone to the 5 iv, Android Auto couldn't hold a connection and produced error messages. After checking all the appropriate settings I couldn't find anything untoward. Past experience has shown at this point try a different usb cable....and with a different cable Android Auto started working and has continued to work flawlessly ever since.
I have come across this "sensitivity" to the usb cable before, with an older Huawei phone.
I would suggest trying a different usb cable, if you haven't already, as it may make a difference.
Click to expand...
Click to collapse
yeah, it's just that the behaviour is the same both on wireless android auto and with USB-c connected...
tonysunshine said:
which firmware version are you running on the CQ54? and which version of Android Auto?
I have an XQ-CQ72 on 64.0.H.11.9, with Android Auto 8.6.124944 and don't have any issues
Click to expand...
Click to collapse
just updated to android 13 (64.1.x) from 64.0.x firmware - same problem except on the way home it was worse than it has ever been before, crashed / disconnected every 5 minutes and reconnected... extremely annoying.
i have 1 IV and don't have crashes. But generally, not as reliable as it was with my XZ2.
Car is Peugeot 3008 mk2 from 2017. Wireless does not work at all but don't really care about that because it just drains battery instead of charging. Now, charging........sometimes it does not charge despite having AA active and using sat nav. Cable that I used with XZ2 (ugreen) does not work at all for AA. And most of the time not even for data on laptop. Cable from XZ2 works with AA every time, did a 5000km trip a few months back, no issues. Except it does not charge sometimes, LED is on, sign for charging is on but battery charge goes down.
Try cleaning the AA app cache. I had same issues w/ my Pixel after update.
TodNex said:
Try cleaning the AA app cache. I had same issues w/ my Pixel after update.
Click to expand...
Click to collapse
Yeah, I've tried that including completely removing / reinstalling app etc.
Now trying on another phone (yes, another 5 IV) which is set up from scratch without restoring from backup.
I have exactly the same behavior with Xperia 5 IV on both Android 12 and 13. Random crashes. Sometime it works for 1 hour, sometimes 5 minutes. It appears to be worse with Android 13.
I tried changing cable, I even bought a new one... no change.
I don't have AA wireless but it does not appear to be cable related. When the crash occurs, my smartwatch (BT) is disconnected.
somm15 said:
I have exactly the same behavior with Xperia 5 IV on both Android 12 and 13. Random crashes. Sometime it works for 1 hour, sometimes 5 minutes. It appears to be worse with Android 13.
I tried changing cable, I even bought a new one... no change.
I don't have AA wireless but it does not appear to be cable related. When the crash occurs, my smartwatch (BT) is disconnected.
Click to expand...
Click to collapse
Hep, another one here!
i'm trying to remove apps one by one now...
Well, I had 1 hours without any crash... after enabling the debug layer for android auto. I didn't notice any difference or additional info but no crash.
Hey Guys; I am facing the same issue. Just, that it's not related to Android Auto.
Many apps were crashing just randomly.
For example, like Tidal, sometimes it was playing music for hours and sometimes just for a few minutes until it crashed.
So I enabled a feature in developer mode which allows to show a crashing dialog. And just a few moments later the nextcloud app crashed and the error message was something like "out of memory".
Looking in to it => Yep, there it was => the OS is holding almost all of the available memory.
So, you might want to check your memory in Settings => Developer Options => Memory.
And since I almost bricked my device last night, I just flashed the latest 64.1.A.0.857 via newflasher and at the moment (fresh OS) it seems to be better - but I will surley find out these days.
Merry Christmas everyone ...
Hi guys, I had similar problems with Android auto. I did a software repair with Xperia Companion, since then AA works fine.