Database Develop

[Q] Is there known GPS problems between xt862, and hashcode's Kexec ISC ROM?

GPS doesn't work for me on hashcode's ISC build. Simply can't find satellites. I used several applications, and two builds — issue persists.
Is this expected? Any thought? Any fix?
Also, is it possible to set up "multiboot" for two roms (namely Maverick, and Kexec ICS)? May be by installing Maverick instead of stock rom, and ISC in the safe system? Sorry, if it's a dumb question, I have bought the device only recently after lots of happy years with the original milestone.
Thanks!

GPS works well for me with the 20120905 build. I use it with Google maps/navigation and CarHome Ultra regularly.

Any ideas how to troubleshoot the problem? The device is Verizon xt862, apps and some data were ported from previous installation via titanium backup. Google location services work decently, but once GPS is on, I am lost. Can it be hardware? The phone is refurbished, so...

i am also curious as to why my gps isnt working on stock/mav/cm9 i tried gps fix, sbf, 906.
edit: works just swimmingly now no problems.

GuyWithDroid said:
Any ideas how to troubleshoot the problem? The device is Verizon xt862, apps and some data were ported from previous installation via titanium backup. Google location services work decently, but once GPS is on, I am lost. Can it be hardware? The phone is refurbished, so...
Click to expand...
Click to collapse
Sorry, no. Mine is also an XT862 and it "just worked". I think I did re-install the apps from the Play Store instead of restoring them from backup.

djbolden said:
Sorry, no. Mine is also an XT862 and it "just worked". I think I did re-install the apps from the Play Store instead of restoring them from backup.
Click to expand...
Click to collapse
Restoring apps from Ti backup across different ROMs is asking for trouble IMO, as is restoring data: the few times i've tried to a fresh install of the same ROM it seems to turn out I've been dealing with an app data corruption issue all along... I am getting sooooooo sick of installing 50ish apps from play store each time. Not as painful as on the old laggy-as-fk 600mhz LG phone though.
Somehow my last install went bad when the gf chucked water on my phone during an argument. Dried it off, started it up... all my google accounts and associated data were gone from the phone (still there on tab/desky)... and playstore FCed constantly on opening, even on safestrap restores. On ROM reinstalls setup.apk would FC as soon as I touched anything (both the android or the corner of the screen) on CM7,CM9,CM10, stock, darkdroid... had to SBF it. Again.
Tell me how a few drops of water can cause that issue... bizarre. No HW damage or non-system corruption at all.

Titanium doesn't work well for the kexec ROMs in my experience.
Sent from my XT883 using xda app-developers app

bennyjg said:
Tell me how a few drops of water can cause that issue... bizarre. No HW damage or non-system corruption at all.
Click to expand...
Click to collapse
Maybe it was unrelated?

It doesn't work on stock rom either, so it's not ti-backup. I will try to clean-install the next build to be sure.

Bluetooth Metadata issues after Nougat Upgrade

Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!

aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.

zelendel said:
Ok first you need to understand a few things.
1. Just because it works on an Iphone doesnt mean anything when talking about android apps. They are completely different OSs as well as completely different apps. Built completely separately with different SDK
2. Just because it worked on the last update doesnt mean it will work on this.
As google play music works, that says they changed something in the 7.x update that broke the other apps. They will need to be updated to work with the change in the code.
Click to expand...
Click to collapse
Appreciate the feedback, thanks!
Yup... Definitely understand that iOS and Android are 2 complete different bases...I tested with the iPhone to make sure that the aftermarket Bluetooth receiver in the car was not the problem.
I do believe it's something that Google has changed and I'm starting to realize that the only option I may have is to wait and see.
One point I want to add is that the Nougat update did not break anything when it comes to connecting to my wife's Acura with built in Bluetooth. The track info continues to work fine..
I was hoping someone with more in depth knowledge of the Android systems maybe be able to chime in on what could have changed...I know the 3rd party apps i use have gone through multiple updates since Nougat came out so if they were gonna update something due to compatibility with Nougat, it would've happened already.

aerohp said:
Hi guys,
For those that have Bluetooth in your cars and use apps like SoundCloud, Pandora, etc., have you had issues with track information being displayed correctly?
Ever since I upgraded my Nexus 6 to nougat, the track information seems to be routed differently by the phones Bluetooth to my car's aftermarket Bluetooth receiver. Same has happened with my wife's Nexus 6 after she upgraded last week.
Both phones were working fine when on marshmallow using the same apps...Nothing else different other than upgrading to Nougat.
The only app that shows the metadata correctly on the main screen is the Play Music app. For all other 3rd part apps, I have to select "Channel List" and then I can see the track name. That was not the case with Marshmallow. All apps showed the metadata at the main screen where now it just displays some random numbers.
I know it's not the 3rd party music apps because they all display the metadata correctly when I have my work iPhone connected to my car.
Had the same problem on stock as well as Pure and Nitrogen. It's so frustrating because I don't have the slightest of clue on how I can go about figuring out what, if anything, has changed with the Bluetooth profile.
Any help or feedback would be greatly appreciated!
Click to expand...
Click to collapse
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.

Syndrome666 said:
Exactly same issue here in my '15 Civic Si with Shamu, Victara, and Titan, Bluetooth metadata breaks after the first pairing/connection. Once Bluetooth is interrupted, either by shutting off car or disconnecting Bluetooth, metadata never displays again until I either clean flash ROM anew or delete the bluedroid folder contents and do the whole unpair and re-pair both audio device. Quite a pain of a workaround, and it doesn't stick either, breaks as soon as Bluetooth is interrupted again.
Since you're on Shamu, I can recommend Cyanide ROM and SIX ROM, also Pure Nexus (not sure why yours didn't work with it), I've tested a few updates of each of the three ROMs, and Bluetooth metadata worked fine. Nitrogen never worked for me either. AICP, CM, LOS, Resurrection Remix, Dirty Unicorns, Emotion OS, all break on this feature for now. Not sure how Google's own OS is running in this department, but I've seen quite a number of complaints on this issue with the 5x, 6p, both pixels, but not so much with Shamu. I've not ran Google's nougat since developer preview 5 of 7.0, and back then it was working, can definitely confirm. I just hopped on the custom ROM train ever since DU released their flavor of Nougat, and just can't or want to go back to stock vendor OS. But do try out Cyanide and SIX ROMs, they both worked flawlessly on this device. Both are packed with extra goodies too. If battery is more important, go with SIX ROM, it's by far the most fine tuned nougat ROM I've tested. You won't find it on XDA, look for it on G+ under "Frankie T (R3DS)" community. It's posted with all the direct links for proper installation. Cyanide is another amazing ROM, also another fine tuned ROM, comes with built in black theme, and good battery life (if you set the governor to interactiveX), but really smooth experience overall. SIX, by the way, uses Pure Nexus as a base platform, so just a heads up there. Personally I've used the last two pure Nexus ROM updates and had zero issues with song data displaying via Bluetooth. Make sure you clean flash the ROM, wipe dalvik cache, cache, date, and system. Leave the internal storage unchecked. If the issue persists, then backup your internal storage files/folders to an external drive/device and format the whole internal storage of your Shamu, then throw everything back on and try clean flashing, pure Nexus should work thereafter. I've even restored it as a nandroid backup a few times and had no issues. SIX ROM is pretty much a refined Pure Nexus with extra features. Give these a shot, well worth it. Let me know how it goes for you.
Click to expand...
Click to collapse
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!

aerohp said:
Wow! Thank you for the detailed feedback! Does your Si have factory nav?
Anyway, I can't tell you how many things I've tried to get this thing figured out...I also have active communication with the manufacturer of the Bluetooth unit to see if we can troubleshoot the issue..So far nothing.
This is the first time I'm hearing of SIX ROM so I'm gonna do some reading and then flash it later on in the week. I'll reply back with updates.
Thanks again!
Click to expand...
Click to collapse
Happy to help. No my Si doesn't have the navigation option, I just use my Shamu for that. I've finally got the attention of AICP moderator and developer at AICP G+ community, so it's looking like the Bluetooth metadata issue is a CM/LOS issue so far, they're going to look into it. I captured a logcat and pictures which are posted there under bugs+logcat. It's under AICP G+ community if you want to look at it, posted under my main Google account as Andrey K, you can check it out here: https://plus.google.com/112643646080294190790/posts/4FRbAonGT55.
As for you never hearing about SIX ROM, that's because the dev doesn't participate on XDA forums. It's a really stable nougat ROM all around, and now supports phh's root, which if paired with Magisk app, allows to hide root access from apps like Android pay and Pokemon go.
The most a manufacturer would offer is to replace the device, possibly for a fee, that won't solve your problem. Most nougat ROMs are currently experiencing this bug. Cyanide, SIX, and Pure Nexus do not have this problem, at least not on Shamu.

anyone ever come across a fix for this?

nerdyone255 said:
anyone ever come across a fix for this?
Click to expand...
Click to collapse
Nah, still struggling with it...I keep hoping that a new Android update will fix it but so far no luck. It used to work fine for me in Lollipop but nothing since I've upgraded to Nougat. I'm on Nexus 6. Wife has a pixel XL and had the same issue when she was on Nougat so it's not the phone. She did get the Oreo update this week so I'll try again to see if it works. If not, then this must be a compatibility issue that the adapter manufacturer may need to look at...
The annoying thing is that the metadata transfer is fine when using my work iPhone. But I hate the iPhone/Apple so I only touch that thing when I absolutely have to (work calls, work emails, etc)

Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
Any solutions so far?
My S2 worked perfect with the Civic (only it did not import the whole phonebook). With S8 I have the whole phonebook but no metadata on tracks (still plays and controls work)

Bluetooth Issues on Nougat, Tab S2 T719

My saved Bluetooth pairings keep disappearing in the Bluetooth settings since updating to Nougat, I think it's happening upon rebooting. It's annoying to have to keep pairing with my devices, especially the hands free link in the car! T719 on the German 7.0 firmware I believe, since that was the first to be released for the T719. Stock unrooted. Anyone else seeing this issue?

YrrchSebor said:
My saved Bluetooth pairings keep disappearing in the Bluetooth settings since updating to Nougat, I think it's happening upon rebooting. It's annoying to have to keep pairing with my devices, especially the hands free link in the car! T719 on the German 7.0 firmware I believe, since that was the first to be released for the T719. Stock unrooted. Anyone else seeing this issue?
Click to expand...
Click to collapse
Didn't happen to me but just so we know, after installing the nougat did you do a reset or something, like a clean install.

zeon22 said:
Didn't happen to me but just so we know, after installing the nougat did you do a reset or something, like a clean install.
Click to expand...
Click to collapse
Ah yes I did, I had to factory reset/wipe data because it wouldn't boot up after a dirty install. So I did start fresh, and everything else seems fine.

YrrchSebor said:
Ah yes I did, I had to factory reset/wipe data because it wouldn't boot up after a dirty install. So I did start fresh, and everything else seems fine.
Click to expand...
Click to collapse
Hmm so that's fine then. On top of that you are stock and unrooted
You can try 2 things
-In settings backup & reset- Do network settings reset This will as name suggests clear your wifi/ mobile data/bluetooth settings and passwords etc.
- Check if you have disabled any app which may be the cause or any app which may be causing this.

zeon22 said:
Hmm so that's fine then. On top of that you are stock and unrooted
You can try 2 things
-In settings backup & reset- Do network settings reset This will as name suggests clear your wifi/ mobile data/bluetooth settings and passwords etc.
- Check if you have disabled any app which may be the cause or any app which may be causing this.
Click to expand...
Click to collapse
Thanks for the ideas. No luck so far tho. I reset network settings, then paired with a Bluetooth speaker, rebooted, and sure enough the pairing is gone. I haven't disabled anything at all, for once I'm just running pure untouched stock unrooted lmao. I guess it could be a bug in this particular build? I have a T719. I'll look and see if it could be some app causing it, but I don't have too many apps, and definitely nothing too crazy lol.

YrrchSebor said:
Thanks for the ideas. No luck so far tho. I reset network settings, then paired with a Bluetooth speaker, rebooted, and sure enough the pairing is gone. I haven't disabled anything at all, for once I'm just running pure untouched stock unrooted lmao. I guess it could be a bug in this particular build? I have a T719. I'll look and see if it could be some app causing it, but I don't have too many apps, and definitely nothing too crazy lol.
Click to expand...
Click to collapse
You can check with other 719 users. Is this happening with wifi/5g wifi too btw?
Edit- Also found something, go to apps and select google backup transport and clear its cache and data the reboot. Might as well give this try as well

Not sure about wifi, haven't used it at all because my LTE is better than my home wifi. And I don't see that backup transport app here. Anyway, thanks for the ideas. Hopefully some other T719 owners will chime in.... I'm just not sure how many others there are. I do see a second Nougat build has been posted for my device, for United Arab Emirates, so maybe I'll install that one and see.

Same problem
Hi!
I have the same problem on my SM-T719.
Even after the second update just a month ago.
Sended it in to MOBYLIFE and they said that everything is fine and that it's my problem.
Even though I send them video proof of the opposite.
Sad...

Bluetooth Phone Calls Don't Work

I've heard this a bug with Oreo, but I've had this issue since Nougat. Essentially, I've tried connecting several Bluetooth devices to my OnePlus 3T with OOS 5.0.3 rooted w/ Magisk, and while I can get music and notifications to play, I can neither hear nor speak through the phone options using Bluetooth. I've searched for hours on Google as to why this may be happened, and while there are hundreds of reports and instances of this happening, there isn't a single consistent solution.
I've tried messing with the settings, codecs, deleting cache, deleting data from Bluetooth, repairing devices, deactivating Google Now, resetting the phone, you name it.
Is this a problem that is still prevalent with Oreo? This is probably the stupidest unsolvable thing I've ever encountered, and I'm convinced its software related, given that music and all other audio works.

Never had such issue with Nougat or Oreo.
Where did you read about such standard bug at Oreo?
Unleashed by my rooted OP3T on 8.0

RASTAVIPER said:
Never had such issue with Nougat or Oreo.
Where did you read about such standard bug at Oreo?
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
https://www.zdnet.com/article/andro...-looking-into-buggy-bluetooth-audio-problems/
https://forums.oneplus.com/threads/bluetooth-mic-not-working-on-phone-calls.805719/
https://www.reddit.com/r/oneplus/comments/7zz7fc/oneplus_55t_callers_cant_hear_me_solution/
https://forums.oneplus.com/threads/...all-whether-i-m-calling-or-vice-versa.731333/

smo69 said:
https://www.zdnet.com/article/andro...-looking-into-buggy-bluetooth-audio-problems/
https://forums.oneplus.com/threads/bluetooth-mic-not-working-on-phone-calls.805719/
https://www.reddit.com/r/oneplus/comments/7zz7fc/oneplus_55t_callers_cant_hear_me_solution/
https://forums.oneplus.com/threads/...all-whether-i-m-calling-or-vice-versa.731333/
Click to expand...
Click to collapse
Of those links, only the last one is relevant to the 3T.
What specific Bluetooth devices do you have the problem with?
I've use the phone feature with 3 different headsets, my car head unit, and a BT speaker, all with no issues with calls.

I have a problem with every Bluetooth device that uses phone features. This includes a Gear S3, Car Dongle and ear phones.

I have tried 2 BT SPEAKERS, 2 BT headset,.1 smart band and 1 smartwatch (moto 360).
No issues at all
Unleashed by my rooted OP3T on 8.0

I must have some kind of app causing the problem. I'm just not even sure which app it could possibly be.

smo69 said:
I must have some kind of app causing the problem. I'm just not even sure which app it could possibly be.
Click to expand...
Click to collapse
Any Magisk modules being used? I haven't seen this Bluetooth issue specifically (from Magisk modules) but they can sometimes cause random bugs, and it is a good enough place to start as any.
I think the Samsung gear watches in general, do not play well with a lot of non-Sammy phones. At least from other threads I've seen around. But it is suspicious that you are having the issue on multiple Bluetooth devices (although you don't name the other brands). So I think you are on the right track, that it may be an app or something else peculiar to your device setup.
I've had the phone functions work just fine with Motorola, Plantronics, JBL headsets, JBL speaker, Subaru head unit (Kenwood made stereo, from what I understand).

smo69 said:
I've heard this a bug with Oreo, but I've had this issue since Nougat. Essentially, I've tried connecting several Bluetooth devices to my OnePlus 3T with OOS 5.0.3 rooted w/ Magisk, and while I can get music and notifications to play, I can neither hear nor speak through the phone options using Bluetooth. I've searched for hours on Google as to why this may be happened, and while there are hundreds of reports and instances of this happening, there isn't a single consistent solution.
I've tried messing with the settings, codecs, deleting cache, deleting data from Bluetooth, repairing devices, deactivating Google Now, resetting the phone, you name it.
Is this a problem that is still prevalent with Oreo? This is probably the stupidest unsolvable thing I've ever encountered, and I'm convinced its software related, given that music and all other audio works.
Click to expand...
Click to collapse
I have the exact same issue. I've tried nougat/oreo.....official OOS....different roms also. Clean flashed the 3T but no luck.
Media audio works perfectly fine. As soon as somebody calls and I answer, the line becomes mute to whatever it is connected to. I've tried both with my car and BT speaker.
I then have to route the call to the ear pierce on the phone to be able to continue with the call.
Everyone I have found with this issue have sent their phones back for repairs.

OnePlus 3Ts seem to face an issue where if you're in a voice call using your SIM card, and also connected to some Bluetooth device at the same time, the WiFi seems to just s**t itself. It can't give more than 0.10 Mbps ever. It left me confused for a long time until I figured it was due to me calling on my Bluetooth headset/speaker. Truly annoying imo.

I finally figured it out. As I stated earlier, I was sure it was software based because music worked just fine, so I was looking for a culprit app that might have been hogging the phone audio/mic. Oddly enough, it was the T-Mobile Visual Voicemail app. I went ahead an uninstalled it. That app was not worth being unable to use Bluetooth hands-free in my car.

