New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Freeze bug #172

Closed
mondalaci opened this Issue Sep 13, 2018 · 90 comments

Comments

Projects
None yet
@mondalaci
Copy link
Member

mondalaci commented Sep 13, 2018

Firmware versions larger than 8.2.5 sometimes freeze. When it happens, your UHK gets unresponsive all of a sudden. Your UHK may not be affected at all, or it can take hours, days or even weeks for the freeze to hit.

The reason we haven't yet fixed this bug is because it happens so rarely, and only on certain UHKs. We need your feedback, so if you're reading this please update to firmware 8.4.5 via Agent.

If your UHK freezes, run the following script and paste its output to provide diagnostics information, so that we can hopefully figure out what the hell is going on. (You'll need another keyboard to do this if your UHK froze).

Pull the Agent repo and build it. Then run packages/usb/get-debug-info.js. It'll output something like this:

I2cWatchdog:919988055 | I2cSlave:306651339 | I2cWatch:950237 | I2cRecovery:0 | KeyMatrix:783778471 | UsbReport:157778114 | Time:101366130 | UsbGeneric:237 | UsbBasic:41632 | UsbMedia:252 | UsbSystem:4 | UsbMouse:110380
I2cWatchdog:919997815 | I2cSlave:306654592 | I2cWatch:950247 | I2cRecovery:0 | KeyMatrix:783783350 | UsbReport:157782993 | Time:101367237 | UsbGeneric:238 | UsbBasic:41632 | UsbMedia:252 | UsbSystem:4 | UsbMouse:110380
I2cWatchdog:920007573 | I2cSlave:306657846 | I2cWatch:950257 | I2cRecovery:0 | KeyMatrix:783788300 | UsbReport:157787816 | Time:101368361 | UsbGeneric:239 | UsbBasic:41640 | UsbMedia:252 | UsbSystem:4 | UsbMouse:110380
I2cWatchdog:920017331 | I2cSlave:306661098 | I2cWatch:950267 | I2cRecovery:0 | KeyMatrix:783793238 | UsbReport:157792640 | Time:101369482 | UsbGeneric:240 | UsbBasic:41644 | UsbMedia:252 | UsbSystem:4 | UsbMouse:110380
I2cWatchdog:920027090 | I2cSlave:306664351 | I2cWatch:950277 | I2cRecovery:0 | KeyMatrix:783798182 | UsbReport:157797462 | Time:101370593 | UsbGeneric:241 | UsbBasic:41644 | UsbMedia:256 | UsbSystem:4 | UsbMouse:110380
I2cWatchdog:920036849 | I2cSlave:306667604 | I2cWatch:950287 | I2cRecovery:0 | KeyMatrix:783803092 | UsbReport:157802316 | Time:101371711 | UsbGeneric:242 | UsbBasic:41644 | UsbMedia:258 | UsbSystem:4 | UsbMouse:110380
I2cWatchdog:920046607 | I2cSlave:306670858 | I2cWatch:950297 | I2cRecovery:0 | KeyMatrix:783808105 | UsbReport:157807084 | Time:101372838 | UsbGeneric:243 | UsbBasic:41644 | UsbMedia:269 | UsbSystem:4 | UsbMouse:110380
I2cWatchdog:920056367 | I2cSlave:306674110 | I2cWatch:950307 | I2cRecovery:0 | KeyMatrix:783812989 | UsbReport:157811962 | Time:101373962 | UsbGeneric:244 | UsbBasic:41644 | UsbMedia:270 | UsbSystem:4 | UsbMouse:110380
I2cWatchdog:920066125 | I2cSlave:306677364 | I2cWatch:950317 | I2cRecovery:0 | KeyMatrix:783821101 | UsbReport:157814081 | Time:101375047 | UsbGeneric:245 | UsbBasic:41644 | UsbMedia:270 | UsbSystem:4 | UsbMouse:110531
I2cWatchdog:920075884 | I2cSlave:306680616 | I2cWatch:950327 | I2cRecovery:0 | KeyMatrix:783831414 | UsbReport:157814333 | Time:101376086 | UsbGeneric:246 | UsbBasic:41644 | UsbMedia:270 | UsbSystem:4 | UsbMouse:110783
I2cWatchdog:920085643 | I2cSlave:306683869 | I2cWatch:950337 | I2cRecovery:0 | KeyMatrix:783838898 | UsbReport:157816997 | Time:101377160 | UsbGeneric:247 | UsbBasic:41644 | UsbMedia:270 | UsbSystem:4 | UsbMouse:110904

One line will be displayed per second. Most variables should be incrementing all the time automatically, but you'll have to manually increment some. Make sure to increment UsbBasic by typing regular scancodes on your UHK. Make sure to increment UsbMedia by typing media scancodes (for example volume up and down) on your UHK. Make sure to increment UsbMouse by mousing with your UHK. As for UsbSystem, you can increment it by typing system scancodes such as sleep, but this one is not terribly important. Every other variable should be incrementing automatically all the time with the exception of I2cRecovery which may spontaneously increment once in a while.

@mondalaci mondalaci self-assigned this Sep 13, 2018

@mondalaci mondalaci added the bug label Sep 13, 2018

@joshginter

This comment has been minimized.

Copy link

joshginter commented Sep 13, 2018

My freezes up to this point show no output from that script. It seems like the whole HID communication gets locked up. Do you expect that to be different for other freezes?

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Sep 13, 2018

I'm not sure, but I hope so. Otherwise folks won't be able to supply us information of what goes on inside of their UHKs without a debug probe.

@tigerkeys

This comment has been minimized.

Copy link

tigerkeys commented Sep 14, 2018

Is there a way to run the debug script under windows? Agent under windows says Cannot write to HID device.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Sep 14, 2018

The debug script should work under every OS. Agent or the script says "Cannot write to HID device"?

@tuxlifan

This comment has been minimized.

Copy link

tuxlifan commented Sep 14, 2018

Could you provide the debug script as AppImage? To install npm just to provide debug info seems a bit inconvenient (not that I have yet experienced a freeze yet, but I only just upgraded the firmware...). Thanks!

@joshginter

This comment has been minimized.

Copy link

joshginter commented Sep 15, 2018

Agent gets a little red error "toast" in the app that has that message. It happened unexpectedly otherwise I'd have tried to take a screen shot.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Sep 16, 2018

@tuxlifan Thanks for the idea! We'll look into it.

@ert78gb Is there a way to add the agent/packages/usb/get-debug-info.js script to the AppImage, so that users can easily execute it without building Agent? I assume it's problematic because it depends on node and libraries, so I don't think there's an easy way.

@joshginter When does this toast error happens? Totally random or upon freezes? Do you remember the message?

@ert78gb

This comment has been minimized.

Copy link
Collaborator

ert78gb commented Sep 17, 2018

@mondalaci We could add agent/packages/usb/get-debug-info.js to the AppImage or any package, but this js file is not enough. Need the agent/packages/usb/uhk.js and the whole node_modules folder.

The whole node-hid package and the usb handler codes deployed in the app.asar file. I think duplicate everything is not a good solution.

I suggest to create a command line argument --freeze-debug-info=true and when it passed to the agent app it will start to write the debug info into the console instead of start the ui.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Sep 17, 2018

@ert78gb Great idea! I think we should rather wait until the next monthly update though. I'll ask people to share their experience regarding the freeze. It may turn out that it's a non-issue on every but a handful of UHKs which are faulty in some ways.

@joshginter

This comment has been minimized.

Copy link

joshginter commented Sep 17, 2018

Sorry. I confused this case and the old one. I originally thought you were asking me about the error because I mentioned in in my previous report on my most recent failure. I only saw it when I unplugged the frozen UHK. Sorry for the confusion.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Sep 18, 2018

@joshginter No problem, appreciate your feedback!

@Jopie01

This comment has been minimized.

Copy link

Jopie01 commented Sep 19, 2018

Got a freeze yet, but during an update of my Fedora Linux. The dmesg shows that the USB disconnected:
usb 4-1: USB disconnect, device number 4

Then messages show up:

[ 8332.839477] usb 4-1: new full-speed USB device number 5 using ohci-pci
[ 8332.979473] usb 4-1: device descriptor read/64, error -62
[ 8333.234446] usb 4-1: device descriptor read/64, error -62
[ 8333.477542] usb 4-1: new full-speed USB device number 6 using ohci-pci
[ 8333.624464] usb 4-1: device descriptor read/64, error -62
[ 8333.871453] usb 4-1: device descriptor read/64, error -62
[ 8333.979526] usb usb4-port1: attempt power cycle
[ 8334.427439] usb 4-1: new full-speed USB device number 7 using ohci-pci
[ 8334.843416] usb 4-1: device not accepting address 7, error -62
[ 8334.979391] usb 4-1: new full-speed USB device number 8 using ohci-pci
[ 8335.396418] usb 4-1: device not accepting address 8, error -62
[ 8335.396474] usb usb4-port1: unable to enumerate USB device
[ 8337.580348] usb 4-1: new full-speed USB device number 9 using ohci-pci
[ 8337.721376] usb 4-1: device descriptor read/64, error -62
[ 8337.969353] usb 4-1: device descriptor read/64, error -62
[ 8338.211351] usb 4-1: new full-speed USB device number 10 using ohci-pci
[ 8338.352406] usb 4-1: device descriptor read/64, error -62
[ 8338.600371] usb 4-1: device descriptor read/64, error -62
[ 8338.707402] usb usb4-port1: attempt power cycle
[ 8339.155356] usb 4-1: new full-speed USB device number 11 using ohci-pci
[ 8339.571340] usb 4-1: device not accepting address 11, error -62
[ 8339.707345] usb 4-1: new full-speed USB device number 12 using ohci-pci
[ 8340.123351] usb 4-1: device not accepting address 12, error -62
[ 8340.123436] usb usb4-port1: unable to enumerate USB device
[ 8348.875138] usb 4-1: new full-speed USB device number 13 using ohci-pci

I disconnected the keyboard, reconnected it and is worked again.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Sep 20, 2018

@Jopie01 Which firmware, and since how long have you been running >8.2.5 firmwares?

@Jopie01

This comment has been minimized.

Copy link

Jopie01 commented Sep 20, 2018

@mondalaci I'm using 8.4.5 since 30th of August and before that I have used 8.4.2. When I'm not using my system, I switch it completely off. This freeze happened during a normal system-update of Fedora. But I was also switching USB from one Arduino to another back and forth. I will keep an eye on it.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Sep 21, 2018

@Jopie01 Thanks! How often do these freezes generally occur?

@joshginter Do you happen to use a longer/different bridge cable than the one that was provided with your UHK?

@joshginter

This comment has been minimized.

Copy link

joshginter commented Sep 21, 2018

No. I use the included bridge cable.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Sep 21, 2018

@joshginter Thanks! Would you please shoot a picture of your usual setup? I'd like to see how much the cable is stretched and its close surroundings. Also, have you ever experienced chatter? Chatter and freezes might be related.

@Jopie01

This comment has been minimized.

Copy link

Jopie01 commented Sep 21, 2018

@Jopie01 Thanks! How often do these freezes generally occur?

@mondalaci This was the first time in months. I can't say anything about the earlier freezes because I don't know the situation anymore 😄

@joshginter

This comment has been minimized.

Copy link

joshginter commented Sep 21, 2018

image
That is my setup at work. Sometimes my phone will be between the keyboard halves. My home setup is very similar but the keyboard halves are usually connected as I find "connected" to be preferred for gaming.

Since you're worried about the bridge cable I figured I'd include a picture of the bot I carry the keyboard in. It's a snug fit and pushes the cable up a bit but certainly not in a way that should be a problem for that kind of coiled cable.
image

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Sep 22, 2018

@Jopie01 A single freeze in months... That's exactly why it's been mission impossible to fix this bug so far. :)

