SkipApp-0.9.955 with IR Learning - Alpha 4

[jason]

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

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

Alpha4

• Fixed - Dragable Buttons getting stuck
• Fixed - Elements / Tabs should not be during in wizard
• Fixed - Sync button should not be clickable during wizard
• Improved - UX elements in record and hover states
• Improved - UX style and animations during record

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

• Better Error Handling and user feedback during record process
• Better phone home for failures so I can quickly identify protocol trouble and issue quick fixes
• Smoother transition when we are done recording
• Automated handling for buttons that only send out one single signal
• Many Many bug fixes you probably don't see

[jason]

Edit, updated links, we had a strange bug where you could not sync the remote sometimes. It's been updated.

[asyba]

@jason today my batteries die again.
but with the previous firmare from https://forum.flirc.tv/index.php?/topic/13729-skipapp-09955-with-ir-learning-alpha-3/#comment-32788
I connected a pair of rechargeable batteries (not fully charge). 
I connected to the PC but logs are empty, after clicking Refresh it log this:

<2>task_start(41): Hypnos: v4.13.4
<1>malloc_addblock(61): Heap Block: 0x200030E8 - 0x20007BFF (18k)
<1>log_rcause(383): BOD33 BOD12 SYST WDT EXT POR
<1>log_rcause(390):     F     F    T   F   F   F
<2>init_remote(261): Low Battery
<1>init_remote(280): Initializing Past Profile: B
<3>usb_hotplug(36): Disconnected
<3>usb_hotplug(46): Connected
<3>learn(85): learn called with: Enable
<3>learn(85): learn called with: Disable

I guess there is no way to save the exception error logs that probably drain the battery?

 

[asyba]

when trying to Sync, without batteries. Mac 

NSInvalidArgumentException - *** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[2]

[jason]

it wasn't dead. It looks like a crash. It takes a long time to reset. I'll reduce the timeout so I can see where it crashed.

[asyba]

@jason are you talking about the app or the batteries comment?
I tried putting again the "dead" batteries and I can click three times an activity button, I can see the light turn on, but then is not doing anything after 2-3 click, low battery I guess ..?
Should I update to Alpha 4 or keep on 3 and report/help issues with another pair of batteries? 

[jason]

2 hours ago, asyba said:

@jason are you talking about the app or the batteries comment?
I tried putting again the "dead" batteries and I can click three times an activity button, I can see the light turn on, but then is not doing anything after 2-3 click, low battery I guess ..?
Should I update to Alpha 4 or keep on 3 and report/help issues with another pair of batteries? 

These are rechargeable? The issue with rechargeable is the low voltage. These tend to hang around the 'dead' battery voltage of normal batteries despite having plenty of current. You can post a video and I can confirm. I can do a few things in firmware to detect and maybe prevent an under voltage lockout, just not on my list of things to do at the moment.

[asyba]

@jason managed to get error logs.
the ones with the issue are not rechargeable they are generics, LR03 1.5V (https://www.simplicity.com.ar/pilas-alcalinas-simplicity-aaa-troquelada/p)
what I did: put the "dead" batteries , then click 3 times any button and then it "shutdown", then I connected to the PC with the batteries, and check logs and found this.
(I reproduce it two times, so two logs sessions.)
Maybe it helps or maybe they are normal logs.
Note: I don't see a low battery message in the log that I looked that before when using a rechargeable batteries.
I can record a video if that still is needed after you analyze the logs, let me know.

<2>task_start(41): Hypnos: v4.13.4

<1>malloc_addblock(61): Heap Block: 0x200030E8 - 0x20007BFF (18k)

<1>log_rcause(383): BOD33 BOD12 SYST WDT EXT POR

<1>log_rcause(390): F F T F F F

<2>crash_report(208): ***** Hardware Exception *****

<2>crash_report(212): ------------------------------

<2>crash_report(213): r0: 0x0000d88b

<2>crash_report(214): r1: 0x000108dc

<2>crash_report(215): r2: 0x20007f28

<2>crash_report(216): r3: 0x20007f23

<2>crash_report(217): r12: 0x2000314c

<2>crash_report(218): lr: 0x00011ac0

<2>crash_report(219): ra: 0x0000e10d

<2>crash_report(220): xpsr: 0x0100e08d

<2>crash_report(224): *******************************

<1>init_remote(280): Initializing Past Profile: A

<3>usb_hotplug(46): Connected

<2>default_handler(163): Down pressed

<2>default_handler(163): Down released

<2>default_handler(163): Down pressed

<2>default_handler(163): Down released

<2>default_handler(163): Okay pressed

<2>default_handler(163): Okay released

<2>default_handler(163): Up pressed

<2>default_handler(163): Up released

<2>default_handler(163): Right pressed

<2>default_handler(163): Right released

<2>default_handler(163): Left pressed

<2>default_handler(163): Left released

 

—

<2>task_start(41): Hypnos: v4.13.4

<1>malloc_addblock(61): Heap Block: 0x200030E8 - 0x20007BFF (18k)

<1>log_rcause(383): BOD33 BOD12 SYST WDT EXT POR

<1>log_rcause(390): F F T F F F

<2>crash_report(208): ***** Hardware Exception *****

<2>crash_report(212): ------------------------------

<2>crash_report(213): r0: 0x0000d88b

<2>crash_report(214): r1: 0x000108dc

<2>crash_report(215): r2: 0x20007f28

<2>crash_report(216): r3: 0x20007f23

<2>crash_report(217): r12: 0x2000314c

<2>crash_report(218): lr: 0x00011ac0

<2>crash_report(219): ra: 0x0000e10d

<2>crash_report(220): xpsr: 0x0100e08d

<2>crash_report(224): *******************************

<1>init_remote(280): Initializing Past Profile: A

<3>usb_hotplug(46): Connected

<2>default_handler(163): Down pressed

<2>default_handler(163): Down released

<2>default_handler(163): Down pressed

<2>default_handler(163): Down released

[jason]

1 minute ago, asyba said:

@jason managed to get error logs.
the ones with the issue are not rechargeable they are generics, LR03 1.5V (https://www.simplicity.com.ar/pilas-alcalinas-simplicity-aaa-troquelada/p)
what I did: put the "dead" batteries , then click 3 times any button and then it "shutdown", then I connected to the PC with the batteries, and check logs and found this.
(I reproduce it two times, so two logs sessions.)
Maybe it helps or maybe they are normal logs.
Note: I don't see a low battery message in the log that I looked that before when using a rechargeable batteries.
I can record a video if that still is needed after you analyze the logs, let me know.

<2>task_start(41): Hypnos: v4.13.4

<1>malloc_addblock(61): Heap Block: 0x200030E8 - 0x20007BFF (18k)

<1>log_rcause(383): BOD33 BOD12 SYST WDT EXT POR

<1>log_rcause(390): F F T F F F

<2>crash_report(208): ***** Hardware Exception *****

<2>crash_report(212): ------------------------------

<2>crash_report(213): r0: 0x0000d88b

<2>crash_report(214): r1: 0x000108dc

<2>crash_report(215): r2: 0x20007f28

<2>crash_report(216): r3: 0x20007f23

<2>crash_report(217): r12: 0x2000314c

<2>crash_report(218): lr: 0x00011ac0

<2>crash_report(219): ra: 0x0000e10d

<2>crash_report(220): xpsr: 0x0100e08d

<2>crash_report(224): *******************************

<1>init_remote(280): Initializing Past Profile: A

<3>usb_hotplug(46): Connected

<2>default_handler(163): Down pressed

<2>default_handler(163): Down released

<2>default_handler(163): Down pressed

<2>default_handler(163): Down released

<2>default_handler(163): Okay pressed

<2>default_handler(163): Okay released

<2>default_handler(163): Up pressed

<2>default_handler(163): Up released

<2>default_handler(163): Right pressed

<2>default_handler(163): Right released

<2>default_handler(163): Left pressed

<2>default_handler(163): Left released

 

—

<2>task_start(41): Hypnos: v4.13.4

<1>malloc_addblock(61): Heap Block: 0x200030E8 - 0x20007BFF (18k)

<1>log_rcause(383): BOD33 BOD12 SYST WDT EXT POR

<1>log_rcause(390): F F T F F F

<2>crash_report(208): ***** Hardware Exception *****

<2>crash_report(212): ------------------------------

<2>crash_report(213): r0: 0x0000d88b

<2>crash_report(214): r1: 0x000108dc

<2>crash_report(215): r2: 0x20007f28

<2>crash_report(216): r3: 0x20007f23

<2>crash_report(217): r12: 0x2000314c

<2>crash_report(218): lr: 0x00011ac0

<2>crash_report(219): ra: 0x0000e10d

<2>crash_report(220): xpsr: 0x0100e08d

<2>crash_report(224): *******************************

<1>init_remote(280): Initializing Past Profile: A

<3>usb_hotplug(46): Connected

<2>default_handler(163): Down pressed

<2>default_handler(163): Down released

<2>default_handler(163): Down pressed

<2>default_handler(163): Down released

This is helpful. Can you post your configuration too?

[asyba]

@jason here https://pastebin.com/5Z8s3U2x
this are the "Slimmed Down Config"

[asyba]

here managed to put the complete version https://pastebin.com/8i0u9PbS

[jason]

7 hours ago, asyba said:

here managed to put the complete version https://pastebin.com/8i0u9PbS

It doesn't happen with the other batteries?

Is it plugged in at the time? 

[asyba]

@jason could be that my control configuration is corrupted?
I added some delays because is wasn't working properly lately , and is working kind of bad, like is not waiting.
not sure if its the battery or the config. but connected to the PC it works.

https://pastebin.com/VfP2w6mn

https://youtube.com/shorts/nSbAEpoiorA?si=iSOBRPcleDUDw0MQ

[jason]

6 hours ago, asyba said:

@jason could be that my control configuration is corrupted?
I added some delays because is wasn't working properly lately , and is working kind of bad, like is not waiting.
not sure if its the battery or the config. but connected to the PC it works.

https://pastebin.com/VfP2w6mn

https://youtube.com/shorts/nSbAEpoiorA?si=iSOBRPcleDUDw0MQ

It's the battery, and they don't look like 30%... Looks like full brightness. I tried your config, and it was fine here. 

The reason why the colors don't work, is because each quadrant is 3 leds. So 3*4 is 12 LEDs. Plus the Profile. It uses much more current. The batteries you are using are not good. Do you have a battery tester? When they. are new, they read 1.5-1.6 Volts. When they are dead, they are around 1.2V.

[Cape]

I have tried to record buttons from three different remotes with alpha 1, 2 and now 4. Sometimes the progress bar seems to move all the way and record the button but then I am asked to record again, other times the progress bar just goes half way or does not move at all. Either way i never seem to be able to move forward in the setup process. What could be causing this? As mentioned, i have tried 3 different remotes, and have had them faceing the Skip 1s one inch or less apart.

[jason]

15 minutes ago, Cape said:

I have tried to record buttons from three different remotes with alpha 1, 2 and now 4. Sometimes the progress bar seems to move all the way and record the button but then I am asked to record again, other times the progress bar just goes half way or does not move at all. Either way i never seem to be able to move forward in the setup process. What could be causing this? As mentioned, i have tried 3 different remotes, and have had them faceing the Skip 1s one inch or less apart.

Most of the work that we've been doing is this. Improving accuracy, decoding, and user feedback. I was hoping to have this up tonight, but there is one more bug we're trying to solve. Early next week. But hopefully the next one will be a release candidate. Very sorry. We are working hard on it.

[Cape]

12 hours ago, jason said:

Most of the work that we've been doing is this. Improving accuracy, decoding, and user feedback. I was hoping to have this up tonight, but there is one more bug we're trying to solve. Early next week. But hopefully the next one will be a release candidate. Very sorry. We are working hard on it.

No worries! I just wanted to know if it was some sort of handling error on my part. good to hear that you are close to a solution :)

[jason]

28 minutes ago, asyba said:

it happen again, I tried this time holding a button and no tacking the batteries, but still nothing connected to de pc, but it did't turn on, then hold again button but nothing, and after a few seconds it light up, and then I check logs but no errors and no low battery message this time.
<2>task_start(41): Hypnos: v4.13.4
<1>malloc_addblock(61): Heap Block: 0x200030E8 - 0x20007BFF (18k)
<1>log_rcause(383): BOD33 BOD12 SYST WDT EXT POR
<1>log_rcause(390):     F     F    F   T   F   F
<1>init_remote(280): Initializing Past Profile: A
<3>usb_hotplug(46): Connected
<2>default_handler(163): 1 pressed
<2>default_handler(163): 1 released
<3>learn(85): learn called with: Enable
<3>learn(85): learn called with: Disable
<2>default_handler(163): RW pressed
<2>default_handler(163): RW released
 

It's the batteries. Can you go to the public version of software, you'll be prompted to 'upgrade' your firmware where it will restore the latest public stable. Also, when and where did you get the remote? 

*EDIT* 

I'm removing most of these conversations. They have nothing to do with learning.

[asyba]

@jason fine I will post future batteries post related here https://forum.flirc.tv/index.php?/topic/12049-battery-does-not-last-for-more-than-a-day/page/4/
I bought it from public page https://flirc.tv/products/skip1s-remote-universal-remote-control?variant=43489094729960
my order is #SHOP-37530  Nov 1, 2023

[jason]

New release ready fro test: