[UNOFFICIAL][13.0][6.0.1][2017-04-18] LineageOS 13.0 for Xiaomi MiPad (mocha) - Xiaomi Mi Pad ROMs, Kernels, Recoveries, & Other D

Here is one more ROM for Mi PAD. This one I consider as stable daily driver.
What working:
audio
sensors (autorotation)
wifi
3D graphics
hardware accelerated video playback
camera
SD card and USB mounting
gapps
Known problems:
not enough space to install gapps in /system
microphone doesnt work
you have to merge 2 system partitions in one to install 2017-02-25 and newer builds
2017-02-21
Initial release
download: lineage-13.0-20170221-UNOFFICIAL-mocha.zip
2017-02-25
changelog:
whole new audio based on opensource tinyhal (microphone should work both builtin and headset). Please report any regression.
new libwvm means widevine drm should work now
big system partition (1.2Gb). You have to install it on merged system1 and system2, if you have already merged just install.
SD card mount fix included (previosly avaliable as boot.img)
Wifi uses unique device MAC addres from /BKB partition
cleaned some useless blobs like powerservice daemon
download:lineage-13.0-20170225-UNOFFICIAL-mocha.zip
2017-03-07
changelog::
Added settings for enable Navigation bar ( check in Settings -> Buttons). Hardware keys disables when nav bar switched on.
Vibration intensity setting (check in Settings -> Sound)
Settings for notification and battery LED (color, intensity)
Settings for buttons backlight intensity
Added ffmpeg codecs for format unsupported by hardware or google, like flac
Download: lineage-13.0-20170307-UNOFFICIAL-mocha.zip
2017-04-18
battery animation on offline charging
userspace cpquiet governor by default (resolves all lags in video)
updated hwui props in build.prop (improve screen stability, less black pixels in chrome)
bigger shader cache (seems to little improved graphic perfomance)
updated wifi driver and firmware
hope finally resolved wifi disconnection issue by disabling IpReachability monitor
Download: lineage-13.0-20170418-UNOFFICIAL-mocha.zip
Fix for 2017-04-18 build
fixed boot.imgboot-20170420.img
MAC address loading fixed
Resolved issue with wifi Switch On
Added hardboot exec patch for work as main rom for MultiROM
gihub source code links:
Device tree (cm-13.0 branch)
Kernel (cm-13.0 branch)
Vendor blobs (cm-13.0 branch)
Thanks for author of this repository for building custom webview.apk manumanfred/android_external_chromium-webview
Merge partitions
Mi Pad by default has 2 /syetm partition, each 640Mb. It is not enogh to install LineageOS and Gapps. To install 2017-02-25 build and newer you have to merge 2 system partition in one 1.2Gb system partition. To dod this follow instruction http://en.miui.com/thread-118294-1-1.html
Root Access
If you want root acces flash SuperSU zip https://forum.xda-developers.com/apps/supersu
XDA:DevDB Information
LineageOS 13.0 for Xiaomi MiPad (mocha), ROM for the Xiaomi Mi Pad
Contributors
highwaystar_ru
Source Code: https://github.com/HighwayStar/android_device_xiaomi_mocha
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod, LineageOS
Version Information
Status: Beta
Created 2017-02-21
Last Updated 2017-04-20

Reserved

so no way to flash gapps via twrp ? how to do this merge thing ? pls make a tutorial...

love this rom, better than cm12.1.
smooth as butter! highly recommended!
thank you highwaystar

OoSTARTERoO said:
love this rom, better than cm12.1.
smooth as butter! highly recommended!
thank you highwaystar
Click to expand...
Click to collapse
Any bugs u encountered so far. Video playback/some lags/restarts?

I have no words to describe except what @OoSTARTERoO said.
I am starting to really love my mipad.
Kudos to @highwaystar_ru
Camera is working fine.
I will check with Antutu after some time.
Anyway, I cannot seem to use sd card as internal storage .. is this a bug ?

@highwaystar_ru omg i cant believe this ur literally One Man Army

Thanks a lot Highwaystar.. Real thanks for keeping the MiPad alive.

darryl1234 said:
@highwaystar_ru omg i cant believe this ur literally One Man Army
Click to expand...
Click to collapse
HighwayStar is one-man army:good:

hell1134 said:
I have no words to describe except what @OoSTARTERoO said.
I am starting to really love my mipad.
Kudos to @highwaystar_ru
Camera is working fine.
I will check with Antutu after some time.
Anyway, I cannot seem to use sd card as internal storage .. is this a bug ?
Click to expand...
Click to collapse
This from myfriend
AnKiT ([email protected]):For all who were searching for Extsdcard... its in /mnt/media_rw/9016-4EF8Go to the directory and from options add shortcut to Desktop.. and access External Sdcard from desktop... ?
Click to expand...
Click to collapse

thanks @highwaystar_ru!!! You are the best one!!

VALRCIEL said:
This from myfriend
Click to expand...
Click to collapse
I think I mis-explained. I can access SD card from file manager, but, I cannot set it as Internal Storage - adoptable storage feature of MM roms.
---------- Post added at 08:51 PM ---------- Previous post was at 08:33 PM ----------
OK ... found a solution to gapps installation.
1) Install the rom
2) Boot
3) Reboot to recovery
4) Backup the ROM in SD Card (internal will be erased)
5) Wipe - advanced - select all except SD card & OTG
6) Reboot to recovery
7) Restore the backup from SD card
8) Reboot to recovery (again)
9) Install gapps (I use pico)
10) Reboot.

I used this ROM and almost everything is OK except HW decoding in MX Player / VLC.
There're some lags when I watch movie with MX / VLC.
Otherwise, very good ROM, thx.

Here's an easier and quicker way to install gapps:
-> Repartition /system
-> Install the ROM
-> From the TWRP main menu, select Wipe -> Select Advanced -> Select the system partition and click on Repair or change file system
-> Click on resize
-> After the process is done, flash gapps.
This would mean no waiting for twrp to backup and restore the entire partition. Fair warning though, I have tested this on one of my other devices, not the Mi Pad. Though I am pretty sure it'll work, it'll help if someone tried it and reported so that it can be added to the OP.

As is said before. saver and god of mipad(MOCHA) @highwaystar_ru.

Is this really good for daily use?

@highwaystar_ru can't we install gapps pico version without merging the memory.

Navin9 said:
@highwaystar_ru can't we install gapps pico version without merging the memory.
Click to expand...
Click to collapse
Nope. Partition is too small and free space after installing ROM is about 73mb. Pico gapps requires about 140 mb.

(Guide) How to merge system1 & system2. And how to flash CM13.
1. Download the bin file from : here
2. Place it in /sbin folder in root using any root file explorer, set permissions 755 (check image in attachments)
3. Download Repartition zip from : here
4. Reboot into recovery.
5. Flash Repartition zip (downloaded in step 3). After flashing this recovery will reboot automatically.
6. Now Wipe everything except internal and external storage. (Create backup of your current ROM just in case, if you want.)
7. Flash latest Lineage OS 13 zip.
8. Go to Wipe > Advance > Select 'System' > Repair and Resize Filesystem > Resize file system.
9. Go back and flash gapps zip + superuser zip.
10. Reboot now

Guys you won't believe it this ROM is amazing. This is smoothest ROM on mi pad . I'm sharing some screen shots . Thisron worth a shot folks.

Related

[G800F/M/Y][ROM][6.0][MHC19J] CyanogenMod 13.0 for G800F/M/Y [Beta 25/03/2016] [eol]

CyanogenMod is discontinued.
This ROM is continued as a LineageOS ROM.
Check the G800F LineageOS ROM for more info.
This is a CyanogenMod 13.0 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y) by CTXz and hennymcc.
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H.
Working features
Internal Root
Brightness slider
Option to use soft keys
Additional settings (Buttons menu in settings)
HW accelerated GUI
Camera (pictures+video: Back+Front)
MTP storage
Flash Light
Bluetooth (A2DP, HFP, HID)
IR
Lock Screen
Sound
SMS
Initiate and receive calls
Wifi
Mobile Data
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
NFC
Hardware sensors (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter)
Light sensor (needed for auto-brightness)
Pulse sensor (preliminary and very inaccurate. Works with Apps like Kardiograph)
SD-Card as internal storage (new Android M feature)
GPS
Multi-Window support (new experimental CM setting, can be enabled via developer settings)
Fingerprint scanner
Non-working features:
SELinux
Known issues:
See the Bug Report section of this thread
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 3.0.0 recovery image [25/03/2016] (AndroidFileHost Mirror)
The newest CM 13.0 releases as well as the latest TWRP can be found here:
https://aykevl.nl/android
-Credit and thanks to @ayke
CM 13.0 ROM for G800F/M/Y (Android File Host)
Google Apps (contains Google Play, ...) for Android 6.0, one of the following two is recommended:
Open GApps Project, Platform:ARM, Android:6.0, Variant: whatever you prefer (e.g. "mini" or "nano")
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 13.0.
Flash CyanogenMod:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CyanogenMod zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM 13.0 ROM zip-package
Install the GApps zip-package
How to root:
No SuperSu is needed as CyanogenMod already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
25/03/2016:
* USB OTG disabled by default for improved waterproofness (can be re-actived via Advanced Settings App)
* how to enable USB OTG:
* start the "Advanced Settings" App
* open the "USB-OTG Mode" setting
* select "Powered (Not waterproof)"
* add support for call recording
* how to record a call:
* start/Receive a call with the CM Dialer App
* During call open settings (icon: three vertical dots)
* Select "record call"
* (if you get an error message that recording failed, try to enable developer settings and enable root access for apps+adb)
* how to playback recorded call:
* open the call history in the Dialer app (icon: clock symbol)
* open details of recorded call
* in the detailed calling list, click on the play button for the recorded call
* removing fingerprints works now
* updated some stock libs with LP versions
* support for F2FS (needs new TWRP recovery)
* updated TWRP recovery (with F2FS support)
* synch with latest CM sources
22/02/2016:
* Fixed lock-screen freeze
* Fixed Infrared support
* Fixed search for mobile networks (search will take ~1min until results are shown)
* Updated some libs with LP versions
* Initial support for a fingerprint scanner
* Sync with CM sources
16/02/2016:
* Fixed camera problems with WhatsApp
* Fixed preferred radio family settings (LTE/GSM/...)
* Added default long-press actions for home and app-switch buttons (DJSteve)
* Switched to LP kernel (G800FXXU1BOL4)
* libsensors: replaced with open source implementation (fixes light sensor which is needed for auto-brightness)
* Preliminary (and very inaccurate) support for heart-rate sensor
* Update to TWRP 3.0 (TWRP 2.x will still work)
* Sync with CM sources
30/01/2016:
* Fixed BT calling problems (only noise)
* CM Camera replaced with CM Snap Camera
* better image quality (check picture quality settings), resulting in image file sizes of > 1MB instead of 200KB
* Saving images to SD card supported (check settings)
* Improved RIL support
* Use stock soft-key layout (left capacitive button is app-switch instead of menu now)
* Key-layout can be configured via button settings.
* Fixed adb root problem (root permissions were lost after reboot)
* SamsungServiceMode app works now
* Sync with CM sources
14/01/2016:
* Add soft keys option under settings > buttons
* Fix crash after hanging up call
* Sync with newest CM sources
31/12/2015:
* Receiving calls works now
* psyafter: SD-Card can be used as internal storage (new Android M feature).
Can be used to store photos on SD-Card.
IMPORTANT: the SD-Card will be formatted if you activate this feature.
* GPS works now
* Sensors work now (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter).
Light and Pulse sensors do not work yet.
* Youtube/Screencast crash fixed
26/12/2015:
* Wifi and Mobile Data work
20/12/2015 Hennymcc :
* Audio Fix
- Audio is now working (Still a bit quiet though)
- Making Calls is now working
14/12/2015 Hennymcc, CTXz :
* 6.0.1
- Updated to Android 6.0.1
- Fixed reboot when locking phone
- Fixed Internal Root in developer options not working
30/10/2015 CTXz :
* Added 'Buttons' settings
- Integrated Buttons/Capacitive Keys menu into settings
- Double tapping or holding button to open camera now works (In CM12 it didn't work)
- Power Menu is added under buttons menu
- Minor fixes
-!- NOTE : Setup Wizard may have some issues/crashes with this build. I will exclude it in the next one
29/10/2015 CTXz :
* Synced to newest sources
- Ugly looking Google search box removed
28/10/2015 CTXz :
* Changed from eng to userdebug
- No more red frames flashing
- Fixed Browser crashing
- Fixed crash after first boot
- More user friendly
- No additional boot.img flashing required
28/10/2015 hennymcc:
* First CM 13.0 test-build
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by two persons (CTXz and hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to CTXz for his awesome work on getting Marshmallow to the G800F
Thanks to spookcity138 and ayke for providing new builds of this ROM.
Thanks to Psyafter for some patches and working on the G800F.
Thanks to Unjustified Dev from Team Regular for the initial work to get the G800F ready with CM.
XDA:DevDB Information
[G800F/M/Y][ROM][6.0][MHC19J] CyanogenMod 13.0 for G800F/M/Y [Beta 25/03/2016] [eol], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, CTXz, spookcity138, psyafter, Unjustified Dev, ayke
Source Code: https://github.com/cm-3470
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version >= 15/08/2015]
Based On: CyanogenMod
Version Information
Status: Beta
Created 2015-10-28
Last Updated 2017-01-26
If you already flashed stock LP, you will get the following message on boot:
KERNEL/RECOVERY IS NOT SEANDROID ENFORCING
If you wait for some seconds (or press some buttons) the message text turns blue:
KERNEL/RECOVERY IS NOT SEANDROID ENFORCING
and after some seconds (or buttons presses) CM will start.
Reserved
You (both of you) are making a great job !
Envoyé de mon SM-G800F en utilisant Tapatalk
$wap said:
You (both of you) are making a great job !
Envoyé de mon SM-G800F en utilisant Tapatalk
Click to expand...
Click to collapse
Ditto!
Sent from my SM-G800F using XDA Premium HD app
I don't see the point in cm13 when we didn't even get official Lollipop required to make cm12 better, "legit". Can someone enlighten me...?
Is it supposed to have the same bugs as cm12 or will there be more of them? Is Marshmallow statistically faster than Lollipop on other phones?
hennymcc said:
This is just a test build.
At the moment you have to flash the following boot.img with Odin after installing CM 13:
https://www.androidfilehost.com/?fid=24052804347848059
CM 13 may reboot after the initial configuration and may not be able to start again. I wiped the data partition and started again. This time it worked without a reboot (I also choose English as language and did not configure Wifi).
Click to expand...
Click to collapse
Updated the link with the boot.img build in
---------- Post added at 07:37 AM ---------- Previous post was at 07:33 AM ----------
n3n00 said:
I don't see the point in cm13 when we didn't even get official Lollipop required to make cm12 better, "legit". Can someone enlighten me...?
Is it supposed to have the same bugs as cm12 or will there be more of them? Is Marshmallow statistically faster than Lollipop on other phones?
Click to expand...
Click to collapse
CM13 is for people that enjoy its minor speed boost, smoother animations, cool new features and less Android related bugs over Lollipop. If you want a, well... almost bugless experience (Cough cough touchwiz) then use the stock rom.
CTXz said:
Updated the link with the boot.img build in
---------- Post added at 07:37 AM ---------- Previous post was at 07:33 AM ----------
CM13 is for people that enjoy its speed and less internal bugs. If you want a, well... almost bugless experience (Cough cough touchwiz) then use the stock rom.
Click to expand...
Click to collapse
Hi, so you think it will be easier to make a CM13 version with less bugs than the unfinished CM12 (Yes / No) ?
I enjoy to use a rom for every day not just having the last version to amaze my friends...
Depends. What I know for sure is that bugs related to Lollipop will be fixed. However we are hoping to get it as stable as cm12 if not more
Screehots
Screenshots with phone frame
Screenshots within Android
What‘s the current status of the mobile-data-connection in this build? Is it working?
In the first build of CM12.1 is was not working.
My experience was that this feature was always a problem in the beginning-time of every CM-build. Even with the official CM-builds.
WarStars said:
What‘s the current status of the mobile-data-connection in this build? Is it working?
In the first build of CM12.1 is was not working.
My experience was that this feature was always a problem in the beginning-time of every CM-build. Even with the official CM-builds.
Click to expand...
Click to collapse
We didn't build the correct RIL yet but it should be working in hopefully only few builds
New update
Download link has been updated
Changed from eng to userdebug
- No more red frames flashing
- Fixed Browser crashing
- Fixed crash after first boot
- More user friendly
- No additional boot.img flashing required
Also for anyone asking if there are really some differences in Marshmallow compared to Lollipop. Yes, the animations are allot smoother. There are some new native features. It has cleaned the mess of Lollipop's Android related bugs and is what Lollipop should have been from begin on. It is snappier than Lollipop and I can see/feel that. You may have realized that gingerbread-ish google toolbar. This is CM13 related since the official CyanogenMod 13 source is still in beta. However we no longer have the problem that the toolbar is laggy, instead it has a smooth animation when selecting it.
Could you please give some information when the RIL is done? Thank you in advance.
WarStars said:
Could you please give some information when the RIL is done? Thank you in advance.
Click to expand...
Click to collapse
It's on our priority list so hopefully soon
You know I have both the G800H and the G800F (the camera bug on the G800H prompted me to get the G800F), and now I don't know which one I should get rid of... I know, I know: "hard problem there KC... ya bloody wanker"
CTXz said:
It's on our priority list so hopefully soon
Click to expand...
Click to collapse
Awesome job so far, guys!
Sent from my SM-G800F using XDA Premium HD app
New update
Download link has been updated
Synced to the newest CM13 sources
- Ugly looking Google search box removed
CTXz said:
New update
Download link has been updated
Synced to the newest CM13 sources
- Ugly looking Google search box removed
Click to expand...
Click to collapse
Working features from page 1 still the same for this new build?
Sent from my SM-G800F using XDA Premium HD app
Mobile connections working now?

[6.0] Omni nightlies for Find 7a/7s

Download:
http://dl.omnirom.org/find7
Kernel source:
https://github.com/omnirom/android_kernel_oppo_msm8974
Google space:
https://goo.gl/spaces/TdBgFFTWcbqDHNRYA
XDA:DevDB Information
Omni nightlies for Find 7a/7s, ROM for the Oppo Find 7
Contributors
maxwen
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Current Stable Version: 6.0
Created 2015-10-30
Last Updated 2016-02-04
Oppo Firmware package 2.1.5
You must run firmware 2.1.5 BEFORE flashing this ROM
If you come from ColorOS 2.1.5 you dont need to to anything else
flash this in recovery
https://drive.google.com/file/d/0B4vRAhHheUkxeUZuSFR3WGVxOE0/view?usp=sharing
md5sum f60e482f29cd238d9e2a5b5bcf682139
3rd party camera apps
For better camera experience using oppo camera apk is possible e. g.
http://www.xda-developers.com/coloros-camera-on-opo-great-port-great-option/
http://forum.xda-developers.com/oneplus-one/themes-apps/port-coloros-camera-cm11s-t3030369
BUT using a non standard camera app is not supported in any way so if you have issues you are on your own.
Known issues
-NFC beam not working
FAQ
How to get root?
Install SuperSU >=2.68 from recovery http://forum.xda-developers.com/apps/supersu
I cant access my internal storage after converting to LVM?
Run the following command in a terminal (you need to install SuperSU before)
Code:
su
restorecon -RF /data/media/0
Is LVM supported?
Yes - actually at the moment only LVM is tested
Non-LVM setup might work but is untested from me
How to setup LVM?
Here is one tutorial http://forum.xda-developers.com/showpost.php?p=64266122&postcount=2035
Backup link for setuplvm https://drive.google.com/file/d/0B4vRAhHheUkxLTZRMlhaRXdKS0U/view?usp=sharing
Can I upgrade from 5 to 6 by dirty flashing?
No - 6 must be flashed clean with proper gapps
I have problems with xposed,viper4android - can you help?
GTFO
Why is encrypt phone is not working?
Most prolly reason is that the /data partiton is missing the needed footer to store encryption keys
If that is the case you can run a resize partiton in TWRP
Use Wipe -> Advanced Wipe -> check Data -> press "Repair or Change ..." -> press Resize
This will resize the partition and free that little space
This is in general save and can be done without loosing data
BUT just to be sure make a backup of ALL in /data - including /sdcard
Does this ROM support Android Pay
Nope
Does this ROM support f2fs
Nope - If for whatever reason you have f2fs partitions you must convert them to ext4 BEFORE flashing
How to encrypt the device
Best do after factory reset before flashing ANYTHING - especially before xposed and SuperSU
gapps:
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
Wow!!! Exciting!!!!!
I can't wait!
wow i will waiting you
..
You're on fire.
Gapps downloaded, now waiting for the best part
In case you guys didn't notice @maxwen already uploaded a test build on 2nd post. Downloading now.
Minor bug. Distance between battery and network indicator.
Edit: new bug encounter. When switching from front camera to back it FC.
Thanks Maxwen, this is impressively stable for an early test! A lot of force closes start when adding GAPPS, but some of these can be mitigated by granting all permissions to them in Settings > Apps.
Pojiku said:
Thanks Maxwen, this is impressively stable for an early test! A lot of force closes start when adding GAPPS, but some of these can be mitigated by granting all permissions to them in Settings > Apps.
Click to expand...
Click to collapse
I didnt face any fc for any gapps. Do you use gapps provided in 2nd post?
Right now im exploring it and notice battery optimization is not there yet? Whenever i enable it for all apps it will revert back.
Oh ****... until this afternoon I can't install it
javier.pc said:
Oh ****... until this afternoon I can't install it
Click to expand...
Click to collapse
Why? For flashaholic this is something new and fun.
why am i getting different colors?
Bookmarking this
Is it LVM compatible ?
StormTrooper89 said:
Edit: new bug encounter. When switching from front camera to back it FC.
Click to expand...
Click to collapse
known: it also FCs sometimes when you exit camera
benoita74 said:
Bookmarking this
Is it LVM compatible ?
Click to expand...
Click to collapse
ONLY lvm since I wont test anything else
Pojiku said:
Thanks Maxwen, this is impressively stable for an early test! A lot of force closes start when adding GAPPS, but some of these can be mitigated by granting all permissions to them in Settings > Apps.
Click to expand...
Click to collapse
gapps are a PITA with 6
make sure you do a factory reset before flashing gapps
StormTrooper89 said:
Right now im exploring it and notice battery optimization is not there yet? Whenever i enable it for all apps it will revert back.
Click to expand...
Click to collapse
details please
i can switch that voodoo setting on and off

[ROM][AOSP][manta] Classic Pie 08-2019 / AospExtended-v6.7 (DISCONTINUED)

It's AOSP time ..
Android Pie ..
manta-Classic_Pie_08-2019_AOSP_9.0.0_r46_followmsi.zip --> DISCONTINUED
AospExtended-v6.7-manta-20191018-1203-UNOFFICIAL.zip --> DISCONTINUED
Known issues:
- NavBar works good, but no icons visible. (AospExtended only)
- NFC may not work correctly and drains a lof of battery - Pls disable thru settings menu.
- HWC (hardware composer) is partly broken (icons are not shown correctly and black home screen)
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- Camera is not working .. same problem like on Nougat. (broken HAL1 camera and unsupported HAL2 camera)
- If you set pin, pattern or password to unlock the device pls be patient - if you press "confirm" the system is freezing for a few minutes - just wait.
Oreo ..
manta-Classic_01-2019_AOSP_8.1.0_r60_followmsi.zip --> DISCONTINUED
Known issues:
- Headphone jack is not fully working (Pls use the "AudioJack" kernel -> 3.4.67 - current standard kernel for all Oreo ROMs)
- If you install Magisk, pls disable Magisk "Hide" feature. (3.4.113 kernel issue)
- NFC has been taken out - still not working.
- Camera is not working .. same problem like on Nougat. (broken HAL1 camera and unsupported HAL2 camera)
- If you set pin, pattern or password to unlock the device pls be patient - if you press "confirm" the system is freezing for a few minutes - just wait.
Nougat ..
AOSP_7.1.2_r28_N2G48C_manta-ota-eng.followmsi-v1.zip --> DISCONTINUED
Known Issues:
- Camera is not working (broken HAL1 camera and unsupported HAL2 camera)
- Bluetooth is not working - fixed
- Audio jack is not working - fixed (still "old" kernel - 2017-05-09)
System and Cache repartitioning / Opengapps: Error 70
The current system partition is (getting) full !
You need to do repartition your system and cache partitions .. either via TWRP package or manually via shell.
It's an one time task.
But the filesystem of the system.img inside the ROM will keep always the same size .. approx. 800mb.
The filesystem does not know the "real" size of the actual partition.
In general .. If you install an image into a partition the filesystem will have the size of the image (in our case 800mb).
The free space we got thru repartitioning needs to be allocated again.
For this reason we need to enlarge/resize the filesystem after each ROM update and/or clean install.
Only the filesystem .. the partition itself will stay untouched.
The automatic enlarge/resize of the filesystem is part of the ROM installer.
For manual repartitioning have a look here:
https://forum.xda-developers.com/showpost.php?p=77759823&postcount=953
https://forum.xda-developers.com/showpost.php?p=77762148&postcount=954
For automatic repartitioning have a look here:
https://forum.xda-developers.com/showpost.php?p=77764246&postcount=957
https://forum.xda-developers.com/showpost.php?p=77770425&postcount=960
@ipdev - Thanks for your TWRP flashable repartitioning package !
Installation:
1. Boot into TWRP
2. Wipe system, cache and dalvik (Not required if you upgrade from previous build)
3. Install ROM.zip from above
4. install opengapps or beansgapps (arm) (optional)
5. install SuperSU.zip and/or Magisk.zip
6. Reboot into system
- Please install Magisk.zip and/or SuperSu.zip yourself.
- Due to systemless rooting - if you have installed magisk and/or supersu before you need to install it again !
- If you install SuperSu.zip it will boot twice - no panic, it's normal !
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- If you face any strange issues, pls do a factory reset via TWRP first.
Gapps:
The AOSP installer does not support "/system/addon.d/" scripts !
For this reason Gapps are not persistent like in LineageOS or in other custom ROMs.
I have modified the installer script to add this functionality.
You should be able to keep your gapps installation when you upgrade the ROM.
SuperSU and/or Magisk:
SuperSU.zip and/or Magisk.zip has always to be installed after ROM installation/upgrade - because of systemless rooting.
If you install SuperSu.zip it will boot twice - no panic, it's normal !
SOURCES:
If you want to build your own ROM ..
https://github.com/followmsi/manifests/tree/manta-aex-pie
https://github.com/followmsi/manifests/tree/manta-aosp-pie
https://github.com/followmsi/manifests/tree/manta-aosp-oreo
https://github.com/followmsi/manifests/tree/manta-aosp-nougat
DOWNLOAD:
https://androidfilehost.com/?w=files&flid=289294
https://drive.google.com/open?id=0By6p5AdQfavBNHkxVWhNOW5CdVk
Thanks to @sooti and @Khaon !
Enjoy
Is this "Pixel C" version with new tablet recents?
stunned said:
Is this "Pixel C" version with new tablet recents?
Click to expand...
Click to collapse
Most probably not .. it seems they are not part of AOSP yet - they are included in stock firmware.
Tested the new "stuff" on my Pixel C running AOSP as well .. the "new" mutil windows view did not work as in stock firmware.
Maybe it's related to the new Pixel Launcher .. maybe they are "hidden" and not activated in AOSP.
Also the battery usage alerts were not working on Pixel C ASOP build.
Need to check this ..
Maybe I need to do a complete wipe and start from scratch to get all the new nice stuff working ? .. )
You may have test yourself on manta ...
Cheers
followmsi said:
Most probably not .. it seems they are not part of AOSP yet - they are included in stock firmware.
Tested the new "stuff" on my Pixel C running AOSP as well .. the "new" mutil windows view did not work as in stock firmware.
Maybe it's related to the new Pixel Launcher .. maybe they are "hidden" and not activated in AOSP.
Also the battery usage alerts were not working on Pixel C ASOP build.
Need to check this ..
Maybe I need to do a complete wipe and start from scratch to get all the new nice stuff working ? .. )
You may have test yourself on manta ...
Cheers
Click to expand...
Click to collapse
Pixel c has its own Aosp tree or branch or whatever it is called. We already have the different navkey layout which is not available on phone aosp.
stunned said:
Pixel c has its own Aosp tree or branch or whatever it is called. We already have the different navkey layout which is not available on phone aosp.
Click to expand...
Click to collapse
For the pixel c AOSP version I have used the pixel c branch.
Still not working ..
Just installing new pixel c launcher on the pixel c to see the difference .. if at all.
We will see if and how we can "enable" those features .. on manta hopefully too.
Sent from my AOSP on dragon using Tapatalk
Keep getting error Bluetooth share keeps stopping, flashed with gapps, and without, same error
dnp77 said:
Keep getting error Bluetooth share keeps stopping, flashed with gapps, and without, same error
Click to expand...
Click to collapse
Yep .. will have a look.
Plenty of Bluetooth changes in 7.1.2.
Thanks for the info.
SetupWizard
If you do a clean install and install opengapps there are issues with the gapps "SetupWizard" on 7.1.2 !
Have a look here ...
https://forum.xda-developers.com/showpost.php?p=71740178&postcount=267
You can also mount system (RW) and type:
Code:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
in TWRP terminal. This will allow you to bypass the SetupWizard altogether on a clean flash.
As it looks like the gapps team is working on an replacement SetupWizard for 7.1.2 ..
Cheers
New version ..
AOSP_7.1.2_r2_N2G47E_manta-ota-eng.followmsi-v2.zip
Installation:
1. Boot into TWRP
2. Wipe system, cache and dalvik (no need to wipe system if you upgrade from previous build)
3. Install AOSP_7.1.2_r2_N2G47E_manta-ota-eng.followmsi-v2.zip
4. Install open_gapps-arm-7.1-xxxx-2017xxxx.zip (optional)
5. Install SuperSU-v2.79-201612051815.zip (optional)
6. Reboot into system
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- Due to supersu installation it will boot twice - no panic, it's normal !
- If you face any strange issues, pls do a factory reset via TWRP first.
- The SetupWizard from gapps is still buggy on 7.1.2
- Camera is not working
Changes:
- Bluetooth is working now !
Enjoy
Audio jack not working
Nicholas1994 said:
Audio jack not working
Click to expand...
Click to collapse
Thanks for the info .. same/similar problem like in LOS 14.1
Have updated the know issues now ..
Known Issues:
- Camera is not working
- Audio jack is not working
- Bluetooth is not working - fixed in v2
Not sure when the Audio jack issue will be fixed ..
Cheers
followmsi said:
Thanks for the info .. same/similar problem like in LOS 14.1
Have updated the know issues now ..
Known Issues:
- Camera is not working
- Audio jack is not working
- Bluetooth is not working - fixed in v2
Not sure when the Audio jack issue will be fixed ..
Cheers
Click to expand...
Click to collapse
What kernel are you using? this is what you should be using. the issue has something to do with changes in merges beyond 3.4.67, try mine if you want a working kernel with headphone support
sooti said:
What kernel are you using? this is what you should be using. the issue has something to do with changes in merges beyond 3.4.67, try mine if you want a working kernel with headphone support
Click to expand...
Click to collapse
Cool .. This works well
Compiled a new kernel using your sources .. really nice.
Thanks a lot !
New manta kernel .. fixing Audio jack !
manta-kernel_kernel-flasher-5.1-20170409.zip
manta-kernel_kernel-flasher-5.1-20170409.zip.sha1
Installation:
1. Boot into latest TWRP
2. Install manta-kernel_kernel-flasher-5.1-20170409.zip
3. Reboot into system
No need for SuperSU ... or anything else.
The installer will take care.
Thanks to @sooti for the information.
Enjoy
Audio jack Works fine now , thanks for a super rom ?
AOSP - Music.apk
The current Music AOSP app is not working .. google did forget to implement a patch
https://groups.google.com/forum/#!topic/android-rpi/LNUCjXXvn2U
This problem occurs on all 7.1.2 AOSP ROMs.
Here is the patch:
https://android.googlesource.com/pl...+/6036ce6127022880a3d9c99bd15db4c968f3e6a3^!/
Have cherry-picked this patch now and compiled the Music.apk again.
You still need to manually grant access to "storage" for the app.
Made a quick installer to replace the broken apk ..
AOSP_7.1.2_r2_Music.apk_fixed-for-Android-N_manta.zip
Maybe I will remove the app next release completely.
Cheers
Grid view
Google has activated the "grid" view of your recent apps for a few devices in 7.1.2.
It's part of AOSP already.
If you would like to use this feature .. just activate it
Pls type inside terminal app as root ..
mount system RW:
Code:
mount -o rw,remount /system
activate grid:
Code:
echo "ro.recents.grid=true" >> /system/build.prop
Reboot into system ...
I am not sure if we should activate this view per default in the next release.
Some comments please
followmsi said:
Grid view
Click to expand...
Click to collapse
For tablet layout and a 10" screen size I prefer recents grid view, thanks for the hint. :good:
Now all the fresh changes are included ...
AOSP_7.1.2_r2_N2G47E_manta-ota-eng.followmsi-v3.zip
Changes:
- Added new kernel to fix Audio jack
- Enabled "Grid View" per default
- Fixed Music.apk
Installation:
1. Boot into TWRP
2. Wipe system, cache and dalvik (no need to wipe system if you upgrade from previous build)
3. Install AOSP_7.1.2_r2_N2G47E_manta-ota-eng.followmsi-v3.zip
4. Install open_gapps-arm-7.1-xxxx-2017xxxx.zip (optional)
5. Install SuperSU-v2.79-201612051815.zip (optional)
6. Reboot into system
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- Due to supersu installation it will boot twice - no panic, it's normal !
- If you face any strange issues, pls do a factory reset via TWRP first.
- The SetupWizard from gapps is still buggy on 7.1.2
- Camera is not working
Enjoy
To finalize the manta kernel testing I have made a last version ..
Activated 1 more governor .. and used a cherry-pick to speedup AC charging.
manta-kernel-aosp_kernel-flasher-5.1-20170413.zip
Changes:
- ONDEMAND CPU governor activated
- The kernel has included changes to speed up AC charging
Installation:
1. Boot into latest TWRP
2. Install manta-kernel-aosp_kernel-flasher-5.1-20170413.zip
3. Reboot into system
No need for SuperSU ... or anything else.
The installer will take care.
If you face any strange issues, pls let me know.
Enjoy

[ROM] JAGUAR PIE OFFICIAL NON-TREBLE V6, updated August 7

Here is Jaguar Pie. In addition to familiar Pie features (all of them), you have:
Official Telegram Link: https://t.me/jaguar_Rom_Official
The main thing: Non-treble! So, your vendor is located in system partition, which is NOT available to the entire world, like in treble roms.
1. Hardened/fortified bionic (over 150 commits) to prevent bad behavior by system and third party apps
2. Most runtime processes are read only, which means they can't be exploited to take over the device. I am trying to attack the cause, rather than the symptoms (a specific exploit)
3. Many kernel security features activated, such as 'configuration_integrity', randomization; hardened user copy, etc. Impulse governor added
4. Yama security in kernel
5. Working msm hotplug, which actually plugs/unplugs CPU based on load
6. Wakelock blocker, Alarm blocker etc
7. Gestures, Omni Theming
8. Smart pixels
9. Offline charging
10. Utouch
11. AOD
12. No response to 'type zero' SMS
13. Boot time on a fully settled rom is about 4-5 seconds after Zuk logo
14. Qualcomm's boost framework
Many more features, which I am tired to list.
This is beta, because I don't have the device - relied on @Dr.07 @The.Night.King and @benedict97 - thanks for testing
INSTRUCTIONS:
1. Format System/Vendor (if you have it)/Data/Dalvik/Cache. If you are encrypted in Oreo or encrypted with FBE, you also need a format with factory reset to get rid of encryption. ALSO: FORMAT FACTORY partition, otherwise, you will have 2 sets of vendor blobs, which would create a mess on boot
2. Flash the rom, flash Gapps, reboot and let the rom run, then
3. Back to TWRP to flash Magisk (18.1 is working)
Rom download V1: https://forum.xda-developers.com/devdb/project/dl/?id=31427
This is the initial release. All future updates will be in post #3, as usual.
Credit: MrHacker (I used his device tree as a base) and many others who work on device tree and kernel and obviously AOSP, OMNI, DU, CopperheadOS, Carbon Rom, Xtended and Benzo
Also, credit for a Jaguar bootanimation to @Ashish9 and @The.Night.King who made a logo and header icon
If anyone is interested in Afwall with administrative option restored (app can't be uninstalled, unless confirmed by you): https://forum.xda-developers.com/attachment.php?attachmentid=4739733&d=1554836212
XDA:DevDB Information
[ROM] JAGUAR PIE NON-TREBLE 3.18 KERNEL OFFICIAL, ROM for the Lenovo ZUK Z2 (Plus)
Contributors
optimumpro
Source Code: https://github.com/optimumpr/kernel_zuk_msm8996
Sources for new (May 29) kernel: https://github.com/optimumpr/android_kernel_zuk_msm8996-1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.1.x
Based On: AOSP, DU, Lineage
Version Information
Status: Beta
Current Beta Version: V1
Beta Release Date: 2019-04-05
Created 2019-04-05
Last Updated 2019-08-07
Screenshots
Some screenshots:
Updates in this post
Those who are coming from treble roms: you need to format Factory partition too, otherwise, you will have 2 sets of vendor blobs, in other words, MESS
August 7. New release.
1. August security patches
2. Google r46
3. Camera should have level 3 now + more
Dirty flashing is fine, if on the previous release. Otherwise, clean flash - wipe Vendor/Factory/System/Data/Cache/Dalvik
Download rom V6: https://forum.xda-developers.com/devdb/project/dl/?id=31753
July 30: New release V5.2 with fixed installation problems:
You could try dirty flash, but I installed clean, then flashed Opengapps, and Firefox installed without any problems, while it didn't on V5.1.
Download rom V5.2: https://forum.xda-developers.com/devdb/project/dl/?id=31733
July 27. New release, v5.1.
This will fix encryption.
The reason it didn't work was the official TWRP. The maintainer (a known pro) put in the wrong size of userdata partition. So, if you ever formatted data on official TWRP, especially with factory reset, your data partition is screwed for the purposes of encryption (no place for crypto footer). I had to install another version of TWRP, and after I did format there, encryption worked. So, I am attaching both the rom and unofficial TWRP by handibuddy. This is also a signed version (as well as the rom itself), so you can re-lock bootloader on this rom: I have been doing this for ages and long before Lineage came up with the idea (you can check my signing guide in Oneplus 5 thread).
Download Rom V5.1: https://forum.xda-developers.com/devdb/project/dl/?id=31727
Download signed TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=31728
Instructions: Rom could be flashed dirty over V5. TWRP could be flashed as image (to recovery) in your existing TWRP or via fastboot.
Just remember, if you want to relock bootloader, encrypt after locking.
July 25. New release, v5
1. July security patches
2. New Night Screen with configurable tint and brightness
3. Support for level 6-6.2 for AVC codecs
4. Option to disable proximity sensor during calls
5. In-CallUi is now themeable
6. Aggressive battery saving mode
7. Latest Lawnchair
Clean flash is required over V4 or if coming from a different rom, in which case you will also need to format vendor or factory partition.
DO NOT ENCRYPT YET!
Instructions:
1. Dirty flash, if already on Jaguar Pie
2. Clean flash, If coming from a different rom, also format vendor/factory/system/data/cache/dalvic
3. Flash the rom, flash GapDirty flash is fine, if on a previous release. Otherwise, clean flash.
Download rom V5: https://forum.xda-developers.com/devdb/project/dl/?id=31725
________________________________________________________________________________________________________
June 6. New release, V4:
1. June security patches
2. Pie r41
Dirty flash is fine, if on a previous release. Otherwise, clean flash.
Instructions:
1. Dirty flash, if already on Jaguar PieClean flash
2. If coming from a different rom, also format vendor/factory/system/data/cache/dalvic
3. Flash the rom, flash GapDirty flash is fine, if on a previous release. Otherwise, clean flash.
Instructions:
1. Dirty flash, if already on Jaguar PieClean flash
2. If coming from a different rom, also format vendor/factory/system/data/cache/dalvic
3. Flash the rom, flash Gapps, reboot, then back to TWRP to flash Magisk
ps, reboot, then back to TWRP to flash Magisk
Download rom V4: https://forum.xda-developers.com/devdb/project/dl/?id=31621
______________________________________________________________________________________________________________________
June 2. Lawnchair update to the latest. Flash in TWRP.
Download Lawnchair: https://forum.xda-developers.com/attachment.php?attachmentid=4770317&d=1559500522
May 31. Rom updated, V3:
1. Major kernel improvements - there is no reason to use my Oreo kernel or any other kernel
2. Flashlight works regardless of 'always on' or 'ambient display' (that required a clean flash)
Instructions:
1. Clean flash recommended - wipe system/data/cache/dalvik
2. If coming from a different rom, also format vendor/factory
3. Flash the rom, flash Gapps, reboot, then back to TWRP to flash Magisk
Download rom V3: https://forum.xda-developers.com/devdb/project/dl/?id=31612
_____________________________________________________________________________________________________________________
May 30. This is an updated version of the new kernel I posted earlier. This one contains my commits + reversed 'power saving' commits. Sometimes, you get things better by reversing.
Unzip, put on internal SD and flash either with TWRP (as image onto boot partition) or via fastboot.
Download new kernel: https://forum.xda-developers.com/attachment.php?attachmentid=4768179&d=1559177914
May 28. Lawnchair update. Flash in recovery:
Download Lawnchair: https://forum.xda-developers.com/attachment.php?attachmentid=4767269&d=1559060237
May 27. Updated release:
1. Fixed toggling flashlight in ambient display
2. Improvements in Qualcomm's boostframework
3. Contactsprovider updated (disappearing contacts)
Could be dirty flashed over V2. Otherwise, clean flash.
Download rom V2.1: https://forum.xda-developers.com/devdb/project/dl/?id=31602
May 25. New release, V2:
1. May security patches
2. Android Pie r37
3. Big changes in frameworks: exec spawning function is severely restricted to all apps, i.e., only one instance is allowed
4. Most resources preloading for exec spawning is disabled. As a result, boot time is shorter, fewer background resources are loaded in ram, which translates into an overall smoother experience.
5. Aggressive battery saving
6. Status bar burn protection
7. Media cover art filter (on lockscreen)
8. Switched to Bromite system webview V74
9. Redone auto-brightness and ambient display: ZukDoze removed, as Customdoze and Amibientdisplay are now builtin (Settings/Display)
10. Lawnchair upgraded: many fixes including Pie recents
11. MusicFX/Equalizer is now themeable
12. Zukparts removed, as spectrum profiles simply don't work, and KCAL could be done via Kernel Adiutor
13. Battery icon Q style
14. Wifi randomization working (Developer Settings)
15. Captive portal detection toggle (Settings/Wifi/Advanced - disable network connectivity check). You can now uninstall Captiveportal and have no 'x' in Wifi and Mobile icons
Instructions:
1. Clean flash required
2. Format system/vendor (or factory, depending on what you have)/data/dalvik/cache; if you were encrypted in Oreo or FBE in Pie, in addition, do factory reset
3. Flash the rom, flash Mind the Gapps or Nano Gaps, reboot. Then back to TWRP and flash Magisk
If your provider's APN is not on the list, set it up and enable. If data doesn't work, then change CDMA subscription in Mobile network to the alternative.
Download rom V2: https://forum.xda-developers.com/devdb/project/dl/?id=31591
__________________________________________________________________________________________________________________
April 9. New release. Lots of changes, mostly in kernel:
1. Inteli-thermal
2. Thermal-engine ported from Jaguar Oreo, so the rom runs about 3 degrees cooler
3. Substantially improved fluidity: according to testers, virtually no lag
Instructions:
1 If on a previous release, flash dirty and wipe dalvik/cache
2. if new, format system/vendor (or factory, depending on what you have)/data/dalvik/cache; if you were encrypted in Oreo or FBE in Pie, in addition, do factory reset
3. Flash the rom, flash Mind the Gapps, reboot. Then back to TWRP and flash Magisk
Download rom V1.1: https://forum.xda-developers.com/devdb/project/dl/?id=31467
_____________________________________________________________________________________________________________________
April 5. Here is the first update, kernel only. Speed improvement.
Just flash boot.img on top of the first release.
Download kernel: https://androidfilehost.com/?fid=1395089523397933955
Finally ?
@optimumpro Thank you. Respect?
Thanks for the work! ?
Woh!!!!...... Waiting for a detailed review by someone.....
Wow finally
vinay069 said:
Woh!!!!...... Waiting for a detailed review by someone.....
Click to expand...
Click to collapse
your prediction turned out pretty accurate about the release date lol
All right, boys and girls. First update: kernel only - speed improvement . Download (in post #3) and flash on top of the first release
Yess! The best! Gonna flash this aftermy exams!
By the way @optimumpro does this contain the dual audio mod which was in Oreo?
Also any screenshots?
GopalKaul said:
Yess! The best! Gonna flash this aftermy exams!
By the way @optimumpro does this contain the dual audio mod which was in Oreo?
Also any screenshots?
Click to expand...
Click to collapse
Screenshots posted. Stereo sound - not yet.
optimumpro said:
Screenshots posted. Stereo sound - not yet.
Click to expand...
Click to collapse
The 1st build is the one I'm using, right? The tweaked dalvik one, so should I flash only the kernel?
BTW can you add GPU driver 331 instead of 319? Since you're using 319 instead of 269, why not 313?
The.Night.King said:
The 1st build is the one I'm using, right? The tweaked dalvik one, so should I flash only the kernel?
BTW can you add GPU driver 331 instead of 319? Since you're using 319 instead of 269, why not 313?
Click to expand...
Click to collapse
Hey brother... Can u help me. ..?
Currently on aex 6.4 and done all this to flash aex..
Now what do i do to go back to beast jaguar?
Shubhi singhal said:
Hey brother... Can u help me. ..?
Currently on aex 6.4 and done all this to flash aex..
Now what do i do to go back to beast jaguar?
Click to expand...
Click to collapse
Just flash rom
The.Night.King said:
The 1st build is the one I'm using, right? The tweaked dalvik one, so should I flash only the kernel?
BTW can you add GPU driver 331 instead of 319? Since you're using 319 instead of 269, why not 313?
Click to expand...
Click to collapse
Kernel only.
venom0207 said:
Just flash rom
Click to expand...
Click to collapse
Seriously?.... Is my twrp correct and nothing to do with vendor and factory at all?
Shubhi singhal said:
Seriously?.... Is my twrp correct and nothing to do with vendor and factory at all?
Click to expand...
Click to collapse
@optimumpro animations r fekked
Shubhi singhal said:
Seriously?.... Is my twrp correct and nothing to do with vendor and factory at all?
Click to expand...
Click to collapse
It is non treble, factory or vendor have nothing to do with it, you can straight away flash the rom
Flashed the ROM.
It took a lot of time to boot.
Swipe up home screen is not showing any options
Recents is not pie recents
Very fast ROM
In some themes, the notifications are invisible

[ROM][12][BECKHAM] PixelExperience 12 OFFICIAL [AOSP]

PixelExperience 12 for Moto Z3 Play [beckham]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
NFC
Lights
Sound/vibration
Known issues
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
Android OS version: Android 12
Security patch level: October 2021
Build author/Device Maintainer: jeferson1979
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Flash instructions:
Download THIS RECOVERY;
Make a backup (you already are in the right forum for search how to do it )
Format data; (yes format)
Install PixelExperience zip;
Install TWRP INSTALLER to make additional flashes;
Reboot;
proofit
Disclaimer:
THIS IS AN ALPHA RELEASE, ALL THE BASIC FUNCTIONALITIES ARE HERE, BUT IT'S UP TO YOU INSTALL.
Builds moved to BETA at https://download.pixelexperience.org/beckham
We now are on OFFICIAL state (stable):
For the next stage we are moving to retrofit dynamic partitions scheme
don't worry, it's totally safe and you can go back at a/b scheme at any moment
INSTRUCTIONS:
1- You need Pixel Experience recovery installed (MANDATORY -TWRP WON'T WORK)
If you are on PixelExperience 11 you already must have installed, it works. if not, download from PE website
2-You need to install retrofit zip to convert your device
Download here
3- Go to PixelExperience recovery and format your data, then sideload or install from sdcard previosly downloaded retrofit.zip. Format your data and reboot to recovery.
4-Download the updated build of PixelExperience from here, sideload or move to your sdcard and install the updated system, format your data and done
FAQ:
1- Can I install magisk in this retrofited system?
yes, you can either sideload by adb or install from sdcard renaming magisk.apk to magisk.zip
2- Why the hell use the retrofited system?
Our system partition is small. Retrofited system allow us to ship all the pixel goodies
reference here
3- How do I go back to the old schema:
Easy as you converted:
- Pick any rom with a/b schema (eg lineage or PE 11)
- Reboot recovery
- Format data
- Flash a/b zip
-Done
DO NOT USE TWRP FOR RETROFITED ROMS, IT WILL BREAK YOUR PARTITIONS
clean install only? how does the update fail?
manck said:
clean install only? how does the update fail?
Click to expand...
Click to collapse
Only clean, because forced encryption is disabled for now
Оk.
And yet another question .... does contactless payment work?
manck said:
Оk.
And yet another question .... does contactless payment work?
Click to expand...
Click to collapse
Well, safety net works, NFC it's up, but untested
the phone does not see the flash card. How can I fix it?
It doesn't show at notification?
the "files" application does not see
the notification hangs in the blind, but you click on it and nothing will open
manck said:
the notification hangs in the blind, but you click on it and nothing will open
Click to expand...
Click to collapse
Will work over that, btw, as I see, payment options worked it seems?
the card is attached, but has not paid yet ... the audio player, by the way, sees the flash drive, the music is playing, but not a single fm sees the flash drive
the payment is working, I checked it this day .... And how is it now for the consumption of the charge?
update last night. So, so nice to me! Very functionally and snappy. I would to say: the sd card no mounted it's my mayor inconvenient.
mosta00 said:
update last night. So, so nice to me! Very functionally and snappy. I would to say: the sd card no mounted it's my mayor inconvenient.
Click to expand...
Click to collapse
Just already update "Google files apk" and now , can read or mount sdcard!!
mosta00 said:
Just already update "Google files apk" and now , can read or mount sdcard!!
Click to expand...
Click to collapse
O! Thank you, it worked great!
The SD card became visible, but the files cannot be deleted and added .... the system does not give permission ..... sadness and sadness ...
Chrome still does not see the SD card. It just looks like waiting for an update
odoes anyone know if bluetooth headset is working?
JLZ9 said:
odoes anyone know if bluetooth headset is working?
Click to expand...
Click to collapse
Working
JLZ9 said:
¿Alguien sabe si los auriculares bluetooth están funcionando?
Click to expand...
Click to collapse
If they work, I use it with xiaomi and they go well.

Categories

Resources