I love Osmand, but my S3M does not (GPS sleep mode), please help

[Danny]

There seems to be an issue with the Galaxy S3Mini and sleep mode.
I have just started bike navigation and Osmand is perfect, but as soon as the display goes to sleep mode, the nice voice tells me the gps is lost, and obviously the whole program stops working (map stays in the same place).
Yes, I've set "sleep mode" option. Tracking interval 1s.
I've tried putting the program into background by homebutton, as suggested on another (s3m) help group.
Does not work.
I have no problems with accuracy of GPS when biking.
But sleep mode voice navigation simply does not work in Osmand.

It DOES with the Komoot-App!!!!!!!

Does that help anyone to see where the problem is and how to fix it???

Thank you!!!!
Danny

[Torsten Bronger]

Hallöchen!

Danny writes:

> [...]

>
> Does that help anyone to see where the problem is and how to fix
> it???

Unfortunately, I can only confirm this problem. But I also have not
found a solution for it.

Tschö,
Torsten.

--
Torsten Bronger Jabber ID: torsten...@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com

[C G]

Have you checked in Android Task manager if OsmAnd is not in the 'Auto-end' list?

[Torsten Bronger]

Hallöchen!

C G writes:

> Have you checked in Android Task manager if OsmAnd is not in the
> 'Auto-end' list?

I don't have a task manager installed, and Osmand must not be in any
auto-end list by default.

[C G]

On my device, task manager was installed by default.
I experienced the same problem. I found that OsmAnd was in the auto-end list (just the nightly build version, not the version installed via google play).

[Torsten Bronger]

Hallöchen!

C G writes:

> On my device, task manager was installed by default.

Can you provide me with a link to the task manager app that you used
in Google Play? There are several, and my first try was full of
adware. Thank you!

[C G]

Sorry, I've just understood this was not an Android task manger, but a Motorola task manager (installed by default on... Motorola device). It doesn't seem to be on Google play. So I cannot help you.
Sorry!

[Danny]

The default Samsung applications manager seems to have no such list.
I don't have/ever had other task managers installed.

As the Komoot-App is able to do sleep mode navigation without any changes in settings, it seems to be something between the app and the device...
Do the OsmAnd programmers listen in here?

I know this obviously does not have high priority, but if it could be fixed easily...
THANK YOU!!!!

[Torsten Bronger]

Hallöchen!

Danny writes:

> The default Samsung applications manager seems to have no such list.
> I don't have/ever had other task managers installed.
>
> As the Komoot-App is able to do sleep mode navigation without any changes
> in settings, it seems to be something between the app and the device...
> Do the OsmAnd programmers listen in here?

Good question. I just wanted to create an issue report at
https://code.google.com/p/osmand/issues/entry but it says there:
"Users are kindly asked to initially open bug reports, enhancement
suggestions, and support requests here:
http://groups.google.com/group/osmand, so we can keep this Issues
list clean for our actual implementation roadmap."

I find this odd, as I already mentioned before on this list.
Obviously, this issue was not entered in the issue list, at least
nobody said so in this thread. So how to proceed? What I certainly
will not do is doing nothing.

So, unless a dev tells me that it's not an issue in Osmand or that
the issue was added to the issue tracker, I will ignore the above
statement and file it myself.

[Max]

Hi Danny and Torsten,

which OsmAnd version are you using?

Maybe it is related to this issue:
https://code.google.com/p/osmand/issues/detail?id=2313

Regards,
Max

[C G]

I've also experienced the same issue. With nightly build #2018D (bicycle mode).
I thought the issue was due to the presence of OsmAnd in auto-end list, but it didn't solve anything! Sorry...

[Danny]

I'm using #1986D.
That's 1.7.5 then??

So would an older version work? Which one, I did not really understand the other thread - I thought he said that 1.7.5 did NOT have problems with navigation in sleep mode, only nightlys after that?

I tried the official Google play release, and it has the same issue.
Suggestions??

Should I try an older version or not?
Danny

Am Donnerstag, 1. Mai 2014 08:26:54 UTC+2 schrieb Danny:

[Torsten Bronger]

Hallöchen!

Max writes:

> which OsmAnd version are you using?

1.7.5+

> Maybe it is related to this issue:

> https://code.google.com/p/osmand/issues/detail?id=2313

Yes, this is probably the same issue.  I subscribed to this

issue report.  Thank you!

Tschö,

Torsten.

[Danny]

#1986D seems to be 1.7.4-174?
So my issue has nothing to do with a problem only accuring after 1.7.5.

Danny

Am Donnerstag, 1. Mai 2014 08:26:54 UTC+2 schrieb Danny:

[pippo pluto]

i have found a solution to fix the problem , it not a bug but a feature di disable background navigation and made gps go to sleep for battery saving

can someone tell victor to make a guide for everyone?

[Torsten Bronger]

Hallöchen!

Am Dienstag, 6. Mai 2014 19:14:26 UTC+2 schrieb pippo pluto:

i have found a solution to fix the problem , it not a bug but a feature di disable background navigation and made gps go to sleep for battery saving

can someone tell victor to make a guide for everyone?

 

I have set all things as in your screenshots (actually, for almost as long as I have used Osmand) and still have this problem.

Tschö,

Torsten.

[Torsten Bronger]

Hallöchen!

Max writes:

> which OsmAnd version are you using?
>
> Maybe it is related to this issue:
> https://code.google.com/p/osmand/issues/detail?id=2313

Sorry, the message was garbled on its way to me. Now the link works
for me. Yes, this is probably the same issue. I subscribed to this
issue report. Thank you!

[Torsten Bronger]

Hallöchen!

Max writes:

> which OsmAnd version are you using?

1.7.5.

> Maybe it is related to this issue:

> https://code.google.com/p/osmand/issues/detail?id#13

The link is broken.

[Max]

Does it help, if you set "sleep mode" -> "GPS wake-up interval" to "Continuous"?
Look at screenshots of "pippo pluto" (this thread).
Is background service still running, after you turn off the screen and turn screen back on?

Regards,
Max

[Danny]

Thanks for the screenshots. Unfortunately, they did not solve the problem. Thanks though, I did not know where to find "continuous" (only found the "tracking interval 1s"), and now the GPS does NOT get lost any more!

Unfortunately, Osmand does not do any voice routing (in sleep mode) either.
As long as my screen is dark, I can move whereever I want without getting any instructions. (Not being disturbed by the "GPS signal lost." any more now...)
If the screen lights up, the voice gives me directions or even a new route is calculated.

Looks like all Osmand is sleeping when my screen sleeps... I've tried it from the main screen and as background app, no difference.

When I turn the screen back on, I see three icons in the top bar: osmand, osmand background navigation, and the GPS icon. As it takes up routing again immediately, I'd say the background service is still running, right?

Danny


Am Donnerstag, 1. Mai 2014 08:26:54 UTC+2 schrieb Danny:

[Max]

Is there an older OsmAnd (1.7.x) version, which is working in your case?
It is hard to find the reason, without knowing where to approximately look at.

Regards,
Max

[Danny]

Max, I've only tried 1.7.5 and 1.7.4-174 (I am new to Osmand). Which older version would advice me to try??
Thanks!

Am Donnerstag, 1. Mai 2014 08:26:54 UTC+2 schrieb Danny:

[Max]

I just tried to find out, since which version it does not work anymore.
But if this feature of OsmAnd never worked for you on this device, it is unlikely, that an older version will work.
AFAIK use of WakeLock didn't change in OsmAnd since a very long time.
If it does work with other applications, maybe they use another WakeLock.
Seems to be a device specific bug.

Regards,
Max

[Torsten Bronger]

Hallöchen!

Max writes:

> I just tried to find out, since which version it does not work
> anymore. But if this feature of OsmAnd never worked for you on
> this device, it is unlikely, that an older version will work.

You mean bisecting I suppose. I never did such a thing on Android.
Can you point me to good resources for how to do that, or maybe
enumerate the steps here? I'm quite competent in software
developing in general, but only on the desktop.

[Max]

I think a good starting point is to test old versions:
http://download.osmand.net/night-builds/

After that, in many cases, you should be close to the bug.
Now you look for the relevant commits within the corresponding time span.

You may use https://github.com/osmandapp/ or a git tool for that.

To exactly locate the bug, you probably want to build a snapshot of OsmAnd to bisect further.

You could use "git bisect" but I like to do it manually.

For example checkout old commits:

cd android
git checkout fb83b64ac456728c3c28cd3e445bdea89d654951

cd core
git checkout 10727c4a7110c92276b87bd7ff2db15afcb3a96c

cd resources
git checkout 0a15af5e3cdfecfbf73c882a6251bdc2d591ba02

and then build OsmAnd.

If you found one or several "bad" commits, you may want to modify the source code, to debug further.

Mostly it is recommendable to remove all build files between each build:
git clean -d -x -f
git reset --hard

Building native libs takes much time, so I recommend to skip build of native libs or to use ccache:
export NDK_CCACHE=/usr/bin/ccache

After that you upload and install the apk to your device via adb:
/path/to/platform-tools/adb install -d -r /path/to/OsmAnd-release.apk

Maybe you also want to start it via adb:
/path/to/platform-tools/adb shell am start -n net.osmand/.activities.MainMenuActivity
or
/path/to/platform-tools/adb shell am start -n net.osmand.plus/.activities.MainMenuActivity

Now happy testing. :-)

But be aware, that you don't catch all bugs with this approach, for example if a change of SDK or NDK causes a bug.

Regards,
Max

[Torsten Bronger]

Hallöchen!

Max writes:

> [...]
>
> Now happy testing. :-)

I just realised that I have to walk at least 10 minutes around the
block after each re-compile. :-)