Related
Hi community,
I'm using my Samsung Galaxy S4 GT-I9505 with the cyanogenmod nightly build 11-20140830-NIGHTLY-jflte.
Works perfect except bluetooth and headset connection with my car.
Connection between S4 and a laptop (win7) works fine.
Car bluetooth is BMW E61 from 10/2006 without any modifications.
Symptoms: S4 and car find each other, PIN/Passphrase is transmitted correctly, car says connection established correctly, S4 says pairing not possible.
If I install build 11-20140724-NIGHTLY-jflte my S4 and car bluetooth works fine.
So what has been changed in the bluetooth development between these two versions?
Anyone with ideas?
Rainer
Got about the same problem with my Peugeot 508. Check the BMW website to see if your radio is compatible with the S4.
Maybe ask your garage for a software update.
Trancicted said:
Got about the same problem with my Peugeot 508. Check the BMW website to see if your radio is compatible with the S4.
Maybe ask your garage for a software update.
Click to expand...
Click to collapse
Thanks for reply, but that's not the solution.
An earlier build (11-20140724-NIGHTLY-jflte) works fine without any necessary updates from BMW.
Rainer.
rainer777 said:
Thanks for reply, but that's not the solution.
An earlier build (11-20140724-NIGHTLY-jflte) works fine without any necessary updates from BMW.
Rainer.
Click to expand...
Click to collapse
Then the problem is related to Cyanogenmod. Revert to a stable option or wait for a new release. Btw, you better report the bug to the developers over there. https://forums.oneplus.net/threads/...ture-requests-improvements-to-cyanogen.41858/
Hi,
I found the solution by myself and the help of cyanogenmod-forum
I deleted cache and data files under settings->apps->->all apps->bluetooth file sharing (I don't know the exact english name for it)
and I also have to use a 6 digit pin instead of a 4 digit pin.
Happy weekend!
Rainer
Hello fellow phone lovers.
Just found out why the Pokemon go plus accessory wouldn't connect to any ROM Ive ever used. Managed to get it to connect on my s4 with resurrection remix 6.0.1 ROM... You need to enable smart lock and add Bluetooth as a trusted device for it to connect properly
Your welcome.
Also forgot to add I'm using magisk v6 systemless and I had to make sure in super su that
*Enable su is ticked
*Enable su during boot is ticked
*Mount namespace separation is un-ticked ! (Main reason for not connecting)
*Trust system user is ticked
Pokemon plus Bluetooth device works flawlessly and connects as fast as it should where as before all this it would either, take ages to connect or not connect at all.
Hey all,
I have a redmi note 4G (global) running 4.4.4 (whoa, outdated as hell). It is running mi 66.55.11.00 which upon some research turns out to be a custom mi (and a bad one because it give u a popup ad on wifi every from minutes). I've checked, the phone is original.
I download the mi 7 images from mi's website and upon trying to update the phone, it failed (surprise surprise).
Can anyone please suggest another way to go about it.
Thanks in advance
Hi,
I have the same issue. Did you find a solution for this problem?
Thanks
This time i have a redmi 3s, its a great phone...
can anyone help me with some questions?
Can anyone tell me how did you for unlock your bootloader? or suggest me a secure method?
I'm looking for a post about fix the bad volume quality in camera videos, it will work with the V8.1.5.0 eu version?
Will the 4g/LTE work with MIUI V8.1.5.0 EU on American continent, specifically in colombia?
Anyone know any way for uninstall the unused google apps without get bootloop?
Thanks for all, and sorry for the inconvenience
1. Over Google a lot guides.
http://en.miui.com/thread-200858-1-1.html
If process stuck on 50% try again few times. Then flash China Dev rom, usually it helps.
2. Yes, patch for fixing bad recorded sound compatible with any rom for now.
3. http://willmyphonework.net
Chinese and International device versions have different bands support, Google it.
4. Bootloop only if you freeze Google Search app (Launcher3), other apps safe to disable.
Root: via MyAndroidTools disable all it's recievers and it won't start automatically.
Thanks for your quickly answer, you re always on fire
About 3 question, i own a redmi 3s working with 8.1.1.0 global estable, but i find that latest versión is 8.1.5.0 chinese and eu rom, i want know if i install the "eu" rom will i have problems with ril (data)
Thanks.
SEc510a said:
if i install the "eu" rom will i have problems with ril (data)
Click to expand...
Click to collapse
Rom version not affect bands / radio behaviour.
All incoming calls are Unknown number (no caller number visible) when VoLTE is activated. No issues with outgoing calls (that does make sense). When VoLTE is deactivated, everything works okay. Turning the feature on/off, also with enable/disable carrier check, does not solve anything. Multiple reboots done. Everything worked okay on my Mi Mix 2S with the same SIM-card yesterday, so I'm guessing it's a software issue.
MIUI Global 10.3.7 (PFJEUXM)
Anyone with the same issue? Is it working okay for anyone?
This used to happen to me on the note 5 AI.. And it got fixed after an update.
Hi, where did you find the VoLTE setting?
You probably have to disable carrier check first (*#*#86583#*#* and dial). Then you will have VoLTE option in call settings. Today was a new OTA but the issue is still present for me.
same here... Mi 9t activated volte and now unknown caller.
I wanted to try VOLTE since my calls are so bad I cant understand what callers are saying.
I have the same problem
K20 Pro
MIUI China 10.3.17
I have a MI 9T Global running version 10.3.11.0 PFJMIXM (and if I'm not mistaken the OP's version 10.3.7 (PFJEUXM) is not global but China based EU..)
My provider is T-Mobile Germany and caller-ID with VoLTE is working just fine.
Can it be that it's a problem with china based ROMs (like the EU version)?
Cheers Helmuth
Well, I managed to get in contact with distributer for Mi phones for our country, got their unit (mine was bought from Amazon ES) and reproduced the problem - I didn't pay attention to ROM version on their unit. They've logged it and said that they've forwarded the issue to the devs. Hopefully it'll get resolved sometime in the near future - for now the issue is the same on 10.3.12.0 (PFJEUXM).
I have same issue on global as eu. My provider checked everything and there was no misconfiguration on their side. so, reading these posts I think its phone related. CallerId outgoing is ok, incoming no name.
Mi 9T 128GB
Miui EU 10.3.15
Have the same issue on my Mi 9T Pro. Will this ever be fixed? If I go to Lineage or different Roms will that issue persist then too?
Planet X said:
Have the same issue on my Mi 9T Pro. Will this ever be fixed? If I go to Lineage or different Roms will that issue persist then too?
Click to expand...
Click to collapse
I fixed it using PDC , requires root
https://forum.xda-developers.com/poco-f1/how-to/guide-activate-vowifi-wlan-call-t3871263
I changed the profile to uk_vodafone and it worked great:good:
Activity manager in the playstore
I downloaded this app and in activity settings, modem config, i selected the vodafone nl modem and now it works for me.
VoWifi not working when open airplane mode and open wifi connection
Is that normal?
Im trying to do this on my k20pro but everytime i install the Qualcomm drivers i dont see anything in device manager?
Mooatreides said:
Im trying to do this on my k20pro but everytime i install the Qualcomm drivers i dont see anything in device manager?
Click to expand...
Click to collapse
For me it's the same, for some reason we can't enter diag mode I think. Tried a lot of stuff, all not working. E.g; https://xiaomifirmware.com/guides-and-tips/enter-diag-mode-backup-imei-using-qpst/
Which rom are you using?
Maksvr said:
For me it's the same, for some reason we can't enter diag mode I think. Tried a lot of stuff, all not working. E.g; https://xiaomifirmware.com/guides-and-tips/enter-diag-mode-backup-imei-using-qpst/
Which rom are you using?
Click to expand...
Click to collapse
Im on official Havok now but i tried on miui also(i have a chinese version).
My imei number is fine though?
Mooatreides said:
Im on official Havok now but i tried on miui also(i have a chinese version).
My imei number is fine though?
Click to expand...
Click to collapse
Sorry for the confusion, I meant the top part of the guide with three different methods to access DIAG Mode. For me the IMEI is also fine.
If you are using the miui rom you may also try this; https://forum.xda-developers.com/showpost.php?p=80159761&postcount=83 (specifically the two steps Additionnal fixing can be made using the app "Activity Manager" listed at the beginning), for this you need Activity Manager (also mentioned by Ratje_nl); https://forum.xda-developers.com/android/apps-games/app-activity-manager-hidden-activity-t3797985. This does not work on AOSP roms I think, I couldn't find the apks at least. I know this is all kind of messy, since there's little information we have to use a lot of different guides.
I am using Pixel Experience by the way.
Maksvr said:
Sorry for the confusion, I meant the top part of the guide with three different methods to access DIAG Mode. For me the IMEI is also fine.
If you are using the miui rom you may also try this; https://forum.xda-developers.com/showpost.php?p=80159761&postcount=83 (specifically the two steps Additionnal fixing can be made using the app "Activity Manager" listed at the beginning), for this you need Activity Manager (also mentioned by Ratje_nl); https://forum.xda-developers.com/android/apps-games/app-activity-manager-hidden-activity-t3797985. This does not work on AOSP roms I think, I couldn't find the apks at least. I know this is all kind of messy, since there's little information we have to use a lot of different guides.
I am using Pixel Experience by the way.
Click to expand...
Click to collapse
I just flashed miui 12 xiaomimeu ill try this nowwww
ADEL_ said:
I fixed it using PDC , requires root
https://forum.xda-developers.com/poco-f1/how-to/guide-activate-vowifi-wlan-call-t3871263
I changed the profile to uk_vodafone and it worked great:good:
Click to expand...
Click to collapse
So I also managed to get it working using this guide. I used Netherlands_Vodafone_LTE (I'm on the KPN network in The Netherlands), but I can confirm it is working.
Trick for me was to switch to a different rom, I am using Lineage OS instead of PE+, so you may give it a try as well if it still does not work.
Hello,
I am curious to see if anyone else had or still has this issue and if there is a fix for it.
Devices involved:
Phone - Samsung Galaxy S10 Plus (SM-G975F) Android Version: 10.0 Build Number G975FXXU4CTC9
Watch - Samsung Galaxy Watch 46mm (NO LTE)
Before rooting with Magisk I was able to pair the watch to the phone using the Galaxy Wearable App and use the watch with no problems. (And it still connects with my unrooted Xiaomi mi 9T)
After rooting my s10+ with Magisk (latest stable and also previous version) I was no longer able to pair the watch. It would start out fine by showing a matching passkey on both devices. I accept the code and they would begin to pair. Once the watch displays "Use phone to complete setup" is when the problems presented.
The Galaxy Wearable app will say its pairing the devices but shows nothing and keeps sending a notification saying it sees the watch and asks to connect or cancel. I tap connect and I get a white screen with a spinning circle. After 3-5 seconds the white screen goes away and 3-5 seconds later I am asked to connect the watch again.
If I go to Settings>Connections>Bluetooth (on the phone) I can see the watch is paired but the app will not complete setup. (I can pair to my car Bluetooth and JBL Xtreme speaker with no problems)
I am using Magisk Hide on the Galaxy Watch Plugin, Galaxy Wearable App, and Samsung Accessory Service but that hasn't helped. Nor does uninstalling and reinstalling Galaxy Wearable App.
Any thoughts?
Please help me, im messing around with this crap since 4 days. (I restored the phone about 20 times with odin an retryed again and again)
Could it be related to tripping knox through rooting (i.e. then some of the Samsung apps will not work e.g. Samsung Health)? I am unable to register S.Health and Wearable (on my rooted S7 edge) will not work.
However, working fine on non-rooted S10+.
Does this help?
https://forum.xda-developers.com/galaxy-s10/how-to/guide-samsung-health-knox-0x1non-root-t4075853
Boot into TWRP and flash @ianmacd's multidisabler
I have the same issue with not rooted s10+ and gear s3
Xenenon said:
Hello,
Exactly Same problem!!!!!
Stuck badly!!!
Any solution!!!!
Ahmed
Click to expand...
Click to collapse
xBrownieCodez said:
Boot into TWRP and flash @ianmacd's multidisabler
Click to expand...
Click to collapse
I did but the problem remains the same!!!
My Galaxy S3 Frontier works fine on Stock rooted + Lineage OS 17.1 .
there is a mgaisk module you can try called "Bluetooth Libary Patcher". Find it in Magisk -- Downloads -- and search for it there (just type bluetooth in search panel on top)
as i said, my watch works as it should.
and for Samsung helath: if youre rooted you just have to add one line in build.prop: ro.config.tima=1
lladwein said:
My Galaxy S3 Frontier works fine on Stock rooted + Lineage OS 17.1 .
there is a mgaisk module you can try called "Bluetooth Libary Patcher". Find it in Magisk -- Downloads -- and search for it there (just type bluetooth in search panel on top)
as i said, my watch works as it should.
and for Samsung helath: if youre rooted you just have to add one line in build.prop: ro.config.tima=1
Click to expand...
Click to collapse
oops! It did not work on mine S10+
Getting frustrated day by day!
I think the era of Rooted Devices is over!!!!!
Xenenon said:
Hello,
I am curious to see if anyone else had or still has this issue and if there is a fix for it.
Devices involved:
Phone - Samsung Galaxy S10 Plus (SM-G975F) Android Version: 10.0 Build Number G975FXXU4CTC9
Watch - Samsung Galaxy Watch 46mm (NO LTE)
Before rooting with Magisk I was able to pair the watch to the phone using the Galaxy Wearable App and use the watch with no problems. (And it still connects with my unrooted Xiaomi mi 9T)
After rooting my s10+ with Magisk (latest stable and also previous version) I was no longer able to pair the watch. It would start out fine by showing a matching passkey on both devices. I accept the code and they would begin to pair. Once the watch displays "Use phone to complete setup" is when the problems presented.
The Galaxy Wearable app will say its pairing the devices but shows nothing and keeps sending a notification saying it sees the watch and asks to connect or cancel. I tap connect and I get a white screen with a spinning circle. After 3-5 seconds the white screen goes away and 3-5 seconds later I am asked to connect the watch again.
If I go to Settings>Connections>Bluetooth (on the phone) I can see the watch is paired but the app will not complete setup. (I can pair to my car Bluetooth and JBL Xtreme speaker with no problems)
I am using Magisk Hide on the Galaxy Watch Plugin, Galaxy Wearable App, and Samsung Accessory Service but that hasn't helped. Nor does uninstalling and reinstalling Galaxy Wearable App.
Any thoughts?
Please help me, im messing around with this crap since 4 days. (I restored the phone about 20 times with odin an retryed again and again)
Click to expand...
Click to collapse
Anything you figure out!
Please do share with me!!!!
I flashed Beyonde Rom 6.7 it comes based on the latest April Patch.
This fixed all my problems
No Bugs yet with this rom
https://forum.xda-developers.com/ga...pment-exynos/rom-beyondrom-v6-0-t4017921/amp/
Flash with TWRP
Health works
Bcs of magisk all my banking works fine (Sparkasse germany)
I LOVE IT
GeekSiddiqi said:
Anything you figure out!
Please do share with me!!!!
Click to expand...
Click to collapse
Beyone Rom 6.7
If you have questions better go to reddit and ask for help
XDA is dead
any update on this issue ?
Xenenon said:
Beyone Rom 6.7
If you have questions better go to reddit and ask for help
XDA is dead
Click to expand...
Click to collapse
But do you lose the Samsung stock camera with this Rom? I have the same exact problem as you. When I was running the Evolution X custom Rom I could connect. But I wasn't happy with the camera that Rom provided. The stock camera on this phone is so amazing and one of the main reasons I bought the phone. I feel cheated when I have to give that up
nasheednashy said:
any update on this issue ?
Click to expand...
Click to collapse
I was having the exact same issue. I just activated magisk hide. And also installed the magisk module, Bluetooth library patcher. Now mine paired up first try. Not sure which helped or if it was a combination of both. But I'm paired up now.
Having same issue too. Tried changing props, tried multi disabler. Tried editing rules.
Now the app can enter but watch not connected
synite said:
Having same issue too. Tried changing props, tried multi disabler. Tried editing rules.
Now the app can enter but watch not connected
Click to expand...
Click to collapse
Did you found a way to connect them?
Inviato dal mio Pixel 3 utilizzando Tapatalk
Hi! Given a Samsung Galaxy Watch Active 2 (LTE) watch and a rooted Galaxy S10 (Android Q). Bluetooth pairing starts but does not end. Two Magisk modules id have been installed but I can't pair them. Is there anything you can bring together? So much for all the stupidity to read, but no answer or stupidity throughout. I can't install Viper4android on the same phone under Android 10. Magisk 21.4, but the 2.7 Viper doesn’t go up. It is installed by plugin, but not among applications. Can these be solved somehow? There was no problem under Android 9. Unfortunately, for the latest Android Q version, XEH version November 27, 2020, TWRP is not trable either. I download the right version, with Magisk, I boot into the AP with Odin, then start button, and odin closes immediately. Nothing goes on this ****ty Android Q. I am waiting for help together or separately! Thanks!
Any update on this issue?
I have problem pairing my Galaxy S21 Ultra and Galaxy Watch Active 2.
No pairing issues before rooting (stock firmware). After rooting using both stable Magisk V22 and Canary 22005, it stuck on Finalizing Pairing screen. I also noticed that the Bluetooth and Samsung accessory icons briefly shown on the notification bar (appear part of the screen) and then disappear.
I hope someone has solution to this.