Troubleshooting ML on Android Mobile Devices
-
Here's a list of all the VM's I've built and tested it on. All of them are running the latest version of Android OS - KitKat, and the latest version of Chrome. Also all of these were tested with their stock browser (In some cases this is Chrome).
Nexus 10 - Worked, May have issues with Landscape mode in some of the posts that have pictures posted in them at resolutions that are not in a 16:9 or 16:10 resolution, due to the 2560 x 1600 display being just plain goofy.
Nexus 7 - Worked
Nexus 5 - Worked
Nexus 4 - Did not work, factory reset and VM rebuild did not work, but Google Chrome works.
Nexus S - Worked
Nexus One - Worked
HTC One - Worked
Galaxy Note S4 - Worked
Galaxy Note S3 - Worked
Galaxy S4 - Worked
Galaxy S5 - Did not work, factory reset and VM rebuild did work
Sony Xperia Advance - Worked
Sony Xperia M - Worked
Sony Xperia ZL - VM did not boot
Sony Xperia Z1S LTE - Worked
And this last one just for fun
NVIDIA Shield - Working, loading, and running at a better speed than any other tested device. -
Seems to be no rhyme or reason as to why some didn't work...
-
I'm starting to believe that there may be something going haywire in the internal workings of the browser. It seems either chrome ties into the browser or vice versa. Does anyone experience this issue that we can use as a lab rat?
-
I've run through a lot of common Android browser coding breaks on the S4 and Nexus 7, the most stable of the VM's, and I can't seem to get MangoLassi to NOT work... Perhaps firewall is an issue???
-
The Razr was attempted under 4G as well, so firewall is unlikely for that.
-
so I have the Razr and this is what i see. Going to the main page upon first initial visit, site loads, but when i try to navigate anywhere else i get stuck.
-
Possible 4G incompatibility with ML? Also, any sort of Antivirus filters or Phone-to-hotspot conversion setups can mess with things.
-
@david.wiese Are you running any sort of software/application on that phone that does any sort of Browser Filtering?
-
@Mike-Ralston nope, no a/v on the device either.
-
@david.wiese Even if you jump into the topics on ML, or the groups, you get stuck? Maybe you could try uninstalling the updates for Chrome, trying it then, then update again and try it updated?
Sorry, I'm still trying to narrow down where this issue might even begin.
-
I use Chrome on an up to date Nexus 7, no issues.
-
@FiyaFly said:
Galaxy S4 - AT&T - ? - 4.4.2 - 34.0.1847.114 - 1.5.28 - Yes*
*- This has been resolved with a factory reset.
I'm guessing this was mine.
I have been using both Wifi and 4G.
the problem only seems to be resolved in Chrome, not the default Android browser. -
@scottalanmiller said:
I use Chrome on an up to date Nexus 7, no issues.
In my experience, the Nexus 7 is one of the most stable Android devices. My personal favorite for testing and troubleshooting Android.
-
@Dashrender I see. And yes, to both you and @david.wiese those were your devices. Could you try removing the updates and trying again, both out of date and after updating the browser again?
-
@Dashrender We've been testing internally on separate S4's. Would you mind being a guinea pig once more?
EDIT I'm mistaken, the Razr Maxx and the S4 listed in the root post are yours. -
@Mike-Ralston said:
Perhaps firewall is an issue???
I'm going to try on 4G only now to see if my office firewall is causing an issue.
-
I will try that this evening and report back
-
It seems with the new update all issues have been solved. On both the VM's and physical devices, everything works fine, except that pesky Nexus 10 with the format. This issue is now closed!
-
@Mike-Ralston said:
It seems with the new update all issues have been solved. On both the VM's and physical devices, everything works fine, except that pesky Nexus 10 with the format. This issue is now closed!
Cool. The update includes a new front end that might alter things.
-
That it did, fixed a nice number of issues.
