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
Bummed that Asus took it out of the quick settings pop up menu as ill take that location over a crappy widget anyday. Anyone capable of getting it put back or do we need bootloader unlocked for such a hack/mod?
UPDATE: jump to page #2 to see the progress on getting this back
Guy...just add the quick settings widget onto your homescreen if you're that crazy over quick on/off for GPS.
Or instal from market beautifull widgets....and dont cry.
Wysłane z mojego Transformer Prime TF201 za pomocą Tapatalk
Tairen said:
Guy...just add the quick settings widget onto your homescreen if you're that crazy over quick on/off for GPS.
Click to expand...
Click to collapse
I'm not your guy buddy... and do you really think I needed you to tell me I could do this? Please.
And BTW it is the power control widget.... not a "quick settings widget" d'ohhh
We had it in HC & lost it in ICS... I simply want it back
mibo666 said:
Or instal from market beautifull widgets....and dont cry.
Wysłane z mojego Transformer Prime TF201 za pomocą Tapatalk
Click to expand...
Click to collapse
See above .. and with your recommendation you get the joy of using that lame widget just to get taken to the settings only to then have to click back or home. And then maybe the app - 2-3 clicks versus 1
Lock-N-Load said:
I'm not your guy buddy...
Click to expand...
Click to collapse
Bbbbllllhahahhahaa!!!!!! ROFL!!!
Sent from my CM7 Atrix 4G
Lock-N-Load said:
I'm not your guy buddy... and do you really think I needed you to tell me I could do this? Please.
And BTW it is the power control widget.... not a "quick settings widget" d'ohhh
We had it in HC & lost it in ICS... I simply want it back
Click to expand...
Click to collapse
I don't really give a flying ape **** what it's called. If you know then use it...guy.
Yo, why is everyone so sour in this thread? What's the deal?
http://youtu.be/ONqYuqWY8iM
AJC9000 said:
http://youtu.be/ONqYuqWY8iM
Click to expand...
Click to collapse
Suddenly, my life seems so much clearer.
It's just a simple question!
+1 for getting the gps button back.
Verstuurd van mijn Transformer Prime TF201 met Tapatalk
gruntguy said:
Yo, why is everyone so sour in this thread? What's the deal?
Click to expand...
Click to collapse
They are just hating for no logical reason. We had it, we lost it, it is a logical quick settings item, lets get it back. How can you hate on that?
The ironic thing is that using a widget is designed to help or aid or speed up a process.... well so is having it back in the quick settings menu but that gets hated on?
If I had the skill to address this I would have done it the day ICS rolled out as clearly they took it out of the quick settings menu as a step to sweep the GPS issues under the rug - out of sight out of mind.
GPS Checkbox findings. Will update this post as I find more
So this is what I have found so far regarding GPS Checkbox missing code. I have been comparing the ICS SystemUI XML files with the HC SystemUI XML files.
I have found 3 pieces of code that differ so far.
SystemUI/res/values/ids.xml
Code:
<item type="id" name="quick_settings_powersaving_checkbox">false</item>
<item type="id" name="quick_settings_powersaving_separator">false</item>
<item type="id" name="quick_settings_normalspeed_checkbox">false</item>
<item type="id" name="quick_settings_normalspeed_separator">false</item>
<item type="id" name="quick_settings_turbo_checkbox">false</item>
<item type="id" name="quick_settings_turbo_separator">false</item>
<item type="id" name="quick_settings_dev_checkbox">false</item>
<item type="id" name="quick_settings_autorotate_checkbox">false</item>
<item type="id" name="quick_settings_wifi_checkbox">false</item>
<item type="id" name="quick_settings_bluetooth_checkbox">false</item>
<item type="id" name="quick_settings_silent_checkbox">false</item>
<item type="id" name="quick_settings_autosync_checkbox">false</item>
[B] [SIZE="4"]<item type="id" name="quick_settings_gps_checkbox">false</item>[/SIZE]
[/B]<item type="id" name="quick_settings_airplane_separator">false</item>
<item type="id" name="quick_settings_airplane_checkbox">false</item>
<item type="id" name="quick_settings_wifisharing_separator">false</item>
<item type="id" name="quick_settings_wifisharing_checkbox">false</item>
SystemUI/res/values/public.xml
Code:
<public type="id" name="quick_settings_powersaving_checkbox" id="0x7f0f0077" />
<public type="id" name="quick_settings_powersaving_separator" id="0x7f0f0078" />
<public type="id" name="quick_settings_normalspeed_checkbox" id="0x7f0f0079" />
<public type="id" name="quick_settings_normalspeed_separator" id="0x7f0f007a" />
<public type="id" name="quick_settings_turbo_checkbox" id="0x7f0f007b" />
<public type="id" name="quick_settings_turbo_separator" id="0x7f0f007c" />
<public type="id" name="quick_settings_dev_checkbox" id="0x7f0f007d" />
<public type="id" name="quick_settings_autorotate_checkbox" id="0x7f0f007e" />
<public type="id" name="quick_settings_wifi_checkbox" id="0x7f0f007f" />
<public type="id" name="quick_settings_bluetooth_checkbox" id="0x7f0f0080" />
<public type="id" name="quick_settings_silent_checkbox" id="0x7f0f0081" />
<public type="id" name="quick_settings_autosync_checkbox" id="0x7f0f0082" />
<public type="id" name="quick_settings_airplane_separator" id="0x7f0f0083" />
<public type="id" name="quick_settings_airplane_checkbox" id="0x7f0f0084" />
<public type="id" name="quick_settings_wifisharing_separator" id="0x7f0f0085" />
<public type="id" name="quick_settings_wifisharing_checkbox" id="0x7f0f0086" />
[B][SIZE="4"]<public type="id" name="quick_settings_gps_checkbox" id="0x7f0f00b8" />[/SIZE][/B]
This one above is a tricky one as it needs the creation of a new ID. Currently I have it right at the end of the file which is why the ID does not follow exactly (there are about 800 lines of code in the whole file). In the HC file it follows directly after autosync checkbox line. This is the ID that I believe needs to be added somewhere into the smali code also. However I currently have no idea where it needs to go as I cannot find the IDs for the other checkbox references anywhere in any of the SystemUI smali code.
SystemUI/res/layout-sw600dp/status_bar_quick_settings_switch.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<com.android.systemui.statusbar.tablet.QuickSettingsSwitch android:orientation="vertical" android:background="@drawable/quick_settings_switch_bg" android:layout_width="fill_parent" android:layout_height="wrap_content"
xmlns:android="http://schemas.android.com/apk/res/android">
<com.android.systemui.statusbar.tablet.QuickSettingsHorizontalScrollView android:orientation="horizontal" android:id="@id/onoff_scroller" android:scrollbars="none" android:layout_width="fill_parent" android:layout_height="69.0dip">
<LinearLayout android:layout_width="wrap_content" android:layout_height="wrap_content">
<CheckBox android:id="@id/quick_settings_powersaving_checkbox" android:background="@drawable/asus_ep_control_onoff_powersaving" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:button="@null" />
<View android:id="@id/quick_settings_powersaving_separator" android:background="@drawable/asus_ep_sepline4" android:visibility="gone" android:layout_width="1.0dip" android:layout_height="wrap_content" />
<CheckBox android:id="@id/quick_settings_normalspeed_checkbox" android:background="@drawable/asus_ep_control_onoff_normalspeed" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:button="@null" />
<View android:id="@id/quick_settings_normalspeed_separator" android:background="@drawable/asus_ep_sepline4" android:visibility="gone" android:layout_width="1.0dip" android:layout_height="wrap_content" />
<CheckBox android:id="@id/quick_settings_turbo_checkbox" android:background="@drawable/asus_ep_control_onoff_turbo" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:button="@null" />
<View android:id="@id/quick_settings_turbo_separator" android:background="@drawable/asus_ep_sepline4" android:visibility="gone" android:layout_width="1.0dip" android:layout_height="wrap_content" />
<CheckBox android:id="@id/quick_settings_dev_checkbox" android:background="@drawable/asus_ep_control_onoff_development" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:button="@null" />
<View android:background="@drawable/asus_ep_sepline3" android:layout_width="1.0dip" android:layout_height="wrap_content" />
<CheckBox android:id="@id/quick_settings_autorotate_checkbox" android:background="@drawable/asus_ep_control_onoff_autorotate" android:layout_width="wrap_content" android:layout_height="wrap_content" android:button="@null" />
<View android:background="@drawable/asus_ep_sepline3" android:layout_width="1.0dip" android:layout_height="wrap_content" />
<CheckBox android:id="@id/quick_settings_wifi_checkbox" android:background="@drawable/asus_ep_control_onoff_wifi" android:layout_width="wrap_content" android:layout_height="wrap_content" android:button="@null" />
<View android:background="@drawable/asus_ep_sepline3" android:layout_width="1.0dip" android:layout_height="wrap_content" />
<CheckBox android:id="@id/quick_settings_bluetooth_checkbox" android:background="@drawable/asus_ep_control_onoff_bluetooth" android:layout_width="wrap_content" android:layout_height="wrap_content" android:button="@null" />
<View android:background="@drawable/asus_ep_sepline3" android:layout_width="1.0dip" android:layout_height="wrap_content" />
<CheckBox android:id="@id/quick_settings_silent_checkbox" android:background="@drawable/asus_ep_control_onoff_silent" android:layout_width="wrap_content" android:layout_height="wrap_content" android:button="@null" />
<View android:background="@drawable/asus_ep_sepline3" android:layout_width="1.0dip" android:layout_height="wrap_content" />
<CheckBox android:id="@id/quick_settings_autosync_checkbox" android:background="@drawable/asus_ep_control_onoff_autosync" android:layout_width="wrap_content" android:layout_height="wrap_content" android:button="@null" />
[B][SIZE="4"]<View android:background="@drawable/asus_ep_sepline3" android:layout_width="1.0dip" android:layout_height="wrap_content" />
<CheckBox android:id="@id/quick_settings_gps_checkbox" android:background="@drawable/asus_ep_control_onoff_gps" android:layout_width="wrap_content" android:layout_height="wrap_content" android:button="@null" />[/SIZE][/B]
<View android:id="@id/quick_settings_airplane_separator" android:background="@drawable/asus_ep_sepline3" android:visibility="gone" android:layout_width="1.0dip" android:layout_height="wrap_content" />
<CheckBox android:id="@id/quick_settings_airplane_checkbox" android:background="@drawable/asus_ep_control_onoff_flightmode" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:button="@null" />
<View android:id="@id/quick_settings_wifisharing_separator" android:background="@drawable/asus_ep_sepline3" android:visibility="gone" android:layout_width="1.0dip" android:layout_height="wrap_content" />
<CheckBox android:id="@id/quick_settings_wifisharing_checkbox" android:background="@drawable/asus_ep_control_onoff_wifisharing" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:button="@null" />
</LinearLayout>
</com.android.systemui.statusbar.tablet.QuickSettingsHorizontalScrollView>
</com.android.systemui.statusbar.tablet.QuickSettingsSwitch>
So these are my findings so far. From what I can see I think that these are the only 3 files in SystemUI that need this modification, other than the possible smali code addition, but that is gonna take a lot more research.
Unfortunately it seems that currently although we can decompile SystemUI.apk with apktool, even if we make no modifications we cannot recompile SystemUI.apk
So currently all this is very much theory, but I'm enjoying the research.
Thanks to Lock-N-Load for the original idea and the words of encouragement, and thanks to reNeglect for being so gracious to allow us to hijack his thread and for also helping with trying to recompile the file.
Stay tuned.
To update users coming in... Doktaphex and reNeglect and I have been tracking down a way to get the GPS icon back into the quick settings menu where it was before Asus nixed it from the ICS build for no other reason than to try to sweep the GPS issue under the rug. we high jacked reNeglect's thread on some other quick settings mods he has done, so now it is time to bring it back to this thread and give him back his thread
Doktaphex, by tediously comparing HC and ICS files, has found some references we believe are the code bits removed so as to remove that icon - that is what is above. We also found that the GPS quick settings icons - 3 of them - are still in the SystemUI - they have just been "turned off" so to speak from being seen and used.
So, right now, it is easy to make the changes to the above code lines, but we cannot yet compile and test under ICS. It is great progress and I have no doubt this will be cracked.
Man, I'd love to take a crack at this, but I'm a little wary of replacing system files without having recovery available. :/
Noxious Ninja said:
Man, I'd love to take a crack at this, but I'm a little wary of replacing system files without having recovery available. :/
Click to expand...
Click to collapse
The more brains on board the better. At the moment though just getting systemUI to recompile is a problem, so there's currently no danger in even trying to replace the file
However, reNeglect did have a nasty experience with trying to mod some framework stuff and getting a soft-brick. So I can understand your wariness.
Doktaphex said:
This one above is a tricky one as it needs the creation of a new ID. Currently I have it right at the end of the file which is why the ID does not follow exactly (there are about 800 lines of code in the whole file). In the HC file it follows directly after autosync checkbox line. This is the ID that I believe needs to be added somewhere into the smali code also. However I currently have no idea where it needs to go as I cannot find the IDs for the other checkbox references anywhere in any of the SystemUI smali code.
Click to expand...
Click to collapse
Do the other existing IDs in the ICS file all match the same call to the IDs in the HC file and that is where you got the ID for the GPS line? Or did you just make it up using logic as the next number? Point is, if the other IDs are the same across each file, it seems logical and stands to reason the same code and line and ID would be put in the ICS file.
Also, if you search the entire SystemUI for just 1 of those other IDs and it does not show up in any other file but that file I am not so sure that there then is another call out there in some file to that ID. If so, you think it is outside SystemUI?
Nope all IDs are completely different than the HC ones, and searching for any of the other IDs will take a while, as I think the only time they are referenced at all is in the smali code, have to open each file and then do a search inside that file. There are a shed load of them.
Damn.. okay here is an idea
Maybe how about look and see if the Moto Xoom ICS has a system dump yet and if it has these files and do a compare as that will be ICS to ICS? See how those differ? (I am about to see if I can do the same on the wpa_supplicant issue to get ad hoc support for tethering IF the dump is available yet.)
Lock-N-Load said:
Damn.. okay here is an idea
Maybe how about look and see if the Moto Xoom ICS has a system dump yet and if it has these files and do a compare as that will be ICS to ICS? See how those differ? (I am about to see if I can do the same on the wpa_supplicant issue to get ad hoc support for tethering IF the dump is available yet.)
Click to expand...
Click to collapse
The problem here is that those quicksettings checkboxes are exclusive to ASUS' UI enhancements, therefore they won't be referenced in any other builds from another manufacturer.
Doktaphex said:
The problem here is that those quicksettings checkboxes are exclusive to ASUS' UI enhancements, therefore they won't be referenced in any other builds from another manufacturer.
Click to expand...
Click to collapse
ahhh yeah.. damn, got ahead of myself. my bad.
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'm new to android development, so unsure if this is the best way to do what I want, so feel free to provide suggestions. What I want to do is simply just display some verbose text messages to the screen that will scroll and allow the user to slide up and down vertically so they can view any of the messages.
I've spent the past few days trying everything I can find on Google and I still have yet to get anything working. I have been able to successfully have the text display, append to the previous text, and scroll on its own. The common issue I have seen with my working implementations has been the ability of the user being able to scroll the vertical scroll-bars themselves. I have implemented the object properties in the xml, as well as in code, but neither have worked and I'm assuming it is just a noob mistake or some little thing i'm missing.
I have tried both a TextView as well as an EditText object. I have used them in Scrollviews, by themselves but nothing seems to work. I would prefer to use the EditText with scrollbars, but at this point I am up for anything that works. I am pasting what I have currently using the EditText. I have removed the scrollview below just to start with a simpler base.
If anyone has any ideas for what will solve my issue please let me know. I also have a device on order so I do not have the ability to try on hardware yet, so I am doing this all in the droid emulator. Unsure if that is a problem.
Code:
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="hxxp://schemas.android.com/apk/res/android"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:orientation="vertical" >
<EditText
android:id="@+id/path"
android:layout_width="fill_parent"
android:layout_height="wrap_content" />
<org.apache.android.media.CustomVideoView
android:id="@+id/custom_videoview"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_weight="3.33" />
<EditText
android:id="@+id/MessageText"
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:ems="10"
android:inputType="textMultiLine" android:layout_marginTop="100dp" android:scrollbars="vertical" android:fadeScrollbars="false" android:gravity="top" android:maxHeight="100dp" android:textSize="10sp">
<requestFocus />
</EditText>
</LinearLayout>
Is it possible to make any app a QSlide app either with or without a rooted device?
Good question. Would like to know this too. Same with dual window. Not all apps can be used with that either. Good thing itll be a native feature with android n.
TheJOJ said:
Is it possible to make any app a QSlide app either with or without a rooted device?
Click to expand...
Click to collapse
Needs something like this added to its manifest
Permission to overdraw added to it
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW" />
It needs to be made selectable within qslide
<application android:theme="null" android:label="App name" android:icon="app's data path to its icon.png"
Then made viewable in the launcher
<uses-library android:name="com.lge.app.floating" android:required="false" />
<activity android:label="App name" android:name="App name">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
No simple drag n drop method can add apps to qslide but possibly a batch editor could be made one day to pull it off on the fly...one day.