1.1.0beta4 Stable For C760

[VirtusRex]

Hello,

I've been thinking of upgrading my c760 from beta1 to beta4. Could someone tell me if the current beta4 rom is stable and works with c760?

Also, what are the benefits of beta4 compared to beta1?

Thanks,

VirtusRex

[Sorearse]

Hello,

I've been thinking of upgrading my c760 from beta1 to beta4. Could someone tell me if the current beta4 rom is stable and works with c760?

Also, what are the benefits of beta4 compared to beta1?

Thanks,

VirtusRex
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143285\"][{POST_SNAPBACK}][/a][/div]

My advice is to stay with Beta 1. If you're going to upgrade, I found Beta 3 to be most stable on my 760. The advantages of Beta 4 don't outweigh the pain of charging problems, spurious suspend issues, keyboard issues and a lot of broken settings applications.

Pain....
I've been using Beta 4 since it was released, and also found that my keyboard responsiveness has become degraded, or messed up somehow. This may be just hardware related and coincidence, but some keys (E, R and space) require a harder press, whilst others seem to repeat too quickly so that i get double characters.
The main issue was with charging - it wouldn't seem to charge sufficiently and on battery power wouldn't last more than a few minutes.  This was resolved at least partially by going into the DM menu and using the manual charging option to get more charge into the battery, then flash the new higher value to the flash memory. This now allows the battery to charge normally.
However, I still face intermittent power suspend, and then having to wait for a minute before being able to power on again. Then it will suspend again repeatedly until I can get mains power connected.


The good stuff...
2.6 Kernel
uboot
Alsa


I use wpa_supplicant to control my Ambicom wi-fi card - works OK. But, when roaming, I need to quit wpa_supplicant, then use the CF card applet to eject and insert, then re start wpa_supplicant in order to connect to a new network - very fiddly, and a complete pain when travelling on the subway because hotspots only exist in the stations. By the time I've finished these fiddly steps, the train has moved out of the hotspot !

My overall feeling is that my 760 is less of a machine than it was using Beta3. I haven't yet upgraded to 121, I'm waiting for something more stable, so for now I'll live with my Beta 4 setup.

Regards

Sorearse

[VirtusRex]

Thanks for the advice Sorearse.

VirtusRex

[donquixote]

My overall feeling is that my 760 is less of a machine than it was using Beta3. I haven't yet upgraded to 121, I'm waiting for something more stable, so for now I'll live with my Beta 4 setup.

I recommend at least upgrading to beta121 if you have 4. It's quite simple to do and it is way more stable. It's still not perfect, and a lot of issues are still there, but I highly recommend switching to 121. However, if you have beta 1 the do not by any means upgrade to beta 4 or 121!!

dq

[Sorearse]

My overall feeling is that my 760 is less of a machine than it was using Beta3. I haven't yet upgraded to 121, I'm waiting for something more stable, so for now I'll live with my Beta 4 setup.

I recommend at least upgrading to beta121 if you have 4. It's quite simple to do and it is way more stable. It's still not perfect, and a lot of issues are still there, but I highly recommend switching to 121. However, if you have beta 1 the do not by any means upgrade to beta 4 or 121!!

dq
[div align=\"right\"][a href=\"index.php?act=findpost&pid=143573\"][{POST_SNAPBACK}][/a][/div]

Thanks for the advice, donquixote. By coincidence, last night I decided to upgrade to 121, but I got stuck after the uboot install. The emergency system boots OK, but with the necessary update files on a CF card, the boot process ends with the following message and leaves me at the command prompt

Code: [Select]

Processing /etc/profile... Done

-sh3.00#
So I proceed by manually to try to run autoboot.sh on the CF card, but my 760 then freezes when I try to view or access the contents of the CF card. However, after rebooting normally into beta4, I can happily see the contents of the CF card, which is FAT16 formatted, and contains autoboot.sh, kernel.img and rootfs.img in the root folder. Has anyone else seen this issue ?

Tried many times, and remembered to remove the SD card too. I'm going to download and re-extract to the card, then if necessary try another card. I'm determined to get 121 working soon !

SA

[Sorearse]

OK - fixed it. Here is what I did...

1. Took out the CF card before booting into the emergency system (hold down OK whilst connecting power, waited for approx 10 secs).
2. Answered no to the question about proceeding with the installation.
3. Inserted the CF card containing the kernel image etc.

4. Entered the following at the prompt

Code: [Select]

cd /mnt/cf
./autoboot.sh /mnt/cf
Then sat back and watched the 760 regenerate itself to r121 !

First impression - I need to fix apm, as the Z 760 freezes with a blinking cursor in the top left whenever I try to suspend. I saw a fix somewhere - will work on that next.

Also need to install wpa_supplicant again - will report back on wireless fun later.

Sorearse

[Sorearse]

...
Also need to install wpa_supplicant again - will report back on wireless fun later.

Sorearse
[div align=\"right\"][a href=\"index.php?act=findpost&pid=144132\"][{POST_SNAPBACK}][/a][/div]

Apm is still an issue. Every time my Z suspends, I can't wake it up again, just get a cursor blinking in top left corner. Got it working once only (by random chance it seems), but after next reboot can't suspend again. Seems intermittent, but 95% of the time it needs a battery yank and full reboot. I tried installing a newer version of APM as suggested in this forum, but this did not solve the issue. Does anyone else have this issue with 121 ? I wondered if it was somehow related to the D+M menu settings to do with battery AD values stored in the flash, but I'm only guessing.

Wireless has been more fruitful. I use wpa_supplicant to connect to my WPA access point, and other APs when roaming around. The same issue occurs as with beta4. To successfully connect, the card needs to be ejected, inserted (not physically, this can be done with pccardctl eject and insert commands), then wpa_supplicant needs restarting, along with dhcpcd. I wrote a small script to do these steps, but it would be better if these could be executed whenever the network comes up. I'm not an expert in init scripts, so could anyone suggest how I might proceed with this ? I want to simply start my network card, start wpa_supplicant and begin surfing without any manual intervention. Then my Z can pull down podcasts, email etc and start being useful again  

Regards
Sorearse