-
Notifications
You must be signed in to change notification settings - Fork 414
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
Publish release #695
Comments
If you want a new update, please do something: Build OpenLauncher from master branch on your own (or CI build) and use that as your default launcher for two weeks. Then report back if everything is OK, or less good than before. OpenLauncher is in maintainence mode since a while and I rather not release a update which doesn't work on other more important areas --- because I won't have the time to fix it again. So please do that and let me know here. Thank you. |
there you go: https://github.com/MASTERdjango/openLAUNCHER, It just works... and yes PR (#637) (PWAs) works... expect bugs... I just built the APK today. |
@MASTERdjango Everything merged on master is available from CI build apk. No need to upload some apk for somebody. |
Are you still in need of beta testers? I'm happy to try a dev build as well, if that would help. The current stable release seems pretty buggy. |
I started testing debug build from CI from 4abc6d2 too, seems to be working just fine so far, in fact better than latest release on F-Droid. I'd say make it a preview/beta release on F-Droid, it does have such a feature. Those who need stable version can continue to use stable release, those who want to test preview can opt-in in F-Droid settings. |
Used for over a week, no issues whatsoever while the published version was crashing for me on Android 13 (I exported and imported the same settings). |
Crashes a lot on Android 11 for me too. |
@MASTERdjango, @gsantner, @tplloi, @jan-kiszka and @chrysn, For what little this is likely worth, while my background is in IT (with scripting and basic development experience) I am not a mobile developer by trade. A previous example using a generic online guide did not go down very well to say the least. It might be impractical but it would be appreciated if Artifact expiration could be disabled. |
For my use, I find the master version better than 0.7.4. I use it daily. |
Via working with ChatGPT I have been able to setup my own build environment based around Debain running within Windows Subsystem for Linux (WSL) version I. PromptGood evening, The source code can be found at https://github.com/OpenLauncherTeam/openlauncher OutputSure, here are the steps to build the Open Launcher Android application on a Debian 9 install within WSL 1 and Windows 10 as the host: Install necessary tools: Java Development Kit (JDK) version 8 or above Open a terminal window and navigate to the directory where you'd like to store the project. Set JAVA_HOME to the path of your installed JDK. Run the command $ sdkmanager "platforms;android-29" "build-tools;29.0.2" to install the necessary SDK components. Navigate to the root directory of the project. The APK file will be generated in openlauncher/app/build/outputs/apk/debug or openlauncher/app/build/outputs/apk/release, depending on the build mode selected. To be more useful: sudo apt-get install openjdk-8-jre To use sdkmanager (https://developer.android.com/tools/sdkmanager), I then downloaded the Linux port of ther SDK-platform tools (https://developer.android.com/tools/releases/platform-tools). After tripple reading the instructions and using some french, I came up with the following file struture. PATH/android_sdk
As to be expected I then had to update the debian image at some point. Within the src folder I executed the following commands cd /mnt/c/Users/03520/Desktop/android_sdk/ I have the following shell script to help automate building my own custom release which sits next to the src folder and I call from within the src folder.export ANDROID_SDK_ROOT=/mnt/c/Users/03520/Desktop/android_sdk/ veryMinorTweaks
[code]
diff --git a/app/src/main/java/com/benny/openlauncher/activity/SettingsActivity.java b/app/src/main/java/com/benny/openlauncher/activity/SettingsActivity.java
diff --git a/app/src/main/res/xml/preferences_about.xml b/app/src/main/res/xml/preferences_about.xml
[/code] |
There was a release on F-Droid a month ago. \o/ |
Yes, release is out on F-Droid, but for some reason it is created for ancient devices (Android 4.2+) and as the result doesn't support auto-updates. Would be great to have release for modern versions of Android. |
Well, that would break it for people running ancient versions of Android. Maybe then there should also be a version that is built for older Android for a while, as long as it does not get complicated. |
No one should be using ancient versions of Android at this point, they're horribly insecure. But those who do can still install older version and continue using it, I doubt they expect latest and greatest 12 years later. |
Much of the world is poor and lacks access. |
Access to older versions of the software? |
OpenLauncher is not developed anymore. You might use something else. There was a final release before that. Older versions can be found on F-Droid. |
@gsantner it would be great if you can trigger CI again and upload apk to GitHub release. F-Droid removed the app from their store and GitHub pruned Actions artifacts, so there is no way to download the app anymore. |
You should find it on F-Droid Archive. Expect nothing to happen anymore. |
As I said they have removed it from F-Droid. Here is 1.0 release apk I extracted from my phone in case someone needs is: open-launcher.zip |
Please consider tagging a version as a new release, be it 0.7.5 or 0.8.0. Such a version should then have it easy to get updated in F-Droid.
I see that a lot of bug fixes have accumulated (and experienced disappearing widgets myself) since late 2020, and in particular PR #637 (PWAs) would be a great improvement to see in a released version.
The text was updated successfully, but these errors were encountered: