[Android] Random compilation result

0 votes
asked Dec 30, 2016 in Critical bug by canan (160 points)
edited Dec 30, 2016 by canan

First, really good job for your awesome asset.

But I found a big bug :
1. I build my project for Android, just a simply one to test all abilities that interest me for my real project
2. I install it on differents smartphone (Samsung S6, HTC M8, Nexus 5, HTC M9, Wiko Tommy, OnePLus 3T, etc.) to be sur of result (screen fit, button reaction, etc.)
3. But the resolution of buttons (and or screenview), toast size, and Back() function don't do the same on all devices !

List smartphone vs bug :
- Samsung S6 : Back() function redirect me on the previous one, but I am stuck on this screen (even if I can see buttons ann click on it, it doesn't redirect me on other screen, just do nothing)
- Wiko Tommy : when I change the selection of a DropDown, the screen resolution of all screenview change foe a big one
- Nexus 5 : depends on luck when build, all toast al so big that their width are the width of screen
- HTC M8 and M9 : perfect result

/!\ If I rebuild, and I test again on all devices (with clear uninstall and install), I have almost the same bug as previous installation, but sometimes fews disapear (like toast bug)

Very cordially.


NB : How can I make my button back on all devices worked as your back function, withour add a detection in code ?

2 Answers

0 votes
answered Jan 5, 2017 by admin (31,720 points)
Hi canan,

What scaling settings are you using?

~ Declan.
0 votes
answered Jan 5, 2017 by canan (160 points)
edited Jan 6, 2017 by canan

I use the size of my "Game View" in Unity3D for Android, depends on result I expect (portrait or landscape), 480x800 or 800x480.
So I put the same size on the "Canvas" for MaterialUI.

I tested on :
- Samsung S6 : 1440x2560 pixels (~577 ppi)
- Wiko Tommy : 1280x720 pixels (~294 ppi)
- Nexus 5 : 1080x1920 pixels (~445 ppi)
- HTC M8 and M9 : 1080x1920 pixels (~441 ppi)

Very cordially.
commented Jan 25, 2017 by admin (31,720 points)


If you're talking about the Back() function in regards to the ScreenView, then I'm pretty sure it's due to scaling issues, as are all the problems you've described.

You may be interested to know that I'm currently working on a more permanent solution (you can read more here).

As for your question regarding the back button functionality - unfortunately there isn't really a way to do this without a fair bit of coding involved just yet, although I am planning on adding automatic functionality to all applicable components (at some point).

~ Declan.

Welcome to MaterialUI support! Ask us anything :)