Related
As the title states, does anyone know of an app that I can launch and load a specific image file without having to navigate to or choose a file every time? Or maybe a script (dunno if you can put a script in a slider shortcut though)
I have my contact info in a QR code and I want to be able to display it from a lockscreen slider shortcut quickly. I want to choose the shortcut and have the QR code display on-screen without further user intervention.
This is the best way I could think to do it, without requiring multiple touches after selecting the unlock shortcut.
Please don't ask me to code it myself, I'm not a dev.
thx in advance.
I changed my DPI systemwide to 560. The dialer, lockscreen and camera become off set. So I downloaded app settings through xposed and changed dialer and camera DPI back to 640 and solved the off set issue. However I can't find the actual file/app name for the lockscreen. There's 100s of system files/apps to choose from. Does anyone know what the actual lockscreen is called. For example com.android.security or something like that. If anyone knows it would be great. I don't want to edit 300 systems apps one by one until I fix my lockscreen. I've tried apps simular to security but nothing changes my lockscreen DPI back to 640.
It should be keyguard if memory serves me right
That was like the second or third one i tried. Didnt fix it
mgbotoe said:
It should be keyguard if memory serves me right
Click to expand...
Click to collapse
You were right. Thanks. there was 2 different keyguard entries and both together solved the problem
budco2000 said:
You were right. Thanks. there was 2 different keyguard entries and both together solved the problem
Click to expand...
Click to collapse
RESOLVED: Found another thread that talks about this and has the fix --> Make sure that "Apply res to widgets" is CHECKED in com.android.keyguard along with DPI 640 AND reboot. There is only one entry and not two. It is com.android.keyguard. See link: http://forum.xda-developers.com/not...anging-note-4-dpi-settings-to-change-t2923408
Hi budco2000, I am having the same problem as you on the lockscreen once I changed my system wide DPI.
Using Xposed's App Settings, I can only find one entry of keyguard (com.android.keyguard) and not the second one like you mentioned. I tried different keywords like "key", "guard", "pin", "lock" and still not able to find the second keygurad entry. So, my lockscreen's PIN pad is still not aligned.
Can you please tell me what's the second entry you are referring to, please? I am using the same T-Mobile's Note 4 on AT&T
Thanks
huoyjii said:
RESOLVED: Found another thread that talks about this and has the fix --> Make sure that "Apply res to widgets" is CHECKED in com.android.keyguard along with DPI 640 AND reboot. There is only one entry and not two. It is com.android.keyguard. See link: http://forum.xda-developers.com/not...anging-note-4-dpi-settings-to-change-t2923408
Hi budco2000, I am having the same problem as you on the lockscreen once I changed my system wide DPI.
Using Xposed's App Settings, I can only find one entry of keyguard (com.android.keyguard) and not the second one like you mentioned. I tried different keywords like "key", "guard", "pin", "lock" and still not able to find the second keygurad entry. So, my lockscreen's PIN pad is still not aligned.
Can you please tell me what's the second entry you are referring to, please? I am using the same T-Mobile's Note 4 on AT&T
Thanks
Click to expand...
Click to collapse
Apply res to widgets!
Introduction
Remember a time when an unthemed popup popped up in an app, and you tried all that you could to change the colors of it, then found out it wasn't even in the app you spent hours on at the first place? Damn right I do!!! Wasted so much of my youth looking for things in the wrong place.
In this guide I will be going over a desktop application called "Android Device Monitor", and how to use it for theming. This program is not bound to theming, as it can help many ROM developers like locating a CP'd commit and forgot where to set a textColor was set in a dialog. For example: https://github.com/TeamBliss-LP/and...mmit/4f85ee62ab0db9d2a78b1bfeee32dfa17313e215.
The guide will also outline other methods to locate hardcoded colors on most apps, and this is not bounded by device. This will theoretically work on any device running Android, as long as you enable USB debugging on your device. So it should theoretically work on TouchWiz, AOSP, CM, Sense, LG Home, XperiaHome, etc...
Most importantly, if your friend comes over with a non-rooted phone, fret not, this DOES NOT require root. So! If you happen to stumble here from a link I requested you to follow, I'll assume you're either a themer, or you're a user of a theme. For users, this guide would be used to aid the themer when the themer does not have access to what you are seeing in an app due to differences in software/region bound software/firmware versions/custom ROMs. For themers, I hav known about this trick for a while but haven't gotten the time to write it - but this saves me precious time solving "unsolvable" issues, like during the days when we didn't have Setting's dashboard exposed (before the January 27th commit).
To understand how this works, we have to understand how Android system works. We can change many colors through colors.xml, but styles, layouts and java can also change colors. We have to remember this structure. Left is greater than the corresponding right.
Java > Layout > Styles > Colors
In this guide, I will be focusing on using ADM to locate colors/usages of resources within Layouts, thus allowing you to locate things within styles/colors.
ATTENTION
This guide is NOT 100% guaranteed.
As many third party apps like Google+ designs it's layout through the java, and the overall code of the application. Using Android Device Monitor, it is the first steps of beginning to theme.
This guide is meant to be a STARTING GROUND when you face any issue. I cannot guarantee any success, but this has helped me find out whether many things are hardcoded or not. So having this as a utility will greatly help a lot of people new to theming!
I also do NOT have access to a TW/Sense/LG Home/XH device, so if you have any issues (non-connection issues) with using ADM to trace your screen, please tell me. But theoretically, this should work on any device.
What is Android Device Monitor?
Android Device Monitor is a desktop application that traces the running programs of your device connected to your PC. You can use this to debug as it shows many useful information.
But for this guide, I will use it to show how to use it to take a screenshot XML dump of your phone's screen, and you can mouseover the elements of your screenshot on your screen to locate the layout of the app, or whatever is on your screen.
Wow! That sounds cool! How do I get it?
All you have to do is install the Android Studio package from Google, and you will get it preinstalled with it.
You can download Android Studio from this link: http://developer.android.com/sdk/index.html?gclid=CLWt6IX99MgCFRCpaQodrhwHng
Make sure you install the prerequisite packages once installing and setting up Android Studio. This includes the complete SDK.
If you would like to install just the SDK, that is possible too: https://developer.android.com/sdk/installing/index.html?pkg=tools
Make sure you install Android SDK Tools in the SDK Manager. Android Studio method is recommended as it comes with everything pre-installed once setting everything up.
Let's get started, shall we?
(*) Make sure you have installed adb/fastboot on your computer prior to continuing: http://forum.xda-developers.com/showthread.php?p=48915118
A great text editing tool is Notepad++, available here: https://notepad-plus-plus.org/
ON YOUR PHONE/TABLET
I will be using a Lollipop based CM ROM in this tutorial. Keep your device unplugged at this point.
First you have to enable Developer Options by going into About Device in Settings, then clicking the Build number 7 times. This enables Developer Options directly in the main menu of Settings.
Once activated, go into Developer Options
Scroll down until you see Android debugging, then activate that.
Plug your phone into the computer
At this point, a popup will appear on your device to verify the RSA fingerprint of your computer. Click Always Allow from this Computer.
ATTENTION: If you did not get a popup, adb is NOT installed correctly/your phone is not detected in ADB mode, or your computer does not have it set up properly. Follow my link above to get it set up quicker than using Android Studio's method. (*)
Once you agreed to the popup, then go to the screen where you want to see what the problem is. For example, you want to find out why there is a random white dialog when toggling GPS telling you to improve location accuracy.
Keep the screen turned on/turn on Stay Awake in Developer Options so it will keep your phone awake while plugged in. After this step, you have successfully finished using your phone.
ON YOUR COMPUTER
ATTENTION: If you already use Android Studio to build your theme, you can skip steps 2 and 3. Also to note, you can always use search and locate the "monitor.exe" file in your Android Studio directory, but that is too fussy, as it likes to error out a lot.
Open Android Studio, and create a new project, you need to Start a new Android Studio Project, follow all the steps till you click Finish.
You may or may not be greeted with a couple of popups, just dismiss them.
Once you get to a window with an available toolbar, click on Tools -> Android -> Android Device Monitor.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ATTENTION: If you're running Android Studio 1.4.1 and above, click on the icon in the toolbar.
On first launch you will get this popup, click Proceed
Your phone will appear on the left, including all the processes and background services running on your phone.
Click on your device, and click on the Dump View Hierarchy for UI Automator icon, an icon that should be next to the camera, with three stacked phones.
At this point, the computer will dump whatever is on your screen, if your screen is off, it will dump a black screen, so you should have kept it awake.
Once complete, you will want to hover over the unidentifiable object on your screen. So if the white dialog (as mentioned previously) when toggling location is a bother, we hover over the screen's focused dialog, and click on it. When selected, the area has a red rectangle.
You will then see a table on the bottom right identifying all its attributes. But most importantly, you will want to see that it is actually in package ID com.google.android.gms (Google Play Services), so you must invert that/theme that.
You can see how the table above told me that the package ID was com.google.android.gms, and thus I was able to go find it in the decompiled APK of Google Play Services.
Also to note, resource-id is also a great way to start, as it tells you the app's layout object ID, which allows you to find it within the app's res/layout folder by using Notepad++ and the Find in Files section. If by any chance, you get no information at all, you should check the structure of the app on the top right, and locate within layouts folder as well. For example, if you see a FrameLayout and textView x2, you have identified the structure of the activity fragment of the app, and it MAY help you for layouts.
In my commit at the beginning of this thread, I was locating an unthemed black text in a dialog, and found out that the dialog's resource-id was "dpi_edit", so I searched in res/layout using N++'s Find in Files tool and found out that it was in this file: https://github.com/TeamBliss-LP/and...13e215/res/layout/alert_dialog_text_entry.xml. So I made the change to the textColor and pushed the commit to the source. Thus allowing users to have a visible DPI text color, even though we expected that the ?attr should work.
Demonstration on how to reverse locate a specific color
Let's find something specific using this trace method, so for example, I would like to find the background of the switch bar in Settings. Pretend I don't know how. So following my above steps, I'm able to reach this:
We see that under resource-id in the Node Detail box, it says: com.android.settings:id/switch_bar -- so we should search for switch_bar under res/layouts of com.android.settings (your decompiled settings).....
We go into Notepad++, and use the Find in Files feature (Search -> Find in Files) and type in the resource-id after ":id/", which is "switch_bar"
Click Find All and wait for it to finish. Afterwards, you will get a list of results with a hit. In this case, we have one result.
Double click on the result, and you will be greeted with a layout XML with the ID. In the XML you will see that you have a bunch of stuff there, so with some smarts and some logic on the same line, you can see if the background is set to a hardcoded hex (hardcoded meaning there's a hex code there, as you can't modify layouts in CMTE, or is it rerouted to another color)
We can see that the background was linked to a color variable, "switchbar_background", now change that in com.android.settings/res/values/colors.xml, then you tell me if I'm correct If you see something else in there, or are a ROM developer and trying to expose some values, replace the hardcoded hex to a rerouted color in the corresponding app's colors.xml, and you have successfully exposed it!
Troubleshooting
Q: There is an error every time I launch ADM again! What should I do?
A: The error is normal, just press OK and proceed. (This error in spoiler, if any others, message below)
Q: I keep getting a permission error with my device when I click the button and it doesn't draw my screenshot!
A: This happens when your device is extremely "dirty", a complete clean flash is required. In my case, I fastbooted stock and reflashed my custom ROM. You can try wiping data, as the permissions lie somewhere there.
Q: I still can't get my theme to theme the hardcoded thing, help!
A: As I said, this doesn't work for all cases, this is only a starting and ending ground to see if it is themable. If you can't find out what to do, then chances are you did everything you can!
Q: Any other tips?
A: If you really can't find it, but you have a specific color you want to get rid of, try using Photoshop's Eyedropper tool to pick out the color from the screenshot, then use Notepad++ to search for this color. You should find the hex from the color by clicking the color palette.
Q: What about using backgroundTint?
A: You can use this to target many white hardcoded (definite) backgrounds by adding a backgroundTint attribute, but this may affect other things, like the Paste tooltip will take on this backgroundTint thus you can't read the "Paste" text. But definitely, this is a great way to start targeting white backgrounds!
Q: I have more questions!
A: Post in the thread and tag me using @nicholaschum, I'm more likely to check if I get a notification.
XDA:DevDB Information
[GUIDE] Locating hidden values, random dialogs and hardcodes (AOSP/TW/Sense/XH), Theme for all devices (see above for details)
Contributors
nicholaschum
Version Information
Status: Stable
Created 2015-11-03
Last Updated 2015-11-06
Reserved
Reserved
Thanks.
Sent from my GT-I9100 using XDA Free mobile app
I always get a black screen on my PC. How can I solve it? My phone screen is always on.
Thank you for the guide.
starbucks2010 said:
I always get a black screen on my PC. How can I solve it? My phone screen is always on.
Thank you for the guide.
Click to expand...
Click to collapse
Hmm, that's a bit strange, because black screen is mainly when your screen is off, are you seeing the background processes of the app on the left of ADM?
Solved. Actually, I have to have the screen on in the moment I start to take the "screenshot" of my phone. It's ok now.
I'm still looking for that white contact detail background ...
PS. Do you know what it means class = android.widget.RelativeLayout ? It doesn't give too much details so I don't know where should I search for it?
Thank you.
starbucks2010 said:
Solved. Actually, I have to have the screen on in the moment I start to take the "screenshot" of my phone. It's ok now.
I'm still looking for that white contact detail background ...
PS. Do you know what it means class = android.widget.RelativeLayout ? It doesn't give too much details so I don't know where should I search for it?
Thank you.
Click to expand...
Click to collapse
That means that the layout is using a RelativeLayout. It's a type of layout configuration. You should use N++ to see if you can find that RelativeLayout, as not all xmls have that layout.
Sent from my Xperia Z3 Tablet Compact LTE using Tapatalk
Thank you, great guide!
For themers, this is the best guide and most useful, ever. It should be a sticky.
Thank you very much Nicolas.
Well, in the new version of Android Studio, there's no option for UI, Only Camera / Print, and other Monitor related options.
abo hani said:
Well, in the new version of Android Studio, there's no option for UI, Only Camera / Print, and other Monitor related options.
Click to expand...
Click to collapse
I'll take a look at this, I might make a standalone package if this is the case.
@abo hani, updated the guide with Android Studio 1.4.1 instructions to locate ADM. Once ADM launched, it works exactly the same way now.
Thank you so much. This is a perfect tool for somebody like me trying to catch up to all the great themers on here. At least I can help myself and ask better questions.
Thank you for this guide
Do you have any tips on how to make a transparent background transparent instead of grey? I have changed backgrounds edited pngs edited styles and manifests and still get a grey box on the light option
rickberg said:
Do you have any tips on how to make a transparent background transparent instead of grey? I have changed backgrounds edited pngs edited styles and manifests and still get a grey box on the light option
Click to expand...
Click to collapse
If a transparent background is already transparent, why are you changing it to grey? What changes are you making?
I worded that wrong im trying to make the apk transparent but it will not go transparent it goes to a grey i added Theme.Translucent to styles and manifest also changed background hexes on light to 00000000
Anyone knows from where is taken the color of the text in the search box? Is taken from the app itself of from somewhere else (SystemUI, framework, etc)? It drives me crazy this search text from SecGallery. Is always black on black.
Thank you.
nicholaschum said:
If a transparent background is already transparent, why are you changing it to grey? What changes are you making?
Click to expand...
Click to collapse
This is the color i get as background even though everythong is set to transparent
Sent from my SM-N920P using Tapatalk
A module which applies a "true" value across all installed apps to enable multi-window display mode without using the workaround of the Developer Options toggle, which would also remove the unsightly system message that pops up when using split screen with "incompatible" apps, noting, "This app may not work with Multi window."
Per https://developer.android.com/guide/topics/ui/multi-window
Set this attribute in your manifest's <activity> or <application> element to enable or disable multi-window display:
android:resizeableActivity=["true" | "false"]
If this attribute is set to true, the activity can be launched in split-screen and freeform modes. If the attribute is set to false, the activity does not support multi-window mode. If this value is false, and the user attempts to launch the activity in multi-window mode, the activity takes over the full screen.
Click to expand...
Click to collapse
Effectively, this is "editing" the APK's manifest to declare it resizeable without needing to do it manually one by one, and avoids the signing issues that may come with doing this on a system/app level.
Thoughts?
nickthaskater said:
A module which applies a "true" value across all installed apps to enable multi-window display mode without using the workaround of the Developer Options toggle, which would also remove the unsightly system message that pops up when using split screen with "incompatible" apps, noting, "This app may not work with Multi window."
Per https://developer.android.com/guide/topics/ui/multi-window
Effectively, this is "editing" the APK's manifest to declare it resizeable without needing to do it manually one by one, and avoids the signing issues that may come with doing this on a system/app level.
Thoughts?
Click to expand...
Click to collapse
There's a toggle in Dev options that does this already?
Why workaround that?
nickthaskater said:
Yes, I referenced that toggle in my original post...
I said why in the OP: so that you don't need to use the Dev toggle and so that you don't get the annoying system message "warning" you that the app may not be compatible with multi window.
Seems like you didn't read beyond the subject line.
Click to expand...
Click to collapse
.....
First... Magisk doesn't mod apks individually like you want...
You're looking for Xposed...
Unless something in framework could be found... Then you could insert the apk with your mod...
Seems like you didn't read beyond the module part when talking about Magisk...
Thread cleaned no need for names or trolling if I get called back out here there will be infractions issued so lets both treat each other with kindness and respect ya?
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.