• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[APP 4.0+] 3C All-in-One Toolbox

Search This thread

3c

Senior Member
Jul 19, 2005
2,767
1,902
www.3c71.com
Could someone confirm if configuring permissions with the use of xposed module work for you? I have xposed module enabled and disabling permission in 3c toolbox does not work at all. Could someone help?

Last time I checked it was still working on Android 11.

What version of Android are you running, is the module truly loaded, what permission are you trying to change, what happens when you block a permission in the app (any popup?), etc...

Best is to send a support request from app settings help and support mentioning your issue so I can check all those quickly and help or start investigating.
 
  • Like
Reactions: duttyend

3c

Senior Member
Jul 19, 2005
2,767
1,902
www.3c71.com
Dear dev,
Is there an option to clean/remove useless files and folders (empty directories, tombstones, etc.)?
Have a good day

Not at the moment, after checking apps that do that I found the saving pretty useless except for big files which you can identify from system manager's, SD card tab, and then open explorer from big folders.

That said, it's something that might be added in a future release as a one-click tab in system manager to clean one's device entirely (running app, files and folders, cache, and uninstalling unused apps, etc).
 
  • Like
Reactions: duttyend

robkor

Senior Member
Oct 1, 2017
85
7
Last time I checked it was still working on Android 11.

What version of Android are you running, is the module truly loaded, what permission are you trying to change, what happens when you block a permission in the app (any popup?), etc...

Best is to send a support request from app settings help and support mentioning your issue so I can check all those quickly and help or start investigating.
I am able to set permissions correctly and it looks like everything is OK. However they not work. The permission don't block for example using camera, recording voice, turning vibration off etc. I am using lsposed latest and running android 11. My phone is mi 11 miui 12.5

All others modules such as xprivacylua or android faker work perfectly. Just 3c tool module does not work for me
 

3c

Senior Member
Jul 19, 2005
2,767
1,902
www.3c71.com
@3c Do you can add support model like Xiaomi Redmi Note 10S in battery manager? Right now value from app not make sens.

If you can send a support request mentioning the issue (while using automatic setting) I will be able to add support, otherwise every manufacturer/phone/model is reporting mA data differently, sadly, not following Google's specs!

Without that information I cannot possibly know how your device is reporting mA data.
 

Strannik10

New member
Sep 15, 2021
2
0
Hello.

I installed 3c All in One Toolbox on my Huawei Mate 20 (cpu Kirin 980) .

This is the best tools for Android, but i have issue. The CPU temperature show incorrect. Always show 40° and temperature does not change over time. Is it issue only Kirin cpu? Can you help me? Thank you in advance.
 

3c

Senior Member
Jul 19, 2005
2,767
1,902
www.3c71.com
Hello.

I installed 3c All in One Toolbox on my Huawei Mate 20 (cpu Kirin 980) .

This is the best tools for Android, but i have issue. The CPU temperature show incorrect. Always show 40° and temperature does not change over time. Is it issue only Kirin cpu? Can you help me? Thank you in advance.
Can you send a support request from app settings help and support so I can check which sensor is used and how to select the right one on your device?
 

Strannik10

New member
Sep 15, 2021
2
0
Hello.
I sent request from app settings help and support one day ago and receive answer (patch).
I downloaded and installed patch, after that everything work fine.
I hope this patch will be include in next version 3C All in One Toolbox.
Thank you.
 

emadmahdi

Member
Jan 28, 2017
22
1
Hello,
Thanks for this great tool ... Though unfortunately I spent few hours trying to install 3C All In One ... It causes bootloop when using almost any 2.4.x or 2.5.x versions ... I tried many apk ARM64 files from play store and from other stores ... The latest release that worked for me without bootloops was 2.3.9d

Note:
Battery Manager ... Current Detection ... Choices List ... In this list i noticed you use microampere in replace of milliampere and vice versa !!

Device:
Asus zenfone 2: ASUS_Z00TD
Android: 6.0.1
Kernel: WW_21.40.1220.2181_20170805
CPU: Dual 4 Cores (8 cores total) ARM64
RAM: 3 GB
Storage: 16GB
Battery: 3000mAh
Phone is: Rooted + Magisk + Xposed
 
Last edited:

3c

Senior Member
Jul 19, 2005
2,767
1,902
www.3c71.com
Hello,
Thanks for this great tool ... Though unfortunately I spent few hours trying to install 3C All In One ... It causes bootloop when using almost any 2.4.x or 2.5.x versions ... I tried many apk ARM64 files from play store and from other stores ... The latest release that worked for me without bootloops was 2.3.9d

Note:
Battery Manager ... Current Detection ... Choices List ... In this list i noticed you use microampere in replace of milliampere and vice versa !!

Device:
Asus zenfone 2: ASUS_Z00TD
Android: 6.0.1
Kernel: WW_21.40.1220.2181_20170805
CPU: Dual 4 Cores (8 cores total) ARM64
RAM: 3 GB
Storage: 16GB
Battery: 3000mAh
Phone is: Rooted + Magisk + Xposed
Thanks for letting me know. I'll try to get my hand on a Zenfone to see what happens.
If you can clarify under which scenario it actually bootloops it might help. Like activating Xposed module or simply granting root or? A clear path to reproducing this would be a first step.

Concerning battery mA reading method, those are not reversed, it lists reading/retrieval method all aiming at providing a consistent mA data for all devices. MicroAmp method means it'll read data from device as MicroAmp and convert it to mA. Sadly even to this date no manufacturer are following the specs, not even Google and there are 4 main ways devices report ampere data, mA or uA standard or reversed.

Thanks.
 
  • Like
Reactions: emadmahdi

emadmahdi

Member
Jan 28, 2017
22
1
Thanks for letting me know. I'll try to get my hand on a Zenfone to see what happens.
If you can clarify under which scenario it actually bootloops it might help. Like activating Xposed module or simply granting root or? A clear path to reproducing this would be a first step.

Concerning battery mA reading method, those are not reversed, it lists reading/retrieval method all aiming at providing a consistent mA data for all devices. MicroAmp method means it'll read data from device as MicroAmp and convert it to mA. Sadly even to this date no manufacturer are following the specs, not even Google and there are 4 main ways devices report ampere data, mA or uA standard or reversed.

Thanks.

After reading your reply i did the folowing new tests:

install 3c all in one 2.4.1e
run 3c all in one
exit 3c all in one
remove 3c Xposed module
exclude 3c from Xposed
exclude 3c from Magisk root
reboot
ok
Add 3c to Magisc root
reboot
ok
Add 3c to Xposed
reboot
logo screen never finish (6 minutes)
reboot to safe mode
uninstall 3c
reboot
ok
install 3c all in one 2.5.3a
exclude 3c from Xposed
reboot
ok

I am using Xposed Installer version 3.1.5 with framework version 89 and api version 23

I forgot if i am using system or systemless Magisk ... most likely it is systemless.

Attached is the log file from Xposed .. I found many lines saying "Not Found" but all of them do exist in my device and have one of these permissions:

-rw-r--r-- system system
-rw-r--r-- root root
 

Attachments

  • xposed_error_20210926_152616[1].log
    30.9 KB · Views: 1

3c

Senior Member
Jul 19, 2005
2,767
1,902
www.3c71.com
After reading your reply i did the folowing new tests:

install 3c all in one 2.4.1e
run 3c all in one
exit 3c all in one
remove 3c Xposed module
exclude 3c from Xposed
exclude 3c from Magisk root
reboot
ok
Add 3c to Magisc root
reboot
ok
Add 3c to Xposed
reboot
logo screen never finish (6 minutes)
reboot to safe mode
uninstall 3c
reboot
ok
install 3c all in one 2.5.3a
exclude 3c from Xposed
reboot
ok

I am using Xposed Installer version 3.1.5 with framework version 89 and api version 23

I forgot if i am using system or systemless Magisk ... most likely it is systemless.

Attached is the log file from Xposed .. I found many lines saying "Not Found" but all of them do exist in my device and have one of these permissions:

-rw-r--r-- system system
-rw-r--r-- root root
The only thing this log shows is that the module did not load at all:

09-26 15:19:02.931 I/Xposed ( 441): Loading modules from /data/app/ccc71.at.free-1/base.apk 09-26 15:19:02.931 E/Xposed ( 441): File does not exist

This is a common issue with xposed manager not having updated the app path after an update/install.

Anyway the fact that it's not booting confirms there is an issue, however that log doesn't show the actual issue. If you have a way to run logcat from a PC while booting you could get system logs to show the problem.
 

emadmahdi

Member
Jan 28, 2017
22
1
The only thing this log shows is that the module did not load at all:

09-26 15:19:02.931 I/Xposed ( 441): Loading modules from /data/app/ccc71.at.free-1/base.apk 09-26 15:19:02.931 E/Xposed ( 441): File does not exist

This is a common issue with xposed manager not having updated the app path after an update/install.

Anyway the fact that it's not booting confirms there is an issue, however that log doesn't show the actual issue. If you have a way to run logcat from a PC while booting you could get system logs to show the problem.

