<![CDATA[Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image)]]>Hi,

I've created a new build for the Oneplus5/T, which is based on the nowadays for android9+ devices recommended build method (Standalone kernel method).
I am running it myself for some months now and also just fixed the last issue, the not working fingerprint, that I think it's time to let it test by you owners for regressions, compared to the current full-system-image version.

Why a new build method at all, since the current build is working fine?

  1. Reduce CI-load
    The full-system-image method is very "ressource-hungry". For every device with full-system-image, our jenkins-CI needs to build a (devel) build every day. For the OP5/T it takes about 7 minutes. That doesn't sound much, but the build-server seems to be very powerful, since a system-image build on my local machine takes about half an hour (Ryzen 5700U Processor). Also, these CI-Pipelines need to be maintained by someone.
    So, for the standalone-kernel-method, the CI only needs to build one generic_arm64 image (for every Halium version), which will be used by many devices, and the build of that image only takes about 2 minutes.

  2. Better maintainability
    The kernel-standalone-method in combination with the generic halium image is more future-proof, regarding maintainability, and also new features or system-upgrades. The general needed updates for newer Halium-versions are centralized and the same for every device.
    A device maintainer only needs to take care for the kernel and the relatively small device-config tree with device-specific overlays.

Other improvements of the new build
  1. It already contains the fix for the microphone not working after a call. It survives system-image upgrades.
  2. It contains an initially disabled user-service, that, when enabled, is switching mobile-data to 2G when the screen is off, to save battery.
    You can activate it by executing in the terminal on the phone: systemctl --user enable lte-battery-saver.service
    It will be started on next boot or you start it manually by executing: systemctl --user start lte-battery-saver.service.
    It survives system-image upgrades.
  3. For device-specific needed system-changes, it is using the overlaystore method. Compared to the current method, it is more reliable when doing system-upgrades. The overlays of the current build, may be overwritten by an OTA update, which can lead to device not booting and you would need to use the ubports-installer to reinstall the system-image. With the overlaystore method, such things should not happen.
Flashing and Testing

You can just flash the boot and system image with fastboot, without loosing any data.
At least flashing the system image should be enough, since we are using the same kernel source for both build-methods.

HINT
For me, my local distributions fastboot version does not work for flashing the system image. Therefor I am using mfastboot, a motorola implementation, which works for me.

Get the latest images here:
https://gitlab.com/ubports/porting/community-ports/android9/oneplus-5/oneplus-cheeseburger-dumpling/-/jobs/artifacts/master/download?job=devel-flashable-focal

Extract it, boot the device in bootloader mode, connect it to your pc and flash the ubuntu.img to system partition: fastboot flash system ubuntu.img.
Then reboot.

Snaps

The rootfs/system-image size of the OP5/T is very limited. That's why it is hard to install anything additional on the rootfs, for example the snap-dependencies.
But it is possible to expand it a little bit. For that:

  • reboot to recovery
  • connect through adb
  • execute: e2fsck -f /dev/block/by-name/system
  • execute: resize2fs /dev/block/by-name/system
    Output should be something like:
    Resizing the filesystem on /dev/block/sde21 to 786432 (4k) blocks.
The filesystem on /dev/block/sde21 is now 786432 (4k) blocks long.
  • reboot

Now it should be possible to install snap-dependencies, using the app Snapz0r.

Finally

Please share your experience here.
Especially, I am interested in feedback for the OnePlus5 (without T), since I don't have this device to test it myself.

]]>https://forums.ubports.com/topic/9864/call-for-testing-a-the-new-build-variant-standalone-kernel-method-vs-full-system-imageRSS for NodeSat, 14 Mar 2026 05:13:55 GMTTue, 20 Feb 2024 10:40:41 GMT60<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Thu, 17 Oct 2024 11:34:47 GMT]]>@Luksus thanks for already testing that. I am more curious than in need, so no rush.

