Originally Posted by Android_808

funny enough, i spent some of yesterday looking into it. as a warning, 1st time attempting RE, so i may be way off here.

i was expecting to find xprot settings string in strings section of disassembly for use with string comparison to identify sections within config file. so far no luck in -common or -music.

Originally Posted by sulu

2. In LXDE tapping the screen will always trigger the right mouse button which makes it hard to control the desktop. I guess that's manageable via evdev. Reading man evdev also revealed that tap-hold for right click can be configured via evdev and therefore desktop-independent.

Originally Posted by sulu

4. LXDE battery monitor may not work. I say "may" because I only tried with power cable connected.

Originally Posted by sulu

I didn't try phone functions so far, but I'll try soon. Unfortunately the fso-deviced package isn't installable on i386/amd64 atm. Not sure if it's any better on armhf.

Originally Posted by Niko2040

I compiled and packaged Enlightement DR19 for armhf debian unstable. Compiled with systemd support.
From E19 version 0.19.0 alpha 1 mobile profile are deprecated. But default profile is usable.
Trick to add Nokia N900 keyboard support in Enlightenment. After first run (after initial configs created), run in terminal (enlightenment session need to be stopped!):

Code:

eet -d .e/e/config/standart/e.cfg config e.txt

Now, edit e.txt
Find:

Code:

        group "E_Config_XKB_Layout" struct {
            value "name" string: "us";
            value "model" string: "default";
            value "variant" string: "basic";
        }

Replace with:

Code:

        group "E_Config_XKB_Layout" struct {
            value "name" string: "us";
            value "model" string: "nokiarx51";
            value "variant" string: "basic";
        }

After this, run in terminal:

Code:

eet -e .e/e/config/standart/e.cfg config e.txt 1

All E19 packages:
https://www.dropbox.com/sh/ql5b60dyd...w53vFds4a?dl=0

Originally Posted by sulu

RE: critical speaker frequency:
According to this [1] 480Hz is either the critical frequency or well on the safe side. (I'm no audio expert)
So muting everything below that frequency in alsamixer should make audio safe.
Who want's to play the guinea pig?

Originally Posted by sulu

On another note, I finally got around to install Debian on real hardware, installed LXDE and it works mostly fine.

I found some small issues:

1. After a reboot when I select Maemo (CSSU thumb kernel sitting on eMMC) the first attempt to boot will always fail at the 5 dots of dread, the second one will always be fine. No idea if it's a Debian, a u-boot or a CSSU thumb thing.

Originally Posted by sulu

2. In LXDE tapping the screen will always trigger the right mouse button which makes it hard to control the desktop. I guess that's manageable via evdev. Reading man evdev also revealed that tap-hold for right click can be configured via evdev and therefore desktop-independent.

Originally Posted by sulu

I played a bit:
How do I configure evdev in DebiaN900?
I need to figure out which is the correct device. Usualy it's done like this (output from my PC):

Code:

$ find /dev/input/by-id/ -name "*event-mouse"
/dev/input/by-id/usb-Logitech_USB_Mouse-event-mouse

But on the N900 the whole by-id directory isn't there:

Code:

$ ls /dev/input/
by-path  event0  event1  event2  event3  mice  mouse0

In short: I have no idea how to change the mouse button mapping now.

Originally Posted by sulu

3. I noticed that the CLI and GUI keymaps differ (e.g. no Tab via Shift+Space in GUI). Where is the CLI keymap defined for comparison?

Originally Posted by sulu

4. LXDE battery monitor may not work. I say "may" because I only tried with power cable connected.

Originally Posted by sulu

No, it doesn't work. Afair the reason is that it only looks in /sys/class/power_supply/BAT* but it should look in /sys/class/power_supply/bq27200-0
I had a look at the code long ago and I believe this is easily changed. But on the other hand I could have sworn there is a way to configure this without recompilation, which doesn't seem to be true - so no idea how accurate my memory is here.

Originally Posted by sulu

Other than that I'm quite impressed.
btw. is there an easy way to overclock the CPU within Debian, probably the same way KP does it in Maemo?

Originally Posted by sulu

I didn't try phone functions so far, but I'll try soon. Unfortunately the fso-deviced package isn't installable on i386/amd64 atm. Not sure if it's any better on armhf. I guess it's due to changes in connection with systemd introduction (but right now it doesn't work with sysvinit either).]

Originally Posted by sulu

It doesn't install on armhf either, with the same error. I filed a bug report:
https://bugs.debian.org/cgi-bin/bugr...cgi?bug=766114

Originally Posted by wicket

I experience this sometimes too. I think lifeguard timer is being triggered and is resetting the device. Try activating R&D mode to see if that makes a difference.

Originally Posted by wicket

When did you grab the scripts? On 8th October I merged this pull request from Niko2040. Perhaps the EmulateThirdButtonTimeout value needs tweaking. evdev is normally configured in xorg.conf.

Originally Posted by wicket

X11 uses a separate key map. Both key maps are taken from Arch Linux for the N900 as mentioned in the first post. The X11 key map has some problems that are yet to be fixed that have been inherited from the Arch patches. The console key map gets installed with this command and then ends up under /etc/console/boottime.kmap.gz

Originally Posted by wicket

E17 has the same issue although I've not yet looked into it. If the problem is as you describe, I wonder if it could be worked around by creating symlinks.

Originally Posted by wicket

Note that my scripts revert to good old System V init (at least for now). When Debian changed the default init system to systemd, it broke the N900 power button functionality.

Originally Posted by wicket

oFono is also available for Debian if you want to try an alternative to FSO.

Originally Posted by wicket

When Debian changed the default init system to systemd, it broke the N900 power button functionality.

Originally Posted by sulu

I downloaded the zip you provided in the first post on 17th or 18th and created the SD card on 18th.
I think the problem lies deeper since at least to my understanding /dev/input/by-id/ should be present regardless of xorg.conf. It should be there once xserver-xorg-input-evdev is installed.

Originally Posted by sulu

In Easy Debian I copy the whole /usr/share/X11/xkb directory from Maemo to the image (and then set xkb-data on hold). This is the only way I've found so far to make sure the keymap is correct. I tried different things with setxkbmap (the N900 keymap is in Debian) but can't make it work correctly. According to diff both directories are identical.
I'll try if that works for DebiaN900 too.

Originally Posted by sulu

Afaik one can't create symlinks in /sys.

Originally Posted by sulu

I guess in the long run there's no way around systemd in Debian because sysvinit compatibility just won't be maintained actively anymore and I don't believe that any of the recent attemts (new GRs) will really change that.

Originally Posted by sulu

I think I know why the battery monitor doesn't work.
For comparison my netbook:

Code:

$ cat /sys/class/power_supply/BAT0/uevent 
POWER_SUPPLY_NAME=BAT0
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CYCLE_COUNT=0
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=8400000
POWER_SUPPLY_VOLTAGE_NOW=7500000
POWER_SUPPLY_CURRENT_NOW=1192000
POWER_SUPPLY_CHARGE_FULL_DESIGN=6580000
POWER_SUPPLY_CHARGE_FULL=4194000
POWER_SUPPLY_CHARGE_NOW=3337000
POWER_SUPPLY_CAPACITY=79
POWER_SUPPLY_CAPACITY_LEVEL=Normal
POWER_SUPPLY_MODEL_NAME=901
POWER_SUPPLY_MANUFACTURER=ASUS
POWER_SUPPLY_SERIAL_NUMBER=

Notice the key POWER_SUPPLY_CHARGE_NOW which is used to determine the current charge of the battery:

Code:

$ cat /sys/class/power_supply/BAT0/charge_now 
3237000

On the N900 (on battery) I get this:

Code:

$ cat /sys/class/power_supply/bq27200-0/uevent 
POWER_SUPPLY_NAME=bq27200-0
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_VOLTAGE_NOW=4012000
POWER_SUPPLY_CURRENT_NOW=307912
POWER_SUPPLY_CAPACITY_LEVEL=Normal
POWER_SUPPLY_TEMP=311
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CHARGE_FULL_DESIGN=2056320
POWER_SUPPLY_CYCLE_COUNT=22
POWER_SUPPLY_POWER_AVG=315818

POWER_SUPPLY_CHARGE_NOW is missing so the battery monitor has no way to determine the current charge of the battery:

Code:

$ cat /sys/class/power_supply/bq27200-0/charge_now
cat: /sys/class/power_supply/bq27200-0/charge_now: Keine Daten verfügbar

("No data available")