100% Agreed! I’ve provided instructions on how to do each update I did, and provide a script for how to do it when possible, which although isn’t a simple package to install, is a start.
The problem for me was, knowing exactly what people have done when asking for help. Having things done in a ready made image was just easier, and let me know exactly the place where people started experiencing problems.
I could/should package the files into upgradeable packages, but like you said it’s not trivial, and I’d have to start again from scratch, using the 0.5 image as a base.
Maintaining a server to have current updated files for me is a fair bit of work, since it’s not something I usually do. I’d have to learn to do it essentially. If someone could assist in doing so, that would be great! Physically being able to do it for me as opposed to just providing information on how to do it.
I suppose if I ever have to go into quarantine/lockdown I could dedicate time to do it myself. But as it stands now, I’m just doing this as a pet project of my own to help out people.
Anyway, I’ve put up a link for and earlier build 200313, for people who are having troubles with the flickering screen. It’s in the first post of this thread.
I think you’re right. I might start a DEOT v3+ thread soon, instead focussing on being a package based install process, based on a stock 0.5 image. The only thing I wouldn’t be able to change is the first boot screen. But that isn’t the biggest of problems to deal with. Also the next biggest problem is the time it would take. It’s such a big balancing act between convenience and viability.
On another note, @r043v Thanks for the info re: the sun4i_tcon.c file, and the recent changes to the lima driver. I’ll definitely be trying it out. Again though, there’s no way to tell if what I’ve tested will work for everyone. I’m hoping that the flickering is the same thing that you’ve referenced here: [kernel] mainline support evolution
@1115 - Great to know it worked. It’s a Kernel only problem.
The scripts I included with the OS to change the kernel are just the same things you typed to get it working. By invoking them, you have returned the Kernel to the one that causes your screen to flicker. For now, just keep the old 5.3.6 Kernel.
@shell - Thanks for getting back to me. Interesting to know that you’re using a R16-J board. I’m using two R-16 boards, and have no problems. It would have been clear cut if one board had problems and another didn’t. Perhaps it’s to do with some other component of the CPI 3.1 board? I’m curious to know what the image works perfectly fine on some boards, but not others. Hopefully I’ll get a reply from someone.
@Veronica - You mentioned previously that there is no difference between the R16 and R16-J boards. Is there possibly some other difference between batches produced of the clockwork 3.1 board that could be taken into account when compiling a kernel, in order for someone to write one that is more universally compatible? We are currently assuming that every gameshell is made equally.