Pixel C freezing (not usable anymore) - Pixel C Q&A, Help & Troubleshooting

My Pixel c is freezing a lot.
From time to tome it is not waking up from sleep.
I tried multiple factory reset without any success.
Even without any 3rd party application, I have the problem.
I tried to clean the cache partition but when I reboot in recovery mode, I have a the little android robot opened and the message "no command found"
Everything was working fine till march 2018.
Can you help me?
Shall I install another ROM?
Thanks in advance

Ellian81 said:
My Pixel c is freezing a lot.
From time to tome it is not waking up from sleep.
I tried multiple factory reset without any success.
Even without any 3rd party application, I have the problem.
I tried to clean the cache partition but when I reboot in recovery mode, I have a the little android robot opened and the message "no command found"
Everything was working fine till march 2018.
Can you help me?
Shall I install another ROM?
Thanks in advance
Click to expand...
Click to collapse
I would suggest installing office LineageOS 15.1 (https://download.lineageos.org/dragon)
Along with the the opengapps package (https://github-production-release-a...esponse-content-type=application/octet-stream)
I noticed quite a big improvement in responsiveness my self and it felt smoother and better than stock 8.1.0 from google.

When in recovery mode where you see "no comand found" just press volume down and power in the same time and from there on you will see standard recovery, delete cache from there and reboot. Good luck

damjan006 said:
When in recovery mode where you see "no comand found" just press volume down and power in the same time and from there on you will see standard recovery, delete cache from there and reboot. Good luck
Click to expand...
Click to collapse
I managed to contact Google support
After some questions and tests, they decided to send me a new pixel c
I am writing from it right now
I have reinstalled most of my apps
I have no issue so far
The other pixel c will be sent for repair
Thanks a lot for your help.
We can close the thread.

Ellian81 said:
My Pixel c is freezing a lot.
From time to tome it is not waking up from sleep.
I tried multiple factory reset without any success.
Even without any 3rd party application, I have the problem.
I tried to clean the cache partition but when I reboot in recovery mode, I have a the little android robot opened and the message "no command found"
Everything was working fine till march 2018.
Can you help me?
Shall I install another ROM?
Thanks in advance
Click to expand...
Click to collapse
I have the same Issue, the hard ware in great by all mine's.
I think just the Update was trash, I realy hit update. just i was trust google to give us the best, not a any more.
I would try to make switch to rom and see, even if it not better that dose not make defferent I cant enjoy my pixel c anyway

How did you contact Google?
Ellian81 said:
I managed to contact Google support
After some questions and tests, they decided to send me a new pixel c
I am writing from it right now
I have reinstalled most of my apps
I have no issue so far
The other pixel c will be sent for repair
Thanks a lot for your help.
We can close the thread.
Click to expand...
Click to collapse
I've had the same problems with mine, how did you go about contacting Google?

Using the chat support.
The pixel c that I received in June is not working anymore as well.
The system is fine but the backlight stopped to work.
The warranty is finished since 2 weeks.
I bought a mediapad m5

Related

Problem with Play

I installed the rooted image (http://forum.xda-developers.com/showthread.php?t=2030282) on a Samsung Galaxy S3 Mini. All went well and everything works (including wifi/Internet access) EXCEPT - all downloads from Play now fail. The downloads start but never get anywhere. It's as though there's a problem negotiating the download, in that the progress bar remains the striped version, and the download icon in the notifications bar keeps disappearing & then coming back, as though Android is trying to make repeated attempts to start the download. I've tried deleting caches, uninstalling updates for Play, several different Google accounts (including a brand new one), factory resets & everything else I could find on the web. Nothing is working.
Help!
you have to go into recovery reinstall gapps wipe cache and fix permissions...seems like a pain but its the most effective way to get stuff done :good:
The Tech Ninja said:
you have to go into recovery reinstall gapps wipe cache and fix permissions...seems like a pain but its the most effective way to get stuff done :good:
Click to expand...
Click to collapse
That's great, thanks - but can you give me a clue as to how I do those things?
I've read that holding Vol-Up, Home & Power On enters recovery mode, but that refuses to work on this model. (Vol-Down, Home & Power gives Odin mode). As far as I know, there's no way to get into recovery mode by pressing buttons on the Mini. And I've already tried the normal factory reset...
BTW, I can get a root shell on the phone using adb - can I do any of this stuff that way?
worldinquisitor said:
BTW, I can get a root shell on the phone using adb - can I do any of this stuff that way?
Click to expand...
Click to collapse
Okay, forget about it. Seems Google Play will work fine - provided I VPN via a server in the US...
worldinquisitor said:
Okay, forget about it. Seems Google Play will work fine - provided I VPN via a server in the US...
Click to expand...
Click to collapse
Just stop the downloads in running services and check

Recent/open app list not showing

Hello, I am happy owner of 1+3 (coming from Xperia U) and I am very happy with this phone, no bugs at all except for this. Normally it works perfect but after maybe a day of usage without restarting phone, recent apps (or open apps) tab not showing any open apps but its definitely graphic bug only because all apps that I open again are normally loaded from memory. After restarting phone it works, even all opened apps before restart are showed. Oxygen OS 3.2.2. See screenshot before and after restart.
before reboot h ttp://i.imgur.com/KMOruMN.jpg
after reboot h ttp://i.imgur.com/hLkUn8S.png
Sorry for links, this is my first post...
I'm Also having this problem in 3.2.2. Already had it in 3.2.1.
Sent from my ONEPLUS A3003 using Tapatalk
Here are your options
1. Factory reset
2. Root it and remove unwanted apps
3. Flash another ROM. My suggestion is flash this STOCK BASED ROM..Which is perfect.
Also just had this for the first time yesterday on 3.2.2. Recent apps reappeared after reboot.
Same problem for me
I had the same problem since last upgrade to Oxygen 3.2.2 and fixed with only doing a reboot to recovery (you can do it from power off menu if you mark the option advanced reboot in developer options or if you start the phone holding down power+volume down button at the same time) and then reboot to system normally again and voilá the recent apps button worked again for me.
Hope it helps.
Un saludo.
Get in touch with OP support team
Guys, I have talked with OnePlus 3 support. They wanted to schedule a remote support session with me, but that involves flashing a new firmware, and as I do not feel like tinkering with my new phone I had to decline.
Is anyone experiencing this issue wanting to do some flashing to help the community? Just open a ticket with OP3 explaining the problem. They'll get in touch in no time.
Anyone?
Same problem for me on Oxygen 3.2.4. Only reboot helps!
Clear google app data
This is supposedly a google voice activation bug.
To fix it (atleast temporarily) clear the Google App's data from application settings, then the Recents window starts showing the apps
Awesome! That worked for me. (OnePlus X)

Android Auto Broken for me since Oreo! Problem persists across OOS and Custom Roms!

I am having major issues with android auto since Oreo
Essentially, what is happening is that the Android Auto app itself will work with two and only two apps. They are Google Maps and Google Play Music.
My problem is, none, and I truly do mean no other 3rd party apps will work with Android Auto.
I should also restate that this is a problem with the Android Auto app itself, so let's pretend no head unit or car is involved. This can be replicated on just the phone.
Here's the behavior:
-Open android auto
-Open any 3rd party app (Let's say IheartRadio)
Either one of two things happen next:
-Instantly get a screen that says "IHeartRadio Doesn't Seem to Be Working"
OR
-IHeartRadio starts like it should, and is able to play music for about 15 seconds, and then I get "Doesn't seem to be working" screen
-This happens for every 3rd party app, not just IHeart, but Plex, TuneIn, Radio Scanner, EVERYTHING except Google Play Music and Google Maps.
I should also state that Android Auto and 3rd party apps worked without a hitch, absolutely flawlessly in Nougat.
And, I've asked around the OP5t forums here and nobody is having the same problem.
-------
What I've tried so far (And hasn't worked)
-Re installing Android Auto
-Re installing every 3rd party app and re-trying
-Installing a custom ROM (Oreo) (Same exact behavior right after factory reset flashing new rom )
-Tried installing 3rd party apps from a non google play source
-Flashing OOS 8.0 Stable, as well as OB4 thru factory wipes
What I haven't tried:
-Re-locking the bootloader and flashing back to OOS nougat (Would this even help?)
I'm totally at wits end here, folks. I bought the OP5t to accompany my new car as my old phone couldn't handle android auto, this is one of the most imporatnt features to me.
Does anyone have any suggestions? Would flashing back to nougat and locking the bootloader like the phone was brand new help me? I've never seen such a problem that persists through clean flashes.
Thank you kindly everyone,
Hey!
I had this exact same problem.
I managed to solve this.
I am on OOS Open Beta 4.
Install latest:
Android Auto:
https://www.apkmirror.com/apk/google-inc/android-auto/
Android System Webview:
https://www.apkmirror.com/apk/google-inc/android-system-webview/
Google Maps:
https://www.apkmirror.com/apk/google-inc/maps/maps-9-74-0-release/
Google App:
https://www.apkmirror.com/apk/google-inc/google-search/google-search-7-23-24-release/
Google Play Services:
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-2-21-release/
After installing all the apps, reboot your phone.
Android auto should work smooth again!
Just FYI, the bootloader status (locked/unlocked) has nothing to do with this.
Nick502 said:
Hey!
Android auto should work smooth again!
Click to expand...
Click to collapse
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
captainstarbucs said:
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
Click to expand...
Click to collapse
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Nick502 said:
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Click to expand...
Click to collapse
Yes, I'm using the dash cable that came with the phone, but this problem is isolated within the android auto app. I don't need to connect it to the car to get the issues I'm having. Just launching the app on the phone itself and starting up a 3rd party app will trigger the "seems to not be working" screen.
If I connect it to the car, the same behavior happens. No issue with the connection to the car since I'm still able to use Maps and Play.
I'm considering flashing back to nougat to see if it works and OTA'ing til I get stable 8.0 and dirty flashing OB4 today.
UPDATE!!!
I got it working, and how I fixed it was a total PITA, but it works and I'm on OOS OB4.
Here's what I did:
1. Download the first available nougat OOS and flash it. Factory wipe from stock recovery. Once booted, install android auto and 3rd party apps. Test if it works, if so...
2. Sign in google account and update to 5.0.4 via OOS updater
3. Once rebooted into 5.0.4, take OB4 and stick it onto root, and reboot to recovery again
4. I dirty flashed OB4 over 5.0.4 and it seems to work fine!
I haven't tested this in my car yet, I will be on a long drive tomorrow and update results.
Waze on android auto
Waze is working parallel to google Maps without any problems. When you open navigate both programs are shown.
Damn I just noticed it. My maps work but I tried to open Google play music and got the same error.
That was the one thing that consistently worked for me. Which rom are you on?

Android Auto - Something went wrong. Google play services doesn't seem to be working

I have had a problem loading Android Auto (AA) on my LG G4. I have rooted with Steadfaster's UsU and installed his Lineage 15.1 rom, opengapps nano (Sept 30) and the phone is working great. Prior to rooting the phone AA worked fine with MM 6.0. After rooting the phone, when I open the AA app on the phone I get the error "Something went wrong. Google play services doesn't seem to be working right now". The error comes up immediately and then the app closes. I tried plugged into in the car as well (Pioneer AVIC 4200 deck), but the error stops the phone when opened.
I have been through Google's forums and there have been lots of posts about this error and no real solutions for me posted. I have also tried other "fixes" I have come across, including this one - https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832/. This method involves:
1. Download and install System App Remover from the Google Play Store.
2. Put your device in Airplane Mode in order to prevent auto upgrade of GPS.
3. Open System App Remover and select "System App" from the menu.
4. Find Google Play Services in the list. It should be marked "Should keep", which is a suggestion from the publisher. Select it and press "Uninstall". Ignore completion message.
5. Using Settings/Apps, verify that Google Play Services has reverted to the factory-supplied version. It should be <7. "Force Stop", "Uninstall Updates", and "Disable" buttons should no longer be grayed out.
7. Reboot device and toggle Airplane Mode off.
I followed these steps, but unfortunately stock seems to be the version that came with opengapps which is current.
I'm out of ideas with this problem and need some help. AA is a great app for me and really handy on long trips. I would like to get it running if at all possible.
Appreciate any help you can provide.
jjcdennis said:
I have had a problem loading Android Auto (AA) on my LG G4. I have rooted with Steadfaster's UsU and installed his Lineage 15.1 rom, opengapps nano (Sept 30) and the phone is working great. Prior to rooting the phone AA worked fine with MM 6.0. After rooting the phone, when I open the AA app on the phone I get the error "Something went wrong. Google play services doesn't seem to be working right now". The error comes up immediately and then the app closes. I tried plugged into in the car as well (Pioneer AVIC 4200 deck), but the error stops the phone when opened.
I have been through Google's forums and there have been lots of posts about this error and no real solutions for me posted. I have also tried other "fixes" I have come across, including this one - https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832/. This method involves:
1. Download and install System App Remover from the Google Play Store.
2. Put your device in Airplane Mode in order to prevent auto upgrade of GPS.
3. Open System App Remover and select "System App" from the menu.
4. Find Google Play Services in the list. It should be marked "Should keep", which is a suggestion from the publisher. Select it and press "Uninstall". Ignore completion message.
5. Using Settings/Apps, verify that Google Play Services has reverted to the factory-supplied version. It should be <7. "Force Stop", "Uninstall Updates", and "Disable" buttons should no longer be grayed out.
7. Reboot device and toggle Airplane Mode off.
I followed these steps, but unfortunately stock seems to be the version that came with opengapps which is current.
I'm out of ideas with this problem and need some help. AA is a great app for me and really handy on long trips. I would like to get it running if at all possible.
Appreciate any help you can provide.
Click to expand...
Click to collapse
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. I will capture a logcat and post.
Thanks
Click to expand...
Click to collapse
steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. It never opened without the error I titled this thread with.
My first attempt at a logcat. I searched in Notepad++ and used carservice as the keyword. Some errors were shown. I don't know how to interpret them and would appreciate your help
Thanks
Click to expand...
Click to collapse
jjcdennis said:
steadfasterX said:
Even when it sounds obvious but have you installed AA clean so without restoring data from a backup? Do you have tried to completely factory reset the phone? Do you have tried to format data in TWRP? Obviously you should have a backup of your internal storage when doing so .
You should also catch a logcat when starting the app
After rooting with UsU I followed sdembiske's recommendations for installing Lineage. This included a factory reset and formatting data with TWRP. I then installed Lineage 15.1 UsU and opengapps nano and then installed the apps I wanted. AA went on clean without restoring data. It never opened without the error I titled this thread with.
My first attempt at a logcat. I searched in Notepad++ and used carservice as the keyword. Some errors were shown. I don't know how to interpret them and would appreciate your help
Thanks
Click to expand...
Click to collapse
I just searched a bit regarding the errors of your logcat and found this:
https://productforums.google.com/forum/#!topic/nexus/-N8jJo7A8nI
maybe something there helps you out.
It seems definitively an issue with google play app/updates..
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
steadfasterX said:
jjcdennis said:
I just searched a bit regarding the errors of your logcat and found this:
https://productforums.google.com/forum/#!topic/nexus/-N8jJo7A8nI
maybe something there helps you out.
It seems definitively an issue with google play app/updates..
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
I have been through that forum and tried the last post just now - uninstall updates, clear cache, open AA - and I immediately get the error.
I'm thinking about doing a Titanium backup on apps and data (minus AA) then wipe, reinstall LOS 15.2, TWRP, Lineage SU, do a reboot, reinstall AA first and if it works then run Titanium restore for apps and data.
Make sense?
Click to expand...
Click to collapse
jjcdennis said:
steadfasterX said:
I have been through that forum and tried the last post just now - uninstall updates, clear cache, open AA - and I immediately get the error.
I'm thinking about doing a Titanium backup on apps and data (minus AA) then wipe, reinstall LOS 15.2, TWRP, Lineage SU, do a reboot, reinstall AA first and if it works then run Titanium restore for apps and data.
Make sense?
Click to expand...
Click to collapse
Sounds like a plan
Nevertheless I would to a titanium backup of play and AA BEFORE restoring as well..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
steadfasterX said:
jjcdennis said:
Sounds like a plan
Nevertheless I would to a titanium backup of play and AA BEFORE restoring as well..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Well I wiped cache, Dalvik, system and then formatted data, installed the 15.1 UsU rom, then installed Gapps, rebooted to recovery and installed the Lineage addonsu. I rebooted, went through setup and the first thing I did was open the Playstore install Android Auto and run it - immediate error again. Also the addonsu did not root the phone. And to top it all I did not disable the pin code.
Back to the drawing board.
Click to expand...
Click to collapse
steadfasterX said:
jjcdennis said:
btw: I have just installed AA here without an issue, running LOS 15.1 on my h815..
.
Click to expand...
Click to collapse
I have been beating the bushes and looking for a solution. None so far. You mention AA worked on your phone. Are you running LOS 15.1 and if no, which rom? Also re your install can you look in apps and notifications and see if the more options * is shown on the AA app. I have it, but when I select it nothing happens. My old Nexus 5 the * works and Android Auto opens no problem. LOS 7.1.2.
Thanks
Click to expand...
Click to collapse
jjcdennis said:
steadfasterX said:
I have been beating the bushes and looking for a solution. None so far. You mention AA worked on your phone. Are you running LOS 15.1 and if no, which rom? Also re your install can you look in apps and notifications and see if the more options * is shown on the AA app. I have it, but when I select it nothing happens. My old Nexus 5 the * works and Android Auto opens no problem. LOS 7.1.2.
Thanks
Click to expand...
Click to collapse
I run LOS 15.1 build 20181002 and at the time of installing that ROM version I used this opengapps version: open_gapps-arm64-8.1-nano-20180705.zip (download)
AA works here yes. I run it now for several days, daily, no issues here.
My version of AA is 3.7.584044 (attached: View attachment com.google.android.projection.gearhead-ffadc269cc39417e152ffcdd22183045.apk)
Not sure what you mean by "the more options *" but I've attached 2 screenshots of the app settings which may show what you meant.. if not show a pic of that setting.
oh you may meant the gear symbol at the top right? Here it opens fine but as that opens google stuff it makes sense that it fails on yours
.
Click to expand...
Click to collapse
Isn't mine basically the same as yours, other than H815? That gear icon will not open up the more options page. On my Nexus 5 with LOS 7.1.2 it opens a page with Settings for AA ie: Limit wifi, Connected cars, phone screen settings, etc.
If not the same maybe I should run your version of LOS.
jjcdennis said:
Isn't mine basically the same as yours, other than H815? That gear icon will not open up the more options page. On my Nexus 5 with LOS 7.1.2 it opens a page with Settings for AA ie: Limit wifi, Connected cars, phone screen settings, etc.
If not the same maybe I should run your version of LOS.
Click to expand...
Click to collapse
I've mentioned and linked the opengapps version, attached the AA version and mentioned the exact build for a reason yes.
The idea was that you try the exact same setup.
btw: which model do you have?
.-
steadfasterX said:
I've mentioned and linked the opengapps version, attached the AA version and mentioned the exact build for a reason yes.
The idea was that you try the exact same setup.
btw: which model do you have?
.-
Click to expand...
Click to collapse
H812 on the UsU Oreo build H812 build.
So I can copy what you have, other than I'm using the H812 versus the H815 LOS rom.
Thanks steadfasterX
steadfasterX, is it necessary that I format the data when I reload this rom. Takes a long time to restore everything.
jjcdennis said:
steadfasterX, is it necessary that I format the data when I reload this rom. Takes a long time to restore everything.
Click to expand...
Click to collapse
Use my latest preview version of TWRP then you can backup your data AND internal storage . you can first try without format. if you still have issues try to format it and if it doesn't fix anything you can restore by TWRP but ensure that you use build 144 or higher
Sent from my LG-H815 using XDA Labs
OK, thanks again. Will give it a go. I have your latest TWRP, 144_g4_0.
On the positive side after all kinds of failed troubleshooting my G4 has all of a sudden decided to connect with my PC. It shows as H812 in Explorer and in Device Manager as Lemobile Android Device with Android Composite ADB Device driver. A lot easier than using Cloud.
jjcdennis said:
OK, thanks again. Will give it a go. I have your latest TWRP, 144_g4_0.
On the positive side after all kinds of failed troubleshooting my G4 has all of a sudden decided to connect with my PC. It shows as H812 in Explorer and in Device Manager as Lemobile Android Device with Android Composite ADB Device driver. A lot easier than using Cloud.
Click to expand...
Click to collapse
Gave it a go, but as soon as I tapped on AA the error came up. I did format data to start from clean and used the older versions of AA and Google Play.
Update - I reinstalled all my apps via Titanium Pro (not AA) and set things up. I decided to tryy AA one more time before removing it and bingo it opened. Kinda waking on broken glass here and unsure whether or not the app will continue to function. Hooefully this fixed things.
Thanks again steadfasterX.

Strange Google services behavior after latest AT&T update

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.

Categories

Resources