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

    OnePlus 6(T) port

    Scheduled Pinned Locked Moved Oneplus 6/6T
    46 Posts 10 Posters 14.0k Views 6 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.
      • T Offline
        tomoqv @makeixo
        last edited by

        @makeixo The port works surprisingly well. Phone calls work, without echo too! The overall experience is that the device is very fast and smooth. It has its quirks, e.g. that some apps won't work (mostly non arm64 apps I think). Also, the indicators are partially hidden behind the front facing camera and speaker. Picture quality is excellent. Battery drain for me, with cellular and wifi on seems to be 5-7 percent per hour.

        M 1 Reply Last reply Reply Quote 0
        • flohackF Offline
          flohack @tomoqv
          last edited by

          @tomoqv Updates can be made via OTA if:
          a) the device has a working recovery
          b) the device has a community channel and
          c) an installer config file

          Not sure whats the state but it should be pretty forward to do those things πŸ™‚

          My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

          T M 2 Replies Last reply Reply Quote 0
          • T Offline
            tomoqv @flohack
            last edited by

            @Flohack Ok, I am not sure how to check a) and c). I guess there is no community channel yet, but I could be wrong. I'll wait for more info from @mrcyjanek . So far so good, though. Positively surprised I managed to install UBports on the device even though I wasn't able to follow the installation instructions exactly. The OP6 is a really nice device and much snappier than my aging Pro5.

            1 Reply Last reply Reply Quote 0
            • T Offline
              tomoqv
              last edited by

              I thought OP6 was an arm64 device, but when I tried to install futify.frenchutouch_1.0.0_arm64.click it failed while futify.frenchutouch_1.0.0_armhf.click installed at launched fine.

              S 1 Reply Last reply Reply Quote 0
              • S Offline
                stefwe @tomoqv
                last edited by

                @tomoqv it is a arm64 device but maybe the rootfs is armhf? It is possible to mix this😞

                Meizu MX4 16.04 | Nexus 5 16.04

                T 1 Reply Last reply Reply Quote 0
                • T Offline
                  tomoqv @stefwe
                  last edited by

                  @stefwe Hm, could that be changed? Is it up to the dev porting it?

                  1 Reply Last reply Reply Quote 0
                  • M Offline
                    makeixo @tomoqv
                    last edited by

                    @tomoqv Sounds great! I still look for a device, when the day has come and my Xx resigns. I personally would like to support the Vollaphone guys, but the camera has been tested not that good.

                    I wonder if it is possible to create a port with mainline support some day. As far as I know the driver for the Qualcomm 845 series will be added to the linux kernel.

                    1 Reply Last reply Reply Quote 0
                    • T Offline
                      tomoqv
                      last edited by

                      @mrcyjanek I find the built in speaker volume very low. Is this a known issue with this port or is it a hardware problem?

                      1 Reply Last reply Reply Quote 0
                      • T Offline
                        tomoqv
                        last edited by tomoqv

                        @mrcyjanek After a week of enjoying my OP6 with UBports, it started to act up a bit, particularly with wifi and mobile data connection. I usually solved this by doing a complete reboot, but the last few times the phone would only reboot into UBports with screen at max brightness and then shortly after turn itself off. The battery is at over 90% and I am able to boot into fastboot mode, so I thought maybe I should reflash.

                        Some more info: I am able to ssh into the phone, just like before, but the screen remains off.

                        Any suggestions?

                        Thanks

                        1 Reply Last reply Reply Quote 0
                        • M Offline
                          mrcyjanek @flohack
                          last edited by

                          @Flohack said in OnePlus 6(T) port:

                          @tomoqv Updates can be made via OTA if:
                          a) the device has a working recovery
                          b) the device has a community channel and
                          c) an installer config file

                          Not sure whats the state but it should be pretty forward to do those things πŸ™‚

                          We need a) not sure what b) is and we need c), but that should be easy

                          flohackF 1 Reply Last reply Reply Quote 0
                          • M Offline
                            mrcyjanek @tomoqv
                            last edited by

                            To all future flashers, please refer to https://github.com/ubports-oneplus6/documentation with any questions, and join discord in case of problems there are few of us who are working on both halium and mainline version πŸ˜„

                            1 Reply Last reply Reply Quote 1
                            • flohackF Offline
                              flohack @mrcyjanek
                              last edited by flohack

                              @mrcyjanek for b) you need to have your device created on our system-image server:
                              af833df3-fe4d-45f4-b3f1-bcc95d09e9dc-grafik.png
                              Also, that means that our CI has to build your manifest, so that needs a few steps before we can go live.

                              For a) the recovery:
                              Add the following statements to your manifest:

                                  <remote name="beidl" fetch="git://github.com/fredldotme" />
                                  <remote name="rargente" fetch="git://github.com/Rargente" />
                                  <project path="external/gpg" name="android_external_gpg" revision="halium-7.1" remote="beidl" />
                                  <remove-project path="external/toybox" name="android_external_toybox" />
                                  <project path="external/toybox" name="android_external_toybox" revision="halium-7.1" remote="beidl" />
                                  <remove-project path="bootable/recovery" name="android_bootable_recovery" />
                                  <project path="bootable/recovery" name="android_bootable_recovery" remote="rargente" revision="ubp-7.1" />
                              
                                  <remove-project path="system/core" name="Halium/android_system_core" />
                                  <project path="system/core" name="Halium/android_system_core" groups="pdk" remote="hal" revision="halium-7.1-adbroot" />
                              

                              That will modify the recovery build in such a way that have an always unloocked recovery plus the system-image client which will then allow to install updates or to reset to factory defaults etc.

                              After building systemimage there is also recovery.img in the $OUT path, you can take this flash it and try it out πŸ˜‰

                              My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                              M 1 Reply Last reply Reply Quote 1
                              • M Offline
                                mrcyjanek @flohack
                                last edited by

                                @Flohack said in OnePlus 6(T) port:

                                @mrcyjanek for b) you need to have your device created on our system-image server:
                                af833df3-fe4d-45f4-b3f1-bcc95d09e9dc-grafik.png
                                Also, that means that our CI has to build your manifest, so that needs a few steps before we can go live.

                                I'm using generic system image...

                                and my device doesn't have a recovery partition.

                                flohackF 1 Reply Last reply Reply Quote 0
                                • flohackF Offline
                                  flohack @mrcyjanek
                                  last edited by

                                  @mrcyjanek You will still need a channel in our system-image server if you want to provide OTA updates to your users πŸ™‚ - and how does this thing work withour recovery then?

                                  My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                  M 1 Reply Last reply Reply Quote 0
                                  • M Offline
                                    mrcyjanek @flohack
                                    last edited by

                                    @Flohack I have no idea, probably it does some things with initramfs or process it at boot time, now when I want to boot to twrp I'm using fastboot boot twrp.img command and I didn't try installing it on UT kernel because that would probably break it.

                                    1 Reply Last reply Reply Quote 0
                                    • flohackF Offline
                                      flohack
                                      last edited by

                                      @mrcyjanek Can you plz send me the output of sudo cat /var/lib/lxc/android/rootfs/fstab.* <= you need to find the correct name for it...

                                      My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                      S 2 Replies Last reply Reply Quote 0
                                      • S Offline
                                        SevralTi @flohack
                                        last edited by

                                        @Flohack But on A/B devices, really no recovery partition! Recovery stored on boot partition.

                                        1 Reply Last reply Reply Quote 0
                                        • S Offline
                                          SevralTi
                                          last edited by

                                          YES! Now our device on "devices.ubuntu-touch.io"

                                          1 Reply Last reply Reply Quote 2
                                          • S Offline
                                            SevralTi @flohack
                                            last edited by

                                            @Flohack We need to install recovery in boot image. We need a script for unpack, patch kernel and repack.

                                            flohackF 1 Reply Last reply Reply Quote 0
                                            • flohackF Offline
                                              flohack @SevralTi
                                              last edited by

                                              @SevralTi Sorry I am n ot into Halium 9 porting (yet) I cant help with that.

                                              My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                              S 1 Reply Last reply Reply Quote 0
                                              • First post
                                                Last post