ML not working on Mobile Chrome
-
I tried logging into ML this weekend on my android (both on wifi and 4G) and the pages didn't load. It just sat there and did nothing. I tried logging in and once again it just sat there. Anyone else having this issue. By the way I am on Jelly Bean 4.1.2
-
I have a thread that's about a week old on this same topic.
I did a hard reset last week and still have the same problem with both the default browser and Chrome on Android. Makes me wonder what's different for IOS than Android?
-
@Dashrender said:
I have a thread that's about a week old on this same topic.
I did a hard reset last week and still have the same problem with both the default browser and Chrome on Android. Makes me wonder what's different for IOS than Android?
didn't see that one, i really should know better....
-
No trouble here on Chrome on my android device.
Using KitKat - 4.4.2 -
Seems to be doing alright for me. 4.1.2 Android on a Droid 4. Posting from it right now. Is there any other detail you might have on this one?
-
i am on a droid razr maxx hd on 4.1.2. I have not done a factory reset of the phone because I am due for an upgrade and my speaker just went :(. I have cleared the cache and cookies with the same results.
-
@david.wiese Yeah, I figure a factory reset would be a bit overkill anyway. A hard reset, like @Dashrender mentioned attempting, I think is defaulted to holding the power and down volume buttons simultaneously on Android for 5 seconds, Just does a power cycle. Are there any updates available for your chrome version on your Razr? My chrome looked and ran different when I pulled it up a few minutes ago.
-
@FiyaFly said:
@david.wiese Yeah, I figure a factory reset would be a bit overkill anyway. A hard reset, like @Dashrender mentioned attempting, I think is defaulted to holding the power and down volume buttons simultaneously on Android for 5 seconds, Just does a power cycle. Are there any updates available for your chrome version on your Razr? My chrome looked and ran different when I pulled it up a few minutes ago.
I didn't do a 'power cycle' I did a full data wipe and resetup of the device. Major pain since I had to disable Dual Factor Authentication on a half dozen accounts before doing that so I wouldn't be locked out of those accounts.
-
@Dashrender Oh, Then I guess it was me who misunderstood that one. What type of phone are you using? This now has my curiosity. Also, are you on 4.1.2 as well?
-
I'm on a Samsung Galaxy S4 with Android 4.4.2. Android internet version 1.5.28, Chrome version 34.0.1847.114
-
This is what I have:
Phone- Droid 4 running Android 4.1.2, browser version 4.1.2-49, Chrome version 18.0.1025469
Tablet- Nexus 10 running 4.4.2, Chrome version 34.0.1847.114.Both of these devices work just fine for me. So, from the sounds, I have my tablet matching versions for @Dashrender and phone matching for @david.wiese but something is not jiving for you two. Depending on how deep we wanna get into this, what's the chances I can get some screenshots? I'm feeling in a troubleshoot-y mood today lol
-
I am on chrome 34.0.1847.114 as well. What kind of screen shots do you want. The site half loads then just sits there. I can select from unread/recent/popular but as i tap on one of them to select the site tries to load, the url changes but no content appears on the screen and the loading of the page never finishes
-
Not entirely sure yet. here's a good question- are these devices rooted?
-
I have reached out to a few members of the NTG team to see if they can reproduce this issue.
-
Chrome on iOS is Safari. Not actually Chrome.
-
@FiyaFly nope stock phone with whatever verizon placed on there
-
Mine is not rooted either. Stock AT&T here
-
I just tried Chrome for the first time since hard resetting. It appears to be working OK for me now... I guess I'll have to remember to use Chrome instead of the default browser for now.
-
This post is deleted! -
@Mike-Ralston said:
@scottalanmiller said:
Chrome on iOS is Safari. Not actually Chrome.
Unfortunately, you're right about that. Off topic though.
Not off topic. Someone directly asked why Chrome on Android and Chrome on iOS did not behave the same.
