Trying to systemize a few apps by using you apps mgr but keep getting a not enough room type error...new pixel 6a with 90gb empty. I thought android adjusted it's partition size automatically if it needs drive space. Suggestions?
Edit: I used TeMeFi instead...worked great. Thx anyway...
Edit: I used TeMeFi instead...worked great. Thx anyway...
Last edited:
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…
I tried selecting 2 or more apps for restore and had no issues.
Please start a debug session (in app settings, help and support), then reproduce the issue, then send a support request mentioning your issue. Make sure the zipped log is attached to the email sent, I'll check your logs for any issues that occured.
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.
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.
Hello,
There has been an intended change to merge the 2 behavior thanks to some other data being available. However the algorithm being used appeared unstable.
This is solved in latest beta (2.7.0d), and will continue to improve. Already tested on OnePlus 10 Pro, Xiaomi 11T Pro, OnePlus 9 Pro coming soon as well as some POCO devices.
Last edited:
@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.
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.
Publishing of 2.7.0d has been pending Google's review for the past 4 days, Google questioning the use of accessibility services and how the app is disclosing those before user can enable them.
I just tested a 3GB data backup and it worked like a charm, in about 45 seconds.
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.
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.
Do you mind sending me a " ls -zRl /data/data/<package> " of the data folder that contains 1GB of files? That way we may be able to identify the faulty file if any.
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 ?
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.
I just tested a 3GB data backup and it worked like a charm, in about 45 seconds.
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.
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.
Do you mind sending me a " ls -zRl /data/data/<package> " of the data folder that contains 1GB of files? That way we may be able to identify the faulty file if any.
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 ?
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.)
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.)
Attachments
Last edited:
Can you try sending a support request from app settings, help and support? It should include crash stack trace to help fix this asap.
Right, skip that - I'm thinking in Linux terms - everything as a shell process... :O)
Yeah, it must've been getting stuck on something there - indeed i had /data/data/... in mind.
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...
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...
I don't know which file it is - because the file name etc. is not displayed in the popup window right - this is by design? You don't display it - just the file size, and proress within it. Or is it that your popup window should display it - and it's just malformed on my phone due to the screen dimensions on the Fold 4? But that shouldn't be no?
Anyhow - I just went and deleted - randomly - a whole bunch of older emails within FairEmail and made sure all it's ongoing processes were closed - my thinking was - it might be storing some temp special files and then removing them within /data/data/... and this could've been what was making it stuck - and indeed it did backup the whole app with data now like in one minute - so not getting stuck anymore.
Don't know what it could've been.
Anyhow - maybe really as a lesson from this - it might be helpful if you increased the amount of data displayed ind the popup window - as to which file is getting backed up - instead of just showing the individual file size.
The popup window is only a couple of lines tall and there is definitely room for display of more - and it would be helpful, I think... :O)
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)
Last edited:
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?
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)
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.
Currently I cannot find the battery statistics "on battery". I only see "since boot", "since last measure" and "since reference". What happened?
Data: Xiaomi mi 10 ultra (cas)
Android 12, Pixel Experience.
I know Google locked down tons of stuff, but to measure "since on battery" should be easy for 3cToolbox to do?
Edit: OK, I found a way if I enable markers.
Data: Xiaomi mi 10 ultra (cas)
Android 12, Pixel Experience.
I know Google locked down tons of stuff, but to measure "since on battery" should be easy for 3cToolbox to do?
Edit: OK, I found a way if I enable markers.
Attachments
Last edited:
How can we get to view Partial and Kernel wakelocks? I have an S22U on A13 (OneUi 5). I remember using the app a couple of years ago wherein I could see the app breakdown. Other battery monitoring apps have this advanced steps enabled though adb permissions. Is there a way to give adb permissions for enabling advanced battery stats?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
I won't be doing ad blocking, that's not allowed on Play Store, and that's bad for developpers including me.Whoops my bad there is a search filter inside app for components I didn't actually notice that button.
With the app manager it is ok but this app manager is somehow instant and ur one loads slower for the icons. Well not very slow but maybe 5 seconds.
https://github.com/MuntashirAkon/AppManager.
Not sure how he does it but it's in github and the code I think is then visible. his app manager loads like in the phones settings that stock app manager where it's instant. Icons instant to.
He has a nice 1 click option for tracker and ad component blocking and it does block nearly all the junk on system and user apps I checked.
I think on his github in issues he mentions the database he uses for them it's a public one I think and then he tweaks it to be more correct it is nice when I want to quick block mostly every thing .
is it normal for the mah drain to say 0 for screen of.
I didn't see a zram option can you add a disable zram option in the app and maybe similar raise zram to 15gb like some magisk modules have that strpxzram can make it 15gb i usually have mine disabled though.
Can you also copy how notifications look on franco kernal manager it shows all the relevant info, mah drain screen on and off and deep sleep when i swipe down i attached a screen shot.
Also could you add visible zram usage to go under the ram usage in task manager and system manager or maybe a memory section that's more dedicated to ram with them options to turn lmk off and all that i attached a screen shot of fkm settings that are for turning of zram/lmk and oos reaper if we wanted to test out preventing apps from closing.
In explorer the root section is limited for me because of read write i am unable to do anything besides copy stuff then paste it to user space which is then boring i like to change files and sometimes mofidy them and swap boot animations on the go and also test them.
On xda I found a guys method that seems to work for read write on the system folder and files in it.
It didn't work for boot animations for me though but other magisk modules did.
Maybe you can implement them.
I'll find a link. They use magisk to work.
edit. this link was handy to learn how to make a folder and file read writeable but i wasnt able to edit other folders on my phone like boot animation so i found a working boot animation module and linked the op to it and he reckons hes rw method should work for it by copying what the module has written in its code i discussed it withhim through out the thread and on the 2nd page of thread. or you can look in the boot animations zip on the 2nd link i added about how to do boot animation and probably any other file in the my_product folder which i was struggling with.
https://forum.xda-developers.com/t/how-to-make-files-in-system-writable.4514603/
can you also make a bootloop fix on your app so it detects rebooting or something and disables magisk modules automatically. and 1 for reverting faulty boot animation if possible if its done through the magisk method i then think its revertable if the modules folder is removed.
Customs Boot animation OOS 12.1 & OOS 13
Just sharing 3 boot animations working on OOS...
forum.xda-developers.com
I think u do have a boot animation section that doesnt work from the read write.
I also noticed the github app manager has prevent background running and it runs of app opps setting and ur 1 is prevent sleeping turning the other app on didn't change ur apps sleeping settings so maybe it's a different method or could be added with your method. It's in running apps on the other app. I didn't see app opps in your app either. Also loading a apps details is slow maybe 5 seconds I'll screen shot it.
Edit. added a screen shot of my battery stat's again sometimes it's in 5 minute intervals and other times its not.
Another edit. I noticed ur cpu section doesn't have input boost options like fkm does I'll add screen shot and this cpusets and Stune boost. Also on the battery main page it's a little limited can you make it similar to fkm battery page like it shows good information there to. Screen on and off. Components power use.
thanks for responding to me to.
Edit again I noticed in ur cpu section that changong governor's fails for me but if I go to fkm governor switching works.
App loading is 2 seconds for me because I have backups on cloud storage, otherwise app's list is instantaneous. So 5 seconds is like you run on a 10-year old device? Even my kids low-end 4-years old are loading the list in a snap. !?
Is it the "process details" page you've attached a screenshot for that's taking 5 seconds delay ? If so there's definitely something blocking the app at some stage, any missing permission or App Ops being blocked ?
Concerning CPU, my app not only checks what's written to governor instantly after writing it, but also update it in real-time. While other app don't and just show what users have set.
I'll check the boot animations if I can integrate those in the app.
I found zram options to be useless, tested on a few devices, and not only phones were getting slightly slower and didn't quite allow running more apps. I'm still not convinced it's a good idea, just hype that will degrade overall storage performance.
mAh drain may show 0 when screen's off time/data is not reliable enough. The idea here is to provide accurate data, not some bullshit to pretend to do things better than others.
You mentioned read-write issue many times, so I'm not sure what you are referring to? In explorer, read-write issue, then for boot animations? I'm using boot anim on a Samsung (different than other device) and then on some Xiaomi/OnePlus devices just fine, it uses Magisks as all Android recent versions are now systemless and system cannot be written to and I find this a pretty good thing to avoid messing one's device. Other than that I don't undestand those issues?
Now, I can surely add writable-folder inside 3C's magisk module, probably from explorer, long-pressing a sub-folder of /system would bring options like "Make writable", "Make read-only" depending on actual setting. However that might have to copy a large amount of data depending on folder!
Obviously that'll require a reboot to be activated and possibly some warning if too much data must be copied, or limited to x MB of data ?!
The boot animation tab uses magisk to write to it. However I remember stumble on a device where boot animations couldn't be changed manually, there were stored in /vendor and sym-linked to /system and even though boot anim was overwritten on reboot, it was not used.
I'll have to run more tests again to find if I still have such device handy.
Concerning battery history, that depends on which setting you use, however for reliability reasons, historical data is logged when screen's turned on/off, or device's plugged/unplugged. Then history can be set to only show % changes, or all recorded data.
EDIT: I believe you mentioned App Ops, and that's something I'm interested in adding and forgot about it since years.
App has a bootloop fix in case of bad CPU settings, but didn't find disabling its own magisk module ever needed. Are you referring to auto-disabling 3C module or all of them? -
57[APP 4.1+] 3C All-in-One Toolbox
3C Toolbox, available on Play Store and XDA Labs is the most comprehensive must-have toolbox for Android version 4.1 and above, running any ROM or kernel. Issues, suggestions, feature requests, please make sure to read post #2.
This app includes all features delivered separately in below apps. This is the result of many years of work to bring all features together in an easy-to-use giant toolbox, and it includes the features of many other apps, including Titanium Backup, Greenify, BetterBatteryStats, App2SD, Seeder, ROM Toolbox Pro, SetCPU, System Panel, Root Explorer, Autorun Manager, Terminal Emulator, Script Editor, SD Booster, BuildProp Editor, ATK and so much more.
What is 3C Toolbox Replaces 20+ apps easily worth 30€ for the price of a couple of beers!
Download link Play Store XDA Labs
Can take advantage of the following apps (not integrated because of policy restrictions from Play Store):
3C Sensitive Backup - Allows backup/restore of SMS/MMS and call-log, can work with 3C Toolbox to schedule backups.
3C Legacty Battery Stats - Allows reading Android legacy battery statistics
Non-exhaustive list of integrated apps and features :
3C CPU Manager (root) - CPU/GPU controls for root users
3C Kernel Tweaker (root) - Kernel tweaking for root users
3C Task Manager - A simple yet powerful task manager for Android
3C Task Recorder - A simple yet powerful task recorder for Android
3C Log Reader - A simple log reader allowing you to read logcat, kernel and xposed logs from a single place
3C Explorer - This is a very simple file explorer for Android
3C Toggles - Highly customizable widgets to control about 30 system components.
3C Battery Monitor - The most complete tool to monitor your battery, have no equal on Play Store.
3C Network Manager - Monitor trafic and control network configurations
3C Apps Manager - The most complete app manager to backup/restore/control all your apps
3C SQLite Manager - A simple SQLite editor
More information
App Features
App screenshots
3C Apps Feature Comparison
Lowest CPU consumption on Play Store
Permissions requested
Getting started guide
Online help
Unique features not available elsewhere
◊ Track your ROM, kernel and battery performance (%/h or mA, screen on or standby)
◊ Battery milli-amp (mA), mW and %/h consumption reporting
◊ Automatic backup of installed and updated applications
◊ Highly configurable textual and graphical monitoring widgets
◊ The most advanced and configurable UI
◊ Clean and safe reboots, without data loss (root required)
◊ And much more30FAQ and guidelines for any queries
Before you put a bad rating on Play Store for a single broken feature among the 100 the app delivers, and before you contact me (or post here), you may consider the following:Why such guidelines?
Feature requests?
Issues with CPU temperature or battery current mA or capacity mAh?
Issues with GPU tab missing features?
How to get support for any other issues
You've read all this? I thank you for your time and hope you enjoy my apps.18Future plans
Here is what I'm working on or planning next:
- Improve ROM Manager with extra features.
- Improve Battery Manager status tab and displayed data
- Add tabs to App Manager (protect, debloat, crystallize, others?)
- Add 'optimize' tab to System Manager for memory/storage
- Improve file manager with swipe left-right and new tab options
- Improve Terminal Emulator with real terminal display.
- Improve UI, suggestions most welcome.
- Removing all ads to see if it brings any positive results (currently testing on 3C Toolbox).
- Add PayPal to XDA Labs apps if possible.
This is my current objectives:
- Increase user support from Play Store, Huawei AppGallery or XDA Labs
- Get XDA Labs apps Google-free (using PayPal)
11Recent Update - Mea Culpa
You have certainly noticed the recent updates that is supposed to improve root handling in my apps, and might have experienced issues.
Why make such change
In versions before 1.6.12, the app was using a very common root method, using scripts and Android commands. Each action was taking 120ms just to get started. Some features like app manager and explorer run a lot of them. With Marshmallow, there's even a bug that cause determining path to fail and require root, slowing down everything a lot.
I started testing a shared library in 1.6.12 that would run root commands directly without this 120ms overhead and it worked really well, running some commands in 1ms instead!
In 1.7, I've started 'migrating' all root features to this new method, always implementing a fall-back in case something went wrong. That didn't work so well in the end.
What went wrong?
To make it short, I was testing this new method on a few devices, running Android 6.0.1, 5.1, 4.4 and supposedly 2.3 but it was running 4.1.2. You can imagine easily how misleading this was!
I learned that Samsung devices had special security constraints that made some commands fail completely and prevented the fallback to take place.
At the same time, Xposed module was reported to fail on Marshmallow because of new security policies. Had to change everything because of that!
Then the APK build process was no longer building the x64 versions anymore.
What's next
I'm still receiving reports of various issues on different versions of Android that I will have to address in the next few days/weeks.
Android N is coming with new security restrictions that will require further changes, but this new root method is already taking care of that.
Did I make a bad decision?
No. Since Android implemented SELinux security policies in 4.2/4.3, each new version of Android has required many internal changes to keep features working, and its getting worse with M and now N.
This new method not only offers much better performance but also requires much less workaround to keep working.
Yes, I made a mistake. After hours of working nights and week-ends, it was still not ready for public release as I thought.
What went even more wrong?
In my desire to offer the best experience possible, I published fixes too quickly and instead of stabilizing stuff, I've only made it worse.
Long story short
I'm sorry for any inconveniences you might have experienced, and I'll do my best to make it better asap.
Want to help?
If you experience any issues and want to help, please send a support request from app settings, help and support, mentioning what happens and possibly screenshot for my understanding.
The support request provides valuable information on the Android version, app logs, Xposed version if installed, app config, etc... Much needed so that I can investigate the issue with similar environment, otherwise I might be testing on a dozen devices without reproducing the issue.
I can then send you an updated APK with a fix or with active debug if I can't pin-point the problem on my test devices.
FWIW: Version 1.7 was addressing a number of issues in previous versions and I did hope it would make users happy with some nice improvements. My bad.113C Task Manager 3.0 (beta)
Dear users,
I've updated (in beta) 3C Task Manager with the new project/build structure. APK size is reduced by 15% while delivering more features. Future maintenance will also be much easier.
3C Task Manager is now capable of managing app's components (activities, services, etc...) and also to renice (Linux priority scheduling) processes (optionally using Xposed for efficiency).
On rooted device, the app will also be able to use 3C Explorer to open an app's data folder or 3C Log Reader to get app's logs.
This new build allows me to reduce development and maintenance times greatly when publishing apps other than the Toolbox.
A lot of refactoring and splitting took place, allowing to build other apps (with similar look'n'feel) faster too, namely the SMS/Call-log backups that's now missing in the toolbox (due to Play Store restrictions).
Next steps include:
- Building an SMS/Call-log backup companion app and link it to the toolbox.
- Adding full SAF / Content Provider support to Explorer
- Allowing browsing network shares through Explorer's SAF / Content Provider
- Adding app labeling in Apps Manager.
- Rebuilding other apps (Battery Monitor, Toggles)
- Creating 3C App Manager
