Database Develop

Android Auto connectivity workaround that works!

Workaround that works 100% of the time for those having trouble connecting.
Unlock phone and turn on car or head unit. Note you should have android auto installed already before this will work. Plug in the cable to your phone and you will hear the link sound and the screen on your phone will flash off for just a second. As quickly as possible once the screen goes black on your phone uncable the phone and reconnect it. I know this sounds janky, but it really works. You can tell it is working by the screen on your head unit going black in the background and you will see the android auto icon sI have tried all suggested fixes and this is the only one that works 100% of the time. It also does not take over the telephone's display so you can navigate to other apps and still have android auto running. It is quick and gives you the best of both worlds. I almost returned my 2016 gti due to the frustration from this issue, but now it is no big deal.
Hope this helps guys and gals.

No. For what I read , the only API available for 3rd parties are to send messages and music, and that, using google interface. No other developer can do anything with AA.

[FIX available] Bottom part of the touchscreen stops working

Solution:
Go to Settings (if you're stuck in an app, use the button in your notification panel)
Go to 'System' (try tapping above the broken screen area)
Go to 'About this phone'
That should be all that has to be done! Do note: this fix isn't permanent. Let's hope Nokia fixes this.
Old thread:
Hello all!
When i woke up today and unlocked my phone (while an app is open) the bottom part (starting just above the nav-buttons) of my touchscreen just stops working.
I've had this problem a couple times (at most once per day) since updating from Oreo.
The solution to this problem seems to just to reboot the phone.. (This won't fix it permanently, sadly)
I'm asking if anyone else has this same problem, because i don't know the source of this problem.. (Maybe its because of the app not being P compatible?)
Thanks!

Hi, I have the same problem after the last update (september). Android Pie beta. Almost every morning i have to restart ..
Before the update was enough to just torn off/on the screen .

i don't have this problem on TA-1046 with Pie DP2-DP4.1 or Pie stable... maybe some incompatible apps? you use some for changing NavBar/Gesture area?
although i use XDA NavigationGesture what replace NavBar/Gesture with own, still not having problem, maybe you can try too this replacement, have many more function/settings that stock Pie gesture

for u its bottom touch screen is not working , but for me top of my touch screen isnt working .. and iam facing some serious problems after updating to pie . my phone restarts all of a sudden while charging , app crashes and more , hope hmd fixes this kind of issues in upcoming oct security patch update .

k3dar7 said:
i don't have this problem on TA-1046 with Pie DP2-DP4.1 or Pie stable... maybe some incompatible apps? you use some for changing NavBar/Gesture area?
although i use XDA NavigationGesture what replace NavBar/Gesture with own, still not having problem, maybe you can try too this replacement, have many more function/settings that stock Pie gesture
Click to expand...
Click to collapse
The app i left open last when it happened was "Boost For Reddit"
I'm using the old navbar layout (so no swipe)
dexterboon said:
for u its bottom touch screen is not working , but for me top of my touch screen isnt working .. and iam facing some serious problems after updating to pie . my phone restarts all of a sudden while charging , app crashes and more , hope hmd fixes this kind of issues in upcoming oct security patch update .
Click to expand...
Click to collapse
That's soo weird! I really hope HMD will release a patch soon.. I don't want to downgrade back to oreo

Issue with charging
I am having a charging issue. My phone usb and adapter is working fine with other phones. But when I connect my Nokia 7 Plus below 50%,My phone shows charging And when I tap the screen it doesn't charge. It occurs couple of time. And then It becomes normal and shows rapid charge after 55%. My charging port is fine when I connect it with my Pc usb port. some how the rapid charge doesn't respond. Does anyone have this problem?

Rahul Deshmukh21 said:
I am having a charging issue. [...]
Click to expand...
Click to collapse
What is real time for charge? Rapidcharging is disabled while you activated LCD

Yeah I'm facing similar issues, or did... I'm not sure... but it's been a non-issue for the past ~36 hours now. Here's to hoping it's not an issue any longer. I speculated it might be adaptive battery related somehow, so I tried rebooting my phone just before going to bed Sunday night, but my navbar still worked Monday morning, and this Tuesday it's still working in fact. I did this to test if it stopped working based on time since last reboot, or because some background process being killed due to adaptive battery/doze putting the phone to sleep. But based on my recent experience I think my hypothesis can be rejected. And I'm still not sure what caused it.

STcraft said:
Hello all!
When i woke up today and unlocked my phone (while an app is open) the bottom part (starting just above the nav-buttons) of my touchscreen just stops working.
I've had this problem a couple times (at most once per day) since updating from Oreo.
The solution to this problem seems to just to reboot the phone.. (This won't fix it permanently, sadly)
I'm asking if anyone else has this same problem, because i don't know the source of this problem.. (Maybe its because of the app not being P compatible?)
Thanks!
Click to expand...
Click to collapse
Same for me ta-1046, happened to me twice now. bottom part of screen stops reacting to touch. reboot fixes it.

Hmm... After playing around in the settings while having this problem active, for some reason, going to the phone info section just fixed it... I'm not sure if going there actually did that. needs more testing, I suppose.

+1 I use navigation gestures

STcraft said:
Hmm... After playing around in the settings while having this problem active, for some reason, going to the phone info section just fixed it... I'm not sure if going there actually did that. needs more testing, I suppose.
Click to expand...
Click to collapse
Huh, I'll be damned. When my nav bar was frozen this morning I went into the "about phone" section in the menu, and, lo and behold, my nav bar sprang back to life instantly. Now it might still just be a coincident of course, but it's certainly interesting, and could potentially be a fix where you don't have to reboot.

​
silverphoenix87 said:
Huh, I'll be damned. When my nav bar was frozen this morning I went into the "about phone" section in the menu, and, lo and behold, my nav bar sprang back to life instantly. Now it might still just be a coincident of course, but it's certainly interesting, and could potentially be a fix where you don't have to reboot.
Click to expand...
Click to collapse
surprised me as well that it worked. He could be a good beta tester. lol

Capture of
I managed to capture a video of the bounds of the touch-registration when the bottom 1,5 centimeter of the screen stops registering.
https://imgur.com/xrRB906

Same problem for me after upgrading a couple of days ago. Bottom of the screen (navbar and a bit more) is not accessible. Always happens after a night charging.
Going to the "About phone" menu fixes it. Thanks!
I have seen reports of people with other phones saying this is due to the setup wizard being active and preventing using the navigation bar. Tried some suggested adb commands without success. I will still try to disable the setup wizard app and report back.

IT ACTUALLY WORKS!!
AssKiRK said:
​
surprised me as well that it worked. He could be a good beta tester. lol
Click to expand...
Click to collapse
oh thank you! XD

Updated the OP

Please put a comment here as well: https://community.phones.nokia.com/support/discussions/topics/7000036457?page=1
This might help getting a quicker fix from Nokia.

Looks like the recent October patch still has this issue.
Would be nice if i can get a logcat this issue, but given this issue gets triggered after hours of inactivity, it would take a looong time to sift through the log.
Maybe there's a way to trigger it without waiting?
I can try logging when i do the "about phone" fix, will come back to this.

same isue here.. after chsrging at night nav bar bottom inch not responsive.. will try the phone info thing in the morning... is this software related ? will there be a patch??

10.2.27.0 EEA ROM withdrawn?

After several days of reading posts that 10.2.27.0 EEA was available, I finally tried to upgrade just now.
Checked on the phone. No update available.
Went to official ROM depository en.miui.com. The latest they have is still 10.2.26 EEA.
Ended up doing the download at miblog.co. But when I installed it failed at validation saying this is beta and I need a beta authorized Xiaomi account to be able to install it.
... So did they rollback the ROM distribution?

My guess is that with the major problems during the latest Mi 9 SE update they stopped all roll outs until they have figured out the problem. Also for other Mi9 devices.

I flashed the update via TWRP and its not so good to use. Have some connection problems with it. Hopefully they fix the issues soon and deliver it new.

I am positively surprised about the .27 update. It fixed all my battery standby drain issues. Got a much better runtime now, 2 days when fully charged

Thank God i didnt install the update. The update appeared like week ago and then suddenly disappeared. I was waiting for some reviews, because my phone is running great on .26 update,although there are still some minor bugs.

I have exactly opposite experience to the Dada124's. 10.2.26.0 was very gentle to the battery, while 10.2.27.0 drains it like crazy. Yesterday it went down from 68 % to 18 % in 3 hours - 1hour watching video, 1hour surfing web and 1hour listening to an audiobook. No wonder they pulled it. Hope they fix it with next update, because this is beyond ridiculous.

I don't have battery issue with .27
Bluetooth volume is now synced with my earbuds, there is direct control.
My alarm still don't show up on the lockscreen in the morning, it's annoying to unlock the phone to deactivate it. Am I the only one with this problem ?!?

Gokh said:
I don't have battery issue with .27
Bluetooth volume is now synced with my earbuds, there is direct control.
My alarm still don't show up on the lockscreen in the morning, it's annoying to unlock the phone to deactivate it. Am I the only one with this problem ?!?
Click to expand...
Click to collapse
I have only good things to say about the .27 update. Slightly better battery life, pocket mode (yay!), better volume handling with different Bluetooth devices (no too lows or too highs) more devices turning up as aptX or better codecs instead of the basic SBC.

gerhard_wa said:
...pocket mode (yay!)...
Click to expand...
Click to collapse
No option too turn on/off pocket mode, and screen still wake in pocket

bioly87 said:
No option too turn on/off pocket mode, and screen still wake in pocket
Click to expand...
Click to collapse
I cannot make it turn on if the upper part of the screen is covered. No need to turn off pocket mode. I tested the pocket mode very intensively and at no time however much I try or tap the whole screen or the fingerprint reader will it go to the lock screen anymore!

Gokh said:
I don't have battery issue with .27
Bluetooth volume is now synced with my earbuds, there is direct control.
My alarm still don't show up on the lockscreen in the morning, it's annoying to unlock the phone to deactivate it. Am I the only one with this problem ?!?
Click to expand...
Click to collapse
No you're not. I thinks it's a bug in the clock app. Workaround ist to schedule the DND mode to end in the same Minute Like your Alarm is ringing.

I have .27 on two Mi 9s, and both are experiencing problems:
- Battery drain
- Connection problems, both 4g/LTE and Wi-Fi
- Pocket mode, if exists, is enabled by default, because there is no switch on/off.
- Multiple issues with Android Auto
At least they fixed the AI button - it does pull Google voice assistant directly now.

lusp00ky said:
I have .27 on two Mi 9s, and both are experiencing problems:
- Battery drain
- Connection problems, both 4g/LTE and Wi-Fi
- Pocket mode, if exists, is enabled by default, because there is no switch on/off.
- Multiple issues with Android Auto
At least they fixed the AI button - it does pull Google voice assistant directly now.
Click to expand...
Click to collapse
It is similar to me

Hey, they launched 10.2.28.0 EEA!

Updating to 10.2.28.0 EEA right now.

No 28 for my mi 9 running 27 so far. Does anyone have a direct link?

nupi said:
No 28 for my mi 9 running 27 so far. Does anyone have a direct link?
Click to expand...
Click to collapse
OTA incremental
https://bigota.d.miui.com/V10.2.28....PFAEUXM-V10.2.28.0.PFAEUXM-0e3ced5073-9.0.zip

Thanks. No obvious difference to 27 yet

I updated to 10.2.28, no issue.
Except how can we confirm pocket mode? As someone said above, there is no on/off options. Is it enabled by default?
Sent from my MI 9 using Tapatalk

mynameismada said:
I updated to 10.2.28, no issue.
Except how can we confirm pocket mode? As someone said above, there is no on/off options. Is it enabled by default?
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
Cover the upper part of the screen with one hand and tap the fingerprint scanner fast for some time. Does this make the lock screen show then pocket mode doesn't work for you. It's on by default. It works well for me.
Skickat från min MI 9 via Tapatalk

Question Has anyone had trouble with Android Auto

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)

A12 bugs?

So I've clean flash a12 on my p5 and I've noticed a few annoying things;
. Selecting vibrate only shows no icon in status bar
. Music player gets stuck in notifications despite untoggling this function
. Battery seems to have taken a massive hit (granted it's only day 2, it may just be settling)
. Bluetooth audio seems to take longer to pair in my car
. WiFi toggle gets stuck on despite being deactivated
Is anyone else having any issues?
I'm otherwise loving the flow and detail of a12, just abit disappointed with these niggles.

dlb134 said:
So I've clean flash a12 on my p5 and I've noticed a few annoying things;
. Selecting vibrate only shows no icon in status bar
Click to expand...
Click to collapse
Not a bug, ring mode is no longer displayed in status bar
dlb134 said:
. Music player gets stuck in notifications despite untoggling this function
Click to expand...
Click to collapse
Swipe to one side, tap the settings icon, turn off "Pin Media Player"
dlb134 said:
. Battery seems to have taken a massive hit (granted it's only day 2, it may just be settling)
Click to expand...
Click to collapse
My battery life seemed a little higher on the A12 beta 5, it went back to normal after a day, I can easily last 24+ hours with casual use
dlb134 said:
. Bluetooth audio seems to take longer to pair in my car
Click to expand...
Click to collapse
Haven't noticed if it's taking any longer, Bluetooth seems to work normally
dlb134 said:
. WiFi toggle gets stuck on despite being deactivated
Click to expand...
Click to collapse
Do you have WiFi scanning enabled? System will automatically turn it on to detect networks and to assist coarse location
dlb134 said:
Is anyone else having any issues?
I'm otherwise loving the flow and detail of a12, just abit disappointed with these niggles.
Click to expand...
Click to collapse
Honestly I haven't noticed any issues specific to Android 12. I did notice my car's head unit stopped displaying track information with Android 11, but it came back with Android 12. I like the UI revamp, but I'm also in my mid 30s so I appreciate things that are designed to be a bit more ergonomic. Overall function is pretty much the same. My only frustration has been rooting the 12 final release, whereas the beta seemed simpler.

V0latyle said:
Not a bug, ring mode is no longer displayed in status bar
Swipe to one side, tap the settings icon, turn off "Pin Media Player"
My battery life seemed a little higher on the A12 beta 5, it went back to normal after a day, I can easily last 24+ hours with casual use
Haven't noticed if it's taking any longer, Bluetooth seems to work normally
Do you have WiFi scanning enabled? System will automatically turn it on to detect networks and to assist coarse location
Honestly I haven't noticed any issues specific to Android 12. I did notice my car's head unit stopped displaying track information with Android 11, but it came back with Android 12. I like the UI revamp, but I'm also in my mid 30s so I appreciate things that are designed to be a bit more ergonomic. Overall function is pretty much the same. My only frustration has been rooting the 12 final release, whereas the beta seemed simpler.
Click to expand...
Click to collapse
V0latyle said:
Not a bug, ring mode is no longer displayed in status bar
Swipe to one side, tap the settings icon, turn off "Pin Media Player"
My battery life seemed a little higher on the A12 beta 5, it went back to normal after a day, I can easily last 24+ hours with casual use
Haven't noticed if it's taking any longer, Bluetooth seems to work normally
Do you have WiFi scanning enabled? System will automatically turn it on to detect networks and to assist coarse location
Honestly I haven't noticed any issues specific to Android 12. I did notice my car's head unit stopped displaying track information with Android 11, but it came back with Android 12. I like the UI revamp, but I'm also in my mid 30s so I appreciate things that are designed to be a bit more ergonomic. Overall function is pretty much the same. My only frustration has been rooting the 12 final release, whereas the beta seemed simpler.
Click to expand...
Click to collapse
Think I found why I was having such battery drain....
Disabled the service 'Android system intelligence'. Do you.know what this is?

dlb134 said:
Think I found why I was having such battery drain....
Disabled the service 'Android system intelligence'. Do you.know what this is?
Click to expand...
Click to collapse
A quick Google would had served me well... I've reenabled but on restricted... I've never had personalisation service drain so much

. Selecting vibrate only shows no icon in status bar - Haven't found an option to switch profiles yet.
. Music player gets stuck in notifications despite untoggling this function - Haven't noticed this issue.
. Battery seems to have taken a massive hit (granted it's only day 2, it may just be settling) - Isn't as advertised, for sure.
. Bluetooth audio seems to take longer to pair in my car - No noticeable difference for me.
. WiFi toggle gets stuck on despite being deactivated - This, I have noticed. Very annoying.
Overall, I feel that Android 12 is a downgrade, rather than an upgrade in so many areas. Hopefully the good folks at XDA will find fixes and customizations to offset this horrible mess of design and functionality.
I'm seriously considering going back to A11. If I wanted the customization level of an iPhone, I'd get an iPhone (no I wouldn't )

The main bug i found is that Chromecast volume can't be controlled directly by volume button on the phone, we must absolutely pass by the Google home apps...
That's quite annoying...
And i read that this isn't even a bug, it's a "feature" wanted by Google... Legal issue...
If anyone can help :
A12 Chromecast volume control
Hi there, There is a wanted behavior in Android 12 that disable the volume button that control Chromecast volume. https://issuetracker.google.com/issues/201546605?pli=1 Is there an ADB command that can return the behavior to what was in...
forum.xda-developers.com