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?
Related
Ok, so I have a rooted Vibrant on stock firmware and I've been having a problem with my screen becoming unresponsive. It originally happened on a smaller level when the phone was newer and unrooted, however the problem has gotten much worse. I've done a factory reset of the phone along with a nandroid backup of it before the problem was severe, yet it comes back just as strong.
I already went through the problems with the no wake from setcpu, even thought it was my lock screen becoming unresponsive until I disabled it with NoLock. Also, I have the Logcat live wallpaper, and usually when you tap the screen, you can see the system processing the information, however when the problem occurs there is no response on the logcat live wallpaper. The phone doesn't freeze at all though. All the soft keys still work perfect as do the volume and power buttons.
Any ideas, tips, suggestions that might help me narrow down this problem? Could it be from a bad version of busybox? Autokiller maybe? I have it set to strict(was previously on aggressive) but no change. Maybe Autostarts is causing something to freeze up. Thanks for any help. Seams like these phones have alot of wake up issues.
I would reflash back to stock with Odin and see what happens when you don't have task killer, set CPU, etc. Also, be careful with autostarts
So I removed Autostarts and rebooted, same deal. I did a factory reset and still the same. I just unrooted a few minutes ago and the problem seams to have gone away. I'm gonna leave it like this for a bit without installing any apps and see what happens. Is it possoble I have a bad root.zip file or bad version of busybox? Doesn't make sense to happen when I have root, then go away when I don't. Any reason it could cause this? I'm really close to sending the phone back, but don't want to waste my time if it's just a bad root file or user error.
Well I don't know for a fact, hopefully someone more knowledgeable can chime in. Maybe when you are unrooted, changes made by autostarts no longer have the permissions to affect anything. Personally I would use Odin (have done it twice already) and start from scratch. But then you risk accidentally screwing up the phone if something goes wrong.
I removed Autostarts and rebooted just to make sure the changes took effect though. Even did a factory reset. Those removed all apps that required root access and the problem was still so bad it took me an hour to get the screen responsive again. Once I did get into my phone I booted into recover and unrooted. Restared the phone and now the issue seams to have gone away. Touch screen is very responsive now which leads me to believe it was something that had to do with the root file i'm flashing, or possibly busybox. Very very strange.
Hopefully someone much smarter than me could give some insight as to what could potentially cause the touch screens to just stop recieving signal. It's just bizarre that the phone continues to run fine, just not the screen.
I am using CM7 latest weekely every thing is perfect but now suddenly my phones screen turns on like call is coming and turns back off after 2 sec and this happens randomly.
is this expected behavior?
is there any work around?
My fiancee has an atrix that is totally stock and hers just started doing this yesterday. I would also like to know the answer to this. I was thinking it was a hardware issue with the power button but hopefully i am wrong, that way I dont have to mess with a warranty exchange. Any help would be appreciated.
by any chance have u just start using this app "Memory Booster - RAM Optimizer" if yes then this might be the one, i have just messed around in its settingsd and no screen wakup problems so far
https://market.android.com/details?...xLDEsImltb2JsaWZlLm1lbW9yeWJvb3N0ZXIubGl0ZSJd
No. The only apps that I think might cause this that I have on her phone is beautiful widgets and a data toggle. She has had these apps on there for awhile and the phone just started to act up.
Sent from my MB865 using xda premium
Both me and my brother own atrix and it happens on both.It was happening on stock 2.3.4 and now on cm7 as well it must be something with the phone not a rom related issue
i also have beautiful widgets, can sk8trix conform that his and his brother phone have this app too. if yes then this might be the cause. or we have to tell each other whole list of apps that we have installed to narrow down the culprit.
On her phone I have all of her apps that are supposed to sync turned off. I recently installed data enabler for her so she would have a data toggle on her home screen. I use advanced task manager to kill her apps by force stopping them. Last night I used it and closed everything and turned her screen off. 5 minutes later it come on for about two seconds and shut off. I have been looking at what apps might be causing this and really dont see anything unusual except for the data enabler and beautiful widgets. I will uninstall both of those and report back later on to let you know the result. Hopefully someone else will come along with a better solution.
xateeq said:
i also have beautiful widgets, can sk8trix conform that his and his brother phone have this app too. if yes then this might be the cause. or we have to tell each other whole list of apps that we have installed to narrow down the culprit.
Click to expand...
Click to collapse
I don't use beautiful widgets ever.....I even tried with a clean install no apps installed except stock cm7 apps and google apps and it still happened so I gave up trying to figure it out.
it doesn't shorten my battery life at all so I don't worry however if there is a fix I will use it because it is annoying.
Edit the only time the phones wake up by themselves is right after we hit the power button to turn the screen off or when the phone firat boots and is still locked it will turn the screen off and turn it back on the dim again.
I dont think its cm7 issue cos i was at weekly # 4 and there was no issue then i flashed tuch recovery and after that boot it started happening. Then i flashed latest weekely and reverted back to old recovery. And i agree this only happen when i turn screen off (randomly)
OK here is where I am at now with this problem. I uninstalled both apps and it seems to be ok for the time being, but my fiancee told me she had been receiving weird messages in her notification bar. I looked into it and she was getting ads in her notification bar. So I downloaded AirPush Detector from the market and ran a scan on her phone and it detected a couple of apps pushing notifications. I got rid of the apps and now im back to checking the phone again. I dont know if that AirPush app would help you guys out or not but it would hurt to try.
since i have started this thread my problems have gone away like a little *****, and i dont know how to recreate this problem any more so i am stuck with no problem no solution thing.
12 hrs passed no problem so far.
It was apps in the background running. Airpush helped. I told her from now on no more free apps, i would rather buy them then fight this **** again. I put the data toggle and beautiful widgets back on her phone and it's ok. Thanks for your guys input.
Sent from my MB865 using xda premium
tmease1 said:
I use advanced task manager to kill her apps by force stopping them. Last night I used it and closed everything and turned her screen off. 5 minutes later it come on for about two seconds and shut off. I have been looking at what apps might be causing this and really dont see anything unusual except for the data enabler and beautiful widgets. I will uninstall both of those and report back later on to let you know the result. Hopefully someone else will come along with a better solution.
Click to expand...
Click to collapse
I am having The same problem with my Samsung Galaxy ace Gt-5830i.
Earlier it had problems with charging and SD card. So we took it to authorized service center. And they said they had formatted the phone and installed stock ROM on it. They also replaced the charger port. But now after two days the phone screen is turning on and off at repeated intervals (for about 2 Seconds). So what might be the problem.
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
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!!!