{
"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"
}
We are very excited to announce the beta of Paranoid Android Topaz, based on Android 13.
On the first launch, you’ll notice a clean setup with beautiful wallpapers from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app from the PlayStore.
Our builds are based on the Code Linaro Organization Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Notice
We kindly ask all of you that are in a position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.
You can donate on the link below:
Donate
Device-specific issues
* No issues have be found upon testing, feel free to report if you encounter any.
Requirements
Make sure you've latest platform tools for Android.
Download
You can always get our builds from our website Paranoid Android website
Note: Custom kernels are NOT supported the kernel says it supports PA and GMS is included!
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them. For more detailed information please have a look at the second post of this thread of each build changelog on the website.
Paranoid Android Topaz released
Instructions
Make sure your data is backed up (via Google or other services)
Unlock your bootloader, and in bootloader mode follow the next command
fastboot -w (Wipes the entire device as well as userdata)
fastboot update aospa-topaz-beta-*-image.zip
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Source code
Kernel
Cheers and #StayParanoid!
This rom has support for OTA updates. If you plan to stick around with PA, your feedback will be appreciated on our new OTA system. We're consistently testing full and incremental OTA updates.
Key Features
- Face unlock support
- A slew of Pixel exclusive features
It's my first time having a pixel and I heard from the past that Pixel's in general can relock bootloader on custom ROM. Will that work in this ROM?
Just installed, THANKS!
Working well so far! Installed most of the mods I was using on the factory image...
Magisk, lsposed, revanced, aosp mods all working.
Only problem for me is you can't customize settings for the at a glance widget and the flashlight suggestion is annoying.
thattechguy_69 said:
It's my first time having a pixel and I heard from the past that Pixel's in general can relock bootloader on custom ROM. Will that work in this ROM?
Click to expand...
Click to collapse
Don't know haven't tried
OMG YES, PARANOID ANDROID!!! flashing now!
thattechguy_69 said:
It's my first time having a pixel and I heard from the past that Pixel's in general can relock bootloader on custom ROM. Will that work in this ROM?
Click to expand...
Click to collapse
You would need to make your own custom signing keys for the ROM or the ROM would need to come with them. Otherwise when you lock the bootloader, it will brick.
EtherealRemnant said:
You would need to make your own custom signing keys for the ROM or the ROM would need to come with them. Otherwise when you lock the bootloader, it will brick.
Click to expand...
Click to collapse
And also does the pixel 7 have a similar tool like msm tool from OnePlus devices when bricked?
Flashed about an hour ago and so far so good...only issue is it's saying lte and not 5g...anyone else having the issue?
Edit: the issue worked itself out
Edit 2: the issue is back... In the settings it says 5g but by my signal bars, it's giving the lte icon
Been waiting for this, very exciting. Thanks!
thattechguy_69 said:
And also does the pixel 7 have a similar tool like msm tool from OnePlus devices when bricked?
Click to expand...
Click to collapse
There is no EDL mode on the Pixel as that's a Qualcomm thing and we don't have access to Samsung's EDL alternative. If you manage to permanently brick it, Google will charge you for a board replacement which is like $500+.
EtherealRemnant said:
There is no EDL mode on the Pixel as that's a Qualcomm thing and we don't have access to Samsung's EDL alternative. If you manage to permanently brick it, Google will charge you for a board replacement which is like $500+.
Click to expand...
Click to collapse
I'mma just stay away from flashing for now.
thattechguy_69 said:
I'mma just stay away from flashing for now.
Click to expand...
Click to collapse
It's really hard to brick a Pixel unlike OnePlus
sirhc said:
It's really hard to brick a Pixel unlike OnePlus
Click to expand...
Click to collapse
I would agree with this. In fact I had never bricked a phone until my OnePlus 9 and I've had Android phones going back to the HTC Hero in 2009. I even majorly screwed up a flash on my Pixel 3 XL and it was totally recoverable since I didn't lock the bootloader. Regardless though, the fact that such a recovery tool doesn't exist, has definitely left people with bricks so it's worth pointing out.
Oops, boot loop... coming from QPR1 Beta. Looks like I will have to roll back to stable and then flash this
EtherealRemnant said:
I would agree with this. In fact I had never bricked a phone until my OnePlus 9 and I've had Android phones going back to the HTC Hero in 2009. I even majorly screwed up a flash on my Pixel 3 XL and it was totally recoverable since I didn't lock the bootloader. Regardless though, the fact that such a recovery tool doesn't exist, has definitely left people with bricks so it's worth pointing out.
Click to expand...
Click to collapse
Last year bricked my 6pro..
Got a replacement from Google..
Aks said:
Oops, boot loop... coming from QPR1 Beta. Looks like I will have to roll back to stable and then flash this
Click to expand...
Click to collapse
QPR1 isn't released in AOSP/CAF(CLO) until December I wouldn't recommend flashing any rom on top of it
Do we know if Widevine L1 is retained?
oryanh said:
Do we know if Widevine L1 is retained?
Click to expand...
Click to collapse
+2
Related
{
"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 Realme 5 Pro [RMX1971]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
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 10.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
Nothing
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 10.0.0_r27
Security patch level: February 2020
Device Source code: https://github.com/bablusss/device_realme_RMX1971
Source code: https://github.com/PixelExperience
Difference between this and the other Pixel Experience?? Is this going official near time soon?
Is this working on Realme Q?
saurav_xdadev said:
Difference between this and the other Pixel Experience?? Is this going official near time soon?
Click to expand...
Click to collapse
Bruh... Just let it go. Official means nothing to us end users. For devs official means they would've to dedicate themselves to that one ROM, become part of the official PE site and dev group and keep it updating even if they don't really want to. I think it means responsibility. So don't keep asking 'official when!?' for a dev is dedicated enough towards one ROM will take on official too. If not they won't.
saurav_xdadev said:
Difference between this and the other Pixel Experience?? Is this going official near time soon?
Click to expand...
Click to collapse
Official doesn't mean it's stable, just a tags bruh, they can update without Official
Hey there. Tested out the other PE version here on XDA, but that bootlooped after 2 weeks of usage (apparently a problem with most custom OSes). Does this fix the bootloop issue? Havoc OS recently pushed a patch that fixes said problem
greenys' said:
Bruh... Just let it go. Official means nothing to us end users. For devs official means they would've to dedicate themselves to that one ROM, become part of the official PE site and dev group and keep it updating even if they don't really want to. I think it means responsibility. So don't keep asking 'official when!?' for a dev is dedicated enough towards one ROM will take on official too. If not they won't.
Click to expand...
Click to collapse
viethoang18 said:
Official doesn't mean it's stable, just a tags bruh, they can update without Official
Click to expand...
Click to collapse
I didn't mean to be rude. Just as to know why there are two threads for the same rom.
I'll be more than happy to have any roms having no bugs at all and be unofficial rather than having bugs and be official. Peace :good:
Nice! tho fingerprint hardware becomes unavailable at times, and TWRP can read the internal memory as it becomes encrypted
saurav_xdadev said:
I didn't mean to be rude. Just as to know why there are two threads for the same rom.
I'll be more than happy to have any roms having no bugs at all and be unofficial rather than having bugs and be official. Peace :good:
Click to expand...
Click to collapse
Sure thing. Me too.
It's good rom. All functions work well for me! But wifi doesn't connect automatically.
bahuy2003 said:
It's good rom. All functions work well for me! But wifi doesn't connect automatically.
Click to expand...
Click to collapse
It will work only if linked to a know location. Kind of trade off.
How do you flash this rom from stock non rooted ColorOS.
JominatorX said:
How do you flash this rom from stock non rooted ColorOS.
Click to expand...
Click to collapse
Yes you can!
1. Unlock bootloader.
2. Flash recovery over fastboot mode.
3. Download rom and copy it into sdcard (not internal memory).
4. Put your device into recovery mode.
5. Flash rom from sdcard
6. Format data (factory reset).
7. Come back fastboot mode and flash vbmeta.img
8. Reboot system.
So that's, you didn't need to root your mobile.
---------- Post added at 04:11 PM ---------- Previous post was at 04:09 PM ----------
clavicle said:
It will work only if linked to a know location. Kind of trade off.
Click to expand...
Click to collapse
Yes, that's right. I think this rom is the best from custom roms.
How does user update OTA with this Custom ROM if the new version is available? Must flash again and cannot do it through the phone directly?
Thanks for your detailed guide! One last request tho where can I find a compatible vbmeta.img that I can flash to avoid recovery destroyed error.
one question: how can I upgrade to this version from the previous PE such like the 17/01/2020 version by @BabluS?
@Orgasmtrron
There is this double tap to wake bug in this rom. No matter how your toggle is selected to in the settings, the Tap to Wake feature is always on. This is leading to battery drain too.
Another, can the wifi fix be incorporated? The wifi will not reconnect after switching it off, even though I have activated the option of wifi scanning and set the location to on. It still wouldn't reconnect automatically. You always have to manually turn the wifi on.
Thanks.
JominatorX said:
Thanks for your detailed guide! One last request tho where can I find a compatible vbmeta.img that I can flash to avoid recovery destroyed error.
Click to expand...
Click to collapse
Vbmeta.img
https://drive.google.com/file/d/1-vk6rZJg-u53jMQZGC_gnb6Rhi5KXNC0/view?usp=drivesdk
my questions to those testers who have tested the current official version(PixelExperience_RMX1971-10.0-20200227-0250-OFFICIAL.zip)
1) anyone tried gcam with all 4 back cameras (including macro and wide cameras) work in this rom ?
2) which version of gcam is stable for this rom?
3) is auto call recording feature available?
So far the rom is so stable, but the ram management is bad, I barely can't open 4 apps together and they load many of the times.
Sent from my Realme 5 Pro using Tapatalk
Nothing to see here
ROM source here: https://github.com/Bootleggers-BrokenLab
And chat here: https://t.me/keepthebootleg
Remember this is not an official build so builds won't be here ^ and unofficial support, chatting, etc, are not allowed here so please respect the rules.
*Bootleg 8t Chat coming soon..
This one too
Current Build: v14
v14.zip
drive.google.com
Previous build here: https://drive.google.com/file/d/1-I3z_pLzLEZPhBmJb_FZesLUcycY_5Ud/view?usp=drivesdk
Tnx for your amazing work bro
damn! bootleggers is a coming!
and comes with neutrino power!
thankssss
What about MTP not working ??
Some people saying that in some chats do you know anything about that??
This is the best news ever.
dpryor88 said:
This is the best news ever.
Click to expand...
Click to collapse
MTP working for you?? Thanks in advance
alex moymoy said:
What about MTP not working ??
Some people saying that in some chats do you know anything about that??
Click to expand...
Click to collapse
Enable in development options if you have issues, Works fine for me. I have no issues. But I always enable via development options
alex moymoy said:
MTP working for you?? Thanks in advance
Click to expand...
Click to collapse
Well I certainly don't work for IT. It works for me on the weekends, part time. I don't pay it well, but it doesn't know any better.
FullOfHell said:
Spoiler
Hello, you all may remember me from my ROMs for pixel 5, pixel 4, 8t, 7t, 6t, Shamu, and J7..
I left 8t development a few months ago to have some fun with a pixel 5, and a month ago, dusted the ol' kebab off and jumped back in. I keep most of my ROMs on the silent side of things and don't use xda but for official releases. Hopefully, This unofficial build will become official. I think you all will love it as much as I do. It comes with my own branch of neutrino kernel, as does all my ROMs, it's entirely based on neutrino, but I add klapse, hbm, vibration tuning, etc, and some other kernel options that I don't care to add device tree side. This is a beta build so it has a couple weird small bugs, and no they do not affect anything.
Bugs-
1. At first boot, soon as you see the setup wizard, it will show you a toast, phone is rebooting, it reboots then setup continues not to happen again. This affects nothing. Not sure why, but don't really care either, as it all works ferociously fine after.
2. Occasionally, up at the left most corner, where the status bar clock is, a slice of the hour part of the clock is sliced off, it doesn't exist all the time, just sometimes. It is perfect in quick settings view and typically corrects itself only to randomly get sliced. I probably have a duplicate overlay for the dimensions related to that spacing. Will fix next chance I get.
That's it for any issues.
Features-
All the current bootleggers features for "Rimbon". Perfect fingerprint, face unlock, endless theming options, larger quick setting icons for easier tapping, proton aosp blur, proton aosp optimizations, Verizon support, dual sim support, enable/disable fingerprint vibration, Dolby, raise to wake, app lock, the list goes on. More features will be coming once I add them, prob fod animations and edge notification pulse.
Things I don't care to add-
fod screen off, safety net spoofing, sm8250-DeviceSettings(we really don't need them at all)I added and they're redundant, and call recording, oh yeah gaming is for PCs and consoles I don't add it to phones. If you want these things. Bootleggers is not for you.
All my builds are fastboot update zips and include gapps. I'm a Google guy and need all their stuff and yes I don't care they can have mine too. Haha.
Flashing- no matter what you are on currently, for best performance flash oos stable first, then format data via recovery, reboot bootloader and the command is fastboot update bootleg_kebab_v7.zip *note, you must open terminal in the folder where the zip is to give this command, other wise fastboot update HereIsLocationToTheZip.zip. after it does it's thing and flashes it boots and then at first boot shows the setup wiz and reboots as declared in "bugs" section.. Root if you would like to use kernel features, this requires the same old process we have used for 3 android versions, I hope you know how, lol. If you have troubles, re read this entire post.
Thanks- to my testers, my friends, the entire kangarooster squad, and the couple android geniuses who shared their wisdom teaching me the ropes the last 4 years of source building.
@xstefen @dpryor88 @omariscal1019 @Neo @wrongway213 @semdoc @hondajohn88 @varund7726 @abalam @ZVNexus @return.of.octobot @aer0zer0 and countless others who I will add once I figure out their xda name.
Trees:
jacks84 - Overview
jacks84 has 98 repositories available. Follow their code on GitHub.
github.com
Click to expand...
Click to collapse
alex moymoy said:
MTP working for you?? Thanks in advance
Click to expand...
Click to collapse
Just connect your phone with pc, go to dev menu and hit this. Choose what you want
{
"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"
}
Hey, I tried to flash your ROM using the method you recommended, But it only spat out,
error: failed to load 'bootleg_kebab_v7.zip': Not enough space
Click to expand...
Click to collapse
Is there something I am doing wrong? Many apologies, I haven't flashed a ROM like this, This will be my first time.
Huskied said:
Hey, I tried to flash your ROM using the method you recommended, But it only spat out,
Is there something I am doing wrong? Many apologies, I haven't flashed a ROM like this, This will be my first time.
Click to expand...
Click to collapse
have you adb sideloading a rom before?
Huskied said:
Hey, I tried to flash your ROM using the method you recommended, But it only spat out,
Is there something I am doing wrong? Many apologies, I haven't flashed a ROM like this, This will be my first time.
Click to expand...
Click to collapse
Update sdk
Huskied said:
Hey, I tried to flash your ROM using the method you recommended, But it only spat out,
Is there something I am doing wrong? Many apologies, I haven't flashed a ROM like this, This will be my first time.
Click to expand...
Click to collapse
Prob need to msm first, sounds like your partitions are funky, or as abalam said, update platform tools
Just kidding
bootleg_kebab_v7.zip
drive.google.com
Huskied said:
Hey, I tried to flash your ROM using the method you recommended, But it only spat out,
Is there something I am doing wrong? Many apologies, I haven't flashed a ROM like this, This will be my first time.
Click to expand...
Click to collapse
You need a platform tools update
best rom i ever used on my 8t
smooth af, snappy af, fod fast af
thanks dev
{
"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"
}
StatiXOS for Essential PH-1 (mata)
What is StatiXOS?
StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal while providing quality of life improvements and up to date security patches.
Spoiler: Known Issues
Some minor Launcher bugs (thanks AOSP)
SElinux Permissive
Spoiler: Download StatiXOS Here!
Primary
SourceForge Mirror
Spoiler: How To Flash
1. Download the image
2. Reboot your Essential Phone to bootloader and plug it in to your computer
3. Now open up your Terminal (macOS and Linux) or Command Prompt (Windows) and download the firmware from the links below.
4. Once downloaded, type in fastboot -w to make sure your /data is formatted
5. Now type in fastboot update <location of the firmware>, things will be automated from this point on.
6. Profit!
Spoiler: Stay in touch with our Telegram channels!
Official Chatroom
Official Releases & Announcements Channel
Prerequisite firmware: Latest stock Android 10
Android version: 12.1.0
Linux Kernel Version: 4.4.205
Source code: GitHub
Code Review: Gerrit
Trying it now thank you for the work and dedication!
I flashed this firmware and everything is fine. But when I flashed magisk, the screen seemed to move a little to the right. The screenshot is OK, but it can be seen in the photo.
Before flash Magisk
Code:
adb shell wm size
Physical size: 1312x2560
After flash Magisk
Code:
adb shell wm size
Physical size: 1376x2560
btbochs said:
I flashed this firmware and everything is fine. But when I flashed magisk, the screen seemed to move a little to the right. The screenshot is OK, but it can be seen in the photo.
Click to expand...
Click to collapse
This issue showed at one or two latest StatiXOS Android 11 builds for mata, after installing Magisk. According to Anay, one the team devs, it could be related to "the kernel thinks you’re in recovery, so it shifts the whole framebuffer 64 pixels".
The fix was to use a kernel from previous builds not affected or to wait until the issue can be fixed with StatiXOS Android 12, because Android 11 builds were EOL.
Currently in use, the problems found are that the night light mode is invalid, and the hot spot is opened, setting the password, and others' connection fails
if magisk is not supported, what is the alternative for rooting the rom? thank you.
Does Google pay work with this?
On statix A11, how to update/flash from los recovery
I noticed that, even in previous versions of statixos 4.x, there is a wifi performance gap. On the aosp version, for example, the test is passed with about 300mbps in download, while on statixos it is around 100mbps. Have you also noticed this?
digitalsimon said:
I noticed that, even in previous versions of statixos 4.x, there is a wifi performance gap. On the aosp version, for example, the test is passed with about 300mbps in download, while on statixos it is around 100mbps. Have you also noticed this?
Click to expand...
Click to collapse
Yes
Vi7eta said:
Yes
Click to expand...
Click to collapse
There are possible fixes, maybe from next releases?
Someone have idea about what cause this gap?
Deleted
I love this ROM and am very appreciative of the work you've done to keep my favorite phone off all time going. Magisk compatibility would be a nice addition. And maybe a pixel launcher version that allows the 2X2 grid pattern and super large icon folders on the desktop. Old people approved. Good work.
jeddy877 said:
I love this ROM and am very appreciative of the work you've done to keep my favorite phone off all time going. Magisk compatibility would be a nice addition. And maybe a pixel launcher version that allows the 2X2 grid pattern and super large icon folders on the desktop. Old people approved. Good work.
Click to expand...
Click to collapse
is it that good? I've been wanting to install it but I fear of bugs and battery issues (since my battery is already trash because of age)
Mario3DS said:
is it that good? I've been wanting to install it but I fear of bugs and battery issues (since my battery is already trash because of age)
Click to expand...
Click to collapse
It is fast. I haven't noticed a difference in battery life. Chrome doesn't work. I use the browser. Even the 360 mod works. The screen and battery are really easy to replace. I did it on the PH-1 here. My white one is stock and it's is a little tired. The ROM probably fully works on Verizon. I switched to Visible and it only partially works. It fully works on my Mint SIM.
jeddy877 said:
It is fast. I haven't noticed a difference in battery life. Chrome doesn't work. I use the browser. Even the 360 mod works. The screen and battery are really easy to replace. I did it on the PH-1 here. My white one is stock and it's is a little tired. The ROM probably fully works on Verizon. I switched to Visible and it only partially works. It fully works on my Mint SIM.
Click to expand...
Click to collapse
Does the rom has any customization options in setting? would you provide some SC for it,tnx
ali.sbi said:
Does the rom has any customization options in setting? would you provide some SC for it,tnx
Click to expand...
Click to collapse
It doesn't really have any customization options other than the normal A12 stock ones. I also noticed yesterday that I can no longer flash boot images or even restore it to stock firmware. The AB partitioning seems to be gone. Love the ROM but there should be a way to leave it. I may have just not figured it out yet.
jeddy877 said:
It doesn't really have any customization options other than the normal A12 stock ones. I also noticed yesterday that I can no longer flash boot images or even restore it to stock firmware. The AB partitioning seems to be gone. Love the ROM but there should be a way to leave it. I may have just not figured it out yet.
Click to expand...
Click to collapse
I haven't used this rom yet but as far as I know, a rom can't remove the A/B partitioning on a device
This awesome ROM is flashed just like flashing the stock firmware using flashall.bat. When I try reflashing the stock firmware, it says NO NO. The size of some file is too large. If I try to flash just any boot image, including the one from this ROM, to _a or _b in fastboot... It says AB partitioning is not supported by this device.
{
"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"
}
Google Pixel 3a XL
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Google Pixel 3a XL.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
bonito - Official builds
bonito - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9
Thanks for sharing!!
Thanks!
Awesome!
Got to install today and everything is working very smoother then butter on a bagel! Thanks for all of your hard work!
Was able to install on my Pixel 3a XL successfully! Sadly there was a niche feature that was removed, but i hope as this rom continues to be developed, the feature might be readded. The feature i am referring to is the Now Playing detection, for the ability for the Pixel to hear music that is playing in background and display it on the Always On Display. Other than that, this is a solid rom. I would give it a 9/10 regardless because LineageOS is a good rom nonetheless.
Well I am not having as much luck... I keep getting errors
Android system intelligence keeps stopping
This is with the UNOFFICIAL buld from the 21st
Also there does not appear to be any theming colors other then the deafault ones found in stock android. One of the reason I like LOS so much is that gogle does such a horrible job picking allowed theme colors
UPDATE: Loaded the official version and while I dont have the issue with android system intelligence I no longer can find any way to change theme color. In the custom version I had the options to use the standard google colors, in the stock version those choices simply dont exist. I only see wallpaper options and nothing else.
Is it hidden somewhere else under settings as I cant find it
Also changing system icon type doesnt affect all icons, not sure this may be an issue with pure sock as well
adm1jtg said:
Well I am not having as much luck... I keep getting errors
Android system intelligence keeps stopping
This is with the UNOFFICIAL buld from the 21st
Also there does not appear to be any theming colors other then the deafault ones found in stock android. One of the reason I like LOS so much is that gogle does such a horrible job picking allowed theme colors
UPDATE: Loaded the official version and while I dont have the issue with android system intelligence I no longer can find any way to change theme color. In the custom version I had the options to use the standard google colors, in the stock version those choices simply dont exist. I only see wallpaper options and nothing else.
Is it hidden somewhere else under settings as I cant find it
Also changing system icon type doesnt affect all icons, not sure this may be an issue with pure sock as well
Click to expand...
Click to collapse
intelligence error will be fixed next build.
As for official not having color selection - yeah, that's a pixel goodies thing.
npjohnson said:
intelligence error will be fixed next build.
As for official not having color selection - yeah, that's a pixel goodies thing.
Click to expand...
Click to collapse
Is the theming/pixel goodies slated to come to the stock build anytime soon? If not could I load the unofficial on top of the official build I have now WTHOUT having to wipe data.?
adm1jtg said:
Is the theming/pixel goodies slated to come to the stock build anytime soon? If not could I load the unofficial on top of the official build I have now WTHOUT having to wipe data.?
Click to expand...
Click to collapse
No, and maybe.
ok so whats the official party line from LOS for theming as currently there is no way to change accent colors at all. Mine defaults to lime green and I can find no way to change it
That said I dont want to seem negative as for a first build for android 12 everything else seems to work perfectly
adm1jtg said:
ok so whats the official party line from LOS for theming as currently there is no way to change accent colors at all. Mine defaults to lime green and I can find no way to change it
That said I dont want to seem negative as for a first build for android 12 everything else seems to work perfectly
Click to expand...
Click to collapse
On the official build there is no way.
It's monet. Matches AOSP.
With much thanks & appreciation for LOS support for our beloved devices over the years, going back to the early Moto & Nexus days ... here I come, joining soon - my Pixel 3a XL in excellent condition, well cared for and AccuBattery health put it at 97% still, SOT on stock rom of close to 8 hours - not putting this away anytime soon, nor going to trade it for $25 or even $50 (BL unlocked, ready to have fun)
Really sorry for this question
I have mido and it's quite simple to flash roms via usb in twrp or of...... instructions are...
Wiping
Dalvik/art cache
Cache
System
Data
Interal storage
Vendor
After all this
Data wipe with yes option
Installation
Rom.zip
Gapps.zip
Magisk.zip
Reboot
But here in bonito download section it has rom.zip + recovery.zip?
My question is am I able flash the rom via usb?
Please guide me
npjohnson said:
On the official build there is no way.
It's monet. Matches AOSP.
Click to expand...
Click to collapse
Guess I will just watch the thread till you release your fixed build
UPDATE: forgot stock android theming is horrible. Only 4 colors to pick. Will keep using official with the magisk module for now... and yes I know this makes me unsupported since am using magisk but until LOS implements some kind of theming its really the only choice
Quick Pull down Tile-Accent Colors Android 12
If you don't care for Android 12 stock colors, you can change the pastel QS Pulldown Tile colors to more basic colors. I've added two more options. After flashing these, you have all color options to pick from in settings/Display/Device Theme...
forum.xda-developers.com
jesudas said:
Really sorry for this question
I have mido and it's quite simple to flash roms via usb in twrp or of...... instructions are...
Wiping
Dalvik/art cache
Cache
System
Data
Interal storage
Vendor
After all this
Data wipe with yes option
Installation
Rom.zip
Gapps.zip
Magisk.zip
Reboot
But here in bonito download section it has rom.zip + recovery.zip?
My question is am I able flash the rom via usb?
Please guide me
Click to expand...
Click to collapse
Read this: https://wiki.lineageos.org/devices/bonito/install
Instructions are clear as they can be.
jesudas said:
Really sorry for this question
I have mido and it's quite simple to flash roms via usb in twrp or of...... instructions are...
Wiping
Dalvik/art cache
Cache
System
Data
Interal storage
Vendor
After all this
Data wipe with yes option
Installation
Rom.zip
Gapps.zip
Magisk.zip
Reboot
But here in bonito download section it has rom.zip + recovery.zip?
My question is am I able flash the rom via usb?
Please guide me
Click to expand...
Click to collapse
There is no recovery zip. Not at all sure where you are looking.
Follow the wiki.
what a smooth experience with the official version I did not expect less from LOS
btw, how does the version with the Pixel Features runs?
KarinByChance said:
what a smooth experience with the official version I did not expect less from LOS
btw, how does the version with the Pixel Features runs?
Click to expand...
Click to collapse
About the same
npjohnson said:
No, and maybe.
Click to expand...
Click to collapse
Actually The answers seem to be No and No then. Tried to load yours on top of official and had intelligence errors as well as just general app stoping errors mostly when in settings.
Back on official LOS for now, had to reload with a factory format to get it to work right again. Hope LOS team implements some kind of theming in the near future.