Hi @Salah
The next OTA will probably have no improvement to the camera.
Even for 24.04 it is not done...
That is something we need to work on... for example to support larger files or multi camera...
Hi @Salah
The next OTA will probably have no improvement to the camera.
Even for 24.04 it is not done...
That is something we need to work on... for example to support larger files or multi camera...
@bbiw said in Problems with apt because root partition isn't big enough:
The biggest problem i see with UT are the proprietary drivers. Even with libertine there's no e.g. hardware acceleration. By using stow and the symlinks it creates i can, at least with glmark2-es2-mir, have hardware rendering.
You seem to have enough knowledge to contribute to the port for the device(s) that you own.
I may be a technical person, but I don't know enough on this topic.
To fix your issue with hardware acceleration, you might want to have a look at the porting documentation.
Try to build the image from source and see what you can do to improve the experience with the Fairphone 4 for everyone else.
My mother uses Ubuntu on her laptop without any knowledge about Linux and I hope they soon might be willing to give Ubuntu Touch a try.
To me, the goal is to bring an alternative to anyone willing to regain control over their data.
Doesn't matter if they know how to tinker with their phone. And that's also what I want for me.
I use Linux since 1995 and I never used Windows on a personal computer since 2001.
I know my way around things but what I like is that I don't need to if don't do something stupid.
And I expect the same for my phone. I have 3 devices with Ubuntu Touch, one is my daily driver and is often on Stable or on RC just to be sure that an OTA won't break my phone. The others are to tests things out and improve my knowledge of our OS and maybe one day I will be able to make a port.
Hello @bbiw
This is not a problem and this is not something we want users to do.
The reason is if they are not able to fix this themselve then they probably should not try this.
We don't want people come back and complains about having bricked their device because they didn't understand why Ubuntu Touch is image based.
As we frequently say, a phone or a tablet are not regular computers.
For the purpose of Ubuntu Touch, we decided to go with ease of use and daily driving capabilities, so the image should be stable and users are restricted to prevent issues from the user.
There are enough quirks and trade-offs to live with as it is...
But thanks for pitching in some ideas for people who understand the risks.
Hi @twitchos
I took the liberty to move your post in this new topic as I think it will make things easier for everyone.
I tried also to give some answer in my introduction post...
Hello everyone,
In order to keep things orderly, I decided to create this post so you can have the latest news regarding VoLTE support for the Pixel 3a.
In Q&A 152, Alfred gave some information regarding the issues he's facing in that regard.
To sum things up and (try) to avoid mistakes, I'll keep it simple.
The plugins required to use VoLTE on Ubuntu Touch is available for both Qualcomm and Mediatek devices.
But integrating it for the current port is not possible or complicated.
Alfred mentioned 2 ways to solve the problem, but I remember only the one involving rebasing the port on halium 11.
What I remember also is that Alfred needs help to (at least) test things out because his device is not authorized by his service provider to use VoLTE.
So I take this opportunity to ask for your help.
If you have skills to help port to halium 11 that would be great.
If you cannot, maybe you can donate some money to Alfred to thank him for all the work he already put into these devices and the upcoming work.
And @fredldotme if you can share more information regarding what you need (skills or how to check if we can technically help), that would be wonderful.
Hello @lduboeuf
Do you happen to know someone who can point a volunteer towards the appropriate documentation/repository so someone willing to help would have something to start with?
Hi @AmauryDBZ
Given that the software haven't change it's probably something hardware related.
Have you tried disassembling your Fairphone and clean the connectors, especially the one for the screen?
If you have a dry air can you can start by just dusting off the connectors.
If you find something sticky then you can try to use isopropyl alcohol to clean them.
Best of luck
Hi @Salah
You posted your question in the Pixel 3a/3a XL sub-category, so I assume you're having issues with one of those model.
I have the Pixel 3a (non XL) and the vibration seems OK.
But to be honest I didn't use it with Xenial as I was waiting for 20.04 to go back to daily driving Ubuntu Touch since I let my Nexus 5 go...
Also 16.04 to 20.04 was not just a system update but a whole new port as far as I can tell (I hope I get this right ).
When OTA-6 will only bring system updates. Of course porters can add some fixes and tweaking but it has to be on their radar as device specific issue don't get fixes magically.
Some magic can happen when drivers are updated when using a newer halium version, but it can also be the other way around so it's rarely done as far as I can see.
Hi @tuXut
So according to Marius in the last Q&A, having a newer version of Halium allows us to benefit from newer drivers and config file for a better support of VoLTE on the given chipset.
So having a newer halium version will help improve the quality and the ease of use.
So it's not a yes/no answer, it will depend on the device and the maintainer of the port.
For a specific device, the porter can try to integrate the plugin hoping that the config files and radio drivers were already good enough.
VoLTE needs a new port for the devices, so the porters might want to switch halium base in order to get the more recent drivers and config files hoping not many regressions.
As an example, Alfred is considering switching halium base for the Pixel3a in order to get better drivers for the modem, GPS, ...
So a recent halium version makes things easier but it's not a requirement.
But there is no hard requirement like kernel version to allow systemd during the move from xenial to focal.
I hope this clarifies things.
Hi @Kamil
Currently the system doesn't allow for AppImage.
We only recently (I mean Alfred) managed to handle snaps but a complete integration into the OS is not yet possible as well.
So if you're willing to take upon yourself to bring this feature to Ubuntu Touch, please do.
Else it is not in our radar at the moment.
Hi @volatius
Yes this is very strange.
I'm at the Ubuntu Summit this weekend, but I'll make some tests later next week.
GPS signal has nothing to do with your issue.
Routing uses map data that you locally downloaded.
There are different levels of precision and the algorithm tries to figure out the best itinerary, usually by prioritizing the major roads until it can't and has to fall back on smaller streets.
I'll try to replicate your issue if I can and let you know what I think about it.
Ping me in few days if I forgot about it
Please avoid advising people to stop applying updates or to not follow documentation.
The best course of action is to follow directions and if something is still not working and you managed to work around the same issue then you can explain what you did and that it worked for you.
But every device is different and things can go south.
Regarding OP's issue, maybe it's a GPS signal issue, but given the description I doubt it.
@volatius OpenStreetMap's quality depends on the local community's involvement.
So maybe try a similar scenario in another country to see if you can replicate the issue.
Also if you can share a picture of the route so we can visualize things.
Hopefully it can spark some ideas, but currently I'm stuck as I had no issue in my use cases...
@Kamil IDK, it depends on what the porter did.
But if the only options are 60 and 90, I would guess 60 to improve battery usage.
Hi @Kamil
No, currently you cannot change the framerate.
Of course software being software you can investigate on how to implement such feature, but it's not that simple ; one would need to come up with a way to toggle between the two mode for power management.
But 90Hz is only useful for high framerate games which is a fringe scenario for Ubuntu Touch.
The guide state to check the firmware version.
So the link is to the firmware.
It does not state one should flash it manually, except if you know what you're doing.
The general rule is to install whatever version of Android is required for a given device.
How to install Android or a particular version of Android is not something UBports wants to be accountable for.
There is a plethora of guides on how to mess with android available online...
The first steps to install Ubuntu Touch are not something we have direct control over.
So unlocking the bootloader and getting sure that one have the proper version of Android will remain the user's responsibility.
Just follow the porter's instruction as to what version should be present before running the UBports installer.
Hi @ds2k5
You can try to download it from the website and install it on Focal.
It's probable it won't work, but might be worth a try.
Or can make a feature request on their Gitlab project.
Hi @jojumaxx
As far as I know, it is easier and faster to create a port for Ubuntu Touch on an Android than it is on the PinePhones.
You seem to think that the time from contributors can be managed like in a company ; that is simply not true.
When a porter has a desire for Ubuntu Touch on a device they own, they invest their time doing so and share it with the larger community.
And that's probably not time they would have invested in Pine64's devices or another Ubuntu Touch related project.
A major chunk of development time is actually spent on keeping up with Ubuntu LTS.
A effect is the Qt version supported and it lead to the fact that our browser is out of date.
If we had the manpower a better strategy would be to keep up with Ubuntu Stable and update every 6 months, but that is out of reach at the moment.
To answer your question we are not running after Android and there are few ports to newer devices.
The exceptions I have in mind are Fairphone5 and Volla better we are partnering with them.
We partnered with Pine64 but it was very difficult to improve with the drivers provided if I understood it correctly.
I for sure would love to have an open hardware phone well supported by Ubuntu Touch.
But it has some challenges that we could not address without compromising the OS so focus shifted.
Now if you can motivate enough skilled developers to improve the Pine devices situation that would be great and welcome by many I'm sure.
What Oren is doing with the PinePhones is remarkable, you're absolutely right.
And I'm sure he appreciates the gratitude love and if you can donate it's always appreciated...
Hi everyone!
I know it can be hard to grasp what UBports does.
It's hard for people to buy a device (often very expensive), install Ubuntu Touch on it and realize it's not what they expected.
Many people are disappointed because some things are taken for granted, considered: "normal" or "basic".
Also people come with "needs" related to their phone usage.
I'm lucky because what I consider "needs" are very simple:
Shelter, food, oxygen and friends
The rest is nice to have and I consider it privileges.
This intro is to put things into perspective and to explain what is done at UBports.
When considering Ubuntu Touch at the moment, it is important to make the distinction between:
The foundation UBports encourages porting to new devices and is set to promote the best ports or at least to give a clear picture of the features you can expect.
The foundation also depends on app developers to build and grow a catalog of apps that users might expect.
This is a difficult task as most app developers are focusing on iOS and Android in order to earn money and very few are willing to give their time to bring killer apps to Ubuntu Touch.
Currently, the foundation's efforts are focused on the maintenance of Ubuntu Touch ; rebasing on 24.04, bringing support for VoLTE and 5G which are critical tasks.
With this in mind, it's easy to understand that, with a skeleton crew, it's very hard to fight all those battles at once.
We are also facing a "battle" within. This one is related to our users and is about "support".
This aspect of things has been brought up lately and some community members start to get fed up with it.
My understanding of the origins of the problem is that we needed to bring more people onboard with us to help:
This effort to widen the community attracted also people that did not help with those tasks and generated support.
Ideally newcomers would learn from the elders and then help back newer users.
In reality it mostly falls back on the same highly motivated people which for some are also helping in porting, developing apps or maintaining the OS (sometimes all of the above).
So first of all I would like to thank all the people helping this amazing community.
But my goal today is to ask people to understand the situation we are in and to encourage them to help us out.
Ubuntu Touch and the UBports community have a lot to fight for and it will be really hard in the coming months.
So if you feel you can help us out a bit more, then please do.
We need skills to port or maintain current ports.
We need skills to maintain the OS, test it out and fix issues.
We need developers to maintain and create new apps.
We need money to keep paying the bills for infrastructure.
We need sponsors or crowdfunding to invest on some targeted features and give some money to people who already invest so much in this community.
We need volunteers to give back a bit of what they got from this community: support, moderation, communication, organization, management, lobbying... anything you think we lack of...
Complaining is natural and understandable but it's not helping... and we are in desperate need for help.
Hi @Sota4Ever_k
That's progress.
But sadly I never ported Ubuntu Touch to a device, so I'm not able to help you with it.
Have you tried to follow Keneda's suggestion and join the porting group on Telegram?
Hi @Andrej1299
Telegram will ask on the new device to register with your phone number.
Then it will send a code that you'll have to enter.
So as Bolly said, it's best to set your new phone first.
What I do is set everything using WIFI, install the app and configure everything.
Create a backup or transfer data to your new device (if they both run Focal)
Then when everything is working on the new device, I switch SIM on a weekend, so I have time to mess things around if the mobile network does not work out of the box.
Test everything out and you should be golden.