An android prject, thought as two app, installed on the phone twice, Online

posts by benzmonkey edited 2013-11-15 16:42:26

Is this:
I have a andrid project, the overall tone is red, we call it Project A, I installed on my phone,
Now due to certain needs, there is a project B, with A roughly similar functions, just turned blue tint, removed some features, added some features, but the code is based on the reform project A code paths are the same, how can I put the phone works as a B and then re-installed upstream about it?
That is, both mounted on a mobile phone A.APK, also installed B.APK, is to modify the manifest files? Or modify the code path? What is the signature? Online,<-! Main posts under Banner (D4) -><-! Posts under the main text (D5) ->
Reply:
Another package name on the line, like the other horses are your God does not matter
Reply:
Change the package name, manifest inside the package
Reply:

 
A: 
package = "com.test.a" 
android: versionCode = "1001" 
android: versionName = "1.0"> 
B: 
package = "com.test.b" 
android: versionCode = "1001" 
android: versionName = "1.0"> 

This can be a
Reply:

cited landlord benzmonkey reply:

is this:
I have a andrid project, the overall tone is red, we call it Project A, I installed on my phone,
Now due to certain needs, there is a project B, with A roughly similar functions, just turned blue tint, removed some features, added some features, but the code is based on the reform project A code paths are the same, how can I put the phone works as a B and then re-installed upstream about it?
That is, both mounted on a mobile phone A.APK, also installed B.APK, is to modify the manifest files? Or modify the code path? What is the signature? Online,

That code path is not to be adjusted, adjusted to the new package with the same name as the structure?
Reply:

reference to the third floor lieri111 reply:

 
A: 
package = "com.test.a" 
android: versionCode = "1001" 
android: versionName = "1.0"> 
B: 
package = "com.test.b" 
android: versionCode = "1001" 
android: versionName = "1.0"> 

This can be a

That code path is not to be adjusted, adjusted to the new package with the same name as the structure?

        


Reply:

reference to the second floor youngc527 reply:

change the package name, manifest inside the package

That code path is not to be adjusted, adjusted to the new package with the same name as the structure? Or just modify the manifest of this property, and the rest do not move, you OK? ?
Reply:
After recompiling the package name changed, R file regenerate, all references to the place might be R Ctrl + Shift + O look, I wish you good luck

Reply:
The mainifest file can be right,
Reply:

references, 5th Floor benzmonkey reply:

Quote: references to the third floor lieri111 reply:

 
A: 
package = "com.test.a" 
android: versionCode = "1001" 
android: versionName = "1.0"> 
B: 
package = "com.test.b" 
android: versionCode = "1001" 
android: versionName = "1.0"> 

This can be a

That code path is not to be adjusted, adjusted to the new package with the same name as the structure?

Change or not change the matter, do not change, then change R compile time import file can be
Reply:

reference to the 7th floor youngc527 reply: After

changed the package name to recompile, R files will be regenerated, all references to the place where R may be Ctrl + Shift + O look, I wish you good luck

Well! Thank you for pointing, modify the manifest file inside the package, and re-searched and all documents referenced class R, replace all come under the import path again manifest path by which all activity relative to absolute, ok it! !