Skip to content
Snippets Groups Projects
New look: Off

Anbox: F-Droid will often not refresh repos

    • Closed Imported Issue created by Administrator @root

    After fixing networking as described in #480 (closed), F-Droid still will not refresh repos and list apps. No error is displayed, and networking works fine in every other app.

    Edited
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Administrator mentioned in issue #495 (closed) · Imported

      mentioned in issue #495 (closed)

      By Nikhil Jha on 2020-03-22T02:48:41

    • Administrator changed milestone to %Anbox · Imported

      changed milestone to %Anbox

      By Oliver Smith on 2020-03-22T02:59:21

    • Administrator added help wanted type::bug labels · Imported

      added help wanted type::bug labels

    • Administrator
      Administrator @root · Imported
      Author Owner

      I believe this is due to #480 (closed). Edit: sorry, did read the other issue afterwards. Relevant information: #480 (comment 309027832)

      By Antoine Fontaine on 2020-03-22T08:21:25

      Edited by Administrator
    • Administrator added 1 deleted label · Imported

      added 1 deleted label

    • Administrator
      Administrator @root · Imported
      Author Owner

      Potentially relevant log

      04-24 13:46:14.814   111   382 I ActivityManager: Start proc 675:org.fdroi .fdroid/u0a38 for broadcast org.fdroid.fdroid/.receiver.StartupReceiver
