Messages

Seems like there ARE some ways around this limit. Not a very coder-friendly ones, though.

InFX ... as I wrote. calibrated maps are then saved into locus/mapItems directory. Did "Map item manager" works for you? If so, you should there see all available and loaded maps ...

Sorry, it's just me being dumb, i've read it as "map manager" instead of "map item manager" and have been wondering where the heck am i supposed to see it The new map item manager works for me. BTW, i did try a few more pics, no more out of mem crashes happened, but... Memory problems are not over yet :-(

I've been playing with the calibration, added the shortcut button to the right bar, moving around the map, playing with it all a little more until finally i've tapped that shortcut button and got a nasty crash. Guess what i found in the logcat...

Code Select Expand

I/LocationState(10846): addLocationChangeListener(menion.android.maps.a@40582e80), listeners:1
I/LocationState(10846): addLocationChangeListener(menion.android.locus.core.MainActivity@4057db68), listeners:2
W/MainApplication(10846): onAppRestored()
I/Orientation(10846): addListener(menion.android.locus.core.maps.MapScreenView@4058a158), listeners.size():1
I/MainActivity(10846): ----------------------------------------------------
I/MainActivity(10846): Memory info: onResume() - finished, correct:true (47787ms)
I/MainActivity(10846):            PrivDirty      Pss     SharedDirty
I/MainActivity(10846):   dalvik: 684 (0), 731 (0), 1600 (0)
I/MainActivity(10846):   native: 3188 (-88), 3207 (-88), 672 (0)
I/MainActivity(10846):
I/MainActivity(10846):           nativeHeapSize: 29.55 MB
I/MainActivity(10846):  nativeHeapAllocatedSize: 20.35 MB
I/MainActivity(10846):       nativeHeapFreeSize: 291.52 kB
I/MainActivity(10846): ----------------------------------------------------
I/SmartKeyboardPro(  795): Trying to load dictionary: EN
E/CustomActivity(10846): dialog:null
E/dalvikvm-heap(10846): 9830400-byte external allocation too large for this process.
E/GraphicsJNI(10846): VM won't let us allocate 9830400 bytes
W/dalvikvm(10846): threadid=1: thread exiting with uncaught exception (group=0x40015560)
I/Logger  (10846): handleException(java.lang.OutOfMemoryError: bitmap size exceeds VM budget, SILENT)
I/Logger  (10846): Writing crash report file.
W/MainApplication(10846): onAppMinimized()
I/DbWaypoint(10846): saveVisibles() - data:0, saved:true, size:0
W/Service (10259): setForeground: ignoring old API call on com.carl.tcpro.counter.UpdateService
I/SmartKeyboardPro(  795): Trying to load dictionary: EN
I/Process (10846): Sending signal. PID: 10846 SIG: 9


Menion, i just did a quick test at work, took a random full resolution pic (5mp) with the phone camera, and tried to "calibrate" it as if it was a map. I no longer get an out of memory crash :-)

Note that i only tested it once, though.

PS: A bit of a noobish question - where do i put the resulting files in order to be able to select them from GUI later ?

Thanks, i will check if it still crashes on the cam images later today or tomorrow morning (i am at GMT+2). About 4000x3000 image, it's 12megapixels, that's not exactly unusual on todays high-end phones. And, btw, how comes loading the whole image in memory only takes 25mb or RAM ? I would assume it need either 3 or 4 bytes per pixels, requiring at least 36mbytes (not counting the 1000/1024 crap).

Now, about the max memory the system lets the process to have - for those of us on rooted phones, where can we modify this ?

Thank you for feedback, I'll surely improve it. Currently worst part is size of images ... that's maybe reason why app crashed to rijackson.

I seem to get an out of memory crash on every calibration attempt, after clicking compute and confirming. I have yet to do a single successfull use of the feature The out of memory exception is thrown by bitmap factory, but this is only visible via a system log or the report preview details, to the simple user its just an evil detailless fc.

Note - i use the normal 5mp internal camera pics at its full resolution, not some oversized 100megapixel paper map scans.

Make sure you are not misinterpreting something entirely different as GPS disabled while the is screen off. I had a seemingly erratic track recording in Locus while testing the GPS auto-off features, that, at some point, for a moment, seemed to me like a GPS disabling while the screen is off, yet it wasn't. What it was is the track recording minimal interval and GPS auto-off interval both enabled, creating some strange behavior with the intervals, seemingly, drifting against each other, only recording a point when the on state for both happens to overlap.

PS: Try setting the time and distance intervals in track recording settings to 0, max accuracy to something much higher than the min accuracy in GPS auto off, and try again.
PPS: Don't get me wrong, this is most probably NOT it. I am just trying to coin in some possible directions, and it's easy enough to check it.

Having an option to start/stop track recording via intent broadcast would allow tasker or a similar app integration without much coding needed on the Locus side. And this, in turn, can allow some interesting user-side stuff, such as turning the logging on automatically while using a GPS nav app, turning the logging off when the battery is below a certain level, etc etc etc. Obviously, a proper way of doing such an integration would be coding a tasker plugin (more info here), but i guess that's really kinda too much to ask :-)

Thanks in advance.

Menion - thanks a lot for the feature :-) I keep getting pleasant surprises from Locus :-)

Not being on the forum very often at all, i've just noticed the feature mentioned in the market change log, totally surprised by it, especially after being the original poster of this thread and after being told, politely, that "not all wishes may come true", in this very thread :-)

Something i would really wish to separate is the GPS power control while recording a track and GPS power control while using the application in general. For example, i only want a point recorder once a minute, yet, when i actually open the app activity and look at the map, i'd like it to run continuously.

If you'll be using auto-power off feature of GPS, you can set for track recording interval 0 for time and distance and only set accuracy value to same as in GPS settings. This will cause that only points with this accuracy will be saved

Exactly what i thought, so ive just set it to 0,0,some huge accuracy number, and controlling the logging by the gps off thing.

Again, thanks for the feature

hmm, not sure if this is not more confusing for users then this (already quite complicated settings)

anyway I currently published new version on market, so please anyone ... test this feature. I think it's much better then previous version and it needs some using to discover possitives and negatives ... we'll see

I've just noticed this feature while reading the change log on the market and wanted to thanks you for finally implementing something that actually allows using an HTC HD2 for GPS logging without being a battery hog (the GPS subsystem on the HD2 seems to consume full current the moment it is turned on, doesn't matter what params you pass to the LocationManager, it will draw over 100mA even if you requestLocationUpdates each 10 minutes!!!).

Something that looks confusing in the settings, though: while recording a track, it isn't clear what time interval is being used, or how they are combined.

Hmm, i did not know this, the only thing ive ever coded on android is a kind of hello world, just to get a taste of it. Obviously, ive never registred on market to explore it on the dev side (i probably should have, lol).

Anyway, whats "an instance" ? A copy installed on a device assigned to the acc ? An actual running app instance ? Anything else ?

I've successfully bought & installed the plugin yesterday, and got this infinite "Loading" the first time i tried it as well. But, after killing the app and retrying in 1..2 minutes, i was able to successfully download an Israel, Switzerland, and, later, and Italy map.

BTW, i've noticed a small rendering issue with the Swiss map, the Lucern lake is rendered white.

The applications you buy on the Android Market (all of them, not just Locus) are linked to the specific Google account, not a specific device. You can buy an app and use it on every device you have, as long as you use the same Google account on all those devices.

No, it doesn't seems the functionality is already there, it seems you pass this interval param into the location manager and trust the location manager to wake up, get a fix and give you that location once in a time interval. This is exactly what doesn't work properly, matching my description above. What i meant is to totally stop everything GPS related, waking up the device once in a time interval using alarm manager or something similar, and only reenable the GPS until you get a fix.

PS: Sorry if i wasn't clear and do correct me if i am wrong somewhere.