Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I have a lost some respect for Apple Quality Control and Testing. How could you NOT test/catch this?
Did they only test 1 phone or 100?
 
Last edited:
Issue fixed by software 3 days after this entire forum and some youtubers made a MASSIVE ****ING FUSS over some minor testing oversight.

Jesus.

Not charging is a “minor testing over site?” Lol. Ok, buddy.
[doublepost=1538508172][/doublepost]
This happened to me last night. Plugged my phone in to charge it and it was at 65% this morning.

Well according to some around here that’s just a “minor” issue :rolleyes:
 
  • Like
Reactions: john123
Issue fixed by software 3 days after this entire forum and some youtubers made a MASSIVE ****ING FUSS over some minor testing oversight.

Jesus.

I don't like this claim. People were reporting that 12.1 Beta 1 phones were not affected after the whole thing blew up. It was a bug with 12.0 that was either corrected unknowingly or with discrete attention by Apple in 12.1 Beta 1. I was able to eliminate the bug on multiple devices through 12.1 Beta 1 as well.
 
I have a lot some respect for Apple Quality Control and Testing. How could you NOT test/catch this?
Did they only test 1 phone or 100?

No doubt they did. People are presenting this like it happens 100% of the time. Who knows what the real statistics are. Is it like that video where the guy was able to hand pick ones that worked or didn't? All I know is in my household of 4 iPhones running IOS 12, including a Max and an X, and 5 tablets including the Pro, that not ONE of those EVER exhibited this bug. I am not saying it doesn't exist. And I can imagine the frustration of those that did have it. But its not 100%,and I doubt its as high as the youtuber would have one believe.
 
"While this issue originally came to light because of complaints from iPhone XS and iPhone XS Max owners, it appears it was widespread and affected many devices running iOS 12"

That's literally quoted from the article this thread is based on and people are posting stuff like nothing to see here move along. I almost returned my XS over this because I had no idea if it was fixable by software and Apple support said it was a hardware problem and to bring it in.
 
I saw the reports but refused to watch the video because the guy is obnoxious and did not notice the charging issue on my phone since day 1.

Spent some time trying to replicate it and was able to do it on my phone and two co-workers phones.

Basically I had never seen it because the phone needs to be asleep for at least ~7 seconds before connecting the charger. If the phone just went to sleep and you connect it, it charges fine so it seems like the problem was from when it went into deep sleep.
 
  • Like
Reactions: NetMage and roncron
Yeah I’m hoping for a WiFi fix. My XS Max struggles on any weaker WiFi connection. Strong connection, no if issues

Discovered today that my tethering must be impacted by it too - couldn’t get my MacBook to connect to my phone via WiFi and Bluetooth - had to attach the plug.

On lte, I seem fine. I seem to have fewer lines than normal in some spots, but my speed still seems pretty good overall. My WiFi however has been so horrible I’ve been leaving my WiFi off on my phone most of the time.
 
OK so Apple just put some engineering effort into provided a fix for something that was merely a lie.
Noted.

Truth be told I'm not sure much effort was put into this specific issue this late as Beta 1 was a solution to the issue for people experiencing it. I have plenty of thought to believe that Beta 1 was an unintentional fix or possibly quietly addressed it before the launch day of the new phones even.
 
I ****ed up getting rid of my X phone for that stupid trade-in amount, when they conveniently discontinued it since the XS is basically the same ****.

This XS Max has a few issues that are not being addressed but we are getting new emojis.

I went back to Apple and bought a Qualcomm iPhone X - night and day reception difference!
 
Spent some time trying to replicate it and was able to do it on my phone and two co-workers phones.

Basically I had never seen it because the phone needs to be asleep for at least ~7 seconds before connecting the charger. If the phone just went to sleep and you connect it, it charges fine so it seems like the problem was from when it went into deep sleep.

Yep, I can confirm this replicates my issue exactly. I'm installing 12.1 beta to make sure it fixes the issue on my phone.

Edit: Yep, 12.1 beta fixes the issue!
 
Last edited:
  • Like
Reactions: NetMage
My friend who has Verizon on his XS Max reports better reception than his X
As Antennagate taught us, or should have, everything about reception, speed, etc., depends on where you are. I the desert, you likely won't have ANY reception. I Manhattan, there is so much struggle between strong signals and buildings that anything you say about reception is probably true. Apple is fighting very hard against Qualcomm's monopoly on patents that should be FRAND. All phone makers agree, but they don't have a chip foundry, or money to spend on making them adhere to the law on patents when they exist on networks. This year, the modems are all Intel's. They're a lot better than last year, but there are still bugs.
 
Hope 12.1 also fixes poor Wi-Fi range; slow Wi-Fi connection speed; poor battery life; and app update issue where update downs and installs, but then update reappears in available update list and you have to download and install again.

iPhone SE
 
While it's not good to see some people are already having issues with a new product, it's good to see they released an update which hopefully resolves the problem.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.