OnePlus 6(T) port

tomoqv · 22 Jul 2020, 16:38

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.

stefwe · 22 Jul 2020, 18:34

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

tomoqv · 22 Jul 2020, 19:19

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

makeixo · 22 Jul 2020, 21:13

@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.

tomoqv · 23 Jul 2020, 10:29

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

tomoqv · 30 Jul 2020, 11:01

@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

mrcyjanek · 2 Aug 2020, 09:20

@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

mrcyjanek · 2 Aug 2020, 09:24

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

flohack · 8 Feb 2020, 09:34

@mrcyjanek for b) you need to have your device created on our system-image server:

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

mrcyjanek · 2 Aug 2020, 09:38

@Flohack said in OnePlus 6(T) port:

@mrcyjanek for b) you need to have your device created on our system-image server:

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.

flohack · 2 Aug 2020, 20:30

@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?

mrcyjanek · 2 Aug 2020, 21:40

@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.

flohack · 3 Aug 2020, 08:45

@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...

SevralTi · 20 Aug 2020, 13:25

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

SevralTi · 20 Aug 2020, 13:35

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

SevralTi · 24 Aug 2020, 08:12

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

flohack · 24 Aug 2020, 08:27

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

SevralTi · 24 Aug 2020, 08:28

@Flohack Yes! A/B it's relly problem... Without recovery.

sparkster666 · 21 Sept 2020, 22:22

I just got this up and running seems to run great. The one problem I am having is it will not sleep. I can use the power button and i get the power menu but if i click it fast the screen stays on and it never goes to sleep on its own. Is there somthing i missed or is this a known issue? Any work around.

flohack · 22 Sept 2020, 09:59

@sparkster666 That means that Lomiri thinks this is a desktop. A proper configuration file injected into the build should fix this.