Hi Guys
Not sure what is going on but my Note 10 restarts randomly. Funny part is that it is not a full restart that I have to insert my sim pin again, I am using an uptime app and that does not register a restart when this happen.
I will see the carrier splash screen and then I must enter the phone unlock code before the finger print and facial recognition works again. This happens randomly in any app or screen.
I have done the below already but nothing fixed it
Cleared the cache
reset all setting
reset permissions
full factory reset
Have any of you experienced this?
Thanks in advance
There is an option to schedule periodic restarts when the phone is idle, but it doesn't sound as though that's what's happening here (for one thing, scheduled restarts don't occur if you've set a sim PIN).
So your phone is crashing, due to either a hardware or software problem. If you've done a factory reset to no avail, then it's not a software problem unless you've re-loaded the problematic software or settings. The only thing I can think of that could destabilize the system is use of a package disabler or other aggressive "debloating" techniques. If you're not doing anything like that, I'd suspect defective hardware.
Related
Sometimes I unlock my phone and the screen remains black, then the phone reboots but weirdly it doesn't ask for the SIM pin number. Other times I notice the phone reboots by itself and I notice it because obviously the screen lights up during the boot animation. This happens very rarely, so far it has happened about 3 to 5 times in a couple of months but it's still mega annoying when it happens.
Does it happen only to me? Is there any way to troubleshoot this issue?
MarkMRL said:
Sometimes I unlock my phone and the screen remains black, then the phone reboots but weirdly it doesn't ask for the SIM pin number. Other times I notice the phone reboots by itself and I notice it because obviously the screen lights up during the boot animation. This happens very rarely, so far it has happened about 3 to 5 times in a couple of months but it's still mega annoying when it happens.
Does it happen only to me? Is there any way to troubleshoot this issue?
Click to expand...
Click to collapse
If you provide some logs then maybe someone can see what is happening....
Or even basic information, like the configuration and setup of your device.
Right, forgot my configuration. I have an unbranded Z3 on latest Lollipop (but I recall I had a reboot also on Kitkat), no root, no weird apps like task killers or antivirus or anything like that. Sometimes it just does a reboot by itself, but doesn't ask for pin number so it's not a full reboot.
How do I provide logs again?
Info
MarkMRL said:
Right, forgot my configuration. I have an unbranded Z3 on latest Lollipop (but I recall I had a reboot also on Kitkat), no root, no weird apps like task killers or antivirus or anything like that. Sometimes it just does a reboot by itself, but doesn't ask for pin number so it's not a full reboot.
How do I provide logs again?
Click to expand...
Click to collapse
Factory Reset can solve ur problem /based on personal experience
I did that already less than two months ago and I refuse to believe I have to factory reset this thing every month to get stable operation. Also I'm not even rooted and I haven't messed with the system itself so why would I need to factory reset? Factory reset implies that there is something that has changed and needs to be re-set, and I haven't changed anything special that would require such a drastic solution. Not having done anything special, the issue would come back sooner or later if I don't spot the real cause.
Anyway, in diagnostics I have 21 application incidents for systemUI... Could it be caused by a bugged theme? Does this happen to anyone else?
Today I had two and I had another one last week. A off these were weird half reboots like I described above. I only noticed one because I was at my desk and the phone lighted up for the boot animation.
These reboots show up in diagnostics (phone info menu) as system events. Can you please check out if you have any system events and post here? I want to know if this is a widespread problem. Post here if you have any and also if you have a solution or way to troubleshoot.
Nobody at all? Really?
I've been having problems with device Encryption and the external storage not mounting, but I recently noticed that after enabling Secure Startup on my Galaxy S7 Edge running 6.0.1 for Verizon and left at this screen for longer than a minute without touching it, a clicking sound as if you were pressing buttons or entering the pattern can be heard. It's continuous and clicks every other second. I Reset All Settings, Reset Network Settings and even applied updates as well as restarted the phone after turning Secure Startup off and back on, but it's still happening. Not exactly sure if this is expected, but I couldn't imagine it would be, especiall due to the fact it's really audible. Any advice or suggestions would be great! I'm really at my wits end with this phone and I'm ready to throw it away. The encryption problem I had originally (found here: SD Card No Longer Available (Encrypted) After Firmware Update) is still an issue even after applying the latest updates and I can't afford to lose all the data on my SD card again.
Androidlee said:
I've been having problems with device Encryption and the external storage not mounting, but I recently noticed that after enabling Secure Startup on my Galaxy S7 Edge running 6.0.1 for Verizon and left at this screen for longer than a minute without touching it, a clicking sound as if you were pressing buttons or entering the pattern can be heard. It's continuous and clicks every other second. I Reset All Settings, Reset Network Settings and even applied updates as well as restarted the phone after turning Secure Startup off and back on, but it's still happening. Not exactly sure if this is expected, but I couldn't imagine it would be, especiall due to the fact it's really audible. Any advice or suggestions would be great! I'm really at my wits end with this phone and I'm ready to throw it away. The encryption problem I had originally (found here: SD Card No Longer Available (Encrypted) After Firmware Update) is still an issue even after applying the latest updates and I can't afford to lose all the data on my SD card again.
Click to expand...
Click to collapse
wrong forum mate...
maybe here they can help you better:
http://forum.xda-developers.com/verizon-s7-edge
So, my phone reset itself after a freeze and I did a hard restart. On bootup, it went into recovery and did a factory reset. Once I got everything set back up I noticed when I pick up my phone it makes me use my pattern lock rather than the fingerprints I set up. It does it constantly, unlike what the security protocol says (after 24 hours of not being used). Any ideas?
I may have it figured out. I'll update for sure, but I had AC Display installed and it seems to be cooperating now that I've uninstalled. I'll update at the end of the day to be sure
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
Ive updated to latest ota on pixel 1 and had no problems so far. You could check the dialer app is set as default dialer and all permissions are granted and maybe clear the apps storage/cache, force stop it and re open it and see if that solves anything? Could also check background apps and running services in developing options to see if an app is banging out the memory causing it to lag?
Sent from my Pixel using XDA Labs
pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
if you already did factory reset then it must be a sign of motherboard is dying soon or bad nand chip. motherboard failing on pixel is very common but it happens to less than 1% of people. there are plent of threads on reddit/xda on this.
What's the status of your Pixel? Is the bootloader unlocked? Rooted? Did you have any such problems on the December udpate?
As mentioned - I did factory reset as I thought it may help cure the problems, but it didn't.
I have never unlocked bootloder and phone is not rooted. All standard here.
I have the latest update installed and same problems persist ;/
I'll try another factory reset today.
I can't unlock my phone with the Pattern I assigned it. I always use the same Pattern, so I was pretty sure it's not an error. When I draw the pattern, it says "incorrect pattern" and makes me wait 30 seconds before trying again (from the first try).
Luckily, I have access to Samsung's Find my Mobile, I unlocked the device, removed the lock. But every time I restart the device, the bugged lock screen would come back, and I would have to unlock the device again with Find my Mobile.
please note that I can't set a new lock after unlocking the device, it will revert back to no lock after setting a new pattern/pin/password. definitely a bug.
if there is any method to fix this, or to reset Samsung's lock screen app, please let me know!
my device is Samsung Galaxy A8+ in case anyone was curious.
I never set a lock on a phone or bios password on PCs... now you know why.
You're lucky it was recoverable... some lockouts are not
Data corruption can trigger this and it's just random luck if it happens or not. Even if rare you can see the implications. You're now very close to being completely locked out as it stands
You can try a clearing the system cache and data from the apk(s) controlling it.
Try a hard reboot.
Factory reset... if that fails it's probably hardware. Or simply keep it unlocked and in your possession at all times which is the best security.
blackhawk said:
I never set a lock on a phone or bios password on PCs... now you know why.
You're lucky it was recoverable... some lockouts are not
Data corruption can trigger this and it's just random luck if it happens or not. Even if rare you can see the implications. You're now very close to being completely locked out as it stands
You can try a clearing the system cache and data from the apk(s) controlling it.
Try a hard reboot.
Factory reset... if that fails it's probably hardware. Or simply keep it unlocked and in your possession at all times which is the best security.
Click to expand...
Click to collapse
I'd like to keep it unlocked, yet as I mentioned, it will spring back again immediately as I restart the phone. It won't be funny to get my phone locked outside my home and not having a pc near to access find my mobile to unlock it
I'm trying to avoid factory reset, too much data to back up and I'm quite lazy to do it
And it seems like there is no way to clear cache/data, as the Samsung's lock screen doesn't appear in storage/apps. (Or it is there with some strange system name?)
This thread may help you as it helped me. Read the full thread first.
https://forum.xda-developers.com/t/solved-samsung-a20-twrp-restore-data-sm-205w.4261401/
majdcomp said:
I'd like to keep it unlocked, yet as I mentioned, it will spring back again immediately as I restart the phone. It won't be funny to get my phone locked outside my home and not having a pc near to access find my mobile to unlock it
I'm trying to avoid factory reset, too much data to back up and I'm quite lazy to do it
And it seems like there is no way to clear cache/data, as the Samsung's lock screen doesn't appear in storage/apps. (Or it is there with some strange system name?)
Click to expand...
Click to collapse
Oh my bad, it locks no matter what. That's not good.
Boot menu>clear system cache (don't hit factory reset by accident).
Google for the button sequence to hit for that model. Timing is critical, you might need to try more then once.
That might get it.
Try clearing the Dynamic Lock Screen data.
I would backup all critical data now if you haven't. Do not use Smart Switch to transfer settings if you do factory reset, ha-ha.
Someone here probably has a better solution as I know little about this system.
As always do a Google search, you can probably use solutions from other Samsung models going back a few years.
Erratic and strange behavior can also be a sign of a virus, rootkit etc.
When in doubt, factory reset especially if you can't track down the root cause.
Finding the root cause and correcting it is always preferable to a factory reset but not always possible. If the OS load is older then a year a factory reset be a good plan anyway... nothing like a clean, fresh OS.
Delete your Google account before you factory reset so that doesn't password pester you. I'm told if you reset from settings vs the boot menu that doesn't happen. Not sure haven't tried a factory reset that way.
sammiev said:
This thread may help you as it helped me. Read the full thread first.
https://forum.xda-developers.com/t/solved-samsung-a20-twrp-restore-data-sm-205w.4261401/
Click to expand...
Click to collapse
Can you do that on a stock Android that's not rooted?
blackhawk said:
Can you do that on a stock Android that's not rooted?
Click to expand...
Click to collapse
You would need to be rooted.
sammiev said:
You would need to be rooted.
Click to expand...
Click to collapse
I read if you load TWRP you'll lose things like Samsung Pay.
Seems risky at least to me. I like to play with it but don't have a phone to burn.
A factory reset for me at this point is fairly painless ie no data loss and takes under a couple hours.
If it's of any interest here:
On Android the pattern lock data (SHA-encrypted) is kept in a file named gesture.key and stored in the /data/system folder.
If phone's Android is rooted you simply delete that file to bypass the pattern lock. Using ADB you would run command sequence
Code:
adb devices
adb shell "rm -f /data/system/gesture.key"
to achieve this.
The phone should be now accessible with no pattern lock applied.