Hi, all..
I find that the android keyboard starts to break after a few days without a restart when I'm using either the DevNull or Oxygen rom. (Currently on DevNull 1.0.3 but I have tried several versions and several Oxygen versions.)
Things that start breaking:
The "symbol" key in the bottom left corner becomes really, really slow - you wait about 10 seconds for the keys to change.
The orientation sesor detects that you've rotate the phone but the keyboard doesn't change for several seconds. (It hangs and then changes)
Sometimes the keyboard isn't sized properly after an orientation change.
Sometimes apps crash while waiting for an orientation change.
A restart usually fixes the problem for a while.
Has anyone else seen this? Any fixes?
Related
I was using Energy ROM (dated June 2012) and my KF suddenly locked up. I rebooted the KF and it stuck at the color tiles for at least 10 minutes before I gave up and restarted it, which didn't help. I then flash it with the latest Energy ROM and the problem won't go away and I used the complete wipe option. I also tried out Alien ROM and Hashcode's CM 10 ROM. While both of them would boot fine, I have problem with internet videos in browser. Particularly, the video control bar would pop up and down as soon as I nudge the KF. This was happening when I'm using Dolphin and the default browser. Is there a way to fix it?
What recovery are you using? Version? Not that it really matters. I'm just curious why Energy wouldn't work after a complete wipe.
To fix the problem you have with videos, simply turn your rotation off.
I believe TWRP is 2.2.2.1 and latest FFF bootloader retrieved from KFU. If I turn off rotation, wouldn't the display be stuck at 1 orientation?
LOL. Rotate your device, THEN turn rotation off. The rotation is pretty sensitive and when the media player detects a slight amount of rotation, it acts up.
OK I'm dumb =). I noticed that in the default browser, it doesn't suffer from the annoying video controls popping up and down. However, Dolphin still does so I assume it's Dolphin's problem. I'm using iPad as user agent otherwise the sites will try to get me to install Flash.
However, my original problem with Energy ROM baffles me. A few months back, I notice it was gradually slowing down and getting less responsive and completely dropping WiFi connections. So I reformat and reinstall it and it ran until I notice the same problem until it locked up for good. What kind of problem is preventing the ROM from running properly even after a full wipe install?
Energy ROM hasn't been updated in months and is pretty much dead in the water. The 3.0 kernel for the Kindle Fire has been updated many times since Energy was last active here.
Hello,
Ive noticed in some apps, and in particular Firefox (and i believe Gmail), that selecting text sporadically LAGS on my Galaxy S3 running Cyanogenmod 10.1.3.. to the point where dragging the markers to the left or right is delayed by several seconds.
Has anyone experienced severe text selection lag? Any debugging steps?
Ive undergone many app updates, and updating from C 10.1.0 to 10.1.3, without change. Happens sporadically it seems. Does this happen on stock rom? I haven't been stock for a while and can't go back.
kevinf28 said:
Hello,
Ive noticed in some apps, and in particular Firefox (and i believe Gmail), that selecting text sporadically LAGS on my Galaxy S3 running Cyanogenmod 10.1.3.. to the point where dragging the markers to the left or right is delayed by several seconds.
Has anyone experienced severe text selection lag? Any debugging steps?
Ive undergone many app updates, and updating from C 10.1.0 to 10.1.3, without change. Happens sporadically it seems. Does this happen on stock rom? I haven't been stock for a while and can't go back.
Click to expand...
Click to collapse
I have been on stock for a while and so far I haven't had that issue. Could be an issue with your keyboard app or just a plain bug.
forgot to note, I do use SwiftKey keyboard
It did it again today in Firefox, and I noticed it was not fully zoomed in (eg: normally when you select a textbox the page zooms into that field). clicking the textbox a few more times until the page zoomed in in Firefox 'fixed it'... hmm
I am currently running the latest build of the PacMan rom for my Sprint S3, but my problem didnt start there. As over the course of a few weeks my phone has been randomly crashing while running build 7 of Slimkat. It started crashing when i wanted to take a picture with the AOSP camera (when i hit the camera button and then it would shut off). Then it progressed to just crashing trying to use accuweather, or even when the screen was auto-rotating in my SMS app. So finally i just backed up my important bits and made a clean wipe into Wicked X 8.0 TW rom (because i'm on Ting and TW roms initially work on their network and wanted to export, or to just copy down the settings of, the APN xml to use in AOSP roms). After playing around with that for 20 minutes, i didn't experience any fc's or reboots. Though i did not use the camera in that time (i forgot to check). To which i then wiped it into PacMan rom that im at now. Which at the moment seems fine to do everything, except it will shut off if i want to OPEN the camera (doesn't let me use it at all). Plus i did have it crash once rotating with the play store up...
So im kinda lost, i wonder if this is just an issue with the camera in the rom, or if it might be a bigger issue with the phone itself. As ive been having the same random error's with two roms and i dont see anyone having FC's with pacman rom with the camera.
more testing done
So i have also attempted to odin completely back to stock and i have a stock rooted rom with nothing touched. The sudden shut-offs still happen and occur randomly. I installed logcat and what seems to be throwing error's is the accelerometer. Plus at first when i flash a new rom it seems to work ok with no problems for the first day, then suddenly start showing symptoms the next. Plus ive had it shut off during bootup too while going through the sprint 4g animation screen. Though i have not had it die on me in recovery, so thats a thing.... Plus it will rotate no problem half the time, and then ive seen it die rotating to use my keyboard.
So at this point i feel like its actually a hardware option. If it is the accelerometer, is it easy to fix (i guess re solder the connections if they're broke?)? or should i just try and replace the main board?
Hi there,
I had gotten the OTA on my Mi 10T Pro some time back and since the update, I notice the screen responsiveness reduce a lot. I always missed the gesture to perform back or pull the notification status down or any other gesture.
I even notice my Capacitive Pen (fine tips) wasn't registering the touch too. Previously, it was working fine on my Mi 10T Pro.
Do you notice that too? Or it is only me?
I have the same problem with big lags on the touchscreen, or maybe big lags on the apps that freeze touchscreen changes.
I updated to 12.1.1 Global via an OTA a few weeks ago, but had to factory reset to get it working. Then it worked well, except for the very annoying lack of gesture support for non-stock launchers.
Now I get major lags scrolling through items or using swipe on the Google Keyboard. Very frustrating ,and I only hope the 12.5 update comes soon and fixes things.
Look like we are not alone.
You set to factory default fix the problem?
No, it's still lagging badly.
I had to Factory Reset to get the phone to work acceptably after the OTA to Android 11. It worked well for a couple of weeks, then started lagging badly with many apps involving a long swipe (like keyboard using swipe, scrolling through news etc) would become unresponsive after about 1/2 sec movement.
Reboots didn't seem to fix it but may have improved things for a while before returning to lag.
Hi all.
I have 12L beta 3 installed on my 6 Pro. Everything running fine apart this weird visual when closing apps by pressing the back button a few times. I dirty flashed over Feb A12.
I have always pressed the back button a few times to close apps in case they have that "Press again to close" message. Now in 12L the screen pauses when the app closes. Didn't happen in 12. Tried stock kernel and latest radioactive/dispair and same result.
Attached is a video showing me close 3 apps by quickly pressing back a few times, and then by just pressing back once.
Anyone else experienced this?
Yes I've experienced something very similar to that, the windows are left open for a second before disappearing. I just put it down to it being a bug in the beta and something that might be resolved.
Same here, I hope it is a bug because I am not a fan of it.