Guest LSteam Posted June 1, 2011 Report Posted June 1, 2011 PROXIMITY FIXED BY ANOTHER WAY - WE CAN CLOSE THIS :D my 10 hours for this app > trash XD see you in the next thepasto or mine release with all sensors working :D
Guest sundawg Posted June 1, 2011 Report Posted June 1, 2011 PROXIMITY FIXED BY ANOTHER WAY - WE CAN CLOSE THIS :D my 10 hours for this app > trash XD see you in the next thepasto or mine release with all sensors working :D Sounds Good!! :o ...
Guest zorginho Posted June 1, 2011 Report Posted June 1, 2011 PROXIMITY FIXED BY ANOTHER WAY - WE CAN CLOSE THIS :D my 10 hours for this app > trash XD see you in the next thepasto or mine release with all sensors working :D old sensor fixed? great!
Guest zebbe77 Posted June 1, 2011 Report Posted June 1, 2011 PROXIMITY FIXED BY ANOTHER WAY - WE CAN CLOSE THIS :D my 10 hours for this app > trash XD see you in the next thepasto or mine release with all sensors working :D Good news!!!
Guest GameGain Posted June 2, 2011 Report Posted June 2, 2011 (edited) disable the switch's sensor from the menu "Call settings" by unchecking the "Always use sensor" and instead of adding the checkmark in the "Keep alwaus the screen on" the same menu. then, usually, fully functional :D Thank LsTeam, and ThePasto :D could you tell me wether you could see the checkcall running? i can't see it except APP management .thx. Edited June 2, 2011 by GameGain
Guest LSteam Posted June 2, 2011 Report Posted June 2, 2011 (edited) EDIT: THIS METHOD DOESN'T FIX 100% THE PROXIMITY SENSOR, WE ARE WORKING TO SOLVE THIS PROBLEM COMPLETELY OK IT'S TIME TO RELEASE MY WORKAROUND :D READY? 0) INSTALL OLDSENSORS PATCH 1) REMOVE all apps like sanity or mine 2) adb pull /system/build.prop 3) open build.prop in your adb folder 4) add this line at the end of the file: hw.acer.psensor_calib_max_base=32717 hw.acer.psensor_calib_min_base=32716 hw.acer.psensor_thres=500 hw.acer.psensor_mode=1 5) CHECK if there are other strings like hw.acer.psensor_X in your build.prop file and REMOVE them 6) save and close build.prop 7) adb remount 8) adb push build.prop /system/build.prop 9) REBOOT your phone 10) enjoy :D 11) and PLEASE, tell me if it works for you :9 bye! edit: oh...and thanks to thepasto for his precious help! start to working on LED issue :o Edited June 3, 2011 by LSteam
Guest albi86 Posted June 2, 2011 Report Posted June 2, 2011 OK IT'S TIME TO RELEASE MY WORKAROUND :D READY? 0) INSTALL OLDSENSORS PATCH 1) REMOVE all apps like sanity or mine 2) adb pull /system/build.prop 3) open build.prop in your adb folder 4) add this line at the end of the file: hw.acer.psensor_calib_max_base=32717 hw.acer.psensor_calib_min_base=32716 hw.acer.psensor_thres=500 hw.acer.psensor_mode=1 5) CHECK if there are other strings like hw.acer.psensor_X in your build.prop file and REMOVE them 6) save and close build.prop 7) adb remount 8) adb push build.prop /system/build.prop 9) REBOOT your phone 10) enjoy :D 11) and PLEASE, tell me if it works for you :9 bye! edit: oh...and thanks to thepasto for his precious help! start to working on LED issue :o Thanks :( Now i will try on miui 1.3.18 with old sensor !
Guest kubrick89 Posted June 2, 2011 Report Posted June 2, 2011 Using it with latest 1.5.27 miui by sundawg (compass working... so oldsensors??? ) and works really good... thank you so much for your work...
Guest bais Posted June 2, 2011 Report Posted June 2, 2011 Doesn't work on CM7 oldsensors. Screen just doesn't turn off...
Guest LSteam Posted June 2, 2011 Report Posted June 2, 2011 impossible... this patch change ONLY the uncovered value, not the covered... check covered/ucovered values with a sensor test please :D
Guest bais Posted June 2, 2011 Report Posted June 2, 2011 (edited) Sensor test always shows 1 as the value. But I don't use thepasto's ROM, since I get broken baseband after several reboots. I use f1rSt's ROM, but I changed the boot.img and lib folder with thepastos one, maybe that's what makes the ROM bug. (And yes, I applied the Oldsensors boot) Edited June 2, 2011 by bais
Guest LSteam Posted June 2, 2011 Report Posted June 2, 2011 i encourred the same problem, solved with flash thepasto rom
Guest bais Posted June 2, 2011 Report Posted June 2, 2011 I won't be able to use it if it requires thepasto's ROM. Dunno why I have the baseband problem, but well having fixed sensors when you can't call is pretty pointless. Wonder what is in thepasto's ROM which makes the Sensor work...
Guest Hilo27 Posted June 3, 2011 Report Posted June 3, 2011 OK IT'S TIME TO RELEASE MY WORKAROUND :D READY? 4) add this line at the end of the file: hw.acer.psensor_calib_max_base=32717 hw.acer.psensor_calib_min_base=32716 hw.acer.psensor_thres=500 hw.acer.psensor_mode=1 10) enjoy :D does not work, even with thepasto cm7, screen just doesn't turn on
Guest Winston Ma Posted June 3, 2011 Report Posted June 3, 2011 OK IT'S TIME TO RELEASE MY WORKAROUND :D READY? 0) INSTALL OLDSENSORS PATCH 1) REMOVE all apps like sanity or mine 2) adb pull /system/build.prop 3) open build.prop in your adb folder 4) add this line at the end of the file: hw.acer.psensor_calib_max_base=32717 hw.acer.psensor_calib_min_base=32716 hw.acer.psensor_thres=500 hw.acer.psensor_mode=1 5) CHECK if there are other strings like hw.acer.psensor_X in your build.prop file and REMOVE them 6) save and close build.prop 7) adb remount 8) adb push build.prop /system/build.prop 9) REBOOT your phone 10) enjoy :D 11) and PLEASE, tell me if it works for you :9 bye! edit: oh...and thanks to thepasto for his precious help! start to working on LED issue :o Thanks Should I just follow your steps here or just flash the zipped file on the first post? Does oldsensor means eclair rom?
Guest GameGain Posted June 3, 2011 Report Posted June 3, 2011 OK IT'S TIME TO RELEASE MY WORKAROUND :D READY? 0) INSTALL OLDSENSORS PATCH 1) REMOVE all apps like sanity or mine 2) adb pull /system/build.prop 3) open build.prop in your adb folder 4) add this line at the end of the file: hw.acer.psensor_calib_max_base=32717 hw.acer.psensor_calib_min_base=32716 hw.acer.psensor_thres=500 hw.acer.psensor_mode=1 5) CHECK if there are other strings like hw.acer.psensor_X in your build.prop file and REMOVE them 6) save and close build.prop 7) adb remount 8) adb push build.prop /system/build.prop 9) REBOOT your phone 10) enjoy :o 11) and PLEASE, tell me if it works for you :9 bye! edit: oh...and thanks to thepasto for his precious help! start to working on LED issue :( i think my p-sensor is broken... :D the two methods don't work on my device and many friends said the two methods are ok .long time with cm7, so i dont know wether my sensor is ok now. let me check my device in offical 2.2 rom later
Guest LSteam Posted June 3, 2011 Report Posted June 3, 2011 i found the last bug of proximity...will fix next week sorry :D
Guest GameGain Posted June 3, 2011 Report Posted June 3, 2011 i found the last bug of proximity...will fix next week sorry :D I will anticipate very much . thx for your hard work!
Guest LSteam Posted June 3, 2011 Report Posted June 3, 2011 ok now i'm back from school... essentially...after 5/10 seconds from the screenoff the phone go in a kind of sleep mode and don't care about sensors or others... you can check thi in this way: make a call and after 1 second from the screenoff press VOL - ...the call volume will decrease... IF you make a call, put the screen off (with your face near the phone or with power button), wait about 15 seconds and press VOL - (or VOL + :o) the volume of the call WILL NOT decrease... because the phone is sleeping... so...with my patch sensor work very fine, but the phone sleeps and don't care about it :D with the ORIGINAL acer kernel this problem doesn't appear and the sonsor during a call works fine... so i think that it is another bad commit of chocolate-kernel... me and thepasto will investigate very soon :D as always, sorry for my bad english :(
Guest zorginho Posted June 3, 2011 Report Posted June 3, 2011 ok now i'm back from school... essentially...after 5/10 seconds from the screenoff the phone go in a kind of sleep mode and don't care about sensors or others... you can check thi in this way: make a call and after 1 second from the screenoff press VOL - ...the call volume will decrease... IF you make a call, put the screen off (with your face near the phone or with power button), wait about 15 seconds and press VOL - (or VOL + :o) the volume of the call WILL NOT decrease... because the phone is sleeping... so...with my patch sensor work very fine, but the phone sleeps and don't care about it :D with the ORIGINAL acer kernel this problem doesn't appear and the sonsor during a call works fine... so i think that it is another bad commit of chocolate-kernel... me and thepasto will investigate very soon :D as always, sorry for my bad english :( tnx for ur work we're waiting for news
Guest LSteam Posted June 3, 2011 Report Posted June 3, 2011 ok the story is really hard... i think that a good workaround it to apply my patch and use sanity that force the phone to stay awake... please do some test with my patch and sanity and tell me if you encour problems...thanks :D
Guest LSteam Posted June 3, 2011 Report Posted June 3, 2011 and i noticed that we don't have to enable proximity feature of sanity app, just bring it install to run during a call and bring the phone awake :o so it will be simple (really?) to find what code bring the phone awake ant implement it in liquidsettings :D a step closer to a final solution... :D
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now