To my knowledge .. I am using the latest Xposed Framework and latest Xposed Installer that is available for my android 6.0.1 ... As for the app path ... Kindly let me know what file should i change to correct the app path ?!!

Attached the logcat while booting ... It is with 3c xposed module enabled ... This is the command that i used:

adb -d logcat > file.log
 

Attachments

  • 3c_problem_with_xposed.zip
    101.2 KB · Views: 2
Last edited:

3c

Senior Member
Jul 19, 2005
2,767
1,902
www.3c71.com
To my knowledge .. I am using the latest Xposed Framework and latest Xposed Installer that is available for my android 6.0.1 ... As for the app path ... Kindly let me know what file should i change to correct the app path ?!!

Attached the logcat while booting ... It is with 3c xposed module enabled ... This is the command that i used:

adb -d logcat > file.log
To resolve path issue, you cab open xposed manager and disable and re-enable the module so that it updates the path in the modules list with latest information. That usually works for me.
But then if you reboot I assume booting will fail and if you can get logcat when that happens this should show what's wrong, unless ADB is not yet up?
 

emadmahdi

Member
Jan 28, 2017
22
1
To resolve path issue, you cab open xposed manager and disable and re-enable the module so that it updates the path in the modules list with latest information. That usually works for me.
But then if you reboot I assume booting will fail and if you can get logcat when that happens this should show what's wrong, unless ADB is not yet up?

I did enable/disable many times ... the problemn still exist.

As for logcat log file "during booting" and the "3c xposed module" was enabled ... you can find it in the attached zip file.
 

Attachments

  • 3c_problem_with_xposed.zip
    101.2 KB · Views: 3

3c

Senior Member
Jul 19, 2005
2,767
1,902
www.3c71.com
I did enable/disable many times ... the problemn still exist.

As for logcat log file "during booting" and the "3c xposed module" was enabled ... you can find it in the attached zip file.

I barely see the module loading for one app and then the whole system goes into sensor waiting for 6 minutes .... not much information otherwise.

Odd enough I bought the same device a year ago to solve some other issues, and now I suppose I have to get another one ;)
 
  • Like
Reactions: emadmahdi

emadmahdi

Member
Jan 28, 2017
22
1
Hi @3c

I need to see the battery usage for a period like a week or more ... I usually recharge every day or every two days and i need to see the average usage or total usage of each app or each compnnents used the battery.

Kindly let me know how i can do that using 3c all-in-one ... In battery manager I only see the usage of one recharge cycle ?!!

I tried reference point but it seems that it covers only the ongoing recharge cycle !!
 
Last edited:

白い熊

Senior Member
Aug 29, 2011
743
274
相撲道
@3c which parts exactly is the xposed module used for? The reason I’m asking I’d probably like to use it without the xposed module enabled — I have the Samsung Fold 3 now and when 3c module is enabled, it seems to mess with System UI, or Samsung One UI, disabling the navigation bar and status bar...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hello,
    Thanks for this great tool ... Though unfortunately I spent few hours trying to install 3C All In One ... It causes bootloop when using almost any 2.4.x or 2.5.x versions ... I tried many apk ARM64 files from play store and from other stores ... The latest release that worked for me without bootloops was 2.3.9d

    Note:
    Battery Manager ... Current Detection ... Choices List ... In this list i noticed you use microampere in replace of milliampere and vice versa !!

    Device:
    Asus zenfone 2: ASUS_Z00TD
    Android: 6.0.1
    Kernel: WW_21.40.1220.2181_20170805
    CPU: Dual 4 Cores (8 cores total) ARM64
    RAM: 3 GB
    Storage: 16GB
    Battery: 3000mAh
    Phone is: Rooted + Magisk + Xposed
    Thanks for letting me know. I'll try to get my hand on a Zenfone to see what happens.
    If you can clarify under which scenario it actually bootloops it might help. Like activating Xposed module or simply granting root or? A clear path to reproducing this would be a first step.

    Concerning battery mA reading method, those are not reversed, it lists reading/retrieval method all aiming at providing a consistent mA data for all devices. MicroAmp method means it'll read data from device as MicroAmp and convert it to mA. Sadly even to this date no manufacturer are following the specs, not even Google and there are 4 main ways devices report ampere data, mA or uA standard or reversed.

    Thanks.
    1
    I did enable/disable many times ... the problemn still exist.

    As for logcat log file "during booting" and the "3c xposed module" was enabled ... you can find it in the attached zip file.

    I barely see the module loading for one app and then the whole system goes into sensor waiting for 6 minutes .... not much information otherwise.

    Odd enough I bought the same device a year ago to solve some other issues, and now I suppose I have to get another one ;)
    1
    How do I get 3C Toolbox to work with LSPosed? The prompt to install the xposed module is in the active tweaks section, but there is a 3C module already installed and active in my module list. I don't know how it got there though. I presume it self-installed when I installed the system helper module, but I might have installed it manually another way and forgotten how.

    There are no default recommended options so I tried enabling systemui and system framework but these don't make it active within the app.

    Is it a simple matter of enabling the right LSPosed apps in the mod list, or is there another way to install the LSPosed mod and have the app recognise it as an intalled xposed mod? Is there a list of recommended apps to enable for 3c's LSPosed app list?
    Late reply, but I managed to test this LSPosed version of Xposed. I didn't have the prompt to install xposed module in active tweaks section, which only appears if module is not loaded/active.

    Yes you'll have to activate all apps under the 3C Toolbox module. If you enable no app underneath the module, it won't be active at all. If you enable only few apps, its features will be limited to those selected apps.

    IMO, this new way of activating module is not safer than before and will make it highly frustrating for any users that wish to use system-wide modules.

    That said, I've made some improvements in latest toolbox beta, and it should work better on Android 11+. Note however that there seem to be remaining issues blocking localization services, which I'm still working on.
  • 54
    [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 more
    29
    FAQ 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:
    3C Toolbox runs on hundreds of devices and custom ROMs, I cannot test all of them, however I try to change device regularly to ensure the app is compatible with all devices, please check my signature.

    ◊ 3C Toolbox and its derived apps are, at the time of writing, used by more than half a million users and 3C Toolbox Pro is rated 4.8/5 by about 3000 users.

    ◊ 3C Toolbox runs on Android 4.x and above, I always have at least one device running 4.x, 5.x, 6.x, 7.x and 8.x to avoid issues, however I may miss some key differences from time to time, possibly causing the app to crash or a feature to malfunction.

    ◊ 3C Toolbox is not a game relying on well established documentation, but an advanced toolbox which uses some undocumented features, which have evolved along with each version of Android. Even some documented features had to be adapted to newer Android versions.

    ◊ 3C Toolbox provides milli-Ampere data for your battery either provided by Android OS or estimated by the app when there is no current sensor. Hardware current sensor can sometimes report inaccurate or no data at all. It's impossible to predict how the next device will report milli-Ampere if it does at all.

    ◊ I'm a human being, not a service center, not a big corporate. Like any other human being I don't like being bashed or insulted by email or anywhere else and will no longer waste my time for anyone doing so.
    Why such guidelines?
    - You want new features and improvements as soon as possible?
    - You want a quick solution to a problem?
    - You don't want to waste your time explaining?

    Me too, that's that simple.
    Feature requests?
    Please explain using as few words as it's possible and join a screenshot if it applies to an existing feature. Pictures speaks 1000 words they say, maybe.
    Issues with CPU temperature or battery current mA or capacity mAh?
    Please explain this in a support request sent from app settings, help and support so I can provide the appropriate option to use in 'mA retrieval method' of battery / monitoring settings and add out-of-the-box support for your device. All necessary information is provided in the request's attachments.

    Battery current mA and CPU temperature are non standard on Android and every devices/manufacturers provides it differently or not at all. Don't blame the app if your device doesn't provide it or report inconsistent values, ask your manufacturer which get paid lots of bucks.
    Issues with GPU tab missing features?
    GPU configuration is not something standard on Android, and there are currently 10+ implementations available. If you miss something, please send a support request from app settings, help and support mentioning what's missing and a screenshot of each GPU tabs.
    How to get support for any other issues
    Please send a support request from app settings, help and support. You need to clearly explain your issue, attach any relevant screenshots showing where and how the issue occurs. I will not provide any support here.

    The idea is that you explain the observed issue, possibly add a screenshot so that I know exactly where to look (app has 100+ screens and sometimes words don't mean the same for you and me), from there I can really do a good job at helping you. You want my help, do it the right way or simply don't.

    The support requests contains the following (you can check the content before sending). Privacy policy is available here.

    ◊ Battery technical details as available on device
    ◊ Battery history recorded (last 100 records)
    ◊ CPU technical details as available on device
    ◊ SD mount points (to help identify unsupported SD locations)
    ◊ Previous visible and internal crash reports (FC)
    ◊ Process running (to identify possible conflicts)
    ◊ App configuration (version number, type and mA retrieval method in use)
    ◊ Android configuration (version, security settings, ROM, kernel)


    You've read all this? I thank you for your time and hope you enjoy my apps.
    17
    Future 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)
    11
    3C 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
    11
    Recent 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.