iPhone 18 Pro a 18 Pro Max It has only been on sale for a little over two weeks, but it has already encountered a few more or less annoying bugs that are plaguing some of its owners. And while the problems with random reboots associated with Face ID or crackling in the speakers avoided me, I came across my iPhone 18 Pro to another error, which fortunately can be fixed temporarily and quite easily. In the last few days, the phone has woken me up several times at different times of the night with a repetitive vibration signaling the start of charging.
You might be interested in
At first, I honestly had no idea what the problem could be. iPhone 18 Pro because I charge on the same wireless charging station as iPhone 17 Pro, and I didn't change its power supply or anything like that. And since the phones don't differ in terms of charging standard support and my stand supports Qi2.2, the problem seemed quite unlikely to me. Of course, I tried using a different power supply and then a different charger to see if my solution was broken, which it wasn't.
Gallery
The explanation of the whole plot wasonec much simpler and easier to repair, albeit from the side Apple a corrective update will need to be released. Specifically, I found that the constant "starting" charging and subsequent immediate termination was apparently caused by the activated Optimized Charging function from the Battery - Charging section, which is supposed to extend the battery's life by simply charging it fully (or to the limit you preset) just before you need to start using it fully.
You might be interested in
I don't know if optimized charging was wrong in estimating exactly what time charging should be resumed, or if there is something else behind the problem, but the fact is that when I deactivated this option a few days ago and my phone was thus charged to 100% without any charging "gaps", the vibrations signaling the battery start disappeared. So if something similar is bothering you, it's worth trying to turn off this setting, because it's possible that it's bothering you too. However, I've already fixed the error via the relevant website Apple reported it and now I'll just hope that the developers will look into the problem sooner or later.
