Database Users

Installing ROM on AVD

So, I don't like the stock AVD roms that exist in eclipse. FOr testing out apps so I don't have to screw with my phone, how do I go about installing a ROM to my AVD?

So nobody has any idea, even developers who work with roms and stuff every day that they do it? Please, can someone help?

Honestly, I think most devs here just screw with their phone rather than using a virtual one in Eclipse. At least I do

I guess you could unarchive the zip and then push system and data then reboot.

I don't know how to do that or else I would have... it took me forever to figure out that I can use adb to install apps to a virtual device.
Sent from my HERO200 using XDA App

[Q] Modifying Buil.prop for App Install

Hello there. I'm not new to the Android rooting scene but am brand new to Nook. My Nook came Wednesday night and it was rooted Thursday night. My main goal of root was to install an app (Moon+ Reader) that would give me reading statistics such as time till end of chapter and till end of book. My wifes Kindle has this feature and I want it now .
So Moon+ Reader has a min-SDK version of 8 (Android 2.2). I decompiled and built it using APKTool 1.5.2 changing the min-SDK version to 7; but the app will not install on my phone or the Nook. My next step is to modify build.prop setting 'ro.build.version.sdk=8.' Now, I've modified other parameters in build.prop, but never the sdk version. Will this have any adverse reactions for the Nook? In my mind it will be fine and if the app installs and doesn't function I can uninstall the app and restore the backup of build.prop. Am I crazy here, is there another app that keeps track of statisticts? I've tried Kindle, but it did not work.
--
Mooney

JMooney5115 said:
... the app will not install on my phone or the Nook.
Click to expand...
Click to collapse
Well, why don't you find out what the problem is?
What does your logcat say?
Changing build.prop doesn't make much sense.

I may have misrepresented myself in my OP. The problem in question here is not the install of the modified APK, rather the modifying of the build.prop and the troubles (if any) associated with changing the min-SDK. Sorry I posted a thread on this because I have moved past getting this app working.

JMooney5115 said:
I may have misrepresented myself in my OP. The problem in question here is not the install of the modified APK, rather the modifying of the build.prop and the troubles (if any) associated with changing the min-SDK. Sorry I posted a thread on this because I have moved past getting this app working.
Click to expand...
Click to collapse
I just tried changing the minsdk in build.prop on my HTC One to try and install an 'incompatible app' and now I'm in a bootloop. Need to wait til I get home from work now to fix it.
Doh!

Android checks for incompatibilities between system version and app minimal required version.
Obviously, to make these congruent you can change either one.
The thing is, this will only have any utility if the app maker overestimated the level of API that they are using.
If an app is using Jellybean introduced API features no amount of lying is going to get that app to work.
So if you still want to play with lying about versions, do yourself a favor and modify the app, not the system.

App Problem

*Not sure if in proper section, move if need be*
Noob here so try to dumb things down for me!
Ok, so I followed this tut HERE.
I was able to debug it to my android for testing and it worked. So I exported it as .apk and uploaded it to 4shared.com.
Now my problem is, after downloading to my phone, I went to [Install Package] and it said "Application not installed"
What would be the problem and how would I go about fixing it?
Thanks in advance
~Brine

How are you trying to install the app:
connect your device using USB cable to the comp. and run
Code:
adb install <path_to_apk>
on a terminal
Make sure that the app is not already installed as there could be certificate conflicts it a debug version is installed already. If some version is already installed, just uninstall it and try.
Also try enabling Settings > Security > Unknown sources (turn it off after you are done if you are not sure)

dh41196 said:
*Not sure if in proper section, move if need be*
Noob here so try to dumb things down for me!
Ok, so I followed this tut HERE.
I was able to debug it to my android for testing and it worked. So I exported it as .apk and uploaded it to 4shared.com.
Now my problem is, after downloading to my phone, I went to [Install Package] and it said "Application not installed"
What would be the problem and how would I go about fixing it?
Thanks in advance
~Brine
Click to expand...
Click to collapse
The app not installed errors show up when you try to install an app not ment for your device
Genral cases are
It requires hardware not present in your device
It is trying to replace a system app like systemui
etc..........
Sent from my GT-S5302 using Tapatalk 2

Have you tried to zipalign your apk? It may help

If you have another version of the app remove it and install this
Sent from my GT-S5360 using Tapatalk 2

[Q] Writing an app, works in emulator, crashes on device

Hi Folks, Hopefully this is the right place for this thread. I don't get over here very often so I'm guessing right now.
I wrote an app for my phone (Sprint Galaxy SIII) in Eclipse to control a IOIO (not terribly important to know for this question). I run the app in the emulator and it fires up just fine, but when I run it on my phone (with supposedly the same settings as the emulator--Android version, AP level, etc) it crashes on startup, saying "Unfortunately, <My App> has stopped".
Since it works in the emulator I can't track LogCat to check for errors, so I have no idea where to start looking for the cause. It only crashes on my actual device. My questions are as follows:
1) What would cause an app to work in the emulator but fail to start up in a device with (supposedly) the same settings?
2) Where can I go to look for errors on my phone (if possible) that might point me to the problem?
Thanks!
Matt

