@darwindesign, thank you for the explanation.
1 Like
Hi again, sorry for the delay. Part of it was no doubt a reaction to my first test with one of my better USB power meters. I plugged it into the USB2 port - power. I plugged it into the USB3 port - also power. I unplugged it, went off to find my USB resistive load - which I tested on a charger to check what the current draws were (1, 2 or 3A - so too much to plug into the Vero I assume) - went back to the Vero and plugged just the meter into USB3 again - no power! Did I just not plug it in far enough…??? I went back half an hour later with my best meter, power on both ports. Needless to say I was confused - it didn’t feel likely that I suddenly forgot how to properly plug in a USB device. However - on testing again now - it seems that jiggling the power meter in the USB3 slot is killing the power, so presumably some mechanical damage there. Would opening it up and looking at it under a microscope be appropriate, and resoldering the USB3 connections?
Thanks @thechrisgregory for your suggestion - I confirm that going to settings/system/input/peripherals only displayed CEC Adapter. (logs from startup here: https://paste.osmc.tv/ajehorejem)
osmc-remote-lircd was in brighter white text than all the other entries in settings/My OSMC/remotes, but I followed instructions, confirming it, and rebooted. Alas, no change - remote still doesn’t work, and it’s still not listed under settings/system/input/peripherals. Just checking, on that settings/My OSMC/remotes page, the “Disable RC6” appears to be enabled - I presume this is as intended.
I feel like my issue may also have appeared after a recent update. I hadn’t used the device for a while, came to use it, accepted an update presumably via the remote - but I’m unsure exactly how soon afterwards the remote didn’t work, so it could be unrelated.
Anyway - if repairing/resoldering the USB3 port is a good place to start, are there screws under the rubber feet - and any guides for disassembly? Thanks!
I’ve experimented a little further with the ‘disappearing OSMC RF Remote’ problem. Turns out that a full power cycle is required after a staging repo upgrade to make it re-appear.
After upgrading to vero564-image-4.9.269-78-osmc:arm64 from vero564-image-4.9.269-77-osmc:arm64 (staging repo, Dolby Vision Test builds) I once again noticed my OSMC RF remote was not working, and the vero was not responding to keypresses.
I was able to use my LG TV RF remote to navigate through the Vero-V menus. This time I tried a ‘soft’ reboot (power/reboot) and the remote still did not appear under settings/system/input/peripherals .
Then I tried a full power cycle (power/power off system), disconnected/reconnected the power supply,
and allowed the Vero-V to ‘cold’ boot.
Following this ‘cold restart’ (power cycle) the OSMC RF remote re-appeared under settings/system/input/peripherals along wih the CEC Adapter, and worked as expected.
There are some logs here - https://paste.osmc.tv/owivuwulod
Your logs show that the receiver is being detected.
… but it wasn’t detected after the ‘soft’ reboot …
So if you reboot the receiver is always undetected until a cold start?
I think we might need to split this thread out as other remote issues have since been solved
Sam