New Rom

[kahm]

I'll fire it up and tonight and put the USB stuff through it's paces. I was a bit busy yesterday ;_;

[iamasmith]

I'll fire it up and tonight and put the USB stuff through it's paces. I was a bit busy yesterday ;_;
[div align=\"right\"][a href=\"index.php?act=findpost&pid=73829\"][{POST_SNAPBACK}][/a][/div]

Kahm,

Glad to see that you could join us.

You may want to download the memory applet update that I posted on the last page too.

Have fun,

Andy

[euroclie]

Damn, you guys are so fast... Hard to keep up with only a dialup connection!

I've downloaded the new memory applet and will try it ASAP. FWIW the original one worked like a charm, I did setup a 64Mb swapfile on the SD card allright.

A few notes about what I've found so far:

MusicPlayer 2.0:
The display in play view is a bit "corrupted": every text displayed is not properly erased when modified, and some of it doesn't display at the proper place right from the starts (horizontally). So it's impossible to read the tune's title, or the next tunes coming... all the digits (which I suppose are bitmaps) display fine, though. There's also a bit of the "Off" button bitmap scattered on the bottom left part of the display. All in all the display looks a bit messy, but otherwise the application works as expected, from what I could tell.

Movie Player 1.11:
At first, I thought that the MPEG-1 movies that played fine on the Sharp stock ROM (v1.01) did not play anymore. I was getting a rather obscure "" error message (Japanese text, for sure, but displayed with a non-Japanese font) when trying to play the file. Then I realized that I was already playing a MP3 tune with MusicPlayer at that moment, which obviously is the cause of the error message. Stopping the MP3 lets Movie Player do its job normally, but in the end it would be nice to locate and translate that short & cryptic error message! (Don't remember triggering it with the Sharp ROM so I don't know what it looked like before)

KeyHelper:
The sticky shift key is IMHO causing more trouble than help, as already mentioned... I do realize that there is a learning curve involved, but I've disabled it for now. In fact I reinstalled my previous keyhelper.xml config file and everything is as I like it (accented characters & such).

USB auto-mount:
Works great. I've just purchased the required adaptor, and when I inserted it (alone) in the USB port of the zaurus, it was recognized by the system (at least, the Zaurus detected that something had been connected, thanks to the two grounded pins of the USB-host adapter).Then I inserted a USB memory key, and sure enough it showed up in the Launcher's file explorer. The icon's name is "Storage /dev/sda1" and since the filesystem on it was FAT I was able to browse its content. Using the applet in the bottom bar, I was able to "eject" it (i.e. it didn't show anymore in the file browser screen, and there was one less entry in the mtab file), but this didn't turn off the green light on the key, the way it usually happens when I umount it from my windows PC. Unplugging the key seems to work fine, though, I didn't get any crash or dramatic error message with dmesg.

Let me know what kind of test I must do with USB, if needed, or what potential problems to look for...

[euroclie]

Also for some reason the battery applet seemed not to be active after the first boot (or maybe I did mistakenly disable it afterward, but that would be very unlikely as it would have forced the Zaurus to reboot, which it hasn't). I just re-activated this applet using the "little blue dot" applet, and it works fine now. Did anyone else notice this?

[iamasmith]

euroclie, Thanks, good feedback on the multimedia apps. Haven't seen the battery applet disappear though.

Will take a look when I get the chance.

- Andy

[iamasmith]

USB auto-mount:
Works great. I've just purchased the required adaptor, and when I inserted it (alone) in the USB port of the zaurus, it was recognized by the system (at least, the Zaurus detected that something had been connected, thanks to the two grounded pins of the USB-host adapter).Then I inserted a USB memory key, and sure enough it showed up in the Launcher's file explorer. The icon's name is "Storage /dev/sda1" and since the filesystem on it was FAT I was able to browse its content. Using the applet in the bottom bar, I was able to "eject" it (i.e. it didn't show anymore in the file browser screen, and there was one less entry in the mtab file), but this didn't turn off the green light on the key, the way it usually happens when I umount it from my windows PC. Unplugging the key seems to work fine, though, I didn't get any crash or dramatic error message with dmesg.

Let me know what kind of test I must do with USB, if needed, or what potential problems to look for...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=73834\"][{POST_SNAPBACK}][/a][/div]

No that's good on the USB. The IOCTL to the usb storage device doesn't seem to fully remove the device. If you just used eject sda1 from the command line then you would see that the /proc/partitions still contained /dev/sda although /dev/sda1 would have been purged.

The eject command that the applet uses should trigger a graceful sync and dismount, however, and the next thing the patch to the applet does is rmmod the usb-storage driver so that when you disconnect and reconnect the device it gets /dev/sda and /dev/sda1 rather than being assigned sdb/sdb1.

That all sounds good then,

Andy

[iamasmith]

also, one thing i would like to see, is on the file browser, browse all files, not just ~/Documents.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=73828\"][{POST_SNAPBACK}][/a][/div]

Sorry slackwaresupport, thats part of libqpe. If we rebuilt that then we would lose any extra Sharp enhancements. I would suggest that you use TreeBrowser.

- Andy

[sriley]

Ahem, yeah, battery applet, memory applet, whatever.  Pay no attention to the man behind the typo.  

[iamasmith]

MusicPlayer 2.0:
The display in play view is a bit "corrupted": every text displayed is not properly erased when modified, and some of it doesn't display at the proper place right from the starts (horizontally). So it's impossible to read the tune's title, or the next tunes coming... all the digits (which I suppose are bitmaps) display fine, though. There's also a bit of the "Off" button bitmap scattered on the bottom left part of the display. All in all the display looks a bit messy, but otherwise the application works as expected, from what I could tell.

Right, this is really messy and needs sorting out... I'll try to take a look at this tomorrow. Thanks for the heads-up on this one.. I have to admit that the MusicPlayer and Movie Player, just got launched to check for Mojibake errors.. At the time I was going through reflash cycles so rapidly that I just couldn't push chunks of media at the Z on each cycle but I will try to find out what's going on.

Chances are though that this may be font related. May need to do a bit of hacking to get this to display well.

- Andy

[euroclie]

The new memory applet works fine, except that it seems that somehow the maximum size for the swapfile shrank back to 32Mb, whereas in the original version included with the alpha ROM, you could have up to 128Mb swapfiles, unless I'm mistaken. Otherwise, it seems fine.

Maybe a text change (from "RAM" to "HD") for the RAM radiobutton could be meaningful for C3000 owners? But then, the vast majority of Zaurus owners won't have hard drive, and I don't know how hard it would be to modify the radiobutton's name dynamically according to the device... So take this as a suggestion, not a request!

More about the Music Player 2.0 application: the mode button (normal, repeat, smart, etc...) between the display off button and the stop button isn't displayed at all. This is probably linked to the scattered button bitmaps problem I mentioned earlier. Tapping at the place where the button is supposed to be does work, though, as is reflected by the checkboxes in front of the menu entries in the Mode menu (which works as well).

[iamasmith]

euroclie,

Yes I intend to do something better for final release.. it was just to make it workable on the 3000... + I can change the text for the RAM setting to HDD based upon the checks that I put into the applet to detect an SL-C3000.

Sizes are default to Anton's original, all I did was to put some checking in for the model number and punch in a different location for /home/.swapfile to /home/zaurus/.swapfile to make it sensible for the 3000.

Expect more after my break.

- Andy

[euroclie]

MusicPlayer 2.0:
Chances are though that this may be font related. May need to do a bit of hacking to get this to display well.

Yes, this is probably font related, because it affects mostly the text. OTOH, there's the button problem as well... I know that this button has changed (new modes) between the previous version and the 2.0, as has the display (pictures can now be displayed, so the whole layout changed a bit), so maybe here lies the problem... Good luck to try and find out the cause, anyway!

I'm flying back home tonight, so this'll be my last contribution before tomorrow mid-day. Happy hacking to you all until then!

[iamasmith]

MusicPlayer 2.0:
Chances are though that this may be font related. May need to do a bit of hacking to get this to display well.

Yes, this is probably font related, because it affects mostly the text. OTOH, there's the button problem as well... I know that this button has changed (new modes) between the previous version and the 2.0, as has the display (pictures can now be displayed, so the whole layout changed a bit), so maybe here lies the problem... Good luck to try and find out the cause, anyway!

I'm flying back home tonight, so this'll be my last contribution before tomorrow mid-day. Happy hacking to you all until then!
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

OK, I botched the media player... please install this version instead..

[a href=\"http://cacko.biz/cacko/feed/musicplayer-C3000_2.0.0-1_arm.ipk]http://cacko.biz/cacko/feed/musicplayer-C3...2.0.0-1_arm.ipk[/url]

I missed the pics144 directory from the package and since there are more of them than in media player 1 (which the ROM build system overlays) and the applications controls are sized around the size of the pics that's why the fonts screw up... missing pics=missing positions  ... ah well gotta have these quirks just to remind you it's alpha1  

I have a sneaky suspicion that the exception on the MoviePlayer (about the sound device being in use) may be a little trickier.

- Andy

[iamasmith]

BTW: Anyone tried the built in mouse support?

It's sort of OK, bit of a gimmick though. Because it implements a mouse cursor on the Qtopia frame buffer it's no real use for XQT or SDL apps but someone may get a kick out of using it.

- Andy

[sriley]

Should any USB mouse work, or would it need to be a particular type?  Is there anything I'll need to do other than just plugging it in?