question

Carlos avatar image
Carlos asked

What can I do about discovery issues?

I have several beta users who say that my app isn't finding their Fire TV. I myself see that on my test phones frequently. I am using the Connect SDK for casting and flinging. What kind of information can I gather to help solve this issue? I will be releasing the beta of my app in a few weeks to an app with over 700k downloads and it would be nice if the Fire TV discovery worked better. Thanks.
amazon fling
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Nick Gardner avatar image
Nick Gardner answered
Hi, The users need to have multicast enabled on the wifi network. One good way to check. would be to have them use the Fire TV remote app to see if they can see their Fire TV on there, and if they can there shouldn't be any issues with getting fling working. Otherwise, they may need to change their wifi network settings. Thanks, Nick
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Carlos avatar image
Carlos answered
I don't think multicast is the issue because I launch the same version of the app on all my test phones (4 to 6 depending on what I'm testing) and some will find the Fire TV and some won't. Sometimes they switch, sometimes all find it, sometimes only one finds it, it is very unpredictable.
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Nick Gardner avatar image
Nick Gardner answered
Hi, What devices and OS are you using on these devices? Also, have you experienced the same discovery issues using the Fire TV Remote control app or the Fling Sample app? Thanks, Nick
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Carlos avatar image
Carlos answered
I only have one phone which has this issue frequently, the others have it too but rarely. It is a Moto G. Anyways, the FireTV remote app also has the issue. I am using the ConnectSDK and it is able to find the DIAL service of the FireTV but not the Fling service. I will see if I can get one of the sample apps working. I've had a few users also report this issue and I haven't yet found a way to get it to work for them. For example with the Chromecast usually if you reboot your phone, Chromecast and home wifi then it will show up, but that doesn't help with the FireTV.
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Carlos avatar image
Carlos answered
Just tried the Fling sample app. On my Nexus 5 it found the FireTV really quick. On my Moto G the icon to connect never showed up.
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Nick Gardner avatar image
Nick Gardner answered
What is the build number and android OS version? Logcat logs, especially from app start would also be very helpful in tracking down this issue. -Nick
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Carlos avatar image
Carlos answered
My phone that usually has issues is: Moto G 4.4.4 KXB21.14-L1.41 Using Fling SDK 1.1.3 I'll collect logs the next time it doesn't find the Fire TV Stick, it found it fine right now.
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Carlos avatar image
Carlos answered
Got a chance to capture some logs on my Moto G. 09-22 14:52:15.636 27274-27760/mypackage I/WhisperLink﹕ WPLOG - New log handler set is :com.amazon.whisperlink.platform.GenericAndroidLogHandler@41fb0740 09-22 14:52:16.132 27274-27760/mypackage I/WhisperLink﹕ GenericAndroidPlatform - No Whisperplay XML, will not be hosting any services 09-22 14:52:16.146 27274-27760/mypackage I/WhisperLink﹕ PlatformOptionsImpl - Added memory channel as internal channel 09-22 14:52:16.166 27274-27760/mypackage I/WhisperLink﹕ PlatformCoreManager - Loading system services: 09-22 14:52:16.258 27274-27760/mypackage I/WhisperLink﹕ PlatformCoreManager - Registrar loaded. 09-22 14:52:16.263 27274-27760/mypackage I/WhisperLink﹕ PlatformCoreManager - ServiceDiscovery loaded. 09-22 14:52:16.268 27274-27760/mypackage I/WhisperLink﹕ DeviceManagerService - DeviceManagerService instanciating 09-22 14:52:16.275 27274-27760/mypackage I/WhisperLink﹕ PlatformCoreManager - DeviceManagerService loaded 09-22 14:52:16.349 27274-27760/mypackage I/WhisperLink﹕ PlatformCoreManager - AuthDaemonExternalService loaded. 09-22 14:52:16.352 27274-27760/mypackage I/WhisperLink﹕ PlatformCoreManager - AuthDaemonInternalService loaded. 09-22 14:52:16.420 27274-27760/mypackage I/WhisperLink﹕ PlatformCoreManager - loading routers 09-22 14:52:16.429 27274-27760/mypackage I/WhisperLink﹕ PlatformOptionsImpl - GenericAndroidPlatformInit for /data/data/mypackage/files 09-22 14:52:33.690 27274-27760/mypackage I/WhisperLink﹕ SecurityManagerFactory - Finished initializing SecurityManagerFactory 09-22 14:52:33.693 27274-27760/mypackage I/WhisperLink﹕ PlatformOptionsImpl - GenericAndroidPlatformInit for /data/data/mypackage/files 09-22 14:52:33.776 27274-27760/mypackage I/WhisperLink﹕ PlatformCoreManager - Loaded Service router for external transport=inet, secure=true 09-22 14:52:33.788 27274-27760/mypackage I/WhisperLink﹕ PlatformCoreManager - Loaded Service router for external transport=inet, secure=false 09-22 14:52:33.804 27274-27760/mypackage I/WhisperLink﹕ PlatformManager - Starting platform manager, counter=1 09-22 14:52:33.806 27274-27760/mypackage I/WhisperLink﹕ AccountHandler - Removed 0 authorizations with other devices. 09-22 14:52:33.816 27274-27760/mypackage I/WhisperLink﹕ GenericAndroidPlatform - Registering network state change listener, listener=com.amazon.whisperlink.platform.GenericAndroidNetworkStateChangeListener@420fedf0 09-22 14:52:33.824 27274-28045/mypackage I/WhisperLink﹕ NetworkStateChangeListener - onReceive intent : android.net.conn.CONNECTIVITY_CHANGE 09-22 14:52:33.851 27274-27760/mypackage I/WhisperLink﹕ PlatformCoreManager - Starting WP System servers... 09-22 14:52:33.978 27274-27760/mypackage I/WhisperLink﹕ RegistrarService - Registering service amzn.auth.in from package mypackage 09-22 14:52:34.065 27274-27760/mypackage I/WhisperLink﹕ RegistrarService - Registering service amzn.auth.ex from package mypackage 09-22 14:52:34.070 27274-28052/mypackage I/WhisperLink﹕ WPServer - CONNECTION_POLICY_ONE_PER_REMOTE_DEVICE curr services=[] new services=[] 09-22 14:52:34.089 27274-27760/mypackage I/WhisperLink﹕ RegistrarService - Registering service amzn.endpoint from package mypackage 09-22 14:52:34.097 27274-27760/mypackage I/WhisperLink﹕ RegistrarService - Registering service amzn.reg from package mypackage 09-22 14:52:34.106 27274-27760/mypackage I/WhisperLink﹕ RegistrarService - Registering service amzn.dmgr from package mypackage 09-22 14:52:34.111 27274-28052/mypackage I/WhisperLink﹕ WPServer - CONNECTION_POLICY_ONE_PER_REMOTE_DEVICE curr services=[] new services=[] 09-22 14:52:34.154 27274-27760/mypackage I/WhisperLink﹕ PlatformCoreManager - Start listening on external connections 09-22 14:52:34.154 27274-28063/mypackage I/WhisperLink﹕ JmdnsManager - Starting JMDNS 09-22 14:52:34.204 27274-28068/mypackage I/WhisperLink﹕ WhisperLinkUtil - Adding processor to WPServer :com.amazon.whisperplay.fling.media.controller.impl.RegistrarListener@4206f228: is data provider :false 09-22 14:52:34.214 27274-28068/mypackage I/WhisperLink﹕ WhisperLinkUtil - Adding processor to WPServer :com.amazon.whisperplay.fling.media.controller.impl.ProxyStatusCallback@41fc0ae0: is data provider :false 09-22 14:52:34.299 27274-28068/mypackage I/WhisperLink﹕ RegistrarService - Registering service wlink_cb_0_mypackage from package mypackage 09-22 14:52:34.348 27274-28068/mypackage I/WhisperLink﹕ RegistrarService - Registering service wlink_cb_1_mypackage from package mypackage 09-22 14:52:34.578 27274-28052/mypackage I/WhisperLink﹕ WPServer - CONNECTION_POLICY_ONE_PER_REMOTE_DEVICE curr services=[] new services=[] 09-22 14:52:34.697 27274-28068/mypackage I/WhisperLink﹕ DeviceCallbackRegistry - Adding callback, type=com.amazon.whisperlink.service.RegistrarCb, callback=[devicecb: device=[device: local=true, uuid=F28EC4A7796FDD3A1CF2943BB7D65E76], cb=Description(sid:wlink_cb_0_mypackage, friendlyName:null, accessLevel:0, security:0, flags:0, version:0), channel=memory, connInfo=null] 09-22 14:52:34.917 27274-28063/mypackage I/WhisperLink﹕ JmdnsManager - Not searching, account hint null or empty 09-22 14:52:36.058 27274-28063/mypackage I/WhisperLink﹕ AndroidHashServicesProvider - Insertion conflict hit, ignore. hash=t30gyEJ77o 09-22 14:52:36.075 27274-28063/mypackage I/WhisperLink﹕ JmdnsManager - Ignoring start, already started. 09-22 14:52:39.339 27274-28065/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Incoming connection from Device: 4BAE8E0747B2D9E03DFDA96B4A9AA129 to Service: amzn.dmgr Connection Id: 5233 Channel: inet 09-22 14:52:39.361 27274-28065/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Connection accepted for: sid: amzn.dmgr UUID: 4BAE8E0747B2D9E03DFDA96B4A9AA129 Device Type: 0 Connection Id: 5233 Channel: inet 09-22 14:52:39.392 27274-28156/mypackage I/WhisperLink﹕ TThreadPoolServiceRouter: INET: - Forwarding connection to Service: amzn.dmgr from Device: 4BAE8E0747B2D9E03DFDA96B4A9AA129 Connection Id: 5233 Channel: inet 09-22 14:52:39.429 27274-28156/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Initiating connection to Service: amzn.dmgr Connection Id: 5233 Channel: inet 09-22 14:52:39.481 27274-28157/mypackage I/WhisperLink﹕ DiscoveryManager - device found updated=true 09-22 14:52:39.510 27274-28157/mypackage I/WhisperLink﹕ RegistrarService - Invoking service added callback on device=[device: local=false, uuid=4BAE8E0747B2D9E03DFDA96B4A9AA129], service=amzn.auth.ex, explorer=mdns 09-22 14:52:39.552 27274-28157/mypackage I/WhisperLink﹕ RegistrarService - Invoking service added callback on device=[device: local=false, uuid=4BAE8E0747B2D9E03DFDA96B4A9AA129], service=amzn.dmgr, explorer=mdns 09-22 14:52:39.585 27274-28065/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Incoming connection from Device: EEF183F389227ACB3FF254C4A5A062F7 to Service: amzn.dmgr Connection Id: 2723 Channel: inet 09-22 14:52:39.623 27274-28173/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Initiating connection to Service: wlink_cb_0_mypackage Connection Id: 3291 Channel: memory 09-22 14:52:39.642 27274-28065/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Connection accepted for: sid: amzn.dmgr UUID: EEF183F389227ACB3FF254C4A5A062F7 Device Type: 0 Connection Id: 2723 Channel: inet 09-22 14:52:39.702 27274-28180/mypackage I/WhisperLink﹕ TThreadPoolServiceRouter: INET: - Forwarding connection to Service: amzn.dmgr from Device: EEF183F389227ACB3FF254C4A5A062F7 Connection Id: 2723 Channel: inet 09-22 14:52:39.764 27274-28180/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Initiating connection to Service: amzn.dmgr Connection Id: 2723 Channel: inet 09-22 14:52:39.793 27274-28181/mypackage I/WhisperLink﹕ DiscoveryManager - device found updated=true 09-22 14:52:39.828 27274-28181/mypackage I/WhisperLink﹕ RegistrarService - Invoking service added callback on device=[device: local=false, uuid=EEF183F389227ACB3FF254C4A5A062F7], service=amzn.auth.ex, explorer=mdns 09-22 14:52:39.887 27274-28181/mypackage I/WhisperLink﹕ RegistrarService - Invoking service added callback on device=[device: local=false, uuid=EEF183F389227ACB3FF254C4A5A062F7], service=amzn.dmgr, explorer=mdns 09-22 14:52:41.969 27274-28060/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Incoming connection from Device: 4BAE8E0747B2D9E03DFDA96B4A9AA129 to Service: amzn.dmgr Connection Id: 5233 Channel: inet 09-22 14:52:42.024 27274-28060/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Connection accepted for: sid: amzn.dmgr UUID: 4BAE8E0747B2D9E03DFDA96B4A9AA129 Device Type: 0 Connection Id: 5233 Channel: inet 09-22 14:52:42.050 27274-28206/mypackage I/WhisperLink﹕ WPServer - WorkerProcess: Starting UUID: 4BAE8E0747B2D9E03DFDA96B4A9AA129 Service Id: amzn.dmgr, Connection Id: 5233 Channel: inet 09-22 14:52:42.068 27274-28078/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Incoming connection from Device: F28EC4A7796FDD3A1CF2943BB7D65E76 to Service: wlink_cb_0_mypackage Connection Id: 3291 Channel: memory 09-22 14:52:42.120 27274-28078/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Connection accepted for: sid: wlink_cb_0_mypackage UUID: F28EC4A7796FDD3A1CF2943BB7D65E76 Device Type: 0 Connection Id: 3291 Channel: memory 09-22 14:52:42.141 27274-28210/mypackage I/WhisperLink﹕ WPServer - WorkerProcess: Starting UUID: F28EC4A7796FDD3A1CF2943BB7D65E76 Service Id: wlink_cb_0_mypackage, Connection Id: 3291 Channel: memory 09-22 14:52:43.175 27274-28220/mypackage I/WhisperLink﹕ DiscoveryManager - device found updated=true 09-22 14:52:43.191 27274-28220/mypackage I/WhisperLink﹕ RegistrarService - Invoking service added callback on device=[device: local=false, uuid=4BAE8E0747B2D9E03DFDA96B4A9AA129], service=amzn.dmgr, explorer=mdns 09-22 14:52:43.265 27274-28220/mypackage I/WhisperLink﹕ RegistrarService - Invoking service added callback on device=[device: local=false, uuid=4BAE8E0747B2D9E03DFDA96B4A9AA129], service=amzn.auth.ex, explorer=mdns 09-22 14:52:43.428 27274-28209/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Closing connection for Service: amzn.dmgr isClient: true Connection Id: 5233 Channel: inet 09-22 14:52:43.437 27274-28206/mypackage I/WhisperLink﹕ WPServer - WorkerProcess: Closing UUID: 4BAE8E0747B2D9E03DFDA96B4A9AA129 Service Id: amzn.dmgr, Connection Id: 5233 Channel: inet 09-22 14:52:43.449 27274-28209/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Closing connection for Service: amzn.dmgr isClient: false Connection Id: 5233 Channel: inet 09-22 14:52:43.480 27274-28206/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Closing connection for Service: amzn.dmgr isClient: false Connection Id: 5233 Channel: inet 09-22 14:52:44.615 27274-28060/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Incoming connection from Device: EEF183F389227ACB3FF254C4A5A062F7 to Service: amzn.dmgr Connection Id: 2723 Channel: inet 09-22 14:52:44.670 27274-28060/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Connection accepted for: sid: amzn.dmgr UUID: EEF183F389227ACB3FF254C4A5A062F7 Device Type: 0 Connection Id: 2723 Channel: inet 09-22 14:52:44.680 27274-28234/mypackage I/WhisperLink﹕ WPServer - WorkerProcess: Starting UUID: EEF183F389227ACB3FF254C4A5A062F7 Service Id: amzn.dmgr, Connection Id: 2723 Channel: inet 09-22 14:52:45.504 27274-28247/mypackage I/WhisperLink﹕ DiscoveryManager - device found updated=true 09-22 14:52:45.513 27274-28247/mypackage I/WhisperLink﹕ RegistrarService - Invoking service added callback on device=[device: local=false, uuid=EEF183F389227ACB3FF254C4A5A062F7], service=amzn.dmgr, explorer=mdns 09-22 14:52:45.572 27274-28247/mypackage I/WhisperLink﹕ RegistrarService - Invoking service added callback on device=[device: local=false, uuid=EEF183F389227ACB3FF254C4A5A062F7], service=amzn.auth.ex, explorer=mdns 09-22 14:52:45.639 27274-28238/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Closing connection for Service: amzn.dmgr isClient: true Connection Id: 2723 Channel: inet 09-22 14:52:45.648 27274-28234/mypackage I/WhisperLink﹕ WPServer - WorkerProcess: Closing UUID: EEF183F389227ACB3FF254C4A5A062F7 Service Id: amzn.dmgr, Connection Id: 2723 Channel: inet 09-22 14:52:45.650 27274-28238/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Closing connection for Service: amzn.dmgr isClient: false Connection Id: 2723 Channel: inet 09-22 14:52:45.686 27274-28234/mypackage I/WhisperLink﹕ TWhisperLinkTransport - Closing connection for Service: amzn.dmgr isClient: false Connection Id: 2723 Channel: inet
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Nick Gardner avatar image
Nick Gardner answered
Thanks Carlos for the logs. We see from the logs that the discovery process started successfully on your MotoG. It found 2 Android devices on your network. However, it failed to find the Fire TVs on your network. The root cause of that is not immediately clear from the logs - it could be some as yet unknown network issue. This is a tricky problem that we would like to resolve with your help. What will help us greatly is: - Setup a dedicated network for testing your app (e.g. a dedicated router/mobile hotspot) - Convey to us the network setup/topology (Devices in the network, their IP addresses, etc) - Complete logs on the Android device and the Fire TV - Network logs on the Android device, if possible Thanks and Best Regards, Nick
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Carlos avatar image
Carlos answered
It will probably take me a bit of time before I can setup an isolated network to test this but the other stuff I can probably get quicker. What do you mean by "network logs on the android device"? are you wanting packet captures or something like that?
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.