04-24 13:46:14.854   111   123 W SchedPolicy: add_tid_to_cgroup failed to write '675' (Permission denied); fd=27
04-24 13:46:14.855   111   123 W ActivityManager: Failed setting process group of 675 to 0
04-24 13:46:14.855   111   123 W System.err: java.lang.IllegalArgumentException: Invalid argument: 675
04-24 13:46:14.855   111   123 W System.err: 	at android.os.Process.setProcessGroup(Native Method)
04-24 13:46:14.855   111   123 W System.err: 	at com.android.server.am.ActivityManagerService.applyOomAdjLocked(ActivityManagerService.java:20491)
04-24 13:46:14.856   111   123 W System.err: 	at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:21063)
04-24 13:46:14.856   111   123 W System.err: 	at com.android.server.am.BroadcastQueue.processCurBroadcastLocked(BroadcastQueue.java:274)
04-24 13:46:14.856   111   123 W System.err: 	at com.android.server.am.BroadcastQueue.sendPendingBroadcastsLocked(BroadcastQueue.java:315)
04-24 13:46:14.856   111   123 W System.err: 	at com.android.server.am.ActivityManagerService.sendPendingBroadcastsLocked(ActivityManagerService.java:17582)
04-24 13:46:14.856   111   123 W System.err: 	at com.android.server.am.ActivityManagerService.attachApplicationLocked(ActivityManagerService.java:6669)
04-24 13:46:14.856   111   123 W System.err: 	at com.android.server.am.ActivityManagerService.attachApplication(ActivityManagerService.java:6713)
04-24 13:46:14.856   111   123 W System.err: 	at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:539)
04-24 13:46:14.856   111   123 W System.err: 	at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2812)
04-24 13:46:14.856   111   123 W System.err: 	at android.os.Binder.execTransact(Binder.java:565)
04-24 13:46:14.899   675   675 W System  : ClassLoader referenced unknown path: /system/app/FDroid/lib/arm64
04-24 13:46:15.519   675   675 I ACRA    : ACRA is enabled for org.fdroid.fdroid, initializing...
04-24 13:46:15.603   675   675 I InstalledAppProvider: selectNotSystemSignature: systemSignature == null, querying for it
04-24 13:46:15.656   675   675 I InstalledAppProvider: excluding InstalledApps signed by system signatures
04-24 13:46:15.684   532   674 W MediaScanner: Error opening directory '/oem/media/', skipping: No such file or directory.
04-24 13:46:16.593   532   674 V MediaProvider: pruneThumbnails
04-24 13:46:16.599   532   674 V MediaProvider: /pruneDeadThumbnailFiles...
04-24 13:46:16.759   532   674 V MediaProvider: pruneThumbnails
04-24 13:46:16.768   532   674 V MediaProvider: /pruneDeadThumbnailFiles...
04-24 13:46:16.963   268   268 I VvmSimChangeReceiver: Received SIM change for invalid subscription id.
04-24 13:46:16.995   561   561 D AlertReceiver: onReceive: a=android.intent.action.PROVIDER_CHANGED Intent { act=android.intent.action.PROVIDER_CHANGED dat=content://com.android.calendar flg=0x20000010 cmp=com.android.calendar/.alerts.AlertReceiver }
04-24 13:46:17.021   561   701 D AlertService: 0 Action = android.intent.action.PROVIDER_CHANGED
04-24 13:46:17.057   675   703 I SDCardScannerService: getExternalFilesDirs /storage/emulated/0/Android/data/org.fdroid.fdroid/files
04-24 13:46:17.058   675   703 I SDCardScannerService: getExternalFilesDirs /storage/emulated/0/Android/data/org.fdroid.fdroid/files
04-24 13:46:17.061   675   703 I SDCardScannerService: sdcard files []

      collected using adb logcat

      By Antoine Fontaine on 2020-04-24T14:08:39

      Edited by Administrator
    • Administrator
      Administrator @root · Imported
      Author Owner

      also, for all it's worth, and for future reference: one can launch F-Droid from the command-line using adb shell am start org.fdroid.fdroid/.views.main.MainActivity.

      By Antoine Fontaine on 2020-04-24T14:11:32

      Edited by Administrator
    • Administrator marked this issue as related to #480 (closed) · Imported

      marked this issue as related to #480 (closed)

      By Antoine Fontaine on 2020-04-26T17:06:19

    • Administrator
      Administrator @root · Imported
      Author Owner

      I don't see anything in that logcat that relates to networking. F-Droid's networking is relatively plain Android, so it should work like other apps. There might be something odd if Anbox makes its network device something other than cellular or WiFi.

      By Hans-Christoph Steiner on 2020-04-27T11:50:06

    • Administrator
      Administrator @root · Imported
      Author Owner

      It seems that it will at least sometimes work

      fdroid-pinephone

      By Antoine Fontaine on 2020-04-27T12:13:54

    • Administrator changed title from Anbox: F-Droid will not refresh repos (maybe PinePhone specific) to Anbox: F-Droid will often not refresh repos (maybe PinePhone specific) · Imported

      changed title from Anbox: F-Droid will not refresh repos (maybe PinePhone specific) to Anbox: F-Droid will often not refresh repos (maybe PinePhone specific)

      By Antoine Fontaine on 2020-05-13T23:30:23

    • Administrator
      Administrator @root · Imported
      Author Owner

      Workaround:

      sudo apk add cmd:lxc-enter
sudo /usr/share/anbox/anbox-shell.sh
ip route add default dev eth0 via 192.168.250.1
ip rule add pref 32766 table main
ip rule add pref 32767 table local

      I'm closing this in favor of #480 (closed), because it really is the same issue (the first workaround was partial and didn't fix it on the java parts, I guess)

      By Antoine Fontaine on 2020-08-17T07:15:43

    • Administrator closed · Imported

      closed

    • Administrator
      Administrator @root · Imported
      Author Owner

      Im experiencing similar issue in pmOS on a samsung A3(a3ulte). So you might want to correct title @nikhiljha .

      By . |3vast.org on 2020-11-01T20:13:36

      Edited by Administrator
    • Administrator
      Administrator @root · Imported
      Author Owner

      Also this was also, a problem in vannila android or distributions based on it, not so common, but still happend especially after f-droid installation, ussually 2/3 first times you launched f-droid client. So this might notbe a problemwith anbox, but with f-droid client itself. @afontain

      By . |3vast.org on 2020-11-01T20:16:41

    • Administrator mentioned in issue #480 (closed) · Imported

      mentioned in issue #480 (closed)

      By . |3vast.org on 2020-11-01T22:05:01

    • Administrator
      Administrator @root · Imported
      Author Owner

      after discussion on matrix room, would like to share this references also given they might be usefull for further investigation on this issue, "yes I do https://gitlab.com/fdroid/fdroidclient/-/issues/1978. This would be the main one afontain, but there are other issues that also relate to this one, from what I can gather. like for example the ##1396 (closed) "Repo refresh on every user switch when users' locales differ" issue. ##1688 (closed) is not realted related to this problems but it part of the whole dynamic related tosuch,and also should be considered if a fix is ever made." all this are refering to f-droid client upstream codebase not anbox.

      By . |3vast.org on 2020-11-01T22:25:37

    • Administrator reopened · Imported

      reopened

    • Administrator
      Administrator @root · Imported
      Author Owner

      @afontain could you fix titlet then given your reopen the issue and this is not specific to pinephone? Cheers.

      By . |3vast.org on 2020-12-14T12:37:40

    • Administrator changed title from Anbox: F-Droid will often not refresh repos (maybe PinePhone specific) to Anbox: F-Droid will often not refresh repos · Imported

      changed title from Anbox: F-Droid will often not refresh repos (maybe PinePhone specific) to Anbox: F-Droid will often not refresh repos

      By Antoine Fontaine on 2020-12-14T15:27:08

    • Administrator
      Administrator @root · Imported
      Author Owner

      Anbox has been dropped from Alpine completely, so I'm closing this.

      See https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/33087

      By Newbyte on 2022-04-19T09:47:05

    • Administrator closed · Imported

      closed

    Please register or sign in to reply