These are all different issues so I think they should all be different tickets.

Finally, the biggest issue of them all:

1. We need some hardware that will run "acceptably" with the fedora kernel.

of course the other items would be good to fix for using in the remix, but before official images we should have some kind of target.

These are all different issues so I think they should all be different tickets.

It is not that I do disagree here - but since a fix is needed for all points, before we can restart making Phosh images, I thought it was ok in one ticket.

Finally, the biggest issue of them all:

1. We need some hardware that will run "acceptably" with the fedora kernel.

of course the other items would be good to fix for using in the remix, but before official images we should have some kind of target.

Well, we actually do have that - actually a lot I would think. There are a lot of X86 tablets and AIO's around. I have myself 2 older AIO's that works OOTB with Phosh.

With kernel 6.10 we skould have a new driver for Wifi for PinePhone and PineTab1

We should also now have the displaydriver in for PineTab2. WiFi however doesn't work, requires more or less a rewritten driver. It s however easy to just plugin any USB WiFi dongle, to get it working.

That said, it is ofc a lot easier to get tablet working because of the bigger screen; but since Phosh by definition is for Phones - we need to insure that we have an initial-setup system that works on that form-factor too.

I just tested PineTab2 with todays nightly rawhide image (Plasma-raw).
As I did have latest rk2aw firmware on SPI - it booted straight up - no problems.
( as known internal WiFi have no driver ) but an added USB WiFi works.

I should have added: PineTab2 is available for sale, so it is current HW.
It is for sure very low-end. It runs rather slow on Plasma 6 -
but I think Phosh will be much faster :-)

Thats great news... although yeah, as you mention its going to be slow, and it's not a phone form factor, so phone functionality isn't going to be testable. (modem, etc).

I'm not sure if thats enough of a target to make it worth making official images again for, but I suppose it could be.

We can still test with PP and PPP - both should "work" with Fedora kernels - just with some limitations.
Our Remix is directly based off the Phosh image - besides the different kernel we just add some more packages. Some of them we really should just include in the official Phosh image.
Besides - start making x86 images too - and I'm sure a lot more ppl will start to test it on different devices and virts.

That said ....

1: getting the identity fixed should only be a 1 line patch (PR) to kickstarts.

2: @samcday is currently working hard to make phrog (Phosh-based greeter working with greetd - and we should be able to get that into fedora repos soon. That will be a great replacement for GDM

3: I still have no idea about initial-setup. There exists OSK's out there that works in terminal - which could be ported/packaged to work with the tui setup version - other ideas still welcome

Sure, I have 2 pp's and 1 ppp here. Last I tried (all be it a while back), neither one booted from the fedora image. Or one might have booted and then not lit up the display, I can't recall.

The pinephone is... painfully slow. The pinephone pro isn't much better and also has horrible battery life. I just want to avoid what we had in f39... people showing up and saying: "Hi, I have this samsung phone, how do I run it?" or worse "I have this pinephone pro, how do I use it" as well as needing some hardware we can actually test with to show it works instead of just tossing it out there in hopes...

Yes, I know all about the remix. :)

On initial setup, most of the other arm devices skip running it and user/root is setup via arm-image-installer. So, perhaps we could expand arm-image-installer? but many folks will just dd it and so some better solution would be good.

We probably should just expand arm-image-installer for now to do preconfiguration.