Related
This has been fixed xda postNote: This is a temporary solution until someone fixes this in Xposed. Also I use my module "SnapColors" as a example throughout this post but this fix should for work any module. I've tested it with other modules and it works. If the module did not previously work on 5.0 then ignore this post and continue on with life.
TL;DR Version:
I found a temporary solution of getting modules to work on 5.1 for modules that worked on 5.0 but don't work on 5.1.
Non-TL;DR Version: Backstory and how I found his temporary solution
So a couple days ago I decided to start working on bring my module(s) to Xposed running on 5.1. In doing so what I noticed with a lot of the modules they seem to crash the app without throwing any kind of error whatsoever. Take for example one of my modules "SnapColors", if SnapColors was enabled in Xposed Installer SnapChat would always crash without throwing any error it wouldn't even say anything along the lines of "process has stopped unexpectedly" it would just close the app. So because of this behavior it led me to believe something was wrong with Xposed and not with my module(s). So I went thought what could be broken in Xposed thats causing this because 5.0 is just one up to 5.1 so the changes couldn't be that big. I went though the things that could cause this and came across "dalvik-cache" I remember reading somewhere Xposed makes some changes to the cache file (.dex) thats created during the creation of dalvik-cache files. So then I thought what if in 5.1 a small change was made to the process of making the dalvik cache files and thats what is causing the problem. So I decided to delete the dalvik cache file for SnapChat which is what my module was hooking into, then I tried opening SnapChat again but it crashed so I tried opening it again and what do you know it opened without any problems with my module fully working without any problems. The fix was kind of a guess too.
The fix/Solution
Note: If you reboot your device you have to do the fix again. Also you are deleting the dalvik cache so you won't benefit from it any more for the app(s) you delete it for. Unless you reboot then everything gets reverted.
What you have to do is delete the dalvik cache file for the app the module is for.
Example: SnapColors a module for SnapChat, so we have to delete the dalvik cache file for SnapChat.
What you need:
1) A file manager with root access, or terminal knowledge.
2) Package name example for SnapChat its "com.snapchat.android". How to get the package name look below theres a how to.
Steps for deleting the cache file:
Make sure the app is not running in the background close it if it is.
Method 1) Via terminal command:
Code:
cd /data/dalvik-cache/arm/ && rm [email protected]@"package name here without the quotes"*
Example command for SnapChat would be don't forget the "*" at the end:
Code:
cd /data/dalvik-cache/arm/ && rm [email protected]@com.snapchat.android*
Method 2) Via file manager: Navigate to /data/dalvik-cache/arm/ look for a file starting with the name [email protected]@"package name here without the quotes".apk delete this file and thats it.
Now try and open the app if it doesn't work close the app then try opening it again. make sure that apps not running in the background before trying again.
Getting package name
Via terminal command:
Code:
ls /data/data/ | grep "the app name here without quotes"
Via app: Install https://play.google.com/store/apps/details?id=com.electricsheep.asi
Open it-> Apps tab-> Tap the app-> look for "Package name:" should be the first thing.
Great job figuring that out! I hope @romracer takes a look at it and releases an update with permanent fix
mmamedov said:
Great job figuring that out! I hope @romracer takes a look at it and releases an update with permanent fix
Click to expand...
Click to collapse
Yup. I wish I could help but my knowledge of c++ is limited.
Why are apps on 5.1 creating this dalvik file if the runtime is ART?
r25txe said:
Why are apps on 5.1 creating this dalvik file if the runtime is ART?
Click to expand...
Click to collapse
The files are used by art despite the name of the folder "dalvik-cache". I think don't quote me on that.
Subscribed
sent from your moms phone
Can I get gravitybox to work?
Sent from my Nexus 5 using XDA Free mobile app
Programming4life said:
Yup. I wish I could help but my knowledge of c++ is limited.
Click to expand...
Click to collapse
Enough knowledge to help me out on twitter ALLLL the time! Lol
Great Finding. Thanks for the info.
Any chance of getting work Xposed GEL setting with CM12.1 Android 5.1
Thanks
lolzas said:
Can I get gravitybox to work?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For module related stuff post on there thread. Getting modules to work is on the dev of the module.
mjrifath said:
Great Finding. Thanks for the info.
Any chance of getting work Xposed GEL setting with CM12.1 Android 5.1
Thanks
Click to expand...
Click to collapse
For module related stuff post on there thread. Getting modules to work is on the dev of the module.
Another step into 5.1 with xposed.. Only needs rovo magic Touch.. Thanks for it...
Programming4life said:
For module related stuff post on there thread. Getting modules to work is on the dev of the module.
Click to expand...
Click to collapse
So can you tell us what are those 95% modules for xposed on Lolli 5.1?
Can you give us some examples what modules are working on your smart phone with your metods?
Thanks...
spaxon said:
So can you tell us what are those 95% modules for xposed on Lolli 5.1?
Can you give us some examples what modules are working on your smart phone with your metods?
Thanks...
Click to expand...
Click to collapse
I said ~95% because some modules need to be updated strictly for lollipop and won't work no matter what. Its more like 99% but 95% just in case.
Programming4life said:
The fix/Solution
Note: If you reboot your device you have to do the fix again. Also you are deleting the dalvik cache so you won't benefit from it any more for the app(s) you delete it for. Unless you reboot then everything gets reverted.
Click to expand...
Click to collapse
Something I dont understand, for almost every module in xposed on every version of android, you must enable that module in xposed and reboot smartphone to get it work... is it true?
I have tried Gravitybox LP and some more modules like Flat Style Bar Indicators, with deleting them in /data/dalvik-cache/arm/ but they dont work at all, i have tried couple of times starting them.
Also I tried deleting them in twrp file manager and I have bootloop (but no worries I deleted those modules and started the phone )
Am I doing something wrong?
spaxon said:
Something I dont understand, for almost every module in xposed on every version of android, you must enable that module in xposed and reboot smartphone to get it work... is it true?
I have tried Gravitybox LP and some more modules like Flat Style Bar Indicators, with deleting them in /data/dalvik-cache/arm/ but they dont work at all, i have tried couple of times starting them.
Also I tried deleting them in twrp file manager and I have bootloop (but no worries I deleted those modules and started the phone )
Am I doing something wrong?
Click to expand...
Click to collapse
After installing a module you must enable it and then do a reboot/soft reboot yes that is true. Gravitybox LP and Flat Style Bar Indicators both modify the android system itself so theres nothing we can really do until someone fixes this bug in Xposed's code.
What if we modify the permissions or the file itself so we don't have to constantly delete it upon reboots?
Sent from my Nexus 5 using Tapatalk
Youtube background playback don`t works with that method
FuMMoD said:
What if we modify the permissions or the file itself so we don't have to constantly delete it upon reboots?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Android doesn't like it when the permissions are changed for a cache file so it'll just fc the app.
jabarel said:
Youtube background playback don`t works with that method
Click to expand...
Click to collapse
Worked for me you may have a out dated version of YouTube or YouTube background.
Ive read that Xposed for Lollipop has issues with Sygic.
Is this true??
UPDATE 2015 10 10: rovo89 has taken a personal look at the problem and it seems to be fixed in later versions of Xposed. Here is his comments thruout this thread if you don't want to read the entire thread (like I had to do):
rovo89 said:
Could you try this test build please? It fixes a problem that results in crashes (dump contains "art::Field_get"). It also disables Xposed's resource hooking mechanisms inside the Sygic process, as they have implemented something very similar which also replaces resources at low level.
Click to expand...
Click to collapse
rovo89 said:
Forgot to mention that after flashing this, you have to clear the Dalvik cache or reinstall Sygic. Obviously, tests only make sense if you're using the original/unpatched app and experience crashes with Xposed v70.
Click to expand...
Click to collapse
rovo89 said:
That's totally correct, but for the average user, it's a much simpler to simply delete the whole cache or reinstall the app.
Cool, thanks for testing! So I'll publish an official update soon with these fixes and also commit and push them to GitHub. I'm pretty sure that the authors of unofficial versions will quickly pick them up.
Click to expand...
Click to collapse
rovo89 said:
There's already an option that disables resource hooking completely for the whole ROM. That's useful in case the ROM itself comes with resource-modifying code. Sygic is the first application I'm aware of that "hacks" the system code at such a low level. So I don't think such an option would be required, and in most cases, people wouldn't know exactly when to use it, which would result in strange bug reports for modules which stop working if you disable the wrong thing.
Click to expand...
Click to collapse
rovo89 said:
Are you referring to my comments above? I just said they're modifying resources. Didn't check what they do with that in details, maybe replacing drawables/texts on the fly? I haven't checked whether they do any changes to GPS.
Click to expand...
Click to collapse
rovo89 said:
Not crashing for me with the (expired) trial. Maybe you block access to contacts with some app or module?
Click to expand...
Click to collapse
rovo89 said:
Sygic is working fine for me with v71 - as much as I could test without buying premium. If you still have issues, please send me the logcat of the crash. I can't exclude that there are still issues, but I can't look at them without the log.
Click to expand...
Click to collapse
rovo89 said:
I can't make any sense out of this. It's looking for the class com.flurry.android.FlurryAgent and can't find it. It doesn't seem to use the app's class loader though but the system class loader, so maybe that's a bug on their side. Then again, this might not even be the root cause, as it only tries to load this class because something in Android_ContactsReadNext seems to have failed. If you use any kind of privacy app or ROM feature that might block access to contacts, that could be the reason. It might also be a contact with invalid or too long fields. Have you tried if the same issues appear without Xposed?
Click to expand...
Click to collapse
rovo89 said:
You probably mean the general issues with Sygic that I've fixed with v71. There seems to be an (individual?) issue where the app still crashes when going to the contact selection, but works fine otherwise.
Click to expand...
Click to collapse
Sygic 15.2.2 works with Xposed on my Galaxy S5 with LP
godmode1970 said:
Sygic 15.2.2 works with Xposed on my Galaxy S5 with LP
Click to expand...
Click to collapse
Downgrading to 15.0.4 works. Anything else just fails.
Im sure it is NOT a Sygic problem, its Xposed interfering with Sygic.
@alemtro
How can i delete xposed (to get back SYGIC working) and fix the messaging app crash ( 8.1.1) ??
Same here on One M8 with stock lollipop 5.0.2 ROM. Sygic works only till 15.0.4.
Sygic crashes with Xposed for Lollipop on Moto G 2014
On Moto G 2014
... crashes on Motorola Stock ROM 5.0.2
... crashes on CM12.1 (5.1.1)
Sygic version: 15.1.15
(works fine with Xposed on KitKat)
rabah5 said:
@alemtro
How can i delete xposed (to get back SYGIC working) and fix the messaging app crash ( 8.1.1) ??
Click to expand...
Click to collapse
Simply boot into TWRP, and mount system, then Advanced -> File Manager then do the following:
Go into /system/bin/ and delete app_process32 and app_process32_xposed
Rename app_process32_original to app_process32
Delete dex2oat and rename dex2oat.orig to dex2oat
Repeat the above step for oatdump and patchoat
Go up a directory and then into the lib directory
Delete libart.so and rename libart.so.orig to libart.so
Repeat the above step for libart-compiler.so, libart-disassembler.so and libsigchain.so
Delete libxposed_art.so
Go up a directory and delete xposed.prop
Go into framework directory and delete XposedBridge.jar
Reboot your device.
Yeah, Sygic is completely broken with Android 5.0 and Xposed.
Any fix to sygic 15.x.x on android 5 + xposed?
Thanks all!!!
AFAIK, Sygic is working on this problem, but it is a low priority issue for them, so they didn't wrote any ETA.
Well. That's a big problem. I've been waiting patiently for xposed and now that it works I cannot use Sygic (btw it costed me 15€ Eur+Russia). How can I get back to the version that works with xposed? Legally, I mean. Or can anybody try that module which hides root for a specific app? I don't remember its name. Please.
ciccio83q said:
Well. That's a big problem. I've been waiting patiently for xposed and now that it works I cannot use Sygic (btw it costed me 15€ Eur+Russia). How can I get back to the version that works with xposed? Legally, I mean. Or can anybody try that module which hides root for a specific app? I don't remember its name. Please.
Click to expand...
Click to collapse
Legally, you should try to search and download an official apk of version 15.0.4, install it and disable auto update in Play Store.
The app you search for is called RootCloak but it does not make any difference.
Sent from my NotePRO 12.2 LTE using Tapatalk.
Well. To be onest with you I found only modded apk. And it bothers me because I don't wanna use a cracked app when I paid for it. Thanks anyway. No xposed for now.
Can someone give the 15.0.4 package. The support gives me only the 15.0.9 package which is crashing at start too..
Thanks
I'm running Sygic 14.7.4 on my device with Xposed and it's fine with 2014.09 TA maps. 15.x.x does not work-crashes.
Same issue here, tried to find 15.0.4 as well, but only cracked versions laying around which I don't want. There are basically two options:
- disable xposed, reboot, use Sygic, then enable xposed, reboot (time consuming)
- use another navigation (Copilot, Tomtom,..)
_mysiak_ said:
Same issue here, tried to find 15.0.4 as well, but only cracked versions laying around which I don't want. There are basically two options:
- disable xposed, reboot, use Sygic, then enable xposed, reboot (time consuming)
- use another navigation (Copilot, Tomtom,..)
Click to expand...
Click to collapse
Disable xposed? How? Did you try disabling all the modules? The problem is that if you want to disable xposed completely it is a long process. I mean I cannot wait 20 minutes every time. And I don't wanna use a very old version of the app. There should be a workaround.
Surely, this is Sygic 15.0.4 original (official) version:
Link for download
ciccio83q said:
Disable xposed? How? Did you try disabling all the modules? The problem is that if you want to disable xposed completely it is a long process. I mean I cannot wait 20 minutes every time. And I don't wanna use a very old version of the app. There should be a workaround.
Click to expand...
Click to collapse
Create an empty file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed:
For example from TWRP or terminal type this command and reboot:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
You can create flashable file, or terminal shortcut to speed up the process. To enable Xposed again, just delete the "disabled" file (through file manager or from terminal again).
Source
I've tried 15.0.4 it's working but crashing during navigation, the moment you start navigation it'll crash. Checked with Nexus 7 DU 5.1.1 and Xiaomi Mi3 Mokee 5.1.1.
Hi,
Sometimes in Lollipop some module don't work. Then, in my case I reboot to recovery and I touch the file "conf/disabled" for starting without Xposed. After that, I like to disable the module in the UI of the Xposed Installer App... but when the framework is disabled, this option is disabled.
Please, can you change this?
Thank you!
Note: Yes, is posible to manually change the "/conf/modules.list" file from the recovery, but this is more complicated.
manos78 said:
Hi,
Sometimes in Lollipop some module don't work. Then, in my case I reboot to recovery and I touch the file "conf/disabled" for starting without Xposed. After that, I like to disable the module in the UI of the Xposed Installer App... but when the framework is disabled, this option is disabled.
Please, can you change this?
Thank you!
Note: Yes, is posible to manually change the "/conf/modules.list" file from the recovery, but this is more complicated.
Click to expand...
Click to collapse
Why don't you just disable the module, reboot, enable the module again and reboot again? No need to place any files through recovery?
By the way: could you give us more information about your device, the Android version and the Xposed files you use? Those are important information, without them nobody might help you.
orville87 said:
Why don't you just disable the module, reboot, enable the module again and reboot again? No need to place any files through recovery?
Click to expand...
Click to collapse
Because the device don't boot (bootloop on the boot animation)!!!
So, in this case the ONLY solution is: boot to recovery, touch the "disable" file, reboot with Xposed disabled... and then: How to DISABLE the module? The UI is blocking the option of enable/disable modules when the framework is disabled!
Please, remove this arbitrious limitation in the UI.
Thank you!
Why don't you just delete the modules.list inside the
data/data/de.robv.android.xposed.installer/conf/
folder?
corncobman said:
Why don't you just delete the modules.list inside the
data/data/de.robv.android.xposed.installer/conf/
folder?
Click to expand...
Click to collapse
Good alternative, but this disables all modules and you lost the info related to enabled/disabled modules... or not?
manos78 said:
Good alternative, but this disables all modules and you lost the info related to enabled/disabled modules... or not?
Click to expand...
Click to collapse
Yes, this method disables all modules. But what info related to enabled/disabled modules are you talking about? Which modules have been enabled and which not?
... you lost the info related to enabled/disabled modules... or not?
Click to expand...
Click to collapse
Not. The list of which modules are selected and which are not selected are still shown. Just disable the offending module and reboot.
corncobman said:
Not. The list of which modules are selected and which are not selected are still shown. Just disable the offending module and reboot.
Click to expand...
Click to collapse
Then you recommend "delete this file" instead of "touch the disable file" for disable only the loading of the modules but enable the framework? Then, when rebooting the phone the module list will be re-created?
The module list will be created when you change the list, i.e. toggle one module on or off. The changes only apply when you reboot.
manos78 said:
Then you recommend "delete this file" instead of "touch the disable file" for disable only the loading of the modules but enable the framework? Then, when rebooting the phone the module list will be re-created?
Click to expand...
Click to collapse
Do you want to permanently disable the module that causes the issue or do you want to use the module again after reboot?
In the first case, you can delete the corresponding module by using the in-build file manager of your recovery. Just navigate to /data/app and delete the module's folder. Done.
Otherwise, you only have the limited options presented to you (but I don't know why someone would continue using a module that is causing issues again and again).
orville87 said:
Do you want to permanently disable the module that causes the issue or do you want to use the module again after reboot?
In the first case, you can delete the corresponding module by using the in-build file manager of your recovery. Just navigate to /data/app and delete the module's folder. Done.
Otherwise, you only have the limited options presented to you (but I don't know why someone would continue using a module that is causing issues again and again).
Click to expand...
Click to collapse
Hi, I agree!
However, when a module "fails" I don't like to uninstall it... I like only to disable it. Why? Because I like to contact with the author and try fix the bug. Sometimes the problem is an update, o some other times the module is part of an App that has another functionalities. Then the best option is disable the module and not uninstall/remove it.
So, my concern is related to the best option to fix a bootloop when a module is creating some interference. Until now my best option is disable the Xposed framework, but here the recomendation is disable the load of modules. In this last case, I need to know if this file is re-created by the Xposed framework. And however, I feel is a good recomendation to enable the UI of the modules when the framework is disabled... the current behaviour is annoying.
Regards!
manos78 said:
Hi, I agree!
However, when a module "fails" I don't like to uninstall it... I like only to disable it. Why? Because I like to contact with the author and try fix the bug. Sometimes the problem is an update, o some other times the module is part of an App that has another functionalities. Then the best option is disable the module and not uninstall/remove it.
So, my concern is related to the best option to fix a bootloop when a module is creating some interference. Until now my best option is disable the Xposed framework, but here the recomendation is disable the load of modules. In this last case, I need to know if this file is re-created by the Xposed framework. And however, I feel is a good recomendation to enable the UI of the modules when the framework is disabled... the current behaviour is annoying.
Regards!
Click to expand...
Click to collapse
Ah, I see your point there. Well, I have some thoughts about another possibility. I haven't tried it yet, so no guarantee can be given if this will work. But before updating a module, you could backup the folder of the module from /data/app and place it's backup folder somewhere else. Then update the module and reboot. When facing a bootloop, just use the recovery file manager to replace the new files of the module with the old ones and reboot. This way one does not have to disable all modules or even disable/uninstall the entire framework.
orville87 said:
This way one does not have to disable all modules or even disable/uninstall the entire framework.
Click to expand...
Click to collapse
Yes, but I like the most simple option: At time, I do this when bootloop:
a) Reboot to recovery.
b) Open Aroma File Manager.
c) Rename "_disabled" to "disabled" in the xposed/config directory
d) Reboot
And when the device boots, I like to "disable" in the Xposed App... the problem is the UI... it disables interaction when the framework ins't loaded. From my point of view is a mistake! Why force this? Any reason that I don't view?
Another option is remove the file with the list of modules, but I don't know if the Xposed App recreates this file after boot, and if it's maintains the selected/unselected list of modules (normally I have some modules installed but disabled... think on Apps with Xposed add-ons that I don't like to use!).
Any comment?
manos78 said:
Yes, but I like the most simple option: At time, I do this when bootloop:
a) Reboot to recovery.
b) Open Aroma File Manager.
c) Rename "_disabled" to "disabled" in the xposed/config directory
d) Reboot
And when the device boots, I like to "disable" in the Xposed App... the problem is the UI... it disables interaction when the framework ins't loaded. From my point of view is a mistake! Why force this? Any reason that I don't view?
Another option is remove the file with the list of modules, but I don't know if the Xposed App recreates this file after boot, and if it's maintains the selected/unselected list of modules (normally I have some modules installed but disabled... think on Apps with Xposed add-ons that I don't like to use!).
Any comment?
Click to expand...
Click to collapse
When you have deleted the module list from recovery, Xposed will not create a new list after the following boot process. You have to open Xposed Installer and disable/enable a module, then reboot. This time, Xposed will create a new module list (with exactly the modules states they had before deleting the module list file apart from the last modification you have done to trigger this recreation) and you are free to go. Nevertheless, a cumbersome solution.
I have no idea why one isn't able to interact with the checkboxes, but my best bet would be to prevent the user from thinking that Xposed is indeed active and modules are not working despite being enabled.
orville87 said:
I have no idea why one isn't able to interact with the checkboxes, but my best bet would be to prevent the user from thinking that Xposed is indeed active and modules are not working despite being enabled.
Click to expand...
Click to collapse
Ok. I understand this point... with this the user don't be confused.
So, why not add one option menu in the screen of modules for "enable changes" when the framework is disabled? This option implies "the framework is disabled, but you can change the options". This be user friendly and powerful at time.
What you think?
manos78 said:
Ok. I understand this point... with this the user don't be confused.
So, why not add one option menu in the screen of modules for "enable changes" when the framework is disabled? This option implies "the framework is disabled, but you can change the options". This be user friendly and powerful at time.
What you think?
Click to expand...
Click to collapse
Might be a good point, but you have to ask rovo89 for feature requests. But I highly doubt that he will implement such thing.
orville87 said:
Might be a good point, but you have to ask rovo89 for feature requests. But I highly doubt that he will implement such thing.
Click to expand...
Click to collapse
Well, I hope Rovo89 will read this and agree to implement... it's a very simple change in the UI. :fingers-crossed:
manos78 said:
Hi,
Note: Yes, is posible to manually change the "/conf/modules.list" file from the recovery, but this is more complicated.
Click to expand...
Click to collapse
Not really complicated. If you've access to ADB simply do
Code:
adb shell sed -i '/.*PACKAGE.*/d' /data/data/de.robv.android.xposed.installer/conf/modules.list
adb shell sed -i '/.*PACKAGE.*/d' /data/data/de.robv.android.xposed.installer/shared_prefs/enabled_modules.xml
Change PACKAGE with the package name of the app.
The first command would disable only the module, not the framework, not the rest of the modules. The second command would make sure that when you open the Xposed app -> Modules, your module shows up as unchecked. The second command is not important but it is good to keep confusion at a distance.
If you don't have access to PC always, you can keep a script inside your sdcard or `/data` as
Code:
#!/bin/sh
sed -i '/.*PACKAGE.*/d' /data/data/de.robv.android.xposed.installer/conf/modules.list
sed -i '/.*PACKAGE.*/d' /data/data/de.robv.android.xposed.installer/shared_prefs/enabled_modules.xml
If you've TWRP, you can edit the file to change the package name and run the script without the need of a PC.
nomap_here said:
If you've TWRP, you can edit the file to change the package name and run the script without the need of a PC.
Click to expand...
Click to collapse
Thank you!
But quite complex! I prefer to "touch disable" for disable Xposed (fail safe boot mode) and in the UI of the App (when the Xposed is disabled) then enable/disable the ofending module. I feel is MORE SIMPLE and INTUITIVE!
I hope Tovo read this and change the UI. :fingers-crossed:
This is in place until TWRP is ready. You need root and of course you need to be attached to your PC. On first installation of systemui base, a pop-up asking to give ADB shell root permission will show. Please do so.
The purpose of this installer is to generate for you a custom module that you can flash in Magisk Manager. It will have all the mods that you have selected from the installer menu.
Custom clocks (date, etc) and internet speed indicators do not change colors due to light-dark background colors like the statusbar icons do.
The developer of Active edge gave me permission to use his base so that people would not have to make a choice between his and my mods. All credit for this goes to him. You must delete the active edge sense module and use one of my active edge modules. If it doesn't say active edge then it isn't active edge sense compatible. If there is an issue with edge sense after flashing, do not contact edge sense op with issues. He does not troubleshoot modified versions of his mod (and neither do I).
I'm also including my Pixel Launcher mod. Also a ADB Installer. You can change app drawer background-text color (separately for light mode and dark mode), remove weather from Launcher. Change the number of hot seat icons on home page (and size) as well as change the number of columns in the app drawer.
ADB Installer Instructions-Root is required
1. Flash one of the SystemUI Bases First. They provide the necessary smali files and public ID's for everything to work.
2. FLASH ALL THE MODS YOU WANT. ONCE YOU DONE WITH EVERYTHING, FLASH THE "COMPLETE INSTALLATION" Option. This will create a Magisk Manager flashable zip in a folder on your sdcard called ozop. Flash that to install your selection of mods.
Root required
Instructions.
1. Unzip ADB Mods Installer Files.zip on your PC
2. Run TulsadiverModsInstaller.bat (Give ADB Root Permissions)
3. ADB debugging Enabled
4. Flash one of the SystemUI Bases First. They provide the necessary smali files and public ID's for everything to work
5. Go through the other options selecting what all mods you want. It is generally best to start at the top and work your way down.
6. Once finished with selections, run "Complete Installation" at the bottom. This will generate your mymagisk.zip module in a folder called "ozop" on your sdcard.
List of MODS Available
Clock Format and Position Mods
Internet Traffic Speed Single Indicator (changes from upload-download) otherwise signals are over/under
Choose Traffic Speed Indicator Up-Down Icon Colors (default is white)
Navbar Height Options
Navbar Swap
Remove NavBar
3 Minit Battery
One percent custom battery Mods-Several to choose from
One percent custom battery Text-only-Several to choose from
Colored Statusbar-Navbar Icons
Choose number of QS columns 3-7
Colored Statusbar Icons
Remove Carrier Text Options
Smaller LTE Icon
Custom Battery Sizes in case custom batteries are too large or too small
ADB Module maker uploaded 6-30-21
File on MEGA
mega.nz
-------------------------------------------------
If I helped, hit the Thanks Button!
Feeling generous, send me a beer!
--------------------------------------------------
--------------------------------------------------------------------------------------
Pixel Launcher Mod
Start by picking a base. Bases come with, or without, a search bar and Hotseat heights The larger number of rows you pick, the lower your hotseat drops on your home screen. If your hotseat comes out too low, try again with a higher base.
Remove Search Bar
App Drawer background color (Light and Dark Mode)
App Drawer Text Color or remove (Light and Dark Mode)
Home screen App Text Color
Smart-screen Text color
App Icon Sizes 45-50-56 dip (56 is stock)
Columns (5-6-7)
Rows (5 through 11)
Android 11
ADB Pixel Launcher Installer uploaded 3-10-21
NexusLauncherReleaseADBPixelMar.zip | by Tulsadiver for Pixel
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
-------------------------------
Android 10
ADB Pixel Launcher Installer uploaded 6-18-20
https://www.androidfilehost.com/?fid=8889791610682873110
Zip Installer
Unzip zip into a folder on your internal sdcard. The folder name cannot have spaces in it.
Boot TWRP, find your folder. Install base first. Install the mods you want, then flash complete installation zip. Reboot.
TWRP zip Installer
https://www.androidfilehost.com/?fid=8889791610682873111
Uploaded a new installer. Fixed QS column mod. This has been verfied to work on the Pixel 3a XL and compatible with swift installer themes. Undo theme, apply my mods, then reapply theme.
LOL
Great work!
But it took me 3 hours to unzip and download it... Maybe zip it a little more? Ultra ZIP?
---------------------------------------------------------------------------------------------------------------------
it didnt work, i ran a complete installation, now boots, and instantly powers off to a page with
Code:
Can't load android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
This is the error in ADB:
Code:
Installing TulsadiverMods
cp: bad '/sdcard/vrthemeADBversion/busybox': No such file or directory
cp: bad '/sdcard/vrthemeADBversion/installtheme.sh': No such file or directory
sh: /data/local/installtheme.sh: No such file or directory
UPDATE: I didn't install base. Now I have another problem... It tries to boot and doesn't, it takes forever, then reboots and gets the first error again...
To uninstall mods do we just flash stock?
Has anyone tried this on the Q beta?
SCrid2000 said:
Has anyone tried this on the Q beta?
Click to expand...
Click to collapse
Here is one for Q5
https://www.androidfilehost.com/?fid=6006931924117921001
Posted an ADB installer for December update.
I guess I am a little confused on how this mod works and I have a hard time risking not having a nonbootable phone. I read through some of the 3 xl thread and it seems like we need our phone connected for it to make a magisk module to which we then flash via magisk? This doesn't actually flash anything, correct?
Mainly, all I need is the back/home buttons swapped, which I have now but it seems the December update breaks that according to another thread.
AutomaticFailure27 said:
I guess I am a little confused on how this mod works and I have a hard time risking not having a nonbootable phone. I read through some of the 3 xl thread and it seems like we need our phone connected for it to make a magisk module to which we then flash via magisk? This doesn't actually flash anything, correct?
Mainly, all I need is the back/home buttons swapped, which I have now but it seems the December update breaks that according to another thread.
Click to expand...
Click to collapse
For just three button mode? You can try flashing this if you like. Do you have active edge installed?
Swapping the two is easy though you need a way to get it on your phone which this should do.
Tulsadiver said:
For just three button mode? You can try flashing this if you like. Do you have active edge installed?
Swapping the two is easy though you need a way to get it on your phone which this should do.
Click to expand...
Click to collapse
Alright, I'll give that a shot when I get time to do the December update. I do not have active edge installed.
January update uploaded.
Is this going to have to be updated during every monthly update? Wish Google would just make it so we could change the positions of the 3 button navigation.
AutomaticFailure27 said:
Is this going to have to be updated during every monthly update? Wish Google would just make it so we could change the positions of the 3 button navigation.
Click to expand...
Click to collapse
Depends on the update. If that is all you want, go to this thread:
https://forum.xda-developers.com/pixel-3a/themes/clock-mods-t4024447
Tulsadiver said:
Depends on the update. If that is all you want, go to this thread:
https://forum.xda-developers.com/pixel-3a/themes/clock-mods-t4024447
Click to expand...
Click to collapse
I'm a little confused on this. These just magisk modules? How do I know what's being swapped?
AutomaticFailure27 said:
I'm a little confused on this. These just magisk modules? How do I know what's being swapped?
Click to expand...
Click to collapse
Back and récents.....yes, they are modules.
Tulsadiver said:
Back and récents.....yes, they are modules.
Click to expand...
Click to collapse
Ohhh, alright. I only want back and home to be swapped.
AutomaticFailure27 said:
Ohhh, alright. I only want back and home to be swapped.
Click to expand...
Click to collapse
You can try these if you are stock.
Stock
https://www.androidfilehost.com/?fid=4349826312261700583
Edge sense stock base
https://www.androidfilehost.com/?fid=4349826312261700584
Tulsadiver said:
You can try these if you are stock.
Stock
https://www.androidfilehost.com/?fid=4349826312261700583
Edge sense stock base
https://www.androidfilehost.com/?fid=4349826312261700584
Click to expand...
Click to collapse
Thanks. I assume I can do this myself with your adb mod installer, correct? I tried messing with it before but now I am two months behind on updates.
AutomaticFailure27 said:
Thanks. I assume I can do this myself with your adb mod installer, correct? I tried messing with it before but now I am two months behind on updates.
Click to expand...
Click to collapse
No, these are stand-alone modules and cannot be mixed with any other SystemUIGoogle.apk module (modification) and is built for January update.
Tulsadiver said:
No, these are stand-alone modules and cannot be mixed with any other SystemUIGoogle.apk module (modification) and is built for January update.
Click to expand...
Click to collapse
Oh yeah, ok, makes sense. I was more saying that if I wanted to do this myself and not have you provide a magisk module each time, then I would use the mod installer and go through that way to create my own?
Hey guys i need to download the Xposed Framework for Android 6.01, but the link is not opening up.
https://dl-xda.xposed.info/framework/
can anyone help me
mat1231123123 said:
Hey guys i need to download the Xposed Framework for Android 6.01, but the link is not opening up.
https://dl-xda.xposed.info/framework/
can anyone help me
Click to expand...
Click to collapse
[OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo [v90-beta3, 2018/01/29]
Note: This thread is here mostly for historical purposes. While Xposed is supported in various forms [EdXposed and LSPosed], developent on the Xposed primary app has completed. Xposed framework compatible modules are still in active development...
forum.xda-developers.com
I do confirm that the domain https://dl-xda.xposed.info/framework/ is not working.
Even for already installed Xposed on android devices, when you open it, the application tries to download and fetch an XML file in dl-xda.xposed.info.
There is also another error due to the same source : Could not load available ZIP files. Pull down to try again
I've updated Magisk on my Nougat and now I'm facing the same issue.
Theres a "backup" here, but I don't know how to tell Xposed to used the URL:
Index of /framework/
...or where should I put the framework files.
Edit: the URL that I posted doesn't have the actual files, I've just realized.
Hey all! I had the same problem and I'm happy to report I've fixed it. Daniel_Laixer was on the right track. Take his link, Index of /framework/ and go to whatever sdk version you need (mine was 26). Keep going and pick the .zip when you get there, then pick 1 capture in the upper left area. Click on whatever date is highlighted, and this should give you the .zip file. (it took me a few refreshes before it would give it to me for some reason). Then drop into recovery mode on your phone and install the zip. Done!
maikoherajin said:
Hey all! I had the same problem and I'm happy to report I've fixed [email protected] Daniel_Laixer was on the right track. Take his link, Index of /framework/ and go to whatever sdk version you need (mine was 26). Keep going and pick the .zip when you get there, then pick 1 capture in the upper left area. Click on whatever date is highlighted, and this should give you the .zip file. (it took me a few refreshes before it would give it to me for some reason). Then drop into recovery mode on your phone and install the zip. Done!
Click to expand...
Click to collapse
不能下载了
Mod translation: can't download
link dead again
Daniel_Laixer said:
I've updated Magisk on my Nougat and now I'm facing the same issue.
Theres a "backup" here, but I don't know how to tell Xposed to used the URL:
Index of /framework/
...or where should I put the framework files.
Edit: the URL that I posted doesn't have the actual files, I've just realized.
Click to expand...
Click to collapse
Huh why there a file in there i actually downloaded the xposed sdk 25?
Anonymous V said:
Huh why there a file in there i actually downloaded the xposed sdk 25?
Click to expand...
Click to collapse
It turns out some links work, but others are dead. For instance, this file is not backed up:
https://web.archive.org/web/20190725022140/https://dl-xda.xposed.info/framework/sdk25/arm64/xposed-v89-sdk25-arm64.zip
Yeah your right i redownload the xposed v89 not v88 after i access tge kink i cant download anymore because its down again
https://androidfilehost.com/?w=files&flid=227007 Here i found something, take a look
alfanveykov said:
https://androidfilehost.com/?w=files&flid=227007 Here i found something, take a look
Click to expand...
Click to collapse
Yeah theres a file but it might be risky