Database Info

In Call Screen Off

I resolve the HD2 problem for proximity sensor bug during call with this steps:
1. turn off vibration for connecting (go to dialer menu)
2. turn off dialer keypad sound (via HD2Tweak 1.2)
3. install Touch in call screen tweak 1.2

Hi !
Could explain a little bit the "proximity sensor bug during call" you're facing ?
Which ROM verison are you using ?
thanks a lot !

papagon said:
Hi !
Could explain a little bit the "proximity sensor bug during call" you're facing ?
Which ROM verison are you using ?
thanks a lot !
Click to expand...
Click to collapse
When I dial , the screen go off without any association with proximity!
both original & energy ROM

Hi !
Thanks for your answer...
My problem is slightly different, but involves radio ROM and winmo drivers, because everything was fine with stock ROM 1.48.406.1 and radio ROM 2.15.50.14.
Now that I'm using the stock ROM 3.14.406.2 (wich includes radio 2.15.50.14)
when i'm in a call, the screen stays off even if the phone is no longer on my ear...
So that's why I as interested by your solution, but it does nothing on my phone...
With this last official update from HTC, i'm now facing keyboard sensitivity issues (everything was alright with prévious ROM and HTC patch for the sensitivity), and this proximity sensor problem...

i find the case can make the sensor play up as most manufacturers dont account for the sensor

jonpickles70 said:
i find the case can make the sensor play up as most manufacturers dont account for the sensor
Click to expand...
Click to collapse
please explain more.

manufacturers dont put cut outs on cases or they arent big enough so the sensor is then covered

Dim red light next to proximity sensor

Hi,
I just saw today, that there was a very weak red light just next to the proximity and light sensor. It looked like it was flickering at a very high rate!
I tried to restart the phone normally, but the light didn't disappear. After that I tried a reset by holding the power button down for 10 seconds. That made it vanish.
What the f**k was that all about???
Best regards
Casper

If you were making a phone call, the red flashing light is normal It's the proximity sensor. If you were doing nothing, it should not be seen the red light, might be faulty.
Sent from my HTC One S using XDA

Moved To Q&A​
This is best in the Q&A section, as it been written as a question.​

h.han said:
If you were making a phone call, the red flashing light is normal It's the proximity sensor. If you were doing nothing, it should not be seen the red light, might be faulty.
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Its The Goverment Spyin On us...Making Sure We Dont Flash Anything Or Even Root...If So It Will Say Tampered And The S.W.A.T. Team Will Come Crashin in Our Homes...

That red light is in fact the actual proximity sensor and it's in use while in a call. If you where not in a call then that was a strange occurance unless you ran some of these sensor testing apps...

Well, I wasn't in a call. I had been calling someone through the hands-free in my car on my way to work, where I discovered it about 10-15 minutes after the call was finished...

cawith said:
Well, I wasn't in a call. I had been calling someone through the hands-free in my car on my way to work, where I discovered it about 10-15 minutes after the call was finished...
Click to expand...
Click to collapse
That was an odd one... maybe it was a temporary fluke? Strnag nonetheless...

I often use face unlock. The red light turns on when the front cam turns on.
Sent from my HTC VLE_U using XDA

any tips on how to trouble shoot this? I wish I could figure out which app (if any) is causing the proximity sensor to stay lit.
I've heard it's related to an autobrightness tweak, but it appears even when tweak is not applied, across multiple roms. The only commonality between my roms is the apps I have installed.
I've tried multiple proximity sensor testing apps and, it's working.. it's just always lit up.

decalex said:
any tips on how to trouble shoot this? I wish I could figure out which app (if any) is causing the proximity sensor to stay lit.
I've heard it's related to an autobrightness tweak, but it appears even when tweak is not applied, across multiple roms. The only commonality between my roms is the apps I have installed.
I've tried multiple proximity sensor testing apps and, it's working.. it's just always lit up.
Click to expand...
Click to collapse
Same here. Have to restart to get it off again. Any help? (TrickDroid 4.3)

Anytime you make a call by any means other than handset to your ear, the proximity sensor will come on and stay lit until reboot or until you make another call via handset.
Example:
Place call> turn on speaker phone> hang up - proximity sensor will stay lit after call;
To fix do this:
Place call from handset (not using speaker phone or hands free) and hang up right away, or reboot device and light will go out.
Same seems to go for calls through hands free as well.

These guys are lying its a bomb isn't it obvious flashing red light HTC controls it if u do something they don't want u to do boom ur hands are no more why do u think the phone heats up so much its a warning don't believe me read the thread in forums about heats in the one s another reason they don't want us to remove back well see the bomb :what:
Sent from my HTC One S using xda premium

Hi All,
My One S also does this. I'm finding it a pain to have to make a call after using speakerphone to turn the proximity sensor off again. Has anyone found out what the cause of this is?
I've tried clearing cache partition with HTC support but still no fix.

Hi all, I forgot to mention that the issue on my phone only happens when the call is ended with speakerphone active. If I turn off the speakerphone before ending the call it does not happen.

Hey brothers.. I had the same problem with the proximity sensor not turning off.. Even after so many restarts resets... Finally I just opened the original task manager of the one x, and push "stop all" .. and YES!! the sensor was turned of and stopped lighting.. After that I tried calls with speaker phone or not.. No problem.. Now it is working how it has to...

Sv3TL10 said:
Hey brothers.. I had the same problem with the proximity sensor not turning off.. Even after so many restarts resets... Finally I just opened the original task manager of the one x, and push "stop all" .. and YES!! the sensor was turned of and stopped lighting.. After that I tried calls with speaker phone or not.. No problem.. Now it is working how it has to...
Click to expand...
Click to collapse
You maybe have turned off Viber doing this: http://www.boards.ie/vbulletin/showthread.php?p=80972874
Does it come back after restarting Viber?

Sometimes a restart fixes the problem.

I had the same problem. I uninstaled Viber and the light disipired.

foner81 said:
You maybe have turned off Viber doing this:
Does it come back after restarting Viber?
Click to expand...
Click to collapse
Later I realized that Viber is the reason. Yes. But now it seems that Viber is fixed after last update, and no red light when viber is turned on

[Help Eachother] STOCK / CM11 Issues&Solutions

The point of the topic:
Post your issues found in STOCK / CM11 or post a solution.Simple as that,very productive.
I'll start with a list of bugs:
CM11 ISSUES:
-Video recording lags in reduced luminosity.
-The phone heats too much when playing/watch videos for long time and so on.
-Volume during call is too low.
-Ocasionally freezes & crashes.
-Some graphical issues when the phone freezes.
-Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
STOCK ISSUES:
-Video blinks in low light(from what I've read it focuses wrong on the light source and starts blinking).
-The proximity sensor remains on after a missed call.
-Multi touch doesn't work as well as on CM11.
-Some weird freezes during call ( the screen remains off / freezes and you can't end the call / sometimes even answer )
-Camera doesn't have as much detail as in CM11 ( if you zoom in,the image doesn't clarify).
-Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
CM11 FIXES:
-Lag in video recording can be reduced by lowering the exposure.In medium to low light " - 1 " works pretty good and in very low to low light " - 2 " .However,when you use " - 2 " ,the recorded video will be very dark.Still haven't found a solution for this.
-About heating problem,you might want to try @Shivam Kuchhal 's kernel.He reported that his phone doesn't get heat up more than normal.
-About volume during call,it's been solved partially in newer releases by editing snd_soc_msm file.However,if the value is too high,the phne volume will also be too high and the speaker will produce distorsioned sound.However,I see they found a resonable value and both,the volume during call & speaker is about fine.
-For headset buttons not working,you must edit Generic.kl file.Here's a short tutorial to help you:
Go to: system/usr/keylayout/Generic.kl and change as below
key 226 HEADSETHOOK
key 256 BUTTON_1
change to
key 226 BUTTON_1
key 256 HEADSETHOOK
STOCK FIXES:
-For proximity sensor and weird freezes during a call use this tutorial .Haven't tested it personally,but people reported it works even on latest .17 fw.
-For Mac issue [ works for cm11 as well ]
1)Restore original MAC Address
Open /data/etc/wlan_macaddr0
Copy it's content. Ex: 01:12:13:14:15:16
Open /etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
Find this line
Code:
Intf0MacAddress=000AF58989FF
Replace 000AF58989FF with the content of wlan_macaddr0, but write back to front. Ex: from 01:12:13:14:15:16, write to 161514131201. So it will look like this
Code:
Intf0MacAddress=161514131201
Save & Exit, Reboot the phone
That's all for now,continue to post bugs&fixes and most important:
HELP EACHOTHER

Marius Cristian said:
The point of the topic:
Post your issues found in STOCK / CM11 or post a solution.Simple as that,very productive.
I'll start with a list of bugs:
Click to expand...
Click to collapse
Proximity fix not working!!!

More Kitkat Bugs List:-
1. Headset buttons
2. Camera experiencing crashes randomly, sometimes cause overexposure and being unstable at flash mode
3. Black graphical glitch/scanning effect first time after you turn your screen off then on again after first restart/turning on phone.
4. Call bugs(e.g. distortion etc.)
5. Lag when using the video camera
6. battery draining faster then on stock rom. (was improved on early nightly releases....now its back again)
7. GPS not working again (for some it does...others it doesnt....again...wasnt there on first nightlies)(Mostly Happens In CM11)
8. Camera quality is much,much worse then on stock rom
9 . Phone may left hanging and screen wont turn on for several seconds...
10. Some apps are unsupported on playstore...

CM11 bugs
CM11:
1. Switch to HDR mode and within 3 snaps camera app will FC.
2. Headset buttons.. I have to manually edit that Generic.kl after every nightly update.
3. As mentioned above, graphical glitch after updates.

Some of bugs that u mentioned @David pro has been fixed by users, but device maintainer didn't merged it for some reason in official builds. So, get started:
1. These buttons can be fixed, someone(I don't remember who, Sorry) has created a modified Generic.kl. You can find that file somewhere on this forum.
2. Camera quality is medium, but videos are very poor..
3. Still exist
4. @up
5. As I said, videos are bad
6. Caused by Google Play Services, 1st method is use xposed Framework and one of its add-ons, 2nd is just disable Services from Settings>Apps(i'm using second one, because I just don't like Xposed)
7.GPS is working fine, at least for me. No fix needed
8.Yep, on stock it is better.
9.It's caused by "Black graphical glitch/scanning effect first time after you turn your screen off then on again after first restart/turning on phone."
10.Well, some of them are only for one platform or type of devices,eg. Tegra 4 games.

No heating issues noticed so far(I use my kernel obviously) and yeah the camera and video quality isn't anything worth praising. Also the hwcomposer issue happens only one time after every boot, after that its all fine.
I normally use AOSPA.

Actually,I think the cm11 camera takes better photos than stock,but it can be buggy sometimes :silly:
About GPS,it's working fine for me too.
About video camera being laggy...I think it's because our phone lacks drivers update.It's hard to believe the video camera will ever be 100% fixed.
I'm sorry I'm kinda busy those days and I don't have time to administrate this thread.I'll edit the main post as soon as I can with solution you guys posted.But it's true,there are things which can't be fixed.Until I come back, HELP EACHOTHER

an another bug with stock rom is that "camera not available "or the camera takes a long time to recover after taking a shot
chrome browser restarts the phone or makes the phone to hang

vishalaestro said:
an another bug with stock rom is that "camera not available "or the camera takes a long time to recover after taking a shot
chrome browser restarts the phone or makes the phone to hang
Click to expand...
Click to collapse
Haven't experienced those kind of issues when I used stock.Try to do a factory reset or flash the ftf again.Maybe you added some mods or apps which affected the system.
Overall,we have to admit that CM11 is blazing fast and that's why I'm still using it.I'll update the OP now with your solutions.Thanks guys and keep helping eachother.

Marius Cristian said:
Haven't experienced those kind of issues when I used stock.Try to do a factory reset or flash the ftf again.Maybe you added some mods or apps which affected the system.
Overall,we have to admit that CM11 is blazing fast and that's why I'm still using it.I'll update the OP now with your solutions.Thanks guys and keep helping eachother.
Click to expand...
Click to collapse
another BUG with the stock ROM
1)walkman app flickers in the widget lockscreen
2)poor memory management need to restart the phone daily else the phone lags like a hell
3)camera app didn't respond ,it doesn't even the focus sometimes ,clearing the app data solves this problem temporarily and i think it was not present with the .12 update ,so if anybody could extract the camera app from the .12 update similar to the phone app freeze issue the problem might be solved.
3)walkman app or any other music player makes music to stutter when the same song is played more than one time provided if the songs are stored in memory card also i know that my sdcard doesn't have any problem because it worked fine with galaxy s3.my sd card is sandisk ultra class 10 32 gb
4)battery drain heavy when wifi is switched on compared to previous android 4.1.2
note:i have not rooted my phone or modded my firmware .all i run is the apps taken from the playstore.i have done a factory reset for more than 4 times.

CM11 / Stock (using custom kernel) bug:
Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
Solution:
Restore original MAC Address
Open /data/etc/wlan_macaddr0
Copy it's content. Ex: 01:12:13:14:15:16
Open /etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
Find this line
Code:
Intf0MacAddress=000AF58989FF
Replace 000AF58989FF with the content of wlan_macaddr0, but write back to front. Ex: from 01:12:13:14:15:16, write to 161514131201. So it will look like this
Code:
Intf0MacAddress=161514131201
Save & Exit, Reboot the phone

