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

[oroboros74]

I have read multiple times that People say Fingerprint is working. So is that bug now fixed or do I have to make a Workaround? If yes, how???

I clean flashed the last stable and I haven't had any problems with the fingerprint scanner.

 

[Vortell]

I have read multiple times that People say Fingerprint is working. So is that bug now fixed or do I have to make a Workaround? If yes, how???

Just keep scanning even after it's done tell you feel the vibration signal to enroll. Ignore dialog saying was successful. If it says it failed on it, try tell you can get it to work 2 or three times after it says success it failure dialogue. The finger print thing is about enrolling it right, changing battery optimization on validity service and knowing you have to swipe on the note 4 sensor.

 

[maralexbar]

I have problems with my memory card.
I have a 128GB SD formatted in ext4, in the previous version (10/21) it worked correctly, now (12/6) it marks as "SD damaged" and only allows FAT32

 

[rationaldreamer]

So you flashed a different modem ? And what sim card service do you use?

I have been reading some of the sim death problems MAY be solved by going to an older modem

Cheers

As I already mentioned, I haven't had any SIM problems at all so far and I just noticed that the last original N910F-Firmware I had installed before going to 8.1 was MMB29MN910FXXU1DQJ1 from November 2017. I wasn't aware of that there were released 2 further DBT-Versions in 2018. Maybe this helps someone. Is it correct, if I assume that if CSC changes, Modem (CP) changes, too? So in this case you may be right that sim death could be solved by using older modem.

 

[tze_vitamin]

Update
Check for an apn that is incomplete I had several that did not have any information in them.

I still have no sim death for I forget how long ,I even stop thinking about that.
I don't know how to help with some logs or something.
I can send anything that someone need to see how this work on my phone with no sim death and heaving 4G signal, just tell me what to do ,and I will send it if will that help.

 

[tze_vitamin]

As I already mentioned, I haven't had any SIM problems at all so far and I just noticed that the last original N910F-Firmware I had installed before going to 8.1 was MMB29MN910FXXU1DQJ1 from November 2017. I wasn't aware of that there were released 2 further DBT-Versions in 2018. Maybe this helps someone. Is it correct, if I assume that if CSC changes, Modem (CP) changes, too? So in this case you may be right that sim death could be solved by using older modem.

When I start exploring and reading about sim death problem,first thing that I also do was change CSC to my region.
I didn't know what is this was ,and after someone explains me that CSC has no matter with signal and that CSC is for update and other stuff I decide to change it to my region ,that was the first thing that I was do,then I was changing modem until I was found modem and bootloader that has the same last three or four number that matches with baseband version. When I was complete that,and after restart phone first that I was notice was better signal than after a while I was have LTE icon.

 

[Mantazzz]

Phone is not turning on

Hello guys. Please give me some ideas. I tried to do a full wipe in TWRP. I have followed instructions mentioned in this article. I didn't notice when, but in some point my Samsung Galaxy Note 4 (N910F) turned of in the wiping process and from that point I can't turn on my phone. Maybe you have some ideas what happened and can give me some advices how to amke it working again. Thank you in advance.

 

[rationaldreamer]

When I start exploring and reading about sim death problem,first thing that I also do was change CSC to my region.
I didn't know what is this was ,and after someone explains me that CSC has no matter with signal and that CSC is for update and other stuff I decide to change it to my region ,that was the first thing that I was do,then I was changing modem until I was found modem and bootloader that has the same last three or four number that matches with baseband version. When I was complete that,and after restart phone first that I was notice was better signal than after a while I was have LTE icon.

Thanks for your info. Maybe I should just stick to my present configuration. My N4 is stable, has LTE and good battery life time. I just learned that with the recent firwares, VoLTE was finally introduced. One year ago I was trying to get VoLTE because very often, when people called me, they got "connected" sign but on my side I didn't get any ringing and they thought I din't answer the call on purpose. But this problem seems to be gone, may this be due to lineageOS or provider adjustments. I think, I don't need VoLTE.
The only issue, I have is the finger print scanner. I just need to check out "changing battery optimization on validity service". But for this I would have to reinstall a rather outdated TWRP-Backup where the scanner as such is still operational.
I would be glad If somebody could give me a hint, how to fix it after deleting the related xml-file.

I wonder if it does something to your psyche, when clicking "I'm not a robot" over the years :silly:

 

[tripLr]

I have problems with my memory card.
I have a 128GB SD formatted in ext4, in the previous version (10/21) it worked correctly, now (12/6) it marks as "SD damaged" and only allows FAT32

Put a blank sd card in there and format it. Pull it out and check properties in windows and see what format it is.

1. This will tell us what the ROM is formatting.
2. Boot to twrp with the same card, and format it or fix file structure to all the options in twrp and see if it recognizes each one.

If not the kernel has had a change in the ROM to disallow certain file formats.

---------- Post added at 01:37 AM ---------- Previous post was at 01:35 AM ----------

I have problems with my memory card.
I have a 128GB SD formatted in ext4, in the previous version (10/21) it worked correctly, now (12/6) it marks as "SD damaged" and only allows FAT32

Put a blank sd card in there and format it. Pull it out and check properties in windows and see what format it is.

1. This will tell us what the ROM is formatting.
2. Boot to twrp with the same card, and format it or fix file structure to all the options in twrp and see if it recognizes each one.

If not the kernel has had a change in the ROM to disallow certain file formats.

You should be able to reflash 1021 and have access to your ext4 card. Unless you loaded the magisk module that adds ext4 access.

 

[len207]

Your camera might be broke. Could also be bad room install.

I am also having problems with the camera in more recent versions of this ROM on my N-910P. The stock camera may or may not take a (one) picture and then lock up. This is with both a clean and dirty flash if the ROM. Often not just closing the app or rebooting the phone will get it working again. Also installing Play Store alternatives does not solve the problem. Restoring an older nandroid of this same ROM cures the problem. Pretty much eliminates the broken camera potential cause.

 

[Vortell]

I am also having problems with the camera in more recent versions of this ROM on my N-910P. The stock camera may or may not take a (one) picture and then lock up. This is with both a clean and dirty flash if the ROM. Often not just closing the app or rebooting the phone will get it working again. Also installing Play Store alternatives does not solve the problem. Restoring an older nandroid of this same ROM cures the problem. Pretty much eliminates the broken camera potential cause.

Even with open camera?

 

[len207]

Even with open camera?

Unfortunately with any camera app that I tried including open camera. On the older ROM the stock camera works but isn't very good. I use Footej Camera which works fine with better options.

 

[muzammil gee]

Me mobil note 4 ROM fast 8.1.0 lineageOS 15.

 

[Vortell]

Unfortunately with any camera app that I tried including open camera. On the older ROM the stock camera works but isn't very good. I use Footej Camera which works fine with better options.

I know the 910p can be problematic but never read anything about the camera being the issue. Could be a hardware or maybe flash issue. Maybe there was some thing pushed to Los causing it. I use aicp now. You could check the sources and try to find out if there was any changes. Otherwise maybe try to flash again. Or just revert to older version as it is built daily and all. When I mained it I always kept older builds because sometimes changes are pushed to source before they are ready. The best thing to do is take a logcat of the problem and either revert it deal with it for a week or two. I know someone in S5 thread submitted changes to lineage camera. Maybe that's what caused this. I think it was lineage wide...

 

[_mone]

 

[unibomber]

*fist pump*

 

[maralexbar]

Put a blank sd card in there and format it. Pull it out and check properties in windows and see what format it is.

1. This will tell us what the ROM is formatting.
2. Boot to twrp with the same card, and format it or fix file structure to all the options in twrp and see if it recognizes each one.

If not the kernel has had a change in the ROM to disallow certain file formats.

---------- Post added at 01:37 AM ---------- Previous post was at 01:35 AM ----------



I have already tried from TWRP but it did not work, I also tried with fsck from linux and found no problems.

blkid gives me this

/dev/block/mmcblk0p25: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" 
/dev/block/mmcblk0p26: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" 
/dev/block/mmcblk0p27: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" 
/dev/block/mmcblk1p1: LABEL="Memoria USB" UUID="7bf951f1-45c6-4976-8653-21d932644400" TYPE="ext4"

dmesg

[ 5910.038400] EXT4-fs (mmcblk1p1): Ignoring removed nomblk_io_submit option
[ 5910.041752] JBD2: Unrecognised features on journal
[ 5910.041787] EXT4-fs (mmcblk1p1): error loading journal
[ 5910.091652] audit: audit_lost=2647 audit_rate_limit=20 audit_backlog_limit=64
[ 5910.091688] audit: rate limit exceeded
[ 5910.162648] JBD2: Unrecognised features on journal
[ 5910.162680] EXT4-fs (mmcblk1p1): error loading journal

---------- Post added at 01:13 AM ---------- Previous post was at 01:02 AM ----------

AOSP?

 

[ticky33]

Whaooo ! Pie is coming

 

[Jonkki]

HUOH! People, before you claim that changing the battery optimization setting for "validity service" fixed the buggy fingerprint reader, wait a couple of days.
I came back to this ROM after being with the stock for months because I thought that this was finally fixed, but of course, the fingerprint sensor is still the buggy old self.

So much work for absolutely nothing.

 

[slarti76]

But how steal battery when phone is turned OFF? And i don't think you have to make any set up for a phone that is OFF.

I have this problem too, quite annoying. But someone here pointed me to a workaround that works for me: Keep your phone plugged in while turning it off (and then some seconds). Then unplug. Should hold full power until next power up.