So,
I've been developing applications for a while and today went I went on to compile one of my projects, my APK kept getting corrupted.
This has only started doing this recently and I haven't done anything to Eclipse or the Android SDK.
This is not something to do with my Android Device nor my code.
Anyone got an idea?
here's a problem
i dont know about your android version
if your android version is below 4.2.2 sometimes in case it shows parse error
if it not you didnt properly compiled the apk file
hit thanks if i helped:good:
There are three possible answers.
One - Your device's Android SDK level is too old. (App requires new Android version).
Two - Your app contains manifest errors. (Highly unlikely).
Three - You did not sign your application. (This is very likely).
Sent from my Nexus 5 using Tapatalk
Related
Hey all.
Had this issue for a while now and I have no idea what's causing this problem. It started a week or 2 after updating to the Modaco beta rom from v3 to v4. I assumed it was because I hadn't wiped but I tried a full wipe and tried Overcome but I have the same issue. It worked fine on the first boot, but after rebooting it kept force closing again
Anyone else having issues with it?
Sent from zombie infested Gingerbread.
GANJDROID said:
Hey all.
Had this issue for a while now and I have no idea what's causing this problem. It started a week or 2 after updating to the Modaco beta rom from v3 to v4. I assumed it was because I hadn't wiped but I tried a full wipe and tried Overcome but I have the same issue. It worked fine on the first boot, but after rebooting it kept force closing again
Anyone else having issues with it?
Sent from zombie infested Gingerbread.
Click to expand...
Click to collapse
You can trace the cause by inspecting the android log file. You can view the log file with adb or (more convenient) on the Tab itself with one of the log viewers on the market. I myself use catlog.
If you post the log, I can see what is going on, and if necessary update the keyboard.
No issues here, and I just updated to JMIv2 this past weekend.
Realised my mistakes. I think its because I changed the build.prop sdk number to 9 to fit in with my Gingerbread theme, but after a fresh wipe and not changing orbits fine. Strange thing is, it still force closed after I changed it back to 8.
Sent from my GT-P1000
GANJDROID said:
Realised my mistakes. I think its because I changed the build.prop sdk number to 9 to fit in with my Gingerbread theme, but after a fresh wipe and not changing orbits fine. Strange thing is, it still force closed after I changed it back to 8.
Sent from my GT-P1000
Click to expand...
Click to collapse
Which version do you have? Later versions are compatible with all current SDKs (also sdk 10: honeycomb)
appelflap said:
Which version do you have? Later versions are compatible with all current SDKs (also sdk 10: honeycomb)
Click to expand...
Click to collapse
2.9.2b?
The latest one Probably fc because I'm tricking it into thinking its 2.3?
Sent from my GT-P1000
GANJDROID said:
2.9.2b?
The latest one Probably fc because I'm tricking it into thinking its 2.3?
Sent from my GT-P1000
Click to expand...
Click to collapse
Yes! that certainly could be the case. It uses specific native libraries that differ across some android versions. If you tell it that it's running on sdk 9 it tries to load a native lib that is build for sdk 9. But weird that you still got an error on sdk 8.
appelflap said:
Yes! that certainly could be the case. It uses specific native libraries that differ across some android versions. If you tell it that it's running on sdk 9 it tries to load a native lib that is build for sdk 9. But weird that you still got an error on sdk 8.
Click to expand...
Click to collapse
Aha, my mistake
It is strange. I thought after a few reboots, uninstalling and reinstalling it'd have been fine, but it just wasn't working after that. All fine since I haven't changed the SDK number though
Sent from my GT-P1000
Hello every one
I'm tuck in my problem for few days now. I want to run streamline on my Samsung s2 gt-i9100 device, I followed a lot of guides but still no luck.
the current situation is:
what iam trying to do is running streamline for ds-5 on the Samsung mobile to do that i had to crate gator,ko module and gatord deamon. I cratd both of them using Android 4.1.2 JB from Samsung website.
I had the kernal on mobile is 3.0.15-Siyah-s2v4.1.5+ Android 4.1.1 on my phone and the phone is rooted from inside the phone when i run a terminal in the phone it worked fine but when i try to use adb root from my computer it gives permission deny.
i tried to get the source code for the Siyah kernel to build the gator against it but no luck. i tried the repack-zImage.sh -u from http://forum.xda-developers.com/showthread.php?t=901152 to extract the source code but it still get me some errors"x32 vs x64 compatibility issue".
a next step as to try do is to load another android version so I used vanilla Root box. but like the first try I got the error when running the gatord
gator.ko must be built against the current version.
I can not use the source jb code to install it on the phone. odin do no support the file type "I have.tar.gz and they need .tar.md5"
I need advice on using source code for kernel to build gator then flush it to my phone.
any version would be fine as I need to test apps.
Thanks in dvance
Hi everyone!
I'm looking for help how to get Android Studio working with Androids Internal API.
There is a very good tutorial HERE that shows how to set everything up in Eclipse,
but since Eclipse is now deprecated and Google will be dropping support for ADT plugin
the logical move is to set everything up with Android Studio.
The things I did are pulling the boot.oat file from stock Nexus 5X, and use the standard procedure to get framework.jar and framework-classes2.jar.
After getting the internal packages out of the framework, I modified the android.jar file by adding all the missing packages.
The problem is even though all references, classes, interfaces and resources are there and the code doesn't give errors or warnings
that classes could not be found, the build still fails with messages like these:
Code:
error: package com.android.internal.R does not exist
com.android.internal.R.drawable.sym_app_on_sd_unavailable_icon);
...
cannot find symbol
mLocales = LocalePicker.constructAdapter(this);
...
Basicly, anything related to the internal API gives an error only when compiling.
My next idea is to build all the internal classes as a library and add it to the project where I need it,
but I wanted to ask does anyone else have any better ideas or suggestions?
I've done my googling but I haven't found anything recent and related to AS, only Eclipse.
Hello guys,
Last time I've built Android was about 2-3 years ago. It seems things have changed since then. Currently I'm on Mi 5S LOS-14.1, and I just tried to change SystemUI.apk with the one I compiled from source, but after reboot it rejects being started. Even I reverted it to stock one, but it still doesn't start. I'm not able to see logcat because adb says "error: insufficient permissions for device".
What is the point I'm missing?
I have this phone, I just found in a drawer from at least 5-6 years ago, from Virgin Mobile. When I go to the software upgrade from settings, it says it needs no update and it is currently in most up to date version, which is Android 2.2.1 (kernel ver 2.6.32.9 if relevant) .
I can not run Google Market app which came preloaded on this phone, it fails in 2-3 seconds.
All I need is to load IPwebcam app so that I can use it as a webcam on the room my cats stay and check who is pooping on the carpet (I know it is silly but I have more uses for IPwebcam afterwards, this is the first problem I am dealing with now)
Is there a way to update/upgrade the google market or is there a way to find an old version of this app and sideload it somehow ? It even doesn;t have to be this app. It just needs to function as a live camera feed and be able to run on android 2.2.1.
Any help is greatly appreciated.
I think that you'd better manage to update the system software from Android 2.2.1 to at least Android 8 or 9 at first. Then you will get any favorite apps installed on your device more easy.
James_Watson said:
I think that you'd better manage to update the system software from Android 2.2.1 to at least Android 8 or 9 at first. Then you will get any favorite apps installed on your device more easy.
Click to expand...
Click to collapse
The problem with that is there are no Oreo or Pie ROMs for their device and the hardware in the device they have will not support Oreo or Pie, even if they did find a way to build and flash an Oreo or Pie ROM on the device.
Sent from my SM-S767VL using Tapatalk
---------- Post added at 03:33 PM ---------- Previous post was at 03:27 PM ----------
TrueNomad said:
I have this phone, I just found in a drawer from at least 5-6 years ago, from Virgin Mobile. When I go to the software upgrade from settings, it says it needs no update and it is currently in most up to date version, which is Android 2.2.1 (kernel ver 2.6.32.9 if relevant) .
I can not run Google Market app which came preloaded on this phone, it fails in 2-3 seconds.
All I need is to load IPwebcam app so that I can use it as a webcam on the room my cats stay and check who is pooping on the carpet (I know it is silly but I have more uses for IPwebcam afterwards, this is the first problem I am dealing with now)
Is there a way to update/upgrade the google market or is there a way to find an old version of this app and sideload it somehow ? It even doesn;t have to be this app. It just needs to function as a live camera feed and be able to run on android 2.2.1.
Any help is greatly appreciated.
Click to expand...
Click to collapse
The most recent apps do not support 2.2.
The best you could possibly hope for is to download a copy of a more recent version of the app that you need, then use the Android SDK and APKTool to modify/port the app to work on 2.2. It may not even be possible or even worth it.
I suggest, put the device back in the drawer and leave it there because it is too old and does not have the proper hardware to support newer operating systems and apps. Similar to old computers not having proper support to run newer versions of Windows.
Sent from my SM-S767VL using Tapatalk