@szocse1223 Very good then!
So I guess there are good chances that the fix lands also for Curtana on the next OTA-5 update (I'm on stable channel).
Will let you know...
@szocse1223 Very good then!
So I guess there are good chances that the fix lands also for Curtana on the next OTA-5 update (I'm on stable channel).
Will let you know...
@szocse1223 Oh nice. What did you do? Are you on "dev" channel?
@beyolf Thank you very much!
I don't know if you've had a chance to take a look at these logs?
Meanwhile, a member of the Telegram group "The UT for Miatoll Group" informed me that a developer from Spain was able to fix the problem on the Note 9 Pro (Joyeuse).
The vibrator would already work on the "Dev" channel, so possibly the problem would also be fixed on the Curtana after the next OTA update?
In the meantime I've created the following ticket on Gitlab:
Thanks and have a nice day.
@Tripluradon Indee, as @AppLee said, the development team is very small and has a lot to do.. VoLTE is such a crazy thing to work on.
I'm not in, so I can't tell you further. In general, there is no timetable for deployment within the teams. Things comme "when ready".
If you live in North America, I can strongly recommend this Telegram group: (search for)
UBports [North America Carrier Issues]
Users exchange ideas and workarounds, like third SIP providers for example. But no magic wand for now.
Regards.
@AmauryDBZ Here on this website.
Or... there are also Telegram groups in many languages (check "UBports" in Telegram)
Also you can subscribe to the UBports newsletter here:
https://ubports.com
UBports is also on all social medias.
There are topics dedicated to Ubuntu Touch on many Linux forum sites.
So when the news will be published it won't go unnoticed...
@thomasM At the time VoLTE and VoWiFi (WiFi calling) are still not implemented in Ubuntu Touch, although major efforts have been made in recent months / weeks.
This is mainly due to the fact that these technologies use closed hardware source code that is very complex to unravel.
You should continue to follow the various forums and news feeds on the Internet and Telegram on this subject.
@kuailexs I guess some exciting announcements will happen next Saturday, at least about VoLTE and 5G support on Fairphone 5 (but seems to be possibly applied to a range of modern Qualcomm chipsets):
@Moem Indeed, the title is confusing... GS4 is definitely unsupported by UBports.
@stonee The Gigaset GS290 doesn't have the same digital signature as the Volla Phone, although the hardware itself is the same.
Maybe try installing /e/OS to get it working again:
https://doc.e.foundation/devices/GS290/install
I doubt Ubuntu Touch would be easy to install on it.
Some people have managed to do this by modifying lines of code in the root of the device, but that's beyond my skills...
@beyolf I finally managed to generate the logs you asked for (I hope I did the right thing, my computer skills being limited...)
The command I used was:
journalctl -u repowerd --since 20:30
I rebooted the device just before in order to display the repowerd boot logs.
I hope this helps you in your investigations.
Thank you beforehand if you can take a look
01 20:54:17 ubuntu-phablet systemd[1]: Starting monitor and control system power state...
avril 01 20:54:17 ubuntu-phablet repowerd[1465]: main: Starting repowerd 2023.07
avril 01 20:54:54 ubuntu-phablet repowerd[1465]: DefaultDaemonConfig: Failed to create LibsuspendSystemPower>
avril 01 20:54:54 ubuntu-phablet repowerd[1465]: DefaultDaemonConfig: Trying LogindSystemPowerControl
avril 01 20:54:54 ubuntu-phablet systemd[1]: Started monitor and control system power state.
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:54 ubuntu-phablet repowerd[1465]: DefaultDaemonConfig: Trying LogindSystemPowerControl
avril 01 20:54:54 ubuntu-phablet systemd[1]: Started monitor and control system power state.
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: BinderPerformanceBooster: enable_interactive_mode()
avril 01 20:54:54 ubuntu-phablet repowerd[1465]: DefaultDaemonConfig: Failed to create LibsuspendSystemPower>
avril 01 20:54:54 ubuntu-phablet repowerd[1465]: DefaultDaemonConfig: Trying LogindSystemPowerControl
avril 01 20:54:54 ubuntu-phablet systemd[1]: Started monitor and control system power state.
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: BinderPerformanceBooster: enable_interactive_mode()
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:59 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:59 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:55:05 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:54 ubuntu-phablet systemd[1]: Started monitor and control system power state.
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: BinderPerformanceBooster: enable_interactive_mode()
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:59 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:59 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:55:05 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:55:09 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:55:15 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:55:19 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:55:59 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:56:01 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 20:58:09 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:58:10 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:00:15 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:00:20 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
lines 6-22/31 71%
avril 01 21:02:56 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:02:57 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:03:00 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:03:00 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:03:13 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 21:03:15 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 21:03:31 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 21:05:20 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:05:25 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:06:23 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 21:06:35 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 21:06:36 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 21:07:34 ubuntu-phablet repowerd[1465]: BinderPerformanceBooster: disable_interactive_mode()
avril 01 21:07:36 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:07:51 ubuntu-phablet repowerd[1465]: BinderPerformanceBooster: enable_interactive_mode()
avril 01 21:07:52 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
@beyolf I confirm the same issue on Redmi Note 9S. Everything works well except vibrating.
Will try to get the logs tonight.
Edit: Is there a way to filter repowerd outputs on journalctl ? Cause there are hundreds lines available....
Thank you !
We've often talked about the development of IMS services here (VoLTE - VoWiFi, etc.) and the difficulty of implementing them because of vendor blobs.
But it's been a while since we've talked about the project to activate voice/video calls in the Teleports app.
Would this possibility be "easier" and "quicker" to implement until VoLTE arrives?
This would make it easier for users to make voice calls in North America (e.g. Teleports for Telegram contacts, possibly WhatSapp via WayDroid for other people?).
Thank you!
@Vulpex I'm sorry, I still don't quite understand the problem...
It's the same principle as on Android: If you don't want your phone to activate 5G, you select the "2G, 3G, 4G-LTE" band.
This will permanently disable 5G.
@Vulpex Oh ok, so that's easy.:
You can just change de connection type in the network settings (3G, 4G, etc...)
@Vulpex Enabling 5G NR in Ubuntu Touch is already in the UBports Roadmap. It won't necessarily be a Big Deal, but it's not the priority either, since to date only a handful of devices are 5G compatible.
I think the bigest challenge for developers is to implement IMS services (VoLTE / VoWiFi / Voice calls in messaging apps / etc..) on as many devices as possible. This is very complicated to do, as this technology depends largely on vendor blobs with proprietary source code.
Perhaps Fairphones, Volla phones range, and possibly Pixels (whose device tree is partially published by Google) will be the first to benefit (?)
Another major project is currently underway: Ubuntu Touch's move to the Ubuntu 24.04 Noble Numbat repositories.
Hello,
Just to say that I've finished today all the missing French translations for all the above channels (on Weblate).
All reviews, checks, suggestions and unfinished strings have been successfully finalized.
Don't hesitate to contact me if you need further hand with this
@MrT10001 We can also add OnePlus Nord N10 5G and OnePlus Nord N100?
@MrT10001 Awesome! And seem 100% functional under UT! Congrats!
@ikoz I would dream of a kinda "Android Auto" fork so I could use and mirror PureNav and Teleports on my car's infotainment.
More seriously, a WiFi printing app would be great (there was one in the OpenStore, but only prints blank sheets).
Without wishing to get involved in this intractable debate, I think it's difficult for us to rate the work of developers, whatever their position, on the basis of their public appearances.
Most people in the community work behind the scenes. Some exchange more frequently on the Telegram Dev channel, others less. Some slow down, then get back more actively.
Some leave, others join... Thus I guess it's hard to get a snapshot of our most deserving members.
As AppLee rightly points out, the UBports Foundation - in accordance with its articles of association - is officially entrusted with the task of managing resources as best it can according to the needs of the project at hand. Elected members of the UBports Foundation Board of Directors are its auditors.