just wondering if anyone else has been using the latest swype beta and if so are you having the same issue as me to where im stuck waiting a good 5-15 seconds for the keyboard to pop up after tapping in the input text box? it started last week and hasnt gotten better yet, its so irritating, i feel like im back on my original G1.
same here! happens very randomly but is really frustrating when it happens
Sent from my SGH-T999 using Tapatalk 2
same here ... it seems to happen the first time I attempt to type after a reboot.. it seems to be loading, which means it did not load on boot even tho it is the default keyboard.. weird
after that first request for keyboard after boot.. it comes up normally, in 0.01-3 seconds based on current memory+ cpu load
Related
Today my phone started to lag while I type text messages. I tend to type fast, and if the keyboard starts to lag and I continue to type fast the keyboard will lock up, then a second later it will type all the keys I just pressed.
I have vibration feedback turned on, I have not downloaded or installed anything lately related to my keyboard, or any input, hell I dont even thing I downloaded or updated anything in the past day or so.
I am on froyo, and and on telus. HTC's seem to just love to lag when using keyboards... My last 2 phones (s720 and touch pro) both lagged like hell when using the keyboard.
Anyhow, anyone having this same problem, with a 1 ghz processor I should have no troubles pressing a couple buttons... :S (and havent had any trouble up until today)
I dont want to turn on vibration, I was typing on an iPhone the other day and it felt real weird to type without vibration.
I've also cleared out a bunch of texts, and rebooted the phone, neither helped.
How many texts are loaded on the screen ?
Sent from my HTC Desire using XDA App
I woke up today and it seems to have gone away..
What the hell :S
My keyboard sometimes lags, but only if replying to a a long thread on the digital spy forums using the phone in portrait mode. Holding the phone on its side foxes this for me.
Sent from my HTC Desire using Tapatalk
I also noticed this
If you replay on a long mal with many intermediate stops (RE:s and FW:s), the text you type has to be inserted before the rest of that long conversation and it indeed reacts slower.
Saw a few posting for other android items but none for the GN so here it goes:
Ever since upgrading to JB, my phone takes 2+ minutes to startup. The actual time is 2 minutes 46 seconds displaying the google logo, then about 15 seconds at the multicolor X.
I had tinkered around with a JB release from Vicious a couple months before Verizon rolled their 'official' release out. At that time I also noticed an extremely long startup time, but didn't have it loaded on the phone that long so really not an issue.
But now this startup time is just insane. I made a few laps around the grocery store before the phone actually was ready to use again.
If anybody has an idea on this, please post. I can't imagine people would consider this acceptable so I'm hoping there is some resolution.
Thanks
I have a GSM Nexus and it takes a little less than 15 seconds on the "Google" screen and then another 30 seconds on the multicolored X. 4.1.2
ok so definitely not a common issue. any ideas?
Yup had the same problem after upgrading to JB on both Jelly Belly and AOKP. I would flash the JB bootloader hoping that would help but it didn't. On CM10 now and it boots right up, it's FAST.:good:
I've heard the CM10 referenced before, could you tell a bit about that in comparison to the base VZW version?
militarymedic23 said:
I've heard the CM10 referenced before, could you tell a bit about that in comparison to the base VZW version?
Click to expand...
Click to collapse
CM10 is based on AOSP, so right off the bat it is going to be very similar in terms of look and feel. And then you open the setting menu and find out how many customization options you have, and you see the built in theme engine, and realize how smooth and fluent everything is.
Seems to be random. Sometimes I have no startup delay, and other times the phone hangs at the Google screen for several minutes. No rhyme or reason, just happens. However since rebooting is not all that necessary on a regular basis, I stopped thinking about it. And my phone still works just fine.
Sent from my Xoom using xda premium
Jellybean does filesystem check and repair on boot, so if you did a dirty shutdown or something which caused filesystem errors, that would explain the the extra time taken to boot.
I decided to bump this up to CM10. although on the first try at backing up the phone it actually wiped the thing. Not quite sure what happened there.
I am opening another thread on a display problem with double clocks on the main screen.
As far as I can recall, I've shut the phone down through the software. Once in a great while I force power it off but nothing recently.
Anyway, we'll see how CM10 works.
I'm using thumb keyboard on my n5110, stock android 4.1.2. Sometimes while typing the keyboard disappears. Other times the cursor jumps around on the page instead. Sometimes both.
The weird thing is that this is my 2nd Note 8 and it never happened on the first one. I exchanged it and the second Note is perfect in every way except this keyboard issue. Could it be a hardware issue? I'm guessing no but it's weird that it never happened on the first device.
I've switched to SwiftKey now and to see if it happens with other keyboards. It happens infrequent enough that I'll have to use it for a while to be sure.
Can you tell me what you were doing? I own thumbs keyboard and I can try to recreate it if you want. Ive happily switched to SwiftKey but I do appreciate the features of thar keyboard.
Sent from my GT-N5110 using Tapatalk 4
I tried to google any related threads to the symptom that my N7 2013 shows, but so far couldn't find any. So I decided to start a new thread to see if I'm the only one in this.
As the thread title suggests, the screen freezes randomly and comes back to life after a few seconds later. It doesn't seem to be happening continuously, but the interval between one and the next one should be something like half an hour, give or take. Funny thing is, when it happens, it does recognize all the inputs made on the screen while frozen and once the screen starts responding again, everything I have done in the meantime appears on it afterwards such as typing, swiping, etc.
I suspect it started happening after I installed the newest firmware, JLS36I, but can't be sure as I have received in the fairly early stage of rollout--pretty much on the same day Google started rolling it out, which was just a few days after I got my N7 2013.
I've experienced pretty much the exact same issue on mine, build JSS15R, not sure why though?
This happens occasionally on my Nexus 4, running CM10.2...ive read that its an issue with 4.3 all together.
i don't see a 30 min window like you experience. mine is about 10 seconds.
Just loaded last nights update and we'll see if it continues.
On my N7; ive never had it happen.
racenrich said:
This happens occasionally on my Nexus 4, running CM10.2...ive read that its an issue with 4.3 all together.
i don't see a 30 min window like you experience. mine is about 10 seconds.
Just loaded last nights update and we'll see if it continues.
On my N7; ive never had it happen.
Click to expand...
Click to collapse
Didn't know it's a known issue with Android 4.3. But it's somewhat odd that I never had such problems with Nexus 4 and Nexus 7 2012 although both are on 4.3. And it seems I was a bit ambiguous or misleading with the description. Mine is also about a few seconds, between five to ten second each, but it seems like it happens every half an hour if I use the device continuously. Is it somewhat similar to your N4?
iam_emailer said:
I tried to google any related threads to the symptom that my N7 2013 shows, but so far couldn't find any. So I decided to start a new thread to see if I'm the only one in this.
As the thread title suggests, the screen freezes randomly and comes back to life after a few seconds later. It doesn't seem to be happening continuously, but the interval between one and the next one should be something like half an hour, give or take. Funny thing is, when it happens, it does recognize all the inputs made on the screen while frozen and once the screen starts responding again, everything I have done in the meantime appears on it afterwards such as typing, swiping, etc.
I suspect it started happening after I installed the newest firmware, JLS36I, but can't be sure as I have received in the fairly early stage of rollout--pretty much on the same day Google started rolling it out, which was just a few days after I got my N7 2013.
Click to expand...
Click to collapse
I have the exact problem... I did the touch screen test with no problem.. I would say not hardware issue? Seems like the proccesor freze will trying to load something...
Same problem
I have the same problem also ... input text, playing game ... one day have around 2 time screen freezing ~ any1 have the solution ?
It seems like you are not alone. Mine is acting just the same. After a continuous gaming there would be this weird frozen screen which would magically turn back to normal and not happening again after maybe around an hour.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Me too. Not frequently but from time to time. Especially when I lay the device down .... Its useless sometimes. I can't believe Google can't fix this. I'm running 15r
Sent from my Nexus 7 using Tapatalk 4
I experience the same thing about once for every hour of use. The screen will freeze for about 5 seconds, although the power button is able to turn off the screen the device is otherwise unresponsive.
This was happening in every rom, stock or otherwise for me and I was about to return it then I flashed v10 of Paranoid Android and the problem hasn't reoccurred in 2 days so far. Hoping it stays that way.
Same problem here...
It's the device hanging while it performs an IO operation- the storage on the Nexus 7 isn't particularly fast, though it is faster than the last-gen N7 which was about a million times worse for random device freezes than this model.
Same problem here, was thinking of flashing CM to see if it was any better.
Same issue here, but i notice this today, it was working fine the last couple of weeks after the last update
Hi chaps
I've had my note 2 for nearly 3 years so it's getting on a bit. I've got Android Revolution HD v31 on it, supposed to be one of the most stable roms I think?
Sometimes I get a problem where the keyboard shows up like normal, and when I type it gives the haptic feedback and the app acts like you're typing, but nothing actually enters into the textbox. When I get this problem it can be quite persistent, and it happens in all apps. Chrome/whatsapp/messenger, you name it. I've experienced this with Swiftkey, but also the stock samsung keyboard. Restarting fixes it too but just waiting a few minutes and coming back or force closing all apps and trying again usually works too.
This is really really irritating (probably happens ~20% of the time I go to use the keyboard) - As soon as I get some time I'm going to flash the original samsung firmware again and start afresh but I don't have ODIN setup on this laptop anymore and I don't currently have the time. Any short term solutions or the fastest way to get back to stock would be ideal. Cheers!