[Q] Phone vibration strength weakening - Motorola Droid RAZR

Over the last couple of days, the strength of the vibration on my phone has went really poor, used to be no issues with that for 2 months and now its very very poor.
To my knowledge, I have not bumped or banged the phone that may have dislodged anything etc
Anyone got any ideas on what problem maybe or how to fix ?

If I were you I would download some vibration testing app and determinate if its software or hardware issue first.
Sent from my XT910 using xda premium

theEnzy said:
If I were you I would download some vibration testing app and determinate if its software or hardware issue first.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Thanks for the tip ...... you dont happen to know the name of one of these ?
Update - phone motorola support and only advice they could give me is try a factory reset and if that doesnt work, then send it back to them for repair, but means I would be without my phone for 2 weeks, plus its rooted.
If I do a factory reset when rooted, does this do anything untoward the phone ? Do I lose root ? unsure about this

Reminds me an episode from the IT crowd...

Related

My Phone Won't Turn Off!

Help!
This is the second time my SGS2 keeps turning itself on after I've switched it off.. Last time I removed the battery and then lost all my settings/widgets on the homescreen - pain in the a*** to set it up again! Obviously I don't want to have to do it a third time!
Anyone else having the same problem? Any ideas on how to permanently fix this issue?
Any thoughts are greatfully received.
Jamie
FreshFreddie53 said:
Help!
This is the second time my SGS2 keeps turning itself on after I've switched it off.. Last time I removed the battery and then lost all my settings/widgets on the homescreen - pain in the a*** to set it up again! Obviously I don't want to have to do it a third time!
Anyone else having the same problem? Any ideas on how to permanently fix this issue?
Any thoughts are greatlyfully received.
Jamie
Click to expand...
Click to collapse
What rom are you running? Stock or custom? What kernel? Details man, details.
Sent from my GT-P1000 using XDA Premium App
Fair point. Stock. Not rooted.
Sent from my GT-I9100 using XDA Premium App
FreshFreddie53 said:
Fair point. Stock. Not rooted.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Cheers. Ok , so you are on stock, could you go into settings, about phone, and give the baseband,build number kernel version? Also, where are you? Uk/europe/asia/etc.
I know its a lot of details, but so far theres around 7 different versions of the stock software. Depending what you have, there might be an update for you, or not.
Sent from my GT-P1000 using XDA Premium App
Man, you're putting me to shame here... Sorry!
Baseband version - I9100XXKE4
Kernel Version - 2.6.35.7-I9100XWKE7-CL215725 [email protected] #2
Build Number - GINGERBREAD.XWKE7
I'm in the UK and bought the phone unlocked from Carphone Warehouse.
Appreciate you putting up with me!
Have you tried putting it in your pocket?
feralicious said:
Have you tried putting it in your pocket?
Click to expand...
Click to collapse
not very helpful.
On topic, sadly:
I could say, flash this, flash that. wipe this wipe that. but it does sound like an odd problem. And rather than advise you to do something that may void your warranty......I'm going to suggest that you try to get it exchanged. Rather get it replaced now, than waste time trying to fix it, and then still have to get it replaced/repaired.
GSOH. Looking for a permanent fix though...
Sent from my GT-I9100 using XDA Premium App
FreshFreddie53 said:
Help!
This is the second time my SGS2 keeps turning itself on after I've switched it off.. Last time I removed the battery and then lost all my settings/widgets on the homescreen - pain in the a*** to set it up again! Obviously I don't want to have to do it a third time!
Anyone else having the same problem? Any ideas on how to permanently fix this issue?
Any thoughts are greatfully received.
Jamie
Click to expand...
Click to collapse
Without being an expert I would suggest that some application in your phone is switching it on for updates etc.Check in your phone for active applications & switch them off one at a time or all together & see it that cures the problem. Hope this helps.
so i dont know much about the technical stuff, but i totally had this same problem. but like other people the only time my phone seemed to stay off with the battery in, was when it was plugged into the mains charging. so i tried a combination of plugging the phone in to charge whilst the phone was on or off, and then switching the phone off, and then removing the charger whilst the phone was still off. i'm not sure exactly what combination worked, but one did, and since then, sofar atleast, my phone no longer restarts every time i switch it off!
not very technical, but hope that helps!

Galaxy S III Not responding

