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.
Related
i have a motorola droid and it is rooted.i flashed a new rom and then i flashed sprecovery,i let it run its course and i disconnected the phone.when the phone turns on it starts up and then a red light comes on and my phone says please connect charger.it keeps saying android process is not responding and then the phone shuts itself off.ive tried to boot it into recovery mode and do a restore,it keeps giving me an error that says nandroid exited with status 20 and its also not reading my sd card.can somebody tell me whats happened and if it can be fixed???please and thank you
Well, seems as if you need to reflash or restore because of bad flash. If you try flashing again make sure you wipe data and cache. As far as not reading sdcard I have same problem not sure why but when I'm in recovery and I choose install zip which I used clockworkmod recovery, if it fails then it reboots automatically after couple seconds not sure if this happens with sprecovery. After sdcard mount fail it shuts down and reboots so before it reboots I pull the battery and wait a minute or two before trying again. It may take me 3 to 4 times of doing this but eventually it will mount sdcard in recovery. I recommend keep trying till it allows you to apply recovery file and then flash to either clockworkmod or sprecovery which ever one you not using and then flash back to the one you want. I'd also recommend try if after all this you flash rom again and same thing happens redownload it and try again. Good luck.
Sent from Droid using, Sapphire v1.0.0/ 928Droid Black Glass 2.2 Theme/ Sholes 1.0 Ghz 7 Slot Kernel.
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
Auto Kill Level --> Safe
Auto Kill Frequecny --> Every One Hour
Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
fadimck said:
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
Auto Kill Level --> Safe
Auto Kill Frequecny --> Every One Hour
Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
Click to expand...
Click to collapse
Please note, that there have been wide reports of people having issues with various task killer apps consuming excessive amounts of battery life when used on a Droid with Froyo.
Please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
[*]Auto Kill Level --> Safe
[*]Auto Kill Frequecny --> Every One Hour
[*]Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
Click to expand...
Click to collapse
Please note, that there have been wide reports of people having issues with various task killer apps consuming excessive amounts of battery life when used on a Droid with Froyo.
Click to expand...
Click to collapse
Okay, I didn't know this info as I've Milestone with stock OS 2.1
Sent from my Milestone using XDA App
Updated my SD card to CM7.0.3 and want to use an overclock kernel.
Which one is best to use from the downloads available here do you just use the latest 040411 or are some of the test builds good?
I think most people (myself included) are having pretty good luck running 1.3 ghz from the 042411 file. I'm on 7.0.2 but I haven't seen anything saying it breaks moving to 7.0.3. Had it running OC'd for about a week and haven't had any odd behavior so I'd start there.
- From the Test Builds Section
findmike said:
I think most people (myself included) are having pretty good luck running 1.3 ghz from the 042411 file. I'm on 7.0.2 but I haven't seen anything saying it breaks moving to 7.0.3. Had it running OC'd for about a week and haven't had any odd behavior so I'd start there.
- From the Test Builds Section
Click to expand...
Click to collapse
how is the battery usage when overclocked?
When I first set up my SD card the following instructions were in the thread concerning overclocking
5a. *Optional* If you want to run an overclock kernel you need to choose and download a compatible kernel for SD (not eMMC).
5b. Move the uImage file from the SD card to your pc as a backup.
5c. Rename the oc kernel you have downloaded uImage copy it to the SD card.
Can I simply take the zip file for the 042411 kernel open it and swap the uImage files. I saw in another thread about flashing it.
Had lots of trouble getting the 7.0.3 update to take, timing the hold the n and power buttons trick.
Also I saw something about using setcpu to overclock, can someone fill me in on that, is it software or somewhere in the CM7 settings?
s52m3 said:
how is the battery usage when overclocked?
Click to expand...
Click to collapse
I download with Kernel Manager app the one who is recommended for my device.
I use Test kernel at 1,3G without any problem.
RASTAVIPER said:
I download with Kernel Manager app the one who is recommended for my device.
I use Test kernel at 1,3G without any problem.
Click to expand...
Click to collapse
Are you talking about this app
https://market.android.com/details?id=com.teamwin.kernelmanager.free&feature=search_result
Battery life seems to be pretty good right now but I understand the latest CM builds have some fixes that help increase battery life. I don't think the overclock really effects battery life all that much since the vast majority of the time it doesn't need to kick into high speed.
For the install of the kernel, I normally just flash that when I flash the OS and Gapps. If you are running CM7 off your SD card, I can't help much there except to say that it's SOOOO much easier to run off eMMC since I can just use the built in Rom Manager App to jump into Rom Manager and update things without having to have a bootable card or modifying any files.
Regardless of SD / eMMC install, you don't need to use SetCPU with CM7. If you get the kernel installed, just go into Settings / CyanogenMod settings / Performance / CPU settings and you can change. Most people use the OnDemand performance governor with 1300 max and 300 min and set on boot checked.
I leave Set on Boot off in case something goes goofy. I just reset the overclock to 1300MHz when ever I reboot with a new build.
I could never get the 424 OC to load on my Nook (always got the "expected ) error) so I just swap the OC kernel and system folder into each new build. It's a few extra steps but at least it works.
I'm running N67 at 1300MHz from a Sandisk Class 4 16GB card. Works great!
Tried the 0424 kernel and it stops on first line saying it expected something. Saw someone else had this problem in another post
Just found this on another post
Kernel Issues:
* Flashing OC kernel results in "ANDROID" hanging/bootloops on boot. You need to change the updater-script to ext4, or use this kernel. Here is information about the filesystems used.
* Does the beta test have an OC kernel? No. And do not use any posted OC kernels with it.
* Which OC kernel can I use with stable/nightlies? Either the latest test (4/24) or stable (4/04) can be used. Both need the updater-script to be changed to ext4. Look here for information.
I will try this new one.
GTT1 said:
Tried the 0424 kernel and it stops on first line saying it expected something. Saw someone else had this problem in another post
Just found this on another post
Kernel Issues:
* Flashing OC kernel results in "ANDROID" hanging/bootloops on boot. You need to change the updater-script to ext4, or use this kernel. Here is information about the filesystems used.
* Does the beta test have an OC kernel? No. And do not use any posted OC kernels with it.
* Which OC kernel can I use with stable/nightlies? Either the latest test (4/24) or stable (4/04) can be used. Both need the updater-script to be changed to ext4. Look here for information.
I will try this new one.
Click to expand...
Click to collapse
You're running CM7 off an SD card, unless you want to mess up whatever you have on internal eMMC, don't go changing scripts or flashing things which don't apply to your install. Whichever way you got your CM7 installed, stick to the original instructions and follow up on the original threads instead of grabbing bits and pieces here and there. You'd save yourself and others a lot of confusion.
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!
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
Description
This module is my port of Crossbreeder, the old version was designed for Android 4.4 and below. So if you try use it on Android 5.0 and above, you will have some problems with it.
But now I have fixed that problem, and have changed some of the script; which was out-of-date. I have also added some new features of my own.
Details
For those who want to know what is this mod for, here are the details:
Random/Frandom tweak
Remove /dev/random as it's blocking . Link it to non-blocking /dev/urandom. Since /dev/random is blocking and designed to protect us from Quantum alien cryptographers with mathematical certainty and urandom is non blocking pseudo-random device that most apps and OSs are using anyway and with Haveged running, is as secure anyway as it's very difficult to empty the entropy pool faster than Havege can replenish it. Pre ICS devices have a lot to gain with this but ICS+ devices show visible gains too.
Haveged/Entropy tweak
Modulate OS entropy levels for lag reduction ala Seeder. The whole OS reads either /dev/random or /dev/urandom and both need entropy. However this mod uses a completely different, lightweight and efficient random number generator called Havege . This sharply reduces cpu consumption and corresponding battery life loss compared to Seeder. It also does a better job at keeping entropy levels high hence your device is more responsive. It doesn't run in a CPU intensive loop either. The extend queue functionality has also been added to CrossBreeder. See here for another rationale favouring Havege compared to Rngd - ( Look for the limitations)
Fix "Only position independent executables (PIE) are supported" problem on Android 5.0+ device
Here is how to fix it :
1. Install the Hex Editor.
2. Open the file in Hex Editor.
3. Find the 17th number, if the number is 02, change it to 03.
4. Save the file, that's it !
[Add-on 1] Dynamic Z-RAM/LMK
This tweak will automatic find how much ram do you have, how much ram do you left, then according to these value to set zram/lmk size.
[Add-on 1] Dynamic Power Saving
Here is the original post, I found this feature in Feradroid v0.24
A little translate:
DynBS can significantly reduce power consumption without shutting down the main functionality of the Android device (such as Wi-Fi, Bluetooth, mobile Internet, screen brightness, background processes) by reducing unnecessary high-frequency CPU when not needed.
Magisk Busybox Restorer
This module will let the busybox can be used externally at Magisk v15+
By linking the busybox in /data/adb/magisk to /sbin
Only support Magisk v15+
Trouble Shooting
1. Stuck at the boot stage
---> Reboot again ---> Not work? ---> Flash it again to uninstall it.
2. Application keep crashing after installed this module
---> Just disable Dynamic LMK.
3. CTS Profile miss match
---> Enable all the ways that you can hide the magisk, if its not work, then you can try Universal SafetyNet Fix
4. Any problem about CPU frequency, like your device become so slow, or become warmer, etc.
---> Disable DynBS can fix the problem
5. How to open the setting menu?
---> Open terminal, and type "cbconf" can open it.
6. The phone shows the message of rebooting/turning off but after 30 mins ,the process is not finished
---> Try to forced shutdown
7. Busybox-ndk failed because of install CrossBreeder
---> Try to use mine busybox
This module only test on my HTC One M7 running latest Slim 7.1.2 with Magisk 15.3
Not tested with Android 8.0+ yet.
If you want to install any add-on, you must install the main mod first.
Credit
1. Crossbreeder ( https://forum.xda-developers.com/showthread.php?t=2113150 ) - For most of files
2. FeraDroid Engine ( https://forum.xda-developers.com/an...beta-feradroid-engine-v0-19-ultimate-t3284421 ) - For the Governor Tweak
3. Dynamic Power Saving ( http://4pda.ru/forum/index.php?showtopic=620736&st=1120 )
Github Link
I'm on Lineage OS, OnePlus 3T, Radioactive Kernel, and for some reason whenever I enable this module, it breaks Root (MagiskSU). I'm not sure if this is a known problem, but if not, now you know. ;P
Yea it breaks safetynet for me when I enabled it on magisk. Though for the mod itself that seems to be working great, don't know if it's placebo but I am noticing a little less "lag" on some apps.
Finally, was searching for any information on this module, and got nothing except the original. Any reason why it took so long for a thread to be created about it?
loocool2 said:
Finally, was searching for any information on this module, and got nothing except the original. Any reason why it took so long for a thread to be created about it?
Click to expand...
Click to collapse
I messaged Rorsch about making a thread for their module a couple of days ago, so I assume the thought just didn't occur to them to make a thread. But now it's all good because there's a thread for it
Breaks Root? Try this
ht#tps://drive.google.com/open?id=0B1nFPsNMRIiiYzlsbWxxazlPUkk <------- Remove #
Test on Slimroms 7.1.2 / HTC ONE M7
Rorsch_X1 said:
Breaks Root? Try this
ht#tps://drive.google.com/open?id=0B1nFPsNMRIiiYzlsbWxxazlPUkk <------- Remove #
Test on Slimroms 7.1.2 / HTC ONE M7
Click to expand...
Click to collapse
Seems to be working! Although it's not 100% stable, it's better than having a totally broken Root.
This module gets me stuck in a strange bootloop everytime: I've tried 0.3a version some a week's ago and now with 0.8b. Phone seems to be booting, it passes Google splash screen, there's that little vibration that means the phone's booting right and then it gets stuck in there. Which logs should I provide to be helpful? Maybe last-kmsg?
Sent from my Nexus 5X using XDA Labs
edoardotavecchio said:
This module gets me stuck in a strange bootloop everytime: I've tried 0.3a version some a week's ago and now with 0.8b. Phone seems to be booting, it passes Google splash screen, there's that little vibration that means the phone's booting right and then it gets stuck in there. Which logs should I provide to be helpful? Maybe last-kmsg?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Maybe... but we could just try something easier... ;P
What tweaks have you got? Like; are you using other Magisk modules? Have you changed your build.prop via an app like L Speed, or something like that? Have you made any kernel tweaks? What CPU governor are you using?
It sounds like something CB is trying to modify is conflicting with something else.
edoardotavecchio said:
This module gets me stuck in a strange bootloop everytime: I've tried 0.3a version some a week's ago and now with 0.8b. Phone seems to be booting, it passes Google splash screen, there's that little vibration that means the phone's booting right and then it gets stuck in there. Which logs should I provide to be helpful? Maybe last-kmsg?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Maybe you have too many file in the /system or installed too many modules
It will take a lot of time on the mount stage
Send me your magisk log
nan0s7 said:
Maybe... but we could just try something easier... ;P
What tweaks have you got? Like; are you using other Magisk modules? Have you changed your build.prop via an app like L Speed, or something like that? Have you made any kernel tweaks? What CPU governor are you using?
It sounds like something CB is trying to modify is conflicting with something else.
Click to expand...
Click to collapse
As tweaks, I've removed HEBF and LSpeed apps because I've had the same idea as you. As Magisk Modules, I've installed some camera and audio mods (Some very common mods for 5X: eis, 60fps libs, surround audio mod), Universal Deep Buffer remover, Selinux permissive script and Viper. The only one which modifies build.prop is EIS module. Does Crossbreeder modify build.prop too? Should I remove EIS in order to make this work?
As CPU governor, I'm using interactive (governor profile:Glasscannon)
Rorsch_X1 said:
Maybe you have too many file in the /system or installed too many modules
It will take a lot of time on the mount stage
Send me your magisk log
Click to expand...
Click to collapse
That's strange because usually it's very very fast, it takes something like 3-4 seconds after the vibration. Eith this module installed, I've tried to wait even 10 minutes without any success.
Now I'll retry and send you Magisk log.
Sent from my Nexus 5X using XDA Labs
That's my magisk log without having crossbreed installed. Can you take a look and see if there's something in conflict with your module? @Rorsch_X1
Sent from my Nexus 5X using XDA Labs
edoardotavecchio said:
That's my magisk log without having crossbreed installed. Can you take a look and see if there's something in conflict with your module? @Rorsch_X1
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I don't know about conflicts, but I saw you're using the audmodlib module by @ahrion with the V4A module by @metaspook. That Viper module isn't made to utilise the audmodlib... You probably wanted this one: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Didgeridoohan said:
I don't know about conflicts, but I saw you're using the audmodlib module by @ahrion with the V4A module by @metaspook. That Viper module isn't made to utilise the audmodlib... You probably wanted this one: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Click to expand...
Click to collapse
I know that and I've tried it but it didn't work.
Edit: Now it is working. what
Thanks for your suggestion.
Sent from my Nexus 5X using XDA Labs
crayola555 said:
Yea it breaks safetynet for me when I enabled it on magisk. Though for the mod itself that seems to be working great, don't know if it's placebo but I am noticing a little less "lag" on some apps.
Click to expand...
Click to collapse
I am a big fan of crossbreeder... However...
Iirc without frandom... You are not actually generating "random"
And according to what I have read (stop me if I'm wrong)... The less "lag" you are seeing is from that random number generation keeping your processor a little more ramped up... Equivalent to turning touchboost up a notch... Or raising your cpu min frequency...
Sent from my Nexus 6 using Tapatalk
This work on rooted s7 w/ Exynos CPU?
pan.droid said:
This work on rooted s7 w/ Exynos CPU?
Click to expand...
Click to collapse
Yes, it works on all ARM devices.
edoardotavecchio said:
That's my magisk log without having crossbreed installed. Can you take a look and see if there's something in conflict with your module? @Rorsch_X1
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I have tried am3d & v4a & Audio-Modification-Library & deep buffer remover with my CrossBreeder , but they all works fine.
Where were you stuck at? Boot Animation or Boot logo?
By the way, are you using Android O? I see libfmas.so & android.hardware.audio.low_latency.xml & android.hardware.audio.pro.xml in the log you sent to me.
Rorsch_X1 said:
I have tried am3d & v4a & Audio-Modification-Library & deep buffer remover with my CrossBreeder , but they all works fine.
Where were you stuck at? Boot Animation or Boot logo?
By the way, are you using Android O? I see libfmas.so & android.hardware.audio.low_latency.xml & android.hardware.audio.pro.xml in the log you sent to me.
Click to expand...
Click to collapse
I get stuck at bootanimation after the "boot completed" vibration (that little vibration which runs a few seconds before the phone booting, usually reporting that boot process has been nearly completed). I've never experienced a situation like this in 6 years of modding so I don't know what could have gone wrong: the vibration usually doesn't trigger (when phone can't boot and gets stuck in a bootloop) or after a few minutes, a few seconds before booting (when the OS takes a lot to mount partitions or compiling caches, per example when you clean flash a new OS and caches have to be rebuilt). It's so strange that vibration fires and the phone doesn't boot anyway. I've tried to let the phone work for something like 20 minutes (which I consider is even too much for a simple boot) but nothing happens anyway.
Anyway no, I haven't updated to O yet because some mods aren't compatible with it yet so I've stopped on 7.1.2 which is stable and fully supported.
edoardotavecchio said:
I get stuck at bootanimation after the "boot completed" vibration (that little vibration which runs a few seconds before the phone booting, usually reporting that boot process has been nearly completed). I've never experienced a situation like this in 6 years of modding so I don't know what could have gone wrong: the vibration usually doesn't trigger (when phone can't boot and gets stuck in a bootloop) or after a few minutes, a few seconds before booting (when the OS takes a lot to mount partitions or compiling caches, per example when you clean flash a new OS and caches have to be rebuilt). It's so strange that vibration fires and the phone doesn't boot anyway. I've tried to let the phone work for something like 20 minutes (which I consider is even too much for a simple boot) but nothing happens anyway.
Anyway no, I haven't updated to O yet because some mods aren't compatible with it yet so I've stopped on 7.1.2 which is stable and fully supported.
Click to expand...
Click to collapse
Maybe the some script conflict with your system, try this version, you can enable/disable the tweak by yourself.
https://drive.google.com/open?id=0B1nFPsNMRIiiM2xocl9RTGt3OEk
After install this version, you need to go to /data/CrossBreeder, open the file with text editor then change the 0 to 1 to enable the tweak, I disable all in these config files.
P.S. Don't edit the CONF