2. On/off from a suspend doesn't work again. Hitting home key, turns on my wireless card light right away, but it takes like 15-20 seconds (an eternity in Z time) to show the desktop. My previous beta3 tweaked setup, the on/off and home key turned it on almost instantly.
edit: Oh, the install flies by so could not get anything but an overall impression - very nice, informative. Noticed a long string of "adding apps from the sdcard" went by TWICE for some reason.
Lots to like about the whole installation. Niceties like a box which pops up to tell you it's okay to remove cf or card is great.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156798\"][{POST_SNAPBACK}][/a][/div]
I think these two may actually be related. I had been running pdaxrom beta3 for some time, and more recently I moved to a version of pdaxii13 (don't remember the exact build version, but it looks like I downloaded it on Feb 9).
On both of these, I had some apps installed to my SD card. The apps all worked, waking from suspend usually took 2-3 seconds, and reboots would take a minute or two (never actually timed it).
When I upgraded to pdaxii13 build 5.3.3, I also installed the "full package" of apps to my SD card. I figured I had the free space on the card and it would give me a chance to play with some of the apps I hadn't tried yet.
(BTW, really nice job on this, Meanie! Spectrum24 support and gobs of other wonderful fixes!)The first thing I noticed was that when I rebooted, there was a process running that seemed to be creating all the links to the SD-installed apps. At least that what I assumed it was doing. This took a looong time... possibly ten minutes. I got tired of waiting and came back when it was done. I also assumed that this was a one-time operation.
I played with the Zaurus, suspended it, and then tried to wake it some time later. It was unrespsonsive for an extended period of time. I reset it, thinking something wasn't working. It ran through the whole list of apps again when it rebooted. (I guess it wasn't a one-time operation, after all!)
Again, I suspended the Z and the next time I tried waking it I still wasn't getting a response. I decided to wait. Eventually it woke up. After a little investigating, it appears that the Z is ejecting the cards at suspend and remounting them upon waking. And at every remount, it runs through the entire list of SD-installed apps and it looks like it's recreating the links to those apps.
I removed the scripts for ejecting and remounting the cards. I'm already in the habit ejecting CF cards prior to suspending, and the SD card is never removed. I'm now back to a resume time of a couple seconds.
But I'm still curious what process is running through all the installed apps. And why is this feature now enabled, when I never noticed this before. I didn't have nearly as many installed apps previously, but even before I installed the "mother lode" I noticed significantly slower resume times with build 5.3.3 than I now have after disabling those scripts. I'm nearly positive that beta 3 was not processing all those files at every boot up and certainly not at every resume.
Is this "new" process necessary? And what, exactly, is it doing?
