yashsingh1/xdaforums huggingface dataset:
[Magisk] Zackptg5:
I did answer the question. If you'd look at my signature, you'd see that I have the op5t too. Only use deepbuffer remover if v4a doesn't process on streaming apps like spotify or YouTube. They work fine on the op5t so you don't need this mod. So flash the mod again and it'll uninstall it.

AML is where all of the audio cfg, pol, and mixer files are stored so that's where the patched files are located (which is what this mod modifies). V4a patches cfg files in order to it to work too so it's required for it (and any mod that uses AML)
[Magisk] Dazed No More:
It seems you are correct about Pandora and Spotify (my apologies), but for some reason SoundCloud will not process anymore. This is strange because it processed fine up until a few days ago.

I'm still trying to figure out the headphone dilemma but as I said in my original post SoundCloud is what I listen to most yet it has stopped processing.
[Nexus 6P Q&A, Help & Troubleshooting] Etheralrealm:
For a while I've been using Lineage OS, and now my WiFi has mysteriously stopped working, at some points it'll randomly start working. usually if i goto settings i can click on, then it just sits at "Turning WiFi on..." screen for a while.
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
Hi... You don't need to open multiple threads about the same issue. Ask a mod to close it... :)
[Nexus 6P Q&A, Help & Troubleshooting] Etheralrealm:
Thanks, an also, i seem to have fixed it, i reverted to the first build i downloaded of lineage os, wifi seems to be working, hasnt died yet...
[G3 Q&A, Help & Troubleshooting] Frankenscript:
Hi folks,

I've got a new problem that started after I updated my D851 from (stock/rooted) Lollipop to (stock/rooted) Marshmallow.

When I'm home, I've got a decent LTE signal (ATT, though using the T-Mobile phone variant). But since I'm home, my phone connects to my wifi and uses it for data. I have no problem making/receiving calls or SMS texts to a single person at a time.

However, as long as I'm connected to WIFI (with my cellular signal present but not used for data due to the WIFI), neither MMS nor group texts work. In the stock Messages app, or the Messaging app I actually usually use, these MMS or group texts sit there as "sending..."

If I turn off the wifi, the cellular data signal is used immediately and the texts go through. Same goes for receiving MMS.

Again, this only happens since the marshmallow update that I applied a couple weeks ago.

I have not found a fix. I found lots of people complaining, and a few proposed solutions, like changing the APN so that the APN Protocol would be set to IPv4/IPv6 instead of the default IPv4. See here for that reference, though it didn't work for me:

https://support.t-mobile.com/thread/61843?tstart=0

Anybody have a fix for this? it's a real problem particularly for incoming messages. I can always toggle wifi off if I want to send something, but not knowing when something is coming in gets to be a problem. SMS from single conversations come through.

Please help me troubleshoot this. I've googled my fingers to the bone and while I've found reports of issues like this going back years, no actual solutions that work for me.

HELP!
[G3 Q&A, Help & Troubleshooting] Frankenscript:
There's one workaround so far... using Textra as the messaging app. It has an option called the T-Mobile Wifi Calling fix (in Settings/MMS/scroll down to bottom). Even though my wifi calling is set to off, since I'm on ATT, enabling this setting in Textra automatically toggles off WiFi to send MMS/group sms, and it does the same when it detects an attempted incoming MMS.

I much prefer the Google Messages app, for a variety of reasons, and I'm looking to figure out a real fix rather than this workaround. Any help most appreciated.
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
Ala N95? Via the miniusb? This would be a fantastic development.
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
Nobody know anything about this?
[Touch Dual, MDA Touch Plus ROM Development] maxmerkel:
niki: MSM7200, Windows Mobile 6,...

n95: OMAP2420, Symbian OS,...

why do you think the touch dual would support this ??

looks like these two devices are totally different...
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
So what?

I cited the n95 as an example of a device that has tvout not to compare the two.
[Touch Dual, MDA Touch Plus ROM Development] ducamie:
besides, while you want to go down that route this pdf says the MSM7200 is tvout capable..

