yashsingh1/xdaforums huggingface dataset:
[Meizu MX] Moyster:
you can also make a new twrp backup, and copy/paste the files from the old backup to the new backup ;)
[Meizu MX] jack6666:
F2fs working perfectly for me, thanks so much!!! :) ;)

Inviato dal mio M2 Note utilizzando Tapatalk
[Meizu MX] Carron:
I don't know format in new recovery ext4 take a long time, I thought is a bug and I decided trun off the phone and when I reboot in to the recovery fail all time and then I dicide install the old recovery and format all to ext4 and after this I reinstall the rom, install the new recovery and format cache and data to f2fs and reboot the phone now is all good an very faster thank you Moyster.

Is everything okay after doing this? [MENTION=7685540]Moyster[/MENTION]
[Meizu MX] stryker09:
Hi guys! I've been following this for a good while now but was most I trigued by f2fs support, is the difference noticeable vs ext4? I also saw ext4 got a bunch of updates that may have brought it up to par though

Thanks in advance!!
[Meizu MX] Blouw73:
Is someone managed to get the root on RC3 build ? Trying both SuperSU and Magisk method on fresh install, no one works for me :/ Maybe I'm missing something ?

Thanks for your work
[Meizu MX] numpea:
maybe you missed that Magisk need to be installed from playstore too in order to use it, and supersu make sure you are using the last one and when you boot the phone start supersu app and install su binary

don't forget that after you flash a boot.img you need to reflash magisk.zip or supersu.zip to get root
[Meizu MX] Gargarospo:
I've always flashed the zip downloadable from https://download.chainfire.eu/1001/SuperSU and it always worked for me, since Beta 1.
[Meizu MX] numpea:
i used f2fs before ext4 updates and i got a huge difference

than moyster updated ext4 and got even high score without f2fs

and using f2fs with the updated ext4 has an even better score

if you want you can try go back to ext4 and benchmark it no one knows ;)
[Meizu MX] Bang Thien Minh:
hello! can you guide teach me flash new kernel and flash new Recovery of Moyster?

I dont unsterstand this method between ext and f2fs! helpme ! !! :highfive:
[Meizu MX] numpea:
Me and Moyster have already writed a tutorial on how to do that few pages ago

post 886

post 873
[Meizu MX] n0p3zz:
Newest supersu 2.81 doesnt work for some reason,it fails while modifing kerbel in flashing process.Download 2.79 version and it will work.
[Meizu MX] Gargarospo:
In fact, one can download a flashable zip of SuperSU version 2.78 from the page I've previously linked. That's why it always worked for me, I guess. :)
[Meizu MX] Bang Thien Minh:
Mean is after converted from ext4 to f2fs, continued flash file zip Build RC3? that's right? :D

---------- Post added at 04:11 PM ---------- Previous post was at 04:08 PM ----------

[MENTION=7685540]Moyster[/MENTION]! if i already cut my data saved in Internal storaged, can i skip method back data in recovery?

thank
[Meizu MX] numpea:
yes you can flash RC3 and you need also to flash the new boot of memory fix it's in dowload section

make sur you do backup and copy all the content of internal storage into pc ou in an external sdcard
[Meizu MX] Carron:
I don't know format in new recovery ext4 take a long time, I thought is a bug and I decided trun off the phone and when I reboot in to the recovery fail all time and then I dicide install the old recovery and format all to ext4 and after this I reinstall the rom, install the new recovery and format cache and data to f2fs and reboot the phone now is all good.

Is everything okay after doing this? [MENTION=6520775]numpea[/MENTION]
[Meizu MX] trinsic:
Wow there is a visible difference in speed! I like it, thanks Moyster! I love how this phone still feels great to use after two years, having nearly given up on it I love it more than ever.

Using RC3 with the hotfix I did lose root but I suspect this is either user error or can be fixed with RC4 :) If I flash Magisk I lose the hotfix.

Thanks again.
[Meizu MX] Pcti888:
While use some apps(map inside), the mobile signal lost. this is a system bug ,or apps bug? these apps in other 7.1.2 los are ok. i always flash system after all wipes. This situation arises from build 1 to rc3. i have to give up this perfect system. Can somebody have this problems? give me some solutions .Thank you very much..:victory::victory::victory:
[Meizu MX] arunshand:
Really great share... Thanks man.. Works great
[Meizu MX] kupina:
Nvram error

Can someone help me how to fix nvram warning:err = 0x02? On beta 6 and 5 i dont get this. I try f2fs its work very well.Rom works preaty smooth and no bugs.. Thanks for replay. Sorry for my bad English im from Serbia.:)
[Meizu MX] Bang Thien Minh:
[MENTION=7685540]Moyster[/MENTION] [MENTION=6520775]numpea[/MENTION]

F2fs working perfect! Rapid speed and quickly!

Antutu benchmark 5800 for IO

and this BUild 13 need flash BLOOD-r7.0 to fix crash?
[Meizu MX] Moyster:
Usually people with your symptoms needs a clean wipe and/or simply cleaning dalvik-cache AND the app(s)'s data. Do backups, take your time ;)

Nvram errors like that are wierd, you should restore a previous nvram backups.

What crash ? Also, Blood kernels won't change much, it's just my kernel base + extra schedulers/governors + outdated code ( like varunchitre15's hotplug from mt65xx (sprout device), or enabling ntfs/exfat kernel drivers (really old and bad) when lineage uses FUSE to support exfat/ntfs and other "exotic/licenced" FileSystems.). I used to help him, give him tips (and stopped when he started taking confidence, insulting and harassing me), because he's obviously learning on his own and trying things to make his opinion, at some point he was shipping kernels with "overclock" and "fastcharge", using code that is not properly working or that he understands, which means y'all blood users could lose your device from one "version" to another. at this point, it's not "beta", it's totally "at your own risk alpha-preview" but just saying that (from my point of view) will probably causes some tears to be shed :P

Anyway new kernel update : RC3-memfix-boot.V12.img

Changelog :

[net] ipv4 & ipv6 had some extra latency due to wierd netfiler rules, the cleanup made internet faster ! (Like Intel :D)

[kernel] switched from config_hz=100 to config_hz=300, shouldn't make much difference, but battery life might be better now

[CVEs] as always, I might not have covered "all of the known CVEs", but here's s'moar fixed CVEs ;)

[stability] reverted -O3 compile flag that might end up compiling slower/longer code, linux kernel don't really benefit compiler optimisations as the part of code that do heavy computation usually is optimised using assembler.

Feedbacks on internet reactivity / speed is welcomed, I got latency from 80ms avg (ping / ping6 www.google.fr), got it down to ~25ms avg, overall the PlayStore and any browser seems to be more reactive ;)
[Meizu MX] Bang Thien Minh:
yes! i know! [MENTION=7685540]Moyster[/MENTION]! Hope you skip some one and try to developing this ROM

and You will to plant mod Resurrection Remix in the future?
[Meizu MX] pedgsilva:
This v12 is to flash where ? i've flashed in image / boot and the phone is dead now !
[Meizu MX] Moyster:
boot.img goes to the boot partition, boot.img = boot image, it's an image of the boot partition.

It can't brick your phone, boot.img is not used to boot recovery, boot recovery holding the combo keys and restore a backup or reflash properly whatever you did wrong.

Last but not least, if you're not sure of what you're doing, don't ;) or do it with caution, I can't count the number of other posts like yours I answered, just because people did not care.

Meizu m2 note is an android phone, like any other device, with a recovery, a boot partition, system, data, cache...

If that's your first device, then you have plenty of resources available to learn not to do mistakes, if that's not your first android modded phone, then it's like any other devices,

it doesn't prevent user mistakes
[Meizu MX] pedgsilva:
Moyster this is my 5th android device, always mediatek, i asumed that it was the boot, because of the name, of course.

This is the second time in two days that my phone is a paperweight. Now i have to wait the batery is on 0 to try flash the original rom again. this error ocurs every time i flash the boot.

If my phone come back to life i will install only the recovery and the rom.

Any problem with that ?

Thanks
[Meizu MX] Moyster:
sounds wierd, I'll give a try again, but that's legit wierd, if kernel changes are bad, it would just stop at the "meizu boot logo".

edit: downloaded from xda, copy/paste as is on my internal storage, twrp > install img > xyz.img > boot > flash > reboot to system.

This is really wierd, I read previously someone had your exact problem and fixed it (i don't remember how, but it's written somewhere :D)

The power button is linked to the electrical circuitery in our phone, if you hold it long enough, it will reboot, not sure if you should feel a small vib or not, but at some point you should feel like the phone did stop/reboot, and that's the moment when you need to press volUP as well, so it boots up to recovery. It took me some times to get the timing right, but it's best than waiting for the battery outage.

edit2: you can flash recovery and rom again, but the boot.img I included is fine, so if your problem happens again, you might want to restore flyme stock rom using the spft flashtool (to make sure it cleaned/recreated/reformated any partitions in the correct size).
[Meizu MX] AlexLartsev19:
You now sound like offended girl.

First, about your kernel I can say the same thing, namely : "This is just a base kernel from Meizu + some features from your friends MAD + practices of other developers(some are posted without any credits) . To break the phone using BLOOD may be no more than your rom. And to put it I don't force anyone.

Secondly, now look at you. You're too selfish. And if you weren't, then many users could benefit not only your lineageos, but such firmware as RR, PA, MoKee and other
[Meizu MX] Moyster:
So, tell me, did you have access to everything including patches since last September ? You only motivates yourself when I revoke your access to it ? :/

The only reason you wanted to build RR or any rom is because I finally could solve the camera issue. There it is... after telling me you were lazy and not doing anything?

You're actively kanging, insulting me, you and your "friend(s)", begging for things they don't show any sign of respects.

Your kernel is just that, I never said you were forcing anyone, I'm getting asked if "your" kernel fixes crashes, how can it fixes things ? Now, once again, read again, I said your kernel was "risky" and that you were learning, bear with me, it's the truth, it's not insulting. And I just said I stopped caring/trying to help because you never was able to show respect.

Funny thing is, if you just tried to boot nougat, you probably would already have some "custom roms", but no, you're insulting me, AND thinking I OWE YOU, rofl.

You didn't get anything because you didn't deserve it. SIMPLE.

Now let's talk about you, since you're cleaning the laundry here :

https://github.com/Moyster/android_...6991b711c55ad288c4df8e#commitcomment-21821901

Have a nice day you hateful homophobic retarded useless **** ;)
[Meizu MX] ivanovusa:
Moyster

Hi,will there be support for oms substratum,you can answer like a man,Yes or no?!I need a clear answer,it's important to me!A lot of users on another forum crave it,I asked you this question,but as always you pretend you have a crown.And it's not an insult,but an emotional speech:confused::confused::confused::confused::confused::confused::confused::confused:
[Meizu MX] AlexLartsev19:
The reason my friends(not me) wanted to collect PP - huge customization and more stable than in the linos.Yes, I'm lazy and don't deny it.

Really? And the evidence of my changing?

Next, my kernel does not fix any craches. It simply does not lead to them. And all because I'm testing my kernel, not as you release firmware that freezes if you run more than 4 applications, and then after 4 day release - with the corrections. (Oh yeah, I know what leads to these crashes).

And respect, my dear, must be earned. And about what you owe me, I never wrote.

LOL, you keep all the posts/links where you hurt? Oh, you poor, come i was regret you :D
[Meizu MX] numpea:
If you have followed the thread correctly you will know that few pages back he already said that : "if lineage is not going to add OMS he is not going to add support for it" :good:
[Meizu MX] pedgsilva:
All is working now without yhe boot patch, one very starge thing is in the wireless list of networks apears NVRAM warning: Err=0x10, it connects to all networks
[Meizu MX] faffu41:
Post bugs on the gitub section...

---------- Post added at 08:47 AM ---------- Previous post was at 08:43 AM ----------

Sorry if i'm introducing in this fight but you shouldnt demand things that have been granted to you... All of this fight is pointless... Thanks to him you Can boot Nougat and MM... You can't tell him he is selfish because no One is paying him for his job... He is doing all of these as a favor...stop demanding as a 4 yrs old boy...

---------- Post added at 09:06 AM ---------- Previous post was at 08:47 AM ----------

Btw security patch is May 2017, not april 2017 as you wrote...
[Meizu MX] jack6666:
Hey, the new kernel working perfectly, unfortunately my connection it does not allow me to test the patch introduced. Thanks!!!!!!! :)

Inviato dal mio M2 Note utilizzando Tapatalk
[Meizu MX] coderzs:
[MENTION=7685540]Moyster[/MENTION] , first of all thanks for this rom .

Its possible to bringup 3.18 kernel to this device , as i know walter97 has ported it to elephone p8000

https://github.com/walter79/android_kernel_elephone_p8000-3.18

And why you didnt bringup official los?
[Meizu MX] Pcti888:
Thank you again. I do someting about what you said. it didt work .but i will do it again.:svetius:svetius:::svetius:
[Meizu MX] Laungr:
Root Permission

WHY I can't get root Permission?

After I turned on Developer mode, "Root Access" couldn't be found, and "Manage Root Access" was gray, which meant available.

So can Anyone help me? Many Thanks~
[Meizu MX] :
SR3-SuperSU-v2.79-SR3-20170114223742.zip

Even i lost Root Access when I flashed the newer versions of Supersu.. Soo flash the above given versions of su zip file..
[Meizu MX] goodoane:
SuperSU 2.82 working well. Get the last flashing zip and you will be fine.
[Meizu MX] navdeep001:
i have a problem.when i revert to flyme from any custom rom ,my phone always dead. i have to flash preloader and secro files to alive my phone. this happens even i change flyme verson to another flyme vrsn with stock recovery
[Meizu MX] Gargarospo:
It sounds to me that you already found the solution of your problem. Reading your words, I'd infer (and I would't be surprised at all if I was right) that original Flyme ROM's need a device with original locked bootloader to work (maybe I'm wrong, but I wouldn't be surprised if I was right).

That said, since it's a problem you have with Flyme, I suggest you to ask your questions in a different place, surely not in threads regarding custom ROM's.

Good luck with FlyMe, I keep stuck to Moyster's LineageOS.
[Meizu MX] navdeep001:
i changed roms severel times after bootloader unlocked. never faced any problem like this before

i love los by moyster . but some cemera reasons i have to switch flyme again
[Meizu MX] numpea:
In fact you could reflash flyme and locking the bootloader

To do that you need flyme recovery from flyme 4 and update.zip of flyme 4 there is a thread on how to do that in the forum

The probleme occurs because we use flyme 4 files ( preloader and secro and lk ) to unlock the device and flashing flyme 6 or 5 with old preloader and secro and lk will brick the phone until you re-unlock it again

And you're not on the right place ;)
[Meizu MX] numpea:
if this other rom support f2fs you don't need to format again

in case of flyme it doesn't support f2fs that what i know and you need to go back to ext4
[Meizu MX] Moyster:
Celebrating a bit late Thomas Pesquet and Oleg Novitski safe return to earth, here comes our own "proxima" :)

Download

:

Build 14 (RC 4 "Proxima") : Here

Changelog :

[camera] fixed a couple bugs, exposure, white-balance, brightness/contrast settings should work properly, better picture quality (still missing HDR, for reasons)

[video-recorder] fix a bug where recording with the flash on crashed, video recording is not extra dark anymore

[netd] properly supporting firewalls / iptables rules / per app restrictions :highfive:

[kernel] netfilter rules cleaned, less latency, now using "cubic" as tcp congestion algorithm (faster internet)

[kernel²] includes every modifications/fixes done during the "kernel tests release" (memory management fixed, ext4&f2fs security&performance update, optimised FS mount flags (incl. lazytime))

[lineage] rebased sources as of today "5 june 2017" ~3pm

[misc] small cleanups/improvements

Enjoy ;)
[Meizu MX] Moyster:
All-in-one, like a normal rom ( I even deleted the "old" separate kernels boot.img from the download section) ;)

@ The comment above, flashing from lineage --> flyme will need you to wipe data & cache anyway, so formatting to f2fs or not, you cannot 'not wipe' during an OS change.

edit: hotfix for hotspot :

edit build.prop, find "wifi.tethering.interface=ap0", replace

ap

0 by

wlan

0, save and reboot.
[Meizu MX] Carron:
I need help, I try to do a clean install but when I format all the new recovery say me filed mount /system can you help me now I can't do nothing. [MENTION=7685540]Moyster[/MENTION]
[Meizu MX] xraitor:
Camera not working.
[Meizu MX] Sanjikun22:
failed to flash Nougat Base Gapps package for 7.1.2 (arm64) with error 7 and camera not working
[Meizu MX] korcio86:
Hi,

I had the same problem with gapps. I have solved it by flashing pico opengapps for Android 7.1 Arm64 (opengapps.org). I hope that it will work for you as well.

Cheers!
[Meizu MX] Pcti888:
if you search this code on google , you will find that error7 means system part is not enough to install this package. the camera problem, you can search in this therad , someone said one solution. enjoy it.
[Meizu MX] arunshand:
I am also facing that
[Meizu MX] trinsic:
Tick /system in mount settings for GApps.
[Meizu MX] Sanjikun22:
Thanks
[Meizu MX] xueHon:
Camera can not use the solution into the rec click mount -nvdata exit click advanced - file management -nvdata click on the lower right corner of the √-click to delete and then restart
[Meizu MX] jack6666:
Build 14 need deep wipe or flash above build 13 without wipe? Thanks

Inviato dal mio M2 Note utilizzando Tapatalk
[Meizu MX] ofvmxz:
Camera fix rc 14 "proxima"

I dit with Root Explorer. I deleted "NVDATA" Folder content and then reboot. Camera works perfectly :good:

nvdata is located in root directory
[Meizu MX] Alucard:
Oh my god there is nougat for the device i love you man!
[Meizu MX] Alucard:
If i lose imei information after wiping data through twrp recovery how do i restore it,is engineering mode working with this rom?
[Meizu MX] aLexzkter:
-Backup the EFS partition.

-No, that's a stock-rom related feature.
[Meizu MX] Hemachandrandeena:
camera is not working @Moyster any fix is there

camera is not working..help me to fix this
[Meizu MX] xueHon:
[MENTION=6262740]Hemachandrandeena[/MENTION] Look at the solution I made in front of me
[Meizu MX] Hemachandrandeena:
Do you know how to increase the sound sir???
[Meizu MX] Hemachandrandeena:
And during voice call loudspeaker is always on:crying:
[Meizu MX] Pcti888:
somebobdy had given the solution in some threads. you should find it carefully.
[Meizu MX] athranz:
nice one dude
[Meizu MX] numpea:
No need to wipe the whole NVDATA folder content just this file will make the camera work
[Meizu MX] jack6666:
Deep wipe and installed build 14, camera work for me.

Inviato dal mio M2 Note utilizzando Tapatalk
[Meizu MX] Carron:
Why when I wipe with the new recovery say me failed mount system this error is only when I format system in Ext4 but when I formart in F2FS the recovery don't give me any error.

Please someone can help me?
[Meizu MX] keofly:
confirm.same problem
[Meizu MX] aLexzkter:
Installing latest v14.

Can anyone post some deep sleep battery graphs?

Thanks

---------- Post added at 01:05 AM ---------- Previous post was at 12:07 AM ----------

Clean installed the latest version, configured basic stuff...Then flashed Magisk and Magisk manager says says I don't have root. WTF

I don't understand why, I have Magisk on my other phone working just fine.

Just tried with the latest v13 beta version of Magisk and it works
[Meizu MX] pedgsilva:
this is what happened to me in RC13 after instaling the boot memory fix, the phone stays in the meizu logo.

Returned to flyme, and there are three major diferences that i can see :

1 - the screen is more bright in flyme, the color is more cold

2 - the network 4G is more strong in flyme

3 - sound much higher in flyme
[Meizu MX] imb2h:
Awesome ROM, my device get a new life (:

But how can i switch selinux to permissive?

Method1: setenforce 0 returns "invalid argument"

Method2: echo 0 > /sys/fs/selinux/enforce also not working, getenforce returns "Enforcing"

Cant install divinebeats :C

Thanks a lot.
[Meizu MX] Bang Thien Minh:
me too! wanna install DevineBeat Audio but bootloop
[Meizu MX] :
Check the older posts..! people have given various working solutions for ur issues.. Like steps for changing it to premessive.. and using magisk..
[Meizu MX] demolition23:
For volume boost I use an app from play store, really works good.

Search : Volume booster GOODEV

Στάλθηκε από το M2 Note μου χρησιμοποιώντας Tapatalk
[Meizu MX] athranz:
would be perfect if someone can port the default flyme camera...i miss this feature :angel:
[Meizu MX] vijay.meizu.note2:
Camera not working...
[Meizu MX] soniccm:
Without [MENTION=7685540]Moyster[/MENTION] no nougat or further development so be patient the rom is very solid for now only camera "bug" exist but it's not big deal for daily use is excellent
[Meizu MX] n0p3zz:
HERE is solution for you.
[Meizu MX] vijay.meizu.note2:
Thank you.. Camera get working..
[Meizu MX] Hemachandrandeena:
I had a problem with my speaker while incoming and outgoing coils my loudspeaker is always on so i cant maintain my privacy..does anyone have that problem??
[Meizu MX] janek125:
Hi

Enyone can explane me step by step how to fix camera? I saw solution im post #982 but I can't find this folder. What is the file manager?

Question 2 how to root this software?
[Meizu MX] xraitor:
Root dir (not name)/nvdata/...

Install latest SuperSU from TWRP.
[Meizu MX] bkxckspell:
Ive sucessfully flashed the rom but when i want to login my google account, the play service app crashes

Any way to fix this?
[Meizu MX] Gargarospo:
Have you flashed any Gapps package too?
[Meizu MX] janek125:
Thanks a lot. It works:)
[Meizu MX] athranz:
it is save dirty flash from rc13 to rc14?
[Meizu MX] xraitor:
Yep))
[Meizu MX] bkxckspell:
In fact i did, with the first try i used the recommended base gapps which didnt Work (wasnt able to flash them due error code 7), afterwords i flashed beans gapps (now i get the Play service crashs)

Edit: I performed a factory reset and reinstalled the rom, again with error code 7 flashing the base gapps but ignoring them and now everything except the camera seems to work
[Meizu MX] trinsic:
Error 7 goes if you have system mounted in TWRP
[Meizu MX] Hemachandrandeena:
How to increase the sound..Dolby Atmos is not working??
[Meizu MX] xraitor:
Dolby Atmos is working!
[Meizu MX] deddy317:
" Dolby Atmos " Delete all permissions from magisk, then try again. Works ?
[Meizu MX] Hemachandrandeena:
How to do this?? I installed magisk!!can you explain me :)
[Meizu MX] deddy317:
I first installed "v4fx", it does not work. Installed "Dolby Atmos" issued permissions with "magisk" clean and restarted. "Dolby atmos" now works
[Meizu MX] supernatural91:
sorry

I don't understand whit the last rc4 viper4android whit magisk works?

whit rc3 viper4android did not recognize root
[Meizu MX] arunshand:
Thanks in advance for stable