When starting/ restarting the phone, it turns on amd tells me to sign in to get app notifications (I have password on boot enabled). However about 15-30 seconds of using the phone (after entering my pin) it reverts back to the boot screen (black with the flashing Samsung logo) and goes back to the 'sign in to get app notifications' and I have to enter the pin again.
It's not a huge issue but was wondering if anyone had come across this or had solved it?
mtm1401 said:
When starting/ restarting the phone, it turns on amd tells me to sign in to get app notifications (I have password on boot enabled). However about 15-30 seconds of using the phone (after entering my pin) it reverts back to the boot screen (black with the flashing Samsung logo) and goes back to the 'sign in to get app notifications' and I have to enter the pin again.
It's not a huge issue but was wondering if anyone had come across this or had solved it?
Click to expand...
Click to collapse
Never had or heard of that before. Sorry not a helpful post.
Sent from my [device_name] using XDA-Developers Legacy app
mtm1401 said:
When starting/ restarting the phone, it turns on amd tells me to sign in to get app notifications (I have password on boot enabled). However about 15-30 seconds of using the phone (after entering my pin) it reverts back to the boot screen (black with the flashing Samsung logo) and goes back to the 'sign in to get app notifications' and I have to enter the pin again.
It's not a huge issue but was wondering if anyone had come across this or had solved it?
Click to expand...
Click to collapse
It has happened to me as well, and I don't have password on boot enabled. Now, everytime I reboot the phone I leave it alone for that 15 seconds until it soft reboots by itself
Related
I have had this happen to me a couple of times:
The phone seems to be working alright, but after I turn the screen off, and then turn it back on again, and i enter the right password, it goes into an infinite loop of refreshing the "Enter password" screen. The only way to stop it is to have the phone do a soft reset, but then i can not see what calls i have missed on it.
Does anyone know why this may be happening?
*bump*
doesn't anyone know?
Just updated to a 4.4 rom on my i337, and whenever I reboot my phone, the screen won't turn off.
It would take hours before something happens that finally overloads it and forces a force close on my apps and then its back to working normal.
The only thing I noticed is that when it does happen, some apps show up in the superuser toast and start working again. Superuser wasn't even on the whole time.
Halp
Sent from my GT-I9505G using xda premium
Goliath27 said:
Just updated to a 4.4 rom on my i337, and whenever I reboot my phone, the screen won't turn off.
It would take hours before something happens that finally overloads it and forces a force close on my apps and then its back to working normal.
The only thing I noticed is that when it does happen, some apps show up in the superuser toast and start working again. Superuser wasn't even on the whole time.
Halp
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
Will it turn off hitting the power button ?
hednik said:
Will it turn off hitting the power button ?
Click to expand...
Click to collapse
Does not turn off when:
-Power button is pressed
-timeout time (no matter how long the time out is set for)
This only happens after a reboot, and will last for either an hour or a few hours.
But, if and when it finally does start working, it happens after some weird force close of one of the apps.
Currently, it is working fine after a few reboots and uninstalling Dynamic Notifications. It seems to me that when I disabled Dynamic Notifications, the app would still act as the lock screen. I had to actually remove it completely and so far after a few reboots it hasn't reoccurred.
Phone: SGH-I337 (AT&T S4)
I'm trying to target the cause of my elongated boot time. I'm on 4.3 and unrooted. My phone has the longest startup time ever. It used to be fast and I haven't done anything out of the ordinary to have probably caused the issue. It boots normally, but then when the att logo appears, it does the little animation but then vibrates once slightly, then usually follows another slight vibrate some seconds later. This usually occurs for about 45 seconds to a minute until my lockscreen appears. I factory reset, and I tried powering off and on right after the reset. It was back to normal. However after I downloaded all my apps again and reinstated my settings, the problem reappeared. Is it simply because of the number of apps I have? I don't remember this happening before the update to 4.3. (it was great on 4.2). I thought it was because I had downloaded and used zooper widget, but I uninstalled that app and tried the booting. It was the same duration (1 minute on att screen)
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Been using the S8 Unlocked model SM-G950U1 (stock, not rooted) for the past 4 months without any major problems. A few weeks ago I decided to enable the Secure Boot feature, so that if the phone was powered off and back on, that it would require drawing the password pattern. Haven't had any problem, until tonight.
Since my phone hasn't been rebooted in about a week (which I like to do), I did a reboot, and drew the password pattern, the unlock icon is show with the green & blue circle around it, but then it just stays like this and never gets to the "android is starting, or phone is starting" screen.
I've gone into the boot menu and did a Clear Cache & Reboot, drew password pattern, and then let it sit for 30 min.
I also did a Safe Mode Boot, where it showed "Safe Mode" in the bottom left corner on the same screen where I draw the password pattern, but then it stays at the unlocking icon.
At this point I'm not sure what to do, as I really don't want to do a full factory reset in the boot menu, or do an ODIN wipe, and loose everything.
After trying to get it to properly boot for about 2 hours and trying different things, I ended up going into the boot menu and doing a factor reset. Then took several hours to get the phone all set back up again.
I had thought that when I backup the phone via Samsung Cloud, part of that is for Apps, and I thought it would be the apps and app data (similar to using Titanium Backup). But I guess not, as when I did the restore through Samsung Cloud, it only restores the app programs and not the data.
Thanks for stopping by,
I've had this issue a few times now where I'd restart the phone and would be stuck on the "pixel is starting" message for hours and while googling could only find a factory reset would fix the issue. So instead of resetting for the forth time I figured what do I have to lose if I had to reset anyway. Finally got it to start up without a reset. Here's what I did.
1.reboot into twrp
2.advanced>fix recovery boot loop>reboot
3.reboot back into twrp>flash magisk
4.profit!
Hope this helps anyone that runs into this.
I've always been able to three finger salute it and it boots up. Shouldn't ever take more than a minute or two.
Sent from my Pixel 2 using Tapatalk
Update:
Was able to reproduce the never ending pixel is starting.
Turns out it was the fingerprint unlock after reboot tweak I use.
Turned it off and issue is fixed. Turned on the issue returns.
Think it may have to do with the encryption after fp are entered.
Really enjoyed not having to enter a pin on start up. I can live without it though.
I flashed Magisk without TWRP and I was stuck on the "Pixel is Starting" on my Pixel 3. I found this thread.
I turned my screen off, let it sit for a minute, then turned it back on and it said it needed to be unlocked. I did it again, then used my Fingerprint to activate the "unlock" screen you see after a fresh reboot.
It let me put in a pattern and opened fine.
So yeah I think it does have to do with encryption \ Fingerprint but it looks like that way just let me beat it -- hope that works for someone.