Develop Bugs

Apps Not Automatically Updating

I'm not sure if this is an issue with the Pixel 2 XL or an Android OS bug but it's happening on my Pixel 2 XL so I'm adding here.
I have the Google Play Store app set to automatically update apps when connected to WiFi but apps are not updating. I've been connected to my home wifi for several hours and there are still apps waiting to update.
Anyone else having this issue?

jimv1983 said:
I'm not sure if this is an issue with the Pixel 2 XL or an Android OS bug but it's happening on my Pixel 2 XL so I'm adding here.
I have the Google Play Store app set to automatically update apps when connected to WiFi but apps are not updating. I've been connected to my home wifi for several hours and there are still apps waiting to update.
Anyone else having this issue?
Click to expand...
Click to collapse
I feel like it automatically downloads when on WiFi and connected to power even though there's no setting for power connected.
Sent from my Pixel 2 XL using Tapatalk

I'm having this issue too....mine doesn't auto update...even when connected to power and wifi.

I have the same problem. I've literally tried everything I could think of.

Yes! Bump! I've actually been having this problem as far back as February (at least that's around when I noticed) and had been meaning to make a thread, but hadn't gotten to it 'til now; and XDA showed this thread when I was creating so, I'll be pleading here...
I, too, FOR THE LIFE of me can't correct this...!
My setup: running Oreo 8.1 May update, rooted, Flash kernel, TWRP 3.2.1-2 custom recovery, a few Magisk modules (see sig).
Troubleshooting: rebooted, plugged phone in, allowed all permissions and ability to modify system settings, I've changed it to auto-update apps "at any time" (both mobile data & wi-fi), when updating to May patch I wiped the System partition and flashed the May Full Factory image, cleared Play Store app cache, cleared Play Store app data, uninstalled Play Store updates, Disabled Play Store - then Enabled, uninstalled Google Play Services updates / reset to factory version, and finally manually updated Google Play Services.
Anyone, any thoughts/ideas/advice?! I had hoped the last 3 months' security patch updates might fix this, but since it hasn't, my last hope is here...! :begging:
P.S. I am hoping that flashing a full factory image with the -w intact/included is not the last and only option...

simplepinoi177 said:
Yes! Bump! I've actually been having this problem as far back as February (at least that's around when I noticed) and had been meaning to make a thread, but hadn't gotten to it 'til now; and XDA showed this thread when I was creating so, I'll be pleading here...
I, too, FOR THE LIFE of me can't correct this...!
My setup: running Oreo 8.1 May update, rooted, Flash kernel, TWRP 3.2.1-2 custom recovery, a few Magisk modules (see sig).
Troubleshooting: rebooted, allowed all permissions and ability to modify system settings, I've changed it to auto-update apps "at any time" (both mobile data & wi-fi), when updating to May patch I wiped the System partition and flashed the May Full Factory image, cleared Play Store app cache, cleared Play Store app data, uninstalled Play Store updates, Disabled Play Store - then Enabled, uninstalled Google Play Services updates / reset to factory version, and finally manually updated Google Play Services.
Anyone, any thoughts/ideas/advice?! I had hoped the last 3 months' security patch updates might fix this, but since it hasn't, my last hope is here...! :begging:
P.S. I am hoping that flashing a full factory image with the -w intact/included is not the last and only option...
Click to expand...
Click to collapse
I've said it before that, for me at least, I've noticed it only auto updates when plugged in even if I have plenty of battery like greater than 50%. I'm set to auto update on WiFi only. I'll go into the app store and see I have a handful of update, plug in, and see them to start downloading.
Sent from my Pixel 2 XL using Tapatalk

EeZeEpEe said:
I've said it before that, for my at least, I've noticed it only auto updates when plugged in even if I have plenty of battery like greater than 50%. I'm set to auto update on WiFi only. I'll go into the app store and see I have a handful of update, plug in, and see them to start downloading.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I eventually noticed as well that it only updates when plugged in. I'm not sure if it has anything to do with how charged the battery is but I haven't looked too closely at that.

....yea...I've also plugged in as well, i'll edit to reflect that...
...BUT I think I'm onto something...does anyone/everyone that has this problem have Titanium Backup installed and running btw???

Same, only auto updates when plugged in...
I always have Titanium which is running normally... Awesome app!

