Fling service no longer detectable after 30min of inactivity

Question

question

tifr0z asked · Feb 04, 2016 at 07:05 AM

Fling service no longer detectable after 30min of inactivity

Context: I am using an iOS controller, with a custom media player which is a lightly customized version of the CustomPlayerSample.

After a fresh install, everything works as normal, the controller detects the player on the Fire TV device. But if I leave the player alone for over 30min, it becomes undetectable from the controller (e.g. the DiscoveryListener's deviceDiscovered() is never called - even though the InstallDiscoveryListener's installServiceDiscovered() is called and the version of the installed package is successfully retrieved).

I performed a similar test using the unaltered CustomPlayerSample. The player service was killed after 30min of inactivity as well, but it remained discoverable as normal after the 'kill' event.

So, it's pretty clear that there is an issue with the customizations made to CustomPlayerSample, but because the Fling discovery is a black box from the perspective of app developers, I am not sure where to look for candidate culprits. One hint I believe is the last line for the log extracts copied at the bottom of this message "DefaultService - Failed to create Description during DefaultService creation for service xyz" because this error did not show up when attempting to reproduce with the unaltered CustomPlayerSample.

Can someone help me make sense of this error message, and possibly provide pointers for troubleshooting?

-------------------- Extract from the logs (this is when the service gets killed, after 30min of inactivity) -------------------

02-03 17:12:51.309      482-498/? I/ActivityManager﹕ No longer want com.swishly.webtv.fireosplayer (pid 22457): empty for 1803s
02-03 17:12:51.329      482-493/? W/ActivityManager﹕ Scheduling restart of crashed service com.swishly.webtv.fireosplayer/.WebTVPlayerService in 5000ms
02-03 17:12:56.329      482-498/? I/ActivityManager﹕ Start proc com.swishly.webtv.fireosplayer for service com.swishly.webtv.fireosplayer/.WebTVPlayerService: pid=6054 uid=10004 gids={50004, 3003, 1028}
02-03 17:12:56.679    6054-6085/? E/WhisperLink﹕ TcommSettings - Exception obtaining value from settings cachecom.swishly.webtv.fireosplayer does not have the permission to read device settings;
02-03 17:12:56.829    6054-6085/? E/WhisperLink﹕ TcommSettings - Exception obtaining value from settings cachecom.swishly.webtv.fireosplayer does not have the permission to read device settings;
02-03 17:12:56.879    6054-6087/? E/WhisperLink﹕ DefaultService - Failed to create Description during DefaultService creation for service com.swishly.webtv.fireosplayer;

amazon fling

0

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

3 Answers

Answer 1 · 2016-03-03T11:00:14Z

Levon@Amazon answered · Mar 03, 2016 at 11:00 AM

Hi,

Sorry to hear that the fix is not it. The log lines you have listed in the original post do not affect the discovery then. We are unable to replicate the situation and hence need more information.

Could you please let us know the OS system software version on your Fire TV stick? Also, if possible, could you please send the entire 30 minute log until the discovery is stopped?

Thanks and Best Regards, Amazon Fling SDK Support Team

0 · Share

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Answer 2 · 2016-03-02T13:25:16Z

kal256 answered · Mar 02, 2016 at 01:25 PM

In fact this does not help. The same behaviour detected on HTC One M7 running Android 5.01. Fire TV Stick is visible around 10-15 minutes and after this you need to restart it in order to be discovered again.

0 · Share

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Answer 3 · 2016-02-23T12:32:01Z

Levon@Amazon answered · Feb 23, 2016 at 12:32 PM

Hi tifr0z,

To fix this, we have to add the following lines to the AndroidManifest.xml:

<!-- Permissions to read Device Settings Cache -->
<uses-permission android:name="com.amazon.dcp.settings.permission.READ_SETTINGS"/>
<!-- End of permissions to read Device Settings Cache -->

Thanks, Amazon Fling SDK Support Team

0 · Show 2 · Share

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

tifr0z · Oct 16, 2016 at 04:15 AM

Ugh...the 2 critical lines to add to the AndroidManifest.xml are no longer visible probably due to the forum's new format! @Levon@Amazon could you update your post to add the 2 missing configuration lines?

0 · Share ·

Levon@Amazon ♦ tifr0z · Oct 17, 2016 at 01:43 PM

Hi tifr0z, you are correct, seems like the transition to this forum removed all code snippets. Added now. Thanks!

0 · Share ·

Fling service no longer detectable after 30min of inactivity

question details

Related Questions