Forum Widgets
Latest Discussions
Will the Surface Duo (2) run the Android12L variant?
Hi team, I just try to understand what's up with Android 12L and why it's another flavor and not just a feature of Android 12 - sorry if I understood it not correctly. Does anyone know if the Surface Duo (2) will get Android 12 or the L version? And if yes, in my eyes it makes no different for developers, am I correct? Thanks for helping me out in understanding the new Android 12 versions! - Toby
Can we have booth activities fullscreen in IntentToSecondScreen sample?
Hi, I tried making an app similar to IntentToSecondScreen sample. I notices when device is on 3-button navigation mode: the navigation bar always appears on the screen that not have focused. I tried calling this on booth activities after that but it didn't work: getWindow().getDecorView().setSystemUiVisibility( android.view.View.SYSTEM_UI_FLAG_LAYOUT_STABLE | android.view.View.SYSTEM_UI_FLAG_LAYOUT_HIDE_NAVIGATION | android.view.View.SYSTEM_UI_FLAG_LAYOUT_FULLSCREEN | android.view.View.SYSTEM_UI_FLAG_HIDE_NAVIGATION | android.view.View.SYSTEM_UI_FLAG_FULLSCREEN | android.view.View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY ); onSystemUiVisibilityChange function also is not triggered each time the navigation bar shows/hides. Do you guys have any suggestion on this? Thank you.[Thread] Do you plan to develop Surface Duo only apps?
Hi Team, I'm just curious if anyone plans or has been payed to develop Surface Duo only apps in a B2B context. In my day job as a B2B iOS / iPadOS developer, I have mostly customers that wants to run their apps on specific devices like an iPad 8th gen. Due to the fact, that the Surface Duo is also targeted on business customers, I can imagine that there could be Surface Duo only apps out there. If this is true for some of you, what are the features that your customer wants to be implemented? Drag and Drop? Or just more "space for displaying metrics"?Does the Surface Duo SDK works well the Android apps that run on Chromebooks?
Hi, I just wanna ask if anybody has an Android app that uses the Surface Duo SDK ready to run on a Chromebook? My experimental app runs great on non-Duo Android devices but keeps crashing (while the splash screen is visible) on my Chromebook. Nevertheless, the Google Play Store said that it would be compatible. Otherwise I found no emulator image that would enable me to test my app against a Chromebook environment. Thanks, - TobiThank you MSFT folks! My very first Android app (w/ Duo SDK) is now available in the Play Store
Hi team, I know that for many of you that's not something to be happy and proud about it. Last week I published my very first Android app to the Play Store. Of course, it uses the great Surface Duo SDK for Xamarin. The app is content-related German only. I just wanna say thank you to guymerin , Hakon_Strande, and all of your team mates for your great work and encouraging new Android developers to give it a try. Links: https://play.google.com/store/apps/details?id=io.github.tscholze.rtsd https://github.com/tscholze/xamarin-road-to-surface-duoSurface Duo SDK has been updated with Duo emulator OS bugfixes
Hi all, We have uploaded an updated SDK that contains some bugfixes to the Duo Emulator OS. Double tap to home working by default The Pill bar at the bottom of the apps should not go missing any more The downloads are live at: https://www.microsoft.com/en-us/download/details.aspx?id=100847 HakonSFirst update to the Surface Duo SDK Preview Release is live!
The update aims to improve appcompat on the Duo when apps are running on a single screen. Read about it in the devblog: https://devblogs.microsoft.com/surface-duo/the-surface-duo-sdk-preview-is-getting-an-update-feb-202020/ You can download the updated SDK images for Mac, Windows and Ubuntu using this https://www.microsoft.com/en-us/download/details.aspx?id=100847. We are also in the news! 🙂 There is an article about this update here: https://www.windowscentral.com/surface-duo-preview-sdk-has-its-first-update Keep the feedback coming![Info] Surface Duo SDK Version 02022020 is out!
Hi fellow developers, As Hakon_Strande and guymerin posted on Twitter (see https://twitter.com/gmerin/status/1230642854122274817?s=20), a new version of the Surface Duo SDK is out. It's great to see that the folks at Microsoft listen on our feedback. The major updates of the SDK includes following changes: Changes to how size is reported to an App Updates to DisplayMask API Surface Duo Image Build Flavor is now a USER build and not USERDEBUG And a lot of behind the scene enhancements For further information about this changes please read the https://devblogs.microsoft.com/surface-duo/the-surface-duo-sdk-preview-is-getting-an-update-feb-202020/. Update all the NuGet packages and happy coding folks!Lessons learned: Updating an app from copied Duo lib files to Xamarin.Forms.DualScreen NuGet package
I just updated my https://github.com/tscholze/xamarin-road-to-surface-duo to use the freshly released https://www.nuget.org/packages/Xamarin.Forms.DualScreen/4.5.0.282-pre4. That's why I wanna share my lessons learned, maybe some will be for others obvious, maybe not. Do not forget Update Xamarin.Forms package, to the latest pre-release (don't forget to mark the checkbox) Install the Xamarin.Forms.DualScreen package, it's a pre-release (don't forget to mark the checkbox) Delete all old copy-and-pasted "Duo Lib" that you copy pasted from the very first sample project Embed new namespace in duo-specific (e.g. master/detail pages) files xmlns:dualScreen="clr-namespace:Xamarin.Forms.DualScreen;assembly=Xamarin.Forms.DualScreen"​ Update, usage of TwoPaneView to new syntax with child elements <dualScreen:TwoPaneView> <dualScreen:TwoPaneView.Pane1> <views:ItemsView x:Name="MasterPane" /> </dualScreen:TwoPaneView.Pane1> <dualScreen:TwoPaneView.Pane2> <views:ItemView x:Name="DetailPane" /> </dualScreen:TwoPaneView.Pane2> </dualScreen:TwoPaneView>​ Check if you set the config values correct in the MainActivity.cs to listen on Duo-specific changes ConfigurationChanges = ConfigChanges.ScreenSize | ConfigChanges.Orientation | ConfigChanges.ScreenLayout | ConfigChanges.SmallestScreenSize​​ Conclusion It's great to see that you do not longer need copy & (w/p)asted files in your library. There are not really breaking changes. It took me max. an hour to update my app.
