search

jensstein / oandbackup

backup manager for android
Other
543 stars 194 forks source link

couldn't find oab-utils - running in legacy mode, please report this to the developer #222

Open vi opened 5 years ago

vi commented 5 years ago

Meizu 15 Plus, Android 7.0 (Flyme 7.0.3.1A)

timur-g commented 5 years ago

I had this error when F-Droid upgraded 0.3.0 to 0.3.2-x86 instead to 0.3.2-arm (Huawei P7, Android 5.1)

vi commented 5 years ago

Yes, it's version 0.3.2-x86 [suggested] [installed] on aarch64 device.

Pressing 0.3.2-arm [DOWNGRADE]...

x > a?

jensstein commented 5 years ago

that seems like a bug on fdroid's side if they suggest an x86 version for your arm device. at the same time there is a bug in the build configuration which affects arm64 so even if you get the right version from fdroid it's not going to work until the next version (0.3.3). (also, you need arm64, not arm) https://gitlab.com/fdroid/fdroiddata/issues/1366

vi commented 5 years ago

Installed 0.3.2-arm.

Still getting the same error.

Also:

10-31 00:22:59.565 21344 21344 E oandbackup: error during AssetHandlerTask.onPostExecute: dk.jens.backup.AssetsHandler$AssetsHandlerException: error copying asset arm64-v8a/oab-utils
meijkl commented 5 years ago

Just upgraded to 0.3.3 via F-Droid, still the same . Message "couldn't find oab-utilities - running in legacy mode ..."

My setup: Nexus 5x, LOS 15.1 with microg, no Gapps etc.

jensstein commented 5 years ago

@vi just verifying: are you running 0.3.2-arm, not 0.3.3-arm64? 0.3.3 is the latest release and your device needs the arm64 or the universal version. but looking at the fdroid page there seems to be a problem with which versions they offer because the latest are 0.3.3-x86_64 0.3.2-x86 0.3.3-arm64 i'll contact them to find out if it's a problem i or they or we both have to fix.

if you can't get it from fdroid, there are packages on my gitlab repo: https://gitlab.com/jensstein/oandbackup/-/jobs/116043498/artifacts/browse

@meijkl which abi version of the apk are you running? your nexus is 64bit as far as i know so you also need either 0.3.3-arm64 or 0.3.3-universal

meijkl commented 5 years ago

Sorry, I didn't see the x86 problem.

My case is special - I installed oandbackup via Nanodroid and the x86 version was automatically chosen (don't know why). Now I've reinstalled Nanodroid without oandbackup and installed it manually afterwards via F-Droid. But I had to choose the arm64 version manually, F-Droid automatically selected the x86-64 version.

My problem is solved - thanks for your efforts!

Kelvino9 commented 5 years ago

Same here. F-Droid still recommends the x86 architecture on arm devices. I had to uninstall 0.3.2-x86 and manually install 0.3.3-arm64. The correct version shows no errors after launching it. Thanks.

DamienCassou commented 5 years ago

I have a One+ 1 (bacon) and just installed 0.3.3-arm64 manually. I get 2 errors:

DamienCassou commented 5 years ago

My mistake: my architecture is arm, not arm64. I have no more problems, thank you.

roizcorp commented 5 years ago

and for us with arm64?

Kelvino9 commented 5 years ago

@roizcorp pick the arm64 version manually in F-Droid like all of us with arm64 Phones. F-Droid has problems detecting the correct architecture for oandbackup.

roizcorp commented 5 years ago

yep it works...thanks

mase76 commented 5 years ago

Yes, reinstalling the arm64 build solved the issue. However F-droid still recommends x86_64.

jensstein commented 5 years ago

there is an issue on fdroid's gitlab repo where i mention this problem: https://gitlab.com/fdroid/fdroiddata/issues/1366

jensstein commented 5 years ago

the packagers at fdroid are reporting that the universal apk flavour doesn't work. it works for me but i can only test on armv7 devices so could i get some of you to try this apk and report if it works or not and which abi (arm, arm64, x86, or x86_64) your device has? https://gitlab.com/jensstein/oandbackup/-/jobs/116206298/artifacts/file/apks/oandbackup-universal-debug.apk

and it seems like they rely on the output of the aapt command to determine which abi the built apk targets - this causes some difficulty since rust isn't supported in an splits.abi block in the gradle build configuration (as far as i can tell) and therefore the aapt output doesn't contain a native-code field. i can probably make a work-around but suggestions are welcome :)

zzzardoz commented 5 years ago

@jensstein: Your universal apk works without any issues here (Oneplus One/arm)!

meijkl commented 5 years ago

Just tried to install on my Nexus 6p/AICP Nougat/arm64. Failed with message "package seems to be corrupt".

On a Nexus 5x with LOS Pie prerelease the installation fails too with message "App not installed".

Kelvino9 commented 5 years ago

Debug apk works fine on Redmi Note 4/ AICP Oreo/ arm64

@meijkl try to re-download with a different browser.

meijkl commented 5 years ago

Had to uninstall oandbackup, afterwards the installation worked.

timur-g commented 5 years ago

Same as Issue 212

timur-g commented 5 years ago

Please close this issue if resolved.

vi commented 5 years ago

After manually picking arm64 version of oandbackup it works.

Shall F-Droid behaviour of picking the wrong version or misusing version string as architecture variant specifier be in scope of this issue?

hvdwolf commented 5 years ago

I still have this issue on a rooted Sofia 3GR intel unit. No matter whether I use the universal 0.34 from F-droid, or the universal, signed-x86.apk or signed-x86_64.apk from https://gitlab.com/jensstein/oandbackup/-/jobs/125132334/artifacts/browse.

Therefore my restores do not work on this Intel unit.

Edit: The oab-utils are in /data/data/dk.jens.backup/files. When running them from a rooted terminal I get a "Segmentation fault"

tristan-k commented 5 years ago

Is this fixed?

vi commented 5 years ago

Maybe the error message should be extended with a hint that user may be using the wrong version of oandbackup?

chilliger commented 5 years ago

I am still getting this message when opening the app. When I try to update the app through F-Droid I get this message: ![]() F-Droid thinks that I want to downgrade. What are my options here other than reinstalling and losing all configurations?

DamienCassou commented 5 years ago

I have the same issue.

mvglasow commented 5 years ago

@chilliger same here. 0.3.3-x86_64 has internal version code 4303 while 0.3.5-universal has 305, therefore F-Droid thinks you are downgrading when in fact you are upgrading. Seems to be an issue specific to F-Droid, as I can’t find any hint at such a version code in the source here; however that particular version does not seem to be on the regular repo any longer.

Downgrade via F-Droid did not work for me as the Android package manager rejected the replacement package.

You could try downloading the 0.3.5-universal APK to a PC from F-Droid, then installing it via adb:

adb install -r -d dk.jens.backup_305.apk

This requires ADB installed on your PC and enabled on your device. The command line options tell ADB to replace the existing package and force a downgrade.

Alternatively, if you have a local terminal app and su on your device, you could download the APK to your device, then open a terminal, run su and do:

pm install -r -d dk.jens.backup_305.apk