Hi I'm trying to compile a Titanium Android app directly on my Nexus 7 (2013, SDK 4.3) device but I can't see any 'Titanium on Android Device' option in the Run Configurations.
My device is in Developer mode, connected to the USB, detected by Android File Transfer (Mac OS X 10.9, Titanium 3.1.4), detected by adb...
I tried to restart adb, restart Titanium, plug and unplug the device, but I still cannot see the option.
I also tested all this with Titanium 3.1.3, with no success.
I have no clue of what's happening :/ any help would be appreciated. thanks
It may sound stupid, but my friend had similar problems with his Nexus and he changed the USB slot to which he plugged his device and it worked.
Try using a different cable. Most cables are only able to load the device, somehow. Not every micro-USB-cable is capable of sending data, correctly.
Again a reason why I don´t like to work in the android environment. No one checks whether software and hardware is working the way it´s supposed to. That´s why I love Apples restrictive "closed" system. No 1000 viruses and other crap.
Well, that was a bit confusing but I finally found such option inside a Project Explorer menu...
Related
I am working at an android studio project and I always work with my own physical device SAMSUNG S7. It always worked (for a few weeks now) but today suddenly from one moment to the other my device cant be recognized by android studio anymore. I didnt change any settings! I just changed a line in the code (like a hundred times before) and after it my device is not shown in the list of devices. There is only the virtual device which is useless for me because it never displays the app correctly. Just my physical device shows the app correctly so now I need help. Otherwise I cannot continue programming.
I tried to reopen android studio and restart my phone but it didnt help.
Changing the cable plug mode (credits to Hack06)
Just swipe down the OS status bar, and tap on the device, then choose another connection mode.
Installing Samsung's development drivers
When this doesn't work, try installing the drivers provided by Samsung to improve developments. These can be found here.
USB Debugging
USB debugging may have failed. Or all of the developer settings have been reset. Try that
Reboot your phone into ODIN mode
Caution:
ODIN mode is in charge for flashing your Android phone, and if you’re not careful, you can cause permanent damage to your phone.
This solution applies only to Samsung’s devices, since they are the only devices with access to ODIN mode.
A guide how to access ODIN mode for your phone can be found here.
Install KIES software
If nothing worked till here you might want to download KIES software.
KIES software only works for Samsung’s devices.
Samsung KIES is part of Samsung Smart Switch.
Download here.
Google - Android USB Driver
My last suggestion would be to install Google's Android USB drivers. An official guide can be found here.
This may sound obvious..
but sometimes it could be a cable issue
even if it's charging it could not transfer data
try a new cable
I am trying to create a React-Native app and I need to connect my device to troubleshoot some issues that only occur on the physical device and not the simulator. For some reason I have never been able to connect my Pixel 2 XL to my PC. I am running Windows 10 and I have tried all of the following.
Enabling developer mode and USB Debugging on my device.
Uplugging and replugging my device 20+ times in a row.
Changing the USB port I am using.
Changing the USB connectivity settings in Developer Options > Default USB Configuration. (Options are: File Transfer, USB tethering, MIDI, PTP, No data transfer) I've tried them all.
Restarting my device while it's plugged in
Downloading the Google USB Driver (in Android Studio).
Restarting my PC when the device is plugged in.
Updating my PC, and updating my device.
Checking Device Manager and trying to update the driver. (So the device used to show up with the yellow warning triangle next to it and trying to update the driver never worked. But now, the device doesn't even show up in Device Manager anymore)
Factory Reset my phone.
Downloaded Media Feature Pack for N and KN versions of Windows 10 (Suggested by the google tech support)(I called them)
I feel like I've tried everything previously addressed in every Stack Overflow question on this issue.
Finally solved the issue. The data cable was the problem. If you have tried all the steps above, and nothing is working, buy a new cable. This one works great and seems very durable for my Pixel 2 X: https://www.amazon.com/gp/product/B01N4OKUB8/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
I had this issue too - my Google Pixel 2 XL is about 9 months old. Was developing an app, so using USB debugging to debug the app as I built it. One day it mysteriously stopped working, though no issues with charging. I tried everything, including using all the different USB ports on my laptop, with no luck.
I eventually gave up and started using the emulator on Android Studio, and since I didn't need data transfer for anything else, I didn't send my phone for repair or anything.
A few weeks later it just started working again, all by itself...
I don't think I did anything to fix it - the moral of the story is, if you don't need it urgently, there's a chance it might just decide to work again!
My problem is that my OnePlus One phone is not found in Eclipse on my Mac even after trying things like activating USB debugging of course and even Menu>Storage>menu on the upper right corner>USB computer connection>check box MTP/PTP.
When i try adb devices it tells me that there is no device found.
I have tried two different cables (including stock cable).
It seems that with mac there are no drivers to install needed.
Thanks a lot for any help.
Sebastien
Thanks a lot for your answer Jiang YD.
Finally, i have tried again with the same conditions few days later and Android file transfer recognized my OPO.
My OPO activated the Debug Mode automatically.
And the best is that Eclipse recognize my OPO for debugging.
So everything works well but i don't really undestand why it didn't worked the first time.
It works with the stock cable.
I have a problem debugging apps on my Samsung Galaxy S3, (GTI9300, I believe this is also known as the international version) from Eclipse.
The thing is, debugging actually worked for a time and then it just stopped working. I've tried quite a few things to make it work again. I'll describe my whole experience briefly, to keep you from suggesting things I've already tried, and save us all some time.
When I first got my phone, debugging didn't work. When I plugged in my phone, the system detected it, and I could use it almost like a storage drive (using Media Transfer Protocol or some such thing) But when I started Eclipse and tried to debug, the debugger didn't see the phone.
I googled some, learned that I had to install some specific driver. I honestly don't remember which driver it was, but I believe it was an official one (from Samsung's website). Once I installed this driver, Windows would no longer detect my phone as a storage device. But the debugger did see it, and I was able to debug a few simple apps that I'd made. I could easily live with this tradeoff.
Then I got busy with other stuff and set Android development aside. I came back to it this weekend - after 2 or 3 months - only to find that it no longer works. No matter what I do, the debugger does not detect my phone (Windows still won't detect it either).
I tried all the first aid solutions like restarting Eclipse, rebooting my computer and rebooting the phone. Just for the sake of completeness, I do have usb debugging enabled on my phone.
The only major change of the whole setup that I can think of is that my phone's OS has recently updated. I don't know the exact version it was before, right now it's Android version 4.1.2 (Kernel version 3.0.31-1160235, if this is useful to anyone). I tried plugging the phone into other computers, it gets recognized as a media/storage phone. I can't install the Android development tools and try debugging on any of these computers - I'm stuck with the one I've got.
I've tried reinstalling the usb drivers for my phone. It didn't help. In desperation (and against my better judgement) I tried installing Samsung's software, first AllShare Control, and eventually Kies. None of it helped. When I run Kies, it gives me the option of connecting through USB or via WiFi. However it won't detect my phone when I plug it in. When I click "Troubleshoot connection" (or some such thing, unfortunately Kies decided to use my native language instead of English) it starts reinstalling the USB driver. This process takes quite a while, and fixes nothing.
I'm basically out of ideas, I don't know what to try next. Any help would be appreciated.
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