yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
I have tested on both

Global

&

LTE/CDMA

(both work... sometimes). I did a regular wipe in TWRP coming from stock before I installed the LOS builds.

---------- Post added at 06:46 PM ---------- Previous post was at 06:44 PM ----------

Correct. I had to give it some time to initialize the network from the setup wizard, but I didn't have to do anything else. VoLTE can be hit or miss though... right now I'm actually using the DTMF issues as an easy way to tell if VoLTE is working or not. DTMF works if VoLTE is broken, if DTMF is not working... that means I have data!
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Would the fastboot oem config fsg-id verizon command make any difference? Just trying to think out of the box. Sorry can't flash until later tonight to check.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
I thought that was to solve the phone not correctly recognizing the sim card. My phone works fine, SIM is recognized and everything works. Just not VoLTE.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Could you share your phone info tab from secret menu (with vitals removed)?
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Just curious: when you try using data while in a phone call, did you give it some time before attempting to use data? Normally, I would have issues right after the phone all was established, but once it'd been about 20 seconds, data would be back. I also was the one initiating every phone call.... not so sure receiving phone calls works at all over VoLTE
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
I tried waiting, initiating a call and receiving a call. No dice.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Just to be 100% sure, did you get the most current build? Maybe try building your own, using the most current trees from bhb and see if that makes a difference. Also, any further builds tonight will need to be done by you, I've got to get to bed, I have to be at work in 5 1/2 hours, lol

Happy Testing,

Nepo
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
The most current build is the only one that contains those RCS apps in /system/app, right? If so, then yes.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
So we've got one working and one not. Anyone care to break the tie?
[Verizon Motorola Droid Turbo Android Development] koftheworld:
I'll try. Did we bring in the volte config files from system/etc/diag_mdlog btw? Can't remember offhand or if they were required. I remember them being used on shamu.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
I'm not sure if we did or not, but it's working on TF's phone as-is.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
You can easily check this way Settings > About Phone > Build date should be Thu Apr 6 16:02:31

Also, just tried calling some #s, and it's definitely working. (Between radio crashes & com.android.phone crashes lol)

Fun fact though, on my phone VoLTE Provisioned is actually toggled off lol... attaching picture soon
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Yep, that's the one I installed. I noticed the same thing. I turned it on but no change.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
UPDATE: Okay, I've revived VoLTE!

-Steps I took

-During the setup wizard, tell it to use the cellular network (not sure if this is relevant, but I've had less issues when I did that)

-After that, you may not even have internet

-If that happens, go to the special secret phone menu *#*#4636#*#* click on the top right settings 'dots' and make sure the Data connection is Enabled

-Try making phone calls... if nothing is working, go to the phone app settings and try to open the IMS Settings.

-This will crash the app, and for some reason, after that, it will start working (temporarily)

-I've repeated this a few times and it's worked... let me know if you have any luck with it

-I have not been able to successfully receive a phone call via VoLTE--no matter what I try

-Lastly, it appears removing the IMS apps from system remove the VoLTE menu as its missing in the second picture below, so to me it would make sense to keep them, even though it crashes the phone app

Looks like I just did. I reset, and re-installed and broke it lol! I've got an x over my signal now... not working at all... I've got a theory though as to why it worked before... testing some things now.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
I wasn't able to get a volte signal unfortunately. I'll look tomorrow at the logs and the build to see what's going on.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
When doing a clean install, Cellular Data is off by default (the little "x" above the signal icon), it needs to be turned on in Settings
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Yup I ended up doing a reset of mobile settings and got data, but no volte.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Doesn't make sense that it only works for one person...

It should go without saying, but, all testing should be clean installs only, and no restoring of any apps, this will most certainly prevent conflicts.

My 2 Cents,

Nepo

PS, I still have no way to test, I'll try to get by a VZW retailer today and see what I can come up with :good:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
agreed and yes, that is what i did. i'm not sure why it didn't work for me yet. i was only able to test a little before i had to restore. [MENTION=5747496]bhb27[/MENTION] i made a new pull request for your ims blobs file on the volte2 branch. i added additional cfg files from stock that i also saw on the shamu side. is there any need for the vzw apn, ecid, and qualcomm apks/associated files to be included as well?
[Verizon Motorola Droid Turbo Android Development] fgl27:
If IMS settings has no effect and it is crashing when have IMS and IMS setting, try then just delete the setting one and see the overall effect, here that makes the ims extra config to disappears, and there is no crash...

what about using a different phone app for DTMF? does that help?

---------- Post added at 11:06 AM ---------- Previous post was at 11:03 AM ----------

I add those they seems to me extra loging, if they don't help on making things working they may on understanding way...

---------- Post added at 11:08 AM ---------- Previous post was at 11:06 AM ----------

Anyone else besides [MENTION=7838338]translucentfocus[/MENTION] manage to achieve success?

those not achieving success check the running service, use the kernel app log section to see it it has a shears option that can be used...

and produce some logs so we can cross check against working...
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Yes, I've been doing the default wiping in TWRP and then installing. One thing I did notice though is that after resetting & installing a second time, the VoLTE toggle that was off in other screenshots now stays on that both [MENTION=5901115]TheSt33v[/MENTION] and I had issues with. I believe it was probably due to me deleting the IMS stuff from system. Seems there's lots of ways for it to NOT work :)

