Am I the only one having issues with adb?
I managed to get it working once yesterday night. adb logcat output was very helpful to fix the FC 'parameters' issue with libcamera under Eclair but I couldn't get it working after that. Also, when it did work, I couldn't get /system to remount rw.
I had to manually start adbd on the vogue but after I rebooted to test the new libcamera libs, I couldn't get it to work anymore, even after restarting adbd. I can see a HTC Android device in /proc/bus/usb/devices on my linux dev computer but 'adb devices' doesn't show any devices.
This was under VaniljEclair RLS6.
I did a quick search in 'Touch CDMA Android Dev' and 'Tilt Android Dev' forums, also search in google but couldn't find any quick answer.
I don't have much time (as everybody I guess) to mess with Android Dev so I would much rather spend the little time I have on something productive instead of searching for answers that somebody else might already have.
I don't mind switching to another Eclair ROM/build if I have to but I would appreciate if anybody could give me a few pointers to get adb working under eclair.
Thanks.
dlepage said:
Am I the only one having issues with adb?
I managed to get it working once yesterday night. adb logcat output was very helpful to fix the FC 'parameters' issue with libcamera under Eclair but I couldn't get it working after that. Also, when it did work, I couldn't get /system to remount rw.
I had to manually start adbd on the vogue but after I rebooted to test the new libcamera libs, I couldn't get it to work anymore, even after restarting adbd. I can see a HTC Android device in /proc/bus/usb/devices on my linux dev computer but 'adb devices' doesn't show any devices.
This was under VaniljEclair RLS6.
I did a quick search in 'Touch CDMA Android Dev' and 'Tilt Android Dev' forums, also search in google but couldn't find any quick answer.
I don't have much time (as everybody I guess) to mess with Android Dev so I would much rather spend the little time I have on something productive instead of searching for answers that somebody else might already have.
I don't mind switching to another Eclair ROM/build if I have to but I would appreciate if anybody could give me a few pointers to get adb working under eclair.
Thanks.
Click to expand...
Click to collapse
Are you using the Latest Kernel? Adb is supposed to be fixed with eclair a kernel or 2 ago. If so, Im no sure what the probem is.
Are you running windows, ubuntu ect...?
The adb problem is in the build itelf. As soon as I installed my adb quit working I went back to incubus build but it just gets really quirky after a while. I use Vanilj eclair for speed but really miss adb. And yes I am using the latest kernel I also tried troubleshooting by flashing other nbh files to no avail
incubus26jc said:
Are you using the Latest Kernel? Adb is supposed to be fixed with eclair a kernel or 2 ago. If so, Im no sure what the probem is.
Are you running windows, ubuntu ect...?
Click to expand...
Click to collapse
Eum, I'll have to check for the kernel version. It is the one included with KK VaniljEclair RLS6. The date of zImage is 24/06/2010. What was the issue again, /dev major/minor conflict between adb and 3d hardware? Is there a way to check if this is the issue from within my phone (with terminal)?
I am running Fedora Core 13 as a VirtualBox guest hosted on Windows 7 x64. As I can see a HTC Android device in /proc/bus/usb/devices in linux, I would say that VirtualBox usb passthru is not the issue but then again, I could be wrong.
Before I setup VirtualBox usb passthru, I was also having issues under Windows: it installed a few drivers but I still couldn't see the phone as Mass Storage under Windows. Is there a way to install Android Windows driver without installing the Android SDK under Windows? Since Windows is not supported for AOSP dev, I'd prefer to keep my Windows 'Android free' as far as SDK,tools, etc goes except for 'Mass Storage' access.
Hope I am making sense... As I said, all this Android business is new to me, I am probably forgetting something trivial in my setup.
Yes it is a issue in /dev with 3d hardware. You can flash latest nbh without reinstalling all system so i think that you go faster in this way.
dlepage said:
Eum, I'll have to check for the kernel version. It is the one included with KK VaniljEclair RLS6. The date of zImage is 24/06/2010. What was the issue again, /dev major/minor conflict between adb and 3d hardware? Is there a way to check if this is the issue from within my phone (with terminal)?
I am running Fedora Core 13 as a VirtualBox guest hosted on Windows 7 x64. As I can see a HTC Android device in /proc/bus/usb/devices in linux, I would say that VirtualBox usb passthru is not the issue but then again, I could be wrong.
Before I setup VirtualBox usb passthru, I was also having issues under Windows: it installed a few drivers but I still couldn't see the phone as Mass Storage under Windows. Is there a way to install Android Windows driver without installing the Android SDK under Windows? Since Windows is not supported for AOSP dev, I'd prefer to keep my Windows 'Android free' as far as SDK,tools, etc goes except for 'Mass Storage' access.
Hope I am making sense... As I said, all this Android business is new to me, I am probably forgetting something trivial in my setup.
Click to expand...
Click to collapse
There is a makedev script in the initrd.gz that differs between the initrd.gz originally included with the haretinstall.zip and the one I use. I use the initrd.gz that dzo shared here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
But first try the latest zImage from that site. If it still fails, try using the initrd.gz from this zip-file: http://sourceforge.net/projects/androidhtc/files/2010-02-20/haretinstall.zip/download
kallt_kaffe said:
There is a makedev script in the initrd.gz that differs between the initrd.gz originally included with the haretinstall.zip and the one I use. I use the initrd.gz that dzo shared here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
But first try the latest zImage from that site. If it still fails, try using the initrd.gz from this zip-file: http://sourceforge.net/projects/androidhtc/files/2010-02-20/haretinstall.zip/download
Click to expand...
Click to collapse
Did some more test.
adbd is not running under Android (VaniljEclair RLS6). Using Terminal emulator, I manually start adbd on the phone. Then, I connect the USB cable. From this point adb works from linux. Is it normal that adbd is not running after a fresh boot of the phone?
This is using the zImage and initrd from your androidinstall.tar, as far as I can see by the dates and files size. I am running from the sdcard, in case it matters.
No sweat though, I now have a work around so it is no big deal.
dlepage said:
Did some more test.
adbd is not running under Android (VaniljEclair RLS6). Using Terminal emulator, I manually start adbd on the phone. Then, I connect the USB cable. From this point adb works from linux. Is it normal that adbd is not running after a fresh boot of the phone?
This is using the zImage and initrd from your androidinstall.tar, as far as I can see by the dates and files size. I am running from the sdcard, in case it matters.
No sweat though, I now have a work around so it is no big deal.
Click to expand...
Click to collapse
Strange, this should be controlled by this in sysinit.rc:
Code:
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
disabled
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
on property:persist.service.adb.enable=1
start adbd
on property:persist.service.adb.enable=0
stop adbd
And the persist.service.adb.enable property should be enabled by default.
this may sound stupid but is there a virtual android phone that you can flash roms on?
You can't use the Android Emulator from the sdk?
The emulator in the SDK has a stock AOSP ROM on it - somewhere i've seen instructions on throwing a boot.img into it. Good should be a good source for you.
I am not a developer. I do testing only. Recently I had a problem with a nightly in CM7 sansung galaxy s. I needed to run adb shell.
What is the minimalistic way of installing and running adb shell?
When I installed Android SDK after JDK Java in Win 7, sdk manager and avd manager giving me lot of trouble. I don`t need the emulators, sdk platform for 1.6, 1.8, samples of sdk etc...
I mainly uses custom ROMs, sometimes in betas, rc, or rarely nightlies. So I need a cover for any potential problems..
Cheers.
I've noticed that I can't use ADB while in recovery mode on windows yet it works fine on linux. I'm assuming it's a driver issue being that with windows you have to install motorola's driver and on linux, like with everything, it just kinda works. My question is is there a way to get ADB within recovery working on windows. It would be helpful to not be limited to only being able to use it and mount as a storage device while inside userland. I do have a linux machine but whenever I'm on my gaming rig it would be nice to be able to use ADB and USB storage in recovery. Thanks!
I'm currently running Windows 7 SP1, Android 4.4.4 Kitkat, Linux Mint 17, and TWRP 2.8.0.1(I just noticed there was a 2.8.1.0 update although I doubt any difference will be made)
Have you updated the Android SDK?
Hi,
I would like to know if someone can explain how to build a rom for MI5 on MAC, if it's not possible, i have a windows VPS, thanks.
You can use VirtualBox(VB) to install Ubuntu. VirtualBox is a VM software and what it does is to emulate a computer inside your computer. This allows you to run your MacOS while having VB on to run Ubuntu. From there on, you can use the guide given in Cyanogen mod wiki to build the ROM for Mi 5!