Notices

In the version I just uploaded, the 2 minute crash should be fixed… It will come OTA after PR1.2 is released, because apparently there are problems with the SDK1.2 autobuilder and PR1.1.

(And I don't have access to the repositories and have never used the autobuilder, so hopefully smurfy can release a new version as soon as PR1.2 is out )

Thats strange, for now i cant reproduce the bug. Sry but i dont know how this can be, Yesterday I have checked it several times and it was everytime the same failure.

Thx for the new version. I will try it and give you a feedback.
I am a fan of the CellID based position, becouse most time its enough and need very less resources. So it sounds like a great solution for me.

Ok i am a fan of CellID based locating. But only where it sufficient.

And after a short test of your test application I realized that i cant use that in the City it shows me 10 Stations. All of them are 1-2 kilometers away from here...

well, that's probably the way the lookup at bahn.de (our backend) works...
for me, it always showed many "stations", but the "correct" one was alway included... some of the results were even justs streets without any bus/train station (to my knowledge)
I'm not sure if we can improve this with a better positioning, but of course we can try

I suggest to use:
, See http://wiki.maemo.org/Documentation/...onGPSDeviceFix

The check for accuracy has been suggested before (http://talk.maemo.org/showpost.php?p...0&postcount=50). I don't think power management is a valid reasoning not to enable GPS early on app startup - you can switch it off once you got a fix with sufficient accuracy, and - in case it doesn't get any good fix - after a reasonable timeout (e.g. 10 minutes). As noticed before the location-lib will keep the position, so when you click GPS button later, you'll very likely get a decent position instantly. This scheme will fail only for a usecase where you move away from where you started the app, and then click the GPS button in search station. For all other cases there'll be no difference regarding power consumption between starting GPS on app-start and switch off after time it needs for first fix, and doing the same on hitting button but make user wait for 20sec in that case. Also GPS doesn't eat that much power, so don't worry about some minutes of enabling it during app startup.

jOERG

@joerg_rw:

next version will have a early gps startup

@hcm:

sorry about missing stuff in the repository now it should compile.
i currently doing final tests and try if i get the new version to the autobuilder.

hello everyone,

is it just me or do you also get 'an unknown error occured' all the time..? did deutsche bahn change something in the backend?

keep up the good work!

boudjere

thanks for the report,

it seams that way. gps gives a segfault and search an unknown error.

will fix it sometime today and release a fix.

Edit:
Ok this is a major change so i can't fix it right now, but still today after i got some sleep.

Changes i see so far:
- They added priceing and duration infos directly to the search result
- detailpage also changed a bit

Ok i just submitted a working version to the autobuilder.
Should be in extras-devel in the next couple of houres

Is this App dead? It didn't work for me anymore, so i uninstalled. Now i can't find it to reinstall.