J0nnyMak0
J0nnyMak0
Also is there a way to pass the device # to `llk` script?
And unfortunately, the event # changes with every reboot. It would be nice if there was some way to figure this out. Happy to provide debug info.
After thinking about this, the solution here would be to have an option for `logkeys` to identify devices by-id which are persistent and don't change across boots. So, perhaps something...
> Some related effort expended in #161. > > > Alternatively if `-d` can take a relative path as input that should also work. > > Seems only a slight...
> I'm excited to be able to report that I've got some form of hotplugging working. It's for "display controllers" only, and only tested so far on my laptop with...
ok, thanks. I gave it a quick try. Here is an issue I found. (I'm booting with nouveau blacklisted.) First off, if I first plugin external monitors and then `sudo...
> When Push stops working, do you still see the Push notification? If so, what text does it display? > Do you mean the persistent notification? It still says "Waiting...
> After an authentication error, K-9 Mail's Push code will back off and only retry an hour later. Does the persistent notification text change when k9 is in this mode?
This is still happening from time to time. This is what I was able to capture with the suggested method. [k9log.txt](https://github.com/k9mail/k-9/files/8664154/k9log.txt)
> I suspect that the original reporter of this problem and I both just see the results of our cellphones trying to save some energy. Nope. Sorry, not in my...