{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Bombasti 的问题《WARN/ActivityManager(78): Launch timeout has expir》','https://www.manongdao.com/q-129628.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
As the title indicates i get this "error" when running my little app:
WARN/ActivityManager(78): Launch timeout has expired, giving up wake lock!
It came after I added this line to my manifest file:
<uses-permission android:name="android.permission.INTERNET" />
The reason I added that line was to get my app the abillity to connect to a serversocket. Read on another forum that the line would solve my problem (not being able to connect). And well it might have but instead I get that other error.
I'm totally new to android so don't understand much of that android specific stuff going on. Have some Java experience though.
Any help appreciated (:
BTW: not sure if I should have posted some of my code?
I had a similar problem retrieving a result from a php file in a server. I had solved putting php code inside
<html>tags. Without them the app was hanging there.Hope it helps
This error means your Activity is taking to long to start. If you are doing a lot of processing on the UI thread, Android kills your application. You should use AsyncTask for any processing intensive stuff.
If you could post your code and your SDK version, I can provide more help. There is also another thread on stackoverflow about this. Activity idle timeout for HistoryRecord?
I had a similar problem.
Inside my View.dispatchDraw(), I was calling a method that triggered another dispatchDraw().
(Adding a logline inside my dispatchDraw() showed that the function was called continuously. This did not show up when doing method profiling in Eclipse)
Hope this is helpful to someone.
Check if you don't have 2 or more Eclipse IDEs open (if that is your IDE of choice). It is possible that one of those is taken control over the parts of the ADB and refusing the others access. In my case, I experienced the same error, but when I closed every other Eclipse instance, the app started in debug mode immediately.