Database Users

[HOWTO] Guide to themeing on Android - from one noob to another.

Hello all. I have been using the various android builds for the past few weeks, and much respect to all the developers.
I have been unable to find a central guide how to apply themes on our HD2 android. However, through some trial and error, I have been able finally apply a theme in a relatively straightforward way, without using terminal or coding or whatnot.
Note, this was a themeing attempt on a cyanogenmod build (there are several out there).
Please feel free to add-on or modify or share your comments. Let's help each other enjoy our phones!
------------------------------------
You need to have AndroidSDK installed, as well as droid explorer. Make sure adb process is running; I believe when you install androidsdk, this will start automatically.
Fire up your android build, and connect via usb to your computer.
Run droid explorer, and your list of directories should show up. Now, open the folder of your dark cherry theme. In the "framework" folder you should see framework-res.apk. Drag this file into droid explorer under /system/framework on your android. This will change the theme, and you need to reboot (from the phone, not from droid explorer).
If you want the keyboard and other apps skinned, you can copy the .apk files from the app folder (in your dark cherry folder), and drag them to /system/apps on your android (via droid explorer). Now reboot again (from phone, not from droid explorer).
This is what worked for me 99%. The only issues I noticed was that zedge would keep asking me to upgrade whenever i rebooted. Minor issue really, but otherwise, the theme worked fine, as did the keyboard and all.
* Remember, when you download the theme from the website, make sure it is compatible with your cyanogen build. I was using bangster's build, based of cyanogen 6.0.1. So on the theme website, I downloaded the build under nexus one cyanogen 6.0.1.
Hope this helps, and good luck.
-----------------
I found androidSDK on the web, and there are also web guides on how to install. I am using Windows 7 64-bit on my laptop. My phone had vbn's clarity rc1 droid rom. My android build was bangster's 1.3.

Thanks for the guide maqsur,
but a couple of questions:
Could you please link the site where you got the themes from?
Does it have to be 6.0.1, because I only see 6.0.0 themes for nexus one :S (http://forum.cyanogenmod.com/topic/5977-theme-full-desire-cyanogenmod-600-final-90210-fixed/)

The dark cherry theme that is in the "screenshot" thread is from a site by its creator, and it had a link to 6.0.1. I am also using google to search for "cm6 final themes." I just downloaded a "Black and Bold" theme from droid forums. It's all experimentation at this point, because dark cherry was the first one i ever tried.
I believe most of the newer builds for our HD2 are based on cyanogenmod final 6 (cm6). So I believe if you look for themes like that, you should be okay. I am still trying new ones, and will post screen shots when I can take them.

A note: depending on your build, read the original post for that particular thread, and confirm which rom the cyanogen is based on (nexus one, evo, etc.), because themes that are out there are based on phone models as well as mod versions.

[Q] How To Create A Theme.apk

Hi All
I have the most recent version of Oxygen which includes a "theme picker" app.
Similar to the one found in the HD ROM's it gives the opportunity to change the entire system theme, without flashing a zip. Which is good news
However, I have been trawling the internet trying to figure out how to create the .apk needed to create my own themes, failing miserably.
Could someone with the required knowledge post a tutorial maybe? Or a link to where the info is so that I can do my own research?
Thanks

i've not installed the test rom so cant check, but does it come with any theme.apk's pre-installed?
if so i'd start by pulling them apart and looking at the .xml and images and change them from there.

str355 said:
i've not installed the test rom so cant check, but does it come with any theme.apk's pre-installed?
if so i'd start by pulling them apart and looking at the .xml and images and change them from there.
Click to expand...
Click to collapse
Do you know I didn't even think of that
I shall do so and see what I can come up with

Well I downloaded the Android SDK and all the tools required, then I installed eclipse and started a tutorial on how to build an app - as I assumed this is what I will need to do... but then my brain started to hurt and I needed sleep!

LG G2 F320S Camera Shutter Sound & Info About Camera Workings

About two months ago I purchased an LG G2 F320S which is really good, except for one thing that's really annoying me: because it's a Korean variant, I'm unable to silence the camera when taking a picture.
I've rooted my phone and tried installing LGCamera.apk from: http://forum.xda-developers.com/showthread.php?t=2670972
Given the poster of the apps seems to have the D802 variant, which I believe gives you the option of silencing the camera when taking a picture, I would have expected that installing this APK to provide me the same option. However, after placing the APK and ODEX files in the priv-app directory and restarting, my camera still has no option to silence it (the same 4 shutter sound options).
I have seen some flashable camera packages posted on here which also contain native libraries, but I don't see how these help because the sound files are contained in the APK (also, I don't have a custom recovery flashed as I nearly bricked the phone permanently the last time I tried - had even managed to mess up download mode). I've previously unzipped the APK and tried to remove or change the sound files, but it looks like the resources are signed in some manifest file so that changing them isn't possible without going through the process of creating a signed package (and I would assume you'd need LG's private key in order to achieve that, rather than being allowed to sign your own). What does flashing the C/C++ native libraries give you?
The most annoying thing is that the shutter sound wouldn't even stop a determined perve, as there are camera apps in the Play Store which just save the screen preview (ie full HD image, in the case of the G2) as a photo without making a sound, so the whole thing is just pointless and annoying.
Can anyone provide me with information or pointers to information on how to get rid of the stupid shutter sound on the F320S variant while being able to take 13 megapixel pictures? I am a C# developer and am not a complete stranger to Linux or Java, so feel free to be technical. Even just some information on why my bundled camera APK will install, but others won't (though some will when you restart the device after placing them in the priv-app folder when the phone does an 'installing update' thing) would be useful to know.
Thanks in advance!

