Related
Does anyone know what this is, Or why it happens. my phone would crash and this screen would pop up. I did alot on my phone before it started to happen. I think it has something to do with GPS, but the only other people I have seen on the net to have this problem have different stories.
One says its after he rooted
Another person on the T-mobile forums reported it but didn't give a suspected reason.
Mine did it after three things happened I used the supl.google.com gps fix, and my battery showed an overheat warning when charging turned off. And My girl tried to send 15 pics she took to herself and cousin one through E-mail and the other through mms. The email and text messages to my girl gave me error messages that and a way to solve the problem (which didn't work) The only thing that worked was deleted her thread and the email.
I have since restored factory setting to see if it fixes the problems. I'll keep everyone updated.
If anyone has any ideas or has had this happen chime in maybe we can find out whats going on.
Factory Data reset was useless, it was a waste of time. It appears to be related to the GPS. After thinking about it, the radio probably burned out when i was trying to use gps while charging it in the car yesterday, it had to be 94 degrees outside probably hotter on the dash. The phone actually reset to the battery indicator and flashed a battery heat warning. Gps didn't last last long after that. It was the next morning when I started to get the error.
Called rep, and he gave me an exchange right away, no questions, will be getting another phone sat. or monday.
I realize this is a little old, but I just wanted to say that I just had the same problem today while I was using a navigation tool (Waze). I thought it might be related to the app, but maybe it is the GPS as op said.
I do realize this thread is months old but, likewise, I just had the same thing happen to me.
I wasn't using GPS though, I was simply trying to tether through usb.
Next thing I know the "kernel panic, upload mode" screen came up rendering my phone useless
I pulled the battery restarted, and did the same thing yet this time the screen didn't come up allowing me to tether and search the issue.
From the google search results I came across a thread where a guy said it had something to do with task managers/killers. He said since he unistalled the version he was using "advanced task manager" he never had the problem again.
which led him to believe it came from the wrong proccesses being killed or stopped by it which caused the kernel to crash.
Likewise...I too was using a task killer--Auto killer. So I uninstalled it as well, and now use the system default task manager to kill unwanted apps manually.
So far so good...Idk if this is the solution, but to any future readers that run across this and are having the same problem, I suggest you rid of any task killing apps that may be running. Manually kill apps on your own, and let android handle the rest.
I'm not saying dont use them at all but...unless you are an advanced enough user to understand how they work a little more, your best benefit is to leave it be.
Here are some tips that helped me fix this issue:
1. As someone said earlier, uninstall task killers. It's better to install an app that changes the os default task killer. I use autokiller and I use the preset optimum. This way the os can manage the processes and it will stay stable.
2. If you have setcpu, make sure to go to menu, autodetect device, and then set the minimum to 200.
3. If you flash a rom, if it's possible use a clockwork recovery image instead of using Odin.
After these steps, it never happened to me again.
crazy25000 said:
Here are some tips that helped me fix this issue:
1. As someone said earlier, uninstall task killers. It's better to install an app that changes the os default task killer. I use autokiller and I use the preset optimum. This way the os can manage the processes and it will stay stable.
2. If you have setcpu, make sure to go to menu, autodetect device, and then set the minimum to 200.
3. If you flash a rom, if it's possible use a clockwork recovery image instead of using Odin.
After these steps, it never happened to me again.
Click to expand...
Click to collapse
I was using Autokiller too....I uninstalled it and everything seems fine, Idk, may had nothing to do with it...because I've used Autokiller for quite a while, way back on my G1 and never had that problem, oh well...appreciate your input.
I had several "kernel panic" warnings on my handset which I replaced. If I remember it was after using Google maps right after an update and it was hot as a ***** and could smell components melting. As far as autokiller the experience I had was that say I was online Google reader decided to check XDA for instance,go back to Steel would have closed the App out.this happened using visual task swithcher and the default last used programs panel. So I don't use it for that reason.
if your phone is Loki, use Odin, you'll be Thor.
Thread moved to Q&A.
I think this is related to some applications. This is happening to me also, I am on Stock 2.2 Rooted. First I noticed this one when I was online on Nimbuzz and my yahoo account was logged in through nimbuzz, and when I started Yahoo messenger with the same login ID I got "USER FAULT NOT KERNEL PANIC". It happened with same scenario again & again. So I dont use both together.
Again I noticed when I kept my phone on charging through USB connected to a PC, sometimes my fon went in the same Panic mode without doing anthing.
Somebody needs to find out why this is happening. some application or process is causing this problem which needs to be find out.
Vibrant Crash Response
I have the same problem! It's happened about 20 times to my phone. It crashes, gets hot as ****, and gives me the 'user fault kernel panic upload mode' screen.
I think I've narrowed it down a little though.
Things I've noticed:
1.. It only happens when the phone is charging, never on battery.
2.. It only happens after the screen is turned off, never while I'm using it (anywhere from 5 min to hours after the screen has been off).
I'm guessing its some kind of background process that uses a lot of processing power and overheats the phone..
Hope this helps. Be sure to post up if you find a solution.. I don't want to burn it up!
Just for confirmation sake are we all seeing the same Kernel Fault error? are you seeing the same codes?
RST_STAT 0X4
PMIC_IRQ1 0x0
PMIC_IRQ2 0x0
PMIC_IRQ3 0x0
PMIC_IRQ4 0x0
PMIC_STATUS1 0x0
PMIC_STATUS2 0x0
Also i have tried three different Kernels so i am pretty sure this is going to be a hardware issue.
I may be wrong though, in my case it could be a task killer.
Need help! What can we do?
My cousin had the same problem but, It did happenned on battery power, he did not activated the GPS or Google Map.
The phone is practically bricked. It does not boot to android. We tried everything and came up with no results. Even we get the battery off and waited like a minute or so, plug it back and try to turn it on and it just got us to the same screen with the message saying something about kernel panic upload mode and a bunch of red numbers at the upper left corner. He does not installed any task killer either.
I think he was trying to install a .zip file from the SD Card in clockwork recovery mode. Now we can't even get to recovery mode!
What can we do?
hardware problem
I have been running on I997UCKI4 rom. Now a days the phone suddenly keeps getting into "user fault kernel panic upload mode" and phone would not even go into 3e recovery mode.
I have to take out the battery and put it back again. It keeps heating up until I do that.
Please help.
My original vibrant had this error...
turns out was bad hardware, replaced phone and havent had the problem since.[lots of other problems but not this one]
good luck
i have some issue too
anyone can resolve it?
i get this when i reload new ROM for my galaxy tab..
always shown "KERNEL PANIC RELOAD MDOE"
please help
Same problem
Mine too. What should I do?
I was flashing to stock firmware. Then this error appeared. and i couldn't restore because it doesn't even boot.
PLease help asap. It was my birthday gift.
its nothing to do with GPS.
Jnt
My samsung infuse 4g keeps turning itself off. If I take the battery out then put it back, the phone starts working eventually shuts down again.and gives message user fault not kernal panic upload mode And phone going heat also. Plz tell solution
do anyone find any solution please?
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
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!!!
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...