Currently Being ModeratedJul 8, 2013 3:51 PM (in response to Halkier)
Me too. My iPhone 4s intermittently shuts down and displays the no power plug in symbol. It's dead until I can plug it in. But when I plug it in, it can show 70-80% power remaining, and if I then immediately unplug it, it works fine for ages before needing a recharge. It's hard to believe that this is a battery charge issue.
It has always happened to me when I use the camera app to take photos while GPS is on (tracking with the Cyclemeter app). But it's frustratingly intermittent. Usually I can take photos fine with Cyclemeter tracking, but perhaps once a week, this combination kills the iPhone.
It's **very** annoying. I'm now reluctant to use the camera app when the GPS is running, and I'm contemplating always carrying an external battery with me so I can restart the thing when it crashes.
Currently Being ModeratedJul 8, 2013 3:54 PM (in response to mollivan)
Your battery gauge needs to be recalibrated. Run the battery down until the phone shuts off. If it shuts off above 1% charge it for a minute or two, then run it down again until it really gets to zero. Then charge for 4 hours with the wall charger without using the phone.
Currently Being ModeratedOct 13, 2013 1:52 PM (in response to mollivan)
Did you ever find a solution to this? My 4s is doing precisely the same thing now. When I use the camera app it always shuts down even with battery level at 80%. And then shows empty until I start charging again and returns to previous charge. But it shuts down when using other apps as well. Might be a result of iOS 7??
Currently Being ModeratedOct 13, 2013 2:17 PM (in response to bromleynyc)
Hi, I never did solve this and have since moved on to iPhone 5. Don't have the problem anymore. All the stuff about resetting or recalibrating the batt. have never helped. I had the problem more or less right from the beginning. In cold weather the problem would get worse.
Currently Being ModeratedOct 13, 2013 3:32 PM (in response to bromleynyc)
I had this issue back on iOS 6 (and maybe before that), so I don't think we get to blame iOS 7 for this one.
Currently Being ModeratedOct 14, 2013 1:44 AM (in response to bromleynyc)
The problem is definately not caused by iOS 7 and unfortunately not fixed by iOS 7. It also happens to me more when colder (under 15 degrees celcius or so).
It is truly a shame that Apple can't listen to these problems and act on them. The whole iOS system will start to suffer a slow death by 1000 cuts if some of these smaller problems are not addressed in a reasonable amount of time.
This is obviously a problem that cause a great deal of frustration to a certain set of users.
Currently Being ModeratedOct 14, 2013 5:22 AM (in response to Kalvin1632)
I've had this occur occasionally with every version of iOS and every phone model. And I always have been able to fix it by recalibrating the battery gauge. I'm sure it happens because the phone "thinks" there is more in the battery than there actually is, so when an app that uses a lot of energy like the camera is launched the battery says "enough". I've had it happen with other apps sometimes; the have always been heavy power consumers. But my fix has always solved it.
Currently Being ModeratedOct 14, 2013 6:49 PM (in response to Lawrence Finch)
I tried Lawrence's suggestion (thanks!) early last week. Each time my iPhone 4s would shut down from lack of battery, I'd plug it in for just enough to have it turn on, then keep using it on batteries until it shut down again. I kept doing this for a good 20–30 minutes until it was really flat. Then I charged it up to full without touching it. I've not yet had my phone shut down when it's got some charge, so maybe that has helped (it might still be too early to tell).
However, I still find that using the iPhone camera app while the GPS in Cyclemeter is running often crashes other open apps (most annoyingly Filemaker Go 12, which when crashes loses the contents of the text field I was last using in the open record). Until I find a solution to that, I have to close down all open Filemaker Go databases before using the camera when the GPS is tracking. I forgot to do it again today and lost my entered text from a record. Perhaps this is a separate issue to the "battery crash" issue, but it's odd that this was what typically triggered my battery crashes.
Currently Being ModeratedOct 15, 2013 7:45 AM (in response to mollivan)
Definitely a separate issue. If you have Diagnostics & Usage enabled in your System Services each time an app crashes a report is generated. When you then sync the phone with iTunes that report is copied to Apple, who forwards it to the developer. You should also file a report with the developers. It is probably an undesired interaction between the multiple apps that are using the GPS. BTW, I love Cyclemeter.
Currently Being ModeratedOct 15, 2013 3:03 PM (in response to Lawrence Finch)
Thanks Lawrence. I just checked and I've got Diagnostics & Usage turned on. I might post something on the Filemaker Go user forum (I haven't found anyone else mentioning this yet).
(Yes, Cyclemeter's great.)
Currently Being ModeratedOct 15, 2013 3:05 PM (in response to mollivan)
By the way, I made a mistake in my earlier post. I'm not using Filemaker Go 12 but the earlier (paid) version, 11.0.2.
Currently Being ModeratedOct 16, 2013 2:53 AM (in response to Halkier)
Got the battery replaced on mine and it solved the problem. Apparently the battery had leaked and that is what was causing the problem.
Currently Being ModeratedNov 18, 2013 11:32 AM (in response to Halkier)
I have the exact same problem...iphone 4S shuts off when using the camera and shows battery drained even when there was charge left. The only way to restart is to plug in to a charger. Very annoying since it's left me stranded with no camera and I totally missed the shot I was counting on. And especially since the battery really has a charge. Any solutions? I purchased a new battery and am planning to replace mine. I will repost if this fixes it.
Currently Being ModeratedNov 18, 2013 2:28 PM (in response to frattwins)
The solution has already been posted to this thread. It is probably not a bad battery, but a battery gauge that needs recalibration.