Develop Bugs

Is 14.3.A.0.757 as bug-free and stable as .114?

I’m usually the first to hit the Update button on anything I own, but after reading about all the bugs that Sony introduced with the firmware updates following .114, I chose not to update mine. I’ve been stuck with a permanent notification in my Notification Shade informing me of the update ever since but that is a small price to pay for a relatively bug-free phone.
Now that .757 is released, is it safe to take the plunge? I am in no particular hurry because I cannot think on anything in KitKat that I particularly want and I know that Sony hasn’t fixed my major issues with the phone anyway. I know the camera isn’t any better in low light, the proximity sensor lag remains and the fast dormancy “feature” that drains up to 40% of the phone’s battery every day is still there.
But if it is as stable as .114, I’d like to be on the latest and greatest again. Your opinion is welcome. Thank you.

Android 4.4 has a general bug with the sound (google problem) but apart from that I can't find anything wrong. Battery seems great. In fact I like it better than the 4.3 rom.
Sent from my D5503 using XDA Free mobile app

I did not get any bug yet.. But if u r not rooted then dont upgrade.. Else it will reduce functionality of ur sd card
Sent from my Xperia Z1 Compact (D5503)

coolkoushik07 said:
I did not get any bug yet.. But if u r not rooted then dont upgrade.. Else it will reduce functionality of ur sd card
Sent from my Xperia Z1 Compact (D5503)
Click to expand...
Click to collapse
Oh yes, I was nothing but shocked when I installed KK - I'm mean is this an open source droid or a locked down fruit phone?
Not to forget to mention that email+exchange permissions is changed (for my company mail which uses ms exchange servers).
PIN requirement is not enough on KK, only password with atleast 4 letters, 2 numbers and 3 signs
Takes a week to unlock your phone unless you root and install an old hacked version of email+exchange.apk+the risk of getting sacked (if they would find out).
Only thing I miss from KK is the Stamina icon but the GEL Xperia Xposed dev is looking into porting it :good:

coolkoushik07 said:
Else it will reduce functionality of ur sd card
Click to expand...
Click to collapse
What does this mean?
Sent from my D5503 using Tapatalk

rkelsen said:
What does this mean?
Sent from my D5503 using Tapatalk
Click to expand...
Click to collapse
Other apps cant perform operations in sd card in kitkat without root..
Sent from my Xperia Z1 Compact (D5503)

Thanks for the responses, guys. Are there any new features in KitKat, from either Google or Sony, worth updating for?

Google camera.
Sent from my Nexus 7 using Tapatalk

[SIC] said:
Takes a week to unlock your phone unless you root and install an old hacked version of email+exchange.apk+the risk of getting sacked (if they would find out).
Click to expand...
Click to collapse
There is an Xposed mod: http://repo.xposed.info/module/org.flacid.exchangebypass

i've been in kk using RomAur 3.0 and performs great. No bugs, wifi is more stable (but wiht the same cuts and problems of stock 757 rom) than 114.
Sent from my D5503 using Tapatalk

I considered rooting it but the process seems to be far too convoluted for me to attempt. I'm happy with stock.
Sent from my D5503 using Tapatalk

juried said:
Google camera.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Why do you think it is better than Sony’s Camera app? It does not remove the low light issue (where the camera bumps up the ISO much more than it strictly needs to and makes the photos a grainy, unusable mess) and it does not have a manual mode, so you can tackle it yourself. While I like the sparse interface, I have to stick with Sony’s app, because this phone’s camera is useless without manual mode in low light.
Also, on an unrelated note, can any one of you help me get the Personalised Recognition feature back in Google Now? I used to have it in the settings menu but don’t anymore. It disappeared while I was on .114 and I was hoping that updating to .757 would bring it back, but it hasn’t. Do you guys have it?

Sorry to keep bumping my own thread, but this message is just to help out other users who are thinking of installing this update. My recommendation is: go for it!
I had a long list of annoyances with this phone, but I updated to .757 yesterday and it has fixed almost all the issues I had on .114. The major issues that have been addressed:
The Fast Dormancy bug seems to be gone. That Android process that was eating up 40% of my battery life every day no longer shows up on the battery usage screen.
The proximity sensor delay is gone. You bring the phone away from your ear and the display turns on instantly. Magic!
So far, I have no experienced the keyboard skipping issue, so I hope that is taken care of as well.
The only major issue that remains is that the camera is still terrible in low light, thanks to the software that bumps up the ISO needlessly to insane levels. But I can live with that.
I no longer regret buying this thing.

