Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
I am still on my S100 with tt6 6.010 (7720) and no SIM since I currently use it solely for navigation. What I experience is not really a lockup but just a big delay (almost 1 min) after tt has initialized and only if "Enable wireless data" is enabled.
UPDATE
Turns out that this was a system resource problem. I have Wisbar 2 Advance, PocketBreeze 5, Phone Alarm, and PhotoContacts Pro all active on my device. I guess this is just too much to handle for the Omap when I try to add TomTom on top of that. When I exit WA2, PA and PhotoContacts, shut the device off for about 30 seconds, then turn it back on and launch TomTom, I have no problems. I have also been able to do it only shutting down WA2 and PhotoContacts, but it still locks from time to time like this. I have to shut down all three to be safe. Leaving PocketBreeze running (with some plug-in tabs active too) seems to be a managable workload for the processor. It's kind of a pain, but at least it works! It's not like I need a nav program every day!
Later...
Glad to know you found the source of your problem.
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
Have you tried to defragment your memory card of maybe even clear of any redundant registry entries. I was having issues not too similar to yours and I found that pocket mechanic was able to resolve some of the issues due to the card having so many redundant files and the registry. Give it a go using the demo may solve your issue?
Magic Button - Pocket PC Task Manager
This will CLOSE the program instead of MINIMIZING it to the background process.
JC#79 said:
Have you tried to defragment your memory card of maybe even clear of any redundant registry entries. I was having issues not too similar to yours and I found that pocket mechanic was able to resolve some of the issues due to the card having so many redundant files and the registry. Give it a go using the demo may solve your issue?
Click to expand...
Click to collapse
I only started putting things on the card two days ago - day two i started having tomtom problems.
I'll def give this a go though and let you know if any improvements...
Thanks!
i have the exact same problem with my dopod p800w/artemis etc etc......i found a way to eliminate the freezing and hanging.......rule of thumb is to open the program by going into its root directory and opening it from there, instead of opening it via the start/programs shortcut or today screen......basically just make sure you open the program by going into File Manager and look for the tomtom navigator.exe file (usually in the program files folder and then navigator folder) and open it that way......ever since i tried it this way i never get any freezing and the program would start all the time.......it works for me......
I know it's not a battery issue I have two that I bought at different times and it does this with both of them. The phone just keeps freezing no matter what rom I put on it. I've tried the default t-mobile 6.0 and all the custom roms from here. Here's what's happening, I don't touch the phone for a few days, leave it off and everything. When I turn it on it boots up fine, let it sit for a few hours to make sure it's working and as soon as I start doing things on it, the device slows down then freezes. I've tried overclocking the cpu a little just to speed it up but it doesn't help. So once it freezes I pull the battery and try to turn it back on but it freezes on the windows screen, the only way to get it to boot normally is a hard reset, which then it only lasts for a few hours. Any ideas? Is it completely shot at this point?
Than if it is not a battery problem than all I can think of is that there is a hardware problem.
Memory card it sounds like. Take it out and see if it works normally if so go get a new one. Flash memory cards are great but they dont last forever
Oh I would have never thought it would be a memory card issue... but hey that could be the case.
Similar Problem
My Dash has had 6.1 then I went back to 6.0 after having this problem:
Initially this would occur when I would try to access the internet, email, etc. it would just shut down. Now the problem occurs when in a call as well. The Dash shuts down. I would try to reboot but it reads my battery as dead. I tried different batteries, same problem. THe only way to reboot is to plug into recharge. It will reboot but still reads the battery as 0%. When I reboot on power after the initial reboot, it reads the battery as full again. I can keep the Dash on for awhile but, when receiving a call or when it tries to get email (not All the time, just most of the time) it shuts down again.
I took the phone to a repair shop and they replaced the circuit board but it still did the same thing. After reading this thread, the constant is the memory card. Could this be the problem?
Maybe, but it does sound a lot like a situation I had just a lil while back. I could feel the battery getting hot during use and have to leave my dash plugged in all the time. If I unplugged it the battery would die fast and it's prompt me to shut down. I end up testing a lot of things and found that after I removed OMAPClock from the ROM the problem went away. Now you say you went back to 6.0 after having this problem, did you go with one that had OMAP or install it seperately? Since I removed it I haven't had any problems. I still have the ROM I made to get rid of it. It's Rose 1.6 by Ricky & Stylez, only change is I removed OMAPClock from it. Let me know if you want to try it, I'll just need to upload it somewhere...
OMAP
Sure, at this point, I am wanting to have my DASH back! The problem right now is getting the laptop to recognize it and sync again after all the stuff that the shop did. It is not being recognized after their reflash
To get your laptop to recognize it, try this. With your Dash turned off and unplugged, hold down the camera button then plug in the sync cable. The Dash should load the Blue/Green/Red Boat Loader screen. You should then be able to reflash it with an Official ROM.
My Edited version of the Rose ROM 1.6 by Ricky and Stylez is here:
http://www.mediafire.com/download.php?mhm2t5yxqwm
This is to flash back to the T-Mobile Radio which i am also using:
http://www.mediafire.com/download.php?etj5mtatcm3
This is The SDA Unlocker:
http://www.mediafire.com/download.php?djgqnjnunuy
This is the ET9 Keyboard Fix Cab:
http://www.mediafire.com/download.php?motamjqzhov
This is the T-Mobile Dash WM6.0 Official ROM:
http://www.mediafire.com/download.php?tzmyujnywy0
Flash the ROM first, than flash the Radio.
Not recognizing the USB now
I think that the shop didn't connect something, it is not recognizing the USB now. It will charge but not sync or flash the phone.
I took the dash back to the shop to fix their fixing Hopefully, it will sync when I get it back (and they don't try to charge me for the repair!)
Is it possible that the problem is caused by a faulty SIM card? When I sync it, I will see if the problem persists after removing the memory stick.
The simple things are usually the correct things. memory cards cause all sorts of issues, Removing it is simple enough of a way to tell if it is the cause.
OMAP will drain your battery if you let it run all of the time, and the battery will get hot (as well as the processor) from over use. Simply turning off the over clocking when you dont need it solves that problem.
My bet is it is the Memory card, that would also explain the inability to use the USB sync, Windows first looks to see if you are simply plugging in a USB device, checks to see if it is / has a memory card then in the case of syncing (WM) it loads active sync or mobile center if it detects a compatable OS. If your memory card is bad Windows may never ever get past the memory card check and just sit there.
It's not my memory card, I've removed it and even tried a few different ones I had and keeps doing the same thing. I'm thinking hardware related and was actually looking into getting one with a busted screen off ebay or something to put my screen into.
hello! XDA. i recently bought an used sprint galaxy nexus. that came with android 4.2.1 stock. tha day i bught it i downloaded 4 apps (duolingo,templetun2,subway surfers and hilli climb racing) so i play these gams few minutes and when battery charge was low i plugged the charger but when i did it the games was running very laggy and after few secound the phone just freezes and reboot but when the SO started it get freezed again and it continuous happening like 10 times until i decided to take out the battery. so i put the battery and turn on the phone but happends the same, it just freeze. so i turned off the phone and go to sleep.
the next moorning the phone turn on good. but this time when i plugged the charger the phone reconize it good and get full charge. but when i decided to usb connect happens the same ,the phone freezes and all the reboot history i told you... but i unpluged and plug the usb cable many times and one of these my pc reconized the phone as a storage device and was charging it i tested 3 different cables and charging blocks.
when the phone freeze it becomes very hot on the top of it both camera and screen side.
after the many reboots the apps, didnt make any sounds neither my musics but when i go to settings/sounds and select the default ringtones they sounds good.
i get the conclusion that was a software or somthing like kernel issue so i unlock/root/ my phone and installed aokp jb-mr1 build 6. but bitter was my surpise when i saw the same usn/chargin issue goin on.:crying::crying::crying::crying:.
My conclusion is: for a reason i dont know .the usb and charger port its works random like 0.01% probability i plugg the cable.
another thing: i dont know if will work. when iplug the phone without the baterry in my laptop it shows a omap4440 on device manager and pop ups every secound.
so i heard XDA forum its one of the best places for help with android devices. i hope you can help me
.
Anyone???
Hi all, read many threads here and finally posting.
I have an xperia M (C1905 I think)
Short story:
As soon as I turn on this device within a few seconds I get the "Unfortunately, xxxx has stopped". I hit okay and within a second something else is stopped. This is repeated constantly for as long as I could tolerate waiting for. The odd occasion I have managed to get maybe 5 seconds between app crashing to navigate into the settings to try something out or check the album.
I am asking for help on what to do in order to access the files on the device. I really really want to save the images. I since has moved on to a Z and now a Z3 but at this moment I want to get the images. (Factory reset is thus out of the question). I rather leave the phone intact for years to pass until some technology makes it possible to retrieve the files.
Longer story:
I think this issue started occurring after an android update - which leads me to my conspiracy at the end of the post. Basically after an update I started noticing random apps being stopped/crashing without warning. Apps that weren't even being used. This happened maybe once a week, then a couple times a week. Seemed pretty random at first. Thus why I never took a moment to see the exponential trend and act fast to back up data. Over the course of a month probably, this just got worse to the point where an app of some sort is constantly crashing. It could be facebook, then gmail, then google, then a service, then homescreen blah blah anything and everything is crashing just so it can fill the screen. Multiple at a time. I hit ok and another appears or 5 more appear. Then I might get a glorious 4/5 seconds to browse the contents of the phone then boom another batch of crashes. The phone is completely useless right now, no way to navigate. Also, even with the phone turned on in safe mode or not, I cannot access the files whilst connected to my computer. The charging indicator shows up, computer recognises the device but on the odd occasion it does show up in "my computer" the folder does not open and the file explorer/documents just crashes. Xperia companion doesn't work either.
There was also an issue with charging/transferring media with the charge port. Bad connections but it was made better using the Sony original cable I have now. It charges alright now (instead of needing "the right" angle). Still, as far as I can remember data was hard to trasnfer, maybe I got 10 songs copied over before it stopped responding and had to cancel. All the files on the SD card I saved of course but the ones on internal storage are still there. I browsed the album for a few seconds and I just want to get them on my pc. I tried to copy to SD card but I can't perform that with the constant bombarding of crashing app error notifications that fill the screen. Also it seems like once the phone is on, I can navigate around (with the bombardment of crashing) but once the screen is allowed to time out it doesn't wake back with the power button. To mess with it again I have to pull the battery and put it back in. I have booted in safe mode to no avail, apps still keep crashing.
Please please help. I have USB debugging enabled if that helps? I just want to drag and drop my images and then the phone can sit in a draw. I am sure a factory reset would have it working back to normal but I can't lose the files.
Btw I think SONY is purposefully killing off these older devices. The phone worked flawlessly, yes it's older and not as fast but there was not a single issue (besides maybe the charge port wear). This issue with crashing is completely software related after an android update.
The phone is not rooted and no random software was installed (just social media and the like).
THANK you for any help!
Brad
Hey which rom are you using? do you have unlock your bootloader? if you are using stock rom and not unlock your phone bootloader then it can be resolve by using a software repair using sony pc companion.