yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Android Development (Snapdragon)] galakanokis:
I answered above, N910W8 is the Canadian variant of the Note 4. Always go by model number not the rest of the info on the sticker. As far as phone info goes those can all be changed with build prop edits so pay them no mind.

If you have previously flashed the latest, November 2016 version of your carriers stock ROM than you do not need to worry about charging radios or bootloaders again, the are no new ones.

Since the kernel fix my signal has been great on Rogers here in Vancouver.
[Galaxy Note 4 Android Development (Snapdragon)] GerardSamija:
Yes, well, great for you with Rogers. Perhaps if I were with Rogers my data connection would be solid, or perhaps not, I've no way of knowing with this phone. The previous owner was with Telus and said he had no connection problems. I'm with Freedom. I was only asking about which to try because _mone seems quite confident from my Phone Info and stickers that trltecan is the way to go for bootloader and modem. A message like ripee's, unfortunately, doesn't do anything to tell me which variant aside from W8 I ought to try, in order to follow _mone's advice. 910T or 910F? Which of these is compatible with or analogous to trltecan?

I tried a BL and CP last night using clues from one post in the Canadian Note 4 thread, the ones from 2015 called N910W8VLU1COK3. Connection was 100% solid for about an hour before bed. This morning I found it disconnected. Toggling data reestablished the connection and it has been good except for one brief data drop in the hour I've been awake. Will ride it out today with this older pair flashed and see if it's sufficiently better than the fairly good connectivity I have already with 10/24 and the November 2016 BL_CP pair.
[Galaxy Note 4 Android Development (Snapdragon)] merc200k:
I am trying rom for my n9100 note 4..i confirm not working... error 7 at recovery...
[Galaxy Note 4 Android Development (Snapdragon)] galakanokis:
Keep in mind that the Note 4 isn't fully supported on the Freedom Mobile network, it doesn't cover all of the frequencies that the carrier uses. https://willmyphonework.net/.

There is nothing else to try other than a W8 variant, either Telus, Rogers or Bell, Thats it. trltecan is just a unified build of the canadian note 4's bootloaders and radios since they are all the same, pretty much what ripee has linked in the OP. At one point in time it referred to twrp builds as well but I think even that has been merged into trlte or something.

Flash a Telus stock image since at one point it was the closest to Wind as far a frequencies coverage goes and go from there. Once that is done and you load a custom recovery you shouldn't need to touch odin again except to go back to stock, the bootloader and radio are as good as they are going to get.
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
Once again, the most obvious diagnosis is poor carrier coverage.

My BL_CP combo for the N910W8 is from 2 different stock roms, but yes, the PK1 modem remains the latest one for the Canadian variant.

To simplify things for everyone, switch to my unified builds and report bugs in those.

[MENTION=8678616]phonecat[/MENTION], [MENTION=4697695]merc200k[/MENTION], are you able to flash my unified build?
[Galaxy Note 4 Android Development (Snapdragon)] GerardSamija:
Huh, that's odd. When I use that page to see if my phone works with Freedom it only says 2G doesn't work with Freedom. It gives check marks for 3G and LTE. Perhaps 2G is a fall-back within the phone, when Freedom's 3G signal gets weak for a moment for whatever reason (like I happen to walk past a metal object which is between the phone and the nearest repeater), and that's when it's disconnecting? I know LTE isn't an option for me, as Freedom only supports the higher speed with a few models they currently sell, don't allow access for legacy devices.

Well since it was a Telus-issued phone, it has already had a Telus stock image flashed, initially. I'm failing to see how re-flashing such an image would amend the situation, especially considering how as you're saying, 2G isn't supported, and this incomplete band support may well be the specific problem for my Note 4. In which case perhaps I ought to be considering saving up for a fully supported device, rather than continuing to try making a hopeless case work for me. But then that's odd, considering how the custom 6.0.1 ROM (lame as it was in other ways) which came with the phone when I bought it used had zero data connection problems. And as I recall, RR and AICP ROMs also kept me connected... though perhaps my memory is faulty there. I did stick to the same BL_CP with those versions. I do remember there were other reasons I didn't stay with those versions, things which got in the way of daily use for me. I like this Lineage, which would be perfect if it stayed connected.

So far under the older files, BL_N910W8_RWC_COK3.tar and CP_N910W8_RWC_COK3.tar, connectivity is a bit better. As I mentioned earlier, I'll see how they do over the whole day, then update to the November 2016 versions if it seems there's been no long-lasting improvement.
[Galaxy Note 4 Android Development (Snapdragon)] brajangdippy:
Can someone help please?

I tried to install TWRP recovery using the app and must have screwed it up. When I try to boot into recovery I get a screen very similar do Download mode but at the top it says "Could not boot normally". I tried to install TWRP recovery using Odin but I get the same message when I try to boot into recovery. The phones boots up normally by just pushing the power button.

Did anyone know how I can get back to being able to boot into recovery?

Thanks in advance.
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
Power off the phone, boot into Download mode with the button combination, and try again through Odin using the "AP" button. If that doesn't work, flash a stock recovery and start over with TWRP in Odin. Which variant do you have?
[Galaxy Note 4 Android Development (Snapdragon)] galakanokis:
The yellow check mark is described as below.

Result Device is compatible with some of the network carriers frequencies. It may work.

2G is the old school GSM network and voice/sms only no data and I don't think Freedom even uses it. So the issue for you is strictly 3G disconnecting on Lineage ROMs? Not sure if that narrows things down a bit to see what the differences are in the sources for Lineage.

I was only suggesting to Flash stock Telus as a bit of a reset. Every now and then I flash stock on these Samsung phones just to reset things and start from a fresh base.
[Galaxy Note 4 Android Development (Snapdragon)] GerardSamija:
I see. I'll give it a try when I have time.
[Galaxy Note 4 Android Development (Snapdragon)] tripLr:
I have been Bluetooth audio books all day, WiFi worked this morning no problem

Front camera and finger print worked

I flashed pico

I am currently trying to find info on how to get my modem from 3g to 4g (it happened when I switched from the rootable 5.11 to the old February build on the other lineage is thread that i didn't know was buggy, then to RR, then to the 1023 build here

Somewhere in the process I upgraded the modem and lost 4g

Straight talk wireless works seamlessly in 3 g roaming data since then streaming with IHeartRadio app.

So pretty stable, just a little slow

FYI I drive truck in SW Washington state. Lots of hills and mountains. I have only about 5 known dead spots on my route, so I know its not the build or the modem or Verizon or straight talk.

Keep it up. Gonna find my Galaxy Note apps eventually to install

---------- Post added at 01:07 AM ---------- Previous post was at 01:06 AM ----------

Noob looking for logcat instructions. Will be back with it

Thanks
[Galaxy Note 4 Android Development (Snapdragon)] fbarcenas:
Do not restore your modem to something from 5,11. You are just asking for trouble and battery drain.

---------- Post added at 03:33 AM ---------- Previous post was at 03:28 AM ----------

I've seen a modem not take before reflash the newest modem you have but uncheck the reboot option in odin. When it's done flashing the first time, pull the battery. Re install the battery and boot directly into download mode, do not let it boot into the system. Repeat the flash and pull the battery. Put it back in and let it restart normally and check.
[Galaxy Note 4 Android Development (Snapdragon)] k4ever:
Will someone else who is using the latest version of this ROM on a Sprint Note 4 (or any of the other versions) please check to see if your GPS is actually working?

Just so we are talking the same language, check that your GPS is working -- not location services! Just so you know you are only checking GPS, go to the Location setting and set it to "Device Only," then turn off WiFi and cellular data so that apps like Google Maps (which ignores the location settings) will be forced to use GPS only. Actually, don't even use Google Maps to test GPS, use another application like Waze. Make sure to clear the cache (or data) on Waze before you use it to test, just to make sure it is not using a cached GPS location. You need to be standing outside to test GPS, just to ensure you have an unimpeded link to the GPS satellites.

I think some of you are confusing Android's other location services (WiFi and cellular data triangulation) with GPS. These location services are running when your phone is in "High Accuracy" or "Battery Saving" modes. These are not GPS! Don't let that fool you!

Why does this matter? Well when you go into a bad coverage area, like when you are out in the middle of nowhere, these services fail. If GPS only is not working, then your navigation app become useless when you need it the most. I have had this happen to me several times, which is why I have reported repeatedly that GPS is not working with the Sprint version of this ROM on the new kernel builds.

Edit: Almost forgot, when you are in Waze (and fully logged in) tap the little bubble in the bottom right hand corner of the app. If you get the warning "No GPS Reception" and the app doesn't go to your location in about 30 seconds or so, then GPS is not working.
[Galaxy Note 4 Android Development (Snapdragon)] fastguy:
I'm on October 27th TMO build. Gps works. Bluetooth works. No data drops, I used for 4 hours straight today.

Then only issue I found is that my charger (not fast, but normal Samsung 2a one) only charged my phone up to 91%. I tried twice and it never hits 100%. (it used to fully charge in some earlier versions).

I'll try as well with a quick charger.
[Galaxy Note 4 Android Development (Snapdragon)] brajangdippy:
Thanks Ripee. I have the N910F. What stock recovery do I use? I am running 6.0.1
[Galaxy Note 4 Android Development (Snapdragon)] maksimreder:
To Any of the devs, can I dirty flash the latest build? I know a clean flash is always preferred, but I have everything setup on my 10/24 build, and hate to reload everything.
[Galaxy Note 4 Android Development (Snapdragon)] phonecat:
Which unified build

[MENTION=6005084]ripee[/MENTION]

Do you mean the 'lineage-14.1-20171029_050123-UNOFFICIAL-trlte.zip' ? Should I try this?

Update : Tried 'lineage-14.1-20171029_050123-UNOFFICIAL-trlte.zip' , failed in device verification, says my device is trlteduoszh(N9100).

reocovery log(TWRP 3.1.1.0) :

I:Set page: 'install'

I:Set page: 'flash_confirm'

I:Set page: 'flash_zip'

I:operation_start: 'Flashing'

Installing zip file '/external_sd/lineage-14.1-20171029_050123-UNOFFICIAL-trlte.zip'

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

I:Update binary zip

I:Zip does not contain SELinux file_contexts file in its root.

I:Legacy property environment initialized.

script aborted: E3004: This package is for device: trlte,trltedt,trltecan,trltespr,trltetmo,trlteusc,trltevzw,trltexx; this device is trlteduoszh.

E3004: This package is for device: trlte,trltedt,trltecan,trltespr,trltetmo,trlteusc,trltevzw,trltexx; this device is trlteduoszh.

error: 3004

Updater process ended with ERROR: 7

I:Legacy property environment disabled.

I:Install took 0 second(s).

Error installing zip file '/external_sd/lineage-14.1-20171029_050123-UNOFFICIAL-trlte.zip'

Updating partition details...

I:Data backup size is 4492MB, free: 2557MB.

I:Unable to mount '/usbstorage'

I:Actual block device: '', current file system: 'vfat'

...done

I:Set page: 'flash_done'

I:operation_end - status=1

I:Set overlay: 'slideout'

I:Set overlay: ''

I:Set page: 'clear_vars'

I:Set page: 'install'

I:Set page: 'main'

I:Set page: 'clear_vars'

I:Set page: 'main2'

I:Set page: 'advanced'

I:Set page: 'copylog'

I:Set page: 'action_page'

I:operation_start: 'Copy Log'

I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
If you flash a stock rom, it will flash its own stock recovery along with everything else.

https://live.samsung-updates.com/index.php?device=SM-N910F

Choose any of the ones whose PDA Version ends with "I6", regardless of Region. If this flashes successfully, go through its setup wizard until you get to the home screen. Then start over with TWRP in Odin, etc. Note, while this stock rom will give you the latest bootloader automatically, it won't give you the latest modem, so flash the .tar file in my BL_CP for the whose file name starts with N910F.

First make a backup in TWRP of your existing 1024 installation, then dirty flash today's unified 1029 trlte build.
[Galaxy Note 4 Android Development (Snapdragon)] teegale:
Just clean flashed the now unified 10/29 ripe build. Everything is good but phone won't fast charge? Worked fine on 10/24 vzw specific build.
[Galaxy Note 4 Android Development (Snapdragon)] lbcoach3347:
You have GPS working
[Galaxy Note 4 Android Development (Snapdragon)] teegale:
Not sure. I'll test it later and get back to you.
[Galaxy Note 4 Android Development (Snapdragon)] brajangdippy:
Thanks.

Can I install the 10/24 ROM from this thread? Will that install a recovery that functions?
[Galaxy Note 4 Android Development (Snapdragon)] logosA:
there are 2 (two) kinds of recovery.

1. Stock recovery

This comes with the stock rom , which you have to flash it to your phone, using odin in order to get a working stock rom with a working (stock) recovery.

There is no way to flash just a stock recovery. You have to do the whole package.

2. Custom recovery

These days and when we talk about Lineage roms, we have in mind TWRP. This is suggested to be used and preferred in order to be able to flash your custom rom (or modifying your stock rom) without a problem.

Unlike the stock recovery, TWRP can be flashed alone and not with a custom rom together.

In fact you have to first flash TWRP so be able to boot in it and flash your custom rom.

Flashing custom rom, is not flashing / repairing your (custom) recovery.

So , NO , flashing the 10/24 rom will NOT fix your recovery.

You CANNOT flash the rom if you first don't fix your recovery.

Conclusion:

1. use odin to flash a STOCK ROM in your phone

This will give you your phone as it was getting out of the factory.

NO custom recovery, no root, just what Samsung gives with a stock rom, with the stock recovery on it.

So if you want to go back to Custom rom, you will have to do it all from the begin.

(TWRP, ROOT, Custom rom)

If you want to go that way, use link [MENTION=653821]rippe[/MENTION] gave you, find the latest stock rom for your phone and flash it with odin.

2. INSTALLING/repairing the TWRP custom recovery:

go here:

https://eu.dl.twrp.me/trlte/twrp-3.1.0-0-trlte.img.tar.html

I believe said your phone is N910F, if its not, choose the right for you

TWRPtrlte___.tar(qualify for your model)

Get to download mode. - HOME+POWER+VOLUME DOWN

open odin (3.12.3 or later) running it as administrator

Put TWRP.tar that you have downloaded in AP slot.

Uncheck AUTO-REBOOT

.

Flash it.

When odin mark as PASS, unplug your phone and wait for 10 sec

Take off your battery and wait another 10-15 sec.

Put back battery and press the combination to boot in recovery - HOME+POWER+VOLUME UP

(If it doesn't, do it allover again.)

Make sure that everything is working as it should in your recovery.

Go to ADVANCE> reboot> recovery

if it boots ok,

reboot system.

good luck
[Galaxy Note 4 Android Development (Snapdragon)] SUREFACE:
Leaving the Note 4 Family !

First thanks to @ripee , @_mone and to All Others for Our Hard Work!

I Leave the Note 4 Family!

At the Last Weeks my Note 4 did More and More Problems, and I`m not Able to Fix them!

At that Point I changed to a Nother New Device!
[Galaxy Note 4 Android Development (Snapdragon)] maksimreder:
Damn. 10/24 build has been so solid I just don't want to flash anything else. Has there been any updates or bug fixes since the 10/24 build aside from a unified build?
[Galaxy Note 4 Android Development (Snapdragon)] teegale:
Honestly, if it ain't broke don't fix it. I just downgraded back to the 10/24 Verizon build. The 10/29 unified build broke a few things for me that worked in 10/24, like fast charging. I have absolutely no issues with 10/24 other than a few force closes every now and then. No reason to update again for awhile.
[Galaxy Note 4 Android Development (Snapdragon)] maksimreder:
I have to agree, fast charge broke in unified build, also the same apps force close in variant build 10/24 and latest trlte build, for some reason the ui was laggy, I set my settings in kernel auditor like setting SE enforcing to permissive and tuning the governor. My phone runs much cooler in 10/24 build.
[Galaxy Note 4 Android Development (Snapdragon)] _mone:
lol

great attitude!
[Galaxy Note 4 Android Development (Snapdragon)] teegale:
I'm sorry if I came off as unappreciative. That wasn't the point of my post. It was coming from a user standpoint, as to what build is currently ideal as a daily driver. All I meant by it was that as of right now it isn't worth upgrading to the unified build because you lose functionality. When I said "if it ain't broke don't fix it", I did not mean in terms of a developers standpoint. I apologize if I offended you or other developers, as I appreciate all your work.
[Galaxy Note 4 Android Development (Snapdragon)] maksimreder:
Hey [MENTION=6847876]_mone[/MENTION]. No need to throw me under the bus lol, I'm just sharing my experience with the unified build. I needed to restore back to 10/24 build for this week as I need it for work. I don't mind testing, just can't do it this week. Sorry if I offended you. Appreciate all your work, you are one of who make this rom possible. I got nothing but respect for you.
[Galaxy Note 4 Android Development (Snapdragon)] _mone:
Nevermind, I probably misunderstood your posts!

To be clear, the impression was "**** this unified build, it doesn't work, let's go back to 10/24". From your last posts I now understand that it wasn't what you meant.

I'm long time working on this device and lately, with the big user requests, I'm trying to provide support for every snapdragon variant (even if I only own a trltexx). And this unified build is just an idea that can help me to maintain all the different variants. If it's not worth the pain, I'll just drop it and try to maintain all the different device trees.. but as usual I can't do much w/o the support of you users.

So, please, if something doesn't work try to grab and share some logs instead to just tell this/that is not working.
[Galaxy Note 4 Android Development (Snapdragon)] teegale:
I'd be happy to grab logs but I'm not sure how. If you could provide a link to a guide or explain to me what to do it more than happy to. I test new builds frequently but have only communicated my issues without logs. I didn't realize that it wasn't helpful.
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
Please stick with the unified build as long as possible before giving up on it! :) Also, would it work on the N9100 if trltechn and trltechnduosz were added to the updater script? Obviously only the first SIM slot would be functional.

I have no idea how you lost fast charging with the unified build, my N910F charges the same as on trltexx.
[Galaxy Note 4 Android Development (Snapdragon)] GerardSamija:
Well I tried, did share logcats and dmesg files a few times. But looking from the other end of the telescope, as an end user with just the one working phone (I have an 8 year old Windows Mobile 6.5 HTC Kaiser... but it just reboots randomly so no real utility there) and no budget to replace it, I need the basics to work at least most of the time. Data improved for me significantly with 10/24. I tried each successive release to 10/29. But data drops got worse again with those, and jumping back a couple of times to 10/24 it got better. Still dropped too often though, and with a trip coming up next week where I'll really need reliable data, that's just not good enough for me, the end user. Wish I could stick around and offer what logs and reports I could on newer builds but for now I've had to bow out.

Hope I'm not coming across as resentful, as I'm not feeling that at all. _mone and ripee and others have contributed so much effort into this problem. Otherwise Lineage was really rocking for me! I enjoy the day to day experience using these ROMs much more than anything else I've tried on the Note 4, and I'd settled on Lineage for my previous Note 3 for similar reasons (though data was perfect there). But I've been chastised repeatedly by developers and more so by other members who routinely (but not always) insist that the data drops are my individual problem, not common to the build generally. My repeatedly stating that 6.0.1 gave me a flawless data connection went mostly ignored.

Well, I'm now on hour 8 with NotaBene_v1.0. Not one second of dropped data connection in all that time - which I know, as I've been busy setting the dang thing up though all that time, from scratch, all the many hundreds and hundreds of adjustments and installations and logins to various sites and setting up email and FTP and other accounts, using system app remover to de-bloat... all of it a chore, but with perfect data reliability and an otherwise perfectly stable phone, it's going to be worth it once perfectly set up the way I like it. I'll have a true daily driver. And yeah, the laggy screen response typical with Lineage is every so slightly worse with NotaBene_v1.0, but only about 20% slower to react to gestures. And yeah, Marshmallow is a bit depressing to look at, and the user tweak options are a lot fewer. But it's working great.

So without bitterness and only a little self pity, I'm going to stick with that for now and consider coming back to Lineage if/when the data problem specific to my variant (whatever that is still not being entirely clear) is resolved, whenever someone makes a breakthrough and finds the bug which is definitely in the software (NotaBene_v1.0 shows the same modem and baseband as the last one ripee posts in his sig for this variant, so it has to be in the ROM) I'll come back and continue testing. Really would like to see that happen. Just can't be part of contributing my trivial reports to it now.
[Galaxy Note 4 Android Development (Snapdragon)] mon0theist:
No mobile data issues? GPS is working?
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
Added trlteduosz to the unified build updater script

[MENTION=8678616]phonecat[/MENTION], please try this one:

lineage-14.1-20171030_073141-UNOFFICIAL-trlte+trlteduosz.zip

It's identical to trlte in my AFH folder, except I added the extra 2 lines to its updater script file to allow for flashing on trlteduosz. It's expected that the 2nd SIM card slot will not work, but please let us know if you find any other bugs than the ones commonly mentioned here by other single-SIM variant users.
[Galaxy Note 4 Android Development (Snapdragon)] mx-5driver:
[MENTION=3386304]AbuFiraas[/MENTION]

No Idea what kind of Variant you have - I have a SM-N910F and I boldly flash almost each Daily Build.

Except the known Camera Issues and Call-History Isssues in the recent Past I did not face any major Issues.