Done. Now you can hide / unhide apps for the widget with a long press on the item (in the app settings).
This will be a great addition. Thanks so much. Will look forward to g
Thanks Twistedumbrella. This is getting better and better.
So, my experience so far. It appears that apps that, natively, will only display in portrait view, when launched on this outer screen launcher, cause this launcher to disappear as a widget once I close out of the launched app. I then need to restart my phone to get the launcher back. Using the Cover Screen Widget settings does not re-establish the launcher. Pressing the + to add a widget after this happens, does not show this launcher as an option. This does not happen with apps that will rotate. Trying to figure out options.
Got it. Any reason why (am I the only one experiencing this) apps that launch in portrait mode, end up causing the launcher to disappear as a widget to begin with? This does not happen with any apps that rotate.
Yes, so far, I have 1 app that launches in portrait mode, and does not yet crash the launcher (Out of Milk). Other apps that only launch in portrait mode still crash the launcher (TV Time, CNBC, Range Rover Remote).
I don't know what they heck I did but I had pokemon go working in portrait for a while, it would crash 2-3 times initially but eventually catch and stay open. I haven't been able to get it to stay though since I re-enabled lock screen and did the bixby unlock thing, but that may be a coincidence as I changed a bunch of stuff that nightSo the problem with apps launching from a widget is the lack of control over orientation. When an app triggers a rotation, it calls update on the widget. This causes the widget to reload and the app to exit.
There are a few ways to fix this, but the only one without any downside would be Samsung opening up the cover screen launcher to being replaced. The second way is one I originally began to write and will finish to see if it's a reasonable solution. It may have minimal impact on battery and performance, as well.
The alternative would be something like the mirroring, which could act as a pseudo-launcher, but at the cost of HUGE battery drain, since you will now be running the full phone all the time. This also requires you never allow the phone to time out, which would allow AOD or the widget to take over. One slight way around that would be a hybrid widget / mirror app that acted as its own launcher widget. This would, once again, fall under the limitations of the widget, though.
So the one app that did not seem to crash the launcher (Out of Milk) is crashing the launcher. Thus, all portrait only apps crash while those with auto rotation do not.I don't know what they heck I did but I had pokemon go working in portrait for a while, it would crash 2-3 times initially but eventually catch and stay open. I haven't been able to get it to stay though since I re-enabled lock screen and did the bixby unlock thing, but that may be a coincidence as I changed a bunch of stuff that night
I use both this and TagMo so your work on both is appreciated!!I know i've been a little quiet with the updates, but I haven't given up. For anyone that doesn't follow what I do outside of this project (pretty much anyone), I took over TagMo not long ago. It's an app for making custom Amiibo tags. One of the big requests was supporting some specialty hardware that one of the generous users sent along for testing and it arrived Friday night. Much like any phone i've been donated over the years, the biggest thank you I can offer is swift progress. I should have that to a point where I can juggle projects again in the next day or two.
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...