Database Info

No Love For Sprint N5?

What gives? It seems many of the roms in OG or in AD do not work with Sprint, data at least, on the nexus 5. A fix has been found by Team Slim, yet I don't see the roms being updated to work on Sprint. I understand some devs choose not to fix it as they don't run sprint which is fine but why not try fixing it, giving you a larger user base? I bought the N5 because I wanted a true google experience, and figured I would get to try out some awesome roms that were not available for my previous devices, but its almost the same here. This is a legitimate question, and I hope I don't get the usual high horse answer, "why don't you fix it" "we do this for free" etc etc I love that the devs put in personal time, im just looking for answers as to why a fix wouldn't be implemented if it is tested good and working.

Circaflex said:
What gives? It seems many of the roms in OG or in AD do not work with Sprint, data at least, on the nexus 5. A fix has been found by Team Slim, yet I don't see the roms being updated to work on Sprint. I understand some devs choose not to fix it as they don't run sprint which is fine but why not try fixing it, giving you a larger user base? I bought the N5 because I wanted a true google experience, and figured I would get to try out some awesome roms that were not available for my previous devices, but its almost the same here. This is a legitimate question, and I hope I don't get the usual high horse answer, "why don't you fix it" "we do this for free" etc etc I love that the devs put in personal time, im just looking for answers as to why a fix wouldn't be implemented if it is tested good and working.
Click to expand...
Click to collapse
Give it some time....... Its the ONLY CDMA carrier this phone works on... so for most of the devs this is a completely new thing
Or try fixing it yourself, like restore your APN's from a ROM with data working.

Rxpert said:
Give it some time....... Its the ONLY CDMA carrier this phone works on... so for most of the devs this is a completely new thing
Or try fixing it yourself, like restore your APN's from a ROM with data working.
Click to expand...
Click to collapse
the thing is there is a fix, and its proven to work on Slimrom/Slimkat and the code has been put up for use by other devs, that's why im asking this question is it just the devs don't want to support sprint or is there something else

I agree completely. The fix has been posted for weeks now. Any dev releasing a rom without it at this point is being sloppy.

Circaflex said:
What gives? It seems many of the roms in OG or in AD do not work with Sprint, data at least, on the nexus 5. A fix has been found by Team Slim, yet I don't see the roms being updated to work on Sprint. I understand some devs choose not to fix it as they don't run sprint which is fine but why not try fixing it, giving you a larger user base? I bought the N5 because I wanted a true google experience, and figured I would get to try out some awesome roms that were not available for my previous devices, but its almost the same here. This is a legitimate question, and I hope I don't get the usual high horse answer, "why don't you fix it" "we do this for free" etc etc I love that the devs put in personal time, im just looking for answers as to why a fix wouldn't be implemented if it is tested good and working.
Click to expand...
Click to collapse
While I agree that ROM devs should be updating their code with the fix from Slim, one thing I can suggest is maybe just try using a stock rooted ROM with Xposed framework. I am also on Sprint, and while I used to love using SlimBean for my Galaxy S 3, I am also perfectly satisfied with stock Nexus 5 ROMs with Xposed framework and GravityBox. If you're not happy with it, then it's easy to just disable the module and run along. Just something to try out if you're craving more customizability.

metayoshi said:
While I agree that ROM devs should be updating their code with the fix from Slim, one thing I can suggest is maybe just try using a stock rooted ROM with Xposed framework. I am also on Sprint, and while I used to love using SlimBean for my Galaxy S 3, I am also perfectly satisfied with stock Nexus 5 ROMs with Xposed framework and GravityBox. If you're not happy with it, then it's easy to just disable the module and run along. Just something to try out if you're craving more customizability.
Click to expand...
Click to collapse
side note do we know each other? lol same city

Is it only aosp that don't work? Stock works I assume?
Have you tried posting the link to the commit in dev threads asking for it to be implemented? If you're not doing it, maybe no one else is either
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

Circaflex said:
side note do we know each other? lol same city
Click to expand...
Click to collapse
Lol. I doubt it, though it is a small city. I wouldn't be surprised if I passed by you a few times.

Compatible ROMs from AT&T forum?

I didn't see a thread for this (unless I'm blind, which is partially true). I saw a post somewhere linking to the Dirty Unicorn ROM in the ATT gs3 section and saw that they had loads of roms. I simply wondered how compatible some of these were with the vzwS3 before I just started flashing away... Or maybe there is a list somewhere I failed to see?

That reminds me...
On my samsung galaxy nexus I used to use a script called rom switcher (or something like that) that allowed you to flash lets say a sprint rom on a gsm phone or a verizon rom on sprint and so on. Without the need for porting.
However I'm not sure if something like this would be applicable to the s3 because of bootloader differences (nexus is unlocked ofc) and other possible hardware issues. Samsung uses unified architecture on gnexus (kernel level at least) across all three platforms. So I'm guessing the same applies to the s3 and if so that wouldn't be a problem in itself so I think the only real major issues would come from the bootloader.
If there are any devs or someone with more knowldge than i who want to see the script just let me know and I'll see if I can get a link to the thread it's in the galaxy nexus apps and themes section.
Anyway just an idea that may be helpful to at least those who are not locked down.
Sent from my SCH-I535 using Tapatalk 2

Thanks for the response! Luckily I'm not locked which is exactly why I was curious. My friend just got a Galaxy S4 i337 and I rooted/safestrapped it for him but in the process noticed lots of Verizon and Sprint roms floating around which got me curious. There's gotta be someone here with said experience right?

Perhaps you could enlist the aid of mohammed.afaneh, shapesblue, prdog or mikeman?
All those guys are good people and always helping around the forums.
I've only had the s3 for a couple months (coming from a Galaxy Nexus r.i.p.) and locked on 4.3 when I got it so not really comfortable experimenting with things just yet. But basically the script just changes some very basic things like build.prop and updater script for example but it worked very well in my experience.
Sent from my SCH-I535 using Tapatalk 2

47th_Ronin said:
Perhaps you could enlist the aid of mohammed.afaneh, shapesblue, prdog or mikeman?
All those guys are good people and always helping around the forums.
I've only had the s3 for a couple months (coming from a Galaxy Nexus r.i.p.) and locked on 4.3 when I got it so not really comfortable experimenting with things just yet. But basically the script just changes some very basic things like build.prop and updater script for example but it worked very well in my experience.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I messaged prdog. Even if I can't get a specific answer I'll gladly accept any information on the topic. I'll even test out a lot of the roms if it isn't too "unsafe" and put together a compatibility list for other VZW users.

pyrite123 said:
I messaged prdog. Even if I can't get a specific answer I'll gladly accept any information on the topic. I'll even test out a lot of the roms if it isn't too "unsafe" and put together a compatibility list for other VZW users.
Click to expand...
Click to collapse
Ports are usually only problamatic with calls and messaging. You have to use Verizon modem and maybe even RIL cause ATT don't have CDMA. Biggest problem is you need Verizon kernel which we don't have.

prdog1 said:
Ports are usually only problamatic with calls and messaging. You have to use Verizon modem and maybe even RIL cause ATT don't have CDMA. Biggest problem is you need Verizon kernel which we don't have.
Click to expand...
Click to collapse
So you're saying there is no way to flash any of the roms and get them fully functioning without a supported kernel? :sadface:
I have an Aroma addiction >;O

pyrite123 said:
So you're saying there is no way to flash any of the roms and get them fully functioning without a supported kernel? :sadface:
I have an Aroma addiction >;O
Click to expand...
Click to collapse
No matter what we do we need a Kernel. Only option for now is AOSP.

prdog1 said:
No matter what we do we need a Kernel. Only option for now is AOSP.
Click to expand...
Click to collapse
Alright, thanks. It's a shame that companies overcomplicate things and can't all just see eye to eye. Oh well such is life. Maybe one day, when the world is taken over by Google, the world will be a happier place and things will be more simple.
[emoji16][emoji184]
Assuming everything applies to Sprint and i9300 ROMs as well?

pyrite123 said:
I didn't see a thread for this (unless I'm blind, which is partially true). I saw a post somewhere linking to the Dirty Unicorn ROM in the ATT gs3 section and saw that they had loads of roms. I simply wondered how compatible some of these were with the vzwS3 before I just started flashing away... Or maybe there is a list somewhere I failed to see?
Click to expand...
Click to collapse
Most of the AOSP ROMs for the S3 that are still being actively developed have moved to putting out one unified build that works on all US variants of the S3. They will use the tag [D2LTE] in the thread title to note that. [D2VZW] is the Verizon version of the phone. So you can use ROMs that advertise compatibility with either D2LTE or D2VZW. The only problem is that as you've seen, since development for the S3 was, for a long time, specific to each carrier's model, the various D2LTE ROMs are kind of spread around among the various forums for each individual S3 model. The LiquidSmooth thread in the AT&T forum, for example, seems to be the only one that gets updated anymore, even though that ROM is built for D2LTE now and works fine on the Verizon S3. Task650's AOKP build runs fine on our phones too and can be found in the AT&T S3 forum.
If you search all forums for the tag [D2LTE], that's a decent way to get an idea of what's out there now.
ETA: I left out something which I hope you know by now: your bootloader needs to be unlocked to use anything with a D2LTE tag. If you took either the Android 4.3 or 4.4.2 updates from Verizon and locked your bootloader, you're out of luck.

Jacquestrapp said:
Most of the AOSP ROMs for the S3 that are still being actively developed have moved to putting out one unified build that works on all US variants of the S3. They will use the tag [D2LTE] in the thread title to note that. [D2VZW] is the Verizon version of the phone. So you can use ROMs that advertise compatibility with either D2LTE or D2VZW. The only problem is that as you've seen, since development for the S3 was, for a long time, specific to each carrier's model, the various D2LTE ROMs are kind of spread around among the various forums for each individual S3 model. The LiquidSmooth thread in the AT&T forum, for example, seems to be the only one that gets updated anymore, even though that ROM is built for D2LTE now and works fine on the Verizon S3. Task650's AOKP build runs fine on our phones too and can be found in the AT&T S3 forum.
If you search all forums for the tag [D2LTE], that's a decent way to get an idea of what's out there now.
ETA: I left out something which I hope you know by now: your bootloader needs to be unlocked to use anything with a D2LTE tag. If you took either the Android 4.3 or 4.4.2 updates from Verizon and locked your bootloader, you're out of luck.
Click to expand...
Click to collapse
Thanks a lot for the tips. From my time at this forum I had kind of put two and two together and assumed that was what the tags stood for. I hadn't thought of using those tags for searching, though. And luckily I got my S3 last year when I did because my bootloader wasn't locked. And just days later I believe they released that dirty OTA

cyanogenmod is on the horizon

so i just found this today on
xda http://forum.xda-developers.com/galaxy-s6/orig-development/cyanogenmod-13-galaxy-s6-t3269984
it's still possible we may actually have a alpha on our notes before EOY just figured I'd put this up for you all

jameslapc2 said:
so i just found this today on
xda http://forum.xda-developers.com/galaxy-s6/orig-development/cyanogenmod-13-galaxy-s6-t3269984
it's still possible we may actually have a alpha on our notes before EOY just figured I'd put this up for you all
Click to expand...
Click to collapse
Ive been following their progress as well, I'll say its a lot closer than the exynos Note 4 ever got.
Sent from my SM-N920T using Tapatalk

Threads like that make me cringe. Full of noobs who don't know how to read and just constantly ask for things.
Sent from my SM-N920T using Tapatalk

Very exciting, I hope one of our devs will try and port it to our device

The sooner I get off of touchwiz the better in my opinion

i was just about to say that. i miss the note 4 days.
i used to flash mad roms. never again ill buy an xynos device or whatever you call it
but arter said he's not working on one for the note 5

TheUndertaker21 said:
i was just about to say that. i miss the note 4 days.
i used to flash mad roms. never again ill buy an xynos device or whatever you call it
but arter said he's not working on one for the note 5
Click to expand...
Click to collapse
You'll most likely have to switch to a different brand. Remember, they make phones for the world, not just us modders. Their in house processor is literally the best processor that has ever been, ever. No other processor can offer the power and longevity. If CM can harness that as well, that would be great but I highly doubt it.
Sent from my SM-N920T using Tapatalk

@RaymanFX maintains the Note 4 (N910C Exynos), he has a successful build for CM12 and CM13 aswell

