← Back to team overview

ubuntu-phone team mailing list archive

  1. ubuntu-phone team
  2. Mailing list archive
  3. Message #15675

Re: No Carrier on Meizu MX4 Ubuntu Edition

  Thread Previous • Date Previous • • Thread Next 
Dear Ubuntu Team
I tried with five another SIMs(service providers) and the handset was working absolutely fine with 3 Carriers, only two Carrier gave similar problems.
The Flight Mode toggle also worked perfectly except for these two service providers/carriers where after switching off the "flight mode" No SIM was displayed by the Ubuntu Touch.
I am fine with the present arrangement but if you assess any issues then it needs fixing. 

Another issue is
I am now not able to mount the storage drive once I plug it to my Desktop(Ubuntu), updated the usb id list, it is recognised and displayed properly on lsusb but not able to show and mount in display manager. 

Pls help on this issue

Regards

On Saturday 19 September 2015 02:34 AM, "@j"@y wrote:

Dear Tony

I shall try with another SIM(service provider) and provide the feedback.
There is no syslog present in /var/log even after restarting number of times. 

Output of ls -l/var/log is given below.

            total 11448
        -rw-r--r-- 1 root root   11886 Aug 25 23:08 alternatives.log
        -rw-r----- 1 root adm      797 Sep 19 02:09 apport.log
        -rw-r----- 1 root adm     5318 Sep 18 22:09 apport.log.1
        -rw-r----- 1 root adm      487 Sep 18 11:14 apport.log.2.gz
        -rw-r----- 1 root adm     1039 Sep 16 23:46 apport.log.3.gz
        -rw-r----- 1 root adm      587 Sep 16 00:25 apport.log.4.gz
        drwxr-xr-x 2 root root    4096 Sep 15 15:04 apt
        -rw-r--r-- 1 root root   67738 Aug 25 22:45 bootstrap.log
        -rw-rw---- 1 root utmp       0 Aug 25 22:40 btmp
        -rw-r----- 1 root adm   112304 Sep 18 23:54 dmesg
        -rw-r----- 1 root adm    89549 Sep 18 23:52 dmesg.0
        -rw-r----- 1 root adm    27782 Sep 18 22:11 dmesg.1.gz
        -rw-r----- 1 root adm    25612 Sep 18 22:09 dmesg.2.gz
        -rw-r----- 1 root adm    25320 Sep 18 20:42 dmesg.3.gz
        -rw-r----- 1 root adm    31861 Sep 18 14:22 dmesg.4.gz
        -rw-r--r-- 1 root root  790990 Aug 25 23:07 dpkg.log
        -rw-r--r-- 1 root root  768288 Aug 25 23:07 faillog
        -rw-r--r-- 1 root root    1296 Aug 25 22:57 fontconfig.log
        drwxr-xr-x 2 root root    4096 Sep 15 15:04 fsck
        drwxr-xr-x 2 root root    4096 Sep 15 15:04 installer
        -rw-rw-r-- 1 root utmp 9347504 Aug 25 23:07 lastlog
        drwxr-xr-x 2 root root    4096 Sep 18 23:52 lightdm
        drwxr-xr-x 2 root root    4096 Sep 16 23:44 lxc
        drwxrws--- 2 root root    4096 Sep 15 23:25 system-image
        drwxr-xr-x 2 root root    4096 Sep 18 22:13
        ubuntu-download-manager
        drwxr-xr-x 2 root root    4096 Sep 18 23:52
        ubuntu-location-service
        -rw-r--r-- 1 root root  258047 Sep 18 23:52 udev
        drwxr-x--- 2 root adm     4096 Sep 16 00:23 unattended-upgrades
        drwxr-xr-x 2 root root    8192 Sep 19 00:17 upstart
        -rw-rw-r-- 1 root utmp   64128 Sep 18 23:54 wtmp

/var/crash does not have any .crash files present
I purchased the phone new with Ubuntu installed, it updated itself after prompting to latest release after I connected it to my WiFi network. 

Happy to respond to any more queries if you have.

Regards




On Saturday 19 September 2015 01:22 AM, Tony Espy wrote:

On 09/18/2015 02:42 PM, "@j"@y wrote:

Dear Community

Output when executing script "/usr/share/ofono/scripts/list-modems" is
at as txt file


Thanks for the debug information.
It appears you're in India, and that you're using a 'Reliance' SIM? Do you have another SIM you can try? There's a possibility this may be an interoperability problem with the MX4 and Reliance. 


There is no syslog present in /var/log
That's not a good sign. Can you restart the phone and check again? If there's still not a syslog present, can you paste the output of 'ls -l /var/log' for us?
Also can you check /var/crash and let us know if there are any .crash files present?
output of the command 'system-image-cli -i' run on the phone is appended 
below :-

        current build number: 4
        device name: arale
        channel: ubuntu-touch/stable/meizu.en
        last update: 2015-09-15 15:04:36
        version version: 4
        version ubuntu: 20150825.1
        version device: 20150818-0b38025
        version custom: 20150814-887-8-46

Nothing other than apps from the store or standard updates has been
installed.
OK, great. One more question, I assume you purchased the phone new with Ubuntu installed? 


I have very decent signal strength in my location.

When I lose carrier, if I check the network menu, it says "Unregistered
"for the SIM status.

if I toggle flight-mode and donot lock the screen, the phone is able to
re-register promptly and become usable again but if i toggle flight-mode 
and the screen is locked it does not re-registers itself and "Unknown"
is shown for the SIM status, "None is shown for the Carrier".

The Telegram app also forcibly logs you out once the screen gets locked
and is unlocked again. It shows you as unauthorised user, all the chats
get cleared up and it restores itself to initial setup screen.

I am using a four digit PIN to lock the screen.

I believe the problem is with the screen locking up.


This isn't supposed to have any effect on the modem...


I hope that helps!


It's a start!

/tony

Follow ups

References

  Thread Previous • Date Previous • • Thread Next