Hi all,
I had a dead HTC P3300, which i got it to be dead by converting it from Chinese to English rom. While flashing , it went dead, and after heaps of tries i have finally got it alive!
The problem now is that now the speaker is always on when i use the Phone.
I cannot switch off the speaker, and keep it to ear mode. Even when i press the "Speaker On/Off" the speaker is always on!
Currently loaded B&B3.0 in it. I had put the 3.7 too but that didnt help either.
Please help me guys!
Thanks a lot!
I would also like to know this, cause mine is acting the same way
Mine did the same thing. I suspected it was PhoneAlarm. I removed it from my Today screen, soft-reset, then added it back. This corrected the problem for me.
I havent installed any applications on it till now. its freshly flashed with B&B3.0.
Still problem persists, Please help.
Thanks!
I have exactly the same problem, can you please tell me how you fixed it?
Neozzz said:
I have exactly the same problem, can you please tell me how you fixed it?
Click to expand...
Click to collapse
ive seen this one another forum and the guys have been reflashing the radio rom and that fixes the problems.
check the forum here for the latest update radio rom and install.
Sucess.
Yes, upgrading the Radio part is most likely to fix the issue.
Regards,
Carty..
upgrading the radio rom does not fix the problem, at least not for me.
did any of you use/install the new t-mobile wm6 update?
cause i had/have the same problem on my mda compact 3 and the problems started for me after that update. also posted about it in the dutch release of the t-mobile rom here.
i started getting this fixed by installing other roms, no luck at all.
then i tried flashing another radio rom, seemed lucky but not.
when you install or uninstall any appz after that the speakers are on again for ever.
i tried all kinds of rom releases with the same bad luck, even on of the oldest available wm5 roms, and that wm5 was the only working proper, but when trying another wm6 rom after that the speaker stuff was back again
my phone is now @ t-mobile repair, cause after 2 weeks of testing *a million of different releases or combinations, the problem kept coming back.
so there went something very wrong for me with the t-mobile wm6 update, and it is up to them to fix it, cause the phone came from them and the update to.
i explained the guy in the t-mobile store exactly what is happening and the phone was fixed at least repair said, but luckily he knew how all started (minus the part of the good releases here) and did exactly as i told him "uninstall f-secure" and the speakers where on again, and i guess the only option is going to be a whole new phone (or empty totally fresh rom not touched by that that B&%tch of the wm6 update of t-mobile)
i'm thinking personally that the radio rom in that release has written something to rom that can't be overwritten again or at least in not a proper way, or that release did some to the rom in the phone that corrupted it.
but that is just some guessing from my side, but i have a feeling that my guess is not far from the reality.
for me it's now just hoping t-mobile is fixing this soon or giving me a new phone, cause the words of the the guy in the t-store where "that should never have happened and this falls under warranty for sure"
HarryRag said:
upgrading the radio rom does not fix the problem, at least not for me.
did any of you use/install the new t-mobile wm6 update?
cause i had/have the same problem on my mda compact 3 and the problems started for me after that update. also posted about it in the dutch release of the t-mobile rom here.
i started getting this fixed by installing other roms, no luck at all.
then i tried flashing another radio rom, seemed lucky but not.
when you install or uninstall any appz after that the speakers are on again for ever.
i tried all kinds of rom releases with the same bad luck, even on of the oldest available wm5 roms, and that wm5 was the only working proper, but when trying another wm6 rom after that the speaker stuff was back again
my phone is now @ t-mobile repair, cause after 2 weeks of testing *a million of different releases or combinations, the problem kept coming back.
so there went something very wrong for me with the t-mobile wm6 update, and it is up to them to fix it, cause the phone came from them and the update to.
i explained the guy in the t-mobile store exactly what is happening and the phone was fixed at least repair said, but luckily he knew how all started (minus the part of the good releases here) and did exactly as i told him "uninstall f-secure" and the speakers where on again, and i guess the only option is going to be a whole new phone (or empty totally fresh rom not touched by that that B&%tch of the wm6 update of t-mobile)
i'm thinking personally that the radio rom in that release has written something to rom that can't be overwritten again or at least in not a proper way, or that release did some to the rom in the phone that corrupted it.
but that is just some guessing from my side, but i have a feeling that my guess is not far from the reality.
for me it's now just hoping t-mobile is fixing this soon or giving me a new phone, cause the words of the the guy in the t-store where "that should never have happened and this falls under warranty for sure"
Click to expand...
Click to collapse
Hi Harry
i can understand you had so many problems and i know its not nice, but it is really the radio rom that is at fault, please read this Dutch forum, they have posted this problem a lot and the radio had reported to fix the problem.
link to site is http://gathering.tweakers.net/forum/list_messages/1257926
as for me i dont have the problem, never did, just picking info up from site and trying to help others.
good luck with your phone and i hope you get a repair or a new one back.
fijn weekend
That did happen to me when I used AudioNotes to record calls through speakerphones, and got fixed after I unchecked that option from the software. You could use Resco Audio recorder instead.
@ neil H
that topic is one of my daily views, but also could not find the answer over there.
guess that in my case there went something terribly wrong, and also hope T-mobile will fix it soon, cause can't stand being back on my over aged motorola
jij ook een fijn weekend, nu hopen dat de zon gaat schijnen in NL
Related
2 weeks ago i have upgraded to lvsw latest rom release and is the worst release (sorry for that m8).... manny apps doesn't work.... and even the last one before this was much better :|.... and any1 can help me how can i get back to the original orange rom... like when i buyed from the storage? thank u....
Hey, this is bull**** - can u specify which apps etc? I am using LVSW 20070423 from the first day of release and no problem...
This ROM is pretty damned good - so slow operation is probably something you've got installed.
To go back to your original orange ROM (PRESUMABLY wm5) you first need a copy of the original ROM, then follow Mrvanx's guide.
http://forum.xda-developers.com/showthread.php?t=299462
maddogydog said:
2 weeks ago i have upgraded to lvsw latest rom release and is the worst release (sorry for that m8).... manny apps doesn't work.... and even the last one before this was much better :|.... and any1 can help me how can i get back to the original orange rom... like when i buyed from the storage? thank u....
Click to expand...
Click to collapse
MaRaHoX said:
Hey, this is bull**** - can u specify which apps etc? I am using LVSW 20070423 from the first day of release and no problem...
Click to expand...
Click to collapse
lol... i know is bull****... prob is when i m tryin to call ... i hear 2 sounds ... and that`s it ... and office give me this error "Program Not Recognised" .. anyway ... now i am with the previous of lvsw rom
Problem during a call I supposed in GSM part, which is indipendent on LVSW's ROM (maybe other causes - 3rd party app, bad A2DP mod etc.) - but primary try new RADIO ROM.
Office works me well - I just try it before a few secs (immediately after HR) and its ok?
I am using phone daily for hard work and no problems, you mentioned.
Some unstability was caused by wrong Page Pool, but I suppose, that it is not your case.
LVSW ROM is very good, I like it compared to others. Try installing a new radio and try a hard reset or reflash it.
Remember LVSW bundles the Radio along with his ROMs, could you please tell us your Radio version??
mrvanx said:
Remember LVSW bundles the Radio along with his ROMs, could you please tell us your Radio version??
Click to expand...
Click to collapse
@mrvanx, LVSW 20070423 is an OS-only distribution. He recommends that Hard-SPL-v7 and Radio 1.41.00.10 be installed beforehand (links provided). A deviation from his previous ROMs.
John
maddogydog said:
2 weeks ago i have upgraded to lvsw latest rom release and is the worst release (sorry for that m8).... manny apps doesn't work.... and even the last one before this was much better :|.... and any1 can help me how can i get back to the original orange rom... like when i buyed from the storage? thank u....
Click to expand...
Click to collapse
What do you mean many apps doesn't work? All apps works on mine..IMO, LVSW's rom is the best. There must be something you didn't follow correctly or you installed some bull**** 3rd party apps. I am sorry if that offense you.
LSVW 423 is a great ROM - fast with all the bits I want and none of the bits I don't want, but I'm having issues with hanging on soft resets (about 10%) of the time as well as freezing and not able to resume from suspend. I have had these issues with most if not all the WM6 ROMs and can't figure it out.
Anyone else with similar issues?
Meanwhile orange have released a new WM5 AKU3.3 rom on their business site.
I've had no issues with LVSW 4/23 rom. I use the phone heavly during each day for the office and I never had experienced any issues. LVSV rom is the most stable in my opion. All apps are working as they should.
I only down graded my radio back to 1.40.30.00 cause of stability and the fact 1.41.xx.xx kept dropping my calls between 3G to Edge, not to mention weaker signal. Fact, 1.40.30.00 is I beleive the offical ATT radio release ATM (I might be wrong, something more official may be out).
Did you read the entire forum before flashing? As Johnburn mentioned, LVSW repackaged to OS only and given specific instructions to Hard-SPL-v7 and Radio before the OS only ROM due to issues on the his first post of the full package.
I think you're the only who has bad experience w/ LVSW release and you blamed it on the ROM. way to go.
khammo01 said:
LSVW 423 is a great ROM - fast with all the bits I want and none of the bits I don't want, but I'm having issues with hanging on soft resets (about 10%) of the time as well as freezing and not able to resume from suspend. I have had these issues with most if not all the WM6 ROMs and can't figure it out.
Anyone else with similar issues?
Click to expand...
Click to collapse
yep exact same issue right here.
LOVE the roms, hate the fact that I keep freezing in suspend with all wm6 roms.
thought it was my phone till I flashed back to wm5, and its working perfectly again.
charbz said:
yep exact same issue right here.
LOVE the roms, hate the fact that I keep freezing in suspend with all wm6 roms.
thought it was my phone till I flashed back to wm5, and its working perfectly again.
Click to expand...
Click to collapse
What do you have installed??? Also please note if installed programs are on the DEVICE or MEMORY CARD. What today items do you have??? And did you have cabs in the extended ROM??? All of these things will affect the device and could possibility cause it to lock up. Any whos I have no problems with WM6.
charbz said:
yep exact same issue right here.
LOVE the roms, hate the fact that I keep freezing in suspend with all wm6 roms.
thought it was my phone till I flashed back to wm5, and its working perfectly again.
Click to expand...
Click to collapse
to fix the freezing go to:
start-> settings-> today-> items(tab)-> and set the today timeout to 12hr
stukes said:
What do you have installed??? Also please note if installed programs are on the DEVICE or MEMORY CARD. What today items do you have??? And did you have cabs in the extended ROM??? All of these things will affect the device and could possibility cause it to lock up. Any whos I have no problems with WM6.
Click to expand...
Click to collapse
I always installed EVERYTHING on device memory. Nothing on storage card (even though it worked fine with Wm5 for anything other than Today apps).
I thought it was my applications so I went back to scratch. Even no apps installed and even with SD card removed, it fails to wake up from sleep if anything other than Exchange Activesync tried to use the radio while it was asleep.
Main culprits include IMAP mail sync and weather app syncing. You can verify this by setting sync interval to some ridiculously low value (every 5 minutes) and then watch a sitcom or something. It will be locked by the time it's over. (Hey, I just looked down and whaddya know, my phone is locked again).
There are some files laying around in extended ROM but They are not installed on hard reset. Are you saying they might be interfering nevertheless?
I hear rumors that LSVW 3/23 does not have this problem so I'm going to try that one last time. If I can't resolve it, I'm going back to WM5.
webpain said:
to fix the freezing go to:
start-> settings-> today-> items(tab)-> and set the today timeout to 12hr
Click to expand...
Click to collapse
Hmm... seems an unlikely fix. Is this verified to work? What about just unchecking the Today timeout box altogether? I'll give it a try...
EDITED:
I tried the Today timeout fix and it still locks up.
@khammo01
Good to see you have tried to isolate the problem. However you say that a fresh install also locks up. If this is true then the problem is deeper. Have you tried each Cooked ROM? I have and only by preference choose Black2.5. So far the only lock-up I have had came from a today plugin. WHich I should have put on the DEVICE instead of the CARD. At times the Active Sync appears to be sluggish but it is only right as it connects. Then all is well. Verify your download and try again.
stukes said:
@khammo01
Good to see you have tried to isolate the problem. However you say that a fresh install also locks up. If this is true then the problem is deeper. Have you tried each Cooked ROM? I have and only by preference choose Black2.5. So far the only lock-up I have had came from a today plugin. WHich I should have put on the DEVICE instead of the CARD. At times the Active Sync appears to be sluggish but it is only right as it connects. Then all is well. Verify your download and try again.
Click to expand...
Click to collapse
I have tried LSVW, Black 2.0, 2.5, Dutty, Custel, you name it. They all have the sleep error.
If I have IMAP or anything enabled that uses the radio when the device is asleep, I get lockups.
Basically I cannot enable anything useful. I'm going to try LSVW 3/23 (pretty much the only ROM I haven't tried) and if that doesn't work, I'm going back to WM5.
Hi, suddenly whenever I soft reset the handset, take the battery off (to get to the sd card), or simply power off, the phone reverts back to October 24th 2006. I assume that's the date of my ROM.
I have used the 'clear storage' option which I assume is the same as a hard reset. It still has the same problem.
Me being sherlock holmes, I suspect it's a hardware problem, most likely to be some sort of back up battery.
Has anyone experienced this, what else might be affected, do you think it is indeed the back up battery or could it be something else?
Thanks,
Ezman
I have also experienced this with mobiz v2.04b ROM version.
Now I have flashed Prophet_4.0.0.0.4SSE_PV and time date settings is ok.
I think the problem is in ROM.
may be there is some fix about this bug.
what ROM version do you flashed?
cheers for the response, i have the standard o2 orbit wm5 ROM. again, only started recently. v odd
Hmmm,
I have not any experience on that ROM. You should have a try to upgrade WM6 ROM . If you do not have enough experience I strongly recommend to read forums and back up your all data before doing that.
http://forum.xda-developers.com/showthread.php?t=310452 this may help you.
thanks for the advice, i'm trying to be patient and wait for the official orbit uk wm6 rom.
I can't see how it could be rom related when it hasn't done this for the previous 8 months i've had the device.
Something has happened that has survived a hard reset in effect.
I've done a lot of searching and haven't really found anybody with the same problem.
Hi Ezman!
You didn't look too hard did yer mate?!!! I posted the exact same issue on the 13th July ! 4 days prior to yours!
anyway, not here to gather brownie points - but it's weird how it's just started happening.
I've just message my mate for him to try the reset and see what happens.
I'm on a O2 Xda Orbit, and with the ROM that came with the device
rom version 1.25.206.2.wwe and date is 10/4/06
ezman, can you confirm you are on the same ROM version ?
I havent been so up to date with this forum, is the Orbit WM6 the next ROM update that is recommended ? or is this issue happening with the last wm5 rom update as well? if it is , then i'll do the same as you and wait for the wm6 rom....
Cheers! Dennis! West London UK!
DennisCooper said:
Hi Ezman!
You didn't look too hard did yer mate?!!! I posted the exact same issue on the 13th July ! 4 days prior to yours!
Click to expand...
Click to collapse
woah, freaky! i can pin point the start of the problems to 10/07
DennisCooper said:
anyway, not here to gather brownie points - but it's weird how it's just started happening.
I've just message my mate for him to try the reset and see what happens.
I'm on a O2 Xda Orbit, and with the ROM that came with the device
rom version 1.25.206.2.wwe and date is 10/4/06
Click to expand...
Click to collapse
Exact same as mine
DennisCooper said:
I havent been so up to date with this forum, is the Orbit WM6 the next ROM update that is recommended ? or is this issue happening with the last wm5 rom update as well? if it is , then i'll do the same as you and wait for the wm6 rom....
Cheers! Dennis! West London UK!
Click to expand...
Click to collapse
Looks like WM6 is going to be released in the next few days, hope it fixes this issue. Very odd, looks like we both got the issue at the same time, be interesting to hear whether your friends is affected.
update
My mate who has the exact same setup has NOT reported this issue. Weird huh!!
I'm just gonna wait for the latest ROM and whack that on whenever it's out. It's not too annoying at this stage - just a niggly little annoyance!
ahh well...
Dennis! West London UK!
I am really frustrated and wanted to see if anyone could help....
For my ROM, no matter which PDA or Phone version I used, I always have this "cprog.exe" error and I have to hard reset to start all over again. It happens even I have no external software installed. That means, a clean phone also has this horrible cprog.exe error. Yesterday I had to hard reset 5 times in a day....
May I know anyone here has the same problem, anyway it can be fixed? Thanks very much.
PDA: i780DXHE1
Phone: i780PUHE1
Win Mobile 6.1
27149 said:
I am really frustrated and wanted to see if anyone could help....
For my ROM, no matter which PDA or Phone version I used, I always have this "cprog.exe" error and I have to hard reset to start all over again. It happens even I have no external software installed. That means, a clean phone also has this horrible cprog.exe error. Yesterday I had to hard reset 5 times in a day....
May I know anyone here has the same problem, anyway it can be fixed? Thanks very much.
PDA: i780DXHE1
Phone: i780PUHE1
Win Mobile 6.1
Click to expand...
Click to collapse
Looking at your details, my guess is that you may have a cooked rom, therefore it can either be a bad rom or a bad flash.
Thanks for the quick reply.
I just flashed the i780DXHH1 for both pda and phone rom. Hope this is ok for me....
27149 said:
Thanks for the quick reply.
I just flashed the i780DXHH1 for both pda and phone rom. Hope this is ok for me....
Click to expand...
Click to collapse
Let us know if you still encounter the problem.
Wish you luck.
Had this issue when I bought my 1st i780. Took it back to the service centre and they reflashed it but it didn't help. Apparently it is a chip that causes this error so if it is still happening bring it back to them to get the chip changed as I did. No more issues now. Hope this helps.
mobilepalm said:
Had this issue when I bought my 1st i780. Took it back to the service centre and they reflashed it but it didn't help. Apparently it is a chip that causes this error so if it is still happening bring it back to them to get the chip changed as I did. No more issues now. Hope this helps.
Click to expand...
Click to collapse
no wonder how many times, different version of rom I flashed, still get this cprog.exe nightmare! I hard reset 3 times today, and 3 more times to go to break my daily record.
flaw in chipset! sigh. I bought this in HK as parallel products (as they are not launching i780 in HK)....I dont have official support/service center....does anyone know how could I have this fixed? Does Samsung support worldwide warranty?
i780 suits all my needs, qwerty keyboard, good resolution, great sleeky look, but mine comes with cprog.exe curse....I dont want to switch to palm treo pro...but if samsung is not willing to take this back for chip replacement, I have no way out but treo pro, sigh!
mobilepalm said:
Had this issue when I bought my 1st i780. Took it back to the service centre and they reflashed it but it didn't help. Apparently it is a chip that causes this error so if it is still happening bring it back to them to get the chip changed as I did. No more issues now. Hope this helps.
Click to expand...
Click to collapse
HI, just registered here in seeking a solution to the same prob, the guys here said they will fix my phone if i can find out which chip needs the replacing.
Do you perhaps know?
Hi
I haven't found anyone else in TP2 forums report this problem I have on reboot, but can anyone help? After inputting my PIN, a screen comes up stating "We're Sorry... A problem has occurred with services.exe" and it asks if I want to send a report to Microsoft, but if I click either "send" or "don't send", it then appears to function normally.
I, too, have this problem, but hesitated to bring it up here because my assumption was that it must have something to do with a tweak I have done or some software I have installed (and then subsequently uninstalled?). As such, the parameters are too broad (I would have thought) to be able to determine why this is happening. Are you also working with an AT&T Tilt2, stock ROM?
I too have this problem, if it occurs overnight, my alarm will not go off, and it get stuck on the time that it happens until i click ok. kinda sucks
I had it - tech support (AT&T) exchanged the phone
I had it - tech support (AT&T) exchanged the phone
It was within the first thirty days
my 30 days is up
Also got it with my TP2. Dutch stock rom windows mobile 6.5
Also getting the error after a restart sometimes, or randomly in wimo 6.5. Never had it until my wimo ran out of power when playing a game... It shutted off on it's own. Now i randomly get that error so once in awhile. I even did a hard reset, but still getting it sometimes. But not always after restarting...
Bit strange... Don't notice anything not working though. Everything seems to be working fine... Is there a way to disable error reports in wimo?
Sephi- said:
... I even did a hard reset, but still getting it sometimes ...
Click to expand...
Click to collapse
Wow, thanks for the info -- I was actually considering a hard reset because of this -- you've saved me the trouble!
pistou said:
...Are you also working with an AT&T Tilt2, stock ROM?
Click to expand...
Click to collapse
I have stock HTC 6.5 ROM (WWE). It's not a major problem and only occurs if I reboot - luckily it does not happen randomly for me or when unlocking or switching the phone transmitter off and then on again.
agrickard said:
It's not a major problem and only occurs if I reboot.
Click to expand...
Click to collapse
Now, on reboots I'm also getting an error message about gwes.exe -- comes right after the one about services.exe.
I get it too. Stock Rom with plenty of apps and stuff added.
Me Too
I started having this and other errors after installing Hou Ming's fexploreext205. I had just started to look for a replacement when I ran across this thread.
nycny said:
I started having this and other errors after installing Hou Ming's fexploreext205. I had just started to look for a replacement when I ran across this thread.
Click to expand...
Click to collapse
Darn, I don't have this app installed, but this line of investigation may yet yield results. I'm going to try to see if I can figure out the history of my installs (good luck!).
OK, I bit the proverbial bullet and did a hard reset. It's taken me a couple of days but I've got all the software re-installed (with a soft reset after each install! -- more or less) and so far so good: no service.exe (or any other) errors. Let's just hope there isn't some periodic thing that will trigger the error down the road.
I just downloaded and upgraded my Touch Pro2 now to the WM6.5 for GCC and Egypt. However, anytime i do a soft reset i get the following error message:
A problem has occurred with services.exe
And then the blah-blah about telling Microsoft about this problem.
This doesn't happen however if i shutdown and the restart the Touch Pro 2.
I have done a hard reboot and still i get this error. I have posted this on HTC support site. Let's see what they say.
Now appears cured!
azuka said:
I have posted this on HTC support site. Let's see what they say.
Click to expand...
Click to collapse
For some reason I now don't get it. I have no idea why as I haven't been trying to solve it specifically and have not hard reset!
@azuka: Please let us know what HTC say.
i also have this problem..
using stock 6.5 WWE SEA rom
happened after installing some programs..
however doesn't seem to affect or give any problems after
clicking don't send or send ..
would love to know why this occurs tho..
thx
Same thing happened to me. I have the new leaked t-mobile 6.5.
I did the hard reset and it happened to me again after i installed a few programs so i decided to reflash the with the t-mobile rom again and thank God it hasn't happened since the morning. i have been installing the programs one by one with a soft reset right after every new install trying to recreate the problem but it hasn't happen..
i hope it stays that way.
I have the original HTC rom (ITALIAN) and I have this problem if i deactivate Manila and i activate Titanium interface. I think there is some program that try to "talk" with manila during boot.
Now I enabled Manila again and it works like a charm.. (But I miss Titanium interface.. )
HTC simply asked me to download the WM6.5 upgrade again and reinstall. This i did and surprisingly i have not received that error again. 3days+ now and still counting.
I have been using cooked ROMs for so long now that I can't even remember. Only very recently have I been forced to use official ROMs becuase of unavailability of HardSPLs.
I have only had this issue with two devices the Touch Pro2 and Imagio but i'm pretty sure that it happens with other models also.
Error examples:
'a problem has occurred with fexplorer.exe'
'a problem has occurred with services.exe'
I am a flash freek and every time I load about 100+ games and about 150+ applications so before everyone starts saying that when you load so many softwares something bad is bound to happen. I have already considered that but here is why i thing the problem is with official ROMs.
- I flashed official ROM and hard reset
- I first left out all the games and only installed the applications but the problem was still there.
- I then split the applications in half and after another hard reset tried with first batch and problem was there. I hard reset and also tried the second batch and problem was there.
- I am not so desperate an i am installing softwares one at a time and then testing for 10-15 mins and then installing the next software to pinpoint the problem.
even with the last approach I cannot pinpoint which software is causing the problem. Sometimes the phone crashes after 10 applications installed and sometimes after I reach 40 applications.
Now some of you will ask and suggest if maybe the problem is with the softwares. Most of the softwares I have are from freewarepocketpc.net but how can it be the software when all these softwares are the same ones that I have been using without any issues on Cooked ROMs for months and not a single crash on the Cooked ROMs.
I have been scratching my head and trying to figure out what is that secret ingredient in the Cooked ROMs that make them so stable and what can we do to make our official ROMs stable.
At one point I though Microsoft .NET Compact Framework was the culprit and so I tired several times with and without it installed and the problem was still there so I ruled it out.
I also tried installing SDK certs on the official ROM but that did'nt fix it either.
Help me out here guys, what am I missing, whats that Secret Ingredient in the cooked ROMs that make them so stable?
Fairy dust, us cooks sprinkle a little over the rom in the building process and it makes them super stable.
Personally I have never had those two errors on a stock rom. Might I ask which brand of those phones are you using? (aka, is it an AT&T, Telstra, Verizon, etc.) Sometimes (make that 99% of the time) the carrier's version of a rom is THE WORST there can be, causing problems like that.
With that note out of the way, you have tried using it without installing anything for a bit to see if the problem still persists right? If not, it could be one, or more likely more than one application is causing it to die.
the secret words for tonight are
"disable error reporting in your ROM"
most of cooks use this secret weapon.
=)
shadowline said:
Personally I have never had those two errors on a stock rom. Might I ask which brand of those phones are you using? (aka, is it an AT&T, Telstra, Verizon, etc.) Sometimes (make that 99% of the time) the carrier's version of a rom is THE WORST there can be, causing problems like that.
With that note out of the way, you have tried using it without installing anything for a bit to see if the problem still persists right? If not, it could be one, or more likely more than one application is causing it to die.
Click to expand...
Click to collapse
For Verizon Imagio i've used the official shipped ROM
I also had the same problem on the T-Mobile Touch Pro2 with its shipped WM6.1 ROM and once the HardSPL came out, i tried with the European Pro2 WM6.5 Official ROM and that also had same problem.
Yes I tried using the ROMs without any softwares and they work just fine. So that brings me to the conclusion that the softwares that I am installing are causing this but the problem is how to pinpoint which softwares and if it turns out that a wide variety of softwares are causing this (my suspicion) then why is it happening only with official ROMs and not cooked ones?
serfer222 said:
the secret words for tonight are
"disable error reporting in your ROM"
most of cooks use this secret weapon.
=)
Click to expand...
Click to collapse
Does this mean that windows mobile is so unstable that the only way to fix it is to give an illusion of stability by disabling the error reporting?
Say it isn't so, I love WM and if things are so bad with it then I have nowhere else to go.
serfer222 said:
the secret words for tonight are
"disable error reporting in your ROM"
most of cooks use this secret weapon.
=)
Click to expand...
Click to collapse
We have a winner!
Thanks
serfer222 said:
the secret words for tonight are
"disable error reporting in your ROM"
most of cooks use this secret weapon.
=)
Click to expand...
Click to collapse
After thinking about it a few minutes I get it now. I am shocked that I spent over week testing hundreds of softwares one by one when I could have just disabled the reporting. Thanks for the secret ingredient, i'll give it a go and report back in 1-2 days how my ROM is responding. I can already notice a slight increase in speed.
I know this is blashphemy on XDA, but I have the opposite issue. I've never encountered a cooked ROM as bug free as a stock ROM. Maybe this is b/c I've never bought a carrier phone and always gone for the unbranded, unlocked device, so I've had a clean stock rom to start off with... But with every cooked ROM I've tried (and to be fair, I don't flash regularly like I used to - so maybe things are getting better), there's always something wrong even if its a minute detail like text out of place on some screen hidden away in settings that most users don't find, or lost functionality of special buttons in oem programs like Opera (that most XDAers don't know about b/c they flash the first day they get the device), or lack of proper support for landscape, or improper bluetooth implementations where A2DP doesn't work like it used to, etc.
sonus said:
I know this is blashphemy on XDA, but I have the opposite issue. I've never encountered a cooked ROM as bug free as a stable ROM. Maybe this is b/c I've never bought a carrier phone and always gone for the unbranded, unlocked device, so I've had a clean stock rom to start off with... But with every cooked ROM I've tried (and to be fair, I don't flash regularly like I used to - so maybe things are getting better), there's always something wrong even if its a minute detail like text out of place on some screen hidden away in settings that most users don't find, or lost functionality of special buttons in oem programs like Opera (that most XDAers don't know about b/c they flash the first day they get the device), or lack of proper support for landscape, or improper bluetooth implementations where A2DP doesn't work like it used to, etc.
Click to expand...
Click to collapse
I think a lot of cooks are very short-sighted on these issues. I have a habit of testing every button, every program and every feature multiple times before a ROM goes out the door, and I still miss things. Many of the factory ROM's I've used are bad in this regard as well (my Fuze connecting to a secured WiFi network for one). Cutting off the error reporting doesn't really do that much, but I've had crashes before where I had to turn it on to find a bug that was stopping the ROM from working.
Dizzy looking at ...
Man, I got dizzy by looking at your avatar.
Everyone says that.