Re: Gtalk call doesnt work on 3/3.5 G Network

2010-04-26 Thread Kevin T. Neely
Nimbuzz doesn't exist for Maemo yet, only Symbian.  I was just noting when 
Skype works and when it doesn't for my particular network.  I don't know how 
you could proxy the service somehow.  I don't know how Nimbuzz achieves its 
particular connection to the Skype network.

K

On Mon, Apr 26, 2010 at 10:09:43AM +0400, khalid khan wrote:
 Ok I see. But Kevin can you help me to download the Nimbuzz application for
 N900 because i couldn't find it in Ovi nor in Maemo web pages, generally in
 Ovi the Nimbuzz version is not compatible to N900.
 
 Or should i use proxy server for gtalk to be used in 3G network.
 
 Thanks
 Khalid
 
 On Mon, Apr 26, 2010 at 9:59 AM, Kevin T. Neely ktne...@astroturfgarden.com
  wrote:
 
  It may be your carrier.  I notice that on ATT, Skype will not connect, but
  it will when I am using wifi.  What is weird is that using the exact same
  SIM in a Symbian phone, I can connect to Skype using Nimbuzz, although that
  is probably proxied through their own servers.
 
  K
 
  On Mon, Apr 26, 2010 at 04:38:46AM +, khalid.re...@gmail.com wrote:
   Hi,
   Do anyone facing problem using N900 to make calls via gtalk on 3G or 3.5G
  network .I am using Data Package when i call the online gtalk contact it
  connects but no voice from both side.
   Amazingly the gtalk call works on Wi-fi connections perfectly.I have set
  the network setting mode as Any Connections  tick marked Wi-fi connection
  when available is this causing any problem to call gtalk from 3G.
   Note: In UAE there is restrictions to use skype  other third party call
  services but still gtalk works on PC or N900 in Wi-fi.
   Thanks
   Khalid
   --
   Sent from my mobile computer using Nokia Messaging
 
   ___
   maemo-users mailing list
   maemo-users@maemo.org
   https://lists.maemo.org/mailman/listinfo/maemo-users
 
 
  --
  In Vino Veritas
  http://rubbernecking.info
 
 
  -BEGIN PGP SIGNATURE-
  Version: GnuPG v1.4.10 (GNU/Linux)
 
  iEYEARECAAYFAkvVK8AACgkQE+4TUALb7FEMUQCfS9+wvaOJCTWZLRfjXUwyC98Y
  a/8AoJBsrLOxnb6PDFbUZ9w9b3NL1P3y
  =2aC2
  -END PGP SIGNATURE-

-- 
In Vino Veritas
http://rubbernecking.info



signature.asc
Description: Digital signature
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: Gtalk call doesnt work on 3/3.5 G Network

2010-04-26 Thread Bernard Tyers

It will be your carrier. The reason operators do this is so they don't loose 
revenue from services like SMS and voice calls. Sometimes also due to stupidity 
like anti-terrorism laws.

NB: This is not a defence of this practice.

You have a number of options:

1. Complain and ask them if they block gtalk. They may or may not unblock it.
2. Use a service that offers a proxied IM/voip service-like fring, nimbuzz, etc.
3. Try using tor.

Hope that helps.

Bernard

- Original message -
 Ok I see. But Kevin can you help me to download the Nimbuzz application for
 N900 because i couldn't find it in Ovi nor in Maemo web pages, generally in
 Ovi the Nimbuzz version is not compatible to N900.

 Or should i use proxy server for gtalk to be used in 3G network.

 Thanks
 Khalid

 On Mon, Apr 26, 2010 at 9:59 AM, Kevin T. Neely ktne...@astroturfgarden.com
  wrote:

  It may be your carrier.  I notice that on ATT, Skype will not connect, but
  it will when I am using wifi.  What is weird is that using the exact same
  SIM in a Symbian phone, I can connect to Skype using Nimbuzz, although that
  is probably proxied through their own servers.
 
  K
 
  On Mon, Apr 26, 2010 at 04:38:46AM +, khalid.re...@gmail.com wrote:
   Hi,
   Do anyone facing problem using N900 to make calls via gtalk on 3G or 3.5G
  network .I am using Data Package when i call the online gtalk contact it
  connects but no voice from both side.
   Amazingly the gtalk call works on Wi-fi connections perfectly.I have set
  the network setting mode as Any Connections  tick marked Wi-fi connection
  when available is this causing any problem to call gtalk from 3G.
   Note: In UAE there is restrictions to use skype  other third party call
  services but still gtalk works on PC or N900 in Wi-fi.
   Thanks
   Khalid
   --
   Sent from my mobile computer using Nokia Messaging


