It is so demoralizing not being able to have all the other would-be improvements in the new version because the thing randomly fixates on eternal-seeming flashing green in certain unpredictable occurrences before a power cycle, such as right now when I just said to myself, “hell, why don’t I try 2.0.0 rc4”, and after flashing systempart1 and tinker, it is now flashing eternal green, having been connecting perfectly on 1.5.4-rc1 which preceded, and I guarantee if I power cycled right now it would connect.;
Does Particle acknowledge that this has happened and is absolutely the direct and proximate result of a software change they made, or does Particle not even have the business wherewithal to realize that this business-killing bug is currently re-introduced after having been fixed in 2019.
I am beyond any willingness to handhold with tests, detailed descriptions, diagnostic logs, etc. I am not on Particle’s payroll. By far enough information has already been posted on these forums.
Does Particle acknowledge the 2020 reintroduction of cellular reconnection killing misbehavior, previously having been fixed in 2019 (before it was caused by a memory leak) and is working on a fix?
UPDATE: After multiple solid minutes my 2.0.0rc4 just connected. This never happened before - before it would connect in 30 seconds. Even if the bug isn’t a reintroduction of the eternal no-connect, it is a significant degradation from 1.3.1-rc1 through 1.5.4-rc in reconnection performance.