Posts made by AppLee

Hi @ds2k5

This setting is not available directly AFAIK, but maybe it's tied to the volume of alarms set in the Clock app.
Either way, I think you should be able to use uVolMan from the OpenStore to meet your expectations.

No worries,

But you can have a look at what is already reported there:
https://gitlab.com/ubports/ubuntu-touch/-/issues

Before creating a new issue, be sure it hasn't been filed before.
There is not a lot of developers so don't bother creating a lot of issues, it takes time to sort them out and prioritize them.
Also issues can stay open and untouched for years because of the same reason...

Hi @Salah

Your enthusiasm for the project is appreciated and I hope you'll continue trying to contribute.

But please can you stop using this kind of sentence:

@Salah said in Incoming Call (Answer|Reject) Changing UI:

I hope in 24.04 or later will change [...]

This kind of comment is not helpful, hoping doesn't make things happen magically.
To quote a famous master "do or do not, there is no try".

So if you want something to happen there are few options:

1. Do it yourself and ask for support when you get stuck
2. Create a feature request or a bug report on Gitlab
3. Donate, that's another way of hoping but it's more useful to the community
4. Lead developers and motivate them

Publicly stating that oneself hope for something is just a prayer and we're no god, we're a community, individuals rallied under one banner pushing in the same direction...

Hi @tigerpro

I don't think anyone else is attempting this port.
But if you need help you can post in the porting section of the forum if you got stuck after reading the porting documentation.

Hi @JDee-Intl

Your situation is as expected.
LTE data works, but the phone stack (VoLTE = Voice over LTE) is not working.

@JDee-Intl said in VoLTE status on Pixel 3a/3a XL:

I'm not familiar with porting to halium 11, but interested in learning and/or can troubleshoot and/or test. What can I do to help?

Standby for the moment, I bet Alfred will post a call for help when the situation starts to evolve.
Some additional work is also required on the plugins.

Sorry you'll have to be patient. We're getting there but it's not a done thing.

Hi @bbiw

This is normal.
A phone is not an internet router...

@jam1388

That's how it i supposed to work.
There is an issue with your port or your individual device.

But as @MrT10001 told you it's best to follow the instructions as it has been tested by others and the experience is understood and known.
When you go off rails or do some unsupported actions then you're basically on your own.

People told you to follow instructions, you ignored the advice so it's impossible for us to determine whether it was your own doing or a legitimate issue with the port.
Bug analysis is now on you

About VoLTE there are still some work to do. It's almost there for Mediatek devices but there is still work to do for Qualcomm's.
If I had to guestimate I'd say it will be widely available mid-2025.
But no promises, development is hard to predict.

Hi @Ontario

It really depends.
Some apps can be tweaked using configuration files, some other would need a complete overall of the GUI.
There are also limitations with snaps at the moment, for example not being able to use the On Screen Keyboard, ...

Without more information on what you have in mind I can only say.
1- Try it out
2- Try to make it work for you
2.a If you can't then move on
2.B If you made it work for you => Try to make it work for others or fetch help to achieve this new goal.

@AmauryDBZ You're correct. Not yet.

The idea is to have this kind of visibility so users know what to expect and devs know what would be great if they worked on it.

Hi
@jam1388 said in Bought OnePlus Nord N10 5G but got OnePlusN10METRO ? Will this work ?:

is there anytime frame

This is an open source project based on volunteer work.
We cannot have 3 or 5 year plan, it will depend on people's skills and motivation in order to achieve this goal.

VoLTE is still a priority, but basically there is so few people able to understand and work on this.
We're doing our best with limited resources.
Everyone is doing their best to support the community's efforts.

Hi @Ontario

The snap package you can install using snapz0r are often not intended to be used on a mobile phone.
So for each software it will require tweaking in order to be usable with a small touch screen.

There is no way Ubuntu Touch can accomodate for every GUI software out there.

Hi @AmauryDBZ
Kind of yes and mostly no

You can find issues on Gitlab and AFAIK this kind of discussion happen in the dev sync meetings.
I never attended one, so take it with a grain of salt.

But the idea would be to be better structured and organised so volunteer developers have a vision of what is an open priority for Ubuntu Touch.
As discussed in intro of the last Q&A, we need to come up with a solution to motivate developers on tackling priority issues or features.

The Dev Sync meetings seem to be a good place to start but it's already a work in progress.

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.