Related
Anybody know what file system the (untouched) Nexus S might be rocking? RFS?
no.........
demo23019 said:
no.........
Click to expand...
Click to collapse
Is that "no" as in "nobody knows," or is it "no" as in "it is not RFS"?
no its not sporting RFS
Its completely stock 2.3 samsung has no involvement in software
Aqua1ung said:
Is that "no" as in "nobody knows," or is it "no" as in "it is not RFS"?
Click to expand...
Click to collapse
A rep from Google already said, they are using ext4.
http://forum.xda-developers.com/showpost.php?p=9627089&postcount=49
If it's not RFS then I guess the dream of Gingerbread being easily ported to other Galaxy S phones is dead. At least I think that's the case.
Dougefresh91 said:
If it's not RFS then I guess the dream of Gingerbread being easily ported to other Galaxy S phones is dead. At least I think that's the case.
Click to expand...
Click to collapse
Why? We already have Voodoo, that does the same thing in Froyo. The way the Nexus S is set up in terms of filesystem is very similar to the way a Galaxy S running Voodoo is set up. There are some differences in how the partitions are set up and yaffs being used on /cache. But the overall differences very small, and minor changes in the init scripts on the ramdisk packed in the kernel will take care of all the mounting.
I have my Vibrant converted to ext4 with the Obsidian ROM, but that only changes a partition as far as I know, not the whole phones data. Not sure about VooDoo as it would never work on my device.
Some people have been speculating that it'd be easy to get a Nexus S ROM ported over since they're both on T-Mob. I was assuming that since the file systems are different that this isn't the case. Look at how much trouble they're having getting the Cyanogen Mod working on the Vibrant.
Believe me, I'd love it if it really is a simple process for devs, but I have a feeling that that's not going to be the case. Again, I'm just speculating, I'm no dev.
I don't think it will be that difficult, because file systems can be changed - indeed, there are already lagfix kernels for the Galaxy S which eliminate the use of RFS entirely. Provided the kernel has support for ext4, the partition can just be formatted that way and mounted appropriately.
I hope you're right. If so then there's no reason at all for me to trade in my Vibrant for the NS. Lord only knows when Samsung will get it's act together concerning updates, so I think this is my only hope of ever seeing Gingerbread on this phone.
rajendra82 said:
Why? We already have Voodoo, that does the same thing in Froyo. The way the Nexus S is set up in terms of filesystem is very similar to the way a Galaxy S running Voodoo is set up. There are some differences in how the partitions are set up and yaffs being used on /cache. But the overall differences very small, and minor changes in the init scripts on the ramdisk packed in the kernel will take care of all the mounting.
Click to expand...
Click to collapse
YAFFS/YAFFS2 and JFFS etc are flash file systems. Not file systems for operating systems. You still require ext/rfs/fat32 etc for the OS to work with. They mount on a yaffs/etc partition so ext/etc do not have to worry about the intricacies of flash.
Voodoo confused a lot of things for a lot of people.
SpeeDemon said:
YAFFS/YAFFS2 and JFFS etc are flash file systems. Not file systems for operating systems. You still require ext/rfs/fat32 etc for the OS to work with. They mount on a yaffs/etc partition so ext/etc do not have to worry about the intricacies of flash.
Voodoo confused a lot of things for a lot of people.
Click to expand...
Click to collapse
Not to offend you, but you only have little knowledge, and that is a dangerous thing. There is no such distinction as file system for operating system versus flash file system. Linux kernel supports a variety of file systems. Some file systems are optimized and written specifically for flash media (e.g., YAFFS2), some are written for hard drives but could work on flash media too (e.g., fat32, ext4, jfs), some are only suitable for disk based media. The operating system partition can be mounted on any partition with a file system that the kernel recognizes. Ext2/Ext3/Ext4 have been the native file systems of Linux, but there have been a lot of machines with no use of any of them. It is up to the root user to choose what the file system of any partition is. The init script in the ramdisk packed with kernel calls the commands to mount the file systems. All Voodoo lag fix did was to convert some of the partitions mounted as RFS out of the box to ext4, and then allowed them to be mounted natively at boot time. The end result is nearly the same approach being taken by Google in the Nexus S out of the box. One of the differences in how the Nexus S or a Galaxy S running the latest Voodoo is set up is the /cache partition, which is set up as ext4 by default on Voodoo+ Galaxy S, and yaffs2 on the Nexus S. Both partitions are on flash media, but since the chip used in Galaxy S does wear leveling in the firmware, we can't use yaffs2 on /cache. Voodoo might have confused some people, but it sounds like you were confused well before that came out.
rajendra82 said:
Not to offend you, but you only have little knowledge, and that is a dangerous thing. There is no such distinction as file system for operating system versus flash file system. Linux kernel supports a variety of file systems. Some file systems are optimized and written specifically for flash media (e.g., YAFFS2), some are written for hard drives but could work on flash media too (e.g., fat32, ext4, jfs), some are only suitable for disk based media. The operating system partition can be mounted on any partition with a file system that the kernel recognizes. Ext2/Ext3/Ext4 have been the native file systems of Linux, but there have been a lot of machines with no use of any of them. It is up to the root user to choose what the file system of any partition is. The init script in the ramdisk packed with kernel calls the commands to mount the file systems. All Voodoo lag fix did was to convert some of the partitions mounted as RFS out of the box to ext4, and then allowed them to be mounted natively at boot time. The end result is nearly the same approach being taken by Google in the Nexus S out of the box. One of the differences in how the Nexus S or a Galaxy S running the latest Voodoo is set up is the /cache partition, which is set up as ext4 by default on Voodoo+ Galaxy S, and yaffs2 on the Nexus S. Both partitions are on flash media, but since the chip used in Galaxy S does wear leveling in the firmware, we can't use yaffs2 on /cache. Voodoo might have confused some people, but it sounds like you were confused well before that came out.
Click to expand...
Click to collapse
Except that ext4 support didn't exist in the .29 kernel used in Android 2.1 - you seem to think it magically just works, because it works.
SpeeDemon said:
Except that ext4 support didn't exist in the .29 kernel used in Android 2.1 - you seem to think it magically just works, because it works.
Click to expand...
Click to collapse
I know that supercurio patched in native ext4 support in Eclair, and it didn't just magically appear. The Froyo kernels do support ext4 natively though, so a simple script injection enables Voodoo. Since Gingerbread kernels from Google will also suport it (as Nexus S will actually use it), why can't another script injection work again to enable a Gingerbread kernel to work with Galaxy S.
Am I right in thinking that supercurio is a dev?
bedalus said:
Am I right in thinking that supercurio is a dev?
Click to expand...
Click to collapse
You do know this thread is more than a couple of months old, right?
Anyway, to answer your question: yes, supercurio is a dev.
Sent from my Nexus S using Tapatalk
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
Is it actually possible to use fuse to mount my external SD card when it is formatted with ext4 when on a TW ROM on my VZW GS3?
From reading, it seems like it should be possible, but nothing I have tried has worked. Seems like CM/ASOP does it automatically but when trying to duplicate it on TW, I've hit a wall.
I've read that you need a custom kernel to do it, but not sure which kernels support it as I'm not sure what needs added in order to support this. Is it some module that needs compiled in or just support for inet.d? Since even stock supports ext4, I'm guessing inet.d is all that's needed, meaning the stock kernel with inet.d support added should work, but I'm willing to use other kernels. (Tried lean, Zeus, and a couple others I can't think of off the top of my head but had no luck.)
If someone can direct me to a howto or give instructions that work for the GS3 on TW, I'd appreciate it. The ones I've been able to find via search, I've not had any luck getting to work. If using fuse won't work, but directly mounting it does, that would work for me as well as my Windows machines are able to read ext file systems. Fuse would be more convenient for plugging into other PCs though. (Maybe I'll install the ext drivers on all the computers in the district as part of the summer updates...)
--
Tapatalked from my VZW Galaxy S III.
Bumping this in hopes that someone knows the answer and just didn't notice the post.
Stock kernel and Anthrax kernel are the only two I know that support ext4 on TW. Anthrax is invite only currently. So that leaves stock pretty much.
countryfolk07 said:
Stock kernel and Anthrax kernel are the only two I know that support ext4 on TW. Anthrax is invite only currently. So that leaves stock pretty much.
Click to expand...
Click to collapse
You wouldn't happen to know how to get it to recognize my ext4 SD card would you? I've yet to be able to get it to mount. I'll flash stock back on and give it another try.
--
Tapatalked from my VZW Galaxy S III.
countryfolk07 said:
Stock kernel and Anthrax kernel are the only two I know that support ext4 on TW. Anthrax is invite only currently. So that leaves stock pretty much.
Click to expand...
Click to collapse
You sure stock kernel supports ext4?
Hi,
I want to optimize my K1 tablet, however I don't wish you use a custom rom, I prefer to use the stock one...
(I have a pad and a stylus that I wish to use).
So I Installed TWRP and then flashed the (zipaligned) Optimized Stock rom
http://forum.xda-developers.com/shi...rom-optimized-stock-shield-tablet-k1-t3437791
I then flashed this F2FS Kernel
http://forum.xda-developers.com/shi.../tweaked-kernel-nvidia-shield-tablet-t3069776
I then converted the cache and data partitions to F2FS (I had to restore the data partition after converting & wiping).
I'm going to install Xposed next....,
What other tweaks should I be doing?
I find that things like governors, etc vary from tablet to tablet. So any recommendations for that? ( I haven't read through the kernel thread yet, and will probably find some tweaks there...).
Thanks
This kernel was built originally only for private use, but some of you have asked for it so I've decide to share.
I'm not responsible: You use at your own risk.
This kernel is based on latest LineageOS source code, with only a few tweaks in config file and maybe any external commit. It's more a "proof of concept" than a development by itself. My philosofy is "keep it simple"... I don't look for a "overloaded super-kernel with steroids"... if you want many features (exotic governors, OC, etc...) and "bleeding edge" functionalities there are some good alternatives made by good devs here so this kernel is not for you. Maybe other kernels can benefit by this approach in the future.
The approach for BitO-K is a light and stable kernel optimized via some basic params in kernel config and built with latest Toolchain (TC) to get a very optimized code for our device's architecture.
Fronts attacked: Task scheduling (SMT enabled), task efficiency (CleanCache/FrontSwap and other minor tweaks) and IO optimization (the only commit you can see ATM in my source branch) and, depending on version, latest Toolchains from Linaro or UBER. ATM no more "magic"...
*In my personal device I'm also testing with /data and /cache partitions on F2FS instead of EXT4 (this also helps...). Maybe new thread in the future about this...
Download
You can get latest version here.
Installation
Make backup
Install via TWRP
Wipe Dalvik/Cache
Reboot and profit
Notes
You can disable thermal control bins from xiaomi to avoid some lag if you get your CPU hot... Revise your config to be sure you don't get a brick...
You can install on any ROM, but if MIUI based, then you can get some features not to work, like WIFI, etc... If you want to test on MIUI, you have info here, thx to @Hen Ry
How to delete thermal control binaries by Xiaomi
You need root permissions (I suggest Magisk 13.6+)
Go to /vendor/bin
Delete (I suggest to move to a backup folder into /vendor/bin or rename files, not delete):
perfd
thermal-engine
Additonally you can delete (or move/rename to *.bak) file:
/etc/thermal-engine-8996.conf
My Kernel Settings (Kernel Adiutor)
Not necessary the best ones, only the ones I usually set (battery/performance balanced, smooth behaviour, almost total lag free):
CPU BIG MAX: 1900 MHz
CPU LITTLE MAX: 1440 MHz
GPU MX: 560 MHz
Governor: Interactive
Other minor tweaks (sometimes I set them):
IO: Disabled statistics
...
Source Code
https://github.com/BitOBSessiOn/android_kernel_xiaomi_msm8996
How to convert FS's from EXT4 to F2FS (IO performance improvement)
Be prepared to break it all... Again: at your own risk
Your TWRP must support F2FS (look for my latest TWRP-MROM )
Your kernel (on primary or secondary) must support F2FS (usual if LineageOS based)
Your system (on primary or secondary) must support F2FS mounting (fstab.qcom file updated with F2FS entries for /cache and /data ) (usual if LineageOS based)
Make a backup of ALL your data you want to keep (/data partition via TWRP backup + DCIM, WhatsApp folder, etc... ) (I suggest copying/backup via USB from TWRP)
In TWRP go to: Wipe / Advanced Wipe / Change or repair file system / Change file system for /cache and /data and select F2FS
Restore your /data partition from TWRP backup and manually copy your extra folders (DCIM, Whatsapp, etc...)
Reboot and profit
Testing! :highfive:
Behaving awesomely both on RR and AICP, the two roms I've tested it so far with some minor kernel auditor tweaks.
Thanks dev!!!
Awesome with @marchetto96 ViperOS!!
Testing with LOS. So far so good. Thanks Dev
albertoduqe said:
Behaving awesomely both on RR and AICP, the two roms I've tested it so far with some minor kernel auditor tweaks.
Thanks dev!!!
Click to expand...
Click to collapse
Hello Mate. May I please ask if you can share the tweaks / config in Kernal Audiutor ?
It's all placebo or its doing its job very well and very quietly. Either way, its not breaking anything or making anything worse, so bravo.
VerucaSalt said:
Hello Mate. May I please ask if you can share the tweaks / config in Kernal Audiutor ?
Click to expand...
Click to collapse
Governors to interactive. CPU max to 1900 and 1440, GPU max to 560. Thermal bins deleted.
It's not my idea though, I just learnt and copied from the boss
Happy tweaking!
Sent from my MIX using Tapatalk
albertoduqe said:
Governors to interactive. CPU max to 1900 and 1440, GPU max to 560. Thermal bins deleted.
It's not my idea though, I just learnt and copied from the boss
Happy tweaking!
Sent from my MIX using Tapatalk
Click to expand...
Click to collapse
How to delete thermal bin?
rhong said:
How to delete thermal bin?
Click to expand...
Click to collapse
OP updated with little howto.
How to jump from EXT4 to F2FS
Second post updated with a little guide: How to convert FS's from EXT4 to F2FS (IO performance improvement)
BitOBSessiOn said:
Second post updated with a little guide: How to convert FS's from EXT4 to F2FS (IO performance improvement)
Click to expand...
Click to collapse
Cheers. I'm going to try this F2FS mod out but it's going to take forever just to copy everything off my phone (256GB model, almost full). If I switch data to F2FS will it kill the encryption (I don't want it to be encrypted anyway)? If not, I may as well get rid of it now when all my personal files are backed up to my PC.
gavin19 said:
Cheers. I'm going to try this F2FS mod out but it's going to take forever just to copy everything off my phone (256GB model, almost full). If I switch data to F2FS will it kill the encryption (I don't want it to be encrypted anyway)? If not, I may as well get rid of it now when all my personal files are backed up to my PC.
Click to expand...
Click to collapse
Ummhhh.. I always assume an unencrypted scenario... but indeed you lose encryption when reformatting to another FS, you must re-encrypt after formatting (target FS must be encryptable).
BitOBSessiOn said:
Ummhhh.. I always assume an unencrypted scenario... but indeed you lose encryption when reformatting to another FS, you must re-encrypt after formatting (target FS must be encryptable).
Click to expand...
Click to collapse
I copied everything off, took a backup of data in TWRP and copied it to the PC too. Wiped data/cache, changed both to F2FS and rebooted into recovery. Copied the data backup back to the phone and restored (gave a warning about it being from an EXT4 source but it restored ok). Rebooted into Resurrection Remix and in the settings it still says it's encrypted. To get it decrypted I had to use the 'Format Data' option in TWRP (as opposed to ticking data and wiping it).
Between the new kernel, some tweaks in EX Kernel Manager (mainly ondemand governor for CPU and performance for GPU), and decryption, I'm getting the highest Antutu scores I have for months. Just got 156k (60477/53925/31252/10475). Now I just have to wait while it copies 200GB+ of stuff back to the device.
gavin19 said:
I copied everything off, took a backup of data in TWRP and copied it to the PC too. Wiped data/cache, changed both to F2FS and rebooted into recovery. Copied the data backup back to the phone and restored (gave a warning about it being from an EXT4 source but it restored ok). Rebooted into Resurrection Remix and in the settings it still says it's encrypted. To get it decrypted I had to use the 'Format Data' option in TWRP (as opposed to ticking data and wiping it).
Between the new kernel, some tweaks in EX Kernel Manager (mainly ondemand governor for CPU and performance for GPU), and decryption, I'm getting the highest Antutu scores I have for months. Just got 156k (60477/53925/31252/10475). Now I just have to wait while it copies 200GB+ of stuff back to the device.
Click to expand...
Click to collapse
Battery? Stability? Smoothness...? Thx for feedback
BitOBSessiOn said:
Battery? Stability? Smoothness...? Thx for feedback
Click to expand...
Click to collapse
I always found ondemand to give the smoothest experience and that's exactly what I'm getting here. It feels like being back on MIUI (that's a good thing).
I can't give any input battery-wise as I'm rarely away from a charger and don't care about battery life (within reason obviously), so I never monitor it.
As for stability, I did temporarily lose WiFi connectivity (other network devices were fine), and when that dropped out I lost mobile data too. This happened when I was transferring the last batch of files I forgot to restore via USB. I've been using RR for weeks and it has never happened before, but it could just be a one-off. It took a reboot to resolve.
I have noticed the device can get very warm when transferring a large number of files over WiFi. It has always been like that regardless of kernel. I had the case on when I lost connectivity so I couldn't feel if it was that warm, but maybe that sustained high temp buggered the WiFi. If it happens again I'll let you know.
I should note that I had the thermal files removed (I've always deleted them from I first got the device). I also usually run the OC'd DragonXia kernel so my device is no stranger to a little extra heat.
I'm using it for a day now. so far so good. Latest Mokke rom, working flawlessly. using ondemand governor with stock clocks, CFQ and I/O Scheduler with 2Mb read ahead value.
only odd thing I have noticed so far is that WiFi signal seems to be a bit weaker. In places that I had connectivity before, now I'm not in range.
Otherwise all good! Keep up the good work, and thanks man!
BitOBSessiOn said:
How to convert FS's from EXT4 to F2FS (IO performance improvement) (-- WIP --)
Be prepared to break it all... Again: at your own risk
Your TWRP must support F2FS (look for my latest TWRP-MROM ) -- perhaps 4/128GB pending, WIP --
Your kernel (on primary or secondary) must support F2FS (usual if LineageOS based)
Your system (on primary or secondary) must support F2FS mounting (fstab.qcom file updated with F2FS entries for /cache and /data ) (usual if LineageOS based)
Make a backup of ALL your data you want to keep (/data partition via TWRP backup + DCIM, WhatsApp folder, etc... ) (I suggest copying/backup via USB from TWRP)
In TWRP go to: Wipe / Advanced Wipe / Format Partition and select /cache and /data and format to F2FS
Restore your /data partition from TWRP backup and manually copy your extra folders (DCIM, Whatsapp, etc...)
Reboot and profit
Click to expand...
Click to collapse
my rom is aicp,after converted，i can not mount the data,but the speed is really fast
315602494 said:
my rom is aicp,after converted，i can not mount the data,but the speed is really fast
Click to expand...
Click to collapse
Weird... seems that AICP does not include F2FS entries in fstab.qcom file...
If I have time I will try to make a zip to inject updated fstab.