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

Search This thread

白い熊

Senior Member
Aug 29, 2011
894
311
相撲道
Why don't you store the data in the TWRP installer in a way that can restore both old and wiped data?
Because thanks to Samsung, if you decrypt /data so TWRP can access in now, Dex will not work, sharing on the system stops working and other errors now on Fold 3.

So the only way is to have /data encrypted and then TWRP cannot access it - this is the current reality unfortunately.
 

3c

Senior Member
Jul 19, 2005
2,852
1,973
www.3c71.com
OK, so this means really: do not restore toolbox settings on new system – set up by hand, then first toggle Firewall to whitelist in this case, then restore all apps.

You see where this leaves us, right? For system apps there is no way to restore firewall settings this way.

I think then really full xml or whatever export/import for firewall settings, encoded by package name is desired. Or have a backup/restore switch only for this, but that's overkill and maybe not desirable.

Anyhow web access control for everything is one thing highly desirable to be saveable and restorable in one go for many apps, I think.
I agree, this should be an import/export in firewall tab and include it into existing import/export feature.
As for restoring toolbox settings, I'll clear firewall settings.
That should make things work as expected.
 

白い熊

Senior Member
Aug 29, 2011
894
311
相撲道
Oh yeah, it would be also beneficial if you'd allow setting the location of the exported files, also for toolbox settings, somewhere in settings – so that it wouldn't have to go to sdcard root by default, if you don't want it there. :)
 

3c

Senior Member
Jul 19, 2005
2,852
1,973
www.3c71.com
OK, so this means really: do not restore toolbox settings on new system – set up by hand, then first toggle Firewall to whitelist in this case, then restore all apps.

You see where this leaves us, right? For system apps there is no way to restore firewall settings this way.

I think then really full xml or whatever export/import for firewall settings, encoded by package name is desired. Or have a backup/restore switch only for this, but that's overkill and maybe not desirable.

Anyhow web access control for everything is one thing highly desirable to be saveable and restorable in one go for many apps, I think.
Finally found a way to save package names along with UIDs and upon restore/loading settings it will double-check all UID vs package names and remove unknown package names and fix all UIDs as it should. Starting with next update, you'll be able to restore toolbox settings and have firewall settings applied automatically.

Note however if a package is not installed, the UID is "lost" and firewall config for that package is not restored.
 

白い熊

Senior Member
Aug 29, 2011
894
311
相撲道
Note however if a package is not installed, the UID is "lost" and firewall config for that package is not restored.
OK - this will mostly affect user apps.

However, if I export settings and then backup apps - the backups should save the firewall settings, right?

So then, on system update - import settings with an incomplete app set - so then firewall settings will be “lost” for non-installed apps. If I then restore an app, the firewall settings should be restored for it, no?
 

3c

Senior Member
Jul 19, 2005
2,852
1,973
www.3c71.com
OK - this will mostly affect user apps.

However, if I export settings and then backup apps - the backups should save the firewall settings, right?

So then, on system update - import settings with an incomplete app set - so then firewall settings will be “lost” for non-installed apps. If I then restore an app, the firewall settings should be restored for it, no?
Indeed restoring apps will still restore firewall settings for the apps restored.
 
  • Like
Reactions: 白い熊

白い熊

Senior Member
Aug 29, 2011
894
311
相撲道
Finally found a way to save package names along with UIDs and upon restore/loading settings it will double-check all UID vs package names and remove unknown package names and fix all UIDs as it should. Starting with next update, you'll be able to restore toolbox settings and have firewall settings applied automatically.
I think the implementation is messed up still - all kernel apps lose settings on reboot:

I have whitelist mode and whitelisted all kernel apps: Kernel, Media server, root

They are all not whitelisted after every reboot. Don't know if it affects any user or system apps.

EDIT
It is somehow borked - the only kernel app that stays whitelisted after reboot is Shell, all other ones lose the settings after a reboot.
 
Last edited:

BeachNYC

Senior Member
Sep 1, 2014
74
28
Google Pixel 6 Pro
I suppose this has been asked and answered before, and if so, I apologize, but I cannot find such an answer.

Suddenly, without warning, this little 3C widget or button appears constantly on my homepage. I don't know what function it serves; when it is touched, it gets bright, touch again and it turns off. But it never disappears.

3C Toolbox.jpeg


Can someone tell me its function, and how to get rid of it? Photo attached. You can see it in the upper right corner.

Many thanks.
 

asripath

Senior Member
Jul 12, 2020
142
90
Redmi K20 Pro
I suppose this has been asked and answered before, and if so, I apologize, but I cannot find such an answer.

Suddenly, without warning, this little 3C widget or button appears constantly on my homepage. I don't know what function it serves; when it is touched, it gets bright, touch again and it turns off. But it never disappears.

View attachment 5542269

Can someone tell me its function, and how to get rid of it? Photo attached. You can see it in the upper right corner.

Many thanks.
Accessibility shortcut
 

白い熊

Senior Member
Aug 29, 2011
894
311
相撲道
I think the implementation is messed up still - all kernel apps lose settings on reboot:

I have whitelist mode and whitelisted all kernel apps: Kernel, Media server, root

They are all not whitelisted after every reboot. Don't know if it affects any user or system apps.

EDIT
It is somehow borked - the only kernel app that stays whitelisted after reboot is Shell, all other ones lose the settings after a reboot.
@3c indeed this happens on each reload of rules - so rules for kernel apps are not properly preserved and reloaded - so not even necessary to reboot.

When you clean rules, then reload them - the kernel apps' rules do not get reinstated.
 

3c

Senior Member
Jul 19, 2005
2,852
1,973
www.3c71.com
@3c indeed this happens on each reload of rules - so rules for kernel apps are not properly preserved and reloaded - so not even necessary to reboot.

When you clean rules, then reload them - the kernel apps' rules do not get reinstated.
Yes, sorry about that, when I added a check for installed apps UID vs package names, it killed kernel apps restoration. Will fix that asap.
 
  • Like
Reactions: Lughnasadh

白い熊

Senior Member
Aug 29, 2011
894
311
相撲道
Yes, sorry about that, when I added a check for installed apps UID vs package names, it killed kernel apps restoration. Will fix that asap.
@3c the current implementation is still more problematic than it seemed. User scenario:

- Set the firewall rules - whitelist mode.
- Export the Toolbox settings.
- Toggle some firewall access rights for any app.
- Import the Toolbox settings.
- Result: the toggled settings don't get changed back to what was exported.

You might've mentioned somewhere there needs to be a reboot after settings import, unless I'm mistaken - if that is so, all the more reason to split the Firewall rules export/import functionality from the Settings. This should be doable from the Firewall page - user selectable in settings where the firewall export gets saved - and Firewall settings should update on import, no need to reboot for that or what have you.

Also, if you'll be at it - please include the options to display UUIDs and App package.names - not only app names - in the Firewall page - like I want to search for gms, like this not doable.

Also, I exported full settings prior, had a system crash this morning - had to reset the phone, again they get imported wrong - but seeing as how the Firewall import/export is problematic, no use for me to trace it now.

I really want to use it here, but it's really getting to be a headache this Firewall here in the toolbox - I think it should be manageable neatly without the other settings like I say above - for obvious reasons... Phew - off to manually toggle everything again... :)
 

3c

Senior Member
Jul 19, 2005
2,852
1,973
www.3c71.com
@3c the current implementation is still more problematic than it seemed. User scenario:

- Set the firewall rules - whitelist mode.
- Export the Toolbox settings.
- Toggle some firewall access rights for any app.
- Import the Toolbox settings.
- Result: the toggled settings don't get changed back to what was exported.

You might've mentioned somewhere there needs to be a reboot after settings import, unless I'm mistaken - if that is so, all the more reason to split the Firewall rules export/import functionality from the Settings. This should be doable from the Firewall page - user selectable in settings where the firewall export gets saved - and Firewall settings should update on import, no need to reboot for that or what have you.

Also, if you'll be at it - please include the options to display UUIDs and App package.names - not only app names - in the Firewall page - like I want to search for gms, like this not doable.

Also, I exported full settings prior, had a system crash this morning - had to reset the phone, again they get imported wrong - but seeing as how the Firewall import/export is problematic, no use for me to trace it now.

I really want to use it here, but it's really getting to be a headache this Firewall here in the toolbox - I think it should be manageable neatly without the other settings like I say above - for obvious reasons... Phew - off to manually toggle everything again... :)
Thanks for your feedback.

Once imported, you can open firewall tab and tap reload. It'll do the job. I'm not quite sure but it seems as the app gets stopped, firewall rules are temporarily lost (!?). Yet to confirm.

I will add import/export feature to firewall tab in next update so it'll get easier to manage.
 
  • Like
Reactions: 白い熊

白い熊

Senior Member
Aug 29, 2011
894
311
相撲道
Also, it seems the app restore is not properly linked to UUID identification now - since I just verified:

- I first handclicked all Firewall rules.
- Then restored tens of apps - the resulting Firewall rules are completely messed up - it might be a reload is needed - anyhow that's also unlucky. But I didn't check - it was all messed up due to restore, i.e. apps already present before other apps' restore got firewall rules toggled... And they really got blocked - it wasn't just improper display.

I confirmed it since Firefox lost internet access - as the tens of apps were being restored in the background, i.e. it's firewall permissions got shifted - I went into the firewall settings during the restore, toggled Firefox on, it wouldn't get access as it kept probably being thrown off.

Only after the restore - had yet again import rules - these now toggledd everything - it might've been that had I hit reload as you say, it'd have fixed, only read it afterwards.

Still it seems very unfortunate - it just keeps leaving me in a state of worry constantly that I'll lose the settings.

And it's not like it's a big deal - but with hundreds of apps this is really tens of minutes of clicking it again ang again, lost time...
 

白い熊

Senior Member
Aug 29, 2011
894
311
相撲道
Also, you know - the reload - there should be two kinds - as it's problematic now:

- it's currently "reload from what you have set for apply on boot"
- but if it should be just refresh the displayed rules - i.e. on restore, the firewall tab doesn't get updated with proper restored rules - that's the refresh

But now - what if you have set rules for apply on boot:

- then you toggled some rules

Now you want to reload - you don't want to reload what was saved for boot, if on firewall stop it gets lost, you just want to refresh what you set right.

This due to the fact:
- if you toggle stuff
- then restore

You don't want to reload settings disrespecting what you toggled before restore.
 

3c

Senior Member
Jul 19, 2005
2,852
1,973
www.3c71.com
Also, it seems the app restore is not properly linked to UUID identification now - since I just verified:

- I first handclicked all Firewall rules.
- Then restored tens of apps - the resulting Firewall rules are completely messed up - it might be a reload is needed - anyhow that's also unlucky. But I didn't check - it was all messed up due to restore, i.e. apps already present before other apps' restore got firewall rules toggled... And they really got blocked - it wasn't just improper display.

I confirmed it since Firefox lost internet access - as the tens of apps were being restored in the background, i.e. it's firewall permissions got shifted - I went into the firewall settings during the restore, toggled Firefox on, it wouldn't get access as it kept probably being thrown off.

Only after the restore - had yet again import rules - these now toggledd everything - it might've been that had I hit reload as you say, it'd have fixed, only read it afterwards.

Still it seems very unfortunate - it just keeps leaving me in a state of worry constantly that I'll lose the settings.

And it's not like it's a big deal - but with hundreds of apps this is really tens of minutes of clicking it again ang again, lost time...

I'm not sure how a restore would mess-up firewall rules as it applies restored app firewall setting individually based on saved settings for each app.
That said, it uses live settings, add the new restored app settings and reapply everything, so if it starts wrong, it'll end-up being wrong.

I've now fixed the restoring of toolbox settings, so there won't be any need to reload firewall setting afterward. This should help avoid the above issue you mentioned.

I've also added import/export in network tab and will publish as beta 2.6.0a momentarily.
 

3c

Senior Member
Jul 19, 2005
2,852
1,973
www.3c71.com
Also, you know - the reload - there should be two kinds - as it's problematic now:

- it's currently "reload from what you have set for apply on boot"
- but if it should be just refresh the displayed rules - i.e. on restore, the firewall tab doesn't get updated with proper restored rules - that's the refresh

But now - what if you have set rules for apply on boot:

- then you toggled some rules

Now you want to reload - you don't want to reload what was saved for boot, if on firewall stop it gets lost, you just want to refresh what you set right.

This due to the fact:
- if you toggle stuff
- then restore

You don't want to reload settings disrespecting what you toggled before restore.
There won't be 2 kinds of reload, as the refresh you mention is just the same. After a restore, the reload loads what was saved in previous versions of the app for apply on boot.
No new feature to cope with a refresh that is now fixed as well.

The last part is just unmanageable because if you restore settings, what you toggled before as no meaning anymore. It will be the same when you import settings, you loose what you previously toggled. Otherwise it's no longer a restore of settings whether all settings or just firewall.
 
  • Like
Reactions: 白い熊

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    This I have set up properly — iit shouldn't be getting killed. Sometimes the bar disappears even while in 3c - on other tabs than settings.

    Also - if it was because the app is killed - which it shouldn't be, because I have it outside battery optimization - it would come back on after switching to 3c again. Which it doesn't - I have to do the weird step of going to the Line graph settings and out then - only then it comes on...
    You explained that it disappears when you exit the toolbox, so that was the only logical explanations as I'm using line indicators and have never seen it disappear, ever. What is your settings, showing in fullscreen or not? The line indicator setup is pretty straight forward and appart from fullscreen, there's no option that'll make it disappear, except other apps or OS messing with the draw over other app permission.

    I'm using it without glitch for the past several years... So I can't tell what's wrong with your setup. Could even be another app with draw over other apps permissions that would draw something on top of the toolbox lol. That'd be surprising but I've seen worse on Android.

    PS:
    It's not because you excluded the app from battery optimizations that it cannot be killed. All manufacturers have messed this up. Please read this: https://3c71.com/optim.
    Same goes for permissions granting, many manufacturers have implemented a way to remove permissions if you don't *use* an app for a while. Even if the app shows a widget, a notification or any other visible thing permanently! That's how stupid people who think they're smarter than others keep messing Android experience.
    Same goes, yes again, for draw over other apps... Some manufacturer have decided that some screens/apps shouldn't be drawn over, no matter what the user decided!

    Accessibility have nothing to do with draw over other apps.

    So what happens with the apps that are affected by this - i.e. they are running checks on where the app was installed from: I restore it from a backup in the toolbox, open the app, it'll say something along the lines of "This application was not installed from Google Play Store, uninstall it and reinstall from the Play Store."

    I don't uninstall it - but run the above command, as root obviously, on the apk in the toolbox backup folder. Then the app will function normally.

    Next update will backup owner package (store information) with all backups when set and restore it automatically if set. It'll save it in info.txt file, so you can edit manually to change it at your convenience. No point having special options that would only confuse users.
    1
    I don't think this a proper approach now - for someone who has restored many apps from a 3c backup - like me.

    I just checked - and all apps restored from 3c backups have the vendor set as 'null' - which is improper by default. Only the ones - a handful - that I've installed directly in the above manner or from Google Play after the latest system update have it set properly as the 'com.android.vending' - so if you do it like you say - for me most everything will be saved with 'null' - thus I'll have to edit everything by hand... Whereas if one could select the vendor for multiple apps.... :O)
    You're original suggestion was to have an option in both backup/restore pop-ups to decide whether or not to backup/restore the actual store information. I've just made it automatic and pretty simple.

    For anyone backing-up/restoring many apps, like I do when changing device, it'll be much better than having to tick an option during backup and restore to make sure store information is up-to-date.

    Now, the actual issue is that as of previous versions, the store information is not there. However when Play Store will update your apps, it'll update the store information as well and every subsequent backup will have that information.

    Also you mentioned that you had a handful of apps requiring the store information to be up-to-date, so you only have to edit the info.txt file for those, which I'm sure won't take that long. I did it on the few apps that do that in a matter of minutes, amongst the 500 backups I have.
  • 56
    [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