yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] rockmanneo:
Thanks for the ROM.

Installation went rather smoothly.

OpenGapps gives me lots of "app is closing" messages. I downloaded the arm 8.1 mini version. Should I go with arm64?

Also now my phone can't connect to the network (t-mobile network not available). Any advice? Thanks.
[Galaxy Note 3 Android Development] iesous-kurios:
What was your installation procedure? Sounds like a problem that occurs sometimes when a flash is done over a previous installation. Try a full wipe and clean install. Setup always allows me to restore apps and recent calls/texts but for more security you can download an SMS backup app if that's important to you.

The gapps arm Pico version is what I download and use.

Do you know how to view your apn settings?

I'd do a clean install and see if you still experience problems.

Besides Bluetooth calls not working still this ROM has been working fine as my daily driver.
[Galaxy Note 3 Android Development] rockmanneo:
I upgraded from DomPop TekHD ROM. I did the wipe (system, dalvik, data, cache), then installed the ROM.

I noticed the modem is still at N900TUVUFOB6. I'm trying to update to N900TUVUFQD2 (I read online that's the baseband to use for LineageOS 15.1) multiple times but it either gave me unknown baseband or back to FOB6. Does your ROM use FQD2 modem version?

Should I do complete install with official FQD2 ROM first before installing your ROM?

Or wiping the internal storage will help?

I know where the APN settings is. I compared it with Tmo APN online and they look the same.

Thanks.
[Galaxy Note 3 Android Development] iesous-kurios:
I'm on the QD2. I had to remove battery then boot into bootloader as opposed to shutting phone down manually and booting into bootloader before the new baseband would stick. Did you follow that step as well to ensure the odin flash works?

Wiping internal storage might help, especially if coming from completely different ROM.

Odin baseband flashes should be able to work without affecting ROM installation, iirc they are on different partitions.

If you're still on lineageOS Might want to remove battery and go directly into bootloader to flash baseband then see if it's working before doing more time consuming wipes.
[Galaxy Note 3 Android Development] rockmanneo:
Thanks for the suggestion!

Tried the remove battery trick and after a few tried the baseband finally sticks!!

Downloaded the pico version but it still gave me "Google Play services keeps stopping"

Google Play store stuck at Checking info...
[Galaxy Note 3 Android Development] iesous-kurios:
Double check it's the right gapps?

Arm

8.1 (not 8.0)

And Pico

Maybe downloaded the 8.0 by accident?
[Galaxy Note 3 Android Development] iesous-kurios:
Might also try force stopping all of your Google apps. Like services and market and such. Then clear the cache/stored memory, reboot and try opening play store again.

Not sure if your installation was a full clean one with wiping internal storage as well. I've been doing full wipes each time I flash new build.

I want to make sure problems I see are true to the ROM and not because of a bad dirty flash or something.
[Galaxy Note 3 Android Development] rockmanneo:
Yeah I think I'm just gonna do full wipes and clean install the ROM. Just found out GPS doesn't work either.

BTW what Google Play Services version do you have? Thanks!
[Galaxy Note 3 Android Development] iesous-kurios:
Here is screenshot of my Google play services version.
[Galaxy Note 3 Android Development] rockmanneo:
Just an update, I finally did an internal storage wipe and reinstall, now everything works!

Thanks for all the support Jfuginay!!
[Galaxy Note 3 Android Development] iesous-kurios:
Cool, good to know. Should be able to do dalvik/cache wipes for future build flashes. Will make another build before the end of the weekend.
[Galaxy Note 3 Android Development] iesous-kurios:
9/15 build up is up.

Still no working Bluetooth calls.

:/
[Galaxy Note 3 Android Development] Lee_Falcon:
My wifi doesn't work as well as Bluetooth

Tried turning on wifi but it switches back to off..as for Bluetooth it stays on but nothing happens
[Galaxy Note 3 Android Development] iesous-kurios:
Did you do a clean wipe?

Wipe dalvik and system and internal and cache?
[Galaxy Note 3 Android Development] iesous-kurios:
Dark theme screenshots
[Galaxy Note 3 Android Development] Lee_Falcon:
Did every wiping mentioned and it's still the same.
[Galaxy Note 3 Android Development] rockerdudelive:
how is the lte to 3g on this rom? I've had problems with other LOS roms that won't get incoming calls when I'm on lte and the phone is asleep. about 10% of the time someone has to message me saying the call won't go through. It's like the phone won't drop to 3g from lte when it needs to when it's asleep
[Galaxy Note 3 Android Development] iesous-kurios:
I haven't had any problems receiving calls whether on lte or 3g. My workplace has spotty service so I'm constantly going between lte and 3g depending on where I am in the building. Calls have been coming in just fine.

