UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Unable to connect tho WiFi (on nexus 5)

    Scheduled Pinned Locked Moved Solved Support
    9 Posts 4 Posters 1.4k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • O Offline
      olga.bio
      last edited by

      Hi everyone,

      I flashed Ubuntu on a nexus 5 yesterday, without any apparent issues. But once booted up the phone is unable to connect to WiFi. I do see the networks and when clicking on my network I am prompted to enter the password. But after doing it, no connection is established and after a minute or two I am prompted to enter the password again and so on. I have checked the pw (and have other people check it), so that is not the root of the issue. Flashing the image from a different channel (stable, dev, rc) did not help either.
      Additionally in the software licences tab in the settings there is "License can not be shown" message when I look at the network manager. Is there any solution to it? Are there any logs where I can see more details?

      P.S. I can no longer activate the developer mode after I have flashed the dev image, even when I go back to stable.

      Thanks in advance!

      O 1 Reply Last reply Reply Quote 0
      • O Offline
        olga.bio @olga.bio
        last edited by

        This post is deleted!
        saveurlinuxS 1 Reply Last reply Reply Quote 0
        • saveurlinuxS Offline
          saveurlinux @olga.bio
          last edited by

          @olga-bio The logs may be into the /home/phablet/.cache/upstart folder

          1 Reply Last reply Reply Quote 0
          • O Offline
            olga.bio
            last edited by

            @saveurlinux thanks for the help. Now I have found a network log, but there is no immediate red flag jumping at me apart from
            (process:3323): GLib-GIO-WARNING **: Error releasing name com.canonical.indicator.network: Connection closed
            which might have resulted from me closing the second password prompt after trying to log onto the WiFi once.
            P.S. Yepp, there is no sim card in the phone as of now.

            Debug: nmofono::KillSwitch::KillSwitch(const QDBusConnection&) reply.isValid() true reply.value() false reply.error() QDBusError("", "") ((null):0, (null))
            Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/0" ((null):0, (null))
            Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/1" ((null):0, (null))
            Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/2" ((null):0, (null))
            Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/3" ((null):0, (null))
            Debug: Adding modems QSet("/ril_0") ((null):0, (null))
            Debug: Unlock all modems ((null):0, (null))
            Debug: Waiting for modem to be ready "SIM 1" ((null):0, (null))
            Debug: Notify when ready to unlock "SIM 1" ((null):0, (null))
            Debug: Setting flight mode enabled = true ((null):0, (null))
            Debug: Setting WiFi enabled = false ((null):0, (null))
            Debug: Setting flight mode enabled = false ((null):0, (null))
            Debug: Setting WiFi enabled = true ((null):0, (null))
            Debug: Connecting to: "Vodafone-4E84" ((null):0, (null))
            Debug: Connecting to known access point ((null):0, (null))
            
            (process:3323): GLib-GIO-WARNING **: Error releasing name com.canonical.indicator.network: Verbindung ist geschlossen
            Debug: nmofono::KillSwitch::KillSwitch(const QDBusConnection&) reply.isValid() true reply.value() false reply.error() QDBusError("", "") ((null):0, (null))
            Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/0" ((null):0, (null))
            Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/1" ((null):0, (null))
            Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/2" ((null):0, (null))
            Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/3" ((null):0, (null))
            Debug: Adding modems QSet("/ril_0") ((null):0, (null))
            Debug: Unlock all modems ((null):0, (null))
            Debug: Waiting for modem to be ready "SIM 1" ((null):0, (null))
            Debug: Notify when ready to unlock "SIM 1" ((null):0, (null))
            
            
            1 Reply Last reply Reply Quote 0
            • O Offline
              olga.bio
              last edited by

              Well that is embarrassing... It seems that the issue is not on UB side, as the issue persists after reverting to Android. Sorry for the fuss.
              Though not technically solved, it is best to delete the topic then?

              AppLeeA 1 Reply Last reply Reply Quote 0
              • AppLeeA Offline
                AppLee @olga.bio
                last edited by

                Hi @olga-bio
                No need to delete the topic, just mark it solved so people looking for such issue think about checking the hardware.

                You can mark it using the cog wheel menu in the top of the page:
                1- Ask a question
                2- Mark as solved

                O 1 Reply Last reply Reply Quote 0
                • O Offline
                  olga.bio @AppLee
                  last edited by

                  @applee Thanks & done

                  1 Reply Last reply Reply Quote 1
                  • KenedaK Offline
                    Keneda
                    last edited by

                    Is it your wifi router ?
                    Isn't it filtering devices by MAC address ?

                    I have a N5 and no problem to connect on WIFI on my router, but as i make my router filtering MAC adresses on WIFI, i must add any new device MAC to make it work.

                    2015-2023 : Meizu MX4 ☠️⚰️✝️
                    2023-2024 : Nexus 5 ☠️⚰️✝️
                    2024-***** : FPOS Fairphone 5
                    🇲🇫🇬🇧

                    O 1 Reply Last reply Reply Quote 0
                    • O Offline
                      olga.bio @Keneda
                      last edited by

                      @keneda not in my case. The router itself was malfunctioning. After we have got a replacement everything works fine on both Android and Ubuntu

                      1 Reply Last reply Reply Quote 0

                      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                      With your input, this post could be even better 💗

                      Register Login
                      • First post
                        Last post