Apologies in advance for the potentially vague description, but I also cannot find a solution elsewhere on the forum.
Earlier today, I was watching a YouTube video and then I locked my phone and left it to charge whilst I went downstairs (as I often do). When I returned roughly an hour later, I found the screen on, which I only ever do if I've left Draw Something open, or some similar app - but it was on the lock screen.
(none of that is necessarily important, I just wanted to clear up the "what did you do to make it start rebooting" question)
Anyway, after unlocking the phone, the screen went to black and the phone restarted.
However, it wasn't a "real" reboot, because the boot screen didn't come up, etc. It's just like just the UI is restarted. I can usually use the phone for about 30 seconds at a time. This seems extended when I have flight mode on, and is even longer still when I have the phone locked.
I've uninstalled some potentially-offending apps, removed the SD card, cleared some apps' data, but to no avail.
I'm using default 4.0.4 from Samsung. The only issues I'd had with it until now were that some apps crashed occasionally, but I attributed that mainly to the apps themselves.
The most annoying thing for me is that is seems like it's an issue that can be fixed quite simply, without having to uninstall every app or factory reset the phone.
Anyone have any other ideas as to what I could do? Thanks!
RobHannay said:
Apologies in advance for the potentially vague description, but I also cannot find a solution elsewhere on the forum.
Earlier today, I was watching a YouTube video and then I locked my phone and left it to charge whilst I went downstairs (as I often do). When I returned roughly an hour later, I found the screen on, which I only ever do if I've left Draw Something open, or some similar app - but it was on the lock screen.
(none of that is necessarily important, I just wanted to clear up the "what did you do to make it start rebooting" question)
Anyway, after unlocking the phone, the screen went to black and the phone restarted.
However, it wasn't a "real" reboot, because the boot screen didn't come up, etc. It's just like just the UI is restarted. I can usually use the phone for about 30 seconds at a time. This seems extended when I have flight mode on, and is even longer still when I have the phone locked.
I've uninstalled some potentially-offending apps, removed the SD card, cleared some apps' data, but to no avail.
I'm using default 4.0.4 from Samsung. The only issues I'd had with it until now were that some apps crashed occasionally, but I attributed that mainly to the apps themselves.
The most annoying thing for me is that is seems like it's an issue that can be fixed quite simply, without having to uninstall every app or factory reset the phone.
Anyone have any other ideas as to what I could do? Thanks!
Click to expand...
Click to collapse
just go to recovery mode and fix permissions
Related
Last night I was reading Twitter before going to bed when I noticed that my GPS kept ticking on and off after I'd posted an update (I let my Twitter app access GPS to assign my location to tweets). Thinking that odd, I rebooted.
Talk about the reboot from hell.
Approximately 30 seconds after booting back up, the phone locked: I could tap buttons and feel haptic feedback, but no changes to the screen occurred. I eventually got the bright idea to lock it and unlock it; pressing the lock key blacked the screen, but pressing it again did not bring the screen back. Scared, I eventually pulled the battery and started up again.
It happened again. And again. In the midst of all this, I slowly learned a few things: it wasn't tied to any of the new apps I'd installed (I had enough "functional time" each boot to uninstall a couple of things), it wasn't tied to internet connectivity or GPS (I had time to turn both off), and the SGS3 has a dev option to monitor CPU usage of various apps/threads. That little HUD, which overlayed everything else, would remain updating through a lockup, and I found that a process named "df" was starting up and immediately sucking up the entire CPU and not letting go.
I eventually found that it worked the processor so hard that the phone would overheat if left alone and "soft reboot" (OS restarts, but no Verizon/Samsung loading screens), so I was able to at least stop pulling the battery!
Finally, I turned it off and let it cool down for a few hours whilst Googling: no results anywhere for a similar problem or regarding the "df" process. Turning the phone back on after its reset didn't help at all. The lockup time was so quick that I couldn't even initiate a factory reset--it would lock up in the midst of preparing to perform it!
I eventually restarted it into the bootloader (meant to go for recovery, oops) to poke around and got a really scary image: a "Custom" screen before the bootloader starts that the devs are saying means that system apps/files have been modified. Now, since I don't have root yet (no hacking/voiding warranty JUST yet), I am not ABLE to modify system apps, which means that something got tweaked all by its lonesome, and THAT isn't supposed to happen. It was probably what was causing the lock, though--some driver somewhere that's supposed to say "Processor, don't try to calculate pi to infinity" got hosed or whatever.
I eventually got into stock recovery and was able to initiate the factory reset from there without the use of the actual OS (thus avoiding the hard lock). The phone rebooted fine, let me sign into Google, and spent the rest of the night redownloading apps. It's fine now.
EXTREMELY worrisome. Possibly a hardware fault with the EMMC chips holding my OS or something--there's not a lot that can knock out system files on a non-rooted device. At least it doesn't appear common, insofar as all my Googling leads to no results at all.
Any ideas as to what the heck happened?
Sunday, I started having a problem where my phone (AT&T Galaxy Note 2) would bring itself out of the lock screen without me touching anything. The screen will stay on for 10-15 seconds and then shut off again. It will then stay off anywhere from a few seconds to a few minutes.
Very odd, right? I figured I downloaded a bad app that was causing the issue. I removed practically every app I could (I wasn't going to go through all of them to see which had permissions to bring the phone out of standby). It still kept doing the same thing.
So I did a hard reset on the phone. That should clear everything, right? The problem still kept happening.
I start thinking maybe it's a hardware issue... EXCEPT for it doesn't happen when the phone is in Airplane Mode! Which brings me back around to thinking it's some rogue app, but it still happens even when there's nothing but the default software installed from after a hard reset. It can't be the power button or a bad proximity sensor if it doesn't happen in Airplane Mode, right?
So I took it to the AT&T store and I didn't expect much. The one guy tried to play with my settings and didn't find anything wrong. He took it to the manager in the back room and the manager said I should do a hard reset (ignoring the fact that I told his employee I already had done so twice).
I've looked for answers online. The ones I've found I've tried. I've removed all applications. I've changed the screen time outs. I've even downloaded a Lock Screen replacement program. I've tried using anti-virus to scan for problems. It starts to happen again immediately after I perform the hard reset. I've moved the brightness settings. I've removed the S-Pen thinking it might be causing issues. I've turned on and off motion options. I've turned on and off wi-fi, GPS, screen rotation, multi-window, etc. Power Saving mode doesn't help. Blocking Mode doesn't help. The only thing that works is Airplane Mode.
I have NOT tried rooting my phone. I'm scared to do so, even though I'm a UNIX admin and a techie and shouldn't be scared of something like this.
Has anyone ever experienced this? I'm running whatever the normal, latest AT&T android version (4.1.2) for the Note 2. This is killing my battery and reducing screen life (is that a big deal though? I don't know).
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
Greetings reader. I'm new to the forum but have been viewing threads every now and then, so after having read plenty of times that people should search before posting. I have searched and didn't find what I was looking for, so that's why you can read this now ;p.
4 days ago when I was trying to browse the web in college I wasn't able to connect to the wifi network or even open the wifi settings, so I reset my phone only to find the problem persisting. As if something locked me out of the wifi settings.
I'm perfectly able to access any of the other settings, so I think it's kinda weird.
Shortly after I realised I couldn't get to the wifi anymore my phone started to reboot itself automatically. Ever since that first reboot it just keeps rebooting at the same pace over and over again until I either power it off or until the battery dies.
The phone also get's unusually hot now. Not like, super hot, but definitely hotter than any other time I can remember.
I also get error messages since the problems started saying: 'Process system is not responding'. I then get the option to either force close it or wait. Neither seem to do much if anything at all other than taking away the error message. Sounds kinda critical if you'd ask me.
But so after all these symptoms started to appear I figured I'd just do a factory reset and be done with it, but every time I go into the factory reset settings, I put in my lock screen pattern and then at the last step (pressing the Erase all data button) it just does nothing.
I can touch the button and it does give the animation that it is being pressed, but it just doesn't do anything.
The phone doesn't freeze though, I can still navigate after pressing the button only to see it reboot again shortly after.
After that I tried to flash the rom, but for some reason my PC refuses to show my phone's internal memory in my pcor any sign of my phone's connection at all.
I haven't tried it on any other pc yet, so it might just be my pc, though I doubt it is since it was perfectly able to recognize it shortly before all this started.
The device hasn't endured any shocks lately or expsure to water or whatever, so I think that's ruled out as well.
I am running the stock rom, 2.3 Gingerbread I believe, and the warranty is already way over date (I think. I'll have to check that).
Any suggestions as on how to determine what could be causing this, or how to fix it? Because I really don't want to buy a new phone xD.
Macowski said:
Greetings reader. I'm new to the forum but have been viewing threads every now and then, so after having read plenty of times that people should search before posting. I have searched and didn't find what I was looking for, so that's why you can read this now ;p.
4 days ago when I was trying to browse the web in college I wasn't able to connect to the wifi network or even open the wifi settings, so I reset my phone only to find the problem persisting. As if something locked me out of the wifi settings.
I'm perfectly able to access any of the other settings, so I think it's kinda weird.
Shortly after I realised I couldn't get to the wifi anymore my phone started to reboot itself automatically. Ever since that first reboot it just keeps rebooting at the same pace over and over again until I either power it off or until the battery dies.
The phone also get's unusually hot now. Not like, super hot, but definitely hotter than any other time I can remember.
I also get error messages since the problems started saying: 'Process system is not responding'. I then get the option to either force close it or wait. Neither seem to do much if anything at all other than taking away the error message. Sounds kinda critical if you'd ask me.
But so after all these symptoms started to appear I figured I'd just do a factory reset and be done with it, but every time I go into the factory reset settings, I put in my lock screen pattern and then at the last step (pressing the Erase all data button) it just does nothing.
I can touch the button and it does give the animation that it is being pressed, but it just doesn't do anything.
The phone doesn't freeze though, I can still navigate after pressing the button only to see it reboot again shortly after.
After that I tried to flash the rom, but for some reason my PC refuses to show my phone's internal memory in my pcor any sign of my phone's connection at all.
I haven't tried it on any other pc yet, so it might just be my pc, though I doubt it is since it was perfectly able to recognize it shortly before all this started.
The device hasn't endured any shocks lately or expsure to water or whatever, so I think that's ruled out as well.
I am running the stock rom, 2.3 Gingerbread I believe, and the warranty is already way over date (I think. I'll have to check that).
Any suggestions as on how to determine what could be causing this, or how to fix it? Because I really don't want to buy a new phone xD.
Click to expand...
Click to collapse
Since you've not modified your Sola in any way.
Give this official method a try.
http://xperiafirmware.com/component/content/article/2-uncategorised/29-sony-update-service
Has anyone experience the second screen not working all of a sudden? Mine is just dark with the main screen both on and off. I tried toggling the second screen on and off from the setting, reboot, battery pull, and wiping cache and dalvik but so far none worked.
It's not a hardware issue, I think, because when I open the camera, the second screen comes on for the camera Settings. Also, when in twrp, the second screen is also on as a part of the whole display.
EDIT: I can actually see some light bleed from the second screen with the main screen off. It's just not displaying information it should for some reason.
Sent from my LG-H901 using Tapatalk
I just got mine, and something I did in the course of adding/changing/modding did the same - I lost my second screen when the phone was off, but when it was on I had my shortcuts. I wound up factory resetting and re-installing/re-configuring my apps... knock on wood, everything works just fine now. I think mine failed when I unfroze an app in Titanium that it marked for me.
About the only thing that I did before I lost the second screen is installing a game from the play store. I have uninstalled it, but still no luck. I most likely will factory reset and if that doesn't work, I'll flash stock rooted rom... And set my phone up yet again.
Sent from my LG-H901 using Tapatalk
Same symptoms
I am on stock, albeit rooted. I froze a few apps, but I have also rebooted multiple times before the second screen disappeared, so I am not sure how anything I have done this far could be the cause.
Because I saw I am not alone, I started to do some digging. It looks like the app is located in /data/data/com.lge.signboard, which actually has symlinked directories. Not sure if its a clear indicator of the issue, but most of the directories are empty. Definitely odd.
I'll load up SSHd later and see if I can investigate more.
Did the factory reset and now the second screen works. I'm sincerely hoping that this is not a regular occurrence. I haven't liked a phone so much since galaxy s2.
Sent from my LG-H901 using Tapatalk
I also had my second screen go funky. Haven't factory reset but I'm going to. It seemed to happen as I was also defrosting and refreezing some LG things, mainly services and such and not apps that you interact with per se. At right about the same time I noticed something else strange. When plugging the phone in, it takes several seconds for it to realize it whereas before it used to be instant. Also, the camera is very slow to load and change from the front to the back ones.
So I got a little bored
And fired up adb logcat to see if I could find anything. I don't yet know if it's related or not, but there is a message
Code:
I/[SystemUI]MiniStatusBar( 5541): signBoardWindowShow() requested but unavailable. Hide MiniActivity.
that shows in the log.
I to tried clearing cache and dalvik or art or whatever to try to get the second screen back no avail.
I'm having the same issue. Any update on this?
I too am interested in this, I had this issue occur too when I froze some applications (system apps) that I didn't think were necessary. Unfortunately once you freeze the component it blocks the screen and unfreezing everything back does not bring the screen back you have to factory reset it. Any ideas of what the service is that affects the second screen?
Second Screen symlink busybox
After reading all your comments on what you could have done to cause the second screen from working, it looks like the symlink is broken especially if you have updated your busy box. I too started to have the second screen go bad on me and I couldn't figure it out until I read this thread especially the log post. I am going to reset and ensure that smart install is set right in busy box.
Recently, the AT&T LG V10 (H900) just got root here: http://forum.xda-developers.com/att-lg-v10/general/root-lg-h900-real-tot-make-tungkick-t3336317
I then debloated the V10 on firmware H90010f with Debloater v3.90 here: http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Before, I decided to have the second screen off for a while, so I disabled it in the system's menu. I then advanced towards debloating. Decided to turn on the second screen again. Notice that there were issues with it. So now I'm currently experiencing this issue: the second screen does not show date, time, weather, notifications, quick icons. Only shows quick toggles if I swiped from right to left, such as sound profile, WiFi, flashlight, and camera. I undo all of the debloating, rebooted the phone many times, still the same problem. Sigh. I'm trying to avoid doing factory reset because I'm not up to reloading everything again, especially the SMS/MMS.
So, anybody found out a better solution other than doing a reset?
Update 1: It seems like re-rooting with updating the ROM with the "upgrade" option for the AT&T LG V10 to not do a full clean install does not solve the problem. I didn't lose all my personal data, but I did not gain anything that it restored system apps to previous default settings. Sigh, it's just one step closer to just do a factory data reset.
Update 2: There appears that other things were broken from disabling/removing apps (during phone calls, cannot multitask, such as switch apps or use the notification area; SuperSU couldn't generate a log correctly), so I went ahead and did a factory reset since there was no alternative restoring method. The second screen works again and so does the said apps. Looks like I'll have to be careful which apps I'll be disabling/removing with Debloater.
Uninstalling an app restored my second screen.
I had this issue as well. Camera controls were in the second screen space, the swipe to end call would appear, but none of my other settings stayed long after restarting my phone, maybe 10 min. I uninstalled some of my most recent apps, the suspect one being "Zooper Widget Pro" and the issue stopped. No factory data reset etc. This app was a launcher-type app (I'm a geek but nowhere near the tech terms used elsewhere on this site) and I thought it might be the issue due to its ability to control the home screen. I doubt it was intended to work with this arrangement. So I would look at any launchers or apps which can control the home screen before doing a reset as this exact issue was easily solved for me.
I just got the phone and set it up. the only thing I disabled was ATT bloatware nothing else. 2nd screen is only on when main one is on. Using nova launcher. I tried uninstalling and that didn't help. Is there any more info on this, can I get it working without factory reset ? I get no indication of notification right now other than sound.
I did factory reset and that didn't help either.
I have a same problem with the second screen to. So anybody can help me!
Is there anyone can help me pls!!!
I solved this problem by checking PINs on mainboard for the second Flex Cable for LCD of LG V10, see the video, READ comments here https://www.youtube.com/watch?v=hpeVAqgU94s, so in my case one of three PINs was folded little, so one PIN contact didn't touch the second Flex Cable and this caused the problem...