I am able to run a shell script on the Mac command line, but when I call it in Android Studio java it fails with this error:
GenerateActivity::THE COMMAND=[./go.top-level, Sweden]
java.io.IOException: Cannot run program "./go.top-level" (in directory "/data/user/0/com.example.frontpage/files/scripts"): error=13, Permission denied
My java code to call the script is as follows:
dir = lcontext.getFilesDir(); //lcontext is passed into this procedure
File workingDirectory = new File(dir + "/scripts/");//go.top-level is in /scripts dir
List<String> command = new ArrayList<String>();
command.add("./go.top-level"); // command
command.add(country); // command
System.out.println(TAG + "THE COMMAND=" + command.toString());
// creating the process
ProcessBuilder pb = new ProcessBuilder(command);
pb.directory(workingDirectory);
try {
pb.start(); //pb.wait() errors out indicating need a lock and a thread.....
} catch (Exception e) {
e.printStackTrace();
}
The process is failing immediately in the java. But, when I run it at the command line, i.e., via:
%./go.top-level Sweden (in /scripts dir)
it works, although it takes a couple of minutes. (note: I do "run-as com.example.frontpage" before running). The java seems logical to me since I set the workingDirectory appropriately. Also the /scripts folder and all of the files in it as well as the other folders used in this code are set to 777 permissions dynamically in the code. Why doesn't the error say, "./go.top-level Sweden" since the script call takes one argument? What am I missing here as far as this permission error? Is pb.start() a bad idea since the execution takes on the order of minutes? But when I try pb.wait() I get a different error indicating I need a lock and a thread. If that is best can someone indicate how best to do that?
TIA
I cannot find the file I created in my android app in Android File Transfer under /Android/data. My goal is to copy/edit a config file to the app data folder while I develop the app, and then later link it to a Google Drive file. But, even when I write a file in the app with the following:
FileOutPutStream outputStream;
try {
outputStream = mAppContext.openFileOutput("my_config.json", Context.MODE_WORLD_WRITABLE);
outputStream.write("test".getBytes());
outputStream.close();
Log.d("WRITE", "FILE WRITTEN!");
catch (Exception e) {
e.printStackTrace();
}
I get the debug log message the the file was written, but I cannot find it in Android File Transfer (there isn't even a directory for my app). I have also tried cd-ing into it from adb shell, as well as rebooting the device. What is the best way to quickly transfer a file into and out of an app directory? I am running 4.4.2 Kit Kat.
I'm currently looking for a way to update an android application without starting the installation intent.
Please note, the device is rooted
If it's possible I would just like to start the installation automated without notifying the user(automated APK installation).
If that is not an option I would like to unpack the APK, compile it myself and write it to the app's data directory.
Is there a way to achieve this?
Thanks in advance
you can try this
try {
Runtime.getRuntime().exec("su");
Runtime.getRuntime().exec("pm install /mnt/sdcard/tr.apk");
} catch (IOException e) {
e.printStackTrace();
}
but this requires system permission and
android:name="android.permission.INSTALL_PACKAGES"
while programming android with eclipse, no matter if you're using the emulator or a device connected in debug mode you can easily check the Log for looking at the custom messages that you wrote.
e.g.: Log.i("foo: " + foo);
With the method:
Titanium.API.info("foo: " + foo);
if i'm using the emulator it all works fine, but if i'm deploying on the device is there a way of looking at the INFO?? with TiStudio or even TiDev
Thanks
You can use adb from the android SDK tools directory to see your Titanium Titanium.API.info calls:
tools/adb logcat | grep "TiAPI"
This will filter the adb log, giving you a cleaner view of only your log messages.
You can see logcat from the current device. Enable debug mode on the device, and connect it to the computer.
Then, if using eclipse, on the DDMS view on Devices select the device you want and the LogCat will show logs from it.
You can also see with this app the logs:
https://market.android.com/details?id=org.jtb.alogcat
Or save them to file:
try {
File filename = new File(Environment.getExternalStorageDirectory()
+ "/logfile.txt");
filename.createNewFile();
String[] cmd = new String[] { "logcat", "-v", "time", "-c", "-f",
filename.getAbsolutePath() };
Runtime.getRuntime().exec(cmd);
} catch (IOException e) {
Log.d("mCare", "Unable to log...", e);
e.printStackTrace();
}
You can read more here: How to redirect my log output from logcat to the SD-Card on an android device?
Have you tried Ti.API.log?
I would like to pull the log file from a device to my PC. How can I do that?
Logcollector is a good option but you need to install it first.
When I want to get the logfile to send by mail, I usually do the following:
connect the device to the pc.
Check that I already setup my os for that particular device.
Open a terminal
Run adb shell logcat > log.txt
I hope this code will help someone. It took me 2 days to figure out how to log from device, and then filter it:
public File extractLogToFileAndWeb(){
//set a file
Date datum = new Date();
SimpleDateFormat df = new SimpleDateFormat("yyyy-MM-dd", Locale.ITALY);
String fullName = df.format(datum)+"appLog.log";
File file = new File (Environment.getExternalStorageDirectory(), fullName);
//clears a file
if(file.exists()){
file.delete();
}
//write log to file
int pid = android.os.Process.myPid();
try {
String command = String.format("logcat -d -v threadtime *:*");
Process process = Runtime.getRuntime().exec(command);
BufferedReader reader = new BufferedReader(new InputStreamReader(process.getInputStream()));
StringBuilder result = new StringBuilder();
String currentLine = null;
while ((currentLine = reader.readLine()) != null) {
if (currentLine != null && currentLine.contains(String.valueOf(pid))) {
result.append(currentLine);
result.append("\n");
}
}
FileWriter out = new FileWriter(file);
out.write(result.toString());
out.close();
//Runtime.getRuntime().exec("logcat -d -v time -f "+file.getAbsolutePath());
} catch (IOException e) {
Toast.makeText(getApplicationContext(), e.toString(), Toast.LENGTH_SHORT).show();
}
//clear the log
try {
Runtime.getRuntime().exec("logcat -c");
} catch (IOException e) {
Toast.makeText(getApplicationContext(), e.toString(), Toast.LENGTH_SHORT).show();
}
return file;
}
as pointed by #mehdok
add the permission to the manifest for reading logs
<uses-permission android:name="android.permission.READ_LOGS" />
I would use something of this sort :
$adb logcat -d > logcat.txt
The -d option dumps the entire circular buffer into the text file and if you are looking for a particular action/intent try
$adb logcat -d | grep 'com.whatever.you.are.looking.for' -B 100 -A 100 > shorterlog.txt
Hope this helps :)
For those not interested in USB debugging or using adb there is an easier solution. In Android 6 (Not sure about prior version) there is an option under developer tools: Take Bug Report
Clicking this option will prepare a bug report and prompt you to save it to drive or have it sent in email.
I found this to be the easiest way to get logs. I don't like to turn on USB debugging.
EDIT:
The internal log is a circular buffer in memory. There are actually a few such circular buffers for each of: radio, events, main. The default is main.
To obtain a copy of a buffer, one technique involves executing a command on the device and obtaining the output as a string variable.
SendLog is an open source App which does just this: http://www.l6n.org/android/sendlog.shtml
The key is to run logcat on the device in the embedded OS. It's not as hard as it sounds, just check out the open source app in the link.
Often I get the error "logcat read: Invalid argument". I had to clear the log, before reading from the log.
I do like this:
prompt> cd ~/Desktop
prompt> adb logcat -c
prompt> adb logcat | tee log.txt
I know it's an old question, but I believe still valid even in 2018.
There is an option to Take a bug report hidden in Developer options in every android device.
NOTE: This would dump whole system log
How to enable developer options? see: https://developer.android.com/studio/debug/dev-options
What works for me:
Restart your device (in order to create minimum garbage logs for developer to analyze)
Reproduce your bug
Go to Settings -> Developer options -> Take a bug report
Wait for Android system to collect the logs (watch the progressbar in notification)
Once it completes, tap the notification to share it (you can use gmail or whetever else)
how to read this?
open bugreport-1960-01-01-hh-mm-ss.txt
you probably want to look for something like this:
------ SYSTEM LOG (logcat -v threadtime -v printable -d *:v) ------
--------- beginning of crash
06-13 14:37:36.542 19294 19294 E AndroidRuntime: FATAL EXCEPTION: main
or:
------ SYSTEM LOG (logcat -v threadtime -v printable -d *:v) ------
--------- beginning of main
A simple way is to make your own log collector methods or even just an existing log collector app from the market.
For my apps I made a report functionality which sends the logs to my email (or even to another place - once you get the log you can do whether you want with it).
Here is a simple example about how to get the log file from a device:
http://code.google.com/p/android-log-collector/
Simple just run the following command to get the output to your terminal:
adb shell logcat
Two steps:
Generate the log
Load Gmail to send the log
.
Generate the log
File generateLog() {
File logFolder = new File(Environment.getExternalStorageDirectory(), "MyFolder");
if (!logFolder.exists()) {
logFolder.mkdir();
}
String filename = "myapp_log_" + new Date().getTime() + ".log";
File logFile = new File(logFolder, filename);
try {
String[] cmd = new String[] { "logcat", "-f", logFile.getAbsolutePath(), "-v", "time", "ActivityManager:W", "myapp:D" };
Runtime.getRuntime().exec(cmd);
Toaster.shortDebug("Log generated to: " + filename);
return logFile;
}
catch (IOException ioEx) {
ioEx.printStackTrace();
}
return null;
}
Load Gmail to send the log
File logFile = generateLog();
Intent intent = new Intent(Intent.ACTION_SEND);
intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
intent.putExtra(Intent.EXTRA_STREAM, Uri.fromFile(logFile));
intent.setType("multipart/");
startActivity(intent);
References for #1
https://stackoverflow.com/a/34883741/2162226
https://stackoverflow.com/a/3359857/2162226
~~
For #2 - there are many different answers out there for how to load the log file to view and send. Finally, the solution here actually worked to both:
load Gmail as an option
attaches the file successfully
Big thanks to https://stackoverflow.com/a/22367055/2162226 for the correctly working answer
Thanks to user1354692 I could made it more easy, with only one line! the one he has commented:
try {
File file = new File(Environment.getExternalStorageDirectory(), String.valueOf(System.currentTimeMillis()));
Runtime.getRuntime().exec("logcat -d -v time -f " + file.getAbsolutePath());}catch (IOException e){}
I have created a small library (.aar) to retrieve the logs by email. You can use it with Gmail accounts. It is pretty simple but works. You can get a copy from here
The site is in Spanish, but there is a PDF with an english version of the product description.
I hope it can help.
First make sure adb command is executable by setting PATH to android sdk platform-tools:
export PATH=/Users/espireinfolabs/Desktop/soft/android-sdk-mac_x86/platform-tools:$PATH
then run:
adb shell logcat > log.txt
OR first move to adb platform-tools:
cd /Users/user/Android/Tools/android-sdk-macosx/platform-tools
then run
./adb shell logcat > log.txt
I would use something like:
$ adb logcat --pid=$(adb shell pidof com.example.yourpackage)
which you can then redirect to a file
$ adb logcat --pid=$(adb shell pidof com.example.yourpackage) > log.txt
or if you also want to see it at stdout as well:
$ adb logcat --pid=$(adb shell pidof com.example.yourpackage) | tee log.txt