Also I just saw the build I am using is from July, but pipelines have newer ones available. I will give them a try.

]]>https://forums.ubports.com/post/82727https://forums.ubports.com/post/82727Thu, 17 Oct 2024 11:34:47 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Thu, 17 Oct 2024 09:31:14 GMT]]>@danfro I already did some tests with FP3 and OP5T and on both, something seems to be missing still, for VoLTE to work.
So I would just wait for now, until someone comes up with a solution for devices, which are not the FP5.
I know that it is not working on the P3A too, but work is going on to get that fixed.

]]>https://forums.ubports.com/post/82722https://forums.ubports.com/post/82722Thu, 17 Oct 2024 09:31:14 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Thu, 17 Oct 2024 05:27:55 GMT]]>@Luksus there have been lots of merges regarding ofono and stuff recently to prepare for VoLTE, so might be worth testing a new build with latest devel code and see if that helps?

Also would VoLTE work on OP5T? Could we test that?

]]>https://forums.ubports.com/post/82718https://forums.ubports.com/post/82718Thu, 17 Oct 2024 05:27:55 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Fri, 07 Jun 2024 23:48:38 GMT]]>@danfro Hm, OK. Then I wonder what changed on my device... But the logs would be interesting.

]]>https://forums.ubports.com/post/80558https://forums.ubports.com/post/80558Fri, 07 Jun 2024 23:48:38 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Fri, 07 Jun 2024 20:16:32 GMT]]>@Luksus It definitely seems to work much better (=more often), but right now when testing, one of my sim cards didn't get detected.
And here they still come up in the wrong order, every time. The first sim also generally takes longer to find the network. Maybe related to that?

I did grab some journalctl logs from this boot where it failed and the last one where it worked. In case this may help.

]]>https://forums.ubports.com/post/80552https://forums.ubports.com/post/80552Fri, 07 Jun 2024 20:16:32 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Fri, 07 Jun 2024 08:25:56 GMT]]>@danfro btw. the led-light-fix is now merged into the master branch.

Regarding the second SIM-card:
I did not have any issues in the last weeks. It was always detected at boot and meanwhile even the order of unlocking the SIM1 and SIM2 is correct.

So the system itself seems to have improved and it seems that the previous issues were not device specific.

]]>https://forums.ubports.com/post/80542https://forums.ubports.com/post/80542Fri, 07 Jun 2024 08:25:56 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Sun, 02 Jun 2024 19:26:58 GMT]]>@Luksus Great, thanks a lot. 👍

]]>https://forums.ubports.com/post/80454https://forums.ubports.com/post/80454Sun, 02 Jun 2024 19:26:58 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Sun, 02 Jun 2024 19:13:36 GMT]]>@danfro new build is running.

]]>https://forums.ubports.com/post/80453https://forums.ubports.com/post/80453Sun, 02 Jun 2024 19:13:36 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Sun, 02 Jun 2024 18:41:59 GMT]]>@Luksus would you mind triggering a new build? Some changes during the last couple of weeks may be interesting to test (haptics, log reduction).

]]>https://forums.ubports.com/post/80452https://forums.ubports.com/post/80452Sun, 02 Jun 2024 18:41:59 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Thu, 04 Apr 2024 21:04:18 GMT]]>@Luksus Great, thanks a lot. I missed the fact, that tjis kernel also includes "everything" from devel.

Yes there should be a fix included regarding building of core apps which I would like to see on my device.

]]>https://forums.ubports.com/post/79578https://forums.ubports.com/post/79578Thu, 04 Apr 2024 21:04:18 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Thu, 04 Apr 2024 21:00:42 GMT]]>@danfro if you want a more current devel with this build-variant, I can just trigger a new build.
Otherwise, if you flash the old ubuntu.img again over the updated devel, you will have the old devel again.

