Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - joeloc

Pages: 1 ... 16 17 [18] 19 20 21
256
Implemented / Re: Single click "immediate" route create mode
« on: December 18, 2011, 16:00:45 »
btw... isnt the clear button in this popup menu the same as the X button in the toolbar?

the popup menu is a bit confusing. why would i press a "settings-like" icon to save my route? in general, it might be better to fit all creating functions into the toolbar directly, eg
plus minus route quick confirm cancel

the huge width scroller on screen top is a bit unnecessary imho. is that really needed so often to warrant that amount of screen space? more useful would be a fancy realtime altitude profile :-).

257
Troubles & Questions / Re: Utilizing EXTERNAL SD on new devices?
« on: December 18, 2011, 09:27:41 »
Is there any way to disable this automatism btw? I want Locus to leave the external sd card alone and stay internal, except for the map folders I configure manually.

Reason: I carry plenty gigabytes of maps with me on several micro sd cards. I keep changing them depending on what I do. Locus needs to stay on the internal storage with all its other data, otherwise everything gets messed up badly.

258
Implemented / Re: Single click "immediate" route create mode
« on: December 17, 2011, 22:05:51 »
works for me... i never rotate though.

259
looks cute :)

260
The most clever "filtering method" would be using the pressure sensor. Or offline DEM data. Or online DEM data. Or a clever combination of everything that is available :).

261
Troubles & Questions / Re: CPU usage while track recording
« on: December 17, 2011, 11:04:42 »
I was just wondering... maybe there's a difference if Locus is minimized by home-key or if the screen is simply turned off while Locus was active?

262
Troubles & Questions / Re: CPU usage while track recording
« on: December 16, 2011, 20:27:45 »
HOWEVER... even with the conservative schedule governor, there is still a big difference in cpu usage depending on which map is enabled in Locus:

map "blank": 200MHZ almost 80%, 500MHZ 20%
mapsforge vector map: 200MHZ 30%, 500MHZ 70%(!)

certainly, the type of map should not make any difference at all when the screen is off?! something is bogus and locus still seems to call some rendering code, even if nothing needs to be rendered.

263
Troubles & Questions / Re: CPU usage while track recording
« on: December 16, 2011, 19:29:50 »
I just managed to get the 1400MHZ rate down to 1%, remaining usage is 200MHZ 60% and 500MHZ (20%) on track recording?

How? The tool "Antutu CPU Master Pro" allows to change the cpu frequency scaling algorithm. Android default on 2.3.6 is something called "ondemand" which goes up to Fullspeed rather quickly (probably after a few microsecs) when something is happening.

The setting "conservative" scales up a bit slower... probably slow enough so it is not triggered by simply reading data from gps driver every now and then. Result is very low cpu clock speed during track logging. Disadvantage could be a slightly larger lag when using the phone, although I didnt notice anything yet.

The pay version of Antutu CPU Master Pro would for example allow to set the scaling to "conservative" automatically only when screen is off.

264
Troubles & Questions / Climbing calculation is hopelessly wrong
« on: December 16, 2011, 18:28:08 »
Your calculations for total climbing are hopelessly wrong. Quite understandable, considering that gps altitude data jumps around more or less randomly by at least 30m. The 15 flat kilometers to my dentist resulted in a 2000m locus climb... I wish we had that kind of mountains here :-).

You need to apply some sort of dampening algorithm on the altitude data before summing up the differences, at least if the origin is gps altitudes.

It works better with google heights, but that's not really useful in the mountains in a foreign country without data connection.

On a related note: how about supporting the pressure sensor of newer phones? That gives much cleaner altitude data when calibrated once.

265
Under review / Track splitting
« on: December 16, 2011, 18:19:03 »
Locus can join tracks already. How about allowing to split track as well? The menu that appears when I click a trackpoint on the map should offer "Split track here" and then turn "thistrack" into "thistrack_1-429" and "thistrack_430-1099".

266
Troubles & Questions / Track category on recording
« on: December 16, 2011, 18:16:15 »
When I record a new track and press Stop, Locus asks me for the name. The category defaults to "None". Shouldnt it rather default to "Recorded"?

267
Troubles & Questions / Re: CPU usage while track recording
« on: December 16, 2011, 17:35:57 »
nmea recording was off during my tests. i only tested real gps data logging.

do you write other files while track recording? my locus dir is on sdcard/external_sd, maybe the external microsd makes a difference? although, since the phone was sitting quietly on the window, there were only very few points recorded. maybe five total.

but seriously... this result can have a million reasons. maybe it's only on my ROM or on galaxy notes or whatever. maybe you wait for other cpuspy reports from other people before wasting more time on this :-)

268
Implemented / Track recording message in notification area
« on: December 16, 2011, 17:18:39 »
The track recording message in notification area is a bit boring. Doesnt even give Locus as program name. Could it maybe look like

Locus - track log with 10s/25m since %hh:%mm
myfancytrack - 02:10h - 23.6km - 523 points

first line has gps parameters and start time.
second line has track name & data.

updated not too often to save battery.

269
Implemented / Re: Waypoint text style
« on: December 16, 2011, 17:07:52 »
Very pretty... I LIKE IT!

There's still about two or three wasted pixels, vertically, below the label, though :-).

270
Troubles & Questions / Re: CPU usage while track recording
« on: December 16, 2011, 16:32:06 »
sorry, still the same cpu usage with latest test version. about 70% on 1400mhz when track recording is on. screen off, phone sits quietly on window, gps fix acquired. system settings / location / use sensor aiding is disabled btw for these tests, otherwise android would simply turn the gps off after a while.

exact same test but with track recording OFF: only 5% at 1400 and 90% at 200MHZ!!

Maybe it has to do with the track recording message in notification area? Is it accidently updated too often? Or something on locus screen? Although the screen is off... I have no clue :)

Pages: 1 ... 16 17 [18] 19 20 21