I take that back. Suddenly, it's not working anymore, so I'm more inclined to believe there's something wrong with the phone speaker/mic suddenly hanging with apps other than the actual phone app. The Visual Voicemail app only exposed that there was an issue with this, but the app itself did not seem to be the problem.

Same problem here, I am on Oreo (final beta). Have you managed to find a solution?

DIOmenik said:
Same problem here, I am on Oreo (final beta). Have you managed to find a solution?
Click to expand...
Click to collapse
Just saying.
When was the last time that you had a factory reset?
Sent from my ONEPLUS A3003 using Tapatalk

RASTAVIPER said:
Just saying.
When was the last time that you had a factory reset?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
A few months ago, when moving back from Oreo to Nougat for battery problems.
If you can confirm that on the last (stable?) Oreo release you are not facing this issue, I would really appreciate it and proceed with a factory reset.

DIOmenik said:
A few months ago, when moving back from Oreo to Nougat for battery problems.
If you can confirm that on the last (stable?) Oreo release you are not facing this issue, I would really appreciate it and proceed with a factory reset.
Click to expand...
Click to collapse
I am not at any stable version.
And have tried many different bt sets.
Also never had battery problems at Oreo
Sent from my ONEPLUS A3003 using Tapatalk

DIOmenik said:
A few months ago, when moving back from Oreo to Nougat for battery problems.
If you can confirm that on the last (stable?) Oreo release you are not facing this issue, I would really appreciate it and proceed with a factory reset.
Click to expand...
Click to collapse
I'm on stable OOS 5.0.6 (and multiple/sequential stable OOS builds before that) and never had issues with BT calls, using a headset and my car stereo.

2020, OnePlus 3T rooted magisk, android Pie, same bluetooth problem.

Bluetooth will not enable - S10

Hi all! I was wondering if any of you guys have seen this issue before. I have an old Galaxy S10 that I wanted to resurrect for emulation and forgot the reason why I stopped using it was because the Bluetooth functionality, once toggled on, would look like it's trying to turn itself on but never enables.
I've tried:
Installing all updates
Resetting network settings
Clearing Bluetooth app cache / pairings
Wiping the system cache partition
Factory resetting
Re-flashing current and past firmwares
I was able to get Bluetooth to enable and function normally by random after re-flashing the firmware but would quit after 5-10 minutes.
On the S10 and my current phone Pixel 4a (with functional Bluetooth) I went into Developer options to check currently running services to compare. On the 4a the Bluetooth process is listed as having 1 process and 7 services, whereas on the S10 there were only 2 services and were missing services such as SapService, HidDeviceService, BluetoothPbapService, GattService. (I can post in an edit which services are failing to run on the S10 if need be). The Bluetooth process on the S10 will only show up once Bluetooth is toggled even though it doesn't enable, but will stop running, then start running again, rinse and repeat.
So that being said, is this a hardware issue that I'm SOL with? Are there any other remedies that I could try?
Any input would be appreciated. Thanks!

First off, which S10 do you have... Exynos/Snapdragon makes a big difference, but knowing the model number helps a lot in general as well.
What firmware are you on now?
On my 973U (ie, Snapdragon) I have 1 process and 7 services right now (with BT turned on)... on Oreo with January security (I have stayed off A12 because of many reports of issues on it). I can provide more detail later if needed, as well.

.

schwinn8 said:
First off, which S10 do you have... Exynos/Snapdragon makes a big difference, but knowing the model number helps a lot in general as well.
What firmware are you on now?
On my 973U (ie, Snapdragon) I have 1 process and 7 services right now (with BT turned on)... on Oreo with January security (I have stayed off A12 because of many reports of issues on it). I can provide more detail later if needed, as well.
Click to expand...
Click to collapse
I have an SM-G973U (CCT) running G973USQU6GUJ3, which I believe is the last version of Android 11. I've tried Android 10 and 9 firmwares (can't recall which ones) and I've been having the same issue regardless, which makes me think it could be hardware-based.
In a couple of hours I can edit this post with the two processes that do run, if need be.

Made a mistake - my phone is 975U but that shouldn't matter.
I'm on G975U1UES6GUL1 which I believe is a later version than what you have... but I don't think that will fix anything for your issue. I was on GUL before, and everything worked fine then.
I'd say start off bone-stock after an ODIN and see if it works there (ie, don't download anything, if you can avoid it). Maybe some app you have is killing the BT? But if it doesn't work there, then yes it could just be a hardware thing... disappointing for sure.