Related
To create themes, or to edit themes to your liking, you will need a working knowledge of android, adb, how to resign apk's, knowledge of your own O/S.
Before you start be aware that you will may end up wiping your phone once, if not more. So lets go over the things that you will need.
You will need JF's RC30, RC8, or ADP1 V1.3, depending on what version you intend to create for.
Here is the link to these: http://forum.xda-developers.com/showthread.php?t=466174
You will also want to get the dev bootloader installed on your phone and to HIGHLY suggest everyone trying your theme to install it as well.
Link to dev bootloader: http://forum.xda-developers.com/showthread.php?t=455860
You will also need to resign all the apks located in /system/app and framework-res.apk located in /system/framework. When you push all of these to your phone.
JesusFreke was kind enough to build a custom signing tool for me that would allow me to right click on an apk and resign it from there. I am posting it here for others to use as well. Note that this is a courtesy of JF, so thank him for it. I cannot stress how much time this has saved me and will save you.
Here is the link: Http://www.FightForthePits.com/testsign(2).zip
Before using this you need to know how to set this up:
I will assume that you have the sdk downloaded and extracted somewhere(if not, do that now), extract both files to the tools directory of your sdk.
Now you will need to add the tools dir of your sdk to the environment variable CLASSPATH.(This is for XP, Vista coming soon)
To do this, right click on My Computer click properties, then choose the tab that says advanced. Click the button that says environmental variables. Go to system variables find the one that says CLASSPATH, double click it, go to the end of variable value. There should be a semicolon ; at the end. type in the path to the testsign.jar located in the tools directory of your SDK, for example the path to my testsign.jar was c:\sdk\android-sdk-windows-1.0_r1\tools\testsign.jar If CLASSPATH is not in your system variables then create it. Secondly, Find the system variable called PATH and add to the end of it, the full path to your sdk directory. For example, mine was c:\sdk\android-sdk-windows-1.0_r2\tools
Now right click the reg file that you extracted and choose to install it, or merge.
Now, right click an apk, do you see an option that says ResignApk? That's how you will resign your .apks and .zips.
If you find the right click menu not working for some reason you can type the following in cmd to sign your files: java testsign whateverfiletosign
Now through doing this you have done two things, first off you have made the resigning process extremely easy, secondly you will not have to cd to the tools dir of the sdk to use adb or any other tool in the sdk.
You will also need a version of linux installed or running vmware with linux, if you want to create, or edit, an update script, which will install the theme onto the users phone.
You will need to be specific in addressing what version your theme is for, RC8, RC30, or ADP1. Make sure every file gets signed. Make sure you test the update.zip before you release it.
Every .apk contains the images relating to itself. However, every apk has the ability to use the images in framework-res.apk. The images for every apk is located inside of itself. To find these images open up the apk, you can rename it to .zip or open it with an archiver of your choice, winrar, winace, etc. Then after opening the apk open the folder called res and inside of that there are folders that are named Drawable, drawable-land, drawable-port, etc. This is where the images are stored.
Ther are some things you cannot edit unless you rebuild the entire apk from source, which we will not go into here.(another tutorial, another time) Just know that at this time you SHOULD NOT edit, or even open images with the extension .9.png. If you do you will have problems...Trust me. These are special images called ninepatch images and android resizes these images to fit wherever android, or any other apk, needs it to. if you do open them or edit them they will no longer render correctly when resized. I believe that in order to edit these you must do so and then put them into the source and rebuild the entire apk.
Before getting started you must also realize that you cannot simply resign one or two apk's and stick them in your phone and expect them to work. You must resign every apk inside of /system/app and framework-res.apk and put them on your phone at the same time.
To simplify this process for you though, I have provided an empty update.zip which you can place all of your resigned apps into and use to update your phone to your custom theme. You can also download someonelses theme and use there files, since they are resigned already. It may also be easier to see what files do what and go where since they have already been edited and are easy to point out.
Now, your ready to start changing things up.
You will now need to open the apk, which you can do by adding .zip after .apk, effectively changing it to a zip. Note that if you are using windows you will need to unhide known file extension types. you can also use your favorite archiver such as winrar, winzip, etc.
See here to unhide known file extension types for Xp: http://www.mediacollege.com/microsoft/windows/extension-change.html
See here to unhide file extension types for Vista: http://maximumpcguides.com/windows-vista/how-to-change-a-file-extension/
After opening the apk go to res and copy the folders that have drawable in their name. Go to your desktop, or wherever, create a new folder called Images, or whatever. Open the folder, paste the drawable folders in there. Now you can see what the files look like without opening them. Btw, you may also want to add -frame, or -launcher, to the end of the folders you cope over to keep them separated from others.
Finally, you've edited the images put them all in the apk renamed it back to an apk and resigned it. Now it's time to push it to your phone and see the changes you've made.
Important! : Whenever pushing files to the phone NEVER do it while the phone is running. Do this in recovery mode! If you do this while the phone is running normally you will begin to lose space in /system.
So, boot into recovery plug your phone in and open a cmd prompt. From the cmd prompt type adb shell mount /system then type the following: adb push c:\whereveryourfileis\whateveryourpushing.apk /system/app (system/framework if your pushing framework-res.apk)
Now reboot your phone. If it doesn't boot, try doing a wipe, if that doesn't work reinstall an update and try again. There are alot of things people can do wrong, I can't explain them all here. If you get real stuck, you can ask for help here or contact me on Gtalk [email protected].
So now your theme is done and your ready to make an update.zip for others to install your theme.
I have created a template for you to make your own update.zip. Just download, add the system apps to app, and framework to framework. Zip it up, SIGN IT, TEST IT YOURSELF, and then distribute it!
Empty update.zip template: Http://www.FightForthePits.com/Androidstuff/update_empty.zip
If anyone has any questions please try asking for help in this thread before emailing me for help Usually I will respond to questions in this forum.
I hope this Tutorial has been helpful. I will add on to it as needed.
Stericson
Links of interest:
Downloading SDK: http://code.google.com/android/intro/installing.html
Using ADB: http://code.google.com/android/reference/adb.html
Working with ninepatch should be straightforward if you use the draw9patch tool included in the SDK. Documentation on usage here:
http://code.google.com/android/reference/draw9patch.html
JF could also save theme users a wipe by resigning /system/app/* and /system/framework/framework-res.apk in his builds with the test keys. Nice tutorial, btw.
However it doesn't. I have used that to no avail. I believe you need to edit the images, put them in the source then rebuild the apks from the source.
As for JF's update, it does not currently wipe your phone after install. So, for him to do this he would have to have his update do a wipe. So technically, they would still have to do this initial wipe.
Stericson
Stericson said:
However it doesn't. I have used that to no avail. I believe you need to edit the images, put them in the source then rebuild the apks from the source.
Click to expand...
Click to collapse
Good point. I thought you could simply drop a similarly dimensioned PNG in but apparently there is some metadata that only the android tool can create.
As for JF's update, it does not currently wipe your phone after install. So, for him to do this he would have to have his update do a wipe. So technically, they would still have to do this initial wipe.
Click to expand...
Click to collapse
True, but a user who is upgrading to a JF update after having put in customized (and test-key signed) system apps will have to wipe again anyway =) Anyone using custom themes will have to wipe every time a JF update (or any update) comes out. However if JF resigns, custom theme users would not have to wipe and stock theme users only have to wipe once. (Nevermind the fact I think everyone should wipe when updating...)
thx stericson this will help big time how long before I can get resigned rc30 last night when you said all the apk. need to be resigned I was like this is going to be a long night but I see jf hooked you up save some big time with his resigning tool
jashsu said:
Good point. I thought you could simply drop a similarly dimensioned PNG in but apparently there is some metadata that only the android tool can create.
True, but a user who is upgrading to a JF update after having put in customized (and test-key signed) system apps will have to wipe again anyway =) Anyone using custom themes will have to wipe every time a JF update (or any update) comes out. However if JF resigns, custom theme users would not have to wipe and stock theme users only have to wipe once. (Nevermind the fact I think everyone should wipe when updating...)
Click to expand...
Click to collapse
Ah, good point
The resigned apps will be released maybye sometime tonight...I had them done but ran into a script problem on adp1 and I have yet to try the rc30 and rc8 ones yet. so I won't release those until I've tested them. If you want to be a Guinea pig however, just let me know
Stericson
Stericson said:
Ah, good point
The resigned apps will be released maybye sometime tonight...I had them done but ran into a script problem on adp1 and I have yet to try the rc30 and rc8 ones yet. so I won't release those until I've tested them. If you want to be a Guinea pig however, just let me know
Stericson
Click to expand...
Click to collapse
The resigned apps have been released, each update file will resign all of apps in /system/app and framework-res.apk. However, these updates make no changes to them whatsoever...Meaning your phone will look just like a brand new phone without any modifications.
rc30 works thx Stericson made it easy for use
Issues with using the update.zip above
Hi all,
I just wanted to point out that after I applied the update.zip above and rebooted applications kept force closing randomly and constantly even through the initial setup (where you have to click the green android to start).
Prior to this, I had JF's RC30 1.3, and the engineering bootloader V2 no sigcheck.
First I did just a alt+s then a alt-w and alt+s. And still nothing.
I'm new to all this so I'm not even sure where to begin troubleshooting. Should I be using the HardSPL?
Thanks in advance and I appologize if this isn't the right place for this post.
Update:
After reflashing with JF's 1.3 RC30 and the problem persisted I noticed that there was a new release 1.31 and this has fixed the problem. I hope this helps anyone else who runs into the same problem.
I still don't know what went wrong though, can anyone shed some light on this? thanks.
Truly there's no telling, sounds like J'f's update fixed it. Can I ask what version you tested?
I would also like to announce that now, thanks to JF, again, you do not have to wipe your phone completely to apply the resigned app updates. However, you will have to re-enter your google info and your call history and other minor things will be gone, but all of your apps will be retained.
Stericson
Alright, I am a little confused........
So I downloaded testsign.zip and extracted it to the tools folder. Then I went into environmental variables and added CLASSPATH with the value D:\Android\tools\testsign.jar and now I am not sure what to do next. Can someone give me some clarification. And btw I am on XP but I can get on linux at home if I need it, but I am a total noob to all this stuff so be gentle.
I'm using http://www.fightforthepits.com/Androidstuff/update_Rc30.zip and have been encountering issues when the phone boots up. As soon as the initial phone setup comes up I get process force close errors, I extracted launcher.apk, edited the files I wanted, repacked it, signed it and then resigned the update.zip. Any ideas what I'm doing wrong? I'm already running JF's RC30 1.31
Did you repack it in linux? Did you resign Launcher.apk? Also, that update file was never meant to be used as a template for an update since it kind of wipes your phone. You should be using update_empy, to push your own theme.
If you want to do only one file at a time, flash that update(update_rc30) then adb push your file into system/app. There are lots of things that you can mess up, most of them are hard to catch too. At any rate, everyone who has made a theme can tell you it's not just a straight forward process, expect errors. I've had more than I count I know....
Trial and error is your best teacher
Stericson
Stericson said:
Did you repack it in linux? Did you resign Launcher.apk? Also, that update file was never meant to be used as a template for an update since it kind of wipes your phone. You should be using update_empy, to push your own theme.
If you want to do only one file at a time, flash that update(update_rc30) then adb push your file into system/app. There are lots of things that you can mess up, most of them are hard to catch too. At any rate, everyone who has made a theme can tell you it's not just a straight forward process, expect errors. I've had more than I count I know....
Trial and error is your best teacher
Stericson
Click to expand...
Click to collapse
Must .apk's be signed if they're pushed over ADB? I'm not running Linux, I'm repacking/signing in windows.
I also had the issue with force close when installing the resigned update from the first post, apps that shouldn't even run on start up were force closing.
Also the IM application was gone, had to do a wipe and go back to jf 1.31 to correct it
I will take another look at the update I provided...
Stericson
did you ever figure out how to change the text on the status bar from black to white?
to do that you have to rebuiuld the entire apk from source and edit an xml document
Stericson
has anyone tried making the icons bigger? I noticed they are 48x48 if we go bigger will that affect anything? Also has anyone been able to remove the text below the icons on the home screen? Oh and where is the tab located that has been made invisible?
*edit
well I tried making the icons bigger and it doesn't really do anything, they don't show up bigger on the screen. Might have something to do with the text underneath, not sure.
Kyeld said:
Must .apk's be signed if they're pushed over ADB? I'm not running Linux, I'm repacking/signing in windows.
Click to expand...
Click to collapse
yes they must be signed.
Ok, so i modded about 6 png's that are for the notification bar.
However, when i add them to my used framework-res (no problems at all) my phone get's stuck in a bootloop.
After a quick question in the ROM threat, brady1uk mentioned the file size.
so i checked them, and before i modded them they were a total of 43kb, but now they are 143kb!
Could this be the problem of my bootloop, and if yes, how do i reduce the file size?
*added the status_bar png's*
I don't think it's the file size. Let me ask, when you "add them to your used framework-res" how do you do it? Did you extract the .apk then re-archive?
ephumuris said:
I don't think it's the file size. Let me ask, when you "add them to your used framework-res" how do you do it? Did you extract the .apk then re-archive?
Click to expand...
Click to collapse
I open the framework-res whit winrar, and i just drag and drop my custom files in there with out extracting it.
ok, so i replaced my new png's whit the old ones in the hope my phone would work again, but it didn't
Now i'm totaly clueless...
If someone could take a look at what i have combined and why it doesn't work it would love it (using lee droid 1.9A)
*sleeping*
dragonithe said:
ok, so i replaced my new png's whit the old ones in the hope my phone would work again, but it didn't
Now i'm totaly clueless...
If someone could take a look at what i have combined and why it doesn't work it would love it (using lee droid 1.9A)
*sleeping*
Click to expand...
Click to collapse
as all is failing i would suggest getting the original framework-res.apk - before u ever touched it (download leedroid rom again if you didnt back it up). And then use either APK Manager or Theme Pro to decompile the apk, then mod away and change everything you want then use APK Manager or Theme Pro to compile it back up. Thats how I do it. I think there is a chance using Winrar to just pull out the files and add them back in has currupted it somehow
brady1uk said:
as all is failing i would suggest getting the original framework-res.apk - before u ever touched it (download leedroid rom again if you didnt back it up). And then use either APK Manager or Theme Pro to decompile the apk, then mod away and change everything you want then use APK Manager or Theme Pro to compile it back up. Thats how I do it. I think there is a chance using Winrar to just pull out the files and add them back in has currupted it somehow
Click to expand...
Click to collapse
ok, so i did this, but now when i flash the .zip i get a error [ E:Failure at line 9: run_program PACKAGE:check_data_app instalation aborted.]
Ok, so after failing to create my own apk file i pulled it from my desire and added the 6 files to it.
adb push, reboot.
And it gets stuck in a bootloop...
So ok, that failed, but i had the pulled framework still on my computer, so i decided to push this file back to make it work again.
But now it's still stuck in a bootloop....
seems like my adb corupts the .apk or what could be the problem?
You shouldnt need to decompile it if your only making a few changes to the framework.
I use 7-zip to open the rom, navigate to the required apk, and open that archive then swap the images over, no need to delete the original, they will just get over written. Then press up or back within 7-zip. when you navigate out of the apk you were in 7-zip will say it has been changed, carry on, pressing back untill you are all the way out of the rom. Then resign the rom and flash it.
Ive never used apk tool to change images in the htc resources or the framework res and never had a problem.
dragonithe said:
ok, so i replaced my new png's whit the old ones in the hope my phone would work again, but it didn't
Now i'm totaly clueless...
If someone could take a look at what i have combined and why it doesn't work it would love it (using lee droid 1.9A)
*sleeping*
Click to expand...
Click to collapse
I pretty sure the framework in the zip you posted is not from Leedroid so theres your 1st problem. Unless you made more than just 6 png changes.
djmace said:
You shouldnt need to decompile it if your only making a few changes to the framework.
I use 7-zip to open the rom, navigate to the required apk, and open that archive then swap the images over, no need to delete the original, they will just get over written. Then press up or back within 7-zip. when you navigate out of the apk you were in 7-zip will say it has been changed, carry on, pressing back untill you are all the way out of the rom. Then resign the rom and flash it.
Ive never used apk tool to change images in the htc resources or the framework res and never had a problem.
Click to expand...
Click to collapse
I also sort of use your described methode, but istead of using 7-zip, i use winzip.
djmace said:
I pretty sure the framework in the zip you posted is not from Leedroid so theres your 1st problem. Unless you made more than just 6 png changes.
Click to expand...
Click to collapse
It could be that the base of the framework is from leedroid, but i added a theme to it (think it is NexTang-DJDroid).
used it for about a month w/o problems, then i changed 6 files in the framework. And nothing works anymore ._.
can you try flashing the stock leedroid fw-res.apk to see if you get out of the bootloop? if you can do that, then at least you have a fallback plan.
and instead of flashing it, try using:
Code:
adb mount
adb push framework-res.apk /system/framework/framework-res.apk
I have never had any problems doing it that way.
I had the same problems. But i tried to make a flashable zip file and this work very fine..
And remeber you can not just replace a 9.png file maybe this is your fault?
mista1982 said:
I had the same problems. But i tried to make a flashable zip file and this work very fine..
And remeber you can not just replace a 9.png file maybe this is your fault?
Click to expand...
Click to collapse
hmm,
could you tell me a bit more about that?
[GUIDE] how to make a flashable package (update.zip)
How to edit .9.pngs
nzdcoy said:
can you try flashing the stock leedroid fw-res.apk to see if you get out of the bootloop? if you can do that, then at least you have a fallback plan.
and instead of flashing it, try using:
Code:
adb mount
adb push framework-res.apk /system/framework/framework-res.apk
I have never had any problems doing it that way.
Click to expand...
Click to collapse
I have the same problem, could you tell me how to push the framework-res.apk step by step ( just press the power button --> ) . Sorry ....
dragonithe said:
Ok, so i modded about 6 png's that are for the notification bar.
However, when i add them to my used framework-res (no problems at all) my phone get's stuck in a bootloop.
After a quick question in the ROM threat, brady1uk mentioned the file size.
so i checked them, and before i modded them they were a total of 43kb, but now they are 143kb!
Could this be the problem of my bootloop, and if yes, how do i reduce the file size?
*added the status_bar png's*
Click to expand...
Click to collapse
Same thing happened to me!
I Wiped Cache, Dalvik Cache, but nothing happened!
I had to flash 2.3.6 Stock ROM via Odin, to make my phone work!
On my rooted Defy - how do I install a zip-file??
Like this one;
http://forum.xda-developers.com/showpost.php?p=12426274&postcount=24
install the 2ndinit apk 1.4.2 newer ones wont work with some files
then reboot 2 times.
third reboot: press volume down, when the led is blue.
now choose recovery by pressin vol up or down and power to accept.
then choose costum recovery, and apply zip from sd. choose your file and confirm.
done
hope this answers your question
Thanks, seems simple enough
uh, where do I find 2ndinit.apk
You can find it here.
I know how to install .zip but I have a question. CWM3.1 does not flash some .zip like a baseband or a theme. It says "aborted". I think that the problem is that the file is not signed or something. In CWM2.5.1.8 works but the problem is that CM7 or MIUI changes it to CWM3. So, what should I do?
Thanks!
Works fine, even the mentioned zip-file!
The "issue" is that the latest CWM3.x no longer support "amend scripting" (stored in update-script) and won't apply zip's created with such scripts. Therefore all .zip which where written using the old method should be converted to edify scripting (which use different statements - more details here-).
is there an way to downgrade the 2ndinit? an how-to would be very nice
You can replace the recovery file from /system/bootmenu/recovery/sbin with the one from 2nd init 1.4.2 . The file persimmon should be rwxr-xr-x (755).
nepotu said:
You can replace the recovery file from /system/bootmenu/recovery/sbin with the one from 2nd init 1.4.2 . The file persimmon should be rwxr-xr-x (755).
Click to expand...
Click to collapse
and how do i do that? with rootexplorer? what for do i need the file permission? to change it or to set it after changing the files?
Yup. You can replace it using an app like root explorer. And the file permission should be set up after you copy the file (if you have the wrong file permission it won't work).
EDIT: I haven't tried yet to downgrade it this way but that's what I've read on the forum, therefore I cannot guarantee you it will work.
sry for me being a noob. i found the file named recovery in the folder you mentioned. but have got only the file 2ndinit.apk..... where do i get the recovery file from 2ndinit.apk ?
thank you for your time!
You can unpack it using a tool like Apk Manager 4.9 or simply by using 7zip to extract the files from the apk which is in fact some sort of archive. However as I've mentioned in the previous post I didn't tried to downgrade using this method. All I can say is that I've read here on xda about this method, therefore I cannot guarantee you this will work. I think is better to wait someone with more experience to answer.
As an unexperienced user i think i'll wait for a better solution.
As i read, this problem appears quite often, how come that nobody tried to make a solution for this problem?
Hello, starting to get comfortable with Cygwin/Kitchen but still new at it. After repackaging and trying to flash Wicked Sensations, TWRP gives me an error (paraphrasing) "format, expect 3 args got 4".
I'm allowing the kitchen at the outset to convert updater script to "update" script, and allowing it to reconvert when it repackages. I'm accepting all defaults when repackaging.
I wonder if the kitchen is incompatible with some custom ROM's depending on what was used to create it in the first place? Or does somebody know where I'm going wrong? Thanks a million
Switch out the update binary with the original file from META-INF/com/google/android
CNexus said:
Switch out the update binary with the original file from META-INF/com/google/android
Click to expand...
Click to collapse
could you give me a little more detail? I see where the update-binary file is in the working ROM folder, but I don't see what to replace it with or where to paste that one?
SanDiegoHB said:
could you give me a little more detail? I see where the update-binary file is in the working ROM folder, but I don't see what to replace it with or where to paste that one?
Click to expand...
Click to collapse
It seems like the mayhem replaced the original update-binary...so replace it with the original update-binary from the Wicked Sensations rom zip
CNexus said:
It seems like the mayhem replaced the original update-binary...so replace it with the original update-binary from the Wicked Sensations rom zip
Click to expand...
Click to collapse
Sorry for the bother, I hate sounding dense, I'm just not following you because the only decompiled copy I have of the "update-binary" is the one in the Working ROM folder which was created from the original wicked sensations zip....
Huh...ok, post the "format(...." code that you have in your new updater-script
CNexus said:
Huh...ok, post the "format(...." code that you have in your new updater-script
Click to expand...
Click to collapse
thanks for your patience.
Here's what the "working rom" updater-script.orig says (note there are 3 arguments)
format("ext4", "EMMC", "/dev/block/mmcblk0p14");
But here's the error I get when I try to flash the rom with TWRP,
format () expects 3 args, got 4
E:Error executing updater binary in zip '/extern (it cuts off there)
Error flashing zip '/external_sd/(name of rom)
So I decided to decompile this output rom that gave me the error, and here's what the final updater-script says re: format:
format("ext4", "EMMC", "/dev/block/mmcblk0p14", "0");
As you said, it looks like something happens in the repackaging
Yeah, just use the original "format" command that only takes three arguments
And by "use" I mean copy it over to the new updater script
I also just found this http://forum.xda-developers.com/showthread.php?t=1906605 so I'll do some experimenting. What do you make of this:
"The problem is the Kitchen update to updater conversion. The kitchen doesnt make correctly the conversion. So the solution is: not give any script to kitchen for conversion, remove META-INF folder from original zip and let kitchen create a fresh updater.."
What is it that yoy are editing/changing with the kitchen? Because as long as you are not removing any files, you can use the entire META-INF folder from the original ROM in your edited ROM
CNexus said:
What is it that yoy are editing/changing with the kitchen? Because as long as you are not removing any files, you can use the entire META-INF folder from the original ROM in your edited ROM
Click to expand...
Click to collapse
Thanks for the tip! I was extracting (again) and decided to tell the kitchen to NOT do any update/updater conversion. Made my minor wallpaper edits. Repackaged. And everything worked like a charm.
Thank you very much!
SanDiegoHB said:
Thanks for the tip! I was extracting (again) and decided to tell the kitchen to NOT do any update/updater conversion. Made my minor wallpaper edits. Repackaged. And everything worked like a charm.
Thank you very much!
Click to expand...
Click to collapse
No problem
Whenever I try and flash Super Nexus, PA I get the same error Binary yada yada any general fix?
I removed Album as the default picture launcher like done by venkat kamesh (link to original thread is at the end) for other Xperia models following his nice tutorial , after installing you can choose which app will be used for opening your pictures out of the camera.
Updated 27/03/16
Instructions for MM (use the attached file SemcCameraUI-generic-xhdpi-release.apk)
device needs to be rooted
make a backup of your original "/system/priv-app/SemcCameraUI-generic-xhdpi-release/" folder so you can restore the original behaviour if needed.
copy my SemcCameraUI-generic-xhdpi-release.apk to "/system/priv-app/SemcCameraUI-generic-xhdpi-release/" folder to override the original file
change the permissions of SemcCameraUI.apk to the ones the original app has (rw-r--r--):
Code:
chmod 644 SemcCameraUI-generic-xhdpi-release.apk
delete oat folder
reboot - enjoy!
Instructions for LP (use the attached file SemcCameraUI.apk)
device needs to be rooted
make a backup of your original "/system/priv-app/SemcCameraUI" folder so you can restore the original behaviour if needed.
copy my SemcCameraUI.apk to "/system/priv-app/SemcCameraUI/" folder to override the original file
change the permissions of SemcCameraUI.apk to the ones the original app has (rw-r--r--):
Code:
chmod 644 SemcCameraUI.apk
reboot - enjoy!
Big thanks to venkat kamesh!!!
Original threads
http://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/mod-camera-album-default-app-t3139667
http://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/tut-how-to-remove-album-default-xperia-t3219268
will it work with marshmallow?
No, this version is only working for Lollipop.
I will make a MM version in the following days and post it here.
I'm.using this xposed module to accomplish the same thing.
http://forum.xda-developers.com/xposed/modules/mod-xperia-camera-enhancements-t3260643
I managed to modify the apk, unfortunately it doesn't start any longer, no idea why ... Any hints what could go wrong after recompiling the apk with apktool and cause the app to crash? I did it the same way as with LP ...
civicsr2cool said:
I'm.using this xposed module to accomplish the same thing.
http://forum.xda-developers.com/xposed/modules/mod-xperia-camera-enhancements-t3260643
Click to expand...
Click to collapse
This doesn't work on my MM system, I guess its only for LP ...
Thorstenk said:
This doesn't work on my MM system, I guess its only for LP ...
Click to expand...
Click to collapse
Yeah, I haven't made the jump to mm for a lot of reasons, xposed modules being a big one
Should work by now with MM, see first post for instructions!
Happy Easter
didn't work on mm (32.1.A.A.163), didn't appear in drawer and oat folder didn't recreate himself after reboot, permissions are correctly set, even wiped cache and dalvik/art cache through recovery. is there a problem with the apk ? could you post md5 of SemcCameraUI-generic-xhdpi-release.apk plz
sheraro said:
didn't work on mm (32.1.A.A.163), didn't appear in drawer and oat folder didn't recreate himself after reboot, permissions are correctly set, even wiped cache and dalvik/art cache through recovery. is there a problem with the apk ? could you post md5 of SemcCameraUI-generic-xhdpi-release.apk plz
Click to expand...
Click to collapse
On my device it works without having the oat-folder and as far as I know the oat-folder won't be created again, because the apk is deodexed ...
I just downloaded my file again and did the whole process again and it still works .
Did you do it (copy the file and set the permissions) via adb?
Could you try it again?
md5 is: 43774a75b358b255ca629c0bfd56e289
md5 is correct, I set permissions with total commander, I did it with root explorer too, the permissions are correctly set (rw-,r--,r--) but camera app is nowhere to be found ... I will try with adb and see
The camera is missing after I did this.
Tried it on Marshmallow, can you help bro?
Followed the instructions carefully. Thank you
Tried via adb, doesn't work as well.
Upon checking the file SemcCameraUI-generic-xhdpi-release.apk its still my default apk and not the one i pushed with adb (the one i downloaded here), the oat folder was still there as well. Pretty sure I deleted it via adb as well and no error showed up.
Update: Tried it again via adb, this time SemcCameraUI-generic-xhdpi-release.apk pushed properly with correct permissions and oat folder deleted as well. But the camera is now missing again. Any ideas? Thank you
I had somehow similar problems that I can't explain ... just copy back your original files including the oat folder and check if its working again (it should) and afterwards try it again. For me it works ...
Thorstenk said:
I had somehow similar problems that I can't explain ... just copy back your original files including the oat folder and check if its working again (it should) and afterwards try it again. For me it works ...
Click to expand...
Click to collapse
Thanks but tried it like 3 times already, no luck still.
Not working for me either on 6.0.1 -.-
Seems like .apk is broken or something (when opening .apk get parsing error )
and when replacing original .apk Camera disappears like the other ones said
Thorstenk said:
I had somehow similar problems that I can't explain ... just copy back your original files including the oat folder and check if its working again (it should) and afterwards try it again. For me it works ...
Click to expand...
Click to collapse
Hello, what about using Xposed to create a module like the one working for Lollipop?
it would be a lot easier for people instead of replacing files, messing with odex files and It could probably support all the MM releases. If i have some time i could try to do it, but i'm not as skilled as you.
Apart from that, thank you a lot for the work! I've been searching this since ever.
modified camera for MM 6.0.1
Herewith modified camera file from 32.2.A.0.224
For me it works like a charm.
Enjoy!!
bruno.trudo said:
Herewith modified camera file from 32.2.A.0.224
For me it works like a charm.
Enjoy!!
Click to expand...
Click to collapse
can you make a new one with .253 plz ?
Sure, I can. Please send me appropriate SemcCameraUI-generic-xhdpi-release.apk file.
I am still on .224
Thanks! Here it is : https://drive.google.com/file/d/0B9nyD39hGfrkTWxOczkwdXZZcnc/view?usp=drivesdk