Related
****************************************************************************************************
DO NOT FLASH IF YOU DON'T PLAN ON IMPROVING THIS THEME - IT'S NOT READY!
****************************************************************************************************
I think this could be a cool thing. A community built theme.
Partly for me to learn, partly because that's what we are about, right?
I need the help of the talented themers/developers on here though.
My idea:
Take this INCREDIBLE honeycomb theme done by obsessionXYZ (his thread) and port it to our phone.
I am specifically aiming for Trigger 3.2, but I can't see why it would not work for any 2.2 based ROM.
I think just letting everyone throw in their own personal flavor to make this better.
Not going to lie, I have basically done all that I know to do. Not looking for someone to do my work. Looking for someone willing to take this and make it better, but to post what they did. maybe a bit much, but it would be a very cool thing to do and I know a lot of us would learn.
NOTE, for those interested in doing this. STRONGLY suggest looking at Official_Masters thread on using APK Manager to theme.
It is Crazy simple. So much so that I am embarrased to post this thread as any sort of "work" - It was not.
SOMEONE put a lot of time into it (see above - obsessionXYZ), certainly not me.
How would this work?
Well... I'm certain there are a lot of good ways, but the only way I can think of is dropbox or just downloading what I currently have, and make it better.
****************************************************************************************************
DO NOT FLASH IF YOU DON'T PLAN ON IMPROVING THIS THEME - IT'S NOT READY!
****************************************************************************************************
UPDATES (very minor, very much beta)
5.11.11 - made some of the changes birgertime suggested. Got some white in the dropdown notification for text..
now I need to find that (make the text white) for the power menu, and when adding widgets...
DOWNLOAD THE THEME HERE >>>> BETA DOWNLOAD
Here is the wallpaper (doesnt appear the theme is setting it by default yet):
{
"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"
}
KNOWN BUGS:
I do not know how to make the text white, so it's currently black text on a black background. Awesome. Working on it. Go as I learn.
I do not know how to make the volume sliders thin (like honeycomb and the original theme)
Not all of the power menu buttons are blue
Notification dropdown transparent now, original theme has a blue halo on a solid black background
I want it to say "Rotate" not "Auto-Rotation" but I can't find that
The bluetooth toggle does not work, neither does auto rotate. Awesome.
I am sure there are more I have not found yet. Help me find and squash them.
* I am not a fan of this type battery. I plan on changing that soon.
Honeycomb Bootup:
I found a flashable Honeycomb bootup on TeamWhiskey's site (THREAD). You can download the file (CLICK HERE TO DOWNLOAD).
Simply move to internal and flash like a ROM. Bam. Awesome bootup.
Here is it on my phone:
IMAGES:
SPECIAL THANKS - SERIOUSLY, TRULY APPRECIATED
Birgertime - Not only for an AMAZING ROM for us, but the guy has been so patient with my dumb questions. DUMB questions.
Official_Master (his thread and offering help), Junk_Druggler (lots of advice), rel500, buddahlou, shreddintyres, Master&Slave™, and Annex for offering to help (and even do a theme and give me credit, haha) AND the dock in the images above.
you guys get the point. ALMOST EVERY SINGLE PERSON WHO THEMES HAS VOLUNTEERED TO HELP ME! I LOVE THIS COMMUNITY.
I'm certain I forgot people, shoot me a PM if I did. It was not intentional. I am tired.
Yeap, forgot 00.ante who did the themed market (his thread)
JaiThemes did the wallpaper and I just manipulated it in Photoshop to change it from cyan to blue. Didn't do much more than that.
most of those bugs are xml related, simple edits will fix them, I'll download and take a look, I wanna help, since it was this thread that made me want to make a theme
thanks
ld006 said:
most of those bugs are xml related, simple edits will fix them, I'll download and take a look, I wanna help, since it was this thread that made me want to make a theme
thanks
Click to expand...
Click to collapse
That is awesome. Yeah, I haven't a clue how to edit.xml. I also noticed the original that I linked to had a LOT of .jar's which I removed. I'll search more on how to edit.xml. Birgertime was pointing me in the right direction, but I was exhausted last night.
I think I've seen even a better looking one than that. I going to try and find the link.
rel500 said:
I think I've seen even a better looking one than that. I going to try and find the link.
Click to expand...
Click to collapse
Cool. I was impressed, a lot, by the original but am all for a better version.
Remember though, my pics are missing a lot of the coolness the original had. I'm hopeful we can bring that to this.
I already have the boot logo does that affect anything?
s15274n said:
I do not know how to make the text white, so it's currently black text on a black background. Awesome.
I do not know how to make the volume sliders thin (like honeycomb and the original theme)
Not all of the power menu buttons are blue
Notification dropdown is a flat black, original theme has a blue halo look at the top
I want it to say "Rotate" not "Auto-Rotation" but I can't find that
The bluetooth toggle does not work
I am sure there are more I have not found yet. Help me find and squash them.
* I am not a fan of this type battery. I plan on changing that soon.
Click to expand...
Click to collapse
Always looking for something to kill time with - If any of this still needs fixed tonight, I'll do it.
jellette said:
Always looking for something to kill time with - If any of this still needs fixed tonight, I'll do it.
Click to expand...
Click to collapse
If anyone can fix this, I know you can. I would LOVE for you to take a swing at this.
sRs DoLLaR mEnU said:
I already have the boot logo does that affect anything?
Click to expand...
Click to collapse
I only included the bootup if someone wanted it. I actually prefer the stock Trigger boot, so this is not included in the theme.
Since this is a community theme, let's all make Callip do all the work himself!
in /framework-res.apk/res/layout/status_bar_latest_even_content.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<LinearLayout android:layout_gravity="center_vertical" android:orientation="vertical" android:paddingLeft="10.0dip" android:paddingTop="7.0dip" android:paddingRight="10.0dip" android:layout_width="fill_parent" android:layout_height="fill_parent"
xmlns:android="http://schemas.android.com/apk/res/android">
<LinearLayout android:orientation="horizontal" android:paddingTop="3.0dip" android:layout_width="fill_parent" android:layout_height="wrap_content">
<com.android.server.status.AnimatedImageView android:id="@id/icon" android:layout_width="25.0dip" android:layout_height="25.0dip" android:src="@drawable/arrow_down_float" android:scaleType="fitCenter" />
<TextView android:textSize="18.0sp" android:textStyle="bold" android:textColor="[B][COLOR="red"]#ff000000[/COLOR][/B]" android:ellipsize="marquee" android:id="@id/title" android:paddingLeft="4.0dip" android:fadingEdge="horizontal" android:layout_width="fill_parent" android:layout_height="wrap_content" android:singleLine="true" android:layout_weight="1.0" />
</LinearLayout>
<LinearLayout android:orientation="horizontal" android:layout_width="fill_parent" android:layout_height="wrap_content">
<TextView android:textSize="14.0sp" android:textColor="[B][COLOR="Red"]#ff515151[/COLOR][/B]" android:ellipsize="marquee" android:id="@id/text" android:paddingLeft="4.0dip" android:fadingEdge="horizontal" android:layout_width="wrap_content" android:layout_height="wrap_content" android:singleLine="true" android:layout_weight="1.0" />
<android.widget.DateTimeView android:textSize="14.0sp" android:textColor="[B][COLOR="red"]#ff515151[/COLOR][/B]" android:id="@id/time" android:paddingRight="5.0dip" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginLeft="4.0dip" android:singleLine="true" />
</LinearLayout>
</LinearLayout>
Those are the three colors for the dropdown notifications. Not sure if you know this, but the hex code is as follows
# <opacity 2-bit hex> <color 6 bit hex>
Click to expand...
Click to collapse
=======================================================
Also to change the text color for the extra menu (this might also fix the power menu text):
in styles.xml
Code:
<style name="Theme.ExpandedMenu" parent="@style/Theme">
<item name="listViewStyle">@style/Widget.ListView.Menu</item>
<item name="windowAnimationStyle">@style/Animation.OptionsPanel</item>
<item name="background">@null</item>
<item name="itemTextAppearance">?textAppearanceLarge</item>
</style>
I believe you can change that ?textAppearanceLarge to ?textAppearanceLargeInverse and it will fix the issue.
==================================================
The power menu icons-> View attachment ic_locks.zip
In my farmework they are named hawk_download, hawk_recovery, hawk_reboot
birgertime said:
Since this is a community theme, let's all make Callip do all the work himself!
in /framework-res.apk/res/layout/status_bar_latest_even_content.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<LinearLayout android:layout_gravity="center_vertical" android:orientation="vertical" android:paddingLeft="10.0dip" android:paddingTop="7.0dip" android:paddingRight="10.0dip" android:layout_width="fill_parent" android:layout_height="fill_parent"
xmlns:android="http://schemas.android.com/apk/res/android">
<LinearLayout android:orientation="horizontal" android:paddingTop="3.0dip" android:layout_width="fill_parent" android:layout_height="wrap_content">
<com.android.server.status.AnimatedImageView android:id="@id/icon" android:layout_width="25.0dip" android:layout_height="25.0dip" android:src="@drawable/arrow_down_float" android:scaleType="fitCenter" />
<TextView android:textSize="18.0sp" android:textStyle="bold" android:textColor="[B][COLOR="red"]#ff000000[/COLOR][/B]" android:ellipsize="marquee" android:id="@id/title" android:paddingLeft="4.0dip" android:fadingEdge="horizontal" android:layout_width="fill_parent" android:layout_height="wrap_content" android:singleLine="true" android:layout_weight="1.0" />
</LinearLayout>
<LinearLayout android:orientation="horizontal" android:layout_width="fill_parent" android:layout_height="wrap_content">
<TextView android:textSize="14.0sp" android:textColor="[B][COLOR="Red"]#ff515151[/COLOR][/B]" android:ellipsize="marquee" android:id="@id/text" android:paddingLeft="4.0dip" android:fadingEdge="horizontal" android:layout_width="wrap_content" android:layout_height="wrap_content" android:singleLine="true" android:layout_weight="1.0" />
<android.widget.DateTimeView android:textSize="14.0sp" android:textColor="[B][COLOR="red"]#ff515151[/COLOR][/B]" android:id="@id/time" android:paddingRight="5.0dip" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginLeft="4.0dip" android:singleLine="true" />
</LinearLayout>
</LinearLayout>
Those are the three colors for the dropdown notifications. Not sure if you know this, but the hex code is as follows
=======================================================
Also to change the text color for the extra menu (this might also fix the power menu text):
in styles.xml
Code:
<style name="Theme.ExpandedMenu" parent="@style/Theme">
<item name="listViewStyle">@style/Widget.ListView.Menu</item>
<item name="windowAnimationStyle">@style/Animation.OptionsPanel</item>
<item name="background">@null</item>
<item name="itemTextAppearance">?textAppearanceLarge</item>
</style>
I believe you can change that ?textAppearanceLarge to ?textAppearanceLargeInverse and it will fix the issue.
==================================================
The power menu icons-> View attachment 589674
In my farmework they are named hawk_download, hawk_recovery, hawk_reboot
Click to expand...
Click to collapse
This won't directly help this theme, without the additional resources, but I have moved on to using custom xml's for these types of things, which allows greater control - I feel.
Code:
<item name="textColor">@color/edt_tw_button_text_inversible</item>
Is what the line for primary pop-up menu text looks like lately - while the secondary menus have their own xml.
Anyway, just the way I've started to do it.
jellette said:
This won't directly help this theme, without the additional resources, but I have moved on to using custom xml's for these types of things, which allows greater control - I feel.
Code:
<item name="textColor">@color/edt_tw_button_text_inversible</item>
Is what the line for primary pop-up menu text looks like lately - while the secondary menus have their own xml.
Anyway, just the way I've started to do it.
Click to expand...
Click to collapse
resource is already there, I've done this numerous times with stock frameworks
Depends on the build. JVH, for one, does not contain this in the colors folder and has to be added.
It also does not contain tw_primary_icon_text_light.xml
jellette said:
Depends on the build. JVH, for one, does not contain this in the colors folder and has to be added.
It also does not contain tw_primary_icon_text_light.xml
Click to expand...
Click to collapse
No it's all in the Android resource class
birgertime said:
No it's all in the Android resource class
Click to expand...
Click to collapse
I think you put a comma in my sentence or something, I wasn't saying your way wouldn't work, I was saying mine wouldn't without adding the xml - rather than using the "?textAppearanceLargeInverse "
lol, when I said it wouldn't work, it was a preface to the next part of my next sentence.
jellette said:
I think you put a comma in my sentence or something, I wasn't saying your way wouldn't work, I was saying mine wouldn't without adding the xml - rather than using the "?textAppearanceLargeInverse "
lol, when I said it wouldn't work, it was a preface to my next sentence.
Click to expand...
Click to collapse
Oh LOL, I just misinterpreted that whole conversation.
I'm going to slowly walk away. I should have never doubted your wisdom!
Edit:
lol, when I said it wouldn't work, it was a preface to the next part of my next sentence.
Click to expand...
Click to collapse
Yeah that's the part I misread lol
This is great. If I hadn't drank so much I'd start now. Thank you guys. Not going to lie, sounds foreign to me. Look forward to learning. Thank you both, so much
has anyone seen this thread?
http://forum.xda-developers.com/showthread.php?t=1057234
^ maybe I missed it, but that would only be helpful if you are on CM7 right?
I will try and make the changes birgertime suggested. That seems to make a lot more sense. Jellette, I am way too ignorant for you my friend.. and birgertime, he is just crazy patient with me, ha.
I don't mind publicly embarrassing myself, you guys are awesome.
What J did, Callip, was just make his own XML and define his own colors so he could just make calls to them and know exactly what they are.
Sent from my SGH-T959 using Tapatalk
0. INTRO
One of the only things I like about the US firmwares for our phones is that the dialer actually looks normal. Those of you using Hellraiser on int'l firmwares have probably thought wtf is this fugly mess? It just drives me crazy, so I decided to write a guide to removing the video call icon, and decribe the basics of modding the dialer layout. This is not particularly advanced, but I'm not getting into any apktool specifics, so you will need to be comfortable with that before you try this.
First things first, thank you to jivy26 and dully79 for helping me out with this! And of course to Brut.alll for apktool.
Let's take a close look at this thing:
{
"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"
}
Yup, you're supposed to make a call with that. Or a video call. Or a text message. Especially text message, because if you hit the menu button, you're presented with another way to text: 'Send message'.
</rant>
1. GET RID OF VIDEO CALL ICON
I don't think there's any way to activate it in the US, so let's get rid of it.
a. Get a clean copy of Contacts.apk from your favorite i9100 firmware. The one I'm using is from XWKL1.
b. Decompile.
c. Open up res/layout/dialer_app.xml in a text editor.
d. We will be working in the last LinearLayout entry, find it.
e. We will use android:visibility="gone" to get rid of the icon. You can see that voicemailbutton is hidden by default.
Code:
<LinearLayout android:orientation="horizontal" android:id="@id/dialbuttonset" android:layout_width="314.0dip" android:layout_height="54.669983dip" android:layout_marginTop="2.6599731dip">
<ImageButton android:id="@id/voicemailbutton" android:background="@drawable/call_dial_btn06" android:visibility="gone" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_voicemail_icon" />
<ImageButton android:id="@id/callbutton" android:background="@drawable/call_dial_btn01" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_outgoingcall_icon" android:scaleType="fitXY" android:contentDescription="@string/call" />
<ImageButton android:id="@id/videocallbutton" android:background="@drawable/call_dial_btn02" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_contacts_icon" android:scaleType="fitXY" android:contentDescription="@string/video_call" />
<ImageButton android:id="@id/messagebutton" android:background="@drawable/call_dial_btn03" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_message_icon_04" android:scaleType="fitXY" android:contentDescription="@string/message" />
<ImageButton android:id="@id/imageclear" android:background="@drawable/call_dial_btn06" android:nextFocusLeft="@id/messagebutton" android:nextFocusRight="@id/callbutton" android:layout_width="63.0dip" android:layout_height="52.899994dip" android:layout_marginLeft="6.0dip" android:layout_marginTop="1.0dip" android:src="@drawable/call_clear_btn_04" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
<ImageButton android:id="@id/messagebutton_novt" android:background="@drawable/call_dial_btn05" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_message_icon_03" android:scaleType="fitXY" android:contentDescription="@string/message" />
<ImageButton android:id="@id/imageclear_novt" android:background="@drawable/call_dial_btn06" android:layout_width="98.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_clear_btn_03" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
</LinearLayout>
f. Modify the relevant line by adding android:visibility="gone"
Code:
<ImageButton android:id="@id/videocallbutton" android:background="@drawable/call_dial_btn02" [COLOR="Blue"]android:visibility="gone"[/COLOR] android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_contacts_icon" android:scaleType="fitXY" android:contentDescription="@string/video_call" />
If you were to compile this now, it would look like this:
Got rid of the video call button, but we've introduced new fugliness courtesy of messagebutton_novt and imageclear_novt. I'm really not sure what those are, but they were "next in line" in our layout, and removing videocallbutton revealed them.
2. GET RID OF _NOVT BUTTONS
Who knows what these are, but the last thing we need is more buttons down here.
a. Apply android:visibility="gone" to the relevant lines:
Code:
<ImageButton android:id="@id/messagebutton_novt" android:background="@drawable/call_dial_btn05" [COLOR="Blue"]android:visibility="gone"[/COLOR] android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_message_icon_03" android:scaleType="fitXY" android:contentDescription="@string/message" />
<ImageButton android:id="@id/imageclear_novt" android:background="@drawable/call_dial_btn06" [COLOR="Blue"]android:visibility="gone"[/COLOR] android:layout_width="98.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_clear_btn_03" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
If you were to compile it at this point, it would look like this:
Getting warmer.
3. CHANGE THE ORDER
I want to have the call button in the middle, so we have to move it.
a. Swap the order of the entries so callbutton is between messagebutton and imageclear
Code:
<LinearLayout android:orientation="horizontal" android:id="@id/dialbuttonset" android:layout_width="314.0dip" android:layout_height="54.669983dip" android:layout_marginTop="2.6599731dip">
<ImageButton android:id="@id/voicemailbutton" android:background="@drawable/call_dial_btn06" android:visibility="gone" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_voicemail_icon" />
<ImageButton android:id="@id/videocallbutton" android:background="@drawable/call_dial_btn02" android:visibility="gone" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_contacts_icon" android:scaleType="fitXY" android:contentDescription="@string/video_call" />
<ImageButton android:id="@id/messagebutton" android:background="@drawable/call_dial_btn03" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_message_icon_04" android:scaleType="fitXY" android:contentDescription="@string/message" />
[COLOR="Blue"] <ImageButton android:id="@id/callbutton" android:background="@drawable/call_dial_btn01" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_outgoingcall_icon" android:scaleType="fitXY" android:contentDescription="@string/call" />[/COLOR]
<ImageButton android:id="@id/imageclear" android:background="@drawable/call_dial_btn06" android:nextFocusLeft="@id/messagebutton" android:nextFocusRight="@id/callbutton" android:layout_width="63.0dip" android:layout_height="52.899994dip" android:layout_marginLeft="6.0dip" android:layout_marginTop="1.0dip" android:src="@drawable/call_clear_btn_04" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
<ImageButton android:id="@id/messagebutton_novt" android:background="@drawable/call_dial_btn05" android:visibility="gone" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_message_icon_03" android:scaleType="fitXY" android:contentDescription="@string/message" />
<ImageButton android:id="@id/imageclear_novt" android:background="@drawable/call_dial_btn06" android:visibility="gone" android:layout_width="98.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_clear_btn_03" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
</LinearLayout>
So, here's what it would look like now:
Just have to align it
4. ALIGN IT
So there's many things you could do now. Stretching the message and clear icons to be the same width as the call button by setting android:layout_width="98.66998dip"would result in:
To fix the stretching, you could modify the referenced images. But for simplicity's sake, we are just going to pad the margins so that everything lines up.
a. change the margin of messagebutton to 41.66998dip.
Code:
<ImageButton android:id="@id/messagebutton" android:background="@drawable/call_dial_btn03" android:layout_width="63.0dip" android:layout_height="54.669983dip" [COLOR="Blue"]android:layout_marginLeft="41.66998dip"[/COLOR] android:src="@drawable/call_message_icon_04" android:scaleType="fitXY" android:contentDescription="@string/message" />
b. Wait, where did that number come from??
c. Since we want everything to line up, it's easy to figure out how far to "push" the message button to the left by looking at the layout of the number area of the dialpad in our xml.
Each button is 98.66998dip wide, preceded by a 6.0dip margin.
messagebutton is 63.0dip wide.
98.66998-63.0==35.66998
Add the original 6.0dip for the left margin==41.66998d. SIDE NOTE: If you are a perfectionist, you can also make 2 small changes to the imageclear entry at this point to bring the layout in line with the rest of the buttons.
i. Remove the section in red (below) from the imageclear entry. (No other button has a top margin)
ii. Change the android:layout_height to 54.669983dip, which is what the rest of the buttons use. I can't imagine why only this button would need a tiny top margin, and smaller height, making it a tiny bit smaller than all the rest of the buttons. Samsung goofiness.
Code:
<ImageButton android:id="@id/imageclear" android:background="@drawable/call_dial_btn06" android:nextFocusLeft="@id/messagebutton" android:nextFocusRight="@id/callbutton" android:layout_width="63.0dip" [COLOR="Blue"]android:layout_height="54.669983dip"[/COLOR] android:layout_marginLeft="6.0dip" [COLOR="Red"]android:layout_marginTop="1.0dip"[/COLOR] android:src="@drawable/call_clear_btn_04" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
e. Our final, modified section of xml will look like this:
Code:
<LinearLayout android:orientation="horizontal" android:id="@id/dialbuttonset" android:layout_width="314.0dip" android:layout_height="54.669983dip" android:layout_marginTop="2.6599731dip">
<ImageButton android:id="@id/voicemailbutton" android:background="@drawable/call_dial_btn06" android:visibility="gone" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_voicemail_icon" />
<ImageButton android:id="@id/videocallbutton" android:background="@drawable/call_dial_btn02" android:visibility="gone" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_contacts_icon" android:scaleType="fitXY" android:contentDescription="@string/video_call" />
<ImageButton android:id="@id/messagebutton" android:background="@drawable/call_dial_btn03" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="41.66998dip" android:src="@drawable/call_message_icon_04" android:scaleType="fitXY" android:contentDescription="@string/message" />
<ImageButton android:id="@id/callbutton" android:background="@drawable/call_dial_btn01" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_outgoingcall_icon" android:scaleType="fitXY" android:contentDescription="@string/call" />
<ImageButton android:id="@id/imageclear" android:background="@drawable/call_dial_btn06" android:nextFocusLeft="@id/messagebutton" android:nextFocusRight="@id/callbutton" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_clear_btn_04" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
<ImageButton android:id="@id/messagebutton_novt" android:background="@drawable/call_dial_btn05" android:visibility="gone" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_message_icon_03" android:scaleType="fitXY" android:contentDescription="@string/message" />
<ImageButton android:id="@id/imageclear_novt" android:background="@drawable/call_dial_btn06" android:visibility="gone" android:layout_width="98.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_clear_btn_03" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
</LinearLayout>
f. Compile and push to phone and it should look like this:
flashable VRTheme for i9100 firmwares!
This flashable VRTheme does the following:
1) Removes video call button.
2) Centers call button.
3) Replaces .pngs so that icons are not stretched.
Install:*
0) For international (i9100) 2.3.x firmwares only! Make sure the Contacts.apk is unthemed (stock).
1) Copy US_dialer_VRTheme.zip and VRTheme-Restore-Backup-v0.3.6.zip to your sdcard. Different kernels/versions of CWM recovery mount sdcard differently, so you might have to put it in sdcard/external_sd.
2) Flash from recovery.
3) Reboot. This wipes dalvik so please be patient. First boot can take 5 mins. or more.
*Tested on XWKL1 and XILA2 firmwares. It should work with almost any firmware version b/c the VRTheme just replaces the parts of the apk pertaining to the dialer. For unthemed ROMs only! If your ROM has a themed dialer, this will mess up the theme.
Revert:
0) The zip will automatically create a vrtheme-backup folder in the root of your sdcard in case something goes wrong.
1) Flash VRTheme-Restore-Backup-v0.3.6.zip from recovery.
If this works for people, please let me know what firmware you are on and I'll update the post with confirmed working versions.
NOTE: My phone is themed, so your tabs will look different (stock) as compared to the screenshot!
Thanks to:
VillainROM team for making this useful tool: http://forum.xda-developers.com/showthread.php?t=1207017
D.O.C. for modifications and restore scripts
screenshot:
Hopefully some devs will replace the default dialer. I would take a crack at it, but I have no experience. Tempting, however...
Going to give this a try now, thanks!
Ugh getting a bunch of compile errors, maybe cause its too late for me doing this...
Worked very nicely on LA4, awesome work my friend.
yoderk said:
Worked very nicely on LA4, awesome work my friend.
Click to expand...
Click to collapse
Great! I checked the xml against a couple of other firmwares and that part was all the same so I thought it should work. Good to have confirmation though.
AndAllThingsWillEnd said:
Hopefully some devs will replace the default dialer. I would take a crack at it, but I have no experience. Tempting, however...
Click to expand...
Click to collapse
Now you can do it yourself! Flashable zip in post 2.
Awesome! Thanks so much!
Sent from my AT&T cellular device.
Tried the zip file on xila3 and it did not remove video button. Also tried manually and failed last night. I will try manually again today. Can anyone upload the xila2 or xla4 stock contacts with this done already? I also tried grabbing the xila2 contacts from lilrom to see if i could modify it but then i lose the phone and contact buttons completely.
If someone else has better luck here is the stock contacts.apk for xila3 firmware. I still am not having any luck with getting rid of that damned video call button. http://db.tt/Fg3emi5O
Also here is my modified xila3 contacts.apk that i have already got most the things working except getting rid of the video button and resizing the buttons. The layout/dialer.app just doesn't open up correctly on notepad++ or on my phone. Same thing either way. I tried starting a layout/dialer.app from scratch but then i get a acore.process error and force close when i try to open the dialer after making the changes. http://db.tt/7KmD3fM4
Sent From My KickAss ATT SGS2 SPORTING CM7
RockRatt said:
Tried the zip file on xila3 and it did not remove video button. Also tried manually and failed last night. I will try manually again today. Can anyone upload the xila2 or xla4 stock contacts with this done already? I also tried grabbing the xila2 contacts from lilrom to see if i could modify it but then i lose the phone and contact buttons completely.
If someone else has better luck here is the stock contacts.apk for xila3 firmware. I still am not having any luck with getting rid of that damned video call button. http://db.tt/Fg3emi5O
Also here is my modified xila3 contacts.apk that i have already got most the things working except getting rid of the video button and resizing the buttons. The layout/dialer.app just doesn't open up correctly on notepad++ or on my phone. Same thing either way. I tried starting a layout/dialer.app from scratch but then i get a acore.process error and force close when i try to open the dialer after making the changes. http://db.tt/7KmD3fM4
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
Something is up. I tried to have a look at your modified apk and got an error saying archive could be damaged. Anyway, here's the XILA3 modded for you. I didn't use the apk from your link, so maybe there's something wrong with that file. idk anyway, enjoy
stone_ship said:
Something is up. I tried to have a look at your modified apk and got an error saying archive could be damaged. Anyway, here's the XILA3 modded for you. I didn't use the apk from your link, so maybe there's something wrong with that file. idk anyway, enjoy
Click to expand...
Click to collapse
A BIG THANKS for the help. I will add a link to your thread with a Thanks on my CobraRom Post. Wish I knew where I was messing up though. Here is the finished detail I was going for Thanks to you I am happy with it. Now to start messing with the Phone.ask file. Thanks again Rich
Sent From My KickAss ATT SGS2 SPORTING CM7
Stone_Ship since you know better than I, do you know where/what file I need to change to get rid of the phone.apk? Video call button as seen kn screen shot? I can deal with the first screenshot of the incall dialer but after I hit end call the second screen comes up that I would like to remove or change. I have been able to modify it to exactly my liking without the video call button and such and it works fine except when it goes back to the dialer i get a process.phone error and I lose my signal for a few seconds. Hope you can point me in the right direction.
Sent From My KickAss ATT SGS2 SPORTING CM7
RockRatt said:
Stone_Ship since you know better than I, do you know where/what file I need to change to get rid of the phone.apk? Video call button as seen kn screen shot? I can deal with the first screenshot of the incall dialer but after I hit end call the second screen comes up that I would like to remove or change. I have been able to modify it to exactly my liking without the video call button and such and it works fine except when it goes back to the dialer i get a process.phone error and I lose my signal for a few seconds. Hope you can point me in the right direction.
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
How did you get rid of the video call button? I tried the android:visibility=gone trick on endcall_buttons_view.xml but it did nothing. On the other hand, it didn't FC either. Let me know what you did and I'll try it out.
stone_ship said:
How did you get rid of the video call button? I tried the android:visibility=gone trick on endcall_buttons_view.xml but it did nothing. On the other hand, it didn't FC either. Let me know what you did and I'll try it out.
Click to expand...
Click to collapse
I am not sure how I got rid of the video call button from the first screen shot, I just changed out some of the icons with matching names but different pictures and then the video buttons would be gone. But then i would get the force close once i end the call. With the pics above where it still has the second screen with the video call button and the first screen without it I do not get a force close. Again I just have been trying to swap out some of the .png files is all. I can upload two different apk files if that would help. One with EVERYTHING I want it to be like without any video call buttons but the force close, and the other as the screen shots above that I get NO force closes after endimg call.
NoForceclose but has video button:
http://db.tt/kXzPVtbg
Like But Has force close after call.
http://db.tt/bL5VP5eo
Sent From My KickAss ATT SGS2 SPORTING CM7
RockRatt said:
I am not sure how I got rid of the video call button from the first screen shot, I just changed out some of the icons with matching names but different pictures and then the video buttons would be gone. But then i would get the force close once i end the call. With the pics above where it still has the second screen with the video call button and the first screen without it I do not get a force close. Again I just have been trying to swap out some of the .png files is all. I can upload two different apk files if that would help. One with EVERYTHING I want it to be like without any video call buttons but the force close, and the other as the screen shots above that I get NO force closes after endimg call.
NoForceclose but has video button:
http://db.tt/kXzPVtbg
Like But Has force close after call.
http://db.tt/bL5VP5eo
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
I tested both files on my phone running KL1 and neither gives me FCs. Like But Has Force Close doesn't even go to that Call ended screen. Kinda neat. Are your permissions messed up? They should be 644 (rw-r--r--).
I think you already have what you want in your hands, but just have to figure out where the problem is. Maybe fresh install from an unmodified firmware base?
stone_ship said:
I tested both files on my phone running KL1 and neither gives me FCs. Like But Has Force Close doesn't even go to that Call ended screen. Kinda neat. Are your permissions messed up? They should be 644 (rw-r--r--).
I think you already have what you want in your hands, but just have to figure out where the problem is. Maybe fresh install from an unmodified firmware base?
Click to expand...
Click to collapse
Ya I have put them in system/app with the correct rw/r/r and also just pushed them in without changing permissions then rebooted each time. I have run fix permissions from recovery and also tried via Rom manager also. I downloaded wanamlites version and started from scratcb and also sammys released version also, flashed it via mobile odin, put root explorer back on and pulled the whole system file, then started from scratch. I do not get the force close when i make a call but once i hit end call the screen sticks for a few seconds, then I get a popup that says force close. It loses cell signal completely for a few seconds then cell signal comes back on.
After reading your last message I tried tow other things also, one was to try and edit with notepad++ the endcall.view.xml to visibility=gone and also I totally deleted out the endcall_buttons_view.xml and endcall_buttons_view_land.xml which worked to completely get rid of the extra screen and went right back to the dialer but still gave the process.phone error message. Thanks for trying with me. I will keep testing it out.
Sent From My KickAss ATT SGS2 SPORTING CM7
Something strange is definitely going on. I did make a couple of test calls with no FCs. You can try running ddms to see if you can see what's causing the errors. I'm not very good at reading those, but if you post it, I bet someone can help.
Well i took the one I like already, went in and edited the endcall_button_view.xml for visibility=gone and tben zipped it back up. Applied it, then recreated my rom and installed the rom and nkw so far I am not getting the force close issue I was having. Weird, so far it works pretty much as I put the links to you above. I will test it out a bit more and see how it goes. THANKS again for the help and ideas.
Sent From My KickAss ATT SGS2 SPORTING CM7
Glad it worked out for you. Sounds like you basically short circuited the app so it can't show the call ended screen.
stone_ship said:
Glad it worked out for you. Sounds like you basically short circuited the app so it can't show the call ended screen.
Click to expand...
Click to collapse
I kind of like the way it turned out, thanks for the help and guidance man! I posted a link in the OP to point to your post. Thanks again, Rich
Sent From My KickAss ATT SGS2 SPORTING CM7
I have been helping Sinistertensai with his ShenduOS port for the HTC EVO 4G. I got Wimax to work and was wanting to see if anyone knows how to add a Wimax toggle to the power widget dropdown from the status bar. The port is CM7 based. In the SystemUI.apk I see there is WimaxButton.smali. I have tried adding the ids for it in public.xml and creating pngs for the toggle. I get no errors on compile but I get reboots or force closes when I try to bring up the power widget dropdown. I have very limited experience with editing smail code. I have also tried copying over the resources, classes, and xmls to the original apk with the same results. I have researched how to edit smali but I could just be doing it wrong or leaving something out. This has been driving me to madness. If anyone could help out that would be amazing!
Is there a reason you can't rebuild from source with Wimax enabled?
Sent from my SCH-R760 using Tapatalk 2
The ShenduOS SystemUI has been changed drastically and I cannot find the source code. That would require me to completely redo what Shendu has done and is well beyond my capabilities. The functionality for the wimax is there, I just need to find a way to add the toggle button. The actual widget has a wimax toggle which works, just not the one in the status bar.
Sent from my EVO using xda premium
I have only done smali a few times. How I did it was for example get a cm build going. Remove all wimax toggle related noti widget elements. Compile. Now you have a systemui base. Now build with the wimax toggle. You have a wimax toggle systemui.
Then use a program like beyond compare and after apktooling both systemui in their own folders. Compare the smali differences. Should get you pretty close. Of course there will be some trial and error if the systemui is different then that of cm.
Sent from my Galaxy Nexus using xda premium
The code is quite different that the CM7 code. I have found what needs to be edited, it just results in reboots upon clicking on the status bar to open the powerwidget dropdown. Here are the steps I take:
Decompile SystemUI.apk
In PowerWidget.smali -> replace both instances of toggleNetworkMode with toggleWimax
In WimaxButton.smali -> write down ids from method updateState (0x7f0200ca is off, 0x7f0200cb is on)
In public.xml -> Removed bad APKTOOL_DUMMYs for above ids. Add the following lines:
<public type="drawable" name="stat_wimax_off" id="0x7f0200ca" />
<public type="drawable" name="stat_wimax_on" id="0x7f0200cb" />
In res/drawable-hdpi -> Created on/off images and placed them there
In drawables.xml -> Removed bad APKTOOL_DUMMYs for above ids that were set to false. Add the following lines:
<item type="drawable" name="stat_wimax_off">true</item>
<item type="drawable" name="stat_wimax_on">true</item>
Recompiled
Pushed to phone with adb and cleared dalvik cache
Reboot
I have also tried pushing the changes and overwriting the ones in the original using Archive Manager(Ubuntu) with the same issues. If someone could point out what I am doing wrong that would help alot! I could have broken my tools(Android Utility/apktool). Feel free to give it a shot if you want. Once I/someone gets it right I will write up a tutorial.
Hello everyone,
I got Galaxy S5 running Lollipop. So far I have extracted SystemUI.apk and I have made some changes to Wifi/ Signal icons in my GS5 like making these look like Nexus 6. And Now I want to make my battery percentage text from white to black. I know to do it, we have to change some text in some XML file. But I can't find that file. So would anyone help me with this?
thanks
galaxyuser15 said:
Hello everyone,
I got Galaxy S5 running Lollipop. So far I have extracted SystemUI.apk and I have made some changes to Wifi/ Signal icons in my GS5 like making these look like Nexus 6. And Now I want to make my battery percentage text from white to black. I know to do it, we have to change some text in some XML file. But I can't find that file. So would anyone help me with this?
thanks
Click to expand...
Click to collapse
I haven't personally looked at it because I use 3minit battery. A good guess would be colors.xml in values folder or systemui? Not for sure though. There are a lot of color changes in there. Good luck!
If it is like JB...
You should go to res/layout/status_bar.xml (maybe its called "tw_staus_bar.xml") and find this line:
Code:
<TextView android:textSize="16.0sp" android:textColor="#ffffffff" android:id="@id/percentage" android:paddingLeft="4.0dip" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" />
You should change "android:textColor="#anycolour"" to the colour you want.
I hope this helps :good:
XDA Rule
galaxyuser15 said:
Hello everyone,
I got Galaxy S5 running Lollipop. So far I have extracted SystemUI.apk and I have made some changes to Wifi/ Signal icons in my GS5 like making these look like Nexus 6. And Now I want to make my battery percentage text from white to black. I know to do it, we have to change some text in some XML file. But I can't find that file. So would anyone help me with this?
thanks
Click to expand...
Click to collapse
Please post on the right forum.
Any questions you may have should be posted in this forum:
http://forum.xda-developers.com/galaxy-s5/help
#XDA Rule No. 15
All of the guides/methods/apps/mods I have read are out of date and do not work on the LG G2 since updating to Lollipop. I have tried xposed framework "Remove carrier" and this does also not work for me.
I have decompiled the framework-res.apk and had a look inside for the file "res/layout/keyguard_screen_tab_unlock.xml" as per this thread but it does not exist.
I can find the following though:
In "public.xml" the following lines:
<public type="string" name="keyguard_label_text" id="0x0104039c" />
<public type="string" name="lockscreen_carrier_default" id="0x0104039e" />
In strings.xml the following line:
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout androidrientation="vertical" android:background="#ff000000" androidaddingTop="20.0dip" androidaddingBottom="20.0dip" android:layout_width="wrap_content" android:layout_height="wrap_content" androidaddingStart="20.0dip" androidaddingEnd="20.0dip"
xmlns:android="http://schemas.android.com/apk/res/android">
<TextView android:textSize="16.0sp" android:textStyle="bold" android:textColor="#ffffffff" android:id="@id/label" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="@string/keyguard_label_text" />
</LinearLayout>
I wonder if I remove the 16.0sp above it will go away?
I wonder if I remove the string in quotes under the other two lines in public.xml it would go away.
Probably more to it than that.
I could not find reference to anything else anywhere that seemed like the place to affect it. It's not a big deal really. Just thought I would try to get rid of it.
just try textSize="0.0sp"
maybe in LGSystemUI?
Sorry the larger text section above was from the file named "keyguard.xml" rather than strings. Sorry, my mistake. I might try changing the "textsize=16.0sp" to "textsize=0.0sp" and see what happens.
Are you solved?
Hello, i've successfully removed the carrier and also moved the charging text right under the clock and date. You can check my thread in the themes section. I'll be releasing the version with the removed carrier and with some other nice things like unlocked weather animations, next alarm text etc in the coming day or two.
Sent from my LG-D802 using XDA Free mobile app
Is there any way to replace the text with a custom one without using xposed? And maybe in statusbar too.