|
2010-12-01
, 18:33
|
Posts: 1,548 |
Thanked: 7,510 times |
Joined on Apr 2010
@ Czech Republic
|
#372
|
Quick reply...
Feature request: in GPS, along with On and Off, add third option: Ask. So that when Modrana wants to turn on GPS, it asks me whether it's needed.
It seems some of this you've already implemented, I just discovered there is the download around route option... Woah, GREAT!!!
Can you save and load routings / not sure this is the same as tracks?
Great application! Would you consider integrating functionality from my thread about Itinerer Support?
I like the third option (and think it will help). I also would like to propose the following: Trigger on not just the current point, but the point after it. This way, even if it's still focused on a point behind us, once we pass the next point it will auto-fix itself.
I dislike using one of the buttons for a fix for this though. I would think adding a widget/button to the lower right stack of route buttons would work well for this. (eg "Jump to next point" or "skip this point") It would also allow one to jump to a turn 3 or 4 ahead to trigger on too, and make "robo-phone" quiet during a sequence of turns one already knows well.
I like those options, and highly vote for a restore route on restart. Especially now that there's a top-level button for "clear current route".
Now for the bug list:
So over the holiday, I took modRana on a trip with me, about 800 miles round trip. I found a couple small bugs on the way, three of which were real problems:
1> Despite spending lots of time downloading tiles, when I was in an area that I know downloaded, local tiles were not used. If I turned off (or lost) GSM, I got the "download failed" tiles. And if I switched my data plan setting to "only vital info" I got a grey background. I even had wifi for one stop in the trip, and downloaded tiles for a 20k radius. It said it got all the tiles (and my free space dropped by 200M), but on starting it up and driving, I got the same thing. I have sqlite turned on, and the database files seem to be ok / intact and about the right size. Any ideas?
2> After some points I started getting an odd "blinking" when going over 50MPH. It seemed to happen when I was in an area where I only had GSM2.0 (not EDGE or 3G). The screen would draw, but then would go blank (no title bar or map or anything). The GPS would fall behind during this, and the whole device would become non-responsive. After I'd slowed (under 30mph) or stopped for a short time, it would return to normal.
3> The text in the box seemed to change size randomly, more based on how long the text was. In may cases it was so tiny as to be illegible unless looked VERY closely at the device.
Of course, I was driving and didn't turn on debugging, so I have no logs for any of this. :P And I updated to 1.19 just before the trip, so it's the current version.
One more thing to check out: Not sure if modRana is hitting a processing wall (though it seems it may be). This may be something to check out to see if modRana could benefit from it. It compiles python code in to platform specific executable code, and can really speed things up. At least one other app on the N900 is using it.
Thankfully I didn't have to rely on it much, since the voice announcements are now happening more frequently and with more fore-warning.
Overall, this trip modRana really did a great job. Minus the tile cache issue, everything went well, and the announcments worked like a charm. (I love the warning a couple miles out btw, much better.)
|
2010-12-01
, 18:49
|
|
Posts: 284 |
Thanked: 498 times |
Joined on Jun 2009
@ Poland
|
#373
|
(...)
So basically:?
- "click to start" screen on startup
- display trip distance and elapsed time + distance traveled since last click
- some way to reset both counters
Seems doable, I was already planing to add some non-map navigational aids and this would quite fit in (together with that directions + distance indicator)
BTW, modRana already uses the shortest, once-per-second GPS-fix update interval provided by liblocation. Could that be too slow for racing ?
|
2010-12-01
, 19:21
|
Posts: 73 |
Thanked: 33 times |
Joined on Nov 2010
|
#374
|
Definitely something broken in the drawing pipeline, most probably due to processing more tiles than usual due to the speed.
I suspect the automatic tile download mechanism might be causing this. It basically spawns a thread for every tile that is not found in the local storage.
Provided you are moving fast enough and have a bad Internet connection at the same time, there can be quite a few threads that are contesting for bandwidth and each can live for up to 30 seconds, before its connection times out.
I guess a limit on the number of concurrent auto-download threads might be in order.
But this still should not cause a black screen - just a slowdown, so there is probably also something related, that breaks the drawing.
|
2010-12-01
, 19:33
|
Posts: 1,548 |
Thanked: 7,510 times |
Joined on Apr 2010
@ Czech Republic
|
#375
|
What I did do on day 2 before leaving was loading the tracklog of day 1 on the map as a reference. Could this have caused more drain?
Just after installing the latest version (0.19-3), I noticed some gpx files under log and misc. Since I cleared out my tracklogs, and they are from a location I've never been, I assume they came with the install.
- Can these be removed from the package?
- Can you add an option to set the location where tracklogs get stored, so I can reach them via USB (copy to PC)?
By the way... WHAT HAVE YOU DONE to modRana???
It (0.19-3) has become MUCH faster suddenly, the menus are so much more responsive. YAY!
|
2010-12-01
, 19:34
|
Posts: 739 |
Thanked: 114 times |
Joined on Sep 2009
|
#376
|
|
2010-12-01
, 22:26
|
|
Posts: 1,455 |
Thanked: 3,309 times |
Joined on Dec 2009
@ Rochester, NY
|
#377
|
As there are maybe already a bit too many of the route buttons I am more thinking about integrating last/next turn switches into the directions frame, like this:
Definitely something broken in the drawing pipeline, most probably due to processing more tiles than usual due to the speed.
Its currently set to fit inside the box, which isn't ideal the reasons you describe. I see two possible ways how to improve this:
Looks interesting, ... But it might be quite complicated to properly package for the autobuilder.
BTW, this is how dragging the map with a long road displayed looks like:
The Following User Says Thank You to woody14619 For This Useful Post: | ||
|
2010-12-01
, 23:10
|
Posts: 4,556 |
Thanked: 1,624 times |
Joined on Dec 2007
|
#378
|
|
2010-12-02
, 06:53
|
Posts: 1,994 |
Thanked: 3,342 times |
Joined on Jun 2010
@ N900: Battery low. N950: torx 4 re-used once and fine; SIM port torn apart
|
#379
|
|
2010-12-02
, 19:21
|
Posts: 73 |
Thanked: 33 times |
Joined on Nov 2010
|
#380
|
Tags |
bada rox, martin_rocks, modrana, navigation, openstreetmap, the best, wehasgps |
Thread Tools | |
|
i
However, I realized that it has to do with a usage pattern. If you select route->address to address and then click on "start" with the keyboard closed, you'll get the on-screen keyboard and you can see what you're typing with no problem. But if you open the keyboard, you'll get a little dialog window at the bottom fo the screen that reads "Input the start address". That one uses a black font on a black background. You can see the text if you swipe to select it, which changes the background to light blue.
I don't see anything in user_config.conf to control font colors. I don't have a .gtkrc controlling anything. However, after a bit of exploring, I found that I could modify mod_textEntry.py to fix the problem. After the line:
Hopefully, this post will give somebody who knows more about gtk what they need to fix this bug.