I've used the AT&T GSII and remember that there was a little lag from when I press the home button to when it would actually take me home. There was alot of people on the forum that experimented the same thing, but there was eventually a fix for it.
Even though I haven't seen anyone reporting that issue in the Note's forum, does anyone here that owns the device experience the lag?
No, there is no lag on the device at all, silky smooth.
I'm the owner of one and it's buttery smooth, just watch out for apps that could cause lag or instability.
Users complaining about lag/slowdowns is usually down to a bad app.
Yes, sometimes there's a 1-2 sec delay, usually when the phone's been in deep sleep for a while. No different from the SGS2 and doesn't bother me anyways.
No doubt someone will introduce the same delay fix (which boils down to disabling double-tap Home for Voice Talk).
WillEat4F00d said:
I've used the AT&T GSII and remember that there was a little lag from when I press the home button to when it would actually take me home. There was alot of people on the forum that experimented the same thing, but there was eventually a fix for it.
Even though I haven't seen anyone reporting that issue in the Note's forum, does anyone here that owns the device experience the lag?
Click to expand...
Click to collapse
Yes. Same home screen delay exists. It's probably due to voice commands app. After you press the home button, it waits to check whether you press it again to launch the app. Only when it doesn't receive the second press in the given time frame, it takes you home.
That said, I guess they have reduced the time delay permissible between two taps, so it doesn't delay as much as the sgsii.
I've noticed this...
That bothered me on the GSII and somewhat bothers me on the Note. Anybody have a link for the discussion on fixing it on the GSII?
Related
Hello!
I have been having a small issue with the touchscreen. This all started when I noticed I could type faster on my iPod touch than I can on my Incredible (no, not another Apple fanboy lol). So I started to look into what was causing this. Quite quickly I noticed that some keyboard presses did not register, but I saw the icon pop up (to show which key I was pressing)! This only happened if I typed fast... so then I started to look deeper into why the icon popped up but it didn't type the key. I figured out that if you touch two points too quickly, the screen registers it as a "drag" event. As a side note, I've been using Smart Keyboard Pro for it's multitouch capability. I've tested this by tapping twice quickly in Swype, and sure enough, it drew a line between two keys.
Has anyone else experienced anything like this?
Thanks,
x.v_
I made a video to demonstrate what I'm talking about!
http://www.youtube.com/watch?v=fsln2yas1p0
Someone reply? >.<
100 views + 40 YT views
it has nothing to do with multitouch. do the same thing but hold a finger on a and a finger on l at the same time, then let go of a and the same thing happens. you're just touching it fast enough that that's how it's registering. it's not the screen, it's the apps. swype isn't multitouch so that's what happens when you try.
it has nothing to do with multitouch. do the same thing but hold a finger on a and a finger on l at the same time, then let go of a and the same thing happens. you're just touching it fast enough that that's how it's registering. it's not the screen, it's the apps. swype isn't multitouch so that's what happens when you try.
Click to expand...
Click to collapse
...I didn't say it had to do with multitouch? It is a global problem, not just apparent in some apps. This seems to be a bug in how the phone handles two points being touched too quickly. This should not happen.
Sent from my ADR6300 using Tapatalk
Is anyone else having issues with the back & search keys at the bottom being unresponsive? We have 2x epics and both appear to have this issue.
back button working good here. havent used the search button more than 3 times since i got the phone.
This appears to be a fairly common issue. A lot of people are saying they have issues with different buttons. My home button is the least responsive.
I have to mash the "button" area considerably to get a response - perhaps it waits for a certain amount of capacitive load/change before activating. That would help reduce unwanted taps when swiping across the screen - the Evo was wonderfully sensitive, but an overzealous scroll often had the unintentional side-effect of bringing you back home or backing you out. Also, the Evo, for me, constantly brought up the search dialog if the edge of my hand came too close. So, I suppose it's a tradeoff.
APOLAUF said:
I have to mash the "button" area considerably to get a response - perhaps it waits for a certain amount of capacitive load/change before activating. That would help reduce unwanted taps when swiping across the screen - the Evo was wonderfully sensitive, but an overzealous scroll often had the unintentional side-effect of bringing you back home or backing you out. Also, the Evo, for me, constantly brought up the search dialog if the edge of my hand came too close. So, I suppose it's a tradeoff.
Click to expand...
Click to collapse
This isn't true. My Epic capacitive buttons respond to a very light tap and also a full on *press*.
sounds like non-functioning buttons to me.
You might have a bad sensor on your buttons.
I did have to get used to them. The Evo's were very sensitive, in fact in landscape I'd often accidentally brush one and it was a little annoying.
The epic does seem to need just a half second or so longer for the tap to be recognized.
Aridon said:
You might have a bad sensor on your buttons.
I did have to get used to them. The Evo's were very sensitive, in fact in landscape I'd often accidentally brush one and it was a little annoying.
The epic does seem to need just a half second or so longer for the tap to be recognized.
Click to expand...
Click to collapse
thats more annoying. It makes the phone feel laggy, atleast to me it does. All the my buttons require 2-5 touches before they register
bobdude5 said:
thats more annoying. It makes the phone feel laggy, atleast to me it does. All the my buttons require 2-5 touches before they register
Click to expand...
Click to collapse
I'm not getting that at all. You might want to bring it back and swap it. It takes slightly longer than the evo to register but it feels "about right" to me. When I want to hit it, I have no problem hitting it.
I went to the Sprint store yesterday. The guy told me the early phones had this issue. I asked to try out the one he was giving me. He said, he'll be back and need to take it to the tech for setup and "an update"?...huh, already?
Anyways, he came back and I tried out ALL the buttons. A VERY lite tap and it responds...all of them...
I had a poll going before, and it looked like the issue was relatively wide spread... Apparently though, some phones do not have this problem. If you get this, swap out your phone, it is likely defective.
BTW, the poll is at
http://forum.xda-developers.com/showthread.php?t=772063
I think part of the issue is that the buttons' sensitivity region is slightly below the button icons. If you tap above the buttons, they dont respond. Tap slightly below them, however, and they should respond every time... Unfortunately, this makes most cases for the epic 4g pretty terrible since you cant really press below the menu and search keys... Of course I could be wrong.
Sometimes the Galaxy S II seems to have a slight delay when waking it by pressing the Home or Power button.
I saw a Thread about it in a german Phone forum where a lot of people reported this. I myself noticed it too. I'm running KE2 with Widgetlocker. I can disable Widgetlocker, it still happens.
If you wake it just after locking, it will be instant. If you wait a couple of seconds you will get a delay when waking the device. But it doesn't behave the same all the time, sometimes it's even instantly when waiting for a few minutes.
Can you guys confirm this?
yeah same problem here. I thought the latest update had fixed it but it still seems to be there
Oh and something other that I noticed, while having the phone connected to my pc, it always wakes up instantly.
prob coz its clock the CPU down while screen is off.
domazdk said:
prob coz its clock the CPU down while screen is off.
Click to expand...
Click to collapse
Either that or its the power management when its not being charged.
My lg 2x do not have this delay, should be able to fix in a kernel mod
DocRambone said:
My lg 2x do not have this delay, should be able to fix in a kernel mod
Click to expand...
Click to collapse
Great to hear that! I didn't have this either on my Desire and it was clocked down to 200Mhz...
Oh and another thing, can you disable the double Home button press? Because if you press it 1 time you are getting a slight delay because it has to wait if there will be a second press. I don't need the double-press voice Feature.
Hey. 1st post. Been reading for a while, but the wake issue annoyed me too, so I tried WidgetLocker with not much change. PowerAmp's lock widget seems to make it faster, but I found if you lower the res of the wallpaper on your lock screen, the waking is instant, which I recently realised.
I go to interfacelift.com and choose a wallpaper at 1400x900 (or so. Usually a good one for the actual background, so it doesnt really matter much for the lockscreen) save it and open to allow you to change the lock screen wallpaper. It does mean it won't be the nicest image, but it's made my phone waking sooooo much faster.
Cheers
Thanks for that, it appears to work.
http://forum.xda-developers.com/showthread.php?t=1095371
have you tried this?
I have tried copying over the modified framework and a low resolution (800x480) solid black wallpaper but no luck.
This is starting to agitate me to be honest. I’ve been telling the guy opposite me at work that S2 is the best phone available at the moment for a couple of weeks now. He ignored me and brought the sensation.
Now he has a phone that switches on immediately when he presses the power, immediately switches to his home screen when he presses the home button and his battery is lasting twice as long as mine.
Don’t get me wrong, I’d still rather have the S2. But as the new toy feeling starts to where off the little things are starting to bother me.
i have the same issue.
Well, i had the same lag at power on.
what i did :
1 change wall paper to a standard one, in the samsung gallery wallpaper. Chose one screen WP... ans applied it to both on lock and screen wallpaper
test, switch it of and on.... No lag
I applied back my large customized wallpaper i had before and applied on screen, didn't touch lock screen cause i use Widgetlock...
Now, no more lag....
It's not a cpu sleep issue, just a bug in lock screen wallpaper in my opinion....
Thanks for the suggestions Cuspide but it didn't help me unfortunatley. I even brought widgetlocker in case it was that.
It is true, it may be a minor problem but it is so annoying.
When using my HD2 with Windows Mobile, the wake up was instant, in fact even with Latitude, Email and Facebook syncs, the battery life was fantastic. HD2 with Android obviously reduced battery life and there was the wake up lag - I thought all these niggles would go with an 'actual' Android phone, but it doesn't seem that way...
I have tried the following with no luck;
- modified framework and CRT animation
- installing SetCPU and putting the governor to performance (and min 1200Mhz)
- setting a lower resolution lockscreen picture (800x480)
I'm hoping it is only software related, and something Samsung will fix very soon.
I believe that it is a mere software issue.
My Desire clocks down to 245Mhz when it's sleeping. And it wakes instantly and clocks back up to 998Mhz. The change is completely unnoticeable.
And the GSII with 1.2Ghz and 1GB of RAM - hopefully this will be fixed in a future update.
This seems to just be a kernel sleep issue.
I would imagine it's fixable in a kernel update.
I've noticed that the delay isn't apparent when the phone is on AC power. Plug your charger in and wake the phone up and it's instant, take it off charge and wake it up and there's the delay again.
it's the sleep policy. open an IM like ebuddy (it voids device to get in sleep policy) and no delay at all
update
hi Guys
has anyone found a way around this. The wakeup delay is very annoying..........
Just bought a S4 and some how I don't think the home hardware button is working as it should. I have to press it really well for it to work (same usual laggyness since I haven't yet disabled S-voice double tap). When I do press it, it doesn't sink in or rise up again like buttons should. I have real trouble figuring out if I did press it or not.
Is this a manufacturer's defect and should I return it? It might be because I have the newest 19506 variant (with 2.3GHz Quad core and CAT 4)
If its not too much trouble, may I ask someone to please upload a video either on here or on youtube demonstrating on a macro close up how far the home button should depress and rise and a general comment on how it feels? (I live kinda far away from a phone shop)
Thanks
den10 said:
Just bought a S4 and some how I don't think the home hardware button is working as it should. I have to press it really well for it to work (same usual laggyness since I haven't yet disabled S-voice double tap). When I do press it, it doesn't sink in or rise up again like buttons should. I have real trouble figuring out if I did press it or not.
Is this a manufacturer's defect and should I return it? It might be because I have the newest 19506 variant (with 2.3GHz Quad core and CAT 4)
If its not too much trouble, may I ask someone to please upload a video either on here or on youtube demonstrating on a macro close up how far the home button should depress and rise and a general comment on how it feels? (I live kinda far away from a phone shop)
Thanks
Click to expand...
Click to collapse
never had that problem, samsung s4's home button is usually snappy and responsive. im afraid i cant help with the video uploading for you but im 50% sure you have a defective samsung key.
keedier said:
never had that problem, samsung s4's home button is usually snappy and responsive. im afraid i cant help with the video uploading for you but im 50% sure you have a defective samsung key.
Click to expand...
Click to collapse
Well, I've posted a video online showcasing my problem
https://www.youtube.com/watch?v=3LNulcKnELM
Could anyone please advise me further on this? Would this be a valid reason to return the phone?
I don't expect there's much that can be done if the hardware is to blame. This reminds me of my Galaxy S3 -- so it's a problem that everyone else fixed ages ago. When I touch the touchscreen, very very often, it doesn't register that touch at all. Sometimes you get a delayed response. This leads to all kinds of fun where you tap the screen again at the same moment that PH-1 responds to your first touch, so it applies your second tap to whatever is going to come up on the screen a half second later.
Does anyone know if this can be fixed by firmware updates or is this a hardware issue?
same here! my huawei honor 8 is much faster
Touch Screen unresponsive is a hardware issue. I had the same problem with my HTC U11 until it was replaced. Essential phone does not have this issue assuming screen is working properly.
Sent from my Pixel XL using XDA-Developers Legacy app
Touchscreen responsiveness, having to tap more than once for the screen to register a touch and awful light bleed caused me to send it back. But it was from the first batch that were manufactured. No issues on my U11, but I bought it in early August.
Confirming u installed the most recent OTA (NMI64C)? Because that fixed my touch issues.
flakko86 said:
Confirming u installed the most recent OTA (NMI64C)? Because that fixed my touch issues.
Click to expand...
Click to collapse
Yep that's what I currently have. I think the phone found that update on its own a few days ago. Touch issues seem to be hit or miss and maybe less frequent since that update. We'll see how it goes from here.
touch unresposive is due too thermal trottling or like me the launcher stock.
Solved with Evie launcher
Using a different launcher and such didn't help me out, unfortunately. Besides the tap issues, scrolling through a web page in any browser or with apps was extremely slow and laggy. My PH-1 was already being returned, so I couldn't test the latest software update they pushed out. But my device also had some horrible light bleed all along the left and right edges.
No light bleed here. But [email protected], the responsiveness of this touch screen is worse than any other phone I've had. And the new software update hasn't helped at all!...
Same issue!
I too am having touch screen issues. Today, I was on the phone and went to go back to the screen and the screen stays black. I tried everything including pressing the power button and I got no response from the phone whatsoever. The only thing that finally worked was to press the power button and the volume down button and hold them at the same time to shut my phone off after the call already ended. In addition to that issue , I also use Swipe to type and when I do so it often skips over letters and types words that I am not even trying to type . It should be mentioned that I'm a very experienced swipe user and I have not had this problem with my S7 Edge or my Wellington . Also, I should mention that I have the most recent OTA. Also, has anyone else noticed that the camera shutter has a serious delay in it even with the Google camera mod?
I've noticed my touch screen freaking out sometimes. It has more to do with the screen having too many prints on it. Guess it's a bit too sensitive. I wipe the phone screen off and it's fine. Doesn't happen very often. I have one of the latest batches, pure white.
Already looked into this?
Sensitivity:
1. Tap on the "Settings" icon on the home screen.
2. Tap "Language and Input".
3. Scroll to the very bottom of these settings and tap "Pointer Speed".
4. Increase the slider to make the touch screen more sensitive and easier to tap. Decrease the slider to make your touch screen less sensitive and more difficult to tap.
5. Tap "OK" and then experiment with the results.
Essential Support still working on that and they send me this instructions for now.
I think it makes the user experience better.
Shadow Samurai said:
I've noticed my touch screen freaking out sometimes. It has more to do with the screen having too many prints on it. Guess it's a bit too sensitive. I wipe the phone screen off and it's fine. Doesn't happen very often. I have one of the latest batches, pure white.
Click to expand...
Click to collapse
Same.
Hope it will have a fix soon.
Early on I got the black screen that required a power hold reboot, since moving to Oreo I've not seen that
basongwe said:
Same.
Hope it will have a fix soon.
Click to expand...
Click to collapse
This I have experienced too
edit : solved with oreo beta
basongwe said:
When I touch some letters on my keyboard, it's unresponsive. Same with some apps. I don't know why this phone is so frustrating to use even if it's a very good smartphone.
EDIT : I'm on Nougat's lastest version, not on Oreo beta.
Click to expand...
Click to collapse
Had it on both versions to be honest, but hoping it's getting resolved as time goes on!
Just got mine..same thing but...
My screen was doing fine until i installed "All in one gestures". I was messing around with side gestures and this caused the screen to be non-responsive. I un-installed the app, reinstalled it and set it up differently and now it is fine.
I hope this helps.
D4rk_nVidia said:
Already looked into this?
Sensitivity:
1. Tap on the "Settings" icon on the home screen.
2. Tap "Language and Input".
3. Scroll to the very bottom of these settings and tap "Pointer Speed".
4. Increase the slider to make the touch screen more sensitive and easier to tap. Decrease the slider to make your touch screen less sensitive and more difficult to tap.
5. Tap "OK" and then experiment with the results.
Essential Support still working on that and they send me this instructions for now.
I think it makes the user experience better.
Click to expand...
Click to collapse
This helped me. I have mine set at approximately 3/4 and I'm happy one day in. Seems to work great now. I would still like smoother scrolling though. Thanks a million.
I was also having trouble with Android Pay and then found a post about the NFC being located near the bottom of the phone as opposed to the top as on my Nexus 6p.
With these problems fixed I'm completely pleased with this phone.
ugh! Flashed back to stock on 7.1.1/NMJ32F/436 as that is how my phone came, and now I have no touchscreen after re-boot?!?!?! any advice? Please?
Thanks,
DJ