yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] Mohamedkam000:
They've stopped producing note3 batteries since 2016

I'm using original battery too, a while ago it was draining so fast, like 7% in 2 minutes but now it's stable, and even more powerful on havoc 3, using gpj2 cp & brl2 bl.
[Galaxy Note 3 Android Development] chooks06:
A battery that old should be replaced by now.

All the more if you see it bulging.

If it changes to full very quickly and shows signs of discharging erratically, it's a strong sign battery is reaching end of useful life.

I'm not sure whether you can get originals nowadays. Would probably have to rely on after market products.
[Galaxy Note 3 Android Development] asassello:
Yes it's charging too quickly in my opinion. I'll be checking that.

I contacted Samsung customer service and they gave me contact to shop (it's one of their service centers) that sells batteries for about 25$.
[Galaxy Note 3 Android Development] chooks06:
I could still get Samsung packaged Note 3 battery in Singapore some time last year (about 20 - 25USD). I'm pretty sure it's not the China sold "OEM" stuff cuz I also bought that (less than 10USD). They come with the same serial number, regardless of seller and the OEM is actually the battery producer..lol.

The real deal I could register on Samsung.

I believe there are some pretty reliable after market products available.

---------- Post added at 11:15 AM ---------- Previous post was at 11:13 AM ----------

Best to get that if you plan on using the phone for at least another 2 years.
[Galaxy Note 3 Android Development] MarkerB:
I have the same problem. I've tried every combination of several Pie-based ROMs, lastest TWRP, Gapps nano, SuperSU and Magisk, using both QD2 and PL1 baseband/modems, restoring to stock, full reformatting, on two different N900T devices. All exhibit random reboots at a period from every few minutes to several hours.

I also had the same problems with Oreo as solgae did.

That leads me to wonder if there's anyone that has ever been able to make a daily driver from Oreo or Pie on a Samsung N900T (T-Mobile Note 3). I've given up after a week of these attempts, and went back to a fresh install of LineageOS 14.1. This setup has always been stable, but with the infamous Gmail push/sync glitches.
[Galaxy Note 3 Android Development] Raxinzane:
Vibration intensity

Anyone know how to increase the vibration intensity? The slider from 14.1 is gone.
[Galaxy Note 3 Android Development] Mohamedkam000:
You have to be rooted, install smartpack kernel manager:

https://github.com/SmartPack/SmartPack-Kernel-Manager/releases

Open it, and go to "Misc" section, you'll find vibration strength.
[Galaxy Note 3 Android Development] Raxinzane:
Great, thank you!
[Galaxy Note 3 Android Development] granfarz:
Any One have Experiences camera mod with this OS?

Thanks in advance.
[Galaxy Note 3 Android Development] Mohamedkam000:
What "camera mod" are you talking about?

You mean like ported camera apps? Well .. there's a lot that are not fully working, we have an arm32 device so don't expect much support.

You can use Snap Camera HDR, manual, but the best I've ever used.
[Galaxy Note 3 Android Development] Thivanka Thushan:
Sm 9005 flashing custom rom

I tried to flash this zip file using twrp recovery.but it's not flashing.I'm using sm n9005 version.can you help me.I'm new to this

---------- Post added at 10:20 AM ---------- Previous post was at 10:14 AM ----------

I'm using twrp recovery.but file not flashing.I tried 3 custom roms.same with all roms. I'm using note 3 sm n9005.can someone help
[Galaxy Note 3 Android Development] Mohamedkam000:
What error are you getting on TWRP?

You have to use latest 3.3.1 TWRP recovery:

https://eu.dl.twrp.me/hlte/

Make sure your screen is original AMOLED, not LCD, or it won't boot.
[Galaxy Note 3 Android Development] MonsterPickleRick:
is this good for daily driver ? just asking ? want to try
[Galaxy Note 3 Android Development] chooks06:
I haven't tried it yet cuz I'm waiting out for another hlte to be back.

If you have another phone for a daily driver, go ahead and try. IMO, sometimes we can encounter issues because we setup our phones differently.

Even if there are no issues reported, it may not mean my device will be running smooth.

From my observation on my this thread, I don't feel there are "major" issues for my usage, example, BT important for some but not for others.

But until I try to use it the way I use my daily driver, it can be quite subjective.

Just sharing my opinion.

Have a great weekend! Cheers!
[Galaxy Note 3 Android Development] rayman95:
yes running perfectly with last lolz v12 now....thank's to the chief..:good:
[Galaxy Note 3 Android Development] Raxinzane:
Noob question: if I flash Magisk, would I need to factory reset?
[Galaxy Note 3 Android Development] Atreya1:
No need to factory reset.

Flash Magisk in twrp

Restart

Check Magisk is installed and up to date

Job done
[Galaxy Note 3 Android Development] Raxinzane:
Great, thank you! Didn't realise it was this simple.
[Galaxy Note 3 Android Development] MarkerB:
It might depend on which variant you're using. I haven't been able to get this to be stable on my two T-Mobile SM-N900Ts with the latest QD2 baseband, after complete reformats, and trying different things for a few weeks. It randomly reboots a few times a day, to several times an hour. That's hardly a daily driver.
[Galaxy Note 3 Android Development] Xforce.gp:
Principiante

Ragazzi come posso aggiornare Utilizzando l'app LineageOS Updater? Ci sto provando ma mi esce scritto nessuna connessione a internet

Grazie

Guys how can I update the LineageOS Updater application? I'm trying but no internet connection is written to me
[Galaxy Note 3 Android Development] Murzilka85:
please tell me, what parameter should I configure in the mixer path so that the sound of calls when the headphones are connected goes to the headset, and not to the speaker? I liked that the sound of notifications plays in the headphones, but there are no calls. And tell me, is there a multi-window here, I can’t find
[Galaxy Note 3 Android Development] jerryspring:
U mean fqd2. Runs fine on my note 3s except for data and cell drops. What u think is causing your reboot issues? Mine will random reboot after cell signal is lost. Does this on havoc, resurrection remix and aex.
[Galaxy Note 3 Android Development] MarkerB:
Oh... does that extra character mean something different? I've always seen just the last three characters used as the short ID of a baseband version. In fact, I just Googled "baseband qd2" and got 2000+ results, and only 45 results for "baseband fqd2".

Gosh, I wish I knew the cause. I had seen your August 2019 and later posts about signal loss being the initiator, so I'd put mine in a steel box to check it out. It didn't seem to make a difference, so I'd say signal seems to have no effect on my problems. Actually, my phones reboot randomly even before I've installed the SIM card.

Someone said in this or a related Note 3 Pie thread that they were certain the hltetmo modem code was crashing, and that would cause the Pie kernel to reboot. They even published posted some logs, but no one ever responded... not publicly at least. Not sure if that was you, jerryspring, who'd gotten as far as posting the logs.

Because of these Pie reboots, my daily driver is still LineagoOS 14.1. Yet, in any LOS 14.1 installations I've tried on hltetmo, I've always had constant problems with Gmail push failing, the system GUI crashing, and wallpaper and other settings sometimes resetting to default. Maybe that's just Nougat's symptoms of the same modem crash, whereas Pie just reboots. I also tried downgrading to the previous modem version (N900TUVSFPL1), but was still seeing the same Pie reboots.

I also found the same problem on Pie version of LineageOS, Havoc, and Resurrection Remix. I haven't tried AospExtended, but at this point I sorta' figure any AOSP version will do the same thing.
[Galaxy Note 3 Android Development] Eleo:
No. Only last 3 characters are important. Not the f of fqd2 but the qd2 part
[Galaxy Note 3 Android Development] jerryspring:
Have link to those posts? Thanks
[Galaxy Note 3 Android Development] MarkerB:
Sorry, I had looked for a while for the modem crash log post, and I couldn't find it. I looked again to no avail. I'm not sure which one of the Note 3 devel forums it was in. I do remember the log post was earlier in 2019, asking for a developer to take a look, and no one ever replied to it.

I assume it's the post about the modem crashing that you meant. I also mentioned your posts, but I don't think you need links to them!
[Galaxy Note 3 Android Development] jerryspring:
Ok. Lol. So many threads and posts. Sigh!
[Galaxy Note 3 Android Development] MarkerB:
I guess I'll ask again now: Has anyone with an N900T ever been able to get LineageOS 16.0 Pie to run without frequent random reboots?

... or for that matter, any AOSP-based hltetmo Pie ROM?

I certainly have not, trying on two different devices, with full reformatting, and several modem/baseband versions.
[Galaxy Note 3 Android Development] SeriousX:
Hello friends! So i was forced to use my old note 3 for a week as i sold my main xiaomi and ordered new honor and had to wait for it. So I installed this ROM on my note 3.

I was surprised with ringtone it offered in Sounds app. Now i have a question - how can i get those sounds for other phones? I tryed sending over BT apk of sounds app. It installed but i cannot see it or chose it while picking ringtones.

Where can i dig out the sound file from my note 3?
[Galaxy Note 3 Android Development] anthrax68:
I have a N900T (T-Mobile) and I have been using it with LineaseOS 16.0 Pie as my daily phone since July 2019, the caveat being that I haven't updated the ROM since September. I have not had any random reboots at all. The worst thing I have had happen to me was an occasional unresponsive random freeze displaying a blue screen showing the digital clock, but I found out it had to do with the SmartLock or SmartCover (not sure exactly what it's called, it's whatever detects if a flipcover is on or off), and had to disabled it in the settings. No problems at all since then.

This is what I currently have on my phone:

- Android Version: 9

- LineageOS Version: 16.0-20190926-NIGHTLY-hltetmo

- Build Date: Thu, Sep 26 08:09:50 UTC 2019

- Baseband Version: N900TUVUFQD2

- GApps v9.0 (Pie 9.0.x), ARM, Nano - downloaded on 2019-07-04 (open_gapps-arm-9.0-nano-20190704.zip)

I have not tried any of the official builds since the 20190926 build. Prior to that build, I used Jprimero15's "unofficial" build 20190626 (in post #1060) for about 3 months with no problems at all besides the aforementioned flipcover detection issue.

It has been working well for me so far. No issues with BlueTooth or WiFi, no issues with phone or texting, also tried 64GB & 128GB MicroSD cards, all working great as far as I can tell. I don't know if this matters, but my phone is not unlocked, still tied to T-Mobile.

Will probably download the latest official nightly build on 2020-01-01 to try.
[Galaxy Note 3 Android Development] MarkerB:
Thank you so much for the detailed response! I will try the exact LOS Pie version and Gapps you quoted... if I can find them. Please do let me know what happens with your installation of the 2020-01-01 build.

I hadn't thought about specific carrier, as my phone is unlocked and I'm using the AT&T MVNO reseller "Pure TalkUSA". However, since the random reboots also happen when there's no SIM card, it's hard to believe the carrier could be the issue.

I'm sure jerryspring will also be interested in these details of your working installation, since he was having similar problems.

---------- Post added at 11:23 PM ---------- Previous post was at 11:17 PM ----------

I cannot find that old LineageOS version anywhere. I did find the cited Gapps already.

Do you still have the ZIP installation file for the Lineage version you've been using? I will PM you a place to upload file, in case you still have it available.

Thanks!
[Galaxy Note 3 Android Development] vasyekv:
Post #1228

Latest LineageOS 16

https://download.lineageos.org/hltetmo

Latest GAPPS

https://opengapps.org/

(ARM, 9.0, Nano)

After 4 month no problem at all with phone. I do regular update over Setting>System > Advanced>Updater.

I used this phone in 3 different places North America, Europa , Asia and LTE works fine with international OneSim even in Cuba works too, but only 3G :) .