aryayush said:
Sorry to keep bumping my own thread, but this message is just to help out other users who are thinking of installing this update. My recommendation is: go for it!
I had a long list of annoyances with this phone, but I updated to .757 yesterday and it has fixed almost all the issues I had on .114. The major issues that have been addressed:
The Fast Dormancy bug seems to be gone. That Android process that was eating up 40% of my battery life every day no longer shows up on the battery usage screen.
The proximity sensor delay is gone. You bring the phone away from your ear and the display turns on instantly. Magic!
So far, I have no experienced the keyboard skipping issue, so I hope that is taken care of as well.
The only major issue that remains is that the camera is still terrible in low light, thanks to the software that bumps up the ISO needlessly to insane levels. But I can live with that.
I no longer regret buying this thing.
Click to expand...
Click to collapse
I know it's not really a solution, but keep your cam in manual mode and alter the ISO manually. Every phone I've ever used with a camera (iPhones are particularly bad offenders) ALWAYS overcompensate on the ISO in every single environment other than outside on a bright day.
You'll get spectacular improvements if you just get into the habit of entering manual mode, and altering the ISO to the lowest you can get away with (while keeping all the other options on auto) each time you're taking a photo. As far as Im concerned it's far better that way and produces better results than either superior auto or the iPhone's one-button-capture simplicity.

Thanks. I already do that but the default camera app does not make it easy to change the ISO. It takes at least five taps from within the main camera interface to change the ISO and come back. Often, by the time you are done experimenting with the ISO settings, the subject has moved on. Or you end up with a reasonably well lit but blurry shot because the camera UI makes no attempt to inform you of the shutter speed when you take the shot. I have no found any camera apps on the Play Store that make up for these deficiencies either.

aryayush said:
Thanks. I already do that but the default camera app does not make it easy to change the ISO. It takes at least five taps from within the main camera interface to change the ISO and come back. Often, by the time you are done experimenting with the ISO settings, the subject has moved on. Or you end up with a reasonably well lit but blurry shot because the camera UI makes no attempt to inform you of the shutter speed when you take the shot. I have no found any camera apps on the Play Store that make up for these deficiencies either.
Click to expand...
Click to collapse
Yeah fair enough. Good point.

i have a screen issue. same as a problem the video has been upload to youtube. 10 fingers touch the screen not stable.. also issue is when i draw/sketch on the screen. but only happen some times. on a day happen 10 times or more.
i did flash many kind of custom rom.. but the issue still exist.

shaldi said:
i have a screen issue. same as a problem the video has been upload to youtube. 10 fingers touch the screen not stable.. also issue is when i draw/sketch on the screen. but only happen some times. on a day happen 10 times or more.
i did flash many kind of custom rom.. but the issue still exist.
Click to expand...
Click to collapse
What kind of screen issue do u have??
Sent from my Xperia Z1 Compact (D5503)

