I have just one issue after switching to Windows Mobile 6 (at first "Faria real thing", now "Crossbow Reloaded"). Sometimes the phone behaves as if the sound was switched off.
I read various discussions about which radio ROM is better etc. for not missing calls, but I guess it is not that problem. The call gets through (so I guess radio rom is ok). When having the phone in such state, I checked it by calling from the fixed phone on my desk - the call got through, there was message on the display that somebody is calling (just the ring was silent).
Once in such situation I tried to switch on/off the phone application - no change. The one thing which seems to cure it reliably is to go to the phone settings (I usually try the ringing tone I use - it works ok - and press ok). Afterwards it is normal (the phone rings).
I have not found yet any pattern when this happens... Is it possible that the phone somehow loses setting (about the set ringing tone, or about volume) and it is fixed by going to phone settings?
Has anybody else such experiences?
Othewise I am happy with WM 6 (especially I like "Internet Sharing", quicker booting and the fact that when running "Opera Mini" in "Midlet Manager" it no longer ignores hardware soft keys). Just this think is a bit of nuisance.
Mirek
I've seen this a few times myself, and yes, just playing your ringtone via the Phone Settings will fix this issue. I can say that I haven't seen this issue in some time, and thats since I stopped using the press & Hold of the CommManager button (upper left side of the phone) to switch my phone in and out of Vibrate mode. I used to use that to do a quick switch and it seemed sometimes after coming back out of vibrate mode, this issue would happen (not always, but a few times). I've now quit using that button that way and I don't think I've had the non-ring issue since.
Thanks you for the information, I will try it. It may have been the problem with that button - I mapped there task manager which I use often and pressed it sometimes a bit longer...
Mirek
Related
I flash the my hima with the TofClock 2.01a32WWE ROM, and it works fine, and I'm very glad with it.
But now, some time I turn off my hima by pressing the power button, the screen went black, after a while, I want to light it to operate, the hima keeping black, and the hima cannot operate any more, and I tried to call my phone(hima), the hima didn't ringing. Also, SMS, MMS, all function dead. But the same time, the 2 leds, Blue and Green/Red, flash like normal.
At this time, the only way to operate hima normally was soft-reset it by press the hole with my pen.
:shock: :shock: :shock: :shock:
Is there someone experience this situation, and is there some way to solve the problem.
:idea: :idea:
ps: in the Settings --> System --> Power --> Advanced page, the 2 options can set "Turn off device if not used for" some minutes, when "turn off" time out, the same problem occurs like above, I called it Auto Turn Off
My device is Dopod 696 (Maybe Chinese mainland version of O2 XDA II).
:wink: :wink:
I also experienced similar problems, but with the 64 version.
After a while, when I tried to turn it back on, it began to act strange. First the automatic turn off backlight option was every time reset to 10 sec and then after a day or 2 I noticed that the screen was sometimes still showing some black lines. Changing the volume still gave the corresponding sounds, but nothing else seemed to work (or wasn't visible). Normal operating mode was only reinstated after a soft-reset.
I gave it a hard reset and restored a backup (using SPB). It's operating again, but it already contains the 10 sec change.
So probably have to start clean again and install everything from the beginning, but before I do I would like to make sure it will not happen again.
Appears like the Power Off option is screwed, no matter in which way I use it (button or a program).
Anyone have any thoughts on it?
zplei
yes, i have same problem on my O2 XDA ATOM
with last rom and other
I have the same problem too, the only ay to have it back is softreset
i was using spb to toggle display mode.
someone said can be solve by reegedit. but how to.
anyone found a solution..?
i'm looking for a way to have the touchscreen on my smartphone disabled when a call comes in. I usualy have the phone in my pocket. When a call comes in and i'm taking the phone out my pocket, i accidentely touch the screen. And that's mostly not in the "accept" spot off the screen
So i would like to accept or decline the call by pressing the hardware keys only with the touchscreen disabled.
Been searching the forums and googled my way over the internet. Without luck so far.
Any ideas?
regards, Jeen
S2U2 uses a slide to answer feature, very nice.
Installed s2u2 and it sure looked great... until the first soft reset (after nightly backup). After the soft reset the phone freezes every time a call comes in, having to soft reset again. Whenever a call comes in (when phone is locked or switched off) the normal s2u2 lock screen pops up without the call notification and that's it. Phone freezes and soft or hardware keys don't work anymore.
I even uninstalled SPB Mobile Shell to see if that was conflicting with s2u2. No luck.
Couldn't get rid of this problem so i uninstalled s2u2. Shame, i liked it...
Any other options to answer my original question?
regards Jeen
Hi
Unless I'm actively using it my TP keeps turns itself off after 30 seconds no matter what power settings I use (and despite a factory reset and SPB restore). This isn't too much of an issue, except when I'm trying to use GPS/Satnav (TT7) whilst driving, where turning itself off is a real pain.
Could anyone please suggest how this issue can be resolved?
Many thanks in advance...
Is it physically turning off, requiring you to press the on key, let it reboot, or,
is it going to sleep, and you press the on key to wake it up?
If it is the latter, go to start>settings>system>power, click on the
advanced tab and change the backlight & power off settings there.
If it actually turning off, sounds like it might be a defective phone.
Thanks for your reply!
I've repeatedly altered the power settings but it makes no difference at all, if I set it to turn off at any given time (or not at all) it'll still turn off after 30 seconds. And to claify, it doesn't reboot, it just turns the screen off. It *feels* like a software issue, because it'll stay working forver as long as I tap the screen occasionally, something somewhere just counts down 30 seconds if i don't and turns off the screen...
The max time you can put on it is 5 min. The default setting out of the box is 30 seconds --which sound like what you currently have.
Set the "On Battery Power: Turn off backlight if device is not used for xxx MIN). Make sure first that that's checked, and select the drop down.
Eventually --to conserve battery power--, it will 'sleep'.
Your NAVIGATION software should have a setting to over-ride this to NEVER TURN OFF DISPLAY WHILE NAVIGATION.
Aside from that, there is no other way to keep the backlight on --unless it's plugged into a power outlet.
Many thanks again for your reply; As I mentioned previously I've already changed the power settings settings (frequently) and I'm definitely not on the 30-second default, no setting appears to make any difference, be it 5 minutes or 'never turn off'. It also happens when the 'phone is plugged into a power source too.
(And I have got the 'don't turn off whilst navigating' box ticked for the satnav but the issue applies generally, not just to the satnav, that's just where it's most irritating).
Is there any possibility something has changed in the registry to over-ride the control panel settings in this way?
How about doing a hard reset and not doing a spb restore? You realize that all you did when you restored the phone was restore the bug, right?
Edit: I doubt it will work, but you can try the backlight cab. It will restore all the stock backlight reg settings if yours are messed up.
timpollard said:
Hi
Unless I'm actively using it my TP keeps turns itself off after 30 seconds no matter what power settings I use (and despite a factory reset and SPB restore). This isn't too much of an issue, except when I'm trying to use GPS/Satnav (TT7) whilst driving, where turning itself off is a real pain.
Could anyone please suggest how this issue can be resolved?
Many thanks in advance...
Click to expand...
Click to collapse
Hi,
I have same problem as you. TP keeps turns itself off after 30 sec!!
And I am using TT7. So this problem is so annoying.
I tried hard resetting and install programs one by one. and check if TP is keeping backlight on or not. And I installed TT7 and worked perfect.( display is always on)
That was yesterday.
Today I was using TP, it happened again.
The registry setting is still 3min on battery, uncheck on AC power.
30 sec problem happens both status.
This thing did not happen before Raphael_Cingular_US_5.11.502.2_Radio_Sign.
TP worked fine for a while on this radio.
Now even I check " NEVER TURN OFF DISPLAY WHILE NAVIGATION" box in some apps. TP turn off backlight.
I tried backlight.cab, that did not work and still turning off.
(thanks anyway )
ATT Fuze
Raphael_Cingular_US_5.11.502.2_Radio_Sign
Added Japanese IME
Resco Explorer, regedit
Resco Today Plugin
Spb time, Today plugin
TT7
TomTom 7 - v7.910.9185
I will try hard reset again.
Somebody please help us out.
Did you try the cab? If that doesn't work, just flash another rom.
I am also having this problem. I did get it to stop once by going in to the registry and actually editing it. But it started to do it again after a wile. I am trying it again today and see if it work. I am using a trial version of BestRegEdit and was wonder if it could have changed it back because it was a trial. So if some one elce wants to give it a shot it us under HKey_Current_user\ControlPanel\Power\Display and you will change that 30 to what ever amount of time you want. I pick 0 because i never want it to turn off. Hope this helps Oyeah, does anyone know of a free resitry editor? This is my last day on the BestRegEdit Thanks
Uh, total commander, regedit, dotfred's task manager and probably a few more.
Farmer Ted said:
Did you try the cab? If that doesn't work, just flash another rom.
Click to expand...
Click to collapse
Thanx,
I tried cab, and did not work. So I installed test rom and works fine now. NO 30 seconds backlight off now.
[March 1st] New ATT test rom Radio 1.12.25.19 OS AKU 1.4.6 Build 20771
I will use this until new "Signed" and Works Ok radio comes.
* Recently I use resco explorer and regedit addon. Free app: regedit.Mrln works fine, I think. I have been using these for keyboard layout section.
Glad you solved it, I had an interesting problem, similar to the screen issue, wonder it it might be related. I flashed to a new rom over the weekend, and no matter what I did, the backlight would turn off after 10 seconds. You could reset it to 30 in the power profile, but after a reboot, it would revert back to 10 seconds. Reflahsed it, and after the flash, when it starts loading the customizations, it would freeze. Flashed again, and it hung at customization again! Downloaded the rom again, deleted the old one, and flashed and it worked and the backlight would stay put!
Maybe the one you downloaded was corrupt?
Anyway, glad you got it working.
P.S. The rom isn't an "official" that I downloaded, it was one of the 6.5 that the cooks on the rom page whipped up. I think it was just a corrupted download.
This issue has happened to me a few times. even while i'm still using the phone and typing the screen goes off.
very annoying.
I found it only happened to me using EnergyROM. when I flashed to a different rom the problem was solved.
recently I flashed back to the newest version of EnergyROM again (after the previous ROM decided to hard reset all by itself) and this issue happened again in the first hour!
I really wish I could find a usable ROM for once and for all
My Case: WMWifiRouter was it!
This happend even when TP under Test rom env. I just gave up and installed latest version cause this ver is less stressfull.
Luckly 30 sec issue did not happend for a while until I installed WMWifiRouter.
Just after I install V1.50 30 sec thing and happend.
KB0907027: [BUG] v1.50 backlight timeout issue
http://support.wmwifirouter.com/knowledge/KB0907027/
I Installed V1.52 and now works fine and no backlight problem.
If you installed WMWifirouter check the link.
I use EnergyROM as well and i noticed that right after a fresh flash, if you tried to modify certain settings using the gui (i.e. alarm times, connection settings etc) they wouldnt stick - perhaps a direct registry edit using one of the tools previously mentioned might force the device to remember the changes? this worked for me when i had trouble with my alarm times not being saved.
ive also heard that sometimes a soft-reset isnt enough to commit changes to the registry - i.e. once making a reg edit, cold boot the device - that is press and hold the power button and turn it entirely off.
hope this helps
Hi everyone. Im sorry for posting this as a new thread again. But this is just desperation. (Moderators you can delete this if u feel im unnecessarily clogging the forum.) But im really so pissed off with this problem that throwing my phone is seeming my next option. Im really thankful to all the replies in my previous calls for help. I'll just write my problem in detail:
My phone - HTC P3350 (Love) with WM 6.0
ROM version: 3.17.720.3 WWE
ROM date: 21/01/08
Radio version: 02.94.90
Protocol version: 4.1.13.44
ExtROM version: 3.17.720.103
My exact problem -
1. Whenever i bring back my phone from stand-by mode by pressing power button, the green call receive button somehow gets pressed from the 'inside' and depending on what window is open the action takes place. For eg: if im on my today screen, the dialer screen opens up; if im on the dialer screen, the last dialed no starts getting dialed; AND THE WORST PART - if someone calls me when my phone is on stand-by mode, the call automatically gets received (coz the green cal receive button virtually gets pressed)!!
2. The super-added problem is that if i press the power button to put the phone into standby when im talking to someone, the speaker phone gets activated and then exactly 3 seconds later the call hangs up.
The problems are so weird and 'funny' that im getting to think its a virus doing all this.
What i tried doing -
1. i hard reset my phone and restored using sprite backup. The problem persisted.
2. So next i hard reset again and restored using PIM backup and restored only the contacts. The problem disappeared for a day but reappeared.
3. So i hard reset again and this time i didnt restore and i also removed my storage card. And now the problem has become unpredictable! It appears sometimes and sometimes the phone is completely normal.
Im trying hard to find a pattern as to when it appears for eg: whenever the battery is low; only during the evening, etc. I dont know but i've not found out any fixed pattern (which i expected if it was to be a virus)
My current status -
I disabled the 'Turn off device if not used for' option in Advanced Power settings. And i never put my phone on standby. I just use the device lock option. But the problem is that battery running out twice faster.
This has just temporarily treated the problem but the basic problem still remains....
I do not have auto lock turned on. I did load the VZW "clean up" cab. I can't figure out why sometime when I pick up the phone the lock is on, and other times the screen is simply turned off. I never hit lock, simply turn off screen or let it go off automatically.
Anyone have an idea?
Thanks.
Are you sure you are not hitting the top button accidentally. That button will turn off the screen.
I do use the top button. It only turns off the screen though, not locks the device. I can use it, then hit it again minutes later and the device is fine. But sometimes I'll put the phone down or aside for a while, and when I pick it up to answer a call or something I'll find it has locked itself and I have to press the soft keys.
hmm... sounds strange, I gotta go with what the 2nd guy said, I will sometimes lock the device myself (the soft key for it is on the home screen after all and it's VERY sensitive). About the screen turning off, you sure it's not just going into it's timed sleep/standby mode?
hopefully this will be of some help...i too had this problem and then i realized what the cause of MY problem was...whenever i would receive a phone call and would let it go to voicemail, when i would wake the phone back up it would be locked...i cant remember if the same thing happened when i answered the call but i know for sure it would do it when i pressed ignore call or mute ringer and let it go to voicemail...SOLUTION:i downloaded a cab called disable auto lock (or sumthing like that) and it fixed the problem...hopefully that helps..
mwrood said:
hopefully this will be of some help...i too had this problem and then i realized what the cause of MY problem was...whenever i would receive a phone call and would let it go to voicemail, when i would wake the phone back up it would be locked...i cant remember if the same thing happened when i answered the call but i know for sure it would do it when i pressed ignore call or mute ringer and let it go to voicemail...SOLUTION:i downloaded a cab called disable auto lock (or sumthing like that) and it fixed the problem...hopefully that helps..
Click to expand...
Click to collapse
I've been trying to figure this out as well and came to the same conclusion. My screen is off, I answer a call, and when I hangup my screen is locked. I did a quick google search for disable auto lock and didn't have much luck. Can you post the name of the file and where you got it? Thanks
Not sure where I found it, I think PCGeeks, but it was called Disable_Auto_device_lock.cab
HOWEVER...it did not work for me. I may have to cold reboot (from scratch) as I've tried so many different cabs, things are getting messed up. I'm trying to hold off for the ROM update.
The phone will automatically lock if you miss a call. Sometimes if you pick up on the last ring the phone will consider it a missed call and still lock the phone. That has happened on my 6700, my 6800 and now my TP2, but this is the first phone that locks after a missed call. I actually like it becuase since I dont have a S2U2 or 6.5 on the phone it prevents butt dialing if I leave my phone in my pocket or soemthing.
I have noticed the same issue. I also noticed that it did not happen before I had installed the clean up cab. I had thought that the lock button was being hit while the phone was in my pocket.
Although the "Disable auto..." didn't work for me, I down loaded and am trying S2U2. So far, and if I'm not mistake, It did not lock me after a missed call, or answering a call.
I'm going to play with it for a while. Had something similar before on my old Q9c so if it works, great!
I just hope all these friggin cabs work when I update to 6.5, or I may not! The only real pet peeve I have about the TP2 is earpiece volume. If the cab volume booster doesn't work, I won't upgdate!
I have this issue as well. It seems to lock if the person that calls me hangs up before I do. It also locks if I ignore a call. I have had it lock in the middle of a call as well. Really annoying if I need to use the onscreen keyboard to enter information during the call.
I hope someone can find a solution for this. So far, it's my only complaint about this phone.
Well, I've been using S2U2 now for a couple of days. Getting to like it! My screen no longer locks, and I kind of like the Iphone type unlock. When a call comes in 2 nice large buttons for either answer, or end (ignore).
You may want to try it.
Mine does the occasional random lock also and when it does, it wants a password that does not exist. IF anyone knows what the standard password is, please let me know. I don't have one set and need to reboot when this happens. Really my only beef with the phone which hopefully gets fixed in 6.5
I have found that if I receive an SMS the screen will come on on its own. In those circumstances I have seen it lock the screen afterwards.
I am thinking it is a failsafe put into the phone for accidental button hits after the phone wakes up from certain activity but could be in a pocket.