Android Tablets Forum banner
1 - 4 of 4 Posts

·
Registered
Joined
·
82 Posts
This should be a start of a summary of tweaking Tools and a discussion what tweaks work the best and which Don`t Work.

TOOLS:

1) Pimp my ROM (Beta)
https://play.google.com/store/apps/details?id=com.androguide.pimp.my.rom&hl=de

What Works:
- Entropy Generator Works Great for me (Even If on XDA some People call it placebo)
- Disable Android Logs makes it a Bit faster (but you can' t send logcats to developers anymore)

What doesn't work:
- The tweaks under "Miscellaneous tweak" don't Show me any difference in system behavior
- Kernel tweaks... Because our Kernel doesn't Support over-/underclocking
- category "Apps & Mods" ...None of these work for me

2) ROM Toolbox
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5qcnVtbXkubGliZXJ0eS50b29sYm94Il0.

What Works:
-Autostart Manager Works great and helps To avoid starting apps
-Startanimation Manager is for me one of the best features
-Under keine kernel tweaks is an option SWAPPINESS which boosted MySQL system performance
-the build.prop editor is a nice feature to change the values there e.g. on our device you can enable/disable soundbuttons, screenshot button or the hdmi,Bluetooth setting option or change the screen density (of course you can also do this with any root file editor)

What doesnt't work:
- Theme chooser...because our ROMs do not have this CM feature

3) SetCPU
https://play.google.com/store/apps/details?id=com.mhuang.overclocking&hl=de
- Doesn`t work because of missing Kernel support

... To be continued (More hopefully soon)

Please share your experience maybe it`s different to my subjective Evaluation
 
  • Like
Reactions: KRoman47

·
Registered
Joined
·
82 Posts
Discussion Starter · #2 ·
Reserved
 

·
Registered
Joined
·
13 Posts
We are definitely need someone skilled who can look at source code of our kernel and enable higher frequencies so we can see how much this chips can handle.
 

·
Registered
Joined
·
1 Posts
Any tool to unlock nand and/or enable init.d? The second thing is more important for me. Tried PimpMyROM (FC) Uniwersal Init.d (Activate gives :Done:, Verify says "no init.d, did you tap "Activate"?") Init.d Enabler (says everything went OK, but no init/d folder in /system/etc).

It seems that every app I use cannot enable init.d, because not enough space on /system.

However I cleaned it and now its 330,6 MB free and its 55+% of all space on this partition.

Log from Uniwersal says about it:

sh: <stdin>[148]: can't create /system/etc/install-recovery.sh: No space left on device
sh: <stdin>[148]: can't create /system/etc/install-recovery.sh: No space left on device
sh: <stdin>[148]: can't create /system/etc/install-recovery.sh: No space left on device
sh: <stdin>[148]: can't create /system/etc/install-recovery.sh: No space left on device
sh: <stdin>[148]: can't create /system/etc/install-recovery.sh: No space left on device
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chown /system/etc/install-recovery.sh: No such file or directory
mkdir failed for /system/etc/init.d, No space left on device
sh: <stdin>[190]: can't create /system/etc/init.d/08setperm: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/08setperm: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/08setperm: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/08setperm: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/08setperm: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/08setperm: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[190]: can't create /system/etc/init.d/00test: No such file or directory
Unable to chmod /system/etc/init.d/08setperm: No such file or directory
Unable to chmod /system/etc/init.d/00test: No such file or directory
Unable to chown /system/etc/init.d: No such file or directory
Unable to chown /system/etc/init.d/08setperm: No such file or directory
Unable to chown /system/etc/init.d/00test: No such file or directory
sh: <stdin>[217]: can't create /system/bin/sysinit: No space left on device
sh: <stdin>[217]: can't create /system/bin/sysinit: No space left on device
sh: <stdin>[217]: can't create /system/bin/sysinit: No space left on device
sh: <stdin>[217]: can't create /system/bin/sysinit: No space left on device
sh: <stdin>[217]: can't create /system/bin/sysinit: No space left on device
sh: <stdin>[217]: can't create /system/bin/sysinit: No space left on device
sh: <stdin>[217]: can't create /system/bin/sysinit: No space left on device
Unable to chmod /system/bin/sysinit: No such file or directory
Unable to chown /system/bin/sysinit: No such file or directory
sh: <stdin>[311]: can't create /system/etc/install-recovery.sh: No space left on device
sh: <stdin>[311]: can't create /system/etc/install-recovery.sh: No space left on device
sh: <stdin>[311]: can't create /system/etc/install-recovery.sh: No space left on device
sh: <stdin>[311]: can't create /system/etc/install-recovery.sh: No space left on device
sh: <stdin>[311]: can't create /system/etc/install-recovery.sh: No space left on device
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chown /system/etc/install-recovery.sh: No such file or directory
mkdir failed for /system/etc/init.d, No space left on device
sh: <stdin>[353]: can't create /system/etc/init.d/08setperm: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/08setperm: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/08setperm: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/08setperm: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/08setperm: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/08setperm: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/00test: No such file or directory
sh: <stdin>[353]: can't create /system/etc/init.d/00test: No such file or directory
Unable to chmod /system/etc/init.d/08setperm: No such file or directory
Unable to chmod /system/etc/init.d/00test: No such file or directory
Unable to chown /system/etc/init.d: No such file or directory
Unable to chown /system/etc/init.d/08setperm: No such file or directory
Unable to chown /system/etc/init.d/00test: No such file or directory
sh: <stdin>[380]: can't create /system/bin/sysinit: No space left on device
sh: <stdin>[380]: can't create /system/bin/sysinit: No space left on device
sh: <stdin>[380]: can't create /system/bin/sysinit: No space left on device
sh: <stdin>[380]: can't create /system/bin/sysinit: No space left on device
sh: <stdin>[380]: can't create /system/bin/sysinit: No space left on device
sh: <stdin>[380]: can't create /system/bin/sysinit: No space left on device
sh: <stdin>[380]: can't create /system/bin/sysinit: No space left on device
Unable to chmod /system/bin/sysinit: No such file or directory
Unable to chown /system/bin/sysinit: No such file or directory

My device is Pentagram Eon Prose 2 with RK2926 on board, I've already rooted it and flashed CWM (wanted TWRP, but couldn't boot it. Will try again later.
 
1 - 4 of 4 Posts
Top