Related
Oh,,, hell yeah, i want it badly. :victory:
+1
No. No sources are released, and you'll have to find someone to port it when the sources are released in the fall.
SGWUser said:
No. No sources are released, and you'll have to find someone to port it when the sources are released in the fall.
Click to expand...
Click to collapse
Maybe sir arco will save us again when the sources are released You never know..
a port may come soon but we have to wait until it is final so they release cm 12
eri000 said:
a port may come soon but we have to wait until it is final so they release cm 12
Click to expand...
Click to collapse
That isn't necessarily true, for example CM 10.1 released by arco still in beta4 version
dqsnunes said:
That isn't necessarily true, for example CM 10.1 released by arco still in beta4 version
Click to expand...
Click to collapse
the CM team announced that there will be NO CM version until the google releases the final image of android L on AOSP.This doesn't mean we will have a final stable version of cm immediately BUT we will only see a cm12 build when final android L gets merged into aosp.
^That is for other phones that get CM OFFICIAL.For ancora we have to wait a little bit more for unofficial cm, which is based on official cm.So no official--- no unofficial (arco if he has time to mess with it,or others)
BTW, Android L is currently being ported to the Nexus 4 and Nexus 7 2012 right now. Both are almost functional.
I think even if we were to have Android L here, i don't think it will be responsive. Google said, Animation transitions run at 60fps, Im not sure if overall perfomance can run at the same fps because i bet our processor is not powerful enuff or smth. CMIIW.
Android L Port For Nexus 4
Newest Android L Port For Nexus 4 Is Now Fully Operational And Ready For Download
INFO
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
theloneseeker said:
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
Click to expand...
Click to collapse
A swap partition for art can't help?
theloneseeker said:
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
Click to expand...
Click to collapse
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
sir mordred said:
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
Click to expand...
Click to collapse
Nice thinking and good luck :good:
sir mordred said:
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
Click to expand...
Click to collapse
Umm very interesting if you want some testers,i'm here.
If you have cm11 theme chooser:
http://forum.xda-developers.com/android/themes/theme-l-ready-t2802979
https://play.google.com/store/apps/details?id=nexbit.icons.moonshine
Settings>Performance>Force high-end graphics>check
AND YOU HAVE L IN YOUR WONDER(I LOVE MY WONDER)
what is android L? can someone tell me about it please?
smartiescoke said:
what is android L? can someone tell me about it please?
Click to expand...
Click to collapse
The upcoming Android version. About it...there are many things to say. You could search YouTube for "Google I/O 2014". There are a lot of new things about it. If you've got time to spend and curiosity, it might be very interesting to watch. This way, you will also answer your own question (and more).
arsradu said:
The upcoming Android version. About it...there are many things to say. You could search YouTube for "Google I/O 2014". There are a lot of new things about it. If you've got time to spend and curiosity, it might be very interesting to watch. This way, you will also answer your own question (and more).
Click to expand...
Click to collapse
whoa! really? awesome! i always been waiting google to update different kind of android version. ui and etc, hope it will come to our wonder soon! XD
oh man i love android L ui and statusbar. Hoping our Great Developer can bring this to our Wonder.
#sorry for my bad english.
is there any f2fs kernel working or how to solve error on zwliew f2fs kernel?
i recently flash f2fs kernel zwliew made but got an error cannot find /cache/log
i use cm11 4.4 rom and beanstalk 4.3 rom and get the same error.
http://forum.xda-developers.com/showpost.php?p=53644714&postcount=1
Maybe Chrono kernel?
[email protected] said:
http://forum.xda-developers.com/showpost.php?p=53644714&postcount=1
Maybe Chrono kernel?
Click to expand...
Click to collapse
yes, but chrono required zwliew kernel to as it need to format /cache and /data to f2fs not ext4
http://forum.xda-developers.com/showpost.php?p=53644768&postcount=3
either way zwliew f2fs makes error cannot find /cache/log and failed format /cache
as chrono f2fs without zwliew f2fs stuck at boot animation logo
kalivos said:
yes, but chrono required zwliew kernel to as it need to format /cache and /data to f2fs not ext4
http://forum.xda-developers.com/showpost.php?p=53644768&postcount=3
Click to expand...
Click to collapse
No - thats not true (anymore) - just use an ChroneKernel for F2FS and your ROM Version (R1.3 is good) and procede with the install instructions.
Keep in mind that you need at least 120-130 MB for cache partition for F2FS...
@ChronoMonochrome: Maybe you could correct this outdated instruction and write that your Kernel is OK as well to do the installation...
fluffi444 said:
Keep in mind that you need at least 120-130 MB for cache partition for F2FS...
Click to expand...
Click to collapse
ic... i missed that cache partition requirement :cyclops:
Remixed Kernel
/only for KitKat/
Remember i am not an developer, this is just my personal builded kernel for my own needs.
Also i am not responsible if your device bricked or else, i give my best and test every build that bad things don't will happen.
If you want to support my work, you can do it here
Changelog remixed.kernel-sr1
- GPU OC up to 512 Mhz
- Fixed OC up to 1,6 Ghz
- Revert few commits for performance reason
DOWNLOAD KERNEL HERE
Sources proper the GPL
Last but not least, my biggest thanks and with them credits goes to:
@Ziyan, @MWisBest, @pattyboi:), @franciscofranco, @boype, @bsmitty83, @osm0sis, @Christopher83 and all other i have forgotten :good:
Reserved for future...
So you decided to share it. Thank you
Nice. Got the sources listed anywhere? I want to create my own personal SuperRAM version. (Plus...that GPL stuff ya know )
redj12 said:
So you decided to share it. Thank you
Click to expand...
Click to collapse
Yes, its ready and as i think good to go but this will show the time.
Culex316 said:
Nice. Got the sources listed anywhere? I want to create my own personal SuperRAM version. (Plus...that GPL stuff ya know )
Click to expand...
Click to collapse
Github can be found in my profil...
I flashed this kernel on omni ROM and it works very well, my phone works smoothly
f2fs support?
It has same features as franco kernel so if francos has it, this also has it
Testing!!! thanks for keeping the scene alive. I'll back with comments.
Edit: not working for me. It doesn't pass boot animation. Vanir ROM with /data and /cache in F2FS.
Wiped cache and dalvik and neither works.
sergialess said:
Testing!!! thanks for keeping the scene alive. I'll back with comments.
Edit: not working for me. It doesn't pass boot animation. Vanir ROM with /data and /cache in F2FS.
Wiped cache and dalvik and neither works.
Click to expand...
Click to collapse
franco doesn't support F2FS because F2FS is bullsh*t.
qtoo941 said:
franco doesn't support F2FS because F2FS is bullsh*t.
Click to expand...
Click to collapse
Strange... I'm pretty sure I've read that it was supporting F2FS. Anyway... I won't argue if F2FS is good or bad. I've been using it since BSmitty featured it first time in the GNex, and I'm satisfied. So... back to my beloved Fancy, which supports F2FS without inconvenience.
qtoo941 said:
franco doesn't support F2FS because F2FS is bullsh*t.
Click to expand...
Click to collapse
how is f2fs bullsh*t.
pattyboi:) said:
how is f2fs bullsh*t.
Click to expand...
Click to collapse
f2fs is just experimental. tried it and actually .. it is not as stable as ext4. the whole story about f2f's performance over ext4's performance is just placebo effect. tried it on galaxy nexus and also on s4.. both models without any real benefit from f2fs system. EXT4 is just better and most stable. that's it.
Don't really know much about f2fs because i never used it...
But if you want it, i can add it into the kernel then you can take your decision what you want use
qtoo941 said:
f2fs is just experimental. tried it and actually .. it is not as stable as ext4. the whole story about f2f's performance over ext4's performance is just placebo effect. tried it on galaxy nexus and also on s4.. both models without any real benefit from f2fs system. EXT4 is just better and most stable. that's it.
Click to expand...
Click to collapse
mind i ask which kernel you tried f2fs with on a gnex? i gain 200+ mbs on writes with f2fs on my gnex on a bad day. && how can you actually prove is just placebo? have you done tests showing it doesn't gain ANY write/read performance compared to ext4?
Guys please... if you wanna have f2fs support hit "THANKS" lets see how many want it.
This shows how many need it and want it, if enought need/want it i will add support in next release
sgspluss said:
Guys please... if you wanna have f2fs support hit "THANKS" lets see how many want it.
This shows how many need it and want it, if enought need/want it i will add support in next release
Click to expand...
Click to collapse
I did it in the OP. If you don't mind, please try to support it as long as you can. Thanks.
Enviado desde mi Galaxy Nexus usando Tapatalk 2
sgspluss said:
Guys please... if you wanna have f2fs support hit "THANKS" lets see how many want it.
This shows how many need it and want it, if enought need/want it i will add support in next release
Click to expand...
Click to collapse
f2fs support was in r398, franco just missed one or two commits for the ramdisk i think so f2fs didn't work....but @osm0sis'es last synapsed version works very well with f2fs on data and cache and system on ext4.
i think he gave permission to use his latest ramdisk
pattyboi:) said:
mind i ask which kernel you tried f2fs with on a gnex? i gain 200+ mbs on writes with f2fs on my gnex on a bad day. && how can you actually prove is just placebo? have you done tests showing it doesn't gain ANY write/read performance compared to ext4?
Click to expand...
Click to collapse
fancy and smitty. yes, it shows upgrade in w/r performance at tests but there is no feeling of anything better compared to ext4. Do you know why PA-Team has never supported f2fs? Totally because it's experiment. The same like ART in KitKat. You can send logs to check some bugs only if its on dalvik runtime, but if you were on art runtime nobody would even check your log. ART became official and fully stable in lollipop... i truly think that f2fs can become more stable but i don't actually know when. At this moment ext4 has nearly the same performance as f2fs but is times more stable. It is not worth spending this stability for such a performance upgrade.
qtoo941 said:
fancy and smitty. yes, it shows upgrade in w/r performance at tests but there is no feeling of anything better compared to ext4. Do you know why PA-Team has never supported f2fs? Totally because it's experiment. The same like ART in KitKat. You can send logs to check some bugs only if its on dalvik runtime, but if you were on art runtime nobody would even check your log. ART became official and fully stable in lollipop... i truly think that f2fs can become more stable but i don't actually know when. At this moment ext4 has nearly the same performance as f2fs but is times more stable. It is not worth spending this stability for such a performance upgrade.
Click to expand...
Click to collapse
I find F2FS absolutely stable, and I don't know in what manner it could compromise stability.
ART is working amazingly well in my Moto G, so I don't agree when you saying it's an experiment in KitKat. The fact that ART is choking for our GNex, doesn't mean it's an experiment. Are you a Google engineer to say that ART is fully stable in lollipop?. I think it never won't work smooth in our devices.
You defend EXT4. I defend Dalvik
ok i have a samsung galaxy SM-T700 what rom and kernal has F2FS support i have searched the forms but nothing for this model came up with a answer.....
thanks very much in advance..
Monster212 said:
ok i have a samsung galaxy SM-T700 what rom and kernal has F2FS support i have searched the forms but nothing for this model came up with a answer.....
thanks very much in advance..
Click to expand...
Click to collapse
Probably none of them do. Developers usually only implement F2FS if the device has slow write speeds on its built in eMMC, such as the original Nexus 7 (and a few others). Some devices have native F2FS support such as the Nexus 9 (which is why it gets its extremely high bench scores). However for this device, it has plenty fast storage already, so the benefit would be almost impossible for the human senses to notice. With all that said, I too would love to use F2FS on at least the cache partition.
SkOrPn said:
Probably none of them do. Developers usually only implement F2FS if the device has slow write speeds on its built in eMMC, such as the original Nexus 7 (and a few others). Some devices have native F2FS support such as the Nexus 9 (which is why it gets its extremely high bench scores). However for this device, it has plenty fast storage already, so the benefit would be almost impossible for the human senses to notice. With all that said, I too would love to use F2FS on at least the cache partition.
Click to expand...
Click to collapse
thank you very much for the reply.. i learned something new...
Monster212 said:
thank you very much for the reply.. i learned something new...
Click to expand...
Click to collapse
Actually, if you install TWRP recovery from here http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Then you can have F2FS support. You then just need to look for a rom that supports F2FS, or a kernel that does. I'm still looking myself, so not sure if any ROMs actually do support F2FS yet, but at least you already have F2FS format support. :good:
SkOrPn said:
Actually, if you install TWRP recovery from here http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Then you can have F2FS support. You then just need to look for a rom that supports F2FS, or a kernel that does. I'm still looking myself, so not sure if any ROMs actually do support F2FS yet, but at least you already have F2FS format support. :good:
Click to expand...
Click to collapse
Thank you for the info, I will now be looking for a good rom or kernal.....
Sent from my SM-T700 using Tapatalk
You can test my kernel here: http://forum.xda-developers.com/showthread.php?t=3139716
ashyx said:
You can test my kernel here: http://forum.xda-developers.com/showthread.php?t=3139716
Click to expand...
Click to collapse
thank you i will install it now and see how it goes...
I would like to do benchmark test results for before and after F2FS. Curious how it compares to my Nexus 7. On cache it was a good performance increase, but on system it did nothing better. EXT4 seems to be the better file system for the system partition, at least on my Nexus 7.
Sent from my SM-T700 using Tapatalk
SkOrPn said:
I would like to do benchmark test results for before and after F2FS. Curious how it compares to my Nexus 7. On cache it was a good performance increase, but on system it did nothing better. EXT4 seems to be the better file system for the system partition, at least on my Nexus 7.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
The kernel I posted doesn't support f2fs on the system partition nor does my guide include it.
As you rightly stated the system partition does not benefit from f2fs as its read only. Ext4 is capable of high read speed.
ashyx said:
The kernel I posted doesn't support f2fs on the system partition nor does my guide include it.
As you rightly stated the system partition does not benefit from f2fs as its read only. Ext4 is capable of high read speed.
Click to expand...
Click to collapse
Yeah agreed, EXT4 is slightly faster at reading, but just by a hair on my N7. However, on partitions that have write permissions, it can "sometimes" be three times faster at random writes. I been using F2FS since feb 2014 "religiously" on my Nexus 7 (and wont run a non-f2fs setup on it), so I am very well versed in its use. Legolas was the first one to bring it to custom Android (I know because I was one of his support techs helping users convert to it, until he disappeared that is lol. Then I started helping USBhost with CarbonROM), and was the first to release a F2FS app in the play store. He was also the first, and only individual, to have a Conversion app to convert your ROM to f2fs, which gave new life to my N7 and any ROM I tried back in 2014 (it did not support 5.0 though). Without F2FS, sadly my Nexus 7 is almost worthless.
If only I can find the many screenshot test results we've done with F2FS, it would come in handy here too. On the N7 its a night and day difference, but here this device is already plenty fast. Id love to see some insane results though.... If only Jaegeuk would develop a Windows driver already. I would like to use it for my Linux box, Windows and Android tbh, and format the sdcards with it, and maybe even USB storage drives to try and pick up on the write speeds a bit. Well see I guess...
My SkyHigh TW LL 5.0.2 kernels support both EXT4 and F2FS for DATA and CACHE partitions.
Note: You need to have supported base firmware for successful flash.
Deathly Aosp Kernel supports Ext4 and f2fs on cache and data
Rom support for it is included on aicp, slim, carbon, liquid
deadman96385 said:
Deathly Aosp Kernel supports Ext4 and f2fs on cache and data
Rom support for it is included on aicp, slim, carbon, liquid
Click to expand...
Click to collapse
ANY ROM can support F2FS. Its just the Kernel that needs to be built with support.
It's possible to convert any partition using various scripts (adjusted to suit device) that are about. But the easiest way is to use ashyx F2FS recovery. It saves a lot of pain.
UpInTheAir said:
ANY ROM can support F2FS. Its just the Kernel that needs to be built with support.
It's possible to convert any partition using various scripts (adjusted to suit device) that are about. But the easiest way is to use ashyx F2FS recovery. It saves a lot of pain.
Click to expand...
Click to collapse
Yeah the roms i listed already have native support no scripts or anything because the f2fs lines have been added too the fstab. So all you need to do is format cache and data in twrp and your done.
deadman96385 said:
Yeah the roms i listed already have native support no scripts or anything because the f2fs lines have been added too the fstab. So all you need to do is format cache and data in twrp and your done.
Click to expand...
Click to collapse
Those ROMs probably use a kernel which has already been patched for F2FS and compiled in-line with the ROM.
Same goes for my SkyHigh kernel, but compiled on its own. All you need to do is format your relevant ROM partitions via script or supported F2FS TWRP. No difference to method except having to flash the kernel separately.
UpInTheAir said:
Those ROMs probably use a kernel which has already been patched for F2FS and compiled in-line with the ROM.
Same goes for my SkyHigh kernel, but compiled on its own. All you need to do is format your relevant ROM partitions via script or supported F2FS TWRP. No difference to method except having to flash the kernel separately.
Click to expand...
Click to collapse
Yep they include my deathly kernel which has f2fs, but without that fstab changes it wont boot on aosp if you convert it unless the tab s is different
deadman96385 said:
Yep they include my deathly kernel which has f2fs, but without that fstab changes it wont boot on aosp if you convert it unless the tab s is different
Click to expand...
Click to collapse
It's the same (similar) ramdisk fstab changes for Samsung based kernel as well, not just source. Edit: As I said, all you need to do to actual "ROM" is just format the relevant partitions.
[NX563J+NX595J][9.0][]EAS kernel(unofficial)
this kernel base on https://github.com/android-linux-stable/msm-4.4
import nubia driver and small part of nubia modification
Features
default fiops i/o scheduler
default EAS cpu scheduler
nx563j:charging maximum current modify to 4A(The measured official charging head can reach 3800+mA)
nx595j:charging maximum current modify to 4.5A
Built in qcacld-3.0
Anti-missing width modification (default 20)
20 is the width (px) size to be modified
Code:
echo 20 > /sys/class/input/input1/anti_missing_dp
build.prop(If adb is not available)
Code:
sys.usb.ffs.aio_compat=1
source:https://gitlab.com/xiayesuifeng/android_kernel_nubia_msm8998
z17(nx563j)
TARGET_KERNEL_CONFIG use xiayesuifeng_nx563j_defconfig
z17s(nx595j)
TARGET_KERNEL_CONFIG use xiayesuifeng_nx595j_defconfig
flash patch
z17:
https://mega.nz/#!flQjBIKD!os080WurqI_Y4i_zG1EtjfMWUeVJK5XqrL4Oo-hjlg8
z17s:
https://mega.nz/#!K5QBUYLa!xJBLFZIQV0yPS922zEtUksrJdZx1ZJwQqmzV4siawNw
sign boot
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
edit /vendor/bin/init.qcom.post_boot.sh
remove this
Code:
# online CPU0
echo 1 > /sys/devices/system/cpu/cpu0/online
# configure governor settings for little cluster
echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/use_sched_load
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/use_migration_notif
echo 19000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay
echo 90 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load
echo 20000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate
echo 1171200 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/io_is_busy
echo "83 1804800:95" > /sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
echo 19000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time
echo 79000 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis
echo 518400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/interactive/ignore_hispeed_on_notif
# online CPU4
echo 1 > /sys/devices/system/cpu/cpu4/online
# configure governor settings for big cluster
echo "interactive" > /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
echo 1 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/use_sched_load
echo 1 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/use_migration_notif
echo 19000 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/above_hispeed_delay
echo 90 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/go_hispeed_load
echo 20000 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_rate
echo 1536000 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/hispeed_freq
echo 1 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/io_is_busy
echo "83 1939200:90 2016000:95" > /sys/devices/system/cpu/cpu4/cpufreq/interactive/target_loads
echo 19000 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/min_sample_time
echo 79000 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/max_freq_hysteresis
echo 806400 > /sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq
echo 1 > /sys/devices/system/cpu/cpu4/cpufreq/interactive/ignore_hispeed_on_notif
aljoscha81 said:
How to download ?
Can you make a flashable zip. like you done with caf kernel?
Click to expand...
Click to collapse
I will send it when I have time in a few days, but now you can only compile it yourself.
niu bi :good:
any help.... my device is z17s, how to flash , error 1 in twrp, unsupported device
Jeff88malaquias said:
any help.... my device is z17s, how to flash , error 1 in twrp, unsupported device
Click to expand...
Click to collapse
Send twrp error screenshot
xiayesuifeng said:
Send twrp error screenshot
Click to expand...
Click to collapse
Sorry, I want to upload a screenshot, but it failed.
Hi, could you make a somehow detail tutorial?
Is this kernel compatible with, and what's the order should I flash it with 1. NFound treble base pack, 2. Havoc os gsi, 3. Opengapps and 4. Magisk?
Should this been flashed after all those things? What files should I modifying after flash the kernel?
xiayesuifeng said:
Send twrp error screenshot
Click to expand...
Click to collapse
xiayesuifeng said:
I will send it when I have time in a few days, but now you can only compile it yourself.
Click to expand...
Click to collapse
Hello i have delete all post i have made in this thread to prevent confusing cause i found out that most of the problems i had was caused by the rom i use but i have a question does the kernel have f2fs support?
Cause mokee 90 uses this file system i think and if the kernel can not handle f2fs is it possible to build it in?
Would be great cause i use the vendor since april 20th build cause since this build treble support is back on mokee 90 rom and it is using f2fs it is a massive speed increase but i miss the awesome fast charge of your kernel so much
Edit:i found out f2fs is also remember .... recovery thing but another question i found a configuration your kernel run bugfree ...but one issue
Notification of led any idea ?
Notice before but anyway your source is updated will you compile a newer file to download or will it wrong?
aljoscha81 said:
Hello i have delete all post i have made in this thread to prevent confusing cause i found out that most of the problems i had was caused by the rom i use but i have a question does the kernel have f2fs support?
Cause mokee 90 uses this file system i think and if the kernel can not handle f2fs is it possible to build it in?
Would be great cause i use the vendor since april 20th build cause since this build treble support is back on mokee 90 rom and it is using f2fs it is a massive speed increase but i miss the awesome fast charge of your kernel so much
Click to expand...
Click to collapse
Could you share the steps you took to install treble gsi and most recent vendor? I'm curious and willing to give it a try...
MrBlubke said:
Could you share the steps you took to install treble gsi and most recent vendor? I'm curious and willing to give it a try...
Click to expand...
Click to collapse
First install mokee twrp
2 wipe everything otherwise you will get no f2fs formate data factory reset etc.
3 install mokee 90 and before boot do root
4 boot
5 same as 2
6 install gsi
7boot if it dosent do wipe cache and dalvic and try again
8 factory reset and install gapps
9 now patch up the vendor as needed
10 done:good:
aljoscha81 said:
First install mokee twrp
2 wipe everything otherwise you will get no f2fs formate data factory reset etc.
3 install mokee 90 and before boot do root
4 boot
5 same as 2
6 install gsi
7boot if it dosent do wipe cache and dalvic and try again
8 factory reset and install gapps
9 now patch up the vendor as needed
10 done:good:
Click to expand...
Click to collapse
So have you extracted the 610 vendor yourself? If so could you share? If not, where can I download the flashable vendor? Which gsi's have you tried, and which one is your prefered one?
MrBlubke said:
So have you extracted the 610 vendor yourself? If so could you share? If not, where can I download the flashable vendor? Which gsi's have you tried, and which one is your prefered one?
Click to expand...
Click to collapse
No i use mokee 90 vendor
aljoscha81 said:
3 install mokee 90 and before boot do root
Click to expand...
Click to collapse
when you say root, that's installing magisk?
MrBlubke said:
when you say root, that's installing magisk?
Click to expand...
Click to collapse
I answered you i am sure but can't see that ... for reading here in thread ....
For the question root... Mean yes install magisk su .. you know some virtual engines have to use this power of control
aljoscha81 said:
Hello i have delete all post i have made in this thread to prevent confusing cause i found out that most of the problems i had was caused by the rom i use but i have a question does the kernel have f2fs support?
Cause mokee 90 uses this file system i think and if the kernel can not handle f2fs is it possible to build it in?
Would be great cause i use the vendor since april 20th build cause since this build treble support is back on mokee 90 rom and it is using f2fs it is a massive speed increase but i miss the awesome fast charge of your kernel so much
Edit:i found out f2fs is also remember .... recovery thing but another question i found a configuration your kernel run bugfree ...but one issue
Notification of led any idea ?
Notice before but anyway your source is updated will you compile a newer file to download or will it wrong?
Click to expand...
Click to collapse
My kernel support for f2fs is theoretically no problem, because my cache partition is now f2fs, and there is no problem.
xiayesuifeng said:
My kernel support for f2fs is theoretically no problem, because my cache partition is now f2fs, and there is no problem.
Click to expand...
Click to collapse
Yes i think also it has support for the file system i use mokee 90 rom as base and as it install it formates every partion as f2fs but some users report that a app they use to check partition info got all partitions shown as ext4 is the file system but i also don't think the app showes right
aljoscha81 said:
Yes i think also it has support for the file system i use mokee 90 rom as base and as it install it formates every partion as f2fs but some users report that a app they use to check partition info got all partitions shown as ext4 is the file system but i also don't think the app showes right
Click to expand...
Click to collapse
Have you tried to see what the app shows for you?
MrBlubke said:
Have you tried to see what the app shows for you?
Click to expand...
Click to collapse
Yes for me the same it shows ext4 but i dont think it is right i have fead long time ago that ufs memory cant use this file system or it is bad for the memory but i dont think it is right the new smartphone from zte or nubia i have read a few days ago also use this file system and i dont think that they will have build in emmc 5.1 memory
aljoscha81 said:
Yes i think also it has support for the file system i use mokee 90 rom as base and as it install it formates every partion as f2fs but some users report that a app they use to check partition info got all partitions shown as ext4 is the file system but i also don't think the app showes right
Click to expand...
Click to collapse
can you modify the fstab?