Jump to content
Flirc Forums

jason

Administrators
  • Posts

    3,732
  • Joined

  • Last visited

  • Days Won

    228

Posts posted by jason

  1. 17 hours ago, mechman said:

    Making a mention to @Nathan and @jason to bring this on the radar.

    Reading through a bit more of the forums I came across this post that seems to align with my issue. 

     

    If this was caused by my mistake I'll pony up for a new one, just looking to make sure I'm not missing anything obvious.

    Thanks!

    It's borked, send me a pm. 

  2. Happy Easter.

    Embedded is v4.12.26 which should has this fixed. The GUI is unstable. We have core libraries updated with a lot of fixes involved. Unfortunately, this was a necessary step, as we were falling behind with react native desktops public stable release. 

    There are things that could be broken, icons, crashes. Etc. But the firmware update should work, and you can revert back to the previous if it's giving you problems. But initial testing seems fine. We just not have tested everything yet.

    Linux Download
    Mac Download
    Windows Download

    • Like 4
  3. On 3/29/2024 at 4:04 AM, Droyellis said:

    Ask me for my skip profile again, I dare you

    Listen, I've got very little time, and I'm not posting binary images all over the forum for users to brick their devices because they don't know what they are doing or don't understand their are multiple hardware sku's. 

    The flirc config stores hashes. I know nothing about what it's receiving with those. In order for me to fix anything, I need to reproduce it. 

  4. 4 hours ago, wesdp1 said:

    After updating to the latest software and firmware the GUI must be open and must be the active window for any actions to happen.  If GUI is minimized or closed then no actions happen for an IR functions.  Open the GUI and make it the active window and it all works normally and responds to IR.

     

    This is not true. You can plug the USB into another device with no GUI software and it should work with the previously paired remote.

  5. Because the config is compressed, information is lost when put on the remote, and although I don't have a public way of reading it out, even if we did, it wouldn't tell us the device and manufacturer. But I would use my decoders to try and look it up.

    I have all the past firmwares posted on the forum somewhere. 

  6.  

     

    If the attached video doesn't work, here is cloud link: https://share.flirc.io/3196CdTQ

    This took me about 5 minutes to reproduce of pressing the B button. It is purely timing. If you press a profile button at an exact moment in time, we cause the issue. You do not need to press the profile button in repetition. It can be A/B/C/Color dots at the exact moment after any subsequent button. 

    I confirmed in lab today, in this state, it's stuck and using more power. So you might have pressed this sequence, put the remote down, come back the next day, see it stuck, and it would have had an impact on battery life. This was not the only issue that caused this in this thread. I fixed 3 other edge cases and documented them. I have also replaced a few remotes that were in the first batch of shipments, and completely unrelated.

    Firmware update coming, it's already solved. Just a matter of getting it into a release and publishing. Let's hope this is the last edge case.

    • Like 3
  7. I reproduced it and I fucking fixed it. Jesus christ. I'll post a video tomorrow. 

    I swear I sat here for 3 hours with logging pressing buttons until I got it to happen. I analyzed the logs until I saw a pattern, tried it, never got it to happen. But noticed it only happens after pressing a/b/c 

    It's strictly a timing issue. Edge case, and I understand why it can happen, but don't understand why it wont 'unstick'.

    But I handle these specific buttons in interrupt context. So I changed this. I queue them and move them into my normal task manager and it works fine.

    I'll push an update as soon as possible. GUI is currently a mess, so we need to clean it up. I'll look at some kinda remedy for everyone this week.

    • Like 2
  8. Just now, georgewagner23 said:

    I thought all the IR programming was done through the remote and USB just worked as an IR receiver. I've only ever used Logitech Harmony where the IR receiver was not programmed, just the remote. I honestly had no idea there was separate software for the the USB and the Skip1s remote. I thought the software I downloaded worked for both units. I plugged the USB into my laptop but nothing happened. After your reply, I did some searching and found the USB software but still didn't see the drop down to set the USB for the Shield. Long story short, I feel really stupid but happy to get it resolved.

    That shouldn’t be necessary unless there was a firmware upgrade. I’ll look into it 

  9. 20 minutes ago, georgewagner23 said:

    Just got my remote and i cannot get it to work with the Shield. USB dongle is plugged into the Shield, remote is programmed to only the Sheild. IR receiver is visible. I’ve rebooted, reprogrammed checked every setting I can think of and nothing, any advice. I looked at almost every post on here and haven’t found any solutions. 

    Is it programmed to Manufacturer: Flirc, Device: Shield?

    Make sure ADB Debugging is off.

  10. 46 minutes ago, roland said:

    The same thing has been happening with mine (I am on Alpha 3 firmware). Taking out the battery for few second helps to reboot the remote. It only happened with Alpha firmware that I need with button programing. Beta firmware before that I used I remembered did not have this problem. 

    It’s always after a period of no use right? Like you pick it up and it’s unresponsive. Not right in the middle of pressing during operating an activity?

  11. 3 hours ago, ajmxco said:

    I got the Skip 1s a few days ago and am having the same lock-up issue. Pulling the battery and waiting 30 seconds fixes the problem. I can't use the remote in this state and am ready to get a refund.

    Firmware version is 4.12.20-0-g37a2e44+ (see attached screenshot)

    I'm using the 0.9.965 version of the skip app in Linux and don't see and Admin page showing the log and/or firmware.

    Please help since I really want this to work. What do I do now?

     

    Screenshot_2024-03-19_16-53-57.png

    The latest firmware is 4.12.23. I'm not sure if firmware updates are going to work in linux unfortunately. I can supply a tool for linux, but unfortunately, I am absolutely swamped.

    4.12.23 will be better, but still has one bug. I'm working on it.

  12. 1 hour ago, Netscorpion said:

    I'm having some trouble with my Nvidia Shield Pro. I have a FLIRC USB plugged in, and have programmed the Skip 1S with the "FLIRC>Nvidia Shield Gen 2" profile. All the buttons work except play pause.

    Any advice on how to fix it? I think the issue with the IR code being transmitted because the physical button itself works but there is no action on my Nvidia Shield.

    consistent in all applications?

×
×
  • Create New...