Related
I have an unrooted/unchanged/stock Huawei P10 running EMUI 5.1 and am trying to debug a website I'm making. Latest Chrome on the P10 and latest Chrome on my Retina MacBook Pro 15'' (late 2013) High Sierra 10.13
The route worked on all my previous devices. USB Debugging is checked on, I plug in the cable and say yes to the prompt "Allow Access to device data?". Next prompt "Allow USB Debugging" -> OK gives me the following error: "An App is obscuring a permission request. Settings can't verify your response"
Looking for solutions I read stuff about background apps which mess up things. All I know of / remember installing is "Mi Band Tools", and "Pie Controls".
I tried to shut down "Mi Band Tools" via Settings -> Apps -> Mi Band Tools -> "Stop" – But it seems not to be stopped for long? Since I don't know if this would solve the problem anways, I figured to come here first. It would be great if I wouldn't have to uninstall these apps.. always a pain to restore etc.
Thank you very much!
*gentle push*, because the problem still remains
katerlouis said:
*gentle push*, because the problem still remains
Click to expand...
Click to collapse
I had the same problem with my Huawei Honor View10.
I had to uncheck the "Permit drawing over other apps" for a (in my case) JINA Drawer. Maybe you have to uncheck an other one...
In EMUI 8 = Settings - Apps - Apps & notifications - Apps - Settings (bottom of screen) - Special access - Draw over other apps
Good luck!
fehrcomp said:
I had the same problem with my Huawei Honor View10.
I had to uncheck the "Permit drawing over other apps" for a (in my case) JINA Drawer. Maybe you have to uncheck an other one...
In EMUI 8 = Settings - Apps - Apps & notifications - Apps - Settings (bottom of screen) - Special access - Draw over other apps
Good luck!
Click to expand...
Click to collapse
Thank you for the tip! This got me on the right track <3
Holy Moly.. this setting is hidden as hell; on my P10 running EMUI 5.1 (german), the setting path was:
settings > apps > settings (corg button at the bottom left) > special access > draw over other apps > talkback
Thank youuu!
katerlouis said:
Thank you for the tip! This got me on the right track <3
Holy Moly.. this setting is hidden as hell; on my P10 running EMUI 5.1 (german), the setting path was:
settings > apps > settings (corg button at the bottom left) > special access > draw over other apps > talkback
Thank youuu!
Click to expand...
Click to collapse
Yes! On my device Mate 1o Pro, it was Talkback as well that ¨obscured a permission request¨.
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
help please
im using honor 7x with latest oreo update and running on emui 8.0
none of the above method helped me get through that error
please help i can not verify my computers RSA key because an app is obscuring the permission request .
kamisan said:
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
Click to expand...
Click to collapse
YEESSSS!!! Thank you for mentioning this, I never would've make that connection and that's exactly what it was for me! I guess those pics weren't all that smart after all ?
Panshu Mehra said:
im using honor 7x with latest oreo update and running on emui 8.0
none of the above method helped me get through that error
please help i can not verify my computers RSA key because an app is obscuring the permission request .
Click to expand...
Click to collapse
I have an Honor 8 pro and I'm facing the same issue. I've disabled all apps which draw on the screen and restarted my phone too.
kamisan said:
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
Click to expand...
Click to collapse
Wow, good call. I was having this same issue. Thanks!
Fix #2 - if it works
i was messing with my Samsung Galaxy J7 Core J701F/DS and I was trying to figure out your problem also because i got the same problem as yours so the thing that worked for me is going to Settings (Nougat 7.0/1)> Apps> 3-dot menu/optionsl settings/other settings> Special Access> Apps that can be on top> Disable all apps like literally disable them all and try to debug your phone again...if it works, enable apps in that setting one by one and repeat debugging process. If it doesnt work, disable the last app you enabled, and if it works again...that is the app that is doing the dirty work...mine was not in the system apps it was one of my apps which is AZ Screen Recorder lol....(why the app that is being used everyday need to be disabled....)
kamisan said:
If you have a custom rom with Smart Pixels and it is turned on, it will do this also. Turn it off, retry,
Click to expand...
Click to collapse
Omg thank you so much for this. It was driving me bat**** crazy. I tried everything didnt even think this would cause it.
katerlouis said:
I have an unrooted/unchanged/stock Huawei P10 running EMUI 5.1 and am trying to debug a website I'm making. Latest Chrome on the P10 and latest Chrome on my Retina MacBook Pro 15'' (late 2013) High Sierra 10.13
The route worked on all my previous devices. USB Debugging is checked on, I plug in the cable and say yes to the prompt "Allow Access to device data?". Next prompt "Allow USB Debugging" -> OK gives me the following error: "An App is obscuring a permission request. Settings can't verify your response"
Looking for solutions I read stuff about background apps which mess up things. All I know of / remember installing is "Mi Band Tools", and "Pie Controls".
I tried to shut down "Mi Band Tools" via Settings -> Apps -> Mi Band Tools -> "Stop" – But it seems not to be stopped for long? Since I don't know if this would solve the problem anways, I figured to come here first. It would be great if I wouldn't have to uninstall these apps.. always a pain to restore etc.
Thank you very much!
Click to expand...
Click to collapse
1. Apps such as Blue light filter apps constantly appear on the top of your screen thus breaking some of the on screen functionalities. Try disabling display over other apps permission of such apps and you should be fine.
2. Also, sometimes it is because of your custom launcher, so try switching to your stock launcher if above solutions don't work.
3. If Accessibility for some apps are on then try disabling them first.
PS : Of all the 3 solutions try the possible ones.
Hope it helps.
kapil1100 said:
1. Apps such as Blue light filter apps constantly appear on the top of your screen thus breaking some of the on screen functionalities. Try disabling display over other apps permission of such apps and you should be fine.
2. Also, sometimes it is because of your custom launcher, so try switching to your stock launcher if above solutions don't work.
3. If Accessibility for some apps are on then try disabling them first.
PS : Of all the 3 solutions try the possible ones.
Hope it helps.
Click to expand...
Click to collapse
This put me on the right track.
I have an LG G6 running Android 8.0. My Keeper Security app needs permission to Draw over other apps and since around December 2018 it has started acting 'flaky'. The app would warn me that I need to turn on this permission, but when I clicked "OK" in the Keeper app to take me to the Android setting for the app, it was always turned on. I could turn it ON/OFF, along with the setting that needed this permission in the Keeper app (called Keeper Fill) and eventually get it to work again, but it would always break again very soon after.
As I am getting ready to go on a trip, I installed Google's Datally app. It, too, wants me to turn on Draw over other apps, but when I tap "next" to be taken to the Android settings page to enable Draw over other apps, nothing happens (I usually expect an app detects it has been enabled and gives "success" message).
So I started disabling the 3 possible suspects listed by kapil1100. I had LG's Comfort View and some Accessibility options enabled, so I turned them off and: no change.
I disabled all other apps that have permission to Draw over other apps via: Settings > Apps & notifications > Special access > Draw over other apps, and: no change.
I use Evie launcher, so I went back to the stock one: no change.
I got thinking about what else could be modifying/accessing the screen and realized that LG has custom Home touch buttons.
I went to: Settings > Display > Home touch buttons > Hide Home touch buttons and DISABLED Show lock/hide icon and then tried enabling Draw over other apps for Datally and IT WORKED!.
I was then able to turn Show lock/hide icon back ON and everything has been working as expected. I suspect that, because I had Show lock/hide icon turned on during an upgrade, something got messed up and my turning it OFF and back ON fixed the issue.
I hope this helps someone!
Hello people, as I've seen unlocking and rooting is mooving along quite good. And since in each xiaomi device forum there's a topic like this.
I've tried several apps/methods (adb) to enable navigation gestures on Nova launcher specially, but with no avail. Of course I haven't tried rooting because that's not an option for me.
Currently I'm using navigation buttons with edge gestures (app), but I don't want to use nav buttons permanently as I worry about screen burn in.
So has anyone managed to enable gestures on 3rd party launchers and/or remove/hide the navigation bar? Please enlight us
EDIT: I MADE IT WORK
After several days searching, reading and trying I was about to give up on this one. I was getting acustomed to use Navigation bar + edge gestures (app) and I was kind of happy. But, luckly today I used some of my last shots to try to accomplish it and I DID IT.
Thus here's a brief guide on how to do it:
Install ADB and Fastboot Drivers from here (Select the latest) -> https://androidmtk.com/download-minimal-adb-and-fastboot-tool )
Install drivers for Xiaomi 11T Pro -> https://droidfilehost.com/download/download-xiaomi-usb-driver-for-windows
Enable Developer Options
On Developer options Enable: USB Debugging, Install via USB and USB Debugging (Security settings)
After that and by checking in power shell or the command prompt on windows with "adb devices". If your device get listed you're golden.
Open power shell or CMD on the folder where you installed minimal adb and fastboot.
Type and enter adb shell
Then on the adb console type: settings put global force_fsg_nav_bar 1
This will hide the navigation bar and it will put gestures as your main navigation method, but take into account that you should configure prior to this process another gesture app such as FNG with your preferred gestures. Other additional things you can do is set FNG as "autostart" in app settings and/or lock it in the recents view.
AFAIK Navigation bar will reappear every time you reboot your pohone, in that case you should only repeat the adb command and you should be good. If anyone knows a permanent solution without root please let us all know.
Hope it works for you as it did for me.
I checked about this last week, since I personally use Nova Launcher.
Unfortunately even with the existing phones that are using MIUI 12 that have been out for 1 year or so, I couldnt find a solution with the navigation gestures. If I find something, I will let you know.
nousernamesorry said:
I checked about this last week, since I personally use Nova Launcher.
Unfortunately even with the existing phones that are using MIUI 12 that have been out for 1 year or so, I couldnt find a solution with the navigation gestures. If I find something, I will let you know.
Click to expand...
Click to collapse
Just made it work, check the OP if you want to try it.
It works for me too, but needs permanent solution.
Permanent solution requires rooted phone and can be done like this:
https://www.reddit.com/r/Android/comments/irs1eb
Another permanent solution I've been using since MIUI 12.5 update on my POCO is to install Substratum Lite (root required) and nonavbar.apk. Then open Substratum Lite. For me it applied the changes at this point and I just had to restart the phone but you might have to select the Nonavbar theme in substratum then thick the "Android System (Android [11])" checkbox click "1 SELECTED" then click "install selected". Restart and go back to this screen to "Enable selected".
All credit goes to @Veiran for this solution.
gsus said:
Permanent solution requires rooted phone and can be done like this:
https://www.reddit.com/r/Android/comments/irs1eb
Click to expand...
Click to collapse
How can I bring it back?
EDIT: Figured it out just change " 1 " to " 2 " (props qemu.hw.mainkeys 2)
EEDIT: I can't remove it back again once I did the (props qemu.hw.mainkeys 2), how can I remove it again?
MocnePifko said:
Another permanent solution I've been using since MIUI 12.5 update on my POCO is to install Substratum Lite (root required) and nonavbar.apk. Then open Substratum Lite. For me it applied the changes at this point and I just had to restart the phone but you might have to select the Nonavbar theme in substratum then thick the "Android System (Android [11])" checkbox click "1 SELECTED" then click "install selected". Restart and go back to this screen to "Enable selected".
All credit goes to @Veiran for this solution.
Click to expand...
Click to collapse
Did this, works perfectly.
Hey guys,
There's a very simple method.
DON'T NEED ROOT!
1.Turn on the Gesture Navigation and keep the System Launcher default.
2. Remove all shortcuts from the system launcher, just put a shortcut to your favourite launcher.
Now, you can use it as normal, just needs 2 click for the home
BUT:
3.If you use the FNG (find in Play Store) along with the system navigation, you can set the Up Gesture (normally the Home) to launch your favourite launcher (mine is Total Launcher) and if you do the Home Gesture 99% your favourite launcher will come up
(1% you have to click on the shortcut on the system launcher).
avers said:
Hey guys,
There's a very simple method.
DON'T NEED ROOT!
1.Turn on the Gesture Navigation and keep the System Launcher default.
2. Remove all shortcuts from the system launcher, just put a shortcut to your favourite launcher.
Now, you can use it as normal, just needs 2 click for the home
BUT:
3.If you use the FNG (find in Play Store) along with the system navigation, you can set the Up Gesture (normally the Home) to launch your favourite launcher (mine is Total Launcher) and if you do the Home Gesture 99% your favourite launcher will come up
(1% you have to click on the shortcut on the system launcher)
Click to expand...
Click to collapse
Thanks bro! Using this technique now.
Thanks OP
Worked for me on my Mi 11 running MIUI 12.5.9 Global ROM
Using Nova with Edge Gestures app
Any new method?
After a few updates, I've noticed the Lock app feature, which allows you to never stop an application from working in the background, on my Redmi 9 disappeared completely. How do I bring it back? The Miui version is Miui 12.5.3.
SomeoneFromOuterSpace said:
After a few updates, I've noticed the Lock app feature, which allows you to never stop an application from working in the background, on my Redmi 9 disappeared completely. How do I bring it back? The Miui version is Miui 12.5.3.
Click to expand...
Click to collapse
I dont think you'll find a solution, on my 9a i bringed it back by using root & Lposed, with custoMIUIzer on 12.0.19 (Dont know if it'll work on your version)
Also, if you cant make it work, you can manually enable this option, just enter settings on the Security app and then on "Boost Speed", there you'll find a "Lock Apps", its exactly the same thing
Hello, everyone.
Lately I have been looking for a way to disable navigation bar on Stock rom, and use gestures on third party launchers, for example on Nova launcher. After trying different things, here what worked for me:
First, download Fluid N. G. app and set it (make sure the app stays working and the battery saver doesn't kill it). Don't hide the navbar using Fluid N. G., not only this won't work, but also will cause the navbar to reappear after every unlock. So, don't use the hide option from Fluid N. G. (see the screenshot below).
You also need Tasker app, So install it.
Since the device is not rooted, you need to grant some permissions for the Tasker app, in order to work. To do this, follow the instructions Here.
Once done, open Tasker app, select profiles and click "Import profile". The file that you need to import is in attachements. Enable it, reboot your device (wait for few seconds) and Voilà !.
I tried to keep it as simple as possible. The results are attached below. Good luck!
Mechalikh said:
Hello, everyone.
Lately I have been looking for a way to disable navigation bar on Stock rom, and use gestures on third party launchers, for example on Nova launcher. After trying different things, here what worked for me:
First, download Fluid N. G. app and set it ( make sure the app stays working and the battery saver doesn't kill it).
You also need Tasker app, So install it.
Since the device is not rooted, you need to grand some permissions for the Tasker app, in order to work. To do this, follow the instructions here :
https://tasker.joaoapps.com/userguide/en/help/ah_secure_setting_grant.html
Once done, open tasker app, select profiles and click "import profile". The file that you need to import is in attachement. Enable it, reboot your device (wait for few seconds) and Voilà !.
I tried to keep it as simple as possible, good luck!
Click to expand...
Click to collapse
Thank you @Mechalikh for sharing this hack, but what should I do if my phone is rooted? I have an redmi note 10 pro
Hellera said:
Thank you @Mechalikh for sharing this hack, but what should I do if my phone is rooted? I have an redmi note 10 pro
Click to expand...
Click to collapse
Although this one will work also on rooted devices, I believe there are better alternatives (for example editing build.prop..etc).
Here is a video showing the results
Mechalikh said:
Although this one will work also on rooted devices, I believe there are better alternatives (for example editing build.prop..etc).
Click to expand...
Click to collapse
Wow, it will be easier to edit build.prop... but I dont know what lines to edit... or any other easier alternative... Can you help me, please? Thank you.
Can you attach your build.prop?
Mechalikh said:
Can you attach your build.prop?
Click to expand...
Click to collapse
@Mechalikh, I tried what you said above but when is about to import the profile in Tasker it give an error, "profile not found"
By the way, the profile extension must be .prj.xml not .prf.xml.
I would also like to know more about hiding navigation buttons with build prop. I am on Miui EU rom on sweetin
I wish there was another way to keep fng running in background, instead of in recents always
Hellera said:
@Mechalikh, I tried what you said above but when is about to import the profile in Tasker it give an error, "profile not found"
By the way, the profile extension must be .prj.xml not .prf.xml.
Click to expand...
Click to collapse
Same error for me too
Tried qemu.hw.mainkeys 1 in build prop editor but it won't save.
Also, @Mechalikh I clicked on import project, but it says 'no profile found'.
Hellera said:
@Mechalikh, I tried what you said above but when is about to import the profile in Tasker it give an error, "profile not found"
By the way, the profile extension must be .prj.xml not .prf.xml.
Click to expand...
Click to collapse
I don't get it, I'm on Tasker version 5.15.12 ( the latest one). The extentions are : prf.xml for profiles and tsk.xml for tasks. Anyway HERE is how to do it manually.
Hide navigation buttons, no MIUI gestures.
If you use something like Piecontrol, Gesture Control or any other app to navigate your phone you might want to disable the navigation buttons. As /system can't be rw mounted we can't edit "build.prop" 1. Magisk, install "MagiskHide Props...
forum.xda-developers.com
Frag1le said:
Hide navigation buttons, no MIUI gestures.
If you use something like Piecontrol, Gesture Control or any other app to navigate your phone you might want to disable the navigation buttons. As /system can't be rw mounted we can't edit "build.prop" 1. Magisk, install "MagiskHide Props...
forum.xda-developers.com
Click to expand...
Click to collapse
This doesn't work on Miui 13 EU
Mechalikh said:
I don't get it, I'm on Tasker version 5.15.12 ( the latest one). The extentions are : prf.xml for profiles and tsk.xml for tasks. Anyway HERE is how to do it manually.
Click to expand...
Click to collapse
Thanks for your help. I do have root access but no idea how to do it through build props, so I will stick with this Tasker method. Cheers!
One thing though, FNG bottom gesture isn't as responsive as Miui gesture. Takes like a second to open recents. Found a good FNG file and imported its settings. Better now.
DreamStare said:
This doesn't work on Miui 13 EU
Click to expand...
Click to collapse
Not tested this myself yet, but i doubt this was removed on Android 12 or Miui 13, this is kind of a basic function.
That build.prop is telling the OS the device has hardware keys for navigation. I've been using this for perhaps 10 years now .
Thank you @Mechalikh for sharing this, I watched the video and I succeded it with Smart launcher... I'm using Smart launcher for years...
In my case it wasn't necesary the second task because the phone is rooted.
Edit: only one question please... Is anymore fluid navigation app needded after this?
Hellera said:
Thank you @Mechalikh for sharing this, I watched the video and I succeded it with Smart launcher... I'm using Smart launcher for years...
In my case it wasn't necesary the second task because the phone is rooted.
Edit: only one question please... Is anymore fluid navigation app needded after this?
Click to expand...
Click to collapse
This will only hide the navigation bar, gestures will not work, so before doing that, you need to install a gesture navigation app like Fluid n g.
From my understanding, in android 11 google disabled navigation gestures when not using the system launcher. Probably because third party launchers failed to integrate those animations correctly, which made them look laggy ( same when using fluid n. g. unfortunately)
You can see that in android 10 phones. When you change the launcher, the gestures will remain but there will be no animations.
So this is probably their way to avoid it.
if you look in the system Ui code you will find something like:
if( the launcher is system launcher)
enable gestures
else disable them.
if this is the case. A patched system ui app should do the job. i'll root my device this monday, and try to decompile the systemUI app to see if that's the source of our problem.
Mechalikh said:
This will only hide the navigation bar, gestures will not work, so before doing that, you need to install a gesture navigation app like Fluid n g.
From my understanding, in android 11 google disabled navigation gestures when not using the system launcher. Probably because third party launchers failed to integrate those animations correctly, which made them look laggy ( same when using fluid n. g. unfortunately)
You can see that in android 10 phones. When you change the launcher, the gestures will remain but there will be no animations.
So this is probably their way to avoid it.
if you look in the system Ui code you will find something like:
if( the launcher is system launcher)
enable gestures
else disable them.
if this is the case. A patched system ui app should do the job. i'll root my device this monday, and try to decompile the systemUI app to see if that's the source of our problem.
Click to expand...
Click to collapse
Source :
Android Q beta 5 won't let you use gesture navigation on third-party launchers
Android Q introduces a new gesture navigation control, but Google stops you from using third-party launcher apps with it.
www.xda-developers.com
well they said it has been the case since android 10. But i had a "honor" phone with gestures working fine on android 10 (but of course with no animations when using another launcher) .
Anyway, read that xda article to fully anderstand the issue.
Frag1le said:
Not tested this myself yet, but i doubt this was removed on Android 12 or Miui 13, this is kind of a basic function.
That build.prop is telling the OS the device has hardware keys for navigation. I've been using this for perhaps 10 years now .
Click to expand...
Click to collapse
My build prop editor gives an error when I try to save it. Bummer for me I guess, maybe because I am not on official MIUI
Android Auto - XLauncher Unlocked v2.0.1
Custom Android Auto launcher, unleash your AA app, unlock more features!
- Source code
- Documentation
- Releases
- XDA Thread
Features
NameDescriptionRoot requiredXposed requiredDefaultSet the next used launch option as defaultClassicLaunch the Android Auto settings, with the classic/stable styleMaterial3Launch the Android Auto settings, with the hidden/experimental Material3 styleDebugLaunch various hidden Android Auto debug screensXposed ModuleUnlock more 3th party Android Auto apps! (e.g. Fermata, OsmAnd, S2A, ...)
Description
XLauncher Unlocked is a separate app, to unlock more features in your Android Auto app.
It can launch existing / hidden Android Auto screens with root / ADB commands.
Classic can be launched without root.
If using the Xposed module,
then it will also hook into an existing Android Auto function,
to run some additional code behind it,
to make some of the "installed as Google Play" checks always come back as valid,
which does not modify the AA app itself.
Due to the nature of the implementation of the features,
you should not have to be afraid of "having to wipe AA data to test".
Because no AA data is touched / no AA files are edited in a persistent way.
Default "launch option"
The "Set the next used launch option as default" check-mark can be used to
automatically launch the "launch option" behind the button you click after checking the check-mark.
After a default "launch option" is configured, the next times you open XLauncher Unlocked,
it will automatically open that "launch option" for you.
This works for every "launch option" (Classic, Material3, Debug options),
and can easily be re-configured by selecting another "launch option" with the check-mark still configured.
Clearing/resetting the usage of the default "launch option" is as easy as un-checking the check-mark
Credits
Credits for the hooks from Fermata by @AndreyPavlenko!
New v2.0 release is out which added a bunch of launcher functions!
You can download it from GitHub: https://github.com/Rikj000/Android-Auto-XLauncher-Unlocked/releases/tag/v2.0
Thank you. Interesting app, I will have to play and investigate
I use PlayStore and Play Protect did not let me to install.
I could have to disable Play Protect but I repackaged your app and installed pretending it as it was installed by PlayStore (screenshot).
Now it runs ok and Play protect does not complain
I have just an observation about the main screen. Buttons don't fit to my display (probably since I use enlarged text) and there is no way to scroll and to read the cut-off part on the right side.
Screenshot attached
The other Material screens I tried were ok
Thank you for the feedback @zgfg
Just reworked the installation instructions,
now pointing users to KingInstaller to install the app.
I'll try to figure out a fix to make the UI display correctly on enlarged screens.
However, scrolling up/down appears to work when I enlarge my screen
What's the difference between Classic, Default and Material3? Do you have screenshots?
SOFO888 said:
What's the difference between Classic, Default and Material3? Do you have screenshots?
Click to expand...
Click to collapse
Classic launches AA with the 'classic' design, Material3 with the Material 3 design - screenshots
I suppose Default can make Material to become default style for the future launches (not necessarily from this launcher) but I don't want to wipe AA data to test
SOFO888 said:
What's the difference between Classic, Default and Material3? Do you have screenshots?
Click to expand...
Click to collapse
Classic = The old / default user interface.
Material3 = The new / hidden / experimental user interface.
Check the attached files for comparison screenshots.
Rikj000 said:
I'll try to figure out a fix to make the UI display correctly on enlarged screens.
However, scrolling appears to work when I enlarge my screen
Click to expand...
Click to collapse
I cannot scroll left/right to read the cut-off text (yellow boxed on the screenshot), like Trouble..., Feedback repo ..
zgfg said:
I suppose Default can make Material to become default style for the future launches (not necessarily from this launcher) but I don't want to wipe AA data to test
Click to expand...
Click to collapse
XLauncher Unlocked is a separate app which doesn't modify any Android Auto related things (files/settings).
It simply launches existing / hidden Android Auto screens with root / ADB commands.
And if using the Xposed module, then it will also hook into an existing Android Auto function,
to run some additional code behind it, to make some of the "installed as Google Play" checks always come back as valid, which does not modify the AA app itself.
Due to the nature of the implementation of the features,
you should not have to be afraid of "having to wipe AA data to test".
Because no AA data is touched / no AA files are edited in a persistent way.
Additional Docs - AA - XLauncher Unlocked - Default "launch option"
The "Set the next used launch option as default" checkmark can be used to
automatically launch the "launch option" behind the button you click after checking the checkmark.
After a default "launch option" is configured, the next times you open XLauncher Unlocked,
it will automatically open that "launch option" for you.
This works for every "launch option" (Classic, Material3, Debug options),
and can easily be re-configured by selecting another "launch option" with the checkmark still configured.
Clearing/resetting the usage of the default "launch option" is as easy as un-checking the checkmark
zgfg said:
I cannot scroll left/right to read the cut-off text (yellow boxed on the screenshot), like Trouble..., Feedback repo ..
Click to expand...
Click to collapse
I know, you've reported this earlier, v2.0 is not optimized to handle screen enlargement.
Work Around - GUI cropped on enlarged screens
To make the GUI display correctly, please open your Settings app and go to:
Display => Display size and text => Display size => Reduce the size by a few clicks.
Restore the Display size again once you're done playing with XLauncher Unlocked
and once you have a default "launch option" configured.
GitHub Issue: https://github.com/Rikj000/Android-Auto-XLauncher-Unlocked/issues/1
Thank you very much for the screenshots.
I thought the app will change the Android Auto view in the car. But the app changes the Android Auto phone app. Thank you very much for the clarification.
Maybe I missed in the menus... Is it possible to have the option to switch on/off CoolWalk view in the car
It is possible by AA AIO Tweaker but I don't know is it just some setting for AA or AIO Tweaker has to tweak the AA db
New v2.0.1 release is out which fixed the non-scroll-able Debug "launch options" section on enlarged screens!
You can download it from GitHub: https://github.com/Rikj000/Android-Auto-XLauncher-Unlocked/releases/tag/v2.0.1
zgfg said:
Maybe I missed in the menus...
Is it possible to have the option to switch on/off CoolWalk view in the car
Click to expand...
Click to collapse
It's not possible with AAXLU (Android Auto XLauncher Unlocked),
but afaik it should be as simple as renaming following file at
/data/data/com.google.android.projection.gearhead/files/phenotype/shared/
- From: com.google.android.projection.gearhead.pb
- To: com.google.android.projection.gearhead.pb.bak (Or smth similar, al long as the original "doesn't exist")
Then close Android Auto / reboot.
That file is at least what was required to make CoolWalk / TaskBar-Widgets work / appear on MicroG.
Rikj000 said:
New v2.0.1 release is out which fixed the non-scroll-able Debug "launch options" section on enlarged screens!
You can download it from GitHub: https://github.com/Rikj000/Android-Auto-XLauncher-Unlocked/releases/tag/v2.0.1
Click to expand...
Click to collapse
Thanks. Fixed in this v2.0.1
Rikj000 said:
Android Auto - XLauncher Unlocked v2.0.1
Custom Android Auto launcher, unleash your AA app, unlock more features!
- Source code
- Documentation
- Releases
- XDA Thread
<snip>
Credits
Credits for the hooks from Fermata by @AndreyPavlenko!
Click to expand...
Click to collapse
Thanks a million for this app/ Xposed module. All I needed was to make "unauthorized apps" to work, and until recently, the only way to do that was cumbersome phenotype.db edits with triggers (battery drain!) and wiping AA data.
Working perfectly for me, count me in for a follower/ tester/ anything I can do to help!
News/update, only for MicroG users:
aaxlu (v2.0.1) now comes pre-included with aa4mg (v0.6)
If you manually installed aaxlu before,
then please uninstall aaxlu, before you install aa4mg v0.6.
ph03n!x said:
Thanks a million for this app/ Xposed module. All I needed was to make "unauthorized apps" to work, and until recently, the only way to do that was cumbersome phenotype.db edits with triggers (battery drain!) and wiping AA data.
Working perfectly for me, count me in for a follower/ tester/ anything I can do to help!
Click to expand...
Click to collapse
I think I must be missing something. I have root and the lsposed module installed etc. I have Screen2Auto installed but the app isn't visible in Android Auto. What are the steps to get third party apps to work? Thanks
Edit: more info. Have magisk, zygisk and lsposed module activated
FredQ said:
I think I must be missing something. I have root and the lsposed module installed etc. I have Screen2Auto installed but the app isn't visible in Android Auto. What are the steps to get third party apps to work? Thanks
Click to expand...
Click to collapse
S2A is by far the most restricted app.
I've posted all restrictions/by-passes which are within my knowledge in the S2A thread:
https://forum.xda-developers.com/t/...r-root-devices.4062787/page-147#post-88392893
With those steps I've been able to get S2A showing up reliably.
Maybe I've missed something but what is the purpose of this app, other than to change the look of AA settings? What other 'hidden' features does it show, other than to be found in Developer settings? Thanks.