Database Develop

Have an error message installing android sdk

Getting my feet wet installing the android sdk and getting xml repository error messages trying to install into windows.
"Failed to fetch URL https://dl-ssl.google.com/android/repository/repository.xml, reason: HTTPS SSL error. You might want to force download through HTTP in the settings."
Nothing resembles the tutorial on the SDK setup. Have the contents unzipped and sitting in the folder. Is there another procedure for installing the usb drivers from the sdk? Would somebody mind posting alternative instructions?
*Edit*
Solved!
1) Forced the update by checkmarking "Force". Installed the preliminary files (USB drivers would not install).
2) Visited developer.android.com/sdk/win-usb.html & read about upgrading the USB drivers.
3) Found this link http://forum.xda-developers.com/showthread.php?t=690362&highlight=installing+sdk and upgraded the USB drivers to version 3 (sdk).
4) Windows recognized the update and installed the USB drivers.
Was able to confirm the phones serial number with sdk!

[Q] I9000 UART DIAG Connection ?

when i try to enter UART mode on i9000 it's asking about an "7 CDCs" driver
i tried all the drivers i could find, but none of them is compatible
enter UART mode with *#9090# > Log via UART
then
enter *#7284# > UART MODEM - USB PDA

what are you trying to do?
theathering ?
if so, you don't need any of that

well...
was more thinking of making an normal sim-unlock solution for this model
i already found an uart connection on the phone PCB but for this you have to open the complete phone and work with the testpoints.. not suitable for normal users
on older android models you can enter the uart mode via diag driver over the usb port (for example on i5700, T939, i7500 etc with swallowtail driver) but this one uses a different driver

ahh, that makes sense now.
if you are using the KIES driver, uninstall it.
use the Android SDK drivers, then you will have full access to the phone via USB as a Com port

thats what i already tried, but it keeps popping up with the "7 CDCs" device and asking for drivers with i switch the USB to MODEM with *#7284#
I need to have the Android Diagnostic port available to make some checks
as USB ID i get:
USB\VID_1519&PID_0020

If you know the manufacturer (or chipset) of the modem or if modem is integrated to the motherboard, then you can probably get the drivers from the manufacturer vendor site.

there is another topic in the Dev section that is trying to do something similar
http://forum.xda-developers.com/showthread.php?t=756988

i'm afraid that also not gonna help..
we need to get the uart1 or uart2 enabled somehow..
maybe there is some hardware switching in the phone

This is exactly what I want to do. I'd like to enable Diag mode on the Samsung I9000 in order to use it with QPST.
I tried out the following procedures:
-sending at$susbc=1 on the modem port
-*#782872# does not work
-*#9090# => neither "log via usb", "log via uart" nor "log via ipc" works
Nothing helped.
Any hints are more than welcome.

Jan_1 said:
This is exactly what I want to do. I'd like to enable Diag mode on the Samsung I9000 on order to use it with QPST.
Any hints are more than welcome.
Click to expand...
Click to collapse
Why are you attempting to use it with QPST, the i9000 does not have a Qualcomm CPU.
Odia.

But isn't Snapdragon a Qualcomm chipset?
I'd like to get radio trace out of it.
I tested the Dalvik Debug Monitor (dump radio state) and logcat but these tools deliver very little radio information.

Hello Jan_1,
I expect the same answer, i want to do some radio trace with this type of mobile phone (i9000 and i7500),
If I find something, I will notify you here.
Thanks

Just thought I would finish this off, since no one has posted the way to the diag port.
For starters, you need to enable the weird comneon suspend device and the 7 acm cdc usb com ports.
This can be done thru the commands previously mentioned, *#7284# and *#9090#
Leave the top part alone, where it says MODEM. Change USB to MODEM.
In the 9090 menu set the speed to 115200
After doing that, you should get the devices I mentioned in the device manager.
Download the appropriate bit via drivers from this thread: http://forum.xda-developers.com/showthread.php?t=1696621
You can also enable the weird comneon suspend device and the 7 acm cdc usb com ports by using that little script in thread above in case you don't have access to the 7284 or 9090 menus like me.
You want to use the one that says USB MODEM.
Then you need to extract the drivers to a folder. Then after that you need to extract the files from the msi.
I used the latest unofficial version of uniextract for that.
Now go into the VIA_USB_MDM directory and edit the VIA_USB_MDM.inf file
Basically you want to create 7 different lines in there for each one of your ports.
What I did was edit the BC.MDM line and replace it.
There's 3 sections in my inf file. You want to replace the all the BC.MDM lines with several.
Like so:
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_0a
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_08
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_06
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_04
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_02
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_00
%BC.MDM% = AcmInstall, USB\VID_1519&PID_0020&MI_0c
After modifying the driver, I right clicked on each unknown device, clicked on update driver software, then clicked on locate driver software manually.
Enter the full path to the VIA_USB_MDM folder, then click ok.
It should create a BR-something modem complete with a com port.
I used realterm to open each port at various baud rates and typed AT
into each port and checked for any response.
There was one port that gave strange responses back, so I thought that might be the right port, but it was actually the next port I tried that gave correct responses back.
And there you have it, AT command access to the modem.
But keep in mind, this is not direct access to the modem. It is still going through one or more hals (Hardware abstraction layers) somewhere.
The best way to talk to the modem is with ril commands or ipc commands.
You can use ipctool and logcat -b radio to talk to the modem with ipc commands.
Ril command injection is possible, but damned annoying. I recommend ipc unless there's a really good reason.
These 2 threads are really good sources of info I used to help me get this far:
http://forum.xda-developers.com/showthread.php?t=1483053
http://forum.xda-developers.com/showthread.php?t=1471241

