Jump to content
Flirc Forums

jason

Administrators
  • Posts

    3,732
  • Joined

  • Last visited

  • Days Won

    229

Posts posted by jason

  1. Thank you. This was helpful. I think I understand what's going on. Give me about a week to work this out, do some tests, scope some signals, and I'll likely have an update soon. But I'm certain I understand now. 

    @furyflirc Tell me a bit about what you were doing when this happened. Was it sitting for a while and you pressed a button only to find it didn't work? Did it seem to fix itself after 30 seconds? Were you using it and it randomly stopped? Any chance you know the last button pressed?

    Regardless, I have a suspicion of what it is. I have thrown the remote, hammered all the buttons, sat on it. I can't reproduce it. However, I threw it in my bag, and when I pulled it out when I got home, it was stuck. I saved it by powering it externally, brought it to work, measured the power, and see that the processor is not in sleep. So it's not stuck asleep. It seems like it's stuck in a loop. Something called a watchdog timer should crash it after 5 seconds when it's stuck, and it's not. So it must be when that feature is disabled, and that's only in a couple spots. Stay tuned, and thanks for all the logs. Although they don't point to this, they point 'around' this.

  2. 2 hours ago, asyba said:

    Hi @jason since I update to gd911a15 did't have any crash/lock/dead , but today I click the button Profile A and it light two times and then it was dead, any other button nothing, so I follow the steps:

    Remote Model SKIP.1S.RELEASE.A06
    Firmware Version 4.12.23-0-gd911a15
    Skip app: 0.9.956 [Beta]

    Logs:

    <2>task_start(41): Hypnos: v4.12.23
    <1>malloc_addblock(61): Heap Block: 0x20002C0C - 0x20007BFF (19k)
    <1>log_rcause(378): BOD33 BOD12 SYST WDT EXT POR
    <1>log_rcause(385): F F T F F F
    <2>crash_report(208): ***** Hardware Exception *****
    <2>crash_report(212): ------------------------------
    <2>crash_report(213): r0: 0x0000d407
    <2>crash_report(214): r1: 0x00010214
    <2>crash_report(215): r2: 0x20007f28
    <2>crash_report(216): r3: 0x20007f23
    <2>crash_report(217): r12: 0x20002c70
    <2>crash_report(218): lr: 0x000112d0
    <2>crash_report(219): ra: 0x0000dc89
    <2>crash_report(220): xpsr: 0x0100dc09
    <2>crash_report(224): *******************************
    <1>init_remote(280): Initializing Past Profile: A
    <3>usb_hotplug(46): Connected

    First proc:

    {
    "USB": 86255
    }

    First: butt:
    It show really fast something like

    Sending message...

    but it disappear

    Other proc:

     
    {
    "USB": 300136
    }

    Other butt: same as before.

    After clicking any button of the remote, (light the white color of the profile).
    any "butt" commands respond something like depending the button I click.
    {
       "5": {
          "Released": 2440
       }
    }



    I got a new message that a new update to install : [0.9.957] , Should I install this?
    ...

    • Database - SMSL - SU-8
    • Firmware - Bug fix that can cause power leak
    • Firmware - Bug On power up where LED ring may not dislay
       

    I removed from PC, but remote is dead. I removed the batteries and put it again, same dead.
    I think the batteries got depleted, took almost 2 weeks...
    I think the crash/dead is auto restarting the remote, so I did't notice any "dead" behavior like old firm versions, but still is consuming batteries somehow... that is my thought not sure if the auto restar after crash is something that you added recently or is just my assumption.

    Thanks, very much appreciate the information. I did push an update v0.9.957 with new firmware that catches another issue like this. Please try it and repeat the process if it happens again.

    • Like 1
  3. What you are actually doing is pairing remote control buttons with keyboard keys. So inside the windows media center controller are the keyboard shortcuts specifically for windows media center. If you are using KODI those have different keyboard shortcuts and you should use that controller. If you want both, you need to add them both to the harmony. Does that make sense?

  4. We found a lot of issues bugs and edge cases. We were much farther than I anticipated. This next update. is where I thought this version would be. But we probably have 2 more until we are ready for this to roll into beta. The things that we are focused on is making sure that recording is reliable. I really don't want users to walk through, sync, only to find a bunch of buttons not working.

    So once we are confident in the recording, feedback, and stability, we will focus on re-editing and testing direct from the wizard.

    Locking thread, please test and follow up here: 

    Thanks for all the patience and feedback.

  5. 8 hours ago, laarj said:

    I updated the remote to 4.12.23. Prior to the update, I don't recall the version that was on the remote but the batteries lasted ~2.5 months. With 4.12.23, the new batteries lasted ~2 weeks. In addition, the remote has locked up several times and required the batteries removed to restore operation. 

    I have another update to solve one more edge case for battery drain. Regarding lockup, I need help to determine the reason. 

    When it locks up, wait 30 seconds, do NOT remove the battery.

    • After 30 seconds, Does the remote respond? Details please.
    • Without removing the batteries, via USB, connect to the SkipApp. Is the remote detected, does it respond?
    • What is your current Firmware Version
    • Go to the admin panel. go to the Logs Tab, Go to the sub Remote Logs tab. Hit refresh a few times. Attach the remote logs.
    • Go to the USB Tab and attach the results of the following commands (show us if anything is stuck)
      • "proc" Short for process
      • "butt" Short for buttons

    In the future, any posts without these details will just be removed. Really sorry, this thread is the bane of my existence. People not returning RMA's. People not following up with necessary details. A bunch of remotes returned had hardware issues that were in earlier builds. But I have 6 remotes, no lockups anymore. So please help me help you.

    CleanShot 2024-02-13 at 09.08.02.png

    CleanShot 2024-02-13 at 09.07.45.png

  6. Fairly close to a release candidate. List of what's still left is at the bottom.

    Critical - Learning requires both remotes to be facing each other and about 1 inch apart.

    Further detail here along in previous releases:
    Alpha 1
    Alpha 2
    Alpha 3
    Alpha 4
    Alpha 5

    Here is how it works:

    You need to be using the included firmware in order to do any recording. The version embedded is v4.13.2

    Changelog

    • Improved - Many Recording bugs
    • Improved - Decoding Library
    • Improved - Panasonic Decoding
    • Improved - Ability to capture x1 signals automatically
    • Improved - Manual Recording Overrides
    • Improved - Logging
    • Improved - User Feedback and Messaging during recording
    • Improved - Bad capture detection and feedback
    • Database - Updates
    • Fixed - Windows - Unable to connect with Server
    • Fixed - Bottom and Top bar z-index during wizard
    • Firmware - Battery Improvements

    Mac Download
    Windows Download
    Linux - We understand the issue, and have one more bug to solve. We're working on it.

    Firmware Update

    If you are not presented with update dialog, please follow the directions outlined here.

    What's Next

    • User config optimizations
    • More bad capture edge cases we are aware of
    • Updated Decoding Library
    • Save the button layout for later recall or editing
    • Save the button layout for user config export
    • Fix linux
    • Like 2
  7. 9 minutes ago, Lennard said:

    Hi Jason,

    I was trying the latest firmware it offered me (4.13.4-0-gaa92d6f) and as soon as I start recording, it says it can't connect to the server, when clicking on the first remote-button - even though my internet works. Am I'm doing anything wrong?

    Skip App version: 0.9.955.7168 [learning]

     

    Regards,
    Lennard

     

    Nope, this seems to be new, I'm looking into it.

  8. 1 hour ago, Aziraphale said:

    I'm afraid that I still have, very occasionally, that the remote "freezes" and I need to briefly disconnect one of the batteries. No big deal, but I thought you might want to know.

    Thank you for letting me know. I will add something to the next release to help diagnose this. 

  9. 1 hour ago, roland said:

    Understood. I was confused between device firmware vs software version. Will do!!! Also, why can't i choose dark mode for the app? It says "Follow System Settings" but why can't i just choose?

    It’s not implemented yet. With such  limited team we’re only focusing on needed features before jumping back to fixing style, animations, etc. 

  10. Fairly close to a release candidate. List of what's still left is at the bottom.

    Critical - Learning requires both remotes to be facing each other and about 1 inch apart.

    Further detail here along in previous releases:
    Alpha 1
    Alpha 2
    Alpha 3
    Alpha 4

    Here is how it works:

    You need to be using the included firmware in order to do any recording. The version embedded is v4.13.2

    Changelog

    • Improved - Recording bugs
    • Improved - Admin Panel record capture
    • Improved - User feedback during recording
    • Improved - Possible error feedback during record
    • Improved - Final animation
    • Fixed - Disable start record by clicking on slider item
    • Fixed - Slider Animation spacing
    • Fixed - Slider visual style
    • Fixed - Glitch on sliding blocks
    • Fixed - UX elements in compact mode

    Windows Download
    Mac Download
    Linux - We understand the issue, and have one more bug to solve. We're working on it.

    Firmware Update

    If you are not presented with update dialog, please follow the directions outlined here.

    What's Next

    • User config optimizations
    • 3 more known bug fixes
    • Save the button layout for later recall or editing
    • Save the button layout for user config export
    • Fix linux
    • Like 1
  11. The device that controls flirc. What is the profile you are using on the skip app?

    Where is the flirc located on the PC that's in your room?

    It wont turn off / turn on the computer. Can't do that over USB. You can go into sleep mode though. Pair a code in the Flirc USB app in media keys, suspend/wake. Add this to the Power Up and Power down activity.

  12. On 1/28/2024 at 8:05 AM, IanS said:

    I appreciate your comments, I just wasn't expecting to have to be an alpha tester to get simple functionality to work like AV switching on an LG TV

    this is what annoyed me. I have much more interesting things to do with my time that I actually want to be doing rather than spending it on Alpha testing,

    either way I have fed back my observations on what I've seen on the Alpha 3 (I think it was at the time.)

     

    Ian

    I appreciate your feedback. I'll spare the details, but the delay in this was a massive technical marathon that I did not anticipate. All the way from the firmware to the app, it was a massive bitch. We have one more bug and the next update will likely be a release candidate. I'm really sorry for the frustration but appreciate all the feedback, support, and patience. I know it does not appear so, but we only have a few people at the company. 

    • Like 1
×
×
  • Create New...