I had reboot and freezing problem with my Xiaomi Mi A2 (Android One - v9.0) , but not with Samsung note III N900W8.

Great ROM ! Thank you developers!
[Galaxy Note 3 Android Development] MarkerB:
I had read your old post and tried your sequence before, but I figured I'd try it again with all the latest builds. I've formatted the phone, installed the last stock ROM with QD2 baseband, booted that, installed the latest TWRP, wiped all but int/ext sdcard, and installed the latest LOS16 ROM. I will run it for 48 hours. If there are no random reboots after that, I'll install Gapps, run for another 48 hours, and then Magisk 20.1.

In the meantime, I have some questions for you:

How did you determine that the system had to rebooted between installing the ROM, Gapps, and Magisk? I've rarely heard anyone claim that is needed, and sometimes it is explicitly said that Gapps should be installed immediately after the ROM without an intervening reboot.

You have a N900W8, whereas I'm talking about a N900T. That could make a huge difference in each of our experiences. Certainly other N900 variations have been working with the official LOS 16 Note 3 releases. I started this thread by stating that I've never seen anyone with a N900T claim to install LineageOS 16.0 hltetmo, and not suffer from random reboots. With you having a different device, I'm not sure your experience would apply.
[Galaxy Note 3 Android Development] vasyekv:
Sorry I have no experiences with N900T , only with N900W8 and N900V.

I had problem with installation and I solved for myself.

For N900V I did install latest modem driver, but done time ago, got from n900v forum...

Both phones works fine.

Xiaomi it's different OS and a problems was with some application.
[Galaxy Note 3 Android Development] anthrax68:
I uploaded the file "lineage-16.0-20190926-nightly-hltetmo-signed.zip" to the GoogleDrive link that you sent in the PM.

Just a reminder, prior to using the "official" 20190926 build, I was using Jprimero15's "unofficial" build 20190626 (in post #1060, filename "lineage-16.0-20190626-UNOFFICIAL-hltetmo.zip") without any random reboots, so download and try that one as well.

I forgot to mention last time, not sure if makes a difference... Before I even rooted the phone and installed LineageOS 16.0, I first updated it to Samsung's official Lollipop 5.0 N900TUVUFQD2 rom with Odin (since the phone was on Android 4.4 or something like that), look for "TMB-N900TUVUFQD2-20170502175931.zip" and "Odin3_v3.13.1.zip" if needed.

Also, I used TWRP v3.2.3-0 and Flashable Magisk v18.0 when I first rooted it. Last month I updated it TWRP v3.3.1-0 and Magisk v20.1, still working fine for me.

Good luck!
[Galaxy Note 3 Android Development] MarkerB:
Great! Thanks.

