Sometimes when I'm tapping certain icons at certain times I will have to tap twice becuase the first time it didn't recognize my tap. Sometimes even multiple times. But other times my phone will run as smooth as butter. Hardware or software issue?
Same issues ...
I have the same issues.
This issue occurs often after I unlock my Phone and also during use.
In my opinion that's not acceptable!
How did you act?
Did you send it in?
Pet hate: "Smooth as butter" ARGGHHHHHHHHHHHHH!!!!!!!!!!!!
And relax.
Yes, sometimes it doesn't recognise it. Even sometimes it will actually highlight the icon, so it's recognised I've pressed, but then done nothing with the action.
I would say software issue.
cspius said:
I have the same issues.
This issue occurs often after I unlock my Phone and also during use.
In my opinion that's not acceptable!
How did you act?
Did you send it in?
Click to expand...
Click to collapse
I returned my phone because it was driving me insane.. but yes it's probably a software issue. I bought a Nexus S from google, and it's better, but sometimes it still happens on my NS, however much less often then on my O2X. But i would say just try using a different kernel or rom. CM7 still had the touchscreen issue. So that's why I kind of gave up on this phone.
Scougar said:
Pet hate: "Smooth as butter" ARGGHHHHHHHHHHHHH!!!!!!!!!!!!
And relax.
Yes, sometimes it doesn't recognise it. Even sometimes it will actually highlight the icon, so it's recognised I've pressed, but then done nothing with the action.
I would say software issue.
Click to expand...
Click to collapse
hahaha yeah sorry I don't know why I included the "smooth as butter" cliché. I didn' want to but somehow it just popped into my head. And I'm as relaxed as relaxed can get
I have noticed that o2x screen is not that sensitive. For example in "where is my water " it was difficult to draw lines as precise as on an iphone or gs2. Maybe my fingers are faulty
buluba89 said:
I have noticed that o2x screen is not that sensitive. For example in "where is my water " it was difficult to draw lines as precise as on an iphone or gs2. Maybe my fingers are faulty
Click to expand...
Click to collapse
I agree. I now have a nexus s therefore i think that Samsung>LG.
From the moment I installed RC's ics cm9 I never had touchscreen issues again. On the contrary, now I find the screen too sensitive.
nuvo84 said:
From the moment I installed RC's ics cm9 I never had touchscreen issues again. On the contrary, now I find the screen too sensitive.
Click to expand...
Click to collapse
Screen sensitivity has been fixed in the latest kangs.
Sent from my LG-P990 using xda premium
hisham027 said:
Screen sensitivity has been fixed in the latest kangs.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
I know.
That's funny... I'm still running stock 2.2 on my O2X and I had no trouble triple ducking all levels in where's my water... Now I'm cutting ropes
Hi, i personally dont think this is a problem with our touch screens, i have it happen to me when unlocking the phone etc, but i think its because we try to tap an icon to quickly before we give the phone chance to fully unlock, i've noticed if i wait just a second or 2 after unlocking it doesnt happen, i think its lack of ram in the o2x, it not quite fast enough for our speedy fingers, lol.
---------- Post added at 05:06 PM ---------- Previous post was at 04:43 PM ----------
wayneace8888 said:
Hi, i personally dont think this is a problem with our touch screens, i have it happen to me when unlocking the phone etc, but i think its because we try to tap an icon to quickly before we give the phone chance to fully unlock, i've noticed if i wait just a second or 2 after unlocking it doesnt happen, i think its lack of ram in the o2x, it not quite fast enough for our speedy fingers, lol.
Click to expand...
Click to collapse
Also i forgot to mention, if i turn off all animations this also decreases the chance of this happening.
Related
Ok.. So I searched a while, and I'm not sure if I was just using the wrong terms, but I couldn't get a result that answered my question.
Anywho.. I'm using Fresh Toast 2.0b2, and I'm having an odd problem when playing games that have touch input.
For example... Whilst playing the game "Radiant" The phone slows down considerably when I use the touch screen to move my ship.. I would say framerates cut almost in half.. but clear up as soon as I lift my thumb from the screen..
Same thing happens in the game "Blow Up" When I tap-hold the bottom of the screen to pick up the bombs to drag to the beams, the phone slows WAAAYY down, but clears up the moment I drop the bomb/lift my finger from the screen..
Could this be a ROM problem? Background App Problem? Just one of the quirks of the Hero?
Any input will be seen as valuable.
Thanks,
~jUgGsY~
jUgGsY said:
Ok.. So I searched a while, and I'm not sure if I was just using the wrong terms, but I couldn't get a result that answered my question.
Anywho.. I'm using Fresh Toast 2.0b2, and I'm having an odd problem when playing games that have touch input.
For example... Whilst playing the game "Radiant" The phone slows down considerably when I use the touch screen to move my ship.. I would say framerates cut almost in half.. but clear up as soon as I lift my thumb from the screen..
Same thing happens in the game "Blow Up" When I tap-hold the bottom of the screen to pick up the bombs to drag to the beams, the phone slows WAAAYY down, but clears up the moment I drop the bomb/lift my finger from the screen..
Could this be a ROM problem? Background App Problem? Just one of the quirks of the Hero?
Any input will be seen as valuable.
Thanks,
~jUgGsY~
Click to expand...
Click to collapse
FreshToast is buggy right now - hence the DEV rom titleing.
I also have noticed general touch bugyness. Especially slow responses to touch.
Kcarpenter said:
FreshToast is buggy right now - hence the DEV rom titleing.
I also have noticed general touch bugyness. Especially slow responses to touch.
Click to expand...
Click to collapse
So should it be considered an actual BUG for FT?
jUgGsY said:
Could this be a ROM problem? Background App Problem? Just one of the quirks of the Hero?
Any input will be seen as valuable.
Thanks,
~jUgGsY~
Click to expand...
Click to collapse
Not a ROM problem, Not specific to your device. I feel like its a problem with HTC's multitouch drivers.. Ive noticed the same problem since I got the phone in October. I'm pretty certain when you touch the phone, the Hero is looking for another touch point so it delays the phone.. The HTC Hero doesn't use the same multitouch drivers as other 2.1 devices even on the 2.1 ROMs, Thats why most multitouch programs on the market dont work right for the Hero, and also why I'm jumping to EVO, Hopefully HTC EVO doesn't have the same problem.
mental26 said:
Not a ROM problem, Not specific to your device. I feel like its a problem with HTC's multitouch drivers.. Ive noticed the same problem since I got the phone in October. I'm pretty certain when you touch the phone, the Hero is looking for another touch point so it delays the phone.. The HTC Hero doesn't use the same multitouch drivers as other 2.1 devices even on the 2.1 ROMs, Thats why most multitouch programs on the market dont work right for the Hero, and also why I'm jumping to EVO, Hopefully HTC EVO doesn't have the same problem.
Click to expand...
Click to collapse
That definitely makes sense. Wish I would've known about the EVO previous to my purchase of the Hero..
So I did 2 neocores. One without touching the screen got me 25 dos. Then I touched the screen thru the whole benchmark and got 4.9 dos. Wow that's a big difference!
-------------------------------------
Sent via the XDA Tapatalk App
Kcarpenter said:
So I did 2 neocores. One without touching the screen got me 25 dos. Then I touched the screen thru the whole benchmark and got 4.9 dos. Wow that's a big difference!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
That should be seen as a deal breaking bug for the Hero.. We should all go to Sprint and DEMAND EVOs.
Unless its not present in the official 2.1, I'm going to do what I can to get an EVO.
yeh its really weird how it works right. .27 and touch input didnt play well. at all. the biggest problem is the sh*t digitizer we have. it only senses x OR y moving AWAY OR TOWARDS eachother. it isnt true multtouch. a good example is to download multitouch paint from the demo market. it will read both fingers fine until one crosses the x or y axis in opposite directions.
but anyways back to when you touch, i think toasts source is amazing for the .29 but once htc releases the real .29 source he will really work his magic. .29 fixed alottt of the issues with stuff like music and touch having their own "processes". in .27 they were all bunched together and that made ultra lags while using bt and messing with phone.
This is fixed in Fresh Toast 2.1Final.
I love those two guys.
Hi,
While reading IS review on pocketnow.com I've found them saying that the screen sensitivity on IS is not good. But I'm interested and with others opinions from actual owners of IS. Thanks.
rimvydukas said:
Hi,
While reading IS review on pocketnow.com I've found them saying that the screen sensitivity on IS is not good. But I'm interested and with others opinions from actual owners of IS. Thanks.
Click to expand...
Click to collapse
I think it's very responsive myself. The only problem I've had in that regard is that I have to press down for a split-second before I swipe down to unlock the screen, otherwise it doesn't respond properly - but I've seen this on other Sense-based phones too.
rimvydukas said:
Hi,
While reading IS review on pocketnow.com I've found them saying that the screen sensitivity on IS is not good. But I'm interested and with others opinions from actual owners of IS. Thanks.
Click to expand...
Click to collapse
Perhaps the reviewers were on some kind of experimental drug.. i don't know.. i am too.. but, anyway. the screen sensitivity is just great. Have been using the IS for about three weeks now. Not one hick-up, restart, freeze what so ever.
it has been flying fast all the time.
If anything IMHO its a little over sensitive, sometimes it feels like I don't actually have to make physical contact before the IS makes the action.
TimMun said:
Perhaps the reviewers were on some kind of experimental drug.. i don't know.. i am too.. but, anyway. the screen sensitivity is just great. Have been using the IS for about three weeks now. Not one hick-up, restart, freeze what so ever.
it has been flying fast all the time.
Click to expand...
Click to collapse
I have to agree with you, the response time is instant, i haven't rebooted the phone since i started using it. roughly been 3 weeks 2 days uptime.
Although i sometimes hear an echo on my end but when i ask the person on the other end abt the quality of the sound they all say its crystal clear :S
gudge said:
If anything IMHO its a little over sensitive, sometimes it feels like I don't actually have to make physical contact before the IS makes the action.
Click to expand...
Click to collapse
Yes, definately also something I have noticed! This never happened with my Legend, so the screen of the IS must be more sensitive!
Ive noticed this and Ive been trying to figure out what it is. Swiping between home screens is slower than on my Legend and it takes a more firm/resolute (I have to overerly excagerate the finger movement) to get it to move sometimes. It starts moving, but then it stops.
Ive got a small metal piece stuck between screen and phone body, so this might affect my device. Read own post on the matter http://forum.xda-developers.com/showthread.php?t=1021486
madmaxx82 said:
Yes, definately also something I have noticed! This never happened with my Legend, so the screen of the IS must be more sensitive!
Click to expand...
Click to collapse
This is exactly what I have noticed. You might could say, it's just too sensitiv.
I haven't had any sensitivity issues - so far so good
I have a mate who got this phone & he is having issues with applications opening without him touching the screen he just has to put his finger about 2mm from screen & they open eg messages/camera etc.
Anyone else having this problem ?
Is there a setting he can change to fix this sensitivity issue especially as he has moved from an old Nokia non smartphone ?
MTIA
gudge said:
If anything IMHO its a little over sensitive, sometimes it feels like I don't actually have to make physical contact before the IS makes the action.
Click to expand...
Click to collapse
Yup mine is like this too.
lol. seriously, the guys who reviewed must have been smoking something really good
or they were plain prejudiced or paid to say so.
i would dare say this is the best touch screen i have ever used.
the sensitivity is just great... feels good to touch!
Same sensitivity as my desire... better than my galaxy s 4g...
Hey folks,
I'm experiencing with my IS, as mentioned in the title, an input lag of the touchscreen. It is not really disturbing, but the fact, that my friends Wildfire recognizes the input better, with Stock 2.1 ROM installed, bothers me really
In the moment I'm S-off on Android Revolution HD 1.1.2, which has a slightly better input than stock 2.3.3, but it is still there. Please tell me, if you are experiencing similar problems.
thanks Max
Only thing I've noticed so far is that if you drag slowly In some applications (like the browser, doesn't matter which browser I'm using) it doesn't scroll at all... but in the settings menu I can swipe downwards as slow as I want to, so I guess what I'm experiencing is software related...
What I really want to know is if I'm alone, or if there has noticed the same thing
Sent from a dumb phone
with my IcS... ive noticed that certain parts of my screen at the randomest times will stop recognizing input.... for me this happens exactly at the O and N key... after leaving it for a few seconds... it starts working again so not much of an issue to me...
there is an app in market place called touchscreen booster... maybe apply that and see if that helps u change the sensitivity...
danial.aw said:
with my IcS... ive noticed that certain parts of my screen at the randomest times will stop recognizing input.... for me this happens exactly at the O and N key... after leaving it for a few seconds... it starts working again so not much of an issue to me...
there is an app in market place called touchscreen booster... maybe apply that and see if that helps u change the sensitivity...
Click to expand...
Click to collapse
thanks for the advice danial.aw. I tried your method, but the only touchscreen booster app i found in the market was for SGS, so that hadn't had any effect
Keeps annoying me buying a 500$ phone that has such a crappy touchscreen...
Sounds to me like you might have a faulty unit if it's bad with both stock and custom ROMs. Never had any issue with mine.
doctorsax said:
Sounds to me like you might have a faulty unit if it's bad with both stock and custom ROMs. Never had any issue with mine.
Click to expand...
Click to collapse
any chance I get warranty for that? the lag is really minimal
Infinite104 said:
any chance I get warranty for that? the lag is really minimal
Click to expand...
Click to collapse
Not a clue I'm afraid. Always worth asking them I suppose.
well yes it says thats its for SGS only... but the app worked on my Atrix when i had it... so im assuming it might actually help more phones than that... try it out and see...
Doesn't make any difference no matter what i set in the app. I will drive to a store today to see if it might be subjective but I don't think so.
Edit: well it's not only subjective, I'll give the warranty a try, lets see how the will react
wooh got all of my money back, I'm moving to WP7 now. Android hasnt persuaded me...maybe again when 4.0 comes out.
Infinite104 said:
wooh got all of my money back, I'm moving to WP7 now. Android hasnt persuaded me...maybe again when 4.0 comes out.
Click to expand...
Click to collapse
If you are leaving android id probably recommend waiting for the next iPhone not wp7
Sent from my HTC Incredible S using XDA App
God WP7 is woeful, the mango update had better fix/add a lot of features...
No I've tested the one from my sister for already two months and I'm very content with WP7. A Phone should be fast and I'm not really into Apple's politics.
You will be in microsofts politics though. WP7 is as closed down as ios. At least with apple you get a good warranty service.
Sent from my HTC Incredible S using XDA App
http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=39892
it's pretty sad that there's only 45 votes on this issue. Here's a hint: bugs won't get fixed if people don't speak up about them. And don't think your voice exactly resonates here on XDA.
Just star it, and leave a comment. Doesn't have to be anything long winded either.
Sent from my Nexus 10 using xda premium
Maybe most of us just don't consider it a problem that needs fixing? I get bounce back on a number of different screens but I just swipe again, the world is not going to end because of it.
Troute said:
Maybe most of us just don't consider it a problem that needs fixing? I get bounce back on a number of different screens but I just swipe again, the world is not going to end because of it.
Click to expand...
Click to collapse
While agree it's not the end of the world, it's a complaint I see often here in kernel and ROM threads. While a lot of it is due to wonky behavior due to OC (either CPU or GPU), it's really just exacerbating an issue that is already present.
Besides, UI bugs are some of the most prevalent and immediately noticeable to more "common" end users. While functionally it's not debilitating, it's an aesthetic scar that doesn't need to be there.
Sent from my Nexus 10 using xda premium
Hmmm.. So I assume it doesn't matter that I need exactly 15 seconds everytime I get a notification to pull down the status bar, caused by flipbacks. Okay I'm like 1000% sure Google noticed it anyway, cause its on most devices, also 100% stock ones (like me) so...
Sent from my Galaxy Nexus using xda premium
The scrolling drives me crazy indeed. We shouldn't have to "make sure we're doing an exact certain way" just in order for it not to bounce back. It should just work, correctly, like our sgs3/gnex/etc...
Starred
Sent from my Nexus 7 using xda premium
jbdan said:
The scrolling drives me crazy indeed. We shouldn't have to "make sure we're doing an exact certain way" just in order for it not to bounce back. It should just work, correctly, like our sgs3/gnex/etc...
Starred
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If it would bounce back after a reboot one time, I wouldn't care, but its always there, it doesn't matter what I do, it bounces every time... So its a bit annoying.. This is the only thing which sometimes makes me want to throw the 7 at a wall...
Sent from my Galaxy Nexus using xda premium
Thanks OP, have added my star.
I had not noticed this problem but I was intrigued.
I could not duplicate the problem, but I am using Apex launcher, not the stock launcher. Does the problem occur in all launchers? Also I am not using the stock ROM.
I wonder if this problem happens with only some units, or perhaps it relates to those user's expectations. Maybe they expect their device to react more quickly than it is able to.
Far be it for me to be dismissive of people's satisfaction with their devices, but that bug-report thread has a lot of problems. It contains over-reaching claims and supposed knowledge of the problem's causes and solutions.
Again, I don't write off these people's unhappiness but I personally would not star that issue.
i too have this problem when on stock rom..now on PA beta 9 with m-kernel, the problem still exist...and it's very annoying...i even thought there was a problem with my touch screen panel and sent it to asus for repair but when i got it back, the same problem still remains..
Not starring because it does not bother me.
Life has too many other issues to worry about having to occasionally re-swipe.
Now pop-up ads in the Yahoo app could get me started...
squshy 7 said:
Come on guys, with all the members here and all the people who like to complain, it's pretty sad that there's only 45 votes on this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1801464
Well over 500 people have voted to say they have a shonky screen, either one fault, several or all listed.
If Asus & Google don't by now know that there is a serious problem with QC of the actual screen and with the build quality then no amount of petitioning will work.
I noticed this issue minutes after pulling this thing out of the box, this might not bother you people who casually use their tablets, but top those of us who have been using android since the G1 notice this. It bothers me so much that I am considering taking this junk back and using the money to get a real tablet from Samsung.
This issue is so annoying to me, I not only notice it on the stock launcher, but also Nova and Apex. Now, the launcher I can deal with, but where I becomes a deal breaker for me is the browser, whether it's chrome or the stock browser in CM10. Trying to scroll around the OS that requires some flicking reminds me of trying to flick scroll on a resistive touch screen, I think that best describes the issue.
I just wanna know if it's fixable through a software update or a hardware problem, cause if it's the latter, this thing is going back, and that's too bad because it was a Santa gift, so I'll have some explaining to do.......
compact_bijou said:
http://forum.xda-developers.com/showthread.php?t=1801464
Well over 500 people have voted to say they have a shonky screen, either one fault, several or all listed.
If Asus & Google don't by now know that there is a serious problem with QC of the actual screen and with the build quality then no amount of petitioning will work.
Click to expand...
Click to collapse
As I stated (not in precise terms sorry) in the OP, it would be a mistake to think that xda threads are the first place companies like Google and Asus check to see what issues people are having. They have issue and bug trackers for a reason. The universe does not revolve around our little community.
Also, this issue pertains to the general consensus that touch screen issues (like bounce back) have become exacerbated on 4.2 and above. Not anything regarding physical QC issues (though, to be fair, may very well be the root cause, but that is an entirely different issue; the fact of the matter remains that anecdotally it appears the touchscreen responded better on 4.1.2)
And besides, I'm just looking out for the well being of this device's future. Reporting bugs on bug trackers is important to these developers.
Sent from my Nexus 10 using xda premium
to be honest, this annoys me a lot.
starred and commented.
This really annoys me as well. I voted and commented. Hopefully they can get this fixed soon. Otherwise I might switch to CM10.
Sent from my Nexus 7 using xda app-developers app
This really annoys me too, and its not just the launcher its system wide, my s3 is so much nicer to scroll on, i have tried a few different roms & kernels and also cm10.1 and they all have this issue, anyone found a solution/rom that dosnt have this scroll bounce back issue?
leonclement said:
This really annoys me too, and its not just the launcher its system wide, my s3 is so much nicer to scroll on, i have tried a few different roms & kernels and also cm10.1 and they all have this issue, anyone found a solution/rom that dosnt have this scroll bounce back issue?
Click to expand...
Click to collapse
It seems to have been fixed somewhat (at least for me) on stock 4.2.2.
farmerbb said:
It seems to have been fixed somewhat (at least for me) on stock 4.2.2.
Click to expand...
Click to collapse
Yea the notification bar is better on 4.2.2, but the launcher still does it, nova prime does it too, and even when on dolphin or boat browser sometimes when you flick it will scroll nicely & sometimes a flick wont move the page much at all, weird and annoying, would be a much better experience if it was fixed!
This is a huge issue for me. Is there a way to increase or decrease sensitivity? Maybe that would help.
Sent from my Nexus 7 using xda app-developers app
Interesting, I thought I was the only one who had noticed this. Don't know why I haven't seen this thread earlier.
For me I solved this by using apex launcher, somehow you never get those annoying jumpbacks. I tried nova launcher as well but it worked as bad as the original launcher. Going to star tomorrow.
Sent from my GT-I9300
I experienced this on any ROM and including stock ROM.
Basically when the screen is off and I get a call...it takes a good 1-2 seconds, after ringer has started, before the screen shows anything at all.
Is this normal? Am I being dumb about this? I've just never had such a delay and it is quite annoying.
I'm getting this too, but it wasn't bad at first. I'm assuming some app is causing the lag.
rcobourn said:
I'm getting this too, but it wasn't bad at first. I'm assuming some app is causing the lag.
Click to expand...
Click to collapse
I also use greenify but I had the issue pregreenify. I do have some system apps greenified but none that are related to calls/answering calls
It's normal, and frankly not a problem lol.
devynbf said:
It's normal, and frankly not a problem lol.
Click to expand...
Click to collapse
Well I guess it's all relative. Is it a problem compared to the corruption in the federal government? Lol Then, well, no.
But it really is though. Never had a delay like this. Especially considering this is an expensive flagship phone
v2.2v said:
Well I guess it's all relative. Is it a problem compared to the corruption in the federal government? Lol Then, well, no.
But it really is though. Never had a delay like this. Especially considering this is an expensive flagship phone
Click to expand...
Click to collapse
Yes, an expensive flagship phone with an extremely bloated software.
I mean, as soon as you hear your ring tone you can immediately hit the home button or unlock button if it's that much of a bad thing.
Unless you're sitting and staring at your phone 24/7, you wouldn't even notice this.
Usually your phone stays in your pocket, you get a call and you take it out. *crisis averted lol.
I get what you're saying. Believe me I do. And you're correct about most of the time I won't notice. But that doesn't change the fact that bloated phones previous to this one didn't have this delay. To top it all off I'm debloated. So can't use that as an excuse
v2.2v said:
I get what you're saying. Believe me I do. And you're correct about most of the time I won't notice. But that doesn't change the fact that bloated phones previous to this one didn't have this delay. To top it all off I'm debloated. So can't use that as an excuse
Click to expand...
Click to collapse
You may have debloated your device app wise, but I'm not referring to that. I'm referring to the actual Operating System on the device, aka Touchwiz.
So yes, I am using that as a point of reference.
The OS itself is about 2.5GB, rather on the other hand a pure stock android is about 600MB.
And yes, other "Touchwiz" phones have done this in the past. My Girlfriend's S5 does this and so does my S4.
But guess what?
My Nexus 5 doesnt.
The phone actually turns on before it even starts playing the ringtone.
Stock Android > Touchwiz.
In reality, this is not a problem.
It's software-sided which means it could be fixed IF it was a problem, IMO it's just nit picky. I'm sure they could change this but I'm also sure that a 1-2 second delay will not stop you from picking up your phone call or cause any problems, either way.
If this is a problem, please illustrate one or two downsides because of it, what exactly is the outcome of this *delay* situation that is so problematic?
devynbf said:
You may have debloated your device app wise, but I'm not referring to that. I'm referring to the actual Operating System on the device, aka Touchwiz.
So yes, I am using that as a point of reference.
The OS itself is about 2.5GB, rather on the other hand a pure stock android is about 600MB.
And yes, other "Touchwiz" phones have done this in the past. My Girlfriend's S5 does this and so does my S4.
But guess what?
My Nexus 5 doesnt.
The phone actually turns on before it even starts playing the ringtone.
Stock Android > Touchwiz.
In reality, this is not a problem.
It's software-sided which means it could be fixed IF it was a problem, IMO it's just nit picky. I'm sure they could change this but I'm also sure that a 1-2 second delay will not stop you from picking up your phone call or cause any problems, either way.
If this is a problem, please illustrate one or two downsides because of it, what exactly is the outcome of this *delay* situation that is so problematic?
Click to expand...
Click to collapse
I can give you one right off the bat. And it's the only one that matters. It's called my opinion. If it never happened before with any phone I've ever had, touchwiz phones included...Then no...it isn't normal and it is a problem. No matter the size of the problem. No matter if you think I'm being picky. Frankly I'm done arguing the fact. If you aren't going to offer a fix, then there is no need for you to reply again.