Recently I've noticed that my razr no longer rotates from portrait to landscape, and i'm hoping there's a way to calibrate it in order to get it working again. First thing I did was check all the settings, toggled the auto-rotate switch anywhere I could find it, but nothing would make it switch. I've done some research on the problem, and have tried everything from a soft reset, to a hard reset to pulling the sim card with the phone off, no luck. I'm running SS 3.05 with an ics rom on one slot, and a jb on another, and the problem persists across both roms. I'm considering booting to android recovery and doing a factory reset there, but didn't know the impact it may have on SS. Any thoughts or suggestions?
BTW... Both bubble level and compass apps fail to function properly. Even after calibration they both act erratically
Sent from my Amazon Kindle Fire using XDA Premium HD app
did you try moving a small neodyme magnet along the outside of the case?
As weird as it may seem, put it inside something soft, such as a sock, or tpu case, and beat it against something wooden, alternating th X, Y and Z axes. Worked more than once when my Optimus 3D got a stuck accelerometer (dropped it too much)
Sent from my HTC Sensation XL X315e using xda app-developers app
(That's what the magnet is for - replacing the art of rampage^^)
Well, I tried a HDD magnet once, but it failed to realign the accelerometer sensing needles. Let's wait and see if any of the ideas solve the OPs's problem...
Sent from my LG-P768 prototype
Thanks, I'll give this a try. Any concern about wiping data? I know magnets and drives don't play nicely together
Sent from my DROID RAZR using xda app-developers app
Ok, so i gave it both a good beating, and ran a strong magnet all over it (didn't have a neodyme, but have some strong ones from Home D), but not luck. I've got a similar post on droidrzr.com and it was suggested that it could be kernel related, and to try a kexec kernel or to fastboot. still a bit of a noob (but working on it) so i'm following up on the fastboot suggestion, but i flashed a kexec rom on slot 2 and it made now difference. i'm feeling more and more like its a hardware failure, but before i call verizon, i wanted to both update the thread with the results, as well as see if there were any other ideas out there.
thanks again for the suggestions so far! even though the problem still exists, i'm grateful for the offer of help!:good:
I wanted to update this post with the final outcome. After some advice, i ran Matt's 1.82 utility to go back to stock, but unfortunately it didn't fix the issue. Seems to be a hardware failure, will be returning it to a VZ store in the morning. Thanks for the help and suggestions! Hopefully by this point tomorrow I'll have a new (or factory refurbished) phone, rooted and finally able to bang on the latest 4.2.1 by Hashcode. Thanks again!
Related
Is there a file I can edit or remove to disable trackball functionality entirely?
The trackball has the bug where it perpetually scrolls to the left. Just curious what I can do to work around the problem.
Many thanks in advance
Sent from my ADR6200 ERIS using XDA App
Ah yes, I remember this problem. Not a fun experience at all.
The only luck I had was sending in my Eris to Verizon and getting another one. I'm pretty sure you can't do that anymore though, and they'll send you a D1 instead, if they even do that anymore.
Cleaning the trackball might work, since it could be just a piece of dirt causing problems. If you're as unlucky as I was though, its a hardware flaw that can't be (easily) fixed.
Yeah, its a common issue. However that would be an interesting fix lol i know there is another version of the recovery you can use that does not require the trackball, use that to unroot if it dies completely so you can return to Verizon.
Sent from my ADR6350 using XDA App
I have the same problem too, but i cant send to verizon because i am in canada for family and two days from now i will be in saudi arabia...so i cant really send it to verizon. I use my phone daily and it roams perfectly. I have 2.3 SENSE on my phone. Back when I had recieve teh bug, it was going on and on and on. After sometime, and also after some flashing new roms, the bug is not as "powerful" as it was before. Now it only does it when i charge it. I remember there was an app in the market that actually stopped the trackball but it only worked for a min. and then the app stops working. I hope this gives you a bit help!
Search under the Stickys here under Eris and it will point you to the link to download & flash the Recovery Rom - where use of trackball is optional, especially if do you boot into doing NAND backup/recovery or flash ROMs, etc.
Cleaning the trackball by pressing down hard & rubbing on a hard surface over a white printer/copier paper sometimes worked wonder (at least for a while - to me.) Stickys for earlier posts (plus look into YouTube for a demo) ....
I got my Eris via eBay and it's been out of warranty and the ultimate solution was to spend $2.50 (including shipping from USPS) to get a Blackberry (8300, etc.) trackball replacement & did a simple transplant or replacement - available in many colors (I got a black one, least expensive, to replace the transparent/clear one on the phone) - and less than 10 minutes of labor to get it changed, as good as brand new. Just need to use a jeweler's screwdriver (it's a torx/hex style micro screws x 4 plus 2 on the circuit board) to open the case with the cover removed, take out 4 screws & then pry carefully around the edge/rim to avoid scratching to pop it open enough, then taking out the 2 crews to get to the trackball. A slight push or nudge, it will pop out - note the direction of the contacts before putting your new one in - reverse the disassembly sequence. Power up once everything is tighten back together & you are good to go - watching that black/blue/red/orange colored trackball dance & light up.
It was a fun project for me & feeling of accomplishments, giving new life to the aging Eris coupled with one's choice of Froyo or GB Rom's.
Actually, I've had the problem for a while now. I've tested many rom's and it really depends on the rom. Funny isn't. I had come up infrequently in GSB. MacRom it didn't it a little but wasn't crazy. What i do to fix it is press down hard and that seems to fix it. I'm running Gin-Sense Tazz and haven't noticed it yet, but i've just flashed the rom.
I've heard of people fixing it by laying the phone down face first and rolling it around with pressure to reseat it. I'm not saying to, it might make the problem worse. But its a thought
Sent from my ADR6200 ERIS using XDA App
Thanks for the suggestions!
Sent from my ADR6200 ERIS using XDA App
I've replaced the trackball on a phone with this problem, still having occasional issues... The trackball replacement didn't fix it entirely. What to do next?
From what I understand of the trackball problem is that it is a grounding issue with the contacts and the charging/usb port. Mine is doing it also so when it breaks I will take it apart and find out for sure:}
I finally broke the annoying sucker and flashed a recovery that uses the call and end buttons instead of the trackball. I'm not having any issues.
sjpritch25 said:
I finally broke the annoying sucker and flashed a recovery that uses the call and end buttons instead of the trackball. I'm not having any issues.
Click to expand...
Click to collapse
Love seeing another satisfied customer .
Cheers!
Yep. I've been frustrated for so long that I was glad to finally fix it
Sent from my ADR6200 using XDA App
sjpritch25 said:
I finally broke the annoying sucker and flashed a recovery that uses the call and end buttons instead of the trackball. I'm not having any issues.
Click to expand...
Click to collapse
did that recovery also disable the trackball within the ROM? Or just in recovery? can you post a link to it? Thanks!
haganme said:
did that recovery also disable the trackball within the ROM? Or just in recovery? can you post a link to it? Thanks!
Click to expand...
Click to collapse
No, the custom recovery is mutually exclusive of the ROM. Sorry, my tweaked version of Amon_RA's custom recovery can't touch the ROM that's installed...
Here's a link to the XDA post where for my tweaked version of the trackball-optional custom recovery for the Eris:
http://forum.xda-developers.com/showpost.php?p=9124095&postcount=83
And here is the sister thread over on AndroidForums that has some installation options for you:
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
Good luck and cheers!
After, I broke the trackball. All the trackball issues left and i needed a way to use the recovery. The recovery without trackball works great.
I also had a bad trackball, now using my wifes old eris since she upgrade to an inc2.
So, I've been jumping back and forth between Atrix CM9 and CM7 roms and running the .36p radio. Yesterday on CM9, i started getting a large amounts of random reboots and finally got things settled by doing a factory reset in CWM and flashing a clean cm9 rom. However, whenever I turned on wifi, the phone would crash and reboot to the Dual Core logo. I tried flashing another CM9 rom and it didn't crash, but the wifi radio would never seem to pick up any AP's (i'm at home).
I've gone as far as changing to the .37p radio and going back to cm7 to no avail... I'm a bit worried I might have "fried" the wifi radio on the phone.
Did you do a full wipe? Use fastboot to wipe properly before flashing any ROM. Plenty of threads with instructions.
Sent from my MB860 using xda premium
Looking at the fast boot command, I'm not sure how that does anything different then the clockwork mod wipe... but I will give it a shot.
Sent from my NookColor using xda premium
Sorry, but your wifi/bluetooth card is dead. My Atrix got the exact same symptoms a few days ago. Both WiFi and bluetooth are on the same chip. When the system tries to reference them, it fails to locate the hardware and crashes/reboots.
In fact, in researching this topic, I found dozens of threads about this. We should make a sticky about it at this point. Best Buy was kind enough to take back my phone (unlocked bootloader, rooted, cwm, custom fonts, startup, etc.) if I restored it all to stock. If you want Motorola/AT&T/the store you purchased it at to not void your warranty, you should flash the 2.3.6 SBF. Just be cautious and read all about it. But that is the only way that Motorola will service a modded phone
xandr115 said:
Looking at the fast boot command, I'm not sure how that does anything different then the clockwork mod wipe... but I will give it a shot.
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Nothing like the same. Clockwork wipe only does data and cache. You erase boot, system, preinstall, cache, user, webtop, etc., via fastboot. I've posted the procedure probably more than 20 times before.
Sent from my MB860 using xda premium
Yeah unfortunately even after a fastboot wipe, the phone's bluetooth and wifi were gone. I was also over the year warranty. Luckily, I picked up a barely used one on Craigslist and restored my backup to it. Now i've got an expensive battery charger (and spare phone should i need it).
If there were any tips you'd have on restoring to a new phone? I've restored my phone a lot and worked on a lot of android phones (I work at a repair shop), but I've never restored data/settings from one phone to another. Of course its the same model, but I can only imagine the issues that could arise out of such an operation
Thanks!
I just made sure I did a fastboot full wipe of the new phone, then placed my clockworkmod directory on the internal (external should be ok too) storage and did a restore. After the restore, I re-flashed the latest version of the rom I was running on top of it with Google apps and it booted fine. Afterwards, I made sure to do a permissions repair and reboot.
Yeah, it seems like a lot of people are having this problem. Like me for example :[
So far there is no solution that I'm aware of, after trying practically everything I could think of and find on the internet... I'm pretty sure it's hardware related. I bet the phone just isn't very high quality. How much did it cost again? $600? + all of the dumb accessories for it. Normally when you see a pattern of failures you would call it a design flaw, but apparently when it comes to expensive electronics they call it out of warranty.
xandr115 said:
So, I've been jumping back and forth between Atrix CM9 and CM7 roms and running the .36p radio. Yesterday on CM9, i started getting a large amounts of random reboots and finally got things settled by doing a factory reset in CWM and flashing a clean cm9 rom. However, whenever I turned on wifi, the phone would crash and reboot to the Dual Core logo. I tried flashing another CM9 rom and it didn't crash, but the wifi radio would never seem to pick up any AP's (i'm at home).
I've gone as far as changing to the .37p radio and going back to cm7 to no avail... I'm a bit worried I might have "fried" the wifi radio on the phone.
Click to expand...
Click to collapse
did your wifi
For anyone interested, here is a supposed solution to the problem:
http://www.youtube.com/watch?v=SYz_RiuFVRk
It will require you to open the phone up, and solder the "wifi battery" into place. I'm not sure what the hell that thing is, but that guy in the video called it a battery. Voids warranty etc. Good luck.
cafe. said:
For anyone interested, here is a supposed solution to the problem:
http://www.youtube.com/watch?v=SYz_RiuFVRk
It will require you to open the phone up, and solder the "wifi battery" into place. I'm not sure what the hell that thing is, but that guy in the video called it a battery. Voids warranty etc. Good luck.
Click to expand...
Click to collapse
I'd give it a try, if I could understand what exactly he does. It looks like he just pries it up with a screwdriver and then pushes it back down.
Meursau|t said:
I'd give it a try, if I could understand what exactly he does. It looks like he just pries it up with a screwdriver and then pushes it back down.
Click to expand...
Click to collapse
If I ha some solder I might try it
Sent from my NookColor using xda premium
I just had my Bolt replaced due to issues with the SD Card slot failing on the old one. I have the official HTC Car Dock, and never really had problems with it in the past. Got the new device, rooted it, and installed the radios from the 2.11.605.19 build, otherwise running stock. Now when I put it into the Car dock, it never activates the dock mode. I know it's not root causing it, and I would assume the radios aren't causing it. Tried a co-worker's phone in the dock and it works fine, mine doesn't activate in his dock. Any suggestions? Could the leaked Radios be causing this? Thank you all in advance!
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
My apologies, consider this n00b duly flogged Hopefully it will get seen here and someone will have an answer.
So just for a test, I flashed back to stock recovery, took the .19 OTA, back to CWM and re-flashed su and.... no change. I made a nandroid, so I'm going to try flashing an RUU just to make 100% sure it's not software, otherwise I guess I'm looking at needing my Bolt replaced for the third time....
unrooted, flashed back to 2.11.605.9 RUU, and dock worked. tried to restore back to the backups I made last night and today, and they failed, so I ended up having to roll back to a backup from 2 weeks ago. Went through all the steps to get back to 2.11.605.19 rooted, all programs updated, and car dock works fine now. I have NO idea what changed, but something is better now. If anyone has any ideas, I'd love to hear them, otherwise, Mods, you can feel free to close/delete this thread at will.
Tiezane said:
unrooted, flashed back to 2.11.605.9 RUU, and dock worked. tried to restore back to the backups I made last night and today, and they failed, so I ended up having to roll back to a backup from 2 weeks ago. Went through all the steps to get back to 2.11.605.19 rooted, all programs updated, and car dock works fine now. I have NO idea what changed, but something is better now. If anyone has any ideas, I'd love to hear them, otherwise, Mods, you can feel free to close/delete this thread at will.
Click to expand...
Click to collapse
Maybe a good system wipe is all you needed. Try downloading the superwipe script and flash that before you flash your next Rom.
Sent from my ADR6400L using Tapatalk 2
The strange part was, this was a brand new phone. The issues I had leading up to getting it require some time and a few beers to adequately describe, but I ended up recovering a ton of data off of a formatted SD card, which included what I thought was a good nandroid, but turned out not to be. Same thing with backups I made over the last couple of days, all garbage. The backup I first made after I got the phone and got everything reinstalled is what I'm on now, and everything works fine where it hasn't for two Weeks.
I swear, I have gremlins.
Sent from my ADR6400L using XDA
Your sd card prolly had corrupt blocks from the malfunctioning sd slot on the first device. That's most likely what caused the bad backups. But it could have been that Dock mode was taken out of your backups, which would be my guess as to why it wasn't working.
dlamber7 said:
Your sd card prolly had corrupt blocks from the malfunctioning sd slot on the first device. That's most likely what caused the bad backups. But it could have been that Dock mode was taken out of your backups, which would be my guess as to why it wasn't working.
Click to expand...
Click to collapse
I've checked the card 6 ways to Sunday, no bad blocks. Dock mode was not taken out of any backups, this literally started with the brand new phone, before I attempted to reinstall any backups. I'm thinking I just have a finicky piece of HW, it stopped working again this morning. I did notice that the prior cycle of it working again correlated with the window mount falling off in the middle of the day. Does anyone know what it is that triggers the dock mode on these things? Is it magnetic (a la the BB holster signal) or is it something else?
Yes it is magnetic. Interesting. Well, if stil under warranty have vzw replace it for ya.
yeah, it's definitely in the dock. After it got hot yesterday afternoon, dropped the phone in and it worked fine. Cool out this morning, popped it in, nothing.
When the phone is in the doc, should it flip the screen to landscape? Even when ur on the home screen?
Sent from my ADR6400L using xda premium
With the stock launcher, no. Sense does not rotate like that. What should happen as soon as the Igor us plugged into the dock is that the "car mode" app should launch, which will display in landscape mode. Some things like Bluetooth voice dialing are still in portrait mode, which is kinda screwy.
Sent from my ADR6400L using XDA
Has anyone had this issue? My Maxx seems to freeze the camera when it focuses the main camera. Every camera app I've tried has the same effect. I've even tested this on other razrs. Some take a few shots then lag or freeze and some just slow down. There's an app that is something like speed shot or something that seems to work but it isn't focusing, it simply takes shots as-is. I've read this to be a common issue with this device. Otherwise. I love this phone!
Anyone else having the issue? Anyway to fix it?
Sent from my DROID RAZR using xda premium
stupid question, but have you tried powering down and restarting your phone since this problem started, somethings can be solved with a simple reboot.
Whats your sdcard class?
Sent from my XT910 using Tapatalk 2
Not a stupid question lol and yes I've done that multiple times. Even have wiped a few times.
I believe its the stock class 4 card. I will pop in the class 10 from my transformer prime and see if it has any effect....
Sent from my DROID RAZR using xda premium
Aaaand that's a negative on any improvement with the class 10 card. Plus, I had nothing on the card as well...
Sent from my DROID RAZR using xda premium
jaydoubledub said:
Aaaand that's a negative on any improvement with the class 10 card. Plus, I had nothing on the card as well...
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
download "Camera ICS" from the market (Google Play) and use that instead and see if the problems go away.
Huh, it seemed to help. It does have about a 10 second lag though. Third photo i had to "wait" on the fc option.
Sent from my DROID RAZR using xda premium
Do you folks think it might be a hardware issue? If so, do you think I can send it to Motorola and have them send me 1 back since I bought it off of craigslist? I did buy it new in box is there a chance that I can send it to verizon also?
Sent from my DROID RAZR using xda premium
Update:
My camera is working flawlessly now. Just over night it decided to. Yesterday, i unrooted and set back to stock and applied all OTA updates. Even then it was still having the same issues. The ONLY thing i did this morning was swap my micro SD card back and forth a few times with my transformer prime, to back up all of my photos and music. After I got off of work I tried to go to Verizon and see if I could swap it out. Of course that did not work. Before making the decision to buy 1 outright, sell this to a potential buyer on craigslist, and eat the difference i just tested the camera 1 last time.
BLAM! It's working and focusing as it normally should without the slightest lag.
So, that being said it may have had something to do with the positioning of the sd card inside the phone.
Sent from my DROID RAZR using xda premium
I had the same issue in the past and it was going the same way like yours. But then the camera was completely bricked after a while. I had to send it to repair. Just take care of it.
Well, I ended up selling it for a $50 profit. I bought one for full price from Big Red. Hey, it's a credit card, not REAL money right? haha! I figured if I have issues again in the future, then my warranties and Asurion insurance would at least cover it.
Found a fix (for me at least)
I was having very similar issues to what has been previously mentioned. To be specific, every time I opened the camera app it would respond temporarily, however when i tried pressing the shutter button the phone would freeze. After many cache wipes, data resets, and factory data resets my stock camera app seems to be working.
What I did:
I'm not positive that this was the final solution, but I opened the app and was able to open the settings without it freezing. I then changed storage to SD card (it had been internal). Works like new! I'm guessing there was an issue with the storage folder or some other software issue?
To be thorough, I had also taken out the SD and sim card and put them back and also wiped the cache today. I'm not sure what finally did it but maybe something happened with the storage folder or something internal? I also wiped the SD card earlier in the week so maybe that helped too.
Either way, it works now and I hope this helps someone.
Matt
So last night, my phone decided that it would no longer like me to use it. The screen is a full screen of (for lack of a better term) rainbow snow. It is pixelated. I can't see anything except the snow. I have gotten it to show my lock screen by kind of tweaking the phone by bending slightly. When I get the lock screen, the touch screen no longer works. I can hit the power button to turn the screen off, and then again to only get the snow. I am thinking it's probably a hardware issue. I haven't dropped it or gotten it wet. Which leads me to my next question. I am rooted and running CM 10.1. I can't get in to recovery mode to restore to a stock ROM. If I take it in to Sprint for repair/replacement will they have a way of seeing I am running a ROM and decide they wont't work on my phone?
thedanpal said:
So last night, my phone decided that it would no longer like me to use it. The screen is a full screen of (for lack of a better term) rainbow snow. It is pixelated....
Click to expand...
Click to collapse
Is it possible that you CAN get into recovery and you just don't know it because you can't see it? Work with me here.
If you can power down the phone, try powering up into bootloader/fastboot and try to flash an appropriate RUU from fastboot/usb. Just a shot in the dark...
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
tmwilsoniv said:
Is it possible that you CAN get into recovery and you just don't know it because you can't see it? Work with me here.
If you can power down the phone, try powering up into bootloader/fastboot and try to flash an appropriate RUU from fastboot/usb. Just a shot in the dark...
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Click to expand...
Click to collapse
That is a very good chance. I will give it a shot tonight. Thanks for the idea.
I pretty much have no idea what to do now. My phone won't mount the SD card on any computer. The phone recognizes the SD card, i just wont mount it. When trying to use RUU i just get the error 170. So, i guess i will be dropping my phone off at sprint and hope for the best.
Same issue. Was running Carbon which is cm based. Tried everything, nothing worked. Took it to the Sprint store yesterday and they got me a refurbished LTE. I'm thinking of getting the HTC one but can't afford it right now. Refurb phone works alright so I'll just keep it for know but I know what you're going through. it sucks and although the ROM worked awesome it may have been the culprit.
Sent from my EVO using xda app-developers app
SiGuy11 said:
Same issue. Was running Carbon which is cm based. Tried everything, nothing worked. Took it to the Sprint store yesterday and they got me a refurbished LTE. I'm thinking of getting the HTC one but can't afford it right now. Refurb phone works alright so I'll just keep it for know but I know what you're going through. it sucks and although the ROM worked awesome it may have been the culprit.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
The tech thought it was a connection issue with the display, but he couldn't get it fixed and thinks the motherboard went bad. They are replacing the phone with a new one, but they are backordered so I have to wait a week.
Yeah but what caused all of our phones to have the same issue that doesn't exist on sense roms? Kernel overpowering the motherboard causing it to fry?
Sent from my EVO using xda app-developers app