Related
I am trying to change the default launcher in CM7 to something such as Launcher7.
I tried to remove both the Launcher2 folder as well as ADWLauncher folder and add the Launcher7 source in /packages/apps but CM7 during build seems to add ADW back into the build so that when I flash it to my device, ADW is still default and installed.
Any advice? Is there some xml file or makefile which seems to set or be referencing ADW?
This is all for my Nexus One btw.
If you delete the launchers that are located in system/app om the ROM ZIP and put the apk of the launcher you want in system/app then it should work fine. I always do that for myself, replacing ADW for Launcher Pro,
Yeah I got it now after a fresh build. Apparently, I was messing with the package names and performing custom modifications and I didnt roll back the changes so when I tried building, it caused all kinds of problems. *facepalm*
Additionally, The changes I am making are all in source, not after ROM compilation so for me the changes were in /packages/apps not /system/app. I am trying not to edit the ROM after building as a good learning experience and its a cleaner solution too.
Smh, Thanks for the reply though. Appreciate it.
If you add in another launcher(also add it to PRODUCT_PACKAGES in device), you'll get a prompt on boot, and you may be able to edit default settings via overlay to use some other launcher as default
and what must be done inorder to add the launcher pro(any launcher) preferences to the settings, like we have the adw settings in the default android settings!!!! Please help...
To change it from source just change PRODUCT_PACKAGES (in common.mk) for AdwLauncher to your launcher name.
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/gingerbread/products/common.mk
To find your product name from your own launcher from source just look for your local package name in Android.mk.
example for Adw:
https://github.com/CyanogenMod/android_packages_apps_ADWLauncher/blob/gingerbread/Android.mk
To add a custom launcher in Settings.apk
https://github.com/CyanogenMod/andr...rbread/src/com/android/settings/Settings.java
line 76 in that file change "com.android.launcher.Launcher" to whatever main activity is there for your new launcher.
also in settings.xml
Code:
<!-- Launcher -->
<com.android.settings.IconPreferenceScreen
settings:icon="@drawable/ic_settings_launcher"
android:title="@string/launcher_settings_title"
android:key="launcher_settings">
<intent
android:action="android.intent.action.MAIN"
android:targetPackage="com.android.launcher"
android:targetClass="com.android.launcher.MyLauncherSettings" />
</com.android.settings.IconPreferenceScreen>
Change the "android:targetClass="com.android.launcher.MyLauncherSettings" to your settings class on the launcher. After you compile you should now have a customer launcher available in settings.
lithid-cm said:
To change it from source just change PRODUCT_PACKAGES (in common.mk) for AdwLauncher to your launcher name.
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/gingerbread/products/common.mk
To find your product name from your own launcher from source just look for your local package name in Android.mk.
example for Adw:
https://github.com/CyanogenMod/android_packages_apps_ADWLauncher/blob/gingerbread/Android.mk
To add a custom launcher in Settings.apk
https://github.com/CyanogenMod/andr...rbread/src/com/android/settings/Settings.java
line 76 in that file change "com.android.launcher.Launcher" to whatever main activity is there for your new launcher.
also in settings.xml
Code:
<!-- Launcher -->
<com.android.settings.IconPreferenceScreen
settings:icon="@drawable/ic_settings_launcher"
android:title="@string/launcher_settings_title"
android:key="launcher_settings">
<intent
android:action="android.intent.action.MAIN"
android:targetPackage="com.android.launcher"
android:targetClass="com.android.launcher.MyLauncherSettings" />
</com.android.settings.IconPreferenceScreen>
Change the "android:targetClass="com.android.launcher.MyLauncherSettings" to your settings class on the launcher. After you compile you should now have a customer launcher available in settings.
Click to expand...
Click to collapse
Can you tell me where is the PRODUCT_PACKAGE
thank you ～
Hi guys ..
I'm not a developer so is beyond my knowledge to create custom roms and stuff, but using the little programming skills I have I can manage to play around with the APKs
After trying various XS mods I saw there are small incompatibilities in the framework so there are small annoying graphical and/or animation glitches. Giving that I decided to start modding the stock rom by myself.
This will be a work in progress and I'll update it as I'll advance in my modding skills.
DISCLAIMER: I'm not responsible if you brick your phone by applying these mods. Apply at your own risk.
Do not forget: first thing after putting CWM on your phone, do a full backup of the original system so you can come back to that status in case of emergencies.
Please be aware that these files are not working on ALL odexed 6.1.A.2.45 roms. I have no idea why.
My phone has the following Customization Version: 1266-3278_R3G
Maybe the framework is somehow different form other versions. Please check your cust. ver. before aplying:
- stock dialer and type *#*#service#*#* (*#*#7378423#*#*), Service Info, software information
Current status of my phone:
- Rom updated OTA to 6.1.A.2.45
- Bootloader unlocked with the sony procedure (using fastboot and the key generated online)
- CWM kernel installed: http://forum.xda-developers.com/showthread.php?t=1834129
- Root pushed to the device: http://forum.xda-developers.com/showpost.php?p=30320507&postcount=11
Next I took out the SystemUI.apk and I deodexed it (only this one, so it can be easily modded) and start messing around with it.
12-09-06 - a - CWM flashable: statusbar - 1% battery increments and CM battery style applied, as well as 2 icons changed in the pull-down menu (settings and delete-all notifications buttons): SystemUI_CMbat_120906.zip (attached)
The quick controls are from widgetsoid. I plan to replicate the 14 toggles mod but I will need some time.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
12-09-06 - b - root stuff:: Delete at least part of the bloatware in the rom (I personally just moved the respective apks into a bkp folder):
http://img716.imageshack.us/img716/9964/screenshot2012090612342.png
12-09-09 - CWM flashable: statusbar - 1% battery MIUI style plus wifi, HD drawings (xhdpi): SystemUI_MIUIbat_wifi_120909.zip (attached)
12-09-11 - CWM flashable: statusbar - 1% battery MIUI style plus wifi, HD drawings (xhdpi), clock moved from status bar into the expanded notifications, next to the date, date rearranged, clock font increased.: SystemUI_MIUIbat_wifi_120909.zip (attached)[/b] - the toggles are from widgetsoid .. I will try to implement the quickpanel mod also.
Statusbar:
Expanded notifications:
12-09-16 - CWM flashable: statusbar - 1% battery MIUI style plus wifi, HD drawings (xhdpi), clock moved from status bar into the expanded notifications, next to the date, date rearranged, clock font increased, 8 toggles added to pulldown menu: SystemUI_toggles_120916.zip (attached)[/b]
Enjoy it!
I make no promises this will advance nor I will give OTA for anything ... it is just me trying to improve the experience I have with this phone.
Credits:
- XDA comunity for the info shared over the years.
- alteredlikeness - for the toggles sources and explanations.
You can use my files do to whatever you like! My real work was to understand some relations between the XMLs and SMALI files and also to create some pngs for the graphical aspect. I took the information for free so I'll return it in the same way.
Sept 9th - miui batt style and modded wifi statusbar icons.
Nice thank you so much :laugh: i will try it soon
Sept 11th - clock moved from statusbar into the pulldown notifications, next to the date. The clock font increased from 16dpi to 32dpi.
ro_explorer said:
Hi guys ..
I'm not a developer so is beyond my knowledge to create custom roms and stuff, but using the little programming skills I have I can manage to play around with the APKs
After trying various XS mods I saw there are small incompatibilities in the framework so there are small annoying graphical and/or animation glitches. Giving that I decided to start modding the stock rom by myself.
This will be a work in progress and I'll update it as I'll advance in my modding skills.
DISCLAIMER: I'm not responsible if you brick your phone by applying these mods. Apply at your own risk.
Do not forget: first thing after putting CWM on your phone, do a full backup of the original system so you can come back to that status in case of emergencies.
Current status of my phone:
- Rom updated OTA to 6.1.A.2.45
- Bootloader unlocked with the sony procedure (using fastboot and the key generated online)
- CWM kernel installed: http://forum.xda-developers.com/showthread.php?t=1834129
- Root pushed to the device: http://forum.xda-developers.com/showpost.php?p=30320507&postcount=11
Next I took out the SystemUI.apk and I deodexed it (only this one, so it can be easily modded) and start messing around with it.
12-09-06 - a - CWM flashable: statusbar - 1% battery increments and CM battery style applied, as well as 2 icons changed in the pull-down menu (settings and delete-all notifications buttons): SystemUI_CMbat_120906.zip (attached)
The quick controls are from widgetsoid. I plan to replicate the 14 toggles mod but I will need some time.
12-09-06 - b - root stuff:: Delete at least part of the bloatware in the rom (I personally just moved the respective apks into a bkp folder):
http://img716.imageshack.us/img716/9964/screenshot2012090612342.png
12-09-09 - CWM flashable: statusbar - 1% battery MIUI style plus wifi, HD drawings (xhdpi): SystemUI_MIUIbat_wifi_120909.zip (attached)
12-09-11 - CWM flashable: statusbar - 1% battery MIUI style plus wifi, HD drawings (xhdpi), clock moved from status bar into the expanded notifications, next to the date, date rearranged, clock font increased.: SystemUI_MIUIbat_wifi_120909.zip (attached)[/b] - the toggles are from widgetsoid .. I will try to implement the quickpanel mod also.
Statusbar:
Expanded notifications:
Enjoy it.
I make no promises this will advance nor I will give OTA for anything ... it is just me trying by need base to improve the experience I have with this phone.
Click to expand...
Click to collapse
How you removed clock from status bar?
October 16th 2012 - added 8 toggles to the drop-down notifications menu - OP updated.
ariciusonic said:
How you removed clock from status bar?
Click to expand...
Click to collapse
Use a deodexed SystemUI apk. Decompile it.
Edit: SystemUI/res/layout/status_bar.xml
Remove the line:
Code:
<com.android.systemui.statusbar.policy.Clock android:textAppearance="@style/TextAppearance.StatusBar.Clock"android:gravity="left|center" android:id="@id/clock" android:paddingLeft="6.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:singleLine="true" />
ro_explorer said:
October 16th 2012 - added 8 toggles to the drop-down notifications menu - OP updated.
Use a deodexed SystemUI apk. Decompile it.
Edit: SystemUI/res/layout/status_bar.xml
Remove the line:
Code:
<com.android.systemui.statusbar.policy.Clock android:textAppearance="@style/TextAppearance.StatusBar.Clock"android:gravity="left|center" android:id="@id/clock" android:paddingLeft="6.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:singleLine="true" />
Click to expand...
Click to collapse
Please help, I can't find the line.. Can you remove only clock from my systemUI.apk ? (it's from a xperia s)
:fingers-crossed:
ariciusonic said:
Please help, I can't find the line.. Can you remove only clock from my systemUI.apk ? (it's from a xperia s)
:fingers-crossed:
Click to expand...
Click to collapse
Check this one. If you see incompatibilities with your phone is because I used AcroS framework to decompile/compile your SystemUI.apk.
In that case please give me also your framework-res.apk and I'll redo the steps.
So now there is no clock at all, not in the statusbar and not in the drop-down notifications. I hope I understood correctly your request.
The zip is for CWM .
not working on my S, here is the framework..
https://www.box.com/s/0jpwg52tbw66uzvu3dxa
ariciusonic said:
not working on my S, here is the framework..
https://www.box.com/s/0jpwg52tbw66uzvu3dxa
Click to expand...
Click to collapse
Ok then .. this one is decompiled/compiled using your framework. It should work by default: XS_no_clock_2.zip
The above file is signed with a developer certificate.
If you want to keep the original signature, this is the same modded file as above, but with the original signature in it: XS_no_clock_2_original_signature.zip
Let me know if it worked.
ro_explorer said:
Hi guys ..
I'm not a developer so is beyond my knowledge to create custom roms and stuff, but using the little programming skills I have I can manage to play around with the APKs
After trying various XS mods I saw there are small incompatibilities in the framework so there are small annoying graphical and/or animation glitches. Giving that I decided to start modding the stock rom by myself.
This will be a work in progress and I'll update it as I'll advance in my modding skills.
DISCLAIMER: I'm not responsible if you brick your phone by applying these mods. Apply at your own risk.
Do not forget: first thing after putting CWM on your phone, do a full backup of the original system so you can come back to that status in case of emergencies.
Current status of my phone:
- Rom updated OTA to 6.1.A.2.45
- Bootloader unlocked with the sony procedure (using fastboot and the key generated online)
- CWM kernel installed: http://forum.xda-developers.com/showthread.php?t=1834129
- Root pushed to the device: http://forum.xda-developers.com/showpost.php?p=30320507&postcount=11
Next I took out the SystemUI.apk and I deodexed it (only this one, so it can be easily modded) and start messing around with it.
12-09-06 - a - CWM flashable: statusbar - 1% battery increments and CM battery style applied, as well as 2 icons changed in the pull-down menu (settings and delete-all notifications buttons): SystemUI_CMbat_120906.zip (attached)
The quick controls are from widgetsoid. I plan to replicate the 14 toggles mod but I will need some time.
12-09-06 - b - root stuff:: Delete at least part of the bloatware in the rom (I personally just moved the respective apks into a bkp folder):
http://img716.imageshack.us/img716/9964/screenshot2012090612342.png
12-09-09 - CWM flashable: statusbar - 1% battery MIUI style plus wifi, HD drawings (xhdpi): SystemUI_MIUIbat_wifi_120909.zip (attached)
12-09-11 - CWM flashable: statusbar - 1% battery MIUI style plus wifi, HD drawings (xhdpi), clock moved from status bar into the expanded notifications, next to the date, date rearranged, clock font increased.: SystemUI_MIUIbat_wifi_120909.zip (attached)[/b] - the toggles are from widgetsoid .. I will try to implement the quickpanel mod also.
Statusbar:
Expanded notifications:
12-09-16 - CWM flashable: statusbar - 1% battery MIUI style plus wifi, HD drawings (xhdpi), clock moved from status bar into the expanded notifications, next to the date, date rearranged, clock font increased, 8 toggles added to pulldown menu: SystemUI_toggles_120916.zip (attached)[/b]
Enjoy it!
I make no promises this will advance nor I will give OTA for anything ... it is just me trying to improve the experience I have with this phone.
Credits:
- XDA comunity for the info shared over the years.
- alteredlikeness - for the toggles sources and explanations.
You can use my files do to whatever you like! My real work was to understand some relations between the XMLs and SMALI files and also to create some pngs for the graphical aspect. I took the information for free so I'll return it in the same way.
Click to expand...
Click to collapse
I followed the instruction above but After flashed one of those file my phone became black screen and no Navibar!
Do you know what wrong with my phone?
My phone rooted and unlocked BL already.
You tried this on an Acro S with STOCK 6.1.A.2.45 ? It is very weird it did not worked.
Can you please give me your original SystemUI.apk and the odex file?
P.S.: I hope you had a backup to restore the phone ... otherwise, I can provide the original apk and odex.
ro_explorer said:
You tried this on an Acro S with STOCK 6.1.A.2.45 ? It is very weird it did not worked.
Can you please give me your original SystemUI.apk and the odex file?
P.S.: I hope you had a backup to restore the phone ... otherwise, I can provide the original apk and odex.
Click to expand...
Click to collapse
Yeah it's running stock A.2.45. No worry i did back up already.
Before i used to follow the other method by replace SystemUI.apk from another thread, but finally i got the same thing and even i replaced back the original SystemUI.apk still could not help until i restore phone system.
Ok here the original SystemUI.apk and odex file from my phone...
Thanks for your time
ro_explorer said:
October 16th 2012 - added 8 toggles to the drop-down notifications menu - OP updated.
Use a deodexed SystemUI apk. Decompile it.
Edit: SystemUI/res/layout/status_bar.xml
Remove the line:
Code:
<com.android.systemui.statusbar.policy.Clock android:textAppearance="@style/TextAppearance.StatusBar.Clock"android:gravity="left|center" android:id="@id/clock" android:paddingLeft="6.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:singleLine="true" />
Click to expand...
Click to collapse
Hi! Wich lines edit for the clock? I mean, centered clock
Sent from my LT26i using xda premium
alvizu said:
Hi! Wich lines edit for the clock? I mean, centered clock
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
The same line you delete to remove the clock only that you have to play with the position of the line containing the clock definition and also woth the definition of the clock itself.
So, the line must be moved in the first LinearLayout field and the clock must have android:gravity="center"
That's all.
I'm not pasting here my own xml lines because apparently these might differ from one system to another.
higherman said:
Yeah it's running stock A.2.45. No worry i did back up already.
Before i used to follow the other method by replace SystemUI.apk from another thread, but finally i got the same thing and even i replaced back the original SystemUI.apk still could not help until i restore phone system.
Ok here the original SystemUI.apk and odex file from my phone...
Thanks for your time
Click to expand...
Click to collapse
So .. I took your files and compared the checksums with my files ... guess what? your files are identical to mine.
This lead only to one conclusion .. something is wrong either with the signature of my compiled file (but from my knowledge the signature of the system files do not count) or you have something weird over there.
The CWM package is supposed to automatically delete the original SystemUI.apk and SystemUI.odex files and then put instead the modded SystemUI.apk and set the rigt permissions.
Just to take all the precautions, here is the newest modded file with the original Sony signature.
If the above procedure (done manually) is still not giving results I frankly can not help you because I simply have no idea what's wrong.
ro_explorer said:
The same line you delete to remove the clock only that you have to play with the position of the line containing the clock definition and also woth the definition of the clock itself.
So, the line must be moved in the first LinearLayout field and the clock must have android:gravity="center"
That's all.
I'm not pasting here my own xml lines because apparently these might differ from one system to another.
Click to expand...
Click to collapse
I edit this, but no change, can you help me?
Sent from my LT26i using xda premium
Is this for Acro S ? In order to correctly decompile SystemUI.apk I need also the compatible framework-res.apk.
ro_explorer said:
Is this for Acro S ? In order to correctly decompile SystemUI.apk I need also the compatible framework-res.apk.
Click to expand...
Click to collapse
Xperia S
http://www.mediafire.com/?d207097bncq0ex0
If you have everything ready to edit and recompile, here is the line.
I was wrong before ... and I apologise for that.
You need to create an additional LinearLayout field especially for the clock:
So, the header of your status_bar.xml should look like:
Code:
<?xml version="1.0" encoding="utf-8"?>
<com.android.systemui.statusbar.phone.PhoneStatusBarView android:orientation="vertical" android:background="@drawable/status_bar_expand_default" android:focusable="true" android:descendantFocusability="afterDescendants"
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:systemui="http://schemas.android.com/apk/res/com.android.systemui">
<LinearLayout android:orientation="horizontal" android:layout_width="fill_parent" android:layout_height="fill_parent">
<com.android.systemui.statusbar.policy.Clock android:textAppearance="@style/TextAppearance.StatusBar.Clock" android:gravity="center" android:id="@id/clock" android:layout_width="fill_parent" android:layout_height="fill_parent" android:singleLine="true" />
</LinearLayout>
<LinearLayout android:orientation="horizontal" android:id="@id/icons" android:paddingLeft="6.0dip" android:paddingRight="6.0dip" android:layout_width="fill_parent" android:layout_height="fill_parent">
[...]
Explanation (I think we all are learning better by these trial&errors iterations ):
The XML file is basically presenting how the respective object is being built.
In this case, we are talking about the status bar.
Well, the LinearLayout fields are basically overlapped in the status bar and the objects inside each linear field has local orientation parameters.
By adding a new linear field on top of the others and by placing a clock entity centered, you will get what you want
Be warned: the clock will be overlapped with the notification icons which will be drawn from left to right ... so if many many notification icons will be drawn, these will go over the clock
Schools
2012-12-19 - Post #5 Inspecting the content of an APK
2012-12-19 - Post #6 Understanding .9.PNG or 9-patch PNG
2012-12-19 - Post #7 Let's make our own .9.PNG
2012-12-19 - Post #8 Let's edit an APK
2012-01-13 - Post #12 Keep transparency of PNGs
2013-01-24 - Post #13 Easy but advanced apk-modding
Basic windows tools
The basic windows tools to look inside apk's and learn about it's structures, content and XML's are in this zip.
Mediafire: X10MP_essentials_v3.zip
In the zip you will find:
APK Easy Manager v1.0
APK Edit v0.2
APK Tool 1.5.2 SEMC
Gordons Gate USB driver
Screen Stream
SignApk
Notice: You will also need Java SE Runtime Environment. Download from here, and install first. (The one called JRE)
Gordons Gate USB driver
If you already has rooted your X10M/P you already got the USB driver, and you do not need to install the USB driver. The driver is also installed with SONY PC Companion.
APK Tool 1.5.2 SEMC
Next you need to install the framework files. In the zip is included CM7 and SEMC framework. (If you want to work on CM9 or CM10 you can get the framework-files in any of those ROMs)
Install both framework files in the folder. Open CMD and change dir to the folder with apktool and the framework files.
Then type:
apktool if framework-res.apk
apktool if SemcGenericUxpRes.apk
APK Easy Manager v1.0
This tool will easily decompile most APK's, for easy access to resources and files, incl. XMLs
APK Edit v0.2
This tool will let you extract or inject files and edit existing XMLs.
Notice: Use the Apply button after you do a change to return to root folder. When injecting files, use copy and paste. If you just drag and drop the file wil be moved. Check AndroidManifest.xml after every APPLY, some strings might get changed or corrupted (typically there will be added a / in front of @, just remove the / and save and apply again).
(this is my generel APK-editing tool)
I use Notepad++ for editing XML/SMALI
Screen Stream
Just a very nice tool to make screen shots or video.
SignApk
Just in case you need to sign an APK.
What to do next
Well, just experiment and look inside APKs and get familiar with how they work and where different resources are placed and used by the APK. Slowly you will get more and more curious, read more and more about what ever gets your attention.
Schools and References - thread posts
Links to best posts in this thread
Post #5 Inspecting the content of an APK
Post #6 Understanding .9.PNG or 9-patch PNG
Post #7 Let's make our own .9.PNG
Post #8 Let's edit an APK
Post #12 Keep transparency of PNGs
Post #13 Easy but advanced apk-modding
References - outside forum
Best links to outside XDA forum
....
Reserved for a very usefull content
:cyclops:
Inspecting the content of an APK
The task of inspecting the content of an APK is fairly simple.
If you are only interesting in the graphics (PNGs) you can just rename the extension of an APK to ZIP. Now just extract the ZIP file and you got all the files from the APK. You will not be able to read the XML or SMALI files.
If you want access to everything use APK Easy Manager v1.0 from the essentials pack in post #1 above.
Just drag and drop the APK file into the APK Easy Manager v1.0, select Gingerbread in the dropdown and click Start Decompiling.
The decompiled APK will now be available in the projects folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Understanding .9.PNG or 9-patch PNG
Many attempts has been made to make this easy to understand and edit. Most of them ends up with strange sugestions and very complicated procedures.
Well, it's far from that complicated.
The goal of a .9.PNG is to make a graphical object, that's scaleable around a content, like a button with a text in it.
One good example is the buttons to cancel a call.
This button is made up of 5 different .9.PNG one for each state of the button, and are found in the Phone.apk (Phone.apk/res/drawable-mdpi)
btn_in_call_main_disable.9.png
btn_in_call_main_disable_focused.9.png
btn_in_call_main_normal.9.png
btn_in_call_main_pressed.9.png
btn_in_call_main_selected.9.png
They look like this (200% size shown in Pixlr.com/editor)
They all got the size 21x91. And obviously this is not the size of the buttons The actual button size is 64x64.
All around the PNGs is a 1 px border, with a simple information to the handling of the PNG object. The border must be only 100% transparent or 100% black. It's the black pixels that holds the information.
Top and left border tells what part of the PNG that is scalable/stretchable.
Right and buttom border tells what part of the PNG that can hold content, like text or other PNGs (above the buttons contains both text and graphics).
Very simple run down here: http://radleymarx.com/blog/simple-guide-to-9-patch/
Let's put that into words.
The "normal" butten state fades slightly from very dark at the buttom to less dark at the top and has round corners.
Top/left scalable/stretchable
For this button to look good, the corners sould not be stretched and the vertical transition should streach along most of the button. Left black border-line should be as long as possible for this.
For both horizontal and vertical, the corners should stay clear of being stretched.
Right/buttom content
Most of the button should hold content, so lines are here as long as possible but but still with a nice margin to the edges.
Let's make our own .9.PNG
First thing to be aware of is, that resizing a .9.PNG from another APK most likely will make the .9.PNG unusable because the imageeditor might change the total black of the border pixels and the total transparent might get some colour from pixels next to them.
Lets say that we want to make a Hobbit theme, and want the buttons above to look like something Hobbit, like a document.
So we want to change the document into the button, it would be something like this:
First I would just draw the black lines on the full image later we can do the cutting.
As you can see, I don't want stretch on the part where the corner of the document is missing (black line to the left).
Injecting this new button as it is now (no cutting at all) is fine. It does NOT have to be the size of the system-defaults. All 5 buttons just have to be same size.
This is how it looks with the same PNG for all 5 buttons. Not bad considering it took med 5 min to make
Note: The theme I used to test the Hobbit buttons is the Xperia S CM7 Theme. The caller number being close to the buttons is something that is on my list of fixing, and has nothing to do with the buttons.
Come oin newbie themers... let's build our self an XPERIA X10 Hobbit
Let's edit an APK
So I got this very simple app, that just open up a link. APK -> http://db.tt/WzA4QJhp
The APK has a Windows Live icon and just opens up http://mobile.live.com
We want to change the link to http://forum.xda-developers.com/forumdisplay.php?f=723 (this is the forum base for Sony Ericsson XPERIA X10 Mini), and give it a new nice icon.
Start APK Edit v0.2 (se post #1 for download etc) and open the APK-file (always edit in a copy).
App title and icon are changed from the front of the tool. Just write a new name and click the icon to change it. I made this cool icon.
Next we move to the content tab. This windows functions just like any other window, alowing moving og opening files directly.
The first file you see is AndroidManifest.xml
In this apk, it's not that interesting.....
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest android:versionCode="1" android:versionName="1.0" package="[COLOR="Red"]com.live.mobile[/COLOR]"
xmlns:android="http://schemas.android.com/apk/res/android">
<application android:label="@string/app_name" android:icon="@drawable/icon">
<activity android:label="@string/app_name" android:name=".WindowsLiveMobile">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
<uses-sdk android:minSdkVersion="3" />
</manifest>
..... except for the red text. This is the apk signature, any other apk with the same signature will overwrite each other when installed. So if we want to make another link-APK and have both installed, this needs to be changed - AND ANY REFERENCE TO THIS, INCL PATH REFERENCES com/live/mobile must be changed too INCL the APK folders inside the SMALI folder. We will do this another day :laugh:
For now we will just find the part of the APK where the link is.
Deep inside smali/com/live/mobile are a bunch of smali-files. Our link-string is inside WindowsLiveMobile.smali.
Just open with text-editor (not Wordpad) find the link-string and edit the URL from "http://mobile.live.com" to "http://forum.xda-developers.com/forumdisplay.php?f=723"
Save the file and clik APPLY.
Copy to SD card and install.
This is the result APK http://www.mediafire.com/?v37jtayf7jsow82
Enjoy :good:
A very handy guide to .9.PNG's. Thanks!
Sent from my SK17i using xda premium
Great job!
thanks Emperor.dk for the information
Keep transparency of PNGs
When editing stock apps, everyone at one point will get problems with keeping the transparency of an stock PNG when opening it in an image editor programe on the PC.
Example: Here I have open plate.png from onoffwidgets.apk resources:
It should have been transparent, and editing from here won't do any good.
Solve this by first open it in Pixlr.com/editor and just save it again replacing the original on the PC.
When you open it again in your image editor in the PC, and the transparency works.
Now, enjoy modding and theming
Easy but advanced apk-modding
Cyanogen has made this cool app called CMWallpapers.apk.
You will find the app in a lot of custom ROMs all over XDA, some modded and some not.
In this school we will modify the package id to avoid colission with any preinstalled version and change the content of the app.
See previous schools for how to open an APK and edit content.
Today we are building an Xperia S wallpaper app-pack.
Changing icon and app name
Opening the apk in APK Edit first shows the app icons and name.
To change the icons simply click them and select the one you want from the popup filemanager. I found the original stock icon from WallpaperPicker.apk in the Xperia S stock ROM. It's fine to use the 48x48 for both LDPI and MDPI.
The app and label name is changed to "Xperia S wallpapers".
Notice: This is only the english name. In order to change the name for other languages, we need to change a lot of XML-files. This is done easily using the "replace in all open documents" function in Notepad++.
Navigate to res/ and simply drag and drop all the "value-??" folders into Notepad++, press CTRL+H and replace "CyanogenMod" with "Xperia S" in all open documents (There is one big button to do it in all with one click), and then press CTRL+SHIFT+S to save all documents.
After that click the Apply button in APK Edit.
Changing the package-id
The package id is defined in AndroidManifest.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest android:versionCode="10" android:versionName="2.3.7" [COLOR="Red"]package="com.cyanogenmod.CMWallpapers"[/COLOR]
xmlns:android="http://schemas.android.com/apk/res/android">
<uses-sdk android:minSdkVersion="10" android:targetSdkVersion="10" />
<uses-permission android:name="android.permission.SET_WALLPAPER" />
<application android:label="@string/app_name" android:icon="@drawable/cyanogenmod_icon">
<activity android:label="@string/app_label" android:icon="@drawable/cyanogenmod_icon" android:name="wallpaper" android:screenOrientation="nosensor" android:finishOnCloseSystemDialogs="true">
<intent-filter>
<action android:name="android.intent.action.SET_WALLPAPER" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
<activity android:label="@string/no_wallpaper" android:name="NoWallpaper">
<intent-filter>
<action android:name="android.intent.action.SET_WALLPAPER" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
</application>
</manifest>
Here we can change "com.cyanogenmod.CMWallpapers" to "com.xperias.wallpapers"
IMPORTANT: When you change the package-id you will have to change alle references in all SMALI-files, and all folder-paths inside the apk, or the app will not work.
Inside the APK exists a folder-path to the SMALI-files:
smali\com\cyanogenmod\CMWallpapers
We must rename the foldes "cyanogenmod" and "CMWallpapers" to match our package-id.
In APK Edit we just navigate to "smali\com\" and rename the folder "cyanogenmod" to "xperias", and then navigate into "xperias" and rename "CMWallpapers" to "wallpapers".
The new folder-path to the SMALI-files will now be:
smali\com\xperias\wallpapers
Next we will open all SMALI-files and change any references to match the new package-id. There are a lot, so again you might use the replace in all open documents function in Notepad++
Save all documents and click the Apply button in APK Edit.
Making wallpaper files
One wallpaperfile consists of two files, the wallpaper itself, and a thumbnail, in the format:
wallpaper.jpg
wallpaper_small.jpg
For this app to work properly, the LDPI resolution should be 427x320, and the thumbnail should be 107x80.
The MDPI resolution should be 640x480, and the thumbnail should be 107x80.
I have prepared all the wallpaperfiles from the stock Xperia S ROM, i had to resize and crop some parts off.
The wallpapers in the stock Xperia S ROM is found in "system\etc\customization\content\com\sonyericsson\wallpaperpicker\wallpapers"
The wallpaper-files has to be placed in "res\drawable-ldpi" and "res\drawable-mdpi"
Place wallpaperfiles inside the APK
First we open the "res\drawable-ldpi" folder, and delete the existing wallpaper files.
Notice: Don't delete the icon-file!
Then we copy the resized/cropped Xperia S wallpaperfiles into the folder and click Apply.
Next we do the same for "res\drawable-mdpi" folder.
Edit arrays.xml
Inside "res\values" folder we got an XML-file with references to all the wallpaper-files. This has to be edited to match our new wallpaper-files.
At the upper part of the XML we got file-reference, this must match the filename without the ".jpg", and at the lower part of the list we got wallpaper discription/name.
Be very carefull when editing XMLs in Windows. You will very easily break the text encode if you copy from 3rd party text-editor into Notepad++. It's better just to type in everything manualy.
Result
After install of the modded app, we get an Xperia S wallpaper choise when pressing the Menu-button and tapping wallpaper.
We also get an option to select no wallpaper. If we want to get rid of this, we need to edit AndroidManifest.xml and remove the red part:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest android:versionCode="10" android:versionName="2.3.7" package="com.xperias.wallpapers"
xmlns:android="http://schemas.android.com/apk/res/android">
<uses-sdk android:minSdkVersion="10" android:targetSdkVersion="10" />
<uses-permission android:name="android.permission.SET_WALLPAPER" />
<application android:label="@string/app_name" android:icon="@drawable/cyanogenmod_icon">
<activity android:label="@string/app_label" android:icon="@drawable/cyanogenmod_icon" android:name="wallpaper" android:screenOrientation="nosensor" android:finishOnCloseSystemDialogs="true">
<intent-filter>
<action android:name="android.intent.action.SET_WALLPAPER" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
[COLOR="red"] <activity android:label="@string/no_wallpaper" android:name="NoWallpaper">
<intent-filter>
<action android:name="android.intent.action.SET_WALLPAPER" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
[/COLOR] </application>
</manifest>
And now, let me see some weekend mod-projects from all you newbies. I can't wait to se all your cool idears for app modding. I would realy like to see the Sony Ericsson Notes app with Google Tasks sync
Download the finished app here: http://www.mediafire.com/?i5tw3zpbcl86byg
New version here, cleaned up all MDPI, only 537 KB: http://www.mediafire.com/download.php?srhfp05qma86ctb
Awesome guide! I really want to learn something about the android world. Do you have some tools like these, but for linux?
mortadelax said:
Awesome guide! I really want to learn something about the android world. Do you have some tools like these, but for linux?
Click to expand...
Click to collapse
I'm very sure it's even more easy to do Android coding on a Linux system.... but i don't know how to install it, or use it, or play it.
awesome guide! Thanks a lot
Great! Thank a lot
Emperor.dk said:
I'm very sure it's even more easy to do Android coding on a Linux system.... but i don't know how to install it, or use it, or play it.
Click to expand...
Click to collapse
LOOOOL
Did you notice the line @ 4:55; "my phone doesn't take a week to boot"
That song is from a time way before smartphones .. :laugh:
This Guide will help you to add any application/options to Settings.apk. Well earlier My friend @sandy7 published a guide on how to add various options in Settings. So this extended guide will provide you the necessary knowledge on how to get resources about any app which needed to be added in Settings to include it as an option.
Requirements:
Any Tool that can Decompile & Recompile with it's requirements
Notepad++
1. How to add options/apps in main/general settings :
To add an app in Settings we need some resources of the app. This resources can be found by decompiling the app which we want to add & look for those in AndroidManifest.xml
Now, to add an app we need this resources to be added:
*android:targetPackage - the unique & original package name of the app
*android:action - the On click event of an app & it finds the activity of the app
*android:targetClass - the class which is called on calling Onclick action which opens the app when it is clicked
*android:title - the entry of the app in header & also in strings.xml
*android:icon - the icon which will be displayed for the app entry
Notes: android:targetClass, android:targetPackage & android:action can be found in AndroidManifest of the app. For some apps android:targetClass is not given directly. So it should be searched to find. I will tell you how to do that. android:title & android:icon can be written as per user.
As I explained a bit about the resources I will now move onto the main guide. I will take an app from playstore named "Rom Toolbox" as example & describe the ongoing process
i. 1st we need to decompile the Rom toolbox app & find the resources in AndroidManifest.xml
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as we can see from the picture that I marked the android:targetPackage & android:targetClass. The target package is easy to find. Sometimes target class is also given directly. If it's not given directly like this app we will find it by searching for it in the lines which starts with <activity. Now if there's more than one activity search for the activity that matches with the target package to some extent. & one more thing I should make you clear about. In some apps you will find android:targetClass will just be a one word phrase. Like if we take Serajr's SystemUI Preference as example you will see that android:targetClass is ".SystemUIPreferencesActivity". In those cases we need to add the whole android:targetPackage before targetClass. For Serajr's SystemUI preference the android:targetPackage="com.serajr.systemui.preferences". So the android:targetClass="com.serajr.systemui.preferences.SystemUIPreferencesActivity".
So here for Rom Toolbox app we find
Code:
android:targetPackage="com.jrummy.liberty.toolbox"
android:targetClass="com.jrummy.apps.rom.toolbox.RomToolboxActivity"
android:action="android.intent.action.MAIN"
android:action doesn't always needed to be found, you can always use "android.intent.action.MAIN" as the on click event
ii. Now decompile Settings.xml & go to res\xml & open settings_header.xml with notepad++. Now chose a place where you want to make the entry. If we want to add the app under advanced settings then we need to create a header 1st. We also need to create an android:title & android:icon entry for the app. So this will be the entry in settings_header
Code:
</header>
<header android:title="@string/header_category_advanced" />
<header android:icon="@drawable/ic_settings_rom" android:title="@string/rom_toolbox">
<intent android:targetPackage="com.jrummy.liberty.toolbox" android:action="android.intent.action.MAIN" android:targetClass="com.jrummy.apps.rom.toolbox.RomToolboxActivity" />
The 1st header is for the advanced settings header. We need to make an entry of the same name in strings.xml.
The 2nd header is for the app & icon. We need to write the exact entry as title in strings.xml like I wrote "rom_toolbox". You can write anything as title just make sure it matches the app itself so that you can find it easily. So the settings_header will look like this
Now save it
iii. Now go to res\values & open strings.xml. We need to create two strings here. One for the advanced settings & another for the app. We already chose the string name for header as "header_category_advanced" & "rom_toolbox" for the Rom Toolbox app. So the entries in strings.xml will be
Code:
<string name="header_category_advanced">ADVANCED SETTINGS</string>
<string name="rom_toolbox">ROM Toolbox</string>
You can write anything where I wrote "ADVANCED SETTINGS" & "ROM Toolbox" It depends on you what you would like to see in settings as header.
So the strings.xml should be like this
Now save it.
iv. Now we need to place a png for the app in drawable folder with the name "ic_settings_rom" as it is given in the header of android:icon. Depending on your settings you either should have drawable hdpi or drawable mdpi folder. On my case I have drawable hdpi folder. 1st we need to look at the resolutions of the pngs which starts with ic_settings name. Well generally for drawable hdpi it is 48x48 & for drawable mdpi it is 32x32. So we need to resize the png in any of this resolutions depending on our drawable folder. You can take the png from the original app & resize it. In my case I resized it in 48x48 & placed it in drawable-hdpi folder.
v. Now you are ready to recompile again. Then try your newly modified settings. I will post a screenshot of mine
2. How to add options/apps in sub settings for example in display settings :
Here I will take On-screen-buttons app for an example in the ongoing process. We will add it in display_settings. Now, we need an extra resource called android:key when we want to add any app in sub settings. android:key is the keystore when the app is extracted using any app tool when created by the developer. As we cannot find the original android:key of the app, we will enter a value as android:key & give it's reference in the ids.xml
i. 1st decompile the On screen button app & search for resources in AndroidManifest.xml.
So we find android:targetPackage="cn.kyle.gn.NavBar" & as only one line here starts with <activity it is really easy to find android:targetClass="cn.kyle.gn.NavBar.GnNavBarActivity". android:action="com.android.intent.MAIN" even if it is not written in the manifest.
Now we need to make android:title which can be anything,we just need to refer it into strings.xml, android:key can be anything, we need to refer it in ids.xml & another entry is optional here which is android:summary which is the sub-header of the app. I give you my example what I have written as values of those resources
Code:
android:title="navienable_title"
android:key="on_screen"
android:summary="on_screen_summary"
Now as we fixed every resource & their values we will put the entry in res\xml in display_settings.xml. The entry will look like this
Code:
<PreferenceScreen android:title="@string/navienable_title" android:key="on_screen" android:summary="@string/on_screen_summary">
<intent android:targetPackage="cn.kyle.gn.NavBar" android:action="android.intent.action.MAIN" android:targetClass="cn.kyle.gn.NavBar.GnNavBarActivity" />
</PreferenceScreen>
The display_settings will look like this
Now save it
ii. Now go to res/values & open strings.xml. We need to make two entries here. One for the android:title="@string/navienable_title" & another for the android:summary="@string/on_screen_summary". Now we make the entries
Code:
<string name="navienable_title">On-Screen-Buttons</string>
<string name="on_screen_summary">Enable/Disable On-Screen-Buttons</string>
as I said before you can write anything inside >......</string> it depends on you what text you would like to be seen
The screenshot from strings.xml
Now save it.
iii. Now go to res\values\ids.xml & open it. We need to make an entry for the entry we made in display_settings as android:key. So the entry will be with the same value
Code:
<item type="id" name="on_screen">false</item>
So the ids.xml should be like this
Save it & recompile your edited Settings.apk. Here is a screenshot of the Settings I edited
2. How to add headers in Settings/about to display Developer Name & Rom Name :
i. Decompile Settings.apk & go to res\xml & open device_info_settings.xml. Now choose a place where you want to show your Rom Name & Developer name. The entries you need here are similar with the one's that already exist in the xml. So you can copy one line of entry & press enter then paste it & you can edit it to make the new entries. We need android:title & android:summary which will be shown in strings.xml. We need android:key which you can keep same as android:title to eliminate difficulties, but we don't need an entry in ids.xml this time as it is not an app for which we are making the entry for. Last of all we need a style entry which will be the same as others. So I will write my Rom name & developer name under Kernel_version entry here. The entries will be
Code:
<Preference android:title="@string/rom_header" android:key="rom_header" android:summary="@string/rom_name" style="?android:preferenceInformationStyle" />
<Preference android:title="@string/author_header" android:key="author_header" android:summary="@string/author_name" style="?android:preferenceInformationStyle" />
The device_info_settings.xml will look like this
Now save it.
ii. Now go to res\values\strings.xml to make the entries here. We need two entries for the Rom Name, one is for "@string/rom_header" & another for "@string/rom_name". Same we need for Devloper name, one entry for "@string/author_header" & another for "@string/author_name". So the entries will be
Code:
<string name="rom_header">Rom Name</string>
<string name="rom_name">X Rom</string>
<string name="author_header">Developed By</string>
<string name="author_name">Saqib Nazm</string>
I give my Rom name as "X Rom" for example. You can type anything as you like on rom_name & author_name
The strings.xml should look like this
Now save it & recompile. Enjoy your freshly made new Settings.apk. Here is a screenshot about how it looks
.........................................................................................................................................
At the end I want to say, I will try to explain it more by adding more examples so that you can add anything. Kindly give me credits for my work If it helps you in anyway possible. Like I am gonna give credits to those respective people for whom I could share this guide to you.
Credits:
Neroyoung - for always helping me & clearing my ideas
jerrytan93 - for helping me alot whenever I need him
gagan.u20 - for always saving me if I get stuck somewhere
singh_dd93 - for giving me a clear idea on some resources
sandy7 - who doesn't know his thread from where everyone can learn
Nice one.. now everyone can start to develop their own ROM..
jerrytan93 said:
Nice one.. now everyone can start to develop their own ROM..
Click to expand...
Click to collapse
hehe thanks man & your help is highly appreciated :good:
@saqib nazm
i think u should add this also
after adding an app to settings u dont want that app to show up on launcher ..
so u can hide it by editing Androidmanifest.xml
by delete the red marked line
Code:
<activity android:label="@string/app_name" android:name=".GalleryActivity" android:taskAffinity="android.task.pictures" android:configChanges="keyboardHidden|orientation|screenSize">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
[B][COLOR="red"]<category android:name="android.intent.category.LAUNCHER" />[/COLOR][/B]
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
sandy7 said:
@saqib nazm
i think u should add this also
after adding an app to settings u dont want that app to show up on launcher ..
so u can hide it by editing Androidmanifest.xml
by delete the red marked line
Code:
<activity android:label="@string/app_name" android:name=".GalleryActivity" android:taskAffinity="android.task.pictures" android:configChanges="keyboardHidden|orientation|screenSize">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
[B][COLOR="red"]<category android:name="android.intent.category.LAUNCHER" />[/COLOR][/B]
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Click to expand...
Click to collapse
yeah sure I wanted to,but then thought it doesn't work for every app.like it gives fc on 1st case then if applied later it works Now as you wrote it in the 1st page I think I don't need to add it OP anymore if you change the title of your post :angel:
saqib nazm said:
yeah sure I wanted to,but then thought it doesn't work for every app.like it gives fc on 1st case then if applied later it works Now as you wrote it in the 1st page I think I don't need to add it OP anymore if you change the title of your post :angel:
Click to expand...
Click to collapse
It works for every app.
Just set it for the main activity from
Code:
<activity android:label="@string/app_name" android:name=".GalleryActivity" android:taskAffinity="android.task.pictures" android:configChanges="keyboardHidden|orientation|screenSize">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
to
Code:
<activity android:label="@string/app_name" android:name=".GalleryActivity" android:taskAffinity="android.task.pictures" android:configChanges="keyboardHidden|orientation|screenSize">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
cheers,
jan+
jader13254 said:
It works for every app.
Just set it for the main activity from
cheers,
jan+
Click to expand...
Click to collapse
thanks jader :good: I didn't know that. So it's good to know that now from you
awesomeness.. people like you make people like us who are learning easy to understand things.. thanks bro..
Sent from my HTC Explorer A310e using xda app-developers app
Nice tutor m8 ! Thanx 4 ur aW£s0m€ work !!
Sent from my E15i using xda premium
how would i?
saqib nazm
Click to expand...
Click to collapse
how would i Add a another menu Below the Development menu , because i do want to Add a Credits menu
ps is it posible to add a rom control menu with the sony white balance app, navigation bar, font changer or/and a dpi changer
Envious_Data said:
how would i Add a another menu Below the Development menu , because i do want to Add a Credits menu
ps is it posible to add a rom control menu with the sony white balance app, navigation bar, font changer or/and a dpi changer
Click to expand...
Click to collapse
so you want to add a credit option in settings?& when you click on it what do you want it to do? sony white balance is not yet ported perfectly to our devices & also there is no font changer in our phone (or is it an app?) how to add dpi changer is given in other thread by sandy7.
I am trying to remove some items from settings on my Zelly Cream ROM. Now, I have deleted relevant info from settings_headers.xml and strings.xml, but, when I try to compile with apktool, it gives me an error (see attachment)
I wonder if you could help me. Thank you for your guide.
here
saqib nazm said:
so you want to add a credit option in settings?& when you click on it what do you want it to do? sony white balance is not yet ported perfectly to our devices & also there is no font changer in our phone (or is it an app?) how to add dpi changer is given in other thread by sandy7.
Click to expand...
Click to collapse
Credits > open up just like About Device menu
ROM controll > list of Things , dpi changer etc
other info > i dont mind apps that dont show up, so a dpi chaneger app that opens when clicked for example
important info > i admit i am still learning this
masteriori said:
I am trying to remove some items from settings on my Zelly Cream ROM. Now, I have deleted relevant info from settings_headers.xml and strings.xml, but, when I try to compile with apktool, it gives me an error (see attachment)
I wonder if you could help me. Thank you for your guide.
Click to expand...
Click to collapse
I think you need to update your aapt
Envious_Data said:
Credits > open up just like About Device menu
ROM controll > list of Things , dpi changer etc
other info > i dont mind apps that dont show up, so a dpi chaneger app that opens when clicked for example
important info > i admit i am still learning this
Click to expand...
Click to collapse
if you want to open a credits menu when clicking on it you need to write a whole new .xml file in the xml folder. & about the other rom control thing,you can just give your header & add the apps you want to add. Like the way is shown in the tutorial. Again if you want to open a sub menu when clicking on Rom control that will contain list of things like dpi changer you need to write a new xml file. So if you are willing to take so much let me know I will try to guide you though I haven't yet tried myself that way
saqib nazm said:
I think you need to update your aapt
Click to expand...
Click to collapse
What is an aapt? I don't have the SDK installed,using just apktool which I have been able to decompile APKs with. Also, I have been able to compile APKs using the same setup.
Thanks for your help
masteriori said:
What is an aapt? I don't have the SDK installed,using just apktool which I have been able to decompile APKs with. Also, I have been able to compile APKs using the same setup.
Thanks for your help
Click to expand...
Click to collapse
try with apk multi tool. & make sure you install the proper framework files first
example
could you give me a simplified example with coloured codes
red=changable
ps thank you
Envious_Data said:
could you give me a simplified example with coloured codes
red=changable
ps thank you
Click to expand...
Click to collapse
I will give you a conceptual idea about what I mean in some days,but I have to prepare that for you 1st.please be patient for some days as I am a bit busy with a rom update & everyday life.
Does it work to remove some items from settings??? I`m interested in it, too!
I´m a newbie so sorry for my stupid question:
What do i need exactly for using the apk multi-tool ? Which steps i have to make before i can adjust my settings ...
Thank you for help and patience with a newbie ...:good:
Hi, I want to ask about making sub menu. For example make power management menu, sub menu are battery, cpu control. How ?
Sent from my LT25i using xda premium
Hi all,
I'm an icon pack developer and I've created cool icon packs to be used with the majority of Launchers.
Unfortunately, my icon packs are not compatible with Poco Launcher, installed on both MIUI and non-MIUI phones.
I think that there should be some line code to be put in the Manifest.xml of my icon packs, but honestly I don't know which tags/code to be used.
Can you please help me in understanding the correct code to use in order to make the icon packs to be compatible with Poco Launcher?
I will need something like this I suppose:
Code:
<intent-filter android:label="@string/app_name">
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
Please note that the icon packs I've created are based on CandyBar-Dashboard framework.
Thank you so much!
Marco
you can find an answer here
General Questions about Themes GO HERE!!!!!