[Bluetooth] "No Phone" issue across ROMs - OnePlus 3T Questions & Answers

So ever since the days of CM 13 I've had issues connecting my phone to my car (2015 Nissan Altima) with CM/LOS-based ROMs. I thought that AOSP/CAF-based ROMs would be better, but it's very hit-and-miss. I wanted to ask for some help from the developer community to see what can be done. I'll be exploring differences between ROM files to see if there's a bluetooth issue I can spot, but in the meantime here are the ROMs that I've tested:
Work with Bluetooth:
Freedom OS
Freedom OS CE
Oxygen OS
CarbonROM
Paranoid Android
Do NOT work with Bluetooth:
AOSIP
Citrus-CAF
Validus/Tesla
Phoenix AEX
Vertex OS Carbide
Candy 7
Slim 7
AOSP Extended
Resurrection Remix
I will add ROMs to this list as I test them. I haven't tested a lot of LOS ROMs, because I assume they won't work as they have the same bluetooth stack. I have looked at the init.qcom.bt.sh file and all ROMs have the same values despite some working and others not. Also, the ROMs that request access to messages separately from the original "pair" dialog are the only ones that work. Is there anything that I can do to fix this issue? Are there certain files that I should compare between ROMs? Can you change the bluetooth stack for a ROM by changing text files in the ROM or would that need to be changed in the base before the ROM is compiled?
Thanks in advance!

Also have the same issue. Which is why I'm using AOSPA (among many other reasons)

Issue also present for me.

I finally got tired of waiting for someone to fix this so I learned how to build ROMs and extracted the BT stack from AOSPA for some of my favorite ROMs and they now work in my car! Here's the thread

Related

Difference between so many similar ROMs?

First of all, it's amazing how far Mi5 has come in terms of development and developer attention. There was a time when all this subforum had was 2-3 unofficial TWRPs, and that's it.
Now there are an amazing number of ROMs available. But the increase in variety has brought with it increasing confusion. A lot of the features overlap. Which ROM to flash? Do we just keep on cycling between them till we find the best match for us?
So I would appreciate if we could document the differences between the various ROMs in terms of features, stability, lack of bloat, etc., to help users choose the one suited to them.
@33bca, your input would particularly help, since you've provided almost half the ROMs in this subforum.
Marshmallow:
Official CM 13 (stable snapshots)
-really light
-boots really fast
-no network traffic indicator
AOSP (JDC)
-has substratum theme engine
Dirty Unicorns
PAC-ROM
AOSP-CAF
Paranoid Android
AICP
Mokee
Old ROMs (not recommended):
Hexagon
AOKP
crDroid
BeanStalk
SlimROM
Tipsy-OS
H2OS
BlissROM
ZephyrOS
Resurrection Remix
-quite a heavy ROM (system takes up 10GB )
-boots slower than CM 13
-fast charging LED blinking issue still exists
Nougat: (CM theme engine and firewall missing for relevant ROMs)
Lineage OS 14.1 (Official)
AOSP JDC (OMS) (Official)
CypherOS 3.5.1
AICP (Official)
AOKP
BeanStalk
Resurrection Remix 5.8 (OMS)
Slim 7 (OMS)
SlimDragon 1.1 (OMS) (Official)
Nitrogen OS
crDroid 1.9
Mokee
Zephyr OS 6.1 (OMS) (Official)
XOSP 7.2
XenonHD
DU 11 (OMS)
Xiaomi.eu
UnitedMIUI
In my personal opinion, at this stage, the only Marshmallow ROM you should consider flashing anew is CM 13 because it's the only one with weeklies, and hence actively maintained. The other ROMs will not be maintained as the developers have moved to the Nougat ROM base.
All Marshmallow ROMs except CM13 contain the laggy performance bug below 5% battery.
The nougat ROMs so far are quite stable and usable.
There's just the issue of a missing CM theme engine on CM based ROMs, which is easily resolved by using Substratum Legacy. The OMS compatible ROMs of course can use the latest Substratum framework.
There are little features missing here and there, which probably won't affect usage for a majority of people:
In the WiFi menu, we can't select WiFi frequency between 2.4 GHz, 5 GHZ, and automatic.
Your input is right, having more roms dont mean basicly its better. You have more roms to chose, thats right, but you also have more roms which are basicly the same with the same features.
My experience is, that all the roms with a lot of modifications (like DU, AICP, RR, Beanstalk and so on) are basicly the same, they have an external app for all modifications and near the same options.
Other roms like Paranoid Android, AOSCP, JDC and Cyanogenmod, try to keep the system clean while they still offer some modifications built into the system app to keep the AOSP feeling.
AOSP is AOSP, there i dont have to say much about
Thanks, man. So is it fair to say that DU, AICP, RR and such can be clubbed into the same category, as in "Install any, they're all the same", while it would be more useful to differentiate between AOSP, JDC AOSP, CM, AOSCP and so on?
I'm unwilling to flash ROM after ROM to find out the differences between them. If anyone has the experience of flashing two or more ROMs, please contribute to this thread so that it can become a useful guide to people. I'll keep adding the info to the OP.
Is there a bugs free custom ROM based on cm13 or cm14 so far? What about Mokee?
@selmandeli The best you're going to get is of course the relatively stable weeklies of official CM13. Since it is being maintained by an official CM developer and has had several months to mature, a lot of bugs have been fixed.
Apart from that, most of the 6.0.1 ROMs should be fine, even though they're unofficially built, as the code base is stable and only some kernel changes were needed, which, thanks to the awesome dedication of bgcngm and h2o64, we have.
No 7.1 based ROM is stable yet, since the CM code base is being actively updated. Even here, your best bet is the unofficial CM 14.1, since the developer maintains and fixes bugs himself.
The other 7.1 ROMs depend on CM development, and additionally on whoever their active developers are. The guys we have do a great job of keeping the respective code bases up to date though.
andy356 said:
Thanks, man. So is it fair to say that DU, AICP, RR and such can be clubbed into the same category, as in "Install any, they're all the same", while it would be more useful to differentiate between AOSP, JDC AOSP, CM, AOSCP and so on?
Click to expand...
Click to collapse
@andy356 DU has some original features built into it. Not sure about the version for MI5 though.
Thanks @mintyx. Could you elaborate a bit so I can put it in the OP if it applies?
@WhyOrean Do you plan to continue with your custom CM 14.1 like you said in the thread? Or will the focus be on other ROMs?
andy356 said:
@WhyOrean Do you plan to continue with your custom CM 14.1 like you said in the thread? Or will the focus be on other ROMs?
Click to expand...
Click to collapse
Plan is not dropped..!
andy356 said:
Thanks @mintyx. Could you elaborate a bit so I can put it in the OP if it applies?
Click to expand...
Click to collapse
@andy356 you should search for Dirty Unicorns Fling, Pulse and Smartbar. These are their original ideas. I don't know if someone else has used it in their rom. It is open source so anyone can implement them.
andy356 said:
In my personal opinion, at this stage, the only Marshmallow ROM you should consider flashing anew is CM 13 because it's the only one with weeklies, and hence actively maintained. The other ROMs will not be maintained as the developers have moved to the Nougat ROM base.
All Marshmallow ROMs except CM13 contain the laggy performance bug below 5% battery.
Click to expand...
Click to collapse
@andy356 Tap to home feature implemented in any marshmallow rom?
dkmsn8 said:
@andy356 Tap to home feature implemented in any marshmallow rom?
Click to expand...
Click to collapse
Nope. When it seemed like most of the bugs were gone, and devs could then focus on it, Nougat code was dropped. Now there's again a mad rush to get the major bugs out on Nougat ROMs.
andy356 said:
Nope. When it seemed like most of the bugs were gone, and devs could then focus on it, Nougat code was dropped. Now there's again a mad rush to get the major bugs out on Nougat ROMs.
Click to expand...
Click to collapse
Yeah..
@andy356 Thanks for your precious feedback, it helps to understand the difference between the different ROMs. May I ask you to do an update version of your feedback since a lot a things have changed recently.
Thanks man!
@nicoula91 Right now I have a stable Marshmallow ROM that I want to stick to until Nougat ROMs become stable enough. When I'm ready to flash a new one I'll take that opportunity to flash all the Nougat ROMs and look at what's different. That sounds really troublesome, though.

Help to choose the best rom

Hello
Please advise which is the best ROM Android 8.1 or 9.0 at the moment, which has all the features enabled and no bug?
And as OTA is upgradeable, it does not need to be installed through recovery !
Well, one of the reasons that there are many roms, is that different people find different things "best".
Personally, I'm happy running Nitrogen Pie. Still, there are a few reports of bugs on all Pie roms:
- WiFi calling is missing
- encryption doesn't work
- SeLinux is turned off
If you want OTA updates, I think only Lineage has that. That is also a rom with weekly updates, whereas Nitrogen updates when Nitin feels like it, usually once a month. But Lineage has a bit fewer options to tweak things.
Generally, the Nexus 6 roms are all good. Unless you need very specific stuff, I don't think you'll be disappointed no matter what. And even if you are, changing is easy.

What is the best stable and working rom atm

Hi guys. I'm looking for refreshment to my g5s plus. Since I bought it I'm very satisfied with this device. I'm using old ground zero VALIDUS oreo 8.1 rom (version 1.5) and i was totally satisfied with its features. Like every Android, after 6months+ it started lagging sometimes. I've got no time to try every rom.
Can u share your opinion if u tried multiple roms?
From what I've read pie builds are not working perfectly yet,right? Are they any better from 8.1 though? Should I try any?
My main requirement is substratum to be working on the rom.
I'm considering picking latest build of oreo validus if Noone suggest anything.
Btw. My Google maps lost function to show the direction I'm facing(this triangle thing) . Any ideas? Tried basic solutions like reinstalling another versions. Can it be caused by rom itself? (unfortunately I don't remember when I lost that function).
I'm using a unofficial LineageOS ROM (Android Pie) Here's the link if you want to test it out, but yeah there's also This ROM, I tested Oreo, but not Pie

Blueooth bug fixed on pie, but...

Well, after this great result,I would have expected a good number of ROMs to be rushily updated with the new commit, but so far there has been no run to implement the fix... Not by lineage, not by resurrection remix and neither by bigger or smaller developers, to the point that I world be in trouble choosing a Bluetooth fixed pie rom f at the moment...
Are you as puzzled as I am?...
Try copying working libbt-vendor.so to your ROM.

Why so many roms with bugs?

Im using the Honor 3c as my main phone. Needed to upgrade to at least android 6. I tried several builds, the OctOs 6 (gps not working), the resurrection remix 7 (camera not working) and now im running lineage 6 hassan (bluetooth not working). Why are there so many roms when they all have bugs in basic functionality? Why not concentrate on one or two and put them into a fully working state? And a practical question - is it possible to replace the bluetooth libraries in the lineage6 with the libraries from the OctOs? A nice day to everyone, and thanks.

Categories

Resources