PDA

View Full Version : A Few Nagging Problems...


BrentDC
06-19-2007, 02:12 PM
Hi everyone,

I've been experiencing a few nagging issues with my TX that I would really like to get resolved.

1) I have this problem that when Wifi is connected, and I launch Blazer it boots up so I can see the top toolbar, but it freezes. When Wifi isn't connected this problem doesn't happen. I find myself disconnecting before I launch Blazer, but sometimes I forget and it will freeze about 70% of the time.

2) I can only download with Blazer after a soft reset. I've heard that it is a cache issue, so I've tried flushing the cache with Resco Explorer before a download, but it doesn't help.

3) When opening an email with Versamail it will show a white screen for anywhere between 5 and 40 seconds before opening-a real pain.

It seems like that when I first got my TX I didn't have any of these problems, but over time they cropped up. Also do keep in mind I don't have any money to spend on software right now, so any fixes will have to be do-it-yourself or freeware.

Thanks,

cyberdude
06-19-2007, 02:17 PM
I can tell you right off that I experience the Blazer download problem as well. I don't download that often, so it's no biggie. I always assumed this had something to do with UnCache.

The versamail problem is definitely a dbcache issue and I've solved that by using OffFlush to flush the cache before starting VM.

_Em
06-19-2007, 03:10 PM
Sounds like you also have a software conflict that's keeping Blazer from handling downloads correctly. Check your associations in RE to make sure they're set up correctly. Also, check your notifications in RE to see what possible apps could be messing up your file handling.

BrentDC
06-19-2007, 03:28 PM
Sorry, I didn't clarify enough. Blazer handles the download, but it gives me a "not enough memory" error.

_Em
06-19-2007, 05:01 PM
Ah... then you'll want to read this thread (http://www.1src.com/forums/showthread.php?t=126305&highlight=blazer+download+memory) :)

Oh, and the white screen in VersaMail: this is the built-in DBCache flusher in action. I think OffFlush is faster and flushes more data, and doesn't have the bug in it that Palm's flush routine does, so it's probably better to use OffFlush than the default flush. However, you might find it faster to just do a soft reset if you've got your reset-aware list of apps small. If I soft reset, it takes 12-20 seconds, depending on what I have set to load; OffFlush takes around 35 seconds, and the built-in flush takes 45 seconds.

Hey... maybe we need an app that performs a reset and launches the app previously called to replace the built-in reset function :) The only place I can see this being a bad idea is when you have apps running in the background (pTunes, IM apps, etc.).

BrentDC
06-19-2007, 05:29 PM
I don't think it's dbcache issue with Versamail, and here's why. If I open an email it will take 5-30s to open, if I close the email it will take 5-10s to open another one, but if I open an email and hit one of the scroll buttons (top of screen) it will open the next email immediately. As for the Blazer download issue I think I have a solution (or at least I hope). A long time back I downloaded Dmitry's MemUnfragment, and since forgotten about it, well today I was looking over everything on my Palm and saw it was there so I deleted it then reset. I then tried DL something, and I successfully DL two things (only got one error message). But I've noticed another problem (nothing to do with memunfragment as I noticed it before I deleted it). I often use my palm one-handed so today I noticed this. When I hit the menu button and then hit the right hard button on the five-way nav it executes the command the "cursor" is on instead of scrolling over to the category of things. Does this make sense?

juggernaut#2
06-20-2007, 02:39 AM
1) I have this problem that when Wifi is connected, and I launch Blazer it boots up so I can see the top toolbar, but it freezes. When Wifi isn't connected this problem doesn't happen. I find myself disconnecting before I launch Blazer, but sometimes I forget and it will freeze about 70% of the time.
Do you use AutoWiFi and/or FixWiFi ?

I experienced the very same behaviour. I can confirm that it did depend on whether the connection was up or not during blazer startup. Checking on it I found that it does not really have to do with the amount of dbcache/heap before starting blazer. I used to check on dbache (using CacheInfoDA) before trying to start blazer and flushing if it were to less. If I had a WiFi connection open, the device would freeze while flushing, if not, it would go through.
Since Blazer does the same during startup (flushing dbcache if not enough, which accounts for the long startup time), I suspected something to interfere with the flushing process that dealt with WiFi, which in turn could only be FixWiFi and/or AutoWiFi since I do not use any other software that might hook up into WiFi (esp. not Versamail). Since I disabled both of them I d not experince this kind of problem any more.

I donīt know if this is caused by a bug within those apps or within blazer itself or maybe even within the OS, thatīs why I didnīt file in a bug report to pruss, esp. since a lot of other ppl seem to be using it without any problems. Youīre the first that reports exactly the same problem.

wozofoz
06-20-2007, 04:47 AM
Hi, I use Blazer about 4 hours every day.
I never use VersaMail.
I use FixWiFi and AutoWiFi and have no problems.
I never Flush or Reset before using Blazer and it takes about 15 secs to load then works very well.
I only download using Blazer (I don't have a computer) but I always download to SD Card then unzip and install with RescoExplorer.
I very rarely get a 'not enough memory' message which is wrong since I have over 1GB space on the card. If I simply retry the download it works.

Seems to me like you have a conflict problem or maybe VersaMail is the problem. There have been reports that the VersaMail upgrade at Palm is a good fix but this costs $10. You can read about it here (forum.brighthand.com/showthread.php?t=242582)
Hope it works out for you.

All the best, woz of oz

alt236
06-20-2007, 05:12 AM
Did you try setting a blank homepage on blazer?

BrentDC
06-20-2007, 10:03 AM
Hello,

1) I do have AutoWiFi, so I tried disabling it and launching Blazer with wifi connected, and everything worked fine, but I'll contact Alex (I tried launching 7 times).

2) What version of VersaMail comes in the update? I have v3.51 from the 700p and it didn't help (btw I had all of these problems before installing 3.51), also all of my PIM's are updated to the latest version.

3) My homepage is Google Mobile, what does that have to do with it?

wozofoz
06-20-2007, 11:28 AM
Hi, the update is v3.5 so it seems that is not the problem/answer.

I always have Blazer set to start on Bookmarks but as an experiment:
I set it to start on Homepage and changed my Homepge to Google Mobile then exited Blazer.
With AutoWiFi enabled I turned WiFi off then back on and launched Blazer.
No problems, everything worked fine.
Curiouser and Curiouser.

All the best, woz of oz

BrentDC
06-20-2007, 11:49 AM
But did you have WiFi connected, or just on, because my problem occurs when WiFi is connected. BTW thanks for your help!

juggernaut#2
06-20-2007, 04:28 PM
1) I do have AutoWiFi, so I tried disabling it and launching Blazer with wifi connected, and everything worked fine, but I'll contact Alex (I tried launching 7 times).
What you could do: Check if blazer freezes when connected with AutoWiFi set on only when dbcache is low or everytime.

I found that freezes only occur when dbcache is low. So to me it seems that AutoWiFi is disturbing something that has to do with flushing, (IF it is the culprit, that is). So this sequence works for me if AutoWifi is on: 1. flush, 2. start blazer. Then blazer will only reset when tapping on a text field on a website like 1src quick reply ...

BrentDC
06-20-2007, 06:33 PM
What do you mean by Blazer will only reset when you tap on a text field? Your palm resets when you do that? That's never happened to me.

_Em
06-20-2007, 06:55 PM
Only on javascript-backed text fields. It's a known bug in Blazer 4.3.

BrentDC
06-20-2007, 07:12 PM
What is an example of a javascript-backed text field? I use Blazer all the time (in fact I'm using it to submit this reply) and have experienced many reset, but never when using a text field.

_Em
06-20-2007, 07:43 PM
Hmm... I was going to use the 1src one as an example, but it appears to have been modified since I last had the problem -- the search field now shows as a standard form on Blazer.

wozofoz
06-20-2007, 09:15 PM
Hi BrentDC,
Sorry, yes I was connected (it was late :D ). Basically I reproduced your settings and no problems.
Maybe you and the other poster who has the AutoWiFi problem could exchange App lists to see what is common and maybe causing a problem. This may help Alex as well.

I also have never had a Crash using text fields is there a link to a discussion on this known issue? I would like to read about it.

I use mlvb (mlvb.net/?) for most of my browsing and write text within that so maybe that helps. I really don't know though.

All the best, woz of oz

juggernaut#2
06-21-2007, 03:32 AM
I also have never had a Crash using text fields is there a link to a discussion on this known issue? I would like to read about it.
Iīm sorry, I did a search and didnīt find the thread. Itīs one of those things you read and stuff in your mind somewhere, where it sits and can be recalled but not proved any more :)

But I can tell that whenever I am browsing 1src mobile with Blazer (which works fine) and tap on the "quick reply" field at the bottom of the screen I get an immediate reset right at the moment I tap on it. This doesnīt happen in NetFront, but on donīt get the "quick reply" field displayed there, so this doesnīt really help :)

It didnīt bother me too much so I never bothered to investigate. But I donīt want to hijack this thread :) (but if you do find something on this, pls let me know).

_Em
06-21-2007, 10:34 AM
I can no longer find the thread, and I can't produce the problem anymore, but I do remember when that was the case; about a year and a month ago, IIRC.