yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] Unidave199:
BT Calling no good.

Shane, Its a no-go for the BT calling on my Sprint Note 3. Still doing the same static. The only other thing I can mention is that I tried using the Google Voice calling and it simply cut the Bluetooth and just used the phone speaker.

Its great to see updated posts to this ROM. It was getting too quiet....
[Galaxy Note 3 Android Development] shane87:
[MENTION=3026895]DaOldMan[/MENTION] I think the logcats that I have are pointing me in the right direction. On the other hand, more logcats are better. I can look for points of commonality, and at differences as well.

[MENTION=5554693]Unidave199[/MENTION] thanks for the report, and the logcat. I'll look into it.

One thing interesting that I found digging in the Broadcom bt code is a build switch for a "Bluetooth manta bug." Manta was the codename for the Nexus10, which was built by Samsung. I'm not holding my breath, but who knows, maybe that switch can help. I'll test this weekend.
[Galaxy Note 3 Android Development] fad19:
https://www.bgr.in/news/lineageos-c...mail-app-enhancement-call-recording-and-more/

Are these features will be added to this rom?
[Galaxy Note 3 Android Development] shane87:
I know that at least one feature mentioned in that post has in fact already been added on my last AOKP build, SystemProfile QS Tile. As far as the others, I'll have to check our commits and see if they have been pulled over. Chances are that they will be, though an eta of when is, as always, not available.
[Galaxy Note 3 Android Development] DaOldMan:
BlueTooth Call Logs

Ok here we go [MENTION=3482571]shane87[/MENTION] :

1. Full wipe

2. Installed latest Oreo AOKP

3. Installed Magisk (to be sure I get root for logging, probably not needed)

4. Boot (yes no GAPPS)

5. I did logs from the main buffer and event buffer (although I think it's quite useless) while calling. I changed from Bluetooth to speakers in middle of call... and that works so RIL is fine. When I switch back to Bluetooth, static is back.

I hope those will help you with debugging this stubborn bug. I have more logs if needed. Now back to Nougat :( .....

P.S Maybe [MENTION=2693412]haggertk[/MENTION] can take a look at this as well, LOS has the same problem.....
[Galaxy Note 3 Android Development] Unidave199:
I would like to change the subject a little bit from Bluetooth to Air Command. Obviously this is a key feature of our beloved Note 3. I have been seeing a number of posts on XDA on how to install the air command ability on AOSP Roms, most notably a Note 5 port. I do not want to get in trouble for linking to another developer's work without proper credit so I will keep this discussion generic for now. There is an Aroma installer version that I tried to flash but it just freezes during the TWRP install, and there is a .apk version that you can install which works pretty well, but doesnt 'detect' the SPen being pulled out. Instead it just keeps a floating button up all the time for you to press. Obviously that isnt ideal, and would like to use the SPen removal to trigger the Air Command function but just cant seem to find a way to do this. Does AOKP even have a commit to detect the SPen being removed? Is there a way for it to alert in some way in the notifications? That way I can develop a Macrodroid response to open up the Air Command feature.

Any other thoughts on how to do this?

Dave
[Galaxy Note 3 Android Development] DaOldMan:
I am using a spencommand app. It works ok and does the job. I hope the dev will continue to develop it. Detection of spen removal works fine but needs a permissive kernel. Maybe that's the problem. The spen detection is kernels job anyway. The stock kernel has problems to detect spen insertion for me. The Xenial kernel has both the spen removal and insertion functionality.

Anyway I don't mind air command that much. For spen functionality I need the spen apps which can't be ported like Action memo (with screen off or on). Those give us the main spen functionality.

Send me the links in PM and I will check them out. No problem to install a zip without any twrp at all :)
[Galaxy Note 3 Android Development] shane87:
I am not sure if AOKP kernel (and LOS kernel, as they are one and the same) has spen removal/insertion detection. I have been looking over the Xenial kernel source, and can't find anything specific to the spen. As far as selinux being set enforcing as opposed to permissive, that can't be helped with the stock kernel. AOKP build scripts will not allow the kernel to build as permissive, due to security concerns. With that being said, I will look in to the selinux contexts and see if I can loosen the restrictions on spen, once I get something going on this Bluetooth bug.

Back to the Bluetooth bug, I am running a test build right now with a possible fix. It is something I came across while digging in the Broadcom Bluetooth HAL. Once the build is done, I will be pushing the build for testing purposes. I am only building hlte with the possible fix at this time, since the hlte builds have the most users. Once I have it done I will post requesting some tests, and depending on those results I will then move forward in debugging. Hopefully we can get this thing squashed.
[Galaxy Note 3 Android Development] shane87:
Bluetooth test build

Hey guys, I have a test build up that has a potential fix for the Bluetooth bug. If you guys could test it out and let me know what you find, I would greatly appreciate it. Hopefully its fixed, but who knows.

The download for the test build can be found

HERE
[Galaxy Note 3 Android Development] DaOldMan:
Hello [MENTION=3482571]shane87[/MENTION], sorry to inform you that when trying a BlueTooth call I hear the same static/noise just like before. If I switch the call to the loudspeaker all is fine and when I switch it back to BlueTooth static/noise is back.

Sorry to disapoint, keep them coming :D
[Galaxy Note 3 Android Development] MrMessi10:
The static also appears when using a headset... I have noticed this with several roms..
[Galaxy Note 3 Android Development] shane87:
I guess I'll have to keep digging! :D

Are you saying that the static is also present on a wired headset plugged in to the headphone jack? If so, can someone else confirm this? If that's the case, I may be looking in entirely the wrong place for this bug.
[Galaxy Note 3 Android Development] Iolar:
[MENTION=3482571]shane87[/MENTION], I regularly use wired headsets without any issues but any Bluetooth headset/speaker gives static when I try to call. I hope this clarifies any confusion :)
[Galaxy Note 3 Android Development] shane87:
Thanks for the clarification. Again, I can't test call audio on my test device since it has no active service. I'll keep digging with the Bluetooth stack.
[Galaxy Note 3 Android Development] joetiger:
is this rom good for daily use or its not stable yet??

---------- Post added at 05:33 AM ---------- Previous post was at 05:33 AM ----------

can i root this rom?? can anyone give me a link?
[Galaxy Note 3 Android Development] shane87:
Yes, this ROM is stable, and I am sure that it would make a good daily driver. However, Bluetooth Call Audio is still broken, so if you rely on Bluetooth to make phone calls, either via a BT headset or the BT functionality in your car, then this ROM is not right for you. I am working on the BT issue, but its a tricky bug to track.

This ROM is already rooted. That is why, in the OP, under Features, it says "SU baked in - No need for SuperSU/Magisk (Unless you want them!)." To enable root access, Settings -> System -> Developer Options -> Root access; selects Apps Only, ADB Only, or Apps and ADB.
[Galaxy Note 3 Android Development] shane87:
Bluetooth Issues

Hey guys, I am still looking in to the Bluetooth issues, and I think it may be something to do with the HFP (Hands Free Profile). HFP is used by both car BT systems and BT Headsets for voice transfer. BT Headsets also use HSP (HeadSet Profile), but cars do not. Anyway, I need to ask for more information. Specifically, I need you guys to capture a new set of logs for me. Not logcats, they have been basically useless, they just tell me there is a problem, which I already know. I need you guys to capture some HCI Snoop logs. System => Developer Options -> Enable Bluetooth HCI snoop log. Then make a call through your BT device. You should get a log on your sdcard. It should be /sdcard/btsnoop_hci.log Hopefully those logs will be able to point me in the right direction.
[Galaxy Note 3 Android Development] joetiger:
guys i have experienced a problem with this rom...the volume buttons doesn't play previous or next track on soundcloud while the screen is off.. it's only working with the main music player...and also the hardware keys don't illuminate and i checked the illuminate button but still the same...has anyone experienced these problems?
[Galaxy Note 3 Android Development] Unidave199:
I will be honored to help. I will set things up tonight and make a few calls. I will try both with my Jeep audio system and a Plaintronics Voyager Legend Pro.

Please let me know if there is any more info you need I will be happy to test away!

BTW. We chatted earlier about the SPEN functions... Here is something interesting. If the phone is set down, and the screen off, when I remove the SPEN the screen comes on. When I tap the SPEN and click on the button, my Media player starts!

Weird!!
[Galaxy Note 3 Android Development] shane87:
Using the volume buttons to control media playback may not work with some media sources. It's not a perfect setup. As far as the backlights, go to Settings -> System -> Buttons; there is an option to enable or disable the buttons. And I am talking about the buttons themselves, NOT the backlight. Disable the buttons, then enable them. That will fix the back light issue.

Yeah, I believe that one of the default spen gestures will allow you to launch the media player, but I don't remember. I know that, on Oreo, the s-pen gestures are enabled, but I can't find the option to change them. I can't remember where it's at, lol. I did find the place, or at least one of the places, where the s-pen info is populated: /sys/class/sec/sec_epen There are several objects in that folder, though which one might indicate spen removal/insertion I am not sure of. To be honest, I forget that the device has the s-pen lol.

I would greatly appreciate those hci logs. I was digging in los's Gerrit earlier and I came across a pending commit that I am thinking about testing out. It is a realign of the audio configs back to stock, plus mm enhancements. I wonder if that might fix the bt issue. The only problem is, according to comments on the commit, it breaks playback through the rear speaker. I might have to see what it does.
[Galaxy Note 3 Android Development] Eleo:
Check settings/about device/buttons/touchscreen gestures menu and disable spen button shortcuts. It may not be directly under "buttons" but it is somewhere there.
[Galaxy Note 3 Android Development] svbarbosa:
[MENTION=2473151]macs18max[/MENTION], would you be so kind to share with [MENTION=3482571]shane87[/MENTION] your findings that lead to fix the BT call issue. :o

This is a nightmare for all Note 3 AOSP Oreo rom users.
[Galaxy Note 3 Android Development] shane87:
I would definitely be interested in what [MENTION=2473151]macs18max[/MENTION] did to fix bt, although I am not sure how applicable it will be to hlte and variants, as this was for the S6, 2 generations newer, and, unless I am mistaken, it's for the exynos variants, not the Qualcomm. I would still be interested in seeing what he did though.
[Galaxy Note 3 Android Development] Unidave199:
[MENTION=3482571]shane87[/MENTION] Im not getting a hci.log generated. I have:

Enabled the snoop log in Developer Options

Made a phone call with my Plaintronices Legend Pro (static)

Looked on my SD card and even did a ESFile Explorer on my whole device which came up empty
[Galaxy Note 3 Android Development] svbarbosa:
I know, but this bluetooth call problem is present in so many phones after moving to Oreo that there is a good chance the fix is more related to Oreo itself. So checking how it was fixed in another phone, despite this phonr being Exynos based, may point you in the right direction.
[Galaxy Note 3 Android Development] jprimero15:
Goodluck.. I hope u find a way to fix it..
[Galaxy Note 3 Android Development] Buslova:
Maybe I misunderstood the other day while in another forum, [MENTION=2693412]haggertk[/MENTION] seemed to elude that the S5 might not have the dreaded BT bug since it is fully verified and supported for Lineage 15.1 however our beloved Note3 is still stuck on 14.1. Obviously from my previous wording, I'm not sure if it was in regards to BT or what was keeping Note3 from 15.1 certification but if it WAS due to the BT issue, it might be worth looking at the S5's roms if their BT is fully functional since the S5 and Note3 use almost the same hardware. Just a thought. I could be totally wrong.
[Galaxy Note 3 Android Development] DaOldMan:
Dear [MENTION=3482571]shane87[/MENTION] I took the logs. The log file was not located in /sdcard though, instead I found it in /data/misc/bluetooth/logs. It's filled with binary data so I hope it will be of any help. Thanks for all the hard work. Btw I called twice the number *058 as first time my call was immediately terminated....
[Galaxy Note 3 Android Development] shane87:
Thanks for the log. The log can be opened using a protocol analyzer, such as WireShark or FTE's BPA600 Dual Mode Bluetooth Analyzer. I'll look at it tomorrow, see if it shows anything odd.
[Galaxy Note 3 Android Development] DaOldMan:
Yeah I am looking at already in WireShark :). Looks like it has the info ! First time I see this kind of log. I hope you can find what's going on [MENTION=3482571]shane87[/MENTION] .

Dear [MENTION=3482571]shane87[/MENTION], here is the wireshark dissection export, hope this helps you some.
[Galaxy Note 3 Android Development] len207:
!Shane87 these are a couple logs from my n900p using DotOS 2.5. Hope they are helpful.
[Galaxy Note 3 Android Development] len207:
oday, 11:44 AM |#369

Senior Member267 posts Thanks: 64

Shane87 these are a couple logs from my n900p using DotOS 2.5. Hope they are helpful. (Second log)
[Galaxy Note 3 Android Development] shane87:
Alright guys, I am starting to dig in to these hci Snoop logs with WireShark. I want to first of all give a

HUGE

thanks to everyone that provided logs. I am still looking at the first one I opened. (I can't remember whose it was now, lol, they all had the same file name!) So far, I haven't seen any major problems in the log, but I also haven't decoded the packets yet, either. All of the voice transmission packets are encoded. There is a key that I can get from the log to allow me to decode them, but I am not 100% sure that WireShark has the feature of decoding bt packets. One thing that I have noticed is that the hci host interface starts a Bluetooth le advertisement to the controller (or maybe it's the other way round, the controller starts the advertisement to the host, I don't remember which lol), and the first two packets are always malformed. I don't think that has anything to do with this particular issue, but it could. Anyway, I am looking in to these, but it may take a while for me to find what I am looking for, it's a LOT of data! Again, a huge thanks to all who have provided logs!
[Galaxy Note 3 Android Development] chispas-elek:
Hello.

I have installed this ROM and it's very good, thanks for keeping it updated. I have noticed that hardware buttons behave strange. For example, I configured the menu button with : one press, for, Recent apps and long press for app settings.

When I push once the button, both actions are executed.

I have attached a log of this problem.

Thanks
[Galaxy Note 3 Android Development] Eleo:
Is there any other app that remaps buttons? E.g. if you are using a 3rd party app to remap it but there is also AOKP rom control that has a control on it, then that is an expected behavior. You need to adjust both properly.
[Galaxy Note 3 Android Development] YYCLeo:
Rom installs fine but i'm having issues with the Play store. It keeps crashing asking to close or re-open during the account setup. What am i doing wrong, can someone point me in the right direction?

TWRP 4.2.1-0

Tried both

open_gapps-arm-8.1-micro-20181007

open_gapps-arm-8.1-stock-20181007

am I installing the correct version of gapps?

Thanks in advance
[Galaxy Note 3 Android Development] Eleo:
No. You should install only micro or only nano gapps. Do not flash stock gapps. That is it. And there is no TWRP 4. You probably wanted to write TWRP 3.2.1-0
[Galaxy Note 3 Android Development] chispas-elek:
Hello [MENTION=4598795]Eleo[/MENTION].

Thanks for your reply. I have disabled all actions and you are right. There is something that is mapping the menu button. The problem is that I not sure what application is.

Regards.
[Galaxy Note 3 Android Development] shane87:
Yes I would definitely avoid stock gapps, they are just way too big. However, mini works great, as does micro and nano. Personally, I run mini, and always have. It's a great blend of not having to install a bunch of the apps from the play store, but also not filling up the system partition.
[Galaxy Note 3 Android Development] shane87:
I was just browsing your log. I saw the intent for the recent apps overview being called, but I didn't see any other intents being called. It is definitely strange. I was looking at your log on my phone, so I may be missing something. I'll take a look at it on my pc later, and see if I can dig anything up.
[Galaxy Note 3 Android Development] chispas-elek:
Hello.

Thanks for reviewing the log. If it helps here is my procedure when I installed the rom:

Flash ROM + Micro Gaps + Magisck (full wipe before install anything).

Recover settings using Google account (phone calls, SMS, settings, wifi passwords...)

Use Titanium to recover apps+data

Thanks.
[Galaxy Note 3 Android Development] LEMY67:
Good rom

Enviado desde mi SM-N9005 mediante Tapatalk
[Galaxy Note 3 Android Development] abd96iq:
can i flash this rom on my Korean note 3

N900L

i really want to try it
[Galaxy Note 3 Android Development] shane87:
No. hlte builds are for N9005 and N900P only.
[Galaxy Note 3 Android Development] abd96iq:
well then

can i port it ?
[Galaxy Note 3 Android Development] shane87:
Sure. The link to the source is in the OP. You can check to see if LineageOS has a device tree for your model, or you can start from the hlte device tree and work from there.
[Galaxy Note 3 Android Development] abd96iq:
thanks

i haven't ported a rom before

but i will do it cuz i really like aokp oreo

its very stable and fast

ive flashed it everything is good except sim card is not working also i flashed synergy o b3 kernel
[Galaxy Note 3 Android Development] shane87:
Were you able to flash the hlte build on on your device? As far as sim card goes, you probably need to update your modem. Search around xda for Odin flashable modem files for your device.
[Galaxy Note 3 Android Development] banikgames:
Nice job! I still wait for stable version ;).
[Galaxy Note 3 Android Development] Imprezzion:
N900L is just a N9005 with different firmware. It's also a snapdragon version so it will flash and boot a N9005 ROM but due to region locks it will not get a signal on the modem. It needs a 900L modem and a ROM compatible with that. Most of the custom ROMs support the L and K versions tho.
[Galaxy Note 3 Android Development] abd96iq:
I ve already updated them and am now on LA15.1 hltekor build sim card works perfectly and mobile data but i think AOKP is smother than LA15.1
[Galaxy Note 3 Android Development] shane87:
If it's working on latest LOS-15.1, then it's due to regional lockout. We will have to see what we can do to get AOKP going for hltekor. I sent you a pm with some tips and info on getting started on the port.

For anyone who is having the rotation issues, [MENTION=4581814]stonedead[/MENTION] found a commit that I hadn't seen that may be able to fix the rotation bug. I'm going to get a new build later today and we'll see if we can squash that issue once and for all.
[Galaxy Note 3 Android Development] Imprezzion:
Allrighty then. I'll happily test the build when you release it :)
[Galaxy Note 3 Android Development] shane87:
New Release!

Alright guys, I have a new build up at the download link in the OP. For this build, I pulled in some LOS changes that deal with phone call audio routing, which could help with bt phone audio issues, and I also enabled an overlay that may help with the rotation bug. The overlay was discovered by [MENTION=4581814]stonedead[/MENTION] so a HUGE thanks to him! I may have never discovered the overlay on my own. I also have included pending AOKP commits to add customizable header images. This build also includes all of the latest AOKP commits that have been merged, including fixes and some tweaked features. As always, I upload a changelog with all of the commits pulled in since the last build, so detailed information on the changes between the 4/23 build and todays build can be found there.

I HAVE NOT had a chance to personally test this build! As I have mentioned before, my only test phone is my wife's daily driver, and if she is busy using it, not much of a chance for me to test lol. With that being said, there shouldn't be any major bugs introduced in this build.

Changelog:

Changes to phone call audio routing, may help BT phone audio issues

New overlay that may help with auto-rotation bug

Customizable header images

Full changelog available at download link
[Galaxy Note 3 Android Development] stonedead:
Thanks mate. Will definitely test it. Hopefully we solve the sensors issue.
[Galaxy Note 3 Android Development] Imprezzion:
No good here. Rotation worked for a while but after rebooting (adaway requested a reboot) it immediately stopped again.
[Galaxy Note 3 Android Development] stonedead:
Stop working here too. Quite frustrating this rotation bug. And it occurred on random event too, sometimes after a rebbot, other time after fiddling with google maps.
[Galaxy Note 3 Android Development] Imprezzion:
The only thing we know for sure (kind of?) is that the accelerometer is the guilty one.
[Galaxy Note 3 Android Development] shane87:
All of you guys having the rotation issue, do me a favor. As soon as you notice that rotation has stopped working, get a logcat. You can use an app, such as catlog, or hook up to your PC with adb enabled. Or you can get one using a terminal emulator on your device. If you use adb or the terminal emulator, here are the commands.

For adb (ran from a command line on your PC);

adb logcat -d -f <path/to/file.txt>
Where <path/to/file.txt> is the location to save the logcat, ex. C:\logcat.txt or ~/logcat.txt for Linux.

For terminal emulator (ran on phone):

logcat -d -f <path/to/file.txt>
Where <path/to/file.txt> is the location to save the logat, ex /storage/emulated/0/logcat.txt

Please upload the captured logs, so I can take a look and see what (if anything) the accelerometer is doing.
[Galaxy Note 3 Android Development] awechris:
Protected apps in Settings (in order to prevent certain apps from opening) crashes. Clean Install - everything wiped.
[Galaxy Note 3 Android Development] chispas-elek:
Hello again.

I have disabled hardware button keys from settings and hardware buttons still working. I have recorded a new log, maybe it could help.

Thanks
[Galaxy Note 3 Android Development] shane87:
Hmm, that's odd. I looked through this latest log, and I don't see any intents being called to deal with hardware button presses. I'll fire up my tester Note 3 when I get home and see what I come up with.
[Galaxy Note 3 Android Development] joetiger:
can i install exposed installer on this rom...and how to do it
[Galaxy Note 3 Android Development] shane87:
Yes you can, although be warned that Xposed can cause issues in some cases, so if anything messes up, try a clean flash, without Xposed, before reporting the issue. As far as how to do it, check out the Xposed threads here on xda, they have all the info you need.