Related
All right, so a while ago say..few hours or a day ago, I dropped my phone. Nothing seemed wrong, everything was working fine. Until I decided to go play Abduction World Attack. It's a game where you tilt the G1 and the little character moves according to how you tilt it. Surprise Surprise I ran into my problem. The little avatar wouldn't move and it was just stuck there no matter how I turned my phone. I also just noticed that auto-rotate won't work. I believe it's because the accelerometer is broken...Anyone have any advice on how to fix this or calibrate it? I've tried calibrating inside apps that use the accelerometer. I've searched but to no avail. Help will be appreciated Thank-you.
[Edit]: A wipe has fixed this! =)
If your under warranty, you may want to try and get it exchanged. Let T-Mobile/HTC know that it just stopped working.
If you are out of warranty, you can attempt at looking for a solution by taking apart the phone. The official manual is here
The manual has all of the disassemble instructions. Hopefully that will lead you to a solution.
Sounds like it could be a hardware issue but no harm in testing to see if it is a software one. Tried rebooting the mobile? If so see if other programs like Bubble works. If not then a final resort would be a reflash to at least eliminate the software side of things.
If its no go then best to try and get it exchanged...
I've fixed it guys ^^ Seemed like a wipe would do it. I changed to the hero build for a second and then reflash CM after a wipe and accelerometer is fixed. Thanks for the suggestions though! Greatly appreciated
The power of the mighty wipe ^_- Good to hear its been sorted. Since you're the OP too, could you edit the title to SOLVED so people know?
NeoBlade said:
The power of the mighty wipe ^_- Good to hear its been sorted. Since you're the OP too, could you edit the title to SOLVED so people know?
Click to expand...
Click to collapse
Sure. OP and title has been updated!
Sure wish I had your luck. I'm having the same problem and a wipe didn't do me any good.
I have tried several different mods and none of them work.
tested with browser, bubble, Papi game apps, and Accelerometer xyz Values.
I don't have any akm files located in /data/misc
I do have a /system/bin/akmd but my ps output doesn't show it running.
whatchamccallum said:
Sure wish I had your luck. I'm having the same problem and a wipe didn't do me any good.
I have tried several different mods and none of them work.
tested with browser, bubble, Papi game apps, and Accelerometer xyz Values.
I don't have any akm files located in /data/misc
I do have a /system/bin/akmd but my ps output doesn't show it running.
Click to expand...
Click to collapse
Most likely a hardware problem then mate. You could try un-rooting and see if the accelerometer works.
If I install RC29 then the accelerometer works without issue. So that rules out hardware issue.
Here is another thread I found that goes in much more detail about what I am experiencing.
http://forum.xda-developers.com/showthread.php?t=533749
so far there isn't any movement on this thread. I'm surprised that this issue isn't more wide spread.
I just had the accelerometer on my HTC Sapphire go belly up.
Auto-rotate was broken, compass apps wouldn't initialize, tilting maze games would slowly move the ball to the top left side regardless of actual tilting, etc..
Reboot didn't fix it. However I did have a file under /data/misc/akmd_set.txt and most of the values in it were set to 0.
I renamed that file to akmd_set.txt, then killed akmd, per instructions in a neighboring thread.
akmd rose from its ashes, a new akmd_set.txt automagically appeared, with lots of different numbers for each value in it. All my accelerometer-depending features were happy again.
so yay, and all that.
As a side-note, I've been playing with some not insignificant magnets on my desk, and I'm wondering if abnormal magnetic fields around my phone might have caused the accelerometer miscalibration?
Good for my G1 too.
Kudos to the OP, this solution worked perfectly on my G1 with the same symptoms. Many Thanks!
I've been scouring the forums in hopes of a fix for my problem (the G1 Q&A and the Android Development forums). In my searches I have found 10-20 people who have had this similar problem, specifically, a force close whenever I (we) attempt to use the camera.
I'm %90 positive this is a software issue. I have had this phone (my 3rd one) for a few months now, and never have I had any issues with the camera, i actually use the video cam fairly often. Anyways...I decided a while back to root and flash Cyanogen's latest ROM, with the latest radio (posted a few days ago) and the Death SPL. Once i completed this, I was met with an instant force close when attempting to use my camera.
I have actually wiped and installed Cyanogen's ROM 2x, (the 2 latest versions), I have also installed KingKlick latest ROM, neither of these, coupled with countless different configurations has solved the problem. I have attached a small snippet of the last log I pulled. Any help or ideas would be greatly appreciated.
I also forgot to mention (and this might be completely wrong), I did restore the 1.5 image from the SPL, rebooted the phone, and the camera still didn't work, it didn't force close, just hung like it was trying to boot. I have also used the latest Super D ROM and I'm experiencing the same issue.
With my minimal knowledge, only one thing in the log jumped out at me, or, should I say I only saw one thing that I understood.
"X: /dev/msm_camera/control0 open failed: No such file or directory!"
Please help, this is a major deal for a number of people, every time it's posted, people just seem to ignore it.
Download Camera Magik from the market. If the problem is software related, then using a different camera app could be the solution. I like camera magik because is takes better pictures at low lights then the stock and the ability to zoom, but you can try any other app. Another suggestion is trying a sense based rom and using HTC camera. GL
I guess I should have said Kernel based as opposed to software based. I tried Camera Magic as well as one other new type of photo software, Camera Magic FC's, the other one opens, but, the camera never turns on.
Do you have any other apps that use camera(i.e barcode scanner, shopsavy)? You may have to uninstall and re-install. Did you wipe in-between roms? Try clearing your rotation settings from recovery, that may sort it out (I know it's a long shot). Other then that, email whoever's rom you're using directly with that log, they may be able to help you a lot faster then any of us regular folks can
Good luck
try a complete super duper wipe.
start from rc29, nonrooted. see if the camera works. if it does, start the root-rom process and check at certain intervals. if it doesnt work when your not rooted and on the stock original firmware, then its gotta be the phone. did it ever work before? i know you said this is your 3rd phone. has it ever worked on this particular phone?
First off, the camera/video has worked on all 3 of my phones, the 1st one had to be replaced because the keyboard went out, and, the 2nd one just kept randomly rebooting, the 3rd hasn't had any problems what so ever until my first root, which was Stock 2 Cyanogen.
So, I went back to RC29 unrooted and experienced a different problem. The camera didn't FC, but, it hung indefinitely at a black screen (kind of a dark grey). Unfortunately, for some reason the system option to force update to cupcake wasn't available, so, after 5hrs of waiting, I went back to root SuperD.
I'm really sorry if this has been asked already, but I looked and couldn't fine anything.
I just got a used nexus one online, and its working fine except that the auto rotation isn't working. When I tilt the phone nothing happens, sometimes if I turn the screen off and on a couple times the orientation will change, but then I have to do the same thing to get the orientation back to what it was before.
I've had this problem on four different roms, stock 2.1 and 2.2 before I rooted, and then CM5 and CM6 RC1 after. I've tried wiping and reflashing, as well as wiping the rotation settings using Amon_ra's recovery. The only thing that makes me think its a software issue is that the accelerometer seems to work fine in other apps, such as the bubble lever app, and the labyrinth game.
I've looked everywhere and can't find any fix for this issue. I really love this phone otherwise, but rotation is pretty important for me. I'm kind of at a loss at this point, so any help would be very much appreciated. Thanks!
I know it seems silly but is the box checked under settings : display?
So lately my kindle has been rebooting a lot, I couldn't figure out why, flashed back to stock rom etc. no difference. I remembered it used to lock at random as well, it was something to do with the light sensor and didn't happen in bright rooms, and the same thing applies with it rebooting. I'm not sure what changed that's making it power cycle instead of locking now, but I'm pretty sure that if I could disable the light sensor this would stop happening. I've been through the play store and tried all sorts of different apps, the only thing that was any help was one that showed that the light sensor was the only sensor that wasn't providing any data, and that didn't solve my problem.
So my question is does anyone know how I could disable it? It seems like it should be a really simple thing to do, clearly it's not. Any help would be awesome, thanks.
Download a slightly older build of cm 10.2, hashcode had temporarily disabled the driver while recoding it, so a slightly older build would have it disabled.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I'm using a Z3 compact with CM12.1, that means unlocked bootloader and no more warranty. All of sudden, the main/back camera has stopped working. It is black, OSD still working, front camera still working, other camera apps don't make a difference.
I don't know if that is a problem of some recent CM nightly or something else. Browsing the web I get the idea that this symptom also appears on stock firmware, and it seems that nobody has yet found a solution (neither factory reset nor hardware replacement of camera help).
My question:
Has somebody else this problem, is it CM related?
Is there a solution other than complete phone replacement?
Is there some logfile I might consult to find out if the camera HW should be replaced? I don't want to disassemble the phone only to find out that the camera still does not work.
Thanks!
Must be a software problem related to the nightlies unstableness.
Try flashing a stock firmware to see if it gets fixed.
I'd rather avoid going back to stock. Reverting to a previous CM nightly (from a time when the camera definitely worked) did not help.
Do you have any reports of CM nightlies problems with the camera? I'd love to hear that, because it would mean that I don't have hardware problems. However, searching the web I only found many reports of the camera suddenly stopping to work, but nothing that this is related with recent CM nightlies.
But if it's a Hardware problem, there should be a logfile somewhere, or?
just did trial and error on the same problem with the black camera for 2h
i did however not install CM to cause this
I have a custom debloated rom, which worked fine.
I had to switch phones so i did a TW recovery backup.
Changed the filename on the new phone so it is found when restoring.
Restored. Everything works well, except the camera app.
When i wipe from the systems menu i lose all my data but the camera app works again.
But of course i need my data exactly the way i had it backed up.
Tried all kinds of things around the camera app, backing and restoring with and without kernel, always the same.
Back camera stays black.
This is similar to other reports I found in the web: The hardware works (which means replacing the sensor is of no use), but somehow it is no longer accessible. I tried different hw info apps, which all report the back camera with all specs and no problems, but no camera app is able to get it to work. I flashed several new CM nigthlies since, it doesn't help
I don't really know how to read logs (with 3CToolbox), however this line caught my attention. Maybe somebody here can interpret it:
07:45:48.427 caladbolg( 301)
9530027 cald_parammgr_generic.c (4299) 301 E [PRM] Fail: camera eeprom status
Since my Kernel debugging skills are also not existent i simply factory reset it and transferred my data with titanium backup.
Everything works fine now.
So my advise is to stop wasting your time with it too, just go back to working software
Unfortunately reverting to stock firmware did not repair my camera. Afraid I have some hardware defect
No resolution to this problem it seems