[INFO/WIP] List of ASUS apps/libs/etc that can be removed 'safely?' - Eee Pad Transformer Android Development

PROCEED AT YOUR OWN RISK.
THIS IS WHAT I PERSONALLY DELETE. Tested on my eeePad, no keyboard dock, running Prime 1.3 US version. You can customize the list based on your needs. See the 2nd list for ASUS keyboard information thanks to seshmaru. Also keep in mind you can rename the files from .apk to .old or something else if you want to test. Or keep a copy of the ROM you are modifying handy, and just repush the apk or lib back to where you deleted it from.
Here is the list:
Code:
All listed apks can be found in /system/app
[B][U]APK:[/U][/B]
AsusSetupWizard.apk ** OPTIONAL ** Setups your eeePad from a clean install (wifi/accounts/etc)
AsusReader.apk -- Reader stuff
AWS.apk - Asus Web Storage
DLNA.apk - Local network sharing thingy, never worked for me
Layar.apk - lame
MEar.apk - [URL="http://www.appbrain.com/app/mear-my-ear-wears-music/com.ecareme.mear"]music app[/URL] (not the google one)
MyCloud.apk -- ASUS stuff
MyGazine.apk -- ASUS stuff
MyWater.apk -- ASUS stuff
PCSyncLauncher.apk -- Annoying sync thingy when you attach USB cable (optional)
PixWe.apk -- Asus Cloud Storage Picture App
PolarisOffice.apk -- use google docs, or keep this (optional, keep related libs below)
PRAndroid.apk -- 'PressReader' for Newspapers/Magazines
StrAsus.apk -- it says asus, deleted. Something about "SplashTop"
Vibe.apk -- something stupid, music related.
Weather.apk -- asus weather stuff, optional
[I]-- Provided by seshmaru --[/I]
Phone.apk - we can't make calls on this thing anyways.
HTMLviewer.apk - broken anyways.
PicoTts.apk - text to speech for android. (Causes Text-to-Speech FC in Settings)
TtsService.apk - Also text to speech. (Causes Text-to-Speech FC in Settings)
[B][U]LIBS:[/U][/B]
/system/lib/libereader.so -- I believe this is AsusReader related.
/system/lib/libpolarisoffice.so -- huge office lib, deleeeeeeeeete (keep if you keep PolarisOffice.apk)
/system/lib/libpolarisoffice_Clipboard.so -- more office.. (keep if you keep PolarisOffice.apk)
[I]-- provided by seshmaru --[/I]
system/lib/libttspico.so (Causes Text-to-Speech FC in Settings)
system/lib/libvideoeditor_jni.so
Keyboard & Dock information thanks to seshmaru's post:
Code:
Here's a list for the keyboard files.
Needed for software keyboard:
[COLOR="Blue"]XT9IME.apk
/system/lib/libjni_xt9input.so
/system/lib/libjni_xt9kcm.so
/system/usr/xt9[/COLOR]
Needed for dock keyboard:
[COLOR="Blue"]Keyboard.apk
/system/usr/keylayout/asusec.kl
/system/usr/keychars/asusec.kcm[/COLOR]
You can remove all of the dock keyboard stuff and have the asus software keyboard still work and vice versa.
You can delete these while the system is running, but expect odd behavior and force closes. Rebooting should fix, you might have to force a power off, or use 'adb reboot'.
Ringtones: We have a full set of ringtones included. We should be able to delete all of these and save more space, but not sure if anyone has a use for them. These are RINGTONES and not NOTIFICATION sounds. These can be found here: /system/media/audio/ringtones -- it's only 2MB so probably not worth it.
This should be considered a work in progress. My list has not been tested while using the ASUS dock. It also has not been tested on builds, such as the WW (worldwide?) one. Consider this US builds only.

Your "Mod" breaks the dock, breaks key mapping, breaks autocorrect and basically breaks everything nice about the transformer, just so you know.
definition of minimalist is simplifying form without losing function. What you did isn't minimalist, it's "lets tear everything out of the system to the point where it hardly functions".

Agreed.
ROM devs, please do not do this by default in your ROMs.

seshmaru said:
Your "Mod" breaks the dock, breaks key mapping, breaks autocorrect and basically breaks everything nice about the transformer, just so you know.
definition of minimalist is simplifying form without losing function. What you did isn't minimalist, it's "lets tear everything out of the system to the point where it hardly functions".
Click to expand...
Click to collapse
Thanks for the heads up. I'll see what I can do, but without a dock, I can't test to see what is needed. Most likely the ASUS keyboard stuff is needed to make the dock work. I made those red color in my post.
I didn't tear everything out. I tore out the obvious stuff that I didn't need. Made a list, and shared it. Since I don't have a dock (nor do I want one), I removed all the ASUS keyboard stuff as well since I like the stock keyboard better.

Also not 100% sure on this, but I think you need Asus PC Sync for adb to work. PixWe is the built in screenshot function I believe. So the screenshot option in settings will break.

seshmaru said:
Also not 100% sure on this, but I think you need Asus PC Sync for adb to work. PixWe is the built in screenshot function I believe. So the screenshot option in settings will break.
Click to expand...
Click to collapse
I have adb working on mine still, and I'll test the screenshot function now. There is an .apk called screenshot.apk that I didn't remove, and I saw the toggle option in settings to turn it on.
I'll test after dinner and see.
For ADB to work, I had to manually turn on USB debugging in Settings / Applications / Development

sirmx said:
edit/note: I'm a minimalist by nature
PixWe.apk -- dunno, but sounds lame
Click to expand...
Click to collapse
i love your thinking, i do the same thing... sounds boring and i know it doesnt brick it delete it!

Also you don't need /system/usr/keylayout/asusec.kl to use the Asus software keyboard (XT9IME.APK), asusec.kl is the keymapping file for the dock. Otherway around as well, you can remove XT9IME.APK and still have the dock work, it's just the software keyboard.
EDIT:
Here's a list for the keyboard files.
Needed for software keyboard:
XT9IME.apk
/system/lib/libjni_xt9input.so
/system/lib/libjni_xt9kcm.so
/system/usr/xt9
Needed for dock keyboard:
Keyboard.apk
/system/usr/keylayout/asusec.kl
/system/usr/keychars/asusec.kcm
You can remove all of the dock keyboard stuff and have the asus software keyboard still work and vice versa.

seshmaru said:
Also you don't need /system/usr/keylayout/asusec.kl to use the Asus software keyboard (XT9IME.APK), asusec.kl is the keymapping file for the dock. Otherway around as well, you can remove XT9IME.APK and still have the dock work, it's just the software keyboard.
EDIT:
Here's a list for the keyboard files.
Needed for software keyboard:
XT9IME.apk
/system/lib/libjni_xt9input.so
/system/lib/libjni_xt9kcm.so
/system/usr/xt9
Needed for dock keyboard:
Keyboard.apk
/system/usr/keylayout/asusec.kl
/system/usr/keychars/asusec.kcm
You can remove all of the dock keyboard stuff and have the asus software keyboard still work and vice versa.
Click to expand...
Click to collapse
Sweet! Thanks for testing I'll add to OP
edit: adb still working
Code:
adb shell
# uname -a
uname -a
Linux localhost 2.6.36.4-netformer-1.0-ga063d5f #1 SMP PREEMPT Sat May 21 19:45:
10 CDT 2011 armv7l GNU/Linux
# date
date
Sun May 22 17:14:32 EDT 2011
#

Some more apk's you can delete:
Phone.apk - we can't make calls on this thing anyways.
HTMLviewer.apk - broken anyways.
PicoTts.apk - text to speech for android.
TtsService.apk - Also text to speech.
removable libs:
system/lib/libttspico.so
Also interesting find: we have the libs for the video editor apk but not the apk itself:
system/lib/libvideoeditor_jni.so
You can remove this since we don't have the video editor on our devices.
Also anybody know what Finsky.apk is?
EDIT: system/lib/ also holds some android SDK installer files for some reason.

for some ungodly reason every single dock button unlocks the keyboard, so why did they put a lock button on the dock?
asusec.kl content:
Code:
key 41 GRAVE WAKE UNLOCK
key 2 1 WAKE UNLOCK
key 3 2 WAKE UNLOCK
key 4 3 WAKE UNLOCK
key 5 4 WAKE UNLOCK
key 6 5 WAKE UNLOCK
key 7 6 WAKE UNLOCK
key 8 7 WAKE UNLOCK
key 9 8 WAKE UNLOCK
key 10 9 WAKE UNLOCK
key 11 0 WAKE UNLOCK
key 12 MINUS WAKE UNLOCK
key 13 EQUALS WAKE UNLOCK
key 14 DEL WAKE UNLOCK
key 15 TAB WAKE UNLOCK
key 16 Q WAKE UNLOCK
key 17 W WAKE UNLOCK
key 18 E WAKE UNLOCK
key 19 R WAKE UNLOCK
key 20 T WAKE UNLOCK
key 21 Y WAKE UNLOCK
key 22 U WAKE UNLOCK
key 23 I WAKE UNLOCK
key 24 O WAKE UNLOCK
key 25 P WAKE UNLOCK
key 26 LEFT_BRACKET WAKE UNLOCK
key 27 RIGHT_BRACKET WAKE UNLOCK
key 43 BACKSLASH WAKE UNLOCK
key 58 CAPS_LOCK WAKE UNLOCK
key 30 A WAKE UNLOCK
key 31 S WAKE UNLOCK
key 32 D WAKE UNLOCK
key 33 F WAKE UNLOCK
key 34 G WAKE UNLOCK
key 35 H WAKE UNLOCK
key 36 J WAKE UNLOCK
key 37 K WAKE UNLOCK
key 38 L WAKE UNLOCK
key 39 SEMICOLON WAKE UNLOCK
key 40 APOSTROPHE WAKE UNLOCK
key 28 ENTER WAKE UNLOCK
key 42 SHIFT_LEFT WAKE UNLOCK
key 44 Z WAKE UNLOCK
key 45 X WAKE UNLOCK
key 46 C WAKE UNLOCK
key 47 V WAKE UNLOCK
key 48 B WAKE UNLOCK
key 49 N WAKE UNLOCK
key 50 M WAKE UNLOCK
key 51 COMMA WAKE UNLOCK
key 52 PERIOD WAKE UNLOCK
key 53 SLASH WAKE UNLOCK
key 54 SHIFT_RIGHT WAKE UNLOCK
key 29 CTRL_LEFT WAKE UNLOCK
key 217 SEARCH WAKE UNLOCK
key 57 SPACE WAKE UNLOCK
key 100 ALT_RIGHT WAKE UNLOCK
key 97 CTRL_RIGHT WAKE UNLOCK
key 115 VOLUME_UP WAKE UNLOCK
key 142 SLEEP WAKE UNLOCK
key 105 DPAD_LEFT WAKE UNLOCK
key 103 DPAD_UP WAKE UNLOCK
key 108 DPAD_DOWN WAKE UNLOCK
key 106 DPAD_RIGHT WAKE UNLOCK
key 158 BACK WAKE UNLOCK
key 238 WIRELESS WAKE UNLOCK
key 237 BLUETOOTH WAKE UNLOCK
key 60 TOUCHPAD WAKE UNLOCK
key 224 BRIGHTNESS_DOWN WAKE UNLOCK
key 225 BRIGHTNESS_UP WAKE UNLOCK
key 61 BRIGHTNESS_AUTO WAKE UNLOCK
key 212 CAPTURE WAKE UNLOCK
key 150 EXPLORER WAKE UNLOCK
key 62 SETTINGS WAKE UNLOCK
key 165 MEDIA_PREVIOUS WAKE UNLOCK
key 164 MEDIA_PLAY_PAUSE WAKE UNLOCK
key 163 MEDIA_NEXT WAKE UNLOCK
key 114 VOLUME_DOWN WAKE UNLOCK
key 113 VOLUME_MUTE WAKE UNLOCK
key 172 HOME WAKE UNLOCK
key 139 MENU WAKE UNLOCK
key 104 PAGE_UP WAKE UNLOCK
key 109 PAGE_DOWN WAKE UNLOCK
key 107 MOVE_END WAKE UNLOCK
key 102 MOVE_HOME WAKE UNLOCK
key 86 EUROPE_2 WAKE UNLOCK
EDIT: Another funny thing, a line in build.prop tells us it doesn't have sd card support?
Code:
ro.build.characteristics=tablet,nosdcard
EDIT 2:
For any of you audiophiles, all the speaker settings and equalizer settings can be found in the system/data/srs_processing.cfg file. You can edit it with notepad and push it back to your device.