Good thing for me that went from .114 directly to .757 (i am rooted also)
Camera app have now a 15Meg option
Transparency
Bad things
Conversations.apk (the SMS/MMS app from Sony) is full of bugs. And when I mean full, I really mean it.
Sometimes messages that i already read in the conversations, disappears. All I would see is the blue bubble showing that there's a message, but without the text of the messages. So far this seems to only affect SMS, not MMS.
The color of the bubble when you type, let say blue, and the color of the bubble of the other person talking to you, let say faded blue, often get switch, so reading a conversation might become difficult.
To get the difficulty level higher in following your conversation, sometimes even the side of the screen your bubble is supposed to be attached switch. I mean here, that when you type, your message is next to right side, and your friends reply is next to left side. But now, sometimes you switch side all of a sudden, or worst, sometimes you're on the same side then your interlocutor. Reading SMS with the conversation.apk is totally hardcore now.
Another thing that really piss be off, but I do not know if this is from 757 or if it was already in 114, since I did not use this app in 114, it is the Email software. The Email software stacks/bundles all the messages with the same subjet title when someone reply or transfer your email. (like Gmail does in a browser by default). I really hate this functionality, I prefer to just scroll down to see the previous message if I need to. Unfortunately for me, there's no option in the app to unstack/ungroup emails messages.
Another problem I have with the Email app, this is a bug, because it wasn't doing this in previous build, it is that the Small yellow icon on the icon that tells you that there's 1,2,3 what ever number unread messages, and also the Mail icon in the notification bar, does not go away upon opening the email message. You need to actually press the back button to exit the new messages for it to be marked as read, so that the icon and the notification bar adjust. So if you open an email messages, press the home button to do whatever else, then look back at your notification bar or email icon, you'll think you got new email message, but in fact, it's the same one that is still marked as unread, even if you did open it and read it...
Email and SMS/MMS apps are what I use the most on my phone, I've been using them since I got my first Xperia X10 Mini Pro that was running 1.6, but I've never had that much trouble, they have so many annoying bugs right now. The only problem I've had was the notification LED bug on my Xperia Mini Pro running ICS.
Another thing that I hate, but this is not from 757, but from JellyBean. I come from ICS, and what I hate the most, is the damn white background of all apps. It use more battery and it hurts my eyes in low light room even with minimum brightness. I just wish a stable CyanogenMod with black background pops like in ICS so that I can install it. I've seen some topic about it over here, but they only explain how to uncompile and recompile, too much complicated, I'd rather simply have a package I could simply install with CWM.
EDIT: Oh yeah, I forgot to mention another bug. Somehow the auto-rotate of the screen stopped working twice in the last 2 weeks. Each time I need to go in the accessibility options and uncheck/recheck the auto-rotate option to fix this. (grrr need to wait 5 minutes to be able to edit my msg #xdaforumantispam)

This phone has an LED-backlit LCD display. It does not affect the phone's battery life whether the screen is white or black. Not enough to make a practical difference, in any case.
Sent from my D5503 using Tapatalk

[Q] Galaxy Nexus Sleep of Death

Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
 The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
 The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
 The problem seems to be irrelevant to the Apps installed.
 The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
 I manually reboot my phone at most every two days.
Solutions tried, but don’t work
 Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
 Turning off the auto-brightness control, as suggested by some post on the Internet.

Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app

Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.

Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.

Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?

Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...

eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.

Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.

I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL

I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.

NVM
Screen still goes dead.
Anyone find an actual fix to this?

isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)

LG G4 Touch Screen issues. Ghost Touches?

I've been able to replicate this issue on my G4 (815T Australian model) on a daily basis, just on the instagram app though.
I recorded a video of it. Slowmo part shows the issue
https://goo.gl/photos/F823e125PQckCPLp6
The screen seems confused and it just scrolls the other way even if my thumb wasn't touching the screen.
Factory data reset did not fix anything.
Are you able to replicate this LG G4 owners?

I don't use Instagram, so can't help with that app, sorry.
But if you go into Developer Options, and turn on "Show touch data", it might help add some more info to the discussion. It will show a trace on the screen of what the phone's touchscreen interpreted from your last tap/swipe.
It would presumably show a swipe up, and then back down, when you're getting these ghost touches that change the scroll direction. But perhaps it could also help show if swipes are interpreted the same way in other apps. It might help you learn a little more about what the phone is seeing, at least.

Thanks for the video and everything but why a new thread? Plenty of videos on the main thread.
Is another thread really necessary?
Sent from my LG-H811 using Tapatalk

Might be, because this only happens with IG. I've got the exact same problem, only with IG and its very annoying.

shook187 said:
Thanks for the video and everything but why a new thread? Plenty of videos on the main thread.
Is another thread really necessary?
Click to expand...
Click to collapse
Apologies, first time I posted it I was thinking it was just Instagram-specific.

KL643 said:
Might be, because this only happens with IG. I've got the exact same problem, only with IG and its very annoying.
Click to expand...
Click to collapse
Ahh good to know I'm not alone on this!

chobie said:
Apologies, first time I posted it I was thinking it was just Instagram-specific.
Click to expand...
Click to collapse
To me it looks like it is IG specific because I don't have this problem with any other app

You can try to change the touch feedback time from short to medium under settings/accessibility/motor & cogination. This will reduce the touch feedback time. Give it a try, and see if it gets better.
Sent from my iPad using Tapatalk

alanchai said:
You can try to change the touch feedback time from short to medium under settings/accessibility/motor & cogination. This will reduce the touch feedback time. Give it a try, and see if it gets better.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Done that but it doesn't solve this problem.

chobie said:
I've been able to replicate this issue on my G4 (815T Australian model) on a daily basis, just on the instagram app though.
I recorded a video of it. Slowmo part shows the issue
https://goo.gl/photos/F823e125PQckCPLp6
The screen seems confused and it just scrolls the other way even if my thumb wasn't touching the screen.
Factory data reset did not fix anything.
Are you able to replicate this LG G4 owners?
Click to expand...
Click to collapse
Question, do you have Google keyboard installed? Because I just removed Google keyboard and installed SwiftKey and it looks like the problem is gone....

KL643 said:
Question, do you have Google keyboard installed? Because I just removed Google keyboard and installed SwiftKey and it looks like the problem is gone....
Click to expand...
Click to collapse
Nope, I use Swiftkey from the beginning. Only LG stock keyboard is installed.

Mm, I've got LG keyboard freezed with TB and after changing from Google keyboard to SK, the problem is gone

KL643 said:
Mm, I've got LG keyboard freezed with TB and after changing from Google keyboard to SK, the problem is gone
Click to expand...
Click to collapse
Interesting. Not keen on rooting though. =\
So you reckon it's just a software issue?

chobie said:
Interesting. Not keen on rooting though. =\
So you reckon it's just a software issue?
Click to expand...
Click to collapse
Well this problem is only related to the LG G4 and IG for me...I don't have any other touchscreen problems with this phone. So for me I guess this is not hardware related. During the day I just had 2 small "ghost touches", way better than before. Will see how it goes the next few days...
Edit :
after a view days, it looks like it didn't solve this issue. Today I notice the ghost touches were there again in IG

Force GPU rendening under Developer options somewhat helped.
The new v10f on my Australian G4 didn't fix the issue as well.

Any updates on this? I had same issue. N this is a replacement unit after 2.5 weeks of waiting
Just day one and this ghost touch come up.

I also have this problem
Did you solve the problem?

I am facing similar issue.between...i am not using ig.

I've had this issue as well (not just IG) and sent the phone back for servicing. It was sent back to me with a report showing that they'd done a few things but the problem is still there. I'd been thinking I'd send it back in once more and ask them to have another look. I'm getting ghost touches everywhere and quite a bit, it's very annoying.
Someone mentioned there was another, large thread about this issue but I can't seem to find it, can anyone point me to it?

Hi, I posted this in a new thread yesterday as I couldn't find anything. Never thought to search for 'ghost taps' duh.
Every now and then when just doing normal things on the my phone it totally freaks out and all by it self it suddenly starts to tap random parts of the desktop, slides the pages, opens apps, closes apps, goes into calculator and a bunch of buttons are pressed randomly. It's almost like someone has hacked my phone and is trolling me by just tapping randomly on the phone.
Just today when looking at Facebook it closed the app, scrolled down notifications, data was turned off and wifi turned on.
I thought it might have been my screeen protector, bit of moisture in it or something. Took that off and still does it. Took out the battery for a minute and still does it.
It happened a few months ago then nothing for ages and now it's started again this weekend.
Thought it might have been only when connected to data but has now done it when offline.
Any one got a solution? Does a custom rom fix?

Unable to make or take calls properly on CM11

Please refer to this post:
http://forum.xda-developers.com/showpost.php?p=62828995&postcount=1432
Has anyone gotten this problem? The person who posted this has been the only one having this problem. This can't be a rare thing, is it? Is everyone just dealing with this issue until it gets fixed?

Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
AnotherContributor said:
One issue though I've been having is that when I'm making and receiving calls, sometimes the phone display goes black and will frankly not come back on. I press the App button and sometimes the display comes on, sends the call to the Status Bar, and the screen goes dark. So, I have to press the Application button again and draw down the menu to hang the call up. When I press the power button, the screen flashes on for maybe a quarter second then goes dark. It keeps doing that every time you press the power button. The worst case scenario that has happened a handful of times is that when I'm in a call, neither the power nor application button are responsive. When that happens, pretty much the only option is to power down the phone and reboot.
...
I'm not sure if I would be able to dial an extension with the way the phone is acting up. I feel like this was not an issue the first couple of weeks I had CM on the phone. Now, it seems to be happening with every call.
Click to expand...
Click to collapse
14th September 2015
samuraix21 said:
Hi, I have this issue. Were you able to fix this issue? You're the ONLY person that has posted this issue so I'm not sure if this is a rare hardware issue or everyone on this forum is somehow dealing with it until a fix comes up.
Click to expand...
Click to collapse
19th September 2015
hawk1500 said:
are people still experiencing the screen off during call problem? I am not talking about when you put it up to your face, but how the screen turns off and won't come back on?
Click to expand...
Click to collapse
20th September 2015
hawk1500 said:
Naw, no screen protector installed. tried the proximity sensor fix app as well as the xposed don't go to sleep during call module but it still does it.
Click to expand...
Click to collapse
20th September 2015
tonochito said:
i think that bugs should be listed more detailed:
front facing camera does not work well, if i want to take a selfie it crash. video camera also does not work equal it will crash. I had to install Google Camera and Open Camera in order to have both selfie and video options working, With Google Camera i take selfies and with Open Camera i record videos, As the guy talking about the scren off in calls is true, i don't have a screen protector and it has this behaivour, also as i mentioned there is kind of lag when i try to dial a number i have to do twice, it doesn't show up right away. The same goes when i am calling for example my carrier and i have to dial on the IVR i have to dial twice in order to get the dial keypad. I didn't have Google play crash.
Another thing that i notice was setting a wallpaper as screensaver does not fit in the middle or correctly i had to use Quick Pic and the option 768x1280 because with the stock gallery wallpapers are like aside of the middle
Click to expand...
Click to collapse

