Database Users

[Q] Modifying Stock Keyboard

Hey all,
I was wondering whats the process to modify the stock multi-touch keyboard for the Droid 2? I was able to do it with the multi-touch keyboard that Punk.Kaos ported to the Eris, using some Windows batch files for extracting the apk source, compiling, signing, etc. I just can't remember for the life of me what that little program was called. Any ideas?
Thanks!

it would be nice since the space bar is soooo small i keep pressing . instead of space 70% of the times

Alright, I was able to get the program I was thinking of, it is called APK Manager. But the keyboard is a odex file... Which I don't know how to extract the XML files from... Yet.

I'd de-odex before you try to extract. It will be a lot easier. There's the method I used here.

What exactly is de-odex'ing? How will it affect my phone?

Deodexing just means that all of the stray .odex files will be put back into the correct .apk files this is done mostly for theme purposes in order to edit the services.jar file which has to be de-odexed before it can be edited. It won't corrupt anything if you do it right nothing should change on the outside the phone devs leave the .odex files out for loading reasons but nothing significant should change but you might experience a slightly slower boot up process but like I said nothing significant. Most ROM's now are de-odexed though.

So I deodexed my phone so I could work on the LatinIME.apk package. Using the APK-Manager for Linux, I was able to (0) pull the APK from my phone. Then I (9) decompiled the APK, edited the XML files as I wanted.
Now, from here I'm not entirely sure which direction to take. I tried running (13) Compile APK / Sign APK / Install APK, but I got an error saying something on how the signatures didn't match up. Then I tried running (3) ZIP APK (5) Zipalign APK then (8) ADB push, but now I don't even have the keyboard on my phone anymore.
How can I go about doing the correct way to compile my modified code and install it on my phone?
Here are the options I can do, if you're not familiar with APK Manager:
Code:
------------------Simple Tasks Such As Image Editing----------------------
0 Adb pull
1 Extract apk
2 Optimize images inside (Only if "Extract Apk" was selected)
3 Zip apk
4 Sign apk (Dont do this if its a system apk)
5 Zipalign apk (Do once apk is created/signed)
6 Install apk (Dont do this if system apk, do adb push)
7 Zip / Sign / Install apk (All in one step)
8 Adb push (Only for system apk)
-----------------Advanced Tasks Such As Code Editing-----------------------
9 Decompile apk
10 Compile apk
11 Sign apk
12 Install apk
13 Compile apk / Sign apk / Install apk (All in one step)
---------------------------------------------------------------------------
14 Batch Optimize Apk (inside place-apk-here-to-batch-optimize only)
15 Sign an apk (inside place-apk-here-for-signing folder only)
16 Batch optimize ogg files (inside place-ogg-here only)
17 Quit
****************************************************************************

Anyone? I would love to get my stock keyboard back!
Sent from my DROID2 using XDA App

[MOD] 36DPI NavBar for OmniROM & How-To

