Ok, so I love this phone. Got it about 2 weeks ago. However, today I tried to Bluetooth connect with a friend's Samsung Galaxy S3 to transfer over some photos when, during the pairing, my Optimus G rebooted and now will not connect to ANY bluetooth device. Tried multiple other phones, headsets, and my mini bluetooth keyboard. Hard reset the device and it still will not connect. I know it was working previously because I connected to my own GS3 a few days ago and transferred over an .APK file just fine.
Anyone experiencing any similar issues??
EDIT:
Just got off the phone with LG and they, as I expected, don't know anything regarding this issue and can't do anything but recommend a Master Reset of the device or send it to them for repair/replacement.
adampatricknc said:
Ok, so I love this phone. Got it about 2 weeks ago. However, today I tried to Bluetooth connect with a friend's Samsung Galaxy S3 to transfer over some photos when, during the pairing, my Optimus G rebooted and now will not connect to ANY bluetooth device. Tried multiple other phones, headsets, and my mini bluetooth keyboard. Hard reset the device and it still will not connect. I know it was working previously because I connected to my own GS3 a few days ago and transferred over an .APK file just fine.
Anyone experiencing any similar issues??
EDIT:
Just got off the phone with LG and they, as I expected, don't know anything regarding this issue and can't do anything but recommend a Master Reset of the device or send it to them for repair/replacement.
Click to expand...
Click to collapse
That blows man, since I unlocked my boot loader my Bluetooth Wi-Fi 3g and 4g have been running like crap. I get the demi god screen every time I try to update my profile or prl
My Optimus G refuses to maintain a stable bluetooth connection with my Uconnect 130/res system in my jeep. Also, when using LG tone+ 730's it consistently drops connection once a day. Extremely frustrating.
Are these issues with rooted Optimus G's or stock?
If it can't maintain a BT connection that a pretty big deal, especially of your using it as a hotspot. Things like this drive me crazy. The phone build is nice but it seems like LG needed some more testing.
Sent from my Nexus 7 using xda app-developers app
cassix said:
Are these issues with rooted Optimus G's or stock?
If it can't maintain a BT connection that a pretty big deal, especially of your using it as a hotspot. Things like this drive me crazy. The phone build is nice but it seems like LG needed some more testing.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah, mine is straight stock. I'm waiting on a custom OS to pop up before I root my device.
Actually, I want to add an update to my previous issue. Somehow, the device is now recognizing BT headsets and some BT devices such as my BT keyboard. However, it still will not connect to another phone.
I have absolutely no errors with bluetooth on mine, stream music flawlessly in my car and my headset, dunno if y'all just got defective phones, if you're not past the 30 days (if purchased through BB) i would bring them in...
By the way mreniigma awesome avatar!
Been using my Bluetooth now for a while and luckily have zero issues. Works great.
Sent from my Nexus 7 using xda app-developers app
Related
ive never had an issue bluetooth pairing my g2 to anything up until today. My dad just bought a handsfree bluetooth kit for his car from walmart i believe and asked me to hook his g2 (stock, rooted) to the bluetooth unit and his g2 didnt even see it. I then tried my g2 (cyanogenmod 7 latest nightly) and it didnt see it either. Just out of sheer curiousity i tried his old motorola razor and bam, found it and instantly hooked to it. Im kinda bummed our "smart phones" wouldnt but the one dumb or "challenged" phone would. anybody know why? or how to fix, or even an app to help get around this issue? thanks for any help.
sent from something they thought nasa built
veritasaequita said:
ive never had an issue bluetooth pairing my g2 to anything up until today. My dad just bought a handsfree bluetooth kit for his car from walmart i believe and asked me to hook his g2 (stock, rooted) to the bluetooth unit and his g2 didnt even see it. I then tried my g2 (cyanogenmod 7 latest nightly) and it didnt see it either. Just out of sheer curiousity i tried his old motorola razor and bam, found it and instantly hooked to it. Im kinda bummed our "smart phones" wouldnt but the one dumb or "challenged" phone would. anybody know why? or how to fix, or even an app to help get around this issue? thanks for any help.
sent from something they thought nasa built
Click to expand...
Click to collapse
Did you set your phone as discoverable in the bluetooth settings?
Sent from my HTC Vision using XDA App
yes, it was set as discoverable
sent from something they thought nasa built
I can't seem to find any mention of this anywhere else, and I have looked. My wife and I both have E4GT and are both experiencing this issue everyday and we both have different Bluetooth headsets.
We will walk away from our phones far enough that our headsets disconnect. Once we close enough, sometimes they connect back up, but most of the time, we have to shut off the Bluetooth radio in the phone and turn it back on before it will connect again. Once in a while we are right next to the phone and it will disconnect for no reason at all.
My wife has a cheaper Rocketfish headset and I have a more expensive Jawbone.
Anyone else having this problem?
both our phones are rooted and we're both running Caulkins rom. She is running an older 2.8.0 and I am sporting 2.8.1. I have asked this in his rom thread, but twice have gotten no responses. I can't find anywhere if there is a Bluetooth radio driver update like with modems.
Did this happen while you were on stock?
Sent from my SPH-D710 using XDA App
davidc23 said:
Did this happen while you were on stock?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
HAHA, I knew someone would ask that!
To be honest with you, we got these phones and two hours later, I had them rooted and flashed, so I couldn't say. I've been rooting and flashing roms since we had our first Droid 1 phones and I just can't seem to leave well enough alone.
I have the same issue with a Jawbone Era.
Has happened on stock roms as well as Caulk's and UnNamed.
What happens with my Era is that it will just stop working. Phone will show that it is still paired, but I get no audio to the device. The only way to fix it is to turn off the Era headset, and turn off bluetooth on the phone. Then turn BT back on, followed by the headset.
It's a real PITA. I got this headset after reading several reviews on the webs saying that it was a great unit.
It is, when it works. Unfortunately this happens at least once a day.
I am looking for a solution as well, and I was even thinking of getting a different headset but after reading that it's happening with completely different headsets makes me think that won't solve anything.
I'll try to report back if I find anything.
One other note, the Jawbone Companion app also is very flaky. Most of the time it will not detect the Era headset even when the phone is connected and it's working fine. This too happens on both stock and custom roms.
Bluetooth
Make sure your phone is set to always discoverable and when you get back in range of your phone try hitting the call/end button on your bluetooth, this should help it re-connect without having to restart the program in your phone.
I have been running into this exact situation with my brand new Plantronics Voyager Pro HD, and I was about to return it to the store today, but then I saw this posting, so maybe it is NOT the BT headset afterall. Next time it happens I will give those instructions a shot...
Does making your phone "always discoverable" have any bearing on the battery life or anything? Thanks!
jb8301 said:
I have been running into this exact situation with my brand new Plantronics Voyager Pro HD, and I was about to return it to the store today, but then I saw this posting, so maybe it is NOT the BT headset afterall. Next time it happens I will give those instructions a shot...
Does making your phone "always discoverable" have any bearing on the battery life or anything? Thanks!
Click to expand...
Click to collapse
I'm seeing a pattern here. It appears from what I'm reading, that it does not matter what Bluetooth headset you have or what rom you're running, it's happening to a few people. Makes me think it's the phone or Gingerbread itself that's the issue. Maybe when ICS is ready to be a daily driver, it'll change.
In one respect it makes me feel better as my wife and I don't have to replace our headsets!!
I am not comfortable in leaving our phone "discoverable" as this opens our phones to possible unwanted access from unscrupulous people.
I bought this phone on sale at WalMart about 3 weeks ago to replace my HTC Mytouch 4G, which has been a great phone but I thought it was time for an upgrade. So far I'm not too impressed, and several times I've had an issue when I make a call that no one can hear anything. It shows it's dialing, then connected and I hear nothing. If I call back it usually will remedy itself, but not always. The other day I called my sister back after the first time of no audio, and I could hear her but she could not hear me.
This has happened about 5 to 7 times in the last 3 weeks, but it's unacceptable to me. I don't want to root the phone and run a custom ROM at this time since the phone still has a warranty, but I have a feeling it's the software, not a hardware problem. Is it a known problem with 4.04?
Also, the voice recognition on this thing is terrible! I drive a truck for a living and use my Plantronics Voyager Pro exclusively, and I have to use voice command or take my eyes off the road. I can't get this thing to recognize half of what I ask it to do. My HTC was pretty good at that, too!
I really had some expectations with this phone, and it is a nice one in many respects, but it's faults are driving me crazy!
WarrenEC said:
I bought this phone on sale at WalMart about 3 weeks ago to replace my HTC Mytouch 4G, which has been a great phone but I thought it was time for an upgrade. So far I'm not too impressed, and several times I've had an issue when I make a call that no one can hear anything. It shows it's dialing, then connected and I hear nothing. If I call back it usually will remedy itself, but not always. The other day I called my sister back after the first time of no audio, and I could hear her but she could not hear me.
This has happened about 5 to 7 times in the last 3 weeks, but it's unacceptable to me. I don't want to root the phone and run a custom ROM at this time since the phone still has a warranty, but I have a feeling it's the software, not a hardware problem. Is it a known problem with 4.04?
Also, the voice recognition on this thing is terrible! I drive a truck for a living and use my Plantronics Voyager Pro exclusively, and I have to use voice command or take my eyes off the road. I can't get this thing to recognize half of what I ask it to do. My HTC was pretty good at that, too!
I really had some expectations with this phone, and it is a nice one in many respects, but it's faults are driving me crazy!
Click to expand...
Click to collapse
Why didn't u get the s3?
Anyways, there shouldn't be any calling issues. T989 is a pretty popular phone and wouldn't be if it did not successfully make calls imho. As for voice recognition... guess HTC is better for your voice? Again mine works fine. Idk... this phone is pretty baddass
Sent from my SGH-T989 using xda app-developers app
bzlik88 said:
Why didn't u get the s3?
Anyways, there shouldn't be any calling issues. T989 is a pretty popular phone and wouldn't be if it did not successfully make calls imho. As for voice recognition... guess HTC is better for your voice? Again mine works fine. Idk... this phone is pretty baddass
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
The SII was $299 on sale, the SIII was about $699 without contract....
Having the same problem also with the call connected, but can't hear anything.
kruang said:
Having the same problem also with the call connected, but can't hear anything.
Click to expand...
Click to collapse
I knew I wasn't alone!
This happens to me sometimes actually, but it only happens when I am connected to WIFI calling. Does not happen when on the network.
Its possible that your losing a 4G connection or its a weak signal when you answer the call?
Either way, when it happens to me, I battery pull and then it works again.
ITALIANNYC said:
This happens to me sometimes actually, but it only happens when I am connected to WIFI calling. Does not happen when on the network.
Its possible that your losing a 4G connection or its a weak signal when you answer the call?
Either way, when it happens to me, I battery pull and then it works again.
Click to expand...
Click to collapse
I was thinking of the WiFi calling may cause the connection issue before, so I only turn on WiFi connection at home, but didn't help. Also, it only happens after update to ICS. It happens randomly quite often and I have to use apps (i.e. Tango, Line, etc.) to make call instead. I was outdoor with full signal and 4G.
Too lazy to pull battery because of the protective case. Reboot wouldn't help either
My family has two galaxy s2 and blaze phones and all experience same issues. And that to with no WiFi and in DFW metroplex. It looks like Samsung and T-mobile issue to me because I don't see any ATT side complaint on this.
Sent from my SGH-T989 using xda app-developers app
My girlfriend and I both began having these issues with the 4.0.4 update, and never before that. It's awful, because it's so sporadic.
Edit: I never use wifi calling, and it happens both when connected to wifi and when far away from wifi, with it on and off.
Sent from my SGH-T989 using xda premium
I've seen multiple people with this issue in some of the custom rom threads. This didn't happen to me on 4.03, but it does on 4.04 based roms. It seems to happen with or without wifi calling.
Sent from my SGH-T989 using xda premium
ditto
I been having the same problems. stock or multiple custom ROMs. wifi-calling or no.
thought it was the wifi calling function at first, but verified that even on tmo signal and my family been having the same problems...
I've heard of people calling TMobile for support but leads to nowhere. I'ma try calling too and see what i can find out. will post with any news.
And here I was thinking it was a Rom issue. I have literally installed every Rom this morning and tested to see if the issue remained. It has happened with every one of the Roms which led me to think it was a HW issue. It seems to happen more often when my signal is weak. I have tried all the of the Radios too. Im not sure when the issue started but its very consistent with my phone. I have to try 7-8 times EVERY call to finally talk to the person. I normally just switch to my work phone or send a text.
Same problem, on both stock and custom. Must be a t-mobile thing.
So what do we do? Should we all call T-Mobile? Maybe if enough of us call, they will actually look into it.
WarrenEC said:
The SII was $299 on sale, the SIII was about $699 without contract....
Click to expand...
Click to collapse
I also just made the identical decision (also choosing the SII over the Nexus 4 16GB—call me crazy). I seriously hope I don't have this problem... Setting up the phone now.
Most likely T-Mobile won't help. It's weird though that this only happened on the GS II. The GS I and GNex don't have this problem...
Me and my mom have this phone she is stock but we both have had this same issue lately and its been on 4.0.4 has anyone tried another radio to see if that's it? Maybe the new uvli1 will be better
Sent from my Infamous Jedi
I sign in only to tell how I fix my problem with calling I root and flash Jedi Mind Trick ROM for T-Mobile Galaxy S2 SGH-T989! [X1] and RADIO SGH-T989 UVLE1 (T-Mobile) 4.0.3 . The problem is fix after a few nights no sleep and a lot flashing
style154 said:
Me and my mom have this phone she is stock but we both have had this same issue lately and its been on 4.0.4 has anyone tried another radio to see if that's it? Maybe the new uvli1 will be better
Sent from my Infamous Jedi
Click to expand...
Click to collapse
I've tried all available radios except uvli1. I don't think it's a radio issue. I'm pretty sure it's 4.0.4. I've tried a few 4.0.3 roms and they seem fine so far.
---------- Post added at 09:03 AM ---------- Previous post was at 08:34 AM ----------
Do you have a link to uvli1? I'd like to rule it out
edgie13 said:
I've tried all available radios except uvli1. I don't think it's a radio issue. I'm pretty sure it's 4.0.4. I've tried a few 4.0.3 roms and they seem fine so far.
---------- Post added at 09:03 AM ---------- Previous post was at 08:34 AM ----------
Do you have a link to uvli1? I'd like to rule it out
Click to expand...
Click to collapse
Hmm wonder what it could be no its not out yet. Rushaoz is extracting it from his phone maybe we should ask him if he has had issues because Tmobile said they won't release the uvli1 update it will only come on new phones I feel somewhat cheated
Sent from my Infamous Jedi
So I have tested two different Xbox 360 slims. Both do not want to hook up. Old Xbox 360 with wireless g adapter works fine.
Bui... This has not always been the case with Xbox 360 slim. I used to not have problem. I think this may be due to new WiFi drivers.
Thing is... I can't seem to get the old WiFi drivers back on my phone. I used to have option to host WiFi tethering via wep securrty, which I take as an indicator of old wifi.
I have flashed older kernels to no avail. Running latest rasbean. Any suggestions or help?
Try taking off the Wi-Fi security.
Sent from my Galaxy Nexus
Garridon said:
Try taking off the Wi-Fi security.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes. Tried that.
Changing mixed to G or N?
a maguro wrote this.
Now I'm in your boat. Internet's down and I'm trying to tether to my Xbox slim. I googled, found out that this problem only started happening after the 4.2 update.
Sent from my Galaxy Nexus
Garridon said:
Now I'm in your boat. Internet's down and I'm trying to tether to my Xbox slim. I googled, found out that this problem only started happening after the 4.2 update.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I still think its wlan drivers. Gonna try flashing some old ass kernels to test. Maybe today... I recall it working before wlan drivers were messed with.
I decided to USB tether to my laptop and bridge the connection with an Ethernet cable. Works that way.
Sent from my Galaxy Nexus
Hello all,
Thanks for having me here, this is my first time posting on this site. I recently purchased a Galaxy Tab 3 7.0 from Sprint as they're running a deal and they're cheap. I'm using the tablet for my startup company, we will be using it for route delivery. In order to make things more efficient when visiting customers and placing orders, I purchased a MoKo Bluetooth Keyboard Cover Case from Amazon. I can't link it since I'm a noob haha. I also purchased a Zebra RW420 mobile receipt printer that I have already gotten to connect via Bluetooth with the tablet. However, when I try to use the Bluetooth keyboard that is already paired with the device, it does not work. I've tried factory resetting, unpairing/repairing, etc. Just typical troubleshooting protocol. I know my issue is not with the keyboard as it connects to other Android devices, such as my phone which is a Galaxy S4 and my buddy's tablet by NVIDIA; both are running Android 4.3 while I'm stuck at 4.2.2 on the Tab 3.
I literally JUST bought the device; should I return it and get something else? I got it because it was cheap and I'll only be using it for work so it doesn't have to be spectacular. Is it worth it to root the device as opposed to doing the latter? Are there any risks I have to worry about with rooting that could affect my deliveries (i.e. the device bricks)? Do I have any other options besides what I mentioned? Will I still be able to connect to Sprint's network even after it is rooted? I've been researching all night and the only thing I've really found was that 4.2.2 broke Bluetooth for a lot of devices and that the only way out of 4.2.2 on the Galaxy Tab 3 is to root it. I plan on taking it to the Sprint store tomorrow but figured I'd share my issue with others and come straight to you guys as I'm sure you'll probably be more informative.
Thanks in advance, I look forward to hearing from you all.
Update
Update: Went to Sprint, got the answer I expected there's nothing they can do about it; I can either wait it out and hope they release the 4.3 update or return it since I'm within the first 14 days
That stinks. Haven't tried a bit keyboard yet. I picked it up too since it was cheap. Updates are my only beef with carrier tabs. Will cross fingers they support it better than the ZTE.
Sent from my SPH-L720 using Tapatalk
I just connected my little handheld keyboard with track pad. Worked like a charm actually. Maybe it's your keyboard. Did you try connecting it to another tablet or maybe the tab 3 they had in the store?
Sent from my SPH-L720 using Tapatalk
Thanks for the response. I know it's not the keyboard, I've connected it to other devices, the problem is specifically the Tab 3. When I took it into Sprint they went through the standard troubleshooting protocol on both my device and one that they had in the store and it paired with both of them, the keys just don't register. I'm convinced that it is Android 4.2.2 that is causing it as that's what I've seen in my research; Bluetooth was rewritten in 4.2.2 and broke Bluetooth for a lot of devices. I'm considering rooting it and putting either 4.1 or 4.3 on it, I just have a few questions:
1) Will it rooting/flashing it affect its ability to connect to Sprint's mobile network?
2) I'm using it for route delivery so I can't have it brick on me while I'm out; what are the chances/common causes of bricking?
3) Would I be better off with 4.1 or 4.3? Which is more stable (if either)?
Rooting won't. Flashing shouldn't either, but it would say so in the notes of the rom.
Would imagine 4.1 would be since 4.3 isn't official for this yet.
Sent from my SPH-L720 using Tapatalk
Bluetooth won't connect to my keyboard
hi ,i got the tab 3 t210r ,after i upgraded to a custom rom ,i cant make my bluetooth keyboard to work ,i placed the 4,2,2 android,any solutions ,,,,,,