Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REQ] Alternative installation methods for the android app #582

Open
Axolord opened this issue Dec 29, 2024 · 8 comments
Open

[REQ] Alternative installation methods for the android app #582

Axolord opened this issue Dec 29, 2024 · 8 comments
Labels
enhancement New feature or request

Comments

@Axolord
Copy link

Axolord commented Dec 29, 2024

I am using a degoogled android phone (with CalyxOS) and would like to use your application to update my buds firmware.

Using apps from the play store is possible via the Aurora Store, but installing paid apps only works in conjunction with a Google Accound (that pays for the app) and I do not want to do that.

Would it be possible and acceptable for you to provide the APK either via Github releases (so that obtainium can install it) or maybe even F-Droid? You could ask users to donate, instead of paying (just like OsmAnd does it for example) or implement your own license verification system (like fairEmail).

Thanks for the app though, looks nice!

@Axolord Axolord added the enhancement New feature or request label Dec 29, 2024
@salihefee
Copy link
Contributor

salihefee commented Dec 30, 2024

You can clone the source and just build it locally. The icon of the locally built app says "Demo" but I don't know what's different on this version than the Google Play version since I haven't seen any locked or missing features.

@scynrays
Copy link

Hey, could you tell me how i could do that, i can't seem to find anything online

@salihefee
Copy link
Contributor

Install .NET SDK 8, Android SDK, and the android workload for .NET and run this command in the GalaxyBudsClient.Android project directory.
dotnet publish -f net8.0-android -c Debug -p:AndroidPackageFormats=apk -p:AndroidSdkDirectory={YOUR ANDROID SDK PATH} -p:DebugType=PdbOnly -p:EmbedAssembliesIntoApk=true
You can also edit the .csproj to remove the demo icon and other demo specific stuff.

@salihefee
Copy link
Contributor

@timschneeb Should I be telling people how to do this? I figured it would be okay since the source code is just publicly available. Also, is there anything different on the demo version?

@timschneeb
Copy link
Owner

Should I be telling people how to do this?

Yes, that's fine. My thought process behind this was that people who compile it themselves can use it for free and people who want the convenience of prebuilt APKs and auto-updates need to purchase it.

The demo version just disables some advanced features, like firmware updates. Otherwise, you can use it normally. It's more of a 'lite' instead of a 'demo' version.

Distributing the demo version to F-Droid (most people don't need those advanced features anyway) is on my TODO list.

@salihefee
Copy link
Contributor

Should I be telling people how to do this?

Yes, that's fine. My thought process behind this was that people who compile it themselves can use it for free and people who want the convenience of prebuilt APKs and auto-updates need to purchase it.

The demo version just disables some advanced features, like firmware updates. Otherwise, you can use it normally. It's more of a 'lite' instead of a 'demo' version.

Distributing the demo version to F-Droid (most people don't need those advanced features anyway) is on my TODO list.

I am pretty sure I can still do firmware updates with the version I compiled myself, I can access the tab and do the flashing process. (Though it does not work for me, both on the linux and android versions. I created an issue for it.) Is this how it is supposed to be?

@timschneeb
Copy link
Owner

Is this how it is supposed to be?

Yes, you can also pass the NotDemo=true build parameter to dotnet publish instead of editing the csproj file.

@salihefee
Copy link
Contributor

Is this how it is supposed to be?

Yes, you can also pass the NotDemo=true build parameter to dotnet publish instead of editing the csproj file.

Oh, I did not know how that parameter was passed to the .csproj so I edited it myself lol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants