I have recently starting going through the Java Developers tutorials for application development while using Eclipse with the Android ADT plugin. I got to the part where I had to actually run the example application on my device where I encountered my error. Whenever I run the program, I get an error about "no compatible targets found" while my Galaxy Player 4.0 is connected via USB to my computer. I'm assuming the issue is the fact I can't find the drivers for it ANYWHERE. I tried getting the Samsung Kies program because that's what everyone said to do but I have no idea how to get the drivers from it and everytime I try to hook my Galaxy Player up to my computer with Kies, it gives me an error:
"Reconnect the divice in Samsung Kies (PC Studio) mode.
Current connection mode not supported by Kies.
Check the USB settings.
(Setting -> Applications -> Development -> USB debugging(x))"
Click to expand...
Click to collapse
I have tried with the setting on and off and get the same error. I need some help; can anyone give me some?
Thanks Guys!
Nickmaster24 said:
I have recently starting going through the Java Developers tutorials for application development while using Eclipse with the Android ADT plugin. I got to the part where I had to actually run the example application on my device where I encountered my error. Whenever I run the program, I get an error about "no compatible targets found" while my Galaxy Player 4.0 is connected via USB to my computer. I'm assuming the issue is the fact I can't find the drivers for it ANYWHERE. I tried getting the Samsung Kies program because that's what everyone said to do but I have no idea how to get the drivers from it and everytime I try to hook my Galaxy Player up to my computer with Kies, it gives me an error:
I have tried with the setting on and off and get the same error. I need some help; can anyone give me some?
Click to expand...
Click to collapse
Wow, it turns out Windows automatic driver search thing found it. I'm still wondering why it never ran before...
Thanks for tolerating a noob user that hopes to be a useful part of this community in the near future
Nickmaster24 said:
Wow, it turns out Windows automatic driver search thing found it. I'm still wondering why it never ran before...
Thanks for tolerating a noob user that hopes to be a useful part of this community in the near future
Click to expand...
Click to collapse
Noob questions are ok as long as you try searching the forums/google beforehand. It's always good to see more users getting involved in development work :good:
Supermaster34 said:
Noob questions are ok as long as you try searching the forums/google beforehand. It's always good to see more users getting involved in development work :good:
Click to expand...
Click to collapse
Haha, thanks! I couldn't find anything online and reached my conclusion just messing around on my computer. I'm really excited to start deveolpment! I've been trying to get involved for a while now :
Related
i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
Uninstall everything you previously installed in the way of Samsung drivers (in fact, you could use Windows 7 backup and restore to restore your PC to the state it was in the day before you installed the drivers as they are sometimes hard to uninstall completely). Reboot and simply plug your phone (with USB debugging of course), and let Windows automatically install the drivers for you like it did before you installed the ones linked to on XDA. This time, if your PC recognizes your phone, just keep the drivers you have and don't install the ones linked to. Those drivers from the guide are for those whose PC doesn't automatically install working drivers. From that point, just follow the rest of the guide and skip the install drivers part. You will not have to install any further drivers unless you flash an AOSP ROM, in which case you'll have to follow the instructions in the OP of the ROM thread. I hope this works for you.
Has anyone seen John Connor?
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
bigwhat said:
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
Click to expand...
Click to collapse
root is not flashed via odin, rather cwm is...then the root file su_2.6.3.1 is flashed via cwm. If you need directions section 5 of my guide in general section has it covered...everything needed is there including the correct recovery and root file.
I will tell you what...the Fascinate is probably the biggest pain in the ass phone...I tried forever to root my friends and couldn't get it done...need to try again I guess, but it was a driver issue as well..ODIN just wouldn't recognize the dam phone
Use Droidstyles guide. Very easy to follow. Also, the USB cable for some reason seams to be a bit finicky at times with this device. Unplug from phone and replug. Sounds odd but trust me, I have done this many times.
Sent from my SCH-I500 using XDA App
I am having a problem too and it's not covered anywhere i've seen to date. I've got an XP and a Win7 box at home. On both, I've tried with no drivers and i've tried with every other driver set I can find and every time I hook the phone up to the machine it pops up saying USB device couldn't be recognized or something. I'm going nuts! I've never had so much difficulty in my life, not even the first time changing ROMs on anything.
Droidstyle- I've seen your guide and unless I missed it doesn't cover this. Have you seen or heard of this and have any ideas at all?
Thanks!
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
I've searched but am unable to locate the answer to my issue.
I recently upgraded to a new computer. The old one was a 2GHz dual-core running Win 7 Home 64-bit. The new one is a 3GHz, i5 running Win 7 Ultimate 64-bit. For the life of me, I cannot get the USB driver to start.
On the SAMSUNG Mobile USB Composite Device properties I get "This device cannot start. (Code 10)"
I have downloaded, installed, uninstalled and reinstalled Samsung drivers from multiple sources, including the drivers from Samsung's site.
I've installed, uninstalled and reinstalled Kies multiple times.
I've moved the cable to different ports on the PC.
I've clicked debugging on/off
I've selected MTP instead of Mass Storage.
I've rebooted the PC and phone multiple times after these installations.
Nothing seems to help. I continually get the same error.
Anyone have a suggestion before I take this phone and throw it against the wall?
When I run into that issue, it usually turns out to be a busted USB cable.
Either switch the cable or inspect the port on your phone to see If all the pins are aligned
BROKKANIC said:
When I run into that issue, it usually turns out to be a busted USB cable.
Either switch the cable or inspect the port on your phone to see If all the pins are aligned
Click to expand...
Click to collapse
I appreciate the suggestion but it did not work.
n7slc said:
I appreciate the suggestion but it did not work.
Click to expand...
Click to collapse
Try uninstalling KIES and install KIES Mini to try and get the proper drivers installed.
If that doesn't work it may be an issue with the custom ROM and/or Kernel. I'd suggest flashing over to something else to see if that fixes the issue.
SOLVED!
BROKKANIC said:
Try uninstalling KIES and install KIES Mini to try and get the proper drivers installed.
If that doesn't work it may be an issue with the custom ROM and/or Kernel. I'd suggest flashing over to something else to see if that fixes the issue.
Click to expand...
Click to collapse
Well done BROKKANIC! It must have been the AOKP ROM I was using. I updated to the latest update and now the composite device is working. With my Captivate, Artix and SGSII, I've flashed ROMs hundreds of times and this is the first time I've ever run in to this problem.
Thanks for the suggestion!
Have same problem with Samsung Galaxy Ace S5830M, need help please, i don't know to do to fix conection with PC.
Note: sorry for my english, i'm use translator, don't speak english. xD
gilber1990 said:
Have same problem with Samsung Galaxy Ace S5830M, need help please, i don't know to do to fix conection with PC.
Note: sorry for my english, i'm use translator, don't speak english. xD
Click to expand...
Click to collapse
No we don't have your phone we can't help you
Sent from my SGH-I777 using Tapatalk 2
gilber1990 said:
Have same problem with Samsung Galaxy Ace S5830M, need help please, i don't know to do to fix conection with PC.
Note: sorry for my english, i'm use translator, don't speak english. xD
Click to expand...
Click to collapse
Ask in the appropriate forum for your phone please.
Hey.
I'm currently on Cyanogenmod 10.1 and I am developing an app for college using Eclipse.
My phone wont get picked up by Eclipse when I try to run it on the phone.
Kies doesn't detect my phone no matter what storage mode it is in.
So how can I fix this?
Or is it unsupported with Cyanogenmod?
Also I tried USB debugging, you enable it by clicking on the Cyanogenmod build several times, still doesn't work.
Any help would be sweet!
I don't know about eclipse, but i know only stock works with kies
Sent from my gt-9100 powered by dorimanx
You can thank me if i helped you
AndyOHart said:
Hey.
I'm currently on Cyanogenmod 10.1 and I am developing an app for college using Eclipse.
My phone wont get picked up by Eclipse when I try to run it on the phone.
Kies doesn't detect my phone no matter what storage mode it is in.
So how can I fix this?
Or is it unsupported with Cyanogenmod?
Also I tried USB debugging, you enable it by clicking on the Cyanogenmod build several times, still doesn't work.
Any help would be sweet!
Click to expand...
Click to collapse
Have you tried installing the usb drivers for your phone?
Sent from my SCH-I535 using xda premium
Ah only stock works with Kies?
Maybe I won't be lucky then.
And yeah I even just reinstalled the drivers there.
Would make it so much easier if I could simply run the program straight off my phone rather than have to compile it every time in Eclipse.
AndyOHart said:
Ah only stock works with Kies?
Maybe I won't be lucky then.
And yeah I even just reinstalled the drivers there.
Would make it so much easier if I could simply run the program straight off my phone rather than have to compile it every time in Eclipse.
Click to expand...
Click to collapse
Another possibility is that considering CM 10.1 is still in nightly build stages (Even with the M2 release) and not a final product it's possible that the USB debugging connection may not be playing nice with your computer, does ADB recognize your phone? Does the computer recognize the device at all? The other possibility is to compile the program with eclipse, then after eclipse compiles it locate the compiled program, and push the compiled program to your phone to test it out. Also the reason it has to compile in eclipse and not just run off the phone, is that the Java and XML code (Among other things) that make up the program must be compiled into a .apk package file so Android can read and run the program. If the Java and XML code was left uncompiled and just ran off the phone Android wouldn't be able to run the program.
Yeah I used to compile and push them onto the phone but my friend showed me his S3 running straight off eclipse.
And yeah the PC picks up the phone and I can put files on it no problem. What is the ADB thing?
AndyOHart said:
Yeah I used to compile and push them onto the phone but my friend showed me his S3 running straight off eclipse.
And yeah the PC picks up the phone and I can put files on it no problem. What is the ADB thing?
Click to expand...
Click to collapse
Is your friend's Galaxy S3 rooted and is it running as custom ROM? And to answer you question ADB stands for Android Debug Bridge (Part of the Android SDK) it is an extremely helpful tool that allows you to communicate with your Android device and issue commands to it either by attaching it your computer through a USB cable or wirelessly using Wifi. One of the things you could do with ADB is push the compiled apk file to your device without having to hook the device up to your computer through USB every time you want to test out a new build of your application. You can learn more about ADB from here. You can download the Android SDK which allows you to install ADB from here.
shimp208 said:
Is your friend's Galaxy S3 rooted and is it running as custom ROM? And to answer you question ADB stands for Android Debug Bridge (Part of the Android SDK) it is an extremely helpful tool that allows you to communicate with your Android device and issue commands to it either by attaching it your computer through a USB cable or wirelessly using Wifi. One of the things you could do with ADB is push the compiled apk file to your device without having to hook the device up to your computer through USB every time you want to test out a new build of your application. You can learn more about ADB from here. You can download the Android SDK which allows you to install ADB from here.
Click to expand...
Click to collapse
No his phone isn't rooted it's just stock jelly bean.
So that means that Cyanogenmod is what is stopping it from working I take it?
I will have a look at the ADB thanks man!
AndyOHart said:
No his phone isn't rooted it's just stock jelly bean.
So that means that Cyanogenmod is what is stopping it from working I take it?
I will have a look at the ADB thanks man!
Click to expand...
Click to collapse
Glad I could help, Cyanogenmod may be causing it from not working as some apps and other services are sometimes incompatible or have issues on devices running Cyanogenmod.
Hello there.
I am taking a basic course on creating android apps.
I have the ADT installed and working. I own a S3 i9300 and it has CM 10.1.3 installed on it.
I am having trouble getting it to work as a device for Eclipse and I think it is a driver issue. I used kies to install the drivers but I'm not sure if this is how I should be doing it.
When I try to choose it as a device in Eclipse it says unknown under target with an orange Triangle and under state is says offline.
Sorry if this is a stupid question. I'm just getting started with all this and I wan't it working the best I can.
Thanks for any help
-Mala
EDIT: I disabled USB Debugging and re-enabled it and it worked