Hey guys!
I have a few problem with my P9.
First of all the wifi keeps disconnecting all the time. It says connected for like two seconds, then disconnects, then reconnects immediately, disconnects again, reconnects ... and so on.
I've tried various firmwares and different wifi networks, but the problem persists. GPS and bluetooth seem to be working properly though.
Does anyone know a possible fix?
Another problem is that the loudspeaker sounds distorted, like a crackling sound. Sometimes it stops completely.
Apart of these problems it works fine.
Both of the problems might be because of a water damage, so now I'm wondering ...
Does it make sense to replace just the wifi antenna and the loudspeaker part?
Those would be cheap, so I'd consider replacing them myself.
Or could it be a problem with mainboard or sub board?
In this case I would rather go for a new phone.
I'm not sure, if I wanna take the risk. What's your guys' opinion?
Related
For some reason, whenever I connect my tilt to another device via bluetooth, the connection is very poor (for lack of a better term). Let me explain the symptoms:
When I'm listening to music on my bluetooth stereo headset, it will randomly "blink out" and go from a second, to a few seconds without playing any sound. Then pick up again.
When I try to use bluetooth PAN, it will randomly disconnect at non-regular intervals.
I can't speak to the PAN, but I know that the bluetooth headset works flawlessy with my computer, so I think that the problem likely resides in the phone somewhere.
Any suggestions as to what I might be able to try would be greatly appreciated. Also, as a side not, I've used a few different ROM's and radios, and had the problems regardless. I'm wondering if perhaps I have a hardware problem and need to get my phone repaired? Is there any way to better test? Thanks
Well, I've e-mailed HTC about the issue and am awaiting a response. Looks like it might go back for warranty work though.
Dear All,
My optimus black fell from my hand yesterday on solid floor, and since then I was unable to turn on the wifi or bluetooth, and im not really sure about the GPS, it seems to turn on but it does not detect any satellite signal.
I am almost sure that the fall is the reason of this malfunction because it was working normally before the incident.
I tried to restart the phone several times, but it is always the same. I choose to turn the WiFi on, it says turning WiFi on, then nothing happens and it is off again, the same happens for Bluetooth.
I am familiar with the phone from the inside, I have opened it several times to fix the power button problem, but I am not really sure where the WiFi and Bluetooth ICs are (if someone can tell me I would be really thankful)
I checked the motherboard connections, and everything seems to be intact.
Any suggestions?
I have searched the internet, but I could not find any decent LG optimus black hardware tear down.
Thanks!
Hi All,
Apparently no could help me with my issue, but thanks anyway, I managed to find out the Wifi and Bluetooth IC.
Unfortunately, I could not manage to figure out the problem, probably it is one of the capacitors, but if anyone ever wants to know, Optimus Black uses Broadcom BCM4329 IC (Low-Power 802.11n with Bluetooth® 2.1 + EDR and FM (Tx and Rx)) embedded on the backside of the motherboard when you open the phone.
Thanks
Could be a antenna problem or try downloading an app to check out snr noise.
Hi
I'm experiencing an odd problem with my phone. I'm on Skydragon rom (android 4.4.4) and I'm experiencing the following problem (quoted from another site with the same issue):
I have wifi on all the time and working properly, no network drops. I connect my bluetooth headset. Wifi still seems to function properly. Only when the bluetooth is actually in use (ie. listening to music or taking a phone call on the headset) does it seem to disrupt my wifi connection. If I turn my bluetooth headset off, wifi will work perfectly again without any drops.
Does anyone have any insight into this problem? I have tried changing radios, hboot, the works and nothing works.
Cheers
Anyone else haing issues here with bluetooth? I can connect to everything bluetooth, wireless speakers, car, headsets, watch etc. The only thing I can get to work reliably is the headset, everything else randomly cuts out or has issues. For example both cars have bluetooth for phone calls, one has bluetooth for media, I can get both to work for a short time but it either 1. Cuts out and reverts back to phone, freezes the system in the one car, or jumps back and forth between the 2. Similar results when connected to bluetooth speakers, can get it to work for about 10-15 minutes then nothing, phone shows it still connected and playing music but no sounds from speakers. LG G Watch R also randomly looses connection. I'm beginning to regret my switch from the S5.
Anyone having similar problems or a fix?? I really want to keep the phone but not sure I can deal with this flaw...........
I have no such issues with the bluetooth. I can tell you that I had bluetooth issues with one of my other android phones. I had to get it warranty replaced. My suggestion is that you get the phone replaced since its brand new.
Mine has been fine so far. I just wish that android was more like apple, as much as I hate to say that. Both my S6 and M7 will play phone audio fine when in a call, but to use maps I have to turn the radio to Bluetooth mode. Makes it kinda boring to ride with no radio just to get turn by turn nav.
Sent from my SM-G925V using XDA Free mobile app
I haven't had any issues with my smart watch (moto 360) but I have had some weird issues with my car's Kenwood media deck. The phone will connect to the unit, but 75% of the time no sound will come from the speakers on the first try. Sometimes just waiting about a minute does the trick, other times I turn BT off/on and it'll work fine the 2nd time. However because I haven't had any issues connecting with my watch, ear piece, or laptop I am willing to bet it's it an issue with the Kenwood and not the phone.
Thanks guys. Don't want to have to warranty swap it but looks like that's going to be my first step.
Hey guys, Merry Christmas!
Out of the blue as I was riding my bike somewhere with GPS on and Bluetooth connected to my speaker everything was going fine.
I got where I supposed to be, the connection was fine and all.
When I wanted to return though, the Bluetooth speaker just wouldn't connect.
I tried turning both the speaker and the phone on and off but nothing changed.
Messed a bit with the developer settings but again nothing changed.
Tried to connect to a few more speakers I have and none connected.
My BFF has the same device and his device connects just fine to my speakers, my device just refuses.
It does *technincally* connect but it says Connected (no media), which is obviously useless in my case because the audio players from the phone's speakers and not the external ones.
For some weird reason, it does connect and play though to my car's Bluetooth. (Seat Ibiza 2020 MY not as it matters)
I changed a few roms and one weird thing I noticed when I was running POSP I think was in the dev options, Bluetooth mode, everything was greyed out besides default.
That's pretty weird if you ask me, I mean SBC AAC and some others *should* be available right?
So my concern is I'm facing a firmware/hardware issue, unfortunately, maybe some persist.img problem?
I ended up flashing with mi flash tool the latest miui 12 europe and global roms without luck, and now I'm in the middle of flashing the Chinese one just in case.
Has anything similar happened to you?
How did you fix it?
I cannot for the life of me find a solution and think about giving up and sending it for repair.
Well after trying lots of roms and whatnot (I even went back to MIUI 10, Android 9) I found out that If I try to connect with my speakers as the first device it won't connect, if I connect to my car or my Airdots and then try to connect to my speakers then it does indeed connect.
I cannot comprehend why this behaviour exists, but at least it is persistent if I don't reboot and I only need to this on the first pairing.
I guess problem solved...?
(it should be able to connect normally, but that workaround is good enough I guess)