Bluetooth isn't working on any ROM with any kernel combination! Not even the default kernel that comes up with the ROM. I'm talking about bluetooth file transfers, not connecting to speakers or anything. When I transfer/receive a file, it says 'Unfortunately com.android.bluetooth has stopped.' and then bluetooth is stuck on 'Turning on bluetooth...'. After rebooting, the bluetooth is already ON but still the same thing happens again when I use it. I can just connect and pair devices, can't share any file with them. Tried clearing data and cache of the Bluetooth Share app too, nothing helped.
It's strange because it works perfectly on OxygenOS with any kernel flashed on top of it. It's just perfect with Oxygen... ONLY! On all CM (never tried CM12S or COS12.1, I'm talking about CM12.1 only because I'm not gonna use others at all!) , Slim and other ROMs, the same problem occurs with all the kernels.
I thought the problem wouldn't be somewhere in the /system or /boot partitions and so I tried flashing OxygenOS and a CM12.1 ROM on top of it without booting into OxygenOS. Still, bluetooth doesn't work.
Help! I don't know where I'm wrong but I know that this is just happening with me and no other OPO user!
See the attachment for more information.
Got the culprit. Don't flash the Xperia Z2 Smart Social Camera on OnePlus One. I found it here . It breaks the bluetooth on any ROM. And on OxygenOS, the ROM will keep on saying 'Camera has stopped.' , so I didn't flash it.
Related
i updated CM11s and now bluetooth is not working anymore.
if i try to turn it on, it tries to activate bluetooth, then goes back off.
a full wipe didn't solved the problem, but it works with a clean rom (i tried mahdi, but i had to restore backup since monday i'm leaving for holidays and i don't have time to restore all i need on the mobile now).
i know i'm not giving many infos to have some help, but if you give me some directions i can try to fix it.
also, is it possible to reinstall CM11s with twrp or just through fastboot?
thanks!
I also have trouble with Bluetooth.
It tries to send file but either the app crashes or the file can't be sent.
Any info in that?
seems like noone has this kind of troubles
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Also having troubles with Bluetooth and my car-system since the 5Q update.
Before latest 5Q update everything works fine, but now neither of the devices can see the other one anymore
already deleted existing pairing in my car-system, but can't set up new pairing...
wondering if change of kernel can be a solution tho?
loth77 said:
i updated CM11s and now bluetooth is not working anymore.
if i try to turn it on, it tries to activate bluetooth, then goes back off.
a full wipe didn't solved the problem, but it works with a clean rom (i tried mahdi, but i had to restore backup since monday i'm leaving for holidays and i don't have time to restore all i need on the mobile now).
i know i'm not giving many infos to have some help, but if you give me some directions i can try to fix it.
also, is it possible to reinstall CM11s with twrp or just through fastboot?
thanks!
Click to expand...
Click to collapse
geri.st said:
I also have trouble with Bluetooth.
It tries to send file but either the app crashes or the file can't be sent.
Any info in that?
Click to expand...
Click to collapse
loth77 said:
seems like noone has this kind of troubles
Click to expand...
Click to collapse
nixnix33 said:
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Click to expand...
Click to collapse
J0ch3nK said:
Also having troubles with Bluetooth and my car-system since the 5Q update.
Before latest 5Q update everything works fine, but now neither of the devices can see the other one anymore
already deleted existing pairing in my car-system, but can't set up new pairing...
wondering if change of kernel can be a solution tho?
Click to expand...
Click to collapse
https://jira.cyanogenmod.org/browse/BACON-2822
nixnix33 said:
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Click to expand...
Click to collapse
this is still CM and not oxygen OS
Hey guys,
I have an annoying problem that prevents me to switch from TS CM13 to any newer roms.
I've tried RR, HnT LOS14, Cozzmy's LOS14 and last night even the newest TS LOS14.1
Every nougat rom doesn't work with the bluetooth phone profile on my Citroen DS4.
(The car's multimedia system is already at the last version)
Even stranger, bluetooth pairing works without any issue and media streaming profile works too. Only the phone profile says "there was a problem, try to reconnect".
Does any of you uses in-car BT with nougat roms? And maybe has a PSA group car?
Is there anything i can do? Even rebuilding kernel with legacy bt it's ok, if you give me some hints i can do it
Because on marshmallow roms everything works smoothly.
Thanks!
Try latest stable rom from miglobe and use DX mod (you ll find it here on xda). Its miui reinvinted
(everything work great cause its the official rom from xiaomi but its debloated and there is no thermal issues.Battery is real good too)
-dont know if it works with your car but if the official rom doesnt i think noone else will-
Thanks @nioonline. The problem is i will have to do the whole bootloader upgrade & downgrade again... but you're right, i guess the official rom it's the only way to be sure.
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
atharvvvg said:
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
Click to expand...
Click to collapse
Hello members,
Last week i'v also installed the latest lineageOS version ( 17.1, android 10) Gapps nano, on my Samsung A3 2017. With the TWRP tool., Nice ROM!
Unfortionally with the same issue as above, Samsung and other camera app's very often not working, need to reboot to fix that.
The flashlight does not work either then, and much more irritating BlueTooth not working anymore, my A3 always had perfect connection with my Parrot carkit CK3100.
I'v found in several forum some workarounds for this but these do not solve the issues long enough.
But the issues are also found in older releases from LineageOS.
Will there be a update for these mentioned 3 issues?
If not, i need to install another ROM which is not based on LineageOS.
The Cam and BT must work without any problems.
Thank you very much.
Frank.
Hey Guys,
I installed some custom ROMS to find out which one fits my needs best and I ended up using LineageOS 18. I configured it and everything works perfect. But then I paired my Bluetooth headset (without any problems) and tried to make a call. It confused me that I didn't hear anything and I looked at the phone, only to recognize that the BT-device ist not chosen as output. So I tried to choose it and I couldn't.
Long story short. Installed other ROMS (AOSP, HavocOS), same problem. Flashed stock via Odin. It works. Reflashed TWRP+vbmetaA11 and then LineageOS. Stopped working.
Do you have any ideas, what I can do?
Thanks in advance
Nobi83 said:
Hey Guys,
I installed some custom ROMS to find out which one fits my needs best and I ended up using LineageOS 18. I configured it and everything works perfect. But then I paired my Bluetooth headset (without any problems) and tried to make a call. It confused me that I didn't hear anything and I looked at the phone, only to recognize that the BT-device ist not chosen as output. So I tried to choose it and I couldn't.
Long story short. Installed other ROMS (AOSP, HavocOS), same problem. Flashed stock via Odin. It works. Reflashed TWRP+vbmetaA11 and then LineageOS. Stopped working.
Do you have any ideas, what I can do?
Thanks in advance
Click to expand...
Click to collapse
Goto phh treble settings > Samsung features > set esco transport > set that to 16
Hi, i recently got into booting gsi images on my phone since there aren't any custom roms developed specifically for my phone. (Samsung Galaxy A31)
I am also sideloading new versions of the rom as they come out with DSU sideloader.
Now i stumbled upon this very wierd thing that has happened.
I had android 12 pixelexperience gsi booted and i wanted to upgrade to android 13. So i first checked if it would boot and everything that i use would function by sideloading it with DSU sideloader. I concluded that everything that i use works fine including bluetooth audio playback to my earbuds.
So i flashed it as my main os by just flashing the system partition so i wouldn't lose any data.
It booted as the main os succesfully and all my apps and data were still in place and working, however bluetooth would connect to my earbuds but audio would still be playing through my phone speaker. When i booted the exact same version again that was still sideloaded, bluetooth would work normally.
I tried resetting Bluetooth through System -> Reset options and i tried deleting /data/misc/bluedroid/bt_config.conf and /data/misc/bluedroid/bt_config.bak from twrp and i tried clearing cache/dalvik from twrp but to no avail.
The phh settings and dev settings between the sideloaded rom and the normal rom are the exact same.
Is there some way to like reinstall bluetooth drivers? I am still pretty new to this.
I don't want to factory reset if it isn't needed. I do have a full nandroid (twrp) backup if i mess anything up.
Edit:
Just ran logcat and on the main rom it gives back an error that HAL isn't enabled while it doesn't have that error on the sideloaded rom.
2022-11-13 20:06:31.460 2044-2426/? E/bt_stack: [ERROR:a2dp_encoding_aidl.cc(353)] init: BluetoothAudio HAL is disabled
2022-11-13 20:06:31.520 1093-1093/? E/BTAudioHalDeviceProxyAIDL: init_session_type: device=0x80, session_type=A2DP_SOFTWARE_ENCODING_DATAPATH is not ready
2022-11-13 20:06:31.520 1093-1093/? E/BTAudioHalStream: adev_open_output_stream: cannot init HAL
added logcat to the main message