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.
Firstly,forgive my poor English.I'm just asking for help.
I have an Android Pad,but it's touchscreen doesn't work correctly.It seems to be all right when I'm clicking or swiping slowly.However,when I'm doing the swiping operation in a relatively fast speed,things go wrong.
The word "wrong" means that at the moment the operation is done and my finger is leaving the touchscreen,the action will have a little "back" or "elastic",which make the swiping operation inertialless.
It's may be hard to describe using words,so I turned on the function that can track the touch actions and draw lines on display which are showing you touches(If you're using Android 4.0 or later version,you can find the toggle of this function easily in "Settings-Developer Options-Pointer Location"),then I took a Screen Capture.
You can see that there are three kinds of colors in a line(blue,red and purple).The tail of purple part is in a different or even opposite direction which I swiped.I doubt that this is the root of the wrong.
Is there anyone knowing the meanings of each color in the line?Who can tell me how to solve this problem?
Resetting or flashing new ROMs are tried but it doesn't work.I don't hope this is a problem of hardware!
Thanks a lot!
View attachment 1241019
tutingheart said:
Firstly,forgive my poor English.I'm just asking for help.
I have an Android Pad,but it's touchscreen doesn't work correctly.It seems to be all right when I'm clicking or swiping slowly.However,when I'm doing the swiping operation in a relatively fast speed,things go wrong.
The word "wrong" means that at the moment the operation is done and my finger is leaving the touchscreen,the action will have a little "back" or "elastic",which make the swiping operation inertialless.
It's may be hard to describe using words,so I turned on the function that can track the touch actions and draw lines on display which are showing you touches(If you're using Android 4.0 or later version,you can find the toggle of this function easily in "Settings-Developer Options-Pointer Location"),then I took a Screen Capture.
You can see that there are three kinds of colors in a line(blue,red and purple).The tail of purple part is in a different or even opposite direction which I swiped.I doubt that this is the root of the wrong.
Is there anyone knowing the meanings of each color in the line?Who can tell me how to solve this problem?
Resetting or flashing new ROMs are tried but it doesn't work.I don't hope this is a problem of hardware!
Thanks a lot!
View attachment 1241019
Click to expand...
Click to collapse
Developers,is there anyone who can answer my question?
Sounds like a hardware fault...
If its under warranty, have it checked...
a.cid said:
Sounds like a hardware fault...
If its under warranty, have it checked...
Click to expand...
Click to collapse
Thank you for you opinion.I just have searched this forum and I quickly found a topic about the "purple line".The poster is using an HTC Flyer and have the same "purple line" problem which caused by a function of Android called "Gesture Prediction Engine".I turn on two toggles in Developer Options now,both"Pointer Location"&"Show Touches",then I find that the touching spot is not influenced by this bug,so now I can be sure that this issue is caused by inoptimized software instead of hardware.
Unluckily,I'm an iPhone Developer,not Android.So I still ask for help.
Hello,
I really hate the pin interface when inputting my pin for Samsung pay on the gear S3 classic, I would really love to have an unlock format similar to how a padlock dial works, where you can turn the bezel to get the right number combination. (like the ones used in high school lockers)
I think this would be an elegant and more efficient solution to something with a round interface like the Samsung smartwatches. As currently fiddling with the small numbers on the dial pad can be tedious.
I'm wondering if an app like this exists or whether its even possible to make.
tl:dr. Rotary dial padlock app with rotating bezel interaction for number input during Samsung pay instead of stock. Possible?
Anyone have problem with face unlock about bad angles or not working under bright sunlight! Just set up face unlock under direct sunlight! make sure sunlight sight direct into your face when setting up. Hope that's helpful, it works for me at least
Ps: if you are wearing glasses, put them on when setup.
My biggest issue with face unlock is random challenge to unlock with PIN for "added security".
I say random because I've not rebooted the phone. The message is different when rebooting. I've sent numerous feedback with logs to Google but Google doesn't respond to feedback. I have no idea why this happens. It's annoying. This can happen as often as once a day at random unless I'm missing the reason for it. Maybe it works for days without error. Maybe this is required at intervals I've not recognized?
Patterns I've noticed otherwise include a pause to unlock when I grab my phone and it's upside down. It usually gives me time to recognize this and get screen upright. My phone is usually on a stand upright in portrait mode so it's rare that I pick it up with screen not orientated correctly.
I've not tried setting up face unlock in bright setting though.
Sent from my Pixel 4 XL using Tapatalk
samep said:
My biggest issue with face unlock is random challenge to unlock with PIN for "added security".
I say random because I've not rebooted the phone. The message is different when rebooting. I've sent numerous feedback with logs to Google but Google doesn't respond to feedback. I have no idea why this happens. It's annoying. This can happen as often as once a day at random unless I'm missing the reason for it. Maybe it works for days without error. Maybe this is required at intervals I've not recognized?
Patterns I've noticed otherwise include a pause to unlock when I grab my phone and it's upside down. It usually gives me time to recognize this and get screen upright. My phone is usually on a stand upright in portrait mode so it's rare that I pick it up with screen not orientated correctly.
I've not tried setting up face unlock in bright setting though.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
your problems is totally different with what I mean to. However, It think your problem could be from software or setting. you would reset your phone. And if that keep going, using google warranty is best choice.
nguaogioi said:
your problems is totally different with what I mean to. However, It think your problem could be from software or setting. you would reset your phone. And if that keep going, using google warranty is best choice.
Click to expand...
Click to collapse
Thanks. I should talk to Google Pixel support again. I've been reluctant since they couldn't resolve an issue with Google Home app. They referred me to Google Home app support but they kept getting stuck on the fact they support hardware, not the app. I could link Google and Philips Hue but couldn't add Philips Hue to Google Home app. Failing every time.
Long story but the mobile apps kept telling me that that there was an issue getting provider information for Philips Hue. Yet it went through all the steps and failed at the end, never adding Philips Hue. This once worked until it stopped; nothing I was doing was working, even asking Google and Philips for support was pointless with them refusing to talk to each other or continue support with me until resolution. One day my phone had a notification to control my lights and the linking and final step worked that time. I followed the notification and seemingly skipped several steps I've went through to failure but this time everything went as expected and I can control my lights again. Finally! What was the issue? Google won't say but I suspect they discovered it long after I gave up. Months!
I've seen face unlock improvements in the notes of the monthly updates so I've thought Google is aware but like before, not on my timetable. Low priority. With my past slate now clean, start a new one.
Sent from my Pixel 4 XL using Tapatalk
samep said:
My biggest issue with face unlock is random challenge to unlock with PIN for "added security".
I say random because I've not rebooted the phone. The message is different when rebooting. I've sent numerous feedback with logs to Google but Google doesn't respond to feedback. I have no idea why this happens. It's annoying. This can happen as often as once a day at random unless I'm missing the reason for it. Maybe it works for days without error. Maybe this is required at intervals I've not recognized?
Patterns I've noticed otherwise include a pause to unlock when I grab my phone and it's upside down. It usually gives me time to recognize this and get screen upright. My phone is usually on a stand upright in portrait mode so it's rare that I pick it up with screen not orientated correctly.
I've not tried setting up face unlock in bright setting though.
Click to expand...
Click to collapse
The issue you explained about the seemingly random pin requirement is actually not an issue at all. It's coded into the software as an extra security measure. If you lock your phone and do not unlock it for XXX amount of time (eg. 1 hour) then the phone requires your pin or pattern to verify its still you and your phone hasn't been physically compromised. The other trigger for this happening is at or around 6 hours since the last time your pin was physically entered, it will require you to enter it for the same reasons I listed before. Using face unlock doesn't reset the 6 hours, only physically entering your pin code will.
Hope this helps you understand a little better what's going on with your phone. We all have the same thing happen to us, just most don't notice it when it happens.
1dopewrx05 said:
The issue you explained about the seemingly random pin requirement is actually not an issue at all. It's coded into the software as an extra security measure. If you lock your phone and do not unlock it for XXX amount of time (eg. 1 hour) then the phone requires your pin or pattern to verify its still you and your phone hasn't been physically compromised. The other trigger for this happening is at or around 6 hours since the last time your pin was physically entered, it will require you to enter it for the same reasons I listed before. Using face unlock doesn't reset the 6 hours, only physically entering your pin code will.
Hope this helps you understand a little better what's going on with your phone. We all have the same thing happen to us, just most don't notice it when it happens.
Click to expand...
Click to collapse
Your hour or six a guess, estimation or actual?
What you described seems true but my use would likely indicate more quiring for PIN than I experience. Just asking.
But if this is intent, I don't agree PIN is added security. Sure face ID can be duped in many ways but at the very least what I'd prefer is safe zone like home where face unlock never dupes to PIN or added security. As I recall, total unlock is only option for designated safe zone like home, unless considering Bluetooth device which I don't prefer unless it can distinguish my Fitbit Versa 2 watch is very near and worn?
Surely there's less invasive methods users can deploy to not be so inconvenienced at home. I've even seen this at work with my wife's iPhone X. More choices seems a logical approach to consider. Why hasn't it?
Phone on charger just now, after just talking to Google Assistant, give a smart home command it interprets correctly, the smart assistant says sure, after you unlock your phone. I dismiss the Google Assistant and promptly unlock my phone without the stupid PIN. Not being very user friendly. I'm under the impression many developers don't just use the device and rethink their intents to be most user friendly.
Sent from my Pixel 4 XL using Tapatalk
I feel like I don't see this message more than twice a week... which certainly goes against the every 6 hours idea. My impression was that sometimes movement or Soli will wake it up and it sees something it thinks is a face but it can't unlock with it. If it sees this enough, it may prompt for a PIN unlock with the different message. But sometimes, I think I see this message taking it out of my pocket... where it can't possibly see a face. But maybe it saw part of my face as I was putting it in. It would be interesting to know what the actual rules are regarding this.
I know that when I have the screen upside down, the screen wakes but gives me time to get it upright. Seconds. I don't recall seeing this fail me, thankfully.
I don't have much or any of the Soli features enabled but have screen tap to wake and skip unlock screen enabled.
I've wondered if having the generic stand was causing random face unlock errors but reach for phone is disabled. And I've tried placing my screen down flat instead of the stand and still got prompts to unlock with PIN.
Sometimes I grab my phone and tap to wake doesn't work. But it doesn't mean I get a prompt for PIN every time either. Yesterday, I tapped on the screen repeatedly and it woke and unlocked when it recognized my face. Maybe it's a latent response but I'm usually using the power button to wake by then.
Sent from my Pixel 4 XL using Tapatalk
So I did a chat with Pixel support today.
For the issues with frequent queries for PIN and Voice Assistant asking me to unlock my phone first, the agent had me delete storage and cache for Google and Phone app, delete face unlock and add it back. Reboot phone and get back with them if this doesn't help.
The agent indicated there's not a timer that cannot be reset with unlock that would naturally challenge for PIN after counting down. His advice is to do the above for that issue. The face unlock is suspect. I hadn't done this until today. For kicks, I tried it outside in daylight though the agent didn't recommend this idea. Fwiw, I can unlock my phone in the dark but maybe daylight helps better see contours of the face.
I have a case number to chat again if this continues. Agent says it shouldn't reoccur.
Sent from my Pixel 4 XL using Tapatalk
I only have a basic understanding of how face unlock works... but from what I understand it uses an IR dot projector and two IR cameras to stereoscopically sense the depth of your face. This is why it works in the dark to begin with and based on this, I would think direct sunlight would be a detriment rather than a boon in this sensing method. But it may not have any effect at all as I don't know exactly how the sun and the dot projector overlap in wavelength and strength.
Having a "bad" face calibration might explain it as the phone is more often unconfident about it being your face. So it triggers more failures which prompts the increased security message.
jljtgr said:
I only have a basic understanding of how face unlock works... but from what I understand it uses an IR dot projector and two IR cameras to stereoscopically sense the depth of your face. This is why it works in the dark to begin with and based on this, I would think direct sunlight would be a detriment rather than a boon in this sensing method. But it may not have any effect at all as I don't know exactly how the sun and the dot projector overlap in wavelength and strength.
Having a "bad" face calibration might explain it as the phone is more often unconfident about it being your face. So it triggers more failures which prompts the increased security message.
Click to expand...
Click to collapse
Agreed. It's unknown if added light is a help, hindrance or placebo. But the agent seemed confident just replacing the face unlock would solve my issues.
Not all of my issues sounded familiar was the reason for suggested extra storage wipes and reboot.
Sent from my Pixel 4 XL using Tapatalk
I spoke from my experience. Before that if i will to unlock i have to keep it direct to my face as the right distance or angles and it hardly work with changing light conditions like under direct sunlight. But after set up with aid from sunlight i could say it work quick and more reliable as my iphone xr even in dark or direct sunlight.
I dont know if that is hardware or software problems.
73 hours of uptime. Random PIN for added security prompt has returned when Google Pixel support said it shouldn't after deleting and adding face unlock.
Taking my case ID back to Pixel support. I'm not sure the agent was right about face unlock not occasionally duping to PIN unlock. Very annoying if this is intended or not.
72 hour bug?
Sent from my Pixel 4 XL using Tapatalk
So my Pixel 4 XL face unlock did the same prompt for pin after another 72 hours. No reboot; no error or explanation why other than added security. I'm at 146 hours uptime.
I asked Pixel support again about this. They're researching but want me to do a factory reset now and get back to them.
Sent from my PH-1 using Tapatalk
Hi Guys,
Long time user of Sonys Compact phones here, so I'm custom to small screens and one hand operation of my phone, i HATE that I have to use two hands, and the manufactors thinks that we all loves big screens..
Ok so I bought a Google Pixel 4a, but for me thats also to big.
I have tried to set the display resolution via adb wm Size function, it works like a sharm, but the phone centeres the display, and google have for some reason removed the overscan function i version11, so I cant set the display to be on the bottom. "damn you google"
I have also tried the Quick cursor app, but its so slow to use all the time.
Then a thought, is there a way to force all apps only to be X pixels high, and fixed at the bottom of the screen? I dont want to ever reach over a certain point of my screen.
Or is there another way to solve my problem?
We are seeing our selfs as a smart race, but creates devices that needs two hands to operate?! jeezzee
PS. No root options wanted.
Kind regards
Morten
May be Android's Split Screen mode is a workaround.
BTW: On ChromeOS, Android apps can be presented in free‑form windows that are arbitrarily resizable