Been running AOIP for a few days now, really liking it - quick & stable, I did a clean flash coming from Baked (which I also liked...but needed wi-fi tethering to work). Thanks to all the devs for their support of this device!
I've just noticed a couple hiccups on my phone...can anybody else reproduce them:
compass, accelerometer sensor not working (proximity sensor ok)
voice dialer not working (hangs on 'starting up' box, and the mic image is crossed out)
screen rotation not working on some apps (namely GMaps and Sygic)
Seemed to be working ok on Baked, so not sure what is happening....is it my h/w or does anybody else have these issues?
Related
After trying all the ICS roms out there, I've come to the conclusion that my auto rotation and proximity sensors simply do not work within the OS itself.
Flashing back to a GB ROM confirmed that the the sensors are definitely working. And they work fine in 3rd party apps running on ICS... But neither auto rotation nor "screen off when in call" work at all.
It seems from a quick search that I'm not the only one with this problem (http://code.google.com/p/ice-cream-sandwich-sgs/issues/detail?id=224).
Anyone know of a fix?
EDIT: Never mind, guess it's a known issue: http://ics.samsung-updates.com/trouble/
Sensors working fine
With TH CM9 ICS running on my device i've no issues with the sensors. All working fine.
Did you try this ROM as well?
Never faced any sensor issue, ROMS tried Slim2.7,2.8,2.9 Team ICSSGS 2.11,3.1,4.2
Hi dudes
I'm having problems since few weeks with G-Sensor, it was stop working suddenly, ZDeviceTest says sensors are stucked in 0,0,0 always and any calibration app works (always stuck in 0,0,0). This problem affects to GPS orientation, to camera (undetect when is in landscape) etc.... only way to change to landscape is open keyboard and when close, screen remains in portrait.
I restored by default, rooted looking for to sensor config files, I test another ROMS (Cyanomod 10.2, SlimBean, Pacman, etc), restored to original ICS and JB and I don't know what I can do
Can somebody help me?
Thanks!
Yes, another proximity question!
I have trouble with this sensor using 3rd party apps.
On system it works fine without a problem (screen on/off during phone call never had any problems)
but any apps which use this sensor stops working after rebooting.
-Gravity screen on/off
-Automaton gestures
-Automate it!
These are the apps I tried and encountered problems with...so pretty much all of them!
The sensor works, cpuz sees it working with both distances 3cm near and 10cm far, but apps don't :S
For example if I try to record sensor state in automate it it just reads '10 far' and notihng else.
aamof rules with sensor far work fine but with near don't....
I encountered this problem both across 10.1 and 10.2 and different roms...anybody else encountered this isse?
I recalibrated tegra.so from adb...I'll try to go back to stock and try from there recalibration but seen thtat it "works"
I'm not sure how that is going to help.....
Rudjgaard said:
Yes, another proximity question!
I have trouble with this sensor using 3rd party apps.
On system it works fine without a problem (screen on/off during phone call never had any problems)
but any apps which use this sensor stops working after rebooting.
-Gravity screen on/off
-Automaton gestures
-Automate it!
These are the apps I tried and encountered problems with...so pretty much all of them!
The sensor works, cpuz sees it working with both distances 3cm near and 10cm far, but apps don't :S
For example if I try to record sensor state in automate it it just reads '10 far' and notihng else.
aamof rules with sensor far work fine but with near don't....
I encountered this problem both across 10.1 and 10.2 and different roms...anybody else encountered this isse?
I recalibrated tegra.so from adb...I'll try to go back to stock and try from there recalibration but seen thtat it "works"
I'm not sure how that is going to help.....
Click to expand...
Click to collapse
yeah, i noticed in viber screen doesn't turn off when you put your phone enxt to your ear. i dont have any other apps that use proximity sensor other than phone app, but that one works without issues.
the issue persists in stock as well as custom roms. no idea how it was on ics, though
It also appears on stock?! wow never would've thought...
It's a pretty considerable bug to have never been mentioned before...
all problems with proximity encountered so far always seemed caused by bad calibration..
this kinda sux :S
Devs and wise people, do you think this could be caused by the fact that the 'near' state is set at 3cm reading and 3rd party apps look for 0 distance with 0% tolerance to have widespread compatibility?
Do you think it is possible to change these settings?
I have Note8. It has a very strange sensors error, as below:
- All sensors, from proximity sensor, light sensor, to GPS, iris scanner, and all the other sensors do not work at all.
- In the app like Phone INFO Samsung, CPU-Z or AIDA64, in the Sensors section, all sensors do not work.
- The Auto Brightness function does not work (due to the light sensor), the brightness of the AOD screen is also not adjustable.
- When making a phone call and move the phone close to the ear, the screen does not turn off due to proximity sensor.
- Auto Rotation function is not working (due to rotation sensor).
- Google Maps shows inaccurate location. Other apps that rely on GPS (such as the speedometer app) are completely not working.
- The iris scanner function does not work either.
It was about two weeks ago. I've Wiped the cache, restart the phone but does not make sense.
Yesterday it suddenly returned to normal, I don't know why.
But today - while I'm typing this post - all sensors suddenly do not work again.
Any idea about the error and how to fix it?
Thank you guys
Best advice I can think of is to factory reset and see if that alleviates the problem.
If you did not do anything firmware-related, or you did not drop or submeged your device, the best you can do is to make a warranty claim, pure and simple, if you have no way to make such claim, well, next time you should consider getting a device from an official source
I've read other users have had same problem. Ones I read said it was motherboard issue had to have sammy replace it.
Thank you guys
There is also built-in sensor test. Open dialer and dial *#0*#
I noticed a problem when I was playing Asphalt (racing game on me Note 8). I am unable to use the Tilt controls to move the scar.
Testing out the Sensors using *#0*# at the dialer revealed that all the SENSORS was faulty.
I reset the whole phone just now. The issue is still there with the sensor. As expected Auto rotation doesn't work.
Running the latest version 8.0.
I recently changed my motherboard (under warranty) 3 months back cos something was faulty. Seems it may be another motherboard issue.
Anyone else in this thread solved the issue?
Hey everyone I'm facing the same problem. All sensors stoped working but they were working before on 7.1.1 and i updated my device to oreo and realized all sensors stoped
Then i got another updated for about 900mb i thought maybe this update will fix them and also that update said tha after updating the user cannot downgrade to nougat but after updating the problem still exsist. Please if anyone can help i also try to flash same oreo firmware with odin but doesn't fixed the sensors
I wonder if anyone has experienced issues with proximity sensor (elliptic labs).
In my case sensor is not working properly - I've run few tests and it senses proximity not reliably - sometimes work sometimes not. I can't find any pattern in its behaviour.
After some digging I've found a elliptic_sesnor.xml file in /vendor/etc , after changing from <near value="0.0" limit="3.0"> to <near value="0.0" limit="5.0"> is a bit better but still it works in maybe about 60% of cases.
I'm on crDroid 6.4 with Quantic kernel 1.9, issues were also present on stock MIUI, HavocOS, Disability, Descendant-X and EvolutionX.
I would be really grateful for any tips.