View Single Post
  #1642 (permalink)  
Old 08-23-2010, 07:11 AM
iknowsquat's Avatar
iknowsquat
Retired Staff
Offline
Location: Tampa
 
Join Date: Nov 2008
Posts: 2,940
Reputation: 7809
iknowsquat is a trusted member of the communityiknowsquat is a trusted member of the communityiknowsquat is a trusted member of the communityiknowsquat is a trusted member of the communityiknowsquat is a trusted member of the communityiknowsquat is a trusted member of the communityiknowsquat is a trusted member of the communityiknowsquat is a trusted member of the communityiknowsquat is a trusted member of the communityiknowsquat is a trusted member of the communityiknowsquat is a trusted member of the community
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
re: EVERYTHING EVO - Rooting | NAND | Flashing Roms | Wipe

Quote:
Originally Posted by stanglifemike View Post
OK, but what I type will be different in ADB then it would be if I were using SDK...right? Could you give me the commands to type in the "Window button+R" commands?
Well first lets make sure we are on the same page...I assume since you asked about adb you are trying to figure out which touch sensor you have? If you want to know what screen you have all you need to do is go to Menu/About Phone/Hardware Information. Your screen type 002 or 003 will be at the top.

adb is a tool within SDK so the actual commands will be the same just the path leading up to it would be slightly different.
We both would type:
cmd
in the Run window, then
cd\
to get to a C prompt.
To find out what touch sensor I have, with my device plugged in and USB debugging enabled at the C: prompt I would type:
android\tools\adb shell cat /sys/android_touch/vendor

And you would type:
evo-recovery\adb-windows shell cat /sys/android_touch/vendor

You see the command "shell...." is the same, just how we got there is different.
Hope that helps.
__________________
Reply With Quote