Hi
I got my new S7 today and was looking at the settings, noticed a new condensed display setting which I enabled, the phone said it needed to reboot so I hit reboot.
Now for last 5 minutes is just sitting there either stuck or processing? The blue light is dimming on and off, otherwise no sign of anything.
Is it normal to wait for the change or has something gone wrong?
This is on a out of the box setup, no TWRP, root, custom rom etc.
After an hour I used the hard reset feature (vol down + power button), it rebooted successfully, shows condensed selected but the DPI didnt actually change.
Not a major issue assuming i can still change UI via xposed.
Related
ok im getting mad with this -.- i cant turn off my tablet, when i touch "TURN OFF" it automatically reboot the system.
my tab has 4.2.2
guys do you have any information about this??
thank you all!!
jfedealvarez said:
ok im getting mad with this -.- i cant turn off my tablet, when i touch "TURN OFF" it automatically reboot the system.
my tab has 4.2.2
guys do you have any information about this??
thank you all!!
Click to expand...
Click to collapse
What ROM are you using?
If you want to manually shut down the tablet, press power and volume up while plugged into a power source. It shouldn't power back on.
-RespawnedEvil
Samsung reboots
RespawnedEvil said:
What ROM are you using?
If you want to manually shut down the tablet, press power and volume up while plugged into a power source. It shouldn't power back on.
-RespawnedEvil
Click to expand...
Click to collapse
I am experiencing the same problem with reboot. I updated Tab 2 (PS5113) to 4.2.2 rom through the automatic update via WIFI (on Aug 30,2013). When you turn off normally, the screen shuts down (glows for about 15 sec before full black) then turns back on. Generally the second time I turn it off (in a row) it will turn fully off. I have tried turning off with or w/o connection to WIFI, and tried turning off all programs through applications manager (as well as clearing ram) first. One suggestion was to clear cache partition (hold down power on and volume down button) but this resulted in a quick error message (android logo lying down with X through it), so I am not sure that the cache was cleared. Since I never tried to clear cache before upgrade, I don't know if it is an isue with this upgrade.
Thanks in advance for any help.
It seems as though the OTA update was installed incorrectly. Perhaps a file is corrupt or you have an app installed that is causing an issue with the shutdown process. Is your install rooted? I would recommend either performing a factory restore, or re-flash your devices firmware with ODIN (Use with caution!) Either way, please post your intentions. Have you tried anything other than clearing your cache? Did you recently install an application? Let me know
Best of luck,
-RespawnedEvil
SamsungTab2User said:
I am experiencing the same problem with reboot. I updated Tab 2 (PS5113) to 4.2.2 rom through the automatic update via WIFI (on Aug 30,2013). When you turn off normally, the screen shuts down (glows for about 15 sec before full black) then turns back on. Generally the second time I turn it off (in a row) it will turn fully off. I have tried turning off with or w/o connection to WIFI, and tried turning off all programs through applications manager (as well as clearing ram) first. One suggestion was to clear cache partition (hold down power on and volume down button) but this resulted in a quick error message (android logo lying down with X through it), so I am not sure that the cache was cleared. Since I never tried to clear cache before upgrade, I don't know if it is an isue with this upgrade.
Thanks in advance for any help.
Click to expand...
Click to collapse
In the morning, I have experienced the same thing, I use the cm-10.1.3-RC2-p5110.zip
I had to shut down twice.
Rebooting
My device is not rooted (purchased in March). The update was through the Samsung notification - automatic (except for saying proceed). The update went smoothly - no error messages. However, after update, the Nook app would not open so I uninstalled the original and reinstalled through Google Play. In addition, the home page was changed, Samsung putting back on the Media Hub and removing all of my personal folders - icons (very irritating). The standard weather app and calendar widgets were larger than original after update (pushing the calendar off into page 2), so I removed and added the G0 Weather app (I have since removed it to see if the Tab will shut off - it still needs 2 shut downs. As I mentioned before, after the first shut down, the tablet keeps a slight glow for about 20 sec., then goes black, then immediately restarts (as if during the glow something is happening??). On 2nd shutdown, glow is for 5 sec. then off complete.
I prefer not to root (yet) but am uncertain how to proceed with factory restore if I have updated through Samsung. Might it not just reload a faulty OS? As I mentioned, wiping the cache did not seem to work.
Thanks again.
I just made a bunch of mods and now I'm having trouble getting the screen to turn on. Here's what I did:
1) Unlock boot loader (Used Android Toolkit)
2) Root (Same kit as above)
3) TWRP (Same as above)
4) Installed center clock mod (This one)
5) Installed smaller DPI nav bar (This one)
6) Installed 4-in-1 reboot (This one)
After all were finished, once my screen turns off, I see it kind of light up again (though still blank) and if you press the power button, the lock screen flashes on for a moment and then automatically shut off again. All the way off. A brief moment later, I seen the screen come back on but blank.
I read there was a possible compatibility issue between the center clock and small DPI mods so I removed them. Still have the issue. I can't see how the 4-in-1 could affect the screen.
Any ideas? I search but couldn't find anything close to the issue.
Thanks
Here's a video. Hopefully the screen off but really on glow comes thru the vid.
I had too many issues so wiped back to stock.
The toolkit has a few bugs.
The center clock and small DPI nav bar apps had compatibility issues.
I was not able to revert back to stock with the 4-in-1 app.
Apparently there are still some issues with the toolkit ver 1.1. From my little investigating, I think there's a simple typo in the programming and it's looking for an older version of SuperSU (1.65 vs 1.69).
I'm back to stock, unlocked and rooted. Screen/display works.
I have no idea what broke or how it broke but it's back to normal now.
Turns out my issue was with Light Flow. Not sure on the exact steps to get this to happen. But after 2 wipes and one rebuild without any restoring, I can get the issue to duplicate.
I personally believe it has something to to with being rooted and having the app use rooted options.
Ok. So 14 days ago my wife and I both got S6's for Verizon from a local big box store. (yes, 14. Today is the last day I have to take it back.)
We took the OTA to OE2 and I was able to root both phones with PingPong. Everything was fine until yesterday. Her phone wasn't responding when a call was coming in, so she restarted it by holding in the power button. Now, when it boots up it goes to a black screen after showing the initial "Samsung Galaxy S6" screen. Nothing changes. There is a teal/blue pulsing LED that doesn't go away.
I can enter the recovery and wipe cache, factory reset, safemode, etc. I've tried all of those many times. I can enter download mode and use Odin 3.10.6 to reflash OE2 and it says "Pass". After rebooting, it goes to the "Android is upgrading" dialog and goes through and updates about 248 apps, and then changes to read "Starting apps." It won't go past that screen. I left it on that from 10pm last night until 6am this morning with no change. The battery eventually went dead (from 100%). I've tried Odin many times, and it passes every time.
What are my options? When booting, the padlock is unlocked and says "Custom". I'd really like to get rid of that so I can return it to today without problems. When in Download mode, the system status says "custom".
Please help!!
I've also tried using SmartSwitch on the PC, and it doesn't detect the phone.
Update: I'm trying an Emergency Recovery with Smart Switch. It's at 52% right now. I got a serial number from another S6 so it would allow the download/recovery process to start. It's kind of ridiculous you can't get the serial number for your device from anywhere but the settings page on the phone. (Note: not the IMEI, the actual SN). It's not on the box or back of the phone.
Ok, another update. Emergency Recovery didn't work. It finished, and said that it was successful, but didn't fix the issue.
I took the phone back to the place of purchase and they tried about everything that I had already tried. They ended up just replacing the phone. They said that they never saw this issue before.
I have almost an identical issue except I have not roOted or installed any custom ROMs everything is stock . The fingerprint scanner quit working today and said it required a restart, when I restarted the phone I'm experiencing exactly what you are a black screen and a blue pulsing light. In the stock recovery screen I've tried booting to safe mode USB debugging everything except the factory restore yet I think that is my last resort.
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/
It's late and this literally just happened, and as such I won't really get to dig into it until after work tomorrow however:
Got home from a trivia night with friends, relaxing before bed, rebooted my phone to clear out some junk and re-ran the BAT file for Andromeda.
Loaded up a dark theme, https://play.google.com/store/apps/details?id=com.therealbigjake.darkorange for reference, and screen went black.
Hit the power button / fingerprint sensor and I felt haptic feedback. Held down the power button and got a power / reboot screen. I either tapped outside or hit the power button again, received a black screen. Did the power button again and this time it flashed between the power / reboot prompt and the "Factory Reset" swirl.
Currently phone boots to a Android Recovery screen (will not actually boot, I have yet to choose the factory reset option).
Additional info - Non rooted Pixel XL, Windows 10 pro.
I'll add more info later, but wanted to put a warning out there. Not sure what happened and I have not tweaked or modded the phone at all prior to this.
lc3necro said:
It's late and this literally just happened, and as such I won't really get to dig into it until after work tomorrow however:
Got home from a trivia night with friends, relaxing before bed, rebooted my phone to clear out some junk and re-ran the BAT file for Andromeda.
Loaded up a dark theme, https://play.google.com/store/apps/details?id=com.therealbigjake.darkorange for reference, and screen went black.
Hit the power button / fingerprint sensor and I felt haptic feedback. Held down the power button and got a power / reboot screen. I either tapped outside or hit the power button again, received a black screen. Did the power button again and this time it flashed between the power / reboot prompt and the "Factory Reset" swirl.
Currently phone boots to a Android Recovery screen (will not actually boot, I have yet to choose the factory reset option).
Additional info - Non rooted Pixel XL, Windows 10 pro.
I'll add more info later, but wanted to put a warning out there. Not sure what happened and I have not tweaked or modded the phone at all prior to this.
Click to expand...
Click to collapse
Themes not updated for Android O, will crash the phone. Happened to me and a few others yesterday.
There's only like 1 or 2 themes out there that are Android O ready, so read the theme's description before installing it.
lc3necro said:
It's late and this literally just happened, and as such I won't really get to dig into it until after work tomorrow however:
Got home from a trivia night with friends, relaxing before bed, rebooted my phone to clear out some junk and re-ran the BAT file for Andromeda.
Loaded up a dark theme, https://play.google.com/store/apps/details?id=com.therealbigjake.darkorange for reference, and screen went black.
Hit the power button / fingerprint sensor and I felt haptic feedback. Held down the power button and got a power / reboot screen. I either tapped outside or hit the power button again, received a black screen. Did the power button again and this time it flashed between the power / reboot prompt and the "Factory Reset" swirl.
Currently phone boots to a Android Recovery screen (will not actually boot, I have yet to choose the factory reset option).
Additional info - Non rooted Pixel XL, Windows 10 pro.
I'll add more info later, but wanted to put a warning out there. Not sure what happened and I have not tweaked or modded the phone at all prior to this.
Click to expand...
Click to collapse
This happened to me as well with DNA Project:
https://play.google.com/store/apps/details?id=com.xdnax.apps.dnadarkproject&hl=en
They have since updated the play store details to include "Does not support Android Oreo"
Go ahead and check out this thread for "safe" options
I actually had this happen the other day while using Onyx, which says it supports Oreo.
Not sure what caused it, but it was while applying system.ui overlays.
I caused this to happen to me by flashing the legacy removal ZIP in TWRP, because I wanted to make sure I removed all remnants. Omfg I'm so pissed right now. I was using Substratum on Oreo (Pixel XL) with Swift Dark Substratum Theme +Oreo & Samsung theme.
I shouldn't have done that...besides one crash in Facebook, everything was fine after disabling the theme. My Pixel 2 XL will be here in 12 days...I don't want to go through setting up this phone all over again :''(
happened to me last night. Lost a lot of priceless photos. Substratum should not install overlays which are not supported on the device.
---------- Post added at 03:12 AM ---------- Previous post was at 03:09 AM ----------
also there must be something to disable the overlays while in recovery. the rescue zip should be made on sd card + it must be flashable through stock recovery for people without root /andromeda users. We pay money for the app and if this is what it does then theaming will not be a really a thing lot of people would like to do.