yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
This has nothing to do with the updater script. Please flash TWRP 3.2.1-0: https://dl.twrp.me/trlte/

I gotta add this to the FAQs in the OP :P

---------- Post added at 10:18 PM ---------- Previous post was at 10:14 PM ----------

Thank you for gifting me XDA Ad-Free status, whoever you are! :D

I just got an email from XDA that someone from this thread gifted me this. While I understand you wish to remain anonymous, if you see this post, please know that I am very grateful for this gesture and I plan on sticking around XDA for as long as possible.

However, my efforts are nothing compared with the high level of skill and hard work of _mone, micky387, and cvxda. I'd much rather transfer my Ad-Free status to each of them, so let me suggest that they be given Ad-Free status as well.
[Galaxy Note 4 Android Development (Snapdragon)] kerfex:
Hello Everyone. OK so after years of not wanting to mess up my CM13 install. I finally upgraded to the proper modem and bootloader. I have a N910V and am on CPD1. I have a file I found here on XDA with just the latest bootloader and Modem (I think) so BL_910VVRU2CQ12.tar.md5 and CP_910VVRU2CQ12.tar.md5 . If I flash these with Odin, am I going to loose my unlocked bootloader? I have never flashed just a Bootloader or modem file.

In the mean time I am running the May 7th build. I downloaded it last month when I read here it was stable. And mine is. Sim works. Camera for still works. ( I have not tested video. ) Everything seems to work. Now I have not tester Bluetooth or GPS yet but so far, Love this Rom. Thank you Ripee and Mone_ and anyone else whom has contributed Thank for you answer in advance.
[Galaxy Note 4 Android Development (Snapdragon)] logosA:
15/ 6 / 18, everything is working here
[Galaxy Note 4 Android Development (Snapdragon)] mon0theist:
Anyone know what's up with the SELinux Disabled thing? Seems concerning...
[Galaxy Note 4 Android Development (Snapdragon)] Eclipsep379:
I get the SELinux error too and my sim death on 615 has almost be come fatal and I'm going a build back for now
[Galaxy Note 4 Android Development (Snapdragon)] AndyYan:
[MENTION=8752689]ttipstrying[/MENTION] Thanks for the tip on disabling dual-SIM via build.prop, got my N9100 up-to-date again. First time that cellular is functional since early May (when ripee removed his own trlteduos trees).

(I use the device with only 1 SIM; purchasing N9100 instead of other variants is only because it's easy to find)

For other N9100 users who are wondering, in /system/build.prop, change

persist.radio.multisim.config=dsds
ro.multisim.simslotcount=2

to

persist.radio.multisim.config=none
ro.multisim.simslotcount=1

Save and reboot.
[Galaxy Note 4 Android Development (Snapdragon)] wrfavre:
Im not familiar with build.prop changes can you give me a little more info so I can try and do this on my N9100 as well, or post your version of the build for some of us to try?

[MENTION=6005084]ripee[/MENTION] could you make this change to the current build and post it in the basket. If this works i am sure all of the N9100 users would love to have at least on sim working. Thanks
[Galaxy Note 4 Android Development (Snapdragon)] ripee:
persist.radio.multisim.config=none is the only line that's killing SIM 1. _mone disabled it a while back in his quest to adapt the approach used in the stock rom to handle both SIMs. The only thing he is sure of is that the Note 4 duos handles dual SIM capability differently than the S5, which had been the basis of our inspiration from the get go. I can comment it out regardless of what the simslotcount line is set to and it should fix SIM 1 at least.
[Galaxy Note 4 Android Development (Snapdragon)] jackstyle:
[MENTION=4467696]AndyYan[/MENTION]，Is mic working well?
[Galaxy Note 4 Android Development (Snapdragon)] fattire:
Wow this works really well on 910t (so far)

Hey guys-- sorry I've been gone a spell. Saw the progress on 15.1 and decided to give it a build for my 910T (aka US T-Mobile, aka trltetmo). Hadn't built 15.x in months so I love the work that has been done, especially with the unified build stuff.

I did a repo init -b lineage-15.1 from the 15.0 to the 15.1 source, then had to do a couple changes below, but it all built fine and seems to work pretty well as far as I can tell. I flashed it right over my 14.1 build (which was a flash over 13, which was a flash over 12... I haven't done a non-dirty flash really for years) I now have wifi, mobile network+calling, bluetooth, NFC, accelerometer, camera, headphone, speaker, mic, sdcard... etc.... GPS seems to work too (although one app I was using to test GPS reset the system, so I deleted it and tried another GPS test app... that one did show my location + multiple satellites so I guess it's working...? I'm not 100% sure on this one but it seems to.)

You guys--- [MENTION=6847876]_mone[/MENTION], [MENTION=6005084]ripee[/MENTION], [MENTION=4251307]micky387[/MENTION] -- etc have been doing some great work!

I do get that platform warning on on start as well as the warning about being in permissive mode. This is surely a dumb question but again, I haven't been following this thread-- the only selinux denial warning I'm seeing in logcat is for vmstat. I'm now trying a setenforce 1 from adb shell to see if it causes any problems and will report back. If not, maybe I'll just build it to stay enforcing.

Anyhoo-- here are the changes I used to get it working for me. Please note I didn't exactly do the unified build thing I don't think because I wasn't sure exactly how it works as far as making changes go.. I didn't see a trltetmo repository that was obvious to use (does unified still use them?) so just modified an old one on samsung-apq8084 which seemed to work okay. I started with something like this roomservice.xml As mentioned, I'm still using the cm-14.1 branch of the trltetmo repo. Here are the changes I made to it. The only other repo I had to change was to trltetmo-vendor.mk in the vendor repo, which you can see here. Probably didn't do everything I should have done, but this was the minimum I needed to get it working.

For me, doing a 'brunch trltetmo" resulted in a working lineage-15.1-20180616-UNOFFICIAL-trltetmo.zip, and as far as I can tell on par with 14.1, but it's only been a short few hours, so I won't guarantee anything. Someone who's already building the US T-Mobile (trltetmo) build can compare notes anyway.

If TMO was already working perfectly, sorry- I really just popped in to say hey and, just in case, wanted to share the changes I made to get it going in case it was useful to anyone. May not apply to the unified build way of doing things at all.

Cheers, :good:

ft
[Galaxy Note 4 Android Development (Snapdragon)] AndyYan:
Camera autofocus still takes some time to come up after opening the camera app, though for my use case this is negligible.

I don't have a chance to test out in-call mic, but it does work for both the built-in recording app and camcorder.

You should really use this chance to look up how to modify build.prop instead of sitting around, it's simple. The line(s) are towards the end of the file in the "RIL" section.
[Galaxy Note 4 Android Development (Snapdragon)] Maxpawner:
Same here when walk around outdoor i lose signal random, most time when signal was weak before like in a Mall.

Gesendet von meinem SM-N910F mit Tapatalk
[Galaxy Note 4 Android Development (Snapdragon)] mon0theist:
So does anyone know if the "SELinux Disabled" error is something expected? Is that a problem? Seems like a security issue I guess, I don't really know. But every time my phone reboots I get warned about it so it seems concerning

As far as functionality is concerned I've had no issues so far with the 6-14 build, just concerned about this SELinux thing
[Galaxy Note 4 Android Development (Snapdragon)] Eclipsep379:
I started with 610 and had sim death maybe twice a day and no SELinux error. Just system error on boot. I tried 615 and didn't have any sim death for half the day and then it became constant and SELinux error on 615.

I went back to 614 last night and still get a SELinux error but no sim death today yet.
[Galaxy Note 4 Android Development (Snapdragon)] Shizzle2889:
Alright, just updated to the 16June release from the 24May release. This was a clean rather than dirty install. All seems to be good except a couple things. SELinux warning that plenty of others seem to be having. It seems, and I may be wrong, but to be getting set to permissive mode on boot which i believe is causing this. Changed it to enforced mode with an (unsafe if you will) app I had found on a separate forum here on XDA. From there fixed that for that run time, but then I had Play Store yelling at me about an unsafe app. Past that, rebooting brings it back up in permissive mode. Not sure if this helps or not in trying to debug, but hope so.

My other issue I have is the finger print scanner. With the 24May release, it was spotty at best. With the 16June release, the phone is not recognizing the finger swipe at all as far as I can figure. With the May release, it seemed the more finger prints registered, the more responsive it was. I also never had an issue in it recognizing the swipes, just issues in getting it registered. This release, i seem to be unable to get any registered as it won't recognize the swipe at all. Anybody have a fix for this or troubleshooting I can try for this?

... OK, appologies. Spoke too soon in regards to fingerprint scanner. Finally got it working, and not sure what caused it to work all of a sudden. My only guess was installing xposed framework, which currently runs ok with this rom, but the modules cause a ton of crashing and boot loops. Anyways is I got 2 fingers scanned and registered. After, started throwing errors. Was able to get 1 more registered through the errors, but gave up on trying to get a fourth.
[Galaxy Note 4 Android Development (Snapdragon)] fattire:
More fun stuff

Hey, thanks... So if you've enabled developer mode and turned on adb (with root enabled), you can do this:

$ adb shell

trltetmo:/ $ su

trltetmo:/ # setenforce 1

At this point if you go to Settings->About Phone->SELinux Status you should see "Enforcing". At that point there's no real guarantee of what will or won't work well now that the security policies are enabled... On restart it will returned back to Permissive.

Speaking of security policies, I spent a few hours today trying to figure out the sepolicy settings to let the simcard work on boot in Enforcing, but after about 20 rebuilds and reflashes its' not there yet. I think some mdm_helper/sysfs and other access is needed that may be blocked by another policy, but anyway I am not a selinux expert. It also doesn't help that the lineageos repo for android_device_samsung_apq8084-common contains an /sepolicy directory full of stuff, whereas I'm using the samsung-apq8084 repo for android_device_samsung_apq8084-common, which does not have this folder. I think its contents MAY have been moved to the samsung-apq8084 trlte-common /sepolicy folder, but I wasn't around when this was all set up. It looks like [MENTION=4251307]micky387[/MENTION] & [MENTION=6847876]_mone[/MENTION] did most of those commits tho, so hopefully they can set me straight on where the policies need to be changed so I don't have to track it all down. (I hate this sepolicy stuff.) [MENTION=4251307]micky387[/MENTION], [MENTION=6847876]_mone[/MENTION], any thoughts?

ft
[Galaxy Note 4 Android Development (Snapdragon)] frili:
Latest rom. Apps open very slow.
[Galaxy Note 4 Android Development (Snapdragon)] kerfex:
OK, So I have been running 06/15/18 build for the last few days. Here is what I have experienced:

1) Sim - Death. No sim death except with certain Magisk modules. OK when I installed I did a clean install. Installed Magisk and modules i used were Viper for Android and Doze for Google play services. All was fine. I then installed a few more and I got sim death. Removed them and rebooted no more sim death. I am working on narrowing down which module caused this but it is taking a while because of observation 2.

2) Terrible battery life/drain: I have 3 batteries, 2 almost new, one stock. I have calibrated all of them. They all only last 6-7 hours max. I have Greenify killing everything. Nothing starts on boot except the system and google services and Gsam batter monitor pro. Battery usage say that barely uses any power. So I don''t know what is draining. I have Wifi and data shut off when screen is off, So no constant scanning. So I do not understand why the battery life is so bad.

3) Mobile data will not connect to 4G. Only 3G and I live right near a tower.

4) As many have stated, fingerprint scanner does not work.

5) As many have stated the SELinux bug. Is permissive and get warnings, yada, yada. Downloaded the XDA app change to enforcing and waring goes away, but in settings under security, it still says not activated.

6) When I boot up, in the status bar where the network name should be (Verizon). It first say 0123456, then says Roaming indicator off. I have it switched on in settings.

7) Using Magisk, and Xposed installer for Magisk and Magisk module for Xposed framework SDK 27; the phone will not boot.

The good:

Everything else, Camera works fine. Still and video. Bluetooth works with my old hands free ear piece. Calls work, GPS works fine for me, locks on right away. Over all really smooth and great ROM. Thanks Ripee and Mone_ and Micky397!
[Galaxy Note 4 Android Development (Snapdragon)] NortonRAdix:
Hi

I do not know since which build it does work but with today's build I can install and use normally netflix.

Things are getting better and better.
[Galaxy Note 4 Android Development (Snapdragon)] Da_Mak:
In 13/06 build, you can't.
[Galaxy Note 4 Android Development (Snapdragon)] wrfavre:
Ok thanks that would be great. I will keep my eye on the basket for the dl.
[Galaxy Note 4 Android Development (Snapdragon)] stylemessiah:
[MENTION=6847876]_mone[/MENTION] [MENTION=6005084]ripee[/MENTION]

0617

Selinux, and system process error on boot ("Android is starting" and several seconds delay before desktop) still there

Too early to say on Sim death.
[Galaxy Note 4 Android Development (Snapdragon)] logosA:
I had a thing is the previous 3 versions.

Everytime I made or received a call, after answering it , phone is turning black, while speaking and no way to turn on, until call ends.

No matter what button you are pressing, call could be ended, only if the other part hang up, also screen remains black in all that time.

Making a proximity sensor fix, seems to make bug go away, but only until next reboot, when proximity fix has to be made again.

Has anyone of you meet this kind of behavior?

SM-N910F
[Galaxy Note 4 Android Development (Snapdragon)] Scolaro:
I didn't have the sim death issue for more than a week, only knew it was still there because you and some others posted about it - until 0617.

Right after the dirty flash I had to reboot 5 times in order to get sim again (usually rebooting once or twice at most did the trick).

Selinux as well (also for a couple of versions now), but no process error for me.

Trying 0618 now.
[Galaxy Note 4 Android Development (Snapdragon)] NortonRAdix:
Hi,

One question related to notifications. Since some few build I have not the option to discard next alarms before the time.

Do you have the same issue? I guess is a LOS related problem.

Have a nice day
[Galaxy Note 4 Android Development (Snapdragon)] rwalli:
6/17: did not lose signal for one day but after rebooting today signal lost again.

rebooted 3 times did not help, only "wipe cache" helped.

just looked at the cache - partition, but found nothing related to cellular network,

will try to reproduce this on 06/18 next time when i lose signal.

Robert
[Galaxy Note 4 Android Development (Snapdragon)] _mone:
Hi there!

Test build for trlte users:

lineage-15.1-20180618-UNOFFICIAL-trlte.zip

This build has SELinux in enforcing mode.

As [MENTION=3041959]fattire[/MENTION] was telling that in his trltetmo with SELinux enforcing there were issues with the SIM, today I've addressed all the denials that were in my logs and setted SELinux to enforcing and it seems to run just fine on my trltexx (SIM is working as in permissive mode), so, can anyone test this build and let me know how it goes?

Also I'm not getting any system errors, if this is still an actual issue, try to use MindTheGapps as I think there are some problems with opengapps at the moment. If the system error issue is gone already, nevermind and use whatever gapps you like.
[Galaxy Note 4 Android Development (Snapdragon)] Dopeone:
Great Rom 618 clean install just if i take a picture with WhatsApp and i press the back Button the Phone reboot but Video call via WhatsApp and Facebook are really good
[Galaxy Note 4 Android Development (Snapdragon)] clod22:
Thank [MENTION=745549]mone[/MENTION],

Yes now SELinux is enforcing,
[Galaxy Note 4 Android Development (Snapdragon)] stylemessiah:
SIM not available during pixel setup (opengapps aroma (usual gapps for me)), and so with 2 factor auth on its impossible to authenticate and compete setup....

Will try telephony wipe

Update:

Flashing telephony wipe zip did enable SIM and completed pixel setup just now...
[Galaxy Note 4 Android Development (Snapdragon)] _mone:
Cool. So I guess no problems with the SIM for you!? Which variant do you have?

hmm. Which variant? Can you grab some logs please?

EDIT: Didn't see your update.. What telephony wipe zip did you use? Can you share the link?
[Galaxy Note 4 Android Development (Snapdragon)] stylemessiah:
910G

Used WipeTelephonyProviderData.zip by hsbadr from OP under WipeTelephonyProviderData
[Galaxy Note 4 Android Development (Snapdragon)] _mone:
Thanks. LOL, sorry.. I don't really follow the OP, ripee is the one that usually takes care of it!

I'll have a look at what it does.
[Galaxy Note 4 Android Development (Snapdragon)] clod22:
910 F
[Galaxy Note 4 Android Development (Snapdragon)] stylemessiah:
Cheers, and further update, after several reboots SIM death again

Trying another telephony wipe.....
[Galaxy Note 4 Android Development (Snapdragon)] _mone:
Yeah, the changes in this build don't fix the occasional SIM death. I can't debug that issue atm. With this build I would like to know if every variant is ready to go enforcing or not.

btw the zip you linked doesn't do anything "special", if that's only what it takes to bring every device to enforcing mode I can include it in the ROM.. I'll wait some more feedback though.
[Galaxy Note 4 Android Development (Snapdragon)] Note4Addict:
[MENTION=6847876]_mone[/MENTION] I've tried both your new build and MindTheGapps on my N910F but I ran in some trouble with messages that Truecaller couldn't run unless Google Play services got updated and that SPenCommand couldn't run with selinux enforced. Also, it started with the usual Process system isn't responding so MindTheGapps didn't eliminate this. So, for the moment I went back to today's build. Thanks for trying so hard to improve this ROM.
[Galaxy Note 4 Android Development (Snapdragon)] _mone:
Thanks for reporting back and sorry but I don't really care if SPenCommand can't run with SELinux in enforcing mode.. the whole point of this test build was to see if every variant can run in enforcing mode... once we manage to get it running in enforcing mode I'm afraid you'll have to set SELinux to permissive yourself if you want to use that app.

Not sure what's causing this system error then, as (really strange) I'm not getting it.
[Galaxy Note 4 Android Development (Snapdragon)] clod22:
Same here like Note4Addict, but I have not system error 910 F. work like butter.
[Galaxy Note 4 Android Development (Snapdragon)] kerfex:
Houston, I have a problem. Ha ha. OK so I was running the 06/15/2018 build and all was going fine but I was on the CPD1 and decided to upgrade my modem and bootloader to the latest. Saw Ripee's file for BL_N910VVRUCQ12 and CP_N910VVRUCQ12 and bricked my phone. I can get into download mode and still have Unlocked developer. Problem is, I can not boot into TWRP Recovery. Does anyone have a zip file of just an unlocked bootloader and modem I can flash so I can Odin TWRP? Thanks.
[Galaxy Note 4 Android Development (Snapdragon)] Eclipsep379:
N910T

614

Noticed today streaming music with the screen off for probably half an hour and when I turned the screen on to check the time I saw No Service at the top and then my music stream cut out. I wonder if it would have stayed on if I left the screen off and the sim died when I hit the power button for the screen
[Galaxy Note 4 Android Development (Snapdragon)] fattire:
in total denial

I just did a build w/the latest sepolicy-- the results are here. No SIM on TMO, and the denials are indicated. I did a build with a few additions giving some generous permissions to mdm_helper and audio_server:

diff --git a/sepolicy/audioserver.te b/sepolicy/audioserver.te
index 60636db..6d7157e 100644
--- a/sepolicy/audioserver.te
+++ b/sepolicy/audioserver.te
@@ -14,3 +14,7 @@ allow audioserver unlabeled:file r_file_perms;

allow audioserver sysfs_esoc:file r_file_perms;
allow audioserver sysfs_esoc:dir r_dir_perms;
+allow audioserver sysfs:file r_file_perms;
+allow audioserver sysfs:dir r_dir_perms;
+
+
diff --git a/sepolicy/mdm_helper.te b/sepolicy/mdm_helper.te
index 9c44f08..deb8c7c 100644
--- a/sepolicy/mdm_helper.te
+++ b/sepolicy/mdm_helper.te
@@ -5,3 +5,6 @@ allow mdm_helper self:capability dac_override;

allow mdm_helper diag_device:chr_file read;
allow mdm_helper diag_device:chr_file open;
+allow mdm_helper sysfs:file rw_file_perms;
+allow mdm_helper sysfs:dir rw_dir_perms;
+

Now I have SIM. I also saw a bunch of these:

06-18 12:31:20.785 660 660 W zygote : Failed to remove /acct/uid_1058: Permission denied (there are lots of these)

They were unaccompanied by selinux denials however.

I am also seeing some denials (non selinux) to webview:

06-18 12:33:02.506 6034 6034 E /system/bin/webview_zygote32: Failed to make and chown /acct/uid_99002: Permission denied

Webview seems to work as far as i can tell however. I do use the multprocess webview. This is probably worth looking into still.

Will not be able to build again until at least tomorrow night, but wanted to share this. Running now in enforcing and we'll see what happens over the next 24-48 hrs. Hopefully zygote not being able to remove /acct/uid stuff won't be a deal breaker.

Enjoy!

ft
[Galaxy Note 4 Android Development (Snapdragon)] threader:
Sim (sim death) and open/mind gapps not working on trlte, latest build asked for sim pin, once... (allo allo style) and did not work again.
[Galaxy Note 4 Android Development (Snapdragon)] stylemessiah:
[MENTION=6847876]_mone[/MENTION] @ rupee

Many hours on, Sim has been relatively stable, though a few reboots here and there a few hours back

No sign of any selinux issues at least in the front end, have all my magisk modules loaded and running, usual tweaks applied etc, nothing to report....
[Galaxy Note 4 Android Development (Snapdragon)] ticky33:
Official LineageOs 15.1 for galaxy s5 lte-a.

The next one, our note 4 ???
[Galaxy Note 4 Android Development (Snapdragon)] frili:
Latest rom on N910F. Gallery can't see camera recordings on SD card.
[Galaxy Note 4 Android Development (Snapdragon)] rwalli:
Sorry, but cant test further because Here Wego does not find gps (like other has reported too) and i need it for daily navigation.

It's the only issue why i can't install 8.1 as main os.

tried with various open-gapps variant's and MindTheGapps, with and without mgisk.

Any suggestions how can i fix this?

Other gps-apps work.

Robert

PS: "SELinux in enforcing mode" works as suggested.
[Galaxy Note 4 Android Development (Snapdragon)] AndyYan:
Doesn't mean much, especially with the bugs reported around here, and a different way of handling SIM as quoted:

Keep in mind that "official" isn't significant. Only by fixing bugs and patching can we then try going (applying for) "official" - NOT the other way in which we become "official" and magically all the bugs fix themselves. The "official" moniker is also not much more than a guarantee of auto-generated weekly builds, and in that aspect our devs are doing better (@ripee does nightly).