camera handler crashes after camera release [36912779]

Obsolete

Bug

Status Update

No update yet.

Description

wi...@gmail.com

created issue #1

Jan 22, 2010 11:14AM

- Steps to reproduce the problem.

An application that subscribes to preview frames
and then calls Camera.release()

- What happened.

Looks like a race-condition.

Camera preview buffers are passed to the application as messages, so its
asynchronous. If a preview buffer happens to be processed *after* the
camera has been released, and there is a preview callback assigned, then
then an exception is thrown and the thread dies.

Stacktrace:

D/AndroidRuntime( 3404): Shutting down VM
W/dalvikvm( 3404): threadid=3: thread exiting with uncaught exception
(group=0x4001b178)
E/AndroidRuntime( 3404): Uncaught handler: thread main exiting due to
uncaught exception
E/AndroidRuntime( 3404): java.lang.RuntimeException: Method called after
release()
E/AndroidRuntime( 3404): at
android.hardware.Camera.setHasPreviewCallback(Native Method)
E/AndroidRuntime( 3404): at android.hardware.Camera.access$600(Camera.java:58)
E/AndroidRuntime( 3404): at
android.hardware.Camera$EventHandler.handleMessage(Camera.java:331)
E/AndroidRuntime( 3404): at
android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3404): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 3404): at
android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime( 3404): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 3404): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 3404): at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime( 3404): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime( 3404): at dalvik.system.NativeStart.main(Native Method)
I/Process ( 71): Sending signal. PID: 3404 SIG: 3
I/dalvikvm( 3404): threadid=7: reacting to signal 3

- What you think the correct behavior should be.

The camera preview handler should discard preview frames it gets when the
camera has been released.

This keeps happening to my users on Nexus 1; have not reproduced on other
phones (but the issue may of course still be there).

Comments

de...@gmail.com <de...@gmail.com> #2Jan 22, 2010 05:13PM

Google even has a DroidSansJapanese.ttf font in their Android Git repository, and this appears to be included on Android devices in the Japan domestic market. Why international Android devices do not include this font boggles the mind.

wi...@gmail.com <wi...@gmail.com> #3Jan 22, 2010 10:28PM

This issue *must* be fixed. It is turning Japanese-using people off Android platforms.
Jim Breen

jo...@gmail.com <jo...@gmail.com> #4Feb 17, 2010 09:03PM

Hello. I'm too really annoyed with this bug. It makes impossible to study Japanese with Android, as some kanji are really different. Some applications (Obenkyou for example) allows to change the font, but most applications or webpages doesn't render correctly.

I'm using Android 4.0.2 in the Samsung Galaxy and it's still there.

Please, fix this issue in the next releases. Thank you.

de...@gmail.com <de...@gmail.com> #5Feb 18, 2010 09:14AM

I've just updated to Android 4.0.4 and the problem is still present :(

It doesn't look as if anybody at Android Development Team is interested in this issue.

ra...@gmail.com <ra...@gmail.com> #6Jul 21, 2010 06:00PM

This is a very frustrating issue. I'm studying Japanese and if this isn't fixed I won't be getting another Android phone.

Thanks for the tip about Obenkyo, ncc1701.

ma...@hotmail.com <ma...@hotmail.com> #7May 29, 2011 12:24PM

Yes this is really annoying, I don't want to root my phone to fix this.

Please! Something has to be done, I can't belive this hasn't been fixed.

xi...@gmail.com <xi...@gmail.com> #8Jun 5, 2011 06:18AM

I'm looking for mobile device for learning Japanese. I think of Android devices but I'm not going to buy one util this issue is solved.

ac...@gmail.com <ac...@gmail.com> #9Jun 21, 2011 06:51PM

The new Jellybean release (Android 4.1) makes some improvements, but it is far from complete.

From the developers:

http://developer.android.com/about/versions/jelly-bean.html

"Better glyph support for Japanese users (renders Japanese-specific versions of glyphs when system language is set to Japanese)".

So it seems that the new release will display correctly the kanji if the phone is configured set to Japanese, but not otherwise.

