Related
Hi guys. I'm totally new to the android/smart phone world btw. Anyways, I recently got my Samsung Galaxy S2... first thing I noticed, my touch screen wasn't working. I popped the battery in and out and then it started working as it should.
My phone was working fine this morning, then all of a sudden out of no where, the touch screen stopped working again. I've tried turning on/off the phone multiple times. I've taken out the battery and even my SIM card nothing... i'm worried.
Has this happened to anyone else? Is there a fix? Do i have to go through Samsung? I hope not. Incase anyone asks, I did not root my phone.
Any help/feedback would be appreciated.
When the touchscreen stops working... were you charging the phone at that time?
The first time i turned on my phone, was actually by accident and it was charging.
However, just earlier now, it was not. it was just sitting on my computer desk. The home button, lock button and touch capacitive buttons work.... but i can't get past the lock screen
you could try a factory reset to see if its software related, but it sounds like hardware. I would definitely Return the phone .
I guess I can't do a factory reset, since I can't get into any of the menus... man this sucks. I spent $900 *gulp*
To do a factory reset,
1. Turn the POWER OFF, pull the battery out and put it back again.
2. Simultaneously press and hold the Volume Up, Home and Power button
3. If the Samsung Symbol appears, release the Power button
4. A Boot Menu will then show, Use the volume up/down to choose wipe data/factory reset.
touch screen not needed this way.
oo that's interesting... I tried it. and it didn't get to a boot menu. maybe I was doing it wrong. I tried a few different ways, but no success. It turns out I have warranty with the store. They're going to replace it for me Thanks for the feedback guys. Awesome forums.
Something similar happened to me yesterday. When I had the in-box USB cable attached to a BoxWave VersaCharger (combined AC/DC charger), and the VersaCharger was plugged into 120V AC, the touchscreen would stop working. As soon as I unplugged the USB cable from the SGS2, or plugged the VersaCharger into a 12V DC lighter socket, the touchscreen would work fine.
I've got the same problem as the OP... I had my phone charging overnight and this morning when I first went to use the phone I could not unlock the screen. I could wake the screen via the home button, and see I had a missed call etc but it just wasn't responding to touch. BTW I can't remember if when I first tried to unlock the phone if it was charging or not but really this shouldn't matter.... oh and btw, I'm not rooted or anything either! Naturally I rebooted the phone but still the same problem....so I tried a battery pull and still the same problem. Just now I did a factory reset but the touch screen still isn't working! I guess this is a hardware problem so I'm going to get it fixed under warranty by Samsung! Gutted that I will likely be without my phone for a week or 2!
EDIT, UPDATE...
Well, I was just on my way to the repair shop Samsung warranty had told me to take it too, and I took my sim card out to put in my old Hero (the only thing I hadn't tried!) and I couldn't believe it but the touch screen started working fine again! Weird, but that is now my advice if anyone else has a problem with their touch screen not working - oh and I took the sim out whilst the phone was still turned on. Crisis averted!
UPDATE 2
Sadly this has happened about 4 times to me now and I'm just waiting for the inevitable next time. Each time doing a factory reset then taking the sim card out seems to bring the screen back to life (though last time not immediately) but I shouldn't have to put up with this. Problem is, I don't want to send off a seemingly perfectly working phone to get repaired as I fear they will struggle to notice the problem, never mind fix it! I'm hoping a new firmware comes out soon, in the hope that it may resolve my issues...
Me as well ...
I have had this happen to me twice now (Touchscreen not responding).
The first time I had just installed a game and thought it must have been related to that. Pulled the battery and no joy, left it for a while and it came back to life...
Second time I was surfing the web and it stopped responding, pulled the battery and left it for maybe a minute but no joy .... pulled the battery again and left it for probably 20min and it came back to life. When it came back up I noticed the livewallpaper had been turned off and my widgets were gone from the homescreen.
What I did notice when it wasn't working was it had "safe mode" displayed at the bottom left of the screen
Have the Same Problem
Have the same problem i Mine and was super exicedat first it worked fine and after charging the touchscreen stopped working i pulled the battery out and put it back in but no luckso im gonna return mine to the shop hope they replace it
Moral:AT FIRST SUPER EXICTED BUT NOW SUPER ANGRY
Same issue - Is there ANY way to save my data before I send it in for repair/replace?
Hi all,
As of this morning, I have exactly the same issue as the OP. Screen doesn't react to touch, with the exception of the capacitive buttons. I found a dude on YouTube that had the same issue: youtu.be/0oIdllWiV4I
The last thing I did with the phone before it started misbehaving was to answer a call. The phone was on the charger when the call came in - I can't recall whether I unplugged it before answering, or after, or at all during the call. Not sure it has any relevance anyway, only mention it because I've seen reports of people's screens no longer reacting to touch when the phone is plugged in to a charger (apparently it even states in the manual that this may happen).
Anyway, whilst all my contacts, SMS, photos etc are backed up to the cloud, the same can't be said for my app data. Before I lose hours and hours of progress in various games, or all my settings in numerous other apps, etc, can anyone think of any way to get access to the memory of the phone, bearing in mind the following:
I can't connect to Kies to pull a back-up because bluetooth is currently enabled on the phone and when one connects the USB cable, it says "Activating USB mode will deactivate Bluetooth. Continue?" but I can't click the Yes button
I can't connect in USB mass storage mode because I can't navigate to the settings menu entry to enable it
I can't turn Bluetooth off in order to get Kies working, becuase I can't get to the settings menu or pull down the notification bar to reach the power control.
I can't use Voice input to control the device (on the off chance there was a "bluetooth off" voice command) because (presumably with the most recent firmware I flashed via Kies a few weeks back) for some reason Vlingo is no longer the app on the double-home button action. Instead it calls Samsung Voice and wants to walk me through a first use tutorial, but I can't click the next/skip buttons
I installed via Android Market push the app belonging to www_remoteaccessphone_com as it promises to be able to remotely switch bluetooth off, but the website says I haven't installed the app yet, presumably because alrhough I was able to install it without touching the phone, it probably needs to be run at least once to set it up, and I obviously can't do that
I can't start Kies Air to try and get my data that way (starting it would require using the touch screen)
Kies via bluetooth isn't supported on Android
Needless to say, the data I'm trying to retrieve is on the internal memory, not the SD card. As you can see I've been trying all sorts of creative things, but I'm fairly sure I'm screwed. Any bright ideas I haven't thought of?
blaubeer said:
Hi all,
As of this morning, I have exactly the same issue as the OP. Screen doesn't react to touch, with the exception of the capacitive buttons. I found a dude on YouTube that had the same issue: youtu.be/0oIdllWiV4I
The last thing I did with the phone before it started misbehaving was to answer a call. The phone was on the charger when the call came in - I can't recall whether I unplugged it before answering, or after, or at all during the call. Not sure it has any relevance anyway, only mention it because I've seen reports of people's screens no longer reacting to touch when the phone is plugged in to a charger (apparently it even states in the manual that this may happen).
Anyway, whilst all my contacts, SMS, photos etc are backed up to the cloud, the same can't be said for my app data. Before I lose hours and hours of progress in various games, or all my settings in numerous other apps, etc, can anyone think of any way to get access to the memory of the phone, bearing in mind the following:
I can't connect to Kies to pull a back-up because bluetooth is currently enabled on the phone and when one connects the USB cable, it says "Activating USB mode will deactivate Bluetooth. Continue?" but I can't click the Yes button
I can't connect in USB mass storage mode because I can't navigate to the settings menu entry to enable it
I can't turn Bluetooth off in order to get Kies working, becuase I can't get to the settings menu or pull down the notification bar to reach the power control.
I can't use Voice input to control the device (on the off chance there was a "bluetooth off" voice command) because (presumably with the most recent firmware I flashed via Kies a few weeks back) for some reason Vlingo is no longer the app on the double-home button action. Instead it calls Samsung Voice and wants to walk me through a first use tutorial, but I can't click the next/skip buttons
I installed via Android Market push the app belonging to www_remoteaccessphone_com as it promises to be able to remotely switch bluetooth off, but the website says I haven't installed the app yet, presumably because alrhough I was able to install it without touching the phone, it probably needs to be run at least once to set it up, and I obviously can't do that
I can't start Kies Air to try and get my data that way (starting it would require using the touch screen)
Kies via bluetooth isn't supported on Android
Needless to say, the data I'm trying to retrieve is on the internal memory, not the SD card. As you can see I've been trying all sorts of creative things, but I'm fairly sure I'm screwed. Any bright ideas I haven't thought of?
Click to expand...
Click to collapse
flash it with CF-root, boot into CWM recovery, do a nandroid backup after that, use CWM recovery again to mount USB storage, connect to your PC and pull everything off.
Nitrile said:
flash it with CF-root, boot into CWM recovery, do a nandroid backup after that, use CWM recovery again to mount USB storage, connect to your PC and pull everything off.
Click to expand...
Click to collapse
Thanks for the quick advice. I guess I'll need to use my girlfriend's phone to download CF-root and then transfer the SD card to my device. Quick question before I proceed though - is it possible to remove all traces of such tampering, since I've already made out with Samsung that I'm sending it in for repair, and I'm not sure they will honour the warranty if they see it has been rooted etc.
blaubeer said:
Thanks for the quick advice. I guess I'll need to use my girlfriend's phone to download CF-root and then transfer the SD card to my device. Quick question before I proceed though - is it possible to remove all traces of such tampering, since I've already made out with Samsung that I'm sending it in for repair, and I'm not sure they will honour the warranty if they see it has been rooted etc.
Click to expand...
Click to collapse
get a USB jig off ebay or amazon to reset the flash counter. should not cost more than 5 or 6 euros, shipped.
anyways you need to flash CF-root through ODIN if you are coming from stock. instructions are all in chainfire's cf-root thread.
Nandroid Restore
So I successfully rooted, used CWM to do a Nandroid backup, mounted the sd_card and saved the contents (including the nandroid backup) to my PC, reflashed the stock rom & kernel, usb-jigged it to get the counter back to zero/original and sent the phone in for repair. My efforts paid off as they repaired it without question under warranty. I just received the phone back and today set about restoring my backup:
Copied the sd_card contents I'd saved to my HDD back onto the phone
Re-roooted it with Cf-mod.
Used CWM to restore the backup I took before sending it in
It restored boot/system/data/cache successfully
selected reboot now in CWM
The result is that it is still missing all my apps. It only seems to have the "data" like my camera shots and SMS messages, system settings like whether bluetooth is on or off, the volume level, Wifi networks etc. So something was restored. But there is no Google Account configured, the lock screen picture is the default not the one I had beforehand, and as I said, all the apps - the main reason I did this whole thing as my personal data is all backed up to the cloud on a regular basis anyway - have not been restored. Am I confused? I thought a nandroid backup took a complete snapshot of everything, apps included.
Finding out the list of Apps I had in order to reinstall them is not an issue - I have a list of everything I had installed saved on AppBrain. But if I reinstall the apps, all the settings (or progress in the games) within those freshly installed apps will be back to square one, not where I left them, right? Or should I reinstall the apps and then restore the data partition over the top again?
Are you guys using any type of screen protectors, cause if you are, that may be the issue s their have been reports that the screen becomes unresponsive with certain screen protectors when connected to a charger.
However, if you are not using a screen protector, then I would suggest getting the unit replaced as you should not have to do anything, root or otherwise, to get the touchscreen working on a touchscreen phone
achillies400 said:
Are you guys using any type of screen protectors, cause if you are, that may be the issue s their have been reports that the screen becomes unresponsive with certain screen protectors when connected to a charger.
However, if you are not using a screen protector, then I would suggest getting the unit replaced as you should not have to do anything, root or otherwise, to get the touchscreen working on a touchscreen phone
Click to expand...
Click to collapse
Nope, no screen protector or any kind of case for that matter. Anyway, that isn't my issue anymore. The touch-sensitive unit was defective, the phone was repaired under warranty. My issue now is getting my apps & settings back. I have meanwhile read elsewhere that Nandroid doesn't back up the apps - pretty deceptive "backs up everything!" "it is like time travel" etc comments around here then.
Anyway, I reinstalled all the apps I had previously, and thought by reapplying the data partition from the nandroid backup it might then bring back the settings for the reinstalled apps. Instead all it did was remove all those apps again - now I am really confused. How come the restore DOESN'T bring back the apps I used to have, but DOES remove the ones I subsequently install. Does Nandroid touch the apps or doesn't it?
Touch screen not working
So i am having a very peculiar problem related to the GT-I9100 Touch Screen.
I bought the phone from Saudi Arabia and I live in Bangladesh at the moment. So for now I don't have warranty.
I bought it on 4th of this month. It had 2.3.3. So I updated it to 2.3.5. I did not use the phone much before that so I don't know if this problem was there before.
So here is the problem.
First time I noticed it when i pulled the phone from my pocket and could not unlock the pattern. First I thought I forgot the pattern. After sometime I noticed that i could not touch the buttons. I was dragging my finger over the points but there was no connecting line. I restarted the set. But it still did not work. After sometime I took the battery out. And after that it started normally and unlocked. And the touchscreen is totally fine.
I tested it using *#0*#. And every single point in the screen registers touch.
After that this happened couple of times. First couple of days I thought it was a pattern unlock problem. But i tried PIN and Password even using no unlock. It happened in every case.
So after couple of days it totally stopped happening.
But from yesterday it is happening again. And today it happened 3 times.
So today as I had no unlock protocol i tried tapping Home twice. As this brings on the voice command menu. And for the first time i was in the phone without touching the screen.And first i noticed the Menu and Back Soft keys works.And the touchscreen still does not work. And i noticed some thing weird. Always some thing in the screen is Selected. In Menu the + Icon is selected. In first screen the Map icon is selected. Also in Recent Apps the first App is selected. So after a lot of reboots it is back to normal again. Now i see something interesting. In the Battery Usage Graph i can see some really sharp drops. 3 times. Looks like when this happens phones charge takes a nose dive.
So here is the Gist.
Info related the Problem:
1. Usually happens when the phone is my pant pocket for sometime. It does not happen if it is sitting on the table.
2. Touchscreen gets totally disabled.
3. I have no idea why this happens.The exact reason behind it.
4. Battery Charge takes a nose dive when this happens. See the attached images.
5. I still don't know how to bring it back. Sometimes a simple reboot works. Sometimes I have to pull the battery. And sometimes it works on its own.
6. Every other function of the phone works. Like music playback using my UE 200vi music keys using PowerAMP, Siri(Android version), Call can be received using headset.
Battery nose Dive:
dl.dropbox.com/u/30943431/SC20111115-203017.png
dl.dropbox.com/u/30943431/SC20111116-202913.png
Also the selection
dl.dropbox.com/u/30943431/SC20111116-202146.png
So this is the thing. My biggest problem right now is, I don't know why it happens and I don't know how to bring it back from this situation. If I knew I could make sure I don't get it again or I would just fix it every-time. As when this happens I cant make calls or anything which requires the touchscreen.
So guys help me if you can by giving ideas. As i will not go back to KSA in 6 months. So buying a $550 phone unlocked was a total waste. As i cant use it here.
Thanks a million in advance.
---------- Post added at 09:29 PM ---------- Previous post was at 09:13 PM ----------
Sorry for this. But looks like i cant post outside links before i have 8 posts. So i removed the "ht tp : //" part of the links. Copy paste in browser address bar and it will open fine.
And also the next time it happens i will do a video to shou you guys.
Having the same problem while charging touch screen doesn't work
Stock charger and usb cable
i was on CM7 but that happend so i flashed stock but no luck
I will write more observations
Hi! I got a problem with my S3 (totally standard, no custom rom). It started yesterday... basically if i press home key, sometimes it takes me to the home screen, sometimes it takes me to other widget pages. The odd thing is that it's not always the same page... sometimes it's the 2nd from the left, sometimes it's the 3rd from the right... and so on. It seems to depend on what screen i was on last when i launched the application.
What happened? Anyone else had this odd behaviour? I already tried a softreset... doesn't work. ;(
Help me... thanks!
tharghan said:
Hi! I got a problem with my S3 (totally standard, no custom rom). It started yesterday... basically if i press home key, sometimes it takes me to the home screen, sometimes it takes me to other widget pages. The odd thing is that it's not always the same page... sometimes it's the 2nd from the left, sometimes it's the 3rd from the right... and so on. It seems to depend on what screen i was on last when i launched the application.
What happened? Anyone else had this odd behaviour? I already tried a softreset... doesn't work. ;(
Help me... thanks!
Click to expand...
Click to collapse
make a backup using titanium backup or Go Backup, and do a factory reset, then restore all your apps and settings.
this may help and shouldn't take longer than half hour.
It does sound like a software glitch that can be fixed with a reset.
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...