I might sound like a broken record here but I've been considering switching to this Os it'd be a nice change from Android but I use lots of socials and small banking tools daily, is there much if any app support for this? Because I can't see myself giving up these apps.
That means the command "mount /system" failed inside TWRP shell, are you sure you have an Android ROM installed? You can try formatting the partition as ext4 from the TWRP menu, but you should really flash LineageOS 16.0 (for now) before flashing SFOS as per the instructions.Trying to install but keep getting ERROR: 5 can't mount /system. Has anyone else experienced this?
It appears the quick download buttons for the artifacts are indeed gone now for whatever reason, you can still get to them by opening the pipelines though by clicking a few times. Here's the latest 3.4 artifacts for example.@deathmist Need some help please
I installed sfos 3.3 (as it was the only one i could find on gitlab. the link to download artifacts for 3.4 was not available), used it for a while, was working really well. Then proceeded to update to 3.4 using the command sfos-upgrade 18.104.22.168 after gaining root access, updated sucessfully. Post which tried adding fingerprints, but couldn't then went on to troubleshoot it using
zypper ref && zypper dup
systemctl restart sensorfwd
but still it doesn't work.
Also, double tap to wake screen was broken.
It appears the quick download buttons for the artifacts are indeed gone now for whatever reason, you can still get to them by opening the pipelines though by clicking a few times. Here's the latest 3.4 artifacts for example.
There's some race condition causing various things to fail on boot at times and one easy indication of this is indeed doubletap-to-wake not working. It seems to be related to the SFOS display compositor lipstick failing once, but then starting properly; this could be difficult to fix but I'll take a look at it for the massive SFOS 4.0 upgrade during which I'm hopefully rebasing to hybris-17.1 (Android 10 HAL) as well as switching the userspace to full ARM64.
But for now simply rebooting should fix the non-working gesture daemon and other minor things caused to fail due to that race condition
#include <std_disclaimer.h> /* * I am NOT responsible for data loss, you getting fired because the alarm app failed or if you brick * your device. Please do some research if you have any concerns about features included in this OS * port before flashing! YOU are choosing to do these modifications, and if you point the finger at me * for messing up your device, I will laugh at you. * BOOM goes the dynamite! */
devel-su # enter your SSH password from Settings > Developer tools zypper ref -f zypper dup # choose solution 1 to deinstall conflicting encsfa packages reboot