TheUndertaker21 said:
i was just about to say that. i miss the note 4 days.
i used to flash mad roms. never again ill buy an xynos device or whatever you call it
but arter said he's not working on one for the note 5
Click to expand...
Click to collapse
Just because Arter isnt making a build for the Note 5 doesn't mean there won't be a build for the Note 5.
Folks are getting all stressed out about this but frankly this is better news than most people should have been expecting, the writing has been on the wall for awhile now in regards to the ease of porting aosp based roms on to Exynos devices.
The rumblings started back in 2013. I just think it's bad business to buy a device that costs as much as this one with an expectation that your every need be tended to by the mod community.

It's also getting to the point that you end up losing functions of the phone's now by unlocking bootloaders. They are being crafty with how new features don't work rooted or unlocked etc, it's all to discourage the modding community, hell, last I checked android pay doesn't work on AOSP. I think they are tightening things little by little.

Ducter said:
It's also getting to the point that you end up losing functions of the phone's now by unlocking bootloaders. They are being crafty with how new features don't work rooted or unlocked etc, it's all to discourage the modding community, hell, last I checked android pay doesn't work on AOSP. I think they are tightening things little by little.
Click to expand...
Click to collapse
Look at the root situation where it was handled at the kernel level. I can't really blame them to tell the truth, its sort of expected that cellular companies and manufacturers would not make it easy for the dev community. It's like a cat and mouse game, the cat will always be the cat and the same goes for the mouse.
Heck tactics like these have even bled over into computers. My Samsung laptop has secure boot firmware in the motherboard so I can no longer dual boot linux. Only way to run linux is to wipe windows off or run a live cd...

I'd definitely give it a whirl. Not sure if I'd stick with it though, I like the camera and the Spen features on this phone too much.
It's nice to see that we'll get the choice though.

Akw6190 said:
I'd definitely give it a whirl. Not sure if I'd stick with it though, I like the camera and the Spen features on this phone too much.
It's nice to see that we'll get the choice though.
Click to expand...
Click to collapse
Now would be a perfect time since me spen has been sent off for warranty evaluation..

my spen slot is messed up so something different would be nice

Sure hope one of our devs chime in and let us know they are working on porting this for us! :thumbup::thumbup::thumbup::thumbup::beer::beer::beer::beer:

From what I understand as soon as it works on the s6 it should really simple to port over. Because essentially the note 5 is a oversized s6 with a pen

jameslapc2 said:
From what I understand as soon as it works on the s6 it should really simple to port over. Because essentially the note 5 is a oversized s6 with a pen
Click to expand...
Click to collapse
Yes and no. It's working on the S6 but we can't use it on the Note 5. Not yet anyways. Still need a kernel for the Note 5 unfortunately.

I mean we are close none the less which makes me happy as there isn't much in the way of roms for my note

This does tell me it may at least boot up before Christmas I mean we still have 15 days till the year is over so it can still happen
http://forum.xda-developers.com/galaxy-s6/general/guide-dualboot-cm13-tw-t3271545

IMO, if you're going to use CM, why did you buy a note? CM typically doesn't support the pen features at all. (please correct me if I am wrong)

Roms

What is the hold up on roms? Anyone know?
Sent from my HTC One A9 using Tapatalk

Well it takes time for some developers to make a rom to the best of its ability... Would you rather want a slow buggy rom or a fast and durable rom...so give them some time and im positive they'll have new ones eventually.

There's not much developer support for this device if you haven't noticed

Yeah it just depends if your Device is compatable with the rom you want just keep searching for a rom for your phone there might or might not be one

Hope it will give a Rom with Support for Fingerprint Sensor. :good:

Maybe or maybe not just keep searching for it until you find one good luck

dillanmason said:
Well it takes time for some developers to make a rom to the best of its ability... Would you rather want a slow buggy rom or a fast and durable rom...so give them some time and im positive they'll have new ones eventually.
Click to expand...
Click to collapse
Not complaining. Just asking.
Sent from my HTC One A9 using Tapatalk

I'm not saying you are im just saying give it some time and there might or might not be one.I know that you were asking and I'm telling you in information that I have heard.

