Flyme 7 Coming to Older Phones Like Meizu PRO 5.. to see click here :fingers-crossed:
It's good news, currently only 4.7% of mobile phones have Oreo.
The trouble is until Flyme gets stable
And if there are new drivers maybe someone (@faust93) is able to port it to Resurrection Remix 6, which is still in beta on most phones
You just have to wait and all the pieces are put together
They just released the Meizu 15 with Android 7.1.2. and Flyme OS 7, does not even come with Oreo.
I'm very disappointed!
Meizu is one year behind in the design and software of its mobile phones. They pass the fashions without offering anything.
I expected them to catch up, but nothing. He's going to win a bad name forever.
They will end up putting the sign closed for vacations, which we already know what it means.
Above, they do not pay Google for having Google Play well. The International Version is a fake, they aren't Certified
And they also have blocked the bootloader so you can not install any ROM (there are none in the Meizu Pro 6, Pro 7).
My next mobile will not be a Meizu is clear. In 2015, they competed with Xiaomi, I thought that they would get over them but they have chosen very bad strategies, such as making several versions (China, the International), moving away from Google, problems with apps, very similar designs for all their phones, prices that are too high compared to the competition , many software failures in Flyme, without Android updates ...
Luckily I have it with RR and Android 7.1.2 (in 3G and without finger print but this does not matter at all). And I'm happy with him !!
You do not need another Android if you have it well customized (Substratum, Exposed, Magisk Manager ..).
But it would be cool to have RR with Oreo..
Flyme 7 is out since 22.04.18 and IS NOT BASED on Oreo
It's again based on Nougat 7.0
I've tried 7.8.4.22 A, not soo bad, some little bugs with camera and other things but overall 's good
in 2022 i bet they are going to have oreo
or meizu will die
Meizu has disappointed me so much that I bought another mobile (not from Meizu). I have endured so much thanks to the Faust93 ROM but I could not do it anymore, it was a little on a whim, more than other things
Meizu was downgrading ever since 2015 and their strategy to focus on the Chinese market with dozens of new devices every year led to abandoning all their previous flagships and lack of focus on software updates. Obviously providing regular up-to-date upgrades does not bring in too much revenue compared to the new devices ranging from budget to flagships that bring in millions. This fact showed their real face - hunt for money rather than for creating an outstanding product and attracting even more customers. Pro 5 is my first Meizu phone and is definitely the last one. Even with running RR 7.1.2 and fully and smoothly functioning hardware, I do really lack fingerprint option and I don't like having any sacrifices on the device. which once used to be a flagship and still has pretty powerful insides to date. I like trying different roms and flashing firmware, but for the testing purposes, not because I am forced to in order to have more or less up-to-date Android version and properly working Google Services and Play Store. This is just ridiculous and disgusting.
Did someone tried flyme 7, this version 7.8.5.8?
hi everybody.
I'm surfing the internet.
https://www.getdroidtips.com/flyme-os-7-meizu-pro-5/
I came across this site.
I downloaded and installed the Meizu pro5 Flyme 7.0.2.0A from the https://www.flyme.cn/firmwarelist-23.html#3 link provided on the site. I got backup of my phone. I've installed wipe cache. And it works.
I wanted to share it with you.
Notes:
- I had a flyme 6.3 rom.
- I installed vipe cache from the first installation. sim network did not work. vipe cache cleaning and installed all functions worked.
-Flyme has added facial recognition and works very nicely.
- Press the power button. I installed the version uplink type. As described in the first link. (https://www.getdroidtips.com/flyme-os-7-meizu-pro-5/)
-I've been using it for two days. very nice. Flyme7 is the original system board and stable.
- Before loading, change the ro.product.locale = zh-CN line in the zip file (update.zip/system/build.prop) to -> ro.product.locale = en-US.
- Bad news - I use English. Problems can occur in other languages.
The pro5 really got android 8.0!?
Maybe I should (after switching to the global version a year ago) back to the chinese roms...
Are the google apps all working? Incl. contacts etc?
Thanks already for the update!
pro 5 now is with oreo??
i´m speechless lol
Unfortunately nope, Oreo was only a dream for us
kanaxe said:
hi everybody.
I'm surfing the internet.
https://www.getdroidtips.com/flyme-os-7-meizu-pro-5/
I came across this site.
I downloaded and installed the Meizu pro5 Flyme 7.0.2.0A from the https://www.flyme.cn/firmwarelist-23.html#3 link provided on the site. I got backup of my phone. I've installed wipe cache. And it works.
I wanted to share it with you.
Notes:
- I had a flyme 6.3 rom.
- I installed vipe cache from the first installation. sim network did not work. vipe cache cleaning and installed all functions worked.
-Flyme has added facial recognition and works very nicely.
- Press the power button. I installed the version uplink type. As described in the first link. (https://www.getdroidtips.com/flyme-os-7-meizu-pro-5/)
-I've been using it for two days. very nice. Flyme7 is the original system board and stable.
- Before loading, change the ro.product.locale = zh-CN line in the zip file (update.zip/system/build.prop) to -> ro.product.locale = en-US.
- Bad news - I use English. Problems can occur in other languages.
Click to expand...
Click to collapse
can i use this as daily driver? any bugs etc?
Mollic said:
can i use this as daily driver? any bugs etc?
Click to expand...
Click to collapse
U can use it as daily rom, it's almost near to perfection. But it's not new, it's 2018.08.10 so 3 months old.
:good:
Hi all,
Since it seems there are not updates coming for the global version of pro5 anymore I am considering to switch to the Chinese ROM.
Is it possible to install the latest Chinese version to a GLOBAL Pro5?
If it is a more complex process, do you have instructions a link that shows how to do it?
Thanks a lot!
Jan
badreligion said:
Hi all,
Since it seems there are not updates coming for the global version of pro5 anymore I am considering to switch to the Chinese ROM.
Is it possible to install the latest Chinese version to a GLOBAL Pro5?
If it is a more complex process, do you have instructions a link that shows how to do it?
Thanks a lot!
Jan
Click to expand...
Click to collapse
i think you have to change the product label to chinese ( i tried without doing so and i failed miserably )
it's depend on what recovery you use to update, stock or TWRP. If with TWRP, you need to replace bootloader and recovery in zip to be unlocked bootloader and custom recovery.
This post is about the OFFICIAL Galaxy Note 8 Firmware Release, not the Leaked Released or Custom Mod Releases. DO NOT ASK QUESTIONS or INFORMATION that apply to Leaked or Custom Mod Releases. Only Information and Questions about the OFFICIAL Samsung Firmware.
For the One UI Sign-up Update, scroll a bit down after the App Compatibility List until you see OneUI Update from Samsung Representative about OneUI Beta Sign-up
For App Compatibility, it's below you here!
App Compatibility
As of testing on the Galaxy Note 8, the following apps on Build N950U1UEU5ZSAB do not work (Pre-Loaded Apps Only):
Game Tuner (Missing Game Optimizing Service)
Samsung Members (No access to Beta Forums, Feedback or Notices)
Samsung+
Voicemail
As of OneUI Release, the following apps do not work (Regular Applications):
TBD
OneUI Update from Samsung Representative about OneUI Beta Sign-up
So I recently got in touch with a Samsung Representative a few hours ago as the Samsung Members App, the app that controls Beta Feedback, Forums, and Notices on the Android Pie Release (OFFICIAL not the Leaked Build) due to me getting an error saying that either my Samsung Account or my own device are not registered for the OneUI Beta. The rep during the call informed me that, according to a Samsung Account Representative, the Beta Signup is technically closed as of now. Yes, you can still keep running Samsung's OneUI as is but you cannot register into the Samsung Members App or Open Beta Items unless you managed to update early or have an unlocked device. I'm still unsure about updates that Samsung will send out due to this but I think Updates should be released as normal still for Android Pie. So far my device, a T-Mobile Galaxy Note 8 is what is getting the error and other devices **may** get this error.
I noticed this small bug after flashing the N950U to N950U1 Unlocked and then Flashing the Android Pie Update via Recovery Mode and once I finished the installation. Samsung+ will just crash on OneUI even after reinstalling via Google Play and Galaxy Apps and Samsung Members as already mentioned will work, but you won't get access to the beta feedback, beta forums, or notices from Samsung.
This isn't a news report that should steer you away from trying OneUI. You can still give it a shot by following the guide by Mr. Orange by flashing Pie via Recovery Mode for now as Samsung+ will no longer work for Android Pie Beta Updates, but you will be sort of limited by what you can give back to Samsung due to their Open Beta now being a Closed Beta. If you are still unsure about updating to OneUI, then don't risk it. Even though 99.99% of Flashing always end perfectly right with OneUI, there may be that chance that it can go wrong but very slim. ALWAYS make sure you backup your data before flashing. You can do so in Settings -> Cloud & Accounts -> Backup and Restore -> Back up data, and it will be backed up to Samsung Cloud or do the manual copy everything to your PC and transfer to your phone afterward method.
Issues on OneUI Beta:
Secure Startup + WQHD Bug - https://forum.xda-developers.com/galaxy-note-8/how-to/psa-android-pie-beta-secure-startup-t3891634
Fix on Reddit: https://www.reddit.com/r/GalaxyNote...inside_theres_a_bug_in_the_note8_pie/ee7fwyv/
- Playing Audio may pause a bit when doing other tasks on the device. Noticed on Samsung Music while testing a few FLAC files with Dolby Atmos against my previous settings. Both had audio cut out a bit while browsing Chrome or Discord with and without Sound Effects
Reserved Part 2
[29Apr: Just discovered the Samsung Galaxy Tab Q&A forum, I've moved this post to it]
Seeking Collective wisdom: firmware choice: Samsung Galaxy Tab S2 SM-T810
I'm looking for best bets for choosing a good firmware update for this older tablet that I still like.
The tablet recently got very flaky on Android 5 so I let it install an auto-downloaded image for Android 6. The new image probably came from Samsung since I was told at purchase that device had official Samsung firmware for Android 5.1.1. (see ABOUT DEVICE below)
Things got worse on the new Android 6 image, so bad that I'm ready to install new firmware by sideloading.
1. Since the device was rooted by prior owner (see: DEVICE HISTORY below for details) I am guessing I have little to gain by sticking with an official Samsung image--unless nothing else works. Does that sound right? And, does anything prevent me from going the non-Samsung route?
2. If it makes sense at this point to try a non-Samsung image, my question for folks here boils down to this: where am I likely to have the best luck finding a build that will work well on the device? For example, I wonder
who are the most experienced makers of firmware for this older tablet?
and which version of Android--7 or 8? Should I avoid 8 or go for it?
(I've seen an unofficial Lineage OS build for Android 8. I believe that Android 7 builds exist, too.)
Thanks for any suggestions.
MORE:
(I've waited so long to update because a) I seldom use the tablet and b) seller said that he'd had problems with a German Nougat and had reverted to official Android 5.1.1. )
[ABOUT DEVICE:
## 190425 from Settings / About device
- SM-T810 Model
- 6.0.1 Android version
- 3.10.9-7767647 Kernel version
[email protected] #1
Mon Apr 25 19:57:48 KST 2016
- April 2, 2016 Android security patch level
- MMB29K.T810XXU2CPD9 Build number (aka firmware no.)
- Enforcing SE for Android status
SEPF_SECMOBILE_6.0.1_0010
Mon Apr 25 20:17:25 2016
- MDF v2.0 Release 6 Security software version
VPN v1.4 Release 6.1
- KNOX 2.6 KNOX version
[omitted a lot more KNOX stuff]
- DC 5 V; 2 A RATED
- 5870 mAh Battery capacity
]
[DEVICE HISTORY, as far as I can say:
I bought in 2017 on swappa.com. Seller told me "What you would get out of the box is the official Samsung OEM firmware for Android 5.1.1 (XAR-T810XXU2BPB1-20160323135521) with the official Samsung recovery. Updates will apply without issue, either by directly loading with Odin or SmartSync, or doing an OTA firmware update....It is running pure stock firmware now. Since it was rooted at one point, the Samsung Knox flag is tripped. It's the only thing that would distinguish this device from a new-in-box tablet."]
I'm wondering if I'll be able to install a stock Google android Q GSI as the phone supports project treble. Wilinstalling through fastboot or Odin trip Knox?
Is there a way to get Q without rooting the device?
I'm running Pie with the April security patch
Flashing official ROMs won't trip knox. You'll probably need to wait for the first beta to get released to get a flashable zip.
Also, I don't see any Android 10 based rom. Even if you root, there is nothing at the moment that you can flash. A lot of OEMS pushed already update with beta based on android 10 even Huawei. Sadly, Samsung is not one of them :crying:
Android Q Beta 3 is heading to 21 phones — here's the full list
So I am currently on a HD1910 a OnePlus 7T Pro McLaren (not the 5G variant) that I bought from a Chinese merchant when it first launched but I think it is considered the India version for some reason. (screenshots attached)
I was using the phone for work but today it seems my employer's policy enforcement on the phone using VMWare Hub failed with "Andriod for Work - Sept 1st 2022 requirement Non-Compliant" since Oneplus Oxygen 12 is still stuck on Aug security patch right now. (screenshots attached)
Q1. What ROMs are the best options to migrate to if I wanted to keep passing my company's VMWare Hub check? (there is a "not root", "os version", "android encryption" check as well)
Q2. In order to update to Pixel Experience 13 Plus Edition I need to downgrade from Oxygen 12.1 to Oxygen 11 per https://wiki.pixelexperience.org/devices/hotdog/install/ , where can I find the 11 ROM for my variant of hardware?
Q3. Is there special steps that I need to follow when installing VMWare Hub and letting it setup my Android for Work profile when running under the Pixel Experience 13 Plus ROM?
Q4. During any part of this migration am I going to lose data on the phone? (need to reinstall all the apps, etc)