WORKAROUND: Captivate adb over USB on Glitch v14 + AOKP m6

I'm running AOKP m6 with the default Glitch kernel v14. The problem I'm was having is no adb over USB.
My PC is running Windows 7 64-bit.
The problem lies in the device showing in Device Manager as "SGH-I897" instead of one of the more common identifiers (which obviously were used by other kernels and/or ROMs as other ones worked fine).
NOTE: unless you NEED adb over USB for something, it will probably just be easier for you to use adb over WIFI. The following isn't super-hard but if adb over WIFI works for you ... use it.
What I attempted to do to fix before doing the workaround (add "tested adb: FAIL" to each step below) ... try these, they may work in your case:
Updated to latest Android SDK, rebooted
"Uninstalled" device in Windows
Tried to "Update Driver Software" using Android SDK USB driver ... error: "Windows could not find driver software for your device"
Tried to "Update Driver Software" using Samsung Kies USB driver ... same error.
(over WIFI adb) ran `setprop persist.sys.usb.config mass_storage,adb` ... no luck, Mass Storage worked before and after, no adb
WORKAROUND:
Summary: you need to add your device string to the USB driver INF file. The following ATTEMPTS to be a full step-by-step to show those who haven't done this before what to do.
Go to your android-sdk folder (assuming you have installed the SDK -and- included the USB drivers ... if not ... that's your first step)
Open %ANDROID-SDK%\usb_driver\android_winusb.inf in your favorite text editor
add the following lines to BOTH sections [Google.NTx86] and [Google.NTamd64]
;Samsung Captivate with Glitch kernel
SGH-I897 = USB_Install, USB\VID_18D1&PID_4E22&REV_0231&MI_01
For OTHER phones with this same problem (skip if you are using a Captivate)
NOTE: For other phones or other ROMs ... try the steps I outline at the end of this post to see if they work BEFORE you hack the driver file. You may not have the same problem I've had here.
You will need to change the lines you add to the file above. To find the right string to add to your inf file:
find your Android device in Device Manager, it SHOULD have a yellow "disabled" triangle icon and is probably under "Other Devices".
right-click the entry for your phone and select "Properties"
go to the "Details" tab
change the "Property" from "Device Description" to "Hardware Ids"
right-click and "Copy" the first entry (should look similar to USB\VID_18D1&PID_4E22&REV_0231&MI_01)
Replace USB\VID_18D1&PID_4E22&REV_0231&MI_01 from my lines above with the value you copied in the previous step
Replace ;Samsung Captivate with Glitch kernel in my lines above with something that describes your device. KEEP the semi-colon at the front of the line.
find your Android device in Device Manager
right-click it and select "Uninstall"
(IF your computer tells you to reboot at this point ... yeah ... you gotta ... so just come back here when done and make sure you've done the "Uninstall" step)
in Device Manager, do "Action" > "Scan"
find your Android device again, this time likely under "Other devices"
right-click the device in Device Manager and select "Update Driver Software"
"Browse my computer for driver software"
click the "Browse" button and find %ANDROID-SDK%\usb_driver\
click "Next"
if it tells you it can't find a driver for your device, SOMETHING above went wrong OR this workaround can't solve your problem
if it tells you "Windows can't verify the publisher of this software" ... select ... "Install this driver software anyway"
you're basically done. Verify it worked by trying the command `adb devices`. Your device should now appear.
NOTES:
If you have this problem, both Recovery mode and normal mode will be unable to connect adb via USB
adb works over WiFi, but I have some scripts that are expecting a USB connection and don't behave well without USB connection for sensing when the device has rebooted
I had adb over USB running on the same phone using Doc's ICS, Stock 2.2 and Stock 2.3
adb recovery mode on my phone works with Corn kernel, so I really think this is an issue with Glitch kernel rather than AOKP

[Q] Can't install HAXM even though VT-x is enabled

Hello,
so when I try to manually install Intel HAXM it gives me the following error:
http : // i.imgur . com / fUHAebg.gif
So I checked my UEFI and the standard value for Intel Virtualization Technology is "Enabled".
http : // i.imgur. com / fs77pTx.gif
Does anybody know how to solve this?
And seriously? I can't link pictures???...
Thanks!

On my computer, I had to update the BIOS. Try going to your computer manufacture's website support section. They may have updated BIOS(and other devices) downloads for your model. Follow the instructions when updating the BIOS. Turning off power.etc in the middle of the install can mess up your computer.

Yeah, even with a VT-x enabled CPU you still need to tick off something in the BIOS to really enable it, that is the case at least for me.

[Q] Installation driver Moverio BT 200 Windows 7

Hi,
I am in internship and I develop on Android glasses : I have Epson Moverio BT 200 model. I am at windows 7
My problem is that I don't manage to install driver to connect glasses to computer.
I follow this tutorial provided by Epson (I cannot posted the link => I am a new...)
I am blocked at second last step, during driver installation. I obtain this error message :
"Windows could'nt install your embt2.
Windows has found none driver for your peripheral device. "
I have already uninstalled google's usb driver (whit sdk manager), and next reinstalled, restarted computer, glasses, witout resilt.
The path for driver that I chose is : "C:\Program Files\Android\android-sdk\extras\google\usb_driver".
Do you have a solution, please ?
P.S : sorry for the faults.

Installation of Moverio BT 200
Hey Le-E
Epson Moverio BT 200 has not been certified with Google, therefore, you can't install it as ADB Andriod interface yet or get any app for it from Google play store directly.
Cheers

Hi Farid_Ashabi,
thank you for your response.
However, I follow a document provided by Epson, if Moverio bt 200 was not certified with google, why have they done this document ?
The document : tech.moverio.epson.com/en/life/bt-200/pdf/bt200_adb1505a_en.pdf (add https:// at beginning) (It last updating is 05/21/2015).
Are you sure ?

Installation driver Moverio BT 200 Windows 7
Hey Le-E,
I have looked at the document, it looks like work around......this document tell you how to hack the INF and add Moverio's VID\PID so the device could get recognized as Andriod ADB Interface. I have worked with Vuzix M100 and they have certified Google driver and no such hassle as installing Andriod Studio.
Cheers
Farid

Hi Farid_Ashabi,
I see. I will continue to search why that doens't work.
Thank you for your time !
keep it up !

Hi,
I resolved my problem.
For others persons with the problem, it is neccessary to add next lines twice in file "android_winsub.inf" :
";WS2 - MTP
%SingleAdbInterface% = USB_Install, USB\VID_04B8&PID_0C06
%CompositeAdbInterface% = USB_Install, USB\0VID_04B8&PID_0C06&MI_01
;WS2 - PTP
%SingleAdbInterface% = USB_Install, USB\VID_04B8&PID_0C07
%CompositeAdbInterface% = USB_Install, USB\VID_04B8&PID_0C07&MI_01"
(see the tuto tech.moverio.epson.com/en/life/bt-200/pdf/bt200_adb1505a_en.pdf (add https:// at beginning)).
you had to add this lines in the sections "[Google.NTx86]" and "[Google.NTamd64]".
And it finishes.
good luck =).

Hey Le-E,
I was able to get the BT-200 to show up as ADB interface with INF changes, but when I Execute “adb devices” to confirm name of device (0123456789ABCDEF) ......no devices is listed had no luck (as documents says, I tried is multiple time, still the same).....I'm running it under Windows 7 Ult. 64 bit......can you tell me your BT-200's Andriod version as well as your OS?
Cheers,
Farid

Hi Farid_Ashabi,
I am in Windows 7 32 bits.
BT-200's Andriod version is 4.0.4.
Have you suceeded to intsall driver ?

Hi Le-E
My specs are: Anroid 4.0.4 Kernel Version 3.0.21-00003-OMAP Build number: D1.1.2
Yes, driver have been installed and my BT-200 comes in as Android ADB Interface in device manager, but when I run the "adb device" in command prompt, I should see my device listed, but I don't.............if listed, I can install few APK files manually......no luck yet

Hi Farid_Ashabi,
sorry, I was with friends this weekend.
I have exactly same version for Kernel and Build number. I do not understand why this does not work for you...
Do you have tryed with an other USB cable ?