[Q] DDMS log cat problem - Android Software/Hacking General [Developers Only]

Hi all,
I am facung a strange problem with my new android device and DDMS. I can see my device ID when i execute adb devices. I want to catch some logs using the log cat option in DDMS explorer. The log cat works fine for say a minute or something and then stops. In cmd am getting the below errors. Any idea why this is happening??
C:\android-sdk-windows_3.0\tools>ddms
10:54:02 E/EventLogParser: unknown tag number: 201001
10:54:02 E/EventLogParser: unknown tag number: 206002
10:54:32 W/ddms: Remote exec failed: null

Related

[Q] Problem with Eclipse

Hey there I have a problem with Eclipse when i select run, i get the following error before it starts:
"An internal error occurred during: "Launching New_configuration".
Path for project must have only one segment."
Is it to do with environment variable that had to be set up? If anyone can help with this id be most grateful

[Q] Running logcat from init.rc

Hello
I'm adding my proprietary applications in to CyanogenMod image (building from source).
After using generated image I'm getting 'System UI' has crashed. I'm unable to connect via adb as the error occurs at the very beginning of android runtime. I can see that my application has turned on, but I can't gather any logs.
To enable logs i'm trying the following method:
Appending init.rc in Android root with:
Code:
service logcat /system/bin/logcat -v long -f /mnt/sdcard/logcat.log
oneshot
This solution doesn't generate any logs. The logcat.log file doesn't exist.
I need the output to be stored either on internal or external sdcard. Could someone point me where I'm making a mistake ?

Can not start android studio on linux

I have installed android studio on puppy linux precise 5.71
When I start studio.sh following errormessage is shown and studio does not start
Unable parse command line: Unknown option --error
I have changed script from !/usr/bin/sh to /usr/bin/bash but still same error
Can anybody tell me how to rectify this error ?
Thanks in advance

stack corruption detected

I´m runnig a Moto G5+ (potter) 7.0 stock rom, rooted with magisk 16.
Since a few days I recognize an error when opening a terminal emulator or using adb from a windows PC and just typing the command
Code:
getprop
from terminal emulator or
Code:
adb shell getprop
from PC the output is
Code:
stack corruption detected
.
I´m not new to android and know how to flash roms or kernels and stuff like this but I´m not so good in terminal commands. I googled for it but the answers I found were a bit above my level of knowledge. Can someone help me out a bit and explain what this message means exactly and how to debug and solve it?
I was able to run this command a few weeks ago without problems, also rooted with magisk. Could it be any third party app or a setting?
Any help much appreciated.
edit: attached a log when typing getprop into the terminal emulator.
get same error

Question BP & ECG Watch 4 error - please help

Hi there, i am right at the end of the process of installing the modded samsung health monitor app and ADB etc but i have an error right at the end which is killing me.
This is it here:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb -s "IP address" install Watch.SHM.MOD.1.1.0.215.dante63.apk
error: device 'IP address' not found
adb: error: failed to get feature set: device 'IP address' not found
- waiting for device -
I think it is probably down to the last instruction which is this one:
Now, set your watch aside, type the following ADB command, and hit Enter to install the modded Samsung Health Monitor app on the watch. For this command to work as intended, you need to have the modded Samsung Health Monitor APK in the same directory as the file labeled cmd-here. Also, replace the X in the command mentioned below with the current version number of the APK.
adb -s "IP address" install Watch.SHM.MOD.X.X.X.XXX.dante63.apk
I have put the version number in as i downloaded it 1.1.0.215
I am unclear though on where i am supposed to make sure the apk is in relation to 1.1.0.215
Am i supposed to make sure the APK on my phone is in the same folder as what????? where does the cmd-here file come from ?
Help would be appreciated before i launch the phone towards a crash landing in mild temper LOL
Did you enable wireless debugging on your watch?
naked123 said:
Did you enable wireless debugging on your watch?
Click to expand...
Click to collapse
yep certainly did, and adb connectee so i allowed it
Try using wear installer 2
Sleepwalker54321 said:
Hi there, i am right at the end of the process of installing the modded samsung health monitor app and ADB etc but i have an error right at the end which is killing me.
This is it here:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb -s "IP address" install Watch.SHM.MOD.1.1.0.215.dante63.apk
error: device 'IP address' not found
adb: error: failed to get feature set: device 'IP address' not found
- waiting for device -
I think it is probably down to the last instruction which is this one:
Now, set your watch aside, type the following ADB command, and hit Enter to install the modded Samsung Health Monitor app on the watch. For this command to work as intended, you need to have the modded Samsung Health Monitor APK in the same directory as the file labeled cmd-here. Also, replace the X in the command mentioned below with the current version number of the APK.
adb -s "IP address" install Watch.SHM.MOD.X.X.X.XXX.dante63.apk
I have put the version number in as i downloaded it 1.1.0.215
I am unclear though on where i am supposed to make sure the apk is in relation to 1.1.0.215
Am i supposed to make sure the APK on my phone is in the same folder as what????? where does the cmd-here file come from ?
Help would be appreciated before i launch the phone towards a crash landing in mild temper LOL
Click to expand...
Click to collapse
Did you use the watches IP address instead of the text "IP address"?
Did you connect your watch via adb first?
Apache config:
adb connect x.x.x.x
Yes and yes
Its easy to make a mistake in the process ( happened to me).
Best is to start from step 1 again and carefully follow all instructions.
Use the TAB key to autocomplete file names and directories in a command line interface.
That way you're sure that it's actually the right name

Categories

Resources