Samsung text-to-speech engine - T-Mobile Samsung Galaxy S 4

Hello everyone.
A perplexing issue: Using Maps Navigation, I prefer the voice that Samsung TTS offers (more natural). However, in my S4 with Wicked ROM v.3 there is no choice for English, so no street names are read. If I choose Google TTS all works fine.
There is no choice to download or install in any way, English. Several other languages, but not English.
Any ideas? I copied the APK from Wicked v.1 (where it worked) and pushed it to v.3, but no go.
I have frozen several things in TB, but nothing that should cause this....I think.
I can stick with Google TTS, but I'd like to figure this out.
TIA.

Pinan said:
Hello everyone.
A perplexing issue: Using Maps Navigation, I prefer the voice that Samsung TTS offers (more natural). However, in my S4 with Wicked ROM v.3 there is no choice for English, so no street names are read. If I choose Google TTS all works fine.
There is no choice to download or install in any way, English. Several other languages, but not English.
Any ideas? I copied the APK from Wicked v.1 (where it worked) and pushed it to v.3, but no go.
I have frozen several things in TB, but nothing that should cause this....I think.
I can stick with Google TTS, but I'd like to figure this out.
TIA.
Click to expand...
Click to collapse
Samsung English language TTS seems to be dependent on Samsung S Voice application. Does your ROM include S Voice?

james1375 said:
Samsung English language TTS seems to be dependent on Samsung S Voice application. Does your ROM include S Voice?
Click to expand...
Click to collapse
Thanks for the reply, but my post was from 3 months ago. *chuckle*
Turned out that version of Wicked had no English language installed for Samsung TTS. It was fixed later.

Related

Google Navigation + Voice search for Italian, Spanish, French available now!

Hi,
Today Goggle has enabled the vocal dictation and search for Italian, Spanish and French people.
I have a Desire with Froyo (DeFrost 0.7b) and I can confirm it works very well, but only for Maps and SMS/Email dictation.
It doesn't work for internet search and voice commands.
In addition for Sense users, the HTC keyboard at the moment seems to be not enabled. It works only from Android Google Keyboard.
Is there some developers available to help us having a complete search function on HTC Keyboard and voice searc/command (if possible to link to the new google language server) ?
Thanks in advance
Sorry for my english, as usual
vivus said:
Hi,
Today Goggle has enabled the vocal dictation and search for Italian, Spanish and French people.
I have a Desire with Froyo (DeFrost 0.7b) and I can confirm it works very well, but only for Maps and SMS/Email dictation.
It doesn't work for internet search and voice commands.
In addition for Sense users, the HTC keyboard at the moment seems to be not enabled. It works only from Android Google Keyboard.
Is there some developers available to help us having a complete search function on HTC Keyboard and voice searc/command (if possible to link to the new google language server) ?
Thanks in advance
Sorry for my english, as usual
Click to expand...
Click to collapse
THIS. Then go into settings and enable voice input for languages other than english. Works perfectly
Great News ! Really thank's!
MacCarron said:
THIS. Then go into settings and enable voice input for languages other than english. Works perfectly
Click to expand...
Click to collapse
Can you be more specific? Where is this setting? In HTC_IME settings or phone settings? I don't find anything like that :/
There's more to it:
http://googlemobile.blogspot.com/2010/06/fun-on-autobahn-google-maps-navigation.html

[Q] google navigation not using preferred text-to-voice language

