Active Topics
-
Phone Camera Competition April 2021: "Funny & Foolish" (17)
to General by robthebold - 5 hrs, 3 mins ago -
Maemo-Leste pre-alpha announcement (512)
to Maemo 7 / Leste by nonsuch - 7 hrs, 25 mins ago -
The Intel RealSense Smartphone prototype (0)
to Competitors by n950 - 9 hrs, 59 mins ago -
Maemo Leste Playground (57)
to Maemo 7 / Leste by clort - 1 day, 7 hrs ago -
A Palm OS thread ... and a thank you to the community (23)
to Alternatives by bradvesp - 2 days, 6 hrs ago -
What's the best Handheld gnu/linux machine for 20XX? (77)
to Competitors by biketool - 2 days, 19 hrs ago -
Unofficial Storage for camera phone competition... (61)
to General by Maemish - 4 days, 22 hrs ago -
SailfishOS on Sony Z3 Compact Tablet (180)
to SailfishOS by ogustbiller - 5 days, 10 hrs ago -
Debian "squeeze" Image easy installer (24)
to Alternatives by sicelo - 6 days, 12 hrs ago -
A good modular laptop for Linux in 2021 (8)
to Community by ThomasAH - 6 days, 13 hrs ago - more...
|
2010-08-30
, 04:35
|
|
Posts: 268 |
Thanked: 304 times |
Joined on Oct 2009
@ Orlando, USA
|
#52
|
lircd is a CPU hog.
while running:
When not running:
Unfortunately, Raemote causes a significant amount of battery drain because lircd is running even when the widget is removed from the desktop.
In QtIrreco, lircd is shutdown when the application is closed. See Bug 10040. This bug should really be against Raemote. It would be great if Raemote could be optimized to save battery.
Great app by the way!
while running:
Code:
kia-N900:/home/user# ./powertop
Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 20660us
C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 1.2% | | 600 MHz | 0.0% |
C1 | 0.0% | 0.2ms | 550 MHz | 0.0% |
C2 | 1.5% | 11.6ms | 500 MHz | 2.0% |
C3 | 20.1% | 194.7ms | 250 MHz | 98.0% |
C4 | 77.1% | 701.3ms |
IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
56 | 300 | INTC | i2c_omap
37 | 111 | INTC | gp
11 | 77 | INTC | prcm
86 | 60 | INTC | mmc1
57 | 34 | INTC | i2c_omap
12 | 15 | INTC | DMA
67 | 12 | INTC | ssi_p1_mpu_irq0
71 | 12 | INTC | ssi_gdd
21 | 2 | INTC | SGX
311 | 2 | GPIO | ssi_p1_cawake_gpio
PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 47 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
2718 | 30 | lircd | schedule_hrtimeout_range (hrtimer_wakeup)
1 | 17D| preinit | cpufreq_governor_dbs (delayed_work_timer_fn)
0 | 10 | <kernel core> | hrtimer_start (tick_sched_timer)
39 | 7 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
777 | 6 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
2315 | 3 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
1495 | 2 | shermans | schedule_hrtimeout_range (hrtimer_wakeup)
1495 | 2 | shermans | do_nanosleep (hrtimer_wakeup)
39 | 2 | mmcqd | cfq_completed_request (cfq_idle_slice_timer)
765 | 2 | dsme | do_nanosleep (hrtimer_wakeup)
765 | 2 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
1731 | 2 | piecewise | schedule_hrtimeout_range (hrtimer_wakeup)
1 | 2 | <kernel core> | queue_delayed_work (delayed_work_timer_fn)
777 | 2 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
777 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup)
777 | 2 | bme_RX-51 | schedule_timeout (process_timeout)
1153 | 1 | iphbd | schedule_hrtimeout_range (hrtimer_wakeup)
29 | 1 | mv | setup_wb_timer (wb_timer_fn)
13 | 1 | pdflush | blk_plug_device (blk_unplug_timeout)
1772 | 1 | browserd | futex_wait (hrtimer_wakeup)
796 | 1 | dbus-daemon | queue_delayed_work (delayed_work_timer_fn)
813 | 1 | mce | schedule_hrtimeout_range (hrtimer_wakeup)
1245 | 1 | wlancond | schedule_timeout (process_timeout)
1245 | 1 | wlancond | queue_delayed_work (delayed_work_timer_fn)
1245 | 1 | wlancond | ieee80211_ioctl_siwpower (ieee80211_dynamic_ps_timer)
1547 | 1 | browserd | futex_wait (hrtimer_wakeup)
2826 | 1 | powertop | do_nanosleep (hrtimer_wakeup)
Power domain activity breakdown
Domain | % of time spent in states
--------+---------+---------+---------+---------+----------
usbhost |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
sgx |OFF: 99%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
per |OFF: 96%|RET: 2%|INA: 0%| ON: 1%| now:(ON)
dss |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
cam |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
core |OFF: 77%|RET: 19%|INA: 0%| ON: 3%| now:(ON)
neon |OFF: 77%|RET: 20%|INA: 1%| ON: 1%| now:(ON)
mpu |OFF: 77%|RET: 20%|INA: 1%| ON: 1%| now:(ON)
iva2 |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
Clock activity breakdown at end of period
Domain | Active clocks
--------+---------------+---------------+------------------
core | SDRC | HSOTGUSB_IDLE | OMAPCTRL
| MAILBOXES |
wkup | GPT1 | 32KSYNC | GPIO1
| WDT1 |
ckgen | CORE | PERI | 96M
| 48M | 12M | 54M
| EMU_CORE |
per | GPIO2 | GPIO3 | GPIO4
| GPIO5 | GPIO6 |
Total wakeups 776, 25.9/s | IRQ 625, 20.8/s | Timers 151, 5.0/s
HW wakeups 77, 2.6/s | Real gp_timers expired 111, 3.7/s
Nokia-N900:/home/user#
When not running:
Code:
Nokia-N900:/home/user# ./powertop
Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 93231us
C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 1.5% | | 600 MHz | 0.0% |
C1 | 0.0% | 0.3ms | 550 MHz | 0.0% |
C2 | 1.2% | 8.9ms | 500 MHz | 0.3% |
C3 | 7.3% | 88.0ms | 250 MHz | 99.7% |
C4 | 90.0% | 1933.1ms |
IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
56 | 151 | INTC | i2c_omap
37 | 106 | INTC | gp
11 | 54 | INTC | prcm
57 | 34 | INTC | i2c_omap
86 | 30 | INTC | mmc1
67 | 15 | INTC | ssi_p1_mpu_irq0
71 | 12 | INTC | ssi_gdd
12 | 11 | INTC | DMA
21 | 9 | INTC | SGX
311 | 6 | GPIO | ssi_p1_cawake_gpio
PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 54 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
2315 | 18 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
0 | 14 | <kernel core> | hrtimer_start (tick_sched_timer)
1 | 14D| preinit | cpufreq_governor_dbs (delayed_work_timer_fn)
39 | 8 | mmcqd | schedule_timeout (process_timeout)
777 | 7 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
868 | 3 | sgx_perf | queue_delayed_work (delayed_work_timer_fn)
39 | 3 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
899 | 2 | Xorg | hrtimer_start (it_real_fn)
777 | 2 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
777 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup)
777 | 2 | bme_RX-51 | schedule_timeout (process_timeout)
765 | 2 | dsme | do_nanosleep (hrtimer_wakeup)
765 | 2 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
1 | 2D| <kernel core> | queue_delayed_work (delayed_work_timer_fn)
1547 | 2 | browserd | futex_wait (hrtimer_wakeup)
899 | 1 | Xorg | queue_delayed_work (delayed_work_timer_fn)
1460 | 1 | livewp | schedule_hrtimeout_range (hrtimer_wakeup)
1458 | 1 | livewp | schedule_hrtimeout_range (hrtimer_wakeup)
1731 | 1 | piecewise | schedule_hrtimeout_range (hrtimer_wakeup)
1495 | 1 | shermans | schedule_hrtimeout_range (hrtimer_wakeup)
1495 | 1 | shermans | do_nanosleep (hrtimer_wakeup)
813 | 1 | mce | schedule_hrtimeout_range (hrtimer_wakeup)
39 | 1 | mmcqd | schedule_timeout (process_timeout)
1 | 1D| <kernel core> | rt_secret_timer_init (rt_secret_rebuild)
1 | 1 | <kernel core> | inet_initpeers (peer_check_expire)
2545 | 1 | powertop | do_nanosleep (hrtimer_wakeup)
Power domain activity breakdown
Domain | % of time spent in states
--------+---------+---------+---------+---------+----------
usbhost |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
sgx |OFF: 97%|RET: 0%|INA: 0%| ON: 2%| now:(OFF)
per |OFF: 97%|RET: 1%|INA: 0%| ON: 1%| now:(ON)
dss |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
cam |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
core |OFF: 89%|RET: 5%|INA: 0%| ON: 4%| now:(ON)
neon |OFF: 89%|RET: 7%|INA: 1%| ON: 1%| now:(ON)
mpu |OFF: 89%|RET: 7%|INA: 1%| ON: 1%| now:(ON)
iva2 |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
Clock activity breakdown at end of period
Domain | Active clocks
--------+---------------+---------------+------------------
core | SDRC | HSOTGUSB_IDLE | OMAPCTRL
| MAILBOXES |
wkup | GPT1 | 32KSYNC | GPIO1
| WDT1 |
ckgen | CORE | PERI | 96M
| 48M | 12M | 54M
| EMU_CORE |
per | GPIO2 | GPIO3 | GPIO4
| GPIO5 | GPIO6 |
Total wakeups 576, 19.2/s | IRQ 428, 14.3/s | Timers 148, 4.9/s
HW wakeups 54, 1.8/s | Real gp_timers expired 106, 3.5/s
In QtIrreco, lircd is shutdown when the application is closed. See Bug 10040. This bug should really be against Raemote. It would be great if Raemote could be optimized to save battery.
Great app by the way!
| The Following User Says Thank You to archebyte For This Useful Post: | ||
 |
