yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] tliebeck:
Yes, did see that airplane mode toggle cured it as well. For me it happens so frequently though that I'll lose data constantly. I think changing towers might do it as well.
[Galaxy Note 3 Android Development] alexp1289:
Hmm it's only happened to me like half a dozen times maybe less.
[Galaxy Note 3 Android Development] tliebeck:
Are you using Verizon as your carrier or T-Mobile?

I have a few known dead zones for T-Mobile where I regularly drive (hilly areas), so it's more frequent for me. I'm not certain if changing cells does it, but it does happen every time I get a momentary lapse of service.

At least testing it here is straightforwards as there's a corner in my house that has zero signal. Currently building a version that initializes as T-Mobile even if an N900V is detected at boot. Not my area of expertise though.
[Galaxy Note 3 Android Development] al.islam.333:
the sound is very low ??? any idea
[Galaxy Note 3 Android Development] alexp1289:
Verizon
[Galaxy Note 3 Android Development] demetrios3:
I flashed and reflashed the latest update, July 17.

i keep getting this Google Play Services error and the play store isn't installed.
[Galaxy Note 3 Android Development] djlan:
Weird. I tried the official build 7/19... But no luck. Clean flashed and all.
[Galaxy Note 3 Android Development] vidwhal:
This fix was merged with the lineage device tree repo so any build after that point should include the fix. :good:
[Galaxy Note 3 Android Development] djlan:
Figured it out. All good. 7/19 installed and testing.
[Galaxy Note 3 Android Development] -ION-:
https://github.com/LineageOS/android_vendor_cm/blob/cm-14.1/prebuilt/common/etc/apns-conf.xml
[Galaxy Note 3 Android Development] szotaa:
Sim card not detected on clean-flashed N9005 with 07/19 official nightly( + Supersu and Opengapps nano ARM) . Everything works fine on 07/13 unofficial build. I know that this bug has been already reported like million times but it's weird since I'm running the latest available modem according to the Samsung phone info app from play store. ( N9005XXUBGOJ1 )
[Galaxy Note 3 Android Development] GerardSamija:
I was having a couple of glitches with the 07/18 test build (could not connect to camera suddenly after a few days working fine, keyboard stopped working so all I had left was voice input), so last night I wiped and clean flashed the 07/19 nightly and GApps 07/22 Full. So far smooth like butter, zero connectivity problems. Flashed SR1-SuperSU-v2.82-SR1-20170608224931.zip separately and my N900W8 rooted without issue. So far a few minor hiccups in settings. Minor stuff. I can't seem to get rid of the protected apps lock icons and occasional pop-up about that though I don't want it and have tried turning it off. But that's trivial, probably things I can work around. After installing 89 apps and setting up most of them along with various accounts there are no serious issues, no fixes needed to connect SIM to Freedom Mobile. Wi-Fi still needs a poke or two for initial connects, but stays connected perfectly once established, even for 600MB+ downloads or streaming YouTube. Using latest baseband for my model, which flashed first try thanks to reading about pulling the battery etc.
[Galaxy Note 3 Android Development] alexp1289:
Oh that's really cool so lineage supports all those networks as long as you're smart phones radio is compatible with it? I didn't know there were so many Networks supported by hltetmo lineage I thought they had to be added to specific phones specifically. But now it looks like all of those are pre built into the ROM? If I understand that correctly.

This is absolutely what I love about the open-source software side of computing. Things like lineage make this possible. Everybody wants a pixel phone but here we are with the exact same experience and we don't have to worry about ripping our phones open if the battery craps out. I've always said there's nothing wrong with the hardware on this phone it's just the lack of software support but now that's not even an issue :)
[Galaxy Note 3 Android Development] alexp1289:
[MENTION=2693412]haggertk[/MENTION] I've got two more logs for you that may help solve the issue relating to the select sim card pop up. I've been able to reproduce the issue on my sm-n900v while being in Walmart which has no network access for me while shopping. I've gotten it to pop up like a dozen times in fifteen minutes and took two logs for you if you're interested. Just an FYI I had WiFi turned on so I could get Walmart's WiFi to post these logs for you. I'm not sure if that's information you needed to know but none the less I figured you might need to know.

https://drive.google.com/file/d/0B83noRHOimrRMVVuRUJZSG96cTg/view?usp=drivesdk

https://drive.google.com/file/d/0B83noRHOimrRVGh2YnAwVGtVakU/view?usp=drivesdk
[Galaxy Note 3 Android Development] Keinbockwurst:
Try N9005XXUGBGP1 instead. That one is working for me.
[Galaxy Note 3 Android Development] R3s1du3:
Synergy not working for me since 6/27 build I've been dirty since the beginning of official just boot loops from logo
[Galaxy Note 3 Android Development] djouija:
Hey there, I was in a similar boat tonight when trying to install on my wife's sm-n900w8 with Rogers, where I found out that I was having issues using the hlte version on her device and the sim card not being detected; When I wiped and reflashed with the official hltetmo version instead (lineage-14.1-20170719-nightly-hltetmo-signed.zip), the sim card was then detected :good:

Note I was on TWRP 3.0.2.1 when flashing (and I actually installed the twrp-3.0.2-1-hlte.img.tar via ODIN, *not* the hltetmo version), and I did a complete wipe of the phone prior to flashing, and installed opengapps 7.1 arm nano as well.

Hope this helps!
[Galaxy Note 3 Android Development] soasa:
Hi all, I've modified gps.conf in according to some guides, but nothing, my GPS still doesn't work. I don't know what to do with this problem. I've LineageOS ROM and (i don't know if it is helpfull) i'm from Italy. I've also insalled those files : CP_N9005XXUGBOJ1, BL_N9005XXSGBPL6. Is there anyone who has had my same problem and fixed it?
[Galaxy Note 3 Android Development] djlan:
Thanks. I got it figured out. Working good now.
[Galaxy Note 3 Android Development] Duron23:
Where to find this one ? Tried searching all over the net, didn't find it.

Can you please help.
[Galaxy Note 3 Android Development] shaggyskunk:
You should only Flash the Bootloader and Modem for your Device and Carrier - Go to sammobile.com and search for your Device and Carrier - Download the latest Firmware for your device and Carrier to your computer and Read the Instructions - Backup whatever you want and need to your computer - Flash the Full Firmware (or extract the Bootloader and Modem tar files) Flash with Odin 3.12.3. Google how to Flash Firmware with Odin if you're not sure.

From Down the Rabbit Hole by:

My SM-G930W8 ??
[Galaxy Note 3 Android Development] MuVic:
Hi, I have a n900p I was using hlte 20170627 build but after upgrading to 20170719 sim card was not detected I read some posts that says I should update my baseband so I updated through a androidfilehost link by [MENTION=2693412]haggertk[/MENTION] and updating baseband was totally successful now my baseband is N900PVPSEPL1 but even after that sim card is still not detected what I'm I missing here

any help would be highly appreciated
[Galaxy Note 3 Android Development] Duron23:
Thanks for trying to help me here. But I have already downloaded and installed latest firmware for my phone, still having sim not found issue with 12th and 19th update.

I am using International version SM-N9005
[Galaxy Note 3 Android Development] shaggyskunk:
Thanks - Perhaps I should have looked at your Profile before I posted my "advice" - Apologies if I appeared to assume that you were new to Android ?

From Down the Rabbit Hole by:

My SM-G930W8 ??
[Galaxy Note 3 Android Development] bladebarrier:
Ok, so far everything is working absolutely perfectly for this ROM, except one odd thing.

Nova Launcher Prime lets me select what long pressing the menu button will do (open my non-stock camera app), but it refuses to do so. It defaults to what is in the phone settings, and I don't see a way to change that to a 3rd party app, so I just have it set to the stock camera for that.

No, it's not a deal breaker in any way. This ROM is outstanding, and is now my daily driver. I was just curious if anyone else had this issue.

I enabled all of the permissions, including change system settings, but no luck. It just seems to refuse to override it.

Any suggestions, or is that just something that Android 7 locks down?
[Galaxy Note 3 Android Development] GerardSamija:
I've been able to map button functions to Open Camera in a couple of Nougat versions, RR if memory serves, but not in this series. So I'm using the lockscreen shortcuts workaround. Going into Settings > Security > Screen Lock ( I just use swipe) then screen lock settings > Lock screen shortcuts, I choose Open Camera (and Hi-Q MP3 recorder for the other one). Then if I want the camera with the phone off it's just a swipe-up on the camera. And if the phone is on, just shut it off then do the same after turning it on again. Not ideal, but some of the other button settings are useful at least. Press and hold power for flashlight is nice.
[Galaxy Note 3 Android Development] bladebarrier:
That workaround was perfect! I honestly never liked using the menu key for it anyways, because I would sometimes launch the camera by accident, so this is a great method for my needs.
[Galaxy Note 3 Android Development] StoneToken:
Hello, guys!

This is my second post in thread, hope someone takes a look at it...

Does anybody else have following issues on latest official LA14.1 (no custom kernels):

1. Proximity sensor not working at all

2. Rotation sometimes gets buggy, rotates to landscape and stays like that for 10-20 sec.

3. Screen doesn't turn on. Sometimes it takes 10-20 sec for screen to turn on, hardware buutons work, touchscreen doesn't.

And I would really like to understand, why GPS isn't working and I have to manually uncomment lines in gps.conf. Dear maintainers, may be you can shed some light?
[Galaxy Note 3 Android Development] Suppenhuhn:
Agree with point 2

GPS has to be configured once (GPS.conf) according to your position.

For further information search the thread.
[Galaxy Note 3 Android Development] bladebarrier:
I use GPS locker, and it seems to work really well. I have it start on boot, set the permissions up for it, and it fires up and turns off, on demand.

It also has a bunch of other features to fix various issues, depending on location. I can't say it will solve it for everyone, but it works perfectly for me. GPS is as good as stock, or maybe even better (subjective).

I also have GPS status turn on simultaneously, with GPS locker, and they both turn off when I disable GPS, but turn on when I engage it. Both get great locks, which other N ROMS did not do properly.

But yeah, the rotation can get weird for certain apps. I have only experienced it in camera apps, and such, but if I close them it fixes itself. Not a big deal for me, but maybe the app over-riding the permissions or something.
[Galaxy Note 3 Android Development] GerardSamija:
None of the other issues, but I do get buggy rotation with both the 07/18 test build and 07/19 nightly. Just a few times on my N900W8, where rotation seems to lock to portrait or landscape, then after a while flip the opposite way or some random direction. After less than a minute it's working fine again. Screen wake sometimes takes as long as 6 seconds or so but I chalk that up to running something memory-intensive in the foreground, as it doesn't happen with lightweight applications in the foreground. My GPS is working fine, even in the house not very close to a window. Worked fine this morning while navigating public transit a few times, locking within 1/4 block or so within less than 10 seconds. Never tweaked GPS for any reason, no need with this one either. I've read comments in a few places on XDA that screws sometimes need tightening near the GPS antenna, but don't know anything about that besides running across such comments in other threads.
[Galaxy Note 3 Android Development] alexp1289:
Did you dirty flash the lastest update? I clean flashed the update and have no issues besides a pop up that says select sim card it's just annoying but doesn't really cause any issues.
[Galaxy Note 3 Android Development] haggertk:
I haven't merged 900P compatibility into the hlte build yet because I didn't have a tester. I'll whip up a test build after work, if you don't mind testing (data wipe will be required due to signing keys - you can TWRP backup/restore). If that tests good then I can get it merged into this week's official.
[Galaxy Note 3 Android Development] MuVic:
Okay, I will test it, thanks
[Galaxy Note 3 Android Development] haggertk:
If you don't mind, give this a test:

https://www.androidfilehost.com/?fid=745425885120751201

Make sure you are using TWRP 3.1.0 or 3.1.1 and you will have to wipe data/factory reset. As I mentioned before, you can TWRP backup before the test and restore after. Assuming that you get radio connectivity, give calls, SMS, data, etc all a test.

Thanks!
[Galaxy Note 3 Android Development] djlan:
I'm experiencing #1. When talking one the phone the screen does not turn off. I have to press the power button to avoid cheek pressing something while on a call.
[Galaxy Note 3 Android Development] GerardSamija:
Sorry if I'm being a bit slow, but... When I go to here https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html I see that TWRP 3.1.1-0 is available. Then I click the Devices link here - https://twrp.me/Devices/ - and enter Note 3, and click hltexx from the results taking me here - https://twrp.me/devices/samsunggalaxynote3neo.html- then the download link, and the next page offers only version 2.6 on the phone browser, version 2.87 on the PC. https://dl.twrp.me/twrpapp/me.twrp.twrpapp-26.apk.html

Someone offered a link to v3.02 a couple of weeks ago and that's been working nicely for me, but I would like to have the latest TWRP. Why is it so difficult (impossible?) to get that? Or am I visiting the wrong official TWRP site somehow?

Edit: perhaps I've been been trying for the wrong version? Is the hlte version fine for a Canadian Note 3 version N900W8? I've only dared try the hltexx versions of TWRP.
[Galaxy Note 3 Android Development] haggertk:
https://twrp.me/devices/samsunggalaxynote3qualcomm.html
[Galaxy Note 3 Android Development] GerardSamija:
Ah I see, so hlte is fine then. Thank you, grabbed a copy and will Odin flash this evening.
[Galaxy Note 3 Android Development] MuVic:
i've tested it, and everything is working perfectly.

thank you so much for adding support for the n900p.
[Galaxy Note 3 Android Development] asusgarb:
I have an extremely low sound during call. Both in receiving and making calls, the other person's voice is extremely low. Often, with even a little noise, I can't hear him. How can I increase volume?
[Galaxy Note 3 Android Development] odoll:
+1 - noticed it first since 7/19

And it seems I'm the only one having this Bluetooth AVRCP (*) skip / stop / etc. issues since on the official releases?!

(*) The Audio/Video Remote Control Profile is a Bluetooth profile that allows Bluetooth devices to control media playback on remote devices. It is typically used with A2DP devices for next/previous track selection and pause/play functions. Also known as: "Audio/Video Remote Control Profile"
[Galaxy Note 3 Android Development] haggertk:
N900P support will start in the hlte official builds that are set to pop out later today.

All hlte build users:

Make sure that your recovery is updated, I recommend TWRP 3.1.0 or 3.1.1, else the update will exit with an error. If you run into this situation, update your recovery and re-flash the build -- your data is not corrupted.
[Galaxy Note 3 Android Development] NeWONEx:
Last build has issue with VPN . It connected and only upload works, download goes and back.
[Galaxy Note 3 Android Development] action_papst:
Using a VPN right now. No problems like this. Also no problems with rotation, gyro or proximity sensor.

2 soft reboots within the last few days (no logs), everything else is working as intended.
[Galaxy Note 3 Android Development] StoneToken:
I can confirm on latest build VPN works OK.
[Galaxy Note 3 Android Development] NeWONEx:
I don't know why this happened to me, will try to do clean flash . I tried many other apps and they give me the same result works fine for mins after that as i said no download only upload.
[Galaxy Note 3 Android Development] StoneToken:
Everybody, thanks for your replies. I fixed GPS (by going back to stock and reinstalling recovery and LA; seems like it was some left over from RR rom) and proximity sensor (cleared view port following this advice https://www.youtube.com/watch?v=4-xX2XYipso). Still got some soft resets and rotation gets weird, especially in Google Maps.
[Galaxy Note 3 Android Development] :
Hi All, I've just updated to the latest build 20170725. The issue with the SD Card not showing/recognised still exists. I've searched but no solution found. I believe there is an issue with the roms since the build 20170627, because everything worked fine on that build. Just recovered my backup to build 20170627 all back to normal again.

Anyone have the same issue or has any idea how to resolve this. I would appreciate the help. Thank you.
[Galaxy Note 3 Android Development] deifos:
i have the same issue with build 20170725. In the last build 20170719 all work perfect.

Enviado desde mi hlte mediante Tapatalk
[Galaxy Note 3 Android Development] GerardSamija:
I was having this problem a couple of builds ago, on the 07/18 test build. ulats07 offered a solution using a simple command in a terminal, which I then enabled following his instructions. Worked, as I reported in this post:

https://xdaforums.com/showpost.php?p=73103291&postcount=4393

There were a couple of 'stubborn' apps like Moon+ Reader and one or two others which either refused to see the MicroSD or saw it only partially, and even from the PC I initially had trouble as it displayed only one file and one folder... but these seemed to sort themselves out after I granted deeper permissions to the problematic apps and then the PC started recognising the card just fine as well, for unknown reasons. I've been on 07/19 for a few days after wiping everything but my personal files, had to set up all my apps and preferences from scratch, and the MicroSD problem remains fixed. Flashing 07/25 now... which is taking a VERY long time, kind of surprisingly long, so we'll see if anything glitches with this one. I'll report back if there are problems related to card reading or anything else. 07/19 was working so close to perfectly that I'll probably notice quickly if anything has become worse with 07/25.
[Galaxy Note 3 Android Development] :
I've switched on - local terminal from developer option.

I've no idea how to do the rest though - su and sm set-force-adoptable true.

Sorry but my experience lets me down here.

Update.

SORRY, I've managed to figure it out. I found the Terminal in the Apps Drawer, entered the information and it all looks good now. [MENTION=462516]GerardSamija[/MENTION] and [MENTION=5043818]ulats07[/MENTION], thank you both very, very much. Everything is working correctly again. Great.
[Galaxy Note 3 Android Development] shaggyskunk:
Absolutely the hlte version of TWRP 3.1.1-0 is fine to Flash Roms - The only issue that I have is Nandroid backup to the internal sd card seem to stop at around 40 - 50 Meg (in other words - useless) However Nandroid backups to the external sd card are fine.

When I want to backup to the internal sd card I just Flash TWRP 3.0.2-0 hlte and it's fine.

From Down the Rabbit Hole by:

My SM-G930W8 ??
[Galaxy Note 3 Android Development] GerardSamija:
Well, I tried several times using TWRP 3.1.1-0 (hlte version) to flash the 07/25 nightly build, but it kept hanging at the line "patching system image unconditionally" with just a tiny triangle in the bottom-right corner of the progress bar not blue. Left it half an hour the last time, but no progress. After doing some searching I determined that it's possibly a filesystem type error - mine's on Ext4 and apparently f2fs is preferable/possible, but perhaps not possible with this latest.

So I re-flashed back to 07/19 after yet another cache/Dalvik wipe, booted fine, and found that Google Services were not installed. Got a persistent pop-up declaring that I needed to install the latest TWRP app, which when clicked took me to a placeholder (it said they needed to keep things small in the package, so just providing links) with two buttons, one to the website, one to the Play Store. Play store button just blinked, owing to Google Services not being installed. Website showed me links to ancient TWRP versions.

So apparently GApps was wiped, though it was a dirty flash (except for cache/Dalvik wipes), so I flashed GApps again. After that was done I was able to get the latest TWRP from the Play Store. A bunch of my shortcuts were gone from their folders on the desktop, so have to get those all pushed back into place. Email and other settings are all apparently working fine, but the device was no longer rooted. So I went into recovery yet again and flashed SuperSU. That worked again, so I was able to get Adaway running again (basic survival tool - ads drive me nuts, always hated them, even as a child on TV or in comic books) and various other stuff which requires root. Seems I have to grant permissions all over to a bunch of things. Ho hum, more time wasted on setting things up... I really thought that since I didn't wipe system or files or data that my own data and settings would be completely intact. Silly me. And of course backups still don't work for me in TWRP so no simple restore possible, just a few hours more time wasted on doing the same things over again.
[Galaxy Note 3 Android Development] Gazzasore:
Flashed 25/7

Everything went smoothly

ROM seems all OK to me
[Galaxy Note 3 Android Development] GerardSamija:
Still working on reestablishing various logins and permissions... And just discovered the native clock won't launch. Same problem I had with 07/18 test version which, along with the keyboard vanishing a bit later, moved me to install 07/19. Same ROM re-flashed and same full GApps version, but now my clock is dead. Looks like I'm going to have to waste yet more time doing s full wipe and re-flash and setup routine. It's weird how much Google-related stuff is going wrong for me lately. And with them having removed the backup contacts option I don't find that inspiring much confidence. I mean it seems one could export contacts... But with 1345 in my contacts and a 1000 name limit on the export function now, it just doesn't work.

Edit: I found a replacement for the newly dysfunctional system clock, Alarm by DoubleTwist. Simple and effective, with a lovely nighttime analogue clock face via pull-up from the alarm set interface. I like. And it even remembered my favourite alarm sound from the system clock. Even going into Root > System > Apps and deleting the deskclock folder with the clock app inside, rebooting, then trying to install Google's clock again from the app store failed. Error -505 it said. Very weird.
[Galaxy Note 3 Android Development] ulats07:
u did dirty flash or clean flash from 19/7?
[Galaxy Note 3 Android Development] hamiltonbento:
With the rom lineage-14.1-20170712

When connecting the device to the charger

Gave the message: RAPID LOADING.

On the lock screen.

I updated to

Lineage-14.1-20170725

LOADING SLOWLY.

Does anyone know the reason for this?

And how to solve?
[Galaxy Note 3 Android Development] sarjen iceman:
Dirty flash latest build...so far everything ok

Default kernel, unrooted
[Galaxy Note 3 Android Development] Medyredy:
I have a hardware problem with my GPS..looks like under the hood the GPS pins aren't contacting with the back cover or something of that sort.
[Galaxy Note 3 Android Development] Gazzasore:
Clean from 19/7 yes

All this Chat about TWRP is unreal

I run 3.0.2.1 have been for a long time

Never have a problem