Yes. I've been doing that lately.

In the interim I had seen the post from vasyekv about the flashing/booting sequence, and so I'm trying that first. Did you find that you needed to flash the ROM and boot it first, and then later go back and flash and boot to Gapps and Magisk, all in separate passes?

I'll try your releases if I don't get anywhere with the slow flashing and testing protocol I'm trying, as documented in this post.

Thanks again!
[Galaxy Note 3 Android Development] MarkerB:
I got so far as installing the latest LOS 16 hltetmo build, running it for 18 hours without a problem, and then installing Gapps. Within an hour of that, my phone had a random reboot while in Gmail. I didn't get to Magisk.

So... now I'll try the regressed versions suggested by anthrax68 in his post. To be safe, that means reformatting, reinstalling the stock ROM, TWRP again, etc...
[Galaxy Note 3 Android Development] odoll:
Lost BT Device DB (LOS 16.0 Official)

Sorry for my post in this thread, but we don't seem to have one for the official version, yet!?

Anyhow: think it happend with https://mirrorbits.lineageos.org/full/hlte/20191224/lineage-16.0-20191224-nightly-hlte-signed.zip. (sm-n9005)

I use a Miband and a few others as BT device to Smart (un)Lock.

Lately I was wondering I had to enter my PIN every time activating it. I found BT switched off, but even turning it on again didn't help. So toggeled the plane mode, but the hlte rebooted after a short time.

When it came back up I no longer had any devices in the list of paired devices ...

PS: I also found my (BT) device's name reverted to its standard (I think Samsung Galaxy Note3 or a like) and I had to change it back to what I had been before. (noticed it when repairing)
[Galaxy Note 3 Android Development] MarkerB:
I formatted by device, ODIN flashed the last stock QD2 ROM, then ODIN flashed the latest TWRP, flashed your "16.0-20190926-NIGHTLY-hltetmo.zip", and ran it for a while. It seemed good.

Then I flashed "open_gapps-arm-9.0-nano-20190704.zip", and ran it for a while. It still seemed good.

Not wanting to install Gmail yet, I installed the Aqua Mail email client with the push option, and after several hours it crashed. Remembering that many crashes happened with Gmail while I was manually refreshing mail, I'm now trying Aqua Mail without push enabled. Maybe push does something weird with the modem. Someone on this thread had suspected the modem tends to crash. This might explain why LOS 14.1 push stops working a lot, but doesn't reboot. LOS 16 might decide it's best to reboot the whole device after a modem crash. This is all conjecture, but that's all I have from my limited view of things.
[Galaxy Note 3 Android Development] vasyekv:
Maybe it's big reason to use just original mail app from Lineage OS ?

Or try MS Outlook, so far works very good.
[Galaxy Note 3 Android Development] MarkerB:
My suspicion is that any mail client with push notification will have problems, since both Gmail and Aqua Mail did. That would include the native Android app and Outlook too, which I believe both have IMAP push. Since anthrax68 doesn't have any problems on his phone and presumably uses Gmail, I'm not sure any of this applies to everyone.
[Galaxy Note 3 Android Development] anthrax68:
When I first started with the unofficial build, I would flash them in separate passes - I would flash the ROM first, then backup via TWRP, rename the backup so I'd know it only had the ROM, boot and test for a few days, then next day after, flash GApps, backup and rename the backup so I'd know it had both the ROM and GApps, then started testing for a week from there. I'd do the TWRP backup every set of flashing (such as Magisk) or significant app installations. I did it that way because I was trying to figure out the issue with the flipcover (unbeknownst to me at the time what the issue was), so that I could go back to the previous backup while trying to determine what was causing it.

