Database Develop

blank screen but phone ON!!!!

Has anyone had this issue?
I have tried a few different ROM's and have had this problem on all, the phone will work but sometimes when the phone is locked and asleep you cannot get the screen back.
If you ring the phone it will ring but you can't wake the phone up (the screen is off).
If I then pull the battery and reboot all is well until the next time, which is random.
I will remove all my programs to see if there is one of them causing the issue, I don't believe it is the rom as it has happened on a few of them.

Have you wiped your phone when flashing the different roms? I've had it sometimes, i think it could be a ram management issue...

Talon26 said:
Have you wiped your phone when flashing the different roms? I've had it sometimes, i think it could be a ram management issue...
Click to expand...
Click to collapse
Yeh, I always do a factory/wipe, dalvik cache wipe.
I think it might have been TW4.5, I did some research and installed TW4 Manager I then updated TW4.5 to the latest Version. So far it hasn't happened yet but i'll give it a couple more days.
Thanks.

Yh ive been reading and TW4 generally accelerates the issue (because its a ram hog? not sure i dont use it) Im currently using Golauncher with system tweaks, but was told that nemus launcher and system tweaks was a better combination... Seems to be working, ive had less force closes or issues of that type

it's the proximity sensor. needs replaced.

pch.radu said:
it's the proximity sensor. needs replaced.
Click to expand...
Click to collapse
I don't think so...
The proximity sensor is only used when your in a call. It should not have any effect when he tries to wake it from his pocket after a while...

Well i am on 2.3.5 and using golauncher and never had any problems. Still my best guess is the damn sensor. On samsung apps there is an app called sensors i think and that app tells u what is working inside the phone.
Sent from my GT-I9000 using XDA App

If I recall correctly yeah I had this issue once on JVR and once on JVS and now on JVT I got it a few hours ago
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
pch.radu said:
Well i am on 2.3.5 and using golauncher and never had any problems. Still my best guess is the damn sensor. On samsung apps there is an app called sensors i think and that app tells u what is working inside the phone.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Sounds like a great app but seeing as the screen doesn't turn on that app might as well be useless in this case

No screen turns on, its just when it turns off it wont come back on...

I have the same issue with my SGS. Running stock version of JVT.
Wake up in the morning to phone alarm but screen is black. Pushing home button or any other button does nothing. Had this happen a few times now and only solution is to pull the battery

In order to help you we need to know what you are running currently and what you have tried to resolve the issue so far, can please make as detailed account as possible

It's seems that everybody have this same issue. I have exactly this same - phone is working - buttons are lit, but the screen is blank. I'm on 2.3.5 stock firmware.
Trying to solve this I already did wipe and even formatted the internal storage.
What's more interesting is that this same happens to my wife's Galaxy Mini (S5570) !!.
I can remember though that when my phone was on v2.2 about a year ago it was working ok.
small tip:
What you can do instead of pulling the battery out is to press the power button for about 10 seconds ( phone will turn off) release and the press it again for few seconds to start again.

You don`t need to press power again, just keep it pressed until you see the samsung bootlogo.
Mine has started to blackout too, maybe it`s related to some installed software. It worked ok still few months ago. My galaxy mini is working ok tho, has only few market apps installed.
Sent from my GT-I9000 using Tapatalk

poyda69 said:
Has anyone had this issue?
I have tried a few different ROM's and have had this problem on all, the phone will work but sometimes when the phone is locked and asleep you cannot get the screen back.
If you ring the phone it will ring but you can't wake the phone up (the screen is off).
If I then pull the battery and reboot all is well until the next time, which is random.
I will remove all my programs to see if there is one of them causing the issue, I don't believe it is the rom as it has happened on a few of them.
Click to expand...
Click to collapse
The bug is called SOD (Sleep of Death). Apparently a Gingerbread only bug (I think deep sleep was introduced in Gingerbread).
Your phone is going into deep sleep, and can't be woken agian.
I don't know if there is a fix for it, but you could try search for SOD on these forum pages.

