New build with new kernel experiments targeting official release.
Please test and report whether audio works still:
Please test and report whether audio works still:
New build with new kernel experiments targeting official release.
Please test and report whether audio works still:
is that different from before, or?dirty flashed.
MEDIA audio is JUST BARELY audible at max volume. in any player or browser.
alarms, and phone calls are fine.
on the 9-9 rom i could start to hear MEDIA at 1/2 volume and up.
can you get me these logs:on the 9-9 rom i could start to hear MEDIA at 1/2 volume and up.
on this newest rom i can start to hear MEDIA at 3/4 volume and up. so yes, media on the newest rom borders on unusable.
adb root
adb shell lsmod > lsmod.txt
adb logcat -d > logcat.txt
adb shell dmesg > dmesg.txt
Soon on TheMuppets. But they're simply extracted from the latest OTA, as alwaysThanks for the hard work, @aleasto ! Do you have a link to the proprietary blobs sources? Wanted to try to spin a custom build myself...
noSo if I have the previous unofficial build installed, can I dirty flash the official nightly with no issues?
Yes we do support VoLTE.Thanks for all your hard work Aleasto, I just ordered my pixel 5a yesterday and I am looking forward to installing Lineage on it!
I'm coming to the Pixel 5a from an LG V30 running SGCMarkus' 17.1 unofficial build as it does not and never will have VoLTE and...CDMA service here is "usable" - in the sense of you can make a call...eventually and maybe, if you're lucky you'll be able to talk long enough to finish your conversation without the call dropping
I do have a few questions (not specifically for anyone, they're general questions):
- I hadn't been able to find this specific question answered, but does VoLTE work on Verizon with this build?
- I know "Ol' Faithful" Titanium Backup has been defunct for awhile now but it was what I'd always used. Does it still work for moving data? Specifically SMS/MMS messages, call logs, bluetooth pairings, remembered wireless networks, and I know you can't restore apps anymore, but restoring data was still working when I moved to my V30 as long as you installed the app first. Is this still accurate or should I not even try?
- What do people use for backups these days? Since the Pixel has no micro sd slot (another phone, another feature that I had to trade off) I concerned about being able to backup my device, automatically on a schedule. I read that SeedVault was being adopted by Lineage as the "official" backup, but no new information on that front seems to have surfaced in almost a year.
Great, thanks again for all your hard work!Yes we do support VoLTE.
I don't know about titanium backup.
If you're looking to transfer data from your V30 running LineageOS just use Seedvault, assuming that your unofficial build is recent enough to have that on 17.1.
It supports SMS, call logs, apps and their data.
Also if you use google services, their backup provider does the job as well.
Oh just get the official apk from apkmirror or similar. Latest stable version is 8.2.400Works like a charm! Thanks for your hard work on this. Any recommendations on a replacement for GCam, as the one on the Play Store is so old? I downloaded the latest Camera PX from the GCamMod hub and seems to work well enough -- just want to make sure I'm not missing any other obvious options.
After flashing 19, before booting. Mind that you still must reboot to recovery between the two sideloads.I saw Lineage 19.1 drop. Two questions.
First, when I upgrade, regarding this: "NOTE: If you previously had any Google Apps add-on package installed on your device, you must install an updated package before the first boot of Android! If you did not have Google Apps installed, you must wipe the Data partition (or perform a factory reset) to install them."
By first boot, do you mean before first boot after upgrade to 19.1 or do you mean first boot after Lineage 18.1 was installed ever? I guess my question is, do I have to add gapps if I already have gapps installed? Sorry if this is a basic question, but I'm confused. I do have gapps installed on 18.1. My guess is I need to load the (newest) package again after 19.1, but wanted to confirm.
No more updates.Second, are there going to be any more 18.1 updates? I don't know if I'm quite ready for the Android 12 experience, I'm pretty happy as-is with my phone. But I also don't want to stop receiving security updates if 18.1 is dead now.
If you installed Magisk by sideloading in recovery it will persist the update. Otherwise you'll need to reinstall it after the update if you want to keep root.Two update questions:
- I just got notice for OTA update. For the OTA updates, do we need to disable/uninstall Magisk before applying the update?
- Is there a way to do a Nandroid (or similar) backup in recovery before applying an update so we can roll back if it goes wrong?
I doubt you need to set device fingerprint to Pixel 5 for safetynet.Thanks for putting this together so quickly! I've been running for a couple of days now with MindTheGapps and haven't noticed any significant issues. I'm now pretty darn satisfied with my new 5a (Even though it's a friggin chonk). I'm on Visible and I was able to just pop my SIM card in and everything worked. Wifi calling, texting, 5G connection, etc - all good.
Only weird thing I've noticed is that after setting up fingerprints for device locksreen security I'm not able to then use fingerprint security within my other apps. For example - Chase app tells me "You haven't set up fingerprint sign in on this device", PayPal app says "We're having trouble confirming your fingerprint right now" and Bitwarden app doesn't present an option to enable "Unlock with Biometrics". So I'm using currrently using PINs for these apps which is a fine compromise for me - would be curious to know whether others have experienced this.
There have been some changes to SafetyNet in the past couple of days that tripped ctsProfile on my Pixel 4a running official LineageOS but I was able to pass SafetyNet check in this ROM by installing kdrag0n's Universal SafetyNet Fix v2.0.0 and using MagiskHide Props Config to set device fingerprint to Pixel 5.