http://web20.telecomtv.com/docdownload.aspx?fileid=f7e62028-1ab4-490d-8adb-dfc93628f845/MSM7200_Chipset.pdf&id=395
[Galaxy S 5 Q&A, Help & Troubleshooting] mrpine1987:
just got my phone rooted.....Accidently turned off oem unlock and my bebug turned off my phone and went to put on twrp only to find now its locked now I don't know what to do let alone what I was thinking. what do I do......HEEEEELPMEE
[Galaxy S 5 Q&A, Help & Troubleshooting] Youdoofus:
is it locked with the samsung account or google?
[Android General] Ibuprophen:
- - - deleted thread - - -
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Hello all!

After being on the XT1254 with Verizon from early on, I have gotten tired of reading disjointed communications regarding this subject. This thread is here for us to:

a) compile all known prior research on the subject - enabling VOLTE for non-stock roms for XT1254 users on Verizon;

b) discuss phones that have known working solutions (e.g. ZTE Axon 7); and

c) discuss and test new solutions for this issue.

Not having VOLTE capabilities on custom roms is the last major area of development left for the xt1254 (not counting those that still complain about not having a free unlocking solution - ha! thank you sunshine btw :) ). If you have some time, please let's get all of our ideas in one place so that we can work on this issue together.

All builds from [MENTION=7237874]NepoRood[/MENTION] are here https://www.androidfilehost.com/?w=files&flid=166122

Update 4/11/17

New builds just keep showing up! We are getting close on this. Please install the latest build and contribute logs.

Partial success has been achieved! VOLTE is active for the first outgoing call, but doesn't work after that until using airplane mode. Incoming calls and VOLTE aren't working yet. R&D still being conducted. Please contribute where you can.

UPDATE 5/30/17

I uploaded all logs here. [MENTION=7237874]NepoRood[/MENTION]'s latest test version is still at the link listed about. Version 5 is here, but outdated. [MENTION=5747496]bhb27[/MENTION] made a test rom and kernel for us here.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
[MENTION=5747496]bhb27[/MENTION] - you are the initial inspiration for this thread based upon your work and your words (especially here).

a) compile all known prior research on the subject - enabling VOLTE for non-stock roms for XT1254 users on Verizon;

Last known VOLTE patch from [MENTION=5747496]bhb27[/MENTION] is here.

Research/discussion on this subject has included:

-porting IMS from stock to custom

-My Verizon apk or other verizon specific apps

-mobile network settings switch

-enabling VOLTE flag in phone info *#*#4636#*#*

-disabling/enabling advanced calling on Verizon account page

-potential build.prop differences

b) discuss phones that have known working solutions (e.g. ZTE Axon 7);

Axon 7 - post from [MENTION=3250376]ChazzMatt[/MENTION]

Moto X Pure - post from [MENTION=3836686]kitcostantino[/MENTION]

c) discuss and test new solutions for this issue.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
I think the first question for part c is: has anyone flashed the latest roms from [MENTION=5747496]bhb27[/MENTION] , [MENTION=7237874]NepoRood[/MENTION], [MENTION=6069596]calsurferpunk[/MENTION], [MENTION=5901115]TheSt33v[/MENTION], [MENTION=8045158]keyvo97[/MENTION] and tried VOLTE out of the box? i am currently on [MENTION=6076132]computerfreek274[/MENTION] 's latest 6.0.1 modified stock rom and haven't tried any of them yet. Unless I hear something to the contrary, I will be installing each and trying out some of the prior discussion topics (e.x. volte flag).
[Verizon Motorola Droid Turbo Android Development] koftheworld:
duplicate post
[Verizon Motorola Droid Turbo Android Development] RoboCuz:
I'm running the latest RR Nougat with custom kernel from bhb27 and no luck.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
have you gone through any of the previously stated ideas?
[Verizon Motorola Droid Turbo Android Development] zys52712:
I'm on calsurferpunk's Lineage OS 14.1 ROM and whenever I toggle the VoLTE flag it turns off right after you close the window.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
was this a clean installation?
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
"My" rom is stock. It is not modified in any way. So yes, VoLTE works just fine out of the box. Computerfreek's is stock too, for all intents and purposes, and therefore should also work without further modification.
[Verizon Motorola Droid Turbo Android Development] zys52712:
Yes, it was.
[Verizon Motorola Droid Turbo Android Development] johnjingle:
I don't know where this thread will go, but I have tried everything in the OP many times and I do not think that any new builds of non-stock ROM's will ever have VoLTE appear without figuring out what the signature/handshake is with Verizon.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
That part has already been figured out. There​ are devices out there that run LOS and can do VoLTE on Verizon. The trick is porting it to our device.
[Verizon Motorola Droid Turbo Android Development] johnjingle:
What I meant was handshake/signature (port) is necessary because without the correct code none of the other ROM's will "magically" have VoLTE with a new build.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Yes I forgot that yours was stock when I mentioned you. You have any ideas though?
[Verizon Motorola Droid Turbo Android Development] koftheworld:
interesting things i found looking at los code for our device:

config.xml clear reference from skrilax that he disabled volte on verizon until ims is supported. note is from 12/11/15. Specific lines in code are still there:

<!-- Flag specifying whether VoLTE is available on device -->

<bool name="config_device_volte_available">false</bool>

<!-- Flag specifying whether VoLTE should be available for carrier: independent of

carrier provisioning. If false: hard disabled. If true: then depends on carrier

provisioning, availability etc -->

<bool name="config_carrier_volte_available">false</bool>

<!-- Flag specifying whether VT is available on device -->

<bool name="config_device_vt_available">false</bool>

<!-- Flag specifying whether VT should be available for carrier: independent of

carrier provisioning. If false: hard disabled. If true: then depends on carrier

provisioning, availability etc -->

<bool name="config_carrier_vt_available">false</bool>

a similar file on axon 7:

<!-- Flag specifying whether VoLTE & VT is available on device -->

<bool name="config_device_volte_available">true</bool>

<!-- Flag specifying whether VoLTE should be available for carrier: independent of

carrier provisioning. If false: hard disabled. If true: then depends on carrier

provisioning, availability etc -->

<bool name="config_carrier_volte_available">true</bool>

There are 16 total files on the quark with code exactly as i mention in first file. Skrilax's change log for his volte disable code show these files.

My question is there no chance at volte unless each "false" entry is set to "true". i am going to start to dl source to find out, but someone please try in the meantime.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
I do not. I know as much as you do about this. Probably less. But I'm always willing to test things should the need arise.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
do you have a los build environmental setup already?
[Verizon Motorola Droid Turbo Android Development] fgl27:
that is not how you make it work, those only tell the system in that case the base of android frameworks that the device is volte capable, but that doesn't add the device specific support that is in most cases different from device to device...

latest moto g athene received a custom ROM patch to support volte, it is base on modify stock radio.libs merging it with custom radio lib and some extra permission related, I never try that because the radio lib to use is the VZW and I have no idea of the behavier of that that on my xt1225 or even on xt1254, this is really time demanding I have almost 0 time for developer work, if any one wanna to try anything must undo all the removes I did for volte in my DT I alredy did most of the job, but leave things disable because makes no sense let a thing that doesn't work enable, and patch similar to athene and test and test, if I had a little more time, 4g and volte I would try, but for me is a complete wast of time with is not free.

so if you guys wanna help that is it, go have fun, and look for reference on devices that at least have the same Brand...
[Verizon Motorola Droid Turbo Android Development] mbj731:
A quick google search looking into voLTE on custom roms seems to indicate that there is a simple patch for most custom ROMs to enable Volte, the catch is it seems to work for Joi, a mobile network in India? Many custom ROMs claim "voLTE support" so why is it as easy as flashing a patch for this JOI network, but next to impossible to get voLTE for custom ROMs on Verizon?

I recently switched from Verizon and never understood the need for volte in the first place, but it just seems odd to me that so many ROMs from different phones claim support but in reality it doesn't work for Verizon but does for a network exclusive to India (I think)...?
[Verizon Motorola Droid Turbo Android Development] koftheworld:
Thank you very much for your input and continued support of our device. Especially thank you for even trying to help us even though you are in a different country, aren't on verizon, don't have a xt1254, and don't have LTE where you live. You really are amazing that you even tried.

I will definitely start looking at the radio libs as you stated.

FYI, there are many VOLTE references for the moto x pure (which has working volte in our use case). EX's

VOLTE RATs

init_clark.cpp

proprietary-files.txt

BTW I really like your exchange with moto here about the subject.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
OK, just making sure. More work to do then...
[Verizon Motorola Droid Turbo Android Development] johnjingle:
I also logged into to Verizon to check on VoLTE status and it said my device(s) were already enabled.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Thanks [MENTION=7237874]NepoRood[/MENTION]! I should be able to test in an hour or so. I'll report back.

Unrelated, has anyone thought about methodically disabling things (or maybe deleting files) on the Stock ROM and testing VoLTE after each change until it breaks? I was attempting this before (and discovered that disabling the My Verizon App didn't do anything) but couldn't get any of the more system-level processes to actually stop... even trying to kill them from adb. I'll be glad to take this testing on if it sounds like a good idea, AND if someone can tell me how to kill the stuff lol.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
KA won't function (or collect logs) without root, so it's necessary for that purpose.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
I installed VoLTE_5 and got the same results as my previous test, with the exceptions that the VoLTE flag was enabled by default this time and all files that I added myself last time were there by default.

I also discovered that toggling airplane mode is enough to make VoLTE work again after it stops working. You don't have to reboot the phone. However, it only works once per toggle.

A note to everyone testing: just so we're all doing the same experiment, please try using Chrome as your test when you're testing VoLTE. The default search bar on the launcher doesn't seem to work in any circumstances for me, so it would just make diagnosing easier if we just all use the same app for testing. You can use other apps too if you want, just remember to do at least one test with Chrome.

And one last thing: if you're going to test, post logs or it didn't happen.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
I'm not sure how useful that would be at this point. VoLTE is working, so all the working parts are there. We just need to figure out which app/system process/whatever is getting pissed off after that first instance of it working and tell it to chill out. The only way I can see to do that is to comb through the logs. I've done a little bit of that, but I haven't found anything that's stood out to me yet.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Okay, one other question... has anyone tested incoming calls? I've yet to successfully receive an incoming call on VoLTE.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Confirmed. During an incoming call, VoLTE doesn't work. It also breaks VoLTE for all subsequent calls until you reboot or toggle airplane mode.
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
Update: Attempted an incoming call (didn't even ring) & added logs

Tested this build and instead of repeating exactly what [MENTION=5901115]TheSt33v[/MENTION] did, I tried:

-Making a call (VolTE worked)

-Made another call (VoLTE failed)

-Pulled the SIM card out & put it back in

-Made another test call (VoLTE worked again)

I'm hoping this will give some more illuminating logs. My apologies, but I had to fiddle with some things so the logs aren't completely clean.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
But you can grant it permission with Privacy Guard, right? Anyway, I use SysLog mostly, because you can clean the buffer before doing a test ;)

EDIT:

SysLog requires root too, lol, :silly:

(In my defense, I hadn't been awake very long)
[Verizon Motorola Droid Turbo Android Development] translucentfocus:
SE Linux is in Permissive Mode. (Went to About Phone to confirm) [MENTION=5747496]bhb27[/MENTION] disabled it so that we could test more easily as I recall, but I couldn't find the post in a quick search of the thread.
[Verizon Motorola Droid Turbo Android Development] fgl27:
I will take a long look at the log, that behavior seems to be trigger by some system action hope they log what they are doing so we can make a workaround to get at least 100% out volte call..

there is no selinux rules for ims/volte related yet, to test you must have it at permissive, in the log permissive=1 means it is in permissive, if was a 0 enforcing, getenforce adb command will tell you...
[Verizon Motorola Droid Turbo Android Development] koftheworld:
this log error looked interesting to me:

04-10 22:08:57.953 1550 1747 E Diag_Lib: [IMS_ERROR]| 3544 | 1747 |ims-rtp-daemon ims_rtp_qmi_handler_thread_func waiting on select thread>

I'm going to explore your gh to look into both of those.
[Verizon Motorola Droid Turbo Android Development] koftheworld:
so if i understand correctly, we have ims_rtp_daemon here, but we don't have it listed here or here. based on what you've stated [MENTION=5747496]bhb27[/MENTION], we should have it listed in the android.mk file as well as the ims-blobs.mk location. let me know what you think.
[Verizon Motorola Droid Turbo Android Development] fgl27:
none volte files goes here

https://github.com/bhb27/proprietary_vendor_motorola/blob/N_Volte2/quark/quark-vendor.mk

volte only goes here

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

no need to duplicated (add to quark-vendor-ims-blobs.mk and also to quark-vendor.mk) or add any bin to Android.mk
[Verizon Motorola Droid Turbo Android Development] NepoRood:
VoLTE_6

Turns out, after rechecking, I still missed a couple of packages :confused:

New build, Here

If this one doesn't work properly, maybe we'll need so find something "outside" of what we have...
[Verizon Motorola Droid Turbo Android Development] koftheworld:
thank you for the explanation. i was confused based upon what you wrote about signed packages.

are you building directly from [MENTION=5747496]bhb27[/MENTION] 's tree, or are you building from your own?
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Trees from bhb, I just added to package list (he already had them there, they just weren't included)

EDIT:

Just to show the difference, here's the links.

roodbuild/quark-vendor-ims-blobs.mk

and

bhb27/quark-vendor-ims-blobs.mk

All other files are exactly the same :good:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
great! i was curious what was the difference between your trees. did you submit a pull request to bhb, or are you holding off until we determine effectiveness?

quick question - i saw you listed RcsServiceM \ . shouldn't that only be RcsService \ ?
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Holding off, for now, need to see how it all goes :good:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
quick question - i saw you listed RcsServiceM \ . shouldn't that only be RcsService \ ?

also, i didn't see rcs_config.sh (located in system\bin) listed anywhere.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
Both packages are there, in Android.mk and the rcs_config.sh file is in the device tree (not vendor)
[Verizon Motorola Droid Turbo Android Development] koftheworld:
thank you for the clarification. i downloaded the new version, but i can't install it until later tonight (EST). i'll post logs if no one gets to it by then.

question for you on the files we're using: are the files that you are pulling for each build from the newest stock, or are they from a prior update? maybe that's a better question for [MENTION=5747496]bhb27[/MENTION] .
[Verizon Motorola Droid Turbo Android Development] NepoRood:
I'm pretty sure they're from the MM update of the 1254, but, bhb will need to clarify where he got them from ;)
[Verizon Motorola Droid Turbo Android Development] fgl27:
[MENTION=2640499]koftheworld[/MENTION] [MENTION=7237874]NepoRood[/MENTION]

when you creat a adition to android.mk of vendor like this:

include $(CLEAR_VARS)
LOCAL_MODULE := RcsServiceM
LOCAL_MODULE_OWNER := motorola
LOCAL_SRC_FILES := proprietary/app/RcsService/RcsService.apk
LOCAL_CERTIFICATE := platform
LOCAL_MODULE_TAGS := optional
LOCAL_MODULE_CLASS := APPS
LOCAL_DEX_PREOPT := false
LOCAL_MODULE_SUFFIX := .apk
include $(BUILD_PREBUILT)

we add a variable

LOCAL_MODULE

the name flowing it is how you "build" it...

calling on any .mk file that is load for that device

PRODUCT_PACKAGES += \
werever_is_after LOCAL_MODULE :=

in this case RcsServiceM the name can be anything as long it doesn't have spaces or some special character only test with underline and dots, others may fail... so the name doesn't matter what matter is the pats and other config under the LOCAL_MODULE ...

the way this is called RcsServiceM is because there is a open source for that, and to build it we use RcsService and can't be two LOCAL_MODULE in the build environment with the same name...

by the way that was crashing, at least it did last time I use, the source one also crash, let me know if it does and how I don't remember how it crash if is a constant crash or a phone app crash... it may not as some others things are add and they may help with that...

:good: :good:
[Verizon Motorola Droid Turbo Android Development] koftheworld:
[MENTION=7237874]NepoRood[/MENTION] newest build won't get through setup. com.motorola.service.ims.RcsServiceApp has stopped comes up and won't go away.
[Verizon Motorola Droid Turbo Android Development] NepoRood:
I gathered most of that from your post the other day, when you told me that I was adding the packages in the wrong way :good:

Also, the RcsServceM (the apk) does crash, I have a quick build running now with it removed, that should fix. I'll upload when done...