This is an old problem, but the causes are so plenty it's a doozy. So here's yet ANOTHER cause of "can't click (Install)" button and its solution.
Any way, just updated to SlimKat. And no, I did NOT have official JB installed before, just official ICS, Safestrap, and had been running on CM10 ever since. But that's not the important issue.
Tried to reinstall some APKs, like Amazon store, some Xposed modules... Except none of them will let me click the INSTALL. And yes, 3rd party apps install is active, and I even turned off verify apps.
All of the previous advice I can find says look for screen filter or brightness apps or overlay buttons. I checked. Ain't got any that's active.
I was using PermissionDog to check anything that uses an overlay and uninstall them one by one, when something hit me (not literally). All of these are overlays of some sort. What overlay did I add recently? Then I looked at my screen, then slapped my forehead... hard.
I had enabled "battery bar" that comes with BatteryMix. This optional bar shows you a horizontal 2 px high bar on the very top that shows you your battery level. That is an overlay!
I turned that off, and voila, I can install APKs again. So let that be a lesson to you.
I've been rolling round the net for a few days now trying to solve this but no fully successful result.
It seems the stock launcher has this bug were if u have anything active in the accessibility services such as NoLED then tallback (TB) kicks in.
I tried the disable TB suggestion for NoLED but it always seems to start again. However I have stooped the voice by uninstalling it + the 2 TTS engines. However a hand is displayed in the notification bar (& it ignores my colour thyme) and an ongoing notification is displayed as well U can get rid of this but it reappears at reboot.
So I've tried the used a different launcher idea for NoLED, I think this worked (lots of launchers & playing going on) TB voice wise but I still get the hand
Also the splanner 'full screen' widget does not seem to work with other launchers I've had a look at a few other calendar widgets but they are not as good as they did not display any text only a marker for events unlike the splanner widget.
But even if I could find a good 'full screen' calendar widget I would still have the TB hand problem so I might as well stick with the stock launcher as I have figured out how to shut it up - But I don't want the hand!
I was thinking of trying [KERNEL][TW]Forest-HelloWorld-Make-II kernel for JB N7000 as v1.73 has BLN support but this is an old version and the new version does not support it. Also it looks like v1.73 does not have phils touchwiz recovery; which I currently have and don't wish to loose. Also the BLN in 1.73 is based on wakelock, so would this mean bad battery life?
I cannot ask about the kernel in it's thread yet, so can anybody comment.
Last night I found the LEDBlinker Lite app & that looked interesting but the way in which it works (which I have not looked at yet) means the back & menu buttons are permanently illuminated (this will be because I have them set to be on when the screen is on as I have 360 degree rotation enabled) and the activation icon for button savior is displayed. So this is no go due to battery consumption and screen burn.
Can anybody suggest a way out of this catch 22 hell, so I have some sort of message notification with the screen 'off', with no TB voice, no TB hand in notification, 'full screen' splanner widget or similar which displays text for events, does not cause the prob with button savior and the back/menu keys and has philz touch?
If a new launcher is needed it needs to support folders in the apps draw and ideally be free. I'm def not paying anything till I get it all working due to the catch 22 nature of this.
Any suggestions muchly appreciated as I've been messing around with this for days.
I'm using sweet rom v11.1 with a philz touch v5.
Thanks
Just got this phone yesterday and noticed that I can't do anything while receiving a call, there is an "always on top" screen that won't go away by pressing any of the buttons until you hang up. This is really annoying since it completely disables the phone. Let says you are driving using google maps and somebody calls you, you will miss your exit for sure, or you want to check a text while talking on the phone, not possible... Already tried to disable the phone notifications, as well as trying all the available options ( for notifications), also tried with other phone apps and with SystemUI Tuner app all with no success.
Is anybody else having this issue? I'm happy to provide any info you guys might need as well as do any test. Currently using Nova launcher,
Android version 9,
Security patch Jun 5 2019.
Software info WW_16.0622.1906.19_0
Extension ROM 1.1.93
Maybe because of Nova Launcher. It is actually kinda weird. What firmware is installed on your ROG Phone 2?
I'm also on WW_16.0622.1906.19_0 and when I'm in a call I can just go home or use recent apps while in a call, mine looks like this, note the green bar at the top of the Play store screenshot.
I also use Nova launcher.
D_Gabe said:
Maybe because of Nova Launcher. It is actually kinda weird. What firmware is installed on your ROG Phone 2?
Click to expand...
Click to collapse
I installed Nova Launcher trying to fix the issue, although the result was the same. The firmware is stock WW_16.0622.1906.19_0
willhemmens said:
I'm also on WW_16.0622.1906.19_0 and when I'm in a call I can just go home or use recent apps while in a call, mine looks like this, note the green bar at the top of the Play store screenshot.
I also use Nova launcher.
Click to expand...
Click to collapse
Nothing happens in mine when I press the home or recent apps while in the call screen, I can drag the top menu but that's about it, in this menu even if I press the little gear to go to settings it opens it in the background and once the call is over that will be the first screen that I can see. But somehow the call screen is always on top. On this phone I can't get the green bar, I'm used to it from all my other past android phones, but not on this one.
Any ideas?
dorianmtz said:
Nothing happens in mine when I press the home or recent apps while in the call screen, I can drag the top menu but that's about it, in this menu even if I press the little gear to go to settings it opens it in the background and once the call is over that will be the first screen that I can see. But somehow the call screen is always on top. On this phone I can't get the green bar, I'm used to it from all my other past android phones, but not on this one.
Any ideas?
Click to expand...
Click to collapse
Factory reset.
As seen here, this is the most annoying bug on the phone now...
https://www.reddit.com/r/GalaxyTab/comments/l3wnhr
This is for people on One UI 3.1 using third party launchers. You might come across a bug where:
1.The launcher keeps stopping/force closing or
2. Exiting an app causes the screen to flash and does nothing if you touch the screen immediately after.
Any fixes or workarounds?
I've had this issue with Nova Launcher and my S21 Ultra. Haven't found a permanent fix for it as yet.
thats weird I have had my s21 ultra since 5 pm yesterday, thats the first thing I did was download Nova, that's all i use, and have not had any issues with what you guys are having.
2003vstrom said:
thats weird I have had my s21 ultra since 5 pm yesterday, thats the first thing I did was download Nova, that's all i use, and have not had any issues with what you guys are having.
Click to expand...
Click to collapse
I believe we (AUS) owners are one firmware release behind (I'm on AUA4 with a build date of early Jan where the latest is AUAC with a build date later in Jan) so perhaps it's been fixed in the latest release?
If I use the Samsung gestures (swipe up from the bottom), Fluid Navigation gestures doesn't actually prevent those gestures from working for some reason (even after running the ADB command needed)
Devhux said:
If I use the Samsung gestures (swipe up from the bottom), Fluid Navigation gestures doesn't actually prevent those gestures from working for some reason (even after running the ADB command needed)
Click to expand...
Click to collapse
Yes these bugs are unacceptable
I have this issue as well where swiping up to go home causes the screen to flash and become unresponsive for a second or so. It only happens with gesture navigation and a 3rd party launcher.
I'm on the update release January the 1st. Is there a chance this is fixed in an update already available in part of the world?
Never mind I already have AUAC. that does not fix it. We may need to report this bug to Samsung. Has anyone done that? Chances are a fix is coming since they did fix the rest of the issues that were on earlier oneui versions for gestures in 3rd party launchers.
Did anyone confirm this happens in all 3rd party launchers and not just Nova?
2003vstrom said:
thats weird I have had my s21 ultra since 5 pm yesterday, thats the first thing I did was download Nova, that's all i use, and have not had any issues with what you guys are having.
Click to expand...
Click to collapse
Are you using gesture navigation? AFAIK it only affects the home gesture. Use Nova, launch an app. Swipe up from the bottom of the screen to go home and immediately after, try tapping an icon on the launcher screen to launch another app. You notice no unresponsive issue here?
TigerSoul925 said:
Are you using gesture navigation? AFAIK it only affects the home gesture. Use Nova, launch an app. Swipe up from the bottom of the screen to go home and immediately after, try tapping an icon on the launcher screen to launch another app. You notice no unresponsive issue here?
Click to expand...
Click to collapse
I'm on UAC since yesterday evening but this issue only happened when I first got the phone on Monday. I went into Nova settings and set it as default launcher. Since then no issues at all.
I Infact replicated the steps you just mentioned and was not able to reproduce the issue. Using the Samsung swipe up navigation gestures for clarification
twisted_mind said:
I'm on UAC since yesterday evening but this issue only happened when I first got the phone on Monday. I went into Nova settings and set it as default launcher. Since then no issues at all.
I Infact replicated the steps you just mentioned and was not able to reproduce the issue. Using the Samsung swipe up navigation gestures for clarification
Click to expand...
Click to collapse
That's interesting. Exynos version? I wonder what causes some of us (most?) to experience it but not you. I've set Nova as default in the system settings, not in Nova, but that should produce the same effect. Did you do anything else between the non working and the working state?
By Samsung swipe up, do you mean swipe up from the bottom in 3 different places rather than swiping screen left and right edges to go back? I use the version where you swipe left and right edges for back. Is that it perhaps?
TigerSoul925 said:
That's interesting. Exynos version? I wonder what causes some of us (most?) to experience it but not you. I've set Nova as default in the system settings, not in Nova, but that should produce the same effect. Did you do anything else between the non working and the working state?
By Samsung swipe up, do you mean swipe up from the bottom in 3 different places rather than swiping screen left and right edges to go back? I use the version where you swipe left and right edges for back. Is that it perhaps?
Click to expand...
Click to collapse
Yes exynos. India variant. And yes for your last question too. I prefer the swipe up gestures because using the side swipe with a case I couldn't get it to work reliably.
I'm sorry I couldn't find the setting for this in the settings menu so when I first experienced this issue I simply set nova as default through its own settings.
Also I had used smartswitch cable transfer to migrate all data apps and settings over from the S20+
twisted_mind said:
Yes exynos. India variant. And yes for your last question too. I prefer the swipe up gestures because using the side swipe with a case I couldn't get it to work reliably.
I'm sorry I couldn't find the setting for this in the settings menu so when I first experienced this issue I simply set nova as default through its own settings.
Also I had used smartswitch cable transfer to migrate all data apps and settings over from the S20+
Click to expand...
Click to collapse
Oh I saw just now that this is already stated in the top post. I couldn't see the quoted area on my mobile, now I see it. The bug is only present with google gestures and there's a hint on how to bypass the problem with one hand +, I'll try that now.
TigerSoul925 said:
Are you using gesture navigation? AFAIK it only affects the home gesture. Use Nova, launch an app. Swipe up from the bottom of the screen to go home and immediately after, try tapping an icon on the launcher screen to launch another app. You notice no unresponsive issue here?
Click to expand...
Click to collapse
yeah I`m old school and just use the buttons at the bottom, I don`t care for navigation gestures, that would explain why I don`t have the issues, lol
2003vstrom said:
yeah I`m old school and just use the buttons at the bottom, I don`t care for navigation gestures, that would explain why I don`t have the issues, lol
Click to expand...
Click to collapse
Yeah saw just now that it does not affect the Samsung style gestures.
Thanks for this thread, this was driving me crazy, i tried Action Launcher, Niagra, Smart Launcher and they all have the stutter when you return to then home screen when using android 11 gestures. Samsung gestures fixes but my muscle memory is to swipe from the sides for back so i'm struggling with it. Currently back to the One UI launcher to be able to use android gestures seamlessly. Hoping for a fix to this in future updates to OneUI but doubtful!
orbital247 said:
Thanks for this thread, this was driving me crazy, i tried Action Launcher, Niagra, Smart Launcher and they all have the stutter when you return to then home screen when using android 11 gestures. Samsung gestures fixes but my muscle memory is to swipe from the sides for back so i'm struggling with it. Currently back to the One UI launcher to be able to use android gestures seamlessly. Hoping for a fix to this in future updates to OneUI but doubtful!
Click to expand...
Click to collapse
Use one handed operations+ from play/galaxy store. I hated android 11 swipe from left to go back, because I'm used to open menu in many apps from the left side and now it was going back, with oho+ i have swipe back from right and normal left side without any commands, also that app is OP so you can customise it even more
Wrong alert, still not solving the gesture when you swipe from south to north (down to u
mankvl said:
Use one handed operations+ from play/galaxy store. I hated android 11 swipe from left to go back, because I'm used to open menu in many apps from the left side and now it was going back, with oho+ i have swipe back from right and normal left side without any commands, also that app is OP so you can customise it even more
Click to expand...
Click to collapse
Fantastic, this does the job perfectly, if you were here I'd hug you right now
Does not solve the gesture usage on the bottom.
I have a different issue wherein even tough I have set Nova as the default launcher, after a reboot, One UI launcher is set as default again. This doesn't happen all the time though but just random.
I don't know what happened, I was going to pair my smart watch (non-samsung) to my S21 Ultra but it wouldn't, so I rebooted the phone, and it rebooted with the One UI launcher instead of Nova Launcher, so I switched back to Nova, checked the default setting in Nova settings and it was still set to Nova as the default, when trying to leave the Nova settings, it again returned to One UI home, so I checked in settings for default apps, and Nova is still set to the default. So I tried force stopping One UI home, and return home, and again, it opens One UI home, it will not open Nova anymore.
I tried rebooting again, and oddly enough, Nova was the default launcher again. Figured it was just a glitch so I went on with my day and it just happened again but I haven't touched anything, it was on my desk all day untouched and when I picked it up, One UI launcher again.
Now, no matter how many times I reboot, it will always pick the One UI launcher, but the weird thing is when I'm in Nova, I can't swipe to go home because it's already on the default launcher, but when in an app, I swipe to go home and it goes to One UI home, and swiping to go home does nothing within that launcher as well.
So some how, not sure what happened, but the phone is using both launchers at the default now and there's no way to stop One UI from opening.
I don't know if anyone else is having this issue, or if there's a fix for it, but would removing One UI with ADB (if possible) cause issues? Like if I force remove this with ADB will the phone even boot to a different default launcher if One UI home isn't there anymore?
I would do more testing but this is my daily driver so I don't wanna mess with it too much, but this is really annoying that it keeps defaulting to One UI home.
I was having the same issue at first. What I did to fix it was set OneUI as default, exit the menu. Go back into that menu and then change back to Nova Launcher. Reboot. It took a couple of tries repeating the same process, but it eventually sticks. I haven't had any issues since.
Also, side note. The Samsung widgets that aren't transparent, first set them up in OneUI with the settings you want them at. Then when you go back Nova Launcher, remove the the original and readd them. There is only 1 widget that I can't get to go transparent, Reminders.