Hi,
I wish I had the knowledge to create such an application, but I don't so I'll try to explain this idea as clearly as I can see if someone finds it interesting enough.
As you know some phones already have the built-in feature to turn OFF the screen when a call is established. This prevents accidental actions with your cheek and ear on the touchscreen.
Some phones have fancy sensors like light sensor and proximity sensor.
But many other phones don't have, so this tiny app would be very useful to all of them:
How should it work?
Very simple:
1. Detect when a call is established
2. Call the "Turn OFF screen" command (same as pressing the power button)
That's it.
This would be exactly like pressing the power button after call is connected, so there wouldn't be incompatibilities with other apps. Plus the phone behavior when call is finished would be the same as always, since it only called the same command as power button.
This tiny app then could be cooked inside many ROM's.
Well, it's very easy explained like this, but as I said, I don't have the knowledge to do it myself
If you feel like programming the app I will gladly be your tester (or should I say guinea pig? )
+1
Having the problem with accidental touching the buttons and so fort pausing or hanging up a established Call.
+1
Add the functionality of turning the screen back on after the call is dis-connected and I'm sold
A software like this would be manufacturer dependant. For HTC devices, check out Touch InCall Screen Tweak. This app works on all HTC devices, and is a great app.
You can also use DiamondTweak or Advanced Config and setup the device to suspend quickly when in call (but these apps might only work on Diamond).
longice said:
A software like this would be manufacturer dependant. For HTC devices, check out Touch InCall Screen Tweak. This app works on all HTC devices, and is a great app.
You can also use DiamondTweak or Advanced Config and setup the device to suspend quickly when in call (but these apps might only work on Diamond).
Click to expand...
Click to collapse
Thank you!
Although I have an Elf, and it's got no G-sensor and no light sensor, so it won't work on my device
But it's pretty close to what I'm looking for! Thanks!
Is there really no way to disable the "Green" "Home" "Left arrow" and "Red" button when I'm in a call.
Ive tried to disable the buttons with AEB-plus, but it still doesn't work while Im in a Call.
Is it just me that have the problem with time and time Pausing or Hanging up established calls, "thanks" to the "Hardware" buttons.
PS
Using Touch HD
My last phone before this one is the Droid Mini. So far the Z5C is infinitely better in everything (but my expectations/standards are pretty low...) except that the Active Display feature from Motorola was awesome. From a bit of Googling, there are some other apps that copy this functionality to various degrees, but maybe some of you can give more specific insight than the articles?
1.) First of all, I'm confused. This article below states that Motorola released the app on Google Play Store for the general Android population... but it doesn't come up when I search it on my Z5C. What the hell?
http://gadgetstouse.com/featured/to...lay-notifications-alerts-android-device/19901
2.) If the Moto app is not available, any opinions on the alternatives? From reading a few articles, sounds like Dynamic Notifications is my best bet. Thoughts?
I tried xposed module, but it used proximity sensor, so it is not the same thing. I also miss that feature a lot from my nexus 5x, double tap to wake is kind of replacement when phone is laying on the table. When you take it out from a pocket, pressing the button isn't such a big deal. I couldn't find any reasonable replacement so I learnt to live without it
I really don't understand why other manufacturers don't copy-cat this feature. It was without question the greatest feature of my old phone.
I tried out Dynamic Notifications, but it's weird. First, it didn't play nice with the existing lock-screen and login structure. When I had a notification, pressing the power button no longer took me to the lock screen -- instead it just turned off and locked the screen. It's as if Dynamic Notifications became a second lock screen, and the power button toggled it on/off, and I had to tap the home key to get to the actual lock screen. On top of that, after getting to the actual lock screen it seemed to somehow screw up the fingerprint login because I kept getting prompted to use my other login method (PIN in my case). Most weird of all, it had some crazy bug when I used Uber. I was trying to check where the Uber car was on the map, and it threw me to the Dynamic Notifications screen, with the Uber notification showing. I logged in again, pulled up Uber again, checked the location of the Uber on the map, and it instantly did it again! And again... So screwed up.
TL;DR: Do not use this app, at least not on this phone. It's buggy and/or just makes you jump through extra hoops when logging in.
Yeah I also have double tap enabled. It's okay I guess.
Nexus 5x had a dedicated hardware sensors for that matter, I guess that may be the problem. Anyway I agree with you that every manufacturer should implement it.
I would try AcDisplay for the lock screen and if you want raise to wake, try Gravity Screen . Be warned though, Gravity Screen is kind of glitchy with the fingerprint sensor, so I would just use AcDisplay. ^_^
dlee390 said:
I would try AcDisplay for the lock screen and if you want raise to wake, try Gravity Screen . Be warned though, Gravity Screen is kind of glitchy with the fingerprint sensor, so I would just use AcDisplay. ^_^
Click to expand...
Click to collapse
try use ambient display is an xposed module
dlee390 said:
I would try AcDisplay for the lock screen and if you want raise to wake, try Gravity Screen . Be warned though, Gravity Screen is kind of glitchy with the fingerprint sensor, so I would just use AcDisplay. ^_^
Click to expand...
Click to collapse
So I finally got around to trying out AcDisplay. That video that is on the app download page shows how you can wake up the phone using proximity sensors, when pulling it out of your pocket or even waving your hand over it... But none of this works at all. Not even a little bit. Does that mean that the Z5C does not have any proximity sensors built into it?
I'm new to greenify, so bear with me.
In the pro version, I enabled both shallow hibernation and aggressive doze, in addition to adding a number of apps manually.
However, I found that the proximity sensor became a bit wonky, waking the screen while still in a call, and occasionally failing to wake the screen on call end.
Is it possible that greenify is causing this, and if so, what would you suggest I change to fix it?
HTC 10 rooted, Xposed, Maximus HD (MM)
Sent from my HTC 10 using Tapatalk
BillTheCat said:
I'm new to greenify, so bear with me.
In the pro version, I enabled both shallow hibernation and aggressive doze, in addition to adding a number of apps manually.
However, I found that the proximity sensor became a bit wonky, waking the screen while still in a call, and occasionally failing to wake the screen on call end.
Is it possible that greenify is causing this, and if so, what would you suggest I change to fix it?
HTC 10 rooted, Xposed, Maximus HD (MM)
Click to expand...
Click to collapse
Absolutely! Disable aggressive doze and shallow hibernation as they generally offer no significant benefit on Android 6 (Marshmallow) and often trigger side effects similar to what you describe. I'd also remove ALL apps from Greenify's hibernation list unless they exhibit undesirable behavior.
Given MM based ROM be sure to enable 'Doze on the Go' in Greenify settings which will help your device enter doze more rapidly and remain there longer even when in motion.
Davey126 said:
Absolutely! Disable aggressive doze and shallow hibernation as they generally offer no significant benefit on Android 6 (Marshmallow) and often trigger side effects similar to what you describe. I'd also remove ALL apps from Greenify's hibernation list unless they exhibit undesirable behavior.
Given MM based ROM be sure to enable 'Doze on the Go' in Greenify settings which will help your device enter doze more rapidly and remain there longer even when in motion.
Click to expand...
Click to collapse
Done. Would you suggest a battery app to monitor wake locks, and if so, which one?
Also, a general question about lithium batteries should not be trickle-charged overnight, or left plugged in constantly because it stresses the battery. Just wondering if there's any truth to that, or if it's an urban legend.
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Done. Would you suggest a battery app to monitor wake locks, and if so, which one?
Also, a general question about lithium batteries should not be trickle-charged overnight, or left plugged in constantly because it stresses the battery. Just wondering if there's any truth to that, or if it's an urban legend.
Click to expand...
Click to collapse
Not a fan of monitoring wakelocks which are broadly misunderstood and usually not the source of excess (operative word) battery drain. Android's native monitoring tools are generally adequate. Two well regarded alternatives are Better Battery Stats (BBS) and GSAM. Both can be found in the Play Store.
Leaving a Li-ion powered device on charge overnight is fine. Especially phones and other portable gizmos which are usually discharged the following day. However, Li-ion batteries should not be left in a fully charged or discharged state for an extended period as irrevocable damage can occur. That's why most Li-ion powered devices arrive partially charged which is the state they like best.
More detail: http://batteryuniversity.com
Davey126 said:
Not a fan of monitoring wakelocks which are broadly misunderstood and usually not the source of excess (operative word) battery drain. Android's native monitoring tools are generally adequate. Two well regarded alternatives are Better Battery Stats (BBS) and GSAM. Both can be found in the Play Store.
Leaving a Li-ion powered device on charge overnight is fine. Especially phones and other portable gizmos which are usually discharged the following day. However, Li-ion batteries should not be left in a fully charged or discharged state for an extended period as irrevocable damage can occur. That's why most Li-ion powered devices arrive partially charged which is the state they like best.
More detail: http://batteryuniversity.com
Click to expand...
Click to collapse
Thanks for that info. Very interesting site, but way above my pay grade. I guess by "extended period" that scenario would be a store demo unit that's constantly powered, or a home scenario of similar sort.
Here's what I took away from a brief overview, if anyone else is looking on:
(Sourced from 'How to Prolong Lithium Based Batteries' from Battery University)
From: Battery University:(emphasis mine)
Similar to a mechanical device that wears out faster with heavy use, the depth of discharge (DoD) determines the cycle count of the battery. The smaller the discharge (low DoD), the longer the battery will last. If at all possible, avoid full discharges and charge the battery more often between uses. Partial discharge on Li-ion is fine. There is no memory and the battery does not need periodic full discharge cycles to prolong life.
Environmental conditions, not cycling alone, govern the longevity of lithium-ion batteries. The worst situation is keeping a fully charged battery at elevated temperatures. [I'm reading this as a warning for those of us with quick charging cables]
The question is asked, “Should I disconnect my laptop from the power grid when not in use?” Under normal circumstances this should not be necessary because charging stops when the Li-ion battery is full. A topping charge is only applied when the battery voltage drops to a certain level. Most users do not remove the AC power, and this practice is safe.
Click to expand...
Click to collapse
Davey126 said:
Absolutely! Disable aggressive doze and shallow hibernation as they generally offer no significant benefit on Android 6 (Marshmallow) and often trigger side effects similar to what you describe. I'd also remove ALL apps from Greenify's hibernation list unless they exhibit undesirable behavior.
Given MM based ROM be sure to enable 'Doze on the Go' in Greenify settings which will help your device enter doze more rapidly and remain there longer even when in motion.
Click to expand...
Click to collapse
Still having some trouble from time to time with proximity sensor, screen wake (almost locks on or off) and fingerprint sensor when waking.
I wiped both dalvik/art and system cache which seemed to help for a bit and also seemed to make the phone a bit more responsive, but this afternoon, the above problems resurfaced.
Can you please recommend some settings to start with, since I'm a noob with greenify, and I'm not sure if I have everything set right. Also might app updates without a reboot have something to do with this?
HTC10
Maximus HD (MM)
Rooted (obviously)
Xposed
Thanks in advance!
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Still having some trouble from time to time with proximity sensor, screen wake (almost locks on or off) and fingerprint sensor when waking.
I wiped both dalvik/art and system cache which seemed to help for a bit and also seemed to make the phone a bit more responsive, but this afternoon, the above problems resurfaced.
Can you please recommend some settings to start with, since I'm a noob with greenify, and I'm not sure if I have everything set right. Also might app updates without a reboot have something to do with this?
HTC10
Maximus HD (MM)
Rooted (obviously)
Xposed
Click to expand...
Click to collapse
With Aggressive and Shallow doze disabled the only other setting that might prove troublesome is 'doze on the go'. However, that one is important on MM as it prevents your device from waking and/or staying awake when in motion. Still, might be worth disabling to see if it makes a difference.
Rebooting after app updates is generally unnecessary unless recommended by the developer.
Additional thoughts:
- verify working mode is Root + Boost (Xposed)
- keep the list of apps to explicitly Greenify short (demonstrated bad actors); implicit doze will take care of the rest
While my preference leans towards Greenify (ease of use; flexibility; long term track record; community support) there are several other fine apps with similar functionality. Force Doze pops to the top of the list. Occationally a user will report issues with one while the other works fine. Another option to consider.
BillTheCat said:
Still having some trouble from time to time with proximity sensor, screen wake (almost locks on or off) and fingerprint sensor when waking.
I wiped both dalvik/art and system cache which seemed to help for a bit and also seemed to make the phone a bit more responsive, but this afternoon, the above problems resurfaced.
Can you please recommend some settings to start with, since I'm a noob with greenify, and I'm not sure if I have everything set right. Also might app updates without a reboot have something to do with this?
HTC10
Maximus HD (MM)
Rooted (obviously)
Xposed
Thanks in advance!
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
If you have greenified any system apps, please reconsider. One of them may be the culprit.
If nothing else works, ungreenify everything and start from scratch. Greenify one app at a time, observing the behavior for some time before greenifying the next. You may find the culprit. Laborious, but effective.
Davey126 said:
With Aggressive and Shallow doze disabled the only other setting that might prove troublesome is 'doze on the go'...
Click to expand...
Click to collapse
tnsmani said:
If you have greenified any system apps, please reconsider. One of them may be the culprit...
Click to expand...
Click to collapse
Hey, guys. I'm still having trouble with both the proximity sensor and fingerprint sensor. Could really use some expert advice here.
The phone screen often does not come back on - especially during a long call or when switching between calls, and frequently just "loses its mind" and I have to press the power button to get the screen back, or even to turn the phone off. Another problem is waking via the fingerprint sensor which is unreliable.
I don't know if it's the settings I've selected (my money is on this one) or if there's a rogue app that's hosing me. For example, I use OneBox for my business IP Telephony. Could it be that?
I did, in fact, manually select a couple system apps to greenify, but that's because the ROM developer put them into the system space, rather than the user space. So I'm not sure if that counts.
Here's what I have so far...
Greenified:
ES File Exlorer Pro
Facebook
Firefox
Instagram
Key Ring
SensorPush
Settings:
Working Mode: Root+Boost
Shallow Hibernation DISABLED
Aggressive Doze DISABLED
Wake-up Tracking and Cutoff DISABLED
Automated Hibernation: SELECTED
Xposed based features:
Doze on the go: SELECTED
Wakeup Timer Coalescing SELECTED
Telephone Wakeup SELECTED
Greenifying System Apps: SELECTED
BillTheCat said:
Hey, guys. I'm still having trouble with both the proximity sensor and fingerprint sensor. Could really use some expert advice here.
The phone screen often does not come back on - especially during a long call or when switching between calls, and frequently just "loses its mind" and I have to press the power button to get the screen back, or even to turn the phone off. Another problem is waking via the fingerprint sensor which is unreliable.
I don't know if it's the settings I've selected (my money is on this one) or if there's a rogue app that's hosing me. For example, I use OneBox for my business IP Telephony. Could it be that?
I did, in fact, manually select a couple system apps to greenify, but that's because the ROM developer put them into the system space, rather than the user space. So I'm not sure if that counts.
Here's what I have so far...
Greenified:
ES File Exlorer Pro
Facebook
Firefox
Instagram
Key Ring
SensorPush
Settings:
Working Mode: Root+Boost
Shallow Hibernation DISABLED
Aggressive Doze DISABLED
Wake-up Tracking and Cutoff DISABLED
Automated Hibernation: SELECTED
Xposed based features:
Doze on the go: SELECTED
Wakeup Timer Coalescing SELECTED
Telephone Wakeup SELECTED
Greenifying System Apps: SELECTED
Click to expand...
Click to collapse
Did you try the earlier suggestion of removing everything from hibernation and then hibernating one app at a time? If not, try that.
What is SensorPush? Is that the wireless thermometer thingy? Disable that and see.
tnsmani said:
Did you try the earlier suggestion of removing everything from hibernation and then hibernating one app at a time? If not, try that.
What is SensorPush? Is that the wireless thermometer thingy? Disable that and see.
Click to expand...
Click to collapse
Actually, I figured I'd start from scratch. Disabled the app in Xposed, used TiBu to wipe data and uninstall. I'm going to wipe all the caches and reboot to see what happens.
What I could use some help with is to understand what settings in the app you guys would recommend for my phone /rom:
HTC10
Maximus HD (Marshmallow)
Xposed
Once I'm OK with basic settings, I'll follow your suggestion of one app at a tim.
Yes, Sensor Push is the app for remote temperature / humidity sensors. But it's not this app, I've only had it installed for a couple days, the problem has persisted for weeks beforehand.
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Actually, I figured I'd start from scratch. Disabled the app in Xposed, used TiBu to wipe data and uninstall. I'm going to wipe all the caches and reboot to see what happens.
What I could use some help with is to understand what settings in the app you guys would recommend for my phone /rom:
HTC10
Maximus HD (Marshmallow)
Xposed
Once I'm OK with basic settings, I'll follow your suggestion of one app at a tim.
Yes, Sensor Push is the app for remote temperature / humidity sensors. But it's not this app, I've only had it installed for a couple days, the problem has persisted for weeks beforehand.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
No appwise recommendations can be made since the device, ROM, kernel, apps etc vary vastly not to speak of the the specific usage pattern of the individual.
What is recommended though is to greenify those apps which you don't use often but which keep running. Do not greenify apps which you often use.
As for system apps, be careful, but the same principle applies. Don't greenify something like PlayServices because its running is essential and it will continuously try to wake up draining battery.
Install BBS and monitor which apps drain battery and then greenify only those which drain but will not cause issues if greenified. Always greenify one app at a time to see the effects.
In general, greenify as less apps as possible.
I have a Moto G4 Play model number XT1600 (Moto G Paly in the US) and I am having some issues with the proximity sensor.
When answering a call, sometimes the screen goes dark and unresponsive to touch or by quickly pressing the power button. I have Greenify installed but I'm not sure if it is related.
After reading some posts here, I decided to understand the behavior of my phone when I make the calls and here is what I learned:
- after the proximity sensor turn the screen off when the phone is close to the ear, many times it will not detect when the phone is put away from the ear. But if you make a movement that leaves the phone in the horizontal position in your hand, the screen will be lit again (it takes a few seconds).
- if you put away the phone from the ear and leave it in a desk in the horizontal position, the screen will almost immediately be lit again. It seems that the proximity sensor works together with another sensor that detects the little bump when you put the phone on the desk.
- I did the movement to put the phone away from the ear, leaving it in the horizontal position in my hand; screen continued dark. Then with my finger I did a few taps in the back of the phone and the screen went on again.
- Another test I did when none of the above alternatives worked: in the settings there is an option to turn the camera on with a double press of the power button. When this option is set and the screen goes unresponsive while answering a call, I do the double click to activate the camera. The screen turns on with the camera app and then I am able to switch to the phone app.
Annoying but it is an alternative solution.
Not sure if this is the normal behavior but this is what I learned today
hjbuzzi said:
I have a Moto G4 Play model number XT1600 (Moto G Paly in the US) and I am having some issues with the proximity sensor.
When answering a call, sometimes the screen goes dark and unresponsive to touch or by quickly pressing the power button. I have Greenify installed but I'm not sure if it is related.
After reading some posts here, I decided to understand the behavior of my phone when I make the calls and here is what I learned:
- after the proximity sensor turn the screen off when the phone is close to the ear, many times it will not detect when the phone is put away from the ear. But if you make a movement that leaves the phone in the horizontal position in your hand, the screen will be lit again (it takes a few seconds).
- if you put away the phone from the ear and leave it in a desk in the horizontal position, the screen will almost immediately be lit again. It seems that the proximity sensor works together with another sensor that detects the little bump when you put the phone on the desk.
- I did the movement to put the phone away from the ear, leaving it in the horizontal position in my hand; screen continued dark. Then with my finger I did a few taps in the back of the phone and the screen went on again.
- Another test I did when none of the above alternatives worked: in the settings there is an option to turn the camera on with a double press of the power button. When this option is set and the screen goes unresponsive while answering a call, I do the double click to activate the camera. The screen turns on with the camera app and then I am able to switch to the phone app.
Annoying but it is an alternative solution.
Not sure if this is the normal behavior but this is what I learned today
Click to expand...
Click to collapse
I experienced this same issue on an older XT1030 which is the mini varient of a 2nd gen Moto X. Spent quite a bit of time trying to diagnose the issue (like you) and had devised various work-arounds that were never quite satiafsctory. Also rocking Greenify w/Xposed but ultimately determined that was not a direct factor with the proximity sensor glitch.
What fixed it (for me) was Gravity Screen which you can find in the Play Store. Takes a bit to get understand how to configure but very nice once everything is set up. One downside is you will probably want to disable Moto's active screen function - at least during initial configuration. Good luck.
Is there any reason why pending updates might have an effect on the proximity sensor?
Sent from my HTC 10 using Tapatalk
BillTheCat said:
Is there any reason why pending updates might have an effect on the proximity sensor?
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
I have noticed that if app updates are kept pending in PlayStore, it does affect various things, which seem totally unconnected.
tnsmani said:
I have noticed that if app updates are kept pending in PlayStore, it does affect various things, which seem totally unconnected.
Click to expand...
Click to collapse
Ah. So I'm not hallucinating after all...
Sent from my HTC 10 using Tapatalk
Well guys, it looks like I'm going to have to abandon Greenify. I just can't seem to find any combination of settings that won't interfere with the proximity sensor. Unfortunate, really, because it's a great app and I even bought the donation package, but it's just making my life miserable.
Anyway suggests for alternatives would be appreciated. I have one mention for 'force doze'. Anything else?
Sent from my HTC 10 using Tapatalk
I wish I had more technical skills to understand why my Moto G4 Play (XT1600) had its proximity sensor behaving erratically for several days. I uninstalled Greenify and installed it again. Settings are
Working mode NON ROOT, Agressive doze ON, Wake-up Tracking DISABLED, Auto Hibernation OFF, Alternative Screen Off Mode OFF, Quick Action Notification OFF, Long Press OFF, Don't Remove Notifications ON, Xposed Features (not available), Greenifying System Apps OFF, Extras for Geek OFF.
My proximity sensor is working fine with Greenify installed.
I keep all my apps and system up to date and I suspect that some recent update may have fixed the erratic behavior of the proximity sensor.
hjbuzzi said:
I wish I had more technical skills to understand why my Moto G4 Play (XT1600) had its proximity sensor behaving erratically for several days. I uninstalled Greenify and installed it again. Settings are
Working mode NON ROOT, Agressive doze ON, Wake-up Tracking DISABLED, Auto Hibernation OFF, Alternative Screen Off Mode OFF, Quick Action Notification OFF, Long Press OFF, Don't Remove Notifications ON, Xposed Features (not available), Greenifying System Apps OFF, Extras for Geek OFF.
My proximity sensor is working fine with Greenify installed.
I keep all my apps and system up to date and I suspect that some recent update may have fixed the erratic behavior of the proximity sensor.
Click to expand...
Click to collapse
Aggressive doze is neither needed nor beneficial on most configs. However, it can result in erratic app/device behavior. Suggest disabling and observe drain over several charge/discharge cycles. If only looking at at sleep performance be sure to include 1-2 min after waking as the device plays 'catch-up'. If there are no overall benefits to aggressive doze why introduce the potential for side-effects?
App switching screen on Android 12 is pretty bad. So easy to make mistakes, always unintentionally swiping down or up. I haven't used Android 11, not sure if they are same . Came from iOS.
I came from an lg v20 with android 8 on it and i prefer how it was done on there but with the new app switcher screen I have to say I love the easy screenshot, url sharing, and text selection on screens that are otherwise not text selectable so I guess that makes up for it.
What i dont like is the screen isnt very responsive to touch with my tempered glass screen protector unless I force 90hz in developer options. Speakers sound like crap compared to my v20 , and of course no easily removable battery, no microsd slot, no headphone jack and no ir remote sucks too but as far as I know there isnt a single good flagship phone out there that still has all those.
I only bought a new phone because the v20 became unbearably slow and good new batteries are hard to come by anymore, I also need it for developing AR apps.
nraudigy2 said:
App switching screen on Android 12 is pretty bad. So easy to make mistakes, always unintentionally swiping down or up. I haven't used Android 11, not sure if they are same . Came from iOS.
Click to expand...
Click to collapse
By default, they use a bunch of hideous gestures.
Go into System Settings --> Accessibility --> System controls, and change "System navigation" to "3-button navigation". That will give you three nice buttons on the bottom edge of the screen... back, home, and task switcher.
96carboard said:
By default, they use a bunch of hideous gestures.
Go into System Settings --> Accessibility --> System controls, and change "System navigation" to "3-button navigation". That will give you three nice buttons on the bottom edge of the screen... back, home, and task switcher.
Click to expand...
Click to collapse
Checked this out too, but you get the ancient Android 7-or-8 like buttons. Much rather see the Pixel 3's buttons placed on the bottom.
Although the gestures are a bit finicky, it took me a while to get used to, but now I've got it under control.
Its not about "ancient", its about EFFECTIVE. The 3-button menu bar is the only option that has ever existed that doesn't involve indecypherable/inconvenient gestures.
Helpmepleasekidnqpped said:
My wife was kidnapped and I have no idea how to get her GPS turned on. her phone find my device is off but she tried to share location with me
Click to expand...
Click to collapse
Call the police! They may require SIM card tracking from the operator! Or by IMEI of the device!
trabadura said:
Call the police! They may require SIM card tracking from the operator! Or by IMEI of the device!
Click to expand...
Click to collapse
I'm 99.99% positive that you replied to some kind of scammer. They created a profile to report this on a random forum? I reported the user, if there is any legitimacy, forum admin can sort that out and deal with it.
bebop707 said:
I came from an lg v20 with android 8 on it and i prefer how it was done on there but with the new app switcher screen I have to say I love the easy screenshot, url sharing, and text selection on screens that are otherwise not text selectable so I guess that makes up for it.
What i dont like is the screen isnt very responsive to touch with my tempered glass screen protector unless I force 90hz in developer options. Speakers sound like crap compared to my v20 , and of course no easily removable battery, no microsd slot, no headphone jack and no ir remote sucks too but as far as I know there isnt a single good flagship phone out there that still has all those.
I only bought a new phone because the v20 became unbearably slow and good new batteries are hard to come by anymore, I also need it for developing AR apps.
Click to expand...
Click to collapse
Welcome to 2021! Phones haven't had removable batteries for a while now...
dunno how your triggering app switching when swiping up and down considering you need to swipe from bottom of screen and hold it for a good second
basic gestures hard