Daniel Dudek

The main question is how to get reference to the actual image, so that: RN: `that_node_handle = findNodeHandle(that_reference)` then in android: `context.getCurrentActivity().findViewById(that_node_handle)` will be able to find the view

After going in circles despite above suggestions, using ClassRule in companion object worked, but this gave me a hint that it's an rules ordering issue so also this approach below...

> > After reading this pr, I find a workaround for my needs: > > I define some faster MOVE keys in the dt-bindgs [file](https://github.com/zmkfirmware/zmk/blob/621ecc54503851383736477360d6c8faac4d5cbe/app/include/dt-bindings/zmk/mouse.h) > > ```c > >...

The issue is not with android M or any other. I was able to recreate it today on Samsung J5 Android 5.1.1, but in my crashlogs from production this exact...

We're facing the same issue with: > 1. No "OnNext" The threads thing also applies

I tried some solutions. I managed to trigger `ssd1306_init_device` method in ssd1306.c after bringing back power, but it fails on first writing on I2C with an error. I even re-tried...

wow, looks like I've made it working by resetting i2c too, I'll try to post working workaround in a few days, if not ping me please

I wanted to test it a bit more before publishing to avoid confustion, few notes: - I can't seem to fix the issue when the ext_pwr is OFF on startup...

@Percentnineteen Looks like it was not needed for my screen which is not rotated (I skipped some of the initialization to try shorter sleep) but that might be an easy...

I can confirm as well, I'm having issues with z-offset. Had it 3 times, the scenario is as follows: I change the nozzle, do the z-calibration, I even double checked...