yashsingh1/xdaforums huggingface dataset:
[Sprint  Galaxy Note 4 Android Development] XORr0:
Thank you for getting us Note 4 people Nougat/LineageOS 14.1, I am very appreciative! So far this has been a great ROM, the single - only - issue I have run into is Firefox crashes 100% of the time. Actually, Firefox for Android (installed from the Play Store) has never successfully opened Firefox, not once. I've tried uninstall+re-install, reboot, repeat, tried Firefox for Android Beta, I've tried setting SELinux to permissive, etc. Nothing works for me in regards to running Firefox on this ROM.

Does anyone know a solution? I am running LineageOS-14.1-20170709-UNOFFICIAL-trltespr.

Other than Firefox not working, this really has been a solid OS. Thanks you for all the work you put into this!
[Sprint  Galaxy Note 4 Android Development] ripee:
Switch to Chrome. No joke :D
[Sprint  Galaxy Note 4 Android Development] mon0theist:
I'm having some strange issues with the external SD Card

I used to use Poweramp for my music player, but when selecting what folders Poweramp should scan, it doesn't even see my sdcard as an available option. It only sees Internal Shared Storage and that's it.

When I plug my phone into Windows 7/10 to try to transfer files, changes made on the phone don't show up in Windows. Like if I create a folder on the sdcard using my phone, if I plug my phone into Windows the folder isn't there, as if it was never actually created.

VLC player will see my external SD card but won't actually use any of the files as part of it's library

Basically it seems like there's something screwy going on with read/write on the SD Card. I even tried formatting the SD card to see if that would help but it didn't really accomplish anything.

So far the only music player that will see external SD card files is Eleven, which is fine, but the fact that it's not working with any other app is concerning.

I also tried transferring some files over to the SD card via WiFi File Explorer pro, but despite it appearing to be transferring nothing actually happened. When I went to check the folder, it wasn't there...

Not sure if this is a Nougat permissions thing or some sort of bug with LineageOS...I'm having a similar yet opposite issue with my Tab 3, it can see external storage but not internal.

Am I just missing something? Anyone else experiencing this?
[Sprint  Galaxy Note 4 Android Development] anon1135:
I installed poweramp and vlc to test it and am also not seeing my sd card. works fine with the music app that comes with the rom though. could it be a problem with those apps only?
[Sprint  Galaxy Note 4 Android Development] mon0theist:
Maybe, but then why isn't Windows able to write to the sd card if I transfer files over? I effictively have no way to actually put anything on my sd card now, which sucks since I formatted it in the course of troubleshooting lol
[Sprint  Galaxy Note 4 Android Development] freestyle_89:
sorry english my bad. VR software does not work, ex https://play.google.com/store/apps/details?id=in.fulldive.shell&hl=vi. Thank you
[Sprint  Galaxy Note 4 Android Development] Axis_OP:
Hey guys,

Is there any way to make the Fingerprint scanner work for unlocking the device?

It seems to detect the Fingerprint scanner, but doesn't use it for anything.

Thanks in advance!
[Sprint  Galaxy Note 4 Android Development] mon0theist:
SD Card itself is working fine after using the official formatter (https://www.sdcard.org/downloads/formatter_4/), but Poweramp still can't see it. It doesn't even prompt for storage access permissions. Neither does VLC.

However I just installed Rocket Player and it both prompted for storage permissions and it can see my external SD card, so now I'm thinking that it must be a problem with Poweramp and VLC. Although it's odd that it works for you but not for me. I even tried clearing Poweramp's app data but it didn't have an effect.

Does Poweramp prompt you for storage permissions when you first install it?

My GPS Lock issue is fixed after going back to stock MM firmware and getting a full GPS Lock with GPS Status & Toolbox, then re-rooting and re-flashing LOS :)
[Sprint  Galaxy Note 4 Android Development] chillingspree:
Lineage 14.1 8/25 build?

I'm wondering if anyone's flashed [MENTION=6005084]ripee[/MENTION]'s 8/25 build.

https://androidfilehost.com/?w=files&flid=162322&sort_by=date&sort_dir=DESC

I also have a few questions:

1). Is this (or previous builds) flashable & appropriate for Qualcomm variant of the trltespr?

2). Is SMS/MMS working? (i.e., users don't have to *#*#4636#*#*

3). What's working/not working?

Thanks in advance
[Sprint  Galaxy Note 4 Android Development] ripee:
trapntan has, and we know that it doesn't get past the splash screen. It's most likely the fault of the kernel. Manually flashing EmotionOS's kernel on top of my trltevzw build only advances it to the boot animation.

I crossed off the trltevzw link in my signature for the time being.
[Sprint  Galaxy Note 4 Android Development] chillingspree:
Youch. Good to know there's a temporary fix.

Am I right in remembering that this is also flashable for Sprint (per your signature)?
[Sprint  Galaxy Note 4 Android Development] ripee:
It's not a fix. The builds don't boot properly.

1) My signature contains a separate link to my trltespr builds. I know Verizon users are used to hsbadr's multivariant builds, but mine are separate. As such, please stick with your corresponding variant.

2) My trltevzw builds are currently black boxes full of mystery and disappointment: if they don't boot, it doesn't matter if the SMS/MMS app works.

3) The builds don't boot, which is problem #1 beyond which it doesn't matter what works and what doesn't ;)
[Sprint  Galaxy Note 4 Android Development] chillingspree:
GUH... That doesn't seem like fun. At all. :(

