Hi all. I have been using a 6833 for about 5 months now and it has been problem free. Today while reading a book on aldiko i paused, locked the screen and later when i tried to wake the phone with the power button the backlight of the lcd turned on, but nothing appeared. Since then i have tried to restart the phone by pressing power+volup, the phone does the triple vibrate and shuts down but nothing appears on screen when i turn it back on. Same is the case with the hard reset, the red button under the flap. I have also tried to restore the phone by using flashtool and 108 ftf. The phone is detected properly by the computer but the display remains blank. Only the backlight turns on.
Any help in figuring this out would be appreciated.
Oh and just before this happened i had manually adjusted the screen brightness and turned auto backlighting off and then on.
makfreeman said:
Oh and just before this happened i had manually adjusted the screen brightness and turned auto backlighting off and then on.
Click to expand...
Click to collapse
when you did the FTF did you do a full wipe?
blueether said:
when you did the FTF did you do a full wipe?
Click to expand...
Click to collapse
Used Flashtool and wiped cache, data and appslog, i believe that means a full wipe.
I know the phone is on, i can use the touchscreen from memory for receiving calls. But there is no display. Since i bought it off of amazon i don't have any warranty on it either. Any help or guidance into diagnosing the problem would be appreciated.
Hi,
Had the same exact problem to solve it I actually had to sent it in Sony service to have it reinstated to factory settings.
Now everything is fine.
pavlos46 said:
Hi,
Had the same exact problem to solve it I actually had to sent it in Sony service to have it reinstated to factory settings.
Now everything is fine.
Click to expand...
Click to collapse
Could you elaborate on "reinstated to factory settings". Because sending it to sony is out of the question for me.
As far as i know, flashing a ftf means your phone is wiped completely so in essence its restored to factory settings.
Well I actually was under the exact same impression myself, even my local Sony support centre though so too but when we send it to the main support centre in Athens and they reinstated the problem got solved.
To me it seems that the main Sony support centres have different s/w for wiping and flashing.
Pavlos
pavlos46 said:
Well I actually was under the exact same impression myself, even my local Sony support centre though so too but when we send it to the main support centre in Athens and they reinstated the problem got solved.
To me it seems that the main Sony support centres have different s/w for wiping and flashing.
Pavlos
Click to expand...
Click to collapse
That sounds promising. I'll be back in the US in april maybe i can send it in for repair then.
This device has dynamic backlight that if I am correct was adjustable on versions until 4.3 so have a good look around for that ftf. I presume you are on a non Gpe version.
Also have you used a manual brightness app, cause you could have just turned your backlight way down, try by memory to turn autobrightness back on. Easiest way by quick settings.
Pavlos
pavlos46 said:
This device has dynamic backlight that if I am correct was adjustable on versions until 4.3 so have a good look around for that ftf. I presume you are on a non Gpe version.
Also have you used a manual brightness app, cause you could have just turned your backlight way down, try by memory to turn autobrightness back on. Easiest way by quick settings.
Pavlos
Click to expand...
Click to collapse
Are yiou suggesting that brightness could have been set very low and even flashing a FTF wouldn't have fixed it? Just before this issue happend i was turned off the autobacklight and turned it back on.
Related
I tried to set the screen timeout to whatever interval is there, 15sec and up, none of my trials worked to get my screen to turn off and lock which is killing my battery at no time
only when i press the lock buttondoes it turn off.. but when i have the mobile in my pocket it usually press some button accidentally and that will keep the screen on :s
i searched the net to see if anybody else have had this problem but found nothing, and not even the applications on the market made this screen timeout work!! So i wonder if anyone have any idea about how such a problem could be fixed or what caused it?
amlood said:
I tried to set the screen timeout to whatever interval is there, 15sec and up, none of my trials worked to get my screen to turn off and lock which is killing my battery at no time
only when i press the lock buttondoes it turn off.. but when i have the mobile in my pocket it usually press some button accidentally and that will keep the screen on :s
i searched the net to see if anybody else have had this problem but found nothing, and not even the applications on the market made this screen timeout work!! So i wonder if anyone have any idea about how such a problem could be fixed or what caused it?
Click to expand...
Click to collapse
its a malfuntion, no fix, need RMA, need a new mainboard
you can check if the usb as massstorage works, problably not !!!!!
j
amlood said:
I tried to set the screen timeout to whatever interval is there, 15sec and up, none of my trials worked to get my screen to turn off and lock which is killing my battery at no time
only when i press the lock buttondoes it turn off.. but when i have the mobile in my pocket it usually press some button accidentally and that will keep the screen on :s
i searched the net to see if anybody else have had this problem but found nothing, and not even the applications on the market made this screen timeout work!! So i wonder if anyone have any idea about how such a problem could be fixed or what caused it?
Click to expand...
Click to collapse
when this happens to me, i just reboot my phone and screen timeout returns to work
you should replace your phone by claiming warranty for malfunction
It happns to me only when i use iphone lock or finger scanner and keep off the auto lock after booting.
just check it out or use simply lockscreen or goto.
pafaf said:
its a malfuntion, no fix, need RMA, need a new mainboard
you can check if the usb as massstorage works, problably not !!!!!
j
Click to expand...
Click to collapse
you were right, it is a maulfunction the usb massstorage does not work !!
and i got it back from maintainence only last week :\
thanx much
goooosh.. I just got my phone back from maintenance today and I have the same problems.. :S Gonna have to take a trip back tomorrow.. :S
i also got my o1 back today and i also experience the same problem. screen timeout doesnt seem to work and when i charged the phone it boot up and charge with a screen on. my board was replaced and it stayed at the shop for a week and now i have a screen timeout problem. It seems that their replacement board have all this problem. does anyone here have this problem too after their board have been change??
akitos said:
i also got my o1 back today and i also experience the same problem. screen timeout doesnt seem to work and when i charged the phone it boot up and charge with a screen on. my board was replaced and it stayed at the shop for a week and now i have a screen timeout problem. It seems that their replacement board have all this problem. does anyone here have this problem too after their board have been change??
Click to expand...
Click to collapse
OK, a quick test for you. Please follow these steps:
- go to Menu - Settings - Applications - Development
- check if "Stay awake" is enabled.
If it is, then that's why your phone behaves like that, because you requested it. Uncheck that option - problem solved and you should facepalm yourself for sending the phone in service over this trivial issue.
If not, then you indeed have a problem and you should demand some explanations at the service center.
masteryx said:
OK, a quick test for you. Please follow these steps:
- go to Menu - Settings - Applications - Development
- check if "Stay awake" is enabled.
If it is, then that's why your phone behaves like that, because you requested it. Uncheck that option - problem solved and you should facepalm yourself for sending the phone in service over this trivial issue.
If not, then you indeed have a problem and you should demand some explanations at the service center.
Click to expand...
Click to collapse
actually it is already disabled by default and it is the cause of the problem. Maybe the board they replace is defective. I noticed that most of the people having the same problem as mine are those people who have new board. Ill bring this back tomorow. it sucks! i have to wait for another week!
mass storage doesnt work for me too. have to bring this back again tomorow.
same issue to me...
it just got back from service center with a brand new logic card.. and now it does not work screen time out neither usb functionalities =_=
done many test (different computers and s.o., several reboots... nothing worked)
MAXT3R88 said:
same issue to me...
it just got back from service center with a brand new logic card.. and now it does not work screen time out neither usb functionalities =_=
done many test (different computers and s.o., several reboots... nothing worked)
Click to expand...
Click to collapse
i suggest u return it back immediately. I already return mine a while ago. it seems most of their replacement boards are defective. So its best to be very cautious in modding the phone if u wish not to have a defective board and save ur self the hassle of going back in forth at their center.
There is meant to be a remedy.
The replacement boards require a hard factory reset(see user manual for process) followed by a power down and battery removal then power up, once in users unit.
I am yet to test this out and will give an update next week.
Perhaps this forum could help.
I received a used Xperia Mini [ST15i] as a xmas present from my bro-in-law.
It has Android 2.3.4 – Kernel is 2.6.32.9-perf
Build is 4.0.2.A.0.62
It had a lot of his apps on and foolishly I went into application manager and deleted a whole lot of stuff when suddenly the phone went into what I originally thought was a Haptic Feedback loop.
I was unable to power off so I had to remove Battery and restart from there. The loop starts slowly with one or two vibrates every 10 seconds then it becomes rapid and settles into an almost clock like rythm, two vibration per second.
I tried to get into settings to turn off the haptic feedback indicator but it seems like for each vibration [or tick] , an invisible ‘enter’ has been pressed somewhere on the screen so the only way to get into settings is to press the ‘back’ button and at the same time press the ‘settings’ button to interrupt the loop and after 5 vibrations or so I am able get into the ‘settings’ menu and un-tick the Haptic indicator. The phone goes quiet but the ‘clock’ or what ever process is looping continues. It completely blocks me out from doing anything unless I can interrupt it via pressing the back button.
To try get over this, I have reloaded the complete 150mb software via sony update. Afterward the problem still persisted. I have done both factory resets and still the loop process continues.
Have I screwed the Kernel? Any help or advice would be great. The phone is locked .
Sorry for you but it's an hardware problem (related to touchscreen). You have to send you mobile back to Sony.
Mine had the same issue out of the box and I had it replaced. The guy in the store told me it affects some batches (don't know which ones).
Soda_47 said:
Sorry for you but it's an hardware problem (related to touchscreen). You have to send you mobile back to Sony.
Mine had the same issue out of the box and I had it replaced. The guy in the store told me it affects some batches (don't know which ones).
Click to expand...
Click to collapse
Thanks Soda. Just chatted with Sony. Luckily phone is still under warranty. Cheers
I'm happy to help
Hi folks,
I have had this issue a few times now, basically when I try to tun wifi on using the quick settings tile it doesn't come on, if I then go into settings-wifi & try to turn it on using the toggle the toggle moves but doesn't change to the blue colour or say it is on, it just goes a light blue colour, if I then back out of settings & try again the toggle is back to off. I then basically have to turn the phone off & then back on (the quick boot feature in developer settings doesn't do anything) & when it boots up wifi is on.
Anybody else had this issue? The phone is getting replaced in a few days due to gap issues, over heating & camera lens not being centred anyway but just though I would check.
Cheers.
No one else have this issue?
BanziBaby said:
No one else have this issue?
Click to expand...
Click to collapse
I had this issue on .55 firmware. Haven't noticed it on .69 yet.
Cheers for the reply Jackos.
I had it both on the .55 firmware as well as the .69 firmware, have done factory reset etc but it still happens every few days, really stumped by it.
BanziBaby said:
Cheers for the reply Jackos.
I had it both on the .55 firmware as well as the .69 firmware, have done factory reset etc but it still happens every few days, really stumped by it.
Click to expand...
Click to collapse
I think I saw someone posting this issue at Sony Support Forums, let's hope they fix this in the next firmware revisions.
I'll keep you posted if this happens to me again on .69.
I have this happening to me, on .69 fw. Normally a restart will do.
Sent from my D6503 using XDA Premium 4 mobile app
@Jackos Cheers for keeping us posted mate
@pohsze Yeah mate, only way I have found so far to resolve it is to power off then back on, strange thing is wifi is on when phone finishes booting lol.
I have the exact same problem and I am on .55.
Sometimes I can't even turn Wifi off so I have to reboot. It is really weird because I don't know what triggers the bug.
I almost decided to return the phone but it is hard to recreate the error, and a reboot fixes it so I don't know if my phone company will accept the bug.
Since others have the same problem I hope they fix it in the new updates. Will come back when the .69 is released here.
I have same problem - switching in & out of AIrport mode cleared it.
I have the same problem.
First time I encountered it this morning.
Not sure from when wifi was not working for me.
In wifi settings no networks were shown.
Turning on wifi button would go light blue . . . but nothing would happen.
I selected Airport mode. Waited a moment. Then exited Airport mode . . . and wifi started working.
I'm on firmware .55
BanziBaby said:
Hi folks,
I have had this issue a few times now, basically when I try to tun wifi on using the quick settings tile it doesn't come on, if I then go into settings-wifi & try to turn it on using the toggle the toggle moves but doesn't change to the blue colour or say it is on, it just goes a light blue colour, if I then back out of settings & try again the toggle is back to off. I then basically have to turn the phone off & then back on (the quick boot feature in developer settings doesn't do anything) & when it boots up wifi is on.
Anybody else had this issue? The phone is getting replaced in a few days due to gap issues, over heating & camera lens not being centred anyway but just though I would check.
Cheers.
Click to expand...
Click to collapse
Hey I get it sometimes too, just press and hold on the wifi icon and then manually turn wifi on in the wifi settings, works fine after that. Just a minor bug.
I have also experienced the exact same problem on the newest firmware. Only happened once, and going in to the actual WiFi settings didn't solve it, since the button turned light blue as described. Strangely after a little while when the phone was inactive it started working all by itself.
Phones:
Samsung Galaxy S I9000
Asus Padfone 2
Sony Xperia Z2
____________________________
Android user since mid 2010
Same issue
Hello all,
I have the same problem when I tried to turn Wifi on by accessing Quick Settings and pressing Wifi button.
It works again after 10-15 times pressing Wifi icon.
It just happened last few days and I didn't have any system update recently.
Im also having the same issue. Anyone managed to get a fix for this?
Same issue
Im also having the same issue.
Anyone had a solution for this :/ ?
I don't think i have this issue yet since I just got the phone, but I remember when I setup my wifi connection there was an option to enable/disable wifi based on location. Could it be that the phone's GPS location hasn't update yet and think you are close to your wifi location thus won't let you turn on? May be disable this feature and report back if you guys still have this issue.
I am on .167 and this is happening to me more and more often it seems like it is getting worse. If I go into settings/wifi I get a white screen that says tunring wifi on and no further change. This usually starts occurring 18 hours or so after I reboot. It looks like no one has any idea what is wrong.
Fred
I have this same issue, a restart fixed this fora couple of days but now it seems the Wifi wont start up at all
Still had some warranty so returned the phone at the store that I bought it at.
Had the issue from the moment I got the phone from my gf (she has a new one) and did a factory reset.
After that I have flashed 3 different versions on it and for all the WiFi didn't work.
Let's see what happens after I get the phone back..
SOLVED:
It's a hardware issue. If you have this problem, ask Sony for a screen replacement.
Sony replaced a new Z2 for me, now I got no more touch issues.
Manufacturing Date:
My previous Z2: 14W20 (with bug), @gamer649 with 14W28 has bug too
My new Z2: 14W33 (without bug)
However, @mariosraptor with earlier batch 14W17 reported no bug.
Click to expand...
Click to collapse
Firmware: Xperia Z2 running 17.1.1.A.0.402 and latest 17.1.2.A.314 firmware (previous firmware I'm not sure)
Bug: Glove mode randomly turns on, but in display setting it shows off.
Details:
This happens all the time. Screen sensitivity increases as if glove mode was turned on. But glove mode is actually showed as off in display settings.
Findings: After several days of testing. I found some interesting things that may be helpful:
- 100% bug appears upon launching a game call tower of saviors (by madhead)
- 50% bug appears upon launching keyboard in messaging apps (wechat, whatsapp, fb messenger)
- 50% bug appears after redirecting to messaging apps from notifications drop-down.
- Sometimes it got resolved by pressing the app drawer icon from home screen.
- Not caused by root because bug appears after reflashing firmware.
Temporary workaround: Turn the display off and on. Usually last no more than 1 minute before this bug reappears.
Failed solutions:
Not working steps:
1. Turn glove mode on and off.
2. Turn off tap to wake up.
3. Reduce and increase screen time out.
4. Apply and remove screen protector and tempered glass.
5. Turn x-reality on and off.
6. Turn auto-rotation on and off.
7. Turn smart backlight control on and off.
I also tried all these:
1. Use PC companion to do a phone repair. (bug remains)
2. Using the phone, I did factory reset + erase internal storage (bug remains)
3. Using the phone, I did a factory reset (bug remains)
If you need any info from me I'm happy to provide. This bug is really annoying, it causes unwanted touches and keyboard typos.
zhuhang said:
Firmware: Xperia Z2 running 17.1.1.A.0.402 and latest 17.1.2.A.314 firmware (previous firmware I'm not sure)
Bug: Glove mode randomly turns on, but in display setting it shows off.
Details:
This happens all the time. Screen sensitivity increases as if glove mode was turned on. But glove mode is actually showed as off in display settings.
Findings: After several days of testing. I found some interesting things that may be helpful:
- 100% bug appears upon launching a game call tower of saviors (by madhead)
- 50% bug appears upon launching keyboard in messaging apps (wechat, whatsapp, fb messenger)
- 50% bug appears after redirecting to messaging apps from notifications drop-down.
- Sometimes it got resolved by pressing the app drawer icon from home screen.
- Not caused by root because bug appears after reflashing firmware.
Temporary workaround: Turn the display off and on. Usually last no more than 1 minute before this bug reappears.
Failed solutions:
Not working steps:
1. Turn glove mode on and off.
2. Turn off tap to wake up.
3. Reduce and increase screen time out.
4. Apply and remove screen protector and tempered glass.
5. Turn x-reality on and off.
6. Turn auto-rotation on and off.
7. Turn smart backlight control on and off.
I also tried all these:
1. Use PC companion to do a phone repair. (bug remains)
2. Using the phone, I did factory reset + erase internal storage (bug remains)
3. Using the phone, I did a factory reset (bug remains)
If you need any info from me I'm happy to provide. This bug is really annoying, it causes unwanted touches and keyboard typos.
Click to expand...
Click to collapse
- i had ghost touch issues most on 402 firmware most
-tried 55 which i had this prob, 69, 438 and 402 i had
-CM11 didnt seem to have this issue
try flashing CM11 or something non stock based, if it still happens then we can conform its a Stock Rom issue
(i dont have a Z2 atm so cant test for you)
Envious_Data said:
- i had ghost touch issues most on 402 firmware most
-tried 55 which i had this prob, 69, 438 and 402 i had
-CM11 didnt seem to have this issue
try flashing CM11 or something non stock based, if it still happens then we can conform its a Stock Rom issue
(i dont have a Z2 atm so cant test for you)
Click to expand...
Click to collapse
I will only go as far as root. To flash CM11 i need unlock BL right.
I got an idea to disable glove mode and see if it helps.
zhuhang said:
I will only go as far as root. To flash CM11 i need unlock BL right.
I got an idea to disable glove mode and see if it helps.
Click to expand...
Click to collapse
yes you need unlocked bootloader
i think ill test this my self when i get my Z2 back, ill be trying alot of things, aka disabling glove mode from the kernel n stuff
my freind had the same issue ans she came up with this info below, she didnt test any other but these Roms below
CM11-
no ghost touches
FXP-
uncommon
438-
allways
402-
always
69-
uncommon
55
uncommon
The new 4.4.4 firmware still has this bug! Looks like we need to bring this up to Sony's notice.
I am facing this problem, too.
Got this problem shortly after i bought my Z2 from time to time, mostly while playing Ingress. Than I dropped my phone and had to replace my screen (cracked). The replacement display went totally mad after a few days, I had ghost touches everytime even while the device was lying untouched on the table, the device was practically unuseable. (See video HERE). The repair shop replaced the display again, and it went back to "normal" with ghost touches as described in the first post.
Here's another thread about this issue.
AlanDS said:
The new 4.4.4 firmware still has this bug! Looks like we need to bring this up to Sony's notice.
Click to expand...
Click to collapse
Furchendackel said:
I am facing this problem, too.
Got this problem shortly after i bought my Z2 from time to time, mostly while playing Ingress. Than I dropped my phone and had to replace my screen (cracked). The replacement display went totally mad after a few days, I had ghost touches everytime even while the device was lying untouched on the table, the device was practically unuseable. (See video HERE). The repair shop replaced the display again, and it went back to "normal" with ghost touches as described in the first post.
Here's another thread about this issue.
Click to expand...
Click to collapse
Yup, after update the bug still there. Now I reverted back to 4.4.2 (at least root is possible)
I wonder if this is a bug of Sony or bug of game. But since many are facing it too, I think it is Sony.
In my Z2, I can recreate this bug by running a game call Tower of Saviors.
Immediately after opening this app, the bug will be there.
But after some time being outside the game (display remains ON) the bug went off but easily recreated.
This problem causes me to type wrongly almost all the time.
zhuhang said:
Yup, after update the bug still there. Now I reverted back to 4.4.2 (at least root is possible)
I wonder if this is a bug of Sony or bug of game. But since many are facing it too, I think it is Sony.
In my Z2, I can recreate this bug by running a game call Tower of Saviors.
Immediately after opening this app, the bug will be there.
But after some time being outside the game (display remains ON) the bug went off but easily recreated.
This problem causes me to type wrongly almost all the time.
Click to expand...
Click to collapse
Some devices have more sensitive touchscreens which cause ghost touches, its a manufacturing defect
I found mine does this after being staticly charged by something, clothing or anything else that would cause static, i just touch my phone on a live and it just removes of that odd buzzy feel and also my ghost touches ???
As for 4.4.4, its not rootable but pre-rootable or even rootable via flashing if you know how
Envious_Data said:
Some devices have more sensitive touchscreens which cause ghost touches, its a manufacturing defect
I found mine does this after being staticly charged by something, clothing or anything else that would cause static, i just touch my phone on a live and it just removes of that odd buzzy feel and also my ghost touches ???
As for 4.4.4, its not rootable but pre-rootable or even rootable via flashing if you know how
Click to expand...
Click to collapse
You have no idea regarding the problem we are talking right now.
It's not sensitivity issue, its not a touch issue after all, its glove mode being activated somehow all the time.
zhuhang said:
You have no idea regarding the problem we are talking right now.
It's not sensitivity issue, its not a touch issue after all, its glove mode being activated somehow all the time.
Click to expand...
Click to collapse
even if turned off?
i had a simular issue but since i went and Reset my phone via flashtool i havent had it. it only happpend on 402 firmware
Does it show where it is touching? Because glove mode shows with a dot. If doesn't than it is ghost touch. If it does then yes glove mode automatically gets enabled.
Envious_Data said:
even if turned off?
i had a simular issue but since i went and Reset my phone via flashtool i havent had it. it only happpend on 402 firmware
Click to expand...
Click to collapse
Glove mode is turned off.
mariosraptor said:
Does it show where it is touching? Because glove mode shows with a dot. If doesn't than it is ghost touch. If it does then yes glove mode automatically gets enabled.
Click to expand...
Click to collapse
It doesn't show the dot but I can tell its glove mode, the sensitivity is same as if glove mode is turned on.
I think that dot will only appear if you turn the glove mode ON in settings.
For this problem, I suspect the device is using glove mode sensitivity values instead of normal sensitivity.
I guess there's a touch profile for glove mode in the system, and some apps somehow tricked the system to use that.
Therefore, there's no dots/rings when we hover our fingers.
I got one game (Tower of Saviors) which 100% triggers this situation.
Mind trying on your devices?
I will try it lAter on.
I can recreate this bug most of the time by opening Facebook app or opening keyboard to type on whatsapp message box..
As said earlier, Glove mode is off.. But still the touch has been registered just like we are on glove mode by hovering the fingertip just above the screen... It doesn't shows the boxes when we touch.
I tried to bring this to Sony's notice by posting on their support forum. But nobody supported it or acknowledged it.. So obviously they have ignored. I request all of you who are having this problem to post on Sony's support forum so that we can bring it to their notice. Or else this will never be fixed.
AlanDS said:
I can recreate this bug most of the time by opening Facebook app or opening keyboard to type on whatsapp message box..
As said earlier, Glove mode is off.. But still the touch has been registered just like we are on glove mode by hovering the fingertip just above the screen... It doesn't shows the boxes when we touch.
I tried to bring this to Sony's notice by posting on their support forum. But nobody supported it or acknowledged it.. So obviously they have ignored. I request all of you who are having this problem to post on Sony's support forum so that we can bring it to their notice. Or else this will never be fixed.
Click to expand...
Click to collapse
I posted this issue long time ago, no help too.
I even emailed Sony about this but they say it should not be happening on fully working Z2, and ask me to go to repair centre.
LMAO, what can repair centre do? Deploy an software update on the spot? Idiots.
Anyway, I don't expect 5.0 update to fix it too. Unless someone can get their attention.
I'm wondering why many users don't have this problem. My unit is one of the 1st batches.
Mine is from 14W20... Looks like only few handsets are having this hypersensitive problem(Or people are not noticing it).
Anyways, one of my friend will be buying a new Z2 in coming days. I will check in his device.
I downloaded the game and it worked fine for as long as I played it. I even made a screen record to see while I changed to glove mode. Uploading it to YouTube. Will share link.
Screen record: http://youtu.be/Z0YhsIMaqvE
mariosraptor said:
I downloaded the game and it worked fine for as long as I played it. I even made a screen record to see while I changed to glove mode. Uploading it to YouTube. Will share link.
Screen record: http://youtu.be/Z0YhsIMaqvE
Click to expand...
Click to collapse
Which game, why do you have to change to glove mode?
I just changed to show that glove mode gets enabled only when I want to
mariosraptor said:
I just changed to show that glove mode gets enabled only when I want to
Click to expand...
Click to collapse
Are you trying to prove that the bug doesnt exist?
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!!!