[T-Mobile Galaxy Note 4 Android Development] fattire:
I think the issue isn't so much that you need to kick rocks, but that it's hard to figure out what's the issues are when people say "I can't send SMSes" without mentioning that they are using a Sprint device or whatever. There is no one who has stepped up to support the sprint devices and there is no sprint support in this release, so when people are reporting problems and not saying it's a non-tmobile device, it's confusing for those of us who need to fix it.

If you go to the 910F porting thread- I posted some instructions about how to fork the trltetmo device repository for sprint (or whoever) and how to select the right kernel configuration. If there are other differences in hardware or partitions or whatever (you can consult with TWRP's fstab file) you'd need to account for them in the BoardConfig and other files there (I don't have any idea if there are). You'll want to rename "trltetmo" to "trltespr" (or spt or sprnt or whatever the convention is) both in the file names (full_trltetmo.mk) and in the file content, examples:

Android.mk:ifneq ($(filter trltecan trltetmo,$(TARGET_DEVICE)),)
BoardConfig.mk:TARGET_OTA_ASSERT_DEVICE := trltetmo,trltecan
BoardConfig.mk:TARGET_LIBINIT_DEFINES_FILE := device/samsung/trltetmo/init/init_trlte.c
BoardConfig.mk:BOARD_RIL_CLASS := ../../../device/samsung/trltetmo/ril
BoardConfig.mk:-include vendor/samsung/trltetmo/BoardConfigVendor.mk
cm.mk:$(call inherit-product, device/samsung/trltetmo/full_trltetmo.mk)
cm.mk:PRODUCT_DEVICE := trltetmo
cm.mk:PRODUCT_NAME := cm_trltetmo
device.mk:$(call inherit-product-if-exists, vendor/samsung/trltetmo/trltetmo-vendor.mk)
device.mk:DEVICE_PACKAGE_OVERLAYS += device/samsung/trltetmo/overlay
extract-files.sh:export DEVICE=trltetmo
full_trltetmo.mk:$(call inherit-product, device/samsung/trltetmo/device.mk)
full_trltetmo.mk:PRODUCT_NAME := full_trltetmo
full_trltetmo.mk:PRODUCT_DEVICE := trltetmo
full_trltetmo.mk:PRODUCT_MODEL := trltetmo
README:(trltetmo, trltecan, etc)
setup-makefiles.sh:export DEVICE=trltetmo
vendorsetup.sh:add_lunch_combo cm_trltetmo-eng

In particular, make sure you change the defconfig:

TARGET_KERNEL_VARIANT_CONFIG := apq8084_sec_trlte_tmo_defconfig

to

TARGET_KERNEL_VARIANT_CONFIG := apq8084_sec_trlte_spr_defconfig

(you'll need to make some minor changes to the defconfig to get MTP and the vibrator to work. Same thing we did for TMO. Look at the kernel history or check out the 910F thread where we're talking about it. It's like three lines to comment out.)

Then you'd probably need to create a directory vendor/samsung/trltespr too, and, looking at the trltetmo folder as a reference, add in the blobs for your ril and make sure they get copied to the right place on the phone. (Before you do this, make sure that they actually work though...) But this is where you put those "blobs".

then brunch trltespr (or trltespt or whatever the hell it is) and start fixing errors :)

Basically your particular device (trltetmo, trltespr, trlteintl, etc.) will pull in the generic trlte stuff (trlte-common) which in turn uses generic qcom stuff (qcom-common). That way, if you make a change in trlte-common, let's say get nfc working, it will benefit ALL the trlte devices. If you have something specific just for the sprint phone that has nothing to do with say, tmobile, put it in trltespr and it won't affect the tmo version. Make sense?

When your device repository is ready on github (or wherever you are hosting it), you will amend your roomservice.xml file (see post #2 in this thread) to include a line like this:

<project name="YOURNAME/android_device_samsung_trlteYOURVARIANT" path="device/samsung/trlteYOURVARIANT" remote="github" />

Then start a thread if it doesn't exist already telling people where your repository is located so they can pitch in. Be sure to check with slayher's trltetmo origianl repository in case there's anything exciting that changes there which you might want to reproduce for your device too.

Hope this is helpful. I'll post a link to the above in your thread, if I can find it. (Update: Couldn't. But anyway.. there ya go.)

Update: here is an example sprint device folder, the note 3 one. Just so you can see what it might need.