Database Develop

How to launch an application from Terminal?

Hi guys,
I want to know how to launch an application installed in my Android from command line?
In windows, for example, exists "start" command:
Code:
C:\>start notepad.exe
It Starts notepad application.
Exists something like that in Android?
Thanks in advance.

tolemac said:
Hi guys,
I want to know how to launch an application installed in my Android from command line?
In windows, for example, exists "start" command:
Code:
C:\>start notepad.exe
It Starts notepad application.
Exists something like that in Android?
Thanks in advance.
Click to expand...
Click to collapse
there is a way of doing it, but its a lot more complicated lol .. lemme look for a link
actually i cant find it right now lol but i know it has to do with the "am" command and intents
yup just tried the am command and it tells you how to use it ... hope i pointed you in the right direction

Yeah!!
Thanks xidominicanoix, searching "android am start" I have found this:
http://learnandroid.blogspot.com/2008/01/run-android-application-from-command.html
The sintax (resumed for this case) is:
Code:
am start -a android.intent.action.MAIN -n package/class_fullname
Example:
Code:
am start -a android.intent.action.MAIN -n my.domain.myApp/my.domain.myApp.myClass
Now, I´m trying to launch this as root with from Java with:
Code:
process = Runtime.getRuntime().exec("su");
os = new DataOutputStream(process.getOutputStream());
os.writeBytes("am start -a android.intent.action.MAIN -n my.domain.myApp/my.domain.myApp.myClass"+"\n");
os.writeBytes("exit\n");
os.flush();
The application start but don´t have root permissions :/
Any idea?

I suppose that "am start" command send some signal to other process to launch this application and the other process don´t have root permissions.
Other way?
Thank you so much.

tolemac said:
Yeah!!
Thanks xidominicanoix, searching "android am start" I have found this:
http://learnandroid.blogspot.com/2008/01/run-android-application-from-command.html
The sintax (resumed for this case) is:
Code:
am start -a android.intent.action.MAIN -n package/class_fullname
Example:
Code:
am start -a android.intent.action.MAIN -n my.domain.myApp/my.domain.myApp.myClass
Now, I´m trying to launch this as root with from Java with:
Code:
process = Runtime.getRuntime().exec("su");
os = new DataOutputStream(process.getOutputStream());
os.writeBytes("am start -a android.intent.action.MAIN -n my.domain.myApp/my.domain.myApp.myClass"+"\n");
os.writeBytes("exit\n");
os.flush();
The application start but don´t have root permissions :/
Any idea?
Click to expand...
Click to collapse
would
Code:
os.writeBytes("su");
right after you initialize os work?

humn??
This code:
Code:
process = Runtime.getRuntime().exec("su");
Do it.
Thanks,

When using "su" in linux, when one attempts to execute a command as root, the proper invocation is as follows:
Code:
su -c "[[b]COMMAND GOES HERE[/b]]"
Might help you.
In this case; you'd want:
Code:
os.writeBytes("su -c 'am start -a android.intent.action.MAIN -n my.domain.myApp/my.domain.myApp.myClass'"+"\n");
That ought to do it, IF I understand this correctly. IANAP.

Thanks IConrad01, I will try it as soon as possible.