solution for Play Services battery drain in CM11

CM11 issues
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.

chinmay1234 said:
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
Click to expand...
Click to collapse
Nfc icon not in statusbar is on all cyanogenmod/aosp based rom

chinmay1234 said:
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
Click to expand...
Click to collapse
1. For many people works,for some don't.I don't understand how's possible...
2.Haven't tested it...for me it's a useless feature.
4.Well,crashes happens.However,they're not too frequent.
5.I really like the photos cm11 takes.About video...another story.Try to notice the details in the photos in comparison with stock.
I am going back to stock in order to see if I can obtain(with all the bug fixes from here) a more stable software than cm11.I'll report to you soon guys.Until then, help eachother

@underd0g
Nice fix for WiFi-Mac interference problem. :good:

Marius Cristian said:
1. For many people works,for some don't.I don't understand how's possible...
2.Haven't tested it...for me it's a useless feature.
4.Well,crashes happens.However,they're not too frequent.
5.I really like the photos cm11 takes.About video...another story.Try to notice the details in the photos in comparison with stock.
I am going back to stock in order to see if I can obtain(with all the bug fixes from here) a more stable software than cm11.I'll report to you soon guys.Until then, help eachother
Click to expand...
Click to collapse
guys please try to solve the issues with stock ROM because they are the stable ones and the bugs are easily repairable if the bugs are reached to right hands.so pls first concentrate on stock ROM

I've been playing around with 4.4 video recording..what i think is the lags occurs when we record in low lights related with the kernel..i'm testing with snapcam as its has auto flash when recording in low lights..First result is same as stock..but in snapcam it has touch to focus when recording..after touch,the recording will get a bit darker when it refocus and walla..no lags..
What i found is, the camera will automatically reduced the exposure to -1 for avoiding the lags even it is on default setting..
When moving the camera in low lights,the recording will lags again after few second..that is with continuous focus..set to normal or auto..no lags..so our stock cam using continuous focus for recording..
Back to the kernel thing..from what i see from the recording is same like this when i'm playing with cnt rom to to get wifi and overclock working.

Ok,so I went back to stock.I'm amazed by the battery life,it lasted 2 days and I used the phone a lot ( especially for calls ).
However,after using the fix for freezes during call and so on,I still have experienced this morning an issue.While I was talking to someone,someone else called and the phone was beeping but the screen was frozen.I had to press the power button to lock the device then unlock it to get the screen to show who's calling and to give me the possibility to answer the call.What do you think I should do?For now I'll wipe phone app data,but I'm also waiting if someone knows a good,another solution to post.

Anyone know a way to remove the automatic shutdown?
My phone shuts down if it reaches 25%

List of Bugs and Some software changes need to be made, for an Perfect MI A1

I have listed some of bugs and some software changes need to be made, so that MI A1 will be an perfect mobile.
1. Slow motion (Bug).
2. Electronic image stabilization (EIS).
3. Fingerprint scanner (Animation is slow).
4. Night mode in display (Blue filter).
5. Double tap (Wake up screen).
6. Selfies (Take pics with fingerprint).
7. FM (Radio).
8. Enable flash in portrait mode.
9. Network Stablity Isssue (Bug).
10. Front camera pictures are soft (Lacks detail and sharpness).
11. Low light photography (Noise must be reduced and details must be improved).
12. Ambient display (If i receive any notification, when i clicked, it is not responding).

Does this phone have FM radio (hardware)?
Regards

How many of these can be fixed with updates?
My ambient display is working fine mate
Sent from my Mi A1 using Tapatalk

No matter where you live or what xiaomi phone you have just put .eu ROM its a stock based extremly optimized even better than official global, and supports many languages..

mochoandre said:
Does this phone have FM radio (hardware)?
Regards
Click to expand...
Click to collapse
Yes

Another issue that I seem to be having is with notification tray. When I unlock the device and swipe down to open the notifications, it lags horrendously, same when I try to swipe up or away them. Everything else seems to be pretty good.

same issues with my Mi A1
I have also observed the same bugs/issues that need to be fixed in Mi A1. All of the bugs can be fixed with a software patch/update.
I would like to add that the call app doesn't display caller pictures. It instead displays a blue wallpaper.
The ambient display feature works but the screen doesn't activate when we tap on the screen like it should or does on other phones which have an ambient display.
The slo-mo is more like time lapse. It speeds up the rest of the video and plays the selected part at a normal speed.
asrupesh said:
I have listed some of the bugs and some software changes need to be made so that MI A1 will be a perfect mobile.
..........
Click to expand...
Click to collapse

