PYKL3 version 2.3.1 for Android released

Joined
Dec 12, 2010
Messages
111
Location
On the Llano Estacado in West Texas
PYKL3 Radar version 2.3.1 with some minor cosmetic tweaks and a few nuisance bugfixes has been released to Android Market. Still waiting on 2.3 to show up on Amazon App Store.

The upgrade is free to anyone who has purchased PYKL3 Radar back to version 1.0

Joe
 
VERY minor thing I noticed.....

If you turn on SFC obs, and then pinch to zoom out, and then pinch to zoom back in, it will force close.

I'm using a Garmin-Asus Garminfone with Eclair on it. Not a horrible thing, but thought you'd like to know.

Tim
 
VERY minor thing I noticed.....

If you turn on SFC obs, and then pinch to zoom out, and then pinch to zoom back in, it will force close.

I'm using a Garmin-Asus Garminfone with Eclair on it. Not a horrible thing, but thought you'd like to know.

Tim

Is it consistently happening? None of the 100+ beta testers saw this. You might reboot your phone to clear out the cobwebs.
Joe
 
VERY minor thing I noticed.....

If you turn on SFC obs, and then pinch to zoom out, and then pinch to zoom back in, it will force close.

I'm using a Garmin-Asus Garminfone with Eclair on it. Not a horrible thing, but thought you'd like to know.

Tim

If it continues after reboot, please follow these instructions so that I can ascertain exactly what is going wrong on your device. http://pykl3radar.com/pykl3wiki/index.php/LOGCAT
 
OK.....I'll fiddle some more with it today, and see if it still does it after a reboot.

Thanks!
Tim
 
Joe, a reboot seems to have solved it. Thanks, and sorry for the scare!

Tim
 
I have to say the toggle between reflectivity and velocity is a great timesaver. That combined with the audio alarm each time a new scan comes up keeps my eyes on the road and sky instead of watching the radar display. Outstanding implement.
 
Just bought PYKL3 and I really like it so far... Only problem is I can't get SpotterNetwork positions to work.. I have my app id plugged in and both checkboxes enabled, but it won't show the positions... Am I missing something?

Sent from my Samsung Galaxy SII using Tapatalk 2
 
So, I downloaded this again which is my second attempt to use it on my HTC Thunderbolt and I still seem to have the same issues I had when PYKL was first released. When I zoom in or out, or pan, it is so choppy and the time it takes to draw the screen is so slow that it is really useless...It is a shame because I love the detail of this product.

Does anyone have any suggestions before I uninstall and attempt to get a refund :-(
 
Did you try force closing everything in task manager and clearing your RAM? Choppy video rendering is usually a sign of high RAM utilization.. Are you rooted?

Sent from my Samsung Galaxy SII using Tapatalk 2
 
So, I downloaded this again which is my second attempt to use it on my HTC Thunderbolt and I still seem to have the same issues I had when PYKL was first released. When I zoom in or out, or pan, it is so choppy and the time it takes to draw the screen is so slow that it is really useless...It is a shame because I love the detail of this product.

Does anyone have any suggestions before I uninstall and attempt to get a refund :-(

Unfortunately it's a hardware problem with the HTC devices, most seen in the Thunderbolt and Droid Incredible 2. (I have the Incredible 2.) Even with this issue there are a few things you can do to help the performance. First limit how many layers are turned on. It's the redrawing of the gis data that causes the choppiness. The other much more useful feature is to limit how far from the rda the gis data is drawn. To do this hit Program Options - General Preferences - Performance Tweaks - Gis prozimity filter. The lower the number of degrees you choose the closer to the rda the gis data will be clipped. I run 1.5 on my Incredible 2 and get good results. Also, if they are not already checked, try hiding the counties/states while panning/zooming. This also helps.

These should help out quite a bit. But if it still doesn't satisfy you I'm sure you can contact Joe and see how he can help you out. Here's a link from the pykl3 forum to email Joe.
 
Unfortunately it's a hardware problem with the HTC devices, most seen in the Thunderbolt and Droid Incredible 2. (I have the Incredible 2.) Even with this issue there are a few things you can do to help the performance. First limit how many layers are turned on. It's the redrawing of the gis data that causes the choppiness. The other much more useful feature is to limit how far from the rda the gis data is drawn. To do this hit Program Options - General Preferences - Performance Tweaks - Gis prozimity filter. The lower the number of degrees you choose the closer to the rda the gis data will be clipped. I run 1.5 on my Incredible 2 and get good results. Also, if they are not already checked, try hiding the counties/states while panning/zooming. This also helps.

These should help out quite a bit. But if it still doesn't satisfy you I'm sure you can contact Joe and see how he can help you out. Here's a link from the pykl3 forum to email Joe.

Thanks for the advice guys...I have shut all other apps down, cleared memory, tried cutting out some of the layers, etc. and I am still getting the same results. The one and only way that it will run anywhere near usable is if I cut out all layers, then it does me no good. I will contact Joe directly. I just don't see anyway PYKL is going to run on my current phone :-(
 
Forgot to mention it in the last post but there is a quick way to turn off/on the layers. Hit the gear button in the top right then the lyr button. This toggles through 4 levels of layers. Default is everything turned on. Next is all but radar off, handy to zoom/pan, then radar with counties/states/roads, then back to everything. These devices also loop much better with the layers turned off.

This isn't the ideal solution, but it's the best we've got at this point. Just remember when/if you get a new device give pykl3 another try.
 
Yeah I can vouch that it is working flawlessly on my Galaxy SII.. I wasn't aware that there is a known issue with HTC devices, is this something that could possibly be coded around or is it simply a hardware limitation?

Sent from my Samsung Galaxy SII using Tapatalk 2
 
Back
Top