yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Does that apk have a dependency that we didn't set to move, wasn't deodexed, etc.? Might need the apk lol
[Verizon Motorola Droid Turbo Android Development] fgl27:
The key here is understand what in hell is making it stop after one call, and for that no new app bin or wherever from stock is need, so no more adding and more loging in a way that can pinpoint the exactly point in the log were:

the call finish...

something happens that breaks volte

and produce a very precise log of before and after, that only how has volte can do, I know good logs are already in the tread I did not had the time to read any, as those are not simple to read and as I can't produce it make more hard on me to pinpoint exactly moments in the logs were things are happening, so descriptions like [MENTION=7838338]translucentfocus[/MENTION] and other have be doing helps a lot...

I probably will do some reading and some updates on things that may help, and released some updates this week, in the mean time lets try to understand what I just wrote, the moments were the fails start try to understand from were those logs are from and go trow the source files find the reason of the logs and things turning off...

:good:
[Verizon Motorola Droid Turbo Android Development] NepoRood:
VoLTE_6B

New build, uploading Here.

Don't know if it works, but at least this one makes it through setup :good:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Same error as before.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
that's weird, mine setup just fine, without any errors :confused:

Did you get 6A or 6B? (Cause I'd uploaded 6A prior to my post, but it too was derped and I deleted it from AFH)
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
I think you're on to something with this. In a previous log of mine, we saw this:

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}, imsPhone.isVolteEnabled()=false, imsPhone.isVowifiEnabled()=false, imsPhone.isVideoEnabled()=false, imsPhone.getServiceState().getState()=3, useImsPrefer=false

I opened up GsmCdmaPhone.jar and had a look. The function that causes the null pointer exception is isEmergencyNumber, which is designed to take the string inputted by the user during dialing and determine whether or not it's 911 or a similar emergency number. If that's causing a null pointer exception, that means that the number dialed by the user is not being assigned to dialString like it should be (which makes dialString null and causes the null pointer exception in GsmCdmaPhone.jar). Why this is happening, and why this causes everything else in GsmCdmaPhone.jar to stop working, I'm not sure. I'll have to stare at it more later because some of what determines the output of imsUseEnabled and the other fields that come after it is pretty complicated, but if there's a single condition that's causing all of them to fail, that would be helpful.
[Verizon Motorola Droid Turbo Android Development] fgl27:
that doesn't help much, general log from KA do because they are the logs generate by the ims/telephone/ weever system is running and producing logs, and regular log may tell what volte flag or wherever related is disable after one call knowing it we can force it on , that things are stooping we know the only way to get the reason is trow normal logcat and it associations + dmesg and getprop.

if you tell me that one of this is stopping working after first call

ims_rtp_daemon, imscmservice, imsdatadaemon and imsqmidaemon

using getprop that is a great help and good to know

config-rcs-on is a one time deal service, it runs once and that its, the "on" means it enable things, the config-rcs-off mean that it disable things, so if get prop show that config-rcs-off is stopped that means it run and that may be a cause and in logcat you will find "rcs_config_off run"...

those are good thing to know, I will take a long look at logs already produce, but I need to finish some personal things here and they are time demanding, so I let the thread know what I find when I find if some one find something new let me know, try to understand my post to see if that helps...

:good:
[Verizon Motorola Droid Turbo Android Development] johnjingle:
With the latest build 6b, I keep getting the error:

com.motorola.service.ims.RcsServiceApp has stopped

I close the app and it pops up over and over.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Weird, it went straight through setup for me, never popped up once...
[Verizon Motorola Droid Turbo Android Development] fgl27:
wiping system before flash?

check if system/app/RcsService/RcsService.apk exist in yours out folder just to be shore you are no building it... use search on the system/ folder just to be shore RcsService doesn't exist in side system/ in out/ folder...

some times I have some odd files that keep bugging me from older build that is way I always wipe system even on dirty flash...

:good:
[Verizon Motorola Droid Turbo Android Development] johnjingle:
I always wipe everything, but internal storage and USB OTG.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Same thing that happened to me with it. I haven't tried again yet.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
VoLTE_X

New and most likely final build is up, get it Here

With clean install (TWRP factory reset) Setup went though without a hitch, I didn't have any errors.

I had to dial the "Advanced Phone Menu" (*#*#4636#*#*) and turn on VoLTE Provisioning. This auto enabled Enhanced 4G LTE Mode in Settings/More/Cellular networks, also, while you're here, be sure to go into Access Point Names, and choose VZWIMS (I noticed in someones logs, that this wasn't set ;))

Happy Testing,

Nepo

PS, in my "Out/" folder, under System/App there wasn't anything "rcs" related :good:

Well, to the "rcsservice" app, anyway
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Why do you say final build? Stock apn settings attached btw for reference.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
I said: Most likely final, and I meant for now (I been putting out like one or more a day, lol)

I say that because, as bhb said, it's working once, we need to figure out why it's turning off, by going over the logs. Once we narrow down the reason, the fixes will be implemented, and we'll go from there...
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
What sources did you use to build VoLTE_5 (or the most recent test if the issues from the previous 2 were sorted out. I haven't tried them)? Do you have repos for that up somewhere, or is it all local? I'd like to try some crazy things starting off from a build that partially works.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
I'm not sure if this is helpful, but here is a get.prop comparison between stock and the latest [MENTION=7237874]NepoRood[/MENTION] LOS version. there are many differences between the two, so I wonder if we are in need of changing/adding a few values. verizon is all about device identification, so i wonder if it is not seeing the device as a xt1254.

open the file in Word. lines in black are the same across builds. red text is in LOS, but not in stock. red text marked through is in stock but not in LOS.

just to expand on the verizon identification info, verizon only lets certain devices use their network. a lot of devices with the correct bands can get data only LTE, but no voice service. i wonder if something about the build.prop and/or other files identify our device as something other than a xt1254.

that being said, once i sucessfully use volte on the newest LOS, I can't use the radio at all until i reset it through airplane mode. i can't even make a regular call.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Everything is up on git, I just need to push recent local changes to vendor. For everything else, I use straight LOS 14.1 (minus some mundane apps, like MusicFX), and bhb device and vendor (volte_2) branches.

If you're "experimenting", you may wanna fork his device and my vendor (github.com/roodbuild) I'll make a commit when I come home for "lunch" later this morning.

EDIT:

I've pushed my commit, I also pinned the vendor repo I'm using (device is just for reference), link
[Verizon Motorola Droid Turbo Android Development] newbe1droidx:
Thanks for doing all this work on Volte, it will really help me out in my low to no signal home area. This include WiFi calling?
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
All of our testing has been centered around VoLTE over the Verizon network (SIM card-based). I don't know if once we get it working completely (right now all we can manage is one outgoing-no incoming-call before crashes) WiFi VoLTE will "just work" or not. Someone else with more knowledge may be able to answer that question more effectively. I was actually going to ask if trying to get VoLTE working over WiFi first might be easier... but never did.

---------- Post added at 04:20 PM ---------- Previous post was at 04:14 PM ----------

Not sure if your theory is correct or not... but wouldn't that mean the phone app would never even try to call the number you enter? Because currently, the phone app successfully "tries" to call, but it just sits there saying 'Calling'.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
It's not. I made a build where I replaced the variable in question with a constant string. No more null pointer exception, but no change to volte performance.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Update: Compared LOS build to Stock getprop... and here are some of the differences I found. (full logs attached)

STOCK: [persist.radio.VT_USE_MDM_TIME]: [1] LOS: [persist.radio.0x9e_not_callname]: [0]
lines missing from LOS build:
[persist.radio.0x9e_not_callname]: [1] LOS: missing
[persist.radio.call_type]: [1]
[persist.radio.mode_pref_nv10]: [1]
[persist.radio.mot_ecc_custid]: [common]
[persist.radio.mot_ecc_enabled]: [1]
[ril.ims.supported_services]: [33039]
[ro.hw.device]: [quark]
[ro.hw.hwrev]: [0x84A0]
[ro.hw.radio]: [0x4]

Thank you for all the extra help [MENTION=5747496]bhb27[/MENTION]. I ran getprop before and after a phone call & the only difference is that [persist.radio.cdma.msgid]: [34] is counting upwards--which seems to be normal. Example: I ran getprop a few more times (no more phone calls) and now it's [persist.radio.cdma.msgid]: [37]
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Uhhggg. I can't get VoLTE to work at all on VoLTE X. Does anyone have a copy of VoLTE 5 they can send me?
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
I've got it. link.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Currently out of town, when I get home I'll see what I can come up with for a new build.

It'll most likely be tomorrow though...
[Verizon Motorola Droid Turbo Android Development] johnjingle:
You sure work hard for something you can't even use with your own phone!! I and many others applaud your effort.

Happy Easter!!!
[Verizon Motorola Droid Turbo Android Development] kitcostantino:
Amen! that has always been my thought. we are so lucky to have [MENTION=5747496]bhb27[/MENTION] !!!
[Verizon Motorola Droid Turbo Android Development] NepoRood:
VoLTE_X1

Download

Guys, give this one a test please, and see if we can at least get back to one working call...

Thanks,

Nepo
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Thanks nepo! FYI I was able to get 1 call at a time on the last build. Any substantial changes on this one?
[Verizon Motorola Droid Turbo Android Development] NepoRood:
[MENTION=5901115]TheSt33v[/MENTION] said he couldn't get it to work (VoLTE_X), so I thought I had over added some packages and broke the functionality :o
[Verizon Motorola Droid Turbo Android Development] koftheworld:
FYI volte commits for Griffin https://github.com/LineageOS/androi...mmit/4f74d23690dfae36fc7ddf6e76048283967acf82
[Verizon Motorola Droid Turbo Android Development] koftheworld:
vendor

Additional Griffin commits https://github.com/boulzordev/andro...mmit/25a8ad21fef18f641c8d3e36fc4c07238545c5b3

griffin vendor file is here https://github.com/boulzordev/proprietary_vendor_motorola_griffin
[Verizon Motorola Droid Turbo Android Development] koftheworld:
[MENTION=5747496]bhb27[/MENTION] I was taking a look at the stock kernel and noticed some volte related entries. Anything that you didn't port over to yours? Any chance to look at our logs?
[Verizon Motorola Droid Turbo Android Development] fgl27:
what volte related on the kernel? show me

there is too much confusing on this tread, too many deferents build no new build seems to address any fix so they do noting else or bring new bugs, so is hard to fallow a project like this, produce random logs from random build changes...

so stop making build and changes let me have some time to see a very old log that was made on the base branch that I did and had volte working, I know working only once but that is the base I wanna to fallow and fix wherever the logs was telling without making random changes...
[Verizon Motorola Droid Turbo Android Development] koftheworld:
i'm sorry if the thread is confusing. it was moving very fast initially, but has slowed down a lot now that our initial ideas have been tried. the new builds that were made all had additional ims/volte files added in from the stock side, but very little other changes were made. would it be better if the changes that [MENTION=7237874]NepoRood[/MENTION] made were submitted as pull requests to your github instead of a fork on his own? i'd like to make this effort as centralized and as easy to follow as possible.

you had verizon volte working on one of your builds? i was involved with your initial patches for it, but i don't remember one that worked. i know you had success in getting the correct menus to appear, but i don't recall volte working.

would it be helpful for me to repost the stock logs that are in this thread into the OP as well as logs for the most recent nepo build?

the kernel references i saw were in this tree although i did see motos response to you here which to me means you have it all covered.

what do you think about my theory regarding the identification of the device? would it be possible to have a build made that identifies the device as the xt1254 as it does on stock?

btw i see what you mean re: init.mmi.volte.rc and rcs_config.sh. we have the files that are referenced in the rc file and the setprops i think i've seen in our log files...
[Verizon Motorola Droid Turbo Android Development] fgl27:
the idea to make things more easy to understand regarding logs, for me is, grab all the logs and put them on the OP separated with reference, from what ROM they are from, and preferable change the file name to resemble it, like log_stock.zip and log_buildXX_date.zip... this wy is more easy to go back and for with the logs as the way it is I lost my self, I'm looking to some old logs base on the changes I made and making proper fix to it so we can see if that has a result, I will make tow separated build and released later or whenever I manage to make what I wanna to work...

I'm making changes to the source and rebasing some changes base on others device to see the end result and if some logs error disappears...

the kernel has all necessary things enable noting to add or remove, if you guys think a kernel can make a difference, use my custom for test, after all I never see anyone complain about problems with Volte running on it...

the kernel is not loading the init.mmi.volte.rc before flash it need to edit the file /patch/custom/init.qcom.rc removing the # on the line 30

if all latest changes did not cause any difference on the result, noting that was add or remove from nepo build make a positivity result so there is no need to make pull or use those, after all we need fix the problem without introduce new one and adding files may cause new problems and prevent from getting the real fix for the problem that is lost of volte after one success in a volte call.

so I keep making changes to see the end result and release (tell you guys to use it or share a build) whenever I fell they are ready to be used.
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
To clarify... you are saying your standalone [MENTION=5747496]bhb27[/MENTION] kernel can be installed even on Verizon stock-based [MENTION=6076132]computerfreek274[/MENTION] ROM or pure untouched Verizon firmware and Verizon VoLTE still works?

I'm not doubting it if you say so, but I'm not sure that's ever been stated before.

I knew your kernel works with stock XT1225 firmware, but it doesn't have VoLTE.
[Verizon Motorola Droid Turbo Android Development] johnjingle:
I just installed BHB27-Kernel-V47.zip out of curiosity and VoLTE does work on CF's 1.07 ROM. I made multiple testing phone calls with WiFi off and cellular data worked flawlessly.

I'm going to keep using the kernel and see how the battery life is compared to stock kernel, but that's another topic for the CF ROM thread.
[Verizon Motorola Droid Turbo Android Development] fgl27:
I made a volte test ROM and kernel

https://www.androidfilehost.com/?w=files&flid=173325

The kernel I made so you guys can control and test different scenarios like this

inside of /ramdisk/custom/ there the init file init.mmi.volte.rc that load all other volte related ini and services, in that zip it will run just fine no need to mod the main .rc init.qcom.rc

in line 62 we have

on property:sys.ims.DATA_DAEMON_STATUS=1
start ims_rtp_daemon
start imscmservice
start config-rcs-on

in others device there is no need to run all those service, so removing the start service_name will prevent it from be ever started and one of those may be the reason of the fail, config-rcs-on seems to be really needed, but the others may be disable

so the test to do here is mod that file removing the services

start ims_rtp_daemon
start imscmservice

Clean install the ROM and flash the mod kernel zip before rebooting, test test and test logs logs and log etc etc :D, and run the other two option with only one of those + config-rcs-on and see the behavior... every option is need to clean install to make shore is all clean and use the command in terminal

getprop | grep ims

to see what is running regarding the ims services...

have fun:good:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
thank you so much for this. i'm going to test this tonight. for reference for everyone else, this is the code from the stock init.mmi.volte.rc file in the latest OTA:

service imsqmidaemon /system/bin/imsqmidaemon
class main
user system
socket ims_qmid stream 0660 system radio
group radio net_raw log qcom_diag

# imsdatadaemon starts with root and UID will be downgraded to SYSTEM.
service imsdatadaemon /system/bin/imsdatadaemon
class main
user system
socket ims_datad stream 0660 system radio
group system wifi radio inet net_raw log qcom_diag net_admin
disabled

on property:sys.ims.QMI_DAEMON_STATUS=1
start imsdatadaemon

service ims_rtp_daemon /system/bin/ims_rtp_daemon
class main
user system
socket ims_rtpd stream 0660 system radio
group radio net_raw diag qcom_diag log inet
disabled

on property:sys.ims.DATA_DAEMON_STATUS=1
start ims_rtp_daemon

# Config volte related prioperties
service config-rcs-on /system/bin/sh /system/bin/rcs_config.sh on
user root
oneshot
disabled

service config-rcs-off /system/bin/sh /system/bin/rcs_config.sh off
user root
oneshot
disabled

service cnd /system/bin/cnd
class late_start
socket cnd stream 660 root inet

on property:sys.ims.rcs=1
start config-rcs-on

on property:sys.ims.rcs=0
start config-rcs-off
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Your rom with no changes pictures attached. No volte at all.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
I own both a XT1250 & a XT1254. The XT1250 on Verizon (Moto Maxx) and Verizon's System does not recognize it as a Droid Turbo. VoLTE and everything else still works fine... with all the ROMs & logs & testing I've done both on the XT1250 I have and on my XT1254-- I've yet to see any differences between my XT1250 and a "real" XT1254. Hope this info helps somebody.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Yes but the xt1250 is an allowable phone. If you tried a phone with the right bands that wasn't approved, then you wouldn't get volte.
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
XT1250 and XT1254 are identical in every way, including FCC ID. Maybe something like that is the identifier? Not the "model name" or number, but the FCC ID? Did the Nexus 6 sold by Google and the Nexus 6 sold by Verizon have the same FCC ID? Because I know a non-Verizon Nexus 6 ran on Verizon just fine, including VoLTE.

ZTE AXON 7. It has the right bands, didn't get Verizon VoLTE with Marshmallow (just like you are saying), but now on Nougat DOES get Verizon VoLTE.

While it's an interesting theory, the identifier -- how does ZTE Axon 7 not even sold by Verizon then become an "allowable" phone? And whatever that property is, it's passed on to LOS 14.1.

It (whatever "it" is) was NOT there in ZTE stock Marshmallow for the Axon 7. People were using the phone on Verizon but complained about no VoLTE. Join the club! :rolleyes: Then, Nougat was released by ZTE, SOMETHING suddenly made VoLTE work on the NON-Verizon ZTE Axon 7. Then, on custom ROM LOS 14.1 -- which is NOT stock-based -- Verizon VoLTE still works.

Very strange. WHAT is it that now allows ZTE Axon 7 to have Verizon VoLTE and what is it that the LOS 14.1 for the ZTE Axon 7 has allows Verizon VoLTE? The only two things I can come up with is something in the kernel code and something in the modem. Because really there's nothing else stock Marshmallow and custom ROM LOS 14.1 share, you know? LOS 14.1 is not like CF's debloated stock based ROM.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
It's only​in recent years that this has happened. I think the turbo might predate this policy change.
[Verizon Motorola Droid Turbo Android Development] johnjingle:
[MENTION=3250376]ChazzMatt[/MENTION]

We may be on different wavelengths here, but I installed bhb27's kernel on CF's ROM and VoLTE still worked, battery life just suffered, so I do not think it is a kernel issue.

Anyone, please correct me if I am wrong or ignorant.

Also, is the stock Marshmallow kernel able to be ported/used on Nougat ROM's? Just curious.
[Verizon Motorola Droid Turbo Android Development] RL_Wells:
I have the xt1250 on Verizon and have had no noticeable connection issues with volte on cf's rom on both lollipop and marshmallow, once installed. I have never installed a stock firmware from Verizon.

One additional step I had to take to make cf's marshmallow version work after installation was to re-flash the boot.img file extracted from his radio/bl zip.

The first time I got it working, I know I didn't use bhb's clean modem, but have had to since then (likely because of coming from LOS custom ROMs), however, I haven't been on that rom for quite some time.

If anyone would like me to test anything or produce a log, I can but I may not be able to do so very quickly right now.

Just stating what I know from past experience.
[Verizon Motorola Droid Turbo Android Development] roman.ramirez.12:
Im gonna go out on a limb here. I try to follow along with you guys here but there is so much info here it get a little difficult. So I'm hearing about CF a lot and it may have been considered already but if I remember correctly CF had to leave much of Verizon's apps in his build for Volte to work. He took out majority of bloatware but left the Verizon apps.