yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] GullRaDriel:
You're welcome.

AndDisa, if you pass by here I have a question regarding linux kernel 3.4. Do you have any sighting on it ? What kernel will oreo be using, and do you think there is a small chance that some port the new oreo to the old nexus 7 ?

I know answering can be tedious, so I thank you in advance.
[Nexus 7 Android Development] AndDiSa:
[MENTION=4407934]GullRaDriel[/MENTION] the Unlegacy Android project is working already on Oreo for Grouper ... and they are using the 3.4 kernel. I think 3.4 is the way to go for the next Android release(s).

I don't think that I will start an Oreo port on my own. I don't will have the time for such a project. Probably l will support the Unlegacy Android project ... if there's anything l can bring in.
[Nexus 7 Android Development] vishnumrao:
A philosophical question that may not belong here. But unsure where it should be asked. :) Why would this port of Android not be submitted for inclusion in the official Lineage OS builds?

When I have a device, Lineage OS (and previously cyanogenmod) is the first place I check. If more devs submit their ports to Lineage, wouldn't it become a one location for all alternative roms for all devices?
[Nexus 7 Android Development] Tangofied:
Update on Update

[MENTION=2188693]AndDiSa[/MENTION] Update to latest grouper build was a success, thanks for your update instructions. Only had to reconfigure SuperSU and re-install BusyBox Pro. All apps updated/downloaded through Google Play Store remained intact with current settings. That includes such apps as Google Play Store and Google Play Services. The only anxious moment was the 10 minute first boot, which I expected but still makes me nervous! Thanks again.
[Nexus 7 Android Development] thierry+:
@ AndDisa......with the announcement that the AAC codec is being added to all android devices via ASOP,......will you be adding it to this ROM? I hope you do an upgrade to the lo-fi standard bluetooth codec is due to say the least.

I still note issues with webview in the current release, it still crashes when I attempt to use the XDA app or Bluemail.

My device is unrooted, running June release, no google apps whatsoever including google play and it services, works fine.

Thank you for this ROM and especially your time.

Regards
[Nexus 7 Android Development] iamelton:
why should an AOSP rom be submitted to LOS repo? they are two totally different things..
[Nexus 7 Android Development] vishnumrao:
[MENTION=3638617]iamelton[/MENTION] Pardon my ignorance. Aren't all custom ROMs based on the AOSP project source released by Google / AOSP? Isn't LOS based on AOSP too?

My question is why would devs take the efforts to publish custom ROMs on their own? Wouldn't it be better for muliple devs who support different devices to submit their ROMs to a common project like LOS?

Forum mods, I know I am digressing off topic. I can put this out to a different thread if you point me to one.
[Nexus 7 Android Development] FirePsych:
ROM development is about individuality and initiative and innovation and experimentation. Why should ROM developers perform just for the organized groups?

Having a rooted Android device means you can look for exactly the features you want on a ROM or app that just meets your needs.

All of the big popular ROMs were based on the inspiration of one Dev. Why supress that to give it up to the collective?
[Nexus 7 Android Development] Ahkah:
You are not completely not right. BTW: Has English the capability of double negation? If you look through the threads regarding the so called ROMs you will notice that there is lot of cooperation between or among developers. Especially there is no sense in doing the same complicated thing twice or more often, like adaptions to a special hardware like a total outdated, ancient device. As developers are individuals, some of them prefer contributing to a community project, while others prefer to work in smaller groups or alone. It would be interesting to know if women worked differently or even more effectively, but unfortunately we will never know, as they prefer to do more important things in their life. :)
[Nexus 7 Android Development] adstraylight:
Yes, but it's hardly ever used, in this instance, most people would say "you're not entirely wrong" /OT ?
[Nexus 7 Android Development] vishnumrao:
Thanks for the insight into dev minds. I agree flexibility and independence mean a lot to everyone.
[Nexus 7 Android Development] MacLeod100:
It would be interesting to know if women worked differently or even more effectively, but unfortunately we will never know, as they prefer to do more important things in their life. :)

Awww i was wondering when feminist´s will show up here :D :D :D
[Nexus 7 Android Development] BelzIgoh:
Extract boot.img from rom zip then flash it with fastboot.
[Nexus 7 Android Development] Nexus7_tilapia:
Unfortunately since then the tablet is not recognized by PC! :(
[Nexus 7 Android Development] AndDiSa:
[MENTION=8618734]Nexus7_tilapia[/MENTION] ... but you have the fastboot drivers installed and configured correctly?
[Nexus 7 Android Development] Tangofied:
Webview

How is webview implemented in this ROM? I noticed it is at version 53, while the Play Store's current version is 61 or so and it is not updated by Play Store. Then there is the app Webview Shell which starts a browser. Is their an issue with webview that required some kind of workaround? Just curious about the history.
[Nexus 7 Android Development] Alex_Lyt:
Why not to just download rom to your tablet directly from this thread?

Data is being cleaned without "media" subfolder, so your zip will survive ))
[Nexus 7 Android Development] AndDiSa:
There might be two reasons for that:

1) Normally on 7.x the device is connected via charging mode only. You need to change the usb mode from charging to either PTP or MTP mode otherwise you will not be able to transfer data to your PC.

2) Do you have your udev system correctly configured so that the device is detected? For the Nexus 7 you should see something like

# Google Nexus 7 16 Gb Bootloader & recovery mode
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="ads" # Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="ads" # Recovery
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee7", MODE="0666", OWNER="ads" # Charging only

# Google Nexus 7 16 Gb PTP mode (camera)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e43", MODE="0666", OWNER="ads" # PTP media
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e44", MODE="0666", OWNER="ads" # PTP media with USB debug on

# Google Nexus 7 16 Gb MTP mode (multimedia device)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e41", MODE="0666", OWNER="ads" # MTP media
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="ads" # MTP media with USB debug on

Be aware that other devices need other definitions ... especially when playing around with different devices they get easily overwritten ...
[Nexus 7 Android Development] junk2k06:
OP, so many thanks for your time and effort. My almost dead Nexus 7 is alive now and mostly usable.
[Nexus 7 Android Development] juliaiksdea:
AndDiSa, slow charging occurs sometimes. 1% or 3% per hour. Re-unpluging the device two-three times or rebooting it can help only. Do you know about this bug?.. It occurs only in your rom on my device. I use Tilapia rom.
[Nexus 7 Android Development] Alex_Lyt:
Oh ****! Just installed rom and decided to decrease screen brightness. Suddenly screen turned black. I've stopped breezing. Began to remember where i've bought previous motherboard...

Luckily its not apx, but i had to reset tablet. Failed to increase brightness on a black screen (((
[Nexus 7 Android Development] Alex_Lyt:
That is slow charging really, not usb port, believe me. I was charging my grouper in the morning with 4.4.2 installed and now i'm charging it with the last build from this thread installed. Charging is much slower...

But the tablet itself is much faster ?
[Nexus 7 Android Development] uwo83m:
Just hołd your tablet under some bright light or put a torch to the light sensor until you see the brightness slider. I think the light sensor is not calibrated.
[Nexus 7 Android Development] FirePsych:
On this side of the pond, by "torch", you mean flashlight? [emoji3]
[Nexus 7 Android Development] Alex_Lyt:
It was easier to just wipe a tablet )))

But thanks for the trick.

---------- Post added at 02:12 AM ---------- Previous post was at 02:11 AM ----------

No. Flashlight is flashing. Torch isn't )))
[Nexus 7 Android Development] Alex_Lyt:
[MENTION=2188693]AndDiSa[/MENTION]

Hi, first I want to thank you for such a great rom!

Now about slow charge: )))

I've read valor about this problem: short cords, charging chip, etc but I'm sure that problem is software related, at least at my case, because:

1. I've charged my Grouper in the morning, than flashed your room and charging became much slower

2. Today I've physically changed USB port to one from my donor Nexus. Nothing changed. Charging speed is still not more, than 400 ma.

Please help somehow )
[Nexus 7 Android Development] AndDiSa:
[MENTION=7844548]Alex_Lyt[/MENTION] I am getting up to 800mA ... nevertheless it's slow but I don't know what's the reason for that.
[Nexus 7 Android Development] slybunda:
there is a lot of lag with this rom. after staying on for a few days it becomes very laggy, cant even play a youtube vid without it turning into a slideshow.
[Nexus 7 Android Development] Alex_Lyt:
You are mistaking

You're absolutely right, BUT "data" partition is being cleaned excluding "media" folder. So your media (and all the other files) will survive. In fact you may full wipe your tablet and then install everything you needed from internal memory.
[Nexus 7 Android Development] len207:
Have you considered using a USB to Micro USB adapter and putting the ROM onto a USB stick drive, attaching it to the phone and in TWRP go to select storage and change the Source to USB Storage? I have done that several times with this and other devices with good results.
[Nexus 7 Android Development] Alex_Lyt:
[MENTION=4336485]rottenwheel[/MENTION]

1. Update twrp to latest (3.1.1.0)

2. Wipe and format are two different things. You've talked about wiping, not formatting

3. I've stopped to study English 15 years ago, so pardon me. We may talk my native Ukrainian or, at least, Russian. But then I'll be your grammar nazi for sure. So take it as it is )
[Nexus 7 Android Development] tpuserhp:
I am already using substratum theme in legacy mode for my grouper. The only thing is I need to reboot after the overlays update. I am using Swift dark substratum theme from play store and it works without problems.
[Nexus 7 Android Development] Ahkah:
Inflationary usage of "nazi" or "Nazi" insults the victims of the Nazi dictatorship and downplays the blame of someone being a radical extremist of any "couleur".

Regarding grammar, orthography and punctuation: This has been invented to ease understanding among people and to avoid misunderstandings caused by ambiguity. Further, it's a matter of politeness to write understandable sentences (and Java code ...), and if nobody is ever been corrected due to "political correctness", mistakes will never been noticed and can never be corrected.

Information for insiders: My home town is known to be the region of the best (this is political incorrect!) German in universe. ;)
[Nexus 7 Android Development] AndDiSa:
Your udev rules are looking fine for me, but in this way it's working for the Nexus 7 only, not for other devices. Probably you would like to add these config lines to the ones you have already defined on your system to support all of your devices.

Regarding the flashing issues, also on my Linux system the protocol error from time to time occurs. The easiest solution for that: If that error occurs, reboot your device into bootloader mode. After the reboot the fastboot command should go through smoothly.

Regarding the November release: I am still waiting for Google to submit the changes to AOSP. Up to now only the 8.x branches are updated to newer versons, all 7.x braches are still on the October versions.
[Nexus 7 Android Development] Tensor7:
Hi. I've been testing the newest version of this ROM for a week now. The ROM in quite stable and fast, the only thing that really bothers me here n there in storage access with new apps. My Nexus 2012 has F2FS on Cache and Data partitions. When i install new app, that requires access to storage and i grant them access, the app does not see any files on it (IPTV, Nova launcher ...). The problem is solved by wiping dalvik/cache but still, it takes some time.
[Nexus 7 Android Development] adstraylight:
This strikes a chord of memory, try simply force closing the app in question rather than wiping the caches. This used to happen to me with new installs of chrome a while ago.
[Nexus 7 Android Development] AndDiSa:
Version with November security fixes (2017/11/06)

Today I've uploaded a new version of the ROM (Grouper / Tilapia) containing the November security fixes. You can download them from the OP. I was hoping that Google pushed the changes at least to the 7.1.x branches, but it seems as if they have abandoned that branches in AOSP, too. Nevertheless I've cherry picked the commits from 8.x and backported them to 7.1.2.

Beside that I did some intelliactive governor tuning. I experienced better perfomance than with the last releases but battery lifetime is still quite good. I am waiting for your comments on this.

If you are familiar with the updating process, you can download the new versions also from here: Grouper-OTA-20171111 / Tilapia-OTA-20171111

And as always: flash on your own risk ...
[Nexus 7 Android Development] beepmod:
Hi, I'm new to this rom. Tried the new 171111 version today on a friend's tilapia, and I was very pleasantly surprised. Everything seems to work just fine. In comparison to an installation of Lineage 14.1 I did just a month ago on my mom's grouper your AOSP build is really much faster and came without any problems to circumvent (except installing gapps after a reboot). It is good to know someone cares for the latest security patches! So thank you a lot!!!
[Nexus 7 Android Development] thierry+:
[MENTION=2188693]AndDiSa[/MENTION]......with the announcement that the AAC codec is being added to all android devices via ASOP,......will you be adding it to this ROM? I hope you do an upgrade to the lo-fi standard bluetooth codec is due to say the least.

Thank you for the update....this is still the best ROM for grouper.:good:
[Nexus 7 Android Development] wutzin:
Hi, I'm installing your rom right now. Converted my partitions to f2fs (as described in post #1895), then tried to install today's gapps nano package (arm, 7.1, nano) right after flashing the rom. The installation failed with the following message:

__________________________________________________

Open Gapps nano 7.1 - 20171112

- Mounting /system

-Gathering device & ROM information

*** Incompatible Android ROM detected ***

This GApps pkg is for Android 7.1.x ONLY. Please download the correct version for your ROM: 5.1.1 (SDK 22)

******* GApps Installation failed *******

__________________________________________________

Not sure what is going on here. I really would have preferred the nano install. I then tried to install the BeansGappsMini package linked in the 1st post and that one installed without a problem.
[Nexus 7 Android Development] skinniezinho:
Will give it a try on my Tilapia. I was with version 20170707 and it is stable as hell.
[Nexus 7 Android Development] 239:
Try to reboot to RECOVERY before installing GApps. Never had a problem with OGApps pico package that way.
[XDA Assist] isoch97:
i have a huawei g535-l11 andi want to install android lollipop 5.0.1 on it ! how can i do ?

and how can i get rid of orange systeme on my phone to have an officiel huawei? :o :o

plz answer me
[Meizu MX] Moyster:
Really complete, I could unlock my M2 Note and install CM-12.1 ! Thanks ! :D
[Meizu MX] LBA97:
Moyster xDD :laugh::laugh: Thanks to you, without you this wouldn't have been possible :D
[Meizu MX] Xtian Rey:
Pretty much covered all, just state the Armv7 Android level API 21 64bit, 5.1 Micro or Nano for gapps. They might get confused on what to choose.
[Meizu MX] LBA97:
Very true, thanks a lot. I introduced the platform and the Android version of GApps
[Meizu MX] djzero86:
Thanks nice guide... Very useful for everyone who want play and modified the M2 note.
[Meizu MX] Mr0oHo0:
"This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights*￼)"

I Am Using M571C, But Everything Fine.
[Meizu MX] LBA97:
I include this on the guide. I read it bricked the phone in several cases, but I'm glad yours didn't.:D
[Meizu MX] miracleian:
Thanks for your guideline , it helps a lot !
[Meizu MX] aaawqw:
Great work lol:)

Another thing is…ShevT's recovery has no problem in cache partition.Only my broken recovery did… So remove the cache fixing part:)Any problem just send me a private message. I'll check when i have time.:)

---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------

And Meizu M571C should use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions…

Another thing is, Kingroot is not suggested. It cannot be detected by Flashfire and some other tools. And cannot be replaced by SuperSU. So Kingo Root+SuperSU might be better.
[Meizu MX] Moyster:
https://github.com/Moyster/android_device_meizu_m2note/blob/cm-12.1/BoardConfig.mk#L10

Line 10 to 15 you have the partitions size ;)

$ cat /proc/partinfo

example :

Name------------Start-------------Size

recovery 0x0000000004840000	0x0000000001400000

Take the Size value : "0x0000000001400000" => hexadecimal to decimal => 20971520 = recovery partition size :)

