17 October 2016

CFish 171016 Android Chess Engine

CFish Android Chess Engine

C port of Stockfish by Ronald de Man

  • Chess960 support probably is missing a few lines.
  • Skill level support has been commented out.
  • Not fully tested on Windows.

Download:

armv7a-pgo : HERE
arm64v8 : HERE

Update:

sorry about previous build, it's don't work with flag "-flto" (LinkTimeOptimization) in gcc.

armv7a-pgo : HERE
arm64v8 : HERE
arm64v8 : HERE (new)

52 comments:

  1. Can't start engine on my Huawei p8 Lite on Android 6.0

    ReplyDelete
  2. Can't start engine on my Huawei p8 Lite on Android 6.0

    ReplyDelete
  3. arm64v8, this architecture worked for other engines like brainfish and crochess, but not this one

    ReplyDelete
  4. Di droidfish maupun cfa engine ini nggak ke-load (armv7), mungkin butuh sedikit perbaikan?

    ReplyDelete
  5. Replies
    1. This comment has been removed by the author.

      Delete
    2. with LTO(LinkTimeOptimization) is better than without LTO, but this engine doesn't work with LTO :(

      Delete
  6. No work under HawkChess.

    ReplyDelete
  7. Armv8-noflto working well now on my device, thanks

    ReplyDelete
    Replies
    1. Mauricio, can you tell me please, what device do you have? I managed to work only arm7.pgo on arm7 devices, 64 bit version not working.

      Delete
    2. As I said before, i'm using a Huawei P8 Lite, the noflto version is the only one that works

      Delete
    3. This comment has been removed by the author.

      Delete
  8. May I ask what the difference is between cfish and regular stockfish?

    ReplyDelete
    Replies
    1. It's same algorithm and node, but written in C code. (Original SF using C++). Based on test C is faster than C++.

      Delete
  9. I see, so even the noflto version is faster than normal stockfish?

    ReplyDelete
  10. None of them works on ASUS arm8 64bit, under Droidfish and Cfa. :(

    ReplyDelete
    Replies
    1. arm7 working fine under Droidfish and Cfa, on arm7 device!

      Delete
    2. No, engine exits (Cfa)-engine failed to start (Droidfish), all 3 versions :(

      Delete
    3. It's will be more useful if you run engine in terminal emulator and see what's your error code.

      Delete
  11. Is possible add engine vs engine(different engines) under DroidFish?.

    ReplyDelete
    Replies
    1. Yes, it's one of TODO list in DroidFish code.

      Delete
    2. Can you do it,please?

      Delete
  12. Tested on MTK6752 1.6 Ghz x 8 cores, Lollipop 5.0, CfA 5.2.3, 256MB hash, 1 minute:
    arm7: 1902 knps
    arm8: exits
    arm8.flto: no uci box
    arm8.noflto: 2410 knps (Highest ever on this device, all engines)

    ReplyDelete
    Replies
    1. Gurcan, arm8.nofito is working? On 64 bit device?

      Delete
    2. 2410 knps, it's faster than my pc LOL.

      Delete
    3. Those are some crazy high nodes! What device are you using Gurcan?

      Delete
    4. I did the same test on my phone, got 1709kn/s on armv8

      Delete
    5. I did the same test on my phone, got 1709kn/s on armv8

      Delete
    6. Those are some crazy high nodes! What device are you using Gurcan?

      Delete
    7. Lenovo Vibe S1! I have choosen it because there is no little.BIG config. It's really a true octa core. All A53 Cortez and 1.6 ghz.

      Delete
  13. None of arm8 versions working for me in Droidfish and C4A.
    Anyway, thanks for your great work Aprijal

    ReplyDelete
  14. Mauricio Guevara, you should stop posting this double posts mate.

    ReplyDelete
  15. Mauricio Guevara, you should stop posting this double posts mate.

    ReplyDelete
  16. Yeah sorry, I don't why that happens, must be some kind of bug in my browser

    ReplyDelete
  17. Mauricio, I hope you noticed my planned double post as well ;)

    ReplyDelete
  18. Thought you had the same bug for a second :)

    ReplyDelete
  19. Thought you had the same bug for a second :)

    ReplyDelete
  20. Please, give another try to arm8.

    ReplyDelete
  21. Is it recommended to enable large pages?

    ReplyDelete
    Replies
    1. You shouldn't enabled it, it's for windows API. I will remove it for next build.

      Delete
  22. Works on my mobile but doesnt work on my tablet

    ReplyDelete
  23. Android 6, arm7 doesnt work, from terminal segmentation fault.

    ReplyDelete