Danishblunt
https://zentalk.asus.com/en/discussion/comment/181834#Comment_181834
As you mentioned, the SoC itself is unlikely the suspect as other brand such as samsung with the snapdragon 888 variant does not report any wifi issues related to the entire funtionality being broken. I doubt it has anything to do with the actual manufacturing of the logicboard as well, otherwise the issues would not have happened after an update.
Also the 6900 does not control audio as a whole, it only controls bluetooth audio, which is unrelated to those who experience robotic voices.
You make an excellent point with the bluetooth argument, as normally both go hand in hand due to being in the same chip, that being said, I did see SoC's fail only partly same for desktop CPU's where the integrated graphics would be broken and shorted while the CPU itself was fine.
WIthout users testing, we don't have much to go by, so far my theory is that due to the update, the drivers got messed up and should be fixed via a firmware flash, however it seems nobody here is able to do that.
View post
Always so uncertain because now new users report that the phone no longer turns on.
For audio, yes, the 888 only processes BT audio, I generalized thinking that users used it on the phone with headsets or a hands-free kit because in France it is a majority, mandatory in car or it is connected to the car radio.
I think I also have the phone audio bug, to be confirmed. Yesterday I called a company that handles calls with an intelligent talking robot, we can say Yes / No to it, but also full sentences. The robot recognizes Yes or No once in 10 with the rog 5 and ended up hanging up. I repeated the call twice for the same negative result.
I took my Motorola G8 + and had 30 min of conversation with the robot without any problem. also tried with a Samsung S20 without problems. test with 3 tel and 3 sim (free, orange, bouygues) in each tel. 3 failures with the Rog5.
It annoys me to do it on my own but clearing the cache and the data of the Google Framework service could force a new OTA update on some tel a few years ago, I will do some research.
The cause of a bad firmware update remains to be favored because after the .86 update there were other failures than the WIFI. The proximity sensor and the air triggers. The sensor has restarted after a new firmware update. In theory, this should not happen with the inactive hidden partition system imposed on A11.
I am going to take advantage of my vacation and I will look into it on the way back, if this happens to me with my rog5 and it is not hardware I would like to understand.
