• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Themes / Apps / Mods SamSprung Cover Screen Launcher

Search This thread

Clusco

Member
Dec 19, 2020
20
5
Samsung Galaxy Z Flip3
Pic's
 

Attachments

  • 20210918_155010.jpg
    20210918_155010.jpg
    2.6 MB · Views: 58
  • 20210918_153211.jpg
    20210918_153211.jpg
    1.4 MB · Views: 57
  • 20210918_153333.jpg
    20210918_153333.jpg
    1.4 MB · Views: 52
  • 20210918_153507.jpg
    20210918_153507.jpg
    1.1 MB · Views: 51
  • 20210918_153608.jpg
    20210918_153608.jpg
    1.1 MB · Views: 59

Ptrprkr

Member
Sep 15, 2021
21
2
Thanks for creating such a beautiful widget, and as I installed it from the first launch, it getting more and more stable.

Btw I managed to bypass the lockscreen. If you have configure smart lock (watch, band, or location, etc) and install tasker auto input to bypass lockscreen swipe to unlock. It runs perfectly without disabling the screen lock.

It even support nfc tagging when phone closed just by double tapping (if you use tasker and want to automate something).

I really hope someone working on the cover screen combined with tasker haha

Kudos to dev.
Can you share your Tasker Profile and Task. I'm using Bixby Unlock bypass process. I'd like to take a look at the Tasker bypass. Thanks
 

dallasnights

Senior Member
Sep 25, 2006
145
20
I can use YouTube no problem and it's the right rotation but when I use YouTube TV app Suddenly with your new build I installed,when I click on live TV it's not the right rotation for th coverscreen and does not play the live channel
 

igawa

New member
Sep 18, 2021
2
2
Can you share your Tasker Profile and Task. I'm using Bixby Unlock bypass process. I'd like to take a look at the Tasker bypass. Thanks
Yes please share your profile and task thank you
Actually it just need Auto Input app, you can download it here.

Make sure you set up Smart Unlock from settings. So now your lock screen will shown like this if Smart Unlock detected.

Screenshot_20210918-205553_One UI Home-min.jpg


It requires you to swipe up to unlock the devices. But if you install Auto Input, there's an option to dismiss that keyguard.

Screenshot_20210918-205533_AutoInput-min.jpg


Install it from playstore, setting it like this and bam.

Double tap on cover screen like it never locked.
 
Last edited:
  • Like
Reactions: D4rk4

Ptrprkr

Member
Sep 15, 2021
21
2
Actually it just need Auto Input app, you can download it here.

Make sure you set up Smart Unlock from settings. So now your lock screen will shown like this if Smart Unlock detected.

View attachment 5412999

It requires you to swipe up to unlock the devices. But if you install Auto Input, there's an option to dismiss that keyguard.

View attachment 5413001

Install it from playstore, setting it like this and bam.