Anyway, I'm interested in the appropriate variant (trltespr) for me, so, that's what I'll shoot for. How much trouble am I asking for if I dirty flash from PJ1 (Hybrid Aroma 6.0.1)? Also, should I be concerned about having a Qualcomm chip?
[Sprint  Galaxy Note 4 Android Development] ripee:
All my trlte variants are for Qualcomm Snapdragon. You're asking for a lot of trouble dirty flashing over Hybrid Aroma. Flash stock, then TWRP, then my latest trltespr build, gapps, Magisk or SuperSU if you wish. It's a hassle but you're least likely to run into any problems this way. Oh and flash the latest N910P bootloader and modem as well, BL_CP link in my signature, but do that after you flash the stock rom.
[Sprint  Galaxy Note 4 Android Development] chillingspree:
Thank you for that! Where can I find stock? (I think I've been looking at one too many threads and have confused the hell outta myself! :D :silly: )
[Sprint  Galaxy Note 4 Android Development] ripee:
N910PVPS4DQG1

Extract the big .tar file that's inside this zip, then flash it with Odin, using the "AP" button.
[Sprint  Galaxy Note 4 Android Development] chillingspree:
Thanks! I'll give that a go.
[Sprint  Galaxy Note 4 Android Development] protechtedd:
Sprint service working, how?

[MENTION=6839828]lilferraro[/MENTION]

Thanks for making this Nougat ROM work on the Note 4! Particularly, for making the Sprint service actually work. Can I ask please how did you make the Sprint service work, whereas other Nougat ROMs I've tried so far do not work on Sprint yet? I'm doing some rom comparisons, but if Sprint doesn't work then I can't do much.

Is it just the "apns-conf.xml" file? Or is there other file(s) involved in making it work? I ask because I'm trying a few ROMs and would like to make Sprint work on them too. Thank you in advance! :fingers-crossed:
[Sprint  Galaxy Note 4 Android Development] ripee:
Old kernel still in trltespr but with a purely lineage-ified device tree

I figured out a major inconsistency in lilferraro's device tree repo I was using up to this point: the lineage.dependencies file was pointing to the old EmotionOS trlte-common repo, which no doubt introduced inconsistencies in my builds. I have imported the device tree repo into my GitHub account and "lineage-ified" it fully to bring it in line with my trltevzw repo, which compiles perfectly even if it doesn't boot.

Today's build has the new device tree but old kernel. Flash it clean or dirty over your previous build, but please give feedback.
[Sprint  Galaxy Note 4 Android Development] RagbID:
super su link not working :(
[Sprint  Galaxy Note 4 Android Development] ripee:
I don't know about lilferraro's builds, but mine include the built-in root. Unless you need SuperSU, try Magisk instead.
[Sprint  Galaxy Note 4 Android Development] asforme:
I dirty flashed over the 8/28 build. Working fine so far. LTE, WiFi, GPS and bluetooth are all working.
[Sprint  Galaxy Note 4 Android Development] mon0theist:
Does the lineage su addon package actually do anything? I flash it then run a root checker and it doesn't detect root. Perhaps I'm misunderstanding?

Just switched from Sprint to Ting (which still uses Sprint's network), and when I do a clean flash I lose mobile data connectivity. Revert to stock ROM and it works fine. 8-31 build. Should I just try factory reset instead of full advanced wipe and format?

Also not sure if it matters but on the stock ROM I had updated to new firmware QH1 before wiping and flashing LOS. Not sure if the new firmware could be an issue

EDIT: Fixed it, it was an APN issue

In case anyone runs into a similar problem, the following APN settings worked for me:

This works for me, leaving up in case anyone else runs into this issue:
[Sprint  Galaxy Note 4 Android Development] XORr0:
boot-loop after Dirty Flash build upgrade

Wanted to mention here, that I tried my first UPGRADE to a newer build this morning...

- Prior to this upgrade (attempt), I ran an all user app's backup in Titanium Backup Pro v8.0.0.2

- I was running on [MENTION=6005084]ripee[/MENTION]'s LineageOS-14.1-20170721-UNOFFICIAL-trltespr ROM, and went to upgrade via Dirty Flash to lineage-14.1-20170903-UNOFFICIAL-trltespr (today's build), and open_gapps-arm-7.1-stock-20170902. I ran into a boot-loop during startup.

-- I let the phone try to boot for a little over an hour, but finally gave-up.

- This time, I did a Clean Install, as per instructions -- using FULL WIPE (with external microsd card) -- I again went with [MENTION=6005084]ripee[/MENTION]'s lineage-14.1-20170903-UNOFFICIAL-trltespr (today's build).

-- And, again, I ran into a boot-loop :eek:

-- I'd like to mention too, that on my computer after I'd downloaded the lineage-14.1-20170903-UNOFFICIAL-trltespr.zip file, I ran a "test" in 7zip, and it passed 100% successfully.

- This whole thing very well could be me screwing something up :confused:, it was my first attempted build upgrade...

- Ultimately, I went with a Clean Install, as per instructions -- using FULL WIPE (with external microsd card) of [MENTION=6005084]ripee[/MENTION]'s lineage-14.1-20170902-UNOFFICIAL-trltespr, and it worked perfectly.

-- BTW, I am on [MENTION=6005084]ripee[/MENTION]'s BL_CP flash of N910PVPS4DQG1_N910PVPS4DQG1.tar via Odin.

Thank you VERY MUCH [MENTION=6005084]ripee[/MENTION] and [MENTION=6839828]lilferraro[/MENTION] for the work you've both put into this ROM, and sharing it with all of us!

PS: I plan on posting once more to give a report on my experience with this ROM, as I've ran into some other bumps along the road, but right now, things are working near-perfect! :good:
[Sprint  Galaxy Note 4 Android Development] jlove85:
I have a HUGE question.. when it comes to asop roms. Is there a way to have HDMI MHL connection that work? I know on TW it is native connection and will display on screen. But ASOP doesn't recognize it. Is there a way to fix that?
[Sprint  Galaxy Note 4 Android Development] ripee:
Assuming it's not a proprietary feature with a specific driver that is publicly available, this could theoretically be implemented. However, if MHL is run by a proprietary app, forget it, unless a 3rd party app exists to handle this functionality with a more rudimentary driver that may or may not be as functional as the proprietary driver in TW.

As to whether it not this is a popular enough feature to be on the devs' minds, I don't know. Given what I've seen for other devices that have dedicated microHDMI ports, ie. older Amazon Kindles, devs don't bother with this and just tell users to use Chromecast or a no-name alternative HDMI stick.
[Sprint  Galaxy Note 4 Android Development] jlove85:
Bump
[Sprint  Galaxy Note 4 Android Development] Azizsoft:
Arabic language
[Sprint  Galaxy Note 4 Android Development] sagedafirst:
cellular network not working

just installed and cant get cellular network...any help pls

i really dont want to change this ROM
[Sprint  Galaxy Note 4 Android Development] k4ever:
Having same issue. On today's build (9/11/17) with ripee's N910PVPS4DQG1_N910PVPS4DQG1.tar modem. I'm in a roaming area and had to drive into town to get a Sprint tower. I would get 5 bars with LTE for about 3 seconds before it reported no service. Phone will not stay connected to the tower or activate.

Also, is there anyway to activate the Sprint service while roaming?
[Sprint  Galaxy Note 4 Android Development] ripee:
What do you mean by Sprint service? Roaming means you're not connected to a Sprint tower. Your phone will automatically connect to the strongest tower regardless of carrier, if you enabled roaming in the settings. To manually register on another network, ie. Sprint, go to Mobile network settings, tap on Network operators, tap the circular arrow, and wait for the list to populate.
[Sprint  Galaxy Note 4 Android Development] k4ever:
Thanks for the quick reply! I just reinstalled the ROM (9/11/17 version, along with the modem/BL mentioned in my previous post) after a long hiatus on a Hybrid Note 7/Note 4 ROM. I did a clean install.

I'm stuck in a roaming area right now and for some reason the phone will not connect to any tower (even the roaming ones). Says "Emergency Calls Only." Thought I need to connect to a Sprint tower first...

Anyway I'm having another problem now. I'm not getting any sound out of the speaker (headphones work fine). May install the 9/10 ROM to see if I have better luck with it..

Ok, no sound out of 9/10 either.. I completely wiped and reformatted before install 9/10..
[Sprint  Galaxy Note 4 Android Development] k4ever:
I installed 9/2 (last ROM I see working well in thread). Both speaker sound and roaming are working.
[Sprint  Galaxy Note 4 Android Development] peteb1414:
I installed 9/11 and was unable to get voice and data. Installed 9/2 per the above post and have not run into anything not working yet. Data was available right away, voice came after a reboot or two.

It does say "Activating Cellular service" every time I reboot though.
[Sprint  Galaxy Note 4 Android Development] ripee:
Can anyone who tried 0913 please let us know:

1) does build it flash?

