Related
I managed to fix mms sending on cricket. I edited default.xml in /system/customize/MNS and Mms.apk. Now my picture message works perfectly on my phone.
So in order to install files you need to download them and then unzip default.zip.
You need to place both filies inc c:\ drive.
Now
adb push c:\Mms.apk /system/app/Mms.apk
adb push default.xml /system/customize/MNS/default.xml
adb reboot
Once your phone reboots it should work fine with picture messages.
Did anyone try this let me know how this works for you. I would post my apn settings but I use full android plan. Let me know how this works for you guys.
Now this is something we need to get the mms receive working in miui but for sprint
Sent from my HTC Evo using Tapatalk
This for cricket it allows to receive and send picture message. I tested with verizon and t mobile customers and works realy fast.
Could you fix the one for the miui rom it only sends mms but dont receive
Sent from my HTC Evo using Tapatalk
hmm interesting lemme try summin
Did you modify MMS.apk and fix what was causing it not to send properly? Is this a modified MMS from a Sprint rom? Or one from a Verizon roms like the rest of us have been using?
Would you mind sharing?
Also, are you capable of MMS while wifi is on by any chance?
NICE!
Thanks for sharing....
I will try and repost my results I also am on the android plan this is my apn settings..
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="1">
<apn name="CDMA-MMS" numeric="46605" mcc="466" mnc="05" apn="mms" user="your10digit#here@mycricket.com" server="NA" password="cricket" proxy="wap.mycricket.com" port="8080" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="http://mms.mycricket.com/mycricket/mms.php" type="mms" />
</apns>
Thanks to deathsled... for the apn
WHOA, Im ecstatic!
You did it!
I confirm this solution to be working on my favorite ROM solution...
VirusROM BASE SENSE RC3 with Carbon Theme...
I could not use the adb push method as I am on the road and forgot to grab my micro usb cable...
1. I used Root Explorer to first delete mms.apk from /system/app
2. I copied mms.apk to /system/app
3. Using Root Explorer I over wrote default.xml/system/customize/MNS/default.xml
4. Reboot
5.
A. To my surprise I did not have a messaging app in the app drawer upon boot?
B. Using Root Explorer I navigated my SD card to folder I had placed mms.apk and launched mms.apk thus installing.
6. Downloaded and installed APN Backup, removed current apn.
7. I used the above posted APN.xml after modifying the "red" string with my info, thanks deathsled provided and apn.xml
8. Rebooted
9. SUCCESS!
I figure some of the steps may not be necessary how ever I documented the exact process and procedure in which I now have functioning MMS..
tritron777 Major props to you man!!! You just killed it man!!!!
This is from sprint rom mms.apk and default.xml. I did not try to send mms over wifi.
I believe that for someone using proxy they can use apn proxy by changing this mmsproxy="null" mmsport="null" to mmsproxy="wap.mycricket.coml" mmsport="8080"
Well I found out that modification to default.xml also changed the market. It restored download section. The problem with sending mms over wifi is that we mms server is protected by cricket or any carrier so it limited by range of ip addresses so we can't connect because we are not on a network. So the only way to make this work is to have stop wireless connection and start data the moment we eant to send mms.
What was the issue with the market download section?
I did not have an issue with it that I noticed?
tritron777 said:
This is from sprint rom mms.apk and default.xml. I did not try to send mms over wifi.
I believe that for someone using proxy they can use apn proxy by changing this mmsproxy="null" mmsport="null" to mmsproxy="wap.mycricket.coml" mmsport="8080"
Click to expand...
Click to collapse
Proxy information is not needed on cricket regardless of the plan. (im on a proxy plan and don't have any in there and its fine)
Question for you, was all that you modified was the:
Mms.apk>smali>com>android>mms>transport>HttpUtils.smali
X-SPRINT-MDN to X-Cricket-MDN?
Or were there other internal changes to the Mms.apk file needed? reason im asking is i would like to do the same for hero users as well since this seems to plague all sprint roms and i have been digging to find the root cause for awhile
That the change I made to mms.apk wasto change X-MDN to X-Cricket-MDN I guess metropc would need X-metropc-MDN. Now default.xml I changed all sprint references to
the way ZIO shows it self. Now that gets market back to the way it was before sprint section was added
tritron777 said:
That the change I made to mms.apk wasto change X-MDN to X-Cricket-MDN I guess metropc would need X-metropc-MDN. Now default.xml I changed all sprint references to
the way ZIO shows it self. Now that gets market back to the way it was before sprint section was added
Click to expand...
Click to collapse
Awesome thanks for the info. Going to try to correct this for hero's now as well
and now we know!
Next up, fix MMS under AOSP/non sense roms for Cricket. Or does that work and I'm retarded? I couldn't find anywhere to set the MMS size and I think that might be the only problem.
Just in case I have a backup of the Mms.apk from a brand new Samsung epic. Just email or PM me. no I do not charge for this. And if anyone can host the file i will be more than glad to share.
the Mms.apk does remove the Mms from the phone. when i try to reinstall it from the phone using root explorer it says "Parse Error there is a problem parsing the package." does anyone know what i can do to fix this error?
Not related but... anyone get Metro MMS working yet? I have a working APN from my bros Eris and I cant get it working at all... How would one edit the Mms.apk?
morbidj said:
WHOA, Im ecstatic!
You did it!
I confirm this solution to be working on my favorite ROM solution...
VirusROM BASE SENSE RC3 with Carbon Theme...
I could not use the adb push method as I am on the road and forgot to grab my micro usb cable...
1. I used Root Explorer to first delete mms.apk from /system/app
2. I copied mms.apk to /system/app
3. Using Root Explorer I over wrote default.xml/system/customize/MNS/default.xml
4. Reboot
5.
A. To my surprise I did not have a messaging app in the app drawer upon boot?
B. Using Root Explorer I navigated my SD card to folder I had placed mms.apk and launched mms.apk thus installing.
6. Downloaded and installed APN Backup, removed current apn.
7. I used the above posted APN.xml after modifying the "red" string with my info, thanks deathsled provided and apn.xml
8. Rebooted
9. SUCCESS!
I figure some of the steps may not be necessary how ever I documented the exact process and procedure in which I now have functioning MMS..
tritron777 Major props to you man!!! You just killed it man!!!!
Click to expand...
Click to collapse
I keep getting application not installed for step 5B when trying to install app any way around this?
I tried with Root Explorer, App Installer, and even adb install, non worked!
First of I want to say that I am not a developer. I don't have programming experience nor do I know a whole lot about this particular subject. I hope that sharing what I have found so far will help anyone else who wants to do something similar. With the help of voodoo55 I have successfully created and compiled APKs for use with the TMobile theme engine. Although this appears to be a great idea for the experienced developer because it will make themes cross device compatible it probably isnt going to be such a big hit with the normal joe blow themer such as myself for a few main reasons.
1. You have to be running linux and tapped into the CyanogenMOD github.
2. You're probably going to need to know a bit of xml coding (which I didnt when I started).
3. You're going to have to know how to decompile and edit .9 PNGs.
4. You're going to have to know how to compile APKs un linux as well
None of these in themselves are all that complicated or hard for that matter, just tedious and very time consuming for the average themer. I am not going to get into specifics or xml code details here. As I am not a developer and dont know much about this stuff all I am going to do is tell you how these APKs function and what files need to be changed in order to compile them. Also, you'll find out the time consuming problem with compiling these APKs and how to fix it. Im just too lazy to sit here and manually fix hundreds of images.
Please remember these instructions are not very detailed but give a general idea on the direction you will need to take to make this happen. Also, for anyone who knows more about this than I do, please, feel free to correct me.
Step 1 - You are going to need to have a working linux distro running.Step 2 - You need to follow the instructions located here minus the last step to get the source from Cyanogen's github.Step 3 - Once #2 is complete and you have downloaded the source to the ~/android/system directory, you will find the current uncompiled source for the TMobile themes "Androidian" and "Cyanbread" in the ~/android/system/vendor/tmobile/themes directory.Step 4 - The experienced Dev would probably start completely from scratch here but I didn't so I'm not going to tell you how. As template, make a copy of the Cyanbread folder and renamed to your theme name.Step 5 - Here we are going to want to edit some files to make the compile possible with. In "your theme" directory there is a filed named Android.mk. In a txt editor you will need to change the following line:
Code:
LOCAL_PACKAGE_NAME := Cyanbread
to
Code:
LOCAL_PACKAGE_NAME := yourthemename
Step 6 - Edit the following lines in AndroidManifest.xml by replacing Cyanbread with your theme name.
Code:
<manifest
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:pluto="http://www.w3.org/2001/pluto.html"
package="com.tmobile.theme.Cyanbread"
android:hasCode="false">
<uses-feature android:name="com.tmobile.software.themes" />
<theme
pluto:themeId="Cyanbread"
pluto:styleId="@style/Cyanbread"
pluto:name="@string/theme_name"
pluto:preview="@drawable/preview"
pluto:author="@string/author"
pluto:copyright="@string/copyright"
pluto:wallpaperImage="@drawable/wallpaper"
pluto:styleName="@string/style_appearance_name"
pluto:ringtoneName="Shocking"
pluto:ringtoneFileName="media/audio/ringtones/Shocking.mp3"
pluto:notificationRingtoneName="Teleport"
pluto:notificationRingtoneFileName="media/audio/notifications/Teleport.mp3">
Step 7 - Open up the res/values folder. There are two files in this particular template that need to be edited, strings.xml and themes.xml.
In the themes.xml you will need to change this line of code
Code:
<style name="Cyanbread" parent="@android:style/Theme" />
to this
Code:
<style name="yourthemename" parent="@android:style/Theme" />
and in the strings.xml you are basically doing the same thing by replacing "Cyanbread" everywhere with "yourthemename"
Code:
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<string name="app_name">Cyanbread Theme</string>
<string name="theme_name">Cyanbread</string>
<string name="style_appearance_name">Cyanbread</string>
<string name="author">T-Mobile MSD</string>
<string name="copyright">T-Mobile</string>
</resources>
it should look similar to this when edited
Code:
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<string name="app_name">youthemename Theme</string>
<string name="theme_name">yourthemename</string>
<string name="style_appearance_name">yourthemename</string>
<string name="author">You are the author</string>
<string name="copyright">there is no copyright on open source</string>
</resources>
Ok, so far this isn't to complicated but from here on out it gets a little more tricky for the average joe. Let me try to explain how these APKs work. Basically the xml files in the theme APK tells android to look in its own folders for, basically, substitute PNG images for the ones currently in the your framework and system/app packages on your phone. Pretty simple, no big deal. There are numerous xml files located in the various folders within the APK but I'm only going to talk about the two main ones need. In the res/xml there is a file named redirections.xml and android.xml. The redirections.xml basically tells the Tmobile theme picker thingy what other xml files to look at to find the source for the replacement PNGs. The main one being android.xml. Android.xml tells the OS on your phone what replacement PNGs to use for the theme. This will replace images that would normally be used from the framework-res.apk. There are other xml files in this directory as well, each one is correspondent to any APK in /system/app on your phone that you wish to theme. For instance com_android_systemui.xml will correspond to /system/app/SystemUI.apk. It works the same was that the android.xml file does and can be edited in the same way as well.
Hope that wasn't to confusing.
Step 8 - Now you will notice there are res/drawable-hdpi and res/drawable-mdpi folders in here as well. Here is where you will add new PNGs for your theme. Personally I deleted the entire contents of the folder and started over. Im not going to get into the specifics of what PNGs to replace as any themer should be ok with doing this. You can place images from any /system/app/*.apk as well but for now I am referring to the framework-res.apk. Once you replace your PNGs you are going to have to create an associated link in the android.xml.
Please note: Any .9 PNGs you replace will HAVE, IT IS A MUST, to be decompiled and the borders edited correctly for the APK to compile correctly.
Step 9 - Open the android.xml file. Initially you will see lots of code but since you are starting over you will want to delete everything between these two lines.
Code:
<resource-redirections>
</resource-redirections>
Once this is complete we will now add the code you will need so it will find the PNG you replaced. For instance, if you placed an edited stat_sys_battery_40.png in the res/drawable-hdpi folder you are going to need to add this line of code the the xml file inbetween the <resource-redirections> code
Code:
<item name="drawable/stat_sys_battery_40">@drawable/frameworks_res_stat_sys_battery_40</item>
I hope you can see how the code corresponds to the PNG name as well. You can basically name the image anything you want as long as the code above is told to where to look.
The same this would apply to any other xml file for their associated APKs as well.
Step 10 - Here you will want to edit the res/xml/redirections.xml file. You will see it has tons of stuff in it but again you will want to remove anything are not using. If you are only using say, the android.xml and the com_android_systemui.xml it would look similar to this:
Code:
<theme-redirections
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:pluto="http://www.w3.org/2001/pluto.html">
<package-redirections android:name="android"
android:minSdkVersion="7"
android:resource="@xml/android" />
<package-redirections android:name="com.android.systemui"
android:minSdkVersion="7"
android:resource="@xml/com_android_systemui" />
</theme-redirections>
Step 11 - Now for the final test of whether or not you edited everything correctly you will need to compile the APK. Open a terminal window and type
Code:
cd ~/android/system
and then type
Code:
make yourthemename
If you have edited everything correctly you APK will be compiled and can be found in the ~/android/system/out/target/product/supersonic/system/app folder. If it doesnt compile it will give you pretty specific errors in the terminal window that you could can go by to correct your problems.
And now for the BAD NEWS !!! The troubles I had while doing this was mainly with .9 PNGs. It seems that a ton of the .9 PNGs us normal themers use have been in some way corrupted d/t being edited incorrectly. Most of the borders are not done correctly. One of two things will happen: 1. They will not decompile correctly or 2. the will not compile correctly with the theme due to faulty editing. This is a simple fix but is extremely time consuming. And I, like most of us, simply don't have the time to fix each .9 I use in my themes for build each APK. Normal PNG changes are no problem however. I hope people will experiment with this as I have and will continue to do in my free time but for now I am going to stick to creating themes the old fashioned way. I do sincerely hope Cyanogen plans on placing his "UI Tweaks" section back into "CM Settings" as well for those of us who dont plan on building theme APKs.
Once again, I AM NOT a developer, so I probably couldn't answer any more advanced questions but feel free to ask. I'm sure there are plenty of people here who can. I just wanted to share my findings and what I did to make these APKs. The "Androidian" theme varies slightly if plan on using it as a template.
Hi! Thankk you so much for your tutorial, all works fine and apk is ok and properly installs on my N1, but if i try to upload the apk on market, it says me "The icon for your application is not valid. Please use a 48x48 PNG.".
Obviously, i checked twice my icons, and searched for a solutions on the net, and for the most of people with this problem it was due by a "\n" in the app name, and not from the icon. But i have not "\n" in my app name, and icons are right, so i can't figure out what is the error due to...
Can you give me some help?
Regards and sorry for my english!
do you happen to know how this would be done on windows?
Currently I have the CyanBread template / source off t-mobiles github page and have a working SDK and eclipse plugin. I am capable of making unsigned or test signed apps and have compiled a few simple apps myself, which worked fine.
Now when I Run As or export unsigned app (as done previously) the theme manager say that the theme was NOT compiled correctly.
I have done this with an unedited version and a minimalist version containing only a few of the SystemUI and framework-res files and removed from the xml correctly, the images in use are the ones which came with the template and so should not be the problem.
I must say that I would not have been able to edit this much without your explainations, so TYVM! truely awesome! And when this works I have an awesome theme half developed , I'm itching to finish.
I've read something about a modified appt.exe to allow the theme manager to assign res images differently or something, this i cannot seem to find. or figure how to bypass. I understand that in linux, you can just pull the whole repository and get it as you stated above, but surely its possible in windows???
any and all help welcome! I'm no dev, but I'd love to be able to theme like this! no more update.zips!
------
p.s. I don't want to do it in Linux virtual box fyi, and even if i did repo/adb (in VM only) currently seem to be broken at my end.
Maybe this links are useful too:
http://code.google.com/p/tmobile-themes/
http://code.google.com/p/android-theme/w/list
From "haxzamatic":
I also have a theme template on github with all AOSP graphics so you can start with stock graphics. I put a ton of work in behind the scenes so we can see some awesome themes for this system.
Click to expand...
Click to collapse
http://github.com/haxzamatic/Templatebread-
Ganii said:
Maybe this links are useful too:
http://code.google.com/p/tmobile-themes/
http://code.google.com/p/android-theme/w/list
From "haxzamatic":
http://github.com/haxzamatic/Templatebread-
Click to expand...
Click to collapse
thanks alot for taking the time to reply, but i have read the first 2 links before and it only has instructions for getting the full repository in linux, as for the templates they are all quite similar, althought that one by haxzamatic is one of the "fullest" ones I've seen. This I'm sure is not the problem, as i can compile the template after importing it as a project in eclipse but it will NOT apply.
I have even made a signed apk and installed it off the SD, it installs fine, but wont apply.
I suppose i should get repo working in my linux box.... but i do think its silly the appt wasn't released for windows and linux.... any more advice?
I compiled my theme this morning, and it finished with no errors but when i go to install it doesn't work. The apk looks good, so Idk.
trock79 said:
I compiled my theme this morning, and it finished with no errors but when i go to install it doesn't work. The apk looks good, so Idk.
Click to expand...
Click to collapse
You have to be using the AAPT from T-Mobile git to support the theme resource IDs in resources.arsc. The stock AAPT will not generate the IDs expected by the theme manager.
weareallkosh said:
You have to be using the AAPT from T-Mobile git to support the theme resource IDs in resources.arsc. The stock AAPT will not generate the IDs expected by the theme manager.
Click to expand...
Click to collapse
That is the method I used. When I go to install the apk it fails.
trock79 said:
That is the method I used. When I go to install the apk it fails.
Click to expand...
Click to collapse
Where did you get the modified AAPT from?
NickHu said:
Where did you get the modified AAPT from?
Click to expand...
Click to collapse
From here http://code.google.com/p/android-theme/wiki/TMobileThemeEngine
and here http://pastebin.com/3i7xLBTU
If the instructions in this thread are followed everything works and applies correctly. I am getting the code from the cyan github.
Sent from my PC36100 using XDA App
t3project said:
If the instructions in this thread are followed everything works and applies correctly. I am getting the code from the cyan github.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That is fine if you want to work with the png's that are included with cyanbread theme, but I have more than what is included that theme and do not want to add all the commits just shy of a thousand more png's.
Anybody know how to change the color of the text on [just] the pulldown? I've been fiddling with no luck so far...
Thanks!
Hi t3project, I made a script following your instructions that may help on build apk theme:
http://forum.xda-developers.com/showthread.php?p=12050403#post12050403
trock79 said:
That is fine if you want to work with the png's that are included with cyanbread theme, but I have more than what is included that theme and do not want to add all the commits just shy of a thousand more png's.
Click to expand...
Click to collapse
you can use any png you want and as many as you want as long as you add the resource the the appropriate xml. they just have to be decompiled pngs and correctly edited for compiling. same thing goes for template them xml. just add the appropriate resource to the xmls and you can use whatever or howmany ever you want.
i did have a script that did this in about 2 seconds for you but i cant find it at the moment
You dont need a linux box for it to compile, install the windows android sdk, eclipse + eclipse adt, git clone the androidian theme, create a new android project in eclipse, choose create from source and select the androidian folder, build and enjoy.
How can I just download the t-mobile bit (and gingerbread, or whatever is the barebones minimum for this)? Its downloading all the devices cyanogen supports, and thats just a waste of my time/disk space/internet connection (which is particularly slow)
items name
This is about /res/xml/android.xml.
how to do so that we can know where the drawable position located? I'm confused what the name of the image that I would change.
examples where the position of the image and name in the /res/xml/android.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"
}
{
"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"
}
Tired Storeman's Tutorials
Hello, and welcome to my Tutorials thread for JB 4.1.2 Roms
Here i will post tutorials that i think some people might find useful.
I would like to start off by thanking a few people who have given me
some great advice and help along the way.
@Goldieking
@Spannaa
@bombaybadboy
@churapa
@Many40
@_Sale_
And everyone else who has helped me along my XDA journey.
I am using XWLSW NeatROM Lite v4.8 with Blue Ginger Plus theme with 23 toggles whilst making these tutorials.
A big thankyou to @_Sale_ for his great rom,
and @Spannaa for his great theme.
These tutorials assume you know how to decompile/compile apks and push them to your phone.
Please make a backup before you start, just in case.
MY TUTORIALS
Single Line Notification Date Post #2
Remove Carrier Label Post #5
Centered Settings Headers Post #13
Single Line Notification Date
Single Line Notification Date
Most JB roms display there notification date on 2 lines with fairly small text, making them rather hard to read.
This tutorial will show you how to change the notification date to a single line, change the date format, and increase the font size.
Changing the date to a single line.
Step 1. Decompile SystemUI.apk and open SystemUI/res/layout/tw_status_bar_expanded_header.xml.
Step 2. find the line begining with
<com.android.systemui.statusbar.policy.DateView.....
Click to expand...
Click to collapse
On the end of this line, there should be
android:maxLines="2"
Click to expand...
Click to collapse
or
android:singleLine="false"
Click to expand...
Click to collapse
You need to change them to
android:maxLines="1"
Click to expand...
Click to collapse
or
android:singleLine="true"
Click to expand...
Click to collapse
Step 3. Save tw_status_bar_expanded_header.xml.
Step 4. Open SystemUI/res/values/strings.xml
and find the following lines
<string name="status_bar_date_formatter">%1$s
%2$s</string>
Click to expand...
Click to collapse
You need to make a single line out of both lines
So you end up with this
<string name="status_bar_date_formatter">%1$s %2$s</string>
Click to expand...
Click to collapse
Step 5. Remove the %1$s so you end up with
<string name="status_bar_date_formatter">"%2$s"</string>
Click to expand...
Click to collapse
Step 6. Save string.xml
Step 7. Compile SystemUI.apk
Step 8. Copy and paste META-INF folder and AndroidManifest.xml file from original SystemUi.apk
to newly compiled SystemUI.apk, replacing existing folder and file,
Step 9.Compile SystemUI.apk again
Step 10. Push SystemUi.apk to phone
Step 11. Set permissions to rw-r--r--
Step 12. Reboot
With a bit of luck, you should end up with something like this.
Change Notification Date Format
Please make a backup before you start, just in case
Which date format you have set on your phone,
will determine which line you need to edit to change the date format
I have this format set, so i will edit the appropriate line in strings.xml
Which is "Day Month Year"
The individual date formats that you can combine to change the overall date format are as follows
d......................Day Of Month Without Leading Zero, 7
dd....................Day Of Month With Leading Zero, 07
EEEE..............Day Of Week (Full) MONDAY
EEE.................Week Day (Short) MON
MMMM..........Month (Full) AUGUST
MMM..............Month (Short) AUG
yyyy................Year (Full) 2013
yy....................Year (Short) 13
Whilst you have your decompiled SystemUi.apk open, go to SystemUi/res/values/strings.xml
and find
<string name="quickpanel_day_month_year">d MMMM. yyyy</string>
Click to expand...
Click to collapse
Now it is a matter of replacing
d MMMM. yyyy
Click to expand...
Click to collapse
in the above string with what ever combination you want your date to be.
Once you have finished editing
d MMMM. yyyy
Click to expand...
Click to collapse
Save strings.xml.
If you want to change the size of the date text, open SystemUI/res/layout/tw_status_bar_expanded_header.xml
go to
<com.android.systemui.statusbar.policy.DateView...........
Click to expand...
Click to collapse
After
<com.android.systemui.statusbar.policy.DateView android:textAppearance="@style/TextAppearance.StatusBar.Expanded.Date"
Click to expand...
Click to collapse
There should be
android:textSize="22.0dip"
Click to expand...
Click to collapse
If not insert it immediatly after
<com.android.systemui.statusbar.policy.DateView android:textAppearance="@style/TextAppearance.StatusBar.Expanded.Date"
Click to expand...
Click to collapse
to end up with
<com.android.systemui.statusbar.policy.DateView android:textAppearance="@style/TextAppearance.StatusBar.Expanded.Date" android:textSize="22.0dip"
Click to expand...
Click to collapse
Change
"22.0dip"
Click to expand...
Click to collapse
To what ever size you want
Save tw_status_bar_expanded_header.xml.
Compile SystemUI.apk
Copy and paste META-INF folder and AndroidManifest.xml file from original SystemUi.apk
to newly compiled SystemUI.apk, replacing existing folder and file
Compile SystemUI .apk again
Push SystemUI.apk to phone
Set permissions to rw-r--r--
Reboot
The examples below use "22.0dip"
A few examples of different date formats
please do not create multiple threads for the same reason
As a senior member u should lead by example
Sun90 said:
please do not create multiple threads for the same reason
As a senior member u should lead by example
Click to expand...
Click to collapse
I will be deleting the other thread once i have copied everything over to this thread
Remove Carrier Label
Make a backup of your SystemUI, just in case.
To remove the carrier label from the status bar close/drop down handle
it is simply a matter of changing the text color to transparent.
Step 1. Decompile SystemUI.
Step 2. Open tw_status_bar_expanded.xml.
Step 3. Towards the bottom you will find the following line.
<TextView android:textAppearance="@style/TextAppearance.StatusBar.Expanded.Network" android:gravity="center" android:layout_gravity="bottom" android:id="@id/carrier_label" android:layout_width="fill_parent" android:layout_height="@dimen/tw_close_handle_height" android:layout_marginBottom="10.0dip" />
Click to expand...
Click to collapse
Add the following
android:textColor="#00000000"
Click to expand...
Click to collapse
Immediatly after
<TextView android:textAppearance="@style/TextAppearance.StatusBar.Expanded.Network"
Click to expand...
Click to collapse
So you end up with
<TextView android:textAppearance="@style/TextAppearance.StatusBar.Expanded.Network" android:textColor="#00000000"
Click to expand...
Click to collapse
Step 4.Save tw_status_bar_expanded.xml.
Step 5. Recompile SystemUI.
Step 6. Copy and paste META-INF folder and AndroidManifest.xml file from original SystemUi.apk
to newly compiled SystemUI.apk, replacing existing folder and file.
Step 7. Compile SystemUI apk again.
Step 8. Push SystemUI.apk to phone.
Step 9. Reboot.
Help
Why I dont have this? tw_status_bar_expanded_header.xml
Any file started with " tw_ ". I dnt have
WinchyHanepp said:
Why I dont have this? tw_status_bar_expanded_header.xml
Any file started with " tw_ ". I dnt have
Click to expand...
Click to collapse
Which rom are you using?
feeling sad
Tired Storeman said:
Which rom are you using?
Click to expand...
Click to collapse
I'm usin Jellybean 4.1.2 Stock ROM. My phone rebranded Karbonn a9+ which Cherry Mobile Flare S100
WinchyHanepp said:
I'm usin Jellybean 4.1.2 Stock ROM. My phone rebranded Karbonn a9+ which Cherry Mobile Flare S100
Click to expand...
Click to collapse
Is that a Samsung Galaxy s2 GT-I9100?
no
Tired Storeman said:
Is that a Samsung Galaxy s2 GT-I9100?
Click to expand...
Click to collapse
No sir. It's a phone from India and rebrand here in the Philippines.Im just wondering why I dont have that xml file. Its maybe Im using a stock rom?
WinchyHanepp said:
No sir. It's a phone from Indian and rebrand here on the Philippines.Im just wondering why I dont have that xml file. Its maybe Im using a stock rom?
Click to expand...
Click to collapse
If i had to have a guess, i would say it is probably because it is not a Samsung Galaxy s2 Rom.
My tutorials are generally for Samsung Galaxy s2 users, as that is the type of phone i have
sir
Oh I see. Is this excluive only for Samsung? I think Im on a wrong thread. Sorry sir. Newbie here.
Centered Settings Headers
PLEASE MAKE A BACKUP BEFORE YOU START
I made this tutorial for Alliance Rom users a few months back, but should work on any JB 4.1.2 rom.
Step 1. On your phone, in system/framework make a new folder and name it Frame.
Step 2. On your desktop make a new folder and name it Center,open it and leave open
Step 3. Obtain framework-res.apk from your phone, NOT FROM UNZIPED ROM ON YOU COMPUTER by ether pulling with adb or copy from system/framework with Root Explorer to your desktop
Step 4. Decompile framework-res.apk
Step 5. Open the decompiled framework-res folder
Step 6. Open the res folder
Step 7. Open the values folder
Step 8. Open the styles xml file with what ever you use to open xml files (I use Notepad++)
Step 9. Search for
Code:
<style name="Widget.DeviceDefault.TextView.ListSeparator" parent="@style/Widget.Holo.TextView.ListSeparator">
You need to edit the folowing
Code:
<style name="Widget.DeviceDefault.TextView.ListSeparator" parent="@style/Widget.Holo.TextView.ListSeparator">
<item name="textSize">17.0dip</item>
<item name="textStyle">normal</item>
<item name="textColor">#ffd2d2d2</item>
<item name="background">@drawable/tw_list_section_divider_holo_dark</item>
<item name="paddingLeft">16.0dip</item>
<item name="textAllCaps">false</item>
</style>
Your file might look slightly different, i have changed the text color.
Step 10. Add .
<item name="gravity">center</item>
After
<item name="textColor">#ffd2d2d2</item>
Ending up with
Code:
<style name="Widget.DeviceDefault.TextView.ListSeparator" parent="@style/Widget.Holo.TextView.ListSeparator">
<item name="textSize">17.0dip</item>
<item name="textStyle">normal</item>
<item name="textColor">#ffd2d2d2</item>
[COLOR=Red]<item name="gravity">center</item>[/COLOR]
<item name="background">@drawable/tw_list_section_divider_holo_dark</item>
<item name="paddingLeft">16.0dip</item>
<item name="textAllCaps">false</item>
</style>
Here you can also change the text color and size if you want,
You can also change the textStyle from normal to bold, if you want bold text
or change textAllCaps from false to true if you want All Capital text.
Step 11. Save changes.
Step 12. Compile framework-res.apk. (you should not recieve any errors)
Step 13. Open the folder where it was compiled to (in Apktool it is the build/apk folder).
and replace the META-INF folder and the AndroidManifest.xml file from this folder with the META-INF folder and the AndroidManifest.xml file
from the original framework-res.apk, that you placed on your desktop.
Step 14. Compile framework-res.apk again. (again you should not recieve any errors)
You need to do the following steps to avoid bootloop
Step 15. Open the compiled framework-res.apk DO NOT UNZIP IT. (in Apktool.it is in the dist folder)
Drag the
assets
META-INF
res
AndroidManifest.xml
resources.arsc
folders and files into the previously opened Center folder which you created on your desktop.
Step 16. If it is not already opened, open the Center folder
Step 17. Highlight all of the folders and files in the Center folder and right click on them(if using windows) and click add to archive (i am using Winrar)
In the window that pops up for Archive Format use Zip
and compression method use Store
Change Archive name to framework-res.apk
and hit ok.
Step 18. Once framework-res.apk has been made, push to phone
Step 19. Set permissions to rw-r--r--
If phone bootloops, restore backup and try again
The above steps will have no effect on the ported S4 Tabbed Settings.
Screenshot 1 Centered text normal
Screenshot 2 Centered text bold
Screenshot 3 Centered text All Capitals
WinchyHanepp said:
Oh I see. Is this excluive only for Samsung? I think Im on a wrong thread. Sorry sir. Newbie here.
Click to expand...
Click to collapse
the tw_... files are for touchwiz roms, these mods should work on the same xml files but without tw_ (instead of tw_status_bar_expanded_header.xml you need to mod status_bar_expanded_header.xml)
As i have updated to an S3, i will no longer be monitoring this thread, but i will leave it up for reference.
Sent from my GT-I9305 using Tapatalk
thanks :good:
have any for change the scroll bar ??
like 4.2
After i upgrade my note 3 (sm-n900) to android 4.4 kitkat... my 360 camera app cant't save photo to extsdcard. is it just me? Or because of new kitkat update .help!
Have a look around, theres an issue with using extSD card, there is also a fix for it. - NOt sure if it'll fix saving pictures to SD Card but I don't have issues.
crazy_777 said:
After i upgrade my note 3 (sm-n900) to android 4.4 kitkat... my 360 camera app cant't save photo to extsdcard. is it just me? Or because of new kitkat update .help!
Click to expand...
Click to collapse
You posted the question in someone's else thread and I answered you there.
I'll post the same answer here.
1. Install es file manager or any file reader with root.
2. navigate to /System/etc/permissions
3. open "platform.xml" file to edit
4. look for the stack that has "WRITE_EXTERNAL_STORAGE"
you will find something like <group gid="sdcard_r" />
5. make sure these lines are there, if not, add them
<group gid="sdcard_rw" />
<group gid="media_rw" />
That's it
I was also unable to save my photos to the external SD because in the Camera360 settings, when I change the save location to "external sd" and the dialogue popped up for me to choose a folder in the external SD, no folders showed up.
Any way, whether or not your problem is similar, if someone is reading this thread and is unable to save to ext SD, try what I did. Manually change the save directory.
You need a rooted phone and a root explorer like ES File explorer.
Go the this directory: /data/data/vStudio.Android.Camera360/shared_prefs/
Open the file "vStudio.Android.Camera360_global.xml" with a text editor. This is where some settings are stored. Go to the following line(close to the end):
<string name="pref_camera_save_path_key">/storage/emulated/0/DCIM/Camera/<string>
(you might have a different path depending on what is currently set as the save directory in Camera360)
Change the path in this line to the path you want it save photos in. For example, I have a "DCIM/Camera" folder in my external sdcard and I want the photos to be saved there, so change it to "/storage/sdcard1/DCIM/Camera/", that is, now that line is changed to
<string name="pref_camera_save_path_key">/storage/sdcard1/DCIM/Camera/<string>
NOTE THAT In your phone external sdcard may be at a different path instead of "/storage/sdcard1. Accordingly change it.
gganon said:
I was also unable to save my photos to the external SD because in the Camera360 settings, when I change the save location to "external sd" and the dialogue popped up for me to choose a folder in the external SD, no folders showed up.
Any way, whether or not your problem is similar, if someone is reading this thread and is unable to save to ext SD, try what I did. Manually change the save directory.
You need a rooted phone and a root explorer like ES File explorer.
Go the this directory: /data/data/vStudio.Android.Camera360/shared_prefs/
Open the file "vStudio.Android.Camera360_global.xml" with a text editor. This is where some settings are stored. Go to the following line(close to the end):
<string name="pref_camera_save_path_key">/storage/emulated/0/DCIM/Camera/<string>
(you might have a different path depending on what is currently set as the save directory in Camera360)
Change the path in this line to the path you want it save photos in. For example, I have a "DCIM/Camera" folder in my external sdcard and I want the photos to be saved there, so change it to "/storage/sdcard1/DCIM/Camera/", that is, now that line is changed to
<string name="pref_camera_save_path_key">/storage/sdcard1/DCIM/Camera/<string>
NOTE THAT In your phone external sdcard may be at a different path instead of "/storage/sdcard1. Accordingly change it.
Click to expand...
Click to collapse
it's really working for me
Thanks for Sharing
glad Found this way
================================================================================================
Phone : Xperia Z 6602
FW : Kit Kat 4.4.2 (10.5.A.0.230)
Bootloader : unlocked
rooted : Yes
---------- Post added at 07:32 AM ---------- Previous post was at 06:35 AM ----------
y2kkingboy said:
You posted the question in someone's else thread and I answered you there.
I'll post the same answer here.
1. Install es file manager or any file reader with root.
2. navigate to /System/etc/permissions
3. open "platform.xml" file to edit
4. look for the stack that has "WRITE_EXTERNAL_STORAGE"
you will find something like <group gid="sdcard_r" />
5. make sure these lines are there, if not, add them
<group gid="sdcard_rw" />
<group gid="media_rw" />
That's it
Click to expand...
Click to collapse
i can't save the "platform.xml" after making change. it said "error occurs during saving"
any suggest?
UPDATE
it's work after change the permission of that file.
just change it to read/write on setting
gganon said:
I was also unable to save my photos to the external SD because in the Camera360 settings, when I change the save location to "external sd" and the dialogue popped up for me to choose a folder in the external SD, no folders showed up.
Any way, whether or not your problem is similar, if someone is reading this thread and is unable to save to ext SD, try what I did. Manually change the save directory.
You need a rooted phone and a root explorer like ES File explorer.
Go the this directory: /data/data/vStudio.Android.Camera360/shared_prefs/
Open the file "vStudio.Android.Camera360_global.xml" with a text editor. This is where some settings are stored. Go to the following line(close to the end):
<string name="pref_camera_save_path_key">/storage/emulated/0/DCIM/Camera/<string>
(you might have a different path depending on what is currently set as the save directory in Camera360)
Change the path in this line to the path you want it save photos in. For example, I have a "DCIM/Camera" folder in my external sdcard and I want the photos to be saved there, so change it to "/storage/sdcard1/DCIM/Camera/", that is, now that line is changed to
<string name="pref_camera_save_path_key">/storage/sdcard1/DCIM/Camera/<string>
NOTE THAT In your phone external sdcard may be at a different path instead of "/storage/sdcard1. Accordingly change it.
Click to expand...
Click to collapse
Hi, thank you so much for your post. After 5 to 6 fails, I found out that I have to restart the device for it to work.... sorry guys, is there way to change how the picture is named? For example taking out "C360_" on the name?
Thanks.
Hello everyone!
Ever noticed some of the emoji on your Android device displaying a black version of the emoji instead of the better colored one (for example the red heart or the peace emoji)?
I found a very simple fix, but it requires root and changing some xml files in your system partition.
So basically, find the fonts.xml file in the /system/etc/ directory and open it with a text editor.
Almost at the bottom of the file, you'll find a line which contains "NotoColorEmoji.ttf". This is the colored emoji font (as you might have guessed).
Notice how it is positioned below "NotoSansSymbols-Regular-Subsetted.ttf", this means that, when a symbol is rerquested, Android first checks the NotoSansSymbols font, and only if it is not found in there, it looks for it in the NotoColorEmoji font.
Guess where those ugly black versions of the emoji are stored... Yup, in the NotoSansSymbols font!
So, how do we make Android always use the colored emoji? Just cut
Code:
<family>
<font weight="400" style="normal">NotoColorEmoji.ttf</font>
</family>
and paste it above
Code:
<family>
<font weight="400" style="normal">NotoSansSymbols-Regular-Subsetted.ttf</font>
</family>
Pretty simple, right? You now have to do a very similar thing in the fallback_fonts.xml file in the same directory. I'm sure you guys can figure that one out on your own
And that's it! Reboot your phone, and no more black versions of emoji!
Enjoy!
Note: If someone could push this fix into CyanogenMod or make a flashable zip or make an app that does this, I would be very grateful, cause it's really annoying to have to do this after each ROM flash!
Hi!
I recently flash the Android N emojis onto my LG G3( fulmics 5.3)
When I had previously flashed this pack onto my stock LG Rom (5.0 Lollipop), all emojis were normal in appearance.
After I flashed fulmics and flashed this pack, I have been getting these black and white emojis for some of them( crossbones, writing hand, etc)
What should I do? When I go to edit fonts.xml I cant save my changes
Thanks LanderN, really good guide
some of the emoji which where black before are fine now, but I still have got some that are still black&white. I even tried to move the font entry up but it either didn't change a thing or resulted in bootloop. Anyone with the same problem or even a solution? I'm on latest CM for jactivelte.
Hello! This worked for me the first time I tried it, but as I was updating my emoji, the black and white emojis are back. I tried again this method but the NotoColorEmoji is still above the NotoSansSymbols-Regular-Subsetted. I tried everything, I tried using the backup and then tried this method again, no luck.
[null]
LanderN said:
Hello everyone!
Ever noticed some of the emoji on your Android device displaying a black version of the emoji instead of the better colored one (for example the red heart or the peace emoji)?
I found a very simple fix, but it requires root and changing some xml files in your system partition.
So basically, find the fonts.xml file in the /system/etc/ directory and open it with a text editor.
Almost at the bottom of the file, you'll find a line which contains "NotoColorEmoji.ttf". This is the colored emoji font (as you might have guessed).
Notice how it is positioned below "NotoSansSymbols-Regular-Subsetted.ttf", this means that, when a symbol is rerquested, Android first checks the NotoSansSymbols font, and only if it is not found in there, it looks for it in the NotoColorEmoji font.
Guess where those ugly black versions of the emoji are stored... Yup, in the NotoSansSymbols font!
So, how do we make Android always use the colored emoji? Just cut
Code:
<family>
<font weight="400" style="normal">NotoColorEmoji.ttf</font>
</family>
and paste it above
Code:
<family>
<font weight="400" style="normal">NotoSansSymbols-Regular-Subsetted.ttf</font>
</family>
Pretty simple, right? You now have to do a very similar thing in the fallback_fonts.xml file in the same directory. I'm sure you guys can figure that one out on your own
And that's it! Reboot your phone, and no more black versions of emoji!
Enjoy!
Note: If someone could push this fix into CyanogenMod or make a flashable zip or make an app that does this, I would be very grateful, cause it's really annoying to have to do this after each ROM flash!
Click to expand...
Click to collapse
Wow dude, you really helped me a lot, Thanks?????
Okay, so I downloaded a file text editor and found what you were talking about, so let me get this straight.(I'm pretty dumb sorry) you want me to cut the code, "<family>
<font weight="400" style="normal">NotoColorEmoji.ttf</font>
</family>." As in delete that section of the code and then paste the replacement code, " <family>
<font weight="400" style="normal">NotoSansSymbols-Regular-Subsetted.ttf</font>
</family>?"