Herman76 said:
The bug is called SOD (Sleep of Death). Apparently a Gingerbread only bug (I think deep sleep was introduced in Gingerbread).
Your phone is going into deep sleep, and can't be woken agian.
I don't know if there is a fix for it, but you could try search for SOD on these forum pages.
Click to expand...
Click to collapse
i had this issue on cm7 with neo kernel, but sometimes it responded after some time
i think its black magic made by apple and will kill our cats

As Herman76 said, this is the SOD, I used to get them quite frequently. I created a thread with a possible workaround. So far haven't got any new SODs.

[Q] Galaxy Note not waking up?

I can't put my finger on this issue I've been having with my Note.
Don't get me wrong, this device is a godsend!
The problem I've been having is that sometimes when I take my Note out of my pocket and try to press the unlock or menu button it doesn't show anything on the screen. I've read about people having issues with delay before it pops up, but it doesn't pop up even after 10 seconds or a minute, it feels like the device 'hangs' or doesn't want to wake up. The only way I can turn the phone on again is by pressing the unlock button for like 10 seconds and the phone reboots.
I thought it was a problem with Green Power, I thought it maybe had issues turning off the wifi or data when the screen was locked and that the service would cause the OS to crash or 'hang'. When I look at my battery history after the reboot it shows that I lost a significant amount of battery (5-15%, depending on how long it took for me to 'discover' the crash) and there's a 'jump' in the graph.
Things I've tried:
Stock rom - problem persists
Different kernels - tried all the kernels available in the market including stock, problem persists
Add a bit of paper between back-cover and battery (to make sure it doesn't lose contact)
Checked if there was dust between battery connections
Tried different sim card
Tried disabling wifi and data all day (mysteriously persists)
DIfferent governors (ondemand and interactive) (the phone reverts to default governor after the forced reboot, normal? i have my phone set to interactive on boot, but somehow it skips that after the forced reboot)
I've attached a picture of the battery graph. According to the stats there's a 25 minute gap where the phone was 'stuck' and you can see that the screen was on and active for that duration.
There are NO funny apps running in the background, this is is a clean install with some standard Samsung apps frozen.
tl;dr version: phone randomly won't wake up; battery loss after forced reboot;

I might have found the issue myself. Now when I come to think of it, I think it always occurs after I've been in my car for like a 30 min drive... Maybe the phone is having trouble switching networks? Anyone know what might be causing this?
Or better yet, how can I research this issue? Can I enable some logging somewhere to track this?

I had the note for about 10 days and today, about 1 hour ago it happened to me for the first time. I tried the home button to wake the screen but nothing, tried the power , nothing and holding the power but nothing happened. I had to pull the battery.

I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.

tamarian said:
I had this problem in the beginning, but no more.
It's one of two things, in my case. Restoring apps (with data) from Titaium backup, or SetCPU or both. Do a factory reset, reinstall apps without data. If using setCPU, disable it for a while to see if it happens again. It's been over a week and the problem is gone.
Click to expand...
Click to collapse
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.

I'm on stock room and unrooted. Like I said first time it's happened.

i've had the GNote since 4 days now , and yesterday same thing happened as the device was in my pocket and i couldnt wake it up at all , battery pull solved it.
im on stock , non rooted

I can't believe that we are the only ones with this issue. Anyone else? OR better yet, how did you resolve it?

Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.

kirkla79 said:
Dont know if this is the same issue as the streak had, but with the streak if you kept it your pocket with the screen facing your body this would sometimes happen. Flipping it so that it that the screen doesnt face your body in your pocket solved this issue.
Click to expand...
Click to collapse
Thanks for your reply. I did some research, and apparently it had to do with static being built up in the screen from wearing it towards your body in your pocket.
This issue was that you couldn't swipe the lockscreen cause the touch screen wouldn't respond. The problem we are having is that the screen won't even turn on and that the system locks up.

Same issue here with my 2 days old Galaxy Note, that's how I found this forum. In my case it went from not waking up occasionally to every time WIFI was ON (I did some experimenting with settings to see which one could be the one causing the problem). But then...occasionally it would not wake up even with WIFI OFF: very annoying. And this is my first Android, so I didn't have any custom anything, pretty much same as out of the box when I got it The only solution was to reset the handset. And definitely has nothing to do with having it in my pocket as I don't carry it in my pocket. Rang Samsung, they told me it was faulty, I returned it. Now I'm concern the next one is going to have screen issues? As so many people complain in this forum? we'll see.

My issues have been resolved after flashing AbyssNote 1.4 and when I stopped using System Tuner. I've started using Voltage Control instead and now I'm not even having problem @ 100Mhz undervolted 50mV from stock.

Same problem with my wife's Gnote, totally stock, just a small handful of apps installed. Happened twice, about a week apart.
She does a lot of travelling, maybe you're right about that. But it happens after she gets home when it's still OK.

Had the same same issue twice in two days and had to do a battery pull, just did a master reset and re -installed the applications manually, so far so go.
YOu guys think its a hardware or a software issue?

Hmm.. Happened to me too about three times in the last two weeks. I am on stock rom but rooted, and running Green Power. Hopefully samsung will fix it in the next updates. Seems like a software bug to me. Maybe not enough juice when in deep sleep?

metus666 said:
I was using System Tuner instead of SetCPU to freeze apps and change governor, maybe I've just been using the wrong app? I deleted it just in case. Will see if the problem persists, thanks!
The nasty thing about it is that it seems to happen randomly (but it most likely doesn't) and is pretty rare (happens once every 3 days).
Still, I don't like the fact of not being available for X amount of time, even if it's 30 minutes.
Click to expand...
Click to collapse
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically

neunzehn77 said:
Hello
its the problem of your kernel. try Abyys 1.4 and use XDA Superpower to adjust the CPU-Frequency automatically
Click to expand...
Click to collapse
problem is it also happens on stock rom.

mfractal said:
problem is it also happens on stock rom.
Click to expand...
Click to collapse
It's very well possible that the stock kernel has faulty settings for the CPU. Haven't had the problem again with AbyssNote 1.4 and Voltage Control (even with custom cpu frequencies)

I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??

qazkamakazi said:
I just got my note today.
Battery in, turnt it on a few mins playing around.... the problem started
and hasnt since stopped...
Anyone tried contacting samsung about this?
software fix or hardware issue ??
Click to expand...
Click to collapse
at this point we're just guessing, there haven't been any official confirmations of the problem as far as i know.
But if it's so accute that it keeps happening all the time you must have a faulty device.. call samsung ?

[Q] Galaxy Note GT-N7000 crashing regurlaly how to find out the culprit?

My Note has started crashing regurlaly, I have had it since release and have a lot of software on it. I am not sure when it started happening but it is definatley getting worse as time goes on.
Is there any log file or event browser that can be installed to tell me what is causing the problem?
When I say crashing I mean literally crashing dead not a force close. I either find it in my pocket turned off and then have to hold the power button for an age to turn it on or sometimes it is sat on the desk and I suddenly hear the noise it makes when it re boots.
Any suggestions for finding out what the problem is that don't involve uninstalling software until the problem goes away?!
Thanks

Have you tried better battery stats? It gives a list of processes that have been running.
Definitely strange - do you have an anti-virus program you can run to see if it can help?

That sounds like a Sod (Sleep of Death) issue that's been reported many times b0t with no definitive solution of yet..
Some said changing modem helped, others with changing kernel or even ROM but no consistent solution across all users
Try to fix permissions through advenced menu in recovery but am afraid there is not much I can help with

wingnutLP said:
My Note has started crashing regurlaly, I have had it since release and have a lot of software on it. I am not sure when it started happening but it is definatley getting worse as time goes on.
Is there any log file or event browser that can be installed to tell me what is causing the problem?
When I say crashing I mean literally crashing dead not a force close. I either find it in my pocket turned off and then have to hold the power button for an age to turn it on or sometimes it is sat on the desk and I suddenly hear the noise it makes when it re boots.
Any suggestions for finding out what the problem is that don't involve uninstalling software until the problem goes away?!
Thanks
Click to expand...
Click to collapse
Omfg, I don't think your alone cause I have the exact problems at times when the note just freezes up and you have to manually boot up...lets hope the upcoming pics update will solve this ongoing problem... I'm getting this about 3-4 times a week
Sent from my GT-N7000 using XDA

it is starting to make the phone a liability as I keep finding it turned off in my pocket!
Is there no software that will produce a crash log of some sort?

wingnutLP said:
it is starting to make the phone a liability as I keep finding it turned off in my pocket!
Is there no software that will produce a crash log of some sort?
Click to expand...
Click to collapse
I hope there is...
Sent from my GT-N7000 using XDA

this is driving me nuts. The phone is unusable.... is there no possible solution??
At this point I will try anything. It crashed during the night on Thursday, didn't restart and so there was no alarm and I was late for work!

Please post your current configuration Kernel, Anti Virus program if any, undervolting, overclocking ?

By any chance are you using easy task killer... if you are just change the auto optimize to nothing - I did that and it stopped sleeping...if your problem is persisting then you could just do a factory reset and use default settings...
Sent from my GT-N7000 using XDA

My note recently started crashing as well, whenever i turn on my mobile data plan or the wifi it will crash right away
However this is ironic because when ever i put my mobile in charging mood than i have no problems at all.
So im thinking ,is this the battery problem or the software problem?

mumuxy said:
My note recently started crashing as well, whenever i turn on my mobile data plan or the wifi it will crash right away
However this is ironic because when ever i put my mobile in charging mood than i have no problems at all.
So im thinking ,is this the battery problem or the software problem?
Click to expand...
Click to collapse
battery problem.Try to see what is the output of ur battery in full charge by messure it with electric potension meter (sry for bad english).
If the meter say less than 1850mAh in full charge than u need a new battery.

Touch screen going CRAZY

I think I have the weirdest problem with my Sensation XL.
It works fine and sometimes, when I unlock it, the touch screen goes into super frenzy mode and starts doing things on its own. When it's stuck in that mode, I cannot use it, and it clicks buttons around randomly and very fast.
I have seen it open my messages, swipe a long gibberish text and send it (!) or this morning it just opened contacts and deleted one!
I am pretty sure it's all in random because on the keyboard I can see it swiping very randomly around the screen and in a very fast speed.
What on earth is this and how do I stop it? It almost looks like a virus or some sort of spyware but I checked and see nothing malicious installed.
The phone is about 8 months old and is not rooted. Latest firmware installed.(4.0.3 Android version).
The crazy behaviour did not coincide with any updates in software. Just started 3 weeks ago randomly and happened maybe 5 times till now.
The only way to stop your phone going mad and doing something you don't want it to do is to quickly rip the battery off, because you are unable to restart it from the touch screen.
It only happens after you unlock it, not while you're using it and I noticed it happens after a long period of inactivity.
Has anyone had that? Any help is very appreciated!
Thank you

nkomp18 said:
I think I have the weirdest problem with my Sensation XL.
It works fine and sometimes, when I unlock it, the touch screen goes into super frenzy mode and starts doing things on its own. When it's stuck in that mode, I cannot use it, and it clicks buttons around randomly and very fast.
I have seen it open my messages, swipe a long gibberish text and send it (!) or this morning it just opened contacts and deleted one!
I am pretty sure it's all in random because on the keyboard I can see it swiping very randomly around the screen and in a very fast speed.
What on earth is this and how do I stop it? It almost looks like a virus or some sort of spyware but I checked and see nothing malicious installed.
The phone is about 8 months old and is not rooted. Latest firmware installed.(4.0.3 Android version).
The crazy behaviour did not coincide with any updates in software. Just started 3 weeks ago randomly and happened maybe 5 times till now.
The only way to stop your phone going mad and doing something you don't want it to do is to quickly rip the battery off, because you are unable to restart it from the touch screen.
It only happens after you unlock it, not while you're using it and I noticed it happens after a long period of inactivity.
Has anyone had that? Any help is very appreciated!
Thank you
Click to expand...
Click to collapse
Lock the screen and open it again. If this doesn't stop it could be a Hardware problem
I also had some problems like this on the original firmware, but rarely, it got fixed when i flashed Incredibly Cool Sense v3. You should lock the screen not to rip the battery off, as it's faster and it should work

Lexmazter said:
Lock the screen and open it again. If this doesn't stop it could be a Hardware problem
I also had some problems like this on the original firmware, but rarely, it got fixed when i flashed Incredibly Cool Sense v3. You should lock the screen not to rip the battery off, as it's faster and it should work
Click to expand...
Click to collapse
I don't think it's a hardware issue cause the phone works well most of the time. If it was hardware the problem would be permanent, not intermittent and especially so occasional.
Must be something software related, I did add a lot of games to the phone recently but the problem happens even when these processes aren't running in the background which is puzzling.
Locking and unlocking the screen postpones the problem, it doesn't solve it. As soon as the screen is unlocked, it immediately goes crazy again.
I can only solve it by pulling the battery out, and FAST, before it sends crazy messages to my contacts

nkomp18 said:
I don't think it's a hardware issue cause the phone works well most of the time. If it was hardware the problem would be permanent, not intermittent and especially so occasional.
Must be something software related, I did add a lot of games to the phone recently but the problem happens even when these processes aren't running in the background which is puzzling.
Locking and unlocking the screen postpones the problem, it doesn't solve it. As soon as the screen is unlocked, it immediately goes crazy again.
I can only solve it by pulling the battery out, and FAST, before it sends crazy messages to my contacts
Click to expand...
Click to collapse
Welcome to the club. I had that same issue. But after a hard reset everything is fine with mine.
I assume that there was an app causing all that. If after a hard reset still does that you should send it for repair

If you have a screen protector its can be a main reason for this. To stop this behavior you can use power button and wake up it again. Some htc devices have the problem with multi touch screen
Issues of production. Clear the screen products with some alcohol and see than.
Sent from my HTC One X using xda premium

I don't have a screen protector actually and the screen is usually clean.
Must be some app, I wonder there was some way to find out which without having to do a hard reset and lose everything
stona175 said:
If you have a screen protector its can be a main reason for this. To stop this behavior you can use power button and wake up it again. Some htc devices have the problem with multi touch screen
Issues of production. Clear the screen products with some alcohol and see than.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse

nkomp18 said:
I don't have a screen protector actually and the screen is usually clean.
Must be some app, I wonder there was some way to find out which without having to do a hard reset and lose everything
Click to expand...
Click to collapse
You can't! There is no way you can find out which one is causing that. Maybe it's some update from something that is causing the freezing.
Last night i did notice something else though. My battery was almost empty and i took my gf charger. She has S2 and after i charged my phone it has started to act strange......... Even today after i pluged the phone to install something from the PC it didn't even notice that i have connected it to the PC. Took me about 20 min in/out to get it running I clean the usb slot every week so it is not a dirt issue....

it happens with me when there's water on the screen
Send from my lovely Sensation XL, from a little town in france with a very very slow internet connection.

Mine was also weird when it rains but then I installed android 4.0 Rom and it was much much better it still has the music app problem but I has installed rocket music player and now I don't have any errors at all at with the minfree low memory killer enabled it has high free ram.. still without its holds battery long time and is very smooth defenly try that great Rom
Sent from my HTC Runnymede using xda premium

Be careful from contiouas pressure on screen it may drive it to behave strangely .
Try to use lock code before putting the phone into pocket
Sent from my HTC Runnymede using xda app-developers app

Definitely on to something.
It has happened a few times when it was drizzling and there were tiny droplets on the screen (not proper rain).
It started acting up when I was swiping the screen against the tiny droplets. After locking it, it would stop responding...
Most of the times I find it either non reponsive or acting weird after I take it out of my back pocket and try to unlock it.
Maybe being in my pocket, even locked, affects it somehow.
Is it easy to put another Rom? Do I lose all my apps?
rawadlayous said:
Be careful from contiouas pressure on screen it may drive it to behave strangely .
Try to use lock code before putting the phone into pocket
Sent from my HTC Runnymede using xda app-developers app
Click to expand...
Click to collapse

nkomp18 said:
Is it easy to put another Rom? Do I lose all my apps?
Click to expand...
Click to collapse
Yes you will lose all your apps.

Yes I have the same behaviour, its usually moisture from my hand, greasy buildup, water droplets and or being in my pocket the pressure on the screen makes it act up too, wouldnr worry bout it, not every screen design can be perfect ; )
Sent from my HTC Desire S using xda app-developers app

onejay09 said:
Yes I have the same behaviour, its usually moisture from my hand, greasy buildup, water droplets and or being in my pocket the pressure on the screen makes it act up too, wouldnr worry bout it, not every screen design can be perfect ; )
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
sorry to bump an old thread.
I have this problem on a bashed up screen. however... I don't think it can be hardware because if I hard reset its then OK on the next boot...
we need to learn more about touchscreens - how are they calibrated? I think it is reset on boot and also on each lock

