yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] joetiger:
I am afraid that i am gonna mess this up because there is alot of exposed threads so can't you tell me which one will work for the note 3 please?
[Galaxy Note 3 Android Development] cssr:
I use magisk and magisk manager for root. In the download list of magisk manager is a Xposed framework installer which works with this ROM on a N900V. I use it for Xposed fakegapps module. Warning! Some Xposed modules may not work and may softbrick your phone or cause boot loop.
[Galaxy Note 3 Android Development] wahaj sheikh:
Im getting this any one know why?
[Galaxy Note 3 Android Development] rayman95:
why do you post the same on 2 different threads, one with android 8.1 and another with 9.0???

No issue on LA16.0...
[Galaxy Note 3 Android Development] shane87:
Are you running this AOKP Oreo ROM? When does it happen? Logcat? Device? Gapps version? Twrp version? Clean or dirty flash? No one can troubleshoot an issue from a single picture. Provide more info.
[Galaxy Note 3 Android Development] DaOldMan:
Mate, this cheeky user asks the same question on Los 16.0 thread as well...
[Galaxy Note 3 Android Development] JJEgan:
Cereal Offender
[Galaxy Note 3 Android Development] shane87:
How does one offend cereal? Lol :D

Back to topic, from this point forward, any new issue reports that don't specify:

1. AOKP version/build date;

2. Device model (i.e. hlte/hltetmo/n9000/etc);

3. Gapps version (i.e. OpenGApps 8.1 mini 10/28/18, etc.);

4. Indication of dirty or clean install and TWRP version;

5. A CLEAR description of the problem, and how to recreate it if possible

WILL BE IGNORED!!

I hate to be a hard-ass about this, but without at least the information above, I can't figure out whether your issue is related to AOKP, your specific device, your gapps version, or something that got messed up during install.

On a happier note, a patch has been pushed to LOS Gerrit that MAY fix bt call audio issues, though right now there are a lot of negative votes on it since it is in a system wide project that could have ramifications for a lot of devices. I am keeping an eye on it, and I may try picking the patch in as soon as I get a chance to compile a new build, just so we can see if it does fix the Bluetooth issue.
[Galaxy Note 3 Android Development] wahaj sheikh:
[/COLOR]

-_- so
[Galaxy Note 3 Android Development] shane87:
Please read the information above, and provide the requested information. Otherwise, stop posting in this thread.
[Galaxy Note 3 Android Development] shane87:
New Builds Coming Soon!!

Hey guys, I know it has been a while since I have pushed up any new changes. I have been doing a lot of research into this bluetooth bug, and I have been trying to set up a personal build server. My build server has been shelved (temporarily) until I can order a new hdd and wifi module for it, as every spare hdd I have is dying (damned S.M.A.R.T. reporting!) and the wifi module I have has a RealTek chip, which is notoriously cranky on Linux.

On the bluetooth front, I got excited. [MENTION=2473151]macs18max[/MENTION] responded to my pm asking about how he got bluetooth call audio working for the Galaxy S6, and sent me the patch to implement it. I looked over the patch, it was a simple matter of starting the SCO interface, and seemed perfect. Even better, someone created a commit and pushed it to LineageOS's gerrit for inclusion in official LineageOS builds! So I looked at the commit on LOS. And my dreams were crushed. Kevin Haggerty (hlte maintainer for LOS, and an excellent coder) said that this patch did NOT fix bluetooth for hlte, and it was also reported that the SCO interface was ALREADY initialized on hlte. But I kept digging, and found new hope. Apparently the issue on hlte has to do with the WBS sample rate not being properly set, similar to issues faced by the Samsung Galaxy A3, and someone linked to some commits needed to set the WBS sample rate properly. Two of the commits linked (for klte as a template) had already been implemented for hlte. The third commit (the big one that actually sets the WBS sample rate) was committed to the LOS gerrit, and as of November 11th was verified and merged in officially. So, as of right now, I am running a full set of builds, for hlte, hltechn, hltekor, and hltetmo, and as soon as they are done and pushed to AFH, I will let you guys know and the

testing can begin!
[Galaxy Note 3 Android Development] pelucaslee:
Realy good news, thanks.

Enviado desde mi SM-N9005 mediante Tapatalk
[Galaxy Note 3 Android Development] shane87:
New AOKP Oreo Build

Hey guys, the new builds are up! Download links are in the OP. The big change in this build is, of course, the potential bt bug fix. So those of you seeing the bt issue, please test and let me know how it goes!
[Galaxy Note 3 Android Development] rayman95:
thank's for your hard work.....don't have BT devices to test but will maybe try with the radio in the car...
[Galaxy Note 3 Android Development] Marvino.:
I hope to read that the problem is fixed through the initial tests. Note 3 is about to be reborn again.. Thanks Shane!
[Galaxy Note 3 Android Development] pelucaslee:
bluetooth calls do not work shane87.

Sorry.

Enviado desde mi SM-N9005 mediante Tapatalk
[Galaxy Note 3 Android Development] kirvs:
On 2018-08-19_2149 version,

bluetooth connection

--- to big jambox - ok

--- to plantronics legend - media plays ok, recorder - ok (records thru headset and plays the recording back)

<bluetooth works> when not making phone calls

--- making phone calls when connected, creates loud static noise as if transmit and receive is reversed creating speaker feedback.

I do appreciate all the hard work you are putting into this ROM for older model.

Thanks,
[Galaxy Note 3 Android Development] shane87:
New Builds Coming Soon

Hey guys, I am still digging on this bt call audio issue. I swear, this bt bug has become my unicorn, lol. I have found some changes on LOS's gerrit that look promising. They mostly deal with the audio processing in the hardware_samsung project, which hltex uses. Some of the commits are a pre- and post-processing rewrite, a removal of some unneeded bt_sco_profiles, removal of the out stream resampler, and a few others. I also went ahead and pulled in the commit that [MENTION=2473151]macs18max[/MENTION] used to fix bt call audio in the S6 and A3, even though Kevin Haggerty says it is NOT needed for hltex. The builds are running now, I should have them uploaded for testing in a few hours.

[EDIT]Guys, I have also added a commit to enable Always On Display feature for all hltex variants[/EDIT]
[Galaxy Note 3 Android Development] shane87:
New builds delayed

Alright guys, I know I said I was going to get some new builds up, but I may have to push them off until tomorrow. The extra feature I added, Always On Display, is working great. Except that it makes turning the screen back on kind of like a game of Russian Roulette, lol. I think it is the screen blanking option of AOD that is causing the issue, but I am going to have to take a bit of time to test it out and make sure it works properly. If I can't get AOD working by tomorrow morning, I will just run a set of builds without AOD, and mess with that later.
[Galaxy Note 3 Android Development] Unidave199:
Shane,

Your patience and steadfastness continue to inspire me in my projects at work. No need to apologize for 'delays' or having your real life get in the way of things. Without sounding too much like a fanboy I just wanted to encourage you to pace yourself. Although I switched to your Nougat version (which is super duper stable and continues to make my phone the envy of many a iPhone user) I keep tabs on the Oreo builds to see if the elusive BT bug has been caught.

Nougat was a win! Oreo and/or Pie are just gravy on the proverbial turkey.

Thank you so much for your time and dedication and I know I speak for many of the XDA followers that we all owe you a debt of gratitude.

Dave
[Galaxy Note 3 Android Development] rorroh:
how to center the clock in status bar:confused:
[Galaxy Note 3 Android Development] shane87:
New AOKP Oreo Build

Hey guys, I

FINALLY

got a chance to get new builds up. These have the potential bluetooth bug fixes I mentioned a couple of weeks ago. They do NOT have Always on Display support. I tried to add that, and it works, except it makes the device difficult to wake up. :/ I tried a few different fixes for the issue and couldn't figure it out. These builds also have the latest upstream changes from AOKP and LOS, except for an update to the build fingerprint that I didn't find the commit for until I had started the builds. Please test these builds out and let me know if there is any change or improvement to the bluetooth bug.
[Galaxy Note 3 Android Development] Ave666:
Nice update but I didn't have chance to test BT call yet
[Galaxy Note 3 Android Development] Buslova:
well [MENTION=3482571]shane87[/MENTION] I'm sorry to report that the BT calling bug is very much alive in your latest build. at least it is on my sprint n900-p. Just wanted to let you know in case no one else had yet.
[Galaxy Note 3 Android Development] Unidave199:
I was just going to try the install today but see someone beat me to it....
[Galaxy Note 3 Android Development] addak:
Hi

I currently have an issue where I'm unable to send messages but I'm able to receive them. I've read articles online stating that it's an SMSC issue, in which case I'm planning to resolve said issue with the service provider. But I'd also like to know whether it's possible that it's an issue with the ROM as it was previously working on my previous ROM ( stock ). Just want to cover all my bases.

Thanks.
[Galaxy Note 3 Android Development] chris rock:
Did you update your modem?
[Galaxy Note 3 Android Development] JJEgan:
Usual is APN setting wrong.
[Galaxy Note 3 Android Development] addak:
Yes I had updated my modem(nordic one since it seems it works best) and baseband before installing the custom ROM. I mean my data's working, I can receive and make calls and Mobile data too works fine.

As for the APN, i thought that issues like no data access pertain to a wrongly set APN.
[Galaxy Note 3 Android Development] LenAsh:
Thread cleaned.

Members should ask questions unrelated to this Dev topic in the Q and A Forum for the device.
[Galaxy Note 3 Android Development] shane87:
Hey guys, I just wanted to let you know that I haven't forgotten about you. I am at wits end on this bluetooth bug. My guess as to what is going on is that it is due to us using old proprietary blobs. Unfortunately, those blobs are all we have. Samsung will not release the code to let us compile them ourselves, and they are not going to release updated versions of them. This device is too old. Even in the LOS 16.0 unofficial thread, the BT bug is listed under known issues, and lists it as a "Bug since Oreo". I am not saying that it is impossible to fix, I am just saying it may not happen, unfortunately. On another, but related, topic, I am working on Pie bring up. Once I have something ready for release, I will start a new thread for it. Beyond that, lets keep Pie out of this thread, as asked by the moderator above. Thanks for all of the testing you guys have done!
[Galaxy Note 3 Android Development] jprimero15:
Yeps i too also tried several things to fix it....i also tried to load g2 bt firmware which is working well in s4 but bad luck.. It doesn't work in hlte.. haggertk and jav tried to fix it also but didn't succeed.. I was talking with them this past days and they seem to ran out of ideas to fix the bug......
[Galaxy Note 3 Android Development] shane87:
Glad to know that I am not the only one pulling my hair out with this damned bug. Like I said before, it has to be something in the BT blobs. I hate proprietary software! I have dug through several bt snoop logs submitted by different users, and I can't find anything that is specifically causing it. And my own troubleshooting is very limited, as my Note 3 is no longer in active use, or having active service, so I can't even test bt calls.
[Galaxy Note 3 Android Development] Unidave199:
BT Fixed????

Hya one and all. Can anyone else weigh in on this FIX??

https://xdaforums.com/galaxy-note-3/development/trying-to-fix-bt-calling-issue-t3878607/page8

Lineage OS also is declaring it fixed in their 'Whats Working' section. They are claiming BT CALLING is working as well as BT Audio.

Any thoughts????
[Galaxy Note 3 Android Development] shane87:
What!?!? I can't believe it's finally fixed! Guys, I know I haven't posted any hlte builds in a long time. I don't even have an hlte anymore, and I have been going crazy trying to fix selinux on aokp pie for cheeseburger (OP5). But this weekend, I'll get the hlte Oreo source pulled back down to my build box and get this fix, and all other updates, pulled in and put up a new beta build for you guys to test.
[Galaxy Note 3 Android Development] Unidave199:
I would think all the Note 3 sites would be exploding with the news! I will be happy to test this weekend any versions you get put together. Feel free to IM me or post here and let me know what I can do to help...
[Galaxy Note 3 Android Development] shane87:
Coming soon to a Note3 near you!

Alright guys, the magic is about to happen!

I have fetched in the latest Oreo updates, and picked the BT fixes from the lineage-16.0 branch back to AOKP Oreo.

The BT fix is

NOT

official yet, LOS is still doing some testing, so until they make it official, I will do more beta builds! I just started a set of builds with the fix, and hopefully I will have time to upload them tomorrow.

Stay tuned!

HUGE

thanks to [MENTION=6561802]jprimero15[/MENTION], and all of the LOS team that worked on this bug, even when us lesser mortals had given up!
[Galaxy Note 3 Android Development] jprimero15:
Before SOMEONE says im falsely praised and i didn't help on this BT thing.. Yes that's right.. Its not my commit but z3DD3r's originally for hammerhead.. And i only tried the fix on hlte and it worked.. But on other things for hlte.. I helped alot, one of this is contributing to LOS.. U can check the hlte trees on gerrit.. Actually its you(you know who you are) who didn't helped on anything..
[Galaxy Note 3 Android Development] shane87:
It's here!!

Guys, the BT fix builds are up!!

This build has all of the committed changes for AOKP (almost none, everyone is in Pie mode, hahaha) and LOS since 12-09-2018.

It also has the BT fix that Unidave199 brought to my attention.

Again guys, I want to emphasize that I did

NOT

author this fix! That honor goes to z3DD3r over at LOS.

I want to give another huge thanks to [MENTION=6561802]jprimero15[/MENTION] for testing the fix on hlte, along with [MENTION=5545101]steadfasterX[/MENTION] and Nolen Johnson for additional testing of the fix.

Please let me know how this build runs. I don't have an hlte to test on anymore.

Without further ado, here are the download links (also in OP):

hlte

hltechn

hltekor

hltetmo
[Galaxy Note 3 Android Development] Unidave199:
Sweet! Let me download it and I can do some testing... I just did a backup of AOKP Nougat so ready to wipe and try a little Oreo. I will report back by Friday what I find out..

Dave
[Galaxy Note 3 Android Development] Unidave199:
Im sorry to say... it was a no-go for the BT with the ROM . I still got the Intermittent Static like before using 2018/9/23 ROM that you put under the BT Test Folder
[Galaxy Note 3 Android Development] shane87:
Well damn. I'm on vacation next week, but as soon as I get a chance, I'll take a look and see if I made any errors pulling in the fixes.
[Galaxy Note 3 Android Development] Unidave199:
Please let me know what I can do to help. Send me an IM and you can send a text my way if that helps.... I am loading HAVOC OS now to just see if BT will work on that..

EDIT:

HAVOC OS doesnt seem to want to work with a Sprint Phone..

Update... I did load RR and the bluetooth works flawlessly on my PLT legend earpiece...

---------- Post added at 11:34 PM ---------- Previous post was at 10:48 PM ----------

Did you see this thread?? Its for PIE apparently but..........

https://xdaforums.com/galaxy-note-3...mix-v7-0-0-t3894244/post79744270#post79744270
[Galaxy Note 3 Android Development] shane87:
I hadn't seen that thread, but I would assume that that fix flash is a rebuild of the bt libs using the fix that I tried to include in my last build. As I said, I won't have time to do much work until late next week, but I would assume that I goofed the application of the fix. It also could be due to the fix being written for pie, and I am trying to apply it to Oreo. Like I said, I'll take a look through my tree next week, and see what I can figure out. Thanks so much for testing. I'll update when I know more or have more test builds.
[Galaxy Note 3 Android Development] Unidave199:
All good stuff! Enjoy your vacation!!!

Dave
[Galaxy Note 3 Android Development] shane87:
Another Build Is Up!

Hey guys, I just pushed a new set of builds up. When I checked my last build, I did pull in the BT fix from LOS, but I also screwed up my sync at the same time. It

shouldn't

have had any effect on the fix, but the Android build system is incredibly complex, so it is possible that it could have messed something up. Luckily, the only mess up that I made had to do with the LG G3, which I was only building for myself, and no longer have anything to do with. (My G3 died. Ah well, now I have an OP5, which I LOVE!!) Anyway, other than fixing that mess up, and pulling upstream updates (mostly translation imports) from LOS are the only changes in this build from the last one I posted.

Someone please test this and let me know if the fix worked this time.
[Galaxy Note 3 Android Development] Unidave199:
[MENTION=3482571]shane87[/MENTION] I will give it a go in the next few days!
[Galaxy Note 3 Android Development] Unidave199:
No-go

[MENTION=3482571]shane87[/MENTION]

Sorry boss, the bluetooth calling is a no go... same problems...

As always I am here to test whatever I can to help!

Dave
[Galaxy Note 3 Android Development] shane87:
Hmm, that's odd. I know that the fix is picked in and activated in the common tree. Damn. I'll take a look this weekend, see if I can dig anything up. I know that the fix is still not official on Los, and it was written for pie, not Oreo, so I may have to wait for them to make it official and backport it before I can get it working for us. I'll look at it over the next few days and see what I can find. Thanks again for testing.
[Galaxy Note 3 Android Development] Unidave199:
[MENTION=3482571]shane87[/MENTION],

For whatever it is worth, I had loaded two flavors of Pie. EvolutionX and the RR version. Both rand pretty smooth and the BT calls were fine, but noticed that neither one of them would keep a 'lock' on my Fitbit Versa. I went back to your AOKP 7 so I can keep a reliable bluetooth connection which I depend on for notifications and tracking.

Ill be happy to keep testing as much as I can for ya..

D-
[Galaxy Note 3 Android Development] Niropa:
[MENTION=3482571]shane87[/MENTION] hey! I was wondering if you knew if the aokp pie sources buildable for the note 3? I wanted to build some personal builds of it but my computers specs are atrocious atm and would take days to find out myself lol. thanks in advance
[Galaxy Note 3 Android Development] shane87:
Well, AOKP pie in general is buildable. However, our selinux is a mess right now, many devices have to be built with selinux set to permissive. Also, there are no pie sources for hlte/hltetmo/hltechn/hltekor. You will have to fork los's hltex and msm8974-common pie trees, and update them to work with aokp. I haven't even started on pie trees because, a) the bt bug has kept Oreo from being official, so I didn't want to start pie forks and, b) I no longer have an hlte to do any testing on.

If you need any pointers on forking and converting the los trees, just shoot me a pm, it's not terribly difficult.

One final note, none of our pie sources have been updated recently. I have a TON of open pie commits on the aokp Gerrit, but they are over a month old. Everyone has been busy, and nothing has been merged in a while.
[Galaxy Note 3 Android Development] Niropa:
ahh okay. yea i was gonna fork [MENTION=6561802]jprimero15[/MENTION] 's sources for one of his pie roms like rr and edit them for aokp. I heard about the bt bug but im just using this as a side phone to mess around with. ill probably start work on a build for it tonight. If i run into any issues ill be sure to shoot you a PM :) I haven't compiled a rom in at least a year lol. thanks again.

also do you care if it builds alright that i make an unofficial thread for it? I was thinking of shipping it with a custom rom and other commits to make it distinguishable from the builds straight from source.

EDIT: also its been years so I can't remember if it was the zenfone 2 or nexus 6p but i was briefly the official/unofficial maintainer of it for aokp. We were just waiting on lineage to make their builds official before shipping ours but i took a break from rom maintain before we were able to see that through.
[Galaxy Note 3 Android Development] shane87:
I am going to respond to this via pm, just to keep the thread clean and on topic.
[Galaxy Note 3 Android Development] ivi64:
Will it work on the SM-9002?

Will both sim cards work?
[Galaxy Note 3 Android Development] rayman95:
STOP POST EVERYWHERE SAME QUESTION...

only 1 sim card work....stay on stock if you want both
[Galaxy Note 3 Android Development] ivi64:
It works on this, but there are some problems.https://download.mokeedev.com/h3gduoschn.html
[Galaxy Note 3 Android Development] Eleo:
https://xdaforums.com/galaxy-note-3/development/rom-dotos-v3-0-t3902350/post80242831
[Galaxy Note 3 Android Development] shane87:
Can you get a logcat of the crash?
[Galaxy Note 3 Android Development] Chinaboy5216:
[MENTION=3482571]shane87[/MENTION] Will other HLTE versions become available once the rom stabilizes a bit? Like HLTE CHN, HLTE KOR and HLTE TMO ?

No ETA just curious here
[Galaxy Note 3 Android Development] Imprezzion:
I'll have to install it again and recreate the rotation issue first. I might have wiped it without backing it up hehe. No SD card in my phone and the storage is almost full due to like, 18gb of music..

I can do it but it might take a day or something.
[Galaxy Note 3 Android Development] shane87:
That all depends on how much time I have. As of right now, I just don't have the time to work on anything other than hlte and my daily driver, which is an LG g3. With that being said, I have looked in to hltekor, and it is identical to hlte except for the networks and settings handled by the init program. So I guess the answer is maybe, but probably not.

With all of that being said, anyone who wants to work on other hlte versions, pm me. The hlte-common tree is already being kept up to date by me, so anyone who knows how to use Linux, repo, and Gerrit shouldn't find it too difficult to pick up the other hlte devices. Or anyone who wants to learn, though it can be difficult and frustrating at first. I will gladly help out anyone who is serious about learning to build aokp!
[Galaxy Note 3 Android Development] Chinaboy5216:
Thanks for the reply, pity i'm not clever enough to support you in this or i would place myself as candidate. But hopefully there are people with more skills willing to support you in this.

Thanks again for the reply !!
[Galaxy Note 3 Android Development] Imprezzion:
Got a logfile for ya. Doubt it's correct since it's super small but i did use your exact command in terminal emulator.
[Galaxy Note 3 Android Development] awechris:
LogCat of the Crash

--------- beginning of crash

05-02 18:56:17.349 2277 2277 E AndroidRuntime: FATAL EXCEPTION: main

05-02 18:56:17.349 2277 2277 E AndroidRuntime: Process: org.lineageos.lineageparts, PID: 2277

05-02 18:56:17.349 2277 2277 E AndroidRuntime: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.settings/com.android.settings.applications.ProtectedAppsActivity}; have you declared this activity in your AndroidManifest.xml?
[Galaxy Note 3 Android Development] powerbyandroid:
Any screenshot? :laugh: