yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Thanks. I haven't had a chance to look into his information since posting. I'll take a look at your work there. [MENTION=7237874]NepoRood[/MENTION], do you have your work on github? maybe we should centralize our efforts into one fork.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
I got bored at work so I added a bunch of the commits that bhb pointed out into their appropriate places in the repo. My plan for tonight is to add all the commits, build and see what happens.
[Verizon Motorola Droid Turbo Android Development] fgl27:
you don't do this

https://github.com/theSt33v/device_motorola_quark/commit/c8f756f5e65a4ebbd17ab23a772cad8ea8f51d2e

that probably will not work as you are not dealing with sepolicy and I already add a volte init to keep all in the same place

https://github.com/theSt33v/device_motorola_quark/blob/N/rootdir/etc/init.mmi.volte.rc

add this to the volte init

service imscmservice /system/bin/imscmservice
class main
user system
seclabel u:r:init:s0
group radio net_raw diag diag log
disabled

that will run and if some day you guys manage to make this work I deal with the proper sepolicy rules

Do the proper changes to vendor, enable volte flags in the base overlay and give it a try...

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

and this

start imscmservic

under

https://github.com/theSt33v/device_motorola_quark/blob/N/rootdir/etc/init.mmi.volte.rc#L56

like this

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

:good:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Thank you again for your help. I started a few pull requests related to what you've posted, but I don't have time tonight to get all the way through. I feel like we're closing in on something working...
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Okay everyone, the following build has all the commits recommended by bhb except for the ones that caused the build to fail. Here it is:

https://mega.nz/#!DpIzjTSZ!-3NABKQrYwvBEt5EyxSQ-oU_S3PoequQ2aJnuMj1pX8

The VoLTE provisioned flag is enabled by default, and so is "Enhanced 4G" in the cellular networks menu, but VoLTE functionality still seems to elude us. I'm going to start looking at logs and I would request that others do the same. If you're reading this and you were looking for an opportunity to help without having to mess with coding and github, now's your time to shine.

PS: check out that sweet boot animation
[Verizon Motorola Droid Turbo Android Development] koftheworld:
awesome job! did you work in the pull requests I submitted? i didn't see them committed in your branch.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Nope, didn't see them. I'll accept those at work, but I won't be able to build again until tomorrow. Or maybe tonight if my friends are flakey.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
haha np. take a look and let me know. they are based upon bhbs comments. also, i just submitted another pull request for the ims-blobs file that he mentioned. i found some differences between it and the current stock rom, so i updated the file to reflect. let me know what you think.
[Verizon Motorola Droid Turbo Android Development] fgl27:
I see you guys are trying to deal with some odd error and making some confusion on how to fix it.

so I have update a volte branch so you guys can see how those commits are supposed to be adapted, try to use those tree to build, and read what I did so you guys understand the adaptations in case is needed more you guys can make it

https://github.com/bhb27/device_motorola_quark/commits/N_Volte

https://github.com/bhb27/proprietary_vendor_motorola/commits/N_Volte

I did not try to finish a build because takes too long, but I started one and have no build error from the changes to .mk and related, so it must build just fine, in case it doesn't paste the build log in the thread... to make a build log use this command to end of the command you use to start the build

2>&1 | tee quark.txt

in my case I use

time mka bacon -j4 2>&1 | tee quark.txt

that will produce a .txt file contain all the build process and it error, .zip it to share as it can became very big...

and can you tell me the need of this?

https://github.com/theSt33v/device_motorola_quark/commit/4cb796629fae681ed8ce97a2a168ffa8f86d9198

cmaction build just fine on any source I don't understand the change and you are breaking the functionality of the ambient display switch...

share some logs after testing if it builds OK...

:good: :fingers-crossed:
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
I made that change because that Boolean function was causing my builds to fail. I don't remember what the error said exactly, but forcing that value to be true allowed the build to happen. Everyone else seems to be able to build just fine without that change, so it's probably some problem with me and not the code, but I'll worry about ambient display after we get volte working. I don't expect anyone to actually use these builds for real, but if we get volte working, we can implement it in the real roms that are made by people who know what they're doing.

Also, thanks for the updated device tree. My super awesome PC builds like a beast, so I'll probably build it tonight and throw it up here.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
thank you very much for this! i know i wouldn't be able to get anywhere with this without your continued support. was my pull request for your vendor file okay?
[Verizon Motorola Droid Turbo Android Development] koftheworld:
thanks again man for building these. my pc is the opposite of yours for building haha.
[Verizon Motorola Droid Turbo Android Development] fgl27:
any error always past on the thread as it can help anyone having the same...

I get what is going on, the stock CM doesn't have the bool I was checking for..

fix it here

https://github.com/bhb27/device_motorola_quark/commit/6e20924775d5288a4df7cb133dff43a9e71e51bb

:good:
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Here is the latest build made using bhb's volte branches. It's booting on my phone right now, so I can't say anything about it yet:

https://mega.nz/#!jtgD1KRB!HOMiCRLRFKlxjJinWxOKmfCIYGa7SAhcMaFYY7uOEwI

UPDATE: This build does not recognize that I have a SIM card in the phone. Logcat is attached. I think the culprit occurs at 20:51:09.851.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Logs from STOCK (ComputerFreek ROM) Marshmallow with VoLTE working

Hey everyone!

I'm guessing some has already done this and that it won't help, but thought maybe working backwards from the working VoLTE Marshmallow ROM might help.

Logs file (attached) of the following from ComputerFreek's Marshmallow ROM where VoLTE works great:

-Had "Advanced Calling" (VoLTE) enabled

-Started Logging

-Turned off VoLTE from the menus

-Paused for a little while

-Turned VoLTE back on

-Waited a little while and then stopped logging

Maybe this will tell those of you smarter than I about some of the requirements for VoLTE to work?

This is the first time I've ever captured a log... so if something looks wrong... there could be user error involved. Also, I removed all the Thermal-related stuff and my IP address for easier readability and anonymity :)
[Verizon Motorola Droid Turbo Android Development] fgl27:
is expected, I did not test for and did not adapted the tree to work with vzw libs that is a lot of work have no idea were to start solving the problems of that tree...

may not be needed I manage to make all ims service to run using this

https://github.com/bhb27/device_motorola_quark/commits/N_Volte2

https://github.com/bhb27/proprietary_vendor_motorola/commits/N_Volte2

[init.svc.ims_rtp_daemon]: [running]
[init.svc.imscmservice]: [running]
[init.svc.imsdatadaemon]: [running]
[init.svc.imsqmidaemon]: [running]

have no idea what the result of having it all running but must help

this are starting by default

init.svc.imsdatadaemon]: [running]
[init.svc.imsqmidaemon]: [running]

this are not

[init.svc.ims_rtp_daemon]: [running]
[init.svc.imscmservice]: [running]

this is how to start manually

quark_umts:/ $ su
quark_umts:/ # start service_name

service_name = word next to service in the init example

service ims_rtp_daemon /system/bin/ims_rtp_daemon

service_name=ims_rtp_daemon

so

start ims_rtp_daemon
and
start imscmservice

so build those, test to see if the services ate started

getprop | grep -E 'imsqmidaemon|imsdatadaemon|ims_rtp_daemon|imscmservice'

if some don't show force start, check all volte flags and give a try on a volte call + data traffic...

all those are adb command... logs etc etc have fun

:good:

in the middle of that process can you or anyone else use volte?

you know make a call and use data at the same time???

and use this app log tool

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

Logs > One click All Logs to a zip...

logcat alone will not give what is happening, and do all that after the device has just finished booting, so the logs get the start of booting process (that gets flush when the log gets full), the process you did plus the volte working...

:good:
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Thank you for the very informative information! Here's my first attempt (sanitized log files attached).

Steps I took:

1.) Disable/uninstalled most of my apps and disabled the Play store to reduce log traffic

2.) Rebooted phone

3.) Immediately opened your awesome Kernel Auditor App

4.) Made a phone call to 1-866-894-6848 (Verizon Wireless Accessories line)

5.) After the phone call connected, I opened Chrome and browsed to cnn.com

6.) Switched back to the phone app and used the keypad to select a menu option from the call tree

7.) Hung up after a while

8.) Immediately launched Kernel Auditor again and dumped the zip file

Hopefully this file is helpful?
[Verizon Motorola Droid Turbo Android Development] fgl27:
I did not included to the build process on those N_Volte2 branches, the rcs app, they don't seem needed on custom, but doesn't hurt to try...

After have making a ROM whit all ims services running and have no success in a volte call

grab this two app, past in system/app/ set permission 0644 reboot, after starting all ims service, start the "config-rcs-on" service

start config-rcs-on

it will setup all extra props related to ims and rcs plus will start the attached applications...

test test + log and log, let me know...
[Verizon Motorola Droid Turbo Android Development] koftheworld:
You're awesome. I made some additions/changes to your quark-vendor-ims-blobs.mk file from the stock side. let me know if they are necessary or just redundant.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Sweet. The three ims services that bhb mentioned are running in the stock rom, so we should probably have them running in LOS too. I'll make a new build tonight with the updated trees and try the posted rcs apps as well. I'll also try to get remote login working so that I can get builds started while I'm at work instead of having to wait until I get home.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Great. I made the same mk file changes to your branch as well. Let me know if you like the pull. I think I have a few outstanding.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Is there anything else I can do to help? I was a little confused by bhb's last post.
[Verizon Motorola Droid Turbo Android Development] fgl27:
I see those changes, that LteBroadcastServices app I never try, it is really odd, it has a giant lib and inside of the app has another app, whit is really odd makes no sense to me maybe does to Moto/Vzw... I update the branches to included those app, the LteBroadcastServices run just fine on my device it doesn't do a thing here, but may do for xt1254...

the RcsService app and libs is open source there is the possibility to build it on LOS ROM, but if use the prebuilt or the source one there is some odd behaviors and crash from phone and sincard, I let the file there but don't load it to the build process, I can take a long look some day to it if we never get a solution but doubt one app may do a big change...

I update N_Volte2 branches whit latest finding, you guys build that, share and lets see the results... :good:
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
At this point, I don't think I'm going to bother keeping those branches up to date. It doesn't make sense for us to keep copying and pasting the changes that bhb tells us to make when he's willing to do it himself with his own branches. I'm just going to build bhb's branches from now on and when/if he gets sick of helping us, I'll fork those branches and we can start making changes from there.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Not sure if this helps, but here's some ps dumps from the fully working stock Marshmallow:

root@quark:/ # ps | grep rcs

radio 4551 363 1015128 45564 SyS_epoll_ b6d23bec S com.motorola.ims.rcsservice

radio 4566 363 1012164 40300 SyS_epoll_ b6d23bec S com.qualcomm.qti.rcsbootstraputil

radio 4581 363 1015160 42872 SyS_epoll_ b6d23bec S com.qualcomm.qti.rcsimsbootstraputil

u0_a22 13521 363 1015260 46444 SyS_epoll_ b6d23bec S com.motorola.rcs.eab

root@quark:/ # ps | grep ims

system 362 1 15468 1288 poll_sched b6d03ddc S /system/bin/imsqmidaemon

system 543 1 25408 2096 poll_sched b6bf5ddc S /system/bin/imsdatadaemon

system 1548 1 56088 7812 __skb_recv b6d20b50 S /system/bin/ims_rtp_daemon

radio 4551 363 1015128 45552 SyS_epoll_ b6d23bec S com.motorola.ims.rcsservice

radio 4581 363 1015160 42872 SyS_epoll_ b6d23bec S com.qualcomm.qti.rcsimsbootstraputil

I was trying to figure out how to kill them successfully one by one & test VoLTE after each... but I can't get the services to die no matter what I do lol
[Verizon Motorola Droid Turbo Android Development] NepoRood:
I can agree with this, lol. Sorry I haven't been very helpful, stuff going on. However, I can contribute a build for you guys to test, I just started it, using the latest VoLTE trees, should be up within the hour :good:

EDIT:

Build is uploading HERE

(If it's not there, give it a bit)
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Logs from NepoRood's Build Below

Update 2: Correct logs now attached

Update:

Nooooo! Wrong logs were uploaded (the STOCK rom with VoLTE working ones)

Procedure followed:

1.) Booted phone

2.) Immediately opened Kernel Auditor

3.) Opened phone and called 1-866-894-6848

4.) Opened Chrome and attempted to go to CNN.com (didn't work since VoLTE isn't working)

5.) Went back to the phone app selected menu option 1 on the call tree

6.) Then hung up eventually

7.) Went to the Phone App 'Settings' > Calls > IMS settings (com.android.phone crashed of course)

8.) Opened Kernel Auditor and dumped the logs

Awesome! I'm testing it out now. Here's what I've got so far:

-No VoLTE, but phone calls are working

-Phone App crashes [com.android.phone has stopped] when you go to Phone App Settings > Calls > IMS Settings

-The APN menu is showing up twice (probably an unrelated issue)

Logs will be coming in a bit
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Interesting. Lots of RILQ errors in radio.txt mentioning qcril_qmi_generic_socket_agent. Also a recurring error in ImsManager. ImsManager.getinstance: phoneId=1, imsPhoneId=0. Seems to me like ImsManager still isn't convinced that the device is ready for ims functions.

Logcat shows ImsSenderRxr error at 01:54:56.253. "Registered not sent."

A lot of intersting IMS related stuff goes on at 01:54:56.335. I don't understand most of it, but it seems to understand that VoLTE is available, at least at first.

EDIT: Annnnd nevermind. Those were the wrong logs. Oh well. Now I know what it looks like when it works. Will look at the correct logs now.

At 13:58:25.868 in radio.txt, we see VoLTE:false. In the stock rom logs, this said VoLTE:true. So ImsPhoneCallTracker still hasn't gotten the memo that VoLTE is enabled.

But then oddly enough, at 13:58:31.964, we see ImsManager reporting updateVolteFeatureValue: available = true, enabled = true. Then at 13:58:32.448, ImsManager reports isVoLteProvisioned=true. So it looks like ImsManager is trying to pull through for us at least.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
That's fine and agree. We should keep everything centralized there. I submitted a pull request on his also, so we'll see what he says. Thankfully bhb is on board with helping us - i'm thinking because he sees we are being serious about this research and also have working xt1254s on the verizon network. for him to have done this by himself for basically no reason didn't make sense, so with us actively contributing there is an actual end point potential.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
[MENTION=7838338]translucentfocus[/MENTION] [MENTION=5901115]TheSt33v[/MENTION] [MENTION=2640499]koftheworld[/MENTION] (and any anonymous testers)

Don't forget to also include the services that [MENTION=5747496]bhb27[/MENTION] mentioned on the previous page, there's a couple ims related that need to be started manually (for testing purpose) and also the rcs mentioned later...
[Verizon Motorola Droid Turbo Android Development] fgl27:
the service config-rcs-on did not run, can you run it manually by adb and retest?

su
start config-rcs-on

then test...

al the others seems to be running just fine, can you tell me if you force start any service? because if you didn't I can do some change so they all get start together...

so is need to know the effect of the functionality after that service had run at least once...

:good:
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
It's Working! (Sort of)

UPDATE: Logs attached. VoLTE is definitely working, but it looks like there are some issues

Issues I've noticed so far:

-When 'connecting' the phone call, the data connection is lost, but it's regained after the phone call is connected

-com.android.phone still crashes when trying to access IMS Settings

-I seem to have better luck when I reboot > start config-rcs-on > make first phone call... after that it gets worse and less reliable

-When VoLTE is working, Touch tone menu options are not recognized

Thanks so much to all you guys; this is awesome that you've made this much headway this quickly

I started the rcs service manually... tested and I'm currently in a phone call and surfing the web... donation coming your way! What else do we need fix while we're at it?
[Verizon Motorola Droid Turbo Android Development] fgl27:
This is great then... more tester is need so we can get this 100%

@ all

I have add updates to N_Volte2 branches to improve the process of starting the service and add some extra permissions requested by the logs..

:good:
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Great, I'll sync and build new now, give me 45 minutes +/-

EDIT:

Newest build can be found HERE

(Same name, latest commits)
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Update: Logs now attached

-Had some issues getting the Kernel Auditor to create the logs... so you might see some errors besides VoLTE stuff :)

-Also, after making a phone call and trying touch tone menu options, I then tried to go to IMS Settings to make it crash

Awesome! Things I've noticed so far:

-VoLTE now works on boot without using ADB

-Touch tone menus in calls do not work

-IME Settings in com.android.phone still crash and now cause a no SIM icon temporarily while the radio recovers

logs coming soon...
[Verizon Motorola Droid Turbo Android Development] fgl27:
whar is?

-Touch tone menus in calls do not work

pics please

deleting the app ims will solve that crash of phone app... but don't know if will affect the work of Volte ...

go to system/app/ see if there is a ims/ folder and delete it... then go to system/vendor/app and delete the ims/ foder there... after reboot and try to open the ims setting and try to change the option there... and test for volte...

pics if possible

:good:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Wait are you saying the service starts or volte is actually working?
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
This is actually when you make a phone call, and you get an automated system that might say, "Please press 1 to review your new Voicemails". I can press 1 on the keypad all day long, but it doesn't work. But it only doesn't work when VoLTE is working. Does that make sense?

---------- Post added at 05:47 PM ---------- Previous post was at 05:45 PM ----------

Both, the service starts (I'm assuming) & VoLTE is actually working (just like last test build). It doesn't work smoothly sometimes, but I can make phone calls and then surf the web from my phone while in the phone call. The problem is it disconnects data temporarily when connecting the phone call.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
There is a volte audio service I saw somewhere let me check into it... That's great regarding volte though!!!!! Success!!!!!
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Wooo!! Well done everyone (although let's be real, well done bhb)! I'm flashing the latest build now. Will report back.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
No doubt, [MENTION=5747496]bhb27[/MENTION] gets all the Development credits :good:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
100% agree [MENTION=5747496]bhb27[/MENTION] deserves all the credit
[Verizon Motorola Droid Turbo Android Development] fgl27:
ye I get it DTMF is not working... ok, maybe another phone app can help with that try some other from play, and then after some investigation on how it works on aosp phone app we can try to fix it...

and let me know the behavior after removing ims app...

:good:

---------- Post added at 08:10 PM ---------- Previous post was at 08:05 PM ----------

Like always I'm just having fun... everyone on this thread is helping the point is to make things working and we all did that...

:good:
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
UPDATE: I received a phone call and VoLTE did NOT work. I've attached the logs, but it wasn't right after boot... so not sure how useful it will be. This is with the IMS apps still removed.

Followed your directions. VoLTE still works, and the settings don't crash. However, the IMS Settings don't seem to take. I'm trying to get a screenshot currently. (Having issues with wonderful MTP and files not appearing)
[Verizon Motorola Droid Turbo Android Development] koftheworld:
[MENTION=5747496]bhb27[/MENTION] I remember seeing volte settings in mixer path (like here https://github.com/CyanogenMod/andr...f9198984999a52e9100c12fcafc9a/mixer_paths.xml ) and in audio platform (like here https://github.com/CyanogenMod/andr...999a52e9100c12fcafc9a/audio_platform_info.xml )
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Hint: In the future, click the line number, then copy the link ;)

That way, it goes straight to the line you are talking about and saves a bunch of scrolling :good:

Example

PS, Good Find, lol
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Haha sorry am on my phone while doing dishes will get right links in next time
[Verizon Motorola Droid Turbo Android Development] NepoRood:
No worries, just thought I would point it out :p
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
So if I'm not mistaken, the latest build is supposed to work out of the box, right? Mine does not. Logs attached.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
What preferred network mode do you have enabled? Also do we have the right band selected? If I remember correctly, bhb used to have people select they were on Verizon through an adb command (I think) when using his roms. Also just a thought but maybe change touch tone speed in dev options.