theboomr

I'm not sure if there's some other fix coming, but I use rechargeable batteries and I've found that when this is occurring, swapping out for freshly charged batteries mitigates the issue.

I think what @LouP is saying is that if you have an activity already setup on the remote with, let's say, a TV, and an A/V receiver, for example, but then later you realize you want to add another device to that same activity, like an Xbox or streaming stick or something, the only way to add another device is to go back into the wizard, but then once you've selected the new device and continued through the steps of the wizard, any custom button mappings you had set up (like assigning rare misc functions to number keys or something like that) get reset to their default mappings. I have experienced this several times as well while fiddling and tweaking my setup.

Personally I would love to see a second-gen Skip remote (Skip 2S?) have separate play/pause buttons the same way Logitech's Harmony remotes did. There certainly seems to be room on the current button layout to just tack on another button right beneath the current play/pause one, at least externally. Not sure what it looks like internally. Probably would be nice to have as an elongated "rocker" style of button shape so you can easily feel each part of it without looking. But I know that's getting far ahead of where development is currently at :)

I think this is mostly the right solution (I have an LG C1 but I use a Chromecast with Google TV instead of the LG apps). The only issue I expect would be that in some apps, if you've moved to highlight some UI button other than the play/pause button while something is playing, then let the UI fade out, then click the Skip's Play/Pause button, it might click whatever button you had highlighted instead of just doing a play or a pause. Depends if the app keeps other buttons selected after the UI fades out.

Yeah, I am aware of the voltage difference so definitely considered that that could be causing the issue, I just haven't had issues with them in other devices (including lots of other remotes) thus far, so was hoping the Skip remote wouldn't be the first device to give me trouble with them. But if I find some disposable AAA batteries somewhere I'll make sure to try testing them in the Skip.

So status update for me, in regular usage of the remote the last few days since upgrading the firmware to 4.12.10, I've noticed that after the remote is idle for a while, it takes 2 button presses initially to "wake" it up. Doesn't make it unusable, but definitely a little annoying. Not sure if this is actually a bug in the firmware/settings, or if it's related to me now using rechargeable AAAs (high quality Eneloop ones, though) in the remote vs the disposable ones that shipped with it. I do not have any non-rechargeable batteries to test this theory unfortunately.

Ah, yep that was my issue, I was only messing with the slider on the LEDs tab not the Preferences tab

Ok I put some new batteries in and yeah, that fixed the issue with constant power reset on every button press. Thanks! @jason In response to your question, I currently am not really using the color wheel buttons for anything. I have had ideas about what to use them for but haven't tried using it at all yet while in this sort of troubleshooting mode with it. Once I'm getting a more stable experience I'll definitely be giving it a try. I also did set my brightness down to 25%. Doesn't seem like I can visually tell the difference on the remote between 25% and 100% brightness setting? Is that still expected, or should the different brightness levels actually be noticeably different now?

This firmware did fix it somewhat for me, since it retains which activity I had selected if it does the power reset thing. But, it's still doing that power reset with almost every single button press, so I still can't quickly scroll through lists or hold the volume keys.

Alrighty, wasn't able to sync from the Skip app even though it did stay connected, so I tried the updater again with 4.12.8 and this time it completed successfully to 100%, and now the remote is behaving normally again, I think. Haven't had a chance to test it much yet so we'll see if I run into the same issues the others were having with it becoming nonresponsive after some time.

Ok, I force closed the updater app then unplugged my remote. Seemed entirely nonfunctional, no lights at all when pressing buttons or activity buttons, so I took out the batteries for a minute then replaced them. When I would press buttons, the ring light would flash red repeatedly as long as I hold any button down. Now I've plugged it back in to my PC and opened the Skip app, which still detected it and connected fine, and now if I press buttons it does a slower flash of red 3 times. Will try reloading my profiles now.

I just downloaded the updater and the bin file, connected my remote, and tried the upgrade to 4.12.8. The updater is now frozen at 15%, and has gone to that grayed out state when an app is totally frozen in windows. Not sure what to do, is it safe to unplug my remote?

In this vein, I personally would love to see a future second iteration of the remote that has separate play and pause buttons. it's a tossup for a lot of apps on some devices if they will respond as expected to a remote than only explicitly sends pause or play. I liked my old Harmony remote having these as separate buttons.

No apology necessary at all! I totally get it. I figured it was probably all tied together, just wanted to report back here since the behavior I was seeing had changed from how it initially was happening, just in case that info would be useful.

@jason Maybe this will be a non-issue once we have your forthcoming fixes, but just wanted to post in this thread that this activity reset issue has become incredibly worse on my remote over the last few days. It now resets pretty much every single button press, even if I'm just sticking to activity A, it will just constantly reset (it's easy to tell it's resetting because the white ring light around the activity button turns off instantly with the button press, rather than glowing for the 2s timeout it's supposed to have), which makes it very difficult to consistently use the remote for anything, especially if I want to press and hold a button, like the volume buttons, for example. I'm not totally sure, but I feeeeel like this might've started happening after I had plugged the remote into my PC with the new updated app, but I don't know if anything there could've actually caused this or if that's just a coincidence. I have tried taking out the batteries and letting it sit for several minutes then putting them back in; no effect. I also tried reconnecting to my windows tablet where the app has always worked fine (and it's still running the older 0.9.4 718 app version), and changed a couple things then synced the remote again, but that also didn't help the issue at all.