PS: I don't think the hardware is "that" different, at least, the kernel meizu released should contain both phone models/drivers ;)
[Meizu MX] Qeemi:
Mine is M571H, can I proceed?
[Meizu MX] LBA97:
Mine too and it worked. I can't assure you anything, but I think that the problem are m571C which are different. Good luck if you're going to give it a try!
[Meizu MX] aaawqw:
See it. I'll give a try on m2 note(M571C, China Telecom). At least try to build twrp;) But seems my pc's hdd is not enough:( No space for source code:(
[Meizu MX] dinkan01:
little problems.

bootloader unlocking and twrp and roms works very well..

1. OTG is working for me.. :good:

2. unfortunately my phone is not detected by PC.. :confused:

(show USB is not connected, USB debugging is not accessible..)

3. little bit lag here and there.. :p

4. wifi works well :good:

Need more optimization.. Expecting lot more from you :o

thankyou very much for this :good:

DOUBT : so bootloader is unlocked, now it is possible to make good MM and N based CM roms ?
[Meizu MX] lazicki88:
hi,which build of cm 12 you put in phone?
[Meizu MX] venturaj:
M571U

I have the Meizu M571U Model. Can I do this or will it be bricked?

Thank you very much:)
[Meizu MX] LBA97:
It won't, the only problematic model is the M571C, have fun :D
[Meizu MX] GuestD0098:
How can I check which model my m2 note is..?
[Meizu MX] LBA97:
Check the store page you bought it from. If you bought it from China, then probably it's a M571C. Good luck :)
[Meizu MX] Qeemi:
Read under device info in settings menu
[Meizu MX] Nnayou:
Need help from masters of knowledge.

Thanks you, very good work. Unfortunately I'm not really skilled in phone flashing. I am confused, I tried 3 ways to install twrp (with flash tools, with flashify and even with ADB) and it doesn't work.

Everything seems to be good during the process (no issues) but when I'm trying to access twrp (power + volume level UP) I reach a flymeOS recovery mode.

I'm confused because I strictly followed instructions. :confused:

Can you help me, please ? :o
[Meizu MX] sacha2506:
Nnayou ,

I had the same problem being 5.10.1.0, with TWRP kit needrom his works.

however the root was very complicated, I have not managed to put busy box, I said that I keep Flyme os on my phone

sorry for bad English
[Meizu MX] Nnayou:
Don't worry, I'm not english too. I'm not sure to understand, you don't succeed to install twrp too ?
[Meizu MX] sacha2506:
Yes , but with TWRP and spflashtool of needrom it's ok for me
[Meizu MX] Nnayou:
WOW, I was not sure to understand what to do, but I downloaded a TWRP rom of M2 note on needrom. And it's work

I can say now whoever you are, Big up, you're my savior ! Thanks you ! :victory::fingers-crossed::good:
[Meizu MX] sacha2506:
:good:
[Meizu MX] uvemas:
Hi,

I'm using M571U. Is this guide useful for me?

TIA

PS: I'm new to this forum and not an Android developer. Please, feel free to tell me if my question is not appropriate.

---------- Post added at 05:04 PM ---------- Previous post was at 04:55 PM ----------

OOPS!

I've just seen posts #17 and #18 answering this question. Sorry for the noise guys.

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

I bought mine from China via Amazon. No stickers glued on the phone and the model info not available under Settings but... there is a sticker with the model on the phone box.

---------- Post added at 06:28 PM ---------- Previous post was at 06:11 PM ----------

Hi,

first of all, sorry if this is a stupid question. I've replied to post #19 by clicking its Reply button. The reply has been added to post #29 (my first post to this forum) instead of being a post on itself. I don't understand why.
[Meizu MX] harold.goldensky:
How can i lock the bootloader again? Do i just need to flash stock recovery?
[Meizu MX] LBA97:
Yes, flash the stock recovery and then install an update.zip from it. It should lock your bootloader back :)
[Meizu MX] harold.goldensky:
I'm currently using cm12.1 rom, do i need to flash update.zip first to go back to flyme os then flash stock recovery?
[Meizu MX] LBA97:
First flash the stock recovery or you'll get a brick. From that recovery install the update.zip
[Meizu MX] harold.goldensky:
Any flyme os version will work? Thankyou your help sir. Did you already try this? Do you have stock recovery sir? Thankyou.
[Meizu MX] Xtian Rey:
Remove the 3 preloader images inside the update.zip then u could easily flash it with twrp.
[Meizu MX] LBA97:
I have twrp because I don't want to lock the bootloader back, but if I wanted to lock it I would.

You can do it this way, but I think he wants to lock the bootloader, that's why I told him to flash the recovery first.

Anyway you can of course flash Flyme without having to lock the bootloader.

Good luck and nice to help you :)
[Meizu MX] Xtian Rey:
Oh i never knew he wants to lock it again but why lock? Is there a difference having it locked and unlocked? Better off stay unlocked though
[Meizu MX] NiloGlock:
Can I flash official updates via stock recovery with bootloader unlocked or I have to delete the preloader files into update.zip?
[Meizu MX] maxegawa:
Hi, guys, I'm having a little bit of an issue here:

Every time I connect my phone to the PC, it instantly disconnects after 2 seconds or so, specifically speaking the "PreLoader USB VCOM Port (COM3)"

I've been trying to fix this problem in many ways, such as uninstalling the drivers and then installing them again, changing my OSs, charging your phone 'til 100% and then connecting it to the PC, but nothing seems to work. I come to the conclusion that it is purely a phone related problem/ "feature" .

Does any of y'all have a solution for this? Also, my M2 Note model is the M571H.
[Meizu MX] LBA97:
Download you have a Windows 10? Do you know you have to allow the unsigned drivers to install? It's on the tips. Also you should follow another tip I put. Select download before connecting the phone to the pc. Once you have hit the download button connect your phone and it will work :)
[Meizu MX] LBA97:
You should delete the preloader files, or you'll get a brick.