Hi, today i updated my g2 to kitkat and whenever i plug in my headphones, every single sound (listening to music, playing games, etc.) the sound crackles. My headphones are fine. Does somebody kniw how to fix this? Thank you
yep, I'm using AKG, then switched to Sennheiser and the noise is still there. I rebooted my phone, didn't help, then I factory reset it, still the same. It happend right after I updated to kitkat. Not sureif its a bug or a HW issue:X
Since I updated my phone from D802-SEA-10F to Vodafone 20A i got same problem. When there's any audio playing over headphones I hear crackling and electronic noise in left earpiece. I've tried on few headphones - hifiman re262, akg k712 and stock lg. All headphones had same sound problems. I guess it's time to flash back the 4.2.2 and wait for SEA-20A...
This issue might be connected to the headphone amplifier software (maybe .taiko file). I tried connecting headphones over USB cable and there was no sight of this weird electronic noise.
Before kitkat update I could hear very silent electronic noise in left earpiece too. But it was barely heard when there was no music playing ( and it was with hifiman re-262 which isn't very sensitive to that...). Right now this noise is loud (at same level as the music) and there's static noise too.
Same issue here. My question to all having this issue is how did you do the kitkat update? I updated OTA. Anyone here with this issue who not used OTA?
I have updated to KITKAT on my system (manual update) with 80220A KDZ file and was facing the problem of hiss in my left earpiece. I rolled back to 4.2.2 and it works fine... the update really sucks in terms of audio....
Updated to 4.4.2 today and got the same issue. Noise on left channel when idle and electric crackles when playing music.
I got an expensive high fidelity headset which plays these distortions really well... in other words: headset are useless for music on the G2 from now.
I must be really deaf as i can't hear this. There is always the option to force a downgrade to 4.2.2. But if it's a real issue then need to bombard LG with requests to fix it, ask for official statement on it. Get a timescale.