Martin Hub

Hi, I did some investigation on my RPI Zero W since I had `e-Paper busy` issues sometimes too. This might not apply to all issues people mention above, but I've...

@dyamon I just merged it and they looks awesome! Thanks I just noticed that when Gadgetbridge updates the time (after reboot I had 0:00) then the text did not update...

@StarGate01 Thanks for all the awesome work! I'll try that on my P8 soon. I'm glad I could update them after long time.

Merged all 3 PRs and on PineTime it works absolutely fine. Doesn't break anything. Correct touch driver is detected. On P8 also no major issues. Tested and works fine: -...

Can confirm I was able to have same reset behaviour with 1.3.0. (i do not use the analog clock, also never knew I could go back to sleep with doubleclick...

I might overlook something - but if you use `rand()` and do not set seed by `srand()`, do you get the same pseudorandom numbers again after InfiniTime reboots? I cannot...

My guess is that constructors are run immediatelly after start and they are called cycle-perfect every time, so you seed the random, but it is same every time. You have...

@toitoinou NRF52 has special and certified RNG peripheral exactly for this reason. I did some quick tests and had something wrong, the numbers did not come. If anyone could look...

@geekbozu we don't need to use RNG for `rand`. Single RNG number on boot and applying it to the random seed `srand` should be enough. Then `srand` gives us number...

@stoehraj Hi, was working on other PR and discovered that Nimble is already using RNG peripheral and it has nice driver and wrapper for `rand()`. All I had to do...