Its the LCD ribbon touching the metal housing, short circuiting the screen, easy fix with a piece of tape over the ribbon
Edit
Also, once the phone heats up resistance builds up with it causing the issue
Sent from my cm9 using xda app-developers app

I had that same issue.

You won't loose any of your data if you made a back up before instaling the new rom
if I was of any help Just hit the thanks button
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

Xperia Z vibration problem (experiment was done and detailed explainations given)

I realized that my Xperia Z's vibrator will stop working after an "intense" work or overheated...
for example, i turned on the "vibrate on touch" option, and then keep pressing any key (let's say the Home virtual key), i can feel that the vibration strength will get weaker and weaker, and finally stops.
at this point, the vibrator wouldn't work, no matter how. Neither in Service Test, switching on/off phone (i believe these cannot be altered by the user)
Then if I leave the phone there for a while, the vibrator will start working again, and if i repeat the experiment (pressing Home key), the number of times the phone would vibrate is fewer ( e.g. the phone vibrated ~30 times before stopped working at the first test, then it stopped working after ~10 times at the second test).
Interestingly, the vibrator would work again immediately if i shaked the phone (even straight after it was "dead"), but the length of time it came back "alive" is even shorter.
And it seems that the vibrator functionality also depends on how i hold the phone... by making it flat (screen facing sky), the vibrator seems to work better and longer.
I also found that the vibrator would stop working when the phone is being charged, but i am not so sure if it was caused by charging or the heating up of the phone as it went quite warm when charing. When I unplugged the phone, the vibrator didn't came back alive immediately, so I washed it with cold water (hey it's water proof !) and the vibrator worked again!
I have tried Factory Reset, and re-installing the firmware via Update Service but the phenomenon still exists.
It's kind of weird, and i hope some technitians could give reasons of this behavior. To me it's like the vibrator needs some time to settle down, the damping isn't efficient. Or, the current is too high so it cuts the flow to the vibrator for safety reason?
maybe some xda developers could check the codes and see how the vibrator behaves?
I hope there isn't a faulty of my phone, I really don't want to send it to the service centre for a body-check....
Thanks

