How to Edit Remove "Swipe to unlock" - Samsung Galaxy W I8150

I want to share how to. (My ROM Backhybrid 2)
I found a simple way, thanks to Pako 777 and his utilty PUMa v2.2
Your phone must be rooted and deodexed
Downloud the utility
Open PUMa
Make a copy of your framework-res.apk copy in Folder IN
Even if android 2.3.6 officially not supported
Select device 9100, android 4.0, system; check "Change of lookscreen unlock guide text"
press apply, edit or left blank when finish copy the framework-res.apk from folder OUT to your system/framework
finally reboot

Not really needed?
Settings/location and security/set screen lock... choose 'none'
works for me

thanks for sharing, it's worked

Many Thanks ..

orwell 1950 said:
I want to share how to. (My ROM Backhybrid 2)
I found a simple way, thanks to Pako 777 and his utilty PUMa v2.2
Your phone must be rooted and deodexed
Downloud the utility
Open PUMa
Make a copy of your framework-res.apk copy in Folder IN
Even if android 2.3.6 officially not supported
Select device 9100, android 4.0, system; check "Change of lookscreen unlock guide text"
press apply, edit or left blank when finish copy the framework-res.apk from folder OUT to your system/framework
finally reboot
Click to expand...
Click to collapse
sorry if i ask this silly question, "what the function of this modding "
is it purpose to remove the default lockscreen swipe pattern, or is it removing the lockscreen function of some third party lockscreen application (go locker or magiclocker for example)??
btw, thanks for sharing dude...

Hi
It's just to edit or remove text in lookscreen, cause the translation in italian of "Swipe to unlook" is "Trascina il dito sullo schermo per sbloccare" and I don't like it.
If you want to disable lookscreen search for awakewidget there's a free version, works fine.
Bye

Related

[REF] Porting 2.1 (JM8) Samsung Keyboard to 2.2 (JPK)

Tools needed: smali, baksmali (google them), a JDK, and an extracted factoryfs.rfs from an éclair ROM.
(If you don't have a linux machine to mount an .rfs file to a directory never forget that your device has linux on it, so it can actually mount the .rfs file to a directory)
First collect the files you need from factoryfs.rfs:
/app/AxT9IME.apk
/app/AxT9IME.odex
/lib/libXt9core.so (this is actually the same file that's inside the apk)
/lib/libDHWR.so
/framework/android.policy.odex
/framework/core.odex
/framework/ext.odex
/framework/framework.odex
/framework/services.odex
Copy all the odex files into the same directory as baksmali is. Disassemble it with:
java -jar baksmali.jar -x AxT9IME.odex
This should create an out directory, with the disassembled, and deoptimized files. Now reassemble them, with smali:
java -jar out
This should create an out.dex file. Rename it to classes.dex, and put it into the AxT9IME.apk (don't be fooled by the extension, it's a simple zip file)
Now copy the following files to your phone:
AxT9IME.apk --> /system/app
libXt9core.so --> /system/lib
libDHWR.so --> /system/lib
Remove the following files:
/system/app/AxT9IME.odex
/system/lib/libdhwr.so (this is lowercase. The above was uppercase. Case does matter!)
Now try to enable the samsung keyboard. If everything goes well then you can now use the old keyboard.
-----
Alternatively if you needed the keyboard from the XWJM8 version, you can download the result files from here: http://android.sztupy.hu/dl/SamsungKeyboardFroyo.zip
Thank you
can I use this method in order to replace framework.jar/framework.odex from another build?
JHJP4 support proper BIDI (for Hebrew/Arabic and other RTL languages)
And how do we do the opposite? Want 2.44 on eclair =)
Should work the same
omrij said:
Thank you
can I use this method in order to replace framework.jar/framework.odex from another build?
JHJP4 support proper BIDI (for Hebrew/Arabic and other RTL languages)
Click to expand...
Click to collapse
No, framework.jar is too much different between eclair and froyo. You can only port simple applications (in /system/app) this way.
dupel said:
And how do we do the opposite? Want 2.44 on eclair =)
Click to expand...
Click to collapse
It would only work if the new keyboard doesn't use anything FroYo specific (like gesture support, or enhanced multitouch support). If it does use froyo specific api functions it will break under eclair.
sztupy said:
No, framework.jar is too much different between eclair and froyo. You can only port simple applications (in /system/app) this way.
Click to expand...
Click to collapse
Both frameworks are from Froyo
just different version
JP4 framework has proper BIDI support
omrij said:
Both frameworks are from Froyo
just different version
JP4 framework has proper BIDI support
Click to expand...
Click to collapse
If framework.jar changes then all pre-optimized files (odex) have to be reoptimized (the same way as the tutorial above shows), and even after that it might not work...
hi can I ask a few questions. I don't know much about these complicated things, but I will try my best.
can we collect files you asked us from factoryfs, through root explorer.
you asked to copy file with capital letters to phone and then asked to remove same file name with small letters. can one directory have two files with same name?
and finally how would we copy files to the phone?
thanks.
Sent from my Nexus One using Tapatalk
pitsyapa said:
hi can I ask a few questions. I don't know much about these complicated things, but I will try my best.
can we collect files you asked us from factoryfs, through root explorer.
you asked to copy file with capital letters to phone and then asked to remove same file name with small letters. can one directory have two files with same name?
and finally how would we copy files to the phone?
thanks.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
You can use rootexplorer to transfer the files to /sdcard modify them on the PC, tran transfer them back from /sdcard to their location.
thanks I really appreciate your help can I ask you another simple question. I have downloaded jdk.
and installed it. how do I use these commands to disessemble, java jar. is there any special java prograame. thanks.
thanks v much. problem solved. ported urdu keyboard from eclair to jpk. thanks again.
How do I know which files from /lib do I need to replace?
I'm trying to use contacts apk from other froyo rom
So, I tried the above instructions, and all I get is errors with bksmali, but i get the out directory, then when I run smali, it get another bunch of errors, but no out.dex. Any help would be amazing.
I haven't tried any of this other than trying to just install the AxT9IME.apk which obviously didn't work. I can enable it but trying to switch to it or access its settings instantly resorts in a force closure.
What I don't think I've seen mentioned is whether or not the end result of this allows you to have both the 2.2 and the 2.1 keyboards. Could anyone clarify for me if you get both or just the 2.1 keyboard in the end?
Lastly, would it be possible for someone to write an app (downloadable via market) for this keyboard for any android version? Because that'd be pretty awesome.
It'd be nice if it didnt create an app-drawer icon, but I wouldn't mind as Go Launcher allows me to hide unwanted apps.
I honestly like the 2.2 keyboard, but the 2.1 one (with its 4 pages) has symbols in on it that I have seen no where else, which is pretty cool and why I'm wanting it.

[MOD] Lang characters for hardware keyboard v0.3 [NOR|ESP]

Hi all!
After searching the wide web of the world I didn't find anyone who cared to program the special characters for nordic keyboards (æ,ø and å). The norwegian stock ROM has got these mapped to own keys, but I've never liked to use stock ROMs, so I was stuck with the "long press method".
New! Now Spanish is also supported!
If you screw up your phone trying to adb push, cp -f these files I'm not responsible yada yada yada (nothing wrong should happend, really)
What I've done is taking the modified files from teferi, and added my own editing for the quick keys (as I had to make place for the chars I removed from jkl) and the special chars of course.
Confirmed on my G2 (running the Sense ROM from MoDaCo), but should work for the Desire Z too! Any guinea pigs out there?
Code:
*Norwegian*
version 0.3:
-Fixed issue with , and ; didn't work on hardware keyboard.
version 0.2:
Quick change to the "Z" button, since "`" is used in command substitutions.
-alt-z is still "^", alt-shift-z = "`"
version 0.1:
-alt+j,k,l = æ,ø,å (alt+shift gives capitol letter).
- make ".com" a TAB key, as it ought to be
- left softkey is now "\" "|" "/"
- right softkeys are now "[" "(" "<" and "]" ")" ">"
- alt-z is now "^"
Code:
*Spanish version*
Version 0.2
-Corrected filenames for the new files, and included the right "originals".
Version 0.1
[Key] - [Shift + key] - [FN + key] - [Shift + FN + key]
a - A - ! - á
e - E - 3 - é
i - I - 8 - í
o - O - 9 - ó
u - U - 7 - ú
n - N - = - ñ
? - ¿ - " - ¡
. - < - : - >
INSRUCTIONS:
*Add -wwe after "keypad" in the filename for both files if your running a Desire Z based ROM. CM and G2-based will work without -wwe*
- download file
- unzip *.zip
- adb push vision-keypad.kl /sdcard/
- adb push vision-keypad.kcm.bin /sdcard/
- adb shell
- su (if you don't have ro.secure turned off)
- mount -o remount,rw /dev/block/mmcblk0p25 /system
- cp -f /sdcard/vision-keypad.kl /system/usr/keylayout/
- cp -f /sdcard/vision-keypad.kcm.bin /system/usr/keychars/
- reboot
Btw... backup of original keymapping is included... just rename them without .orig, and follow the procedure above
Code:
Guide to make your own keys:
Download a hex editor (i prefer xvi32), open the "kcm.bin", and alter the symbols shown in the attached .jpg. If you wish to alter the "main" char of the key, you can change that in the .kl file with notepad (check the difference between esp and nor to see an example).
Thanks to teferi for the base files
Novek said:
I can make files for other special characters if someone wants that... or you could simply HEX-edit the files yourself
Click to expand...
Click to collapse
Great work! But, since I'm not Norwegian, I'm not going to try it
However, I'd love to see a modification of the original English Desire Z Sense keymap with just a few modifications.
Here's a picture of the Desire Z keyboard
http://www.theunwired.net/media/news/htc_desire_z_front_open.jpg
1) Getting á, é, í, ó and ú by Shift + FN + a, e, i, o, u (I think it's Shift + Alt in the G2 keyboard). Currently I have to long press the vowel key and then touching the screen. Not efficient.
2) Getting ¿ by using Shift + ? , and maybe ¡ by pressing Shift + FN + ?.
Would it be possible?
If you need the original files or whatever, just tell me
Thank you in advance.
I would need to get the original desire z keymapping files as I've just the g2... they are a little different with the non-letter keys.
Sent from my HTC Vision using XDA App
Here it is
I've just uploaded a file with the two directories, keychars and keylayout.
I think it's interesting that there are several kcm.bin files and several kl files, for different languages, but I don't know how to select them.
Thank you again.
Actually... You can't keep both ! and "á" at the "A" key.... or at least you can't get the "á" capitol that way...
It would then be a, A, !, á available on that key.
Do you want me to remove the !, or...
I don't mind having to long press A to get the Á, I don't use it that often
cool. this is useful for me. I don't got the Nordic version so thanks
Novek said:
Actually... You can't keep both ! and "á" at the "A" key.... or at least you can't get the "á" capitol that way...
It would then be a, A, !, á available on that key.
Do you want me to remove the !, or...
Click to expand...
Click to collapse
Novek, have you had time to look over the Spanish version?
No rush, just curious.
I've actually haven't had time today but I'll try to find some time tomorrow or wednesday...
Just found a bug in the norwegian mod (the comma button doesn't work) so I'll fix that tomorrow too...
Sent from my HTC Vision using XDA App
/edit
New version up with the , and ; working...
bra jobba!! my friend just go a desire z and he was looking for this
Novek said:
I've actually haven't had time today but I'll try to find some time tomorrow or wednesday...
Click to expand...
Click to collapse
As I said, no rush... And thank you for your work
I would like to state that these files /system/keymap/* and /system/kaychar/* might be affecting the capacitive buttons belove the screen also. This will not brick anyone's phone (probably ) but will make it hard to do anything unless fixed.
What I understand:
everyone should use only the files that are meant for their specific DZ version and modify that.
I.E. G2 files on Scandinavian DZ renders capacitive buttons useless. And if u dont have adb access nearby it can be hard to do anything
Novek, I hadn't seen your private message. I already answered and I'm willing to try your alternative files
By the way, does anybody know why there is a lot of different files in /system/usr/keychars and keylayout? I mean, there's a vision-keypad.kcm.bin and a vision-keypad-esn.kcm.bin.
It would seem that the esn file could be useful for us Spanish speakers, but I don't know how to use it.
Hi Novek.
Thanks a lot for the Spanish version, but I'm afraid I'm doing something wrong.
I substituted the original files for the ones you have uploaded (I tried both doing it via Root Explorer and following your guide using adb) and when I press Shift + FN + N I still get = instead of ñ. The same with the rest of the keys.
I think I've read somewhere that the Desire Z uses the vision-keypad-wwe.kcm.bin and vision-keypad-wwe.kl file instead of the ones without wwe, could that be it?
I would assume that you can just rename the files I posted...
/edit
If it works after renaming to wwe, I'll change the uploaded files..
I'll also re-do the norwegian keymapping with the DZ-files tomorrow - removing the files for G2 now.
Sent from my HTC Vision using XDA App
Novek said:
I would assume that you can just rename the files I posted...
/edit
If it works after renaming to wwe, I'll change the uploaded files..
I'll also re-do the norwegian keymapping with the DZ-files tomorrow - removing the files for G2 now.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Takk veldig mye!
I just renamed the files and it worked. Thank you very much
Edit 1. Mmm.. it worked at first, but now when I use Shift+FN+key I get Á, É, Í... instead of á, é, í.
Edit 2. Nevermind... I get the capitalized version when the autocorrection kicks in, at the begining of a sentence
?
Hi!
Im Hungarian so i am very interested on this application. lots of time I need áéóöőüű!!! Im a begginer in the android world.
Could everyone help for me pls!
I wanna know is this appl. works in the original ROM or not?
And could you write a step by step guide for the installation?
Bests, David!
Hi again, Novek! Just noticed that my SYM key is now working like a shortcut key When I press it, I get the "Keyboard shortcuts: Would you like to assign a shortcut to the hardware keys?" screen.
Could you make another version with this fixed? Thank you in advance
daveeer said:
Im Hungarian so i am very interested on this application. lots of time I need áéóöőüű!!! Im a begginer in the android world.
Could everyone help for me pls!
I wanna know is this appl. works in the original ROM or not?
And could you write a step by step guide for the installation?
Click to expand...
Click to collapse
In the first posting, it pretty much is a step-by-step guide. Is there any particular part that's confusing you ? Don't be afraid to ask specific questions about things. It's not dumb to ask questions, it's dumb to just try something when you don't understand what you're doing and it could mess up your phone !
Yes, as far as I know this should work with the original ROM.
It's not really clear for me, how can I make my own layout?
So which file included "which key is which letter" table, and how can i edit it?

[ROM][2/12/11][CHINESE] MIUI for G2 (v1.2.11)

http://bbs.gfan.com/android-575451-1-1.html
ignore the link at the top that one is mostly chinese the english version is provided hear thanks to da900
DOWNLOAD LINK: http://www.multiupload.com/PVZRB1NRHK
P.P.S. All you do with this pack is on your own risk. I am not responsable for any damages of your phone.[/QUOTE]
please aware that this rom is only contain about 20% english , most of words are chinese
u should be able to change it to english in the language and input settings
Is this newer than the QnD 1.2.4 rom?
Look at the number lol. 1.2.11 > 1.2.4
no that one has chinese this one does to thou dnt flash nevermind
dictionary said:
Look at the number lol. 1.2.11 > 1.2.4
Click to expand...
Click to collapse
XD I was thinking 4 > 1.
here's the changelog:
MIUI 1.2.11 version update:
Phone:
Add in the phone settings to add "call from the sensors used in the process" of setting
Fix the call log to the Canadian people through IP numbers to send SMS / MMS will bring IP prefix, resulting in the issue could not be sent
Theme:
Add support for setting alarm
Ringing in the new system comes with the option "mute"
Optimize the system comes with the choice of ring tones
Repair some of the theme of the correct format does not show the problem package
System Update:
Add WIFI connection can support the Ad-Hoc (peer to peer) network
Press the Backspace key fixed the problem miscarriage of justice
Local Backup:
Installed on the sd card repair program can not be the problem with the backup and recovery
Click to expand...
Click to collapse
terrelltp said:
no that one has chinese this one does to thou dnt flash nevermind
Click to expand...
Click to collapse
What? Slow down and make sense lol. Are you saying that you screwed up, and there is next to no English in the build?
terrelltp said:
u should be able to change it to english in the language and input settings
Click to expand...
Click to collapse
i repeat :
this rom does contain 20% of english translation only !
Even you change to english language :
your 80% of menu still display "Chinese".
So, this is useless unless you understand simplified Chinese. I'll wait on g4rb4g3 to release a port.
Sent from my htc.desireZED
Weren't there language packs you could install
Sent from my HTC Vision
Device Specific Language Packs
I think that language packs are device specific.. I haven't been able to find a language pack on the net for the G2.. though I did manage to a how to guide but I'm green to this stuff..
If somebody out here is familiar with how to do this guide and create a language pack for the G2 for us.. that would be helpful.
djmcnz said:
Okay guys, there's a lot of demand for this rom and for language packs but not yet a lot of people who know how to make the packs. Whilst I set up the crowdin translation project I can not create or maintain language packs.
So, here's a summary of the instructions required to create a language pack for MIUI (indeed for any app/rom). You need a collection of tools and a little patience but the process isn't too difficult so do give it a go.
Also note that this summary includes generalisations for brevity. These instructions assume you have a deodexed rom.
Introduction
For the purposes of this post language information is stored in XML strings in files on the Android system. In the case of MIUI and these instructions we will be dealing with .apk files (applications).
Within the apk files is a resources directory (/res) and within this are various values directories, there is a default values directory (/res/values) and alternative language values directories (e.g. /res/values-DE and /res/values-IT).
If the rom is set to use it's default language it will read values from /res/values although these may NOT be in English. In MIUI, all of the common Android ASOP values in /res/values are English but the (additional) custom MIUI strings are in Simplified Chinese.
If you select a different language in the ROM than the default then the appropriate values directory will be searched. If a suitable string that matches your language selection is found in the alternative /res/values-xx directory then that string will be used instead. If an alternative does not exist then the default will be used.
Example:
Code:
/res/[COLOR="red"]values[/COLOR]/strings.xml
<stop_button_text>[COLOR="Red"]Stop[/COLOR]</stop_button_text>
/res/[COLOR="red"]values-DE[/COLOR]/strings.xml
<stop_button_text>[COLOR="red"]Halt[/COLOR]</stop_button_text>
/res/[COLOR="red"]values-IT[/COLOR]/strings.xml
<stop_button_text>[COLOR="red"]Basta[/COLOR]</stop_button_text>
In this example, if the language is set to the default the word "Stop" will be used, if it is set to German the word "Halt" will be substituted in, likewise "Basta" for Italian.
So, to add languages to a rom (or app) or to make an app multi-lingual you need to either change the default strings in /res/values/strings.xml to the ones you want to use or, and this is the preferable approach, add a /res/values-xx/strings.xml with the translations you want. The first approach will work (changing the default strings) but is not recommended because the Android Open Source Project and Android development in general, defaults to English. It's best to use the built in language substitution capabilities of Android rather than to work around them. Indeed, if the MIUI devs actually added their strings in English to /res/values/strings.xml and the Chinese equivalents in the appropriate directory this rom would already be in English!
Adding Languages
To add a translation file (strings.xml) to an apk you need to:
decode the apk
create a language directory
add the translation files
recompile the strings
add the new strings to the apk
Which all sounds a little daunting but it's really quite straight-forward, rewarding when you see the result and a good way to understand how parts of Android work. Here's how you can do it.
1. decode the apk
You will need the excellent apktool from brut.all which you can get from the link below. apktool is relatively easy to use but includes some little tricks so you will need to read the wiki and thread about it.
Do NOT just post problems about apktool if you can't get it to work. The tool DOES work so if it's not decoding (or encoding) your apps correctly then you're probably doing something wrong. If you start with this understand BEFORE you ask for support you'll get a lot more help...
apktool: http://code.google.com/p/android-apktool/
wiki: http://code.google.com/p/android-apktool/w/list
thread: http://forum.xda-developers.com/showthread.php?t=640592
Please make sure you run the following command to include the MIUI framework in apktool. You only need to do this once for each framework. If apktool works with one rom and not the next then (re)install the framework for that rom.
Code:
apktool if framework-res.apk
Where framework-res.apk is the one from the rom you are working with. Make sure apktool can find (the correct) framework-res.apk before you run this command.
This thread is not for apktool support.
Now, before you proceed, decode a simple app from MIUI (such as updater.apk) using apktool, do not make ANY changes, then re-encode it using apktool. For example:
Code:
apktool d Updater.apk ./decoded/
apktool b ./decoded/ new_updater.apk
Use the -v (verbose) flag in apktool if you have problems and need to diagnose further.
Remember, Android uses a case-sensitive file system, make sure your capitalisation is correct.
Typically you will not be able to install this apk because it is not signed so if you want to test the process further you can now just try step 5 below using the two apks you have.​
2. create a language directory
Assuming you can decode/encode now, this is the easy bit. For your decoded app, navigate to the directory it was decoded in, then to the /res/ directory and simply create an empty directory for your language (e.g. /values-FR/) - use international naming conventions.​
3. add the translation files
Again, not too difficult this. Download the appropriate language file for your apk from the crowdin project linked below and, using the same structure as exists in /res/values/strings.xml create a new file called strings.xml in your alternative language directory (e.g. /res/values-ES/strings.xml).
The news strings.xml may contain as many or as few translations as you like. Remember, if a translation does not exist the default value from /res/values/strings.xml will be used.
Crowdin: http://crowdin.net/project/miui-rom-translation/invite
The xml formatting and tag names need to match exactly with the default strings.xml in /res/values although the translated file does NOT need to be complete.
It is worth remembering here that unless your source apk is already translated to English then some of the default values in /res/values/strings.xml will still be in Chinese, it would pay to check these.​
4. recompile the strings
Now, if you've done everything carefully and correctly this step is really easy, all you need to do is recompile the apk with apktool using the b (for Build) switch.
Code:
apktool b ./<decoded_apk_dir>/ <output_apk_name>.apk
If this throws errors or does not work then use the -v switch to turn on verbose mode and diagnose your problem. If you did the test in step #1 and it worked then any problem at this step is likely related to your news strings.xml. Back out the changes one by one until you have found the problem and try again.
If you simply can't get it to compile with your changes then try just making a single change to the default strings.xml file in /res/values and see if that works for you.
Do NOT sign the apk!​
5. add the new strings to the apk
Easy. Open your new apk with a zip program (like 7Zip for Windows) and copy out the resources.arsc file in the root directory of the apk. Now take that file and copy it into the source apk from the rom overwriting the existing one. This process replaces the strings but keeps the integrity of the signatures on the files.
You can now push the modified file to your phone, replacing the stock one, reboot and you're translated. Push the file using "adb push" or copy it into place using a root file manager, do not "install" the new apk. Make sure you put it in the correct place (replace the original) and reboot.​
Conclusion
This process will help you add languages to any app including those in the MIUI rom. Because it's a rom the strings are contained in many different apps as well as framework-res.apk. To completely translate the rom you will need to edit every apk that has strings in it.
You will need to do this every time an apk in the rom changes. If a new version is released and say launcher2.apk is changed but updater.apk is not, then you can retain your updater.apk but you'll need to re-edit your launcher2.apk.
When an app changes the default strings.xml may also change. In this case you will need to make corresponding changes to your translations.
Good luck and if you get really stuck there's lots of people in this that have achieved success and may be willing to help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=789566
MIUI 1.2.11 for Vision ENG
Hi, all. I like the MIUI ROM and as most of you want to have latest version as soon as posible. But I am not a dev and my skills in android development are very very poor. So, i followed the versions of MIUI by g4rb4g3. They all are very stable and fast. And i want to say once more HUGE THANX to him for his work.
But when i found this thread today in the morning i decide to make it in english. So, putting together the ROM from 1st post and ENG pack for N1 from MIUI-DEV.COM with some additional editing of built.prop and adding some apps. I made a pack. Flashed it and it is working fine.
P.S. The only chinese words that i found are in MIUI account registration in Accounts&sync.
Adding: Facebook, Twitter, VoiceSearch, Google Search, gMaps, Street, GMail etc. (all apks are up to date).
DOWNLOAD LINK: http://www.multiupload.com/PVZRB1NRHK
P.P.S. All you do with this pack is on your own risk. I am not responsable for any damages of your phone.
ok cool so basically u made a english version for that latest update cool cool
terrelltp said:
ok cool so basically u made a english version for that latest update cool cool
Click to expand...
Click to collapse
Maybe, you could add the link to ENG version to 1st post of this thread. Could you?
da900 said:
Maybe, you could add the link to ENG version to 1st post of this thread. Could you?
Click to expand...
Click to collapse
i thought thats what u did isint that link u posted the english version
terrelltp said:
i thought thats what u did isint that link u posted the english version
Click to expand...
Click to collapse
I think he means add the link that HE provided to your first post, so that users will actually have an ENG version, instead of the one you posted.
dictionary said:
I think he means add the link that HE provided to your first post, so that users will actually have an ENG version, instead of the one you posted.
Click to expand...
Click to collapse
That's what i mean. Thanx.
lol yes i did that now
da900 said:
Hi, all. I like the MIUI ROM and as most of you want to have latest version as soon as posible. But I am not a dev and my skills in android development are very very poor. So, i followed the versions of MIUI by g4rb4g3. They all are very stable and fast. And i want to say once more HUGE THANX to him for his work.
But when i found this thread today in the morning i decide to make it in english. So, putting together the ROM from 1st post and ENG pack for N1 from MIUI-DEV.COM with some additional editing of built.prop and adding some apps. I made a pack. Flashed it and it is working fine.
P.S. The only chinese words that i found are in MIUI account registration in Accounts&sync.
Adding: Facebook, Twitter, VoiceSearch, Google Search, gMaps, Street, GMail etc. (all apks are up to date).
DOWNLOAD LINK: http://www.multiupload.com/PVZRB1NRHK
P.P.S. All you do with this pack is on your own risk. I am not responsable for any damages of your phone.
Click to expand...
Click to collapse
WOOOO..good job . it's perfect !!!!!!!! work very well ~!! thanks a lot

{PRO} [Q&A] How to change physical keyboard layout on xperia mk16i

As I'm a newbie here, I'm not aloud to post this in the dev section.
So I'll explain how you can simply change you're physical keyboard layout on Gingerbread and ICS easily without flashing an appropriate kernel for the Xperia Pro mk16i iyokan.
-So first you need root access.
-second, you need to install a root explorer like ES file explorer.
activate the root access to /system in the option of ES file explorer.
-ones you're here, you need to identify all the layout you're rom got. they are listed as xml files in the directory:
/system/usr/keyboard-config/layouts
my rom contains almost all keyset imaginable.
-Now you've find the name of your keyset find the file :
/system/usr/keyboard-config/keyprint.xml
-edit it with the file explorer integrated file editor.
-you'll find a file formatted with a fanzy SE header and that:
HTML:
<Keyprint>
<Script name="arabic" keylayout="arabic"/>
<Script name="cyrillic" keylayout="cyrillic"/>
<Script name="greek" keylayout="greek"/>
<Script name="hebrew" keylayout="hebrew"/>
<Script name="latin" keylayout="qwerty"/>
<Script name="thai" keylayout="thai"/>
</Keyprint>
-Choose the alphabet you use and put the name of your layout without the xml file extension.
if you're europeen or american, I guest latin will be you're choice.
For arabic, greek, croatian russian... and every other languages using an another alphabet I let you choose
So for example if I want to change my latin layout from Qwerty to Qwertz
I replace the line
HTML:
<Script name="latin" keylayout="qwerty"/>
by
HTML:
<Script name="latin" keylayout="qwertz"/>
-so save the file and reboot you're phone, you should now get the right keyboard set for you're phone.
Or you can edit it with adb by pulling the file and pushing it after (but it's a bit more tricky
Have a good night and if anybody can move my thread in the good section I'll be very pleased
ps:
All credits and inspiration came from the original post of ameer1234567890 which provide a lot of flashable layout.
I think this works only on stock and stock based ROMs. Can someone please confirm if this works on a ROM like CM7 or CM9.
I'd like to know too, because i used to use cm7 on htc dz but as cm7 or 9 are still in dev for mk16i I never tried them on mine for now
Hey.can u be more specific? How to do this?
I got the file..and now what should i do?
Thnx
Sent from my MK16i using xda premium
anamul.quader said:
Hey.can u be more specific? How to do this?
I got the file..and now what should i do?
Thnx
Sent from my MK16i using xda premium
Click to expand...
Click to collapse
I had an example in the tuto, if you still don't understand, I'll try to explain it again ;-)
Good luck
This does not work in 3rd party apps (smart keyboard pro and swiftkey), also on some cases chrome will misbehave as well. I think chrome is bypassing the xperia keyboard when it's trying to be super-secure such as entering passwords.
Chrome won't show you virtual keyboard at all in such cases so I think it can be safely filed under BUG but that won't help if you can't sign in. Using opera mobile as a workaround works..
I'm pretty sure the stock gingerbread finnish firmware played nice with smart keyboard pro. There's a link in the "root" Xperia pro thread where you can download "hotfix" for Xperia pro. These claim to be keyboard layouts for various languages. These are NOT the text files you describe here but the actual android keymap files.
They did not work for me, though, boo. I'll have to try again. The files in keychars-folder (MAKE BACKUPS!!) are .kcm.bin while the originals are called .kcm. I would assume both are not used at the same time. In keylayouts (backup bro) the replacement files are .kl, same as original but smaller.
3rd party keyboard has never been my point.
Stock android is handling physical keyboard a certain way, and virtual keyboard such as slide it or swiftkey do as they want with that kind of thing.
Switft never works correctly for me with stock rom or with custom rom.
Sorry if it doesn't work.
but if every software interprete keyboard there own way, we're damn lost. I never use Chrome but I guest it can also interprets keyboard layout its own way.
the flash fix you talk about is interesting, I'll try it asap. thks
Those keyboard layout/keychars files just make the HW keyboard stop working properly. I think they come from mini pro. Or at the very least they'd need some configury thingy somethere.
As a positive note, they DO make HW keyboard behave differently but swedish/finnish one definitely does not produce local chars.
Meh, I guess I need to fork up 2€ for wotanserver to get authentic finnish firmware.
FWIW I'm pretty sure stock finnish gingerbread firmware didn't have a problem with smart keyboard pro. And android + keyboard is a bit of a odd-man-out, we don't even get a forum..
Ed: Chrome works ok 95% of the time, I should file bug about text boxes where it goes crazy.
That's too bad, that it doesn't work for you.
Fact is we are at the border of android with physical keyboard.
And ow with nexus 3 without physical button except for sound and power...
I think (not hope) that physical keyboard for phones is almost arrived at its end.
Regarding stock firmwares, my update to ICS made by official sony companion just put me a Qwerty layout :-D so don't be so sure about stock firmwares ;-)
Umlauts in quertz
anybody know how to fix the orders of the umlauts for qwertz layout in the pop-up and make the SYM-Button working?
flashing of files newer worked for me, or a could'nt more use the shortcuts like copy-paste...
see also this thread: http://forum.xda-developers.com/showthread.php?t=1658959&page=20
Search trough the web for solution. nothing.
Physical keyboard has a driver, or own FW or sumthing?
And can i have the stock xperia physical keyboard app?
My sym button doesn't work, my direction arrows are weird, qwerty-stroke keyboard layout. But i accept the latin one too
Or where is this "driver"-stuff in the ROM? Can i copy from old ROM (which one is working), to ICS .587 (which don't)?
Thanks in advance
I installed the arabic script from ameers collection and the language changed to arabic.. thing is my keyboard has the same layout as arabic version but I wanted the english characters.. I tried your method but whatevr script I keep for my keyboard layout, it still follows the same script even after rebooting.. pls help..
Sent from my MK16i using xda app-developers app
ilfunx said:
I installed the arabic script from ameers collection and the language changed to arabic.. thing is my keyboard has the same layout as arabic version but I wanted the english characters.. I tried your method but whatevr script I keep for my keyboard layout, it still follows the same script even after rebooting.. pls help..
Sent from my MK16i using xda app-developers app
Click to expand...
Click to collapse
I'm having the same problem, so if you found a solution over the last few months, could you share it with me, please?
Method not working
Kiwyxda said:
As I'm a newbie here, I'm not aloud to post this in the dev section.
So I'll explain how you can simply change you're physical keyboard layout on Gingerbread and ICS easily without flashing an appropriate kernel for the Xperia Pro mk16i iyokan.
-So first you need root access.
-second, you need to install a root explorer like ES file explorer.
activate the root access to /system in the option of ES file explorer.
-ones you're here, you need to identify all the layout you're rom got. they are listed as xml files in the directory:
/system/usr/keyboard-config/layouts
my rom contains almost all keyset imaginable.
-Now you've find the name of your keyset find the file :
/system/usr/keyboard-config/keyprint.xml
-edit it with the file explorer integrated file editor.
-you'll find a file formatted with a fanzy SE header and that:
HTML:
<Keyprint>
<Script name="arabic" keylayout="arabic"/>
<Script name="cyrillic" keylayout="cyrillic"/>
<Script name="greek" keylayout="greek"/>
<Script name="hebrew" keylayout="hebrew"/>
<Script name="latin" keylayout="qwerty"/>
<Script name="thai" keylayout="thai"/>
</Keyprint>
-Choose the alphabet you use and put the name of your layout without the xml file extension.
if you're europeen or american, I guest latin will be you're choice.
For arabic, greek, croatian russian... and every other languages using an another alphabet I let you choose
So for example if I want to change my latin layout from Qwerty to Qwertz
I replace the line
HTML:
<Script name="latin" keylayout="qwerty"/>
by
HTML:
<Script name="latin" keylayout="qwertz"/>
-so save the file and reboot you're phone, you should now get the right keyboard set for you're phone.
Or you can edit it with adb by pulling the file and pushing it after (but it's a bit more tricky
Have a good night and if anybody can move my thread in the good section I'll be very pleased
ps:
All credits and inspiration came from the original post of ameer1234567890 which provide a lot of flashable layout.
Click to expand...
Click to collapse
Good Post, i tried it but it does not work after i reboot.
So my keyboard is still the QWERTY layout instead of QWERTZ
Also, some detailed instructions on ES Explorer.
Once you open ES Explorer, Left Drawer --> Go to Tools --> Root Explorer --> Mount RW --> Set / to RW
Now you can follow the steps to edit the keyprint.xml
Again let me remind you, i tried this and it does not work. So if i have done it the wrong way, please let me know.

[GUIDE] Remove or Change "Swipe Screen to Unlock text" - Gingerbread

This is just simple guide
Requirements:
framework-res.apk
Step:
In here i will not explain how to decompile and recompile apk
First; you have to decompile your framework-apk
Second; open \framework-res\res\values-in\strings.xml
Note; why "values-in" because i'm using Indonesian language. if you're using another language, just change "values-in" with your language.
Click to expand...
Click to collapse
Third; find "lockscreen_unlock_guide_text"
Fourth; remove or change "Usap layar untuk membuka kunci"
"Usap layar untuk membuka kunci" in english "Swipe Screen to Unlock"
Click to expand...
Click to collapse
Fifth; if you're done, now recompile your framework-res.apk
After step fifth, now go to this site uot.dakra.lt/kitchen
First; select tab file upload, in this step you need to match with your smartphone.
Second; select upload system files, and select framework-res.apk who have edited
Third; now select tab summary and then click Submit work to kitchen, wait for kitchen. Dont forget your order number
Fourth; your flashable.zip will be show in "Your recently cooked files", and download it!
Finally; place your UOT-blabla.zip to sdcard, and flash it via CWM.
TESTED on Galaxy Y
Screenshot in Attachments​
Unsuccessful
MrPhamHpGYC said:
Unsuccessful
Click to expand...
Click to collapse
where your problem sir?
Nice tut :fingers-crossed:
Nice guide.

Categories

Resources