Forum Widgets
Latest Discussions
Unable to launch the Surface DUO Emulator with Visual Studio
Dear Team, I have been facing issues with the Duo Emulator launch with the Visual Studio 2019, as the emulator not shows in visual studio build option(<build> (Android 10.0 - API 29) ). I have followed the official instruction . So far I didn’t find any solution. Below am giving the details. Problems Unable to launch the emulator directly after modified run.bat file: When I click the Surface Duo Desktop Icon a command prompt launch and suddenly go to crash. <build> (Android 10.0 - API 29) : emulator not appear in VS-Xamarin 2019 build option Things I done Followed the official Doc instruction : installation (VS 2019- Xamarin , Surface Duo emulator, Xamarin Android SDK Manager Emulator option checked ), run.bat file modification, Hyper V enabled. Installed the Android Studio Things that works (before modifying run.bat ) The emulator successfully launch with the Android SDK (run_androidstudio.bat😞 I have already installed VS 2019 with Xamarin. And once I installed the Surface Duo emulator, I try to directly launch the emulator by clicking emulator icon, however its not respond, then I installed the android studio and tried again, and it was successfully launched. Please advise, Thanks.
Default behavior for Dual Screen Seem (Hinge GAP)
When an app is spanned across two screens, there is going to be a seam — the space between the two screens. This is a byproduct of making a dual-screen device. This section talks about some of the ideas and techniques you might consider to make your app work with the seam. By default Display driver must skip (should not render behind seem) the content behind the hinge GAP. It should be continuous across screens. In fact the app developer should not be even aware of the seem. It should see as one continuous screen. It enables all web sites and apps usable by default. If any app or site wants to do differently to take advantage of dual screens then they use your API to handle it. This is a very simple approach and I think somebody at Microsoft screwed it up up by opting to ask every developer in the world to optimize their content. This will never happen. Duo will fail if not fixed. If I don't get this behavior in the next DUO update I will return my DUO and start a campaign to return all duo owners. I'm Software Architect love this duo and don't want it to fail. This is the only feature missing in this duo. I use only 3 apps on this. Edge, Chrome and Remote Desktop. All three are hiding content behind seem. This default behavior would have made made all these three apps usable.How to start the SurfaceDuo 2 emulator on an Apple M1 device?
Hi team, I know I had the same questions a few month ago, but I want to bring it up again. Currently I'm using an Apple M1 Mac as my development machine. Everything works expect of the Surface Duo 2 emulator. In short: I cannot find where I can change it from trying to use qemu-system-x86_64 instead of the installed qemu-system-aarch64 one. Facts: M1 Mac MacOS Monterey Android Studio installed AS emulators starts as expected `run.sh` fails because of x86 linked emulator Thanks for any helpful tip!
React Navigation Examples
I love the work being put into dual screen devices. I'm trying to build a dual screen app but having issues with getting TwoPane-Navigation to work with React Navigation. I followed the documentation but when i try to span across both screens my details view doesn't span on the second page. The apps 1st screen just spans across both pages. Is there an example with react native i can follow for clarity?Some sort of indication that split screen is supported?
I have only used the sdk / emulator for a couple hours now, but was curious if there is a plan to create some way of making it obvious / easy to either show the user that the app supports using both screens, or actually providing a shortcut to making the app use both screens when it is available? Or maybe even a system setting on a per app basis to use both screens when possible etc.
[Thread] Showcase your Surface Duo apps!
This thread is meant to be a showcase of your awesome apps that are based on thr Surface Duo SDK. Share your hard work and ideas on how the unique features of this dual screen device could be used. ---------- Name #rTsd (Road to Surface Duo) Genre News Development ecosystem Xamarin.Forms Abstract This is a work in progress https://dotnet.microsoft.com/apps/xamarin Android project which is intended to feature most of the new features that makes the upcoming https://www.microsoft.com/en-us/surface/devices/surface-duo phone unique. It will use the awesome German https://www.drwindows.de/ as data source for its articles. Screenshots Links The source is open source on a https://github.com/tscholze/xamarin-road-to-surface-duo. This app will not be released in the Google Play Store.is TwoPaneBackStackEntry composable list of routes incompatible with arguments / URI Routes?
Hello, I am doing some tests on the SDK and have encountered a roadblock. Currently, my application uses route arguments to find item details. However, upon navigating to them, the following exception is returned: java.lang.IllegalArgumentException: Invalid route item/4, not present in list of routes [home?, items?, item/{itemId}, ...] I am unsure if this is a problem stemming from the fact that listOf[Routes] cannot take into account those values or if it is an error on my end. Could you please clarify? Thank you for all your hard work!UI question on foldable: How to display a small amount of content on top of an extended canvas?
Hi team, during my current pet project I learn, that my UI / UX understanding and how thing should work under Android is still not competitive (and useful) that's why I ask you, the awesome Surface Duo community. You see my following app screenshot. Its foldable emulator because there is sadly no M1 Surface Duo emulator, yet. I use the navigation rail und the left to trigger some actions. But all pages - besides the "Map" are quite small - on the huge Surface Duo displays. For this task I assume that its a Surface Duo, spanned displays and in Landscape mode (as it always is). That's why I do not want a page transition to another view, I thought I use a "BottomSheetScaffold" but a little bot of the sheet is always visible in "collapsed" mode. Another Idea was a simple "Drawer". But the drawer should be on the right screen and not 90% width of display, that's why this idea was always a fail. My latest idea was a "Sheet" that moves from the bottom up - like a BottomSheet but not edge to edge and not visible if not active - if the user taps at e.g. "About". The sheet should have some elevation, maybe a close button, etc. What do you think? I had a look at the samples but I was not able to find such scenario, maybe I overlooked something. Thanks for your help and keep up with your amazing work, - Tobi
App shifted towards right in landscape RTL mode
When the device is in landscape with RTL mode, the app got shifted towards right. Because of which all the touch points and areas are shifted which affects app behaviour. Attaching screenshot for the Microsoft's Edge app. I am trying these things on emulator, please let me know the same bug is there on real device or not. Thank you.
