Hi everybody, I'm trying to make a soundboard to put on the android market. I downloaded a soundboard template from http://myandroidsoundboard.com/, and it works great except I don't know how to successfully change the package name from "com.soundboard" to something else without making the project go all "error" crazy.
I click the package name in the the package explorer and click refactor and I change the package name, but then everything becomes an error because the package name is now different. How can I change the package name successfully so I don't get errors everywhere?
Thank you.
You don't need to change package name of Java classes. You must change package name stored in AndroidManifest.xml and maybe some other files.
Brut.all said:
You don't need to change package name of Java classes. You must change package name stored in AndroidManifest.xml and maybe some other files.
Click to expand...
Click to collapse
I've gone through the android manifest file and I've changed everything there, but do you know what other files might need some changing? The only errors I see are coming from anything with the "R" next to it.
PrestoMovie said:
I've gone through the android manifest file and I've changed everything there, but do you know what other files might need some changing? The only errors I see are coming from anything with the "R" next to it.
Click to expand...
Click to collapse
I think it may be caused by the fact that after changing package name R.java file is generated in different Java package, but app code references original one. I see several ways, how to fix this: you could alter ant building process, use some refactoring tools to modify all references to R class or manually move generated R.java to proper place (and modify package declaration in it).
If you know, what I'm talking, then good. If you don't then it probably does not have sense to explain it further - it will take several pages of posting until you will get it.
Brut.all said:
I think it may be caused by the fact that after changing package name R.java file is generated in different Java package, but app code references original one. I see several ways, how to fix this: you could alter ant building process, use some refactoring tools to modify all references to R class or manually move generated R.java to proper place (and modify package declaration in it).
If you know, what I'm talking, then good. If you don't then it probably does not have sense to explain it further - it will take several pages of posting until you will get it.
Click to expand...
Click to collapse
which way would you say is this easiest? And would you be able to point me in the direction of a link that explains any of them well?
For what it's worth - archival value & others reading this thread now - a link to such info would be appreciated
PrestoMovie said:
which way would you say is this easiest? And would you be able to point me in the direction of a link that explains any of them well?
Click to expand...
Click to collapse
Ok, actually this can be done very simply ;-)
I think the best solution is to refactor code. Do you use some good IDE? Eclipse, Netbeans? If so you could use their refactoring tools, but it is also doable by simple find/replace. Just replace all occurrences of "import old.package.name.R;" in all *.java files by "import new.package.name.R;".
These are basics of Java/Android developing: if you know them, then you should have no problems
Brut.all said:
Ok, actually this can be done very simply ;-)
I think the best solution is to refactor code. Do you use some good IDE? Eclipse, Netbeans? If so you could use their refactoring tools, but it is also doable by simple find/replace. Just replace all occurrences of "import old.package.name.R;" in all *.java files by "import new.package.name.R;".
These are basics of Java/Android developing: if you know them, then you should have no problems
Click to expand...
Click to collapse
I'm using Eclipse. And thank you! Hopefully I can get it working now!
K, for some reason I'm only getting one error now in the androidmanifest.xml and it says "class com.soundboard.SoundBoard doesn't exist", but com.soundboard is no longer the package name.
bump bump bump.
bump.
I'm having the same problems. I've been able to create working .apk's but need to share it in the market and the market won't let me if the package name is the same thanks.
agentkalaw said:
bump.
I'm having the same problems. I've been able to create working .apk's but need to share it in the market and the market won't let me if the package name is the same thanks.
Click to expand...
Click to collapse
Advanced tasks require some knowledge. You must know, what is Android's package name and then changing it will be really easy thing to do.
Ahh and there is new "--rename-manifest-package" switch in newest aapt tool. I didn't test it, but it's official Android tool, so this should work.
PrestoMovie said:
K, for some reason I'm only getting one error now in the androidmanifest.xml and it says "class com.soundboard.SoundBoard doesn't exist", but com.soundboard is no longer the package name.
Click to expand...
Click to collapse
thanks for the help! I was actually able to change the package name and I'm having the exact same problem as the OP ^. I basically just need to edit the androidmanifest.xml file and i should be all set I tried searching on how to edit it after changing package names but no luck. any ideas? how do i edit androidmanifest.xml files to recognize the package name change? thanks again
Its been a long time since this post, but if it helps someone:
Issue: You have a source, you want to build 2 different apks from the same source, and be able to install both in the same device at the same time.
General Solution: Use a refactoring tool, like in eclipse, and rename all package names.
Better Solution: use aapt flag --rename-manifest-package. This does not require you change even a single line in the original source. Just this flag, and pass in a different package name, and whoa, you have a new apk with the different package name. I used it as follows, in the Android.mk:
LOCAL_AAPT_FLAGS := --rename-manifest-package new.package.name
Click to expand...
Click to collapse
Cheers
I looked everywhere tried every program from APK Edit, APK Tool, APK Manager, Eclipse and a few others, I cannot figure out how to edit the Strings.xml in APK files.
APK Edit and APK Tool / APK Manager just gives me issues when i try to edit the strings, when i finally get them changed over and push to the phone it doesn't install the .apk, tried this on two different devices with no change.
I'm making theme files but i require to edit the strings value so the names are different, and i'm using an OEM file as my base file.
When I edit the .apk with my themed graphics and go to install it, it always wants to overwrite the original, but i've found that others have been able to just rename the strings value to another name so it wouldn't replace it.
What i'm trying to do is not replace original skins in HTC sense 2.x. Since there installable they can be installed multiple times if there values are changed in strings.xml, allowing for massive customization options.
I need the developers community to show me how to do this, i've tried on my own and i've failed each time, and i also tried contacting the themers that have done this on there own but they refuse to help me.
I have a bunch of skins i'm working on but i can't render my skins and theme the apk files until i can do this
You guys are my last bit of help i can find.
Hello,
I'm trying to hack an apk.
My first step was to use apk multi tool, and to just decompile and recompile it.
This is what i've done:
decompiling
recompiling (without any mod)
signing
No error appears during those steps.
But this new apk won't install on my phone !
If I check difference between the two apk:
all xml files are differents
.RSA and .SF have not the same name
classes.dex, resources.arsc and manifest.mf are differents
I don't understand those difference. can somebody help me to understand that and how to recomile a proper version ?
PS: This app is a french app that shows speed cameras on the road. However this app is now only showing a big zone and not the exact location for france. But it stills show precise location for other countries, so obfuscation is done at the apk level, and I already found where it is in the code, so i'd like to bypass it and recompile a "special' version
Thanx
Just a few quick questions. Is you phone set to install from sources than Droid market? You do know the newly compiled and signed project will be located in the "place_package _here_ for_Modding" folder and is named "Signed(yourappnamehere).apk?
Sent from my SAMSUNG-SGH-I727 using xda premium
Hi,
yes, i took the newly compiled apk in this directory, and yes my phone is set accept unknown sources.
When i install the apk, i first have the
- liste of phones serviesc that will be used
- then the install progress bar
- then the message "application not installed"
I guess there is some kind of protection in the sources...
I also noticed that the two apk - original, and resigned one - don't have same size.
The only difference is actually in the META-INF directory : the .RSA and the .SF files.
In the original application they are:
- IFOX_.RSA
- IFOX_.SF
But when recompiling, those files are:
- CERT.RSA
- CERT.SF
I'm shure the problem comes from here, but i'm too noob to analyse that...
So my proble can be sum-up by:
Why the recompilation doesn not give me the same RSA and SF file ??
Beware there are some modifications that you cant do on decs, expecially the packagename.
also beware to disable the "non-market" tag on the phone.
Yes, but for the moment i didn't make any modification:
Just decompiling, recompiling and resigning.
Maybe you want to tell that the apk name must stay the same ? (sorry my english is not perfect )
GOT IT WORKED !!!
You must first uninstall the previous application !
I was trying to install my new one over the old one, but the signatures are not the same !!!
Thanx everybody, and hope this will help somebody !
APK edit error 103
Ok im having a similar issue.
I know the file size is mismatched but ive never had this issue
as a test i only modded 1 thing but 4 files
changed a link in an html / changed an image and its name and the html included the link to the new name
when this failed i changed the manifest and the .sf to match the change i made with name but not the sha :"no clue here"
Tried...
APK multi tool ... and 7zip to make the mods
Tried... Bothsigned and unsigned.
Tried copying the sig from old apk to new with names corrected "notsha" fail still
Tried....
Origional APK installs no issue
Uninstall orig apk rebooted
Allow out side apps yes and no.both
using file manager explorer and root browser and es file manager
Copying directly to /system/app fail
copying to data/data/app/copy fail " yes it wont even copy to there"
Tried.. Multiple phones
I then tried a hex editor on the apk. And after changes install still fail.
I modded several other apk's even my framework but this is the first app that ha given me so many issues
This is an app to help elderly users access internet and the devs are AWOL and the project abandoned
Code:
https drive google com/folderview?id=0B5PggxVy7c8meDhrcjNJOGs5cFk&usp=sharing
Code:
www eldy eu/en/software/eldy-tablet/
"edited for posting "
The goal here is to make it more U.S. friendly its English base is geared to English UK and this does not help my family as we are in the U.S.
All i can get from logcat is error 103
Logcat shows package it.vegans.eldy has no certificate at entry AndroidManifest.xml ignoring
Knstallation error code 103
I tried apk multitool certify thing
i tried copying the certs from old to new apk
i tried modding the cert to correct names
So maybe im mentally challenged but i just cant figure this one out
---
Edit .
I attached a zip with original and modified apk's
All i want to do is simple html edits xml link edits and img changes since mostly the app is a series of pages.
I own a BB Playbook tablet for about a year now (bought it during the when it was about 200$ because I needed a 7'', the hardware was specs were nice at the time and the company promised Android app support). Regardless of the sanity of my decision the device saves me about 2 hours per day (I use it mainly to read pdf and build an xls database).
I've converted many apk to bar in order to sideload them to my device (not all of these work). Recently I tried Firefox on my Xperia mobile and was quite pleased with the ABP plugin So I tried to convert the apk but both the apk2bar and the Blackberry Graphical Aid Tool complain that the version number is too long...
Anyone knows how to shorten it? In what file is it located? Or anyone up for the task.
Keep in mind I'm not a dev.
Thanks in advance
android:versionName is what you need to change.
Thanks for the reply.
Tried the apps from your sig. I managed to edit AndroidManifest.xml. Recompiling (after the changes) doesn't seem to work (the result apk is much smaller... many files/folders from the original FF apk were not in the project folder or compiled apk).
Tried unpacking + zip + sign but this last step is failing. Wanam APK suite keeps giving an error message. My box runs Win7 x64 and at first I only had Java RE x86 7.10... it didn't find Java in my machine and stated signing would not work; after I installed the x64 it gives no preemptive messgae and I progress further but the signing process fails
frmariam said:
Thanks for the reply.
Tried the apps from your sig. I managed to edit AndroidManifest.xml. Recompiling (after the changes) doesn't seem to work (the result apk is much smaller... many files/folders from the original FF apk were not in the project folder or compiled apk).
Click to expand...
Click to collapse
Hi.
Look at the files in the apk before decompiling it and you'll see that all those files and folders aren't there to begin with. All those files and folders are from the decompiled resources.arsc so it's normal for them not to be there when recompiled, and when you add the resources.arsc, manifest and meta folder from the original apk to the recompiled apk, it will become larger.
I noticed yesterday I had put an old apktool in the folder but have corrected it now so download and try again.
I was attempting to do the same so I decompiled and edited the android:versionName and the android:versionCode . After doing that, recompiling and resigning I was able to convert using apktobar and load to the playbook with no issues......except the app opens to an all white page and nothing beyond that will work! Just to be clear I was attempting to convert Firefox as well. Hope someone has some helpful hints that could fix it!
Hello developers. I got an app and I followed the tutorial [TOOL] APK_OneClick - decompile
and decompiled the app I want to modify. Here what I got now all the smali files and xml files but these are too many and I am unable to change because of inexperience. I run the apk file on java by right click and selected java decompiler and it has opened java decompiler. Here what I want to do:
changing the app name and package name
changing theme and graphics of the game
changing the start splash screen to another. I want to add push notification too
P.S the developer of the app has given the rights to me to modify and its a challenge b/w me and my friend. I hope you guys will help me.
Thank you