yashsingh1/xdaforums huggingface dataset:
[Meizu MX] greger4528:
Hello

I can help with the translate that line in spanish says:

string nombre="dispositivo_ajustes_aplicacion_nombre">Gestos de panatlla-apagado</string>

Good Work for the amazing ROM [MENTION=7685540]Moyster[/MENTION]
[Meizu MX] Kisszen:
Tq u broo...this a great rom

Sorry broo...i just will ask abaut how can I root and give Twrp in this OS, Tq
[Meizu MX] LBA97:
You already need to have unlocked the bootloader and installer twrp to install this ROM.

If you want to root this ROM, just flash supersu.zip from twrp.
[Meizu MX] navdeep001:
I flashed this zip. After some time its stopped working. I flashed again. But results are same.

Pls fix. Battery backup is awesome
[Meizu MX] zhariffdanny:
same thing occurred to me
[Meizu MX] xraitor:
Please, fix BT connection. Often mi band is spontaneously disconnecting.
[Meizu MX] rudra964:
m3 note bootloader unlocking

Can someone please try to unlock m3 note's bootloader?:confused:
[Meizu MX] 5ham5h33r:
I still don't understand this VoLTE situation... The M2 note's chipset supports VoLTE. I know that much, but Flyme never supported VoLTE.. what is stopping this ROM from supporting VoLTE? Is it that it needs to be enabled by Meizu in Flyme first for this ROM to have VoLTE? Or whether M2 note for some reason can never have VoLTE?
[Meizu MX] LBA97:
This is a m2 note thread, you should find a m3 note thread, posting here isn't adequate at all.

VoLTE has to be enabled from the bootloader, and that's Meizu's task. It isn't a ROM functionality, and developers can't do anything until Meizu changes it.

This is what I understood, correct me if I'm wrong please.
[Meizu MX] rudra964:
The reason for posting here is that absolutely no one gives a satisfactory reply in the m3 note section. I'm lucky if I even get a reply. Moreover, m2 and m3 note are very close to each other in the hardware section except for the change of SoC.
[Meizu MX] Xtian Rey:
ROM Discussion + M2 Note thread here, please don't ask for M3 Note Bootloader, You are way off topic. If no one gives a good reply at your section then be patient and wait, do you think we didn't had a hard time waiting for our M2 Note's bootloader to be unlocked? (Sorry if i was too harsh on my words but its for the better.)
[Meizu MX] Moyster:
Wierd, did you also clean youtube's app data ? Anyway, I modified a bit changes, here and there, if the problem still happens on beta 2 (first without then with a clean wipe) we'll see what can be done, but I don't have such problems so far.

read above ;)

I don't have this problem with my smartwatch, but if you read OP, there's a procedure to report bug issues. Make some logs when the error happens, etc... or buy me a mi band ;) (joke)

read bellow

Imho if no one gives a satisfactory answer is because there is none. M3 note is not unlocked, and while m2 note and m3 note is "similar looking", it's like padlocks, "Master" padlocks all looks the same, but 1 key only opens 1 padlock.
[Meizu MX] titoerlangga30:
[MENTION=7723091]5ham5h33r[/MENTION] ohh... You dont install magisk via twrp? With your metode root handle by supersu not handle with magisk?
[Meizu MX] 5ham5h33r:
[MENTION=7633279]titoerlangga30[/MENTION] well I didn't manually install magisk I just followed the instructions I got after installing magisk manager. Yes my root handler is by SuperSU and not by Magisk.
[Meizu MX] Yukin3:
My device hardbrick. When I'm flashing with SPFT it has worked. But my device is still not on. No vibrations on my device. Can not charge. So I tried the emmc test, but I got a message from flashtool.

1. BROM ERROR: S_DA_MT_DEDICATED PATTER ERROR (3094)

2. S_DA_CUST_PARA_AREA_IS_BLANK (3098)

so what should I do? Sorry i'm using google translate:rolleyes::rolleyes:
[Meizu MX] tomax80:
Did you unlock bootloader before flashing the rom? Why did you flash the rom with sp flash tool ?
[Meizu MX] Yukin3:
No sir, this is still original.di the night I charge this device and in the morning it will not turn on again. I think maybe flash the rom with sp flash tool can solve this problem
[Meizu MX] numpea:
Incorrect call durations in Dialer has been fixed in the new lineage os change log
[Meizu MX] undaclazz:
do you mean official LOS?

because I can't see a new update in OP :D
[Meizu MX] numpea:
Yes the official Lineage OS change log :)
[Meizu MX] 5ham5h33r:
Guys I'm not able to change USB configuration under developer options.. anyone else experiencing the same issue? Any workarounds around it?
[Meizu MX] goodoane:
Just plug in your cable to your PC then on your phone open cable connection setting icons from top bar an chose your preferred connection.
[Meizu MX] 5ham5h33r:
I actually wanted to change the connection type because it was showing charging via USB while it was actually plugged to the AC adapter, but after disconnecting and connecting again it showed charging AC and continued to charge as normal. Still thanks anyways.
[Meizu MX] vitaliy.bilash:
In the last update there is no hdr in the camera(((

What can be done?

Maybe someone has a working version of Google Camera?
[Meizu MX] zoranstojanovic967:
Yes, HDR missing. Same to me. Also, Hotspot tethering sometime working, sometime not. I must turn it on and off, several times.
[Meizu MX] 5ham5h33r:
If I decide to use adoptable storage, will I still be able to flash future updates without any problems or will I have to lose my data each time?
[Meizu MX] Jart0:
Is the saturation option of the stock camera working for anyone? It doesn't work for me and this would be awesome as the M2 note camera always lacks some colour and I need to add like 20% saturation to every single picture I take in order to make them look better (it was the same in Flyme)... Any other app that can do this is also welcome if anyone know.

The room works very well, better than I expected honestly, so Thanks Moyster and keep the good work, the split screen is awesome, the only cons, that the mback button doesn't lock the screen, the necessity to add the button bar and lose some screen space, taking a screenshot doesn't give the option to crop it (althought I downloaded an additional app and it is working well) and that sometimes I receive a notification saying "the app .... has stopped working..." by the way if you tap wait it usually keeps working. I would recommend it to everyone
[Meizu MX] 5ham5h33r:
I think you would be able to increase the saturation with some other camera app, try footej, snapcam, open camera, etc... The mBack button is able to lock the screen, you just have to go to settings then buttons and under the home button you can change the long press action to turn off screen just as it was in flyme, and btw if u prefer swipe up for multitasking like me then download an app called all in one gestures, under the preference option of that app go to Edge preference and set the opacity to 0 and the edge width to maximum. After that u just simply have to go back and tick the bottom area under swipe and set the action to open multitasking. And one more useful tip, while you can't get to crop screenshots as the same way you do in flyme, you can literally take cropped screenshots instead. To do this you again have to go to settings then buttons and then under the power menu you just have to enable screenshot option. After doing this whenever u hold the power button you will see a screenshot option, on long pressing that screenshot button you will get to drag and choose how much area you want to screenshot, sort of like the snipping tool in Windows.
[Meizu MX] Jart0:
Wow thank you so much for the info, after doing this the rom is going to be almost perfect. Another issue I'm facing is that I made 2 partitions in my SD with Mini Tool Partition Wizard, the second one in ext4, and when I start the phone I get a notification saying that the SD card is damaged (the second partition in particular) I saw that Lineageos gives you the option to make a second partition as an internal storage too, so I was wondering if formatting the SD this way would solve the problem. I read there was some problems with the SD cards some time ago. Btw, the apps that I moved to the second partition with Apps2DS seem to work well, but I was thinking that I got the warning "the app ... has stopped working..." sometimes because of this.
[Meizu MX] 5ham5h33r:
Well sorry I can't help you out on your SD problems as of now, my 128 GB SanDisk card got corrupted and I've got to replace it then next time I drop by the service center, but in case it helps you, even I am experience "the app... Has stopped working..." Issue sometimes on certain apps, mostly while using chrome though (or perhaps it's because that's what I'm using most of the time anyways :P).
[Meizu MX] Jart0:
Thanks, I didn't notice at first when you told me, but now everything is working as it did in Flyme, the mback button locks the phone and swiping from the bottom opens the multitasking, swiping twice swaps the two last apps. If someone is also interested in adding some saturation to the pictures, after trying many cameras, I only found one that does what I wanted, it is Cameringo+ (probably the free version as well), you can adjust the saturation, contrast, brightness, etc. and see the effect "live" and even compare it to the original even before taking the picture. It also saves the settings by default so you don't need to add saturation every single time, perfect. Much better and colorful pictures!
[Meizu MX] 5ham5h33r:
Glad to hear it, I personally have my last app set to double tapping the mBack button like in an iPhone and I just wish somebody ported the flyme camera app.. I am unable to find any app which is able to take slomo videos, just managed a little by tweaking the settings in SnapCamera.
[Meizu MX] Carron:
When I try to put a photo on instagram stories the app crash all times. This problem is a app problem or a rom problem?
[Meizu MX] ozichiatt:
stuck in twrp

Hi guys, my meizu is stuck in twrp, flashing rom giving me no results, like there's no firmware on it. Any suggestion please?

Thanks in advice and sorry if it can be a stupid quesion but i'm new in this beautiful world.
[Meizu MX] Moyster:
Download

:

Build 13 (RC 3 "Datupdat") : Here

NOTE: for those having issues with bluetooth not enabling, you need to copy/paste the file :

"/data/nvram/APCFG/APRDEB/BT_Addr" to "/data/"

Changelog :

[bluetooth] config update

[kernel] new drivers (uid_sys_stat, mlog, some mtk drivers fixes), f2fs updates, net updates, now using MEMCG instead of kernel LMK, more CVEs fixed, reworked config, and various small tweaks/updates.

[lineage] latest sources from los, note: they moved from Gello to Jelly (a lighter/easier to maintain browser)

[misc] small fixes for sepolicy / device tree (f2fs fstab support)

[sdcardfs] moar fixes!

[*][TWRP] alpha: for those who wants to test f2fs, I built a nougat recovery with sepolicy support (primarly to restore context on files you push with adb) that should support formating f2fs, I couldn't find the time to try for myself, only /cache and /userdata should be formattable in f2fs, feedbacks welcomed.

File will be available in the download section, labelled:

twrpNsep_recovery.img

Note: this twrp is built based on the Nougat branch, which means it's probably incompatible with older roms (LP/MM) and older backups, as well as older versions of this rom (this TWRP should only allow roms built after TWRP was built, like ~2/3 weeks ago)

enjoy :)
[Meizu MX] hthbence:
Did you unlock the bootloader?
[Meizu MX] numpea:
make sur you are not using an old twrp version LP or MM use the one posted in the op
[Meizu MX] numpea:
I just tried it but it doesn't wrok on both data and cache i ended up with 00Mb on data and cache and unable to mount them ;)
[Meizu MX] hthbence:
Also it can cause problems if you're not wiping Dalvik cache, cache, data AND INTERNAL STORAGE (helped me in many cases). Wipe Dalvik cache and cache before and after flashing gapps. Hope that helps. :)
[Meizu MX] klimu:
Do not simple wipe. Choose advanced and then change file system. Just choose the same as before and it will correctly format cache partition. Happened to me the same on that new modified TWRP.
[Meizu MX] Moyster:
Hi there, thanks for trying ;)

Hi also, so is F2FS working or not ? or you mean the partitions after formatting back to ext4 are working ?
[Meizu MX] numpea:
yes i changed file system to f2fs it will auto format the partition but you will end up with corrupted f2fs partition and going back to ext4 with the same way

anytime [MENTION=7685540]Moyster[/MENTION] ;) i think he means formatting back to ext4 working
[Meizu MX] ozichiatt:
Thanks for the answers.

I solved ublocking the bootloader and booting from cmd.
[Meizu MX] vitaliy.bilash:
The same problem! How you solved the problem?
[Meizu MX] m3shat:
Problems when disabling mobile data for apps

< Remove this post pls >
[Meizu MX] daniel.harbula:
Low Volume

Tried the latest release RC13 and its stable.

My only complaint so far is the low volume and i can't do anyting about it since SElinux is not permissive anymore :'(

Is there a way around this?

I tried installing Magisk but i couldn't install any module since i got some error "safetynet cts profile mismatch"

Thanks for your ROM and hard work, keep it up :D :good:
[Meizu MX] xraitor:
I use DolbyATMOS 6.5 installed via TWRP, not magisk module. It's works fine. ;)
[Meizu MX] vitaliy.bilash:
I just flashed a ROM with all the wipes. I flashed the recommended gapps. But applications freeze and down. What could I have done wrong?
[Meizu MX] Pcti888:
you should flash gapps after rom. It means that, After you flash the RC3 rom, dont restart the phone. then flash the recommend gapps. Yeah, you can use add zip selection in twrp.
[Meizu MX] Pcti888:
Hi~ guys, Can you give me a link? I found some one , flashed it. it always FC.
[Meizu MX] vitaliy.bilash:
Who flashed Google Camera addon from here? https://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

Which version of the application is ok?
[Meizu MX] xraitor:
DolbyATMOS 6.5: https://xdaforums.com/devdb/project/?id=9817#downloads
[Meizu MX] numpea:
Version 2.5

https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera
[Meizu MX] Pcti888:
Thx.

i found this post but i selected the download link:A7000 6.5...:crying::crying:

---------- Post added at 01:58 PM ---------- Previous post was at 01:24 PM ----------

click you link. But it shows that Sorry! This content is not available in your country yet.

We're working to bring the content you love to more countries as quickly as possible.

Please check back again soon.:crying::crying::crying::crying:
[Meizu MX] undaclazz:
What about from apkmirror? once I downloaded from there
[Meizu MX] numpea:
Click here to download from apkmirror
[Meizu MX] vitaliy.bilash:
There is no hdr too(((

Does anyone use Gboard?

It seems to me that the interface with it slows down
[Meizu MX] cartman333:
I would appreciate it too, haven't flashed the one that i found. If you could link us the working version that would be great. [MENTION=5452516]xraitor[/MENTION]

EDIT: Nvr mind found it, thx for the file. :D
[Meizu MX] ozichiatt:
i've done in this order (don't knoq if it's wrong):

1: Downloaded an other gapps and re-downloaded the zip of lineage.

2: Then in bootloader, from pc, fastboot oem unlock.

3: Wiped everything got to wipe, flashed firstly SuperSU and then the rom and gapps

4: back to bootloader, fastboot boot boot.img (the image of lineage on my pc)

Then yhe phone was revived.

Hope it helps
[Meizu MX] jack6666:
Build 13, after full wipe and flash rom and gapp, freeze and crash some apps. Any suggestions? Thanks!

Inviato dal mio M2 Note utilizzando Tapatalk
[Meizu MX] vitaliy.bilash:
The same. Sometimes only restart can help((

http://cloud.tapatalk.com/s/59295b35eef01/alogcat.2017-05-27-10-14-53+0300.txt
[Meizu MX] AlexLartsev19:
Flash this kernel: https://github.com/AlexLartsev19/blood_m2note/releases/tag/BLOOD-r7.0
[Meizu MX] jack6666:
Working perfectly, thanks so much :) :):)

Inviato dal mio M2 Note utilizzando Tapatalk
[Meizu MX] m3shat:
It seems like r13 has some RAM management problems... and that hits performance... Even with no apps running in the background the ram usage is at can 1.6 to 1.7GB full, running multiple apps in the background is not possible in this build it seems (Yes I did clean install)
[Meizu MX] Moyster:
Well, I reverted the LMK -> MEMCG changes, so that should be back to normal, try flashing "RC3-mem-fix.boot.img" ;)

Hotfix changelog :

[ext4] backported 3.18 drivers en encryption features (better I/O, faster encryption)

[f2fs] f2fs stables drivers fully upstreamed and working

[twrp] twrp-3.1.1-0.recovery.img is now able to format cache and userdata as f2fs ;)

MAKE BACKUPS / FORMATING USERDATA MIGHT DELETE INTERNAL STORAGE

Thanks to [MENTION=6520775]numpea[/MENTION] for testing and benchmarking it :)

f2fs vs ext4 :

Antutu 6 reports 'UX I/O performance" ~3700(ext4) VS ~4800(f2fs) points :highfive:
[Meizu MX] Carron:
I flash the twrp-3.1.1-0.recovery.img and try to format cache but don't work. I need install before RC3-mem-fix.boot.img?
[Meizu MX] Moyster:
I'll summon [MENTION=6520775]numpea[/MENTION] for you :P Can you help buddy ? :)
[Meizu MX] numpea:
i'm here :) [MENTION=7685540]Moyster[/MENTION]

Fisrt

make backup and move it to external sdcard or to your pc

because changing /data to f2fs will wipe even internal memory

1- flash twrp-3.1.1-0.recovery.img with twrp select install image and choose recovery

2- go to advanced => file manager => sdcard and delete TWRP folder

3- reboot to recovery

4- go to wipe => advanced wipe => select cache or data and click on Repair or change file system => click on change file system select F2FS and wait for the formatting

5- repeat step 4 for data or cache

6- reboot to recovey and check wipe => advanced wipe => select data or cache => repair or change file system you'll see it F2FS

7- restore your backup flash the new boot (and supersu or magisc) then reboot to system

:highfive:

Formatting using make_ext4fs takes some time so sit and wait for it
[Meizu MX] vitaliy.bilash:
Do I need to format the system partition? Like cache and data

Upd. Sorry, just read that I do not need to do this
[Meizu MX] daniel.harbula:
Selinux to permissive

I was unable to install a working sound mod because Selinux is set to enforcing :\

Is there anyway to set it permissive? Or a sound mod that works with enforing? I tried installing dolby atmos but it keeps Fc-ing same as any outher sound mod. The volume is really low and i can not increase it from engineer mode since it's not existing in this rom :(

Thank you for your help.
[Meizu MX] Moyster:
Hotfix update : RC3-memfix-boot-v2.img

[ext4] fully upstreamed with ext4-crypto and lazytime mounts :D

[binder] cleanup, small fixes and updates

See the antutu 6 benchmark screenshot (the "UX I/O performance" field is what matters for FileSystems), quick summary :

ext4 : 3700~

f2fs : 4800<->5400 (results reached 5400~ after a clean wipe)

ext4 3.18 : 5661

Now the question is, what happens to a clean wiped phone with ext4(3.18) /system and f2fs data&cache partitions :p Can it fly ? :D
[Meizu MX] tomax80:
[MENTION=7685540]Moyster[/MENTION] : Hi I tried the new kernel, but I have problems with gapps. Maps continues to crash and also google foto doesn't find my google account , now I'm back to the previous kernel with ramfix and everything is working again. I made a clean install and using f2fs. Thanks and good afternoon
[Meizu MX] Moyster:
I'm still on ext4 here and maps doesn't crash, did you wipe dalvik cache and tried to clean google maps' cache ? What/when is crashing exactly ?

[MENTION=6520775]numpea[/MENTION] is still on f2fs, can you boot maps and see if you can make a route ?
[Meizu MX] korcio86:
Could someone please explain how to flash RC3-mem-fix.boot.img? Can I do it without wiping data?
[Meizu MX] Moyster:
every *.img can be flashed from twrp, just like a zip except you choose "install an image" and it asks you where to flash it (boot / recovery etc..)

Boot.img => boot

twrp.img/recovery.img => recovery

=> don't flash other images to anything else, there should be no need anyway :)
[Meizu MX] numpea:
Everything is going well for me Maps and Google photos

Using opengapps rc3-v2 on f2fs
[Meizu MX] Moyster:
thanks :) It would've been wierd if ext4 was selective on which apps it crashes :p probably a dalvik cache / app data issue.
[Meizu MX] tomax80:
The solution is wiping cache and dalvik cache after flashing the new kernel. No more gapps problems. Thanks as always :good: :good:
[Meizu MX] Moyster:
Hotfix update : RC3-memfix-boot-v3.img (v3)

[f2fs] merged lazytime mount support

fstab] enabled lazytime for ext4 & f2fs

[fs] tuned mount flags

Here's my current "setup" :

system as ext4 (v3.18+lazytime)

data&cache as f2fs (lazytime)

antutu6 "UX I/O performance" : 6889 (!!!) :D DAT INSANE SH*T!
[Meizu MX] Moyster:
Yup, I only started posting the kernel here because last build had a bad memory management issue (moving from kernel lowmemkiller to memcg didn't go well :P ) and I was already working on backporting the ext4 drivers, now that I backported it correctly, I updated the kernel again to be sure people with a "non-updated ext4 3.18" driver (read kernel rc3 fix v1 &v2) don't suffer wierd bugs, kernel rc3-v3 has a fully working ext4/f2fs driver, upstreamed, fixed, with lazytime supports AND the fstab changes :)

RC4 will have this kernel packed in, but the whole backup / format / restore process to change from ext4 to f2fs is still a MANUAL PROCESS.

formating /userdata (= data partition), also contains INTERNAL STORAGE.

This means, making a TWRP backup is not enough, you need to backup your entire internal storage and transfer it to your sdcard / pc / somewhere.

HOW TO CONVERT TO F2FS WITHOUT LOSING YOUR DATAS !

Steps from TWRP are simple (after backup/transfert) :

