This is a pretty general issue so I've plonked it here.
Since the new version of Microsoft MyPhone was released my phone continues to crash regardless of what ROM I'm using. Has anyone else had this?
There are about 800 text messages to deal with and it will bomb out and crash the handset at random, there is no pattern to it. Sometimes it crashes at about 100, sometimes it crashes at about 300. The most annoying thing is that it synchonises in the middle of the night, crashing the phone and then my damn alarms don't go off!
I've had the same ROM for a few weeks now (Duttys Leo R5) since before the new MyPhone tool came out and didn't have any issues until after this point. I've tried flashing the custom ROM again, flashing different custom ROMs, hard resets etc and they all crash when updating the text messages in MyPhone, I'm now on Duttys Leo R6 and that crashes too.
Any ideas guys?
No one else has had this issue I guess
Mine doesn't even work lol.
Keeps saying My Phone is not responding and must be shut down because of an unexpected error.
I just think it's a junk program.
Related
So im running WM6 w/ TNT PRO, and without fail after about a few weeks of flashing the new ROM my texting starts to go all wacky, it will not register any characters after a certain #, which varies everytime. And then eventually my entire phone will freeze....ive tried soft resetting and everything. But the only thing that seems to solve it is re-flashing which loses all my settings and everything saved, its really a pain...anyone got any ideas>???
Hello guys,
I have an iPAQ 914c with a strange problem.
I text the same contact all through out the day, and occasionally I get complaints that I'm sending the same message multiple times.
It turns out it'll be a message that I sent a day previous that comes back and decides to re-send itself 4-5 times for no apparent reason, It's definatly not a network problem, because it was Happening on Orange UK, and now I'm on T-Mobile UK and its still happening.
I really think its a software problem with windows mobile 6.1 on the device. I've done a hard-reset twice and still get the same problem. I have the latest ROM, which was on the phone stock. I havnt gone to the hassle of Re-flashing the ROM since Its the latest, and theres no other ROMS around to test.
What do you guys think? I've only had the phone a couple of weeks and I love it, but having a bug really drives me insane!
I had a similar problem and this is what I found out.
If you send a message and it doesn't go through (network errors, you get another text or call simultaneously, etc.) it remains in your outbox (or drafts can't remember which one). When you do a soft reset (even days later), windows mobile immediately sends those unsendable texts.
Fix:
Delete items from your drafts and/or outbox folder before doing a soft reset.
When my phone is off, and someone send me a message, then I turn on the phone. The received time of the message is the time when I turn on the phone, not the time when it was sent.
I have tried OpenEclair 2.1 CM 1.6 rom. All of them have the same problem.
I think this is a big problem of the android system. Many other phones have no such problem.
This is a basic function of a phone...
I heared that the developers of Handcent maybe handle with this problem, It would be great.
original rom's have it working normally, that annoys me too
I'm having reliability issues when it comes to SMS. The phone often freezes when a text arrives, requiring a reboot. Once rebooted, the new text is gone and never re-appears. This can be kind of a big deal, as you might imagine, because people assume I got a text that I never actually got to read...
I am running Fireburned's WM6.5 v3.1 ROM. I usually have SMSBubbles running, but it has happened when disabled as well.
If this is not a particularly known problem with some sort of fix available, is there, perhaps, some software that will more robustly save an incoming text? Thank you!
have you tried reflashing the rom? I've had a few softwares problems, and they've always been fixed by a reflash
I'm also facing the same problem.. tried re-flashing but still the problem exists??????? Some body help!!!
Edited for the third time. Apparently Ididn't fix my problem.
So I'm running Cyanogenmod 10.3 on a Samsung Galaxy Tab2 10.1 (p5113***), and for some strange reason, my tablet keeps restarting randomly. I'd be reading a PDF or scrolling through some random app, and it'd suddenly freeze and the tablet would restart.
This all happened after I was typing a message on the Facebook app when it abruptly freezes and puts me through a restart loop that eventually ended. But when I finally got to startup without a crash, I'd see, almost immediately, a notification telling me that "Trebuchet has stopped responding", and my only option is to hit Ok. And I do, and most of the time, it crashes right afterwards.
At first, I was able to 'fix' (I think) this by freeing up space on my internal storage, because an app was on an update loop trying to install an update that was too big for whatever space I had left. I assumed it was eating up memory, space, and RAM and overwhelming my OS, so I uninstalled it and everything worked fine for most of the night. Later, I was reading a PDF file when Adobe just stopped working, froze, and put me through another restsart loop.
Also, I would like to point out that it is extremely difficult to turn this tablet off. It usually loops a few times before shutting down. Also, CM is updated to the latest STABLE update, which is not at all recent.
All this after Facebook crashed. I seriously have no idea what I do, and I would rather not reinstall CM, because it was an ADVENTURE trying to install it the first time, and I heard it's even more difficult and dangerous to uninstall and restore to factory settings. I'm not really good at this stuff.
Please help. Please.
*** Apparently my tablet is p5110, and the version of CM I installed was compatible with p5113, but it managed to work anyways, so I just shrugged and let it happen. And it has been working for the past 14 months, prior to the Facebook crash that started this mess.
Don't mean to bump, but I'm only replying to myself to show that my original post edit is now moot, because the problem resurfaced ... help.
I don't have a solution to you, but will share my own experience on the 5113. I have two of them. One has been stable since I bought it, except for a brief time when it had the awful first 4.2 update, eventually fixed by the MK3 firmware update. It's working fine. My other one has been a nightmare all year long, after six or eight months of stability after I bought it.
I've installed CM on in, in early June. Unstable.
I've installed Omnirom on it shortly afterward. It was more stable, but still not "stable."
Installed Ripper Rom. Worked of a couple days but was ultimately unstable.
I've recently flashed it back to the MK3 firmware via ODIN. It's still unstable.
I've determined it must be some hardware fault in the tablet, and I'm going to sell it for parts. I've bought an ASUS transformer TF701T tor replace it.
I wish you luck and hope your problem is software only. But I've heard many of these tablets go unstable after a while, and fear it is a hardware thing.
Marc