Hi,
I have a problem with proximity sensor and sometimes I can't hang up.
This is quite annoying when I get an answering machine because I have to remove battery.
I've installed HTC official 2.3.3 and I've notice that it's possible to unlock the screen during a call by pressing the power button and I'm fine with this solution.
However I prefer some other roms but it is not working the same way...
Do you know if there are other roms which have the same functionnality (power button to unlock the screen during call) as the official one? and preferably a sense rom.
Thanks
btw
I have already tried acesmod007, insertcoin and oxygen without any success.
As I could not find any ROM working the same way as the official one, maybe I should try to get the appropriate app from the official ROM.does anyone know how I could do that? Which app or files can I copy from the official ROM?
Or is it more complex to do?
Do u use some protecting screen or something that dosnt leave free the proxymity sensor (on the top at the phone) ?
Sent from my HTC Desire
No i'm not using a protector...I think there's dust on the sensor because when it's sunny it's working properly.I tried to vacuum it but the result isn't satisfying...
Coolexe rom with sense 3.5 works the way I wanted
Merci coolexe
Cool 3D Aces
For those who have the same proximity sensor problem:
This one is also working and has less bug than the bliss rom
http://forum.xda-developers.com/show...8#post12995138
Possible fix proximity sensor problem / lock screen in call
djokodi said:
Hi,
I have a problem with proximity sensor and sometimes I can't hang up.
This is quite annoying when I get an answering machine because I have to remove battery.
I've installed HTC official 2.3.3 and I've notice that it's possible to unlock the screen during a call by pressing the power button and I'm fine with this solution.
However I prefer some other roms but it is not working the same way...
Do you know if there are other roms which have the same functionnality (power button to unlock the screen during call) as the official one? and preferably a sense rom.
Thanks
Click to expand...
Click to collapse
Hi
I had the same problem using Leedroid 2.3.3 R5 (moving from Oxygen 2.2.2).
I had underclocked to 245mHz (I think)
I think I may have hit on a fix (only tried it today and it appears to work fine dialling with stock dialler and Contapps) :
Re-flashed Oxygen (full wipe incl cache and Dalvik)
Went to CPU settings
Changed CPU clock settings to 575(?) mHz
full wipe again
Re-Flashed Leedroid
did full install, Titanium apps restore etc.
It appears to have solved the problem.
I have a sneaky feeling that it might drain my battery a bit faster but as I said I've only done it today and haven't ran the phone for too long yet
Hope it works for everyone!
*UPDATE* Looks like I spoke too soon, it's stopped working. I can get the lockscreen toggle (power button) working sometimes in Oxygen, but it takes 10-20 secs - not great.
Even tried raising minimum CPU to 998 and it still didn't work.
Sorry for raising everyone's hopes!
:s
**UPDATE THUR 4TH OCTOBER**
Messed around a bit - updated the SU app (after uninstalling updates) - don't know if that had any effect but it got rid of unable to update binary error
Now Using :
GINGERvillain 3.1
Kernel 2.6.38.4-defrost-bravo+ [email protected] #891 (comes with GV 3.1)
Still a problem with lockscreen but power button seems to wake it every time
Good luck
Actually I'm having a hardware problem with the sensor and I just needed a workaround.
With some roms it's possible to unlock screen using power button so my problem isn't fixed but at least I can end the phone call when needed.
I'm using cool3d aces and it's working fine.
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Restore your previous ROM save
graymonkey44 said:
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Click to expand...
Click to collapse
Are you using a custom kernel. If so are you under / overclocking or over / undervolting?
Nope. I'm running whatever kernel comes with the ROM and no undervolting or overclocking either.
Anyone....?
Have you done a restore?
I would try wiping dalvik-cache and the cache partition. If that dosent work i would wipe everything and do a fresh install of a different rom to determine weather it is rom related or hardware related.
I rooted my girlfriend's S3 with no problems. I can install a TW rom and everything works as expected. If I installed a ASOP rom, when a call is made or received the screen turns off. If you pull the phone away from your ear the screen stays off. I've browsed around the forums, but have not found anything to resolve the issue. Any ideas of what might cause this on ASOP roms ?
Thanks in advance,
Richard
Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.
You could test the proximity sensor response. It might be flaky?
I use this app,
https://play.google.com/store/apps/details?id=com.tbs.activity
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
audit13 said:
Try different ROMs to see if the all do this, inlcuding a stock ROM. If they all do the same thing, sounds like it could be a hardware issue with the proximity sensor.
Click to expand...
Click to collapse
The only time it has been an issue is with ASOP roms. If I use a TW rom, there is an option to leave the screen on during a call. This is what I clicked to get the screen on during calls. However, with ASOP roms there is not an option for this. I don't think it's the proximity sensor since the screen stays on with calls on a TW rom. I forgot to mention that the ASOP was KK rom, but I have the same phone different cell provider and do not have this issue. I think I tried a JB rom with the same effect.
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
audit13 said:
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.
With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
Click to expand...
Click to collapse
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
riche1 said:
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
Click to expand...
Click to collapse
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
audit13 said:
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
Click to expand...
Click to collapse
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
riche1 said:
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.
If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
Click to expand...
Click to collapse
Without making any changes to the stock TW ROM dialer settings, does the screen go black when you place the phone next to your ear and come back on when you move it away from your ear?
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
riche1 said:
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
Click to expand...
Click to collapse
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
audit13 said:
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
Click to expand...
Click to collapse
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard
riche1 said:
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help
Richard
Click to expand...
Click to collapse
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
audit13 said:
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.
I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
Click to expand...
Click to collapse
she said it was not a problem until the phone was updated to 4.3 through ATT software update. This was way before I rooted the phone. The same thing started with her sister's phone. So.. I'm stumped as to what the problem could be. I rooted it because I thought CM11 might fix the issue and that was not the case. I don't know how I can go about fixing it. I don't want to take a chance in bricking the phone.
I got this phone about 1-1.5 months ago and it has been great to me except for one issue.
When I got the phone, I rooted it and installed Carbon rom 4.4.4 on it. Everything worked great except for one big problem.
When making or receiving a call, the phone would go straight to lock (screen off). the call would still go through but the phone would become very slow to wake back to the screen, and after unlocking, the Phone app (teleservice.apk) would not respond to any touch input. This meant I could not access my voice-mail, as I could not enter the pin. Using Developer options i was able to confirm that the touchscreen was still functioning. I had originally thought this was an issue with the specific version of CarbonRom that I had installed on the phone, so i posted to their thread in the hopes i could get an update/answer. CarbonRom for the T0lte has not been updated since 11-24-2014. I was done waiting so I decided to try another ROM. I first tried CM12, And while the phone app did now accept touch input, the phone still had alot of trouble waking after initiating or recieving a call, and the screen would turn off right after turning on most of the time. Then I tried a stable version of LiquidSmooth 3.2 (4.4.4) and it is still having the same problem.
The phone app is accepting touch input, but I can hardly get the screen to come on at all while a call is on. i am guessing an issue such as this presenting itself across 3 separate roms means something between the roms and the baseband/radio isnt communicating correctly? What am I doing wrong here? should I reflash the baseband? go back to stock and see if that works?
Baseband is T889UVUCMK7
CWMT recovery
Hey all!
This is happening to me for 2 months now, I was running official 12.1CM and now official 13CM
I tried to also use some stock based rom but im pretty sure it happened there too.
Whats happening to me is that randomly throughout the day my phone's screen turns black and I cant reboot it by any home button combination, only by getting out the battery.
When this happens the phone just totally freezes and I cant get it to respond or make a sound.
I don't think that the phone dies because sometimes when its freezes I can still see the notification led blinking.
Does anyone know why this might happen? or where can i copy some logs that might help you guys figure it out?
Thanks in advance!
sounds like you have the sleep of death issue? Personally I haven't been on CM roms much on my G3 so I haven't really encountered this issue but on my previous phone I've encountered this a few times on CM.
EDIT: Though it shouldn't happen on stock are you sure it happens on stock as well?
I have this issue as well using the Exodus rom. I never had it while using a stock rom, so I think this is a cyanogenmod issue (Exodus is a CM based rom in 5.1).
I have the exact same issue with my vs985. Seems to happen the most when viewing any sort of video, but I have had it happen at other times as well. Pretty dang annoying, probably 3-4 times a day. Using CM 13.0-20151217-nightly-vs985 but it started when I first flashed CM. Never had the issue on stock rooted rom.