Android 1.8/1.10 support thread

[alep]

Hi,
Finally i have a good news: it works! I can read everything so i think it s ok!
Thank you very much for help and so fast...
My son look like happy so i ll buy it soon!
Good job Alep

Wonderful!!
Soon I'll apply the same fix on the paid version and re-open it to Galaxy Tab 3.
Thank you for the help you gave.

[shogi4fun]

I must admit I am really amazed by how much people are helping me by giving ideas and contributions to it on this forum and by email.

It's enjoyable to be creative and work on a nice project - more enjoyable than playing the game.

One more thing... somebody has complained by email that the close-to-pointer-tap function we discussed can be annoying if you want to correct a mis-tap which was a little out of target.
So I thought to enable the no-pointer-move-on-tap feature ONLY if tap is following a finger raise by a short amount of time (probably less than a half second is good). This way a mis-tap can be corrected easily, double tapping is still easy and swipe-raise-tap action still works.

Are you ok with that?

I would assume it should be okay.

[srulz]

Hi alep, great thread you're having here!

Anyway, I have just gotten myself a new phone (Note 3) and I was wondering what is the "correct method" for me to transfer the data/saves/etc between my current Note 1 to my new phone. Could you please explain step-by-step? I have installed in on my internal memory I think (not SD).

Oh, and by the way:

I must admit I am really amazed by how much people are helping me by giving ideas and contributions to it on this forum and by email.
Thank you all for every contribution you give to make this port better, you guys are great.

You are just awesome with all your support, so you deserved all this!

Thanks!

[alep]

Anyway, I have just gotten myself a new phone (Note 3) and I was wondering what is the "correct method" for me to transfer the data/saves/etc between my current Note 1 to my new phone. Could you please explain step-by-step? I have installed in on my internal memory I think (not SD).

Well, I'd simply:

- run the game on the old device, hit "Change Configuration" on startup, select "Import/Export" and then "Export savegame data to zip" to export savegame data to a file
- make the export available to the new device, by using a shared sd card or via network
- install the game on the new device and perform the first run and data download
- run the game on the new device, hit "Change Configuration" on startup, select "Import/Export" and then "Import savegame data from zip", picking the file you prevoiously transferred

This will let you keep savegames, but addons must be re-downloaded.

[Romulus]

Brand new Nexus 5. Stock, not rooted running android 4.4.

Problem: Bought game (Alessandro Pira) and installed fine. Crashes on startup and goes straight back to homescreen. Have tried to enable debug but it doesnt save that setting when pressing start.

Any ideas?

[alep]

Brand new Nexus 5. Stock, not rooted running android 4.4.

Problem: Bought game (Alessandro Pira) and installed fine. Crashes on startup and goes straight back to homescreen. Have tried to enable debug but it doesnt save that setting when pressing start.

Any ideas?

I'm sorry, but after a short check it turned out that Android 4.4 has a feature that clashes with my BfW port, even on SDK emulator the game does not start.
I think I can handle it, but it could take some time. So for now I just removed Nexus 5 from supported devices on Google Play. I will report to you soon about this.
If any of you with Nexus 5 or any Android 4.4 device bought the game and wants a refund, please send me transaction info by email and I will refund you, no problem.

In the meanwhile I released a new version with some of the feature we discussed about. On Google Play more info about added features.
Up-to-date sources are here:

http://www.alessandropira.org/wesnoth_a ... 18b.tar.gz

[Romulus]

Thanks for your quick reply.
I really like Wesnoth so I am happy to wait for a while.

Hopefully you can find a fix soon.

[alep]

Thanks for your quick reply.
I really like Wesnoth so I am happy to wait for a while.

Hopefully you can find a fix soon.

I think managed to fix this problem. Or at least, the game now runs successfully on SDK emulator. Unfortunately, I still don't have a Nexus 5 device to check if the conflict is fixed on the device too.
So, I uploaded the fix on the FREE version of my port and reopened it to Google Nexus 5.
Can you please try if the free version runs successfully? (please make sure that you try the version named "1.10.7-18c" or "1.10.7-18d", if not wait for Google Play update)
If you can confirm it works I will patch and reopen the paid one too.

[DropOfPeace]

Hello there,

I have a question to the android port of bfw, see this topic there:
http://forums.wesnoth.org/viewtopic.php?f=4&t=39609

Thank you.

Keep up your good work.

[shogi4fun]

Hi again,

read on GooglePlay (as also discussed here):

When tapping very close to pointer in pointer follows finger mode, pointer will not be moved *only if finger has just been raised*, in order to make mis-tapping correction easier

Are you sure the code is in this version, have you tried it and is it working?

I can 'easily' produce a mis-tap.
If the following is not understandable and you can't reproduze it in this way, I should have to make a video to show you.

Doing the following (only an example, also the same on other menus):
- start/load a game
- tap on "menu" and also untap (pulldown is shown)
- tap anywhere on the screen, move your finger over the "Settings"-text from the menu (can be done slowly)

Than there are 2 different tests (exactly only the second one is the test):
- untap, immediately tap the same place and also immediately untap => settings are opening (as expected)

But in the 2nd test:
- untap, immediately tap only a little bit below the place and also immediately untap => the close-tapping-feature should also open the settings (ignoring that you moved a little bit), but instead it goes back to the round shown.

Thanks in advance.

[alep]

Are you sure the code is in this version, have you tried it and is it working?

Yeah, you are right, sorry for that.
I tweaked the code which detects a close-tap and probably I used a too small value for tap distance check.
I just updated a new version with a little higher distance threshold. Can you please check if it's good on your device?

Also, I'm asking for opinions about another thing.
I added pinch-to-zoom, which many people asked. However, IMHO it does not feel really good because BfW zoom management is slow and definetly not smooth, and this is a thing I really cannot change.
So, at least for me, pinch-zooming is a little weird on BfW.
Whato do you think? How does it perform on your device? Do you like it as is or you have suggestions?

So, I uploaded the fix on the FREE version of my port and reopened it to Google Nexus 5.
Can you please try if the free version runs successfully? (please make sure that you try the version named "1.10.7-18c" or "1.10.7-18d", if not wait for Google Play update)

Of course, also last released version (1.10.7-19a) is good for this.


Sources are available here:

http://www.alessandropira.org/wesnoth_a ... 19a.tar.gz

[shogi4fun]

I just updated a new version with a little higher distance threshold. Can you please check if it's good on your device?

I'm sad to say, that it's still not working. I can't recognize even any effect.

For example, when it's the following situation:

My finger is still touching the tablet.

Untapping, and tapping again only a little bit lower I can easily mis-click "back to round 4".
That mustn't be the case.
At what value (pixels?) have you set the distance threshold?
And in what time I need to do it? (You told something about half a second, but from start of untap i'm sure it would be such fast.)

By the way: if you've implemented a limited time to do it, the distance threshold could be even much bigger.

I added pinch-to-zoom, which many people asked. However, IMHO it does not feel really good because BfW zoom management is slow and definetly not smooth, and this is a thing I really cannot change.
So, at least for me, pinch-zooming is a little weird on BfW.
Whato do you think? How does it perform on your device? Do you like it as is or you have suggestions?

It's realy not nice to use.
But on the other side it's not disturbing.

And even if it's slow, it's easy to do (and to know), so even if it's only for changing one time, I didn't know to do it instead (menu? settings? ...)

Of course, also last released version (1.10.7-19a) is good for this.

And also I've confirmed, that I use the right version.

[alep]

I'm sad to say, that it's still not working. I can't recognize even any effect.

Well, first of all don't be sad If it does not work I definitely want to know, so say it happily.

Anyway, what you are telling me sounds a bit weird, and I am still trying to figure how it can be... I tried on a Galaxy Tab 2 and the effect looks pretty evident to me.
Also, the distance threshold is not changed in the release you notified the problem, and in the last one it was increased.
The only thing I have added is time checking, so probably the problem is there... I will check that code. If I cannot find anything I will release a new version with some more logging on and ask you to enable "Send debug info to developer" on run, so I hopefully will be able to understand what exactly is happening on your device.

At what value (pixels?) have you set the distance threshold?

That is device-dependant.
In previous version it was obtained this way:

ViewConfiguration.get(context).getScaledTouchSlop();

In the last version I applied a factor which is around 3 to that (it's not exactly three because the check is made on squares).
So, for example, if getScaledTouchSlop() returns 16 pixels after the factor added in the last release the distance threshold is increased to 45 pixels.

And in what time I need to do it? (You told something about half a second, but from start of untap i'm sure it would be such fast.)

Until the last release it was half a second... in the last release I increased it to 0.7 seconds.

And even if it's slow, it's easy to do (and to know), so even if it's only for changing one time, I didn't know to do it instead (menu? settings? ...)

Well, I used sofware keyboard hotkeys (+ and -) to do zooming.
Thank you for your opinion.
Please try it on... what I am really interested is: is it really not disturbing on the long run? I am worried about getting in the way of two finger-scrolling.

[alep]

If I cannot find anything I will release a new version with some more logging on and ask you to enable "Send debug info to developer" on run, so I hopefully will be able to understand what exactly is happening on your device.

Ok, I've uploaded a new version with more logging.
What I need you to do is:
- wait for 1.10.7-19b upgrade from google play
- run the game, hit "Change Configuration" button on startup
- select "Startup options" and then check "Send debug info to developer"
- hit "Ok" to close the menu and then select "Start game"
- startup a game and do everything to repeat the mis-tapping on the menu
- immediately after mis-tapping hit menu key (if your device has it) or tap and hold three fingers to open popup menu
- from the menu select "Send debug info now"
- let me know when you did that, as I could need to find your log among others

[shogi4fun]

- wait for 1.10.7-19b upgrade from google play
- run the game, hit "Change Configuration" button on startup
- select "Startup options" and then check "Send debug info to developer"

And also after clicking "Ok", I clicked "Startup options" again and checked, if it's selected yes, it is!

- hit "Ok" to close the menu and then select "Start game"
- startup a game and do everything to repeat the mis-tapping on the menu
- immediately after mis-tapping hit menu key (if your device has it) or tap and hold three fingers to open popup menu
- from the menu select "Send debug info now"

But there is no such thing to select.

There are only two lines (under the text "Options" with a line):
- Pointer relative movement
- Hide keyboard button

After next start I've checked "Send debug info to developer" again. This time it's unselected. Should it be selected only temporarely till next start?

Oh, I got it working - just when I want to send this post
: (little) thing to fix: when choosen "keyboard icon not shown" (as it was before), it happend like written above

So with keyboard icon shown ...

... sent.

(At least I hope so. Maybe a second one ...)