Yea...I get that apps are really only automatically updating when plugged in. But assuming even that isn't allowing apps to automatically update....
i'm more wondering if @upperbladez and @smokeythebear3 have Titanium Backup installed; as that's what was stopping the updating the apps automatically....

simplepinoi177 said:
Yea...I get that apps are really only automatically updating when plugged in. But assuming even that isn't allowing apps to automatically update....
i'm more wondering if @upperbladez and @smokeythebear3 have Titanium Backup installed; as that's what was stopping the updating the apps automatically....
Click to expand...
Click to collapse
I do not have Titanium Backup Installed...I don't have any power saver apps either. It's really agitating

upperbladez said:
I do not have Titanium Backup Installed...I don't have any power saver apps either. It's really agitating
Click to expand...
Click to collapse
Yeah...I had really high hopes earlier as well, but found that it wasn't TB. Because there is a setting in the preferences that deals with auto-updating and it seems that, by default, it sets it to Disabled, but even after Enabling it, it hasn't gotten auto-update to work.
I had inadvertently thought it worked because, at the same time as the TB discovery, I reset to factory settings both Google Play Store and Google Play Services (as I have many times before). This seems to have the auto-update work once, but I can't get it to replicate or do it again after this first initial time. Also, it's hard to debug, troubleshoot, and test because I have to wait some time for a number of apps to need updating before I can see if it truly works or not.
I hope someone has an idea or thought that might explain why or help reach an explanation...

simplepinoi177 said:
Yeah...I had really high hopes earlier as well, but found that it wasn't TB. Because there is a setting in the preferences that deals with auto-updating and it seems that, by default, it sets it to Disabled, but even after Enabling it, it hasn't gotten auto-update to work.
I had inadvertently thought it worked because, at the same time as the TB discovery, I reset to factory settings both Google Play Store and Google Play Services (as I have many times before). This seems to have the auto-update work once, but I can't get it to replicate or do it again after this first initial time. Also, it's hard to debug, troubleshoot, and test because I have to wait some time for a number of apps to need updating before I can see if it truly works or not.
I hope someone has an idea or thought that might explain why or help reach an explanation...
Click to expand...
Click to collapse
Yeah it's so agitating?

