looks like data output of my captivate's sensors is reverted with accelerometer, that means I starting any compass app and puts phone to horizontal surface and rotates it clockwise and counterclockwise, normally compas should rotates but it doesn't.
When I put it at an angle to the surface, compass starts rotating. Behaves itselfs as the accelerometer sensor
The strange thing is that compass working like a charm on KK4 modem, but I can't use KK4 modem on CM\MIUI build because of abnormal sensitivity (it is too sensitive) of mic during call, the caller can't hear me clearly.
I trying to google for this problem but didn't find anything usefull, also I tries to calibrate it, of course it didn't help
Any ideas how to fix the problem, its really annoying me during GPS navigation-the map alvays rotating?
P.S. now I'm using MIUI-1.12.9.10 I9000XXJVT baseband and Glitch v13 kernel
I'm actually seeing the same thing; my compass seemingly responds primarily to accelerometer or gyroscope detected motion (or the magnetometer is just busted). As far as I know, this only started happening after I updated to KK4 and installed CM7 over it (the compass was fine under CM7 installed over KB2). I've tested other modems, including KK4, to no avail. Flat surface calibration (face up and face down) and the compass calibration (using the figure 8 rotation) indeed do not help.
Has anyone else experienced this issue and/or have any suggestions? Could this at all be related to GB bootloaders? I doubt the latter to be the case, but I'm all out of ideas here, because outside of things within the OS, that's the only thing I can think of that's changed.
ROM: CyanogenMod v7.2.0 RC0 KANG
Kernel: Glitch v13.1
Modem: JK4
So I cleared /data/system/yas529.cfg and rebooted the phone, and the system created a new file one on startup. This seems to have... changed... something. That is, the phone seems to be reading the magnetometer now, but it's behaving crazily. Firstly, the compass reads west when the phone is pointed north. Secondly, when I move the phone counterclockwise, the compass actually also spins counterclockwise, so when I reorient the phone from north to west, the compass actually points from west to north.
Compass recalibration via figure 8 motion and pitch/roll recalibration (both with phone face up and face down) don't help. Anyone familiar with /data/system/yas529.cfg, and what a "good" copy looks like? Mine currently has the following values:
Code:
13,19,16,174,26,-158,3,255,255,255,2147483647,2147483647,2147483647,0,
The previous one that seemed to respond primarily to accelerometer/gyroscope had the following values:
Code:
14,19,16,-46,52,-170,3,255,255,255,2147483647,2147483647,2147483647,0,
Well. I have no idea why this worked, but I decided to revert to stock KK4, then reinstalled CM7, starting with 7.1.0, then worked my way up to 7.2.0-RC0.
Testing the GPS again, the compass is working fine now. Looking at /data/system/yas529.cfg, I see the following:
Code:
14,19,16,39,-49,159,3,255,255,255,2147483647,2147483647,2147483647,0,
While in KK4, I also rooted and checked this file, and saw the following:
Code:
13,19,16,36,185,150,3,255,255,255,2147483647,2147483647,2147483647,0,
In either case, the compass worked fine. Perhaps worth noting is the fact that the 6th item in the list is actually positive, which may or may not be related to my previous observation that the compass rotation made no sense (not sure, really). I tried negating that number to see if I could reproduce the issue, but it didn't work (and in fact, calibrating the compass only flipped the number to positive, even though calibration always used to set it negative). Not sure what to say.
Anyway, all looks well now. For anyone else who runs across this issue, the only thing I can suggest is for you to just try reinstalling CM7 (and possibly reverting all the way back to stock if reinstalling alone doesn't help).
I find different apps have different results. There are compass apps that work. Keep looking
Sent from my SGH-I897 using xda premium
I didn't test only a single compass app; I tested several apps (Maps, GPS Essentials, GPS Status, to name a few), tested several different modems (JL3, JK4, KK4, to name a few), and calibrating various sensors (accelerometer/gyroscope, magnetometer, GPS). Nothing helped.
After the reinstall, the exact same apps with the exact same modems are working. The fact is that something was screwed up with the install that caused this.
- When the compass wasn't working, my install process was: KK4, Corn Kernel (without rooting), then straight to CM 7.2.0-RC0.
- Before then (when the compass was working previously), my install process was: KB2, root, CM 7.1.0, and then nightlies upward to 7.2.0.
- This time around (with the compass working), my install process was: KK4, Corn Kernel (with root), then CM 7.1.0, then CM 7.2.0-RC0.
I'm not sure I'm up for reinstalling repeatedly just to eliminate possibilities, but I suspect it may have been an issue with the install/upgrade process itself. Or just a random glitch. Either way, the moral of the story is that if nothing else helps, try reinstalling (possibly from stock).
Hi guys, I did some searching and couldn't find a fix so here goes:
Often when I put my phone to sleep (tap power-button) the screen turns black, then green again for half a second or so after the "screen off visuals".
I did some searching and it is similar to this "common issues" post:"Screen turns unusual colors / flickers colors when going to sleep or waking." http://code.google.com/p/ice-cream-sandwich-sgs/wiki/CommonIssues
The only thing is, Voodoo control app is now Voodoo sound plus and doesn't have a "Gamma offset" option anymore.
Does anyone know a tool that has Gamma Offset options, or any other fix to this issue for that matter?
It's not a big thing, as my phone is working fine, but I wanted to research it a bit further.
It has happened to me through many different ROMs, mainly ICS roms, but I am currently running ICS333 v.2.0.1 ICS 4.0.4, with the newest Devil Kernel for ICS.
*BUMP* in hope of info/help
- sorry mods if this is unacceptable.
I instaled 254 stock fw and seems like auto brightness is not working. When I chech auto, it just dims screen a little bit and that's all. It was the same on existenZ rom. Seems like it only worked only in CM11. Is that a common thing or is here some workaround?
Coming from Atrix 4G, i found the way the xperia SP handles auto brightness is pretty bad...
So i tried Lux, but it looked like my light sensor was screwed up... always returning 1 or 2 lux.
So i searched and managed to get it working again by installing this tool first, to disable auto brightness:
https://play.google.com/store/apps/details?id=com.hatcyl.android.Disable_Auto_Brightness&hl=fr
Then Lux would do the trick :
https://play.google.com/store/apps/details?id=com.vito.lux&hl=fr
Same here. Auto brightness is just low brightness. Something is wrong with the stock 4.1 because on SlimKat it works well.
pappbence said:
Same here. Auto brightness is just low brightness. Something is wrong with the stock 4.1 because on SlimKat it works well.
Click to expand...
Click to collapse
On Existenze 3.30, which is JB 4.3, auto brightness also is not working (or at least not working as I would expect it to be). So I guess its just has something to do with sony framework or smth.
Stock auto brightness (4.1.2/4.3) never worked properly for me. I'm using 'Velis auto brightness' app. Works like a charm..
This is my first Lollipop device after a long time with Kitkat, so I may be missing something obvious, but I just can't wrap my head around Adaptive Brightness.
So when it's set to on it adjusts the brightness based on the light sensor, but I can also use the slider to tweak it, correct? But then sometimes the slider just stops working, moving it doesn't change the brightness at all. Only way to make it work again is to change the lighting significantly (for example I point the phone at a lamp). After the auto-adjustment kicks in I can tweak it with the slider again. Is this a bug, or yet another misguided "feature"? Do I have a hardware problem? I've tried a few sensor apps and everything seems to work fine. On top of the auto adjustment not being as good as Kitkat's, the inconsistency is really bothering me.
EDIT: I am on stock rom. I'm sure that CM12 would solve this problem if it's a Lollipop bug, but I can't be arsed with a custom rom a this time. Looking for a stock based solution, or at least an explanation for this strange behaviour.
I have the C5J6 model and before upgrading to Mireks roms I was on the stock rom. While on stock my brightness was controllable, ranging from the expected low to very bright. After upgrading to Mirek v6.1 the brightness option was no longer controllable and appears to be at a set position. I can still move the brightness slider, but nothing actually happens. I have just moved up to v7 and the issue still exists.
I have the dual boot model, so to be sure I wasn't loosing my mind I booted into Windows and brightness is controllable and very bright at the highlest level, as I like it. So I know it's definitely related to something with the rom or Android in general.
Is there a fix to this, or something I am missing?
Aside from this Mireks roms have worked beautifully.
Thanx!
I seemed to have resolved this by installing a brightness app which worked on its own and then seemed to restore functionality to the native brightness control.