You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nebula App version 0.3.0-71 (Play Store)
OS: ChromeOS 113 with ARCVM/Android 11
With the move of Android into its own VM a serious problem with parts of the ChromeOS can lead to the kernel spontaneously killing the entire Android subsystem and restart it after dealing with the cause (usually a bad case of lacking system memory and killing random processes -- some of them being the virtual display(s) of Android applications. (Typical symptom: System freezes but mouse is still working, after some time getting the message "ChromeOS had to restart" but no login window before showing the desktop again -- that was not a boot).
Some applications do not survive that at all (Enpass will not launch again).
In the case of Nebula I have lost all my configurations after an event like that (i. e. Nebula displaying "Welcome to Nebula! You don't have any site configurations...") several times now (this has never happened with ARC++/Andoid-in-a-container.
Something hinting at a more detailed reason (the application storage is not there, is empty or a configuration file has been found but it was not usable) might make the more curious among us happy but won't solve the problem. In typical Android fashion (an application has to fear immediate death all the time it is running) please check if the file is not open if it is not necessary to read or write it.
Please reconsider giving issue #82 a nit higher priority; even saving an encrypted copy on Google Drive (or another installable file system like NextCloud) could be helpful.
The text was updated successfully, but these errors were encountered:
Nebula App version 0.3.0-71 (Play Store)
OS: ChromeOS 113 with ARCVM/Android 11
With the move of Android into its own VM a serious problem with parts of the ChromeOS can lead to the kernel spontaneously killing the entire Android subsystem and restart it after dealing with the cause (usually a bad case of lacking system memory and killing random processes -- some of them being the virtual display(s) of Android applications. (Typical symptom: System freezes but mouse is still working, after some time getting the message "ChromeOS had to restart" but no login window before showing the desktop again -- that was not a boot).
Some applications do not survive that at all (Enpass will not launch again).
In the case of Nebula I have lost all my configurations after an event like that (i. e. Nebula displaying "Welcome to Nebula! You don't have any site configurations...") several times now (this has never happened with ARC++/Andoid-in-a-container.
Something hinting at a more detailed reason (the application storage is not there, is empty or a configuration file has been found but it was not usable) might make the more curious among us happy but won't solve the problem. In typical Android fashion (an application has to fear immediate death all the time it is running) please check if the file is not open if it is not necessary to read or write it.
Please reconsider giving issue #82 a nit higher priority; even saving an encrypted copy on Google Drive (or another installable file system like NextCloud) could be helpful.
The text was updated successfully, but these errors were encountered: