Develop Bugs

Using a Blue Angel handsfree.

Here's the scenario.
I have my blueangel in my pocket.
It's off and the button lock is engaged so that it wont turn itself on accidentally. There's nothing I hate more than when it switches itself on in my pocket and goes berserk with random screen input.
My bluetooth headset is connected.
(I'm not even gonna start on how appaling the blue tooth on the blue angel is !!!!!, but that aside.....)
The phone rings and I press the answer buton on my headset to answer it.
The damn phone is now on in my pocket and the screen is active and receiving input during the call. Quite apart from anything else, there is a great big red END CALL button on the screen just waiting to be touched.
Assuming the call survives any problems, at the end of the call I have to get the phone out of my pocket to turn it off again because it wont turn itself off unless the activity timeout occurs which is not going to happen if the screen is being brused by anything in my pocket.
Is there some configuration or tool or utility or something that can detect when the phone is in handfree mode and disable screen input unless a certain button is pressed (like the green phone buton) and then switch the phone off again when the call is terminated ?

http://www.trancreative.com/nicestart.aspx
Have a look at this.
Im using it, and its the one that does the job best of them all out there, well in my opinion anyway

What about a case?
I had an alu one... no problem!

OK. I got NiceStart and had a play with it.
I think I have got it configured to work OK now.
Seems to solve most of the issues I raised.
I can't believe I had to get extra software to do that though.
I mean, it's not as if any of those probelms are either unforseeable or hard to solve.
It makes you wonder if the people who design these devices ever actually use them for real for any length of time.

The worst thing about it, is that i can buy a 1$ phone with a locking thats even better than this.
People have been screaming about this since the birth of WM, but M$ dont seem to be hearing this.
I have set Start->Settings->System->Button Lock-> Lock all ........power Button
Set a 4 digit password in NiceStart and mapped it to the 4 action buttons right under the screen.
Works great, but the screen will from time to time light up (M$ thing that it must do) to check the battery status. This cant be stopped in any way.

Call status/Light sensor issue?

As everyone may know already, while in a call when we put our ears to the ear piece the screen turns off, but when taking the phone away from the ear to look at the phone the light sensor detects it and lights up the screen.
My question is does everyone's phone go back to the TF3D homescreen when looking at the phone during a call, such as when you want to press number selections during voice prompts? Mine goes back to the TF3D homscreen everytime, and doesn't stay on the call status screen unless I physcially press the phone icon. I find this annoying especially when I need to input number selections. Anyone else experience this?

Nevermind, I found the solution and that is to turn off the password lock feature on the phone, and the phone stopped reverting back to the TF3D home screen during calls....must be a glitch...Blah...

Any way to keep screen off all the time until top power button pressed?

More than half the time I take my phone out of it's case in my pocket to check texts or call somebody, it's always on and eating battery. Alot of the time I have the phone in vibrate or silent because I can't have it going off most of the day, and whenever I get any kind of notification the screen comes on (text, alarm, call, ect.), and then the screen ends up staying on because it's constantly being bumped and never has the time to shut itself down.
Is there any way I can make the screen stay off at ALL times (except on an incoming call), and ONLY come on when I press the unlock/power button on the top of the phone?
I have a TMobile TP2 and I'm running the Nov. 19th, Photon Energy ROM. Upgrading to the Nov. 27th version when it's done downloading but I don't think that will fix the problem as I've changed ROMs before. Thanks to any help.

you will find that when in the case it should be off, on taking the phone out of the case (i assume the HTC one that came with the phone?)
the magnet in the case triggers the keyboard sensor which turns the screen on.
otherwise, you can change the display time out in power options under settings.
Cheers
Steve

That's interesting, I've heard about the case doing that but never thought about it. Would you recommend any cheap cases, or is there a specific magnet location I should be careful of? And do you know if there is a way to keep the screen off when I get a text message for example?

There is a way to fix this... it is to disable "Wake on Slide." I have done this and no more problems.
Here is a link to what to do:
http://forum.xda-developers.com/showpost.php?p=2945249&postcount=3
Hope it helps you, as it did me.

Thanks for the reply and I appreciate the help, but I don't really have a problem with the wake on keyboard slide, it seems that if the phone is in my pocket locked, and I get a text message, the screen comes on to notify me that I have a text message. Then, it's usually being bumped around in my pocket and since the touch screen is usable with any object, it will stay on because something will tap it in my pocket. The phone then heats up over time and drains battery. I want to find a way to keep the screen off at all times unless, I either receive a call, or push the power button. Thanks.

illusion of progress said:
Thanks for the reply and I appreciate the help, but I don't really have a problem with the wake on keyboard slide, it seems that if the phone is in my pocket locked, and I get a text message, the screen comes on to notify me that I have a text message. Then, it's usually being bumped around in my pocket and since the touch screen is usable with any object, it will stay on because something will tap it in my pocket. The phone then heats up over time and drains battery. I want to find a way to keep the screen off at all times unless, I either receive a call, or push the power button. Thanks.
Click to expand...
Click to collapse
Try:
go to HKLM\Drivers\BuiltIn\RIL
change DisableSMSWakeUpEvent to 1 (0 will wake up the device)
On my Rhodium, it does not wake up by default. I hear the notification, but my screen remains dark
Or try this cab file ... soft reset after install

Thanks for the .cab, I'm restarting now to see if it fixes the problem. Kind of random, but I might as well ask here before starting a new thread. I started using Mobile Shell instead of TF3D and so far I love it, but when setting a wallpaper, the wallpapers that I would normally use in TF3D, (480x800), it makes me select or crop out part of the photo to use as a background in Mobile Shell. I can't tell if it actually gets blurry (I would think so, because it's stretching the picture), but does anyone know why it wants me to only use a certain portion of the background instead of just setting the entire picture? Thanks,

More than likely, the version of Mobile Shell you have is either not designed for WVGA or there is a setting somewhere in there that allows you to change it and you haven't found it yet.
Am not a expert on mobile Shell, but according to their website, the latest version (3.5) does support WVGA.
Another option is to, if you have Adobe Photo shop or something similar, scale down the entire picture to the size it reccomends.
Otherwise, if you have a version earlier then 3.5, maybe you could upgrade and see if it makes any difference.

Since updating to 4.0.4 I cannot dial pass 10-digits

Sorry if this has already been posted, I did a search and couldn't find anything.
Anyway, this is a new issue for me as I didn't have this problem before getting my OTA of 4.0.4 last week. When I was on 4.0.2, I didn't have this issue - but I do now that I am on 4.0.4.
My phone will let me dial the area code + 7 digits, but if I am required to input numbers after the call is connected (like when calling your credit card company) the dial-pad screen and phone shuts off as soon as I click the 1st number.
I then have to turn on the phone, swipe to unlock, go back into the phone dialer and do this for each number input.
Anyone else having this issue? Any ideas/and or suggestions how to fix, or at least a workaround until Google gets it fixed?
Not sure if this matters, but I am stock GSM/T-Mobile.
Thank you.

Bmerz said:
Sorry if this has already been posted, I did a search and couldn't find anything.
Anyway, this is a new issue for me as I didn't have this problem before getting my OTA of 4.0.4 last week. When I was on 4.0.2, I didn't have this issue - but I do now that I am on 4.0.4.
My phone will let me dial the area code + 7 digits, but if I am required to input numbers after the call is connected (like when calling your credit card company) the dial-pad screen and phone shuts off as soon as I click the 1st number.
I then have to turn on the phone, swipe to unlock, go back into the phone dialer and do this for each number input.
Anyone else having this issue? Any ideas/and or suggestions how to fix, or at least a workaround until Google gets it fixed?
Not sure if this matters, but I am stock GSM/T-Mobile.
Thank you.
Click to expand...
Click to collapse
This happens to me, however I only have to pull my hand away from the phone to bring it back to the dial pad.
I am guessing you have your phone set to lock "immediately" when the screen goes black (I have mine set to five seconds, so this does not happen to me)
What is happening (in my case at least) is an overly sensitive proximity sensor. It catches your hand, thinking you're putting the phone to your face, and darkens the screen. I have to be careful where I place my hand when I use the dialer after I am on a call (say, checking voicemail and entering password)
If your phone is set to lock immediately, try setting it to five seconds, and see if that helps.
This also happened on my GS2..

ingenious247 said:
This happens to me, however I only have to pull my hand away from the phone to bring it back to the dial pad.
I am guessing you have your phone set to lock "immediately" when the screen goes black (I have mine set to five seconds, so this does not happen to me)
What is happening (in my case at least) is an overly sensitive proximity sensor. It catches your hand, thinking you're putting the phone to your face, and darkens the screen. I have to be careful where I place my hand when I use the dialer after I am on a call (say, checking voicemail and entering password)
If your phone is set to lock immediately, try setting it to five seconds, and see if that helps.
This also happened on my GS2..
Click to expand...
Click to collapse
Thank you, I will look into my settings and change it. But as for the other thing, one has to have their hand on/near the dialer in order to input more numbers. Perhaps I can angle the phone and my hand in a way that the sensor doesn't see my hand over the dial pad. (What a PITA! lol)
Nonetheless, thank you for chiming in!

Question Swiping Down For Notifications When In A Call

Anyone notice it turns the screen off? I think the proximity sensor thinks your face is going against the screen and the display turns off but it's really annoying when your trying to access things from the notifications.

Hello my friend!
I have the same phone as you, and I'm sorry but I'm not having any problems the likes of which you describe.
May I suggest the following?
1. Restart phone in safe mode (now this will vary based on your Carrier: on my unlocked Google issued phone, I press Power and Vol UP at same time; Verizon is Power and Vol down, others may be different: Then on the menu that pops up, press and hold Reset and it'll ask you if you want to restart in safe mode, hit yes, then restart)(SafeMode will display on screen). Then call someone and try to recreate the "black screen, can't pull down notification window". If you can pull it down (as I suspect you will be able) then it's an app problem you've got (not a hardware or system issue)
2. Try going to Settings: Apps: Special App Access (way at the bottom of the screen) and then try finding either Display Over Apps applications or Picture-in-Picture apps or other groups that may interfere with your Phone app. I bet you'll find that there's an app or utility you've installed that is conflicting with your screen.
Let me/us know how it goes!

Batfink33 said:
Anyone notice it turns the screen off? I think the proximity sensor thinks your face is going against the screen and the display turns off but it's really annoying when your trying to access things from the notifications.
Click to expand...
Click to collapse
Yeah, every phone does this if you have your finger over the sensor. Find a better spot to drag down.