DerStrom8 said:
Hi Folks, Hopefully this is the right place for this thread. I don't get over here very often so I'm guessing right now.
I wrote an app for my phone (Sprint Galaxy SIII) in Eclipse to control a IOIO (not terribly important to know for this question). I run the app in the emulator and it fires up just fine, but when I run it on my phone (with supposedly the same settings as the emulator--Android version, AP level, etc) it crashes on startup, saying "Unfortunately, <My App> has stopped".
Since it works in the emulator I can't track LogCat to check for errors, so I have no idea where to start looking for the cause. It only crashes on my actual device. My questions are as follows:
1) What would cause an app to work in the emulator but fail to start up in a device with (supposedly) the same settings?
2) Where can I go to look for errors on my phone (if possible) that might point me to the problem?
Thanks!
Matt
Click to expand...
Click to collapse
Only log could tell you the possible reasons.
Install catalog and look for the error log
Sent from my A0001 using Tapatalk 2

Vivek_Neel said:
Only log could tell you the possible reasons.
Install catalog and look for the error log
Sent from my A0001 using Tapatalk 2
Click to expand...
Click to collapse
Thanks Vivek_Neel. I tried a couple of log viewer apps but they all require superuser access for use on Android 4.1+. I forgot to add it to my profile, but I currently have a Galaxy SIII running Android 4.4.2.
Any other suggestions? I'd rather not root my phone if I don't have to.
Thanks,
Matt

DerStrom8 said:
Thanks Vivek_Neel. I tried a couple of log viewer apps but they all require superuser access for use on Android 4.1+. I forgot to add it to my profile, but I currently have a Galaxy SIII running Android 4.4.2.
Any other suggestions? I'd rather not root my phone if I don't have to.
Thanks,
Matt
Click to expand...
Click to collapse
Running the app on your phone with it plugged in to a pc and eclipse open should mean that eclipse catches the log, no root access needed, you would need to allow adb debugging though. If it doesn't work with eclipse I know for definite that it works with Android Studio.

Jonny said:
Running the app on your phone with it plugged in to a pc and eclipse open should mean that eclipse catches the log, no root access needed, you would need to allow adb debugging though. If it doesn't work with eclipse I know for definite that it works with Android Studio.
Click to expand...
Click to collapse
Eclipse doesn't seem to recognize my phone. It only brings up the emulator as an available device. Perhaps I should dig more into the cause of that first. You're saying if I load the app on my phone while connected to the PC it'll still show up in the logcat? That would be a huge help if that's the case!

DerStrom8 said:
Eclipse doesn't seem to recognize my phone. It only brings up the emulator as an available device. Perhaps I should dig more into the cause of that first. You're saying if I load the app on my phone while connected to the PC it'll still show up in the logcat? That would be a huge help if that's the case!
Click to expand...
Click to collapse
It should do - worked this way around a year ago when I was using eclipse myself before jumping ship to AS.

You might want to handle uncaught exceptions and either debug, write to a file or what ever is the best way for you.
You can see an implementation example for handling uncaught exceptions here: http://stackoverflow.com/questions/8943288/how-to-implement-uncaughtexception-android.
Please note that some crashes are not caught using this technique so you'll need to use the above mentioned methods to view logcat.
If you have root on your device, install a logcat viewer application. most likely that filtering the display by your package name (or parts of it) we'll lead you to the error cause.

Thanks everyone for the help, I have found the solution. Eclipse wasn't recognizing my phone because apparently the driver was no longer installed (I thought I had installed it a long time ago, but that must have been on my laptop--I'm on my desktop now). I installed it and Eclipse found the phone no problem. I loaded the app while watching LogCat and found the following:
java.lang.SecurityException: Need BLUETOOTH permission: Neither user 10211 nor current process has android.permission.BLUETOOTH.
Click to expand...
Click to collapse
Well that was embarrassing! Added the Bluetooth permissions to the app et voila! The app works just fine.
Thanks for your time!
Matt

DerStrom8 said:
Thanks everyone for the help, I have found the solution. Eclipse wasn't recognizing my phone because apparently the driver was no longer installed (I thought I had installed it a long time ago, but that must have been on my laptop--I'm on my desktop now). I installed it and Eclipse found the phone no problem. I loaded the app while watching LogCat and found the following:
Well that was embarrassing! Added the Bluetooth permissions to the app et voila! The app works just fine.
Thanks for your time!
Matt
Click to expand...
Click to collapse
:laugh::laugh:
Haha glad you got it sorted!

Clone Apk issues

Hi, I am trying to clone a few games so myself and some friends can run multiple instances for different accounts. I am fairly new to android programming so sorry if this is a noob question. I am using APK Multi-Tool to decompile, edit with notepad++, then recompile and sign with APK Multi-Tool. The problem I face is after the cloned apk is installed it starts then immediately closes. No message appears i.e force closing message. I have used lucky patcher to clone the app and it did work but I would rather make my own and learn a little. I also tried using APK studio but was unable to even get it to decompile as the button stayed grayed out. I am running windows 10, sgh-m919 and cyanogenmod 12.1. Any help will be much appreciated.

I'm fairly new to Android itself, so this might be a noob answer, but I think that means the apk is corrupted.
Sent from my BN Nook HD using Tapatalk

Could it be a compile thing?