Double tap on cover screen like it never locked.
Got it thanks. I was trying to do an unlock without the very unreliable Samsung Smart Lock setting (which is so iffy that half the time it doesn't work). I had a great Tasker task that would extend the screen lock time to 24 hours, but that used the Tasker Secure Settings which does not seem to work on A 11. I'm trying Bixby Routines to keep the phone unlocked while on my home wifi. It's more stable that the Samsung Smart Lock setting, but still can be finicky every so often, locking the screen even though connected to wifi and not idle for 4 hours. Just wished the way Tasker worked on A 9 was the same on A 11..
 

D4rk4

Member
Dec 25, 2008
37
7
Gave this a go along side the smart lock + autoinput app as mentioned above. Amazing work all round! So good to have that extra bit of functionality on the cover screen.
 

Ptrprkr

Member
Sep 15, 2021
21
2
So, I just added the key guard functionality via autoinput, using Bixby Routines to unlock on my home Wi-Fi. No swiping. Just open and it's ready to go. Super cool.
 

D4rk4

Member
Dec 25, 2008
37
7
Have noticed something. The last app you use in the cover app won't open on the main screen. You have to clear the recent apps to get the app to work again on the main screen. Minor annoyance, just thought I'd share.
 

Ptrprkr

Member
Sep 15, 2021
21
2
Have noticed something. The last app you use in the cover app won't open on the main screen. You have to clear the recent apps to get the app to work again on the main screen. Minor annoyance, just thought I'd share.
Hmmm. This isn't happening with my phone. The last app I used on the cover screen is already open, when I open the phone
 

D4rk4

Member
Dec 25, 2008
37
7
Hmmm. This isn't happening with my phone. The last app I used on the cover screen is already open, when I open the phone
The apps not always open on mine. Im using nova launcher. Not sure if that's the issue?

When the apps already open, if i close it, go back to the homepage and then try to open it again using the app icon on homepage/drawer, it won't load that way either.
 

Ptrprkr

Member
Sep 15, 2021
21
2
Now even more strange. I'm using Nova also (7). Anything I launch on the outer screen is still open when I flip open the phone (I actually wish there was a way to use and close from the outer screen), but I'm not having the issue of the app not being able to be opened once I open the phone. I do have recent apps turned off, so I don't see the 2nd Nova screen, so that's the only difference I see.
 

D4rk4

Member
Dec 25, 2008
37
7
Now even more strange. I'm using Nova also (7). Anything I launch on the outer screen is still open when I flip open the phone (I actually wish there was a way to use and close from the outer screen), but I'm not having the issue of the app not being able to be opened once I open the phone. I do have recent apps turned off, so I don't see the 2nd Nova screen, so that's the only difference I see.
Hmm. Ok thanks. It's definitely intermittent. I will keep playing with it. See if I recreate it more regularly.
 
Have noticed something. The last app you use in the cover app won't open on the main screen. You have to clear the recent apps to get the app to work again on the main screen. Minor annoyance, just thought I'd share.

Take a minute and read the first page of the thread. It's well documented
 

Chestburster107

New member
Sep 18, 2021
3
1
Samsung Galaxy Z Flip3
I'm having some difficulty getting it to work. I have uninstalled Samsung health and disabled fingerprint, pin, ect.

After that when I try to use it the screen is just black and doesn't show me anything. I have toggled for the app to appear on the cover screen through the settings app. I also tried to see if trying to add the widget through the cover screen will work and it doesn't appear there. Even when making sure I have it toggled off in settings page it still doesn't appear on the widget page on the cover screen.

I'm not sure what I am doing wrong and I have uninstalled and reinstalled the app a few times now and still can't figure it out. I even doubled check to see if Samsung health didn't reinstalled itself and it hasn't.

So I'm not sure on what to do
 

nirurin

Senior Member
Nov 25, 2012
322
35
Bristol
I'm loving the work being done here, the cover sceen for the flip seems like it could have a lot of potential. It's basically a large watch screen, so I dont know why they didn't implement a full wearOS implementation for it in the first place!

Curious to know what apps/widgets people have been running on the cover screen with this, that have been particularly useful?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    In all fairness, I don't think i've explained why the limitations are what they are and should probably have done that a while ago.

    The cover screen is effectively like plugging in a second screen on a previous S or Note series phone. DeX is effectively a secondary home launcher. Since this screen is part of the phone, instead of connected by a cable, a second launcher is used instead of DeX.

    The outer screen supports a second launcher, such as Nova or Smart Launcher 5. It also supports a primary launcher having a secondary launcher activity. Samsung, on the other hand, has disabled this support in favor of a hardcoded launcher that's built into the firmware.

    Samsung's launcher has been broken into the home screen, which is the clock selection, and widget pages. It's been further limited by only allowing certain widgets to be available on the widget pages.

    Being a system app signed by Samsung, they've gone a step further. The widgets allowed must system apps or signed by Samsung, as well. One loophole exists, which is Samsung Health. It does not need to be a system app, since you can install it from Google Play. It also doesn't need to be signed by Samsung for whatever reason. It does, however, still need to match up with the expected widget inside the expected app.

    This app takes advantage of the loopholes by using the specific component name (package / package.activity) of the Samsung Health widget and the package for Samsung Health. Because of this, the app must also be a widget, though. It cannot be a full launcher.

    Widget functionality is limited, but can support launching apps. This is another loophole that uses the widget list support to act as a fake launcher. Since the core launcher behind the widgets is still a launcher, it will launch apps on the cover screen.

    Like a normal Android screen, configuration changes are handled by the current activity being displayed. In this case, that would be whatever app is launched. The widget gets taken along for the ride. To minimize the impact of the launched app, the widget is designed to ignore any configuration changes, which would usually trigger the list to refresh.

    A few unique problems exist because of the cover screen being composed of widgets. One is that they do not follow the expected life cycle of a widget. They are not refreshed when they appear, which is why a swipe is sometimes needed to make list items clickable. Another is that they cannot perform any of the prep an activity provides, such as handling the lock screen. When an activity requests overriding the lock screen, it only extends to the activity and not to any it launched.

    This leaves us with what you see. A widget that exploits a bunch of loopholes within the limitations of the widget framework.
    5
    Widgets on the cover screen are granted Settings.canDrawOverlays without the need for permission approval from the user?

    With the option off in the app settings, the app never requested the permission and instead simply verified that it was already granted. That is interesting...

    and now the big news:

    Portrait apps may now be fully functional, if my testing is correct.


    The permission approval button when launching the app from the drawer shouldn't be required, but it exists in case it will help with any finicky apps / devices. It will request system settings and overlay permissions.

    System settings permission will allow the widget to temporarily disable the automatic rotation option, while the overlay permission creates a fake view over the widget that is locked in portrait and steals focus from the widget to avoid it forcing the layout back to landscape. This will not, however, prevent apps with landscape support from functioning normally.

    A new caveat I found is that, when charging, tapping power and waiting won't exit the current app. I do not intend to address this right now. The reason being that the controls to have the power button return to the widget also force a screen timeout to return to the widget and can cause issues with the app being displayed when opening the phone.

    A quick and dirty workaround to change apps when charging is to simply open the phone a bit. This will reset the widget without breaking the expected functionality.

    As it stands, the power button and a timeout will not kill the current app unless they exceed two seconds and will not kill the app at all when charging. This allows long-term use of a single app, which fits most use cases. Other options to switch apps, such as volume button overrides, are also being explored.

    @ChrisChoi314 it appears your list of incompatible apps was lost in the cleanup. If you still find any, you can post the list on the issue for it.

    3
    Except I'm using swipe or no lock screen(both supported configs according to your OP) and the bug is occuring

    Sounds like you should relearn how to read instead of blaming the user for reporting a bug with your app because I clearly stated that I disabled the lockscreen entirely and still couldn't launch apps without either restarting the phone or removing the widget and enabling it again

    It's not my job to bug report for you, I'm doing you a favor by telling you about it, don't be rude and blame me for experiencing a bug you wrote into the code...

    I'm trying to understand your issue to fix it. I'm not obligated to release free software or provide you with any support at all. If you choose not to report a bug and you're the only one that appears to be facing it, how much are you hurting anyone else?
    2
    Added some changes to the initial startup that shouldn't matter, but may solve issues in some rare cases. The configuration activity design for a standard widget doesn't seem to work with the cover screen, but the flow was added to allow making configuration optional and defaults load.

    There are also a few updates to the widget layout and the class info in the manifest that may improve refreshing. Much like the configuration changes, they are fundamentally useless. There may be those rare cases when they make a difference, though.

    Also realized the update notice in the settings activity was a bit silly, since nobody is meant to be opening that regularly. The next update will be focused on moving that to the widget with as little hassle as possible.
    2
    Thanks to whoever made the YouTube video. I have been working on improving the initial startup / return loading. It shouldn't require a restart. That is definitely inconvenient. I don't believe it does now, but I will start throwing that into the testing.

    The next big feature planned is to try prioritizing apps with notifications. This will likely be second to adding some form of indicator.
  • 10
    In all fairness, I don't think i've explained why the limitations are what they are and should probably have done that a while ago.

    The cover screen is effectively like plugging in a second screen on a previous S or Note series phone. DeX is effectively a secondary home launcher. Since this screen is part of the phone, instead of connected by a cable, a second launcher is used instead of DeX.

    The outer screen supports a second launcher, such as Nova or Smart Launcher 5. It also supports a primary launcher having a secondary launcher activity. Samsung, on the other hand, has disabled this support in favor of a hardcoded launcher that's built into the firmware.

    Samsung's launcher has been broken into the home screen, which is the clock selection, and widget pages. It's been further limited by only allowing certain widgets to be available on the widget pages.

    Being a system app signed by Samsung, they've gone a step further. The widgets allowed must system apps or signed by Samsung, as well. One loophole exists, which is Samsung Health. It does not need to be a system app, since you can install it from Google Play. It also doesn't need to be signed by Samsung for whatever reason. It does, however, still need to match up with the expected widget inside the expected app.

    This app takes advantage of the loopholes by using the specific component name (package / package.activity) of the Samsung Health widget and the package for Samsung Health. Because of this, the app must also be a widget, though. It cannot be a full launcher.

    Widget functionality is limited, but can support launching apps. This is another loophole that uses the widget list support to act as a fake launcher. Since the core launcher behind the widgets is still a launcher, it will launch apps on the cover screen.

    Like a normal Android screen, configuration changes are handled by the current activity being displayed. In this case, that would be whatever app is launched. The widget gets taken along for the ride. To minimize the impact of the launched app, the widget is designed to ignore any configuration changes, which would usually trigger the list to refresh.

    A few unique problems exist because of the cover screen being composed of widgets. One is that they do not follow the expected life cycle of a widget. They are not refreshed when they appear, which is why a swipe is sometimes needed to make list items clickable. Another is that they cannot perform any of the prep an activity provides, such as handling the lock screen. When an activity requests overriding the lock screen, it only extends to the activity and not to any it launched.

    This leaves us with what you see. A widget that exploits a bunch of loopholes within the limitations of the widget framework.
    9
    This is a WIP launcher for the cover screen that allows you to run apps without opening the phone.

    This is primarily useful for checking recent messages, running background tasks, or performing actions that do not require a keyboard or the full screen.

    Current limitations:
    • Apps require Screen lock type set to None / Swipe in Settings -> Lock screen
      • Bixby unlock can be used as a workaround for other lock types

    • Keyboards will not open on the cover screen and some app functionality is limited
      • Firmware limitation by Samsung - Secondary IME support is disabled

    • Switching apps requires tapping power and waiting for at least two seconds to close the app before launching the widget again (turn on cover, swipe to widget). The app list, however, can be swiped closed.

    • Samsung Health must be uninstalled to free up the package name for the whitelisted widgets. Installing this app will then add it as an option in the cover screen widgets.
      • Firmware limitation by Samsung - Widget package name or signature




    This app replaces Samsung Health and will not work with any other app that requires uninstalling Samsung Health.​


    Thanks @CarudiBu for discovering the workaround to load a custom widget.
    5
    Done. Now you can hide / unhide apps for the widget with a long press on the item (in the app settings).
    5
    Widgets on the cover screen are granted Settings.canDrawOverlays without the need for permission approval from the user?

    With the option off in the app settings, the app never requested the permission and instead simply verified that it was already granted. That is interesting...

    and now the big news:

    Portrait apps may now be fully functional, if my testing is correct.


    The permission approval button when launching the app from the drawer shouldn't be required, but it exists in case it will help with any finicky apps / devices. It will request system settings and overlay permissions.

    System settings permission will allow the widget to temporarily disable the automatic rotation option, while the overlay permission creates a fake view over the widget that is locked in portrait and steals focus from the widget to avoid it forcing the layout back to landscape. This will not, however, prevent apps with landscape support from functioning normally.

    A new caveat I found is that, when charging, tapping power and waiting won't exit the current app. I do not intend to address this right now. The reason being that the controls to have the power button return to the widget also force a screen timeout to return to the widget and can cause issues with the app being displayed when opening the phone.

    A quick and dirty workaround to change apps when charging is to simply open the phone a bit. This will reset the widget without breaking the expected functionality.

    As it stands, the power button and a timeout will not kill the current app unless they exceed two seconds and will not kill the app at all when charging. This allows long-term use of a single app, which fits most use cases. Other options to switch apps, such as volume button overrides, are also being explored.

    @ChrisChoi314 it appears your list of incompatible apps was lost in the cleanup. If you still find any, you can post the list on the issue for it.

    3
    Also done. Now the switches work as they were intended and long press is no longer used.