Mine seem to do this everytime I reboot. As well as media scanner. What is all this??
I don't know but I am getting
the time auto update thing about every five minutes while I am watching Avatar. Pretty annoying.
Yeah, it does it on boot, but never after that.
Mine has only started the auto-update of time and date thing since applying the GPS 'fix'. It has slowed my boot time from mere seconds to ~1min, accompanied by low FPS (~1-5 max) until the tests are all complete.
Jon C said:
Mine has only started the auto-update of time and date thing since applying the GPS 'fix'. It has slowed my boot time from mere seconds to ~1min, accompanied by low FPS (~1-5 max) until the tests are all complete.
Click to expand...
Click to collapse
mine does what you describe, the whole process do take about a min now from power on to usable state. But the thing is, It was doing this way before the GPS Fix. Im not exactly sure but it might have to do with the amount of programs installed in our phone.
My phone's been doing the choppy thing since I added 10gb of music and all my standard apps. It's because it has to register so much data, not because the GPS is pinging a different server. That's like filling up your car's gas tank, getting a flat and blaming the flat on bad gas.
Wrong thread sorry...moderators please delete my post...thanks
I have searched through XDA and read all the threads regarding the 'suspend process' issue. The specific issue is outlined in Issue # 11126 on the Google Code/Android project home...
http://code.google.com/p/android/issues/detail?id=11126
I am trying to get to the bottom of this, as best as possible. For all intents and purposes, this really appears to be a mystery. Ultimately, it appears as though there is (currently) absolutely no specific reason a to why 'suspend' runs wild until the device is rebooted.
My question is (I know we can all only speculate):
Is there any chance that this could be Google account-specific?
The reason I ask is, I've been doing some "testing," just to try and make sense of this for myself. Here is what I've done/come across thus far...
- My fiancee's first MT4G was a black one manufactured in Taiwan. It had the inferior LCD-SH-C2 screen. Her battery was draining VERY quickly - i.e. before noon, without using the phone for much else other than texting.
- I enabled USB Debugging for her, to "rule out" the init process issue.
- Even though she only had Handcent, Facebook and Angry Birds installed, I removed all of them, leaving only Watchdog.
- I factory reset her phone, twice.
- For all of the above, the device was not rooted. I have since rooted her phone via the steps in this thread.
I'm in the process of creating a new Gmail account for her, exporting ONLY her contacts and then using that account for her new MT4G (Plum) that's scheduled to arrive today. I'm actually thinking of NOT using her new Gmail account at first though, so I can use her original Google account on this new, clean device and see if the suspend issue persists.
I might just be wasting my time, but I enjoy doing this and I don't think it's a complete waste to try and find SOME constant here. Am I nuts for thinking it's tied to the Google account? The Google account seems to be a black box of sorts. There is more than just contacts, apps and settings, yet there is no "window" into everything else that comes down - e.g. I can't log in to Gmail and "configure" it to not restore her wallpaper or WiFi settings. So that's why I say it's a black box of sorts, since it's doing more in the background than we have control over.
Nothing is truly random, at least not in the context of Android and the hardware affected. There has to be some reason why users of various devices, either do or do not experience this issue. Whether it's a specific action or the something that differs between one person's action vs. another person's, there has to be SOMETHING that's triggering this on her device, yet never triggers it on mine. I guess I'm just trying to flush everything out and hope that discussing it will help rule out/rule specific variables.
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
mwelliott said:
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
Click to expand...
Click to collapse
According to XDA and Issue #11126, you're not alone.
What's really bugging me is that neither my first MT4G, nor its 1st replacement or its 2nd replacement, have ever done this. My fiancee's first phone did this. She is now using my 2nd replacement while she waits for hers to arrive (today). So a device that never exhibited this issue, over the course of at least a week of normal-for-me use, started exhibiting this issue for my fiancee maybe a day or so after using the phone.
I thought I had "solved" it when I didn't see it crop up the first day she used my replacement phone. She was quick to let me know I was incorrect.
So I've got serious pressure here - all of my MT4G's haven't exhibited the out of control 'suspend process' issue while I was using the devices, but with her, it does. <queue the jokes>
We own our own business, so we're in the same room all day long while we use our phones. I was the first to tell her, "it's something you're doing." I'm only repeating myself by saying that I blamed it on an app she installed or something she "did" to cause it. After factory resetting, what...2, 3 times...I'm starting to forget; after checking the apps that are installed (and removing all of them); after verifying every setting from USB Debugging, screen brightness, account sync, etc. I seem to at least be able to say, "every single setting, shortcut, widget, app or usage pattern, does not produce the issue on any device I have used with my Google account, whereas it does with my fiancee."
That's the most difficult part to get absolute - the usage pattern. She's doing such basic things though, but I know that even the slightest of difference can produce different results.
I will most certainly report my results, futile or not.
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Chadastrophic said:
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Click to expand...
Click to collapse
That seems to be the constant, to a degree. I'm seeing people state that they're having this issue on anything from the Samsung Galaxy S (i9000) to a Nexus running Cyanogen 6.1. That's people stating it though, so I'm not sure if they're actually experiencing the same issue or not.
I am biting my tongue, but I think I found another common denominator...I am going to post back in a coupla days once I've seen it last for this entire week.
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
zero_oli said:
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
Click to expand...
Click to collapse
Yeah, it didn't seem 100% related to devices running Sense, so thanks for posting back to this.
My fiancee was experiencing this across her first two MT4G devices and has yet to experience the issue on her third and final MT4G. I want to see it run the rest of the week though before I share, but the issue did pop-up for her pretty much within 24-48 hours on her first two MT4G's.
Shlongwoodian: I have been following your posts as the "suspend" process has been affecting me since I received my phone the first day available. However, I am reluctant to send for a replacement as all else is great on the unit I have and there seems no gaurantee that a new phone fixes this issue.
I have tried Tmo and HTC and both seem clueless; therefore, I appreciate your research and look forward to any "fix" short of waiting for Gingerbread.
Anyone have any wisdom to pass on? This issue is driving me crazy! I've noticed it most on my black MT4G (w/the good screen) after browsing the web, youtube or using the media player. My wife's red MT4G (w/the inferior screen) has had no issues and her battery is amazing! The first day she got her phone her battery lasted 24 hours without even conditioning it! Granted she doesn't use it like I do mine, but it is still a huge difference. When this issue comes up on mine, I'm dead within 3-4 hours. I have Watchdog set so when it alerts me I just soft reset. That clears it up until it decides to come back at random intervals. It usually doesn't come back until I open the browser, etc. With as much as I use my phone (I am constantly on the road), it becomes a major pain to have to constantly monitor battery life. Any help is greatly appreciated!!!
Man, I am sorry to report that I gots nothin'. Ok, here was my original theory...
I was speculating that "something" inside the Google/Gmail account was the cause. My reasoning being, essentially, your info is stored in a database. When you get an Android device, that online database is synced locally with the phone's database. We each have different databases and there is more than just your apps, Market links, contacts, etc. I never exhibited the /suspend issue on phones that she experienced the /suspend issue on. I figured it was database-specific.
If a table contains a value, or rather, does not contain a specific value (or if columns are missing, etc.), it can cause an application to respond in a negative way. Sometimes, this causes an error to bubble up in an application. Other times, it doesn't. In my experience, I've seen much more subtle issues in databases, that don't cause errors or a crash, but instead just cause "undesirable results."
When my fiancee got her final, good replacement Plum Glacier, we started with a completely new Google account. We thought we nailed it, when a handful of days passed without seeing /suspend get out of control, leading to Android System and/or OS sucking down battery life. I think it was nearly a week into it and one day while she was out, she realized she lost battery life really quickly - i.e. left the house with 90% and by the time she got to the store, shopped for a bit and looked, her phone was down to like 30-40%. She knows how to check for /suspend and it was, of course, back.
It's still not something that can be completely ruled out, since it's not a very air-tight test. There could be something about my Google account (which I've had pretty much since Gmail beta was available) that's keeping me (and others like me) from getting it or that idea could be crap.
For some reason, I have never, ever seen this happen on my Glacier(s) running stock 2.2.1. Phones that I never saw the issue on, she saw the issue on. There is so much speculation around it, but it just seems like "some people" don't experience it and "some people" do. It's all over different devices, different skill levels, etc. No apps, same apps, whatever and it happens to some but not others.
Sorry to get anyone's hopes up. I'll keep looking for differences/similarities though and if I find anything at all I'll - or if anyone else finds anything, no matter how ridiculous it sounds (yes, we've tested the 'rock' and it doesn't appear to suffer from the /suspend issue) - post it here.
Thanks for trying! It was a good theory. So . . . now what? Is there any way to get this ranked higher with Google, HTC, etc. to get more people working on it? It is really driving me nuts! It mainly happens after I use the web browser, then put the phone on standby for some reason. I can't even use the browser any more without needing to reboot it to save battery life. There is another thread, but specifically for the Evo and I think one for the Nexus one, all with the same problem. What if a new thread were started that is not device specific? That way we can get more people to star it and maybe Google or whoever will pay more attention to it! I would hate to think that we are stuck with this problem until when and if we get upgraded to 2.3. I would suggest rooting and flashing a new ROM, but even those with custom ROM's are having the same problem, so that's not going to help. Thoughts???
jpiano said:
It mainly happens after I use the web browser, then put the phone on standby for some reason.
Click to expand...
Click to collapse
It truly is a mystery to this day. I've seen people say, "it happened right after I installed Handcent" or "it happens as soon as I do..." No one has come up with any concrete evidence thus far.
My fiancee has Handcent, I have Handcent. I used Handcent heavily, never had an issue. She stopped using Handcent - still has the issue. We've gotten so granular in our troubleshooting, we're literally tracking every step. LOL i.e. I pressed the trackpad to wake the phone, once; I unlocked the phone, I swiped my thumb once to view my Watchdog Widget on the screen to the left of my homescreen, etc., etc., etc.
So, for now, we just wait? My phone (and all previous phones) have been just fine. My fiancee however...yeah, I'm trying to find a fix pretty quickly.
One common theme that I've seen with this issue is that it only happens after I put the phone to sleep. I have never seen it crop up while actually using the phone. Maybe we're going about it the wrong way in trying to identify an app, etc that's causing the problem... perhaps it is simply the code involved in putting the phone to sleep and that's why there hasn't been any consistency with what one does to make it appear. In your experience, have you ever seen or heard of it showing up while the phone is being used? Perhaps it's just on mine that it works that way, but I thought it was worth mentioning. I know nothing about code or how android works so please forgive the noob comment if this is an obvious one. Merry Christmas!
I've got this problem big time. Returned my first phone because I thought it was the phone. First few days were good but lately its back and as bad as ever. First thoughts were angry birds twitter or wifi but I have no idea. If I can't figure this out I might have to sell this phone.
I will try to post some more thoughts. I think you're onto some good ideas here.
Sent from my HTC Glacier using XDA App
(Re-posting from the developer's Google blog where others are following this issue): Interesting about using the phone without a Google account. Not sure if this is relevant or not, but I've noticed something else with consistency. Granted I wasn't able to document the behavior through system panel at the time, but this has consistently happened. When suspend goes crazy, I can get it to stop simply by charging the phone! Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot. Noob speaking here but perhaps the part of android that actually logs the battery usage is suspending when the phone goes to sleep? When it us charging, this log is reset and clears the process from running. If this is even possible, then could someone write an app that clears this system log? Maybe by mimicking what happens when the phone is charging, we can at least temporarily clear the issue without the need tovl reboot? Again, I know nothing about all this so sorry if this is all irrelevant. Just sharing what I've noticed to be consistent. Thoughts??
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
jpiano said:
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I wonder if you're on to something with the SD card. I've been thinking I haven't seen the suspend issue return on my phone in quite a while. I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems. For those who are having the problem still, I wonder if removing or formatting their cards would show any improvement? Worth a shot if at least to eliminate another possible factor.
Sent from my HTC Glacier using XDA App
That's cool that this thread is flushing out other ideas and possible variables. I like the idea of connecting it to the charger for a couple of seconds, but my fiancee is so used to just rebooting her phone each morning and sometimes again by mid-day, that it's easier for her to do just that.
jpiano said:
Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot.
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I like the microSD Card notion. This is such a weird issue, that it's so easily associated with other items - e.g. applications, usage patterns, etc. This seems feasible though, but the only way to know for sure is to reproduce it. My fiancee experiences the suspend issue daily, if she doesn't reboot regularly. So, I should be able to take her microSD card and use it in my phone and get the suspend issue. I don't want to 'muddy' up by swapping microSD cards, so I'll try reformatting her card and see if that makes any difference. She usually sees the issue within 24-48 hours of a fresh boot, so it shouldn't be long before we see if that fixes it or not. I can check the card for errors, etc. as well.
werk said:
I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems.
Click to expand...
Click to collapse
I'll be upgrading to a 16 GB Class 10 soon, so I can give her my Samsung if need be. I'd really like to see if this is it though. It would explain the "some people get it and some people don't" pattern.
I also noticed that the minute I plug the phone in the problem goes away. Not sure why, just confirming it happens to me too. I also should note that when I returned my phone, they popped my old SD card into my new phone. So if there is an SD card issue with a corupt file/photo that could be something as well. I wonder woody if your girlfriends phone has had the same SD card after how many times did you say you traded it in? BTW, a side note, how did you exchange it so many times? After I took mine back to the store on day 14 they told me I wasn't able to exchange it again.
I do have a 16GB SD card but just haven't had time to install it. Wanted to double check which things I need on the new one from the old one, but it might be a good way to test this issue. Let me know some ideas before I swap the cards and maybe I can help test this.
Also, one more thing, what is the app you're using to log stuff? I'm just using Watchdog Lite right now.
I've got to figure this out or this is a dealbreaker for me. I have waited 3 years to upgrade phones, first time on Android, really wanted iPhone but wanted to stick with month to month from TMob. If this continues I think I will move to Windows Phone 7 or iPhone if I have to, but I really like this phone when the battery is not draining like a leech.
Thanks.
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
royhobbs said:
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
Click to expand...
Click to collapse
Just straight copied the existing files over from the old card to new one (new one in phone connected via USB, old card in SD adapter in my laptops SD card slot). I think some Angry Birds files didn't make it due to long paths, but reinstalled it and no problems since then.
Can anyone else who has an Xperia Play help me out here? I got the phone this past Tuesday. At that time, it loaded up rather quickly. Now when I turn it on, it takes over 3 minutes to load up. I literally turned my Nexus S on at the same time and I could have powered it on and off 3 times in the amount it took for the Play to load. It sat on the Sony Ericsson screen for like 2 minutes and then another 1 minute after the SE circle logo appeared.
A few details:
1. I am currently in the US on vacation using my Japanese SIM card. Thus I am roaming. The data is turned off however the phone network obviously isn't. When the SIM is out of the unit it loads up much faster.
2. The phone is not rooted.
Has this happened to anyone else? Is there any way to check if there is so kind of malicious program or something that was installed?
My xperia start up load time is aproximated to 3 minutes too.
Jep, same here. The OS is verry fast after the 3 min boot...
It takes a while to boot. Samsung I know have been targeting efforts to get the boot faster. Top of my head I remember them talking about trying to get the fastest boot time on the galaxy II.
Sent from my R800i using XDA App
I believe some Samsung and HTC phones are not actually "rebooting". They are going into some sort of hibernate.
My buddy has an HTC mytouch, and he was having crummy performance. I looked at his uptime, an it was over 1500 hours. I told him that's his problem, he should probably reboot.
When he did, I noticed it rebooted very fast. Performance was still in the crapper, and curiosity had ne check his uptime even tho it should have been reset after the reboot. It was still at over 1500 hrs. Then I realized it didn't actually reboot, just went into a hibernate explaininng the blistering fast reboot time.
Sent from my DROIDX using Tapatalk
WOW...so everyone else is having this issue as well? But it must have something to do with the amount of free storage on the phone, because when it was over 100MB it loaded up much quicker I've noticed.
Also on a side note, with respect to phones and hibernation...
My Desire HD has this issue. If you select "Shut Down" then it takes about all of 10 seconds to start back up. Yet if you select "Reboot" it takes almost as long as the Play. Clearly shut down is hibernation, especially since if applications have crashed or stopped working, shut down does absolutely nothing and thus I need to literally reboot to get them running again.
Finally, in my thinking there was something wrong with my Play, I formatted both the memory and the SD card. Can anyone confirm what was pre-installed on the SD card that I have lost? I noticed Crash Bandicoot was stored there but it can be re-downloaded simply by running the application. I know there are some sample pictures and music and possibly video as well, but anything important?
TokyoGuy said:
WOW...so everyone else is having this issue as well? But it must have something to do with the amount of free storage on the phone, because when it was over 100MB it loaded up much quicker I've noticed.
Also on a side note, with respect to phones and hibernation...
My Desire HD has this issue. If you select "Shut Down" then it takes about all of 10 seconds to start back up. Yet if you select "Reboot" it takes almost as long as the Play. Clearly shut down is hibernation, especially since if applications have crashed or stopped working, shut down does absolutely nothing and thus I need to literally reboot to get them running again.
Finally, in my thinking there was something wrong with my Play, I formatted both the memory and the SD card. Can anyone confirm what was pre-installed on the SD card that I have lost? I noticed Crash Bandicoot was stored there but it can be re-downloaded simply by running the application. I know there are some sample pictures and music and possibly video as well, but anything important?
Click to expand...
Click to collapse
Samsung and HTC 'cheat' quite a bit when it comes to startup times. If you compare the time the Nexus One take with that of the Desire, the Desire is much faster, despite the hardware being the same. The same holds true with the Galaxy S and Nexus S.
From my experience with the Nexus S, I'd say the Play is VERY close to Stock Android 2.3.2. Sony Ericsson just added a few apps here and there and skinned the UI a little, but it feels, works and behaves a lot like the 2.3.2 on the Nexus S. Sooo... I'd say the long boot time is normal, and probably for the best for the device.
boot times are about 3 min as well.... however I find this to be a non-issue to me.
how often are you rebooting your phone though? Mine might go for weeks without being restarted... pending battery doesn't die on me of course
TokyoGuy said:
WOW...so everyone else is having this issue as well? But it must have something to do with the amount of free storage on the phone, because when it was over 100MB it loaded up much quicker I've noticed.
Also on a side note, with respect to phones and hibernation...
My Desire HD has this issue. If you select "Shut Down" then it takes about all of 10 seconds to start back up. Yet if you select "Reboot" it takes almost as long as the Play. Clearly shut down is hibernation, especially since if applications have crashed or stopped working, shut down does absolutely nothing and thus I need to literally reboot to get them running again.
Finally, in my thinking there was something wrong with my Play, I formatted both the memory and the SD card. Can anyone confirm what was pre-installed on the SD card that I have lost? I noticed Crash Bandicoot was stored there but it can be re-downloaded simply by running the application. I know there are some sample pictures and music and possibly video as well, but anything important?
Click to expand...
Click to collapse
Would like to know what was on the memory card originally as well as I formatted money when I got it...
Sent from my R800i using XDA App
Just to ease your mind both my Motorola phones the X and OG were a couple min to boot up.
Sent from my DROIDX using Tapatalk
I noticed the boot times too, expecially since I don't really charge it much, I run it out and swap batteries as I have an excellent spare battery and charger also know as an x10 alway 3 minutes or so though, probably part due to drm checks, and part due to the storage almost full and it having to go through all the apps and initialize them.
To be honoust i have the phone for a few weeks now and only turned it off and then on for a few times. Boot time doesnt actually bother me.
Ever since the latest update (which I totally love), my phone takes over 4 minutes until the startup splash screen disappears, and then another 1.5 minutes until things are useable and not jittery. It used to take half as long before the update. Aside from the dreaded wipe and reinstall everything, is there any other solution? Is there a software that will log what is taking long during startup? My phone is not rooted.
Anyone else notice their startup time doubling?
ozaghloul said:
Ever since the latest update (which I totally love), my phone takes over 4 minutes until the startup splash screen disappears, and then another 1.5 minutes until things are useable and not jittery. It used to take half as long before the update. Aside from the dreaded wipe and reinstall everything, is there any other solution? Is there a software that will log what is taking long during startup? My phone is not rooted.
Anyone else notice their startup time doubling?
Click to expand...
Click to collapse
If you're talking about sense 3 then yes. It is a heavy update and i believe heavier than previous sense that is why you're facing this problem. If you want speed, get custom sense roms...and you won't have this problem.
Official roms are full of junk, for people because not everyone uses everything so to provide every use of the device, official rom provides heck a lot of services, apps to the users but no one uses all of them that is why it takes time to load all of them when in custom roms, bloat is removed so that users can enjoy the speed.
ozaghloul said:
Ever since the latest update (which I totally love), my phone takes over 4 minutes until the startup splash screen disappears, and then another 1.5 minutes until things are useable and not jittery. It used to take half as long before the update. Aside from the dreaded wipe and reinstall everything, is there any other solution? Is there a software that will log what is taking long during startup? My phone is not rooted.
Anyone else notice their startup time doubling?
Click to expand...
Click to collapse
had the same issue, had to hard reset and its super snappy now
I was really hoping to avoid a hard reset, and all the hours involved reinstalling the apps and changing app and system settings.
I keep getting this message on my N7 every once in a while, when I never opened the application in the first place. How do I fix this, and could this be draining my battery life?
map crash
UnixxinU said:
I keep getting this message on my N7 every once in a while, when I never opened the application in the first place. How do I fix this, and could this be draining my battery life?
Click to expand...
Click to collapse
I am also seeing this on my xoom after I updated to stock Jellybean.
I get this on a pretty regular basis as well. By pretty regular I mean once every day or two (as long as I'm using the thing) - and I don't even have to touch Maps to get it.
I can have freshly booted it up, used it all day, never loaded maps once, be using it some more then next day and then Maps crashes...
It's kind of annoying, it interrupts me in the middle of doing things sometimes but not any one thing in particular that I could narrow it down to being related to.
A new update out for maps today. Hopefully this fixes our crashing.
Nope, no fix... still doing it, no change in frequency that I've noticed. Is really no one else experiencing this? Its difficult to troubleshoot if its being caused by conflict with some other app as it happens not often enough, like every couple of days.