Hi all, This is not getting exposure on the AT&T help forums so i thought i'd try here
I had been on CM12 for a while and at some point, not sure exactly when, my accelerometer stopped working, it would not autorotate landscape when holding the phone that way, all my photos were saved in the wrong direction etc. I also noticed that autobrightness completely stopped working.
I recently flashed the new stock based rom that is on the android development section thinking it was a AOSP or CM based bug, but I still am unable to get those things to work. It is very frustrating. If i try to calibrate the accelerometer, it closes out in settings instantly.
Anyone know what I can do to fix this?
Related
Hello Folks
I am new to this website. I have a question. My phone is Rogers Samsung Galaxy S3. I flashed Cm10-20121125-nightly. Everything works fine except camera. When I took picture, My camera froze for a while and then saying that the Gallery not responding, When I close the camera and reopen camera, it says cant connect camera. If i took video or use sphereview, it works fine. Do you guy have any ideas what is going on? This drives me crazy.
Thanks
Please search next time. This has been covered.
What you need to do with the 4.2 camera is focus by touching middle of screen then take pic.
Sent from my Samsung Galaxy S3
I'm running 10.0.0 stable version and I can't get the camera to focus either. I've tried tapping the screen and the [ ] box lights up but nothing changes.
I should mention I'm on the Sprint U.S. version of the phone. Just thought I'd ask here since this post came up when I started a new post in the Sprint section.
camera issue still unresolved
I've tried a number of things from different threads and nothing seems to help. I'm running CM 10 on AT&T Gs3. After flashing, camera app shows error saying "can not connect to camera". I know this is a common problem, but I cant seem to find a real solution.
I have the same problem with Beanstalk running the 4.3 Jellybean update. Do you have Focal installed on the phone ?
edit : My front camera don't work either, tanking a picture cause the phone to reeboot.
Can it have someting to do with the kernel ?
I am using SlimBean with lean-kernel and I don't have focal, but no reboots with frot facing camera...
Hello everyone,
I have a pretty big problem with the accelerometer on my S3. I'm running stock jelly bean, not-rooted.
The problem is that the sensor data is always way wrong. Using bubble level apps the phone always has to be tilted to an extreme angle to get the correct reading (holding the phone in portrait it has to be 45 degrees to the right for the bubble to be centered). This makes playing accelerometer based games impossible.
Calibrating from the motion menu does not work.
Factory reset did not work.\
Can anyone please help me with this?
More info:
My problem is pretty much the same as this person's, except they have a different device/ the problem wasn't resolved
http://forums.androidcentral.com/google-nexus-7-tablet-forum/199901-miscalibrated-accelerometer.html
Any ideas? Does anyone else have this problem?
bump
Given what you've said it sounds more like its your hardware, as much as it sucks you might need a replacement.
I am currently running the latest build of the PacMan rom for my Sprint S3, but my problem didnt start there. As over the course of a few weeks my phone has been randomly crashing while running build 7 of Slimkat. It started crashing when i wanted to take a picture with the AOSP camera (when i hit the camera button and then it would shut off). Then it progressed to just crashing trying to use accuweather, or even when the screen was auto-rotating in my SMS app. So finally i just backed up my important bits and made a clean wipe into Wicked X 8.0 TW rom (because i'm on Ting and TW roms initially work on their network and wanted to export, or to just copy down the settings of, the APN xml to use in AOSP roms). After playing around with that for 20 minutes, i didn't experience any fc's or reboots. Though i did not use the camera in that time (i forgot to check). To which i then wiped it into PacMan rom that im at now. Which at the moment seems fine to do everything, except it will shut off if i want to OPEN the camera (doesn't let me use it at all). Plus i did have it crash once rotating with the play store up...
So im kinda lost, i wonder if this is just an issue with the camera in the rom, or if it might be a bigger issue with the phone itself. As ive been having the same random error's with two roms and i dont see anyone having FC's with pacman rom with the camera.
more testing done
So i have also attempted to odin completely back to stock and i have a stock rooted rom with nothing touched. The sudden shut-offs still happen and occur randomly. I installed logcat and what seems to be throwing error's is the accelerometer. Plus at first when i flash a new rom it seems to work ok with no problems for the first day, then suddenly start showing symptoms the next. Plus ive had it shut off during bootup too while going through the sprint 4g animation screen. Though i have not had it die on me in recovery, so thats a thing.... Plus it will rotate no problem half the time, and then ive seen it die rotating to use my keyboard.
So at this point i feel like its actually a hardware option. If it is the accelerometer, is it easy to fix (i guess re solder the connections if they're broke?)? or should i just try and replace the main board?
Hi there,
I have cyanogenmod 14.1 update 20161217, and I've been having an issue since I updated to 14.0. Like I said in the title, my camera says it can't connect, my phone won't rotate, and the proximity sensor isn't working. Does anyone know if these are normal bugs that will be fixed later, or it's just an isolated case?
Any help is much appreciated.
Hey,
I'm having a problem with my GPS and compass for a long time now. I installed multiple custom ROMs and currently using Havoc 3.2.
The GPS/location signal are fine. But in Google maps or Pokemon GO, the compass is not working at all. It keeps spinning and turning around. It never points in the same direction. Does someone know how to fix this? Did I mess something up, and is it possible to fix this or is this hardware related :crying:?