I just started a new build, you can download it here, when it is finished:
https://gitlab.com/ubports/porting/community-ports/android9/oneplus-5/oneplus-cheeseburger-dumpling/-/jobs/6552410058

]]>https://forums.ubports.com/post/79577https://forums.ubports.com/post/79577Thu, 04 Apr 2024 21:00:42 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Thu, 04 Apr 2024 19:51:15 GMT]]>@Luksus Thanks for the answer. So nothing in short time and still with some open question marks. That's life. 😉

I just wanted to find out for myself how to proceed with this kernel and "normal" devel updates. I can update devel and flash this kernel again then occasionally. No trouble.

It is good to have you and Jami doing some work and improving things. I really like the battery safer feature and its nice to have the led back.

]]>https://forums.ubports.com/post/79576https://forums.ubports.com/post/79576Thu, 04 Apr 2024 19:51:15 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Thu, 04 Apr 2024 19:38:32 GMT]]>@danfro not really.
I would like to merge a proper fix for the hfd-service-delay and then, we could theoretically do through transition.
But I don't know yet, how the transition could be achieved.
And I heard, Jami is experimenting with a halium 10 build, so I would ask him first how far he has come and if it is an option to maybe switch to halium 10 at all.

]]>https://forums.ubports.com/post/79575https://forums.ubports.com/post/79575Thu, 04 Apr 2024 19:38:32 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Thu, 04 Apr 2024 10:43:27 GMT]]>Btw. is there any timeline/plan yet, if/when this kernel might become offically released?
I suppose features and fixes can be added rolling releasing later as they get done.

]]>https://forums.ubports.com/post/79561https://forums.ubports.com/post/79561Thu, 04 Apr 2024 10:43:27 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Tue, 26 Mar 2024 00:37:05 GMT]]>@danfro

@vince-vs said in Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image):

I know @vince-vs would love to see the LED fixed. 😉 (Would you also dare to flash a kernel to get the led working?

Hello,
Very true, but I think it will make many more people happy than I am, and if the LED flashes again after incoming missed calls, just like it does when the battery is full after charging, it will be Top again.
What's more, you had written to me that the new kernel could solve the problem of the camera sound after recording, ...so, for me, what more could I ask for, except that the project continues in this way towards the path of fluidity for its operating system....
Many thanks to you

]]>https://forums.ubports.com/post/79419https://forums.ubports.com/post/79419Tue, 26 Mar 2024 00:37:05 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Thu, 21 Mar 2024 20:27:11 GMT]]>@Luksus said in Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image):

The sim card issue is probably the next thing, I will have a look at.

Oh, that would be great. :smiling_face_with_heart-eyes:

Although I suspect this not going to be easy (it never is 😉 ), since also other devices are affected. In Volla group someone mentioned, that mainly O2 and derived services are causing trouble.

If you need any logs or testing regarding that please let me know.

]]>https://forums.ubports.com/post/79353https://forums.ubports.com/post/79353Thu, 21 Mar 2024 20:27:11 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Wed, 20 Mar 2024 23:14:53 GMT]]>@danfro great, that it works for you. The sim card issue is probably the next thing, I will have a look at.

]]>https://forums.ubports.com/post/79336https://forums.ubports.com/post/79336Wed, 20 Mar 2024 23:14:53 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Wed, 20 Mar 2024 21:58:17 GMT]]>I wonder if my sim card detection issue is also a delay thing. 🤔

Sometimes only one sim gets detected. Sometimes both get detected, but the second sim first and the first sim last and in very very few cases both sims in the right order. The first two cases sadly result in the device "forgetting" which sim was set for mobile data, so I need to set it back to sim 1 manually after ever reboot.

]]>https://forums.ubports.com/post/79335https://forums.ubports.com/post/79335Wed, 20 Mar 2024 21:58:17 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Wed, 20 Mar 2024 21:54:38 GMT]]>@Luksus said in Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image):

I have a fix for the notification LED, you can test it with build here:

Oh, great! Just flashed that image. LED worked after the reboot. I will test this further.

