[connectivity-service] bandwidth limitation detection not functioning
Bug #1362592 reported by
Dan Chapman
This bug affects 5 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| indicator-network (Ubuntu) |
Triaged
|
High
|
Unassigned | ||
Bug Description
The bandwidth limitation detection is still missing from the connectivity-api. It would be great to have the ability to know when the network is on a potentially expensive/bandwidth limited connection.
| Changed in indicator-network: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| affects: | indicator-network → connectivity-api |
| Changed in connectivity-api: | |
| assignee: | nobody → Antti Kaijanmäki (kaijanmaki) |
Revision history for this message
| Michael Sheldon (michael-sheldon) wrote | #1 |
| Changed in indicator-network (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| no longer affects: | connectivity-api |
| summary: |
- bandwidth limitation detection not functioning in the connectivity-api + [connectivity-service] bandwidth limitation detection not functioning |
| Changed in indicator-network (Ubuntu): | |
| importance: | Medium → High |
To post a comment you must log in.
This bug is still present in vivid-proposed r172 and currently prevents us from implementing an "automatically download only on Wifi" option in Podbird (the podcast manager) as the "limitedBandwith" property always returns false regardless of the type of connection.