Frustrating Experience on First Trip

I took my first short EV road trip recently. 220 miles, but I'm driving a Mini Cooper SE (range ~110 miles on the highway based on my experience, but I've never run it below 10%). I decided to give ABRP a try with the premium membership, and to connect the car via Enode to monitor the charge level. As I've seen elsewhere, the app constantly says it has connection issues, but that's not the only issue.

When I click into the vehicle settings it says "Not Authorized," but then happily updates the charge level and odometer to reflect the car's current status. When I start driving a trip, the charge status is accurate, and for a while it remains that way. However, once I get between cities (where I assume the car itself loses its cell service) ABRP loses its connection and stops updating the charge.

So far, so good, if you enter the charge level manually it will estimate based off of that, right? Wrong. The app kept defaulting the charge level to 95% (which I think is the departure SOC I set before I even connected the vehicle through Enode). Even if I set the charge level manually to what the car was currently showing, the app would periodically revert to the 95% charge level when I switched to another app for a while and then back again to ABRP.

Even worse, the app would then keep prompting to switch to a shorter route. When I clicked that route I found that it had removed my next charging stop because the car had miraculously charged to 95%.

This would all be a non issue if ABRP would just keep estimating based off of the last time it did get an update from the car, perhaps with a warning that it's doing so. Reverting to a state of charge setting that I don't even know how to change now that it's using the live car data made it semi useless.