moonset said:
I realized that my Xperia Z's vibrator will stop working after an "intense" work or overheated...
for example, i turned on the "vibrate on touch" option, and then keep pressing any key (let's say the Home virtual key), i can feel that the vibration strength will get weaker and weaker, and finally stops.
at this point, the vibrator wouldn't work, no matter how. Neither in Service Test, switching on/off phone (i believe these cannot be altered by the user)
Then if I leave the phone there for a while, the vibrator will start working again, and if i repeat the experiment (pressing Home key), the number of times the phone would vibrate is fewer ( e.g. the phone vibrated ~30 times before stopped working at the first test, then it stopped working after ~10 times at the second test).
Interestingly, the vibrator would work again immediately if i shaked the phone (even straight after it was "dead"), but the length of time it came back "alive" is even shorter.
And it seems that the vibrator functionality also depends on how i hold the phone... by making it flat (screen facing sky), the vibrator seems to work better and longer.
I also found that the vibrator would stop working when the phone is being charged, but i am not so sure if it was caused by charging or the heating up of the phone as it went quite warm when charing. When I unplugged the phone, the vibrator didn't came back alive immediately, so I washed it with cold water (hey it's water proof !) and the vibrator worked again!
I have tried Factory Reset, and re-installing the firmware via Update Service but the phenomenon still exists.
It's kind of weird, and i hope some technitians could give reasons of this behavior. To me it's like the vibrator needs some time to settle down, the damping isn't efficient. Or, the current is too high so it cuts the flow to the vibrator for safety reason?
maybe some xda developers could check the codes and see how the vibrator behaves?
I hope there isn't a faulty of my phone, I really don't want to send it to the service centre for a body-check....
Thanks
Click to expand...
Click to collapse
I'm facing the same problem, the vibration works occasionally , and there is a lot of people with this problem, I will wait for now waiting a fix, some people here confirm that the problem disappeared after 2 days of use. How old is yours?
Sent from my C6602 using xda app-developers app

new update:
i did some more tests. and i found that:
1. vibrator stopped working during charging once the phone's temperature rised above 30 degrees (actually vibration kept working for a few times before completely dead). and even it then cooled down to below 30 degrees, the vibrator was still dead (still in charging, cable plugged in). and vibrator came back alive immediately when unplugged (at this moment the temperature was 28 degrees). but if the temperature went above 30, unplugging wouldn't bring the vibrator back to life, and i had to leave the phone there for a while.
2. at any temperature, continuously pressing the soft keys (with haptic feedback switch on) VERY quickly (i mean like pressing it 10 times in one second that quickly), or just go to Service Test -> vibrator and set the vibration time to something LONG (e.g. 90000), the vibrator worked for a while then died. then if i gave it a break (~10 mins) of gave it a shake, vibrator came back alive again.
3. no matter what caused the death of vibrator (point 1 or 2), if I could cool the phone down very rapidly, i.e. I put it in cold water, the vibrator would come back alive.
4. the cooler the phone is, the stronger and longer working time of the vibration (as in point 2)
so i guess it's the temperature that causing this problem, seems like a hardware issue (because my X10 doesn't behave like this), probably the circuit isn't connected properly.

hamud.q said:
I'm facing the same problem, the vibration works occasionally , and there is a lot of people with this problem, I will wait for now waiting a fix, some people here confirm that the problem disappeared after 2 days of use. How old is yours?
Sent from my C6602 using xda app-developers app
Click to expand...
Click to collapse
mine is nearly a month old. i didn't notice this problem until a few days ago. so i cannot comfirm if it was already like this when i bought it.
i think we should gather all the complaining posts of this issue and send it to Sony (at least before we send it to service centre for repairing).

push up

i have this issue on italain xperia z... very annoing problem...

Any new update? Any fix? I don't want to send my phone for 2 weeks to fix this
Sent from my C6602 using xda app-developers app

I found that after tapping on the back panel close to speaker, the vibration is working again for a while..then, it stops working again...

gdavidoff12 said:
I found that after tapping on the back panel close to speaker, the vibration is working again for a while..then, it stops working again...
Click to expand...
Click to collapse
Yes, same thing with me
Sent from my C6602 using xda app-developers app

Yes me too... It is a hardware problem?
Sent from my C6603 using xda app-developers app

Seems like it. I'd send the phone in for repairs if I were you

I already sent it.

gdavidoff12 said:
I already sent it.
Click to expand...
Click to collapse
Please keep us updated!
Sent from my C6602 using xda app-developers app

Any news? Only we have this problem?
Sent from my C6603 using xda app-developers app

gdavidoff12 said:
I already sent it.
Click to expand...
Click to collapse
any news ??

same problem for me :crying:

I have the exact same problem.
Can someone with a custom ROM confirm this? I'm wondering if it's hardware or software related.

@ hamud.q
After one month of waiting, finally the phone will be replaced with a new one! Apparently here in Bulgaria in the service dоn't try to fix the phone (if it's a hardware problem) and directly replace it with a new phone...

Does anyone have a solution for this problem?