seshmaru said:
For any of you audiophiles, all the speaker settings and equalizer settings can be found in the system/data/srs_processing.cfg file. You can edit it with notepad and push it back to your device.
Click to expand...
Click to collapse
I'm pretty sure audiophiles don't listen to music on their tablets ;P

Finsky.apk, according to random google searches, has to do with the Market as well. I didn't even want to touch that after I read this.
I wonder if the nosdcard deal is because our /sdcard isn't really an sdcard?
I'll modify the OP with the info you have provided. Seems like you are having fun?

sirmx said:
Finsky.apk, according to random google searches, has to do with the Market as well. I didn't even want to touch that after I read this.
I wonder if the nosdcard deal is because our /sdcard isn't really an sdcard?
I'll modify the OP with the info you have provided. Seems like you are having fun?
Click to expand...
Click to collapse
I enjoy digging through system files I used to do mods for the HTC hero but I don't have the time anymore.
I'm pretty sure audiophiles don't listen to music on their tablets ;P
Click to expand...
Click to collapse
If they have a portable DAC why not?
EDIT: Framework-res shows signs of the upcoming phone interface,
this is the redesigned slider for the unlock screen on phones:
default graphic
pressed graphic
It doesn't seem to be in use yet as the xml files point to the classic glass style slider button.

seshmaru said:
I enjoy digging through system files I used to do mods for the HTC hero but I don't have the time anymore.
Click to expand...
Click to collapse
Yes, I had a HTC Hero CDMA model, and loved trying to get the Sense ROM as small as possible, then use the Custom MTD mod to have as much room for /data as possible. I'm more a a 'oh what happens if I delete this' then 'I know what this does' kind of guy. Trial and error lol, can't really break anything.
Anyway, I'm done poking around today. Managed to get the Prime 1.3 zip down to just at 150MB unsigned (removed ringtones, broke dock support since I don't have one, and removed all but 1 notification and alarm).
EDIT: Okay, we can't get rid of the TTS stuff without a FC in Settings / Language & Input / Text-to-speech Settings -- I had to repush all the TTS files to get it to work. This is still optional, at least.

Pretty sure libjUPnPCP.so has something to do with the DLNA application.. Why else would you need to detect a upnp device?

Thanks, I wanted to rip splashtop out of this thing already. Causes some of my apps for FC.

List of what i have removed so far:
AsusReader.apk LatinImeGoogle.apk PolarisOffice.apk
AsusSetupWizard.apk LatinImeTutorial.apk PRAndroid.apk
AWS.apk Launcher2.apk Screenshot.apk
Browser.apk Layar.apk SoundRecorder.apk
CifsManager.apk LiveWallpapersPicker.apk StrAsus.apk
DLNA.apk MEar.apk Street.apk
DMClient.rename MyCloud.apk Talk.apk
Email.apk MyGazine.apk TelephonyProvider.apk
EmailWidget.apk MyWater.apk Vibe.apk
FileManager.apk PCSyncLauncher.apk VoiceSearch.apk
GoogleQuickSearchBox.apk Phone.apk Weather.apk
HTMLViewer.apk PixWe.apk XT9IME.apk

Just exactly do you remove them? I am trying to rename StrAsus.apk in root explorer and it keeps saying I can't. So could you tell me the commands I need to use in ADB, I am not used to it.

adb remount
adb shell
rm /pathoffiles

Related

[GUIDE] How to Remap Hardkey Actions || Custom App Launching

