I think there needs to be some notice that the new app isn't enabled in widgets. It seems like a lot of people are coming from the old one or one of the random YouTube videos on it and having a breakdown that it doesn't show up there.
Seems we also need to do something about the issue submission. The bot account has it's own account and the email is fundamentally unused as anything more than identifying your issue to you.
The problem is when someone goes crazy about remaining anonymous and turns their issue into a faceless rant. If there is that much concern for remaining anonymous, the likelihood that they will break anonymity for a conversation is slim.
The login is completely private. It's just requesting a token to post as yourself. It's not stored. In case anyone was skeptical about that being unsafe. The backend is the Eclipse EGit API (http://www.eclipse.org/egit/)
Alright, the back item is now 20% opaque (almost invisible) and supports swiping from the far left side to go back to the launcher. Touching the far left side is still supported, too. This may or may not be removed down the line.
Like many projects before it, I think we have reached a point where this one can handle most problems and feature requests through GitHub without needing to post about every update.
I did address this to some extent. Now, if the app is actually open on the cover and you open the phone, it resumes. This would be the "expected" behavior (similar to the open phone to continue thing). However, if you close the app on the cover or turn the screen off, it reverts to the home screen with the app in the background (as you would expect if you turned the screen off and on with a "normal" phone).
The first scenario was the intentional one. I can see where the others would be more of a bug than a feature and hadn't really noticed it was launching apps that weren't being used anymore.
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.
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.
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.
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.
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.