Related
hello friends, I need to know, how much energy can be spent, the proximity sensor
using Tap Tap app.
I'm looking for the best option to unlock the screen without touching the power button
T989
Im not quite following. Whats the Tap Tap app have to do with the proximity sensor and are you wanting to keep the screen live with the app open?
Sent from my SAMSUNG-SGH-I727 using Tapatalk
I think he's referring to the "always on" feature, keeping the proximity sensor always working so that the phone can be unlocked by waving your hand over the phone a set number of times (without even touching the phone physically)
However, battery life would only be a small concern IMO.. I would be more worried about the durability of the sensor being constantly on.. as in, would it cease to function eventually from over usage?
Update: it seems the "always on" setting is being reported as shutting off on it's own despite settings after an extended period of time. Reports vary from ten minutes to several hours/overnight, so the amount of time before it fails to stay active is unclear.
Personally I'm not sure of that's a bug or intentional. There are a couple of logical reasons to force the auto shut off after some time
1. Security - If you're not using your phone for an extended period of time, then it should lock back up, because frankly some people are idiots. Also who would want their phone easily accessed because they took a nap or ran to the store and forgot their phone? If you're not near it, you don't need to show off the feature (which let's be honest, that's the coolest thing about it. Who wants to constantly wave their hand over their phone like a weirdo with no one watching? You're not a wizard bro no matter how many RPG's you play)
2. Sensor Durability - the app won't last long if there's people in the play store leaving ratings like "proximity sensor doesn't work anymore, even after uninstalling. Factory reset didn't fix, I'm suing you ****er!". Plus if the Dev's worth supporting he's already tested and knows that's an issue, then he or she's protecting their customers
All of this information comes from user reports in the Google Play store and various threads. I have not installed the app and do not plan to until I see consistent commenting that issues have been addressed or resolved by the Dev (and yes I will be watching)
Seems like a "show off" app and I'd like to give it a shot when I'm sure it's functional. Typically in this case I'd just install, see what happens then email the Dev. However when it comes to hardware (proximity sensor) I'm a little more cautious since my phone is running like a champ with a flawless screen..I can't risk an exchange.
Sent from my T989 hunting for Siri Connor
Just thought I would point out that, when using an AT&T Skyrocket UCLA3-based ROM, the proximity sensor turns itself off if you leave the Phone app so that the screen doesn't keep turning off if you try to pull down the notification tray
I have purchased a device, one X, but I did not see features in the system impressive when seen on the subject of galaxy S3 See some of the properties that characterize the system ((i say the system and not the device)) my question for programmers and developers you can add features that our system beloved of (one x) and such
1 Property of lock the device (which is linked to eye)
2 Feature video calling(
It's supposed to be present because the camera front available)
3 Face to open the device footprint
And many things I do not remember
It is well known that the device (OneX) features a powerful Hardware
But I do not see anything useful on the system
You need the Samsung eye sensor hardware to use the screen on feature. There are apps for video calling. I didn't know HTC removed face unlock but it should be in most of the dev os. Sense is not going to grow much on this so if you need Samsung then sell before it drops value any further.
My one x has face unlock, go to settings then security then screen lock and pick face unlock.
Sent from my HTC One X using Tapatalk 2
IN GALASY S3
There is a new property which is not mentioned when the arrival of a new message and the message you want to contact the owner all played by the lifting device directly at the ear and it will automatically connect to the owner of the message
samsung only. just tap the persons name at the top of the message and hit the green call button
kasserx said:
I have purchased a device, one X, but I did not see features in the system impressive when seen on the subject of galaxy S3 See some of the properties that characterize the system ((i say the system and not the device)) my question for programmers and developers you can add features that our system beloved of (one x) and such
1 Property of lock the device (which is linked to eye)
2 Feature video calling(
It's supposed to be present because the camera front available)
3 Face to open the device footprint
And many things I do not remember
It is well known that the device (OneX) features a powerful Hardware
But I do not see anything useful on the system
Click to expand...
Click to collapse
Video calling IS available. You just need an app like Skype or Fring. Do note that carriers are moving away from "video calls" and are servicing video calls through your 3g data connection instead. Years ago, phone plans included credit for calls, sms and VIDEO calls. They don't do that anymore. It's all through your data plan/Wi-Fi now.
kasserx said:
IN GALASY S3
There is a new property which is not mentioned when the arrival of a new message and the message you want to contact the owner all played by the lifting device directly at the ear and it will automatically connect to the owner of the message
Click to expand...
Click to collapse
Very gimmicky. Just like Facetime and Siri, it's something that will rarely be used outside of the first week/month.
phil112345 said:
samsung only. just tap the persons name at the top of the message and hit the green call button
Click to expand...
Click to collapse
I think Samsung has people hypnotized. I mean seriously, your hands are already on the phone working in either a contact, e-mail, or text. So how difficult is it to press the dial key or long press and then the dial key? They slap a name (Direct Dial) on holding the phone to your ear instead and people are awe struck. And what is it going to do if there are four numbers listed for a contact? By the time it asks you which one you want and to confirm pressing the dial key would have been faster.
I'm curious to see what kind of battery life the phone gets. Keeping all these sensors active 24/7 waiting to detect movement or watch you blink has to take a toll on battery life. That and S-Voice constantly listening in case you say something.
Don't get me wrong, some of the soft features their introducing are cool; but they're not life changing (to me). I had Vlingo and it was neat but I never used it and activating the listen feature just killed the battery in the i9100.
Having extensive experience with both phone watches and BT-enabled watches, I want to make an important remark to firmware/software developers for these devices, more so after having recently acquired a SONY Smartwatch.
It is simple: NOTIFICATIONS NEED TO BE PUSHED ALL THE WAY. ALL GOODS NEED TO BE DELIVERED.
In the Sony Smartwatch, a vibration accompanied by a Gmail logo is useless. Having me awake the watch, click on ‘Events’, click again on the message and only then being able to see the email message defeats the purpose of immediateness. Probably easier for me to reach out to the phone and see what the notification is about.
The right way to go is simple: everything the phone has in terms of message info needs to be pushed to the watch notification:
“Email from John Doe
To [email protected]
Subject: Dinner on Tue
->And the entire body”
Same with SMS, IM notifications, or anything. Having only the SMS or Gmail or Whatsapp logos and have to hunt down for the message in the watch is absurd.
The way the MBW-150 worked offered way more info at a glance; Sony is moving backward with this minimalistic notification approach. More is needed.
Secondly: let me disable BT on the watch (say when batt is low or overnight) without forcing me to shut down the device -> no time telling anymore.
Third: watch brightness needs to be adjustable from the watch itself (let me manage battery life myself, I’m a grown up).
Fourth: an audio beep won’t kill anyone. When I’m driving, for instance, I cannot feel the phone vibration. A CASIO-style ‘beep-beep’ cannot hurt. While I understand this may involve additional hardware and pose operational complexities, this is a nice-to-have feature.
First two remarks are KEY, and I’d appreciate not only Sony but everybody involved in such development to think a bit smart before pouring a fortune into development.
Anyone has anything else worth highlighting?
Thanks
Sure dude. But first things first... I would scream that let these things display the clock at all times. Failure to do so defeats the whole watch disguise!
Sent from my GT-N7000 using xda premium
Which app are you using to get Gmail notifications?
jairmoreno said:
Which app are you using to get Gmail notifications?
Click to expand...
Click to collapse
I am messing with Customnotifier, GMail notifier (not 2), and RSS (which works best but drains the battery on the phone if set to frequent checks).
In any event, on the watch I only get an icon on the screen, no further info.
Rgds
Well they are moving in the right direction. With the updated firmware, that was released today, you are able to do a couple more things. You now have an option of leaving new watch faces on at all times. Also with notifications, you can now single tap the new notification icon and it will take you straight to the notification!
gtdRR said:
Well they are moving in the right direction. With the updated firmware, that was released today, you are able to do a couple more things. You now have an option of leaving new watch faces on at all times. Also with notifications, you can now single tap the new notification icon and it will take you straight to the notification!
Click to expand...
Click to collapse
Yes indeed. Touchscreen seems a tad more responsive now also, more polished.
Still, notifications need to appear spontaneously -no need to tap- and bightness should be adjustable -too much backlight for me; always staying indoors.
But it's a good step fwd and the app in the phone is more efficient.
Hi, I'm Considering buying this watch simply cos I'm a geek I guess, but, if it is possible for sony to update the firmware/create new apps, and others also to create new apps etc, isn't it almost inevitable that more detailed notifications will be developed eventually? Or am I wrong, is it up to just sony to develope new apps etc, meaning we'll have to wait for just them to decide, taking ages etc? (Unlinke the wimm one for example)..
It does look great, but I agree, notifications really MUST include details, and if this is a future possibility, then I'll get one. (Mainly due to the wimm one not being on sale over here yet! Arrghh!)
jmpcrx said:
Hi, I'm Considering buying this watch simply cos I'm a geek I guess, but, if it is possible for sony to update the firmware/create new apps, and others also to create new apps etc, isn't it almost inevitable that more detailed notifications will be developed eventually? Or am I wrong, is it up to just sony to develope new apps etc, meaning we'll have to wait for just them to decide, taking ages etc? (Unlinke the wimm one for example)..
It does look great, but I agree, notifications really MUST include details, and if this is a future possibility, then I'll get one. (Mainly due to the wimm one not being on sale over here yet! Arrghh!)
Click to expand...
Click to collapse
The notifications seem detailed to me I mean you see the icon if you want to read the message tap the icon once. I like the screen always on update but I won't use it often since I rather have the battery last through the week.
I've checked back ever so often and there new apps popping up so I think development will only improve. Its honestly one of my favorite phone accessories I would recommend trying it out.
general forceps said:
Yes indeed. Touchscreen seems a tad more responsive now also, more polished.
Still, notifications need to appear spontaneously -no need to tap- and bightness should be adjustable -too much backlight for me; always staying indoors.
But it's a good step fwd and the app in the phone is more efficient.
Click to expand...
Click to collapse
I agree I can't wait til they update to allow adjustment of of the backlight. The notifications I find using the MMS notifier over Sony's I get no delay in the notifications. The Gmail notifier app I use for Gmail sends me the notice without delay also.
Have you looked at the Metawatch at all? That ended up being my choice. Waiting for delivery.
RedRamage said:
Have you looked at the Metawatch at all? That ended up being my choice. Waiting for delivery.
Click to expand...
Click to collapse
Good choice RedRamage. I have the analog Metawatch and expect the new iOS digital version any day. Latest phone console release and functions here
OP - fullly agree with the "at a glance" concept. Metawatch provided this for me and I have the Sony, WIMM, original Liveview and MotoACTV also.
Only very recently I was able to stop using MetaWatch and switch to the Sony only for this. See my blog @ augmentedtraffic.wordpress.com/2012/06/09/finally-true-real-time-at-a-glance-notifications-on-sony-smart-watch (you need to cut & paste into a browser since I have < 10 posts).
I use Tasker/K-9 combined with my app to get "at a glance' on a SonyWatch!
I am still testing battery life, but it seems OK. I haven't put the app on the market as yet as it is very customized to my use cases and it may be a bit too much for others to use. The only thing I am currently missing from the MetaWatch is the next upcoming appointment. I have everything else I was using (notifications at a glance, phone battery life, location, weather). I even added my last Withings scale weigh-in
Ok, I've got both of the 1st Gen MetaWatch models (The bt2 Analog and Digital ones), and maintain a popular fork of the Android MW software (see link in my sig), so I'll try and answer your points in relation to that watch.
1) Yes, MW will display your notifications as soon as the phone does - gmail is a little tricky as google keeps changing/modifying/revoking permissions with the official gmail app, so the information available to the watch manager app can be a little sketchy. If you use k-9 mail, you'll see the sender and subject. It doesn't display body text yet, but that is doable. Gmail would also be fixable by just making the app go to the gmail server directly and pull the message text when the new mail notification comes in.
The fork I maintain has an "Other notifications" Option, that lets you selectively display any android notification, although the OS limits how much information we can actually pull. If anyone has requests for additional notification support, then I'm happy to try adding it, assuming the developer of the app has provided intents or an api to access that information.
Currently notifications will stay on screen for a few seconds, then disappear (except for the SMS notifications, which, on the digital watch can be set to stay on screen until dismissed, as you can see the full body, and scroll) - On the digital watch you can configure a button to redisplay the last notification again if you missed it, and there's an on watch menu of all the previous notifications which is only a few button presses away.
2) Yes, all the MW models have a menu option (on the watch) that let you disable BT without turning off the watch, so you can still tell the time
3) Yes, the Analog MW model has menu options to configure the OLED brightness. There's nothing to configure on the Digital model, as it has an always on LCD screen (though there's an option in my fork of the app to automatically turn on its light when a notification comes in)
4) The MWs don't have a speaker, but they do have a powerful vibrator inside - it's pretty hard to miss it when it does vibrate, and the app lets you configure different vibration patterns for different notifications, so you can know what sort of message it was without even looking.
Let me know if you've got any other questions!
MW has some very good stuff, I'm quite familiar with it.
Pity -both for MW and SW- is the poor pixel density. I believe MOTO has a much better display.
B/W displays appear sub-optimal to me and definitely not the direction the market wants to move toward.
Also, beyond the immediate 'at-a-glance' notification, can you read within the watch the full email or notification in MW? This is also a key element.
One more topic I missed on SW is that once connection is lost we need not only vibration but some on-screen display, like a warning sign or something. This feature prevented me from leaving behind a SGSII in a bar when I was using my ancient MBW-150. Vibration won't typically suffice.
I survive 2.5 full days with heavy notification traffic with my SW. How long you stay unplugged with MW under heavy traffic?
Thanks for the good discussion.
general forceps said:
Also, beyond the immediate 'at-a-glance' notification, can you read within the watch the full email or notification in MW? This is also a key element.
Click to expand...
Click to collapse
As I said, the current software doesn't support that, but it's something I'm planning on adding.
SMS messages currently support this - you can page through a long message, then dismiss it when you're done, so I just need to add the code to pull out (and strip html from) the body text - I know for certain that it's easily possible using k-9 mail, gmail will probably need work to talk to google's mail server directly to get the message text.
general forceps said:
One more topic I missed on SW is that once connection is lost we need not only vibration but some on-screen display, like a warning sign or something. This feature prevented me from leaving behind a SGSII in a bar when I was using my ancient MBW-150. Vibration won't typically suffice.
Click to expand...
Click to collapse
Yes, it'll display a "No watch connection" icon in the top right of the time display, which is pretty hard to miss!
general forceps said:
I survive 2.5 full days with heavy notification traffic with my SW. How long you stay unplugged with MW under heavy traffic?
Click to expand...
Click to collapse
I tend to get 2 or 3 days, depending on what I'm doing - 3 days for medium traffic, 2 for heavy traffic (usually when I'm developing features, so pushing lots of data to the watch)
3 days = Taken off the charger on Monday morning, needs to go back on the charger Wednesday evening before I go to bed.
I could probably get much longer battery life if I manually turned bt off each night, and back in the morning, but I like having my watch vibrate in the morning when the alarm goes off! Perhaps adding a "bt sleep" mode to the firmware would be a good addition.
How long does your battery last on the Sony Smartwatch if you keep the small digital clock on at all times?
I've had my watch a little over a week and haven't been able to make it through the day yet even with minimal notifications. The battery life has been very disappointing.
@benjymous:
I forgot to note that I shut it down when I go to sleep. In the morning I turn it on with no pairing issues, so we'd be looking at 18h/day actual uptime, for a total of say 45h per charge. Not stellar by any means.
@tjrhine:
It didn't even cross my mind to have the screen on full-time. It is obvious you won't make it tremendously far (I think the bat has a capacity below 130). No way. I push the button to get the time, I can live with this.
I also need to report that the glass is far from scratchproof. That's something that really pisses people off. Next HW release should DEFINITELY include at least Gorilla Glass and certainly a bigger battery. The thickness of the plastic clip and the strap can be each reduced by about half a millimeter that combined gives you 1mm that they should invest in a bigger capacity batt.
And obviously, a standard usb port.
Please keep ideas coming folks, thanks.
And this is how the notification queue should look like:
http://www.slashphone.com/media/data/767/inPulse_SmartWatch-2.jpg
I'm having exact same problem - Battery lasts barely 8-10 hrs. Do we need replacement watches?
general forceps said:
And this is how the notification queue should look like:
w ww.slashphone. com/media/data/767/inPulse_SmartWatch-2.jpg
Click to expand...
Click to collapse
Looks like chinese product
[Update March 5th 2014]
Probably all 2014 Note 10.1's sold these past few months are suffering from one or more multitouch issues. From what we now know these appear to be software issues, effecting all current firmware versions for this device.
There are 2 known manifestations of this bug (or more likely: these bugs), described below. In both cases it seems to be a software issue because normally the 2014 Note 10.1 will work fine and the process of re-creating the issues is very clear and repeatable.
It looks like the multitouch driver becomes unstable if either one of the following occurs:
1. (Some models) You place (a part of) your hand on the screen for (at least) 5 seconds without moving it. This would usually happen when you are writing or drawing with the S-Pen.
2. (All models?) You place a finger (or several) on the screen for a longer time (close to 30 seconds) without moving it (them).
After either of these situations a 'defective unit' will show very erratic multitouch behaviour for a while.
It is easiest to see what happens if you use a so-called "Multitouch testing tool" (available Free on the Play Store). Such a tool typically shows all the screen areas where screen touches are detected by the device (in this case: the 2014 Note 10.1). Examples of such tools are: MultiTouch Test, MultiTouch Tester and YAMTT.
Erratic behaviour will usually start with all screen touches suddenly disappearing, meaning the device forgets that you have fingers (or part of your hand) on the screen. If you remove fingers (your hand) from the screen and again touch the screen several times a whole range of behaviour is seen: touches are detected and erroneously forgotten in quick succession. Sometimes so-called ghost-touches appear (meaning, the device will detect touches not anywhere close to where you are actually touching the screen).
This erratic behaviour will usually disappear when you leave the screen alone for a while, although several people (including me) have reported longer running issues (for instance during typing and editing using an on-screen keyboard). A surefire way to get rid of the issues is rebooting your device.
Since this is a "Note" device many people who's 2014 Note 10.1 suffers from these multitouch issues will encounter it while (or after!!) using the S-Pen. Others will notice issues while gaming or during typing/ editing.
The following clip by Kizune shows an example of what can happen while being inside a Multitouch testing app:
More videos you can find below (in post #16) and in the SwiftKey not working well on 2014 Note 10.1 topic, where the roots for starting this topic sprout from.
As of yet Samsung appears to be unaware of these issues, although several have approached them about this, returned their Note tablet, exchanged it or even handed one in for repairs. Hopefully we get this fixed soon.
Note 1: from early reports (in post #83) it looks like the new Note Pro 12.2 doesn't suffer from these issues.
Note 2: It is possible that a build up of static charge (through capacitance) is causing these issues, possibly caused by bad wiring (grounding) of the touch/ S-Pen detection circuitry.
Note 3: A new video has surfaced (in post #89) which shows 'noise' introduced in the touch-detection software while pinching/ zooming (see video below). It is unclear if this is related to the issues mentioned above.
i noticed this using the stock kb. i'm not a particulary fast typist on the screen but i'd get far too many lack of responses when typing on the split kb. standard qwerty was fine, but that have been b/c i'd type slower. i'm able to hit keys quicker on my gn8 without any misregistering of keystokes.
the fact there has been to OTA's in just a week is a sign they let this one out before it was ready. i still love the tablet though.
It happens to me too just like you see in the youtube video.
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it.
Click to expand...
Click to collapse
Did you try the "whole hand" thing too? It would be super if Samsung solved things that quickly, but I feel a little aprehensive. We didn't get the recent updates yet in my area so I cannot see for myself.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
Click to expand...
Click to collapse
no, I took both OTA's Just before rooting.
wingdo said:
Just tried YAMTT and I am luckily not showing the issue seen in the video. Perhaps the second OTA solved it?
Sent from my Galaxy Note 10.1 via Tapatalk.
Click to expand...
Click to collapse
Same here. I tried a couple touch apps and all were fine. The YAMTT app just seemed buggy at times. but I could not replicate what the video showed on any of the apps and do not have problems in real world applications either.
atg284 said:
Same here. I tried a couple touch apps and all were fine. The YAMTT app just seemed buggy at times. but I could not replicate what the video showed on any of the apps and do not have problems in real world applications either.
Click to expand...
Click to collapse
Did you try the "whole hand" procedure too?
---
I changed the opening post because I feel many will be tempted to just try the youtube clip and not bother reading anything else. Hopefully we won't have too many people voting before properly taking all steps because you cannot change your vote once you voted (an xda forum limitation).
Ettepetje said:
Did you try the "whole hand" procedure too?
---
I changed the opening post because I feel many will be tempted to just try the youtube clip and not bother reading anything else. Hopefully we won't have too many people voting before properly taking all steps because you cannot change your vote once you voted (an xda forum limitation).
Click to expand...
Click to collapse
I did what the person was doing in the video and could not replicate what was happening on his. I also placed my whole had on it and put all ten fingers on it. No bugs. I am on the second update. Build number ending in AMJ4
Edit: the YAMTT app seems buggy because the other touch apps don't go crazy when all ten fingers on on it. But I could not replicate what YAMTT app was doing to the one in the video.
atg284 said:
I did what the person was doing in the video and could not replicate what was happening on his. I also placed my whole had on it and put all ten fingers on it. No bugs. I am on the second update. Build number ending in AMJ4
Click to expand...
Click to collapse
Did you place your whole hand on the screen of the 2014 Note 10.1 for several seconds, without moving it? Did you put your fingers on the screen afterwards? The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Edit: The YAMTT app is not important, puting your hand for several sevonds on the scyeen IS. This creates what goes on afterwards. You can repeat it in any of the Multitouch testing apps, just place your hand (or part of it) on the screen for a while and see in the MT app what happens.
Ettepetje said:
Did you place your whole hand on the screen of the 2014 Note 10.1 for several seconds, without moving it? Did you put your fingers on the screen afterwards? The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Edit: The YAMTT app is not important, puting your hand for several sevonds on the scyeen IS. This creates what goes on afterwards. You can repeat it in any of the Multitouch testing apps, just place your hand (or part of it) on the screen for a while and see in the MT app what happens.
Click to expand...
Click to collapse
Ok, I see. So when I put my whole hand/palm on it for 2-5 seconds then I try to put all ten it starts to "wig out" a bit but it still registers all ten its just sporatic. Also it seems to only have a problem with like 7 or more after because I can put many fingers on it before it wigs out. I still don't see a real world issue on mine even after I do the full hand thing.
Side note once I exit out the app the ten fingers on it are fine again.
What problems are people seeing due to this?
atg284 said:
Ok, I see. So when I put my whole hand/palm on it for 2-5 seconds then I try to put all ten it starts to "wig out" a bit but it still registers all ten its just sporatic. Also it seems to only have a problem with like 7 or more after because I can put many fingers on it before it wigs out. I still don't see a real world issue on mine even after I do the full hand thing.
Side note once I exit out the app the ten fingers on it are fine again.
What problems are people seeing due to this?
Click to expand...
Click to collapse
As far as I am aware the problem doesn't disappear as simple as that. It would be great if there was a way to get rid of it without rebooting.
You could get any type of interface problem afterwards, as even one finger touch can give ghost finger touches. I noticed things being wrong in SwiftKey before finding out what it was.
Ettepetje said:
As far as I am aware the problem doesn't disappear as simple as that. It would be great if there was a way to get rid of it without rebooting.
You could get any type of interface problem afterwards, as even one finger touch can give ghost finger touches. I noticed things being wrong in SwiftKey before finding out what it was.
Click to expand...
Click to collapse
Oh I don't have that at all. no ghost finger touches ever. I have not rebooted over the period of testing either today. Are you fully updated?
I will keep checking this over time though.
Ettepetje said:
The video is not meant for reproducing the bug, the written procedure is. The video just shows what happens when you write, as the bug has already be introduced before the start of the clip.
Click to expand...
Click to collapse
Well, actually the method shown in the video is the "previous version" of the current one. I could produce the bug with that method very often right after booting. But the "whole hand" method is more reliable.
What problems are people seeing due to this?
Click to expand...
Click to collapse
1. When taking notes at the university, I sometimes move the viewport in S Note using the zoom gesture without the zooming motion. And as you can see, putting my hand on the screen as shown in the video triggers the problem for me, so doing that gesture is almost impossible for me. I know there are scrollbars, but they move the viewport too slowly (but of course I use them when I notice the multitouch issues are occurring).
2. Same as above, but when drawing in Sketchbook or ArtFlow. And here it's extremely annoying because there are no scrollbars I could use.
3. A small annoyance compared to the others but: When I play Carmageddon, the multitouch issues get triggered once in a while. And then I can only either control the car, or accelerate or break, but not both simultaneously. Sometimes my touches aren't even registered at all. I often get destroyed due to the multitouch issues.
Kizune said:
Well, actually the method shown in the video is the "previous version" of the current one. I could produce the bug with that method very often right after booting. But the "whole hand" method is more reliable.
Click to expand...
Click to collapse
I changed the description in the opening post. I never had it happen like that yet. Did you know you get the errors just by holding the side of your hand on the screen for a bit? I thought that was how you discovered this. Doing that looks very similar to how you are holding your hand in the videoclip.
Did you find another way to get rid of the issues besides resetting your Note?
Btw: With Carmageddon, if you are high enough level and want to kill pedestrians, not having control means your opponents die crashing into you, ending the race before you finish all pedestrians.
Ettepetje said:
Did you know you get the errors just by holding the side of your hand on the screen for a bit? I thought that was how you discovered this. Doing that looks very similar to how you are holding your hand in the videoclip.
Click to expand...
Click to collapse
Exactly, I noticed it while taking notes. And then I made this my test method to replicate the error.
Anyway, here are some videos. The first shows a real-life situation in S Note with that problem, the second and third show that the problem also occurs in other multitouch test apps (yes, I'm looking at you, atg284 ).
And to make it more "real-world friendly", I used my old "provocation method" because that's how you put your hand on the screen while drawing and writing.
Btw: With Carmageddon, if you are high enough level and want to kill pedestrians, not having control means your opponents die crashing into you, ending the race before you finish all pedestrians.
Click to expand...
Click to collapse
Yup. And I even got that tank-like bonus police car, so they die just by touching my car tank.
I do stand corrected I can reproduce this issue on the new Note, old Note is fine and dandy.
Sent from my Galaxy Note 10.1 via Tapatalk.
wingdo said:
I do stand corrected I can reproduce this issue on the new Note, old Note is fine and dandy.
Click to expand...
Click to collapse
Did it take longer to get the erratic behavior like you said in pm? I'm trying to get the description in the opening post right, since we got 4 people now who claim they don't have it. I think the score should be 100%, and just included the Poll so that people at Samsung would quickly realise how big the impact is.
I can duplicate this.. just didn't figure how to repeat consistently until now..
First noticed when trying to pinch zoom in adobe reader .. you get very jerky redraw back and forth.. this could be app specific , but i haven't seen this on other devices
Sent from my SM-P600 using xda app-developers app
I'm also experiencing this. It's a terrible issue when taking notes in class.
Can we expect a fix?
Hello,
I am relatively new in the Samsung world. Currently, I own a S20U 5G phone, with latest Android (G988BXXU6DUB5)
I have several questions, just put them in a list not to create a lot of threads. I would be really grateful if you could share advice/your experience.
I've noticed some clicking sound when I exit my Camera app and also when I open Settings for this app inside of it. Is it ok? I bet it is somehow related to the lens.
I've also read some articles regarding the autofocus issues. Are those solved? For me it seems to work decently fine, but I am not sure what are the best settings, should I keep tracking autofocus turned of or on.
Also, I've noticed that if I do some AF test with bringing hand relatively close (20cm), and on the background there are some objects contrasting with the background, some grey squares are popping around them and focus seems to be jumping to them randomly. Did anyone notice the same thing? What are those grey squares?
The battery. My SoT is around 4.5-6hrs, on LTE mostly with some calls, a lot of FB and messenger. I've noticed that the battery likes to drop quickly from 100%. Like if after I start using it on 100%, it could drop to 97% during 10-15 minutes of active usage. Then it is going slower, in a normal pace. Is you experience similar?
Thanks in advance for sharing your experiences.
Sorry if questions seem newbie ones, I just need some advice.
1. Yes it's just the camera sensors locking AF
2. AF was vastly improved with updates, there seems to be no issue with it now
3. Grey squares are usually the camera AI trying to find faces to focus on, so anything that might look a bit like a face to the AI it will try locking onto
4. Normal for Samsung devices to lose a few % very quickly, and your SOT time is fine
*Detection* said:
3. Grey squares are usually the camera AI trying to find faces to focus on, so anything that might look a bit like a face to the AI it will try locking onto
Click to expand...
Click to collapse
Hello, thanks for your answers, it is much clearer now.
I've noticed an odd thing about this specific feature, for example, if my child is moving, it tries to lock onto face with a grey square and if I start shooting, often I get a message "this photo might be blurred" or similar, and it is indeed blurred. Maybe you know how to combat this, if possible? Maybe some specific camera settings?
jdx111 said:
Hello, thanks for your answers, it is much clearer now.
I've noticed an odd thing about this specific feature, for example, if my child is moving, it tries to lock onto face with a grey square and if I start shooting, often I get a message "this photo might be blurred" or similar, and it is indeed blurred. Maybe you know how to combat this, if possible? Maybe some specific camera settings?
Click to expand...
Click to collapse
For moving subjects it's best to use Pro camera mode (Tap the "More" button under the view finder > Pro Mode
Set the shutter speed low as possible while still allowing enough light in, you can raise the ISO to get more light without increasing shutter speed (At the expense of noise depending how high you set it), that way you get a lot less blurring on the moving subject, in this case your child
The blurring occurs if the subject moves while the shutter is open collecting light, so the less time it is open, the less distance the subject will have moved, thus less blur
Works best in good light such as sunlight, then you don't need ISO too high and can drop shutter time right down while still getting good exposure
There is also a setting for Auto camera mode in the camera's main settings called "Tracking Auto-focus" which once you tap the screen to focus on a subject, regardless of where it moves to, it should remain in focus