Are you on latest bootloader/modem?

Also, are you on t mobile? Might be a carrier issue if you are on another provider
[Galaxy Note 3 Android Development] o_deacon:
How to fix it?
[Galaxy Note 3 Android Development] rockerdudelive:
Yes I am on the latest bootloader and modem. I've been having the problem on nougat ROMs. I have tried a few Oreo rooms and while I haven't tested incoming calls, I notice my signal bars don't fluctuate. And I am on T-Mobile. I've tried hlte and hltetmo based ROMs and they both do the same (nougat ROMs) so fingers crossed it's fixed in Oreo.

I got a new sim card out of desperation, but it's one of those break away ones so when I do eventually upgrade I won't need a new one. When I activated it I asked about the lte issue and they basically said everything was fine on their end and they can't guarantee something unofficial will work and didn't really want to help me further
[Galaxy Note 3 Android Development] iesous-kurios:
I think your twrp recovery might be too old. Try downloading twrp 3.0 or higher and flashing that image via twrp, rebooting into updated recovery and flashing again.
[Galaxy Note 3 Android Development] o_deacon:
The same problem.

---------- Post added at 10:16 PM ---------- Previous post was at 09:57 PM ----------

ok. I figured it out
[Galaxy Note 3 Android Development] retrobits:
thanks

Just wanted to thank you for the awesome rom. So glad to run Oreo on my good old Note 3.

I tried Lineage Nougat and my mobile connection kept randomly (silently) disconnecting, missed calls etc.

Flashed latest TWRP through odin, booted to recovery, wiped everything except ext storage, installed this.

No problems at all so far. Mobile and wifi connections are solid and switch quickly.

Bluetooth media audio works amazing. I've never seen my Note 3 perform better in my car (stock rom or otherwise).
[Galaxy Note 3 Android Development] iesous-kurios:
Awesome, that's great to know, I'm glad it's working well for you.

I think I'll be able to upload a new build before Monday.
[Galaxy Note 3 Android Development] milladog:
Sounds great I can't wait for the update....let us know. Ty
[Galaxy Note 3 Android Development] milladog:
Help I have the same issue error 7. N900V here.....was on 14 lineage but cell service was terrible. So I followed directions but must be missing something here. I have no cell until I can get some help here. ty Edit: Needed the newest twrp not even 3.0.2.0 could install this. All good now...ty
[Galaxy Note 3 Android Development] o_deacon:
Try twrp-3.2.3-0-htl.img.tar
[Galaxy Note 3 Android Development] iesous-kurios:
Latest build up.
[Galaxy Note 3 Android Development] milladog:
What are the changes in the new build? Thanks I just flashed your last build and it runs great!
[Galaxy Note 3 Android Development] iesous-kurios:
Change log since last build:

sepolicy: public: add TCSETSF to the list of unprivileged TTY ioctls

2018-10-08 18:20 UTC (android_system_sepolicy)

Screenshot: Append app name after screenshot date.

2018-10-08 18:18 UTC (android_frameworks_base)

mm-qcamerad: move move snap_app:fd use perms to common

2018-10-07 23:28 UTC (android_device_qcom_sepolicy)

move snap_app type definition to public

2018-10-07 23:28 UTC (android_device_lineage_sepolicy)

Update arm/arm64 webviews Chromium 69.0.3497.109

2018-10-07 22:19 UTC (android_external_chromium-webview)

Settings: fix apn_editor carrier_enabled summaryOff string

2018-10-07 14:58 UTC (android_packages_apps_Settings)

Messaging: Fix crash of blocked participant list activity

2018-10-07 14:40 UTC (android_packages_apps_Messaging)

manifest: android-8.1.0_r46 -> android-8.1.0_r47

2018-10-06 17:48 UTC (android)

sepolicy: Reflect the fact that Snap has now a defined domain

2018-10-06 11:47 UTC (android_device_qcom_sepolicy)

Should be able to wipe cache and dalvik and dirty flash with no problems.

I typically do full wipes anyway weekly when trying out my new builds.
[Galaxy Note 3 Android Development] hakcenter:
Any ideas if volte is a possibility at all ?
[Galaxy Note 3 Android Development] iesous-kurios:
I'm able to use data while on voice calls, so I think so. Maybe it depends on your carrier?

I'm on T-Mobile
[Galaxy Note 3 Android Development] Bruce lee roy:
It may also depend on modem version.
[Galaxy Note 3 Android Development] Bruce lee roy:
Than you for an awesome experience, I'm really enjoying this ROM. It's light, fast, and dependable.
[Galaxy Note 3 Android Development] iesous-kurios:
New build up, will supply change log later.

Lineage is starting nightly builds for 15.1 so I will likely have more frequent builds up.

Still working on getting Bluetooth calling to work
[Galaxy Note 3 Android Development] milladog:
Sweet! Thanks for the new build.....keep up the updates we appreciate it.
[Galaxy Note 3 Android Development] iesous-kurios:
With RIL now working on Lineage 16.0, I will be switching to Lineage 16.0 as my daily driver. I will continue to issue at least one Lineage 15.1 build per week though as long as all of you are still using it and would like it. I am still trying to help figure out the bluetooth calling. I am working on this for the Lineage 15.1 ROM, then if/when it is working on Lineage 15.1 I will see how that affects bluetooth calling on 16.0

Since it won't be my daily driver anymore, I'll need some help from all of you to know if there are odd bugs in the Lineage 15.1 builds I provide.
[Galaxy Note 3 Android Development] iesous-kurios:
I might stick with my ROM as my daily driver. Having troubles connecting my gear s2 on the pie ROMs.
[Galaxy Note 3 Android Development] iesous-kurios:
New build, 11/21/2018 is up. Improved wifi and mobile data stability. Been experimenting with incorporating parts of the working bluetooth files from Lineage 14.1 but won't push those experiments to you until they actually make the bluetooth calls work.

Majority of changelog is just bringing the system up to date with security patches.
[Galaxy Note 3 Android Development] Therac25:
Ill try this it out, I was having issues with network not reconnecting after going into buildings where the signal dropped. Hopefully that is fixed now.
[Galaxy Note 3 Android Development] iesous-kurios:
Another option you may want to try out with this particular problem is turning off the "automatically search for network" feature, and making sure "keep data connection active" is turned off.

Steps for turning 'search for network' off:

Settings

Network & Internet

Mobile Network

Advanced

Then make sure the slider is to the left under "Automatically select Network"

This will begin a search for networks in your area, once the list pops up select your network and it should default to that network instead of searching for others when your signal is down. (This also helps with battery life)

Steps for 'data always active'

Enable developer mode (I'm pretty sure you know how to do this if you have rooted your phone and installed custom ROM)

In developer options, scroll down to "Mobile data always active" and make sure the slider is all the way to the left to turn off.

I have T-Mobile, and my cell reception is horrible at work and in my home (I live in the basement level). I was constantly having to restart my phone to get it to connect to network again, but on these recent builds, following the steps I just provided, I have been able to go into an area with poor network, then come back outside and the data connection would come alive without having to restart my phone.

You may get notifications that your selected network is unavailable, but to me that is better than it trying to search and connect to other networks while draining my battery.
[Galaxy Note 3 Android Development] Therac25:
appreciate the tips (and the rom), im on t-mobile as well and i work in what amounts to a metal lined building in an area with poor coverage

ill be able to test it out in a few days
[Galaxy Note 3 Android Development] bharganwar:
Dirty flashed 04/12 over Edricchan's 13/10 build without any issue so far on hltetmo. Thanks for making weekly builds.
[Galaxy Note 3 Android Development] Therac25:
same thing happened again

I get a notification that selected network is unavailable, then when I go into settings and hit network select it immediately gives a toast with the text "Error while searching for networks."

and phone need reboot to recover from this
[Galaxy Note 3 Android Development] iesous-kurios:
I would do the manual switch to network while outside, then once on the network you chose, leave it there. When you're in an area with no reception you will get the notification that no network is available. This is normal, and if annoying you can have it hidden by long pressing on it and selecting from the options there.

No need to try to manually select network again when you are in bad or no network range, as you noticed, it will freak out.

As you can see from my screen shot, I have no network, and I've hidden the notification. When I go outside the network kicks back on.
[Galaxy Note 3 Android Development] Therac25:
yeah but the problem is that it doesn't ever find the network again till phone is rebooted
[Galaxy Note 3 Android Development] iesous-kurios:
Sorry to hear, I can't seem to recreate that problem with my device.

I went to place with good cell signal, manually selected network, then left it like that. I go in and out of no-cell areas daily and my network kicks back in when I'm outside again.
[Galaxy Note 3 Android Development] iesous-kurios:
New builds up for all variants.
[Galaxy Note 3 Android Development] chris rock:
Works like a Charme. :good::laugh:
[Galaxy Note 3 Android Development] NA5I7HAH2:
how did you connect this ROM to your gear s2?
[Galaxy Note 3 Android Development] Therac25:
yeah i dunno whats wrong with my phone, im on stock rom now with idle kernel and it reboots when signal is lost

might just be time for a new device
[Galaxy Note 3 Android Development] iesous-kurios:
https://xdaforums.com/android/software-hacking/mod-samsung-gear-app-android-n-samsung-t3547035

Download all the samsung gear s2 apps on the thread in the link above. Then before installing them, use root browser (or any other file explorer with root access) to change two appearances of "samsung" in your build.prop file to "htc". (navigate to /system and open build.prop file with text editor)

Change:

ro.product.brand: samsung

to

ro.product.brand: htc

and change:

ro.product.manufacturer: samsung

to

ro.product.manufacturer: htc

Then restart the device, install the apps, run samsung gear manager and it should begin the process of connecting to your phone.

You'll have to click on "mine's not listed" when it asks for which watch you have, then it will scan for near by devices. Make sure your watch is on and charged and in the mode for connecting to new device.
[Galaxy Note 3 Android Development] JJEgan:
Nandroid and try battery is down to you not the rom .
[Galaxy Note 3 Android Development] iesous-kurios:
New builds up for all variants.

Merry Christmas everybody!
[Galaxy Note 3 Android Development] iesous-kurios:
Changelog since last build:

ext4: always verify the magic number in xattr blocks

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237306

ext4: add corruption check in ext4_xattr_set_entry()

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237305

ext4: fix check to prevent initializing reserved inodes

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237304

ext4: only look at the bg_flags field if it is valid

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237303

ext4: Calculate and verify checksums of extended attribute blocks

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237302

ext4: calculate and verify checksums for inode bitmaps

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237301

ext4: calculate and verify inode checksums

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237300

ext4: calculate and verify superblock checksum

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237299

ext4: load the crc32c driver if necessary

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237298

ext4: change on-disk layout to support extended metadata checksumming

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237297

jbd2: don't mark block as modified if the handle is out of credits

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237296

ext4: add more inode number paranoia checks

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237295

ion: invalidate the pool pointers after free

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237294

netfilter: ebtables: fix erroneous reject of last rule

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237293

ANDROID: sdcardfs: Add option to not link obb

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237282

ANDROID: sdcardfs: Add sandbox

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237281

exec: Limit arg stack to at most 75% of _STK_LIM

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237280

net: Set sk_prot_creator when cloning sockets to the right proto

https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8974/+/237279

Revert "power: qpnp-charger: Reduce target charger voltage to 4.39V"

https://review.lineageos.org/c/LineageOS/android_kernel_oppo_msm8974/+/237013

Messaging: Fix crash when trying to view a vcf file

https://review.lineageos.org/c/LineageOS/android_packages_apps_Messaging/+/237255

ext4_utils: disable ext4 64bit block support

https://review.lineageos.org/c/LineageOS/android_system_extras/+/236684

Changing SUPL_ES=1 for SUPL end point control

https://review.lineageos.org/c/LineageOS/android_device_samsung_msm8974-common/+/235989
[Galaxy Note 3 Android Development] chris rock:
Flashed without issues!

Hlte...

Thank you!
[Galaxy Note 3 Android Development] iesous-kurios:
Whenever people stop downloading them :)
[Galaxy Note 3 Android Development] Bobanovicz:
May I ask you, if is any chance to fix the bt call issue in the future or is it a permanent yet?
[Galaxy Note 3 Android Development] cssr:
It is being worked on, no answer yet.
[Galaxy Note 3 Android Development] Bobanovicz:
Yes I know it. My question was for developer.
[Galaxy Note 3 Android Development] JJEgan:
Ongoing thread in development re. BT
[Galaxy Note 3 Android Development] JJEgan:
Four mirrors found now.
[Galaxy Note 3 Android Development] iesous-kurios:
Which variant?
[Galaxy Note 3 Android Development] zmx01403137:
lineage-15.1-20181228-UNOFFICIAL-hltechn has screen flicker and flash issue while using Adaptive brightness with 0% Brightness level, the issue will be gone if disable Adaptive brightness.

In actually, lineage-15.1-20181213-UNOFFICIAL-hltechn also has similar issue, but not so serious.

Another issue is the Map Navigating. The navigation is not working at all, for example, using BaiduMap or com.autonavi.minimap. However, GPS Positioning is working, but always without good signal like official ROM build. I try to disable battery saving feature, but nothing changed.
[Galaxy Note 3 Android Development] iesous-kurios:
Yeah, I should be able to do that.
[Galaxy Note 3 Android Development] Medyredy:
I'm using edricchans build.. and I want to test these build.. can I just dirty flash?
[Galaxy Note 3 Android Development] chris rock:
Yes, I did for hlte.

No issues.
[Galaxy Note 3 Android Development] iesous-kurios:
Here you go:

LineageOS 14.1 [UNOFFICIAL]

Make sure you download the appropriate google apps for Google Play functionality.
[Galaxy Note 3 Android Development] jerryspring:
Reflash twrp

---------- Post added at 02:35 PM ---------- Previous post was at 02:32 PM ----------

Yes... please verify..you need twrp for hlte

---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------

Mine does that too. Also have 900t
[Galaxy Note 3 Android Development] iesous-kurios:
I see a few people have browsed the rest of my uploaded files, which is fine, that's what they're for, but one warning:

Don't try to flash my Lineage 16.0 hltetmo ROM dated January 7th. Successfully built but I couldn't finish booting on that build. I'm currently using the January 8th build as my daily driver. It's not 100 percent lineage, I borrowed some msm8974-common code from Furkan(fessmm on git). The file size is a lot larger than the haggertk builds, so that's why I haven't made a post talking about the build and attempting sharing it with anybody yet. I'm still learning how to properly use git and make/commit changes to code so that's why I wanted to get in with the Pie development to see if I could get a build for the hltetmo up and running.

As stated before, I'll still keep building these 14.1 ROMs until people stop downloading them :)

There have been a few updates to Lineage14.1 that affects our devices since my last builds so I'll do new builds here pretty soon :)

*edit*

Upon closer inspection, my ROM is about same size as haggertk ROM, but they are both larger than lineage 15.1, so perhaps I don't have a problem with too big a file size.

I will try building again Tonight with lineage os msm8974 source code and hopefully it is successful and let's me boot.
[Galaxy Note 3 Android Development] iesous-kurios:
*deleted*
[Galaxy Note 3 Android Development] Medyredy:
Is there a way to rename your thread to add your username at the end..all these build have the same name..lol it's confusing..
[Galaxy Note 3 Android Development] iesous-kurios:
I can try changing it up to make it stand out some. Just trying to meet the xda standards for threads.
[Galaxy Note 3 Android Development] iesous-kurios:
Is that better?
[Galaxy Note 3 Android Development] zmx01403137:
Thanks a lot, Jfuginay. I tried to modify gps.conf to the one you provided, and reboot the system once, but still have the same issue, not sure what's wrong.
[Galaxy Note 3 Android Development] Medyredy:
Oh thanks! yesss!!!! Lol.

---------- Post added at 04:27 PM ---------- Previous post was at 04:23 PM ----------

Jfuginay..I'm using your latest build, without any external customizations on my HLTE. I realized that I can't turn off the WIFI.. anyone seen this as well..
[Galaxy Note 3 Android Development] iesous-kurios:
Making new builds tonight, got some tips from jprimero and will be using some code haggertk made so next build should be better
[Galaxy Note 3 Android Development] lemonmkw:
I'm sure you're aware but adaptive brightness isn't working on the latest lineage 16 build. Its the same with haggertks build
[Galaxy Note 3 Android Development] iesous-kurios:
Seems to be working on my latest build. Just uploaded new build this morning.

At least the option to enable it is working, will need more testing to see if it's actually adjusting brightness

Edit: just moved my phone under lamp, it got brighter, then darker when I took phone out from under the lamp
[Galaxy Note 3 Android Development] iesous-kurios:
New 15.1 builds up for all variants.