I have discovered that if I let my Pure go into sleep mode when it wakes up, it doesn't "take calls". I have 2 phones, one for personal and one for work. When I call the phone running android, the phone I call from rings and rings then goes to vmail, but the android doesent even register a call came in.
It does let me know I had a voicemail
it does pick up on text messages.
Just not incoming calls.
When I try to call out after I wake it up from sleep mode, it tries, but just does not want to connect. Phone doesn't freeze, just never makes the call. when I try to hang up, the "hanging up" screen stays forever, but I can go back to home screen. The phone icon in the top left taskbar never goes away, either.
I am using builds from the 26th-27th aug.
I am fairly certain this is a known issue, but is there any workaround for this? Perhaps command in startup txt regarding sleep mode?
smoakeater said:
I have discovered that if I let my Pure go into sleep mode when it wakes up, it doesn't "take calls". I have 2 phones, one for personal and one for work. When I call the phone running android, the phone I call from rings and rings then goes to vmail, but the android doesent even register a call came in.
It does let me know I had a voicemail
it does pick up on text messages.
Just not incoming calls.
When I try to call out after I wake it up from sleep mode, it tries, but just does not want to connect. Phone doesn't freeze, just never makes the call. when I try to hang up, the "hanging up" screen stays forever, but I can go back to home screen. The phone icon in the top left taskbar never goes away, either.
I am using builds from the 26th-27th aug.
I am fairly certain this is a known issue, but is there any workaround for this? Perhaps command in startup txt regarding sleep mode?
Click to expand...
Click to collapse
Hi smoakeater,
this is a know issue which is document and talked about in the main XDANDROID thread all the time. It's being investigated on.
Please don't open up new threads for every little bug - of which we still have a thousand - which are already known.
Thanks for your understanding.
Michael
Sorry, dude.
Will keep noob questions to a minimum in the future.
huh!!! Do u think its a small issue....The phone is just like a brick in sleep mode...I pray that u shouldnt be having this problem coz u ll convert your freinds to enemies..when u are not calling back the freinds who called you.....with not even a miss call notifications....I do have the same problem with Artemis..Any fix for that..
earthwind3 said:
huh!!! Do u think its a small issue....The phone is just like a brick in sleep mode...I pray that u shouldnt be having this problem coz u ll convert your freinds to enemies..when u are not calling back the freinds who called you.....with not even a miss call notifications....I do have the same problem with Artemis..Any fix for that..
Click to expand...
Click to collapse
To whoever your answer was directed at, but nobody treats this issue as small. Use pm.sleep_mode=1 without overclock and you should be fine. When you OC, use pm.sleep_mode=2 for the time being.
Michael
I have the same problem. pm.sleep_mode = 1, 2 and 3 do not help.
thank you
thank you for this post i have bin weeks trying kernels and other things
no i have the latest kernel 01250 and setting pm.sleepmode to 1
and it works i have the same trouble by gingerbread so this will work on gingerbread to i think
thank you again people
mweirauch said:
To whoever your answer was directed at, but nobody treats this issue as small. Use pm.sleep_mode=1 without overclock and you should be fine. When you OC, use pm.sleep_mode=2 for the time being.
Michael
Click to expand...
Click to collapse
are you able to elaborate on the settings of 1, 2 and 3? ive only seen this suggested to be set to 1. thanks.
edit: found this
http://www.androidonhtc.com/wiki/Boot_Options
and this info below elsewhere:
Sleep Modes: (pm.sleep_mode=) in the startup.txt
This is supposedly for topaz/rhodium that I found on the xda wiki:
* '4' will do "wait for interrupt", no change in arm11's clock or voltage
* '3' will do "wait for interrupt and ramp clock", the arm11's clock is lowered to 20MHz instead of 300-500, and voltage is lowered too.
* '2' will do "app sleep", arm11 is still on, but put into low power mode (registers are still saved)
* '1' and '0' will totally power off the arm11 (so we have to restore registers and things ourself), don't know the differences between them
pm.sleep_mode=0 -> Power Collapse Suspend
pm.sleep_mode=1 -> Power Collapse (Provides best power savings)
pm.sleep_mode=2 -> Apps Sleep
pm.sleep_mode=3 -> Slow Clock and Wait for Interrupt
pm.sleep_mode=4 -> Wait for Interrupt
Values
0 - Power Collapse Suspend
1 - Power Collapse - __Provides best power savings__
2 - Apps Sleep
3 - Slow Clock and Wait for Interrupt (default)
4 - Wait for Interrupt
tailsthecat3 said:
are you able to elaborate on the settings of 1, 2 and 3? ive only seen this suggested to be set to 1. thanks.
edit: found this
http://www.androidonhtc.com/wiki/Boot_Options
and this info below elsewhere:
Sleep Modes: (pm.sleep_mode=) in the startup.txt
This is supposedly for topaz/rhodium that I found on the xda wiki:
* '4' will do "wait for interrupt", no change in arm11's clock or voltage
* '3' will do "wait for interrupt and ramp clock", the arm11's clock is lowered to 20MHz instead of 300-500, and voltage is lowered too.
* '2' will do "app sleep", arm11 is still on, but put into low power mode (registers are still saved)
* '1' and '0' will totally power off the arm11 (so we have to restore registers and things ourself), don't know the differences between them
pm.sleep_mode=0 -> Power Collapse Suspend
pm.sleep_mode=1 -> Power Collapse (Provides best power savings)
pm.sleep_mode=2 -> Apps Sleep
pm.sleep_mode=3 -> Slow Clock and Wait for Interrupt
pm.sleep_mode=4 -> Wait for Interrupt
Values
0 - Power Collapse Suspend
1 - Power Collapse - __Provides best power savings__
2 - Apps Sleep
3 - Slow Clock and Wait for Interrupt (default)
4 - Wait for Interrupt
Click to expand...
Click to collapse
Why did you say the same thing twice, and drag up a year old post in the process...? I answered your question in the battery thread.
arrrghhh said:
Why did you say the same thing twice, and drag up a year old post in the process...? I answered your question in the battery thread.
Click to expand...
Click to collapse
Shoosh. And what you typed in the battery thread, I would hardly call an 'answer'. Thanks anyway.
Sent from my Nexus S 4G via XDA Premium
tailsthecat3 said:
Shoosh. And what you typed in the battery thread, I would hardly call an 'answer'. Thanks anyway.
Click to expand...
Click to collapse
lol, it seems like an answer to me. Not sure what you were looking for - you posted the explanation of the different modes already... twice even. What else do you want...?
Related
Hi, I have discovered that Direct Push e-mail is causing the wizard to power on at certain intervals and for me at least was causing significant power drains under crossbow. Here are 2 fixes.
1. This is for those that use an exchange server and/or direct push email.
-Locking the device stops the wizard powering on and still allows use of direct push email.
2. Those that don't wish to lock their device and don't use direct push email.
-Change the following Registry values:
HKEY_CURRENT_USER\Software\Microsoft\ActiveSync\
HeartbeatIncrement DWORD: 0
InitialHeartbeat DWORD: 0
MinHeartbeat DWORD: 0
MaxHeartbeat DWORD: 0
Reset
Hopefully this will work for you guys it did for me, no power on all night.
EDIT: Sorry after longer testing No. 2 appears not to work however I still think it has something to do with Activesync and Direct Push E-mail. The settings reset themselves after soft reset.
It works!
Confirmed. Locking the device via the Today screen plug-in prevents the undesired power ups.
I am using a small program called Device Lock with the Suspend option. I set Button 4(Hold) to Device Lock. Sometimes it wakes up immediately after suspending, but I can press the power button and it stays off.
http://forum.xda-developers.com/showthread.php?t=261277
I discovered this yesterday also.
He means using the today screen plugin to lock it, not just having buttons locked except power in case you weren't aware of that.
No wonder I never had this problem. I use batterystatus to lock my screen all the time. Isn't the lock nice? Very convinent. My only hope is if there is anyway to unlock it with one hard button.
Oh. I was using the Lock in the control panel set to lock after 0 minutes of idle so when I pressed power it would power down and lock.
I'll have to find a better way to lock.
it didnt work....
Malik05 said:
it didnt work....
Click to expand...
Click to collapse
using the batterystatus, not the lock in the control panel.
i meant the regedits, it didnt fix the problem...i dont like to lock my phone when not in my pocket...
i hit the lock button on the today screen and i watch it turn on and off every minute... still... it didn't help ...
I wonder how did faria fix it in his ROM.
any update? wokring solution ?
Faria has the only known solution to this but is refusing to share that knowledge by looks of things, maybe so he can forces users to use his own cooked ROM or something...
the only working solution i have seen was the one rusigor suggested and that was taking the device password off. and im believer because it worked for me. so im sticking with that. Also i noticed that my battery is lasting like alot lot lot lot lot lot lot longer now. before i would go to bed with the phone at 80% battery and when i would wake up it would be like at 30. The last couple nights i would go to bed with it at 59 and woke up and it was at 55. I was shocked. so thats why im sticking with this method.
neonkoala said:
Faria has the only known solution to this but is refusing to share that knowledge by looks of things, maybe so he can forces users to use his own cooked ROM or something...
Click to expand...
Click to collapse
I hope it's just a case of him not knowing of this thread! Has anyone PM'd him?
I will if no one has yet.
Karl
Sorry meant to update this, fix has been around for a little while now.
Untick Turn off backlight for both battery and mains power and this will cure the problem however you may still have automatic power offs.
I don't use push, nor do I have an Exchange server configured. I also had a problem with automatic power-ups. I found that having the device configured to display the owner info screen when it is switched on caused it to power up on its own shortly after it was switched off.
Getting rid of the owner info display on power-up did the trick for me.
I'd love to know how those two things are connected.
I found a solution for me
I also think is more related with the screen light as I used the WM6 MB and i put the screen auto off after 30 sec, and it was waking up very frequently. I completly removed the screen light auto off and now my phone never wakes up alone (just when it should be =D).
Hope it helps!
Hi everyone,
I just switched from the Touch to the Kaiser and have a problem with the device not going into powersave mode. I am NOT talking about the backlight settings but the power settings that turns off the device after x min of inactivity. The device never turns off for some reason.
This was working fine on the Touch. Is this a common problem on the Kaiser ?
Thanks
pchronos said:
Hi everyone,
I just switched from the Touch to the Kaiser and have a problem with the device not going into powersave mode. I am NOT talking about the backlight settings but the power settings that turns off the device after x min of inactivity. The device never turns off for some reason.
This was working fine on the Touch. Is this a common problem on the Kaiser ?
Thanks
Click to expand...
Click to collapse
You don't mention what settings you have it set to. When you tap the battery icon (top bar) and then "advanced", are there time limits set?
If there are - untick the boxes and exit the screen "OK"
Then return to the screen and tick the boxes again and enter time limits exit with "OK"
Personally I always turn to standby manually. WM5/6 often seems to prefer this. WM5 in particular has a habit of not coming out of standby if it goes to standby by itself. The Kaiser seems MUCH more tolerant of this but I just got the habit of doing it manually.
Mike
My backlight settings are not set and my Power settings are as follows:
Turn off device if not used for "1 min" is SET for batt power and NOT SET for external power.
I will try unchecking everything and rechecking to see if that helps.
Thanks,
BTW, TouchFlo scrolling is horrible on the Kaiser compared to the Touch especially in the Internet browser. Surprising for a device with so much more memory and horsepower over the Touch...
i had a same problem with my kaiser... Try to hard reset u phone after hard reset you wont see any problem...
Thanks for the suggestions..
I did a hard reset and the problem remains. It is very strange because if I manually power of the phone it does wake up when I call comes in bit stays on after that.
During a call however the screen goes off !!!
I did the recommended reg hack to stop the screen from blacking out during a call but it still does it.
Has there been any updates to the original (HTC) firmware since release ?
Thanks again.
check this:
\HKLM\Drivers\BuiltIn\RIL\EnableFastDormantDisplayDuringCall
from "1" to "0" will leave the screen on long enough for voicemail use (probably falling back to the backlight/power settings)...
Click to expand...
Click to collapse
From this:
http://forum.xda-developers.com/showthread.php?t=330583&highlight=screen+off
I find this rather annoying, but don't know how to adjust it.
When making a call, sometimes you have to press through prompts like, 1, 2 , 3 etc. But after listening to the prompts, I find the phone screen to be OFF. I know that it's a power saving feature. However, it's quite annoying when to have press other keys to continue. I have to press the power button to get the screen to come back on.
Secondly, when connected to a call, the dialpad goes to the status screen by default. I have to change to keypad as well.
So here are my questions:
1) Anyway to change the amount of time before the screen blanks out while in a call?
2) Any other way to turn on the screen quickly without have to push the power button (which is difficult to push BTW)?
3) Any way to make the dialpad go to the numbers by default after a call is connected?
Thanks for any inputs!
Using WM6.1 ROM by Duty
anubus12 said:
I find this rather annoying, but don't know how to adjust it.
When making a call, sometimes you have to press through prompts like, 1, 2 , 3 etc. But after listening to the prompts, I find the phone screen to be OFF. I know that it's a power saving feature. However, it's quite annoying when to have press other keys to continue. I have to press the power button to get the screen to come back on.
Secondly, when connected to a call, the dialpad goes to the status screen by default. I have to change to keypad as well.
So here are my questions:
1) Anyway to change the amount of time before the screen blanks out while in a call?
2) Any other way to turn on the screen quickly without have to push the power button (which is difficult to push BTW)?
3) Any way to make the dialpad go to the numbers by default after a call is connected?
Thanks for any inputs!
Using WM6.1 ROM by Duty
Click to expand...
Click to collapse
KaiserTweak should solve some of your problems, if you have installed it.
http://forum.xda-developers.com/showthread.php?t=333898
tkalli said:
KaiserTweak should solve some of your problems, if you have installed it.
http://forum.xda-developers.com/showthread.php?t=333898
Click to expand...
Click to collapse
that utility doesn't change any of those settings.
anubus12 said:
that utility doesn't change any of those settings.
Click to expand...
Click to collapse
isnt that was the fast sleep and the sleep function in KT does??
Speaking of dialpads,
Do any of you guys having problems with inaccurate digit presses? I mean, I try to press 2, and 0 gets pressed instead, or other adjacent and non-adjacent numbers. Quite annoying really. Anyone experienced the same?
I bought a Touch Diamond recently.
But I can't resolve a problem with the fast dormont display during call function.
I tried to modify the setting in the following path:
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL\EnableFastDormantDisplayDuringCall
I change the DWORD Data from 1 to 0.
But after a soft reset, I still have the problem that screen turns off quickly during calls.
It bothers me when I need to use the keypad during a call
to enter ext. number or to follow a vocal operation.
Does any one have the solution here?
Thanks a lot.
Craig Shih
My problem is now solved. Any one who needs the solution can go to post#19 and post#29.
But it needs more tests and feedbacks because I don't know how it works for other roms.
No body in the diamond forum knows how to solve this problem.
Maybe this is a very very difficult problem to solve.
No one knows how to sovle it until now.
Hope a real master comes to help us.
diamond bugs
yes it's really sad to have a expensive mobile without a support even the htc don't have a solution what kind of support we had ??? lucky us we had a website like XDA developer to help us tnx to the dude who put up all the tweaks and update....try to flash the euro rom it will solve the prob.blank screen during call...
as soon as phone call is received, just press on joystick centre button shortly. Display will not go off then. Simple enough.
if before you'll make the call ypu'll take out the stylus, it won't go off, and it will automatically start a note.this setting is in phone option last tab...
remember: it goes to sleep the moment you hold it against your ear (or your hand or anything in the front).
if you set the registry right it will stay on as long as you don't hold anything against the front.
pskint said:
automatically start a note.this setting is in phone option last tab...
Click to expand...
Click to collapse
that's an additional and necessary side effect since he only needs the display to stay on so he can use the keypad without pressing extra buttons.
SecureGSM said:
as soon as phone call is received, just press on joystick centre button shortly. Display will not go off then. Simple enough.
Click to expand...
Click to collapse
Thank you for your suggestion.
I tried this method and then the call will be on hold immediately
until I press the central button again.
But it surely keep the screen on during calls though I have to press the central button twice.
pskint said:
if before you'll make the call ypu'll take out the stylus, it won't go off, and it will automatically start a note.this setting is in phone option last tab...
Click to expand...
Click to collapse
Thank you for your suggestion.
It's a good functionality for diamond users.
But sometimes I want to use the keypad during calls rather than to make a note with stylus.
For example when we call for some credit card toll free service,
we might have to key in ext. numbers or ID numbers or card numbers etc.
pietrucci said:
remember: it goes to sleep the moment you hold it against your ear (or your hand or anything in the front).
if you set the registry right it will stay on as long as you don't hold anything against the front.
Click to expand...
Click to collapse
Could you explain the registry for us?
Err... personal view..
If there is a solution.. it would be great.. but just in case, there isn't :
I have gotten used to it.
now if it is to enter extension numbers or whatever.. I just start off by pushing the center dial once. The key pad is there.. I get on with entering the ext. number or the Account numbers..
Same call - next time I have to enter other details, hit the center thing again.. and the key pad is there..
It's not that much of a hassle.
Of course a solution would be great, but even if there isn't, one does get used to it, in time.
why do you want it to stay on.
i noticed that when it stays on during a call, my ear is opening programs.
which i really do not want.
if you need to use the phone during a conversation just press the on button.
L o r d R a j said:
Err... personal view..
If there is a solution.. it would be great.. but just in case, there isn't :
I have gotten used to it.
now if it is to enter extension numbers or whatever.. I just start off by pushing the center dial once. The key pad is there.. I get on with entering the ext. number or the Account numbers..
Same call - next time I have to enter other details, hit the center thing again.. and the key pad is there..
It's not that much of a hassle.
Of course a solution would be great, but even if there isn't, one does get used to it, in time.
Click to expand...
Click to collapse
You are right, it 's not a big deal.
Maybe it's only my preference with mobile phone or somebody else's.
But if we can choose which way to go, that would be better.
i think there is a slotion please try
got this one now and it looks like problem solve for me
Originally Posted by minkol
I suggest this too:
HKCU\ControlPanel\Backlight\LightSensorPollingEnab le to 0 (default 1)
During call the light sensor can also switch the backlight off. This setting will that disable.
This registry setting will disable your screen from turning off when making a call:
HKLM\ControlPanel\Backlight\LightSensorPollingEnable set to 0
It disables the lightsensor so it doesn't react when you're putting the phone next to your ear.
It worked for me, so I hope it will work for you as well.
motin said:
got this one now and it looks like problem solve for me
Originally Posted by minkol
I suggest this too:
HKCU\ControlPanel\Backlight\LightSensorPollingEnab le to 0 (default 1)
During call the light sensor can also switch the backlight off. This setting will that disable.
Click to expand...
Click to collapse
Thank you.
I 'll try it right away and see how it works.
motin said:
got this one now and it looks like problem solve for me
Originally Posted by minkol
I suggest this too:
HKCU\ControlPanel\Backlight\LightSensorPollingEnab le to 0 (default 1)
During call the light sensor can also switch the backlight off. This setting will that disable.
Click to expand...
Click to collapse
Hello. That registry entry solved that problem, but still after a few seconds the light turns off, even if I set it to turn off after 5 minutes in the Power settings. Is there any registry "tweak" to increase the backlight duration during a phone call?
craig_shih said:
Could you explain the registry for us?
Click to expand...
Click to collapse
Yes I can. Look at this post, point 8: http://forum.xda-developers.com/showpost.php?p=2278799&postcount=1
This regkey is also mentioned a few times in this thread.
See also point 17 of that post.
Done.
This is what I did
HKLM\Drivers\BuiltIn\RIL\BatteryTimeoutInCall set to 0
HKLM\Drivers\BuiltIn\RIL\BatterySuspendTimeoutInCall to 0
HKLM\Drivers\BuiltIn\RIL\EnableFastDormantDisplayDuringCall to 0
HKCU\ControlPanel\Phone Sleep to 0
HKCU\ControlPanel\Backlight\LightSensorPollingEnable to 0
That done..
Restart the phone (I waited for a minute or so)
Backlight remains on now.
Then, just for the hell of it.. went back into the registry and set back the default values for:
lightsensorpollingenable
Phone sleep
Fast dormant
Checked again.. still works.
If one or two people could confirm that this works, we could finally put a SOLVED thing to this nonsense and get it over with.
I have a couple of anoying problems with the diamond. Its my first smart phone and there are som things I think the SonyEricsson handle better
First, whats up with the deal that Phone mode dissapears when you talk? When I´m calling some kind of support and need to press numbers thru the menu the phone locks after just about 5 secs and I have to go in to phone and keypad again, very anoying. Is their a way to keep in i phone mode to easy access to the keypad and ex speaker mode?
Second, the phone doesnt vibrate when it rings. When I choose vibrate-mode in the quick list it goes quite and vibrating, great for meetings. But I still want the phone to vibrate if I´m in a club or something
Third, Is there any way to shut down the function of the keypad appears automatically? When I go in the phone and wants to call I may have the number in the quick list but then I have to get the keypad away to see it. Isnt there a way to get it to appear only when I actually press the keypad button?
That was the first three questions, I suspects there will be plenty more after a while But I would appreciate any help I can get
claxx said:
I have a couple of anoying problems with the diamond. Its my first smart phone and there are som things I think the SonyEricsson handle better
Click to expand...
Click to collapse
those are not problems. those are you not reading diamond's manual or searching the forum. anyway:
First, whats up with the deal that Phone mode dissapears when you talk? When I´m calling some kind of support and need to press numbers thru the menu the phone locks after just about 5 secs and I have to go in to phone and keypad again, very anoying. Is their a way to keep in i phone mode to easy access to the keypad and ex speaker mode?
Click to expand...
Click to collapse
this is a feature not a bug and it is for you not to start any app with yr ear.
it can be override in many ways. one of them is using advance configuration 3.2. search! search!
Second, the phone doesnt vibrate when it rings. When I choose vibrate-mode in the quick list it goes quite and vibrating, great for meetings. But I still want the phone to vibrate if I´m in a club or something
Click to expand...
Click to collapse
try settings/phone/ring type/ vibrate and ring or vibrate the ring.
Third, Is there any way to shut down the function of the keypad appears automatically? When I go in the phone and wants to call I may have the number in the quick list but then I have to get the keypad away to see it. Isnt there a way to get it to appear only when I actually press the keypad button?
Click to expand...
Click to collapse
also can be changed. in phone mode go to menu/view/speed dial. this way when you call you'll get behind the phone pad yr speed dial. just push the little phone icon in the middle, lower screen and you'll have the speed dial only.
That was the first three questions, I suspects there will be plenty more after a while But I would appreciate any help I can get
Click to expand...
Click to collapse
i hope that next questions you are going to ask are going to be after you'll read the manual and a few threads here or you'll get ignored or worse...seriously flamed.
this is a feature not a bug and it is for you not to start any app with yr ear.
it can be override in many ways. one of them is using advance configuration 3.2. search! search!
I was told to put Phone sleep during call and fast sleep during call to Disable and Not Allowed in AC but the problems still remains.
also can be changed. in phone mode go to menu/view/speed dial. this way when you call you'll get behind the phone pad yr speed dial. just push the little phone icon in the middle, lower screen and you'll have the speed dial only.
I want to change the way the keypad acts. So its never appears automatically when the phone thinks I´m gonna use it, when I´m gonna write a SMS for example