Author Topic: Ok, No More Major Issues In Cacko 1.22?  (Read 23326 times)

petya

  • Jr. Member
  • **
  • Posts: 61
    • View Profile
Ok, No More Major Issues In Cacko 1.22?
« Reply #15 on: January 10, 2005, 02:49:42 pm »
After i put the proper init string in the init string section, it still hand with initializing modem, and the phone doesn't do anything. Could you recommend me some stuff to read about the topic to make it work, from command line, etc, i am familiar with linux, but just not with bluetooth. The phone is motorola V525.

petya

  • Jr. Member
  • **
  • Posts: 61
    • View Profile
Ok, No More Major Issues In Cacko 1.22?
« Reply #16 on: January 10, 2005, 03:00:56 pm »
Send AT&FX1E0V1
Send CR
Delay 1
Send at+cgdcont=1,"IP","internet.vodafone.net";^sgauth=1
Send CR
Send ATDT*99***1#^m
Send CR
Delay 1
End

here is the palmos chatscript, i hope this helps

flens

  • Newbie
  • *
  • Posts: 14
    • View Profile
Ok, No More Major Issues In Cacko 1.22?
« Reply #17 on: January 10, 2005, 05:23:47 pm »
Hi,
1. Is it possible to add some configurations for debugging the WLAN-communication?
2.Is it possible to at some constaints, that the light doesn't suspend after 0 or 1 second?
Thank you flens

Christian Paulsen
http://auu.homelinux.org
c760 cacko X/QT

solighten

  • Newbie
  • *
  • Posts: 43
    • View Profile
    • http://
Ok, No More Major Issues In Cacko 1.22?
« Reply #18 on: January 11, 2005, 04:27:02 am »
Hi,

the issue with charging is in fact very strange.

When my Z is turned off the charging always works fine. It is only an issue when the Z is turned on and connected to the power supply. I expect that under these circumstances the power to be used for charging and for the device itself. When charging is done the light should go off and the power should be used only for the device itself. I have an iRiver mp3 player which shows exactly this behavior.

My Z when I bought it with the original Sharp Rom usually didn't turn off the charging light when it was switched on and connected to power. With Cacko 1.21b the light usually went off and now with Cacko 1.22 it is always on when the Z is turned on and connected to power.

I also fear that my battery doesn't like it to be charged all the time and I now think about what I should do. If the problem persists I will probably don't use the Z with the power line connected but that will make everything difficult.

Any suggestions?

Kind regards, Jan
SL-C860 - PdaXrom 1.1.0r197
2GB SD XStore 2GB CF SanDisk
Wlan D-Link DCF 660W

petya

  • Jr. Member
  • **
  • Posts: 61
    • View Profile
Ok, No More Major Issues In Cacko 1.22?
« Reply #19 on: January 11, 2005, 05:12:51 am »
Hi! qtredesktop starts in qvga mode if i launch it from icon, but it starts in vga mode if i start it from command line. This is on sl-c760.

tovarish

  • Sr. Member
  • ****
  • Posts: 297
    • View Profile
Ok, No More Major Issues In Cacko 1.22?
« Reply #20 on: January 11, 2005, 05:18:14 am »
is is also possible to release a kernel without the sharp splashscreen, i like to see how the kernel is loading. alternately could you release the kernel source or patch so that i can compile it myself.

thanks
tovarish

maslovsky

  • Hero Member
  • *****
  • Posts: 1426
    • View Profile
    • http://my-zaurus.narod.ru
Ok, No More Major Issues In Cacko 1.22?
« Reply #21 on: January 11, 2005, 08:14:09 am »
Quote
is is also possible to release a kernel without the sharp splashscreen, i like to see how the kernel is loading. alternately could you release the kernel source or patch so that i can compile it myself.

thanks
tovarish
This is a quote form Cacko ROM home page:

Quote
Kernel source used in Cacko ROMs is available here: http://developer.ezaurus.com/sl_j/source/source_dl.htm

Tarballs of patches to the kernel and configuration files are available here:

cacko-1.22-kernel.tar.gz

maslovsky

  • Hero Member
  • *****
  • Posts: 1426
    • View Profile
    • http://my-zaurus.narod.ru
Ok, No More Major Issues In Cacko 1.22?
« Reply #22 on: January 11, 2005, 08:25:53 am »
Quote
My Z when I bought it with the original Sharp Rom usually didn't turn off the charging light when it was switched on and connected to power. With Cacko 1.21b the light usually went off and now with Cacko 1.22 it is always on when the Z is turned on and connected to power.
So, this means that currently it behaives exactly like it did with original Sharp ROM, which means it's most likely OK for the battery.

Stubear

  • Hero Member
  • *****
  • Posts: 1164
    • View Profile
    • http://
Ok, No More Major Issues In Cacko 1.22?
« Reply #23 on: January 11, 2005, 08:42:40 am »
Quote
Hi! qtredesktop starts in qvga mode if i launch it from icon, but it starts in vga mode if i start it from command line. This is on sl-c760.
A lot of the apps not specifically designed for the Cxx0 series do this.

To stop the icon starting in QVGA, tap-hold the icon and uncheck "Display with magnified screen"

Stu
SL-C1000, Hand converted to English with Japanese Input
Running X apps via X/Qt
iRiver USB host cable; Diatec P-Cord usb power cable (extendable); Acro's Reel Cable USB (A to A, B, Mini-B,  & Mini-B 8pin); GreenHouse 1Gb PicoDrive+; 2x256Mb Hagiwara SD cards; 128Mb Transcend CF card; 512Mb PQI CF card; AmbiCom WL1100C-CF 11B WLAN card

petya

  • Jr. Member
  • **
  • Posts: 61
    • View Profile
