On 11/2/23 11:37, Jerry Latimer wrote:
> I've also been using AVARE for over 10 years with no issues. Last week
> (10/29/23) Avare became unstable.
Thank you SO much to those who've reported this problem!! I'm happy not
to have been flying in busy unfamiliar territory lately, in case it
happened to me too. Hopefully this discussion will also prepare other
pilots to quickly and safely shift focus if it crashes.
In all my years happily using Avare since first release, I'm
*exceptionally* glad to only have a handful of issues in 2k hours'
flight all over N. America, Bahamas, HI, and even N.&S. NZ islands. That
said, when Avare has had an issue in flight it feels like there's
nothing worse! Without the fore-warning of this discussion it could add
pilot workload to decide if/when to give up on trying to figure out the
problem while keeping situational awareness both inside & outside the
cockpit!
Anyway, in the hope it might be helpful for our tireless volunteer
Apps4Av Dev Team, I googled for an explanation on how to send a bug
report. In essence consensus seems to be that the "easy" way is via the
Developer Options "applet" in the Settings of every Android device.
If despite exhausting search you've never seen that applet in your
Settings, it's because Google "hides" it to keep users from being
frightened or inadvertently messing something up. I've been using it
since not long after excitedly buying the early DROID phone. Never
having had need to send a Bug Report, my use has to do with carefully
turning off "Bloatware" that I can't Disable in the Apps section of
Settings.
(while not for everyone, I've found disabling Bloatware has made
all of my dozen or so Android devices faster, more stable, and with
many days of battery charge & longer battery life)
Anyway, if anyone who can replicate this crash is willing to take a few
minutes and get/send a Bug Report to the Dev Team you'll be helping
yourself and every other Avare user. Here's one HowTo link (please post
any you find, too) that looks fairly good:
https://academy.test.io/en/articles/2541912
It's for both Android & iOS (Apple), so you have to wade thru some
irrelevant info. After you skim the intro, the simple HowTo part starts
here:
https://academy.test.io/en/articles/2541912-crash-logs-on-mobile-devices#h_434c246525