USA: Meizu Pro 5 changes from cellular carrier to "Denied" (AT&T and T-Mobile)

Bug #1592232 reported by Seth
30
This bug affects 7 people
Affects Status Importance Assigned to Milestone
turbo
New
Undecided
Unassigned
ofono (Ubuntu)
Confirmed
Undecided
Unassigned

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.

Revision history for this message
slash (slash-tux) wrote :

The same on rc-proposed mako in Houston

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ofono (Ubuntu):
status: New → Confirmed
Revision history for this message
SuperIke (ilkka-kalliainen) wrote :

Same issues here in Finland with Sonera, DNA and Elisa. Tested both sim slots.

Revision history for this message
Seth (seth-ciango) wrote :

I have created a video and log file to demonstrate some of the behavior.

Step 1: Notice "No Network" at dialer screen for "SIM 2 AT&T." "SIM 1 Cricket" shows connected
Step 2: Visually verify connections
Step 3: Select SIM 2 AT&T at the dialer screen
Step 4: Successfully dial the US Naval Observatory Time Announcer to verify connection to AT&T network
Step 5: Hang up
Step 6: Visually verify that "No Network" is still displayed for "SIM 2 AT&T"

This happens no matter which SIM card is in which slot. In this instance, AT&T was not showing service. However, Cricket and T-Mobile will exhibit the same behavior of "No Network" yet successfully make phone calls.

Revision history for this message
Seth (seth-ciango) wrote :

Attaching video file

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :

@Seth, thanks for the detailed description. Pasting the output of the execution of /usr/share/ofono/scripts/list-modems would be helpful here.

Revision history for this message
Seth (seth-ciango) wrote :
Download full text (6.5 KiB)

Here you go, Alfonso.

I'm happy to provide any additional information that I edited out in an email to you directly if you need it.

Additional information about this scenario:
RIL 1 has the AT&T SIM card
RIL 0 has the Cricket SIM card

Cricket is an MVNO of AT&T. However, as I sat in the same exact spot as I did yesterday when I recorded the previous video, my phone said "DENIED" for AT&T (2G/3G) but Cricket (2G Saves Battery) was fine with solid signal. I executed the list-modems script, and the AT&T network came back as an [H] network with 2Mbps download speeds. Obviously not the best speeds that I've seen, but far from "DENIED." Updating from "DENIED" to "H" while executing the script may be a coincidence, but I figured that I would mention it.

/usr/share/ofono/scripts/list-modems log
___________________________________________________________________________________

[ /ril_1 ]
    Revision = S333_M86_20151002_CHNOPEN_MZ024
    Lockdown = 0
    Serial = xxxxxxxxxxxxx (Edited)
    Powered = 1
    Model = Fake Modem Model
    Features = gprs ussd net sms rat sim
    Emergency = 0
    Type = hardware
    Online = 1
    Manufacturer = Fake Manufacturer
    Interfaces = org.ofono.ConnectionManager org.ofono.CallForwarding org.ofono.CallBarring org.ofono.CallSettings org.ofono.SupplementaryServices org.ofono.NetworkRegistration org.ofono.Phonebook org.ofono.PushNotification org.ofono.MessageManager org.ofono.NetworkTime org.ofono.MessageWaiting org.ofono.RadioSettings org.ofono.SimManager org.ofono.CallVolume org.ofono.VoiceCallManager
    [ org.ofono.ConnectionManager ]
        RoamingAllowed = 1
        Attached = 0
        Powered = 1
    [ org.ofono.CallForwarding ]
        VoiceBusy =
        VoiceUnconditional =
        VoiceNoReply =
        ForwardingFlagOnSim = 1
        VoiceNotReachable =
        VoiceNoReplyTimeout = 20
    [ org.ofono.CallBarring ]
        VoiceIncoming = disabled
        VoiceOutgoing = disabled
    [ org.ofono.CallSettings ]
        CalledLinePresentation = disabled
        CallingLinePresentation = enabled
        ConnectedLinePresentation = unknown
        ConnectedLineRestriction = unknown
        VoiceCallWaiting = enabled
        CallingLineRestriction = off
        HideCallerId = default
        CallingNamePresentation = unknown
    [ org.ofono.SupplementaryServices ]
        State = idle
    [ org.ofono.NetworkRegistration ]
        Status = registered
        Mode = auto-only
        Technology = hspa
        Strength = 25
        CellId = 160075535
        Name =
        LocationAreaCode = 7981
    [ org.ofono.Phonebook ]
    [ org.ofono.PushNotification ]
    [ org.ofono.MessageManager ]
        Bearer = cs-preferred
        ServiceCenterAddress = +13123149810
        Alphabet = default
        UseDeliveryReports = 0
    [ org.ofono.NetworkTime ]
    [ org.ofono.MessageWaiting ]
        VoicemailMailboxNumber = +14432803092
        VoicemailMessageCount = 0
        VoicemailWaiting = 0
    [ org.ofono.RadioSettings ]
        FastDormancy = 0
        AvailableTechnologies = gsm umts lte
        TechnologyPreference = umts
    [ org.ofono.SimManager ]
        MobileCountryCode = 310
        ...

Read more...

Revision history for this message
Seth (seth-ciango) wrote :
Download full text (6.1 KiB)

I was just able to capture the inverse using the same script. Cricket was disconnected and AT&T was connected without a problem (See attached picture.) Again, my phone hasn't moved. It's been charging in the same location this entire time. However, service has changed for both SIM cards.

There seem to be lots of interesting changes between the last log that I posted and this one. Hope it helps!

[ /ril_1 ]
    Type = hardware
    Powered = 1
    Revision = S333_M86_20151002_CHNOPEN_MZ024
    Manufacturer = Fake Manufacturer
    Online = 1
    Interfaces = org.ofono.ConnectionManager org.ofono.CallForwarding org.ofono.CallBarring org.ofono.CallSettings org.ofono.SupplementaryServices org.ofono.NetworkRegistration org.ofono.Phonebook org.ofono.PushNotification org.ofono.MessageManager org.ofono.NetworkTime org.ofono.MessageWaiting org.ofono.RadioSettings org.ofono.SimManager org.ofono.CallVolume org.ofono.VoiceCallManager
    Lockdown = 0
    Emergency = 0
    Features = gprs ussd net sms rat sim
    Serial = xxxxxxxxxxxxxx
    Model = Fake Modem Model
    [ org.ofono.ConnectionManager ]
        Bearer = hsupa
        Powered = 1
        RoamingAllowed = 1
        Attached = 1
        Suspended = 0
    [ org.ofono.CallForwarding ]
        VoiceUnconditional =
        VoiceBusy =
        VoiceNoReplyTimeout = 20
        ForwardingFlagOnSim = 1
        VoiceNoReply =
        VoiceNotReachable =
    [ org.ofono.CallBarring ]
        VoiceOutgoing = disabled
        VoiceIncoming = disabled
    [ org.ofono.CallSettings ]
        ConnectedLinePresentation = unknown
        ConnectedLineRestriction = unknown
        VoiceCallWaiting = enabled
        CallingLineRestriction = off
        CalledLinePresentation = disabled
        CallingNamePresentation = unknown
        CallingLinePresentation = enabled
        HideCallerId = default
    [ org.ofono.SupplementaryServices ]
        State = idle
    [ org.ofono.NetworkRegistration ]
        Strength = 16
        MobileCountryCode = 310
        CellId = 160097075
        MobileNetworkCode = 410
        Technology = hspa
        Status = registered
        Name = AT&T
        LocationAreaCode = 7981
        Mode = auto-only
    [ org.ofono.Phonebook ]
    [ org.ofono.PushNotification ]
    [ org.ofono.MessageManager ]
        Bearer = cs-preferred
        UseDeliveryReports = 0
        ServiceCenterAddress = +13123149810
        Alphabet = default
    [ org.ofono.NetworkTime ]
    [ org.ofono.MessageWaiting ]
        VoicemailMailboxNumber = +14432803092
        VoicemailWaiting = 0
        VoicemailMessageCount = 0
    [ org.ofono.RadioSettings ]
        AvailableTechnologies = gsm umts lte
        TechnologyPreference = umts
        FastDormancy = 0
    [ org.ofono.SimManager ]
        FixedDialing = 0
        MobileCountryCode = 310
        SubscriberNumbers = xxxxxxxxxxx
        Retries =
        SubscriberIdentity = xxxxxxxxxxxx
        LockedPins =
        PinRequired = none
        PreferredLanguages = en
        BarredDialing = 0
        CardIdentifier = xxxxxxxxxxxxxxxxxxx
        MobileNetworkCode = 410
        Present = 1
    [ org.ofono.CallVolume ]
        Muted = 0
        Spe...

Read more...

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :

Duplicate of bug #1598181.

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

actually seems to be a separate issue per other comments

Revision history for this message
Seth (seth-ciango) wrote :

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

Revision history for this message
Seth (seth-ciango) wrote :

I spent an hour on the phone last night with AT&T. They stated that my phone should not be having this problem with their network, but they offered to give me a free Android phone anyway. I politely declined. AT&T reset my network status in their system and pushed out an updated PRL. This problem of being DENIED is still occurring when connecting to the same CellID that allowed me a connection earlier in the day. I will be connected to a tower without a problem on Tuesday but the next day while connected to the same tower, I am denied.

[ /ril_1 ]
    [ /ril_1/operator/310410 ]
        MobileCountryCode = 310
        Status = current
        Technologies = gsm umts edge hspa hspa
        MobileNetworkCode = 410
        Name = AT&T

[ /ril_0 ]

Revision history for this message
jessesmith (jessefrgsmith) wrote :

I still have this error, though much less frequently, now that OTA-14 has been installed on my Meizu Pro 5. I have found that to fix the "network denied" or "network unavailable" issue I need to reboot the phone and switch the mobile network setting from "2G" to "2/3/4G". Once the 4G network has been selected, the phone usually reconnects.

I'm not sure why the system keeps defaulting to 2G. Also, the only time I seem to come disconnected is if I have been moving around a lot. For example, driving in the car or visiting a new location. If I stay at home all day the phone has been maintaining its mobile/data connection.

I'm on the Telus network.

Revision history for this message
Seth (seth-ciango) wrote :

Thanks for the info, Jesse. In regard to the reboots not keeping your preferred network and defaulting back to 2G on the Meizu Pro 5, that is a specific bug that is affecting a number of people including me. Please subscribe to that specific bug as well here:

https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613327

Revision history for this message
W Mauldin (wkm2007) wrote :

If I change to a different APN, let it connect, then change back to the original APN, then it works.

I have to do this when I start the phone. This didn't use to be the case. Some change on the cell networks' parts?

I have AT&T, by the way.

Revision history for this message
Seth (seth-ciango) wrote :

AT&T did get rid of their 2G network in the US as of January 1, 2017. They are still using the same 850mhz spectrum for 3G. However, another one of the bugs for the Meizu Pro5 is that it will boot into 2G only mode and that has to be changed manually each time at boot because there is no 2G network for an AT&T customer.

What APNs are you using? Default or manually configured? What has your experience been in regard to coverage? For me, I still have to use Meizu Pro 5 as a test/development only phone because of the cellular coverage.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.