boot TWRP

make a backup and only select "DATA" partition

settings > untick "use rm -rf instead of format"

format > advanced format > tick "cache" & "data" > change filesystem > f2fs > confirm

copy your internal storage datas and twrp backup back to your device

settings > tick "use rm -rf instead of format" (= this will make TWRP not format the partitions before restoring to it, it's very important if you want to restore

restore only "data" partition

reboot under the same rom, with faster read/write times :)
[Meizu MX] Bang Thien Minh:
how to using file .img? guide me
[Meizu MX] Moyster:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

If you're reading this thread to know the very last news, you shouldn't skip posts/pages :)
[Meizu MX] Bang Thien Minh:
oh, i'm sorry! this new your kernel only using for for ROM Lineage OS?

and next RC when will release?

:D

thank for posting rom! hope you alway happy

---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------

@Moyster i hope you can public a video guilde everyone all step flash new recovery and new kernel

many NewBies still work unsuccesfully
[Meizu MX] Moyster:
You can probably flash it to other roms, the best is to either unpack boot.img and grab the zImage to repack it to the rom's boot.img you target, or simply compile it from : https://github.com/Moyster/android_kernel_m2note/ .

Next RC when it's ready (tm) (c) :D

edit:

I can't do everything and still have time on my own, any help is welcomed, there's already a million videos on youtube, probably in your own language too already :)

flashing a boot.img with twrp is the same for every devices with a kernel and twrp, which means going to youtube and typing "howto flash recovery.img / boot.img with twrp" should yeld a lot of results.
[Meizu MX] Moyster:
did you make the backup with an old version of TWRP, before updating TWRP and formating ? Old twrp from shev_T and the new twrp don't have the same backups naming convention, if your backup doesn't show up in the new twrp, try renaming it (make a simple backup with the new twrp and check it's name ;) )

Also, I just grabbed a picture off google images but, as I wasn't sure what you meant, look at this :

[IMG="twrpbkp"]https://www.howtogeek.com/wp-content/uploads/2016/01/TWRP-backup.png[/IMG]

(it's the backup screen, but it works the same for restore), only select "data" ;)