Guys,
I'm pulling my hair out over this. My MDA Vario has often rebooted itself and i've always put it down to a glitch of one form or another, but today it has been rebooting every few minutes.
Each time it reboots a text message i've read reappears as NEW, as though the phone doesn't register me reading it before it crashes and reboots. If I delete this and other messages, within minutes once it's crashed and rebooted they will all return like a CACHED memory or something.
I don't know what to do.
It seems as soon as my screen dims on power save, it won't come back on and within a few seconds the screen goes white as it is rebooting.
Sometimes reading this message or doing anything in the message application causes the crash, sometimes it's happenign even without me doing anything.
HOWEVER - once i've turned off the power saver dimming the screen, no reboot is occuring. I've gone into the messages, read and deleted this message among others, and no reboot. If I manually turn the screen off though, within a few seconds it reboots.
What is going on ?!
i have the same exact problem! I changed the battery the day before yesterday and it has not done it since, but im not sure if it solved the problem as sometimes it does not restart in one whole day!
phone crashed in browser, completely froze up, i restarted by holding power button down, once it restarted i get a red disk symbol in notification about database storage low and device managment keeps force closing then logs provider keeps force closing.
cant do a thing on the phone, have restarted numerous times..dont know what todo.
i am on JF5 and rooted.
update:
ok hard reset and this has fixed the issue, but would be good to know if anyone else has seen this error, the last app i installed before crash was SEEPU free version, just kept getting constant cycle force closes of logs provider and device managment as mentioned.
Hi All the people that has sudden problems with frozen Note3. (No root, original 100% yet)
My experience has shown that WATCHON app is creating me some problems. From the very moment I opened the app, configured and so on I had problems. The mobile suddenly didn't respond, the alarm get stuck when started to sound, the whatsapp voice button causes to freze the complete mobile, and sometimes when trying to turn on the scren with button the screen remains off... (black screen). Always had to restart...
For solve issue, I tried everything I leave the idea to solve it until next complete wipe. But one day, I saw also some problems on the unlock screen with watchon, and several issues with watchon configuration.
When dissabled the app everything shines again. Any more problem since then. Any. At last...
If any of you have problems like this, try dissable WatchOn....
langas said:
Hi All the people that has sudden problems with frozen Note3. (No root, original 100% yet)
My experience has shown that WATCHON app is creating me some problems. From the very moment I opened the app, configured and so on I had problems. The mobile suddenly didn't respond, the alarm get stuck when started to sound, the whatsapp voice button causes to freze the complete mobile, and sometimes when trying to turn on the scren with button the screen remains off... (black screen). Always had to restart...
For solve issue, I tried everything I leave the idea to solve it until next complete wipe. But one day, I saw also some problems on the unlock screen with watchon, and several issues with watchon configuration.
When dissabled the app everything shines again. Any more problem since then. Any. At last...
If any of you have problems like this, try dissable WatchOn....
Click to expand...
Click to collapse
I will try this and hope that it works.
I had a sudden freeze during my first time wizard right after selecting my language.
http://forum.xda-developers.com/showpost.php?p=47178130&postcount=52
Nope, still happening:
http://forum.xda-developers.com/showpost.php?p=47382126&postcount=81
After Oreo OTA update "CRB7", when phone wants to act with security setting (for example when I want to go to Lock screen and security), a message appears: "Face keeps stopping".
I cleared "Face" application cache and data manually and then restarted phone, but still this problem repeats and repeats consecutive.
I don't want to reset factory my phone and this is annoying.
A fresh start is always better.
I've never rooted or unlocked the bootloader, after updating to official oreo 8.1(via OTA), Lenovo startup screen is blocking the screen so I cannot access anything directly, like, the touch and everything is working fine but with the lenovo screen I just can't see where I'm touching, the phone starts up ok and I can hear when I getting messages and I can use Whatsapp web to write messages, I could rotate the phone and see half of the screen and the other half Lenovo logo still blocks, Is there anything I could do exept factory reset?
Hello,
Try to turn on screen rotation,
And turn the phone sideways and use split screen with the settings as the second app.
Uninstall any app that has access to system controls,like TeamViewer
rickyninpo said:
Hello,
Try to turn on screen rotation,
And turn the phone sideways and use split screen with the settings as the second app.
Uninstall any app that has access to system controls,like TeamViewer
Click to expand...
Click to collapse
I've fixed it after wipe cache in stock recovery.
But thanks anyway
Edit: and there we go again, same problem and not even a wipe cache is helping
.....
Thats how its looking like, this system popup shows something that i cant see
rickyninpo said:
Hello,
Try to turn on screen rotation,
And turn the phone sideways and use split screen with the settings as the second app.
Uninstall any app that has access to system controls,like TeamViewer
Click to expand...
Click to collapse
Done it and not worked
I am having the same issue: phone boots normally, then seems to hang on the Moto boot animation - except that the phone is fully booted, alive, accepts touch inputs and has network/signal, except nothing is rendered to the screen, only the frame of the Moto boot animation is displayed. This remains the case regardless of what occurs on the phone, e.g. the phone can receive a call, and will respond as expected, except the display remains fixed on the single frame from the Moto boot animation.
I have wiped cache partition multiple times to no avail.
Any ideas on what might be causing this?
Any ideas on how to solve this?
Worst case scenario, any ideas on how to pull data off the phone?
Thanks
zinkyzinkerson said:
I am having the same issue: phone boots normally, then seems to hang on the Moto boot animation - except that the phone is fully booted, alive, accepts touch inputs and has network/signal, except nothing is rendered to the screen, only the frame of the Moto boot animation is displayed. This remains the case regardless of what occurs on the phone, e.g. the phone can receive a call, and will respond as expected, except the display remains fixed on the single frame from the Moto boot animation.
I have wiped cache partition multiple times to no avail.
Any ideas on what might be causing this?
Any ideas on how to solve this?
Worst case scenario, any ideas on how to pull data off the phone?
Thanks
Click to expand...
Click to collapse
I've faced that issue a couple times, I don't know what is causing this but I think it's kind of some storage issue, and the workaround I've found is freeing up some storage space. You could try it and see if it works for you too!
I had same problem. TL;DR - Rebooted several times after wiping cache and resetting dpi to 400.
Full story:
I had recently encrypted the device and had about only ~300 MB left in my internal storage. Decided to wipe cache partition and went to shut down the device. Hit reboot instead of shutdown.
Decided to shut down after it boots up. But when it started, the motorola lenovo image was stuck.
I could hear the phone unlock and the notifications. Called the phone thinking the incoming call might display over the image but to no avail.
Google assistant could hear me and respond to commands. Opened apps with that.
Then tried to see if apps would respond to touch. Long pressed power button to bring up the power menu(Power off, Restart, Emergency), pressed the place right next to the power button because I remember the "Power off" option there. Booted into recover and cleared cache partition. Rebooted twice with the same result. Stuck at the moto image.
Read in the beginning of this thread that rotated screen seems to show half the display. So, tried to see of it works and it did. That was of no use to me as I didn't know what to do after that.
So decided to see if changing the dpi would make a difference. Used ADB and "adb shell wm density DPI" (replace DPI with your desired number. Default value is 480.) to change and rebooted. It seemed to fix it as I rebooted after the command and my display was back to normal.
Not going to change the value now as I don't want to mess with anything now. Maybe later, I will reset it to 480 and see if the issue appears again.
Manolingam said:
I had same problem. TL;DR - Rebooted several times after wiping cache and resetting dpi to 400.
Full story:
I had recently encrypted the device and had about only ~300 MB left in my internal storage. Decided to wipe cache partition and went to shut down the device. Hit reboot instead of shutdown.
Decided to shut down after it boots up. But when it started, the motorola lenovo image was stuck.
I could hear the phone unlock and the notifications. Called the phone thinking the incoming call might display over the image but to no avail.
Google assistant could hear me and respond to commands. Opened apps with that.
Then tried to see if apps would respond to touch. Long pressed power button to bring up the power menu(Power off, Restart, Emergency), pressed the place right next to the power button because I remember the "Power off" option there. Booted into recover and cleared cache partition. Rebooted twice with the same result. Stuck at the moto image.
Read in the beginning of this thread that rotated screen seems to show half the display. So, tried to see of it works and it did. That was of no use to me as I didn't know what to do after that.
So decided to see if changing the dpi would make a difference. Used ADB and "adb shell wm density DPI" (replace DPI with your desired number. Default value is 480.) to change and rebooted. It seemed to fix it as I rebooted after the command and my display was back to normal.
Not going to change the value now as I don't want to mess with anything now. Maybe later, I will reset it to 480 and see if the issue appears again.
Click to expand...
Click to collapse
I am also facing the same issue, I have tried cache wipe but it's not working. I can't access anything in mobile because of the logo. USB Debugging was already enabled but ADB commands are not working. Can you please share the steps how you have changed DPI.
Thank you
JaiSoni.87 said:
I am also facing the same issue, I have tried cache wipe but it's not working. I can't access anything in mobile because of the logo. USB Debugging was already enabled but ADB commands are not working. Can you please share the steps how you have changed DPI.
Thank you
Click to expand...
Click to collapse
Sorry for the late reply. Is this resolved?
Solution:- Clear some of your device's internal storage. Uninstall infrequently used apps & delete unnecessary data. Power off your phone & then power it on. It should get back to normal. Description:- While using my phone I got stuck on an application & had to restart the phone. During boot up it took longer than usual & at last got stuck at Lenovo logo. I tried restarting it several times again but in vain. I searched on the internet & tried their suggestions. Basically the phone is working in the back end. Only the screen is stuck at Lenovo logo. So I unlocked my phone by typing my PIN by guessing where the numbers would be. Then tried to turn on auto rotation using Google Assistant but since mobile data was off so it didn't work. Then I turned mobile data & auto rotation on by toggling the quick settings by guessing where they would be & trying again & again. Once turned on, hold your phone in landscape mode half of the screen will be visible if your home screen allows rotation, if not go to any app which supports auto rotation & then switch to landscape. Then using multi tab open settings in the second tab. Clear your internal storage. I cleared about 5-6 GB but 2 GB should be enough. After clearing your storage, power off your phone & then power it up. The phone was normal again.