Database Develop

[Q] Ambient display failure

It worked when I first booted up. After a few hours it quit. I did a factory reset, and the same thing happened. I then went through my running apps and turned them off until none were running except the system apps. Still didn't work.
Anyone else have this happen that can suggest a fix? If I have to reset and install apps one by one, how do I do that, since on signing into Google the apps auto load

gmermel said:
It worked when I first booted up. After a few hours it quit. I did a factory reset, and the same thing happened. I then went through my running apps and turned them off until none were running except the system apps. Still didn't work.
Anyone else have this happen that can suggest a fix? If I have to reset and install apps one by one, how do I do that, since on signing into Google the apps auto load
Click to expand...
Click to collapse
To fix auto load, you can change the system setting to not backup apps; it's in Settings > Backup & reset. I thought upon initial Google account sign in you could switch that setting off too, and that prevents the apps from auto-installing. I have backup turned off because on previous devices and versions of Android it was contributing to battery drain.

laur3n.newm4n said:
To fix auto load, you can change the system setting to not backup apps; it's in Settings > Backup & reset. I thought upon initial Google account sign in you could switch that setting off too, and that prevents the apps from auto-installing. I have backup turned off because on previous devices and versions of Android it was contributing to battery drain.
Click to expand...
Click to collapse
I did what you suggested, adding single apps and confirming the ambient function worked. Found an app that seemed to be the cause, and upon uninstalling it the ambient function came on line. However, about a half hour later, it stopped working again. Spent over an hour on the phone with Moto, and they figured out that ambient doesn't respond unless the phone has been asleep more than 10 seconds. That seemed to work for me. So I did my 4th reset/install of the day, and again, it worked for a while, even with all my apps (including the one that seemed to be the cause in the first place). And then, it stopped again.
I searched, and one suggestion was that ambient won't work unless you have a locked screen. I usually don't use a lock, but what the hey, I'll try it. Set up a pattern unlock and (wait for it.........).
Nope.
I'm stumped.......

Mine seems to stop displaying the ambient as well. It will display a few times initially and then stops. I don't know if it extends its sleep period after every interval or not. Also seems like if you lift up your phone to look at your ambient notifications, that disables any repeat display too

Changes to Device Administrator keeps crashing settings

I know there's got to be some setting turned on that is preventing me from toggling the apps in Device Administrator because whenever I go to it, I can see the full list, and when I attempt to toggle one of them on or off, settings crashes and locks the phone. I have two apps that have been toggled on, so somehow I was given the ability to do it before this hard to find setting was turned on preventing me from toggling any more apps....
Any suggestions on what I'm doing wrong? Thanks!

KryptosXLayer2 said:
I know there's got to be some setting turned on that is preventing me from toggling the apps in Device Administrator because whenever I go to it, I can see the full list, and when I attempt to toggle one of them on or off, settings crashes and locks the phone. I have two apps that have been toggled on, so somehow I was given the ability to do it before this hard to find setting was turned on preventing me from toggling any more apps....
Any suggestions on what I'm doing wrong? Thanks!
Click to expand...
Click to collapse
I was getting the exact same issue on my S8+ yesterday. Do you perhaps have the latest/beta version of Call Recorder by SKVALEX installed? With my issue at least, I think it was down to that app, well a conflict between the two versions I had on the phone. May have been coincidence and could have been unrelated of course but removing both (old and beta) then just installing the latest beta sorted the issue, or t least the issue went away at the same time...

chippyuk said:
I was getting the exact same issue on my S8+ yesterday. Do you perhaps have the latest/beta version of Call Recorder by SKVALEX installed? With my issue at least, I think it was down to that app, well a conflict between the two versions I had on the phone. May have been coincidence and could have been unrelated of course but removing both (old and beta) then just installing the latest beta sorted the issue, or t least the issue went away at the same time...
Click to expand...
Click to collapse
Not, I don't have that app nor do I think this is AN app preventing me from adjusting Device Administrator toggles

I Had the same problem in my note 7, only thing I could do was a reset all app settings, that solved the issue

S Pen Unlock menu bug.

Hello,
So I noticed this issue and the local live chat support failed to help me and the only thing suggested was a factory reset.
The Unlock with S Pen Remote" option on the Note 9 is a bit buggy. First, whenever it's on, your phone can be unlocked bypassing every security you've set up.
Having this issue since the day I own it and it's not fixed via the November update. Also it's not related to the Google's Smart Lock.
The second thing about this is the menu which can't seem to be able to save the chosen option. Here is a video of what I am talking about.
https://imgur.com/a/jT82AF9
For long time I was looking for a way to disable it and after one reboot I finally did it and now I cannot turn it back on. Apparently there is almost invisible "OK" button
Trying to figure out if anyone is having the same issues.

Frozen screen after waking up screen

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?

Question Face recognition/unlock stopped to work after last update

Hello! After the last update that I've received a couple of days ago (current OS version: 31.1010.0410.61) I can't unlock my phone using the camera, I need always to use the fingerprint. I've tried to re-setup the face recognition but nothing, I can't unlock the phone using the camera. Any idea how to fix it? I've noticed also that before during the unlock there was the green camera icon on top right, now there is just a green dot. I don't know if it can be relevant.
Any suggestion is appreciated.
Thanks!

Try to - delete your face from phone. Then in apps find Asus Face Unlock Service - force stop, then clear internal memory. Restart phone - register face and boom - works like charm, at least for now. You can also clear cache files system-wide and reboot your device.

Thanks for the suggestion but at the end I've solved in another way. When I went to "Security & Lock screen" section to remove the face recognition. I've noticed that there was a "Google Play system update" pending.
I've launched it and it fixed it

Good to know. But it may be temporary fix. I reported this bug of Asus official forum and - one of mods reply that they fix this in next FOTA. This must be something more serious.

The problem came back, after about a day later. Now everything is updated but the unlock doesn't work anymore. I wanted to try your method, but I don't find any "Asus Face Unlock Service" app. In the meanwhile I'll hope in a fix in the next FOTA

herod2k said:
The problem came back, after about a day later. Now everything is updated but the unlock doesn't work anymore. I wanted to try your method, but I don't find any "Asus Face Unlock Service" app. In the meanwhile I'll hope in a fix in the next FOTA
Click to expand...
Click to collapse
When you enter all apps menu press three dots and select show system apps. Then you find Asus face app.
Edit.
For me this solution is working for a out 2 days. After app crashes and you need repeat whole process.

I've just noticed that if you restart the phone it also "fixes" the problem, but I suppose that it won't last long. I really hope that they fix it asap