Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - cattin

Pages: [1] 2
Zaurus - pdaXrom / Fvwm-pdaxrom 0.4.x
« on: March 21, 2006, 02:29:23 am »
I used the method proposed by jerrybme above and made a three level window zoom function out of it.

- First key press (Fn+2) maximises the window with the taskbar still visible
- The second key press (Fn+2) resizes the window so that it covers the taskbar
- Third key press (Fn+2) removes window decorations and uses the full screen for
  the window
- Fourth key press (Fn+2) switches the window back to its initial size

To use it, just put the code below in your /home/root/.fvwm/personal/config file and restart the window manager.

have fun, Philippe

Code: [Select]
Key 2 A 2 RotateFullscreen

DestroyFunc RotateFullscreen
AddToFunc   RotateFullscreen
+ I Current (!State 0) Zoom1
+ I Current (!State 1) Zoom2
+ I Current (!State 2) Zoom3
+ I Current (State 2) Zoom0

DestroyFunc Zoom1
AddToFunc Zoom1
+ I SetEnv OldX-$[] $[w.x]
+ I SetEnv OldY-$[] $[w.y]
+ I SetEnv OldWidth-$[] $[w.width]
+ I SetEnv OldHeight-$[] $[w.height]
+ I Current Maximize 640p 448p
+ I Current State 0 true
+ I Break 2

DestroyFunc Zoom2
AddToFunc Zoom2
+ I Current ResizeMaximize 640p 455p
+ I Style ZaurusTaskbar StaysOnBottom
+ I Current State 1 true
+ I Break 2

DestroyFunc Zoom3
AddToFunc Zoom3
+ I Move 0p 0p
+ I Resize 100 100 frame
+ I WindowStyle NoTitle, !Borders, StaysOnTop, !Iconifiable, !Maximizable
+ I Current State 2 true
+ I Break 2

DestroyFunc Zoom0
AddToFunc Zoom0
+ I DestroyWindowStyle
+ I PipeRead "echo ResizeMove \\$\\[OldWidth-$[]\\]p \\$\\[OldHeight-$[]\\]p \\$\\[OldX-$[]\\]p \\$\\[OldY-$[]\\]p"
+ I Current State 0 false
+ I Current State 1 false
+ I Current State 2 false
+ I Break 2

Zaurus - pdaXrom / Needsl-c7x0/860 Owner With Sd Mmc Cards Bigger 1g
« on: February 18, 2006, 03:58:51 pm »
The Sandisk 2GB SD card I have is not working properly on my 3k1 on 1.1.0beta1. I would therefore like to test the new driver as well.

thanks, ph

Zaurus - pdaXrom / Kdepimpi For Rc12 On 3100
« on: January 07, 2006, 02:20:00 pm »
Well done cattin.  Is the "14% constant CPU usage by KA/PI" issue still there?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=109865\"][{POST_SNAPBACK}][/a][/div]

unfortunately this version of KA/PI still uses precious CPU resources even when idle.


Zaurus - pdaXrom / Fvwm-pdaxrom 0.4.x
« on: December 22, 2005, 03:52:49 am »
Keep up the good work! I like your fvwm configuration a lot. It allows me to configure and change the functionality very easily. As of this release it works a lot better on the SL-C3100. There are only two thinks that aren't properly working so far:

(1) the CPU  speed Menu. Your CPU speed logic doesn't seem to work on the C3k1 platform. I'll try to look into this next week.

(2) from time to time strange things happen to the taskbar when turning on the Z. Sometimes I get an additional purple 'X' with the root menu, sometime I get an additional ztaskbar in a separate window.

BTW: I love your dynamic menus! I haven't yet studied the mechanics behind it, but it seems the logical place for a CF/SD/wlan card unmounting menu.

regards, Philippe

Zaurus - pdaXrom / A Couple New Packages
« on: December 19, 2005, 06:17:04 am »
Just tried your attachment, with an /etc/gnokiirc containing:

port = /dev/ircomm0
model = AT
initlength = default
connection = infrared
bindir = /usr/local/sbin

It's a Nokia 8890 which apparently uses the AT "model".

I did the "/etc/rc.d/init.d/irda start" and switched on the infrared on the phone.

gnokii --identify responds with "Telephone interface init failed" and xgnokii "GSM/FBUS init  failed!" which apparently means no comms with the phone    I suppose the phone could be broken.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=107507\"][{POST_SNAPBACK}][/a][/div]

replace 'infrared' with 'irda' and it should work.


Zaurus - pdaXrom / 3100 Power Switch & X
« on: December 09, 2005, 04:34:35 am »
I have the same problem, but it's easy to avoid it:

When you push the power button to suspend (or use the menu in X), just make sure you wait long enough before you resume. (about 15 seconds ?). I don't know exactly how long it is you really have to wait, but it solves the problem for me.

when you push the power button, the backlight is turned off immediately. you can still see the windows/desktop under bright light and perfectly see when the Z really turns off. only after it completely turned off you can savely switch it on again.

regards, ph

Zaurus - pdaXrom / Alarms With Kdepim/pi For Rc12 Sl-c3100
« on: December 07, 2005, 03:38:51 am »
I copied the original apmsleep back and tried it. That doesn't work either, it just stays off until I use the On/Off button to wake it up again. BTW did you use the patch that albertr refers to in post #16?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=106309\"][{POST_SNAPBACK}][/a][/div]

No I didn't have to compile a patched kernel. I just flashed a brand new SL-C3k1 with RC12 directly (including the kernel). Even the original apmsleep was working as long as one didn't wrap around a day boundary.

regards, philippe

Zaurus - pdaXrom / Alarms With Kdepim/pi For Rc12 Sl-c3100
« on: December 06, 2005, 11:41:16 am »
Is there anything I can do to further debug this? I would love to get it working (I've already installed the specially compiled version kdepim in anticipation )

this is a mistery to me, as the RTC settings seem to be okay. did your zaurus wakeup with the old apmsleep?


Zaurus - pdaXrom / Alarms With Kdepim/pi For Rc12 Sl-c3100
« on: December 05, 2005, 05:19:00 pm »
I must have messed up with the timezone logic. I'll look into it this afternoon and post a revised version. Shouldn't be too difficult to fix.

It took me a little longer as expected as I have a four week old NMI (non maskable interrupt) called Celine ;-)

the changelog for this new release 0.1 is as follows:

- rewrote the timezone logic in apmsleep.c. 'apmsleep +h:m' should work regardless your timezone.

- I also made 'apmsleep hh:mm' timezone aware and added one more twist to the original implementation. If hh:mm has already passed this day, the Zaurus will wake up @ hh:mm the next day :-) quite obvious but didn't work in the original implementation.

- the two scripts next_kopi_alarm & next_kopi_suspend both check whether kopi is indeed a running process, as it doesn't make sense to turn on the zaurus when kopi is not running in the first place (so don't change the filename of kopi or otherwise adapt the scripts accordingly).

I hope this release solves the problem people were reporting with my initial version and doesn't break for users were it already worked.

regards, Philippe

Zaurus - pdaXrom / Alarms With Kdepim/pi For Rc12 Sl-c3100
« on: December 05, 2005, 03:29:05 am »
Mine doesn't work either.  By running apmsleep I found that the RTC time is wrongly set if /etc/localtime exists.

I must have messed up with the timezone logic. I'll look into it this afternoon and post a revised version. Shouldn't be too difficult to fix.


Zaurus - pdaXrom / Alarms With Kdepim/pi For Rc12 Sl-c3100
« on: December 04, 2005, 04:33:59 pm »
Thanks for your great work, Philippe.

my C1000 doesn't wake up before the alarm   

Is it a C1000 problem ?

There are several thinks you could test to find out the problem:

1.) check that the scripts in /etc/apm/wakeup.d are working correctly

Code: [Select]
cd /etc/apm/wakeup.d

are there any errors? does next_kopi_alarm give you the right number of minutes until the next alarm? the output of next_kopi_suspend is most likely an empty line.

2.) check apmsleep

Code: [Select]
/usr/bin/apmsleep -d +0:1
this should put your zaurus at sleep for 1 minute and then wake up again. if you don't get an error here and your debug output looks okay then there might be a more fundamental problem with your setup.

regards, Philippe

Zaurus - pdaXrom / Alarms With Kdepim/pi For Rc12 Sl-c3100
« on: December 04, 2005, 10:06:41 am »
I'm sure you are all well aware of the problems with KO/PI alarms on pdaxrom. I checked all the relevant threads in this forum but couldn't find a working solution. So I started designing my own.

