You could catch on here: https://github.com/SPIRIT-org/SPIRIT

@gpatel-fr I feared you'd say that. But I thought I ask anyway. Nevertheless, thank you so much! Yet, that helped me a lot.

@gpatel-fr The typo seems to have resulted from typing too quickly when I wrote this.

$ GDK_DPI_SCALE=2 snap run gimp

did solve half of the problem. All fonts are accordingly bigger and very good to read. Thank you for this!

However, all Buttons with their symbols on them (e.g. tool selection, layer selection,...) stay tiny.
Is there way to tweak this, too?

Maybe the terminal output is any help?

 $ snap run gimp

(gimp:5667): Gdk-WARNING **: 17:13:55.133: Failed to read portal settings: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.portal.Desktop was not provided by any .service files

(gimp:5667): dbind-WARNING **: 17:13:55.167: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
set device 'Wayland Touch' to mode: disabled
set device 'Wayland Pointer' to mode: disabled

(gimp:5667): IBUS-WARNING **: 17:13:59.655: Failed to mkdir /home/phablet/snap/gimp/557/.config/ibus/bus: Not a directory

(gimp:5667): GLib-GIO-WARNING **: 17:13:59.662: Error creating IO channel for /proc/self/mountinfo: Permission denied (g-file-error-quark, 2)

(gimp:5667): Gdk-WARNING **: 17:14:00.405: Server is missing xdg_foreign support
gimp_widget_set_handle_on_mapped: gdk_wayland_window_export_handle() failed. It will not be possible to set windows in other processes as transient to this display shell.

(gimp:5667): Gdk-WARNING **: 17:14:00.406: Server is missing xdg_foreign support
gimp_widget_set_handle_on_mapped: gdk_wayland_window_export_handle() failed. It will not be possible to set windows in other processes as transient to this display shell.

(gimp:5667): Gdk-CRITICAL **: 17:14:06.972: gdk_wayland_window_unexport_handle: assertion 'impl->display_server.xdg_exported_v2 || impl->display_server.xdg_exported_v1' failed

Hi,

I'm running UT (24.04-1.2) natively on a Volla Tablet (no dual boot).
I installed some snap apps like Gimp and LibreOffice. They work great with one exception:

The workspace scales to a normal size and works perfectly. But the menu bar as well as all menus around the work area (where you choose e.g. tools in Gimp or fonts or text styling in LibreOffice) are tiny and it's hard to work with.

I tried different UI settings from within the apps (like screen resolution in DPI from Gimp settings) without any effect.

I tried to tweak that with UT Tweak Tool without success.

I tried to run these apps from terminal with settings like

$ GDK_SCALE=2 GDK_DPI_SCCALE=0.75 snap run gimp

and

$ snap connect gimp:gtk-3-themes :gtk-3-themes

Also no success.

Is there any way to tweak this? Thank you!!!

I have experienced issues on my Quintus:

The bluetooth gui does not see my headsets when searching for devices. But I can directly pair them using bluetoothctl and their hardware identifier.
After having done this, they seem to stay saved in the list of paired devices, since they auto connect from then on.
Yet, the quintus does never show the headsets in the GUI (one are Volla buds, the other is no name).
The Pinetime in contrary works without issues and is always visible in the list.

I can't remember having these issues before which makes me think that is connected to Noble.
My phone is running UT natively, no dual boot.

Maybe this can be added to observations made on Noble that might be addresed at some point.

I have experienced issues on my Volla Phone:

Bluetooth works normal at first. But when no audio is streamed for some time (e.g. your local playlist is over), the phone turns bluetooth off. When I turn it back on, I can't connect to the headsets again (tried with Volla Buds and a no name headset). I have to reboot the device to make bluetooth work again.
It looks like the GUI switch indicates bluetooth is enabled but I think it's not.

I can't remember having these issues before. Therefore I think it's a Noble issue.
My phone is running UT natively, no dual boot.

Maybe this can be added to observations made on Noble that might be addresed at some point.

Libertine funktioniert meines Wissens auf Noble nicht zwingend richtig. Du hast nativ Snap Support, also Anwendungen wie Libre Office, Gimp usw. kannst du direkt als Snap installieren.
Die Menüs sind sehr klein, aber die Arbeitsbereiche skalieren normal, man kann ganz gut damit arbeiten.
Soviel im Moment von meiner Seite...

EDIT: Dual Boot funktioniert meines Wissens nach nur mit Volla OS, von dem aus man mit dem Volla Boot Manager UT als Zweitsystem einrichten kann, nicht umgekehrt

For me it also feels more performant. That's great!

A big THANK YOU to the dev team!

@pparent said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed:

@jojumaxx

Does that work without having developer options enabled?

Normally yes, it's unrelated if we're talking about Ubuntu Touch developer mode.

Have you tried to 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 the installer? For me it is detected by the installer only this way.

Thank's for reporting this bug, I'm honestly a bit cautious about upgrading my own VollaPhone 22, since there were similar reports in pre-release, and apparently still now. Anyone can report it the upgrade worked for them?

Thank you so much, that worked.
The installer recognised the phone as Volla Phone 22 (mimameid) again, immediatly. Flashing went smooth, without problems and Yumi was normal sized again during installation (I don't know if that matters or is of any interest).
My Volla Phone 22 is on 24.04-1.1 stable now, too.

While this went smooth on my Volla Phone and Volla Phone X, the upgrade from 24.04-1.0 to 24.04-1.1 failed on my Volla Phone 22.

I'm on stable channel and startet the upgrade process from the updater in the settings.
It rebooted and the normal update applying screen showed (Yumi was tiny compared to the other phones).
It rebooted again and got stuck at the Volla logo. After an hour I turned it off because it got pretty warm.
Now, after turning it on, I see the Volla logo and then the screen starts flickering and nothing else happens.

What am I supposed to do now?

I had issues with this phone before, Volla support helped me to solve. Since then, the installer doesn't recognise the phone as Volla Phone 22 any more.
Nevertheless, that was in 16.04 times and all upgrades (to 20.04, to 24.04 and those in between) went yet smooth since then...
So in case of using the installer I have to choose it manually...

Should I try the installer?
Does that work without having developer options enabled?

Thanks in advance!

Yes, without a working clipboard it's unfortunately hard to use another browser...

Thanks for all your answers.
I flashed UT myself (just to mention it).

What I summarize is, that my VP22 seems to perform "within normal parameters".
That calms me down and is kind of what I hoped to hear.
Thanks for resolving this issue.

@gpatel-fr I can't use lsmem since the folder it aims to (/sys/devices/system/memory) does not exist. Maybe I overlook something.

I thought, that 'total' of 'free' shows the correct amount of physical ram.
However, the result is noticably different and the VP22 should probably perform better...

Hello again,

some time ago I reported about
the laggy performance of my Volla Phone 22.
Today I compared the output of free -h of my Volla Phone 22 and a Volla Phone X which both are supposed to have 4GB of RAM.
Both are on 24.04-1.0 stable.

Volla Phone 22 output:

          total     used       free     shared    buff/cache   available
Mem:      3,3Gi     2,4Gi      254Mi    54Mi      707Mi        941Mi
Swap:     1,8Gi     103Mi      1,7Gi

Volla Phone X output:

          total     used       free      shared   buff/cache    available
Mem:      3,7Gi     2,5Gi      158Mi     51Mi     1,1Gi         1,2Gi
Swap:     0B        0B         0B

Both Phones are running the same apps (Terminal, Launcher Modular and Morph (same number of tabs)).

I am ok with 3,7 GB of RAM of the Volla Phone X, I suppose that's within tolerable range. But why is my Volla Phone 22 missing 700MB of RAM?
Is that why it's swapping? And is that why it performs laggy?

Maybe other Volla Phone 22 owners could verify their RAM for comparison here?

@Kamikaze said in Volla Tablet on UBPorts questions:

I am wondering how well the Volla Tablet works with UBPorts?

I ordered the Tablet with UT and also got the keyboard some days ago. Maybe I can answer at least some questions. I didn't use the tablet often before the keyboard arrived.
And even since I got it, I had not much time, yet.

From the short time I tried (without any troubleshooting) I can say:
UT doesn't always recognize the keyboard at startup. You need to disconnect and reconnect to make the tablet realize, the keyboard is there.
Tapping on the touchpad or two finger scrolling etc. doesn't work. You have to use the physical "mouse" buttons. The sensibility of the pointer is too low.
Even though there are mouse and touchpad settings you can't set anything because it asks you to connect bluetooth mouse and keyboard.

Battery life: Can't tell yet

Bugs: Sometimes charging takes the whole day and it discharges even while charging. When turning it off it keeps discharging and shortly after the battery is completely drained.
But that's not always the case (I haven't figured that out, yet). And yes, I'm using the charger and cable delivered with the tablet.

Yes, there is a stable 24.04 release

Wifi is stable so far.

Haven't installed Waydroid yet.

Maybe that helps a bit...

Update doesn't start on Volla Phone (the original one).

I'm on OTA-10 (stable).
I selected "Upgrade" from the screen as seen in the screenshot from domubpkm above. It downloaded the update. When I tap on "Install" it shows the known blue colored "Restart & Install" button.
When I tap on it, it disappears and just nothing happens.
Tried several times, even with reboots in between.
So what am I supposed to do?

EDIT:
After asking in the Telegram group I triggered the update by executing

sudo sh -c 'sync && reboot -f recovery'

in the Terminal. Should also work by booting to recovery manually by holding volume up while powering on.
Thanks to the guys in the group! My Volla Phone is on 24.02-1.0 now

In this Reddit post, there's some "demo video" shown:

https://www.reddit.com/r/UbuntuTouch/comments/1nolhr1/odm_devices/

Hi,

just stumbled across a device called "QCOM U6701" with Ubuntu Touch preinstalled.
Doing a quick search I didn't really find a manufacturer website, but if you search for it, you'll get some hits. Don't know if that's for real, looks kinda scammy...

However, just wanted to leave that here.

Maybe someone else knows more...

You can install Termux on any Android Tablet and run a full blown Linux desktop there. It's relatively easy to setup and works very well.

That's at least my replacement until something comparable is reached in Linux OS world.
The Volla tablet should get support on UT soon, at least I hope so and look forward to it.

My Volla Phone 22 (no replaced display) performs very laggy.
Even with no app open, fading in/out the sidebar or the app drawer is laggy. Also just scrolling up/down the settings menu.

The original Volla Phone performs way smoother here.

What could be the reason for that?
I switched channels, but that didn't change anything.

Any help appreciated...