I am trying to write a simple program in eclipse. I noticed that I guess with ICS 4.0, when you update strings.xml, the strings.out.xml is affected, because when i change strings, it gives an error at strings.out. what must I do so that this no longer happens? when i coded with this before (before ics) i never encountered these files
sniper8752 said:
I am trying to write a simple program in eclipse. I noticed that I guess with ICS 4.0, when you update strings.xml, the strings.out.xml is affected, because when i change strings, it gives an error at strings.out. what must I do so that this no longer happens? when i coded with this before (before ics) i never encountered these files
Click to expand...
Click to collapse
what is the actual error that is apearing?
Pvy.
pvyParts said:
what is the actual error that is apearing?
Pvy.
Click to expand...
Click to collapse
res\layout\activity_main.xml:0: error: Resource entry activity_main is already defined.
res\layout\activity_main.out.xml:0: Originally defined here.
Related
So here's the thing, after wrestling a lot with android sources to get them to compile, I did.
So now comes the task of adding a new device so I can actually compile it for my phone. Here's what I already did:
1. Used the existing CM sources for my phone and put them in devices/samsung/ancora (also ran extract-files.sh, and did all the necessary changes)
2. Got all the vendor files and put them in vendor/samsung/ancora
3. Altered the envsetup.sh to include the line "aokp_ancora-userdebug" so I can actually tell it to build the damn thing
4. Added an ancora.mk to the vendor/aokp/products folder with all the necessary information
Now what happens when I try to build is I get the error:
Code:
build/core/product_config.mk:205: *** No matches for product
How do I go about fixing this?
Thanks in advance for all those who help.
KezraPlanes said:
So here's the thing, after wrestling a lot with android sources to get them to compile, I did.
So now comes the task of adding a new device so I can actually compile it for my phone. Here's what I already did:
1. Used the existing CM sources for my phone and put them in devices/samsung/ancora (also ran extract-files.sh, and did all the necessary changes)
2. Got all the vendor files and put them in vendor/samsung/ancora
3. Altered the envsetup.sh to include the line "aokp_ancora-userdebug" so I can actually tell it to build the damn thing
4. Added an ancora.mk to the vendor/aokp/products folder with all the necessary information
Now what happens when I try to build is I get the error:
Code:
build/core/product_config.mk:205: *** No matches for product
How do I go about fixing this?
Thanks in advance for all those who help.
Click to expand...
Click to collapse
In vendor/products, did you also edit AndroidProducts.mk?
KBizzle said:
In vendor/products, did you also edit AndroidProducts.mk?
Click to expand...
Click to collapse
Yes I did. And it points to the ancora.mk that I created.
Ok I am trying to build a Torch APK from git sources from Wayland_Ace. I went to repository and downloaded them as a zip. I've set up ADT and have Eclipse running. I chose to create a project with existing sources and chose the folder I extracted from the zip.
Now, I want to make some edits to this and I already know how and what I am going to, but I figured I would make sure the app would build before I made any changes and it won't. I get four "TORCH_STATE cannot be resolved or is not a field" errors and few warnings about some imports never being used.
I have a feeling this is because it's importing the settings from stock Android and not CM10.1. Can anyone help me fix this so I can build a Torch APK. I've Googled and fooled around with this for hours and have not had any success and am getting a bit frustrated.
admiralspeedy said:
Ok I am trying to build a Torch APK from git sources from Wayland_Ace. I went to repository and downloaded them as a zip. I've set up ADT and have Eclipse running. I chose to create a project with existing sources and chose the folder I extracted from the zip.
Now, I want to make some edits to this and I already know how and what I am going to, but I figured I would make sure the app would build before I made any changes and it won't. I get four "TORCH_STATE cannot be resolved or is not a field" errors and few warnings about some imports never being used.
I have a feeling this is because it's importing the settings from stock Android and not CM10.1. Can anyone help me fix this so I can build a Torch APK. I've Googled and fooled around with this for hours and have not had any success and am getting a bit frustrated.
Click to expand...
Click to collapse
How are you trying to build the apk? Through eclipse or through the android sdk?
fairct said:
How are you trying to build the apk? Through eclipse or through the android sdk?
Click to expand...
Click to collapse
Eclipse.
admiralspeedy said:
Eclipse.
Click to expand...
Click to collapse
I took a look at the source (CMs, not the one you pulled), and it is indeed because you don't have the CM SettingsProvider. It may sound foolish, and I'm not sure what will happen, but you could try commenting it out. I think that's just updating a system var so that things like the power widget can update appropriately. Worst case scenario you get a force-quit, or your LED won't turn off, forcing a battery pull
fairct said:
I took a look at the source (CMs, not the one you pulled), and it is indeed because you don't have the CM SettingsProvider. It may sound foolish, and I'm not sure what will happen, but you could try commenting it out. I think that's just updating a system var so that things like the power widget can update appropriately. Worst case scenario you get a force-quit, or your LED won't turn off, forcing a battery pull
Click to expand...
Click to collapse
I'm not going to do that, however your answer is extremely helpful now that I know it's caused by settings provider. Do you know how I could use a different settings provider in Eclipse? I could take the CM10.1 from the git of the ROM I'm using and somehow use it in Eclipse.
I really find it strange that I can only find a couple other people asking the same question as I. Do people not edit a single app from Cyanogenmod or some other ROM like AOKP without rebuilding the entire source? Upon doing some more Googling, it seems I need an Android.jar from Cyanogenmod.
Hoew I get this, I'm not sure.
admiralspeedy said:
I really find it strange that I can only find a couple other people asking the same question as I. Do people not edit a single app from Cyanogenmod or some other ROM like AOKP without rebuilding the entire source? Upon doing some more Googling, it seems I need an Android.jar from Cyanogenmod.
Hoew I get this, I'm not sure.
Click to expand...
Click to collapse
Well, I think they generally pull whatever APK they want, and then modify it to make it work. In some instances, that means changing other apks due to interdependency. Maybe someone who's familiar with building in eclipse could point you in a better direction...
I did it. I followed a guide to build a custom Android.jar from my phones framework.jar and Eclipse wouldn't build after because of it, so instead I only replaced the class files for settingprovider and my app had no errors after. I then saved the class files I edited, decompiled the classes.dex from the existing Torch APK and replaced the classes in it with my edited ones, recompiled that into a new classes.dex and put that in the Torch APK and it worked!
Hello,
I build a couple ROMs and make my own mods/apps. However, when re-adding them back to the system directory, i get this in the logcat, and then the apk/jar is not loaded and doesn't let the ROM boot.
Error:
Code:
01-01 00:07:19.157: E/PackageManager(9928): Package com.sec.android.app.nfctest has no signatures that match those in shared user android.uid.system; ignoring!
I know exactly what the issue is, the signatures of the new modded file do not match what is found in android.uid.system.
What I am asking, is, how can I change what is found in the android.uid.system UID?
I tried re-signing all the jar and apk files of the ROM to see if that changes it but it still shows that same error in the log.
I have no idea where this is stored the UIDs of the system.
THanks all for looking!
UIDs are not stored anywhere on the system lol. That's like asking where your IP addresses are stored!
You really should do some googling - this is pretty basic level stuff that can be understood easily once read.
I know you haven't tried googling UIDs because you wouldn't have asked this question if you had.
I know you don't develop apps either or you would understand this already too.
CtrlAltDelIrl said:
UIDs are not stored anywhere on the system lol. That's like asking where your IP addresses are stored!
You really should do some googling - this is pretty basic level stuff that can be understood easily once read.
I know you haven't tried googling UIDs because you wouldn't have asked this question if you had.
I know you don't develop apps either or you would understand this already too.
Click to expand...
Click to collapse
Thanks for the laugh I appreciate it! Youre a joke dude, i have created a bunch of apps and created ROMs which people love. I don't know who you think you are but you're obviously an idiot. If you have nothing to contribute, but smart ass remarks, mind your own business.
The packagemanager is obviously doing a signatures check with something else, that something else is stored somewhere, so yes, the system UID is stored somewhere.
Ok then smartypants
What I am asking, is, how can I change what is found in the android.uid.system UID?
Click to expand...
Click to collapse
This doesn't even make sense. The UIDs are dynamically served (like IP addresses) by Android.
There is nothing "in" the system UID. It is just a UID lol.
You need to look at your manifest.xml or makefile for your app, not recompiling Android to suit your app.
Now who's the idiot?
CtrlAltDelIrl said:
Ok then smartypants
This doesn't even make sense. The UIDs are dynamically served (like IP addresses) by Android.
There is nothing "in" the system UID. It is just a UID lol.
You need to look at your manifest.xml or makefile for your app, not recompiling Android to suit your app.
Now who's the idiot?
Click to expand...
Click to collapse
You are. Because its a system app that i am modifing i cannot "change the manifest" you need to resign the manifest when you change it or else the apk does not get loaded.
And there is a thing in the manifest called sharedUserId="android.uid.system" the PackageManager is checking if this apks signature matches the UID of "android.uid.system". When they don't match, the error posted in the OP is thrown by the package manager and the package is no longer loaded. If i sign the apk with my own keystore, then it won't grant the apk the signature level permissions it needs to properly run.
You obviously have no idea what i am talking about or trying to do..
Modders lol.
You shouldn't play with things you are incapable of understanding!
Good luck!
CtrlAltDelIrl said:
Modders lol.
You shouldn't play with things you are incapable of understanding!
Good luck!
Click to expand...
Click to collapse
I understand exactly what the problem is dude.. I understand exactly what i am doing, just don't know how to fix it. Thanks for contributing nothing
Hey @elesbb
Did u find out the solution for this issue? I'm tryin to do some ports from miui to AOSP and I'm having this error while tryin to install.
Hope u answer. Have a nice day.
LOswaldoRO said:
Hey @elesbb
Did u find out the solution for this issue? I'm tryin to do some ports from miui to AOSP and I'm having this error while tryin to install.
Hope u answer. Have a nice day.
Click to expand...
Click to collapse
Yes but you HAVE to use xposed
elesbb said:
Yes but you HAVE to use xposed
Click to expand...
Click to collapse
Please, could you tell me how to do it? Files that I need and all that stuff?
Thanks in advance man.
the solution found here worked for me: Signing my android application as system app - Stack Overflow
Hi,
I seem to have destroyed some things in my /system partition, and since I'm too stupid to make a backup before I edit a single file, I could really need your help.
The version I currently have installed is the one with the following values in the files:
/custom_build_verno:
20140513.163904
/system/build.prop:
ro.adups.fota.version=TrueSmart-20140513-1040
As far as I know right now, the following files are being complained about in the boot loop that I'm currently stuck in:
E/linker (25065): load_library(linker.cpp:757): library "/system/lib/libnetcmdiface.so" not found
E/linker (25064): load_library(linker.cpp:757): library "/system/lib/soundfx/libloudnesswrapper_mtk.so" not found
Can someone check if they are available in their TrueSmart or if this is a red herring and this file is not available at all?
The missing files are not available in the firmware found in these forums with the file name Omate_TrueSmart_20140513.103530_V2.0.zip
Can anyone verify in their logcat that they are also getting these missing file errors on a working TrueSmart?
Snackiz said:
E/linker (25065): load_library(linker.cpp:757): library "/system/lib/libnetcmdiface.so" not found
E/linker (25064): load_library(linker.cpp:757): library "/system/lib/soundfx/libloudnesswrapper_mtk.so" not found
Click to expand...
Click to collapse
Hi, I clearly remember seeing these 2 error when I messed up with my TS. (I did many things, not sure what caused this)
I finally managed to go back to stock with "sp flash tools".
MrTip said:
Hi, I clearly remember seeing these 2 error when I messed up with my TS. (I did many things, not sure what caused this)
I finally managed to go back to stock with "sp flash tools".
Click to expand...
Click to collapse
Thanks. I flashed the system partition and it's working fine now.
Hi,
I own a Pono player, which is great when it comes to sound, but has a crappy firmware.
On early versions, it seems that debugging was easier (https://forum.xda-developers.com/t/...-file-1-0-3-gingerbread-complete-rom.2967757/) but since version 1.0.6 everything is locked (or I'missing something.. how did they extract logs, ROMs, etc?).
So my idea is to craft a fake update file in order to re-enable adb, push a new main app, etc.
The upgrade process works as follow:
- Connect the PonoPlayer and put a "pono_1.0.6.update" file on the /.pono/ directory
- Craft a firmware.xml file which is supposed to contain the current firmware version: set it to 1.0.5
- Disconnect the Pono, it now thinks it' in version 1.0.5 and an upgrade to 1.0.6 is available.
Internally, the main Pono app scans the .pono/ folder and calls RecoverySystem.verifyPackage.
This works just fine: the device updates again to version 1.0.6.
Now I want to modify this update file and I still have no success even with a simple unpack/repack, without touching anything, thus not altering signatures.
I've tried to unpack/repack using apktool ("apktool d pono_1.0.6.update" + "apktool b pono_1.0.6.update.out") but the firmware update fails (stucked at 0%, and according to the app code that's what happens when an unexpected exception occurs).
I've tried to re-sign it (PonoPlayer is using the android testkey) with no more success.
How is it that a simple unpack/repack creates an apk with seems wrong is some ways?
Thanks for any help, I'm quite stucked..
NothNoth said:
Hi,
I own a Pono player, which is great when it comes to sound, but has a crappy firmware.
On early versions, it seems that debugging was easier (https://forum.xda-developers.com/t/...-file-1-0-3-gingerbread-complete-rom.2967757/) but since version 1.0.6 everything is locked (or I'missing something.. how did they extract logs, ROMs, etc?).
So my idea is to craft a fake update file in order to re-enable adb, push a new main app, etc.
The upgrade process works as follow:
- Connect the PonoPlayer and put a "pono_1.0.6.update" file on the /.pono/ directory
- Craft a firmware.xml file which is supposed to contain the current firmware version: set it to 1.0.5
- Disconnect the Pono, it now thinks it' in version 1.0.5 and an upgrade to 1.0.6 is available.
Internally, the main Pono app scans the .pono/ folder and calls RecoverySystem.verifyPackage.
This works just fine: the device updates again to version 1.0.6.
Now I want to modify this update file and I still have no success even with a simple unpack/repack, without touching anything, thus not altering signatures.
I've tried to unpack/repack using apktool ("apktool d pono_1.0.6.update" + "apktool b pono_1.0.6.update.out") but the firmware update fails (stucked at 0%, and according to the app code that's what happens when an unexpected exception occurs).
I've tried to re-sign it (PonoPlayer is using the android testkey) with no more success.
How is it that a simple unpack/repack creates an apk with seems wrong is some ways?
Thanks for any help, I'm quite stucked..
Click to expand...
Click to collapse
Alright, I think I got it:
When rebuilding, the original scripts found in META-INF/com/ are lost. Just need to figure out how I can place them back.
It's probably for me time to read: https://forum.xda-developers.com/t/guide-index-how-to-modify-an-apk.4208093/post-84170227
NothNoth said:
Alright, I think I got it:
When rebuilding, the original scripts found in META-INF/com/ are lost. Just need to figure out how I can place them back.
It's probably for me time to read: https://forum.xda-developers.com/t/guide-index-how-to-modify-an-apk.4208093/post-84170227
Click to expand...
Click to collapse
For the record, I finally found how to fix that: https://forum.xda-developers.com/t/need-tech-advice-before-archeology.4306981/#post-85423037
Hi, I inadvertently wiped ny pono player, so now no music shows on player or the SD card. I formatted the internal memory when I was supposed to format the SD card. I am sure the player will now be unusable. Is this right ?