[HOW-TO] Viper4android - Install the proper way (Root Required) - Galaxy Note 4 Themes and Apps

Viper4android: How to install it properly ​
This is something I've been meaning to write up for a long time now. All over XDA I see people have trouble with getting Viper4android working and I thought this might shed some light on the issue.
There are many zips out there that will install viper but most of them have other sound mods rolled into it and I prefer viper only. I find that most of the others often distort the sound a little, but with Viper4android only, the sound is just perfect for my tastes.
What you need:
- A root file explorer (RootExplorer, EsFileExplorer, etc.)
- Root (obviously)- Either Magisk or SuperSU
- If using Magisk you'll need a Permissive kernel. My kernel works with certain models and is permissive.
- If using SuperSU you can use enforcing, but will need an extra file that I'll cover later on.
- Some good music to listen to.
This method is really not much of revelation since it's actually on the Viper4android thread itself, but almost everyone tries to let the install the drivers automatically. Do not let the app install the drivers for you. It will install the old driver and it doesn't include the Neon driver.
First things first. We need to do a little cleanup just in case there are already some viper files or drivers partially installed.
Viper4android has three places in which it installs:
/system/lib/soundfx/
/system/etc/audio_effects.conf
/system/app/Viper4android.apk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Using your root explorer go to /system/lib/soundfx/ and look for any old V4A files and delete them. It should look like this, libv4a_fx_ics_X86.so. Also check in your system/app/ and check to see if you have the old viper app and if so delete that too (the newest version is 2.5.0.5). Note: if you already have the app installed you can go to the settings menu and select uninstall drivers and it should remove everything for you. Then just double check to make sure. Then uninstall the app unless it's the newest version and placed in /system/app/.
Once we have everything cleaned up it's just a matter of placing the right files in the right spot. I've attached a zip that has everything you will need in it. It is not a flashable zip. Just unzip it to get to the necessary files.
1. Place the Viper4android app in /system/app (no extra folder necessary) and change the permission to 0644 or rw-r-r
2. Place the .so files in /system/lib/soundfx/ and change permission to 0644 or rw-r-r
3. If you don't have any other sound mods installed you can swap out my audio_effects.conf file for yours and set permission to 0644 or rw-r-r, but if you do that back up your original file just in case (just rename the original to audio_effects.bak). If you do have other sound mods installed you'll want to add the following red lines to you existing audio_effects.conf file.
Code:
# List of effect libraries to load. Each library element must contain a "path" element
# giving the full path of the library .so file.
# libraries {
# <lib name> {
# path <lib path>
# }
# }
libraries {
[COLOR="red"]v4a_fx {
path /system/lib/soundfx/libv4a_fx_jb_NEON.so
}
#NECESSARY FOR XHIFI
v4a_xhifi {
path /system/lib/soundfx/libv4a_fx_jb_X86.so
}[/COLOR]
# This is a proxy library that will be an abstraction for
# the HW and SW effects
proxy {
path /system/lib/soundfx/libeffectproxy.so
}
# This is the HW implementation library for the effect
offload {
path /system/lib/soundfx/libaudioeffectoffload.so
And...
Code:
# }
# ...
# }
effects {
[COLOR="red"]v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}
#NECESSARY FOR XHIFI
v4a_standard_xhifi {
library v4a_xhifi
uuid d92c3a90-3e26-11e2-a25f-0800200c9a66
}
}[/COLOR]
soundalive {
library proxy
uuid 05227ea0-50bb-11e3-ac69-0002a5d5c51b
libsw {
Placement is everything with this. If there's an extra space or missing a space you'll will get the "drivers are not installed" error when opening the viper app. It took me several tries in the beginning to get the audio_effects.conf part of this right, but it will work when everything is correct.
4. This step is dependent on your setup. If you are using a permissive kernel this is not necessary. If you're using SuperSU with an enforcing kernel you'll need to flash the ViPER4Android-supolicy.zip that is included in the attached zip file.
Original instructions are here, but nobody seems to see them including myself for the longest time.
Now if everything is in place properly you should get this:
It should work with any music player (I mostly use Spotify), YouTube, video players, etc.
Enjoy.
Credits:
 @viper520 -for creating Viper4android 
 @zhuhang - for co-founding and continuing to maintain Viper4android
If anyone knows the identity of who created the ViPER4Android-supolicy.zip let me know. I would love to be able to give proper credits on that as well.

Thanks Mate Nice thread

Hi kevintm78, I have some questions.
1. In your Driver Status screen shoot you have Processing:Yes, I have Processing:No, what does that mean for me?
2. It is said to install or move Viper to System/app, does System/priv-app location achieve the same as System/app?
3. I've heard it said that using DDC and Convolver together is not adviseable, is this true?
4. where can I find/download more DDC profiles?
5. I'm on a Note 4 Android version 6.0.1 Rom: NEMESIS REFINED N7 port, on odd occasions after using the built-in "Smart
Manager app, viper's profile folder contents sometimes disappear, although the DDC and Kernel folders will remain intact.
Would you have ant idea why this happens? That said, I have found that if I delete the Cache and Data of the Smart Manager app, the Viper Profile folder contents will remain more often but as mentioned, they will disappear
6. On rare occasions the "Load effect profile" List would be in alphabetical order, is there a way to force this?
I would appreciat your thoughts and help for the questions mentioned.
Many Thanks for Your tutorial.

asia559571 said:
Hi kevintm78, I have some questions.
1. In your Driver Status screen shoot you have Processing:Yes, I have Processing:No, what does that mean for me?
2. It is said to install or move Viper to System/app, does System/priv-app location achieve the same as System/app?
3. I've heard it said that using DDC and Convolver together is not adviseable, is this true?
4. where can I find/download more DDC profiles?
5. I'm on a Note 4 Android version 6.0.1 Rom: NEMESIS REFINED N7 port, on odd occasions after using the built-in "Smart
Manager app, viper's profile folder contents sometimes disappear, although the DDC and Kernel folders will remain intact.
Would you have ant idea why this happens? That said, I have found that if I delete the Cache and Data of the Smart Manager app, the Viper Profile folder contents will remain more often but as mentioned, they will disappear
I would appreciat your thoughts and help for the questions mentioned.
Many Thanks for Your tutorial.
Click to expand...
Click to collapse
You're very welcome. I think I can help with some of your questions.
1. For processing, it will say no unless there's something playing. Try playing a song and then checking it again.
2. You can use priv-app if you'd like. The only difference between the two is that priv-apps are given more system permissions than just /system/app. The results should be the same though with either one.
3. I've been using them together and haven't noticed any negative impact. I'll see if I can find out more on that though, but you should be fine.
4. I think what you're looking for is IRS packages. You can find out more about it here. You can also download the starter IRS packs here. Viper4android has depricated they're XHFI features so I'm not sure that more DDC profiles are helpful anymore (though I could be completely wrong about that.) Most of the other DDC profiles I've found are at least a few years old now.
5. That's strange that they are being removed. Are the folders empty? Maybe that's why they are being removed. Try downloading the IRS starter pack, unzip it, and move the whole folder to the Viper4android/kernel folder on your sdcard. To get that folder to show up just press on the Convolver setting and it should create those folders for you. That's about the only reason I could think of as to why they are being removed.
Thank you by the way for asking those questions. That's something I need to cover a little more thoroughly. I definitely will expand on this topic if it looks like people are interested.

Thank you so much it works! but only for certain music player, i tried it with Phonograph and Samsung's stock music player and it works.
It doesn't work with spotify. I did the exact step you mentioned. I using note 4 exynos eRobot v33. any ideas why?

damadikaz said:
Thank you so much it works! but only for certain music player, i tried it with Phonograph and Samsung's stock music player and it works.
It doesn't work with spotify. I did the exact step you mentioned. I using note 4 exynos eRobot v33. any ideas why?
Click to expand...
Click to collapse
That's strange, Spotify is kind of the only music player I use. What does the driver status say when Spotify is playing? Did it say it's processing while the music is playing?

kevintm78 said:
That's strange, Spotify is kind of the only music player I use. What does the driver status say when Spotify is playing? Did it say it's processing while the music is playing?
Click to expand...
Click to collapse
I've attached the screenshot. pls check it.
I just check it with another streaming music player called Joox, V4A doesn't work either.
but when I play any local music files even using Solid File manager V4A works.

thnx for the explaination sir.. i have a question, why V4A not "active" after reboot..? i have to manually open the app to make it work every time after reboot.. thnx..

Same problem here. N910c with erobot v33 rom with native viper, magisk, permissive kernel, etc. And still, no processing with Spotify or deezer. Local files are processed.

Deleted

Danielreo said:
Same problem here. N910c with erobot v33 rom with native viper, magisk, permissive kernel, etc. And still, no processing with Spotify or deezer. Local files are processed.
Click to expand...
Click to collapse
Try to freeze soundalive

1.Install Viper as system App & start up app and load preferred version of driver
2.Update build.prop: root/system/build.prop
## ViPER4Android Build.prop Tweaks
lpa.decode=false
lpa.releaselock=false
lpa.use-stagefright=false
tunnel.decode=false

Nothing of the above worked here.
Even before the suggested configs, I realized that the bluetooth mode is processing like a charm. Phone speaker and headset still not.

I've followed your step by step (twice), and V4A still asks me to install the drivers...
I placed the apk on system/priv-app (the 1st attempt was on system/app), put the .so files on system/lib/soundfx, replaced the audio.conf on system/etc, changed the permissions exaclty to rw-r-r, then used TWRP Recovery mode to install the SU Policy - even though I have a selinux changer.
On Default Storage, the only option I have to set is "/storage/emulated/0/", not sure if this matters (I think it doesn't, probably it's just where it'll save your profiles etc).
Tried restarting the phone, to see if it would detect, tried to switch compatible/normal, deactivated selinux (using v4a dev mode), tried to change the permissions to rwx-rx-rx... nothing worked. V4A still asks me for the drivers.
It does work, however I install it, but only on compatible mode, and not with Spotify LOCAL synced files - which is a great issue to me.
PS.: I have NoozXoide installed here - cause it's the only one which also works with local files on Spotify. I've already tried to unninstal it and redo all the procedures, though...
OH, also, should I deactivate Android stock Audio effects app?
Can you help me please OP?

mateusonego said:
I've followed your step by step (twice), and V4A still asks me to install the drivers...
I placed the apk on system/priv-app (the 1st attempt was on system/app), put the .so files on system/lib/soundfx, replaced the audio.conf on system/etc, changed the permissions exaclty to rw-r-r, then used TWRP Recovery mode to install the SU Policy - even though I have a selinux changer.
On Default Storage, the only option I have to set is "/storage/emulated/0/", not sure if this matters (I think it doesn't, probably it's just where it'll save your profiles etc).
Tried restarting the phone, to see if it would detect, tried to switch compatible/normal, deactivated selinux (using v4a dev mode), tried to change the permissions to rwx-rx-rx... nothing worked. V4A still asks me for the drivers.
It does work, however I install it, but only on compatible mode, and not with Spotify LOCAL synced files - which is a great issue to me.
PS.: I have NoozXoide installed here - cause it's the only one which also works with local files on Spotify. I've already tried to unninstal it and redo all the procedures, though...
OH, also, should I deactivate Android stock Audio effects app?
Can you help me please OP?
Click to expand...
Click to collapse
Are you using magisk or supersu? Also, I've recently found a secondary spot for the libs and audio-effects.conf if using certain port roms. If using a stock rom that's enforcing, I would supersu and the su policy file.
If it is a stock rom I never had to freeze or uninstall anything to get it fully working. But I can help you get it going if you're still up for it.

kevintm78 said:
Are you using magisk or supersu? Also, I've recently found a secondary spot for the libs and audio-effects.conf if using certain port roms. If using a stock rom that's enforcing, I would supersu, and I flashed the su policy file.
If it is a stock rom I never had to freeze or uninstall anything to get it fully working. But I can help you get it going if you're still up for it.
Click to expand...
Click to collapse
Thank you very much for replying mate!! :angel: And sorry for misinforming.
I have a Moto G4 Plus (XT1360) with stock Android 7.0 (never rooted this device before - but I used V4A back in 2015, in a s.g. 4 mini), TWRP, Elemental X, supersu and busybox, if that matters... It was supposed to be enforcing, but I also got SELinuxModeChanger. I tried installing V4A on both system/apps & system/priv-apps. Oh, and I'm listening through headset.
I tried several combinations to try to "trick" the app, tried install drivers > deleted them, tried not to install, tried not to install > use on compatible mode/normal, tried install > renamed the .so provided here ones as the original isc... tried all again restarting my phone between steps, tried all the mentioned them then reflash supolicy, tried all and killing the selinux on dev-mode before playing songs, tried the Build.prop Tweaks... nothing worked, every time I open V4A, it asks to install the drivers. And it does work afterwards, but only on Compatible, and with Spotify, and not the local files, neither Youtube etc.
I was taking a look on the apk with ES exp, I know **** about android, but there seems to be 4 .so files inside... would there be any way to reference all the 4 on audio.conf?
Oh, I shoul mention I also tried all that I mentioned above, but replacing the files with the 4 ones I extracted from the apk between steps etc - it didn't ask for install drivers when I started it! But again, only worked on Compatible, etc...
I did some research - and got nothing -, saw some people mentioning to freeze Sound Alive, or even delete it. As I mentioned, the stock eq I got is Audio Effects, but I also saw sometimes soundalive on audios.conf... but again, I know **** about Android :/
Tks to be trying to help!

mateusonego said:
Thank you very much for replying mate!! :angel: And sorry for misinforming.
I have a Moto G4 Plus (XT1360) with stock Android 7.0 (never rooted this device before - but I used V4A back in 2015, in a s.g. 4 mini), TWRP, Elemental X, supersu and busybox, if that matters... It was supposed to be enforcing, but I also got SELinuxModeChanger. I tried installing V4A on both system/apps & system/priv-apps. Oh, and I'm listening through headset.
I tried several combinations to try to "trick" the app, tried install drivers > deleted them, tried not to install, tried not to install > use on compatible mode/normal, tried install > renamed the .so provided here ones as the original isc... tried all again restarting my phone between steps, tried all the mentioned them then reflash supolicy, tried all and killing the selinux on dev-mode before playing songs, tried the Build.prop Tweaks... nothing worked, every time I open V4A, it asks to install the drivers. And it does work afterwards, but only on Compatible, and with Spotify, and not the local files, neither Youtube etc.
I was taking a look on the apk with ES exp, I know **** about android, but there seems to be 4 .so files inside... would there be any way to reference all the 4 on audio.conf?
Oh, I shoul mention I also tried all that I mentioned above, but replacing the files with the 4 ones I extracted from the apk between steps etc - it didn't ask for install drivers when I started it! But again, only worked on Compatible, etc...
I did some research - and got nothing -, saw some people mentioning to freeze Sound Alive, or even delete it. As I mentioned, the stock eq I got is Audio Effects, but I also saw sometimes soundalive on audios.conf... but again, I know **** about Android :/
Tks to be trying to help!
Click to expand...
Click to collapse
Do you have an etc folder in /system/vendor/ ? Some roms have another audio_effects.conf in that location or maybe it's in another location. I have to be honest I'm not familiar with many other kinds of phones besides samsung.
The instructions I'm using are the ones taken from the viper4android thread itself and works with at least this phone with no other steps necessary. Maybe you can find some hints in that thread but I'm thinking that the conf file is either in another location or its different from samsung's version so it's not being found.
The other lib files inside the app aren't necessary. They are just there for different android versions. One set is for ICS and below and the other is for JB and above. The app installs the ICS drivers by default which is why I like using this method instead.
If you want, upload your original audio_effects.conf file. I'll try and modify it for you and see if we can figure out why the drivers aren't being found.

kevintm78 said:
Do you have an etc folder in /system/vendor/ ? Some roms have another audio_effects.conf in that location or maybe it's in another location. I have to be honest I'm not familiar with many other kinds of phones besides samsung.
The instructions I'm using are the ones taken from the viper4android thread itself and works with at least this phone with no other steps necessary. Maybe you can find some hints in that thread but I'm thinking that the conf file is either in another location or its different from samsung's version so it's not being found.
The other lib files inside the app aren't necessary. They are just there for different android versions. One set is for ICS and below and the other is for JB and above. The app installs the ICS drivers by default which is why I like using this method instead.
If you want, upload your original audio_effects.conf file. I'll try and modify it for you and see if we can figure out why the drivers aren't being found.
Click to expand...
Click to collapse
Wow, that was right on spot! I had another audio_effects conf on vendor/etc. So, I replaced it with yours.
I removed the excessive .so I put on the lib/soundfx, and let only the jb and, later, the ics file.
Now, Viper asks me to install the drivers even after I've already let it install and rebooted :/ and for some reason, it doesn't work both on normal nor compatible mode (ok, as expected, since it's asking to install etc). I checked to see if it had rewrite anything on audio_effects.conf, but it didn't in neither of the files, on system/etc nor vendor/etc. They were still pointing the libraries to the jb files, and v4a did install the ics files on system/lib/soundfx, either way...
It gets weirder and weirder.
UPDATE: I got V4A to work once I commented the jb drivers lines, and re-included the ics path reference on audio_effects.conf at vendor/etc. It's not asking me to install the drivers again, anymore, but it's still not working with local synced files... I tried leaving it pointing to 2 paths, and tried including v4a_neon or something like that, so I could reference the 2 most important drivers, but it only works with v4a_fx pointing only to the ics file, and everything else is ignored.
UPDATE 2: I opened the backup I've mentioned below, and unfortunately I'm pretty sure I haven't done the backup and it is actually your file before I do any mod.
I'm sending you what I THINK is my backup but it might be just a backup of yours before I changed some stuff just to test (I replaced my modified files by copying the original one I had on downloads after testing, I got back to yours version on both /etc), sorry. (don't think so, though)

@kevintm78 hey OP, you there?

kevintm78 said:
Viper4android: How to install it properly ​
This is something I've been meaning to write up for a long time now. All over XDA I see people have trouble with getting Viper4android working and I thought this might shed some light on the issue.
There are many zips out there that will install viper but most of them have other sound mods rolled into it and I prefer viper only. I find that most of the others often distort the sound a little, but with Viper4android only, the sound is just perfect for my tastes.
What you need:
- A root file explorer (RootExplorer, EsFileExplorer, etc.)
- Root (obviously)- Either Magisk or SuperSU
- If using Magisk you'll need a Permissive kernel. My kernel works with certain models and is permissive.
- If using SuperSU you can use enforcing, but will need an extra file that I'll cover later on.
- Some good music to listen to.
This method is really not much of revelation since it's actually on the Viper4android thread itself, but almost everyone tries to let the install the drivers automatically. Do not let the app install the drivers for you. It will install the old driver and it doesn't include the Neon driver.
First things first. We need to do a little cleanup just in case there are already some viper files or drivers partially installed.
Viper4android has three places in which it installs:
/system/lib/soundfx/
/system/etc/audio_effects.conf
/system/app/Viper4android.apk
View attachment 4308261
View attachment 4308262
View attachment 4308263
View attachment 4308264
View attachment 4308265
Using your root explorer go to /system/lib/soundfx/ and look for any old V4A files and delete them. It should look like this, libv4a_fx_ics_X86.so. Also check in your system/app/ and check to see if you have the old viper app and if so delete that too (the newest version is 2.5.0.5). Note: if you already have the app installed you can go to the settings menu and select uninstall drivers and it should remove everything for you. Then just double check to make sure. Then uninstall the app unless it's the newest version and placed in /system/app/.
Once we have everything cleaned up it's just a matter of placing the right files in the right spot. I've attached a zip that has everything you will need in it. It is not a flashable zip. Just unzip it to get to the necessary files.
1. Place the Viper4android app in /system/app (no extra folder necessary) and change the permission to 0644 or rw-r-r
2. Place the .so files in /system/lib/soundfx/ and change permission to 0644 or rw-r-r
3. If you don't have any other sound mods installed you can swap out my audio_effects.conf file for yours and set permission to 0644 or rw-r-r, but if you do that back up your original file just in case (just rename the original to audio_effects.bak). If you do have other sound mods installed you'll want to add the following red lines to you existing audio_effects.conf file.
Code:
# List of effect libraries to load. Each library element must contain a "path" element
# giving the full path of the library .so file.
# libraries {
# <lib name> {
# path <lib path>
# }
# }
libraries {
[COLOR="red"]v4a_fx {
path /system/lib/soundfx/libv4a_fx_jb_NEON.so
}
#NECESSARY FOR XHIFI
v4a_xhifi {
path /system/lib/soundfx/libv4a_fx_jb_X86.so
}[/COLOR]
# This is a proxy library that will be an abstraction for
# the HW and SW effects
proxy {
path /system/lib/soundfx/libeffectproxy.so
}
# This is the HW implementation library for the effect
offload {
path /system/lib/soundfx/libaudioeffectoffload.so
And...
Code:
# }
# ...
# }
effects {
[COLOR="red"]v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}
#NECESSARY FOR XHIFI
v4a_standard_xhifi {
library v4a_xhifi
uuid d92c3a90-3e26-11e2-a25f-0800200c9a66
}
}[/COLOR]
soundalive {
library proxy
uuid 05227ea0-50bb-11e3-ac69-0002a5d5c51b
libsw {
Placement is everything with this. If there's an extra space or missing a space you'll will get the "drivers are not installed" error when opening the viper app. It took me several tries in the beginning to get the audio_effects.conf part of this right, but it will work when everything is correct.
4. This step is dependent on your setup. If you are using a permissive kernel this is not necessary. If you're using SuperSU with an enforcing kernel you'll need to flash the ViPER4Android-supolicy.zip that is included in the attached zip file.
Original instructions are here, but nobody seems to see them including myself for the longest time.
Now if everything is in place properly you should get this:
View attachment 4308290
It should work with any music player (I mostly use Spotify), YouTube, video players, etc.
Enjoy.
Credits:
@viper520 -for creating Viper4android
@zhuhang - for co-founding and continuing to maintain Viper4android
If anyone knows the identity of who created the ViPER4Android-supolicy.zip let me know. I would love to be able to give proper credits on that as well.
Click to expand...
Click to collapse
This worked for me.
You did not mention where to insert the audio_effects.contf file ... this file should be placed in the /vendor/etc
also you did not state that we would have to install the app after placing it in the /system/app.
Thanks once again

Related

[TEAM XPOSED] [Guide]9/21/11: How to dissect a ROM and mod it to your satisfaction.

Hi guys, I'm back again with somewhat of a guide.
How to dissect, repackage, and flash a ROM to your satisfaction without a kitchen!
Don't let anyone else fool you. The awesome devs at XDA, one in particular dsixda have made making ROMs very easy with kitchens. But you don't need to go through the process of installing and using one to get a ROM the way you want it. If installing and working with a kitchen seems too cumbersome and/or hard, or you're tired of waiting for or asking your ROM chef to include/exclude/change a feature, then this guide is for you.
ROMs aren't scary things, they're actually quite simple in terms of structure. As long as they're built correctly from the get go, you will learn how to mod it to suit your needs.
Tools needed: (most of which will be included in this guide)
A base ROM (start with your favorite)
WinRAR (or any good archiver)
Notepad++ (Recommended or something that can handle files encoded in UNIX)
SignAPK/APK Manager/APKTOOL/smali/baksmali (optional/advanced)
Time
Patience
Common sense (can't stress this enough)
Step 0:
-Start with a clean working environment, such as a folder or partition dedicated to this task. Your desktop probably won't be very good if you have a lot of stuff on it already.
Step 1:
-Using the archiver of your choice, you will need to extract the ROM to the work environment you've set up in Step 0.
--Your final result will look something similar to this:
NOTE: I am using my ROM as a reference.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Most ROMs will follow this structure, with some utilizing the folders "sdcard" and possibly others, depending on how customized they are. But as long as you have the /system folder, you will be fine. It is where you will probably spend the majority of your modding time. Get a feel for how the folder structure is. Navigate through them (don't make any changes). This guide will focus mainly on removing and adding apps, the more advanced stuff such as editing text files (with the exception of build.prop) and apks may come later.
NOTE: Please keep the original archive, do not delete it after extracting.
Step 2:
Navigate to the /system folder, which again should look similar to this:
Step 3:
The first folder we'll focus on is app. This is one of the most important folders when customizing your ROM. It will look something like this:
This folder is important because it houses your 'system apps', which are included in your ROM and cannot be uninstalled by traditional means. Here you can remove or add your own apps you want to include as system apps. Remember that not all apps are capable of running as system apps--actually, apps that are placed in this folder receive a higher permission level than apps that are placed in /data/app, so use caution when adding your own here. I would also suggest creating a "removed" folder [in a different location] and move any apps you decide to take away to here so you'll have them in case you remove something that causes a side effect you weren't intending to cause. If you feel comfortable with your WinRAR or 7zip skills, most of the images in these apks can be simply overwritten (this is initially how themes are created, among other ways). Be careful not to overwrite any 9.pngs because they are a special format. You can simply explore (not extract) them with your favorite archive program and replace images as you find them, which will typically reside in the res/drawable and res/drawable-hdpi folders.
Step 4:
Next up is the bin folder. This folder is very tricky and I would advise caution against removing anything that's currently in here unless you get real familiar with the contents of this folder. It will look something like this:
Most ROMs will include all the necessary scripts you will need in this folder. However, it doesn't hurt to familiarize yourself with it. Scripts such as bash and even sometimes busybox, can be installed here. If you're working with a very stock ROM, and I mean stock as in the only thing that was changed is adding root, then it wouldn't hurt to add bash here, other than that, let's move on.
Step 5:
Here we have the customize folder. This folder is pretty important as well. It holds all of your first boot activities and pretty much sets your phone up after you've flashed and/or updated ROMs. It looks like this:
Things start to get more involved and interesting around here. You'll notice three sub-folders inside of here, which house various customization scripts. To be honest, I'm not even sure how many of these get ran, but I'm almost positive the ones labeled "default" do get ran. Here's where Notepad++ will finally start to come in handy! If you're looking to do quick editing, then you can open any one of these xml files in Notepad++ and poke around. (For advanced script editing, I would suggest looking at the appropriate Android documentation. I'll see if I can get a link to that up.)
NOTE: Be VERY careful of what you remove from these xml files, the syntax has to be perfect, otherwise the script won't get initialized. I would suggest copying everything you intend on editing to another folder of the same name, in a different location of course, so that you can have copies. True beginners should not attempt editing any files in here until you familiarize yourself with their syntax.
Folder structure:
-CID
--cidProfile1.xml: I don't think this file gets parsed. However, I do take the time to remove language settings that I will never use, just for my own OCD reasons.
--cidProfile2.xml: I don't think this file gets parsed. However, I do take the time to remove language settings that I will never use, just for my own OCD reasons.
--default.xml: Settings such as screen timeouts, IME language settings, etc gets parsed here. Nothing of too much importance. However, I do take the time to remove language settings that I will never use, just for my own OCD reasons.
-MNS
--default.xml: This is probably the single most important file in the customize folder. Here houses most, if not all the first boot settings that get parsed, such as widget placement, bookmarks, and a whole plethora of other settings. This is a very fun and interesting file to edit, but again i heavily caution you to edit this file if you're a beginner. One simple mistake can lead to nothing getting parsed here--a mistake I've made a few times because of incorrect syntax.
-resource: This is probably the second most important folder in the customize section. Here lies all of the thumbnails and wallpapers for Sense. If you are planning on removing Sense, you can safely remove all the files here with the exception of CCInfo.txt. You can also replace the images as well as boot/power down animations here.
Step 6:
Ah, the etc folder--you'll spend probably no more than five minutes in this folder unless you're truly advanced, which means this guide is probably meaningless to you. It houses a lot of useless epub (ereader) books and looks like this:
If you have time, you can definitely do some exploring of files in here with your favorite text editor (Notepad++) and see if anything is of significance. If you find something, please report back! So far, I don't think very much, if anyone takes advantage of the actual files in this folder (the folders are a different story)
Folder structure:
-bluetooth: nothing to see here. bluetooth configuration files. could be useful down the line.
-dhcpcd: looks like configuration files for dhcp/dns/internet. could be useful down the line.
--dhcpcd-hooks: same as above
-fakeserverxml: This folder looks strange, even has a strange name. I assume if you're removing Sense, this won't be needed either. I'm not even sure it's needed WITH Sense. Poking around revealed some configuration files for what appears to be HTC Hub and scenes, widgets, skins, and other things.
-firmware: I wouldn't touch anything in here unless you know exactly what you're doing.
-init.d: Finally, something that matters! A lot of ROM chefs make use of this folder because it initializes scripts in here upon system boot. You'll see various things in here from various ROMs including: zipaligning, overclocking, kernel stuff, apps2sd, and more. If you know what you're doing, you could even drop your on initialization scrips into this folder and have them boot with the system. Be careful what you do in this folder though. You want to make sure you are following the correct set of steps to either add or remove things. I would poke around with a text editor at those files to see any dependencies, etc.
-iproute2: Nothing here for the average user.
-permissions: If you're removing Sense, without any intent on having it return, remove the relevant files from this folder as well. Other than that, let's move on.
-ppp: Nothing here for the average user.
-security: Nothing here for the average user.
-slideshow: Safe to get rid of. Inside are pictures that Sense uses as a slideshow.
-soundimage: Nothing here for the average user. However, things in here look promising for sound enhancement!
-terminfo: Nothing here for the average user.
--l: Same as above
--u Same as above
-updatecmds: Nothing here for the average user.
-wifi: Nothing here for the average user. However, you may be able to replace the wpa_supplicant file with a modified one for WiFi improvements.
-wimax: Nothing here for the average user. However, the files in the sub-folders here may be used in the future to enhance or modify WiMAX.
--dhcp: Same.
--sequansd: Same.
Before we move on, if you're going to use any sort of adblocking, your preconfigured hosts file should go here. Downloading ad-free from the market will overwrite this file when updating hosts, but if you want to supply your ROM users with a hosts file already somewhat updated, you can place that here. Looking at the various .sh/txt/csv/cfg/* files in Notepad++ will show you some defaults you can change, if you're comfortable in your editing skills, take a look at some of them and see what you can do. Not even I have bothered to look through most of these.
Step 7:
In and out like a robbery for this folder, "fonts", which houses the default fonts that Android uses for various things. I like to replace the clocktopia (which is used on the aosp lockscreen as the clock font) with the honeycomb clock font. Other than that, fonts replaced in here must retain the Android naming structure:
Step 8:
The framework folder is very...sensitive aka dangerous. Deleting or modifying the wrong thing in here can render your system unbootable. Until you're more seasoned in modifying ROMs, I would steer clear of this folder. However, the framework-res.apk file can be used to modify a lot of images to change the look, or "theme" of your ROM. So again, if you feel comfortable, fire up that archive program and get to replacin', otherwise let's move on:
If you're anything like me (anal) then you will wanna remove anything from the framework folder that has anything to do with apps you've removed. For instance, there is a blockbuster file in here that you can safely remove if you've removed the blockbuster app. Again, be careful with what you modify or remove from here, because your system can quickly become unbootable which will leave you wondering what happened.
Step 9:
The lib folder, like the framework folder, is very sensitive aka dangerous. Deleting or modifying the wrong thing in here can render your system unbootable. Until you're seasoned in modifying ROMs, I would steer clear of this folder. However, there are a few things that can be done in here if you've deleted other apps:
Folder structure:
-bluez-plugin: nothing here for the average user.
-egl: nothing here for the average user.
-hw: nothing here for the average user.
-modules: This is where kernel modules for things like WiFi/WiMAX/TUN/CIFS/ETC go. If you are modifying a ROM, and are including a kernel, be sure to delete what's here, and add the modules that came with the kernel. Not doing so will more than likely make its associated parts not function. Example: Error starting WiFi can usually be traced to wrong modules in this folder after updating a kernel.
-plugins: This folder houses plugins for different preinstalled apps. For instance, the Adobe Flash plugin would be here, but if you remove Flash from your ROM (since you can get it from the market and may be more updated than what was included) you should remove its associated files. I wouldn't remove the flashlite plugin though.
-soundfx: nothing here for the average user.
The lib folder can be very overwhelming from the sheer number of files in here but the majority of them will have little of no value to the average user. BUT, you should definitely check here if you are removing any system apps for associated lib files. For instance, Swype is included on HTC's stock software, and if you remove it from the /system/app folder, you want to come here and remove its associated lib file. There won't be a lib file for every program you remove, but it's good to double check here afterward to make sure you get all traces of it gone.
Step 10:
The media folder, probably the easiest folder ever, and least time spent in here. This folder controls all the built in audio sounds such as notifications/ringtones/etc as well as any other media related files, like video clips, images that would indicate an animation, etc:
Folder structure:
-audio: parent folder for system sounds.
--alarms: self explanatory.
--notifications: self explanatory.
--ringtones: self explanatory
--ui: self explanatory
-GPU: nothing here for the average user. Not sure what it even is for.
-mms: nothing here for the average user. Not sure what it even is for.
-weather: This folder isn't really of any use, but it does contain weather animations that the HTC weather app uses. If by some reason you want to edit, replace, or modify those animations, here they are. I would suggest placing files of the same resolution in here.
Be sure to place the files you want in their respective folders, because they won't show up when you try and select them for things they aren't intended for. For instance, placing notification sounds in the ringtones folder will make them not show up when you go to choose a notification sound from within Android.
To be continued...
Now that this guide is progressing nicely, below you will find a list of items that I have removed or replaced. This list will be edited as I make further adjustments. For the sake of consistancy, I too am working with Freeza's rom FreEVO 3D 1.1, which can be downloaded from this same subforum. Please keep in mind that this list is based on my particular needs and is heavily dependent upon which custom rom you choose to modify.
-Here's what I've removed from /system/app
browser.apk
DCSStock.apk
DebugTool.apk
dms.apk
DockMode.apk
DSPManager.apk
EReader.apk
Flickr.apk
FriendStream.apk
GoogleQuickSearchBox.apk
HtcCarPanel.apk
HtcConnectedMedia.apk
HtcDirect.apk
HtcFacebook.apk
HtcFMRadio.apk
HtcGreader.apk
HtcHubSyncProvider.apk
HTCLivewallpaperStreak.apk
HtcMusic.apk
HtcMusicEnhancer.apk
HtcMusicMarkedItems.apk
HtcRecommends.apk
HtcRingtoneTrimmer.apk
HtcSoundRecorder.apk
HtcStreamPlayer.apk
HtcTwitter.apk
HTMLViewer.apk
JETCET_PRINT.apk
JETCET_PRINT_Resources.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
LMW.apk
MagicSmokeWallpapers.apk
Mail.apk
Mode10Wallpapers.apk
MyHTC.apk
picasapryramid.apk
PolarisOffice.apk
QuickLookup.apk
SetupWizrd.apk
SoundRecorder.apk
SprintZoneNC.apk
TrimIt.apk
VisualizationWallpapers.apk
VoiceDialer.apk
VpnServices.apk
Weather.apk
WeatherAgentService.apk
WeatherProvider.apk
WeatherSyncProvider.apk
WorldClock.apk
-Here's what I've removed from /system/customize/resource
hTC_bootanimation
hTC_downanimation
Sprint_bootanimation
Sprint_downanimation
-Here's what I've removed from /system/media:
-The entire /weather folder from /system/media .
-All unused ringtones (all but 2) from /system/media/audio/ringtones
-All unused notifications (all but 3) from /system/media/audio/notifications
-All unused alarms (all but 3) from /system/media/audio/alarms
I should also mention, not only can you remove these, you can also replace them with any .mp3 file you like. So in theory, you could remove every .mp3 from these folders and put your own .mp3 files in.
After removing all of the above contents from Freeza's rom, the flashable zip size has gone from 307MB to 168MB. This should just about conclude my list of removed .apk's and files from Freeza's rom. After a little more testing, I'll move the "to be tested" .apks into the list of safe to remove .apk's, and finally begin theming this thing
Congratulations on taking the first step towards customizing your rom. More information to follow as I further refine this rom. Happy flashing!
hockeyfamily737 said:
Nice tutorial. I'm sure lots of people will find it helpfull when it's finished.
Click to expand...
Click to collapse
You keep giving me good ideas lol
excellent! going to utilize this
Can't wait for this to evolve. I have been looking for a good place to start.
very cool, looking forward to this!
Thanks. About time for me to get into this)
Sent from my PG86100 using XDA Premium App
Thank you very much for this noobs like me will learn a lot
I'm gonna reserve my weekend to go through this once complete.
Thanks for your time and effort for the tutorial in advance.
Been waiting for a "how to" tutorial on this specifically.
looking forward to it..
Thanks...
Thank You! This will be awesome! Can't wait till its finished!
Post #2 has been updated with a quick little starting off point for those of you who are anxious to begin while Freeza's tutorial is still under construction. I will attempt to help Freeza with his guide and help to answer questions within the thread. However, this guide is completely Freeza's. Any information that I provide that might conflict with or contradict anything in the guide should be disregarded until such time as I can edit my posts.
I see that this is under the "EVO 3D" Section, But this seems like a general rom guide. Will it extend later into how to put only onto a EVO 3D? Curiosity is all.
edit;
As previously stated, this guide is a work in progress and it is aimed at the EVO 3D, but the general concept is the same across all Android devices. Please leave your feedback and thoughts for the dev.
Click to expand...
Click to collapse
Ooops :|
Page Bookmarked ..
I am a Desire user and have been playing with ROMS for months adding stuff and changing stuff and i look forward to checking this out once its complete.
Very hectic day. HAven't forgotten about it. I'm working on the guide.
freeza said:
Very hectic day. HAven't forgotten about it. I'm working on the guide.
Click to expand...
Click to collapse
Thank You! looking forward to this!!!
Lol this is exactly how I learned... I've never used dsixda's kitchen, or any kitchen, in my life. Good guide man, I'm sure many will find this useful.
Hey it got featured!
lets dive into playing around with the framework-res.apk next!!!
gREAT JOB iM USING AUTOSIGN RIGHT NOW BUT WILL LOVE TO BE ABLE TO EXTRACT THE ROM AND REMOVE THE FILES THAT WILL BE JUST GREAT i HAVE TRIED TO EXTRACT ROM BUT COULDNT ZIP THE FILE BACK SO THAT IT COULD BE FLASHED

[GUIDE][MOD] Tuned MegaBassBeats for SGY (update-3/6/2012)

D3HuM4NiZ3D has made a post about "MegaBassBeats" in dev section. I don't want to make a kind of double post. from now on I'll made this post focused to explain on how it work and how to improve it. even if the tittle said that its for SGY it will work also on other Gingerbread based ROM. it tested on SGY, SG-Fit, SG-Mini, and SG-Gio. you can get all version for all my modified MegaBassBeat here. please check changelog for further details for every version.
v1.1
http://www.mediafire.com/download.php?gw2s475p1uwyby9
v1.2
http://www.mediafire.com/download.php?d2ftf4vdbai4hrq
v2.0
http://www.mediafire.com/download.php?fgc3kxdznmny7s8
v.2.0.1
http://www.mediafire.com/download.php?ei6xclihci8d3g9
v.2.1
http://www.mediafire.com/download.php?a1vxoqcd23mbzvb
btw, I've found something funny. if you find any mod called ultimate_multimedia_enhancement, it is actually same with my the one in this link.
Click to expand...
Click to collapse
this patch will install several files including two apk, a framework file, lib files, and some additional needed files in /system/etc/. this mod also include bravia engine mod. I've added the framework, the lib, and the xml file needed for bravia engine. for an addition from v1.2 I've also added dsp manager for best result. please delete your dsp manager if you already have one.
PS:
1. do it with your own risk
2. no need to thank nor press that button for me. I'm just a noob, give that for the original dev instead.
3. special credits for D3HuM4NiZ3D who has kindly given me the permission to modify his work. you can get the original link here. http://forum.xda-developers.com/showthread.php?t=1642961
HOW TO UNINSTALL IT
=================
Click to expand...
Click to collapse
well...no one can make a single mod which suitable for all kind of music. if you don't satisfy with this work, but too lazy to modify the setting as described in 2nd post you can follow these guide to uninstall this mod. it won't be easy and only can be done in a rooted device with root explorer installed.
1. extract megabassbeat zip file.
2. make a list of all files in that zip file
3. open your root explorer and delete these file
Code:
- in /system/app delete audioeffectservice.apk
- in /system/bin delete all files listed in megabassbeat
- in /system/etc delete all files listed in megabassbeat
- in /system/framework delete all files listed in megabassbeat
- in /system/lib delete all files listed in megabassbeat except libaudioeffect_jni.so and audio.so in /system/lib/bluez-plugin
4. delete this lines from build.prop file
Code:
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
5. reboot your device.
CHANGELOG
=========
v1.0
- initial release by D3HuM4NiZ3D
v1.1 (10-5-2012)
- my first release. minor change on sound configuration
v1.2 (12-5-2012)
- new sound configuration
- added DSP manager
v2.0 (27-5-2012)
- new sound configuration
- added missing files
- added more lib files
- added new framework file
- added new binary file
- new lib configuration for sound effect
v2.0.1 (30-5-2012)
- new apk added
- small configuration changed
v.2.1 (3-6-2012)
- new build.prop script added to activate xLoud
- new eqfilter configuration
- new sound configuration
- new lib added
Click to expand...
Click to collapse
basicly this mod is kind of improvement for old beats audio. beats audio have two different version. the newer one have b1.jar inside it. it has bad issue with several music player. the older one doesn't have b1.jar. MegaBassBeat combine xLoud mod+old beats audio to get more solid bass sound.
how it works?
it will install an apk and a framework and the lib needed to our rom. both of them works as enhancement for our audio system. they're using some files in /system/etc/ as their default setting. we can modify them as we like.
how to modify it?
at this time I can only change the setting for equalizer setting. if you didn't satisfy with the sound quality, you can modify it by yourself. go to /system/etc/audio. you'll find a lot of *txt files. those files contain all the value for audio setting. in this mod, you'll need to change the setting in eqfilter.txt.
the original setting was
Code:
A,1
B,1
C,1
D,15000
E,20
F,0
G,50
H,500
I,3000
J,4000
K,5500
L,96
M,150
N,96
O,400
P,600
Q,0
R,4
S,0
T,-4
U,5
I've changed the value to
Code:
A,7000
B,10000
C,10000
D,15000
E,20
F,0
G,50
H,500
I,2500
J,4000
K,5000
L,500
M,500
N,500
O,1000
P,1000
Q,0
R,4
S,0
T,4
U,5
the value from A to U is the equalizer setting. you can change the value from -15000 to 15000. please be carefull since any value you set in this file can affect on your sound quality so much. after modifying this file, you have to copy eqfilter.txt to /system/etc too.
btw, further modification to all files in /system/etc/audio is possible. however, I don't know the right value for the setting. the other file contain a lot of variable, make it difficult to understand. please contact me if someone know how to modify those files. I'll include them in my latest update.
reserved...lol
I'm planning to leave this project for a while. I'll give you all details modification I've done in the original work. beside adding more files into the original work. I've change the value in three files. if you extract my latest version, you'll see some files with *xxx1 extension. thats the original file comes from dehumanized. the one without '1' is my modified one. those three files are: eqfilter.txt, HP_audio.csv, and audio_effects.conf.
eqfilter editing is easy. you already can find the guide on 2nd post. this files comes from the xLoud mod. for the latest value you can check in my latest version.
HP_audio.csv contain the setting for beats audio. the original value is
Code:
ID,Value
TDAS_BUNDLE,
TDAS_VERSION,0,
TDAS_SAMPLERATE,1,
TDAS_IN_CHANS,2,
TDAS_IN_MATRIX,0,
TDAS_BYPASS,0,
TDAS_RATE_MULTIPLIER,0,
TDAS_IN_CHAN_FORMAT,0,
TDAS_DOWNMIX_CONFIG,0,
TDAS_OUT_CHANS,2,
TDAS_M2S,
M2S_ENABLE,1,
M2S_DETECTOR,1,
TDAS_SSH,
SSH_ENABLE,1,
SSH_MODE,3,
TDAS_SSE,
SSE_ENABLE,0, --> stereo effect. 1 for enable
SSE_WIDTH,0,
SSE_SPK_MODE,0,
TDAS_SLC,
SLC_ENABLE,1,
SLC_LEVEL,1,
SLC_DEPTH,0,
TDAS_VOL,
VOL_ENABLE,1,
VOL_GAIN_INTERNAL,0, --> you can change the setting. max10
VOL_GAIN_EXTERNAL,0, --> you can change the setting. max10
VOL_GAIN_TYPE,0,
VOL_BALANCE,0,
VOL_MUTE,0,
TDAS_NB,
NB_ENABLE,1,
NB_CUTOFF,5,
NB_BOOST,5,
NB_LEVEL,1,
TDAS_GEQ,
GEQ_ENABLE,1,
GEQ_NBANDS,6,
GEQ_PREAMP,0, --> you can change the setting
GEQ_MAXBOOST,24,
GEQ_BAND1,0, --> the equalizer setting. you can edit it. --> 5
GEQ_BAND2,0, --> 5
GEQ_BAND3,-4, -->4
GEQ_BAND4,0,
GEQ_BAND5,4, --> 0
GEQ_BAND6,4, --> 0
GEQ_BAND7,0,
TDAS_MUP,
MUP_ENABLE,0, --> 1
TDAS_MSR,
MSR_ENABLE,0, --> 1
TDAS_HFE,
HFE_ENABLE,1,
HFE_DEPTH,1,
TDAS_FADE,
FADE_ENABLE,0,
FADE_TARGET,0,
FADE_TIME,0,
audio_effects.conf contain the additional library setting and the setting. I'll only show you my edited part here since the file is quite long.
Code:
libraries {
bundle {
path /system/lib/soundfx/libbundlewrapper.so
}
reverb {
path /system/lib/soundfx/libreverbwrapper.so
}
visualizer {
path /system/lib/soundfx/libvisualizer.so
}
pre_processing {
path /system/lib/soundfx/libaudiopreprocessing.so
}
}
I add these lines to load the sound lib
SRS {
path /system/lib/libsrsfx.so
}
bass_enhancement {
path /system/lib/libbeatsbass.so
}
then for the effect setting, I added these lines
effects {
dynamic_bass_boost {
library SRS
uuid f7a247b0-1a7b-11e0-bb0d-2a30dfd72085
}
srsgeq5 {
library SRS
uuid f7a247c2-1a7b-11e0-bb0d-2a30dfd72085
}
wowhd {
library SRS
uuid f7a247d2-1a7b-11e0-bb0d-2a30dfd72085
I still can't understand the uuid stuffs. those lines are taken from beats audio.
all the additional files are taken from various sound tweak. there are about 5-7 sound enhancement used to improve this work. please don't ask me since I've mixed them and can't remember all of them.
reserved
[Reserved]
[Reserved]
I'll waiting tut.
did ya notice any sound improvements??
Sent from my GT-S5360 using XDA
I'm afraid all the tut are already included in my second post. modifying those file are not easy. I doubt if someone could find the correct variable and value for every files.
@hell_lock: just try it. it won't harm your device. this mod is work with all music player and any equalizer app. best result may come from poweramp music player + cm7 dsp manager.
Finnaly u released it
Good works brotha haha
Sent from my GT-S5360 using xda premium
any feedbacks so far? O_O
Pls provide the equivalent value(every numbrers) of what we are going to edit. Thanks!
davidroid03 said:
Pls provide the equivalent value(every numbrers) of what we are going to edit. Thanks!
Click to expand...
Click to collapse
all the value for eqfilter.txt is already in second post. I haven't touched any other files in /system/etc/audio
this mod works!?
if i install this mod, how about dsp manager will force close or not?
this mod will work with all music player and equalizer app including dsp manager.
Superb! My phone sound is better from before. Thankyou sir.
I think its working
post edited to avoid overlap. new update added. now including dsp manager inside it. from this moment. this thread will serve on what I've stated in 1st post.
is the bravia engine working??

[APK][Xposed] ResXploit : Theming your android the easiest way! No decompiling APKs!

This would be my second public-released xposed module...
(A duplicate thread is also posted in the Android Themes Section, so user who are only interested in themes can also see this)
I did not expect that my WisdomSky Xploit would be a big hit.
I'm just an Amateur developer who just started delving into android development 3months ago and I didn't expect that much appreciation from my work... XD
But all of these would not be made possible if not because of sir @rovo89 and sir @Tungstwenty and their Xposed Framework, right? That's why I thank them a lot...
REQUIREMENTS
Xposed framework must be pre-installed before installing this.
What does the ResXploit do?
ResXploit has two parts:
the Removable part, terminal
and the main star, engine
The terminal is where you enter the commands(I'll discuss it later). These commands will then be interpreted by the engine and then passed to Xposed framework...
Flow:
TERMINAL >> ENGINE >> XPOSED FRAMEWORK
I have provided a variety of modules:
ResXploit (Terminal + Engine) (RECOMMENDED FOR NEWBIES)
ResXploit Terminal (Terminal Only)(DEPRECATED)
ResXploit Engine (Engine Only)
You might be wondering why I made one which has both terminal and engine... and other two which are separated...
ROM Chefs, Themers and some others would understand directly why...
All the commands are interpreted by the Engine right? so that would mean that once you have entered all the desired commands, the terminal will now end up as useless... so you will just delete so no one can touch the engine...
If you are a ROM Chef or a themer, you can theme all the apps you need to theme using ResXploit and then remove the terminal, so end-user interaction of the engine is prevented after you have released your ROMs to the world.
FOR NEWBIES!
I recommend you to use the ResXploit (Terminal + Engine)...
It is very smart..
I included 99% accurate error-checking system,
line numbering system,
and also Xposed module prioritization(which is first implemented on ResXploit for better module performance).
COMMANDS
We have four basic commands in the ResXploit, the apk, drawable, string, and boolean.
apk - A prerequisite command. This command is very vital whenever you using the ResXploit. This will define the target application by using the package name of the target application. You need to include this before you enter any command or else your command will not know which application is targeted and end up in lost island.
Code:
[B]format[/B]: [I]apk <package name>[/I]
[B]example[/B]: apk com.android.systemui
drawable(also drw) - The most often used command. The command which will change icons/images (png drawables) of an application. You can either overlay the existing image with your favorite color or completely replaced it with a .png image from your sdcard.
Code:
[B]format1[/B]: [I]drawable <target application's drawable name> <image path, no need to include /sdcard> <transparency, 0 to 255>[/I]
[B]example1[/B]: drawable status_bar_background bg.png 255
[B]format2[/B]: [I]drawable <target application's drawable name> <HEX RGB color code> <transparency, 0 to 255>[/I]
[B]example2[/B]: drawable status_bar_background #fff00ff 255
string(also str) - This command will change string(text) values of the application. The predefined string values are usually located in res/values/strings.xml of an application, but I guess they are not visible when you view the contents of an application using Archive managers like RootExplorer. But there is a way to identify them. I will include it later.
Code:
[B]format[/B]: [I]string <target application's string value holder name> <replacement string>[/I]
[B]example[/B]: string app_name My App
boolean(also bln) - This command will change boolean values of the application. The predefined boolean values are usually located in res/values/bools.xml of an application, but I guess they are not visible when you view the contents of an application using Archive managers like RootExplorer as well.
Code:
[B]format[/B]: [I]boolean <target application's boolean value holder name> <replacement boolean value, either [B]true[/B] or [B]false[/B] only>[/I]
[B]example[/B]: boolean allowNumberNotifications true
Some simple examples screenshots:
drawable and string commands in action
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ResXploit UI screenshots:
If you find my ResXploit module interesting,
Please hit THANKS!!! XD:angel:
UPDATES & CHANGELOGS:
ResXploit Engine 1.0.8 - added support to framework-res(android).(latest)
ResXploit 1.0.8 - updated engine(1.0.8).(latest)
NOTICE: ResXploit is now an abandonware.
My flash drive where I stored the sources of my android projects was corrupted unexpectedly.
And also, my phone was broken. I have no device to use to re-write everything from scratch... Sorry...
Tutorial and samples
System Apps Package Names:
SystemUI - com.android.systemui
Settings - com.android.settings
Mms - com.android.mms
Contacts - com.android.contacts
Launcher - com.android.launcher
Gallery - com.android.gallery3d
File Explorer - com.android.qrdfileexplorer
Framework-res - android
Tip: If you want to find the package name of a specific application(not on the list), you can open Root Explorer(download it from googleplay) and then browse the apk you want to check, open it and choose "view". You can find AndroidMaifest.xml file inside. Open it then find the package="xxxxxxxxxxx". The words or group of words inside the quotations separated by a period is the package name of that application.
Note: ResXploit is far safer(in terms of error awareness) to use than the ResXploit terminal. If possible, only use ResXploit. In the simple tutorials below, please expect that I'm referring to ResXploit only.
Changing Statusbar background color
let's say color red...
Code:
#!/
apk com.android.systemui
drawable status_bar_background #ff0000 255
Changing Notifications Panel background color into transparent
Code:
#!/
apk com.android.systemui
drawable notification_panel_bg #000000 0
Changing Notifications Panel background with an image from sdcard
let's say that the png image is located in /sdcard/my_img.png
Code:
#!/
apk com.android.systemui
drawable notification_panel_bg my_img.png 255
You might be wondering where i'd get the target application's drawable filename?
Actually, you can just open the root explorer and view the files inside the apk of the target application. under the /res directory(folder), you can find a variety of subdirectories prefixed with [drawable, like drawable-hdpi,drawable-mdpi and so on... Basically, all images inside those folders are under the scope of drawable command in Resxploit. And if you want to target a certain image in the drawable folders, you just need to get the file name without the .png or .9.png. That's it!
Adding "comments"...
Comments in programming are human-readable additional information. If you want to put notes somewhere in your script, you can put "#" before your statement. When the terminal find a "#" before a statement, the terminal will ignore it and skip it. However if you will enter a non-command information and is not started withcl a "#", the terminal will ofcourse read it as command and then throws an error message.
Code:
#!/
# my comment. my comment. my comment
apk com.android.systemui
drawable status_bar_background #ff0000 255
# the terminal will skip the command below
# because it started with a "#"
#drawable oh_no #ff00ff 255
Defining working directory path of your images
If you want to start theming and you already have the images you want to use stored inside a single folder, then you can tell the terminal where these images are located so you don't need to enter the path redundantly.
You can define it on the very first line of ResXploit, after the "#!/" you can add the folder name or path to the folder.
let's say we have our images put in a folder in sdcard named my_images or /sdcard/my_images, then you can define it like this.
Code:
#!/my_images
#we can start theming now
drawable hello some_image.png 255
drawable world next_image.png 255
great work dude...noypi are very smart of course,,
Very interesting. I've been interested in theming for a while now but haven't gotten my feet wet. I'll be waiting for your tutorials. Great work mate!
Sent from my Galaxy Nexus
Nice! I love to see Pinoys In-Action with the XDA community!
Will wait for the tutorial of yours repa!
@greedisgood99999 Please stop that bad-habit of quoting... It's quite irritating tropa...
Wait for the tutorial
Sent from my Xperia Mini Pro
So ... a scriptable general purpose module. This is a phenomenal idea. OK still requires digging into the apk but a whole lot easier than building a new module from scratch.
Mission: Get rid of Armv7 calls the FC apps on my old clunker (also need help buying a new phone--if I had it, would have reserved the edge already!). Google Now first tries to init the "off line" voice recognition engine. Minimum, want to simply disable this call. I use overlays to prevent other such calls. Maximal, to replace with the old "on line" voice recognition engine.
Capability in this yet?
Among the booleans?
what say you
Dovidhalevi said:
So ... a scriptable general purpose module. This is a phenomenal idea. OK still requires digging into the apk but a whole lot easier than building a new module from scratch.
Mission: Get rid of Armv7 calls the FC apps on my old clunker (also need help buying a new phone--if I had it, would have reserved the edge already!). Google Now first tries to init the "off line" voice recognition engine. Minimum, want to simply disable this call. I use overlays to prevent other such calls. Maximal, to replace with the old "on line" voice recognition engine.
Capability in this yet?
Among the booleans?
what say you
Click to expand...
Click to collapse
i don'think so... because ResXploit's scope is only the res or resource directory of the apk structure...
if a boolean value is defined in the res/values/bools.xml that will actually toggle controls then it would be great... but i think, in your case it is deeply hard-coded to work like that...
Framework.res?
Can you theme the framework.res using this?
package name is only 'android' no com. or anything..
EDIT: Tried and it seems to go through ok, but nothing seems to change. Rebooted several times, changed an image in my keyboard, checked it was ticked in Xposed framework, setup a folder in my internal storage, checked superuser granted access, pressed high priority in settings. Don't know
Here's a debug log (uploading tomorrow, pc occupied)
Will this work for non system apps? The unlock button on the PowerAmp lock screen drives me insane because it's the only thing I can't change and I absolutely hate green.
Metallijim said:
Can you theme the framework.res using this?
package name is only 'android' no com. or anything..
EDIT: Tried and it seems to go through ok, but nothing seems to change. Rebooted several times, changed an image in my keyboard, checked it was ticked in Xposed framework, setup a folder in my internal storage, checked superuser granted access, pressed high priority in settings. Don't know
Here's a debug log (uploading tomorrow, pc occupied)
Click to expand...
Click to collapse
I'm so sorry for that...
in exposed, framework-res(android) uses different method...
so i forgot to implement it fo support the framework-res...
thanks for your feed back. I'll add it up and upload it later...
Rokonacdc said:
Will this work for non system apps? The unlock button on the PowerAmp lock screen drives me insane because it's the only thing I can't change and I absolutely hate green.
Click to expand...
Click to collapse
Ofcourse! it will work with non-system apps too... XD
This looks very promising, thank you for your work!!
here's a Debug
Here's my Debug log
Xperia Z 4.2.2, Images in internal storage, Xposed priority set low, all other xposed modules that I have installed disabled
Metallijim said:
Here's my Debug log
Xperia Z 4.2.2, Images in internal storage, Xposed priority set low, all other xposed modules that I have installed disabled
Click to expand...
Click to collapse
sir l've already added support for framework-res, please check the changelogs for the download link...
Interesting, sounds like a concept similar to Ninjamorph.
A couple of quick questions:
Is this able to apply folders or just single png's?
Also do you need extract png's from apks in order to apply or does it extract and apply automatically?
:good:
dully79 said:
Interesting, sounds like a concept similar to Ninjamorph.
A couple of quick questions:
Is this able to apply folders or just single png's?
Also do you need extract png's from apks in order to apply or does it extract and apply automatically?
:good:
Click to expand...
Click to collapse
Unlike ninja morph, in resxploit, there is no permanent replacing of resources happened... which means you can deactivate, share, edit easily anytime....
Q: Is this able to apply folders or just single png's?
A: only single pngs... 1 drawable command = 1 png... but there is no limitation on how how many commands you can add
Q: Also do you need extract png's from apks in order to apply or does it extract and apply automatically?
A: As what I've added on the title, "No decompiling APKs"... it means, no decompiling or extracting is involved in the process as what Xposed Framework aimed. You just need to put the image to replace inside your sdcard and just add a command to tell the engine "to replace that with this"... there is no permanent replacing of resources happened here... the image is just move into the /data partition and will be just overlapped to the target resource so there will be an impression of replacing of resources
I didnt mean does it decompile/extract full apks. I meant can you pull an resource/image out of the apk to apply.
I know it overlays instead of permanently overwriting the original resource, similar to Icon themer and XTheme engine.
Ninjamorph/ Metamorph unzips apks into folders so you can navigate through them and choose what you want to apply.
Example:
Choose target resource/image to change.
Choose apk to pull resource/image from.
Navigate and choose resource/image (extract if applicable) to apply.
This would be good if it also done the same. Although you could just unzip with an on board app like Zarchiver.
Basically it would make it a new and improved Ninjamorph/ Metamorph (dont tell Stericson i said that)
No offense, but looking at it from newbies point of view, it seems like a bit of a drawn out process if you were wanting to change numerous items.
I know it's early days and I'm sure this would be greatly improved with a GUI, if you decide to add one.
Personally speaking, i think this has massive potential and could be something very special. I applaud you, i wish i had your talent.#
Thanks.
I tried clicking on the changelog link, it gave an error "Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Not sure if its the file attached to the post that is the updated one or if the actual update got deleted. Please help me here
phanitej said:
I tried clicking on the changelog link, it gave an error "Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Not sure if its the file attached to the post that is the updated one or if the actual update got deleted. Please help me here
Click to expand...
Click to collapse
Oh sorry for that.. ill just upload it to a third party site and add the link...
thnx for reminding...
dully79 said:
I didnt mean does it decompile/extract full apks. I meant can you pull an resource/image out of the apk to apply.
I know it overlays instead of permanently overwriting the original resource, similar to Icon themer and XTheme engine.
Ninjamorph/ Metamorph unzips apks into folders so you can navigate through them and choose what you want to apply.
Example:
Choose target resource/image to change.
Choose apk to pull resource/image from.
Navigate and choose resource/image (extract if applicable) to apply.
This would be good if it also done the same. Although you could just unzip with an on board app like Zarchiver.
Basically it would make it a new and improved Ninjamorph/ Metamorph (dont tell Stericson i said that)
No offense, but looking at it from newbies point of view, it seems like a bit of a drawn out process if you were wanting to change numerous items.
I know it's early days and I'm sure this would be greatly improved with a GUI, if you decide to add one.
Personally speaking, i think this has massive potential and could be something very special. I applaud you, i wish i had your talent.#
Thanks.
Click to expand...
Click to collapse
thanks for the appreciation and to your suggestions...someone did suggest to me to add GUI...
I'm still a newbie in terms of androld... there's so much to learn first before I can fully implement whats on my mind...
My phone is also not that good for development... its so slow... XD
but if everything turns out good... then maybe I should reconsider...XD
WisdomSky said:
Oh sorry for that.. ill just upload it to a third party site and add the link...
thnx for reminding...
thanks for the appreciation and to your suggestions...someone did suggest to me to add GUI...
I'm still a newbie in terms of androld... there's so much to learn first before I can fully implement whats on my mind...
My phone is also not that good for development... its so slow... XD
but if everything turns out good... then maybe I should reconsider...XD
Click to expand...
Click to collapse
Which phone do you use?

RemixOS -- Overlay Apps, FAQ, Tips/Hints & Requests

Note: This is a Q/A thread please don't duplicate posts - upvote/comment on similar post
Root AccessBy default you have access to root via the root shell (ALT+F1 ALT+F7 to exit) using this root will give you access/control over some system related items but for proper root access and use of a su access manager (i.e. SuperSu) you need to 'manually' install a SuperSU.zip package that is normally installed via recovery - this process has been automated via RMXTools on Windows and a rootx.sh script on Linux.
Additionally the system is being 'forced' to remain ro (read-only) via the initrd.img - so an altered one is needed - the one provided here has just two ro's removed so the OTA mechanic is still in place.
System-less root
An alternative to the above this requires modifying ramdisk.img and includng a file in the data.img.
Required files can be obtained here: 64bit [32bit - will require it's own su.img and ramdisk.img]
Instructions -- download and replace the ramdisk.img (keep a copy of the original for OTA),
-- boot into RemixOS
-- download su.img
-- copy su.img to /data/su.img using ALT&F1 # i.e #cp /data/media/0/Download/su.img /data/su.img
-- reboot
Optional. If you also want rw access to /system files, then also download an replace the initrd.img ==> this will break OTA and will require replacing initrd.img and system.img with stock files for an OTA to complete.
Note. It is unknown what the consequence of rooting/modifying system.img will have on applying the implied upcoming regular OTA's OTA section follows​OTAOTA's as expected/hoped are patched updates, unfortunately they aren't individual file patches but are block patches, meaningthat for an OTA to complete you need to have stock unaltered system.img, ramdisk.img, kernel and initrd.img files - if you have altered any of these or potentially just mounted system as rw even once; an OTA will simply fail.
Verification Lets have a look at the OTA [64bit] updater-script
Code:
(range_sha1("/mnt/system.img", "2,0,1") == "12775f6b5137acc7d8a1dcc2f4a401d194ce7644") || abort("/mnt/system.img has been remounted R/W; reflash device to reenable OTA updates");
if range_sha1("/mnt/system.img", "2,0,655360") == "359e95683918ae74e3742dbf2c6e50ef20fb38e8" then
ui_print("Verified system image...");
else
(range_sha1("/mnt/system.img", "2,0,655360") == "177ef6310b9f9125f9d76e71da381d98d50dfb6d") ||
abort("system partition has unexpected contents");
endif;
apply_patch_check("/mnt/initrd.img", "2", "bb0e9d622986383dcdba757ed6602d4f39f878ff", "1ea2c462df3804af097cf6c9deb7a062af7a4659") || abort("\"/mnt/initrd.img\" has unexpected contents.");
apply_patch_check("/mnt/ramdisk.img", "2", "4a516fa61dc2ffabe03806aa768217cb7c713ea2", "b14ab6183073f0162c95f80ed8168f3462882fcb") || abort("\"/mnt/ramdisk.img\" has unexpected contents.");
apply_patch_check("/mnt/kernel", "2", "ffbd1a85f514f1c662b327733b96a63535b11a95", "9a4464cae128abb4b90148aa413d6035ef09b5af") || abort("\"/mnt/kernel\" has unexpected contents.");
# ---- start making changes here ----
ui_print("Patching system image after verification.");
show_progress(0.900000, 0);
block_image_update("/mnt/system.img", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
apply_patch("/mnt/initrd.img", "-",
1ea2c462df3804af097cf6c9deb7a062af7a4659, 1568778,
bb0e9d622986383dcdba757ed6602d4f39f878ff, package_extract_file("initrd.img.p"));
apply_patch("/mnt/ramdisk.img", "-",
b14ab6183073f0162c95f80ed8168f3462882fcb, 1153529,
4a516fa61dc2ffabe03806aa768217cb7c713ea2, package_extract_file("ramdisk.img.p"));
apply_patch("/mnt/kernel", "-",
9a4464cae128abb4b90148aa413d6035ef09b5af, 5041936,
ffbd1a85f514f1c662b327733b96a63535b11a95, package_extract_file("kernel.p"));
set_progress(1.000000);
From this we can see the 4 needed files as stated previously and the expected sha1 hash for these files:
Code:
[b]64bit 1503 OTA[/b]
ramdisk.img b14ab6183073f0162c95f80ed8168f3462882fcb
system.img 359e95683918ae74e3742dbf2c6e50ef20fb38e8
initrd.img 1ea2c462df3804af097cf6c9deb7a062af7a4659
kernel 9a4464cae128abb4b90148aa413d6035ef09b5af
Could someone with 32bit OTA post their sha1 values
In order to check these in Windows open a command prompt in the RemixOS folder and issue:
PowerShell
Get-FileHash -Path .\*.img -Algorithm sha1 > sha1.txt
Get-FileHash -Path .\kernel -Algorithm sha1 >> sha1.txt
Then read the resultant sha1.txt file​GAppsWithin the beta there are preinstalled 'disabled' gapps
#terminal (ALT+F1)
Code:
Original Credit goes to [url="https://www.reddit.com/r/RemixOS/comments/48puc4/gapps_are_preinstalled_but_hidden_heres_how_to/"]SubredditReddit[/url]
Follow the guide there - I would just be parroting it.
GUI (Via App) [unverified]
Freeze JideAppPolicy app
Unfreeze GoogleApps
Alternative: Those who kept their gapped installed data from Alpha to Beta may have noticed that gapps still worked with doing anything to 'enable' them ; thus it must be concluded that something in data is keeping them active - perhaps an update of GooglePlay(Services) has been installed in /data - in that vain could someone simply install a copy of PlayStore and/or GooglePlayServices obtained from apkmirror.com or via raccon​Overlay AppsOverlay apps like Tincore Keymapper and Twilight can't run properly by default due to them not having access to the Draw On Top permission - there are several reasons for this I guess; 1 being that with the multiwindow framework overlays are part of the integral part of the OS and third-party apps possibly misusing it could have unforseen consequences, and 2 it could simply be proper Android policy (the overlay was originally indented for just Warning/Error messages).
That being said; Tincore and Twilight have worked fine for me, but use at your own risk.
GUI (Via App)
Download App Ops from the Playstore (root required) - this one is tested and works as expected.
Once downloaded give it root access, install AppOps and reboot.
After reboot open the AppOps app, go to device tab, find the desired app and give it the Draw On Top permission.
#terminal (ALT+F1) [unverified]There is an appopps binary present in /system/bin (well a script for appopps.jar) - likely it's being used to disable this 'feature'
Code:
[b]---For Tincore Remapper ---
#appops set com.tincore.and.remapper SYSTEM_ALERT_WINDOW allow
--- For Twilight ---
#appops set com.urbandroid.lux SYSTEM_ALERT_WINDOW allow[/b]
Personally I wouldn't touch anything else in the AppOps app to reduce the risk of messing something up.
Note: if using a overlay layer like Twilight, buttons like those to grant SU permission will be unclickable until you disable/pause the overlay
Alternative [unverified]: the root App Ops app just needs root to install another app named App Ops to /system/priv-app as seen in the attached screenshot below - thus it should be possible to include this app via something like the rooting method from RMXTools without requiring full root to be installed. But it's untested ad I wouldn't be comfortable with posting a copy of that apk without the developers permission.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tablet ModeGUI (App/Root Browser)
/system/build.prop edit ro.remixos.box=true to ro.remixos.box=false
and while you are there you might as well edit
ro.no_wallpaper=true to ro.no_wallpaper=false
#terminal (ALT+F1) [unverified]
Code:
[b]#sed -i -e 's/ro.remixos.box=true/ro.remixos.box=false/g' /system/build.prop[/b]
[b]#sed -i -e 's/ro.no_wallpaper=true/ro.no_wallpaper=false/g' /system/build.prop[/b]
Screenshot
LauncherIn RemixOS the default desktop is essentially (like Windows) an expanded file browser window (com.jide.filemanager); enabling tablet mode (/disabling box mode) as above and exposing additional Experimental Features (multitap kernel version in Settings => About) allows you to disable the file based browser and use the other; technically stock launcher (com.android.launcher3); this is a minimal launcher without widget support and without an app drawer.
Third-party launchersDownload your 3rd party app of choice (Nova/Apex seem to be working 'fine')
GUI (Via App)
freeze My Home and Launcher
#terminal (ALT+F1)
Code:
[b]#pm disable com.android.launcher3
#pm disable com.jide.filelauncher[/b]
Press the Home (circle) button. Once launcher is set-up make sure it is set to run in full-screen mode i.e. Settings=>App=>Nova=>Restart in FullScreen Mode​ Credit to rafial who mentioned a similar procedure with launcher3 for Remix1.0
Screenshots
PhoenixOS
In PhoenixOS there is a similar filemanager/launcher3 setup but launcher3 is an 'empty' app and additionally 3rd party launchers are actively blocked from being installed, so until the location of this block is found 3rd party launchers won't work
​(Auto-)RotationDue to the number of different accelerometer/gyroscope sensors there are numerous different ways that sensors reading can be processed; and currently Ax86 doesn't read from a property value to rearrange the sensor readings - thus if you 'enable' autorotation (disable the forced landscape), results may vary by device - i.e. screen/accelerometer may be misaligned (90/180/270 degrees).
To enable autoration - in addition to the build.prop edits for 'Tablet Mode' above; enable additional Experimental Features by multitapping on Kernel version info - then disabling Forced landscape and file based launcher
Screenshots
Disabling InputsProcedure listed here​AppsIf an app isn't working correctly or instantly crashes there's 2 options to try before writting it off:
1. Open the app fullscreen mode
2. If available use a different set of libs; this is done using pm install -r --abi * *.apk
I have also a simple script here it's run like applib sonic for a sonic app, then follow onscreen directions (add this to /system/bin as well)​Build Prop tweaks
Apart from the Tablet mode edits mentioned above:
​RequestsIf there's something that works in Androidx86 but not in RemixOS then please request it here and I'll take a look​
Added #terminal (ALT+F1) method for AppOps -- this should work for stock (unrooted) system
Actually tincore is showing up the overley, but it was not touching the target instead it was touching the mouse pointer location. Do u successfully ran tincore without any hiccups
Yes I get the same problem as krishrocks, any solutions? TY.
Tincore isn't something I'm used to using; could it be a fullsceen or calibration issue.
Can either of you post a couple screenshots perhaps; as an answer rather than a comment and describe what should happen, and what actually does.
i set ro.no_wallpaper to false, remix os taskbar is missing.
how to fix?
Which launcher are you using?
Only reason for tasbar would be if it's set to autohide, or something is messing with SystemUI
when i would like install third party launcher, i use terminal with command
#pm disable com.android.launcher3
#pm disable com.jide.filemanager
is disable launcher an filemanager, but when run nova, i have message no support third party launcher....
I no longer got that message after disabling both apps,
If it's causing nova not to launch, try pressing the circle button and ticking the box to make it default first.
It could be that you also need ro.remixos.box=false but not sure
yes my remixos.box is false
nova work. i use titanium backup fot freeze launcher and filemanager
i am using nova launcher, maybe build.prop no wallpapaer true is meant to remix os cause if set to false then the taskbar will missing
edit:
sory u right, if set taskbar to autohide and buildprop no_wallpapaer to false tasbar is missing but i set taskbar to "not autohide" no_wallpaper to false tasbar is back, tyty
I think I had the wrong package listed for the #pm disable; try the above again.
@arts821 try the same - com.jide.filelauncher instead of filemanager.
screenshot of nova here: http://imgur.com/EDW6lOu - so it appears fine for me (I was using Apex previously so I had to disable that as well).
I managed to run Nova Launcher on Phoenix OS:
https://www.reddit.com/r/PhoenixOS/comments/4a67tm/chilling_with_nova_launcher/
Screenshot:
http://i.imgur.com/WfvGPaz.png
Any more details?
Nova was blocked from being installed for me (could see in logcat that it was a banned install or something).
Tablet mode on Phoenix is just launch each app fullscreen, if anyone is wondering; took me a while to realise that.
Just re-read your reddit post, I take it you manually installed an apk; rather than using the playstore --- if so that sould make sense to me.
Regnas said:
I managed to run Nova Launcher on Phoenix OS:
https://www.reddit.com/r/PhoenixOS/comments/4a67tm/chilling_with_nova_launcher/
Screenshot:
http://i.imgur.com/WfvGPaz.png
Click to expand...
Click to collapse
Yeah, I installed manually, and I thought it could work with Play Store too, but as you tested, it didn't...
Anyway, Nova is running pretty smooth on my Phoenix.. I also installed Apex and it's running great too, even the widgets are showing up in the app drawer (unlike Nova)..
I tried Arrow Launcher as well, it's working but the icons are a little bit small..
Aviate is not fully working at moment...
Cheers..
Thanks for the confirmation, not quite sure if that helps identify where the blacklist is.
I was going to try and replace packageinstaller... Or figured it might be one of the certificates in Settings.apk (perhaps the stock Android feature for buisness where apps are restricted).
PlayStore isn't included stock right? Pretty sure I manually gapp'ed...
Yep, there's no Play Store built-in... I installed gapps manually as well...
I'm waiting for the results of your tests..
Systemless root [64bit] and OTA section added
Some way to deactivate touch pad would be helpful.
It will be a while before I can check/test but you should be able to disable specific inputs via a file in /system/etc; using #getevent to find the right device name. Do you mind reposting your comment as as Answer instead so it gets it's own string
Edit. it's the /system/etc/excluded-input-devices.xml file

[Mini-Howto] Layers Management via Init.d script

Like many of you, I like to keep my Android system rootless and true to stock as much as possible. However, I like to be able to enjoy the native support of layers for better look n feel. I wrote the script attached to help me with it however, it doesn't come easy without root access. There are some work cut out for you, read below.
Prerequisites:
Have extracted theme from layers theme app from Play Store. No, I'm not talking about the main theme app which is used by Layers Manager. Rather, it's the apks that go into the /vendor/overlay. I tried to extract respective apks out of the main one without using Layers Manager. However, my attempts yielded no success as I'm getting FCs all over, so I must be missing something. I current have a Nexus 9 which is rooted with Layers Manager, I use N9 for testing out and bring the /vendor/overlay/*.apk onto my N6P under /sdcard for my script to process. If you know of a better way, by all means share.
Of course, kernel which support INIT.D.
TWRP installed for root access via recovery, a MUST.
Busybox installed via flashable zip
Install:
- Download the script attached
- Rename .txt to .sh
- Have all extracted themed apks in one directory. For instance, I like fa and art layers, so my directory on sdcard as such /sdcard/0flash/layers/fa/fa_*.apk
- Change up the first few lines to match your environment
- Boot into twrp, mount /system if needed
- Drop the script into /system/etc/init.d
- chmod 755 /system/etc/init.d/01layersmanager.sh
- Create a file named ".current_theme" in /sdcard/
- In the above file (.current_theme), put the name of theme you want init.d to install. Example, if I want to install "fa" then I'll just have a line of text fa in it (same goes to art, coalesce,etc). IMPORTANT: no trailing new line.
- Reboot and test it out
- If theme successfully installed, you'll see it.
- Also, the /sdcard/.current_theme file will be updated with "current" to avoid theme installation on next reboot if you don't want to install new themes.
Troubleshoot:
See /sdcard/debug.txt for info. If you want additional information dumped, edit the init.d script to echo out more.
O bio hnki
vboyz103 said:
Like many of you, I like to keep my Android system rootless and true to stock as much as possible. However, I like to be able to enjoy the native support of layers for better look n feel. I wrote the script attached to help me with it however, it doesn't come easy without root access. There are some work cut out for you, read below.
Prerequisites:
Have extracted theme from layers theme app from Play Store. No, I'm not talking about the main theme app which is used by Layers Manager. Rather, it's the apks that go into the /vendor/overlay. I tried to extract respective apks out of the main one without using Layers Manager. However, my attempts yielded no success as I'm getting FCs all over, so I must be missing something. I current have a Nexus 9 which is rooted with Layers Manager, I use N9 for testing out and bring the /vendor/overlay/*.apk onto my N6P under /sdcard for my script to process. If you know of a better way, by all means share.
Of course, kernel which support INIT.D.
TWRP installed for root access via recovery, a MUST.
Busybox installed via flashable zip
Install:
- Download the script attached
- Rename .txt to .sh
- Have all extracted themed apks in one directory. For instance, I like fa and art layers, so my directory on sdcard as such /sdcard/0flash/layers/fa/fa_*.apk
- Change up the first few lines to match your environment
- Boot into twrp, mount /system if needed
- Drop the script into /system/etc/init.d
- chmod 755 /system/etc/init.d/01layersmanager.sh
- Create a file named ".current_theme" in /sdcard/
- In the above file (.current_theme), put the name of theme you want init.d to install. Example, if I want to install "fa" then I'll just have a line of text fa in it (same goes to art, coalesce,etc). IMPORTANT: no trailing new line.
- Reboot and test it out
- If theme successfully installed, you'll see it.
- Also, the /sdcard/.current_theme file will be updated with "current" to avoid theme installation on next reboot if you don't want to install new themes.
Troubleshoot:
See /sdcard/debug.txt for info. If you want additional information dumped, edit the init.d script to echo out more.
Click to expand...
Click to collapse
Yt? Bird :
Sent from my Nexus 6P using XDA-Developers mobile app

Categories

Resources