Hey folks,
I'm running OmniROM on my Nexus 5 and was very much missing the option to change the NavBar height from AOKP on my Nexus 4.
I did a feature request for OmniROM but until it will be implented in the future I'm helping my self and wrote a little How-To on my Android 4.4 experiences.
Use at your own risk!
I'm not responsible for what you do on your phone.
If you don't even know how to flash a ZIP stop reading here this goes far more into detail.
Download for
omni-4.4.2-20140224-hammerhead-NIGHTLY
(it can work with newer or older versions too, It changes the framework-res.apk and SystemUI.apk, if they are changed on later nightlies I't will not work)
Screenshot with original 48 DPI NavBar
If you want to make a smaller NavBar by yourself I have made a little 20 Step How-To for you, based on this Guide by APatte111 and using this great Tool by Flextrick
you need AndroidMultitool, Java, Notepad++ and 7-Zip on your PC (this How-To is made for Windows).
(don't forget to add "C:\Program Files (x86)\Java\jre7\bin" (for your Java Runtime) to the PATH Var. in your Windows System Settings)
Here is the How-To:
Folder structure of the AndroidMultitool
GUI of the AndroidMultitool
1. Extract SystemUI.apk (system\priv-app) and framework-res.apk (system\framework) from ROM-ZIP
2. put both original files into a Recovery flashable ZIP, "framework-res.apk" under (system\framework) and "SystemUI.apk" under (system\priv-app) for restoring.
3. Copy both files to the "Files" folder of AndroidMultitool
4. Install Framework in AndroidMultitool
5. Decompile framework-res.apk
6. Go to "decompiled_apk" into "res\values" and open "dimens.xml" with Notepad++
7. Look for the "navigation_bar_height", "navigation_bar_height_landscape" (only matters for tablets) and "navigation_bar_width" entry
8. Change the DPI values to your preferences, for example 36.0dip/36.0dip/32.0dip and Save
9. Take a look into "decompiled_apk\framework-res\res" for folders like "values-mcc310-mnc-1" and delete the "-" in front of the last number it have to be "values-mcc310-mnc1" for compiling without errors.
10. Under compiling choose the folder of the decompiled framework-res "decompiled_apk\framework-res" and click compile
11. Open the new framework-res.apk under "Compiled_apk\framework-res" with 7-Zip and extract the "resources.arsc" file (thats the only one wich includes our changes)
12. Open the Original "framework-res.apk" with 7-Zip and put the resources.arsc into it, apply the overwriting and close 7-Zip
13. Decompile SystemUI.apk
14. Go to "decompiled_apk" into "SystemUI\res\layout" and open "navigation_bar.xml" with Notepad++
15. Search for "@drawable/ic_sysbar_back" and "@drawable/ic_sysbar_back_land" and delete the line " android:scaleType="center" " after it and save.
16. Under compiling choose the folder of the decompiled SystemUI "decompiled_apk\SystemUI" and click compile.
17. Open the original extracted "SystemUI.apk" with 7-Zip and extract the "META-INF" folder and "AndroidManifest.xml"
18. Open the new SystemUI.apk under "Compiled_apk\SystemUI" and insert the "META-INF" folder and "AndroidManifest.xml" file from the original "SystemUI" in it, apply the overwriting and close 7-Zip
19. Put both changed files into a Recovery flashable ZIP, "framework-res.apk" under (system\framework) and "SystemUI.apk" under (system\priv-app)
20. flash the ZIP in recovery and see your changes (if it failes, install your Restore-Zip from 2. and try the steps again)
Have fun with your new NavBar guys :highfive: :victory:
Changelog:
- version updated for OmniROM 4.4.2 20140224 (2014-02-24)
- version updated for OmniROM 4.4.2 20140206 (2014-02-07)
- version updated for OmniROM 4.4.2 20140203 (2014-02-03)
- version updated for OmniROM 4.4.2 20140128 (2014-01-28)
- version updated for OmniROM 4.4.2 20140123 (2014-01-23)
- version updated for OmniROM 4.4.2 20140117 (2014-01-17)
- version updated for OmniROM 4.4.2 20140115 (2014-01-15)
- version updated for OmniROM 4.4.2 20140105 (2014-01-05)
- version updated for OmniROM 4.4.2 20131227 (2013-12-27)
- version updated for OmniROM 4.4.2 20131217 (2013-12-17)
- version updated for OmniROM 4.4.2 20131212 (2013-12-12)
- version updated for OmniROM 4.4.1 20131208 (2013-12-09)
- 20131201 Version works flawless on Nightly 20131204, name changed (2013-12-04)
- version updated for OmniROM 20131201 (2013-12-02)
​

nvm, solved

auggie246 said:
nvm, solved
Click to expand...
Click to collapse
?!

tested on 20131204 and it works fine because there are no changes to SysUi and framework

next update will come after 4.4.1 OmniROM is available

Updated to 4.4.1 (Nightly 20131208)

which file should I modify to CM11? i can't find the string: "@drawable/ic_sysbar_back" and "@drawable/ic_sysbar_back_land" in SystemUI.apk... Can you help me?

[email protected] said:
which file should I modify to CM11? i can't find the string: "@drawable/ic_sysbar_back" and "@drawable/ic_sysbar_back_land" in SystemUI.apk... Can you help me?
Click to expand...
Click to collapse
are you looking in the navigation_bar.xml under the Decompiled "SystemUI\res\layout" folder?
€: OK, I've checked it and it is true there are not such values in CM11 SystemUI, so just try it with just the modified framwork-res.apk and see what happens, if the back button is not awkwardly big all is fine
Edit: - version updated for OmniROM 4.4.2 20131212 (2013-12-12)

No, I tried and does't work

[email protected] said:
No, I tried and does't work
Click to expand...
Click to collapse
Seems like CM is using some different code, and if you just change the values in the "dimens.xml" nothing happens?
€: - version updated for OmniROM 4.4.2 20131217 (2013-12-17)

I tried just changing the values ​​in "dimens.xml" and doesn't change

kabauterman said:
Seems like CM is using some different code, and if you just change the values in the "dimens.xml" nothing happens?
€: - version updated for OmniROM 4.4.2 20131217 (2013-12-17)
Click to expand...
Click to collapse
updated to 20131227

anyone tried if it works with 20140103?
€: Doesn't work, I tried it.
can you please build a new version of your mod for omnirom 2014-01-03?

illnez said:
anyone tried if it works with 20140103?
€: Doesn't work, I tried it.
can you please build a new version of your mod for omnirom 2014-01-03?
Click to expand...
Click to collapse
for 20140105
https://drive.google.com/file/d/0B4ESb_YBhAxIRzhqelFWYmxRNnM/edit?usp=sharing

Thanks kabauterman for this mod.
It works with latest build also omni-4.4.2-20140113-hammerhead-NIGHTLY but with some problems,please can you fix it?
Thanks in advance

micr0g said:
Thanks kabauterman for this mod.
It works with latest build also omni-4.4.2-20140113-hammerhead-NIGHTLY but with some problems,please can you fix it?
Thanks in advance
Click to expand...
Click to collapse
I have made a how-to for all of you wich use a version of Omni I havn't made yet
Now you can find 20130115 in OP :victory:
https://drive.google.com/file/d/0B4ESb_YBhAxIYWZWWkdiX3dYWXM/edit?usp=sharing

20140117 added to OP

20140123 online

You can find 20140128 in Post #1

Pretty cool change to OmniROM, changing the SystemUI if no more needed thanks to the new NavBar changes possible in OmniROM.
And it seem that the framework-res file is still the same then in the last releases. :good:
Post #1 updated

Theme Overlay Mods

Any settings made in the value files found within framework-res.apk can be overlaid with new values if an archive called framework-res is placed in /system/media/theme/default.
The framework-res archive is just a zip file without the .zip extention and must contain a file called theme_values.xml
The format of the contents of theme_values.xml is critical and all value entries placed in the <MIUI_Theme_Values> section:
Code:
<?xml version="1.0" encoding="utf-8"?>
<MIUI_Theme_Values>
inset lines here
inset lines here
inset lines here
</MIUI_Theme_Values>
If you already have a framework-res file in /system/media/theme/default, this means you already have some overlaid settings. Just merge your wanted settings into the same file being careful not to contradict existing lines.
I have attached the decompiled value files that contain the majority of what you may wish to play with. Copy and paste lines from these files into theme_values.xml with your edited values.
The value files come from 6.12.29 but are almost universal across all MIUI8 ROMs.
I have also included a file called framework_tweaks.xml which is my quick reference for useful tweaks - it is by no means exhaustive. Remove my comments from lines if you copy directly from this file.
The big advantage in modding this way is that it is very easy to re-edit the mod and easily reversed by simply deleting the file. This is much easier than decompiling and recompiling the parent file every time you want to change something. Furthermore, some files simply will not recompile successfully.
Other overlay files that can be created and placed in /system/media/theme/default
com.miui.home
values from MiuiHome.apk
Commonly used to change grid size for launcher
com.android.systemui
values from MiuiSystemUI.apk
Commonly used to change Status bar and toggles grid
framework-miui-res
values from framework-ext-res.apk
Commonly used to set toggles grid columns

Mods that are pure overlays will be attached here.
A comprehensive MIUI Home Launcher grid mod will be added next time I run a ROM with stock launcher
Contributions to the mods welcome

This is amazing!!!
After trying so hard to decompile/recompile/package/sign etc the framework-res.apk just to change two values in dimens.xml AND FAILLING
This is SOOOO much easier!
THANK YOU SO MUCH FOR THIS!

@ugene1980 Download TickleMyAndroid from its XDA Thread for decompile/recompile apks - it will do everything you need. Don't re-sign framework files or system apps.
Note that the full complement of framework files consist of the following:
framework-ext-res.apk
mediatek-res.apk
framework-res.apk
miui.apk - rename this to miui-res.apk to be recognized as a framework file
miuisystem.apk - rename this to miusystem-res.apk to be recognized as a framework file

jajk said:
@ugene1980 Download TickleMyAndroid from its XDA Thread for decompile/recompile apks - it will do everything you need. Don't re-sign framework files or system apps.
Note that the full complement of framework files consist of the following:
framework-ext-res.apk
mediatek-res.apk
framework-res.apk
miui.apk - rename this to miui-res.apk to be recognized as a framework file
miuisystem.apk - rename this to miusystem-res.apk to be recognized as a framework file
Click to expand...
Click to collapse
Nice, i'll give it a try, hope it works for miui 9.
I'm assuming mediatek-res.apk won't be needed if the device uses a SD835 instead of a mediatek processor?

@ugene1980 It works on MIUI9. You assume correctly

Can I use this mod to create AMOLED theme? And which app will be themed?
Coz MIUI theme manager failed to theme other than icon and wallpaper on MIUI 9 (Marshmallow).
Thanks.

Hi, thanks so much for your hints.
I've created two mods for MIUI9 on MiMix2 8.1.26 Beta rom, com.miui.home and framework-miui-res.
The mods flaulessly work, but only if the phone is rooted.
- Firstly rooting was needed because I had to put the files on /system and change permissions... but once checked I created a flashable zip that makes the work from TWRP.
- Once created the flashable .zip... rooting is not needed to modify system partition... but it doesn't work without root.
- Looking at same files but inside /data/system/theme (files created by themes app) I discovered some things to try:
-- Put 0755 permission with 9801 owner and group
-- Make framework-miui-res with the same structure... with filters.xml and framework-miui folder
- No way... I cannot make it work without root... and all the attempts worked very well if the phone is rooted.
Do you know how to make it work withour rooting?
Best regards.
---------- Post added at 04:06 PM ---------- Previous post was at 04:04 PM ----------
jajk said:
@ugene1980 Download TickleMyAndroid from its XDA Thread for decompile/recompile apks - it will do everything you need. Don't re-sign framework files or system apps.
Note that the full complement of framework files consist of the following:
framework-ext-res.apk
mediatek-res.apk
framework-res.apk
miui.apk - rename this to miui-res.apk to be recognized as a framework file
miuisystem.apk - rename this to miusystem-res.apk to be recognized as a framework file
Click to expand...
Click to collapse
Only to get your attention

@Huexxx It could be an sepolicy issue. What version Android and what version security update will determine how hard it is to get something foreign in System to execute.

jajk said:
@Huexxx It could be an sepolicy issue. What version Android and what version security update will determine how hard it is to get something foreign in System to execute.
Click to expand...
Click to collapse
Alright, I'll look deeper inside the logs.
Thanks for the point.
Enviado desde mi Mi MIX 2 mediante Tapatalk

Rom porting tutorial for beginers

Its all about MTK
This porting guide is succesfull for beginers for porting Roms using SMART PHOBES
#PC can also be used for this porpose
I'am currently using MTK 6582 .This method is 100 % working
____starting rom porting_____
1) create 2 folders called port and stock
2)extract port rom in port folder and system (folder of your stock) in stock
3) replace boot img for stock to port
[You can also use custum kernals]
4) Delete vendor folder and replace it
5) Delete this files
Systel/lib/hw
/modules
/etc/wifi
/firmware
Repace this with your stock
6) Replace This files from stock to port
System/bin/pq
/vold
/lib/lib.camalgo.so
/lib.camdrv.so
/libcameracustum.so
/libdpframework.so
/libsensorservice.so
/libvcodecdrv.so
/etc/apns.conf.xml
/vold.fstab
/vold.fstab.nand
If you was porting from diferent key phase phones please replace system/user/keylayouts/generic.kl
7) change your mountpoints with your stock
8) now using 7zip from playstore compress the system,boot.img,meta
9) flash the zip using cwm or twrp or etc
points to be noted
@ if recovery shows zip as bad compress it with solid explorer
@you have to use same version of androi
@select custum rom based on
Soc
Version
Cores of processor
RAM.
If anyone found more improved files.please suggest for knowledge.
Bugs can be solved by asking
THANKZ

file location - bootanimation.zip on android nougat?

Hi all
I have a Nexus7 which I've updated to Android Nougat.
I had a custom bootanimation prior, when on Lollipop. This was located in system/media. In Nougat, the media folder no longer exists.
Any ideas where the bootanimation.zip file is now located so I can install my custom animation?
Also, should I be able to use my bootanimation from lollipop on Nougat?
Thanks in Advance
Dave.

You can still create the /media/ folder and put the bootanimation in there, it should work as long as it is readable (permissions are usually rw-r-r) and the ROM accepts it. I think the resolution needs to be correct (1280 x 800) but if you were using the same zip on Lollipop then it should be fine on Nougat.

plusminus_ said:
You can still create the /media/ folder and put the bootanimation in there, it should work as long as it is readable (permissions are usually rw-r-r) and the ROM accepts it. I think the resolution needs to be correct (1280 x 800) but if you were using the same zip on Lollipop then it should be fine on Nougat.
Click to expand...
Click to collapse
Thanks - worked a treat