Thanks other time IConrad01, I have tried your command.
1) I have created an Android application called TestBackup that try to write a simple file on startup in this path: /system/bin/hello.txt
2) I have ran the application in my device and I get a normal exception:
Code:
(new File("/system/bin/hello.txt")).createNewFile();
java.io.IOException: Parent directory of file is not writable: /system/bin/hello.txt
3) I have opened an "adb shell" shell and I have ran this commands:
Code:
# busybox mount -o rw,remount /system
busybox mount -o rw,remount /system
# su -c 'am start -a android.intent.action.MAIN -n org.jros.TestBackup/org.jros.TestBackup.Test'
su -c 'am start -a android.intent.action.MAIN -n org.jros.TestBackup/org.jros.TestBackup.Test'
Starting: Intent { act=android.intent.action.MAIN cmp=org.jros.TestBackup/.Test }
# busybox mount -o ro,remount /system
busybox mount -o ro,remount /system
The application started but don´t have root permissions (I think), this is the LogCat from "am start":
Code:
11-05 13:21:32.082: DEBUG/su(1175): 0:0 /system/bin/sh executing 0:0 am start -a android.intent.action.MAIN -n org.jros.TestBackup/org.jros.TestBackup.Test
11-05 13:21:32.462: DEBUG/AndroidRuntime(1176): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
11-05 13:21:32.462: DEBUG/AndroidRuntime(1176): CheckJNI is OFF
11-05 13:21:32.642: DEBUG/AndroidRuntime(1176): --- registering native functions ---
11-05 13:21:32.672: INFO/jdwp(1176): received file descriptor 30 from ADB
11-05 13:21:32.842: INFO/BluetoothOppService.cpp(1176): register_android_server_BluetoothOppService
11-05 13:21:32.872: DEBUG/ddm-heap(1176): Got feature list request
11-05 13:21:33.202: INFO/ActivityManager(129): Starting activity: Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=org.jros.TestBackup/.Test }
11-05 13:21:33.232: DEBUG/AndroidRuntime(1176): Shutting down VM
11-05 13:21:33.242: DEBUG/dalvikvm(1176): DestroyJavaVM waiting for non-daemon threads to exit
11-05 13:21:33.242: DEBUG/dalvikvm(1176): DestroyJavaVM shutting VM down
11-05 13:21:33.242: DEBUG/dalvikvm(1176): HeapWorker thread shutting down
11-05 13:21:33.242: DEBUG/dalvikvm(1176): HeapWorker thread has shut down
11-05 13:21:33.242: DEBUG/jdwp(1176): JDWP shutting down net...
11-05 13:21:33.242: DEBUG/jdwp(1176): +++ peer disconnected
11-05 13:21:33.242: INFO/dalvikvm(1176): Debugger has detached; object registry had 1 entries
11-05 13:21:33.262: DEBUG/dalvikvm(1176): VM cleaning up
11-05 13:21:33.272: ERROR/AndroidRuntime(1176): ERROR: thread attach failed
11-05 13:21:33.302: INFO/ActivityManager(129): Process com.android.vending (pid 1046) has died.
11-05 13:21:33.332: ERROR/Error Test SU(1072): Parent directory of file is not writable: /system/bin/hola.txt
11-05 13:21:33.332: WARN/System.err(1072): java.io.IOException: Parent directory of file is not writable: /system/bin/hola.txt
11-05 13:21:33.342: WARN/System.err(1072): at java.io.File.createNewFile(File.java:1208)
11-05 13:21:33.342: WARN/System.err(1072): at org.jros.TestBackup.Test.TestSU(Test.java:32)
11-05 13:21:33.342: WARN/System.err(1072): at org.jros.TestBackup.Test.onCreate(Test.java:24)
11-05 13:21:33.352: WARN/System.err(1072): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123)
11-05 13:21:33.352: WARN/System.err(1072): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2364)
11-05 13:21:33.352: WARN/System.err(1072): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2417)
11-05 13:21:33.352: WARN/System.err(1072): at android.app.ActivityThread.access$2100(ActivityThread.java:116)
11-05 13:21:33.352: WARN/System.err(1072): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1794)
11-05 13:21:33.362: WARN/System.err(1072): at android.os.Handler.dispatchMessage(Handler.java:99)
11-05 13:21:33.362: WARN/System.err(1072): at android.os.Looper.loop(Looper.java:123)
11-05 13:21:33.362: WARN/System.err(1072): at android.app.ActivityThread.main(ActivityThread.java:4203)
11-05 13:21:33.362: WARN/System.err(1072): at java.lang.reflect.Method.invokeNative(Native Method)
11-05 13:21:33.362: WARN/System.err(1072): at java.lang.reflect.Method.invoke(Method.java:521)
11-05 13:21:33.362: WARN/System.err(1072): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
11-05 13:21:33.372: WARN/System.err(1072): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
11-05 13:21:33.372: WARN/System.err(1072): at dalvik.system.NativeStart.main(Native Method)
11-05 13:21:33.372: DEBUG/dalvikvm(1176): LinearAlloc 0x0 used 685236 of 4194304 (16%)
11-05 13:21:33.442: INFO/ActivityManager(129): Displayed activity org.jros.TestBackup/.Test: 218 ms (total 218 ms)
Perhaps is impossible to start an application with root permissions.
I don´t now.
And you?
what are you think about?
Thanks in advance.

What you are asking for makes no sense.
The user who starts an android application has nothing to do with the user who the application RUNS AS.
Whether you use "am start" or click on the button, the SAME THING HAPPENS -- the user who runs the application is the user assigned to THAT application by the PACKAGE MANAGER.
am start does NOT start the application. It sends an INTENT that the application is *to be* started.
If you want your application to have root access, you need to gain root access *from within* that application, and having root access is restricted to executing SHELL COMMANDS.

Thank you very much lbcoder.
I suppose this.
Ok, while I have been trying it I have learned other things, doesn´t loss time
Thank you so much.

Is there any way to work out what package/class_fullname is for specific apps? I want to autostart my IM program at boot (Nimbuzz) - how would I go about determining a command line for it?

I guess everyone forgot to mention that this is in the wrong section?
-.-

Start Android app from terminal
So when I start
Code:
am start -a android.intent.action.MAIN -n my.domain.myApp/my.domain.myApp.myClass
e.g.
Code:
am start -a android.intent.action.MAIN -n com.google.browser/com.google/browser
will start the standard browser ? As I only have a root terminal (via ssh using SSHDroid) does this mean that the apps are started as root ?
I prefer them starting normally except for root specific apps like vnc server.
When I try this I get errors.
Code:
pocketpenguin:~ #am start -n com.google.android.contacts/.ContactsActivity
Starting: Intent { cmp=com.google.android.contacts/.ContactsActivity }
Error type 3
Error: Activity class {com.google.android.contacts/com.google.android.contacts.ContactsActivity} does not exist.
pocketpenguin:~ #
Does somebody know this ?

mermaidkiller said:
Does somebody know this ?
Click to expand...
Click to collapse
Um:
Code:
# am start -a android.intent.category.DEFAULT -n com.android.contacts/com.android.contacts.DialtactsContactsEntryActivity
For your contact list (in the aosp gingerbread contacts apk anyway), read the AndroidManifest for othe links, or cortect names in other versions of the apk.
Of course to open a page in your default browser try:
Code:
# am start -a android.intent.action.VIEW http://www.google.com/

Thanks anywY, but how can I start any app from the command line ?

Is there any way at all to run Java code as root, maybe by exec'ing the dalvikvm itself?
==EDIT==
Nevermind, I got it.

I can understand the command but may I know how to find out the exact folder or com description for the app that I intend to start at command-line ? for example, let's say I wish to start the FIREFOX browser, can someone show me how to find out the com description to use in the command line and give me an example of the command line. Thank you in advance.

cd /data/app
ls
cd /system/app
ls
Etc etc
Sent from my Nexus 4 using XDA Premium 4 mobile app

Launch an Application from Terminal
You dont need to know the location of the app on the phone. However you need to know the package name (application name) and various activities in the app. Basically if you intend to just launch the app then you need yo know the main activity that triggers the application to start. So suppose that your package name is, com.mozilla.firefox and the start activity is say MainActivity. Then you can launch the app from terminal with su privilage with following command,
Code:
am start -n com.mozilla.firefox/.MainActivity
Thats it.
Coming to knowing the package name for your application, use
Code:
pm list packages
And if you want know the location of the apk, use
Code:
pk list packages -f
And if you intend to know names of the third party apps installed only use
Code:
pm list packages -3 -f
Now to know various activities in an app, see the AndroidManifest.xml. You will see names of activities. Most probably the first activity is the start activity ie., MainActivity.
To see the contents of androidManifest.xml you need to extract it from apk file. Online tools are available to do so.
Hope this helps.
sent from my huewei honor 4x

Help devs and add a LOGCAT next to your BUG report

