yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] grumpycoder100:
Jotted that down, thanks [MENTION=4598795]Eleo[/MENTION] and [MENTION=6561802]jprimero15[/MENTION] !Will definitely be sticking around the forums to help in any way I can, even if my Note 3 is no longer here with me. Will also take a look at the logs shared :)
[Galaxy Note 3 Android Development] morische:
Hi,

How to discard the root?

And can applications be moved to the sd card if thrown?
[Galaxy Note 3 Android Development] TomPiXX:
Anybody else having issue RIL working with the latest build?

I got still "No Sim Card" error.
[Galaxy Note 3 Android Development] Eleo:
RIL is fixed on shared ROM. Please provide MORE info for troubleshoot
[Galaxy Note 3 Android Development] Michelsup:
You need the latest modem.

I discovered I can't receive MMS. I checked the APN but every setting is fine.
[Galaxy Note 3 Android Development] TomPiXX:
Makes sense. Where can I get it?
[Galaxy Note 3 Android Development] loudawg11:
This release lineage-16.0-20181009-UNOFFICIAL-hlte works great flashed over nougat lineage on the sprint note 3. It still has the BT Calling issue. But its up and running. Will try a clean install later to see if BT works. Great Work. Magisk 17.2 working
[Galaxy Note 3 Android Development] Scorpionea:
If your phone is n9005 hlte go here

https://xdaforums.com/showthread.php?p=71676276
[Galaxy Note 3 Android Development] Eleo:
BT calling issue is not fixed on oreo and pie. Please try to read previous posts in thread to familiarize yourself with the topic.

Good luck
[Galaxy Note 3 Android Development] loudawg11:
Thanks Eleo. Does the Bluetooth issues plagued the older devices because of older Hardware? I don't follow other devices I'm still a fan of my hlte Sprint Note 3 because it allows me to talk and surf the Internet over data simultaneously. Sprint abandon the two radio phones after the Note 3 and the S4 but they are slowly making a comeback with their new devices. But I still love the fact I can swap my battery on the Fly without charging and it supports to 256 memory cards and I still have a lot of fun with my IR blaster. Just curious if this is just a big issue with Android Oreo and Pie among other devices thanks for your input.
[Galaxy Note 3 Android Development] cafe-creme:
You have to change the apn main internet (not that of the mms).

You have to add to apn type "mms" and put your own server MMSC from its provider (not the one in the example).

Restart and send or receive.
[Galaxy Note 3 Android Development] TomPiXX:
Got it and flashed CP_N9005XXUGBOJ2.tar with Odin without any difference. The N9005 doesn't recognize the SIM card.
[Galaxy Note 3 Android Development] alisan28910:
Screen mirroring

Screen mirroring not working.
[Galaxy Note 3 Android Development] Eleo:
Please read:

https://xdaforums.com/galaxy-note-3/general/bootloader-baseband-bl-cp-samsung-t3582504/post77849359

Please read the previous posts in thread:

https://xdaforums.com/galaxy-note-3/development/rom-lineageos-16-0-t3840244/post77848148
[Galaxy Note 3 Android Development] DarkSam18:
hltmobile download link is the same hlte ?
[Galaxy Note 3 Android Development] Scorpionea:
You mean hlte tmobile same as hlte? If so no.. it should say hltetmo for tmobile
[Galaxy Note 3 Android Development] asassello:
So when it's finished (I mean LOS 16) - will it be available on the Lineage OS site? Like 14 before.
[Galaxy Note 3 Android Development] Eric_Lev:
Of course : https://review.lineageos.org/c/LineageOS/lineage_wiki/+/252385
[Galaxy Note 3 Android Development] Merotaha:
updates

where can i find the daily updates for this os ??

i need a link to bookmark and keep checking on the daily to keep updating my os and gapps
[Galaxy Note 3 Android Development] jprimero15:
HLTE is now OFFICIAL !!!
[Galaxy Note 3 Android Development] doombuger:
Nice! Would that mean the HLTEMO variant is now

official

too?

Have an updated link? :)
[Galaxy Note 3 Android Development] Eric_Lev:
Official builds (20190811):

HLTE: https://www.lineageoslog.com/16.0/hlte

HLTECHN: https://www.lineageoslog.com/16.0/hltechn

HLTEKOR: https://www.lineageoslog.com/16.0/hltekor

HLTETMO: https://www.lineageoslog.com/16.0/hltetmo

Official LineageOS Wiki ==> https://wiki.lineageos.org/devices/hlte

LOS su addon 16.0 (arm) and OpenWeatherProvider 16.0 (if needed) : https://download.lineageos.org/extras

Open Gapps (ARM 9.0) : https://opengapps.org/

==> Open Gapp pico or nano is strongly recommended to avoid modifying system files.

FYI :

LineageOS Changelog : https://www.lineageoslog.com/

LineageOS Builder : https://builds.lineageos.org/devices/

LineageOS Gerrit : https://review.lineageos.org/q/status:open

Thanks to Kevin Haggerty (@haggertk) and Nolen Johnson !
[Galaxy Note 3 Android Development] chrisg2010:
Hlte lineage os 16.0 download link

Fantastic news indeed! Thanks for all your efforts! I see the build page has already been refreshed for hlte, but its download link still points to an empty location. Do you know when this will be updated by the build infrastructure? Thanks
[Galaxy Note 3 Android Development] Eric_Lev:
FYI, a dirty flash of the first official build (20190811) works fine ... Right now ... but a clean flash is recommended!

==> HTLE : https://lineageos.mirrorhub.io/full/hlte/20190811/lineage-16.0-20190811-nightly-hlte-signed.zip

Before flashing: latest [MENTION=2693412]haggertk[/MENTION]'s build (lineage-16.0-20190612-UNOFFICIAL-hlte.zip) + open gapps pico + los su addon ... (nothing else)

After flashing: first official build + open gapps pico + los su addon

My procedure (TWRP 3.3.1-0 on my side):

0- Optional but recommended: Make a backup of your data (Nandroid backup... etc)

1- Download the zip files (latest build + open gapps + su) via a PC

(see my previous post for the download links: https://xdaforums.com/showpost.php?p=80050363&postcount=1186)

2- Boot your phone to TWRP (with the device powered off, hold Volume Up + Home + Power)

3- Connect your phone to your PC and copy the zip files on your SD card/Internal storage.

4- Wipe Cache, Dalvik cache and System ... but do NOT wipe Data

5- Flash build + open gapps + su (if needed)

6- Boot to system

7- Enjoy !

If this procedure fails, perform a clean flash ... Same procedure but 4- Wipe Cache, Dalvik cache, Data and System.

Thanks to Kevin Haggerty ( [MENTION=2693412]haggertk[/MENTION]), Nolen Johnson, LineageOS team, [MENTION=6561802]jprimero15[/MENTION] ... and all the other contributors!
[Galaxy Note 3 Android Development] odoll:
You don't have to bookmark. As long as it's an official build you should be able to DL updates over the air via your mobile. Check the update config in your device's system settings, to when and how often the mobile should check for updates.
[Galaxy Note 3 Android Development] jprimero15:
I talked with Nolen.. And i asked if he will create thread for Official LOS .. and he said "I will probably make one".. But don't expect anything yet... But if that happened.. I will put the link of official one here and I will just lock this thread for good..
[Galaxy Note 3 Android Development] odoll:
I fear this would be the recommended upgrade path for users still on the official LOS14.1!?

(I tried to upgrade to the unofficial 16.0 version several times, just wiping Cache, Dalvik cache and System.

The system ran good first, but after some time the launcher? always crashed when I tried to unlock the device, which made it nearly impossible to use. I tried to swich between trebuchet and pixel, but doesn't do the trick)

indeed ditto!
[Galaxy Note 3 Android Development] Eleo:
Always clean flash:

1. When changing android versions

2. When changing from one ROM to another.

You can dirty flash:

- If you update a version of a ROM on one android version to another version of same ROM on same android version.

Remember: the fact that you didn't notice any issue doesn't mean that it ended up being successful flash.

Good luck
[Galaxy Note 3 Android Development] Eric_Lev:
Migration from official LOS 14.1 to official LOS 16.0 :

A possible procedure (clean flash):

1- Make a backup of your data (Nandroid backup... etc)

2- Download the zip files (latest build + open gapps + su) via a PC

(see my previous post for the download links: https://xdaforums.com/showpost.php?p=80050363&postcount=1186)

3- Boot your phone to TWRP (with the device powered off, hold Volume Up + Home + Power)

(Optional but recommended: Flash the lastest TWRP (3.3.1-0 - https://twrp.me/Devices/) via ODIN and boot to TWRP)

4- Connect your phone to your PC and copy the zip files on your SD card/Internal storage.

5- Wipe Cache, Dalvik cache, Data and System

6- Flash build + open gapps + su (if needed)

7- Boot to system

8- Enjoy .... Hope so !

Official LineageOS Wiki ==> https://wiki.lineageos.org/devices/hlte

---------- Post added at 15:16 ---------- Previous post was at 14:18 ----------

FYI, Bluetooth/BT Calling works fine on official LOS 16.0 (20190811 - HTLE).
[Galaxy Note 3 Android Development] Atreya1:
Did a dirty flash worked a dream
[Galaxy Note 3 Android Development] dimii27:
Is it ok to install the official version over the last unofficial version without whipping anything at all? Just like I was updating every time?
[Galaxy Note 3 Android Development] chrisg2010:
Hangs on "Just a sec" after installing official LineageOS 16.0

I installed the official LineageOS 16.0 (first nightly build from 11 Aug 2019) on my Note 3 (N9005) using TWRP 3.3.1-0-hlte as per the "Clean Flash" instructions by Eric_Lev - thanks. Prior to flashing I cleaned the cache, Dalwik cache, as well as system and data partitions. I also used the Pico version of Gapps.

Flashing worked great and didnt report any errors. However, on reboot, I am stuck on the Android 9 "Just a sec" screen. The circle below this message keeps rotating, so it's not completely hung - but also not proceeding. I tried to reboot several times, I waited up to 10 minutes on this dialog, yet no luck.

I used the latest official LineageOS 14.1 before trying to upgrade today, and this has been working great for many months. Also, for what it's worth, TWRP displays that the flash target is "samsung/hltexx/hlte:5.0/LRX21V/N9005XXSGBRI2" whilst its installing LineageOS.

Did anyone else encounter this or are there any suggestions on what else I could try?
[Galaxy Note 3 Android Development] Mongoo8e:
Yes, I have just experienced exactly the same issue you have.

Edit: It is now working. I think by doing an Advanced Wipe in TWRP on all paritions except MicroSD and USB, then clean install has seemed to have fixed it.
[Galaxy Note 3 Android Development] Raxinzane:
Thanks for this. I got the update via the LineageOS updater app, not realising it's the update to 16.0. I wasn't really paying attention. It rebooted via TWRP without wiping anything. So far so good, I just had to flash the newer GAPPS and reinstall a few apps. I also noticed I can no longer hide the battery icon (I use powerline) or move the clock to the middle of the status bar. Other than that, happy so far.
[Galaxy Note 3 Android Development] chrisg2010:
"Just a sec" despite clean flash

So far I am still stuck on the "Just a sec" screen after selecting the language in the Android setup flow after booting the first time, having flashed LineageOS 16.0. I wiped all partitions (including system and data) using TWRP before flashing LineageOS 16.0, official nightly build from 11 Aug 2019. I also tried the pico, nano, and micro editions of OpenGapps version 9, ARM architecture.

I noticed that the phone gets extremely hot as it is displaying the "Just a sec" screen. I left it sit on that screen up to 10 mins. This never happens otherwise. It is as though some code in there is stuck in a tight loop, burning CPU cycles without progressing.

Any suggestions on how I could extract the information from my system which are required for a formal LineageOS bug report? As it happens so early, before Android has even been setup, I wonder whether logcat (required for a bug report) would actually be able to extract meaningful logs. Has anyone tried this before to diagnose such setup issues?

I have now reverted to LineageOS 14.1 and spent a few more hours setting my apps again, so would be interesting to know before I give 16.0 another try.

Thanks to the devs for the good work on LineageOS 16!
[Galaxy Note 3 Android Development] Atreya1:
Did you try a back up then clean install?????

---------- Post added at 11:29 AM ---------- Previous post was at 11:25 AM ----------

Did you try

1 Back up

2 Clean install ( as per instructions in the earlier post) rather than a dirty install?
[Galaxy Note 3 Android Development] dotKin:
Try deleting the google's setup wizard from TWRP. Mount system, and from the TWRP's file manager go to system>priv-app>SetupWizard and delete the apk inside the folder (after you flash gapps of course) That should allow you to use the LOS setup wizard instead the google's one
[Galaxy Note 3 Android Development] vasyekv:
Same problem here too, with official HLTETMO version.

Can't pass the Nano Gapps wizard.

Without Gapp OS works fine.

Return back ResurrectionRemix v7.0.2
[Galaxy Note 3 Android Development] dotKin:
Setup wizard is a mess, sometimes it even won't allow me to sign in into google accounts. And a suggestion, As I post before:
[Galaxy Note 3 Android Development] yumitot:
bootloader and modem

what bootloader and modem i need in this rom?

can i have the download link

im n900l user
[Galaxy Note 3 Android Development] Eric_Lev:
Bootloader and modem

See here :

==> https://androidfilehost.com/?w=files&flid=196446
[Galaxy Note 3 Android Development] jerryspring:
I know I can flash hlte to my hltemo...anyone else try it?
[Galaxy Note 3 Android Development] BillGoss:
Has anyone successfully installed official Los 16 on an encrypted phone with an on boot password? If so, how did you do it?

My story: I always run my phones encrypted with an on boot password (with the default password you might as well have the phone decrypted, but that's another story).

I noticed that there are decryption issues with TWRP (see https://xdaforums.com/galaxy-note-3/development/recovery-twrp-3-2-1-1-t3746760/post80043822) so I tested installing official Los 16 (190812) coming from the last official Los 14.1 using TWRP 2.8.4, 3.2.1, and 3.3.1.

Process:

- clean flash (wipe data and system): phone boots and prompts for password then says the password is correct but the phone needs to be reset.

- clear the encryption in TWRP (wipe>format data; tested with all versions): phone boots successfully.

- set password and encrypt phone: phone prompts for password and boots successfully, but TWRP (all versions) doesn't recognise the password.

So I'm back to Los 14.1 (had to use TWRP 3.2.1 as it's the only one (tested all versions) that correctly handles the encryption).
[Galaxy Note 3 Android Development] odoll:
How to "squeeze" another ZIP Install between LOS and Magisk Update?

@ll, since my hlte, which had been still on the latest 14.1 gets fresh updates again- thx - I ran into a little issue during the latest updates:

I "pimp" my mobile with Bluetooth drivers for the rSAP / SIM Access Profile offered by a 3rd party developer [1].

The problem is, that whenever I flash an updated LOS version, it seems to overwrite the additionally installed BT rSAP driver files and I also have to re-flash the rsap-instal.zip to get them back in.

However as I use Magisk these days, Magisk automatically "kicks in" immediately after the LOS update has been flashed and flashing the rSAP after that gets me into a "No SIM" situation.

I worked around this so far in the way, that I just DLed the new LOS version and manually use the following "update procedure":

Reboot to Recovery

In TWRP:

i) wipe davlik/cache, cache and system

ii) flash 1st LOS and 2nd GApps nano

Reboot to System and let things settle ...

Reboot to Recovery

In TWRP flash 1st rSAP and 2nd Magisk

Reboot to System

However you can image that this is a bit cumbersome. Does sb have an idea how I can ensure that the sequence of an (automatic) update is 1st LOS, 2nd rSAP and only after that Magisk?

[1] BTW: maybe the thread "LineageOS for Galaxy S II now includes rSAP" might be also interesting for the maintainers of this LOS version!?
[Galaxy Note 3 Android Development] BillGoss:
Here are two options:

1. Create a script in /system/addon.d, similar to the gapps or Magisk ones.

2. Wipe system before flashing and then flash Los, rSAP, gapps, Magisk.
[Galaxy Note 3 Android Development] jerryspring:
Yep! I was correct in thinking I think. This ROM, havoc and evolution along with any post nougat ROMs, 900t reboots after data signal is lost. I recall this happening to other users too. Anyone else?

Could maybe me flashing an older recovery might help?
[Galaxy Note 3 Android Development] odoll:
Re: How to "squeeze" another ZIP Install between LOS and Magisk Update?

> 2. Wipe system before flashing and then flash Los, rSAP, gapps, Magisk.

that my workaround ;)

> 1. Create a script in /system/addon.d, similar to the gapps or Magisk ones.

Thanks for that hint, however as I'm more like a script kid than a programmer (or better a script doter) does TWRP execute these shell scripts during an update?! To me they look more as they get executed when he system boots up!?

I see the "install FILENAME zip file." command in the "TWRP Commandline Guide" but so far I can't spot such a command in neither 99-magisk.sh, /data/adb/magisk/addon.d.sh nor boot_patch.sh

Still searching to understand how "Magisk" lets TWRP unpacking the boot image, decompressing the ramdisk, extracting the ramdisk and patching the ramdisk for Magisk support, after an OTA LOS update ...
[Galaxy Note 3 Android Development] jerryspring:
Anyone know what the dot in status bar is? I noticed it on havoc and Evo also.
[Galaxy Note 3 Android Development] jprimero15:
No dot on mine.. Havoc.
[Galaxy Note 3 Android Development] jerryspring:
It goes away when I take one of the status bar icons away.
[Galaxy Note 3 Android Development] rayman95:
Got sometimes on havoc but it disappear I don't know how...
[Galaxy Note 3 Android Development] jerryspring:
Anyone else getting screen really dim when receiving a phone call?
[Galaxy Note 3 Android Development] BillGoss:
The os assumes that there's a notch and will collapse status bar icons to a dot if there's too many of them.

---------- Post added at 08:32 PM ---------- Previous post was at 08:19 PM ----------

If you look at the updater script for the rom you'll find these lines;

run_program("/tmp/install/bin/backuptool.sh", "backup", "/system");
...
run_program("/tmp/install/bin/backuptool.sh", "restore", "/system");

And the backuptool.sh script (in the install/bin folder of the rom zip file) runs the addon scripts to backup and restore the programs.

So it's nothing to do with TWRP other than TWRP kicks off the process by executing the updater script in the zip file.

And one last thing, it's good practice to quote the post you're replying to so that people can see what you're referring to and to the the person know you're responding to them (XDA send a notification if you are mentioned or quoted).

So please use the "reply" button on posts when replying (like I just did to reply to you).
[Galaxy Note 3 Android Development] jerryspring:
Can't do that on the app. Only can on a browser
[Galaxy Note 3 Android Development] BillGoss:
Are you referring to my comment to [MENTION=8067849]odoll[/MENTION] regarding using the reply button?

If so, it is available in the app (I'm using XDA Labs) - see screenshot.
[Galaxy Note 3 Android Development] jerryspring:
Um...how u think I been replying to posts? Silly.
[Galaxy Note 3 Android Development] asassello:
I installed LOS 16 juat yesterday and so far it's amazing!!!

The biggest problem for me with LOS 14 and before with unofficial LOS 16 was battery life which was worse than stock. Now it seem that's it's at least similar which would be enough for me.

I haven't tested yet if Bluetooth and Google Pay work.
[Galaxy Note 3 Android Development] NanDroider:
If BT Call works now, what was the fundamental change that it is working now?

Thank you to all developers and contributers to kept Note 3 alive.
[Galaxy Note 3 Android Development] odoll:
Re: How to "squeeze" another ZIP Install between LOS and Magisk Update?

On 16th August 2019, 09:32 PM BillGoss posted:

> So please use the "reply" button on posts when replying (like I just did to reply to you).

Hm, think I did that as I do now and I also set the Title as "Re: How to "squeeze" another ZIP Install between LOS and Magisk Update?" so the topic / context I'm replying to should be clear.

Anyhow, thanks for your feedback.

> So it's nothing to do with TWRP other than TWRP kicks off the process by executing the updater script in the zip file.

If I understand your hints aright: lets assume I manually downloaded e.g. lineage-16.0-20190818-nightly-hlte-signed.zip to my mobile and that file would then sit in /storage/emulated/0/download.

I then reboot into recovery and once TWRP comes up I'd manually select that zip for an update (Install option in TWRP).

Even if I'd select the rsap_install.zip file to TWRPs installation queue too, once I acknowledge the installation, the updater script /lineage-16.0-20190818-nightly-hlte-signed/META-INF/com/google/android/updater-script would also execute the scripts in /system/addon.d, namely

70-gapps.sh

99-magisk.sh

and the latter would already Magiskfy the updated LOS even before my 2nd queued rsap_install.zip comes into play?

So the idea would be to e.g. create a - lets say - 85-rsap_android.sh file in /system/addon.d, which then would execute the install scripts of the rsap_install.zip file before 99-magisk.sh kicks in?

(And there's no need to add rsap_install.zip to TWRP's installation queue.)

And to keep it simple, the potential command "sh adb install /storage/emulated/0/download/rsap_install.zip" in a fictional 85-rsap_android.sh file would instruct TWRP to execute rsap_install.zip's installation scripts?

BTW: what would be a good / safe place / directory for the rsap_install.zip file on the mobile.
[Galaxy Note 3 Android Development] asassello:
BT calling works, however caller tells me that he can hear me not that well as it was on stock.

Google Pay works too, but there are 2 things:

1. it seems that I need to put phone closer to the terminal, but I paid successfully in 2 shops today,

2. in third shop it didn't work and the terminal was displaying a message - to only use one card at the moment (which I was doing using only my phone...)
[Galaxy Note 3 Android Development] BillGoss:
Lol: you may have manually quoted bits from my post but because you didn't use the reply button, the text of my post and the back-link to my post didn't get added, nor did I get a notification that you replied.

So, please use the the reply button.

You're partially on the right track. An add-on script, if written properly, will backup and reinstall rSap before Magisk gets reinstalled. But it's not as simple as reinstalling the original script. Have a look at the Magisk and gapps scripts and see how they work and compare them to the updater scripts in the original zip files. You'll see they are related, but not identical.

If you find that writing the add-on script is too difficult, then you can use the workaround.

There is a third option which is to use a TWRP command file (Open Recovery Script or ORS, see https://twrp.me/faq/openrecoveryscript.html). You would create a file like the one I've attached, put it in /cache/recovery/openrecoveryscript and then boot into TWRP. TWRP will process the file and reboot the system if everything succeeded.

I use ORS a lot for doing my backups and installs. I've written shell scripts that produce them so that I don't have to manually create them.
[Galaxy Note 3 Android Development] jerryspring:
Who is this post referring to? U have no quotes

---------- Post added at 03:08 AM ---------- Previous post was at 02:58 AM ----------

Bluetooth not seeing any device? Do we use Bluetooth call fix zip for that as well?

---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------

Where is the fix zip at?