There's already a Pachi Android app, unfortunately it uses an old Pachi version without patterns / dcnn so it's really weak. I'd be nice to have an up-to-date version with dcnn support.
On old phones you can hack around by replacing pachi binary after installing the apk and adding data files. I've had success using armv7 static binaries from the linux release, but apparently this doesn't work on newer phones: selinux rules are more strict and a ndk build is needed.
Todo:
ndk pachi build
The big one, could split it into another issue.
nodcnn build should be easy. dcnn build needs caffe as well as all its dependencies built under ndk. Will likely run into similar issues as the windows build, which is documented (ask me). Could go for dynamic build and package the libs instead of static build, easier.
Package Pachi data files into the app
App extracts pachi binary from resources and installs it on first run. Would need to do the same (or find better packaging method) for data files as well.
Add/update strength settings ?
Right now strength levels translate to thinking time, which is device dependent. Would be nice to have a dcnn/nodcnn toggle and have levels use playouts instead of time so strength stays the same everywhere. Maybe also an option to specify pachi command line to use instead of using levels (developer mode ?).
jopdorp
commented
1 year ago
Android hackers wanted !
There's already a Pachi Android app, unfortunately it uses an old Pachi version without patterns / dcnn so it's really weak. I'd be nice to have an up-to-date version with dcnn support.
On old phones you can hack around by replacing pachi binary after installing the apk and adding data files. I've had success using armv7 static binaries from the linux release, but apparently this doesn't work on newer phones: selinux rules are more strict and a ndk build is needed.
Todo:
ndk pachi build The big one, could split it into another issue. nodcnn build should be easy. dcnn build needs caffe as well as all its dependencies built under ndk. Will likely run into similar issues as the windows build, which is documented (ask me). Could go for dynamic build and package the libs instead of static build, easier.
Package Pachi data files into the app App extracts pachi binary from resources and installs it on first run. Would need to do the same (or find better packaging method) for data files as well.
Add/update strength settings ? Right now strength levels translate to thinking time, which is device dependent. Would be nice to have a dcnn/nodcnn toggle and have levels use playouts instead of time so strength stays the same everywhere. Maybe also an option to specify pachi command line to use instead of using levels (developer mode ?).