Re: Qt application crashes after 2 minutes if started from app grid
On 05/09/2011 03:04 PM, Cornelius Hald wrote: Hi all! I've got a bit a weird problem. I'd we happy if anyone could give me a hint. My Qt (QML/C++) app terminates after exactly 2 minutes if it was started via the graphical launcher. If I start it from the terminal it runs fine for hours. I think this could be connected with D-Bus, but I'm not sure how/where to look. I remember this being talked about on IRC yesterday - maybe look at the logs? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: is wireless modem tivoizated?
DmitryTurin.narod.ru wrote: what does mean memory is signed and signature? Some number (hash) is calculated for memory of modem, and stored where? Modem re-calculate hash at booting and compare with number, stored in some place? As I understand it, the modem CPU has a small internal boot ROM. It boots from this, and verifies the first stage bootloader on the external flash (which is not part of the normal flash). Only if the http://en.wikipedia.org/wiki/Cryptographic_signature matches is the bootloader executed. This then runs the modem 'main' OS - which is not linux. The modem then boots, and communicates with the main processor running linux for commands. (dial, login to network, ...) The signature is stored in the ROM of the modem CPU. It is very difficult to extract the key from the ROM, as it is not meant to be readable external to the processor. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Is wireless modem support police functions
DmitryTurin.narod.ru wrote: *) Is wireless modem specify in packages the factory number of equipment like Ethernet-card? (this number in Ethernet-packages has cynical name MAC-address) All of the low level functions are dealt with by the modem firmware. This can be flashed. However, it will not operate unless the signature is correct. Even if you replace the (as I understand it) package-on-package flash memory, the chip still verifies the signature before booting. So, you basically can't, unless you can crack the signature. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: chip of cellular/wireless modem
DmitryTurin.narod.ru wrote: If there is a need for: *) catch packages of another phones, You can't do this generally - the hardware cannot do general purpose scanning. For various technical reasons - there are hundreds of channels, and the modem can be tuned to only one, amongst others. Also, for legal reasons the software which runs on the modem chipset will not support this. This software is completely seperate from the application softwae - maemo/meego. *) send package with abnormal AKEY (or abnormal SIS) than it is necessary to patch code of pnatd, working directly with modem, or some other code? You would need to break the signature algorithm in the modem code signing, reverse engineer the interfaces, and then binary patch the modem code to add this functionality. Distributing this code - in the UK - for example - would then be a criminal act - once it's first used to do criminal acts, and you've been notified of this. 'manufacturing' this code for the first time would be a seperate offence. In short - find another platform where it can be done. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Neighboring Cell Towers
Neal H. Walfield wrote: Hi, I'm writing a context-aware application. I want to learn the current location using any visible cell towers and their respective signal snip I can get the currently associated cell tower using the Phone.Net API, but I have not found an interface to obtain the visible, non-connected cell towers. Is there one? Do I have to interface with the SIM card or modem directly? If so, do you have any pointers on how I should go As far as I'm aware, there is no way to do this. ssh root@phone Nokia-N900:~# pnatd at+cops=? +COPS: (2,T-Mobile,,23430,0),(2,T-Mobile,,23430,2), (3,O2 - UK,,23410,0), (3,3 UK,,23420,2),,(0,1,3),(0,2) at+csq +CSQ: 6,99 Is about the closest we get. There isn't as I understand it a way to get the unconnected cell tower info. Various events you can listen to are sent over dbus. http://maemo.org/packages/view/netmon/ for example. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: chip of cellular/wireless modem
DmitryTurin.narod.ru wrote: What is the concrete name of chip of cellular/wireless modem in Nokia 770, Nokia N800, Nokia N810, Nokia N900 ? P.S. E.g. for Nokia N900: As i read, TI OMAP 3430 SoC does not contain integrated modem? No, it doesn't. The n900 has no available documentation on the modem. There is limited information on the chipset - codename Rapuyama. http://wiki.maemo.org/N900_Hardware_Phone http://wiki.maemo.org/N900_Hardware_Schematic This modem has its own RAM. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Nokia and MS
Jeremiah C. Foster wrote: On Fri, Feb 11, 2011 at 09:01:23PM +0100, Klaus Umbach wrote: Don't be silly. Intel has to _compete_ with Android - Android doesn't run on x86 hardware! MeeGo is Intel's embedded OS, and they are spending 100 million US to support just the IVI vertical. I think you're barking up the wrong tree here. Of course it can. http://www.android-x86.org/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: need code for decoding cell broadcast SMS messages
Jonathan Wilson wrote: I am looking for some code that can decode cell broadcast SMS messages, anyone know of any? ofono has some but its too hard to separate from ofono itself. Regular SMS decoders wont work as the cell broadcast SMS message format is different. Have you considered posting on the osmocombb http://openbsc.osmocom.org/trac/ or http://bb.osmocom.org/trac/ mailing lists or IRC? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Nokia and MS
Andrew Flegg wrote: On Fri, Feb 11, 2011 at 9:30 PM, Sivan Greenberg si...@omniqueue.com wrote: On Fri, Feb 11, 2011 at 9:00 PM, Andre Klapper aklap...@openismus.com wrote: On Fri, 2011-02-11 at 13:25 -0500, Demetris wrote: How does this affect the future of Maemo on Nokia's devices? I've three hats to wear: I only have one hat. :( But there is a benefit to this that I can see. With no clear successor for the N900, some people will keep theirs for a bit longer, others - who may have been waiting for the Harmattan device - may now buy one. This means the Community SSU can have more users, more developers and more polish: http://wiki.maemo.org/Community_SSU The graph on http://www.flickr.com/cameras/nokia/n900/ would seem to indicate that n900 use is crashing. From one point of view this is depressing. From another viewpoint, users who have 'upgraded' after 12 months with the n900 may dump their phones on ebay. And the non-hardcore were not to some degree the 'important' userbase for things like CSSU. And as it's a 'dead' platform, it may be fairly cheap. There are many semi-interested hackers that haven't been able to justify a comparatively expensive phone. Added to the promise of the CSSU, and related efforts, as well as the increasing potential freedom both from reverse engineered bits, as well as documentation that should have been found ages ago, but for various reasons hasn't been - and code 'newly' released for meego - the platform could be an interesting one for hackers for some time to come. Even in the absence of a nice shiny new meego phone. I had aspirations to fly concorde one day - if only once. The closest I came was hearing the sonic boom, as it zoomed on its last flight past the east coast of Scotland. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to ensure only HTTP requests from the device can be accepted in a web app?
Sivan Greenberg wrote: Hi list, I'm developing and application that sends very small amounts of data over HTTP ReST to an http server, and want to restrict request to those only coming from the device itself (the N900 running Maemo/MeeGo). This will be of-course complemented with a user login and limitation of how many pings such a user can do to the server a day. What would be the way to achieve this? Has anyone done/ tried something like this before? (I thought about reading some hardware identified off the device, but then again- how do I make sure an IMEI is an RX-51 one? Several issues occur. Firstly - why on earth do you care? If a user is authenticated, why does it matter if they are breaking any agreements they may have made with you to only access content on their n900. Bearing in mind that the absolute maximum possible deterrance is the cost of a 'new' n900 on ebay. The silly hack that comes to mind is to go to the firmware download page, and use that as an authenticator, but that would be insane. Also - as a user, I would be hesitant at giving out my IMEI. While there are few risks at the moment, open-source GSM platforms are becoming available to the hacker community, and the protocol was not really designed for security. I will note that http://www.omniqueue.com/ shows a pleasing sparseness of design, that many websites would do well to imitate. No flash ads, no slow javascript, and at 0 bytes, quick to transfer! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to ensure only HTTP requests from the device can be accepted in a web app?
Sivan Greenberg wrote: On Mon, Nov 8, 2010 at 2:27 PM, Ian Stirling ma...@mauve.plus.com wrote: Firstly - why on earth do you care? If a user is authenticated, why does it matter if they are breaking any agreements they may have made with you to only access content on their n900. Never post to public list when you are going over your 5 tasks in the same time limit. This is perfectly true and holds! Moreover, the client for the service would only run on the N900 (well until I develop a desktop version of it) . but for all purpose a user account would suffice. Yeah - seems more sane to apply it on a per-user basis, as a filter at the server, unless I'm missing something. The silly hack that comes to mind is to go to the firmware download page, and use that as an authenticator, but that would be insane. Out of *pure* technical curiosity how would that work? I mean, how can I ask tablets-dev to authorize someone when it authorizes it due to knowing that IMEI he/she provided is indeed a nokia device? As simple as go to the firmware download page (with a script) enter the IMEI the user supplies, see if it authenticates. Though not specifically answering that point, I suggest http://laforge.gnumonks.org/weblog/gsm/ http://threatpost.com/en_us/blogs/researchers-hijack-cell-phone-data-gsm-locations-042110 Also - you can bar the phone in many instances with only the IMEI, by reporting it stolen. My concern is not so much that you might do something nefarious - but that you might screw up, and my IMEI turns up along with my name, address, and possibly CC/paypal details on thieftorrent. There are - as I understand it - limited attacks that are possible using the IMEI at the moment. GSM very much is not designed as a secure protocol, so I wonder if with the increasing ease of access, if that will remain so. Also - as a user, I would be hesitant at giving out my IMEI. While there are few risks at the moment, open-source GSM platforms are becoming available to the hacker community, and the protocol was not really designed for security. I never gave thought to this, what would it help in abuse to have your IMEI ? I will note that http://www.omniqueue.com/ shows a pleasing sparseness of design, that many websites would do well to imitate. Thanks! I try ;-) Even if it had a design it would most probably be very minimalistic on the brink of a text document No flash ads, no slow javascript, and at 0 bytes, quick to transfer! Cellular data consumer kept in mind! :-p Cheers, -Sivan ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Trying to switch GSM provider by API
Filip-M. Brinkmann wrote: Hi Faheem, thanks for the awesome answer. Due to several reasons, I got into coding not until this week. Your code led to much insight on my side ;) However, It seems that the get_operator_name method on com.nokia.phone.net does not exist (anymore). I verified by issuing dbus-send --system --print-reply --type=method_call --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.get_operator_name Seems like my problem got a lot more difficult now. You have any idea what happened? Maybe the Nokia DBus API changed in PR1.3? PR1.2 dbus-send --system --print-reply --type=method_call --dest=com.nokia.phone.net /com/nokia/phone/net Phone.Net.get_operator_name Error rpc.Error: can't find method Phone.Net::get_operator_name ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: listenning for orientation changes using dbus
David Hautbois wrote: Hello I'm looking for a way to listen for orientation changes using dbus. the subscription to the mce dbus service sig_device_orientation_ind works fine, but only when the device is unlocked. I'm using this to avoid battery draining. I also tried Qmobility, but this uses 10% of CPU. I don't think that an infinite loop querying the orientation is the good trick How to enable this signal when the device is locked ? Is there another way ? The good news is the hardware can interrupt on orientation change. (sort-of). The bad news is that the kernel driver does not do this. The only way to read the accel is to poll. Depending on the latency you need, polling may not be too bad. A 5s poll isn't _too_ nasty on battery life. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Using N900 accelerometer with 8g
ds wrote: Hello, as far as I can read from wiki the accelerometer should be usable in a 2g and 8g mode. Does anybody know how to switch the modes?? Standard mode is 2g I think. echo full /sys/class/i2c-adapter/i2c-3/3-001d/scale Pops it into 8G mode. http://wiki.maemo.org/N900_Hardware_Accelerometer lists some other APIs - I'm unsure if rthese implement that. Thanks a lot D. Schmicker ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: how to get crash stack trace in Maemo 2.2 (Nokia 770)
Han wrote: Hi, I am using Maemo 2.2 to develop some programs for Nokia 770. Things run pretty well except sometime my program would crash for unknown reason. Normally I start the program from x terminal, and it would crash with only message Killed. I am wondering if possible to get a stack trace when the program crashes? so that I can find out where the crash happened in the code. I tried to reproduce the issue with i386 in scratchbox, but did not repro yet... My exposure to 2.2 is limited to seeing a 770 once. However. Have you tried simply starting the program under gdb? Also- might it be the OOM killer? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: backgrounding/lock QA fail
Attila Csipa wrote: I see we have a few apps (especially ports and stuff using SDL) that do not know how to suspend themselves and therefore it fails the QA. Now, I was thinking, as this sort of bug is a kind of a 'be aware' type, is that maybe we could allow these to pass if they made it clear to the user they are not able to suspend themselves. A popup after install, or a Hildon banner before/during startup... that sort of I would with some hesitation agree to this. For some apps, it's probably the only sensible route. Expecting the porter of a huge app that did little more than simply package it, and write 3 or 4 lines of description to take the leap to screwing with core portions of the event loop is hard. It should not be a blocker if there is no practical way to change it. But for apps where it should be possible to change this easily, it should remain. http://wiki.maemo.org/N900_Software_Power_management - I'm planning to populate with links to info on how to change, as well as flesh it out some more. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How can I get Display Resolution in N900 maemo5?
praveen koduru wrote: Hi Ian, I have tried apt-get install xrandr on my N900, Errror: couldnt find the package. Can you tell me which package you installed to make xrandr work for you on N900? I diddn't. open a terminal on the phone. ssh -X yourdesktop xrandr ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: is there a way to make N900 Display doesnt OFF?
praveen koduru wrote: is there a way to make N900 Display doesnt go OFF? I am able to set it maximum to wait for only 2 mins. I need it for long time. I recall from browsing the docs that the general way to do this is for the app to say every minute 'keep screen on for a couple of minutes'. This is what the media player and ... does. I don't have a link to this in the docs though. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: n900 debugging techniques
Martin DeMello wrote: So I installed kernel-power, which appears to have killed my gps (even when I reverted to the stock kernel), and I'd like to try finding out exactly what's wrong, rather than just reflashing. What are the general techniques to debug this sort of thing? dmesg has nothing, and I can't see anything promising in /var/log/* either. http://repository.maemo.org/pool/maemo5.0/non-free/l/location-test-gui/ may be of use. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Controlling N900 Display Brightness Display turn on
praveen koduru wrote: Hi, I need to control the Display Brightness Display Turn off(While it went to standby). For Display Turn on, I have increased the standby timer to 2 mins(max). But I need to increase it further more say 10 mins. Can I control that? As I understand it, the general way to do this is to tell the system every 30s to keep the display on. This stops software accidentally leaving the display on. For Display Brightness, I need to dim and bright the Display programatically, like using dbus commands. I'm unsure if this is possible, I haven't investigated it. I'd look at the source of simple-brightness-widget. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Unable to write to the serial port /dev/ttyS0 using QextSerialPort on Maemo device
suyash.ku...@tieto.com wrote: OK, I understood, Thanks for the explanation Denis but I have one more question? IWe decided this approach as we have already implemented serial communication of Nokia N95 and PC (connected via USB cable). We simply used the symbian APIs for writing the information to the COM1 port and received the same on the windows PC's COM1 port and read it from there thus establishing a successful serial communication. That's why I was trying the same for Maemo. The serial port is not visible physically on N95 also but somehow we managed the serial communication between device and PC using this approach. Also, if the serial communication is not possible in this way, can you suggest me some other way/ sample code to achieve the same. That wasn't really USB, it was RS232, with a wierd connector. There are some RS232-over-USB-port capable phones - but absolutely no desktop hosts support this. Serial (RS232) and Universal Serial Bus - have about as much in common as man and manatee. You need to configure the n900s USB port to emulate a RS232-USB converter - in some way. http://www.kernel.org/doc/Documentation/usb/gadget_serial.txt is an overview of how it would be setup. Unfortunately, I'm unaware of how this would interact with the default process that enables the requisite USB drivers. I know hald-addon-usb-cable monitors the lowest level of this, and sends an event on dbus, but I'm unsure what watches for this event, and configures USB gadgets. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: GoogleCL
Sivan Greenberg wrote: Looks cool, I think I'll give it a try but most surely someone else here will already have packaged it faster than me :) Actually even if that is the case, I think this now enabled providing lean UI to do all that common tasks with google services, especially bulk uploads of photos or creating blogger posts with the html ready so you don't have to fight with blogger's terrible handling of inline code snippet. I was playing with this eaarlier on the phone uploading photos to picasa. Fun. I'd not been using picasa for a while, as there was no easy way of uploading pics from linux. Interesting to some will also be the calendar and youtube options! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Low Latency Audio Capture on the N900, QAudioInput BUG: has 5000msec latency, Meego audio future
Benno Senoner wrote: Thanks to all for your responses, yes I agree with what you said. I will try to track the evolution of the audio subsystem on meego and provide my feedback and findings. I'll discuss the issue with the JACK authors too what they think about it, about adding power management to jack etc. (the main author of Jack2, Stephane Letz is one of the coauthors to LinuxSampler too). It's understandable that Nokia will probably not change the audio subsystem for the current Meego version, so at least they should try to provide a stable working system, giving developers a way to achieve 50msec mic to speaker latency. As I understand it, pulseaudio on the n900 achieves 5ms latency, and a few dozen microseconds of jitter. It's just not for normal users. I point you at: http://linuxplumbersconf.org/2009/slides/Jyri-Sarha-audio_miniconf_slides.pdf ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How many times each application is downloaded from extras-devel
Andrew Flegg wrote:
On Wed, Jun 16, 2010 at 17:40, Felipe Crochik fel...@crochik.com wrote:
Is there a way to find out how many times each application was downloaded
from extras-devel? It would be a valuable tool to help access if the
applications are being used (and/or are useful) and decide on how to
invest on each one.
Not sure - there is once you get to Extras; click Download
Statistics on the http://maemo.org/downloads/ page.
No, there isn't, that's misleading.
#!/bin/bash
wget --quiet
http://maemo.org/download-stats/fetch.php?unixname=$1os=Maemo5; -O -|\
awk -F'[' '/^ *var d/{for(x=1;xNF;x++){split($x,a,,);
total+=a[2]}}END{print total}'
(also at http://www.mauve.plus.com/count-downloads)
This says - for ecoach - 105529.
http://maemo.org/download-stats/index.php?unixname=ecoachos=Maemo5repo=extras
is the page which it pulls this info from.
http://maemo.org/packages/view/ecoach/ says 108000
But.
http://maemo.org/packages/view/ecoach/ - gives several dates, if you
look at the package events, and glance at the graph, you can see that
both the 'download-stats', and the 'maemo.org/packages/view' page must
be counting downloads from extras-devel and testing too.
For some preliminary analysis that I did for fmms - as many users have
testing enabled as extras.
The download number is also misleading - as it's really 'total downloads
and updates'.
ecoaches headline number is 100K.
In reality, it seems likely that the real number of users is more like 10k.
(integrate the size of the spike after each package event, and you can
see how many updated. If you look at the shape of this when there are no
external events, then you can decipher stuff.
For example - a upload of a fresh version to testing - if over the next
5 days, there are 5K downloads, and then 12 days later when it's pushed
to extras - there are 3K - then it's probably reasonable to assume there
are around 5000 users with extras-devel enabled, and 3000, with extras only.
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QT map widget
Till Harbaum / Lists wrote: Hi, Am Samstag 12 Juni 2010 schrieb Joerg Reisenweber: It's rather moot, as this isn't a movie at 25fps, so an occasional image refresh, no matter how it's done, will take magnitudes less energy per time in average, than the backlight eats to display the image. When screen is dimmed (or the widget invisible/hidden/background) then of course all gfx workload should suspend, for obvious reasons 100% CPU load is bad no matter if this is for a 25fps movie or a 0.5fps 3d map widget. Believe me, i have these discussions regarding maep. People _do_ care for CPU load and battery consumption. And this is good. I believe the point is not that battery life is unimportant, but that with the backlight on, the CPU using 200% of nominal for 2/25th of the time, this increases the total CPU power by 8%. But - using numbers from http://wiki.maemo.org/N900_Hardware_Power_Consumption - with the screen on dim, and the GPS on, this 8% drops to 4% of total system load. - with the backlight on bright, it's only an increase of 2.5% or so. The main point I was attempting to make was not this one anyway. It was that while 3D may be possible on platforms similar to the n900, it is undesirable, even if it performs perfectly, if the widget may also be wanted to run on the increasing number of low end phones that may have limited or no 3D capability. (Unless of course it can also do 2D optimally - but that seems like lots more code/work.) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QT map widget
Till Harbaum / Lists wrote: Hi, Am Freitag 11 Juni 2010 schrieb Marijn Kruisselbrink: You might also want to look at the marblewidget (http://edu.kde.org/marble/). I did. On the n900 as well as on the linux desktop. While i really think this is great for desktops i also think that it isn't the right thing for mobile devices. There are several issues: - It is big and installs ~10MB data - It is pretty complex and doesn't really fit on the small screen - It takes several seconds to load - It runs pretty slow snip I have read that poeple are working on the speed issue. But speed alone isn't And speedups may be very possible - if for example you can offload portions of the workload onto a GPU. But, for the forseeable future, 3D will not always be available on the mobile platform. Especially as I wouldn't expect the future of featurephones to be a simple race to 2GHz/GPU/... Yes, that'll be happening - but in parallel will be soon coming out (I predict - regrettably I have no inside info) n900-lite devices based on whatever can be gotten that week in china. It's also not impossible that as capacities of cheap phones rise - take a look at http://noknok.tv/2010/01/04/nokia-5230-officially-shipping/ - for example - and even phones at the very bottom of the market are starting to include 'web browsers' - capabilities of the processors and GPU will not be up to n900 levels for some years. The ability for such a widget to be 'cross platform' - and run on small devices would be a valuable one. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Quality assurance of stable software: my battery drained in few hours
Jan Knutar wrote: Doesn't the userland carry some sort of process monitoring, killing malignant processes ? If not, we should develop something like this for MeeGo. It's pretty hard to find out what's eating the battery on N900. First you have decide that the battery is being consumed too fast. The default charge meter occasionally realizes it's very wrong, and rapidly readjusts itself, giving potential misreadings there. bq27200 certainly helps there, though there's no production quality software available to use it yet. Nokia Energy Profiler still shines with its absence ;) I'm trying to develop something like this. An energy profiler. The ideal would be 'top' - sorted by power use. But this is hard. :) Initial stages are looking like something rather more modest. Basically porportion out to every job that ran in a measured period a best guess at a 'fair' proportion of the power use during that period. Further break this down by subsystem. It's not 'fair' for example to count the power usage of xterm as very high, due to the backlight/display being on, when that's the users fault. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Quality assurance of stable software: my battery drained in few hours
Robin Burchell wrote: On Sun, Jun 6, 2010 at 2:23 PM, Ian Stirling maemo-de...@mauve.plus.com wrote: It's pretty hard to find out what's eating the battery on N900. First you have decide that the battery is being consumed too fast. The default charge meter occasionally realizes it's very wrong, and rapidly readjusts itself, giving potential misreadings there. bq27200 certainly helps there, though there's no production quality software available to use it yet. Nokia Energy Profiler still shines with its absence ;) I'm trying to develop something like this. An energy profiler. The ideal would be 'top' - sorted by power use. But this is hard. :) You mean, like, powertop? http://en.wikipedia.org/wiki/PowerTOP No, fairly unlike powertop. Powertop sorts by wakeups, which is not useless. Consider a compute intensive task that uses 99.95% of the CPU. At the same time, you've got a lightweight task that polls some descriptor 10 times a second. This will appear above the application that's really causing most battery drain. Powertops metric - wakeups per second - is arguably for some loads better than top, but it can be horribly misleading for a number of reasons. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: DBus Methods and Signals Introspection or Documentation
Wei Li wrote: Hi all, I am doing a project of middleware on Maemo/N900. I need to find the methods and signals related to the hardware, for example, HAL (especially the objects under /com/nokia since it is somehow proprietary). However, I couldn't find a detailed documentation on that. And I also used tools such as mdbus2, but since it lacks documentation and so does DBus itself, I couldn't figure out how to do the introspection to find the information I want. Anyone knows how to find that? Thanks! As I understand it, many of these mrhods do not support introspection, and there is no documentation. For example - the dbus 'backend' of liblocation. It's possible I'm confused, and have simply missed the docs. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
