[App] AndDiscovered - Android exploration tracking tool modeled after EDDiscovery

[Gen.Fussypants]

As for the screencapping, I wonder if it'd be possible to make an on-the-fly OCR? Ie, without taking a picture (my phone is REALLY slow these days when it comes to taking pics), just hold it up with the camera running and see if it can OCR it directly. Various barcode scanners can do it, but I'm guessing that's mostly because barcodes are designed for scanning and aren't really needing OCR.
I've never played with screencap/OCR before, so no idea how much support Android provides developers here.

The screenshot would come from in-game. Currently F10 (current in-game resolution) or Alt-F10 (Very high resolution)

Edproxy understands when images have been taken and informs AndDiscovered. This is how I currently do the Photo Gallery. The OCR would occur when you are adding a System. There will be a button that says something like "OCR this planet". You then hit "F10" in-game. Edproxy will tell AndDiscovered about the image, AndDiscovered will pull the image, and then the OCR will attempt to read the text off the image.

 

[Iron Orchid]

I hadn't seen this before - can it work at the same time as EDDiscovery?

 

[Gen.Fussypants]

I hadn't seen this before - can it work at the same time as EDDiscovery?

Yes.

EDDiscovery runs on the PC directly and accesses the netLog directly. For AndDiscovered we use Edproxy to get to the netLog. Both applications may access the netLog at the same time.

However, AndDiscovered (currently) cannot import any "extra" information that EDDiscovery may be allowing you to put in today. Things such as Notes or extra information about Stars/Planets. An import is on my TODO list, however, I need more time in a day.

 

[Gen.Fussypants]

In the last 24hrs I have experienced, and received reports on, a crash when running AndDiscovered. It appears that between 12/3 and 12/5 (UTC) there was a massive amount of systems "modified" within EDSM. Thus when AndDiscovered attempts to synchronize with EDSM we eventually get an Out-of-Memory (OOM) error. This in turn causes the application to ANR or exit altogether.

AndDiscovered should be able to handle this amount of data coming back from EDSM without issue. I am actively looking into why we get the OOM error, and how to address it. I apologize for the inconvenience.

Gen. Fussypants
a.k.a CMDR Duck Rodgers

 

[AnthorNet]

In the last 24hrs I have experienced, and received reports on, a crash when running AndDiscovered. It appears that between 12/3 and 12/5 (UTC) there was a massive amount of systems "modified" within EDSM. Thus when AndDiscovered attempts to synchronize with EDSM we eventually get an Out-of-Memory (OOM) error. This in turn causes the application to ANR or exit altogether.

AndDiscovered should be able to handle this amount of data coming back from EDSM without issue. I am actively looking into why we get the OOM error, and how to address it. I apologize for the inconvenience.

Gen. Fussypants
a.k.a CMDR Duck Rodgers

Yeah I've corrected a lot of system yesterday

 

[Gen.Fussypants]

Version 2.6
- Fix critical crash when receiving massive amounts of data from EDSM.
* The updates will take a little longer to finish out, but it is safer and uses considerably less memory.
- Merge from 3.0: Updated database index tables. This gives approx. 10x improvement in database read response.
- Merge from 3.0: Updated reference system selection algorithm.
* Previously too many system where collinear, and thus not able to produce a coordinate.
* Now the algorithm will pull 90deg right, left, top, and bottom. It will also pull from straight out along the traveled vector.
* This reduces the number of required references when in the core from 10~15 down to 5~7.

- - - - - Additional Content Posted / Auto Merge - - - - -

Yeah I've corrected a lot of system yesterday

No worries. This should have been handled better in AndDiscovered from the beginning. It is expected that EDSM could provide massive amounts of data at any time. Besides, it gave me an excuse to push out some database and reference system selection improvements from 3.0 early.

 

[AnthorNet]

