I know that the standard Android keyboard allows you to call up the [Enter] key by a prolonged press on the visible Emoji key.
I can't seem to be able to do the same in Lineage.
Do I need to set any special options ?
Found it....Setting is under "Messaging" ---> Emoticons access
Set Off
Related
I was just looking for some opinions... It seems to me that out of all the WP7 Devices, the LG Quantum is the easiest to make changes to simply because of MFG.
Debranding and unlocks take just a couple of seconds and seem to be more reliable when I look at all the different posts on here. Incase anyone is looking for them for the quantum, here they are btw...
LG "debranding" hack
1. Enable the MFG application by going to the dialer and dialing ##634# then pressing call.
2. Launch the MFG application and enter 277634#*# when prompted for a password.
3. Select the Engineer Menu item.
4. Select the Other Setting menu item.
5. Select the Edit registry menu item.
6. Set the input boxes on this menu as follows:
Select ROOT_PATH: HKEY_LOCAL_MACHINE
Input SUB_PATH: \System\Platform\DeviceTargetingInfo\
Input KEY: MobileOperator
Data Type: STRING
Instead of putting in a blank, put in an empty space.
Also, if you want to re-brand your phone after the update for AT&T your input should be ATT-US
7. Select Query and write down the result in case you need to re-brand for some reason.
8. To debrand just enter the same information above and leave the input data field blank. The tool will say fail but it really did set correctly.
You can now connect to Zune and check for updates.
How to Un-Lock your Phone without Chevron 7
You can unlock the phone by using the MFG registry editor.
Open the MFG app and use the password to open it. If you don't know it's (appmfg#*#)
Go to Engineer Menu -> Other Settings -> Edit Registry
Set your ROOT PATH to "HKEY_LOCAL_MACHINE"
Set your input path to "\Comm\Security\LVMod"
Set your input key to "DeveloperUnlockState" and set to DWORD
Hit Query. Output result should return a "0" or a random long number. If it does continue.
Set your input data box to "1" and hit SET. Output result should be 1
How To Keep Your Phone Unlocked
You can keep your phone unlocked and prevent Zune from re-locking it.
Open the MFG app and use the password to open it. If you don't know it's (appmfg#*#)
Go to Engineer Menu -> Other Settings -> Edit Registry
Set your ROOT PATH to "HKEY_LOCAL_MACHINE"
Set your input path to "\Software\Microsoft\DeviceReg"
Set your input key to "PortalUrlProd" and set to DWORD
Hit Query. Output result should return data. If it does continue.
Keep your input data box empty and hit SET. Output result should be 0
Keep this screen open and continue to Part 2
Part 2
Set your ROOT PATH to "HKEY_LOCAL_MACHINE"
Set your input path to "\Software\Microsoft\DeviceReg"
Set your input key to "PortalUrlInt" and set to DWORD
Hit Query. Output result should return data. If it does continue.
Keep your input data box empty and hit SET. Output result should be 0
Backout to the password screen and shutdown the phone via powerbutton.
Reboot and sync. Your phone should stay unlocked.
How to Re-Lock your Phone without Chevron 7
Don't want your phone unlocked anymore? You can re-lock the phone by using the MFG registry editor.
Open the MFG app and use the password to open it. If you don't know it's (appmfg#*#)
Go to Engineer Menu -> Other Settings -> Edit Registry
Set your ROOT PATH to "HKEY_LOCAL_MACHINE"
Set your input path to "\Comm\Security\LVMod"
Set your input key to "DeveloperUnlockState" and set to DWORD
Hit Query. Output result should return a "1". If it does continue.
Set your input data box to "0" and hit SET. Output result should be 0
Your phone is now locked. To Unlock the phone redo the above steps but set back to "1"
Oh and I can confirm this unlock method works and keeps it unlocked.
Then once unlocked, if you combine it with the Chevron ringtone manager-> http://www.chevronwp7.com/post/20542...ngtone-manager, and any registry changes you know of such as changing themes and such, there really doesn't seem to be much you cant do with it. Is my opinion accurate? Or is it just skewed because I love this phone? Also, is the MFG the reason why it doesn't seem like anyone has worked on software for the phone like they have with the Samsung and HTC models?
Nothing unstable about my hd7. Wonder if LG ha finally broken the feature phone stigma.
Sent from my HD7 using XDA Windows Phone 7 App
@nrfitchett4
I have to say I think so with this one, i always hated LG, but i fell in love with the physical keyboard, even before NoDo i didnt have marketplace issues... out of the three from AT&T, this one is def my fave, and it seems like it is just so much easier to hack and change with MFG... with your HD7, does it have anything like MFG already on the phone? My understanding was HTC phones had to use software on ur PC to get inside
Someone please explain how to properly decompile the kcm.bin so that it can be edited and recompiled. There are quite a few of us who would like to remap certain hardware buttons (mainly custom user keys) but just using the files from (this thread) leaves us with some broken keys, the "?" key mainly... but some would also like to tweak this layout and don't have a proper tutorial. I will gladly donate a minimum of $10USD to the first person who properly explains the process for both *nix and windows environments.
This is another approach.
(If you have already read this and it is not the way you want it, I am sorry)
According to http://forum.xda-developers.com/showthread.php?t=1285244&page=3
In short:
# Remount
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# fetch Keylayout
adb pull /system/usr/keychars/vision-keypad-wwe.kcm.bin /tmp/vision-keypad-wwe.kcm.bin
# edit Keylayout according to Thread above with a hex editor
For example A 2 a A ! ! that represents:
A: Scancode
2: Does not matter
a: Letter when button connected to the keycode is pushed
A: SHIFT + button connected to the keycode is pushed
!: ALT + button connected to the keycode is pushed
!: SHIFT + ALT + button connected to the keycode is pushed
(for me ALT = FN)
# push it back
adb push /tmp/vision-keypad-wwe.kcm.bin /system/usr/keychars/vision-keypad-wwe.kcm.bin
The first line in every row is the constant value of the keycode.
For example: http://developer.android.com/reference/android/view/KeyEvent.html#KEYCODE_A
For Button A it is: 29 in decimal, 1D in hex.
With this approach you can change every key, but only the printable characters.
Search button will not work, as it is implemented in another way...
ok, not sure if I missed something, but specifically I need to modify the ? key and the 3 user assignable keys on the g2/dz keyboard... I don't see in the hex editor any line that starts with the ? symbol then has a number and two more chars/symbols after the number (ie: A 2 a A ! ! )
when I load keynumber tracker app the ? key reports "214" the user assignable keys report 183, 184 and 185... I'm just not sure what to do with those numbers, or how they help me modify anything...
I guess I just don't understand what I'm doing...
Ok, so I noticed in hex editor that the only difference between the modded kcm.bin and the stock one where my ? key works (besides the remapped keys) was the last 64 blocks of hex so I copy /pasted that part to the modded kcm.bin then saved and pushed... Now it's working, thanks so much, will PM you momentarily to get your paypal addy. Sooooo happy!!!
Edited w/ a cold press a CNC and a water jet @ 30,000PSI.
Hi,
I use SwiftKey ($) as my standard keyboard on the S3 since the built in keyboard mostly stinks. But the one problem is the input method reverts to the Samsung keyboard when the device reboots. I searched around & couldn't find exactly what I was after, so thought I'd post my solution here to pay it forward. :angel:
Requirements:
Rooted phone (using SuperSU free)
Tasker ($)
Secure Settings (free)
Busybox (free)
Process:
0. before starting, install Secure Settings, go to system+ tab, click to enable. It will help you get busybox if not installed. Once installed, again go to system+ tab and get it Enabled.
1. create a tasker "Event" profile
2. Event type is System>Device Boot. There are no options here, tap to go back
3. New task, give it a name ("Change Input Method" is good)
4. + to create an action, then Task>Wait. I put 40 seconds here. This is the delay after reboot before tasker goes & changes the method. It takes a while for my phone to be ready to roll after a reboot. YMMV. Tap top left to go back.
5. Now + to add another action and select plugin
6. Secure Settings, pencil to modify configuration
7. System+ Actions>Input Method, tap to select the input method (Swiftkey for me but this could be anything you want).
8. Click the save icon.
That's it. Try rebooting and see if the input method is changed to Swiftkey after the reboot. Works for me! Enjoy! :laugh:
Hi for all this is my first thread
I am not responsible for any errors that may get in your phone
I was test it in my phone gt-i9301i
1-Open the dialer (dial pad)
2-Insert *#0011# (you needn't to tap call button)
3-Press the menu button and select back(don't not press back button)
4-Press the menu button again and select 'key input' menu item
5-Enter "Q0000" then tap ok
Wait for about 10 seconds.and you will see servicemod menu
NOTE: Make a Backup for (efs) by use recoveryORtwrp(recommended)
Sorry for my English C u
Wrong!
Push menu, tap back then push menu again tap key input & write Q0000 (Q 4 zeros) wait & there you go.
Zola III said:
Wrong!
Push menu, tap back then push menu again tap key input & write Q0000 (Q 4 zeros) wait & there you go.
Click to expand...
Click to collapse
OK thank (Zola III) but You can see the third step?
it seems that while adding non-remappable assistant buttons is a growing trend, solutions aren't easy to find, however the solution is real simple, you just have to modify the keymap file...
I successfully managed to get the button detected by flashing XperiaGAButtonRemap through magisk, and I'm pretty sure the same solution works for a bunch of other phones also, it even has code that should allow flashing through custom recoveries also.
all you have to do is "install from storage" in magisk manager, select the zip, and reboot.
what that zip does, is it adds /system/vendor/usr/keylayout/gpio-keys.kl (overriding /system/usr/keylayout/gpio-keys.kl because /vendor has higher priority) and replaces the ASSISTANT key with PROG_BLUE, which is a dummy key, you can remap that with any remapper app or module, or you could edit the zip, and change it directly to something like CAMERA, if that's all you want.
here's what the file will look afterwards, if you're curious:
key 115 VOLUME_UP
key 114 VOLUME_DOWN
key 102 HOME
key 528 FOCUS
key 766 CAMERA
key 457 PROG_BLUE
the original file has copyright notice for The Linux Foundation, from 2013, but all other keys map the same, so it's highly likely most phones (at least the AOSP-adjacent ones) just have hooks for the ASSISTANT key, but still rely on the universal keymap file
thanks a lot!worked just fine,
big ups!!!
Hello, sorry for the question, does this work on Android 12?
SHANOA_zasha said:
Hello, sorry for the question, does this work on Android 12?
Click to expand...
Click to collapse
I've just tested and yes it works in A12