Database Info

Ultra Power Saving Mode - unusable phone

Hey guys-
Was on a long international flight yesterday and decided to put my (unrooted) Galaxy S6 into "ultra power saving" mode for the first time. It was a horrible mistake and I'm not sure how to undo it!
The first issue it had was that it said Ultra Power Saving mode doesn't support the use of themes, so it was reverting to the default theme (I use Material Black).
After a long time of saying it was reverting to the default theme, I'm not sure if it worked - it ended up in the state that it is currently in: if I turn the phone on, the screen is just black - it has the status bar at the top of the screen, but just a blank black screen below it. It does not look like images I've seen on other websites for what Ultra Power Saving mode is supposed to look like (no icons on the screen, no "More" at the top right). If I go to settings by dragging from the top of the screen and hitting the settings button, I get a very limited set of settings: WiFi, Bluetooth, Airplane Mode, Mobile Networks, Location, Sound, and Brightness - nothing that enables me to turn off Ultra Power Saving mode.
I am afraid to reboot the device, because when I did that yesterday, I had major issues. My device is encrypted, and I think this mode doesn't play nicely with encryption; when I rebooted the device, I was asked to sign in to unlock the encryption (as normal), but then the encryption booting screen (an unlock symbol with a circle around it) just idled indefinitely - for an hour or two. I couldn't do anything to get the phone to actually boot. Eventually, many hours later, rebooting the phone and logging in allowed it to boot to the state I described above; I don't know what went differently that time.
I tried various key combinations on restart, one of which seemed to result in the device trying to boot to Safe Mode (it said safe mode in the bottom left corner when asking me to sign in to device encryption), but ended up leaving me in the exact same place - the extremely limited Ultra Power Saving mode black screen I described above.
Anyway - is there anything I can try to get my phone out of Ultra Power Saving mode and back to normal? It is unusable right now and I can't figure out how to get it back. Would like to avoid a factory reset if possible (because I'm overseas with ****ty internet, and don't have access to my office to get it re-set up with enterprise mail etc.).
If I have to factory reset the device - I'm not even sure how to do it from this current UPSM state, so any tips there would be helpful too.
Thanks a ton in advance for the help guys

Go to download mode, reflash original rom with odin. You need your rom file from sammobile or samsung-updates or xda and odin 3.

Sorry, I am no power user although I am not totally tech incompetent. Can you tell me in a little more detail what your instructions mean? It sounds like it is basically a total reset of the OS; is that right? Any implications for my warranty? Any alternatives?

If you had package disabler and disabled any of the packages required to run ultra power saving mode, you get symptoms like this.
com.sec.android.emergencylauncher is one package amongst many.
I have honestly only heard of factory resetting working.
http://www.hardreset.info/devices/samsung/samsung-g920f-galaxy-s6/

Pulled sim broke screen? Can't do anything

Heu guys,
So I received a P30 as a gift yesterday, it said it had an update so it downloaded. Then it said it needed to be at 20% to install the update so I just left it until later when I could get to a charger. The thing is, I also didn't have a sim card in it.
I pulled the sim slot with the phone turned on (install pending) , and as soon as I did that I got a new black screen of death, nothing like in any of the videos online.
This one allows me to interact with the screen, however the entire screen stays black except for about 50% of the top (like I can see 50% of the battery icon) notification area. The tiny section of the screen that turns on also looks sorta wonky, like screens often do when they get water damage.
I've been able to turn it off, by guessing where the power buttons were. I *think* I even got it to the hard reset menu, but not being able to see, I can't type on the screen. It does react to the soft reset (power + volume down) but when it turns back on, it won't even show the logos on boot, everything still stays black minus a section of the notification bar.
Is there a way to do a hard reset without being able to interact with the screen at all? Can I do it using my computer somehow?
I know the screen is not broken because I can interact with it. Also on 1 of the 30 soft resets I did, the screen flickered some sort of error message for a quarter of a second, so fast all I could do was see it was text.
I'd just return the phone but it was a friend's old work phone and there is no way to get a replacement.

I recommend you to use Hisuite on a computer, try to connect the phone (I said try because you must select the type of connection on the phone). If the phone connects to Hisuite, use the recovery option to reinstall the default firmware. Good luck!

marselcj said:
I recommend you to use Hisuite on a computer, try to connect the phone (I said try because you must select the type of connection on the phone). If the phone connects to Hisuite, use the recovery option to reinstall the default firmware. Good luck!
Click to expand...
Click to collapse
this might be my only option. I was trying to find something just like that. Couldn't figure out if there was a software for it or not. Thanks will try when I get back to a computer tomorrow!

