Related
Yesterday I bought a used Galaxy Note from a guy on Craigslist. Everything works great except Bluetooth. I usually pair my phone with 3 different devices. Rocketfish headphones, Creative D200 speaker, and a Belkin bluetooth receiver connected to my home theater. All of my previous and other current devices have no problems streaming to these devices. my new Note pairs with each of these devices and connects, then starts streaming, then no music or sounds can be heard after a few seconds. It still shows connected. I have tried everything unpairing, repairing, rebooting. i even upgraded to ICS and get the same problem except after it streams for a few secs it disconnects now and shows paired and will not connect again until I reboot. Has anyone else had problems like this? By the way im tring to stream Iheartradio using a wifi connection. Any help you guys can give me would be greatly appreciated
Thanks.
[email protected] said:
Yesterday I bought a used Galaxy Note from a guy on Craigslist. Everything works great except Bluetooth. I usually pair my phone with 3 different devices. Rocketfish headphones, Creative D200 speaker, and a Belkin bluetooth receiver connected to my home theater. All of my previous and other current devices have no problems streaming to these devices. my new Note pairs with each of these devices and connects, then starts streaming, then no music or sounds can be heard after a few seconds. It still shows connected. I have tried everything unpairing, repairing, rebooting. i even upgraded to ICS and get the same problem except after it streams for a few secs it disconnects now and shows paired and will not connect again until I reboot. Has anyone else had problems like this? By the way im tring to stream Iheartradio using a wifi connection. Any help you guys can give me would be greatly appreciated
Thanks.
Click to expand...
Click to collapse
Im sure its a hardware issue.
Sent from my GT-N7000 using XDA Premium App
Do you think AT&T would replace my phone under the one year warranty?
sahilarora2003 said:
Im sure its a hardware issue.
Sent from my GT-N7000 using XDA Premium App
Click to expand...
Click to collapse
you dont think once factory reset worth to try? (Though it is much complicated now by flashing ics)
Sent from my GT-N7000 using xda premium
dr.ketan said:
you dont think once factory reset worth to try? (Though it is much complicated now by flashing ics)
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks but I have given that a try too.
Oh that escaped from my vision, or may you hav not mentioned in op.
Anyway then best.way is to give it to service center.
Sent from my GT-N7000 using xda premium
After further testing I have had limited success streaming music that is stored on my phone to the bluetooth devices. they stream for at least 45 minutes. Its just when I try to stream Iheart, tunein,winamp shoutcast,ect through wifi or 4G I have this problem. this is strange. I wish I could find some other people that claim they stream online media to bluetooth.
@OP
any chance using or flashing a custom kernel would do the trick on your current issue?
Whatever you do never factory reset or data wipe on stock ICS.
Sent from my GT-N7000 using XDA Premium HD app
[email protected] said:
Do you think AT&T would replace my phone under the one year warranty?
Click to expand...
Click to collapse
Either you are in the wrong forum, or no. The ATT Note is a completely different device.
Sent from my GT-N7000 using Tapatalk 2
Yes I do believe i am in the wrong forum. I should have posted in the AT&T version of the Galaxy Note forum. One last question. Do any of you stream online media through your galaxy note to bluetooth devices?
I haven't seen anybody create a thread about this, but has anyone not been able to enable their bluetooth without rebooting their device? I'll hit the bluetooth toggle in the settings and it just shots off right away. I'm not exactly sure what's causing it but I'm hoping that it's just a software issue since I use A2DP to listen to music.
EDIT: I performed a Factory Reset, I'll let you guys know if this problem still occurs.
FatalityBoyZahy said:
I haven't seen anybody create a thread about this, but has anyone not been able to enable their bluetooth without rebooting their device? I'll hit the bluetooth toggle in the settings and it just shots off right away. I'm not exactly sure what's causing it but I'm hoping that it's just a software issue since I use A2DP to listen to music.
Click to expand...
Click to collapse
Yeah same here, had that a while ago.. it happened after I used bluetooth for a while then switched it off, and then when I tried switching it on again after about 10-15 mins it wouldnt switch on. Had to reboot before it worked again..
Hope there's a software fix soon!
mohit1234 said:
Yeah same here, had that a while ago.. it happened after I used bluetooth for a while then switched it off, and then when I tried switching it on again after about 10-15 mins it wouldnt switch on. Had to reboot before it worked again..
Hope there's a software fix soon!
Click to expand...
Click to collapse
It's good to know that I'm not the only one.
Sent from my Nexus 4 using xda premium
Bump
This happened to me a few times with my galaxy nexus. Haven't had an issue with the N4 yet.
Sent from my Nexus 4
El Daddy said:
This happened to me a few times with my galaxy nexus. Haven't had an issue with the N4 yet.
Sent from my Nexus 4
Click to expand...
Click to collapse
Would you recommend a factory reset?
I've had this happen occasionally on my N4, have to reboot in order to enable BT again. I'm guessing a software bug to be fixed in a future update. I doubt a factory reset will cure the problem.
Had this happen yesterday. I figured it was the nfc tag getting triggered too many times in the car mount? Simple reboot fixed it though.
hfuizo said:
I've had this happen occasionally on my N4, have to reboot in order to enable BT again. I'm guessing a software bug to be fixed in a future update. I doubt a factory reset will cure the problem.
Click to expand...
Click to collapse
frigidazzi said:
Had this happen yesterday. I figured it was the nfc tag getting triggered too many times in the car mount? Simple reboot fixed it though.
Click to expand...
Click to collapse
I'm really hoping that this is just a software issue. I really don't want to RMA again. I actually have a Nexus 4 with a perfect screen.
Boooo
Sent from my Nexus 4 using xda premium
FatalityBoyZahy said:
Boooo
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I just experienced this problem as well. It was really annoying. Even toggling airplane mode wouldn't even work. On reboot, my bluetooth was already on though.
yokuyuki said:
I just experienced this problem as well. It was really annoying. Even toggling airplane mode wouldn't even work. On reboot, my bluetooth was already on though.
Click to expand...
Click to collapse
It's looking like a software problem. I wonder if people are experiencing this on CM10.
Sent from my Nexus 4 using xda premium
yokuyuki said:
I just experienced this problem as well. It was really annoying. Even toggling airplane mode wouldn't even work. On reboot, my bluetooth was already on though.
Click to expand...
Click to collapse
I had this exact problem. Only happened once so far.
Edit: happened again today.
shilent said:
I had this exact problem. Only happened once so far.
Click to expand...
Click to collapse
It's kind of annoying when I'm all motivated for a run and then my headphones won't connect. -_-
Sent from my Nexus 4 using xda premium
Nopes !
Bluetooth works like a charm man !
This is really starting to bother me -__-
Sent from my Nexus 4 using xda premium
happens to me to. BT won't come on and need to reboot phone to fix issue.
i only use BT while driving as my music streams from the N4.
It's prob a software bug. i wonder if there's a service that we could kill that may get it to work again with rebooting.
Same here. Reboot fixes the issue for me.
Sent from my Nexus 4 using xda app-developers app
First issue with my N4 I've experienced is this - happened just now and came looking to see if I was the only one. Normally I have alogcat installed, but hadn't gotten around to it yet. Next time it happens I'll fire it up and see if there's any useful messages or not If I get any info from it I'll share it here.
Reapman said:
First issue with my N4 I've experienced is this - happened just now and came looking to see if I was the only one. Normally I have alogcat installed, but hadn't gotten around to it yet. Next time it happens I'll fire it up and see if there's any useful messages or not If I get any info from it I'll share it here.
Click to expand...
Click to collapse
Thanks man. If it doesn't turn out to be a software issue, I'm going to RMA.
Sent from my Nexus 4 using xda premium
I looked for a solution everywhere but all i got was to change the phone. I have the no audio in-call problem. There is a way to fix it wothout changing the phone? Any help would be appreciate. Sorry for bad english.
ScimmiaUbuntu said:
I looked for a solution everywhere but all i got was to change the phone. I have the no audio in-call problem. There is a way to fix it wothout changing the phone? Any help would be appreciate. Sorry for bad english.
Click to expand...
Click to collapse
Are you running 4.2.2 with a non .48 radio? AKA did you enable LTE on 4.2.2?
i don't know and i don't think so, i was on PA 4.2.2 when i tried 0.47, 0.33, 0.27(?), i tried almost all modems, then i tried stock 4.2.1 (i bought my nexus 4 with 4.2.2), then i tried CM RC1 but never worked. I hope i can make it work without changing it. Thanks for the reply.
up
ScimmiaUbuntu said:
up
Click to expand...
Click to collapse
If you did all that then I guess it is a hardware issue.
First for the sake of trying give it a good shake ,cause the earpiece might have slipped for less than a mm.
If that doesn't help then you will have to either RMA or open the device and perform an earpiece exchange.
Sent from my Nexus 4 using xda premium
mariosraptor said:
If you did all that then I guess it is a hardware issue.
First for the sake of trying give it a good shake ,cause the earpiece might have slipped for less than a mm.
If that doesn't help then you will have to either RMA or open the device and perform an earpiece exchange.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
The problem is that I can make internet calls, so the microphone and the speaker both work. Which part have i to change?
ScimmiaUbuntu said:
The problem is that I can make internet calls, so the microphone and the speaker both work. Which part have i to change?
Click to expand...
Click to collapse
You have to change the earpiece
http://stellatech.com/lg-e960-nexus-4-ear-speaker,a,en,814613.html
Sent from my Nexus 4 using xda premium
mariosraptor said:
You have to change the earpiece
http://stellatech.com/lg-e960-nexus-4-ear-speaker,a,en,814613.html
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thw fact is that my speacker works well in internet call (Tango, skype, etc) so will surely that solve my problem? or will it work only in internet calls again?
ScimmiaUbuntu said:
Thw fact is that my speacker works well in internet call (Tango, skype, etc) so will surely that solve my problem? or will it work only in internet calls again?
Click to expand...
Click to collapse
Before you go swapping hardware I suggest you flash the full 4.2.2 stock image from Google. Bootloader, radio, everything. Then, check if the problem persists.
Sent from my Nexus 7 using Tapatalk 4 Beta
El Daddy said:
Before you go swapping hardware I suggest you flash the full 4.2.2 stock image from Google. Bootloader, radio, everything. Then, check if the problem persists.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I bought the phone with Google's pure 4.2.2, tried also original 4.2.1. Same question as before? Is it possible that the problem will persist?
Its highly unlikely it's a hardware problem if you have audio with internet calling. As I said before, flash the full stock image including an wipe with fastboot.
Sent from my Nexus 7 using Tapatalk 4 Beta
ScimmiaUbuntu said:
Thw fact is that my speacker works well in internet call (Tango, skype, etc) so will surely that solve my problem? or will it work only in internet calls again?
Click to expand...
Click to collapse
The speaker is other spare part and the ear piece is another one.
The main speaker how's with the antenna.
Sent from my Nexus 4 using xda premium
El Daddy said:
Before you go swapping hardware I suggest you flash the full 4.2.2 stock image from Google. Bootloader, radio, everything. Then, check if the problem persists.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
+1
RMA if you can before trying to change any hardware yourself, but this does sound like an earpiece problem
I'll try 4.2.2 stock. I'll keep you updated.
I had the same problem but it was fixed after I flashed the latest radio.
http://forum.xda-developers.com/showthread.php?t=2147194
Nothing worked (flashing/factory reset/downgrading) so I returned back the phone. The new one has no problem.
I had the same problem.. everything working fine in all apps except for normal calls. Even after resetting to stock Google image. After some digging I found the application Soundabout. It has an option to disable the check if a headphones has been inserted or not. After ticking the checkbox to disable the headphone check I could call again with the earpiece.
Funny thing tough, after reflasing my phone with CM 10.1 it still worked. Even on the stock Google image after re-enabling the headphones check I was able to make calls again with the earpiece. Really really strange problem.
You can find the app here: https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix&hl=nl
Altough you already replaced your phone it might be usefull for other people with the same problem.
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
nader9999 said:
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
Click to expand...
Click to collapse
Hello, I have been experiencing moments of "freezing" or unresponsiveness as well.
For me, it seemed to be due to chrome or using power saving mode. (People in another forum were blaming their droid maxxs freezing problem on chrome) I disabled chrome and disabled power saving mode.
Then I started using opera. I experienced another moment of unresponsiveness using opera without the power saving mode.
I was thinking back to the first times that it happened and it seemed to be paired to the wifi download and upload symbol being active in upload and download activity.
I know that correlation does not mean causation, but I think it is worth exploring if the network activity is causing it to somehow hang.
This bizzar occurance made me perform a factory wipe leading to another round of issues involving processing err_0000, but that is another story; sadly, it didn't even fix the issue.
OP, are you still experiencing the moments of unresponsiveness? If you are, have you noticed the events that are correlated with the event?
Has anybody else experienced this or found a remedy?
It could be one of the apps from the play store that is not playing nice with kitkat, but due to the multitude of other issues, I'd say it is a kitkat or touchwiz flaw.
Thanks for any help.
Lago
nader9999 said:
Hi everyone
So I update my N9005 to the official polish kitkat firmware and I've been experiencing episodes of screen unresponsiveness very often. Anybody else has this problem? Anybody managed to fix it?
P.S I'm aware of the counterfeit/unoriginal s-view flip covers issue which I'm having as well but the thread isn't about it.
Hope someone has a solution.
Click to expand...
Click to collapse
I had an issue with screen not responding sometimes .....I figured out it was due to the flip case (original by Samsung). Although lately I haven't experienced that either.
Try using the original non flip case and see if you still have the issue.
Sent from my SM-N9005 using XDA Premium 4 mobile app
pac-mannan said:
Try using the original non flip case and see if you still have the issue.
Click to expand...
Click to collapse
I have never had a s-view flip case on mine. I use holster iblason case that has no interaction with the screen.
This only started for me once I upgraded to kitkat.
Sent from my SM-N900 using xda app-developers app
lagoboss said:
I have never had a s-view flip case on mine. I use holster iblason case that has no interaction with the screen.
This only started for me once I upgraded to kitkat.
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
pac-mannan said:
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If your phone isnt hanging up and freezing, that gives me hope. I'll gsm reset, clear the cache and then flash.
Thanks
Sent from my SM-N900 using xda app-developers app
pac-mannan said:
Hmmm...no idea then...try flashing it again?
Maybe that will help
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just cleared the cache, factory wiped, and installed the Russian update N900XXUDNC4 and so far, the phone is a lot smoother. No hangups in the browser yet, but time will tell lol.
It is annoying setting up the phone like new lol. I'll update the post as to if I have moments of freezing or the screen becoming unresponsive.
Sent from my SM-N900 using xda app-developers app
Cheers mate..do tell me how the battery is..if its good I might flash Russian as well ,currently have but flashed
Sent from my SM-N9005 using XDA Premium 4 mobile app
Had this problem too, as well as lots of lag. Reflashed and did a factory reset. Took care of both.
Sent from my SM-N900W8 using xda app-developers app
Battery life is looking good. Power Saving off, bluetooth on and connected to my smart watch.
I made one short call. I don't talk on the phone that much. I mostly use it for Internet browsing, music, and instant messaging/texting. I'll update on Tuesday when I have a full day at school.
Keep in mind though that the n9005 is the lte version. I have a n900, the non lte international variant; our battery life may be different.
Edit: 4/20/2014 same charge 70% 1 day 6 hours bluetooth, wifi, gps, and 1 Gmail account in sync.
Sent from my SM-N900 using xda app-developers app
Even I experienced the same. My phone came with Kitkat installed. Freezing happens when a webpage is loading or the time i turn on Sync etc. strange thing is phone seems smooter when power save mode turned on.
I think it may be a problem that was not fixed until the March 31st 2014 KitKat build. I have been using Chrome heavily since I installed the most recent official rom; I have not experienced any lag or hanging system wide or in the browser. It reminds me of 4.3.
When I wiped and reinstalled the previous rom, I noticed the lag and unresponsiveness right away.
I'm going to use the browser heavily next week. If I have no issues, I think it may be safe to say that the bug was fixed in the latest kitkat with March 31st 2014 build date.
People with lag, do you have the lte variant or the regular SM-N900? I'm starting to think only the SM-N900 are being impacted by sour Sammy updates.
And if you guys wipe your phones, make sure to turn reactivation lock off because it could cause an error that will not recognize your real Sammy account and password. This phone has become stressful; I'm not updating it again lol
Sent from my SM-N900 using xda app-developers app
I just experienced another moment of unresponsiveness using the google search box within the chrome app running DNC4 :/ Going to try the latest Russian KitKat
Sent from my SM-N900 using XDA Free mobile app
Hi guys,
Somebody has happened something similar to me, BT stopped working after rooting?
I did factory reset. I haven't tried Odin back to stock yet.
Sent from my C811 4G using XDA Premium 4 mobile app
motumbo said:
Hi guys,
Somebody has happened something similar to me, BT stopped working after rooting?
I did factory reset. I haven't tried Odin back to stock yet.
Sent from my C811 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine still works after rooting
djbling said:
Mine still works after rooting
Click to expand...
Click to collapse
Mine is working also without issue. It doesnt have anything to do with root.
Go into app manager and find the 2 bluetooth apps and clear the data and restart your phone. See if that helps
motumbo said:
Hi guys,
Somebody has happened something similar to me, BT stopped working after rooting?
I did factory reset. I haven't tried Odin back to stock yet.
Sent from my C811 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are attempting to use bluetooth headphones and the above method does not work, when you turn on the headphones continue to hold the power button after they turn on, and in a few seconds it will wipe the paired devices and allow you to pair again. (Happened with my headphones and took forever to figure that out.) I'm sure a similar method would work for other non-headphone devices.
I never hated a phone that much as this one. Having it is a nightmare, first no root then Bluetooth issue and now warning: camera failed. I'm gonna return this crap, once I get the replacement one I'll sell it asap.
Sent from my C811 4G using XDA Premium 4 mobile app
did you disable or delete anything after rooting? rooting doesn't alter things like this, users with root access do.
my Bluetooth works flawlessly after rooting.
I rooted and disabled many apps. Still have Bluetooth that I use to make calls with my radio. And I sent my buddy the Pandora with unlimited skips yesterday with Bluetooth. It's probably a user error.
Sent from my SM-G900V using Tapatalk
jakeneal22 said:
I rooted and disabled many apps. Still have Bluetooth that I use to make calls with my radio. And I sent my buddy the Pandora with unlimited skips yesterday with Bluetooth. It's probably a user error.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
lol most likely is a user error.. he messed up his bluetooth n blamed it on rooting smh.. its been said that whatever you do after youre rooted is on you.. if u dont kno wat youre doing with root then i wouldnt mess with it.. as suggested, odin back to stock and if that doesnt fix it then its not user error lol
Sent from my SM-G900V using XDA Premium HD app