i was developing android app and logcat or anything is not showing on console.
i tried every solution in android studio but failed.
then i tried different mobile under exactly same environment and app. BOOM, logcat worked normally.
when i "adb logcat"
output: "logcat read failure"
so how to enable logcat? pls help me.
sorry for bad grammar
Related
Hello fellow Devs!
I have noticed a particular bug with this device, and only this device. A bug with the soundpool causes many apps to randomly crash (but without an FC). I'd like to post this in hopes some dev with knowledge on this would be willing to jump on this. I'm not very knowledgeable with it, but I do wish to help in any way possible!
If anyone has a logcat of the crash occuring, please pastebin it and we'll see if we can get anything fixed with it. How do you capture logcats? Either installed alogcat on your phone, OR plug your phone into a PC with SDK installed, open up CMD and type; (Make sure USB debugging is enabled)
adb devices
adb logcat > Logcat1.txt
Click to expand...
Click to collapse
This script will save the logcat in "Logcat1.txt" on your computer, to find it, you can simply search for it after pressing Start on windows.
Currently, apps that crash with soundpool bugs are;
Gameboid
GBCoid
(will update list as we are informed.)
To mods, if this is in the wrong place, let me know! I didn't feel it was necessary in the apps section since it's more of a device issue, instead of an app issue.
~Overstew
http://forum.xda-developers.com/showthread.php?t=1385500&highlight=request
Logcats are on here, to bad Samsung ignores this issue.
http://code.google.com/p/android/issues/detail?id=17623
Well I have a question to our devs. Is there any one way to logcat that is preferred over another? I never have done logcat to determine issues for our device and I would like to start. I know there are a couple apps on the play store that are useful like aLogcat or Catlog. I know its best to use adb and even run the command in terminal emulator.
There is a great guide here that I've been referring to http://forum.xda-developers.com/showthread.php?t=1726238
And DONT forget to thank paxChristos for the guide.
In short I want to logcat to help out our devs as much as possible so is there any requirements that you like to see for a logcat? Should I/we try and duplicate the issue a certain amount of times while doing the logcat? Any feedback would be useful.
Thanks to everyone who makes these devices we have just that much better. And keep up the great work.:thumbup::thumbup:
Adb is always the best and easiest way. Always be sure to use -v long when logcatting as it's makes our lives 10 times more easier. Personal favorite log cat guide is this
http://forum.xda-developers.com/showthread.php?t=1378491
Sent from my Nexus 7 using xda app-developers app
sinfulgray said:
Well I have a question to our devs. Is there any one way to logcat that is preferred over another? I never have done logcat to determine issues for our device and I would like to start. I know there are a couple apps on the play store that are useful like aLogcat or Catlog. I know its best to use adb and even run the command in terminal emulator.
There is a great guide here that I've been referring to http://forum.xda-developers.com/showthread.php?t=1726238
And DONT forget to thank paxChristos for the guide.
In short I want to logcat to help out our devs as much as possible so is there any requirements that you like to see for a logcat? Should I/we try and duplicate the issue a certain amount of times while doing the logcat? Any feedback would be useful.
Thanks to everyone who makes these devices we have just that much better. And keep up the great work.:thumbup::thumbup:
Click to expand...
Click to collapse
I think this will work for you
http://forum.xda-developers.com/showthread.php?p=37825398
sent from my htc pico
ADB is a great way to do it. The two guides stated above should help teach you how to logat.
Sent from my Nexus 4 using xda premium
For some reason i can not get my device to connect to adb, Ive never had this problem before and my my old G2x connects just fine. Ive uninstalled the drivers and reinstalled with no luck. Also went as far back as uninstalling the drivers and odin back to stock to try and have them reinstalledwith no luck. Any ideas?
sinfulgray said:
For some reason i can not get my device to connect to adb, Ive never had this problem before and my my old G2x connects just fine. Ive uninstalled the drivers and reinstalled with no luck. Also went as far back as uninstalling the drivers and odin back to stock to try and have them reinstalledwith no luck. Any ideas?
Click to expand...
Click to collapse
Try installing the regular ADB drivers then. I linked a Google search for "Samsung adb drivers".
Damn still can not connect, I've tried to uninstall Google USB driver and Samsung USB drivers and they uninstall and install just fine witj a reboot in between of course but phone is still not connected. I'm my device manager on the PC under other devices it shows 4 android devices all with yellow caution signs.
Now my G2x won't show either lol Going to try and completely remove ADB and reinstall and see what happens.
Sent from my SGH-T989 using xda premium
sinfulgray said:
Damn still can not connect, I've tried to uninstall Google USB driver and Samsung USB drivers and they uninstall and install just fine witj a reboot in between of course but phone is still not connected. I'm my device manager on the PC under other devices it shows 4 android devices all with yellow caution signs.
Now my G2x won't show either lol Going to try and completely remove ADB and reinstall and see what happens.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
If using Windows you must run the command prompt [cmd] as an admin be sure to do the following in Win 7:
click start type cmd in the white box and wait as it searches. When it lists cmd in that list now right click and choose run as admin.
Also you need to enable developer options [go to settings about device and tap the build ID like 7 times [as you tap it, it should count down after the first couple taps once you hit it enough it will say you have enabled developer options if you don't see them in settings already]
Be sure to hit the on off switch in upper right of window when you first tap developer options if the options are greyed out and don't let you change anything
Now in developer options be sure to go to the option where it says enable root access and be sure it says apps AND ADB if it says apps only tap that and change it to Apps and ADB.
Now try again
BTW I love CatLog it has a home screen widget that can start / stop recording for you] so if you know how to produce the problem go to home screen tap the widget go through the steps until the error occurs go back to home screen tap widget again and it stops then look in /sdcard/catlog/ and it will have text files named with the date and time and that will be the entire log cat that happened between the time you started and stopped the recording of your actions.
Hi,
I have been working on getting an app built with NDK and I have the visual studio environment working, compiling, deploying, and debugging with my Samsung GS3. I just bought the new Nexus 7, and when I try to debug, it gives me:
Failed to attach: Failed to start debug server on device: run-as: Package 'com.biotic.appstub' is unknown.
The pulling files step seems to completely bypass then I get the above message. I have googled and not found anything particularly helpful yet. My device is now rooted as well, which also didn't help.
I can explore the storage on the Nexus and see my app there, and I can execute it manually.
Any help would be greatly appreciated!
Cheers,
Paul
Fixed!
pblagay said:
Hi,
I have been working on getting an app built with NDK and I have the visual studio environment working, compiling, deploying, and debugging with my Samsung GS3. I just bought the new Nexus 7, and when I try to debug, it gives me:
Failed to attach: Failed to start debug server on device: run-as: Package 'com.biotic.appstub' is unknown.
The pulling files step seems to completely bypass then I get the above message. I have googled and not found anything particularly helpful yet. My device is now rooted as well, which also didn't help.
I can explore the storage on the Nexus and see my app there, and I can execute it manually.
Any help would be greatly appreciated!
Cheers,
Paul
Click to expand...
Click to collapse
This is working now. I had to install an ADB rooted ROM and it worked first time!
Hi.
Im looking for some help to run the app called "applike" on a emulator on pc or mac without the app recognising that the emulator is not a real phone or "too old device" to stop giving me this message:
This app is not able to run on this device currently.:crying::crying::crying:
Ive tried Andy, Bluestacks, Nox, Genymotion with android 6.0.0 and android 7.0.0. I can download the app and open it but when i try to log in it doesnt let me and gives me the same old message over and over.
Some help or fix or just a wake up to tell me it just plain out doesnt work at all, please tell me!:fingers-crossed:
Thanks.
I've tried everything to my knowledge including doing multiple google searches but I can't figure this out. I recently switched to Linux Mint 19 from Ubuntu 18.10 and I'm having issues getting my device to properly work using ADB. I have created the proper rules (to my knowledge) in /etc/udev/rules.d/51-android.rules and also added vendor id in ~/.android/adb_usb.ini. The main issue I seem to be having here is that after I revoke USB debugging authorizations from developer settings, I do not get the pop up on my device to allow authorization. I've tried restarts of my phone and PC but it still shows as unauthorized when typing adb devices. Any help would be appreciated. Also, just noticed I was missing some spaces in 51-android.rules I fixed but that did not fix it.
Triscuit said:
I've tried everything to my knowledge including doing multiple google searches but I can't figure this out. I recently switched to Linux Mint 19 from Ubuntu 18.10 and I'm having issues getting my device to properly work using ADB. I have created the proper rules (to my knowledge) in /etc/udev/rules.d/51-android.rules and also added vendor id in ~/.android/adb_usb.ini. The main issue I seem to be having here is that after I revoke USB debugging authorizations from developer settings, I do not get the pop up on my device to allow authorization. I've tried restarts of my phone and PC but it still shows as unauthorized when typing adb devices. Any help would be appreciated. Also, just noticed I was missing some spaces in 51-android.rules I fixed but that did not fix it.
Click to expand...
Click to collapse
Try this
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
If after that you type adb devices and you don't see your serial number type
echo 0x2717 >> ~/.android/adb_usb.ini
Just something I googled...
Tulsadiver said:
Try this
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
If after that you type adb devices and you don't see your serial number type
echo 0x2717 >> ~/.android/adb_usb.ini
Just something I googled...
Click to expand...
Click to collapse
The first two commands are to install adb and fastboot, which I've done. The third command is to add a new product id in adb_usb.ini which I got "permission denied" so I entered it manually for ****s and giggles but it didn't help. Thank you though!
I was finally able to get the device to authorize, I did a few things but I'm not sure which one corrected the problem, first. I deleted the adbkey file from /home/.android folder, I also changed permissions of the folder to rw-rw-rw and finally I hit "Revoke USB debugging authorizations" under development settings WHILE the phone was plugged into the computer. Every other time I had done it after unplugging the device. Not sure which one worked but it did, now I can get back to flashing again!
Sent from my Pixel 2 XL using XDA Labs
I had to go back in time to find this.. but this was how I originally was able to get things going in Ubuntu... It's very dated but I'm sure some of this may work?
https://forum.xda-developers.com/showpost.php?p=39144762&postcount=2
jbarcus81 said:
I had to go back in time to find this.. but this was how I originally was able to get things going in Ubuntu... It's very dated but I'm sure some of this may work?
https://forum.xda-developers.com/showpost.php?p=39144762&postcount=2
Click to expand...
Click to collapse
Yep I honestly think my problem was that I was unplugging my device before revoking authorizations..... Silly me haha
Sent from my Pixel 2 XL using XDA Labs