___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: Gtalk call doesnt work on 3/3.5 G Network

2010-04-26 Thread khalid khan
Thank you Bernard for your kind information but here in UAE
Skype,Fring,Nimbuzz or other third party are blocked only gtalk is working,
i will take your advise  call to customer care  check what is the issue 
remedy to that, if they have any.

Best Regards,
Khalid

On Mon, Apr 26, 2010 at 10:32 AM, Bernard Tyers 
b...@runningwithbulls.comwrote:


 It will be your carrier. The reason operators do this is so they don't
 loose revenue from services like SMS and voice calls. Sometimes also due to
 stupidity like anti-terrorism laws.

 NB: This is not a defence of this practice.

 You have a number of options:

 1. Complain and ask them if they block gtalk. They may or may not unblock
 it.
 2. Use a service that offers a proxied IM/voip service-like fring, nimbuzz,
 etc.
 3. Try using tor.

 Hope that helps.

 Bernard

 - Original message -
  Ok I see. But Kevin can you help me to download the Nimbuzz application
 for
  N900 because i couldn't find it in Ovi nor in Maemo web pages, generally
 in
  Ovi the Nimbuzz version is not compatible to N900.
 
  Or should i use proxy server for gtalk to be used in 3G network.
 
  Thanks
  Khalid
 
  On Mon, Apr 26, 2010 at 9:59 AM, Kevin T. Neely 
 ktne...@astroturfgarden.com
   wrote:
 
   It may be your carrier.  I notice that on ATT, Skype will not connect,
 but
   it will when I am using wifi.  What is weird is that using the exact
 same
   SIM in a Symbian phone, I can connect to Skype using Nimbuzz, although
 that
   is probably proxied through their own servers.
  
   K
  
   On Mon, Apr 26, 2010 at 04:38:46AM +, khalid.re...@gmail.comwrote:
Hi,
Do anyone facing problem using N900 to make calls via gtalk on 3G or
 3.5G
   network .I am using Data Package when i call the online gtalk contact
 it
   connects but no voice from both side.
Amazingly the gtalk call works on Wi-fi connections perfectly.I have
 set
   the network setting mode as Any Connections  tick marked Wi-fi
 connection
   when available is this causing any problem to call gtalk from 3G.
Note: In UAE there is restrictions to use skype  other third party
 call
   services but still gtalk works on PC or N900 in Wi-fi.
Thanks
Khalid
--
Sent from my mobile computer using Nokia Messaging


 ___
 maemo-users mailing list
 maemo-users@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-users

___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: how memory management mechanism of maemo, where can I find information?

2010-04-26 Thread Andre Klapper
Hi,

Am Sonntag, den 25.04.2010, 23:46 -0300 schrieb Rafael Rocha:
 hi everybody, I am now just studying how memory management mechanism
 of maemo, where can I find information?

Can you please be a bit more specific, or describe what you plan to do?
Makes it more likely to get an answer... 

Thanks,
andre

-- 
Andre Klapper (maemo.org bugmaster)

___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: N900 power consumption

2010-04-26 Thread Henrik Frisk
Hi Adrian,

I haven't updated my firmware since I received the unit so probably
no. I will try that. Does it affect the power management?

/h

On Mon, Apr 26, 2010 at 7:26 AM, Adrian Yanes de...@ayanes.com wrote:
 Hi Henrik,

 Do you have the latest firmware version?

 On 22 April 2010 00:27, Henrik Frisk fris...@gmail.com wrote:
 Hi,

 After a few weeks of usage my up time before the battery was
 completely drained was less than 7 hours (during this time the unit
 was idle; completely unused). I started disabling services following
 the suggestions in some of the other threads discussing battery
 duration. Widgets, skype, they all went. But to my surprise, the
 biggest power hog was the sip account. When I disabled it my up-time
 was more reasonable. Anyone knows a way to reduce the power
 consumption without disabling the account? Some of the advanced
 options I don't really know what they do.

  It's really a shame because I was so pleased to finally have found a
 mobile sip client that really works. Any suggestions are appreciated.

 best,

 /henrik
 ___
 maemo-users mailing list
 maemo-users@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-users


___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: N900 power consumption

2010-04-26 Thread Bernard Tyers

Unless a newer firmware is available, don't upgrade to 3.2010.02-8. 

I have found since I upgraded my battery life has gone from 1 1/2 days to about 
7-8 hours.

Hope that helps,
Bernard

- Original message -
 Hi Adrian,

 I haven't updated my firmware since I received the unit so probably
 no. I will try that. Does it affect the power management?

 /h

 On Mon, Apr 26, 2010 at 7:26 AM, Adrian Yanes de...@ayanes.com wrote:
  Hi Henrik,
 
  Do you have the latest firmware version?
 
  On 22 April 2010 00:27, Henrik Frisk fris...@gmail.com wrote:
   Hi,
  
   After a few weeks of usage my up time before the battery was
   completely drained was less than 7 hours (during this time the unit
   was idle; completely unused). I started disabling services following
   the suggestions in some of the other threads discussing battery
   duration. Widgets, skype, they all went. But to my surprise, the
   biggest power hog was the sip account. When I disabled it my up-time
   was more reasonable. Anyone knows a way to reduce the power
   consumption without disabling the account? Some of the advanced
   options I don't really know what they do.
  
    It's really a shame because I was so pleased to finally have found a
   mobile sip client that really works. Any suggestions are appreciated.
  
   best,
  
   /henrik
   ___
   maemo-users mailing list
   maemo-users@maemo.org
   https://lists.maemo.org/mailman/listinfo/maemo-users
  
 
 ___
 maemo-users mailing list
 maemo-users@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-users

___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: N900 power consumption

2010-04-26 Thread Andre Klapper
Am Montag, den 26.04.2010, 09:18 +0100 schrieb Bernard Tyers:
 Unless a newer firmware is available, don't upgrade to 3.2010.02-8. 
 
 I have found since I upgraded my battery life has gone from 1 1/2 days
 to about 7-8 hours.

...while for others 3.2010.02-8 has increased battery life.

I don't think that such generic statements are helpful without providing
some basic info (what does that time refer to? Being online? Heavy usage
or idling? IM accounts activated? Extra software installed? etc etc).

andre
-- 
Andre Klapper (maemo.org bugmaster)

___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: N900 power consumption

2010-04-26 Thread Bernard Tyers

- Original message -
 Am Montag, den 26.04.2010, 09:18 +0100 schrieb Bernard Tyers:
  Unless a newer firmware is available, don't upgrade to 3.2010.02-8.
 
  I have found since I upgraded my battery life has gone from 1 1/2 days
  to about 7-8 hours.

 ...while for others 3.2010.02-8 has increased battery life.

 I don't think that such generic statements are helpful without providing
 some basic info (what does that time refer to? Being online? Heavy usage
 or idling? IM accounts activated? Extra software installed? etc etc).

That time refers to unplugging device from charger at 7-8AM and having battery 
go down approx to half way by lunchtime.

I measure a day as 24 hours.

Most of the day when I am in the office it is connected to work wifi to receive 
mail. When at work it is idling on wifi.

By afternoon if I do not charge it, the device will be dead by approx 6-7PM.

If I am at home I use it to read rss feeds, and make calls. When at work it is 
idling on wifi.

* Phone ALWAYS on 2G, unless I want to download something via cellular network.
* No more softwae installed than before upgrade.
* exact same IM accounts/SIP acount usage as before.

After the upgrade I reconfigured all settings/parameters for maximum power 
saving as they were wiped when the upgrade finished.

At the weekend I use my E71 and joikuspot to share 3G access to the n900.

By 6-7PM since 10-11AM the battery is almost empty. (This is understandable)

I don't make statements like that without testing extensively.

Bernard

___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: N900 power consumption - particularly on SIP VoIP

