@qnx_guy
That kind of support is in the hands of porters.
You should open a feature request issue on device GitLab :
https://gitlab.com/ubports/porting/community-ports/android11/fxtec-pro1x/fxtec-pro1x/-/issues

@kristatos
I think he talks about read only system files.

@Opino said in Need testers Home Screen for Ubuntu Touch:

Thank you @pavelprosto for this app.

Yes he did good work.
Sadly we don't have any news about him for a long time now.
As he is russian i wish he is in a safe place.

@Lakotaubp
That would not be a problem for average users to reinstall if it was possible to save user data easily, using the installer for instance.

Merry Christmas @all !

@danfro
My question is to know if that new "week dev thread" is about only noble (24.04), or whole OS subjects (fonctionnalities for instance), or any dev subjects related to UT (like new devices from core team).

@danfro said in This week in development (week 52 2024):

Its about a Noble based version of Ubuntu Touch (the OS).

I meant "about 24.04 version of the OS, or the OS in general".
You answered.

@mariogrip said in This week in development (week 52 2024):

I'd like to start posting weekly development updates here on the forums - this is a bit of an experiment, so please let me know if you find these updates useful and what could be improved. The goal is to provide a high-level overview of our development progress.

Is this is only about 24.04 or OS (see my signature to have a clue of my wonder ^^ ) ?
And yes, I bet it will interest lot of people whatever the subject is.

@manoiese
As @AppLee said you don't sound rude, just honest.
But what you don't understand is that Ubuntu Touch is like that since the beginning, Canonical made it that way (read only in first) and users like me that adopted it since that time don't need a phone system with full access all the time.

Like already said if you want you can make it full read/write in a persistent way.
Or like you experimented, temporarily untill next reboot.

That can be useful, but for normal users for whom the system is designed, again, since the beginning, it is not mandatory or a normal use case.

If you want to continue with Ubuntu Touch on a normal way, you should consider trying to achieve what you want/need in respect with this particular behaviour of the system, like some Devs already did with crackle or things like that, I'm sure this would be a welcomed contribution.

Or maybe, like said @AppLee also, Ubuntu Touch is not what you need.

@manoiese
Did you read my message above ?
You CAN make the system r/w.
Now if you want that the Devs change Ubuntu Touch just for you that will not happen.
You're not the first to ask, you'll probably not be the last disappointed.

And no, android is not what "common" people using Ubuntu Touch want.

@manoiese said in Libertine on Ubuntu Touch: Poor Performance and Issues with "Read-Only" File System:

Even after attempting to remount it as read-write (rw), the system continues to revert to a read-only state after rebooting, making any changes temporary at best.

First, the read-only file system is by design for important reasons. UT is designed for "normal users" before all.
Second, for Devs like you, it is possible to make it r/w in a persistent way, I don't remember the command line, but you can do it using Ubuntu Touch Tweak Tool app anyway.

@moaner said in Oneplus Nord N100 boot failure:

so your boyfriend's abruptness seemed a bit like a tone problem

You felt "bossed" and that was not my intention. I apologised but that's not enough for you ?
So you think you have the right to call Moem, that know me and my intentions better here because she is part of the community for much more time than you, with names ?
You're not on X here.
You're on a European forum for a worldwide open-source project with open-minded people from Earth.

@moaner said in Oneplus Nord N100 boot failure:

why are you being bossy

I'm not.
Sorry you feel that way.
I intended to be clear.

@moaner said in Oneplus Nord N100 boot failure:

I tried locking it to get rid of the nag screen but it wouldnt then boot at all, saying something was corrupt.

You must NOT in any case relock the bootloader after installing UT on any device...

@paulcarroty
Don't forget to quote the "edit 3" please...

Edit3 after 6 months: IF YOU DO THIS, YOU MAY END UP WITH A BROKEN BATTERY CABLE! I had to replace my screen and after that my battery cable broke. I had to solder regular wire on its place.

I no longer recommend doing this!

@Antares86
What do you mean by latest ?
Most recent phone ported or most recent port whatever phone release date ?

Anyway take a look here for UT 20.04 devices : https://devices.ubuntu-touch.io/
One of the latest device is Fairphone 4 (Fairphone 5 incoming), ones of the latest ported devices are OnePlus N100/N10 5G.

@domubpkm
And we all hope for this to become a core app, or better, a part of system/call app settings

@AppLee
He is not mistaking, see there :

https://forums.ubports.com/topic/10484/qualcomm-volte-call-for-testing/25?_=1733537347588

Well, he is mistaking because he tries to install VoLTE on the wrong device, but installing it on the good one, Fairphone 5, needs installing via apt.

@vince-vs
Did you try with another USB cable ?

@vince-vs
Check with Ubuntu Touch Tweak Tool that you have MTP protocol checked under ADB parameters (system section).