Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 58307 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 23726 [details]
sample project with hardwareAccelerated set to "false"
We need to set hardwareAccelerated to "false" on the AndroidManifest.
This causes multiple issues on Android 5 with some controls, e.g. Scrolls stop working, unresponsive entries, etc.
I'm attaching a sample project
Steps to reproduce:
Open the attached solution
Verify that the scroll works on the initial screen
Tap any item, this will push a new page
The scrolls don't work anymore
The scroll will work as it does in other Android versions regardless hardwareAccelerated false/true
The scrolls don't work on Android 5
(Android 4.2 and 6.0 work fine with both configurations)
Thank you for filing this report! I tested this on an emulator and I believe I am seeing the issue. I am tracking down an actual device to test this on and confirm. In the meantime, I am curious what situation would require you to disable hardware acceleration? I am hoping to better understand this scenario better so we can determine how this could be supported better.
Thanks for taking a look. We have a library that uses Skia, refactor that library so it can use SkiaSharp.Views.Forms would be a significant effort. As a work around we disabled the hardware acceleration, this works fine on other Android versions.
I discovered this bug and it describes our issue too. We never explicitly set the hardwareAccelerated property but noticed this problem on Android 5 devices. Perhaps the default value is true for 4,x and 6-onwards which explains why only this version shows the error.
Interestingly it is not the scrolling which is broken, the page behaves correctly but the page doesn't redraw meaning blank areas or controls not changing state (but sounds and event handlers still responding). This can mean you can scroll a ScrollView and select an item but you have no idea what is currently visible.
We don't use Skia or any other custom drawing code.