[ROM][UNOFFICIAL][11.0][ N7105/T0LTE ][Samsung Galaxy Note 2 LTE][ LineageOS 18.1 ][BETA][TREBLELIZED]

[No3te]

Hmm ok, I didn't test google voice service...

Hmm, strange, this seems to work with my device.

Maybe it's my english.
I ment Android keyboard. I speak a lot, instead typing.
Pressing mic icon on keyboard does nothing.

Regarding "blink" problem it's very well known - check Note 3 thread.
There were "accusations" like: inteli pixels, Live display, blur option and may be others.

It's less then 24 hours, and I flashed ROM only 2 times.
I will try MGapps today and report, for sure.
My device was flashed with LOS to Android 5, and then 7.1.2 and used as everyday phone.
Now I'm using Note 3 9005, as CrDroid+GA works with not a single problem on Androd 11, including OTA upgrades.

 

[html6405]

Regarding "blink" problem it's very well known - check Note 3 thread.
There were "accusations" like: inteli pixels, Live display, blur option and may be others.

Could you create a video where you can show what exactly happens?

 

[No3te]

OK, I had no problem with this, what happened?

This is normal, because selinux is permissive.

Ah you're right, I will remove or disable this, because I've removed the lineage recovery from the build in general,
I don't wan't that TWRP will be overwritten...

I'm unsure what do you mean with this

After choosing language in initial set up, it says - google voice services not working, 2 more set up screens and it stops in "wait a minute" screen.
Voice service not working in AOSP keyboard.

Another problem is well known in Note 3 ROMS - 10 and 11.
When you pull qa menu from the top of screen you get icons: wifi, battery etc. While pressing and holding battery icon(and some others) screen blinks to black, says "interface crashed" and goes back to normal.
"Solution" to this is switch off description under icons.

Sorry for not giving "logs" but it's over my skills.
Tried to send "bug report" but it warns about privacy
I will try Mind the gapps, what helped me with Note 3.

Could you create a video where you can show what exactly happens?

I just flashed LOS and latest MindTheGapps.
After first reboot ALL seams FINE and working. Not a single problem.
No problems durying setup.
It's just an hour and I dont't know about NFC which I dont use.
Congratulations for Your great work.

P.S.
I wouldn't like to record crashing interface, as it works now.
I will try to explain.
On main screen from the top you pull quick access menu.
There are many icons like: battery,wifi,location,NFC, rotation etc.
Pressing and holding finger on battery icon should automatically open battery menu in settings.
Instead all screen turns black for second or so and comes back with main screen.
Repeating this procedure gives notificaion - "interface keeps crashing" and "about app".
When you turn of descriptions under icons in qaccess pull down "drawer" (in settings menu) everything works OK.
It happens also when you touch "settings" icon at the bottom of qaccess drawer.

 

[html6405]

After choosing language in initial set up, it says - google voice services not working, 2 more set up screens and it stops in "wait a minute" screen.

Maybe a gapps problem,

icon(and some others) screen blinks to black, says "interface crashed" and goes back to normal.
"Solution" to this is switch off description under icons.

hmm tested this on all my devices, it's working everywhere...
Did you install the ROM clean?

It happens also when you touch "settings" icon at the bottom of qaccess drawer.

Tested also this, no problem.

 

[No3te]

Maybe a gapps problem,

hmm tested this on all my devices, it's working everywhere...
Did you install the ROM clean?

Tested also this, no problem.

I did wipe: cache, d.cache, data, system.
Wipe d.cache before reboot to system.
It looks like gapps issue.
Now it works and don't have to switch off descriptions under icons.
I may say I'm amazed that in first version of ROM there are no problems AT ALL.
Never seen that before, installing custom ROM's like...100 times.
If alpha is that good I've no idea what would be "official" .
Only this recovery bug...
For me only one feature missing is editing clock widget(font-bold, colour).

 

[Deleted member 11848357]

pretty solid for an alpha

some issues compared to LineageOS 16.0

major: no baseband/imei/etc..maybe corrupted efs? not a deal breaker since wifi works

minor: - no charging/notification led
- heavier battery drain (10%/hr) screen off airplane mode/no sync on clean flash with no gapps and only termux + magisk / on 16.0 was 10%/day with same setup
"cat /sys/class/power_supply/battery/current_now" shows 0
- livedisplay is buggy and settings don't survive reboot
- "Device Wi-Fi Mac address" shows 00:00:00:00:00:00 but shows and connects to access point with correct mac under "wi-fi mac address" in about phone.

I removed Via - /vendor/app/via. Not sure if that's meant to be included.

 

[html6405]

It looks like gapps issue.
Now it works and don't have to switch off descriptions under icons.

