• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[ROM][8.1.0][OFFICIAL][Cancro] Pixel Experience

gujiangjiang

Senior Member
Oct 5, 2011
188
144
0
Nanjing
gujiangjiang.renren.com


Pixel Experience for MI 3 and MI4 [cancro]
Code:
[SIZE="3"]/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */[/SIZE]
What is this?
An AOSP based ROM, with gapps included, and all Pixel stuffs (launcher, wallpapers, icons, fonts, bootanimation).

Based on Android 8.1



Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
NFC(MI3W Only)
Lights
Sound / vibration


Known issues
You tell me

DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website

Translation
Help with project translation

Telegram channel
Stay tuned for something awesome

Cancro ROM release channel
Star me and get the latest ROM information


XDA:DevDB Information
Pixel Experience, ROM for the Xiaomi Mi 3

Contributors
xda dmf
Source Code: https://github.com/PixelExperience

ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: MPSS.DI.4.0-eaa9d90
Based On: AOSP

Version Information
Status: Stable
Current Stable Version: 8.1.0-20181004-1313
Stable Release Date: 2018-10-04

Created 2018-10-05
Last Updated 2018-10-05
 

Attachments

Last edited:

gian_48

Member
Dec 24, 2015
18
1
0
the bug i was found
1. whatsapp video call show a green in camera,
2. i think speaker is too loud, when i play some music in full volume the speaker like broken
 

milad192

Senior Member
May 10, 2010
76
6
0
1-Instagram can't paly videos and some body can't install from play store
2-Some applications can't be install from play store
3-Whan play game or work long time phone will be reset
4-Dark mode in massage don't work
5-And nobody answered questions and read post
We don't know rom updat or not...
???????
 

Stickman89

Inactive Recognized Developer
Apr 5, 2007
1,615
2,428
0
Milton Keynes
Now I'm curious... Since nobody has reported this issue yet. This ROM failed to install via TWRP (3.1.0-0) due to a failure in the updater-script, and so I checked the script. It performs two checks before proceeding with the installation.

1) is that the device in question is a supported device, and it does this this by checking the property 'ro.product.device'. If it does not retrieve "cancro" as a result from the query, it fails, and so the installation is aborted.

2) that you are running baseband 'MPSS.DI.4.0', and it does this by performing the command 'cancro.verify_baseband'.

Super confused. How is it my cancro device (Mi3W) failed these two checks, and aborted installation.

So I check the device_check.sh script located within the ROM installation package, just to double check results there. Even though that script isn't even called upon until much later in the updater-script. In fact the end of the script... After the system and boot image has been extracted/patched. Little late in the script to be double checking that, don't you think.

Anyway, using shell I issued the command 'cat /sys/devices/system/soc/soc0/raw_id', and of coarse returns the id 1978. Which is Mi3W, and which device_check.sh even confirms. As previously mentioned, this is much to late within the script, the updater-script was failing at the beginning of the script.

So despite already knowing I am on the correct, and latest baseband. I locate the full fastboot image for the stock MIUI build this ROM is targeting. V9.6.3.0.MXDCNFD.

After flashing the full fastboot stock image this build targets, reinstalling TWRP, then flashing a re-downloaded version of this build. I am still presented with the premature failure as a result of the two early checks, are you cancro and does the returned baseband version contain "MPSS.DI.4.0'. I am, and it does.

Anyway, I ended up removing the first two lines (assertion checks) from the updater-script and the installation completed successfully and as normal. The ROM boots up without any problem to. I am just to curious as to why nobody has mentioned a similar story yet.
 
Last edited: