Alright, so the issue is... I have the SDK... and it won't work on either of the operating systems I run. I am running Ubuntu 9.10 and Windows 7, both 64bit. There are two main aspects I am after with it. Using DDMS to take screenshots and mess with stuff on devices, and the virtual Android system. On Ubuntu, DDMS comes up, but it shows my device as just ?????? and I am unable to do anything. I have already tried putting in the rules thing I found all over google, and it has done nothing. The correct IDs were in as well. On Windows, why I try to use it... it pops up with a command prompt screen for a split second and does nothing. On both Ubuntu and Windows, when I try to use a virtual device, all it does is crashes. This is with all different settings. So, is there anyone that can help me out with these issues? I just spent 3 hours of google searching to no avail. None of the fixes or anything I have found made any difference. Well... that's not true... one of them made DDMS not work at all... but that just needed to be restored. Any help would be appreciated. Thanks!
Update: Doesn't work on the gf's laptop either which is running on Windows XP. So, it doesn't work on Ubuntu, Windows 7, or Windows XP. Wtf does this run correctly on?
Related
Hi,
I'm using latest froyo/eclair on nand, but have problems with adb and windows 7 x86. I've installed latest android sdk, connected my kaiser and then installed drivers. I can connect with adb but it disconnects and reconnects all the time. I cannot even install app or copy files. The same situation is on my second win7 installation.
This is rather not android build problem, but windows, because on the same laptop with ubuntu, adb works without such problems.
Anyone have some workaround for this? Maybe there should be other drivers used?
Same thing happens to me. It happened with his eclair build also. I wonder if it has to do with background processes running. I reinstalled froyo and nothing so far. Before I used to get the charging light go on and off all the time killing my battery.
Actually this happens on XP also, and has happened on every build I have used, I'm sure it's a driver or even hardware issue.
Since I very rarely use adb it's never really been an much more than an occasional annoyance.
I'm expecting to get a G1 delivered in the next few days, so I may be able to check the whole driver/hardware aspect in more depth.
My own workaround for this is simply to use an SD card reader and adaptor for moving files around between phone and computer, actually I find this almost as fast as adb, considering the time taken to set up adb, enter the commands, etc.
zenity said:
Actually this happens on XP also, and has happened on every build I have used, I'm sure it's a driver or even hardware issue.
Since I very rarely use adb it's never really been an much more than an occasional annoyance.
I'm expecting to get a G1 delivered in the next few days, so I may be able to check the whole driver/hardware aspect in more depth.
My own workaround for this is simply to use an SD card reader and adaptor for moving files around between phone and computer, actually I find this almost as fast as adb, considering the time taken to set up adb, enter the commands, etc.
Click to expand...
Click to collapse
It's not hardware issue,but rather windows drivers. Like I wrote earlier - it works ok on ubuntu...
voyteckst said:
Hi,
I'm using latest froyo/eclair on nand, but have problems with adb and windows 7 x86. I've installed latest android sdk, connected my kaiser and then installed drivers. I can connect with adb but it disconnects and reconnects all the time. I cannot even install app or copy files. The same situation is on my second win7 installation.
This is rather not android build problem, but windows, because on the same laptop with ubuntu, adb works without such problems.
Anyone have some workaround for this? Maybe there should be other drivers used?
Click to expand...
Click to collapse
Same problems for me with the Polaris.
Anyone this working with windows 7 x86?
I've given up trying to get it to work on both my machines, I get buy with the sdsplit app
Hey guys, I have been trying to get Windows 7 Drivers to work properly with adb on my A100. I have a Virtual Machine of Windows 7 and I have manually added the USB device ID's to the VBox settings for the VM client, Windows 7 sees the device ok and will mount the device fine via MTP. I can even get the drivers to say that they are working properly for the device, but when it all comes down to it they aren't.
I have tried using the ADB driver from the Android SDK which of course won't work out of the box since the device ID's aren't made for the Iconia A100, however I modified them to match the vendor/device IDs, but still - no go. I can do ' adb devices' and it will either show the device as offline or will just say the name and serial#, but when I try to connect it either says 'device offline' or it will give me a adb protocol error.
I don't know what else to really try, and at this point I am really thinking Virtualbox isn't passing the USB properly to the Guest OS, but what is odd, is my HTC WildFire S will work fine with adb (same binary).
I have also tried the Acer drivers that are available on the Acer Website, as well as a few other device drivers that I can't recall off the top of my head.
I guess some people are wondering if this is working in Linux why am I so concerned about getting it to work in a Virtual Machine running Windows. In short the answer is: I am developing kernels and recovery for the A100 as many may already know, and I am working on some automated installers that are cross platform compatible and I need to test the Windows side of things before I make releases, yet it's a bit hard to do when Windows is such a PITA when it comes to anything Android.. Yea, I'm a Linux person I know it's obvious - but I need this working somehow in a Virtual Machine because I'm not willing to do a native install of Windows on any of my machines, simple as that lol..
Anyone who may have a Virtualbox install of Windows 7 (or vista) that has adb working with their A100, please let me know the adb drivers you used and if at all possible attach them here, or give me a direct link. I greatly appreciate the help guys!
Here is a snippet of the troubles:
Code:
List of devices attached
037c624643a033d7 device
C:\Users\Lance\Downloads\godmachine81-Acer-A100-TWRP-Installer\godmachine81-Acer
-A100-TWRP-Installer-c8ccd42>adb shell
error: protocol fault (status 72 6f 6f 74?!)
**Edit: I kinda found a solution to my own problem, but not a great one. The problem was with EHCI 2.0 in VirtualBox, when this setting is disabled it will allow adb to work correctly, however on Windows 7 it will break the USB host so there is no possible way to use the tablet period, with Windows XP however it works fine. Windows XP has the exact same issue, but the USB Hub will actually work without EHCI 2.0, not really sure if there is a workaround to the Windows 7 problem, but I didn't really mess with it long - I'd say one might be able to uninstall the USB adapter and reinstall it after disabling EHCI and then also reinstall the Acer drivers. I got tired of fooling with windows 7 and just installed a copy of XP, wrote the batch script for windows, and will soon be uninstalling most likely haha.. Hope this might be some good info for others who run into a similar issue
Hi all,
I've got a problem and I hope someone will be able to help me :fingers-crossed:
I'm now working on a Core Due Duo PC at 2.1GHz on Kubuntu.
When I need Windows, I usually virtualize it in my VirtualBox. Since now, I had no problems with it.
Because I HATE Windows 7 for previous problems, I tried to install Windows Phone SDK on my Windows XP virtualized, following this guide:
http://forum.xda-developers.com/wiki/Windows_Phone_7_Emulator
Now, emultators starts but it is too slow!
After it starts, after about 20mins disappears the writing as in "booting_1.jpg" file here attached and after some minutes appear Windows Phone Logo as in "wp.png" file attached.
After that, emulator don't go on any more.
I tried the same emulator in a Windows XP machine no virtualized and after some minute emulators was ready.
According to you, is there something I can do for developing for WP7 in my virtual XP? Some particular settings?
I hope in some help, thank you very much
Hi, I am trying to connect my 1P7T to Windows 7 and 10, both in Virtualbox guests. But I cannot get the prompt to come up on the phone. It connects just fine to the Linux host, but not to Windows, it has worked before when I had my system on a different version of Linux but not now. Unless there is some better way to run fastboot commands on my phone in Linux, I am all ears. But I would really like to just use the All in one tool in windows.
Thanks
Got it all figured out, first I had the wrong Virtualbox extension pack installed. I still could not get it to work when set to USB 3.0. I set it to USB 2.0 and the phone is now connected and authorized.
Glad I figured it out on my own, but also good for someone else to know.
Hi all,
I purchased a gemini wifi recently, but a 4g version arrived! I'm now trying to flash Linux on there, but I cannot get the flash tool to do anything.
I'm pretty sure that this is a driver issue, but I'm not sure what to do about it. I've tried windows 11 and 10, as well as ubuntu 20.04 to flash this thing and nothing is working.
On the windows 11 host I even disabled memory protection to allow the drivers to work correctly, but that made no difference.
Following the guides on planet computer, it's not clear what state the device should be in, but I've tried normally booted into android as well as in recovery mode (booted with Esc and side button depressed on boot}
What am I missing here? Does flashing this device just no longer work?
Thanks in advance for your help!
it still works presuming you are referring to this guide: https://support.planetcom.co.uk/index.php/Linux_Flashing_Guide
I unfortunately don't think I am able to help you debug the situation from the information you provided.
I am not sure where most of the users congregate, but I have seen some sporadic recent activity here: https://www.oesf.org/forum/index.php?board=192.0
From my own experience, windows 7 and windows 10 have worked flawlessly, ubuntu worked for me in the past, but had trouble recently. win7 and win10 in virtualbox requires delicate usb device setup adding device during gemini reboot, and still gives some trouble.
I haven seen any updates or security patches from planet on neither android nor debian, so got myself a sailfish X license to support their development, it looks like a lot of updates (most recently yesterday: https://forum.sailfishos.org/t/release-notes-vanha-rauma-4-4-0-72/ )
good luck