I never updated my Shield to Experience 9, so I haven’t gone through that downgrade process.
I did rebuild PMS from scratch with v1.24.5.5173 because I couldn’t figure out how to get Plex to start after copying the previous DB and metadata. No server start/stop buttons. I’m day 1 into what will be 4 days of Plex detecting intros and generating thumbnails.
As I keep saying here, the proper interim solution should be to downgrade Shield to prior version, and downgrade PMS to v.1.24.5. This is the most stable/functional configuration I’m aware of.
Super easy. I wish I had done that many days ago rather than put up with the pain of this current upgrade/hotfix nonsense. View this guide, ignore his “it is a very difficult task presentation” and just go for recovery image pointers and links to get NVIDIA stock image and ADB/fastboot drivers.
Even this one is still useful…
I have an android USB keyboard and A+B works fine. Don’t connect the shield to your PC before you have booted the shield in bootloader mode. Once you see that red menu then you can connect the USBA-USBA/USBC and install the driver. If you just connect the shield to PC in normal boot then your PC is going to see the shield as a MTB device and not install the ADB interface properly.
Then follow the commands in the NVIDIA instructions to transfer the 8.2.3 images to the box and boot… Took me less than an hour to do this process for my Shield 2019 Pro.
What do you mean “standby”? If you mean sleep, I set mine to “sleep now” and left it like that and couldn’t reproduce the problem.
So the screen saver needs to kick in while the scanning is happening? I’ve tried with the screen saver on and with the entire device in sleep. I have not tried letting the screen saver kick in during other PMS tasks.
Still being worked on. Android 11 permissions is a pain. Yes, we will update here with any news.
Yes, there is 1 issues we’ve identified, see Shield tv don't hw transcode. If HW transcoding is not working in a scenario other than what’s mentioned in that thread, I have not looked into it.
@redpoint5, @yooshaw, and @famzgb See if that thread fits your issue. Please post there and I will follow up in that thread. If it’s something else, please start a new thread with logs.
Unfortunately, seems like it does, so word of caution to anyone going down that route within your 1 year warranty:
Will Unlocking my Bootloader Void my Warranty?
Warning: Unlocking your Nvidia Shield’s bootloader will void the warranty, please note that even if you re-lock the bootloader the bootloader still show a flag that the device is voided for warranty.
Even better for you. I wouldn’t hesitate to use warranty if I paid for it. Send that back to whoever sold it and demand a box that works properly like how you bought it.
Today like yesterday I am unable to access PMS on the Shield over the network and smb also isn’t working. Today I tried accessing the internal storage using smb and it also doesn’t work so it’s not just the the external drive that is having issues.
After waking up the Shield it was completely frozen. It didn’t turn on the TV (CEC) but I manually turned on the TV and Plex was on the display but I couldn’t do anything. Still can’t access PMS over the network and smb isn’t working (internal and external storage).
This seems to primarily be a Shield issue with the new android.
I might have to downgrade. I also have a 2017 Shield that didn’t update and it’s working perfectly for me.
Same issue, something between Plex and Shield is now crashing PMS while the shield is sleeping. Seeing this as PMS not working in the morning, rebooting the Shield fixes it.
When I was Scanning Libraries to rebuild, the Scan would die and the Shield would eventually lock up, if the Shield was on and the screen saver came on. When I prevented that, the scan worked.
Now, overnight something happens so when I come back to it in the AM, the PMS is no longer running. Have to reboot the Shield. Not sure what’s causing it. It may be the 2am tasks but there’s no way to turn that off…
Since updating to this version of plex, I have had the most stability since the hotfix #2 was applied to my system.
I did a clear data/cache from the apps, system apps, area in android settings before installing this, and setup my libraries from scratch (annoying since this is the 10th time i have done so since all the issues started, but I only have a 2TB library of films, tv shows, and music).
I should also note that after installing, the permissions for file system access for the app was disabled again by default, I had to change this to “Allow” from “Do Not Allow” in the app permissions settings.
I also made sure to move library storage to adopted storage before setting up my libraries this time.
Since doing all this, I havent had any unexpected crashes, database corruption, etc… which i was getting almost every few hours with the previous .5410 update which was bundled with hotfix 2.
Hope this information helps. plex employees/testers, please contact if you need more information.
Thank you so much for the hard work over the last two weeks since this horrible update came out.
Do you suspect the tasks running has something to do it with it as it seems to happen overnight when these tasks are running and not during the day so would rule out time being an issue.
Yes, but I haven’t found anything consistent between users. I also have all the scheduled tasks enabled on my system and I can’t reproduce. There is something going on, just can’t narrow down the cause.
Yes before the updates were rolled out, I had plex library data moved to adopted storage, Internal (User), is how it shows up when selecting it from the plex settings.
I had done this because Plex data being on internal storage on my 2017 shield with 16gb was causing it to max out internal storage.
I should note that my developer settings are also enabled to “force allow apps to external” although this doesnt make a difference since Plex and Plex Media Server apps themselves cant be moved to external drive setup as adopted storage. As far as I know its only the Plex Data that is stored on the external drive adopted storage.
Is there a way of running the tasks individually for “normal” users? That way, I can run each of the tasks individually, and then wait to and see which one topples PMS? I know some of them can be triggered, but it would be good to have a script which runs and gives you progress once each one has run, and then it will show which one is causing the issue.
And due to the wide issues created with PMS crashing, creating a script button in Plex web and enabling it for specific users wouldn’t help? Should be an easy test, button to enable tasks to run, and progress report for each tasks and it’s success rate?
and just go for recovery image pointers and links to get NVIDIA stock image and ADB/fastboot drivers.
