ubuntu-phonedations-bugs team mailing list archive
-
ubuntu-phonedations-bugs team
-
Mailing list archive
-
Message #02180
[Bug 1592232] Re: USA: Meizu Pro 5 changes from cellular carrier to "Denied" (AT&T and T-Mobile)
Is their a way to view signal strength other than by running
/usr/share/ofono/scripts/list-modems?
I'm trying to find out if I'm denied because of lack of signal or some
other reason. If I'm "DENIED" at the time, signal strength isn't listed
in the output. Here's an example with the same CELLID and
LocationAreaCode
Working:
[ org.ofono.NetworkRegistration ]
Mode = manual
MobileNetworkCode = 410
Name = cricket
LocationAreaCode = 7981
Status = registered
Strength = 25
MobileCountryCode = 310
CellId = 160075533
Technology = hspa
DENIED:
[ org.ofono.NetworkRegistration ]
Mode = manual
CellId = 160075533
Technology = hspa
Name =
LocationAreaCode = 7981
Status = denied
--
You received this bug notification because you are a member of Ubuntu
Phonedations bugs, which is subscribed to ofono in Ubuntu.
https://bugs.launchpad.net/bugs/1592232
Title:
USA: Meizu Pro 5 changes from cellular carrier to "Denied" (AT&T and
T-Mobile)
Status in turbo:
New
Status in ofono package in Ubuntu:
Confirmed
Bug description:
current build number: 102
device name: turbo
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2016-06-13 17:24:38
version version: 102
version ubuntu: 20160611
version device: 20160531-61c5e72
version custom: 20160504-975-19-6
While walking around outside, signal strength goes from full bars to "Denied" or "Unavailable." This occurs with one SIM card in SIM Slot One and the second slot empty. I have noticed the behavior with both the US provider T-Mobile and AT&T. This will occur while driving as well. Sometimes, the phone will have to be restarted before signal bars are displayed again. However, restarting does not always fix it. This occurs both in Los Angeles, CA and Washington, DC as well as other major cities. If stationary, I can expect reasonable speeds and reliable service all day without interruption.
To manage notifications about this bug go to:
https://bugs.launchpad.net/turbo/+bug/1592232/+subscriptions
References