Error in helloandroid tutorial

by Qin XiaoYang » Mon, 23 Nov 2009 13:51:33 GMT


Sponsored Links
 Hi all,
I met the following error message appared on the emulator screen.
 "There's a big error message saying that 'Application Android Keyboard (in
process com.android.inputmethod.latin) is not responding.' and asking
whether i want to force close it or wait."
Anybody knows why? Thanks.

--



Error in helloandroid tutorial

by Indicator Veritatis » Tue, 24 Nov 2009 09:08:35 GMT


 I haven't seen that error message. But since the name of the
application in the tutorial is certainly not "Android Keyboard", you
can safely force close it. My guess is that you should go ahead and do
that, and then look for the application ("Hello Android" or
"HelloAndroid") you made during the build and run that.

Normally, that application would run anyway, without waiting for you
to start it. But that does not appear to be happening, since you are
getting this other application in the way.

But all this is only a guess. If you are lucky, after a little while
you will see more knowledgeable answers in this thread.




--


Sponsored Links


Error in helloandroid tutorial

by Qin XiaoYang » Wed, 25 Nov 2009 00:06:13 GMT


 Thanks for you help, in fact the application runs normally after force close
the message box.
I was just curious about why this error message appeared.





>



Error in helloandroid tutorial

by AJ » Mon, 14 Dec 2009 06:08:35 GMT


 I was wondering if you found out why do we see this error. I am having
this error too with Hello Android App.

--AJ







> >



Other Threads

1. variable tooltips

Sometimes when I am debugging in eclipse I can see the variable value
in the tooltips and sometimes I can't, it just shows me the type.
Does anyone know what I am doing wrong?
--~--~---------~--~----~------------~-------~--~----~

2. Stressing the Contacts sync to death (acore again...)

Dear experts,

As hinted earlier, I've hacked up a little service called "Zap's Hitta" 
(available for free on the Market) which basically takes the incoming 
phone number and pulls various info from public phone catalogs (only 2 
implemented so far) to both show more details about who calls you in a 
Toast and also update your Contacts with more data.

It works pretty well IMHO, though it could do with some visual polishing.

However, it appears that what I do will somehow also potentially stress 
the sync process (specifically Android.process.acore) to die. Here is a 
summary of what I experience:

* As long as I just use the system "passively" - that is: stuff is only 
added to Contacts when calls arrive - everything is hunky dory.

* Using a (crude) ExpandableListActivity to show existing phone numbers 
(standard stuff I found in an example here) works seemingly perfectly. I 
have 1000+ Contacts that scroll by perfectly fast and expand as needed, 
seemingly without eating memory (I see no calls to onLowMemory nor do I 
run out of file descriptors.)

* Trigging a few of the numbers in the list to fetch data also works 
just fine (I can't see any file descriptor leaks or significant memory 
allocation).

* However, if go somewhat wild and start pulling down names+addresses 
for a lot of the numbers in my phonebook (note: just one by one in 
sequence) I will set off the sync process (acore) too and this is where 
the trouble starts:

My ExpandableListActivity obviously runs a top level query over 
People.CONTENT_URI with a SimpleCursorTreeAdapter for each person's 
phone numbers (standard stuff from this list/example).

When the sync process starts, my Activity will slow down significantly 
and if I keep going it will seem to freeze for a few seconds now and 
then (presumably when acore is busy), after a while I start to get those 
classic annoying warnings (the log file warns about this much earlier). 
Still, between hangs things keep working.

However, if I keep going, I can see in LogCat various activities being 
restarted and in the end my app will be killed too - according to the 
log the reason is that acore has been killed and my app relies on it and 
hence must be killed too (that's not the exact wording, but I can get it 
if you need).

My main question is of course: Is this a bug/limitation or just me being 
stupid/naive about how to implement this? Sure, I may add an 
Organization and a Postal address every 5-10 secs or so, but that's not 
particularly extreme IMHO, is it?

A side question (hinted in an earlier thread, but I got no response - 
bumpiety-bump ;-)) is whether there is any possibility to skip my 
ExpandableListActivity completely and instead "teach" the standard 
Contacts app to optionally call my service from the ContextMenu that 
currently includes "Make default number". (I know going the other way of 
my calling this activity isn't possible.)

BTW: This acore issue is very different from the one I reported in bug# 
2377 - the data here is perfectly legitimate as far as I can tell and 
will sync fine if I leave the phone alone.

All advice appreciated - keep the good stuff coming...

                Best / Jonas

--~--~---------~--~----~------------~-------~--~----~

3. HTTPS connections through the browser, from within application

4. A simple question about a particular intent...

5. .text alignment problem

6. ImageView 's layout_width and layout_height

7. ScrollView and Programmatically Scrolling