Great,

If alpha is that good I've no idea what would be "official" .

I don't think that I will make it official, this is so much time consuming, did this
for some devices on /e/.

major: no baseband/imei/etc..maybe corrupted efs? not a deal breaker since wifi works

Ok, this shouldn't be, if you're having a recent KitKat modem and bootloader installed, the modem should boot up.
Does it work with LOS 16? Than it should also work with LOS 18...

heavier battery drain (10%/hr) screen off airplane mode/no sync on clean flash with no gapps and only termux + magisk / on 16.0 was 10%/day with same setup

This is because of the not working modem, the RIL deamon tries to boot up all the time.

I hope you didn't touch the efs partitions in the repartitioning process.
(Maybe you can tell me how you did it?)

- livedisplay is buggy and settings don't survive reboot

Ah ok, what's exactly buggy? I've just tested a reboot and the settings were stored correctly.

- "Device Wi-Fi Mac address" shows 00:00:00:00:00:00 but shows and connects to access point with correct mac under "wi-fi mac address" in about phone.

Ok, this is also known, the macloader works correctly but it doesn't show's it in the settings, I will check this...

I removed Via - /vendor/app/via. Not sure if that's meant to be included.

Via is included for AOSP (GSI), because there is no useful browser included.

 

[Deleted member 11848357]

Ok, this shouldn't be, if you're having a recent KitKat modem and bootloader installed, the modem should boot up.
Does it work with LOS 16? Than it should also work with LOS 18...

This is because of the not working modem, the RIL deamon tries to boot up all the time.

I hope you didn't touch the efs partitions in the repartitioning process.
(Maybe you can tell me how you did it?)


Ah ok, what's exactly buggy? I've just tested a reboot and the settings were stored correctly.

Ok, this is also known, the macloader works correctly but it doesn't show's it in the settings, I will check this...

Via is included for AOSP (GSI), because there is no useful browser included.

Don't remember if I updated to Kitkat on stock, it had CWM and CMx.x. when I pulled it out of the drawer.

Went to https://xdaforums.com/f/t-mobile-samsung-galaxy-note-ii.1877/ but its dead so came here.

Flashed your TWRP and LOS 16. I remember seeing IMEI on 16 but didn't test sim

For repartition, I adb pushed parted, did rm partitions 11-16, then mkpart remade those in same order but resized and reformatted the new ones using mke2fs. Didn't touch radio/efs.


What's the best way to fix this? Flash stock through Odin? Flash modem? It doesn't bother me that modem isn't working but battery drain is a pain. Maybe disable telephony service?

For livedisplay, I have to switch between Off and auto when its set to auto for it to change temp. connected on wifi with right date/time

 

[html6405]

Flashed your TWRP and LOS 16. I remember seeing IMEI on 16 but didn't test sim

Ok this is good, than your modem should be compatible.

For repartition, I adb pushed parted, did rm partitions 11-16, then mkpart remade those in same order but resized and reformatted the new ones using mke2fs. Didn't touch radio/efs.

Oh, so you've also deleted:
11 164MB 432MB 268MB ext4 TOMBSTONES
12 432MB 1432MB 1000MB ext4 CACHE
?
May I ask why (it's not needed for the re-partitioning process)?

Tombstones is needed for our modem, without it can't be booted up.
Maybe you've didn't formatted Tombstones correctly (ext4), maybe you should recheck this.

Otherwise set the original pit-file and restart your re-partitioning process and just delete 13-16.

 

[Deleted member 11848357]

Ok this is good, than your modem should be compatible.

Oh, so you've also deleted:
11 164MB 432MB 268MB ext4 TOMBSTONES
12 432MB 1432MB 1000MB ext4 CACHE
?
May I ask why (it's not needed for the re-partitioning process)?

Tombstones is needed for our modem, without it can't be booted up.
Maybe you've didn't formatted Tombstones correctly (ext4), maybe you should recheck this.

Otherwise set the original pit-file and restart your re-partitioning process and just delete 13-16.

Ah that's where I messed up. I tried to reclaim some disk space and mirrored my Nexus device without thinking . I shrunk Tombstones from 268mb to 128mb.

11 164MB 292MB 128MB ext4 TOMBSTONES
12 292MB 804MB 512MB ext4 CACHE
13 804MB 2804MB 2000MB ext2 SYSTEM
14 2804MB 3391MB 587MB ext4 HIDDEN
15 3391MB 3399MB 8000kB OTA
16 3399MB 15.8GB 12.4GB ext4 USERDATA

 

[html6405]

Ah that's where I messed up. I tried to reclaim some disk space and mirrored my Nexus device without thinking . I shrunk Tombstones from 268mb to 128mb.

11 164MB 292MB 128MB ext4 TOMBSTONES
12 292MB 804MB 512MB ext4 CACHE
13 804MB 2804MB 2000MB ext2 SYSTEM
14 2804MB 3391MB 587MB ext4 HIDDEN
15 3391MB 3399MB 8000kB OTA
16 3399MB 15.8GB 12.4GB ext4 USERDATA

I guess, if you fix this, baseband should work and the battery drain should be gone.

 

[Deleted member 11848357]

I guess, if you fix this, baseband should work and the battery drain should be gone.

so something's not right..

Fully restored to latest 4.3 T889UVUCOH4 using Odin. Shows baseband/imei and works.

Loaded your TWRP twrp-3.5.2_9-1-t0lte.img through Odin.
Clean flash your LOS 16. No baseband/imei.

Restored again to 4.3. Shows baseband/imei.
Loaded your TWRP twrp-3.5.2_9-1-t0lte.img through Odin.

Clean flash LOS 14.1 https://xdaforums.com/t/rom-eol-7-1-2-official-lineageos-for-t0lte.3538310/ Shows baseband/imei and works.

Dirty flash your LOS 16 over 14.1. Shows baseband/imei and works.

Going to try repartitioning and flash 18.1 tomorrow.

 

[html6405]

Loaded your TWRP twrp-3.5.2_9-1-t0lte.img through Odin.
Clean flash your LOS 16. No baseband/imei.

Hmm this is strange, by the way, I would recommend to use a KitKat modem and bootloader.

Going to try repartitioning and flash 18.1 tomorrow.

Tell me how it works.

 

[Deleted member 11848357]

Hmm this is strange, by the way, I would recommend to use a KitKat modem and bootloader.

Tell me how it works.

Got it working on 18.1

I can try using Canada's T889V 4.4.2 modem/bootloader as 4.3 is the latest/last for US T889
Don't think N7105 or other variants will work cause of lte bands

 

[Robs03]

Just got this ROM up and running on my refurbished GT-N7105 that I recently bought.
I have noticed the Trust security features (SELinux) and (Encryption) seem to be disabled and keep getting alerts whenever turning on the phone.

I also unfortunately cannot get MMS working at all on any Lineage Version I have tried (3 so far).
I have tried re-setting my network settings and configuring my APN settings using my mobile network carrier's settings.

When connecting to a Wifi network MMS then suddenly works.

Total novice here.

 

[html6405]

I have noticed the Trust security features (SELinux) and (Encryption) seem to be disabled and keep getting alerts whenever turning on the phone.

Yes, but you can disable these alerts.

I also unfortunately cannot get MMS working at all on any Lineage Version I have tried (3 so far).
I have tried re-setting my network settings and configuring my APN settings using my mobile network carrier's settings.

When connecting to a Wifi network MMS then suddenly works.

Hmm ok, I never tried this, did you use 3G for this?
Because LTE is causing more troubles...

 

[Robs03]

Hmm ok, I never tried this, did you use 3G for this?
Because LTE is causing more troubles...

Hi, I tried resetting my network settings to factory default last night and then selecting 3G but unfortunately no luck with the MMS or getting internet access. The phone now seems to be stuck in 3G mode and cannot change it back to 4G / LTE.

I recently bought a refurbished Note 10+ for mum.

I was attracted to the Samsung Note phones as they score well in the SAR radiation tests compared to other phones.

 

[html6405]

Hi, I tried resetting my network settings to factory default last night and then selecting 3G but unfortunately no luck with the MMS or getting internet access. The phone now seems to be stuck in 3G mode and cannot change it back to 4G / LTE.

I recently bought a refurbished Note 10+ for mum.

I was attracted to the Samsung Note phones as they score well in the SAR radiation tests compared to other phones.

Hmm ok, thanks for testing, but at least after a reboot you should be able to switch back to LTE.
There is still much work to be done to have a good enough working RIL.

 

[Deleted member 11848357]

Not sure if intentional but, flashlight goes to sleep after screen locks within 5 secs. takes a few presses on the icon to retoggle in quick settings.

Doesn't happen on your LOS 16.

also on both LOS 16 and this, lowest display brightness is a bit bright for an amoled panel? anyway to increase the range from lowest to highest?

 

[html6405]

Not sure if intentional but, flashlight goes to sleep after screen locks within 5 secs. takes a few presses on the icon to retoggle in quick settings.

Ah ok, I will try this.

also on both LOS 16 and this, lowest display brightness is a bit bright for an amoled panel? anyway to increase the range from lowest to highest?

The display brightness is set to 20% as minimum value.