Open GoogleCodeExporter opened 9 years ago
GoogleCodeExporter
commented
9 years ago I'm getting the same issue. Disabling the GeolocationService in webkit fixes
temporally the situation. Is there a setting to disable the geo location
properly if there is no GPS on device?Original comment by grego...@gentil.com on 3 Oct 2010 at 10:08
GoogleCodeExporter
commented
9 years ago Please explain how to disable the webkit GeolocationService, thanksOriginal comment by cjohnson...@gmail.com on 22 Oct 2010 at 2:53
GoogleCodeExporter
commented
9 years ago I also get the same problem. Did your get the solution??Original comment by abukust...@gmail.com on 27 Oct 2010 at 4:40
GoogleCodeExporter
commented
9 years ago [deleted comment]I am facing same issue. The browser crashes when homepage (google.com) is being
loaded. If I stop the loading and divert it to some other sites (yahoo.com
etc.), it is not crashing.
Any pointers in this regard would be helpful.
Thanks in advance.
-ChaitralOriginal comment by chaitral...@gmail.com on 28 Jun 2011 at 11:50
GoogleCodeExporter
commented
9 years ago As Comment 1 said, disable GeolocationService will fix this problem.
ALso try tp disable GEOLOACTION in WebKit.
Changed ENABLE_GEOLOCATION=1 to ENABLE_GEOLOCATION=0 in
WebCore/Android.derived.v8bindings.mk
Or add a GPS HAL will also fixed this problem.Original comment by abukust...@gmail.com on 29 Jun 2011 at 12:59
GoogleCodeExporter
commented
9 years ago Is there any way to get the Geolocation? From the browser or from another app?Original comment by hsk...@syntomos.com on 8 Sep 2011 at 11:39
GoogleCodeExporter
commented
9 years ago You need to disable GPS/location based stuff.
You can disable this in the build system by removing
com.android.location.provider and com.android.location.provider.xml from
build/target/product/core.mk or by including core.mk in your platform specific
makefile and then filtering them out of the variable.
You can also hack GeolocationService.registerForLocationUpdates() in
GeolocationService.java to not update for GPS but this is a messier fix as it
is application side (webkit)Original comment by matthew....@gmail.com on 14 Nov 2011 at 5:18
GoogleCodeExporter
commented
9 years ago This upstream webkit patch fixes this issue for webkit alone:
http://pastebin.com/MgaDqxxe
Although other apps could behave errantly and not catch this exception or check
providers are enabled properly first, that behaviour is probably an app bug
that we should not try and plan ahead for though.Original comment by matthew....@gmail.com on 23 Nov 2011 at 2:49
Original issue reported on code.google.com by
cjohnson...@gmail.comon 10 Sep 2010 at 6:44