Updated on 02/06/2015:
Version 1.2 Release
-Fixed Voltage Setting
-Optimized crypto AES, SHA1,SHA256,SHA512
-Optimized memcpy for Krait/Cortex-A15
-exFAT 1.2.5
-etc.
ZIP file here:
https://drive.google.com/open?id=0B1...RjQ&authuser=0
github: https://github.com/nunogia/Z7Max_NX505J_H129_kernel
Version 1.1 Release
Release Notes:
-F2FS: New updated Sources;
-NEON VPF Optimization;
-CPU: Overclocking to 2.7Ghz - new 2 steps;
-GPU: Overclocking to 640Mhz - new 2 steps;
-GPU: Underclocking to 100Mhz - 1 new step;
-Build optimizations with Cortex-A15 flags;
-Mount: Default to NoAtime,NoDirAtime instead Relatime;
-Voltage Control: using TricksterMOD (p.e);
-IO Sched: New IO schedulers - BFQ, ZEN, VR, SIO;
-Some Thermal optimization to comply with OC;
You can found it in here: https://drive.google.com/file/d/0B1u...ew?usp=sharing
[Kernel] - Only tested with KK Stock Rom 1.64 !
Good afternoon!
After many time of running with me head against the wall, I am glad to be able to deliver the first real version of my modified kernel with F2FS.
After some help from @paolothlw8 on the initial stage, and with study of multiple git's from other devices, specifically from Dorimanx to G2, AK-Kernel and UBER-N5, i was able to get our Nubia Z7 Max to work with F2FS.
At this stage, to get this to work, modded recovery (TWRP) and Kernel (with modules installed to system - thanks again @paolothlw8) must be flashed.
I warn you all that this can be risky, i am not responsible if problems occur, but i will try to provide the safest procedure that i follow.
Needed:
- Stock TWRP recovery with EXT4 partitions;
- My 2 zip files on SDCard (Internal or External) - NX505J-NGIAKernelV1.0-F2FS-DC.zip and TWRPNGIA-F2FS-Fixed.zip .
The procedure:
1 - On your stock TWRP recovery make a full backup, then you will always be able to revert;
2 - After Backup, install my modded TWRP ("TWRPNGIA-F2FS-Fixed.zip");
3 - Reboot again to new Recovery;
4 - On new recovery can appear "can't mount /data" , no problem it's normal;
5 - Go to "Wipe", "Advanced Wipe", select "Data" and then press "FS Options";
6 - Then "Change FS", select "F2FS" and swipe to format partition;
7 - Repeat steps 5-6 but selecting "Cache";
8 - Go back to main menu of TWRP, and go to settings(right upper corner) and pick "Use rm -rf instead of formatting" - Make sure is picked! Otherwise on restore it will format back again to EXT4;
9 - Now, all set to restore Data - Go to "Restore" , select your last Backup (made on step 1), select ONLY "Data" (confirm with scroll), and proceed with restore;
10 - Done Restoring;
11 - Now time to flash "NX505J-NGIAKernelV1.0-F2FS-DC.zip" ;
12 - If all suceeded, you can now restart System and enjoy!
PS: If during normal use some FC's found, try wipe "Dalvik cache, Android Secure, Cache" and restart again.
Find the necessary zip files here:
https://drive.google.com/open?id=0B1...R2s&authuser=0
Thank You All!
ITA Translate:
[Kernel] - Only tested with KK Stock Rom 1.64 !
Buon pomeriggio!
Dopo molti tempo di correre con me testa contro il muro, sono felice di essere in grado di consegnare la prima versione reale del mio kernel modificato con F2FS.
Dopo un po 'di aiuto da @ paolothlw8 concernente la prima fase, e con lo studio di git più di altri dispositivi, in particolare da Dorimanx a G2, AK-kernel e UBER-N5, sono stato in grado di ottenere il nostro Nubia Z7 Max lavorare con F2FS.
A questo punto, per ottenere questo al lavoro, recupero modded (TWRP) e Kernel (con moduli installati al sistema - grazie ancora @ paolothlw8) deve essere balenato.
Vi avverto tutto ciò che questo può essere rischioso, io non sono responsabile in caso di problemi, ma cercherò di fornire la procedura più sicura che seguo.
Necessario:
- Recupero della TWRP con partizioni EXT4;
- I miei 2 file zip su SDCard (interno o esterno) - NX505J-NGIAKernelV1.0-F2FS-DC.zip e TWRPNGIA-F2FS-Fixed.zip.
La procedura:
1 - Sul recupero magazzino TWRP fare un backup completo, allora si sarà sempre in grado di tornare;
2 - dopo il backup, installare il mio TWRP modded ("TWRPNGIA-F2FS-Fixed.zip");
3 - Riavviare nuovo per nuovo recupero;
4 - Il nuovo recupero può apparire "non può montare / dati", nessun problema è normale;
5 - Vai su "Wipe", "Wipe Avanzate", selezionare "Data" e quindi premere "Opzioni FS";
6 - Allora "Change FS", selezionare "F2FS" e scorri per formattare la partizione;
7 - Ripetere i passaggi 5-6, ma selezionando "Cache";
8 - tornare al menu principale di TWRP, e andare alle impostazioni (in alto a destra) e raccogliere "Usa rm -rf invece di formattazione" - Accertarsi che viene raccolto! In caso contrario, il ripristino sarà formato di nuovo a EXT4;
9 - Ora, tutto pronto per il ripristino dei dati - Vai su "Ripristina", selezionate il vostro ultimo backup (fatta nel passaggio 1), selezionare solo "dati" (confermare con scorrimento), e procedere con il ripristino;
10 - Fatto Ripristino;
11 - Ora il tempo a lampeggiare "NX505J-NGIAKernelV1.0-F2FS-DC.zip";
12 - Se tutto suceeded, è ora possibile riavviare il sistema e buon divertimento!
PS: Se alcune FC ha trovato durante il normale utilizzo, provare pulire "la cache Dalvik, Android sicuro, Cache" e riavviare.
Trovare i file zip necessari qui:
https://drive.google.com/open?id=0B1...R2s&authuser=0
Grazie A Tutti!
[Kernel] Z7 Max Kernel - NGIA - F2FS Data and Cache
Visualizzazione stampabile
-
26-05-15, 17:50nuno169[Kernel] Z7 Max Kernel - NGIA - F2FS Data and Cache
-
26-05-15, 18:57nuno169Tests - Before and After
Androbench:
EXT4:
Allegato 143986
F2FS:
Allegato 143987
A1 SD Bench:
Comparison exfat (Internal SDCard) vs F2FS (Internal Memory):
Allegato 143988
With EXT4 was getting R:138Mb/s W:38Mb/s
DiskInfo:
Allegato 143989 -
29-05-15, 13:59nesquix
not working here. after wiping data and cache partition to F2FS, the recovery (the new one) say all time unable to mount /data and /cache, like he can't read the partition. impossible to restore the /data partition from the backup to the F2FS parition who is not "readable" by the recovery modded. so i was forced to uncheck "-rm" from the setting and i'm now restoring the data in ext4 format.
strange....
i tried 3 times
i'm on BB72 1.64 kitkat, old parition setup, with expanded partition for app (6go)
Quote:
Originariamente inviato da nuno169
-
29-05-15, 14:04nuno169
Hi!
Are you sure you are on the new recovery?
I have only faced "Can't mount /cache" on other recoveries, when /cache with F2FS.
Make sure you are on the new recovery. Then make sure you format /data and /cache to F2FS (without -rm selected!) , then yes select -rm and then restore your data. -
29-05-15, 14:39nesquix
ok i'm trying again in direct live.
I have my backup on my external SD card, so :
1. i flash again your recovery right now (TWRPF2FS.zip)
- Flash ok, i reboot again in recovery....
2. now i go to Wipe, Advanced Wipe, i select only DATA (by the way because of all this manipulation before i have 2 DATA and 2 CACHE on the partition selection in TWRP, like a double but with the same mount point "/data" in both cases, and "/cache" for cache partition..), it was not here before trying your tutorial, anyway, i tried booting again on the rom with all formated and restored in ext4 and all is working great so don't worry about that, just strange.
so i go to wipe, advanced wipe, i select the data partition (bc there are the same..xD), i go to FS options, Change FS, i choose F2FS, and i swipe to change.
The recovery log say :
Updating partition details...
Unable to mont "/data"
Unable to mont "/data"
done...
I wipe my cache partition too now,.. i go to Wipe, advanced wipe, change FS, i choose F2FS, i swipe to change...same things.
Formating cache using mkfs. f2fs, done.
Formating cache using mkfs. f2fs, done.
Updating partition details...
Unable to mount /cache
Unable to mount /data
Unable to mount cache
Unable to mount /data
so .. of course i will not be able to restore anything on the data partition if i can't read it. but i'm ready to play the game. i go to settings, use rm -f, i go back and try to restore only the data of my working backup :
"Error : Unable tu mount /data"
sooo...... something strange is when i go to Advanced Wipe again, i go on the /data partition, the recovery say that the current file system is ext4, no F2FS... ok i try to wipe it again in F2FS....
Error, Unable to mount /cache, / data , /cache , /data ... done
strange because the cache partition is on F2FS, say the recovery.
ok i reboot in recovery again, and untick the "rm -f" from the setting, format data and cache partition to ext4 like it was before... (working, no error with partition now like "unable to mount /something"
and i can restore my /data partition, in ext4 without any problems.
here my experience bro. -
29-05-15, 15:15nuno169
Ok,
Maybe i uploaded wrong TWRP. I will check right away. Thank you! -
29-05-15, 15:18nesquixOK, tell me when you uploaded the good one. I will try againQuote:
Originariamente inviato da nuno169
-
29-05-15, 15:37nuno169
Yes i uploaded wrong version. Sorry about time wasted!
Here is the right version:
https://drive.google.com/file/d/0B1u...ew?usp=sharing
Tested!
Thanks again @nesquix! -
29-05-15, 16:08nuno169
PS: If during normal use some FC's found, try wipe "Dalvik cache, Android Secure, Cache" and restart again.
-
29-05-15, 18:15nesquixeverthing is perfect now! thanks for the work and sharing =)Quote:
Originariamente inviato da nuno169
question : why not converting all partition to F2FS ? system for exemple, not only data/cache ?
it will run faster, no ? i just have to wipe/convert to F2FS, install the 1.64 rom, and flash your kernel ...yes?
and why not modding a little bit the kernel to do some OC/UC, some new governor and so on.... ? -
29-05-15, 19:10nuno169
Honestly didn't tried to convert /system because usually there are some problems, and no gains will come from that except maybe boot time. /system partition after boot is a Read-Only partition. However i could try to convert later.
Installing any rom without modification will probably format /data and /cache to EXT4. You can install and then you have to format again to F2FS (without -rm option).
This Kernel will (probably) work only on stock roms, it was tested only with 1.64 version.
I will release a new version right away. I have some improvements implemented, including OC/UC and new IO Schedulers. -
30-05-15, 00:57nesquix
OK ! so I will not change the system for f2fs now. let me know about the new kernel! everything is working good now. thanks!
-
30-05-15, 01:03nuno169
Its on the first post the new release. Many improvements.
To change system to f2fs ramdisk must be changed. Do not try because it will fail. -
30-05-15, 01:07nesquix
you are amazing man. what app do you recommend me to fine tune the CPU?
-
30-05-15, 02:21nuno169
I use trikster mod :)
-
30-05-15, 09:19nesquixi hope you uploaded the right kernel now :-P, because when i set the GPU to the max frequency for exemple,with TricksterMOD, he always stuck at 100mhz. and i can't see 100mhz on the CPU mini freq, but only 300.Quote:
Originariamente inviato da nuno169
i don"t like this application for modding the kernel so much, you should try a free alternative with a better UI, more updated and with more free features. go on the play store and install "Kernel Audiutor"
something strange is too is that Antutu always crash with OC
what setting do you recommand?
mine are :
CPU / min 300 max 2726mhz
governor interactive
gpu governor msm_adreno
gpu max frequency 6
mp decision off
the GPU max frequency is s et to -1053mhz by default on the app, WTF ? lol, so i set it to 640mhz.
the gpu governor, i let msm-adreno-tz
E/S setting,i set the scheduler on "sio"
i set the buffer to 4096ko (for internal storage and external, with "sio" too)
with that antutu crash again :P -
30-05-15, 09:19manuelb
Grande nuno bravo!!!!
Sai percado se ci sono in giro i sorgenti della lollipop stock nubia ?? Li ho cercati ma senza risultati molto probabilmente nubia non ha rilasciato nulla ancora.
Inviato dal mio NX505J usando Androidiani App -
30-05-15, 11:55nuno169Yes its the right file this time :pQuote:
Originariamente inviato da nesquix
You should set on your OC frequencies voltage +25 and it should not crash. Mine dont needed but it varies from phone to phone.
CPU has just OC not UC. 100mhz is on GPU. -
30-05-15, 11:56nuno169Hi manuelb! I didnt find lollipop sources too. I think it has not been released :(Quote:
Originariamente inviato da manuelb
-
02-06-15, 19:59nuno169
New release on first post.
@nesquix all your bugs fixed. -
03-06-15, 18:40nesquixthanks you sir ! i will flash it nowQuote:
Originariamente inviato da nuno169
-
05-06-15, 12:22PaoloW8bravo, alla fine sei riuscito ! :)Quote:
Originariamente inviato da nuno169
volevo solo avvertire che nubia ha rilasciato i sorgenti del kernel lollipop sia del mini che del max un'oretta fa
z7max_lollipop_source
z7mini_lollipop_source -
05-06-15, 12:23manuelbottimoooooQuote:
Originariamente inviato da paolothlw8
-
05-06-15, 12:29nuno169
@ paolothlw8
Si l'ho fatto! Ho dovuto fare alcune soluzioni a causa di moduli WLAN e TEXFAT, come non ho dovuto fonti ... per rispettare Module.Symversion generato ... Ma io non ho nel mio github.
A proposito di lollipop ... Eccellente!
Inizierò a lavorare su di esso presto. Vuoi fare lo stesso? Forse potremmo unire un po 'di lavoro! -
05-06-15, 12:32manuelbsei tornato paolo o ci lasci nuovamente?Quote:
Originariamente inviato da paolothlw8
-
05-06-15, 15:05PaoloW8io per il modulo wlan.ko usavo semplicemente quello compilato da nubia e funzionava senza problemi mentre tutti gli altri moduli li compilavo ioQuote:
Originariamente inviato da nuno169
per fare una cosa ben fatta bisognerebbe integrare il modulo "prima" prendendolo da codeaurora (https://www.codeaurora.org/projects/...jects/msm-wlan)
per il kernel lollipop...mi spiace ma non credo di lavorarci su per il momento, non ho ne la voglia ne il tempo
no non sono tornatoQuote:
Originariamente inviato da manuelb
-
05-06-15, 18:17pesa1234Mi dispiace...Quote:
Originariamente inviato da paolothlw8
