@anna
I am using Dekko and GMX account, it works fine send and receive emails.
Maybe encryption and/or authentication are incorrect.

Imap server data is here: https://support.gmx.com/pop-imap/imap/server.html

This weekend I updated my Vollaphone22 from 24.04-1.0 to 24.04-1.1 and screen starts blinking on boot before the logo Ubuntu appears.
With installer reinstalled 24.04-1.1 without wiping data and everything I use every day starts working normally until I found a serious bug on calls.
Yesterday a friend calls me, I answered the call but no sound from other side. My friend repeated calling me and all answering was no sound.
With other phone at hand I search the source of the error and found the Vollaphone22 was the culprit.
How to reproduce is like this, make a call to other phone, wait that the other side answer the call, talk to test that audio is ok, wait that the other phone hang the call, now if you repeat process there is no sound if answered the call. Only rebooting Vollaphone works again, untill other phone terminates the call first and error returns.
This error does not happens on version 20.04 stable.

@lduboeuf said in Broadcast cell id.:

@Carlos said in Broadcast cell id.:

Hello,
how can i list the broadcast cell id that is available on phone location?

Thanks.

Hello,
With this script: /usr/share/ofono/scripts/get-serving-cell-info

Thanks, i will give it a try.

Hello,
how can i list the broadcast cell id that is available on phone location?

Thanks.

@Taiga-Woods
I also have a Vollaphone with same "ghost touch" problems. I decided to change the touchscreen myself and contacted Vollaphone to buy the touchscreen, but the answer was that there are no parts available.
I then found the courage to disassemble the Vollaphone, I take note of part-number of touchscreen and did contact cleaning on connectors. It worked well for some days.
Now I am waiting for a spare that I ordered and maybe fit this model.

A curiosity, when the touch doesn't react to touches, if I press long on the touchscreen area between 7 and # of the dialing app, the touch works again briefly.
Mine is a first generation vollaphone.

@sven yes, i want to replace touchscreen. I searched from China to Portugal and couldn't find it.
I'm in Portugal and I can buy in the European community.

I'm facing the same problem, "ghost touches".

I bought the used Vollaphone in June 2022 and until mid-2023 it worked properly. Since then the problems have started, first sporadically and now more and more often.
Lately, I can't even answer calls without first locking/unlocking them with the power button, and some calls have already been rejected, with one being sent the sms "I can't answer at the moment, I'll call you back later".
I decided to change the touchscreen to see if it would work. I contacted Vollaphone to buy touchscreen and to my surprise I received the reply that they don't have any parts available for the first version.

I'd like to ask if anyone knows of a phone application like the "xev" programme in Linux distros that allows you to test events when you move the mouse or use the keyboard?

@anna Hostname is different from mine, I have imap.gmx.com.

@anna
I am using Dekko and GMX account, it works fine send and receive emails.
Maybe encryption and/or authentication are incorrect.

Imap server data is here: https://support.gmx.com/pop-imap/imap/server.html

Hi,
i have a Sony xperia Z that i am experimenting to install ubuntu touch.
After installation, phone boot and stay on black screen.
When i try SSH connection i get this:

debug1: Next authentication method: password
phablet@10.15.19.82's password: 
debug3: send packet: type 50
debug2: we sent a password packet, wait for reply
debug3: receive packet: type 52
debug1: Authentication succeeded (password).
Authenticated to 10.15.19.82 ([10.15.19.82]:22).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Requesting no-more-sessions@openssh.com
debug3: send packet: type 80
debug1: Entering interactive session.
debug1: pledge: network

I disabled rsyslogd as documentation says, but nothing change.
What could be done?

Thanks for the help.