Open GoogleCodeExporter opened 8 years ago
[deleted comment]
I have the same issue. I can set the temperature units of the weather but the
extension never shows up on my lockscreen.
Original comment by scot.cow...@gmail.com
on 14 Feb 2013 at 4:53
Likely something related to network location. Do you all have location services
turned on? Per the FAQ [1], DashClock uses network location, not GPS, so that
must be enabled.
[1] http://code.google.com/p/dashclock/wiki/FAQ
Original comment by roman.nurik
on 15 Feb 2013 at 3:08
[deleted comment]
The weather widget won't show up for me either, not even after a day. Location
services are on and Yahoo Weather knows my location. LG Nexus 4 with 4.2.2.
Original comment by trilsb...@gmail.com
on 17 Feb 2013 at 2:58
it showed up eventually at my work location (5 miles from my house) and now
seems to stay even at home. Maybe the location info from location services
doesn't map 100% to Yahoo's WOEID?
Original comment by trilsb...@gmail.com
on 18 Feb 2013 at 9:22
@trillsbeek: as of 1.2, the weather extension tries to find a WOEID in
decreasing precision order (locality, suburb, town, city, state, etc.)... if
it's not finding anything at all, perhaps the app can't find your coarse
location... in v1.3 you'll see a more obvious "Location could not be
determined" error that'll give you more of a clue as to what's going on.
improvements can definitely be made in the future to the weather extension.
Original comment by roman.nurik
on 19 Feb 2013 at 1:55
I don't know what the issue was, it is there now all the time with varying
location precision (locality, suburb, city). The error message will indeed be
helpful. Anyway, thanks a lot for providing this widget, it's by far the most
useful lockscreen widget!
Original comment by trilsb...@gmail.com
on 19 Feb 2013 at 8:18
I am not sure if this is Rom related, location related or something else. I
have this installed on both my Galaxy Nexus and Nexus 7 and I do not get
weather data. Both are set to have Location Access via GPS and Wifi Mobile. On
both devices I have the no weather data available shown with the latest version
on my lock screen. Weather hasn't worked on any version of CM10.1 I have run or
any version of dashclock.
I am currently in the US, Eastern Pennsylvania running Cyanogenmod 10.1
nightlies from this week(4.2.2).
Original comment by jeffalicea
on 22 Feb 2013 at 12:05
Seconding the weather data not being available on CM10.1 builds. I am in
Seattle running 10.1 nightlies from this week (4.2.2).
Original comment by trey.causey@gmail.com
on 22 Feb 2013 at 1:12
Resolved the CM10.1 issue. It's AdBlock.
Original comment by trey.causey@gmail.com
on 22 Feb 2013 at 9:07
AdBlock? interesting... anyone else seeing this issue have that installed?
Original comment by roman.nurik
on 22 Feb 2013 at 9:12
Same issue here on Nexus 4 rom stock.
Weather doesn't show anything.
Is there any way to use it without the GPS???
Original comment by aeden.hi...@gmail.com
on 24 Feb 2013 at 1:10
[deleted comment]
Just to follow up, in v.1.3 I never get a location when I'm at home. Other apps
have no issue getting my approximate location (only relying on cell network,
i.e. GPS and WiFi turned off), so I'm still wondering whether there is a
mapping issue. Is there any way to find out what is given out by location
services?
The option to put in a location manually will be a workaround but I'd rather
have it set automatically depending on where I am.
Original comment by trilsb...@gmail.com
on 24 Feb 2013 at 2:06
[deleted comment]
I'm experiencing the issue with adblock enabled as well. I've tried with easy
list and fan boy's list. It looks like the url in
WeatherExtension.java:buildPlaceSearchUrl(Location l) is the one that is being
blocked.
Original comment by ksufin...@gmail.com
on 14 Mar 2013 at 2:58
The latest adblock plus for android release (v1.1) fixed the issue for me. If
you were running abp, you'll have to install the apk manually because it's been
removed from the play store. Here is the brief changelog:
http://adblockplus.org/releases/adblock-plus-11-for-android-released
Original comment by ksufin...@gmail.com
on 24 Mar 2013 at 1:40
Original issue reported on code.google.com by
MrAtlant...@gmail.com
on 12 Feb 2013 at 4:17