I've been playing around with some of the settings regarding the Korean Model's Dual Screen. This Thread is just meant to discuss what I've found.
Dual Home Launcher:
The Dual Screen has its own launcher, to which the Dual Screen will always return when the "Home" button is taped on the Dual Screen. There is no option to set a "Default Launcher" for the Dual Screen. Of the standard launcher options preinstalled on the main device, the Dual Home Launcher most closely resembles the "Home & App Drawer" launcher, but is its own environment.
The Dual Screen can load a different launcher as you would load a typical app, but the home button will always take your back to the Dual Home Launcher. A different launcher can be assigned as the "Dual App" (the app that automatically loads whenever the dual screen is turned on) but again, the home button will still take your back to the Dual Home Launcher. Additionally, when a "Dual App" is assigned, they Dual App will automatically be brought to the forefront whenever the device is brought back from "screen off", opened from a closed state, or returned from the 360° opened, second screen off position. Basically, using a Dual App is an annoying option, and it doesn't work to assign a different launcher for the dual screen anyways.
I have discovered that is possible to open the Dual Home Launcher on the main screen. To do it, you need Nova Launcher or Action Launcher on your system, or a similar Launcher that adds an "activities" widget. In the activities widget's apps list, you will find the Dual Home Launcher as as n app, and the primary launcher activity can be used to bring it up on the primary screen. As usual, if you got home on the dual screen, it just moves the application over to that screen.
I'm interested in testing with the disabling of the Dual Home Launcher App, per this method: https://www-xda--developers-com.cdn...ers.com/disable-system-app-bloatware-android/, but I have no idea what it would do. Too bad I can't make a TWRP backup first. I'm also interested in the idea of spoofing the app's name in the system to make the device think that a third party launcher is the Dual Home Launcher and basically set THAT launcher as the default Dual Screen launcher. In particular, I think Lucid Launcher, AIO Launcher, or WX Launcher would be good Default Dual Screen Launchers, per my tastes, but I think having Lawnchair on the Dual Screen next to Nova Prime would probably be a popular setup.
Tasker:
The App Tasker has had zero efforts in it's development for dual screen compatibility, as far as I can tell. Events triggered to bring up apps or things like that will have their action committed on whichever screen is active at the time, basically, whichever screen you've used last.
To demonstrate what I mean, as a test, I've loaded up a simple "torch" app on both screens that has one function, a single tap on the screen will make the screen change from white to Black, or black to White. If you tap the second screen, it changes, then you tap the primary screen, "nothing" happens and it requires a second tap to change the color is the main screen. Then, tap the second screen again, and it takes two taps to cause the app's function. When you are using one screen, your first touch on the other screen doesn't activate anything, just changes the focus of the device to that screen, whereupon you can begin making touch inputs on that screen. The screen that you're on, that you've used last, is your active screen. This is the screen that Tasker will commit actions on, regardless of which environment triggers the event. There is no option in the Tasker Dialogues to choose which screen something will target. I haven't experimented with it much at this time, but I'm certain that this could cause bugs and failed triggers if you have triggers try to target an environment in which an app that would be expected to be forefront is not there. I haven't experimented much yet, but I've been attempting to make contact with the Developers of Tasker, to add a screen targetting plugin, and to add "Secondary Display on", "Secondary Display off", and "Secondary Display Load App" as selectable event triggers. I've been on the Tasker Forums, and someone recommended I explore the methods on here: https://forum.joaoapps.com/index.ph...ings-to-use-in-autotools-secure-settings.210/ to try and find the variables for Secondary Display On/Off at least, and I'm hopeful that there might be a way to shift focus to one screen or the other as part of a series of actions, which would allow an app to be loaded on a specific screen. I'm interested to see what can be done in this regard.
"Island" App:
The App "island" is a very interesting project that is still under development. When you install it, it requests the permissions and then takes you through the setup of a "Work" App Environment, and installs to it another copy of the Google Play Store. Basically, this Play Store is the same as your normal Play Store, and should be linked up to the same Google Account. The App's icon gets a little Briefcase on it to signify that it's a Work app, and you have to set up a second Pin, Knock Code or Password for it (I'm not sure if this can be the same it not. I made mine different). When you load it, it asks for the code, and then opens a normal looking play store, except none of your apps are downloaded yet. Any app that you download with this play store get that same little Briefcase icon, and exist as "Work" apps, which basically lets you install two copies of any app.
Some limitations: any Launchers that you attempt to download within the Work Environment will only include Work Environment Apps within their app drawers. Normal, or "personal" environment Launchers, however, DO show Work Environment Apps next to their regular, "Personal" Environment counterparts. "Work" Launchers do not appear in the "default launcher selection" dialogues. Widget's are funky too. Work Environment Apps that have widgets do not have them become available universally, the way that normal apps do. Work Environment Launchers with widgets, for instance, can only load those widgets within that launcher. Basically, "Work" dual loaded Launchers just aren't a great idea.
Island also adds another APK installer, do you can install any downloaded apk in the work environment. I haven't tested installing an alternative app store in the work environment, but I would imagine that one would still install apps from it into the Work Environment as well. Untested theory though.
Using island, you can load to copies of, say, social media apps, and then have both apps running at the same time, one on one display, the other on the other, whereas, normally trying this would just cause the app to jump over to that screen, rather than dual booting. In most cases, you can log in the same account, or a different account, on the two screens. Be actively watching two different Discord servers on your device, from one single account, for instance, if you'd like.
Island is a little funky in certain regards, as it's still in development, but I've gotta say, it works very well at this point. And it basically makes every app in existence dual screen compatible.
I haven't tried installing a Qslide app in the Work Environment yet. I'm intrigued, now that I'm thinking about it.
Shoot, I've written a serious mini novel here. I guess I'll stick a bookmark in it here for now. I'll keep this Thread up to date on what I've discovered though. I've got a few avenues that I want to explore.
Dual Home Launcher:
The Dual Screen has its own launcher, to which the Dual Screen will always return when the "Home" button is taped on the Dual Screen. There is no option to set a "Default Launcher" for the Dual Screen. Of the standard launcher options preinstalled on the main device, the Dual Home Launcher most closely resembles the "Home & App Drawer" launcher, but is its own environment.
The Dual Screen can load a different launcher as you would load a typical app, but the home button will always take your back to the Dual Home Launcher. A different launcher can be assigned as the "Dual App" (the app that automatically loads whenever the dual screen is turned on) but again, the home button will still take your back to the Dual Home Launcher. Additionally, when a "Dual App" is assigned, they Dual App will automatically be brought to the forefront whenever the device is brought back from "screen off", opened from a closed state, or returned from the 360° opened, second screen off position. Basically, using a Dual App is an annoying option, and it doesn't work to assign a different launcher for the dual screen anyways.
I have discovered that is possible to open the Dual Home Launcher on the main screen. To do it, you need Nova Launcher or Action Launcher on your system, or a similar Launcher that adds an "activities" widget. In the activities widget's apps list, you will find the Dual Home Launcher as as n app, and the primary launcher activity can be used to bring it up on the primary screen. As usual, if you got home on the dual screen, it just moves the application over to that screen.
I'm interested in testing with the disabling of the Dual Home Launcher App, per this method: https://www-xda--developers-com.cdn...ers.com/disable-system-app-bloatware-android/, but I have no idea what it would do. Too bad I can't make a TWRP backup first. I'm also interested in the idea of spoofing the app's name in the system to make the device think that a third party launcher is the Dual Home Launcher and basically set THAT launcher as the default Dual Screen launcher. In particular, I think Lucid Launcher, AIO Launcher, or WX Launcher would be good Default Dual Screen Launchers, per my tastes, but I think having Lawnchair on the Dual Screen next to Nova Prime would probably be a popular setup.
Tasker:
The App Tasker has had zero efforts in it's development for dual screen compatibility, as far as I can tell. Events triggered to bring up apps or things like that will have their action committed on whichever screen is active at the time, basically, whichever screen you've used last.
To demonstrate what I mean, as a test, I've loaded up a simple "torch" app on both screens that has one function, a single tap on the screen will make the screen change from white to Black, or black to White. If you tap the second screen, it changes, then you tap the primary screen, "nothing" happens and it requires a second tap to change the color is the main screen. Then, tap the second screen again, and it takes two taps to cause the app's function. When you are using one screen, your first touch on the other screen doesn't activate anything, just changes the focus of the device to that screen, whereupon you can begin making touch inputs on that screen. The screen that you're on, that you've used last, is your active screen. This is the screen that Tasker will commit actions on, regardless of which environment triggers the event. There is no option in the Tasker Dialogues to choose which screen something will target. I haven't experimented with it much at this time, but I'm certain that this could cause bugs and failed triggers if you have triggers try to target an environment in which an app that would be expected to be forefront is not there. I haven't experimented much yet, but I've been attempting to make contact with the Developers of Tasker, to add a screen targetting plugin, and to add "Secondary Display on", "Secondary Display off", and "Secondary Display Load App" as selectable event triggers. I've been on the Tasker Forums, and someone recommended I explore the methods on here: https://forum.joaoapps.com/index.ph...ings-to-use-in-autotools-secure-settings.210/ to try and find the variables for Secondary Display On/Off at least, and I'm hopeful that there might be a way to shift focus to one screen or the other as part of a series of actions, which would allow an app to be loaded on a specific screen. I'm interested to see what can be done in this regard.
"Island" App:
The App "island" is a very interesting project that is still under development. When you install it, it requests the permissions and then takes you through the setup of a "Work" App Environment, and installs to it another copy of the Google Play Store. Basically, this Play Store is the same as your normal Play Store, and should be linked up to the same Google Account. The App's icon gets a little Briefcase on it to signify that it's a Work app, and you have to set up a second Pin, Knock Code or Password for it (I'm not sure if this can be the same it not. I made mine different). When you load it, it asks for the code, and then opens a normal looking play store, except none of your apps are downloaded yet. Any app that you download with this play store get that same little Briefcase icon, and exist as "Work" apps, which basically lets you install two copies of any app.
Some limitations: any Launchers that you attempt to download within the Work Environment will only include Work Environment Apps within their app drawers. Normal, or "personal" environment Launchers, however, DO show Work Environment Apps next to their regular, "Personal" Environment counterparts. "Work" Launchers do not appear in the "default launcher selection" dialogues. Widget's are funky too. Work Environment Apps that have widgets do not have them become available universally, the way that normal apps do. Work Environment Launchers with widgets, for instance, can only load those widgets within that launcher. Basically, "Work" dual loaded Launchers just aren't a great idea.
Island also adds another APK installer, do you can install any downloaded apk in the work environment. I haven't tested installing an alternative app store in the work environment, but I would imagine that one would still install apps from it into the Work Environment as well. Untested theory though.
Using island, you can load to copies of, say, social media apps, and then have both apps running at the same time, one on one display, the other on the other, whereas, normally trying this would just cause the app to jump over to that screen, rather than dual booting. In most cases, you can log in the same account, or a different account, on the two screens. Be actively watching two different Discord servers on your device, from one single account, for instance, if you'd like.
Island is a little funky in certain regards, as it's still in development, but I've gotta say, it works very well at this point. And it basically makes every app in existence dual screen compatible.
I haven't tried installing a Qslide app in the Work Environment yet. I'm intrigued, now that I'm thinking about it.
Shoot, I've written a serious mini novel here. I guess I'll stick a bookmark in it here for now. I'll keep this Thread up to date on what I've discovered though. I've got a few avenues that I want to explore.
Last edited:
