Notices


Reply
Thread Tools
Posts: 368 | Thanked: 442 times | Joined on Jan 2006 @ Italy
#31
Originally Posted by vi_ View Post
so how many times a second does this thimg poll the proximity sensor?
I did not read the code, but I think you and the OP are not understandig each other because the thing should not poll the sensor. The sensor is polled via HW and a dbus signal is emitted. Then there are interfaces exposed to react to those signal. More on your original thread which I found looking about that. BTW congrats for this app idea though I won't use it becuase while sleeping I am sleepanalized, I think it's really useful for who could need it
 
Posts: 539 | Thanked: 165 times | Joined on Feb 2010 @ Berlin, Germany
#32
Originally Posted by jurop88 View Post
BTW congrats for this app idea though I won't use it becuase while sleeping I am sleepanalized, I think it's really useful for who could need it
Nice new word: sleepanalized
I'm using both of them, SleepAnalyser and ProximityClock. As my phone is laying beside my pillow it's not covered all night and I can easily open the clock by skimming over the device. Very useful!
 
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#33
Originally Posted by jurop88 View Post
I did not read the code, but I think you and the OP are not understandig each other because the thing should not poll the sensor. The sensor is polled via HW and a dbus signal is emitted. Then there are interfaces exposed to react to those signal. More on your original thread which I found looking about that. BTW congrats for this app idea though I won't use it becuase while sleeping I am sleepanalized, I think it's really useful for who could need it
Orly? THen why must I install the proximityd package to get the proximity sensor to emit a signal on dbus? Further more proximityd works by polling the sensor (by a user configerable sample rate). This leads me to believe that the proximity sensor is not connected to a hardware interrupt and is 'read' whenever it's state is needed to be known.

Unless you are using some custom magical way for reading the sensor you are polling it.

So, how many times a second are you polling the sensor OR are you just using the proximityd defaults?

Are you even using proximityd at all?

What is this thing programmed in?

Has anyone run powertop while this thing is running?
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 
Posts: 136 | Thanked: 115 times | Joined on Jul 2010 @ Greece
#34
nice app that I did not know I wanted!
Could it be made so that when the device is locked and the app wakes it up to show the time, afterwards it locks itself again?
Also perhaps another way to exit in addition to timeout could be if you tap the screen.

I tried powertop
first result is with proximityclock inactive and second when it is active
Total wakeups 4009, 133.6/s | IRQ 3184, 106.1/s | Timers 825, 27.5/s
HW wakeups 191, 6.4/s | Real gp_timers expired 141, 4.7/s

Total wakeups 7863, 262.1/s | IRQ 5767, 192.2/s | Timers 2096, 69.9/s
HW wakeups 52, 1.7/s | Real gp_timers expired 36, 1.2/s

with top, cpu usage when active between 0,3 and 0,9.
I can not really interpret them, but they seem good numbers.

Last edited by evan; 2011-03-21 at 14:38. Reason: powertop
 
Posts: 318 | Thanked: 735 times | Joined on Oct 2009
#35
@vi_ : I didn't use proximityd or dbus. I simply read the state (through the /sys file) every 100ms only when the daemon is active.

@evan: thanks. Your request sounds good, maybe I'll implement it
I've also tested the behavior with top, and I think that it use not so much in term of resources.


Best Regards,
Daniele.
 
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#36
Any chance you could be a bro and post your code?
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 
Posts: 318 | Thanked: 735 times | Joined on Oct 2009
#37
Originally Posted by vi_ View Post
Any chance you could be a bro and post your code?
Sure, (as always) the code is uploaded into the garage's svn : https://garage.maemo.org/plugins/scm...proximityclock
 
Posts: 87 | Thanked: 25 times | Joined on Mar 2010 @ Canada
#38
Originally Posted by b0unc3 View Post
Hello,

I've just upload a new version (0.3) to extras-testing.
With this new version you can change the color of the clock's background and the numbers. You can also set the clock timeout (in seconds).
All these settings are accessible through a home widget's setting button.
Test&Vote
Tank you.



Best Regards,
Daniele Maio.
Great app!! Thanks a lot!

Works fine, except that the colours don't seem to work: I can change them but the end-result is always white numbers on black background.

An other remark is when I activate it by moving in front of the proximity sensor when my screen is on stdby, I am seeing (for a split-second) my home screen before seeing the time. This may be due to a slow unit...?

Edit: I also discovered that if you receive a phone call while Proximityclock is ON, the screen remains sensitive! So you have to be careful not to press your ear too hard against the screen...
__________________
Jan

Last edited by bioman; 2011-03-22 at 06:37. Reason: found out an other bug
 
Posts: 112 | Thanked: 105 times | Joined on Mar 2010 @ Montpellier, FRANCE
#39
Hi all

Nice app i realy like it.

2 Features:
Could you add, date and list of future alarm with time reamining.

Thx for your work.
 
Posts: 185 | Thanked: 49 times | Joined on Apr 2010 @ The Netherlands
#40
Is it possible to make the app only work when the phone is locked? Also when my phone is locked it unlocked it’s self when using proximityclock.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 21:36.