Can't See My Device Of Chrome://inspect/#devices


Answer :

Try these steps:

  • Download and install Android SDK
  • Open SDK Manager.exe
  • Select Android SDK Platform-tools and press Install packages...
  • Open a command prompt and execute these commands:
    • cd C:\Program Files(x86)\Android\android-sdk\platform-tools (or C:\Users\User\AppData\Local\Android\Sdk\platform-tools)
    • adb.exe devices

You should receive a response like this:

List of devices attached ABCDEFG123  device

If your device is listed check if Chrome detect the device, otherwise try to execute this command:

  • adb.exe kill-server
  • adb.exe start-server
  • adb.exe devices

Check again if Chrome detect the device.

If your device is not listed at all after executing adb devices command there is something wrong in your configuration (e.g. incorrect or missing drivers?)


Hope this helps somebody else...

This happened to me because I was trying to Chrome inspect a release build (Ionic; i.e. ionic build android --release). If I build a debug app (ionic build android), I am able to see the app from the chrome inspection tool without any issues.

Google play does not like debugable apps https://developer.android.com/studio/publish/index.html which is needed for the inspection - see this SO link: debugging an ionic app for android platform hence proper releases won't appear in the Chrome inspection.


In my case the problem was solved changing the usb connection mode in the settings of the Android device to "Camera (PTP)" . For some reason the usb debbuging did not work when connection mode was set to MTP.


Comments

Post a Comment

Popular posts from this blog

Are Regular VACUUM ANALYZE Still Recommended Under 9.1?

Answer : VACUUM is only needed on updated or deleted rows in non-temporary tables. Obviously you're doing lots of INSERTs but it's not obvious from the description that you're also doing lots of UPDATEs or DELETEs. These operations can be tracked with the pg_stat_all_tables view, specifically the n_tup_upd and n_tup_del columns. Also, even more to the point, there is a n_dead_tup column that tells, per table, how much rows need to be vacuumed. (see Monitoring statistics in the doc for functions and views related to statistics gathering). A possible strategy in your case would be to suppress the scheduled VACUUM, keeping an eye on this view and checking on which tables the n_dead_tup is going up significantly. Then apply the aggressive VACUUM to these tables only. This will be a win if there are large tables whose rows never get deleted nor updated and the aggressive VACUUM is really necessary only on smaller tables. But keep running the ANALYZE for the optimiz
Read more

Can Feynman Diagrams Be Used To Represent Any Perturbation Theory?

Answer : Diagram machinery works also for perturbation theory in classical statistical mechanics and classical field theories. Generally, various kinds of diagrams constitute a pictorial way of talking about tensor products and their contractions while hiding the multi-linear algebra from the layman. In the simplest case, vertices (or blobs) represent vectors, matrices, tensors; vertices have ingoing and/or outgoing ports; ingoing ports denote (contravariant) ro indices; outgoing ports denote (covariant) co indices; directed arcs between blobs give a pair of equal indices summed over; different base spaces ⇔ \Leftrightarrow ⇔ different arc types; symmetric tensors ⇔ \Leftrightarrow ⇔ undirected diagrams; no labels are needed for internal lines. In many cases, the directed arcs are decorated (as thin, thick, broken,wavy, curly lines), each decoration indicating the presence of a so-called propagator, a function of its label to use as a weight in the sum, which may beco
Read more