07-12-2023, 05:52 AM
Thank you for the welcome feedback and for keeping track of the issues that concern you most.
It takes a second until the screen re-appears (the drivers need a bit of time to start again). When pressing the button during this second, the press is interpreted as command to enter the screensaver again (we may better discard those events in this intermediate phase).
Does the bad behavior still happens when tapping the power button (just once) and giving the screen two seconds to re-appear? If the screen stays blanked, I need to contemplate how to get more diagnostic information out of your specific device in order to see what's going wrong. The volume buttons can in principle (at least according to my understanding) not have any effect on the screensaver.
That toggling of the "Use" button does not make any sense to me. I never do this and think that the advise earlier in this thread was misguided. The file system issues a sync request every 10 seconds. So it should be fine to merely wait a few seconds after installing a system update before invoking the Device -> Reset. By toggling the "Use" button, you effectively kill the file system by force. This is fine when everything is synced after the last write operation, but it can leave the file system in an inconsistent state when doing it shortly after a write. In short, the use-button dance is not needed or may even be counterproductive.
I wonder, does the corruption still occur for you when you delay the reset for 10 seconds after the last write? If not, it would be fair to at least add a safeguard ("nag screen") for the reset/power-off function.
Quote:I could not consistently turn the screen back on the same way. Sometimes it took pressing the power button once, twice, thrice, etc. and waiting 5 seconds. Other times the same thing was done using the volume buttons (up and down) to get the screen to return not pressing the power button at all.
It takes a second until the screen re-appears (the drivers need a bit of time to start again). When pressing the button during this second, the press is interpreted as command to enter the screensaver again (we may better discard those events in this intermediate phase).
Does the bad behavior still happens when tapping the power button (just once) and giving the screen two seconds to re-appear? If the screen stays blanked, I need to contemplate how to get more diagnostic information out of your specific device in order to see what's going wrong. The volume buttons can in principle (at least according to my understanding) not have any effect on the screensaver.
Quote:3. Still lose the Sculpt OS on reboot after clicking Storage "USE" off requiring reburning the image, reloading the OS, and redownloading the Presets. I did this without looking at previous notes which may have the correct procedure listed, but this is still way to much work to cleanly power down/restart the OS on the PinePhone.
That toggling of the "Use" button does not make any sense to me. I never do this and think that the advise earlier in this thread was misguided. The file system issues a sync request every 10 seconds. So it should be fine to merely wait a few seconds after installing a system update before invoking the Device -> Reset. By toggling the "Use" button, you effectively kill the file system by force. This is fine when everything is synced after the last write operation, but it can leave the file system in an inconsistent state when doing it shortly after a write. In short, the use-button dance is not needed or may even be counterproductive.
I wonder, does the corruption still occur for you when you delay the reset for 10 seconds after the last write? If not, it would be fair to at least add a safeguard ("nag screen") for the reset/power-off function.
