anDGS

mdobbins · #1

anDGS is an Android client for the Dragon Go Server at dragongoserver.net and a local game recorder/editor.

Version 1.15 updates include:
- Fixed stack overflow fault the local game editor.
- Fixed opening keyboard in the DGS Player interface reconnecting to DGS.
- Improved the landscape layout to make it larger.
- Added a zoom to 7x7 (in addition to the previous zoom to 9x9) for both the portrait (labeled large and large7) and landscape (labeled landscape and landscape7) layouts.
- Centered the display of small boards.
- Added German and Chinese localizations.
- Added a Credits menu item to give credit to the Translators.

If you like and use this client with DGS, please put that you are a user of the andDGS client in your DGS Bio.

tealeaf · #2

Hi,

I just downloaded anDGS onto a T-Mobile G1 (HTC Dream - Android 1.6). I get a "force close" every time I try to check for new moves. Sorry that I can't give you any more information than that.

mdobbins · #3

tealeaf wrote:

Hi,

I just downloaded anDGS onto a T-Mobile G1 (HTC Dream - Android 1.6). I get a "force close" every time I try to check for new moves. Sorry that I can't give you any more information than that.

Thanks for the report.

1) Have you run an earlier version of anDGS on that phone? If so, what was the result?

2) Did you set your DGS username and password in the preferences menu?

3) What layout option did you select in preferences?

4) On the force close, was there an option to report the problem? If so did you select to report it? I have not seen the report in my developer account. That would give me a stack trace pinpointing the problem.

Also, please try to create a new game in the local editor and make a couple of moves there. It would be nice to see if there are any issues in that area on that particular hardware. (This requires an sdcard installed for local storage. The Android handbook does not say if this phone came with an sdcard installed, only that it supports one.)

tealeaf · #4

mdobbins wrote:

1) Have you run an earlier version of anDGS on that phone? If so, what was the result?

No, sorry. This was the first time that I installed.

mdobbins wrote:

2) Did you set your DGS username and password in the preferences menu?

Yes. I went back and checked that both were correct a few times as well.

mdobbins wrote:

3) What layout option did you select in preferences?

The default, which was "large". The board does seem to render in the background, without any stones shown, under the "Force Close" message.

mdobbins wrote:

4) On the force close, was there an option to report the problem? If so did you select to report it? I have not seen the report in my developer account. That would give me a stack trace pinpointing the problem.

No, just a close option I'm afraid.

mdobbins wrote:

Also, please try to create a new game in the local editor and make a couple of moves there. It would be nice to see if there are any issues in that area on that particular hardware. (This requires an sdcard installed for local storage. The Android handbook does not say if this phone came with an sdcard installed, only that it supports one.)

I'm pretty sure it came with an SD card installed. Either way, it definitely has a (16gb) card installed now.

Creating and editing a local game works fine. I hope this helps. Let me know if there's anything else I can do. I can install random .apk files if you want to test anything.

mdobbins · #5

tealeaf wrote:

The default, which was "large". The board does seem to render in the background, without any stones shown, under the "Force Close" message.

mdobbins wrote:

4) On the force close, was there an option to report the problem? If so did you select to report it? I have not seen the report in my developer account. That would give me a stack trace pinpointing the problem.

No, just a close option I'm afraid.

Seeing the empty board background under the force close, tells me that it faulted connecting to DGS. I have not seen problems in this area before. DGS seems to be having some network problems, maybe this is returning some result that I am not handling correctly. Please try to connect a few times at various times of the day and let me know if you do ever get a good result. If you never do, it is probably platform specific as I am not seeing it on my Droid. I will investigate more network failure conditions.

Yes, too bad I can't get a stack trace. Now it is like shooting in the dark.

Thanks

mdobbins · #6

One other thought, Does your DGS username or password contain any special characters (if you understand URL encoding I mean one that would require encoding to be sent to the server.) Since most of the strings sent the server are simple alpha-numeric I only currently URLEncode the comments send in a move. I may need to also URLEncode the username and password.

tealeaf · #7

mdobbins wrote:

One other thought, Does your DGS username or password contain any special characters (if you understand URL encoding I mean one that would require encoding to be sent to the server.) Since most of the strings sent the server are simple alpha-numeric I only currently URLEncode the comments send in a move. I may need to also URLEncode the username and password.

The password contains some standard punctuation symbols.

mdobbins · #8

Version 1.16 - Fixed some special characters in Password would fail to connect.

anDGS

Who is online