Develop Bugs

[Q] Universal Switch enabled, screen unresponsive

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

Power button turns screen off, but not back on, can boot device ok though

Basically my issue is this:
If my phone is booted normally, and the screen turns off due to time out or me pressing the power button, I cant get it back on without a reboot.
Things i have tried:
- booting into download mode, recovery, and boot manager - When in any of these the screen works correctly. The power button works as expected.​
- full rom wipe and clean install of a different rom + updated firmware - No change​- Replacing the SD card+volume/power controls hardware - no change in behaviour​- I have Vysor (an application for screen mirroring on PC and device control), when i use the button on it for turning the screen on/off, it shows correct behaviour of the mimicked screen on my PC.(i.e on/off wake/sleep). When i use the hardware power button Vysors mimic shows correct behaviour of on/off wake/sleep, even though the phone screen does not turn on.​- I have tried disconnecting and re connecting the ribbon cable of the LCD, and tested with another LCD known to work - behaviour remained the same.​
Summary:
- My phone is otherwise functioning correctly - confirmed using Vysor
- My phone screen works - confirmed using 2x phone screens
- My phone screen works in recovery, bootloader and download mode as expected
- My power buttons work - confirmed in each of the above
- My phone boots by pressing the power button just fine, and the screen comes on fine
- Digitiser functions all working as expected
- if my phones screen is on, I can turn it off with the power button just fine
-- I can not turn the phone screen back on without rebooting the device (I use ADB or Vysor to reboot), but the phone IS waking up (seen through Vysor)
Any ideas?
On the one hand, it really looked like a hardware issue to me at first, but the problem persisted through 2x screens and 2x power buttons, and the power buttons and screen work in all other situations.
This then made me think it was software, but i replaced the firmware, recovery, and changed rom, with a full wipe (except data) to no effect. (yes i am s-off, and have done the trick to get permissions over the other remaining items such as software status)
I am completely stumped on what to try next.
Any suggestions would be very much appreciated, I am not overly familiar with software specifics.

