So, I finally updated to Nugat last night, and now Android Auto 2.0 has a few annoying 'features' I needed to fix. I figured them out, so I'll share here.
I could no longer get to my main home screen. This used to be really handy, as I could plug in my phone, get everything setup, tap recent apps and then home to get to my regular home screen. I need to be able to do this to arm my home alarm and to launch Waze.
SOLUTION 1 - 1 Tap Quick Bar
There are a lot of apps like this, and I tried this one first, did exactly what I wanted it to, but it left too much going on in my notification pane. Basically this creates an additional notification bar that you can add settings or applications to. I added Action Launcher 3, Waze, my home alarm app, and two others to it, worked fine.
If there were a way to have a notification bar like this be active only when Car Mode was enabled, it would be my preferred method.
SOLUTION 2 - Custom Quick Settings - (PREFERRED)
This works perfectly, takes up almost no space (one quick settings tile), and looks like it is built in.
I installed this, added a quick settings tile to go directly to my Action Launcher 3 home screen (my wife set it up to go to Nova Launcher), and now I just pull down on the right side of my Nexus 6P screen, tap on the Quick Setting Tile that says Home, and bam, back at the home screen. Tap on the Home button in the Android Auto overlay and I'm back in Android Auto (I just leave it in Waze).
Hope this helps others.
Hey!
I accidentally see, that when you touch the gear in the notification bar for a while, it starts to spin. Was not that in older versions of Android the activation gesture for a system tuner or something?
Spoiler: the spinning gear starts no action. So it's a useless function??
My gear doesn't spin like yours but that was the gesture to activate the System Tuner in Marshmallow but all it did on stock Android was allow you to customize the System Tray in ways that are now part of the menu you access by hitting the icon to the left of the gear. Some phone manufacturers would add a few additional UI Tweaks but they were always pretty minor.
mine (on v152) spins as wheel - seems like it does nothing though...
So I'll try to keep this as short as possible but it is a bit complicated.
Basically I purchased a Chinese Android Radio for my 2014 Cayenne. I was very hesitant because I know that AliExpress type items can be very hit or miss (mostly miss) in terms of quality. Black Friday came around and I had the option to save $70 on the Radio so I just went ahead and ordered it. I have since received and installed the radio and am actually very happy with it overall.
Now like most Full Android Head Units this radio does not have built in Android Auto but has the option to use it via external USB dongle and the "Autokit" App.
My question stems from the fact that the radio has a dedicated navigation button that opens a default navigation app and also activates the split screen function so you can run the default navigation app on the top half of the screen and a media app on the bottom. The problem is that what I want to do is run the carplay interface on the top half of the screen (through the Autokit App) but it does not show up as an option for Default Navigation.
Is there a way that I could make the Radio see the Autokit app as navigation app so I have the quick launch feature and split screen option for Android Auto?
This is the radio I purchased:
https://www.aliexpress.com/item/400...chweb0_0,searchweb201602_7,searchweb201603_53
And this video shows the functionality (Dedicated nav button and split screen function at 1:55 to 2:15)
https://www.youtube.com/watch?v=W8m_ogoY718
Hi everyone,
trying on MIUI 12.5 to enable Microsoft Launcher with Gestures instead of the 3 Bar Bottom Navigation.
Installed "MyGestures" App - which enables gestures - fine.
But still having the 3 buttons bar on the bottom.
Have tried FNG which is recommended by many people, but it only hides the 3 bar bottom - still having a black bar.
Some months ago (before I wiped my phone) I have enabled the gestures in the MIUI menu, and it hid the navigation bar.
But now I get the following chinese info (seems like a message to activate the default launcher, as it gets enabled after right clicking the button)
see screenshot.
Any idea how to activate it without auto starting default launcher?
well for anyone with the same problem, I got a workaround which is quite embarrasing but at least it works to remove the 3-bar navigation.
You need the "LADB" application from Playstore which sadly costs some money.
Then in short:
1. Developer Options - > Wireless ADB enable
2. start LADB and connect it (you have to use dual window feature, because otherwise the port+pin will change)
you need to do this once, after setting up - it will connect next time automatically.
3. insert in LADB command line: settings put global force_fsg_nav_bar 1
It works good. But you have to do it again after a reboot.
Note: app compatible with any phone with 1080x2400 screen or lower. Probably higher too, try it. Also it's impossible to make such block when talking in messengers (more precisely, it's difficult). App won't work without gapps, rare case.
Instead of classic reliable optical sensor we have sucky ultrasonic one.
Sometimes it does not turn off the screen while phone call and something is pressed with ear or cheek up to dropping call.
Popular workaround is app "Call Proximity Sensor Fix" which automatically turns off the screen. Or you can press the power button immediately after the answer.
But IMHO this is inconvenient because if you need to look at something on the screen it will not turn on by itself which is so familiar.
My simple application makes screen insensitive to taps. And unlike analogs soft buttons and status bar are blocked too (but not gestures).
On screen will be translucent button that disables lock if you need to use the phone:
– Long tap on button - unlock (button will turn green)
– Short tap when unlocked - lock again
– Long tap when unlocked - remove button at all so as not to interfere with e.g. for entering text
When second call comes in screen will automatically unlock so you can easily answer or hang up. Then it blocks again.
When manually launching the application there will be a question whether to enable 4 seconds delay for an outgoing call. So you able to choose SIM card.
Made by powerful Tasker, the project was exported as standalone application via App Factory. Implemented via scenes with new full-screen blocking type.
Location of button adapted for default AOSP / Google Dialer. It can be misplaced for third-party dialers and / or interface scale. It's impossible to cover all possible variants. So if it really bothers you, install Tasker and project below. Then change coordinates of the buttons.
Installation
Follow manual carefully, otherwise nothing will work.
Application is safe and doesn't have internet access.
1. Download APK below this post
2. Install it via file manager and launch
3. Answer the question about delay, decision can be changed later by launching app again
4. Open Settings > Apps & Notifications > In-Call Screen Lock
5. In "Notifications" turn off them all completely, otherwise they will be annoy you
6. In "Permissions" enable everything: Contacts, Call List and Phone
7. MIUI: right there in application settings enable "Autostart"
8. MIUI: and in "Background" select "No restrictions"
9. Custom: Settings > Apps & Notifications > Advanced > Special app access > Battery optimization > All apps > In-Call Screen Lock > Don't optimize
10. Custom: Settings > Apps & Notifications > Advanced > Special app access > Display over other apps > In-Call Screen Lock > Allow display over other apps
11. MIUI: Settings > Privacy > Management > Special app access > Display over other apps > In-Call Screen Lock > Allow display over other apps
12. Settings > [MIUI: Advanced settings] > Accessibility > In-Call Screen Lock > enable "Use In-Call Screen Lock"
If you using Tasker
1. Download ZIP archive below this post
2. Extract file from it to phone/Tasker/projects
3. Tap on "House" icon at the bottom > Import Project > In-Call_Screen_Lock
4. If you don't need a delay on an outgoing call: delete / disable action #3 ("Wait") from the "In-Call Lock Start" task
5. Custom: Settings > Apps & Notifications > Advanced > Special app access > Display over other apps > Tasker > Allow display over other apps
6. MIUI: Settings > Privacy > Management > Special app access > Display over other apps > Tasker > Allow display over other apps
7. Settings > [MIUI: Advanced settings] > Accessibility > Tasker > enable "Use Tasker"
UPD: files updated, fixed small bug.
does this affect battery life
shakeelbirmani said:
does this affect battery life
Click to expand...
Click to collapse
No.
Tested now on my RN10-pro... works just fine! Thank you!
Tested without gapps and it didn't work. I use the standard phone app from Arrow OS. I do all settings from your instruction.
There was no 4 seconds query of the sim card. The and no lock screen button.
Social_Work said:
Tested without gapps and it didn't work.
Click to expand...
Click to collapse
Unfortunately, APK's exported by Tasker always have dependencies from GMS no matter actions it should perform. Sorry, I can't fix that.
I reinstal Arrow with Gapps and Install tasker. IT works great! Thx a lot! Now ist this Phone uesable.
Great application. Tested it via Tasker and works. Thank you so much!
Small question, if you do use the power button while in call to lock the screen and you unlock it again and then use your unlock button, it unlocks but the button disappears so you can't lock it again. How do I get the button back then?
Note: sensors are automatically calibrated and sometimes this creates a problem.
To cleanup and recalibrate the sensors, all you need to do is this:
Bash:
# dd if=/dev/block/by-name/persistbak of=/dev/block/by-name/persist conv=notrunc
For me that solved everything on official MIUI V13.0.12.0 (and previously on V12.5.9.0).
Amazfit User said:
if you do use the power button while in call to lock the screen and you unlock it again and then use your unlock button, it unlocks but the button disappears so you can't lock it again
Click to expand...
Click to collapse
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
Zibri said:
sensors are automatically calibrated and sometimes this creates a problem
Click to expand...
Click to collapse
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Bonoboo said:
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Click to expand...
Click to collapse
Thanks for the information. Tested it and ticking the block overlay + fixes the issue. I guess it's because even though I'm able to tap the icon and other call icons the phone is still locked. I guess the overlay + makes sure that the lock off scene is still visible on the "lock" screen. I'm on Samsung One UI 4.1 with the native Google dialer.
Thanks for the help.
Bonoboo said:
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Click to expand...
Click to collapse
ultrasonic sensor can be even manually calibrated and the calibration is indeed stored and used.
Also: the ultrasonic sensor works in software, relying also on the position and angle of the phone.
If that measurement fails or is inaccurate, everything is ruined.
Trust me: try to do a fastboot flash of V13.0.12.0 then reset that partition as I said.
Then you can tell me if it improves or not.
For me now it works perfect both in DUO both in the stock dialer and messenger.
You can find the latest stock firmwares here:
Codes and study of the Redmi Note 10 PRO (SWEET) and some findings
code name 76937 com.miui.powerkeeper.cloudcontrol.CloudUpdateReceiver 8437625 com.miui.powerkeeper.thermalconfig.ThermalConfigReceiver 37263 com.miui.powerkeeper.ui.framerate.FrameRateSecretCodeReceiver 2877...
forum.xda-developers.com