New Releases Bugs/issues And Fixes (plz Post!)

[scheck.r]

--------------Sound----------------
If OSS driver is selected in xmms, the volume CANNOT be controlled from xmms and the volume applet in fbpanel is too sensitive, not linear enough, sound becomes audible at 2/3 of the max.
If ALSA driver is selected in xmms, volume CAN be controlled from xmms and it's easier to adjust since it increments by 2%. However, volume applet and volume cursor in xmms are no more independent like in beta3.
If you move the volume applet with the stylus you can see the volume cursor in xmms changing also. Volume is also too sensitive with ALSA driver. If you do the reverse i.e if you change volume from xmms, volume settings are not updated in the fbpanel volume applet and neither in zmixer, zmixer and the volume applet keep there previous settings(even if volume is lower).

But at least on akita, putting speaker volume to zero in Zmixer works.


And sound is stuttering like crazy when moving volume control panel with the stylus.

[scheck.r]

Using mplayer from the cli(from r198 feed), I don't have any problems(after adjusting zmixer of course) and I am using OSS default driver. I CAN adjust everything separately(speakers and headphones), tried with mp3 and mpg.

[wellswang]

One more thing: SCIM cannot run in r197/r198. It seems to have something to do with the gtk library. Have read an old post that installing a Beta3 gtk lib will make it work. But this will come with a bigger cost that many newly updated gtk stuff in the new feeds may not run.
I know this is not a bug, and things like SCIM probably have to be recompiled. I did try to compile SCIM before. It ended up with tons of painful errors ...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159319\"][{POST_SNAPBACK}][/a][/div]

SCIM (from beta3 feed) works fine on my C3100 with r198
(scim , scim-pinyin)

I modified ~/.xinitrc, added :

Code: [Select]

scim -dbefore openbox/matchbox started

and modified /etc/profile , added:

Code: [Select]

export GTK_IM_MODULE=scim
export QT_IM_MODULE=scim
export XMODIFIERS="@im=SCIM"

====

Ctrl+Space to call up the SCIM in applications

and I found it was using XIM protocal (not GTK IM MODULE)

so I think

Code: [Select]

export XMODIFIERS="@im=SCIM"is the most important configuration.

[ZDevil]

Thanks, wellswang.
I have already done exactly what you suggested, also with "gtk-query-immodules-2.0 > /etc/gtk-2.0/gtk.immodules" after installation. I was also using this in all my old setups.
But scim stops working in 860@r197 . Ctrl-Space doesn't call the program in leafpad or GTKTerm2. Neither can i use the scim config tool (scim-setup) to set keys, etc (showing segfault in terminal). Reinstalling them doesn't help.
Can someone using r197 verify this?  

[wrc4]

Thanks, wellswang.
I have already done exactly what you suggested, also with "gtk-query-immodules-2.0 > /etc/gtk-2.0/gtk.immodules" after installation. I was also using this in all my old setups.
But scim stops working in 860@r197 . Ctrl-Space doesn't call the program in leafpad or GTKTerm2. Neither can i use the scim config tool (scim-setup) to set keys, etc (showing segfault in terminal). Reinstalling them doesn't help.
Can someone using r197 verify this?   
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159357\"][{POST_SNAPBACK}][/a][/div]

I can't run scim-setup on r198. Do you have this problem? Are you using the scim from old beta feed or built by yourself?

[ZDevil]

I use the packages from the r121 feeds, which are supposed to be just the same as the r197/198 feeds.
And yes, scim-setup segfaults and fails to launch. And I don't seem to find its icon in the program menu (i am using icewm).
If my C3200 does not arrive today, then I will have to flash my C860 back to Beta3 to get the working environment back.

[wrc4]

And yes, scim-setup segfaults and fails to launch. And I don't seem to find its icon in the program menu (i am using icewm).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159367\"][{POST_SNAPBACK}][/a][/div]

So, how difficult it is to re-complie scim? I tried it on my pdaXrom build environment but ended up with the following error:

checking for /usr/share/sgml/docbook/xsl-stylesheets/html/tldp-html.xsl... configure: error: cannot check for files existence when cross compiling

Does this mean scim is not friendly to cross-compiling? I'm using the 1.4.5 source with the following (simple) switches:

CC=armv5tel-cacko-linux-gcc ./configure --host=armv5tel-cacko-linux --build=i686-linux

[wrc4]

Issue on Akita:

There seems no bvdd support:

# modprobe bvdd
FATAL: Module bvdd not found

[ZDevil]

And yes, scim-setup segfaults and fails to launch. And I don't seem to find its icon in the program menu (i am using icewm).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159367\"][{POST_SNAPBACK}][/a][/div]

So, how difficult it is to re-complie scim? I tried it on my pdaXrom build environment but ended up with the following error:

checking for /usr/share/sgml/docbook/xsl-stylesheets/html/tldp-html.xsl... configure: error: cannot check for files existence when cross compiling

Does this mean scim is not friendly to cross-compiling? I'm using the 1.4.5 source with the following (simple) switches:

CC=armv5tel-cacko-linux-gcc ./configure --host=armv5tel-cacko-linux --build=i686-linux
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159368\"][{POST_SNAPBACK}][/a][/div]

The Docbook thingy is tricky. One thing is the documentation is (again, alas!) confusing. I got to download the source and extract it in the correct paths in order to compile quite a few apps (onboard in Z). I can go back to my mac at home to fish the pointer tonite.
But i remember i got past that and got lots of other make errors.

[ZDevil]

Good news!

Screen rotate DOES work for C860@r197!  

This morning i was reading an ebook with JustReader on the train. Then I use the rotate function of JustReader, then flipped the machine into portrait mode, thinking that the screen rotate in the build or icewm was broken.
But ...
No, it worked!
The only small step i had missed before is to pull the screen all the way down to the keyboard.
Perhaps i am mistaken, but it seems for C1000/3000/3100/3200 you just have to turn the screen to rotate the display.
Also in the older Cxx0 devices there are two small "buttons"  along the hinge and the swivel and there is only on Cxk switch which does the same thing.
I remember it seems to be the tiny button above and between the number keys "1" and "2" that does the job...?

And it seems my build of icewm 1.2.30 can handle rotate well, in contrast to the current 1.2.20 in the feeds. Maybe someone can verify that.  

[tombraider]

This fix was in the other thread posted by ZDevil.  It fixes the mounting of cf and sd cards:

Code: [Select]

II. Fix the card mounting issue (thanks to louigi600 for providing this)
You will notice that upon reboot after flashing, both SD and CF are not mounted.
To fix this, edit /etc/fstab. Use your favorite editor to do so.
Open the file, in the lines for /dev/hda1 (for CF) and /dev/mmcblk0p1 (for SD), change
CODE
noauto,owner

to
CODE
owner

Save the file, exit the editor.
Reboot.
Then the cards will be mounted automatically.

Hi pdaX folks,

Chero and I have taken up the job to make new documentation for the pdaXrom releases.
Chero has been working on a template tree of notes, and I am focusing more on taking notes on the new releases.

InSearchOf (as well as the other devs who help building) has been doing great job and he promises to release a public build EVERY OTHER WEEK.   
This can be a fantastic idea, IF ...
1) bugs and known issues are tracked systematically
2) fixes are found AND incorporated into the next new build(s)

Although there seem to be quite a few new brave testers being put off by the persistent problems, this shouldn't stop us to make things even better!

So, now, in order to help the development of pdaX, the dev team, and ultimately you the users, it would be great if ...
1) I (and Chero) can keep track of reports of bugs/issues and fixes;
2) Users/Testers can contribute to the refinement of the builds by:
-- submitting reports to the pdaXrom bugtracker (the link in the pinned post is no longer valid),
-- thru PM or emails to me (dvm DOT zaurus AT gmail DOT com),
-- or right in this thread and/or the threads for the new releases. 

Then I can keep track of things in these three sources.

I am preparing a new section Chero's tree: Known issues & solutions in the latest version.  There I will put as much useful information as i can find. So if you have got something to say and to fix, please do drop me a line!

As for the new builds, many of us still spot old problems as in the older releases. So if you manage to recall or recover the old fixes (as in Beta3, Beta4, r121 or even r1xx), please go ahead and tell me!

Admittedly I am no linux guru or hacker, but I enjoy sharing and dare to work against my holy RL by wasting time typing out simple short notes to help myself and others. The Documentation will surely become more complete and useful with your contributions.

Come, join us, brave pdaXromers! The making a perfect pdaXrom release is an everlasting battle against the dark side of M$ Lose Mobile. Let's roll out and conquer the small world of dinozaurus!

[To InSearchOf: no, it wasn't meant to be angry, but aggressive!   ]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159155\"][{POST_SNAPBACK}][/a][/div]

[ZDevil]

No, it's not my fix. louigi600 found it.

[tombraider]

I know,  i thought I said it was "posted" by you in that thread....on the other hand,  maybe I just wasn't very clear in how I phrased it.    
I wanted to give you credit for posting it.

Sorry for the misunderstanding.

No, it's not my fix. louigi600 found it.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159445\"][{POST_SNAPBACK}][/a][/div]

[Fushnchupsh]

@Sheck.r
For your symbol wifi card, did you have to drop the firmware file someplace?

Thanks
--Fish

[ZDevil]

@Sheck.r
For your symbol wifi card, did you have to drop the firmware file someplace?

Thanks
--Fish
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

It's in this thread:  
[a href=\"https://www.oesf.org/forums/index.php?showtopic=23753]https://www.oesf.org/forums/index.php?showtopic=23753[/url]