So I updated my Google Play services to 8.1 but I had package disabler (which is now turned off) running on my phone which problem is the culprit. But after updating my phone started heating up, freezing constantly and giving all kinds of google play update errors.
I thought, great I will just uninstall the update and everything will be fixed. Well uninstall and force stop are both greyed out. So I went to the device admin and turned off Android Device Manager but, it just turns right back on and greys out if I restart my phone it goes back to normal but then when I try to disable it does the same thing. I have tried with Android Device Manager both installed and uninstalled same issues.
So I can't disable Android Device Manager, I can't uninstall Google Play Services update... anyone have any ideas short of factory reset?
Thanks in advance...
I've been running Lineage 13 for 6 months, but the phone mysteriously got into a boot loop yesterday, so I had clear the local data and re-install the apps from the Playstore
However I found that every time I installed the nRFToolbox app (by Nordic Semiconductors) (Who are a reputable company), that when the App installed, it crashed a load of internal OS services e.g. PlayServices and all sorts of Google services.
If I rebooted the phone it appeared to work OK, but if I went into the "Apps" in Settings, the phone hung again, and I had to reboot it.
I tried updating to the latest unofficial Lineage 13, but that didnt help, so I've now installed the official Lineage 14, and this seems to have solved the problem.
But I don't quite see how a single app can kill so many core services, and I prefer to stay on Android 6 (Lineage 13), because of XPosed and specifically XPrivacy.
(BTW. I know XPosed is now supposed to work on Android 7, but I didnt think XPrivacy will every get ported to work with the updated version of Xposed - at least according to the developer)
Does anyone have any insight into why this app can hang the phone
I don't know, why this APP makes your phone crash, but i had similar problems when installing greenifys latest app and two days ago, i updated some apps ending in bootloops.... I am using unofficial Lineage 13 with xposed and xprivacy too
I run stock OS but have this same issue when updating any big and heavy apps such as Snapchat, Google app and FB Messenger for the past 6 months at least. The app starts to update but then will crash in the installing phase often giving an error such as "503 can't be updated", at which point multiple Google services will crash endlessly the only way to stop the crash is hold down power to force the phone to reboot.
I have reset the phone several times but after setting up the phone and updating all the apps the first update to one of those apps the issue happens again (the app always installs from scratch ok it's only it's updates that cause it)
A sort of fix I have been using (because it doesn't 100% always work) is when you see an update for the app you know will cause the crash first update all the other apps manually leaving only the problem app, then close all apps go to Settings > Storage & USB > Internal storage and clear the Cached data, then power cycle the phone, let the phone boot and complete all it's background tasks it does after booting, then open Play Store and click Update on the offending app then put the phone down and leave it until the app either updates or causes the crashes. If this doesn't work then waiting 24 hours and doing the same steps seems to work.
I am certain it comes from either an app update (probably from Play services or the Play Store app) or maybe from having the phone encrypted which does make the phone run slower especially over time. (May or may not be related but I've noticed on my phone if I factory reset it then after setting it up and updating all the apps I try to encrypt the phone the phone will 'break' and will boot loop forcing a reset from the boot loader, however if I set up the phone, don't update any apps then encrypt it completes successfully, all the apps will then update ok and the phone then functions as you would expect)
All in all this issue is incredibly frustrating!
Just got this phone days ago and flashed fresh new .205 firmware, then configed the phone and installed apps on it.
Everything appears fine, but suddenly all auto-start apps stop auto-starting after phone boots, until I unlock my phone manually, then finally they can start in the background.
What could cause this to happen? My other phone, Xperia XZP with exact same apps and settings works fine with no problem.
Update: app-start turns normal after disabling PIN. But how? Why? Can I turn it on again?
Update: apps stopped auto-starting again after fingerprint(PIN) is enabled. Really need some help here. Smart lock also appears broken, it just shows a blank screen in its settings page.
Update 2:
OK now I know it's caused by a feature called "FBE" and I have to do a factory reset to get rid of it. So damn great. I hate these companies.
At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Tritonio_GR said:
At some point after upgrading to Android 9 I started having the following issue where if the screen turns off due to inactivity and I turn it back on by pressing the power button, I see whatever screen I had open before it went to sleep but it's frozen. Scrolling touching etc still perform (invisible) actions but the screen is frozen until I either press the app switch button or perform some action that would change the current application. While the screen is frozen the drawer from the top works just fine. Also when the app that gets frozen is the desktop (I'm using the default launcher), I can see the background scrolling if I swipe left or right but the widgets don't change, they are frozen.
Does anyone else have the same problem? Any ideas what could be causing it?
Click to expand...
Click to collapse
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Tritonio_GR said:
FWIW I have not really solved the problem but I am circumventing it by having the screen lock immediately instead of waiting 5 minutes. That way I have to unlock with a fingerprint every time the screen is off, and unlocking refreshes the screen which "fixes" the problem.
Click to expand...
Click to collapse
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset or software repair with Xperia Companion
Use Xperia Transfer to back up your calls/contacts/texts before you reset the phone
Didgesteve said:
There were lot of reports of glitchy phones after the Pie update.
The cure was a factory reset
Click to expand...
Click to collapse
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
thegrobi said:
Can you please link a thread, where users told, that problem is solved after reset?
I have the same frozen display (since Android Pie), when turning display off and on again.
Don´t wish to reset and install all again, if that does not help.
bye,
Ralf
Click to expand...
Click to collapse
Hi Ralf,
the phone will always work better with a reset after a major update, all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
here, is one example, or another, but I didn't jump to Pie because of all the negative feedback and the scores of people trying to downgrade.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Thanks for the links.
Didgesteve said:
all the Oreo applications are trying to work under Pie. Sometimes it works, sometimes it doesn't. Oreo apps aren't made to work under Pie and they can error.
Click to expand...
Click to collapse
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
A reset will fix your problem and if you use Xperia transfer then the amount of personal information lost will be minimal.
Click to expand...
Click to collapse
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
thegrobi said:
Thanks for the links.
This sounds to me, the combination of "old" Navi-apps with Pie is the problem. May be only with Pie on some Sonys.
I'm afraid, a reset will not change the frozen display.
All other apps till now do not freeze after display-on except MagicEarth and Osmand+
This 2 apps i deinstalled (+ deleting the data) and installed again.
Xperia transfer shows me only 2 apps for backup.
I'll probably try a reset in the next few days anyway.
bye,
Ralf
Click to expand...
Click to collapse
Looks like there is know issue with the Osmand+, the date of the post is may last year, but it may just be a 'feature'
When backing up with Xperia transfer, make sure you select all the boxes that are optional. It's things like text messages/contacts/phone history that are useful after a reset. Some apps can't be moved and have to be downloaded directly from the playstore, but Google should give you that option, after you log back in to the wiped phone.
Edit: I can recomend Sygic, free maps for one country, works without data.
In the meantime, I found more users with this problem and a little solution that another user describes:
I can confirm I have the exact same issue since Android 9 with my Xperia xz1 compact.
I normally have no lockscreen options set. So when I wakeup the Phone, it sometimes kind of 'locks' the screen. Widgets do not respond, I cannot switch home screens. The time on the status bar remains correct. If I then click on an app and go back, everythning behaves normally.
So I'm quite sure this must be a software issue, as other people have this problem to.
My workaround for now is to have a lockscreen option aktive. But I would rather have not, for conveniance.
I tested this also with safe mode and complete factory reset of the phone. The 'bug' is still there.
Click to expand...
Click to collapse
If I disable lockscreen, then apps stop when it is switched on again. However, I always have to enter pin or use fingerprint sensor, or smart lock.
This often does not work when cycling and is dangerous when cardriving.
On Android 8, the lockscreen did not need to be active.
So the problem is not Osmand and MagicEarth.
It is a Sony 9 bug with Android 9.
bye,
Ralf
Found in an other forum an easy method to reproduce the problem.
disable the screen lock (it must be set to "None");
lock the phone and then unlock it;
lock and unlock it again.
Click to expand...
Click to collapse
bye,
Ralf
---------- Post added at 01:50 PM ---------- Previous post was at 01:20 PM ----------
Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf
[/COLOR]Because I believe that Sony will not fix the error, I could imagine a solution:
An app (possibly tasker), which puts a selectable running app from foreground while pressing the power button in the background and immediately brings it back to the foreground.
Does anyone know such a tool?
bye,
Ralf[/QUOTE]
So, did you ever find a solution?
I have a Nokia 7 Plus, running Pie, unrooted. Generally a great phone, had the charging port fixed by Nokia a few years ago.
But every now and then the screen locks up, I can usually get control back by locking the screen and waiting a moment and unlocking.
I've factory wiped my phone a few times, I've removed of my apps but today it's been terrible and seeks to be locking up more than ever.
I put it into safe mode and used chrome, with Bluetooth and wifi and had no issues at all.
Any ideas how I can diagnose and fix the issue?
benji1304 said:
I have a Nokia 7 Plus, running Pie, unrooted. Generally a great phone, had the charging port fixed by Nokia a few years ago.
But every now and then the screen locks up, I can usually get control back by locking the screen and waiting a moment and unlocking.
I've factory wiped my phone a few times, I've removed of my apps but today it's been terrible and seeks to be locking up more than ever.
I put it into safe mode and used chrome, with Bluetooth and wifi and had no issues at all.
Any ideas how I can diagnose and fix the issue?
Click to expand...
Click to collapse
Any suggestions how to potentially fix this?
Maybe worth to try the following:
1) clear system UI cache
2) Android system force stop
3) reboot
and /or
1) activate developer settings
2) under -> debugging -> Game-Driver Settings activate "prerelease-driver* for all Apps. It will survive re-starts
3) enter recovery mode and perform the graphics test
4) reboot
This is working for me since 29 May 2021. To be confirmed....
chrhei said:
Maybe worth to try the following:
1) clear system UI cache
2) Android system force stop
3) reboot
and /or
1) activate developer settings
2) under -> debugging -> Game-Driver Settings activate "prerelease-driver* for all Apps. It will survive re-starts
3) enter recovery mode and perform the graphics test
4) reboot
This is working for me since 29 May 2021. To be confirmed....
Click to expand...
Click to collapse
Thanks @chrhei
Unfortunately the issue still persists with the first option.
I'll try the 2nd one - what does the Game Driver setting do?
benji1304 said:
Thanks @chrhei
Unfortunately the issue still persists with the first option.
I'll try the 2nd one - what does the Game Driver setting do?
Click to expand...
Click to collapse
To be honest: I've no idea what it does, but it's still working for me.
Sorry to all
After 5 days of usage it happened again.
Conclusion: No fix.
Sorry for being to optimistic.