I think this issue needs some attention. I am having this problem as well (with and without screen protector). There are times that I need to enter extensions and codes during calls which has become impossible. I have two of these phones and they both behave this way. I recommend that people start posting screenshots of the app Proximity Sensor Finder which displays different distance numbers detected by the prox sensor. See my screenshot attachment which shows the proximity sensor always detecting a "covered" state of 0.0cm even when nothing is in front of the screen. Everyone should go try this and post their findings.
Other phones on CM11 were able to fix this problem in the past by adjusting the calibration which is unique for each phone, so I started searching around through the Fire Phone CM11 files and I found these:
/system/etc/permissions/android.hardware.sensor.proximity.xml
I could not discern anything of value from this .xml file.
/persist/sensor_calibration/SHCAL_DU20060142640727.csv
This file seemed promising. Its timestamp is back in 2014 so I assume that this comes straight from the original Fire Phone files. If this file is actively used to govern sensor behavior, I'm wondering if perhaps it is not being read correctly. It makes me wonder if there is a log out there somewhere that could shed more light on it. Anyways, you can open up that badboy in any spreadsheet to discover sensor IDs for a bunch of sensors along with calibration coefficients in the form of:
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=550.30
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=395.62
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=19262.26
You'll have to open it and analyze it in context of the other columns and other sensors. I've attached it (re-saved in xlsx format because .csv files are not permitted - if you don't trust my xlsx just retrieve the file from your phone). I highlighted the rows of interest. We could just mess with coefficient values, but without any guidance, it could just be a waste of time. Plus we don't know if this even governs the sensors or if it's just helpful documentation. If anyone has insight about this or even far fetched theories, please comment!
I'm thinking about doing a 'grep' on the entire file tree for some of these key words like SENSOR_ID=SI1143, SI1143, 4CCU1, COEFF0, SENSOR_TYPE=PROX etc etc - to see if any files use any of these terms. It may prove unfruitful due to the amount of compiled software that is no longer in text form. Any thoughts about any of this?

i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number

tonochito said:
i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number
Click to expand...
Click to collapse
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?

jdmillard said:
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?
Click to expand...
Click to collapse
i will give a shot, and post my result

In fact, it would be AWESOME if we could get someone (whose screen does behave perfectly during calls) to post their findings from Proximity Sensor Finder. If their screen works perfectly during calls and this app shows 0.0cm all the time for them too, then we can conclude that this app isn't functioning correctly and we know we need to find our root cause elsewhere.

tonochito said:
i will give a shot, and post my result
Click to expand...
Click to collapse
Available but why it doesn't work right?

tonochito said:
Available but why it doesn't work right?
Click to expand...
Click to collapse
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)

jdmillard said:
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)
Click to expand...
Click to collapse
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero

tonochito said:
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero
Click to expand...
Click to collapse
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?

jdmillard said:
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?
Click to expand...
Click to collapse
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls

I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!

jdmillard said:
I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!
Click to expand...
Click to collapse
your welcome

I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.

KLit75 said:
I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.
Click to expand...
Click to collapse
I was lucky enough to have a good return policy on the glass screen protectors I recently got (for two Fire Phones). I'm returning them today and I've already ordered this as a replacement:
http://www.amazon.com/gp/product/B00WXY18WK?psc=1&redirect=true&ref_=od_aui_detailpages00
It has excellent reviews, decent price, very thin, and it is specifically mentioned many times in the reviews that there is a little cutout for the prox sensor (and you can see if if you look carefully at the pictures). I'm hoping that it will solve my black screen woes and protect my screen. There are reports from folks on these forums saying that there is still some strange behavior during calls (such as your example among others). I personally haven't encountered what you're describing, but I'll keep an eye out to see if I can be of any help.

jdmillard said:
Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
14th September 2015
19th September 2015
20th September 2015
20th September 2015
Click to expand...
Click to collapse
Hi. I like to get back about this since I've been quoted on this.
For me, the glass protector screen that I brought from XtremeGuard was the issue my dad had when he tried to make or take calls. After I removed it, it was back to normal.
The persistent issues now, based on what my dad is telling me, is that sometimes after you dial in a number and call a person, you don't hear the ringing tone to know if it went through or not. My dad would freak out when someone on the other line said something since the ringing tone is not working.

tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
hi
this is usually related to hardware composer.
cheers

superdragonpt said:
hi
this is usually related to hardware composer.
cheers
Click to expand...
Click to collapse
but why? does it matter with the bootloader, i mean i know the CM11 on the Fire phone still on beta with no NFC working and the camera too at least i am using Snap camera and everything works. But making calls is a bit annoying even i don't use the phone to make a lot of calls just for WhatsApp almost all the time

AOD not turning off when phone is in my pocket or when face down

As the title indicates.* Always On Display now never goes off even when it is in my pocket or phone face is down at night.* AOD used to turn off as expected and believe this broke after the September security update.*
AOD remaining on when the phone is in pockets or face down is resulting in increase of battery use. I have unlocked Note 10+ on T-Mobile.
I posted this on Samsung support as well. Can you guys check and confirm if you are seeing the same issue?
Sent from my SM-N975U1 using Tapatalk

I've mentioned on another forum that I'm having this issue as well. I have the Note10+ T-Mobile with the September update. When I first got my phone before the September update, my phone's AOD used to turn off when I close my flip case. I checked this when I first got my phone because I was reading forums and people were saying it didn't work. Then after the September update, I noticed that the AOD will not turn off anymore when I close my flip case or even face down. Now it will just dim when the case is closed but never turn off.
Thanks for posting this on the Samsung forum as well. I hope they get back to you and give us an update to fix this issue.

Mine also is not working. I'm using tap-to-turn-on right now, and prefer it, but just chiming in here.

As a temporary solution you guys could set it to "show on tap", that's how I set mine from the beginning, so AOD is off unless you tap on it, or set it active during certain hours. If it was working and no more, probably bug in the update, what else is new, yawn.

Pinan said:
Mine also is not working. I'm using tap-to-turn-on right now, and prefer it, but just chiming in here.
Click to expand...
Click to collapse
pete4k said:
As a temporary solution you guys could set it to "show on tap", that's how I set mine from the beginning, so AOD is off unless you tap on it, or set it active during certain hours. If it was working and no more, probably bug in the update, what else is new, yawn.
Click to expand...
Click to collapse
Kind of disappointing. Pay $1,100 for a phone to only be forced to use it half ass LOL.
Sent from my SM-N975U1 using Tapatalk

Lepa79 said:
Kind of disappointing. Pay $1,100 for a phone to only be forced to use it half ass LOL.
Click to expand...
Click to collapse
This is not likely to ever change. Every new (rushed to market) device has issues. They'll fix it. I actually prefer the tap-on method now.
It is what it is.

If my phone is inside my pocket, I need to take it out and hold in my hand, same at night when sleeping, phone is laying down on night table, I need to pick it up to see the screen. If tapping the screen to activate AOD, when holding the phone in your hand is such a problem, I really would hate to see the drama, when real problems appear, like when you get a message or miss call and there is no notification light etc. LOL.

It's actually worse than just AOD not turning off because after the Sep update the proximity sensor doesn't work except when making a phone call. If I get a text message or email and my phone is in my pocket then the phone display turns on. At a minimum it's bad because the device wastes power turning on in the pocket, but depending what's on the screen it can also inadvertently clear notifications, open apps make a call all by accident. Needs a fix from Samsung ASAP.

sansnil said:
It's actually worse than just AOD not turning off because after the Sep update the proximity sensor doesn't work except when making a phone call. If I get a text message or email and my phone is in my pocket then the phone display turns on. At a minimum it's bad because the device wastes power turning on in the pocket, but depending what's on the screen it can also inadvertently clear notifications, open apps make a call all by accident. Needs a fix from Samsung ASAP.
Click to expand...
Click to collapse
It makes sense the problem is with the sensor post the security update since AOD depends on the sensor to turn off in pockets and when face down. Really crappy this gotten broken [emoji17]
Sent from my SM-N975U1 using Tapatalk