I am using AOSP to do some projects with TinkerBoard2 board. I have a problem enabling the serial console input. I have changed kernel command line arguments in order to ovveride console as such:
console=ttyS2,115200 androidboot.console=ttyS2,115200
Now I am able to see output in /dev/ttyS2 while device boots. However, there is no single user login (console opening) on that TTY. I have an idea what to do in Linux, but for Android don't have much understanding how to open up this console. I have came across following documentation that is written for another Android board, but this mostly seem unapplicable to my case:
https://android.googlesource.com/kernel/msm.git/+/android-msm-shamu-3.10-lollipop-mr1/Documentation/serial-console.txt
What I found also from TinkerBoard2 sources how console for ADB is opened:
on fs && property:ro.debuggable=1
start console
service console /system/bin/sh
console
disabled
seclabel u:r:shell:s0
Any guidance is appreciated. How do I add a console for /dev/ttyS2 for this Android board? Is getty usable for Android platforms?
Thanks
Related
It's a weird situation. I have a react native app that has a test and production environment. On the production side, my app is correctly integrated with crashlytics. But when I try to integrate on test apk, I see only "App detected and we're waiting for a crash!"
SS
Test and prod use the same application, the only difference is google-service.json files. I've not found anything. Please help.
Some notes:
I've tried on emulator and physical devices.
When I try to see dashboard for prod build, I can see correctly.
I don't think that it is related by package versions(Because it works on prod). So I didn't put those.
I 've seen " Crashlytics automatic data collection DISABLED by API" with adb logcat -s FirebaseCrashlytics command
When running the app, if you see the "App detected and we're waiting for a crash!" message, that means that the SDK was able to connect with the back end. But something could be preventing the SDK from sending crashes.
The first thing to do would be checking if the mapping file contains the parameter firebase_crashlytics_collection_enabled and if it is set to false. Check this document.
If so, you can override this parameter opting in with the code:
Firebase.crashlytics.setCrashlyticsCollectionEnabled(true)
Currently logback captures all the logs to a file that are mentioned via error, debug etc.
Apart from this logs, in Android Studio logcat we could we other logs that are provided by other apps or by the Android System.
Is there a mechanism to include all the logs that are available in adb logcat to the logs created using logback?
Unfortunately, no :
For security reason, an application can only see its own logcat, since Android 4.1 (API 16) there is no way for it to access logs from other applications or from the system.
While it is possible to add logback events to the logcat with a suitable appender, the other way around is not easy. There is no API to access the logcat events. The only solution would be for the application to launch the adb logcat command (without the usual -d flag), continuously read its output and create logback events.
I'm running a build from the Android Things Console built with several custom apks
One of the apps is failing with "{AppName}" has stopped. Open app again" The cause appears isolated to only one Configuration.
I'm trying to get to root cause, normally I would run "adb logcat" to view full details with android. Is adb logcat support with Android Things build? Is a mechanism such as logcat available in Android Things when built with a build from the Android Things Console? If not, is there an alternative?
ADB is available on development images of Android Things, not on production builds. You can change which one in the console. You can also add crash reporting tools like Crashlytics which will provide crash reports for you.
I'm working in Android Studio 2.2 RC on OSX 10.11 , and after implementing In-App Billing, after having generated my app-release.apk and having installed it on my phone, I noticed that when the purchase is successful and Ads are removed from my App, something in a secondary Activity of mine, is causing a NullPointerException and Activity is not loading.
To figure out what is causing it, I need to somehow debug the app while the In-App Purchase is active (debug.apk won't let me complete iAP) so...
How do I debug a release apk that is installed on my phone?
Use the following steps:
Enable debug in your device and connect usb to your device use
command adb devices to list connected devices
use command adb -s "device id" logcat and hit enter
It will show you a lot of log message but don't worry. Just test your phone and it will show you the error. Use ctrl + z to stop the log and you can check your error.
Please read this link. It will help more. Hope this will help you.
below code in google play service 7.0 showing perfect logs.
tagManager = TagManager.getInstance(activity);
tagManager.setVerboseLoggingEnabled(true);
but, its not working in version 8.1 and 8.4.
so, is it something like its not backword compatible or any other issue?
please, help with this.
There is some issue with the GTM sdk from the google play services v7+. It wont show any logs even though you have enabled the verbose logging.
As Google Tag Manager SDK is only showing the logs for the hits being sent to the Google Analytics, you can check the logs that is being sent to Google Analytics using below command:
$ adb shell setprop log.tag.GAv4 DEBUG
Just fire this command on terminal & it will create a logcat filter with GAv4 & enables the Google Analytics Logs. You can create a filter in logcat with "GAv4" then all the logs will be shown.
Let me know if you need more information on this.
Regards,
V