Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image)
-
@Luksus said in Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image):
Thanks for the detailed feedback.
As I tried to explain, the kernel and kernel features itself should be the same as in the official image... the difference is the system-image and how device-overlays are getting applied.Because of that, i.e. the usb-config is more generic and does not allow to distinguish between OP5 and OP5T.
Just my hope that some things get magically solved so I mentioned or tested those things.
@danfro said in Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image):
after applying the battery saver patch and rebooting, the "one sim card is not detected" issue came up again at a 50:50 rate. Can that be related?Maybe, since it is modifying sim cards mobile data config.
I turned the script off later to see if the sim card detection then works again. No. But I also have the impression, that it works good after doing some larger (kernel?) updates/OTA or flashing a kernel manually as here. As soon as I change or update something or whatever things go bad again. I guess I could only test this by flashing the whole thing again.
@danfro said in Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image):
can this patch be amended so it also turns to 2G when wifi is on (even with the screen on)?Sure. I have that on my mind too for a while, but did not find the time to look into it.
Maybe there is already an attempt somewhere in this thread:
https://forums.ubports.com/post/51164Quickly zapping over the post I couldn't see anything regarding wifi. I may give it a more detailed read later. But battery safer app has this already implemented, which I was using. I turned that off for testing this kernel.
@danfro said in Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image):
And one last question: I should not do any devel/RC/OTA updates right now since that would overwrite this kernel, right?Yes, kind of.
I am not sure, if it would replace the kernel, but it would at least switch to the official system build again.
I will not update then for a while and see how this version works. -
Just some preliminary report:
- I got the same error message as @danfro "invalid sparse file format.." but everything was OK and it flashed fine
- the keyboard is smaller??
- I've had a bug where I could not write anything and I had to reboot
- snaps after the space "hack" finally works again
- I can confirm the kernel config BINFMT_MISC is not set as you mentioned, but not biggie since winebox never really worked for me on this device.
I will apply now the battery saver ""patch"" and see if I notice some improvements. I will continue testing and report any findings.
-
@malditobastardo Oh yes, I forgot to mention that:
I've did some adjustments (improvements in my opinion) to the keyboard, that it fits better the display height. Mainly for the landscape mode, but then I found, that it could use an adjustment in portrait mode too.And I made the font smaller in the the "word-ribbon" (the line above the keyboard, with suggestions or the options to copy and paste when in editing mode).
If you want you can switch it forth an back to compare. It would be needed to make system writable and then edit the file
/opt/halium-overlay/usr/share/maliit/plugins/lomiri-keyboard/keys/key_constants.jsThe original parts are commented:
/* overlay-adjusted */
See: maliit key_constants.js overlay
"invalid sparse file format.."
I have that too, but I don't think its relevant, though I just don't know.
I still wonder, if virtualization (pocketVMs) is working for you?
Do you have any kernel-adjustments for making it work? Which images are you using? -
@Luksus Hello everyone,
After testing this on my OP5 for the past 2 days and experiencing issues with the battery life (it only lasts for 2-3 hours with minimum use), I've decided to rollback to the stable kernel by using the updater (updating from the phone using the channels didn't work).
I will continue running more tests to try to see if this is an isolated case or not. -
@malditobastardo thanks forums testing.
I wonder, if maybe your CPU is not clocking down, or something like that. I will check the device tree of the OP5, if there are differences to the OP5t in this regard.
-
@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?
-
@danfro should be possible.
-
@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)
-
@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 failedIs that because of the resized partition?
-
@danfro I don't know, why that happens. But I remember this from FP3 in the early porting days...
Tryfastboot -S 300M flash system ubuntu.img -
@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 -
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.
-
D danfro referenced this topic on
-
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/pipelinesI 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. -
@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? 
) -
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.
-
@danfro great, that it works for you. The sim card issue is probably the next thing, I will have a look at.
-
@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.
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 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 -
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. -
@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.
