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

    after update to 24.04-1.3 calling is not possible anymore

    Scheduled Pinned Locked Moved Unsolved Xiaomi Poco X3 NFC
    14 Posts 2 Posters 137 Views 2 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.
    • B Offline
      bunt7 @gpatel-fr
      last edited by

      @gpatel-fr anyway thanks for your lines and good to know, that the problems with tones is frequently.

      B 1 Reply Last reply Reply Quote 0
      • KenedaK Keneda moved this topic from Support
      • B Offline
        bunt7 @bunt7
        last edited by

        Now I tried some thinks out. After I switched to only 2G calling work properly. But I cant use the internet anymore.
        Bevor the update I used always 2/3/4/5 G, and both were possible, calling and internet.

        G 1 Reply Last reply Reply Quote 0
        • G Offline
          gpatel-fr @bunt7
          last edited by

          @bunt7

          I think that your device is here:

          https://gitlab.com/ubports/porting/community-ports/android10/xiaomi-poco-x3

          try to return your phone to 1.2 using the link I provided.

          A direct return should be possible using sudo system-image-cli -b 2 -m 3

          Before doing it take note of the kernel version with uname -a

          After downgrade check if your phone works correctly, if not it's not a regression it's a random coincidence then post again here so we can investigate further.

          If yes (the problem is fixed in 1.2), it's indeed a regression of 1.3, then use again uname -a, if the output is NOT the same the problem may be in the kernel that was recompiled, so create an issue in the kernel subrepository, if the output is the same better create an issue in the other subrepository.

          1 Reply Last reply Reply Quote 0
          • B Offline
            bunt7
            last edited by

            I tryed today trevert my phone to a previous state, but it din'nt work.
            Tomorrow I will try again and tell if I sugseed.
            Thanks a lot for your support!

            G 1 Reply Last reply Reply Quote 0
            • G Offline
              gpatel-fr @bunt7
              last edited by

              @bunt7

              Since I found this trick in one week I have used it about 10 times without problem, I'd be interested in more details on what you tried and what happened.

              B 1 Reply Last reply Reply Quote 0
              • B Offline
                bunt7 @gpatel-fr
                last edited by

                @gpatel-fr I pased: "sudo system-image-cli --switch 24.04-1.x/arm64/android9plus/stable" but nothing happend

                G 1 Reply Last reply Reply Quote 0
                • G Offline
                  gpatel-fr @bunt7
                  last edited by

                  @bunt7 said:

                  nothing happend

                  yes, the syntax you used asks to use 24.04-1.x and you are already using it, so it's rather logical that nothing happens.

                  What I said in my thread is that to downgrade you have to use a more specific syntax and I gave you this syntax in my previous post:

                  sudo system-image-cli -b 2 -m 3
                  

                  that is asking the upgrade system to use the build number 2 for the current version - if you are on 24.04-1.3 your current build number is 4 as reported by sudo system-image-cli --list-channels.

                  B 2 Replies Last reply Reply Quote 0
                  • B Offline
                    bunt7 @gpatel-fr
                    last edited by

                    @gpatel-fr Ok, thanks, it worked. Now it is 24.04-1.2

                    1 Reply Last reply Reply Quote 0
                    • B Offline
                      bunt7 @gpatel-fr
                      last edited by

                      @gpatel-fr When I would upgrate to 1.3, will the problem come again? And if yes, in a long terme it would be practicel, to have the newest software.

                      G 1 Reply Last reply Reply Quote 0
                      • G Offline
                        gpatel-fr @bunt7
                        last edited by

                        @bunt7 said:

                        When I would upgrate to 1.3, will the problem come again?

                        Well, has the problem been solved by downgrading ? If yes, give some attention to what I posted before on creating an issue on GitLab to actually provide information to the port maintainer so maybe some investigation and hopefully correction could be done for a future 1.4 release.

                        B 1 Reply Last reply Reply Quote 0
                        • B Offline
                          bunt7 @gpatel-fr
                          last edited by

                          @gpatel-fr Yes, like I wrote before, now it works.
                          Thanks for the info with Gitlab!

                          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