Related
Hi.
I am solving the issues of CommMgrPro with Raphael. The most important were.
1) CMP didnt change the band correctly (2G <-> Auto <-> 3G)
2) CMP didnt set correctly the speaker volume.
Any help to see if those issues are gone in this version will be wellcome with free licenses
Version V2.2(2008-09-12)
1) There are towers on each country with same cell id. So now the primary key for Cell Mode will be CellID + LAC. CMP will convert your database so make a backup before and will fill the lac information each time it finds a cell with lac equals 0
2) Compatibility with HTC Touch Diamond and HTC Touch Pro (Fixed Band manager, speaker manager, GPS manager and some GUI changes).
3) New option to repair the database.
4) New page for connections option (In connections/menu/options)
5) Option to disable/enable connections on roaming
6) Option to CMP startup delayed on page Options 3.
7) Option to Show/Hide the main window after start CMP.
8) Clicking on the higher part of the battery bar opens the battery page
9) Clicking on the lower part of the battery bar opens the battery page
10) Hide button is raplaced by calendar button.
11) New Today tab. This dialog lets you see the next events that will happen in the place, including calendar events, "Always on" schedules and other events (time limits, etc)
I´m on it!
I´m curious to see how much battery economy this will bring when switching off 3G? I´ll post my findings. What do you mean by speaker volume (in call?).
thanks
Belive me, it really save your battery if you swith off 3G mode. My battery lifetime increase from 8 to 26h.
Regards
B.
danielherrero said:
Hi.
I am solving the issues of CommMgrPro with Raphael. The most important were.
1) CMP didnt change the band correctly (2G <-> Auto <-> 3G)
2) CMP didnt set correctly the speaker volume.
Any help to see if those issues are gone in this version will be wellcome with free licenses
Click to expand...
Click to collapse
Hi Daniel,
I'm expecting my Touch Pro on Friday, I'll report as soon as I can.
Manni
So far so good on the band...
I´ve tried all day switching between 2G and 3G and it seem to work seamlessly, which comes as a huge plus for me to save on battery when 3G is not needed.
One thing I don´t get.. the HIDE button. CMP is hidden but how to unhide it without having to press the icon to launch it again.
Update: Yes it asks for the PIN but naturally it has to since it´s reestablishing a connection to the Celular provider.
Regarding band switching - it works sometimes because sometimes CM just reset himself (generate errors)
Another thing is that if I'm switching from 3g to 2g is asking me for PIN
When I'm doing it mannualy (GSM to WCMDA switching) system never ask for it.
B.
Hi
In the options page you can set the pin code. In this way CMP will enter automatically the pin when switches the band....
fllysurfer said:
I´ve tried all day switching between 2G and 3G and it seem to work seamlessly, which comes as a huge plus for me to save on battery when 3G is not needed.
One thing I don´t get.. the HIDE button. CMP is hidden but how to unhide it without having to press the icon to launch it again.
Update: Yes it asks for the PIN but naturally it has to since it´s reestablishing a connection to the Celular provider.
Click to expand...
Click to collapse
Well, I usually assign a hw button to CommMgrPro. Raphael has few buttons so I assigned long press phone button to CMP. CMP installs a Today plugin and a tray icon to manupulate CMP directly from today screen or bring it to front but you cannot see them with touchflo 3d. Sorry for not saying it before, you can set pic code in options dialog so cmp will enter pin code automatically....
Dani
fllysurfer said:
I´m curious to see how much battery economy this will bring when switching off 3G? I´ll post my findings. What do you mean by speaker volume (in call?).
thanks
Click to expand...
Click to collapse
No, system volume. You can control ring tone and ring volume as a action associated to enter/exit in a profile/place (using cell ID)
It was short and 5min test - I'll check everything once again tomorrow and let you know.
Regards
B.
For those who want to check the 3g effect on the battery live. There is a tab on CMP that shows graphically the battery evolution in different scales of time and if you touch two points it tells you the speed, for example, 6 units per hour. Ok, let your device during some hours in 3g and check the drain speed. Do the same test using 2g. As you will see battery live lasts double (or more) using 2g...
Great Commmanager Replacement
Testing for about 15 mins now and so far no problems.
Although the ON/OFF switching for phone with the "no time limit" function is not very responsive. I had to click another icon before i could switch it on again.
Great work on the battery graphs very useful
I will report tomorrow after some intesive usage.
WatskeBart said:
Testing for about 15 mins now and so far no problems.
Although the ON/OFF switching for phone with the "no time limit" function is not very responsive. I had to click another icon before i could switch it on again.
Great work on the battery graphs very useful
I will report tomorrow after some intesive usage.
Click to expand...
Click to collapse
hehe I see to tested it deeply. Turn on phone with time limit was disabled one month ago because the people requested in this way. Anyway I will remove the time limit dialog to avoid confussion....
CommManager replacement is only a little feature. The main one is let CMP (CommMgrPro) to set the state of the device (phone, band, BT, WIFI, speaker, connections, beam, messaging, brightness, ring tone, today theme, call forward, open and close programs, etc) depending on your current location by cell id (home, work, cinema, etc) and weekday/hour. In this way the state of the device will be different on your work&monday&10:00 than on home&sunday&13:00, isnt it?
Dani
Hi
I ve uploaded a new beta (b6). It warns if you want to change the band but you didnt set the pin code on options and a few more things. If you look at the screenshots on first post you will see there is a screen dedicated to the current (different than the battery page)with two lines, one for instant current drain and other for average. In this way is easy to check the current (in mA) needed for your device under different circunstances (wifi, band, gps, etc) and the temperature of the battery (important for the people like me having problems with device not charging if running gps/tomtom in a warm day).
ps: Talking about gps and temperature, finally I bought and A/C mount system so the battery's temperature is always low and no problem charging....
Hi Daniel,
So I received my Touch Pro today, and the first program I installed was CMP
Couple of issues:
- I installed without deactivating Touch Flo 3D, so I got an error message when the program first launched (I guess it couldn't launch the today plugin).
- If I deactivate the Touch Flo 3D, the icons in the plugin are stil QVGA. Same thing if you change the icons of the location (which makes it difficult to select the right one, as they are not for the software where the seem to be on the screen, if you see what I mean)
- Same thing for the fonts on mostpages / menus. Most of them are very small (hard coded for QVGA I guess) which makes them much harder to reads than on a QVGA device. The location line, or the function icons at the bottom of the main screen, are normal size. Everything else is small (for example, "there is a newer version").
- When Touch Flo 3D is activated, there is no directaccess to CMP (lower right globe icon), but I guess that's normal.
Otherwise, everything seems to work fine. I guess most of this is VGA related rather than Touch Pro related, but here you go, I'm coming from CMP on a Tytn II...
Edit: forgot to specify that the speaker setting and the band switching seems to work fine.
Hi
Thank you very much for your comments and help. Fortunately most of those issues are related with the sizzo vga skin so can be changed modifying the file skin.xml. Modify and enhance the vga skizzo skin is one of the pending things to do. Please follow reporting anything you see
Hi Daniel,
Done a bit more testing today, and I found out that there are two connections in CMP (T-mobile PicMessage and T-Mobile Internet), while I have only one connection setup by default (T-mobile).
They are both enabled, none of them is always on, and only the PicMessage is connected.
Is this normal? I'm quite sure I had only one on my Vario III. Which one do I need to get my push email? If I want to get my exchange email as it arrives, do I need to switch one of these to always on? (by the way, my exchange server is setup properly, and it works thanks to MrVanx...).
Hi Manni
CMP shows all the connectios,even hidden connection. Probably in the connections wizard your operator set up the second connection for other pourposes like mms,wap,etc.
If you re using direct push(like me) you dont need to mark any connection as "always on" because activesync will keep the connection alive....
Dani
danielherrero said:
Hi Manni
CMP shows all the connectios,even hidden connection. Probably in the connections wizard your operator set up the second connection for other pourposes like mms,wap,etc.
If you re using direct push(like me) you dont need to mark any connection as "always on" because activesync will keep the connection alive....
Dani
Click to expand...
Click to collapse
Thanks a lot for the clarification!
I've tested both b5 and b6 versions on orygial HTC rom.
Discovered that :
1. Cannot clear history of battery usage in CURRENT tab - on BATTERY tab this feature works fine
2. Cannot verify database integristy - error message appear
3. Switching between G2 and G3 works smooth - tested VERY intensivly for last 3-4 days.
Small hints
1. there are two graphs on main screen - on the left is graph for battery and on the right for available field. Is nice of you if you can just create the link between battery graph on main screen and CURRENT/BATTERY tab on settings. This is common problem that Touch Pro battery has very short lifetime and I'm very interested in checking which action is draining my battery more than normal - graph is perfect place for this.
5. Last suggestion for booting TP and application starting process. Everytime when I'm performing soft reset or just starting device, I'm waiting to put my PIN as fast as possible to get my TP online, but THEN CommManPro LOGO is showing and grrrrrrrrrrrrrr I'm must wait next 5sek to tap my PIN.
You know, this is not a problem if you are using your phone for private, and there is no more than 3-4 calls from you sister/girlfriend/mother/lover by day, but I'm using my TP for buisness (and testing everything in the same time) manner so time when I'm available is critical - one missed call (because of 5sek delay) and couple of bucks less in my pocket
If it possible for you to just pospone CommManPro to starting just after TF3D it's nice!
Regards
B.
Hi, I have a few questions regarding Raphael.
1a - I can't get the gps work. So far it worked only once. I use TomTom and usually it is searching for signal and sometimes even for gps device. Therefor I want to try different radio firmware. I had a look at wiki and there are radios with different version number. I'm not sure if those version numbers indicate exactly which radio fw is for my version of radio or if i'm free to try and flesh any Faphael radio.
1b - I have read something about 3g not working in usa or something along the lines. I have europan Raph and live in europe. Can flashing any radio fw interfere somehow with 3g?
2 - Is there a navigation software (TomTom, iGo...) which tends to work better with Raphael?
3 - How can I remove specific sms messages from main manila screen? Or they are by default all the inbox messages?
4 - Is there anyting like underclocking of the cpu to save battery life? Or does this happen automatically? I was thinking that maybe it could save some battery life if each time I turn off or lock my Raphael the cpu would underclok.
5 - SPB shell will replace manila?
6 - What happens when battery reaches 0? Will the device turn off and go to some suspend mode for a few hours or i loose everything? If it will go to suspend mode, how long can it survive like that?
7 - Is there some tool in the default device or some external software which would alow me to create profiles with different sound/ring volumes, vibrations and so on? Currently i have to mess with ring volume if i only want to turn of phone ringing but still have other sounds or I haven't find a way how to have ringing and vibration turned on at the same time.
profiles
8 - If I turn off Raph, is there a way how to turn it on with pad button? It's a bit unconvinient inconvenient to pick up the device from desk and reach for the turn on button at the top, dpad would be much better.
9 - I'm not sure if it's because of threaded messages, but for some reason some or all (not sure) messages I send are in the inbox folder. Is that ok? Can I change this so they are in sent messages?
Many thanks.
Please help with at least point 1
Bumping up the thread the last time
1a - I can't get the gps work. So far it worked only once. I use TomTom and usually it is searching for signal and sometimes even for gps device. Therefor I want to try different radio firmware. I had a look at wiki and there are radios with different version number. I'm not sure if those version numbers indicate exactly which radio fw is for my version of radio or if i'm free to try and flesh any Faphael radio.
Lots of people have GPS issues and there are tons of threads regarding it. Use the search function to figure it out.
1b - I have read something about 3g not working in usa or something along the lines. I have europan Raph and live in europe. Can flashing any radio fw interfere somehow with 3g?
3G works on At&t Branded Raph in US.
2 - Is there a navigation software (TomTom, iGo...) which tends to work better with Raphael?
3 - How can I remove specific sms messages from main manila screen? Or they are by default all the inbox messages?
Not sure what you mean.
4 - Is there anyting like underclocking of the cpu to save battery life? Or does this happen automatically? I was thinking that maybe it could save some battery life if each time I turn off or lock my Raphael the cpu would underclok.
If you are turning the power all the way down, you will not receive calls or be able to quickly use the phone but you should get around 7 days of battery. If you have the device on sleep/suspend with all radios on then you should get about 30 hours. However incoming calls and sms or emails will turn it back on and you will increase drain. Average day to day hours for me is 8 to 12.
5 - SPB shell will replace manila?
SPB Mobile Shell will not replace manilla. You would still be able to use both, if manilla is touchflo3d. I don't know what manilla is.
6 - What happens when battery reaches 0? Will the device turn off and go to some suspend mode for a few hours or i loose everything? If it will go to suspend mode, how long can it survive like that?
Device turns off and you don't lose anything that isn't saved. Sounds like the last device you owned like this was a Palm from 1992 DONT LET THE BATTERY DIE, OH NOES! haha Im just having fnu with you!
7 - Is there some tool in the default device or some external software which would alow me to create profiles with different sound/ring volumes, vibrations and so on? Currently i have to mess with ring volume if i only want to turn of phone ringing but still have other sounds or I haven't find a way how to have ringing and vibration turned on at the same time.
profiles
I thought SPB allos this but do a search there is tons of stuff regarding this.
8 - If I turn off Raph, is there a way how to turn it on with pad button? It's a bit unconvinient inconvenient to pick up the device from desk and reach for the turn on button at the top, dpad would be much better.
I have not searched for this yet but I want the answer too.
9 - I'm not sure if it's because of threaded messages, but for some reason some or all (not sure) messages I send are in the inbox folder. Is that ok? Can I change this so they are in sent messages?
Well in winmo6.1 they group messages, I notice in touchflo3d you only see incoming and not any outbound.
Hi,
I recently bought a HTC Touch HD, and I think that the "shutdown-screen-when-you-answer-a-call" function of phones like Diamonds, Touch Pro and HD is the dumbest way to prevent accidental presses on the touch screen.
Our devices have a light sensor, that could be used to switch off the screen if the phone is near the ear (like the phone using an "i" word ) and keep it on when you answer with loudspeaker for example.
The "problem" with this function is that when you're already in a "no-light" environment, the screen lock function doesn't work.
To resolve this issue, I think we could use the G-Sensor. Indeed, if the place has no light, then, the phone cannot detect the proximity of a ear. But when you put the phone next to the ear, you hold it a the vertical...
To make it short, the app should do :
Do nothing in normal use.
When a call arrives :
- it monitors the ambient light
If there's light :
- when you answer the call, if there's light then no more (you stick the phone next to the ear), it switches off the screen and continue to monitor.
- while in call, if there's light again (you want to see some info on the screen for example), it switches on the screen and continue to monitor.
- and so on until you end the call
If there's no light :
- when you answer the call, but let it at the horizontal (you let it on the desk for example), it does nothing
- if you take the phone on the vertical position (you stick the phone next to the ear), it switches the screen off.
- if the phone, during a call, goes from vertical to horizontal of horizontal to vertical, the screen is switches on/of
- and so on until you end the call
Obviously, you could replace the "switch on/off screen" with "lock/unlock screen".
What do you think about ?
UPDATE :
After playing a bit with the HD, it appears that HTC DOES use the light sensor for turning the screen off during a call.
Let's do a test :
In a place with plenty light :
- put your mobile with the face up
- call a number (always face up) : the screen will not be switched off until the light sensor detects a loss of luminosity or a timeout set in the registry.
So, my conclusion is that HTC already use the light sensor to switch the screen off during a call, but they do it in an absurd way :
- they poll the sensor just to shut down the screen, not to switch it on.
- once the screen has been switched off, they do not longer poll at all.
Do you think it could be a way to "hack" their system to do what we want to do ?
no one has an opinion on this idea ? if there's nobody that want / have the time to develop a soft, I understand, but at least please, give me just your opinion
I agree with your idea for such an application. I must admit that I am very used to just pushing the power button when I answer a call (from Polaris use) to ensure I am not going into other programmes as I rub the phone against my ear. On the other hand I am trying to get used to the Touch HD's modern automatic method but I can't help not feeling relaxed that it has worked and keep trying to look at the screen in the corner of my eye to see if it did go off or not.
If it does not come now I am sure there will be such an app very soon just as you describe especially as all the latest models now have it.
i'd use the half of it that doesn't require the G-sensor as i don't have a diamond or HD...
but i'm certainly sick and tired of my ear operating my touch screen while i'm speaking.
I've written a prototype to do exactly what you are talking about although the one crucial part I am missing is the lock code. Every example or suggestion for locking the screen is very hacky and never feels like a good approach. If anyone has a good solution for locking the screen (especially in managed code) I would be happy to complete what I have started and release it with source so it could be improved upon.
So far, the best locking utility I have seen is PocketShield although I'm not sure what approach was used for locking in that case. It almost feels like a form that captures all windows events but I'm not sure exactly.
fireweed said:
I've written a prototype to do exactly what you are talking about although the one crucial part I am missing is the lock code. Every example or suggestion for locking the screen is very hacky and never feels like a good approach. If anyone has a good solution for locking the screen (especially in managed code) I would be happy to complete what I have started and release it with source so it could be improved upon.
So far, the best locking utility I have seen is PocketShield although I'm not sure what approach was used for locking in that case. It almost feels like a form that captures all windows events but I'm not sure exactly.
Click to expand...
Click to collapse
Maybe the simpliest way to "protect" the screen is to switch it off. I suppose it must be some API to do that ?
Concerning the "locking", I think the simpliest way is to put on focus an empty window (transparent if it can be ).
I'm really happy to know that you're working on an app like that
lpaso said:
Hi,
I recently bought a HTC Touch HD, and I think that the "shutdown-screen-when-you-answer-a-call" function of phones like Diamonds, Touch Pro and HD is the dumbest way to prevent accidental presses on the touch screen.
Our devices have a light sensor, that could be used to switch off the screen if the phone is near the ear (like the phone using an "i" word ) and keep it on when you answer with loudspeaker for example.
The "problem" with this function is that when you're already in a "no-light" environment, the screen lock function doesn't work.
To resolve this issue, I think we could use the G-Sensor. Indeed, if the place has no light, then, the phone cannot detect the proximity of a ear. But when you put the phone next to the ear, you hold it a the vertical...
To make it short, the app should do :
Do nothing in normal use.
When a call arrives :
- it monitors the ambient light
If there's light :
- when you answer the call, if there's light then no more (you stick the phone next to the ear), it switches off the screen and continue to monitor.
- while in call, if there's light again (you want to see some info on the screen for example), it switches on the screen and continue to monitor.
- and so on until you end the call
If there's no light :
- when you answer the call, but let it at the horizontal (you let it on the desk for example), it does nothing
- if you take the phone on the vertical position (you stick the phone next to the ear), it switches the screen off.
- if the phone, during a call, goes from vertical to horizontal of horizontal to vertical, the screen is switches on/of
- and so on until you end the call
Indeed, you could replace the "switch on/off screen" with "lock/unlock screen".
What do you think about ?
I searched the forum for an existing app that could do this, but I didn't find anything.
If there's already an app that do this stuff, I'm truely sorry for this post.
Click to expand...
Click to collapse
I'm looking for this.. If you find a solution send me a PM, I will do the same
Thanks!
We need this app, how does the iphone acheive this?
I think the 'easiest' way to make this app would be to keep the phone doing what it does currently (put the phone on standby when answering a call) then have the light sensor take the phone out of standby when it receives light, (taking it away from your ear)?
Obviously if its dark then we would have to use the power butten as we currently do now or have the Gsensor do it with a twisting motion (vertical to horizontal).
If anyone has an idea how to program this i'm willing to help in any way, the current systems seems so crude on such tech devices!
DB
lpaso said:
Hi,
I searched the forum for an existing app that could do this, but I didn't find anything.
Click to expand...
Click to collapse
There a program, that can help you. Not full, but it can switch off screen, using g-sensor. However its using not vertical aligment of the phone. There are using changing orientation of the phone to decide when phone near the ear.
http://forum.xda-developers.com/showpost.php?p=2622590&postcount=45
I have always wondered why our WM phones don't do what the iphone does...
For the SE Xperia X1, the light sensor is right near the earpiece (along with the little front facing camera), so it would go to virtually 100% darkness when near the ear. I would presume unless you are using the phone also in 100% darkness (which should be pretty rare I would guess) then it would work like the iphone.
I have also been quite annoyed by the fact that after a phonecall, sometimes I found i'm in a note taking program or weather program or something else. It just seems dumb, considering our phone HAVE these lightsensors?!
I think it's a fantastic idea to solve a VERY FRUSTRATING PROBLEM
lpaso said:
no one has an opinion on this idea ? if there's nobody that want / have the time to develop a soft, I understand, but at least please, give me just your opinion
Click to expand...
Click to collapse
I would rank myself this way:
Not a newbie who's just gotten a touchscreen phone and is now discovering the quirks when holding screen to ear,
and not a developer,
but a power-user. I have installed all sorts of XDA-developed features/enhancements for my phone.
But now I have 4 years experience -- starting with the T-Mobile MDA, and its successor, the T-Mobile WING. And despite all of the advancements expected in that time, STILL, I inadvertently end a call, or put it on hold accidentally, ALL THE TIME. Between that and trying to retrieve the phone from my pocket just to answer the damn ringing phone, I would say I have, on the average, a 20% success rate -- and 80% of the time the call is disrupted. And at least once a day my ohone, in my pocket, even when using s2u2, manages to REDIAL my latest conversation, so mcuh so that all my friends say "why don;t you get rid of that phone. It does all these whiz bang things but still can't reliably manage a basic phone call.
My most recent experiment was to call someone, then when they answered, press the s2U2 key to lock the phone screen. Only I came to find out from A_C that this is no good: S2u2 does not have recognition that you're ending the call, thus, since it's in lock-mode, the "END CALL" or Hang-Up hard key does not work.
So by all means, I would even pay for an app that once and for all handles the baseline problems of simply making a phone call. Thanks for making this request.
fireweed, have you contacted A_C, author of s2u2 ?
There may just be perfect synergy between the two of you. His "best of breed" screen-lock app is widely used -- and other developers, like supbro, for example, author of iDialer, have collaborated on small code-bits from A_C to solve some integration problems.
If for any reason you are unfamiliar with A_C, go to his website: www.ac-s2.com -- where his apps are explained, and all link back to XDA.
He's even managed to make the screen lock work, yet, have it selectively overridden when you insert headphone jack -- such that his s2p (slide to play) app opens and allows you to switch music tracks etc while otherwise the screen and buttons are all fully locked...
fireweed said:
I've written a prototype to do exactly what you are talking about although the one crucial part I am missing is the lock code. Every example or suggestion for locking the screen is very hacky and never feels like a good approach. If anyone has a good solution for locking the screen (especially in managed code) I would be happy to complete what I have started and release it with source so it could be improved upon.
So far, the best locking utility I have seen is PocketShield although I'm not sure what approach was used for locking in that case. It almost feels like a form that captures all windows events but I'm not sure exactly.
Click to expand...
Click to collapse
Hi,
After playing a bit with the HD, it appears that HTC DOES use the light sensor for turning the screen off during a call.
Let's do a test :
In a place with plenty light :
- put your mobile with the face up
- call a number (always face up) : the screen will not be switched off until the light sensor detects a loss of luminosity or the timeout set in the registry expires.
So, my conclusion is that HTC already use the light sensor to switch the screen off during a call, but they do it in an absurd way :
- they poll the sensor just to shut down the screen, not to switch it on.
- once the screen has been switched off, they do not longer poll at all.
Do you think it could be a way to "hack" their system to do what we want to do ?
I think HTC does not only switch off the display but goes to standby (phone works independent if you didn't know yet). Your idea is a lot different in terms of programming.
I don't know if it goes to standby : when the screen is switched off during a call, a press on any button switch it on again. In the registry, the key controlling the timeout before the screen is shut off is named "LightSensorToScreenOff" so I think it is just switching off the screen...
lpaso said:
I don't know if it goes to standby : when the screen is switched off during a call, a press on any button switch it on again. In the registry, the key controlling the timeout before the screen is shut off is named "LightSensorToScreenOff" so I think it is just switching off the screen...
Click to expand...
Click to collapse
Well if thats the case, its HALF of what the iphone does... it turns off the screen based on the light sensor going dark suddenly (next to ear) but then fails to turn the screen back on after you move the phone away from your ear...
Anyone know how to enable this?
Interested in having this feature too. Isn't it possible to have the G-Sensor determine when the phone is vertical and shut the screen and then when it is lying flat to turn the screen back on again. Believe that the Iphone does it this way, not with the light sensor.
Hmm... I never had my ear 'navigating' my phone during in-call before....
I never allowed the screen to touch my face anyway, and the speaker is facing the ear canal, when I receive or make calls...
But i do understand that s2u2 can do what you guys might need, it locks the screen during in call.
Hennyb said:
Interested in having this feature too. Isn't it possible to have the G-Sensor determine when the phone is vertical and shut the screen and then when it is lying flat to turn the screen back on again. Believe that the Iphone does it this way, not with the light sensor.
Click to expand...
Click to collapse
I think the Iphone has something called proximity sensor, which senses the distance from the ear to the phone, hence when the phone rest on the outer ear, the phone screen shut off.
Or am I wrong?
Section9 said:
I think the Iphone has something called proximity sensor, which senses the distance from the ear to the phone, hence when the phone rest on the outer ear, the phone screen shut off.
Or am I wrong?
Click to expand...
Click to collapse
No, you're right. It uses an iR sensor to know if there's something near the phone.
Hi all,
I tried searching but cannot find anything on this, so as my first post, here goes...
I have a Touch Diamond with official ROM (WM6.1). I want to get over the known "issue" that with the device set to pin lock after 0 minute timeout, it still locks automatically after 1 minute of idle time.
Of course, I found an answer on this forum, see, for example http://forum.xda-developers.com/showthread.php?t=291868: in the registry, set AEFrequencyType to 2 (instead of 1), which works as hoped as far as the device is concerned... it no longer auto-locks after any amount of time, but locks instead whenever it goes into standby.
The issue is this: Activesync no longer requires the pin to connect to the device and without pin can read ALL files from its memory, even if the phone is locked at the time. Setting AEFrequencyType back to 1 forces Activesync to require the pin even if it is not locked when it is plugged in to the computer. Does anyone know a way to force Activesync to require the pin... of course, I am looking for a setting on the device, not the PC, as I want to make it hard for anyone who might steal the phone (or if I lose it!) to read the data on the device.
In case anyone is wondering, I also found another workaround. Having set the pin timeout to some large time, like 30 minutes, I can then use a pin locking program, Zenyee's 'Pin Lock.exe', and create a wakeup event notification with Dotfred's Task Manager (seems very useful app for free!). This works, until I run FlexMail, which seems to intercept these notifications and prevent it from locking!! So, I have to override a soft key on the home screen to run the pin lock, then hit the power button to put the device into standby. Not too bad, but there must be a better way...!
Thanks in advance,
Martin
Just a quick follow up for anyone who may be interested. FlexMail DOES NOT intercept the wakeup events... however, because it causes a little processing to be done, it seems it can delay the device from sleeping for a while (a minute or two) whenever a full synchronisation is performed. So, the wakeup event, whilst normally quick to activate, can sometimes take a minute before becoming effective.
However, I now have a workable solution for me. Just as I said above, I set my Pin Lock timeout to something large, like 30 minutes. However, instead of relying solely on wakeup events, I have now installed Gyrator 2 (http://forum.xda-developers.com/showthread.php?t=427805) which is an excellent application for many reasons... I particularly like being able to identify the window class/title using the stylus-in event to identify the in-focus window! More importantly, for this issue, it has the option to both Pin Lock and Suspend the device whenever a certain criteria is met. For me, this is when it is held face down for a second. So, now I just do this instead of hitting the power button and I'm guaranteed to have the device Pin Locked on next wakeup. ActiveSync also requires the Pin as AEFrequencyType is the default value of 1. A perfectly workable solution.
All the best,
Martin
I strongly suggest you take this towards the Diamond section as knowledge about specific problems in specific devices are usually conversed over at that specific section.. more than here.
Thanks, but I think this is WM6/WM6.1 specific, not Diamond specific. The problem with AEFrequencyType set to 1 giving a timeout even with zero minutes is known and seems to be device independent. I just found that setting it to 2 to fix this timeout issue, as many people do, seems to prevent ActiveSync from requiring the PIN as well! Not a good result.
That said, my workaround solution is probably Diamond specific, sorry! Perhaps I should post in the original thread that I found out about the AEFrequencyType registry tweak?
All the best,
Martin
Credits:
Foremost, let us all acknowledge Koushik for his brilliant "Sensors" library upon which most if not all non-HTC apps that use the G-Sensor, Light-Sensor, and Navi-Sensor are built, simply ingenious. Moreover, I would like to recognize No2chem for the NeuLed2 library which is an equally exquisite peace of code that allows access to the Diamond/Pro Leds. Without those two guys, accessing these advance interfaces on the diamond/pro would be inapproachable at best.
Reason: HTC gave these phones lots of sensors, lets give them.."Sense".
......... EXTRA-Sense ...........
* Hopefully an innovaton, though mostly an integration of RANDOM but needful features...
Features:
1. Courtesy Profiles:
- Set Volume Profiles to activate on Face-Down & Face-UP events. Choose from: None, Silent, Normal, and Vibrate. You can also choose to suspend the Phone when its facing down.
2. Notifications-Sense:
- IF there is/are any outstanding notification(s), the device will vibrate whenever you move it - at customizable intervals: Missed Call(s), Voice Mail, and SMS.
3. Stylus-Sense:- When the Stylus is in/out: Will play sound + Blink the Back button's light.
- When the Stylus is out and the device is moved: Device will vibrate faintly + blink the Back button's light to REMIND you that the Stylus has not been placed back in. This goes on UNTIL the Stylus is placed where it should be.
* Uses "in.wav" & "out.wav" files in the \XSense\ Dir; you can use whatever wave files for this. OR, use the UI to select whichever wave files you want!
4. General Settings:
- Polling Interval: From 200 to 3000 Miliseconds. This determines the rate at which the G-Sensor is polled. Lower values give higher response times and fluid operation at the cost of battery life & CPU utilization.
- Flash Navi Lights: Will blink button lights to notify you of Profile changes and Stylus In/Out.
- Vibrate on Events: Will induce very subtle vibrations to notify you of Notifications and Profile changes.
- Suspend when UP-Side-Down: ???
- Light Navi Button When Suspended: Will do just that when the Light Sensor senses Dim or Dark conditions. This is an independent setting that turns ON the Navi button's light at suspend time, and OFF at Resume time (this is Event Driven, so no polling is involved). This feature really helps if, like me, you want to see where the damn thing is in the dark - before you launch it against the floor.
5. Installs to "\Program Files\XSense", and Creates 2 shortcuts:
"Start Menu\Programs\XSense" and "Startup\XSenseSvc".
Program Settings are saved to the Registry at "HKCU\Software\XSense\".
Use of System Resources:
1. Diskspace: 162 KB RAM footprint: 374-535 KB Battery: NOT observed.
2. CPU Usage: %0.29 Average. Spikes for 2 seconds to %2.7 - %8.5.
3. Battery Impact: Neligeable if at all!
* Indicated CPU usage occurs ONLY when there is an EVENT (posture changed, stylus in/out Sounds playing,
etc)
- Vibration: The way I like it is in waves of 200 miliseconds length! I generally hate vibrations, so if you want it at 201 ms. you're welcome to make your own program and exercise your personal taste.
- This prgram Registers Event Handlers for: "G-Sensor", "Incoming Call", "Phone Call in Progress", "Stylus in/out", and Power Manager events. DO NOT move it to Internal Storage, you have been warned.
Requirements:
.NET 3.5 + HTC device with GSensor & Light Sensor.
Compatibility:
Specifically designed for Diamond & Raphael, but will work fine on HD/Rhodium/Topaz/HD2 etc...
Bugs/Limitations:
Knock yourself out...
Release Notes:
- This is the LAST revision/release/app I make; programming too much work
- Download & Install the CAB
- Run the XSense from your Start Menu\Programs, customize to taste, and enjoy!
Change Log:
- Brand New UI: VERY "finger friendly" this should be especially useful if you have a WVGA Device
i.e. HD/Rhodium/Topaz/HD2 etc...
- Revised entire code for existing & potential bugs, and Performance
tweaked to death.
- Removed various functions (auto speakerphone, car-kit options, etc...). Use "Touch InCall Screen Tweak" for these,
its handles Phone/Speaker brilliantly!
- Shortcut added to Startup for automatic launch after reboot.
- Shortcut with a nice icon added to Start Menu (Credit to VetVito).
- General Tab:
- Navi Button will only light up if the device is in a dark place, i.e. You will
always see where your phone is (before you trash it against the wall).
- Stylus Tab:
- UI elements to select & set sounds for Stylus-in/out events.
Disclaimer:
This program is provided strictly "as is". It is intended only as a proof-of-concept. Although fully functional, it must NOT be considered for daily use. This software is very likely to compromise the integrity of your data as well as invariabley cause your device to malfunction in any way, shape, or form. Therefore, the developer shall be absolved of all responsibility towards testers and/or their computers & devices. While using this software you agree to be solely liable for all and any damages you do to yourself, your device, or any damn thing you possess and care for!
Download XSense 1.2 - Final:
http://forum.xda-developers.com/attachment.php?attachmentid=265847&d=1263112521
This initiative sounds great But I would love one more feature. The ability to lock and unlock the device by using G-sensor. In particular, a gesture consisting of tilting the device donwards (with the screen facing the ground) and then upwards again (the screen facing the sky)
Look promising, but ... Leo dont have a stylus
Caramel said:
Look promising, but ... Leo dont have a stylus
Click to expand...
Click to collapse
I'm glad you noticed!!!
I'm just too lazy to make this LEO-specific, and this way I don't have to make 2 programs (one for LEO and one for everything else)....
Cheers
jgal said:
This initiative sounds great But I would love one more feature. The ability to lock and unlock the device by using G-sensor. In particular, a gesture consisting of tilting the device donwards (with the screen facing the ground) and then upwards again (the screen facing the sky)
Click to expand...
Click to collapse
Max Manila does this. Well, it locks when you aim the top of the phone at the floor.
Doesn't seem to work well with S2U2. For example, if your HD2 is set to lock with S2U2, then u put if face down, phone is not put in silent mode until u press a button to light up the screen when the screen is face down. So the first call to come in will still ring. But subsequent calls won't because when the first call comes in, the screen lights up and phone is set to silent.
The reverse is also true. If I revert to face up from a silent-ed face down position, and I do not press any button to light up the screen, it remains in silent mode until an action that lights up the screen.
Anyway to work around this? Or is it sorely the problem of S2U2?
kenkiller said:
Doesn't seem to work well with S2U2. For example, if your HD2 is set to lock with S2U2, then u put if face down, phone is not put in silent mode until u press a button to light up the screen when the screen is face down. So the first call to come in will still ring. But subsequent calls won't because when the first call comes in, the screen lights up and phone is set to silent.
The reverse is also true. If I revert to face up from a silent-ed face down position, and I do not press any button to light up the screen, it remains in silent mode until an action that lights up the screen.
Anyway to work around this? Or is it sorely the problem of S2U2?
Click to expand...
Click to collapse
This is not due to interference wth S2U2, it is in fact a programmed behaviour - I made it this way. The reason for this was conserving power; the device wakes up to incomming calls on a priority basis -think bus mastering- and the only way around it is to give the G-Sensor polling a higher priority, which means continuous polling + disallow the device to suspend power (the same effect as Shake2Wake). This costs you lots of battery juice, and according to Microsoft, a non-snapdragon device won't last the day in this operation mode!
Nonetheless, suggestions are welcomed...
Cheers
shirreer said:
This is not due to interference wth S2U2, it is in fact a programmed behaviour - I made it this way. The reason for this was conserving power; the device wakes up to incomming calls on a priority basis -think bus mastering- and the only way around it is to give the G-Sensor polling a higher priority, which means continuous polling + disallow the device to suspend power (the same effect as Shake2Wake). This costs you lots of battery juice, and according to Microsoft, a non-snapdragon device won't last the day in this operation mode!
Nonetheless, suggestions are welcomed...
Cheers
Click to expand...
Click to collapse
Hmmm...so the first call that comes in when phone is face down will not be silenced, and the first call that comes in when phone is face up after being moved from a face down orientation will always be silent?
The first scenario is still ok, can still silence it with a key press. But the 2nd scenario makes it possible to miss a call even when phone is face up. That does sound like it defeats the purpose of the app.
I'm not sure of the technical side of solving this, but missing every first call after flipping face up just sounds strange.
Finally, the closest thing to what i've been looking for. I have a HTC Fuze. With this app, I can only get the center LED (around the D-pad) to be on solid only in the dark, which is a nice feature, but i'd like to have all the LEDs at the bottom of the device (Home, Back, Send and End) to be on in dim or dark conditions, WHILE the phone is in use or suspended.
Can it be added, or how would I go about setting it up myself?
Thanks
~Des