Meanwhile I do 50% of my internet-ing in private mode and get annoyed when I change between apps the wrong way and loose my 4 tabs lol. I think this particular issue happens because firefox-android must get told by android-OS to free up RAM as it's now a background-app.
But there's another private-tab-killer, and it happens when the screen times-out automatically or manually (eg, when you push the power button). I don't have a passcode or anything, so when I push the power button to power the screen on, it shows the simple "swipe to unlock" screen. The problem is that FF leaves a "private browsing" notification — and FYI, if you click on any notification on my lock screen, it will unlock and go to straight to that app — so of course I see that notification and think "shit yer, here's a shortcut" and click it, to which it unlocks the phone and opens FF, but it wipes all my private browsing tabs in the process!!! But if you unlock it by swiping, then your tabs will survive...
Actually, as I'm typing this, I think it might wipe ALL tabs, but that's not so bad for regular tabs (as you have history, cookies, etc), but it can still ruin your "state" of a search/scroll/etc.
Edit2: I'm also just realising that the way it wipes tabs when I click the notification sounds just like the first issue I mentioned (which I presume is android-OS garbage collecting the memory held by "background" apps). I have a POCO phone that runs Xiaomi HyperOS, and if it's running a non-standard lock-screen "app" by default (because I'm using the default whatever with settings that suit me), then perhaps that's why clicking a notification counts as "changing apps"?! (or perhaps even the default android lock screen counts as its own app?) But this idea seems strange because it would imply that the "swipe to unlock" feature is not part of the "lock screen app"...?
But there's another private-tab-killer, and it happens when the screen times-out automatically or manually (eg, when you push the power button). I don't have a passcode or anything, so when I push the power button to power the screen on, it shows the simple "swipe to unlock" screen. The problem is that FF leaves a "private browsing" notification — and FYI, if you click on any notification on my lock screen, it will unlock and go to straight to that app — so of course I see that notification and think "shit yer, here's a shortcut" and click it, to which it unlocks the phone and opens FF, but it wipes all my private browsing tabs in the process!!! But if you unlock it by swiping, then your tabs will survive...
Actually, as I'm typing this, I think it might wipe ALL tabs, but that's not so bad for regular tabs (as you have history, cookies, etc), but it can still ruin your "state" of a search/scroll/etc.
Edit2: I'm also just realising that the way it wipes tabs when I click the notification sounds just like the first issue I mentioned (which I presume is android-OS garbage collecting the memory held by "background" apps). I have a POCO phone that runs Xiaomi HyperOS, and if it's running a non-standard lock-screen "app" by default (because I'm using the default whatever with settings that suit me), then perhaps that's why clicking a notification counts as "changing apps"?! (or perhaps even the default android lock screen counts as its own app?) But this idea seems strange because it would imply that the "swipe to unlock" feature is not part of the "lock screen app"...?