Tony Quan Posted June 18 Share Posted June 18 I'm fairly new to Control4. Using the Android app 324.21.0.6, Director version 3.3.0.628678-res. When I use the Android app to power on my Roku TV, no controls for the Roku are displayed (see screenshot). This works properly in iOS though on app version 324.21.0.2769 and used to work properly for me in Android, I don't believe I've changed anything that would impact this. The same symptom is observed on the wall touchpanel (I believe this runs Android as well?) . Would appreciate any suggestions. Quote Link to comment Share on other sites More sharing options...
ChrisHenderson Posted June 18 Share Posted June 18 Hello, @Tony Quan! Welcome to Control4! I'm terribly sorry it's not working on Android for you! I just chatted with one of the Android developers and he confirmed that this bug hasn't been reported yet. He says he'll look into it, but he needs a controller snapshot. It's a zip file that contains the controller and touchscreen logs. It can be generated via Composer, if you're a dealer. If you're not a dealer, could you ask your dealer to provide the snapshot and email it to me? I'll PM you my email address. Quote Link to comment Share on other sites More sharing options...
Tony Quan Posted June 18 Author Share Posted June 18 24 minutes ago, ChrisHenderson said: Hello, @Tony Quan! Welcome to Control4! I'm terribly sorry it's not working on Android for you! I just chatted with one of the Android developers and he confirmed that this bug hasn't been reported yet. He says he'll look into it, but he needs a controller snapshot. It's a zip file that contains the controller and touchscreen logs. It can be generated via Composer, if you're a dealer. If you're not a dealer, could you ask your dealer to provide the snapshot and email it to me? I'll PM you my email address. I'm not a dealer, so I'll ask my dealer for this. Quote Link to comment Share on other sites More sharing options...
Tony Quan Posted June 19 Author Share Posted June 19 in case anyone else runs into this, it is now being investigated by the Android engineering team at SnapOne. I'll post back when there's a fix. Quote Link to comment Share on other sites More sharing options...
msgreenf Posted June 19 Share Posted June 19 not an issue I can replicate on 5 Roku TVs Quote Link to comment Share on other sites More sharing options...
Tony Quan Posted June 20 Author Share Posted June 20 On 6/19/2024 at 11:44 AM, msgreenf said: not an issue I can replicate on 5 Roku TVs well, I can reproduce it always, so there must be some difference. Will see what engineering comes up with. Quote Link to comment Share on other sites More sharing options...
ChrisHenderson Posted June 28 Share Posted June 28 @Tony Quan The Android team looked at the logs. They can't reproduce the issue, but they believe that your project may be missing a "refresh navigators." Every time a dealer makes a change, they're supposed to refresh navigators so that the changes will be fully applied. There's a way to do it via the mobile apps as well. Could you go to "Settings > Support > Support Settings > Sync Settings > Sync my system". They say that if you still have problems after that they can look into it more. Just let me know if that fixes it for you. Quote Link to comment Share on other sites More sharing options...
Tony Quan Posted June 29 Author Share Posted June 29 @ChrisHenderson unfortunately “Sync my system” had no effect, the problem is still there. Let me know if there’s anything else to try. Quote Link to comment Share on other sites More sharing options...
Tony Quan Posted June 29 Author Share Posted June 29 @ChrisHenderson I also noticed that Android app version 324.23.0.7 released earlier this week. Updated to that version and the issue is still there even with “Sync my system” Quote Link to comment Share on other sites More sharing options...
ChrisHenderson Posted June 30 Share Posted June 30 Thanks for testing that out! I let them know that it didn't fix it. Quote Link to comment Share on other sites More sharing options...
Tony Quan Posted June 30 Author Share Posted June 30 @ChrisHenderson I also tried the app on a different Android phone with the same results. Quote Link to comment Share on other sites More sharing options...
Tony Quan Posted July 23 Author Share Posted July 23 The SnapOne team (thanks @ChrisHenderson) worked to reproduce this bug and has started working on a fix. It ended up reproducing on later iOS versions of the Control4 app also. Quote Link to comment Share on other sites More sharing options...
Tony Quan Posted August 9 Author Share Posted August 9 Version 324.29.0.13 of the Android app fixes this bug and is available in the Google Play Store. There is also a fix coming for the iOS version of this same bug, it should be in Apple's App Store in a couple of weeks according to @ChrisHenderson Quote Link to comment Share on other sites More sharing options...
ChrisHenderson Posted August 13 Share Posted August 13 @Tony Quan The Android team says that they didn't fix the issue yet. It could be a driver issue, or possibly simply the act of updating the app fixed it somehow? Either way, if you run into the problem again, feel free to reach out. It's hard to figure out why it broke if it's working again, but if it breaks again, we can take another look. Thanks so much for your help! We try to resolve bugs as quickly as possible, but sometimes we have several bugs we're looking into at the same time. We really appreciate your helpfulness in fixing the bug for iOS! Quote Link to comment Share on other sites More sharing options...
Tony Quan Posted August 21 Author Share Posted August 21 Today's release of the iOS app version 324.31.0.2870 fixed the similar issue on iOS. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.