Open Bug 802118 Opened 7 years ago Updated 4 years ago

Improve update detection in update service in WiFi-only environments

Categories

(Firefox for Android :: General, defect)

ARM
Android
defect
Not set

Tracking

()

People

(Reporter: aryx, Unassigned)

References

Details

Firefox for Android trunk nightly 20121012, Android 4.1.1, Google Nexus S

Since the switch to the android update service in bug 786380 I hardly get updates (and a substantial part of the download fails, likely due to connection loss). The device only connects via Wifi to the internet and my browsing session last between 1 and 20 minutes. Wifi gets turned on and off before accessing it, updates for apps installed via Google Play are shown more often. Twice it has taken a week until I got the next update for Fennec.
Snorp?
Blocks: 786380
So the device only has a connection to the internet for a few minutes and only during your browsing session? That would mean that the scheduled update checks are likely to fail. We could fix this in a few different ways. Probably the most reliable one would be to listen to notifications for network changes, and once you connect to the network we could check for updates if we are overdue.
Tangentially related potential use case for relevant developer pondering:
 - Very rare internet connectivity for a group of devices (eg. remote location).
 - One device travels elsewhere, receives an update, returns with a signed update. The device could be able to share the update over ad-hoc wifi connections with its peers (eg. wifi via 'connection sharing').
 - Search could be triggered via current 'search for updates'
 - In the developing world where downloads are slow and access points often shared (very slow at peak times) this could be very useful. Overall, not too dissimilar to the use case described on this thread.
Filed ~related bug 945047
You need to log in before you can comment on or make changes to this bug.