Ok, No More Major Issues In Cacko 1.22?
« Reply #24 on: January 11, 2005, 11:06:44 am »
sorry, i have no such thing, when i tap and hold, i got a detalis windows, wth the fields: name, type, comment, and a checkbox to exec with root privileges

cmpayc

  • Newbie
  • *
  • Posts: 27
    • View Profile
Ok, No More Major Issues In Cacko 1.22?
« Reply #25 on: January 11, 2005, 01:49:59 pm »
Hi ALL,

my SanDisk CF-Wifi Card is also recognized as "Zcomax Xi-325H 200mW", but seems to work properly :-)

Another prob is from my point of view much more important.

After flashing Cacko 1.22 (Lisa) and installation of VNC-Server from Cacko-feed the VNC-client on my XP-Box does not respond to keyboard and mouse (although I can see the picture from Zaurus).

The same configuration works well at Cacko 1.21 (Elen) Hotfix B.

Best regards

Cmpayc

stupkid

  • Hero Member
  • *****
  • Posts: 578
    • View Profile
    • http://
Ok, No More Major Issues In Cacko 1.22?
« Reply #26 on: January 11, 2005, 02:14:23 pm »
Did you reboot the Z after installing the VNC server?

Zaurus SL-C3200 pdaXii13v2 5.5 / Ambicom WC1100C-CF / Socket Bluetooth Rev G


OpenMoko FreeRunner - Running Tweaked OM2008.x Image

Flandry

  • Jr. Member
  • **
  • Posts: 77
    • View Profile
    • http://
Ok, No More Major Issues In Cacko 1.22?
« Reply #27 on: January 11, 2005, 04:34:55 pm »
I really like the improvements and simplifications in this Rom version.  The things that (i think) should be fixed are:
-D-link wifi properly detected (already described in this thread)
-The confounded backlight issue, which was never resolved in the previous version and continues to be a problem.  I often prefer the backlight set to the lowest level, but in this setting it will do unexpected turn-off kind of things (there was a thread just the other day describing this in full, i did so a few months ago)
-There are some issues with kino that may or may not be suitable for a hotfix.  Probably the easiest or least intrusive of these is that when kino is playing back, all the key strokes are directed to it, even if it's in the background.  This makes eg browsing a bit difficult, as the arrow keys don't work as expected.
-Maybe it's just me, but it seems like the expected dtm filename case was changed from 1.21.  Not sure how that would have happened, but i had to change the case of my old data files so they would overwrite the new ones.

I've experienced some really strange suspend/screen save issues, especially while kino is playing audio files, and (seperate problem) setting kino to enable underclocking during audio playback really FUBARs my z until it's rebooted (not to mention that it doesn't play smoothly while underclocked, anyway).  This is of course easily enough resolved by not checking that box; i just thought i'd mention it.

Future stuff:
I've been using 1.22 long enough now to have a wishlist for the next version (yeah, i know...never satisfied).  First and foremost is the browser and email apps.  The included email client is pretty much worthless as it doesn't support enough options (secure connections, for example) for me to use it.  I installed OM/Pi for the first time right after flashing, and i haven't found any reason not to replace the default email app with it.  Excellent program.  I can understand the hesitation to replace the other (almost equally inept) default PIM apps because of the syncing and dtm issues, but i don't believe that's an issue for email.

And browsers... this is an area that has me confused.  When i got my z from a previous owner seven months ago, it had opera 7.30 installed.  Now, the brand-spanking-new 1.22 rom has 7.25, which (still) has issues that a mature browser just shouldn't have (don't get me started on netfront).  Why is a version months old the standard for our shiny new ROM?
Edit: Okay, i see.  After reading a thread in the security forum it seems clear that the newer versions of opera are flaky.  Too bad.  It could use some fixing.
Kino2... what an improvement in multimedia capabilities it represents!  Nevertheless, the interface is awkward, and adding files to a playlist seems to take a very long time.  Adding a directory to a playlist only works if the directory depth is one, which isn't how most of my media library is arranged.  And it's more sluggish than the old player was.  So it's a huge step in the right direction, especially in consolidation of capabilities, but a bit rough around the edges.  But wow, that video playback is purdy!

So now you have my input... unsolicited as it may have been . 8)
« Last Edit: January 11, 2005, 05:50:55 pm by Flandry »

kbranch

  • Jr. Member
  • **
  • Posts: 72
    • View Profile
    • http://
Ok, No More Major Issues In Cacko 1.22?
« Reply #28 on: January 11, 2005, 07:32:30 pm »
For anyone that's concerned about the battery overcharging, there's a very low level protection circuit in the battery itself that would prevent any damage regardless of what the Zaurus is doing.

Lithium Ion batteries will emit a flammable gas if they're overcharged.  Shortly after they start doing that, they become hot enough to ignite that gas.  With such serious consequences, there's no way a company would let it overcharge because of a software problem.  Even if the protection circuit were to fail, it should be designed to fail open so that the battery just stops working.
« Last Edit: January 11, 2005, 07:33:10 pm by kbranch »
Open source RTS.  It's still in the very early stages, so testers are quite welcome.

ev1l

  • Hero Member
  • *****
  • Posts: 608
    • View Profile
    • http://bbshuffle.blogspot.com/
Ok, No More Major Issues In Cacko 1.22?
« Reply #29 on: January 11, 2005, 10:51:00 pm »
Quote
Lithium Ion batteries will emit a flammable gas if they're overcharged.  Shortly after they start doing that, they become hot enough to ignite that gas.  With such serious consequences, there's no way a company would let it overcharge because of a software problem.  Even if the protection circuit were to fail, it should be designed to fail open so that the battery just stops working.
Sounds like a pocket-load of fun. And remember: disabling the overcharge detection circuit might constitute an act of terrorism in your country