Opening Tor logs on Android cancels bootstrapping

This is due to the fact that opening settings cancels bootstrapping on Android. However I'm not sure why that decision was made historically, since desktop users can view (and even change?) settings during bootstrapping without consequence.

Ideally, unless there's a good reason for the deviation, we should apply the same UX to both platforms for consistency – however the side effect that opening Tor logs now cancels bootstrapping is the most pressing issue.

IRC logs, for reference:

[11:34:00]  <donuts> hrmm, it seems that bootstrapping is cancelled on Android when settings is opened – is that a known issue or a technical limitation?
[11:36:27]  <dan_b> donuts: thats the behaviour it has always had 
[11:36:31]  <dan_b> and desired
[11:36:54]  <dan_b> if folks went into settings to change things we wanted bootstrap stopped until they changed things and start again with those changes
[11:37:02]  <dan_b> thats some ux decision we've had for a bit
[11:37:53]  <donuts> gotcha, unfortunately opening Tor logs during bootstrapping now cancels bootstrapping though
[11:38:20]  <dan_b> LOL right
[11:38:20]  <donuts> would it be possible to change the logic so bootstrapping is only cancelled if a setting is changed? Although I'm not 100% clear why it's necessary at all, tbh
[11:38:46]  <dan_b> it would be i think easy to stop bootstrap from firing when settings is opened
[11:39:20]  <dan_b> i think if bootstrap is done, when we push new settings it ususally behind the scenens redoes what it needs? pierov you know more about saveSettings / applySettings
[11:39:41]  <PieroV> applySettings calls `SETCONF` on the control port.
[11:39:49]  <PieroV> If it succeeds, the settings are applied immediately