Settings page unresponsive?
Closed this issue · 6 comments
I just installed Metar watchface on my pebble time, and the settings page doesn't seem to work. I can enter a new home airport, but clicking OK doesn't do anything. The face still shows JFK.
Likewise with selecting the option to use my location. Nothing changes on the watch. I'm based near CYVR.
This happened with another user. Something in his phone's browser settings
was disabling JavaScript. JS is required to return the info from the web
page to the Pebble.
On Tue, Jun 16, 2015 at 2:51 AM Rob notifications@github.com wrote:
I just installed Metar watchface on my pebble time, and the settings page
doesn't seem to work. I can enter a new home airport, but clicking OK
doesn't do anything. The face still shows JFK.Likewise with selecting the option to use my location. Nothing changes on
the watch. I'm based near CYVR.—
Reply to this email directly or view it on GitHub
#1.
Odd. Chrome reports that Javascript is allowed... And I can load another page in Chrome that I know has Javascript (and I know the JS is running). Is there somewhere else in the phone where Javascript settings would be restricted? Is the internal browser that "Settings" uses not Chrome?
The Pebble app uses the OS' built-in browser. I don't have an Android phone, so I've never run into this problem myself
I think something must have changed in Lollipop (the latest version of
Android). There are no obvious settings for enabling Javascript on a
system-wide basis... All of the browsers show it as "allowed" but the
settings page still doesn't work. I'll google some more on the issue and
see if others are seeing it as well.
On Tue, Jun 16, 2015 at 9:03 AM, Michael duPont notifications@github.com
wrote:
The Pebble app uses the OS' built-in browser. I don't have an Android
phone, so I've never run into this problem myself—
Reply to this email directly or view it on GitHub
#1 (comment)
.
I went in and made the source links HTTPS. Might be why only a few phone/OS configs were complaining. Try it now
That worked. Flipping the switch to "use closest location" now saves and the watch updates properly. I was wondering if the problem was related to this one:
https://code.google.com/p/android/issues/detail?id=79924
It seems to be specific to Android 5.0, an issue introduced with the way javascript is handled using the internal WebView browser. Apparently it may be fixed in 5.1, alas my phone is still on 5.0.2.
Thanks for the fix though! It seems to be working fine now.