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......
Related
I am just wondering if I am alone with this problem because I can't find anyone with similar problems.
When I put the phone in the cradle when its off, after a minute or so the phone turns on and ActiveSync starts. This is obviously very annoying because it syncs when I don't even want it to. I have never had this problem with my wallaby only my blue angel.
I have gone throught the settings and turned off any automatic sync options but still it does it. Have I missed any options or am I doing something wrong?
Thanks, Ian
Not to be one of those 'oh! I have that problem, too!', but you asked if any others are having this problem, sooooo....
I've got the same problem! I notice that this happened with other USB devices, too. I had an IPAQ that did the same thing. It would power up when connected to the USB, even after a few hours.
What I think is happening is this:
I think that the USB lines are separate from the lines that the charger connects to (someone correct me on this?). There are 2 lines on USB for voltage, the other 2 are signal I think. So, when the device sees a voltage on the USB line (like when you first plug it in), it turns on. Perhaps the USB is changing state for some reason, causing the thing to turn on?
To keep it from sync-ing (I just want it to charge), I kill WCESMgr.exe and wcescomm.exe to stop activestynk. But then something even more annoying starts to happen if the phone is left on... windows constantly connects the USB and then disconnects... over, and over, and over...
What the heck?
At least somebody else is having the same issues
I came to the same kind of conclusion as you I think. As far as I know its a driver/hardware problem on the USB side, where the USB 'wakes' every now and again, in turn powering on the phone.
I am going to update my USB drivers and see if it makes a difference.
You can also open connection settings in activestink and remove the tick in the box marked "Allow USB connection with this computer".
Hello all
My artemis won't turn on anymore. I managed to do an hard reset but when it got to resetting the device, it will not start again. Tried removing the battery for some time, but no results.
Only thing I'm able to do is start the bootloader and use mtty. Is there something I can do from there ?
Regards
Hello,
I had the same problem, ended up with service - took 3 weeks (Norway). In the beginning it happen once or twice a day, managed to turn it on but after a few weeks it didnt start at all.
Best regards
BA
I had the same problem today on my Orbit. I started the GPS (igo 2006) this morning, and it started calculating a route from my present location to somewhere really far (forgot to reset the route). It became unresponsive, so i decided to soft-reset.
However, it wouldn't turn on... I removed the battery, sim, and microsd card for an hour, and tried to start, but no luck. Soft-reseting didn't do anything either. When I got home, I plugged it in to charge, but no go... the charging light stayed off, and a soft-reset wouldn't work.. wouldn't even power on!
Finally, I pressed the voice tag button (top left button on the side, beside the volume slider), and the soft-reset button togther for a couple of seconds... and it booted up like normal.
Not sure if this is a permanent solution, but I'm going to back-up everything daily from now.
Try it... might work for you.
N.
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.
I have some questions. (Copy from the old thread)
1. I mean that i read it here, but I'm not sure. At the moment I have very often the bug, that the volume button not works. Mute works, but louder and quieter not. I don't know when it doesn't work, but after a while no function.
2. Since a few days I have the wifi problem, that wifi works sometimes and after a while too, it shows empty bars and shows the connection but it doesn't work. In other case if I start the radio he can't find any WiFi. Why?
3. Since a few days the touchscreen doesn't work. I have set, that i can See if i touch. Then it shows a point. so i can see that the touch works, but there is no reaction. After a minuten the radio shows the bootlogo and have a loop. So i have start the radio new with reset or power off from the car.
4. Since a few days if i turn off the key normally all lights form the radio and display shut down. Additionally board computer shut down too after a few seconds. Now the light from the dvd tray is on and board computer too (after a lock from the car too). I dont know why but I don't know if that is so good (Battery).
All this errors are since a few days. I tried to do any settings but the problem is always here. Does anyone no about that? I think it's an app, but I don't know which one. The last chance (if I get no solutions) is to install another rom? That is really crazy, because it's only since a few days. The days before it works perfect.
I have JY 2.73 with the Malaysk Rom from September (1024).
Thanks
Update: Now i installed 2.59 JY and tried again. WiFi will always gone with no bars. So i turn off and turn on again. At the most cases it works. But the problem is here again. The same with the touchscreen crash. 3G doesn't work. always no bars.
So the previous MCU doesn't work again. Maybe a software error.
Could you please try to measure the voltage alignedto the HU while you encounter those problems? I rellay mean at the radio side (so not at the battery poles).
Such issues could be lack of voltage. If not and flashing does not solve it could be a defective unit.
Just to ensure: You flashed Firmware AND MCU? AM I right wit this assumption?
If not: Try to flash a new ROM first (probably try Malaysk ROM)
Btw: Moved to Q&A
dark alex said:
Could you please try to measure the voltage alignedto the HU while you encounter those problems? I rellay mean at the radio side (so not at the battery poles).
Such issues could be lack of voltage. If not and flashing does not solve it could be a defective unit.
Just to ensure: You flashed Firmware AND MCU? AM I right wit this assumption?
If not: Try to flash a new ROM first (probably try Malaysk ROM)
Btw: Moved to Q&A
Click to expand...
Click to collapse
Thx for answer. How can i measure that? Do you know which cable it is? And if the cable shows not the 12V? What can i do to fix the problem?
Sure. I have Malaysk Rom and the MCU JY 2.59.
you would have to get amulti- or vooltmeter and attach that between plus and ground pins at your HU.
If you don't know how you should eigther try to follow another way first if possible or ask someone to do it for you (it's electrics)
dark alex said:
you would have to get amulti- or vooltmeter and attach that between plus and ground pins at your HU.
If you don't know how you should eigther try to follow another way first if possible or ask someone to do it for you (it's electrics)
Click to expand...
Click to collapse
Thanks. I ordered a multilmeter. Maybe it's the battery. At the moment the car works really hard if I start it. The radio takes so much battery but the radio is off. So that can be the problem.
low voltage can cause many weird problems but you have to know a new battery might not solve your problem!
If you have low voltag while the engine is ruunning then you have a different problem. eighter there is a connection issue somewhere on the path the energy takes from battery and generator to the HU or your generator might have a problem. But that is open to check when we know if it really is a voltage issue.
Hi,
i'd like to give you an update for my problems. Since the last days I have the problems, that my car didn't start. Now we see, that the battery is nine years old. Now I charged the battery (tomorrow I'll get a new battery) and the first test shows WiFi works for 3 minutes. I know - that's not a lot, but I only can try if I have the new battery. 3G doesn't work - always the same. But that's not so important for now.
At the moment I don't have the volume error. I will test it, If i have a longer car drive.
The problem with the touchscreen is actually. Since a few time, after few minutes the touchscreen is bricked and I see the points that i touch it, but I can't click anything. If I touch ten times, twenty times or often then radio shut down and shows the boot logo... forever... it doesn't boot again. So I have to make a hard reset.
And the last point with the light board computer and the light dvd slot after plug off the key is actually too. It don't shutdown the lights on the standby time from 10 minutes (set it to 10 minutes). I know now, that I can shutdown it completely if I press the volume button for 3 seconds. Than it's turn off. So it's a setting problem from the firmware?
Today I plug in the key - nothing. Radio doesn't start. So I looked behind the radio and saw, that one thin cable is not in the wiring harness and I can see the wires on the cable. So I tried to put it in the wiring harness again. I hope it works longer now. I wrote carjoying and ask for a new wiring harness. Maybe all problems will be fixed, If i have a new.
Hello again,
now I've got a solution for the wifi problem. I've tried to connected wifi - i Known that doesn't work only few seconds and after a few seconds it shows 0 bars on wifi... now I disconnected my 3g stick and LOOK it works... full bars, no losing connection. I connect 3g again and the same problem after a few seconds.
So th3 3g stick (E1750 from Huawei) makes some problem OR the usb cable?
Huawei E355 also not working. Same connection problems with malaysk rom MTCD
Any suggestions?
Cross-posting this from r/NextbitRobin
So Tuesday night before bed I went to check my phone (which had been on the charger for the last couple hours and so was at >95%) and noticed the volume button was not responding. I figured something buggy was going on, sometimes I need to reboot my phone every couple of days to get it to work properly (especially if it had run down into low power mode before recharging), so after unplugging it from the charger, I held down the power button, selected reboot, and clicked okay. The phone then proceeded to shut down, but not start back up.
When I tried to start it up again by holding the power button, I got no response initially. Then I was able to get it to buzz/vibrate, but the screen never came on.
I tried holding down the Vol- button and the power button together for 20 seconds to force a reset, and it vibrates a couple of times, but nothing happens.
If I plug it into a charger, I don't see any LEDs illuminate, and it just vibrates approximately every 3 seconds (not continuously, it seems to have some semi-random pattern). If I unplug it, the vibrating stops, but I still can't get it to turn on. It does not seem to make a difference if I am using a wall charger or trying to charge it off my laptop.
I have not rooted the phone or installed any custom ROMS, and have had it since I bought it on Amazon in June of 2017.
Any ideas what might be the issue? Any tips for reviving my phone?
This doesn't seem to match anything I have been able to find with some basic google searching.
Edited to add that I also tried removing the sim card and starting it up without one, but that did not appear to make a difference.
Update: I left it plugged into a wall charger for about 18 hrs and when I came back there was no change in behavior.
This many sound repetitive but lets first get the obvious out of the way so that we are sure you tried the most basic things for sure.
Is there an issue with the cable not able to charge the device? Can you try changing the cable?
Power + volume down for 30 secs / 1 minute / few minutes. This usually helps, sometimes more than 30 seconds for some reason. Try doing it while plugged in.
When you connect to the laptop what happens? Does it power on for a minute or vibrate?
Do you have adb installed on your computer? does you device get detected on your laptop?
/root said:
This many sound repetitive but lets first get the obvious out of the way so that we are sure you tried the most basic things for sure.
Is there an issue with the cable not able to charge the device? Can you try changing the cable?
Power + volume down for 30 secs / 1 minute / few minutes. This usually helps, sometimes more than 30 seconds for some reason. Try doing it while plugged in.
When you connect to the laptop what happens? Does it power on for a minute or vibrate?
Do you have adb installed on your computer? does you device get detected on your laptop?
Click to expand...
Click to collapse
Tried charging it with both the OEM cable as well as an amazon basics USB-c cable (both of which had been used to charge the phone successfully in the 24 hrs before it went wonky), no noticeable difference in behavior.
Held the power + volume down buttons for 180 seconds, did not boot. Repeated this with it plugged in (wall charger) and it still did not boot.
When I connect it to my laptop, I get the same behavior of vibrating as when plugged into a wall charger, but it does not boot or power on, nor does the laptop detect the phone in any fashion. I do not have adb installed on my laptop.
Anything else I can try, or is the phone a write-off at this point?
First step to solving any device issue is to somehow boot it and get in any mode possible. Since you can't do that I can't think of any other way to get it working.
I'm having the same issue, phone is not giving me any signs of life...frustrated at the moment
It's a total long shot, but try carefully cleaning out your charge port with a needle or a small pin and a little bit of alcohol. I pulled quite a bit of pocket lint out of mine and it works fine now. It didn't look like it was that dirty, but I pulled out a large ball bearing sized amount.
Other than that the only other thing I can think of is that your battery might be shot. It might have been taking enough of a charge to try and turn on, but not enough to do so.