yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Android Development (Snapdragon)] maksimreder:
Well I on the other hand do care about video recording, as I record my families memories on my phone, and create small video clips as my kids grow up, so i will stay on 6.0.1 until these two main issues are fixed.

as for the data drop, install google duo from the playstore, and start a video call, and attempt that several times, and you will see the data drop on each time, turn off your wifi of course, and when you start the video call the video will be fill screen but during the video call swipe down and open your notifications during the video call and you will see the data drop,

---------- Post added at 02:51 AM ---------- Previous post was at 02:44 AM ----------

That there summarizes my experience, no data drop during idle, BUT when I browse the web, or send email, etc, data drops during forum submission, or right when I press end on an email, and all last about 20-30 seconds at the most, then as more traffic is generated data drops drops again. It's not a timed interval, but happens when you least expect it.
[Galaxy Note 4 Android Development (Snapdragon)] mon0theist:
Hmm looks like the jury's still out on the mobile data issue lol.

Does anyone know if Magisk is working with the new unified builds? I had this really weird issue where Magisk would do something to my phone's partitioning and most apps couldn't see my external SD card anymore, but SuperSU works just fine. Even stranger, it doesn't happen on the Official builds for my Tab 3. Updating from Magisk 13 to 14 didn't help. Never was able to determine what was causing it and it seems like I'm the only one who's experienced it because I know others here are using Magisk.
[Galaxy Note 4 Android Development (Snapdragon)] Texas_Ace:
The updated bootloader seemed to work at first but after flashing the 10/21 version again it would lock up during boot, even after wiping and flashing several other roms including a full odin flash back to stock, it would not boot.

I flashed an older modem and bootloader and it finally started booting again.

So Is there any reason to update the bootloader? Or is the modem the only thing that matters? I assume that the bootloader was the issue, I will test only flashing the modem tomorrow.
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
I see none of you have addressed the issue of the speakers not working in-call. Is trltexx the only variant on which this is a bug?
[Galaxy Note 4 Android Development (Snapdragon)] negativman:
lineage-14.1-20171022-UNOFFICIAL-trlte. The speaker does not work when making a call. They hear me, I can not hear.
[Galaxy Note 4 Android Development (Snapdragon)] mbr007:
And data is dropping.
[Galaxy Note 4 Android Development (Snapdragon)] mrrhq:
I just want to know if this version of Android fixes the KRACK Wi-Fi vulnerability.

I really need to upgrade from my Cyanogenmod phone, and I'm still waiting for some Oreos. But I think this, along with probably Dirty Cow and others, probably warrants an upgrade already...
[Galaxy Note 4 Android Development (Snapdragon)] weissnix:
Same here.

N910F / trltexx
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
Going back to variant-specific builds for the time being...

It looks like I jumped the gun a bit too early, my fault.

Individual builds are cooking right now.
[Galaxy Note 4 Android Development (Snapdragon)] GerardSamija:
No problem with phone calls on mine, W8, sound working fine both ways. Only tested with 10/21 so far as no one has called me yet under 10/22.
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
What about the other bugs on N910T, any changes between trlte and trltetmo?

Do the speakers work in-call on trlte flashed on N910P/R4/V? I removed the trlte builds because of this mission-critical bug. However, if one or more of the device-specific variants aren't plagued by this bug, I'll discontinue only those variants in favour of trlte while still building for the remaining variants that have this bugs.

The 1022 builds are up now.

[MENTION=4573886]Texas_Ace[/MENTION], which variant is your phone?

[MENTION=7879394]mrrhq[/MENTION], is that wpa2 vulnerability really that important to you? I challenge you to google Gerrit Code Review and see for yourself how many days ago that patch was merged into the codebase.
[Galaxy Note 4 Android Development (Snapdragon)] unsignedLong:
Thanks ripee!

Sound/speakers bug is gone. GPS is ok and no data drops.

Note4: SM-N910F
ROM: lineage-14.1-20171022-UNOFFICIAL-trltexx.zip
BL/CP: N910FXXS1DQI7 / N910FXXU1DQE3
Info: clean ROM install with full wipe
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
Yes, it does, but we need to know if in-call speakers work on trlte for N910P, N910R4, and N910V.

If anyone else can confirm that speakers work in-call on the unified build on N910T, N910T3, and N910W8, I will switch trltetmo to trlte.
[Galaxy Note 4 Android Development (Snapdragon)] Texas_Ace:
N910P

Going to start some more testing in a little while to see if the 10/22 version works better.

What should I do about the modem and bootloader? It is really hard to understand which version I should use from the links in the OP. Just a bunch of random letters in file names.
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
Did your speakers work in-call on trlte 1020 or 1021?

In my BL_CP folder, find the one that starts with N910P. They match the model numbers ;)
[Galaxy Note 4 Android Development (Snapdragon)] Texas_Ace:
Strange, that page was not loading yesterday so I ended up using one from the other links. I will download that one and see how it does.

Sound worked in all the test calls I made when I had working data, sadly I do not remember which nightly they were as I flashed at least a dozen times yesterday.

I will be trying the 10/22 version in a few hours though, I will report back then.

Oh yeah, does it matter when you flash the bootloader and modem? Should it be before or after lineage?
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
Don't worry about reporting on 1022, we know it works. No it doesn't matter when you flash them.
[Galaxy Note 4 Android Development (Snapdragon)] maksimreder:
I have the N910V,

I did not get the latest trlte before it got removed to test, but the one I do have is the 20/10/17 build and in-call works fine, speaker works good, they can hear me and I can hear them, with speaker and no speaker.

GPS works great..

Data drops continue to happen from time to time, with traffic demand is more noticeable, have not noticed it drop while phone is idling,

and camera app does not recognize the video camera when I press record.

Update: Downladed trltevzw 22/10/17 and data drops continue to happen from time to time, not as often as before, but big improvement, GPS works fine, and video camera does not record video, says cannot recognize the camera in either of the camera apps.

Update 2: Camera and Video Camera works, I downloaded "Open Camera" from the playstore it is working great on the 22/10/17 trltevzw build, the bundled camera app does not recognize the video camera, I used "system app remover (root)" app from the play store to remove it. So far data has been great, I do get a few drops here and there, but better than it was,
[Galaxy Note 4 Android Development (Snapdragon)] fbarcenas:
There are newer modems listed for your phone, but your modem was released 12/2016 so it not that old and should work just fine. Did you come from a Dirty Flash? There have been reports of the N910W variant having that problem, so I'm not that entirely surprised. Have you tried the network settings reset option on your mobile and recreating the mobile data options?
[Galaxy Note 4 Android Development (Snapdragon)] GerardSamija:
Clean flash, after another clean flash to try _mone's first multi-version trlte version which (as I reported) gave me significant data connection problems. And I've reset network so many times in so many versions... It sometimes helps for a bit, sometimes doesn't. I'm not clean on why these occasional questions about data drops and specific users keep coming up from various members, considering that the Lineage team and _mone have some weeks ago acknowledged that the data drop problem is a known issue and one for which there is as yet not a fix, nor even an understanding of the cause. It is common to at least a couple of variants.
[Galaxy Note 4 Android Development (Snapdragon)] mbr007:
Tmobile- Data is dropping...lineage-14.1-20171022-UNOFFICIAL-trltetmo.zip
[Galaxy Note 4 Android Development (Snapdragon)] fbarcenas:
Then you my friend have an opportunity to really help out all of those having that problem. You can upload your logs to a paste-bin. Use the aLogcat app in the Google playstore if possible. When you contact the Dev to find out where and how he (or the lineageos dev team) would like to receive the logs, let us all know. I would send my logs as well if I notice the same problem.
[Galaxy Note 4 Android Development (Snapdragon)] GerardSamija:
Have you been following this thread? I've uploaded logcats, as well as a number of dmesg.txt files at _mone's request, for various versions. No solution to the data drop problem has been announced. No further logcat or dmesg requests have been made.
[Galaxy Note 4 Android Development (Snapdragon)] fbarcenas:
This is my second day following this thread. So please forgive my ignorance.

Thank you for your efforts in helping resolve this problem! Hopefully together we can all contribute and make a difference.

---------- Post added at 06:58 PM ---------- Previous post was at 06:41 PM ----------

Try https://play.google.com/store/apps/details?id=net.sourceforge.opencamera many people that have reported problems with the built in camera have installed this camera and have used it with great success.
[Galaxy Note 4 Android Development (Snapdragon)] GerardSamija:
Okay. Well, when I acquired this Note 4 in August I did a lot of searching. And when I settled on ripee's Lineage builds I read this entire thread to get up to speed. As I have done in every development thread relevant to my interests going back to Windows Mobile 6.5 in 2009, which has seemed to me to be a minimum requirement prior to submitting criticisms. XDA threads might be 75% shorter if every new follower of every thread took the time to at least skim the entire thread.
[Galaxy Note 4 Android Development (Snapdragon)] Texas_Ace:
475 pages of skimming at a minimum of say 2 minute a page would equal almost 16 hours of solid reading just to figure out how to install a rom.

Just slightly impractical to expect people to invest that much time into a choice of a rom IMHO.
[Galaxy Note 4 Android Development (Snapdragon)] GerardSamija:
Sure. Hence my point about reading first. If everyone did change their practices as such we wouldn't have 475 pages to read, as most posts tend to be along the lines of 'hey, can anyone tell me if this ROM is okay as a daily driver?' and 'is GPS fixed yet?' or other questions and statements which are similarly uninformed. Even going back ten or twenty pages would eliminate the need for most of this sort of posting.
[Galaxy Note 4 Android Development (Snapdragon)] rob_z11:
Have you tried running test kernel 4 that he uoaded about week ago or more? I didn't have any data lose using that kernel, but since than switched to stock since I am traveling for 10 days
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
Here's an idea: rather than bombarding this thread with reports of data drops on each and every build for each and every variant, how about you all hold off until data drops are fixed and then, and only then, report your excitement to the rest of us?!

_mone does read your posts so he knows very well what works and what still needs work...
[Galaxy Note 4 Android Development (Snapdragon)] GerardSamija:
Yes, I've tried all the test kernels, but unfortunately none gave me 100% or even 90% data connection reliability. So I'm back to running nightlies without test kernels nor build.prop edits. So far the briefly-shared ripee 10/22 trlte build is cutting out data about twice as frequently as the 10/21 build, his first unified release, which itself was proving slightly more reliable than _mone's one unified build. I switched away from that _mone build primarily because of the camera errors, which for me aren't present in 10/21 nor 10/22.

---------- Post added at 12:06 PM ---------- Previous post was at 12:02 PM ----------

My apologies if these excess reports are bothering you ripee. Perhaps you've not noticed that they are primarily in response to other users, who are directly quoting me and asking for details. I replied to _mone's requests for reports as well. I shall fall back now on not reporting data drops further, thank you for clarifying that data drop fixes are not yet included. I misunderstood _mone's comments, apparently...
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
They're not bothering me, and I'm not addressing you specifically. But constant data drop posts are not exactly useful at this point.
[Galaxy Note 4 Android Development (Snapdragon)] logosA:
Tip, in trltexx 20/10/17 build, infrared remote control on tv and media devices is again working. (In Septembers builds was not) :)

Not very important but its helpfull for some of ud
[Galaxy Note 4 Android Development (Snapdragon)] len207:
Hey guys I have a real problem with my Note 4! I have an N910P (Sprint) that ran well for a couple hours after I got it off of ebay. Then the problems started. I had it rooted with Magic's and a TWRP recovery all was good. But I decided to get the latest TWRP for this phone. I got a coy from the Play Store and ran it with the latest version of the recovery. After I had gotten everything set up I tried to boot into recovery and then BIG problems. I could not tap on any section of the GUI in TWRP nor could I use the slider. I was finally able to reboot into the system with a battery pull but the problem persisted. I can scroll the home screens left and right and somewhat up and down. All icons on screen require selecting an area about an inch above the icon wanted. The very top and very bottom of the screen seem to not be working. Now the kicker, if I use the pen everything works exactly as expected!! I have tried to reload the stock firmware but it always fails. I also installed the stock recovery and ran a system reset. It ran but to no avail.

I have no idea what the problem is, whether hardware or software. Either way if anyone has any idea of what might be the problem or even more important a solution I would be grateful! My thanks in advance for any assistance!
[Galaxy Note 4 Android Development (Snapdragon)] GerardSamija:
Just a thought... but are you having this problem with the phone in a tightly fitting case? Or does the problem persist with the phone out of a case, nothing touching along the screen edges? Sometimes the wrong sort of contamination, even a small crumb of food or water along the edges, can cause a 'short circuit' of sorts in the screen, disabling input in total or in part. If not this, I'd suspect a hardware fault, perhaps the phone was dropped.
[Galaxy Note 4 Android Development (Snapdragon)] maksimreder:
See post below for steps to fix.
[Galaxy Note 4 Android Development (Snapdragon)] maksimreder:
Steps to fix the touchscreen sensitivity loss from a bad flash.

Open your dialer and type in

*#2663# then select TSP FW Update (General)

Wait a few seconds and should restore your functionality.

Your carrier my prevent you from opening the secrets code, like mine did, Verizon didn't allow me to enter the code, I luckily had a rooted rom when this happened and download the"phone info - Samsung"' from the play store and select the menu in the app and be go to "secrets codes" scroll to 2663 and do "Launch 0" which will ask for root, Grant the rights and I'll be you to the tsp screen.
[Galaxy Note 4 Android Development (Snapdragon)] logosA:
Testing the phone info*SAMSUNG*, that is mentioned above, I found out that method suggested is only aplied in stock rooted phone.

But searching the app around I found out that it can be used to trace and (maybe) download the latest stock rom available for our phone/model/region/csc code. It could be handy looking whats new in stock BL and CP. Take a look if you like
[Galaxy Note 4 Android Development (Snapdragon)] fbarcenas:
Relax man. This isn't a life or death situation. Nothing to be so intense over. I highly recommend you do what I do when I think I'm going to get worked up over something. I just take a shot of Tequila and play a favorite song and chill out. :D :highfive:

---------- Post added at 12:02 AM ---------- Previous post was at 12:00 AM ----------

That is what the FAQ is for on the first or second post, usually. People read those ya know. I sure did.
[Galaxy Note 4 Android Development (Snapdragon)] mrrhq:
Excuse me, but yes. That vulnerability is important to me, just like any other ones. I'm sorry you feel like you have to challenge me to something. Maybe you're the one being mentally challenged here?
[Galaxy Note 4 Android Development (Snapdragon)] Luminar2010:
Generally agree, but someone asking about how it functions as a daily driver can only be answered by current users experience, that can't be found in the OP. As for current bugs and their status, I don't think they are specially on the OP either. People are encouraged to report bugs, but really there is no easily accessible log for them to check the progress of their report, or even if it was acknowledged at all
[Galaxy Note 4 Android Development (Snapdragon)] nicholes:
Hi guys, I have a few questions.(Sorry for the noob questions, and / or If already have asked)

Do i need to flash bootloader and modem while i Am rooted and installed TWRP already?( Right now I am on Stock 6.0.1 N910F)

What exposed version works in this rom ?( SKD23 arm based)have you tested?

If i have to install bootloader and modem and if i stuck on bootloop or anything. Can i get back to my rom using backup which i have already done in my recovery(full backup done only data is not backed up )

Do I need to purchase Spen apps in order to make spen work?

Thanks.
[Galaxy Note 4 Android Development (Snapdragon)] Texas_Ace:
Is it possible to get an unrooted boot image for the latest versions? I noticed that in the older pre ~9/02 builds they were unrooted if pulled out of the zip and would accept magisk without an issue.

The latest versions seem to cause a boot loop if you flash magisk and you can't mix the old boot image with the new rom without the same issue or I also get a boot loop.
[Galaxy Note 4 Android Development (Snapdragon)] len207:
Thank you! That appears to have solved the problem, at least for now. Never knew of that code or what it can do.
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
I cooked another unified build because not enough people had the chance to test it and give feedback. This is for trltetmo, trltespr, and trltevzw users

ONLY!

lineage-14.1-20171022-UNOFFICIAL-trlte.zip

trltexx users: in-call speakers still do not work, so there's no reason to flash this and report any feedback about this bug.

Please dirty flash it over your current build and let us know if the speakers work in-call. Please do not report about other bugs yet, there's not as critical as the ability to make phone calls. Please do not complain about data drops, they will most likely still happen on this build. Please also mention the variant of your phone, either in your post or add it to your signature or profile.

I am asking for very specific feedback and I would appreciate very specific feedback. If you do not feel comfortable in flashing this build over top of what is working for you already, you are not missing out on any new features, so do not worry. The reason why I am asking for very specific feedback is to know if I can replace any or all of the above variant-specific builds with this one, therefore having fewer builds to run in total and more time and processing power to run builds more frequently, should any significant changes be implemented in the code.
[Galaxy Note 4 Android Development (Snapdragon)] GerardSamija:
Just flashed the 10/22 unified build second uploaded version and tested using voicemail service (it's late, can't call anyone). Both regular speaker and speakerphone speaker worked fine - trltetmo variant again.
[Galaxy Note 4 Android Development (Snapdragon)] hkris:
Clean flashed your new unified build on my trltevzw N910V, I can confirm that in-call audio works on both speakers.
[Galaxy Note 4 Android Development (Snapdragon)] fattire:
TMO kernel quick-fix.

Sorry so I haven't been following the thread lately, but I think I narrowed down the mobile issue for 910T (tmo). It's working for me now. No more choking on streams.

The fix to the kernel would look something like this. Basically add two lines:

diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index 231fd71aa6f..7128e02eb32 100644
--- a/drivers/usb/host/xhci.c
+++ b/drivers/usb/host/xhci.c
@@ -1328,11 +1328,13 @@ int xhci_urb_enqueue(struct usb_hcd *hcd, struct urb *urb, gfp_t mem_flags)

if (usb_endpoint_xfer_isoc(&urb->ep->desc))
size = urb->number_of_packets;
+#ifndef CONFIG_MACH_TRLTE_TMO
else if (usb_endpoint_is_bulk_out(&urb->ep->desc) &&
urb->transfer_buffer_length > 0 &&
urb->transfer_flags & URB_ZERO_PACKET &&
!(urb->transfer_buffer_length % usb_endpoint_maxp(&urb->ep->desc)))
size = 2;
+#endif
else
size = 1;

_mone or corinna, once it's confirmed by others... feel free to add it to the kernel.
[Galaxy Note 4 Android Development (Snapdragon)] mx-5driver:
[MENTION=6005084]ripee[/MENTION]

Hi ripee,

is there a specific Reason why todays Build for the trltexx does not follow the usual Naming Convention ?

lineage-14.1-20171023_065112-UNOFFICIAL-trltexx.zip

I am a bit "irritated" about the "_065112" after the Date - wondering what it means & whether I should flash it or not ?

Can you please explain ?
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
So was I, but the S5 dev, haggertyk, merged a commit last night so as to make it easier to identify unofficial builds if more than one is cooked in a single day. You can find it on Gerrit.
[Galaxy Note 4 Android Development (Snapdragon)] mx-5driver:
More than one ROM cooked for a single Day - where is the 2nd one ?

I am afraid I am as confused as before - your Explanation would make Sense to me if I would see 2 Builds coocked for today here:

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

However I can just see that single one ?!

Where is the second one you are talking about ?
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
I'm afraid you misunderstood me. That commit serves to differentiate more than one unofficial rom zip file cooked in a single day by one or more builders. This has nothing to do with there being more than one 1023 build from me today, or any other day. In retrospect, this change makes sense, but I'll ask them to change the random number to a time stamp.

https://github.com/LineageOS/android_vendor_cm/commit/2179abe87e5f4bb79053160ce7cafca2c9fe3bc4

---------- Post added at 03:15 PM ---------- Previous post was at 02:52 PM ----------

Speaking of more than one build in a single day, I merged this quick fix into my fork of the new kernel and I'm building a 2nd trltetmo build that could potentially not have data drops. Check the folder in about an hour and a half.

If this works, I'll run 2nd 1023 builds for trltespr and trltevzw.

lineage-14.1-20171023_162147-UNOFFICIAL-trltetmo.zip(data drop fix)

FYI, the time stamp in the zip file name is GMT time ;)
[Galaxy Note 4 Android Development (Snapdragon)] Rjergbohn:
Will lineage 15 come for n910f ?