Develop Bugs

[Q] Caller ID Contact Picture -

Hey there,
Was wondering if this was a common thing or just my set-up.
When one of my contacts call and I have set a Pic for them to show when they call, not the whole pic shows. It cuts off the top portion and it is not the full pic that I cropped when I assigned this to that contact.
I have checked my settings and not sure if I am looking in the right place.
Can someone please chime in and let me know if this also happens to them or if it is something I am doing wrong.
I had the M7 before this and it did show full screen.
Thanks

So i guess noone else is having this same problem??
henry1970 said:
Hey there,
Was wondering if this was a common thing or just my set-up.
When one of my contacts call and I have set a Pic for them to show when they call, not the whole pic shows. It cuts off the top portion and it is not the full pic that I cropped when I assigned this to that contact.
I have checked my settings and not sure if I am looking in the right place.
Can someone please chime in and let me know if this also happens to them or if it is something I am doing wrong.
I had the M7 before this and it did show full screen.
Thanks
Click to expand...
Click to collapse

Wow So I'm assuming no one else is having this problem.....
400 something views and noone can comment...
Was it something I said??
:crying::crying::crying:

It does that for me too. I assume that it's by design.

danguyf said:
It does that for me too. I assume that it's by design.
Click to expand...
Click to collapse
Well Thank You very much for taking the time to chime in...

After a 1 week with Moto 360

I received my beautiful Moto360 a week ago,since then I loved it.
I'm less like to use my phone outside,of course I'll make calls from it I can read all of my mails,whatsapp messages, calendar events. It's very very usefull and fast. At the beginning, I don't think this watches can help me at my normal life,but it seems that it's helping a lot. I really don't have to use phone for small things, watch vibrates gently and you can read notifications anytime
Also I don't have any battery problems with it, my phone and watch ( always on mode off because it's useless) can survive a full day with 3g connection. That's enough for me, I don't have any screen problems,screen looks gorgeous. I dont notice any crack yet but I dont think there will be any watch seems ok and I just saw survey about cracks and it's low rate ( thankfully)
I'm open to any question about this awesome watch.

Hi, can you reply to notification from whatsapp message directly from the Moto 360 ?

zhix said:
Hi, can you reply to notification from whatsapp message directly from the Moto 360 ?
Click to expand...
Click to collapse
You can reply with preload answers like "yes", "no", "I'm on the way". Or you can reply with your voice

With which phone you use it? Is it possible to use with every device(or at least every with 4.x + Android)?
Does it feel as good as it looks?^^

AndroidPaul said:
You can reply with preload answers like "yes", "no", "I'm on the way". Or you can reply with your voice
Click to expand...
Click to collapse
Just to add on, to reply with pre-loaded answers you'll need to swipe up from the voice screen. It took me a while to figure that out. Hope this helps.

papa_Lutz said:
With which phone you use it? Is it possible to use with every device(or at least every with 4.x + Android)?
Does it feel as good as it looks?^^
Click to expand...
Click to collapse
At least Android 4.3+ is required.

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

Help! Ambient mode seems to freeze watch.

Have had the Huawei Watch for a few days and it seems to have a deal-breaking bug. Frequently, after the watch has been in ambient mode for a while, it won't come out of it. If I touch the screen, the ambient display gets brighter, but that's all. No response from swiping or button presses. Sometimes, after a very long pause (a minute or so) it'll come back to life, but usually I have to hold the button until it restarts. Anyone run into this before? Ideas? Any help is greatly appreciated.
Using it with a Nexus 6. Android wear version 1.3.0.2176821.
Thanks!!!
Sent from my Nexus 6 using XDA Free mobile app

Forgot to mention that the time sticks at whatever time it freezes and so it doesn't even tell the correct time. Sigh.
Have tried a factory reset. Didn't fix it.

Sounds like it's maybe in need of replacing. Like any new product release, there's bound to be a certain percentage of failures. Depending on how you look at it, you're either really lucky, or really unlucky

Well, just in case anyone else encounters this issue, I called Huawei tech support and described my issue. After a few minutes, they came back and said it was a known issue that effects some but not all watches. They said it would be corrected in a future software update but he was unable to tell me when that would be. So I could either wait for that update or send it back for an exchange. Since it happens frequently and renders the watch temporarily unusable, I opted to exchange it. They send an RMA label next day. The joys of new tech. Hope this helps someone else.

gyromiterob said:
Well, just in case anyone else encounters this issue, I called Huawei tech support and described my issue. After a few minutes, they came back and said it was a known issue that effects some but not all watches. They said it would be corrected in a future software update but he was unable to tell me when that would be. So I could either wait for that update or send it back for an exchange. Since it happens frequently and renders the watch temporarily unusable, I opted to exchange it. They send an RMA label next day. The joys of new tech. Hope this helps someone else.
Click to expand...
Click to collapse
I have absolutely same issue. In ambient mode it freezes from the first day I bought this watch. Thank you for investigation and info.

got my hwatch and experienced the ambient mode freeze. to unfreeze, i enter and exit theater mode. it works. but now i'm never sure if the ambient time i'm glancing at is accurate or not...

Similar problem with an HTC M8. I'll try the theater mode to see if that helps. I still can't trust the time any more.

+1 on the Huawei Watch freeze. Sometimes after 15 minutes, sometimes after several hours. It has frozen with ambient mode disabled and with wrist gestures disabled as well.
Sent from my LG-V500 using Tapatalk

Two watches and no freezes here. Are you guys testing with no Wear apps installed and with a built-in Huawei face?

brizey said:
Two watches and no freezes here. Are you guys testing with no Wear apps installed and with a built-in Huawei face?
Click to expand...
Click to collapse
Yes, after factory reset with no additional apps and with original buil-in Huawei faces and used to freeze. I returned it to the shop, got new one and problem is fixed.

lukhof said:
Yes, after factory reset with no additional apps and with original buil-in Huawei faces and used to freeze. I returned it to the shop, got new one and problem is fixed.
Click to expand...
Click to collapse
Good to hear you got it fixed!

how are you sure that the problem is fixed as opposed to it not showing yet? the freeze seems to be random and i don't know of a way to replicate it on demand. thanks

maximus96 said:
how are you sure that the problem is fixed as opposed to it not showing yet? the freeze seems to be random and i don't know of a way to replicate it on demand. thanks
Click to expand...
Click to collapse
Before it froze every day several times. Now i have new one and it has been running non-stop for one week with ambient mode on and no freeze at all.

lukhof said:
Before it froze every day several times. Now i have new one and it has been running non-stop for one week with ambient mode on and no freeze at all.
Click to expand...
Click to collapse
thanks, good to know. i'm curious if your replacement watch has the red-tint issue. i wonder if the two are somehow related.

maximus96 said:
thanks, good to know. i'm curious if your replacement watch has the red-tint issue. i wonder if the two are somehow related.
Click to expand...
Click to collapse
None of them had red-tint issue. It seems this is not related with the freezing ambient mode.

Thanks, that solve my problem as well.

Happening to me too. Was using 3rd party skymaster watch face.

Got a replacement from amazon and it hasn't froze yet in the past two days of using it. The last one froze several times a day