@joshginter Your setup looks fine to me, and I don't think it should make freezes frequent, however I noticed you mentioned that sometimes your phone is in the middle of the halves. Is there a correlation between your phone being between the halves and the freezes? Also, how frequently do you experience key chatter, if ever?

@joshginter

This comment has been minimized.

Copy link

joshginter commented Sep 22, 2018

I don't think there is a correlation. About half of my freezes have come at home with the keyboard connected not split. The most recent two at work came when I was signing in so my phone probably wasn't there.

I've not experienced chatter (to my knowledge) but I'm a pretty haphazard typer. So it's possible its happened rarely and I just attributed it to my shitty typing. Definitely not as common a problem as some people see in the other thread.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Sep 22, 2018

@joshginter When you use your keyboard merged, is the bridge cable connected? If so, would you disconnect the bridge cable while using your keyboard merged and watch for freezes?

@joshginter

This comment has been minimized.

Copy link

joshginter commented Sep 22, 2018

Ya I keep it connected. I can disconnect see how it goes. Though I havent been using my Pc at home a ton the last few weeks.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Sep 22, 2018

@joshginter Thank you! Appreciate very much the loads of feedback you've been providing.

@irwand

This comment has been minimized.

Copy link

irwand commented Oct 2, 2018

fwiw, I'm still on 8.2.5 firmware, and I've seen it freezes. It's random and rare, and I don't have any insight into pattern or anything. But I'm just saying that potentially this bug is older than 8.2.5.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Oct 2, 2018

