I2C Problem? All sensor tests show a FAIL

asked 2014-10-26 00:41:27 +0300

Jörg

1113 ●16 ●22 ●24

updated 2014-10-27 13:39:00 +0300

I am still on 1.0.8.21 and as of yesterday I am having the following problems:

The proximity sensor seems to be going wild. Double-tap does not work, I can't take incoming calls (the screen stays black), and as soon as I press "Call" when making a call the screen also goes black. Although I found questions here with the same problem, I did not find a workaround to solve the problems. Reboot or taking out the battery did not help. csd shows a FAIL after the proximity sensor test and after all other sensor tests.
After a while the phone locks into landscape mode, i.e. any app, which supports landscape is automatically locked to landscape. When this happens dmesg is clogged with the following lines

[ 4464.821790] qup_i2c qup_i2c.12: Recovery failed due to undefined GPIO's

[ 4464.821882] qup_i2c qup_i2c.12: Transaction timed out, SL-AD = 0x10

[ 4464.821912] qup_i2c qup_i2c.12: I2C Status: 132100

[ 4464.821973] qup_i2c qup_i2c.12: QUP Status: 0

[ 4464.822004] qup_i2c qup_i2c.12: OP Flags: 10

(I can force the apps to portrait using the settings. )

Basically the phone is not usable at the moment (AGAIN). Any idea what's wrong?

edit retag flag offensive close delete

Comments

Looks very much like a hardware problem to me. The sensors (both proximity and orientation) communicate via the I2C bus, and that seems to have trouble. Screen going black may be related or may be an unrelated issue, possibly also caused by the same hardware problem.

dthierbach ( 2014-10-26 12:42:39 +0300 )edit

Agree with the previous commenter, looks like a hardware issue. At least ALS, proximity, gyroscope, and I guess also accelometer are behind that I2C bus number 12. Seek service for your device.

The screen going black is most likely because the proximity status cannot be read. For screen orientation same thing with accelometer.

kjokinie ( 2014-10-27 09:28:24 +0300 )edit

answered 2014-10-27 09:47:40 +0300

spiiroin
13237 ●151 ●224 ●199

moderator

Broken/dirty/otherwise stuck to "covered " proximity sensor would explain all of (1), but (2) makes it likely that it is not just the proximity sensor.

Anyway, as a temporary workaround you could use:

mcetool --set-ps-mode=disabled -> proximity sensor is not used; logic assumes uncovered

But then display will stay on & active during calls (need to be careful not to touch the screen with chin/ear), double tap detection stays active also in pocket (can consume more power / generate false positives) and display will turn on unconditionally when there is incoming call, alarm, etc (pocket calls etc are more likely).

These might help to some extent:

mcetool --set-doubletap-wakeup=never -> double tap detection is kept disabled
keep display pointing outwards when device is in pocket -> no capacitive touch from adjacent skin

Comments

@spiiroin: Thanks for your help. I'll give it a try this evening to do a factory reset (2 days work to get everything in place again). If the problem persists I'll contact service. If this is a hardware problem then it would be the third time I have to send in the phone due to hardware problems. Although I really like my Jolla and I am one of the early supporters from July last year, I am getting kind of frustrated. Just wondering whether it's just me having bad luck or whether the build quality of the hardware is really so exceptionally bad. Just ordered a Lumia.

Jörg ( 2014-10-27 11:00:24 +0300 )edit

After rsyncing /home/nemo to my NAS yesterday, I made a factory reset and the problem was gone, I could double-tap again (Hooray!), but after going through the intro and creating the Jolla account the problem re-appeared (Oh, no!). I did not update the firmware or install any apps. So I think this is a case for Jolla care. I already wrote them an email. Currently I am using my good old N8 again.

Jörg ( 2014-10-28 09:54:03 +0300 )edit

I2C Problem? All sensor tests show a FAIL

Comments

1 Answer

Comments

Question tools

Stats

Related questions

I2C Problem? All sensor tests show a FAIL

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions