Ever since I upgraded my Samsung Galaxy S3 to android 4.3 (from 4.1.2) I am unable to use Chrome's remote debugging for android (more details here).
I have the developer options and USB debugging enabled on my phone, and this worked perfectly fine on android 4.1.2.
Now, when I connect my phone to my PC, it simply connects as a media storage device and is not discovered as a USB device by chrome.
I am ruling out any problems with chrome as I could USB debug with a Google Nexus4, also, looking at some other thread (here and elsewhere) it seems to be a problem with Samsung's 4.3 upgrade.
Any pointers to get this working?
My devices stopped working as Chrome de-activated the now depracated ADB plugin as it's built in dev-tools now.
I downloaded the SDK and followed the instructions at Chrome Developers. How ever I found the instructions served by Alphonso out not to be sufficient and I did it this way on Windows 8:
Download Android SDK here ("SDK Tools Only" section) and unzip the content.
Run SDK Manager.exe and install Android SDK platform tools
Open up the Command prompt (simply by pressing the windows button and type in cmd.exe)
Enter the path with ex:
cd c:/downloads/sdk/platform-tools
Open ADB by typing in adb.exe
Run the following command by typing it and pressing enter:
adb devices
Check if you get the prompt on your device, if you still can't see your phone in Inspect Devices run the following commands one by one (excluding the ")
"adb kill-server"
"adb start-server"
"adb devices"
I had major problems and managed to get it working with these steps. If you still have problems, google the guide Remote Debugging on Android with Chrome and check for the part about drivers. I had problems with my Samsung Galaxy Nexus that needed special drivers to be compatiable with ADB.
Update
If you are using Windows 10 and couldn't find the link to download Android SDK; you may skip #1 and #2. All you need is activate "Android Debug Bridge". Go straight to #3 - #7 after download and execute "platform-tools"(https://developer.android.com/studio/releases/platform-tools.html)
Having attempted to follow Valros.nu's answer, i discovered that the sdk download is now bundeled with androind studio, in an 840MB exe installer.
As all you need for this particular program is the adb program, you can get this in a standalone installer from the xda guys:
http://forum.xda-developers.com/showthread.php?t=2317790
Note that you do not need to type adb.exe, simply type adb devices into the command prompt that is launched after install.
Also, i had to unplug and replug in my samsung s4 to get the remote debugging prompt to appear on the phone
After looking around a little longer I came across this. Apparently, there isn't a solution to this issue yet, but there is a workaround - going back to the legacy workflow.
The legacy workflow did work for me, and the only additional thing I had to do was to go to the platform-tools folder from android SDK download, open a command window here and run command "adb devices".
This caused the computer RSA key fingerprint panel to pop on my mobile screen, and after granting permission, the device showed up under Chrome's Inspect page.
Turns out that it was not an issue caused by mobile OS upgrade but by Chrome (I was thrown off by the fact that it worked on my Nexus4 somehow).
In the older versions of Chrome there was't a need to download the 500 odd mb Android SDK, as it supported an ADB plugin. But with latest version of Chrome, I guess, going legacy is the only way to go.
I have Samsung Galaxy S3 and it was not showing in the "Remote devices" tab nor in chrome://inspect.
The device did show in Windows's Device Manager as GT-I9300, though.
What worked for me was:
Plug the mobile phone to the front USB port
On my phone, click the notification about successful connection
Make sure the connection type is Camera (PTP)
On my Windows machine, download installer from https://github.com/koush/UniversalAdbDriver
Run it :)
Open cmd.exe
cd "C:\Program Files (x86)\ClockworkMod\Universal Adb Driver"
adb devices
Open Chrome in both mobile phone and Windows machine
On Windows's machine navigate to chrome://inspect - there, after a while you should see the target phone :)
I'm not sure if it affected the whole flow somehow, but at some point I've installed, and later uninstalled the drivers from Samsung: http://www.samsung.com/us/support/downloads/ > Mobile > Phones > Galaxy S > S III > Unlocked > http://www.samsung.com/us/support/owners/product/galaxy-s-iii-unlocked#downloads
For me the solution was to download the Android SDK and launch adb devices which started the adb daemon.
I know this is an older question, but I thought I would also post my solution:
Update your Chrome on your phone and on your PC.
Even if it says you have the latest driver for your device inside
Device Manager, you may need an alternative. Google latest Samsung drivers and try updating your drivers.
I had success after using ade.exe as explained above, plus using the latest version of Chrome Canary. Apparently your desktop version of Chrome has to be higher than the version running on your Android device.
For me, the menu item Inspect Devices wasn't available (not shown at all). But, simply browsing to chrome://inspect/#devices showed me my device and I was able to use the port forward etc. I have no idea why the menu item is not displayed.
Phone: Android Galaxy S4
OS: Mac OS X
In case it helps anyone I will post what worked for me.
I had to plug my S3 into a direct USB port of my PC for it to prompt me to accept the RSA signature. I had my S3 plugged into a hub before then.
Now the S3 is detected when using both the direct USB port of the PC and via the hub.
NOTE - You may need to also run adb devices from the command line to get your S3 to re-request permission.
D:\apps\android-sdk-windows\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
9283759342847566 unauthorized
...accept signature on phone...
D:\apps\android-sdk-windows\platform-tools>adb devices
List of devices attached
9283759342847566 device
Those who updated their device to Android 4.2 Jelly Bean or higher or
having a 4.2 JB or higher android powered device, will not found the
Developers Options in Settings menu. The Developers Options hide by
default on 4.2 jelly bean and later android versions. Follow the below
steps to Unhide Developers Options.
Go to Settings>>About (On most Android Smartphone and tablet)
OR
Go to Settings>> More/General tab>> About (On Samsung Galaxy S3,
Galaxy S4, Galaxy Note 8.0, Galaxy Tab 3 and other galaxy
Smartphone and tablet having Android 4.2/4.3 Jelly Bean)
OR
Go to Settings>> General>> About (On Samsung Galaxy Note 2,
Galaxy Note 3 and some other Galaxy devices having Android 4.3 Jelly
Bean or 4.4 KitKat)
OR
Go to Settings> About> Software Information> More (On HTC One or
other HTC devices having Android 4.2 Jelly Bean or higher)
2. Now Scroll onto Build Number and tap it 7 times repeatedly. A message will appear saying that u are now a developer.
Just return to the previous menu to see developer option.
Credit to www.androidofficer.com
Related
I'm aware the deadline for the developer kit for AppleTV has now passed some time ago.
What I'm confused by is, is it not possible to test tvOS apps on the actual AppleTV itself?
Is it possible to say hook up your mac with the tv device via HDMI and test it that way, like the way you do with other apps?
Many thanks
The dev kit is an actual AppleTV and was recently updated to the official tvOS release. You can test tvOS apps on it (or any other AppleTV) by connecting it to your Mac with a USB-C cable.
I have made a video showing how to test an app in Apple TV with TestFlight. https://youtu.be/Bsgdnl3dd4U .
Install TestFlight in your Apple TV first
Use "redeem code" to be able to see the apps in your TestFlight
Afterwards, you can see your beta versions on TestFlight.
To run your tvOS app on an AppleTV on your local wifi network:
On your AppleTV go to Settings > Remotes and Devices > Remote App and Devices.
In Xcode open Window > Devices and Simulators. You should see your AppleTV listed there.
Press the 'Pair' button and fill the 6 digit code shown on the tv.
I just bought a Samsung gear 2 neo and wanted to create my own watch. So this means I am new to Tizen development.
I installed the Tizen IDE and the SDK but for some reason after following -a part- this tutorial (http://www.slideshare.net/badaindonesia/professional-tizen-application-development) Tizen won't run my projects because it can't find Google Chrome on the specified location. This problem occures when I try to run a Tizen web application as a Tizen web simulator app. When i try to launch it as a Tizen web app it says Could not find emulator or device but that isn't my current target.
The specific message is Google Chrome could not be found (C:\Program Files(x86)\Google\Chrome\Application\Chrome.exe). Please install Google Chrome and specify the Google Chrome program location in Window->Preferences under "Tizen SDK/Web/Simulator".
I have tried changing the location to C:\Program Files(x86)\Google\Chrome\Application\ But this wouldn't help either. Yes, i have entered the correct location since i have manually located the chrome.exe to.
The only thing which might be wrong is that I am using the Windows 7 64 bit installer while I am on a Windows 8 64 bit desktop pc.
I have experienced a similar bug. Maybe this will help you/future developers:
My problem was that the Chrome app wouldn't open while pressing debug. I subsequently tried it with the Visual Studio Tizen extension: same problem.
The fix: I dove into the extension code and found that changing the chrome path via the option "Change Chrome path" doesn't actually change your chrome path.
What does? Going into "C:\Users\[USERNAME]\.vscode\extensions\tizenweb.wappl-1.1.2\lib\constants.js" and changing Constants.CHROME_PATH to your chrome path (for the operating system you are using).
I have not found a solution for the Tizen app, though I would recommend using the VScode extension anyway.
I had the same problem. Though not exactly a solution, I found a workaround.
Start the Web Simulator from Start Menu
Enter the location of your index.html file in the address field and press Enter
Don't forget to add file:/// in the front.
There you go!!
I'm trying to move an app created in flash professional cs6 to my 7" RCA tablet (serial number:RCT6378W2), but when I try to publish it, flash doesn't register the device as connected at all. The device is connected to my PC running windows 7 64 bit via USB to mini-USB. The device shows up in the computer panel as if it is connected. I have USB debugging activated on the device, I have the android SDK as well just to be sure I'm running the appropriate drivers to make up for the lack of drivers built into the RCA tablets for USB. The device runs android version 4.2.2 with jelly bean. I've already created the APK file through FLASH from the SWF. So, after all that I've been trying to bypass publishing and simply use the AIR SDK to download the app to the device using ADT commands and arguments.
adt -installApp -platform android -device RCT6378W2 -package C:\users\me\Desktop\FILE.apk
the command line returns either one of the following errors:
invalid argument
invalid device
To be clear, flash won't recognize the device when publishing. I've entered all of the appropriate info in the publishing settings, created a certificate, I even have the APK file ready to go saved on my desktop.
Does anyone have any experience with this situation, is the tablet simply not able to handle what I'm asking? Am I approaching this the wrong way? Any thoughts at all are appreciated.
Running adb with the 'devices' keyword and NOT getting any devices listed should tell you that you DON'T have a suitable USB driver installed.
Try the 'universal' driver found here:
http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
Restart your computer for good luck and then run adb again. Make sure that your tablet is connected to your PC and tat your cable is good. When your device is finally recognized by adb you can then see if you still have a publishing problem.
https://developers.google.com/chrome-developer-tools/docs/remote-debugging
I followed the steps but I did't get the prompt on my galaxy nexus in the step 3 and chrome://inspect/#devices didn't show the phone whereas I've got the prompt and debugged successfully using a nexus 5. I have installed the driver for the galaxy nexus downloaded at Samsung. Previously I could debug with the adb plugin but recently chrome has disabled it and forced me using the native one.
Does anyone know how I can get rid of this issue?
I finally get rid of the unhelpful samsung official driver by
http://adbdriver.com/downloads/
Please uninstall the original one before install this driver.
Cheers.
Is it normal not to have the Google Chrome browser on a google TV emulator in a Linux machine with KVM enabled?
When launching an Intent from my application that hits a web page,
I get the error message "No activity found to handle intent {act=android.intent.action.VIEW, dat=http://...}" and I have tried several web addresses.
The code from My Activity is this and it works fine in other android platforms:
Intent myIntent= new Intent(Intent.ACTION_VIEW,
Uri.parse( "http://www.test.com");
startActivity(myIntent);
Am I missing some step to install the Google Chrome browser? On the other hand I can not find the Google Market application neither.
Sadly it is normal not to have the Chrome browser installed with the emulator. This does make it a bit of a pain to do things like you are trying currently. I'm not sure if there are plans for adding Chrome to the emulator in the future, but in the meantime, it is possible to install Browser.apk (the Android browser) to the emulator (via adb install Browser.apk, which you can either build from AOSP or possibly pull from a device or standard Android emulator via adb pull /system/app/Browser.apk - I think this is the default Browser location on devices).
Once Browser.apk is installed you should be able to test these things as you would expect.
So the steps are:
Start an emulator with Android 3.1 running
adb -s device_id pull /system/app/Browser.apk
adb -s device_id install Browser.apk
In the Android smart TV emulator, I've tried the simplest method to download the Chrome browser.
Drag and drop the APK onto the emulator after downloading it from the provided link. After you will allow from to Settings > Device Preferences > Security & Restrictions > Unknown sources
Chrome APK Download URL
Second
Alternate you can follow the article link