I have an apk application but it's not working on my mobile?
And I tried it to convert by following steps:
I downloaded an apk file on my computer.
then I converted it to jar by dex2jar?
but it didn't worked on my mobile and a message shows "Invalid file".
then I open it in jd-gui and then save it to src file.
then I open it but all file shows as .java file.
How to open it on my mobile?
How to convert it to .class?
My mobile name is: samsung gt-s3653
You can run Android applications on Android devices. You cannot run Android applications on JavaME devices.
Related
I have written code for an android application using ApacheCordova. Now i want to generate apk file from that source code inside an android smartphone. Is it possible ?
You can use Shareit. When you share your app through ShareIt, the shareit would generate .apk file and send to other user. Thus you get your .apk file.
Install this app and you can extract an apk file from an android application, click here
I'm building a game for mobile devices with corona sdk, it already run on iOS devices and now I want to install it on android device.
I'm trying to install my app on android device and because my app is large than 50mb, the corona split it into apk and obb files.
apk = 12mb,
obb = 130mb
I copied the both of files into my device and put the obb file under "sdcard/Android/obb/myPackagefolder" folder (according to some guides),
then I launch and install the apk.
now - when i'm trying to open my application it open the download page to try download the data (obb file) from google play and doesn't recognize the file I already put into the obb's folder.
I tried to run it on another devices and I get the same issue.
my build.settings contains the permission "WRITE_EXTERNAL_STORAGE"
my Q: is it even possible to do that ? and what I miss that cause my problem?
please help me, I spend a lot of time on it..
thanks
I address the file like this directly under the SD card and it wirks fine:
local fileName = "/sdcard/coordinates1.txt"
local doc_path = system.pathForFile( fileName )
local contents = doc_path:read( "*a" )
start with something like this and then use other folders.
I am trying to build my project in oculus gear vr using unity5 , but when I deploy my app I get the below error
thread priority security exception make sure the apk is signed
I have even created keystore
any suggestion why I might be facing this error in gear vr
I figure out the answer , to run apps in gear vr , you must have signature file for used device by get device id & use site below
https://developer.oculus.com/osig/
after you get the file , you should put inside your project in this directory
YourProjectName --- > assets --> Plugins ---> android ---> assets
(notice if you don't find this directory make sure your build platform
android , from build setting -- > switch platform)
then what you if you get this error
why this error happen ??
when I work in project I copy signature file with its meta file
so to fix error , just copy signature file without its meta file
UPDATED ANSWER
How you can get device id?
There many ways to approach that but best way to write in terminal
adb devices
You should see a list of attached devices like this:
List of devices attached
ce0551e7 device
or if you are lazy like me use this app its working very well it called
SideloadVR DeviceID
I solved this problem by following the steps as below,
Get the device ID using the adb.
For that, take the command prompt and type adb devices.
Ensure that adb path is added in the environment variables.
Also, you can use SideloadVR app to get the device ID.
Used the device ID to generate the oculus signature file using the service at https://developer.oculus.com/manage/tools/osig-generator/
Copy the signature file generated in step 2 at the following location in your unity project sub folder - Assets / Plugins / Android / assets (Create the folders if that do not exist).
Now build and Run the App on an Android Device.
For more: Oculus Signature File (osig) Generator
The above method didn't work for me, but I found that putting the signature file (osig) into "Project_Name/app/src/main/assets" does work. Within Android Studio you will see the file in your 'assets' folder too.
For example with the GearVRf Cockpit Demo, I put my osig file in:
GearVRf-Demos\gvr-cockpit\app\src\main\assets
Hi i'm new to android my client want to run the app in their on Android Device i go through the many answers through Stack overflow like this:-
How to make .apk file
How to build an APK file in Eclipse?
but i'm unable to make build.
I want to make a build of app in which is usually .apk extension and how i'm able to install this .apk file in my clients android device it doesn't have any eclipse or IDE.
Please suggest me the way or some links regarding this process to build and install the app in clients android device without using eclipse or any IDE.
Thanks in advance.
Eclipse create .apk file of your project by itself and save it in bin folder copy that apk file and send that to client and tell him to save apk on SD card and run directly from SD card. It will work.
the moment you run the app on the emulator or a device, the .apk file is created and put in /%YOUR PROJECT%/bin/app.apk
you can send that to your client...
I made an application and took the .apk file from the bin folder ( eclipse project ). I installed it on my mobile which i used as an emulator earlier and it worked just fine. However when i put the file on a friends mobile it said "cant open package" or something similar when i tried to install the application.
What could be wrong since it worked on mine? The API level was 10, so nothing fuzzy about that.
I've read something about keystore but i dont understand the meaning and function of em.
More than likely your friend phone doesn't accept unsigned packages.
You can either:
A. Sign you application
B. Enable untrusted instals on those phones via Settings > Applications > Unknown Sources
I had same problem.
Test if the size of copied APK file is same as size of file on your PC.
If they are not same, copy the APK file using a RAM reader to your PocketPC memory.