search

wlky / AnkiDroid-Wear

Anki for Android Wear devices
GNU General Public License v2.0
48 stars 11 forks source link

Updating the project #26

Open LemmusLemmus opened 3 years ago

LemmusLemmus commented 3 years ago

I have the same problem as issue #23, as such I'm currently unable to answer "good" on any card. I am therefore attempting to edit the source code and build a new APK to fix the issue. However, a lot has, unsurprisingly, changed since 2016/2017 and I can no longer build the project as it is with the latest version of Android Studio.

Do you happen to know which version of Android Studio was used when this project was being actively developed?

wlky commented 3 years ago

Hi @LemmusLemmus, could you tell me why you closed the issue? I recently tried to update the project to the current wear version as well, but it seems that repositories and especially google support libraries have completely changed or are offline now.

LemmusLemmus commented 3 years ago

@wlky I closed the issue since it wasn't very clear, I was merely struggling with a multitude of things that I have now to some extent resolved. I suppose the issue could be reformulated to something along the lines of "updating the code of the project". I've been able to build an APK in Android Studio 2.3.2 (albeit with two ignored errors, one of which is a deprecated command), but it seems like I'm only building the either the wear or mobile module, instead of the entire project. I'm unsure as to what I'm doing wrong. Any help would be appreciated. Edit: I was mistaken, I was apparently only able to import the APK to the wear device when I built the APK as a signed release, instead of a mere debug version. One oddity that I have noticed is that the build I made is double the file size of your latest release here on GitHub, and when starting the app I get a warning that the app is old and might not work properly, an error that I do not get when using your release. EDIT 2: This "oddity" might be related to issue #28? EDIT 3: Resolved in #28, thanks wlky!

Might it be worth attempting to move the code to one (or two) major new versions at a time and fix the errors that occur along the way? Or would recreating the project in the newest version be "easier", if updating the project to the latest version is highly desirable?

LemmusLemmus commented 3 years ago

The app still works well on Wear OS despite its age. However, when I first installed it from the play store I had to use the third-party app "wear installer" to extract the wear component to the watch, as Google has relatively recently ditched support for "the legacy embedded app model".

wlky commented 3 years ago

I think it would be really cool to migrate this app to the new android wear sdk. As I said I have tried once a couple of weeks ago but I gave up after a couple of hours because too much had changed. Maybe it would be easier to create a new project and then migrate the features piece by piece 🤔

LemmusLemmus commented 3 years ago

@wlky Just out of curiosity, what are your general thoughts regarding backwards compatibility and the minimum sdk version?