| piggz[m] | nephros_: running the update-sources script..... | 06:31 |
|---|---|---|
| nephros_ | piggz[m]: cool, I have a couple of PRs on top then :) | 08:30 |
| nephros_ | piggz[m]: Wanna add Pipewire support? ;) | 08:56 |
| piggz[m] | nephros_: happy to, let just make sure stuff builds :) | 09:57 |
| piggz[m] | funny, for qt-base, i apparently submitted a PR for that forkfd thing back in november .... im sure i forget many things ive already done! | 10:02 |
| piggz[m] | nephros_: instead of a bunch of PRs, should i just give you RW on the qt6/kf6 repos for updating .specs ? | 11:37 |
| nephros_ | piggz[m]: Yeah if you dare! hehehe | 11:52 |
| piggz[m] | nephros_: done .. go wild | 11:58 |
| piggz[m] | i see qtbase needs some spec updates due to unpackged files | 11:59 |
| nephros_ | piggz[m]: on it, almost ready: qt6-lts branch, or tag 6.8.3+git2 | 12:43 |
| nephros_ | also, updated the qt macro repo | 12:43 |
| nephros_ | In my testing environment, I try to enable Vulkan backend just for kicks, wrapped in bcond. Do we ant to support that? | 12:45 |
| nephros_ | *want | 12:45 |
| piggz[m] | nephros_: im happy if in main, then tag with VER+gitX | 13:08 |
| nephros_ | fine, will merge and tag once this run compiles. BTW, I'll be offline tonight until monday, will push other stuff later. | 13:16 |
| piggz[m] | great .. whaever you get up to, i will carry on | 13:19 |
| piggz[m] | nephros_: have added you as maintainer to https://build.sailfishos.org/project/users/home:piggz:qt6sb2 | 13:19 |
| tigran | Hello everyone! Has anyone tried running Sailfish OS on a Pixel 9, or is it hopeless? | 18:01 |
| tigran | I asked in sailfishos-porters, but nobody responded there so far | 18:01 |
| piggz[m] | nephros_: why added QT_QML_SKIP_CACHEGEN=true ? | 18:20 |
| attah | tigran: It's not something "you just try and run" like for regular computers. Porting is rather involved. But as far as porting targets go, pixels are supposed to be pretty good. | 18:22 |
| tigran | I'm aware it's a pretty tedious process, I've seen people online discuss porting custom ROMs to various devices and I'm aware it includes stages like compilation and stuff | 18:23 |
| tigran | And I've read Sailfish's porting guide in the past, you needed a Lineage OS base for Android phones, right? | 18:24 |
| tigran | Pixel 9 does have a Lineage OS but I don't know if it'll work because people make ports for the Pixel 3A but for some reason not the newer Pixels, why is that? | 18:24 |
| attah | You need a base of some description. Usually AOSP of some sort, but theoretically mainline Linux too if it exists (it very likely does not). | 18:25 |
| attah | Compilation is a machine task or misnomer for some other part of the process. | 18:25 |
| tigran | Pixel 3A has various ports. It has postmarketOS, it has Ubuntu Touch, not sure if it has a Sailfish OS port too but... | 18:26 |
| tigran | How come they don't make ports for newer Pixels? | 18:26 |
| tigran | Is it just that Pixel 3A is old and lots of people have it as a second phone that still works? | 18:26 |
| attah | Or are you actually asking "how come they are not done instantly?"? | 18:26 |
| tigran | No no no I'm just asking if anyone tried running Sailfish OS on a newer Pixel device like the Pixel 9 | 18:27 |
| tigran | And yeah by running I mean doing what's necessary for it to run | 18:27 |
| attah | SFOS is also like 2 Android versions behind current on what can be somewhat readily used as a base | 18:28 |
| tigran | I think the Pixel 9 launched with Android 14 | 18:28 |
| tigran | and the latest version is Android 16 | 18:28 |
| attah | So hopefully not a blocker | 18:28 |
| attah | Perhaps Pixels are not all that popular with big g being a-holes about Android. Not sure. | 18:31 |
| tigran | I did hear that Google has been making AOSP more restricted recently | 18:35 |
| tigran | And the Pixel 10 had some restrictions too. If I'm not misremembering the bootloader was harder to unlock, and I also heard something about Google not releasing some things that they used to release that were necessary for low-level development with the device | 18:36 |
| tigran | Device trees? Blobs? What were they called again? | 18:37 |
| tigran | Well whatever it was they started doing it since the Pixel 10 | 18:38 |
| tigran | But the Pixel 9 should be ok, right? | 18:38 |
| attah | Details is for actual porters really | 18:38 |
| attah | But asking for SFOS for a phone and not a phone for SFOS is honestly backwards unless you are a porter | 18:39 |
| tigran | Well that's the phone I happen to have..? | 18:39 |
| attah | And porting work is worth magnitudes more than buying another phone | 18:40 |
| tigran | I was just curious if anyone tried it | 18:40 |
| tigran | Well does it involve a risk of making the phone unbootable? | 18:41 |
| attah | And really quite questioning in "why haven't they" | 18:41 |
| attah | Only temporarily for any sane phone | 18:42 |
| tigran | Well yeah there seems to be lots of work done for the Pixel 3A | 18:42 |
| attah | You'd normally have enough left to be able to flash back to Android | 18:42 |
| tigran | And not the newer Pixels | 18:42 |
| tigran | That's why I asked | 18:42 |
| tigran | Is it because there's one person passionately working on that particular device or is it that the device has something special about it that's an attractive choice for any porter? | 18:43 |
| tigran | I don't know that's why I'm asking | 18:43 |
| attah | It would appear it takes a combination of the two | 18:44 |
| attah | Good quality AOSP port and similar enough interfaces to the hardware to what has been done before should be attractive | 18:45 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!