Database Info

[Kernel] Dodgekernel v1.6 SENSE (uv, oc, bfq, bash, ext3, and ext4)

Here is the next version of my HTC Evo Shift Sense kernel. It was built from the 2.3 gingerbread source. It should be stable and smooth as that was my main goal with this. I usually dont come here to XDA as often, so you may receive better support for questions/concerns here at SDX
Kernel Features:
Undervolted
Overclocked to 1.92Ghz
Interactive governor added
Smartass governor added
Enabled powersave governor
Faster charging over USB (Still slower than AC Wall charger)
BFQ (Budget Fair Queuing) i/o scheduler
Full bash mod (Gives you working directory, command history, tab completion and a shameless plug of my kernel in the shell )
Enabled ext4 filesystem support
Included HAVS/SVS support for Vipermod or incredicontrol (thanks to cayniarb and his tiamat kernel for guidance)
Init.d scripts supported (needs testing)
Default Settings:
Max Frequency = 1.209GHz
Min Frequency = 245MHz
Governor = Interactive
I/O Scheduler = BFQ
Download a cpu control application like No-Frills/SetCPU from the market for editing these settings.
Information:
The bash mod is something that cloverdale proved was what people liked so I went ahead and edited the ramdisk and zip to set that up so thanks to him for that.
After playing with the frequency table a bit, I changed methods this time and used the CM method for overclock on this phone. Its a method I saw several developers use while on 2.2 and seemed a bit cleaner than the method that I had originally set up. Thanks to toast, for the implementation of that.
This is still something I want to improve so I really need some feedback as to what you guys want to see. I will try my best to fulfill all logical suggestions.
With the bash mod, if you flash a kernel over this, it may (depending on the script method) remove the nice pretty text for the shell. It will still be functional as that part is installed to the phone itself. I will post up a 'bash removal' zip to restore back to default eventually
Ext4 FS has been added. It requires you to convert your filesystem from ext3 to ext4. Ive made it pretty simple for you to do with a script inside of a flashable zip. If something goes wrong, please let me know.
HAVS/SVS passes the VDD (Voltage draw for each frequency) values to userspace, meaning that they can be set by the user. While nothing NEEDS to be done for it to work, users now of the option of tweaking the voltages just a bit in order to increase their battery life. This was tested with the free application 'incredicontrol' from the market. ANY and ALL bug reported due to the fact that you dropped the voltages a bit to much will be ignored. This is DUE AT OWN RISK. I can tell you that from my experience, dropping down 50mv is about as far as you can go on my kernel. Good luck.
To anyone wanting to learn how to start getting into development, Please email, PM, or find me on irc #gen-dev, #sdx-developers, #htc-evo-3d on irc.freenode.net. I will teach you whatever I can as best I can. It is the only way to progress the development community. Ive spent hours teaching several over the past week and countless hours in the past. Please do not hesitate to ask.
Kingdom ROM Users:
Thanks to nfinitefx45 for letting me know what had to be changed in the ramdisk, I now have a new zip for this ROM that includes the full bash mod.
Downloads:
all downloads can be found here
Installation:
EXT3:
1. Download and place on SD card
2. Boot into recovery and make a back up if required
3. Flash zip
4. Reboot
EXT4:
1. Download both the ext4 kernel and ext4 conversion zip and place both on SD card
2. Boot into recovery and make a nandroid backup (very important)
3. Flash EXT4_fs_conversion.zip (do not reboot)
4. Restore the nandroid you just made (do not reboot)
5. Flash ext4 kernel.
6. Reboot
Returning to EXT3:
1. Download ext3 conversion zip and have an ext3 kernel. Ensure both are on the SD card
2. Reboot into recovery and make a nandroid backup (very important)
3. Flash EXT3_fs_conversion.zip (do not reboot)
4. Restore the nandroid you just made (do not reboot)
5. Flash ext3 kernel
6. Reboot
FAQ:
Q: What is EXT4?
A: Ext 4 is the newest version of the extended filesystem. It is mainly used as the default linux filesystem in most distros. It has improved read and write speeds over the previous versions (ext3 and ext2) It should provide slight speed improvements over the default filesystem on the shift, ext3.
Q: Why do I have to 'convert' my filesystem and is it necessary?
A: My ext4 kernel will only mount system, data, cache, and devlog partitions as ext4. It is not 100% necessary to convert the existing filesystem to ext4 as ext4 is backwards compatible, meaning it can mount ext3 partitions as ext4. By converting it to true ext4, you will be able to take full advantage of ext4 speed.
Q: Will this affect the way I flash ROMs and modifications?
A: In theory, no. The ROM should flash like normal but if they do have a custom kernel included, it will be necessary to flash an ext4 kernel after the ROM.
Q: Is this safe?
A: While working with partitions and their filesystem is considered risky on any account, I have made the conversion zips as simple and as safe as I possibly can. If any corruption does occur, it is usually fixable but should not happen in the short life of these devices.
Q: Does this change the way the backup and restore functions work in CWM or TWRP?
A: No, it should not effect the way the recoveries backup and restore data. There have been some notification of the 'wipe' functions in 'mounts and storage' reformatting back to ext3 but, you should be able to just flash the conversion zip again to return to ext4.
Q: I want to use a different kernel that is not ext4.
A: You will need to flash the EXT3 conversion zip to return your partitions to ext3. Then flash like normal.
Q: AOSP ROMs are on ext4, why do they not require the conversion?
A: While this was an option, I felt it best to do ext4 100%. An ext3 partition can be mounted as ext4 and it will provide some speed enhancements but, it is not full ext4. AOSP roms are simply mounting the ext3 partitions as ext4 which is fine, just not my preferred method.
Q: Will this effect my sdcard in anyway
A: No it will not.
Q: What do I do if something goes horribly wrong and my phone is stuck in a bootloop and I cant pull it out?
A: This is a help forum, post your issues and I or another helpful person will help you. If you are not receiving help, PM me or email me at [email protected] and I will get back to you.
Click to expand...
Click to collapse
Changelog:
11/11: Added support for HAVS/SVS. Re-worked clock table and added 1.9ghz. Enabled init.d scripts. Finished tweaking smartass governor.
11/03: Added EXT4 version of both kernels. Added bash mod to Kingdom ROM version.
11/02: Initial Release v1.5
Source available at https://github.com/dodgejcr/speedy-2.6.35
Thanks to all the people in the huddle that tested this before release to ensure it was up to standards (especially strapped and crump). Big thanks to joeykrim for his FlashimageGUI app that made testing 20 or so kernels over the past day or two less of a headache

Thanks for this. Just installed and seems to be great
Sent from my PG06100 using xda premium

For the Kingdom you will need to change the dhcpcd line in speedy.rc to
service dhcpcd_eth0 /system/bin/dhcpcd -ABKL eth0
disabled
oneshot
this will allow for the wifi to enable.
hope that helps

nfinitefx45 said:
For the Kingdom you will need to change the dhcpcd line in speedy.rc to
service dhcpcd_eth0 /system/bin/dhcpcd -ABKL eth0
disabled
oneshot
this will allow for the wifi to enable.
hope that helps
Click to expand...
Click to collapse
Sweet thanks. I had planed on either asking you today or tearing down your ramdisk to find it. Saved me time. If I add any more tweaks to the ramdisk ill be sure to add this. Much apreciated

Thank you Dodge! XDA is honored by your visit! So... when we getting an AOSP flavor?

jesusice said:
Thank you Dodge! XDA is honored by your visit! So... when we getting an AOSP flavor?
Click to expand...
Click to collapse
Been working on one for a while now. Cant seem to make myself happy with it but I have yet to stop. With this one done and out of the way, maybe I switch over to AOSP and whip something up for that. LOL Who knows

You the man Dodge. Thanks for all the work, been running smooth so far.
Sent from my PG06100 using Tapatalk

been running for two days, smooth as buttermilk.

Thanks for the fix dodge! Runnin great nice and smooth, hope you tweak it up and add nfinite's fix in. As soon as I come up with some ideas will drop'em on ya. Enjoy the movie! Lol
Sent from my AT100 using Tapatalk

-somebody- said:
been running for two days, smooth as buttermilk.
Click to expand...
Click to collapse
+1... Never disappointed with your kernels...
Sent from my PG06100 using Tapatalk

Ext4 support for filesystem
Sent from my PH44100 using XDA App

nfinitefx45 said:
Ext4 support for filesystem
Sent from my PH44100 using XDA App
Click to expand...
Click to collapse
+ 1 on the ext4 support dodge!
Sent from my AT100 using Tapatalk

nfinitefx45 said:
Ext4 support for filesystem
Sent from my PH44100 using XDA App
Click to expand...
Click to collapse
Sounds like a glorious idea. Ill probably add that for the next release. Keep the suggestions coming

modmouse78 said:
Thanks for this. Just installed and seems to be great
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
touche, seems to run quicker than x99 at 1.2 ondemand governor

dodgejcr said:
Sounds like a glorious idea. Ill probably add that for the next release. Keep the suggestions coming
Click to expand...
Click to collapse
Enable call recording.

jesusice said:
Enable call recording.
Click to expand...
Click to collapse
Ooh a challenge. Haven't done that before, should be interesting. Ill give it a shot
Sent from my HP Touchpad

You do know J this is a sese kernel! You lost or forget what thread you're in ? Lol jk
Sent from my PH44100 using Tapatalk

dodgejcr said:
Ooh a challenge. Haven't done that before, should be interesting. Ill give it a shot
Sent from my HP Touchpad
Click to expand...
Click to collapse
Video calling support is in the newer aosp kernels. If you need a start on where to look. I don't think the .13 one does tho I could be wrong. Not sure how easy it would be to impliment. Best of luck tho.
Sent from my PG06100 using xda premium

sparksco said:
Video calling support is in the newer aosp kernels. If you need a start on where to look. I don't think the .13 one does tho I could be wrong. Not sure how easy it would be to impliment. Best of luck tho.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
being that the shift doesnt have a front facing camera video calling is kinda pointless (just my opinion)

Check in the dhd and dz threads as there source is very similar to ours
Sent from my PH44100 using XDA App

[NookHD+] CM10.1 native emmc install Now part of CM Nightlies

By popular demand, I am bringing to you CM10.1 that you can install into Nook's internal ROM.
Note, this version totally overwrites your ROM, so back up everything important before proceeding. This is not a dual-boot solution as before, you do loose B&N ROM for good after installing this.
This is work in progress, yadda yadda.
Simplified instructions if instructions below don't work for you or you cannot follow them.
Get emmc-cwm-early2.1.img.gz, gunzip and write it to an sdcard of at least 1G in size (all content on that card will be lost).
Download CWM recovery (text) or TWRP recovery (gui) zip if you want internal recovery to be replaced with CM one (if you don't know what is it about, then you need ONE of these).
Also download latest binary zip from CM nightlies: http://download.cyanogenmod.com/?device=ovation
Add all these files + whatever other packages you might need right away on to the sdcard.
Boot from that sdcard, and install recovery (if desired) and the cm10.1 binary and whatever else you put there.
Erase /data (During initial install only. this is important to avoid crashes on bootup! Naturally, make sure you have copies of whatever important info from there).
unmount /sdcard and remove the card from the Nook. You might need to use this sdcard for your recovery needs in the future should EMMC content become badly damaged, so probably a good idea to have a copy of it somewhere.
Congrats, now on reboot you'll get into cm10.1 on your Nook HD+.
When you need to get into recovery, you can either do "reboot to recovery" in reboot menu (need to enable that in settings) or reboot the nook, and when you see original nook boot logo, press and hold power + home buttons for about 4 seconds.
If you plan to use USB Host feature, you will need a gender changer, as B&N decided not to release a special cable so far. The control to enable USBHost is in quick settings panel (slide down in the top right corner of the screen to bring it up). (QS controls are not available in CM nightly builds so you'll need to install the switcher app for now if you need it).
Known problems:
- Nook app reports incompatible in market (workaround1: just sideload it ; workaround2: change ro.product.device to nookhdplus in build.prop) - This is because they specifically blacklist Nooks! Note that workaround #2 will actually kill your sound, so revert back when you are done.
- Certain sdcards still remain unstable.
- Google Earth crashes when pressing "my location" button (but works fine otherwise).
Useful apps:
Overall loudness and volume control app: NookHDVolumeAdjuster-1.apk
Touch screen sensitivity control: NookTouchscreenSensitivityAdjuster-4.apk (backup link)
USB host control (not really needed, as you can use Quick Settings panel): USBHostSwitcher.apk
Changelog:
13/08/09 - We are official part of CM now, yay! Further updates will be at http://download.cyanogenmod.com/?device=ovation
13/08/01 - cm-10.1-20130801-UNOFFICIAL-ovation-emmc.zip
- Data usage display should work now
13/07/19 - cm-10.1-20130719-UNOFFICIAL-ovation-emmc.zip
- Picked some kernel fixes from omapzoom tree that I think would be useful for us too, this includes some voltage changes (decreases).
- Disabled hwui scissors optimization as it seems to be doing more harm than good.
- Reverted too greedy davlik vm settings
13/07/16 - cm-10.1-20130716-UNOFFICIAL-ovation-emmc.zip *Experimental*
- Update wifi drivers to R5.SP3.06
13/07/11 - cm-10.1-20130712-UNOFFICIAL-ovation-emmc.zip (backup link)
- Added Apple keyboard support
- Updated to CM-10.1.2 for security fixes
13/07/10 - cm-10.1-20130710-UNOFFICIAL-ovation-emmc.zip
- Updated to CM-10.1.1 for security fixes
13/07/08 - cm-10.1-20130708-UNOFFICIAL-ovation-emmc.zip
- NTFS and ExFAT support from upstream
13/07/06 - cm-10.1-20130706-UNOFFICIAL-ovation-emmc.zip
- redone touchscreen sensitivity changing mechanism. (app to control touchscreen sensitivity NookTouchscreenSensitivityAdjuster-4.apk)
13/07/04 - cm-10.1-20130704-UNOFFICIAL-ovation-emmc.zip
- upgraded to fixed SGX DDK [email protected] (this fixes Google Earth, and a bunch of games)
13/07/03 - cm-10.1-20130703-UNOFFICIAL-ovation-emmc.zip Experimental
- experimental touchscreen sensitivity change
- usb ids changed to match stock
- swap support enabled
13/06/30 - cm-10.1-20130630-UNOFFICIAL-ovation-emmc.zip
- Serial number is now visible in Android
- usb audio now actually works (only for output)
13/06/29 - cm-10.1-20130629-UNOFFICIAL-ovation-emmc.zip
- in-kernel bluetooth
13/06/26 - cm-10.1-20130626-UNOFFICIAL-ovation-emmc.zip Experimental
- cpu frequency changes for screen on scenario, new sgx binary blobs.
13/06/24 - cm-10.1-20130624-UNOFFICIAL-ovation-emmc.zip
- more kernel drivers for bt hid, usb 3g modems and gps devices
13/06/15 - cm-10.1-20130615-UNOFFICIAL-ovation-emmc.zip
- WiFi Direct and BT tethering are now working
- /sdcard now points to internal storage.
13/06/13 - cm-10.1-20130613-UNOFFICIAL-ovation-emmc.zip
- Boosted speaker volume. If you do not like new loud volume, flash this reversal zip after every ROM update: quietvolume-2.zip
- zinio now should work out of the box
13/06/11 - cm-10.1-20130612-UNOFFICIAL-ovation-emmc.zip
- Fixed HDMI audio
- Added USB audio support
13/06/08 - cm-10.1-20130608-UNOFFICIAL-ovation-emmc.zip
- Fixed nav bar settings crash
13/06/05 - cm-10.1-20130605-UNOFFICIAL-ovation-emmc.zip
- USBHost access is now conveniently located in QuickSettings. (IF you use some mod that disables quick settings, you still need my old ugly USBHost switcher app, just sideload it).
- now any (one at a time) usb storage should be automounted no matter how you plug it.
13/06/02 - cm-10.1-20130603-UNOFFICIAL-ovation-emmc.zip
- Forced USB Host support.
13/05/30 - cm-10.1-20130530-UNOFFICIAL-ovation-emmc.zip
- No Nook-specific changes, based on CM10.1-RC3
13/05/27 - cm-10.1-20130527-UNOFFICIAL-ovation-emmc.zip
- Fixed microphone input volume
- Kernel change to hopefully better work with some sdcards.
13/05/12 - cm-10.1-20130512-UNOFFICIAL-ovation-emmc.zip
- Fixed A2DP audio
- Fixed booting when not connected to PC/charger.
13/05/11 - cm-10.1-20130511-UNOFFICIAL-ovation-emmc.zip
- Should fix sgx crash on startup for those affected -- not.
- Cover close now should sleep the device (please test)
- Updated screen properties to highdpi (though that did not fix Nook app compatibility in market)
- Baselined on CM10.1-RC2
13/05/10 - cm-10.1-20130510-UNOFFICIAL-ovation-emmc.zip
- Wifi battery drain should be gone now.
13/05/05 - cm-10.1-20130505-UNOFFICIAL-ovation-emmc.zip
- Fixed mmc presentation, BT, sdcard mounting.
13/05/04 - cm-10.1-20130504-UNOFFICIAL-ovation-emmc.zip initial release.

Thanks for this though.
Verygreen, I am interested how this boots without sdcard as before the expliot worked because B&N left dev code to boot a kernel from sd card.
What exploit is used to boot from internal since sdcard isn't used.
Also I don't think cm10 is needed really.
I think its best to put the work into cm10.1 as its the latest platform and try bring that up to the same stage as cm10.

Wow, thank you once again verygreen! Thank you so much for your efforts!
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Regardless, appreciate your efforts once again!

HiddenG said:
Wow, thank you once again verygreen! Thank you so much for your efforts!
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Regardless, appreciate your efforts once again!
Click to expand...
Click to collapse
Is the reboot to 99% problem solved ? This is the biggest issue to me.

sorrowuk said:
Verygreen, I am interested how this boots without sdcard as before the expliot worked because B&N left dev code to boot a kernel from sd card.
What exploit is used to boot from internal since sdcard isn't used.
Click to expand...
Click to collapse
Same method as Bauwks, B&N forgot to fix it, they fixed some other possible vectors only.
I was holding to this knowledge hoping that it would be useful on next B&N reader, but it does not look like they'll release another omap-based one, so no need to keep suffering anymore.
So here's hope whatever they release next, the debugging code will remain in place
HiddenG said:
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Click to expand...
Click to collapse
Yes, this does overwrite stock ROM, so no dualboot.
While it's possible to perform some hair-splitting by putting multiple kernels into boot partition, that's quite a bit of hassle + all the /data splitting, so I decided to not go that way, at least yet.
There are performance differences. I did not perform any real studies, but I was shocked at how fast the install phase in cwm works compared to sdcard.

lchen5 said:
Is the reboot to 99% problem solved ? This is the biggest issue to me.
Click to expand...
Click to collapse
Yes, it is solved by removing the ROM, so nothing is left there that could complain about cards with too many partitions

Awesome
I've gotten this loaded up this morning, haven't done a whole lot with it as of yet, but it did boot right up
I have noticed one thing that is not working correctly, specifically the sd card. It's reported as not mounted.

aszid said:
I've gotten this loaded up this morning, haven't done a whole lot with it as of yet, but it did boot right up
I have noticed one thing that is not working correctly, specifically the sd card. It's reported as not mounted.
Click to expand...
Click to collapse
Yes, I was just going to post that. Verygreen forgot to change the vold.fstab file from the sdcard version to emmc version.
Go to /system/etc/ and edit the vold.fstab file to say "/storage/sdcard1 auto" instead of "/storage/sdcard1 5". Just change the 5 to an auto. Then reboot and it should be ok.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
Yes, I was just going to post that. Verygreen forgot to change the vold.fstab file from the sdcard version to emmc version.
Go to /system/etc/ and edit the vold.fstab file to say "/storage/sdcard1 auto" instead of "/storage/sdcard1 5". Just change the 5 to an auto. Then reboot and it should be ok.
Click to expand...
Click to collapse
It's always the small things that gets forgotten, sigh.
I knew I needed to update that, but did not find it at 4am. Now it's in my tree, so next version will have it fixed.
Also need a better way to write sdcard image, I guess, without uploading a whole gig or so of zeros which will get slow. I tried to put in some shortcuts to minimize the write area, but failed so far. Since everything is in the same partition, changing stuff on the fly is hard.
Perhaps a solution where we only use sdcard as means to do initial bootstrap and write correct recovery and use /data/media as the actual sdcard would be better after all.

Follow up question
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?

jentous said:
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
Click to expand...
Click to collapse
For restore (note, I did not really test any of these steps, but that's how it should unfold):
boot into recovery image from sdcard you made at the beginning.
Upload the backup boot image there (adb push mmcblk0p4 /tmp)
then do adb shell and in there write the image in place:
dd if=/tmp/mmcblk0p4 of=/dev/block/mmcblk0p4 bs=1048576
then do:
mount /bootdata ; rm /bootdata/BootCnt
The removal of BootCnt will tell stock u-boot to force factory restore.
now remove sdcard and reboot, the Nook will do factory restore and you are back to some sort of early 2.0.0 B&N release.

verygreen said:
It's always the small things that gets forgotten, sigh.
I knew I needed to update that, but did not find it at 4am. Now it's in my tree, so next version will have it fixed.
Also need a better way to write sdcard image, I guess, without uploading a whole gig or so of zeros which will get slow. I tried to put in some shortcuts to minimize the write area, but failed so far. Since everything is in the same partition, changing stuff on the fly is hard.
Perhaps a solution where we only use sdcard as means to do initial bootstrap and write correct recovery and use /data/media as the actual sdcard would be better after all.
Click to expand...
Click to collapse
I've been trying to examine what you have done here, and have most of it figured.
That CM zip is pretty straight forward where it just flashes the rom to emmc /system and replaces the boot.img.
The CWM looks straight forward too, but you must use the empty file for something and I can't quite figure that. I thought maybe you were using it to mount something on emmc but I see no code to do that in the ramdisk. You might have the code in a customized init binary. Recovery looks like just a normal 6.0.3.2 recovery from CM.
A suggestion on the CWM recovery.fstab. Change the boot partition fstype from vfat to emmc and backup/restore will handle it properly. And change the emmc to datamedia and /dev/null instead of vfat and 0p10. That way the emmc media partition will mount properly.
Sent from my Nook HD+ running CM10 on Hybrid SD

leapinlar said:
That CM zip is pretty straight forward where it just flashes the rom to emmc /system and replaces the boot.img.
Click to expand...
Click to collapse
Yes, it's pretty straight-forward, and that was one of the goals. Unlike Kindle where you need to jump through some crazy hoops due to Amazon design decisions, Nook is significantly more relaxed.
The CWM looks straight forward too, but you must use the empty file for something and I can't quite figure that. I thought maybe you were using it to mount something on emmc but I see no code to do that in the ramdisk. You might have the code in a customized init binary. Recovery looks like just a normal 6.0.3.2 recovery from CM.
Click to expand...
Click to collapse
The recovery IS straighforward, there's no modified init or anything like that. I am not sure what empty file do you refer to.
The only difference between this CWM and sdcard cwm for sdcard installs are: removed repartitioning code in postboot script and updated fstab to point back at emmc.
A suggestion on the CWM recovery.fstab, change the boot partition fstype from vfat to emmc and backup/restore will handle it properly. And change the emmc to datamedia and /dev/null instead of vfat and 0p10. That way the emmc media partition will mount properly.
Click to expand...
Click to collapse
Aha, thanks. I'll try this and it'll probably solve the remaining CWM problems for me.
Also need to do twrp image, I guess.

verygreen said:
The recovery IS straighforward, there's no modified init or anything like that. I am not sure what empty file do you refer to.
Click to expand...
Click to collapse
I'm talking about the "file" in the recovery image. It is about 950MB and all zeros.
And if you make those mods to the recovery.fstab, then users can use that CWM to reflash back to stock using the B&N zips.

leapinlar said:
I'm talking about the "file" in the recovery image. It is about 950MB and all zeros.
Click to expand...
Click to collapse
Whoops, forgot to remove.
This is how I zero out sdcard content so it better compresses before uploading it somewhere.

jentous said:
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
Click to expand...
Click to collapse
Based on what verygreen said in the posts above, you should be able to use my stock CWM SD to both backup and restore his new setup. And you can restore an earlier backup of stock too. You can use my 2.1 zip on my thread to put the new stock on if you want replacing his CM10.1 on emmc.
Thanks verygreen, you are awesome!
EDIT: Yes! I just flashed verygreen's new CM10.1 emmc to my internal memory using my stock CWM SD. Worked perfectly.

I just uploaded emmc-cwm-early2.img.gz with fixed recovery.fstab and a zero file removed as well.

Got it going
Thanks Verygreen and Leapinlar.
I got it installed and I saved the boot partition just in case. I hopefully will not be needing to restore, but it is nice to know that I can.
The installed ROM appears snappy and I will report back any issues I discover.

my sdcard is working great after updating the mount. Thanks!
leapinlar said:
Based on what verygreen said in the posts above, you should be able to use my stock CWM SD to both backup and restore his new setup. And you can restore an earlier backup of stock too. You can use my 2.1 zip on my thread to put the new stock on if you want replacing his CM10.1 on emmc.
Thanks verygreen, you are awesome!
EDIT: Yes! I just flashed verygreen's new CM10.1 emmc to my internal memory using my stock CWM SD. Worked perfectly.
Click to expand...
Click to collapse
verygreen said:
I just uploaded emmc-cwm-early2.img.gz with fixed recovery.fstab and a zero file removed as well.
Click to expand...
Click to collapse
Is there any effective difference between the 2 recoveries? That is.. is there any reason i should be bothering to keep 2 different recovery SD cards?
Thanks for all the great work!

aszid said:
Is there any effective difference between the 2 recoveries? That is.. is there any reason i should be bothering to keep 2 different recovery SD cards?
Click to expand...
Click to collapse
There's no great logic in my recovery, just an image I use to test-drive my installs for now.
So you can use whatever other recovery you like.

[Q&A] [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F

[Q&A] [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F
Q&A for [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F2FS
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.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F2FS. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Thanks
@Cl3Kener: Big thanks for your hard work. Installed your kernel yesterday, and can definately see some improvements.
 @ramjet73: Big thanks to you too. I followed your posts/instructions and flashed rastapop+uber and am happy i finally took the plunge.
Now for my question: I have the tricksterMOD and I can't see any color profiles (except the default). How can I apply other profiles? I only see one.
Regards,

On LiquidSmooth LP 4.0 with UBER-L 3.4.105
Governer = optimax
Scheduler = zen
Read Ahead Buffer Size = 3072
Everything is running smooth and fast! Good battery life!

Low brightness after install
Hello, I gave a question... When I installed a last Uber kernel L v4.10 from 9 December of 2014... I have a very low brightness... How can I fix it...
Also I cannot make OC more than 2.7 or 2.8 ... Phone doesn't boot... And how I can fix it...
Thank you for a answer

Hi,
is it advisable to disable filesystem trim in ubers cfg file while using f2fs?
Chet says, F2FS is auto-trimmed: https://plus.google.com/app/basic/stream/z13cxltwwqjcsx3ta22pyx5reobgudsiq04

Are there any negative consequences for clocking the minimum frequency at 96MHz?

Usb-otg f2fs
I'm currently using the latest version of UBER-L kernel (01/01/15).
I have formatted my Micro USB to F2FS and would like to use it with my phone. TWRP recognises the USB and mounts it successfully, but the ROM (OptiPop) does not mount the USB. Both mount the USB fine when it is formatted to FAT32.
Is it possible for me to use F2FS using USB-OTG?
Thanks.
Edit: Got it working by using the 'Stickmount' app. ^_^

FloGatt said:
Hi,
is it advisable to disable filesystem trim in ubers cfg file while using f2fs?
Chet says, F2FS is auto-trimmed: https://plus.google.com/app/basic/stream/z13cxltwwqjcsx3ta22pyx5reobgudsiq04
Click to expand...
Click to collapse
I disabled trimming and I dont see a difference with f2fs. I would conclude that it isn't necessary with f2fs

Is there changelog of the new kernel version?

FloGatt said:
Is there changelog of the new kernel version?
Click to expand...
Click to collapse
Its all on github. The link is on the OP of the original thread. (The one with the download links)

GPU clock not going above 450MHz
Hey, I'm using this kernel (latest version as of now), on a clean flash of Optipop (also latest as of now - 11/01) with F2FS.
I set the max gpu clock to 650000000 in the uber_v1.3.cfg file in /etc
(also by terminal as in the 2nd post just to be sure) (echo "650000000" > the path and all)
Apps like System Monitor Lite and CPU-Z confirm that the max gpu clock is 650Mhz (Adreno 330 @ 650Mhz).
I have also set the performance governor (in the config file, and I tried via synapse + UKM 3.6.1 too) (I have set synapse not to apply settings on boot, so that should not be interfering with the init config of uber kernel until I set something in it.) I have no other kernel tweaking apps anyway.
However, the clock only goes up to 450MHz no matter what. It goes directly to 450 when touching the screen due to the performance governor, so I know settings are being applied.
However System Monitor, CPU-Z etc all show, current clock: 450MHz, Max Clock 650Mhz.
Even benchmarking with GFX bench gives results basically identical to the stock Nexus 5 with 450MHz, so there is no performance and FPS difference that should be there.
I searched the developer thread and found a few posts from many months ago that the gpu overclock was working properly for many people, with an appropriate improvement in FPS and benchmarks, with a couple of people also having my issue, that whatever of 650/533/450 max I apply, gpu doesn't go over 450MHz. However I couldn't find any solution.. it stopped working properly at some point between those builds when Chet introduced 533/650 and now?
I can't post in the dev thread (less than 10 posts).
This is reproducible, right after a clean boot, not a thermal issue (am not overclocking CPU, not running any CPU benchmarks, temp is less than 50C).
Hope someone can help. Thanks!

Installed Optipop back onto my N5 today. After a few hours of the phone being on the UI starts to act up then eventually needs a reboot to get back to being functional. I then flashed UberL kernel and now my screen is fuzzy and glitches out. Never had this problem in the past with Optipop or UberL. Please don't ask if I dirty flashed or deleted the android folder. I completely wipe my phone before I install a new ROM. I have been installing ROMs for a good minute now and have never seen this before. I have tried at least 5 other rom/kernel combos.....none have the same affect as UberL and Optipop. Yes I've tried F2FS ONLY Permissive Only and EXT4/F2FS Permissive and Enforcing with no luck.

Has the issue with the missing charging icon when the phone is turned off and plugged in reappeared? I have System, Data, and Cache formatted as F2FS and flashed F2FS-ONLY-Lollipop-Kernel-Cl3Kener-Kexec-Permissive.zip before flashing UBER, but I am still having this issue. Everything else appears to be running smoothly.

Is there anyway to know if I isntalled corectly this kernel ? I changed a setting in the cfg file and it seem to not change anything. For exemple,
10.2 : Double tap to wake
# -Double tap on screen to wake up the device.
# - option are:
# 0 - Diable
# 1- BOTTOM hald of screen
# 2- Full screen
DT2W=2
When i tried to doubletap the screen, nothing happened.
When i installed the kernel, i didn't cleared the cache and the ????? but it might be working Anyway. is there a way to know if its working ?
After a benchmarks i think that the kernel isn't realy doing someting. i added +50 in 3.CPU SETTINGS OVERVOLT... isn't realy doing someting.

sirarduin said:
Is there anyway to know if I isntalled corectly this kernel ? I changed a setting in the cfg file and it seem to not change anything. For exemple,
10.2 : Double tap to wake
# -Double tap on screen to wake up the device.
# - option are:
# 0 - Diable
# 1- BOTTOM hald of screen
# 2- Full screen
DT2W=2
When i tried to doubletap the screen, nothing happened.
When i installed the kernel, i didn't cleared the cache and the ????? but it might be working Anyway. is there a way to know if its working ?
After a benchmarks i think that the kernel isn't realy doing someting. i added +50 in 3.CPU SETTINGS OVERVOLT... isn't realy doing someting.
Click to expand...
Click to collapse
Confirmed. I have the same problem. Nothing in the uber.cfg file works. Its as if it wasn't even there.

JayR_L said:
Confirmed. I have the same problem. Nothing in the uber.cfg file works. Its as if it wasn't even there.
Click to expand...
Click to collapse
Format rom and then delete cache + tmp\mksh. Make sure to have a fresh ROM folder. Reinstall OptiPoP.ZIP, then flash the kernel before even boot. Now u can boot. install GA APP. Some time reinstalling work. Am lcuky...
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions

sirarduin said:
Format rom and then delete cache + tmp\mksh. Make sure to have a fresh ROM folder. Reinstall OptiPoP.ZIP, then flash the kernel before even boot. Now u can boot. install GA APP. Some time reinstalling work. Am lcuky...
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions
Click to expand...
Click to collapse
So you are saying that fixes the issue with the cfg file?

JayR_L said:
So you are saying that fixes the issue with the cfg file?
Click to expand...
Click to collapse
After 2 Benchmarks, i can say that doing this fixed MY problem. Uber/sabermod is now working realy well for the performance. Uses AnTuTU to check if its working. It upgraded a lot the performance for me.

Which governor gives me more performance?

[email protected] said:
Which governor gives me more performance?
Click to expand...
Click to collapse
performance ?! but it will drain your batterie a lot.

Lollipop improvements for HOXL

Hey guys and gals.
So I got myself a new/old HOXL and immediately flashed a Candy5 ROM on it with all lollipop and CM12 bells and whistles. To keep things even more interesting, I threw a nice package of google apps on top of it and enabled Google Now.
Guess what I found out immediately after my phone booted
My phone was sloooooooow. Like, it was fast for 1 hour or so after reboot and then it started to drag. After a day of moderate usage it became barely usable; sometimes I would miss a phone call because it wouldn't show me the bloody dialer and let me answer.
My phone was sucking battery like a thirsty camel in an oasis in the middle of Sahara desert... ok, ok, just don't throw that tomato at me. Anyway, I was losing 10-15% of my battery per hour.
So, I started messing around with the phone and found out several interesting things. I think it's worth sharing and discussing. In the next posts, I will share my findings with you. Please share yours.
My goal is pretty obvious: fast, smooth experience on CM12 and decent battery life. I was getting 2 full days of moderate usage on my good ol' HD2, so that's my current target with HOX. I also want Google Now working, at least to some extent. I especially like the feature when it shows me my parking location and things around me, so disabling locations altogether is not an option.

First step to smoothness: swap and OOM
DISCLAMER. The script below plays with your system settings. It might cause bootloops, brick your device or start nuclear war. Please use at your own risk.
So, first thing I noticed was that the phone was getting slow because it didn't have enough memory to run. I figure that CM12 and lollipop in general is probably optimized for 2GB RAM, whereas our device has only 1GB. So I tried to play with OOM values, but didn't get the desired results. So I went and enabled swap. Guess what? Works like a charm.
Here's how I did it:
1. install SuperSU from here .
2. open it and let it install its su module. this part might be tricky; for me, doing this via recovery didn't work and regular install didn't work either. i ended up having to open ADB terminal and setting SELinux to permissive manually, like so:
su
setenforce 0
and only after that did it succeed to push its su module to system/xbin.
3. go to SuperSU's settings and make sure you have checked the following:
a. Enable Superuser
b. Enable su during boot
c. Trust system user (this is not mandatory; however, if you don't check this, you will be flooded with requests to grant su to system apps)
4. after you have everything set up, reboot to recovery and install the attached zip like you would install a ROM.
5. reboot and enjoy your new silky smooth HOX
This script enables swap on data and cache. The files are pretty large, too: 250MB on data and 250MB on cache. I saw that even with this I still have plenty of room on data and cache to keep rolling. This gives me 0.5GB of swap, virtually enlarging my RAM to 1.5GB. This seems to be enough for all my needs.
The script also sets swappiness to 50, sets OOM to the values that work best for me at the moment and brings over several optimizations from my HD2 ROM. Feel free to edit the values and share.
EDIT: uninstalling script attached
EDIT2: scripts updated to reflect my latest changes.
EDIT3: reduced small (small_swap.zip) attached for those who want to use swap with ZRAM
Second step to smoothness: kernel
This step proved to be extremely important for smoothness. For some reason, stock CM12 kernel appears to be severely underoptimized... or the kernels that our devs generously made available for us are heavily overoptimized
To my best knowledge, currently there are only two kernels that work with LP and support swap: Torched Kernel v1.4 and Frosted Kernel.
IMPORTANT: if you are going to flash Torched kernel, be sure to flash LP version 1.3 or 1.4. Previous versions break swap, thus hurting speed and stability
IMPORTANT: if you are going to flash Bricked kernel, you ABSOLUTELY MUST flash the voltage table (see this post). First flash the kernel and then the voltage table. Not following this procedure can damage your phone.
I am currently using the Bricked kernel and the results are extremely impressive.
Third step to smoothness: Ext4 optimizations: disable journaling, enable dir_index
This step helps quite a bit if you decide to stay with ext4 for now. But even if you don't and want to switch to F2FS (see step 4), it's worth doing it on the /system partition.
WARNING. Journaling slows your system down quite a bit but it also adds stability. Please beware. You may lose your data or may even have to reflash your ROM in some extreme cases.
I never experienced any problems with non-journaling systems, but be aware that google enabled it for a reason.
Note: Your system might became unstable only if you forcefully shut the device down by long-pressing the power button or if you run out of battery. In case of normal work and normal shutdowns/restarts, everything will be fine.
1. Flash the attached zip (no_journal.zip).
2. Profit! Your cache, data and system partitions have no journaling now.
Fourth step to smoothness: F2FS
It took me some time to figure out this one, but it proved to be extremely helpful in terms of speed and general smoothness. Stability is yet to be tested, but I have it for ~24 hours now, and everything looks fine so far.
0. You need a F2FS-enabled TWRP. Luckily, we have jrior001 with us, who took care for that. Grab it from here (please thank jrior001 in his thread).
1. Install Torched kernel 1.4. (Bricked supports F2FS too, but for some reason, the performance is degraded and the stability is much worse than with Torched).
1a. If you had Bricked installed, remove undervolt script from /system/etc/init.d
2. Install attached zip (evita_F2FS_conversion_v2.0_pav.zip). This will enable you to work either with ext4 (with some extra optimizations) or with F2FS, so you can always go back without having to remove it. (note that you'll have to flash this zip each time you install a new kernel)
3. In TWRP, go to Backup, select data and cache and unselect system. I also disabled compression, just in case. Start the backup and wait for it to finish.
3a. STOP! Check that backup returned no errors. If there were errors during the backup, don't go any further or you'll lose your data!
4. Now connect your device to the PC. On PC, browse to Computer\One X\Internal Storage\TWRP\BACKUPS\<number of your device>\<latest backup>
5. You will see a bunch of files whose name contains ext4. For example, data.ext4.win.md5
6. Go ahead and change ext4 to f2fs for each file. The names should now look as follows: data.f2fs.win.md5
7. Back in TWRP, choose Restore -> your latest backup.
8. Sit back and relax while TWRP reformats your data and cache partitions as F2FS and restores all your data.
9. Reboot and enjoy!
10. If you'll ever want to go back to ext4, just go to TWRP, connect your device to the PC, on your PC, restore the original names of the backup files (rename f2fs to ext4), in TWRP choose restore and you're back to where you stated

First step to battery life: wakelocks
1. Go to Settings -> Privacy -> Privacy guard.
2. Scroll down till you reach the word Google.
3. Enable privacy for everything that starts with the word Google, including (!!!) Google Play Services.
4. Long-tap to enter each row and disable "keep awake" and "wake up" wherever applicable
Also, I use ServiceDisabler (from Play Store) to enter Google Play Services and disable Google Analytics
Second step to battery life: WIFI
Settings -> WI-FI -> three dots on top of the screen -> Advanced.
Disable "Keep WIFI on during sleep" (set to never) and "Scanning always available"
Third step to battery life: build.prop
Attached is my modified build.prop. It is derived from the stock build.prop, with some important tweaks that I brought over from my HD2 ROM. The measurements here are not that objective, but I felt that I could squeeze ~30% more juice from a single charge.
Of course, uninstall script is attached as well, just in case.
Fourth step to battery life: data usage
1. Head to Settings -> Data usage.
2. Scroll down till you see Google App.
3. Click on it and enable "Restrict app background data".
4. Go back and scroll further down till you find cLock.
5. Enable "Restrict app background data" as well.

for me

another one for me

last one for me

Cannot end a call by pressing the red button.. After unswap everything is normal again.. Can you please check it?
Nice work!!!!

How did u unswap ?
My phone was kinda cool.... Until I flashed this, my phone lagged the more.
Nice work BTW.
I want to unswap please!

Flash unswap.zip.. But i just notice that despite unswapping problem still persists.. Maybe it.s a cm12 bug.. I dont know

flashing unswap.zip should remove any traces of what swap.zip has done. if the problem persists after you flashed unswap, then the problem is elsewhere

I downgraded firmware from 2.18 to 2.15 and now i can terminate the calls.. I also install your swap file in latest cm12 02.19 nightly and seems to work fine..

I flashed Candy 5 and noticed that even after installing Torched kernel and overclocking, optimizing, etc, my phone would slow to a crawl by the end of the day and it definitely wasnt a memory problem as I had plenty free. What I found was that randomly my IO settings reset to 128Kb read-ahead and the scheduler resets to ROW. Changing back manually to 512Kb and FIOPS and suddenly the performance is back to what it was. This has happened twice in two days and I'm not sure if this is a Torched/CM/Candy/or Lollipop bug but at least I figured out what was causing it....

Hi thelonewolf_pav,
I just saw your post in the torched kernel lp thread. So if I have torched kernel lp flashed, the swap doesn't work? I flashed swap.zip and then flashed torched kernel lp, and my evita seems to be running without lag, for now. I hope torched can figure out what the problem is. Also, if I use fiops for my I/O scheduler and 512 Kb read ahead cache size, it helps. One more thing, how do I check if my swap portions are being used, I just want to see if mine are being used or not.
Thank You,

Hi harpin,
harpin14789 said:
I just saw your post in the torched kernel lp thread. So if I have torched kernel lp flashed, the swap doesn't work?
Click to expand...
Click to collapse
nope. it starts alright, but it's never actually used
harpin14789 said:
I flashed swap.zip and then flashed torched kernel lp, and my evita seems to be running without lag, for now.
Click to expand...
Click to collapse
that's cool
unfortunately, that wasn't the case for me, I had to return to the stock kernel. my evita would run without lags for a day or two and then slow down to a crawl. very annoying
harpin14789 said:
Also, if I use fiops for my I/O scheduler and 512 Kb read ahead cache size, it helps.
Click to expand...
Click to collapse
fiops should be great. too bad we don't have it in stock kernel. however, in my experience, the lower read ahead cache is, the better. try experimenting with it. i ended up setting it to 0.
harpin14789 said:
One more thing, how do I check if my swap portions are being used, I just want to see if mine are being used or not.
Click to expand...
Click to collapse
very simple. run terminal from the phone or start ADB. then type:
free
Click to expand...
Click to collapse
look at the last reported line (swap). it should say that you have about 1GB total and some amount of it in use. if you have all values (including "total") at zero, then swap wasn't initialized properly (or isn't supported by the kernel) and didn't kick in. if you have "used" at zero for a prolonged period then you, like me, experience the Torched bug: swap was started but kernel isn't actually swapping anything. if all values are greater than zero, that means that swap is working properly.
please report here what you get. it would be very nice to know whether Torched kernel worked for you

thelonewolf_pav said:
Hi harpin,
nope. it starts alright, but it's never actually used
that's cool
unfortunately, that wasn't the case for me, I had to return to the stock kernel. my evita would run without lags for a day or two and then slow down to a crawl. very annoying
fiops should be great. too bad we don't have it in stock kernel. however, in my experience, the lower read ahead cache is, the better. try experimenting with it. i ended up setting it to 0.
very simple. run terminal from the phone or start ADB. then type:
look at the last reported line (swap). it should say that you have about 1GB total and some amount of it in use. if you have all values (including "total") at zero, then swap wasn't initialized properly (or isn't supported by the kernel) and didn't kick in. if you have "used" at zero for a prolonged period then you, like me, experience the Torched bug: swap was started but kernel isn't actually swapping anything. if all values are greater than zero, that means that swap is working properly.
please report here what you get. it would be very nice to know whether Torched kernel worked for you
Click to expand...
Click to collapse
Hi thelonewolf_pav,
I really appreciate you telling me how to do this. I will get back as soon as I can with the results I am getting. Thanks for the swap.zip in the first place

harpin14789 said:
Hi thelonewolf_pav,
I really appreciate you telling me how to do this. I will get back as soon as I can with the results I am getting. Thanks for the swap.zip in the first place
Click to expand...
Click to collapse
hi thelonewolf_pav,
You were right, my phones is slowing down to a crawl even with swap enabled. I think, since I clean installed candy5 version 1.0.1, I got some good performance without much lag, but after some time the lag came back, I am torched kernal now. Should I switch back to stock kernal? To do that do I just fastboot flash boot boot.img from candy5 rom?

harpin14789 said:
hi thelonewolf_pav,
You were right, my phones is slowing down to a crawl even with swap enabled. I think, since I clean installed candy5 version 1.0.1, I got some good performance without much lag, but after some time the lag came back, I am torched kernal now. Should I switch back to stock kernal? To do that do I just fastboot flash boot boot.img from candy5 rom?
Click to expand...
Click to collapse
yes, just do fastboot flash boot boot.img
alas, you will lose all the bells and whistles of the Torched kernel. i really hope the dev will be able to solve the problem in Torched...

thelonewolf_pav said:
yes, just do fastboot flash boot boot.img
alas, you will lose all the bells and whistles of the Torched kernel. i really hope the dev will be able to solve the problem in Torched...
Click to expand...
Click to collapse
Hi thelonewolf_pav, if I flash the stock kernal do I need to reflash swap.zip? And what will losing the over clock to 1.7 GHz and GPU over clock to 512 MHz actually do to my device? As long as swap is enabled on stock kernal, my phone should run without any lag without the over clock, right? It is sad that I well lose fast charge, s2w and dt2w. But do we know what the root cause of this problem is, like in touched?
Thanks

harpin14789 said:
Hi thelonewolf_pav, if I flash the stock kernal do I need to reflash swap.zip? And what will losing the over clock to 1.7 GHz and GPU over clock to 512 MHz actually do to my device? As long as swap is enabled on stock kernal, my phone should run without any lag without the over clock, right? It is sad that I well lose fast charge, s2w and dt2w. But do we know what the root cause of this problem is, like in touched?
Thanks
Click to expand...
Click to collapse
Hey,
flashing the stock kernel should be enough. you don't have to reflash swap.
regarding your overclocked settings, they simply won't apply. the phone should boot normally, and you will be able to set the frequencies to the values that are allowed by the kernel.
regarding the root cause of the problem, unfortunately, we don't know it. kernel dev said that he will look into it. all i know is that swap starts perfectly well on Torched kernel, but the kernel never actually uses it. ("used" value is always at zero). which is equal to not having swap at all

thelonewolf_pav said:
Hey,
flashing the stock kernel should be enough. you don't have to reflash swap.
regarding your overclocked settings, they simply won't apply. the phone should boot normally, and you will be able to set the frequencies to the values that are allowed by the kernel.
regarding the root cause of the problem, unfortunately, we don't know it. kernel dev said that he will look into it. all i know is that swap starts perfectly well on Torched kernel, but the kernel never actually uses it. ("used" value is always at zero). which is equal to not having swap at all
Click to expand...
Click to collapse
ok, thanks

[DEPRECATED] Young Engine - The best balance of performance and battery life

Introduction
I tested a lot of mods, and I read a lot of scripting stuffs over time but the finding was always the same : A majority of mods contained only placebo things, and they only made things worse. I decided to make my own mod and Young Engine is what I got, I was septic to share it but sharing is caring after all ! Its particulairity is that every code line and every tested values inside suit our Galaxy Young.
Features
Compatible with all the ROMs (Stock and custom ROMs, CM7/CM9/CM11) and kernels.
Better memory management (calculated and based on Galaxy Young's RAM).
Better partitions mount options (compatible with both of EXT4 & RFS filesystems).
Better battery life.
Better call quality. That's placebo.
Better scrolling. That's placebo.
Better SDcard read/write speed.
I/O scheduler general and specific tunables for SIO and SIOPlus schedulers.
SmartassV2 governor tuning.
3G and TCP/IP optimisations (Download/upload speeds, network's latency reducing).
Useless debugging disable (for non-dev users).
Requirements
Rooted device with Busybox installed.
Init.d support.
Custom recovery.
Installation
Delete your installed scripts (expect which your kernel and/or your ROM need).
Download the attached ZIP file and put in inside your SDcard.
Reboot your phone in recovery mode.
Flash the ZIP file and reboot again your phone.

Credits
@FeraVolt : Your awesome work with FeraDroid gave a new life to my mod, thank you a bunch !
@osm0sis & Franco's Dev Team : For their great scripts which helped me a lot, the entropy part, and the TCP/IP optimisations are from them ! Thanks a lot guys.
@pkgnex : For his SIO and SIOPlus schedulers tunables, thank you for the great work !

Nice work Dude !! Keep it up !!!

First changelog - Thanks again @FeraVolt !
Added SmartassV2 governor tuning.
Removed the screen state scaling script.
Updated partitions mount options.
Updated debugging disable script.
Updated memory management, filesystem and entropy tunings.
Updated I/O scheduler tunables.

Cannot download ......please fix the download link.

Arkonite said:
Cannot download ......please fix the download link.
Click to expand...
Click to collapse
Sorry, it's now fixed !
Best regards.

Is this compatible with cm 7.2?

Arkonite said:
Is this compatible with cm 7.2?
Click to expand...
Click to collapse
Of course, it's compatible also with CM11/CM9 and stock ROM.
Best regards.

Second changelog - Thanks @raisul2010.5396 for some ideas :
Added calculated LMK's minfree/adj and Android's OOM flags (which are both synced with each other).
Added build.prop flags for several purposes :
Overall performance improvement.
Battery life improvement.
Better scrolling.
Call related improvements (Reduced proximity and ring delays, enabled Adaptive Multi-Rate Wideband for a better call quality, mobile data's speed increase).
Updated again memory management, filesystem and entropy tunings.
Updated again debugging disable script.
Please, I'm tired of the feedbacks lack. Try to understand my situation as I done all my possible for this mod's making.
Best regards.

I have a question: Is compatible with the Percy's ROM and kernel?

danielcuervog said:
I have a question: Is compatible with the Percy's ROM and kernel?
Click to expand...
Click to collapse
Yes, it is.
Best regards.

Nice.... New update is much stable and faster.

BlackGunZ said:
Second changelog - Thanks @raisul2010.5396 for some ideas :
Added calculated LMK's minfree/adj and Android's OOM flags (which are both synced with each other).
Added build.prop flags for several purposes :
Overall performance improvement.
Battery life improvement.
Better scrolling.
Call related improvements (Reduced proximity and ring delays, enabled Adaptive Multi-Rate Wideband for a better call quality, mobile data's speed increase).
Updated again memory management, filesystem and entropy tunings.
Updated again debugging disable script.
Please, I'm tired of the feedbacks lack. Try to understand my situation as I done all my possible for this mod's making.
Best regards.
Click to expand...
Click to collapse
Will test it soon, and add the link to your thread in tweaks section of my ports

good tweak for this lil device,maybe its cooler to have a cleaner in it too for clean junk files and other things like that on boot,when needed i can give u a lil help for this,keep it up.
--SIGNATURE--

Final changelog
Updated LMK's minfree/adj and Android's OOM flags (RAM management). Thanks a lot @ImbaWind !
Updated build.prop flags (Better UI and better performance).
Updated again memory management, kernel and entropy tunings (it does the same as the well-known Seeder scripts).
Updated partitions mount options.
You will be impressed guys (@raisul2010.5396 - @Arkonite - @-CALIBAN666-) !

i am using hyperion 9 beta and i flashed this zip file but it takes time much less than 5 seconds even u can say that it flashes the whole zip file in 2 seconds only. it means it didn't flashed on my rom correctly...or it is?

Aryanyadav9 said:
i am using hyperion 9 beta and i flashed this zip file but it takes time much less than 5 seconds even u can say that it flashes the whole zip file in 2 seconds only. it means it didn't flashed on my rom correctly...or it is?
Click to expand...
Click to collapse
The whole content of the mod is contained in the init.d script file, that's why the installation is very fast. Mount your /system partition, install the ZIP and check the log file after the reboot in the /data partition.
Edit : I did a very small update again to the ZIP package, I corrected a typo.
Best regards.

BlackGunZ said:
The whole content of the mod is contained in the init.d script file, that's why the installation is very fast. Mount your /system partition, install the ZIP and check the log file after the reboot in the /data partition.
Edit : I did a very small update again to the ZIP package, I corrected a typo.
Best regards.
Click to expand...
Click to collapse
ok i got it right now, Tysm