Search results

I think 19.1 only gets monthly security updates for devices that didn't move to 20 in the build roster, unfortunately.

Yep same problems with NikGApps Full here, though it did seem like it took longer for the issues to occur with more GApps as system apps. Pixel Extended thread reads like it receives few updates and has a number of ongoing issues. So it's probably back to 19.1 for me as well. Edit: I even...

Of interest, my wife is running latest OP8T Pixel Experience 13, which is based on Lineage's trees, and doesn't have any of these issues, so either it's something completely isolated to the lemonadex trees, or there's some secret sauce somewhere to be discovered.

I experimented the last couple of days running without USNF, Shamiko or Zygisk enabled to see if it would make any difference, but still getting video hangs and RCS messages getting stuck until I Force close the app or Play Services. Next I'll try different GApps just to be certain of that variable.

Why are you in a root module thread if you don't have root. Of course it won't pass without root. 🤦‍♂️

Not going to hold my breath; an update to an app would have the same effect as a Force close, so would certainly temporarily get things working again.

No, that's cut from the end of my recovery.log from TWRP. You can tell from the digest/compatibility/SELinux checks and "I:" log entries. For comparison, here's my FKM log for the same kernel: Archive: /data/data/com.franco.kernel/files/blu_spark_r123-custom_op9x_9feb79506.zip inflating...

No such issues here: Installing zip file '/sdcard/franco.kernel_updater/blu_spark_r123-custom_op9x_9feb79506.zip' Checking for Digest file... Skipping Digest check: no Digest file found I:Update binary zip Verifying package compatibility... Package doesn't contain compatibility.zip entry...

I tried a format and factory reset yesterday and things look a little better, with more appropriate default permissions for Carrier Services and such, but all the problems remain. Still Google apps are all behaving weirdly, like my Calendar widget will go blank, Keep will freeze, Messages will...

I also failed Wallet "meeting security requirements" and clearing Play Services and Play Store was the only way to get going again. I started fresh with a clean Lineage install yesterday and even with USNF 2.4.0 set up to run from before initial setup lead to failed PI and SN, but reverting to...

Not fully phased out yet, and any gap in coverage is still suggestive of something being wrong with however 2.4.0 is selectively and temporarily spoofing.

I have noticed YASNAC sometimes failing CTS with 2.4.0 as well, especially directly after boot. This wasn't the case with 2.3.1-MOD_2.1 that I've seen.

Nope. Unrelated. Everything's still janky as ****. 🙃

Right, but arguably if Lineage's included firmware/vendor is going to match anything (and therefore presumably cause fewer problems) it'll be the Global device/ROM variant, which I do have, and which definitely is having some GApps problems, at least with the dirty upgrade from...

Yeah I don't know why you're starting with 19.1 and then upgrading; just flash 20 directly over last Android 12 stock, or if you've upgraded to 20 already then simply format data. The firmware and everything remain intact and wouldn't be related to any migration issues.

Yikes. Guess I'll have to bite the bullet and give that a try as well. Likely I'll just format data though, MSM shouldn't be necessary unless downgrading the bootloader.

Just noticed error reporting seems broken on Lineage 20/MindTheGapps 13 as well. Apps crash and nothing happens. Searching settings for Bug report handler suggests there should be an option in Developer options to select e.g. Google Play Services, but when you actually go to find the setting it...

You build them yourself from source.

Just for future reference, Android 12-13 TWRP is pretty much feature complete for OP9x: https://forum.xda-developers.com/t/recovery-3-7-0-12-1-unofficial-twrp-with-a12-a13-encryption-support.4523857/ Will be made official soon. @der_akinator has done an amazing job, and in a remarkably short...

TWRP might allow it?

Interesting... I'll revert and see if that helps any of the issues I had been chalking up as Lineage 20 and MindTheGapps 13 being janky. 😲

I'd be worried the decryption key would have been updated for Android 13, so a downgrade could result in being unable to decrypt and require a data format. Otherwise I'm tempted to do this myself, since Android Auto, Digital Wellbeing, Photos, Messages/Carrier Services (RCS), Keep and Calendar...

It only does that before Google Play Store is wiped. Wipe data and cache for Play Store again and reboot, then once it shows Certified again you should be able to see Netflix, etc. For the record, my flo is basically unusable with this ROM, lots of Launcher/SystemUI/Recents crashes and hangs...

Works fine for me with latest USNF and Shamiko. Then you need to wipe data of Play Store and Google Play Services, not just cache.

Having a misunderstanding and/or disagreement is one thing, but insults and name-calling cross a line.

I still use FKM for testing, and it still also flashes just fine on my lemonadep, for the record.

s/yet/ever/ 😉

Just Android Auto storage/cache? I'm starting to worry LOS20 might require a data wipe to function well. Curious if anyone sees the same issues with a clean flash. (I know a clean flash on upgrade is already best practice, but there ARE dirty update instructions on the Lineage Wiki, so this IS...

What's the adb vs MTP fix? I think most OnePlus devices need this!

I can confirm media playback issues in specifically Photos. Sometimes there's no sound but muting and unmuting in the app gets it going, then if it will only show as loading then Force close. Worse is Android Auto. Sometimes it shows a black screen and only a reboot will get it working; Other...

There already is one. Search settings for clock position. Something that is missing is an option to only show battery percentage when the quick settings pulldown is visible; looks like Android 13 made percentage visibility all-or-nothing, so a specific setting option to restore the previous...

Sounds not really like an AIK question... Anyway, the TWRP script is documented pretty well. https://github.com/osm0sis/twrp_abtemplate/blob/master/META-INF/com/google/android/update-binary#L57-L63 Since swapping in TWRP's ramdisk in effect unroots the device, the kernel/cmdline patches from...

Ohh, yeah, I don't have arm Linux or arm MacOS builds in there. Android arm binaries could potentially work since they're all static builds, if you want to mess with setting it up manually.

I mean, looks like that tmpfiles link is dead.

Thanks! Working so far with my usual modules! 🙌🤞

That's not a fix. That's a workaround. If you want to help me actually fix the issue (broken busybox sed under certain conditions?), please go back and provide the info/files I've requested.

But it's always my busybox, whether run booted or in recovery. I tested with both Lineage 20 booted and TWRP 3.7.0_12 recovery and can't reproduce the issue. You still haven't answered any of my questions or requests for info from any of my posts that could help me figure out further, so 🤷‍♂️

Even though you didn't answer any of my questions I looked into this today using the exact script you had posted, and anyway, I can't reproduce your issue at all: Parsing boot image: [/tmp/anykernel/boot.img] HEADER_VER [3] KERNEL_SZ [40954368] RAMDISK_SZ [45808778] OS_VERSION...

I've got no insider news updates, but hoping everyone is safe and well, and hoping to see some new official builds sometime this year. 🤞

@Displax Would something like QuickSwitch overlay trigger this as well? Or was it only fonts or specific kinds of overlay modules at fault?

This thread should probably be closed since what will become the new official TWRP thread is linked above. You should try the builds in that thread instead. I'm unsubscribing here now. 👍

I notice RCS was getting stuck as "Messages is doing operations in the background" or something like that, but force closing Messages and opening it again resolved it and all the RCS messages came in. I joined the Carrier Services Beta to see if it helps, and so far I think it has. Android Auto...

No, it won't, because it isn't in a separate partition anymore. See my above reply for a solution.

Pressing this setting shows a toast notification saying it can't be disabled (on boot-as-recovery and newer 2-stage-init devices). You can use my 98-twrp_ab.sh addon.d-v2 script to keep TWRP installed through an A/B update, however...

Yeah decided I'd put up with Trebuchet as Recents until Lawnchair starts publishing builds from their 13-dev branch since I really wanted to jump onto Lineage 20. Doesn't seem too bad!

If you don't see it in the OP it's not here. @Zackptg5 made a good bash module, check him out.

Just my opinion, of course! I personally use Lineage 20 with MindTheGapps, Magisk Canary and several modules (mostly my own, plus root hiding), blu_spark, Lawnchair Dev and MCG GCam.

OnePlus doesn't care about the community anymore (closed dev program, incomplete/broken source, removed decryption in stock recovery, removed advanced reboot, the list goes on...), so why should the community care about OnePlus? Support for custom ROMs is absolutely the only way to go here.

Ah, I was just going by what Fox's MMM reported. Didn't try to install since I was worried about that issue, so false alarm then I guess! Hopefully someone's reported the issue internally to kdrag0n. 🤞

Anybody know if this has been addressed for 2.4.0 public release which came out today?