Feature Request / Feedback for a my project

2010-04-13 Thread Alexander Schröter
Hi I am very happy with my N900 and Maemo as it's operating system. But a couple of things I am unhappy with. Some of them rather minor others are bigger. I am writing these down in the hopes that some can be fixed by the community and also I would like some feedback on how important those feat

Re: Weird battery (?) problem bricked N900

2010-04-13 Thread Joerg Reisenweber
[Dawid Lorenz Di 13. April 2010]: > [...] He said that during normal > use, just while fiddling with menu/apps, suddenly a "charging error" message > appeared (*without* a charger connected!), notification light turned red and > device has switched off by itself, never booting back again. No idea

Re: N900: Force charging on USB?

2010-04-13 Thread Joerg Reisenweber
[Nils Faerber Di 13. April 2010]: > Hi! > I am preparing for a vacation and want to avoid carrying too many > accessories. > So I took my universal USB charger (which is just a USB plug carrying > the +5V) plugged in the Nokia micro-USB cable and connected to the N900. > > Well, it does not charg

DBus / mce

2010-04-13 Thread André Hänsel
Hi, I tried this example code: http://wiki.maemo.org/Using_Fremantle_widgets#Listening_To_Hardware_Orientat ion_Changes_.28Python_example.29 However, it only works when the telephony application is running at the same time. Otherwise the sig_device_orientation_ind is not being sent, as one can al

N900: Force charging on USB?

2010-04-13 Thread Nils Faerber
Hi! I am preparing for a vacation and want to avoid carrying too many accessories. So I took my universal USB charger (which is just a USB plug carrying the +5V) plugged in the Nokia micro-USB cable and connected to the N900. Well, it does not charge - in contrast to almost any other device. This

Re: Weird battery (?) problem bricked N900

2010-04-13 Thread Dawid Lorenz
2010/4/13 Cláudio Sampaio > As for the continued malfunction, have you tried to reflash everything, > including the eMMC? Might be a corruption in files caused by the successive > attempts to get it up, that could only be fixed by a complete reflash. Yes, as I already said - I've reflashed both