2010-04-26 Thread Henrik Frisk
On Thu, Apr 22, 2010 at 5:15 PM, Joerg Reisenweber jo...@openmoko.org wrote:
 [Henrik Frisk Mi  21. April 2010]:
 But to my surprise, the
 biggest power hog was the sip account. When I disabled it my up-time
 was more reasonable. Anyone knows a way to reduce the power
 consumption without disabling the account? Some of the advanced
 options I don't really know what they do.

  It's really a shame because I was so pleased to finally have found a
 mobile sip client that really works. Any suggestions are appreciated.


 Hi Henrik,

 as usual the main battery energy leak in *idle* is 3G TX (and to a lower
 degree 2(.5)G as well). TX occurs for each bit of data sent upstream to the
 internet including TCP ACK for downstream TCP data.

 So a SIP user agent *may* idle completely for hours, just waiting for an
 inbound call. But usually you see TX activity caused by re-registrations, NAT
 keep-alive pkgs, MWI notification, propagation of own online status, updating
 online status of contacts(!), STUN, hosted NAT traversal, and even arbitrary
 bogus data packages inbound to port 5060 or the RTP ports.
 Alas there's relatively little you can do about this, as most of the issues
 depend on your SIP registrar's and your GSM/UMTS provider's config of their
 services.

 You could install SIP Swiss army knife User Agent twinkle [1] - probably to
 your PC as regrettably there's no N900 or even ARM version I'd know of -
 tether N900 to PC to use the 3G of your provider, and then try if you find
 some better settings for the 512 knobs and dials you can tweak SIP with.
 Things like changing port from 5060 to a value not associated to SIP come to
 mind, as it's even possible your carrier isn't interested that much in a
 working SIP over his network. If you're really going to dive into that, feel
 free to ping me on IRC [2], I might still be able to walk you through
 twinkle's various functions and settings, and help create and interpret decent
 twinkle logs.

 FWIW: My SIP account at sipgate.de seems to work relatively flawless, though I
 never thoroughly tested the maximum battery endurance when connected strictly
 via 3G only.

Thanks for this very helpful information. It seems to help if I allow
my N900 to switch to selected WiFi netwworks when available. Also, I
wonder what the N900 SIP account settings Keep.alive-mechanism and
Keep-alive-period and the switchable Automatic STUN detection may
do to the power consumption. The fact that your SIP account appears to
work well without draining the battery suggests that this is an issue
that may be resolved by tweaking the settings, (or, as was suggested
in another reply, a new firmware. What's your firmware Joerg?) Also, I
shoud point out that the SIP client works excellent, the only problem
is it's draining the battery.

Thanks,

/Henrik
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: N900 power consumption

2010-04-26 Thread Dawid Lorenz
On 26 April 2010 10:01, Bernard Tyers b...@runningwithbulls.com wrote:

 If I am at home I use it to read rss feeds, and make calls. When at work it
 is idling on wifi.

 * Phone ALWAYS on 2G, unless I want to download something via cellular
 network.
 * No more softwae installed than before upgrade.
 * exact same IM accounts/SIP acount usage as before.

 After the upgrade I reconfigured all settings/parameters for maximum power
 saving as they were wiped when the upgrade finished.


When your N900 is idling, fire up top (preferably via ssh session) and see
whether pulseaudio is constantly eating 2-5% of CPU. If so, run killall
tongend as root. This is a bug fixed in PR1.2 (afaik) which seems to be
launched sometime between today and the next decade.

Also, BatteryGraph application from extras(-testing?) helps debugging
battery usage a lot. From what I found, the *greatest* *ever* battery hog is
browsing web via 3G. I do that daily while commuting to/from work and it can
take up to 40-50% of battery within less than an hour!

-- 
Dawid 'evad' Lorenz * http://adl.pl

null://google 'no evil' mail has taken away my random signatures
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: N900 power consumption

2010-04-26 Thread Igor Stoppa

ext Bernard Tyers wrote:


If I am at home I use it to read rss feeds, and make calls. When at work it is 
idling on wifi.
  


It would be interesting to know if it supports power save.

Even if you have not changed anything, in the environment where the N900 
lives, setup conditions different from the expected ones (and I believe 
our testing is done with AP with power-save enabled) might give 
interesting results. Like this one.


igor
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: N900 power consumption

2010-04-26 Thread Bernard Tyers

- Original message -
 ext Bernard Tyers wrote:

  If I am at home I use it to read rss feeds, and make calls. When at work it 
  is
  idling on wifi.   

 It would be interesting to know if it supports power save.

Are you asking about the wifi ap? I'll check and see if that is the case. That 
doesn't help though if I am in the wild using a public wifi spot.

 Even if you have not changed anything, in the environment where the N900
 lives, setup conditions different from the expected ones (and I believe
 our testing is done with AP with power-save enabled) might give
 interesting results. Like this one.

Agreed. My only real issue is with the power management of this device. I 
understand installing non-power optimised software will likely cause issues, 
but this is no help when some issues are device related.

Other than power, this is an excellent device.

Bernard
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: N900 power consumption

2010-04-26 Thread Bernard Tyers


 When your N900 is idling, fire up top (preferably via ssh session) and see
 whether pulseaudio is constantly eating 2-5% of CPU. If so, run killall
 tongend as root. This is a bug fixed in PR1.2 (afaik) which seems to be
 launched sometime between today and the next decade.

I had a look at top and /usr/bin/pulseaudio --system --high-priority seems to 
be running constantly, at around 0.2 (when idle) to approx. 32.2% cpu (when 
making a call).

Trying to killall tongend gives response:
killall: tongend: no process killed. 

This is right, as the /usr/bin/tongend process ID is the same after the kill 
command as before it.

 Also, BatteryGraph application from extras(-testing?) helps debugging
 battery usage a lot. 

I've used it and I don't find it too useful, unless I do nothing for that time.

From what I found, the *greatest* *ever* battery hog is
 browsing web via 3G. I do that daily while commuting to/from work and it can
 take up to 40-50% of battery within less than an hour!

Not my case, as I do little browsing with 3G (only if I am out of wifi 
coverage).

Thanks,
Bernard
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: N900 power consumption

2010-04-26 Thread Michel Dänzer
On Mon, 2010-04-26 at 12:10 +0100, Bernard Tyers wrote: 
 
  When your N900 is idling, fire up top (preferably via ssh session) and see
  whether pulseaudio is constantly eating 2-5% of CPU. If so, run killall
  tongend as root. This is a bug fixed in PR1.2 (afaik) which seems to be
  launched sometime between today and the next decade.
 
 I had a look at top and /usr/bin/pulseaudio --system --high-priority seems 
 to be running constantly, at around 0.2 (when idle) to approx. 32.2% cpu 
 (when making a call).

Non-0 usage when idling probably means you're suffering from the
tonegend bug or a similar one.

 Trying to killall tongend gives response:
 killall: tongend: no process killed. 
 
 This is right, as the /usr/bin/tongend process ID is the same after the kill 
 command as before it.

There's a typo, should be 'killall tonegend' (first 'e' was missing).


-- 
Earthling Michel Dänzer   |http://www.vmware.com
Libre software enthusiast |  Debian, X and DRI developer
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: N900 power consumption

2010-04-26 Thread Dawid Lorenz
On 26 April 2010 12:10, Bernard Tyers b...@runningwithbulls.com wrote:

 I had a look at top and /usr/bin/pulseaudio --system --high-priority
 seems to be running constantly, at around 0.2 (when idle) to approx. 32.2%
 cpu (when making a call).


CPU usage when making a call is valid. I meant pulseaudio constantly taking
approx. 2-5% CPU time when device is completely idle, even with screen off.
Oh, found it: https://bugs.maemo.org/show_bug.cgi?id=6868



 Trying to killall tongend gives response:
 killall: tongend: no process killed.

 This is right, as the /usr/bin/tongend process ID is the same after the
 kill command as before it.


As Michel pointed - there was a typo, I should say 'tonegend'.



  Also, BatteryGraph application from extras(-testing?) helps debugging
  battery usage a lot.

 I've used it and I don't find it too useful, unless I do nothing for that
 time.


It helps finding which usage patterns are the most battery-hungry and gives
indication of some dodgy background action (like tonegend above) eating
battery when device is supposedly idle. But that's only my personal
preference, I guess.

All in all, I definitely concur that one of N900's worst gripes is power
management (or lack of thereof) and getting out without a charger at hand
for more than 1 day should be considered a crime. ;)

-- 
Dawid 'evad' Lorenz * http://adl.pl

null://google 'no evil' mail has taken away my random signatures
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: how memory management mechanism of maemo, where can I find information?

2010-04-26 Thread Rafael Rocha
i'm actually just doing a job in college
well, if I wanted to know where to find information about operation of the
architecture, including memory management

ie wanted to know how to read the maemo maximize memory management and gain
relative to symbian too.


On Mon, Apr 26, 2010 at 3:59 AM, Andre Klapper aklap...@openismus.comwrote:

 Hi,

 Am Sonntag, den 25.04.2010, 23:46 -0300 schrieb Rafael Rocha:
  hi everybody, I am now just studying how memory management mechanism
  of maemo, where can I find information?

 Can you please be a bit more specific, or describe what you plan to do?
 Makes it more likely to get an answer...

 Thanks,
 andre

 --
 Andre Klapper (maemo.org bugmaster)

 ___
 maemo-users mailing list
 maemo-users@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-users

___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


N900 power usage entrail reading skills (aka powertop output)

2010-04-26 Thread Marius Gedminas
I get the feeling that my N900 eats through its battery quicker than it
used to.  I'm not sure when it started, maybe when I upgraded to
RX-51_2009SE_3.2010.02-8_PR_MR0 firmware?  It could very well be some
app's fault.

