Is there any way to take screenshots? I'm running vegan 5.1
If you get the Android SDK installed on Windows, it has a tool called DDMS:
http://developer.android.com/guide/developing/tools/ddms.html
You can use DDMS to take screenshots:
http://www.simplehelp.net/2009/07/2...ots-of-your-android-based-phone-from-windows/
Jim
jimcpl said:
If you get the Android SDK installed on Windows, it has a tool called DDMS:
http://developer.android.com/guide/developing/tools/ddms.html
You can use DDMS to take screenshots:
http://www.simplehelp.net/2009/07/2...ots-of-your-android-based-phone-from-windows/
Jim
Click to expand...
Click to collapse
agreed, as of now that's about it. Most here have tried EVERY screenshot app available and they just produce black screens (trying to save you some time).
Thanks ill give it a try
jgeiger said:
Is there any way to take screenshots? I'm running vegan 5.1
Click to expand...
Click to collapse
I've tried to use screen grabbers I've found on the market, non of them worked properly - all creating black image.
it2steve said:
agreed, as of now that's about it. Most here have tried EVERY screenshot app available and they just produce black screens (trying to save you some time).
Click to expand...
Click to collapse
Any help available on why DDMS (or ADB for that matter) does not see my G-Tab? I have USB Debugging enabled (conected) and I can see the "SD" card?
Thanks!
ensign.fodder said:
Any help available on why DDMS (or ADB for that matter) does not see my G-Tab? I have USB Debugging enabled (conected) and I can see the "SD" card?
Thanks!
Click to expand...
Click to collapse
Just installing the SDK is not enough
the USB driver needs to be configured to allow the SDK to communicate with the device. The default driver just allows for removable drive functionality.
to configure linux ADB this thread
http://forum.xda-developers.com/showthread.php?t=919425
to configure Windows ADB this thread
http://forum.xda-developers.com/showthread.php?t=902860
Once configured follow the DDMS instructions posted earlier in the thread.
ensign.fodder said:
Any help available on why DDMS (or ADB for that matter) does not see my G-Tab? I have USB Debugging enabled (conected) and I can see the "SD" card?
Thanks!
Click to expand...
Click to collapse
or Try Adbwiress, so you don't need to connect via USB.
and on your computer , type adb connect <G-Tab Ip>
palagai said:
or Try Adbwiress, so you don't need to connect via USB.
and on your computer , type adb connect <G-Tab Ip>
Click to expand...
Click to collapse
Wow, how did I not know about this? I spent an hour setting up adb for my Gtab because of driver issues last week. I ended up having to use USBdeview to zap the previous drivers to get it to run.
Thanks for this great tip!
manikin13 said:
Just installing the SDK is not enough
the USB driver needs to be configured to allow the SDK to communicate with the device. The default driver just allows for removable drive functionality.
to configure linux ADB this thread
http://forum.xda-developers.com/showthread.php?t=919425
to configure Windows ADB this thread
http://forum.xda-developers.com/showthread.php?t=902860
Once configured follow the DDMS instructions posted earlier in the thread.
Click to expand...
Click to collapse
Thanks given that did the trick.
Related
Hi,
i am trying to upgrade cupcake to donut (google navigation doesn't work on 1.5). The adb doesn't find my handset. I downloaded and installed this sdk. Since i have cupcake, should I use sdk 1.5?
Thanks for any help!
Frank
Do you have installed the adb usb drivers? It´s needed to work´s in adb.
connecting my handset to the computer brings up the new hardware wizzard. I locate the C:\androidsdk folder. After a while a message pops up that ADB cannot be installed.
The correct folder is: C:\your-current-sdk-dir\usb_driver\x86
so the usb_driver\x86 folder should come along with the sdk package (android-sdk_r3-windows.zip), but it's not.
frank&frank said:
so the usb_driver\x86 folder should come along with the sdk package (android-sdk_r3-windows.zip), but it's not.
Click to expand...
Click to collapse
How about the STKSETUP.EXE ?!?!
Also this belongs into general. -.-""
*A lil pissed off*
sdk-full
frank&frank said:
so the usb_driver\x86 folder should come along with the sdk package (android-sdk_r3-windows.zip), but it's not.
Click to expand...
Click to collapse
Try download this adb version. Is full packet (included usb drivers).
http://developer.android.com/sdk/1.6_r1/index.html
problem solved. Just installed the htc sync. Works fine now.
Thanks a lot for helping!
fabioccoelho said:
Try download this adb version. Is full packet (included usb drivers).
http://developer.android.com/sdk/1.6_r1/index.html
Click to expand...
Click to collapse
Doesnt work, the 1.6_r1 link redirects you to this one: android-sdk_r3-windows.zip
It can't find my phone when I go to connect to it (probably because I installed it on the F:/ drive, and my ADB drivers are on the C:/ drive. How do I specifically tell it where to look? I thought I remembered seeing this in the tutorials, but I can't find it now.
Edit: Whoops, forgot that there's WinMo development here too. Feel free to move this to Android General.
TheBiles said:
It can't find my phone when I go to connect to it (probably because I installed it on the F:/ drive, and my ADB drivers are on the C:/ drive. How do I specifically tell it where to look? I thought I remembered seeing this in the tutorials, but I can't find it now.
Click to expand...
Click to collapse
Ummm... Your ADB drivers don't matter where they are. The phone is plugged in in adb mode, you install the drivers, and they are copied to C:\Windows\System32\Drivers iirc.
Have you installed the latest correct ones for your device?
pulser_g2 said:
Ummm... Your ADB drivers don't matter where they are. The phone is plugged in in adb mode, you install the drivers, and they are copied to C:\Windows\System32\Drivers iirc.
Have you installed the latest correct ones for your device?
Click to expand...
Click to collapse
Yes, and I do stuff with ADB all of the time. I think it can't find the location of adb.exe (at least I think that's what one of the guides mentioned somewhere). My phone is connected and USB Debugging is enabled, and it is detected when I execute "adb devices."
Is adb folder in your path environmental variable?
pulser_g2 said:
Is adb folder in your path environmental variable?
Click to expand...
Click to collapse
Huh? I've got my SDK installed in the default location on the C:\, but my App Inventor stuff is on the F:\ drive with all of its default settings, so I'm not sure if it is looking for F:\android-sdk-windows or not.
TheBiles said:
Huh? I've got my SDK installed in the default location on the C:\, but my App Inventor stuff is on the F:\ drive with all of its default settings, so I'm not sure if it is looking for F:\android-sdk-windows or not.
Click to expand...
Click to collapse
OK. I see what you mean, and that's not the issue.
See http://www.villainrom.co.uk/forum/s...de-Setting-up-ADB-and-how-to-use-it.-(Windows) and follow step 2 to add the adb folder to your path.
To check it works, you should be able to go to command prompt and run "F:", and then type "adb devices" and see your phone.
IE. this lets you use adb from any folder. AFAIK this will let AppInventor work.
A few days ago I've tried using ADB but it said my device is offline. Earlier I tried ADB over network. Again, it said my phone is offline. So I wanted to see if I can get ADB access from the bootloader. Surprize: I can't get into the bootloader. If I turn my phone off and press Volume Down + Power, it just boots.
Now, my phone is working good, I just wanted adb access to do that darn EFS backup. And what's up with that "can't get into bootloader" stuff? I did it fine and dandy when I rooted my phone..
EDIT: well, since I can not do the backup the normal way, I just downloaded the efs folder as a zip. and dev/block/. Is it as effective as the normal way?
andrei1015 said:
A few days ago I've tried using ADB but it said my device is offline. Earlier I tried ADB over network. Again, it said my phone is offline. So I wanted to see if I can get ADB access from the bootloader. Surprize: I can't get into the bootloader. If I turn my phone off and press Volume Down + Power, it just boots.
Now, my phone is working good, I just wanted adb access to do that darn EFS backup. And what's up with that "can't get into bootloader" stuff? I did it fine and dandy when I rooted my phone..
EDIT: well, since I can not do the backup the normal way, I just downloaded the efs folder as a zip. and dev/block/. Is it as effective as the normal way?
Click to expand...
Click to collapse
It is Vol-Up + Power for bootloader. And you can't have adb access in bootloader mode. Only fastboot access.
Ok but why isn't adb working? Why does it always say it's offline?
Sent from my Google Nexus S
andrei1015 said:
Ok but why isn't adb working? Why does it always say it's offline?
Sent from my Google Nexus S
Click to expand...
Click to collapse
It could be that you installed some software/driver that overrides a working USB driver.
Try install Google USB driver from Android SDK Tools.
Install Android SDK Tools
When SDK Manager runs, select Google USB Driver, see attached pic
If missed, run SDK Manager again as Administrator
Also, make sure you turn on Developer options and "check" Andoid (USB) debugging option in Developer options setup.
_android_ said:
It could be that you installed some software/driver that overrides a working USB driver.
Try install Google USB driver from Android SDK Tools.
Install Android SDK Tools
When SDK Manager runs, select Google USB Driver, see attached pic
If missed, run SDK Manager again as Administrator
Also, make sure you turn on Developer options and "check" Andoid (USB) debugging option in Developer options setup.
Click to expand...
Click to collapse
Yup, I have all of the above.. Still offline >.<
andrei1015 said:
Yup, I have all of the above.. Still offline >.<
Click to expand...
Click to collapse
Do you have the Samsung Galaxy Nexus ADB interface showing in your device manager?
Try uninstall and reload again.
Almost = https://dl.dropbox.com/1/view/xiulpm329s4wxcd/Apps/CloudShot/shot_25022013_192328.png
Still it says offline.
(thank you for trying to help me )
In fastboot mode it looks like this:
just tested at work and it says "device" instead of "offline" which is good I think. The only difference is that at work I installed the SDK long after I got it at home and it has a slightly different folder structure and it also comes with eclipse.
Resolved. Downloaded the new SDK with ADT from the android site and it works. Please forgive me for posting so many times. Can someone please delete this thread?
andrei1015 said:
Resolved. Downloaded the new SDK with ADT from the android site and it works. Please forgive me for posting so many times. Can someone please delete this thread?
Click to expand...
Click to collapse
Good for you.
Anyway, if you followed post #4 and installed the new SDK Tools, would have saved you a lot of time.
Hi,
I am using htc sensation with vipers 3.1.2 rom with sabestian fm kernel. while playing with my phone, i've found out that my phone is offline. even though the usb debugging is enabled, my computer is not reading my device. i've installed the htc driver many times but it doesnt work. since my computer doesnt recognize my device, the adb is showing the device as offline. Plz help
huzefaonline said:
Hi,
I am using htc sensation with vipers 3.1.2 rom with sabestian fm kernel. while playing with my phone, i've found out that my phone is offline. even though the usb debugging is enabled, my computer is not reading my device. i've installed the htc driver many times but it doesnt work. since my computer doesnt recognize my device, the adb is showing the device as offline. Plz help
Click to expand...
Click to collapse
You need to get newer adb files. Since android 4.1 you need newer ADB files. Just download the sdk and extract the updated files. Also possible (if you have the SDK) is to open the SDK manager and download updated platform-tools.
astar26 said:
You need to get newer adb files. Since android 4.1 you need newer ADB files. Just download the sdk and extract the updated files. Also possible (if you have the SDK) is to open the SDK manager and download updated platform-tools.
Click to expand...
Click to collapse
ok. i am done with that. whats next? plz guide. need to get computer detect my phone as well. unable to install drivers.
huzefaonline said:
ok. i am done with that. whats next? plz guide. need to get computer detect my phone as well. unable to install drivers.
Click to expand...
Click to collapse
connect the device to pc
open a command prompt and do
adb devices
see if it detects it now
also install htc sync.it might help
rzr86 said:
connect the device to pc
open a command prompt and do
adb devices
see if it detects it now
also install htc sync.it might help
Click to expand...
Click to collapse
Yaay its working now thank you so much
huzefaonline said:
Yaay its working now thank you so much
Click to expand...
Click to collapse
so it was all about htc sync?
rzr86 said:
so it was all about htc sync?
Click to expand...
Click to collapse
Nops. i am downloading htc sync at the moment. i had the old file of the adb. updated that using the sdk manager, copied them to my android folder and then used cmd to link adb to phone. now the usb debugging is working fine
rzr86 said:
connect the device to pc
open a command prompt and do
adb devices
see if it detects it now
also install htc sync.it might help
Click to expand...
Click to collapse
i am having the same problem again even have the updated abd and installed the correct driver but my computer is not detecting my phone neither is adb detecting. help plz
huzefaonline said:
i am having the same problem again even have the updated abd and installed the correct driver but my computer is not detecting my phone neither is adb detecting. help plz
Click to expand...
Click to collapse
ok lets take things from the beginning again
check usb debugging mode
htc drivers
install/uninstall htc sync in any case
use usb 2.0 ports not 3.0
use also different usb ports
also try this app
https://play.google.com/store/apps/details?id=com.ramdroid.adbtoggle&hl=el
rzr86 said:
ok lets take things from the beginning again
check usb debugging mode
htc drivers
install/uninstall htc sync in any case
use usb 2.0 ports not 3.0
use also different usb ports
also try this app
https://play.google.com/store/apps/details?id=com.ramdroid.adbtoggle&hl=el
Click to expand...
Click to collapse
OK.
usb debugging is enabled but no enable sign on the rom and my computer doesnt show any sign on the computer.
htc drivers installed
htc sync uninstalled
using usb 2.0 port
have tried all the ports in system. none of them work.
Adb toggle app is also not working
huzefaonline said:
OK.
usb debugging is enabled but no enable sign on the rom and my computer doesnt show any sign on the computer.
htc drivers installed
htc sync uninstalled
using usb 2.0 port
have tried all the ports in system. none of them work.
Adb toggle app is also not working
Click to expand...
Click to collapse
install htc sync again
if fails then maybe something is wrong with usb
have you tried a ruu.exe?
rzr86 said:
install htc sync again
if fails then maybe something is wrong with usb
have you tried a ruu.exe?
Click to expand...
Click to collapse
ok. let me search xda for ruu.exe. btw whats it for?
huzefaonline said:
ok. let me search xda for ruu.exe. btw whats it for?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1672425
ruu.exe returns the device into completely stock situation as you bought it
but don't worry if you are on S-OFF you won't lose it
then see if you have better results with adb usb
Mod please delete!
Jiggs82 said:
Hey guys I followed the correct instructions and downloaded the correct files (cf auto root and Google drivers) but my PC can't find/detect my device and because of that when I run the windows command it stays on "waiting for device" and nothing happens. Is there something I did wrong? Do I need to download something else? Any help would be much appreciated
Click to expand...
Click to collapse
I take it you have created a path in windows /android-sdk/platform-tools ?
Have you disabled usb driver signature authentication if you`re on Win8/8.1?
You could try removing the device in device manager and also uninstalll all drivers, then dis- and reconnect to the pc and install the google usb drivers from the sdk manualy.
ADB debugging enabled?
gee2012 said:
I take it you have created a path in windows /android-sdk/platform-tools ?
Have you disabled usb driver signature authentication if you`re on Win8/8.1?
You could try removing the device in device manager and also uninstalll all drivers, then dis- and reconnect to the pc and install the google usb drivers from the sdk manualy.
Click to expand...
Click to collapse
Yes I have, this is not my first time rooting a device I own and I had downloaded the android sdks a few years ago so I really don't know what's going on and I'm on windows 7 smh lol
Jiggs82 said:
Yes I have, this is not my first time rooting a device I own and I had downloaded the android sdks a few years ago so I really don't know what's going on and I'm on windows 7 smh lol
Click to expand...
Click to collapse
You might try installing the USB naked drivers 0.73 from here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339.