Ascy said:
About two months ago I purchased an LG G2 F320S which is really good, except for one thing that's really annoying me: because it's a Korean variant, I'm unable to silence the camera when taking a picture.
I've rooted my phone and tried installing LGCamera.apk from: http://forum.xda-developers.com/showthread.php?t=2670972
Given the poster of the apps seems to have the D802 variant, which I believe gives you the option of silencing the camera when taking a picture, I would have expected that installing this APK to provide me the same option. However, after placing the APK and ODEX files in the priv-app directory and restarting, my camera still has no option to silence it (the same 4 shutter sound options).
I have seen some flashable camera packages posted on here which also contain native libraries, but I don't see how these help because the sound files are contained in the APK (also, I don't have a custom recovery flashed as I nearly bricked the phone permanently the last time I tried - had even managed to mess up download mode). I've previously unzipped the APK and tried to remove or change the sound files, but it looks like the resources are signed in some manifest file so that changing them isn't possible without going through the process of creating a signed package (and I would assume you'd need LG's private key in order to achieve that, rather than being allowed to sign your own). What does flashing the C/C++ native libraries give you?
The most annoying thing is that the shutter sound wouldn't even stop a determined perve, as there are camera apps in the Play Store which just save the screen preview (ie full HD image, in the case of the G2) as a photo without making a sound, so the whole thing is just pointless and annoying.
Can anyone provide me with information or pointers to information on how to get rid of the stupid shutter sound on the F320S variant while being able to take 13 megapixel pictures? I am a C# developer and am not a complete stranger to Linux or Java, so feel free to be technical. Even just some information on why my bundled camera APK will install, but others won't (though some will when you restart the device after placing them in the priv-app folder when the phone does an 'installing update' thing) would be useful to know.
Thanks in advance!
Click to expand...
Click to collapse
I have a UK EE LG G2 and I can assure you that that trying to silence the camera click doe NOT work! By all accounts you need to 'root' the phone and delete 'cameraclick.ogg' (which I believe is only accessible when in root (which you appear to have?)
.
Michael

A Bit of an off-topic thing, but i am facing the same problem on my Lg g3 as well.
Removing the camera_click.ogg from the system>media>audio>ui folder does not do the trick.
The actual LGCamera.apk will need to be decompiled and the audio file contained in the res>raw folder will need to be replaced with a silent one.
However i do not know the exact procedure to recompile and re-sign the apk again

nisargz said:
A Bit of an off-topic thing, but i am facing the same problem on my Lg g3 as well.
Removing the camera_click.ogg from the system>media>audio>ui folder does not do the trick.
The actual LGCamera.apk will need to be decompiled and the audio file contained in the res>raw folder will need to be replaced with a silent one.
However i do not know the exact procedure to recompile and re-sign the apk again
Click to expand...
Click to collapse
Exactly the issue, so I've given up on it. In fact, I removed root entirely (not an easy job) as it was preventing updates.
I had tried replacing the sound files in the camera app, but the package needs to be signed. I would assume that just signing the package isn't enough, but that it would need to be signed by an LG authorised key for it to be recognised.

Ascy said:
Exactly the issue, so I've given up on it.
Click to expand...
Click to collapse
Just to let you know the new G3 Tweakbox Xposed Module works like a charm and silences all the annoying camera sounds. Time to root again I guess lol

Google Assistant on any Android Phone

This giude was made as i found a method to enable google assistant in your phone..
Requirements:-
A phone with custom recovery
Three files provided below
Android 7.0 or higher (as for now)
All google apps must be either force closed or uninstalled before flashing the files
For this,you have to download the 3 files from this MOD EDIT: REMOVED.
->After downloading puth these files in your phones storage.
->Then,Reboot into recovery..
-> In recovery mode you will not be able to see the third file(tweak.prop)
First,flash GoogleAssistantVelvet.zip
Then,flash GoogleAssistantBuildProp
->After installing Wipe Cache
You Are done..Enjoy The new Google Assistant in your phone,,
F.A.Q
Supported languages by Assistant?
-> English and German as for now.
Will I get OTA Updates?
->Nope,As phones build.prop will be changed to PIXEl
Will it work on Marshmallow??
->i dont know,But i found this thread..You can try and tell me.. Visit this thread.
Working Devices
Almost all Phones.. Tested on Arm64(Redmi Note 3) Arm(Moto X2) x86(zenfone2)..All working fine..
Good Luck:highfive:
Tell Me if i helped...

Who created these files, where are they from? Are these for 32bit or 64bit? I am not sure I would call this a guide. How about some additional information, like what device you have a working version running on. Also, brief as it may have been, upon a little looking around it would appear there is not a one-size-fits-all solution as different devices require different parts of certain apk's. Have you resolved this?
Are all functions of assistant working?
Is OK Google working?
Not tryingto come off harsh, but this seems off somehow. Maybe I shouldn't have looked at your "How to build a custom ROM beginners guide", not exactly building a ROM, more like a coloring book, everything is already there you just slip a picture into the back and now it's 'Your Custom coloring book".

StevetotheH said:
Who created these files, where are they from? Are these for 32bit or 64bit? I am not sure I would call this a guide. How about some additional information, like what device you have a working version running on. Also, brief as it may have been, upon a little looking around it would appear there is not a one-size-fits-all solution as different devices require different parts of certain apk's. Have you resolved this?
Are all functions of assistant working?
Is OK Google working?
Not tryingto come off harsh, but this seems off somehow. Maybe I shouldn't have looked at your "How to build a custom ROM beginners guide", not exactly building a ROM, more like a coloring book, everything is already there you just slip a picture into the back and now it's 'Your Custom coloring book".
Click to expand...
Click to collapse
yeah sure,iwill

Thread closed as this is a copy of this guide: http://forum.xda-developers.com/showpost.php?p=69074667&postcount=112"
The Flash
Forum Moderator

Porting Dolby 2.5 from Leaked Android 8 beta?

So for a while I've been trying to port Dolby Atmos 2.5 but to no avail. I tried using the Dolby Atmos Axon 7 magisk module as a reference to which libs and other files it may depend on, but it seems that there are different files, removed, possibly changed and added.
I've listed below the lib/dependency files and folders in the magisk module and the known Dolby atmos files from the system.raw image of the leaked build
These are the ones in the magisk module zip
/system/etc/media_codecs_dolby.xml
/system/etc/dolby/dax-default.xml
/system/lib/soundfx/libhwdax.so
/system/lib/soundfx/libswdax.so
/system/lib/libdlbdapstorage.so
/system/lib/libdlbmemoryservice.so
/system/lib/libhwdaphal.so
/system/lib/libstagefright_soft_ddpdec.so
/system/lib64/libhwdaphal.so
And now these are the ones that I have found in the system.raw image of the leaked Oreo ROM. I assumed the ones named "libdlb*" are ones used by Dolby so I included those, along with lib files that are similar to the old ones just incase.
/system/etc/dolby/dax-default.xml
/system/lib/soundfx/libswdap.so
/system/lib/soundfx/libswvlldp.so
/system/lib/libdlbdapstorage.so
/system/lib/libdlbdsservice.so
/system/lib/libdlbmemoryservice.so
/system/lib/libdlbnativeservice.so
The ones in red are the new libs that could be related to dolby that I've found. And as you can see, some of them are gone or changed such as /system/etc/media_codecs_dolby.xml and the lib files in /system/lib/soundfx/
Upon flashing these new files, the dolby app crashes. Logcat says this: https://i.imgur.com/ClcqbVr.png
I'm not developer guys but I am good at piecing things together. If there was a simpler way this could be done we could figure it out easily. Maybe some libs were added, removed, or modified for the Magisk Module to be compatible with ahrion's AML. I have uploaded a flashable zip that I created using Nikhil's Android Flashable Zip Creator which you can download right here. Make a backup, of course,
before flashing this. This is all being tested on the Project New World Oreo ROM by OrdenKrieger

I'm running the latest 8.1.0 Project World ROM and I'm reporting back with some force closing if the Dolby Atmos application. I can't seem to launch the app at all due to this. Thanks for trying to make this work, I appreciate it. ?

troy5890 said:
I'm running the latest 8.1.0 Project World ROM and I'm reporting back with some force closing if the Dolby Atmos application. I can't seem to launch the app at all due to this. Thanks for trying to make this work, I appreciate it.
Click to expand...
Click to collapse
Well if you noticed, the app does hang a little bit before crashing as it tries to load everything. But it seems when it can't load the audio effects it crashes. I don't know if it's related to audio_effects.conf or something

Teet1 said:
Well if you noticed, the app does hang a little bit before crashing as it tries to load everything. But it seems when it can't load the audio effects it crashes. I don't know if it's related to audio_effects.conf or something
Click to expand...
Click to collapse
I've noticed it do that when I try to launch it. My guess is that it has something to do with the audio_effects.conf

I uploaded the /system/ folder of the leaked ROM as a zip if anyone feels bold enough to try. Download here

Teet1 said:
I uploaded the /system/ folder of the leaked ROM as a zip if anyone feels bold enough to try. Download here
Click to expand...
Click to collapse
Why don't we ask the magisk module guys.
@ahrion and @Zackptg5 Is there a port of the Oreo Atmos version under way? Teet1 couldn't make it work by just taking the libs it seems

Choose an username... said:
Why don't we ask the magisk module guys.
@ahrion and @Zackptg5 Is there a port of the Oreo Atmos version under way? Teet1 couldn't make it work by just taking the libs it seems
Click to expand...
Click to collapse
I hope they are working on it....but I am certain the magisk module version was modified to work with their audio modification library. Perhaps I can try messing with that, but I probably can't share it if its their code
EDIT: so...after looking through the system image, I have found most of those missing files inside the /system/vendor/ folder...and just occured to me that a lot of the magisk patching occurs in the /system/vendor/ folder. Looking into it....
edit again: oh yes, I think I hav efigured out the problem. Now to test... https://i.imgur.com/ZfcGGka.png

Okay, so I'm making some progress. After copying from libs and other files from /system/vender/ it seems that the dolby service starts to work but still stops working. Ultimately, in the logs it ends in "dolby service not found". Also noticed a new error, the app crashes with an error saying "AudioEffect: set/get parameter error"
The app opens briefly, and hangs and then crashes. Attempting to play music pauses it for a while, then starts. Opening the dolby app while music plays pauses the music and then continues again. I copied a lot of audio files and "mixer pathes" files. If you take a look at my logcat, it seems as if I made the speakers work as they should as if it was in the stock rom! Maybe...they don't distort at high levels anymore and it's much clearer and louder. I can't get proper logs right now as I'm about to go to sleep and on my phone so i'll upload quick screenshots
I may still be missing some files, but who knows.
I am getting close. I've uploaded a link to the new zip here
Be warned, make a backup before flashing this. It's to test only, it doesn't work.
Here are some quick screenshots:
https://imgur.com/a/YQyKM

Have you had any progress?

chrisrodsa210 said:
Have you had any progress?
Click to expand...
Click to collapse
Nope, stumped now. I moved a lib/lib64 file called libaudioeffect_jni.so and that caused the app to instantly crash with a new error, which unfortunately I can't remember. The behavior was the same where the music took a couple seconds to start playing and then starts playing and opening the dolby app causes the music to pause for a bit. I took a look at that lib file and saw there were other audio libs it asks for so I moved those, which lead the phone into a bootloop. I assume that the service wants to work but can't call the audio effects for some reason. I'm not a developer, so I don't know what else I can do

Hello,
Here is a OnePlus 5 port of our Oreo Dolby. Maybe you can find the necessary files there. The current version of that thread works with OP5 but sadly didn't work with the first Project New World build, maybe the newest build works with this? Looking forward to this
https://forum.xda-developers.com/oneplus-5/themes/app-dolby-atmos-axon-7-oreo-port-t3734040

mariusfl0rian said:
Hello,
Here is a OnePlus 5 port of our Oreo Dolby. Maybe you can find the necessary files there. The current version of that thread works with OP5 but sadly didn't work with the first Project New World build, maybe the newest build works with this? Looking forward to this
https://forum.xda-developers.com/oneplus-5/themes/app-dolby-atmos-axon-7-oreo-port-t3734040
Click to expand...
Click to collapse
I'll definitely test this with the latest Project World and report back
---------- Post added at 09:07 PM ---------- Previous post was at 08:44 PM ----------
troy5890 said:
I'll definitely test this with the latest Project World and report back
Click to expand...
Click to collapse
EDIT: Tested the zip out and it didn't install on twrp. It just kept going and didn't install. Had to do a Hard Reboot.

getting the same issue where it doesn't install. I could try to use the files it moves, but theres a lot of scripts of setting permissions, writing things, etc and i feel like thats so much more complicated than just moving files it needs. I'm more hopeful of that zip than with mine.