@irwand How rare?

I've been testing the freeze, and I find it increasingly probable that it may not be an issue at all. So far, I reproduced it about once over months. This might be a hardware issue. For example, if a user touches the pogo pins and a static discharge happens, a voltage spike may freeze the CPU. That kind of stuff.

According to my knowledge, @joshginter is the only person who experiences the freeze frequently (not sure how often).

@irwand

This comment has been minimized.

Copy link

irwand commented Oct 2, 2018

good question. It's hard to say.. although I haven't had it for the past 2 weeks.. Maybe more. So it's rare enough for me, that it's not quite yet a big issue. I wanted to keep watching my issue, but I thought I should say something to this thread. If you're pretty sure it's HW voltage spike issue, why not release the new shiny firmware builds? Then more people will try them out. :) That said, I'll install the new firmware, and will watch the behavior some more.

@kbdh

This comment has been minimized.

Copy link

kbdh commented Oct 15, 2018

Yes, I am using the stock bridge cable.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Oct 15, 2018

Well, let's wait a couple days to see if your UHK freezes with 8.2.5. I don't have a better idea right now.

@ManuelLevi

This comment has been minimized.

Copy link

ManuelLevi commented Oct 15, 2018

Hi everyone.

My keyboard frequently freezes.

Today, after freezing twice in an hour or two, I've updated the firmware to 8.5.2, the last version I could find to see if it would not freeze anymore. It still does.

