Pdaxrom 1.1.0beta 4 - Bugfixes And Feed, for C1000/C3100/C3200 Options

[sashz]

http://mail.pdaxrom.org/node/82

Next 1.1.0beta4 preparing for C7x0/860

[MONVMENTVM]

great! Just now I wanted to look into the sound things and so on.

Thank you sashz!

[Xromer]

Sashz, as i' m finishing compiling the Beta3 completely to add the rules-ipk for the GPE-Packages, when the Beta4 Builder will be online?
I had many problems compiling the kernel with the Builder.
Now i think that could be because you need the /usr/include/linux stuff already in the PdaXrom.iso X86 env to compile the kernel.
Do you think that this could be the problem?
Now that i understood better the builder composition, i will add the rules-ipk of the GPE-PIMS directly in the builder, so that dependencies will be satisfied automatically like the ROMS one.
Very, very good work Sashz, the Builder is perfectly functional now that i understood how to fix addresses of the packages and compilation rules.
Now, do you think the Pakacges i built with the Beta3 will work with the Beta4 release or i have to wait for the Beta4 builder to build them?
Because i have to know if i can flash directly the Beta4 or wait until all the Developing packages are online.
BYEZ!

[sashz]

super!!

I'll upload builder tomorrow, also pdaXrom beta4 for x86 (host system for builder )

Sashz, as i' m finishing compiling the Beta3 completely to add the rules-ipk for the GPE-Packages, when the Beta4 Builder will be online?
I had many problems compiling the kernel with the Builder.
Now i think that could be because you need the /usr/include/linux stuff already in the PdaXrom.iso X86 env to compile the kernel.
Do you think that this could be the problem?
Now that i understood better the builder composition, i will add the rules-ipk of the GPE-PIMS directly in the builder, so that dependencies will be satisfied automatically like the ROMS one.
Very, very good work Sashz, the Builder is perfectly functional now that i understood how to fix addresses of the packages and compilation rules.
Now, do you think the Pakacges i built with the Beta3 will work with the Beta4 release or i have to wait for the Beta4 builder to build them?
Because i have to know if i can flash directly the Beta4 or wait until all the Developing packages are online.
BYEZ!

[gromituk]

Can you make sure the stylus problem fix is included please? http://www.oesf.org/forums/index.php?showtopic=19411

[emip]

1) Does anybody else find that their settings menu in fbpanel goes off the bottom of the screen? I can't always access the lower items. Is there a way to fix this?

2) I'm working on a fix for the LAN & WIFI applet to allow multiple profiles to work again (as this was a very useful feature). Is anybody else interested in this?

3) Is it possible to get the hostap utilities put into the main ROM in future versions? It's tricky to install them without wireless networking, which is why I need them. (Should I build my own ROM for this?)

4) Does video acceleration work with a standard video overlay?

5) When I tap the screen with the stylus, sometimes it does not register that I have un-tapped and the mouse stays down (for example, if I click on a button, the button might stay down until I click somewhere else). Is this something anybody else has found, and is there a way to fix it?

6) Thank you all so much! I really appreciate your ongoing hard work.

[sashz]

1) - patch coming soon
2) - yes!
3) - yes
4) - overlay driver exists but mplayer not support it yet
5) - need fix it

[emip]

Here are two hacks I have made to make networking on my pdaXrom 1.1.0beta4 work more smoothly.
They're not pretty and not ideal!

pdaxrom-1.1.0beta4-network-applet-hack.tar.gz
This is a hack of network.py (The LAN & WIFI configuration applett).
It allows a person to use multiple profiles again, with the following restrictions:
If a profile is wireless, then the configuration will be applied to the wlan0 interface.
If the profile is normal, then the configuration is applied to the eth0 interface.
EXCEPT: if the profile is named usb0, then it is applied to the usb0 interface.
NOTE: Do not name your profiles wlan0 or eth0 anymore!

pdaxrom_1.1.0beta4_hostap_fw_fix2.tar.gz
This fix loads firmware into prism2 CF cards automatically when they are inserted, it's been updated so it works more often. (100% in my experience)
This is helpful for cards like: Netgear MA 701, Planex GW-CF11X, Linksys WCF11, etc.
See: A list of prism2 CF cards

Enjoy.

Attached File(s)

 pdaxrom_1.1.0beta4_hostap_fw_fix2.tar.gz ( 80.29K ) Number of downloads: 294
 pdaxrom_1.1.0beta4_network_applet_hack.tar.gz ( 7.16K ) Number of downloads: 232

 

[MONVMENTVM]

5) If you tap the screen a bit longer there is no problem if you release it. If you tap and release fast then the Zaurus doesnt know that you already released so it remains "tapped".

[bdbell]

There are two main problems I am having with using the latest beta - I am hoping someone can help me with these so that I can continue to use it I have a 3100.

- I can not get the right click with stylus to work (works fine with mouse of course). In the Input settings applet the default for right click is 'Fn' - but that does not work. I have tried the other options with no luck, except tap and hold for right click - but after the first tap and hold every tap is then a right click!

- after exiting X I can not type the letter 'a' - so I can not restart X - my only option is to type reboot, pull the battery out, or press reset. All other keys seem to work after exiting x - except A?

The only other problem I was having was the menu being cut off - but it looks like there is a fix on the way for that

thanks for the great work on this amazing rom!

[MONVMENTVM]

It seems that you dont have the latest release. In the first beta4 release I also had that problem with "A" after exiting X.... but now it is gone.

look here: http://mail.pdaxrom.org/node/82

[flexibyte]

wow, I'm starting to love this rom!
I almost dismissed using this rom as it seems you need to always run as root to allow things to run smoothly. However, I've now gotten used to the idea and it does infact simplify things (though Im sure Ill change my mind when I accidently rm -rf / or something ).

I'm having similar problems to the others in this thread, but sashz has identified them so I wont repeat them. I would like to second gromituk's request for the stylus fix though. Tapping and holding a scroll bar becomes an annoyance when the page you are trying to read keeps jumping about. The stylus doesnt need to be that accurate, so giving it some breathing room for tiny movements would be good.

Now the problems Ive been having:

1) one problem that i havnt seen mention is the jogwheel on the side of the Cxxxx doesnt seem to be working properly... only 'up' works on it. Also only the down key on the min keyboard has repeat keys ie. press and hold and it keeps scrolling a webpage. I have to use the jogwheels up to scroll back up in a similar fassion as the up keyboard key only pressed once when you hold it down.

2) The delay from pressing and holding a key to the key repeating seems too short. I often accidently enter 2 or 3 of the same key. Is there any way to change this delay?

3) The clock time and date keep resetting when I reboot! it keeps join back to 1970 jan 1st, so to compile anything I need to set the time again after reboot otherwise it sees my build environment is not sane

4) I cant tear myself away from the Zaurus now, and as a result I'm getting very little sleep. Can anyone recommend any good caffine products

Keep up the good work - if all this gets fixed (except number 4 ) I'll start donating on a regular basis, and I'll make it my mission to get other people to donate too - if i'm really happy I will donate a small percent of profit for every Zaurus I sell when I start selling them

Thanks,
Phill

[emip]

3) The Z doesn't seem to have a powered RTC chip, so if you take all the power away, you lose the date and time. Install the ntpdate package and run "ntpdate pool.ntp.org" to set the time easily when connected to ethernet or wlan or something... it's not ideal, but pretty easy.

4) Live in the UK? Try Red Bull or one of the ripoffs like Blue Charge, Kick, etc... (or pro-plus if you like pills)
Live in the US? Try Mountain Dew (banned in the UK) (or vivarin if you like pills -- very strong!)
Live /anywhere/? get a caffatiere and buy some freshly ground coffee and make a nice cup of alertness

--

Has anybody found that their Z becomes unstable now when overclocked? I find in 520 I often get super-distortion on the screen and in 624 it's often to unstable to use, especially with a wifi card attached... might this be too much current being used?
Any ideas?

[flexibyte]

3) The Z doesn't seem to have a powered RTC chip, so if you take all the power away, you lose the date and time. Install the ntpdate package and run "ntpdate pool.ntp.org" to set the time easily when connected to ethernet or wlan or something... it's not ideal, but pretty easy.

4) Live in the UK? Try Red Bull or one of the ripoffs like Blue Charge, Kick, etc... (or pro-plus if you like pills)
Live in the US? Try Mountain Dew (banned in the UK) (or vivarin if you like pills -- very strong!)
Live /anywhere/? get a caffatiere and buy some freshly ground coffee and make a nice cup of alertness

--

Has anybody found that their Z becomes unstable now when overclocked? I find in 520 I often get super-distortion on the screen and in 624 it's often to unstable to use, especially with a wifi card attached... might this be too much current being used?
Any ideas?

I'll pickup some redbull ripoffs on my next shopping trip
Okay, I guess the network time will do fine, I'll mainly be around a wifi access point anyway.

I have overclocked to 624 fine. I have been running at that speed while compiling and I havnt noticed any problems yet.

[MONVMENTVM]

Thats funnny... I found the overclocking potential of beta4 to be something really *special*. When I first overclocked I didnt believe that it was because the screen had no distortion or something else... just the speed and the really told me that it was OC'ed... really nice!