regression cannot connect to 3g network on boot on vivid r129

Bug #1431026 reported by taiebot65
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ofono (Ubuntu)
Incomplete
Undecided
taiebot65

Bug Description

Device nexus 4 mako running devel-proposed r129

On stable and devel channel 3g connection works as expected.

On vivid channel r129 i can not connect to 3g network, after booting my phone. If i restart ofono with sudo stop ofono and sudo start ofono multiple times, after a while i manage to get an active connection but i lose the indicator icons and it just becomes a setting icon.

Everything works after that as expected. i have attached the 2 ./list-modems one after a fresh boot and one after i manage to connect to the 3g network. i am also attaching a picture of the setting icon.

Revision history for this message
taiebot65 (dedreuil) wrote :
Revision history for this message
taiebot65 (dedreuil) wrote :
Revision history for this message
taiebot65 (dedreuil) wrote :
Revision history for this message
taiebot65 (dedreuil) wrote :
description: updated
Revision history for this message
taiebot65 (dedreuil) wrote :

On first boot when i ran nmcli d Wifi turned off
DEVICE TYPE STATE CONNECTION
ril_0 gsm unavailable --
wlan0 wifi unavailable --

wifi on
DEVICE TYPE STATE CONNECTION
wlan0 wifi connected OpenWrt
ril_0 gsm unavailable --

I

taiebot65 (dedreuil)
description: updated
Revision history for this message
taiebot65 (dedreuil) wrote :
Tony Espy (awe)
Changed in ofono (Ubuntu):
status: New → Incomplete
assignee: nobody → taiebot65 (taiebot65)
Tony Espy (awe)
Changed in ofono (Ubuntu):
assignee: taiebot65 (taiebot65) → taiebot65 (dedreuil)
Revision history for this message
Tony Espy (awe) wrote :

@taiebot65

Starting and stopping ofono multiple times isn't advised.

I looked at the output of list-modems in comment #1 and comment #2, and in both cases the your phone is registered to Vectone with 'umts', and ofono's ConnectionManager interface shows your device as both 'Powered' and 'Attached' with bearer = 'hspa'.

Can you also run 'list-contexts' after you boot the device, and attach /var/log/syslog? The dmesg file isn't really helpful as it just shows kernel messages, whereas NM logs to syslog, and we can see connection activation attempts.

Also, after booting, please wait least 5m and see if the device activate your mobile data connection.

Revision history for this message
Tony Espy (awe) wrote :

I'm also not sure what you meant by comment #5.

Was WiFi enabled when you booted the device? You say "On first boot when i ran nmcli d Wifi turned off" and then the output shows both /ril_0 ( the modem ) and WiFi as unavailable. If you disable WiFi, urfkill remembers this state and will preserve it even across reboots.

Revision history for this message
taiebot65 (dedreuil) wrote :

Regarding comment #8 yes i turned off wifi before rebooting that what i meant.

Revision history for this message
taiebot65 (dedreuil) wrote :

Attaching /var/log/syslog but all the output is from Aug the 19??

Revision history for this message
taiebot65 (dedreuil) wrote :

[ /ril_0 ]
    [ /ril_0/context23 ]
        Active = 0
        Settings = { }
        Name = ___ubuntu_custom_apn_internet
        Password =
        Protocol = ip
        AccessPointName = webuk.mundio.com
        Username =
        IPv6.Settings = { }
        Type = internet

Revision history for this message
taiebot65 (dedreuil) wrote :

Even after 20 min i cannot connect to 3g but it looks like ofono tries to connect to /ril_0/context1 while mine is 23.

This is certainly a duplicate of https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1415495
as i used to have more than 20 APN at one time because when you where entering the APN editor window another entry was added

Revision history for this message
Tony Espy (awe) wrote :

@taiebot65

Please contact me on IRC again tomorrow to discuss this bug. The fact that you have 23 contexts is pretty bad, and I'd like to help you fix this.

Revision history for this message
Tony Espy (awe) wrote :

After a bit of poking at taiebot's system, we discovered the permission in /var/log are messed up, with syslog being owned by usermetrics:adm instead of syslog:adm.

According to taiebot, the phone has been continually updated since Oct 2014, and at times, and the channel changed at times as well.

As such, until we can get base functionality restored ( via a fresh flash which is what I've recommended ), I'm going to leave this bug as Incomplete for now.

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.