---------- Post added at 03:14 PM ---------- Previous post was at 03:09 PM ----------

No, I tried the Google Phone App & Asus Phone App. DTMF didn't work on either.
[Verizon Motorola Droid Turbo Android Development] fgl27:
Ok I will do further checks on those..

let me know when you can, the behavior after removing the imssettings/ from vendor/app..

:good:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Great thanks for adding those (plus the others from before) in. Hopefully a new build will give us different results for those of us that didn't achieve success initially. [MENTION=7838338]translucentfocus[/MENTION] do you mind going through your steps for installation, setting up, and making sure that volte is working on the most recent build? i want to be sure i followed the same procedure.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Not at all; it was a standard procedure. Reset stock rom in TWRP. Install LOS with root and pico gapps. Boot up. Went through setup wizard and never enabled wifi; it hung for while configuring the radio, but eventually came through. Like [MENTION=7237874]NepoRood[/MENTION] said, make sure you enable data from the phone settings dial *#*#4636#*#* from the phone app (top-right menu button). BTW, VoLTE worked for me without even having to do an initial reboot.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Would this help? Here's two logs, one for

STOCK

VoLTE outgoing call right after boot, and me navigating a DTMF call. (I pressed lots of extra buttons in the phone app figuring that would send more DTMF codes. The other log is for an incoming VoLTE call :)
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Did you use flash the modem clear and newest radio files beforehand? what radio/boot package are you on? That's good to know re: reboot.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
I didn't do any of that. Baseband screenshot attached. (I'm on stock right now due to work/dumping logs)
[Verizon Motorola Droid Turbo Android Development] koftheworld:
i put in another pull request for 2 additional stock lte files that i found as i was browsing through the structure. let me know.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
maybe that is why i didn't have volte. i went from cf's 1.0.7, flashed the clear modem and newest radio, and then installed los. i'll have to try later today after work. hopefully we'll have a new build by then to test too. btw, thank you for submitting so many logs and testing along the way. it's help a lot.
[Verizon Motorola Droid Turbo Android Development] fgl27:
com.verizon.hardware.* are all present already they are common files, they are not volte only.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
oh ok didn't realize it. :) i'll hold off on proposing any more changes until after an updated build is run.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
New build is uploaded, get it Here

Also, [MENTION=5747496]bhb27[/MENTION], it threw me this error, around 52 seconds in

ninja: error: 'vendor/motorola/quark/proprietary/vendor/app/ims/lib/arm/libimscamera_jni.so', needed by '/media/nepo/common/LOS14.1/target/product/quark/system/app/ims/lib/arm/libimscamera_jni.so', missing and no known rule to make it