This the best report I can give at the moment:

I was frequently changing between base, mouse and mod modes. I was browsing and I use a lot of browser shortcuts and the mouse feature on the UHK.

The LED indicators are activated when FN, MOD or MOUSE keys are pressed, in either side of the keyboard. That seems to be working.

Joining the keyboard together doesn't change the behavior.

UHK agent shows the message "Loading keyboard configuration...Hang tight!". It doesn't update after a couple minutes.

After disconnecting the keyboard, I got a message on the top right corner saying "could not read from HID device".

After connecting the keyboard again, the agent loads it in a second or two, and everything seems to be working fine again.

Hardware:
Using the cable provided with the UHK (the only one I have);
Running on a MacBook Pro with OS High Sierra 10.13.6.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Oct 16, 2018

Hi @ManuelLevi, thank you for your report, and sorry about this issue!

Which firmware version were you running before 8.5.2 with which you also experienced the freezes?

When your keyboard freezes, what happens when you simply reconnect the halves (but don't reconnect USB)? Does it unfreeze your keyboard?

@ManuelLevi

This comment has been minimized.

Copy link

ManuelLevi commented Oct 16, 2018

Hi!

I was using the one it came with, 8.2.5 if I'm not mistaken.

That's what I meant with "Joining the keyboard together doesn't change the behavior.". Nothing changed when I reconnected the halves.

Seeing both halves have an effect on the LED's made me feel like it was the OS that decided to ignore the keyboard (maybe because it misbehaved before?).

Could this happen?

(I just had 2 other freezes this morning)

@irwand

This comment has been minimized.

Copy link

irwand commented Oct 16, 2018

@ManuelLevi, seems that your "freezes" might just be because the USB stopped working, maybe related to #189 ? I'm on Windows though.

@kbdh

This comment has been minimized.

Copy link

kbdh commented Oct 17, 2018

I have used firmware 8.2.5 for two days without any freeze, but I was missing the macro functionality. So I switched back to firmware 8.5.2 and will see if it freezes again. I will probably also test the UHK with another computer and maybe try different USB ports (if that makes sense?)

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Oct 17, 2018

@irwand I agree that @ManuelLevi is probably also affected by #189. I will follow up there.

@kbdh Testing your UHK with another computer and with different USB ports does make sense. Interested about your further findings.

Worst case scenario: We may end up replacing all the affected keyboards. According to all the freeze bug related reports we received, the failure rate is about 0.3% which we can definitely handle.

This is quite an umbrella issue, so I think I will close it in the near future. Both #189 and @kbdh's issue differ from what I have fixed. The root cause may share similarities, but still.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Oct 17, 2018

@Jopie01 @joshginter @kbdh @irwand Please shoot an email to support@ultimatehackingkeyboard.com guys, and include your GitHub user name and order id. I want to correlate all the available information on GitHub and our manufacturing database, and possibly get one on one with you.

@jwr

This comment has been minimized.

Copy link

jwr commented Oct 19, 2018

A data point: I had freezes with 8.4.5 about once a week. I upgraded to 8.5.2 6 days ago and just had my first freeze, but this time it seems different: only the left half froze. The right half was working normally.

I was able to unplug and re-plug the left half and things were back to normal.

I find it slightly suspicious that these freezes occur after several days. I should start taking notes of the exact time.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Oct 19, 2018

@jwr Damn! Your report made me realize that I screwed up the I2C watchdog of the left keyboard half starting from firmware 8.4.3. Thank you so much!

Anyone who encountered with freezes which were solved by reconnecting the keyboard halves, please upgrade to the newly released firmware 8.5.3. Chances are it'll fix your UHK.

@kbdh

This comment has been minimized.

Copy link

kbdh commented Oct 25, 2018

So far the only problem which still occurs with my UHK on firmware 8.5.3 is the one I mentioned earlier where the LED display turns off. I have now created a separate issue for this.

Apart from this no more freezes with my UHK since upgrading to firmware 8.5.3. five days ago.

@rbrt86

This comment has been minimized.

Copy link

rbrt86 commented Oct 26, 2018

I'm afraid I also have the freeze bug since the beginning. Updating to 8.5.3 stopped it for a day, yesterday it came back once and now I have it again almost every 10 minutes. This also happended after upgrading to 8.4.5, first day was fine, but after that more issues.

Unplugging and replugging the keyboard helps, I just plug it in the front USB port and about every 10 minutes when it stops responding I have to re-insert the usb cable

Note: I'm using it for work, connected to the client pc (w10) on which I do not have Admin access. Not sure if it's related to the client, maybe some USB scanning tool interferes with the keyboard or something?

@irwand

This comment has been minimized.

Copy link

irwand commented Oct 26, 2018

@rbrt86 : when it freezes, does any of the LED respond to keypress? or is it completely dead?

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Oct 26, 2018

@rbrt86 Very sorry to hear this! What do you mean by "USB scanning tool"? Do you have a specific hardware attached or software running?

@rbrt86

This comment has been minimized.

Copy link

rbrt86 commented Oct 30, 2018

@irwand having the freezebug as we speak, I can press mod, mouse or FN and all those leds light up. The keystrokes however are not registered on the pc, I can type whatever I want and nothing happens. I attached a dumb keyboard to the second front USB port and that works fine. Putting the who halves together doesnt fix the issue, reconnecting the usb temporarily is the only workaround I have right now.

@mondalaci I connected the UHK to a workstation from the client which handles sensitive data. I do not have Admin access and I do not know if there are security measures running in the background to check for USB storage devices, I can imagine they run some sort of audit tooling somehow. No specific hardware is attached, just the keyboard and an optical mouse. I've checked windows Device Manager, it just shows up as an HID-keyboard in there and says it is functioning properly. Reconnecting the keyboard doesnt show any changes in device manager (it disappears obviously and then shows up again the same). Is there any additional debugging I can do?

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Oct 30, 2018

@rbrt86 After the freeze kicks in, what happens if you reconnect the halves? Does it unfreeze your UHK?

@irwand

This comment has been minimized.

Copy link

irwand commented Oct 30, 2018

@rbrt86 it sounds like your problem is different from this freeze issue. Your problem seems similar to issue I raised here: #189
You might want to try plugging the keyboard to a usb hub instead of straight to the computer, and see if that helps any. It'll be a good data point.

@jwr

This comment has been minimized.

Copy link

jwr commented Oct 31, 2018

Just wanted to report that since the upgrade to 8.5.3 on 2018-10-19 I did not see any freezes or issues (writing this on 2018-10-31). The problem that affected me seems to have been fixed. :-)

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Oct 31, 2018