My solution doesn't scan ko/pi's data file for the next alarm, but uses the two files (/home/root/.kopi_next_alarm & .kopi_suspend_alarm) created by ko/pi and relies on ko/pi to play the alarmtone and display the alarm message. My proposed solution can therefor not be called an 'alarm applet' as it just tries to fire-up the zaurus shortly before an alarm event triggers and as it requires KO/PI to be running.

The first problem I had to solve was related to bad parameters KO/PI used to play the alarm sound with the playwave command. This was easy to solve, as I just removed the offending sampling rate option '-r ....' from the source and recompiled KO/PI. With this simple change KO/PI could play the alarm sound given my zaurus was already running when the alarm was triggered.

Next I wrote three little scripts that would wake up the zaurus just before an alarm, so that KO/PI could ring the alarm. As you might know, the zaurus runs all scripts found in the folder /etc/apm/wakeup.d just before suspending. Each script either returns nothing or the number of minutes the zaurus should wait before wakeing up. So I created two little shell scripts (/etc/apm/wakeup.d/next_kopi_alarm & /etc/apm/wakeup.d/next_kopi_suspend) that are simple wrappers to the real awk script /etc/apm/scripts.d/min_to_next_kopi_alarm.awk. These scripts just  return the remaining minutes until the next alarm and are called just before the zaurus suspends.

So far so good. My Zaurus could now wake up just before an alarm and play the alarm sound. For some strange reason this only worked for alarms on the same day, and not for alarms e.g. the next morning. As can be easily seen in the suspending scripts, apmsleep is called in the following manner:

Code: [Select]
apmsleep +0:n
with n being the number of minutes until the next alarm (note: n can be bigger than 60). As it turned out, the Zaurus wouldn't wakeup if the next alarm wrapped around midnight. It turned out, that apmsleep is indeed not aware of day wraps and was thus waiting for a time that alread passed.
My first tests after making the apmsleep command aware of day wraps seem to work. I am, however, not sure that it works correctly with all timezones.

Attached you find the apmsleep.c with my suggested changes. If you feel like playing around with it you need the apmd_3.2.1.orig.tar.gz package from the pdaxrom site to compile. Otherwise just use the binary version I included in this thread.

I don't take any responsibility if it doesn't work or even fries your Z ;-)

any comments or suggestions?

regards, Philippe

### Installation

1. copy all the files (except apmsleep.c) to your zaurus (in my case a SL-C3100)

2. mv next_kopi_suspend next_kopi_alarm /etc/apm/wakeup.d

3. mv min_to_next_kopi_alarm.awk /etc/apm/scripts.d

4. mv /usr/bin/apmsleep /usr/bin/apmsleep.orig

5. mv apmsleep /usr/bin

6. check, that all files are executable

Zaurus - pdaXrom / Kdepimpi For Rc12 On 3100
« on: December 04, 2005, 08:45:18 am »
As I need the password manager as well, I cross compiled the most recent version 2.2.7 of pim/pi. This ipkg contains kopi, kapi, kammu, pwmpi, and ompi. Beware that I changed one small thing. In particular I removed the sampling rate option '-r ...' when ko/pi calls 'playwave' in case of an alarm, as this option is not supported on my RC12's playwave.

regards, Philippe

PS: In a separate post I will describe my solution to the alarm problem for ko/pi on my 3100.

Zaurus - pdaXrom / Kdepimpi For Rc12 On 3100
« on: November 29, 2005, 03:12:21 am »
there are two problems with this version of kdepimpi I know of (they have all been reported in this forum):

1. kapi expects the libraries to be in a different place than kopi. simple links should solve this problem.

Code: [Select]
cd /opt/kdepimpi
ln -s /usr/lib/libmicrokabc* .

2. when you start kapi the window manager doesn't automatically show kapi's window. you can, however, activate it with ALT-TAB. I have seen this behaviour with MB, in fvwm it seems to work properly.


Zaurus - pdaXrom / 3100 Beta Testers Needed!
« on: September 16, 2005, 01:42:03 pm »
C3100/C1000 new test rom:

can anyone tell me how to make a rooted version out of this? I'd like to try the newest release on my spitz (C3000).

thanks, philippe

Pages: [1] 2