yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] stephendt0:
This ROM is a bit buggy for me. Here's some issues I've noticed on the latest ROM (lineage-18.1-20230423-nightly-hlte-signed.zip)

1. Unable to remap menu button as recents. Just stays as menu button

2. 5Ghz Wi-Fi doesn't work for me on some channels (149). Worked on the previous build (lineage-18.1-20230323-nightly-hlte-signed.zip)

3. Settings app crashes most of the time when trying to launch it.

Any ideas if it is just me? Not messing around with kernels or anything. Battery is in good shape still, was a clean install and I have the latest modem installed.
[Galaxy Note 3 Android Development] npjohnson:
You did something funny - I suspect you didn't format data in the install process, or use Lineage recovery - 1 and 3 work fine here.

2 - we changed literally nothing between those builds - there'e no way that one specific thing broke - because there were no changes in that realm - so that's confusing.
[Galaxy Note 3 Android Development] stephendt0:
I installed the ROM via TWRP, so I guess that is probably where I messed up. I did format data though. I'll re-flash, and see if that helps.
[Galaxy Note 3 Android Development] js-xda:
TWRP (but still 3.6.1) giving no issues here upgrading from March to April build. Using OpenGApps Pico but no other packages.
[Galaxy Note 3 Android Development] enzo80:
hello there,

google play store is missing.

How can i install google play store ?
[Galaxy Note 3 Android Development] js-xda:
As with any official LOS build, one has to flash before use a GApps package. Format data (loosing all data!) when adding now.

Please read the guide: https://wiki.lineageos.org/devices/hlte/
[Galaxy Note 3 Android Development] chris@xda:
That is quite new. Am I supposed to just flash eg. lineage-18.1-20230420-microG-hlte.zip or do I need to flash boot and recovery as well?
[Galaxy Note 3 Android Development] rayman95:
Nom, only los..
[Galaxy Note 3 Android Development] chris@xda:
The ROM seems to work.

Issues so far:

GPS fix for navigation is taking forever and sometimes doesn't do

BT connection disconnects, reconnects, disconnects, reconnects, etc... while no audio output is active
[Galaxy Note 3 Android Development] rayman95:
update last modem and bootloader
[Galaxy Note 3 Android Development] chris@xda:
NOT the slightest idea what you are talking here
[Galaxy Note 3 Android Development] chris@xda:
OK, The video shows how both are flashed. Where to get the last modem and BL
[Galaxy Note 3 Android Development] rayman95:
Downloads for : Samsung Galaxy Note 3 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com
[Galaxy Note 3 Android Development] chris@xda:
Great!

I understood from rom here I need booth BL and Modem

Then in ODIN I'd set path to BL in BL field, Modem path to CP field and with options left as default hitting start

I'm not sure if I will understand, but what am I doing here and why both files?

Where do they come from and why's that necessary?
[Galaxy Note 3 Android Development] rayman95:
just flash BRI1 BL and PQB1 CP and check if flashed correctly with samsung info app and you re good to go
[Galaxy Note 3 Android Development] chris@xda:
I see, when you initially said "last", you didn't refer to the upload date. To be more specific:

CP_N9005XXUGPQB1-Nordic.tar​

and

BL_N9005 XXSGBRI1.tar​

are the ones?

My guess (because of date and naming convention) for CP was

CP_N9005 XXSGBRI1.tar​

You won't explain, do you? Somehow the Bootloader goes together with the modem part, so I would have assumed that either must be BRI1 or PQB1 and no mix, sorry. Wrong assumption?

I'm asking, because I have a similiar issue with a freshly flashed LOS18.1 for SM-A510F regarding WiFi and GPS that is yet not solved. Anyway if that fixes and takes away the causes for instability: I still don't know where to find BL/CP parts for the a5xelte. Do I need to extract them from a given source or do I find those somewhere else?

How am I supposed to know which BL and CP plays well together and so on.
[Galaxy Note 3 Android Development] JJEgan:
Cannot find latest bootloader etc .

Then flash latest stock rom .

Look in the two modem / bootloader threads first but they are probably well out of date now .
[Galaxy Note 3 Android Development] Mr Reman:
I just updated my note 3 through the built in updater and now I can't open most of the programmes I've installed via the play store. All I'm getting is a black screen, but I can still access the notification bar.