Here's what powertop says.  Note that the CPU is spending almost 100%
time at 500 MHz.  Any clues?  The word 'mmc' shows up quite a lot and
pretty high up, but what could be causing all that IO, if that's IO I'm
seeing?  top is not very informative; the highest-CPU-using process is
'top' itself at 1.5%.  iotop doesn't run on Maemo (Linux = 2.6.20 with
I/O accounting support: Not found)

Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 9217us

C#  | Ratio  | Avg/dura | Frequency | Ratio
++--+---++
 C0 |  43.3% |  |   600 MHz |   3.1% |
 C1 |   4.6% |0.5ms |   550 MHz |   0.0% |
 C2 |  45.2% |4.7ms |   500 MHz |  96.4% |
 C3 |   6.8% |   19.1ms |   250 MHz |   0.5% |
 C4 |   0.0% |  | 

IRQ#| Activity   | Type   | Name
+++---
 12 |   7410 |   INTC | DMA
 86 |   5456 |   INTC | mmc1
 37 |   2433 |   INTC | gp
 11 |611 |   INTC | prcm
 56 | 90 |   INTC | i2c_omap
 57 | 43 |   INTC | i2c_omap
202 | 19 |   GPIO | wl1251

PID#| Activity   | Name   | Function Entry (Expire)
+++---
  0 |   2365 |  kernel core | tick_nohz_restart_sched_tick 
(tick_sched_timer)
492 |192 |  mmcqd | cfq_completed_request 
(cfq_idle_slice_timer)
 37 | 94D|awk | cpufreq_governor_dbs 
(delayed_work_timer_fn)
   1087 | 30 | hildon-desktop | schedule_hrtimeout_range 
(hrtimer_wakeup)
492 | 22 |  mmcqd | queue_delayed_work 
(delayed_work_timer_fn)
464 | 12 | wl12xx | schedule_timeout (process_timeout)
464 | 12 | wl12xx | queue_delayed_work 
(delayed_work_timer_fn)
   1370 | 11 |hildon-thumbnai | blk_plug_device (blk_unplug_timeout)
  25268 | 10 |skyhost | futex_wait (hrtimer_wakeup)
  25262 |  8 |skyhost | do_nanosleep (hrtimer_wakeup)
706 |  8 |  bme_RX-51 | sys_timer_settime (posix_timer_fn)
  0 |  7 |  kernel core | hrtimer_start (tick_sched_timer)
 29 |  6 |  mount | setup_wb_timer (wb_timer_fn)
464 |  4 | wl12xx | schedule_timeout (process_timeout)
   1140 |  4 |   wlancond | ieee80211_ioctl_siwpower 
(ieee80211_dynamic_ps_timer)
747 |  4 |   avahi-daemon | schedule_hrtimeout_range 
(hrtimer_wakeup)
686 |  3 |   dsme | do_nanosleep (hrtimer_wakeup)
686 |  3 |   dsme | __enqueue_rt_entity 
(sched_rt_period_timer)
  17887 |  3 |pdflush | blk_plug_device (blk_unplug_timeout)
 15 |  3 |kswapd0 | schedule_timeout (process_timeout)
  0 |  2 |  kernel core | queue_delayed_work 
(delayed_work_timer_fn)
706 |  2 |  bme_RX-51 | do_nanosleep (hrtimer_wakeup)
706 |  2 |  bme_RX-51 | schedule_timeout (process_timeout)
 10 |  2 |omap2_mcspi | neigh_add_timer (neigh_timer_handler)
  1 |  2D|  kernel core | queue_delayed_work 
(delayed_work_timer_fn)
   1370 |  2 |hildon-thumbnai | journal_get_write_access 
(commit_timeout)
   1584 |  2 |   FBReader | schedule_hrtimeout_range 
(hrtimer_wakeup)
  25477 |  1 |   sshd | sk_reset_timer (tcp_write_timer)
706 |  1 |  bme_RX-51 | sys_timer_settime (posix_timer_fn)
   1097 |  1 |e-addressbook-f | schedule_timeout (process_timeout)
   1370 |  1 |hildon-thumbnai | schedule_timeout (process_timeout)
  17887 |  1 |pdflush | journal_get_write_access 
(commit_timeout)
  1 |  1 |  kernel core | inet_initpeers (peer_check_expire)
716 |  1 |dbus-daemon | schedule_hrtimeout_range 
(hrtimer_wakeup)
927 |  1 |dbus-daemon | schedule_hrtimeout_range 
(hrtimer_wakeup)
  25557 |  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: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
per |OFF:   0%|RET:  51%|INA:   0%| ON:  48%| 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:   0%|RET:   0%|INA:   0%| ON: 100%| now:(ON)
   neon |OFF:   

Re: N900 power usage entrail reading skills (aka powertop output)

2010-04-26 Thread archebyte .
Hi,

On Mon, Apr 26, 2010 at 10:47 AM, Marius Gedminas mar...@pov.lt wrote:
 I get the feeling that my N900 eats through its battery quicker than it
 used to.  I'm not sure when it started, maybe when I upgraded to
 RX-51_2009SE_3.2010.02-8_PR_MR0 firmware?  It could very well be some
 app's fault.


I have seen this happen on a couple of occasions. Restarting
hildon-desktop (killall hildon-desktop) seems to resolve it.


 Here's what powertop says.  Note that the CPU is spending almost 100%
 time at 500 MHz.  Any clues?  The word 'mmc' shows up quite a lot and
 pretty high up, but what could be causing all that IO, if that's IO I'm
 seeing?  top is not very informative; the highest-CPU-using process is
 'top' itself at 1.5%.  iotop doesn't run on Maemo (Linux = 2.6.20 with
 I/O accounting support: Not found)

 Powertop 1.13.3
 status: Unknown job: pmtrackerdaemon
 Sleeping for 11 seconds before sampling
 Collecting data for 30 seconds
 Sample interval was 00m 30s 9217us

 C#      | Ratio  | Avg/dura | Frequency | Ratio
 ++--+---++
     C0 |  43.3% |          |   600 MHz |   3.1% |
     C1 |   4.6% |    0.5ms |   550 MHz |   0.0% |
     C2 |  45.2% |    4.7ms |   500 MHz |  96.4% |
     C3 |   6.8% |   19.1ms |   250 MHz |   0.5% |
     C4 |   0.0% |          |

 IRQ#    | Activity   | Type           | Name
 +++---
     12 |       7410 |           INTC | DMA
     86 |       5456 |           INTC | mmc1
     37 |       2433 |           INTC | gp
     11 |        611 |           INTC | prcm
     56 |         90 |           INTC | i2c_omap
     57 |         43 |           INTC | i2c_omap
    202 |         19 |           GPIO | wl1251

 PID#    | Activity   | Name           | Function Entry (Expire)
 +++---
      0 |       2365 |  kernel core | tick_nohz_restart_sched_tick 
 (tick_sched_timer)
    492 |        192 |          mmcqd | cfq_completed_request 
 (cfq_idle_slice_timer)
     37 |         94D|            awk | cpufreq_governor_dbs 
 (delayed_work_timer_fn)
   1087 |         30 | hildon-desktop | schedule_hrtimeout_range 
 (hrtimer_wakeup)
    492 |         22 |          mmcqd | queue_delayed_work 
 (delayed_work_timer_fn)
    464 |         12 |         wl12xx | schedule_timeout (process_timeout)
    464 |         12 |         wl12xx | queue_delayed_work 
 (delayed_work_timer_fn)
   1370 |         11 |hildon-thumbnai | blk_plug_device (blk_unplug_timeout)
  25268 |         10 |        skyhost | futex_wait (hrtimer_wakeup)
  25262 |          8 |        skyhost | do_nanosleep (hrtimer_wakeup)
    706 |          8 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
      0 |          7 |  kernel core | hrtimer_start (tick_sched_timer)
     29 |          6 |          mount | setup_wb_timer (wb_timer_fn)
    464 |          4 |         wl12xx | schedule_timeout (process_timeout)
   1140 |          4 |       wlancond | ieee80211_ioctl_siwpower 
 (ieee80211_dynamic_ps_timer)
    747 |          4 |   avahi-daemon | schedule_hrtimeout_range 
 (hrtimer_wakeup)
    686 |          3 |           dsme | do_nanosleep (hrtimer_wakeup)
    686 |          3 |           dsme | __enqueue_rt_entity 
 (sched_rt_period_timer)
  17887 |          3 |        pdflush | blk_plug_device (blk_unplug_timeout)
     15 |          3 |        kswapd0 | schedule_timeout (process_timeout)
      0 |          2 |  kernel core | queue_delayed_work 
 (delayed_work_timer_fn)
    706 |          2 |      bme_RX-51 | do_nanosleep (hrtimer_wakeup)
    706 |          2 |      bme_RX-51 | schedule_timeout (process_timeout)
     10 |          2 |    omap2_mcspi | neigh_add_timer (neigh_timer_handler)
      1 |          2D|  kernel core | queue_delayed_work 
 (delayed_work_timer_fn)
   1370 |          2 |hildon-thumbnai | journal_get_write_access 
 (commit_timeout)
   1584 |          2 |       FBReader | schedule_hrtimeout_range 
 (hrtimer_wakeup)
  25477 |          1 |           sshd | sk_reset_timer (tcp_write_timer)
    706 |          1 |      bme_RX-51 | sys_timer_settime (posix_timer_fn)
   1097 |          1 |e-addressbook-f | schedule_timeout (process_timeout)
   1370 |          1 |hildon-thumbnai | schedule_timeout (process_timeout)
  17887 |          1 |        pdflush | journal_get_write_access 
 (commit_timeout)
      1 |          1 |  kernel core | inet_initpeers (peer_check_expire)
    716 |          1 |    dbus-daemon | schedule_hrtimeout_range 
 (hrtimer_wakeup)
    927 |          1 |    dbus-daemon | schedule_hrtimeout_range 
 (hrtimer_wakeup)
  25557 |          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: 100%|RET:   0%|INA:   0%| ON:   0%| now:(OFF)
    per |OFF:   

