@pparent said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed: Unable to discover I tried to stuff a .webm file into the imported directory and restarted the service, it produced the same error. Since it seems that the video library is currently unable to play webm files, it seems indeed that the video libs are broken somehow since the mp4 files are not seen as valid (play quite well on my fp5). Yet you seem to have gstreamer library on your system. No clear idea to go forward and it's a bit late now :-(. "sudo snap install mpv" should give you the ability to play the files but it will not prove anything about the libraries since snap application packages all their libraries and don't use system libraries.

@undrwater it depends on the kernel, hence on the particular port for your phone/tablet, more details in this post

@domubpkm said in How to use volte: I speak of Volte in this case, I can confirm you that the people who defined VolTe (the businesss associations working on this standard) are most definitely not bothering with the interactions of UT and Bouygues, this is far far below their field of concern

@XPran You need to turn off the phone, and then boot with long push on "power" and "volume up" buttons at the same time, until you see a "Recovery Menu", then select the first option "Boot recovery", then connect it in USB to your computer and the installer should work fine. Select Ubuntu Touch 24.04, and sit back & relax while the installer is doing its job.

I have a similar problem with my Volla Quintus, see : https://forums.ubports.com/topic/11263/frame-rate-and-slow-animations-movies . I am already in contact with Volla about this. But because "laggyness" or "low framerate" is quite subjective (not easy to measure in technical terms), except you can record the screen in high framerate and without aliasing, it is not easy to talk about and to discuss this problem.

@digi6622 said in Replace Volla OS with Ubports: My problem is that I bought the smartphone second-hand and I don't have an invoice for it. Maybe Volla support can help me anyway. In that case, maybe the Volla Forums might also be a place to find help.

@Dave said in UBports firmware for device "Volla Phone 22 with new display (mimameid_h12)" does not boot when using the "stable" or "rc" channels.: So is it a good idea to run 20.04/devel on Volla 22 phone for daily productive use? Since the devel channel is the only one that boots for you (not sure what is going on there, but since you are experiencing it, you are the expert) then I don't think you have much choice in the matter for now. Overall the devs try to keep the devel channel as functional as possible, but eventually an update will be available that will break your OS in some way. One measure you can take to keep this to a minimum is not to update your OS every time there is an update. If you have a configuration that mostly works, stick to that and resist the urge to update every time you notice there is a new update available. Another way to go is to keep an eye on the forum. There usually is a post warning about an update that breaks devel. But since devel is updated daily, you might see the post too late.

The Phone Service Berlin shop today replaced the display of my Volla22 phone. The display appears to work, as far as can be judged by looking at the fastboot screen or recovery image screen, or the installation screen ("installing system image"). However, the installed Volla Phone 22 with new display (mimameid_h12) firmware does not boot. After installation, and whenever I switch on the phone, the phone is stuck in the bootup greeting screen showing volla~~~ in white letters on black screen. In that stuck state, a short press on the power button just switches off the phone. Is this the Volla phone's boot loader? Note that this problem cannot be explained by phone damage. Before the screen was replaced, the phone did boot and work "normally" with the standard Volla firmware image. And the same "stuck at boot" problem already happened when installing the "Volla Phone 22 with new display" firmware on the not yet repaired phone. Just at that time I attributed the failing boot to the firmware not being compatible with the old display (see post above). edit: the phone now booted, after installing the "devel" channel of the Volla Phone 22 with new display (mimameid_h12) firmware. I also created a dedicated topic for the problems concerning the Volla Phone 22 with new display (mimameid_h12) firmware image: https://forums.ubports.com/topic/10395/ubports-firmware-for-device-volla-phone-22-with-new-display-mimameid_h12-does-not-boot

Hi @magnargj Can you describe what you already did in order to fix your issues? This will allow people to avoid suggesting things you already tried. You mentioned having tried to reflash, but how? There are several methods and I guess this is the way to go except if there is a hardware issue with your device.

Nobody ?

@magnargj See also this topic that I just created: https://forums.ubports.com/topic/10388/volla-phone-22-replacing-a-broken-display I contacted Volla directly via their website's contact form and they offered to sell me a screen. Though I'm now waiting for roughly a week for them to reply to my last email, following up on my request to actually place the order. Also I asked in one of the shops that are listed as Gigaset service partners here: https://phone-service.de/gigaset/ and they appear to be able to repair the Volla 22 phone, as that is the same (?) hardware as the Gigaset GS5. Though there is still the question whether the latest ubports firmware is recent enough to support the newer screens which appear to require newer driver support compared to the stock screens (see the new thread that I linked above).

Addendum: I found an issue at github "HelloVolla" https://github.com/HelloVolla/ubuntu-touch-beta-tests/issues/129 Please also comment or vote for it. I am asking me, if it is a hardware or software problem? How can we narrow the problem to help the dev to solve this issue? Unfortunately I am not a dev, but have no problem to import a fix and play with it to get it fixed. Best regards, zintor

Seems to be fixed with OTA-5 (20.04). Thank you!