Is this just me, or has anyone else seen this issue in the last couple days?

It's currently on LineageOS version "18.1-20230523-NIGHTLY-hlte"

Edit - The update seems to have knocked out the WiFi and mobile data. They LOOK to be connected, but neither allow any data movement.

Just to clarify, everything looks normal UNTIL I try to open a program, then I get the black background with the notification bar still accessible. The only way to get back to the "desktop" if to hold the home button and kill the program I was just trying to open.

I've restarted the phone several times, tried removing the SD card (Because before the update, on boot, it often took a couple of minutes to recognise it was there), and looked through the settings, but nothings standing out to me.

If this isn't a widespread glitch in the update I'll just wipe the phone and put an earlier image back on, but if there's multiple people getting this problem, I'm thinking my phone might have log files or such that could be useful to the LineageOS devs trying to work out what's happened, so it could be handy to leave it be for now.
[Galaxy Note 3 Android Development] js-xda:
Thank you for reporting! I haven't updated yet (and won't with this report as the phone is used by a family member living some distance away - so I am in trouble if the same happens there). But your remark about WiFi triggered a thought: It is a known issue at least for NikGApps that upgrades (and maybe also updates but not sure anymore) cause that at least the GApps have WiFi & mobile data disabled. I experienced myself but then it was not with a black screen but simply as if not having internet access.

Can you ...

... share which GApps you are using?

... check whether it is just the setting per app that WiFi and mobile data are disabled?
[Galaxy Note 3 Android Development] Mr Reman:
Starting to get out of my depth with what version of GApps I'm using. The file name of the only package I have that even mentions GApps is "MindTheGapps-11.0.0-arm-20220217_095902".

I've checked network permissions for a few of the programs that aren't starting (Just a black screen) and they look to have permission for WiFi. Interestingly, I've just noticed that one of the programs that won't start is the updater itself, so it's not just the apps I've added that are having problems.

I AM starting to think this problem is probably either something isolated to me, or a very small group of people though, as I'd have expected a flurry of people online all quoting "18.1-20230523-NIGHTLY-hlte" if it was more widespread, but that doesn't seem to be the case.......... Mind you, this post doesn't even show up when I Google that string either, so who knows? :)
[Galaxy Note 3 Android Development] js-xda:
Unless you are dependent on it, maybe wait a bit with drastic steps. With the monthly updates, I would not be surprised that not so many users updated yet. In my kind of special case, I wait typically 1-2 weeks for no disastrous reports before advising the user to apply the update.
[Galaxy Note 3 Android Development] Mr Reman:
There's currently no pressing rush to wipe it. I have 2 note 3's and this one's just a backup. I've been using it on WiFi to play games and do a bit of web surfing at home because I wanted to know it was 100% stable before turning it into my everyday phone (And updating my other note 3 to LiniageOS to become the backup). Up to this it's been pretty much rock solid.
[Galaxy Note 3 Android Development] Mr Reman:
Well, the weekends over and there's still no flurry of panicked posts from folks screaming about how "18.1-20230523-NIGHTLY-hlte" broke their phones, so I'm really starting to think it's just mine. :D

I'll give it a couple more days and I'll try a factory reset to see if that sorts it.
[Galaxy Note 3 Android Development] Mr Reman:
Still no mass of people complaining about this update online this morning, so curiosity about if this was the update or my phone that was the problem finally got the better of me, and so I did a factory reset. I was slightly worried when I saw the rom on the phone was updated on 23/05/23 (Same date as the rom that started the problem), but I cleared the cashe, ran through the reset without issue, and after reinstalling all my apps it seems to be working perfectly fine again.

God only knows what had happened before, but it's now on the version that was causing problems before, but this time it's totally happy.

Maybe some system setting that a lot of software I use needed got changed during the update, but this time the software got installed AFTER the OS, so it got changed back to the setting the software wanted? It's a total stab in the dark, but I can't think of anything else......... Though this wouldn't explain why even some built in system utilities/options were playing silly beggars too.
[Galaxy Note 3 Android Development] js-xda:
FYI: The Note 3 in my family was updated today and I haven't received any complaints so far.
[Galaxy Note 3 Android Development] Mr Reman:
Fair enough, that's good to know.

I'm pondering if there might have been some sort of incompatibility between the original image I used, and how I didn't bother with a few of the updates between then and when it fell over? Maybe some files would have been changed by one of the missed updates, and the 23/05/23 update was expecting the newer version of those files?

TBH, I haven't got a clue (I'm a PC, hardware tech by trade. Android is just something I USE rather than understand in depth) but that doesn't stop me speculating about what might have gone wrong. :)
[Galaxy Note 3 Android Development] q2n:
Just sideloaded perfectly to N900T with Team Win v.3.7.0_9-0.

Now setting up APKpure for a Google-free experience. Hope this goes as well...
[Galaxy Note 3 Android Development] rayman95:
use droidify for open source apps and aurora store for replacement on google store
[Galaxy Note 3 Android Development] q2n:
Thanks for the recommendations. I picked APKpure after seeing (possibly false) posts on Aurora-sourced apps found with malware. That left APKmirror -- a dud as it requires a credit card -- and some also-rans. Will give Aurora another look.

F-droid good. Had seen its Droidify client but not checked it out (which I'll do now). After many years with no concern, I'm now easing away from G.
[Galaxy Note 3 Android Development] SirGarmaples:
While I'm not using this ROM at the moment, I use Droid-ify on all my devices and it's great so far! Probably one of the better F-Droid clients I've used in a long while.
[Galaxy Note 3 Android Development] 3tclte:
Please add the Always On Display feature!
[Galaxy Note 3 Android Development] baerenbisch:
No more monthly updates ?
[Galaxy Note 3 Android Development] odoll:
As far as I can tell the N3 device family is still in the schedule for monthly builds

However the build status is "idle" in general(!?) and I can't figure any hint, e.g. that the build process for the n3 only ran into any issues or is stalled?!

PS: Which slightly is a pity esp. as this month patch level would mitigate the somewhat more severe Zero Day issue CVE-2023-4863?! Or has the patch already been merged into the 23/09 image?
[Galaxy Note 3 Android Development] q2n:
Getting into this, I found some apps refuse to run without G playstore.

Best I find to overcome the lameness is an implementation of microG.

Various methods of installation are published, but the cleanest/easiest I find is flashing a build from the microG download page, which has all hlte variants. Installation instructions here.
[Galaxy Note 3 Android Development] odoll:
@haggertk et al.: Thx for lineage-18.1-20231108-nightly-hlte-signed.zip (incl. recent security fixes)!
[Galaxy Note 3 Android Development] fschmeck:
Is anyone else experiencing the audio-echo issue, where the person on the other end can hear their own voice sent back to them? I've been reading about this on multiple devices, but can't figure out how to fix it. I'm on 18.1.
[Galaxy Note 3 Android Development] Farriman:
Is there a way to enable Gesture navigation?

my back button is broken.

I can see it in the Settings, I just can't find a way to enable it.
[Galaxy Note 3 Android Development] falconsson:
Thank You!..
[Galaxy Note 3 Android Development] HadyShaltout:
Hi Guys,

Can anyone confirm that this app InstaPay Egypt working successfully? It was installed but always kept closing.

Any thoughts about the yellow-white background?

Thanks
[Galaxy Note 3 Android Development] Oslanki:
Instale lineageos 18.1 y no me funcionó 4g 1800 mhz mi note 3 sm-N9005 me ayudan
[Galaxy Note 3 Android Development] entauri:
Does the S-pen pressure sensitivity work properly? I tried Lineage a few years back and it was borked.
[Galaxy Note 3 Android Development] Lazuli Ly:
Hi....im about to buy this phone but its true that youtube app wont work?
[Galaxy Note 3 Android Development] bilatche:
on mine, i used smartubenext, it was ok, no ads.
[Galaxy Note 3 Android Development] rayman95:
Choose a more recent...too old now
[Galaxy Note 3 Android Development] Computershik:
"This device does not exist". Where can I find alive links for this ROM?

I found only this unofficial archive: https://lineage-archive.timschumi.net/build/18168
[Galaxy Note 3 Android Development] odoll:
Thx for the link!

But as these devices as hlte (or klte or ...) - which rely on 18.1 and can't be upgraded top any more recent versions - fell out of LOS-'support' ~ end of March and thus have been purged from the list in the meantime.
[Galaxy Note 3 Android Development] Hassan 4:
magisk causes issues currently with this rom (idk if it's device related or general bug), some sensors stop working when you flash it.

Anyway, I had the same issue about "Parsing package". What I did to fix it is that i flashed lineage18.1 and mindthegapps then flash magisk directly after them without booting first to system (All this done from lineage official recovery), then after completing android setup, simply install magisk apk over the one currently installed as system app. It will start normally then.

Currently I reflashed lineage without magisk as I don't need root anyway, I was just keeping it for Just in case I needed it :D
[Galaxy Note 3 Android Development] O's:
I have random reboots with and without Magisk, so I'm trying to hone in on why. I figured I needed root. Hoping a successful Magisk installation solves it. I love this ROM, but I've reinstalled it more than 10 times in the last week because of the reboots!

Did you flash Magisk by renaming the .apk to .zip?
[Galaxy Note 3 Android Development] Hassan 4:
Yeah I did flashing Magisk by renaming .apk to .zip, What device are you on, hlte? and maybe the random reboots are because of some buggy app, did you try to keep running the rom with minimal apps just to test if reboots are because of certain app?
[Galaxy Note 3 Android Development] O's:
I'm on N900T. It might be from Prime Video, but at least once it's happened before I get any apps.
[Galaxy Note 3 Android Development] odoll:
I dirty upgraded my SM-N9005 (hlte) from last 17.1 to the second 18.1 version on last Saturday and had two reboots since then (however as it's a dirty upgrade I won't complain ;-)

My first attempt with the first 18.1 version was without luck as I didn't knew that I have to disable Smart Lock, so I ended up in a reboot loop. In the end I used A2017X-remove+_all_+locksettings.zip before erasing system, flashing 18.1 and open_gapps-arm-11.0-nano-20210130-TEST.zip.

After the first reboot I also flash Magisk-22.1(22100).apk renamed to .zip and enabled Smart Lock in Security -> Trust Agents, again.
[Galaxy Note 3 Android Development] O's:
Edit: Let me install Magisk after all, even though it failed signature verification. I'll see if this install works.

Edit 2: Couldn't get through initial setup before a reboot.

Lineage recovery, 4/29 tmo nightly ROM, MindtheGApps 11, Magisk 22.
[Galaxy Note 3 Android Development] Kiki B:
I can't believe my old device (hlte) is still running so well - thanks tor this ROM.

I have but one issue, and it seems I am the only one: I can activate Bluetooth, but I do not find any devices to connect to. There is, however, one devices that always comes up and which does not even exist - the name is made up of numbers and characters: 90676414DB2033A8A9 - too long for a hardware address

Has anyone seen this before and has a remedy? I am pretty sure my baseband version should be OK: N9005XXUGOJ1?

Any hints are greatly appreciated.
[Galaxy Note 3 Android Development] kisilmike:
As far as I remember:

1) install Magisk ZIP via twrp, without any renames of extension. Just install zip.

2) boot into the system and some magisk icon already be there. Launch that, it will ask for the complete installation - confirm. After that, as far as I remember, the phone rebooted and everything was fine, you will see magisk manager with all information about installed magisk.
[Galaxy Note 3 Android Development] O's:
I think you're working with old information. There is no install zip anymore. See Magisk Github Installation page. https://topjohnwu.github.io/Magisk/install.html. There's only instructions to rename an apk as a zip.

