Themes / Apps / Mods SamSprung TooUI - Cover Screen Home (FREE)

Search This thread


Senior Member
Jan 12, 2011
Registered by pm email address and used the link from the first of the 2 posts above.
Downloaded test version 1.0.0 onto Android 12.
Gave all necessary permissions and bypassed screen lock.
This is what I get on cover screen...

The link took me to 1.0.0
I will see if there is an update on the Play Store.
How else to get to 1.0.2 ?

Google is being... Google. The APIs published are not meant to be used in the ways they allow, but only in the way they were intended. Already had them threaten my account and call the app malicious because it didn't plug a security hole that is actually the purpose of the receiver. "It's not a problem, but could be abused to create a problem. That possible problem will then be blamed on you and your account will be terminated" or something like that. Really considering an iPhone.

It was the post right before yours. They're not updating it yet.
  • Like
Reactions: kashortiexda
Bonjour où ce trouve le lien pour télécharger le fichier s'il-vous-plaît ?

I appreciate your confidence, but I am not fluent in French and rule 4 says you have to include an English translation with any other language.

On a different note, how messed up is it that I know the rule number?
Screen Shot 2022-01-16 at 2.02.15 PM.png

Screen Shot 2022-01-16 at 2.03.00 PM.png

This is what we're dealing with right now. An IMPOSSIBLE vulnerability that is being flagged for nothing more than the existence of the ONLY required method for that particular API.

So, in the meantime, I will be looking into an alternate method of release. I have a feeling, given about 15 years of experience with Google, they are going to deny the appeal and simply claim the issue wasn't fixed.
Last edited:
Bonjour où ce trouve le lien pour télécharger le fichier s'il-vous-plaît ?

Hello where is the link to download the file pleas

I appreciate your confidence, but I am not fluent in French and rule 4 says you have to include an English translation with any other language.

On a different note, how messed up is it that I know the rule number?

Wow what a mess on that reply, apparently nobody reads threads these days. Sorry to hear about the api issue. Google is much more strict on permissions now. Crazy how far we've come

It's really just embarrassing these days. The documentation used to be incomplete, but but at least attempted to give decent examples. Now, it's literally excerpts from an example out of context and with almost no explanation at all. The reviewers know nothing about code, so the best they can do is keep reciting the automated error that they were shown.

I've got some great conversations saved, including one where they claimed I was submitting deviant sexual content because the dress on a character showed what would be an inch of cleavage in real life when you approached her from just the right angle. Hadn't noticed until the perverts performing the review spilled their Kleenex in my inbox.

Anyway... has the current build. It's the same one that is available to the beta testers as 104. Hopefully this won't end the same way as TagMo with Google saying "you don't need X" and it being the entire basis of the app.
As a temporary solution, the repository above will have new builds as they are released. They will update themselves just like the previous builds that replaced Samsung Health. I'll still be pushing to have it published on Google Play. Once the app is to a point where I feel it's a release version, the source will be made public.

For those that have seen how the new build looks, I am sure you can see why this is being kept secret for now. It will always be the first launcher, but it deserves a little more time also being the best.
  • Like
Reactions: BWA80
Methinks we fixed the issue, though. Seems Google was trying to find a roundabout way of punishing me for the GitHub releases. At least that is how it looks when the problem was suddenly resolved by removing a reference to them not even in the receiver.

Now, the only issue is that I have to replace the old version from internal testing before they will complete the review for open testing. Internal testing is unreviewed and completely separate. So, just to be clear, they reviewed a build they aren't supposed to review and require it be fixed to publish a completely separate one that passed.
Last edited:
Thanks to everyone who sat through the frustration. It would appear the issues have been addressed and now we are just waiting on an obligatory delay. They've casually reminded me the review process can be extended up to 7 days. I get the feeling nobody saw the humor in what I named the permission or that my appeal request said "find the nearest literate person and have them read it to you"
  • Haha
Reactions: paul c


New member
Jan 17, 2022
Thank for u update to use in One UI4
But I have some problem
I can't find bixby voice unlock
(I want to use it but need something lock my phone when I'm stay at outside) 🥰🥰🥰
I'm from Thailand
Sorry for my English

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    That being said about Samsprung being free makes me wonder why in the world everyone wouldn't donate to you? It's a very functional and totally useful app. I know for sure that you've put many, many hours into it. Fixing bugs, adding features, etc. takes so much time (and you probably have a real job too).
    Just forego even one Starbucks latte or an overpriced candy bar or whatever and give this Dev some appreciation!


    With all this discussion about finding workarounds, everyone knows that SamSprung is free, right? Nobody needs to be saved from downloading an app without signing up, installing it without a credit card, and using it without being nagged to subscribe.
    Orientation control and self destruct. Got it.
    Search is moving to the pull up window with the quick toggles, so it will no longer have an option switch. There's not much point to "freeing up space" when it's already freed up.
    In the end, putting the search in a sub-menu proved too confusing for some.

    The next release will bring back the optional bar directly in the drawer. I'll look into other options to hide it without needing the elaborate setting. It would still be nice to hide it when it's not being used without having to disable it entirely.
    To avoid having to set the system-wide rotation, it will need to be set from the quick toggle drawer. It will persist between uses, though.

    Since the default is landscape and apps that set portrait are not designed to display in landscape, the options will be portrait and auto. The locked rotation icon is portrait.

    Again, it will need to be set before launching an app to apply.

    Adding a dynamic toggle for each app requires system settings permission and locking rotation universally. This way, there is no lock. There is no risk of bleeding into the main screen and it won't change any phone settings that may not restore.

    @Respectful slide up the bottom bar in the app drawer to toggle.
  • 19

    Welcome to the original Z Flip 3 launcher.
    A complete home experience on the cover screen.

    This is the next innovation in cover screen apps. After pioneering the widget launcher, this app has evolved into a full parallel launcher and continues to revolutionize the cover screen.

    This launcher adds cover screen support for full notifications with actions, apps, widgets, quick toggles, voice launch, custom screen timeouts, animated wallpapers, and more.

    TooUI began and remains the only cover screen app to fully integrate with the stock launcher, bypassing the limitations of the widget interface or attempting to replace the existing home functionality.

    The Android 12 version is backward compatible, but the widget is not compatible with Android 12

    Samsung Health replacement widget (Android 11) -

    Thanks @CarudiBu for discovering the workaround to load a custom widget.

    See the GitHub README for setup and usage information​


    If a picture is worth 1000 words, it would take hundreds to match the code being written.


    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.
    Done. Now you can hide / unhide apps for the widget with a long press on the item (in the app settings).
    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.

    For now, the plan is to keep working on some things I don't want to advertise for fear Samsung will go and ruin them before I find answers.