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.
Magic Trackpad 2 and multitouch in Android emulator
In reference to https://devblogs.microsoft.com/surface-duo/android-emulator-multi-touch-support/ I was trying to use the app I am the developer of (Ink&Paper) on the android emulator with a Cintiq 16 on a mac. Everything works except using the Magic Trackpad 2, which has unexpected behavior. I don't know if it's a device type issue but I think it's more likely common to all trackpads. However it would be nice if it was implemented in the correct way (it works well in Bluestacks but it is a completely different type of emulator). Regards.MainActivity.kt from the Flutter sample is all red - it works, but is it normal?
Hi team, I just played a little bit around with the Flutter https://devblogs.microsoft.com/surface-duo/get-started-with-flutter-on-surface-duo/. During the tutorial I noticed that after I copy pasted the Kotlin source, mostly everything went red aka in an error state. Please see attached screenshot. The source was still buildable and worked as expected but it's a little bit of a shock for a beginner if everything is red.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![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.FLAG_LAYOUT_NO_LIMITS it is not respected on one screen mode
The https://developer.android.com/reference/android/view/WindowManager.LayoutParams#FLAG_LAYOUT_NO_LIMITS is not respected on one screen mode on real device and emulator. This was reported by one of my app user and can be replicated really easy on emulator. Placing a View with https://developer.android.com/reference/android/view/WindowManager.LayoutParams#FLAG_LAYOUT_NO_LIMITS outside the screen boundaries does not work on single screen mode, as you can see in the screenshots above. When both screens are visible, the blue rectangle (a view) it is correctly placed outside the screen, when the screen is closed it is restricted inside the screen. Video demo with the problem: https://streamable.com/2tgevf
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?
