[port-ish]{x86_64} 24.04 daily
-
so i used ubuntu server and ubports pdk and manage to get it up and running using some python
first bed ....sweet sweet bed ...then work ...then hardware testing on a ancient laptop ....this will be a big leap this is a windows tiny 11 core duo 4 gb ram old hdd 80gb? and like it can play doom 3? maybe i was never brave enough to try ...but im going to commit it to ubuntu touch and this is a big deal because i used it for my orange pi 5 sbc flashing as the windows flash tool is best ...but im going to begin porting the ubuntu touch rock chip flash tools as well eventually someday this will make it sooner than later .....this is the same build script im using for my orange pi 5 as well so this is wonderful news on that front but more testing is needed
updated now can fold in system apps still needs more testing still stuck on daily but works will prob pause and come back around to this later
known bugs you will most likely have to reset it once on the first boot at the language selection idk why? ...and many others still need to test opi5 and actual hardware but its a thing
https://drive.google.com/file/d/1psGjDJQ40fcwWYlxNBS_0QZW_Tpne4ZU/view?usp=sharing
-
i need to be clear daily is considered 1.2 correct or am i building the wrong image this whole time?
-
once i get it dialed in ill make the builder script into a clickable also i have a iso writer app once i figure out how to get UT to write raw block devices ....we will be able to build and deploy UT from UT natively
-
but right now something isnt rubbing me right about this currently
-
i need to be clear daily is considered 1.2 correct or am i building the wrong image this whole time?
Daily is 24.04.1.x
There is a 24.04.1.2 stable and a 24.04.1.2 RC. -
y'all wanna mess with this here is the build script im using ...also i think it automatically break UT's immutability i just installed thonny from the terminal like without a hitch ...lol im glad but i actually was not trying for that i think the ubuntu server base file system is the culprit so its not gonna be set read only like UT is supposed to be ...this means many bugs everywhere i need more hands
.....personally i like it ...but i get it some people will be mad at it probablyyou gonna need like 30gb hdd space to build it ...its in python
UT port builder script:
https://drive.google.com/file/d/1psGjDJQ40fcwWYlxNBS_0QZW_Tpne4ZU/view?usp=sharing -
while i want to keep it "normalish" on x86_64 and opi5 or any desktop like experience ....its not my goal despite what i want or my past misgivings on this topic i would better like it if it was immutable as well because if we are not all on the same page it breaks UT's design .....we need to have a discussion about this ....lol i got what i used to want by accident!!!
....although i could probably just set it read only but ill eventually update the script so its a checkbox so its handled in the build process
-
now i understand clickable more i dont really care about it being writable ...with a few hard buts
-
this would be a excellent way to test system apps i thinks at least? ...and convergence
-
im having a NERDGASM!!!!!!!
-
@developerbayman Is this running on a PC with a touchscreen, or are you using a mouse ?
-
@oldbutndy i am using a mouse i do have a touch screen on my opi5 havent tested yet ...also only tested in a VM so far
-
updated also for some reason im having trouble with the different release channels
-
@developerbayman I would say, it depends.
Since your work is based on the PDK image, which itself is a developments tool and does not have a read-only rootfs, it is expected that you would also end up with a writable rootfs.
If you are planning to support OTA updates just like on other UT devices, then making the roots r/o would be a requirement. But until that moment, there isn't really that much benefit in having it configured that way.
🇦🇼 🇳🇱 🇺🇸 🇪🇸
Happily running Ubuntu Touch
JingPad (24.04-1.x daily)
OnePlus Nord N10 5G (24.04-2.x daily)
PinePhone OG (20.04)
Meizu Pro 5 (16.04 DEV) -
@arubislander honestly there was no plan ...umm i just was bored and wondered and asked and then did and did some and lots more ...now its this and i dont know ....so to compound things im making a installer app actually based off the old installer app and i plan on folding it during the disk image creation process so it will be a bootable usb image with a disk installer
-
@arubislander if you downloaded the builder script download it again and maybe a few other times in the future as im updating it as i go along
...may work may break but eventually ill leave it on working -
@arubislander also i do want the "official" style writeable is cool but i want it to follow UT maybe present the writable version as a fork? more like a standard distro? but not as its clickable compatible ...also just gained new respect for clickable i just yank out the whole "arm64" under body bolt on x86 and im running all the apps ....am i missing something? am impressed
-
@developerbayman To be completely honest, half the time I don't know what you're on about
. I just chime in when I see a question I think I can answer. Otherwise, I leave all well enough alone 
-
this is gonna be sweet still refining for a opi5 boot ...i dont expect much gaming in qemu though i couldnt resist trying though everything seems to work still stuck on daily
-
right now the graphics stack is giving me some issues in all this ...i might break on this for a bit and work the opi5 build or a plethora of programs for a bit to avoid burn out
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login