I moved the app/ims folder to vendor/app/ims, and build completed...
[Verizon Motorola Droid Turbo Android Development] koftheworld:
probably was my fault in one of my pulls sorry.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
No apology needed, lol. A PR has to be merged by the owner, just because you request, doesn't mean it was merged (that make sense?)

The culprit seems to be here

That path doesn't actually exist ;)
[Verizon Motorola Droid Turbo Android Development] koftheworld:
yup. on my end in stock it is located in system/vendor/app/ims/lib/arm and system/vendor/lib. thank you btw for the new build. i'll try it out tonight. [MENTION=5747496]bhb27[/MENTION] i made a pull request with changes to this call and one other that need to be in system/vendor.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Tried the latest build. Still no dice. I followed TF's instructions exactly. I'll upload logs in a few minutes.

Looks to me like the action starts at 16:52:39.132 in radio.txt.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
no volte here either. i'll take a look at the logs and see if what they say. apn settings don't seem right going in, but that shouldn't be a decider.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
you notice this gem?

16:53:05.811 E/GsmCdmaPhone( 4988): [GsmCdmaPhone] NullPointerExceptionjava.lang.NullPointerException: Attempt to invoke interface method 'boolean org.codeaurora.internal.IExtTelephony.isEmergencyNumber(java.lang.String)' on a null object reference
04-07 16:53:05.813 D/GsmCdmaPhone( 4988): [GsmCdmaPhone] imsUseEnabled=false, useImsForEmergency=false, useImsForUt=false, isUt=false, imsPhone=Handler (com.android.internal.telephony.imsphone.ImsPhone) {c3b3295}, [B]imsPhone.isVolteEnabled()=false[/B], imsPhone.isVowifiEnabled()=false, imsPhone.isVideoEnabled()=false, imsPhone.getServiceState().getState()=3, useImsPrefer=false
04-07
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Thanks! I tested it, and although it was much more difficult to get VoLTE to work thene previous builds (mainly because there is no IMS Settings I can use to crash the phone app which seemed to help restart things working), I did manage to make 1 outgoing call successfully and then browsed to several different websites. When VoLTE is working, incoming calls do not work at all as usual.

Update: Not sure if this is even relevant, but I can disable the 4G Voice toggle, yet the 'VoLTE Provisioned' toggle stays enabled... I'm guessing this is the way it is supposed to work, but just in case, I thought I'd add them

While I don't know what exactly got it to work for the 1 call I managed to make successfully, here are some of the things I did in no particular order that I recall:

-I had rebooted the phone

