I am making a code changes to a Boron on OS V 3.1.0 from build.particle.io console. I have to be honest, it is a slow and terrible experience compared to the competitor, and I am wondering if I am doing something wrong.
First, is it normal that every single flash causes an entire green-flashing cellular reconnect? Why can’t it just start with the same code? Competitor does not force full reconnect for minor code change from cloud. I am using SYSTEM_MODE(AUTOMATIC) and not doing anything fancy to the connection.
Second and more disconcertingly, I notice repeatedly that it takes far longer for it to reconnect after a code flash (minutes flashing green) than if I just pull the plug after it downloads the new code flash. From a cold start, it will connect much faster. Why is this the case? Is this an intentional impediment or a bug?
Third, is it normal that it takes up a whole minute for a flash to propagate to Boron from a de minimis code change? Competitor takes a handful of seconds, using same LTE CAT-M connectivity.
Fourth, why does the Particle cloud have so much apparent overhead that even after it has established internet connection and goes into flashing blue, it sometimes takes forever to connect? I have even seen it connect to internet with modem (done flashing green), and then take so long to connect to “cloud” (an abstraction which shouldn’t require any additional connectivity but is 100% software-imposed) that it stops flashing blue, says “well that didn’t work, I’ve been trying to connect to particle.io for so long that I will back off for now and try again later, even though my UBlox SARA modem is fully connected to internet”, and goes to solid green? Am I doing something wrong or is this standard experience on 3.1.0?