For me, it is very hard to understand that this problem is not yet solved, nor even acknowledged by Google :(

no...@gmail.com <no...@gmail.com> #10Jun 27, 2011 01:58PM

It's a step in the right direction, but it should be locale-based; not just based on system language. I guess just having Japanese rendering available will mean developers can probably use it.

ra...@gmail.com <ra...@gmail.com> #11Sep 4, 2011 11:19AM

please do something about this issue. I signaled it a couple of years ago in an anki software related forum. It's driving me nuts, having software like anki or aedict display the wrong characters.
I'm working on remembering all jôyô kanji and getting confused so often lately, not being sure if it's my memory failing me or the darn android character display issue.

I was in Japan this summer and all the people around me had android phones, with correct fonts of course, and it's just so strange having to explain that non japanese android phones can't display Japanese properly.

I also don't want to root my phone to fix this. Please do something (like use the same Japanese standard font used in Japanese android phones...)

b

ma...@gmail.com <ma...@gmail.com> #12Oct 5, 2011 10:02AM

I have to throw my voice in with the others here. I managed to root and update the font on my phone to display Japanese correctly, but on my new Toshiba tablet that has not been rooted and has a locked bootloader it is looking more and more like this will never be an option. It's somewhat ridiculous to me that this issue has existed for so long without so much as an acknowledgement that it will eventually be fixed.

an...@gmail.com <an...@gmail.com> #13Dec 18, 2011 04:45PM

I see this issue is still classified as "New" (after nearly 14 months!) That means "The bug report has not yet been triaged (that is, reviewed by an AOSP contributor.)"
(see

http://source.android.com/source/life-of-a-bug.html)
Also it's rated as "Priority-Medium".

How on earth do we get it triaged? Will it just stay bleeding in the hospital corridor.

fj...@gmail.com <fj...@gmail.com> #14Dec 20, 2011 07:01PM

Same thing here, I am learning Japanese in Tokyo and have been using Anki, Aedict, and JED for about a month, only to find out today that I was learning the wrong kanjis (the Chinese/Korean versions according to my teacher).
None of my classmates using iPhones have this issue, I wonder why Android should be different...

Please please please fix this!

fo...@gmail.com <fo...@gmail.com> #15Jul 2, 2012 11:18AM

the ankidroid issue can be fixed, but not the others.

To get anki to display correct kanji, you need to download the Droid Sans
Japanese font, then edit your anki deck on the computer to set all the font
fields in the card layout (deck properties) to Droid Sans Japanese
you then need to copy paste the Droid Sans Japanese in a font folder in
ankidroid (you'll need to create it if it's not there), and then activate
the "use custom font" option in the ankidroid options, where you'll see the
Droid Sans Japanese font. It works fine. Only issue I had was getting the
font's name right, in my compter anki decks the font is listed as Droid
Sans Japanese , with the spaces.
Doing this, Ankidroid cards will display the correct kanji, but the rest of
your android japanese display will still be inaccurate.
Hope this is fixed some day, it's ridiculous.

ben

xd...@gmail.com <xd...@gmail.com> #16Oct 8, 2012 02:08AM

The new Android version, 4.2, has been announced. Among the improvements, there are new Korean fonts and some unspecified improvements about internationalization. Let's hope this issue has been fixed.

ma...@gmail.com <ma...@gmail.com> #17Jan 28, 2013 02:40PM

I have Android 4.2 on both my Galaxy Nexus and Nexus 7 and sadly both are incorrectly displaying non-Japanese characters in the han unification Wikipedia link provided above. How can an issue like this still not be resolved yet???

je...@gmail.com <je...@gmail.com> #18Aug 13, 2013 01:21AM

I won't be purchasing another Android product until this is resolved. Apple has had proper Japanese display forever. Why can't Android?

sa...@gmail.com <sa...@gmail.com> #19Feb 27, 2014 08:41AM

I recently acquired a Nexus 7 tablet, running 4.2. It has Japanese fonts, and displays them properly (as far as I can tell) if the interface language is set to Japanese.

But when the interface language is set to English, by default kanji are displayed as the Chinese versions.

However, if you're willing to root your device, it seems to be easy to change this default:
+ root the device
+ remount /system read-write
+ save a copy of /system/etc/fallback_fonts.xml
+ edit /system/etc/fallback_fonts.xml, moving the lines

<family>
<fileset>
<file lang="ja">MTLmr3m.ttf</file>
</fileset>
</family>

to the beginning of the list, right after <familyset>. (I also took out 'lang="ja"')

+ Reboot the device in order for the changes to take effect.

And if you don't understand those instructions, find someone who uses Linux to help you.

[Deleted User] <[Deleted User]> #20Aug 25, 2014 04:34PM

Given that jellybean features such a gorgeous Japanese font built in, this is a deeply frustrating problem with such an easy potential fix. If it's too much to ask Android to distinguish hanzi from kanji, at the very least give us a simple switch to choose whether Chinese characters are displayed as kanji or displayed as hanzi. I'm fed up of changing the language of my entire system just to read Japanese text properly. No other OS I've ever used has suffered from this.

en...@google.com <en...@google.com> Dec 8, 2014 01:33AM

Status: Won't Fix (Obsolete)

ke...@kerrickstaley.com <ke...@kerrickstaley.com> #21Dec 12, 2014 07:12AM

I find Android's silence on this matter disturbing. Do they not investigate what users really need? The fix in jellybean is really half-baked. As an open-source devotee, I'd like to recommend Android devices, but instead I have to alert people wanting to use Japanese that there is a major problem that Android is simply ignoring.

jo...@gmail.com <jo...@gmail.com> #22Apr 2, 2015 11:17PM

Can't believe this issue is still "new" and it's been over 1 year since it was first reported.
Seems really easy to fix ...

bo...@gmail.com <bo...@gmail.com> #23Apr 1, 2017 11:55AM

Android 4.3 on Nexus 4, STILL not fixed.
On my old rooted HTC Desire S, I just installed a font with the name DroidSansJapanese.ttf. Please just include this font on the next version, that's all that's needed!