Client merge requestshttps://staging.gitlab.com/fdroid/fdroidclient/-/merge_requests2017-07-10T21:02:35Zhttps://staging.gitlab.com/fdroid/fdroidclient/-/merge_requests/258WIP: Android 6 Device Owner unattended install2017-07-10T21:02:35Zusername-removed-16558dominik@schuermann.euWIP: Android 6 Device Owner unattended installThis is a very early merge request, just to show how we could use Android 6's "device owner" PackageInstaller API.
As can be seen by comparing https://github.com/android/platform_frameworks_base/blob/59701b9ba5c453e327bc0e6873a9f6ff87...This is a very early merge request, just to show how we could use Android 6's "device owner" PackageInstaller API.
As can be seen by comparing https://github.com/android/platform_frameworks_base/blob/59701b9ba5c453e327bc0e6873a9f6ff87a10391/services/core/java/com/android/server/pm/PackageInstallerSession.java#L211 with
https://github.com/android/platform_frameworks_base/blob/marshmallow-release/services/core/java/com/android/server/pm/PackageInstallerSession.java#L221
the PackageInstaller API has been enabled for "device owners" on Android 6.
So I hacked a proof of concept code and it looks like it works.
If you like to test:
1. get this branch
2. To make F-Droid a device owner, do "adb shell" and then "dpm set-device-owner org.fdroid.fdroid/.receiver.DeviceOwnerReceiver" (this does not require root). However I suspect that if we want to execute this without adb and in the context of F-Droid it will require root.
3. Install any app
I am not entirely sure what else can be done as a device owner, I will look into this more later. The only drawback I saw was that a notification is shown (but no further user interaction was necessary), as seen on the screenshot:
![device-2016-04-14-154250](/uploads/e04a7941a25fc032644f00a67f83c08c/device-2016-04-14-154250.png)
What do you think?https://staging.gitlab.com/fdroid/fdroidclient/-/merge_requests/416WIP: modernize update scheduling2017-09-29T13:50:14Zusername-removed-24982WIP: modernize update schedulingThis is just the first step towards modernizing the scheduling of updates, including index and auto app updates. Android 5.0 introduced `JobScheduler` which will try to opportunistically schedule jobs based on whether the device is idle...This is just the first step towards modernizing the scheduling of updates, including index and auto app updates. Android 5.0 introduced `JobScheduler` which will try to opportunistically schedule jobs based on whether the device is idle, there is good wifi, its connected to power, etc. This can help us drive the update process entirely to when the device is plugged in, connected to the home wifi, and idle.
The annoying part is that this requires putting the work into a new `JobService`. `UpdateService` is currently an `IntentService`. So in this merge request, there is just a shim `JobService`. Ideally, the full update procedure would happen in the `JobService`, and heed its `onStopJob()` callback.
This is only very lightly tested, I'm posting it for feedback on how its implemented @commonsguy @relan @pserwylo @ssinelnikau1.1https://staging.gitlab.com/fdroid/fdroidclient/-/merge_requests/435Allow the priorities of repos to be changed via the UI2017-04-26T07:40:34Zusername-removed-25042Allow the priorities of repos to be changed via the UIAn earlier change improved support for repo priorities, however it didn't add a UI to change these priorities. This change adds support in the UI for changing repo priorities.
![repo-priorities](/uploads/e97f073c36c27df2d3cb8e266f8824...An earlier change improved support for repo priorities, however it didn't add a UI to change these priorities. This change adds support in the UI for changing repo priorities.
![repo-priorities](/uploads/e97f073c36c27df2d3cb8e266f88243e/repo-priorities.mp4)1.1https://staging.gitlab.com/fdroid/fdroidclient/-/merge_requests/455Better offline support2017-09-02T21:10:27Zusername-removed-25042Better offline supportThe simple part of this is to add a "No Internet" banner to the top of the "Latest", "Categories", and "Updates" screens. The more complex part is that when viewing an apps details while offline, it will present the user with the option ...The simple part of this is to add a "No Internet" banner to the top of the "Latest", "Categories", and "Updates" screens. The more complex part is that when viewing an apps details while offline, it will present the user with the option to "Download later". This stores a flag against the app in the database, so that whenever they visit the Updates tab, it will show a list of apps that have been marked for subsequent download. These will then automatically download next time F-Droid receives a network connection.
There are likely a handful of edge cases when this will need to be ironed out, but for the most part, it is a fully working feature.
Fixes #94, #884, #885.1.1https://staging.gitlab.com/fdroid/fdroidclient/-/merge_requests/543Lint fixes2017-09-04T14:03:24Zusername-removed-49982Lint fixesI fixed some of the issues that appear in Android Studio after running `Analyze` -> `Inspect Code`. The majority of these fixes are very simple, and I just used the automatic fix option in Android Studio. I've also removed all dead code ...I fixed some of the issues that appear in Android Studio after running `Analyze` -> `Inspect Code`. The majority of these fixes are very simple, and I just used the automatic fix option in Android Studio. I've also removed all dead code that's currently in the app.
There are still tons of issues remaining. Many of them are more complex than the code I'm changing here, so it would be good if someone with more knowledge of the F-Droid code could have a look at the `./gradlew lint` and `Inspect Code` output.https://staging.gitlab.com/fdroid/fdroidclient/-/merge_requests/578WIP: Mirror support2017-10-04T20:38:18Zusername-removed-1345cdesai@lineageos.orgWIP: Mirror supportAddresses #35Addresses #351.1https://staging.gitlab.com/fdroid/fdroidclient/-/merge_requests/588Stable v0.1022017-10-04T20:38:02Zusername-removed-803513atcharatip9035@gmail.comStable v0.102https://staging.gitlab.com/fdroid/fdroidclient/-/merge_requests/5922 commits: Floating search button animation & [Fix] AppDetails: Card covere...2017-10-08T14:57:37Zusername-removed-14063082 commits: Floating search button animation & [Fix] AppDetails: Card covered inside header graphicHi guys :kissing_closed_eyes:
I can't split the 2 commits (Git not happy) because I didn't create branches, it was my mistake I think.
The 2 commits are:
* Floating Search Button animation (shaking)
Ref: https://gitlab.com/f...Hi guys :kissing_closed_eyes:
I can't split the 2 commits (Git not happy) because I didn't create branches, it was my mistake I think.
The 2 commits are:
* Floating Search Button animation (shaking)
Ref: https://gitlab.com/fdroid/fdroidclient/issues/868 <br>
A simple shaking Search button, you can adapt at your convenience.<br>
I adapted the code to avoid multiple user clicks on the button and several opening of app list.<br>
Works great :)
* There is no more overlap and better for users.
Ref: https://gitlab.com/fdroid/fdroidclient/issues/1030 <br>
We can do more with coordinatorLayout, I will study the subject lol.<br>
(v) Tested in all themes<br>
(v) Portrait/landscape orientation<br>
(v) Call from 1st tab and Categories