In some custom recoveries, the installation may fail silently (it might look like success but in reality it bootloops). This is because the installer scripts cannot properly detect the correct device info or the recovery environment does not meet its expectation. If you face any issues, use the Patch Image method as it is guaranteed to work 100% of the time. Due to this reason, installing Magisk through custom recoveries on modern devices is no longer recommended. The custom recovery installation method exists purely for legacy support.

Download the Magisk APK

Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file.

Flash the zip just like any other ordinary flashable zip.

Warning: sepolicy.rule file of modules may be stored in cache partition, do not clear it.

Check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK.

As for using Magisk Manager, just installing Magisk now consists of all this:

If your device has boot ramdisk, you need a copy of the boot.img

If your device does NOT have boot ramdisk, you need a copy of the recovery.img

You should be able to extract the file you need from official firmware packages or your custom ROM zip (if using one). If you are still having trouble, go to XDA-Developers and look for resources, guides, discussions, or ask for help in your device’s forum.

Copy the boot/recovery image to your device

Press the Install button in the Magisk card

If you are patching a recovery image, make sure “Recovery Mode” is checked in options.

In most cases it should already be automatically checked.

Choose “Select and Patch a File” in method, and select the stock boot/recovery image

The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.

Copy the patched image to your PC with ADB:

adb pull /sdcard/Download/magisk_patched_[random_strings].img

Flash the patched boot/recovery image to your device.

For most devices, reboot into fastboot mode and flash with command:

fastboot flash boot /path/to/magisk_patched.img or

fastboot flash recovery /path/to/magisk_patched.img if flashing a recovery image

Reboot and voila!

Yeah, that's ridiculously excessive.
[Galaxy Note 3 Android Development] YF6y3MU1YonA:
Is there a way by now to use VoLTE on the Note 3 with LineageOS?
[Galaxy Note 3 Android Development] Kiki B:
Please ignore my above problem. As I expected it is not related to LOS.

I went back as far as the original firmware and now I know for sure that it must be a hardware problem.

Installing LOS 18 again now, I will use my phone without Bluetooth. This device/OS combination is still way better than any of the new devices :)
[Galaxy Note 3 Android Development] Unidave199:
Congratulations on Offical Status! I cant wait to give this a try.
[Galaxy Note 3 Android Development] gordonshamooay:
Found a bug that seriously interferes with using LOS 18.1. Previous versions (16-17.1) did not have it.

The essence of the bug is that if you choose to unlock without a password or swipe "Security => Screen lock => None" (need reboot to effect), the camera starting 2x Power button hotkey stops working and call a System UI stopping, as well as entering the "Clock" application (upper left) and smartphone settings (gear icon down right) from the curtain of the status bar.

I created Issue by this link but it is already closed.

System UI stopping at camera "2x Power button" hotkey, and "Clock"/"Settings" status bar links when the screen lock is disabled (#3422) · Issues · LineageOS / issues / android · GitLab

Expected Behavior 2x Power button hotkey (2x Menu button also) should open a camera app and "Clock" (tapping on time) and...

gitlab.com

I probably did something wrong. I ask you to take it into account in future updates as well. Thank you.
[Galaxy Note 3 Android Development] Hassan 4:
Anyone else facing when there's music playing and a notification sound comes, comes some noise from the speaker?
[Galaxy Note 3 Android Development] kisilmike:
Yes, the same problem! Sometimes (not always), with an incoming notification, the bluetooth sound suddenly stops going. Only reswitching BT solve the problem :(

If someone succeeds in finding a specific sequence of actions to repeat the bug, please write here, I will try to make a bug report
[Galaxy Note 3 Android Development] n00bieZ:
Yes!

Also the microphone is very buggy with voice recording apps (works fine with calls though)
[Galaxy Note 3 Android Development] kisilmike:
How can I expand the Quick Settings panel? When swiping, player control is displayed, I see only 3 quick settings buttons, instead of ~ 9+ in LOS 17.1. Very uncomfortable. Attached screenshot with expanded quick settings, as u see, only 3 buttons there.
[Galaxy Note 3 Android Development] r0mushii:
increase your dpi, probably around 390-420. it's under developer options

this happens as the ui adjusts dynamically for the media controls, linage can't do anything about it as it's an android 11 thing
[Galaxy Note 3 Android Development] kisilmike:
roger that, same problem
[Galaxy Note 3 Android Development] kisilmike:
Thank you! Set 390 dpi and now i have 6 icons. Any way 17.1 is better in this case, because more icons and the player does not interfere
[Galaxy Note 3 Android Development] oladushek111:
there are problems with split screen, from the very first unofficial build

- YouTube

Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

youtube.com
[Galaxy Note 3 Android Development] galaxys s:
how to root for line 18.1
[Galaxy Note 3 Android Development] MarkusOSx:
Flash magisk v23
[Galaxy Note 3 Android Development] flo108:
I can't get gps to work. :( Can someone, please, help me with this? Thank you!
[Galaxy Note 3 Android Development] odoll:
check your variant's modem/baseband version?
[Galaxy Note 3 Android Development] YF6y3MU1YonA:
But aren't there like other custom, unofficial ROMs which make it possible to make use of VoLTE? Or am I mistaken?
[Galaxy Note 3 Android Development] JJEgan:
Stock based roms for Volte .