My text-to-voice language is set to UK english and I have also enabled the 'force programs to use this choice' option yet the navigation app still uses the american english voice.
Anyone else seeing this on the desire?
Maybe the uk choice is not installed?
Swyped from Oxygen with Transparent XDA App
Both UK and US English packs seem to be installed and are available as language selections. The 'listen to an example option' indeed correctly uses the UK english voice, but google navigation refuses to honour that choice... Does anyone know where maps stores its language choice as it seems to ignore the 'voice input and output' settings?
(this is on close-to-stock gingerbread ROM with maps v5.8.0)
I had the same problem - it's annoying having a robot tell you what to do, even worse to have an American robot bossing you around.
After a lot of tinkering, the problem seems to be that Navigation gets confused if your global language and your text-to-speech language aren't the same. So you need to change your global language to English (UK) in Menu / Language and Keyboard / Select Language. The trouble is, the stripped down Gingerbread for HTC Desire doesn't have English (UK) as an option - only English (US). So you also need to run a little app called "Any Locale, a switching widget" (by leohoo) available free on the market, to let you select English (UK).
Once you have selected English (UK) as your global language, you can actually delete the "Any Locale" app to save storage space.
And ta-da! Annoying English robot is back.
Thanks, it does look like a Google Maps bug, but this works....
UK language
@ SolentUK
THANKS a bunch for that app info! Finally got rid of that American [email protected]%.
It's ok. I can say that. I'm American.
I love the British accent. It sounds just like Ferb from Phineas and Ferb.
Yeah, I like to watch cartoons.... still.
Speech in Navigation is stuck
OKay. Here's the scenario.
Got tired of U.S. female robot very quickly.
Selected English UK whch sounds like Ferb from Phineas and Ferb, if you watch Disney...
Had to use Any Locale to switch to the English UK
Work for a few days, then intermittently went back to U.S. Female robot.
Downloaded SVOX and the voice Oliver UK. He worked for weeks.
All of a sudden now, when I start Navigation(Google) the only things Oliver says is "50 feet". Tthen in about 20 seconds or so, he repeats "50 feet. 50 feet."
Reset all of the language inputs and even tried using different languages. Still Oliver comes on and says "50 feet."
Uninstalled SVOX and Oliver. rebooted phone, but still Oliver comes on saying, yep. you guessed it, "50 feet".
Tried resetting languages ifor the default and langauge inputs and text to speech...again and used Any Locale. Nope!
I know that Google Nav can be buggy a little, but c'mon!
Any help is welcome. I'm excellent at navigating and reading maps. Don't need a GPS, but damn it! It's supposed to be a feature that works, therefore I want to use it. It makes a fun toy.

Google Navigation Crash

Hi, since last update to gg maps i can't use navigation on the galaxy nexus, when it starts calculating the route it always crashes. I've tried disabling GPU render on settings but it doesn't matter. Anyone having this issue? I find it strange, considering it's a google app.
ps: yes, i've already cleared app data
Same problem
I solved it today as soon as I read your username (ruimoura) and saw the flag of Portugal. I got the same problem and I am brazilian.
So when I saw only you and me reporting this problem, I changed the language of my Galaxy Nexus to English (United States).
Bingo! The navigator worked perfectly...
I hope Google correct this bug, so we can use the Navigator on our language (Portuguese).
Thanks ruimoura for your indirect help.
Obrigado.
Dedemor
I think this is mentioned in other threads. Check your Pico TTS setting language in language and input settings. Set it to English if it is set to some other language
Sent from my Galaxy Nexus using Tapatalk
If someone doesent find the setting its Settings - Language & input - Text-to-speech output
Had this same problem - but now solved - Big Thanks !!
Ignore please Thought I had problem but I was being an idiot.

[Q] Talkback bricks Smartphone cause no speechpackage

Hi my friends,
a long time I have used my loved HTC HD2 and got a lot of help from your forum.
Best thanks for the HD2 support all the time to all!
But time is fleeting and so meanwhile I own a HTC One X.
After weeks of testing, now I feel familiar with Android.
My One X is a device with a Stock Android 4.1.1 with Sense 4+, SW: 3.14.401.31, SDK API 4.63, HTC Extension_Sense 45_1 build in Shanghai 2012/07
Only one thing is killing me...
The talkback doessn't work unfortunetely.
If I activate this function, I get a error-message, that tells: "Gesprochenes Feedback kann nicht hergestellt werden,da es keine Sprachdaten gibt" (a am a German) - what means "The feature 'spoken feedback' can not be established, because missing speechdata".
For me it is nessesary in double ways to get talkback activated and working.
First, I am a woman - and most important for women is to have smalltalk all the way
But as second, I have a little bad eyes, so it will be easier to recognise what my android does, if I can hear all orders and what my Smarty is doing.
Meanwhile I have installed "IVONA text to speech". With this speech-package maps-navigator speaks - before the navigator was dumb as well but talkback still shows the error.
Thinking some data are missing in my Rom - but I don't know how to fix this.
Can anyone help me to get talkback working?
kind regards
Veronika
Are you rooted? I have personally never tried or used talkback, and I'm not running a Sense based ROM now so I can't check. But if the problem is indeed missing files, I think that you should apply a RUU (be sure to download the right one) to your phone. Viel Glück!
EDIT: I enabled it on an AOKP ROM and it just didn't work. It said that Talkback stopped. Made my device unusable, had to preform full wipe in order to get it to work again.
Sent from my HTC One X using xda app-developers app
Hello Victor,
uh, I am so sorry that you had to reinstall your Android because your try to help with my problem. :crying:
But best thanks for your try to help me anyhow :highfive:.
I own a standard unchanged, unrooted HTC One X with the origin firmware (thinking it is named 'Jelly Bean' - V 4.1.1) - no brandings ore some like that on the device. More information about it's versions I have written in my opening posting.
After buying the One X, I have tested it a few days, then I returned it back to factory settings after I have feel a little familiary with Android.
Since then I just have installed some applications onto it. Not more..
Meanwhile I found out, that TalkBack should come with a integrated voice named Pico TTS.
But on my device, this voice is not listed in the Text-To-Speech (no voice is in there after factory reset).
Perhaps no german voice is availiable for Pico?
Cause of the missing Pico, a activated Talkback is lagging the device and makes it nearly unuseable.
After recognising this, I have installed 'IVONA TTS' what should work with Talkback, as the webpage of IVONA says.
Now if activating Talkback, it does not lag the device anymore.
But here the german voice 'Marlene' (probably not the 'Dietrich' ) won't speak.
Neither in the voice-test screen of IVONA nor in any applications.
So the speech-machine of IVONA seems to work fine, but there is no audio voice coming with.
All volumes, I have set to 100%. This couldn't be reason for dumbness.
So I tried 'SVOX'
With installed 'SVOX' TTS and the both availiable german voices for, the google navigator speaks, but not the TalkBack.
Perhaps SVOX just support applications, but not TalkBack.
Does anyone knows a TTS-System what works with german voices together with TalkBack, eBook-Reading, Navigator and so on?
Or is it possible to download the origin Android 'Pico' (if availiable with german voice) somewhere for reinstalling this, perhaps.
Wish to get a nice Sunday to all
Veronika
I got it finally
Just now, desperately I bought the german voice from SVOX, named 'Petra' - even though the demo hasn't work.
In principle I did this with no hope finally to get SVOX running with, but as last option.
After downloading and installing this both program-parts (speech machine + voice) of SVOX, I was gladly surprised to find SVOX as well as IVONA both as chooseable options in the 'text to speech' settings page.
No more a grey "test example" below, but it is written in black letters now and useable.
Some in the SVOX voice makes IVONA working likewise.
Thinking in IVONA some part is missing, what comes with payed SVOX.
The SVOX voice 'Petra' isn't really understandable in all, but 'Marlene' from IVONA nearly sounds perfect.
And IVONA even is free as long it is in Beta-development.
So I had to buy SVOX to get IVONA working.
But this Marlene-Voice from IVONA sounds as good, I will buy it surely, if the Beta-period is finished some day.
Now, my Andoid speeks to me!!!
Absolutely wonderful and it makes my day.
Perhaps this Thread can help others with same problems.
- Install IVONA machine with any voice
- Buy and install SVOX Classic machine with any voice
- Choose in 'Settings' - 'Input help' the voice you want to get
That's it...
Much greetings from the german Bavarian
Veronika

[Q] Samsung keyboard missing Japanese IME on N7100?

Hello,
Samsung keyboard default doesn't support Japanese IME on Galaxy Note 2 N7100 so I wonder if I can install addition pack or flash a cook ROM to make the Jap IME available ?
I know I can install another keyboard which supports Jap but I don't like it because it's inconvenient for switching keyboard every time.
Thank you.
IT_Fan said:
Hello,
Samsung keyboard default doesn't support Japanese IME on Galaxy Note 2 N7100 so I wonder if I can install addition pack or flash a cook room to make the Jap IME available ?
I know I can install another keyboard which supports Jap but I don't like it because it's inconvenient for switching keyboard every time.
Thank you.
Click to expand...
Click to collapse
Japanese has its own stock samsung keyboard separate from the Regular Stock keyboard. You'll need to get that apk and then get the necessary libs for it. Its annoying thats for sure.
IT_Fan said:
Hello,
Samsung keyboard default doesn't support Japanese IME on Galaxy Note 2 N7100 so I wonder if I can install addition pack or flash a cook room to make the Jap IME available ?
I know I can install another keyboard which supports Jap but I don't like it because it's inconvenient for switching keyboard every time.
Thank you.
Click to expand...
Click to collapse
If you haven't tried ATOK お試し版, it might be worth it even if you have to switch keyboard from time to time. You can take the trial for a spin.
There are a few other keyboards in my sig, to consider and play around with.
Robobob1221 said:
Japanese has its own stock samsung keyboard separate from the Regular Stock keyboard. You'll need to get that apk and then get the necessary libs for it. Its annoying thats for sure.
Click to expand...
Click to collapse
Do you have a link for it ?
IT_Fan said:
Do you have a link for it ?
Click to expand...
Click to collapse
I grabbed the stock Japanese firmware for the SC-02E here (or you can get it from sammobile):
http://forum.xda-developers.com/showthread.php?t=1996006
The files I added from the firmware were these (sorry long list):
Code:
system/fonts/UDGothic-Regular.ttf
system/fonts/UDGothic-Bold.ttf
system/fonts/UDGothic-Italic.ttf
system/fonts/truetypeEmoji.ttf
system/fonts/UDGothic-BoldItalic.ttf
system/lib/libnjaddress_voiceeditor.so
system/lib/libennjubase1gb.so
system/lib/libmazecdict.so
system/lib/libennjubase1gb_voiceeditor.so
system/lib/lib_dic_en_USUK_urldotcom.conf.so
system/lib/libnjubaseidx1_voiceeditor.so
system/lib/libnjname.so
system/lib/lib_dic_morphem_ja_JP_voiceeditor.conf.so
system/lib/libMazecRecJpnDicD.so
system/lib/libnjemoji_voiceeditor.so
system/lib/libnjcon.so
system/lib/libnjaddress.so
system/lib/libiwnn_voiceeditor.so
system/lib/libMazecRecJpnDicB.so
system/lib/libnjexyomi_voiceeditor.so
system/lib/libnjtan.so
system/lib/libnjcon_voiceeditor.so
system/lib/libnjfzk_voiceeditor.so
system/lib/libMazecRecognizer.so
system/lib/lib_dic_en_USUK_emaildotcom.conf.so
system/lib/libnjubase2_voiceeditor.so
system/lib/libkaomoji_tyukyu_voiceeditor.so
system/lib/libennjcon.so
system/lib/libnjubase1.so
system/lib/libEnjemailuri_voiceeditor.so
system/lib/lib_dic_en_xlarge_USUK_voiceeditor.conf.so
system/lib/libnjtan_voiceeditor.so
system/lib/lib_dic_ja_xlarge_JP.conf.so
system/lib/libennjubase2_voiceeditor.so
system/lib/lib_dic_en_xlarge_USUK.conf.so
system/lib/lib_dic_en_USUK.conf.so
system/lib/libMazecJpnDic.so
system/lib/libennjubase2.so
system/lib/libiwnn.so
system/lib/lib_dic_morphem_ja_JP.conf.so
system/lib/libennjubase1_voiceeditor.so
system/lib/libnjfzk.so
system/lib/libnjubase2.so
system/lib/libennjubase3.so
system/lib/libMazecRecJpnDicC.so
system/lib/lib_dic_ja_JP.conf.so
system/lib/libkaomoji_kihon_voiceeditor.so
system/lib/libennjcon_voiceeditor.so
system/lib/libnjname_voiceeditor.so
system/lib/libnjemoji.so
system/lib/libnjexyomi.so
system/lib/lib_dic_ja_JP_voiceeditor.conf.so
system/lib/libkaomoji_kihon.so
system/lib/libnjubaseidx2_voiceeditor.so
system/lib/libennjubase1us_voiceeditor.so
system/lib/libennjyomi.so
system/lib/libennjubase3_voiceeditor.so
system/lib/libennjubase1us.so
system/lib/libMazecRecJpnDicA.so
system/lib/libnjubase1_voiceeditor.so
system/lib/libennjyomi_voiceeditor.so
system/lib/libkaomoji_tyukyu.so
system/lib/lib_dic_en_USUK_voiceeditor.conf.so
system/lib/libEnjemailuri.so
system/VODB/ja_JP/checked
system/VODB/ja_JP/files.txt
system/VODB/ja_JP/ja_JP_jisx0213-lk-text.lite.res
system/VODB/ja_JP/ja_JP.lang
system/VODB/ja_JP/ja_JP_jisx0213-ak-cur.lite.res
system/voiceeditor.prop
system/app/DcmVoiceSearch.apk
system/app/DcmVoiceEditor.apk
system/app/Maruberi.apk
system/app/iWnnIME_T0.apk
system/app/DcmVoiceRecognition.apk
system/app/Mazec.apk
I'm not sure if all of them are actually necessary or not, but that's what got iWNN (called "Samsung Japanese Keypad" in the UI) and MazeC (for handwriting) working on my US (TMobile) Note2. The voice recognition will fail with a SIM card error unless you have a Docomo SIM (so go into the settings and change voice input to Google Voice - I'm not sure how well that works), and I don't think this gets emoji working (it probably wouldn't work anyway outside Japan).
The process to get them was a bit involved. I had to untar the tar file, then run sim2img on the system.img and cache.img... then after mounting both, in the cache partition, there is a file recovery/sec_csc.zip. Most of the files I listed above are in the system partition, but the rest need to be extracted from that zip file. Then you can put them in place with a root file manager or adb.... If that sounds like too much work, maybe I can zip the the files up (not a flashable zip) and post them here.
Besides that, I'm a bit surprised by the lack of integration compared to the built in keyboard, especially with the multiwindow (it doesn't detach like the builtin keyboard). Also, you'll have to switch back to the "Samsung Keyboard" to get the sliding input or decent English handwriting recognition. So, I'm not sure if I actually missed anything and it or maybe that's just how it works.
The theming/colors also won't match what you see in the videos - it's more gray like the default keyboard on US Note2, while it appears to be blue in the youtube videos I found.
Thank you for your hard work in testing and posting here but I am afraid that's not what I am looking for, I need the Japanese IME integrated right into Samsung Keyboard then I can just slide to change the IME right away without needing effort to switch keyboards. For that mazec Japanese handwriting we can just purchase from Google Play if needed, no need to flash the JAP ROM.
Moreover, I tested Mazec's trial version. Mazec handwriting is good, but IMO it's not as good as the handwriting of Samsung keyboard compared to what I've been using with English and Chinese handwriting.
But anyway, I really appreciate your kindness in testing and reporting :good:.
IT_Fan said:
Thank you for your hard work in testing and posting here but I am afraid that's not what I am looking for, I need the Japanese IME integrated right into Samsung Keyboard then I can just slide to change the IME right away without needing effort to switch keyboards. For that mazec Japanese handwriting we can just purchase from Google Play if needed, no need to flash the JAP ROM.
Moreover, I tested Mazec's trial version. Mazec handwriting is good, but IMO it's not as good as the handwriting of Samsung keyboard compared to what I've been using with English and Chinese handwriting.
But anyway, I really appreciate your kindness in testing and reporting :good:.
Click to expand...
Click to collapse
Basically you can't integrate Japanese into the stock Samsung keyboard, at least not yet. It seems to have a different IME on all phones, at least in my experience.
If/when Swiftkey add Japanese to their language packs then it might get added to the Samsung Keyboard as well.
If you want all your languages in one keyboard you'll have to resort to using Swype or Smart Keyboard Pro.
Robobob1221 said:
Basically you can't integrate Japanese into the stock Samsung keyboard, at least not yet. It seems to have a different IME on all phones, at least in my experience.
If/when Swiftkey add Japanese to their language packs then it might get added to the Samsung Keyboard as well.
If you want all your languages in one keyboard you'll have to resort to using Swype or Smart Keyboard Pro.
Click to expand...
Click to collapse
Why does when Swiftkey add Japanese to their language packs then it might get added to the Samsung Keyboard as well ? These apps are made by the same developer ?
Yes, I am using Swype but the reason I love Samsung keyboard more because their handwriting is the best one IMO.
The current Samsung keyboard uses the swiftkey api/dictionaries/prediction engines whatever they call it I believe.
And swiftkey doesn't have a Japanese input method yet. So I guess I'm making the assumption that when that gets updated then you'll see Japanese added for the Samsung keyboard too.
Sent from my GT-N7105 using Xparent Skyblue Tapatalk 2
Robobob1221 said:
The current Samsung keyboard uses the swiftkey api/dictionaries/prediction engines whatever they call it I believe.
And swiftkey doesn't have a Japanese input method yet. So I guess I'm making the assumption that when that gets updated then you'll see Japanese added for the Samsung keyboard too.
Sent from my GT-N7105 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Just notice that you're from Japan. So could you tell which keyboard app you're using to type and handwrite Japanese ?
Honestly I don't do much handwriting as my character drawing is terrible! As regards keyboards try what has been recommended. I use either the stock Samsung Japanese keyboard or swype for ease of switching when typing.
Sent from my GT-N7105 using Xparent Skyblue Tapatalk 2
Add Japanese locale?
I too have a Galaxy Note 2 and I'm bemoaning the lack of Asian languages on it.
I'm not bothered by having to install a third party Japanese IME as I don't type in Japanese much. What I really want is to be able to switch the device language to Japanese (and/or Korean actually) just as I can switch it to French etc, for testing purposes. I'm not even that bothered about whether a few glitches and so on happen; I just want to be able to test application localization on one device!
Is there a way to make the 7100 act as if it's Japanese, such that apps use jp resources and so on?
For localization, I think you are looking for "Language Enabler" ( https://play.google.com/store/apps/details?id=com.wanam ), which should work on any (rooted) Samsung device. Just open it up, select the languages you want, save and reboot.
Although Korean was in the default list on my phone.
yubimusubi said:
For localization, I think you are looking for "Language Enabler" ( https://play.google.com/store/apps/details?id=com.wanam ), which should work on any (rooted) Samsung device. Just open it up, select the languages you want, save and reboot.
Although Korean was in the default list on my phone.
Click to expand...
Click to collapse
It enables just those in system language but still doesn't have input method of languages.
Stock to AOSP
Has this been tried on a non-stock rom?
I assume you are working with a stock Samsung rom and taking the files from the Japanese rom into the english version, but I may be wrong.
I would like to explore the possibility of doing this from a stock-japanese to an AOSP or cyanogenmod.
What METHOD did you use to identify these files? It would be of great help. I seriously want to use the mazec that came with my original rom into this cyanogenmod that I am using.
Thanks~~
yubimusubi said:
I grabbed the stock Japanese firmware for the SC-02E here (or you can get it from sammobile):
http://forum.xda-developers.com/showthread.php?t=1996006
The files I added from the firmware were these (sorry long list):
Code:
system/fonts/UDGothic-Regular.ttf
system/fonts/UDGothic-Bold.ttf
system/fonts/UDGothic-Italic.ttf
system/fonts/truetypeEmoji.ttf
system/fonts/UDGothic-BoldItalic.ttf
system/lib/libnjaddress_voiceeditor.so
system/lib/libennjubase1gb.so
system/lib/libmazecdict.so
system/lib/libennjubase1gb_voiceeditor.so
system/lib/lib_dic_en_USUK_urldotcom.conf.so
system/lib/libnjubaseidx1_voiceeditor.so
system/lib/libnjname.so
system/lib/lib_dic_morphem_ja_JP_voiceeditor.conf.so
system/lib/libMazecRecJpnDicD.so
system/lib/libnjemoji_voiceeditor.so
system/lib/libnjcon.so
system/lib/libnjaddress.so
system/lib/libiwnn_voiceeditor.so
system/lib/libMazecRecJpnDicB.so
system/lib/libnjexyomi_voiceeditor.so
system/lib/libnjtan.so
system/lib/libnjcon_voiceeditor.so
system/lib/libnjfzk_voiceeditor.so
system/lib/libMazecRecognizer.so
system/lib/lib_dic_en_USUK_emaildotcom.conf.so
system/lib/libnjubase2_voiceeditor.so
system/lib/libkaomoji_tyukyu_voiceeditor.so
system/lib/libennjcon.so
system/lib/libnjubase1.so
system/lib/libEnjemailuri_voiceeditor.so
system/lib/lib_dic_en_xlarge_USUK_voiceeditor.conf.so
system/lib/libnjtan_voiceeditor.so
system/lib/lib_dic_ja_xlarge_JP.conf.so
system/lib/libennjubase2_voiceeditor.so
system/lib/lib_dic_en_xlarge_USUK.conf.so
system/lib/lib_dic_en_USUK.conf.so
system/lib/libMazecJpnDic.so
system/lib/libennjubase2.so
system/lib/libiwnn.so
system/lib/lib_dic_morphem_ja_JP.conf.so
system/lib/libennjubase1_voiceeditor.so
system/lib/libnjfzk.so
system/lib/libnjubase2.so
system/lib/libennjubase3.so
system/lib/libMazecRecJpnDicC.so
system/lib/lib_dic_ja_JP.conf.so
system/lib/libkaomoji_kihon_voiceeditor.so
system/lib/libennjcon_voiceeditor.so
system/lib/libnjname_voiceeditor.so
system/lib/libnjemoji.so
system/lib/libnjexyomi.so
system/lib/lib_dic_ja_JP_voiceeditor.conf.so
system/lib/libkaomoji_kihon.so
system/lib/libnjubaseidx2_voiceeditor.so
system/lib/libennjubase1us_voiceeditor.so
system/lib/libennjyomi.so
system/lib/libennjubase3_voiceeditor.so
system/lib/libennjubase1us.so
system/lib/libMazecRecJpnDicA.so
system/lib/libnjubase1_voiceeditor.so
system/lib/libennjyomi_voiceeditor.so
system/lib/libkaomoji_tyukyu.so
system/lib/lib_dic_en_USUK_voiceeditor.conf.so
system/lib/libEnjemailuri.so
system/VODB/ja_JP/checked
system/VODB/ja_JP/files.txt
system/VODB/ja_JP/ja_JP_jisx0213-lk-text.lite.res
system/VODB/ja_JP/ja_JP.lang
system/VODB/ja_JP/ja_JP_jisx0213-ak-cur.lite.res
system/voiceeditor.prop
system/app/DcmVoiceSearch.apk
system/app/DcmVoiceEditor.apk
system/app/Maruberi.apk
system/app/iWnnIME_T0.apk
system/app/DcmVoiceRecognition.apk
system/app/Mazec.apk
I'm not sure if all of them are actually necessary or not, but that's what got iWNN (called "Samsung Japanese Keypad" in the UI) and MazeC (for handwriting) working on my US (TMobile) Note2. The voice recognition will fail with a SIM card error unless you have a Docomo SIM (so go into the settings and change voice input to Google Voice - I'm not sure how well that works), and I don't think this gets emoji working (it probably wouldn't work anyway outside Japan).
The process to get them was a bit involved. I had to untar the tar file, then run sim2img on the system.img and cache.img... then after mounting both, in the cache partition, there is a file recovery/sec_csc.zip. Most of the files I listed above are in the system partition, but the rest need to be extracted from that zip file. Then you can put them in place with a root file manager or adb.... If that sounds like too much work, maybe I can zip the the files up (not a flashable zip) and post them here.
Besides that, I'm a bit surprised by the lack of integration compared to the built in keyboard, especially with the multiwindow (it doesn't detach like the builtin keyboard). Also, you'll have to switch back to the "Samsung Keyboard" to get the sliding input or decent English handwriting recognition. So, I'm not sure if I actually missed anything and it or maybe that's just how it works.
The theming/colors also won't match what you see in the videos - it's more gray like the default keyboard on US Note2, while it appears to be blue in the youtube videos I found.
Click to expand...
Click to collapse
logicsama said:
What METHOD did you use to identify these files? It would be of great help. I seriously want to use the mazec that came with my original rom into this cyanogenmod that I am using.
Thanks~~
Click to expand...
Click to collapse
+1
I'm hoping for an answer to this too. I'm using Assassin ROM and would like to get the Stock Japanese Keyboard and Mazec Handwriting on my Note 2. I wasn't able to crack open the pure stock Docomo image I found online, but I was able to extract most of those files from a zip that Robobob1221 pointed me to. I can't find 3 of the apks in yubimusubi's list:
system/app/DcmVoiceSearch.apk
system/app/DcmVoiceEditor.apk
system/app/DcmVoiceRecognition.apk
I'll see for myself soon enough, but wondering if anyone knows up front whether those files are necessary.
Seems most of the files from yubimusubi's post may not be completely necessary, but that may still be a bit premature to say.
I've only copied the fonts, VODB folders, Maruberi, iWnnIME_T0, Mazec apks and the following lib files to my system directory:
system/lib/libiwnn.so
system/lib/libmazecdict.so
system/lib/libMazecJpnDic.so
system/lib/libMazecRecJpnDicA.so
system/lib/libMazecRecJpnDicB.so
system/lib/libMazecRecJpnDicC.so
system/lib/libMazecRecJpnDicD.so
system/lib/libMazecRecognizer.so
So far, Mazec handwriting works (!!), the English keyboard of the Samsung Japanese Keyboard works, numbers keyboard works, and symbols/emoticons work. The only problem I'm having now is getting the Japanese part of the keyboard to work. When I press a key, the keyboard freezes. Gonna try and figure out which of the other libs might help.
But so far it seems that the voiceeditor.so files aren't necessary. But then again, I don't use voice recognition or anything, so I'm not sure.
UPDATE: I didn't want to hijack the thread, so I started one here. I managed to get the hiragana and katakana input working, but I seem to have broken the ability to change kana to kanji and now the kanji. Everything seems to work fine! If you're interested in what files I used, please check the other thread.

Categories

Resources