profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/sp4rkie/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

sp4rkie/debian-on-termux 246

HOWTO install plain Debian 10 (buster) on your non-rooted Android smartphone

sp4rkie/docsis-cable-load-monitor 52

CLI tool to monitor downstream load on DOCSIS cable networks

sp4rkie/pcap2audio 4

CLI tool to extract conversation audio from pcap files

sp4rkie/tracksplit 3

CLI tool to split WAV audio files into separate tracks based on periods of silence

sp4rkie/docsis-ts-scanner 2

CLI tool to display DOCSIS transport streams in a human readable way

sp4rkie/awesome-raspberry-pi 1

📝 A curated list of awesome Raspberry Pi tools, projects, images and resources

sp4rkie/termux-packages 1

Android terminal and Linux environment - packages repository.

sp4rkie/orgzly-android 0

Outliner for taking notes and managing to-do lists

startedpradeesi/record_audio_from_phone_line

started time in 12 days

issue closedjonasoreland/runnerup

program dies silently after a few kilometers with no data recorded at all.

smartphone: Sony G8441 Android version: 9 RunnerUp version: 2.3.6.0 battery optimizations: excepted (i.e. off) for this app

no special settings, just using Audio cue standard (default) and Target 'None' there were no GPS issues at the time of failure. osmand+ was running in parallel with no problems.

is there any additional info I can provide? do eventually exist workarounds? could I install a debug version of runnerup?

the issue occurs in about 1 of 10 cases

closed time in 17 days

sp4rkie

issue commentjonasoreland/runnerup

program dies silently after a few kilometers with no data recorded at all.

for the time being I close this now. I can't reproduce the problem after reinstall+reconfiguration nor can I provide better material for diagnosis. cheers.

sp4rkie

comment created time in 17 days

issue commentjonasoreland/runnerup

weirdos recording the first 400m: runnerup vs. osmand+

I today run with all filters off (as far as possible from GUI perspective). Red ist RU, blue is osmand+

It appears RU reacts more quickly in curves. osmand+ mostly lags a little.

Would be interesting to know what happens if GPS provides 'jumpy' data as encountered in the initial post

sshot_000 sshot_001 sshot_002 sshot_003

sp4rkie

comment created time in 17 days

issue commentjonasoreland/runnerup

weirdos recording the first 400m: runnerup vs. osmand+

probably a filter/ GPS accuracy issue. For the time being I close this...

sp4rkie

comment created time in 18 days

issue closedjonasoreland/runnerup

weirdos recording the first 400m: runnerup vs. osmand+

first of all: in the meantime I use runnerup each run. I like the flexible cue settings a lot. For navigation I run osmand+ in parallel. Nonetheless I had strange effects yesterday :-)

Please have a look at the attached picts. The blue track is recorded by osmand+. The red track is recorded by runnerup the same time on the same smartphone device. The first few 100m runnerup jumps around like crazy and gives me an outstanding running pace :-) After about 400m the phenomenon is over though. Both applications then show approximately the same track. The lower screenshot enlarges the track section where the issue fades out (i.e. the error disappears).

How can that be? Exist different data sources for GPS data on the same device?

sshot_000 sshot_001

closed time in 18 days

sp4rkie

issue commentjonasoreland/runnerup

weirdos recording the first 400m: runnerup vs. osmand+

How is the correlation to map paths?

not bad so far. To see the difference I now will deactivate 'Kalman filter' in osmand+. Then no filters should be active nowhere. I hope...

Should be visible in OsmAnd too, load the RU .gpx.

I loaded the jumpy RU track in osmand+. Looks exactly as in JOSM. No smoothing of the track takes place. It is shown as is. It appears 'kalman' in osmand+ is applied directly to live data only.

What device, version and type of terrain is this in? Same as #1037 ?

correct.

sp4rkie

comment created time in 18 days

issue commentjonasoreland/runnerup

weirdos recording the first 400m: runnerup vs. osmand+

