Closed GoogleCodeExporter closed 8 years ago
Hi, diagnosing 'force close' issues is nigh on impossible without logs. You can
retrieve logs from the device using e.g. 'Log Collector' from the market.
Grateful if you could attach a log showing the problem.
Original comment by foobum
on 19 Aug 2010 at 5:01
OK. Here's a log. I have tried to de-htmlize it but not sure if I was 100%.
Looking forward to your analysis.
Original comment by brianjmu...@gmail.com
on 22 Aug 2010 at 10:25
Stupid chromium attached the wrong file, even after several attempts at getting
it's file chooser to select the correct file. This one should be the correct
file.
Original comment by brianjmu...@gmail.com
on 22 Aug 2010 at 10:27
Attachments:
Thank you. I've uploaded a 0.3.6 apk
(http://code.google.com/p/mythdroid/downloads/detail?name=MythDroid-0.3.6.apk)
that includes a number of changes that have gone in since 0.3.5 was packaged.
Hopefully they include a fix for this. If the problem persists with the new
version, please upload new logs.
Original comment by foobum
on 23 Aug 2010 at 2:29
Yeah. 0.3.6 doesn't seem much better. Attached is a log from trying to watch
recordings. In this case, it said it could not even find any.
Original comment by brianjmu...@gmail.com
on 23 Aug 2010 at 3:22
Attachments:
Looks like the problem is that you don't have any frontends defined. MythDroid
should now inform you of this instead of force closing as of r136. The 'no
recordings' issue is likely the odd protocol version issue that was fixed in
r134 courtesy of Justin Johnson. 0.3.7 binaries on the way soon.
Original comment by foobum
on 7 Sep 2010 at 11:48
Ahhh. OK. So I just configured a frontend and now "get" (i.e. understand what
it's all about) mythdroid. Unfortunately, not so much what I was looking for,
but neat all the same. Ultimately, for me, my handheld IR is more convenient
than tapping on a screen. Great interface for somebody who might not have an
IR remote though.
A real myth client on Android would be skookum though.
Original comment by brianjmu...@gmail.com
on 8 Sep 2010 at 2:42
Original issue reported on code.google.com by
z33k...@gmail.com
on 28 Jul 2010 at 5:37