U honestly don’t understand why, I’m literally inside Google developer account and I can see pixel 8 supported in the list. I’m baffled.
I have Pixel 7 pro and also Pixel tablet and both work.
Ralf
Im rooted as well, if that makes a difference.
My devices are not rooted anymore.
Ralf
I think it’s showing like that for rooted devices?
I tried to hide root from the PlayStore, but no luck.
i assume you tried with Magisk? unfortuantly, i really unsure how to help with this
it seems like its an issue with rooted devices.
Yes. Added the Play store to the deny list, but no luck.
I hate sharing offline apk cause I really don’t want to maintain two update channels. But here is the latest apk this time, curious if offline will allow you. https://drive.google.com/file/d/1uEXJ1ksTQQttI4S8W3qusD5a9i0u0QLC/view?usp=drivesdk
Root has nothing to do with this. For me, I needed to update to the latest January update. I’m rooted, not hiding anything, and it works for me now.
EDIT: Also, use the direct link from the github page. Searching never seemed to find it. I think I checked after I updated, but had to use the direct link.
Thanks for that!
I’ve been trying all the name variants I could think of, in case there was a typo or “UC Remote Android” was incorrectly listed on Google Play…
I couldn’t see a direct link on the github page, just a huge (very detailed) readme…
It’s not necessarily obvious, but it’s the “Google Play Available” bit at the top of the readme.
Ah, now I see it… I didn’t realise they were links!
It’s a very nice implementation… but sadly, it doesn’t make the integrations any more stable or reliable.
Neither did I, GitHub isn’t the best with readability sometimes.
I don’t think the app could ever help with the stability of the integrations/ecosystem, and it’s not intended to.
It’s there as an alternate control method, especially useful for when the remote itself is low on battery (as is so often the case with the current status of the firmware).
i edited the README in GitHub to have a direct link to better visibility, check it out and let me know if its simpler to find the link and app name now.
The app is a mirror of the remote, it is not the remote and doesnt process anything, it uses a bidirectional traffic via APIs to see anything on the remote and make changes but the remote is still the main brain and driver, its acting the same as any app for any smart device. it is a companion app.
Yes, I understand. I was just a bit peeved that my SKY Q integration has just vanished!
What do u mean it vanished?
It wouldn’t connect, so I tried setting it up again, but it just timed out (I checked the Sky Q box was on and connected to the network & I could control it with Harmony). So I deleted the integration and went to reinstall it and couldn’t find it on the official list and it wasn’t in my custom integrations folder…
I’ll try restoring from a backup configuration when I get the chance.
Meanwhile, the Philips Hue integration needs setting up again, and SmartThings integration stopped working and won’t set up again, so I’ll have to delete and reinstall that again - at least I have the custom file to upload. I’m spending more time setting up & reinstalling integrations than actually using the Remote 3 !
Ok. First, this has nothing to do with this android app.
Second, sounds like you have something going on with your remote, I’d suggest to join the discord channel, go on the support channel and discuss there. What you’re describing indicates something going on, it must definitely doesn’t need to be this problematic but need more information from you to try and help. But it’s not relevant to this android app. Join the discord channel and we can try and help there to see what’s going on with your setup.
I developed the smartthings, sky q and others, it 100% doesn’t have the issues your describing