Hi all,
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.
Anyone know what I can do to fix this?
Related
My nexus s' proximity sensors have stopped working. I am rooted and running aokpcb rom, I'm wondering if this is a hardware problem or something with the rom? The screen won't turn off when answering / making a call when the phone is brought up to my ear. I also tried using the app prox pro, and that wouldn't work either. If anyone knows a fix or what the problem is, that would be great.
Backup your current ROM , wipe and install a Stock ROM.
Issue solved --> Rom Issue
Issue unsolved --> hardware issue
Thank you for your response. I tried your suggestion, and the problem wasnt fixed with wiping and installing a stock rom. But, with experimentation, I installed the app "Prox Pro" and whenever I would turn it on, it would execute the command that was specified for when the phone was "flat". So, when realising this, I am assuming that my phone developed some sort of calibration problem with the sensors. All in all, I am wondering if there is a way that I can re-calibrate my proximity sensor so that they work properly. Thank you.
Could that just be the default for the phone if it's not getting a reading?
I don't think its the default. The sensors always worked fine up until sometime last week.
I meant a default if there is no signal or an error, which is what it currently looks like.
Oh, okay, ya that could be it. Do you have any idea how to change it? I also realised that the light sensor isn't working either, when on auto brightness, the screen will always be dim, no matter how bright it is outside. If you, or anyone else has a solution, I will open up my phone and check to see if there are any connection issues or something like that .
[Q] Compass / attitude sensor problem, Evo3D CM 10.1 "Wild For the Night" (Jan 30)
Would have posted in the related thread but I guess I haven't been chatty enough yet.
I've been running either Gangnam Style or Wild For the Night for about as long as they have been available and generally loving them, much better than previous roms.
However, when I installed the January 30 release of 10.1 WFTN, I noticed my compass isn't working. It seems like the attitude sensor is also iffy.
When I run GPS Status, the compass always stays locked at 000 degrees regardless of what attitude I'm holding the phone in. I have tried the Tools > Calibrate Compass function in GPS status and that doesn't seem to do anything. No heading arrow appears on Maps, either.
The attitude sensor in GPS status does not seem to work either, but if I open up Bubble Level, that seems fine - so I'm not sure if the compass and attitude sensor actually have any trouble, or if it's simply that some apps can't communicate with them properly.
This all comes up because I was trying to use photosphere and it can't figure out what angle I'm holding the phone at so it never takes a picture. I used the photosphere zip from the E4GT Wild For The Night thread, as suggested by Dastin.
I tried various combinations of reflashing the ROM, wiping cache + dalvik and reflashing the rom, reflashing Gapps, and reflashing the camera. I also reverted to 10.0 Gangnam Style (Jan 30) to see if that made it work, and all that got me was a neverending cyanogenmod boot screen. Reverting to 10.1 got me booting again, but...
Basically, does anyone know of a way to get the compass/attitude sensors working? Is this likely just an issue in the ROM or can those sensors be separately configured/calibrated?
Anyone have any input or suggestions?
I'd really like to check out photosphere, but the inability to use sky map hurts too as I'm a wannabe stargazer...
omgallthenamesaretaken said:
Would have posted in the related thread but I guess I haven't been chatty enough yet.
I've been running either Gangnam Style or Wild For the Night for about as long as they have been available and generally loving them, much better than previous roms.
However, when I installed the January 30 release of 10.1 WFTN, I noticed my compass isn't working. It seems like the attitude sensor is also iffy.
When I run GPS Status, the compass always stays locked at 000 degrees regardless of what attitude I'm holding the phone in. I have tried the Tools > Calibrate Compass function in GPS status and that doesn't seem to do anything. No heading arrow appears on Maps, either.
The attitude sensor in GPS status does not seem to work either, but if I open up Bubble Level, that seems fine - so I'm not sure if the compass and attitude sensor actually have any trouble, or if it's simply that some apps can't communicate with them properly.
This all comes up because I was trying to use photosphere and it can't figure out what angle I'm holding the phone at so it never takes a picture. I used the photosphere zip from the E4GT Wild For The Night thread, as suggested by Dastin.
I tried various combinations of reflashing the ROM, wiping cache + dalvik and reflashing the rom, reflashing Gapps, and reflashing the camera. I also reverted to 10.0 Gangnam Style (Jan 30) to see if that made it work, and all that got me was a neverending cyanogenmod boot screen. Reverting to 10.1 got me booting again, but...
Basically, does anyone know of a way to get the compass/attitude sensors working? Is this likely just an issue in the ROM or can those sensors be separately configured/calibrated?
Click to expand...
Click to collapse
Hi to rmbq developer of [ROM][S4][AOSPA3+][10jun] UNOFFICIAL PARANOIDANDROID 3.60 | HALO 10
Thank you for this ROM. I cannot post in the One S development forum as I am a newbie.
My phone has a problem where the hardware buttons (back/home/recent apps) stop working after the phone goes to sleep. The buttons are fine when the phone is first turned on but after the phone has gone to sleep the buttons don't work.
I have tried many ROMS ParanoidAndroid 2.54, stock rooted, viperS... but this one is the only one that keeps the buttons working.I know the buttons don't light up in your ROM whereas they do in the other ROMs.
Yours is the only ROM I have found where the buttons work all the time even after sleep. Would you know why this would be the case?
Another thing. I know you are working to fix a lot of bugs and to add a lot of features and a new kernel. What I'm worried about is that this would break this button working for me in a later version. The only thing that I really need fixed on this ROM is the auto rotate.
So I am using blisspop rom for few months now and they have this annoying bug that when u turn the screen into horizontal mode and you try to lock it in that mode (landscape) it automatically goes back to portrait mode and locks it in that mode
Does anyone know where I can report that annoying bug?!
I am pretty sure its super easy to fix it's just that they are not aware of it
Thank you in advance
I would suggest the Blisspop topic?
I've already posted about it in the Blisspop thread, along with many others. Doesn't seem to be a high priority bug I'm guessing. If it's that annoying flash the TeamEOS ROM instead--they are both AOSP (if I'm not mistaken...)
It's not a big surprise either. Even stock nvidia firmware has bugs.
One I found out is after the latest update I can't no longer remove my USB pen drive like before, removing it does nothing (tested on my 2 nvidia shields with latest update).
Hi, it appears that recently the gravity sensor in my Nexus 5 stopped working.
At least it is what it seems by using sensor testing apps. And this makes it impossible for the phone to get its orientation (compass is not working).
Screen rotation is still working fine though.
Here is what happened exactly: not long ago I was using Google Maps, but the phone was a bit sluggish so I decided to reboot it.
After rebooting I opened Google Maps again and immediately noticed that the orientation indicator was missing (the blue "beam"), while it was present before the reboot. But I didn't care about it, and just thought that the compass needed re-calibration.
After a few days the orientation indicator was still missing, and the phone never asked me to re-calibrate, as it used to do before instead.
Then one day I launched Google Sky Map, and noticed that the view does not rotate automatically.
So I fired up a sensor test app I had installed (asd.vector.sensor), and no data is displayed for the Gravity sensor. Also orientation is not displayed and the info says that the gravity sensor is used to compute orientation, too.
Other sensors are ok, and as I already wrote screen rotation still works great.
Any clues about this issue? Did anyone ever experience this?
I'm afraid a system restore would not help...
I'm using Resurrection Remix ROM, Android 6.0.1.
Thanks.
If the problem exists on a stock ROM, it could be a hardware fault.
audit13 said:
If the problem exists on a stock ROM, it could be a hardware fault.
Click to expand...
Click to collapse
Ok yes, but I still do not know if it exists on a stock ROM.
Taking it the other way around... Do you think there is real possibility that it is a software fault?
I mean: did it ever occur to anyone? Is there really any hope that resetting my phone to stock will fix this?
I HATE having to reset my phone...
Thank you.
I stopped using custom roms a while ago because of minor problems that would suddenly appear.
I don't think there is a way to really tell if it is software or hardware unless you reset or use a stock ROM.
audit13 said:
I stopped using custom roms a while ago because of minor problems that would suddenly appear..
Click to expand...
Click to collapse
Well, that's a little hope at least.
I will need to find some time to re-stock my Nexus and try.
Thanks .
Ok, I restored the phone to stock and all sensors work again now!
Thanks audit13 for pushing me in that direction .
That's great that it was a software bug in the custom ROM.
Now you get to hunt for a custom ROM that works with a minimal or zero number of issues