Database Develop

[REF] Ext4 speed improvement with a safe mount option on /data

Hey everyone.
As I spend some time on studying Ext4 for the Galaxy S devices, working on Voodoo lagfix, and based on what I saw in mount logs it's possible that the performances could be increased without altering data integrity nor filesystem integrity in case of crash.
On /data, noauto_da_alloc is not used.
This option activates a sort of Ext3 emulation mode, which force sync on write close without sync.
It also comes with a speed penalty for SQLite writes, and is unneccessary when hardware barriers are enabled.
Barriers allow usage of delayed allocations without risk. Delayed allocations are the key to performance for modern filesystems.
as root:
Code:
mount -o remount,noauto_da_alloc /data /data
You can count on me to cook a kernel with this mount option as default
PS: this option is already used in Voodoo kernels for Galaxy S devices / has been chosen after extensive performance and reliability tests.

Okay, kevin_teslacoil run quadrant:
before:
<kevin_teslacoil> 1676 for the full quadrant bench mark
after:
<kevin_teslacoil> interesting
<kevin_teslacoil> 2422 this time
<GuiPer> :O
<Ibanez33> wtf?
I'm not a fan of quadrant, but used as a tool, it can give some useful infos
Also, note that this dramatic change in benchmark result won't be as incredible in real life usage.
But still, it's a better choice of configuration, using the filesystem driver like it should be given the hardware parameters.

Can this be implemented in Voodoo for SGS?

Reference, from man mount.
auto_da_alloc|noauto_da_alloc
Many broken applications don't use fsync() when noauto_da_alloc replacing existing files
via patterns such as
fd = open("foo.new")/write(fd,..)/close(fd)/ rename("foo.new", "foo")
or worse yet
fd = open("foo", O_TRUNC)/write(fd,..)/close(fd).
If auto_da_alloc is enabled, ext4 will detect the replace-via-rename and replace-via-trun‐
cate patterns and force that any delayed allocation blocks are allocated such that at the
next journal commit, in the default data=ordered mode, the data blocks of the new file are
forced to disk before the rename() operation is commited. This provides roughly the same
level of guarantees as ext3, and avoids the "zero-length" problem that can happen when a
system crashes before the delayed allocation blocks are forced to disk.
Click to expand...
Click to collapse

I'm trying this now.

jaju123 said:
Can this be implemented in Voodoo for SGS?
Click to expand...
Click to collapse
It's already implemented in Voodoo

Okay thanks

Still at it I see?

We lose this whenever we reboot I'm assuming?
Quadrant scores:
Before: 1672
After: 2334
Cook this into some good 1.2GHz OC/UV
We already know the Hummingbird can potentially hit 1.6

Its late, nevermid

Preparing a kernel with this option activated as default.

Anderdroid said:
We lose this whenever we reboot I'm assuming?
Quadrant scores:
Before: 1672
After: 2334
Cook this into some good 1.2GHz OC/UV
We already know the Hummingbird can potentially hit 1.6
Click to expand...
Click to collapse
fstab
10 char

Could you please implement this new mount option in your Vibrant "voodoo" kernels? Much appreciated! Thanks for your hard work, Curio!

zimphishmonger said:
Could you please implement this new mount option in your Vibrant "voodoo" kernels? Much appreciated! Thanks for your hard work, Curio!
Click to expand...
Click to collapse
Already told. This is the default mount option for Voodoo, after extensive analysis for both performance and filesystem+data integrity

I am using the latest of the trasig OC kernel for JPO and tried this options with no changes in quadrant. (1720)

deleted...................

Does this work on the galaxy tab?

futuregerald said:
Does this work on the galaxy tab?
Click to expand...
Click to collapse
no.
go to the galaxy tab section

Lagfix
So does this revert upon a reboot? I tried it on my SGTab and nothing happened, just want to make sure there is nothing i need to "undo" other than just rebooting. Thanks!

cba1986 said:
I am using the latest of the trasig OC kernel for JPO and tried this options with no changes in quadrant. (1720)
Click to expand...
Click to collapse
Doesn't work for me either on Galaxy S with JH3 (stock Telstra ROM other than root). Quadrant score actually dropped (916 to 896).

[Q] Installed Suckerpunch #51, Serendipity ....

I would like to know how I can check if the phone is overclocked? I used the same settings I found in the Suckerpunch #51 Kernel, -100 pretty much everywhere. Stable, Quadrant score is about 1600 consistently...
How can I check how much I'm running at? Also using Serendipity and Suckerpunch does that mean I'm running EXT4?
I'm pretty new to this, I installed this all last night for the first time.
Any help would be appreciate.
T.

Sorry for the double post, but how can i check my file system and how can I get EXT4 - All files if I don't already have it.
Thanks,

I assume your using voltage control if so go into it select the mhz you want to run at from the drop down then there is a tab at the bottom that says select states un check every mhz above the mhz you want to use example: you want 600mhz then only 400, 200, 100 checked the rest all unchecked.
As for ext 4 boot into cwm goto speedmod then lagfix look at the bottom if u see ext4 at the bottom for file systems then lagfix enabled if u don't then u need to enable it in that menu. only about half the file systems will say ext4 if lagfix is enabled
Paragon rc6 with Paragon Kernel
Underclocked to 800mhz
Undervolted to -100mV
Paragon rc6 with Paragon Kernel
Underclocked to 800mhz
Undervolted to -100mV

I'm currently running Serendipity latest release with SuckerPunch #51 Kernel.
When you say boot into CWM and go to Speedmod then lagfix, that means i need to change kernels right?
my settings for voltage control are not higher than 1200 and my states checked are 7 states under that like suggested in the Suckerpunch #51 post.
Nevermind my friend, I believe I am in the process of updating to EXT4
"keywords are I believe "

Although right now after doing the lagfix like you mentioned from CWM and enabling EXT4 on all data and systems, I try and run Voltage and i get a message I am not rooted.
Is that a problem? am I doing something wrong?
Edit again I apologize I'm rooted again through CWM.
Thing i still don't understand is how do I bring my OC up to 1200 -- or even better how can I confirm I am Overclocked?

Lol very new to this heh? Go into cwm goto backup and restore and make a backup for me please lol. That way if you screw up you can go into cwm and restore. Now for voltage control id recommend underclocking to 800 because it will help with battery and you won't notice a difference in performance unless you run benchmarks which mean nothing other than giving you.some numbers to show off. Now after you select what you want in voltage control click options button and apply boot settings then exit and thats it. You can get a system info app from market or run linpack and it will show you your clock speed in the results.
Paragon rc6 with Paragon Kernel
Underclocked to 800mhz
Undervolted to -100mV

Thank you so much - everything seems to running like you said.
File Extensions are EXT4 now, lagfix is enabled, rom is running beautifully, kernel seems stable after 60 runs through stability test.
I think I'm good
I appreciate your input.

np like I said too if your battery life is an issue try underclocking because I run st 800mgz no problem
Paragon rc6 with Paragon Kernel
Underclocked to 800mhz
Undervolted to -100mV

[Q] OC Nook Color 1.3.0

Hello all,
I just rooted my nook color using the ManualNooter 4.6.16 after updating my stock ROM to 1.3. Now I am trying to run the CPU OC using the Nook Color Tweaks. I am very Noob to this but am very tech savvy.
I know that I need to flash one of Dalingrin's OC kernel's but I really have no idea where to start. And since I am new to the forum I cannot post directly in one of those existing threads yet.
Can I get a step by step instructions on this and which kernel I need to download please? I searched high and low through all of the threads and cannot figure out which kernel i need and how I flash it?
Thanks

DO A FULL BACKUP FIRST
I used Dalingrin's OC kernels found here - http://forum.xda-developers.com/showthread.php?t=925451
There's a link that says 'All kernels hosted here'. Scroll down to the 090111 folder and pick the emmc file.
Throw it onto your bootable CWM card's root directory.
Boot into CWM
Wipe cache partition
Advanced
Wipe Dalvik Cache (mine locked up completely after doing this - just reboot the unit by pressing and holding the power button until it powers off, and then turn it back on.)
Install zip from SD card, select the kernel linked above, and voila.
After that's complete, remove your bootable card and select reboot.

thanks!
thanks for the directions, they worked perfectly. Now what do I do. I am able to get into the CPU settings through the Nook Color Tweaks, but I'm not sure how high I should be setting all the different CPU Stepping stages? Or is this pretty much trial and error? I've read that i can use SetCPU. Is that true or should I stick with the Nook Tweaks?

I could be way off here, but I believe it's already setup to be OC'ed compared to stock.
I have also installed SetCPU.
There are few settings out there on the thread for the kernel. Check out the later pages.

carbfrze said:
thanks for the directions, they worked perfectly. Now what do I do. I am able to get into the CPU settings through the Nook Color Tweaks, but I'm not sure how high I should be setting all the different CPU Stepping stages? Or is this pretty much trial and error? I've read that i can use SetCPU. Is that true or should I stick with the Nook Tweaks?
Click to expand...
Click to collapse
If you allow SetCPU to show recommended settings the app will show you suggested paramenters that should allow you to OC without digging into all the esoteric settings. I've always just used the slider bar to clock up a step at a time to find the point I like and is stable. For me, about 1.4 seems most stable for what I run.

another problem
ok, i was changing the settings in the Step 2 options under the Nook Tweaks app and must have messed something up. It was stuck in a boot loop. It would get to the Nook Color animation boot screen and then reboot constantly. It would boot into the O/S every once in a while but would immediately lock up and not allow me to change any settings or anything. I tried wiping the Davlik Cache along with some other suggestions but could not get it running again.
I ended up wiping it and going with the latest CM7 build that has the built in Dalingrin's app. Having issues with that but I will post another thread to get help with that.
Thanks for the suggestions!

[Q&A] [Kernel][CPU OC][GPU OC][F2FS] CroPol kernel

Q&A for [Kernel][CPU OC][GPU OC][F2FS] CroPol kernel
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

doesn't work
I've got an error on boot, something like 0x0000d0d2. I got it with all versions. I use the latest cm10.2 by novaFusion with PurePerformanceX installed.

vietnam131 said:
I've got an error on boot, something like 0x0000d0d2. I got it with all versions. I use the latest cm10.2 by novaFusion with PurePerformanceX installed.
Click to expand...
Click to collapse
Afaik it doesn't support 4.3.x ROMs. Try any 4.4.x ROM.

Ok, I will try. But if you can make this kernel for previous versions of Android, it would be nice.

i cant get 1150/2000 mhz
what cpu governor and i/0 scheduler are you guys running to get 1150/2000 mhz? i have the normal s3 mini, not the nfc version and im running cyanogenmod.

snakeboy1011 said:
what cpu governor and i/0 scheduler are you guys running to get 1150/2000 mhz? i have the normal s3 mini, not the nfc version and im running cyanogenmod.
Click to expand...
Click to collapse
Try pegasusqplus+sioplus.

mauam said:
Try pegasusqplus+sioplus.
Click to expand...
Click to collapse
what should i put as the min frequency?

snakeboy1011 said:
what should i put as the min frequency?
Click to expand...
Click to collapse
100 or 200. You need to try by yourself

what ROM do you use as I don't think CyanogenMod supports 1150/2000mhz?
mauam said:
100 or 200. You need to try by yourself
Click to expand...
Click to collapse
Sorry for your time

deep sleep bug? reboot bug? voltage limits? persistent config by userinit.sh?
Hello!
I got several questions regarding the usage of this kernel's voltage and clocking/voltage options:
1. Everytime my mobile goes to deep sleep, it sets maximum clock to 400MHz and minimum clock to 100MHz. It stays so after enabling and while using the phone. It's horrible slow. So I got to increase maximum clock by hand everytime the phone was in deep sleep before.
What's the problem there?
2. After rebooting the maximum clock is always reset to 1000MHz, although i had set it to 1150/1200MHz before.
Why?
3. I noticed 1200MHz not being completely stable on my device. So I wanted to increase the voltage for step9.
In /sys/kernel/liveopp/arm_slot09 i saw the default hex value for VARM was 0x3f. So I tried increasing this to 0x40 and 0x41, but the voltage shown in this file didn't increase anymore.
3a) So is the voltage capped at 1362,5000mV or is it just not displayed correctly?
3b) Will increasing Varm to more than 0x3f do anything at all?
Also I've seen the voltage called Vbbx (default value for step9: 0xff)
3c) What exactly is this voltage, and how does it go together with Varm?
3d) Is there a way for increasing voltage any further than 0x3f for Varm and 0xff for Vbbx?
4. For persistence I tried automatically setting changed voltage parameters on boot, using userinit.sh.
The file didn't exist before, so i created it as /sys/local/user/userinit.sh, set the perissions to 755, and added the following content:
Code:
#!/system/bin/sh
echo set_volt= 1 > /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x41 > /sys/kernel/liveopp/arm_slot09
But the script doesn't work. After rebooting varm for step09 is always at default value (0x3f).
4a) Why doesn't this work?
4b) I think it maybe is not working because the above command needs to be run as root, but how could i do this in userinit.sh without sudo?
Many thanks for patience and help!

Elmarigo said:
1. Everytime my mobile goes to deep sleep, it sets maximum clock to 400MHz and minimum clock to 100MHz. It stays so after enabling and while using the phone. It's horrible slow. So I got to increase maximum clock by hand everytime the phone was in deep sleep before.
What's the problem there?
Click to expand...
Click to collapse
First of all, notice that deep sleep is a power state in which the CPU has a very low voltage consumption.. Therefor its not even clocked at 100 Mhz. With this Kernel, when screen is off, the clock is set 100-400 MHz if its needed (by wake locks).
Now, I see that the problem here is that it stays when you wake the phone. What ROM are you using? You could try flashing the Kernel again.
Elmarigo said:
2. After rebooting the maximum clock is always reset to 1000MHz, although i had set it to 1150/1200MHz before.
Why?
Click to expand...
Click to collapse
Unless this values are set compiled in kernel, you will have to manually set everytime you boot. But a quick solution is to enable the "apply settings on boot" on the app that you are using to OC. (You can use ROM Toolbox if your ROM doesn't have built in this options)
Elmarigo said:
4. For persistence I tried automatically setting changed voltage parameters on boot, using userinit.sh.
The file didn't exist before, so i created it as /sys/local/user/userinit.sh, set the perissions to 755, and added the following content:
Code:
#!/system/bin/sh
echo set_volt= 1 > /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x41 > /sys/kernel/liveopp/arm_slot09
But the script doesn't work. After rebooting varm for step09 is always at default value (0x3f).
4a) Why doesn't this work?
4b) I think it maybe is not working because the above command needs to be run as root, but how could i do this in userinit.sh without sudo?
Click to expand...
Click to collapse
Try deleting the space between "1" and ">" like this:
Code:
#!/system/bin/sh
echo set_volt= [B]1>[/B] /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x4[B]1>[/B] /sys/kernel/liveopp/arm_slot09

xhhb said:
First of all, notice that deep sleep is a power state in which the CPU has a very low voltage consumption.. Therefor its not even clocked at 100 Mhz. With this Kernel, when screen is off, the clock is set 100-400 MHz if its needed (by wake locks).
Now, I see that the problem here is that it stays when you wake the phone. What ROM are you using? You could try flashing the Kernel again.
Click to expand...
Click to collapse
Hello!
I'm using Carbon Rom by novafusion. There's an update from 27.10. now, and I'll see later if this helped against this particular problem!
xhhb said:
Unless this values are set compiled in kernel, you will have to manually set everytime you boot. But a quick solution is to enable the "apply settings on boot" on the app that you are using to OC. (You can use ROM Toolbox if your ROM doesn't have built in this options)
Click to expand...
Click to collapse
In Carbon there's an option for applying saved values on boot. I used these and I also tried CoCoreManager, but both didn't apply my saved config although I had enabled this setting.
xhhb said:
Try deleting the space between "1" and ">" like this:
Code:
#!/system/bin/sh
echo set_volt= [B]1>[/B] /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x4[B]1>[/B] /sys/kernel/liveopp/arm_slot09
Click to expand...
Click to collapse
Ok, I will try this. Is userinit.sh being executed as root by automatic?
Thank you!

Ok, i found multiple bugs in my script and corrected these.
The script currently is like:
Code:
#!/system/bin/sh
echo set_volt=1 > /sys/kernel/liveopp/arm_step09
echo varm=0x41> /sys/kernel/liveopp/arm_step09
The commands are working from terminal/SSH, but playing them in /data/local/userinit.sh doesn't change anything after reboot. (file is marked as executable!)
So can anyone help please how to make this working?
I still believe it's maybe because of the script not being executed with root permissions, but I'm not sure about that and I don't know how to work around this without a sudo command.
Also I still could use help with my remaining questions from my older post: http://forum.xda-developers.com/showpost.php?p=56343298&postcount=10
Thank you!
PS: this 10message restriction for 'new users' doesn't seem like a working way for keeping the forum's content at good quality.
I'm forced to writing in Q&A-Thread, while the creator and the other most experienced users of original thread don't even seem to look here.
Aswhile, the 'more experienced' users, having more then 10messages, in original thread are keeping the most experienced users busy, asking questions that are even way more basic than mine, but regarding the same topic (persistent undervolting). So I can't help these users and no one from that other thread can help me

Not working on miui
I flashed it on miui v5 http://forum.xda-developers.com/showthread.php?t=2647472 and it won't boot!!! Need help!!!!

chaudhary1122 said:
I flashed it on miui v5 http://forum.xda-developers.com/showthread.php?t=2647472 and it won't boot!!! Need help!!!!
Click to expand...
Click to collapse
Did you delete your Cache and reboot twice?
If you already did, then flash your full ROM again.

Elmarigo said:
Did you delete your Cache and reboot twice?
If you already did, then flash your full ROM again.
Click to expand...
Click to collapse
Nope, I guess not. So I'll give it a try now!!! Thanx!!!!

Elmarigo said:
Did you delete your Cache and reboot twice?
If you already did, then flash your full ROM again.
Click to expand...
Click to collapse
Did it but still not working!!! Not booting first the Samsung startup screen with the name and model is replaced with a white screen and then comes a black screen with red text at the top left corner I don't actually remember what it says!!!! Need help!!!

wifi and bt not work
I have a problem with this kernel , no wifi or bluetooth install on virginity v14 rom with option 2 for stock based rom otherwise I will work perfect kernel 1.1 ghz wifi but I need someone a suggestion? Do not attempt to try to option 1 cm based on that I guess should be different thanks

chaudhary1122 said:
Did it but still not working!!! Not booting first the Samsung startup screen with the name and model is replaced with a white screen and then comes a black screen with red text at the top left corner I don't actually remember what it says!!!! Need help!!!
Click to expand...
Click to collapse
I think for saving your phone you should flash your previous ROM (the one you had on that phone before) using Odin from a PC. If this doesn't help either you should try Full Wipe and flash stock ROM.
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2159660
LaInfluenza said:
I have a problem with this kernel , no wifi or bluetooth install on virginity v14 rom with option 2 for stock based rom otherwise I will work perfect kernel 1.1 ghz wifi but I need someone a suggestion? Do not attempt to try to option 1 cm based on that I guess should be different thanks
Click to expand...
Click to collapse
I didn't see anyone else trying the kernel on stock-ROM, yet. You should write a PM to ChronoMonochrome about this, so he can tell the developer.

Elmarigo said:
I think for saving your phone you should flash your previous ROM (the one you had on that phone before) using Odin from a PC. If this doesn't help either you should try Full Wipe and flash stock ROM.
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2159660
I didn't see anyone else trying the kernel on stock-ROM, yet. You should write a PM to ChronoMonochrome about this, so he can tell the developer.
Click to expand...
Click to collapse
The fact that the kernel is pretty good, I loved it but I need the wifi I use it all day and does not serve me well beyond virginity v14 rom that I really like, I tried it on the newest cm11 but I do not really like this rom I hope for the next update will fix this kernel as serious buenisimo roms have oc in stock or stock -based.

[April 2, 2016][MOD][FIX]MaxOpt R2 1.0.6 UPDATED CODE BASE

NEW EASY INSTALLER, RECOVERY ZIP
Total overhaul of code.
*HELP WANTED, PM FOR RELEVANT DETAILS*
This software package was originally just made for my personal use to rectify the issue of my phone not entering deep sleep when idle and me not having access to a charger for the majority of the day while also improving multitasking because being my phone is also my build environment/office environment, I am frequently jumping around various apps that I'd prefer to keep open.
Things this package accomplishes on your phone (very simple and brief summary):
*Forces entry into deep sleep as soon as the screen is off (if enabled, on by default). It also has audio detection so you can listen to music with the screen off without unwanted deep sleep entry.
*Improves multitasking, no more apps having to reload/redraw when you switch back to them.
*Automatic odexing of all apps, including new installs (if enabled, pre-lollipop ROM's).
*Easy management of swap.
*CPU management. You can set your own values to be locked (no other app can change them) or let its device manager automatically set CPU frequencies and the governor you specify.
*Dynamic Max CPU Freq: When enabled (on by default) it will automatically scale the max CPU frequency value depending on the CPU load. This can help with governors that favor the high end of the frequency table too much by allowing you to save battery but have the CPU power available when needed, without having to adjust anything manually whenever you go from doing something processor demanding to having your phone sit idle.
*Fixes issues with several kernels where the touch screen is unresponsive after waking the device. No more inconvenient force reboots.
*Enables all idle and suspend states available (they are disabled by default quite often) and can help get your device into the lower C-States.
*Fixes broken links to firmware files caused by buggy init scripts on some ROM's.
New/Other features:
*New recovery flashable installer
*Force system wide GPU rendering and faster framerate.
*Fixes Dt2w and Sw2w lock screen freeze bug.
*Now compatible with KSM.
*Faster app loading and responsiveness. Key android services are given priority status for I/O and CPU resources.
*Multitask over 20+ apps simultaneously without any redraws and low-latency app switching (provided you have the swap space)
Tip: I use the large amount of unused space on /system to increase the size of that MaxOpt managed swapfile.
*Fixed the crash on boot issue between MaxOpt and some kernels.
Default MaxOpt config:
•Swap on, default MaxOpt generated swapfile size is 64 MB, with one made on /data, one on /cache, and one on /system if mounted rw.
•Auto-odexing off.
•Hotplugging compatibility on.
•User CPU settings off, auto-device manager on.
•Deep Sleep immediately on screen off enabled.
•KSM off (you must have a kernel that supports it to enable this option and have it work).
•Kernel settings on.
•Everything is forced to be drawn by the GPU.
All of the above listed features are user optional/tuneable.
For those who wish to only use MaxOpt for fixing the lock screen freeze bug associated with some kernels/DT2W/S2W use the following link: http://forum.xda-developers.com/showthread.php?t=3061589
If you would like to just use individual components or adjust program settings from a terminal app, here is an example usage and description of their individual functions as well as other useful documentation (VERY OLD DOC, NEEDS LOTS OF UPDATES):https://docs.google.com/file/d/0B_hgNZE_j5sVbEN4ZUtkS2p0bW8/edit?usp=docslist_api
Terminal Emulator is what I would recommend for use with managing MaxOpts' settings.
System Requirements (not entirely sure due to lack of public testing):
Busybox
A terminal app
A kernel that can best be utilized by these programs.
Please make a nandroid backup before using.
And here is the MaxOpt installer ( R2 1.0.6 ):
* https://drive.google.com/file/d/0B_hgNZE_j5sVaGdxV0FfODdxbVU/view?usp=docslist_api
Changelog:
R2 v1.0.6- Adjustments to write buffering and multitasking memory performance.
R2 v1.0.5a- Fixed a bug present in both this project and MaxLife where data wasn't validated thoroughly enough before using it.
R2 v1.0.5- Added a new completely experimental new user tuneable (on/off, default off) that changes runtime memory allocation values. Only activate it if you have a large amount of swap.
R2 v1.0.0- Totally rebuilt the project, installable with a recovery flashable zip now, kernel image installer is no longer compatible and is scrapped.
For those still getting crashes:
The issue still appears to be related to the device radio when it happens, so, after a crash could you please force reboot your device and try to disable mobile data when it boots before it crashes again and please post a copy of /proc/last_kmesg. Thank you.
Screenshots of battery screen showing time spent in sleep:
https://docs.google.com/file/d/0B_hgNZE_j5sVSjRUU0ZlX0UwUWc/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVSmNjYThkUzAtNGM/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVcWxJd0JyV09nMDA/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.

Wow, this looks amazing. Very nice work.
I Will be playing with this for the next few days.
Sent from my Moto G using Tapatalk

Damn this looks complicated as hell haha. Good job OP

Very nice job

Thank you very much everyone. Glad for the positive feedback, this is my first public software release. I daylight in a machine shop, so this was far from my field of expertise and a long learning experience for me

I tried it on faux kernel 014m.
But my phone bootlooped
I have faux clock app.
Is it causing the problem?
Thanks

One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.

elrod16 said:
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
Click to expand...
Click to collapse
I followed steps as below:
I put that 2 files in the data partition.
Then boot.img of faux.
I set permission 755 for both files and boot.img
Then from terminal I executed the command.
I got new_image.img
I repack the zip using this new boot image and flashed it in recovery.
Then I reboot.
Phone booted and stuck on "optimizing apps 1 of 98"
Then again same.
Also I had 700mb of free memory when I tried this.
When I again booted using faux kernel I had 450mb of free memory.
Can you guess what's going wrong?

Did you disable APK signature checking?

elrod16 said:
Did you disable APK signature checking?
Click to expand...
Click to collapse
Sorry I forgot that.
Where exactly should I put those 2 files.
Was I doing right to put them in data partition?
And after first boot can I enable signature verification?
Do I need to disable it before every boot?

Unfortunately for now it needs to be off whenever an app is upgraded or added, but can be enabled after the reboot that that happens on, and yeah, /data works

Even after disabling signature verification it doesn't work on faux boot.img
Am I doing right?

For whatever reason it sounds like the dexy binary isn't playing well with your phone, I'll make a new installer with the option of disabling it for incompatible setups for the time being, but the other ones should still work. I'll keep ya posted.

My rom is stock 4.4.4
I will try again with disabled optimization.

kedar512 said:
My rom is stock 4.4.4
I will try again with disabled optimization.
Click to expand...
Click to collapse
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.

elrod16 said:
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
Click to expand...
Click to collapse
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.

kedar512 said:
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
Click to expand...
Click to collapse
I would say yeah, try it with it and see if it makes a difference

Also did you try the new build with a clean restore? (Before any of the failed install attempts) Try not wiping the cache/dalvik-cache after install and flash.

I tried again but this time booted upto lock screen and rebooted.
I tried with new build.

after placing ./maxopt boot.img appears running with dexy enabled.
That means it's already working? If yes, have to do anything else?
Every time you turn the meter will have to repeat the procedure?
Sorry my bad english