jason
-
Posts
2,989 -
Joined
-
Last visited
-
Days Won
132
Posts posted by jason
-
-
18 minutes ago, theboomr said:
My computer is a custom-built desktop, and it is my primary PC that I use for a lot of stuff every day so unfortunately shipping it to you wouldn't be a possibility for me. If I were the only one having this issue I would definitely just chalk it up to some weirdness with Windows 11 Insider builds (since I'm on the dev channel I get a lot of updates that introduce funky behavior semi-regularly).
Would it be helpful if I could do some kind of remote session with you to troubleshoot on my PC? Unfortunately I don't think I would have any time to do that tonight but probably tomorrow night I could (I'm in Colorado, Mountain time zone).We need to install all our dev tools and debugger on it and sit there playing with windows settings etc.
Anyone have an off the shelf machine that can be purchased online? I’m going to try and put together something tomorrow but I worry I’m going to spend a few hours on something that won’t even reproduce the problem.
-
21 hours ago, theboomr said:
The issue is occurring for me on Windows 11, insider version 22H2, build 25276.1000.
Also, with the latest version, the error behavior has changed a little bit for me. Now when I plug in the remote, the bottom left area just stays the same, disconnected, with no blips/changes, but the bottom center gray icon changes and gets stuck saying "CONNECTING...", even after unplugging the remote.
I've attached log with the 0.1.0.5282 version and the new behavior I see when plugging in and unplugging the remote.
I am using an administrator account.Sorry. What kind of computer do you have where the issue is? I’m going to buy one. I can’t reproduce it and the logs aren’t that helpful. I’m tearing my hair out.
Also another option is if someone is in the San Jose area or willing to send me a machine, I’ll cover all the costs. I’m getting desperate. Once we reproduce it, it’ll be easier to solve.
-
7 minutes ago, theboomr said:
Here's my log after doing the same steps with version 5287. Version 8288 (is that supposed to be 5288?) link still does not work though.
Also for the record, I tried installing the app on my Windows 10 Eve V tablet and there it works fine! So I'm only having this issue on Windows 11 (which I unfortunately only have installed on 1 computer in the house, so I can't test Win11 elsewhere). But at least I can actually try out using the remote, I'm not totally dead in the water :)Thank you. Last one is broken. Looking into it
-
Just now, wb6vpm said:
Fair enough, maybe either switch to AA, or over to a rechargeable Li-Ion battery via the USB-C port?
Definitely.
-
Just now, wb6vpm said:
Please reconsider no backlight stance in a future revision, it makes for a very difficult experience when trying to do things in the dark!
on 2xAAA it would have been a stretch. But definitely not out of the cards on future designs.
-
1 hour ago, theboomr said:
Here's my log after trying the first 4 versions. For each version I installed the updated version, launched the app, plugged in the remote (every time, it had the same behavior of not connecting and getting stuck in the bottom center at "CONNECTING..."), unplugged the remote, then closed the app.
I'll post another log once the links become valid for the last 2 versions.As always, thanks for getting back to us so quickly. If you have a chance to do the others, it would be greatly appreciated
-
56 minutes ago, Arnold said:
USB keyboard works also, checked.
Yeah. So flirc usb will work. PM. I’ll take care of you.
-
Needs a USB keyboard connected. Is that possible?
-
14 minutes ago, sWRbQTFGSIAW said:
Maybe the path we are finding isn't correct. Would you mind downloading this: USB Device Tree Viewer (uwe-sieber.de) saving the report, and posting that. I'd like to make sure the path we are trying to open is the same. Maybe it's being mangled.
-
Just now, sWRbQTFGSIAW said:
In the drop down, was there only the one?
-
4 minutes ago, AeroCluster said:
Just tried again, this time with SkipApp-0.1.0.5282. The behavior is slightly different than with the previous version.
Initially, the bottom center of the window will say "OFFLINE", and then after plugging in the remote, it will switch to "Ø CONNECTING". It usually stays there seemingly indefinitely though, and is grayed out. When it doesn't stay on "Ø CONNECTING", it just switches back to "OFFLINE".
Two log files this time. The first attempt was in Windows 10 Safe Mode with networking, and the second was back in normal Windows 10 after a reboot. The files are both bigger than the 2.27 MB filesize limit, so I'm including a Google Drive link instead: https://drive.google.com/drive/folders/1OL5laBp0DFFqwEvY0OChtOZBMqtvSOgE?usp=sharing
I'm running this on an Administrator account, and I didn't have the Flirc USB app running. I only had one instance of the SkipApp running, and I'm not even sure what the skip color picker is because I haven't done anything else with the software except try to get it to see my remote. I do have Malwarebytes installed, but it hasn't yelled at me about SkipApp, so I assume it hasn't interfered. I haven't been experiencing any USB issues with my PC other than this.
I ask about the malware/viruseware because I did see someone on stack overflow complaining that it changed the path of certain usb devices. Thanks for the logs, looking.
-
I have an idea. Drop the config.json file into the same file as the log folder. Restart the app. This will enable the admin window. Head on over to that. Send me a screenshot of the first window "USB"
Let me know if you see more than one Skip1s. Report results on trying to connect here to either of them.
-
I am really puzzled, there are reported no windows permission issues. It's like something else has the device opened. There are no instances of this app running? The skip color picker is not open? My other Flirc USB app? (although the flirc usb app should not open the remote). This is crazy.
-
2 minutes ago, dnalloheoj said:
Just for whatever it's worth, spinning up a W11 VM in VirtualBox and using USB passthrough works just fine. Remote stays connected. W10 vHost that experiences the same disconnect issues being discussed.
Can you post your windows 10 logs?
-
1 minute ago, jason said:
Losing my fucking mind:
CS ConnectTask V41KT9Q4SDQI91P3 ERROR Current|status:|Allowed
So it fails to open the device despite reporting back that it is allowed.
It should fail with;1. Disallowed by system
2. disallowed by user
3. Unknown
Do you have any virus protection apps installed?
-
1 minute ago, theboomr said:
The issue is occurring for me on Windows 11, insider version 22H2, build 25276.1000.
Also, with the latest version, the error behavior has changed a little bit for me. Now when I plug in the remote, the bottom left area just stays the same, disconnected, with no blips/changes, but the bottom center gray icon changes and gets stuck saying "CONNECTING...", even after unplugging the remote.
I've attached log with the 0.1.0.5282 version and the new behavior I see when plugging in and unplugging the remote.
I am using an administrator account.Losing my fucking mind:
CS ConnectTask V41KT9Q4SDQI91P3 ERROR Current|status:|Allowed
So it fails to open the device despite reporting back that it is allowed.
It should fail with;1. Disallowed by system
2. disallowed by user
3. Unknown
-
Just now, AeroCluster said:
If it's a permission issue, it might be related to the way MSIX installers work on Windows 10.
I don't know how they work on Windows 11, but on Windows 10 there's no "Run as Administrator" option in the right click menu for MSIX, unlike EXE files which do have that option.
This is just a shot in the dark though. I've never encountered MSIX installers before.
There is an XML file used to create the msix package and you have to explicitly call out the devices used to grant permission. It’s also strange that our windows 10 works fine.
Is everyone using an account that is an administrator?
-
-
The quick turnaround on feedback is really helping. Thank you so much.
We have it narrowed down. This seems to be a windows permission issue. This will provide a bit more context. Is anyone seeing the issue with Windows 11? Seems to be only Windows 10. -
Thanks, great feedback.
We have an animation that is supposed to play and we are going to update the UX to something closer to the attached.
This will change, but you can see it's much more flexible to test any button before you add something.
-
2 minutes ago, AeroCluster said:
Ok, I just tried it again with 0.1.0.5281. Seems like the possible improvement from pressing the "colors" button before connecting wasn't real, just a coincidence.
The remote connects for a few seconds whether I press any buttons on it right before plugging it in or not.
Here's the new log:
Thank you so much for the very quick response and patience. Can't tell you how much I appreciate it.
-
All helpful, here is another with even more logging. This wont solve anything, but will continue to give us more info.
FYI: A description of what we are debugging:
- Device is found
- Device is opened
- We send a command to the device
- Error, device is not open
- Uh oh, close the device
- Device successfully closed (How can this happen, if the device is not open)
-
1 minute ago, theboomr said:
0.1.0.5279 works for me on Windows 11!!
EDIT: I spoke too quickly, it seems to "almost" work. The "connected" dialog pops up and lasts a few seconds now, instead of just the blink of an eye, but then it goes back to disconnected again unfortunately.ah okay, throw us your log.
-
1 hour ago, sWRbQTFGSIAW said:
New update still not working.
All helpful, I don't think this one solves it, but it's going to help give us some more logs.
Skip App v0.9.4 Beta
in Beta Feedback
Posted
Anything else in that text box when you scroll down?