{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[B][CENTER]**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****[/CENTER][/B]
Android Open Source illusion Project
About us:
AOSIP is a quality custom ROM based purely on AOSP. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Harsh Shandilya
Anirudh Gupta
Bug reporting:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Source code:
AOSiP Gerrit Review
AOSiP Github
Kernel Source
Latest Downloads:
Official Server | SourceForge Mirror
Credit/Thanks:
Mike Williams (founder and creator of AOSiP)
Google for Android and AOSP
LineageOS
ABC ROM
AquariOS
BootleggersROM
Dirty Unicorns
PixelExperience
OmniROM
CarbonROM
nathanchance
---------
Other projects whose work helped us to create this
And last but not the least, all our testers, who have helped us to squash many bugs so that we can try to release builds that as are flawless as possible
Hosted and built on
XDA:DevDB Information
Android Open Source Illusion Project, ROM for the Google Pixel 3a XL
Contributors
Skittles9823
Source Code: [url]https://github.com/AOSiP[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: May 2020 security patch
Based On: AOSP
Version Information
Status: Official
Created 2020-02-04
Last Updated 2020-05-25
Installation procedure:
Have an unlocked bootloader (Not gonna be explained here, there'll be threads in this forum somewhere)
Make sure to backup internal storage as wiping data will delete everything.
Reboot to fastboot and flash the provided boot.img with the following commands:
Code:
adb reboot bootloader
fastboot flash boot /path/to/boot.img
reboot into recovery and select "Apply update from ADB":
Code:
fastboot reboot recovery
adb sideload /path/to/rom.zip
In recovery before rebooting, make sure to factory reset/wipe data.
Reboot into the system, and enjoy the illusion!
Update procedure:
Just use the built in updater. Easy peasy.
Updating with Magisk:
Update using the built in updater same as you would without magisk, but when it prompts you to reboot, open magisk manager, tap install for the magisk option > then select "install to inactive slot" > then proceed as you normally would and reboot once it's done.
KNOWN ISSUES:
Currently none, let me know what you find!
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Include your firmware versions in reports.
Mention any and all Magisk modules you might be using along with the Magisk version
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Reserved
Nice! Some new roms showing up! Thanks for your hard work! Is there any links to screen shots or features lists?
Flashed it about an hour ago.... dang.. it is fast! This rom feels really smooth! I use Visible service and it works great on this rom too. I have LTE + (volte). It honestly feels faster then any other custom rom I have tried and faster then stock for sure. And this isn't just because of animation speeds or what not; I always set mine to x0.5. It just is faster and smoother.
Nice job!
Ericarthurc said:
Nice! Some new roms showing up! Thanks for your hard work! Is there any links to screen shots or features lists?
Click to expand...
Click to collapse
I'll have to get some screenshots posted with a current list of stuff in OwlsNest soon.
Ericarthurc said:
Flashed it about an hour ago.... dang.. it is fast! This rom feels really smooth! I use Visible service and it works great on this rom too. I have LTE + (volte). It honestly feels faster then any other custom rom I have tried and faster then stock for sure. And this isn't just because of animation speeds or what not; I always set mine to x0.5. It just is faster and smoother.
Nice job!
Click to expand...
Click to collapse
Nice! Glad you're liking it
Sent from my Pixel 3a XL using XDA Labs
Excellent
Thanks for maintaining it for both Bonito and Sargo
(kshmr_in)
Using adb reboot fastboot didn't work for me.
This is what worked for me for anyone having problems:
After flashing February's stock firmware to both slots, without actually starting the system afterwards, I immediately booted into fastboot by Volume Down + Power.
On the bootloader screen(fastboot not fastbootd) is when i entered fastboot flash boot /path/boot.img.
Next step I did was reboot back into fastboot, and then entered recovery by volume down/enter.
Entering "Apply update from ADB", I then sideloaded AOSiP-10-Alpha-bonito-20200204.zip. (AOSiP-10-Alpha-beryllium-20200204.zip wouldn't flash no matter what process I did)
Rebooted system and everything loaded fast! (When certain processes failed I would get stuck at the boot animation.)
Anyways, its snappy and haven't ran into any bugs.
Great work and i love the boot animation!
godpowerrr said:
Using adb reboot fastboot didn't work for me.
This is what worked for me for anyone having problems:
After flashing February's stock firmware to both slots, without actually starting the system afterwards, I immediately booted into fastboot by Volume Down + Power.
On the bootloader screen(fastboot not fastbootd) is when i entered fastboot flash boot /path/boot.img.
Next step I did was reboot back into fastboot, and then entered recovery by volume down/enter.
Entering "Apply update from ADB", I then sideloaded AOSiP-10-Alpha-bonito-20200204.zip. (AOSiP-10-Alpha-beryllium-20200204.zip wouldn't flash no matter what process I did)
Rebooted system and everything loaded fast! (When certain processes failed I would get stuck at the boot animation.)
Anyways, its snappy and haven't ran into any bugs.
Great work and i love the boot animation!
Click to expand...
Click to collapse
Ahh yea my bad, it's adb reboot bootloader, fixed that in the install instructions post.
As for your beryllium troubles that's because that's another device (Poco F1 to be exact).
Make sure to use the bonito/Pixel 3a XL links in the future.
:good:
Sent from my Pixel 3a XL using XDA Labs
A full wipe is obviously recommended??
thatsupnow said:
A full wipe is obviously recommended??
Click to expand...
Click to collapse
You just need to factory reset after sideloading the rom zip.
Ahh I missed that part in the install instructions, thanks. Just added that part.
Sent from my Pixel 3a XL using XDA Labs
Does the updater work in new build? I tried it on the 1-31 build you posted in Telegram, but it would not download the new update. Just curious. New build is working great. Thank you!
oranget said:
Does the updater work in new build? I tried it on the 1-31 build you posted in Telegram, but it would not download the new update. Just curious. New build is working great. Thank you!
Click to expand...
Click to collapse
Pretty sure updater isn't ready for logical partitioned devices yet.
Sent from my Pixel 3a XL using XDA Labs
Looks incredibly promising! Have been using HavocOS but the kernel it's built with causes issues with ElementalX, and it has several issues such as freezing my music players and crashing my Netflix randomly, causing a total reboot - has this ROM been noted to have either of these issues? I'd prefer to wait until after it's at least in Beta, but if it has less issues than this ROM I'll definitely do a factory reset just to install it!
Karitoriki said:
Looks incredibly promising! Have been using HavocOS but the kernel it's built with causes issues with ElementalX, and it has several issues such as freezing my music players and crashing my Netflix randomly, causing a total reboot - has this ROM been noted to have either of these issues? I'd prefer to wait until after it's at least in Beta, but if it has less issues than this ROM I'll definitely do a factory reset just to install it!
Click to expand...
Click to collapse
I've not had any stuttering issues so far. Definitely haven't been forced to perform a reboot.
Sent from my Pixel 3a XL using XDA Labs
I have been running this since it was released...i have had no issues as well. Solid build!
Thanks dev for the Rom! Very solid.
Btw is there anyway to turn of vibration for notifications and call ringer?
anbinhv said:
Thanks dev for the Rom! Very solid.
Btw is there anyway to turn of vibration for notifications and call ringer?
Click to expand...
Click to collapse
There isn't any notification vibration customisation. What I generally do is disable the "noisy notifications if screen on" option in OwlsNest > notifications and I also disable heads up notifications via the quicksettings tile. It's not exactly the same thing you want but it works for me.
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
I've not had any stuttering issues so far. Definitely haven't been forced to perform a reboot.
Sent from my Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
That unfortunately does not answer anything.. the issues I have with stebo's HavocOS are that media players freeze up after a certain amount of songs are played, causing me to have to force stop it, and that attempting to use Netflix caused a COMPLETE freeze of the OS, whereupon a buzzing sound is heard through the speakers and the phone forces ITSELF to reboot.
Also of importance is ElementalX compatibility, as HavocOS has issues with it - it flashes and applies settings fine, but it completely disables Wi-Fi functionality, in that not even the settings page for it will load.
Regardless of whether or not you know whether or not these issues are prevalent in your own ROM, or how you answer, I'm going to be giving it a try as his January 9th HavocOS release has completely broken my SIM cards' APN, brought Chrome back onto my phone with no way to uninstall it, and made it so the recent apps view loads the Pixel Launcher. I'm sure I won't be disappointed, seeing as you seem much more capable.
P.S.: Your change-log link is 404'd
Related
Right guys you know whats coming.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
P A C man ALL IN 1
Check the Q&A Thread for PAC-specific questions!
ROM INTEL
Here we go then, This is the PAC-man AIO (All-in-one) ROM, for the Xperia TX. Since the TX isnt that different from the T, I compiled it, asked a tester to test it, and here it is! A big shoutout to @Rycon33 who did some extensive testing on the ROM for me.
I'm searching two more testers to test updates before releasing it into the wild. If you want to do so, please shoot me a PM
These testers will get the ROM, they will test it, and after the release to the public will take place.
PAC is a combination of the three biggest ROMs here at XDA. Paranoid Android, Android Open Kang Project and CyanogenMod. It features CM profiles, PA's Hybrid Engine, and ROM Control by AOKP. Everything!
A main complaint under the developers whom originally developed their features about 'mashup' ROMs, is that they are messy, and the different features aren't integrated as well as the individual projects. PAC was the first of all 'mashup' ROMs and has the best integration of them all. It took a LOT of work of thinking behind to merge the frameworks in the right order. These are not just your daily git cherry-pick developers trying to pull money off of XDA
PAC-man has a solid team with good developers and device maintainers, bringing you this totally awesome ROM. :victory:
If you'd like to support me or the PAC developers, be sure to drop them a thanks / beer!
FEATURES
Hybrid Framework
CM10.1
AOKP
AOSPA
Per App DPI
Per App Color
Pie Controls
Open Source Camera HAL
cLock
Hardware Key Control
Any Widget on lockscreen
CM Profiles
Lock Screen Shortcuts
Lock Screen ring target
Fresh compiled CM10.1 kernel
Init.d Support
...
...
...
The list is endless.
BUGS
Basically every bug from CM10.1/FXP
Headphones
Vibration
Camera is a bit buggy sometimes
You tell me... Read down here how to report bugs, which are really usefull to me.
REPORTING BUGS
Source: JellyTime
Code:
How To File a Bug Report with Logcat:
[LIST]
[*] Install android sdk
[*] Install drivers for adb on PC
[*] Connect phone to PC
[*] Open cmd.exe or terminal
[*] Type 'adb logcat' without the quotes
[*] Start the app that causes the issues
[*] Wait for the app to close or get to the error
[*] Copy logcat contents and put in pastebin
[*] Copy pastebin links here
[/LIST]
How To Find Wakelocks:
[LIST]
[*] Install android sdk
[*] Install drivers for adb on PC
[*] Connect phone to PC
[*] Open cmd.exe or terminal
[*] Type 'adb shell cat /proc/wakelocks > wakelocks.txt' without the quotes
[*] Copy contents and put in pastebin
[*] Copy pastebin links on your post
[/LIST]
How To Get dmesg logs:
[LIST]
[*] Install android sdk
[*] Install drivers for adb on PC
[*] Connect phone to PC
[*] Open cmd.exe or terminal
[*] Type 'adb shell dmesg > dmesg.txt' without the quotes
[*] Copy contents and put in pastebin
[*] Copy pastebin links on your post
[/LIST]
Before filing a bug report, please consider the answer to these:
[LIST]
[*] Is the bug reproducible?
[*] How do you reproduce it?
[*] What is the expected behavior?
[*] What actually happens?
[*] Are you on the default Kernel?
[*] Did you restore data of System Apps using Titanium Backup?
[/LIST]
CHANGELOG
Go and check out PAC on github
INSTALLATION / NOOB GUIDE
Unlock your bootloader, if you haven't done so.
Download this the latest version of this badboy!
Grab a copy of the latest GAPPS package
If you come from a stock rom, reboot to bootloader, flash the boot.img from the ROM zip.
Reboot to recovery
Do a "Factory Reset" if coming from any other ROM than the semi-latest version of PAC
Flash the ROM! /system will be automatically wiped during install, as in all good ROMs.
Flash GAPPS
Reboot
Enjoy!
DOWNLOADS
Please be aware that the ROM is throughly tested, but that there are certain bugs!
Grab the latest PAC-man HERE or HERE
Normal GAPPS
Inverted GAPPS
DAILIES
Since shortly, Hayabusa builds are also available on PAC's basketbuild, check it out here: http://pacman.basketbuild.com/index.php?dir=main/hayabusa/nightly/
FAQ
Q: My sound is way too low!
A: Find Pimp My Rom in the Play Store, and install xLoud with it. This can also bring back BE with unlocked bootloaders!
Q: Paranoid Android preferences do not work!
A: https://github.com/ParanoidAndroid/android_vendor_pa/commit/e99a9b192386ca186dfe5a52126ce6fbe7da79a5 - or grab one of the latest ParanoidAndroid ROMs and sideload /system/app/paranoidpreferences.apk
SIGPIC
Code:
http://i.imgur.com/MOG8AGD.png
Fan-art is always welcome
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
a BIG thanks to these people:
szl.kiev and PACman Team
CM team
ParanoidAndroid team
AOKP Team
XDA for just about everything else
@Rycon33 for testing this release
If you think you need to be thanked, just let me know
thanks to techfanatic9 for this.....
so excited to see PACman on TX
thousands of thanks :good::good::good:
Awesome mate, many TX users will surely be happy.
Though still many things to iron-out(see the mentioned bugs and some you need to tell the dev), people will still be quite satisfied with the ROM as I did.
I just want to reiterate that during testing I didn't check if the voice calls are fine(lol it should be the basic thing to test).
Though I think even at this early stage, it's good that everyone gets to test it and it will definitely help the dev more because more feedbacks are going to flow.
So fellow TX users, flash it and give feedback.
Tapatalked from my bricked TX
Rycon33 said:
Awesome mate, many TX users will surely be happy.
Though still many things to iron-out(see the mentioned bugs and some you need to tell the dev), people will still be quite satisfied with the ROM as I did.
I just want to reiterate that during testing I didn't check if the voice calls are fine(lol it should be the basic thing to test).
Though I think even at this early stage, it's good that everyone gets to test it and it will definitely help the dev more because more feedbacks are going to flow.
So fellow TX users, flash it and give feedback.
Tapatalked from my bricked TX
Click to expand...
Click to collapse
I've been running it for the past few hours and everything seems alright.
The headphones don't seem to register but calls do work and everything else seems to be fine.
Keep up the great work, glad to see support for the TX as well.
Daily builds are a fact!
Bluetooth is kinda spotty so I can't accurately say if it works. It worked for a little bit with my radio but then it stopped working and hasn't worked since.
There's also a reboot whenever it tries to install something over 5mb's sometimes. I'm not entirely sure why but it happens whenever it feels like it.
Vibration does not work (already been listed) and the battery is draining kinda fast. Not entirely sure as I haven't fully cycled it but it has been kinda grr from what I've seen.
Also the touch screen calibration seems to be a tad bit off. I often find myself pressing something else when I directly press what I intended. Its not bad to the breaking point but sometimes I have to take a moment to think about what I'm actually pressing.
Now this looks interesting
Will give this a try once i backup all my stuff
UPDATE : my stock rom was rooted, but bootloader was still locked. so i got my bootloader unlocked, and flashed the pacman's boot.img. after booting into CWM, it says that "E: Unable to mount/data" Tried to format /data , /cache, /system , /dalvik-cache, all the same.
Tried TWRP, but also no bueno. Display was cut into half, and also got the same error as CWM. And due to that, I kept getting bootloops
ericmaxman said:
Now this looks interesting
Will give this a try once i backup all my stuff
UPDATE : my stock rom was rooted, but bootloader was still locked. so i got my bootloader unlocked, and flashed the pacman's boot.img. after booting into CWM, it says that "E: Unable to mount/data" Tried to format /data , /cache, /system , /dalvik-cache, all the same.
Tried TWRP, but also no bueno. Display was cut into half, and also got the same error as CWM. And due to that, I kept getting bootloops
Click to expand...
Click to collapse
try to flash it using other kernel including CWM(6.0.X.X )
Good news guys, I've been testing the latest build(2-June) and some issues has been fixed, e.g. still no random reboots here, creating lockscreen shortcuts is Ok now, and many more.
Though some minor issues is still there like no vibration and headset/earphone not detected.
But overall, ROM is really very fluid and smooth. Plus we can use those awesome themes available around. Check out those new themes like flatron theme and simplex theme. They are simply awesome.
EDIT: and we can enter recovery now(from OFF state) by pressing volume button. last time we can go recovery only when we're coming from OS.
Tapatalked from my PACmanned TX
Leo said:
try to flash it using other kernel including CWM(6.0.X.X )
then shutdown and flash the pac boot.img in fastboot mode
Click to expand...
Click to collapse
Thanks for the heads up. I'll give it another try
Rycon33 said:
Good news guys, I've been testing the latest build(2-June) and some issues has been fixed, e.g. still no random reboots here, creating lockscreen shortcuts is Ok now, and many more.
Though some minor issues is still there like no vibration and headset/earphone not detected.
But overall, ROM is really very fluid and smooth. Plus we can use those awesome themes available around. Check out those new themes like flatron theme and simplex theme. They are simply awesome.
EDIT: and we can enter recovery now(from OFF state) by pressing volume button. last time we can go recovery only when we're coming from OS.
Tapatalked from my PACmanned TX
Click to expand...
Click to collapse
Glad to hear that the ROM is improving :good:
Any other bugs that we need to take note of?
PAC 22.4 is here!
djpbx said:
PAC 22.4 is here!
Click to expand...
Click to collapse
Does it fix the headphone bug?
Fuzalert2k said:
Does it fix the headphone bug?
Click to expand...
Click to collapse
Unfortunately, not yet, same as in CM.
Tapatalked from my bricked TX
v23 is up
Any bug solved?
Vibration is very important for me
where can i find the changelog in github....
Leo said:
where can i find the changelog in github....
Click to expand...
Click to collapse
the normal commits of PAC are actually the changelog. you can also visit settings -> about phone -> changelog on your android itself.
navigation bar isnt showing
Just installed the rom and works fine but my navigation bar isnt showing.. can somebody help me with this?
boydje said:
Just installed the rom and works fine but my navigation bar isnt showing.. can somebody help me with this?
Click to expand...
Click to collapse
try to add this line in build.prop(make a backup is suggested)
qemu.hw.mainkeys=0
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
****Disclaimer: We are not responsible if you destroy your device. Use at your own risk.****
Intro:
Features:
Downloads/Changelog/Links:
Pure Fusion:
ROM Downloads
Our Gerrit
Changelogs
Tools/Custom Settings:
Beans GApps:
FULL: Android File Host
MINI: Android File Host
Tips:
You installed the full gapps, but you want to use Snap Camera instead of Google Camera? Flash this zip (Google camera will be removed): Android File Host
Not Working:
Workarounds:
Credits & Thanks:
Our awesome testers!
LineageOS
Dirty Unicorn
AospExtended
SlimRoms
OmniRom
@RenderBroken - For EAS Commits and Help
@joshuous for Vox Populi EAS PowerHAL
@BeansTown106
@jhenrique09
FAQ:
So you want to enter the competitive world of professional ROM flashing? If so, you need to take your phone flashing to a new level. How can you position yourself and your expertise so you are the dev's obvious choice? Be honest. Do you enjoy troubleshooting? Do you have a problem with things going wrong? If so, then you might be better off staying on your current OS.
If you are still reading this and are sitting in your chair thinking: “I could do that, if I tried”, then maybe you have a chance.
If you can't read, watch this video: https://youtu.be/JmvCpR45LKA
Q: I flashed an update and lost TWRP
A: If you have access to a computer, go to 1. No computer and s-off go to 2. No computer and s-on go to 3.
You need to re-flash the TWRP file via fastboot.
Go to this thread: https://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520
Read the instructions before flashing anything. Make sure you choose the right file.
Refer to this post: https://forum.xda-developers.com/showpost.php?p=72875043&postcount=2059
Q: How can I prevent the loss of TWRP when updating?
A: You need to flash root to prevent TWRP from being overwritten.
Note that this is only true for older builds as of July 2017. The problem with TWRP has been resolved as of the first official release of July 2017.
Q: I’m coming from Viper or some other stock-based ROM. What do I need to do?
A:
If you’re encrypted, you need to format (different than wipe. You have to type “yes” in TWRP) your internal storage.
This will wipe everything from your internal storage including TWRP folder with backups, titanium backup, etc. If you have anything you want to keep, move it to external storage or back it up to the computer before proceeding.
If you’re not encrypted, just do a normal wipe (system, cache, dalvik, data) and flash the ROM, gapps, and either SuperSU or Magisk for root.
Q: I want to use this ROM, but I don’t want root. Is that possible?
A: You’re in luck. This ROM does not come pre-rooted. So you can use this with no root if you desire. Although, I’m not sure why you would want to do that, but you can.
Q: My phone reboots randomly
A: Use adb or any other file explorer tool to pull a copy of /sys/fs/pstore/console-ramoops (command: adb pull /sys/fs/pstore/console-ramoops) after the reboot and post that. Try to include what you were doing when experiencing the reboot. Also refer to the next question before filing any reports.
Q: I’m having weird crashes/reboots
A: Do you have other third party software installed such as a different kernel, Magisk, sound mods, etc.? Remove all of these before submitting a bug report. Reports made with unsupported software like what is listed above will not be addressed.
Q: Will this ROM receive frequent Security Updates?
A: Yes
Q: Does this ROM pass SafetyNet?
A: It should if you don’t flash root when installing the ROM, since it doesn’t come loaded with root out of the box. If you want root, Magisk will allow you to pass SafetyNet.
Q: Does OTA work?
A: Yes
Q: Do I need to do a clean install?
A: If you’re coming from another ROM, yes. If you’re already running ours, a dirty flash should be fine unless otherwise specified. If you have problems, try a clean flash before reporting issues. Refer to an above question if you are coming from a stock-based ROM or are possibly encrypted.
Q: Will you add stuff to the ROM?
A: *insert perhaps cow meme here*
Q: Is this a Sense based ROM?
A: No
Q: Does the camera work?
A: See the OP for current stuff not working
Q: Will Stock camera work on this ROM?
A: No
Donate on Paypal:
@Eliminater74: - Lead developer and HTC 10 Maintainer - Donate on paypal
@tabp0le: - Lead developer and HTC 10 Maintainer - Donate on paypal
Device Source Code: https://github.com/FusionDevices/android_device_zte_axon7
Kernel: https://github.com/FusionDevices/android_kernel_zte_msm8996
XDA:DevDB Information
[ROM][EAS][7.1.2_r27]★ Pure Fusion OS ★ Substratum [UNOFFICIAL], ROM for the ZTE Axon 7
Contributors
aclegg2011
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: Purenexus
Version Information
Status: Stable
Created 2017-07-23
Last Updated 2017-09-08
Reserved
Reserved
Thanks can't wait to try.
RUNNERX said:
Thanks can't wait to try.
Click to expand...
Click to collapse
Let us know how you find it!!!
I've used PureFusion on the HTC 10 and it's rapid!!!
Sent from my OnePlus 5 using XDA Labs
Hmm, aclegg2011 and Eliminater74? You know I gotta try it. ?
Any reason for linking the May Beans Gapps instead of the June ones? Just curious.
Flashing as soon as I finish up here. Woohoo!
ZTE Axon 7 A2017U, OctOS ROM, Llama Sweet Kernel, Tapatalk 4.9.5
marcdw said:
Hmm, aclegg2011 and Eliminater74? You know I gotta try it. ?
Any reason for linking the May Beans Gapps instead of the June ones? Just curious.
Flashing as soon as I finish up here. Woohoo!
ZTE Axon 7 A2017U, OctOS ROM, Llama Sweet Kernel, Tapatalk 4.9.5
Click to expand...
Click to collapse
Oversight: just need to update the link.
Please report back on your experience once you have had a moment to try and it let things settle in.
Sent from my OnePlus 5 using XDA Labs
Installed it first thing this morning running fine haven't had any major hiccups other then having to install snap camera
Found another bug. When putting fingerprint in if you don't get it first try it disables fingerprint untill you relock the screen
Installed this rom this morning and all is running well. It's very smooth and fast as advertised. I noticed a few things that are missing however, at least in my experience. These are in no offer except the first one.
1. The Speakerphone bug still exists on this build. It was fixed on the latest build of AOSP Extended. The workarounds do not appear to work either by cutting the screen on or off nor ticking the bottom on or off.
2. There is no option for weather on the lockscreen. This is not a deal breaker but nice to have.
3. There doesn't appear to be a way to remove the input selector in the status bar when you open a text field.
4. Although there's an option to use the fingerprint scanner after reboot, there's no option to unlock after pin without pressing check button.
5. The purenexus Kernel Aduitor zip will not flash in recovery. Error message reads file is not in proper zip format.
6. SELinux preset to Permissive in Dev Ops. Even when changed to Enforcing, defaults back to Permissive.
That's all I could think of at the moment. Other than that, this is a very nice build. Thanks for sharing your work OP!
Sent from my ZTE AXON 7 using Tapatalk
dcscorpio76 said:
Installed this rom this morning and all is running well. It's very smooth and fast as advertised. I noticed a few things that are missing however, at least in my experience. These are in no offer except the first one.
1. The Speakerphone bug still exists on this build. It was fixed on the latest build of AOSP Extended. The workarounds do not appear to work either by cutting the screen on or off nor ticking the bottom on or off.
2. There is no option for weather on the lockscreen. This is not a deal breaker but nice to have.
3. There doesn't appear to be a way to remove the input selector in the status bar when you open a text field.
4. Although there's an option to use the fingerprint scanner after reboot, there's no option to unlock after pin without pressing check button.
5. The purenexus Kernel Aduitor zip will not flash in recovery. Error message reads file is not in proper zip format.
6. SELinux preset to Permissive in Dev Ops. Even when changed to Enforcing, defaults back to Permissive.
That's all I could think of at the moment. Other than that, this is a very nice build. Thanks for sharing your work OP!
Sent from my ZTE AXON 7 using Tapatalk
Click to expand...
Click to collapse
Ill look at the 1 issue. I need to add the selinux fixes so we can run the kernel enforced.
joemossjr said:
Found another bug. When putting fingerprint in if you don't get it first try it disables fingerprint untill you relock the screen
Click to expand...
Click to collapse
Yea, I have to look into this myself.
marcdw said:
Hmm, aclegg2011 and Eliminater74? You know I gotta try it.
Any reason for linking the May Beans Gapps instead of the June ones? Just curious.
Flashing as soon as I finish up here. Woohoo!
ZTE Axon 7 A2017U, OctOS ROM, Llama Sweet Kernel, Tapatalk 4.9.5
Click to expand...
Click to collapse
fixed, I have beangapps folders linked now. I also have the changelog linked too.
dcscorpio76 said:
Installed this rom this morning and all is running well. It's very smooth and fast as advertised. I noticed a few things that are missing however, at least in my experience. These are in no offer except the first one.
1. The Speakerphone bug still exists on this build. It was fixed on the latest build of AOSP Extended. The workarounds do not appear to work either by cutting the screen on or off nor ticking the bottom on or off.
2. There is no option for weather on the lockscreen. This is not a deal breaker but nice to have.
3. There doesn't appear to be a way to remove the input selector in the status bar when you open a text field.
4. Although there's an option to use the fingerprint scanner after reboot, there's no option to unlock after pin without pressing check button.
5. The purenexus Kernel Aduitor zip will not flash in recovery. Error message reads file is not in proper zip format.
6. SELinux preset to Permissive in Dev Ops. Even when changed to Enforcing, defaults back to Permissive.
That's all I could think of at the moment. Other than that, this is a very nice build. Thanks for sharing your work OP!
Sent from my ZTE AXON 7 using Tapatalk
Click to expand...
Click to collapse
I noticed a few people have asked about the weather on lockscreen... We will look into that.
as for the purenexus kernel aduitor zip, that has to do with the new twrp's update scripting and busybox.......
I will look into that as well.. but it will be helpful if you left a recovery log on that.......
As for your speaker phone that would be Maintainer on the device tree...............
Thank you for your support and reporting the problems...........
Lol @Eliminater74 always so dotty
aclegg2011 said:
fixed, I have beangapps folders linked now. I also have the changelog linked too.
Click to expand...
Click to collapse
What is the kernel adiutor link for?
How do we use it?
joemossjr said:
Lol @Eliminater74 always so dotty
Click to expand...
Click to collapse
Did I say something wrong?
Sent from my HTC 10 using Tapatalk
Eliminater74 said:
Did I say something wrong?
Click to expand...
Click to collapse
No I just remember you from another thread lol nothing wrong with being dotty lol
Can someone explain to me what I asked please?
nfsmw_gr said:
What is the kernel adiutor link for?
How do we use it?
Click to expand...
Click to collapse
I took the link down, because we couldn't flash it anyways.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for OnePlus Nord N10 [billie]
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 11
Whats working?
RIL
Mobile Data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Lights
Sound/vibration
WIFI
NFC
Default 90hz refresh rate
Known issues
Adaptive Brightness
DT2W
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
Join Telegram SUPPORT GROUP
Flash instruction
Pre-requisites:
* You are familiar with helping yourself out of awkward situations. You won't defame or complain at the developer of this ROM for your misfortunes.
* You are familiar with using fastboot
* Bootloader unlocked
* You have created a backup of your ROM & data
* !!!CLEAN FLASH RECOMMENDED!!!
Spoiler: Instruction
Download the ROM and recovery image
Boot into bootloader adb reboot bootloader
Flash the recovery image fastboot flash recovery recovery.img
Do a factory reset in recpvery
Reboot into recovery fastboot reboot recovery
Go to Apply update and choose Apply from ADB
Sideload the rom adb sideload rom.zip
A special thanks to @churchner420 who donated me the device!
Thx to @KakatkarAkshay who helped me!
Android OS version: 11.0.0_r32
Security patch level: March 2020
Build author: Billaids / Telegram
Device Source code: https://github.com/Billaids/device_oneplus_billie
Kernel Source: https://github.com/Billaids/kernel_oneplus_sm6350
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Thanks for sharing! Is SELinux enforcing ?
Billaids said:
Flash the recovery image fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Does this automatically default to the current boot partition? I think there is no recovery partition. Wouldn't it be enough to fastboot boot the recovery, so the current kernel is not overwritten? (second partition set can remain unchanged as backup)
downloading, thanks
Very nice Rom, installed it and it works. One thing I couldn't find is an option to switch to 90Hz? Is it possible to get it to 90Hz?
EDIT: Found a way " adb shell settings put system min_refresh_rate 90.0 " does the job.
Nice Rom, keep up the good work. Thank you a lot!
Finally we are gifted with the boon of roms for this phone. Praise be!
But for real though thank you so much.
If've tesed the Rom a little bit, two things, first the Statusbar is a little bit to high and scrolling is a little bit stuttery (maybe something to do with scrolling cache?).
Other than that very smooth and stable rom.
MH190102 said:
If've tesed the Rom a little bit, two things, first the Statusbar is a little bit to high and scrolling is a little bit stuttery (maybe something to do with scrolling cache?).
Other than that very smooth and stable rom.
Click to expand...
Click to collapse
Both and a lot more will be fixed in the next update. Meanwhile the refresh rate is set to 60hz hence your phone feels stuttery. That can be fixed with the following adb command: adb shell settings put system min_refresh_rate 90.0
churchner420 said:
Both and a lot more will be fixed in the next update. Meanwhile the refresh rate is set to 60hz hence your phone feels stuttery. That can be fixed with the following adb command: adb shell settings put system min_refresh_rate 90.0
Click to expand...
Click to collapse
Yeah, its the first build and for that its running pretty good, as you can see above I've allready fixed the refresh rate at 90Hz with this command, still some stutters but its ok.
Really looking forward for the next update, love the Rom.
MH190102 said:
Yeah, its the first build and for that its running pretty good, as you can see above I've allready fixed the refresh rate at 90Hz with this command, still some stutters but its ok.
Really looking forward for the next update, love the Rom.
Click to expand...
Click to collapse
Yepe too oh yes ok I didn't see it was you. The stuttering probably is because of the kernel not being polished 100%. Will prbably be a lot better in the next update
Tried flashing this ROM today, wifi still doesn't work after rebooting multiple times. re flashing yields the same result. Anyone else having this problem?
Generic123. said:
Tried flashing this ROM today, wifi still doesn't work after rebooting multiple times. re flashing yields the same result. Anyone else having this problem?
Click to expand...
Click to collapse
I completed the setup without wifi and once I got to the Homescreen, I rebooted the device and wifi was working.
Is this ROM for the 5G? If so is it for the unlocked version?
creativetrendz said:
Is this ROM for the 5G? If so is it for the unlocked version?
Click to expand...
Click to collapse
5G should work
Generic123. said:
Tried flashing this ROM today, wifi still doesn't work after rebooting multiple times. re flashing yields the same result. Anyone else having this problem?
Click to expand...
Click to collapse
try to flash boot.img from stock rom
after booting the stock boot.img the roms runs nicely I am happy to st modifying this device
Can you say if the next update for this awsome Rom is comming soon?
Billaids said:
try to flash boot.img from stock rom
Click to expand...
Click to collapse
Late reply, but flashing the stock boot.img doesn't appear to fix things on my end. Will go back to oxygenOS for now. Hope that the next update makes the ROM more stable.
Hello Sir, I bought the OnePlus NORD N10 5G phone last week and wanted to use it for direct streaming with my new Hearing AIds. In the System/Accessibility menu, i ticked Hearing Aids Compatibility and paired my hearing Aids devices and they showed up as connected. Alas, no sound in my aids! They still come out from the loudspeaker even if I press the volume button and change the output to Hearing Aids. I know that ASHA (Audio Streaming for Hearing Aids) works well on PIXEL 3 and 4. Is it implemented in your ROM? I don't want to void my guarantee if there is no hope that it ill work. Thanks for your answer.
vakwa42 said:
Hello Sir, I bought the OnePlus NORD N10 5G phone last week and wanted to use it for direct streaming with my new Hearing AIds. In the System/Accessibility menu, i ticked Hearing Aids Compatibility and paired my hearing Aids devices and they showed up as connected. Alas, no sound in my aids! They still come out from the loudspeaker even if I press the volume button and change the output to Hearing Aids. I know that ASHA (Audio Streaming for Hearing Aids) works well on PIXEL 3 and 4. Is it implemented in your ROM? I don't want to void my guarantee if there is no hope that it ill work. Thanks for your answer.
Click to expand...
Click to collapse
As far as I know unlocking your Bootloader on a OnePlus-Phone doesn't void your guarantee.
Help pls, not sure what I am doing wrong. I have a Oneplus Nord N10 5G and have once again had to rely on the MSM Dowload Tool at billie8_14_O.01_201121 to recover the situation!
Like on all my phones of past nearly 10 yrs, rooting is the best option for me. I wonder when TWRP will be available?
I managed to install the custom recovery as above but adb sideloading the PixelExperience_billie-11.0-20210306-2121-BETA-UNOFFICIAL.zip doesn't work for me. It crashes out about halfway thru saying it was expecting to receive file for the N10, which it is.
Just to clarify this Pixel zip file is for the Build Number Oxygen OS 10.5.7 BE86AA and after?? Thanks all for any advice/pointers
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has addressed it already. Especially if you're even close to new at this.
2) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
3) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
You should start off with the latest Android 11 OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery by flashing the boot.img using
Code:
fastboot flash boot fajita-YYYYMMDD-HHMM-boot.img
followed by booting to recovery through the bootloader.
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-fajita-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
FINALLY! YES! WOOHOO!
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
void4ever said:
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
Click to expand...
Click to collapse
Indeed, the current required base is the latest Android 10 stable.
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
void4ever said:
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Click to expand...
Click to collapse
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
I would be happy to provide logs if/when i run into an issue.
I can give some background right now, which may not be very useful since we don't know if 9.0 is going to have the same issue. I don't recall if it was you @Myself5 or the dev from Paranoid, but we had a short discussion about this a while ago. If I recall one of you suggested it might be the modules you were using from the ASOP libs maybe? I'd have to go search through the old threads.
The only car I have to test with is my 2019 Traverse. AA works perfect everytime with stock Oxygen, and the only other ROM I ever ran into that seemed to work fine was AOSIP, however the rom itself was unstable on my hardware and I had to remove it due to my alarm not going off cuz the phone would crash overnight. So perhaps there's something in the way they implemented USB detection.
The last rom I tested (I forget which) I noticed that the phone wasn't even popping up the USB notification (where you can select File Transfer, USB tethering, MIDI, PTP, No data transfer) when connecting to the car.
Anyways this is far more info than we need until I can test it. Hopefully this weekend if not sooner.
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Mckillagorilla said:
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Click to expand...
Click to collapse
Yes you can install Magisk through Carbon Recovery. TWRP should be just fine, especially as the Recovery isn't used for updates etc as that is all done through Seamless updates in CarbonDelta on the system itself.
When i installed the rom i had to install the gapps after i was done with the phone setup. Otherwise the Android Setup would crash as soon as android booted.
The screen would then go cracy (blinking button icons) and I couldn't do anything.
I also can't update using the ota update.
Just tells me "Update could not be installed".
Other than that it works great
Edit: I didn't see the message about the video playing fix in some apps.
Updated from to latest version and now all videos work
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
Thank you for this great rom .
I had a problem with Android Auto, It's solved but I report if someone faces the same issue.
With Nikgapps basic on cr-9.0, Android Auto was not working: the phone was detected by the car (Peugeot 2008 from 2018), but when I initiated the connection the phone hangs and freeze, nothing happens on the car and I often had to reboot the phone.
It was an error related to usb permission in the logs.
It was solved using the stock package of Nikgapps (the problem is reported on other other devices as well). I was using the basic package of nikgapps on carbonrom cr-8.0 without problem, I don't know what changed that made the stock package needed.
I did not try for other gapps providers, but at first glance, this problem doesn't seems related to the rom itself but more to the gapps package.
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Prabhuraj 0 said:
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Click to expand...
Click to collapse
By updating to the latest build as mentioned a few posts above yours.
On that note:
I've found and fixed an issue where the device would not be reported as an A/B device properly which resulted in the integrated updater being broken. It will be fixed in wednesdays build (along with August ASBs) but you will need to manually update (through recovery) to that build.
So I haven't had a chance to install because I had to be OnCall for my job this week, no messing with my phone...... BUT that may have been a blessing?
I see the Stable A11 was released today for the 6 and 6T. Are there plans to rebase Carbon 9.0 to this?
Void4ever
Solid ROM! I haven't used Carbon since the Epic 4g phone. I'm running latest without Gapps, and I have to ask is there a better camera available outside of the play store? I know its a long shot but thought I'd try.
Google Camera, just google up gcam ports
only reason fr nt using Carbon is there is no
face unlock
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Wishmasterflo said:
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Click to expand...
Click to collapse
The last version also took a while (~4-7 days, not sure) until it was available on the website
I see it now. Probably didn't wait long enough!
Also @Myself5 is this by chance based on A11 now, or still A10?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience Plus for Xiaomi Mi 10 Lite 5G [monet]
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 11
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from SourceForge
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our Telegram Device Group
Our Telegram Device Release Channel
Our blog
Android OS version: 11.0.0_r43
Security patch level: September 2021
Build author/Device Maintainer: maluueu
Device Tree Source code: https://github.com/maluueu/android_device_xiaomi_monet
Common Tree Source code: https://github.com/maluueu/android_device_xiaomi_sm7250-common
Kernel Source code: https://github.com/maluueu/android_kernel_xiaomi_sm7250
ROM Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
reserved for future use
So, what's the flashing process for this? Haven't really flashed many ROMs to my Mi 10 Lite and I'm under the impression some things have changed (previous phone was Redmi Note 4X).
Do I:
1. Reboot to Recovery
2. Download the proper ZIP for your device
3. Wipe Data/Cache/System when coming from non-AOSP ROMs
4 Flash the proper firmware
5. Flash the ROM
6. Reboot to System
or is there something else I have to do beforehand?
Necrogenisis said:
So, what's the flashing process for this? Haven't really flashed many ROMs to my Mi 10 Lite and I'm under the impression some things have changed (previous phone was Redmi Note 4X).
Do I:
1. Reboot to Recovery
2. Download the proper ZIP for your device
3. Wipe Data/Cache/System when coming from non-AOSP ROMs
4 Flash the proper firmware
5. Flash the ROM
6. Reboot to System
or is there something else I have to do beforehand?
Click to expand...
Click to collapse
You can find the installation instructions in our Telegram Device Release Channel.
Here's a direct link to the post: here
Adding to that, don't wipe anything else than Data and Cache, the partitions are automagically format or written by need.
When I wipe cache and format data partition I can't transfer rom file to phone using pc and I can't see any files on device using twrp app.. Tried to push file using adb sideload but twrp says encrypted fbe, any ideas?
Never mind, I suceeded
Domac5 said:
When I wipe cache and format data partition I can't transfer rom file to phone using pc and I can't see any files on device using twrp app.. Tried to push file using adb sideload but twrp says encrypted fbe, any ideas?
Never mind, I suceeded
Click to expand...
Click to collapse
Ahh, nice to hear that it's working now.
Nevertheless, if you have any other difficulties, you can also just join our telegram group and ask for help there.
@Domac5 forgot to say, that after you wipe and format your data partition you need to "reboot to recovery" and then the partition will be ready to take your files, for the flashing process.
Thanks for the ROM, will try it asap.
Edit.
Turns out. It has many flaws. The recents are not snappy when they come up, and the there are a few lags when scrolling in the google feed (on the left hand side of the home screen), and in Google Chrome, reading the stories - even after they have loaded up form the network. This is the same for all the AOSP-like ROMs because they are compiled from the same source as far as I see.
The last version works very well, it's nice to have the pixel experience and without glitches.
Infinite thanks to the authors. I look forward to new updates
EDIT: by the way, I miss the gallery application, there is none, just google photos but it is not the same
MetallicGR said:
@Domac5 forgot to say, that after you wipe and format your data partition you need to "reboot to recovery" and then the partition will be ready to take your files, for the flashing process.
Thanks for the ROM, will try it asap.
Edit.
Turns out. It has many flaws. The recents are not snappy when they come up, and the there are a few lags when scrolling in the google feed (on the left hand side of the home screen), and in Google Chrome, reading the stories - even after they have loaded up form the network. This is the same for all the AOSP-like ROMs because they are compiled from the same source as far as I see.
Click to expand...
Click to collapse
I don't have those problems, have you flashed the correct stock rom before?
ccerrato said:
I don't have those problems, have you flashed the correct stock rom before?
Click to expand...
Click to collapse
Yep. Up to the last instruction. Flashed eu firmware, flashed pixel rom, cleared cache, reboot.
I maybe cannot express this enough, but i can tell you how it can be recreated, at least in my end.
Go to settings app, tap on battery, swipe to go to the recent apps. Then, the settings app will not go to the recents and 'join' the others and will stay there.
Moreover I saw that If I leave the app there, it will crash after a while. So far its happening on the Settings app, and on the Play Store as well.
MetallicGR said:
@Domac5 forgot to say, that after you wipe and format your data partition you need to "reboot to recovery" and then the partition will be ready to take your files, for the flashing process.
Thanks for the ROM, will try it asap.
Edit.
Turns out. It has many flaws. The recents are not snappy when they come up, and the there are a few lags when scrolling in the google feed (on the left hand side of the home screen), and in Google Chrome, reading the stories - even after they have loaded up form the network. This is the same for all the AOSP-like ROMs because they are compiled from the same source as far as I see.
Click to expand...
Click to collapse
The recents issue should be resolved already. About the other ones, I can't replicate any of these. If you could send me a video explaining/showing the issues that would be great
ccerrato said:
The last version works very well, it's nice to have the pixel experience and without glitches.
Infinite thanks to the authors. I look forward to new updates
EDIT: by the way, I miss the gallery application, there is none, just google photos but it is not the same
Click to expand...
Click to collapse
Hey ccerrato, first of all, infinite thanks for your donation. I really really appreciate that )
But remember, none of you have to donate anything to me. You can use everything for free (obviously), as I also use this ROM as my daily driver, but if you have some money left over, feel free to do so
Coming back to the gallery "issue", there only is Google Photos on Pixel devices, hence why there is only Google Photos in PixelExperience. But if you don't want to upload your data to Google servers you can just use the app without backup functionality.
MetallicGR said:
Yep. Up to the last instruction. Flashed eu firmware, flashed pixel rom, cleared cache, reboot.
I maybe cannot express this enough, but i can tell you how it can be recreated, at least in my end.
Go to settings app, tap on battery, swipe to go to the recent apps. Then, the settings app will not go to the recents and 'join' the others and will stay there.
Moreover I saw that If I leave the app there, it will crash after a while. So far its happening on the Settings app, and on the Play Store as well.
Click to expand...
Click to collapse
I tried this a couple of times and couldn't replicate the issues you're experiencing.
#### New PixelExperience Plus Release ####
Changelog:
- Fixed OEM charger (thanks @spakkkkkk for finding the fix)
- Fixed random reboot while phone is off with OEM charger
https://telegra.ph/New-PixelExperience-Plus-Release--MONET-10-06
maluueu said:
I tried this a couple of times and couldn't replicate the issues you're experiencing.
Click to expand...
Click to collapse
On EvolutionX this doesn't happen. Will try today with the latest build to check.
Edit, yep still the same. The recents problem. Sometimes i cannot go to home screen immediately and i have to repeat the gesture to get out of the stuck app.
Ive managed to capture the problem in the latest build https://sourceforge.net/projects/sm...t/PixelExperience/New Tree (stable)/20211005/
MetallicGR said:
Ive managed to capture the problem in the latest build https://sourceforge.net/projects/sm7250-releases/files/Monet/PixelExperience/New Tree (stable)/20211005/
Click to expand...
Click to collapse
Okay, I could replicate the issue. We know where it originates from and will try to fix it now
Thanks @maluueu
#### New PixelExperience Plus Release #### MONET
Changelog:
- Latest PixelExperience Plus updates (20211017)
- Display color fixed
- Disabled HD sim notification
- Fixed fingerprint payment in apps (AliPay and others)
- Clean up useless init files
- Optimized
- Fixed FM radio
- Display color fixed
- Set display color to normal as default, not adaptive anymore
- Using 64 bit binder
Release Notes: https://telegra.ph/New-PixelExperience-Plus-Release--MONET-10-18
Wow, so the issue for the swipe from bottom was the FOD all along :")