thanks for answering. I always start osmand+ several minutes prior to starting the run and pressing record on RU. Please have a look at the attached image of the live recording shortly before I start . Again the blue track is recorded by osmand+. Of course the track floats around when still at home (blue 'mesh'). In this screenshot I removed the parts of the track regarding the return. I use JOSM for displaying *.gpx data.

RU gets started when I'm already running and satellites are safely synced since minutes. This normally works like a charm.

I'm not aware of any filters/smoothers in effect. Except there is 'Kalman filter' selected in osmand+.

Logging interval is set to 1s in both applications.

sshot_000

sp4rkie

comment created time in 18 days

issue openedjonasoreland/runnerup

weirdos recording the first 400m: runnerup vs. osmand+

first of all: in the meantime I use runnerup each run. I like the flexible cue settings a lot. For navigation I run osmand+ in parallel. Nonetheless I had strange effects yesterday :-)

Please have a look at the attached picts. The blue track is recorded by osmand+. The red track is recorded by runnerup the same time on the same smartphone device. The first few 100m runnerup jumps around like crazy and gives me an outstanding running pace :-) After about 400m the phenomenon is over though. Both applications then show approximately the same track. The lower screenshot enlarges the track section where the issue fades out (i.e. the error disappears).

How can that be? Exist different data sources for GPS data on the same device?

sshot_000 sshot_001

created time in 18 days

issue commentjonasoreland/runnerup

program dies silently after a few kilometers with no data recorded at all.

As far as possible I've now checked the other crashes for the symptoms above. It's always the same.

The app-frontend crashes/disappears but recording in the background continues for hours/ sometimes days. I always wondered why the 'location' symbol in the notification bar sometimes was on even when no abvious app was active at that time. Now I know some parts of the RunnerUp process framework still survived the crash...

sp4rkie

comment created time in a month

issue commentjonasoreland/runnerup

program dies silently after a few kilometers with no data recorded at all.

I now accidentally discovered something very odd. What has happened?

  • I yesterday started to run and record with RunnerUp at 08:43
  • after about 14km the app crashed or died (as reported)
  • looking again at the history today there actually is some activity recorded saying: activity start yesterday at 08:43 and distance of run 2.3km?!
  • I then started to play around with RunnerUp and got to the 'Recompute activity' menu item
  • I recomputed and - you won't believe it - a 28km distance recording (my complete running distance yesterday) shows up with all data in it (including many hours after the run)

conclusion: some background process still worked after the app crash without notice. So you will not discover this until selecting 'Recompute activity'

sp4rkie

comment created time in a month

issue commentjonasoreland/runnerup

program dies silently after a few kilometers with no data recorded at all.

thanks for the answer, there is nothing special in Android 9 for Sony regarding task killer. No other of my used app has such problem either. I'll try to install a Debug build if time permits...

sp4rkie

comment created time in a month

issue openedjonasoreland/runnerup

program dies silently with no data recorded at all.

smartphone: Sony G8441 Android version: 9 RunnerUp version: 2.3.6.0

no special settings, just using Audio cue standard (default) and Target 'None' there were no GPS issues at the time of failure. osmand+ was running in parallel with no problems.

is there any additional info I can provide? do eventually exist workarounds? could I install a debug version of runnerup?

the issue occurs in about 1 of 10 cases

created time in a month

startedSymeonChen/WakeUpScreen

started time in a month

startedlewish/asciiflow

started time in a month

startedjonasoreland/runnerup

started time in a month

issue commenttermux/termux-packages

Laggy SSH

setting 'wakelock' and 'disabling battery optimization' alone did not yet fix all the connectivity issues for me. In particular if it comes to establish a new connection. What finally fixed all these issues for me is to run a reverse tunnel and make all new connections via a proxy machine:

    -N -R 49465:localhost:8022 proxy

Connecting directly to 8022 of termux sometimes times out. If I try to connect via 'proxy' (port 49465 in this case) connection is always setup without any issues.

It appears some mechanism in Android does impact establishing new connections. Using a reverse tunnel for this works around the issue since the new connection is made via the proxy machine.

dredmorbius

comment created time in 2 months