locify - Project Hosting on Google Code

Last 7 days Dec 20, 2009 issue 31 (Locify is very very slow) commented on by ne...@centrum.cz - Sorry, it wasn't seek() but skip() function which must have been replaced with read (). Sorry, it wasn't seek() but skip() function which must have been replaced with read (). Dec 20, 2009 issue 31 (Locify is very very slow) reported by ne...@centrum.cz - What steps will reproduce the problem? 1. I use Sony Ericsson G900 phone (Symbian UIQ 3), 3G internet connection 2. Going through the menus is very slow, it usually takes at least 4 seconds to go from one screen to another Example: Main menu -> Nearest caches : 4 seconds Nearest caches -> choosing position : 4 seconds choosing position -> list of caches : 15-25 seconds list of caches -> details of the cache : 4 seconds details of the cache -> list of caches ("back" button) : 14 s list of caches -> choosing position ("back" button) : 5 second or java.io.IOException: -36, Place: Http.run.request, Data: http:// locify.com.server1.azhosting.sk/nearestCaches/service/nearest.php choosing position -> Nearest caches : 12 seconds Nearest caches -> Main menu ("back" button): 2 seconds What is the expected output? What do you see instead? Switching between screens should be max 1 second (except when loading online data). What Locify version are you using? What is your cell phone brand and type? Locify 1.5.12, Sony Ericsson G900 phone (Symbian UIQ 3) Please provide any additional information below. I reported similar speed issue on my phone at "Openwig" project and the solution was to replace seek() function with read() function. Details here (in Czech): http://code.google.com/p/openwig/issues/detail?id=38&can=1&colspec=ID %20Type%20Status%20Priority%20Milestone%20Summary What steps will reproduce the problem? 1. I use Sony Ericsson G900 phone (Symbian UIQ 3), 3G internet connection 2. Going through the menus is very slow, it usually takes at least 4 seconds to go from one screen to another Example: Main menu -> Nearest caches : 4 seconds Nearest caches -> choosing position : 4 seconds choosing position -> list of caches : 15-25 seconds list of caches -> details of the cache : 4 seconds details of the cache -> list of caches ("back" button) : 14 s list of caches -> choosing position ("back" button) : 5 second or java.io.IOException: -36, Place: Http.run.request, Data: http:// locify.com.server1.azhosting.sk/nearestCaches/service/nearest.php choosing position -> Nearest caches : 12 seconds Nearest caches -> Main menu ("back" button): 2 seconds What is the expected output? What do you see instead? Switching between screens should be max 1 second (except when loading online data). What Locify version are you using? What is your cell phone brand and type? Locify 1.5.12, Sony Ericsson G900 phone (Symbian UIQ 3) Please provide any additional information below. I reported similar speed issue on my phone at "Openwig" project and the solution was to replace seek() function with read() function. Details here (in Czech): http://code.google.com/p/openwig/issues/detail?id=38&can=1&colspec=ID %20Type%20Status%20Priority%20Milestone%20Summary Last 30 days Nov 30, 2009 r251 (Move status icons on Sony Ericsson phones) committed by glo...@gmail.com - Move status icons on Sony Ericsson phones Move status icons on Sony Ericsson phones Nov 30, 2009 BuildRequirements (What you need to build your own version of Locify) Wiki page edited by libor.tvrdik - Revision r250 Escape unwanted italic. Revision r250 Escape unwanted italic. Nov 30, 2009 BuildRequirements (What you need to build your own version of Locify) Wiki page edited by libor.tvrdik - Revision r249 Added Emulator troubleshooting Revision r249 Added Emulator troubleshooting Earlier this year Nov 18, 2009 issue 30 (add support for map atlas) reported by tropikhajma - What steps will reproduce the problem? 1. try to use my existing TrekBuddy map in Locify What is the expected output? What do you see instead? expected: map is usable instead: map could not be initialized as is unsupported What Locify version are you using? What is your cell phone brand and type? 1.5.12 Please provide any additional information below. locify does not support the atlas type of maps. Since I already have quite a large atlas in TrekBuddy, I'd be grateful if: 1. locify could reuse the map files from TB folder to save space on the card (hmm, that looks like a separate feature request) 2. locify could use the atlas type of offline maps What steps will reproduce the problem? 1. try to use my existing TrekBuddy map in Locify What is the expected output? What do you see instead? expected: map is usable instead: map could not be initialized as is unsupported What Locify version are you using? What is your cell phone brand and type? 1.5.12 Please provide any additional information below. locify does not support the atlas type of maps. Since I already have quite a large atlas in TrekBuddy, I'd be grateful if: 1. locify could reuse the map files from TB folder to save space on the card (hmm, that looks like a separate feature request) 2. locify could use the atlas type of offline maps Oct 31, 2009 r248 (fix & bug in waypoint name and date bug in navigation sc...) committed by glombt - fix & bug in waypoint name and date bug in navigation screen fix & bug in waypoint name and date bug in navigation screen Oct 30, 2009 Locify.jar (date fix, navigation url fix) file uploaded by glombt Oct 30, 2009 Locify.jad (date fix, navigation url fix) file uploaded by glombt Oct 30, 2009 r247 (Fix date bug in Navigation screen) committed by glombt - Fix date bug in Navigation screen Fix date bug in Navigation screen Oct 24, 2009 issue 28 (Geocaching service mess strings in another apps) commented on by Pitlicek - Still a problem in 1.5.11 Still a problem in 1.5.11 Oct 22, 2009 r246 (geocaching service back fix) committed by gdestil - geocaching service back fix geocaching service back fix Oct 22, 2009 issue 24 (I cannot download new version for BlackBerry 9000) commented on by gdestil - This is all right. Higher version couldn't be launched on BlackBerry so we keep this version. We are looking for volunteers to take Blackberry development in hands. This is all right. Higher version couldn't be launched on BlackBerry so we keep this version. We are looking for volunteers to take Blackberry development in hands. Oct 16, 2009 issue 29 (Turning off Locify breaks recorded track) reported by Pitlicek - What steps will reproduce the problem? 1. Start track recording 2. Turn Locify off and on 3. Continue track recording 4. Save recorded track What is the expected output? What do you see instead? Properly saved track. Track is invisble in saved files list. What Locify version are you using? What is your cell phone brand and type? 1.5.10, SE K550i Please provide any additional information below. I'm attaching messed kml file. What steps will reproduce the problem? 1. Start track recording 2. Turn Locify off and on 3. Continue track recording 4. Save recorded track What is the expected output? What do you see instead? Properly saved track. Track is invisble in saved files list. What Locify version are you using? What is your cell phone brand and type? 1.5.10, SE K550i Please provide any additional information below. I'm attaching messed kml file. Oct 16, 2009 issue 28 (Geocaching service mess strings in another apps) reported by Pitlicek - What steps will reproduce the problem? 1. Open nearest cache service, do nothing and get back to services list 2. Open another service (Wikipedia, for example) What is the expected output? What do you see instead? I see "Vyfiltrovat nalezene" (or other string from geocaching form sometimes) as labels for location inputs. I expect to see original labels. What Locify version are you using? What is your cell phone brand and type? 1.5.10, SE K550i What steps will reproduce the problem? 1. Open nearest cache service, do nothing and get back to services list 2. Open another service (Wikipedia, for example) What is the expected output? What do you see instead? I see "Vyfiltrovat nalezene" (or other string from geocaching form sometimes) as labels for location inputs. I expect to see original labels. What Locify version are you using? What is your cell phone brand and type? 1.5.10, SE K550i Oct 16, 2009 issue 23 (Locify doesn't exit on Blackberry) commented on by j...@petrdavid.cz - You don't need to remove battery. Just press Alt+Right_Shift+Del You don't need to remove battery. Just press Alt+Right_Shift+Del Oct 15, 2009 issue 27 (Map caching does not work) reported by Pitlicek - What steps will reproduce the problem? 1. Show yout position on map, wait for map to download 2. Zoom in/out, wait for map to download 3. Zoom to previous level What is the expected output? What do you see instead? Map will show immediately, because it should be cached. But it isn't, it's redownloaded. What Locify version are you using? What is your cell phone brand and type? 1.5.10, SE K550i Please provide any additional information below. I have caching enbaled, cache size 5120 kB and plenty of free space on my memory card. What steps will reproduce the problem? 1. Show yout position on map, wait for map to download 2. Zoom in/out, wait for map to download 3. Zoom to previous level What is the expected output? What do you see instead? Map will show immediately, because it should be cached. But it isn't, it's redownloaded. What Locify version are you using? What is your cell phone brand and type? 1.5.10, SE K550i Please provide any additional information below. I have caching enbaled, cache size 5120 kB and plenty of free space on my memory card. Oct 15, 2009 issue 26 (Can't stop track recording when GPS is disconnected) reported by Pitlicek - What steps will reproduce the problem? 1. Go outside, connect with GPS, start recording track, arrive to your destination 2. Turn off Locify (but forgot to turn off track recording), turn off GPS. 3. Remeber you forgot to disable track recording 4. Turn on Locify, try to access track recording screen What is the expected output? What do you see instead? Display track recording screen with enabled Stop button. Locify complains it can't do that without connected GPS. What Locify version are you using? What is your cell phone brand and type? 1.5.10, SE K550i Please provide any additional information below. It will be nice to have automatic track recording on every new start of navigation. What steps will reproduce the problem? 1. Go outside, connect with GPS, start recording track, arrive to your destination 2. Turn off Locify (but forgot to turn off track recording), turn off GPS. 3. Remeber you forgot to disable track recording 4. Turn on Locify, try to access track recording screen What is the expected output? What do you see instead? Display track recording screen with enabled Stop button. Locify complains it can't do that without connected GPS. What Locify version are you using? What is your cell phone brand and type? 1.5.10, SE K550i Please provide any additional information below. It will be nice to have automatic track recording on every new start of navigation. Oct 15, 2009 issue 25 (Messed character encoding) reported by Pitlicek - What steps will reproduce the problem? 1. Create new place 2. Write something with diacritic marks to name and description, save new place 3. Try to open/view new place What is the expected output? What do you see instead? Showing proper characters with diacritic, but it shows strange characters instead. What Locify version are you using? What is your cell phone brand and type? 1.5.10, SE K550i Please provide any additional information below. The encoding should be utf8 What steps will reproduce the problem? 1. Create new place 2. Write something with diacritic marks to name and description, save new place 3. Try to open/view new place What is the expected output? What do you see instead? Showing proper characters with diacritic, but it shows strange characters instead. What Locify version are you using? What is your cell phone brand and type? 1.5.10, SE K550i Please provide any additional information below. The encoding should be utf8 Oct 09, 2009 r245 (gc fix) committed by gdestil - gc fix gc fix Oct 06, 2009 r244 (tagging 1.5.9) committed by gdestil - tagging 1.5.9 tagging 1.5.9 Oct 06, 2009 issue 23 (Locify doesn't exit on Blackberry) commented on by slavek.zika - I have the same problem, Locify 1.5.7 Blackberry 9000 Bold I have the same problem, Locify 1.5.7 Blackberry 9000 Bold Oct 06, 2009 issue 24 (I cannot download new version for BlackBerry 9000) reported by slavek.zika - What steps will reproduce the problem? 1. I cannot download new version for BlackBerry 9000 2. 3. What is the expected output? What do you see instead? I download version 1.5.7 instead of 1.5.9 What Locify version are you using? What is your cell phone brand and type? BlackBerry 9000 - Bold Please provide any additional information below. What steps will reproduce the problem? 1. I cannot download new version for BlackBerry 9000 2. 3. What is the expected output? What do you see instead? I download version 1.5.7 instead of 1.5.9 What Locify version are you using? What is your cell phone brand and type? BlackBerry 9000 - Bold Please provide any additional information below. Oct 01, 2009 r243 (http connection fix, google maps fix) committed by gdestil - http connection fix, google maps fix http connection fix, google maps fix Sep 30, 2009 issue 23 (Locify doesn't exit on Blackberry) commented on by jan.cejka - The same issue was already reported as Issue #21 on Blackberry 8800 with 1.5.6 version. I have the same experience with 1.5.7 on BB 8800. The only (stupid) solution for me is to remove batery and reboot BB completely if I want to exit Locify :-( The same issue was already reported as Issue #21 on Blackberry 8800 with 1.5.6 version. I have the same experience with 1.5.7 on BB 8800. The only (stupid) solution for me is to remove batery and reboot BB completely if I want to exit Locify :-( Sep 17, 2009 Locify-1.5.7-1.jar (Route recording in GPX or KML format) file uploaded by glombt Sep 17, 2009 Locify-1.5.7-1.jad (Route recording in GPX or KML format) file uploaded by glombt Sep 17, 2009 r242 (Route recording in KML or GPX format) committed by glombt - Route recording in KML or GPX format Route recording in KML or GPX format Sep 17, 2009 r241 (Empty Message) committed by glombt - Empty Message Empty Message Sep 17, 2009 r240 (Empty Message) committed by glombt - Empty Message Empty Message Sep 16, 2009 Locify-1.5.7.jad (Fixed Google maps problem and new maps) file uploaded by glombt Sep 16, 2009 Locify-1.5.7.jar (Fixed Google maps problem and new maps) file uploaded by glombt Sep 16, 2009 r239 (fixed google maps problem) committed by glombt - fixed google maps problem fixed google maps problem Sep 07, 2009 r238 (added map providers) committed by men...@asamm.cz - added map providers added map providers Sep 02, 2009 r237 (location timeout) committed by gdestil - location timeout location timeout Aug 23, 2009 Locify-1.5.7.jar (Locify with tourist Map of the Czech Republic) file uploaded by glombt Aug 23, 2009 Locify-1.5.7.jad ( with tourist Map of the Czech Republic) file uploaded by glombt Aug 23, 2009 r236 ([No log message]) committed by glombt - [No log message] [No log message] Aug 23, 2009 r235 (prvni commit) committed by glombt - prvni commit prvni commit Aug 23, 2009 r234 (prvni commit) committed by glombt - prvni commit prvni commit Aug 23, 2009 r233 (prvni commit) committed by glombt - prvni commit prvni commit Aug 23, 2009 r232 (Empty Message) committed by glombt - Empty Message Empty Message Aug 11, 2009 r231 (new bag of improvement, almost everything except HTML browse...) committed by men...@asamm.cz - new bag of improvement, almost everything except HTML browser works well new bag of improvement, almost everything except HTML browser works well Aug 11, 2009 issue 23 (Locify doesn't exit on Blackberry) reported by j...@petrdavid.cz - What steps will reproduce the problem? 1. Install and run Locify on Blackberry 2. Exit Locify, select "Yes" from menu when confirmation window is shown 3. What is the expected output? What do you see instead? It is expected that Locify exits. The confirmation window is shown and Locify is running instead of exiting. What Locify version are you using? What is your cell phone brand and type? Locify 1.5.7 Blackberry 9000 Bold Please provide any additional information below. What steps will reproduce the problem? 1. Install and run Locify on Blackberry 2. Exit Locify, select "Yes" from menu when confirmation window is shown 3. What is the expected output? What do you see instead? It is expected that Locify exits. The confirmation window is shown and Locify is running instead of exiting. What Locify version are you using? What is your cell phone brand and type? Locify 1.5.7 Blackberry 9000 Bold Please provide any additional information below. Aug 07, 2009 issue 22 (Starting GPS on BlackBerry after upgrade to 1.5.6 locks phon...) commented on by jan.cejka - Just for follow-up - in the end this was not a problem. After trying everything, I have deleted directory with all the Locify files on BB. New run of program just downloaded all the services again and I can start GPS without blocking all the device and everything seems to work normally (version 1.5.7). Question is if this "solution" couldn't be put into BlackBerry troubleshooting section as one of successful ones. Jan Just for follow-up - in the end this was not a problem. After trying everything, I have deleted directory with all the Locify files on BB. New run of program just downloaded all the services again and I can start GPS without blocking all the device and everything seems to work normally (version 1.5.7). Question is if this "solution" couldn't be put into BlackBerry troubleshooting section as one of successful ones. Jan Aug 02, 2009 r230 (new editor) committed by gdestil - new editor new editor Aug 02, 2009 r229 (design fixes, lwuit doc) committed by gdestil - design fixes, lwuit doc design fixes, lwuit doc Aug 02, 2009 r228 (my phone start exception fix, start work on layout, small fi...) committed by gdestil - my phone start exception fix, start work on layout, small fixes my phone start exception fix, start work on layout, small fixes Jul 23, 2009 r227 (errorscreen and authscreen fix) committed by gdestil - errorscreen and authscreen fix errorscreen and authscreen fix Jul 23, 2009 r226 (icon and midlet name) committed by gdestil - icon and midlet name icon and midlet name

issue 31 (Locify is very very slow) reported by ne...@centrum.cz - What steps will reproduce the problem? 1. I use Sony Ericsson G900 phone (Symbian UIQ 3), 3G internet connection 2. Going through the menus is very slow, it usually takes at least 4 seconds to go from one screen to another Example: Main menu -> Nearest caches : 4 seconds Nearest caches -> choosing position : 4 seconds choosing position -> list of caches : 15-25 seconds list of caches -> details of the cache : 4 seconds details of the cache -> list of caches ("back" button) : 14 s list of caches -> choosing position ("back" button) : 5 second or java.io.IOException: -36, Place: Http.run.request, Data: http:// locify.com.server1.azhosting.sk/nearestCaches/service/nearest.php choosing position -> Nearest caches : 12 seconds Nearest caches -> Main menu ("back" button): 2 seconds What is the expected output? What do you see instead? Switching between screens should be max 1 second (except when loading online data). What Locify version are you using? What is your cell phone brand and type? Locify 1.5.12, Sony Ericsson G900 phone (Symbian UIQ 3) Please provide any additional information below. I reported similar speed issue on my phone at "Openwig" project and the solution was to replace seek() function with read() function. Details here (in Czech): http://code.google.com/p/openwig/issues/detail?id=38&can=1&colspec=ID %20Type%20Status%20Priority%20Milestone%20Summary

What steps will reproduce the problem? 1. I use Sony Ericsson G900 phone (Symbian UIQ 3), 3G internet connection 2. Going through the menus is very slow, it usually takes at least 4 seconds to go from one screen to another Example: Main menu -> Nearest caches : 4 seconds Nearest caches -> choosing position : 4 seconds choosing position -> list of caches : 15-25 seconds list of caches -> details of the cache : 4 seconds details of the cache -> list of caches ("back" button) : 14 s list of caches -> choosing position ("back" button) : 5 second or java.io.IOException: -36, Place: Http.run.request, Data: http:// locify.com.server1.azhosting.sk/nearestCaches/service/nearest.php choosing position -> Nearest caches : 12 seconds Nearest caches -> Main menu ("back" button): 2 seconds What is the expected output? What do you see instead? Switching between screens should be max 1 second (except when loading online data). What Locify version are you using? What is your cell phone brand and type? Locify 1.5.12, Sony Ericsson G900 phone (Symbian UIQ 3) Please provide any additional information below. I reported similar speed issue on my phone at "Openwig" project and the solution was to replace seek() function with read() function. Details here (in Czech): http://code.google.com/p/openwig/issues/detail?id=38&can=1&colspec=ID %20Type%20Status%20Priority%20Milestone%20Summary

Last 7 days

Last 30 days

Earlier this year