y'all need focal for FP2?

there

Pardon my intrusion. Just a few questions. Is the port you are showing/using/building usable? Can you describe what works and what not? Is there a way I (or anyone else with FP2) can test the product of your effort?

Thanks.

@Opolork said in Is Ubuntu Touch OTA-2 Focal incompatible with the Fairphone 2?:

How would I disable SSH?

That depends. On most devices, if not all, it should be disabled by default. Certain devices have it enabled when you enable Developer Mode in the settings. So disabling developer mode should see ssh disabled on the next reboot.

One way to check if ssh is enabled on your device is to open the terminal app and type:

ssh localhost

If you get a result saying ssh: connect to host localhost port 22: Connection refused, then the service is disabled.

That's a handy tip. :thumbs_up_light_skin_tone:

@Opolork You can use UT TT : System / SSH parameters.
It seems for me SSH is reactivated at every start of my Volla. To be checked.

Cheers. It was already off,

How would I disable SSH?

That depends. On most devices, if not all, it should be disabled by default. Certain devices have it enabled when you enable Developer Mode in the settings. So disabling developer mode should see ssh disabled on the next reboot.

One way to check if ssh is enabled on your device is to open the terminal app and type:

ssh localhost

If you get a result saying ssh: connect to host localhost port 22: Connection refused, then the service is disabled.

disable ssh on your device

Thanks for the advice/info.

How would I disable SSH?

So effectively, I'm using an unsecure OS on my FP2?

No, you are using an unsupported OS. That does not mean it is insecure. It does mean it will not get any more security updates.
But not all vulnerabilities are equally exploitable. Also, UT's read-only file system and confined application runtime environment go a long way into protecting you additionally. Add to that fact that there are no services running on the device out-of-the box that can be connected to remotely (if you are concerned with security, you should disable ssh on your device, even if on a supported OS), then I would say, realistically, you are probably as safe as you would be on 20.04.

The main reason to stop using 16.04 would be lack of support for newer apps. But we haven't quite gotten there as yet.

Damn.

So effectively, I'm using an unsecure OS on my FP2?

You mean you are actually doing the port ?
This image is... You adapting the kernel ?

Edit : https://forums.ubports.com/topic/8386/no-new-stuff-for-xenial-but-what-about-old-new-stuff/12?_=1691470274847

what makes Pinephones hard to port is because their ports are not built on halium

What makes the Pinephones hard to port was mostly the lack of drivers for the hardware. As the hardware becomes better supported, then the port works better, see Focal on RPi 4, for instance. If drivers would be mainlined, then it would not be necessary to use Halium to communicate with them.

My point however, is that even such support is not 'free'. If a piece of hardware is not widely used, maintenance for it could potentially still fall on the shoulder of a team of one. And unless support is financed by the hardware vendor, that one could become none at any time unexpectedly.

but I am not sure what advantage it brings to continue using Halium

Like you said yourself, porting UT to pinephone is an uncharted challenge, still ongoing for years, whereas porting in the halium way is a known territory.

Some relevant posts from the FP Forums

Yes, I gave link to this topic in my previous post ^^

And as you can read from the FF employee that work on mainlining FP4, it'll help to maintain android rom on it also, so as one Fairphone goal is to make their device last the longer possible, we can hope the soon to be released Fairphone 5 not to kill mainlining effort for the 4.

Anyway, let's hope the port for Pinephone reach a 100% state and then it can be adapted quickly for any mainlined kernel android device, making halium irrelevant for those.

Some relevant posts from the FP Forums:
https://forum.fairphone.com/t/official-mainline-kernel-support-for-fp4-planned/76741/10
https://forum.fairphone.com/t/official-mainline-kernel-support-for-fp4-planned/76741/19

Also note that mainlining drivers for the latest FP device is a multi year effort, and is being done part-time. Chances are good that it will not be completed before a new device is released, and then attention might shift to that device instead (as you see, another game of catch-up).

Does that necessarily also mean you can't no longer use the halium way if Fairphone release some FPOS including this mainlined linux kernel ?

Also, as I understood what makes Pinephones hard to port is because their ports are not built on halium, unlike any android device mainlined or not.

The whole point of a mainlined Android device would be exactly that Halium would no longer be needed, presenting it with the similar challenges as the Pine64 devices and RPi's, which are mainline devices.

But not an insurmountable one, as has been shown in the effort to bring Focal the OP1

Yes, like said in the link I gave in a previous post here, it is possible to bring focal to android 9 devices with a huge work.
By the way, kernel is 3.4.113 on both OPO and FP2.

Anyway, with the "good" kernel, it's simpler.

Let's hope someone step on for doing this huge amount of work for the sake of FP2 UT users.

Also, as I understood what makes Pinephones hard to port is because their ports are not built on halium, unlike any android device mainlined kernel or not.

My point is the FP4, wich is a promoted device, will, if mainlined, not suffer end of support due to deprecated kernel, like majority of the Xenial ones are suffuring now.

The old kernels in the Android devices are a challenge, for sure. But not an insurmountable one, as has been shown in the effort to bring Focal the OP1. Sure it is a whole lot of work (a HUGE thank you to @TheVancedGamer for undertaking it!!), but what is slowing the effort the most is contributors, not kernel version.

Continued support also is not necessarily easier for mainlined, as development on the PinePhone has shown. Newer kernels also introduce new bugs. Support for older or less common hardware deteriorates or gets dropped.

As newer Fairphone models are introduced, hopefully also with UT support, choices will have to be made if, and how long, the limited resources will continue to be allocated to older models, mainlined or not.
The only way continued support for any device can be guaranteed is a large enough maintainer base.