Related
Hi everyone,
I'm new here, nice to meet you all. Last night I finally bought the LG G3, switched from an iPhone 5S.
Right away I flashed the phone to Lollipop that I found in this thread: http://forum.xda-developers.com/lg-g3/general/kdz-poland-lollipop-lg-g3-20a00-t2938255
And the phone really works flawlessly except for one weird (and pretty annoying) bug.
When I'm surfing using Chrome or the generic browser that comes with the phone, after visiting a few websites (music forums, basketball websites, etc., nothing out of the ordinary that I usually visit), for some reason the browser gets redirected to an app called "Porn Factory" and wants me to download it to my phone.
Now, I'm pretty sure this isn't normal behaviour. And I've read that people have experienced a similar issue with their phones, but I still haven't found a solution to stop this from happening.
I tried a fresh install of Chrome, deleted all data/cache and it still happens from time to time. My phone isn't loaded with a lot of apps, just a few social media apps basically as it's brand new. Also tried scanning it with a few of the anti-virus apps on Google Play and nothing.
So yeah, if anybody could give a tip or two on how to solve this I would be very greatful. This is my last resort. :-\
Other than this, I'm really enjoying the G3!
p.s. I do apologize if the thread isn't in the right section, I'm new here.
Try to do factory reset (wipe data)
Next time use G3 Q&A, Help & Troubleshooting forum as it belongs to this section.
sounds like it is trying to tell you something
but seriously it doesn't sound like anyone else has that issue (or they think it's a good thing, who knows)
could it be an SD card issue?
Can you boot into safe mode by pressing+holding the reboot button?
So the only thing I can do is a complete factory reset? How certain are you guys this could work? I mean I could do it, but I just want to try everything else before wiping everything and starting again from scratch.
Really appreciate the help guys!
Are you signed into chrome?
Bert.C said:
Are you signed into chrome?
Click to expand...
Click to collapse
Yeah, I logged in with my google account the first time I launched it. I could clear all settings and re-install the app and not sign in when I launch it for the first time. If that's a viable solution?
The thing is this is also happening on the stock browser which came with the phone and I'm not signed into anything on there.
* Try other browsers.
*Try some free antivirus solution.
* Is this happening on the same connection (WiFI / Data)? Maybe it's something in the network / dns proxy, etc.
* Check your internet settings (ip, dns, etc.)
What you have there is either mallware or some other type of bad "virus". This can't be considered a but by a long shot.
kraven001 said:
* Try other browsers.
*Try some free antivirus solution.
* Is this happening on the same connection (WiFI / Data)? Maybe it's something in the network / dns proxy, etc.
* Check your internet settings (ip, dns, etc.)
What you have there is either mallware or some other type of bad "virus". This can't be considered a but by a long shot.
Click to expand...
Click to collapse
Same thing is happening on my home Wifi, my friend's house wifi and my cellular data. On Chrome and the stock browser.
Well I've done a factory reset a few moments ago, will see if anything changes.
My best guess is either some bad configuration (with a mallware dns or whatever) or some mallware that does that intercepting / redirect. Bugs are crashes, things not working etc not porn redirection , that's what mallware does.
kraven001 said:
My best guess is either some bad configuration (with a mallware dns or whatever) or some mallware that does that intercepting / redirect. Bugs are crashes, things not working etc not porn redirection , that's what mallware does.
Click to expand...
Click to collapse
I get what you're saying, but how is it possible the phone got infected out of the box? I basically used it for a couple of hours before this started happening. Didn't surf any "bad" websites and installed only a couple of social apps.
there are lots of "ways" these get pushed and lots of crappy ads that you press and install things or reconfigure things that you wouldn't know. I don't know, I would start analyzing the apps looking at what's going on ...
don't want to be the devil's advocate but maybe one of your friends played a practical joke on you ... don't know these things tend to happen ...
kraven001 said:
there are lots of "ways" these get pushed and lots of crappy ads that you press and install things or reconfigure things that you wouldn't know. I don't know, I would start analyzing the apps looking at what's going on ...
don't want to be the devil's advocate but maybe one of your friends played a practical joke on you ... don't know these things tend to happen ...
Click to expand...
Click to collapse
Nobody has touched the phone except me since I got it.... and just finished the factory reset thing and set up a totally new device, opened chrome, surfed a few pages and it happens again.
This makes no sense.
try this: https://play.google.com/store/apps/details?id=com.bitdefender.antivirus
don't know, out of ideas really
One thing you guys may not have considered also, is that the guy you got the kdz from might have tampered with it and put adware or malware into the file...
Now, I'm in no way saying he has (Everyone on here is very trustworthy), but from all the solutions that look to have failed in this thread, that could be the only option. You can always try a factory reset, as stated above and if it's just something on the ROM then it might fix it, but if it's in the KDZ itself, the only way to get rid of it would be to flash a different file.
iDefalt said:
One thing you guys may not have considered also, is that the guy you got the kdz from might have tampered with it and put adware or malware into the file...
Now, I'm in no way saying he has (Everyone on here is very trustworthy), but from all the solutions that look to have failed in this thread, that could be the only option. You can always try a factory reset, as stated above and if it's just something on the ROM then it might fix it, but if it's in the KDZ itself, the only way to get rid of it would be to flash a different file.
Click to expand...
Click to collapse
Is there another 5.0 Lollipop KDZ file except the one I used? (http://forum.xda-developers.com/lg-g3/general/kdz-poland-lollipop-lg-g3-20a00-t2938255)
At this point I'm willing to try everything as reseting the phone to factory settings also didn't help.
Id consider flashing the stock kdz again. But get it from here from someone known and start fresh.
Bert.C said:
Id consider flashing the stock kdz again. But get it from here from someone known and start fresh.
Click to expand...
Click to collapse
Could you please point me to the file I need to download? I'm new to all this and really don't have an idea which file I need. I have the D855 version of the phone.
Thank you!
See if this is the what you're looking for.
Or here?
Or here?
Its not a bug, just webpage redirecting. Some website does that, some on both desktop and mobile version, some just one of them. One of the web page i visit lg-phone-firmware.com is one of them. In mobile version it always redirect to ads.
Viable solution is to try desktop view. Else try browser that support adblock.
Well it appears I got rid of this problem. Downgraded to KitKat, rooted my device and installed a custom ROM that I found here.
Thanks for the help guys!
Sent from my LG-D855 using XDA Free mobile app
Hi all,
I know there are quite a few people with issues on the google app crashing and I thought it might be helpful to see if we could collate different people's experience here - what hardware (RK?), rom, version etc, in case there is a particular version that works.
I have a RK3066/stock rom configuration. In terms of the version I have tried:
So 3.3.12 didn't crash at all in my brief test . But can't voice dial, guess they changed how it works some point after that .
5.4.x can crash repeatedly, best case feels like every other time. It also does not pick up my navigate requests correctly.
4.9.22 crashes infrequently so far. Never repeatedly which is importantly , worst every other time,usual say every five attempts.
4.7.x similar to 4.9.22
4.5.x - crashed alot
4.1.x crashes every 2-3 attempts, but can voice dial with this version (and above).
There is a 5.12 beta I haven' tried.
APKs at http://www.apkmirror.com/apk/google-inc/google-search/
Finally, is there a way of logging the detail of a google app crash - to see if there is something specific causing it?
Cheers
Another option.. I played w/ it on my phone and it was pretty nice. It does rely on google voice search so who knows if it'll crash also.
http://www.xda-developers.com/how-to-get-voice-access-beta/
TT_Vert said:
Another option.. I played w/ it on my phone and it was pretty nice. It does rely on google voice search so who knows if it'll crash also.
http://www.xda-developers.com/how-to-get-voice-access-beta/
Click to expand...
Click to collapse
Minimum android version is lollipop
Well that sucks a big one. To be honest it started to annoy me today. Couldn't fund out how to quickly turn it off
I would prefer to dig into why it crashes rather them retry to replace it. We know Goggle Voice works well when it works we just need to keep it working.
Unfortunately I really don't know where to start with it. I wish I had a bench top unit so I didn't always need to be in my car.
Is anyone running a HU emulator?
hans109h said:
I would prefer to dig into why it crashes rather them retry to replace it. We know Goggle Voice works well when it works we just need to keep it working.
Unfortunately I really don't know where to start with it. I wish I had a bench top unit so I didn't always need to be in my car.
Is anyone running a HU emulator?
Click to expand...
Click to collapse
Yes I think this will get us furthest, if we can understand why it crashes, then maybe there is a work around. Is it to do with microphone readiness, data connection or some other launch/ROM issue????
Having a crash free google app voice search would turn this HU from good to virtually perfect for me!
Mr Bigglesworth said:
Yes I think this will get us furthest, if we can understand why it crashes, then maybe there is a work around. Is it to do with microphone readiness, data connection or some other launch/ROM issue????
Having a crash free google app voice search would turn this HU from good to virtually perfect for me!
Click to expand...
Click to collapse
On my device it crashed offer if radio was playing during while I initiated the search. But it crashed also when the radio was not playing.
p_mike83 said:
On my device it crashed offer if radio was playing during while I initiated the search. But it crashed also when the radio was not playing.
Click to expand...
Click to collapse
On my HU is crashing all the time. I'm using the latest ROM from Malay Master. I have tried different version(some are crashes often, some rarely), but until now I didn't find a solution/workaround to this problem.
Still investigating...
dj.martzian said:
On my HU is crashing all the time. I'm using the latest ROM from Malay Master. I have tried different version(some are crashes often, some rarely), but until now I didn't find a solution/workaround to this problem.
Still investigating...
Click to expand...
Click to collapse
So are you able to say which are more stable? And what hardware do you have?
Mr Bigglesworth said:
So are you able to say which are more stable? And what hardware do you have?
Click to expand...
Click to collapse
The most stable is version 4.9.22.19 from apkmirror.com
HU Technical Specs: RK3188, 1024x600
Here is the link with the product:
http://www.aliexpress.com/item/Quad...r-DVD-Player-For-FORD-MONDEO/32563024121.html
Best Regards,
D.
dj.martzian said:
The most stable is version 4.9.22.19 from apkmirror.com
HU Technical Specs: RK3188, 1024x600
Here is the link with the product:
http://www.aliexpress.com/item/Quad...r-DVD-Player-For-FORD-MONDEO/32563024121.html
Best Regards,
D.
Click to expand...
Click to collapse
Yes, I also thought that 4.9.22 is one of the most stable of those that I have tried and have proper functionality. I'm on RK3066 and stock ROM. Interesting that your RK3188 doesn't improve things markedly, I don't think it is a processing power issue.
I was thinking about this a little bit more, I remember trying 3.3.12 (or whatever is the stock one installed) and it was very stable, but can't voice dial on it; 4.1.x etc start to crash so I wonder if there is information out there about the main changes that happened between these versions and so what might be causing it. is it something that has greater dependency on a good wifi connection or something else or some kind of software module that's not meshing right with the HU?
I found this in an old thread http://forum.xda-developers.com/showpost.php?p=48854301&postcount=714
gpmg762 said:
Got Google Now working, sort of anyway. Here's how I did it.
install an old PrebulitGMSCore apk https://drive.google.com/file/d/0B2FRr4c4c1g8WVI2YWg3TFZ4MTg/edit?usp=sharing (Google Play Services).
install Velvet apk https://drive.google.com/file/d/0B2FRr4c4c1g8X2t2MzQ4MkMyd1U/edit?usp=sharing (Google Now).
this step probably not be needed as I was trying to install Google Home Launcher, install Google Home apk https://drive.google.com/file/d/0B2FRr4c4c1g8OU9odi1ZRzJ5cHM/edit?usp=sharing (Google Home Launcher).
launch Google Now, it will detect a new version, update it.
I can use Google Now to launch default Radio and Music app by "play music" and "play radio".
"play disc" not working for me, neither are "navigate home" and "navigate office", they just get normal search results.
Click to expand...
Click to collapse
Has anyone gone done the route of changing the PrebulitGMSCore apk but with a more functional Google Now etc?
I'm hesitant to dig into this until Malaysk's next update that will be out soon.
Hello all,
I made some good progress, although with one drawback.
Today I tried v3.6 (I think it was 3.6.16) from apkmirror. And tried it just under ten times with NO crashes. A record for my head unit!!
v3.6 does have calling functionality, and navigate works fine too.
The only drawback seems to be the play music function (I really only need these three functions as everything else I do is quite straightforward from steering wheel controls). It doesn't seem to bring up poweramp and play the music as later versions do....But maybe this is something can be resolved by settings, I need to investigate more when I am back in the car.
Please can others try this and contribute to the thread - I feel I am so close to having this up and running well!
I'm going to continue posting on this thread, although it does somewhat feel like I am talking to myself.
So in the car a couple more times today. Absolutely no crashes on this version of 3.6.16 (what did they change after that which made it no work so well on MTCB HU?). When online, call and navigation work brill, don't know why it refused to play ball on play music.
Messing around with some voice command apps, and still testing this, but this sorts out the play music, and play music and navigate commands work well when offline - but just cant seem to get call to recognise properly when offline - it would be the last missing link for me - think it might be something that can be customised to be fixed though - will update when I figure this last bit out!
I'll play with this soon also.
Dave
I'm swamped right now but I will try to test it later in the week.
Ok, that would be great - was in the car again this morning and seemed to work fine. If someone knows how to make this version work well with the play music command (i.e. find local music and load it in poweramp), that would be great!
The other reason why i went to 3.6 is that it offline voices is meant to work but it isn't. I am wondering if the gapps version needs to also be rolled back to an earlier version for offline voices to work.
Mr Bigglesworth said:
I'm going to continue posting on this thread, although it does somewhat feel like I am talking to myself.
Click to expand...
Click to collapse
Please continue to talk to yourself, i'm listening
I hope to give version 3.6.16 a try later today and I'll post my results here.
There are some things I need to figure out to make this HU (almost) perfect and a stable voice command/search certainly is one of them.
I loaded 3.6.16 today and so far no issues. Do you happen to have a chameleon or version history so we can try to bisect this?
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.
My Google Assistant suddenly stopped working. Whenever I tried to issue a command, it returns "Cannot reach Google at the moment.".
Tried in my old phone, there are no problems.
Tried restarting but the problem still persists.
Anyone experienced this? Any solution?
HI YOU HAVE MANY WAYS TO FIX THAT
1-TRY FORCE CLOSE GOOGLE ASSISTANCE AND CLEAR ALL DATA AND CACHE .
2-IF YOU ARE USING A DATA PACKAGE ,USE A VPN
IF THOSE METHODS DON'T WORK UNINSTALL APP AND REINSTALL IT
Thiviru Gunarathna said:
HI YOU HAVE MANY WAYS TO FIX THAT
1-TRY FORCE CLOSE GOOGLE ASSISTANCE AND CLEAR ALL DATA AND CACHE .
2-IF YOU ARE USING A DATA PACKAGE ,USE A VPN
IF THOSE METHODS DON'T WORK UNINSTALL APP AND REINSTALL IT
Click to expand...
Click to collapse
dont need to shout.
The problem is nomally related to internet not working, be it service, or vpn stalled
Thiviru Gunarathna said:
HI YOU HAVE MANY WAYS TO FIX THAT
1-TRY FORCE CLOSE GOOGLE ASSISTANCE AND CLEAR ALL DATA AND CACHE .
2-IF YOU ARE USING A DATA PACKAGE ,USE A VPN
IF THOSE METHODS DON'T WORK UNINSTALL APP AND REINSTALL IT
Click to expand...
Click to collapse
Tried, didn't work.
Same here, brand new Pixel 6. Go into Assistant settings, scroll all the way down to "Your Apps (manage how Assistant works with installed apps)." Click on the Chrome browser and make sure "let your assistant choose this browser" is checked on. THEN, in the same settings, go to whatever other browsers you have installed and UNCHECK those.
Apparently Assistant got confused by too many options. (it might work if you check another browser and uncheck Chrome, but I quit playing with it once it was working again.)
Sea21 said:
Same here, brand new Pixel 6. Go into Assistant settings, scroll all the way down to "Your Apps (manage how Assistant works with installed apps)." Click on the Chrome browser and make sure "let your assistant choose this browser" is checked on. THEN, in the same settings, go to whatever other browsers you have installed and UNCHECK those.
Apparently Assistant got confused by too many options. (it might work if you check another browser and uncheck Chrome, but I quit playing with it once it was working again.)
Click to expand...
Click to collapse
Did this one but didn't work. Also, I only have Chrome as browser so I guess this isn't the problem.
Thiviru Gunarathna said:
HI YOU HAVE MANY WAYS TO FIX THAT
1-TRY FORCE CLOSE GOOGLE ASSISTANCE AND CLEAR ALL DATA AND CACHE .
2-IF YOU ARE USING A DATA PACKAGE ,USE A VPN
IF THOSE METHODS DON'T WORK UNINSTALL APP AND REINSTALL IT
Click to expand...
Click to collapse
Tried uninstalling, rebooting and re-updating the Google app. The Assistant is working again but Continued Conversations doesn't work. There were also times after I did this, the problem returned.
I had the same problem yesterday and fixed it by doing the following:
Google app->settings->Google Assistant->Assistant Voice-> and switch Phone to full.
I also purchased universal safetynet fix 2.2 and now pass Safetynet. Did both in conjunction with each other so that combo should work if you are rooted with the correct Magisk Canary.
Starzboy77 said:
I had the same problem yesterday and fixed it by doing the following:
Google app->settings->Google Assistant->Assistant Voice-> and switch Phone to full.
I also purchased universal safetynet fix 2.2 and now pass Safetynet. Did both in conjunction with each other so that combo should work if you are rooted with the correct Magisk Canary.
Click to expand...
Click to collapse
Not rooted and already set to Full, Continued Conversations still doesn't work.
danw_oz said:
dont need to shout.
The problem is nomally related to internet not working, be it service, or vpn stalled
Click to expand...
Click to collapse
ok i forgot to off capital letteres
I have struggled with this recently. Here's what worked for me. I noticed that on cellular it worked, but on my WiFi it did not although it had in the past. The trick was to go into WiFi settings and tell it not to randomly change the Mac address (use Device MAC). I suppose that -- maybe only with some routers -- the changing MAC is upsetting the NAT translation and your phone is making an outbound connection but that's just a theory.
I had the same problem, had used adaway and blocked some dns requests, cleared these and Hey Google worked again. Cheers.
Usually, the only times I have trouble with the Assistant this way are when I get in my car, hook it up for Android Auto, and in my driveway, I'm kinda in range of my Wi-Fi but not very well. It doesn't usually take very long for my phone to switch to mobile data on its own in this situation (and it took my Samsung way longer), but once it establishes a reliable connection via mobile data, then it's fine.
Necro'd thread to post POSSIBLE FIX:
Go into Developer options and disable 'App Wi-Fi Multi/Broadcasting Filter'. I'd turned it on randomly and forgotten, and have been suffering ever since. Turning it back off allows the app to connect to the internet, despite your phone being locked until standby.
Going off to cross-post this elsewhere because I've searched SO many pages trying to find a fix, and nobody mentioned trying this.
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.