Hello Community, this is my first time posting but I have used this site to answer all of my other android questions so I know this is the right place. I have spent three days now on this 'issue' and still I have found no resolve.
My Mother bought a MyTouch 3G Slide the other week and she has very poor vision. The best solution I found for her was to change the DPI on the phone to make EVERYTHING big. This seemed like a good solution except the Phone.apk / in call dial-pad is off the visible screen. I am not looking to fix the dialer there are numerous apps that will put that in the visible area, it is just that in call dial-pad, and since my Mother actually used a phone to make calls this is an issue to her.
The only way I can think of to fix this is to make a custom phone.apk for small screens, if anyone can help me do this, or has a better idea please share and THANKS in advance.
Technical Info: Default DPI=160; Custom DPI=220.
This make the 3.4inch diagonal screen into a virtual 2.6inch one.
Screen Shot of the Issue (Phone.apk does not work to show in-call dial-pad due to me trying alternative ones atm but dialer illustrates the issue.)
i46.photobucket.com/albums/f116/shadowck5000/screenshot_4.png -cant link yet sorry
Please if anyone has any idea I would really like to get this done as soon as possible.
Ok by accident today I fount a possible alternative. When the phone dialer is displayed even though it is out of proportion when I click on the area where numbers being dialed are displayed a soft keyboard with 0-9 is displayed.
However the Phone is a myTouch Slide, with a physical keyboard so holding the menu button will not bring up a soft keyboard. Is there a way to bring one up in calls even though a phone has a physical one? Also the physical keyboard is not a option for my mom when she would be in a call with someone and need to dial a button.
So now lets talk real world experience of the phone interface
When it blanks the phone buttons seem to operate...
I mean a number of occasions I have lost people because I have mysteriously put them on hold...with the phone to my ear.
People are always complaining to me that I am quiet even though the phone is in the correct place on my face and incall volume is at max
Often I cannot pick up calls ...I hit the answer icon to no avail...if I flick it upscreen it works but pressing the icon is only recognised intermittently
What is it like for you?
PianoSam said:
So now lets talk real world experience of the phone interface
When it blanks the phone buttons seem to operate...
I mean a number of occasions I have lost people because I have mysteriously put them on hold...with the phone to my ear.
People are always complaining to me that I am quiet even though the phone is in the correct place on my face and incall volume is at max
Often I cannot pick up calls ...I hit the answer icon to no avail...if I flick it upscreen it works but pressing the icon is only recognised intermittently
What is it like for you?
Click to expand...
Click to collapse
have to tried to factory data reset the phone to see if that helps?
This is called the incall/proximity sensor issue and the reasons have not yet been found by xda people.
There are few fixing attempts available though which involve different strategies.
Someone lately suggested to the ViperOne team to make a tweak that allows for automatically locking the phone on call pick up as a permanent workaround fix. There was no developer response on this yet though. Its a good idea though.
The same sensor is causing another issue which is quite frustrating. On some occasions the normal method of simulated battery pull (press power for more than 15 seconds to force reboot) does not do anything unless shining a really bright light into the sensor. Apparently the prox sensor, not the light sensor.
It seems there are a few units out there which have issues with this sensor.
Another theory is that its jut the user tilting the phone until it recognizes landscape orientation and then the sensor is switched off...
I'm kinda old fashioned but I still use an HTC Desire with the original ROM (and living and suffering with its issues) and couldn't move myself to flash it with a custom ROM, because they all seem not to fit my needs. It may sound weird, but here is my thinking about the Android UI development:
Back than, when I bought my Desire it was the best Device of its class out there. The Sense UI was way better than the native Android (which was really ugly) and very comfortable. Since then Android developed to Holo, Sense made several big and weird changes up to the latest one on the M8 and TouchWiz I never liked; and I still think the old Desire Sense UI is one of the best out there. The main reasons for that seem a bit ridiculous but are a major usability issue for me:
Unlock with a slide to the bottom
While receiving a call, slide to the bottom to accept, slide to the top to decline
Two separate lock screens, one as keyboard lock and one as security lock (with password or pattern) that only activates after a set amount of time (not like the Samsung devices where you have to enter your pattern EVERY time you turned off your display)
Why on new devices it is common that I have to slide to the side to unlock? Sliding to the bottom is the most comfortable movement you can do with your thumb without any danger to let your phone slip and hit the ground. So why it is so absolutely uncommon? And why on native Android you can't move the unlock option to the bottom, where is plenty of space and would also give you the opportunity for a fifth quick access app? In my point of view it would increase usability a lot.
While receiving a call on new phones you have to press a virtual button, but why? With old phones you could feel the right button to accept or decline a call, but with touchscreens you have to look at it first and then touch precisely. But there is no need for that. Even the pressing and sliding the green or red circles is based on hitting the screen on a special area, which is kinda unpleasant for me. With the old Sense you only have to roughly slide up or down from around the middle of the screen, so declining a call without taking the phone out of your pocket works like a charm.
At last the lock screen. I always had to decide between the normal keyboard lock and a pattern (password was never an option) but never get it to work with having the pros of both. I understand that some may find it stupid to have two lock screens, but for me they have different functions and so they work very well together in my workflow. On Cyanogenmod I found an option that seems to give me what I want, but it never worked like my Desire.
Yeah, even when I still use my Desire I have used other phones too (in parallel for work) and I really always missed the listed options of the old Sense UI and hated the strange design decisions made since then. But am I the only one who thinks about that in that particular way or is it me who is too picky? Is there no one else out there thinking the Desire Sense UI was outstanding at that time and still is today? Or is there an app for that I haven't found yet?
Just my two cents.
Hi all,
I am using a Moto G4 on android 7.0. I personally find the default android swipe from the centre to answer icon un-intuitive and difficult for answering the phone from the lock screen . I would much rather have an accept / decline button . I have tried a few of the incoming call screen apps which feature accept/decline buttons but am finding that in all cases ( so far) the decline button works but the accept button does not - it is odd that this is applying across multiple apps and suggests that it is soething within the OS that is causing the issue . Has anyone else noticed this or found a resolution ?
Slight off the topic but there is of course an accept / decline option ( a headsup I think ?) if the phone is already unlocked but I find it too insignificant to always notice and in any case results in a totally inconsistent experience when answering calls (one way from the lock screen - a different way otherwise ). I understand the headsup is so as to not take over the phone if somebody is otherwise engaged but for me the primary purpose of the phone is to be a phone i.e make and receive calls , then perhaps SMS and only then other apps.
So, what the title says, I just downloaded it from xpirifirm and Installed it using flashtool, am hoping to fix the problem with voice messages from WhatsApp and messenger as well (basically 1 in 10 voice messages I send go silent in the middle of the recording), there is not a changelog from Sony but they never give any so I hope this could be more than just a security patch, I want to know if any of you have installed it and if you have noticed any fix, thanks, If I find out something I will tell you. Thanks for reading.
Well, sadly I couldn't fix the issue with the voice notes, but I disabled the "ok Google" feature from the Google assistant and I haven't had any problem with voicenotes anymore, let's see if it stays like that.
It didnt solved the problem, I plan to go back to android 9
Does not feel any fix, but so frustrating 'couse battery capability is much much worse...
I think the fingerprint at least is faster and more reliable.
ferluna18 said:
So, what the title says, I just downloaded it from xpirifirm and Installed it using flashtool, am hoping to fix the problem with voice messages from WhatsApp and messenger as well (basically 1 in 10 voice messages I send go silent in the middle of the recording), there is not a changelog from Sony but they never give any so I hope this could be more than just a security patch, I want to know if any of you have installed it and if you have noticed any fix, thanks, If I find out something I will tell you. Thanks for reading.
Click to expand...
Click to collapse
I fixed the voice messages disabling the feedback tactile of 3 under screen buttons
Did the upgrade change your GPS functionality? Since the day I updated, my phone started drifting. I have 25 kilometers displacement on a day staying permanently at my home office. Compared to 0.5 kilometers before the update.
I didn't understand how you fixed the voice messages, can you be more specific?
Hey guys, it's July 9th and the last firmware released for xperia xz2 is 52.1.A.2.1, will Sony stop supporting this device or what? Btw my cellphone has now a ghost touch.
ferluna18 said:
Btw my cellphone has now a ghost touch.
Click to expand...
Click to collapse
Same for me! Just about a week or so, I am annoyed by the quick settings bar being occasionally pulled from top while typing on the keyboard or working in apps. With the "Show taps" option turned on from the developer settings, I can clearly see that the device sometimes detects an extra tap (draws the corresponding circle) at the very top of the screen right after I tap somewhere else. This activates the system bar and switches the focus from the app. This only happened before with the screen very dirty or wet (i.e. in the rain). However, this time cleaning it and rebooting the system didn't help. My initial idea was that I could have damaged the screen sensors or other hardware somehow. But this might be instead a planned action to support the upcoming models' sales Interestingly, there was no software update accompanying the behaviour change — seems like there are some remotely controlled sensor options their engineers could be playing around.
sersel2 said:
Same for me! Just about a week or so, I am annoyed by the quick settings bar being occasionally pulled from top while typing on the keyboard or working in apps. With the "Show taps" option turned on from the developer settings, I can clearly see that the device sometimes detects an extra tap (draws the corresponding circle) at the very top of the screen right after I tap somewhere else. This activates the system bar and switches the focus from the app. This only happened before with the screen very dirty or wet (i.e. in the rain). However, this time cleaning it and rebooting the system didn't help. My initial idea was that I could have damaged the screen sensors or other hardware somehow. But this might be instead a planned action to support the upcoming models' sales Interestingly, there was no software update accompanying the behaviour change — seems like there are some remotely controlled sensor options their engineers could be playing around.
Click to expand...
Click to collapse
Thanks for sharing your experience, well I still have the ghost touch but now occurs more often and I have had another issue since some months ago ad well and tje thing is that sometimes the proximity sensor "detects" it's being covered and makes the screen flash several times during a call or hearing voice notes in whatsap, sometimes the failure is as bad that I have to restart the phone, I don't know what could be causing this problem but I have to say that I have dropped some water in my cellphone in the past two or three times, and I don't know, maybe some of this water came into the phone through the earpiece and messed with the upper part of the screen and the other sensor up there, my phone os almost a year old now, Do you guys think it might mot be water resistant anymore? And btw, have you dropped water in the phone as well? Thanks for reading.