I have to wait for Japanese input, I'm afraid. The AllLang packs won't have it but the jAllLangs will, none of which exist in leaked form yet.
So?? You can still copy and paste the japanese CODs yoy wish to import into the 267 java prior shrinking/installation and fire up the loader. Was that hard?
What's the point of waiting when there's a leak .267 available?
Aren't leaked builds usually development builds which are prone to annoying bugs?
I read through the latest 7.1 leaked OS thread and saw many pages of people experiencing problems.
I suspect the official 7.1 release will be something we haven't seen in a form of a leak.
Aren't leaked builds usually development builds which are prone to annoying bugs?
I read through the latest 7.1 leaked OS thread and saw many pages of people experiencing problems.
I suspect the official 7.1 release will be something we haven't seen in a form of a leak.
Aren't leaked builds usually development builds which are prone to annoying bugs?
I read through the latest 7.1 leaked OS thread and saw many pages of people experiencing problems.
I suspect the official 7.1 release will be something we haven't seen in a form of a leak.
Can't recall an official OS7 carrier approved release that has not appeared as a leak so would be very suprised to see the first official 7.1 be something brand new.
Official OS's usually turn out to be identical to the leaked version of the OS and two steps behind the latest leak.
Sure there are the odd bugs in leaked OS's but the same can be said for carrier approved versions and a lot of the supposed bugs are user error or incompatible app related.
There are no real problems with .267 which at least 1 carrier is said to be pushing out as an OTA update.
So?? You can still copy and paste the japanese CODs yoy wish to import into the 267 java prior shrinking/installation and fire up the loader. Was that hard?
I've tried countless times. Japanese is different than all the other languages on BBs and I have no idea why. I can port over the CJK files, the Korean inputs, and the Chinese ones no problem, but Japanese needs something else that nobody has ever been able to help me find to make it work. That's why the loader files that allow Japanese input in the first place have that little "j" in front of them. There is something inherently different about that language that normal packs won't take.
If you find a way to make it work I'll be in your debt, otherwise I'm stuck waiting for the official update from a carrier who chooses to release a j* pack.