Dropped phone, screen blank now. Need to recover data/wipe phone

Hi all,
I dropped my OnePlus 6 and the screen is completely blank. The device seems to be working(vibrations and screen unlock lock sounds)
I am on Stock OOS with the latest update installed, completely unmodded(bootloader locked, no TWRP installed, no custom ROM)
I thought I had USB debugging enabled but it seems I have not as 'adb devices' says unauthorized.
I need to pull some data from the phone, what are my best options in this case?
I am ready to flash any TWRP/custom recovery to do this.
Biggest problem is screen is completely blank.
Thanks

Did you check whether the touchscreen still reacts to touch input? Although not the easiest solution but you might try to either authorize it by tapping on the screen multiple times or compare screenshots of where it should be to authorize it. The "Allow" button should be a little bit down further from the vertical center and a little bit to the right. You could just tap dozens of times unless you press "Cancel" on the left side.
You could do this with TWRP as well but there is a risk you tap on the wrong parts and maybe wipe your device accidentally.
Unfortunately, the OnePlus 6 doesn't support HDMI outputs and DisplayLink adapters require an app on the device to work.

Macusercom said:
Did you check whether the touchscreen still reacts to touch input. Although not the easiest solution but you might try to either authorize it by tapping on the screen multiple times or compare screenshots of where it should be to authorize it. The "Allow" button should be a little bit down further from the vertical center and a little bit to the right. You could just tap dozens of times unless you press "Cancel" on the left side.
You could do this with TWRP as well but there is a risk you tap on the wrong parts and maybe wipe your device accidentally.
Unfortunately, the OnePlus 6 doesn't support HDMI outputs and DisplayLink adapters require an app on the device to work.
Click to expand...
Click to collapse
@sigma_p As suggested by Macusercom, you have to somehow enable adb. After that you can try
Scrcpy tool to display your phone on your PC and retrieve your data.
https://github.com/Genymobile/scrcpy
Good luck?

Broken screen, with constant phantom touches preventing everything

My phone's screen was broken, so the touch sensor (capacitive) sensing constant phantom touches, which prevents to do anything with it, even with mouse connected on OTG.
I can't connect on ADB, as once i've allowed my PC to always connect to it, yet asks for a confirmation at every connect, which i can't grant, as if i unlock the phone with fingerprint, the phantom fingers instantly tap the dialog away.
I can connect with fastboot, but it's useless.
My next idea is to disconnect the screen ribbon cable (xiaomi "engineers" were so smart that the display and the digitizer are on same cable... which is weird, as redmi 7 had seperate cables and this redmi note 7 have one), and buy an MHL type-c -> HDMI-OTG adapter, and connect it to TV, and the mouse, then i can access my files... however i doubt that it will work
Any tips how to hack it or something? I'm thinking about that it maybe possible to electronically disable, or "burn out" the touch sensor without disconnecting the screen ribbon. Is that possible? Perhaps the cleaning of screen would kill the phantom?

Any help?

I would like to help you but never had to deal with such a problem.
But let's try:
1. What do you want to achieve? Do you want to backup your data?
2. The phantom touches are instantly and do not stop?
3. Don't know if that works, but... Is the mouse connected to OTG always on the same place? Like does it appear on a fix default position on your screen every time you plug it in or does it remember its last position (or is it random)?
If you know that you could maybe try to detach the display and use the mouse to enable your adb connection constantly. And if that works you could use scrcpy (screencopy. Find it on github) to show your devices display on your computer without having to use your real smartphone display.

User699 said:
I would like to help you but never had to deal with such a problem.
But let's try:
1. What do you want to achieve? Do you want to backup your data?
2. The phantom touches are instantly and do not stop?
3. Don't know if that works, but... Is the mouse connected to OTG always on the same place? Like does it appear on a fix default position on your screen every time you plug it in or does it remember its last position (or is it random)?
If you know that you could maybe try to detach the display and use the mouse to enable your adb connection constantly. And if that works you could use scrcpy (screencopy. Find it on github) to show your devices display on your computer without having to use your real smartphone display.
Click to expand...
Click to collapse
Its a quite common problem, however the most people just buy a new phone, and dump the broken one.
I want to backup one application's data particularly, yes.
Phantom touches are constant, always at the menu buttons.
I cant connect otg mouse and to adb at the same time... 1 usb only.
Why cant i just authrnticate myself through adb?

sanyigz said:
I cant connect otg mouse and to adb at the same time... 1 usb only.
Click to expand...
Click to collapse
I'm sorry. Sometimes I don't see the most obvious things..
sanyigz said:
Why cant i just authrnticate myself through adb?
Click to expand...
Click to collapse
I don't know. What exactly happens if you try that?
You connect your phone with your computer and run some adb command (e.g. "adb devices") and then it asks you to authenticate, right?
And then?
Another question which I think you'll answer with "no": Did you unlock your bootloader?

I just cant do it, and didnt fide any help for it on google.
If i connect it, and list the adb devices, i see "unauthorized" and a dialog pops up on the phone to allow adb connection, but as soon as i unlock the phone the dialog goes away as the phantom touching the menu buttons...
No, the bootloader is not unlocked, else if would be able to save with twrp. I can unlock it with fastboot, but it does a factory reset on unlock...

sanyigz said:
No, the bootloader is not unlocked, else if would be able to save with twrp. I can unlock it with fastboot, but it does a factory reset on unlock...
Click to expand...
Click to collapse
Yes, that won't be helpful.
sanyigz said:
If i connect it, and list the adb devices, i see "unauthorized" and a dialog pops up on the phone to allow adb connection, but as soon as i unlock the phone the dialog goes away as the phantom touching the menu buttons...
Click to expand...
Click to collapse
I have another idea. If you refer to the menu buttons you refer to the home, back buttons right? If your phone support it (and phantom touches allow it) you can go to setting -> System -> Gestures -> System navigation -> gesture navigation. Then click on the setting next to "gesture navigation" and turn of navigation hint.
Whatever those phantom touches are touch now – it won't be any of those menu buttons since they disappeared.
Now, hopefully adb authorization works.

User699 said:
Yes, that won't be helpful.
I have another idea. If you refer to the menu buttons you refer to the home, back buttons right? If your phone support it (and phantom touches allow it) you can go to setting -> System -> Gestures -> System navigation -> gesture navigation. Then click on the setting next to "gesture navigation" and turn of navigation hint.
Whatever those phantom touches are touch now – it won't be any of those menu buttons since they disappeared.
Now, hopefully adb authorization works.
Click to expand...
Click to collapse
As i wrote, i cant do anything on UI, as the phantom always touch back to the menu, or to the photo app, which i cant even pull out from quick access due to the phantom.

Having a ghost touch issue, it's probably not a problem with the software, but it's a hardware problem with your display and the way it's housed inside the chassis of your phone. If you're an engineer and happy taking electronic devices apart ( and have all the required specialty tools ), then you might fix the issue by simply disconnecting the screen from its data connectors for a while and then reseating the screen.

jwoegerbauer said:
Having a ghost touch issue, it's probably not a problem with the software, but it's a hardware problem with your display and the way it's housed inside the chassis of your phone. If you're an engineer and happy taking electronic devices apart ( and have all the required specialty tools ), then you might fix the issue by simply disconnecting the screen from its data connectors for a while and then reseating the screen.
Click to expand...
Click to collapse
It's very hard to do anyting on phone anything blindly...

How can I run Pixel 3 without the screen?

I'm attempting to run a google pixel 3 without the physical screen. The phone will be used in remote management, so I have a remote management utility installed on the device as well.
Everything works flawlessly when the screen is installed - all apps and configurations work as they are intended. However, once the screen is removed, the phone doesn't work. On a pixel 3a I was able to attach just a ribbon cable for the screen without the actual screen, and when I pulled it up in airdroid, it would only display a condensed screen about 1/3 the height. On the Pixel 3 it doesn't load up at all.
I've connected the phone to my computer with USB debugging enabled. Without the screen it shows up in the devices list. But with the screen it doesn't even show up in the devices list. The only way to make the phone operational is to remove the battery cable then restart the phone. About 30% of the time it displays a message upon boot "This device failed to boot, do you want to factory reset", with an option of "yes" and "reboot" (selectable through the volume and power buttons).
Also of interesting note, if I power on the phone without the digitizer connected, I can use AirDroid just fine, but it won't register my clicks on the remote view screen. Which leads to believe the phone is registering the hardware of the screen and digitizer upon boot.
If I disconnect the digitizer and LCD after the phone is booted up, I can attach them both and it'll work. It's just when they're disconnected from the phone during the initial boot phase.
I tested this with a Galaxy S8 previously, and that phone worked just fine without the screen attached, and ran fine that way.
Does anyone have any ideas on how to "register" the hardware correctly? I'm not certain that's what's happening, but it appears to be something with the hardware not registering correctly, or something like that. What's odd, is that it doesn't work even with the ribbon cables attached. It requires the full screen to be connected to the ribbon cables.
I've searched up and down google, but there doesn't appear to be much information available on this, as it appears to be a very specific problem which not many people encounter.
Thanks!