Your device needs to run current development version “Droidian 102” and you should be familiar with apt.
Add this two repos to apt:
deb http://droidian.g.droidian.org/next-upgrade-gbinder/ trixie main
deb http://droidian-ofono-binder-plugin-ext-qti.repo.droidian.org/next-aidl/ trixie main
Then sudo apt update && sudo apt upgrade, this should update some libgbinder and ofono packages.
Reboot and confirm that calls/sms/data still works.
MTK: sudo apt install ofono-binder-plugin-ext-mtk
For qcom there are two implementations HIDL or AIDL available. Only known to me qcom device with AIDL and running Droidian is ThinkPhone.
Now create a config file in /etc/ofono/binder.d/, here is an example used for bronco
MTK devices need to set extPlugin = mtk in that file.
Reboot. You can try calling and see if data still drops to 3G or run gdbus call --system --dest org.ofono --object-path /ril_0 --method org.ofono.IpMultimediaSystem.GetProperties
If it works, you should see this: ({'Registered': <true>, 'Registration': <'auto'>, 'VoiceCapable': <true>, 'SmsCapable': <true>},)
It works fine so far, but no signal strength is displayed, even with 4G. In my city, where 5G is available, it connected automatically, but when I left, the display remained on 5G even though no signal was possible until I restarted the device.
Yes, I know about the signal strength, will fix it. Don’t have the issue with switching back to 4G. Will see what we can do about that. Thanks for testing!
Also, does your carrier support VoLTE? If so, does it work?
On Vodafone Romania, it all seems to work. I have 5G and can use VoLTE, which I know because it doesn’t have a tone (it connects straight to the other party, without tone). Probably on VoLTE there’s actually no tone and other phones fake it?
Yeah, same here. No dial tone. Also one issue I noticed, when I go into my basement and no cell there. So once Im back up and have cell, VoLTE wont register until I reboot. Will look into that.
This thread mentions the device needs to run Droidian 102. It’s also my understanding that it likely can’t work on a device ported from Halium 9. Could you clarify what min (or max) Halium version the ported device should be based on in order for this to be likely to work?
I can’t easily buy American or European phone models (ThinkPhone, Volla, OnePlus), but I can probably easily get my hands on used Redmi or Sony phones. Any recommendation?
I dont know if there is a halium version restriction. But yes, you need droidian 102 to be able to install the packages. You can just follow the guide, worst case 5G/VoLTE does not work. But should still function as before with 4G and 3G calls.
Firstly thanks to all the people working on this project.
I have a thinkphone and followed your instructions, android 14 and then droidian 102 as above. VOLTE working normally, voice calls, data, and receiving SMS. All functions worked on standard android 14.
Sending SMS does not work, it states sent on chatty but never receive on other device.
If I change sim to my pinephone on mobian, all works as expected. So one final hurdle before switching.
VoLTE cannnot work on POCO F5 (QCOM 7+ gen2),but 5G is work sometimes,The 5G signal is unstable, and most of the time it falls back to the 4G signal,I cannot keep 5G always.
I flash Droidian 102,test HIDL and AIDL,I get this:
I can use mobile network ,receive or send texts,only VoLTE is broken,I am sure the Carrier support VoLTE and my sim is support it,My android device can keep 5G and VoLTE anytime.in fact, the place where I am only 4G and 5G/5G-A network, have no 2G or 3G,so if VoLTE is not work, I cannot make or receive any calls.
Reinstalled A13 and 101, you are right SMS did not work proper, unable to receive or send texts.
Installed A13 and upgraded it to A14, then installed base next level, 102, and SMS work both ways but need to put in country code and make sure 4G is selected in gnome settings. Receiving volte call worked with 4G but could not call on Volte from phone.
Then did as top of the thread and added the two repos along with other instructions, the bronco comes with an already installed conf file same as the one you mention. Now volte works both ways and able to receive sms, but now unable to send sms, well can send on chatty and says sent but never received on recipient device
Just to test things out installed A15 and the next level, upgraded as above, same behaviour
Hmm, actually I had issues with incoming sms with initial port. Have /usr/share/ofono/scripts/monitor-ofono running in terminal.
Then sent the sms and check if ofono reports as sent or is it stuck in pending?
Did the carrier shutdown 3G? If not, there is something else you could test.
Add -d to ExecStart: ExecStart=/usr/sbin/ofonod -d --nodetach
Reboot and check logs when sending SMS with sudo journalctl -f | grep ofono might see where it fails. Don’t just share the logs, there might be some information you should not share
Hi,Thank you for your reply. I cannot determine whether the IMS service is enabled or disabled, because I could not find the corresponding switch in my Droidian system. I have no other way to determine.I tried entering `sudo logcat | grep ims` and received the following output:
droidian@drnf:~$ sudo logcat | grep ims
[sudo] password for droidian:
04-18 21:41:10.095 22722 22722 I init : Parsing file /vendor/etc/init/ims_rtp_daemon.rc…
04-18 21:41:10.095 22722 22722 E init : /vendor/etc/init/ims_rtp_daemon.rc: 7: service ‘vendor.ims_rtp_daemon’ overrides another service across the treble boundary.
04-18 21:41:10.095 22722 22722 I init : Parsing file /vendor/etc/init/imsdaemon.rc…
04-18 21:41:19.181 22722 22722 I init : starting service ‘vendor.vsimservice’…
04-18 21:41:22.668 42 42 I servicemanager: Found vendor.qti.hardware.radio.ims.IImsRadio/imsradio1 in device VINTF manifest.
04-18 21:41:22.683 42 42 I servicemanager: Found vendor.qti.hardware.radio.ims.IImsRadio/imsradio0 in device VINTF manifest.
I found a 2G network in another place and can make calls normally.I am sorry, I am not a professional.
Yes,I use this port, How do I operate to enable IMS? Modifying the imsdaemon.rc file doesn’t seem to be working.. ‘service vendor.imsdaemon /vendor/bin/imsdaemon_HALIUM_DISABLED’ revised to ‘service vendor.msdaemon /vendor/bin/imsdaemon’. and the system is broken