I'm afraid it looks like there isn't much developer support here. Contrast the Oneplus X which came out a few weeks later, and there are plenty of modded OEM roms as well as a somewhat functional version of cm 12.1 being worked on.
I might be moving on to that device myself. It's a shame though since the A9 is physically my favorite phone since the 2013 moto x...

Yeah developers don't want this phone apparently. Devs have to want the phone or have a big enough demand to support a device
Sent from my Nexus 5 using Tapatalk

Don't worry! The one Max was like this at the beginning to, and it turned out fine.

probably has alot to do with there being no us kernel source yet if i remember correctly, also theyre arent too many marshmellow roms yet anyway. and no kernel source for lolipop means no lolipop roms. just wait young padawan
edit: i just checked htcdev. there definitely ARE source files for att at least.
just gotta wait for somone to port something.
perhaps... pray.

Ae3NerdGod said:
probably has alot to do with there being no us kernel source yet if i remember correctly, also theyre arent too many marshmellow roms yet anyway. and no kernel source for lolipop means no lolipop roms. just wait young padawan
edit: i just checked htcdev. there definitely ARE source files for att at least.
just gotta wait for somone to port something.
perhaps... pray. [emoji14]
Click to expand...
Click to collapse
That's great news. I can't wait to flash CM 13 on this thing [emoji1]
Sent from my HTC One A9 using Tapatalk

Pan Skrzetuski said:
I'm afraid it looks like there isn't much developer support here. Contrast the Oneplus X which came out a few weeks later, and there are plenty of modded OEM roms as well as a somewhat functional version of cm 12.1 being worked on.
I might be moving on to that device myself. It's a shame though since the A9 is physically my favorite phone since the 2013 moto x...
Click to expand...
Click to collapse
OnePlus X? You live in Europe? Because that phone doesn't support any CMDA, and it doesn't support one of the largest frequencies for LTE by ATT in the US.
So, OnePlus X is kind of a fail, with worse specs than the A9...there are other options out there besides that phone that you need a "special invite"...pleaze..makes me NOT want one just because of that.

techlogik said:
OnePlus X? You live in Europe? Because that phone doesn't support any CMDA, and it doesn't support one of the largest frequencies for LTE by ATT in the US.
So, OnePlus X is kind of a fail, with worse specs than the A9...there are other options out there besides that phone that you need a "special invite"...pleaze..makes me NOT want one just because of that.
Click to expand...
Click to collapse
Well I'm on T-Mobile, so radio coverage is pretty good, although I would like band 12 LTE.
You can buy opx without an invite on Tuesdays.
As for specs, the 801 is fine with me. My 2014 Moto x had that and it was plenty fast. I think we're at the point laptops hit a few years ago where processors are just fast enough unless you are doing something special with your device.

Pan Skrzetuski said:
Well I'm on T-Mobile, so radio coverage is pretty good, although I would like band 12 LTE.
You can buy opx without an invite on Tuesdays.
As for specs, the 801 is fine with me. My 2014 Moto x had that and it was plenty fast. I think we're at the point laptops hit a few years ago where processors are just fast enough unless you are doing something special with your device.
Click to expand...
Click to collapse
Tmo and att use many of the same bands. Band 12 is all it has. That won't translate well to ppl outside of metro areas
Sent from my HTC One A9 using Tapatalk

There's a stock rooted 6.0.1 ROM based on the Dev Edition here.
Someone needs to actually try it and confirm it works.

Captain_Throwback said:
There's a stock rooted 6.0.1 ROM based on the Dev Edition here.
Someone needs to actually try it and confirm it works.
Click to expand...
Click to collapse
Great job Captain! Wish it was for Sprint lol. Kinda missing my M9 at this point tbh.

Blackcircle said:
Great job Captain! Wish it was for Sprint lol. Kinda missing my M9 at this point tbh.
Click to expand...
Click to collapse
Building a Sprint version should be relatively straightforward. What's the latest software for Sprint? If someone grabs me a boot and system image backup from TWRP, I can easily build a flashable ROM from it (in fact, anyone can, using SuperR's Kitchen).

Captain_Throwback said:
Building a Sprint version should be relatively straightforward. What's the latest software for Sprint? If someone grabs me a boot and system image backup from TWRP, I can easily build a flashable ROM from it (in fact, anyone can, using SuperR's Kitchen).
Click to expand...
Click to collapse
I honestly have not even rooted yet. Tbh...I'm a little confused on all this encryption stuff with rooting and s-off. Haven't had a day to really sit down and read in detail the process lol. If I was rooted, I would gladly get what you need sir.

LineageOS 14.1 for N920C installs on N920P just fine. Now, how to address cellular?

Howdy friends!
I was able to install the SM-N920C Lineage-14.1 ROM by RaymanFX on my SM-N920P Sprint device.
https://forum.xda-developers.com/note5/orig-development/rom-lineageos-14-1-t3572047
To make it install I simple unzipped the ROM, and edited the file "META-INF/com/google/android/updater-script" and remove the top line that starts with "assert". This line is basically the part of the script that makes the ROM abort in TWRP if your device isn't nobleltejv. Then I re-zipped the contents of the ROM, pushed via adb and flashed per the instructions in RaymanFX's thread.
It seems to run really well -- it seems more stable than the CM 13 ROM that I tried previously. However, like the CM 13 ROM, cellular doesn't seem to work.
I got a good deal on this device primarily for hacking on it, so I don't mind trying some things (although I'd prefer to avoid bricking it). My only limitation is that I am a GSM user so I can't test full CDMA functionality while I go. That being said, I don't mind grabbing a cheep prepaid CDMA SIM if I actually make any progress.
I'm looking for resources on how to diagnose why cellular doesn't work. I'm fairly new to hacking on Android, but I'm an experienced software engineer and have a strong Linux background, so I'm pretty confident that with docs I could get to the bottom of this.
If anyone with more experience in this realm can point me at the appropriate docs/examples/forums etc. I be happy to take a swing at it.

jnovek said:
Howdy friends!
I was able to install the SM-N920C Lineage-14.1 ROM by RaymanFX on my SM-N920P Sprint device.
https://forum.xda-developers.com/note5/orig-development/rom-lineageos-14-1-t3572047
To make it install I simple unzipped the ROM, and edited the file "META-INF/com/google/android/updater-script" and remove the top line that starts with "assert". This line is basically the part of the script that makes the ROM abort in TWRP if your device isn't nobleltejv. Then I re-zipped the contents of the ROM, pushed via adb and flashed per the instructions in RaymanFX's thread.
It seems to run really well -- it seems more stable than the CM 13 ROM that I tried previously. However, like the CM 13 ROM, cellular doesn't seem to work.
I got a good deal on this device primarily for hacking on it, so I don't mind trying some things (although I'd prefer to avoid bricking it). My only limitation is that I am a GSM user so I can't test full CDMA functionality while I go. That being said, I don't mind grabbing a cheep prepaid CDMA SIM if I actually make any progress.
I'm looking for resources on how to diagnose why cellular doesn't work. I'm fairly new to hacking on Android, but I'm an experienced software engineer and have a strong Linux background, so I'm pretty confident that with docs I could get to the bottom of this.
If anyone with more experience in this realm can point me at the appropriate docs/examples/forums etc. I be happy to take a swing at it.
Click to expand...
Click to collapse
Have you pm'd @RaymanFX to see if he can point you in the right direction. Also @tdunham, not sure where he stands in taking on another project. Either way hopefully you'll make some progress!!!

justlookin412 said:
Have you pm'd @RaymanFX to see if he can point you in the right direction. Also @tdunham, not sure where he stands in taking on another project. Either way hopefully you'll make some progress!!!
Click to expand...
Click to collapse
Not a bad idea. I don't really have time to be a project maintainer right now -- hoping if I make progress I can just submit a patch against Rayman's work and occasionally make any needed updates, but I don't really know how ROM projects are typically managed.
Like many folks on XDA, I love Samsung's hardware but don't care for their implementation of Android. I generally prefer something closer to stock like Lineage or AOSP. Sprint doesn't get a lot of love (although Moar is a pretty nice ROM) and I'm sure those folks who prefer something closer to stock would benefit.