gsttarun said:
The slo-mo is more like time lapse. It speeds up the rest of the video and plays the selected part at a normal speed.
Click to expand...
Click to collapse
thats what i thought but if you record a video in slo-mo then use something like quickpic to watch it back it really good quality (normal speed) video lol

ya all these r necessary updates!!!

the lastest update fixed the slo-mo for me

Did it really fix it ? I still see the video being fast forwarded like a time lapse video. And why was the update so big for only security patches ?
robgee789 said:
the lastest update fixed the slo-mo for me
Click to expand...
Click to collapse

gsttarun said:
Did it really fix it ? I still see the video being fast forwarded like a time lapse video. And why was the update so big for only security patches ?
Click to expand...
Click to collapse
Definitely fixed for me mate and I think there were a lot of bug fixes which would explain the size but there must a official list of bug fixes somewhere
Sent from my Mi A1 using Tapatalk

Proximity Sensor Issue OP7P

Guys!
Do you experience proximity sensor issues while answering calls on OP7P?
For me while I'm on calls. The display comes on and gets disturbed and get pressed by my ears all the time.
Also any idea of where the proximity sensor is located on OP7P?
Thanks ?

Yes, I'm having the same issues. While I'm on calls I often activate the notifications pulldown. It would be nice to know how to fix this.

If you pull down the notification shade, the sensor is located just above the fifth icon on the first row. IE behind the screen.
If you pull the shade all the way down it is above and between the third and fourth icons. Easiest way to describe it. Put your thumb over that area with auto brightness on to watch the slider move.
Annoying while on a call that the screen comes on.

I'm experiencing the exact same issue with the caller app.
I also tried to make a flip cover to turn screen on or off with a proximity sensor detection app and it didn't work either.
I search a little in engineer mode (*#808#) and found that there is multiple proximity sensor, the IR sensor work quite well but it doesn't seem to be the default one.
The default one seems to be the ultrasonic sensor which works really bad.
There is also a "TP" proximity sensor which seems to be a near field detection which seems to work if I move my hand near the screen.
The sad thing is that in dedicated app to use or test proximity sensor (and in antutu or else) only one proximity sensor is listed (The ultrasonic one I guess) so you cannot switch to use the one which is working well.

Isn't this in the wrong place? Shouldn't it be in the Questions and Answers section?
Mods?

Probably just here looking for a mod to improve the situation

Actually I was going to open a new thread in Q&A when I found this one with the same subject and problem.
Do you think I need to open a new thread?
Is any of you experiencing the same issue as I described in my answer?

did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people

I tried to with no luck but as I explain in my first message the IR sensor is only used when screen is off (that's why it could help with double tap to wake)
But when screen is on another or couple another sensors are used and you can't calibrate them.
I think ultrasonic sensor is used when screen is on.
Do someone tested proximity sensor with any app on the play store? (Like proximity sensor test)
Put it on a table and check if it's working, mine is absolutely not. If I hold it like I was about to phone it works a little but it's not impressive.
Since I got 9.5.7 (EU version) earlier this evening screen turn off when I make a call.

I'm having this issue since 9.5.8... It's very annoying and I'm really disappointed, I often turn on airplane mode during a call... I tried to calibrate but it doesn't work.
I'm very very frustrated

schmeggy929 said:
did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people
Click to expand...
Click to collapse
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8

dallasnights said:
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8
Click to expand...
Click to collapse
This...

I've been having issues with phone calls but more so with pocket issues.. When I had the 6t pocket mode kept the phone neutral but this phone doesn't seem to have an accurate prox sensor.. Is there a way to activate a pocket mode?
Sent from my [device_name] using XDA-Developers Legacy app

Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.

Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out

pinzarualex said:
Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.
Click to expand...
Click to collapse
Let us know if it's going to fix the issue wiping and resetting everything please!!!

Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
But I have had this issue since release.. Do you a link to this information? If that's the case maybe someone can look into the firmware and see if it's minor tweak that can fix it?
Sent from my [device_name] using XDA-Developers Legacy app

Jack_Sparrow_ said:
Let us know if it's going to fix the issue wiping and resetting everything please!!!
Click to expand...
Click to collapse
Of course it didn't fix anything...

Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app

j0hnee said:
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have reported this to Funk wizard on the OOS support thread and he said he cannot reproduce it anymore on the latest test build, so... We have to wait for next firmware release and see if that is indeed the case