I think I figured it out....[GUIDE] included!
I think I figured it out (at least in my case) -- but I think it's probably applicable to most any other(s) who are having the same issue...
First of all, if you have Titanium Backup, make sure to set Default auto-update app to Enabled
Go to Menu
Preferences
Go to Restoration Settings
You will find Default auto-update mode in the section; 4th on the list within that section
Go to Google Play Store App Info
Clear Cache (inside Storage)
Clear Data (also inside Storage)
Disable the app
Click OK when warned that it will "replace this app with the factory version..."
Go to Settings, Apps & Notifications, See all ### apps
At the top right, select the 3 verticle dots and select "Show system"
Find and select Google Play Services
Clear Cache
Go back to App Info (back arrow; arrow pointing left), at the top right, select the 3 vertical dots and select "Uninstall updates"
Click OK when warned that it will "replace with the factory version..."
Reboot
Download the latest Google Play Services
HERE'S one place you can find it and/or you can Google search to find other copies yourself...
Pick the newest latest version (beta if you wish to be on bleeding edge but stability not ensured)
Choose the Android 8.0+ variant
Download the "arm64 + arm" & "nodpi" one
Install the latest Google Play Services using the file you downloaded
Reboot
Go back to Google Play Services App Info (show all ### apps, show system, etc.)
Clear Cache (of Google Play Services)
Go back to "show all ### apps"
Select the drop-down menu and select Disabled
Select Google Play Store
Clear Cache and Data (of Google Play Store inside Storage)
Plug Phone to charger
Launch Google Play Store
Select the 3 stacked horizontal lines on the top left and go to Settings
Select and configure how you wish to auto-update apps
Click on Play Store version (all the way on the bottom)
After pressing OK (it'll most likely say Play Store will update soon), it may or may not begin downloading components for the Play Store. After a bit, it may or may not actually begin auto-updating...
In the few instances I've done this and on the 2 pixel 2's I have access to, the auto-updating may begin soon after (within 2 minutes), or eventually (sorry for vague description, but I had thought these steps didn't work and wasn't paying attention and after a while, I saw it auto-updating!).
Also, it still seems that it'll auto-update only while plugged in charging. That particular bug/requirement hasn't been resolved, but as this is specifically an auto-update troubleshooting thread.......
Hope this helps any/all who is having the same issue. I hope (but am doubtful) that this will work for everyone; but if it doesn't, I'd have to say that it might be something with your ROM (stock or custom), settings (system or another app interfering [As I found out TB actually might/does]), or some very unique bug because this is probably the most comprehensive app reset for Google Play. It's kind of overkill, but you might have some luck going the "last resort" route and flashing the Full Factory image in hopes it'll fix the system and app comparability issues (if that is indeed the reason...).
In the end, I hope this helps any who might be having this issue....:victory::highfive:

I have this same issue. I tried wiping Google Play cache/data and had a hell of a time getting it to show my installed apps after that. I don't have TB installed so I'm not really sure what's going on. It's a PITA having to manually update apps all the time.

corywf said:
I have this same issue. I tried wiping Google Play cache/data and had a hell of a time getting it to show my installed apps after that. I don't have TB installed so I'm not really sure what's going on. It's a PITA having to manually update apps all the time.
Click to expand...
Click to collapse
Yeah....but maybe uninstalling Google Play store (not just cache and data and actually reverting to an older version) and doing the same (sorta) towards Google Play Services is the critical difference (as shown in my guide)... Hopefully that sorts ya out...!:good:
Good luck to ya!

I'm set to auto update over WiFi, and I've never actually paid attention.. but my apps are always updated and I get the notification stating that 13 apps were updated... So it must be working on my end?
EDIT: Not sure if it would make a diff, but I am running latest DU...

Az Biker said:
I'm set to auto update over WiFi, and I've never actually paid attention.. but my apps are always updated and I get the notification stating that 13 apps were updated... So it must be working on my end?
Click to expand...
Click to collapse
Yes, that's "the dream" . For us/me, that wasn't happening -- for whatever reason; whether it was set to do it over WiFi or both mobile & WiFi.
I used to not pay attention either, until I went and checked and kept finding a list of 50+ apps needing to update and/or all these apps were outdated every 3 or so days! Then I realized I hadn't been getting that which you are experiencing... And, as @corywf as stated, it can get quite tedious and annoying having to manually "Update all" every few days just to keep all the apps up-to-date! (Curious note: I never realized how many times in a small number of days certain apps actually update; it's like every 2 days! Which is nice and good to say towards the app as the devs are continuously working on it -- Instagram, Nextdoor, and Chrome come to mind -- but certainly rather annoying when manually "keeping up") Especially when we've all experienced these things happening automatically and in the background...

I had this issue since the Feb or March update I think but since flashing the May update, apps are back to updating automatically

Tebor said:
I had this issue since the Feb or March update I think but since flashing the May update, apps are back to updating automatically
Click to expand...
Click to collapse
That's good! I believe it was around the same time I noticed the issue as well (although as said in my last post, this is usually something that is in the background and done automatically so I can only say it was around this point). I'm glad flashing the latest update worked -- I'm wondering, did you flash a Full Factory or an OTA? -- and hopefully it works for others. But, unfortunately, I had Full Factory flashed to the May update with no such luck. It took my guide (a little up above) to fix it on me and my gf's Pixel 2 (non-XL)...
Cheers! :highfive::victory::good:

Samsung Wearable App Crashing?

Hi!.
I've been having this annoying problem with Galaxy Wearable app for the last three days where the app crashes on launch every time. I've been trying to fix it all this time and i have tried different remedies that didn't help at all. I haven't the slightest clue what's wrong and i don't know where to ask for help so i figured i ask for it here first. I'll post a logcat if anyone is willing to help.
Here's what i've tried so far:
1. Cleared cache - Didn't fix the issue
2. Cleared storage - Didn't fix the issue
3. Complete reinstall of the Wearable app and services - Didn't fix the issue
4. Removed the Samsung account - Didn't fix the issue
5. Resetting the watch and setting it back up again - Didn't fix the issue
6. Tried 3 and 5 together - Didn't fix the issue
7. Did a clean install of ROM (Havoc 2.8) - Fixed the issue but it came back in about an hour
9. Rolled back to the previous build of Havoc (2.7) - Same as above, problem came back after some time
10. Dirty flashed 2.8 - Same
11. Restored to 2.8 and uninstalled a bunch of apps that i thought might be clashing with the Wearable app - Didn't fix the issue
ANY help would be much appreciated. I'm starting to think something is wrong with the watch itself.
EDIT: Never mind, i found what's going on. It's Samsung Pay that's making the app crash. I uninstalled it on a whim and now it works!!! Mods, kindly delete this thread.

How much memory your phone got? Try to close all other apps and then try. I have the same behave with other apps on my Moto phone.

Helhound0 said:
Hi!.
I've been having this annoying problem with Galaxy Wearable app for the last three days where the app crashes on launch every time. I've been trying to fix it all this time and i have tried different remedies that didn't help at all. I haven't the slightest clue what's wrong and i don't know where to ask for help so i figured i ask for it here first. I'll post a logcat if anyone is willing to help.
Here's what i've tried so far:
1. Cleared cache - Didn't fix the issue
2. Cleared storage - Didn't fix the issue
3. Complete reinstall of the Wearable app and services - Didn't fix the issue
4. Removed the Samsung account - Didn't fix the issue
5. Resetting the watch and setting it back up again - Didn't fix the issue
6. Tried 3 and 5 together - Didn't fix the issue
7. Did a clean install of ROM (Havoc 2.8) - Fixed the issue but it came back in about an hour
9. Rolled back to the previous build of Havoc (2.7) - Same as above, problem came back after some time
10. Dirty flashed 2.8 - Same
11. Restored to 2.8 and uninstalled a bunch of apps that i thought might be clashing with the Wearable app - Didn't fix the issue
ANY help would be much appreciated. I'm starting to think something is wrong with the watch itself.
EDIT: Never mind, i found what's going on. It's Samsung Pay that's making the app crash. I uninstalled it on a whim and now it works!!! Mods, kindly delete this thread.
Click to expand...
Click to collapse
Yep had the same exact problem the other day after upgrading to Android 10. There's another thread in here where I found the same issue (it's throwing a java ClassNotFound exception on mine). It's especially nefarious because they sideload the pay plugin so you won't see it if you're uninstalling via the play store, and it's not sorted alphabetically with the other Samsung apps so you might not even see it if you're searching manually.
I say nefarious because depending on how bad the crash is (background task vs UI), they may not be able to even push an automatic fix since they're not using the play store. Seems like a pretty terrible approach to me.
Sent from my Pixel 2 using Tapatalk

oxygenes said:
How much memory your phone got? Try to close all other apps and then try. I have the same behave with other apps on my Moto phone.
Click to expand...
Click to collapse
I got 3 gigs and not even half of it being used at idle. And i don't really do memory intensive stuff on my phone anyway. The issue was definitely Samsung Pay. if anyone has this issue where you're running Pie and are rooted with any version of magisk, uninstall Pay. It's been a few days and i haven't had this issue repeat even once.
shmaque said:
Yep had the same exact problem the other day after upgrading to Android 10. There's another thread in here where I found the same issue (it's throwing a java ClassNotFound exception on mine). It's especially nefarious because they sideload the pay plugin so you won't see it if you're uninstalling via the play store, and it's not sorted alphabetically with the other Samsung apps so you might not even see it if you're searching manually.
I say nefarious because depending on how bad the crash is (background task vs UI), they may not be able to even push an automatic fix since they're not using the play store. Seems like a pretty terrible approach to me.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I just uninstalled Pay from the app list in settings and rebooted. If there is a sneaky sideloaded plugin somewhere, it doesn't seem to be interfering with the Wearables app anymore.
And I guess you're right about this being a terrible approach. But Pay isn't even supported where i currently live so my question is WHY even sideload it on a device being used in an unsupported region... Such a waste of resources.

Question Problems with app permissions, Dev mode, Autonotification - Color OS

Hi All,
Just upgraded from LGV30 to OnePlus 9 Pro. I'm in China so running Color OS and actually hoping to stay on that (I think).
Google account, play services and play store all working fine.
I have activated Developer Options but the phone then deactivates it, with a warning that it might not be safe.
App permissions (and accessibility permissions) that I set manually are revoked.
Autonotification doesn't seem to be consistently getting access to notification contents.
I believe autonotification is not getting the info because of permissions.
It's been so long since I was on an up to date version of Android, I don't know if these issues are due to the OS, Android 11, or OnePlus.
Does anyone have any light to shine on this?
Also, please let me know if I should post this in a different forum.

That's why we hate ColorOS. Maybe you should contact OnePlus directly to fix these "bugs".

AndroPlus said:
That's why we hate ColorOS. Maybe you should contact OnePlus directly to fix these "bugs".
Click to expand...
Click to collapse
I believe a system update fixed it. Dev mode is now persistent, as are permissions. Autonotifcation has passed its first test and that leads me to believe my issues are now gone.

COLOR OS is literally '****'

General New Play System Update

Just had a new Play System Update 55mb. I'm now on Nov 1 instead of the August 1 after the last update.
https://imgur.com/a/yknsVGp

Same here.

Still on September. Won't find any update.
There is no way to force/sideload this, right?

@m1ckbr1t
Thanks for the heads up.
I have been checking a couple of times per week to update to the November patch, but I hadn't checked since Wednesday last week; I didn't realize the update was there until I saw your post

I went from Nov. 5 to Nov. 1

I got that update yesterday. My phone rebooted after it downloaded. Did the reboot happen to anyone else.

Bxrider117 said:
I got that update yesterday. My phone rebooted after it downloaded. Did the reboot happen to anyone else.
Click to expand...
Click to collapse
Yes it did

Bxrider117 said:
I got that update yesterday. My phone rebooted after it downloaded. Did the reboot happen to anyone else.
Click to expand...
Click to collapse
I thought the phone had rebooted yesterday but wasn't sure. This explains it.
I am on Nov 5.
But Google needs to fix bugs, not just security updates. Like the camera overprocessing, the screwy 4x zoom which is not used at times when chosen by the user, the sub-optimum battery, and the constant requests for PIN instead of FPS, or unlocking with a trusted device.

MacGuy2006 said:
I thought the phone had rebooted yesterday but wasn't sure. This explains it.
I am on Nov 5.
But Google needs to fix bugs, not just security updates. Like the camera overprocessing, the screwy 4x zoom which is not used at times when chosen by the user, the sub-optimum battery, and the constant requests for PIN instead of FPS, or unlocking with a trusted device.
Click to expand...
Click to collapse
I've had none of these issues

