[Wrong section] xposed framework module idea - Xposed General

MOD EDIT: Thread closed as this is the wrong section for module requests/questions. Please read these guidelines for more info.
Can we have another module feature for app mutiwindow. However, this time, after selecting the "always"or "only once" pop up screen, id like to have a select a multi-window app? For example, im in official fb app, and I click a url. Then, a pop up comes up, sqare box, with apps to open with. Next, select an app. Now here goes my idea, after app choice selected;a new window appears. Now, in this window, it will ask "use multi-window." Lastly, click yes or no.
Thanks in advances.

Related

[Q] Xposed Module for modyfing recents floating menu

Hi
Is there any xposed module, which would let me modify the list that is being shown upon long clicking the tasks in Recents screen? By default, those are:
1) Remove from list
2) App info
I'd like to remove the #1, but most importantly add to it "Uninstall" option and also "Clear data" option, that are available from "App info" screen of an app.
Anybody willing to help me out and point me to a module which allows it (if there is none, and someone searched for it, I'd appriciate info like that also)
Lucas
If anyone knows of any way to achieve it, please respond.
Lucas

Cannot install any module

Hi there,
I'm running Android 4.2.2 and have the following issue, which I just noticed yesterday.
I am able to download Xposed Framework modules, but can't install them: I hit the "install" button within the module page, but then, when I am to select between "install" and "cancel" (i.e. in the permission page), I find that the "install" soft button is not enabled, while "cancel" button is.
So far, for some modules, I've been able to sidestep this by going through the Play Store, but I'm not sure all the modules are in there.
Any help would be appreciated. Thanks a lot.
this happened for me when a screen filter app was enabled. Do you use one?
Rodrigo Porto said:
this happened for me when a screen filter app was enabled. Do you use one?
Click to expand...
Click to collapse
So just for reference you're saying apps like Twilight, Bluelight Filter, CF.Lumen, and others can cause bootloops with xposed?
I'm using Screen Filter, that isn't a xposed module. I'm saying that problem you have with "install" button is because of apps like Screen Filter, they don't allow you to install apps manually.
Sorry bad english

Screen overlay

I have a problem with my note 5. Everytime i open new app that i install to my note, always ask about permission and if i choose allow there is popup said turn off screen overlay. What should i do?
Quick Solution for screen overlay problem
aleca said:
I have a problem with my note 5. Everytime i open new app that i install to my note, always ask about permission and if i choose allow there is popup said turn off screen overlay. What should i do?
Click to expand...
Click to collapse
Just disable all apps which appears when you tap 'open settings'.
And from 'more options' disable system apps too.
You must be good to go.
Thank you its working.
I got the same issue.
It caused by facebook messenger apps.
When the application asks for permission, there will be a permission pop up display on screen, if there is any application run with screen overlay mode (just like facebook messenger or its chat head) , It will overlap the permission pop up and users will not be able to see it. After a few hour workaround with it. I found the way to resolve it without disable the screen overlay that is close the facebook messenger as well as its chat head then try again with the apps with require permission.
If the problem still occurs, Press the "List" button and end all the background applications.

Hide the toast message *App* has obtained Superuser permissions

Hello!
I'd really like to disable the toast in the subject, possibly selectively for selected apps. The case is "Pixel Launcher Mods" which requests root access from time to time, I trust the app and it's annoying to randomly see the notification.
Thank you very much!
elegos said:
Hello!
I'd really like to disable the toast in the subject, possibly selectively for selected apps. The case is "Pixel Launcher Mods" which requests root access from time to time, I trust the app and it's annoying to randomly see the notification.
Thank you very much!
Click to expand...
Click to collapse
You can remove the toast notification completely in Magisk Manager settings (toward the bottom) but not selectively on a per app basis.
In the superuser tab of the Manager press the app name and switch the notification toggle. If you're using the Canary Manager you long press the app name.
Done.
Didgeridoohan said:
In the superuser tab of the Manager press the app name and switch the notification toggle. If you're using the Canary Manager you long press the app name.
Done.
Click to expand...
Click to collapse
Awesome, thanks! I reached that page, but wasn't clear how to enter the sub-menu (I thought that tapping on it would disable the root access).

[Release][v2.0.1] Android Auto - XLauncher Unlocked (AAXLU)

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
Name​DescriptionRoot required​Xposed required​Default​Set the next used launch option as default​​Classic​Launch the Android Auto settings, with the classic/stable style​​Material3​Launch the Android Auto settings, with the hidden/experimental Material3 style​​Debug​Launch various hidden Android Auto debug screens​​Xposed Module​Unlock 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.

Categories

Resources