30 replies to this topic

[C3C0]

Or you could chmod a-w prox file to remove write permisson so no app can overwrite it.

[Wacky.ddw]

C3C0, on 14 March 2012 - 08:16 PM, said:

Or you could chmod a-w prox file to remove write permisson so no app can overwrite it.

Wow you lost me there

I wouldnt know how to do that. But if the other people who are having the same problem as me can confirm this works, its would be really nice if someone could make a flashable ZIP that does this for them it should be really easy since its only flashing a .txt file to a directory. But i have 0 expirience with these things

Maybe make the file Read only so i cant be changed so the sensor keeps working.

I edited the first post so people can test if it works on there phones, ive test it over and over for a long while now. And how i explained it in the first post is the only solution that keeps working for me

[C3C0]

OK. Here is the flashable zip which will:

1) install prox_threshold.txt with correct value

2) make the file read-only so it can't be overwritten by proxcal apps.


http://ceco.sk.eu.or...2771-update.zip

[Wacky.ddw]

C3C0, on 14 March 2012 - 09:23 PM, said:

OK. Here is the flashable zip which will:

1) install prox_threshold.txt with correct value

2) make the file read-only so it can't be overwritten by proxcal apps.


http://ceco.sk.eu.or...2771-update.zip

Thanks for the help i really appreciate it!

Im making a backup now, i will try reflashing atomic and then your fix and tell if it works. Anyway im really happy i can finally call normally again

[C3C0]

Ok. Good luck :-)

[Wacky.ddw]

Ok the value i posted in the fist post was wrong it seems only  "H601L1G32" works. The value from your phone "H601L4G32" give's me a black screen instantly i had to remove my battery.

I opened your ZIP file and changed the 4 to a 1 flashed it again, and it works like a charm now When i try to calibrate the proximity sensor in atomic mod settings it says "callibration failed" wich is better then force closing .

Should i reupload the version with the number changed or do you want to do it?

[C3C0]

Feel free to provide your owm link in the first post... anyway i suppose that while L1 will  work on some phones L4 may work on others. I think this should also be mentioned in the guide providing guidance on how to change it in zip before flashing.

Edit: or simply give link to both versions + guidance on how to change if non of them work

Edited by C3C0, 14 March 2012 - 10:19 PM.

[tilal6991]

Or another solution is just to use the cm sensors lib which works for everyone.

[Wacky.ddw]

C3C0, on 14 March 2012 - 10:17 PM, said:

Feel free to provide your owm link in the first post... anyway i suppose that while L1 will  work on some phones L4 may work on others. I think this should also be mentioned in the guide providing guidance on how to change it in zip before flashing.

Edit: or simply give link to both versions + guidance on how to change if non of them work

Ok i changed the first post, if you cant to see anything changed just ask

@tilal: What are you talking about, its something devs must add right? because i wouldnt know how to change add things like that in a ROM.

[mrmonster]

cant understand why people dont just use the 'keep screen' app if there having proximity issues.......works a treat.

just activate dialer and dialer storage in the applications settings of the app.

[Wacky.ddw]

mrmonster, on 15 March 2012 - 08:35 AM, said:

cant understand why people dont just use the 'keep screen' app if there having proximity issues.......works a treat.

just activate dialer and dialer storage in the applications settings of the app.

Because it should work... it allways worked so why would i want to use a app to keep my screen on, it consumes mutch more battery then if the screen goes black. Anyway it works like it should now.