Screen Filter Glitch - HTC EVO 3D

Try sideloading an app with the button lights turned off
Weird huh?

WWwhha?.. your..
...your post didn't make any sense, what are you talking about? I'm intrigued because I'm using screen filter right now. But I don't understand your language
SPEAK UP!

I use screen filter to turn off the capasitive buttons, when I sideload an app (from slide me for instance) the install button on the screen is dead. The "show all" and "cancel" button work, but when you touch install nothing happens.
I was confused why this was happening because I was able to install app a few days ago. I tried a few file managers, even checked the unkown sources setting, the dern app didn't want to install. For some reason I decided to turn on the buttons and try to install the app again and it worked.
Just a weird glitch I found, it happens every time the buttons are turned off.

Yeah, discovered this awhile back. Screen Filter, when enabled, prevents that Install button from being pressed. Was driving me crazy before figuring out the cause

phatmanxxl said:
I use screen filter to turn off the capasitive buttons, when I sideload an app (from slide me for instance) the install button on the screen is dead. The "show all" and "cancel" button work, but when you touch install nothing happens.
I was confused why this was happening because I was able to install app a few days ago. I tried a few file managers, even checked the unkown sources setting, the dern app didn't want to install. For some reason I decided to turn on the buttons and try to install the app again and it worked.
Just a weird glitch I found, it happens every time the buttons are turned off.
Click to expand...
Click to collapse
Oh!!. I know... God that was driving crazy until I realized it was screen filter. Man, what a weird glitch.
Sent from my PG86100 using Tapatalk

Related

Any one know how to have the screen not time out in calls?

Any one know how to have the screen not time out in calls? I want the screen to time out and i like setting the power button press to end calls
But with setting combo when the screen times out in a call you can not wake up the screen without killing the call
Sent from my MB855 using XDA App
I second that. I ended many a call be fore I figured out what was happening.
Sent from my MB855 using XDA Premium App
Download "Screen On" from the Market and put a checkmark on "An Active Call" so it never goes to sleep.
CCallahan said:
Download "Screen On" from the Market and put a checkmark on "An Active Call" so it never goes to sleep.
Click to expand...
Click to collapse
Does "Screen On" affect the Proximity Sensor, or just keep the device from locking?
Not sure. Don't remember it messing with the sensor. I used it a lot while on CM7 with my other phone and it always worked stellar.
All I can say is give it shot and see if it works the way you want. On my phone, if the screen goes dim all I have to do is tap the power button and takes me right back to the "in call" screen.

S3 Lock Screen Issues - Getting Stuck

weird and terribly disappointing. Once in atleast 15 unlocks, when I press the power/wake button, screen just doesnt respond. I try to swipe, but no response. But when I press wake button to turn off screen and press it again, theres no issues. This happens only during unlocking screen. Did anyone face this issue?
rest all is good..no lag..once unlocked phone works perfectly...no lag..no getting stuck..again, let me tell u this issue happens once in 15-20 lock/unlocks.
I think I have the same issue as you, but in case I don't I will post what I am seeing on my device.
In about the same frequency, say once in every 15 unlocks from phone sleeping, the screen will come on but will be completely unresponsive. Doesn't matter if it is swipe unlock or pin code etc, there is no response to touch input on the screen. In fact, I think the screen is just frozen or the operating system is causing the lock screen to hang.
If the lock screen is hanging, pressing power will:
(a) sometimes make the phone sleep again
(b) make the phone screen kind of glitch/blip and then it takes input again
(c) does nothing and the screen remains on and hung/frozen
Occasionally mashing both the volume key and power key will help fix it, but usually if it is completely stuck I have to do a hard reset (holding HOME+VOL UP+POWER and then selecting reboot from the menu).
Now - I think this could be an app, but not sure.
When I first got the phone, set it up with my Google account etc, it went ahead and downloaded ALL the apps I had installed on my previous phone (HTC Sensation running Android ICS). So if it is an app, it is having issues with this phone, not the OS, imo.
I uninstalled all those automatically downloaded apps, and used the phone for a bit without my normal stuff installed. Then started installing apps singularly.
I think it is either Facebook or Alarm Clock Xtreme. The latter makes more sense given it would be polling the system to find out when to go off, so it is doing more in the background I would expect than Facebook or any other non-system app.
Other apps I have installed/running:
Swiftkey X
3G watchdog
Dolphin Browser HD
ES File Explorer
Winamp (locks without this running or running at all in lock screen mode, so that is not the issue)
Real Calc
Google Drive
Facebook
Alarm Clock Xtreme
It is quite frustrating for a brand new phone to have these issues. Not sure if it is hardware related, and if it is, I want to find out soon so I can take it back to carrier within their 28day device swap RMA period.
Thoughts?
So others may try to help or identify the possible cause / fix .......
What is your firmware version?
Are you rooted, custom ROMs or Mods etc?
Stock ROM,Baseband : XXLE8. Build No :XXALE9.
But my screen responds after i press wake button again. You are right seems to be issue with the app. i will just compare your apps and below are the ones which are common between us.
Facebook
3G watchdog
Dolphin Browser HD --i never use
Google Drive
a fix that worked for me
Steps to the solution that worked for me (so far) were to uninstall:
1. Alarm Clock Extreme (no noticeable result but I wasn't needing that application anyway)
2. I had WIFI Fixer installed because of the problems I experienced with the WIFI connectivity on my Galaxy S3.
I disabled that application and problems seemed to go away for a time, but every so in a while they resurfaced. Much less often than before, though.
I was still stuck with my WIFI problem anyway, so I looked into solutions for that problem and since I could not find a workable solution I uninstalled Wifi Fixer and started tweaking my WIFI settings.
While doing that I noticed that disabling "Network Notification" under the Settings -> WIFI -> Advanced tab fixed both my problems.
Now I can't be 100% sure this solution works for all, but I am pretty sure the application that created the problem was "WIFI Fixer".
It's been more than 4 hours now without the "disabled unlock screen from hell", and I’m very happy.
LOOOL
Actually...
My WIFI problem was not solved.... but I found a solution on another forum , which you can read below:
I dialed *#0011# then pressed menu button, then selected WIFI, and pressed the button to turn off the "WIFI power save mode". Hit back until I was back in the homescreen. WIFI has worked to my satisfaction ever since.
This is not a solution, this is a work-around....
It will remove the standby wifi.... My phone was at 0% battery in one night... But actually yes, the phone doesn't hang up when unlocking.
Someone who had replaced the phone could tell me if the problem is solved with a new one ?
calint said:
My WIFI problem was not solved.... but I found a solution on another forum , which you can read below:
I dialed *#0011# then pressed menu button, then selected WIFI, and pressed the button to turn off the "WIFI power save mode". Hit back until I was back in the homescreen. WIFI has worked to my satisfaction ever since.
Click to expand...
Click to collapse
Sadly having the same issue! and only sing LG6 and LG8 of the UK firmware was release.. out the box was LG4 if I am not mistaken... have been putting off custom roms due to the fact stock one is so far good..
This fix seems to be working..Thanks! will live with battery drain as data is expensive in SA!
khan.dharvesh said:
weird and terribly disappointing. Once in atleast 15 unlocks, when I press the power/wake button, screen just doesnt respond. I try to swipe, but no response. But when I press wake button to turn off screen and press it again, theres no issues. This happens only during unlocking screen. Did anyone face this issue?
rest all is good..no lag..once unlocked phone works perfectly...no lag..no getting stuck..again, let me tell u this issue happens once in 15-20 lock/unlocks.
Click to expand...
Click to collapse
This looks like a bug from wifi, i had the same problem and i found a fix:
On the dialer type: *#0011#
Then press menu -> wifi, there is a button ON ( power saving or something ), change it to OFF.
let me know if it solves ur problem
It worked!!
douglasurbano said:
This looks like a bug from wifi, i had the same problem and i found a fix:
On the dialer type: *#0011#
Then press menu -> wifi, there is a button ON ( power saving or something ), change it to OFF.
let me know if it solves ur problem
Click to expand...
Click to collapse
This worked for me!!! Thank you!! I was about to take a hammer to this phone! :good:
I seem to have another problem. When unlocking the phone the screen turns on in a quite ok amount of time, but then when I touch it immediatelly after it turns on it doesn't react to touch. This moment when touch is not working is getting longer and longer depending on how long the system is running, anybody else sees this?
RhavoX said:
I seem to have another problem. When unlocking the phone the screen turns on in a quite ok amount of time, but then when I touch it immediatelly after it turns on it doesn't react to touch. This moment when touch is not working is getting longer and longer depending on how long the system is running, anybody else sees this?
Click to expand...
Click to collapse
Not sure what ROM and kernel you are using, but at a big guess, try reflash another kernel or with less aggressive settings.
Sent from my GT-I9300 using xda premium
hey guys. I have a problem with my s3's lock screen similar to the described. whenever I press the power button to unlock, it takes 2 second for the screen to turn on. Anyone got any ideas on that?

Screen won't timeout while charging

I'm running stock, and I've found the screen won't automatically turn off while charging. 53 seconds after last touching the screen it will dim (when not charging it turns off at 60 seconds as it should), but will never turn off or lock as long as it is plugged in.
I've only installed these apps: audible, Facebook, pandora, speed test, and swift key. All updates installed.
This problem even happens after a battery pull at the lock screen before I've touched the phone, it just dims the lock screen.
There is an option in settings somewhere for "Keep screen awake while charging".
On ICS its in the development submenu - I can't remember exactly where it was on GB..
If you use a power control widget, you can change the screen timeout options.
I recommend Power Controls by Painless Death.
https://play.google.com/store/apps/details?id=com.painless.pc&feature=nav_result#?t=W251bGwsMSwyLDNd
Best free widget I've found.
Or just press the lock/power button manually once phone is plugged in?
Sent from my GT-I9100 using xda app-developers app
a.mcdear said:
There is an option in settings somewhere for "Keep screen awake while charging".
On ICS its in the development submenu - I can't remember exactly where it was on GB..
Click to expand...
Click to collapse
Great thanks! I found it under applications/development. Verizon sent me a new phone today because they didn't know how to stop it, sad.
thechristobol said:
Great thanks! I found it under applications/development. Verizon sent me a new phone today because they didn't know how to stop it, sad.
Click to expand...
Click to collapse
LOL. Oh well, it will just get sold to someone else in a few months! No big loss.

Screen turns on when on call using bluetooth headset

Hello everybody.
I have a rooted 4.0.4 XXLFB Galaxy S3 and have noticed a problem.
Whenever I'm on a call using my blueooth headset, the screen turns on once every 30 seconds, give or take.
It's a problem because if I have the phone in my pocket, sometimes I mute the call, other times I turn off the headset...
Does anybody know how to solve this?
Thanks in advance.
Posting to add a "me too" to the list. Trying a ton of different things, almost to the point of clean device.
Hit the button and the screen turns off, about 2-5 seconds later, screen turns back on. Does not matter what I do. Seems to do it with speakerphone option too. If neither Bluetooth nor speakerphone are used, and you put the phone to your ear, backlight stays off. Otherwise, it automatically turns back on by itself. Tried with wifi on/off, speaker with bt on/off, different headsets, etc. My Wife's does not have this issue, so I gotta look into what is different. There has gotta be a setting or app installed that is doing this. I've even tried apps such as screebl and others. Some even had a thing to say lock it off till press button, and it still comes back on after 2-5 seconds. I've muted and hung up on many people when the phone was in my pocket because of this issue.
I've not used a BT headset but i'm thinking that maybe because the phone isn't against your head the screen comes on. possibly to give you information about the caller.
I'm not saying you should put the phone to your head even though your using bluetooth either.
thanks, but, don't help, tried that too. Had entire top half of phone covered during most tests. Screen does not turn off unless I press button, then comes back on automatically after 2-5 seconds. I did find one app today that seemed to work, but not sure if it works too well "Smart Screen Off".
Sounds silly but have you tried locking the handset?
That's what I meant by pressing the button. Button on right side that if I am not on a call, turns off screen and locks it.
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
visegrip72 said:
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
Click to expand...
Click to collapse
agree with the above. if you leave call status up while connected via BT headset, screen remains active (comes in and out). if you exit active call status (ie press home) then the screen timeout works. if you are talking on the phone without headset, no problem.
so yes, that's the prob. any solid fix yet?
please and thanks....
visegrip72 said:
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
Click to expand...
Click to collapse
Thanks a lot, visegrip. It was really frustating having to redial every other call because i hang up without noticing.
Any solution to this problem? Hitting a home button and locking the phone is not an option when I keep my phone in a leather holster on my belt. That's a main reason for having bluetooth as hands free.
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Almazick said:
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Click to expand...
Click to collapse
Almazick,
It would be great if you can send me the fix!
ital1981 said:
Almazick,
It would be great if you can send me the fix!
Click to expand...
Click to collapse
Here is the fix for a screen that I created. Let me know if it works or not for you.
http://www.mediafire.com/download.php?1ikj7d4wnjs9hx5
Almazick said:
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Click to expand...
Click to collapse
You know, I use tasker and have been trying to figure this out for a while. I've also been trying Secure settings and Locale Using multiple settings and plug-ins. I have not been able to create anything yet that seems completely reliable.
Not trying to be rude or anything, but I am and always have been a little leary of installing APK files unless I know the source. However, if you would be so kind to post the contexts and tasks so that I may enter them myself manually, it would be greatly appreciated. Thank you in advance.
Inane65 said:
You know, I use tasker and have been trying to figure this out for a while. I've also been trying Secure settings and Locale Using multiple settings and plug-ins. I have not been able to create anything yet that seems completely reliable.
Not trying to be rude or anything, but I am and always have been a little leary of installing APK files unless I know the source. However, if you would be so kind to post the contexts and tasks so that I may enter them myself manually, it would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
Well, It's pretty easy.
Profile -> Phone Offhook
Task:
Wait 20 seconds
App-> Go Home
Display -> System Lock
In case if you'll have any problems just use my apk file which is exactly the same.
Good news! I just took the Jelly Bean update from sprint & this problem is FIXED!
I tried calling and turned off the screen and it stayed off!
I also called and didn't touch the screen and after the timeout, it turned itself off!
Hmmmmm... OK. Thank you. I'll have to try that and see how it works. I was looking, hoping and working on trying to get something that would keep the screen off. Dialing, talking and ending the call. I've got something that seems to work for the most part, (I still get quick flashes, which is fine) but still have some more work to do on it.
Sent from my ADR6425LVW using xda premium
visegrip72 said:
Good news! I just took the Jelly Bean update from sprint & this problem is FIXED!
I tried calling and turned off the screen and it stayed off!
I also called and didn't touch the screen and after the timeout, it turned itself off!
Click to expand...
Click to collapse
It's not fixed. I'm getting crazy about this master bug.

Screen won't time out

After my phone is running for awhile the screen won't time out, a reboot will fix it but after some time the screen won't timeout again. Also if Quick glance is activated, while the issue is present, the screen will turn on, start to dim and then the lock screen will show and stay until I shut it down. Maybe an app is running in the background and keeping it from shutting down? This is when the phone is not charging so it's not the Stay awake setting. I've also turned various settings on and off as well as changing the screen timeout, which is now set to 15 secs, and the problem still persists.
Anyone with this issue?
I've seen some (Issue 37974) with the GS3 posting about the same issue but never saw a resolution.
Any help or insight would be appreciated.
I've noticed this but it usually was an app that kept it running.
From the Homescreen, try holding down the Home "Verzion" button for a few seconds. Click "Remove All" and then see if it times out. If that doesn't work, try clicking "Task Manager" instead and closing all Active Applications.
If either of these do work, then when you notice it again, be more selective in which apps you close until you find the offending app. I have a few Sound Engineering apps that use the microphone and one of them forces my screen to stay on. I'm assuming to access the mic hardware. It seems to run in the background even when I "close" the app.
I've done the remove all and nada but I'm adsuming it is and app too...
Thanks for the reply...
It must be Stay Awake in developer options that is causing this bug. As stated a reboot fixes the issue temporarily, after the reboot the Stay Awake option gets turned off on its own, If I turn it on again the issue appears again shortly after. So somehow the Stay Awake option must be getting messed up and keeping the screen on even when not charging.
My workaround is turn off Stay Awake and Use Tasker to keep the phone awake while charging. Not what I'd like, I'd prefer the system work correctly, but it works for now.
Thanks
first off are you using a different keyboard other then the Samsung one ?
i had this happen to me using Swift.
just reboot your device and you should be golden.
Dont know why the keyboard would do this to the phone but thats what it was and all i did was reboot and Timeout works fine...
thenuke1 said:
first off are you using a different keyboard other then the Samsung one ?
i had this happen to me using Swift.
just reboot your device and you should be golden.
Dont know why the keyboard would do this to the phone but thats what it was and all i did was reboot and Timeout works fine...
Click to expand...
Click to collapse
Don't think the keyboard is a major issue with this. I've had this issue both when using swift and just the SS keyboard. I am more inclined to think like the other poster said that it has to deal with SmartStay. I haven't tried turning it off then rebooting, going to see if that works now. It sucks because toggling SmartStay is really useful, but i'm concerned with burn-in and especially with a battery that lasts 10hrs+, that could be an issue.
kimdoocheol said:
Don't think the keyboard is a major issue with this. I've had this issue both when using swift and just the SS keyboard. I am more inclined to think like the other poster said that it has to deal with SmartStay. I haven't tried turning it off then rebooting, going to see if that works now. It sucks because toggling SmartStay is really useful, but i'm concerned with burn-in and especially with a battery that lasts 10hrs+, that could be an issue.
Click to expand...
Click to collapse
interesting...
just my 2 cents. When i switched to swift from samsung key i just rebooted and it corrected the issue. Im sure theres a permanent fix but works as a temp one imo

Categories

Resources