I've made an update (2.7.0) which includes that solution.I think the above solution would definitely be good - it would need to list the packages also under the specific profile, so that you would see which ones are affected.
I've made an update (2.7.0) which includes that solution.I think the above solution would definitely be good - it would need to list the packages also under the specific profile, so that you would see which ones are affected.
Yes - I was actually just about to write that this would be a usable alternative as a 2ⁿᵈ choice actually :O) You'd then quickly see what's older than a cutoff etc.…Ok, what about sorting backups by date? This will avoid having to ask user about which date to filter to/from, and will allow you to see which backups have not been updated since any particular date.
Next update in beta adds sorting and filtering by date.Yes - I was actually just about to write that this would be a usable alternative as a 2ⁿᵈ choice actually :O) You'd then quickly see what's older than a cutoff etc.…
I think some bug has been introduced with the change:
I tried selecting 2 or more apps for restore and had no issues.I think some bug has been introduced with the change:
I select two backups for restore, one is moderately big - 200 MB, the other one huge - 2 GB. Individually they both restore fine - needing significant time to complete though.
When selected for restore together - the toggle box pops up, allowing me to toggle data and settings restore on/off. I leave it on - then a “restore” operation runs for cca 2 seconds, then reports success and it jumps back to the toolbox main window.
So obviously it doesn't restore properly…
Hello,Hi,
In the battery configuration wizard Oneplus is missing. It was here in 2.58. I have a Oneplus 9pro and the battery current flow is divided by 2. Please can you add again Oneplus with 65W charging.
Thanks.
Won't add debug window on a service that's not using shell commands at any time. Maybe zipping with root tools is fast, but when you have to go through Google apps' restrictions it can get very messy. Doesn't mean backing-up will be slow.@3c do you think you could add the possibility of displaying a running console for the ongoing backup/restore command? I'm thinking of having a button “display terminal output”-of-kinds that you could click when selecting the backup/restore operation, and you couldgsee the full zip/unzip flow…
The reason for this is the following: I'm currently experiencing issues with a single - albeit critical - backup.
I'm trying to backup FairEmail - it's an advanced email app. Its data directory isg1GB in size, mostly due to the downloaded email attachments. If I backup without the data option, it concludes momentarily - couple of seconds.
With the data option, the progress popup gets “stuck” momentarily on showing some file progress of 100%, and that's it - I let it rundovernight to make sure it's not just extra slow but it never finishes and the data is not backed up.
I have an older backup of this app with data, so something is happening now that's causing the zipping to either not start or not finish...
The zipping of the data directory of the app in Termux takes let's say 30 seconds so runs fast.
That's why I'd like to see what the zip operation during backup chokes on. Anyhow live terminal display isn't necessary per se - if the ongoing operation output could be tee'd to some log somewhere during the operation (not after finishing obviously) that'd be enough to inspect what's happening.
Can you try sending a support request from app settings, help and support? It should include crash stack trace to help fix this asap.Not sure if it is my phone or the app, but 3C Toolbox continually crashes since upgrading to 2.7.0d. I have not yet tried downgrading.
Samsung Note20 Ultra 5G, Android 12.
(Requesting support from the app does not work, it said something about not being able to attach an empty file. I just emailed logs that I attached manually.)
Right, skip that - I'm thinking in Linux terms - everything as a shell process... :O)Won't add debug window on a service that's not using shell commands at any time. Maybe zipping with root tools is fast, but when you have to go through Google apps' restrictions it can get very messy. Doesn't mean backing-up will be slow.
Yeah, it must've been getting stuck on something there - indeed i had /data/data/... in mind.Anyway, I assume your device is rooted and you're referring to internal data (eg /data/data/...) ? Because if not, that's a whole different story. If you're backing-up external data, that is yet another story.
That said, the app must be stuck on a specific file, and in the past special files may have caused this but it has been long fixed.
Yeah, that's where I looked - didn't create a zip there - I thought it might be creating it temporarily somewhere else - that's why I speculated it might not be finishing. So it didn't even start...To actually know if zipping starts or does not finish, please check backup folder, data/<ID>/<package_name>.zip file if it exists, its size and possibly content.
What i meant - the "Backing up..." popup window (I hope that's what it says in English - translating from Japanese here) pops up - and I the top progress bar stays at "0/1" - logically. The bottom progress bar - it would go to 100%, as of the first file - and then it would freeze there...What do you mean stuck momentarily (and what after that moment?) on showing some file (what file?) progress of 100%.
Maybe you can check that file for size, type, permissions, etc ?
Thanks. When I tried sending that directly to Gmail it failed saying something about an empty file, but I saved the 10 logs and manually emailed them.Can you try sending a support request from app settings, help and support? It should include crash stack trace to help fix this asap.
Empty file doesn't mean it failed. I need the crash files to solve this.Thanks. When I tried sending that directly to Gmail it failed saying something about an empty file, but I saved the 10 logs and manually emailed them.
The app seems to run, but my widgets aren't working and I keep getting notified that 3C Is crashing. I have noticed other "odd" behavior from my phone today, not sure if 3C is causing it or "it" is causing an issue with 3C. I will attempt to downgrade to prior version.
(Downgrading to 2.9.6g appears to have fixed the issue)
With 2.6.9g installed now, the reporting works, but these aren't the logs I expect we want. I just emailed you again and referenced this thread. The logs from 2.7.0d are attached in a zip file. I can't really read them, but they do show a widget crash I believe. Thanks.Empty file doesn't mean it failed. I need the crash files to solve this.
If widgets are not working and considering the UI is not crashing it's likely one of the widget data that fails to load.
In any case sending a support request should help fix this as long as the crash files are included.
You can find those in /sdcard/Android/data/ccc71.at.free/support.
So far I haven't received any file? Did you add a ref to this thread/post?
Got the files, thanks. Indeed widgets are crashing because of lack of permission, new restrictions enforced by Google since beginning of November, for which I didn't pay attention:With 2.6.9g installed now, the reporting works, but these aren't the logs I expect we want. I just emailed you again and referenced this thread. The logs from 2.7.0d are attached in a zip file. I can't really read them, but they do show a widget crash I believe. Thanks.
(Widgets are working after downgrade)
This permission is supposedly automatically granted on Android 12, and requires user activation on Android 13.Caused by: java.lang.SecurityException: Caller ccc71.at.free needs to hold android.permission.SCHEDULE_EXACT_ALARM to set exact alarms.
I will watch for an update and let you know. Thanks!Got the files, thanks. Indeed widgets are crashing because of lack of permission, new restrictions enforced by Google since beginning of November, for which I didn't pay attention:
This permission is supposedly automatically granted on Android 12, and requires user activation on Android 13.
Please try 2.7.0f published minutes ago (allows time for Google review), which should solve your issue.