In my Android app, the soft keyboard is working properly, but the physical keyboard is not working. I could not find out the reason for this. Is it due to any coding mistake of my app, or my phone's issue?
if issue in emulator
then try this
this is android AVD manager issue.
go Window -> ADV manager
then select Emulator and press Edit Button
then go Hardware section and press on New
after press new select property Keyboard support and press OK
and Set Value TRUE
and is issue in phone then try this
i would go to settings>language & keyboard... and check you keyboard settings... see if "shortcuts" is ON... Also, try clearing out "Learned Words"... that usually helps with any OS keyboard issue... :-)
if not, then get 1-click Cleaner from Market... its free... download... install.. run it... afterward run, turn phone off... remove battery... wait 2 min... insert battery and turn on... work now?
if not again... then you may need to do a factory reset... yes this will earse any data you put on the phone... except the SD card and SIM---these 2 will not be touched... but the internal memory will be wiped to factory settings---the way it looked on day 1 minute 1 of when you first got the phone...
if factory reset dont help the issue... then call tmobile to get a replacement... the g2 is OLD and i highly doubt your warranty is still active... you may need to upgrade or get a insurnace repalcement.... both needs money!.... good luck!
Source(s):
Sincerely,
Related
My Android emulator crashes whenever I press keys on the pc keyboard or hit the emulator side buttons. the only part that works is the emulator mobile screen. This doesn't happen to just one device but to all emulators I use. This is really annoying cause whenever I press any key on the keyboard while the emulator screen is active it will instantly crash. But keystrokes won't crush it when text input is active on the emulator screen. The operating system I use is ubuntu but Windows fix is also useful.
I need help from someone who has managed to solve this problem before.
I'm pretty sure I got this error before too. Whenever I pressed a button, the emulator would just say "Saving State..." and just closes. The only solution I found to fix this was to delete the emulator and create a new one. It's not the most effective solution, but I couldn't find any other solutions.
Really weird issue but when I try to click once it doesn't register on the emulator but then I click again and the click registers. This is using AVD. Every other click seems to trigger in the proper place. This has nothing to do with my app just base image.
Take a look at this:
https://www.youtube.com/watch?v=axvxtGj4HPo&feature=youtu.be
and notice the first click doesn't register.
I notice the age on this thread, so not sure if you have already figured this out. I ran into something similar like this today in which no clicks were being registered at all. This issue still persisted even after closing and reopening the simulator. One thing I did notice is that the power button still worked.
I ended up fixing this by:
Clicking and holding the Power Hard Key
Restarting the device OS by clicking the Restart
After the OS Reboots, everything seems to work again.
Note: the Hard Key for power is the power button next to the volume controls on the right.
In my case it usually happens when the size on disk is very high (see in AVD Manager) and the solution in my case is to make a Wipe Data
Update #1 (Because the solution from above not always works)
Another thing I found is that when you want to swipe up from the Google bar does not open the apps menu. Then I open first the Messages app or Chrome and close again. From there the Swipe up works again.
I created a brand new emulator today but it is behaving weird today. Here is my setting:
When i start it up, it loads fine. Until it gets to the lock screen. I keep on dragging/swiping from bottom to top to unlock, but it wont! This is the first time I encountered such behaviour. I tried with target Android 6.0 - API Level 23 but was able to unlock. I want to test my app on Google API 23. Please help to figure out the proper setting values.
Happened to me as well.
Another solution in addition to what #TTRansmit suggested is as below:
Close emulator.
Go to AVD manager screen, edit your Emulator and go to Advanced Settings.
Select Cold boot as Boot option located in Emulated Performance section. This way you will be able to restart your emulator and get it unlocked without loosing data.
Power off (via holding power) on the device buttons and wipe data (from Android Virtual Device Manager) worked for me. It was turning off the Device Frame from the edit/Virtual Device Configuration screen of AVD that seemed to cause the problem.
I still did not solve this problem, somewhat. To get thru, what I did was I activated the Camera emulation then relaunched the emulator. On the lock screen, I dragged the Camera icon. The camera would crash and emulator would notify you about it thru a pop up dialog. Once you exit the dialog, it will go back to your homepage UNLOCKED! I know, it was weird but it worked.
I am keep getting this each 10 sec. What is it about? How can I fix this?
This problem is not related to any app I created, it just happens on emulator I work on in eclipse. I thought it's some common 'error'. I may just lunch avd, unlock the screen and wait few sec for this message to comes up.
This is my very first contact with android emulator, so I am not that fluent, didn't know what else to post. I found logcat but it is empty.
These chinese characters say:"Google's PinYin input method",so I guess this problem is related to the input method(PinYin is a way to mark the pronunciation for a character with Latin letters) . It seems that this happens when you are inputting something in the TextView. On the emulator, there is a native Google PinYin input method and perhaps this app has something wrong. Please disable it or create a new emulator.
Actually, how is your app on a real device?
There is probably a Japanese keyboard trying to run, turn it off from Settings->Language & Keyboard
Being a couple of days into Android development, I encountered the same issue. It only began, however, after I was playing around with the system settings of the emulator. I could have sworn that I didn't change a thing in the languages and settings menu. But, since I did inspect it and this dialog did appear, I'm sure it did. My emulator has mucho latency due to the fact that my dev machine is a few years behind the times ( a good development practice btw.)
So, I did the following:
enable: system settings->Dev Settings and check Show cpu usage
this shows you all android processes running. You will see:
com.android.pinyin
just before the error.
google that error and hopefully come across this post.
go back into system settings->Language and input and change the default back to English.
I was having the same problem using the 4.0.3 WXGA800 emulator but could not disable the Chinese keyboard nor the Japanese IME keyboard since the check mark was greyed out (not blue). I was about to post a question when, by mistake, I clicked on the Default option, cycling through the different options until I came back to English (US). After that, fortunately the message stopped appearing.
I tried to post an image to show the check marks and the Default option, but as a new user was not able to.
I have the same problem as #Bobby, from Android +4 the check is unavailable. The solution was to disable the Chinese application. To make disable go to "Settings" > "Apps", tap on "ALL" option in the action bar tab on the top, and at the end of the list you will be found the application, then tap in the item, and in the next screen make click in "Force stop" button and "Disable" button.
This is my fix:
Settings > Language & Input > Keyboard and Input Methods > Default > English (US)
Changed default to another language and then back to English (US)
Message hasn't appeared for over 9000 seconds
The log tab is visible in DDMS and I have been logging data using Log.v(...) for many a week now without any problems.
Today, the log data is now longer being displayed in the Log window. Worked, then did a programming change to track a bug and now the log data is no longer showing.
Have tried running the app on an external Android phone, on the Android Simulator and it makes no difference.
Have closed down Eclipse, reloaded and still no change.
The console displays activity but only to the point of starting the activity.
The external phone is set up for debugging - not that this could be a problem since I have the same problem with the simulator
It looks like I have inadvertantly set something incorrectly but can't remember changing anything :-(
Anyone come across this problem before - have looked at previous posts but none seem relevant.
Regards,
Oliver
I had the same problem a while back. I was using the emulator and device for debugging. Apparently you have to select the device listed in the DDMS view whose logs you want to see. My logs were blank because the device that I was expecting logs from was not the one selected.
Hope that helps
Tried this:
https://stackoverflow.com/a/9826502/1238317
Check in your logcat window - TOP RIGHT corner PAUSE button || (Pause
receiving new logcat messages)
Few clicks + eventually restart eclipse (usually works in my case)
Check your LogCat window to see if you are filtering and make sure to set the debug level to Verbose.
There are possible reasons and solutions:
LogCat might have to much in cache, clear the log and see if it fixed the issue
You might need to select the device in the device view (even if it is already selected, try to click on it)
adb is not correctly working anymore, try to kill and start it again
Check if you see output if you use the command line adb logcat
Just go to DDMS perspective and click on the device's name in upper left corner and done your log cat will Start with a BOOm :P
In Android Studio, which I have found to be much more reliable and intuitive than Eclipse, I found this to be a common issue. For me what solves it (device is automatically set when running your app) besides checking code, is to Quit and restart the emulator or Quit Android Studio and Emulator and reopen/restart