Hi there.... yeah, Im a newb too in this business, but the only one thing that I know, that the DEVS gett pissed off when we report bugs without LOGCATs
We dont understand it but they do SO LETs hear them and do it like we should do it.
Every time when you get into the thread and post something like "aaaaaa, the power button doesent work, or Play Store wont open...", this is just a cup of crapy words for the devs (correct me if Im wrong).
Of course theres a ADB version for doing logs, but I think for the START, this one is just fine.
Click to expand...
Click to collapse
What is logcat?
Logcat is the command to view the internal logs of the Android system. Viewing logs is often the best way to diagnose a problem, and is required for many issues. This way you'll find out what apps are doing in the background without you noticing.
Advantages of Logcat
Debugging
Debug your apps. Find error stacktraces. See what your phone is saying about you behind your back. It's all there in the system log, aka logcat!
Click to expand...
Click to collapse
DOWNLOAD APP
I was googleing around and I found the best app for doing it for us newbs.
Download the FREE app called CATLOG.
Click to expand...
Click to collapse
HOW TO USE IT
After you installed it, RUN it and click the options button, there youll get a record options. Click on the record button and let it run in the background. If you had problems with Play Store, just run the PS again and when the ERROR comes, the CATLOG recorder is recording. After you did that, just go back to the app, hit the options key and press STOP RECORDING. There you GO, you have a .txt catlog of your problem.
This is just a example with the PLAY STORE fc...
Use some file manager or something like that so you can go into your sdcard / catlogs / and there should be your TXT saved log. Now just select it, press on share and put it on the FORUM or the DEVs mail. It depends on each developer. (Correct me again if Im wrong.)
Click to expand...
Click to collapse
Hope it helps out!
DO IT PEOPLE !

Heres is the more advanced but not so hard way to LOGCAT!
All credits goes to paxChristos who made this awesome tutorial HOW TO LOGCAT!
Original post: http://forum.xda-developers.com/showthread.php?t=1726238
paxChristos said:
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Click to expand...
Click to collapse

Adding some LogCats for CM10 nightly
Powerbutton
http://forum.xda-developers.com/showpost.php?p=33593548&postcount=1130
no sound - poor in/out sound on CALLs
http://forum.xda-developers.com/showpost.php?p=33630013&postcount=1395
blinking screen on "screen off"
http://forum.xda-developers.com/showpost.php?p=33629455&postcount=1391
Hope it helps!

