Develop Reference

How Do I Enable ADB Debugging on Chrome OS?

According to both Google and Google, if I enable Linux on Chrome OS, then in Settings' "Linux (Beta)" section, I should see a "Develop Android apps" option.
On an HP Chromebox G2 (Kench), I see this option and eventually got it activated.
On a Samsung Chromebook Plus (Kevin), I do not see this option, even with Chrome OS 88.0.4324.186.
On an ASUS Chromebook Tablet CT100 (scarlet), I see this option. This particular device is short on ports, though, so I'm going to be struggling to use it for what I need.
On an Acer Chromebook R11 (cyan), I do not see this option, even with Chrome OS 88.0.4324.186.
So... how do I enable ADB debugging on the Samsung or the Acer?
Or, another way to look at it: how do I know whether a given Chrome OS device model will or will not support ADB debugging, besides actually trying to set it up? It is difficult to plan on getting something else for testing if I do not know whether it will support ADB before buying it.

With Linux development environment (Beta) enabled,
Go to Settings of the Chromebook
Enter "android" on the search bar on top,
Select "manage Android preferences"
then you will enter generic Android setting page in a new window.
Scroll down at bottom select "System",
then select "Developer options"
I found my ADB debugging there.

It's a known issue since September 20.
There is no official response from google about this issue yet.
According to Google's product platinum expert DennyL:
"I believe it has to do with the architecture and/or the kernel version used on the device" ......... "So far, there have been no authoritative responses but we hope to see something soon."
Source: https://support.google.com/chromebook/thread/71852070?hl=en

looks like that devices without TPM 2.0 will never get this feature.
this following issue was marked as won't fix
Source: https://bugs.chromium.org/p/chromium/issues/detail?id=1072174

Chrome devTools detects remote device but not active Chrome tabs and offers no link

I have been struggling to figure out how to debug a webpage on mobile. Previously I have had no difficulty with this, but the last time I tried was maybe a year ago and some things have changed. I have an Android device with version 9 installed and Chrome stable 80. On the connected laptop I'm trying to use to debug, I have Ubuntu 19.10 and Chrome stable 80 installed.
The first thing I notice that's different is the disapearance of the remote devices tab in DevTools. Instead I am directed to chrome://inspect/#devices This is not documented in the relevant guide from google (an issue has already been filed). As such I don't know if the functionality is identical and therefore not part of my problem of if the move represents an important change that I am failing to understand in trying to debug my webapp.
Second. I go to the new devices page and find my device listed, great! The problem is that I can't figure out how to do anything with it. In the old remote devices tab there was a way to show the currently active webviews and chrome tabs and debug them. Now I see nothing of the sort.
I want to know what to do to get access to my browser on the device to debug. I have usb debugging active and connected. adb devices reports:
$ adb devices
List of devices attached
a6f8aef4 device
I have searched far and wide on the internet with no luck. This question is very similar but is in the context of Android 4.0 and trying to debug an APP instead of a chrome tab.
What am I missing?

Why does Genymotion insist upon OpenGL support when Virtual Box doesn't, and how to work around?

I am aware of Genymotion openGL error stack overflow question.
I am attempting to run Genymotion on a Windows 10 system, but the graphics adapter is Intel G45/G43 Express Chipset WDDM1.1 and the driver supplied does not support OpenGL and Intel appear to have no interest in delivering a driver that does for Windows 10. I understand that officially this combination is not supported.
But here's the thing: I can start a Genymotion VM fine from Virtual Box, and it appears to work (almost) perfectly, as far as I can tell.
Certainly I don't see any problem with the graphics.
This must be using some (probably Virtual Box provided) software implementation of OpenGL.
However, when I try to start the same phone VM from the Genymotion console, or from the Genymotion button inside Android Studio, I get the error dialog-box in the linked question above.
My question is: Why is Genymotion insisting that there is OpenGL support from the real physical display driver? And of course, if its for a quality reason only (ie: sub-optimal user experience otherwise) is there any way to disable this check?
The reason this matters is that Android Studio does not list the Virtual Box started phone VM as somewhere an application can be run upon. I suspect that when Genymotion runs a phone VM, they set up something that the Android Studio integration needs, that simply running from Virtual Box doesn't provide.
In addition, I can't circumvent the Android Studio integration by deploying to a phone VM using the gmtool device install file.apk command bundled with Genymotion because this is a paid license feature. As you can imagine I am somewhat reluctant to purchase such a license when I know I am running in an unsupported configuration.
Purchasing new hardware also isn't an option for me in the short term.
EDIT: The justification for this question has since evaporated. Although I can't deploy using Android Studio or gmtool.exe, I have managed to deploy by using the phone web browser to fetch the .apk file. The gotcha here is that the web server must supply a Content-Length header or the download will fail. So I now have a workable solution.
{{{ Andy

I'm part of the Genymotion team. That's an interesting question. The answer is: yes, we ask for OpenGL drivers for performance reasons. Without this, the whole Android rendering would be handle by the CPU (as soft rendering) which is not fast enough to allow a real usage of the devices, with a seamless user experience, particularly since 4.3. If you run a 4.2.2 image from VirtualBox, you'll see the UI inside the window but the rendering will be very laggy.
As you maybe already noticed, running the Genymotion devices from VirtualBox works only for images up to 4.2.2 (released 3 years ago). The other image will show only a console window. And to be honest, you should more consider it as a side effect than a real feature. This behaviour could disappear on a future release for any reason. And there is no way to disable this check.
As you mentioned, this configuration is really weird and exceptional. As far as I know, we don't plan to support these kind of configuration and I don't see any real viable solution to make it work properly.
Also, to explain the problem you encountered with Android Studio. When a Genymotion device start, it gets a local IP. This IP can be used to connect it to adb. Then it is possible to interact with the device like with any other Android device. This is the tools used by your IDE (and (m)any other tools communicating with Android devices.
Usually, the Genymotion app does this for you, by connecting the newly started device to adb. But you can do it yourself by running adb connect <DEVICE_IP>:5555. Just be careful because this connection could not be permanent and you should have to run this command regularly in some situations.
I hope this answer will help.
Cheers.

Android Virtual Device - Can't access basic OS features / Internet

I'm new to the Android OS and I am having trouble interacting with a virtual device. I've installed the Android SDK + Java + Eclipse and I'm trying to get a virtual device running and debug an apk I have.
I create a AVD and start it up and get this basic screen below but none of the other Android OS options you'd see on a standard phone. I can't even really control this device as the buttons seem to have no effect. I can't get into settings or see default installed applications, etc..
What am I doing wrong? I'd expect to have a basic clean Android OS startup when I launch these virtual devices but I get this funky screen and can't do anything with it, controls don't seem to work.
Worth noting I am doing this from a VMWare Workstation running Windows 2012 R2, not sure if there are issues if I'm running this all in a VM.
UPDATE:
OK so it appears I was using the Android 4.4W which I think is for wearable devices and why the OS was basically empty. I changed it to Android 4.4.2 x86 by cloning a Nexus 5 and now I just get a blank screen when I try to start the emulator. Here is a screenshot, any ideas?

Update:
You are using Android Wear API target, please try with regular android API (L preview or API 19 or below). I was able to reproduce your issue if i used Android Wear Target, it works if i used non-wear target. Android wear target is for 'wear' device types.
When configuring the AVD, you can pick different "skins" , please see below highlighted in redbox
If you are using a custom (or vendor) defined device type, go into AVD Manager -> Device Definitions and double-click your device entry, it will open the below window, make sure Buttons tab says Software
You can also navigate the emulator UI with keyboard shortcuts, often quicker this way.**

A. Ashoke is right about using skins, you may choose a skin when you create or edit the emulator. Here is a screen-shot. Check the 'skin' dropdown. (It may not be available for some 'devices' you select here.
You are using VMWare, so you might be behind a proxy. You may need to provide proxy, using following steps -
Click on Menu
Click on Settings
Click on Wireless & Networks
Go to Mobile Networks
Go to Access Point Names
Here you will Telkila Internet, click on it.
In the Edit access point section, input the "proxy" and "port"
Also provide the Username and Password, rest of the fields leave them blank.
When you will load it for the first time, it may again ask for your credentials. So provide there as well.

App does not show up in the installed application list of the Sony smartwatch2 app

I have some problems with SmartWatch2:
Sony Xperia Z1:
Accessory Version:1.0.B.0.60;
Host Application Version:1.0.12;
Smart connect: 5.4.8.
Verizon Samsung galaxy note 2:
Smart connect: 5.4.8.
My two apps do not show up in the installed application list in Sony Smart Connect. I really don't know what to do!
Does anyone have problems like this and solved it?
Many thanks.
Update:
I use "Sony add-on SDK 2.0" and SmartExtensionAPI, SmartExtensionUtils from this pack as linked libraries in my apps. Also "Sony add-on SDK 2.0" marked as a target platform for apps.
Update 2:
Another user with SmartWatch 2 write me that my app didn't listed on his phone smart connect app list.

I assume that you have tried the extension yourself on real HW and it works for you? Couple things you can tell them to try:
Uninstall the extension and reinstall it.
Unpair the bluetooth connection to SW2 and re-pair it.

Make sure:
Your SmartWatch2 extension gives the correct dimensions about itself
(i.e. the dimensions of the SmartWatch2 screen)
Your application maps correctly those dimensions, and transfers the control to your
extension
That was in case your extension never appeared on the SmartWatch2 screen. If it did, but does no more, restarting your phone normally helps. In more difficult cases, uninstall the SmartWatch2 app from your phone (it will be reinstalled once you pair your SmartWatch2 again).

I have a similarly problem but related to the development process. I'm working on a control extension app for SW2, and I was able to compile the code and see the app on the SmartConnect Installed Apps and then test it in the real device (i.e. SmartWatch 2).
After a couple of iterations on Edit code > Compile > Test, the app stops to show on the SmartConnect App list and on the SmartWatch 2 too.
I don't understand why this happens and its not clear what is the solution for this. Rebooting, uninstall, etc. Its like a random try&error solution, and leads to o much time lost on getting the app running again.
Sony SDK Team should give one word on this...