Hey,
i have some problems with my device (Exynos)
Bixby and Google Assistant stopped working.
I can ask bixby to turn on flashlight, but as soon as i ask something like the weather it just crash.
Google Assistant stopped working completly, i can open it, but it just dissapear und closes.
Further i can use apps like tiktok, but when i switch to another app and back, it hangs and just crash.
if i press restart phone, it shuts down but wont boot until i hold power
other things seem to be working fine
i havent changed anything.
As ive got a lot of apps and data i want to make sure i try everything before i reset my phone (and want to make sure the problem wont persist after reset)
thanks
I think it's because of a wrong update of Android System WebView, so probably you won't be able to solve the problem by resetting your phone
Fronnie said:
I think it's because of a wrong update of Android System WebView, so probably you won't be able to solve the problem by resetting your phone
Click to expand...
Click to collapse
Damn, you seem to be right.
i just deactivated it and except tiktok everything started to respond again (buts not working as i blocked webview haha)
so what i have to do now? no solution but waiting for a new version?
Yep, you have to wait for a new version. Where I live they just released wath seems to be a fix update
Fronnie said:
Yep, you have to wait for a new version, where I live they just released wath seems to be a fix update
Click to expand...
Click to collapse
i hope im getting it.
i uninstalled all updates for webview via settings.
now everything is working.
big thanks, i were really close to resett everything
Related
I have been seeing these bunch of errors (screenshots) at every re-start for the past couple of days. I am running Viper Rom version 2.5.
I tried to run the GPE rom as well but i get the same errors on that rom as well. Not sure what the issue is but nothing is broken apart from the weather app/widget not able to find the current location. It just shows 'current location' instead of the actual location. But this does not affect the Maps at all, it pin points my exact location on the Map.
Can anybody help with this?
Sounds like a dirty flash, did you do a factory reset? A factory reset should fix that.
Misledz said:
Sounds like a dirty flash, did you do a factory reset? A factory reset should fix that.
Click to expand...
Click to collapse
Yes i did a reset and clean flash. Still has the same issues.
I'm having the same issue on viper 2.5. Never had problems before. I even followed steps to convert play store from user to system app and downgraded play services to the latest 5 version, in which everything works well, cleared data/cache/defaults, uninstalled and reinstalled market. But every time I reboot it updates to version 6 and the problems begin. I even used disable services app to prevent it from updating, but still happens. Any help would be appreciated. (Forgot to mention that all apps work well but with constant error pop-ups)
Glad you wrote this. Been having same problem a UK rom debranded m8. I get the same errors restart but google play is popping up saying there's been a problem followed by a goggle services popup. I narrowed it down to either news and weather app or me just getting a new car and syncing with it. Filling in a zip code made the errors less. Still annoying as hell. Either latest google play update borked things or news and weather is causing a big fluke like it has several times in the past.
I just bumped my lollipop rom and install xposed then I noticed that my phone shows out "android is upgrading" on every reboot. Is there any way to fix this as it is a little annoying...:crying:
Sorry for my broken English
+1 !
afaik its just a side effect of using the alpha build of xposed. sure, it can get annoying, but having xposed and this 'issue' is better than, well you know.
kp_q said:
afaik its just a side effect of using the alpha build of xposed. sure, it can get annoying, but having xposed and this 'issue' and better than, well you know.
Click to expand...
Click to collapse
This activity tends to get lengthier after every reboot. I've found that once it "seems" to loop in the "Android is upgrading" screen, to remove the battery, boot into recovery, wipe the Dalvik cache, and reboot. It will go through the lengthy procedure of updating software, but will boot a WHOLE lot faster after that.
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
abbey666 said:
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
Click to expand...
Click to collapse
I tried this method but it didn't work, and there are still 3 apps that are being "optimized" on every boot. Is there any way to find out which apps these are?
alqoshi4life said:
I tried this method but it didn't work, and there are still 3 apps that are being "optimized" on every boot. Is there any way to find out which apps these are?
Click to expand...
Click to collapse
Try to change the version of Xposed installer and see if that fixes the problem. By the way, the problem is 100% fixed now on my phone. I used lucky patcher to remove all odex files. I also installed another version of Xposed. The latest one did not work well so used an older version.
abbey666 said:
Try to change the version of Xposed installer and see if that fixes the problem. By the way, the problem is 100% fixed now on my phone. I used lucky patcher to remove all odex files. I also installed another version of Xposed. The latest one did not work well so used an older version.
Click to expand...
Click to collapse
Which Xposed version did you use? I'm on v68 right now which is the latest. I had v67 and it did the same thing.
V66. I tried2 later versions but this one worked for me.
I have a Oneplus One but I have the same issue. Every damn boot. Android is starting. optimizing app 1 of 121.
I also have the latest version of xposed.
I know not the forum for the OPO but just thought I'd let you guys know other phones face it too and hopefully find a solution to this.
I had to make a really important call and my phone restarted all on its own. That's bad enough but add to the random restart sitting for 5 minutes to wait for android to finish optimizing
abbey666 said:
V66. I tried2 later versions but this one worked for me.
Click to expand...
Click to collapse
I tried v66 like you recommended and the same thing happened. So it must be something else that solved your problem. I guess I can live with it though.
have the same problem with my g3.. everybody have data backup ? )
BlackGodRaven said:
have the same problem with my g3.. everybody have data backup ? )
Click to expand...
Click to collapse
Try the newest Xposed framework v69. Solved my problem completely after a dalvik cache wipe.
alqoshi4life said:
Try the newest Xposed framework v69. Solved my problem completely after a dalvik cache wipe.
Click to expand...
Click to collapse
l solved it too ) l transfer backup to sd card )
abbey666 said:
There is a fix to that. I have the same problem that started after installing xposed on my s4 lollipop. I was able to get rid of the "androidis upgrading". the one that shows you how many apps are being installed. Now, it goes straight to "starting apps". This is not a complete fix though, since it should boot straight up but at least, it's a lot faster now. Use lucky patcher then use the option "remove all odex". That fixed the issue for me. Though not 100% fixed.
Click to expand...
Click to collapse
Trying this now...my G3 crashes for whatever reason from time to time after my Tasker that disables bluetooth as soon as the USB power is disconnected from the car.
Currently on version 79. Patched it with Lucky Pater and removed all odex; rebooted (got stuck but battery out & booted normally).
I'll report if there are any further issues
Okay it's very odd it seems like there's an issue with my LG G3 disconnecting bluetooth from the stock head unit in '13 WRX. If I try pushing the power button off on the radio then shut off the engine (Tasker shuts down bluetooth) then I don't seem to have this issue with the phone crashing. I've yet to have the phone crash if it's on A/C power and Tasker performs the same function.
I dont know if this is specifically a Razer issue, that's what I'm here trying to find out
Yesterday my play store automatically updated To 12.9.12
And now every time I go to search it force closes.
Full disclosure I'm rooted with magisk and I have xposed. ROM is stock 8.1 build opm1.171019.011-rzr-180803.6033
As a part of troubleshooting I did actually try to uninstall xposed but the issue still remained.
If I go to settings and disable (uninstall updates) and reenable and Clear data it works...but shortly after it reupdates itself.
There's options to disable apps from Auto updates but not the play store. There's guides to stop it from Auto updating with service disabler but it's missing options in the guides and also doesn't work.
I'm here trying to find out if
A. anyone else is experiencing the same issue.
B. If anyone has found a solution
C. If there's no solution does anyone know how to stop the play store auto updates on 8.1 razer
Any help appreciated
Thanks!:fingers-crossed:
Still no replies just wanted a slight update
I installed a log app so you guys can see whats happens when it crashes... No idea if this helps... Id also like to add I found out the version doesn't matter it starts working when I clear data and stops shortly after so I suppose stopping the update is pointless, its just what i thought originally was the solution but then I relized it crashes on the old version too... So yea the only thing that stops crashing is clear data but its only a temp fix for minutes until crashing returns anyway heres my log
Alright guys... I guess i was wrong it was xposed... I originally didn't fully uninstall it when testing my issue is solved now... Its apperently a known xposed for oreo issue
Anyway problem solved
Sucks because i really really like xposed but oh well what can you do ill just have to be patient and wait for them to work out the beta bugs.
majicmazo said:
Alright guys... I guess i was wrong it was xposed... I originally didn't fully uninstall it when testing my issue is solved now... Its apperently a known xposed for oreo issue
Anyway problem solved
Sucks because i really really like xposed but oh well what can you do ill just have to be patient and wait for them to work out the beta bugs.
Click to expand...
Click to collapse
I don't think it will ever get past beta or get another update. The last release was in January and now Pie is here soon and I think that will be the end of Xposed.
I received the latest AT&T update a week or so ago containing the 2.5 One UI update. After the update, I am experiencing some really strange issues with a variety of Google services.
1) Google Play Store updates are stalling. Most apps will download to a high percentage of completion (98% for example) and then just stall. If I leave the phone sit for a long time, eventually the updates will finish. This happens with every single app update or new download. I have 100GB free on the phone and it occurs on multiple networks (WIFI and AT&T).
2) GMail attachments won't download. They also stall at 0%.
3) I don't receive any incoming text messages when Google Messages Chat is enabled. Turning off chat and switching to SMS works though several texts say they failed to send and I have to retry (and they always end up going through). WIFI Calling is enabled.
4) Notifications from multiple apps are returning after I swipe them away. (Notification reminders is turned off in accessibility settings).
I did the usual - cleared cache in Google Play Store, Google Play Services, Google Services Framework, Download Manager. I cleared the cache after booting to recovery. When none of that fixed it, I completely reset my phone to factory conditions. Everything worked fine for 2 days and then today, all of the problems came back.
Everything else about the phone is normal as usual. I can't figure this one out and don't know what else to troubleshoot.
Try clearing the system cache on the boot menu.
blackhawk said:
Try clearing the system cache on the boot menu.
Click to expand...
Click to collapse
Is that the same thing as clearing the cache after booting to recovery? (Volume up and power button)
jkcarp94 said:
Is that the same thing as clearing the cache after booting to recovery? (Volume up and power button)
Click to expand...
Click to collapse
That's it. Can work like voodoo on lots of gremlins.
If that doesn't get it try clearing data on the Google apps. Might have to take it back to the stone age but probably not.
Reboot afterwards if you do. Playstore is a pain.
If the OS hasn't been reloaded since Q was flashed consider reloading to get a snappy clean load.
My 3rd OS load is the best.
Although I'm still running Pie, it's fast and very stable... lol, I like dinosaurs. I don't update a lot as it usually causes more problems than it solves.
I had cleared the cache from recovery before I factory reset and it didn't fix it. However, I just tried it again on the new rebuild and this time I cleared the cache 5 times in a row and then rebooted. It appears to have fixed all of the problems. I wonder if it was a bad app update to Google Play Services after the restoration to factory conditions?
jkcarp94 said:
I had cleared the cache from recovery before I factory reset and it didn't fix it. However, I just tried it again on the new rebuild and this time I cleared the cache 5 times in a row and then rebooted. It appears to have fixed all of the problems. I wonder if it was a bad app update to Google Play Services after the restoration to factory conditions?
Click to expand...
Click to collapse
Sometimes you're better off staying on the factory load versions. I never let auto updates run.
I keep Playstore disabled unless I want to use it or check for updates because of this and it also is a resource pig.
Manually doing it makes spotting the trouble maker easier.
I also keep backup copies of known good updates for system apks so that the factory load isn't my only recourse if a apk been updated more than once. APK Export is a great freeware app for doing this. Backup all your Playstore apps too for faster and easier reloads. Plus if Playstore discontinues the app, you still have it. Been boned by Playstore* once too often.
*sometimes the software goes greedy, gets sold or there's a licensing issue. Either way once it's gone having a known good copy makes life so much easier.
Hello,
The same thing is happening to me but for several months now. I am in Spain with Movistar. The only way I could get them to update the Google Play APPs was to switch my mobile to "safe mode" and from there it really works.
I'm going to try a factory reset, to see how it went.
Foguet said:
Hello,
The same thing is happening to me but for several months now. I am in Spain with Movistar. The only way I could get them to update the Google Play APPs was to switch my mobile to "safe mode" and from there it really works.
I'm going to try a factory reset, to see how it went.
Click to expand...
Click to collapse
A reload probably won't help. It will very likely reoccur.
It sounds like a 3rd* party apk is the culprit.
Find the root cause and correct it.
It may be just a setting issue in a 3rd party apk.
*they include carrier, Samsung and misc others you installed.
Hi all,
I've tried to update my chrome application (the pre-installed on my Global Poco F3 which is under MIUI Global 12.02 stable global) I have tried multiple times to update the Chrome app from the Google Play Store with no success to this day.
I've investigated using adb logcat and I've seen a specific error trigger itself :
4-10 00:34:14.008 17140 17170 E Finsky : [993] tvh.apply(44): IQ::GROUP_INSTALL: Error validating group. Rejecting requests: [com.google.android.trichromelibrary, com.android.chrome]
04-10 00:34:14.008 17140 17170 E Finsky : com.google.android.finsky.installqueue.impl.preprocessor.GroupInstallValidator$InvalidGroupException: GROUP_INSTALL: Group com.google.android.trichromelibrary and com.google.android.trichromelibrary have overlapping module [com.google.android.trichromelibrary, com.android.chrome]
Obfuscated long Java backtrace...
Click to expand...
Click to collapse
I have tried to update chrome on a Redmi Note 8 pro without success as well. However, under LOS (Lineage OS 18.1) another phone has successfully updated the Chrome app, meaning this issue is probably not due to a weird Google Play Store bug but most likely due to MIUI 12.
Anyone has encountered this issue ? And is there any way we could work around this ? (instead of waiting for a potential fix in MIUI 12.5)
Thanks for any help on this matter, I can provide the whole backtrace if anyone want to see it but I doubt it would help anyway since she looks pretty obfuscated to me (the only thing I could understand was some execute function being called but all the classes names have been randomized and most functions call names too).
Hi! This is usually a problem for those who have set up the system for the first time. I also encountered this, after a while Google Chrome was updated on its own. The same applies to the Android System WebView application. Wait for a while and the app will update.
UPD: Or you can download right now from apkmirror.com, if you want
Xoby said:
Hi! This is usually a problem for those who have set up the system for the first time. I also encountered this, after a while Google Chrome was updated on its own. The same applies to the Android System WebView application. Wait for a while and the app will update.
Click to expand...
Click to collapse
But my Redmi Note 8 Pro isn't brand new, but I still encounter an issue to upgrade Chrome at least, I'm not too sure how long should I be waiting ? (like 6 months or just even a few weeks I guess ?)
AkechiShiro said:
But my Redmi Note 8 Pro isn't brand new, but I still encounter an issue to upgrade Chrome at least, I'm not too sure how long should I be waiting ? (like 6 months or just even a few weeks I guess ?)
Click to expand...
Click to collapse
Okay, try log out from your Google account, then clear data & cache Google Play Services, Service Framework and Google play store too, then reboot and login again, but not sure about this method
I cannot understand the mistake. I updated Chrome to the latest version 3 days ago.
Xoby said:
Okay, try log out from your Google account, then clear data & cache Google Play Services, Service Framework and Google play store too, then reboot and login again, but not sure about this method
Click to expand...
Click to collapse
You were correct, I had unfinished the device configuration (the first time you have to connect your Google account etc.) hence it didn't work to update Chrome and Android Web View, I just finished it right now and Chrome did successfully update. That's weird I think Android should change (if this issue is at the Android level).
In the end I didn't need to do all this logging out, clearing data & cache and so on, just finishing the device configuration solved the issue.
AkechiShiro said:
You were correct, I had unfinished the device configuration (the first time you have to connect your Google account etc.) hence it didn't work to update Chrome and Android Web View, I just finished it right now and Chrome did successfully update. That's weird I think Android should change (if this issue is at the Android level).
In the end I didn't need to do all this logging out, clearing data & cache and so on, just finishing the device configuration solved the issue.
Click to expand...
Click to collapse
Hey mate, what did you exactly did for solve this?
I'm facing the same problem for update my chrome and web view.
Fabio Bertelli said:
Hey mate, what did you exactly did for solve this?
I'm facing the same problem for update my chrome and web view.
Click to expand...
Click to collapse
I had a somewhat permanent notification that said something along the lines of "Finish configuration of your device" I clicked on it and then I pressed next and tweaked the last options, once that notification was cleared, all the Google Apps kinda of updated themselves somehow (I saw some of them even reinstalled themselves that was a bit weird but everything went fine afterwards).
AkechiShiro said:
I had a somewhat permanent notification that said something along the lines of "Finish configuration of your device" I clicked on it and then I pressed next and tweaked the last options, once that notification was cleared, all the Google Apps kinda of updated themselves somehow (I saw some of them even reinstalled themselves that was a bit weird but everything went fine afterwards).
Click to expand...
Click to collapse
Thank you for your help.
Unfortunately I didn't have this message to "Finish configuration". So, I followed a tutorial on internet and erase all Google play store and Google Play services data.
After that rebooted the phone and put my information again on Play Store and than the update starts working for it self.
Fabio Bertelli said:
Thank you for your help.
Unfortunately I didn't have this message to "Finish configuration". So, I followed a tutorial on internet and erase all Google play store and Google Play services data.
After that rebooted the phone and put my information again on Play Store and than the update starts working for it self.
Click to expand...
Click to collapse
Good thing you figure it out, and also thanks for explaining how for others who will face this issue, maybe sometimes the notification disappears for some reason or the configuration doesn't finish successfully and this issue happens.