Good thread.
My favourite app for logs on the go is Lumberjack.
For logcatting at the PC I think "adb logcat" via cmd / terminal is better than an app (see torq1337's second post).
What's important: A normal logcat can be useless in some cases.
For audio, calls and anything else radio related you should add a radio logcat as well. (adb logcat -b radio).
If you got a bsod, kernel panic, or sth else that results in a bsod or phone restarting than you should post the last_kmsg.
Get it with Lumberjack or manually in the Terminal by typing "su" and "cat /proc/last_kmsg > /sdcard/last_kmsg.txt"

Dont forget to logcat

I updated my previous post now.
I am posting again to push this thread as I personally belive that most people are unable to do so because that some people out there in our nation don't have maps and that I belive that our education people who are flashing custom ROMs should know how to give developers some valid feedback - and you can learn how to logcat in 5 minutes.

tonyp said:
I updated my previous post now.
I am posting again to push this thread as I personally belive that most people are unable to do so because that some people out there in our nation don't have maps and that I belive that our education people who are flashing custom ROMs should know how to give developers some valid feedback - and you can learn how to logcat in 5 minutes.
Click to expand...
Click to collapse
Im gonna cry xDxDxDxD
Sent from my LG-P990 using xda app-developers app

Hi, maybe you would like to include my tool as well, AIOlog, as it not only logs logcat(with the -b radio for radio issues as well), but dmesg, kmsg and last_kmsg as well

tonyp said:
If you got a bsod, kernel panic, or sth else that results in a bsod or phone restarting than you should post the last_kmsg.
Get it with Lumberjack or manually in the Terminal by typing "su" and "cat /proc/last_kmsg > /sdcard/last_kmsg.txt"
Click to expand...
Click to collapse
What /proc/last_kmsg? (It doesn't appear to exist, on my phone at least.)

withoutwings said:
What /proc/last_kmsg? (It doesn't appear to exist, on my phone at least.)
Click to expand...
Click to collapse
It would be removed in a restart but still, you can retrieve the /proc/kmsg instead(better than none, I suppose, just more work for the devs )

wcypierre said:
It would be removed in a restart but still, you can retrieve the /proc/kmsg instead(better than none, I suppose, just more work for the devs )
Click to expand...
Click to collapse
No, /proc/kmesg is reset upon a restart. The whole point of last_kmesg is in the case of a crash, it is there upon the next boot so you can find out what happened. But on CM10 it doesn't appear to exist. I read somewhere this could mean the RAM Console isn't set up properly?

Read-only file system on Virtual Device

I am trying to get a simple "Hello World" app running in Android Studio but am having a surprising amount of trouble. My current issue seems to be that Android Studio is unable to write to the virtual device. Although my virtual device takes a long time to start up it does eventually get going and seems to present as 'working'.
The output for the device in the "Run" windows shows:
C:\Users\Slarti\AppData\Local\Android\sdk\tools\emulator.exe -netdelay none -netspeed full -avd Nexus_5_API_23_x86
emulator: device fd:928
HAXM is working and emulator runs in fast virt mode
creating window 43 59 329 583
emulator: emulator window was out of view and was recentered
emulator: UpdateChecker: skipped version check​However the output in the "app" log of the "Run" window reads:
Target device: Nexus_5_API_23_x86 [emulator-5554]
Installing APK: C:\Users\Slarti\Documents\...
Uploading file to: /data/local/tmp/...
com.android.ddmlib.SyncException: Read-only file system​
and the "Event Log" shows:
2:01:53 PM Gradle sync started
2:04:30 PM Gradle sync completed
2:04:35 PM Executing tasks: [:app:generateDebugSources, :app:generateDebugAndroidTestSources]
2:04:56 PM Gradle build finished in 25s 136ms
2:10:33 PM Unable to obtain result of 'adb version'
2:11:03 PM Executing tasks: [:app:assembleDebug]
2:11:40 PM Gradle build finished in 36s 851ms
2:11:43 PM transfer error: Read-only file system
2:11:43 PM Error during Sync: Read-only file system​
I've spent a lot of time searching for a solution for this, including re-installing Android Studio but I still keep having the same problem. Does anyone know what could be causing this and how I can fix it? The program itself is a very simple "Hello World!" program and I have left most things in Android Studio at their default values but clearly something somewhere must be set incorrectly. Any ideas as to what it could be?
Thanks for any help,
Slarti.

LG G3 F460 - Marshmallow - dex2oat ~ permission denied

Installed the latest v86 framework, then the stock camera app force closes.
Find the problem in logcat:
Code:
08-15 15:36:19.656 I/ActivityManager(2429): Start proc 29745:com.lge.camera/u0a22 for activity com.lge.camera/.CameraAppLauncher
08-15 15:36:19.807 E/dex2oat (29758): Failed to create oat file: /data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex: Permission denied
08-15 15:36:19.810 W/art (29745): Failed execv(/system/bin/dex2oat --runtime-arg -classpath --runtime-arg /system/framework/XposedBridge.jar --instruction-set=arm --instruction-set-features=smp,-div,-atomic_ldrd_strd --runtime-arg -Xnorelocate --boot-image=/system/framework/boot.art --runtime-arg -Xms64m --runtime-arg -Xmx512m --instruction-set-variant=krait --instruction-set-features=default --dex-file=/system/priv-app/LGCameraApp/oat/arm/LGCameraApp.odex --oat-file=/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex) because non-0 exit status
08-15 15:36:19.812 W/art (29745): Falling back to interpreting /system/priv-app/LGCameraApp/oat/arm/LGCameraApp.odex
08-15 15:36:19.813 W/System (29745): ClassLoader referenced unknown path: /system/priv-app/LGCameraApp/lib/arm
The .dex file and the path /system/priv-app/LGCameraApp/lib/arm do exist.
I would like to solve this badly cause it seems like it's one of the apps that optimize everytime the phone bootup!

@rovo89 may help you. You should report bug on Github https://github.com/rovo89/XposedBridge/issues

pyler said:
@rovo89 may help you. You should report bug on Github https://github.com/rovo89/XposedBridge/issues
Click to expand...
Click to collapse
thx plyer for the hint : )

Hi, please let me know if the problem was already fixed. I have the same problem.

How to call apktool (dalvikvm) in a magisk module?

Hello,
I'm currently trying to run apktool using dalvikvm in the customize.sh script:
Bash:
apktool_d() {
#ANDROID_DATA=$TMPDIR_JCD ANDROID_ROOT=/system LD_LIBRARY_PATH=/system/lib dalvikvm -Xbootclasspath:/system/framework/core.jar:/system/framework/conscrypt.jar:/system/framework/apache-xml.jar -classpath $BIN/apktool_*-dexed.jar brut.apktool.Main d --frame-path $TMPDIR_JCD/framework --no-src -o $TMPDIR_JCD/resout $1
dalvikvm -classpath $BIN/apktool_*-dexed.jar brut.apktool.Main d --no-src -o $TMPDIR_JCD/resout $1
test $? != 0 && abort "Decoding APK resources failed. Aborting..."
}
I've tried to port that code from an outdated template: https://github.com/djb77/magisk-module-template-apkpatcher
When using the commented out method the command aborts with "Decoding APK resources failed" and logcat *:E is telling me the following:
Code:
04-17 21:11:53.649 11641 11641 E dalvikvm: Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Unexpected component count in /system/framework/arm/boot.art, received 11, expected non-zero and <= 3
04-17 21:11:53.677 11641 11641 E dalvikvm: Could not initialize without image: Boot classpath is empty.
When trying the second approach without -Xbootclasspath and so on I'm getting a NullPointerException directly in the magisk log (saved file):
Code:
I: Using Apktool 2.3.4 on Bluetooth.apk
I: Loading resource table...
I: Decoding AndroidManifest.xml with resources...
Exception in thread "main" java.lang.ExceptionInInitializerError
at brut.util.OSDetection.isMacOSX(OSDetection.java:28)
at brut.androlib.res.AndrolibResources.getFrameworkDir(AndrolibResources.java:913)
at brut.androlib.res.AndrolibResources.getFrameworkApk(AndrolibResources.java:754)
at brut.androlib.res.AndrolibResources.loadFrameworkPkg(AndrolibResources.java:116)
at brut.androlib.res.data.ResTable.getPackage(ResTable.java:84)
at brut.androlib.res.data.ResTable.getResSpec(ResTable.java:67)
at brut.androlib.res.data.ResTable.getResSpec(ResTable.java:63)
at brut.androlib.res.decoder.ResAttrDecoder.decode(ResAttrDecoder.java:39)
at brut.androlib.res.decoder.AXmlResourceParser.getAttributeValue(AXmlResourceParser.java:385)
at org.xmlpull.v1.wrapper.classic.XmlPullParserDelegate.getAttributeValue(XmlPullParserDelegate.java:69)
at brut.androlib.res.decoder.XmlPullStreamDecoder$1.parseManifest(XmlPullStreamDecoder.java:97)
at brut.androlib.res.decoder.XmlPullStreamDecoder$1.event(XmlPullStreamDecoder.java:65)
at brut.androlib.res.decoder.XmlPullStreamDecoder.decode(XmlPullStreamDecoder.java:141)
at brut.androlib.res.decoder.XmlPullStreamDecoder.decodeManifest(XmlPullStreamDecoder.java:153)
at brut.androlib.res.decoder.ResFileDecoder.decodeManifest(ResFileDecoder.java:155)
at brut.androlib.res.AndrolibResources.decodeManifestWithResources(AndrolibResources.java:204)
at brut.androlib.Androlib.decodeManifestWithResources(Androlib.java:136)
at brut.androlib.ApkDecoder.decode(ApkDecoder.java:122)
at brut.apktool.Main.cmdDecode(Main.java:164)
at brut.apktool.Main.main(Main.java:73)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.lang.String.toLowerCase()' on a null object reference
at brut.util.OSDetection.<clinit>(OSDetection.java:21)
... 20 more
Decoding APK resources failed. Aborting...
! Installation failed
After some research I tried to find out if the customize.sh is running as root because some posts telling that setting LD_LIBRARY_PATH setting as root fixed those "Could not create image space" dalvikvm errors but can't find any info about that. see https://github.com/termux/termux-packages/issues/900#issuecomment-322207233
I'm out of ideas and happy for any help.
Thanks in advance
Danny.