I know @vince-vs would love to see the LED fixed. 😉 (Would you also dare to flash a kernel to get the led working? :smiling_face_with_halo: )

]]>https://forums.ubports.com/post/79334https://forums.ubports.com/post/79334Wed, 20 Mar 2024 21:54:38 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Wed, 20 Mar 2024 09:37:25 GMT]]>I have a fix for the notification LED, you can test it with build here:
https://gitlab.com/ubports/porting/community-ports/android9/oneplus-5/oneplus-cheeseburger-dumpling/-/commit/76220f525846ad2f6fa7c6fb63f861912ad576e5/pipelines

I am not sure yet, if this fix will be the final solution.
Maybe Jami has an idea, how to make it better, based on my description in the merge request.

]]>https://forums.ubports.com/post/79327https://forums.ubports.com/post/79327Wed, 20 Mar 2024 09:37:25 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Tue, 05 Mar 2024 19:13:49 GMT]]>Btw. after flashing the kernel, my led works for notifications and charging. Also my sim cards get detected.

As soon as I make my device r/w or apply any other change or an update that is not a full flash, this functionality breaks. No idea why though...

Edit: Nope, did not work this time. A shame. I wish we could reproduce better why led and sim detection work sometimes to at least get an idea where to start fixing this.

]]>https://forums.ubports.com/post/78994https://forums.ubports.com/post/78994Tue, 05 Mar 2024 19:13:49 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Sat, 02 Mar 2024 17:11:49 GMT]]>@Luksus Thanks, looks like that has worked. The label is now shown as suggested above. 👍

The log does show different size numbers than on my initial install of this kernel as shown above.

$ fastboot -S 300M flash system ubuntu.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/9 (300225 KB)            OKAY [ 12.544s]
Writing 'system'                                   OKAY [  0.005s]
Sending sparse 'system' 2/9 (301241 KB)            OKAY [ 15.055s]
Writing 'system'                                   OKAY [  0.009s]
Sending sparse 'system' 3/9 (298985 KB)            OKAY [ 14.681s]
Writing 'system'                                   OKAY [  0.005s]
Sending sparse 'system' 4/9 (302652 KB)            OKAY [ 14.525s]
Writing 'system'                                   OKAY [  0.009s]
Sending sparse 'system' 5/9 (281309 KB)            OKAY [ 13.530s]
Writing 'system'                                   OKAY [  0.007s]
Sending sparse 'system' 6/9 (307196 KB)            OKAY [ 16.153s]
Writing 'system'                                   OKAY [  0.011s]
Sending sparse 'system' 7/9 (293496 KB)            OKAY [ 14.079s]
Writing 'system'                                   OKAY [  0.009s]
Sending sparse 'system' 8/9 (294882 KB)            OKAY [ 14.181s]
Writing 'system'                                   OKAY [  0.007s]
Sending sparse 'system' 9/9 (246952 KB)            OKAY [ 12.233s]
Writing 'system'                                   OKAY [  0.006s]
Finished. Total time: 135.474s
]]>https://forums.ubports.com/post/78938https://forums.ubports.com/post/78938Sat, 02 Mar 2024 17:11:49 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Fri, 01 Mar 2024 22:14:00 GMT]]>@danfro I don't know, why that happens. But I remember this from FP3 in the early porting days...
Try fastboot -S 300M flash system ubuntu.img

]]>https://forums.ubports.com/post/78912https://forums.ubports.com/post/78912Fri, 01 Mar 2024 22:14:00 GMT<![CDATA[Reply to Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image) on Fri, 01 Mar 2024 20:53:26 GMT]]>@Luksus Great, thanks for adding that.

But when I try to flash the new ubuntu.img, I get the error message:

$ fastboot flash system ubuntu.img
Sending 'system' (2867200 KB)                      FAILED (remote: 'Requested download size is more than max allowed
')
fastboot: error: Command failed

Is that because of the resized partition?

]]>https://forums.ubports.com/post/78911https://forums.ubports.com/post/78911Fri, 01 Mar 2024 20:53:26 GMT