Related
HI EVERYONE
I HAVE BEEN READING A LOT ABOUT THE 1.11ROM
I JUST INSTALLED THE RADIO PART OF IT ...
BUT TO MY DISAPPOINTMENT ... NO CHANGE TO MY PREVIOUS 1.01
HAVENT INSTALLED THE COMPLETE ROM BUT WANNA KNOW IF THERE IS ANY ADVANTAGE AT ALL ??????
sigh
what was that for ??
@ morphosin
I suppose, it was his way to say "well, there are several threads in this forum about upgrading to 1.11. Please take a look at the search button".
If You are currently using radio 1.01, upgrading to 1.11 should be a major improvement. Wne I upgraded to 1.05 (or was it 1.06) it was a big step towards good sound (but I must admit that there is hardly a difference between 1.06 and 1.11 in terms of sound). Sound improvement will not depend on the installation of the other ROM-Files, the radio.nbf is enough.
with 1.11 there will be only a few performance features at my side ...
Too bad none of those several threads are able to conclusively identify any solid benefit from upgrading. I am still looking for posts that tell me why 1.11 is worth the bother. And he did say he was reading about it beforehand (presumably in this forum). So seems the question is valid in my opinion.
ROM upgrades are mostly used to fix bugs in older version. From time to time new capabilities are thrown in as well, but that is not the main concern of a ROM update. So the question is: do you want to live with these bugs, or do you want them fixed?
Don't expect all bugs to be fixed by doing a ROM upgrade, though. ROMS are made by humans, and we make mistakes. Of course new bugs can be introduced as well, but unless these new bugs are very bad and a lot of users are experiencing them, I see no reason to run an old buggy version.
Seems they've replaced the old tired bugs with new and improved ones! I have finally stabilised my JAM on the 1.06 ROM after much pain. I am still not convinced that the 1.11 is any better since some people claim its better and some claim its much worse. In other words, there is little consensus.
BTW, I don't accept the human factor as an excuse for lingering bugs. I am not a beta tester and I don't wish to use beta products. Once maybe, twice is pushing it, but three ROMs and still no sign of fixes for the fundamental problems is unacceptable. My phone is unreliable and if I don't get it sorted soon I will be back on a Nokia / Blackberry combination (quite a step backward in my opinion).
All I want is a stable working ROM that allows me to hear calls when I make them, to hang up when I hang up, and to connect and disconnect to GPRS when I need to and to put an end to soft reseting all the time! Unit and regression testing as part of a typical QA process should kill off 90% of bugs either new or old.
The problem is that in the rush to market HTC/Imate have obviously failed to complete a proper QA cycle prior to release. Their QA is terrible.
ianwood, what are these numerous bugs that you're referring to?
I'm heavily using my JAM on a daily basis. I was very cautious and selective on what 3rd party software I install. I had some 3rd party software that f*cks up my JAM completely (JGUI's for example), but now I have a list of software that WORKS WELL TOGETHER and don't have any problems. I never do a soft reset and the JAM behaves exactly how I want it.
We also have to distinguish between 3rd party software bugs, Windows bugs and HTC flaws.
The same bugs that everyone else refers to:
Intermittent:
GPRS not being able to resume after a call
Answering call fails with "unable to answer call" message
Hanging up fails with service command error message
ActiveSync becoming unresponsive when syncing
BT not installed errors
Unresolved items in ActiveSync when there is no conflict
Constant:
Heavy static on calls
Sound quality is crap (worse than the old T68s)
Speakerphone is also crap
Camera is slooooooow and picture quality is mediocre
BT headset drops after 15 minutes
Several reputable today plugins just don't work
BTW, I have very little installed on the thing. GPRS Monitor, a couple of simple games, Resco, Skype, TomTom. The rest are I-Mate default apps.
Let's face it; I am not the only one to have an issue with this thing.
MS, Imate, HTC, et all need to wake up and realise they will continue to be a footnote in mobile until they get this stuff sorted out! Let's hope WM5 will be better -- too bad we might not get it on our JAMs.
Some problems just not related to the Rom itself. I am using 1.11 rom
ianwood said:
The same bugs that everyone else refers to:
Intermittent:
GPRS not being able to resume after a call (I don't have GPRS)
Answering call fails with "unable to answer call" message (never happen to me)
Hanging up fails with service command error message (never happen to me)
ActiveSync becoming unresponsive when syncing (never happen to me too)
BT not installed errors (Yes! But not anymore after 1.11 rom)
Unresolved items in ActiveSync when there is no conflict (blame stupid MS)
Constant:
Heavy static on calls (sometimes)
Sound quality is crap (worse than the old T68s) (Ok for me)
Speakerphone is also crap (I agree)
Camera is slooooooow and picture quality is mediocre (I agree)
BT headset drops after 15 minutes (not in my case for my HBH 600, even 30+ mins still ok)
Several reputable today plugins just don't work <- This is the plugin's problem. All my plugins works without problem (SBSH's Pocket Breeze, Marware's Pocket Weather and PocketMax's Phone Alarm)
Click to expand...
Click to collapse
ianwood said:
The same bugs that everyone else refers to:
Click to expand...
Click to collapse
I had some of those when I first got my Magician, but haven't seen any of them since upgrading to 1.06.
Intermittent:
GPRS not being able to resume after a call - Constant, but fixed in the Norwegian.
Answering call fails with "unable to answer call" message - Never happened to me.
Hanging up fails with service command error message - Never happened to me.
ActiveSync becoming unresponsive when syncing - Agree.
BT not installed errors - Never in 1.11, but only in 1.06.
Unresolved items in ActiveSync when there is no conflict - Constant.
Constant:
Heavy static on calls - Never happened to me.
Sound quality is crap (worse than the old T68s) - No.
Speakerphone is also crap - No.
Camera is slooooooow and picture quality is mediocre - As in all ROMs.
BT headset drops after 15 minutes - Haven't got a headset, but BT GPS stays connected hour after hour.
Several reputable today plugins just don't work - Name one. I haven't had one single problem and I use many.
Let's face it; I am not the only one to have an issue with this thing. - And there are lots of users that think that it's more stable than 1.06.
MS, Imate, HTC, et all need to wake up and realise they will continue to be a footnote in mobile until they get this stuff sorted out! Let's hope WM5 will be better -- too bad we might not get it on our JAMs. - Oh yeah.. I've worked with QA and I woudn't have released even the 1.11 as 1.0! Terrible!
Ok, so with WM6 still in its "testing" phase and a few bugs that just wont seem to go away, I am being promoted at work and it will require me to use my phone as a tool for the job. ie direct push and all. Should i go back to my carriers WM5 release or Stick with WM6 in hopes that they will fix the rumored direct push issues?
i never got a direct pus problem on wm6... I use my mobile for work and i am using mb edition. I think is quite ok... on Faria`s i got some problems with gprs switching on and off all the time.... strange....
I've never used direct push. how do I go about setting it up. I can put together an exchange box if needed
nottoosmart said:
Ok, so with WM6 still in its "testing" phase and a few bugs that just wont seem to go away, I am being promoted at work and it will require me to use my phone as a tool for the job. ie direct push and all. Should i go back to my carriers WM5 release or Stick with WM6 in hopes that they will fix the rumored direct push issues?
Click to expand...
Click to collapse
I have experimented with all the WM6 releases, and have not encountered any issues at all with push mail and my Exchange 2003 Server. Within a couple of seconds of a new e-mail reaching my desktop, it hits my phone.
I also have my POP3 account check for messages at 1 hour intervals. No probs there either.
I was one of the unlucky ones who did have a problem with push email on Farias WM6 ROM. It would sync the first time the phone was switched on, but then some time later would randomly stop working even though the GPRS connection was still up and Activesync said it was 'Connected' - only a manual resync would get it going again.
I tried multiple radio ROMS, 2.19, 2.25, 2.47 and 2.61 (hoping it was a radio ROM problem) but to no avail. Interestingly, I never had this particular problem with the MB WM6 rom - but that ROM had other issues, so in the end (as always) I've dropped back to Farias 3.3 ROM which is rock solid in every area.
Don't get me wrong those of you who take offence easily - Farias ROMS are great and I'm not knocking him any way - it's just "one of those things" that's probably quirky to my setup. If when he produces a new version, I'll test again.
Andrew
Most odd. Like bradsnw I've never had a direct push problem. This includes the more than 50 individual devices I've setup in the past, the 10 or so that I upgrade on a regular basis and mine. As Faria's tester and Junior Chef in Training my poor lil 8125 has seen just about every ROM variant (and mutant) imaginable, but never a DP problem. (And I've created some near bricking ROM's let me tell you!)
One thing I always do however is to not create my initial AS profile with my PC but on my device directly. (This is the only way I can get my task OTA) and I probably hard reset my device on the shoulder of Interstate 95 or a McDonalds parking lot as many times as I do at home.
I've never had an issue with Direct Push/Exchange 2003 while using WM6 either.
Dr Puttingham said:
Most odd. Like bradsnw I've never had a direct push problem. This includes the more than 50 individual devices I've setup in the past, the 10 or so that I upgrade on a regular basis and mine. As Faria's tester and Junior Chef in Training my poor lil 8125 has seen just about every ROM variant (and mutant) imaginable, but never a DP problem. (And I've created some near bricking ROM's let me tell you!)
Click to expand...
Click to collapse
I agree - very odd. I've never had push fail before on the multitude of ROMS I've tried - those sort of problems always happened 'to other people' and not me ;^)
I tried all the usual stuff, resets, new partnerships, reloading the same ROM, new radio ROMS, certificates, etc etc etc. But in the end, I had to get the phone working 'for work', so went back to 3.3. Like I said, when Farias next ROM comes out, I'll try it again.
cheers,
Andrew
achick said:
I was one of the unlucky ones who did have a problem with push email on Farias WM6 ROM. It would sync the first time the phone was switched on, but then some time later would randomly stop working even though the GPRS connection was still up and Activesync said it was 'Connected' - only a manual resync would get it going again.
I tried multiple radio ROMS, 2.19, 2.25, 2.47 and 2.61 (hoping it was a radio ROM problem) but to no avail. Interestingly, I never had this particular problem with the MB WM6 rom - but that ROM had other issues, so in the end (as always) I've dropped back to Farias 3.3 ROM which is rock solid in every area.
Don't get me wrong those of you who take offence easily - Farias ROMS are great and I'm not knocking him any way - it's just "one of those things" that's probably quirky to my setup. If when he produces a new version, I'll test again.
Andrew
Click to expand...
Click to collapse
There's nothing wrong with your push email.
Connected is good, it means that you have a connection with the server and you're up to date. This is how it shows in WM6
When you see "Synchronized Today" with a time, this means that was the last time your device updated with the server for whatever [email protected] tihs point, if you have signal....do a manual sync.
Again...CONNECTED...is good ......... SYNCHRONIZED TODAY...is ok
If your device doesnt synchronize folders at all ....you need to adjust your network connections and get the web to work 1st and then push email.
This isn't faria specific, that's how WM6 works.
nottoosmart said:
I've never used direct push. how do I go about setting it up. I can put together an exchange box if needed
Click to expand...
Click to collapse
You need an exchange account.
I use www.4smartphone.com. It's a paid service that's cheap and I let them deal with the headaches of maintaining a server. The service has been 100% so far, not to try to sell you.
If you have the means and time to set up a box, let me know and I'll help as much as I can.
No problem at all with DP mail. I just give it to the people at IT and they set it up nicely for me. And I have taken it in daily because I keep changing roms!
But I am stopping at Faria's for now
dwny said:
There's nothing wrong with your push email.
Connected is good, it means that you have a connection with the server and you're up to date. This is how it shows in WM6
When you see "Synchronized Today" with a time, this means that was the last time your device updated with the server for whatever [email protected] tihs point, if you have signal....do a manual sync.
Again...CONNECTED...is good ......... SYNCHRONIZED TODAY...is ok
If your device doesnt synchronize folders at all ....you need to adjust your network connections and get the web to work 1st and then push email.
This isn't faria specific, that's how WM6 works.
Click to expand...
Click to collapse
dwny, I appreciate your reply, but I beg to differ. I've been using push mail for a long time now, and I know when it's working or not - I'm not going to bore everybody with pointless detail, but:
I had a working internet connection via GPRS - I could surf using Pocket IE.
It would "automatically" sync my folders via GPRS when I turned the phone on. It would then stop working later.
Manually syncing is not push email? I had set the schedule settings to 'as items arrive' - why would I sync manually?
And as I said previously, I did not get the problem with the MB WM6 rom, nor the PDAviet 3 or 4 and I do not get the problem with Farias 3.3. Mail arrives automatically via GPRS (usually a a few seconds before it hits my desktop outlook) just fine in every ROM I've tried except Faria's latest. But I'll repeat - I'm not in any way 'blaming' Faria. It's just one of those things.
Andrew
achick said:
dwny, I appreciate your reply, but I beg to differ. I've been using push mail for a long time now, and I know when it's working or not - I'm not going to bore everybody with pointless detail, but:
I had a working internet connection via GPRS - I could surf using Pocket IE.
It would "automatically" sync my folders via GPRS when I turned the phone on. It would then stop working later.
Manually syncing is not push email? I had set the schedule settings to 'as items arrive' - why would I sync manually?
And as I said previously, I did not get the problem with the MB WM6 rom, nor the PDAviet 3 or 4 and I do not get the problem with Farias 3.3. Mail arrives automatically via GPRS (usually a a few seconds before it hits my desktop outlook) just fine in every ROM I've tried except Faria's latest. But I'll repeat - I'm not in any way 'blaming' Faria. It's just one of those things.
Andrew
Click to expand...
Click to collapse
Again...this is how it works in WM6
When your device says "Connected" ... you are up to date.
While there..press Menu > Status and it will tell you when your device last synchronized.
WM5 shows "last synchronized" when up to date
WM6 shows "last synchronized" when not up to date.
What I experienced:
When I get "last synchronized" ... I also don't have internet and everything was working. I go to connections and change the name of the connection and all is well. Try this & see if it works for you.....
dwny, you ARE persistant!
"Again...this is how it works in WM6"
But it *wasn't* working!
I could tell it was not sychronizing because I would get 25 emails arriving in my Outlook inbox over period of an hour, and none of them arrived on my PDA! If I simply manually synced, they would all coming flooding in.
But let's not dwell on this anymore - I'm back on 3.3 now. If I find some time, I'll do a fresh download of the ROM and try again.
thanks for you time,
Andrew
Outlook
First, you get too damn much email. 25/hour? What are you, the president?
Seriously though, something has to be running to be able to get those push notifications. With all the tweaking people do I'm not surprised that things end up breaking. My suggestions are these:
1) Turn off X Button or whatever you are currently using to close rather than hide applications. WM5 and 6 were never designed for the apps to be closed every time. Many have background features that they depend on -- like poutlook. Why do you think it's in your \windows\startup folder.
2) It is *still* in your \windows\startup folder right?
Those are your hints -- all I know is that push worked fine for me as long as I left something there to push to.
baarod said:
First, you get too damn much email. 25/hour? What are you, the president?
Seriously though, something has to be running to be able to get those push notifications. With all the tweaking people do I'm not surprised that things end up breaking. My suggestions are these:
1) Turn off X Button or whatever you are currently using to close rather than hide applications. WM5 and 6 were never designed for the apps to be closed every time. Many have background features that they depend on -- like poutlook. Why do you think it's in your \windows\startup folder.
2) It is *still* in your \windows\startup folder right?
Those are your hints -- all I know is that push worked fine for me as long as I left something there to push to.
Click to expand...
Click to collapse
President? - lol... I wish...
I get automated warnings and messages from databases and servers. And when things aren't running well, I get LOTS of emails.
Yep, poutlook was in my startup....
Anyway, after seeing all these success stories, I downloaded the ROM again (didn't trust the last download) and reflashed. Followed exactly the same procedure as normal (I flash ROMS regularly, so literally have my set routine) and guess what?
Works fine - 'straight out of the box'. I did nothing different to every other flash I've ever done....
Andrew
P.S. I now have an 'officially recognised' issue with the 2.61 radio ROM. But at least I'm back in the fold...
i am running the mun rom on tmobile usa and have no problems with exhange mail...push is working 100%
FYI - i am using the 2.61.11 radio rom
achick said:
President? - lol... I wish...
I get automated warnings and messages from databases and servers. And when things aren't running well, I get LOTS of emails.
Yep, poutlook was in my startup....
Anyway, after seeing all these success stories, I downloaded the ROM again (didn't trust the last download) and reflashed. Followed exactly the same procedure as normal (I flash ROMS regularly, so literally have my set routine) and guess what?
Works fine - 'straight out of the box'. I did nothing different to every other flash I've ever done....
Andrew
P.S. I now have an 'officially recognised' issue with the 2.61 radio ROM. But at least I'm back in the fold...
Click to expand...
Click to collapse
Glad to see a fresh install worked for you.
Be careful with radio 2.61.11, it's known to cause dialpad issues and missed calls with the newer roms.
Anyone else having an issue with the Wizard not vibrating on receipt of a new e-mail when the device is on standby? Does anyone know if this is correctable with a tweak to the registry or somewhere else or if it's a bug in the OS files themselves? Does anyone on the MB or aRTM ROMs have this problem?
When the device/screen is on, I'll get a vibrate notice on new e-mails, but not when it's on standby.
I'm having no issues with anything else in this ROM and it's a keeper even if I don't get the vibrate working, but it sure would be nice to get that working.
Thanks.
-Pete
Gor to Start Settings, sounds and notifications. Tap the notifications tab. for event new email, check the vibrate box.
badersk said:
Gor to Start Settings, sounds and notifications. Tap the notifications tab. for event new email, check the vibrate box.
Click to expand...
Click to collapse
Yes, that's set. Everything works fine except when the device is on standby. If I'm actively using it or the screen is otherwise active, the device vibrates on new e-mail as expected. When it's on standby and I receive a new e-mail, nothing happens.
-Pete
paschott said:
Anyone else having an issue with the Wizard not vibrating on receipt of a new e-mail when the device is on standby?
Click to expand...
Click to collapse
Yeah I am having the same problem...sorry I don't have a solution but just wanted you to know you aren't the only one.
fryman said:
Yeah I am having the same problem...sorry I don't have a solution but just wanted you to know you aren't the only one.
Click to expand...
Click to collapse
Ditto. I have the same prob. Sounds but no Vibe. BUT, Faria's ROM is so far THE BEST that I have used yet (and I've used a lot).
Well, good to know I'm not alone. I've said it before - I don't think this is a problem with Faria's build particularly, but more than likely something in the ROM/OS itself. I like everything else about the ROM and am not considering switching back at this point. It's just disappointing that this one feature doesn't work right now.
Still, if the WM6 release was actually a year ago, it could have just been a bug in WM at the time that has since been resolved. I know that WM5 1.18 had this issue and it was fixed in the 2.* releases. Hopefully this will be similar (and we'll actually be able to get the fix when it's GA).
-Pete
Same problem here, the Molski AKU 3.2 rom had the same problem, the AKU 2.3 was working. A lot of people got this problem, nobody knows what the problem is (even the official NL Tmobile rom got this problem)
This isn't unique to just Faria's WM6 ROM. I've tried both MBE and mUn's aRTM ROM and they both had the same problem. Push e-mail isn't as common yet as the old POP3 pull e-mail and I suspect that more people aren't reporting the problem because of that.
As was mentioned by others, I imagine this will be fixed in future releases of WM6 since it was an issue with earlier releases of WM5 and wasn't fixed until the AKU 2.* releases.
I know, but I still think it is strange that this problem keeps coming back. Isn't there anybody who knows how to fix this problem? That is one of the key features of WM and a lot of people want to use this feature.
(and yes, it will be fixed in the future but I want to know what the problem is )
I am having the same problem with MBE. Any Fix yet?
SavageNL said:
I know, but I still think it is strange that this problem keeps coming back. Isn't there anybody who knows how to fix this problem? That is one of the key features of WM and a lot of people want to use this feature.
(and yes, it will be fixed in the future but I want to know what the problem is )
Click to expand...
Click to collapse
fixing the problem is realy easy guys,i know for sure that all of u guys forgot to create an accout on ur pda.easy dont sign to wm live then just open ur imbox then a window will apear other than the imbox at the end there is a new account , make one and use the internet settings and ur good to go
I'm running Faria's final edition of WM6 on my Wizard, pretty much stock except for mun's keyboard and a few apps. This rom is almost perfect for my needs.
The only problem is that when the wizard is connected to my computer USB port to charge, it won't go to sleep... In fact, if I press the power button, it turns off for maybe a minute then turns right back on again!
I searched the forums looking for an answer and came up with very little. I do recall seeing some tips for preventing this behavior several months ago but can't seem to find the post anymore (???).
Actually I had this issue fixed on this rom at one time, but then I went and re-flashed about 20 times, trying all the latest cooked versions out there before returning to Faria's. But now I can't recall the fix for the power-on problem!
So, could someone help me out and re-post the fix?
Many thanks in advance...
Don't know of a fix, but this happened to me also when using Faria's ROM and still happens now using the NBD ROM.
Have same problem with Core 2.0n
Same with my XDA ROM. I thought thats a WM6 feature that I have to live with.
It's a common problem then...
Ok, this sounds like a common problem then.
I've been thinking about it, and if I recall, I think the posted fix might have been from mrfrazz or dr puttingham... I'll try to PM them (not that they know me) and see if I can get them onto the thread....
Wasn't from me.
Ok thanks for that mrfrazzz.
How many folks have this problem? Does anyone have a fix?
Sorry, not from me either.
remove the pin password (start -> settings -> lock). used to solve this problem for me on older WM6 rom's. Don't know if the problem still exists in the newer roms...
nbd 7.4 has this problem and also wm6 business edition.
I am using the Dopod Pro 838 [Mobile 5] and have the same issue, when connected it does not sleep, no matter how many times I close the screen off
Thanks everyone for chiming in. So this is a widespread problem.
Is there a solution? Or is everyone just living with it?
For what it's worth, I've searched and searched and can't find that post with the solution. The only reason I can think of is that the post was removed. (?)
Oh well. I guess I'm going to have to live with it like everyone else until an answer turns up. If anyone has any info or ideas post here and we'll try it out.
WM6 TNT 3.0.... same problem
settings, system, backlight settings?
i'm using an enhanced xm6 and i don't seem to have this problem when i charge with the usb at work (no activesync installation). perhaps you may need to disable that, because i recall reading somewhere that activesync tends to wake the phone from time to time to constantly resync pim information.
if you don't like the backlight on, you can go to settings, system, backlight, and change the settings there. I know on faria's roms, the backlight goes off after some time, even when it's plugged into the usb. t-mobile's default rom and the one i'm currently using don't turn off, unless i hit the power button. (but unlike what was initially stated, my phone doesn't turn back on).
or in case i've misinterpreted something...i recall reading that in some roms, the phone would keep waking up due to the push service and it would require some combination of locking the phone to get it working. in those cases, i believe you have to read the respective rom thread. i know farias "the real thing" thread has info on it.
Thanks for the suggestions, I'll look into somehow getting better control over activesync.
Yeah, that's about where I'm at, just turning off the backlight and pretending the phone is off. But it still kind of irks me, all I want is for the phone to sync then go to sleep until I need it. And stay off when I hit the sleep button...
I've had this problem forever, and I consider it a "problem" because my phone is overclocked to 273, and I'd like to keep it off to keep the temperature down. It's definetly not a rom issue, but like someone else stated, it's an activesync issue. Even disabling sync options on activesync doesn't seem to help, only thing I can think of is uninstalling activesync, but who the hell wants to do that? Maybe preventing activesync from starting or running in the background on windows start, until you want to open activesync manually?
This is the random wake-up problem that first apeared in some build of WM5 (I guess). I too can't find much info on it but I guess you could remove the pin prompting. It happens due to activesync/wmdc and usb connection while the pin is enabled. I guess this is a bug in WM6 which is yet to be fixed. Hope microsoft and WM6 team reads this thread.
May be end tasking activesync in both phone and system will help. I haven't tried as I live with it and is not an issue for me.
with PhoneAlarm there is an option to disable the ActiveSync scheduling within a profile (eg profile work no ActiveSync, while ActiveSync will still be usable at home)
Maybe this can help you?
btw, PhoneAlarm has some other very nice features, it's still my nr 1 app for the wizard!
any one else getting it? unit goes in to standby and then wont wake up you have to soft reset.
ive been getting it frequently very anoying im using the big storage rom i dont rember who made it i can find out of some one wants to know
but is any one else having problems like me?
No problems here. I'm using the clean 1978 ROM...
I had it happen yesterday, running the stock AT&T ROM.
Hi
No problems here either.
It's worth remembering the phone wakes itself up about once an hour, although the display is dark so you will not see this happening.
If you have installed some software that doesn't handle this switching on very well and it crashes the phone, it will look the phone has died in standby, but it probably hasn't, it just looks that way.
I would advise a clean reset and not to install any programs, and see if it happens again. If it does your phone may be faulty, for example a memory problem that surfaces when the phone goes into a low power state.
Regards
Phil
Mine SOD'ed last night. I was using the phone, turned the screen off using the power button, then plugged it into my computer USB to charge. I was trying to do it one-handed and as you could imagine I was fiddling with the cable/phone for 30 seconds before I got the mini-usb plug into the phone. I watched to see the charging light come on but it didn't. I then tried to turn on the phone and realized I was SOD'ed. It only happens to me once every 1-2 weeks. My phone runs the stock Tilt ROM, but with lots of custom cabs installed, ie:
HTC Home 6 button
HTC Taskmanager 2.0 30995
Skype
Color Dot battery indicator
Schaps 10 Button Comm manager
PocketCM
Funambol 6.5.4
I push my phone all day long, surfing, ssh'ing into servers with putty, imap email, playing music etc, and I think if there was a bad memory issue Id see something other than an SOD. IMHO,theres a bug in the power management software.
SOD happened on my Tilt too. Im runnig the ATT rom. I had the same problem with the 8525 with the earlier ROM. The problem is IMAP email push. IF you use IMAP there is a chance you will get SOD once in a while. I changed all my emails to POP3 never had SOD since then.
I think you guys have to run the kaiser tweek to turn off the sleep mode in the registry. I had the SOD once....forgot to modify the registry via the kaisertweak app. 1st 2 options i think is what you have to modify.....that should fix you guys up.
Happened With Me too !!!
Now after using my at&t tilt flashed with HTC stock rom for 5 days, suddenly today my device suffered from a SOD.... had to soft-reset.... tried to figure out what went wrong but without any luck..... do any of u guys figured out the cause.... Kaiser Tweak only allows us to disable the sleep mode during call.....
kaiser falling sleep happens to me so frequently that I read all the posts with the key words KAISER FREEZE on xda-developers.
The only solution seems to power off and on again.
On modaco.com somebody posted a small applet which does automatically the power on-off for you.
Of course this does not remove the problem, just hide it...
Additionally I have tried 4 different WWE ROMS! from Att to HTC original ROMS to cooked Helmi aka 0.7.0 etc... No way to solve.
Please if modifying the registry can solve, can somebody post the link for kaiser tweaks and possibly the application?
Thanks
Saulo866
I think it might have something to do with Windows Live Maps program. This happend to me everytime I was using the program in the background. I upgraded the version and it stopped the problem I was having.
hollywood said:
I think it might have something to do with Windows Live Maps program. This happend to me everytime I was using the program in the background. I upgraded the version and it stopped the problem I was having.
Click to expand...
Click to collapse
Same here... I upgraded to helmi_c's Tilt ROM and haven't had the problem since. Pretty much guarantted though, if you leave Live Search running in the background and your phone goes to sleep... it will not wake up with the stock ATT ROM (at least with the current version of Live Search).
Cheers!!
SOD has typical been associated with running programs off of a Storage card. I had tons of SOD problems with the early WM6 Hermes ROMs. So far I have only had SOD a few times on my Tilt (running austinsync's BigStorage ROM). I installed Google maps to my microSD and within 20 minutes had 3 SODs. I uninstalled it and they stoppped immediately (Live Search is way better anyway).
I would recommend installing any programs that you use heavily or leave running onto the main memory. Also, saving attachments to a storage card has been a known cause as well.
I think SOD issues will get better as more ROMs start coming out for the Kaiser (and the chefs keep cooking).
OK, this keeps happening to me with the AT&T ROM....today it happened with no programs running in the background, anybody figure out a solution yet?
Me too
well I've had this problem also while running my own cooked rom, however to be fair i had this problem in the early days of the hermes. I thought however that the hermes problem was related to activesync's push email and the data connection (i.e. switching between 3G and 2G alot making activesync trip out) That all said maybe I'm barking up the wrong tree?!
Oh just in case anyone as the time to investgate this problem, I do know the Toshiba G900 had alot of problems with SOD inwhich tosh releases a fix for...... maybe if someone was to look at what that fixed it could help us here? have a read here > www.my900.com
Kaiser won't power back up
My unit after reset won't either power up or down with the power button. Everything still functions.
I found that if I have the power charger connected it works fine, so I thought I had a weak battery. Got a new battery and same thing.
Don't know what's going on, but if you do a soft reset with the charger plugged in, it will reset fine.
Hope someone figures this out!
Be careful overconfiguring...
PhilipL said:
Hi
No problems here either.
It's worth remembering the phone wakes itself up about once an hour, although the display is dark so you will not see this happening.
If you have installed some software that doesn't handle this switching on very well and it crashes the phone, it will look the phone has died in standby, but it probably hasn't, it just looks that way.
I would advise a clean reset and not to install any programs, and see if it happens again. If it does your phone may be faulty, for example a memory problem that surfaces when the phone goes into a low power state.
Regards
Phil
Click to expand...
Click to collapse
This might be the case, but I tried calling my phone when it SOD'd and didn't get a ring (it rang on the phone I was calling from.) I bet the problem is installed programs conflicting somehow, maybe kaisertweak will fix it in the future.
I can't guess what causes it tho...
For now, I'm running Kyphur's XDA Live and it has yet to happen.
PocketCM
rotohammer said:
Mine SOD'ed last night. I was using the phone, turned the screen off using the power button, then plugged it into my computer USB to charge. I was trying to do it one-handed and as you could imagine I was fiddling with the cable/phone for 30 seconds before I got the mini-usb plug into the phone. I watched to see the charging light come on but it didn't. I then tried to turn on the phone and realized I was SOD'ed. It only happens to me once every 1-2 weeks. My phone runs the stock Tilt ROM, but with lots of custom cabs installed, ie:
HTC Home 6 button
HTC Taskmanager 2.0 30995
Skype
Color Dot battery indicator
Schaps 10 Button Comm manager
PocketCM
Funambol 6.5.4
Click to expand...
Click to collapse
I was running Kypher's Tilt XDA-Live v 1.0 (AWSOME) with several custom cabs including PocketCM and was getting the SOD every time. I wiped the phone and started adding all of my cabs one at a time and all of them are loaded back in except PocketCM and since then i have not seen a single SOD.
Tim
I've noticed that I get the SOD a LOT more when I have bluetooth active. Not sure if that's just coincidental but literally the only time I've noticed the SOD has been when I've had BT enabled.
Happens to me a few times a week very annoying.
Well, I don't do emails, use Windows live, have pocketCM, used my bluetooth, tried Google maps, or have any programs on my sd card (basically whatever you all mentioned above, I don't have or do!), and still get SOD. So I guess I start backtracking. Sigh...
tilt with xda Live