You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Last week the options on Roku 2 changed from "Themes" to "Wallpapers and Screensavers" and there is no longer a place to change the screensaver settings, like switching up which folders it pulls from for the screensaver. My old Roku express did not make that change, and still works the same as it always did. I communicated with Roku for numerous days, and eventually, they told me I needed to ask the developer if the app still supported Roku 2. When I go into Wallpapers and Screensavers, and then click on PhotoView, it ends up taking me to the main app, which doesn't include the screensaver settings. Hopefully I attached these photos correctly.
The text was updated successfully, but these errors were encountered:
Here's a workaround if you're using a Roku:Go into Roku Photo Streams and connect it to your Google Photos account and ditch Google Photo View for now.
HTH
On Thursday, April 18, 2024 at 04:28:45 PM EDT, Robb ***@***.***> wrote:
I also am having this problem and came here for support for it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
Last week the options on Roku 2 changed from "Themes" to "Wallpapers and Screensavers" and there is no longer a place to change the screensaver settings, like switching up which folders it pulls from for the screensaver. My old Roku express did not make that change, and still works the same as it always did. I communicated with Roku for numerous days, and eventually, they told me I needed to ask the developer if the app still supported Roku 2. When I go into Wallpapers and Screensavers, and then click on PhotoView, it ends up taking me to the main app, which doesn't include the screensaver settings. Hopefully I attached these photos correctly.
The text was updated successfully, but these errors were encountered: