[hlte][2014/DEC/07][CM11/12] Yank555.lu kernel v1.1c-beta6

[ezaechiel]

Thanks Kenzolo

@yank : if it's not kernel related why I don't have the problem with CM stock kernel? I don't really understand. And I'm not saying that's kernel related, just want to understand I'm curious.

Envoyé de mon SM-N9005 en utilisant Tapatalk

[yank555]

Thanks Kenzolo

@yank : if it's not kernel related why I don't have the problem with CM stock kernel? I don't really understand. And I'm not saying that's kernel related, just want to understand I'm curious.

Envoyé de mon SM-N9005 en utilisant Tapatalk

What I meant is, the calibration and the re-calibrating, is totally kernel unrelated, it just tells the system (whichever kernel you're on) how to read the proxy sensor value so it can tell if proxy is closed or open.

The proxy has (in my case) values from 0 to 1004 ... those need to be translated into "proxy triggered yes/no", so the question in the calibration is, when does the system consider a yes and a no

That is what you would write into the file in the /efs partition, which survives full wipes, ROMs and kernel flashing.

Now as to the proxy code in my kernel, it's 100% stock CM code, only thing I added is just a function so touchwake can read the current raw value, I do the interpretation in touchwake all by myself, this is all that has changed in the code, if you can read C, you'll see it's just about reading, I don't interfere with it at all.

JP.

[ezaechiel]

Thanks for explanation , yes I could read C, I'm a developer too , so I don't really understand why this issue happens only when I flashed the kernel and not with the CM stock one , that's pretty weird I don't see the reason in your code.

Envoyé de mon SM-N9005 en utilisant Tapatalk

[ezaechiel]

Hello in my case cat prox_cal tells me : 0,120,80.

Which one might I take? 120?

Envoyé de mon SM-N9005 en utilisant Tapatalk

[yank555]

Hello in my case cat prox_cal tells me : 0,120,80.

Which one might I take? 120?

Envoyé de mon SM-N9005 en utilisant Tapatalk

As I understand the procedure, it would be 0.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Temasek v85 on Yank555.lu htle v1.0b-beta8 (3.4.92) kernel.

[yank555]

I checked, I have a 0 on state and 0,120,80 as prox_cal.

Important, for state, there must not be anything close to the proxy sensor, or the value will be off.

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Temasek v85 on Yank555.lu htle v1.0b-beta8 (3.4.92) kernel.

[ezaechiel]

Hmm on state I have 61 with nothing close to my sensor. I missed something?

So if I take 0 the sum of prox_cal and state will be the same as state, it could be a problem for the calibration no?

Envoyé de mon SM-N9005 en utilisant Tapatalk

[yank555]

Hmm on state I have 61 with nothing close to my sensor. I missed something?

So if I take 0 the sum of prox_cal and state will be the same as state, it could be a problem for the calibration no?

Envoyé de mon SM-N9005 en utilisant Tapatalk

Not really, that would just set the offset to 61, so at real 61 it will be read as 0, thus 120 and 80 are applied again as thresholds.

But if you have sth different than 0 without anything in front of the proxy, there's very likely dirt or humidity in there

JP.

[ezaechiel]

Oh OK, so with cat prox_cal at 0,120,80 and cat case at 61 when nothing in front of the sensor I'm good in fact?

Envoyé de mon SM-N9005 en utilisant Tapatalk

[yank555]

Oh OK, so with cat prox_cal at 0,120,80 and cat case at 61 when nothing in front of the sensor I'm good in fact?

Envoyé de mon SM-N9005 en utilisant Tapatalk

No you're off by 61 ...

The supposed 0 for you now lies at 61, so you need to tell the system.

If I get the cal values correctly, going above 120 triggers proxy to yes (screen off in call), going below 80 triggers it to no.

In your case adding 59 you already reach 120, that's too fast, so even with sth far from the proxy, or dirt moving, you're on the wrong side already, and may not get below 80, and your screen stays off.

Setting the offset to 61 will adjust it back to 'norm', so reaching 120 when getting close to sth will trigger a yes again only if 120 'more' is detected instead of only 59.

It'smas if your speedometer in your car was showing 61kmh when your car is stopped. You need to remember to withdraw 61 from the current reading when driving so you know your real speed

JP.

Send from my 'proudly eFused' Note 3 (n9005) running SlimKat 5.8 Weekly on Yank555.lu htle v1.0b-beta9 (3.4.92) kernel.