@jwr Very glad to hear it! :) Thanks for your feedback!

@jfieber

This comment has been minimized.

Copy link

jfieber commented Nov 3, 2018

Installed 8.5.3 when it was posted. Nothing that could be construed as a freeze since before or after the update. (Order 39566 for reference, is there a serial number on these that I haven't noticed?)

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Nov 4, 2018

@jfieber There's a serial number label on the PCB, but I don't advise disassembling any UHKs unless needed.

@richrd

This comment has been minimized.

Copy link

richrd commented Nov 12, 2018

Today I encountered my first issue with the UHK, the left half froze, but the right half still works fine as we speak. I've had my keyboard for something like two months now.

  • I have 8.5.1 on both halves of my UHK
  • Agent starts and loads fine
  • UHK is connected via a USB hub which has worked fine in the past
  • Any of the status leds on the left half won't light up but the segment display still shows my layout
  • The freeze happened when I unplugged and then re-inserted my monitors HDMI cable into my laptop.

Unfortunately the debug script didn't find my UHK and returned null instead. This is the output I got:

dev 835 / 8501 : usage_page:b1f8, usage:17f
dev 45e / 39 : usage_page:2e32, usage:2f31
dev 1d50 / 6122 : usage_page:2d31, usage:2e32
dev 1d50 / 6122 : usage_page:2d31, usage:2e32
dev 1d50 / 6122 : usage_page:2d31, usage:2e32
dev 1d50 / 6122 : usage_page:2e32, usage:2f34
dev 835 / 8502 : usage_page:2d31, usage:2e32
dev 5ac / 8290 : usage_page:2d31, usage:2e32
dev 5ac / 8290 : usage_page:2e32, usage:2f35
dev 5ac / 273 : usage_page:2e32, usage:2f35
dev 5ac / 273 : usage_page:eca0, usage:310
dev 5ac / 273 : usage_page:3a35, usage:2e31
dev 5ac / 273 : usage_page:3a35, usage:2e31
/home/richard/code/oss/agent/packages/usb/get-debug-info.js:20
    device.write(uhk.getTransferData(payload));
           ^

TypeError: Cannot read property 'write' of null
    at getDebugInfo (/home/richard/code/oss/agent/packages/usb/get-debug-info.js:20:12)
    at Object.<anonymous> (/home/richard/code/oss/agent/packages/usb/get-debug-info.js:66:1)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)
    at Function.Module.runMain (module.js:694:10)
    at startup (bootstrap_node.js:204:16)
    at bootstrap_node.js:625:3

Let me know if there's any other info I can provide.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Nov 12, 2018

@richrd Please update your UHK to the latest 8.5.3 firmware which should fix the issue.

@Nnarol

This comment has been minimized.

Copy link

Nnarol commented Nov 25, 2018

Hi!

I have some sort of freezing bug as well. It started in 2 days after getting the UHK.
I used it with 2 laptops successfully, but when I tried to use it with a 3rd one, it froze right away.

The firmware version for both halves of the keyboard is 8.5.3 according to the UHK Agent.
The laptop it does not work with is a Lenovo y510p.

The keyboard was plugged in right before the PC booted, and the LED-s showed garbled characters during the GRUB bootloader screen. The CapsLock indicator and the triangle (whatever it stands for) was lit up.
I tried to use the arrow keys in the bootloader menu to select Windows 8.1. The menu has a countdown, which stopped immediately after I pressed Mod + j (my "Down" arrow), meaning that the PC recognized the fact that a key was pressed, although nothing else happened, the GRUB menu selection didn't move.

After bootup, no key seemed to work. The LEDs were still garbled, and turned blank after a short while.
I plugged the UHK back into the laptop it previously worked with, but the same thing happened.
Then I pulled the cable out and plugged it back again after rebooting the laptop, and ever since it works again with that laptop, but never the one I encountered the issue with.

Plugging the keyboard back into the problematic laptop, the LEDs were always completely dark from that moment on, and sometimes only the right keyboard half worked, but mostly neither.
The exact symptom was that at the time of plugging in, the LEDs correctly showed the default key map, and turned dark after pressing the first key.

All of the above observations were made with the keyboard in split mode.
With its halves joined, the LEDs light up when plugged into the problematic laptop, both halves work, although individual key presses sometimes don't register. The LEDs show anomalies when typing, some of the additional ones to those making up the letters flashing in and out, and all of them turning black after a while.
While joined, the two halves were still connected by the cable.

The cable I used was not the original one, but a 3 meters long one I bought afterwards, since I found the original way too short. I only used the original cable for about 1-2 hours before one of my colleagues took pity on me and lent me a longer one; and on most machines, the keyboard has been working fine.

An issue that may or may not be unrelated though, was that the mouse layer sometimes turned into the fn layer for short bursts and then back again, when I used a 5m long cable of the same sort. I concluded that it must have been too long for the signal to arrive between the halves with proper intensity.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Nov 25, 2018

@Nnarol Please give a try to the original bridge cable that we provided with the problematic laptop, and let me know how it works.

@Nnarol

This comment has been minimized.

Copy link

Nnarol commented Nov 28, 2018

@mondalaci I could not reproduce the issue with either the original nor the 3m long cable. The only difference I can think of was that the laptop was not plugged into the wall, and was running off a battery.
It does cause a difference in how the touchpad makes the pointer move with this model, so it might not be irrelevant.
The UHK is at my workplace now, I'll have to bring the charger of the laptop next time.

@mondalaci

This comment has been minimized.

Copy link
Member

mondalaci commented Nov 28, 2018

@Nnarol Thanks for the follow up! Noisy power supply seems to be the cause of your issue.

We've been flashing firmware 8.5.3 for a while to UHKs, and haven't received any reports that are due this bug, so I consider this to be fixed, and closing it.

@mondalaci mondalaci closed this Nov 28, 2018

@rbrt86

This comment has been minimized.

Copy link

rbrt86 commented Jan 2, 2019

@rbrt86 it sounds like your problem is different from this freeze issue. Your problem seems similar to issue I raised here: #189
You might want to try plugging the keyboard to a usb hub instead of straight to the computer, and see if that helps any. It'll be a good data point.

sorry for the late response, I've got myself a powered usb hub recently and I can confirm that the freezes no longer appear, apparently it was not related to the firmware!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment