iPhone XS and XS Max: You’re Charging It Wrong

Twisted Kidney said:
I had this crap happen with an LG or Moto phone (can't remember) that I ended up returning because there was no evidence of a patch coming.

I'll bet Apple patches this problem with the quickness, Android phones like mine only get patched after months of hand-fucking by the manufacturers and rebranders. Returning the phone is more efficient.

I still can't ever see the ridonkulous extra cash for Apple. Fuck their shit, drop those prices by 35% and we'll talk. You pay all that extra and get the same problems.
Click to expand...

They have already fixed it on 12.1 beta. People have verified that. Just have to release that.
 
Thanks nizmoz - who’d a thunk. Guess I’ve managed to not do any of those things yet somehow..
 
NIZMOZ said:
All devices have the issue from iPhone 6 and up that are on iOS 12. You just have to know how to make it happen. Do not touch the device, let it sit for 5 minutes, then just plug it into the charger cable (without waking the device up), it won't beep or light up.
Click to expand...
After reading you post I say this is an incorrect statement. Not ALL devices have this issue. I conducted a test on both of my Iphones using your method of letting it set for 5 minutes and not touching the phone and then plugging in the charger cable. I have an iPhone 6 work phone and an iPhone 8 plus on IOS 12 and both started charging after sitting on the night stand for more than 5 minutes undisturbed and then plugging in the charging cable only touching the case as to not disturb the phone.

The only problem I have had since IOS 12 was installed on both phones was both were dropping calls like crazy after installing IOS 12 from Apple on the Wednesday before the official release date. I contacted Apple the day after I installed IOS 12 and talked to the tech support and they moved me to a Apple Senior level tech promptly once he could not find a solution. The S tech reviewed the carrier data information about dropped calls but the 1st tech had me erase the info trying to fix the issue. I was shocked that the Apple Senior level tech gave me his work number and told me to contact him directly if I had any more dropped calls. That evening the eve of IOS12 official launch, ATT pushed a carrier update at 4:30pm on my work phone and 730pm on my 8+ and my problems went away. BTW, I received a call from the Apple Senior tech the next checking to see if I had any more dropped calls which I haven't had since the ATT update. BTW, the S tech told me this was a problem that Apple knew about that only affected ATT customers and they were waiting on the update to happen.
 
Baditude said:
After reading you post I say this is an incorrect statement. Not ALL devices have this issue. I conducted a test on both of my Iphones using your method of letting it set for 5 minutes and not touching the phone and then plugging in the charger cable. I have an iPhone 6 work phone and an iPhone 8 plus on IOS 12 and both started charging after sitting on the night stand for more than 5 minutes undisturbed and then plugging in the charging cable only touching the case as to not disturb the phone.

The only problem I have had since IOS 12 was installed on both phones was both were dropping calls like crazy after installing IOS 12 from Apple on the Wednesday before the official release date. I contacted Apple the day after I installed IOS 12 and talked to the tech support and they moved me to a Apple Senior level tech promptly once he could not find a solution. The S tech reviewed the carrier data information about dropped calls but the 1st tech had me erase the info trying to fix the issue. I was shocked that the Apple Senior level tech gave me his work number and told me to contact him directly if I had any more dropped calls. That evening the eve of IOS12 official launch, ATT pushed a carrier update at 4:30pm on my work phone and 730pm on my 8+ and my problems went away. BTW, I received a call from the Apple Senior tech the next checking to see if I had any more dropped calls which I haven't had since the ATT update. BTW, the S tech told me this was a problem that Apple knew about that only affected ATT customers and they were waiting on the update to happen.
Click to expand...

No sir, all devices from 6-10s have that issue. You need to read MacRumors and many are having it on their older devices including my own household.

Your test is flawed, as you are doing something wrong. You may have the security setting turned down, or you have touch to wake up turned off. Those two things will make it work.

https://forums.macrumors.com/thread...ge-while-screen-is-turned-off.2144288/page-11

https://forums.macrumors.com/thread...is-real-terrible.2144226/page-5#post-26597523
 
Meh, screw expensive phones, I use $300 or less phones just for calls, a flashlight, improvised mirror for looking behind things and to send pictures for parts requests. I don't game on it, I don't keep my life on it.
 
I have this issue with one charger and my iPhone 7. I’ve used the charger for six straight months with no issue, shortly after iOS 12 I was waking up to an uncharged phone. I swapped the charger and the problem went away, figure it was a charger issue... That same charger still works totally fine with my iPad Pro 10.5 though. Then I saw this video and yep, that’s my issue right there...



What a mess... They definitely fucked something up when it comes to detecting charge current in sleep mode.
 
NIZMOZ said:
No sir, all devices from 6-10s have that issue. You need to read MacRumors and many are having it on their older devices including my own household.

Your test is flawed, as you are doing something wrong. You may have the security setting turned down, or you have touch to wake up turned off. Those two things will make it work.

https://forums.macrumors.com/thread...ge-while-screen-is-turned-off.2144288/page-11

https://forums.macrumors.com/thread...is-real-terrible.2144226/page-5#post-26597523
Click to expand...
You need to read the title of the thread you have listed. The very first word in the title is SOME. I'm not about to go read 2 threads about someone else's problem when I don't need too. My phones are working just fine. I performed your test using your method and my phones worked fine.

Touch (It's actually called Raise) to wake is on. As far as security being turned down, tell me exactly which settings and I'll be glad to help you prove your point.
Apparently I'm not the one doing something wrong as my shit works just fine.
Sorry your having issues and glad to hear Apple addressed the problem and have a fix in the update.
Just because someone post something on the internet it does make it true.
 
I'd be glad if they just dropped Lightning and went to USB-C.

Of course that won't happen. Dongles for the Dongle God!
 
I have noticed this charging issue twice on my phone but I noticed it quickly enough that I didn't leave it 'not'-charging for any amount of time.

There is another bug that I'm a bit peeved with and that's with the stereo sound on the XS Max. Twice the ear piece has gone completely silent when playing videos, which results in mono right-channel only audio, and the only fix I've been able to figure out is to reboot the phone. Hopefully that is an acknowledged bug and gets fixed soon.
 
Ever since going from ios 6.x to ios 7 I always told people (I sold phones for 5 years) that you don't do the update until there is the x.1. Some people actually listened.
 
Baditude said:
You need to read the title of the thread you have listed. The very first word in the title is SOME. I'm not about to go read 2 threads about someone else's problem when I don't need too. My phones are working just fine. I performed your test using your method and my phones worked fine.

Touch (It's actually called Raise) to wake is on. As far as security being turned down, tell me exactly which settings and I'll be glad to help you prove your point.
Apparently I'm not the one doing something wrong as my shit works just fine.
Sorry your having issues and glad to hear Apple addressed the problem and have a fix in the update.
Just because someone post something on the internet it does make it true.
Click to expand...

Wow, you are clueless. Did you not read the thread? It's an IOS 12 bug, and been fixed in 12.1. ALL DEVICES are affected.
 
NIZMOZ said:
Wow, you are clueless. Did you not read the thread? It's an IOS 12 bug, and been fixed in 12.1. ALL DEVICES are affected.
Click to expand...
Not Clueless and not affected. Did you read my post? No I didn't read, don't need too. I understand it is a bug and it does not affect either of my phones nor my wife's or either of my daughters or my son's Iphones.
Sucks to be you.
 
BSmith said:
but, but, but Apple never makes a mistake. There must be a reason for this outside the scope of cognitive observation that Apple does this. One we mere mortals cannot see, nor comprehend. If Apple were to explain it to us, our heads might explode!
Click to expand...
I"ve used iphones for years, and Apple regularly screws up software. I skipped iOS 11 altogether and for 10 I didn't upgrade until 10.3.x was out. They had that antenna issue years ago (hwich may have reared it's ugly head again on the current version).

I'm sure there are still users that think Apple is perfect, but not me. Didn't think that before i used an Iphone don't buy that today. That said, when I switched around the 4s or 5 release it was generally a better experience than android. I always hated how horrible the settings were organized in Android. Also back then (not sure about today), firmware updates were controlled by the provider and providers often don't provide users with updates that are available.

The alternative was to hack the s/w and put a different version of Android, but you might lose features (while gaining others) and that's way beyond what most users can/will do.

It's all a matter of what you want. I have no doubt that Apples price structure is crap. 100 bucks (or more) for extra memory is ridiculous, but I still pay it...aside from the current round (and i still may return it rather htan open it and use it), is the only time I've bought a new phone. 6 months after release, I can find NIB phones for far less than NIB from Apple or a carrier.
 
NIZMOZ said:
It's a problem with the power save feature on the phone and security. If you turn off the security for the lightning port when locked, it will work. Only when it's on and the phone goes to sleep after a minute or two, it does it.
Click to expand...
So pretty much what I guessed. Good to know. If my case ever arrives (monday or tuesday), I'll crack the box open and give it a whirl (more than likely, but I still kinda feel like I should bring it to apple, get my money back and buy it early next year. I've saved hundreds each time I've done this since I started buying my phones (vs getting from work) in 2015.
 
Baditude said:
Not Clueless and not affected. Did you read my post? No I didn't read, don't need too. I understand it is a bug and it does not affect either of my phones nor my wife's or either of my daughters or my son's Iphones.
Sucks to be you.
Click to expand...

Laugh. Let me explain something to you. A bug in IOS 12 that affects ALL DEVICES, doesn't just skip a device like yours. You don't know how to make it happen or your configuration is different. End of discussion. It is a bug on all devices.
 
nilepez said:
So pretty much what I guessed. Good to know. If my case ever arrives (monday or tuesday), I'll crack the box open and give it a whirl (more than likely, but I still kinda feel like I should bring it to apple, get my money back and buy it early next year. I've saved hundreds each time I've done this since I started buying my phones (vs getting from work) in 2015.
Click to expand...

Yeah, they fixed it in 12.1, so as soon as that is released, it will go away. :) I mean to say only when its off and it goes to sleep. :)
 
The alternative would be an android phone, where an issue like this would never be fixed and they would just release a new phone a couple of months later and stop supporting the messed up one.
 
Cmdrmonkey said:
The alternative would be an android phone, where an issue like this would never be fixed and they would just release a new phone a couple of months later and stop supporting the messed up one.
Click to expand...
I can't imagine a bug like this could stay on android forever, but I suspect getting a fix would take longer than it will with Apple (mostly because carriers are piss poor at sending updates to android handsets).
 
Own an Xs. I have had none of these problems.

First, if cable flipping fixes it, either your socket is dirty as shit, worn out, or your cable is messed up. I suspect the people whining about that have a different problem.

As for the problem listed? Haven't had any issues with mine. I'm probably protected by my usage patterns. Because for charging I'm either in the car, in which case I'm hooking it up to listen to music as well, so no idle. I'm in the middle of using it and chewed through the battery (not really a problem on my Xs yet, but my clapped out 6 updated to ios12 it was), or I'm heading to bed where I plug it in and check the time and alarms.

Even beyond that, default behavior is raise to wake is on. To set crap like this off in that mode, you would literally have to use things like he does. Sneak up on it on a table and plug it in without disturbing it.

Not saying it doesn't happen, but that some people are just fucking odd in how they use stuff.
 
nilepez said:
I can't imagine a bug like this could stay on android forever, but I suspect getting a fix would take longer than it will with Apple (mostly because carriers are piss poor at sending updates to android handsets).
Click to expand...

It might not stay on the core android os forever, but serious bugs can and do stay on your particular piece of android using hardware forever. I've got several android devices that do bad things in software that have NEVER received an update ot fix it and also will never receive any more updates. I also get to deal with provisioning mobile devices for a large user base. Android WAY outraces apple in terms of problems that never get fixed.

Outside of genuine bugs in the OS, some of the bugs are an artifact of how android is given away to any oem. For example, device encryption and MDM policy compliance. Way back when this started as a core OS bug. Google did eventually fix it, however there is zero repercussion when a vendor alters the OS to lie about the device actually being encrypted. It's very problematic intended behavior. That being said, when the iphone X came out, we found an MDM compliance problem in iOS when used with MS device management tools. Although getting it taken seriously required some effort, Apple and MS sorted things out and we had a fix for it in ~6 months. We got years of the middle finger from Google with similar issues.
 
You must log in or register to reply here.
Back
Top