1234. AI DIsaster Lesson 3

 As I noted in Lesson 2, you can't trust AI to logically resolve your problem. It seems that most of what it does is collects OLD procedures and tries to use them to resolve your newer hardware/software versions of products. Today's lesson is a3-4 hour fiasco where AI destroyed working phones connected to Hearing Aids.

Problem: I have two identical phones I purchased from Tracfone - both Moto g Play phones (2026). I received one, call it A, in early June and activated it 6/4/26, while the other was activated 6/10. I have 2 Hearing Aids from Phonak. Initially, the HAs were BT paired by the audiologist onto an older Moto e phone successfully giving me immediate ability to hear my mobile phone through my HAs. 

All was fine until I configured the TV Connector that allowed the TV sound in the HAs to be controlled, particularly volume assigned to 5 different programs. Well, according to AI after hours of guessing, the glitch that kept it from working on that old phone was old technology. I'm not convince now that AI was ever correct, but I purchased by new Moto g Play, same as my wife's, because I did get it working on her phone. I therefore assumed I could match the installation onto my new phone and have the same success. WRONG. 

My New phone could not pair the hearing aids to produce individual volume for each ear that wife's phone had no trouble doing. 2 hours with AI #1 resulted in AI#1 quitting! Couldn't fix it despite running me through Hell trying. So, I accessed AI a different was - this brough on AI#2. Immediate after describing the issues in detail and incorporating some of the attempts AI#1 tried, AI#2 immediately started his guessing entirely different. It then wasted 2.5 hours running through technical details over and over in circles only to end with Something I suggested in minute 10. AI#2 was insistent in me NOT to hit the Split L/R button on the volume to see 2 volumes, 1 for left ear, 1 for right. It claimed that would mask the problem it was trying to resolve. Well, AI#2 never resolved the problem bur provided a bunch of technical mumbo jumbo no one could remember. Everything tried failed the same was and the steps to get to the error included so many wrong directions it was impossible to remember all the mistakes and corrections. 

I could spend a day trying to document the details. But I'd bore you out of your mind. Suffice it to say that once again AI worked in its own world and I couldn't imagine what it was looking at. My constant WTF comments got it to change its mind up to 5 times for each occurrence until I could perform the correct sequence on MY phone and Phonak rather than his imaginary ones. I did learn my lesson 1 and 2 though and believed only 20% of what it instructed always being careful of its desire to kill my phone, my HAs, or me! The end Go ahead ant hit the Split L/R like I suggested. It surrendered and quit just like AI#1 saying that the Split L/R was the best workaround and recommended. Ha-Ha. 

AI has NOT be helpful for problems not already documented and found by straight Google searches. It seems it takes the worse of the worse and tries to sell you on it! I'm exhausted from this last encounter.

1233. AI Lesson 2

 Since post 1232 AI Lesson 1 I have used Copilot many, many times. Most provided a solution that worked or got me close to working. However, it does have some annoying habits:

1. AI will always attack what it thinks your most recent problem is rather than the reason why you are there. For example, if you jump at its recommendations in first query and hit a snag doing it, AI focuses on that snag, Then if you try fixing that one to proceed and hit another snag (2), AI switches to that, etc. I have gone down a path of over 10-15 snags in a row throwing me way off the initial problem trying to solve each snag instead. Then you get to one that is a monstrous recommendation like download something to execute that you know is not involved with the initial problem. I was told about a .dll missing that never existed on my systems. AI couldn't be convinced that it was never part on my initial installation, granted many years ago in 2010. The application at fault was Any Password. It took AI about 40 minutes before telling me that fact and that it was discontinued and thus the module is gone. Fact though, is Any Password has worked for 15 years now without a hiccup and had its first one AI claimed was an encryption problem within. Not true. Works perfectly again whatever the problem was! AI believes it has to tell you details about why something isn't working. Half of the time it is wrong. This leads to incorrect analysis and recommendations re the major issue which is lost in the process.

Just beware of this annoying habit. Take what you can get from AI, CHALLENGE it if it is wrong. It always apologizes and throw out another THIS ONE WILL work. I had about 15 of those and all failed! Gather what you can and assemble the correct facts it or you find and proceed with those.

It can be a frustrating experience. One must understand that it is using data from man soles, right or wrong, to put its pieces together. I'm not particularly happy with it diagnosing technical computer problems as the "leader". I have found that you take what it offer and proceed with you know is right.

Always more than not the procedures to implement in the Android world are incorrect and something else must be substituted. AI does NOT confirm the starting point, i.e., device, device age, brand, software, etc. first. Instead it jumps into trying to resolve you issue with "hidden assumptions". So, my advice, just like a customer support person, begin with details about you hardware and software before he runs in the wrong direction. I'm still learning. But this AI is NOT a hands off tool that gives you correct answers. It must be told details. Life goes on.