I really hate to bring such a general question here, but this has gotten to the point where it's making me not like an otherwise amazing device. I don't necessarily expect a full answer to the problem, but I figured it was worth asking
Since I got my N6 (say about 4 months now), I've had an odd problem where I'll get completely random crippling lag while typing. it'll let me keep typing and then after a few seconds the places I tapped will start to ghost type behind where me. At first I blamed the google keyboard and tried swiftkey, but it does the same thing.
This has followed me across several ROMs and kernels, and I'm really curious wtf is causing it. If anyone has anything to say on this, please post here about your experiences and solutions
youwonder said:
I really hate to bring such a general question here, but this has gotten to the point where it's making me not like an otherwise amazing device. I don't necessarily expect a full answer to the problem, but I figured it was worth asking
Since I got my N6 (say about 4 months now), I've had an odd problem where I'll get completely random crippling lag while typing. it'll let me keep typing and then after a few seconds the places I tapped will start to ghost type behind where me. At first I blamed the google keyboard and tried swiftkey, but it does the same thing.
This has followed me across several ROMs and kernels, and I'm really curious wtf is causing it. If anyone has anything to say on this, please post here about your experiences and solutions
Click to expand...
Click to collapse
Have you ever done a complete factory image flash? Wipe everything, start fresh.
youwonder said:
I really hate to bring such a general question here, but this has gotten to the point where it's making me not like an otherwise amazing device. I don't necessarily expect a full answer to the problem, but I figured it was worth asking
Since I got my N6 (say about 4 months now), I've had an odd problem where I'll get completely random crippling lag while typing. it'll let me keep typing and then after a few seconds the places I tapped will start to ghost type behind where me. At first I blamed the google keyboard and tried swiftkey, but it does the same thing.
This has followed me across several ROMs and kernels, and I'm really curious wtf is causing it. If anyone has anything to say on this, please post here about your experiences and solutions
Click to expand...
Click to collapse
Do you have magnification gestures on in the accessibility menu? That can slow typing down to a crawl because it is waiting to register 3 consecutive taps to magnify the screen.
youwonder said:
I really hate to bring such a general question here, but this has gotten to the point where it's making me not like an otherwise amazing device. I don't necessarily expect a full answer to the problem, but I figured it was worth asking
Since I got my N6 (say about 4 months now), I've had an odd problem where I'll get completely random crippling lag while typing. it'll let me keep typing and then after a few seconds the places I tapped will start to ghost type behind where me. At first I blamed the google keyboard and tried swiftkey, but it does the same thing.
This has followed me across several ROMs and kernels, and I'm really curious wtf is causing it. If anyone has anything to say on this, please post here about your experiences and solutions
Click to expand...
Click to collapse
Not sure if you've found a solution to your issue, but just a few weeks ago (ever since the 5.1.1 OTA update) I was suffering the same issue. I found wiping the cache partition using stock or custom recovery will do the trick. I just did this a few days ago and have not experienced any keyboard lag or goofy keyboard glitches since. Simply boot into recovery by powering down, then hold volume down and power together. Use the volume buttons to select recovery, and the power button to confirm it. You'll reach a screen with the little Android guy and text below it saying no command. First hold power, then press volume up. You'll see a list of options. Using the volume keys again, highlight wipe cache, press power to select. Wiping cache will not delete any of your settings or media. It will take a minute or two, then you can select restart from the menu options. Hope this works for you as it did for me.
Sent from my Nexus 6 using XDA Free mobile app
Just found this post after a search as I get same issue. Have tried cache wipe, but comes back after a while. While this exhibits on the keyboard quite regularly, it also has crippling lag elsewhere where the phone becomes unresponsive for a more than a few seconds.
Currently running Marshmallow.
Anyone ever find what causes this?
I have the same problem, but I noticed that it only happens on landscape rotation.
jshaffe1 said:
Do you have magnification gestures on in the accessibility menu? That can slow typing down to a crawl because it is waiting to register 3 consecutive taps to magnify the screen.
Click to expand...
Click to collapse
Thank you! This was driving me nuts! I actually quite like the magnification gestures feature, but if it makes my keyboard lag then I am never using it again until it's fixed. This never used to happen before today.
Related
Hi Guys,
I did some research here and on google but couldn't find any good results.
I really have a serious lag in my keyboard, more likely at the repeating characters like, hello or whoohoo ... wil be like helo whoho, ...
Is there a fix or something else. When typing emails this result in a lot of frustation. I don't know how you guys think or experience this problem!
Thnx for you comments.
it's been brought up before but might be hard to search on...
Others have reported that turning off Word Completion and Auto Correct have helped.
Settings --> Input ... Word Completion tab
Give that a shot.
I have the same problem. I've turned off input completion under settings -> input -> word completion and in programs -> xT9 Settings. But when I type the letter A, Q, O, and L it tries to auto complete. Also Z is displayed as X. I installed the AT&T Keyboard fix from TaurusBullba and nothing changed. I am using Dutty_s_hybrid_Rom_Build_18533 Final on an AT&T tilt. Thanks for the help.
I've got the same issue. I've turned off Word Completion, etc. but it didn't seem to make a difference. Guess I need to slow my thumbs down...
Yes, the lag is quite annoying at times. It seems to be less of an issue when less programs are running. But I noticed the problem is not as bad since I stopped using Windows Media Player (which I would run all the time) and started using Audio Manager.
L8
With me the lag was even bigger after I had installed the HTC Touch Keyboard cab, which also xt9. After removing it got a little better (but still there's lag)...
So i guess there is no 1 solution for this keyboard lag? I'm also faced with the same problem I can finish typing my sms about 4 to 5 words faster then it can appear on the screen.
Anybody found a solution?
It might seem irrelevant but it obviously affects any consecutive keystrokes:
Start -> Settings -> Buttons -> Up/Down Control
If you put the delay to minimum, it seems to make things a lot better.
On the contrary, the "turning off autocomplete" solution didn't work for me.
Even though I think this should help you guys as well, I'm kind of pissed off that one has to use workarounds for such an expensive device to work properly. Especially when it comes to the keyboard which is among the top 5 reasons for buying it in the first place. I'm aware of the argument that this kind of thing happens with all WM devices, but still this seems close to unacceptable for me.
All the best
dsyro said:
Even though I think this should help you guys as well, I'm kind of pissed off that one has to use workarounds for such an expensive device to work properly. Especially when it comes to the keyboard which is among the top 5 reasons for buying it in the first place. I'm aware of the argument that this kind of thing happens with all WM devices, but still this seems close to unacceptable for me.
Click to expand...
Click to collapse
I totally agree, especially for a product that costs €600 or more! Nevertheless it's with all WM and HTC devices, and... has your pc never crashed or do you use a WindowsXP pc which has no tools or addons?
dsyro said:
It might seem irrelevant but it obviously affects any consecutive keystrokes:
Start -> Settings -> Buttons -> Up/Down Control
If you put the delay to minimum, it seems to make things a lot better.
On the contrary, the "turning off autocomplete" solution didn't work for me.
Click to expand...
Click to collapse
This appears to have fixed it for me, thank you!
This seems to have fixed it about 90% of the time. Sometimes when typing "www." it will end up ww. but that is only part of the time.
Thanks!
Mine sped up somewhat when I did the repeat rate change, but I REALLY noticed a difference when I removed the 3G dial pad and rebooted, seems everything is running faster now, but knowing my luck its a tease and it'll just go back to normal
dsyro said:
It might seem irrelevant but it obviously affects any consecutive keystrokes:
Start -> Settings -> Buttons -> Up/Down Control
If you put the delay to minimum, it seems to make things a lot better.
On the contrary, the "turning off autocomplete" solution didn't work for me.
Click to expand...
Click to collapse
Very odd, but it works for me. Thanks for the tip!
Up/Down control setting change worked for me too. Now the only problem is I actually get 3 letters sometimes!
Axman said:
Up/Down control setting change worked for me too. Now the only problem is I actually get 3 letters sometimes!
Click to expand...
Click to collapse
Maybe decrease the key repeat rate?
SWEET
the up down to a minimum seems t work for me. any suggestions as to which screen keyboard is better to use then the one in the rom my thumbs are to fat and its hard to use the keyboard when im driving. I knwo tis not safe but everyone does it. i guess it would be safer If my kaiser had bigger screen buttons for ppl with chubby fingers. LOL
thanks in advance.
juanitto
Hi Juanito,
Don't think it's your chubby fingers - we all suffer from it. I've heard people talk about the PCMKeyboard. On the last Roms i've tried, it didn't work, not sure why. I am currently running a ROM that has the Diamond keyboard, which I like too. The only thing I have to get used to is that it has two keys on each button (similar to for instance Nokia) but it is QWERTY (see here http://forum.xda-developers.com/showpost.php?p=2199341&postcount=15)...
Regards,
Nika.
I do also have the same problems with the whole touchscrenn input.
after some time working around, somehow all inputs have a delay. so for example when I am trying to close a program, the X (to close Prg) animates to be pushed half a second after I clicked on it...
or when I am trying to switch between tabs, it seems as the cpu is hanging somewhere around 100% and you have to repeat your input more times or try to push harder on the screen etc... until the inputs has been accepted.
is that a known issue? its very annoying...
only thing that helps is to softreset the device... but after some minutes the effect starts again...
to dr-house: your problem might be related to the 'htc task manager', especially versions 2 and higher. Disable it's auto start-up and see if you see any improvements.
how do u disable the taskmanger on startup and do the 3G txt thing??
Ive not tried searching for this problem, seems abit of an awkward thing to search so please dont shoot me
I've noticed for awhile now some times when im typing a text msg it'll work fine..... then it suddenly misses letters/key presses etc so my text message ends up
"Hey mate, how re yu oing?"... esspecially on words like "Little" i end up with "Litle" etc.
But going into Word / notepad etc it types no problems & other times i can do an SMS session with no problems then it'll suddenly act up, any idea why its doing this?
Im only using the kaisers default SMS program, maybe i should be using something abit better?
search for clear type in this forum you'll find your answer.
Ahh thanks, went to disable clear type ... damn things already disabled
*scratches head in confussion*
well ive enabled it, maybe that'll help lol
Blank2k2 said:
Ahh thanks, went to disable clear type ... damn things already disabled
*scratches head in confussion*
well ive enabled it, maybe that'll help lol
Click to expand...
Click to collapse
I haven't had any recent issues even with clear type enabled. A while back I did but now all is fine. My device appears to act funny at times. Just recently I lost all sound for almost 3 days, which was not a rom/radio compatibility issue.
redbandana said:
I haven't had any recent issues even with clear type enabled. A while back I did but now all is fine. My device appears to act funny at times. Just recently I lost all sound for almost 3 days, which was not a rom/radio compatibility issue.
Click to expand...
Click to collapse
Funny mine had just done this too, lost all sound for 2 days....
redbandana said:
I haven't had any recent issues even with clear type enabled. A while back I did but now all is fine. My device appears to act funny at times. Just recently I lost all sound for almost 3 days, which was not a rom/radio compatibility issue.
Click to expand...
Click to collapse
mine does weird things aswell, i use alarms alot... anyway i flashed my phone (so date was reset), my alarms werent going off, couldnt figure out why.
then relised the year was off & set the year correctly then the alarms started working, no idea what caused it to rely on the date.
now i think about it i guess "Monday 8am" would of been day differant day in 2005.... oki problem solved.
not very often that happens
Okay boys, here is the answer. There are two different functions you will have to modify. They are both under Settings>Buttons>Up Down Control.
Cleartype is only used for smoothing edges and has no affect on typing... btw.
Two different functions you will have to change are Lower the delay before first report to short, (far left) and Repeat rate to the slower side.
That helps on the lag issue you have been experiencing.
The second thing you should try is to disable predictive text.
Settings>Inputs>Word Completion
Try turning it off it helps a lot of people.
Have you flashed your rom or are you using the ATT one?
If you use the ATT one these problems will help, but the interface is still slow due to the bloatware on the phone. If you use a cooked rom the first thing should help as well as the second however, I am running a cooked rom L9 (laurentius) with no problems and I rarely miss type.
I have noticed one issue with my keyboard though that I cannot figure out and do not like, pressing the space bar and a number or letter before or after, the spacebar trumps the other buttons and many times I just see the space and no letter or number that I typed in close time proximity to the thing I was entering. Hope this helped.
I'm not sure if my 2 month old Note has had the following problem since day 1 but it's been doing if for a long time now.
The problem is there with a stock standard rom and any of the other custom roms and kernels that I've tried. I'm currently using Rocketrom with Speedmod kernel. I've also used Checkrom and Abyssnote kernel.
If the Note had been asleep for about 15 minutes or more when I wake it up then try to do anything like opening an app, closing an app that's already open etc there's a 2 to 3 second lag the first time I try to do anything. Everything is then normal until the next time that the Note has been asleep then it's the same story again.
Can anyone give me a clue as to what is going on here? I'm starting to think that it's hardware related, but apart from this problem the Note functions perfectly normally.
Also, if I have a CPU monitor installed, like URsafe CPU Monitor, when the lag is happening the monitor shows that the CPU is working hard.
Help please!!!!!
Does this happen after a complete hard reset with no apps installed?
Does this happen on Stock ROM?
Are you using WiFi?
Sounds like WiFi is sleeping when the screen is off, and either it is trying to connect and/or some app is wildly trying to connect using it.
Try seePU++ can tell you what the most active app is, but IIRC you have to pay for that that feature. There may be others.
PoisonWolf said:
Does this happen after a complete hard reset with no apps installed?
Does this happen on Stock ROM?
Click to expand...
Click to collapse
Yes, it happens on stock rom with no apps installed. I'm not totally sure what you mean by a complete hard reset. Can you please tell me how I do that? I'm willing to try anything to get rid of this problem.
jeromepearce said:
Are you using WiFi?
Sounds like WiFi is sleeping when the screen is off, and either it is trying to connect and/or some app is wildly trying to connect using it.
Try seePU++ can tell you what the most active app is, but IIRC you have to pay for that that feature. There may be others.
Click to expand...
Click to collapse
The problem still happens with WiFi disabled. On top of that it doesn't matter how long I leave it after I wake the phone up till I try to do something like launching an app. The problem is still there the first time I do anything with the phone.
I have rocket rom and sometimes when I turn on the screen the screen wont work. The physical buttons work but the screen is wont respond to touch.
Turning on and off the screen fixes this.
Very annoying.
Makes me appreciate Apple more.
CorruptedSanity said:
...snip...
Makes me appreciate Apple more.
Click to expand...
Click to collapse
Ban him!
appro77 said:
Yes, it happens on stock rom with no apps installed. I'm not totally sure what you mean by a complete hard reset. Can you please tell me how I do that? I'm willing to try anything to get rid of this problem.
Click to expand...
Click to collapse
Do a clean stock ROM with no root or anything.
Do a factory reset and erase your USB storage as well (i.e., tick the option when you're factory resetting).
Remove your microSD card.
Now, does the problem still occur? If it does, get your phone exchanged/repaired. It sounds like a hardware problem.
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
kanej2006 said:
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
Click to expand...
Click to collapse
Really? I haven't noticed this at all on my phone. Any specific apps I can test this on?
kanej2006 said:
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
Click to expand...
Click to collapse
Same here, totally normal.
Sent from my GT-N7000 using Tapatalk
1902 said:
Same here, totally normal.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Just not getting that myself. I am not terribly patient, and generally the most I have to wait is a second for an app to respond after waking the phone, and that is not often.
Stock unrooted HK version, never seen anything like that delay, mine works instantly on waking
Sent from my GT-N7000 using Tapatalk
Same delay here. Stock ROM, and rooted.
kanej2006 said:
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
Click to expand...
Click to collapse
I dare say this is not normal, the only time there is a delay in opening the dialer/contacts application is when you initially boot the device and have both of those running for the first time subsequent runs have no delay what so ever on my end ( when i still had the note )
kanej2006 said:
What you are experiencing is perfectly normal.
I'm getting the exact same issue. When the phone is not used for a long period of time, is then unlocked, opening contacts, sms or the menu takes a good 2-3 seconds.
It's really annoying and it's a delay when 'waking up' the phone.
Supposedly this issue should be fixed with Ice Cream Sandwich, so be patient and this bug should soon be gone...
Click to expand...
Click to collapse
If this is normal it's incredibly bad that Samsung would design something like this. The wake up lag is bad enough let alone this. Can't see how it can be normal though. My SGS2 didn't have it and some other users aren't seeing it. I think I'll hang out for ICS and see if it goes away before I take any further action.
Strange issue, seems it occurs for some but not all...
Once again, I unlocked the screen after 2 hours of no use, when pressing contacts, there was a 2 second delay and when attempting to call someone there was a good 2-3 decond delay...
jeromepearce said:
Just not getting that myself. I am not terribly patient, and generally the most I have to wait is a second for an app to respond after waking the phone, and that is not often.
Click to expand...
Click to collapse
Luky you :banghead:
Sent from my GT-N7000 using Tapatalk
Despite being my first Android device I have come to accept that this is normal for this OS.
Unfortunately I have become a big whiner on this forum because of this same issue.
The day before yesterday there was an update on the kies ,LA4,after updating it felt a bit faster overall but the wake up and the incredibly annoying Contacts lag is still there.
I myself am not any particular OS follower or a fanboy of any certain brand for that matter.
So I'm stuck with Android for the time being, since I don't like both iTunes and izunes dependency, besides no big screens there.
However I suspect that this is an Android thing, as far as I know Android is based on Java and Java is known to be laggy,so until a very powerful CPU is available for mobiles, for me its either live with it or Leave it !! and since there is no alternative for now will wait and see how good ICS does and decide accordingly.
I'm on stock ROM and unrooted.
The Note seems to do this once or twice but when a program/app has been opened once it usually reopens them instantly.
This morning when turning on my Note for the first time, there was a few second delay when attempting to call someone, another delay when opening contacts and another slight delay when viewing sms messages.
However, the second time I attempy to open something it's usually immediately.
There should not be ANY delay when opening programs/apps and Ice Cream Sandwich should fix this wake up issue which some users such as myself am experiencing.
It's a shame, really since I'm getting no other lag/delay. The phone is super fast in every possible way, only sometimes it's a little slow at waking up!!
You ever finding yourself picking up the phone, swiping down to unlock and the actual ring doesn't show up till AFTER you swiped? It's starting to be really annoying. Usually happens after a long standby as opposed to having used the phone recently. Sometimes even though the ring shows up it doesn't register my swipe the first time at all, even if done firmly.
How the hell can you develop muscle memory with a device that doesn't always react the same way to your input?
I hate having to slow down to cater to my device's (special) needs... It's driving me nuts
I'll be putting it up on swappa tomorrow if I can't find a solution.. if anyone wants, XT1058 bootloader and carrier unlocked
I switch phones a lot so nbd. I hate android's lack of consistency. Plagued every single android flagship device I've ever had in various ways. I think it's time I try WP8 =)
I'm less then 24 hours after a fresh wipe (RSD lite). Running very little apps. Nothing frozen in titanium, just rooted with TWRP recovery.
scorpion667 said:
You ever finding yourself picking up the phone, swiping down to unlock and the actual ring doesn't show up till AFTER you swiped? It's starting to be really annoying. Usually happens after a long standby as opposed to having used the phone recently. Sometimes even though the ring shows up it doesn't register my swipe the first time at all, even if done firmly.
How the hell can you develop muscle memory with a device that doesn't always react the same way to your input?
I hate having to slow down to cater to my device's (special) needs... It's driving me nuts
I'll be putting it up on swappa tomorrow if I can't find a solution.. if anyone wants, XT1058 bootloader and carrier unlocked
I switch phones a lot so nbd. I hate android's lack of consistency. Plagued every single android flagship device I've ever had in various ways. I think it's time I try WP8 =)
I'm less then 24 hours after a fresh wipe (RSD lite). Running very little apps. Nothing frozen in titanium, just rooted with TWRP recovery.
Click to expand...
Click to collapse
never had this issue unless you are referencing the active notifications which has nothing to do with android. If you are talking about pressing the unlock button then the unlock icon appearing and swiping that down (which is the only part that is part of android, then I have never seen this happen. If you are talking about active notification (which i assume you are because it swipes down while the android unlock screen swipes to the right i believe) then yes sometimes it doesn't appear for me but not in a lagging since. In that it just doesn't recognize i want active notifications to pop up. But its typically not when it has been in standby for a while but when i have been moving it a lot like in my hand. Either way, it typically pops up for me before i can even see the screen.
edit: android lockscreen unlocks in all directions not just down.
jayboyyyy said:
never had this issue unless you are referencing the active notifications which has nothing to do with android. If you are talking about pressing the unlock button then the unlock icon appearing and swiping that down (which is the only part that is part of android, then I have never seen this happen. If you are talking about active notification (which i assume you are because it swipes down while the android unlock screen swipes to the right i believe) then yes sometimes it doesn't appear for me but not in a lagging since. In that it just doesn't recognize i want active notifications to pop up. But its typically not when it has been in standby for a while but when i have been moving it a lot like in my hand. Either way, it typically pops up for me before i can even see the screen.
Click to expand...
Click to collapse
When you pick up the phone, the unlock ring appears. I'm saying the time it takes for it to appear is not consistent. This makes it impossible to develop the muscle memory needed to consistently unlock your device fast. It makes me feel like my phone can't keep up with me, something I've never had a problem with on the...dark side.
I wasn't referring to this as this as the sole reason as why I think android is consistent, but just one example out of many. Inconsistent scrolling, dropped frames during transition animations, app open times varying wildly even if precached, etc. I just don't think I'm an android guy, I can't ignore the crappy UI handling. Some people don't even perceive it as lag but for me it just jumps in my face every time. BUT that's subject matter for a different topic.
double post delete pls
scorpion667 said:
When you pick up the phone, the unlock ring appears. I'm saying the time it takes for it to appear is not consistent. This makes it impossible to develop the muscle memory needed to consistently unlock your device fast. It makes me feel like my phone can't keep up with me, something I've never had a problem with on the...dark side.
I wasn't referring to this as this as the sole reason as why I think android is inconsistent, but just one example out of many. Inconsistent scrolling, dropped frames during transition animations, app open times varying wildly even if precached, etc. I just don't think I'm an android guy, I can't ignore the crappy UI handling. Some people are used to it and don't even perceive it as lag but for me it jumps in my face every time. BUT that's subject matter for a different topic.
Click to expand...
Click to collapse
if you want to keep up with muscle memory then click the unlock button on the right and then unlock by swiping the lock on the screen like all the other phones on the market. It will work every time all the time with 100% accuracy/consistency. If you don't like the active notifications that Motorola built into the phone then don't use it. The inconsistency you are describing here is Motorolas fault, but it is their first shot at active notifications so I expect more bugs than I have seen so far.
But as i said before, mine either doesn't pop up or pops up before i can even look at the screen so I don't have the problem you do. And when it doens't pop up its typically because Im playing with in my hand then decide i want to use it and I have been tossing it all around. If it is sitting still or in my pocket and i pick it up it pops up the ring faster than I look at the screen. I doubt it but maybe it has to do with the twrp rooting method.
If I have to resort to that, 95% of what moto X brings to the table for me, is gone. At that point I might as well be using a nexus for the awesome dev support.
I would rather try to troubleshoot the issue since it IS software. It is evident because the method which you described brings up the phone instantly anytime anywhere so the hardware capability is there... i guess... lol.
No issues on mine, active notifications with and without notifications works every time, before the phone is completely flipped or out of my pocket, the pixels are fully lit. I'm stock non rooted though, but it works every time as it is intended.
Sent from my XT1058 using XDA Premium 4 mobile app
No issue for me either. When I pickup the phone or take it out of my pocket, the ring is there. And I've experienced zero lag either in UI transitions or opening apps.
I've never experienced anything like this before. The performance of my X has been flawless.
I tested it a little bit more and I found you are right. I didn't notice it because I don't grab my phone and instantly try to unlock. When I did let it sit for 10 minutes or so and had the screen not flipped over so I could watch it there was a noticeable 1 second time difference as opposed to when I laid it down let the screen go dark then pick it back up. But for me I really had to grab my phone and try to unlock it before bringing it to my face for it to not pop up in time for my unlock swipe.
Sent from my XT1060 using xda app-developers app
Hello
Ive had numerous problems while i was on KK 4.4.2 .681 and .757 with freezeing phone, random reboots(usually once a day) and touch screen issues.
I have asked alot here and over at Sonys support forum and ppl began to point out that i could very well have a hardware problem. Although the problems i have had on KK wasnt that odd. Since ive read about others having theese problems.
But early monday morning i thought that hmm why not try what a dude here suggested. Wipe the phone completley with cache, dalvik cache and all that and flash the latest 4.3 firmware with JB. Hmm oki well i did that, and so far i havent had any reboots, or any freezes. Camera is QUICK and takes better pictures. At some point i thought the touch was acting weird but that could just be the app itself freaking out, it was only for a few seconds and after that everything was working like it should. Battery time is better aswell(although it goes down to 75% quite fast but after that its slooooow).
So do you still think i might have hardware issues ? I was about to ship my phone back to China but now it feels like it is pure software issues. And i have had big troubles with the retailer to accept this as a warranty matter since he belives its a software issue.
But then again, my phone aint operating good at all with KK 4.4.2
So far everything is fine with the phone, missing some stuff from KK but not the end of the world. But im still testing. If it will remain on without a freeze until the end of the week i could be quite certain that it is KK that ****s up my phone totally.
Please respond with thoughts.
Who told you to wipe your phone? ..lol..
Just my thoughts about touch screen, I replaced 2 days ago my "lucid" classic transparent screen protector with one Anti-Glare, which is not lucid glass like many but is rough and it influence a little little bit on the visualization of the screen, tiny, tiny thing but the touch screen is much much more responsive.
Classic issue with touch screen, unlock with patterns, with the lucid screen protector sometimes it skipped the touch and I had to try 2 times to unlock the phone if the phone was put on the table without hold it. With the new screen protector it not skip anything.
Sometime a stupid thing can be the issue.
Could be the screen protector, remember the first one I had was a antiglare, and as far as I remember I didn't have those issues then. Now I have ultraclear one. Could be that, you never know. I do have tempered glass one wich I haven't used.
Just before the phone actually froze for a few seconds just when I took a picture, but it came back with no reboot. And I got a msg on WhatsApp and messenger at the same time so that could be what was causing the lag this time. Hopefully
Sent from my C6903 using XDA Free mobile app
Still no reboot! Used camera alot and done all sorts of stuff.
And today I changed my screenprotector to see if that would rectify the touchscreen issue. I used a tempered glass screen protector. O my god how much better that protector feels! But still testing for any issues
Sent from my C6903 using XDA Free mobile app
Some updates.
No random reboots!
But two other odd things occurred and one of them is known.
1. Touchscreen went crazy, it didn't press what I wanted and so on. I noticed it actually swiped on the keyboard. Turned that function off and unistalled the app "Color notes". Touch screen bugs are known and Sony even admitted it so.
2. I couldn't send sms today, tried to several but got error. Data and so on still worked. Restarted the phone and then it worked again (might just be coincidence). Although I noticed that it at some point it had trouble sending data, took forever to get connection even though I had 3-4 pins reception. Also noticed when that sms bug occurred that it switched from 2 pins to full every time I opened the sms to send.
But still no reboots. These things maybe would trigger reboots with kitkat, I dunno.
Sent from my C6903 using XDA Free mobile app
Jonas740 said:
1. Touchscreen went crazy, it didn't press what I wanted and so on. I noticed it actually swiped on the keyboard. Turned that function off and unistalled the app "Color notes". Touch screen bugs are known and Sony even admitted it so.
Click to expand...
Click to collapse
I have it all the time, I mean not the touch screen going crazy but the swipe one on keyboard, it happen always when I click on the letter A on left side, it really piss me off.
I think I have to turn off the swipe thing too.
Ye I've read about ppl having issues like we do and they just turned it off and then it works. Sony said they would fix the touchscreen issues in updates but still not fixed.
Btw, have you noticed that the "swipe" to turn off the alarm clock is less sensitive? It takes some trys to swipe to turn it off. Although it is a good thing because it makes me pissed and I have to concentrate to turn it off wich makes me to get up Might be an intended "bug".
Sent from my C6903 using XDA Free mobile app
Jonas740 said:
Ye I've read about ppl having issues like we do and they just turned it off and then it works. Sony said they would fix the touchscreen issues in updates but still not fixed.
Click to expand...
Click to collapse
Yeah, they are very lazy to fix this issues but they are not to put on the market a "new" device and forgot about Z1.
Jonas740 said:
Btw, have you noticed that the "swipe" to turn off the alarm clock is less sensitive? It takes some trys to swipe to turn it off. Although it is a good thing because it makes me pissed and I have to concentrate to turn it off wich makes me to get up Might be an intended "bug".
Click to expand...
Click to collapse
Yes, Yes, I am glad that I am not alone. It was less sensitive even before I turned off the "keyboard swipe" thing. So not really know if it's related to that features, it shouldn't, but you confirmed a "bug" which was keeping me thinking. O Lord, I dream about a Z1 bugs free! (dream only)
might not be
eclyptos said:
Yes, Yes, I am glad that I am not alone. It was less sensitive even before I turned off the "keyboard swipe" thing. So not really know if it's related to that features, it shouldn't, but you confirmed a "bug" which was keeping me thinking. O Lord, I dream about a Z1 bugs free! (dream only)
Click to expand...
Click to collapse
Well that Alarm swipe might not be a bug actually, ive tried it back and forth and if you "lazy" swipe it fast like you would when it rings in the morning it wont turn off. But if you do apply pressure and swipe slow it will turn off. Not a huge problem for me since it actually help me getting out of bed
Jonas740 said:
Well that Alarm swipe might not be a bug actually, ive tried it back and forth and if you "lazy" swipe it fast like you would when it rings in the morning it wont turn off. But if you do apply pressure and swipe slow it will turn off. Not a huge problem for me since it actually help me getting out of bed
Click to expand...
Click to collapse
Of curse, it help me too, I get angry because of that so I have to leave my bed ..LOL..
The thing is, who know if it was meant to be like that? It was made with that purpose? Because if it isn't then it's a "bug".