[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [trlte][tblte][trlteduos]

[tripLr]

Hey, uh will this work for the Verizon Variant? I know theres another unofficial build for the verizon variant but its on 7.1.2 and I want an Oreo rom. So, will this work on the Verizon variant?

I am running the 910v. Works great. Let me know if your fingerprint works. I have a feeling my sensor is dead.
@ripee @_mone

0623 version is really really stable (nano). I have had the aosp camera on running in the background and no crashes.
A couple times I lost Bluetooth .

Interesting thing, I was streaming iHeartRadio and I wanted to change my home button settings for a different launcher , so I went to settings/apps/show all/reset app preference/ and when I reset, it killed the Bluetooth. So maybe the Bluetooth is getting a intermittent kill from some other app in the OS ? Log attached

 

[fattire]

for me this build 0626 has been the best for N910T. stable hotspot, working gps, stable BT as compared to the disconnects on 0625. i'm glad i made the jump. no issues for me yet

I had an annoying BT disconnect at random times (with no error in the UI) that correlated to this:

06-26 11:07:20.113 10732 10732 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
06-26 11:07:20.122 10732 10732 F DEBUG : Abort message: '[FATAL:future.cc(64)] Check failed: future != NULL.

...and I've been trying to track down the issue. For fun i tried building using this repo in place of the lineageos one. I used the "android-8.1.0_r32" branch because I noticed that the most recent commit in lineageos updated to r30, so it's r2-better, right?

Okay so that said, I have not had any BT crashes yet. But it's only been about 6 hours of which I've barely had bt connected, only for a few moments-- just because I haven't really had occasion to try it. But anyway if I notice anything is fixed, it might be interesting to switch to that repo or try to figure out what is fixed there. I'll report back if I find any issues.

If anyone wanted to try something similar I figured I'd just let people know. I'm also open to any other suggestions of what could be wrong. I didn't track the bug down too diligently, I admit.

 

[desvariando]

I had an annoying BT disconnect at random times (with no error in the UI) that correlated to this:

06-26 11:07:20.113 10732 10732 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
06-26 11:07:20.122 10732 10732 F DEBUG : Abort message: '[FATAL:future.cc(64)] Check failed: future != NULL.

...and I've been trying to track down the issue. For fun i tried building using this repo in place of the lineageos one. I used the "android-8.1.0_r32" branch because I noticed that the most recent commit in lineageos updated to r30, so it's r2-better, right?

Okay so that said, I have not had any BT crashes yet. But it's only been about 6 hours of which I've barely had bt connected, only for a few moments-- just because I haven't really had occasion to try it. But anyway if I notice anything is fixed, it might be interesting to switch to that repo or try to figure out what is fixed there. I'll report back if I find any issues.

If anyone wanted to try something similar I figured I'd just let people know. I'm also open to any other suggestions of what could be wrong. I didn't track the bug down too diligently, I admit.

That working would be great news!

 

[UNForces]

AT & T Variant

Does this rom support the AT&T variant (N910A)?

 

[ripee]

Does this rom support the AT&T variant (N910A)?

No, but only because the bootloader cannot be unlocked.

 

[pro99line]

I have been on multiple daily builds and still have the same problem. N910V currently on 6/24, updated gapps, updated modem and bootloader. When I am on a current call and another one is coming in, I see the new incoming call and when I press answer to swap over, the screen just goes to in call and doesn't answer the new call. I checked the phone app settings and there are none for call waiting. Am i missing something?

 

[kerfex]

Hi community, Question to other N910V users. I have been dirty flashing every build since 06/15/2018 Ripee's builds of course. Currently Running the newest, 06/27/2018. All seems well. I still have no fingerprint scanner working. I also get a system app crash when I go to /Settings/System/About Phone/Status. Nothing else in settings crashes it. Minor issue and for me every thing else is working perfect.

The question I have is, has anyone clean installed either 06/25, 06/26 or toady's build, 06/27 and the fingerprint reader works for you? Thanks again and Thank you DEV's. This ROM is just simply fantastic for being Beta/Unofficial. Just spectacular.

 

[lodilovesmuffins]

I am running the 910v. Works great. Let me know if your fingerprint works. I have a feeling my sensor is dead.

Hey! Yea it works beautiful. My fingerprint sensor works, its just a little finicky to try and assign one. Whenever I tried setting a fingerprint it immediately got deleted so I just kept trying and then it worked.

 

[kerfex]

Fingerprint

Hey! Yea it works beautiful. My fingerprint sensor works, its just a little finicky to try and assign one. Whenever I tried setting a fingerprint it immediately got deleted so I just kept trying and then it worked.

Did you do a clean install? What version? Thanks.

 

[lodilovesmuffins]

Did you do a clean install? What version? Thanks.

I did a clean install and i did version 20180625 from trlte

 

[kerfex]

I did a clean install and i did version 20180625 from trlte

Great. When I go home later, I will do a full wipe and cleans install of 6/25. Thanks!

 

[lodilovesmuffins]

Great. When I go home later, I will do a full wipe and cleans install of 6/25. Thanks!

No problem man, just keep trying when you do it though. It may fail sometimes.

 

[lodilovesmuffins]

Ok so theres a problem with the rom that idk if its my problem or if its the rom. For some reason i got twrp removed twice with this rom. I could still flash it because the bootloader was unlocked but idk why twrp got removed.

 

[RockwellB1]

Is anyone else still having issues with the play store and basketbuild downloader taking FOREVER to initialize downloads? This has been going on for awhile and is becoming so annoying doing any kinds of updates or makes it impossible to grab an app when out and about that you might need right then.

Otherwise everything else seems to be working great for me that I use (basically anything but BT and fingerprint scanner, don't use them).

 

[zed37]

I had issue with play store (not in this rom) - i cant update anything. Any solution after few day fight was uninstall play store (all updates) and install again.

 

[X(d)avier]

Quick test with clean install on N910F :

- N910FXXU1DRD1_N910FXXU1DQL1 (from https://basketbuild.com/devs/ripee/BL_CP)
- lineage-15.1-20180627-UNOFFICIAL-trlte
- addonsu-remove-15.1-arm-signed
- MindTheGapps-8.1.0-arm-20180610_023943
- Magisk-v16.4

Seems stable. Here MAPS locate me quickly. But after some test with different core on Retroarch, the sound delay problem is still here ;(

 

[unic0rnio]

You folks are legends. I thought the file was corrupt when I saw the download was ~380 mb. But legit that's the size of the ROM! My phone is literally lightning fast now there is absolutely no lag between any task switching or anything. Godlike porr, much appreciated :highfive:

 

[stylemessiah]

Ok so theres a problem with the rom that idk if its my problem or if its the rom. For some reason i got twrp removed twice with this rom. I could still flash it because the bootloader was unlocked but idk why twrp got removed.

The ROM cannot remove TWRP

Check or post your flashing process to see if perhaps youre doing something wrong

 

[kerfex]

OK, So I went home last night and wiped everything and clean installed 06/25/2018. Fingerprint scanner did not work. Does not even sense anything. So I cannot even try to register one fingerprint . So I thought well my reader must be dead. So just for the heck of it, I went back to BPA1 full stock. Sensor worked. So, I just thought I would let the DEVS know that. The only other thing I can think that might be messing it up, is that I always flash Gapps-Stock. Do you think that might have something to do with it?

---------- Post added at 12:00 PM ---------- Previous post was at 11:51 AM ----------

Oh, and one other thing for Ripee. I have the TWRP 3.2.1 and when I went to reinstall my NAND back up, it said it did but would only boot to download mode. And I had system and data and boot backed up. N910V and 32 gig SD card. Sandisk. I have never experienced not being able to restore a NAND backup before. Not sure if its the card or the TWRP recovery itself. Anyone else experience this.? Just thought I would let you know Ripee. It is no biggie since I have multiple backups of my programs ( Google and a manual one to Google Drive). So, never a problem restoring. Anyway, just wanted to give you a heads up. Thanks.

 

[Shizzle2889]

OK, So I went home last night and wiped everything and clean installed 06/25/2018. Fingerprint scanner did not work. Does not even sense anything. So I cannot even try to register one fingerprint . So I thought well my reader must be dead. So just for the heck of it, I went back to BPA1 full stock. Sensor worked. So, I just thought I would let the DEVS know that. The only other thing I can think that might be messing it up, is that I always flash Gapps-Stock. Do you think that might have something to do with it?

---------- Post added at 12:00 PM ---------- Previous post was at 11:51 AM ----------

Oh, and one other thing for Ripee. I have the TWRP 3.2.1 and when I went to reinstall my NAND back up, it said it did but would only boot to download mode. And I had system and data and boot backed up. N910V and 32 gig SD card. Sandisk. I have never experienced not being able to restore a NAND backup before. Not sure if its the card or the TWRP recovery itself. Anyone else experience this.? Just thought I would let you know Ripee. It is no biggie since I have multiple backups of my programs ( Google and a manual one to Google Drive). So, never a problem restoring. Anyway, just wanted to give you a heads up. Thanks.

Ok- for everyone having issues with the fingerprint scanner. I am currently utilizing the verizon note and have yet to flash a lineage build that the scanner did not work at all. The issue is that the fingerprint scanner has issues, but the majority of those issues are in trying to get the fingerprint registered. Just need to work with it. Once registered, it sometimes works and sometimes doesnt for unlocking the phone, but never had an issue with permitting so or many other security thresholds that may utilize the fingerprint.

What i have gotten used to for the lock screen is continually swiping. 99% of the time (and in the last 2 weeks, can only recall 2x it didnt) it will get to a point where it eventually displays a red exclamation circle stating it was a bad scan. The next swipe has always unlocked the phone for me. Those 2x i can recall that it didnt work, i never got anywhere outside of for some reason, the pin number pad popping up.

Now for the issue with registering the finger prints. You will just want to skip during setup and go into settings to set up once phone setup is complete. From there, setup a pin, password, or something of the sort. Select to register a fingerprint, type in your passcode, and select to add a new fingerprint. It will ask you to swipe to initialize the registering. Then swipe 7 or 8 more times to register the print (unsure why but have seen it ask for 7 or 8 swipes on registering and cant figure out what concludes how many it wants). If the swipe does not work to initialize the registration, then you need to put a pause to it. Try doing different things to get it to work. Only time i had this issue, got it to work by charging to 98%, then unplugging and trying. Once you finish the registration, ensure that there is a fingerprint registered before exiting the fingerprint settings. If not, redo the registration process. I have never gotten it on lineage the first try, but have in as few as 8 and other times as many as 30+.

At the end of the day, this can be quite a time consuming process to get working, but it does work. I would not suggest doing if you clean flash daily. If you dirty flash, I am unsure if it wipes the print, though i would assume it does. It is completely up to you though.

Also, @ripee and the other devs. Is it possible to get verification or testing on the other note4 variants, outside verizon for the fingerprint scanner issues?