Okay, I've got several Samsung Keyboard issues, so bear with me as I explain as it may be a bit long.
First and foremost, my keyboard keeps crashing. At first, I assumed this was just a general issue that a reboot was necessary in order to fix. This is entirely not the case, as it even happens directly after a reboot at times. Also, they keyboard crashing happens in several different ways. This normally happens while using Kik messenger, but it does happen at times while using normal text messaging as well, so I'm assuming Kik isn't the problem.
1)Normal keyboard crash, where it gives an error and the phone tells me it has stopped working.
2)Keyboard entirely disappears, yet I can still type by touching the black area where the keyboard would normally be.
3)Keyboard doesn't disappear, but text entered doesn't appear inside the text box until after closing the keyboard.
4)Keyboard crashes normally, causing either (2) or (3) to happen.
I'm unsure what's going on. I am running a rooted system, so I'm guessing it may be some issue with the root combined with something I've installed, but I'm unsure what it could be. Keyboard was (and has been) working fine for months and months, and I haven't installed anything new since the day I rooted.
I'm rooted with Rooted Community Rom. I've not had any problems with this root since I've installed it, so I don't know what the Hell is going on. Any input would be wonderful, especially if someone could tell me what's causing this to happen, or if others have this issue.
BobScramit said:
1)Normal keyboard crash, where it gives an error and the phone tells me it has stopped working.
2)Keyboard entirely disappears, yet I can still type by touching the black area where the keyboard would normally be.
3)Keyboard doesn't disappear, but text entered doesn't appear inside the text box until after closing the keyboard.
4)Keyboard crashes normally, causing either (2) or (3) to happen.
Click to expand...
Click to collapse
I'm thinking 1) is due to Low Memory causing Force Close (due to many running apps) or the Keyboard App data somehow got corrupted and 2) and 3) are happening due to GPU not being able to draw the Keyboard and letters when called upon; can't entirely be sure unfortunately.
I can think of two solutions to try however:
Clear Data and Cache of Keyboard App
Go to Settings -> Apps -> ALL -> Keyboard
Select Clear data and Clear cache
Reboot or start a messaging app and start typing again
Try another Keyboard App
Many options available, try: AOSP Keyboard, Google Keyboard, Swype
Hope that helps!
Clearing it and letting it reload does fix all of the issues, but it just happens again shortly after. I don't have very many apps, and normally still have around 100MB RAM free at all times. I don't use social media or anything on the phone at all, and most everything else is just Google things, Kik messenger, and stuff pre-installed on the phone(Like the normal sms app, phone app, etc) Reboot, clearing memory, etc, all have the same result. Fixes the problem, only for it to happen again shortly afterward. Sometimes, in the case of the keyboard going blank, clearing memory doesn't fix the issue. It re-loads with a blank keypad. Doesn't happen very often, but it did once or twice today.
I've tried using Swype since it's already pre-installed, but it's not really the same size as the standard keypad and it's difficult to adjust to typing on it :\ I suppose I'll have to make due with using it for now, because that keypad doesn't seem to freeze or crash at all as I've used it (wasn't for very long, but the normal keypad tends to crash at least twice within the span of an hour if it's used regularly).
It wouldn't even be a problem if it wasn't happening so damned often. I'm used to things crashing at random, because having a load of apps (before) caused it to make things crash sometimes. But this is definitely not a "sometimes" issue. It's a "Please God, make it stop" issue lol
BobScramit said:
It wouldn't even be a problem if it wasn't happening so damned often. I'm used to things crashing at random, because having a load of apps (before) caused it to make things crash sometimes. But this is definitely not a "sometimes" issue. It's a "Please God, make it stop" issue lol
Click to expand...
Click to collapse
I know how that feels. I remember experiencing those keyboard symptoms you mentioned in the past. Frankly, I couldn't leave the stock ROM fast enough.
You should try AOSP or Google Keyboard, the keys are bigger and appear less confusing than Swype.
Related
Maybe we can start a sticky thread about applications that are not working right on the Eris. I don't mean apps that are designed for another version of Android, just apps that don't work for one reason or another(this could include apps that keep force closing).
Pandora can cause your phone to reset your phone then cause major force closes which require a factory reset to fix. It's not every time but it happens to me
PDANet force closes alot. And, brings my laptops internet with it. Sad days.
Grooveshark has the habit of not downloading music to play while on mobile network. It will try, fail, and wait for you to pause and play it again.
I had an odd problem the other day: when I rotated my phone to landscape the screen would fade to black as it was being rotated. Found this out by trying to use camera and had to do a factory reset in the options menu. Big pain in the ASS. Never had so many problems with my G1 or MT3G. Come-on HTC get the Eris together, this is not the only problem I have had either.
Iheartradio once in a while force closes. Also, not sure if this is an issue of the Eris(due to 3G connection issue not fully fixed), or an issue of the software, but certain stations cause my Eris to freeze a second and the won't work(I never been able to connect to a few stations).
For me it was Task Panel. After I did the manual update, every time I exited task panel, I got stuck on HTC screen for a while. I had HTC sense, HTC touch input, and thing needing to run on Ignore list, so I know they were not killed by task panel. Finally I deleted it and am fine....although am itchin to keep checking my memory
Note: I just blogged about it and planning on posting on few Googler's twitter to see if we can get some attention to fix these issues, if they already haven't started looking in to these! If you are interested, please visit "Is the latest Gingerbread (Android 2.3.3) OTA update for Nexus One buggy? "and share your experience with Android 2.3.3 on your NexusOne's the Android team can get a bigger picture of these issues! More the merrier!
By now, I have reset to factory default couple of times but still after about 50hrs of usage my Nexus One starts acting freaky! Performance slows down, launching apps gives me black screen, lock screen freezes until I receive a call and not answer it and finally forcing me to reboot the phone.
Is anyone else aware of these issues or experiencing these issues?
I've had a few, repeated issues since upgrading to Gingerbread:
The stock messaging application will sometimes crash after sending a text message. The message gets sent, but the program closes out and returns me to the home screen. When I try to get back into the app, it animates like it is opening, animates like its closing and then gives me an error message about it not responding. I have found the only way to get rid of this is to reboot the phone.
Occasionally, all of the items - icons, widgets, etc - will disappear from the home screen. All I can see is my background image (just a plain JPEG, nothing animated) and cant get anything else to happen. I've tried to give it a few minutes (coming from Windows Mobile, I've learned to be patient) but it never came back. As expected, only a full reboot of the phone fixed the problem.
I've been having strange WiFi and data connection problems. Sometimes when connecting to WiFi it takes several minutes to establish a working connection; however most times it is pretty instant. The data connection will sometimes completely drop out and not come back on its own - even in areas with known good signal (I'm on AT&T, insert jokes here). Again, the best solution I've found is a full reboot.
I have heard some reports from friends that they have experienced issues with Exchange support after the upgrade, but I haven't seen it personally. Other than those above issues (which are very annoying) Gingerbread is has been OK. As I like to tell everyone, I'm sure glad my phone makes a cool TV of animation but can't seem to want to send text messages... Thanks Google?
monkeyboy0076 said:
I've had a few, repeated issues since upgrading to Gingerbread:
The stock messaging application will sometimes crash after sending a text message. The message gets sent, but the program closes out and returns me to the home screen. When I try to get back into the app, it animates like it is opening, animates like its closing and then gives me an error message about it not responding. I have found the only way to get rid of this is to reboot the phone.
Occasionally, all of the items - icons, widgets, etc - will disappear from the home screen. All I can see is my background image (just a plain JPEG, nothing animated) and cant get anything else to happen. I've tried to give it a few minutes (coming from Windows Mobile, I've learned to be patient) but it never came back. As expected, only a full reboot of the phone fixed the problem.
I've been having strange WiFi and data connection problems. Sometimes when connecting to WiFi it takes several minutes to establish a working connection; however most times it is pretty instant. The data connection will sometimes completely drop out and not come back on its own - even in areas with known good signal (I'm on AT&T, insert jokes here). Again, the best solution I've found is a full reboot.
I have heard some reports from friends that they have experienced issues with Exchange support after the upgrade, but I haven't seen it personally. Other than those above issues (which are very annoying) Gingerbread is has been OK. As I like to tell everyone, I'm sure glad my phone makes a cool TV of animation but can't seem to want to send text messages... Thanks Google?
Click to expand...
Click to collapse
You are right, I've been having those home screen issues as well, though my wifi connectivity seems to be fine so far.
Sent from my Nexus One
http://mindmirror007.blogspot.com/p/home.html
I can confirm Gingerbread on my N1 facing similar problem. Riddled with bugs such as battery drain, Wifi, Exchange Server, Date format on Notification Bar, Awake forever, just to name a few.
REverted back to 2.2.2 More stable amid less 'cheeky' in term of UI.
Also had force close issues with launcher and other programs getting a black screen after about 2 days without a reboot. Got tired of it and went back to Froyo
I've had trackball notification issues. First it stopped working entirely. After a restore it now only blinks notifications if the screen is off. Once the screen is turned on (even if the phone isn't unlocked) it stops. If the screen is on when the notification is recieved nothing happens.
I'm experiencing battery drain that i believe is associated with maps and location services (the alogcat shows it checking in all the time!).
I've had the launcher become unresponsive to touch. You can use the trackball to navigate, its slow, and once you're inside an app it works fine. Need to restart.
I've had the blank keyboard show up and need to restart.
I'm probably going to switch back to 2.2.2 tonight...
Wow! The issue seems to have touched a lot of NexusOne's. I just blogged about it and planning on posting on few Googler's twitter to see if we can get some attention to fix these issues, if they already haven't started looking in to these! If you are interested, please visit Is the latest Gingerbread (Android 2.3.3) OTA update for Nexus One buggy? and share your experience with Android 2.3.3 on your NexusOne's the Android team can get a bigger picture of these issues! More the merrier!
I have also been affected by the "black screen" problem after about 48 hours uptime. Returning to the home screen shows just the wallpaper and no icons. Pressing the "Home" button worked for a while to bring back the icons, but eventually most apps started showing some black screens and I had to reboot to fix the problem. I'm sticking with Gingerbread 2.3.3 for now, but it is disturbing after the multi-week uptimes I was getting under FroYo 2.2.2.
I wish I could explain better what I did, but I can't figure out what it might be.
I am running Captivate rooted, mostly stock 2.2 with a modded camera app, and sideloaded apps allowed (for the Amazon market). The behavior is this:
Phone takes about 5 minutes to boot, was previously booting in maybe 1-2 minutes before launcher comes up. Launcher loads and i have a slow but usable phone for 30 seconds then phone freezes, and maybe a few minutes later, launcher will restart. this whole time, i am getting double vibrate every few seconds, like something is freezing/crashing in the background (that's my best guess). I disabled all Widgets in both launchers and it does not hookup via USB once it freezes, but will charge.
This is happening with Samsung TWlauncher and with LauncherPro. Thinking this was a LauncherPro issue, I switched default launcher to TW, but same behavior occurred. I also uninstalled LauncherPro, but still no change in behavior for default launcher. I would like to try to get back to a usable phone, or if worse comes to worse, get my data off the phone before reinstalling either stock, CM7, etc. I do not have a phone recovery as I could never seem to get the clockwordmod recovery to install, so I only have reset user settings as an option from default recovery mode.
The only thing I can remember doing when this started was changing LauncherPro memory presets to see if it would stop restarting often, so I thought maybe LauncherPro was the issue, but it does not appear to be.
I reinstalled LP during a few hour period of usability, but then it occurred again and it took all day to have the right moment of unlocking my phone and getting to be able to uninstall LP before it froze again. If I wait too long to unlock, it is frozen until I restart or pull battery and try again at first bootup before the launcher goes crazy.
My main question is this:
Is there a way to determine which app is causing the problem, pull logs, etc. when the phone is off, and does not connect on USB (when it's frozen)?
If not, is there a way to pull data under same circumstances? (I'm guessing this is tied into the first answer)
If these all fail, I guess I will probably go to CM7 and try that out, but I have a hard time finding out what known issues there are as it still appears in unofficial status, since there's no downloads from the Cyanogenmod site.
Any help or advice is greatly appreciated. This has been a hard one to search for, so if anyone knows of other instances of situations like this, I would be glad to see what else was encountered. If I have this in the wrong forum, please forgive me.
Ever since Android 11, of which I am running Magisk, I have lately been getting these strange occurrences where my device will stop loading apps and slowly things will start breaking down in the system UI. If I try opening an app that is not already opened, it will simply keep me on the screen I was on, such as the lock screen or the notification shade, and tapping on the screen does nothing. I can swipe up to go to home then, and when I open recants it shows me the app with a transparent or black window. Then things such as screenshotting, screen recording, and the settings app will stop working, so I cannot try to force close an app. Because of this, its somewhat difficult to demonstrate and record. If I close an app that was open before the lockup and try to reopen it, that app meets the same fate.
The only way to revert these changes is with a reboot, and I haven't seen it occur when I have Magisk disabled. But it does take a few days of the device not being rebooted (which I have a habit of doing) to occur.
I've seen the same things on occasion... though I also had EdXposed installed, so I blamed it on that.
Eventually all the issues started stacking up and I decided to do my first ever factory reset and install fewer things. Hasn't been set up long enough to decide what's fixed. Though the factory reset caused a bunch of other issues, which annoys me.
Ever figure this one out?
Hi Everyone,
It has been going on for roughly a year now, while I'm using my phone it suddenly just freezes entirely. Touchscreen just becomes unresponsive, can't tap on anything, gestures don't work and notification bar can't be pulled down.
Physical buttons does not seem to be affected, even if my screen is totally frozen I can still adjust volume levels and I can lock the phone via the power button. After locking and unlocking my phone, everything goes back to normal, touch responsiveness comes back and starts working as it should till the next hiccup.
It happens frequently, there are times when the screen locks up 2 or 3 times in a 10 minute period window. Every time this happens, I need to lock and unlock my phone and it starts working again.
Also it doesn't seem like a specific application is doing it, it happens when I'm browsing websites via Google Chrome, it happens with Amazon App, Messenger, Google Play Store, even on the Google News feed.
It gets more and more annoying as time goes by and it still hasn't been fixed.
I have been in contact with Google Support in the beginning when it started, but all they suggested is that I should do a Factory Reset (which I did).
Has anyone else experienced this issue or is it just my device doing this?
PS.: My phone is fully stock, hasn't been messed around.
Any physical damage to the device? & Have you tried checking if the issue occurs in safe mode too? If it is caused by a 3rd party or background app it wont replicate in safe mode.
Scan with Malwarebytes.
Try clearing system cache.
Try safe mode and a hard reboot.
That qualifies for erratic behavior and may be the only sign of a virus or trojan you'll see... at first.
Either way you could be headed for a boot loop.
Regardless even if Malwarebytes finds nothing it's factory reset time. Nuke it; a trojan can do a lot of damage to you in a short amount of time.
After the reload change your Google password.
Before you load -anything- make sure the issue is gone!
If it persists it's either a firmware or more likely a hardware failure.