Related
This script has only been tested with CM ROM, I cannot guarantee that it will work with other ROMs.
DESCRIPTION
I couldn't decide on one single boot animation to use on my phone, so I thought, why not start every boot with a random animation?
I threw together a simple script that will randomly choose a boot animation zip file from a directory and copy the file to /data/local. The script defaults to using /sdcard/bootanimation as the directory to store all the animations.
INSTALLING THE SCRIPT
Extract 09bootanimation from the zip file, then type the following from your command prompt:
Code:
adb remount
adb push 09bootanimation /system/etc/init.d
adb shell chmod 750 /system/etc/init.d/09bootanimation
If you are using CM 5.0.6 - 5.0.8, you will need to do an additional step. The fstab file is missing, so extract fstab from the zip file and execute the following:
Code:
adb remount
adb push fstab /system/etc
Thanks to godsfilth for figuring out the fstab problem. =)
If you are not using CM ROM, you may have the init.d directory in a different location.
Reminder: Because the script is installed in the system directory, you need to redo all the installation steps after upgrading your ROM.
INSTALLING BOOT ANIMATIONS
Create a directory called bootanimation in the SD card root directory, and put all your animation zip files in the directory. The script will only choose from zip files in the directory.
If you want to change the default directory, just change the variable in the script.
Thanks to godsfilth for getting it to work with SD cards! =)
SELECTING A SPECIFIC ANIMATION
If you want to view a new animation, instead of rebooting repeatedly and hoping that it will be selected at random, you can use the following method.
Create a file called bootanimation.use in the bootanimation directory where you have placed all the zip files. The file should contain a single line with the filename of the boot animation, without the directory path. For example:
Code:
bootanimation-prash.zip
When you want to go back to random animations, simply delete bootanimation.use from the directory.
HELP! I CAN'T GET THIS TO WORK!
If you have problems getting the script to work, grab the logcat of the startup process and post it to pastebin. You can get the logcat output by rebooting the phone and then immediately running
Code:
adb logcat > log.txt
Once the boot animation has started you can press Ctrl-C to stop the log collection. Please include in your post the ROM that you are running.
SAMPLE LIST OF BOOT ANIMATIONS
For those who are looking for some boot animations to choose from, here's a small list of animations from other XDA threads. Feel free to recommend animations, and I'll update this list.
Prash's CyanogenMod 5.0
Qteknology's Nexus animations
Nighthound's Win7 Nexus
Nighthound's BSOD
Nighthound's Qteknology's Splash Inverted
nmeofdst8's Nexus One Red Flame Edition
iDance°-->ra1n's Ubuntu Nexus and Tiesto animations
Droid Eris thread with lots of cool boot animations
FUTURE CHANGES
Eventually I might get motivated enough to write a simple program to simplify the entire process. It would be great if someone has the spare time to do so.
CHANGELOG
Version 1.3
Updated to work with CM 5.0.6 (push fstab to /system/etc) [thanks godsfilth again]
Added option to specify boot animation to use
Added logging output
Version 1.2
Changed filename to 09bootanimation to work with CM Apps2SD.
Version 1.1
Enables storage on SD card [thanks godsfilth!].
Added error checking for no animation files.
Version 1.0
Initial release.
Nighthound said:
I couldn't decide on one single boot animation to use on my phone, so I thought, why not start every boot with a random animation?
I threw together a simple script that will randomly choose a boot animation zip file from a directory and copy the file to /data/local. The script defaults to using /data/local/bootanimation as the directory to store all the animations.
Installing the script
Extract the script from the zip file, then type the following code:
Code:
adb remount
adb push 10bootanimation /system/etc/init.d
adb shell chmod 750 /system/etc/init.d/10bootanimation
Note that I'm running CM5, your ROM may have the init.d directory in a different location.
Installing boot animations
Do this once, the very first time you're using this:
Code:
adb shell mkdir /data/local/bootanimation
After that, use this to copy your animations:
Code:
adb push [i]animation-filename.zip[/i] /data/local/bootanimation
If you want to change the default directory, just change the variable in the script.
My knowledge of the Linux system is limited and I couldn't figure out how to access the sdcard during boot up, so unfortunately all the animations will have to reside in the data partition for now. Would be great if someone could help out with that.
Click to expand...
Click to collapse
Exactly what i was looking for thanks!!!!!!
Anyone else gonna touch this to get it to work off the sdcard?? That would make this so sweet!
good stuff! I altered this a bit to work from the sd card.
edit: I see godsfilth did too...nice
i got it working don't know if theres any negative side effects everything seems to work fine just delete the bootanimation.tmp file when you add new animations
installation is the same as before except I have the boot animations going to /sdcard/bootanimation so put them there
might want to nandroid before installing i did but im paranoid about things like that.
also im not responsable for anything that happens if you flash this file everything runs fine on my phone so i think its stable but all mods run some form of minor risk
also not responsible for worn out sdcards or missed calls/sms sue to the constant rebooting of your phone to show off the animation
Are we supposed to rename each bootanimation.zip with a unique name, or keep the filenames "bootanimation.zip" and make individual directories? Renaming each bootanimation.zip and placing them in /sdcard/bootanimation is not working for me.
godsfilth said:
i got it working don't know if theres any negative side effects everything seems to work fine just delete the bootanimation.tmp file when you add new animations
installation is the same as before except I have the boot animations going to /sdcard/bootanimation so put them there
might want to nandroid before installing i did but im paranoid about things like that.
also im not responsable for anything that happens if you flash this file everything runs fine on my phone so i think its stable but all mods run some form of minor risk
also not responsible for worn out sdcards or missed calls/sms sue to the constant rebooting of your phone to show off the animation
Click to expand...
Click to collapse
overground said:
Are we supposed to rename each bootanimation.zip with a unique name, or keep the filenames "bootanimation.zip" and make individual directories? Renaming each bootanimation.zip and placing them in /sdcard/bootanimation is not working for me.
Click to expand...
Click to collapse
have you tried deleting the temp file that the script generates? I have all different kinds of names for my boot animations so i dont think it matters as long as there all in the same directory
godsfilth said:
have you tried deleting the temp file that the script generates? I have all different kinds of names for my boot animations so i dont think it matters as long as there all in the same directory
Click to expand...
Click to collapse
Well, there was no .tmp file created, and I was using the /sdcard/bootanimation version, which did not work for me. Using the original version works fine. Thanks
Edit: Although, I'd rather have them on sd...I'll keep trying.
Edit2: Still no go on the /sdcard option...wonder if using Desire Rom or apps2sd messes it up? Doesn't seem like it should. The /sdcard script looks fine. Hmmm...?
overground said:
Well, there was no .tmp file created, and I was using the /sdcard/bootanimation version, which did not work for me. Using the original version works fine. Thanks
Edit: Although, I'd rather have them on sd...I'll keep trying.
Click to expand...
Click to collapse
what ROM are you using i'm running CM's latest if you are running CM then try pushing the script again following the directions in the first post just use the sdcard script instead also
i have no idea why the script Nighthound posted works and my sdcard one does not. all i did was edit his script to mount the sdcard load from /sdcard/bootanimation and then unmount the sdcard literally added for lines of text and edited the load directory
EDIT:so you're using the desire rom where does the desire ROM keep its init.d if its not /system/etc then you will need to push the file to wherever the desire rom stores it plus i think desire uses a different format for boot animation since it has sound too
godsfilth said:
what ROM are you using i'm running CM's latest if you are running CM then try pushing the script again following the directions in the first post just use the sdcard script instead also
i have no idea why the script Nighthound posted works and my sdcard one does not. all i did was edit his script to mount the sdcard load from /sdcard/bootanimation and then unmount the sdcard literally added for lines of text and edited the load directory
Click to expand...
Click to collapse
I know. It looks fine and there's no reason why it shouldn't be working. Right now I'm on Manup's NexDesire. I've been back and forth like 3x now and OP script is the only one working for me. Oh well, not a big deal. When I switch ROM's, I'll try your's again. Thanks for the ideas.
Edit for your edit: init.d in this rom is also in /system/etc
Sweet! The sdcard script worked like a champ! Thanks for modifying that. Now I can just keep adding all the coolness without getting bored!
godsfilth said:
i got it working don't know if theres any negative side effects everything seems to work fine just delete the bootanimation.tmp file when you add new animations
installation is the same as before except I have the boot animations going to /sdcard/bootanimation so put them there
might want to nandroid before installing i did but im paranoid about things like that.
also im not responsable for anything that happens if you flash this file everything runs fine on my phone so i think its stable but all mods run some form of minor risk
also not responsible for worn out sdcards or missed calls/sms sue to the constant rebooting of your phone to show off the animation
Click to expand...
Click to collapse
Thanks for the help! I've updated the OP with the new version. By the way, you don't have to delete the temp file because it is regenerated every boot.
Are we supposed to delete the one we have in /system/media? I haven't actually seen a random change. I've seen the same one everytime I reboot.
Beast84 said:
Are we supposed to delete the one we have in /system/media? I haven't actually seen a random change. I've seen the same one everytime I reboot.
Click to expand...
Click to collapse
I've only got the random changing to work using the original script with folder /data/local/bootanimation. That is working flawlessly, however.
overground said:
I've only got the random changing to work using the original script with folder /data/local/bootanimation. That is working flawlessly, however.
Click to expand...
Click to collapse
I got a different animation the first time I booted & now I only see one everytime I boot. I have the stock, cyanogen, win7nexus & both QTeknology's white & black animations but all I see is the win7nexus.
Beast84 said:
Are we supposed to delete the one we have in /system/media? I haven't actually seen a random change. I've seen the same one everytime I reboot.
Click to expand...
Click to collapse
Which version of the script are you using (v1.0, godsfilth's version or v1.1)? And where are you putting the animation files?
overground said:
I've only got the random changing to work using the original script with folder /data/local/bootanimation. That is working flawlessly, however.
Click to expand...
Click to collapse
Are you using any custom ROM?
Nighthound said:
Which version of the script are you using (v1.0, godsfilth's version or v1.1)? And where are you putting the animation files?
Click to expand...
Click to collapse
I'm using 1.1 and all my animations are in /sdcard/bootanimation. Is there a difference between godsfilth's & your 1.1?
Beast84 said:
I'm using 1.1 and all my animations are in /sdcard/bootanimation. Is there a difference between godsfilth's & your 1.1?
Click to expand...
Click to collapse
The only difference is I added an error check in 1.1. Other than that the sdcard mount procedure is the same. From your earlier description, you said that the script copied the animation to /data/local once, and then didn't work again after that? Did you chmod the script after copying it into /system/etc/init.d ?
Nighthound said:
Are you using any custom ROM?
Click to expand...
Click to collapse
Yes, as I mentioned earlier in the thread, I'm on Manup's NexDesire 1.2, which may or may not be the culprit. Was suggested earlier that because the Desire ROMs sometimes call a boot sound in addition to bootanimation, this may screw with it. I haven't really looked into it, but this ROM has no boot sound. I don't know if it is because it is
1. removed the .mp3
2. the portion of the script that calls it is commented out
3. both 1 and 2
I hope 2 or 3 is true, because that would be cleaner.
I'll check it out further when I get a chance.
In the meantime I suggest posting both versions of the script, so it can work for everyone. Thanks Nighthound
Nighthound said:
The only difference is I added an error check in 1.1. Other than that the sdcard mount procedure is the same. From your earlier description, you said that the script copied the animation to /data/local once, and then didn't work again after that? Did you chmod the script after copying it into /system/etc/init.d ?
Click to expand...
Click to collapse
I can't get adb to work properly on my laptop so I actually made an update.zip to get the file in system/etc/init.d. Shouldn't that get it working properly without having to chmod anything? If not, would be nice enough to give me the commands to chmod from terminal? I know it can't be too different from the adb commands but I just wanna make sure I do it right
AutoMod BETA 1.6 by MAD Industries
-----------------------------------------------------------------------------------------------------------------------------------
First off, this is not another APK Manager, this is also not Auto APK Tool. These two tools focus on the decompiling and recompiling of APK and jar files. AutoMod intends to bring a new paradigm to modding. That is, there are mods and there are roms. AutoMod makes them friendly with eachother. APKs are handled internally by the script.
I wrote this tool because as a developer who was using APK Manager, I ran into several obstacles along the way. One of them was that I liked to be able to take requests from users and personalize the mod to their tastes. Unless I was impeccable with my folder organization, it very quickly got out of hand with people asking for personalizations based on other personalizations. I would find myself decompiling a version I made the day before so I could remember what was in it and create yet another version on top of it. All this back and forth and I would end up with a mess of recompiled, decompiled, original, custom, extracted, etc files all over the place taking unnecessary HD space. On top of that, every step of the way required user input in the form of a yes/no prompt or selected a menu option for decompiling/recompiling/keep folders/signing/etc. And then I would manually create a flashable zip file for each version. AutoMod solves many of this issues in it's current BETA state. When it is finished, it will have solved all of them.
Features for End-Users:
Mods are dynamically applied to your ROM (this allows mods to stay up-to-date with the ROM without original developer support)
Mods often work across multiple similar ROMs (easy porting)
Mods are stored in what I call "opensource" format which means it is very easy to dig into the Mod package and change things to your personal preferences with very little knowledge modding
Only the modified files within the apk are stored in a mod package. This greatly reduces filesize
AutoMod encourages backups at every major step in the process
Backups are dynamic, meaning it will only backup the files which are modified
Backups are automatically saved as a flashable zip file so you can have it ready if a mod does not successfully integrate
AutoMod always keeps itself up-to-date with the latest features
Distribution of AutoMod requires only the script itself
AutoMod has the ability to accept a ROM Install file or an actual device as a base for creating a flashable zip file out of any mod package
Supported devices can have mods applied instantly and automatically over adb
Features for Developers
Since mod packages only contain changed files, you no longer have to hunt through hundreds of files to find a single png (such as when creating five different colored versions of a theme)
Easy packaging of mods for redistribution for this tool as well as update.zip format
AutoMod can "install" multiple ROMs into it's system so you can make a mod once, and then distrubute it for several ROMs at the same time
If you run nightly builds of your own ROM, AutoMod will soon include a scriptable feature which will allow you to release nightly themes, mods, etc with no extra effort
Much of the developer features are yet to come (such as quick prototyping of mods and parallel device/ROM support)
---------------------------------------------------------------------------------------------------------------------------------------
Tutorial written by mybook4 on post #16 (be sure to thank him)
---------------------------------------------------------------------------------------------------------------------------------------
1) Download automod.sh script and place it into an appropriate directory (I used one called AutoModTest)
2) Download the ROM Install zips you would like
3) Create your mod package (see below)
4) Run automod by typing “bash automod.sh” in a terminal
5) Select option 5 (Install a new ROM file into AutoMod), and follow the script's directions (copying your ROM zip, to the directory, not moving it or it will be overridden)
6) Select option 4 (Install a new mod package into Automod), and follow the script's directions (copying your mod zip, to the directory, not moving it or it will be overridden)
7) Select option 3 (Use a ROM Install zip + mod to create a flashable zip for another ROM/device), choosing the appropriate ROM and mod package.
8) Out came the zip! This makes things soooooooooooo much easier and more manageable!
Notes about automod mod packages:
1) A mod file is structured as a zip file with the extension .zip replaced with .mod (so as to separate it from flashable zips with the same name)
2) In the mod file is a directory with the name of the mod.
3) In the directory with the name of the mod is a directory tree leading to the files within the specific apk you would like to modify. For example, in the ICSBlueFull.mod file, the directory tree is as follows: ICSBlueFull, system, app, SystemUI (the apk being modified), res, directories with modified files (images, xml files, etc).
4) Just to be safe (and to match the ICSBlueFull mod supplied), I set permissions on all folders in my mod to 755 and all files to 644 (if these numbers don't mean much to you, open a terminal and type “man chmod”)
5) There is a command to package mods you have made into .mod files. This can be found in the developer menu. (option 11)
6) Spaces in file name are currently not handled very well. Try and name your mods accordingly.
---------------------------------------------------
How To Create A Mod
click to enlarge
---------------------------------------------------
Download the script here: http://cl.ly/code/463B1C3B123i
Note: Proper syntax is 'bash automod.sh'
Download an example mod here (for stock GS3 touchwiz based ROMs) [Fixed!]: https://github.com/downloads/MADindustries/automod/ICSBlueFull.mod
Original thread for this mod can be found here: http://forum.xda-developers.com/showthread.php?t=1775235
View the source/branch it here: https://github.com/MADindustries/automod (check this to see if using a 'forceupdate' would add features/functions)
awesome work dude!
invisiblek said:
awesome work dude!
Click to expand...
Click to collapse
Thanks. Btw you are in the credits on the script itself. (even if it was a couple binaries haha)
Wow. Great work. Can't wait to see more!
Ta very much indeed.
ALQI
Sent from my SCH-I535 using xda app-developers app
Nice job buddy..No Windows support?
This is amazing. +100000000000
Sent from my SCH-I535 using xda app-developers app
incubus26jc said:
Nice job buddy..No Windows support?
Click to expand...
Click to collapse
Not just yet. I'm on Mac personally which makes it not too difficult to see some Linux support as well. But Windows would be a completely new write from what i can tell. It will likely happen after this is out of beta unless a Windows dev feels like working with me on it. Obviously everything is open source and i would love to see a port pop up before i get around to it.
Sent from my Galaxy Nexus using Tapatalk 2
Very cool indeed.
Tried to download the example mod but appears it's down/not available.
Definitely want to give this a try.
Thanks for sharing
MAD Industries said:
Not just yet. I'm on Mac personally which makes it not too difficult to see some Linux support as well. But Windows would be a completely new write from what i can tell. It will likely happen after this is out of beta unless a Windows dev feels like working with me on it. Obviously everything is open source and i would love to see a port pop up before i get around to it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It might work on windows with the right install of cygwin. I'd have to create a windows VM to test it out and I'm not all that familiar with cygwin anymore, any windows devs out there good with cygwin?
Sent from my SCH-I535 using xda app-developers app
alquimista said:
It might work on windows with the right install of cygwin. I'd have to create a windows VM to test it out and I'm not all that familiar with cygwin anymore, any windows devs out there good with cygwin?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Oh yeah! I totally forgot about cygwin. Yeah that should do it. It has all dependencies packaged with it except java and wget/curl. And only java is really necessary if you kinda know your way around.
Nice! Another great tool for the community!
Just what ive been waiting for
---------- Post added at 08:40 PM ---------- Previous post was at 08:32 PM ----------
Looks like running with cygwin gives unknown operating system. Can't proceed after that.
clark44 said:
Just what ive been waiting for
---------- Post added at 08:40 PM ---------- Previous post was at 08:32 PM ----------
Looks like running with cygwin gives unknown operating system. Can't proceed after that.
Click to expand...
Click to collapse
Oh yeah, that will have to be changed. run the command 'echo $(uname)' in a cygwin terminal and let me know what it outputs. I'm guessing just cygwin. Then i'll update the script to support it.
Any chance anyone has the example mod posted in the first post available on another hosting provider? It's been down for 2 days
myn said:
Any chance anyone has the example mod posted in the first post available on another hosting provider? It's been down for 2 days
Click to expand...
Click to collapse
Fixed it! Sorry about that. I don't know what happened with cloud.
Automod works great! Thanks so much! Here are the steps I took to create a quick little test mod to enable a 40x38px navigation bar and have only the wifi, bluetooth, gps, rotation, sync status bar toggles for Beans R8. I'm on Beans R3.1, so I didn't get a chance to test the zip in CWM.
1) Download automod.sh script and place it into an appropriate directory (I used one called AutoModTest)
2) Download the ROM Install zips you would like
3) Create your mod package (see below)
4) Run automod by typing “bash automod.sh” in a terminal
5) Select option 5 (Install a new ROM file into AutoMod), and follow the script's directions (copying your ROM zip, to the directory, not moving it or it will be overridden)
6) Select option 4 (Install a new mod package into Automod), and follow the script's directions (copying your ROM zip, to the directory, not moving it or it will be overridden)
7) Select option 3 (Use a ROM Install zip + mod to create a flashable zip for another ROM/device), choosing the appropriate ROM and mod package.
8) Out came the zip! This makes things soooooooooooo much easier and more manageable!
Notes about automod mod packages:
1) A mod file appears to be structured as a zip file with the extension .zip replaced with .mod
2) In the mod file is a directory with the name of the mod.
3) In the directory with the name of the mod is a directory tree leading to the files within the specific apk you would like to modify. For example, in the ICSBlueFull.mod file, the directory tree is as follows: ICSBlueFull, system, app, SystemUI (the apk being modified), res, directories with modified files (images, xml files, etc).
4) Just to be safe (and to match the ICSBlueFull mod supplied), I set permissions on all folders in my mod to 755 and all files to 644 (if these numbers don't mean much to you, open a terminal and type “man chmod”)
The 5StatusBarNavBar mod package for Beans R8
The CWM zip for the above mod package
MAD Industries said:
Oh yeah, that will have to be changed. run the command 'echo $(uname)' in a cygwin terminal and let me know what it outputs. I'm guessing just cygwin. Then i'll update the script to support it.
Click to expand...
Click to collapse
CYGWIN_NT-6.1-WOW64 (edit: uname -o will just return Cygwin)
Took a quick look at your script and I don't think it will too much of effort to offer cygwin support. Package manager by default will install bash, and curl/wget is available as well. You would need to install java naively on OS (it is accessible via your bash shell). Also to note don't think it will be required for your script based on my quick look, but you could always use the built in 'cygpath' command to convert windows<->unix paths if necessary.
Unfortunately only have a Windows box at work so can't spend to much time on but if no one gets to it I will take a stab later this week time permitting.
incubus26jc said:
Nice job buddy..No Windows support?
Click to expand...
Click to collapse
Linux is free and easy to dual boot. Nothing stopping you.
Or just run Linux from a VM. You can even forward the USB ports with Vitualbox.
mybook4 said:
Automod works great! Thanks so much! Here are the steps I took to create a quick little test mod to enable a 40x38px navigation bar and have only the wifi, bluetooth, gps, rotation, sync status bar toggles for Beans R8. I'm on Beans R3.1, so I didn't get a chance to test the zip in CWM.
1) Download automod.sh script and place it into an appropriate directory (I used one called AutoModTest)
2) Download the ROM Install zips you would like
3) Create your mod package (see below)
4) Run automod by typing “bash automod.sh” in a terminal
5) Select option 5 (Install a new ROM file into AutoMod), and follow the script's directions (copying your ROM zip, to the directory, not moving it or it will be overridden)
6) Select option 4 (Install a new mod package into Automod), and follow the script's directions (copying your ROM zip, to the directory, not moving it or it will be overridden)
7) Select option 3 (Use a ROM Install zip + mod to create a flashable zip for another ROM/device), choosing the appropriate ROM and mod package.
8) Out came the zip! This makes things soooooooooooo much easier and more manageable!
Notes about automod mod packages:
1) A mod file appears to be structured as a zip file with the extension .zip replaced with .mod
2) In the mod file is a directory with the name of the mod.
3) In the directory with the name of the mod is a directory tree leading to the files within the specific apk you would like to modify. For example, in the ICSBlueFull.mod file, the directory tree is as follows: ICSBlueFull, system, app, SystemUI (the apk being modified), res, directories with modified files (images, xml files, etc).
4) Just to be safe (and to match the ICSBlueFull mod supplied), I set permissions on all folders in my mod to 755 and all files to 644 (if these numbers don't mean much to you, open a terminal and type “man chmod”)
The 5StatusBarNavBar mod package for Beans R8
The CWM zip for the above mod package
Click to expand...
Click to collapse
Thank you so much for writing this! I am adding it to the OP. (let me know if you want me to take it down for some reason though)
Quick note, I think step 6 was supposed to be copy mod file to install directory? Also, a .mod file is exactly that; a zip file renamed to .mod. I did this to differentiate it from flashable zip files because the two would likely have the same name and it would cause confusion yet I still wanted to keep the .mod format easily modifiable/not proprietary. And one last thing, there is a hidden command called "packagemod" which can be used after you create your own mod to zip it up properly for distribution. It is entered at the main menu in place of choosing an option. Syntax: 'packagemod ICSBlueFull'.
lowg said:
CYGWIN_NT-6.1-WOW64 (edit: uname -o will just return Cygwin)
Took a quick look at your script and I don't think it will too much of effort to offer cygwin support. Package manager by default will install bash, and curl/wget is available as well. You would need to install java naively on OS (it is accessible via your bash shell). Also to note don't think it will be required for your script based on my quick look, but you could always use the built in 'cygpath' command to convert windows<->unix paths if necessary.
Unfortunately only have a Windows box at work so can't spend to much time on but if no one gets to it I will take a stab later this week time permitting.
Click to expand...
Click to collapse
Thanks for the tips. I have next to no experience with cygwin so this information is very helpful. I'll look into adding support to the next release.
So here I have noticed issue with using vrtheme on new 4.3 MJ2 and seeking some Linux expert help to solve it.
work around
Simply using vrtheme causing FCs, SO i have changes the destination to see outcome file structure.
-All changes we have applied through vrtheme applied to output file. but icons get changed to android icon.
-Now if you move that output file to other destination using root explorer then also it regenerates original icons and we can use as final apk ready to push to System/app
-Again if we giving same command through recovery, it doesn't works
-Also copying with terminal emulator with cat command, it regenerates original structure. again same command using recovery fails to do it.
May be recovery issue??
here is log cat along with used vrtheme script.
dr.ketan said:
So here I have noticed issue with using vrtheme on new 4.3 MJ2 and seeking some Linux expert help to solve it.
work around
Simply using vrtheme causing FCs, SO i have changes the destination to see outcome file structure.
-All changes we have applied through vrtheme applied to output file. but icons get changed to android icon.
-Now if you move that output file to other destination using root explorer then also it regenerates original icons and we can use as final apk ready to push to System/app
-Again if we giving same command through recovery, it doesn't works
-Also copying with terminal emulator with cat command, it regenerates original structure. again same command using recovery fails to do it.
May be recovery issue??
Click to expand...
Click to collapse
doc, am not a linux expert, but i tried to inject your black aosp vrtheme files into the apk and flash them from cwm, it kills the wifi and have to wipe and reflash the whole rom. so, perhaps you want to put more attention to it.
waiting for your aosp theme and thanks a lot.
Wifi issue will be solved by reflashing recovery
I can show you temporary solution.
Just change path of pushing files to other from System/app then 1. you want get FCc bcoz it is not in system/app
2. Now from where you have defined destination from there move to some pther place with root explorer, now you will be able to see icons, once icons are correct you can pust to system/app.
dr.ketan said:
Wifi issue will be solved by reflashing recovery
I can show you temporary solution.
Just change path of pushing files to other from System/app then 1. you want get FCc bcoz it is not in system/app
2. Now from where you have defined destination from there move to some pther place with root explorer, now you will be able to see icons, once icons are correct you can pust to system/app.
Click to expand...
Click to collapse
sorry doc, but i cannot understand what you mean.
do you mean i should change the flashing path (in the script)? or do you mean i should copy the apks manually into the system/app by root explorer? if you mean the later, i can do, but the first one i don't.
i can see all the icons, just the wifi would not start after i flashed the modified apks through cwm flash. what do you mean by reflashing recovery?
Ok making clear again who want to use vrtheme
1.Change path in vrtheme installertheme.sh from system/app to other (e.g. just system)
2.Now when you flash vrtheme, you won't see any changes in system bcoz all apps will be in system and not in System/app.
3. Manually cut all app with root explorer from system to SDcard
4. Now you can see correct icons of all appl after moving to sdcard.
5.Now move those apk to system/app OR System/framework, where it should be.
6.Enjoy all the changes now in system
7.By this process you will lose wifi and you have to reflash recovery to get it back.
PS : For AOSP for MJ2 I have made it with same method above and uploading, Once uploaded will post to MJ2 thread, you have to simply flash that file. without doing anything above.
dr.ketan said:
Ok making clear again who want to use vrtheme
1.Change path in vrtheme installertheme.sh from system/app to other (e.g. just system)
2.Now when you flash vrtheme, you won't see any changes in system bcoz all apps will be in system and not in System/app.
3. Manually cut all app with root explorer from system to SDcard
4. Now you can see correct icons of all appl after moving to sdcard.
5.Now move those apk to system/app OR System/framework, where it should be.
6.Enjoy all the changes now in system
7.By this process you will lose wifi and you have to reflash recovery to get it back.
PS : For AOSP for MJ2 I have made it with same method above and uploading, Once uploaded will post to MJ2 thread, you have to simply flash that file. without doing anything above.
Click to expand...
Click to collapse
will just wait for your file then. dont want to mess my setup again. spent too much time experimenting with it today. lucky it's saturday in my country...
ok then wait 10 min.
EDIT : AOSP theme for MJ2 ROM Posted to MJ2 thread post#2
Doc.
I just came across thia issue thread discussion.
Surprised to see vrtheme issues.
I think it is worth trying morphing instead of vrtheme.
If it fails, then it is not a recovery issue..m
It might be android 4.3 security files that I noticed in /system...
I will dig in further and check...
Thx for sharing this discussion thread. :thumbup:
wesamothman said:
Doc.
I just came across thia issue thread discussion.
Surprised to see vrtheme issues.
I think it is worth trying morphing instead of vrtheme.
If it fails, then it is not a recovery issue..m
It might be android 4.3 security files that I noticed in /system...
I will dig in further and check...
Thx for sharing this discussion thread. :thumbup:
Click to expand...
Click to collapse
Already fixed that (at least in my MJ2 rom)
vrtheme works perfect on framework-res.apk and secsettings.apk
I have been on XDA for 2 and a half years or so. I have gained a vast amount of knowledge and skills and its all in part due to XDA and the individuals who spend their time helping others who have made this all possible. The list of those to thank is too long. So before you see what I have to offer below, I want to thank everyone around the forums here for your help, or criticism . Without you guys, I never would've learned what I know today.
Most of my hacks for the HD 10 are spread out around several threads. That makes it hard to keep everyone updated when I find or create new goodies. It also makes it hard for users to find these goodies. This thread aims to solve that problem. From now on, I will include, if possible, my tricks and hacks in this thread. This aims to make searching for and installing these modifications quick and simple.
I have created a flash zip that installs all my goodies and hacks I have come up with so far. I just need so others to test it and make sure the installation process works and everything that is installed works. So please report back your findings so I can remove test from the thread.
***IIf this zip doesn't work or if it fails the worst that can happen is you will have to flash back to fresh stock and start all over and re-root. So make note of your Fire OS version before installing this zip. I am not responsible for anything that doesn't work. If you install this zip, you are doing so at your own risk.***
This zip does NOT contain the Google Play Store. By installing this zip, I assume you already have it installed. ViPER4Android requires an extra step or two and SELinux switch. See below.
Requirements:
- HD 10 with Fire OS 5.6.1.0 or 5.6.2.0
- Rooted with Xposed installed and Flash Fire functioning properly. See here to get it up and running.
What this zip includes:
- *ALL* of my framework-res mods including WiFi and location service optimizations.
- My rewritten Settings.apk which also includes all of my mods.
- Stock Basic Dreams and Photo Table screensaver. This was one of my goals when I first signed up on XDA. I knew what needed to be done to get this to work, I just didn't know how. Finally after nearly 4 to 6 months of reading and testing, I was finally able to edit the framework-res.apk to bring you this and other features. I also had to track down a working Basic Dreams and Photo Table APK. That was half the battle. Go to settings -> display settings -> Daydream. You can choose colors, clock or set some custom photos in Photo Table. Tap three dots in upper right to decide when Daydream turns on. (Note: Photo table requires your images be placed in internal storage in the 'Pictures' folder).
- Google Calendar (assuming you have deleted Amazon's calendar).
- DeskClock latest update and APK for Google Clock (assuming you deleted Amazon's clock).
- Google Contacts Sync Adapter (Once installed, you can delete Amazon's contact sync adapter as seen here. Also for non-root users). This allows for a small amount of visual customization when you pull down the notification bar. When you customize your profile in Google Contacts (also included in this zip) with a photo, the icon in the notification panel will change to whatever you upload as your contacts photo.
- Google Contacts (requires sync adapter listed above).
- Google TTS. You can delete PicoTTS in /system/app once Google TTS is installed. It's very outdated. You can also delete both of the Ivona folders in /system/priv-app. Best to delete app data for all three before deleting.
- Latin IME (AOSP replacement for stock keyboard. Will only work when you delete Amazon's keyboard (com.amazon.redstone), any other keyboard you have installed, then perform a factory reset without installing a new one.
- Stock Android Marshmallow boot animation. The zip replaces the bootanimation binary file in /system/bin/bootanimation with one from from @ggow custom ROM for the Fire 7. Amazon had modified the stock bootanimation binary to force the gold 'fire' boot animation. Doing this made it impossible to customize the boot animation. So I replaced it under the assumption the Fire 7 ROM binary is from an AOSP build and is pretty much universal among most custom ROMs. And it worked!
- Gallery3d. Replaces Amazon Photos (You have to delete Amazon Photos on your own) with library injection so it is fully featured. You can edit all images with a full stock of editing options. (does not set lock screen wallpaper. To change lock screen wallpaper, see here. Requires root). I was able to find the APK and libraries in this thread. The flash zip there doesn't work for our devices so I modified the APK to be more tablet friendly, allowing for scrolling and viewing in landscape mode then added the relevant files to this zip. In the APK, I removed the options for a settings menu, because it doesn't function, but the library does a great job at making up for the loss of it.
- CM Browser. I was able to port over this APK along with CM File Manager, CM Wallpapers, Lock Clock and Trebuchet from an official CM Lollipop ROM for the Amazon HD 8.9.
- CM File Manager (Can replace your favorite root explorer).
- CM Wallpapers. Cyanogenmod actually had a few good wallpapers. I wish they had made their own live ones though.
- CM Lock Clock with weather. (Yahoo weather doesn't function. Use Open Weather and set update interval to 30mins).
- Trebuchet Launcher with basic launcher settings. (You have to delete fire launcher on your own for this to take effect. /system/priv-app/com.amazon.firelauncher)
- Google Calculator (assuming you deleted Amazon's)
- Stock Android Live Wallpapers and Live Wallpaper Picker (doesn't include Androids add on wallpapers. For all of Android's stock live wallpaper add ons and stock wallpaper images, see this thread.
What this zip DOES NOT include or do:
- Google Play store is NOT installed. It is best advised to do this manually. Even flashing Gapps doesn't stop you from needing to tweak Secure Settings a little bit.
- Does not delete or remove any files or folders. It does however overwrite some. The framework-res, FireTabletSettings and bootanimation files will all be overwritten.
- Not yet a custom ROM, but it's close.
-Build.prop edits are not included. My WiFi optimizations and ViPER4Android need a few tweaks. Please see the 'build.prop' section below for details.
Installation:
NOTE: If you only wish to install certain packages or tweaks such as ViPER4Android, see instructions below installation guide.
1. Simply place the DragonMods.zip into internal storage.
2. Open Flash Fire and tap the '+' and select Wipe.
3. Make sure ONLY Dalvik Cache and Cache Partition are selected and tap the check mark in the upper right of the pop-up.
4. Tap the '+' again and tap 'Flash Zip or OTA'
5. From internal storage, select my zip package DragonMods.zip.
6. Tap FLASH and wait for everything to happen. This will take upwards of 10 minutes or more, depending on many variables so be very patient.
Install only select packages:
1. Place DragonMods.zip on your PC desktop. For this I use 7zip for Windows. Right click on the zip file and select 7-zip and open as archive.
2. Double click on system folder then double click on the folder you you want to delete. Example: If you do not want to install my framework-res APK, delete the framework folder. If you don't want CM Browser, delete that folder.
3. Once you are happy with your custom installation, replace the zip on your tablet's internal storage and follow installation instructions above.
ViPER4Android:
I have not included this in my zip for a few reasons. The foremost one being it requires you to delete a couple key files so I would rather you make the choice yourself rather than me doing it for you. I confirm it is full operational and functional and doesn't force close once installed properly. If you aren't convinced, just activate the notification.
1. Download the V4A2.3.4.0 Lollipop.zip provided at the Google Drive link below or go to this thread and download it. Make sure Selinux switch is installed, set to permissive with notification enabled. Also make sure BusyBox is installed.
2. On your tablet, go to /vendor or /system/vendor and tap etc.
3. Back up both of the audio files, audio_effects.conf and audio_policy.conf then delete them from the folder
4. Go to storage -> downloads and tap on the V4A2.3.4.0 Lollipop.zip, system, etc, and extract the two .conf files.
5. Go to the folder they were extracted into and copy both of them to /system/etc, overwriting the ones that are located there. Set the permissions (rw-r--r--) and reboot.
6. Go to downloads again, tap the V4A2.3.4.0 Lollipop.zip and system, app and extract the APK.
7. Create a folder in /system/app titled 'ViPER4Android'. Rename the APK 'ViPER4Android.apk' and paste it into the folder.
8. Set folder permission rwxr-xr-x, APK permission rw-r--r-- and reboot.
9. Open App and follow instructions. Tap upper right for menu and set UI to expert.
build.prop edits:
1. ViPER4Android needs a few tweaks to the build prop. If these variables and values already exist in your build.prop, please change them to the ones below. You can use Build Prop Editor or a root file explorer to make the edit:
Code:
Ipa.decode=false
tunnel.decode=false
lpa.use-stagefright=false
2. The WiFi needs a tiny bit more tweaking here too. Locate the following line in /system/build.prop and add the value to it as seen below (there is currently no value set and the best ones are 1, 6 or 11. You can use any number as long as it's 11 or less.
Code:
ro.wifi.channels=11
3. Locate the following lines in your build.prop. Back them up to a text file then delete both lines (numbers might be different):
Code:
wifi rssi->bar thresholds
persist.wifi.rssi.thresholds=-84,-75,-66,-55
Downloads:
DragonMods.zip (the main zip you need) - Current as of November 16, 2018
DragonMods5-6-2-0.zip (for users on FireOS 5.6.2.0)
V4A2.3.4.0_Lollipop.zip
That's all for now. This includes pretty much every hack, trick and tweak I have been able to achieve on these tablets so far. I hope you enjoy all of these and watch out for more of my hacks. Thank you everyone for making all of this possible! Don't forget to hit the thank button
Change Log
- November 22, 2018: Updated links to reflect the following: Fixed issue with Trebuchet launcher missing from zip by readding it to the folder. I don't know How I missed that. Replaced google Clock with correct APK. I meant to put in the DeskClock available from the Play Store. If anyone would like a zip containing the CM/AOSP DeskClock that changes colors as the day and night change, let me know and I will upload the APK. The reason for this mess: I used the wrong zip template I have for this package. The one with the mess was intended for my personal device. My apologies.
Problems:
-If you delete Amazon photos, when you tap settings, display settings, wallpaper, it will kick you back to main settings. Solution: download Amazon photos from the play store as a user app then do this:
Code:
adb shell
su
pm disable com.amazon.photos
pm clear com.amazon.photos
.
Function returns.
not sure how to install this
darkfortedx said:
not sure how to install this
Click to expand...
Click to collapse
Flash it in flash fire...says that in the OP
Be advised
I just downloaded it and realized I didn't put th right folder in for Trebuchet launcher so the folder is empty. So don't flash this zip until I can fix it when I get home later.
Update November 22, 2018 1:42PM:
- Fixed issue regarding launcher. See change log at the end of the OP.
after changing the permissions for /system/vendor/etc to rw-r-r and rebooting, get the boot screen then boot to quick flash on desktop then to black, can only get the power down window to show when holding power. I'm trying to change the permissions back in adb. . can you please send code to do this correctly? if this is the correct approach. i backed up the 2 files in es file explored back up folder.
I got it....
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/vendor/etc
this worked... took me a while to figure it out. But it's all part of learning!
---------- Post added at 01:37 AM ---------- Previous post was at 01:33 AM ----------
I missed that it was for the two files not the folder lol....
nikothebarber said:
I got it....
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/vendor/etc
this worked... took me a while to figure it out. But it's all part of learning!
---------- Post added at 01:37 AM ---------- Previous post was at 01:33 AM ----------
I missed that it was for the two files not the folder lol....
Click to expand...
Click to collapse
I have an update of this I'll upload later. I just want to make sure everything works as advertised. Apologies if not. I made a stupid mistake earlier that I fixed but might have missed a small thing or two.
Sent from my MotoG3 using XDA Labs
When I tried to flash it if flashfire, it will juz stuck in the first black screen for over 15 mins.
I can juz simply quit the app and everything remains the same and work fine though.
What would possibly be the problem?
@DragonFire1024
Tried to Install ViPER4Android with the steps and files you linked but was unsuccessful. When I bring up the Driver status and they all say no to Enabled. It already prompted me to install drivers which I did and re booted and still no go. I'm familiar with installing ViPER4Android and have it installed on my phone but not able to get it going in HD10. This tablet needs some way to higher the sound, sound on this tablet SUCKS. Any help would be greatly appreciated.
Touchpad64gb said:
Tried to Install ViPER4Android with the steps and files you linked but was unsuccessful. When I bring up the Driver status and they all say no to Enabled. It already prompted me to install drivers which I did and re booted and still no go. I'm familiar with installing ViPER4Android and have it installed on my phone but not able to get it going in HD10. This tablet needs some way to higher the sound, sound on this tablet SUCKS. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sorry I've been very sick the last several days and have spent most of it in bed. Until I can look and see what's wrong, I can suggest you try 'volume boost by goodev' on the play store. You may need to make it a system app though.
Sent from my MotoG3 using XDA Labs
jeffreyyip314 said:
When I tried to flash it if flashfire, it will juz stuck in the first black screen for over 15 mins.
I can juz simply quit the app and everything remains the same and work fine though.
What would possibly be the problem?
@DragonFire1024
Click to expand...
Click to collapse
Flash fire will take approx. 10+ mins sometimes to go through the files then about the same time until the red flash fire bar appears at the top. With flash fire you just have to wait.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Sorry I've been very sick the last several days and have spent most of it in bed. Until I can look and see what's wrong, I can suggest you try 'volume boost by goodev' on the play store. You may need to make it a system app though.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
Thanks for your response, get some rest and I'll patiently wait to see what you come up with...Thanks again
Touchpad64gb said:
Thanks for your response, get some rest and I'll patiently wait to see what you come up with...Thanks again
Click to expand...
Click to collapse
Try deleting the viper folder if you installed it via a file explorer. Reboot then install viper as a regular app. Don't open it. In a root file explorer go to /data/app and copy viper folder to /system/app then reboot.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Try deleting the viper folder if you installed it via a file explorer. Reboot then install viper as a regular app. Don't open it. In a root file explorer go to /data/app and copy viper folder to /system/app then reboot.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
I did that the first time. I had to enable Selinux Switch and enable Permissive which it seems like you have to enable each time you want to use Viper. The Driver Status now says NEON enabled, Enabled=Yes, Status=Normal, Audio Format= Supported but it still sounds like it makes no difference in boost in volume. The App you suggested Volume Booster works great. On my phone I can notice the difference on Volume quality and boost but not on the HD10 using Viper. What settings are you using? Maybe it's the settings.
Touchpad64gb said:
I did that the first time. I had to enable Selinux Switch and enable Permissive which it seems like you have to enable each time you want to use Viper. The Driver Status now says NEON enabled, Enabled=Yes, Status=Normal, Audio Format= Supported but it still sounds like it makes no difference in boost in volume. The App you suggested Volume Booster works great. On my phone I can notice the difference on Volume quality and boost but not on the HD10 using Viper. What settings are you using? Maybe it's the settings.
Click to expand...
Click to collapse
Did you rename the audio.conf files in vendor?
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Did you rename the audio.conf files in vendor?
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
No, I didn't see any instructions to do so. Was I supposed to?
Touchpad64gb said:
No, I didn't see any instructions to do so. Was I supposed to?
Click to expand...
Click to collapse
Yes. Rename them. But you should do it before installing viper.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
Yes. Rename them. But you should do it before installing viper.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
The original files were named the same as the files copied over that's why you have to allow it to overwrite. Original files and copied files were both named audio_effects.conf & audio_policy.conf. I also edited the build prop entries you mentioned. Can you share your build prop file so I can compare your entries to mine? What were the names you change audio_effects.conf & audio_policy.conf to?
Touchpad64gb said:
The original files were named the same as the files copied over that's why you have to allow it to overwrite. Original files and copied files were both named audio_effects.conf & audio_policy.conf. I also edited the build prop entries you mentioned. Can you share your build prop file so I can compare your entries to mine? What were the names you change audio_effects.conf & audio_policy.conf to?
Click to expand...
Click to collapse
Just put a _ at the end of .conf. I didn't add the removal of the vendor files in the zip and I think I stated that in the OP.
Sent from my MotoG3 using XDA Labs
If you are someone like me who loves using Android with your right hand then you might also hate what Google did to the navigation bar in the recent Android editions.
The back key is on the far left of the screen which is difficult to touch.
Before you could just go to system/usr/keyLayout/Generic.kl and edit the values of back and recent keys but nowadays it doesn't work on most of the phones since Google doesn't allow modifying navBar.
So here's how you can swap back and the recent in Android 10 and 11.
This will only work if you are rooted.
1) Get a file manager like Root Explorer or Mixplorer
2) Go to root/system_ext/priv_app or wherever the hell your SystemUI is.
3) Copy your SystemUI to phone memory.
4) Rename it from SystemUI.apk to SystemUI.zip
5) Now open it. Navigate to res/layout and look for back.xml and recent_apps.xml
6) Now for the back.xml name it to recent_apps.xml
For recent_apps.xml name it back.xml
( That is pretty much self-explanatory. We are just swapping here)
7) Get out and rename SystemUI.zip to SystemUI.apk again.
8) Now move newly edited SystemUI to root/system_ext/priv_app or wherever the hell your SystemUI was before.
9) Restart SystemUI. (Might get restarted automatically)
or simply reboot your phone.
10) Enjoy!
Credit :
Thanks to xda member @Tulsadiver for the idea
Thanks for the idea, but your method requires modification to /system which is not recommended. I suggest place the modified copy of systemUI.apk in a Magisk Module.
Never_Sm1le said:
Thanks for the idea, but your method requires modification to /system which is not recommended. I suggest place the modified copy of systemUI.apk in a Magisk Module.
Click to expand...
Click to collapse
Like this.
One is for a Pixel phone (SystemUIGoogle.apk). Second for SystemUI.apk
Edit: Currently formatted for Android 11 but if you go down into the vrtheme folder and change the "system_ext" folder to "product" it'll be good for Android 10.
Hey ! Thanks for the module , but for some reason it made the two buttons disappear and non-functioning , just vibrating when clicked ..
is there any solution for that ?
I am using DotOs android 11 on Redmi 5 plus vince
thanks in advance !
@Tulsadiver
The zip above doesn't work properly. Back buttons works but not visible. Regents buttons doesn't work and isn't visible.
Could you create one for the following android 11 rom please?
[GSI][ROM][ CURTANA | JOYEUSE | EXCALIBUR][11.0][AOSP+GAPPS][04/08/21]
Hi, I try to make the ROM compilation on my computer, but the script have somes issues: [email protected]:/media/USB/AOSP_11$ patch -p1 < patch.txt patching file system/sepolicy/Android.mk [email protected]:/media/USB/AOSP_11$...
forum.xda-developers.com
Thx
k2828 said:
@Tulsadiver
The zip above doesn't work properly. Back buttons works but not visible. Regents buttons doesn't work and isn't visible.
Could you create one for the following android 11 rom please?
[GSI][ROM][ CURTANA | JOYEUSE | EXCALIBUR][11.0][AOSP+GAPPS][04/08/21]
Hi, I try to make the ROM compilation on my computer, but the script have somes issues: [email protected]:/media/USB/AOSP_11$ patch -p1 < patch.txt patching file system/sepolicy/Android.mk [email protected]:/media/USB/AOSP_11$...
forum.xda-developers.com
Thx
Click to expand...
Click to collapse
This is phone and sometimes even firmware update specific. If you are running this rom and care to pull your systemui.apk, I'll take a look but I don't have time to download a entire rom, extract it, and then modify it.
@Tulsadiver
Thx
mody3bdo said:
Hey ! Thanks for the module , but for some reason it made the two buttons disappear and non-functioning , just vibrating when clicked ..
is there any solution for that ?
I am using DotOs android 11 on Redmi 5 plus vince
thanks in advance !
Click to expand...
Click to collapse
I'm using dotOS 5.1 Android 11 on Redmi Note 7. I managed to get it to work by following the manual steps. The Magisk module gave me the same problem.
Thank you OP. Ur a live saver. I hated the left side back button and been searching everywhere for this. Thank you!
I couldn't made the Magisk module working. I'm using conquerors android 11 on redmi note 7 pro
RyanCr7 said:
If you are someone like me who loves using Android with your right hand then you might also hate what Google did to the navigation bar in the recent Android editions.
The back key is on the far left of the screen which is difficult to touch.
Before you could just go to system/usr/keyLayout/Generic.kl and edit the values of back and recent keys but nowadays it doesn't work on most of the phones since Google doesn't allow modifying navBar.
So here's how you can swap back and the recent in Android 10 and 11.
This will only work if you are rooted.
1) Get a file manager like Root Explorer or Mixplorer
2) Go to root/system_ext/priv_app or wherever the hell your SystemUI is.
3) Copy your SystemUI to phone memory.
4) Rename it from SystemUI.apk to SystemUI.zip
5) Now open it. Navigate to res/layout and look for back.xml and recent_apps.xml
6) Now for the back.xml name it to recent_apps.xml
For recent_apps.xml name it back.xml
( That is pretty much self-explanatory. We are just swapping here)
7) Get out and rename SystemUI.zip to SystemUI.apk again.
8) Now move newly edited SystemUI to root/system_ext/priv_app or wherever the hell your SystemUI was before.
9) Restart SystemUI. (Might get restarted automatically)
or simply reboot your phone.
10) Enjoy!
Credit :
Thanks to xda member @Tulsadiver for the idea
Click to expand...
Click to collapse
I used root explorer try to copy the modified system UI but denied. why?
sailorcanfly said:
I used root explorer try to copy the modified system UI but denied. why?
Click to expand...
Click to collapse
You need to give write permission to root explorer. It's written as RW on top of Root Explorer app.
Or use Mixplorer. Give it Allow management of all files permission.
the phone is stuck on this "Phone starting up", I tried to back the original file but it doesn't work, can anyone help me to back it to the previous state?
Works with me on Arrows OS a12
Still works for a12 aosp rom poco x3 nfc
Never_Sm1le said:
Thanks for the idea, but your method requires modification to /system which is not recommended. I suggest place the modified copy of systemUI.apk in a Magisk Module.
Click to expand...
Click to collapse
Thanks for the great advice but I didn't quite get what do you mean by "place the modified copy of systemUI.apk in a Magisk Module". Can you explain the steps in a bit more detail? Thank you very much.
ScarletMeteorC said:
Thanks for the great advice but I didn't quite get what do you mean by "place the modified copy of systemUI.apk in a Magisk Module". Can you explain the steps in a bit more detail? Thank you very much.
Click to expand...
Click to collapse
Are you rooted with Magisk? What Android level are you on...11, 12, etc.
Tulsadiver said:
Are you rooted with Magisk? What Android level are you on...11, 12, etc.
Click to expand...
Click to collapse
Thank you so much for the prompt reply. I loved the experience of the original android and I am not so interested in modifying it bc the navigation button was the only thing I thought I cannot get used to. After a week or so I re-trained my muscle memory to accommodate the return button on the left and the recent button on the right. Happy days now!
There is many suggestion, which one is best.
Tulsadiver said:
Like this.
One is for a Pixel phone (SystemUIGoogle.apk). Second for SystemUI.apk
Edit: Currently formatted for Android 11 but if you go down into the vrtheme folder and change the "system_ext" folder to "product" it'll be good for Android 10.
Click to expand...
Click to collapse
hi, my system does not have the file SystemUI.apk. Can I swap the recent button and the back button with the following files?
SystemUIEx.apk
framework-res.apk
#:/system/product/priv-app # ls
ls
ConfigUpdater GooglePartnerSetup Phonesky_CN
GmsCore OobConfig SettingsIntelligence
#:/system # find /system -name SystemUI*
find /system -name SystemUI*
/system/priv-app/SystemUITools
/system/priv-app/SystemUITools/oat/arm/SystemUITools.vdex
/system/priv-app/SystemUITools/oat/arm/SystemUITools.odex
/system/priv-app/SystemUITools/SystemUITools.apk
/system/priv-app/SystemUIEx
/system/priv-app/SystemUIEx/SystemUIEx.apk
/system/priv-app/SystemUIEx/oat/arm64/SystemUIEx.odex
/system/priv-app/SystemUIEx/oat/arm64/SystemUIEx.vdex
r3gister said:
hi, my system does not have the file SystemUI.apk. Can I swap the recent button and the back button with the following files?
SystemUIEx.apk
framework-res.apk
#:/system/product/priv-app # ls
ls
ConfigUpdater GooglePartnerSetup Phonesky_CN
GmsCore OobConfig SettingsIntelligence
#:/system # find /system -name SystemUI*
find /system -name SystemUI*
/system/priv-app/SystemUITools
/system/priv-app/SystemUITools/oat/arm/SystemUITools.vdex
/system/priv-app/SystemUITools/oat/arm/SystemUITools.odex
/system/priv-app/SystemUITools/SystemUITools.apk
/system/priv-app/SystemUIEx
/system/priv-app/SystemUIEx/SystemUIEx.apk
/system/priv-app/SystemUIEx/oat/arm64/SystemUIEx.odex
/system/priv-app/SystemUIEx/oat/arm64/SystemUIEx.vdex
Click to expand...
Click to collapse
r3gister said:
hi, my system does not have the file SystemUI.apk. Can I swap the recent button and the back button with the following files?
SystemUIEx.apk
framework-res.apk
#:/system/product/priv-app # ls
ls
ConfigUpdater GooglePartnerSetup Phonesky_CN
GmsCore OobConfig SettingsIntelligence
#:/system # find /system -name SystemUI*
find /system -name SystemUI*
/system/priv-app/SystemUITools
/system/priv-app/SystemUITools/oat/arm/SystemUITools.vdex
/system/priv-app/SystemUITools/oat/arm/SystemUITools.odex
/system/priv-app/SystemUITools/SystemUITools.apk
/system/priv-app/SystemUIEx
/system/priv-app/SystemUIEx/SystemUIEx.apk
/system/priv-app/SystemUIEx/oat/arm64/SystemUIEx.odex
/system/priv-app/SystemUIEx/oat/arm64/SystemUIEx.vdex
Click to expand...
Click to collapse
You are welcome to try using this zip. Either upload your SystemUIEX.apk or do it yourself. Replace the ones that are currently in this zip.