Enough with the hardware issue. Seriously. Im not even joking
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
You've been saying that always, but I haven't seen any developer fix it with a patch.
Not even Google has fixed it with updates. Do you really believe the all powerful Google can't fix it? They have great software engineers and developers, yet still no solution.
In the Google forums everyone keeps saying it's a hardware problem and I believe that.
It looks like Google won't/can't fix the issue, so it's not software, or they could have already fixed it.
Same reason LG hasn't updated the bad GPS of the G2 or the antenna location to fix the cell reception issues.
Same reason Apple didn't update the antenna issue on the iPhone 4 until the next model iPhone 4S.
Same reason OnePlus won't update the screens on their phone to fix the yellow tint issue.
Same reason they haven't updated the Nexus 5 to include a stronger vibration motor.
Same reason they haven't updated the Nexus 7 2013 with a new screen to fix the touchscreen issue.
Enough with the software issue seriously.
Google guys doesn't seem to be that good engineers exactly because they haven't been able (or willing) to fix this issue. And about Google being a powerfull company; true as long as it gives them money. Google is not the most user friendly company as we all know so I guess this issue has got pretty much ignored by them. Or then it's just that their engineers have weak knowledge about audio related hardware/software optimizing.
And finally I'm glad to show you something that gives you bulletproof evidence that this issue is indeed SOFTWARE ISSUE. FLASH THIS PLEASE (third post includes flashable zip): http://forum.xda-developers.com/show....php?t=2837930
That is not bulls**t, simply 100% working fix.
Yes it does indeed. Now let's hope the patch will be merged to aosp so everyone could benefit from @chdloc 's great work.
|Thread Tools||Search this Thread|