2) if so, does it boot without Magisk? built-in su or SuperSU is fine

3) if so, do you have SIM?

4) if so, can you add or edit APN settings?

5) do you have sound, either in multimedia or VoIP apps?
[Sprint  Galaxy Note 4 Android Development] ripee:
The 0915 build is cooking!

However, due to the sound problems with trltespr that are most likely caused by the new kernel, I will switch over to the old kernel for trltespr until _mone posts his updated device tree and blob repos.
[Sprint  Galaxy Note 4 Android Development] k4ever:
Anyone test this out? My phone is my only form of communication at the moment while my wife is out and about. Don't want to risk it until I know it's working.
[Sprint  Galaxy Note 4 Android Development] ripee:
As it's only been up for 6 minutes, perhaps not yet ;) Sorry for the delay, I had to revert my device tree back to so that it referenced _mone's old kernel.
[Sprint  Galaxy Note 4 Android Development] k4ever:
LOL! Didn't pay attention to when you posted the update..

So you think the new kernel was causing the speaker and cellular modem not to work in previous builds?
[Sprint  Galaxy Note 4 Android Development] ripee:
It wouldn't be updated blobs since I updated those back in July after lilferraro asked in the thread for someone to update them. The new kernel is significantly difference from the old one, but _mone and fattire have only brought it up to work with trltexx and trltetmo thus far. Of course trltespr, trltevzw, and other less popular Snapdragon variants will come eventually.
[Sprint  Galaxy Note 4 Android Development] k4ever:
Dirty flashed 9/15 (and Gapps) over 9/2 about 10 minutes ago. Phone is still booting... May have a boot problem.. I will give it another 10 minutes before I stop it and re-flash 9/2.

