Has anyone tried developing application using Lenovo K900, I am writing application for my phone (Android 4.2.2) but its not getting detected by eclipse.
Please help
I found a couple of drivers and the combination seems to do the trick.
I installed the drivers from this post to see the device as a CloverViewPlus device
https://forum.lowyat.net/topic/2918390/+940# (Post #943)
The IntelAndroidDrvSetup1.2.0.exe and iSocUSB-Driver-Setup-1.0.2.exe were needed.
Then I installed the drivers from this post to get Eclipse to recognize the device:
http://singledrivers.blogspot.com/2013/12/lenovo-k900-usb-driver-for-windows.html
It seems that you do not need the MTK driver.
You do seem to need the PDANet Driver.
The ADB driver did not seem to hurt either.
Now Eclipse can see my K900 and download code to it.
Only enabling USB Debugging will not help solve your issue.
You need to install certain drivers in order to make your cell phone visible while running the application.
For now, even I am searching the perfect drivers to install in my system. Will get back to you once I have them. Also, I request you to search as well and revert in case you find success in the same.
Related
I'm trying to get my phone to connect with Eclipse so I can run android apps without using an emulator. I've already gotten this to work and made an app, but I got a new hard drive since then. Every time I try to reinstall it on the new hard drive, it says that it doesn't install properly. I've tried using 2 different usb cords, rebooting every time I try it and installing/uninstalling the USB driver from the Motorola website to no avail, and I can't remember exactly how I did it before.
Can anyone help?
Make sure your usb debugging turned on and use this free software to install the driver :
http://adbdriver.com/
Android's development page doesn't explain this one in full detail. I had problems with it myself. Although my situation wasn't exactly like yours, installing the usb driver from the SDK made it work.
Follow this guide!
I just upgraded my phone to 4.2.2, but now i cannot use it in eclipse anymore.
I tried rebooting the device, reset my debug-settings but I cannot get it to work anymore.
I saw it is already a registered issue. There are some new security enhancements, so there should be a dialog (see here at bottom) but this dialog doesn't appear. I don't have several accounts on the phone, which is pointed out in the issue..
Anyone any suggestions?
EDIT: Look at accepted answer below, this should cover all cases. In my case, there were some packages missing, which weren't shown in the Android SDK Manager. I just found the Packages -> Reload in the Android SDK Manager... And I thought this happens automatically
You need three things in order to make sure this update goes smoothly:
Make sure your device is actually running 4.2.2 and the problem is not something else
Your SDK is updated to the latest tools. The adb binary in all but the latest version does not support the 4.2.2 security enhancements.
You are on the main account of your device in case of multiple user accounts.
Connect your Device to your computer and execute adb devices (make sure USB debugging is enabled). You should see something like this:
3tiu52839ry082j3 offline
Right about now, there should be a dialog on your device that looks something like:
Check the Always allow from this computer box if you want and click OK.
That's about it.
Some other things to check:
Make sure your USB cable isn't broken. Sometimes, the smaller cables break inside the main one, and your device may charge but have no data connection. Try with a different cable, or try accessing files on the device over USB (this will go fine if your cable is fine)
Make sure you're using the newest version of adb. Even after I updated my SDK tools, I couldn't get my device authorized when using adb. I eventually figured out that the Nvidia install of the NDK and SDK tools had updated my PATH variable to use the adb from that install, which wasn't the latest update. By using the adb in my newly updated install, I was able to get it all working.
For me it was solved by changing Nexus 7 tablet to "Camera(PTP)" mode.
Check out this blog post on how to do it.
After USB connection of Nexus 7 and confirming digest on Nexus 7, also connecting through TCP/IP with ADB worked.
Wierdly, unchecking and rechecking the "Allow USB Debugging" option popped me the window and selecting "ok" solved my problem.
If none of the solutions worked for you then Reset ADB.
Go to Devices ---Click the right most down arrow----Select Reset ADB from the list.
I had tried everything suggested here and suggested in every log/blog that I could find in google, but still no go. The USB cable is known to be good. ADB is version 1.0.31 (as shown with , USB Debugging is enabled in the Nexus 7 tablet, the SDK was updated to the very latest tools as available on 1-mar-2013 for 4.2.2/API 17. I had tried both Media and Camera modes for USB, rebooted windows, rebooted device over and over again, re-installed latest google USB driver, etc. etc. but ADB Devices still showed nothing.
I hard reset the Nexus 7 tablet thinking that maybe the screen to allow usb debugging had appeared but got hit with cancel. But that didn't work either.
What finally worked was:
going into windows control panel | Device Manager,
selecting NEXUS under Portable devices,
then in the Driver tab clicking on update and manually selecting the Google USB driver (the check feature said it was up to date). Previously, the date shown was in 2006, afterwards a date in 2012 (but more on this in a moment).
That didn't fix anything though.
So then I switched USB from MEDIA device to Camera device - THEN it wanted to install driver software, so I let it do that. Afterwards, I noticed that the driver for the Nexus was back with the 2006 version, BUT then ADB DEVICES FINALLY SHOWED OFFLINE!!!! HALLELUJAH AND the Nexus was displaying the Dialog to allow USB debugging, and it now all works.
What I am not sure of is what step actually solved the problem. I don't think it was necessary to hard reset the Tablet, but the fiddling with the device driver wasn't a very convincing solution either - I don't think the driver was corrupt - but maybe it had to be changed to get the right driver associated with the tablet when connected as a Camera Device. In any event, it is necessary to connect the tablet as a Camera device for ADB to work...
Restarting device or enabling USB debugging did not solve my problem.
However I changed USB PC Connection to "Camera(PTP)" mode and adb devices showed the device id of the phone.
After reading a lot post talking about this particular problem, I actually solved it by resetting user permissions on files (that were owned by root): ${HOME}/.android/adbkey and ${HOME}/.android/adbkey.pub
Go to Device Manager and uninstall your device and remove from USB
HAve you CMD opend and make sure you are at least in ADB Help.
Connect device to USB and continue with steps provided by Raghav Sood - few answers ahead of me.
Worked for me just fine
I tried with this custom build and it works for me. Now I can see my logcat in Eclipse again.
https://github.com/khaledev/ADT/releases
Download the zip file then in Eclipse menu Help > Install New Software... > Add > Archive... Just pick the downloaded zip and do the rest of the install process.
I need an android phone to test my apps with that will work with Eclipse. It has to be low cost, run Gingerbread with modest memory and CPU.
Thinking that any android phone would work I recently purchased a Virgin Mobil Chaser but as it turns out, it cannot be seen by either Eclipse or adb (but device manager does see the phone). Another developer has also had the same identical problem with the Chaser.
I could keep buying phones and see if they work but that could be long and frustrating. I hope to find a "no contract" phone.
Is there any list of phones that work with Eclipse. Does anyone know of any other Virgin Mobil phones that will work?
thanks, Gary
Any android phone should work. And it is not Eclipse you need it to be compatible with. You need ADB drivers for the device so ADT tools can communicate with device. So what you need is to install ADB drivers for your phone and then, once installed, you should be able to see your device once you enable USB debugging on the device. Then ADB should be able to see it (either in Eclipse plugin or via command line adb devices).
EDIT if you are on Windows, then enabling USB Debugging on the device and connecting it to the computer should result in Windows asking for ADB drivers. You may try if "stock" (these available with SDK in <SDK>\extras\google\usb_driver) are suitable. If not, check manufacturer website (for HTC you may need to install HTC Sync) and if this fail, just google for your device name along with "ADB drivers" and you should get something usable shortly.
One correct answer to my question is: the LG Optimus Elite works fine as a test phone. Drivers installed immediately. Also, it's less than $100 with no contract.
I still haven't found anyone who has gotten the PCD Chaser to work.
Gary
Picked up my S3 on launch and want to get started learning to develop for android using Eclipse. So far I'm having fun!
However, I want to be able to debug my application on the phone hardware itself and not just in an AVD. My problem is that I cannot find appropriate USB device drivers. The Samsung support site is garbage and windows update told me 'where to go'.
Has anyone got this working yet? If so, how?
For those still looking, you don't need to install the bloat. Go to:
http://www.samsung.com/us/support/owners/product/SCH-I535RWBVZW
Click on or scroll to "Manuals & Downloads" and then USB (Driver) is available under "Downloads".
Direct download link: Samsung USB Driver - 1.5.45.00
Turns out you have to install Samsung Kies to get the USB driver. Similar to the iPhone. I wanted to avoid this unnecessary bloat (i plugged my phone in and it threw a WPF exception...) and thankfully you can uninstall Kies without uninstalling the driver. Result.
After that, ADB is able to see the phone with no problem at all and I can debug on the device perfectly.
you need the usb driver for it. Once you have that installed simply connect the phone via usb to your machine, start eclipse and adb will pick up the device given that the drivers installed properly. try this link, one of these will probably have the driver. Samsung Galaxy S3 downloads
Can be downloaded on the following link
http://www.samsung.com/uk/support/usefulsoftware/ASPS/JSP
There's no need for KIES or other bloat!!
There's a very useful toolkit that does much more then kies, and it's available here:
http://forum.xda-developers.com/showthread.php?t=1703488
Direct link from Samsung's Downloads section:
http://org.downloadcenter.samsung.com/downloadfile/ContentsFile.aspx?CDSite=US&CttFileID=5301407&CDCttType=SW&ModelType=C&ModelName=SCH-I535RWBVZW&VPath=SW/201211/20121110030255344/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Any ideas where I can begin to find out what's going wrong?
I have a T-Mobile Pulse Mini (Huawei) which I'd like to get working for developing and testing apps on. I can't get it to be seen by Android Debug Bridge despite restarting the adb server. (and emulators are seen by adb any way so that's unlikely to be the problem).
In the device manager the phone is displayed as a CD-ROM and when I select 'transfer files' from the auto 'PcOptions.exe' it is then displayed as a USB driver but in either case I can't see it in adb. I have enabled debugging on the phone. I remember it took me ages to get it to work on my previous Vista 32-bit. I can't figure out where to search from here. The drivers used to install the phone are on the phone itself.
Thanks very much.
Drivers. If you can't see the phone in ADB, it's almost always a driver issue and this is especially common on Windows. The regular user drivers are sometimes different from the ADB drivers. If you can find the OEM dev drivers directly that's ideal, otherwise there's a way to modify the INF file which you'll have to Google for unless someone else provides it, as I don't remember the details at the moment.