This is really a low-level type of hack, as it just requires editing a few files.
------------------------------------------------------------------------------------------
Sick of the Hero not having a designated "camera" button?
Well then, remap the damn thing.
How to:
MAKE A BACKUP OF THE FILE BEFORE PROCEEDING
Firstly, we'll need to pull the file that controls the heroc keypad which is entitled "heroc-keypad.kl" in "system/usr/keylayout".
To pull the file:
Code:
adb remount
adb pull system/usr/keylayout/heroc-keypad.kl heroc-keypad.kl
Now the file will appear in your Android SDK tools folder so you can edit it.
I recommend using Notepad++ but any kind of text editing tool will work.
Now open the file and it should look a little something like this(minus the "unuse" keys):
Code:
key 102 HOME
key 139 MENU WAKE_DROPPED
key 158 BACK
key 127 SEARCH
key 231 CALL
key 107 ENDCALL WAKE_DROPPED
key 191 DPAD_CENTER
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
As you can see, there are different attributes assigned to each key.
Specific application/action launchers:
Code:
HOME #Launches "Home"
MENU #Launches "Menu"
BACK #Takes you back to the last activity
SEARCH #Launches "Universal Search"
CALL #Launches the "Phone" activity and corresponding .apk or initiates a call
ENDCALL #Ends a call
CAMERA #Launches "Camera" activity and corresponding .apk
FOCUS #Initiates Auto-Focus while using the Camera
VOLUME_UP #Self explanatory
VOLUME_DOWN #^
And attributes saying if it should wake the phone at button push to complete the action, or if it should just complete the action without waking the screen.
Code:
WAKE #Completes the action without waking the screen
WAKE_DROPPED #Wakes the phone to complete the action
NOTE: "CAMERA" can't utilize the "WAKE_DROPPED" attribute since it's an attempt to launch an activity without initializing anything else.
Anyways you can assign any of these attributes to any of the keys.
Personally, I remap the Phone button to launch the Camera, and the Search button to activate Auto-Focus:
Code:
key 231 CAMERA
key 127 FOCUS
Then when I'm using the Camera, I just hold down the "SEARCH" button to focus and push the "TALK" button to take a snapshot.
After you're done with your edits, you'll need to save the file properly(NO .txt files!), and then you'll have to push it back to the phone.
Code:
adb remount
adb push heroc-keypad.kl /system/usr/keylayout
Reboot your phone, and then long press the selected button to see if your edits worked!
Enjoy!
UPDATE!!!!
Code:
--------------------------------------------------------------------
key 200 MEDIA_PLAY_PAUSE #Pauses Music
key 201 MEDIA_PLAY_PAUSE #^
key 166 MEDIA_STOP #Stops the media
key 163 MEDIA_NEXT #Plays next media
key 165 MEDIA_PREVIOUS #Plays previous media
key 168 MEDIA_REWIND #Rewinds the media
key 208 MEDIA_FAST_FORWARD #Fast Forwards the media
The second half is from the AVRCP.kl which controls media actions on our device. But as you can see the keys aren't correctly mapped as we don't have that many(or those key numbers) at our disposal.
What you can actually do is take these attributes and map them in heroc-keypad.kl
Code:
key 102 HOME
key 139 MENU WAKE_DROPPED
key 158 BACK
key 127 MEDIA_PLAY_PAUSE WAKE
key 231 CALL
key 107 ENDCALL WAKE_DROPPED
key 191 DPAD_CENTER
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
This maps the attribute "MEDIA_PLAY_PAUSE" at the "SEARCH" key. By pushing it, you can pause media with the first push and play it with a successive push. The added attribute "WAKE" allows it to complete the action without waking the phone.
__________________________________________________________________________________________________
I want to thank Geniusdog254 for the heads up regarding not having to edit AVRCP.kl
CHECK OUT HIS FREE APP: Search2Play(Hero/Evo support!)
and
CHECK OUT HIS REMAPPING MOD FOR THE G1
Big thanks!
NOTE: You can also use Root Explorer or any other Root File Manager that has Text Editing
Custom app launching
Ok, so with some inspiration from BuglessPete's How to make script run by using hardware keys. I've devised an 'idea' as to how to custom launch an activity with keypad push.
Currently, you can launch any activity from shell by just using am.
Here's an example of launching the browser using am in the shell:
Code:
am start -a android.intent.action.MAIN -n com.android.browser/.BrowserActivity
Which results in:
Code:
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.browser/.BrowserActivity }
And the program launches!
But if you put this into a script, even a basic linux shell script, you can call it quickly just by running the script! So in theory if you map this script to a keycode, you can call the script by a button push.
How?
Well first, before you compile the ramdisk, you need to create a service that contains the script necessary for the intent activity you are trying to accomplish.
Second, you have to add the proper keycodes in an init script of your choice:
Code:
#example
service <activity> /path/to/yourservice
oneshot
disabled
keycodes 107 127
Which maps the activity to the search button after launching the service with the endcall button
This is currently just a theory as I haven't tested it out myself(busy with other things).
But if you would like to attempt it, I'd love feedback.
Quick Service Creation Tutorial: http://developerlife.com/tutorials/?p=356
Little error.. heroc_keypad.kl is in /system/usr/keylayout/heroc_keypad.kl.
EDIT: And it's heroc-keypad and not heroc_keypad.
HeroMeng said:
Little error.. heroc_keypad.kl is in /system/usr/keylayout/heroc_keypad.kl.
Click to expand...
Click to collapse
Nice catch, lol.
Always forget something simple.
EDIT: I really need to start posting stuff while using my laptop.
nice
thanks man this is awesome.
im just "learning" linux. how would i set up the search button for an intent(sp) like opening the browser.apk
feefeeboomboom said:
thanks man this is awesome.
im just "learning" linux. how would i set up the search button for an intent(sp) like opening the browser.apk
Click to expand...
Click to collapse
Well "SEARCH" essentially launches the browser by linking it automatically to google search.
But, in regards to assigning it to launch a different(unlisted) activity, I'm not sure. That's something I'm actually looking into myself, and I think I'm making a little bit of head way .
Haha great work [HOPE]maybe the hero development won't die[/HOPE]
I'm putting this in my sig if you don't mind?
thatguythatdid said:
Haha great work [HOPE]maybe the hero development won't die[/HOPE]
Click to expand...
Click to collapse
As long as there are people there willing to learn, development for the Hero will never die.
[RANT]
I'll make a post in the General Section with all the bookmarked dev'ing related resources that I've found over the year. Then people can just jump in and start reading/tinkering.
What I don't like about the HeroCDMA forum is that most of the community here doesn't share much of HOW they did/do things. Hopefully that will change.
=D
[/RANT] (Please don't respond to this part, haha)
almost forgot what program are you using to open the kl file? Mine always comes out in a horizontal line instead of a vertical like yours?
Edit: Nevermind wordpad does it great
notepad++ is the sh!-|-
feefeeboomboom said:
notepad++ is the sh!-|-
Click to expand...
Click to collapse
I'm a dumbass. I didn't read the entire post before I asked my question and thought that nevermind. Yes notepad is the s
Good work, thanks for putting together a very easy to read how-to.
Thanks for this, the trackball is so annoying for pictures. I made the changes just as it states to but the zoom won't work on the search button, I hold it down and it does nothing, any idea why that may be? And the search button no longer responds on the homescreen, which makes sense but why not in the camera app?
chrish03 said:
Thanks for this, the trackball is so annoying for pictures. I made the changes just as it states to but the zoom won't work on the search button, I hold it down and it does nothing, any idea why that may be? And the search button no longer responds on the homescreen, which makes sense but why not in the camera app?
Click to expand...
Click to collapse
Zoom? Do you mean auto-focus?
I want to do this but I cant get my phone to remount. I have never had a problem before.
cd c:\android-sdk-windows\tools
adb remount
doesn't remount says "no devices found"
CarbonKang said:
I want to do this but I cant get my phone to remount. I have never had a problem before.
cd c:\android-sdk-windows\tools
adb remount
doesn't remount says "no devices found"
Click to expand...
Click to collapse
Heh, is your phone plugged in? USB cable damaged? USB port damaged? Hole plugged? Bears?
If it's none of those, do this:
Code:
adb kill-server
adb start-server
then
Code:
adb remount
If that doesn't work, start from the top again.
Decad3nce said:
Zoom? Do you mean auto-focus?
Click to expand...
Click to collapse
LOL, reading comprehension FTW! I got FOCUS and ZOOM confused. Don't play with your phone late at night!
Decad3nce said:
Heh, is your phone plugged in? USB cable damaged? USB port damaged? Hole plugged? Bears?
If it's none of those, do this:
Code:
adb kill-server
adb start-server
then
Code:
adb remount
If that doesn't work, start from the top again.
Click to expand...
Click to collapse
none of that worked. And there is nothing wrong with the ports at all. I think its Darchdroid.. It has something defective every time I use it lol.
CarbonKang said:
none of that worked. And there is nothing wrong with the ports at all. I think its Darchdroid.. It has something defective every time I use it lol.
Click to expand...
Click to collapse
Do you have USB debugging enabled?
(I haven't had any problems with darchs build)
Decad3nce said:
Do you have USB debugging enabled?
(I haven't had any problems with darchs build)
Click to expand...
Click to collapse
ya, trust me I know what I'm doing.
It just doesn't work
I would love to show you a logcat... but i cant adb remount LOL
Can someone make a flashable zip so i can have a designated camera button as search? I want to be able to click it to take a snap shot of my phone with dro cap.
Thanks

Apple Wireless keyboard driver for Android

I use an Apple Wireless keyboard with my android phone and it works well but not perfectly. Many keys aren't mapped properly.
On this thread I hope some skilled people will come along and help generate a keymap bin file for this great keyboard so more android users can benefit from it.
Checking the logs when the phone connects to the keyboard show:
W/KeyCharacterMap(13414): Can't open keycharmap file
W/KeyCharacterMap(13414): Error loading keycharmap file '/system/usr/keychars/Apple_Wireless_Keyboard.kcm.bin'. hw.keyboards.196612.devname='Apple Wireless Keyboard'
W/KeyCharacterMap(13414): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
Click to expand...
Click to collapse
So it appears we just need to generate an Apple Wireless Keyboard kcm file and this page should help: http://www.kandroid.org/android_pdk/keymaps_keyboard_input.html#androidKeymapIntro
I am going to have a go but am probably not technically skilled enough for this.
i got the same problem, but no solution...
I use the apple wireless keyboard, the norwegian version, and of course the layout for default bluetooth keyboard is english and doesn't match the hardware keys for my norwegian keyboard. My question is about the file pointed to here:
"Using default keymap: /system/usr/keychars/qwerty.kcm.bin"
Is this in any way related to the on-screen keyboard? If not, if it will be working as a default with the apple keyboard, then maybe it is possible to just manually edit the file? I don't know anything about this, so sorry if this is a stupid question My phone is not rooted, so I don't even have access to "/system/usr/keychars/qwerty.kcm.bin"..
I would very much appreciate if anyone could check this on their phone, maybe paste the contents of the file here? If one could easily change the mapping of the bluetooth keyboard in this file, this could work for me.
In my case, I'm satisfied with the keyboard, works well, but the default layout is in english and that means I can't use the norwegian hardwarebuttons "ÆØÅ".
Have been trying a bit on my own, with the fear of "bricking" my device,
I am a total noob with android so please don't laugh if my ideas are stupid
Please help!
The file /system/usr/keychars/qwerty.kcm.bin seems impossible to edit.
However, I found the file /system/usr/keylayout/qwerty.kl
The following is the contents of the file:
key 399 GRAVE
key 2 1
key 3 2
key 4 3
key 5 4
key 6 5
key 7 6
key 8 7
key 9 8
key 10 9
key 11 0
key 1 BACK WAKE_DROPPED
key 158 BACK WAKE_DROPPED
key 230 SOFT_RIGHT WAKE
key 60 SOFT_RIGHT WAKE
key 107 ENDCALL WAKE_DROPPED
key 62 ENDCALL WAKE_DROPPED
key 229 MENU WAKE_DROPPED
key 139 MENU WAKE_DROPPED
key 59 MENU WAKE_DROPPED
key 127 SEARCH WAKE_DROPPED
key 217 SEARCH WAKE_DROPPED
key 228 POUND
key 227 STAR
key 231 CALL WAKE_DROPPED
key 61 CALL WAKE_DROPPED
key 232 DPAD_CENTER WAKE_DROPPED
key 108 DPAD_DOWN WAKE_DROPPED
key 103 DPAD_UP WAKE_DROPPED
key 102 HOME WAKE
key 105 DPAD_LEFT WAKE_DROPPED
key 106 DPAD_RIGHT WAKE_DROPPED
key 115 VOLUME_UP
key 114 VOLUME_DOWN
key 116 POWER WAKE
key 212 CAMERA
key 16 Q
key 17 W
key 18 E
key 19 R
key 20 T
key 21 Y
key 22 U
key 23 I
key 24 O
key 25 P
key 26 LEFT_BRACKET
key 27 RIGHT_BRACKET
key 43 BACKSLASH
key 30 A
key 31 S
key 32 D
key 33 F
key 34 G
key 35 H
key 36 J
key 37 K
key 38 L
key 39 SEMICOLON
key 40 APOSTROPHE
key 14 DEL
key 44 Z
key 45 X
key 46 C
key 47 V
key 48 B
key 49 N
key 50 M
key 51 COMMA
key 52 PERIOD
key 53 SLASH
key 28 ENTER
key 56 ALT_LEFT
key 100 ALT_RIGHT
key 42 SHIFT_LEFT
key 54 SHIFT_RIGHT
key 15 TAB
key 57 SPACE
key 150 EXPLORER
key 155 ENVELOPE
key 12 MINUS
key 13 EQUALS
key 215 AT
Click to expand...
Click to collapse
If I use a text-editor to edit this file, and save it in the same charset as the original, it should work, right?
When I press the hardwarebuttons -ÆØÅ- , I get ';[
so accordingly I am thinking of changing the following:
key 26 LEFT_BRACKET --> Å
key 39 SEMICOLON --> Ø
key 40 APOSTROPHE --> Æ
I fear that I will "brick" my phone if this doesn't work. Does anyone have an opinion?
If this is indeed a stupid idea, I hope somebody can tell me before I destroy my phone
I went ahead and tried this, after consulting an experienced friend who thought this wouldn't do any harm. It turned out this had no effect at all. Phone is ok, still nothing changed at all.
Found out how to edit the .kcm.bin-file and now I made it work for me,
and maybe others with norwegian apple keyboard
http://forum.xda-developers.com/showthread.php?p=11886341#post11886341
I have absolutely no skills in this, but was able to remap some simple buttons with the app Keytest.apk (simply google) and some alterations in the qwerty.kl and others,
i broke a couple of times the file i guess resulting the keyboard stop working but a simple backup put everything back in working order.
Ill try to play some with this in the next couple of days.
will let you know! and post my results!
Yes! If your keyboard is in english and that is also your prefered language, then it seems that all you have to do is alter the .kl-file used by the keyboard in order to get the symbols in proper places according to the scancodes given by "KeyTest.apk"
The phone will probably not be "bricked" in any case. If you make a mistake when editing the .kl-file, you can just use a backup to get it working again (at least if you have a working touch-screen).
Still, some combinations might not work that easily. Then you'll have to alter the .kcm.bin-file in a hex-editor, in my case for "æøå" and others, like for instance to get "7" and "/" on the norwegian keyboard to be on the same button, so that it gives "/" when typing "7" and holding shift (while english keyboards have "7" and "&" with shift if I'm not mistaken..)
i.e. the .kcm.bin-file contains a binary formated layout of the characters and the symbols to show accordingly when pressing normal, with shift, alt or fn, while the .kl-file only decides what scancodes from the keyboard referes to what characters in the .kcm.bin-file.
So editing the .kcm.bin-file, you could make all kinds of fun, for instance make shift+a print "£" in stead of "A". This file decides what symbols will show up on your screen when pressing a function-key like shift, alt, fn etc with a normal key. In this file you cannot alter the places on the keyboard, only existing combinations of characters.
The .kl-file will only let you change the places on the keyboard and not the existing keychars.
So in the .kl-file you cannot put in any foreign letters like german "ü" or french "ç",
but you can change the .kcm.bin-file to make alt+c print "ç" and shift+alt+c print "Ç".
Then just leave the "C" where it belongs in the .kl-file.
The biggest caveats with this solution is that there is no fast way to switch between two languages, for instance some times I write in cyrillic and some times in latin letters. For this I would have to manually change between two .kcm.bin-files, one in latin and one in cyrillic. (I am already planning how to make one in cyrillic)
Sorry for my bad english, don't write much in english hope my writing is understandable
If you cannot use the adb logcat to find out which file to edit, then just try to edit one letter in one .kl file for instance change the "K" to be "P", and see if it makes it print "P". If it doesn't then change it back, and do the same with the next .kl-file until you find the one you have to edit.
I would assume one has to disconnect the keyboard and maybe turn off bluetooth for every try, since the keyboard layout is probably loaded into memory as soon as it is connected, so a change wouldn't have any effect when it is connected.
Biffy said:
On this thread I hope some skilled people will come along and help generate a keymap bin file for this great keyboard so more android users can benefit from it.
Click to expand...
Click to collapse
I'm not so skilled, but I managed to do this with a norwegian keyboard.
I could try the same for english keyboard if I had at least a good picture of the
keyboard with the scancodes for every key, and also the original .kcm.bin / .kl files to alter. And also what combinations to alter. It is not so difficult.
I have created a qwerty.kl file to use the apple wireless keyboard with connectbot in landscape mode. It works great with cyanogenmod on my HTC DHD but should work with other phones / roms.
modifications :
- change arrows directions to match landscape mode (phone bottom on the right)
- map the left "ctrl" key of the keyboard to DPAD_CENTER so that it can be used as ctrl in connectbot as well as escape key (two presses).
modifications I would like to have
- have the escape key work correctly
- have the "tab" key work correctly in connectbot
To install, replace on your phone:
- unzip the file to your computer
- enable USB debugging
- remount partition in read write
Code:
adb remount
- backup the original file somewhere
Code:
adb pull /system/usr/keylayout/qwerty.kl $SAVE_PATH
- copy the new file to the phone
Code:
adb push $NEW_QWERTY.KL_LOCATION /system/usr/keylayout/
- reboot your phone (to remount the system partition read-only)
If you can improve, don't hesitate to publish

Moving the menu button back where it belongs

Let's face it, the menu belongs on your left thumb. We all know it.
It's not a hard fix.
First, you need to root your phone. Next, get Root Explorer from the market. (Other file managers and text editors can be used, but Root Explorer makes it easy.)
Navigate to /SYSTEM/USR/KEYLAYOUT/s3c-keypad.kl
(If you aren't using Root Explorer, make a backup copy of the original file before you edit!)
Open s3c-keypad.kl and make sure you are set to read and write the file.
It will look like this:
#
# NAGSM_SEL_FRAMEWORK
# abhilash.b - Keymaping and added custom labels - SYMBOL , MULTITASKER, SMILEY
#
key 16 1
key 17 2
key 25 3
key 33 4
key 41 5
key 49 6
key 2 7
key 10 8
key 18 9
key 67 0
key 68 Q
key 65 W
key 3 E
key 11 R
key 19 T
key 27 Y
key 35 U
key 43 I
key 51 O
key 59 P
key 20 A
key 28 S
key 36 D
key 44 F
key 52 G
key 60 H
key 5 J
key 13 K
key 21 L
key 4 DEL
key 45 SEARCH
key 53 Z
key 61 X
key 6 C
key 14 V
key 22 B
key 30 N
key 38 M
key 54 SMILEY
key 29 ENTER
key 15 SHIFT_LEFT
key 23 ALT_LEFT
key 56 AT
key 48 COMMA
key 63 SPACE
key 64 PERIOD
key 32 QUESTION
key 40 VOICE_INPUT
key 46 SHIFT_RIGHT
key 7 MULTITASKER
key 34 BACK WAKE_DROPPED
key 66 MENU WAKE_DROPPED
key 8 HOME WAKE
key 42 VOLUME_UP WAKE_DROPPED
key 58 VOLUME_DOWN WAKE_DROPPED
key 26 POWER WAKE
key 50 DPAD_CENTER WAKE_DROPPED
key 39 FOCUS
key 31 CAMERA
# Need to be interchanged later - abhilash.b
...Now, switch the HOME WAKE to the key 66 line and put the MENU WAKE_DROPPED on the key 8 line.
When you save it, Root Explorer cleverly makes a backup of the original for you.
Now, reboot and enjoy. The menu is back where it belongs (top left) and the home button has moved to the cancel key position--upper right.
It's easy fix and it makes the device feel more like home.
Sent from my SGH-T839 using XDA App
man kind of wish i had run into this earlier. Coming from the G1 I kept hitting the wrong buttons for a long time. Now i've already gotten used else i'd jump right on this
LesserAnimal said:
man kind of wish i had run into this earlier. Coming from the G1 I kept hitting the wrong buttons for a long time. Now i've already gotten used else i'd jump right on this
Click to expand...
Click to collapse
Lol same thing for me, im used to it now
hahaha omg i totally didn't even think about this. I might have to do this for the question mark too...
Would this allow us to change the trackball click function into a search button? Because that woukd solve the biggest flaw on this phone.
And if so, would trackball scrolling still work for text selection? I like that, just don't really use the trackball click. I'm guessing the trackball button would be the one labeled "center" right?
Falkner09 said:
Would this allow us to change the trackball click function into a search button? Because that woukd solve the biggest flaw on this phone.
And if so, would trackball scrolling still work for text selection? I like that, just don't really use the trackball click. I'm guessing the trackball button would be the one labeled "center" right?
Click to expand...
Click to collapse
if you can get that to work i'd remap my trackball to search as well. good idea .. never woulda though of that
ayoteddy said:
if you can get that to work i'd remap my trackball to search as well. good idea .. never woulda though of that
Click to expand...
Click to collapse
So did anyone try it?
Remapped long after getting "used" to the new menu location, now I get to re-train myself. Whoops. Ah well. It is where it should be now!
ayoteddy said:
if you can get that to work i'd remap my trackball to search as well. good idea .. never woulda though of that
Click to expand...
Click to collapse
Well my trackpad is officially now a search key all u do is replace line 50 with SEARCH (all upper case) and reboot so thank u guys for the information appreciate it
Edit: trackpad still scrolls too
Sent from my SGH-T839 using xda premium
Gplayjay said:
Well my trackpad is officially now a search key all u do is replace line 50 with SEARCH (all upper case) and reboot so thank u guys for the information appreciate it
Edit: trackpad still scrolls too
Sent from my SGH-T839 using xda premium
Click to expand...
Click to collapse
WOO! Thanks now it feels like my phone is fulfilled!
You can put your search button on the "multitasker" button. The key still works as a jump key when the phone is open.
You will lose access to your recent apps, but you can take care of that with a new launcher or a "prehome" app.
Just replace MULTITASKER with SEARCH.
Sent from my SGH-T839 using XDA App
I tried doing this without root explorer (don't want to pay) and I ant find any app that will open the file. I edit it and then I reboot my phone, nothing changes.
Sent from my SGH-T839 using XDA App
the search button works when changed to the trackpad thanks everyone
would this work on forcing the enter key to send a message instead of just creating a line break?
theU1991 said:
would this work on forcing the enter key to send a message instead of just creating a line break?
Click to expand...
Click to collapse
Sadly, it will not.
TTYTYTYTYTYTYTY sooo much ive been looking for this
pretty sick, gonna look at changing the smiley face key to be another ALT key. thanks!
---------- Post added at 06:43 PM ---------- Previous post was at 06:31 PM ----------
mksin11 said:
I tried doing this without root explorer (don't want to pay) and I ant find any app that will open the file. I edit it and then I reboot my phone, nothing changes.
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
root browser lite by JRUMMY16, free from market. got it just now to do this. worked perfectly. automatically makes a backup of the file for you when you save your edits. app seems solid overall.
---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------
alright, i changed the SMILEY key to ALT_RIGHT and it TOTALLY WORKS AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAH
This is perfect!
My Sidekick 4g took a bath this summer in a creek...the joy damage was the Back button stopped functioning.
I used this post to switch the Jump button to Back, since I never used the Jump button...and my phone works great now. Thanks!
very helpful, even though i'll probably screw this up. Is it possible to change jump key into launching a pre home app, like URL="https://playDOTgoogleDOTcom/store/apps/details?id=mohammad.adib.sidebar.lite"this one? (too new, cant post links)
fuzzie said:
This is perfect!
My Sidekick 4g took a bath this summer in a creek...the joy damage was the Back button stopped functioning.
I used this post to switch the Jump button to Back, since I never used the Jump button...and my phone works great now. Thanks!
Click to expand...
Click to collapse
How can I do that is the Jump key the one that says Multitasker?

How to disable the wake-up button

The play wakes up sometimes if the home key is pressed while in my pocket, this solve's the problem
Phone must be rooted and Root Explorer or an alternative installed.
- open root explorer and go to /system/usr/keylayout
- mount as R/W
- open keypad-pmic-zeus.kl in text editor
- go to the line KEY 102 HOME WAKE_DROPPED
- delete the text WAKE_DROPPED
- save & exit and reboot
Instructions got from this forum
http://forum.xda-developers.com/showthread.php?t=1126218
It's usefull tips,thanks
Sorry to resurrect a dead thread, but I actually just recently had enough of the home button waking my screen. With a search, I found this thread, and figured I'd bump it for the other Xperia Play noobs, like me.
I don't have that file and that file is keypad-zeus.kl - stock 2.3.4
take a look in keypad-phone-zeus. Think it might be in there.

[Q] How to Wake up Optimus 3D with volum key?

I try agilelock, wiget locker, lockbot pro... but no program work ... It work when I plug in usb or changer... When i plug out, I can't use volum key to wake up..
I need a help..
Thank you very much...
I believe its cause USB and charger doesn't really put the phone to sleep. It's still awake even if screen is off. However all those lock screen apps you tried will put phone to sleep.
Download an app called NoLock and give it a try. That'll remove the keyguard, but some people have discovered it also allows the phone to wake up from Volume Keys.
Technically, if your phone can wake up from volume keys, it can wake up from the 3D key too.
DevJackey said:
I believe its cause USB and charger doesn't really put the phone to sleep. It's still awake even if screen is off. However all those lock screen apps you tried will put phone to sleep.
Download an app called NoLock and give it a try. That'll remove the keyguard, but some people have discovered it also allows the phone to wake up from Volume Keys.
Technically, if your phone can wake up from volume keys, it can wake up from the 3D key too.
Click to expand...
Click to collapse
Thanks, i will download Nolock and try...
Have any mod about wake up by volum key? (wake up from sleep).. I search and found a lot of mod to do that (other device, my Optimus can't install ...)
Nolock don't work, i can't use volum or 3D key to wake up or unlock...
I've found this tweaks:
http://forum.xda-developers.com/showthread.php?t=1227269 not tested I don't know if it works
Try to insert in build.prop in /system (phone rooted)
ro.config.hwfeature_wakeupkey=1
Hope this help...
Claudio67 said:
I've found this tweaks:
http://forum.xda-developers.com/showthread.php?t=1227269 not tested I don't know if it works
Try to insert in build.prop in /system (phone rooted)
ro.config.hwfeature_wakeupkey=1
Hope this help...
Click to expand...
Click to collapse
work only when usb cable is connected...
Claudio67 said:
I've found this tweaks:
http://forum.xda-developers.com/showthread.php?t=1227269 not tested I don't know if it works
Try to insert in build.prop in /system (phone rooted)
ro.config.hwfeature_wakeupkey=1
Hope this help...
Click to expand...
Click to collapse
nic85 said:
work only when usb cable is connected...
Click to expand...
Click to collapse
Thanks, I will try...
uit.edu said:
I try agilelock, wiget locker, lockbot pro... but no program work ... It work when I plug in usb or changer... When i plug out, I can't use volum key to wake up..
I need a help..
Thank you very much...
Click to expand...
Click to collapse
If you still haven't got it there's an app in the market called magic locker. I'm using it to wake the phone using the volume keys.
Sent from my LG-P920 using xda premium
thegregulator said:
If you still haven't got it there's an app in the market called magic locker. I'm using it to wake the phone using the volume keys.
Sent from my LG-P920 using xda premium
Click to expand...
Click to collapse
not found 'called magic locker' in market,may you help me?pls.
TKs
---------- Post added at 01:43 PM ---------- Previous post was at 01:26 PM ----------
Tks all,i try app 'magic locker main' in market and it working.
binhxitrum said:
not found 'called magic locker' in market,may you help me?pls.
TKs
---------- Post added at 01:43 PM ---------- Previous post was at 01:26 PM ----------
Tks all,i try app 'magic locker main' in market and it working.
Click to expand...
Click to collapse
Glad you got it to work. It's a pretty great app actually!
Dear friend
I have installed the "Magic lock main" it just work within 01 minute when I sent my phone go to sleep, after 1minute I not work, I must used the power button to wake my phone up.
Please help me How to config the setting, I also used "Go lunch EX".
Thanks
No solution to wake up
Not quite what you guys are looking for but if you go to /system/usr/keylayout and open omap_keypad.kl scroll down and by key 249 3d_hot_key space over and add "wake" (you will see when you open the file just make it line up) you can use the 3d button to wake the phone up.
...fighting ninjas at night, talkin' about this and that.
Well if you use GO launcher EX you should test Go locker.
Enable Go locker and in setup take "Emergency unlock" on use.
It let you unlock phone by pressing volume button up or down for few seconds,
if thats the "wakeup" what you are finding for?
Urabewe said:
Not quite what you guys are looking for but if you go to /system/usr/keylayout and open omap_keypad.kl scroll down and by key 249 3d_hot_key space over and add "wake" (you will see when you open the file just make it line up) you can use the 3d button to wake the phone up.
...fighting ninjas at night, talkin' about this and that.
Click to expand...
Click to collapse
Thanks for your help... I follow you and have a question:
At "249 3D_Mode" I edit "249 3D_Mode Wake" ?
yesse87 said:
Well if you use GO launcher EX you should test Go locker.
Enable Go locker and in setup take "Emergency unlock" on use.
It let you unlock phone by pressing volume button up or down for few seconds,
if thats the "wakeup" what you are finding for?
Click to expand...
Click to collapse
I using Go locker and turn on Emergency Unlock, at 30s after lock phone, it works, after that is not..
Not quite what you guys are looking for but if you go to /system/usr/keylayout and open omap_keypad.kl scroll down and by key 249 3d_hot_key space over and add "wake" (you will see when you open the file just make it line up) you can use the 3d button to wake the phone up.
i follow your guide
works for me thank you Urabewe.....
1. i first have to change the permission for omap_keypad.kl by using file manager. if u don't change permission, u won't be able to save changes made.
2. stroll down to put key 249 3D_MODE WAKE (between mode and wake, put in some spaces )
3. save and reboot.
and now can be able to wake up screen that sleeps for longer than few minutes using 3d button
anduios said:
Not quite what you guys are looking for but if you go to /system/usr/keylayout and open omap_keypad.kl scroll down and by key 249 3d_hot_key space over and add "wake" (you will see when you open the file just make it line up) you can use the 3d button to wake the phone up.
i follow your guide
works for me thank you Urabewe.....
1. i first have to change the permission for omap_keypad.kl by using file manager. if u don't change permission, u won't be able to save changes made.
2. stroll down to put key 249 3D_MODE WAKE (between mode and wake, put in some spaces )
3. save and reboot.
and now can be able to wake up screen that sleeps for longer than few minutes using 3d button
Click to expand...
Click to collapse
Good it isn't quite the option you guys were looking for but still glad it works I am finding it pretty convienient uit.edu follow what anduios said. All you have to do is space over add in wake and you are good to go. Should wake phone up no matter how long it has been idle.
...fighting ninjas at night, talkin' about this and that.
anduios said:
Not quite what you guys are looking for but if you go to /system/usr/keylayout and open omap_keypad.kl scroll down and by key 249 3d_hot_key space over and add "wake" (you will see when you open the file just make it line up) you can use the 3d button to wake the phone up.
i follow your guide
works for me thank you Urabewe.....
1. i first have to change the permission for omap_keypad.kl by using file manager. if u don't change permission, u won't be able to save changes made.
2. stroll down to put key 249 3D_MODE WAKE (between mode and wake, put in some spaces )
3. save and reboot.
and now can be able to wake up screen that sleeps for longer than few minutes using 3d button
Click to expand...
Click to collapse
Is 3D button still work? For launching 3D space and other functions?
Yeah it is still set to open 3d space all you are doing is adding the wake function to the button. You don't remove anything you just space over and add wake. You will see what I mean when you open the file. The button should work as usual plus add the ability to wake phone.
What is really odd is that the vol keys actually have the wake function set just doesn't work.
...fighting ninjas at night, talkin' about this and that.
Sorry double post.
Easy way
1) open root explorer
2) go to /system/usr/keylayout
3) press the "mount r/w" button in top right
4) long press on omap-keypad.kl
5) scroll down on menu and choose "open in text editor"
6) scroll all the way down to bottom
7) at "key 249 3D_MODE" space over until cursor is lined up with the word wake on line above
8) type in "wake" make sure it is lined up with column above either add spaces or delete them to line it up
9) reboot phone
10) wake phone with 3d button
...fighting ninjas at night, talkin' about this and that.

Categories

Resources