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.
Related
wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
EDIT: SOLVED!
So, I'm waiting for my Nexus one to come in the mail, and I think to myself, "Why not give rooting the slide another go?"
Worked second try. How's that for random....
So, here's how I made it work...Dunno if it was 'luck of the draw', but here ya go anyways...Hope it helps someone!
1. Instead of turning off the phone normally, I rebooted straight into recovery, with the phone being on first.
Code:
./adb reboot recovery
2. While rebooting, MANUALLY search for devices as soon as you can type it in, repeating rapidly (This made the difference for me).
Code:
./adb devices
3. You should catch the device in offline mode right before the recovery screen. Unplug device for 5 seconds or so, then plug it back in.
Code:
./adb devices
List of devices attached
HT05MPS02279 recovery
4. You should see your device in recovery, then you're good to go. If not try again.
How to you get the loop to stop? I have to quit Terminal app to stop it.
Click to expand...
Click to collapse
No, simply hit <control> c from inside the Terminal app to break out of the shell script.
Any other things to know?
Click to expand...
Click to collapse
Not really, it may take you several tries to get this as it did for people using M$ Winblows. I tried it about 20 - 30 times on XP and never was successful. After switching to my mac, I got root on the 5th try!
My suggestion is to follow Eugene's guide, it worked great for me! If you have problems, post them here and myself or others will try to help you.
Good luck!
wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
So I set up my camera to record myself rooting my phone using OSX and a couple friends walked into the room. I got distracted explaining what it was I was doing and didn't make the how to. If I have free time tomorrow afternoon I can make a how to vid. My girlfriend just got her slide yesterday and I believe she wants me to root it.
it's exactly the same doing it in Mac OSX as doing it in Windows except you don't have to worry about drivers. Make sure you get android SDK for Mac OSX and that you put it somewhere that is in your PATH variable.
But if you feel more comfortable doing it from Bootcamp Windows partition -- by all means do that.
Don't boot camp it... lol
I'll be posting a Mac OSX version of Eugene's Root Method shortly.
sk8rbebop, Fordude, stangri, Thanks for the quick replies! Wasn't expecting anything so soon!
I think I have tried to press CMD+C to stop the script, must have been my problem. lol.
@stangri What do you mean by PATH variable? I have the Android SDK installed in my home folder...
@sk8rbebop That's pretty funny . I'm going to have a go at it right now, I'll edit this post with my results.
edit: I don't know if this is right, but I stop the script when I see the device in offline mode. But when I unplug device, re-plug and run ./adb devices nothing shows up. The same happens if I don't unplug.
edit2: Still nothing. adb never recognizes device after I stop the loop.
I threw up a guide. Hope it helps.
Don't shut off the loop until something displays under the devices.
Re: Question: How to root MyTouch Slide using OSX?
When u connect the slide to your mac and type "adb devices", do you see your phone listed? Crucial first step before moving on.
To make things a little easier for me, I put the sdk tools folder in my path so I could issue adb commands in any directory I want to.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
@sk8rbebop Read the guide and i'm still stuck at the loop. I'm having the same issues as earlier, the device will show for a little bit but right before the recovery screen shows, it dissapears. I was stopping the script once I saw the device, before it "dissapeared". Stopping the script after it dissapears does the same...
BTW, I've noticed that I need to start the adb daemon before I run the loop in order for it to even see the device in the loop. Odd.
@Fordude Yes, if I run ./adb devices when the phone is on I get my serial number and it says "device".
edit: I found that I am running an out of date SDK revision, so I am updating to the newest (revision 6), lets see if that makes any difference...
edit 2: No dice. Lame. Oh well I guess...Try try again. My mac seems to be determined not to let this happen
update: So, I'm getting a nexus. Thanks all for your help, happy hacking!
SOLVED
post removed
I'm sorry if this has been posted before, but nothing came up in search for me. But how do you take screenshots with the G2?
Menace II Society said:
I'm sorry if this has been posted before, but nothing came up in search for me. But how do you take screenshots with the G2?
Click to expand...
Click to collapse
get the Visionary temp root app from market.
type in screenshots in market search, download that app.
Open up screenshots app, check box "shake phone for screenshots". and then if you shake your phone, it will take a screenshot
Shootme from the market (requires root) or use the Android SDK on your computer.
Download VISIONary for root, and Shoot Me for screenshots.
Sent from my T-Mobile G2 using XDA App
if u dont feel like rooting (which is super easy with visionary) and have adb already installed and working on ur computer.
while ur phone is connected to ur computer...
go into ur android-sdk folder, wherever you stored all the files
go into the 'tools'
find and click on the 'ddms' file. it will open up a blank command prompt and will eventually open up a different window.
at the top, click on the 'device' tab and click on 'screen capture'. it will do the capture by itself and i think will display it also.
jakijal said:
if u dont feel like rooting (which is super easy with visionary) and have adb already installed and working on ur computer.
while ur phone is connected to ur computer...
go into ur android-sdk folder, wherever you stored all the files
go into the 'tools'
find and click on the 'ddms' file. it will open up a blank command prompt and will eventually open up a different window.
at the top, click on the 'device' tab and click on 'screen capture'. it will do the capture by itself and i think will display it also.
Click to expand...
Click to collapse
If you try this and, like what happened to myself, your phone doesn't show up, I suggest you install PdaNet on your computer. If it asks if you want to reinstall drivers, hit yes and select HTC. Should work.
rmcsc said:
If you try this and, like what happened to myself, your phone doesn't show up, I suggest you install PdaNet on your computer. If it asks if you want to reinstall drivers, hit yes and select HTC. Should work.
Click to expand...
Click to collapse
oh, so u used pdanet 2 get ur adb working?
yeah, alot of people have taken this route instead of downloading all the sdk files and all of that. itll work this way also.
I don't see what I'm looking for when I search so here goes. I'm helping out with a bible app that you can download off line versions for. Only in certain ROM's like SR it reboots instead. They want me to capture the log for it when I go to try download but don't know what to use so I can have it show on my computer. When the phone reboots everything is log of course. Can anyone suggest a program? Thanks
Vicky
Alogcat
Sent from my ADR6300 using XDA App
I have that but once the phone locks up I can't access it then it goes into reboot which wipes the log clean. Then all I get is the boot up sequence. I'm hoping someone knows of one that I can use via my usb cord or wifi to my computer that way I can hopefully capture it on the pc instead.
Can't remember off the top of my head, but look into adb commands.
Sent from my ADR6300 using XDA App
I had thought about that but for some reason the adb shell will lock up my computer after a bit. I think it's a Windows Vista problem there.
Now when I first got my Incredible I had something like an SDK viewer? Darn I'm having one of those senior moments.
You're helping beta test too, eh? I'm Justin over there.
I'm not an Android developer, but would the files in /data/tombstone/ help? You can do an adb pull to get the file. With ddms you can browse and download files, but personally I can't get that to work in recovery...
having never used Linux before and wanting to root with AlphaRev, would anybody that has been successful with root mind summarizing all the steps that are being desecribed in the other post?
http://forum.xda-developers.com/showthread.php?t=1160511
kind of getting lost with all the various steps being talked about in there.
really appreciate it.
thanks
-Go to ubuntu.com
-Click the big orange "Get Ubuntu" button, then "Try it from a CD or USB stick"
-Follow their details for downloading and installing onto a USB drive
-Once you are booted into Ubuntu, set up your network, whether WiFi or wired. Should pop up on the upper right corner
-Plug in your phone (make sure USB debugging is on). A "restricted drivers" icon should pop up in the upper right. Click it and tell it to use them.
-Use Firefox and download the beta from the alphrevx link. Open the file from Firefox, and in the archive manager, tell it to extract to your desktop.
-Click the applications tab on the left, click show all next to installed programs, and select Terminal
-type "cd Desktop"
-type "sudo ./alpharevx"
-Follow their instructions
Hopefully that helps a bit.
Amazing
You rock! Thank you for simple instructions for us non-Linux Users, worked perfectly!
cambunch said:
-Go to ubuntu.com
-Click the big orange "Get Ubuntu" button, then "Try it from a CD or USB stick"
-Follow their details for downloading and installing onto a USB drive
-Once you are booted into Ubuntu, set up your network, whether WiFi or wired. Should pop up on the upper right corner
-Plug in your phone (make sure USB debugging is on). A "restricted drivers" icon should pop up in the upper right. Click it and tell it to use them.
-Use Firefox and download the beta from the alphrevx link. Open the file from Firefox, and in the archive manager, tell it to extract to your desktop.
-Click the applications tab on the left, click show all next to installed programs, and select Terminal
-type "cd Desktop"
-type "sudo ./alpharevx"
-Follow their instructions
Hopefully that helps a bit.
Click to expand...
Click to collapse
Will this work with no internet on the pc? Because I have all the files and I'm about to make a live disk and just run off that and if so how would I install cwm after
Sent from my ADR6350 using XDA App
bradsinram said:
Will this work with no internet on the pc? Because I have all the files and I'm about to make a live disk and just run off that and if so how would I install cwm after
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
You would need to download it and install under Windows using this thread:
http://forum.xda-developers.com/showthread.php?t=1134520
Aside from that, just copy the alphrevx binary to the Desktop via flash drive, and it should work just fine
-Plug in your phone (make sure USB debugging is on). A "restricted drivers" icon should pop up in the upper right. Click it and tell it to use them.
not getting this popup...what should made USB sync option be? didnt think step would mess me up lol
guess i should event bother trying..looks like im on baseband 0.99
now what
bettadaze said:
guess i should event bother trying..looks like im on baseband 0.99
now what
Click to expand...
Click to collapse
Someone in the alpharevx irc channel (I believe it was attn1) said a downgrade to 0.97 would be coming but that's really all the details they gave.
thanks for the update. perhaps will get lucky and they will include it with the rereleased windows version.
bettadaze said:
having never used Linux before and wanting to root with AlphaRev, would anybody that has been successful with root mind summarizing all the steps that are being desecribed in the other post?
http://forum.xda-developers.com/showthread.php?t=1160511
kind of getting lost with all the various steps being talked about in there.
really appreciate it.
thanks
Click to expand...
Click to collapse
This is a general section post. *shakes fist at you*
I've burned my ubuntu live disk in 64bit, but for some reason, when i boot it up on my HP dv2945se, the screen is distorted by these horizontal lines and no adjustments to Monitor Settings would get rid of them. I'm also having trouble getting my computers built in wireless router to be seen by Ubuntu... save me! i'm a helpless Linux n00b!!!
A good idea is to use virtual box. Free and you won't worry about rebooting or video distortion
Sent from my ADR6350 using XDA App
Well, thanks guys. I succeeded only after typing it in like 3 times (not sure how the hell I was doing it wrong, but suddenly - it worked.)
S-OFF w/ recovery in 30 seconds
Now just to teach myself about the rest of android tweaking now that root has opened her legs for us...
Nachobass25 said:
I've burned my ubuntu live disk in 64bit, but for some reason, when i boot it up on my HP dv2945se, the screen is distorted by these horizontal lines and no adjustments to Monitor Settings would get rid of them. I'm also having trouble getting my computers built in wireless router to be seen by Ubuntu... save me! i'm a helpless Linux n00b!!!
Click to expand...
Click to collapse
There are different versions of ubuntu (x86, etc). Whatever one you downloaded is the wrong one. The other should work.
Carelessly swyped on my phone so there may be some weird typos
collinray said:
A good idea is to use virtual box. Free and you won't worry about rebooting or video distortion
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
The free version if virtual box doesn't have the usb support needed. I didn't try it but people who used wubi claimed errors. The live cd worked fine for me.
Carelessly swyped on my phone so there may be some weird typos
I rooted my incredible using WUBI with no problems whatsoever.
I'm hurting for some one on one help
Sent from my ADR6350 using Tapatalk
I know that it was foolish of me to not fully research this set of commands I have copied the before and after of tit all from the command line. I was attempting to mess around with my phone with QPST. I know, I can REALLY REALLY make things hideous if I don't tread carefully with QPST, but I am willing to take the risk in order to learn, even if I do get burned because my phone bursts into flames.
Any who here is the output from my commandline which I ran because using *#0808# and switching to either RNDIS+DM+MODEM or DM+MODEM+ADB didn't make my phone visible for QPST. And I also tried while in recovery, download mode, and all the other settings in the *#0808# menu, plus variations of the menu and then booting into recovery, normal boot, and download mode. All to no avail, then in frustration I tried the following and it's gotten to the point I can't see my phone via adb anymore. So could someone please give me the undo set of commands for typing into my phones terminal as I can't type them via my computer due to adb not seeing it anymore? Thanks
C:\Users\xxxxx>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\xxxxx>adb shell
$ echo MODEM USB > /sys/class/sec/switch/usb_sel
echo MODEM USB > /sys/class/sec/switch/usb_sel
cannot create /sys/class/sec/switch/usb_sel: permission denied
$ su
su
# echo MODEM USB > /sys/class/sec/switch/usb_sel
C:\Users\xxxxx>adb shell
error: device not found
Oh!, and if anyone can explain either what the commands did or better yet where I can go read about such commands and what they do that would be great too. Thanks
Not sure how relevant this is or if it will help you but this man seems to be in kinda the same boat, why don't you take a look at this thread particularly post #2 http://forum.slimroms.net/topic/2008-broken-usbuart-path-causing-loss-of-adb/
Sent from my Nexus 7 2013 using Tapatalk
crazymonkey05 said:
Not sure how relevant this is or if it will help you but this man seems to be in kinda the same boat, why don't you take a look at this thread particularly post #2 http://forum.slimroms.net/topic/2008-broken-usbuart-path-causing-loss-of-adb/
Sent from my Nexus 7 2013 using Tapatalk
Click to expand...
Click to collapse
Thank you for the link I haven't tried anything based on the information yet, actually haven't read it all yet. Very complex stuff just lets me know how far I have to go. Odd thing is that I now for some reason have ADB working again. I did a factory reset recently and the other day I reinstalled/refreshed my computer. My computer was infected by a bunch of viruses and malware the phone was just sluggish and I had way more apps I wanted rid of than to keep. Anyway, I don't know if the virus on my system had anything to do with the malfunction or if it was the command I used but for now it is back to working.
I was working on a friends HTC Desire and was having a hell of a time getting fastboot commands to work. I got hboot USB working but when giving a command it would generate a "device connected toi USB has malfunctioned" also the USB ports would shut off untill reboot too intermittantly and even my wifi three or four days ago became disabled and I reset the adapter fine for 5mins then it went a level deeper and deeper till I reinstalled the driver. That being said it is more likely that it was the virus and or the person messing with my system that was causing all the grief. They even triggered email alerts on a couple of my accounts that passwords were input wrong 5 times in a row and that some security settings were being changed. Hopefully I have dealt with that if not I'll have to wait till they get bored. Sorry if that was a little off topic it sort of conencts to my recent problems.