Last modified: 2013-10-30 15:02:42 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T43636, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 41636 - Nearby only waits 10 seconds
Nearby only waits 10 seconds
Status: RESOLVED WONTFIX
Product: Wikipedia App
Classification: Unclassified
Near by (Other open bugs)
Unspecified
Other other
: Normal major
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-11-01 14:39 UTC by Andreas Kuckartz
Modified: 2013-10-30 15:02 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: Android 2.2
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Andreas Kuckartz 2012-11-01 14:39:21 UTC 
The "nearby" feature only waits 10 seconds until the satelites are found. It takes significantly longer on a Samsung Galaxy S (GT-I9000) with Android 2.2.1.

I have had this problem in all Wikipedia App versions up to now, including the recent 1.3.1. The "nearby" feature therefore is unusable.

My suggestion is to wait at least 120 seconds, maybe configurable.
Comment 1 Brion Vibber 2012-11-21 00:30:02 UTC 
120 seconds is... wwwaaaayyyyy too slow to be usable, surely?

If we're not getting *any* data back for a long time, we've got nothing to show on screen and no progress... not sure we can distinguish between "it might work in the future" and "you probably don't have GPS signal".

If on the other hand we're getting less accurate pingback information while it's running, we could jump around the map I guess. Hmm...
Comment 2 Brion Vibber 2013-10-30 15:02:42 UTC 
Current app no longer maintained, will be retired. New app will be implemented differently.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links