-Tried calls (phone wouldn't connect a call at all)

-Switched Preferred Network from Global to LTE/CDMA

-Enabled & disabled VoLTE in the *#4636#* menu

-Tried calls (phone still wouldn't connect a call at all)

-Enabled Data Roaming (I always do this because I figure it's one less thing that could get in the way... maybe this is one of the differences that is making mine work sometimes?)

-Enabled and disabled Airplane mode

-Eventually, I tried a call and it went through--to my surprise; I then kept the phone call going and proceeded to browse to many different websites

My apologies that I didn't do a better job of keeping track of exactly what I did... and I also didn't save logs from this test... I'll probably have to move back to stock for tomorrow as not being able to receive any calls at all is a problem for me. I'm going to try getting some logs of it working tonight, if possible ... but it takes me so long to get a successful VoLTE call sometimes after boot (jumping through hoops like above) that I'm afraid the logs may not be as useful.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
noticed some entries in your log like:

01-03 13:30:53.472 1833 1833 W SystemConfig: org.xmlpull.v1.XmlPullParserException: Unexpected start tag in /system/etc/permissions/qcom_ims.xml: found exceptions, expected 'permissions' or 'config'

01-03 13:30:54.166 1833 1833 W PackageManager: Library not found: /system/framework/rcsimssettings.jar

01-03 13:30:54.287 1833 1833 W PackageManager: Library not found: /system/framework/com.verizon.ims.jar

01-03 13:30:54.920 1833 1833 W PackageManager: Library not found: /system/framework/com.motorola.ims.rcsmanager.jar

01-03 13:30:57.517 1833 2043 W PackageManager: Failed to parse /system/app/ims: Missing base APK in /system/app/ims

01-03 13:30:58.511 1833 1833 W PackageManager: Failed to migrate com.qualcomm.qti.rcsimsbootstraputil: Failed to execute migrate_app_data [null, com.qualcomm.qti.rcsimsbootstraputil, 0, 2]: -1

Does this mean we are not pulling in everything that we need (such as those .jar files) from stock?
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
It would seem that way to me... the Moto X Pure has them on their latest build of Lineage OS... and VoLTE works.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Very interesting. So here's an idea: up until now we've been trying to decide which vendor files are necessary and adding them a few at a time. Why don't we just add all of them and see what happens? I find it hard to believe that Motorola said "let's just include a whole bunch of unnecessary files along with the important ones" when they were developing this phone.

Also, /system/app/ims is in our vendor tree. Are we not including it in the builds? If not, why not? My time is limited this weekend but I'll get on that if no one else beats me to it whenever I can find the time.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
where can I find said vendor files?

And yes, ims files from vendor are included
[Verizon Motorola Droid Turbo Android Development] fgl27:
I believed I have fix the build but had no try, anyway you guys must know how to local fix it is simple, I'm just trying to push the app libs to its folder that is on vendor/

keep pushing logs I will find time to cross check what works and what doesn't works.

clark only uses ims/ app noting else on that list, those seems to be related to moto frameworks no one else use, but I have deodex it all so is all in the vendor you guys just need to add them to the build process to test.

Theoretically they don't need special sign so is possible to just copy and post to the phone check permission 0644 of greater and reboot, search on the logs by the file name if they are gone they good if not try to build it...

in doubt let me know
[Verizon Motorola Droid Turbo Android Development] NepoRood:
New build is uploading, get it Here (If it's not there, give it a bit)

Looking for "VoLTE_3", I added the aforementioned "jar" files and corrected the ims apk path, I think, lol

Clean install, and grab logs :good:

[MENTION=2640499]koftheworld[/MENTION], I upload all test builds to the same folder, if you wanna clean up the OP :highfive:

https://www.androidfilehost.com/?w=files&flid=166122
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Still no success with this one. See logs. My plans for tonight dissolved, so I'm going to have a look at them now and see what I can find.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
No success for me either on this one. I'll take a look at your logs as well lol.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
interesting that it lists the phone as a gsmcdma phone in the radio log. can you do the fastboot command that i mentioned earlier in the thread?
[Verizon Motorola Droid Turbo Android Development] koftheworld:
still has this entry:

01-04 14:53:09.384 1719 1719 W PackageManager: Library not found: /system/framework/com.motorola.ims.rcsmanager.jar

01-04 14:53:09.461 1719 1719 W PackageManager: Library not found: /system/framework/rcsservice.jar
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Done. No change. See updated logs. I'm in the process of copying and pasting all the deodexed files from the latest stock to /system without overwriting any of the existing files. If it still says something is missing after that, it's wrong.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
make sure you fix the permissions and reboot after setting them. i'll take a look at your logs. try installing the myverizon app as well. it didn't work for me, but hey lol. also make sure you take the deodexed apks from [MENTION=5747496]bhb27[/MENTION] instead of just from a dump.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
list of prop. radio files that LOS for clark uses:

-app/ims/ims.apk

-app/MotoSignatureApp/MotoSignatureApp.apk:app/MotoSignatureApp/MotoSignatureApp.apk:PRESIGNED

-priv-app/atfwd/atfwd.apk

-priv-app/qcrilmsgtunnel/qcrilmsgtunnel.apk

bin/diag_klog

bin/diag_mdlog

bin/diag_mdlog-getlogs

bin/diag_mdlog-wrap

bin/diag_qshrink4_daemon

bin/port-bridge

bin/test_diag

bin/ipacm-diag

bin/netmgrd

bin/qmi_motext_hook

bin/qmuxd

bin/rfs_access

bin/rmt_storage

vendor/bin/qti

etc/diag_mdlog/Connection_Issues_V10.cfg

etc/diag_mdlog/Bluetooth_V1.cfg

etc/diag_mdlog/Bluetooth_audio_V1.cfg

etc/diag_mdlog/default.cfg

etc/diag_mdlog/default.opts

etc/diag_mdlog/FIT_V19_1.cfg

etc/diag_mdlog/FIT_V19_2_volte_full_ip.cfg

etc/diag_mdlog/FIT_V19_3_audio.cfg

etc/diag_mdlog/GNSS_OTDOA_V1.cfg

etc/diag_mdlog/GNSS_SUPL_V6.cfg

etc/diag_mdlog/GNSS_V5.cfg

etc/diag_mdlog/Vzw_Connection_Issues_V1.cfg

etc/diag_mdlog/WLAN_V1.cfg

etc/permissions/com.verizon.ims.xml

etc/permissions/ims.xml

etc/permissions/org.simalliance.openmobileapi.xml

etc/permissions/qcnvitems.xml

etc/permissions/qcrilhook.xml

framework/qcnvitems.jar

framework/qcrilhook.jar

framework/com.verizon.ims.jar

framework/org.simalliance.openmobileapi.jar

lib/libmdmcutback.so

lib64/libmdmcutback.so

lib/libmotext_inf.so

lib64/libmotext_inf.so

lib/libqmimotext.so

lib64/libqmimotext.so

lib64/libadropbox.so

vendor/lib/libimscamera_jni.so

vendor/lib64/libimscamera_jni.so

vendor/lib/libimsmedia_jni.so

vendor/lib64/libimsmedia_jni.so

vendor/lib/liblqe.so

vendor/lib64/liblqe.so

vendor/lib/libmdmdetect.so

vendor/lib64/libmdmdetect.so

vendor/lib/libnetmgr.so

vendor/lib64/libnetmgr.so

vendor/lib/libperipheral_client.so

vendor/lib64/libperipheral_client.so

vendor/lib/libril-qc-qmi-1.so

vendor/lib64/libril-qc-qmi-1.so

vendor/lib/libril-qcril-hook-oem.so

vendor/lib64/libril-qcril-hook-oem.so

vendor/lib/libxml.so

vendor/lib64/libxml.so

vendor/lib64/libqcmaputils.so
[Verizon Motorola Droid Turbo Android Development] koftheworld:
list of ims/hd voice prop. files for shamu:

-app/atfwd/atfwd.apk

-app/ims/ims.apk

lib/libimscamera_jni.so:app/ims/lib/arm/libimscamera_jni.so

lib/libimsmedia_jni.so:app/ims/lib/arm/libimsmedia_jni.so

bin/ATFWD-daemon

bin/imsdatadaemon

bin/imsqmidaemon

etc/permissions/com.verizon.hardware.telephony.ehrpd.xml

etc/permissions/com.verizon.hardware.telephony.lte.xml

etc/permissions/com.verizon.ims.xml

etc/permissions/rcsimssettings.xml

etc/permissions/rcsservice.xml

-framework/com.verizon.hardware.telephony.ehrpd.jar:PRESIGNED

-framework/com.verizon.hardware.telephony.lte.jar:PRESIGNED

-framework/com.verizon.ims.jar:PRESIGNED

-framework/rcsimssettings.jar:PRESIGNED

-framework/rcsservice.jar:PRESIGNED

lib/libimscamera_jni.so

lib/libimsmedia_jni.so

vendor/lib/lib-dplmedia.so

vendor/lib/lib-imsSDP.so

vendor/lib/lib-imsdpl.so

vendor/lib/lib-imsqimf.so

vendor/lib/lib-imsrcs.so

vendor/lib/lib-imss.so

vendor/lib/lib-imsvt.so

vendor/lib/lib-imsxml.so

vendor/lib/lib-rcsimssjni.so

vendor/lib/lib-rcsjni.so

vendor/lib/lib-rtpcommon.so

vendor/lib/lib-rtpcore.so

vendor/lib/lib-rtpdaemoninterface.so

vendor/lib/lib-rtpsl.so

vendor/lib/libvcel.so