i am currently facing a weird issue.
I have the following setup:
1 aTV3 ( Gen before 2013 ) running Firmware 5.2 is working perfectly
1 aTV3 ( Gen 2013 Model A1469) running Firmware 7.2 (7512) restarts after playing 5 - 10 minutes of a movie or TV series.
DNS server on both aTV are set to: 192.168.178.13
Local IP Adress of device where plex-cponnect is installed: 192.168.178.13
plex-connect is running on a Windows 2012 R2
PMS version: 0.9.12.4
local IP adress where PMS is is installed on: 192.168.178.13
plex-connect version: 0.5-dev-020615
Description of the issue:
After playing a movie or TV series for 5 - 10 minutes, the new aTV3 restarts and i pushed back to the main menu of the aTV.
What i already tried:
Resuming the movie or TV series from where it stopped
Result: No picture, only sound is played.
Replaced the aTV3 with a new one, because i thought that the former one was defect.
Result: No improvement, issue still exists
Downgrade to a older Firmware version
Result: Failed, because Apple has only the latest Firmware signed for being installed with aTV3 Gen 2013 ( according to ipsw.me/all#AppleTV32 )
Transcode to 1080p 20Mbps, 1080p 8Mbps etc
Result: aTV3 is still restarting after 5 - 10 minutes
The only workarounds i currently have are:
Recode the movies and TV series to native aTV3 format ( .m4v ). The movie or TV show is runing without any issues in this format.
Restart the movie or TV series from beginning and forward to a time in the movie which lies behind the time where it crashes. From there the movie or TV series is running without any issues.
I have no clue why the new aTV3 is restarting and this is driving me nuts
Im not sure if its the newer iOS, PMS, PlexConnect or what exactly but its a known issue, the higher the resolution/audio track the sooner the aTV buffers/locks/reboots for some users. Unfortunately @iBaa and @Roidy only can code this wonderful code for aTV’s to view PMS content, plex.tv can only author PMS, apple can only author and design aTV’s and their firmware which is proprietary. Don’t expect a device with limited capabilities to not have issues, its a miracle that the PlexConnect developers even came up with this to begin with because the other way was only for jailbroken aTV2’s but even then the code wasn’t the problem, the hardware of the aTV2/3 just can’t handle it from what I can tell and constant reboots happen using heavier PIL enabled themes of PlexConnect just navigating thru the menus, xbmc/kodi reboots happen all the time viewing 720 content on aTV2’s and development is no longer maintained for them for a reason same with the old native plex app for aTV2 for a good reason, the device. If you looking to run higher bandwidth/audio content I would recommend a good PHT client or other client(s) with some decent specs until if when this can be resolved or recode all your content to .mkv. I wish I had a better solution for you but personally I do not.
I have had the same issue occasionally. Two movies that were guaranteed to cause this were very HD versions of Avatar and Planes Fire and Rescue. The ATV3 would reboot within minutes. The only fix was to download lesser HD copies of each movie. Very disappointing as the ATV3 is otherwise a good platform. I’m currently looking for a more elegant solution (Roku, WD TV?) or even installing a computer under the TV!
I have the same issues. The problem is memory pressure on the AppleTV. Every iOS app has to clean up memory if the OS sends a memory warning to the app. If the app ignores the message or can not clean up memory it gets killed by Apples memory status mechanism (jetsam).
The question for me is: why the heck all worked fine with ATV3 Rev.1 but with Rev.2 (the same config with the same PlexConnect server) the Trailers app get’s jetsamed all the time.
An why this occours only the first couple of minutes of a tv show. Continuing to watch the same show afterwards from where it was interrupted works fine.
I have the same issue. I pretty sure the problem is due to the last firmware of ATV (7.2)
I’m connected by WiFi. Is someone connected by network with same problems.
