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

Preferred icon theme

  • No icon

    Votes: 0 0.0%
  • Flat material icons

    Votes: 5 45.5%
  • Theme colored 3D icons

    Votes: 2 18.2%
  • Colorful 3D icons

    Votes: 4 36.4%

  • Total voters
    11
Search This thread

ecips

Senior Member
Dec 31, 2006
144
81
Perth
Widget tap action

Hi!

I've got 3c Toolbox Pro on my device. Version 1.9.7.8.7

I'm using the CPU and Battery 2x1 Text widgets.

When I tap the CPU widget I am taken directly into the CPU manager, however when I tap the battery widget I am taken to the main page with all the buttons.

Is there any way to change the tap action of the widget??

Cheers!
 

Rinoceros

Senior Member
Jul 8, 2008
369
165
Hi!

I've got 3c Toolbox Pro on my device. Version 1.9.7.8.7

I'm using the CPU and Battery 2x1 Text widgets.

When I tap the CPU widget I am taken directly into the CPU manager, however when I tap the battery widget I am taken to the main page with all the buttons.

Is there any way to change the tap action of the widget??

Cheers!
Settings -> Widgets -> Widget Content -> Widget Tap Action
Easy as it can be... :p
 
  • Like
Reactions: ecips

3c

Senior Member
Jul 19, 2005
2,936
2,059
www.3c71.com
It looks the Issue with Xposed and freezing Toolbox has been solved with v1.9.7.8.7
I have installed ElementalX kernel (including the manager), made a couple of Nandroid Backups, so I had to reboot a couple of times and it comes always back on line. I can see it on the widget, on my homescreen, as well.

Explorer is working fine on Nougat.

I can confirm this too.

In case it's not clear, I haven't made any changes whatsoever in the app. It's been fixed in Xposed v89 by Rovo89 as explained a few posts above.
 

3c

Senior Member
Jul 19, 2005
2,936
2,059
www.3c71.com
v1.9.7.8.7: I can't open any files with the explorer with Oreo (8.0/8.1). I just get the message "Operation failed".
Of course the storage permission is granted and I can't say since which version this happens.

I run multiple devices with Oreo and have not experienced such issue. Hence issue has nothing to do with app versions or Oreo.
 

peterbonge

Senior Member
Sep 16, 2006
506
116
I run multiple devices with Oreo and have not experienced such issue. Hence issue has nothing to do with app versions or Oreo.

I've just done a clean install on my HTC U11 life with Android 8.0 (Stock, no root):
Opened the app -> Manage -> Explorer -> granted storage permission -> searched a text file -> tap -> "Operation failed".

Same on my Nexus 5X with Android 8.1 Beta.
 

3c

Senior Member
Jul 19, 2005
2,936
2,059
www.3c71.com
I've just done a clean install on my HTC U11 life with Android 8.0 (Stock, no root):
Opened the app -> Manage -> Explorer -> granted storage permission -> searched a text file -> tap -> "Operation failed".

Same on my Nexus 5X with Android 8.1 Beta.

Thanks, turns-out it works just fine when using debug APK, but fails completely in release mode. Next update, about to be published, should fix this.
 
  • Like
Reactions: peterbonge

3c

Senior Member
Jul 19, 2005
2,936
2,059
www.3c71.com
I did had the problem also when XPosed 89 was installed. But after your update it was gone. Weird...:rolleyes:

If you read Rovo89's thread, you'll see the problem is Android optimizations that re-compile the APK code, and Xposed is included. Updating the app forces code compilation. In that same thread you could find a workaround to force recompilation that would work temporarily with v88 of Xposed and would have fixed the issue with v89 without having to update the app. Nothing weird.
 

jfromeo

Senior Member
Aug 7, 2011
94
10
I am running Android 7.1.2 (LineageOS 20180122 Nightly) with OpenGapps nano 20180122, Magisk 15.3 and systemless Xposed framework v89.1 (SDK25).

I have 3C Toolbox 1.9.7.9.1 installed and I cannot get any widget to actually change any of its values as I could some weeks before. It only shows the default green android icon along with the default values (process count and system memory used I guess).

If I enter the customization widget menu and try to change anything (icon, values, bars, style...) the changes are not saved. It does a quick refresh animation like if it tried to change the values but it goes back to the default status and the widget does not update.

Before I had several system widgets like this:
ojEyvwd.png


But now I cannot get past to this:
Oki5eHh.png


3C Toolbox has root permissions in MagiskSU and it is activated as a module in xposed framework. I have tried with and without root permissions and with and without system framework activation, but none work. I have also tried to move the app as a system app and reboot. I installed and old version of the app (1.9.6.X) which I was sure it worked before, and it shows the same behaviour, so I guess it is something OS/system related.

The rest of my xposed/root modules (greenify, amplify...) works like a charm.

Is there anything I could check?

I suspect of something related to Magisk, as when I had SuperSU (by chainfire) and regular Xposed Framework (by rovo) I did not have any problems to manage the widgets.
 
  • Like
Reactions: Prince8167

SevenFactors

Member
Nov 20, 2013
42
7
CPU Manager Sometimes Works , Other times it doesn't work.

LineageOS 14.120180228 athene.
Using the latest version of 3C Toolbox Pro via play store.
Magisk 16.0

There are times in which the core controls show but there are others in which they are not available. This behavior is the same for "CPU" and "Governors" settings. The control can either be or not be available.

Can this be fixed?

Can you please answer this questions.
- Is xposed required for CPU manager?
- For what features of 3C Toolbox Pro is xposed needed?
- Does the 3C Toolbox Magisk module & root enough for the proper function of all features provided/supported by 3C Toolbox pro?

Thank you.
 

Attachments

  • Screenshot_20180307-011155.png
    Screenshot_20180307-011155.png
    140.6 KB · Views: 245
Last edited:
  • Like
Reactions: Prince8167

gadgetguy08

Senior Member
Apr 2, 2008
330
110
I can't seem to get the DNS changer to work for me unless I toggle it off and then back on each time I need it to change.

I have installed the system helper app. Running 7.1.2.

Am I missing something?
 
  • Like
Reactions: Prince8167

heyjoe66

Senior Member
Mar 15, 2007
566
173
I have several concerns here:

1. Logcat is not shown on my Honor 8. If I go to the terminal and type 'logcat' I can see that it's being written as expected, but the Tools/System Log window is empty.

2. After reflashing the same stock ROM the toolbox doesn't see some backups. I can see them in the /sdcard/backup folder, but not in the backups' list.

3. How in the universe to restore the call log and messages?


UPDATE:
2. .apk file are missing, still it could restore data after app was installed from the Play Store, but instead it just ignores backups without an .apk. Tittanium did not.

3. Found that button in One-Click tab
 
Last edited:

Top Liked Posts

  • 2
    3C toolbox 2.9.3 system uptime in widget shows cpu frequence also cant show in double chart
    This will be fixed in 2.9.3d, but you'll have to edit widget configuration to show the option you want. There's been an overlap in data configuration causing this.
  • 2
    3C toolbox 2.9.3 system uptime in widget shows cpu frequence also cant show in double chart
    This will be fixed in 2.9.3d, but you'll have to edit widget configuration to show the option you want. There's been an overlap in data configuration causing this.
  • 58
    [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
    30
    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.
    18
    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
    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.
    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