Let's hope it's precistant and Samsung finaly fixed the damn bug.
Fixed.
Let's hope it's precistant and Samsung finaly fixed the damn bug.
My bluetooth headset will connect to my phone, but when I make a call it will not connect. Any one else have this issue or know of a fix?
What is fixed? If your talking about the the silent notification bug it's not fixed in this build. Calk said Sammy thought it was fixed and is working on it now. I use Google+ a lot and I think it's one of the reasons why I get the bug. It happens without making a phone call and I think when I get a message from a huddle.
So after setting this up the market doesn't recognize my apps? Anyone else having this issue? On odex.
Also when flashing I noticed it copied, deleted and pushed data? That hasn't happened before to my recollection. Agat an I wrong?
Sent from my SPH-D710 using Tapatalk 2
I had the same issue with the last leak and this one... Ive had to go back three versions to get it to work again.My bluetooth headset will connect to my phone, but when I make a call it will not connect. Any one else have this issue or know of a fix?
There is an extra setting to toggle now once you pair and connect the Bluetooth. You now have the option it have calls only, media only, or both come through Bluetooth. I don't know why phone was off by default but it was
Sent from either ET4G or NS4G using Xparent Tapatalk 2
Just checked it.
I have 2 cellphones.
I did text myself and got notification sound.
Called my other cell. Picked up and hang up. Hit back buttom immediatly.
Text again and got notification sound again.
Let's hope it's precistant and Sprint finaly fixed the damn bug.
Not sure what agat is doing different but I went back and verified it 9 times.I didn't test it yet but I was referring to sfhub's original thread regarding fd19.
http://xdaforums.com/showpost.php?p=25082338&postcount=3
That makes more sense. I think it has always been easier for some phones to hit the bug than others.1 call. Hit back button = Got notification.
2 calls. Hit back button = Got notification
3 calls. Hit back button= Notification gone.
Pretty much I can say you really have to try to reproduce the bug.
In normal use it should be OK.
This would be good news if it sticks
Sent from my SPH-D710 using xda premium