Android Devices V2 Protocol

cjisble's Avatar Topic Author
User User
  • Posts: 202
  • Thanks: 12

Android Devices V2 Protocol

4 days 17 hours ago
#5126
I happened to notice that there are two Android drivers.  AndroidTV Devices driver is marked as deprecated, and there is a driver named Android Devices V2 Protocol.

Were there always two, or was Android Devices V2 Protocol a recent addition?

If it is new, what's the difference between it and the old driver?  Are we supposed to switch the Smart Remote, or other devices like the nVidia Shield, to the new driver?

Please Log in or Create an account to join the conversation.

David Li's Avatar
Admin Admin
  • Posts: 1027
  • Thanks: 99

Re: Android Devices V2 Protocol

4 days 3 hours ago
#5127
Try switching. The new V2 should provide faster response to ADB commands that should eliminate the need for the Videostorm USB device some are now using for FireTV control.

Please Log in or Create an account to join the conversation.

cjisble's Avatar Topic Author
User User
  • Posts: 202
  • Thanks: 12

Re: Android Devices V2 Protocol

4 days 2 hours ago
#5128
Is there a recommended way to do that?

If I simply add a new device, can I keep the old and the new side-by-side and see which one works better for me?

How do I avoid deleting and completely rewriting my activation macros?

Please Log in or Create an account to join the conversation.

David Li's Avatar
Admin Admin
  • Posts: 1027
  • Thanks: 99

Re: Android Devices V2 Protocol

3 days 15 hours ago - 3 days 15 hours ago
#5129
install the new driver and run the Migrate Devices command in the new driver. Then you can delete the old driver.
As long as the Device IDs remain the same, then your macros should be fine.  Take note of the IDs in the old driver.
Last edit: 3 days 15 hours ago by David Li.

Please Log in or Create an account to join the conversation.

cjisble's Avatar Topic Author
User User
  • Posts: 202
  • Thanks: 12

Re: Android Devices V2 Protocol

3 days 20 minutes ago - 3 days 19 minutes ago
#5131
After migrating, the Shield driver stopped working.

I turned off ADB debugging, rebooted the Shield, and turned ADB debugging back on.  I then got the prompt to allow the server to connect.

Navigation controls now work.  Rapid scrolling through a long list (the biggest problem with the old driver) is NOT improved.

The main screen for the shield should have a list of all the apps.  That list is now empty.  I cleared the cache on the smart remote, and restarted.  No change.

I don't see anything in the log file:

 19/09/2026
11:44:26.44 · DEBUG · Server.WebCmd - Loadscene|shieldtv19/09/2026
11:44:26.44 · DEBUG · Server.doCommand - setvariable|backenabled_smartremote-fx-h6pt~1 from smartremote-fx-h6pt19/09/2026
11:44:26.44 · DEBUG · Server.doCommand - SetVariable|pagetitle_{{clientname}}~ from smartremote-fx-h6pt19/09/2026
11:44:26.44 · DEBUG · Server.doCommand - SetVariable|pagetitle_smartremote-fx-h6pt~19/09/2026
11:44:26.44 · DEBUG · Server.doCommand - SetVariable|overlay-header-visible-{{clientname}}~true from smartremote-fx-h6pt19/09/2026
11:44:26.44 · DEBUG · Server.doCommand - SetVariable|overlay-header-visible-smartremote-fx-h6pt~true19/09/2026
11:45:09.45 · DEBUG · Server.doCommand - SetVariable|android-command-builder-visible-dashboard-fx-h6pt~true from dashboard-fx-h6

 
Last edit: 3 days 19 minutes ago by cjisble. Reason: Reformat logfile after cut/paste

Please Log in or Create an account to join the conversation.

Time to create page: 0.264 seconds