[OFFICIAL] LineageOS 18.1 for the Google Pixel 3a XL - Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot

[OFFICIAL] LineageOS 18.1 for the Google Pixel 3a XL - Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot

{
"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 18.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
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

Going to try it now.
Thank you!

npjohnson said:

Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Click to expand...
Click to collapse
syntax error Are we talking about the Kernel being bundled?

ssurell said:
syntax error Are we talking about the Kernel being bundled?
Click to expand...
Click to collapse
What? No, firmware, like modem, bootloader, etc.

Question:
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
So are you saying if we root there is no support? As most of us coming from stock would at least need root temporarily to restore all our apps.
Can anyone confirm if root even works on this build. I woudnt see any reason not but would like to know cause of the above reason.
UPDATE: Decided to just go for it and everything is working great so far. Took a little work to get google apps working instead of the included aosp ones (phone calendar and contacts) and a bt more work to get it to pass safteynet but its all working 100% now. Also tested this build with both ex kernel and mvk and they both seem to work just fine as well. Will report back if anything changes as have only been running it.a few hours but so far no issues or complaints at all.
Great job LOS team

What is the official way to obtain root access? or is there one any more?

cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
Based on the above statement i quoted sounds like root is not "officially" supported at all. That said to get root i followed the process by which you patch a boot image file with magisk manager. Making it pass safteynet net took additional steps.
If you need more details on either process just post back and i can be more detailed

adm1jtg said:
If you need more details on either process just post back and i can be more detailed
Click to expand...
Click to collapse
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!

cliffordd said:
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
Click to expand...
Click to collapse
sent you a private

cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
i flashed the version of Magisk (v21.4) via the LineageOS recovery using the adb sideload and just updated to v22 via the app. I haven't had any issues with root since installing.

First off, I want to say thank you for all the hard work on these builds.
I have came across one issue that isn't working for me, but might not be something everyone else uses a lot. My "squeeze" for Assistant isn't working, but I can change it to take a screenshot of any other option, except the Assistant. Am I doing something wrong or is there another settings need to activate for it to work?
Thanks!

Really want to try this, but can't "fastboot boot twrp.img" or "fastboot flash boot twrp.img" in Android 11 to backup my partitions. What's the point of Android OS if I can't backup my system? I can boot into Lineage OS Recovery, enable adb, figure out the partition names, dd the partitions from shell or pull with adb? But good grief, kinda ridiculous if you ask me.

Haven't been able to use twrp since Android 9 far as i know

lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.

Nevermind, user error.

ssurell said:
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Click to expand...
Click to collapse
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.

npjohnson said:
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
Click to expand...
Click to collapse
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1

ssurell said:
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
Click to expand...
Click to collapse
weird - we don't have MTG builds for 17.1 though, sadly.

How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.

ssurell said:
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
Click to expand...
Click to collapse
Why do you want encryption disabled?
It's hardware backed, and FBE, so very little gain from running unencrypted...
"Trust" has nothing to do with encryption, it can be on, off, trust just reports it to the user.
Why do you want TWRP? Lineage Recovery does the job just fine. What do you mean "/data (formerly userspace)"? That statement doesn't make much sense.
Regardless of all the above, the disabel force encrypt zip, followed by `fastboot -w` to format userdata ought to do it - but be warned, if you set a PIN, Android (AOSP, not a lineage thing specifically) will re-encrypt you... hence there being no point.

Related

[ROM][T710/T715][9.x] LineageOS 16.0

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
Requirements:
- twrp 3.2.0+ with treble support https://forum.xda-developers.com/showpost.php?p=78708796&postcount=2
- backup everything before install including efs partition
- wipe cache and vendor partitions before install
Install:
- Flash zip in compatible TWRP
- Don't forget about gapps (arm 9.0)
Google apps should be installed via recovery immediately after installing ROM.
If you reboot into ROM before installing Google apps, you must factory reset and then install them, otherwise expect crashes.
Doesn't work:
RIL
Download:
0207 build
T710: https://drive.google.com/open?id=1VScAyyvr8WcAseGAFVmIM4DPd2-Q1Us6
T715: https://drive.google.com/open?id=1q7oHTyV_JJGG3B56h0Wd_QiUsKn6hVzg
Device sources:
https://github.com/bonuzzz

treble-enabled twrp
t710: https://drive.google.com/open?id=1d0YycDthOxo7IM1b5gZbNI7zCdlu2Cix
t715: https://drive.google.com/open?id=1wrZKDMQcosQRrZGDypIG27Oqv-zL6m2G
known issues:
info on data partition is not accessible

Hi, thank you for the build, awesome! I was going to install LOS 15 but now I'll go directly for this one. I'll tell you how it goes
Sent from my Aquaris M5 using Tapatalk

Hello bonuzzz thanks for your hard work, I think there is not a lot of change to do but can you make a lineage rom 16.0 for t810. Thank you in advance.

Hockron said:
Hello bonuzzz thanks for your hard work, I think there is not a lot of change to do but can you make a lineage rom 16.0 for t810. Thank you in advance.
Click to expand...
Click to collapse
Unfortunately it's not so simple. So no new builds for t810/t815 at least in near future (several months). I focus on t710/t715 only.

as usual gr8 job ma8 considering. We got los15.1 stable finally seeing this beta makes me really happy so, keep up the good work...

This project is suspended. Maybe temporarily, maybe not. I tried to estimate how much time I need to get it stable and to be honest I don't want to have deal with it. As I know few developers are already working on lineage16 since november. Maybe they will upload anything to public. What about me, I don't want to spend months and some day one dev just kang my work again. Thanks for understanding.

bonuzzz said:
This project is suspended. Maybe temporarily, maybe not. I tried to estimate how much time I need to get it stable and to be honest I don't want to have deal with it. As I know few developers are already working on lineage16 since november. Maybe they will upload anything to public. What about me, I don't want to spend months and some day one dev just kang my work again. Thanks for understanding.
Click to expand...
Click to collapse
Its very sad for everyone that you abandoned the rom, but I understand what not having the time and the energy means. Thank you very much for the build. In any case I installed as I said before.
I haven't tested it much but for the time being its running pretty smooth. I installed some apps and no crashes so far. Just an error message at boot saying something happened, after closing it everything OK.
I add some screenshots here.
Ill keep posting issues if I find any. Do you think I could compile your sources in my computer?
{
"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"
}
Sent from my SM-T710 using Tapatalk

what to do when you are sick and staying at home? answer is simple:
new lineage16 builds are uploaded.
all hw stuff has been brought up except ril on t175, so no mobile network support yet. everything else should work.
links are in first post.

How much work should it be done to port this onto T810? And do you know anybody is doing it?

frankieboy1233 said:
How much work should it be done to port this onto T810? And do you know anybody is doing it?
Click to expand...
Click to collapse
not so much really but anyway it does
as I heard Ather was doing llineage16 with another dev. Maybe someone else.

T815 plzz. I have no knowledge about porting roms, but if by any way I can help u in porting this to T815 plzz let me know...

sweet, i saw your trebel twrp in the other forum, freaking fntastic

#1. Loaded trwp and ROM only no root
Excellent power 97 percent remain after 13 hours
No 5gz WiFi. But because I had nothing else loaded I couldn't see the nvram_net.txt settings.
So I tried to load pico and lineageos add-on su, and had several boot up and setup issues with the play services kept crashing. After bypassing lots of stuff, gave up and reloaded, I was able to see the root permissions in the developer settings, but lineageOS extras shows only arm 15.1 no 16 for root. Thought that was an issue. Silly me I didn't do a logcat. Before I did #2
#2nd try wipe , load, pico and magisk 17 . no magisk 17 in apps.
Did a bypass load apps to get to desktop. Had a couple " this device has errors, please contact manufacturer "
Play store was able to install apps, but I had no access to my paid apps. See #1 I wanted to fix my 5gz WiFi files. And I use es file explorer pro, but since I didn't have root... Well.
Play store recovered my programs am going to try magisk 18 . BRB
Looks nice, a couple of google play store bugs, an actuall desktop black out.
In conclusion, awesome ! Work !
Will fiddle some more. couldn't get a logcat

Downloaded all my gapps, and I found an unofficial root for lineageos 16 in another forum.
Trying again. Cheers
https://androidfilehost.com/?fid=11410963190603875495

issue with paid apps i think is more gapps issue rather than device specific because i have the same behavior on another devices and had to flash one image several times before got showing my purchases in play store

bonuzzz said:
not so much really but anyway it does
as I heard Ather was doing llineage16 with another dev. Maybe someone else.
Click to expand...
Click to collapse
i have an 815 to test as well
---------- Post added at 05:35 AM ---------- Previous post was at 05:17 AM ----------
bonuzzz said:
issue with paid apps i think is more gapps issue rather than device specific because i have the same behavior on another devices and had to flash one image several times before got showing my purchases in play store
Click to expand...
Click to collapse
Same here.
I got 5gz to work . I changed
Code:
ccode=US
regrev=69
Based on several posts over the years, I researched what regrev is in related to the ccode
It relates to what frequencies and I believe power outputs for different countries legal free and open radio frequencies.
The clues are in the driver for the wireless device source code.
Here is a broadcom driver for the 3.10 kernel
https://android.googlesource.com/ke...drivers/net/wireless/bcmdhd/dhd_custom_gpio.c
In there is a small database that should be consulted when you boot up your device and your country code should be selected when the driver is accessed
This has never worked properly for any lineageos based ROM.
Also most stock ROMs do not have this in their correctly.
All the files in /system/vendor/etc/wifi that have nvram in their name ( total 6 files ) need updated manually with an editor with root access.
As soon as I enter codes and reboot, I see all the 5 gz and many other networks that normally are too far away.
Kind of a chore to do this on every reloaded device, but that's what it takes.

Will this work on the 2015 model? I was able to flash it on my Tab S2 running exynos processor however it won't past the samsung logo.
Tried not flashing the gapps package to make sure that wasn't it... still stuck with recovery only. Any ideas?

samw52000 said:
Will this work on the 2015 model? I was able to flash it on my Tab S2 running exynos processor however it won't past the samsung logo.
Tried not flashing the gapps package to make sure that wasn't it... still stuck with recovery only. Any ideas?
Click to expand...
Click to collapse
Same here I cant flash Gapps with out it sticking on Samsung's boot logo

@samw52000 @legojoe8 read the first post carefully, in particular about twrp

[OFFICIAL] LineageOS 18.1 for the Moto Z2 Force

How did you find this? I got an alert that lineage 18 came out but went to the website less than five minutes ago and it wasn't available for nash yet ?
*Edit* I just checked again it's not available for download even though it's listed ..weird

PrivyetCyka said:
How did you find this? I got an alert that lineage 18 came out but went to the website less than five minutes ago and it wasn't available for nash yet ?
*Edit* I just checked again it's not available for download even though it's listed ..weird
Click to expand...
Click to collapse
Am the developer - and it is building on official servers tonight, check back in 24 hours.

npjohnson said:
Am the developer - and it is building on official servers tonight, check back in 24 hours.
Click to expand...
Click to collapse
Oh awesome. Thank you for the hard work ! Glad to see roms still being made for this phone

Just flashed on my t-mobile device from recovery. My phone is bricked. The battery life on my z2 force was getting old anyway so I am probably going to have to get a new phone if I can't fix it.
If you have a t-mobile device DO NOT FLASH FROM RECOVERY!!!

I fixed it! Please make sure to flash lineage from your computer when you are updating to a new version of lineage... NP Johnson makes this clear in his instructions. Unfortunately it has been awhile since I have flashed a rom onto a phone and I forgot that step...
here is how I did it
fastboot flash boot_b recovery-nash.img
factory reset your phone
flash the lineage zip from your computer using adb sideload lineage 18.1 nightly

Very good upgrade, thanks for the hard work and making this real

Thank you for not letting our device die

Thanks a ton for keeping our device up to date! I see that the efficiency mode is working for the battery mod, amazing!!

The clock app is not working and I think usb tethering is not working.

Vibration is not working

Firstly, THANKS FOR THIS!
I get the following error when opening the Camera app: dlopen failed: library "libmcf-jni.so" not found.
HDR mode is missing and you still can't save to SD - otherwise seems to work OK
Install steps taken:
1. adb sideload lineage-18.1-20210401-nightly-nash-signed.zip
2. Reboot into the newly-updated 18.1 recovery
3. adb sideload MindTheGapps-11.0.0-arm64-20210328_143848.zip
Since I was updating from 17.1 with Google Apps, I did not perform a factory reset per the upgrade instructions here: https://wiki.lineageos.org/devices/nash/upgrade
Was this wrong? Should I have done a clean install?

Big_Brother_Is_Watching said:
Just flashed on my t-mobile device from recovery. My phone is bricked. The battery life on my z2 force was getting old anyway so I am probably going to have to get a new phone if I can't fix it.
If you have a t-mobile device DO NOT FLASH FROM RECOVERY!!!
Click to expand...
Click to collapse
Flashing from recovery is fine - so long as you can see the zip, it's no problem. Not sure where your problem hit.
But thank you for ultimately flowing the guide and using your PC, it just raised and more seamless.

vivebatu said:
Thanks a ton for keeping our device up to date! I see that the efficiency mode is working for the battery mod, amazing!!
Click to expand...
Click to collapse
Yup! And will from here on out
Big_Brother_Is_Watching said:
The clock app is not working and I think usb tethering is not working.
Click to expand...
Click to collapse
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
Manuelmartad said:
Vibration is not working
Click to expand...
Click to collapse
It works, your motor may have died.
wyldwilly said:
Firstly, THANKS FOR THIS!
I get the following error when opening the Camera app: dlopen failed: library "libmcf-jni.so" not found.
HDR mode is missing and you still can't save to SD - otherwise seems to work OK
Install steps taken:
1. adb sideload lineage-18.1-20210401-nightly-nash-signed.zip
2. Reboot into the newly-updated 18.1 recovery
3. adb sideload MindTheGapps-11.0.0-arm64-20210328_143848.zip
Since I was updating from 17.1 with Google Apps, I did not perform a factory reset per the upgrade instructions here: https://wiki.lineageos.org/devices/nash/upgrade
Was this wrong? Should I have done a clean install?
Click to expand...
Click to collapse
dlopen, HDR, and save to SD: all expected and WIP. Working on them

npjohnson said:
Yup! And will from here on out
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
It works, your motor may have died.
dlopen, HDR, and save to SD: all expected and WIP. Working on them
Click to expand...
Click to collapse
Noice/Thanks!
Oh, I'd like to report that my Mophie external battery seems to be working better than it did in 17.1.

wyldwilly said:
Noice/Thanks!
Oh, I'd like to report that my Mophie external battery seems to be working better than it did in 17.1.
Click to expand...
Click to collapse
That's efficiency mode and proper battery mod support for ya! Haha.

npjohnson said:
Yup! And will from here on out
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
It works, your motor may have died.
dlopen, HDR, and save to SD: all expected and WIP. Working on them
Click to expand...
Click to collapse
no, its not working i tried it on;stock and it works well

Wifi is not working, everything else looks fine. No using cellular (no chip in device). Any ideas?

idelgador said:
Wifi is not working, everything else looks fine. No using cellular (no chip in device). Any ideas?
Click to expand...
Click to collapse
sounds like a persist issue - did you ever flash pie firmware?

npjohnson said:
sounds like a persist issue - did you ever flash pie firmware?
Click to expand...
Click to collapse
Is that related to a previous flash of pie? :O

[11][OFFICIAL] CarbonROM | cr-9.0 [fajita]

{
"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?

[ROM][UNOFFICIAL] LineageOS 17.1 for Lenovo Tab M10 HD (TB-X505F/L/X)

Reserved.

can we flash it on x505x?

UDONTHAVERIGT said:
can we flash it on x505x?
Click to expand...
Click to collapse
Yes it should work on x505x.

I am reporting with an X505f, Lineage OS logo appears but goes into a bootlop ending up TWRP? How can i debug more? Any advice?
For reference OTA is at TB-X505F-S001142-210804_ROW.zip

What do i do when i have S001137? Can i just normally install this? TB-X505F
(I have twrp btw)

sinhus said:
I am reporting with an X505f, Lineage OS logo appears but goes into a bootlop ending up TWRP? How can i debug more? Any advice?
For reference OTA is at TB-X505F-S001142-210804_ROW.zip
Click to expand...
Click to collapse
Please format data and enable ADB On boot.

DominicNoobAtRoming said:
What do i do when i have S001137? Can i just normally install this? TB-X505F
(I have twrp btw)
Click to expand...
Click to collapse
I recommend upgrading to S001142 for safety reasons (since I'm not really sure about the changes Lenovo did between the updates).

tried this rom on a x505f.
A few issues:
1. I couldn't get it to start unless gApps was installed.
2. I also can't get the wifi to work at all.

How do i install the update safely becauss im worrying about bricking my tab

yukeiw said:
tried this rom on a x505f.
A few issues:
1. I couldn't get it to start unless gApps was installed.
2. I also can't get the wifi to work at all.
Click to expand...
Click to collapse
1. I didn't need GApps here. What do you mean "can't get it to start"? Care to be specific?
2. WiFi works OOTB here, but it may be due to kernel (highly unlikely tho as I tested kernels of all 3 tabs on my X505L). Were you on S001142?

henloboii said:
1. I didn't need GApps here. What do you mean "can't get it to start"? Care to be specific?
2. WiFi works OOTB here, but it may be due to kernel (highly unlikely tho as I tested kernels of all 3 tabs on my X505L). Were you on S001142?
Click to expand...
Click to collapse
I have same issue S001142, no WiFi on X505F, toggle just flicks on/off instantly.
However works fine without GApps (only because it wouldn't install, not enough system space Err70 apparently)

Same problem on my X505F, no WiFi. GApps worked well.

Can any X505F users send logs? I would like to take a look.

henloboii said:
Can any X505F users send logs? I would like to take a look.
Click to expand...
Click to collapse
happy to assist if you tell me what logs/where to pull them from, someone on telegram group said they were updating the image?

I tried this on my X505L and I couldn't get it to boot using S001142 and TWRP following the instructions exactly, is there a way to log or debug it if it doesn't boot, or do I have to reflash the firmware and hope for a better attempt?

Hi,
I tried it on my X505F and it was not as easy as I thought. I already had S001142 and started with installing TWRP as denoted here:
[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD
This version of TWRP works on the Lenovo TB-X505F (wifi). For the TB-X505X, see this thread. For the TB-X605F/L, see this thread. For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC. #include...
forum.xda-developers.com
Installing Magisk led to some problems, though, as the wipe of /data afterwards prevented me from flashing the ROM ("Magisk binaries not found"). I had to install Magisk again *and* create a symlink from /data/adb/magisk to /data/magisk to be able to uninstall it again (additionally to renaming it to uninstall.zip etc.). Then I was able to flash this LineageOS.
It didn't boot, though, but was stuck at the Lenovo logo (very early boot phase). I flashed it again, but it didn't help. What *did* help was installing Magisk via TWRP Now the tablet booted into LineageOS, but only with an Android popup that some internal error occured and I should contact my vendor.
After having a black screen for a minute or so the LinageOS setup UI appeared and I was able to set up the clock. When reaching the WiFi page, I wasn't able to switch it on (like the other reported).
Attached you find a logcat and the dmesg output. I hope that's what you need.

I would love to try this but i do use bt audio so i look forward to any updates. i dont think ill ever see this thing run anything past android 10, but im not too worried about that, i know its an old cheap tablet. are you able to expand internal storage to an sdcard? my number one complaint about this thing is it always complaining of low storage.

Hay dose anyone have a copy of the stock firmware (so
TB-X505F-S001142-210804_ROW.zip)

I had the exact same experience as this. Ah well... It would've been nice to strip out this Lenovo bloated ROM with something sleeker.

[OFFICIAL] LineageOS 19.1 for the Razer Phone 2

{
"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"
}
Razer Phone 2
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 Razer Phone 2.
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.
aura - Official builds
aura - 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:
Known bugs:
- Chroma RGB LEDs are not implemented yet
Known bugs (won't fix):
- Can't switch screen resolution (defaults to 2560x1440)
Find any more? 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_razer_sdm845

Coming from PixelExperience. Performed a clean install of 19.1. Having an issue using a VoIP app. In this case Streams UC, but also experience the issue with voice calls on Signal. Everything works on outbound calls, but with inbound calls, the microphone isn't working. Caller cannot hear my voice. Any suggestions? Possible changes to the build.prop file?

runuts said:
Coming from PixelExperience. Performed a clean install of 19.1. Having an issue using a VoIP app. In this case Streams UC, but also experience the issue with voice calls on Signal. Everything works on outbound calls, but with inbound calls, the microphone isn't working. Caller cannot hear my voice. Any suggestions? Possible changes to the build.prop file?
Click to expand...
Click to collapse
it works on PE?

npjohnson said:
it works on PE?
Click to expand...
Click to collapse
No. This is why I switched from PE to Lineage 19.1 where it also didn't work. Flashed back to 18.1 and it is working.

Upgraded via adb successfully from the 18.1 ROM.
Got the 47% glitch during sideload, but it rebooted fine.
Similar results on my Razer Phone 1 (cheryl).
(Still mourning the end of HTC One M8 support, though.)

unsponsoredgeek said:
Upgraded via adb successfully from the 18.1 ROM.
Got the 47% glitch during sideload, but it rebooted fine.
Similar results on my Razer Phone 1 (cheryl).
(Still mourning the end of HTC One M8 support, though.)
Click to expand...
Click to collapse
Hint: I am working on m8 right now

npjohnson said:
Hint: I am working on m8 right now
Click to expand...
Click to collapse
That is good to know. I installed an unofficial LineageOS 18 ROM recently, but haven't played with it since then.

Just updated to LineagOS for MicroG 19.1 so far so good.

unsponsoredgeek said:
Upgraded via adb successfully from the 18.1 ROM.
Got the 47% glitch during sideload, but it rebooted fine.
Similar results on my Razer Phone 1 (cheryl).
(Still mourning the end of HTC One M8 support, though.)
Click to expand...
Click to collapse
If you read the install instructions this is normal behavior

npjohnson said:
Known Bugs:
Known bugs:
- Chroma RGB LEDs are not implemented yet
Click to expand...
Click to collapse
Not really a bug as its an app in the stock ROM. The current solution is to root and install Logo+ and it works.
Should also list Dolby Atmos missing too

omega552003 said:
If you read the install instructions this is normal behavior
Click to expand...
Click to collapse
I did. It was not unexpected.

I followed the instructions to the letter upgrading from 18.1 and mine is stuck in boot. It's been showing the little logo animation for almost 10 minutes now. Mild panic has set in.
edit: Fixed it!
Had the wrong gapps package. Downloaded the correct one, (MindTheGapps12.1 arm64 for those lost souls still out there).
Fixing procedure if stuck on LOS logo loop:
1. Make sure your devices is still plugged into your computer and hold down power button until you see the fastboot landing page where it gives you the option to pause boot. PAUSE BOOT.
2. hold down power button again to turn phone off. You'll know it's off when you get the white and black charge animation
3. hold power and volume down until you get to the recovery page.
4. Choose recovery mode, recovery from adb, and then run adb sideload /path/to/zip to install the correct gapps package.
Hope no one else does the same dummy move I did but if they do I hope this helps.
P.S. I have no idea yet what my screw up did long term btw. Device is still finishing the update. I did have to reinstall messages and gmail but for all I know that would have needed to happen anyway.

Just installed the UNOFFICIAL version on my Vzw RP2, but I can't make/receive calls/texts. Should Lineage work on the Verizon network?

edison said:
Just installed the UNOFFICIAL version on my Vzw RP2, but I can't make/receive calls/texts. Should Lineage work on the Verizon network?
Click to expand...
Click to collapse
Yes, it should. I remember seeing some folks have similar issues with 18.1 but I don't recall what the issue was. Maybe check out the 18.1 forums and see if there's any applicable advice there

Coming from Pixel Experience and I am getting audio crackling/stuttering only when using game streaming apps such as Moonlight and PSPlay and the volume is less than 50%. I had the same issue on Pixel Experience but the dev had fixed it using this commit. Any chance the fix can apply here too?

With the most recent build I am seeing Location pings even though Location is off and no apps are granted Location permissions. It was difficult, but I did get a screen capture of the event. You can see the location pip in the status bar. What is going on?

How do I root this version because I tried flashing the latest magisk zip and nothing happened do I have to rebuild the boot with magisk manager

Cylow333 said:
How do I root this version because I tried flashing the latest magisk zip and nothing happened do I have to rebuild the boot with magisk manager
Click to expand...
Click to collapse
I was looking for the same information

This is working very well for me keep up the good work. One thing I have found however is that while on a call rtt or tty as it is known seems to be on. I have made sure it is off in accessibility settings so I am sure it's just a bug but wanted to make aware of it. Does anyone else have this issue? I am on verizon. Not sure if that matters.

marcxpr said:
I was looking for the same information
Click to expand...
Click to collapse
I was able to root by adb sideload and running adb sideload followed by the magisk.zip file

Database Develop

welcome