OESF Portables Forum
Everything Else => Model Specific Forums => Distros, Development, and Model Specific Forums => Archived Forums => SIMpad forum => Topic started by: albertr on June 18, 2005, 04:31:11 pm
-
Does anyone know who compiled it?
-albertr
-
Has anyone tried out the images? Are they newer then the 0.91 release or different at all? Any idea what source they were made from? All I can tell from the filenames is that they were recently compiled.
-
Does anyone know who compiled it?
-albertr
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=84828\")
Apparently, I should read better. [a href=\"http://devernay.free.fr/]http://devernay.free.fr/[/url] says it all.
-albertr
-
By the way, I updated these last week. They are still untested, but run on the 2.4 kernel (which is known to work).
To make simpad buttons work, you should follow the advices of geron:
QWS_KEYBOARD (in /etc/init.d/opie) has to be set to 'Buttons' now.
The touchscreen handling can be improved by setting
pthres pmin=400
in /etc/ts.conf
Fred
-
Fred, thanks for clarification. Do you have instruction on how to flash it? I think opensimpad.org was not updated for awhile and doesn't reflect the current state of 0.9 release and handheld's bootloader...
Since you already have a toolchain setup for building these, is there any chance you can build me opie2 lib with Till Harbaum's patch for cs3 register access? It doesn't seem that it has made it into opie cvs nor to 2.4.25 simpad kernel in OE.
-albertr
-
Nevermind, I'll set up a toolchain and recompile it.
-albertr
-
I installed the image from the .fr site - and I can login from a serial terminal - but I can't seem to start anything on the screen of the simpad? What am I missing? I tried starteing qpe as root - but nothing is showing up.
During booting the penguin logo shows up, and then the starting message. Once the init runs the screen clears and turns grayish / but qt never starts up on the screen. When I look at the ps process output it looks like qpe is not running.
I've flashed with the normal 0.9.x release candidate and everything works fine (except for know issues).
-
I've just installed the old 0.9.0-rc1 build from last December, and it runs on my Sl4. There're few problems, tho. Touch screen is not quite accurate, and I can't get any sound. The battery indicator seems to have a wrong window size - from all three digits it only seem to display first two, i.e. "10" instead of "100" percent. These are just ones that you'll notice right away. There're also a bunch of errors reported in logs which probably indicate some other problems. I'll try to set up a toolchain and build my own image sometime in next few days (time permitting).
-albertr
-
There're few problems, tho. Touch screen is not quite accurate, and I can't get any [div align=\"right\"][a href=\"index.php?act=findpost&pid=85346\"][{POST_SNAPBACK}][/a][/div]
The touchscreen handling can be improved by setting
pthres pmin=400
in /etc/ts.conf
[div align=\"right\"][a href=\"index.php?act=findpost&pid=84945\"][{POST_SNAPBACK}][/a][/div]
...and then recalibrate.
-
I've tried that already, it didn't help me with accuracy. My touch screen is a bit off at the bottom. What this paramater is supposed to change? Touchscreen pressure?
-albertr
-
I'm not sure exactly what it is *supposed* to change - sensitivity, I think. What it do for me, though, is to remove the "jittering" that made it impossible to use the onscreen keyboard. What would happen is the cursor would suddenly jump up the screen about an inch or so every few seconds and bumping this number up prevented that from happening.
I have heard people setting it as high as 2000. I think I used about 50 for a while but I eventually settled on 400, same as the original poster.
I haven't heard of anyone with other accuracy problems until now.
-
Tim,
Thanks for explanation. I'll try different values and see if it could help. On the other side, if it's not a known issue, then it might be a hardware problem with my SL4.
-albertr
-
I have the same problem with the battery displaying the wrong value (only 10 percent of the actual value). It didn't have that problem with windows on it, so I'm guessing it's something to do with the new build...
-
I believe the battery applet problem might be a sizing problem - it seems to display two first digits from three, i.e. "10" instead of "100", thus last digit does not fit in the screen.
The other issue I noticed right away is cracking sound problem. Also there's a bug when mounting a CF card it updates /etc/fstab, but forgets to specify a mount point, i.e.:
instead of
/dev/hda1 /mnt/cf auto defaults 0 0
it writes out
/dev/hda1 auto defaults 0 0
The other issue is with shutdown. When I do `shutdown -r now` it suspends before rebooting. It looks like some process (opie?) puts device into suspend when is being killed on shutdown.
-albertr
-
It's not a sizing problem with me, considering it tells me my battery is critical when it's actually full...
-
Insteresting... It shows "10" for me, but it's not critical level. I have a warning set @ 10%, but it doesn't warm me. Also, the battery bar indicator seems to be consistent with "two digits" theory. I believe at 10% charge it should show appox. 1/10 of the bar, right? Mine shows full bar. There must be something different between our setups... I'm running 0.9.0-rc1.
-albertr
-
Ahh, scratch it. Now I started getting warnings too. On the other hand graphical indicator still shows full bar. Go figure...
The other issue I have is screen sometimes gets corrupter after suspend. I'll try to put an apm.d script to restore it by apmd on resume, will see if it could help.
-albertr
-
I am running the same build,
The funny thing is, yeah, like you said, the bar shows approximately the correct amount, all the way full when it's at "10%" and down respectively.
Mine is at "6%" right now...and the bar is about 60% over...
Did you get yours from the guy in Arizona, too? From ebay...
If so, maybe he has a batch of slightly weird ones...with a bit different hardware...
Or maybe nobody else is running this build? Or just didn't notice...
Okay, enought guesses for now...
Oh, and does that apmd thing work? I'd like to not have to rotate the screen to clear all that junk off
-
I think most of these are known problems and just reflect the current state of play of Linux on the Simpad.
The battery thing is a sizing problem with the last digit (and the "%" IIRC) dropping off the edge of the screen.
The battery warnings I only get on resume and I think are due to incorrect battery calibration settings (maybe in the kernel?). Some people have charging weirdness for the same reason.
The screen corruption at resume is a known problem.
The noise before the first suspend is a known problem (although in my case it remains fairly noisy even after that).
It is probably worth having a look at the fora at opensimpad (http://opensimpad.org/) where you'll see some discussion there. That forum has been shutdown in favour of this on now, though (but still worth looking at the history).
-
Yeah, I looked in the old forum, and there were messages saying that the 10% problem was from a bad battery...which it is most definitely not...
-
Yes, I've got mine from the same guy on Ebay. It looks brand new except for scratches on the outside box. Maybe a refub? Who knows...
apmd script seems to be helping, at least I didn't see the screen corruption since then, but it wasn't long since I put it in, so jury is still out on this one. The idea and script itself was posted by Till Harbaum on the list a while ago. Here's the script:
#!/bin/sh
#
# save video contents in ram disk during suspend
# this meant to be ran from /etc/apm/event.d
case "$1" in
suspend)
cat /dev/fb/0 >/tmp/video_suspend
;;
resume)
cat /tmp/video_suspend >/dev/fb/0
rm -f /tmp/video_suspend
;;
esac
My understanding is that this code is implemented in opie2 library, but for some reason it's not working all the time on simpad (timing issue?).
I believe the charging on/off problem was discussed on the list a while ago too, and the solution was proposed to reduce the minimum voltage detection from 12V to 11V, since not all power adapters supply > 12V all the time. Too bad that this patch also didn't seem to make it into official opensimpad builds.
The battery applet problem is new to me. But if it's as simple as miscalculated window size, it should be rather easy to fix.
The cracking noise problem is annoying. I'm getting it before and after suspend too. I'll try to rebuild the kernel with all recent patches which didn't make it into official builds, and see if what's going on.
-albertr
-
Re: battery applet
Here's a snipset from opie' changelog:
2004-11-26 Opie 1.1.8
.....
Fixed Bugs
.....
* n.a. - Battery Applet - fix sizing of battery info popup (drw,mickeyl)
-albertr
-
Ha-ha, that battery applet is a bad boy, is he not?
Here's another one:
2005-??-?? Opie 1.2.1
....
Fixed Bugs
.....
* #1546 - Battery applet popup is not always large enough to show jacket remaining info (skyhusker)
-albertr
-
I guess this is the sort of stuff I should work on fixing
If I could only get USB working...
-
albertr, could you please post a list of your patch? I can try to maintain a stable 2.4 kernel with such missing features.
Hopefully the 2.4.29 pcmcia bug will be stupid enough so I can fix it
-
*sigh* You really don't like the OE people, right?
Is it forking time again or why do you insist on maintaining your stuff seperatly?
*shakes head in grief and sorrow*
-
I like OE, it's just a bit too complicated and tries to do too much things at once.
If you want, I can keep in sync with the simpad 2.4.25 kernel hosted in OE CVS, but I don't really want to have to deal with everything else.
-
I don't really have any patches other than ones already in OE and those posted on the list by Till H which sadly were not included in OE.
Anyway, if there's any interest, I can email them to the list again and hopefully they won't go unnoticed this time?
I don't really have experience with OE, I've just installed it last night and I like it so far. I've already built opensimpad opie-image, however it doesn't work quite yet I'll try to take another look sometime this weekend.
-albertr
-
Ok, since the latest & greatest opie runs on my SL4 now, here's a preliminary feedback comparing it to 0.9.0-rc1 from last December:
- battery applet is fixed.
- don't know what has been changed, but now my touchscreen is accurate! It was a bit off at the bottom of the screen in 0.9.0-rc1.
More to follow... But so far it looks great!
-albertr
-
Please use our new bugtracker for patches now. Since we switched from RT to bugzilla we actually make use of it
http://bugs.openembedded.org (http://bugs.openembedded.org)
-
http://devernay.free.fr/hacks/opensimpad/20050620/ (http://devernay.free.fr/hacks/opensimpad/20050620/)
Just wondering if there are any install guides available
-
is there any way to get a *.bin- file for flashing via "serload" ? like the 0.8 opie ?
cheers
Mike
-
is there any way to get a *.bin- file for flashing via "serload" ? like the 0.8 opie ?
cheers
Mike
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86470\"][{POST_SNAPBACK}][/a][/div]
Yeap, that would be useful alright!