MacGuy2006 said:
I thought the phone had rebooted yesterday but wasn't sure. This explains it.
I am on Nov 5.
But Google needs to fix bugs, not just security updates. Like the camera overprocessing, the screwy 4x zoom which is not used at times when chosen by the user, the sub-optimum battery, and the constant requests for PIN instead of FPS, or unlocking with a trusted device.
Click to expand...
Click to collapse
have you guys seen this page. I dunno what to think anymore. the hype around Pixels is such a weird thing. I get that there are bugs (and I've had a few glitches) but none of the bugs I've had are even listed here:
Google Pixel 6, 6 Pro, & 6a new updates, bugs, issues, problems tracker
A detailed & continuously updated round-up of everything related to Google Pixel 6, 6 Pro, & 6a updates, bugs, issues, & problems.
piunikaweb.com

MacGuy2006 said:
But Google needs to fix bugs, not just security updates. Like the camera overprocessing, the screwy 4x zoom which is not used at times when chosen by the user, the sub-optimum battery, and the constant requests for PIN instead of FPS, or unlocking with a trusted device.
Click to expand...
Click to collapse
When the phone fails to read your Fingerprint (something along the lines of three or four times in a row), it automatically blocks/deactivates the FPS, until you unlock it with your TO KNOW security measure (in your case PIN).
I had it happen to me a couple of times over the course of this month, and it was a tad too annoying to shrug off. I definitely miss my old P4 Faceunlock, never bothered me (except when I wore masks, lel).

I had it as well ... was on Nov 1, update, reboot and still on Nov 1 ...
Note there are two things: (a) security update (Nov 5 in my case) and (b) Play-systemupdate (Nov 1 in my case).
See screenshot.

When I manually checked for a Play System update just now, it told me my update was over 600 MB! Sorry, no screenshot.

roirraW edor ehT said:
When I manually checked for a Play System update just now, it told me my update was over 600 MB! Sorry, no screenshot.
Click to expand...
Click to collapse
Damn that's huge for a play system update. You have an unlocked device or carrier?

roirraW edor ehT said:
When I manually checked for a Play System update just now, it told me my update was over 600 MB! Sorry, no screenshot.
Click to expand...
Click to collapse
You apparently ordered the supersize version at the drive-thru

pimpmaneaton said:
Damn that's huge for a play system update. You have an unlocked device or carrier?
Click to expand...
Click to collapse
Yes, I have the Unlocked (and rooted) 512 GB model, using on AT&T. Maybe it hadn't checked for any Play System updates since I rooted - since I waited to root (and disable verity and verification, and flash the stock firmware and wipe) until just a week and a half ago (I think).
I confirm it now says November 1. Thank goodness Settings has search and I'm also glad it remembers my last several searches in settings, even after a reboot.
Lughnasadh said:
You apparently ordered the supersize version at the drive-thru
Click to expand...
Click to collapse
LOL!!!!

Lughnasadh said:
I went from Nov. 5 to Nov. 1
Click to expand...
Click to collapse
You do realize that Google Play system update (Settings > About phone > Android version > Google Play system update) is different from the monthly security patch (Settings > System > System update), right?

snoopygum said:
You do realize that Google Play system update (Settings > About phone > Android version > Google Play system update) is different from the monthly security patch (Settings > System > System update), right?
Click to expand...
Click to collapse
Yes, of course.

Lughnasadh said:
Yes, of course.
Click to expand...
Click to collapse
Excellent, because judging by some of the posts here that's not quite universal.
In case anyone is still confused:
Monthly patch - Nov 5
Google Play system Update - Nov 1

any noticeable changes? I'm asked to reboot... but I rather not until the next system update

Question [partly solved]After downgrading to Android 12, every browser keeps closing itself within minutes

Hi all,
Now I can't browser, I wrote this post via Pixel 3.
Just in one day time, I updated my Pixel 6 to Android 13, then forced downgrading to Android 12.
Now I almost have the same settings and Apps installed as previous Android 12.
But now, I am unable to keep browsing for 5 minutes.
I have tried Chrome(stable, Beta, Development), Microsoft Edge. I have also cleared App cache, rebooted the phone, used Beta WebView and Google Play service...
All won't help.
It seems that doing a factory reset is a only possible approach. But this takes too long, and downgrading actually did erase user data.
Any comments would be greatly apappreciated
Add: Firefox works well. But every several minutes there is a small window appears and disappears at once without being fully noticed.

When you say
bush911 said:
downgrading actually did erase user data.
Click to expand...
Click to collapse
How exactly did you downgrade, and if it's not obvious by the explanation of the method you chose, how exactly did it erase user data?

roirraW edor ehT said:
When you say
How exactly did you downgrade, and if it's not obvious by the explanation of the method you chose, how exactly did it erase user data?
Click to expand...
Click to collapse
I just: fastboot --force update imagexxxzz.zip
Then: fastboot reboot
The phone tried booting into OS, failed.
A user interface similar to fastboot showed up, said something like data is bad, I must choose to erase data etc.
Then I used volume key to choose power key to confirm
Finally, everything is just as always

bush911 said:
Hi all,
Now I can't browser, I wrote this post via Pixel 3.
Just in one day time, I updated my Pixel 6 to Android 13, then forced downgrading to Android 12.
Now I almost have the same settings and Apps installed as previous Android 12.
But now, I am unable to keep browsing for 5 minutes.
I have tried Chrome(stable, Beta, Development), Microsoft Edge. I have also cleared App cache, rebooted the phone, used Beta WebView and Google Play service...
All won't help.
It seems that doing a factory reset is a only possible approach. But this takes too long, and downgrading actually did erase user data.
Any comments would be greatly appreciated
Click to expand...
Click to collapse
I've had bad Trichrome libraries before, and there wasn't much resolution other than just waiting for an update to fix it, but these were always with the Dev versions.
If everything from stable to dev versions are crashing then there isn't much I can give other than two things.
Try going in and removing the beta and dev versions of Chrome/Edge/WebView, then go and uninstall updates for the stable WebView, disable it, then reenable it. Apparently that was something that had to be done back in the beta for Android 12. Might need to reboot.
If that still doesn't fix it then a factory reset might be in order.

It seems that web related apps will automatically close themselves within minutes, even if the App is launched and leave it alone.
Sometimes on the launcher, a very small window appears and disappears at once without being noticed.
I took two logcat files, hope someone can help figure it out. Both files were obtained while Chrome was running and stopped recording logs as soon as the Chrome closed itself.
Thank you for your attention
logcat_08-19-2022_14-14-02.txt
drive.google.com
logcat_08-19-2022_14-11-11.txt
drive.google.com

I thought downgrading is impossible cause of the changed bootloader

sille said:
I thought downgrading is impossible cause of the changed bootloader
Click to expand...
Click to collapse
Downgrading the bootloader is impossible. You can still downgrade the rest of Android, and Android 12 boots just fine on the Android 13 bootloader (so far - this could easily change with a future Android 13 update).

bush911 said:
It seems that web related apps will automatically close themselves within minutes, even if the App is launched and leave it alone.
Sometimes on the launcher, a very small window appears and disappears at once without being noticed.
I took two logcat files, hope someone can help figure it out. Both files were obtained while Chrome was running and stopped recording logs as soon as the Chrome closed itself.
Thank you for your attention
logcat_08-19-2022_14-14-02.txt
drive.google.com
logcat_08-19-2022_14-11-11.txt
drive.google.com
Click to expand...
Click to collapse
Chrome is dying during compositing, and the appears to maybe be relating to graphics drivers or DRM/WideVine. Try checking DRM Info to see if WideVine is very broken. For graphics drivers try running 3DMark to see if the Vulkan or OpenGL driver are busted.
I also noticed you have XLua and LSPosed, have you tried disabling all of your Magisk modules to see if one of them might be causing the issue?
You might have to do a wipe or even flash the factory image again. If DRM Info or 3DMark show issues or things are still crashing after disabling modules then I would wipe, not install any applications, and see if Chrome is still crashing. If it still is then a flash would be in order.

@bush911
Sorry to tell you but you won't be able to run Android 12 on the Android 13 bootloader. It appears to work fine, and for the most part it does, however the DRM APEX module crashes whenever any application tries to use a method from it. Even if the application isn't actively trying to verify or display DRM laden material it will still crash, which is what happens to WebView as it checks if the ClearPlay or WideVine are working sometime after start, and DRM Info doesn't even make it to a splash screen.
You're going to have to update back to Android 13.

Does this have anything to do with the Tiktok keyloggers and other malware found through Android webview and built-in browser for Tiktok on iOS? EDIT: It is a java script injection method.. nevermind.

rester555 said:
Does this have anything to do with the Tiktok keyloggers and other malware found through Android webview and built-in browser for Tiktok on iOS?
Click to expand...
Click to collapse
No.

Namelesswonder said:
@bush911
Sorry to tell you but you won't be able to run Android 12 on the Android 13 bootloader. It appears to work fine, and for the most part it does, however the DRM APEX module crashes whenever any application tries to use a method from it. Even if the application isn't actively trying to verify or display DRM laden material it will still crash, which is what happens to WebView as it checks if the ClearPlay or WideVine are working sometime after start, and DRM Info doesn't even make it to a splash screen.
You're going to have to update back to Android 13.
Click to expand...
Click to collapse
Thank you very much for the detailed analysis, this is really a bad news, I have to live with it for a while as I found Firefox works for now.

bush911 said:
Thank you very much for the detailed analysis, this is really a bad news, I have to live with it for a while as I found Firefox works for now.
Click to expand...
Click to collapse
Good luck, as other apps that try to verify DRM enforced material will also suffer crashes. I didn't test the YouTube app but it should crash also, along with any streaming app in the world, and VLC will most likely suffer the same fate, and music apps too depending on whether they support DRM.

Namelesswonder said:
Good luck, as other apps that try to verify DRM enforced material will also suffer crashes. I didn't test the YouTube app but it should crash also, along with any streaming app in the world, and VLC will most likely suffer the same fate, and music apps too depending on whether they support DRM.
Click to expand...
Click to collapse
I don't know much about these technical terms
But I found it seems that most web related Apps are suffering this, such as, webpage launched from Google feeds etc.
I seldom use YouTube, just watched 5 minutes, by now it was good

Namelesswonder said:
Good luck, as other apps that try to verify DRM enforced material will also suffer crashes. I didn't test the YouTube app but it should crash also, along with any streaming app in the world, and VLC will most likely suffer the same fate, and music apps too depending on whether they support DRM.
Click to expand...
Click to collapse
is there any way to disable DRM? would that help?
i dont support it anyways and would prefer it turned off

I can actually account for a couple things here.
The first time I downgraded to 12 I actually didn't have any problem with chrome, no crashing.
Then several days later I saw this thread and downgraded again and chrome did indeed crash often. But oddly enough I watched YouTube for several hours without issue, just my experience.