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.
So after using the TF for a week or so, I can't decide how to orient the pad while using it in portrait mode. Sometimes it is Camera on the right side. This orientation places the power and sound buttons on top but the headphone jack is on the bottom. Sometimes the other way around. I am curious how others use the TF and if they actually have given this any thought.
lol..... top marks for producing what is, in my humble opinion, the mostly pointless poll ever on XDA
in my view you are missing an option .... i just turn the tablet randomly. i dont find i need volume and power often whilst in portrait
im not ambidextrous though !
Why is there two threads? As for where the camera is, does it really matter? When you take pictures, you have to adjust your placing anyways.
There are lots of videos showing this problem: after you have touched the screen sometimes the screen registers finger presses even after you've removed them.
It's very hard to see what is going on if you don't turn on "show touches" in settings, so I suspect many reports about touch screens being unresponsive, or acting strangely is really the same problem.
It occurs both in stock ROMs and aosp, but subjectively more often in stock roms. It's not about moisture remaining, I've wiped the screen completely clean and dry and the phantom touches are there before, during and after cleaning.
Is there a software solution to this or is it hardware? Any thoughts of how this problem could be approached? I'm having trouble even reproducing it reliably.
yet another video of the odd problem: https://www.dropbox.com/s/mglol5qon6vy67g/2013-08-11 20.15.01.mp4
I replaced my Asus TF300 because of a similar issue. Asus fixed it once under warranty (replaced the entire LCD and digitizer, I think) but the issue came right back within a few months after RMA. By then the warranty had expired. In my case, the ghost touches were prevalent in a specific part of the screen; couldn't tell from your video whether the false touches were in the same general area every time or not.
Surprisingly, until the problem became so bad that an entire area was unusable, I could flash a new ROM and get somewhat different behavior. Just to be sure, though, I did flash a stock ROM prior to sending back to Asus and verified the issue existed there, labeled the area with tape so they could not miss it, and described in details the steps to reproduce.
Good luck.
Sent from my GT-N8013 using xda app-developers app
bsaman said:
I
Surprisingly, until the problem became so bad that an entire area was unusable, I could flash a new ROM and get somewhat different behavior.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
This is my experience also, the aosp revolt rom, seems to suffer much less so than the stock roms.
It does seem to be the same area but it might be just because it's the side that is used most often for scrolling due to me being right handed.
The difference between how the roms behave is what make me suspect it's a software issue.
Just to be clear, you've not noticed this even once with your note? Before I turned on the "show touches" I saw it most clearly when I used chrome or other programs with scrollable elements. The page would sometimes just vibrate a little when left alone.
PremiumMediocre said:
Just to be clear, you've not noticed this even once with your note? Before I turned on the "show touches" I saw it most clearly when I used chrome or other programs with scrollable elements. The page would sometimes just vibrate a little when left alone.
Click to expand...
Click to collapse
No, my note has been rock solid, but I haven't enabled show touches so I can't say for sure.
Sent from my Vivid 4G using xda app-developers app
I'm thinking it might be possible to alter the idc file that specifies the behaviour of the touchscreen (https://source.android.com/devices/tech/input/input-device-configuration-files.html). But it's all a bit over my head.
I'm not alone at least:
http://www.youtube.com/watch?v=ii7m2696T3Y
A simpler cause?
I'm not alone at least:
(YouTube Video URL that I'm not allowed to post, yet)
Click to expand...
Click to collapse
The guy in the video did a great job with research. Did you catch the part where he found nearly imperceptible damage to the screen that was a possible cause? The ghosting always seems to occur in the same places because that's where the screen has been "crushed". Now "crushed" is a bad word because the screen probably hasn't been compressed beyond an acceptable level but there might be some correlation between where the users normally places his/her hand when using the pen and where the phantom touches occur. Maybe when writing, some users are baring-down harder than they realize and prolonged pressure in the same arc-shaped area created by the side of a hand, causes some changes in the capacitive properties in that area which cause a "latch" condition -- where the digitizer gets stuck and won't unstick until power is removed.
I've noticed in the videos that I've seen that the presenter get the problem to appear when using the side of their hand in a rolling fashion -- probably the same motion that they use when they just start to write. I also believe that devices that have this problem "get better" or less sensitive when not used for a while. This would follow the idea that the screen is compressed and given some time, the compression relaxes.
If the problem is limited to a certain area of the screen, I find it hard to believe that the problem could possibly have anything to do with ROM or firmware. The matrix of the digitizer in X-Y coordinates is addressed such that if there were a problem like this, the error would occur and repeat in either a straight vertical or horizontal direction instead of finite points spanning many rows and columns.
I guess one way of ruling this idea out would be to find someone who has never used the pen to write yet still has the problem.
I haven't ruled out that it is hardware related, but I have noted a significant improvement leaving stock ROMs for aosp. Maybe that's just a coincidence, I can't know for sure. I have noted something else that might help diagnose this problem.
If the period of turning on the screen, using the tablet then turning off the screen constitutes one session, there are two types of sessions. Sessions which suffer from this problem, which will be apparent in a relative short period of time. But there are also sessions where everything works as it should, regardless of how long the session is. So you will notice this problem within 10 min or not at all.
There really should be a pinned thread for utter disappointed features and/or people.
I am not returning my new SW2. Its too cool to have the lamest, inept and funtion-killing GUI cause me to give up. ** But I bought a Pebble watch the same day because (the SW2n currently):
- can not function as a watch. It does but it goes to sleep VERY fast. WAY too fast. This is completely unacceptable. If I want to drain my f*ing watch and be able to read it all day, I should be able to!!! Put a warning on the settings area.. like: WILL DRAIN BATTERY VERY FAST or something...
- Can not finish reading my incoming sms. Maybe you dont know the girl I am dating but she WRITES A LOT... and this may not be normal amounts ... I really mean a lot. And SONY clearly has NO IDEA about this.
- AND continuing from the above point, it goes back to the f*ing CLOCK in sleep mode. SHOULD dim and remain on my screen until I SAY OTHERWISE. NOW I have to press the power button and NOT make it power off buy accident (another STUPID DESIGN) and make it activate, press the home button and then the stupid function messaging button. NO LOGIC FLOW HERE. I have to read 5 or 6 TXTs by now.
- CAN NOT read the messages in order without going BACK and opening the messaging app again. At least that seems to be what I had to do. I might have missed proper procedure here but if that is true, shame on SONY for lacking a more intuitive operation.
The Poweramp app is cool when it works. It should STAY active. I DONT CARE about anyone else or what slogan SONY wants to claim about battery life. I want FUNCTION my f*ing way. I use Poweramp all the time. But it is not able to stay on my watch, active? Total shame.
The ONLY app I kept on my watch is the custom watch faces. It allwos me to keep the display on until the dumbwatch, overthinking watch disconnects from my RazrMaxx/4.4 Dhacker29 ROM.
So in conclusion, This watch completely fails at being a watch. Fails at running apps because it times out WAY TOO FAST. Fails at every possible area other than fitting well.
Maybe your accelerometer is faulty. It should not timeout when on hand, actually it dims and always shows time.
Sent from my SM-N9005 using Tapatalk
jmaciak said:
Maybe your accelerometer is faulty. It should not timeout when on hand, actually it dims and always shows time.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I hate to be the guy to say it, but is the OP trolling us?
I have the smartwatch 2, just got it yesterday, and what the OP is saying makes no sense.
deitiphobia said:
I hate to be the guy to say it, but is the OP trolling us?
I have the smartwatch 2, just got it yesterday, and what the OP is saying makes no sense.
Click to expand...
Click to collapse
Well it can timeout and go totally blank ... try it, put them on the table and do not move the watch/table and it will dim and then go completely blank after a while, because the accelerometer sees it's not on the hand. So if OP's accelerometer is faulty, it might behave this way ...
jmaciak said:
Well it can timeout and go totally blank ... try it, put them on the table and do not move the watch/table and it will dim and then go completely blank after a while, because the accelerometer sees it's not on the hand. So if OP's accelerometer is faulty, it might behave this way ...
Click to expand...
Click to collapse
I am not a troll. At least I am not trying to be a troll. I do feel slightly underwhelmed buy my experience so far.
And maybe my accelerometer needs checking? If it is supposed to remain on (the screen) for more than 5 seconds when I am wearing it and trying to read something, then yes, something is wrong. Maybe the watch doesnt know when it is on a troll arm?
deitiphobia said:
I hate to be the guy to say it, but is the OP trolling us?
I have the smartwatch 2, just got it yesterday, and what the OP is saying makes no sense.
Click to expand...
Click to collapse
Hello,
What he is saying actually makes perfect sense, especially on this forum - we are not the average, marketing-targeted user and we like to use our devices any way we please, without being limited by design hickups. And we are more sensitive to design flaws and marketing bs than the average consumer.
Sony missed and even lied about basic features and is not allowing, at least so far, anyone to tweak with this product's FW.
In my experience the watch proved very useful ONLY IF YOU ARE NOT RELYING SOLELY ON IT for most of your work - i, for one, would not like to read my correspondence on such a tiny screen and prefer to use the phone instead - but it would sure be nice to know that I CAN use the watch if i wanted to.
Fortunately, while driving a motorcycle, for example, getting a hint of the message content usually suffices for me to determine if i need to pullover and get my phone out, provided i get to see the screen before it times-out, which is another awkwardly missing basic function.
I will, however, hold on to the SW2 for now in hopes that Sony will straighten things the way they should.
Sent from my LT25i using Tapatalk
i agree fully with the OP as well
if i didn't know better, i would suggest posting your opinions on talk sonymobile, but as i already did that and got NO reply from Sony, i guess it would be just a waiste of time
that's my biggest problem with Sony right now: no communication
(although i must admit most manufacturers suck at communicating with their customers, try finding out when the Butterfly s is getting 4.3/4.4, not a chance)
I actually agree with the OP, there are some features that could be included in the settings menu like timeout duration or stopping the watch default to the watch screen every time it goes into standbye especially useful if travelling and using features like poweramp - you need 3x button presses to bring the poweramp screen back on and if you have a messaging app open (reading messages) it should prevent the watch from sleeping
and how fecking hard is it to develop a few watch face designs with different colours etc
TBH I think Sony are in the process of designing a totally new Smartwatch for release in early 2014 and have completely dropped the ball with this one
well, there was an update today, so i guess they didn't drop it completely
update looked good at first, but disappointing anyway
-only 1 extra watch face that's usable, i still want the abilty to design/choose my own watch face
-the option to use the light sensor for brightness is nice, but i'm glad it's optional, don't like it
-music app update totally messed it up (used to work for me)
-camera app update didn't do anything for me, still does nothing
-still no selectable timeout, huge issue for me
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
Find It for SmartWatch by AQ i purchased also doesn't work anymore
argh, their own Find Phone Smart Extension ALSO doesn't work anymore!
JarlSX said:
their own Find Phone Smart Extension ALSO doesn't work anymore!
Click to expand...
Click to collapse
AFAIK I suspect that problems might occur pairing the SW2 with a non-Sony smartphone.
But please let's keep the discussion in one place only, so we can better compare these findings:
http://forum.xda-developers.com/showthread.php?t=2554874
i think i know why the watch can't dim while still displaying an app
those apps don't really run on the watch, they're just displaying what's happening on the phone (that's where the app is installed)
so for a watch-app to work, the watch is constantly communicating with the phone
such a connection will probably drain the watch very quickly
only the watch part can run independently, so that's why it always goes back to that screen, to save power
this is of course just what i think
FWIW, the screen on time can be controlled by the app. I use and app called IPBike for cycling which runs on the phone. This app allows you to use the watch as a head unit on the bars. It has an option to keep the watch screen on for the entire ride.
jmaciak said:
Well it can timeout and go totally blank ... try it, put them on the table and do not move the watch/table and it will dim and then go completely blank after a while, because the accelerometer sees it's not on the hand. So if OP's accelerometer is faulty, it might behave this way ...
Click to expand...
Click to collapse
Should it really go totally blank/black? Mine is only dimmed out and showing clock face all the time, but really dimmy. And it is on the table...
Oh it does, took some time, longer than i expected...
Sent from my GT-N8000 using Tapatalk 4
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.