Related
Hello,
Since it seems like no one has ever asked this question before I've decided to post about it.
On the Droid when you dial a phone number and put the phone up to your ear it locks the phone's screen. Then if you are dealing with a PBX or menu system on the phone that requires you to press a certain option and you move the phone away from your ear to tap the dialer, the screen automatically auto-unlocks. This is, by far, the best feature I have seen in a phone to-date.
Where do I get a dialer that supports that feature (it obviously uses the accelerometer)? Somehow I doubt you can just rip the APK out of the Droid image and have it work on a G1. Or does that feature just not work on the G1 for some reason?
Any replies are appreciated.
--Nickhttp://forum.xda-developers.com/showthread.php?p=6419439#post6419439
nbetcher said:
Hello,
Since it seems like no one has ever asked this question before I've decided to post about it.
On the Droid when you dial a phone number and put the phone up to your ear it locks the phone's screen. Then if you are dealing with a PBX or menu system on the phone that requires you to press a certain option and you move the phone away from your ear to tap the dialer, the screen automatically auto-unlocks. This is, by far, the best feature I have seen in a phone to-date.
Where do I get a dialer that supports that feature (it obviously uses the accelerometer)? Somehow I doubt you can just rip the APK out of the Droid image and have it work on a G1. Or does that feature just not work on the G1 for some reason?
Any replies are appreciated.
--Nick
Click to expand...
Click to collapse
The Droid uses a proximity sensor to tell when it goes up to your ear:
pocketnow.com said:
The Motorola Droid also has a proximity sensor so that the screen shuts off when you hold the phone close to your face. This helps to conserve battery life while at the same time prevent accidental screen input if your cheeks press upon the screen.
Click to expand...
Click to collapse
Not sure how you would do the same thing with the Accel.
That feature actually uses the proximity sensor, which the G1 unfortunately lacks.
jshealton said:
The Droid uses a proximity sensor to tell when it goes up to your ear:
Click to expand...
Click to collapse
Oh. That makes sense.
jshealton said:
Not sure how you would do the same thing with the Accel.
Click to expand...
Click to collapse
Not sure why it would be so hard. Accel can tell how it's positioned and the position next to your ear is completely different from that of holding your phone in front of you. It would just require some evaluation and data recording of degrees and ranges.
nbetcher said:
Oh. That makes sense.
Not sure why it would be so hard. Accel can tell how it's positioned and the position next to your ear is completely different from that of holding your phone in front of you. It would just require some evaluation and data recording of degrees and ranges.
Click to expand...
Click to collapse
Not sure about that. If I remember correctly the accell only sees if the phone is in landscape or portrait orientation, and when you are talking on the phone it is almost straight up and down. Not sideways. Will venture to find an answer.
Edit: You almost have to have the phone on its side for the accel to see that you have moved your phone. Don't know about you but when I talk on the phone it is almost up and down.
jshealton said:
Not sure about that. If I remember correctly the accellerometor only sees if the phone is in landscape or portrait orientation, and when you are talking on the phone it is almost straight up and down. Not sideways. Will venture to find an answer.
Click to expand...
Click to collapse
That certainly can't be since many games, namely Armageddon Squadron (flying game) use the X and Y axis on the phone (roll vs pitch). Also think of rolling objects in games that you have to "steer."
nbetcher said:
That certainly can't be since many games, namely Armageddon Squadron (flying game) use the X and Y axis on the phone (roll vs pitch). Also think of rolling objects in games that you have to "steer."
Click to expand...
Click to collapse
That may be true. I don't have any games on my phone that use the accel. I can only go by logcat durring screen orientation. I am sure you can now, the only problem is at what amout of tilt does the screen lock. And you would have to tie it in to when there is a call connected. Would hate for my sreen to auto lock when I am laying in bed playing with my phone.
jshealton said:
And you would have to tie it in to when there is a call connected. Would hate for my sreen to auto lock when I am laying in bed playing with my phone.
Click to expand...
Click to collapse
Well, of course it's connected to the dialer - that's its only purpose. If the dialer doesn't have foreground then it won't auto-lock.
If developing for Android wasn't such a pain in the ass (compared to C++) and I knew more Java classes/methods then I'd probably just implement this myself. I'll probably get the myTouch Slide soon enough though.
We wouldn't be able to so much measure the exact position to do this but a good shake-like-hell-to-unlock-dialpad event might be possible... If I (or someone) can find some code for a dialer, I'd be happy to take a stab at making it "native..." I know just enough Java/Android to cause some trouble, so it could only be good ;-) If not the dialer, then an app could be started as a service, with an intent to snag the call, and listen for a good jostling. I wonder what this would do to the battery/performance and how often I would have to make it poll the sensor? Hmm....
I'll see if I can poke around and find ANYTHING. Haven't googlified anything yet... I do need something constructive to add to my workload.
And yes, the accelerometer measures force applied to the X, Y and Z axis. you can technically program it to sense when you've dropped (or are dropping) the phone.
boredpcguy said:
We wouldn't be able to so much measure the exact position to do this but a good shake-like-hell-to-unlock-dialpad event might be possible... If I (or someone) can find some code for a dialer, I'd be happy to take a stab at making it "native..." I know just enough Java/Android to cause some trouble, so it could only be good ;-) If not the dialer, then an app could be started as a service, with an intent to snag the call, and listen for a good jostling. I wonder what this would do to the battery/performance and how often I would have to make it poll the sensor? Hmm....
I'll see if I can poke around and find ANYTHING. Haven't googlified anything yet... I do need something constructive to add to my workload.
And yes, the accelerometer measures force applied to the X, Y and Z axis. you can technically program it to sense when you've dropped (or are dropping) the phone.
Click to expand...
Click to collapse
try looking here.
http://github.com/cyanogen/android_packages_apps_Phone
edit: It should be possible, since it looks like a feature to "turn over to silence" has been implemented.
boredpcguy said:
We wouldn't be able to so much measure the exact position to do this but a good shake-like-hell-to-unlock-dialpad event might be possible...
Click to expand...
Click to collapse
I'm not sure if shaking my phone is really much better than tapping the screen twice - both require similar times for completion.
boredpcguy said:
If I (or someone) can find some code for a dialer, I'd be happy to take a stab at making it "native..."
Click to expand...
Click to collapse
Here's a tar.gz of the source-code that was released with the Droid https://android.git.kernel.org/?p=p...9af2e10e23c7c21f22abec5f3d7fa05d6406a2;sf=tgz
Not sure if it's still out and compatible with the newest builds, but the app Shake Awake did this quite some time ago.
Hairybroness said:
Not sure if it's still out and compatible with the newest builds, but the app Shake Awake did this quite some time ago.
Click to expand...
Click to collapse
I used to use this on android 1.1. iirc it stopped working on cupcake, and I haven't checked on it since then.
I don't think this would work, because what if you're laying down with the phone? I'm pretty sure it would mess up with the Accel. I'm not too much into this, but when playing a game like teeter for example, the side of your phone has to be horizontal with..the horizon (correct me if I'm wrong)
Dialer wake-up w/o real sensor
Shake Awake never worked too well for me.
I have always wondered in the back of my non-programmer brain if one who was really good could implement a sonar/feedback type code whereby when the phone was close to an ear, the amount of feedback from the earpiece to the mouthpiece was quite low, but drawn away from the ear increased just enough for the phone to pass through to the code through an intent (is there anything like a feedback intent? I bet Meltus would know!), which would issue the commands to unlock and wake-up.
More ideally would be a program which got the earpiece to put out a search tone up around 20 kHz, which would be analyzed by the mouthpiece. Sound present = user has moved the phone away from the ear, wake up and unlock to touchpad, sound muffled or totally gone = user is still using the earpiece, don't unlock.
BTW, all 2.1 eclair ROMs I've used in the past 3 months have a setting for a substantial improvement to screen awake times during calls.
Don't think this has been asked before:
So I usually use my tab sitting in my chair chilling with it up in front of me in landscape.
I have tried to play 2 games now that use the device's accelometer (since it doesn't have a gyroscope from what Ztest says). Both are going totally nuts. Is there anyway to calibrate it internally so that when I am chilling out with it upright it uses that calibration rather than the one when it is laying flat (ie on a table).
I doubt there is, but hey its worth a shot, and just in case anyone was curious, it was Grabtron (indie free game from the market) and Asphalt 5 both with the issue.
Grabtron actually has a calibration option, however you can't calibrate it with the position I use the device in, which I find kind of interesting.
So I am guessing that is a no? There is no way to calibrate it for an upright position rather than a laying down position?
Gtab2 have gyroscope: MS-X orientation sensor
Good to know, any way to calibrate it?
Rotundjere said:
Gtab2 have gyroscope: MS-X orientation sensor
Click to expand...
Click to collapse
Learned something new today, the diagnostics software I was using said it was an accelometer, and did not have a gyroscope, guess it doesn't know how to read ours correctly.
The next question is any way to calibrate it? So I can enjoy my games chilling out in a chair rather than leaning over using it over a table?
One of the most annoying things of the Gear 1 is the motion to wake up the watch. Is it improved? I watched a bunch of hands on but they all tell the same story. No word about the fact that the display can't be lit all the time and that you have to do some abracadabra to wake the device. Most curious about any improvements in this department.
appelflap said:
One of the most annoying things of the Gear 1 is the motion to wake up the watch. Is it improved? I watched a bunch of hands on but they all tell the same story. No word about the fact that the display can't be lit all the time and that you have to do some abracadabra to wake the device. Most curious about any improvements in this department.
Click to expand...
Click to collapse
well you can't have screen all the time due to technology used. AMOLED. if it would be LCD then you could have screen on all the time, but without background light (like in sony smartwatch 2). i already got used to blank screen, and i just turn the screen on/off with a single button.
hurdlejade said:
well you can't have screen all the time due to technology used. AMOLED. if it would be LCD then you could have screen on all the time, but without background light (like in sony smartwatch 2). i already got used to blank screen, and i just turn the screen on/off with a single button.
Click to expand...
Click to collapse
I know. I'm wondering if they made the watch more sensitive for motions, introduced a new or better wake up motion etc . Definitely want to know more about that.
if samsung did not mention it, then probably it's the same.
hurdlejade said:
if samsung did not mention it, then probably it's the same.
Click to expand...
Click to collapse
That would be a detail for people coming from the Gear1.
If the battery life is better they might have add a more sensitive option.
Btw personally I dont mind to charge the watch every night. Just some routine. I like it even better than checking the battery to see if it needs to be charged again. So if they made the wake up motion more sensitive and could still pump one day out of the battery, it would definitely be a reason for me to upgrade. Otherwise I see no compelling reasons.
I understand what OP is saying. I'm interested to know that answer as well. I actually had to turn motion off because the watch constantly stayed on while driving all day. It would kill my battery. With it off and me pressing the on button as needed, I get at least 3 days of battery life. A better motion sensor could possibly solve this issue.
alprazolam said:
I understand what OP is saying. I'm interested to know that answer as well. I actually had to turn motion off because the watch constantly stayed on while driving all day. It would kill my battery. With it off and me pressing the on button as needed, I get at least 3 days of battery life. A better motion sensor could possibly solve this issue.
Click to expand...
Click to collapse
I noticed having non-TW launcher caused issues with the motion sensor. Using stock had better motion sensor.
Sepharite said:
I noticed having non-TW launcher caused issues with the motion sensor. Using stock had better motion sensor.
Click to expand...
Click to collapse
what kind of issues did you have? i had none with nova.
I read a hand on today where the reviewer said it does turn on with the flick up of the wrist but that it doesn't turn on right away, like a couple of seconds delay. That isn't good. I want it to be quick like the pebble when you shake the wrist slightly the light comes on. Hopefully they tweak that before it is released....
Sent from my SM-N900P using Tapatalk
hurdlejade said:
what kind of issues did you have? i had none with nova.
Click to expand...
Click to collapse
I haven't had any problems with it either.
everlast716 said:
I read a hand on today where the reviewer said it does turn on with the flick up of the wrist but that it doesn't turn on right away, like a couple of seconds delay. That isn't good. I want it to be quick like the pebble when you shake the wrist slightly the light comes on. Hopefully they tweak that before it is released....
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
That's what I want. I move my arm to that wrist up position to much so the watch is almost always on. I wish it had the option to shake the wrist instead so I have better control.
Personally the only good thing about this watch is the motion thing. It works like a good 90-95% of the time. Wake up is excellent on it. However, it goes crazy when your driving.
When I put my finger on the sensor, it used to open instantly, but now it takes about a second and a half.
Anyone know why this is happening?
Are you talking about the fingerprint sensor?
Sounds like he's talking about the fingerprint sensor but due to the confusing title, I am not sure.
JAYNO20 said:
Sounds like he's talking about the fingerprint sensor but due to the confusing title, I am not sure.
Click to expand...
Click to collapse
Yeah, i'm talking about that.
When you put your finger on the sensor when the device was sleeping, it would instantly wake. Now it takes about a second to do wake.
Hi guys,
Noticed a very interesting thing today: suddenly a white light started to pulse next to the front cam every time I was tilting the phone. It was quick 3-4 pulses with strict intervals as if a sensor was working. It didn't pulse when phone was in a fixed position, only when tilting, in all apps.
A reboot fixed this, but I wonder if there is any sensor there that activated because of something? Never experienced this before!
Any thoughts what it can be? Thx.
Sounds like proximity sensor to me.
znel52 said:
Sounds like proximity sensor to me.
Click to expand...
Click to collapse
Thanks. I also thought so but the phone didn't turn off the screen when I was placing my finger on that sensor. The proximity sensor should turn the screen off as far as I am aware. Maybe a glitch after doing a video call via Viber?
VirtualWaver said:
Thanks. I also thought so but the phone didn't turn off the screen when I was placing my finger on that sensor. The proximity sensor should turn the screen off as far as I am aware. Maybe a glitch after doing a video call via Viber?
Click to expand...
Click to collapse
A glitch with viber thats causing excessive proximity sensor usage. It will eventually burn the pixels around that area like the other post posted today.
Limeybastard said:
A glitch with viber thats causing excessive proximity sensor usage. It will eventually burn the pixels around that area like the other post posted today.
Click to expand...
Click to collapse
Thanks for this! I did test my screen and all looks good but this is worrying. However, this only happened once although I use Viber video calls every day.
VirtualWaver said:
Thanks for this! I did test my screen and all looks good but this is worrying. However, this only happened once although I use Viber video calls every day.
Click to expand...
Click to collapse
Im going to try this out myself next week and see what's going on. Mine ain't coming until Monday.
Limeybastard said:
A glitch with viber thats causing excessive proximity sensor usage. It will eventually burn the pixels around that area like the other post posted today.
Click to expand...
Click to collapse
Hoe bright is it?
Normally it could blink during SOT and with that duty cycle it will outlast many of the other screen pixels.
Or is there something I'm missing???
Are it's pixels IR?
blackhawk said:
Hoe bright is it?
Normally it could blink during SOT and with that duty cycle it will outlast many of the other screen pixels.
Or is there something I'm missing???
Are it's pixels IR?
Click to expand...
Click to collapse
Who's a hoe?
Probably much ado about nothing. But I can't test it. , The only thing that came to mind was screen being full brightness and proximity sensor being on for hours causing this. But just a hunch .
Limeybastard said:
A glitch with viber thats causing excessive proximity sensor usage. It will eventually burn the pixels around that area like the other post posted today.
Click to expand...
Click to collapse
Limeybastard said:
Who's a hoe?
Probably much ado about nothing. But I can't test it. , The only thing that came to mind was screen being full brightness and proximity sensor being on for hours causing this. But just a hunch .
Click to expand...
Click to collapse
Even at full brightness because it's flashing, it's duty cycle is less than the surrounding pixels plus it will "flash" by darkening its pixels depending on screen color.
If it has specialized IR emitters I could see that happening maybe; if there's a design or manufacturing flaw.
Because it's flashing visible light it would be hard to use a cam to detect IR... which is how I normally check IR emitters.
While it was easily seen on the Note 10 i can't see it on the Note 20
Nastrahl said:
While it was easily seen on the Note 10 i can't see it on the Note 20
Click to expand...
Click to collapse
Interesting. Maybe it uses IR diodes?
If it doesn't display when it's active maybe that's why some think it's "burnt out"?
Lol, until someone mentioned the flashing circle I never noticed it.
blackhawk said:
Interesting. Maybe it uses IR diodes?
If it doesn't display when it's active maybe that's why some think it's "burnt out"?
Lol, until someone mentioned the flashing circle I never noticed it.
Click to expand...
Click to collapse
I don't know.
I've read that they replaced all the sensors with the front camera, and that′s one of the battery killer since a few were completely passive like the ambiant light one, that's now active.
When a passive sensor needs no electricity to operate, an active needs to, and the camera can't work passively so it drains battery.
They advised to turn off all the features that use the front camera as a sensor like the auto brightness, smart stay (and also what can use the accelerometer like smart alert and raise to turn on the screen), etc. to avoid the process Android System to take to much battery.
Nastrahl said:
While it was easily seen on the Note 10 i can't see it on the Note 20
Click to expand...
Click to collapse
Nastrahl said:
I don't know.
I've read that they replaced all the sensors with the front camera, and that′s one of the battery killer since a few were completely passive like the ambiant light one, that's now active.
When a passive sensor needs no electricity to operate, an active needs to, and the camera can't work passively so it drains battery.
They advised to turn off all the features that use the front camera as a sensor like the auto brightness, smart stay (and also what can use the accelerometer like smart alert and raise to turn on the screen), etc. to avoid the process Android System to take to much battery.
Click to expand...
Click to collapse
Even passive sensors use some current although it may be in the microamps.
Autobrightness is a trash apk anyway.
Seems highly unlikely that the whole cam be used for these functions if at all.
VirtualWaver said:
Thanks. I also thought so but the phone didn't turn off the screen when I was placing my finger on that sensor. The proximity sensor should turn the screen off as far as I am aware. Maybe a glitch after doing a video call via Viber?
Click to expand...
Click to collapse
Not sure if anyone told you this sorry haven't had time to read the thread but I would suggest avoiding viber calls on this phone. The proximity sensor is damaging the screen when on viber. It seems viber is accessing the sensor too aggressively.
Sent from my SM-N986U1 using Tapatalk
warriorvibhu said:
Not sure if anyone told you this sorry haven't had time to read the thread but I would suggest avoiding viber calls on this phone. The proximity sensor is damaging the screen when on viber. It seems viber is accessing the sensor too aggressively.
Sent from my SM-N986U1 using Tapatalk
Click to expand...
Click to collapse
You know this is most likely a digital circuit; a fixed voltage of an either high or low value... those values are fixed and don't change. Even firmware can't alter that let alone apks. Duty cycle rate/length maybe.
This urban rumor about the proximity sensor causing screen damage has been around since at least 2015, long before OLED screens.
A Google search yielded nothing except this:
https://us.community.samsung.com/t5/Galaxy-S10/Proximity-sensor-issues-S10-S10/td-p/498492/page/9
blackhawk said:
Even passive sensors use some current although it may be in the microamps.
Autobrightness is a trash apk anyway.
Seems highly unlikely that the whole cam be used for these functions if at all.
Click to expand...
Click to collapse
Trash apk ? Sorry i meant the built-in adaptive brightness.
---------- Post added at 01:16 AM ---------- Previous post was at 01:15 AM ----------
blackhawk said:
You know this is most likely a digital circuit; a fixed voltage of an either high or low value... those values are fixed and don't change. Even firmware can't alter that let alone apks. Duty cycle rate/length maybe.
This urban rumor about the proximity sensor causing screen damage has been around since at least 2015, long before OLED screens.
A Google search yielded nothing except this:
https://us.community.samsung.com/t5/Galaxy-S10/Proximity-sensor-issues-S10-S10/td-p/498492/page/9
Click to expand...
Click to collapse
I personally never heard about it. Thanks for the insight
Nastrahl said:
Trash apk ? Sorry i meant the built-in adaptive brightness"
I personally never heard about it. Thanks for the insight
Click to expand...
Click to collapse
My opinions.
There certainly are long standing Samsung issues that span more then one generation of phones. The proximity sensor trashing the screen doesn't appear to exist at all. If anything it conserves screen life.
Auto brightness was always twitchy even on my S4+.
Auto brightness was never truly adaptive... and still isn't. Lol, all it does is give me a headache and waste resources.
The other thing is I always try to avoid using my phones in direct sunlight. Very rarely do I ever go past 65% brightness.
Direct sunlight+high ambient temperature+high power consumption can really overheat a phone fast.
Even worse...
Auto brightness on+charging+sunlight+accidental screen turn on that's not noticed, can fry a phone in a few minutes. Real easy to do in the car... been there.
blackhawk said:
My opinions.
There certainly are long standing Samsung issues that span more then one generation of phones. The proximity sensor trashing the screen doesn't appear to exist at all. If anything it conserves screen life.
Auto brightness was always twitchy even on my S4+.
Auto brightness was never truly adaptive... and still isn't. Lol, all it does is give me a headache and waste resources.
The other thing is I always try to avoid using my phones in direct sunlight. Very rarely do I ever go past 65% brightness.
Direct sunlight+high ambient temperature+high power consumption can really overheat a phone fast.
Even worse...
Auto brightness on+charging+sunlight+accidental screen turn on that's not noticed, can fry a phone in a few minutes. Real easy to do in the car... been there.
Click to expand...
Click to collapse
Thanks, i never thought about that so it's a very valuable information.
Just in case if it can be useful :
A few years ago I found an app called Underburn which is a complete new approach about adaptive brightness.
https://play.google.com/store/apps/details?id=com.out386.underburn
Instead of adjusting the screen brightness from the ambient light, it set it according of the amount of white pixels displayed on screen to avoid binding you, and it doesn't care about sunlight.
The more white is displayed, the more it will dim the screen (by reducing the screen brightness, not by applying a filter ; even if there's also a setting for that if its too bright for you even at the minimum level) by the amount of your choosing.
It can play a role to save battery too somehow.
Nastrahl said:
Thanks, i never thought about that so it's a very valuable information.
Just in case if it can be useful :
A few years ago I found an app called Underburn which is a complete new approach about adaptive brightness.
https://play.google.com/store/apps/details?id=com.out386.underburn
Instead of adjusting the screen brightness from the ambient light, it set it according of the amount of white pixels displayed on screen to avoid binding you, and it doesn't care about sunlight.
The more white is displayed, the more it will dim the screen (by reducing the screen brightness, not by applying a filter ; even if there's also a setting for that if its too bright for you even at the minimum level) by the amount of your choosing.
It can play a role to save battery too somehow.
Click to expand...
Click to collapse
Thank you
I'll take a look at it. I'm running on dark mode but since it's Pie it's not native to all apps like Gmail which burns my eyes out.
*I'm playing with it. It will run on Pie. It takes some time to set up but definitely has potential.
Haven't been able to fairly gauge it's configured battery usage.