yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Very true. I remember back when every phone had multiple kernels and roms. Now we are being herded into a few phones. I get it, but there is definitely less choice if you like xda and what it stands for. FYI everything I state is from the perspective of a Verizon customer.
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
All the ones I am talking about have kernels. The LG G6

has ROMs even.

Here's the list of

LG phones with official bootloader unlock.

Here's a ROM for the BOOTLOADER UNLOCKED LG G6 U.S. 997 (which has all the U.S. carrier bands):

https://xdaforums.com/lg-g6/development/rom-aquarios-7-1-2-oms-t3639363

And a dev says he's interested in building a custom ROM for the Snapdragon bootloader unlocked Samsung S8/S8+. That one is still in early stages of development, only a modified kernel which allows TWRP and root.

https://xdaforums.com/galaxy-s8/sam...ecovery-twrp-galaxy-s8-s8-snapdragon-t3636718

but with TWRP and root, devs will follow.

I'm not arguing with anyone, but the LG G6 and Samsung Galaxy S8 both have the specs the Essential should have had -- and they both have bootloader unlock for some models (including Verizon friendly), and dev work (or will). So, look elsewhere to try to make the pig look better.

One current Verizon user says his Verizon speeds on the Chinese/Hong Kong 128GB Galaxy S8+ model aren't as good as his Verizon-branded Galaxy S8+ (because of lack of carrier aggregation), but it's still early in the dev work. He IS able to use it on Verizon, and he has root and TWRP. One dev has been in contact with members about doing a ROM. Then carrier aggregation will work.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
I'm on VZW too brother, wish I had a better option, but for my job (which pays the bill for My phone), I have no other choice. Wife's phone is totally optional, and we may take a look at TMobile, since they recently opened up a store here.
[Verizon Motorola Droid Turbo Android Development] johnjingle:
I am stuck on Verizon for my phone because of work too. I need a new phone soon as my headphone jack doesn't work and some other minor issues. What have you decided on? I am still using computerfreak's ROM for the VoLTE.

All I need is durability, VoLTE and hopefully a custom ROM.

Please let me know any thoughts you or anyone else who would like to chime in has.

Thank you.
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
With the official carrier unlocked version of the LG V30 you will get root, custom ROM. You'll also get Verizon VoLTE, but not Wi-Fi calling.

Will be released end of this month.
[Verizon Motorola Droid Turbo Android Development] quadcrap1:
I'm looking over the past whatever number of posts, and if I didn't know better, I'd think this thread was about "what phone are you going to get next?"

There's another thread for that. Let's try to keep this somewhat relevant to VoLTE on non stock XT1254 roms.
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
Cool your jets. ;)

The op himself gave the OK for the discussion. And the project is dead.

No devs are working on it.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
I am on the axon 7 now sorry.
[Verizon Motorola Droid Turbo Android Development] fgl27:
I'm still working on this I just don't have noting new that works, will open my own thread the day I have anything to share, as this type of random post that have no relation to the goal make rally hard to work on this tread I complete lost were I was if wanst for those random post I probably be more dedicated to this...

You guys can close this if you wanna as it makes no sense anymore, just don't delete post or they content...
[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
I didn't know you were still working on it.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Hey man! I'm still here; I'll chip in with logs etc. if needed. Just tell me what you need. Maybe we need to make a new thread & close this one?
[Verizon Motorola Droid Turbo Android Development] Dralix:
Any and all assistance appreciated.

Hey, guys, I'm still rocking the OG Droid Turbo XT1254 with Ballistic Nylon (what a gimmick, LOL) as my daily driver. It's just too solid a phone to ditch, even with the Pixel 2's, Galaxy Note 8, and LG V30 out there... with more goodies on the horizon. The only thing stopping me from using a custom ROM on the XT1254 -- my BL has been unlocked for months now, (my thanks to beaups, jcase, etc., and Sunshine) -- is VoLTE not being available. The very first day (no exaggeration) I installed a custom ROM, my wife called me at work. Yes, I unlocked my BL and installed a ROM at work :o. I was too excited not to. While talking with her, she texted me a pic of our toddler and asked me to check it out. With no VoLTE, I couldn't receive the pic while on the call. After I hung up with her, the pic arrived. Right back to stock I went. I know there are stripped versions of Marshmallow out there (thanks to Woodstock) that have VoLTE. But, knowing full well we'll never see "O" on the XT1254, as it's too far gone, I'd love some nougaty goodness on this bad bear. At the very least, I'd love the ability to try other variants, with VoLTE in tow. I'm no Dev. I'm just some schlep that can't help -- for that I'm sorry. But, I'm a schlep who's following this thread, not quite with bated breath, but close... just in case someone much smarter than me out there comes through. Devs and contributors, thank you for all you do. And thanks for continuing to show the love to a phone that, despite how old it is, can still hold its own to varying degrees, even among some devices released today. If someone does start a new thread, please post the link here. Thanks again.
[Verizon Motorola Droid Turbo Android Development] Raistlen0:
Just wondering if anyone has come across this thread.

https://xdaforums.com/apps/magisk/module-v4-volte-enabler-t3649613

I am not as smart as the main testers in this thread but I was curious if this is new changes or if it is stuff already tried on our phone.

They talk about needing to have the IMS libraries in the ROM already and some other things I am not sure what they are. Some of the posters in the forum make it sound like it works for them.

Just thought it may be useful.

page 13 seems to have a user or two reporting success and they display some build.prop changes to make.

Edit----

Page 3 and page 4 also seem to have possible good info with users reporting success.

Addition----------------

Looks like these phones were successful:

OnePlus3

MotoZ play on LOS14.1

Galaxy S5

huawei P9

xperi Z3

OnePlus5T
[Verizon Motorola Droid Turbo Android Development] Raistlen0:
[MENTION=5747496]bhb27[/MENTION] I was wondering if your RR ROM has in it IMS apk and libraries. Also, what about these files? WiFiCalling.apk, ims.apk or ims4.apk

EDit-----

Did any of the ROMS you guys [MENTION=7237874]NepoRood[/MENTION], @calsurferpunk, [MENTION=5901115]TheSt33v[/MENTION], [MENTION=8045158]keyvo97[/MENTION], [MENTION=6076132]computerfreek274[/MENTION], [MENTION=2640499]koftheworld[/MENTION] tested with have these items?

I don't know what these are but perhaps the missing link to get VoLTE working.
[Verizon Motorola Droid Turbo Android Development] fgl27:
no
[Verizon Motorola Droid Turbo Android Development] Raistlen0:
Well after reading through the thread https://xdaforums.com/app...abler-t3649613 It looks like these are necessary things to have in order to get the VoLTE to work.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
We had a partially working rom that Nepo built for us using all ims-related files from the stock rom. bhb said our implimentation was not right though and that was why we were still having issues.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
if you want it [MENTION=5747496]bhb27[/MENTION], my verizon turbo is currently unused sitting in my basement. do you want it if it would help move this development forward? i sent you a PM.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
sorry double post
[Verizon Motorola Droid Turbo Android Development] Raistlen0:
I followed along by reading only. I was only hoping this other thread may have the missing info that was needed.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
It's been a while but yes, I think we did include those. We actually did get VoLTE working, just not for more than 1 call before a reboot was necessary. So we had all the pieces, they just weren't put together correctly and fixing that was beyond our abilities.
[Verizon Motorola Droid Turbo Android Development] Raistlen0:
[MENTION=5747496]bhb27[/MENTION]

Still no LTE service available to you?

These articles made it sound like it might be coming.

https://www.telegeography.com/produ...osts-4g-coverage-nextel-stake-sale-concludes/

https://www.telegeography.com/produ...-launching-volte-in-sao-paulo-rio-de-janeiro/
[Verizon Motorola Droid Turbo Android Development] fgl27:
I'm not trying to enable Volte on my stable released as volte is unstable.

no, I don't leave on big centers, and I doubt those carrier really enable anything, probably only works on latest phones, I can buy food for over two years on the price of those latest phones, as Moto has kill quark even if they enable anything here going to be next to impossible to make the none volte firmware of xt1225 to work...
[Verizon Motorola Droid Turbo Android Development] Raistlen0:
[MENTION=5747496]bhb27[/MENTION] I was wondering if VoLTE may get looked at while you are working on your OREO release.?
[Verizon Motorola Droid Turbo Android Development] fgl27:
I'm working on that for a long time I never stop working on it I just give it up on this thread, if some day it works I share.
[Verizon Motorola Droid Turbo Android Development] Travisholt92:
I know how it goes, my LG K20 plus doesn't use Qualcomm IMS stack either. I'm sure Motorola used a specific IMS stack for Verizon
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Yes, I won't go into details here, but I've confirmed that there is some Verizon software that is required for Advanced Calling on the Turbo. This was a very recent discovery of mine. bhb27 put in an enormous effort trying to get it work & we really appreciate it. In this case, I think he probably would have a working solution except that there's some specific weird things going on with this phone & Verizon (which I might add bhb27 doesn't have to test) I've got some experiments I'd like to try & maybe there's still a chance of getting it working.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
No, but I could set one up. I've got Ubuntu ready to go, so it's just a matter of downloading a bunch of stuff.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Awesome. Do you have the latest fxz unpacked? I think bhb has given us a huge hint and we just to need start looking at the specified files in stock as well as starting over with the radio libs that he put together.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Let me get back to you in a few days. I should have more time to focus on this this weekend.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
I've got system and boot from the fxz unpacked and cm14-1 source synced, but I haven't started evaluating. Let me know when you are set.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Sorry it took me so long to post on this thread, [MENTION=2640499]koftheworld[/MENTION], took your PM to make me notice it again :(

The thing about VoLTE and me: I'm on a VZW Business account, that I don't have access to. The XT1254 is mine, but the bill is paid by my employer. That means, I have no way to go to website and turn it on, even though I can enable in my phone...

If you guys take a look at my tree Here, it has all the VoLTE commits [MENTION=5747496]bhb27[/MENTION] was talking about (I've recently removed them from the "Official" AOKP tree for the same reason he did)

I'm happy to help, but I have no way to test. I have many, many repos on my HDD, and it only takes 30ish minutes to build a ROM. Let me know what I can do...

Regards,

Nepo
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Thank you so much for your offer. Having you on the team will really help. That is unfortunate regarding your account. I wish there was a way for you to request that the feature is added to your account since it is free of charge. Maybe they would be able to do it at a store or on the phone without getting approval, or someone at your job can easily add it? I've had an employee account before as well and I understand the difficulties.

I think the crux of the situation is that we need to compare the solutions for similar devices of the same brand like the moto x pure and moto g. according to [MENTION=5747496]bhb27[/MENTION], we need to start with the radio libs from the latest verizon release and then merge them with the custom ones for CM. He also mentions extra permissions, but I'm not sure what that is related to. I'm willing to look at code and files as well as test. Since you have a really nice build environment set up, would you be able to look too for the indicated fix as well as tweek?
[Verizon Motorola Droid Turbo Android Development] NepoRood:
I live in Arkansas, Corporate Headquarters is in Kentucky and they could give a flying fig about me having VoLTE, I will try the store route though.

I know the Moto G dev for AOKP, and I've been looking over his VoLTE commits. I'm going to try some stuff later and see what happens :D
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Perfect nepo. I haven't had a chance yet today. Once my kids go to sleep I'll take a look at the volte commits on the moto x pure since you have the g covered. Good luck with the store route. Let us know your results with the g and the store.
[Verizon Motorola Droid Turbo Android Development] kitcostantino:
well, i finally made it to the party. (ba ha ha ha)

Comparing MM RR on xt1254 and xt1575, i finally found one folder that is different (as in not present on and seems to have the right category of [parts]. the folder is located on the MXPE at

/system/rfs/msm/mpss/readonly/firmware

if this is in part or in whole what is missing, i've no clue how to manifest those for the quark. but hopefully, that is helpful to some extent to *someone*.

Here are some screen shots to show what i mean as far as the contents being plausible for what is missing. mind you, i am not a dev and don't *really* know anything. Just a guess.

The RFS folder does not exist on the xt1254. It is literally the only folder i found that is different in /system on the MXPE.

That may mean absolutely nothing. They are, after all, two totally different devices.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Very nice find. I've been looking at the commits on the moto x side and haven't found anything extraordinary. I think I may just look at the Moto g patch itself and see what it does.
[Verizon Motorola Droid Turbo Android Development] kitcostantino:
if anyone looked at this and said "why not copy/paste just to see if it works?" it *definitely* does not work on the Turbo. i knew it wouldn't work, but i tried it for shiggles. #nope
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Test Build #1

NOTE

: For the Love of Android, take a TWRP backup of your current ROM before testing this!

I used Lineage 14.1 for simplicity reasons. I recommend, and did, a clean install so there will be no conflicts from previous installations. I flashed ROM, GApps and Latest Radio. I got the same errors as with AOKP when setting up about "com.android.phone" (I really need to fix that)

I'm not going to hold my breath on it, because I don't think it's going to work yet :rolleyes: but, it's a start I suppose...

Download

Regards,

Nepo
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Thank you nepo. I'll try it tonight. What changes/additions did you make?
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
No dice. There's no option for VoLTE in settings, VoLTE toggle in service menu does not stick, VoLTE does not work. Although APN settings is listed twice for some reason, and they both take you to the APN menu.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Thanks for the input. Like I said, I didn't think it was going to work. I'll look into some other IMS/VoLTE related files and compare them to what I have. I'll try to get another build up later today or tomorrow morning.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
No worries. Sorry I can't be of more help. Apparently building LOS is beyond my abilities. Stupid builds always failing after making bootanimation.zip for some reason...
[Verizon Motorola Droid Turbo Android Development] NepoRood:
I'm happy to help with that, PM me to see which apps we have for communication. Also, I'll be honest, with this VoLTE stuff, I'm flying blind. All I'm doing is comparing other devices and adding in what they have if Quark doesn't have it already, lol
[Verizon Motorola Droid Turbo Android Development] koftheworld:
[MENTION=7237874]NepoRood[/MENTION] i know it's kind of dumb, but what about a simple system.prop add?

telephony.lteOnCdmaDevice=1

persist.ims.volte=true

persist.ims.vt=false

persist.ims.vt.epdg=false

persist.ims.rcs=false

persist.ims.disableADBLogs=2

persist.ims.disableDebugLogs=0

persist.ims.disableQXDMLogs=0

persist.ims.disableIMSLogs=0

service.qti.ims.enabled=1

net.lte.volte_call_capable=true

persist.ims.enabler.enabled=true

i grabbed those lines from the same file on the athene.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Not that "dumb", I did add those, lol (link)

There's just gonna be more to it, that's all, first I gotta figure out why it won't stay enabled in the advanced menu...
[Verizon Motorola Droid Turbo Android Development] koftheworld:
[MENTION=7237874]NepoRood[/MENTION] lol I meant dumb for me to suggest ?. I'll see what else I can find today. Take a look at bhbs old commits. I believe he was able to get the menu and get it to stick in the menu.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Still not dumb, ;)

I have been looking, I made a build yesterday, but still haven't found that commit. I'll keep trying though :good:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
FYI here is [MENTION=5747496]bhb27[/MENTION]'s volte patch github repository for reference.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
contents of latest stock init.mmi.volte.rc file

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:
I'm uploading potentially relevant stock files here.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Had another thought. Regardless of the additions you are making [MENTION=7237874]NepoRood[/MENTION], I have a feeling that we need to modify the proprietary blobs that are grabbed from our device (like Shamu and pure nexus here https://github.com/PureNexusProject/proprietary_vendor_moto/tree/n-mr1/shamu ). For example, all of the ims apks and files are most likely essential. Bhb has openly admitted that he uses his device and situation (as he should) for development purposes, so we are dealing with a different base of proprietary files every time we make a los14/re/aokp/whatever build. A quark is a quark except when it's not...a x1254 with Verizon firmware is obviously functionally different in the use case we want to use it (volte custom rom on Verizon). This means that the propriety manifest from bhb listed here (https://github.com/bhb27/device_motorola_quark/blob/N/proprietary-files.txt ) is most likely incomplete for the xt1254. Look here at the actual script compared to stock https://github.com/bhb27/device_motorola_quark/blob/N/setup-makefiles.sh
[Verizon Motorola Droid Turbo Android Development] fgl27:
you guys are confusing a lot of things, I know this are confusing, but don't just guess things you don't know how work, ask what you need to know...

Those txt files are not used to build propose, that extract.sh also is not you are looking on the wrong three, don't use them to pull any blobs from the device, just make a backup of stock ROM, pull that to a pc, and rename it to .tar, then extract and use the files, the apk will be unusable, but those I already pull to my vendor in a usable way

https://github.com/bhb27/proprietary_vendor_motorola/tree/N/quark

I let all volte related on one separated .mk

https://github.com/bhb27/proprietary_vendor_motorola/blob/N/quark/quark-vendor-ims-blobs.mk

But I think it is damage, I don't recall lat time I build it as you can see it is commented out of the build process because it causes some crash but it builds

https://github.com/bhb27/proprietary_vendor_motorola/blob/N/quark/quark-vendor.mk#L394

this

RCSBootstraputil \
RcsImsBootstraputil \
rcsimssettings \
rcsservice \
com.motorola.motosignature \
com.motorola.ims.rcsmanager \

need revision and cross compare to working moto devices, everything need cross compare...

Any way is all there, what I advice you guys to do is check the athene files but those are "hidden" in a common three here are all the commits that may help

DT

https://github.com/LineageOS/androi...mmit/27a2e4e05ceab661e21d065175db06b71b54ac3f

https://github.com/LineageOS/androi...mmit/01442a2174b9f07a16cd2b002b8a1c978ec099d1

https://github.com/LineageOS/androi...mmit/c3c3beced81dee664d70c445f8f328d43882ed37

https://github.com/LineageOS/androi...mmit/8e8d34c5e339c6e5ba8ee56fd244ee27ce3d1e61

DV

https://github.com/TheMuppets/propr...mmit/eba7cc996a2bdbcc227770f8a7512136a27b148b

https://github.com/TheMuppets/propr...mmit/1571fd040f479e4307ac67206e3dd004190d3d97

Is basically all there

is also need to "un" commented out this from DT

https://github.com/bhb27/device_motorola_quark/blob/N/rootdir/etc/init.qcom.rc#L30

so the init volte is started during bootup

adapt what I have already done base on those 8916 commits and build and test, a lot of logs will be need to understand what is going on and adapt, check if services are running, if libs are loading, what happen during calls, and adapt from there, as you can see was need a lot of changes and a lot of collective dev work to make it work on another device, and I believed the devs working on it had a working volte device on a volte network so is easier, as you guys have that you can try...

if guys have problem adapt from that let me know...

post any builds and logs in the thread so I can read those as I'm used to read those I can help with that...

so if this cause more confusion just ask and wait I answer whenever I can...
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
I've forked the relevant repos from bhb. So far I've only uncommented the two lines that he recommended, but if anyone wants to see any of the other ridiculous stuff that I try, it will show up here: https://github.com/theSt33v