Yeah, wouldn't boot. Was stuck on boot logo for 20 minutes first time. I pulled the battery, then tried it again. Same results. Wasted 30% battery power in the process. Currently re-flashing 9/2.

Done re-flashing 9/2. Only took 5 minutes to boot. Everything back to normal. No luck with 9/15..
[Sprint  Galaxy Note 4 Android Development] ripee:
Old kernel in build 0916

But I kept the same device tree as before. If this still give you SIM and sound problems, I will go back to lilferraro's device tree.
[Sprint  Galaxy Note 4 Android Development] sircharlieg:
_mone's trlte twrp is 404 and I can't seem to find it anywhere else (although it is 03:00, I may be missing something). Is that necessary, or can I go on without flashing it?
[Sprint  Galaxy Note 4 Android Development] ripee:
Go on the main thread by jef_00, all links that work are in the OP.
[Sprint  Galaxy Note 4 Android Development] ripee:
trltetmo variant on trltespr?

Those of you who visit the main thread may have noticed that a Verizon user asked for the trltevzw codename to be added to the updater script of trltetmo to allow GSM-based SIM access on the trltevzw.

Do many of you use your Spring Note 4 on a GSM-based network? I will add trltespr to my trltetmo updater script in time for the 0917 build. Would one of you brave souls please try it tomorrow and report back?
[Sprint  Galaxy Note 4 Android Development] k4ever:
Has anyone gotten the new 9/16 build to work on their Sprint Note 4?
[Sprint  Galaxy Note 4 Android Development] ripee:
What about build 0917?
[Sprint  Galaxy Note 4 Android Development] k4ever:
Just dirty flashed 9/17. Same issue as with 9/15 -- stuck on boot logo for long time. I let the phone sit on the boot logo for 20 minutes before I pulled the battery and reflashed 9/2. Of course 9/2 only took 5 minutes to boot up.

Any brave soul out there willing to do a full wipe, then try to install 9/17 to see if it will boot? I've got to study for a test. I don't have 3 hours to spare this week doing a full wipe and setting my phone back up...
[Sprint  Galaxy Note 4 Android Development] Phititan:
Same results as dirty flash :(
[Sprint  Galaxy Note 4 Android Development] ripee:
I re-built my device tree from scratch from lilferraro's in time for 0918. Let's see if it'll work like 0902.
[Sprint  Galaxy Note 4 Android Development] _newb_:
Here's to hoping 0918 works! I'm so ready to go back to AOSP.
[Sprint  Galaxy Note 4 Android Development] ibedanny:
Besides the current issues with booting, are there any issues with Bluetooth, gps and MMS?
[Sprint  Galaxy Note 4 Android Development] sircharlieg:
For whatever it's worth, I have not yet been successful with any of the versions (I just found this a week ago and tried flashing a couple days ago).

I am in the process of attempting 0917 with a full wipe. I'm not optimistic, it's been boot screen for 20+ minutes. I'll pull battery and retry a few times to be thorough.

If 0917 does not work, I'll wait to see if the device tree rebuild in 0918 is successful. If that doesn't work, k4ever will you share the 0902 package (or direct me to another place to find it)? By the time I read the thread about 0902 being the last one to work, 0903 was the oldest one on ripee's file host. (IIRC, you are trltespr?)
[Sprint  Galaxy Note 4 Android Development] ripee:
2nd 0918 build with new kernel

_mone made some RIL-related changes in his device tree, which he set up for the new kernel anyway, so I cooked a build. His changes may help with SIM recognition.
[Sprint  Galaxy Note 4 Android Development] anon1135:
latest build crashed at setup wizard for me after selecting language. has this happened to anyone else?
[Sprint  Galaxy Note 4 Android Development] k4ever:
Which one did you use - 9/18 or 9/18 with the new kernel?

---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------

I'm glad to say that build 9/18 with the new kernel is working for me. I was able to dirty flash it over 9/2. It only took 5 minutes for the first boot (normal).

I'm reinstalling Magisk right now and will run some tweaks on the ROM.

No issues so far.

Gosh darn-it! Installing the update for Magisk caused a darn boot loop! This is ridiculous!

So I got it to boot again by re-flashing the ROM, GApps, and installing Magisk (version 12) from Aroma. Apparently 9/18 (new kernel) does not like Magisk version 14. However, now I have discovered that Bluetooth no longer works.

I am going to flash 9/18 old kernel and see if Bluetooth works with it.

Ok, now 9/18 with old kernel is stuck in a boot loop! Ugh! I've been at this for two hours now! I'm going back to 9/2...
[Sprint  Galaxy Note 4 Android Development] mon0theist:
Bluetooth won't toggle on on 9-19 trltespr build, 100% clean flash
[Sprint  Galaxy Note 4 Android Development] anon1135:
hey thx for reply I tried 9/18 with the new kernel. currently on an older one and baseband QG1 without problems I just wanted to see how different the newest build was
[Sprint  Galaxy Note 4 Android Development] ripee:
AFH Downloader 0.4.3

I took the liberty of compiling it myself from daktak's source code. Uninstall the previous version first, otherwise this one will not install.

Changelog from version 0.4.2

- Files available for download are visible again,

- Files are once again color-coded.

trltespr build 0919 and onwards contains the on-screen nav bar and the new kernel

I switched to _mone's trltespr device tree, which he set up for the new kernel. Bluetooth doesn't turn on, though, but your phone won't crash.
[Sprint  Galaxy Note 4 Android Development] k4ever:
Ripee, any word on when Bluetooth will be fix for the new kernel or how to get your builds based on the old kernel (9/3 and onward) to boot?

I'm really happy with 9/2. It has been very stable for me. However, I would like to get the September security updates but none of your ROMs with the updates are stable at this time.

Working Bluetooth is a "stability" requirement for me. I need Bluetooth for hands free driving and to receive alerts on my watch from my phone while I'm sitting in class (professors are anal about having phones out during class).
[Sprint  Galaxy Note 4 Android Development] ripee:
While I'm certainly sympathetic to the importance of having bluetooth that works, fixing it is way above my head. Please ask [MENTION=6847876]_mone[/MENTION] about it. I regret to inform you that I forgot which sources I used for build 0902, otherwise I'd go back to those.
[Sprint  Galaxy Note 4 Android Development] k4ever:
Thanks! Dropped a comment in the main LineageOS Note 4 thread. Hope [MENTION=6847876]_mone[/MENTION] can fix Bluetooth for the trltespr builds quickly.

I was excited that the 9/18 build with the new kernel was actually able to boot after dealing with the problem on 9/15-9/17 (and 9/18 old kernel), only to be heartbroken when Bluetooth wouldn't work. Almost there....:(
[Sprint  Galaxy Note 4 Android Development] k4ever:
[MENTION=6847876]_mone[/MENTION] posted a response in the main thread... had some instructions for you on how to fix Bluetooth for trltespr.
[Sprint  Galaxy Note 4 Android Development] anon1135:
any differences with the new kernel? old one is already really good
[Sprint  Galaxy Note 4 Android Development] ripee:
New N910P bootloader and modem

N910PVPS4DQH1_N910PVPS4DQH1.tar
[Sprint  Galaxy Note 4 Android Development] anon1135:
still a great rom saved me from buying the note 8
[Sprint  Galaxy Note 4 Android Development] lbcoach3347:
Delete