rukia06 said:
Basically my issue is this:
If my phone is booted normally, and the screen turns off due to time out or me pressing the power button, I cant get it back on without a reboot.
Things i have tried:
- booting into download mode, recovery, and boot manager - When in any of these the screen works correctly. The power button works as expected.
- full rom wipe and clean install of a different rom + updated firmware - No change
- Replacing the SD card+volume/power controls hardware - no change in behaviour
- I have Vysor (an application for screen mirroring on PC and device control), when i use the button on it for turning the screen on/off, it shows correct behaviour of the mimicked screen on my PC.(i.e on/off wake/sleep). When i use the hardware power button Vysors mimic shows correct behaviour of on/off wake/sleep, even though the phone screen does not turn on.
- I have tried disconnecting and re connecting the ribbon cable of the LCD, and tested with another LCD known to work - behaviour remained the same.
Summary:
- My phone is otherwise functioning correctly - confirmed using Vysor
- My phone screen works - confirmed using 2x phone screens
- My phone screen works in recovery, bootloader and download mode as expected
- My power buttons work - confirmed in each of the above
- My phone boots by pressing the power button just fine, and the screen comes on fine
- Digitiser functions all working as expected
- if my phones screen is on, I can turn it off with the power button just fine
-- I can not turn the phone screen back on without rebooting the device (I use ADB or Vysor to reboot), but the phone IS waking up (seen through Vysor)
Any ideas?
On the one hand, it really looked like a hardware issue to me at first, but the problem persisted through 2x screens and 2x power buttons, and the power buttons and screen work in all other situations.
This then made me think it was software, but i replaced the firmware, recovery, and changed rom, with a full wipe (except data) to no effect. (yes i am s-off, and have done the trick to get permissions over the other remaining items such as software status)
I am completely stumped on what to try next.
Any suggestions would be very much appreciated, I am not overly familiar with software specifics.
Click to expand...
Click to collapse
It's a costly experiment in way of time and effort, but it may be worth going completely stock with a RUU. Assuming a backup of your data & settings you won't lose anything - and you might rule out the software issue (I'm thinking maybe you've gotten unlucky with the ROMs and/or kernels you've chosen, but possibly an app as well).

computerslayer said:
It's a costly experiment in way of time and effort, but it may be worth going completely stock with a RUU. Assuming a backup of your data & settings you won't lose anything - and you might rule out the software issue (I'm thinking maybe you've gotten unlucky with the ROMs and/or kernels you've chosen, but possibly an app as well).
Click to expand...
Click to collapse
Cheers for the suggest, not sure why i didnt think of that... think my mind was subconsciously blocking out that option.
So, i flashed the RUU for my 401 device from Flippys collection, and I still have the problem.
if everythings stock and i have the issue, I guess it must be hardware.
My Zenfones away getting fixed though so ill just have to struggle along with this somehow.

rukia06 said:
Cheers for the suggest, not sure why i didnt think of that... think my mind was subconsciously blocking out that option.
So, i flashed the RUU for my 401 device from Flippys collection, and I still have the problem.
if everythings stock and i have the issue, I guess it must be hardware.
My Zenfones away getting fixed though so ill just have to struggle along with this somehow.
Click to expand...
Click to collapse
I'm plumb out of ideas - I agree that it probably is a hardware issue, maybe something to do with the motherboard itself? I'm sorry.

Samsung Galaxy Nexus running Lineage - On/Off button fails

I have a Samsung I9250 which I've unlocked, rooted and loaded with Lineage. The Lineage version is 13.0-20171126-NIGHTLY-maguro. The recovery is TWRP and the root is through SuperSU FREE (CM) v2.79-SR3. The On/Off button doesn't usually work. If the phone is off then pressing On/Off has no effect. Occasionally it works for no reason I can see, it seems to be random, but for the most part it simply doesn't have any effect. If the phone is on then the same is true. Turning it off from the On/Off button is usually impossible. I get round this through Settings>Display & lights>Wake on plug. This means I can activate the phone by connecting it to a PC using its USB cable. This will activate the phone immediately if it is off. It doesn't help with turning it off and I am usually reduced to taking the battery out. The phone is effectively useless although it is clearly NOT bricked. When I can turn it on it works fine.
I don't know if this is a hardware or software problem. If it's a software problem I don't know if the fault is in Lineage or TWRP or SuperSU. I noticed that the problem existed before I installed SuperSU. Has anyone else come across this problem? I'm reluctant to bin the phone because I spent such a long time getting Lineage on to it, but, if I can't turn it on or off it's not really a phone. Any help would be greatly appreciated.

@erich_vogt it's more a hardware problem, you can buy a new button (find link of online stores in accessories section or google.it).
for easyness you don't need to plug charge/usb everytime, you can set volume button waker, find in settings > button (don't remember where correctly, it will be somewhere there) then use volume switches to wake it.

erich_vogt said:
If the phone is off then pressing On/Off has no effect.
Click to expand...
Click to collapse
There have been power button bugs, but only in the OS. If it's not turning on from off, then I think the switch is broken! A common failure in old phones, which is why "volume button to wake" is important, to reduce load on the power button.

Thanks very much for offering to help.
I already had the option for the Volume control buttons to wake the phone turned on. It's here - Settings > Buttons > Volume Buttons > Wake up device. This worked for a while then stopped. I disassembled the phone to look at the On/Off button. I tried turning the phone on directly from the metal contact pad beneath the plastic button. This worked. When the phone had booted I checked to see if there was another nightly update for Lineage. There was the 3rd of Dec update. I downloaded and installed the nightly update using TWRP. It reported a successful install. The phone rebooted and never got past the Google boot-up screen. I waited for a few minutes and the took the battery out and tried turning on again from the metal contact pad. The phone booted but again got stuck (or seemed to) on the Google boot-up screen. I'm afraid that's it for me. This doesn't appear to be related to anything I have done or not done. The phone is just taking up too much time and it will have to go the the local recycler. Life is, as they say, too short. Thanks again for your suggestions.

erich_vogt said:
Thanks very much for offering to help.
I already had the option for the Volume control buttons to wake the phone turned on. It's here - Settings > Buttons > Volume Buttons > Wake up device. This worked for a while then stopped. I disassembled the phone to look at the On/Off button. I tried turning the phone on directly from the metal contact pad beneath the plastic button. This worked. When the phone had booted I checked to see if there was another nightly update for Lineage. There was the 3rd of Dec update. I downloaded and installed the nightly update using TWRP. It reported a successful install. The phone rebooted and never got past the Google boot-up screen. I waited for a few minutes and the took the battery out and tried turning on again from the metal contact pad. The phone booted but again got stuck (or seemed to) on the Google boot-up screen. I'm afraid that's it for me. This doesn't appear to be related to anything I have done or not done. The phone is just taking up too much time and it will have to go the the local recycler. Life is, as they say, too short. Thanks again for your suggestions.
Click to expand...
Click to collapse
3rd dec nightly has problem with booting, get back to older than it.
Reset volume button waker, if it stopped working. I never had problems with volume buttons.

I'd second the idea of it being software. I've had problems with all builds after 20171112. I get the impression there was something overlooked when the developers unified the builds for different GNex variants.
If you still have the phone, try that 20171112 build.

I don't know how to roll back to an earlier build. The phone will not boot. If I try VolumeDown+On/Off to try to get into TWRP Recovery mode nothing happens. The adb bridge option is turned on but if I connect the phone to my PC with a usb cable it does not appear in Device Manager as it used to. If I run ".\adb devices" it is not listed so clearly adb cannot find it. I don't know what else I can do.

erich_vogt said:
The phone will not boot. If I try VolumeDown+On/Off to try to get into TWRP Recovery mode nothing happens. The adb bridge option is turned on but if I connect the phone to my PC with a usb cable it does not appear in Device Manager as it used to. If I run ".\adb devices" it is not listed so clearly adb cannot find it. I don't know what else I can do.
Click to expand...
Click to collapse
Ah, ok. Sorry, I thought you could still do more than that, but it was rebooting and unusable in that sense.
That's well beyond any help I can offer you. I hope you got any data off it.

Screen froze, asked for reboot, now nothing

My wife was typing and the screen froze, she pushed the power button was the reboot or power off box appeared. She selected reboot and the screen went dark and now nothing comes on no matter how long the power button or power + power up or power down is held. I plugged in the charger and the battery icon does not appear. Could the connection from the motherboard to the screen have come loose? It seems strange that it would die coincidentally after requesting a reboot. Another other suggestions before I try to sell it as a paperweight on Ebay?

lmacmil said:
My wife was typing and the screen froze, she pushed the power button was the reboot or power off box appeared. She selected reboot and the screen went dark and now nothing comes on no matter how long the power button or power + power up or power down is held. I plugged in the charger and the battery icon does not appear. Could the connection from the motherboard to the screen have come loose? It seems strange that it would die coincidentally after requesting a reboot. Another other suggestions before I try to sell it as a paperweight on Ebay?
Click to expand...
Click to collapse
It depend on if you had TWRP Recovery installed on your tablet. Was this an original setup device or a custom ROM? If it was custom, you should have the necessary files to reinstall from scratch. If you know you do have TWRP Recovery installed (IIRC, it would not show up as an installed app) then to access it you need to push POWER, HOME button (middle front panel)and VOLUME +(up)at the same time! This will get you into recovery mode. Then, you would have to reinstall your custom ROM and gapps from backups. If you don't have these you may still be able to repair it via a Windows PC connection with the right files.
When you post probs you are having, the more info that you include, the better chance you will get a solution for it. I have three smp600 tabs, all configured the same way with multiple backups for each on SD cards as well as Google Drive cloud. So, I can have any tab restored fully in under an hour. Whatever you do, good luck, but it takes a lot to truly "brick" one! ;-DeanoD=
Sent from my SM-P600 using Tapatalk

Thanks. It was running stock Lollipop with no custom recovery. When I was taking the back off to see if a connection was loose I could hear audio but I did not find a loose connection so it's still dead.?

Xtrons PB7839BP Hal9K PX5 Strange wake up behavior

My Xtrons system running Hal9K 3.2.1 with MCU version MTCE_GS_V3.01_2 is reacting very strange during wake up.
Most of the time it all goes wel. As soon as I turn my car key system wakes up within seconds and runs normally. Even after days of not using my car.
On the other hand, sometimes, system starts up, but now showing the Android and Car logo. This means system did shutdown instead of go to sleep when leaving the car.
But since a couple of weeks I am having a new issue.
As soon as turn the key, all the lights on head unit go on, but screen does not light up.
Pressing the left button on the unit does not do anything.
Only thing that works is pressing the reset button. This morning , even pressing the reset button did not wake up the unit.
After several attempts , reset and power button, finally system woke up and run normally.
Wonder what this problem could be?
Why does the unit one day wake up fine, an other it restarts ? And what could cause the problem that lately i need to use the reset button?

Hi,
I am experiencing a similar issue. As soon as it gets around 0°C the unit does a full reboot. I guess it has something to do with the power supply circuit. I am also running the Hal9k ROM but on a Witson device with a different MCU version.