Related
hi,
does anyone know how i can set it so the screen auto locks after a given amount of time or is there a freeware app that can do this please. because i rather have it that having to remember to press the power button to lock everytime, sometimes i might forget.
cheerz,
snoop
Lock the Screen? Power-Button simply switches the Device of, e.g. the screen. In Power Management you can set a Device timeout in Battery Mode and on AC Operation. This is equal to pushing the Power Button
I think i see the problem, or i'll tell my problem with that issue...
When you push the power-button the screen turns off and is locked, but if you receive a sms or so, the screen returns back on and is not locked...
ok ye i think u get my point.
i dont know about screen lock after receiveing sms or call.
but i c the point of samson, pressing the power botton does lock the screen.
snoop85 said:
ok ye i think u get my point.
i dont know about screen lock after receiveing sms or call.
but i c the point of samson, pressing the power botton does lock the screen.
Click to expand...
Click to collapse
look for deviceock or vj devicelock.
There is a today-application called BatteryStatus. With its help you can lock the device automatically when it is shut down. Does the job for me - of course you allways have to unlock the device after turning it on.
drmadu said:
There is a today-application called BatteryStatus. With its help you can lock the device automatically when it is shut down. Does the job for me - of course you allways have to unlock the device after turning it on.
Click to expand...
Click to collapse
hi
do u have the file? As im sure there would be many apps with similer name. would be great if u could attach file plzz
thnx
Snoop
snoop85 said:
hi
do u have the file? As im sure there would be many apps with similer name. would be great if u could attach file plzz
thnx
Snoop
Click to expand...
Click to collapse
If you had bothered typing 'BatteryStatus' into Google you'd have seen it was the first hit. Establishing it is the right program is simply a case of reading the web page. Why are people so goddam lazy these days?
yes ok i get your point. sorry.
right i have installed. lots of nice options and things. but have little problem now. As we knw the device has the function where as the backlight will turn off after a set amount of time. Mines set to 30sec for battery power and 1min for external power.
After 30secs (using battery) it does its job and turns off the backlight. Normally i would press the power button and device turns back on. HOWEVER! since installing batterystatus the device just wont turn back on. I mean its got enough battery, i can tell this because 1) the light at the top flashes 2) Heres the strange thing , the only way i seem to be able to waking the device from backlight is by pluging in the usb cable.
So i thought i would try and un-install the app see if that would help..but nope that didnt help because it still does the same thing.
After installing the app i did a soft rest. I thought it might help, but it didnt. This is the other thing, once i did this, i see the t-mobile splash screen where shows the ROM and other info. And then i just goes blank for a while....and then i see the T-mobile PIN entry keypad splashing by every few secs. I was only able to by pass this after trying and trying to enter pin number on a black screen.
Do you think i should do a hard-rest? Dont really want to do this. Means i have to re-install my little apps and contacts, email settings etc etc.
Can anyone help me with this problem please??
Hi there, i had quite te same problem, after a soft reset the backlight turns on until the bootup screen dissapears, then the screen seems to be blank, but it shows everything, but without the backlight on. You have to point a light onto the screen and you can hardly see wats on it.
Then go to the backlight settings and turn it up.
Then you have to look at every program, thats adjusting the backlight settings and turn of automatic darken screen or so in the program.
That helped for me.
amokoma said:
Hi there, i had quite te same problem, after a soft reset the backlight turns on until the bootup screen dissapears, then the screen seems to be blank, but it shows everything, but without the backlight on. You have to point a light onto the screen and you can hardly see wats on it.
Then go to the backlight settings and turn it up.
Then you have to look at every program, thats adjusting the backlight settings and turn of automatic darken screen or so in the program.
That helped for me.
Click to expand...
Click to collapse
WOW great i thought it was just me *phew! lol*. Thats excatly what is/was happening to me but....
this app just gets stranger and stranger.
i reinstalled baring in mind your suggestion. I did the same thing i did before, expect i turned the brightness up before i installed. Then once installed waited 30secs and soft restted. And :S stranger thing was that the problem didnt happen this time, i saw the t-mob splash screen, saw the windows mobile green splash screen and then my keylock and then pin number screens.
hmmmm no idea wots that was all about. but hey its all working K.O so im happy now. just got to fiddle with the settings now
Thanks againt to everyones help. Appercaited
Snoop
Had the same problem SPB pocketplus 3 seemed to be the problem did a hard reset and no more pocket plus all problems resolved.
my problem seemed to be SPB PocketPlus too, but i did the thing i wrote earlyer and it still works just fine.
ClearType Lock the screen
I've noted that the screen will be lock when I set the CleartType. Has somebody the same issue?
faria said:
look for deviceock or vj devicelock.
Click to expand...
Click to collapse
people claims in this thread that OnLock is much better than VJ DeviceLock
http://pdaphonehome.com/forums/ppc-6700-xv6700/80830-i-have-written-another-screenlock-program.html
regards
Hey guys, i have some problems that i hope somebody can help with. My phone isnt rooted, basically out of the box stock, but ive had it since the day it came out. So shes got some time on her.
It was working perfectly till about a day ago. Then all of a sudden the screen would not stay off for more than a second. I would push the lock button and it would turn off, but the lighted buttons (home, back, etc) would stay lit. Then the screen would turn back on a second later. But i found that if i push the lock button and immediately push it again, the lighted buttons will also turn off and the screen will stay off. If i hold the lock button it will just flash the menu with the options to power off options (airplane mode, silent mode, etc..), but immediately disappear. But if i hold the lock button till just before that menu would pop up, it wont always disappear.
Also sometimes when i try to open any app it will close automatically, popping up with a recent apps menu that ive never actually seen before. I can push back and the menu will go away and i can try to open the app again. Usually successful the second time.
And last my battery life has gone down the drain. It went from fully charged to empty in about 7 hours. It used to last much longer. The screen might be on in my pocked, so that could be the problem, but i try to check it often to see if its on.
Just hoping that someone will know if this is a hardware or software problem. The phone was perfect in the morning, and a few hours later the problems started.
I have android version 2.2.1, froyo i believe.
Any help will be really appreciated. Sorry for the long post, just trying to be specific.
As we all know(or should know if you read around the forums) that there is an issue with "sod". Now these sods are not the same as the sod i was familiar with before 4.2. Before 4.2, the device(s) were for all intensive purposes not alive. Sure you could connect to adb, but the device was "dead" until you pulled the battery and rebooted. But with these 4.2 "sods", the device is alive, with the exception of the screen not being able to turn on. Phone calls and messages still come in. notification sounds still play, and you can use the volume buttons to raise/lower the volume. But you still have to pull the battery and reboot for the screen to come back on. Running logcats via adb doesnt seem to show anything related. Well, ive found a way to reproduce these 4.2.X "sods" while the device is awake with the screen on. I can reproduce it at will, and have had other users confirm this. What i do is this.. I go into the main settings, display, then brightness. Turn off automatic brightness if its on. Now adjust the brightness, up, then down, then up(back and forth, but take your finger off the slider when you go up then down). now press ok to set the brightness. Go back into the brightness setting and repeat. Eventually(sometimes seconds, sometimes minutes) the screen goes completely black, like its off, but the device is completely awake. same as these 4.2 sods, phone calls and messages come in, notifications sound, etc. Only difference is the device screen is on when it goes black instead of it being off. The symptoms are the same. This behavior leads me to believe that it most likely isnt a kernel issue like many believe. I believe that its related to some coding that controls the screen. As we know, every rom/kernel has shown this behavior, even stock and unrooted(some more, some less). Personally, i had 3 of these sods last month(trinity kernel/rasbean rom), but i know that some users have them many times a day unfortunately. What could it mean that i can replicate this behavior on an awake device? Any more thoughts about this?
maybe someone using another kernel/rom can try to reproduce this?
I haven't tried your method yet. I'll and post my results here. I was able to replicate it using another program (check the links below)
But reading your post, I'm sure now that SOD has to do with autobrightness or brightness control (knowing that, maybe it is easy to solve?)
Check my posts:
http://forum.xda-developers.com/showthread.php?p=35205418#post35205418
http://forum.xda-developers.com/showthread.php?p=35496824#post35496824
Check my post here:
[URL="http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638"]http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638[/URL]
whre I answered to that phenomen. I was on RBJ + franco r348 that time
I can't reproduce (force) it now with RBJ + franco r360, I tried about 100 times.
Just wanted to post my results, maybe it's too early to tell as r360 is too young.
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
Maybe because OMAP is abandoned at 3.0.
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Jessie-James said:
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
if your device wakes, even after a few presses, its not sod.
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
pressing and holding the power button for 10-20 seconds will force reboot those devices.
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
MondoMor said:
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
Click to expand...
Click to collapse
wouldnt it be easier to just pull the battery? thank you for your observations btw.
simms22, I actually think it is a kernel issue. I only experience SOD problems when i use a custom kernel. Also yesterday I flashed stock 4.2.1 and tried for 10 min to replicate SOD using your method - I could not. Today I tried again - nothing.
simms22 said:
wouldnt it be easier to just pull the battery? thank you for your observations btw.
Click to expand...
Click to collapse
My phone is in an Incipio case, and it's more of a pain to separate the case, especially if I'm in my car or out hiking or whatever. I've gotten pretty good at doing it blind. Also, years of running Windows have made me anal about doing orderly shutdowns. :laugh:
Forgot to add earlier: I was unable to replicate with the technique described in the OP. But as long as someone can get this to happen on demand, it ought to be solvable.
Edit: although I got the SOD in normal usage a few minutes after trying the technique in the OP. Maybe the display SODs on some specific number of brightness changes? That would explain it happening more often with autobrightness, also.
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
Just hold down the power button for several seconds. Continue to hold down the power button until the screen blinks off and the boot logo appears.
We are flooding here.. lets discusse this other place and leave the devs alone here
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
andQlimax said:
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
Click to expand...
Click to collapse
When I was running the first few nightlies of CM10.1 it still did the "sod" on me. By default the animation settings are at 1.0. Not sure if it's different on stock.
I've had several sod's daily for last few day's and today finally flashed RBJ from the beginning plus dax's modified kernel and now i'm in watching phase. So far so good.
I have time without any sod... Maybe because I'm trying not to use auto brightness or because of the lastest versions of Francos kernel... Stock ROM
Sent from my Galaxy Nexus using xda app-developers app
Phone arrive in mail yesterday. Charged phone fully. Turned phone on. Lots of voice activations on the set-up wizard screen. I try to pick a language from the drop-down screen and it just highlights it with green dashed lines and the voice activation says 'english'. That's it. I try to hit the next arrow for the next step and it keeps telling me the time. I mean I'm no expert by any means but I'm also no rookie when it comes to turning a phone on for the first time. This is really weird. I can't get past this screen. Tried fully shutdown and start back up. Same thing. Mind you I haven't put a sim card in yet but I didn't think that would matter as I was going to use wifi to set it up anyways. I can't even turn the phone off by touching on screen either. I have to long press the power button to turn it off as the touch screen doesn't seem to work. Anyone have issues with this? It's very disheartening coming straight out of the box...
Update
brahmaboba said:
Phone arrive in mail yesterday. Charged phone fully. Turned phone on. Lots of voice activations on the set-up wizard screen. I try to pick a language from the drop-down screen and it just highlights it with green dashed lines and the voice activation says 'english'. That's it. I try to hit the next arrow for the next step and it keeps telling me the time. I mean I'm no expert by any means but I'm also no rookie when it comes to turning a phone on for the first time. This is really weird. I can't get past this screen. Tried fully shutdown and start back up. Same thing. Mind you I haven't put a sim card in yet but I didn't think that would matter as I was going to use wifi to set it up anyways. I can't even turn the phone off by touching on screen either. I have to long press the power button to turn it off as the touch screen doesn't seem to work. Anyone have issues with this? It's very disheartening coming straight out of the box...
Click to expand...
Click to collapse
I got past the screen but I had to 'double-tap' (and by double tap i mean like 4-5 taps sometimes) the next arrow. I have to do this at every screen until it gets to the log into gmail screen. I try to type my email in by double tapping each letter but this doesn't work. Now I have no idea what to do.
I had the same thing happen to me yesterday and figured it out.
If you have not figured it out let me know I can help.
mine arrived same problem
brahmaboba said:
Phone arrive in mail yesterday. Charged phone fully. Turned phone on. Lots of voice activations on the set-up wizard screen. I try to pick a language from the drop-down screen and it just highlights it with green dashed lines and the voice activation says 'english'. That's it. I try to hit the next arrow for the next step and it keeps telling me the time. I mean I'm no expert by any means but I'm also no rookie when it comes to turning a phone on for the first time. This is really weird. I can't get past this screen. Tried fully shutdown and start back up. Same thing. Mind you I haven't put a sim card in yet but I didn't think that would matter as I was going to use wifi to set it up anyways. I can't even turn icy phone off by touching on screen either. I have to long press the power button to turn it off as the touch screen doesn't seem to work. Anyone have issues with this? It's very disheartening coming straight out of the box...
Click to expand...
Click to collapse
I'm having this same issue as you. Mine just arrived today. It seems likely they put a recent image on these that may have something missing off broken on it. The models before them seem to not have this problem. Worst is you can really fix it or get past it since its the initial setup. What to do now? Send it back?
Flash a new image?
Sent from my KFTHWI using Tapatalk
TalkBack may be enabled. If this setting is enabled, there will be voice prompts to every action made. Also the touch screen may behave differently and appear to be defective. Instead of one tap to open an item it will require tapping once to highlight then double tap to open. Also when swiping it may require using two fingers instead of one. To disable go to Apps/Settings/Accessibility/Talkback - turn off.
Sincerely,
ASUS_USA
brahmaboba said:
Phone arrive in mail yesterday. Charged phone fully. Turned phone on. Lots of voice activations on the set-up wizard screen. I try to pick a language from the drop-down screen and it just highlights it with green dashed lines and the voice activation says 'english'. That's it. I try to hit the next arrow for the next step and it keeps telling me the time. I mean I'm no expert by any means but I'm also no rookie when it comes to turning a phone on for the first time. This is really weird. I can't get past this screen. Tried fully shutdown and start back up. Same thing. Mind you I haven't put a sim card in yet but I didn't think that would matter as I was going to use wifi to set it up anyways. I can't even turn the phone off by touching on screen either. I have to long press the power button to turn it off as the touch screen doesn't seem to work. Anyone have issues with this? It's very disheartening coming straight out of the box...
Click to expand...
Click to collapse
is this the initial set up after opening the phone? i dont have activation or things like that on my initial set up....activation thing is after the set up on settings...... weird...... hope your tech can help you
Asus_USA said:
TalkBack may be enabled. If this setting is enabled, there will be voice prompts to every action made. Also the touch screen may behave differently and appear to be defective. Instead of one tap to open an item it will require tapping once to highlight then double tap to open. Also when swiping it may require using two fingers instead of one. To disable go to Apps/Settings/Accessibility/Talkback - turn off.
Sincerely,
ASUS_USA
Click to expand...
Click to collapse
Thanks! This worked. I found someone else online who had the same issue and that's exactly what happened to him. I just used 2 fingers to click through the setup wizard and then finally was able to go into settings and turn TalkBack off. This was very annoying right out of the package. Hope this helps someone else.
Could any of you please kindly send me a private message with the model, serial number, and if purchased in the USA? We are trying determine which units have been distributed with TalkBack feature enabled.
Thank you,
Frank
ASUS_USA
TalkBack enabled on new phone
Frank - How do I send you a private message?
Asus_USA said:
Could any of you please kindly send me a private message with the model, serial number, and if purchased in the USA? We are trying determine which units have been distributed with TalkBack feature enabled.
Thank you,
Frank
ASUS_USA
Click to expand...
Click to collapse
I had someone that had this happen at the Intel pre-Google IO event Wednesday night. If you don't want to go through the full setup -
1). Turn the phone off
2). Hold volume up + Power
3). Use the volume down button to highlight recovery
4). Press power button to select, it'll show an erroring Android screen now
5). Press volume up + power again (might take a few times before the recovery menu is available
6). Wipe user data and reset. It'll take a few minutes but it'll save you from having to deal with talkback
Thanks so much for this thread. Just got mine and am in Nicaragua and have no way to send it back to Amazon and was gonna flip the **** out.
Asus_USA said:
Could any of you please kindly send me a private message with the model, serial number, and if purchased in the USA? We are trying determine which units have been distributed with TalkBack feature enabled.
Thank you,
Frank
ASUS_USA
Click to expand...
Click to collapse
Same issue on mine. Purchased via Amazon. PM you the info...
Same issue- purchased from Amazon
I had the same issue when I received my phone this morning. I couldn't get it to work even after following the instructions to power it off and then power on + volume up. I am returning it to Amazon for a replacement. If I have the same issue with the replacement, I'll just return it. There's no way I'm paying $200 for a brand new phone to have it not even work upon taking it out of the box.
I just received my telephone today... After spending 20 minutes to pass the wizard guide (as i had to tap over 10 times to pass a single step), I cant even unlock my screen. Im from Bulgaria, there is no way I will send back the phone to Amazon. Its just not financially possible for me. I dont know what to do. A brand new phone...
i just bought an asus zenfone 2 from amazon and the same talkback is happening.
ready to shove phone where the sun dont shine
i am trying to wipe and redo intall because i got a dud. why the heck send out phones like this
i get to error screed but cant get past it
is there a secret??
ozexpat said:
i am trying to wipe and redo intall because i got a dud. why the heck send out phones like this
i get to error screed but cant get past it
is there a secret??
Click to expand...
Click to collapse
Push power button when you see the android with eroor under it and press up volume, you might need to dothis a couple of time but be aware that if you do it too fast you can go to recovery then jump back out just as quickly.
Holding power for more than 8 seconds will result in a reset.
Hi, Just bought the Asus ZenFone 2 , I cant pass the Welcome screen its talk back feature is on Pls Help. Thanks
This is 4/30/16. I just got my screen replaced on my ASUS ZenPad 8 inch 580. Same problem happened with Talkback to me. I followed the instuctions from the guy who said tap twice on the buttons. I had to sometimes do this many times, but I got through to the tablet settings to turn Talkback off even before settig up Google and other apps, I just connected to my wifi, then went next until the home screen could be opened, then settings symbol, then accessibility, then turned off Talkback. Boy was I happy. Maybe I got an old LCD and screen? Dont know why it happened so much later than you people in 2015. from:[email protected]
So I activated Universal Switch on S6 Edge to check it out, something went wrong in the settings (long story short, got a pop up while setting it up), now screen unresponsive.
It works, I just get this blue horizontal line scanning the screen and nothing else but the power button and home button works. Tried safe mode, no bueno. How can I disable US feature without resetting to factory or at least no data wipe (if possible!)?
Android 5.0, rooted with pingpong, no custom recovery, knox 0x0.
All help is appreciated.
Same
[The exact same thing just happened to me someone please help
Fixed!
The way I had fixed this is by holding down the power button, both up and down sound buttons, and the home button until it restarted. When the device turned back on it gave the option to turn the setting off. Hope it helped!
ImJustBoss99 said:
The way I had fixed this is by holding down the power button, both up and down sound buttons, and the home button until it restarted. When the device turned back on it gave the option to turn the setting off. Hope it helped!
Click to expand...
Click to collapse
it works , thanks so much buddy , i love you:good:
how to turn off universal switch
hit home button 3 times
Thanks alot
It worked buddy
It doesn't give me the option to turn it off
Hi,
I have been struggling with Universal Switch on a Samsung S5 Neo. I switched it on, but was never able to switch it off again.
These are findings so far:
-> Did a factory reset using "Sound Up", "Home" and "Power" button simultaneous.
-> The device comes back and wants to configure itself again.
-> I restored my settings from Google, but this immediately brought back "Universal Switch"
-> Factory Reset again and configured the device, but told Google that I want to use it as a "New Device".
-> Now I can use my device in a proper way.
-> In Google Play Store I find all my Apps which were linked to my account and reinstalled them and I am back in business again.
-> Took me half a day to sort this out.
The programmer who designed and programmed this should be hung and shot and poisoned, because this is absolute Crapware.
Hope this helps for all the others who are suffering.
You can also push the home button three times and it should turn it off.
thank u ur the best
Ok, so i have exactly the same problem except my home button doesn't work
Anyone one know how to sort this without having to take it in to a store?
I was faced with this problem before and looked everywhere and couldnt find a fix. This was a while ago. So I dont remember what I did to clear it. I was cleaning off the screen and touched the home button as I was wiping it off and the problem began again.... I just came across your comment because all the others failed. I pressed the home button 3 times quickly and the blue lines stopped scrolling. In addition, I went over the accessibility and I turned off the "Universal Switch" option as much as the option allows. I hate this function. I do not use it or need it (for my needs). I hope I can remember what to do next time this happens. I swore to myself I would remember last time, but apparently that wasnt a guarantee. This time, I will write it down and put is somewhere I know I will find it next time I see these nefarious blue lines scrolling. Hopefully I wont see it again since I disabled it more than it was to begin with. Thank you ever so for commenting. You saved me a lot of frustration!
great fix
CarlyCraig said:
hit home button 3 times
Click to expand...
Click to collapse
thank you for posting the only sollution that works.
Hello,
I have activated Universal Switch option Screen - Volume Increase button on S6 Edge upgraded version of android 6.0 and but it messup everything.. I am now unable to access any feature on screen.. none of the button are working on screen.
I have also tried rebooting it with the option suggested by you.. but I am locked due to password protected... My device not asked to disable Universal Switch option after reboot as well..
Please help, how to get this Function Disable, without affecting my data as I do not wish to loss any of my data..
So what the heck is that scanning blue line option supposed to do?
My home button is not working, now tell me how do i get out this situation
Akki167 said:
My home button is not working, now tell me how do i get out this situation
Click to expand...
Click to collapse
Have you tried pressing it rapidly three times?
It happens to me too, have you solved this problem? Please tell me what to do im freaking out right now
me too @Alifanasya
same issue
it works with OTG cable + mouse