Yes exactly. It started after using 1.4.0. Now I went back to 1.3.1. I already spent enough time trying to fix this on my end with no luck. This problem also appears on all Borons I tested whenever I use 1.4.0 as deviceOS…
Yes exactly. It started after using 1.4.0. Now I went back to 1.3.1. I already spent enough time trying to fix this on my end with no luck. This problem also appears on all Borons I tested whenever I use 1.4.0 as deviceOS…