jnovek said:
Not a bad idea. I don't really have time to be a project maintainer right now -- hoping if I make progress I can just submit a patch against Rayman's work and occasionally make any needed updates, but I don't really know how ROM projects are typically managed.
Like many folks on XDA, I love Samsung's hardware but don't care for their implementation of Android. I generally prefer something closer to stock like Lineage or AOSP. Sprint doesn't get a lot of love (although Moar is a pretty nice ROM) and I'm sure those folks who prefer something closer to stock would benefit.
Click to expand...
Click to collapse
I completely agree. I have no complaints. MOAR is an excellent ROM. I would like to run Lineage or an AOSP ROM just for a change, but I knew from the beginning what I was getting myself into.

I'm not sure what all needs edited, but AFAIK the RIL needs to be. How or what needs to be changed is beyond me.
Sent from my SM-N920P using Tapatalk

Moderator: should this thread live in one of the development sections?
Had a quick exchange with Rayman. He seems like a nice guy!
My objective is to get the modem working to some degree, but no promises about things like proper CDMA configuration, band selection, etc. Not really sure how all that stuff works, TBH. If I can get he modem to go, though, maybe someone who actually knows a thing or two about wireless can help with the other stuff?
Seems like the first order of business is to discover what modem hardware this thing is using, and what drivers it wants. I'll need to get root and dig around in sysfs/devfs. I'll post what I learn.
My day job is as a web developer and I'm an embedded hobbyist. Many of the ROM devs on XDA seem to work as embedded developers in their day jobs. I expect this to be a slow-going learning project for me in my limited spare time.
I'll do my best to document my progress (and foibles) in this thread in case anyone can learn a thing or two from it.

jnovek said:
Moderator: should this thread live in one of the development sections?
Had a quick exchange with Rayman. He seems like a nice guy!
My objective is to get the modem working to some degree, but no promises about things like proper CDMA configuration, band selection, etc. Not really sure how all that stuff works, TBH. If I can get he modem to go, though, maybe someone who actually knows a thing or two about wireless can help with the other stuff?
Seems like the first order of business is to discover what modem hardware this thing is using, and what drivers it wants. I'll need to get root and dig around in sysfs/devfs. I'll post what I learn.
My day job is as a web developer and I'm an embedded hobbyist. Many of the ROM devs on XDA seem to work as embedded developers in their day jobs. I expect this to be a slow-going learning project for me in my limited spare time.
I'll do my best to document my progress (and foibles) in this thread in case anyone can learn a thing or two from it.
Click to expand...
Click to collapse
It seems like talking to him has steered you in the right direction!!! Take your time. If anything you'll learn something that you can apply later in your career or personal projects!

Have u tried flashing the sprint modem?

@jnovek if you could provide the zip you put together to flash I would try something in my spare time to help. Doesnt seem to be a very busy thread.

Long time no chat. I've been busy .
Could someone post the output to "getprop" from a stockish Sprint device on 7.x? Among other things I'd like to see what magic incantations are used for the ro.telephony settings.

hackwoof said:
@jnovek if you could provide the zip you put together to flash I would try something in my spare time to help. Doesnt seem to be a very busy thread.
Click to expand...
Click to collapse
Not totally sure how to use the hosting that everyone here uses and I have limited time this morning to play around w/this, but I can give you brief instructions on how to roll it yourself. It's super easy.
1) Download the n920c rom linked in the first post.
2) Unzip it.
3) Edit the file "META-INF/com/google/android/updater-script".
4) Remove the first line -- it starts with "assert". You can just straight up delete it.
5) Zip everything back up.
6) Flash using the instructions provided in the linked thread for n920c.

Any headway here?
Sent from my SM-N920P using Tapatalk

link
Done according to guidelines by jnovek
If anyone can check

No time today. But I'll make a backup and try it tonight.
Sent from my SM-N920P using Tapatalk

It installs fine. No service tho.
Sent from my SM-N920P using Tapatalk

What that mean "No service tho"

It means the RIL and APNs need to be edited and added I believe.
Sent from my SM-N920P using Tapatalk

S Pen works?
I flashed the rom, but S pen is not working anymore. And has anyone figured out how to set up the network?

The developers of the ROM are working on it. But as of now this ROM is not for our phones unless you're going to only use it on WiFi. Cellular connections of any sort are out of order.
Sent from my SM-N920P using XDA Labs

Bump