Related
Hi, I bought a Motorola Droid 4 (Verizon Wireless) on eBay and I just got it yesterday. I also upgraded the firmware to 98.72.18.XT894.Verizon.en.US. I'm not sure if the touch screen is bad because of the software update or because I bought a defective used Droid 4 from a dishonest seller. I didn't test the screen before updating to Jelly Bean.
My problem only occurs in the home screen and app drawer. There seems to be two types of swiping interfaces. One is like scrolling (the phone book, for example) and the other is the "bouncy" pages found in most launcher home screens and app drawers. When I scroll my phone book or navigate a webpage in Chrome, screen scrolls perfectly. However, when I slide left and right in the home screen (or drawer) it slides partially and snaps back to the original page. Most of the time I swipe to right but I move to the left screen instead of the right. This problem never happens with my Droid 3.
A temporary (but not permanent) solution is that I have to swipe right and pause for a millisecond while still pressing on the screen, and then I have to slide right one more time and release my finger.
I notice that the reason why the Droid 4 go left when I swipe right is because the Droid 4 is so sensitive that when I swipe an inch right but 1/8 of an inch left (at the very end) it registers the last movement so that the screen moves left. It is as if the phone ignores the majority of the gesture and only registers the last portion of the gesture. Don't be confused, the majority of the gesture is recognize by the phone because I see screen moving along with my finger but the phone only registers the last part as the "confirmation" to change screen. If I swipe really slowly following the steps from the temporary solution above, it works. But I never had to do this with the Droid 3 or G2 or Samsung Galaxy S 4G.
So does anyone notice this problem? Does anyone notice that their Droid 3 swipes accurately 100% of the time while their Jelly Bean Droid 4 often swipes inaccurately? Should I return my Droid 4? What is going on? Is there a permanent fix? Can someone please verify whether or not this is an isolated issue? In other words, the problem is a bad touch screen (which doesn't make sense to me because everything else works perfectly) or the firmware (which means everyone experiences the same issue).
Also can someone verify to me that their pinch to zoom does not work when they use the Dolphin Mini browser?
Go into your developer options and check pointer location just to get a better understanding of what's going on when trying to swipe... is the phone on charge when this occurs? The touch is vary erratic when on a non OEM charger... there may be some static interference going on... if you haven't I would FDR and clear cache partition from the recovery menu... test the home screen/drawer... test your touches with developer options... try safe mode... test the touches... only time I have noticed this is while on a charger not putting out the OEM 5.1v 850mA...
Sent from my DROID4 using xda app-developers app
dbreezy187 said:
Go into your developer options and check pointer location just to get a better understanding of what's going on when trying to swipe... is the phone on charge when this occurs? The touch is vary erratic when on a non OEM charger... there may be some static interference going on... if you haven't I would FDR and clear cache partition from the recovery menu... test the home screen/drawer... test your touches with developer options... try safe mode... test the touches... only time I have noticed this is while on a charger not putting out the OEM 5.1v 850mA...
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
(1) Developer options was the first thing I tried when I notice the problem. The lines and dots were as accurate as my finger placement and gesture.
(2) The phone was on charge and wasn't on charge. The problem occurred under both conditions.
(3) I was using an OEM charger purchased from Verizon Wireless.
(4) Static interference??? I get shocked a lot when I touch things, but the problem doesn't occur on my D3 when I touch it. IDK what static interference is or how to fix it.
(5) FDR? You mean factory data reset? clear cache? I don't want to resort to this. Won't I have to reinstall everything and re-do all of my settings? I did a hard reset before the update but not after it. And now I don't want to reset again without knowing the cause of the problem.
(6) Safe mode and test the touches? How do I do safe mode? Test the touches is a bit vague.
poetryrocksalot said:
(1) Developer options was the first thing I tried when I notice the problem. The lines and dots were as accurate as my finger placement and gesture.
(2) The phone was on charge and wasn't on charge. The problem occurred under both conditions.
(3) I was using an OEM charger purchased from Verizon Wireless.
(4) Static interference??? I get shocked a lot when I touch things, but the problem doesn't occur on my D3 when I touch it. IDK what static interference is or how to fix it.
(5) FDR? You mean factory data reset? clear cache? I don't want to resort to this. Won't I have to reinstall everything and re-do all of my settings? I did a hard reset before the update but not after it. And now I don't want to reset again without knowing the cause of the problem.
(6) Safe mode and test the touches? How do I do safe mode? Test the touches is a bit vague.
Click to expand...
Click to collapse
This phone has a captivate touchscreen... As the human body is also an electrical conductor, touching the surface of the screen results in a distortion of the screen's electrostatic field, measurable as a change in capacitance. This is how it responds to our touch I would think the d4 screen would be more sensitive then the d3 that's why I say static interference... safe mode by hold power when you get screen pop long press power off when you get screen pop press OK... once in safe mode see if it still does it... if it does then its not third party app interference... if it doesn't then FDR and add apps one by one to see which app is the issue... personally I would just FDR and wipe internal storage clear cache partition ( in the stock recovery there an option for that) and try with no SD card... if it still did it I would see if it did it with a stylus
Sent from my DROID4 using xda app-developers app
dbreezy187 said:
This phone has a captivate touchscreen... As the human body is also an electrical conductor, touching the surface of the screen results in a distortion of the screen's electrostatic field, measurable as a change in capacitance. This is how it responds to our touch I would think the d4 screen would be more sensitive then the d3 that's why I say static interference... safe mode by hold power when you get screen pop long press power off when you get screen pop press OK... once in safe mode see if it still does it... if it does then its not third party app interference... if it doesn't then FDR and add apps one by one to see which app is the issue... personally I would just FDR and wipe internal storage clear cache partition ( in the stock recovery there an option for that) and try with no SD card... if it still did it I would see if it did it with a stylus
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
I am having doubts about the FDR. After going to the Verizon Wireless store, I tested the Motorola Razr phones and they all had the same problem with the Droid 4. They all use Jelly Bean. I also tried scrolling with the Samsung Galaxy Note 2. The Note 2 (didn't check which firmware) was as fluid and accurate as the Droid 3.
Am I crazy or is everyone not able to notice the touch issues with the Droid 4?
its the static I tried to find the link for you with no luck... months back a guy had this issue also... I was going to suggest testing a VZW device if safe mode and FDR didn't work but that's what troubleshooting is...
dbreezy187 said:
its the static I tried to find the link for you with no luck... months back a guy had this issue also... I was going to suggest testing a VZW device if safe mode and FDR didn't work but that's what troubleshooting is...
Click to expand...
Click to collapse
I just tried Safe Mode, and scrolling seemed better. I don't have the scrolling/swiping issues as frequently after I uninstalled ADWLauncher EX.But then again, I never had that problem in the Droid 3, which I had the ADWLauncher EX installed on it. I still have the problem though. Whatever, I guess???
Droid 4 seems really to be very sensitive on touch. At the beginning I had the problem that when I tried to open a program from home screen (using Go Launcher Ex) I suddenly was on the next homescreen instead of having the programm opened. I was coming from Droid 1 and it took me 2 weeks to get used to it - but now after some month it happens just once a week to me.
tbv2005 said:
Droid 4 seems really to be very sensitive on touch. At the beginning I had the problem that when I tried to open a program from home screen (using Go Launcher Ex) I suddenly was on the next homescreen instead of having the programm opened. I was coming from Droid 1 and it took me 2 weeks to get used to it - but now after some month it happens just once a week to me.
Click to expand...
Click to collapse
I believe this touch issue that we are having is a design feature for the new Motorola Droid phones running JellyBean. I've gotten used to it but I think the D3 has a better touch screen.
I just want to update this very old thread to say that my Droid 4 no longer has that problem. I think it really was static that caused these issues. There hasn't been a single software update but over several months, the screen just got better.
As stated, screen will not go off via timeout or power button tap. Power button is recognized and will bring up shut down menu like normal.
Device is rooted (thanks DG) and had been running well for over a week. Defrosted all apps from tibu in case I got over zealous but no better. A factory reset has not cleared it up either. Hoping the oneclick from the root package will correct the issue, but thats not until I get home later this evening.
Has anyone experienced / recovered from this issue?
Smart stay is turned off
I've had noticeable lag like a few seconds and sometimes I wonder if it's going to shut off but it always does. Better set a dark lock screen wallpaper to conserve your battery
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I know this is kind of basic, but what is your setting here:
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
3496255310
papashex said:
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
Click to expand...
Click to collapse
I'm having the same problem, I rooted through vroot.... what do you mean one click fixed it little my incite would be helpful....
thank you
Mine just did this, scared the hell out of me It also didn't go into deep sleep before it started. (Not rooted).
Pulled the battery, waited 30 seconds, plugged it back in.... same thing. Waited a few minutes, seems to have sorted itself out.
Scary....
This is definitely a software bug and it is related to the Headphone detection bug that people are having too (it's actually the same bug causing both issues). This happens to me quite often after I restart my phone. It's kind of like the phone hangs during the startup process. I've also noticed that the wifi/bluetooth status that was present before restarting the phone (i.e. whether they on/off) doesn't get applied until the bug sorts itself out.
For me sometimes this works: open an app like Chrome and then hit the home button to get back to your launcher. This works 95% of the time for me. I'm wondering if it has something to do with not having Touchwiz set as the default launcher.
I'm experiencing this same problem. If I don't manually turn the screen off by tapping the power button, the screen will not timeout.
I'm using a stock, rooted, manually debloated 5.1 system image that has incorporated some audio mods. Every once in a while, I'll notice that after waking my phone up, I'll get a redraw. I'm using the stock launcher. Here's what I've tried to get rid of them:
1. Just about everything you can think of involving the Google App (clear data, clear cache, uninstall and reinstall, etc.)
2. Switching to the Google Now launcher and back again.
3. Booting into safe mode and back again.
4. Reverting to the rom that doesn't have the audio mods that I implemented (at least I think I implemented them. I'm not sure how or if I can tell the difference).
5. Clearing cache from recovery about a million times.
Has anyone run into this problem and solved it?
The same behavior occurs on the Moto Maxx with 5.0.2. I was really hoping that it would have been fixed in 5.1.x.
I just flashed 5.1 the other day (using CF's image). I do get frequent redraws of the home screen and icons. I just installed Nova launcher thinking it was an issue with GNL.
I am seeing this on my Turbo since going to the OTA 5.1. with Nova. I don't seem to see it with Action Launcher 3 on the Turbo though. I also see it on my Nexus 7 2013 with 5.1.1 with Nova. Again I don't seem to see it with Action Launcher 3 on the Nexus.
I've noticed that it happens less and less frequently the longer I've been running this rom. Maybe it's just an android thing.
I did notice one thing.... I have turned off the google search bar that shows at the top of each screen by default. However every time I unlock the screen, it flashes the Google search box momentarily, then it disappears.
Also during phone calls, sometimes the bottom right part of the screen will flicker
I turned off Moto Display and the issue is completely gone. But I'm so used to unlocking my phone without having to use the power button that I really want it back
It is a Moto Display issue for sure. I have been experimenting lately and have discovered if I use only swipe for locking that once in a while when unlocking the phone I will have to do the android unlock after the Moto Display unlock. If I use smart lock associated with my Moto 360 watch those same times I'd get the second unlock I get a home screen redraw instead.
So come on Motorola - fix the problem! It is not just the Turbo/Maxx that has the problem. It is the Moto X etc as well.
I just (excitedly) updated to Oreo, and now I am wishing I had not. I love the new features, but two really irritating issues presented themselves:
1) My screen is not tinted an awful color. It looks almost like my blue light filter is on (but it isn't - when I turn it on it gets HILARIOUSLY bad). Whites are not white. Adaptive mode is the worst, basic mode makes it tolerable but not good at all. My screen looked so much better before.
2) My always on display is wonky. It occasionally is so dim I cannot even see it. Sometimes it is fine, other time it's bad. No rhyme or reason to it (my lighting is the same so it's not adjusting to the environment).
Neither is these things were an issue before. Anyone else experiencing these things? Any idea how to fix either one?
Same issies
Horrible screen tint, opaque orange and the whites are awful. They work fine during initial bootup of the phone, then change. Contacted Verizon and Samsung, they are both aware and no fix as of yet to what the deal is. So do not update your note8, there's absolutely nothing exciting or great with the update. Waited 3+ months for this update, had it on my Z2 force and it was great, ABSOLUTELY blows on the note 8...
PsiPhiDan said:
I just (excitedly) updated to Oreo, and now I am wishing I had not. I love the new features, but two really irritating issues presented themselves:
1) My screen is not tinted an awful color. It looks almost like my blue light filter is on (but it isn't - when I turn it on it gets HILARIOUSLY bad). Whites are not white. Adaptive mode is the worst, basic mode makes it tolerable but not good at all. My screen looked so much better before.
2) My always on display is wonky. It occasionally is so dim I cannot even see it. Sometimes it is fine, other time it's bad. No rhyme or reason to it (my lighting is the same so it's not adjusting to the environment).
Neither is these things were an issue before. Anyone else experiencing these things? Any idea how to fix either one?
Click to expand...
Click to collapse
Try clearing the cache in recovery
You can do that by turning the phone off
Hold Volume Up+Power+Bixby and wait till the blue screen goes away
Navigate down with the volume keys and select Wipe Cache Partition with the power button.
Select Yes
Select Reboot System Now
If that doesn't help, I would either try a factory reset or flash Oreo with Odin.
I didn't do the OTA, but flashed the ROM with Odin instead and I have zero issues
Ripthulhu said:
Try clearing the cache in recovery
You can do that by turning the phone off
Hold Volume Up+Power+Bixby and wait till the blue screen goes away
Navigate down with the volume keys and select Wipe Cache Partition with the power button.
Select Yes
Select Reboot System Now
If that doesn't help, I would either try a factory reset or flash Oreo with Odin.
I didn't do the OTA, but flashed the ROM with Odin instead and I have zero issues
Click to expand...
Click to collapse
I did the OTA and also have zero issues. Agree with suggestion for factory reset...
Update
Did the wipe cache/partition and no luck.
Won't try the FDR option as that was never worked for any issues I've had in the past decsde. Always a waste of time and hassle. Unless that's a guaranteed fix by Samsung or Verizon I will wait for a software patch update or whatever else it is to fix this issue.
OP, did you have blue light filter enabled prior to Oreo update?
Furthermore, it seems to me like Samsung devices prefer having their original Android OS , meaning updates seems to make them not as true and stable as they originally were out of the box. Perhaps another little sly tactic for us users to upgrade hardware yearly.
Sent from my SM-N950U using Tapatalk
Limeybastard said:
OP, did you have blue light filter enabled prior to Oreo update?
Furthermore, it seems to me like Samsung devices prefer having their original Android OS , meaning updates seems to make them not as true and stable as they originally were out of the box. Perhaps another little sly tactic for us users to upgrade hardware yearly.
Click to expand...
Click to collapse
I had the blue light filter on before taking the Ota and don't have this issue. I turned it off just after the Ota and looks normal
MACHEK said:
I had the blue light filter on before taking the Ota and don't have this issue. I turned it off just after the Ota and looks normal
Click to expand...
Click to collapse
Yeah something definitely went wrong for OP during install. I would start fresh and reinstall or reset.
I haven't taken the update. But its a new Android version. I personally always factory reset before updating to a new Android base version. I've never had issues on any phone Samsung or not when clearing data first.
Sent from my SM-N950U using Tapatalk
autogeek said:
I haven't taken the update. But its a new Android version. I personally always factory reset before updating to a new Android base version. I've never had issues on any phone Samsung or not when clearing data first.
Click to expand...
Click to collapse
I also factory reset with ever major update and never had a problem.
The bluelight filter is off, turning it on makes it way worse. I've never had to do a FDR with any phone for an update for over a decade, but those phones were all Motorola. This is my first Samsung and it's definitely a problem with the software causing this orange effect on all the white portions of the screen. Samsung and Verizon both confirmed this has happened to several so hopefully there'll be a fix soon as this is most annoying.
reset here too. no more issues.
I've always factory reset before taking a major update.
Do you have any substratum themes installed? Substratum seems to be buggy for oreo. I disabled all the them and my lockscreen went back to normal color.
I've never used it downloaded any themes
Clearing Blue Light or Screen Tint issues with Oreo on Samsung S8
My friend had this issue on an S8 after Oreo. It started by dismissing a dialog box when launching Google Play Books then opening a book. The dialog was asking something about Blue Light mode. Dismissing apparently caused a default to Blue Light mode and Always Enable. But, we could not find a way to get back to those settings in Google Play Books. Using the system setting to turn off did not work and turning on made screen colors worse. So, we uninstalled the Google Play Books app, restarted phone. Still bad colors at this point. Next, we re-installed app. After opening app and then selecting a book the same dialog box appeared. We selected Settings this time and turned the slider to OFF for Blue Light mode. Now, the Blue Light mode is off for the app and the rest of the phone screens outside of the app. Everything seems like correct colors again.
Even if you do not use Google Play Books, maybe this process will unstick a setting for you.
I don't use or have never used Google play books. Never seen a prompt like that either
Ripthulhu said:
Try clearing the cache in recovery
You can do that by turning the phone off
Hold Volume Up+Power+Bixby and wait till the blue screen goes away
Navigate down with the volume keys and select Wipe Cache Partition with the power button.
Select Yes
Select Reboot System Now
If that doesn't help, I would either try a factory reset or flash Oreo with Odin.
I didn't do the OTA, but flashed the ROM with Odin instead and I have zero issues
Click to expand...
Click to collapse
It's funny, I actually factory reset because the cache wipe didn't work. All looked well. Then after the initial setup (with a beautiful white background), my home screen popped up, and the screen immediately got all tinted. Some setting must have restored with my account! So I factory reset AGAIN, didn't import my setting or apps, then redid everything on my phone from scratch. Now it's fine. What a pain!
RogerTheGeek said:
My friend had this issue on an S8 after Oreo. It started by dismissing a dialog box when launching Google Play Books then opening a book. The dialog was asking something about Blue Light mode. Dismissing apparently caused a default to Blue Light mode and Always Enable. But, we could not find a way to get back to those settings in Google Play Books. Using the system setting to turn off did not work and turning on made screen colors worse. So, we uninstalled the Google Play Books app, restarted phone. Still bad colors at this point. Next, we re-installed app. After opening app and then selecting a book the same dialog box appeared. We selected Settings this time and turned the slider to OFF for Blue Light mode. Now, the Blue Light mode is off for the app and the rest of the phone screens outside of the app. Everything seems like correct colors again.
Even if you do not use Google Play Books, maybe this process will unstick a setting for you.
Click to expand...
Click to collapse
I didn't get a blue light filter prompt when I opened google books.
RogerTheGeek said:
My friend had this issue on an S8 after Oreo. It started by dismissing a dialog box when launching Google Play Books then opening a book. The dialog was asking something about Blue Light mode. Dismissing apparently caused a default to Blue Light mode and Always Enable. But, we could not find a way to get back to those settings in Google Play Books. Using the system setting to turn off did not work and turning on made screen colors worse. So, we uninstalled the Google Play Books app, restarted phone. Still bad colors at this point. Next, we re-installed app. After opening app and then selecting a book the same dialog box appeared. We selected Settings this time and turned the slider to OFF for Blue Light mode. Now, the Blue Light mode is off for the app and the rest of the phone screens outside of the app. Everything seems like correct colors again.
Even if you do not use Google Play Books, maybe this process will unstick a setting for you.
Click to expand...
Click to collapse
Thanks for posting this!! I had the same problem and couldn't figure why. After reading this, I went into Google Play Books and simply turned the night light off, and problem solved! It seems the nightlight setting in Google Play Books gets stuck in Oreo and overlays everything.
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?