I've been playing with adctaskman to see where all the memory is going. I noticed that cprog.exe (phone app) stays resident after the phone is used and gradually creeps up to occupy 3-5mb. The program doesn't load until the phone is first used from a reset, but won't quit after that. I tried to close the process with no success. I then killed the process. The phone still starts at the press of the phone button and is able to receive calls and killing cprog doesn't seem to have any other downside. Why does this process stay resident? Am I missing some bad effect from shutting it down? If there isn't a big downside from shutting it down, is there a way to get it to close other than killing the process so that I can reclaim that 3-5mb?
I think when it's not running, it takes an extra 3-5 seconds before the phone will acknowledge a call it has to load, so by having it resident, the phone will ring faster and you are less likely to miss a call. Tho this is just a guess, but I do know the first call I get, the backlight lights up and it may be 3-5 seconds before the call notification screen opens up.
So yes, you can close it, but you will get less time once the phone starts ringing before they get kicked to voice mail.
BTC
Related
Hi all
My Wizard has been acting very strangely for the last 24 hours. Without any obvious trigger evet, it has started doing the followig things:
- GSM notification light has started blinking amber without any associated problem or warning. Normally this means GSM disabled, but I can still place and receive calls fine.
- Refusal to sync with desktop. When I plug it in, both the computer and phone make studdery 'hardware connected' noises but nothing else. Whatever I try, I cannot coaxe them to talk.
- Worst of all, at seemingly random times, in perhaps 1-minute intervals, the phone vibrates briefly and makes the notification noise, as if an appointment was coming up. But there are no appointments, all system alarms have been turned off and I can't for the life of me tell what's triggering it - there's nothing in the task manager list, so it seems to be a system fault. This is making it an extremely annoying device to be around.
I tried a soft reset, nothing. I'm reluctant to do a hard reset beacuse I have some data which I mustn't lose (but I can't back it up). The only thing that I can think of is an application I installed a while back SMS Threader, which was pretty parasitic. I removed it, but apparently the uninstallation wasn't clean. The buzzes and noises sound a bit like what the phone would do when I received a message while I had SMS Threader installed.
Any ideas?
Thanks...
Every few phone calls on my 8525, I notice that when I am done, and hit the end button (on screen, soft key or red phone button) the phone will not hang up...even after the other person has already hung up. I can keep hitting the buttons, but nothing registers. Everything else on the phone still works just fine, I can exit the dial pad, and get into any other menu, and the phone icon is still showing by the signal strength indicating a call is still in progress.
Anyone else experience this at all? Any suggestions?
I sometimes get the same thing, but I have no solution aside from the little "in-and-out" routine with the stylus and the reset hole.
-Humbert
Same problem here as well. Sometimes the call will go for 20 - 30 seconds after the other person has hung up.
Maybe it is cingulars way of getting us to use more minutes!!
same for me too...I figured out that my Cingular 8525 only does this when I am out of a 3g area. Every time that my phone displays the G icon and I'm on the phone it won't hang up for another 30 sec. after my conversation has ended...it is annoying...
My THD keeps running out of battery power and it has taken me untill now to work out why.
If the THD is OFF and the phone rings it turns on, but when the call is finished IT STAYS ON and because I keep in my shirt top pocket every time I move it restarts the "turn off timeout" and I use up battery power.
Surely the phone should work this way:
THD ON when phone rings, it stays ON after the call is finished.
THD OFF when phone rings, it turns OFF when call is finished.
Is it possible for it to do that or can anyone sugest a solution.
Sam
samcory said:
My THD keeps running out of battery power and it has taken me untill now to work out why.
If the THD is OFF and the phone rings it turns on, but when the call is finished IT STAYS ON and because I keep in my shirt top pocket every time I move it restarts the "turn off timeout" and I use up battery power.
Surely the phone should work this way:
THD ON when phone rings, it stays ON after the call is finished.
THD OFF when phone rings, it turns OFF when call is finished.
Is it possible for it to do that or can anyone sugest a solution.
Sam
Click to expand...
Click to collapse
I think if you keep it locked in your pocket you can still answer calls although it is in a locked state. When the call is finished it will go back to being locked automatically so you don't need to worry about activating anything on the phone in your pocket and it will go to sleep according to the settings you have made.
You can enable the AutoLock function so that you won't accidently touch it (although it got some bug with backlight).
Or you can use S2U2......(but it drain powers too).
stm2008 said:
You can enable the AutoLock function so that you won't accidently touch it (although it got some bug with backlight).
Or you can use S2U2......(but it drain powers too).
Click to expand...
Click to collapse
I like the sensor lock, much nicer to make a rotational pattern to lock/unlock the phone. Makes the slide to unlock look outdated.
batery problems
I do not think you understood what I was saying.
Auto turn off is TURNED ON
Keylock IS TURNED ON
When an incoming call "wakes up" my sleeping unit and I have a conversation on the phone, when I finished the call and press "end call button" the phone does not go back to sleep. It should shut down after the preset time of, in my case, 30 seconds. But because the phone is in my top shirt pocket every movement of my arms or body causes the screen to be touched and the 30 second closedown time starts all over again.
What I have to do at the moment whenever I finish a call is to press first the "end call button" and then the "turn off" button. What I need is one button that will end the call and shut the phone down as well.
I guess post title says it all..
Whenever I start a phone call, the screen goes off...it is very annoying.
Any way to stop that behavior ?
I have searched this forums with no luck.
I am running Modaco's 2.3 ROM on an unbranded hero.
I have tried using Powermanager tools to define a 2min timeout in the "screen off during call" feature but with no luck.
thanks for the help!
Cheers,
-Eric
There is an app called shake awake which wakes up the screen during a call when you move it away from your face.
http://www.cyrket.com/package/com.maplekeycompany.apps.shake
Thanks. i'll give a try but the bad reviews are scaring me.
Is there a setting anywhere for that screen turning off while on call ?
i didn't liked "shake awake" the calls got dropped when the phone "shaked" sometimes i had to call the same person 3 or 4 times because the call ended. first i thought it was my phone but the problems started after installing shake awake. after i removed it my phone worked again
Keepscreen does the trick. Works absolutly great. The full version is able to keep the screen on with every application. Very handy when reading mail, browsing etc. You must set youre screenout delay in settings from the phone to 30sec.
http://nl.androlib.com/r.aspx?r=keepscreen
I'd like an app that actually does kill the screen as soon as the call button is pressed. Sometimes the Hero is too slow to turn off the screen and you hang up the call with your cheek.
Thats annoying.
Anyone else has this or is it just me, when i receive a text message my phone freezes for 4-5 seconds and after that back to normal.
if im doing some thing i notice it hangs for a second but nowhere near that long.
I Agree
I noticed this issue more today than any other. I recently hard reset my phone, and thought that I needed to reapply some hotfixes, so I did. On the way home I will see if my music keeps cutting out during bandswitching and receipt of text messages.
Why just WinMo priotise so much resource to receive a poxy text?!? It doesnt need 1Ghz of power for such a basic communications protocol!
Mine freezes after clicking send. It freezes for like 10s and sometimes the message I send doesn't show under the message I received.