TWRP
aka Team Win Recovery Project
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First of all :
FOR EXYNOS ONLY
By flashing custom binaries, such as twrp, you will trip knox, loose your warranty and all Samsung Knox features FOREVER.
Firmware-Over-The-Air will no long works with custom binaries.
You have to enable "OEM Unlock" from developers settings.
Don't flash it if you don't understand the previous points.
• Download links :
twrp-3.3.1-r4.1-crownlte.tar
- Mega
- GDrive
• Changelogs : Post 2
• Guide : @geiti94's guide
• Device tree : android_device_samsung_crownlte
• Kernel source : android_kernel_samsung_crownlte
• Known bugs :
No data decryption
Boot delay with f2fs
• Credits :
All you guys who contribute to this and all others projects
Special thanks to @Eamo5 for his Endurance-Kernel-GSI
Thanks to @yarpiin for lot of tips
@jesec for his universal9810 kernel
Zeus Kernel team, @azZA_09 and @Da-BOSS
As for @geiti94 for the flash guide and for publicly publishing his device tree for the Note9
@farovitus for the Exynos-Linux-Stable
TeamWin of course!
Samsung for kernel source
All developpers here and elsewhere who released their sources
Informations
Status : Stable
Created : 2019-05-13
Last edited : 2019-05-08
Changelogs :
Betas
Beta1 :
Removed unused and space hungry System Image backup option
Vendor is no more backed up as disk image, save more space in back up
Tried to get better read/write external sdcard speeds
Improved MTP compatibility (USB connection), closer to aosp
Beta2 :
Backups from previous TWRP versions are now fully supported
F2FS support
Reduced image size
Possibly better i/o speeds
Others minors improvements
Beta3 :
Fixed backups restoration issue (reverted back from 9 to 8.1 build platform for now)
Switched to LZMA compression (about 33% smaller)
Disabled twrp app install prompt (sorry for their authors but this is very annoying)
Other minors improvements
Beta4 :
Fixed FAT32 support
Add NTFS support
Add lot of partitions to backup/restore/wipe
Experimental : Started to introduce an option to full backup data, including internal storage. The best way to switch between ext4 and f2fs. The checkbox is in the setting but it doesn't work for now.
Beta5 :
Updated to TWRP 3.3.1-0
Builded on Pie platform (since backups restoration works perfectly now) which brings lot of improvements
Removed all modifications related to experimental full data backup
Possibly fixed F2FS boot lag
Old releases
Release 1.1 :
Switched to ELS kernel, more up to date, this is the most significant part of this update
Synced with latest omni and twrp commits
Cleanedup device tree ( see sources above )
Implemented the LineageOS DTB image builder for more kernel compatibility (builder will understand)
Switched to gcc-9.1.1 toolchain for kernel compilation part
Deeply improved r/w speeds, at least in internal memory, globally +25% in average. It can reach 90MB/s during a backup saved in internal storage. ( Tests showed pics at 190MB/s in optimal condition :good: )
Fixed F2FS twrp boot delay -> Seems to be related to cache partition with F2FS
Doubtless more things I forgot and will add later
r1.1 : Prevention for some graphical issues
Release 2 :
Less or not at all glitches
95% of zip issues solved ( you can now flash devbase or all the others roms :highfive: )
Release 2.1 :
TWRP source and ELS kernel source updated
Gcc kernel cross-compiler updated
Minors kernel improvements
Others minors improvements
Release 3 :
Finally fixed all zip issue (Thanks to yarpiin for the help)
TWRP source updated
Switched to jesec kernel
Switched to cfq i/o scheduler
Minors improvements
Edit: Big omission to mention, based on omni 8.1
Release 3.1 :
Finally fully working omni 9 twrp
Release 3.2 :
Switch to stock samsung kernel source (latest CSI3)
Deeply reduced size by removing sound, ethernet, tcpip and lot of other useless drivers and stuff for twrp (Around 7MB less)
Update to gcc 10 cross-compiler for kernel part
Fixed toybox which now replaces and updates busybox
Changed MTP device name (Windows users will have to uninstall the phone from device manager then unplug/plug to see effects)
Other minor improvements
Release 3.3 :
Fixed unzip fail with some zips by replacing it with precompiled UnZip/InfoZip 6.0
Fixed flashing .img on odm partition
Release 3.4 :
Definitively fixed flashing .img on odm partition
Removed unusable encrypted backup option
Add an option to prevent samsung account and lockscreen loop issue in the zip install page - I strongly advise to check the box when flashing a kernel
Release 3.5 :
Add a workaround for the (too) common busybox calls
Add the secured kernel flash checkbox for image flash
Release 3.6 :
Synced to last sources
Switch to busybox which should fix most of zip flash issues
Fix screenshots color
Move secured kernel flash checkbox in settings
Release 3.7_q :
Add support for system as root introduced in One UI 2 beta - Don't use it with android Pie
For devs : in line with twrp, system partition mount point as moved to /system_root and android system folder is symlinked at /system, some changes are needed to keep compatibility
Release 3.8_q :
Synced to last source
Updated kernel to DTA1 source
Finally support almost all roms & zips
Fixed dmesg
Release 3.9_q :
Synced to DTA5 kernel source with latest linux stable upstream (4.9.214)
Clang compiled kernel
Reworked system mounting, it should be more rom compliant
Release 4.0_q :
Synced to DTCA and 4.9.218 kernel source
Fixed lockscreen/samsung account issue patch
[/LIST]
Release 4.0.1_q :
Fixed not clang compiled kernel in r4.0
Last release
Release 4.1 :
Removed my hardcoded force system as root mount stuff (All AOSP 10 based and some OneUI roms (as DevBase) have now merged proper SAR support)
Merged some SAR related commits which unified Q and Pie support
Synced to last kernel and recovery sources
Fixed unencryptable data partition after format
Fiiiiirst. Great twrp!
After updating to beta 3 i cannot see in twrp the fat32 external card 200gb sandisk. I see the internal f2fs sdcard. With beta 1and 2 it was the opposite. Why is that???
Sent from my [device_name] using XDA-Developers Legacy app
karapoutsoglou said:
After updating to beta 3 i cannot see in twrp the fat32 external card 200gb sandisk. I see the internal f2fs sdcard. With beta 1and 2 it was the opposite. Why is that???
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
It will be fixed in next release. Sorry for that!
But seriously why do you use this sh*t?!:laugh: Go to exFat!
At least you point it out this issue!
I will upload in few hours.
Arteush said:
It will be fixed in next release. Sorry for that!
But seriously why do you use this sh*t?![emoji23] Go to exFat!
At least you point it out this issue!
I will upload in few hours.
Click to expand...
Click to collapse
Believe it or not i never managed the twrp to see and flash from sdcard with anything but fat32! With exfat will i be able to flash from twrp??? With ntfs i never managed to do that
Sent from my [device_name] using XDA-Developers Legacy app
karapoutsoglou said:
Believe it or not i never managed the twrp to see and flash from sdcard with anything but fat32! With exfat will i be able to flash from twrp??? With ntfs i never managed to do that
Click to expand...
Click to collapse
He's trolling just ignore him. Use either the stock filesystem or f2fs if your kernel supports it
Care to share the device trees?
Sent from my SM-N960F using Tapatalk
karapoutsoglou said:
Believe it or not i never managed the twrp to see and flash from sdcard with anything but fat32! With exfat will i be able to flash from twrp??? With ntfs i never managed to do that
Click to expand...
Click to collapse
extfat FTW
yeah it works with windows too and is more optimised for card storage# fat32 is dead and ntfs is more of a windows dedicated format.
bober10113 said:
extfat FTW
yeah it works with windows too and is more optimised for card storage# fat32 is dead and ntfs is more of a windows dedicated format.
Click to expand...
Click to collapse
ok. i will reformat to exfat. im pretty sure that with exfat i could not flash from twrp. let's see
Sent from my [device_name] using XDA-Developers Legacy app
karapoutsoglou said:
ok. i will reformat to exfat. im pretty sure that with exfat i could not flash from twrp. let's see
Click to expand...
Click to collapse
well since the note 8 ive been using 256gb sd cards with extfat and no problems.
fat32 and cards over 128 gig dosent work well
karapoutsoglou said:
ok. i will reformat to exfat. im pretty sure that with exfat i could not flash from twrp. let's see
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
karapoutsoglou said:
Believe it or not i never managed the twrp to see and flash from sdcard with anything but fat32! With exfat will i be able to flash from twrp??? With ntfs i never managed to do that
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
With Beta4 you have now NTFS and FAT32 full support
DEVILOPS 007 said:
He's trolling just ignore him. Use either the stock filesystem or f2fs if your kernel supports it
Click to expand...
Click to collapse
Ahaha seriously?! I think you did not understand his question. Or you are the troll?
Arteush said:
With Beta4 you have now NTFS and FAT32 full support
Click to expand...
Click to collapse
It's really great TWRP!
My backup size now is reduced from 18GB to 12GB.
Well done job! Thanks!
Sent from my SM-N960F via Tapatalk
Arteush said:
With Beta4 you have now NTFS and FAT32 full support
Click to expand...
Click to collapse
yes i already installed. you are amazing
Sent from my [device_name] using XDA-Developers Legacy app
Arteush said:
Ahaha seriously?! I think you did not understand his question. Or you are the troll?
Click to expand...
Click to collapse
Come on don't tell people to use anything other than ext4 or f2fs lol
DEVILOPS 007 said:
Come on don't tell people to use anything other than ext4 or f2fs lol
Click to expand...
Click to collapse
So you don't reread or don't understand his question? ( Or troll again?:silly: )
We talked about a microSD dude!
Arteush said:
So you don't reread or don't understand his question? ( Or troll again?:silly: )
We talked about a microSD dude!
Click to expand...
Click to collapse
Sorry I'm just joking around. Thought that was obvious so my bad?
Mate the beta 4 still has the start up bug. It get stuck at the twrp screen for 8 secs. Hoping u can fix the issue. Thanks for ur hard work n time ????
I think it is related to mtp service. The twrp boots when you hear the sound of fiding your phone on pc. However, idk if it is a really problem to wait a little
Related
this rom is with the intention of bringing the nexus experience to the lg optimus g, so is based on the source code of google android kitkat 100% stock, and the kernel and device tree is based 100% on the nexus 4.
I have taken the kitkat nexus 4 kernel and I have adapted it to the Lg optimus G preserving the essence of the nexus also the device tree is based 100% on the nexus 4
at this moment this rom not pretend to have new mods or options, i only one to focus in the performance so this rom is based in the nexus 4 but with optimizations, like a15 optimizations, kernel vm optimizations, ui rendering optimizations, i/o performance for more speed in read and write, building with ART compatibility (dalvik default for now)
my sources are open and free in my github: http://github.com/samuaz
what works?
everything
what not work?
MHL, I WILL FIX THIS IN THE NEXT DAYS
REMEMBER THE PROCESS TO INSTALL THIS ROM IS THE SAME AS OTHERS KITKAT ROMS LIKE OMNI OR PA, You need to update your recovery download from here for geeb
http://ribs.bbqdroid.org/recoveries
Is a flasheable zip flash from your actually recovera and reboot the recovery, next do the wipes and reboot the recovery again And next flash The rom
BUT REMEMBER THIS RECOVERY DONT HAVE A EXTERNAL SD SUPPORT
Code:
you can get back to your old twrp recovery with external sd support flashing it via twrp sideload example
download this: http://forum.xda-developers.com/attachment.php?attachmentid=2275794&d=1379880501
that is the twrp recovery with external sd support
restart your phone in recovery mode go to advance and next click on adb sideload
connect your phone to the pc and start a terminal or cmd if you use windows
type adb devices to check if your devices is detected if yes, type
adb sideload TWRP-2.6.3.0.zip
and that will flash the recovery with external sd support,
you need to have adb installed in your pc
the process to install this rom is the same like the others kitkat roms like omni or pa it requiered lasted twrp recovery with selinux support, but that recovery builded by chadouming dont have sdcard support i will build a new recovery with external sd support for our e970
CHANGELOG AND DOWNLOADS IN 2ND POST
EXTRAS:
FOR ROOT USE THIS FLASHEABLE ZIP (FLASH AFTER THE ROM - THANKS TO CHAINFIRE):
http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip?retrieve_file=1
GAPPS (PLEASE ONLY USE THIS TESTED GAPPS TO USE CORRECTLY THE ART COMPILER ):
http://www.androidfilehost.com/?a=show&w=files&flid=7988
Contact:
G+:https://plus.google.com/114802107956069595377
Email: [email protected]
FACEBOOK:https://www.facebook.com/sazcona
TWITTER: @samuazcona
INSTAGRAM: @samuazcona
If you want to buy me a drink
XDA:DevDB Information
Pure Nexus Aosp for lg optimus g e970, a ROM for the AT&T LG Optimus G
Contributors
samuazcona
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2013-12-02
Created 2013-12-03
Last Updated 2013-12-09
Reserved
changelog:
3rd release DEC 07-2013
- improve the system ui rendering to remove rendering stutterings
- enable vsync in kernel to help to remove stutterings in system ui rendering (is disabled by default in the google kernel)
- SWITCH TO ART by default, with fixes to install unsoported apps like whatsapp and fix for system cache rebuild on every reboot (you can install whatsapp and others and works good with art and have a fastreboot)
- FIX for lag when you are downloanding apps or installin apps from play store
- Fix and improve bad read and write i/o speed (by default the stock kernel have a very bad values, i get 500+ in read and 35+mb in write test maked with mpdecision disabled)
- maybe others dont remember
ALERT: FULL WIPE IS MANDATORY AND THIS GAPPS ARE MANDATORY TOO
so the process to install this update is, Full wipe: system, data, cache and dalvik, install the rom, install the mandatory gapps, and install the root
ALERT 2: THE FIRST BOOT CAN TAKE 5-10 MINUTES BECAUSE ART IS DOING THE JOB, SO DONT WORRY JUST WAIT IT WILL BOOT FINE, AND MAYBE YOU GET GAPPS PROCESS FC DONT WORRY TOO CLICK OK ONLY DO FC AT BOOT, GAPPS WORKS GOOD
DOWNLOAD:
ROM
size: 183 MB
md5: 5710c515583ef175a65b77c130f97880
url: http://www.androidfilehost.com/?fid=23252070760974333 link
GAPPS MANDATORY: http://www.androidfilehost.com/?fid=23212708291681724
--------------------------------------------------------------------------------------------------------
OLD
Second release DEC 4 - 2013
- add nexus bootanimation
- add optimized moto x dalvik
- add init.d support and user init support
- disable art verification (now you can install apps like whatsapp with art enabled)
- fix vm tweak value
- EGL and GPU rendering optimizations
- fix for default max a min cpu and gpu freqs
- maybe others i dont remember
download link
http://www.androidfilehost.com/?fid=23252070760972882
first release: DEC 2 - 2013
- finish to adapt and make a rebase of the mako kitkat kernel for the lg optimus G, all working
- finish to adapt the device tree from the mako kitkat
- build with ART compatibility
- odexed like stock google roms for use with ART
- add A15 compile optimizations
- add EGL optimizations from nexus 5
Download link
http://d-h.st/vhE
Reserved
Unable to install zip I am getting error while installing like 'this is geeb your device is e970….'
Sent from my LG Optimus G using xda premium
Not working
It won't install. This is what it says:
this is geeb your device is e970….
murali12 said:
Unable to install zip I am getting error while installing like 'this is geeb your device is e970….'
Sent from my LG Optimus G using xda premium[/QUOT
mine says this package is geeb your device is geebus
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
murali12 said:
Unable to install zip I am getting error while installing like 'this is geeb your device is e970….'
Sent from my LG Optimus G using xda premium
Click to expand...
Click to collapse
theonlytrill said:
It won't install. This is what it says:
this is geeb your device is e970….
Click to expand...
Click to collapse
ChiefWilNel said:
murali12 said:
Unable to install zip I am getting error while installing like 'this is geeb your device is e970….'
Sent from my LG Optimus G using xda premium[/QUOT
mine says this package is geeb your device is geebus
Click to expand...
Click to collapse
You need to update your recovery download from here for geeb
http://ribs.bbqdroid.org/recoveries
Is a flasheable zip flash from your actually recovery and reboot the recovery, next do the wipes and reboot the recovery again And next flash The rom
Click to expand...
Click to collapse
samuazcona said:
ChiefWilNel said:
You need to update your recovery download from here for geeb
http://ribs.bbqdroid.org/recoveries
Is a flasheable zip flash from your actually recovery and reboot the recovery, next do the wipes and reboot the recovery again And next flash The rom
Click to expand...
Click to collapse
thanks, the version of twrp you have posted doesn't access my external sd...so now I am screwed. I will have to figure out how to downgrade twrp which is impossible since it doesn't read external
Click to expand...
Click to collapse
ChiefWilNel said:
samuazcona said:
thanks, the version of twrp you have posted doesn't access my external sd...so now I am screwed. I will have to figure out how to downgrade twrp which is impossible since it doesn't read external
Click to expand...
Click to collapse
you can get back to your old twrp recovery with external sd support flashing it via twrp sideload example
download this: http://forum.xda-developers.com/attachment.php?attachmentid=2275794&d=1379880501
that is the twrp recovery with external sd support
restart your phone in recovery mode go to advance and next click on adb sideload
connect your phone to the pc and start a terminal or cmd if you use windows
type adb devices to check if your devices is detected if yes, type
adb sideload TWRP-2.6.3.0.zip
and that will flash the recovery with external sd support,
you need to have adb installed in your pc
the process to install this rom is the same like the others kitkat roms like omni or pa it requiered lasted twrp recovery with selinux support, but that recovery builded by chadouming dont have sdcard support i will build a new recovery with external sd support for our e970
Click to expand...
Click to collapse
samuazcona said:
ChiefWilNel said:
you can get back to your old twrp recovery with external sd support flashing it via twrp sideload example
download this: http://forum.xda-developers.com/attachment.php?attachmentid=2275794&d=1379880501
that is the twrp recovery with external sd support
restart your phone in recovery mode go to advance and next click on adb sideload
connect your phone to the pc and start a terminal or cmd if you use windows
type adb devices to check if your devices is detected if yes, type
adb sideload TWRP-2.6.3.0.zip
and that will flash the recovery with external sd support,
you need to have adb installed in your pc
the process to install this rom is the same like the others kitkat roms like omni or pa it requiered lasted twrp recovery with selinux support, but that recovery builded by chadouming dont have sdcard support i will build a new recovery with external sd support for our e970
Click to expand...
Click to collapse
I downloaded the file you linked. side loaded. ext sd now shows up, however I still get the same error with your rom
Click to expand...
Click to collapse
ChiefWilNel said:
samuazcona said:
I downloaded the file you linked. side loaded. ext sd now shows up, however I still get the same error with your rom
Click to expand...
Click to collapse
You cant flash my rom with The old recovery only can be flashed with the new without external sd support i will work to build a new twrp with external sd suport
Click to expand...
Click to collapse
building a new update with the next changes:
- add nexus bootanimation
- add optimized moto x dalvik
- add init.d support and user init support
- disable art verification (now you can install apps like whatsapp with art enabled)
- fix vm tweak value
- EGL and GPU rendering optimizations
- fix for default max a min cpu and gpu freqs
- maybe others i dont remember
I am able to install
Sent from my LG-E970 using xda premium
murali12 said:
I am able to install
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
what did you do? I was thinking of trying to do an adb push to the internal card, however all I can do is adb side load. is it a good rom?
can F180L flash this rom?
besides, do this rom support F93kernel? because i want "double click screen on" function
adilsh said:
can F180L flash this rom?
besides, do this rom support F93kernel? because i want "double click screen on" function
Click to expand...
Click to collapse
At this moment only e970 i need to make the device tree for the others devices, you can flash any kernel only if is for kitkat
New update maybe tomorrow is building right now
Changelog
- rebase on master branch of KitKat (a lot of fixes and updates)
- fix lag when you are downloanding and installings apps
- improves in the read and write speed 500+mb of read and 35+mb on write speed
- a lot of improves in ui rendering not more stutterings
- maybe more
- ART compiler by default dalvik as fallback
samuazcona said:
New update maybe tomorrow is building right now
Changelog
- rebase on master branch of KitKat (a lot of fixes and updates)
- fix lag when you are downloanding and installings apps
- improves in the read and write speed 500+mb of read and 35+mb on write speed
- a lot of improves in ui rendering not more stutterings
- maybe more
- ART compiler by default dalvik as fallback
Click to expand...
Click to collapse
This sound pretty cool. Keep it up!
samuazcona said:
At this moment only e970 i need to make the device tree for the others devices, you can flash any kernel only if is for kitkat
Click to expand...
Click to collapse
it's a pity really want to try this awesome rom
I got it installed by side load..the rom works but it is kind meh compared to stock, don't see much improvement. I really do like LG's ui I could just do without all the at&t bloat
Recovery and Kernels for F2FS
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Instructions:
I tested this procedure with SlimKat so my advice is to start with a working SlimKat rom or another rom that is reported to work good.
We have to Format our memory with F2FS. We need a "special" TWRP and a compatible kernel.
Compatible Kernel:
MiRaGeKernel-mako-F2FS-140331.zip
SlimKernel-mako-F2FS-140331.zip
(All credits to authors. I have only made them compatible with F2FS)
Download compatible Kernel
Download "special" TWRP openrecovery-twrp-2.7.0.0-mako-F2FS.img
Copy Kernel on Phone
Flash Kernel with your current Recovery
Flash "special" TWRP with Fastboot
Reboot in Recovery
Go to Wipe Menu and press Format Data (The Big BUTTON!) (You will LOSE all your Data! Music, Movies etc!!)
Reboot
(Recovery has a RED back button to remember you that you are using the F2FS recovery!)
Enjoy
Phone is snappy and smooth with F2FS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To go back:
- Flash a "normal" recovery
- Flash your previous kernel
- Format Data
(Required commit)
legolas93 said:
Recovery and Kernels for F2FS
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Instructions:
I tested this procedure with SlimKat so my advice is to start with a working SlimKat rom or another rom that is reported to work good.
We have to Format our memory with F2FS. We need a "special" TWRP and a compatible kernel.
Compatible Kernel:
MiRaGeKernel-mako-F2FS-140331.zip
SlimKernel-mako-F2FS-140331.zip
(All credits to authors. I have only made them compatible with F2FS)
Download compatible Kernel
Download "special" TWRP openrecovery-twrp-2.7.0.0-mako-F2FS.img
Copy Kernel on Phone
Flash Kernel with your current Recovery
Flash "special" TWRP with Fastboot
Reboot in Recovery
Go to Wipe Menu and press Format Data (The Big BUTTON!) (You will LOSE all your Data! Music, Movies etc!!)
Reboot
(Recovery has a RED back button to remember you that you are using the F2FS recovery!)
Enjoy
Apart from Benchmarks phone is snappy and smooth.
To go back:
- Flash a "normal" recovery
- Flash your previous kernel
- Format Data
(Required commit)
Click to expand...
Click to collapse
whtz the benefit of this, plz
abir099 said:
whtz the benefit of this, plz
Click to expand...
Click to collapse
It's built specifically for flash storage, including FS level TRIM which executes the command during every commit and doesn't need to rely on Android's native TRIM which only TRIMs during screen off. It's much faster based on current implementations and etc. The only downside is that F2FS isn't considered "stable" yet. This is why there's not a lot of devices on the market has F2FS out of the box. The only one I know is the Moto X and G.
deltatux
Also work with my HellsDoctor and @ak 's one.
@legolas93 are you going to release an ALL-F2FS version like you did for the nexus 7 2012?
Doesn't seem to have done anything. I followed the op. Running ak newest kernel. Got the right twrp with red back button. Went to wipe went to format typed yes. Operation completes very quickly. Reboot and everything seems to be the same ie all items are still on SD card.
How do I tell if this worked?
Sent from my Nexus 4 using Tapatalk 2
jmtjr278 said:
Doesn't seem to have done anything. I followed the op. Running ak newest kernel. Got the right twrp with red back button. Went to wipe went to format typed yes. Operation completes very quickly. Reboot and everything seems to be the same ie all items are still on SD card.
How do I tell if this worked?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
it worked when there's no data left on your internal, maybe try to wipe data again, and post recovery.log
@legolas93 Did you ported F2FS from which version of Linux?
jmtjr278 said:
Doesn't seem to have done anything. I followed the op. Running ak newest kernel. Got the right twrp with red back button. Went to wipe went to format typed yes. Operation completes very quickly. Reboot and everything seems to be the same ie all items are still on SD card.
How do I tell if this worked?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
This happens to me too. Some installed apps FC after doing this, though.
It is like TWRP does nothing to the phone. Factory resets or classical wiping don't do anything, either.
--
PatrickMac said:
@legolas93 are you going to release an ALL-F2FS version like you did for the nexus 7 2012?
Click to expand...
Click to collapse
I don't think that All-F2FS make us gain a big benefit and we will lose support of all ROMs...etc..
I think it's better to stay with only /data as F2FS in this case, so we can use all ROMs with a very small pain.
jmtjr278 said:
Doesn't seem to have done anything. I followed the op. Running ak newest kernel. Got the right twrp with red back button. Went to wipe went to format typed yes. Operation completes very quickly. Reboot and everything seems to be the same ie all items are still on SD card.
How do I tell if this worked?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Try to follow the procedure flashing one of the two kernel on first post. When you are ok try to flash ak over it!
Use DiskInfo to see if all went good!
guimendes said:
@legolas93 Did you ported F2FS from which version of Linux?
Click to expand...
Click to collapse
It's mainly a dennes54 kernel-work. We are around Linux 3.10+ level..
@legolas93 could you maybe upload another compatible kernel? Seems like these only work for AOSP ROMs and not CAF.... Hellscore's CM kernel (http://d-h.st/u6o) would be awesome ☺
Sent from my Nexus 7 using Tapatalk
Awesome mate I liked f2fs; better storage performance and handling. But only thing holding me back is fewer kernels supporting this filesystem. Can you make matr1x kernel supporting this f2fs?
Thanks. My device is not yet rooted, gonna root it soon. So my question is, after finishing rooting and flashing slimkat like I planned to, can I use the f2fs like instructed or do I need to do anything else?
So anyone can tell me what's the advantage? I read it but didn't get it.
Don't work.... always on ext4 and data not formated... My kernel support f2fs.
barome said:
Don't work.... always on ext4 and data not formated... My kernel support f2fs.
Click to expand...
Click to collapse
Do you mean it does not work with HellsDoctor?
Sent from my AOSP on Mako using Tapatalk
---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------
@legolas93 Is there a modified CWM recovery image with F2FS support added for this device?
Sent from my AOSP on Mako using Tapatalk
halfbytecode said:
Do you mean it does not work with HellsDoctor?
Sent from my AOSP on Mako using Tapatalk
---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------
Is there a modified CWM recovery image with F2FS support added for this device?
Sent from my AOSP on Mako using Tapatalk
Click to expand...
Click to collapse
Hells Doctor is comptaible F2FS but this recovery doesn't format data at all... And always ext4 of course
barome said:
Don't work.... always on ext4 and data not formated... My kernel support f2fs.
Click to expand...
Click to collapse
It worked for me. My data was formated. I tried it with the kernels provided in the OP. Your kernel stuck at the bootanimation. So I guess your implementation is different from legolas kernel mods.
PatrickMac said:
It worked for me. My data was formated. I tried it with the kernels provided in the OP. Your kernel stuck at the bootanimation. So I guess your implementation is different from legolas kernel mods.
Click to expand...
Click to collapse
Hmmm... Maybe... I committed same change as @ak so xGenesis must not work too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Slim6, based on marshmallow 6.0.1, is now available for download! Slim6 is still in its early stages of development so if your favourite feature is not back yet, don’t worry more will be added with later releases along with additional devices.
Features:
DPI Changer
SlimLauncher
Root access
Layers support
Add dt2w on doze
Show each app name being optimized during boot
Chamber of secrets
SlimActions and shortcuts
Slim's Hardware key rebinding
Advanced reboot menu
AOSP Day Night theme (experimental)
In-call vibration features (not on this device obviously)
Statusbar clock and date customizations
Battery icon and text
SlimRecents
Slim NavBar with double tap function
Snap camera
Slim6 builds: awifi / v500
Google Apps: OpenGApps (arm, 6.0, I usually use micro)
SOURCES:
Device: https://github.com/MyczkowskiAdam/android_device_lge_awifi
Kernel: https://github.com/awifi-dev/android_kernel_lge_awifi
Vendor blobs: https://github.com/awifi-dev/proprietary_vendor_lge
Thanks:
@fefifofum for the device tree and his hardwork on this device! Keep it up!
@indian84 for testing my builds, as I don't own the device itself ( Please ask him questions about how this ROM runs and feels, I cannot answer them)
XDA developers
SlimROMs Team
CyanogenMod Team
Google
XDA:DevDB Information
SlimROM for v500 aka awifi, ROM for the LG G Pad 8.3
Contributors
Adam Myczkowski, fefifofum, indian84
Source Code: https://github.com/SlimRoms
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: KiKat Bootloader
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 1.7
Stable Release Date: 2016-10-07
Created 2016-07-16
Last Updated 2017-11-15
Reserved
30/07/2016
Updates to device/qcom/common
Fixes to dark theme UI elements
Updates to frameworks/av
Updates to frameworks/native
Hardware/qcom/audio-caf/msm8960: Revert 'hal: Add support for AUDIO_DEVICE_OUT_LINE'
System/netd: Don't build the QSAP SDK on Nexii
System/bt: Bluetooth: fix stuttering on broadcom bt devices (Thanks Cal Archer)
Updates to device/qcom/common and device/qcom/sepolicy
Ashmem updates from aosp to native and system/core
Updates to frameworks/native
Updates to frameworks/opt/net/ims, frameworks/opt/net/wifi and frameworks/opt/slim
Rebased wpa_supplicant_8
Remove smart pulldown and search from SlimActions
Updates to caf msm8916 hardware/qcom/audio and hardware/qcom/media hals
Slim DeviceHandler: Add device specific screen off gesture settings
SlimLauncher: Remove launcher shortcut from update_workspace and fix settings not enabling/disabling properly
Updates to system/core and system/extras
SysUI: Guard against NPE in SignalClusterView
FAQ
Flashing Instructions -
First Time flashing Slim6
1. Make sure you have latest TWRP installed.
2. Make a nandroid of your current ROM.
3. Wipe everything except for internal storage and external SD card if you using one. Clean Flash is mandatory.
4. Flash ROM + Gapps. I use Open GAPPS Pico. Adam uses Open GAPPS Micro on his V400. You can use GAPPS of your choice, but it is advised to stick to recommended GAPPS.
5. Reboot.
6. Enjoy the awesomeness.
Updating Slim6 build
1. Dirty flash ROM and GAPPS.
2. Reboot.
If you want, you can wipe Cache, Dalvik/ ART Cache and System before flashing ROM and GAPPS. Do not forget to flash GAPPS.
Root
The ROM has root built-in. You can enable it under Developer Options.
WARNING - DO NOT FLASH SUPERSU. THE TAB WON'T BOOT.
goog work,
FAQ Added in 3rd Post..
Will be adding more as we go ahead..
Great!!! I'll try this soon. Thanks for support this device
Tried this out last night. Install ran well with zero problems. Seems to be very fast. Thanks for the support! keep it up.
good work. But one problem I have . 64 gigabytes sdcard
Twrp 3.0.2 = ntfs not work , exFAT work
he system slim = ntfs work , exFAT not work
what with this ?
k3wlar said:
good work. But one problem I have . 64 gigabytes sdcard
Twrp 3.0.2 = ntfs not work , exFAT work
he system slim = ntfs work , exFAT not work
what with this ?
Click to expand...
Click to collapse
Strange. I do not use SD Card, so I cannot confirm. May be @Adam Myczkowski can give us some logic behind this?
k3wlar said:
good work. But one problem I have . 64 gigabytes sdcard
Twrp 3.0.2 = ntfs not work , exFAT work
he system slim = ntfs work , exFAT not work
what with this ?
Click to expand...
Click to collapse
From the mountpoints in device tree it should support any type. Can you check if it works on CM13 or not? If it doesn't work on CM13 fefifofum did not add support for exFAT yet, alternatively you can reformat your sd card to FAT32, Im 100% sure theres a tool that allows you to format storages bigger than 32GB into FAT32 which should be supported by any rom. I've got 16 and 32GB cards for my G4 and G Pad 7.0 formated to FAT32 and never had any issues.
indian84 said:
Strange. I do not use SD Card, so I cannot confirm. May be @Adam Myczkowski can give us some logic behind this?
Click to expand...
Click to collapse
Adam Myczkowski said:
From the mountpoints in device tree it should support any type. Can you check if it works on CM13 or not? If it doesn't work on CM13 fefifofum did not add support for exFAT yet, alternatively you can reformat your sd card to FAT32, Im 100% sure theres a tool that allows you to format storages bigger than 32GB into FAT32 which should be supported by any rom. I've got 16 and 32GB cards for my G4 and G Pad 7.0 formated to FAT32 and never had any issues.
Click to expand...
Click to collapse
I just tested with 32GB SD Card formatted to FAT32, and it works well in TWRP and ROM.
This problem I had earlier ... unfortunately we can not use FAT32 because I often zip and rar files larger than 2 gigabytes and films more than 2GB ..and if I remember correctly for FAT 32 file one registration is limited to 2 gigabytes
what amazes me that there is no support for NTFS twrp 3.0.2
clean cm13 try and let you know how it went
k3wlar said:
This problem I had earlier ... unfortunately we can not use FAT32 because I often zip and rar files larger than 2 gigabytes and films more than 2GB ..and if I remember correctly for FAT 32 file one registration is limited to 2 gigabytes
what amazes me that there is no support for NTFS twrp 3.0.2
clean cm13 try and let you know how it went
Click to expand...
Click to collapse
Let us know how it goes..
So I successfully applied cm13 .sdcard works as it should. from five at the beginning .. and wipe again applied SLIM ... and now exFAT works ... do not know what it was but nothing here changed the sdcard. Barrel is that it already goes
k3wlar said:
So I successfully applied cm13 .sdcard works as it should. from five at the beginning .. and wipe again applied SLIM ... and now exFAT works ... do not know what it was but nothing here changed the sdcard. Barrel is that it already goes
Click to expand...
Click to collapse
Im glad to hear it. It might have been some internal error or something with sdcard itself, that can happen sometimes.
k3wlar said:
So I successfully applied cm13 .sdcard works as it should. from five at the beginning .. and wipe again applied SLIM ... and now exFAT works ... do not know what it was but nothing here changed the sdcard. Barrel is that it already goes
Click to expand...
Click to collapse
Good to hear you got it working.
My tablet feels smoother than ever on this ROM.
Thanks to Adam. :good:
I'm sorry but I have a back problem .. I have some applications that require root .. unfortunately, one that is built into the system for some reason is not working as it should.
tried here on supersu.2.46 bootlop..... then I tried 2.76 bootlop again .....
Any suggestions on how to solve it?
edit : Then I tried the 2.76-SYSTEM MODE ... bootloop
k3wlar said:
I'm sorry but I have a back problem .. I have some applications that require root .. unfortunately, one that is built into the system for some reason is not working as it should.
tried here on supersu.2.46 bootlop..... then I tried 2.76 bootlop again .....
Any suggestions on how to solve it?
edit : Then I tried the 2.76-SYSTEM MODE ... bootloop
Click to expand...
Click to collapse
Can you hold this till tomorrow? I don't have access to my tablet to test. I flashed 2.76 system mode before putting together the FAQ and had no problem. But let me confirm again tomorrow.
k3wlar said:
I'm sorry but I have a back problem .. I have some applications that require root .. unfortunately, one that is built into the system for some reason is not working as it should.
tried here on supersu.2.46 bootlop..... then I tried 2.76 bootlop again .....
Any suggestions on how to solve it?
edit : Then I tried the 2.76-SYSTEM MODE ... bootloop
Click to expand...
Click to collapse
Slim does not support superuser, you need to go to developer options and enable root for apps and adb.
Adam Myczkowski said:
Slim does not support superuser, you need to go to developer options and enable root for apps and adb.
Click to expand...
Click to collapse
So it is a pity .. but nothing can do nothing but wait
FizTech kernel
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will ignore you.
*/
Click to expand...
Click to collapse
Hi, I modifed stock 23.5.A.1.291 kernel to support f2fs file system etc.
The kernel is EXPERIMENTAL so I need testers.
Features for now:
F2FS support (without encryption)
Disabled sony RIC
SELinux permissive
GPU overclock
Kcal support
IntelliThermal
init.d support
Multirom works using no-kexec workaround (WIP kexec-hardboot)
DIRTY COW exploit patched!
Both f2fs and ext4 partitions support
Custom CPU govenors
Custom ZEN I/O scheduler as requested
Adreno Idler
Intelli-plug
Voltage Control
Features that will be added:
CPU overclock
Optimizations
working kexec-hardboot patch
CPU govenors
I/O schedulers
you tell me?
Features that will not be added:
TWRP - install it with fastboot (custom roms also have them )
Prerequisites:
Official TWRP from https://twrp.me/ (it contains mandatory mkfs.f2fs file)
Xperia Z3 Compact
Fastboot drivers installed and unlocked bootloader
FizTech kernel - helium
Instructions:
I recommend to do this after fresh install of ROM of choice. I tested my kernel on SLiMM and AOXP.
Kernel must be flashed through recovery. The zip contain wifi module and script that corrects partition layout.
If you want to use f2fs filesystem then follow optional steps which will format your /data and /cache partitions. (Maybe backup? )
Think thrice if you are determined to install this!
Install official TWRP
Code:
fastboot flash recovery twrp.img
To enter recovery press POWER and VOLUME down buttons simultaneously when phone is switched off. It should boot to recovery. This requires new bootloader, that allows booting to recovery.
Install ROM of your choice
F2FS optional : Wipe->advanced wipe select /cache and change filesystem to F2FS (Repair or Change File System)
F2FS optional : Do the same for /data
Install kernel ZIP
Reboot and wait. Sometimes it takes few minutes, especially after fresh install.
F2FS advice: If device is not booting, please reboot to recovery. Check your if your /data and /cache filesystems are F2FS. If not then repeat F2FS optional steps. Even if your partitions were F2FS, install kernel zip once again.
Optional: install TWRP once again if it was damaged by ROM installation.
If you don't see F2FS format option in "Repair or Change File System" then your recovery doesn't have mkfs.f2fs file in /sbin of your recovery (it needs to have permissions also). Use offical TWRP from @someone755
Downloads:
Lithium <latest>
Kernel sources:
[url]https://github.com/adrset/kernel[/URL]
Credits:
@someone755
@Myself5
@AndroPlus
@DooMLoRD
@faux123
@frantisek.nesveda
@arter97
@tomascus
SONY
And all other contributors!
Sorry if I forgot you! Tell me and I will add you
About me:
I am currently studing, so the amount of time I can dediacate to XDA is limited. I am begginig my journey with developing - be understanding!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog:
Version 1 - Fiztech Hydrogen
- initial version
- F2FS support
- DM-verity disabled
- sony RIC disabled
Version 2 - FizTech Helium
- added GPU overclock
- added kcal support
- added IntelliThermal
- added init.d support
- initial patch for Kali-Nethunter support
- patched DIRTY COW exploit - in near future more safety patches will be added
- Kernel supports f2fs and ext4 partitions
Version 2.1 - FizTech Helium Revised
- added some CPU govenors
- added ZEN I/O scheduler as requested
- added Adreno Idler as requested
- enabled Intelli-plug
- exfat module enabled
- SElinux enforce
Version 3 Codename Lithium
- Added Voltage Control
- Added sioplus I/O scheduler
- Storage optimizations
Version (double) n (work still in progress)
- I will try to update the kernel to newer versions (AFAIK current one is 3.4.0, will try to update maybe to 3.4.113 if it's possible?)
- CPU overclock (don't prefer this - our device is warm enough )
- govenors
- maybe compile using linaro toolchain
- Kali-nethunter support
If you wanted to reserve this one, though luck
Not often I get tagged in new kernel threads. All the best man, and happy holidays
A day were a new kernel project is starting is a good day...
Good work up to now...
Maybe UV would also be nice...
Good to hear about the new kernel. Awesome works!
I'm having with issue with the touch screen on my Z3 compact. The top and bottom of screen is unresponsive. But it happens on main screen, not in lock screen, not in welcome screen (when installed a fresh rom), and also not in TWRP.
I believe this related to the Sony' kernel. Could you help to investigate and hopefully fix the issue.
I will test the rom if hearing any word from you
Many thanks.
LoveTKB said:
Good to hear about the new kernel. Awesome works!
I'm having with issue with the touch screen on my Z3 compact. The top and bottom of screen is unresponsive. But it happens on main screen, not in lock screen, not in welcome screen (when installed a fresh rom), and also not in TWRP.
I believe this related to the Sony' kernel. Could you help to investigate and hopefully fix the issue.
I will test the rom if hearing any word from you
Many thanks.
Click to expand...
Click to collapse
Did I understood correctly, that you installed my kernel and such issue appeared? If yes: does the it exist on other kernels? I didn't modify anything in panel/screen/touchscreen. The only possible problem for now is that some kernel modules are not loaded. I must check which one is resonsible for what to decide whether to enable it or not or if it could be responsible for such issue (which I doubt).
What about your charger? In some cases broken chargers caused misbehaviour in touchscreen . For instance they are not properly grounded.
I need more information to help you.
Regards
Can someone please explain to me what are benefits of f2fs, and what does it mean? Are there any bad sides of using it?
-CRO-Maher said:
Can someone please explain to me what are benefits of f2fs, and what does it mean? Are there any bad sides of using it?
Click to expand...
Click to collapse
If you search on Google, you will find that f2fs is a filesystem developed by Samsung, faster than the others file systems(if used on emmc, SD card and ufs) so it'good if we could use it. But the kernel must have compatibility for it. Correct me if I'm wrong! And I'm looking forward using this kernel!
Sent from my D5803 using XDA-Developers mobile app
king960 said:
Did I understood correctly, that you installed my kernel and such issue appeared? If yes: does the it exist on other kernels? I didn't modify anything in panel/screen/touchscreen. The only possible problem for now is that some kernel modules are not loaded. I must check which one is resonsible for what to decide whether to enable it or not or if it could be responsible for such issue (which I doubt).
What about your charger? In some cases broken chargers caused misbehaviour in touchscreen . For instance they are not properly grounded.
I need more information to help you.
Regards
Click to expand...
Click to collapse
It's not from your kernel. It's issue on Sony's ROM, which causes top and bottom screen area is not touchable. I think it was the kernel issue. Some forks from the thread had the same of my issue: http://forum.xda-developers.com/z3-compact/help/home-button-t3151587
Many appreciates if you can figure out and have some fixes included in the kernel.
Thanks,
Cool! All the best developing this kernel. I will surely try this. BTW, do you see and performance and battery improvements in SliMM or AOXP?
panzerox123 said:
Cool! All the best developing this kernel. I will surely try this. BTW, do you see and performance and battery improvements in SliMM or AOXP?
Click to expand...
Click to collapse
Yes, both have better performance and battery life than stock.
PS. Version 2 released - codename Helium
king960 said:
Yes, both have better performance and battery life than stock.
PS. Version 2 released - codename Helium
Click to expand...
Click to collapse
Cool I'm developing AOXP... And 1.3 I will be releasing 1.3 now!
Also, how stable is the kernel?
This kernel Is awesome! It would be good if you added zen io, Adreno idler and dynamic fsync
frixed said:
This kernel Is awesome! It would be good if you added zen io, Adreno idler and dynamic fsync
Click to expand...
Click to collapse
Thank you, I will try to add these.
Can you make version for concept?
karol5wwy said:
Can you make version for concept?
Click to expand...
Click to collapse
Maybe I will consider it in the future. Now I would like to focus on stock based kernel and patching it.
I have a problem with my sd 64GB with this kernel i get a notification that says "corrupted sd card" i touch to format and fix but not work and my sd work with twrp :/ i use SLIMM 3.8
noob question could you tell me a good setup for running games without lag? I have problems in games like NFS no limits and RR3 in stock.
I tested another kernel only that always hangs up then I need to reboot.
Game always starts well only after a while drops to 15/20fps I'm almost changing smartphone. I've seen that is some limit that sony puts after a certain temperature thank you for help
frixed said:
I have a problem with my sd 64GB with this kernel i get a notification that says "corrupted sd card" i touch to format and fix but not work and my sd work with twrp :/ i use SLIMM 3.8
Click to expand...
Click to collapse
Hi, what is the filesystem of your sdcard?
Have you tried to format in TWRP or with help of PC?
zEminho said:
noob question could you tell me a good setup for running games without lag? I have problems in games like NFS no limits and RR3 in stock.
I tested another kernel only that always hangs up then I need to reboot.
Game always starts well only after a while drops to 15/20fps I'm almost changing smartphone. I've seen that is some limit that sony puts after a certain temperature thank you for help
Click to expand...
Click to collapse
Hi, after certain temperature a feature called CPU throttling is enabled. It's implemented by thermal driver to prevent damage to your phone. I haven't tried it in gaming but I read many positive opinions about intelli thermal driver which is included in my kernel.
I'll install that game and tell you how it works for me.
king960 said:
Hi, what is the filesystem of your sdcard?
Have you tried to format in TWRP or with help of PC?
Hi, after certain temperature a feature called CPU throttling is enabled. It's implemented by thermal driver to prevent damage to your phone. I haven't tried it in gaming but I read many positive opinions about intelli thermal driver which is included in my kernel.
I'll install that game and tell you how it works for me.
Click to expand...
Click to collapse
Hi, I use exfat, if I already try to format it in twrp but it does not work with the rom, in the pc it works, in twrp also and with another kernel also it works, it is kind of strange maybe it has something to do with format extfat
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kernel features:
Build with custom toolchain Linaro GCC 4.9.4 2017.01
Full -O2 build with device and target flags enhanced, linaro build improvements, etc
Less is more: stockish builds from BKL-L04 EMUI8.1.0.107 source drop
Systemless installer (doesn't touch system/vendor partition, OTA friendly)
Removed some debug and logging options
ARM enhanced performance and battery patches
CVE security patches, general upstream and miscellaneous fixes
Several CPU Governors (blu_active modded own governor by default - fastlane mode available!)
cpu-boost CAF driver ported for kirin with some added improvements (Dynamic Stune Boost included)
No OC, use 300HZ base timer frequency
Enhanced TCP methods (westwood is default), Network and Wifi tweaks and updated drivers
Several I/O control tweaks, added schedulers FIOPS and ZEN v2 is default, tweaked and upstreamed filesystems (F2FS, ExFAT, NTFS, CIFS & NFS) (WIP)
Removed verify and doesn't force encryption, patched SafetyNet flags to pass CTS (WIP)
Stock thermal driver by default
Optimized crypto routines (WIP)
Swap and ZRAM off by default
Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel an FPR) (WIP)
Graphic stack fixes and reworked GPU driver
USB Fast Charge (USB mode up to 900mA with MTP on)
Battery/Notification LED control (WIP)
FS fsync toggle on/off
Wakelock blockers available
zx2c4's wireguard support
CDROM emulation on mass_storage (compatible with DriveDroid 0.10.36+)
init.d support (put your scripts in /system/su.d or /su.su.d [systemless SuperSU], /magisk/.core/post-fs-data.d [Magisk])
Compatible with Kernel Adiutor and others
DOWNLOAD KERNEL ZIP (No mirrors please)
Warning: If you come from other kernel or have any issues, you should dirty flash your ROM before flashing blu_spark zip to avoid problems.
Reflash ROM -> if you want root flash SuperSU or Magisk (default, no plugins/modules) -> flash blu_spark.
If you are already rooted or upgrading between blu_spark versions, just flash the kernel zip. Also uninstall or clean data of any kernel control app you're using.
About bugs and troubleshoots: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock EMUI with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with modules, etc.
If you're using custom ROMs (including EMUI based ones) you're on your own. I'm only interested on debugging stuff in stock and stable EMUI.
Save the SOT and battery stats/screenshots for general threads, here we deal with development, not personal tastes and results.
Also don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" , no OT about OTAs, apps, ROM bugs, Recovery/TWRP troubleshoots and other userspace stuff. There's threads for it, use them.
Going back to stock: This kernel installer doesn't change your filesystem (systemless).
You can backup your ramdisk.img and kernel.img with TWRP before flashing blu_spark if you want to go back to full stock or just dirty flash your full ROM.
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free
Honor View 10 development unit donated by Honor USA. Big shouts to them
Special thanks to @[email protected]_USA for being such a supportive person.
XDA:DevDB Information
blu_spark kernel for Honor View 10, Kernel for the Honor View 10
Contributors
eng.stk
Source Code: https://github.com/engstk/view10
Kernel Special Features: Powered by sparky
Version Information
Status: Stable
Current Stable Version: r16
Stable Release Date: 2018-05-31
Current Beta Version: r8
Beta Release Date: 2018-04-30
Created 2018-04-29
Last Updated 2019-11-29
blu_spark r8
All right crew!
blu_spark has made to Honor View 10!
First build is up :highfive:
Lot's of stuff merged in, we now have a nice and stable baseline to work with.
More of the usual missing goodies to come in future builds :fingers-crossed:
It was tested in L04 model with latest EMUI 8.1.0.105 so any other FW your results may vary.
To install you must use TWRP, @Pretoriano80 Unofficial TWRP is recommended.
You must have stock (or rooted) ramdisk and kernel before install.
blu_spark_r8-view10_66f0c4b.zip
build: use Linaro GCC 4.9.4-2017.01 for now
First kernel build with too much stuff to talk about, check git
ramdisk and installer changes to match View 10 stuff
Click to expand...
Click to collapse
Keep it real, keep it true, keep it blu :highfive:
Keep in mind: I will give no active support for custom ROMs (including EMUI based ones).
Meaning, if using anything besides stock and stable EMUI don't bother posting about it.
I am only interested on debugging stuff in stock and stable EMUI (with logs and reproducible steps to replicate the issue).
Don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.
Also don't go spam and bug reporting on ROM threads if using this.
No mirrors please
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free
nice glad to see linaro gcc was usable and was just something odd in my end... lol
for some odd reason on ubertc was usable as gcc fir me...
Nice job....
Does this support changing charging rate in KA?
Can i install this on BKL-L09 model?
kevp75 said:
nice glad to see linaro gcc was usable and was just something odd in my end... lol
for some odd reason on ubertc was usable as gcc fir me...
Click to expand...
Click to collapse
Yeah well try to check if you have any cruft or leftovers derping, I encountered similar situation when building.
venreddy said:
Nice job....
Does this support changing charging rate in KA?
Can i install this on BKL-L09 model?
Click to expand...
Click to collapse
No charge changes at the moment.
If fw is 8.1 should work, otherwise I don't know. Backup, try and let us know.
Sent from my blu_spark'd Honor View 10
eng.stk said:
Yeah well try to check if you have any cruft or leftovers derping, I encountered similar situation when building.
Click to expand...
Click to collapse
yeah, thought that too... did the same on fresh source download too tho
Got it to compile using Uber TC tho, so maybe I'll run with it and see what I can break LOL :laugh:
Woot
eng.stk said:
No charge changes at the moment.
If fw is 8.1 should work, otherwise I don't know. Backup, try and let us know.
Sent from my blu_spark'd Honor View 10
Click to expand...
Click to collapse
BKL-L09 is still with 8.0 emui.
I doubt this will work, but will try this later. It would not brick my phone right? Just need to back up stock kernel and fish it, if phone doesn't boot then flash backedup kernel. Right?
venreddy said:
BKL-L09 is still with 8.0 emui.
I doubt this will work, but will try this later. It would not brick my phone right? Just need to back up stock kernel and fish it, if phone doesn't boot then flash backedup kernel. Right?
Click to expand...
Click to collapse
backup both kernel and ramdisk
Rommco05 said:
Not bootnig on L09 LOS, stock kernel L04 don't boot too
Click to expand...
Click to collapse
fastboot flash your stock kernel.img and ramdisk.img
Rommco05 said:
Not bootnig on L09 LOS, stock kernel L04 don't boot too
edit: just telling
Click to expand...
Click to collapse
Thanks for testing. Hope Honor updates all the phones from all regions to Android 8.1 besides L04 devices :fingers-crossed:
Fragmentation is never good...
can i flash on BLA-L29 with emui 8 oreo 8.0?
fatalynx said:
can i flash on BLA-L29 with emui 8 oreo 8.0?
Click to expand...
Click to collapse
backup your ramdisk.img and kernel.img and tell us
(note, if you read the thread a little [like the couple posts above you], you'd see that it really only works on the US version, but, do what you want....)
Try to enable bonding mode inside defconfig, most of the new wifi driver support this option
scafroglia93 said:
Try to enable bonding mode inside defconfig, most of the new wifi driver support this option
Click to expand...
Click to collapse
I can checknit out, but some OEM don't enable that on 2.4G because it can introducr wifi issues with some APs.
Sent from my blu_spark'd Honor View 10
kevp75 said:
backup your ramdisk.img and kernel.img and tell us
(note, if you read the thread a little [like the couple posts above you], you'd see that it really only works on the US version, but, do what you want....)
Click to expand...
Click to collapse
will give it a shoot tq btw..
kevp75 said:
yeah, thought that too... did the same on fresh source download too tho
Got it to compile using Uber TC tho, so maybe I'll run with it and see what I can break LOL :laugh:
Click to expand...
Click to collapse
cross-compile is hardcoded in tzdriver/Makefile and will only use aarch64-linux-android-
https://github.com/UchihaDev/HyperPlus/commit/f04adc459eb60bcc1e22158ef6ae834e24929232
ajituchiha said:
cross-compile is hardcoded in tzdriver/Makefile and will only use aarch64-linux-android-
https://github.com/UchihaDev/HyperPlus/commit/f04adc459eb60bcc1e22158ef6ae834e24929232
Click to expand...
Click to collapse
Appreciate it mate.
Thanks for helping the noob compiler lol
fatalynx said:
will give it a shoot tq btw..
Click to expand...
Click to collapse
And already failed??
Sent from my HUAWEI BLA-L29 using XDA Labs
Tried on bkl-al20, cannot enter tne system.