-
Notifications
You must be signed in to change notification settings - Fork 41
List of tested devices #7
Comments
If I'd get any feedback, I could do that – but until now I did not. Leaving this issue open for exaclty this purpose: Everybody can enter his/her own "tested devices" this way, so we hopefully end up with an appropriate list :) Here are the devices I'm using Adebar with currently: Phones:
Tablets:
Your turn: next post list at least one MTK device, please :) |
So here’s my list (very shooooort one xD): Phone:
Later on I’ll update this post. :) |
adebar
was tested
Update: see here. Linked the page back here a) for details and b) suggesting to add more devices this way. Would be nice to have a little feedback where my little tool is running 😇 |
|
@inktrap Thanks for the details – but I'd prefered to leave them here, and the wiki-edit to me :) Now I've got to clear a "collusion" as I've made some editing as well: as the wiki has no "branches", I usually push its updates whenever a new version of the code is released; otherwise "new features" already listed in the wiki would cause confusion to people who stick to the releases (well, for the moment we now have to live with that – until the next release is done). My fault, I should have "locked" the wiki (done now). So some details from your contribution "got lost" – which is why I reverted your edit here. Hope you understand this ;) |
No problem! btw, I am running Android 5.1.1, that detail got "lost". |
That detail never was part of your post here "in the issue". But it's not lost anyway, as it's part of the wiki page – but feel free to re-edit your above post (click the "pen icon" on its header) to include it there as well :) |
Had several issues:
I don't know if you intend to try to work around the adb issue, but it should be documented, so that the user knows what to try if they get 0-byte, 41-byte or otherwise fixed-size small backup files or all apks on older androids. |
Thanks for the detailed report, @Irfy ! I've updated the documentation accordingly (Tested Devices and Known Issues). See the latter place for a partial work-around on the ADB issue: you can add I'm not sure if I should implement the "argument quoting" (escape_arg) in Adebar, e.g. adding a new config var so the user can easily switch it on. Seems you're not the only one hit by this issue (in the SE post, I count at least 3 people with it). Shouldn't be a big deal – feel free opening a separate issue for that. |
(Had an issue with ADB. Doesn't sound like the one described in Known Issues. Bit I fixed it with the patch in PR #15.) |
Thanks, @chaotix- – just added to the wiki. Will take a look at the other issue ASAP. |
Also successfully using it now with the Wileyfox Swift running CyanogenOS 12.1 / Android 5.1.1. Device is rooted, no issues found so far. Thanks to this device I was now able to improve the "DualSIM related details" which I wasn't able to test before, and to add a bunch of new details to the device documentation page :) |
@IzzySoft I managed to use your script to transfer most of my Apps & data (63 of 82): Thank you, it really saved me a lot of hassle. |
Thanks @jreast – glad to read! Just added your device to the Wiki (Tested Devices). As for the CRLF: I assume you've cloned on Windows, and not in Cygwin itself? Thanks for the hint, which I just integrated with the Wiki as well (Installation). |
Hello,
Thanks a lot! |
Thanks @JimboJoe – Wiki updated again 👍 |
Just tested with Coolpad Porto S (E570), Android 5.1 and I am getting zero-length applications backup files. I tried with ADB 1.0.31, 1.0.32 (the same as on the phone) and 1.0.36 (latest), but without any change. Trying directly |
@Jakuje that's nothing Adebar can change. Adebar just creates the script for the backup, which then is performed by ADB. You could ask about that issue at Android.SE, hopefully some ideas pop up (please include whether this happens for all apps, or just for specific ones – in the latter case it could simply be they've "opted out", having set |
adebar-cli and userbackup runs on Xiaomi Redmi3 Pro running CM12.1 although lots of 0/41 byte files produced. AUTO_CONFIRM=1 doesn't work. Haven't tried sysbackup or any restores yet. |
Thanks @walkjivefly – wiki updated! AUTO_CONFIRM indeed seems to have trouble with some devices (I remember one where I wasn't able to get it to work either). As for the 0/41 byte files: not much we can do about that if the app is refusing being backed up. Xposed with BackupAllApps is the only work-around known to me. |
@IzzySoft Success on Amazon Kindle Fire HD 8 (7th Gen) backup and restore. Thanks again! |
Thanks, @jreast – what Android version is that? And "stock ROM" I guess? |
@IzzySoft, yes stock ROM, not rooted, Fire OS 5.6.2.0 |
Confirmed devices:
Hi izzy, thanks for this tool and your Fdroid repo! |
Thanks @5c0tt-b0t – and wow, the first TV box reported, great! Wiki page updated. Glad you like it – enjoy Adebar (and my repo 😃)! |
Two more devices!:
(Another TV box, different CPU, safe to say it works on the two most popular TV box brands!) |
Thanks again! Added to the wiki. Great to know that most Android TV boxes should be covered as well! Though I'm not sure whether that can be said based on the chip alone. Also depends on their ROM… |
I work with Android TV box firmware (just for fun, to improve the usually bad chinese firmware found in most of them) unlike Phones they are very particular with paths (directories) so do not tend to differ with ROM as the dev has to use the standard paths found in the stock ROM, luckily they are very AOSP in that sense, they only differ slightly on /root paths. |
Good to know about the Android TV backgrounds – thanks for sharing! Btw, my Lenovo tablet is a MediaTek device, no issues with that. And of course, PRs are welcome! I cannot think of new features all for myself and usually only add one when I miss it. Having so many project to work on, my work on Adebar is not that continuous either 😆 Your backup idea sounds interesting as well (reminds me of rsyncbackup, which I use on my PC). Curious about your restore approach then. But that's a different issue (this one already is quite long; Github already has problems loading all its JS stuff along in my browser, so preview, auto-complete etc. are already not working; need to split this)… |
It will be automatically restored, the script can push the restore script to: For most devices
For Magisk users
The contents of these directories are launched on boot so the backup will be initiated automatically, no PC, magic happens in the background, could also let the user know when its completely done by outputting a file in internal storage called "RestoreComplete" or "RestoreFailed" (the latter containing any errors). P.S great news on Mediatek! I see no problems arrising with AllWinner. |
As the title suggests, it would be good to know on which devices
adebar
has been tested, esp. for those who just heard aboutadebar
.The text was updated successfully, but these errors were encountered: