- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
With the latest app update, the signal strength went down and it also is inconsistent between Ipad and Android devices. Why does my Ipad (1 device) app show all 3 bars while at the same time, my android (2 devices) app only shows 2 bars?
- Related Labels:
-
Online and Mobile Apps

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Who knows? What percentages are reported?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
emsherman0 wrote:With the latest app update, the signal strength went down and it also is inconsistent between Ipad and Android devices. Why does my Ipad (1 device) app show all 3 bars while at the same time, my android (2 devices) app only shows 2 bars?
I noticed the same, though between Android and Web.
- 80% signal strength is reported with two "bars" in the Android app, but has three in the Web UI.
- 60% signal strength shows with one "bar" in Android app, but two in Web UI.
So, it looks as if the Android app is underreporting signal strength by one "bar".
What's also strange is that the percentage reading is only available in the app, but not in the Web UI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
'Scuse me? It's in my web interface.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I normally use Chrome and it's fine. Just tried FF and it's not there. Edge shows it fine.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
jguerdat wrote:I normally use Chrome and it's fine. Just tried FF and it's not there. Edge shows it fine.
Yup. Not there with Firefox. Not there in Chrome version 49.x. Since Chrome's current version is 50.x, it must be due to that.