Version 2.6
- Fix critical crash when receiving massive amounts of data from EDSM.
* The updates will take a little longer to finish out, but it is safer and uses considerably less memory.
- Merge from 3.0: Updated database index tables. This gives approx. 10x improvement in database read response.
- Merge from 3.0: Updated reference system selection algorithm.
* Previously too many system where collinear, and thus not able to produce a coordinate.
* Now the algorithm will pull 90deg right, left, top, and bottom. It will also pull from straight out along the traveled vector.
* This reduces the number of required references when in the core from 10~15 down to 5~7.

- - - - - Additional Content Posted / Auto Merge - - - - -



No worries. This should have been handled better in AndDiscovered from the beginning. It is expected that EDSM could provide massive amounts of data at any time. Besides, it gave me an excuse to push out some database and reference system selection improvements from 3.0 early.

Nice then ^^
I'll continue a bit the maintenance process

 

[Gen.Fussypants]

To those upgrading to 64-bit:
You will need to update Edproxy to point to the new "NetLog" path. You an do this from within Preferences. I also recommend that you copy over all of your old log files.

 

[dognosh]

How did I miss this !?!?
Added to TOOLS section of sticky

 

[Gen.Fussypants]

Thank you!

I got moved somehow over to the "Community creations" sub-forum so I didn't get much visibility. I was kindly moved back though!

 

[Gen.Fussypants]

Version 2.7
- Fix crash when EDSM provides an empty system name during synchronization.
- Force the keyboard to show when entering distances in the Distance dialog. (Thank you Micha!)
- Add in missing Gas Giant planet types: Ammonia, Water, Helium-rich, and Water Giant. (Thank you Micha!)

 

[Iron Orchid]

I like the interface but seem to be having trouble with entering distances - it pulls up the data (very slowly) for a couple of systems and then stops. Any ideas what is going on?

I was going to use this instead of EDDiscovery for entering the distances (save all that alt tabbing) but it's just too slow when you switch to the data entry screen - nothing seems to happen for a while and if you are lucky the distances box is filled.

 

[Gen.Fussypants]

When you start the app for the first time, or after not using it for awhile, I perform a sync with EDSM. For some reason this is currently impacting local database performance. Once the sync is finished populating the distance list should be near instant. On my current platform populating the distance list takes around 15 milliseconds.

Unfortunately I did NOT present the fact that I am actively performing the EDSM sync as I didn't think this would be an issue. It wasn't until recently that I started getting very large EDSM syncs and experienced the problem. The best I can say right now is give it a while. On first sync, or a very large sync due to EDSM database clean-up, it can take anywhere from 15-30 minutes. After this syncs should be in the 5-10 second range.

I am sorry you are having difficulties. I will try and see if I can make it better in 3.0.

 

[Iron Orchid]

When you start the app for the first time, or after not using it for awhile, I perform a sync with EDSM. For some reason this is currently impacting local database performance. Once the sync is finished populating the distance list should be near instant. On my current platform populating the distance list takes around 15 milliseconds.

Unfortunately I did NOT present the fact that I am actively performing the EDSM sync as I didn't think this would be an issue. It wasn't until recently that I started getting very large EDSM syncs and experienced the problem. The best I can say right now is give it a while. On first sync, or a very large sync due to EDSM database clean-up, it can take anywhere from 15-30 minutes. After this syncs should be in the 5-10 second range.

I am sorry you are having difficulties. I will try and see if I can make it better in 3.0.

That explains it then - tried it a few minutes ago and it seems a lot quicker. Probably all those explorers adding extra data! Could you add a Syncing Light or something as not seeing it doing anything is a little bit frustrating. Keep up the good work - its definitely a bit less resource hungry than Eddiscovery.

 

[Matt L. Icious]

I was going to use this instead of EDDiscovery for entering the distances (save all that alt tabbing) but it's just too slow when you switch to the data entry screen - nothing seems to happen for a while and if you are lucky the distances box is filled.

I gave it a shot today as I really like the idea of using my tablet as a second screen. However, I am experiencing similar issues. I see a 'loss of sync' after the first jump: Anddiscover stops tracking my route, the distance list does not update, or maybe after minutes. EDProxy also stops to see my client.
However, if I forcibly quit and restart Anddiscover, sync is immediately restored and the distance list populates immediately. Doing so after every jump is quite cumbersome.
Something is wrong here, my usage, my setup, my networking, or Anddiscover locks up some way.

Good idea, great work, but sadly it doesn't work for me as-is.

 

[Gen.Fussypants]

* It may be an hour or so for the Play Store to update it's sites


Version 2.8
- Allow database read and write at the same time.
- Updated EDSM first install database to be more current.

- - - - - Additional Content Posted / Auto Merge - - - - -

I gave it a shot today as I really like the idea of using my tablet as a second screen. However, I am experiencing similar issues. I see a 'loss of sync' after the first jump: Anddiscover stops tracking my route, the distance list does not update, or maybe after minutes. EDProxy also stops to see my client.
However, if I forcibly quit and restart Anddiscover, sync is immediately restored and the distance list populates immediately. Doing so after every jump is quite cumbersome.
Something is wrong here, my usage, my setup, my networking, or Anddiscover locks up some way.

Good idea, great work, but sadly it doesn't work for me as-is.

I just updated the Play Store to version 2.8. This version allows read and writes to the database to occur at the same time. This should help with the delay in the distance list. However, I do not know if it will help with the sync issue you are seeing as these are two different databases internally. This sounds to me more of an issue on the part of Edproxy not eventing out on new system change.

Can you go into some more detail on "Edproxy also stops to see my client"? Do you mean the connection between AndDiscovered and Edproxy is no longer visible in the "connected" list within Edproxy? If so, does the connection "come and go"?

 

[dognosh]

If you want more people to use your program, you have to give instructions to those who are not "IT" minded
The wiki is not enough.

1. Download AndDiscovered from PLAY store
2. Download edproxy from https://bitbucket.org/westokyo/edproxy/downloads
(latest version https://bitbucket.org/westokyo/edproxy/downloads/edproxy-win32-2.1.4.exe)
3. Run edproxy, click on "file", then "preferences", then enter your "Netlog Path"
For HORIZONS it is C:\Users\your username here\AppData\Local\Frontier_Developments\Products\elite-dangerous-64\Logs
For non-horizons it is something like this C:\Users\your username here\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1001\Logs
4. After setting log path press "OK" , then press "Start"
5. Read the wiki https://bitbucket.org/westokyo/anddiscovered/wiki/Home
6. Edit your appconfig.xml file and add VerboseLogging="1" to the network section, example :
<Network
Port="0"
upnpenabled="1"
LogFile="netLog"
DatestampLog="1"
VerboseLogging="1"
>
( location in HORIZONS C:\Users\your username here\AppData\Local\Frontier_Developments\Products\elite-dangerous-64\AppConfig.xml )
( location in NON-HORIZONS C:\Users\your username here\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1001\AppConfig.xml )
7. Run AndDiscovered

p.s. as I have already got verbose set to 1, do users have to do this manually with your program or is it automatic ? If it is auto, remove step 6

 

[Gen.Fussypants]

If you want more people to use your program, you have to give instructions to those who are not "IT" minded
The wiki is not enough.

1. Download AndDiscovered from PLAY store
2. Download edproxy from https://bitbucket.org/westokyo/edproxy/downloads
(latest version https://bitbucket.org/westokyo/edproxy/downloads/edproxy-win32-2.1.4.exe)
3. Run edproxy, click on "file", then "preferences", then enter your "Netlog Path"
For HORIZONS it is C:\Users\your username here\AppData\Local\Frontier_Developments\Products\elite-dangerous-64\Logs
For non-horizons it is something like this C:\Users\your username here\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1001\Logs
4. After setting log path press "OK" , then press "Start"
5. Read the wiki https://bitbucket.org/westokyo/anddiscovered/wiki/Home
6. Edit your appconfig.xml file and add VerboseLogging="1" to the network section, example :
<Network
Port="0"
upnpenabled="1"
LogFile="netLog"
DatestampLog="1"
VerboseLogging="1"
>
( location in HORIZONS C:\Users\your username here\AppData\Local\Frontier_Developments\Products\elite-dangerous-64\AppConfig.xml )
( location in NON-HORIZONS C:\Users\your username here\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1001\AppConfig.xml )
7. Run AndDiscovered

p.s. as I have already got verbose set to 1, do users have to do this manually with your program or is it automatic ? If it is auto, remove step 6

Thank you for the feedback! I will look into updating the documentation.

Appconfig is updated automatically. There is no need to manually set it.

 

[disorganise]

If you want more people to use your program, you have to give instructions to those who are not "IT" minded
The wiki is not enough.

1. Download AndDiscovered from PLAY store
2. Download edproxy from https://bitbucket.org/westokyo/edproxy/downloads
(latest version https://bitbucket.org/westokyo/edproxy/downloads/edproxy-win32-2.1.4.exe)
3. Run edproxy, click on "file", then "preferences", then enter your "Netlog Path"
For HORIZONS it is C:\Users\your username here\AppData\Local\Frontier_Developments\Products\elite-dangerous-64\Logs
For non-horizons it is something like this C:\Users\your username here\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1001\Logs
4. After setting log path press "OK" , then press "Start"
5. Read the wiki https://bitbucket.org/westokyo/anddiscovered/wiki/Home
6. Edit your appconfig.xml file and add VerboseLogging="1" to the network section, example :
<Network
Port="0"
upnpenabled="1"
LogFile="netLog"
DatestampLog="1"
VerboseLogging="1"
>
( location in HORIZONS C:\Users\your username here\AppData\Local\Frontier_Developments\Products\elite-dangerous-64\AppConfig.xml )
( location in NON-HORIZONS C:\Users\your username here\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1001\AppConfig.xml )
7. Run AndDiscovered

p.s. as I have already got verbose set to 1, do users have to do this manually with your program or is it automatic ? If it is auto, remove step 6

Spot on. Even being an IT tech years back there's plenty I don't get. I got here from your sticky and was intrigued by an android app....then realised I'd need to figure out edproxy and maybe eddiscover too and....that's a lot of reading for the limited game time I have available.
Your summary just reinspired me to take a look

 

[Matt L. Icious]

Hi!

Version 2.8
- Allow database read and write at the same time.
- Updated EDSM first install database to be more current.

I just updated the Play Store to version 2.8. This version allows read and writes to the database to occur at the same time. This should help with the delay in the distance list. However, I do not know if it will help with the sync issue you are seeing as these are two different databases internally. This sounds to me more of an issue on the part of Edproxy not eventing out on new system change.

Can you go into some more detail on "Edproxy also stops to see my client"? Do you mean the connection between AndDiscovered and Edproxy is no longer visible in the "connected" list within Edproxy? If so, does the connection "come and go"?

First, thanks for your work. I got V2.8 via auto-update last night, will try it today, and report back as soon as I have. One additional observation/suggestion: While Anddiscover does long-running operations in the background there is currently (2.7) no feedback in the UI, right? Adding some 'job busy' indicator would work wonders to stop impatient people like myself from forcefully terminating the program mid-job.

By "stops seeing my client" I mean, as you guessed correctly, that my client drops from the EDProxy 'connected' list after some time. OTOH I have not seen the Anddiscover connection 'dot' go from green back to yellow or red. Once I restarted Anddiscover, the connection reestablishes, but IIRC under/from a different port. I did not record what happened in detail in the rare occurrence of 'reconnect after long runtime'. Not very scientific, I disquality for the Cannon .

My working assumption was: Anddiscover enters a long-duration operation - i.e. the database thing - and being inactive/unresponsive for a long time causes EDproxy to timeout/close the socket/remove the target from the observer list. So I have really high hopes that the new concurrent solution will fix that.

More later.