Hi everyone,
i don't know if someone already encountered this but sometimes my GS3 does not respond when i try to wake him up. (it's not turned off just standby). The screen stays black en nothing works. One time the screen did woke up but i couldn't unlock it because the touchscreen didnt work. It could not be turned off and the buttons didn't do anything! The only way for me to get out of this was a battery pull!
I did not root or modify anything on this phone because i like the stock samsung TW for the first time .
Did anyone else have this problem? And how did u solve this? Thank u.
Possibly due to an app you have installed.
Sent from my GT-I9300 using xda premium
dnlgee said:
Possibly due to an app you have installed.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thank u i didn't thought of that. Is their an easy way to find out wich app this could cause? I still find it very weird. If an app is not compatible than it just shouldnt install intead of breakin the phone right? XD
This happened me last night as well. Couldn't do anything other than turn the phone off, and when it came back on it was fine again.
Unrooted as well. Would like to find out how I can prevent this from happening again?
if you are not sure about the root cause of the problem better factory reset your mobile
bala_gamer said:
if you are not sure about the root cause of the problem better factory reset your mobile
Click to expand...
Click to collapse
Yes, if it happens again than i will try that. But i already sent the unit back from were i ordered it. They will send me a new one because its their policy to send a new one if something happens in 2 weeks.
So i will see if it still occurs with the new one otherwise its one of my apps. Than i will install only a few apps and see what causes it. If it doesnt occur one more thime than the unit was faulty. Ill keep u guys updated.
chicoelnino said:
This happened me last night as well. Couldn't do anything other than turn the phone off, and when it came back on it was fine again.
Unrooted as well. Would like to find out how I can prevent this from happening again?
Click to expand...
Click to collapse
Did it happen once? My phone had it like 3 times so thats why i sent it back. But if it still occurs with my new phone than it must be one of the apps i got Luckily they got DOA policy. I asked if it includes ''the phone does not work as it should" and they said yes send it back u will get a new one yaay but now i have no phone
I had this. After a hard reset, multiple times, and configuring with no accounts (no samsaung account, no google, nothing), it still happened. I ended up returning the phone and I've not had a single problem since.
I think it was either faulty memory or a dodgy firmware flash (more likely). Either way, I didn't care to find out and now it's all good.
sama said:
I had this. After a hard reset, multiple times, and configuring with no accounts (no samsaung account, no google, nothing), it still happened. I ended up returning the phone and I've not had a single problem since.
I think it was either faulty memory or a dodgy firmware flash (more likely). Either way, I didn't care to find out and now it's all good.
Click to expand...
Click to collapse
Yes lucky i found this out early too.. Because after another week i wouldnt get a new one and now i get
Factory reset your phone.
Hope everything turns out alright.

Touch Issues

A small part of my screen does not work. The part above the menu button. It has been this way for a while and the phone is usable. I can't type w,e,s,z and the comma in portrait mode. I thought the digitizer was damaged but last night everything started working and did so for quite some time until I charged my phone. After that it has been the same. Anyone ever have this problem before and could someone suggest a solution?
PS: The pds partition fix did not work.
Sent from my MB860 using XDA Premium HD app
What caused this? Did you recalibrate the screen with aroma installer?
Sent from my MB860 CM7.2 RC3 36p Radio
darkhokage said:
A small part of my screen does not work. The part above the menu button. It has been this way for a while and the phone is usable. I can't type w,e,s,z and the comma in portrait mode. I thought the digitizer was damaged but last night everything started working and did so for quite some time until I charged my phone. After that it has been the same. Anyone ever have this problem before and could someone suggest a solution?
PS: The pds partition fix did not work.
Sent from my MB860 using XDA Premium HD app
Click to expand...
Click to collapse
There are random reports of Jokersax's CM9 causing issues, and my phone is currently out on warranty repair with the same issue (dead area in digitizer). I have also heard that Motorola used crappy digitizers in the Atrix, and for this reason rolled the Atrix 2 to market quickly. All of these theories are unsubstantiated.
I tried the PDS fix (after backing up my PDS partition), a Google Play screen fix solution, flashing different ROMs on a fully wiped phone, SBF'ing to stock, and another calibration solution I found on XDA, but none worked. At that point it was back to Motorola with the phone. Hoping for a 2 week TAT. Good luck.
Soldier-2Point0 said:
What caused this? Did you recalibrate the screen with aroma installer?
Sent from my MB860 CM7.2 RC3 36p Radio
Click to expand...
Click to collapse
I don't know. This happened a few months after I bought the phone. Since I am in Pakistan, the phone came without the international warranty and repairs are not that easy. Up until a day ago, when everything started working, I thought that the digitizer was broken but now I have started to think differently.
Sent from my MB860 using XDA Premium HD app
tobnddl said:
There are random reports of Jokersax's CM9 causing issues, and my phone is currently out on warranty repair with the same issue (dead area in digitizer). I have also heard that Motorola used crappy digitizers in the Atrix, and for this reason rolled the Atrix 2 to market quickly. All of these theories are unsubstantiated.
I tried the PDS fix (after backing up my PDS partition), a Google Play screen fix solution, flashing different ROMs on a fully wiped phone, SBF'ing to stock, and another calibration solution I found on XDA, but none worked. At that point it was back to Motorola with the phone. Hoping for a 2 week TAT. Good luck.
Click to expand...
Click to collapse
I guess I will just have to live with it. The incident where everything started to work still gives me hope though. I will keep on trying and let you guys know if I make progress.
Sent from my MB860 using XDA Premium HD app
I had the same exact issue. If you still have warranty, send it in. This is a well documented problem.
If you have unlocked the bootloader, just flash the proper sbf back to stock.
That's what I did, and they sent me a brand new phone.

[Q] Stock S III boot loop - SIM?

My stock, never-rooted GT-I9300 (4.1.2, I9300BWELK1, JZO54K.I9300XXEMC2) is plagued by boot loop problems. It first started about 3 months ago, where the blue charge LED would suddenly come on and the phone would not wake from sleep. I pulled the battery, then when it was turned on it showed the initial S III logo, then the O2 logo followed by the glowing Samsung logo. Then repeated from the O2 logo endlessly. I pulled the battery again, then the next morning restarted it without the SIM or SD card in, and it had done a partial factory reset - i.e. lots of phone contacts were there with the texts, but all the settings had reverted to default. Later that day while on charge the same thing happened again, and I sent it away to O2 for repair.
When it returned, the same thing happened 6 weeks later although this time it was on when it froze and went straight to the O2/blue LED stage. Another repair (I'm fairly sure these 'repairs' were just factory resets...), and 6 weeks later exactly the same. Back to the O2 shop for another repair.
This time they replaced the 'main board' and when it came back it had a different Wi-Fi MAC address. This time only 6 days elapsed before the same fault arose again, and finally I was eligible for a replacement handset. This lasted 2 days before a boot loop condition occurred again! This time, being sure it couldn't be a hardware fault I tried my own /data and /cache wipe, which worked. I skipped all but the must-have apps, and I thought this was going to be stable but once more this past weekend the boot loop happened again (I've got my restoration procedure down to about 15 minutes thanks to the practice!)
I don't know what could be causing this and I'm fed up with resetting my phone. Are all S IIIs this unstable? I've never had a phone that required a factory reset within 18 months! When it is in the boot loop, I can access recovery and download modes, but safe-mode start-up has no effect.
The last remaining candidates I can think of are a problem with my SIM card, or a defect with my SD card... or an app. Can anyone suggest the best way to troubleshoot this? I'd really really rather not have to skip importing my settings as I have among other things many SSIDs I don't easily have access to re-create.
What ROM are you on? 4.1.2?
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
What ROM are you on? 4.1.2?
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Yes, 4.1.2. I don't recall this behaviour before I got the OTA update from 4.1.1 though
kernalk said:
Yes, 4.1.2. I don't recall this behaviour before I got the OTA update from 4.1.1 though
Click to expand...
Click to collapse
No, not all S3 owners experience this, a factory reset solves most of these issues however, if it doesn't, a trip to the Samsung service center will help.
I'd say it's probably a dodgy app, or some kind of unstable firmware update for your region/carrier, since hardware replacements didn't help with it.
Skander1998 said:
No, not all S3 owners experience this, a factory reset solves most of these issues however, if it doesn't, a trip to the Samsung service center will help.
I'd say it's probably a dodgy app, or some kind of unstable firmware update for your region/carrier, since hardware replacements didn't help with it.
Click to expand...
Click to collapse
Hmm. Thanks for the reply. I'm not sure I know anyone else with and S III on O2-UK but it seems to be news to O2, so I assumed it must be fairly rare.
I'm not sure about dodgy apps; testing them one app at a time isn't really feasible as it can take up to 6 or 7 weeks to fail judging by past performance. Are there any logs or similar that I can pull out somehow in the event of a boot loop? I've seen about logcats but I am not sure if this would be of use
Sent from my GT-I9300 using xda app-developers app
kernalk said:
Hmm. Thanks for the reply. I'm not sure I know anyone else with and S III on O2-UK but it seems to be news to O2, so I assumed it must be fairly rare.
I'm not sure about dodgy apps; testing them one app at a time isn't really feasible as it can take up to 6 or 7 weeks to fail judging by past performance. Are there any logs or similar that I can pull out somehow in the event of a boot loop? I've seen about logcats but I am not sure if this would be of use
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Everything to carries is "news".
I can't help with logs and whatnot, so I'll leave that to someone else.
You can always flash and downgrade to the older firmware that didn't give you a problem, if the problem persists, it is indeed an app.
Even when rooted, informative logs are nigh on impossible to get
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Even when rooted, informative logs are nigh on impossible to get
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
That doesn't fill me with confidence!
Thanks again for the replies. I'm not wild about downgrading. I liked the improvements! Is it possible to downgrade in a carrier supported way? Retaining warranty compliant has been rather useful in the past few months!
Sent from my GT-I9300 using xda app-developers app
You can flash any official via odin.
Sent from my GT-I9300 using Tapatalk 4
Well late Friday night it did it again. Not sure when exactly as I was asleep. Woke up in the middle of the night and went to check the time, Looked at my phone to find the blue LED on when it should have been red for charging or green for fully charged, and it was very hot - wouldn't turn on either. Pulled the battery but it kust went into the loop. I was away from home so I couldn't do any troubleshooting and had no choice but to wipe.
This time I didn't restore settings and the only apps I installed were SMS Backup & Restore and Puzzle Alarm (I know this isn't the culprit as I only started using it this week!). Gone are all my precious wifi SSIDs but otherwise I'm not sure I've noticed the difference.
So I'm now not connected to my work wifi, nor have I set up my work email or Lync - two of the things I use my phone for must after Facebook which I've also not reinstalled. Facebook mobile web is really hard to use by comparison.
By chance I popped into the O2 shop later that day and had the fortune to bump into a Samsung rep who had never heard of this and agreed that I was unfortunate to have these problems (how touching!) and suggested I speak directly to Samsung support rather than O2 which I will do this week. I will also contact O2 about a replacement SIM and look into replacing the SD too.
This is really silly. I'm not keen on downgrading the software because the first thing either Samsung or O2 will do is upgrade it again. Frankly at this point I'm fed up with the whole thing but I've got a year left on the contract and even a pretty much new handset like mine won't fetch enough.

Any one else get black screen?

It's happened alot over past two weeks and it's now done it 3 times in past 2 1/2 days. Screen stays black press any button does nothing and hold down power still does nothing. Only way is to hold volume up and power for 3 vibrations then power back on its really annoying and must be due to some problem....?
Sent from my C6833 using Tapatalk
What firmware are you on?
.257 happened when was complete stock aswell @Lordmanhatten
Sent from my HTC One using Tapatalk
am going thru this currently ... and i cant do anything to the device at all! urs might work after the restart ... i've done the power button/volume up restart that didnt help ... did the emergency reset using the red button also didnt work ... the phone is running in the background as i can still receive whatsapp msgs but i cant view them as am receiving "inititalbootsetup" isnt responding either close or wait ... and again both of these options arent working ..
Go to settings and disable auto brightness. I'm not sure why it works, but after researching for a while on this same issue, this is the setting that worked for me. Try it and update us if it works.
Sent from my C6833 using XDA Premium 4 mobile app
Did you guys update to 257 without wiping? I didn't wipe, but there might be some bugs sticking around from 532. Do a factory reset (full wipe if you have recovery) and see if that solves it.
any updates on this issue .the device screen simply doesnt wake-up from sleep ,unless you hard reboot .
i'm on 290 stock ,and testing the auto brightness disable method.
update : issue persists with auto-brightness disabled .
Hmm, it has to be a software bug. I can't see how this could be a hardware issue. Have you tried everything? Wiping? Re-flashing? Flashing a different ROM?
I did still get it on stock rooted rom. Twice in a day
Sent from my C6833 using Tapatalk
Happened to me view times when i tried to play movies, weird thing its not all movies, just some of them. Then i tried to remember what did i just installed because it never happens before. For me it was Nooxzoid, i uninstall it, and it back to normal.
So maybe try to remember does it happened before or just recently, maybe some app went roque with your phone.
Sent from my C6806 using xda app-developers app
Old topic but this just happen to me. Screen went black and couldn't get it back still heard noises from speaker when got message but couldn't get screen on I tried red button and volume up but never worked. I had to remove sim which forced a reboot. Never installed anything recently on rooted. 532. I've had nothing but issues regarding this phone. Regretting getting it thought sony would make a better product then this.
Sent from my C6806 using XDA Premium 4 mobile app
Xyphir said:
Old topic but this just happen to me. Screen went black and couldn't get it back still heard noises from speaker when got message but couldn't get screen on I tried red button and volume up but never worked. I had to remove sim which forced a reboot. Never installed anything recently on rooted. 532. I've had nothing but issues regarding this phone. Regretting getting it thought sony would make a better product then this.
Sent from my C6806 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have it just once though two days ago. Force reboot it by the button i almost gone mad when it's still not working, but somehow after a minute, it's normal again. I don't know why. But in case of yours, try to upgrade to the latest ROM first. That might fix it for you. No point for rooting if you can't fix the problem so let it go.
Sent from my C6802 using xda app-developers app
Hello Good People,
Still having this issue and it seems to be getting worse
Did anyone find a solution?
T.I.A.

Categories

Resources