With the official build, I flashed the ROM and then GApps in the same pass before booting. I've flashed the ROM and GApps (in that order) many times, in the same pass, without problems.

I don't use any mail apps at all, so I don't know, maybe that's really what's causing your random reboots. I check my email via my account's webmail via Chrome or the built in WebBrowser. You might have found a major bug with the ROM, maybe? Or it might be the mail apps themselves... I have a few apps that worked on Android 8 that do not work on Android 9 (they would crash, but did not cause a reboot), and had to look for the latest version of those apps.

In regards to Push Notifications, I do use a ABC News app for my local TV news station, and have Push Notifications for local breaking news, and I do receive the push notifications even with the phone locked. Does not crash my phone or reboot it, seems to be working correctly. On the other hand, I have the United Airlines app with Push Notifications turned on for Flight Status changes, and I never receive the Notifications at all - but it does not crash or reboot my phone either. So I can't really say if Push Notifications is working correctly, seems to be app related to me.

If you can narrow down to the reboot being related to push notifications on mail apps, try to see if you can live without the push notifications or if there are other people with similar issue and if they have a workaround. I have issues with the built-in Camera app not writing to DCIM in the MicroSD card and the built-in Gallery app not actually deleting photos, and saw in other LineaseOS threads (for other phones) where people had similar issues and I ended up using workarounds (i.e. other apps) that everyone else used as a workaround.
[Galaxy Note 3 Android Development] MarkerB:
I'm glad you noticed that. I don't think it's ever helped me to flash in separate passes, so I'll stop trying that too.

I think that is significant. Since my last post a few days ago, I've only seen one random reboot with Aqua Mail having push turned off. Perhaps IMAP push is more liable to trigger this problem, but that it exists nonetheless.

Hmm... If that were true, wouldn't all the other Note 3 variants exhibit this behavior too? I think it's more likely that the modem baseband has a bug, but it wasn't really a problem until the Pie kernel decided to reboot when the bug was triggered. Nougat variations never reboot on me, but have annoying push-related glitches. I think it could all be the same modem baseband problem, but just a different kernel response. Keep in mind that even the latest modem baseband (QD2) is from spring 2017, and meant for Lollipop (Android 5.0). Since then we've had Marshmallow, Nougat, Oreo and now Pie... all that were possibly not compatible with such an old modem baseband. Have the APIs to the radio changed enough over the years, even subtly?

Sadly, I cannot live without push, as I need to be on-call for work emergencies. No email clients I like will check mail often enough through polling.

I've been posting a lot to the few people who had reported similar issues, but your responses are by far the most complete. I thank you for that! Most have just not answered, or a few have since moved away from the Note 3. I've just always given up and gone back to LineageOS 14.1, which I've now done again for a spell. I have a feeling after spending 50+ hours on this over the last year, I'm never going to fix it by trial and error.

I don't want to ditch this phone because I haven't found a modern one that fits my criteria. The Note 3 also seems to be the most supported old phone around. It's surprising how few new phones are supported by official LineageOS releases.

Thanks again anthrax68; you're the most solid source of information I've had.

Thanks also to official maintainers haggertk and npjohnson, who probably don't own the T-Mobile variant, and can only just build blindly.
[Galaxy Note 3 Android Development] kimi21105:
Good
[Galaxy Note 3 Android Development] MarkerB:
Thanks again for your efforts in both trying things, and documenting them so thoroughly.

It's funny, because the nice thing about Pie on my N900T is that my push Gmail is very reliable; it's the random rebooting that kills me. For you, it is apparently the entirely other way around!

Maybe the carrier locking is the problem, since my two N900Ts are unlocked. Since my random reboot problem exists before I even insert a SIM card, I kind of doubt it has anything to do with the carrier. I mean, unless the unlocked aspect of the phone can cause random reboots in Pie. Seems unlikely, but this is way above my pay grade.

Also... Push shouldn't have anything to do with T-Mobile's systems, since I assume you were on WiFi a lot of the time you were testing. If you were only using cell data for your tests, it would be easy to check again over WiFi.

Anyway, your findings are very interesting, but they seems to be creating more questions than answers.

I still applaud your work!