Hi there
I am having some issues finding a proper remote desktop tool for Ubuntu Touch (20.4), does anyone have some advice for me? I want to use the phone as a "client" for a network project in school, remoting into it and showing that it still gets a DHCP address, and can access the internet when plugged into a L2 switch.
World
Topics from outside of this forum. Views and opinions represented here may not reflect those of this forum and its members.
-
Koloběžky, kola, EUC, skateboardy a zkušenosti s nimi
-
A world of content at your fingertips…
Think of this as your global discovery feed. It brings together interesting discussions from across the web and other communities, all in one place.
While you can browse what's trending now, the best way to use this feed is to make it your own. By creating an account, you can follow specific creators and topics to filter out the noise and see only what matters to you.
Ready to dive in? Create an account to start following others, get notified when people reply to you, and save your favorite finds.
Register Login-
-
I've experimented a bit around building a click package based on Qml6 with Qtwebengine6 , to display some html/css/js page.
I built a virtual piano application that works well with tactile and multi-touch, that I wanted to have. I've decided to base it on piano.co code but, it did not execute well in the older web-engine, so I figured let's experiment on bundling Qt6/Qml6 into my package.
The conclusion is: It does allow to build a working .click package based on Qml6 by bundling all the Qt6 dependencies provided by the ubports repositories, and that runs as a charm (see screenshot bellow) ... And the openstore refuses to publish it because it has references to Qt6. I thought it would be possible as we have some version of Morph based on Qt6 in the openstore, but I guess the devs from the core team must have special permissions for that?
Anyway if you are interested here is the repository:
https://github.com/pparent76/touchpiano
And here is the .click compiled (confined click):
https://github.com/pparent76/touchpiano/releases/tag/v0.1.2
I guess I will have to wait for the Qt6 migration to publish this app to the openstore!
, In the meantime here are some screenshots.
@bhdouglass Ok thank's a lot it worked! https://open-store.io/app/touchpiano.pparent I promise I will use Qt6/Qml6 very sparingly, until the library is available inside the OS. In the mean time this app can serve as a demonstration Qml6 app. Ps: But what might be usefull is to start building a a Qt6 version of Whatsweb, that is currently broken. -
Hello,
When trying to upgrade I got the error:Downloading boot0… Done Downloading boot1… Done Downloading _install.sh… (Connecting…) --- Failure --- Details for developers: java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but no scheme was found for install… at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1261) at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1634) at okhttp3.Request$Builder.url(Request.kt:184) at org.andbootmgr.app.util.AbmOkHttp$run$2.invokeSuspend(AbmOkHttp.kt:42) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104) at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:111) at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:99) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:811) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:715) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:702)```Downloading _install.sh…
Done
Flashing DroidBoot…
Note: probably cannot write to bootloader
--- Failure ---
Details for developers:
java.io.FileNotFoundException: /dev/block/by-name/lk: open failed: ENOENT (No such file or directory)
at libcore.io.IoBridge.open(IoBridge.java:574)
at java.io.FileInputStream.<init>(FileInputStream.java:179)
at com.topjohnwu.superuser.io.SuFileInputStream.open(SuFileInputStream.java:59)
at com.topjohnwu.superuser.io.SuFileInputStream.open(SuFileInputStream.java:42)
at org.andbootmgr.app.UpdateDroidBootFlowKt$Flash$1.invokeSuspend(UpdateDroidBootFlow.kt:71)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:811)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:715)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:702)
Caused by: android.system.ErrnoException: open failed: ENOENT (No such file or directory)
at libcore.io.Linux.open(Native Method)
at libcore.io.ForwardingOs.open(ForwardingOs.java:563)
at libcore.io.BlockGuardOs.open(BlockGuardOs.java:274)
at libcore.io.ForwardingOs.open(ForwardingOs.java:563)
at android.app.ActivityThread$AndroidOs.open(ActivityThread.java:8820)
at libcore.io.IoBridge.open(IoBridge.java:560)
-
Hi all-
I have been using UT on my Pixel 3a as my daily phone here in Canada for a few years. However, 3G coverage is slowly being phased out and i'm worried i'll be stuck without being able to make calls soon.
What is the exact status of VoLTE functionality on the Pixel 3a? I see that another update to UT has come out recently (24.04-1.2, i've not updated yet). I know people have been working on it, but i can't tell if there is any functional version of it yet (either development or stable).
If VoLTE on the Pixel 3a is not an option anytime soon, i may need to consider changing my phone. In that case, what options do i have?
Thanks much!
-Fizz
-
Hello everyone,
I realized a privacy concern about microphone that concerned unsuspended whatsweb, and whatsnew, but that could possibly concern many other webapps, or even regular apps.
The concern is that when running those webapps with microphone permission allowed and unsuspended to get notifications, then the subjacent website (in that case whatsapp) can effectively spy on your microphone at any moment, while your phone is suspended and the screen turned off, without you even being notified about that.
I'm going to see what I can do, on the application side, but it's not easy as it seems chromium engine does not allow easily to switch on and off the microphone in the webview, whether we are using electron or on Qtwebengine. You can chose to give or not the permission for the microphone, but when it's given it's hard to revoke without reloading the whole application.
Here are some possible features that could be useful, on the side of the OS:
- Add an icon to the systray when an Application is recording the microphone as KDE does.
- Add an option to disable the microphone for all apps (except maybe the phone app) when the phone is suspended.
- Or Even add an option to automatically diable the microphone for apps that are not in foreground (maybe except if they have a background microphone authorization)
- Add some tools for the apps themself to be able to know wether or not they are recording, and enable/disable or mute/unmute the microphone for themself a the level of pulseaudio. This should be accessible even for a confined app, and through shell command so that is universal.
Any thought on that?
@nbdynl Apps like Signal or Whatsapp will maintain a background network connection with their servers weather or not they are calling. On top of they, if they wanted to spy on on you they could leverage that to start a fake invisible call/connexion, so that they can keep spying quietly when the phone is suspended. I don't think whether or not there is "an active forground connection", can be used to determine reliably if the app is legitimate to record the microphone when the screen is off... -
Ubuntu Touch Q&A 185
Ubuntu Touch Q&A 185 is live this Saturday 7th March at 19:00 UTC on our YouTube channel: https://www.youtube.com/watch?v=l6_v0on1DFI
We will cover all the latest news and development, and your questions and answers.
Questions can be posted live during the show or using this Forum link for priority: https://forums.ubports.com/topic/12033/ubuntu-touch-q-a-185-call-for-questions.
Please remember that questions on porting to device **** or its status, or questions on bugs will not be answered.
UBports@telegram
#ubports:matrix.org#UBports #UbuntuTouch #UBportsQandA #Lomiri #OTA12 #UTnoble #Ubuntu
-
Just wondering what kind of apps you wanted on Ubuntu Touch.
As for me, I'd love-An alternative browser
-a color to do list
-vocal search
-an app to learn HTML5
-One for the QML basics
-some crazy alarm you can't stop without solving maths equations
-one for a dark mode (reducing the intensity of light even more)
etc etcAnd you? what would you like to see?
read more →Hello, personnaly, I m found of the fossify apk (on android - https://f-droid.org/en/packages/org.fossify.calendar/ ). Calendar, note, contacts... they are great quality and cover a large needs. most of all, it will help androids (lineage) users to switch to UT... I don't know if the code is realy open and how difficult it is to port them (i have no any competences in app building). but it could be agreat advantage for UT ? -
Am using Linux Mint since many years. Now the idea grows to purchase an advanced mobile phone, load Ubuntu touch and use it as a mobile PC. My usage is not too heavy!
Any recommendations to hard-/software combinations that might work?
read more →protonvpn in Libertine Out of curiosity I tried to install protonvpn in Libertine container in the same way one would install it on Ubuntu Desktop. Protonvpn didn't work at all, showing loads of dbus related errors. Libertine runs in chroot according to python3 error messages, which apparently complicates a lot of systemd related things. Maybe it is not impossible to fix, but I kindly request more skilled developers to look at the errors protonvpn is throwing to figure out what to do about it. Hopefully the protonvpn team realizes that they need to help out and make their software run also on Ubuntu Touch, not only regular Ubuntu, Debian, Fedora, openSUSE and Archlinux. Secure FTPS server I have seen discussions that there is a need for a solution where Ubuntu Touch offers some kind of server connectivity, like secure ftp with wifi hotspot so that another device can connect directly to Ubuntu Touch and share files. The Ubuntu Touch wifi hotspot serves as an access point for another device to obtain an ip address so that a connection to the server can be made with a ftps-client. Here is a simple working python3 ftps-server example that can be installed in a Libertine container. It has been tested with Android app CX File Explorer which has an inbuilt ftps client located in the section on the right side NETWORK/New Location/REMOTE/FTP -> choose FTPS passive explicit mode: FTPS server which works with Ubuntu Touch internal wifi hotspot #!/usr/bin/env python3 """ FTPS server with a simple switch to enable or disable pyftpdlib debug logging. File name: start-ftps-server.py Save this file in Libertine container folder: mkdir $HOME/ftps_server Make executable: chmod +x start-ftps-server.py Run ftps server: ./start-ftps-server.py [--debug] or python3 start-ftps-server.py [--debug] Stop ftps server with Ctrl + C Default ftps username: user Default ftps password: 12345 Default port: 2222 Install dependencies: apt-get install python3-pyftpdlib python3-netifaces python3-openssl Create ftp directory: mkdir $HOME/Downloads/ftp Create self-signed certificates in the same directory as the ftps server: cd $HOME/ftps_server openssl req -x509 -newkey rsa:4096 -keyout keyfile.pem -out certfile.pem -days 365 -nodes """ import argparse import logging import netifaces from pyftpdlib.authorizers import DummyAuthorizer from pyftpdlib.handlers import TLS_FTPHandler from pyftpdlib.servers import FTPServer from OpenSSL import SSL def parse_args(): parser = argparse.ArgumentParser( description="Start a minimal FTPS server (pyftpdlib)." ) parser.add_argument( "--debug", action="store_true", help="Enable detailed pyftpdlib debug logging.", ) return parser.parse_args() def configure_logging(debug: bool): level = logging.DEBUG if debug else logging.INFO logging.basicConfig( level=level, format="%(asctime)s %(levelname)s %(message)s", ) logging.getLogger("pyftpdlib").setLevel(level) def get_current_ip() -> str | None: for iface in netifaces.interfaces(): addrs = netifaces.ifaddresses(iface) if netifaces.AF_INET not in addrs: continue for link in addrs[netifaces.AF_INET]: ip = link.get("addr") if ip and ip != "127.0.0.1": return ip return None def create_ftps_server() -> FTPServer: authorizer = DummyAuthorizer() authorizer.add_user( username="user", password="12345", homedir="/home/phablet/Downloads/ftp", perm="elradfmwMT", ) ctx = SSL.Context(SSL.TLS_METHOD) ctx.use_certificate_file("/home/phablet/ftps_server/certfile.pem") ctx.use_privatekey_file("/home/phablet/ftps_server/keyfile.pem") handler = TLS_FTPHandler handler.authorizer = authorizer handler.allow_passive_mode = True handler.passive_ports = range(60000, 65500) handler.ssl_context = ctx handler.tls_control_required = True handler.tls_data_required = True ip = get_current_ip() if ip is None: raise RuntimeError("No non‑loopback IPv4 address found.") server = FTPServer((ip, 2222), handler) return server if __name__ == "__main__": args = parse_args() configure_logging(args.debug) ftps = create_ftps_server() host, port = ftps.socket.getsockname() print(f"Starting FTPS server on {host}:{port} (debug={'on' if args.debug else 'off'})") try: ftps.serve_forever() except KeyboardInterrupt: print("\nServer stopped by user.") except Exception as exc: print(f"Server error: {exc}") Conclusions from desktop mode tests As you may see, most software that you find on a linux desktop does actually run well enough on Ubuntu Touch, although inside Libertine container. You can get most things done that you normally would use a desktop, laptop or notebook for. The absolute biggest headache is the difficulty to get copy-paste to work well between all windows, especially to and from LibreOffice. Screenshot functionality like xfce4-screenshooter or gnome-screenshot is wanted. It is used to grab a single window or to select a region and save it, or copy the screenshot directly into a chat. Printscreen key on a regular wired PS2 keyboard takes a screenshot of the whole screen and saves it in ~/Pictures/screenshots. I didn't get xfce4-screenshooter or gnome-screenshot to work as intended. Automated, simple VPN that regularly adjusts parameters and autoselects a good node is probably wanted by some users. An example of that would be the functionality of protonvpn, which exists on Android and linux desktops. Ability to control random MAC-addresses on public wifi networks is wanted. I read somewhere that Ubuntu Touch offers some privacy concerned MAC-address shifting when moving between public wifi networks, but it would be nice to get this verified by someone who knows more about how it works in detail. I think that Ubuntu Touch with Libertine can be used as a PC, a linux desktop, already now. It passed the test to be considered good enough. Once the copy-paste functionality works to satisfaction, it will be many user's choice. If the device supports USB3.0 display out so that you can connect Ubuntu Touch to an external monitor, mouse/touchpad, keyboard and external harddisk or pendrive, you really get the PC experience already in my opinion as a newbie myself. For USB2.0 devices, it would be good to know exactly what is needed to connect to needed periferals including a monitor and compare the cost to a device which offers USB3.0 display out. I have come to understand that the USB-port is used quite a lot more than one expects, which makes it the most sensitive part that eventualy will stop working at some point. RAM memory 6GB seems to be enough for all the use cases I went through. Most of the time I see 2.5-4.2 GiB RAM used, with the absolute top at 5.9 GiB. Thunderbird and Firefox do not eat as much RAM as I thought they would do. Hopefully these use cases give readers a bit more feeling for what Ubuntu Touch in desktop mode can offer at the present, using snaps and Libertine container. It gets better each day, as more and more users start to experiment with it and share their findings. Conclusions about native mode Desktop mode on a 24 inch monitor offers several ways to increase text sizes so that people with not perfect eyesight can adjust the zoom. The native mode when using the mobile device screen by itself does not offer as much scaling capability as the desktop mode without messing up the look and feel. As a consequence, it may at times be quite difficult to see miniature text smaller than 1mm without a magnifying glass. If Ubuntu Touch is meant for a larger target group, each app has to implement text scaling capabilities so that text can be shown bigger for those who need it without ruining the functionality of the app. Preferably, the text size settings should be set in Ubuntu Touch settings on a global level, which are then used by each app to show the text in the desired size. Android has this functionality from very early versions and new Ubuntu Touch users are going to look for these text scaling settings in the Ubuntu Touch settings. I think users would benefit from an app naming convention that clearly indicates if a native Ubuntu Touch app is supposed to run in desktop mode for improved visibility. As an example, Linphone that is usable on a device screen size five or six inches should be called Linphone. Linphone-Desktop clearly indicates that the app needs desktop mode for visibility reasons. Every app meant to be used on the device without desktop mode should be able to display large text for better visibiltiy without falling over the edge. Another example: Brave browser should be visible and usable on a small screen, otherwise it should be called Brave-Desktop to indicate that you need desktop mode to use the app for better visibility. Yet another example: Thunderbird should be usable on a small screen versus Thunderbird-Desktop which is supposed to be used in desktop mode for greater visibility. Preferably, an app should be able to be useful and have visible text on a small screen as well as in a scaled-up desktop mode. -
Hello, I am about to install Ubuntu Touch OS to my Fairphone 3. At the "How to install Ubuntu Touch OS" section from the Fairphone 3 device page page, it is instructed to "Install the required Android/stock rom version".
Can someone please clarify what exactly this means? Should I install the latest Android 10 version (Fairphone OS version 8901.3.A.0136) which was offered at their official webpage, here:
- fp3-fp3-fairphone-os-updates-changelog-download-links/60430
- Specifically: FP3-REL-Q-3.A.0136-.gms-7c69ec7e-user-fastbootimage.7z
Or is the "Android/stock rom version" referring to something else? One of the problems at the moment, is that the url above to the 7z archive is dead.
Thanks for any help.
-
Has anyone with a Nexus 5 been able to successfully synchronize calendar with radicale?
The calendars are visible, but no appointments can be seen. I set up the account using the calendar. I set up several calendars in radicale. I get a synchronization message for everyone but the calendar is empty ?!
My radicale server has been in use with other devices for years without any problems. What's wrong?
@slowcyclist err, no, my test reconnects to the server. However there is something of a strange behaviour that I don't understand currently. When asking for a sync even in test mode from the command line: syncevolution --print-databases backend=caldav username=<user> password=<pwd> syncURL=http://192.168.20.12:5232 [INFO] start database search at http://192.168.20.12:5232, from sync config '@default', syncURL='http://192.168.20.12:5232' I often see a block, the connection is not established (nor refused). After some time (a few minutes ?) the reply is sent. I see the log of the server at the same time, it does not receive anything, it's syncevolution that is refusing to send. When looking at the same behaviour from the phone UI point of view, when clicking on the sync button, it turns in display busy and after some time the server is receiving data and the sync button turns in mode inactive (but with an red error indicator). Even trying syncevolution --help blocks. It's as if syncevolution was refusing to work at some moments. Looking a bit more, it's as if it's the phone UI connection that is blocking itself (and all other operations such as syncevolution --help or the manual sync that I posted above; when the UI phone attempt at connection finishes, I can then do sync tests from the command line without limitation. It's as if the sync initiated from the phone UI was blocking syncevolution for about 5 minutes, then it deblocks itself (and other syncevolution clients on the phone such as my test sync) , synchronize the events successfully but returns an error. A bit of testing seems to show that the delay is about 5-6 minutes. Maybe it's actually that syncevolution is setup to sync every 10 minutes and the button has no effect other than to block until the automatic sync does its thing. If what you see looks like what I see, that would be a pattern and maybe an issue could be created on Gitlab. -
I have a OnePlus 10 Nord on Mint Mobile. I can send and receive regular text-based messages (just regular text). When my wife and son send images, I get a "Could not fetch the MMS message. Maybe the MMS settings are incorrect..."
Is there anything I need to tweak to be able to view pictures, screenshots, gifs, jpegs, ... when receiving text messages?
I am on Mint Mobile in the US.
read more →@lsitongia any carrier's SIM logged into an android phone with a google account. All RCS goes through Google's servers, and RCS is opt out, not opt in. Go into your google account settings, search for RCS. Turn it off for that device. If you never used that device with a google account, then you're good. So, yes, you can put that SIM in another android phone to turn off RCS. But, you need to be sure what google account you used that SIM with. -
I've taken the liberty of packaging Lagrange for Ubuntu Touch. Lagrange uses its own completely custom C-based UI stack built on top of SDL/OpenGL, which means that while it runs fine, the keyboard does not work out of the box on Ubuntu Touch. The UT package has a patch that 1) enables the keyboard and 2) packages it as a .click.
There are still some issues with the keyboard and integration with the system. Namely:
- Clipboard does not work.
- Keyboard still has some weird behavior on textboxes that aren't the URL bar. You cannot edit text in the middle of them, for example.
- No integration with content hub.
- No integration with URL dispatcher (i.e. cannot open gemini links in Lagrange).
I think most of these should be solvable. I will continue working on it and see what comes out.
You can find Lagrange here: https://next.open-store.io/app/fi.skyjake.lagrange/
-
Hey everyone,
Starting a new bug fixing project for Ubuntu Touch called Smooth Edges (name pending). The idea is simple: fix the bugs that make people give up on UT or prevent them from trying it in the first place.
The Problem
Look, we all know Ubuntu Touch has rough edges. Some bugs are annoying. Some make daily use frustrating. And some make people pull out their old Android phone after a week. We need to fix those bugs first. I'm not talking about theoretical issues or edge cases that affect small amount of users. I mean the stuff that actually stops UT from being a usable daily driver.How This Works
Instead of just going through the bug tracker randomly, we're prioritizing based on impact. Two questions:What bugs stop people from switching to Ubuntu Touch?
What bugs make current users switch away?Simple as that. Real-world impact over everything else.
Priority Levels
Breaking bugs down into 5 categories:Priority 1: Core System Stuff - Boot loops, crashes, phone completely unusable. Fix immediately.
Priority 2: Basic Phone Features - Calls, SMS, WiFi, Bluetooth, notifications, camera. If these don't work, it's not really a phone.
Priority 3: Daily Use - Browser crashes, app store issues, keyboard problems, file management. The stuff you hit every day.
Priority 4: Polish - Like those tiny contact navigation arrows that are impossible to see. UI glitches. Things that make UT feel unpolished.
Priority 5: Nice to Have - Advanced features, edge cases, stuff that matters to specific users.
QtWebEngine Upgrade
This is a big one. The browser affects almost everything you do on a phone. We're planning to upgrade QtWebEngine, which should improve a ton of daily use cases.Finding the Bugs, We're looking at:
Forum posts, support tickets, social media complaints
Comparing UT to Android/iOS to see what's missing
Actually using UT as a daily driver (dogfooding)
TestingTimeline (really rough estimate)
Roughly 20 weeks broken into phases:
Weeks 1-2: Figure out what needs fixing and how bad it is
Weeks 3-10: Fix the critical stuff (Priority 1 & 2), start planning the QtWebEngine upgrade
Weeks 11-18: Fix daily use bugs (Priority 3), get QtWebEngine upgrade done
Weeks 19-20: Test everything, make sure we didn't break anythingWhat Success Looks Like
No critical bugs in stable releases
Phone features that just work
You can actually use UT daily without workarounds
People stop complaining about the same issues
UT becomes a real option vs Android/iOSNot shooting for perfection, just want UT to be solid enough that you'd recommend it to someone.
Need Your Help
This only works if the community gets involved:Tell us what's broken - What bug almost made you quit UT? What stops you from daily driving it?
Report bugs properly - Help us reproduce issues
Test fixes - Volunteer to test updates
Spread the word - Help gather more feedbackTracking Progress
We'll measure:Crash rate
Number of Priority 1-3 bugs
Boot time, battery life, app performance
Community feedback (less complains = winning)So What Do You Think?
What bugs are driving you nuts? What would it take for you to daily drive UT? Drop your thoughts below.
read more →@arubislander said: it is not the case for video codecs either indeed. This week-end I tried seriously to add ffmpeg codecs to my FP5 with 24.04-1.2 stable and basically succeeded, see https://gitlab.com/ubports/development/core/lomiri-messaging-app/-/issues/359#note_3122981838 So it is possible to play ALAC files with the existing UT applications (mediaplayer...). The fact that it is slower than when accelerated by the hardware is true of course, but a not too old processor like the FP5 one is powerful enough to handle simple video files without acceleration (did not try 4K though). -
Hi!
I have a problem with my Bluetooth helmet headset (Cardo Freecom 1+) using with VollaX23, it pairs fine and I am able to stream audio, but there is no sound or mic input when making calls. Unit works fine with android phone, also other bluetooth headsets work fine during calls.
Here is dbus log:
[21/06/2025 13:16] Setting up pulseaudio for voice call [21/06/2025 13:16] Recorded default sink: bluez_sink.00_0A_9B_7B_E0_F8.a2dp_sink default source: source.primary_input [21/06/2025 13:16] Found card that supports voicecall: 'droid_card.primary' [21/06/2025 13:16] 1 [21/06/2025 13:16] 2 [21/06/2025 13:16] 3 [21/06/2025 13:16] Found card that supports hsp and a2dp: 'bluez_card.00_0A_9B_7B_E0_F8' [21/06/2025 13:16] 3 [21/06/2025 13:16] Setting PulseAudio card 'bluez_card.00_0A_9B_7B_E0_F8' profile 'headset_head_unit' [21/06/2025 13:16] Setting PulseAudio default sink to 'sink.primary_output' [21/06/2025 13:16] Setting PulseAudio sink 'sink.primary_output' port 'output-bluetooth_sco' [21/06/2025 13:16] Setting PulseAudio source 'source.primary_input' port 'input-bluetooth_sco_headset' [21/06/2025 13:16] PulseAudio audio mode changed: 0x8 [21/06/2025 13:16] Setting PulseAudio source 'source.primary_input' muted '0' [21/06/2025 13:16] Notified about card (bluez_card.00_0A_9B_7B_E0_F8) changes event from PulseAudio [21/06/2025 13:16] Setting PulseAudio card 'droid_card.primary' profile 'voicecall' [21/06/2025 13:16] Setting PulseAudio default sink to 'sink.primary_output' [21/06/2025 13:16] Setting PulseAudio sink 'sink.primary_output' port 'output-bluetooth_sco' [21/06/2025 13:16] getContactAttributes (5) ("org.freedesktop.Telepathy.Connection.Interface.SimplePresence") [21/06/2025 13:16] oFonoConnection::inspectHandles contact (5) [21/06/2025 13:16] oFonoConnection::inspectHandles ("+xxxxxxxxxxxxx) [21/06/2025 13:16] getContactAttributes (12) ("org.freedesktop.Telepathy.Connection.Interface.SimplePresence") [21/06/2025 13:16] oFonoConnection::inspectHandles contact (12) [21/06/2025 13:16] oFonoConnection::inspectHandles ("xxxxxxxxxxxxx") [21/06/2025 13:16] getContactAttributes (6) ("org.freedesktop.Telepathy.Connection.Interface.SimplePresence") [21/06/2025 13:16] oFonoConnection::inspectHandles contact (6) [21/06/2025 13:16] oFonoConnection::inspectHandles ("xxxxxxxxxxxxx") [21/06/2025 13:16] getContactAttributes (10) ("org.freedesktop.Telepathy.Connection.Interface.SimplePresence") [21/06/2025 13:16] oFonoConnection::inspectHandles contact (10) [21/06/2025 13:16] oFonoConnection::inspectHandles ("xxxxxxxxxxxxx") [21/06/2025 13:16] getContactAttributes (11) ("org.freedesktop.Telepathy.Connection.Interface.SimplePresence") [21/06/2025 13:16] oFonoConnection::inspectHandles contact (11) [21/06/2025 13:16] oFonoConnection::inspectHandles ("xxxxxxxxxxxxx") [21/06/2025 13:16] getContactAttributes (8) ("org.freedesktop.Telepathy.Connection.Interface.SimplePresence") [21/06/2025 13:16] oFonoConnection::inspectHandles contact (8) [21/06/2025 13:16] oFonoConnection::inspectHandles ("xxxxxxxxxxxxx") [21/06/2025 13:16] Setting PulseAudio source 'source.primary_input' muted '0' [21/06/2025 13:16] Notified about card (droid_card.primary) changes event from PulseAudio [21/06/2025 13:16] Notifying card changes for the voicecall capable card [21/06/2025 13:16] Setting PulseAudio default sink to 'sink.primary_output' [21/06/2025 13:16] Setting PulseAudio source 'source.primary_input' muted '0' [21/06/2025 13:16] active [21/06/2025 13:17] disconnected [21/06/2025 13:17] onCallChannelClosed() [21/06/2025 13:17] call channel closed [21/06/2025 13:17] onCallChannelDestroyed() [21/06/2025 13:17] call channel closed for number "/ril_0/voicecall01" [21/06/2025 13:17] Setting PulseAudio source 'source.primary_input' muted '0' [21/06/2025 13:17] Restoring PulseAudio card 'droid_card.primary' to profile 'default' [21/06/2025 13:17] Setting PulseAudio default sink to 'sink.primary_output' [21/06/2025 13:17] Setting PulseAudio sink 'sink.primary_output' port 'output-speaker' [21/06/2025 13:17] Setting PulseAudio source 'source.primary_input' port 'input-builtin_mic' [21/06/2025 13:17] Restoring pulseaudio previous state [21/06/2025 13:17] Restoring PulseAudio card 'bluez_card.00_0A_9B_7B_E0_F8' to profile 'a2dp_sink' [21/06/2025 13:17] PulseAudio audio mode changed: 0x4 [21/06/2025 13:17] Restoring PulseAudio default sink to 'bluez_sink.00_0A_9B_7B_E0_F8.a2dp_sink' [21/06/2025 13:17] Restoring PulseAudio default source to 'source.primary_input' [21/06/2025 13:17] Notified about card (droid_card.primary) changes event from PulseAudio [21/06/2025 13:17] Notified about card (bluez_card.00_0A_9B_7B_E0_F8) changes event from PulseAudio [21/06/2025 13:17] Notified about card (bluez_card.00_0A_9B_7B_E0_F8) changes event from PulseAudioIt seems like to switch correctly to HSP and when receiving calls the headset sounds incoming call sound. But when call is answered there is no sound, I can switch to phone or even speaker and it works fine, only the headset seems to be muted during calls.
Pulseaudio log displays only
library "libsndcardparser.so" not found.Thanks in advance and any help is greatly appreciated.
Hi, I have a slightly different problem. Oneplus Nord N100 (UT 24.04-1.2 stable) with Nissan hands-free kit <MyCar>. Pairing works without any errors, but the screen shows that no network is available. This means that I cannot make or receive calls. image20260223_151514524.png[image: 1772400412224-9cd5c12b-0204-409c-a456-f4a635e3a255-image.jpeg] It seems that my hands-free kit cannot handle VoLTE, is that correct? With UT 20.04 OTA 9 / on the 3G network, it was possible to make calls using the hands-free system. Greetins Mario
