Running latest pie update phone started shutting of yesterday when the screen is turned off. Anyone else having this issue?
No micro SD in it and I've done a factory reset.
ickna11 said:
Running latest pie update phone started shutting of yesterday when the screen is turned off. Anyone else having this issue?
No micro SD in it and I've done a factory reset.
Click to expand...
Click to collapse
I suggest u reinstall the frimware again without ur user data in it! Let it be a fresh installation u can back ur data on SMART WHICH but don't restore yet till u observe the fone closely
ickna11 said:
Running latest pie update phone started shutting of yesterday when the screen is turned off. Anyone else having this issue?
No micro SD in it and I've done a factory reset.
Click to expand...
Click to collapse
Same here. After a factory reset, for me, it's a little better, but there are certain things that I can't do. For instance, if I try to register my finger prints or change my pin, it shuts down.
I also noticed that the Samsung+ app doesn't work. I get a red screen and an exception error when I launch it.
Related
I'll go short about the issue I've been facing since past week.
Ever since I get call, when the screen is locked, screen would just remained off. It's like my phone is ringing and vibrating with turned off screen. To wake up to see who's calling I need to press the power button and then the screem would lit up. Or else the screen would stay turned off till the call ends. Any idea whats wrong?
Also I'm stock JB 4.1.1 no root no nothing.
Cheers!
Thank you,
Blue3125
via HTC Sense
You have bootloader unlocked? If yes, did you install ROMs before? If yes, then you maybe need a clean reinstall. Otherwise you may have a hardware issue, claim warranty then. Instead you can always try wiping cache and dalvik cache.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Blue3125 said:
I'll go short about the issue I've been facing since past week.
Ever since I get call, when the screen is locked, screen would just remained off. It's like my phone is ringing and vibrating with turned off screen. To wake up to see who's calling I need to press the power button and then the screem would lit up. Or else the screen would stay turned off till the call ends. Any idea whats wrong?
Also I'm stock JB 4.1.1 no root no nothing.
Cheers!
Thank you,
Blue3125
via HTC Sense
Click to expand...
Click to collapse
Already said no bootloader unlocked no root no roms no mods no nothing,its 100% stock..
You didn't mentioned if you restarted or/and restore to factory defaults.
If not, do it first (of course after you backup your data).
MoshPuiu said:
You didn't mentioned if you restarted or/and restore to factory defaults.
If not, do it first (of course after you backup your data).
Click to expand...
Click to collapse
Ya I restart my device like once everyday cause it gradually turns laggy if it isnt restarted and yes factory reset doesnt helps
Hey guys.
Had some trouble on my Z2 and thought I'd create an account here and ask for your advice before I did something stupid. Have no experience with rooting or modding whatsoever, so bear with me please.
I bought a Z2 whose screen never slept. I found out that the responsible was com.sonyericsson.startupflagservice v2, who would always run when I turned the phone on and remained on my notification area with no text, just an icon resembling two blue screens superposed. If I force stopped the process, the phone would sleep normally until I powered it off. When I turned it on, the process would be there again preventing sleep.
I did some research and learned how to flash a different ROM, wipe cache, wipe dalvik... Did all that and the process would still be there. Rooted my phone, bought Titanium Backup and froze the process... it worked fine, but would I reset to factory settings, there was the process again.
And finally I come to my question: would un-installing the process and wiping its data with Titanium backup work? Would I be at risk of bricking my phone?
I'm running out of options on what to do and returning isn't really an option!
Thank you very much!
Phone: Xperia Z2 D6503
Android v: 4.4.2
Build number: 17.1.2.A.0.314
Please let me know if there is any other info I can provide you with in order to find a solution. Thanks again!
busseto said:
Hey guys.
Had some trouble on my Z2 and thought I'd create an account here and ask for your advice before I did something stupid. Have no experience with rooting or modding whatsoever, so bear with me please.
I bought a Z2 whose screen never slept. I found out that the responsible was com.sonyericsson.startupflagservice v2, who would always run when I turned the phone on and remained on my notification area with no text, just an icon resembling two blue screens superposed. If I force stopped the process, the phone would sleep normally until I powered it off. When I turned it on, the process would be there again preventing sleep.
I did some research and learned how to flash a different ROM, wipe cache, wipe dalvik... Did all that and the process would still be there. Rooted my phone, bought Titanium Backup and froze the process... it worked fine, but would I reset to factory settings, there was the process again.
And finally I come to my question: would un-installing the process and wiping its data with Titanium backup work? Would I be at risk of bricking my phone?
I'm running out of options on what to do and returning isn't really an option!
Thank you very much!
Phone: Xperia Z2 D6503
Android v: 4.4.2
Build number: 17.1.2.A.0.314
Please let me know if there is any other info I can provide you with in order to find a solution. Thanks again!
Click to expand...
Click to collapse
Interesting questions... I've also experienced this.
After about 30 mn of waiting, startupflagservice had finished its job (I don't know what it is doing).
Anyway, I don't recommend to uninstall it.
See if flashing the .402 FTF solves this? Maybe it is a random bug in the .314 firmware. I haven't got this process running so I can't comment on it. Have you got power saving features enabled? If so, is the battery drain still bad with the process running?
I know I am asking a lot of questions but there are multiple things that could be causing the issue. When you factory reset the stock ROM, does it occur after you have installed apps or before? There could be a rogue app keeping the phone awake. Install either:
Betterbatterystats (https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats)
Wakelock detector (https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector)
Hopefully either app should give you a better insight as to what is keeping your phone from deep sleep.
EDIT: Also, according to quite a few lists, that particular thing (com.sonyericsson.startupflagservice v2) is safe to delete. If you are rooted and have a custom recovery, make a nandroid backup (ask if you don't know what it is or how to do so) and then go ahead and delete it using ES file explorer. Worst case scenario your phone reboots/gets stuck in a bootloop or something and you can just restore the nandroid.
Thanks for the replies, guys!
I'll try flashing the .402 FTF next weekend. Unfortunately, I don't have much time to tinker with the phone on weekdays anymore. I have reasons to believe the current firmware is not the responsible though, as this problem occurred on the firmware that came on the phone (don't remember which one it was), and continued after I updated to .314 through the PC Companion.
Answering your questions, Devzz:
I have no power saving features enabled.
I haven't noticed any battery drain, as I didn't allow it to happen... I usually turned the screen off with the power button, which worked... the only problem was the phone not sleeping by itself after the inactivity period I set.
The problem occurs right after I turn the phone on. As soon as I turn it on after a reset and every time thereafter, I'm greeted by a black screen with a big black button that reads: POWER OFF. If I click it, nothing happens. When I press Back or Home, I'm on my home screen with the icon I mentioned on my original post on the notification bar.
I'm starting to think I just had bad luck and got a defective piece of hardware. There's another problem now that didn't happen before the update: the volume of the notifications now is always low, regardless of how much I set on the slider on Settings > Sound > Volumes. I've noticed some people had this problem as well, and I could temporarily fix it by enabling Dynamic normalizer and xLoud on the Sound Effects, although that is hardly an ideal solution.
Thanks very much again for your help! I'll look into the nandroid backup and try that next weekend.
P.s.: another piece of information that I haven't mentioned and may be relevant: I was never able to access recovery mode, despite my efforts to do so. I had to install XZDualRecovery to be able to boot into recovery mode.
busseto said:
Thanks for the replies, guys!
I'll try flashing the .402 FTF next weekend. Unfortunately, I don't have much time to tinker with the phone on weekdays anymore. I have reasons to believe the current firmware is not the responsible though, as this problem occurred on the firmware that came on the phone (don't remember which one it was), and continued after I updated to .314 through the PC Companion.
Answering your questions, Devzz:
I have no power saving features enabled.
I haven't noticed any battery drain, as I didn't allow it to happen... I usually turned the screen off with the power button, which worked... the only problem was the phone not sleeping by itself after the inactivity period I set.
The problem occurs right after I turn the phone on. As soon as I turn it on after a reset and every time thereafter, I'm greeted by a black screen with a big black button that reads: POWER OFF. If I click it, nothing happens. When I press Back or Home, I'm on my home screen with the icon I mentioned on my original post on the notification bar.
I'm starting to think I just had bad luck and got a defective piece of hardware. There's another problem now that didn't happen before the update: the volume of the notifications now is always low, regardless of how much I set on the slider on Settings > Sound > Volumes. I've noticed some people had this problem as well, and I could temporarily fix it by enabling Dynamic normalizer and xLoud on the Sound Effects, although that is hardly an ideal solution.
Thanks very much again for your help! I'll look into the nandroid backup and try that next weekend.
P.s.: another piece of information that I haven't mentioned and may be relevant: I was never able to access recovery mode, despite my efforts to do so. I had to install XZDualRecovery to be able to boot into recovery mode.
Click to expand...
Click to collapse
I have the exact same problems with my phone not going to sleep and the big "power off" button. What the heck does it mean? Anyone fix this problem yet?
matase said:
I have the exact same problems with my phone not going to sleep and the big "power off" button. What the heck does it mean? Anyone fix this problem yet?
Click to expand...
Click to collapse
In spite of my efforts, I couldn't find a way to get rid of the problem. Currently I have the phone rooted, installed Titanium Backup and deleted the files related to the process.
It's working, although if I ever revert to factory settings, the problem will be there again.
Best of luck to you and please let me know if you find a fix.
busseto said:
In spite of my efforts, I couldn't find a way to get rid of the problem. Currently I have the phone rooted, installed Titanium Backup and deleted the files related to the process.
It's working, although if I ever revert to factory settings, the problem will be there again.
Best of luck to you and please let me know if you find a fix.
Click to expand...
Click to collapse
Which process/es did you exactly delete? What are those files for the process are even doing? When did this problem start for you? Thanks
On mine that service displayed a persistent notification and on every reboot it prompted to power off or use phone. Anyway, as soon as I saw that I rooted and froze com.sonyericsson.startupflagservice in titanium backup. Problem solved! As far as I've tried it's not essential and can be uninstalled as well. I really don't get how they overlooked this, it's a huge annoyance for anyone that can't root the phone I imagine.
Solution!!!!!
I had the same issue on a Z2 I bought off a guy. It was on 4.4.2 and it kept saying no update available. I downloaded and flashed the 5.0.2 update via Sony Flashtool. At first boot the issue appear again after a few seconds. It got very intense with the screen becoming unusable. The phone shut itself down and rebooted without the issue. Gone and nowhere to be found. I immediately got another prompt to update to a newer Android version - same 5.0.2 (17MB file).
So flash away, guys!!!
Hi,
I'm looking for some general advice and troubleshooting for my phone's issues. My phone started crashing very often, sometimes at complete random, as well as when I was using it fairly heavily (any app that froze my phone for a second before loading before the crashing would now crash my phone). Sometimes it would reboot fine, other times it would bootloop once or twice before reloading fine. I previously tried doing a factory reset, removing my external microSD card, and updating everything via Kies and nothing worked.
I got bored and rooted my phone, did a full wipe, and flashed the latest Infamous update. The problem was still there but it wouldn't crash as often while using it because my phone could handle higher app activity but it's still there. Oddly enough, after flashing Infamous, it often fails to reboot and so I have to do a battery pull before turning it back on, otherwise it won't even vibrate after holding the power button.
I'm just wondering if you guys have any idea what the issue could be. Is it likely still something I can fix? Is this potentially a battery issue or is it a hardware issue?
Thanks so much!
jasonale said:
Hi,
I'm looking for some general advice and troubleshooting for my phone's issues. My phone started crashing very often, sometimes at complete random, as well as when I was using it fairly heavily (any app that froze my phone for a second before loading before the crashing would now crash my phone). Sometimes it would reboot fine, other times it would bootloop once or twice before reloading fine. I previously tried doing a factory reset, removing my external microSD card, and updating everything via Kies and nothing worked.
I got bored and rooted my phone, did a full wipe, and flashed the latest Infamous update. The problem was still there but it wouldn't crash as often while using it because my phone could handle higher app activity but it's still there. Oddly enough, after flashing Infamous, it often fails to reboot and so I have to do a battery pull before turning it back on, otherwise it won't even vibrate after holding the power button.
I'm just wondering if you guys have any idea what the issue could be. Is it likely still something I can fix? Is this potentially a battery issue or is it a hardware issue?
Thanks so much!
Click to expand...
Click to collapse
So when your phone have become unstable , in what condition it was ? did you ever flash it before ... so my s2x did the same thing afer a update with odin on 4.2 ... so i have reflashed it and evrything was working good after
After some minor bug I have decided to master reset my phone after wiping all data and stuff the phone was running cool but since yesterday when I lock the screen 1-2min after the phone freeze and restart after. When I am using it no problem whether is plugged to charge or not.
It’s only reboot or freeze when you lock the screen or stop using the phone
I need help
Silverpat said:
After some minor bug I have decided to master reset my phone after wiping all data and stuff the phone was running cool but since yesterday when I lock the screen 1-2min after the phone freeze and restart after. When I am using it no problem whether is plugged to charge or not.
It’s only reboot or freeze when you lock the screen or stop using the phone
I need help
Click to expand...
Click to collapse
Are you Running a Custom ROM?
If yes you should go into your ROM's thread .
If you are running stock Android , the problem comes from the OEM , you should search for this issue on internet to find someone else who faced this bug and try to know if there's a fix.
On my side , I can't do much because I don't own your device and I never heard about this before
I hope you'll find the answer on the internet
S22+ on Verizon (Locked). I’ve had the phone since launch with no major issues. I received the March update on Friday the 18th. Since then, I have lost my network at least once every day. I get the message “Your phone’s not registered on a network so you can only make emergency calls.” Restarting or toggling Airplane mode on and off will correct it temporarily. I’ve gone into Settings>General Management>Reset, and reset the network settings, but that hasn’t corrected the problem. Anyone else with this issue? What else can I try?
bilbo60 said:
S22+ on Verizon (Locked). I’ve had the phone since launch with no major issues. I received the March update on Friday the 18th. Since then, I have lost my network at least once every day. I get the message “Your phone’s not registered on a network so you can only make emergency calls.” Restarting or toggling Airplane mode on and off will correct it temporarily. I’ve gone into Settings>General Management>Reset, and reset the network settings, but that hasn’t corrected the problem. Anyone else with this issue? What else can I try?
Click to expand...
Click to collapse
Have you tried a factory reset? That's usually recommended after each update
The only time I do that is after an Android version update. The phone is only a month old, and this is the first update. I will if nothing else works.
So every month when you get a security update you do a factory reset and set up your phone again, reinstalling your apps?
never heard of that issue, normally you wouldn't factory reset after a security update. maybe try clearing cache in recovery mode?
bilbo60 said:
S22+ on Verizon (Locked). I’ve had the phone since launch with no major issues. I received the March update on Friday the 18th. Since then, I have lost my network at least once every day. I get the message “Your phone’s not registered on a network so you can only make emergency calls.” Restarting or toggling Airplane mode on and off will correct it temporarily. I’ve gone into Settings>General Management>Reset, and reset the network settings, but that hasn’t corrected the problem. Anyone else with this issue? What else can I try?
Click to expand...
Click to collapse
try to download last stock firmware and flash from odin
Fytdyh said:
Have you tried a factory reset? That's usually recommended after each update
Click to expand...
Click to collapse
Just a regular restart is enough after an update why do we have to factory reset each time??
Maskman_101 said:
Just a regular restart is enough after an update why do we have to factory reset each time??
Click to expand...
Click to collapse
If I find my device behaving in a weird way after any type of update, I usually just factory reset said device. Now, for starters, I do have a micro sd, on which I store all my data. So, instead of wasting time trying to find out the culprit app/update, I hit factory reset. Cleans up everything I don't need, frees more space and the time required to reinstall all my apps is just around 5 minutes. For example, I had this phone for 2 years and had 10 factory resets so far.
have you contacted your carrier yet? if your phone keeps showing 'not registered' error message then it's likely that SIM should be replaced or the carrier side made some sort of error from their end and keeps dropping your phone from being recognized as registered.
I've seen one case that the phone was not listed as US device during an update and pretty much de-registered some people's phones. Random stupid things do happen
I think I might have fixed it by deleting system cache. Also did a forced restart. It is an intermittent problem.
Fytdyh said:
If I find my device behaving in a weird way after any type of update, I usually just factory reset said device. Now, for starters, I do have a micro sd, on which I store all my data. So, instead of wasting time trying to find out the culprit app/update, I hit factory reset. Cleans up everything I don't need, frees more space and the time required to reinstall all my apps is just around 5 minutes. For example, I had this phone for 2 years and had 10 factory resets so far.
Click to expand...
Click to collapse
For me, just a restart is enough to make my phone better to use and I do it weekly once!
Maskman_101 said:
For me, just a restart is enough to make my phone better to use and I do it weekly once!
Click to expand...
Click to collapse
So you actually keep the phone 24/24 powered on? I turn off mine every night.
I leave my phone on always. Usually restart once a week.
Issue returned. It is just so random. I cleaned and reseated the SIM card. If I get time I will visit the Verizon store tomorrow.
I would think it's something software issue that samsung engineers need to look into.
If you haven't already, submit error report after seeing the issue again.
Samsung members app > get help > error report
Thanks, I will do that.