Re: N900 power consumption

2010-04-26 Thread Craig Woodward

I found quite the opposite.  My battery life went from ~16 hours to ~26 hours 
when 3.2010.02 hit.  It was the one noticeable change on the device from the 
update. :)  And yes, I have a very similar setup.  It's on wifi at home and 
work, and on 2.5G when not on Wifi.  I have the IM plugin enabled and am 
constantly on-line, do moderate web surfing at times (usually on wifi), and 
occasional mp3 playing.

I've also seen a major increase with the new over-clock kernels, which I 
tweaked and played with a bit.  The main set(s) have simple branches that are 
low voltage or ultra-low voltage.  Even if you don't overclock (Titan's kernels 
by default are the standard 250-600 range), just using the newer kernels can 
increase device life quite a bit.  Since I put in the lv kernel set (oc set to 
250-900) I've been seeing average battery levels at 50% or so most nights, and 
have had an actual up-time of over 40 hours between charges a couple times now 
over weekend trips.

Personally I'm more surprised that these devices can last as long as they do on 
the battery they have.  Most people would love to get a few hours out of a 
laptop while web browsing.  Why do you expect a device with as much power as a 
laptop to last longer just because it has a GSM chip in it?  Admittedly, my 
last cell phone had an up time of 2 or 3 days between charges, but that's all 
it really did.  If I ran J2ME apps on it, that life cut down to a day or less 
quick.  I'm pleased as punch that I can IM, text, browse a bit, enter calendar 
items, etc, and still have any juice left at all at the end of the day. :)


 Bernard Tyers b...@runningwithbulls.com wrote: 

=

Unless a newer firmware is available, don't upgrade to 3.2010.02-8. 

I have found since I upgraded my battery life has gone from 1 1/2 days to about 
7-8 hours.

Hope that helps,
Bernard

- Original message -
 Hi Adrian,

 I haven't updated my firmware since I received the unit so probably
 no. I will try that. Does it affect the power management?

 /h

 On Mon, Apr 26, 2010 at 7:26 AM, Adrian Yanes de...@ayanes.com wrote:
  Hi Henrik,
 
  Do you have the latest firmware version?
 
  On 22 April 2010 00:27, Henrik Frisk fris...@gmail.com wrote:
   Hi,
  
   After a few weeks of usage my up time before the battery was
   completely drained was less than 7 hours (during this time the unit
   was idle; completely unused). I started disabling services following
   the suggestions in some of the other threads discussing battery
   duration. Widgets, skype, they all went. But to my surprise, the
   biggest power hog was the sip account. When I disabled it my up-time
   was more reasonable. Anyone knows a way to reduce the power
   consumption without disabling the account? Some of the advanced
   options I don't really know what they do.
  
    It's really a shame because I was so pleased to finally have found a
   mobile sip client that really works. Any suggestions are appreciated.
  
   best,
  
   /henrik
   ___
   maemo-users mailing list
   maemo-users@maemo.org
   https://lists.maemo.org/mailman/listinfo/maemo-users
  
 
 ___
 maemo-users mailing list
 maemo-users@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-users

___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users

___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users