4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
i had a similar problem but with my car's bluetooth. i cleared up my contact listed and the problem was resolved.
here is where i found the solution: http://forum.xda-developers.com/showthread.php?t=2646592&page=2
hope you come right.
Please help, after 4.4.2 with my note 2, bluetooth headset connection quality got crappy. I cant walk away from my phone more than 1 meter. Anyone experiencing this problem????
...
onurcandan said:
Please help, after 4.4.2 with my note 2, bluetooth headset connection quality got crappy. I cant walk away from my phone more than 1 meter. Anyone experiencing this problem????
Click to expand...
Click to collapse
I did not find a solution yet! You yeah?
Jackal107 said:
I did not find a solution yet! You yeah?
Click to expand...
Click to collapse
I have the same issue with my headset. Hope someone will find a solution soon.
I too have same problem!!
Whats wrong with samsung!!, sometime Wifi problem and sometime bluetooth.:silly::silly:
earlier I was on 4.1.2 and it was working good with my jabra clipper bluetooth headset, after updating to 4.4.2 it sucks!.
according to my observation,
The OS is trying to save battery by limiting the bluetooth signal strength!, and the same problem with wifi also.:silly:
Looking for a workaround. If i find any will post for sure.
I have the same issue with my Note 2 after update to 4.4.2..
It seems to be a distance problem with my headset, every distance more than 50 cm creates
sound break up´s .. In my car the phone has a fixed place, it happens too, but not this much.
Maybe it is caused by a lower power managment for BT after update ?!
Found some others having the same issue e.g. here
http://androidforums.com/samsung-ga...nge-extremely-dropped-after-4-4-2-update.html
Frank67 said:
I have the same issue with my Note 2 after update to 4.4.2..
Found some others having the same issue e.g. here
http://androidforums.com/samsung-ga...nge-extremely-dropped-after-4-4-2-update.html
Click to expand...
Click to collapse
Yepp, I know that threat. But on my N7100 nothing works. In the meantime I'm on Paranoid ROM with 4.4.4 and it's a little better, but not much.
Frank67 said:
I have the same issue with my Note 2 after update to 4.4.2..
It seems to be a distance problem with my headset, every distance more than 50 cm creates
sound break up´s .. In my car the phone has a fixed place, it happens too, but not this much.
Maybe it is caused by a lower power managment for BT after update ?!
Click to expand...
Click to collapse
Hi
and have the same problem with the bluetooth, the phone in my pocket, Samsung headphones on the head and lose the music signal, conclusion .... android version
Before to upgrade I had 4.3 and works very well and now I upgraded to 4.4.2 my Note 2 with Phantom_V7.0 and work awesome but has a minus....... the bluetooth signal gets lost and it's not about the power,for ex i have battery with 4200 mAh
I will continue to keep looking this problem and I will return
There is no way to get better connection. The only way is using a 4.3 ROM
Seems like the problem is solved.
Hey guys!
It seems to me I’ve found the solution!
But firstly, a few words about the problems I’ve got…
I have Samsung Galaxy Note 2 and, when I decided to replace my old Plantronics Discovery 975 with their Voyager Edge, it had installed Android 4.3.
Both events, start using the new Bluetooth devise and upgrading to KitKat (4.4.2) occurred almost simultaneously, so it was pretty difficult to recognize what was the source of the problems that I run into – hardware/firmware issues of Voyager Edge or KitKat’s quirks. The problems were the following:
- Poor Bluetooth connection that resulted in distorted sound (not always, but often) thru the headset.
- Regularly losing the ability to use various Edge’s features, such as calling back to the last number, checking the battery status, recognizing who's calling, etc.
- Note’s battery drained badly – instead of 50-60% left at the end of the day, I got 10%...
I spoke several times with Plantronics support, but they ended advising me to replace the headset. I have neither found the specific solution in the internet and it was even reported that the factory reset would hardly help. So, that was almost the dead-end. But there was one pretty weird solution that helped to some people – deleting the duplicates in the phone’s contact list. But, since I had NO duplicates, it didn’t seem to be helpful. But then, I noticed one very strange detail – during the moments when Edge worked properly it correctly pronounced the names from my phone book, even tho some of them were quite unusual for English speaking "robot". All of them, but one – my mother’s record, which was a simple “Mom”, but when she called me, the Edge’s notification was definitely not “calling from mom”…
So, I just renamed “mom” to “mother”!
Guys, can you believe that, but ALL the problems (both phone’s and headset’s) have just gone! I’ve been using it for almost a week already and it’s OK. So, you may check your contact list, whether it sounds correctly.
Well, one issue left – weird/funny bug of the Edge’s firmware – start playing music when you take it off the cradle. (2 latest firmware updates didn’t cure that…). I just long press the voice button on the Edge to pause it. Not a big deal, to be honest.
Oh, just one last note – since Voyager Edge cannot be rebooted you can do the following if/when you neither hear the music (!), nor the report that the headset is connected when you take it off the cradle. Just long press the Call button on the headset (in my case it runs Note’s S-voice) and then everything works just fine. (Checked twice.)
Hope that this will help you too.
Cheers,
Max
Hi Max,
nice story, but I can't belive that this entry or change of entry will make the BT signal better.
cheers
Harvey
harvey186 said:
Hi Max,
nice story, but I can't belive that this entry or change of entry will make the BT signal better.
cheers
Harvey
Click to expand...
Click to collapse
Hi Harvey,
Absolutely the same reaction was mine, when I read the comment by dawolverune (see page 1 of this thread). How deleting duplicate contacts might help…
Well, if assume that I tell the truth (and I actually do! ), then the solution may be explained in 2 ways: a) logical – I’ve been hammering with all this stuff for almost a week and nothing helped until I renamed that single contact and then, it just start working and b) technical – since Voyager Edge pronounced the wrong name it means that it took it from somewhere, but definitely from the wrong place and this might require extra “efforts” from the Bluetooth receiver/transmitter, etc. This indeed may result in abnormal behavior of the devise and “eating” the battery. If re-phrase the title of S. Coppola’s movie – here we had “Lost in Bluetooth” case.
Cheers,
Max
hack fix
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
Am guessing someone has a fix to this issue by now, if so let everyone know
if not i just tried a hack that seems to work. when facing crackling/distortion of audio on Note2 just switch on the WiFi hotspot and range seems to improve
hope it helps......plzz educate about downsides of this hack
ivan_109 said:
Am guessing someone has a fix to this issue by now, if so let everyone know
if not i just tried a hack that seems to work. when facing crackling/distortion of audio on Note2 just switch on the WiFi hotspot and range seems to improve
hope it helps......plzz educate about downsides of this hack
Click to expand...
Click to collapse
cool, it seems, that this hack is working
Thx
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
I have the Exact Problem, and no one seems to have a solution to this. Did u find any by any chance ??
Thanks
SOLUTION OF BLUETOOTH DROPPING after 4.4.2 update
Yo !
I found the solution. No one has to downgrade Note 2 (N7100) to Jelly-bean in order to fix the Bluetooth range and WiFi dropping issue.
The fault is with the latest update from Samsung itself, May be it is a tactic to make people shift to the newer phones.(who knows) !
Anyway the solution to this problem is to Flash it with Odin it a previous release of 4.4.2.
In my case which is from the INU (India) region the release of August that is 29.08.2014 is a faulty update.
So i downloaded the older one and flashed it.. then everything worked perfectly as if the phone was new
Here is how to do it:- [BACKUP YOUR PHONE WITH KIES 3]
1. Check your version from *#1234#, Compare the version with Near August version of your Region. If it is same you better change it to get a way better performance.
2. Look up the earlier ROM version released from samsung-updated .com , http://samsung-updates.com/device/?id=GT-N7100&details=Galaxy_Note_2__International , I personally flashed it with the first version of Kit-Kat that came for note 2 in INU region. on the 8th April (08.04.2014).
3. Download ODIN http://www.mediafire.com/download/mbvtjub21ehsxrl/Note+2+Odin.zip
4. Install Samsung USB drivers http://www.mediafire.com/download/9qaqkld45387lzi/Skyrocket_GSII_ADB_Drivers.zip
[IF THE LINKS DON'T WORK then GOOGLE THEM AND INSTALL]
5. Power off your Samsung Note 2.
6. Hold Volume Down, Power, and Home Buttons at the same time. You will enter the ODIN DOWNLOAD MODE on your phone.
7. Press Volume up to Continue. It will Show "Downloading" "do not power off"
8. Connect your device to the PC where you have put ODIN and the md5 file (Firmware you want to flash with)
9. It will show connected to your device name on the top left of ODIN which means that it recognizes your device.
Click on PDA and select the firmware that u downloaded to flash Note 2 with.
It will lag for a few seconds but let it take its time.
When it is done. [Refer Image attached]
10. Press Start [It will take around 5 minutes, 3 minutes give or take]
11. It will Automatically Reboot your phone. Do not disconnect the USB cable.
After the boot is Complete ODIN will show a PASS on the left Side. Which means that the Flashing Process has been a Success.
If it shows fail then Repeat the process from STEP 6 all the way till STEP 11.
{ RECOVERY STEPS:- this will wipe all your data}
[Also, If device is Stuck at setup connection or on any other process, then disconnect your Note 2 from PC, close Odin, remove phone’s battery and put it back inside AFTER 5 seconds, press Volume up, Home key and Power key at the same time, When the Logo comes then Leave the Power button but keep pressing the other 2. Wait for it to show MANUAL MODE. Select Wide Data and Factory reset with Volume down and press power to continue, Then again wipe Cache.
Select Reboot . Now it should work perfectly.
CAUTION :- DO THIS AT UR OWN RISK.
Is this problem appears in official update? Want to update, but dont want any probs)
Yes the problem is with the official update. Better not update it till there is another update of it available.
I'm thinking this might have to do with Samsung dropping the Bluetooth version from 4.0 back to 2.0. I have no idea why they would do that but I've been wondering why my phone listed version 2.0 when the specs for this phone always said version 4.0. As you can see my debug screen shows it as version 2 and not 4.0. My Edge shows 4.0 on that same screen. I can't recall if older builds for the Note 2 had 4.0 listed but I believe they did and kitkat lowered it. Guess that's their trick to get people to upgrade, break things on our phones quietly...
Sent from my SM-N915P using XDA Free mobile app
Has anyone been able to get Android Auto working on this phone? Every time I plug in my phone to my car nothing happens on my phones end but on the cars dashboard it displays the message "This device doesn't support media function" I have the Android Auto app installed and launched and ive tried multiple roms:
Roms Ive Tried:
Jasminerom
Cyanogenmod
Euphoria
Paranoid Android
I have also made sure its set to MTP when connecting via usb and ive toggled USB debugging on and off on all these roms and still the same message!!!
Anyone else experiencing these issues or have been able to get Android Auto to work with vs985?!
Please does anyone have a fix for this?! This is on a 2015 Sonata btw.... Im also using the original usb cable that came with the phone... any help would be appreciated :fingers-crossed:
Edit: Whelp looks like Verizon strikes again... I just found this:
LG G3
"Android Auto is not currently supported in the U.S. on the LG G3 for Verizon Wireless customers. Google is working with LG on compatibility and will announce an update when the issue is resolved."
Verizon Auto incoming. Why else would Big Red cripple a function like that? They don't like completion like Apple so they do all possible to kill it.
PiousInquisitor said:
Verizon Auto incoming. Why else would Big Red cripple a function like that? They don't like completion like Apple so they do all possible to kill it.
Click to expand...
Click to collapse
Right?! Seriously though this is a huge disappointment... its literally the 1 of 3 phones that doesnt work with it... and it is only transferring data via USB.... someone on XDA must have an idea on how to get this to work properly...
Had this issue on my Note 3. (several diff roms)
Flashed it back to stock. (no root)
Working perfect now.
Over all I'm very happy with MM on Z5 Compact. But I've got some issues with my Bluetooth since the update.
I've got a DVD800 in an Opel. Before the update it worked mostly. Once a month I had the issue, that I had to toggle bluetooth, because the connection ran into a bad state.
But since the update I've got regulary disconnects. Special here: I don't have to toggle Bluetooth on either site.. Only try to force a reconnect and mostly it works.
But on my 30 minute drive to work, it disconnects around every 2-15 minutes.
Did anyone discover such things?
Is it possible that some Battery Optimization -Feautres makes some problem here? energy saver (doze) is not active.
Have to add here:
I'm on:
- E5823_Customized CH_1298-7257_32.1.A.1.163_R2C with my 1298-1220 device
- Installed AndroPlus v20
- Installed TWRP 3 from xy.03.2016
- Installed SuperSu
Now I'm testing on
- Installed AndroPlus v21
- Installed TWRP 3 from 21.03.2016
I'm on Customized Nordic and I have not experienced any disconnects with my BT earphones (with phone in pants) nor with my BT speakers. Had MM since it was released on XDA. Doze active.
Yep. Here's a copy/paste from my post in the BIG Z5 Marshmallow thread:
I've been getting the same issue as you. Just now, I was playing through my bluetooth speakers and suddenly the sound completely cuts out. I go and try to toggle the volume up and down and no volume indicator shows up. After about half a minute to a minute the volume indicator appears and the sound comes back. Very strange.
Has anyone noticed a very long delay in bluetooth auto connecting? When my Z3c, when I enter my car, the bluetooth hooks up immediately, within 10 seconds of being in my car. With my Z5c it's a hit or a miss. Sometimes, it won't connect for up to 5 minutes and I'd have to go into my settings and manual connect.
Hopefully, the April update will work out all the kinks.
Click to expand...
Click to collapse
Yeah, I have a fitness tracker - a Basis Peak - that will not connect to the Z5C since the Marshmallow update. The phone can see the watch (and vice versa) but they just can establish a working connection.
Update for today: I didn't have a disconnect within the 20 minute drive. But have to monitor a few days further
Unfortunately I changed more than one thing. So I don't know which one changed the behaviour.
now with
- Installed AndroPlus v21
- Installed TWRP 3 from 21.03.2016 (not really think, thats comming from here... but I changed that too)
- And Battery Optimization disabled for (NOT DOZE)
Bluetooth-Sharing
Bluetooth-MIDI-Service (not really think, thats comming from here but...)
Anyone have an ETA for 6.01? Looks like that's the fix I'm going to need.
milesg said:
Anyone have an ETA for 6.01? Looks like that's the fix I'm going to need.
Click to expand...
Click to collapse
Probably first week of May.
youvedone said:
Update for today: I didn't have a disconnect within the 20 minute drive. But have to monitor a few days further
Unfortunately I changed more than one thing. So I don't know which one changed the behaviour.
now with
- Installed AndroPlus v21
- Installed TWRP 3 from 21.03.2016 (not really think, thats comming from here... but I changed that too)
- And Battery Optimization disabled for (NOT DOZE)
Bluetooth-Sharing
Bluetooth-MIDI-Service (not really think, thats comming from here but...)
Click to expand...
Click to collapse
Unfortunately it's better..... but not good at all... but I can reconnect any time, when it disconnects.
This is H0_EEA firmware(OS01) not H0(OS00) firmware
Here is file
- update notes (same as global mq1 firmware's update notes)
1. Update Google Security Patch to 2020-06-05
2. Update brand element related content
3. Updated bootup animation
4. Updated SharkSpace, GamerStudio
5. Addressed mic malfunction issue
6. Optimized camera auto focus at close range
Thanks you bro.
I just updated it anybody have any problems with it so far?
Is there one for BS2 Pro "DLT-H0"?
2dogs16 said:
I just updated it anybody have any problems with it so far?
Click to expand...
Click to collapse
Yea I do. After I installed it my bluetooth devices keep disconnecting regulary. If I don't restart the phone I can't even connect some of my devices like my headphones because it rapidly connects and disconnects. My Galaxy watch also gets disconnected randomly. Besides from that not really.
The fingerprint sensor got faster though!
Bit I STILL can't use smart unlock via bluetooth devices. The list doesn't get populated so I have to use fingerprint all the time
Also YouTube Vanced gets killed randomly if I use background play. Already checked power saving options.
Black Shark 2 pro new update
I'm still having the strange phone problems calls can't hear me
Looking at the official BS2 forums the closing of background apps regardless of the power saving options is a new bug since I am also affected. My Galaxy watch keeps getting disconnected probably due to the accessory service being closed and any background music or video app gets closed as well.
You can't reach the official forums anymore! I wonder why ?
I think this phone global developer bad. Now they deleted their own forum. :crying:
Hello,
since I purchased my Redmi Note 10 (which came with MIUI Global 13.0.7, Android 12) I experienced some bluetooth issues which I hadn't with my previous phone (Redmi Note 7 with Android 10).
E.g.: I'm wearing a device (Dexcom G6) which sends every 5 minutes my blood glucose value to my phone via bluetooth; if I'm away for a while, the device doesn't reconnect automatically but asks for pairing again... and until I confirm I don't get new values. This could happen several times per day.
I've read a lot of people complaining about this behaviour (that seems related to Android 12); several workaround are suggested but nothing really solved the problem. I can provide more details if needed
Btw, the connection with Miband 6 is unstable too.
These issues are quite annoying and, as I said, I didn't experience them with my previous phone, so I'm wondering if switching to a custom rom can help me on this!
Hello,
Changing ROM can help, if the problem is software and related to MIUI for example.
As a last resort, I think it doesn't cost anything to try custom ROM, it is always possible to go back to the initial MIUI, if necessary.
It would be interesting to list the attempts you have already made to avoid making unnecessary suggestions.
If you haven't already done so, I'm thinking in particular of disabling battery optimization for the application used with Bluetooth.
spider1163 said:
It would be interesting to list the attempts you have already made to avoid making unnecessary suggestions.
If you haven't already done so, I'm thinking in particular of disabling battery optimization for the application used with Bluetooth.
Click to expand...
Click to collapse
Thanks for your reply!
Bascially, there are several apps well known in the diabetics community that can be used to read values from the device: xDrip+, Dexcom etc.
They all worked flawlessy on my old phone but with the Redmi Note 10:
- xDrip+ disconnects for 20 minutes after each reading (it should be 5)
- Dexcom asks for BT pairing now and then, sometimes even when I'm near my phone
Of course I disabled battery optimization.
These issues have been reported by users since Android 12 and not only on Redmi phones...
I tried to follow some suggestions:
- disable BT battery optimization: this was possible on Redmi Note 7 but I can't find such option on my Redmi Note 10;
- use apps like "Blue Car Tethering" that force BT tethering with paired devices; this improves the situation but doesn't solve it (with Dexcom I get fewer BT pairing requests, and with xDrip+ I get readings every 10 minutes);
- on "developer options": change "ACRCP Bluetooth" and "MAP Bluetooth" versions, but it didn't work even trying all possible combinations.
I'm experiencing problems with my Miband 6 too, that sometimes disconnects from its app; this didn't happen on my previos phone but it could be related to some bugs with the app itself.
My feeling is that, generally speaking, BT is more unstable.
Important: there are also users claiming not having issues with Android 12 at all, so maybe they are related to some manifacturer customizations; that's why I'm wondering if using a custom rom can help.
Sorry if I was too long but I tried to give more details.