|
2010-08-31
, 11:59
|
|
Posts: 1,390 |
Thanked: 4,262 times |
Joined on Sep 2007
@ Vienna, Austria
|
#53
|
Originally Posted by archebyte
So, this is really a bug in lircd and not in RaeMote then? Closing down lircd could have side-effects on other applications (imagine removing the widget while some other application that utilizes the IR port is running).
Unfortunately, Raemote causes a significant amount of battery drain because lircd is running even when the widget is removed from the desktop.
I wonder why lircd keeps waking up and doing something if there are no requests from other applications?
|
|
2010-08-31
, 12:58
|
|
Posts: 268 |
Thanked: 304 times |
Joined on Oct 2009
@ Orlando, USA
|
#54
|
Originally Posted by thp
There is definitely an issue with lircd. But it isn't much noticable in Qtirreco because its not running constantly.
So, this is really a bug in lircd and not in RaeMote then? Closing down lircd could have side-effects on other applications (imagine removing the widget while some other application that utilizes the IR port is running).
I wonder why lircd keeps waking up and doing something if there are no requests from other applications?
To address the side-effects of killing lircd, is it possible to run a second instance of lircd on a different port that can be safely killed when the wodget is removed? Just a thought.
|
|
2010-09-02
, 18:39
|
|
Posts: 1,390 |
Thanked: 4,262 times |
Joined on Sep 2007
@ Vienna, Austria
|
#55
|
Originally Posted by archebyte
I thought the IR device could only be opened by one process, and that that was the whole point of lircd in the first place? Although I don't know, and haven't looked into it that much.
There is definitely an issue with lircd. But it isn't much noticable in Qtirreco because its not running constantly.
To address the side-effects of killing lircd, is it possible to run a second instance of lircd on a different port that can be safely killed when the wodget is removed? Just a thought.
If RaeMote was an app (and not a widget), this would be much easier - it could just display a prompt if the user wants to keep the IR daemon running with the option to "always kill lircd on exit".
|
|
2011-05-18
, 19:21
|
|
Posts: 96 |
Thanked: 12 times |
Joined on Jun 2008
|
#56
|
I have installed Raemote and the widget is showing up, my n900 is also sending out an IR signal(tested using the webcam), but my macbook will not respond.
I have the newest macbook model.
What can I do to fix the problem?
I have the newest macbook model.
What can I do to fix the problem?
__________________
n810.
n900
n810.
n900
|
|
2011-05-19
, 11:54
|
|
Posts: 1,390 |
Thanked: 4,262 times |
Joined on Sep 2007
@ Vienna, Austria
|
#57
|
Originally Posted by jackdoor
Make sure that your MacBook is not paired with any other remote. The app sends out codes only for unpaired remotes.
I have installed Raemote and the widget is showing up, my n900 is also sending out an IR signal(tested using the webcam), but my macbook will not respond.
I have the newest macbook model.
What can I do to fix the problem?
|
|
2011-05-20
, 10:03
|
|
Posts: 96 |
Thanked: 12 times |
Joined on Jun 2008
|
#58
|
The problem is that Apple stopped making the Macbooks with IR receivers, only the Macbook pros or older Airs have IR.
__________________
n810.
n900
n810.
n900
|
|
2011-05-28
, 22:51
|
|
Posts: 26 |
Thanked: 7 times |
Joined on Mar 2011
|
#59
|
Hey,
I'm trying to get this to work with my iMac. The Real Apple Remote works fine. It's not paired or disabled (as verified under the security tab in the System Preferences). It's as if the iMac doesn't catch the signal or something...
I'm using the "Otterbox" case. I don't really see where the infrared light would even be emitted. Is it coming from the little LED on the front? I've tried with the shutter open but I highly doubt that's the source.
Let me know if you have any ideas! My iMac was purchased at the end of 2010 and it's running the latest Snow Leapord.
Thanks
I'm trying to get this to work with my iMac. The Real Apple Remote works fine. It's not paired or disabled (as verified under the security tab in the System Preferences). It's as if the iMac doesn't catch the signal or something...
I'm using the "Otterbox" case. I don't really see where the infrared light would even be emitted. Is it coming from the little LED on the front? I've tried with the shutter open but I highly doubt that's the source.
Let me know if you have any ideas! My iMac was purchased at the end of 2010 and it's running the latest Snow Leapord.
Thanks
|
|
2011-05-29
, 11:42
|
|
Posts: 1,390 |
Thanked: 4,262 times |
Joined on Sep 2007
@ Vienna, Austria
|
#60
|
Originally Posted by kurtis
The IR transmitter is the small black square with two corners rounded next to the two-stage (focus + shoot) camera button. You can check if it transmits IR codes by using RaeMote while having your iSight (or any other webcam) pointed to that spot. It should blink in rapid fashion while sending out codes.
I'm using the "Otterbox" case. I don't really see where the infrared light would even be emitted. Is it coming from the little LED on the front? I've tried with the shutter open but I highly doubt that's the source.
| The Following User Says Thank You to thp For This Useful Post: | ||
"I can't seem to get it working" is not a very specific problem report. What did you try? What error messages do you get? What version, firmware, additional packages have you got installed?