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

danfro

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

Because of that, i.e. the usb-config is more generic and does not allow to distinguish between OP5 and OP5T.

Btw. would a label like "OnePlus 5/5T" be possible to show that it could be either one?

Luksus

@danfro should be possible.

Luksus

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

Btw. would a label like "OnePlus 5/5T" be possible to show that it could be either one?

Its updated now. (you would need to reflash system image with the latest pipeline build)

danfro

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

Luksus

@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

danfro

@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

danfro

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.

Luksus

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.

danfro

@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: )

danfro

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.

Luksus

@danfro great, that it works for you. The sim card issue is probably the next thing, I will have a look at.

danfro

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

vince.vs

@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

danfro

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.

Luksus

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

danfro

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

Luksus

@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

danfro

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

danfro

@Luksus would you mind triggering a new build? Some changes during the last couple of weeks may be interesting to test (haptics, log reduction).

Luksus

@danfro new build is running.