I never had that issue before with my iphone.
Did you try all other methods of fixing this like restore etc...
Did you try all other methods of fixing this like restore etc...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iPhone update 1.0.1 is OUT!!!!
- Thread starter angrygolfer
- Start date
- Sort by reaction score
First bad news...
Safari still crashes. It took more surfing to make it happen than usual but it still happened. I was listening to music in the background and the music didn't stop playing...so I guess that's good - although that rarely happened.
I hope in some way, my Safari crash was due to a unique condition that they didn't test yet because if it keeps crashing in the next few days, I may have to switch back to my BB Pearl until the next release.
I was so excited and now...not so much
Does this happen when you are browsing using wifi or edge? I have heard from other users that this was fixed for them while browsing using edge.
Sadly this happened while on EDGE...I was on a high and then BOOM as Jobs would say, Safari crash brought me back to earth.
I don't mind it happening even once in a blue moon (i.e. once a month or so) but anything more frequent than that is really annoying. Maybe I'm spoilt or have been lucky but the Blackberry devices I owned never had app crashes like this ever.
as long as they dont use a mac.......
(and no, i dont run boot, parallels or anything similar. OSX ONLY).
I think theres many other variables that have to do with the crashing and its not the same with every user, phone, settings etc...
I been using my Iphone thru edge and wifi and only crashed on me 3 or 4 times so far knock on wood.
I do regural shut off and restarts every day or 2. clear cash and cookies every week. Dont open up 10 safari pages, try to listen to music, make phone calls and many other things at once.
Any computer will freeze or crash if you over push it nevermind a cellphone.
I been using my Iphone thru edge and wifi and only crashed on me 3 or 4 times so far knock on wood.
I do regural shut off and restarts every day or 2. clear cash and cookies every week. Dont open up 10 safari pages, try to listen to music, make phone calls and many other things at once.
Any computer will freeze or crash if you over push it nevermind a cellphone.
This is a really wide problem that a lot of people have had, and it's not really a problem, just a little software bug. The battery is charged all the way but the phone reports it as slightly not, like 98% or something. This will also cause the phone not to reset how long it's been used or in standby since the last full charge since the phone doesn't report that it has been fully charged.
Yes, its not available for macs yet.
He said that he's working on a mac version so hopefully the mac guys can enjoy it also soon.
Its very easy and simple to use.
He said that he's working on a mac version so hopefully the mac guys can enjoy it also soon.
Its very easy and simple to use.
That sucks, so you tried everything and still nothing?
Maybe take it back to an apple store and have them take a look at it.
Maybe take it back to an apple store and have them take a look at it.
Just like everyone else that used iFuntastic had to restore.
It was fantastic while it lasted but for now I am switching to iphoneringtonemaker since everyone that used that program did not have a problem. Back to reloading everything.
Ya, they said it was a known software bug and it would be fixed in an update. I'm pretty sure Engadget or someone had a little bit about how all the phones in an Apple store had the same glitch and they had tested three phones and battery life seemed fine even though they never showed a full charge after being charged all night.
Wow, sounds like a pain in the ass.
Does the battery charge and work fine though? Is it just a display issue where the battery is fully charged but the indicator doesnt display it properly.
Does the battery charge and work fine though? Is it just a display issue where the battery is fully charged but the indicator doesnt display it properly.
For me, the answer to your question is yes. I've never had the big battery glow, and it has never indicated a full charge... and I've never had the usage stats work (always showing "--")... but I DO get outstanding battery life, so I figured it was a software thing and have been waiting it out.
Tonight, when I started the update I had a large green battery showing 30-40% charged. AFTER the update (only 5 minutes later and still on the charger/dock) and after it rebooted it was showing much less, red and gave me the "less than 20% warning"...
Will see tomorrow morning if I have a REAL full charge
Good luck bro, hope it goes green all the way
For me, the answer to your question is yes. I've never had the big battery glow, and it has never indicated a full charge... and I've never had the usage stats work (always showing "--")... but I DO get outstanding battery life, so I figured it was a software thing and have been waiting it out.
Tonight, when I started the update I had a large green battery showing 30-40% charged. AFTER the update (only 5 minutes later and still on the charger/dock) and after it rebooted it was showing much less, red and gave me the "less than 20% warning"...
Will see tomorrow morning if I have a REAL full charge
Yep, that's totally the deal. Battery life rocks for me it just never displays it at the glowing super full charge status, just a tiny tiny bit under full.
Yes, that is new. I even had someone verify it before they updated their iPhone. I'm so glad it was added but it's odd that it isn't mentioned in any of the new documentation. And I would think if they have the ability to add that BCC feature, they could easily add a BCC for Recipients as well, no?
Maybe they weren't supposed to release it yet?
I'm thrilled to hear that the update seems to bring more reliability. Maybe this will make AAPL a bit more reliable tomorrow? It broke my heart today!
I have the battery status issue as well, but turning off wifi before charging it allows it to fully charge.
I used iphoneringtonemaker too and my 12 ringtones are still working...didnt force me to go into restore or anything (maybe that will be addressed next time 1.0.2 hopefully not)... and i saw no noticable difference in alert/ringtone volume mine is the same...
oh and I would really like an update with the ability to sms text multiple contacts the same message... I miss this function...
Used iFuntastic and i have to restore...
my question is, do u choose to reload your back up of info, or start a new iphone or whatever it says when you guys restore ur phones?
my question is, do u choose to reload your back up of info, or start a new iphone or whatever it says when you guys restore ur phones?
The good news, I think... is that I can almost guarantee you, that if you used your iPhone Safari in the same way you used your BB Pearl to browse the Internet, your iPhone Safari would likely never crash. Cheifly because you can have up to 8 tabs open concurrently, handling complex Javascript and Stylesheet executions as well. You also need to use "Switch applications" if you expect the browser to keep running when you leave it downloading a big page.First bad news...
Safari still crashes. It took more surfing to make it happen than usual but it still happened. I was listening to music in the background and the music didn't stop playing...so I guess that's good - although that rarely happened.
I hope in some way, my Safari crash was due to a unique condition that they didn't test yet because if it keeps crashing in the next few days, I may have to switch back to my BB Pearl until the next release.
I was so excited and now...not so much
Because I generally never turn my phone off (usually just putting it to sleep, or leaving it charging while playing something), I think the memory tends to get somewhat fragmented over time, causing difficulty later as it does house keeping. Simply shutting the phone OFF once in a while cures this nicely. I'm sure my iPhone has gone for at least a week without being shut off. The moment I get a couple of Safari crashes, I switch it on and off (takes about 30 seconds).
If your crashes are THAT frequent and annoying, I'd love to know either what webpages you go to, or whether your phone has a particular problem you might need looked at. Plenty of other reasons to go back to a BB Pearl... I can't believe "better web browsing" (even IF you're only talking about "stability") would EVER be one of those reasons. Just can't... sorry.
Personally, I'm still waiting for my Safari to crash again after the update. Mm, good.
~ CB
I had the battery & usage stats problem from the very first day i bought my iPhone way back on June 29th. I called Apple the following Tuesday to report the problem, they gave me the option of sending the iPhone back, go to the closest Apple store (150 miles away in Memphis, TN), or wait to see if it could be resolved with an update.
I decided that I would wait to see if an update would resolve the problem.
The update has corrected all issues regarding the battery and the usage stats.
jailbreak still works after the update.
There is a slight problem though.
Originally when pressing and holding Home and Sleep, you would have to release them before jailbreak would go to "sending more files", the program seems to automatically start sending the files once the Exclamation Point screen comes up on the phone. If you do not release the buttons fast enough the jailbreak will fail and tell you that
"Problem with Ditto: 6
Sorry, apparently things just didn't work out.
Look on the bright side, if jail was that good for Paris maybe you should give it a second chance."
So this time as soon as I saw the Exclamation Point screen I released the buttons right away and everything works now
Just a little FYI.
-Derek-
I was having problems with that ditto: 6 message as well, i will have to try and let the buttons go faster like you said. Luckily i was able to put all the hacks i did before the update back on my phone. I was pretty dissapointed that the hacks i did kind of screwed up the update process. I got the error message like everyone else mentioned. I hope i wont have to do this after every update.