Stuck at "Long swipe from the left edge to open the Application Drawer"



  • I've just installed the image from https://ci.ubports.com/job/rootfs/job/rootfs-pinephone/ to a 64GB MicroSD card, and during the first boot it started showing what looks like an instructional app to teach me what the device is capable of.

    However, it's stuck at "Long swipe from the left edge to open the Application Drawer", and no amount of tapping of swiping appears to help. Even rebooting just brings back the instructional app, with no obvious way to continue.

    I tried plugging in a USB keyboard, to see if there were some keyboard shortcuts I could use to close the instructional app or launch something else, but it appears that the keyboard is not recognised (I couldn't use the USB keyboard to unlock the phone at the passphrase prompt).

    How do I skip this instructional app and get to the rest of Ubuntu Touch?



  • @Msquared
    I have the same issue.
    My workaround is to lock the phone, wait a couple of minutes ands unlock it...



  • @AppLee
    swiping left to right ,didnt they remove that. and then "maybe"not from the demo ?



  • @Marathon2422 No. Swiping from left edge to open launcher and drawer is still a thing. However, there was an issue with the fix to the tutorial to ensure it gets played correctly, which is now fixed in git, and should be in tomorrow's image.



  • @Marathon2422
    Swipe from left to right shows the drawer.
    Why would it be removed ?

    The same appears from swipe from the top down and I did the same to get rid of it.
    Once done you can reboot and it doesn't show up again.



  • Not sure if this is still an issue, but a "work around" to not get prompted (if you have access to the filesystem) for tutorial swipes is to edit this file:

    /var/lib/AccountsService/users/phablet (or whatever username file is there)

    And add the missing elements to the DemoEdgesCompleted variable until it is like this:

    DemoEdgesCompleted=[‘left’, ‘top’, ‘right’, ‘left-long’]



  • Thanks @rik
    On the recent images the bug has been fixed.


Log in to reply