That's no device specific issue for the Volla22, it's a general issue of WaydroidHelper. Here's the bugreport. Long story short: You have to manually edit the .desktop-files and set the NoDisplay-Value to the correct section [Desktop Entry].

@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!

@Luzeruz said in Rephone (Gigaset GS5/Volla22) won't boot anymore:

cause its not allowed to flash non original Volla Devices

Here is open source world, where user liberty is MANDATORY.
If some entity wants to restrain user liberty, then user should dump it to the void.

What a user that flash a GS5 with UT or VollaOS should not hope is support from Volla, but Volla has no interest in forbid anything to anyone.

Ubports installer allow to flash any device with any software, and it is like that on purpose.

Some people that want récent hardware with UT on it don't have the money to afford a 450€ V22.

Any Volla 22 is a Gigaset GS5 with specific skin, specific codename, and specific partitioning.

I bought GS5 Lite phones (running Android) for almost all my family, those are GS5 less glossy and more cheap (170€), and are very good devices for very good price, made in Germany.

@Pingu ....it should be no problem, to go back to VOS11 via SP Flashtool and after via Ubports installer to UT 20.04 Focal (the follow the screen)

Do you use UT via VollaBootManager from SD Card ? I had no problems with installing Waydroid via Waydroid Helper App a few days ago (Focal 20.04 Stable , Waydroid LineageOS Androoid 11)....You could install Waydroid also via Terminal

Hello @MV,

You can try sending them as a file or try this version of Teleports which fixes the problem.
https://gitlab.com/ubports/development/apps/teleports/-/issues/308#note_1778248915

@lduboeuf
Problems solved on the Volla with UT doing an update.
On my one with dual boot, there are no updates available now through the Vollaboot loader and the phone continues to not ring with incoming calls

@magnargj You can check the issues at https://github.com/HelloVolla/ubuntu-touch-beta-tests and open another one, if it is a new issue.

@chris_bavaria I use SIM1 only for cellular-data and SIM2 for calls/messaging. Because of the slow activation of the cards (SIM1 is ready maybe 10 seconds later than SIM2), mostly SIM2 is switched to be the cellular-data card. That's really annoying.

@Bolly
Solved. Thank you

Problem Solved
I noticed that there was a 28th of December update on Volla OS so done the update
After that I wiped the SD card and done a fresh install of Ubuntu Touch 20.04
And it's working fine