Related
Android 2.3, 407band, DSC 7.0 rom, Go launcher (default), Zeam launcher (secondary)
Today while using an app called wallbase, I hit the home button while the app was setting a wall paper for me (normally I wait until it says wallpaper set). The home screen popped up but then Go launcher had a FC error (which it has never had since I've been using it). It had the option fc or wait I hit wait. Next my wall paper went black then my screen followed by two vibrations and a notification sound I never heard my device make.
I rebooted to the lock screen with a black background and no service on the screen. It was unresponsive to my touch and after about 10sec. it gave the same two vibrations and sound from before then shut the screen off. The power button did not turn on the display so I had to hold it down for about 20sec for it to reboot to dell logo. From there i went into nandroid and flashed severals roms loaded to the lock screen, rinse/repeat, to find the same result (simple streak, streakroid, older version of dsc).
I reset permissions, wiped cache and dalvik, calibrated screen. Want to avoid a factory reset because I don't have a backup.
Help guys? Mods please move to the appropriate forum.
If all fails and you don't have another alternative.
install the DSC v0.70 update, it shouldn't delete your 'data'.
I would backup your streak, better be safe than sorry.
So I tried letting it sit with the battery out for the night (6 hours) and booting it up this morning with the ac charger. It loads to the same lock screen (standard screen with black background and no service on screen) and all my start up apps loads, it even showed me a text notification. I did notice that the time was wrong though and never changed.
Any one have this issue before? What suggestions are there to combat this? The G.Note doesn't fit into my budget right now. May have to factory reset this and sell it as a last resort.
Help guys?
Outlook for this issue looks grim. Seem others with a similiar issue on different devices have had to factory reset or return it to manufacturer.
Before I do that, is there are any possible way for me to backup some of my app data?
Anyone know if Dell still helps with this device?
I use the app cadrebible often(its the only one I really care about) but it doesn't auto sync/backup and my last manual backup must be from Dec2011 - yea makes me want to cry.
I can load into fastboot, so is there a way I can uninstall a few apps I suspect are causing the issue? Move files from the phones to the sd card/computer?
factory reset. Mod feel free to close thread. -- yes im crying.
Did you try calibrating the touch screen?
Earlier today, a few apps on my Nexus 7 have just started closing within one or two seconds of opening them.
Google Search Bar, Facebook and Catch Note all close within a couple of seconds after opening them. I have used them fairly frequently for the last few weeks with no problems. Other apps, such as Twitter, Chrome and some games all work fine.
I have turned my device on and off a couple of times, but the problem still persists. Any ideas?
The problem is still occurring for me.
Gmail, Calendar etc... all also closing within a second or two of opening. Is this a common problem?
Is your N7 all stock or do you have a custom rom?...custom kernel?
You really need to provide some information in order to get help.
I haven't seen it in the OP so: Reinstall them
Visa Declined said:
Is your N7 all stock or do you have a custom rom?...custom kernel?
You really need to provide some information in order to get help.
Click to expand...
Click to collapse
I haven't rooted my Nexus, or anything like that, it's all stock.
I just uninstalled Facebook, then downloaded it again. It seems to be working. Other apps still have the same problem. I assume that I have to do the same for all other apps - but is that even possible for apps such as Gmail, Calendar and the Search Bar?
Uninstalling and re-downloading hasn't worked as I had hoped.
It seems to have worked for Facebook. But I did the same for Catch Notes, and although it worked for a minute or so when setting it up, after creating a test note, it force-closed, I opened the app up again, and the old problem of closing within 2 seconds happened.
Other apps such as Gmail, I uninstalled, 'updated' again, and nothing changed, still closes immediately. There is no error message, it just returns to the home screen.
I thought that Task Killer might have been a problem, but I uninstalled that, restarted the Nexus, and the problem persists. Actually, when I turned off my Nexus, and tried to turn it back on, it was stuck on the 'coloured X' screen for a few minutes, I had to hold the power button down, and turn it on again. I'm starting to worry about my Nexus now.
Update:
A couple of other odd ones.
Google Drive doesn't even open. When clicking on the icon, the normal shading effect happens, but nothing else, no window even for a second.
Google Calendar opens, and just has a white screen, as if it is ready to load the calendar, but nothing loads. It doesn't close, just remains on the white screen, which can't be backed out of without pressing the home button.
Have you tried doing a cold-boot on the device? Maybe another app running in the background is causing conflicts. Where there any recent apps that you've downloaded?
Asus_USA said:
Have you tried doing a cold-boot on the device? Maybe another app running in the background is causing conflicts. Where there any recent apps that you've downloaded?
Click to expand...
Click to collapse
I have just followed the instructions for a 'cold-boot' and now my Nexus can't get beyond the 'X' screen...
I have held the power button down a number of times, and tried turning it on again - but the 'X' continues to be displayed for over 20 minutes.
Just managed to turn my device on - but the problem still exists.
I didn't download any new apps that seem to have caused this problem. Though I think an app might have force closed and the Nexus displayed an error message such as "android/Google system stopped working" (probably different) and my home screen went blank for a while. Everything reappeared though after a short while. It could have stemmed from that.
Sorry about another bump, but i'm wondering if anybody has any more ideas before I go for a factory reset?
Edit: Actually, I think that I have found the cause of the problem. I just opened a game (Let's Golf 3) that I was playing before the problem started and after a few seconds, a message popped up saying "Unfortunately, Launcher has stopped". When I press OK, it returns after a few seconds.
I pressed the sleep button, and my Nexus turned off. Now trying to turn it on again, having some problems getting past the 'X' screen again. If I finally get in, should I uninstall the game? Any other solutions to this problem?
If your N7 can boot up, go the isolate & identify routines - disable/uninstall or freeze the golf game - do a normal shutdown/restart.
If normal functionality is back, you've just found the source. Not a gamer myself except for Angry Birds ... , but from the Play Store description, it access & make changes to system & protocol, etc. as you should contact/email golf's tech support for resolution. Otherwise, take a look of any background running apps or widgets, newly added or updated.
Letitride said:
If your N7 can boot up, go the isolate & identify routines - disable/uninstall or freeze the golf game - do a normal shutdown/restart.
If normal functionality is back, you've just found the source. Not a gamer myself except for Angry Birds ... , but from the Play Store description, it access & make changes to system & protocol, etc. as you should contact/email golf's tech support for resolution. Otherwise, take a look of any background running apps or widgets, newly added or updated.
Click to expand...
Click to collapse
Thanks for the help.
I couldn't get my N7 to boot up, so I finally gave in and did a hard reset (by holding power + volume down, Recovery Mode, then wipe data etc...) but my N7 still won't boot up
I have wiped it twice, and rebooted it, yet it is constantly stuck on the 'X' screen. What on earth can I do?
Gawge said:
Thanks for the help.
I couldn't get my N7 to boot up, so I finally gave in and did a hard reset (by holding power + volume down, Recovery Mode, then wipe data etc...) but my N7 still won't boot up
I have wiped it twice, and rebooted it, yet it is constantly stuck on the 'X' screen. What on earth can I do?
Click to expand...
Click to collapse
I would flash the stock system image.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
I would flash the stock system image.
Click to expand...
Click to collapse
How would one do that?
My N7 isn't rooted or unlocked.
Gawge said:
How would one do that?
My N7 isn't rooted or unlocked.
Click to expand...
Click to collapse
You will need to download the factory image, unlock your bootloader, and flash it. There is a guide on this forum, it might be stickied.
Sent from my Nexus 7 using Tapatalk HD
I was hoping there was going to be a resolution to this other than a "flash to stock" suggestion... My Nexus started doing this exact same thing this past Sunday when it ran out of power completely and needed to be recharged. After it powered back up from charging the following apps quit working altogether or just started quitting once it appears they try to access data: Netflix, Currents, Zillow, Gmail, HBO Go, Press (though Google RSS Reader works), NVision, TegraZone and a couple others. I have done the reboot thing as well and almost had this thing brick again (stuck at X), but I managed to clear the data cache from the fastboot menu and it started up again. I'm now at the point where I'm troubleshooting individual apps but the clear data/cache, uninstall - reinstall process isn't working for any of the broken apps. This is now the 4th time I will be facing a 'flash to stock' situation as it appears that I've had every problem that leads to this 'fix'. I'll try a couple more things (mostly deleting and clearing everything) but I'm really frustrated with how many times I've had to flash this damn thing. sigh.
This is really starting to get on my nerves now. Ever since I got my new S10+ from AT&T, it's occasionally done this thing where after I reboot the phone, I unlock it, and it briefly says "starting phone" on the home screen, and then will mysteriously do a quick reset, where it skips the AT&T logo and jingle, and just shows the Samsung splash screen , then takes me back to the lockscreen and it's usually fine after that.
However, Just now I decided to reset my phone, like one should do periodically, and it did the strange double reset after unlocking... Then when I unlocked it, after the "starting phone" message I tried to open a browser, and BAM! Quick reset again! Unlocked, let it start up, tried to open an app, BAM quick reset again after the screen briefly shifted from landscape to portrait mode (even though I was still holding it long ways in landscape position). Its never done this before and I'm getting concerned. It's never randomly reset while using the phone, this only happens right after a reset.
Any ideas? I've already tried wiping partition cache after big updates, doing soft resets. I'm worried that I'm going to have to end up resorting to a factory wipe, as others suggested I do when I was having battery drain issues on the ASD3 firmware, possibly because of restoring everything from a backup of my last phone when I got this one. Because supposedly restoring from backups from AT&T, Google or Samsung has caused all sorts of problems for people. I really don't want go wipe everything and spend hours try to get it all back on here manually if i don't have to.
SinisterDev said:
This is really starting to get on my nerves now. Ever since I got my new S10+ from AT&T, it's occasionally done this thing where after I reboot the phone, I unlock it, and it briefly says "starting phone" on the home screen, and then will mysteriously do a quick reset, where it skips the AT&T logo and jingle, and just shows the Samsung splash screen , then takes me back to the lockscreen and it's usually fine after that.
However, Just now I decided to reset my phone, like one should do periodically, and it did the strange double reset after unlocking... Then when I unlocked it, after the "starting phone" message I tried to open a browser, and BAM! Quick reset again! Unlocked, let it start up, tried to open an app, BAM quick reset again after the screen briefly shifted from landscape to portrait mode (even though I was still holding it long ways in landscape position). Its never done this before and I'm getting concerned. It's never randomly reset while using the phone, this only happens right after a reset.
Any ideas? I've already tried wiping partition cache after big updates, doing soft resets. I'm worried that I'm going to have to end up resorting to a factory wipe, as others suggested I do when I was having battery drain issues on the ASD3 firmware, possibly because of restoring everything from a backup of my last phone when I got this one. Because supposedly restoring from backups from AT&T, Google or Samsung has caused all sorts of problems for people. I really don't want go wipe everything and spend hours try to get it all back on here manually if i don't have to.
Click to expand...
Click to collapse
Had an issue with this early on but seems to have been fixed at some point, I'm I'm exynos though so probably not much help!
mtm1401 said:
Had an issue with this early on but seems to have been fixed at some point, I'm I'm exynos though so probably not much help!
Click to expand...
Click to collapse
Dang... So it does appear to be an issue experienced on both Exynos and Snapdragon variants. I wonder if there is or will be a fix for this. I've been asking around and haven't gotten many responses about this problem at all. I'm concerned because it seems to be getting worse than when I first got the phone.
I'm having the exact same problem. Sometimes it goes through quick reset, full reset, a couple more quick, then back to the Verizon logo, then starts up. Opening an app at that point usually does another quick, then full, then everything works. Glad I'm not the only one, but I haven't found any solutions either.
macmanui said:
I'm having the exact same problem. Sometimes it goes through quick reset, full reset, a couple more quick, then back to the Verizon logo, then starts up. Opening an app at that point usually does another quick, then full, then everything works. Glad I'm not the only one, but I haven't found any solutions either.
Click to expand...
Click to collapse
Mine does the same. Unlocked bought directly from Samsung. I don't reboot the phone very often so it doesn't bother me that much.
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.
From power off or restart to the screen lock.. takes 1 minute and 40 seconds.... seems very long to me.. My PH-1 is stock and never rooted and always went through the OTA updates and is current and up to date on Android 10.
Thoughts
My first thought is it may be time for a factory reset.
have you tried safe mode?
Never timed mine until now. Just got curious... Regular restart: 1:25 from tapping the button in Power menu to the screen lock. Faster than yours, but not by much. Seems normal to me, consistent with what I've been seeing with this phone.
kt-Froggy said:
Never timed mine until now. Just got curious... Regular restart: 1:25 from tapping the button in Power menu to the screen lock. Faster than yours, but not by much. Seems normal to me, consistent with what I've been seeing with this phone.
Click to expand...
Click to collapse
Thank you for timing yours! Just ran mine again with the stop watch on my Smart watch and it came in at exactly 1:52:78 so it is a bit slower than yours. Think I will try a factory reset and then time it before restoring everything from the cloud and see what I get. :highfive:
It seems due to the November Update.
SirDigitalKnight said:
Thank you for timing yours! Just ran mine again with the stop watch on my Smart watch and it came in at exactly 1:52:78 so it is a bit slower than yours. Think I will try a factory reset and then time it before restoring everything from the cloud and see what I get. :highfive:
Click to expand...
Click to collapse
Yes, seems very long. Mine takes about 35secs & that was with me putting the wrong SIM pin in the first time (I stoped timing when the clock appeared on screen (and my always on VPN had started, so could have been even quicker)
(I'm using a pin for unlock & was connecting to mobile data. Wonder if there is an app that runs at start up that could be slowing you guys down?)
64 seconds from cold to lockscreen for me - stock rooted 10.
I use SD Maid and selectively disable boot from a lot of applications - You would surprised be how many apps think they have the right to launch every boot and sit around in the background.
Magisk scripts can take a while to complete and will slow down launch too, a lot of modules would probably slow it too.
A little bit of housekeeping would probably help, a reset and restore however could just restore the same problem again....
After a factory reset without a restore it took 18.22 seconds from powered off state to the lock-screen. After a full restore from cloud backup it now takes 22.51 seconds from power off state to the lock-screen. Also the phone is way more responsive like it was when I first bought it.... Guess it is true what I have read online... best to factory reset your phone from time to time.
I get occasional long boot times, mostly after an update or similar. I haven't hooked up to adb during boot in awhile, but typically if you are having a long boot time the odex optimizer is probably re-running.
SirDigitalKnight said:
After a factory reset without a restore it took 18.22 seconds from powered off state to the lock-screen. After a full restore from cloud backup it now takes 22.51 seconds from power off state to the lock-screen. Also the phone is way more responsive like it was when I first bought it.... Guess it is true what I have read online... best to factory reset your phone from time to time.
Click to expand...
Click to collapse
So mine had some issue & I lost data connection & wifi, couldn't fix so rebooted & now it's really slow to reboot. Did you have any issue with data/wifi. (I run a vpn so thought that might have been the cause, but even with it uninstalled it's still slow, though could have been initial cause)
Also since then installed this months security update but it still slow (over 1:30), update tons took about 30min as app optimising was so slow.
IronRoo said:
So mine had some issue & I lost data connection & wifi, couldn't fix so rebooted & now it's really slow to reboot. Did you have any issue with data/wifi. (I run a vpn so thought that might have been the cause, but even with it uninstalled it's still slow, though could have been initial cause)
Also since then installed this months security update but it still slow (over 1:30), update tons took about 30min as app optimising was so slow.
Click to expand...
Click to collapse
Mine did not have any issues with data nor wifi.
I would still do a factory reset.
Same thing happened to me with painfully slow boot times. Factory reset and restore, now boots in 25 seconds from switch on to lock screen.
i did a factory reset and it still takes over 2 min to boot.. accidentally wiped my phone trying ot install twrp..
then went ahead and installed lineage.. boots fast but can't get gapps to load lol
going to try to install lineage 18 and gapps.
dannysportbike said:
i did a factory reset and it still takes over 2 min to boot.. accidentally wiped my phone trying ot install twrp..
then went ahead and installed lineage.. boots fast but can't get gapps to load lol
going to try to install lineage 18 and gapps.
Click to expand...
Click to collapse
Note: Are you using MindTheGApps, still only recommended package (though someone got another gapps to work, can't remember which)
Also make sure you are installing gapps BEFORE 1st boot into Lineage OS, if not do a factory reset & install gapps then boot to OS
should work fine on LOS 19.1 (or use npjhonstone unofficial version which has it included with rom)
PS. Never hand issue with increasing boot times since installing LOS.