Database Info

[THEME DEVS][THEME-CHOOSER] New Mod standards[TAKE NOTE PLEASE]

So 2 rom teams. Savaged-Zen and Evervolv both by stock utilize the 6 bar and 100 battery mod in there themes. With the recent addition of Theme-Chooser in the roms, we've come together to make a standard for Theme Dev's to utilize these mods in their themes, and let the system be smart and know how to change it in the backend framework to properly use the mods.
To add a 6 bar mod or the 100 battery mod, add the images into the theme. and modify the below file
res/values/theme.xml
Code:
<resources>
<style name="Theme Name" parent="@android:style/Theme" />
//for signal mod set to true if not used you dont even need this line
<boolean name="extra_theme_compatibility_signal">true</boolean>
//for battery mod set to true if not used you dont even need this line
<boolean name="extra_theme_compatibility_battery">true</boolean>
</resources>

wow....i seriously cant figure out how to do this....thanks for the info tho....i never did this before so its all new to me.....im sure ill figure it out sooner or lata, cause it'll drive me crazy...thanks man

[GUIDE] Hide Status Bar and still being able to expand it on Jelly Bean

The purpose of this guide is to show you how to hide the status bar and still be able to swipe it down.
I've tested this guide on CYANOGENMOD10.1 with my galaxy nexus and everything works perfectly.
Tested and working on: cm10, cm10.1, paranoid android. Not tested but should work on: aokp and aosp roms.
On miui roms, it should be ok with some differences (watch here)
It should work also on other custom roms. I don't know if will work on htc,sony based roms (if you manage to make it working, please report).
If you are on a samsung based rom read the guide and also watch here
Some users reported that it works on ics too.
I don't know if this is going to work for tablets too (since they have the notification area and the buttons in the same bar).
I'm not a themer, i had to flash almost 50zips to make everything work.
what i mean is that if you will have problems, i might not be able to help you (especially with smali files).
If you are looking only for a transparent status bar watch HERE.
I made a short video to show you what this mod is about.
We will be using apktool, if you don't know how to use it, check HERE.
If you are having problems with apktool on ubuntu, THIS might help you.
How does it work:the status bar will still be there. it will be fully transparent, a bit smaller and it will not have anymore the reserved top space
it might look difficult, but you will only have to modify a few lines of code
--------------------------------------------------------------------------------------STEPS--------------------------------------------------------------------------------------
download your rom and extract SystemUI.apk and framework-res.apk
open the terminal/cmd (you will NEVER close it during the procedure) in the folder where you unpacked systemui and framework-res and type
Code:
apktool if framework-res.apk
Code:
apktool d framework-res.apk
this will create a framework-res folder.
open framework-res/res/values/dimens.xml and replace the line
Code:
<dimen name="status_bar_height">25.0dip</dimen>
with
Code:
<dimen name="status_bar_height">6.0dip</dimen>
you can choose a value between 1dip and 10dip (i suggest 2 to 5 dip). I personally use 2dip. If you can't swipe it down after the flash try with 10dip.
EDIT: if you want also a 0dip navbar modify the 3 lines below this one
save the file and close it
type in the terminal/cmd
Code:
apktool d SystemUI.apk
this will create a SystemUI folder
open SystemUI/res/values/drawables.xml and replace the line
Code:
<item type="drawable" name="status_bar_background">#ff000000</item>
with
Code:
<item type="drawable" name="status_bar_background">#00000000</item>
save and close
open SystemUI/res/layout/super_status_bar.xml and replace
Code:
<com.android.systemui.statusbar.phone.StatusBarWindowView android:background="@*android:color/transparent" android:focusable="true" android:fitsSystemWindows="true" android:descendantFocusability="afterDescendants"
with
Code:
<com.android.systemui.statusbar.phone.StatusBarWindowView android:background="#00000000" android:focusable="true" android:fitsSystemWindows="true" android:descendantFocusability="afterDescendants"
save and close
open SystemUI/res/layout/status_bar.xml and replace
Code:
<LinearLayout android:orientation="horizontal" android:id="@id/status_bar_contents" android:paddingLeft="6.0dip" android:paddingRight="6.0dip" android:layout_width="fill_parent" android:layout_height="fill_parent">
with
Code:
<LinearLayout android:orientation="horizontal" android:id="@id/status_bar_contents" android:paddingLeft="6.0dip" android:paddingRight="6.0dip" android:layout_width="0.0dip" android:layout_height="0.0dip">
then
Code:
<ImageSwitcher android:id="@id/tickerIcon" android:layout_width="@dimen/status_bar_icon_size" android:layout_height="@dimen/status_bar_icon_size" android:layout_marginRight="4.0dip">
with
Code:
<ImageSwitcher android:id="@id/tickerIcon" android:layout_width="0.0dip" android:layout_height="0.0dip" android:layout_marginRight="4.0dip">
and then
Code:
<com.android.systemui.statusbar.phone.TickerView android:id="@id/tickerText" android:paddingTop="2.0dip" android:paddingRight="10.0dip" android:layout_width="0.0dip" android:layout_height="wrap_content" android:layout_weight="1.0">
with
Code:
<com.android.systemui.statusbar.phone.TickerView android:id="@id/tickerText" android:paddingTop="2.0dip" android:paddingRight="10.0dip" android:layout_width="0.0dip" android:layout_height="0.0dip" android:layout_weight="1.0">
save and close
now open SystemUI/smali/com/android/systemui/statusbar/phone/PhoneStatusBar.smali
and search for
Code:
invoke-direct/range {v0 .. v5}, Landroid/view/WindowManager$LayoutParams;-><init>(IIIII)V
you will have 3 matches, the correct line should be right after
Code:
const/16 v3, 0x7d0
const v4, 0x800048
const/4 v5, -0x3
you have to replace
Code:
const/16 v3, 0x7d0
with
Code:
const/16 v3, 0x7d1
(with this change the status bar will not have anymore the reserved top space)
save and close
now you can recompile framework-res and systemui typing in the terminal/cmd
Code:
apktool b framework-res framework-res.apk
Code:
apktool b SystemUI SystemUI.apk
make a flashable zip with this 2 files (if you have problems flashing or when you reboot nothing has changed, use my zip attached below).
--------------------------------------------------------------------------------------DONE--------------------------------------------------------------------------------------
to revert back just flash the stock systemui and framework-res of your rom
You will have only one "bug", you will not to able to expand the status bar in the lockscreen.
If you are a themer and you know how to fix this, you are welcome.
You will avoid this bug using a lockscreen app like widgetlocker.
I use this mod along with notifier pro, a very useful app.
thank you for reading my guide

Re: [GUIDE] Hide Status Bar and still being able to expand it on CM10.1
Really nice, I will use this when 10.1 comes to my device
By the way, you made an error in your first sentence. It should say status bar instead of navbar.

thanks for the correction.
i checked and it works also on cm10.
i will update the title of the first post

Thanks for the guide, this helps me use the Sony Xperia launcher on CY10.1.............

very good tutorial. easy to understand and easy to do
worked fine. My Statusbar disappeared... But I can't swipe it Down
Any idea?^^
edit: i'm using Cm 10.1-20120121-NIGHTLY-i9300 and Next launcher 3D

halliba said:
very good tutorial. easy to understand and easy to do
worked fine. My Statusbar disappeared... But I can't swipe it Down
Any idea?^^
edit: i'm using Cm 10.1-20120121-NIGHTLY-i9300 and Next launcher 3D
Click to expand...
Click to collapse
Uhm, maybe you should set an higher status_bar_height? Try with 10dip.
Or you can even leave it to 25dip and test it to see if the problem is the small swipable area

enryea123 said:
Uhm, maybe you should set an higher status_bar_height? Try with 10dip.
Or you can even leave it to 25dip and test it to see if the problem is the small swipable area
Click to expand...
Click to collapse
works fine now. thanks

You're welcome

Why not add as an optional feature for cm10.1? It would be interesting to do it in full screen app slide down once for low to show the status bar and once again to open the notifications bar like this http://www.youtube.com/watch?v=ek-hq-lD1lw

Does this make it to where you can only swipe from a small area? because I use a setting in CM 10.1 to swipe down on the quicksetting already when you pull down from the right corner. I love that.
Does Apktool even work on Windows 8, I'm wanting to do this, but not quite prepared.
Another thought, Is there any way to do this only on the home screen? That's the only place it really really bothers me.
Also, You Signature is priceless.

I don't know anything about smali, is there any way to edit this from source ?

lukakas said:
Why not add as an optional feature for cm10.1? It would be interesting to do it in full screen app slide down once for low to show the status bar and once again to open the notifications bar like this http://www.youtube.com/watch?v=ek-hq-lD1lw
Click to expand...
Click to collapse
i would totally love that feature too, unfortunatly i'm absolutely not capable of doing it.
Edit: i think that it is not system wide. But just a launcher feature
Can't_Live_Without_My_Evo said:
Does this make it to where you can only swipe from a small area? because I use a setting in CM 10.1 to swipe down on the quicksetting already when you pull down from the right corner. I love that.
Does Apktool even work on Windows 8, I'm wanting to do this, but not quite prepared.
Another thought, Is there any way to do this only on the home screen? That's the only place it really really bothers me.
Also, You Signature is priceless.
Click to expand...
Click to collapse
yes it is 100% like if you have the status bar, if fact with this trick you will just make it absolutely trasparent (and a bit smaller). so you can swipe everywhere, swipe to the right to access quick toggles and double swipe to access quick toggles.
I can't tell you about windows 8 because i'm using linux, but it should be ok. I did not hear people complaining about apktool not working on W8.
About the homescreen, this trick works systemwide, so you should maybe try an alternative launcher (like apex) which allows to hide the status bar with a gesture
ahah i found my signature here
by the way: You know you are rooted when your up till 1.00am, looking on xda rather than watching porn
AnakTeKa said:
I don't know anything about smali, is there any way to edit this from source ?
Click to expand...
Click to collapse
i don't know anything about smali too , yes it is possible to do it from source but it would be more difficult. Morover to compile a cyanogenmod rom from source it took me 55 minutes (i have 12GB or ram and an intel i7 950)

Re: [GUIDE] Hide Status Bar and still being able to expand it on CM10/CM10.1
Hey, just wanted to let you know, this guide came up on xda news, and even Talk Android (or android talk, I don't remember ) congrats!
Sent from my Galaxy Nexus using xda premium

SahilC said:
Hey, just wanted to let you know, this guide came up on xda news, and even Talk Android (or android talk, I don't remember ) congrats!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thank you for reporting

Flashable zip for Galaxy R
Created a flashable zip for CM 10.1 (only for Galaxy R) to apply & revert this "Hide status bar" hack.
http://forum.xda-developers.com/showpost.php?p=37531377&postcount=1233

Thank you for this!Is there anyway you could tell me how do you just make the status bar transparent, with it still showing? Any ideas?All guides I've tried do not work on CM, systemUI just crashes with it.

Steam. said:
Thank you for this!Is there anyway you could tell me how do you just make the status bar transparent, with it still showing? Any ideas?All guides I've tried do not work on CM, systemUI just crashes with it.
Click to expand...
Click to collapse
I second this, I'd much rather have it transparent than gone.
I got the app notifier Pro though, Which is really polished and nice, I'm gonna do this procedure later on.

at the moment i'm not able to make an only transparent status bar (yea that's weird) but i'm working on it and i'll post a tutorial as soon as possible

Much like the new Sense status bar behaves would be amazing. It's just a regular status bar that's completely transparent behind it, but when you swipe down the drawer comes in from the very top as if it was normal, then completely hides away in the top edge but still has all the icons and time and everything there. It actually looks and works really nice! But it isn't AOSP

different way
i know another way to disable statusbar and expand it while it is hiding. firstly you should have a kind of rom that can apply expanded desktop feature then install an app which is called smart statusbar found in play store. that's all. thank you for your sharing btw

[MOD][GUIDE] Change Air Command Apps

Hello,
This is an update to a mod I previously posted in the T-Mobile Note 3 forums, that will allow you to open any apps you want with Air Command.
This mod assumes that you have working knowledge of how to decompile/recompile apk and jar files. If you do not know how to do so, there are several threads on XDA that will teach you. This is not one of them.
This mod is for Kit-Kat only. Lollipop version will be up tomorrow, and will appear in the second post.
***Before proceeding any further, MAKE A BACKUP***
***I am not responsible for any loss of data or damaged devices***
***resulting from this mod.***​
Did you make a backup? Good....
The file we are primarily going to be working with is services.jar, found in /system/framework, so go ahead and pull yours from your phone, and decompile it.
Once you have it decompiled, download the attached file, navigate to /com/android/server/smartclip/ in your decompiled services.jar, and replace the existing SpenGestureManagerService$6.smali with the one you just downloaded.
Now, open that file and scroll all the way to the bottom, where you will see this:
Code:
:pswitch_data_234
.packed-switch 0x0
:pswitch_43
:pswitch_b7
:pswitch_120
:pswitch_19d
:pswitch_1f8
.end packed-switch
.end method
Each switch in that array corresponds to one of the Air Command functions. By default, they are as follows:
switch_43 = ACTION MEMO
switch_b7 = SCRAP BOOKER
switch_120 = SCREEN WRITE
switch_19d = S-FINDER
switch_1f8 = PEN WINDOW
In order to use different apps, you must find the internal package name of the app that you want to use, and the default activity of the app. These can be found by decompiling said app, and looking at the AndroidManifest file.
Once you have both of those, search the new SPenGestureManagerService$6.smali for "YOUR_APP_NAME1" and "YOUR_APP_ACTIVITY1" and replace them with the package name and activity name, respectively.
Repeat this for any additional apps you wish to use, searching instead for "YOUR_APP_NAME2" and "YOUR_APP_ACTIVITY2". I have included these up to "YOUR_APP_NAME5" and "YOUR_APP_ACTIVITY5" for the sake of convenience.
Now, back to that array...
For every custom app you add, you must replace one of the existing switch numbers. For the first app, that you added the package name and activity for above, you will use:
Code:
:pswitch_ms1
For the second,
Code:
:pswitch_ms2
And so on, up to
Code:
:pswitch_ms5
You can use any combination of the original switches and custom ones, in any order you wish, but you cannot add any more than 5.
Once you have finished making any changes, recompile your services.jar, push it back to your device, and enjoy!
To change the icons, so they match the new apps, decompile your framework-res.apk, and go to res/drawable-xxhdpi. The icons will all begin with "airbutton_global_icon". Simply find the one(s)
corresponding to the app(s) you've changed, and edit it however you want. Just be sure to keep the file name the same.
To change the text that appears when you hover over the icon in Air Command, go to your decompiled framework-res.apk
and open res/values/strings.xml. Locate the one(s) you want to change, change the content of the string(s), save, recompile, push to system/priv-app, set permissions, and reboot.
***Note: You may have to change them in res/values-en-rUS/strings.xml also.

RESERVED

[GUIDE][MOD][APP] Modify chomp SMS to make it look exactly as SGY SMS app

Introduction (skip it if you are in a hurry )
Is it newer always better than older? not always indeed...
For example, the transition from Windows XP to Windows Vista, or from Windows 7 to 8 is been for many a move backward in terms of user experience and performance.
I would say that also the new *security* features inplemented starting with Android KitKat, that highly limited the usage of the external physical SDcard and introduced a quite confusing virtual/emulated internal SDcard, gave to many users who switched to the newer Android OS a number of problems and limitations they didn't have before.
Beside operative systems, also on the applications world, of course, sometimes an older app is better than a newer.
I, for example, can't get used to the new Messaging app look, that I found on my new phone, once I for years happily and comfortably used the Messaging app that was available on my *old* Samsung Galaxy Y (with Android GingerBread 2.3.6) which was optimized for a small screen and therefore very essential but still complete and able to provide a good user experience.
Some of us, smartphone users, would like that switching to a bigger screen phone from a smaller one, would give us the chance to have bigger text, menus, labels, so that everything can be read easier than on previous smaller phone...
But that doesn't seem what developers (who are eventually very young and so their sight is still very good ) usually think when they have a chance to deal with a bigger screen... they rather think that a bigger screen should give the opportunity to display more things, than the same things as previously but bigger.
So, moving from my old and beloved Samsung Galaxy Y, 3inch screen, to a new Cloudfone (asian brand) 4inch smartphone didn't make me any easier to read the texts on the screen, but instead I found the screen filled of new "things" and even "empty spaces" that honestly I don't really feel the need and I found very questionable their presence... (I think that sometimes developers are just like some journalists that are in need of a "scoop", and that if they don't have one, they will try to make it out of a normal news... the marketing department usually pressure the developers to "invent" new things, a "different look" whatever it is, so that they can sell it to the public as "new"... because... you know... new is better. So it doesn't matter if "new" is really "useful", as it doesn't matter if a "scoop" is really "real").
So I tried to find an alternative SMS app on Google Play store, that looked as close as possible like my old Messaging app.
I didn't find any that looked as I wanted by default, but I found that "chomp SMS" was very customizable, featuring many "theme" options (I especially liked the option to remove the contact pics, which most of the time are just a useless box with the contact initials) that made it possible to have it looked similar, even though not same, to my previous SMS app.
Yet, the waste of screen space for empty areas, and the formats of date and time labels and other details made me willing to use my reverse engineering skills to modify "chomp SMS" so that it looks perfectly same as the SMS app I was using before.
Here below I'll show you what I've done, what I modified and where, so that you too can do your modifications at your will, if you like to.
Let's start!
This is how the default Messaging app on both the phones, the old smaller, and the bigger new, looks like.
"Conversation List" view (first pic) and "Conversation" view (second pic)
.
I then found, on Google Play Store, and installed "chomp SMS", which by default looks like this.
.
I then went into Settings and used all the available options to customize the app look and this is the best that I've been able to achieve.
.
Compare the above with this screenshots of the SGY original Messaging app that we'll use as reference
.
From now on the only thing to do is to modify the app resources and code so...
first of all, you need to know how to decompile, compile and sign an Android app package.
If you don't know how, the simplest way to do it is to use APK Studio, a nice IDE (Integrated Development Environment) application, running on Windows and Linux, made by XDA developers member vaibhavpandeyvpz
Read this http://www.xda-developers.com/decompile-edit-and-recompile-in-one-tool-with-apk-studio/
Unfortunately such software might not work due to an older embedded version of APK Tool.
So, well... you might want to use the below attacched zip file that contains my own batch files together with the latest version of APK Tool (v2.1.0) that I downloaded from here http://ibotpeaches.github.io/Apktool/install/
Just download the zip and expand the archive in your C: disk.
You need to have at least Java Runtime Environment (JRE) ver. 1.8.0 installed (http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html)
Simply copy the apk file to that C:/Decompression.chamber folder and drag it over the apktool_decomp batch file and release, to get the apk decompiled.
As result you'll have a new folder in C:/Decompression.chamber with the same name of the decompiled apk.
To compile and sign just drag the folder over the apkt_BuildNsign batch file and release... if everything will be fine you'll find a new file named out.apk inside C:/Decompression.chamber and that's the compiled and signed apk.
Now, get the chomp SMS apk file and decompile it. (can be downloaded from here http://www.apk4fun.com/apk/1180/)
Now you are ready to modify the app same as I did (or on your own different way )
1) Let's get rid of that waste of screen space...
at the sides of the message box bubbles in Conversation view.
.
Looking on the layout folder (C:\Decompression.chamber\com.p1.chompsms-1\res\layout) we can find a file name message.xml that contains the description of the elements that are visualized on the Conversation view (how I found it? I don't remember I guess I just spot it by reading all the names of the files in the layout folder)
The message.xml file begins with this row:
Code:
<?xml version="1.0" encoding="utf-8"?>
<com.p1.chompsms.views.Message a:orientation="vertical" a:paddingLeft="2.0dip" a:padding ...
We can understand then that the contents of this layout is dynamically controller by a piece of code (a "class"), of name com.p1.chompsms.views.Message, that we can read by opening the related smali file, of name Message.smali, that we can find in (C:\Decompression.chamber\com.p1.chompsms-1\smali)\com\p1\chompsms\views.
By looking inside Message.smali we can find a few rows of code like this:
Code:
invoke-virtual {v2, v1, v3, v4, v5}, Landroid/widget/RelativeLayout$LayoutParams;->setMargins(IIII)V
Those rows, obviously, will set the message layout margins, that means the outer distance from the message box and the "container" the screen borders.
Few lines of code above, you can find a couple of "const"ants, means "fixed values"
Those constants are set by this code instructions
Code:
const/high16 v3, 0x428c0000 # 70.0f
That means that the value stored on "v3" is equal to 70.0 (floating point number).
Actually 70.0dpi is exactly the big "margin" that we want to remove.
There's also another margin, on the opposite side, which is much smaller (but still a waste) and it's set to only 2.0dpi by instructions const/high16 v1, 0x40000000.
In order to remove those margins we need to set to zero those constants by searching and replacing all the occurrences of 0x428c0000 and 0x4000000 with 0x00000000
If you wonder how can be 0x428c0000 equal to 70.0 give a look to this useful webpage http://www.h-schmidt.net/FloatConverter/IEEE754.html
Here's the result of this first modification.
(first pic is "before", second is "after")
.
.
2) Let's put the timestamp inside the message box bubble
The timestamp position is defined inside the message.xml layout file (already mentioned above) located in C:\Decompression.chamber\com.p1.chompsms-1\res\layout.
Having a look to that file we can see a reference to the timestamp at row number 4, above everything else, and identified by the attribute a:id="@id/message_date_label"
Code:
<TextView a:textAppearance="?historyDateTextAppearance" a:layout_gravity="center_horizontal" a:id="@id/message_date_label" a:paddingLeft=...
In order to have it inside and at the bottom of the message box, we have to move that line down, exactly under the line identified by the label a:id="@id/message_field" so that this:
Code:
<com.p1.chompsms.views.LinearLayoutWithOverlay a:layout_gravity="bottom" a:orientation="vertical" a:id="@id/message_view" ....
<TextView a:textAppearance="?historyMessageTextAppearance" a:autoLink="phone|email|web" a:id="@id/message_field" ...
<ViewStub a:layout_gravity="center_horizontal" a:id="@id/mms_layout_view_stub" ...
</com.p1.chompsms.views.LinearLayoutWithOverlay>
become this:
Code:
<com.p1.chompsms.views.LinearLayoutWithOverlay a:layout_gravity="bottom" a:orientation="vertical" a:id="@id/message_view" ...
<TextView a:textAppearance="?historyMessageTextAppearance" a:autoLink="phone|email|web" a:id="@id/message_field" ...
<TextView a:textAppearance="?historyDateTextAppearance" a:layout_gravity="right" a:id="@id/message_date_label" ...
<ViewStub a:layout_gravity="center_horizontal" a:id="@id/mms_layout_view_stub" ...
</com.p1.chompsms.views.LinearLayoutWithOverlay>
As in the original layout the timestamp is set to be positioned on the center of the screen, we also need to change the a:layout_gravity attribute from "center_horizontal" to "right" so that it will be positioned at the bottom/right of the message text.
Here's the result of the second modification (I changed the timestamp color to black using the app theme settings)
.
3) Let's change the timestamp date and time format
In my opinion the timestamp format that chomp SMS developer had chosen is unnecessarily too long and a not immediately clear as in the Messaging app of the SGY.
Unfortunately find where in the app is defined the date and time format of the timestamp isn't that easy because the chomp SMS developer(s) didn't link the format to any "style" or attr or string or anything that can be found in the "values" folder within the "res" (resources) folder; instead the format is "set" in the programmig code, somewhere, in one of the 4143 smali files
Anyway the code must be "called" by Message.smali (mentioned above) somewhere as that's the part of the app that handle the contents of the Conversation view, including the timestamp.
By searching for the id message_date_label (which refers to the timestamp textview inside message.xml layout) inside Message.smali and for "date" I then found the method setDate(J)V
Code:
.method public setDate(J)V
.locals 3
.prologue
.line 264
iget-object v0, p0, Lcom/p1/chompsms/views/Message;->m:Landroid/widget/TextView;
new-instance v1, Ljava/util/Date;
invoke-direct {v1, p1, p2}, Ljava/util/Date;-><init>(J)V
iget-object v2, p0, Lcom/p1/chompsms/views/Message;->c:Landroid/content/Context;
invoke-static {v1, v2}, Lcom/p1/chompsms/util/cd;->b(Ljava/util/Date;Landroid/content/Context;)Ljava/lang/String;
move-result-object v1
invoke-virtual {v0, v1}, Landroid/widget/TextView;->setText(Ljava/lang/CharSequence;)V
.line 265
return-void
.end method
Here we can see that "m", which earlier is been initialized as a pointer to the timestamp view, is read (iget-object) and stored in v0, then an object "date" and the object "c" are passed to a method "b" defined in com/p1/chompsms/util/cd that will return a "text" (stored in v1) that will be set (with setText) in v0, the timestamp view!
So we need to look at the code of (C:\Decompression.chamber\com.p1.chompsms-1\smali)\com\p1\chompsms\util\cd.smali.
In cd.smali, at the part of the code related to .method public static b(Ljava/util/Date;Landroid/content/Context called by setDate in Message.smali, we can find the instructions that are executed to "build" the timestamp string, with a space (const-string v1, " ") used as junction of the date and the time part of the timestamp text.... bingo!
So now we know that is inside cd.smali that the timestamp is "build"... but unfortunately the code there doesn't use any "string" to format the date and time but, instead, it just call/uses the standard format provided by the operative system
So things are getting more complicated.
In order to change the date and time format we actually need to add some "new" code in cd.smali that will set the format in the way we want.
Here is the code I've added.
In the beginning section # static fields I've added the following that define a couple of additional objetcs containers, "i" and "l" (l like lima)
Code:
.field private static final i:Ljava/text/SimpleDateFormat;
.field private static final l:Ljava/text/SimpleDateFormat;
More down after the marker .line 45 and the instruction
Code:
sput-object v0, Lcom/p1/chompsms/util/cd;->h:Ljava/text/SimpleDateFormat;
I've added the following that stores on "i" and "m" two different formats, one for the time and the other for the date
Code:
.line 99967
new-instance v0, Ljava/text/SimpleDateFormat;
const-string v1, "h:mma"
invoke-direct {v0, v1}, Ljava/text/SimpleDateFormat;-><init>(Ljava/lang/String;)V
sput-object v0, Lcom/p1/chompsms/util/cd;->i:Ljava/text/SimpleDateFormat;
new-instance v0, Ljava/text/SimpleDateFormat;
const-string v1, "d MMM"
invoke-direct {v0, v1}, Ljava/text/SimpleDateFormat;-><init>(Ljava/lang/String;)V
sput-object v0, Lcom/p1/chompsms/util/cd;->l:Ljava/text/SimpleDateFormat;
I then added the following code (which read the format from "i" and apply it to the date stored in p0) inside .method public static b(Ljava/util/Date;Landroid/content/Context
Code:
.line 999388
sget-object v1, Lcom/p1/chompsms/util/cd;->i:Ljava/text/SimpleDateFormat;
invoke-virtual {v1, p0}, Ljava/text/SimpleDateFormat;->format(Ljava/util/Date;)Ljava/lang/String;
move-result-object v1
.line 999395
which goes right above before this:
Code:
invoke-virtual {v0, v1}, Ljava/lang/StringBuilder;->append(Ljava/lang/String;)Ljava/lang/StringBuilder;
move-result-object v0
const-string v1, " "
then const-string v1, " " is been replaced with const-string v1, ", " (I added a comma)
More down, six lines down from const-string v1, ", " , soon after this
Code:
invoke-virtual {v1, p0}, Ljava/text/DateFormat;->format(Ljava/util/Date;)Ljava/lang/String;
move-result-object v1
I've added the following:
Code:
.line 999415
sget-object v1, Lcom/p1/chompsms/util/cd;->l:Ljava/text/SimpleDateFormat;
invoke-virtual {v1, p0}, Ljava/text/SimpleDateFormat;->format(Ljava/util/Date;)Ljava/lang/String;
move-result-object v1
.line 999422
And here is the result of all those modifications...
.
not bad ah?
4) Let's change the bubble style and make it same as in the SGY Messaging app
chomp SMS provides a number of different message box "bubble" styles but in my opinion non of them has the same nice proportions of corners radius and "tail" as seen in the SGY Messaging app.
The bubble styles are actually defined by some related images that are part of the app resources and are saved on (C:\Decompression.chamber\com.p1.chompsms-1\res)\drawable-????-v4, where ???? is anything like ldpi, mdpi, hdpi, etc...
What we need to do is to get the 9.patch (resizable) images from the SGY Messaging apk and save them in the chomp SMS resource folder with the same name of the images that are related to the chomp SMS bubble style that we want to replace
So, first we need to find the images on the SGY Messaging app.
We need to get the apk from an SGY stock firmware... actually the apk name isn't Messaging but Mms .apk. Once we have the apk we need to decompile it and look inside the res folder for any "drawable-????-v4" folder, then using the preview, scroll all the images till one that looks similar to the bubble style is found.
Here is what I've found in (C:\Decompression.chamber\Mms)\res\drawable-ldpi-v4
.
.
.
The images names are respectively: message_bubble_readmessage.9.png, message_bubble_readmessage_selected.9.png, message_bubble_sentmessage.9.png, message_bubble_sentmessage_selected.9.png
This images are very small, and indeed belong the "ldpi" drawable group, that is meant to be used on small screen devices; they can be used on phones with bigger screen too, but they will be scaled up and therefore the image will result blurred along the borders.
These are the images that I found that are related to one of the bubble styles available in chomp SMS and that I chose as the ones that will be replaced.
.
.
.
The images names are respectively,incoming_bubble_matte_retina.9.png, incoming_bubble_matte_retina_selected.9.png, outgoing_bubble_matte_retina.9.png, outgoing_bubble_matte_retina_selected.9.png
These images are available in both mdpi and hdpi versions so their "quality", their resolution is higher than the one available on the SGY Messaging app.
As we are going to copy the SGY Messaging app images in the (C:\Decompression.chamber\com.p1.chompsms-1)\res\drawable-ldpi-v4 folder of decompiled chomp SMS (it has to be the ldpi folder because is the one that match with the size of the images) but the chomp original images are in the mdpi and hdpi folders, we need to delete the original images so chomp SMS app is "forced" to get the images from the ldpi folder.
Then the images from the SGY Messaging app, once copied on the ldpi folder of chomp SMS, they need to be renamed with the same names of the original chomp SMS images, so that chomp SMS app can find them
Here is the final result of the images substitutions (bubble style selector, before and after)
.
Conversation view scaled to be comparable in real size with the screen of SGY
.
5) Let's fix padding and margins in Conversation view
As you might have observed on the above screenshot the relative position of the text inside the message box isn't optimal and anyway doesn't match at all with our reference, the SGY Messaging app.
Also the bubble round corners are clearly blurred due to the low resolution of the 9.patch (resizable) images taken from the SGY Messaging apk.
In order to fix this we need to adjust the 9.patch borders lines that "controls" the padding, the distance between the inside message text and the bubble image borders.
There's also need to make new, bigger size images so that a better quality "bubble" image can be displayed.
Additionally some paddings attributes related to the Conversation view, have to be adjusted.
So here is the old (the first on the left) and the *new* images.
.
.
.
.
.
.
As you might observe the fix of the padding has been done by changing the lenght of the bottom and right/vertical borders black lines (more on that can be read here https://developer.android.com/guide/topics/graphics/2d-graphics.html#nine-patch )
The bigger size images had to be made from scratch (I used GIMP as image editing application) using the original small as a reference. The tricky part was to properly reproduce the transparency (alpha channel) and the shadow.
The bigger images have exactly double the size as the original small one.
According to the Android developers documentations, ldpi images size relative factor is 0.75, mdpi is 1.0 and hdpi is 1.5, so that means that hdpi is 2.0 times than ldpi. By doubling the original small ldpi size the obtained image is suitable to be saved on the hdpi resources folder (C:\Decompression.chamber\com.p1.chompsms-1)\res\drawable-hdpi-v4; if the device is mdpi it will just scale down (by 0.66 factor) the hdpi image, but scaling down is much better than scaling up as it doesn't blur the image.
As the original chomp SMS hdpi versions of the bubble images have been already deleted, saving the new version on that folder won't be a file replacement, but it would have been if we didn't previously deleted the orginal images.
Padding and margins of message box and Conversation layout is also controlled by some values stored in (C:\Decompression.chamber\com.p1.chompsms-1)\res\layout\styles.xml; specifically this:
Code:
<style name="conversation_messageBubbles">
<item name="android:paddingLeft">3.0dip</item>
<item name="android:paddingRight">3.0dip</item>
The value of 3.0 has to be changed to 0.0
Also on (C:\Decompression.chamber\com.p1.chompsms-1)\res\layout\message.xml (that has been modified already above)
Change the attributes values according to this:
On row
Code:
<com.p1.chompsms.views.Message a:orientation="vertical"...
change:
paddingLeft="2.0dip" to 0.0
paddingRight="2.0dip" to 0.0
paddingBottom="8.0dip" to 6.0
On row
Code:
<LinearLayout a:orientation="horizontal" a:id="@id/message_view_wrapper" ...
change:
layout_marginBottom="4.0dip" to 0.0
On row
Code:
<TextView a:textAppearance="?historyDateTextAppearance" a:layout_gravity="right" a:id="@id/message_date_label" ...
replace:
layout_marginBottom="4.0dip" with layout_marginTop="3.0dip"
Once again, here is the achieved result...
.
Above: Conversation view scaled to be comparable in real size with the screen of SGY
Below: Close up of message bubble, before and after
.
Very close to perfect... isn't it?
The tutorial will continue on the following post...

6) Let's customize the "action bar"
The contact number shown in the action bar below the contact name is so ridiculously small that it can't be easily read, especially because a sequence of number is less likely to be visually recognized than a word that have "patterns" that our brain can use to recognize it.
Unfortunately chomp SMS, among the many theme settings, doesn't provide any related to the action bar contents, apart from the color.
So, once again, we need to find out where, in the app resources or code, are saved the values that controls the action bar contents appearance.
Looking at the content of the layout folder we can find a file named conversation.xml that likely will contain the description of the layout of the Conversation view and possibily has a reference to the action bar.
Indeed we can find, at row 5, the following
Code:
<FrameLayout a:id="@id/conversation_header_holder" a:background="?fakeActionBarBackground"
Still in layout folder we can find another file that might be related, with name action_bar_holder.xml
here we see that the second row contains this attribute
Code:
layout_height="?initialActionbarHeight"
The question mark tell use that the value is saved in the styles.xml files which can be found in (C:\Decompression.chamber\com.p1.chompsms-1)\values
Opening styles.xml file and searching for "initialActionbarHeight" we'll find the following:
Code:
<item name="initialActionbarHeight">@dimen/actionbar_height</item>
That means that the value of initialActionbarHeight is saved in dimens.xml file that can be found in the same value folder as styles.xml is.
Opening dimens.xml and searching for actionbar_height we'll find this:
Code:
<dimen name="actionbar_height">48.0dip</dimen>
bingo!
So, let's make the action bar bigger... let's change 48.0 in 52.0
Searching for "actionbar" inside styles.xml we can find a number of styles and values but with some analysis and trial and error attempts you can realize that styles that has "convo_actionbar_customview" in their name are the ones relevant.
Among them the follow two are the one that we are looking for:
Code:
<style name="convo_actionbar_customview_title" parent="@style/ActionBarTitle">
<item name="android:ellipsize">end</item>
<item name="android:layout_width">wrap_content</item>
<item name="android:maxLines">1</item>
Code:
<style name="convo_actionbar_customview_subtitle" parent="@style/ActionBarTitle">
<item name="android:textSize">12.0sp</item>
<item name="android:ellipsize">end</item>
<item name="android:layout_width">wrap_content</item>
<item name="android:layout_height">wrap_content</item>
<item name="android:maxLines">1</item>
Here we can see that the subtitle (which actually is the contact phone number, while the title is the contact name) has a textSize of 12.0sp... to have it bigger we need to, well... you know what!
Let's change it to 16.0sp and set a bit of free space at the bottom, to have it more vertically centered on the action bar, by adding the following line to the style
Code:
<item name="android:paddingBottom">3.0dip</item>
The convo_actionbar_customview_title style doesn't define its own textSize value, so it will just use the one set on the "parent" stlye ActionBarTitle, which is 18.0dip
Code:
<style name="ActionBarTitle" parent="@android:style/TextAppearance.Holo.Widget.ActionBar.Title">
<item name="android:textSize">18.0dip</item>
I tried to change it to 20.0dip but it turned out that the textSize changed only if the contact name was displayed alone without the phone number (without subtitle), but if the number is shown then the contact name text size was as small as the original.
Doing some more searches in the the styles.xml file I then found the following line that belong the definition of the DefaultTheme style.
Code:
<item name="convo_actionbar_customview_title_with_subtitle_textsize">@dimen/convo_actionbar_customview_title_with_subtitle_textsize</item>
That line tells us that the dimension of the phone number is saved in dimens.xml file (already mentioned above) and indeed there we can find this:
Code:
<dimen name="convo_actionbar_customview_title_with_subtitle_textsize">16.0dip</dimen>
By replacing the value of 16.0dip with 20.0dip, the contact name will become bigger and easier to read.
:highfive:
I've observed that there's a glitch on how the ellipsis (the shortening of a text with addition of the theree dots) is applied to the contact name... it's sometimes much shorter than the available space.
I found out that the glitch is fixed if the singleLine attribute is enabled.
So let's add the following line to the convo_actionbar_customview_title style.
Code:
<item name="android:singleLine">true</item>
As last thing I wanted to remove the call button on the action bar because it has appened more than once that while I had the phone on my pants pocket and the screen was unlocked (forgot to lock) then accidentally the call button was touched and a phone call initiated without me being aware of it.
To find where in the app is defined the visualization of the call button, I started with a search for word "call" inside all the files existing in the chomp SMS decompiled app folder (C:\Decompression.chamber\com.p1.chompsms-1)
I then found that the button icon image is saved as ic_call_icon.png both on xhdpi and and xxxhdpi drawable folders.
Searching for ic_call_icon text inside all the files, I found a layout name ic_call_icon_wrapper.xml that contain a reference to that image.
Searching for ic_call_icon_wrapper, I found a smali file, (C:\Decompression.chamber\com.p1.chompsms-1)\smali\com/p1/chompsms/activities/Conversation.smali that contain a reference to ic_call_icon_wrapper layout.
At line 8510 of Conversation.smali, inside .method public onCreateOptionsMenu(Landroid/view/Menu we can find
Code:
sget v2, Lcom/p1/chompsms/s$f;->ic_call_icon_wrapper:I
by analyzing the code a little above and below that row it's possible to spot the "section" that actually initialize the button and attach to it an "intent" the "action" to initiate a call.
To avoid the button to be displayed we can set a jump in the code that will make the execution to bypass that section.
So here it is how to add the jump:
After
Code:
.line 822
invoke-static {}, Lcom/p1/chompsms/util/Util;->g()Z
move-result v0
if-eqz v0, :cond_2
add
Code:
.line 9998500
goto :goto_9998531
Before
Code:
.line 830
const/16 v1, 0xd
add
Code:
:goto_9998531
And now... as usual... the final result!
.
Before... after
That's more than enough for what concern the Conversation view... mission accomplished!
7) Let's "fix" the "Conversation list", the "main" view, layout
Let's have again a look at the chomp SMS conversations and compare it to the SGY Messaging app.
.
First of all I don't understand why the date should be on the same line of the contact name thus shorting it, instead of being on the same line of the message preview as it is in the old SGY Messaging app.
Secondly... I don't like that date format! :silly:
So... let's fix it.
As usual the first thing to do is to find the layout file, or smali file that control the appearance of the conversation list view.
The first guess is the layout file main.xml in res\layout folder.
It indeed contains some references to a few parts of the view, but not in detail the parts that we are looking to modify, which are eventually described on another layout file.
Scrolling the files in layout folder another one seems very promising by its name: conversation_row.xml
Found! bingo!
in conversation_row.xml there' are clear references to the contact name, message row, and date
Here is the related lines
For contact name and date
Code:
<com.p1.chompsms.activities.search.SearchResultTextView a:id="@id/person_label" ...
<com.p1.chompsms.views.TextViewWithEllipsesFix a:id="@id/date_label"...
For message text
Code:
<com.p1.chompsms.activities.search.SearchResultTextView a:id="@id/subject_label"
The textview id attributes (id/person_label, id/subject_label, id/date_label) makes it very sure that those lines are the one that controls the positions of contact name, message text, and date.
So, in order to change the relative positions we just have to properly move those lines within the layout
Let's cut the date_label TextView line and paste it right below the subject_label TextView line, so that it looks like this
Code:
<LinearLayout a:orientation="horizontal" a:layout_width="fill_parent" a:layout_height="wrap_content">
<com.p1.chompsms.activities.search.SearchResultTextView a:id="@id/subject_label"...
<com.p1.chompsms.views.TextViewWithEllipsesFix a:id="@id/date_label" ...
<ImageView a:layout_gravity="bottom" a:id="@id/pinned_marker"...
That's enough to move the date from the above line with the contact name to the below line with the message text.
But we can see that in the same line of the date, now (actually at the right of the date) there's the placeholder for the image that is used to a conversation row as "pinned".
The three objects, message text, date and marker are listed in three rows one below the other, but they will actually be displayed on one horizontal row, one next the other, as the LinearLayout they belong is set as orientation="horizontal".
Is better to move the pinned marker on the same row of the contact name, so... cut and paste right below the person_label TextView line, so that it looks like this
Code:
<LinearLayout a:orientation="horizontal" a:layout_marginTop="-3.0dip" ...
<com.p1.chompsms.views.BaseLineImageView a:id="@id/unread_marker"...
<com.p1.chompsms.views.BaseLineImageView a:id="@id/no_notification"...
<com.p1.chompsms.activities.search.SearchResultTextView a:id="@id/person_label"...
<ImageView a:layout_gravity="bottom" a:id="@id/pinned_marker"...
Ok, that's done
Now the "hard" part... the modification of date formatting.
To find where in the 1672 smali files contained in (C:\Decompression.chamber\com.p1.chompsms-1)\smali\com\p1\chompsms is the piece of code that set the date format we can try to trace back the chain starting from the conversation_row.xml layout.
Here we see that the date TextView contents is "controlled" by com.p1.chompsms.views.TextViewWithEllipsesFix that can be found and read as a smali file of name TextViewWithEllipsesFix.smali saved in (C:\Decompression.chamber\com.p1.chompsms-1)\smali\com\p1\chompsms\views
Giving a look at the code of that smali file doesn't show anything related to the date format, so it means that there must be another place, another smali file, that does the date formatting and then pass the result to TextViewWithEllipsesFix; we need to find any smali file that has inside a call to TextViewWithEllipsesFix.
Unfortunately, there's not even one smali file that contains a reference to Lcom/p1/chompsms/views/TextViewWithEllipsesFix in order to pass some data to it or call any of its method.
Eventually the code we are looking for is in (C:\Decompression.chamber\com.p1.chompsms-1)\smali\com\p1\chompsms\views\ConversationRow.smali that is defined in conversation_row.xml layout as the root view, the main container.
By reading the contents of ConversationRow.smali, we can see that at the beginning is defined a variable "p" made to contain a date object
Code:
.field private p:Ljava/util/Date;
A few line below, inside the .method public constructor, the "date" , received by as argument p0, is saved in "p".
Code:
iput-object v0, p0, Lcom/p1/chompsms/views/ConversationRow;->p:Ljava/util/Date;
Searching for the string "->p:Ljava/util/Date" we can see that "p" is used only in the .method public final b(J)Ljava/util/Date;
The method "b(J)Ljava/util/Date" isn't called anywhere within ConversationRow.smali, so the parameters it receives and the results it returns must be related to some code in some other smali file.
Searching the whole chomp SMS smali folder for files containing the string "b(J)Ljava/util/Date" gave me as result two files:
com/p1/chompsms/activities/conversationlist/ConversationList$a.smali
com/p1/chompsms/activities/search/a.smali
In a.smali, in .method public final bindView, at row 171 there's the call to method "b(J)"
Code:
invoke-virtual {v3, v4, v5}, Lcom/p1/chompsms/views/ConversationRow;->b(J)Ljava/util/Date;
The result of the call, supposedly it's a date or time, is then saved to v4, then v5 and v9 are set to numeric value "1", then v0 is set equal to p2 (a parameter received by the bindView method) then v4, v0, v5, v9 are all used to make a call to method a(Ljava/util/Date;Landroid/content/Context;ZZ)Ljava/lang/String defined in com\p1\chompsms\util\cd.smali
Code:
invoke-static {v4, v0, v5, v9}, Lcom/p1/chompsms/util/cd;->a(Ljava/util/Date;Landroid/content/Context;ZZ)Ljava/lang/String;
util\cd.smali ?
But that's the same cd.smali that we had to modify earlier to change the format of time and date in the conversation message timestamp!
Let's have a look to method "a(Ljava/util/Date;Landroid/content..." in cd.smali
The method is quite long, but it's clear that is doing some kind of operations on the date that it has received when is been called by a.smali, which has received the date from method "b" in conversation_row.smali.
The "a" method calls the calendar
Code:
invoke-virtual {v2, v3}, Ljava/util/Calendar;->get(I)I
in order to know how many days are past from the given date and the present time.
It then choose if in place of a "text" containing a formatted date it has to return a string like "today" or "yesterday"
Code:
.line 78
:cond_1
sget v0, Lcom/p1/chompsms/s$l;->today:I
Code:
.line 82
sget v0, Lcom/p1/chompsms/s$l;->yesterday:I
But if it's not the case for "today" or "yesterday", but still the given date isn't past than more than three days, than the method code will format the date using the SimpleDateFormat stored in "a" variable!
Code:
sget-object v0, Lcom/p1/chompsms/util/cd;->a:Ljava/text/SimpleDateFormat;
invoke-virtual {v0, p0}, Ljava/text/SimpleDateFormat;->format(Ljava/util/Date;)Ljava/lang/String;
move-result-object v0
If we look at the very beginning of the cd.smali file we can see that the date format stored in "a" is in the form of "EEEE"
Code:
const-string v1, "EEEE"
invoke-direct {v0, v1}, Ljava/text/SimpleDateFormat;-><init>(Ljava/lang/String;)V
sput-object v0, Lcom/p1/chompsms/util/cd;->a:Ljava/text/SimpleDateFormat;
"EEEE" is the standard pattern letter that refers to the "day of the week" (for more info read here https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html) and as the "E" letters are four then the name will be in full, not abbreviated... like Sunday and Monday, instead of Sun, and Mon.
So if the date that has been received is same as the present date or is one day or two days old the result would be either "today", "yesterday" or the day of the week, but if it's older...
Code:
.line 89
:cond_4
invoke-static {p1}, Lcom/p1/chompsms/util/cd;->b(Landroid/content/Context;)Ljava/text/DateFormat;
The DateFormat returned by .method private static declared-synchronized b(Landroid/content/Context; )Ljava/text/DateFormat will be used.
Having a look to the contents of that method we can see that it retrieves the DateFormat by querying the System Settings
Code:
const-string v2, "date_format"
invoke-static {v0, v2}, Landroid/provider/Settings$System;->getString(Landroid/content/ContentResolver;Ljava/lang/String;)Ljava/lang/String;
That means that the Date Format will change (synchronized) accordingly with the current System settings.
Well... that's enough! Tiring ah? :silly:
So, we found it! :highfive:
But we still have to fix it... well... that's quite simple once we know where to put our hands
Let's just add a SimpleDateFormat as we already did before for the message TimeStamp and insert the code to force the use of that format instead of the one returned by method "b"
At the beginning of the cd.smali file, # static fields section, add
Code:
.field private static final m:Ljava/text/SimpleDateFormat;
At the end of .method static constructor <clinit>()V, below the code added before, add the following
Code:
new-instance v0, Ljava/text/SimpleDateFormat;
const-string v1, "d MMM yy"
invoke-direct {v0, v1}, Ljava/text/SimpleDateFormat;-><init>(Ljava/lang/String;)V
sput-object v0, Lcom/p1/chompsms/util/cd;->m:Ljava/text/SimpleDateFormat;
(note that "d MMM yy", is a pattern for a date format like 9 Sep 16)
Then, as last step, replace this
Code:
.line 89
:cond_4
invoke-static {p1}, Lcom/p1/chompsms/util/cd;->b(Landroid/content/Context;)Ljava/text/DateFormat;
move-result-object v0
invoke-virtual {v0, p0}, Ljava/text/DateFormat;->format(Ljava/util/Date;)Ljava/lang/String;
move-result-object v0
with this:
Code:
.line 89
:cond_4
sget-object v0, Lcom/p1/chompsms/util/cd;->m:Ljava/text/SimpleDateFormat;
invoke-virtual {v0, p0}, Ljava/text/SimpleDateFormat;->format(Ljava/util/Date;)Ljava/lang/String;
move-result-object v0
Job done! Congratulations! :highfive:
So, let's see how it looks the result of this hard work
.
8) The last touch
If you observe the above pictures you'll find that the Conversation list layout isn't as compact as in SGY Messaging app; moreover the divider line, for some reason, doesn't go all the way from one side to the other of the screen, but has a sort of "margin" distance on its left side.
In order to fine tuning the layout we need to change a few values here and there and add a few too
In values\styles.xml, style "conversationlist_row_content",
change android: paddingLeft value from 8.0 to 0.0
change android: paddingTop value from 10.0 to 7.0
change android: paddingRight value from 16.0 to 6.0
change android: paddingBottom value from 10.0 to 8.0
Code:
<style name="conversationlist_row_content">
<item name="android:paddingLeft">0.0dip</item>
<item name="android:paddingTop">7.0dip</item>
<item name="android:paddingRight">6.0dip</item>
<item name="android:paddingBottom">8.0dip</item>
In values\styles.xml, style "conversationlist_row_personlabel",
change android: paddingRight value from 6.0 to 0.0
add android:lineSpacingExtra with value -2.0dip
Code:
<style name="conversationlist_row_personlabel">
<item name="android:paddingRight">0.0dip</item>
<item name="android:lineSpacingExtra">-2.0dip</item>
In values\styles.xml, style "conversationlist_row_datelabel",
add android: paddingLeft with value from 6.0
Code:
<style name="conversationlist_row_datelabel">
<item name="android:paddingLeft">6.0dip</item>
In values\styles.xml, style "conversationlist_row_subjectlabel",
add android:singleLine with value "true" (to fix the glitch on the ellipsizing)
Code:
<style name="conversationlist_row_subjectlabel">
<item name="android:singleLine">true</item>
About the divider...
I hoped I could find any layout file or style attribute somewhere that was related to that left margin that prevents the divider to fill the screen from one side to the other... I couldn't... there's not such thing.
Once again, same as for the case of the message box margin, the divider left margin is "hardcoded".
By searching "divider" within all the smali files existing in (C:\Decompression.chamber\com.p1.chompsms-1)\smali\com\p1\chompsms, there are 27 smali files found but one of them has name ConversationList.smali that seems promising.
The file is located in (C:\Decompression.chamber\com.p1.chompsms-1)\smali\com\p1\chompsms\activities\conversationlist
Indeed... it's the right file!
It invokes setDivider...
Code:
invoke-virtual {v1, v0}, Lcom/p1/chompsms/activities/conversationlist/ConversationListListView;->setDivider(Landroid/graphics/drawable/Drawable;)V
... and setDividerHeight
Code:
invoke-virtual {v0, v1}, Lcom/p1/chompsms/activities/conversationlist/ConversationListListView;->setDividerHeight(I)V
Unlike what we found on com/p1/chompsms/views/Message.smali, in ConversationList.smali can't be found any call to setMargins method; there's instead a call to the InsetDrawable class.
Code:
invoke-direct/range {v0 .. v5}, Landroid/graphics/drawable/InsetDrawable;-><init>(Landroid/graphics/drawable/Drawable;IIII)V
Changing this
Code:
.line 678
:cond_0
const/high16 v1, 0x41800000 # 16.0f
To this
Code:
.line 678
:cond_0
const/high16 v1, 0x00000000 # 0.0f
Will get rid of the divider "margin"
Changing this
Code:
.line 683
iget-object v0, p0, Lcom/p1/chompsms/activities/conversationlist/ConversationList;->h:Lcom/p1/chompsms/activities/conversationlist/ConversationListListView;
const/high16 v1, 0x3f800000 # 1.0f
To this
Code:
.line 683
iget-object v0, p0, Lcom/p1/chompsms/activities/conversationlist/ConversationList;->h:Lcom/p1/chompsms/activities/conversationlist/ConversationListListView;
const/high16 v1, 0x3fc00000 # 1.0f
Will increase the divider thickness from 1.0dip to 1.5dip
So, now... it's showtime! :fingers-crossed:
.
Cherry on the cake
If the phone is connected to the Internet, every three times that the user "enter" one of the SMS conversations, chomp SMS will display an advertisment that will pin on top of the Conversation list... like this
and it will stay there untill the ad gets touched.
The ads are displayed according to their dedicated layouts; there are two different layouts: one generic and one specific for Facebook ads.
The two layouts are defined by two xml files: conversation_list_native_ad_row.xml and conversation_list_native_ad_row_facebook.xml
By adding the attribute a:visibility="gone" to the layouts, the ads won't be visibile anymore (please don't ask "how"... find it out yourself)
As cherry on the cake I decided to make a new app icon for the modified chomp SMS app; an icon that is a mix of the SGY Messaging icon and the original chomp SMS one.
+
=
The icon is of hdpi size and it's available for download as attachment to this post.
That's all folks!
If you have enjoyed to follow the tutorial your click on the thanks button here below will be highly appreciated
Thanks for reading

Reserved

good job. yes, apps keep getting worse. i guess the focus is now on getting your credit card number or harvesting your contacts for marketing, not with the user.
ok - somewhat unrelated, but i trust you'll know... - where does chomp SMS keep its blacklist? i need an SMS app that has an import function, but barring that, i could manipulate the file manually if it's text or XML.

hi, I never used the blacklist function so I didn't even never bother to know where it's saved.
Anyway usually apps have two preferred places where to save their data, one is the databases folder inside the app dedicated folder in the /data partition, the others is the shared_prefs also inside the app dedicated folder in /data/data.
After a quick check I found out that the blacklist is saved in the chompSMS Preferences.xml file.
Unfortunately the list is encoded so the numbers in the list aren't visibile and the app doesn't recognize the numbers if they aren't properly encoded.

You are so spot on with your comments in the first post. I have been using my old LG F3 for so long and the SMS worked so great with layout etc etc... I got a BLU Vivo last year because I needed a bigger screen for GPS driving...
I have just been using the larger phone for driving with my job, via a hotspot on the LG... but time had come to make the newer BLU phone my main phone...
And it has been drudgery finding a replacement app for the new phone, just getting the look and feel to the old phone which was perfect (stock SMS) circa 2013.
Chomp was close... I stumbled upon this post and I am stoked to try your work.
I've never done apk mods.. lots of other coding.. and I am excited to dive in with your examples as my first learning experience with apk.
Doing the date mod in the bubble, and removing wasted space in the bubble, is most important to me.
I am going to try to add an Icon for the "templates" somewhere on the screen, because I use them a lot.
If successful I'll get back and post the info.
Thanks a bunch for your work. I'm stoked !
Rob

Question Disable Swipe To Dismiss (Go Back)?

TL;DR - Is there a way to disable the swipe right to go back feature?
I recently sideloaded a VNC viewer on the Watch 4 to access apps on my phone/computer, and it works well except when I try to move the mouse cursor to the right, the watch exits and disconnects the VNC client. Same problem with scrolling the screen to the right when zoomed in. The only workaround that I have found is to move the cursor to the top or bottom of the screen with a slight rightward motion until the cursor is far to the right, then move it back down/up. Is there a way to disable the swipe right to go back feature, or is there an on-screen input app, such as a joystick, that will work? Perhaps a different VNC viewer might work better? Thanks!

Do not think there is a way to disable the swipe. At least I could not find one.

Also, haven't seen any way to disable it....

TacoDeMuerte said:
TL;DR - Is there a way to disable the swipe right to go back feature?
I recently sideloaded a VNC viewer on the Watch 4 to access apps on my phone/computer, and it works well except when I try to move the mouse cursor to the right, the watch exits and disconnects the VNC client. Same problem with scrolling the screen to the right when zoomed in. The only workaround that I have found is to move the cursor to the top or bottom of the screen with a slight rightward motion until the cursor is far to the right, then move it back down/up. Is there a way to disable the swipe right to go back feature, or is there an on-screen input app, such as a joystick, that will work? Perhaps a different VNC viewer might work better? Thanks!
Click to expand...
Click to collapse
Thats an OS feature, if there was a way to disable it you would probably lose all gestures.

Thanks for the replies guys! I had a hunch that it was more of a communication between the apps and the OS and have found some information. There are flags that need to be set within the app that disable swipe to dismiss while a scrollable overlay is selected. This is how something like Google Maps on the watch will allow tap + drag in any direction as well as scrolling through menus in other apps. I would think there would also be a flag/setting somewhere within the OS to disable swipe-to-dismiss altogether, but perhaps we will need to wait for custom ROMs for that. In the meantime, I will work on customizing the UI of apps to ignore swipe-to-dismiss.
Some additional information:
https://developer.android.com/reference/kotlin/androidx/wear/widget/SwipeDismissFrameLayout
Code:
"To suppress a swipe-dismiss gesture, at least one contained view must be scrollable,
indicating that it would like to consume any horizontal touch gestures in that direction.
In this case this view will only allow swipe-to-dismiss on the very edge of the left-hand-side of the screen.
If you wish to entirely disable the swipe-to-dismiss gesture,
setSwipeable can be used for more direct control over the feature."
wear-os - swipedismissframelayout - android wear disable swipe to dismiss
Code:
There is an attribute in window style to disable this behavior:
<style name="AppTheme" parent="@android:style/Theme.DeviceDefault.Light">
<item name="android:windowSwipeToDismiss">false</item>
</style>

TacoDeMuerte said:
Thanks for the replies guys! I had a hunch that it was more of a communication between the apps and the OS and have found some information. There are flags that need to be set within the app that disable swipe to dismiss while a scrollable overlay is selected. This is how something like Google Maps on the watch will allow tap + drag in any direction as well as scrolling through menus in other apps. I would think there would also be a flag/setting somewhere within the OS to disable swipe-to-dismiss altogether, but perhaps we will need to wait for custom ROMs for that. In the meantime, I will work on customizing the UI of apps to ignore swipe-to-dismiss.
Some additional information:
https://developer.android.com/reference/kotlin/androidx/wear/widget/SwipeDismissFrameLayout
Code:
"To suppress a swipe-dismiss gesture, at least one contained view must be scrollable,
indicating that it would like to consume any horizontal touch gestures in that direction.
In this case this view will only allow swipe-to-dismiss on the very edge of the left-hand-side of the screen.
If you wish to entirely disable the swipe-to-dismiss gesture,
setSwipeable can be used for more direct control over the feature."
wear-os - swipedismissframelayout - android wear disable swipe to dismiss
Code:
There is an attribute in window style to disable this behavior:
<style name="AppTheme" parent="@android:style/Theme.DeviceDefault.Light">
<item name="android:windowSwipeToDismiss">false</item>
</style>
Click to expand...
Click to collapse
I dont seem to get it working. Could you explain it in steps to make someone like me who doesnt understand code to make this work?

Beekitu said:
I dont seem to get it working. Could you explain it in steps to make someone like me who doesnt understand code to make this work?
Click to expand...
Click to collapse
There are different methods out there, but try this as a starting point:
1. Open Android Studio and create a new project. File > New > New Project > Wear OS > Blank Activity > Next > Finish
2. Convert the root layout into a SwipeDismissFrameLayout in activity_main.xml. From the file explorer on the left: app > res > layout > activity_main.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<androidx.wear.widget.SwipeDismissFrameLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:padding="@dimen/box_inset_layout_padding"
tools:context=".MainActivity"
tools:deviceIds="wear">
<FrameLayout
android:layout_width="match_parent"
android:layout_height="match_parent"
android:padding="@dimen/inner_frame_layout_padding"
app:layout_boxedEdges="all">
<TextView
android:id="@+id/text"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="@string/hello_world" />
</FrameLayout>
</androidx.wear.widget.SwipeDismissFrameLayout>
3. Disable SwipeToDismiss via style and theme in a resource file. app > res > values > dimens.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<!--
Because the window insets on round devices are larger than 15dp, this padding only applies
to square screens.
-->
<dimen name="box_inset_layout_padding">0dp</dimen>
<!--
This padding applies to both square and round screens. The total padding between the buttons
and the window insets is box_inset_layout_padding (above variable) on square screens and
inner_frame_layout_padding (below variable) on round screens.
-->
<dimen name="inner_frame_layout_padding">5dp</dimen>
<style name="AppTheme" parent="@android:style/Theme.DeviceDefault">
<item name="android:windowSwipeToDismiss">false</item>
</style>
</resources>
That should be all you need to get started. Once that is working, read over the code and make the necessary edits to achieve the desired result. For example, the text "Hello Round World!" is still swipeable, but the app doesn't close on a swipe, so you would need to edit the text box's attributes to prevent that from moving on a swipe. Also, check out the Google Maps example project for additional information. Keep in mind that the non-swipe to dismiss layouts are derived from the "Fragment" type of layout.

TacoDeMuerte said:
There are different methods out there, but try this as a starting point:
1. Open Android Studio and create a new project. File > New > New Project > Wear OS > Blank Project
2. Convert the root layout into a SwipeDismissFrameLayout in activity_main.xml. From the file explorer on the left: app > res > layout > activity_main.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<androidx.wear.widget.SwipeDismissFrameLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:padding="@dimen/box_inset_layout_padding"
tools:context=".MainActivity"
tools:deviceIds="wear">
<FrameLayout
android:layout_width="match_parent"
android:layout_height="match_parent"
android:padding="@dimen/inner_frame_layout_padding"
app:layout_boxedEdges="all">
<TextView
android:id="@+id/text"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="@string/hello_world" />
</FrameLayout>
</androidx.wear.widget.SwipeDismissFrameLayout>
3. Disable SwipeToDismiss via style and theme in a resource file. app > res > values > dimens.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<!--
Because the window insets on round devices are larger than 15dp, this padding only applies
to square screens.
-->
<dimen name="box_inset_layout_padding">0dp</dimen>
<!--
This padding applies to both square and round screens. The total padding between the buttons
and the window insets is box_inset_layout_padding (above variable) on square screens and
inner_frame_layout_padding (below variable) on round screens.
-->
<dimen name="inner_frame_layout_padding">5dp</dimen>
<style name="AppTheme" parent="@android:style/Theme.DeviceDefault">
<item name="android:windowSwipeToDismiss">false</item>
</style>
</resources>
That should be all you need to get started. Once that is working, read over the code and make the necessary edits to achieve the desired result. For example, the text "Hello Round World!" is still swipeable, but the app doesn't close on a swipe, so you would need to edit the text box's attributes to prevent that from moving on a swipe. Also, check out the Google Maps example project for additional information. Keep in mind that the non-swipe to dismiss layouts are derived from the "Fragment" type of layout.
Click to expand...
Click to collapse
I'm already stuck on step 2. After I chose Black Project in step 1, it asks me for some information about the project, not sure what I should put there.. And on step 2 im confused from the very start..

Beekitu said:
I'm already stuck on step 2. After I chose Black Project in step 1, it asks me for some information about the project, not sure what I should put there.. And on step 2 im confused from the very start..
Click to expand...
Click to collapse
Just click "Next" then "Finish". You can change the name of your project if you want and can also change the programming language to Java or Kotlin, but shouldn't be necessary. Just click finish.

TacoDeMuerte said:
Just click "Next" then "Finish". You can change the name of your project if you want and can also change the programming language to Java or Kotlin, but shouldn't be necessary. Just click finish.
Click to expand...
Click to collapse
alright. this is currently what I am seeing. Can you explain where I need to go in step 2 using the screenshot?

Beekitu said:
alright. this is currently what I am seeing. Can you explain where I need to go in step 2 using the screenshot?
Click to expand...
Click to collapse
Click "Code" or "Split" near the top right corner. Remember where this is as it comes in handy later. I would also add that this thread isn't meant to be a tutorial on Android Studio, and would highly recommend searching for an introduction video tutorial of Android Studio before proceeding further.

TacoDeMuerte said:
Click "Code" or "Split" near the top right corner. Remember where this is as it comes in handy later. I would also add that this thread isn't meant to be a tutorial on Android Studio, and would highly recommend searching for an introduction video tutorial of Android Studio before proceeding further.
Click to expand...
Click to collapse
I understand nothing about coding and dont plan on learning coding. I just want to disable swipe right gesture on my watch. after that I do not plan on using Android studio in the future..

Beekitu said:
I understand nothing about coding and dont plan on learning coding. I just want to disable swipe right gesture on my watch. after that I do not plan on using Android studio in the future..
Click to expand...
Click to collapse
Oh I see. Unfortunately, these steps will not accomplish what you need. These steps are for app development. The solution to disabling the swipe gesture has still not been found. I suspect it will require root access and maybe a custom kernel or ROM. Some people have mentioned patching individual apps to disable swipe to dismiss, but as far as I know, they haven't posted the process to do so. I think it involves decompiling the .apk, making similar edits to the steps above, then recompiling, which is a more complicated process than the steps I posted, and would need to be done for every app you use.
I believe we will have to wait for root access to disable the gesture altogether.

TacoDeMuerte said:
Oh I see. Unfortunately, these steps will not accomplish what you need. These steps are for app development. The solution to disabling the swipe gesture has still not been found. I suspect it will require root access and maybe a custom kernel or ROM. Some people have mentioned patching individual apps to disable swipe to dismiss, but as far as I know, they haven't posted the process to do so. I think it involves decompiling the .apk, making similar edits to the steps above, then recompiling, which is a more complicated process than the steps I posted, and would need to be done for every app you use.
I believe we will have to wait for root access to disable the gesture altogether.
Click to expand...
Click to collapse
Okay, thanks anyways.. sorry for wasting your time.
Have a great day

Beekitu said:
Okay, thanks anyways.. sorry for wasting your time.
Have a great day
Click to expand...
Click to collapse
Not a problem. If a solution is found, it will be posted on this thread.

hi, i found a fun game for wear os, i installed it on my watch, but i can't turn off the swipe to exit, can anyone help?

mustafamfc said:
hi, i found a fun game for wear os, i installed it on my watch, but i can't turn off the swipe to exit, can anyone help?
Click to expand...
Click to collapse
To disable the swipe gesture, you'll need to decompile and patch the apk. I can't help you with decompiling, but there are a few options on this thread: How to decompile an APK or DEX file on Android platform
Once decompiling is complete, follow the steps posted above. For your convenience, I will post them again here, starting with step 2 in Android Studio:
TacoDeMuerte said:
2. Convert the root layout into a SwipeDismissFrameLayout in activity_main.xml. From the file explorer on the left: app > res > layout > activity_main.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<androidx.wear.widget.SwipeDismissFrameLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:padding="@dimen/box_inset_layout_padding"
tools:context=".MainActivity"
tools:deviceIds="wear">
<FrameLayout
android:layout_width="match_parent"
android:layout_height="match_parent"
android:padding="@dimen/inner_frame_layout_padding"
app:layout_boxedEdges="all">
<TextView
android:id="@+id/text"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="@string/hello_world" />
</FrameLayout>
</androidx.wear.widget.SwipeDismissFrameLayout>
Click to expand...
Click to collapse
TacoDeMuerte said:
3. Disable SwipeToDismiss via style and theme in a resource file. app > res > values > dimens.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<!--
Because the window insets on round devices are larger than 15dp, this padding only applies
to square screens.
-->
<dimen name="box_inset_layout_padding">0dp</dimen>
<!--
This padding applies to both square and round screens. The total padding between the buttons
and the window insets is box_inset_layout_padding (above variable) on square screens and
inner_frame_layout_padding (below variable) on round screens.
-->
<dimen name="inner_frame_layout_padding">5dp</dimen>
<style name="AppTheme" parent="@android:style/Theme.DeviceDefault">
<item name="android:windowSwipeToDismiss">false</item>
</style>
</resources>
Click to expand...
Click to collapse
NOTE: You may need to repeat step 3 for any style and theme in the app that you want to disable the swipe gesture on. It doesn't necessarily have to be in the 'dimens.xml' file, but it will be in the 'res' folder. Since this step changes from app to app, you'll need to figure out which changes are necessary on your own. Once you're done, recompile and deploy the modded apk.

TacoDeMuerte said:
To disable the swipe gesture, you'll need to decompile and patch the apk. I can't help you with decompiling, but there are a few options on this thread: How to decompile an APK or DEX file on Android platform
Once decompiling is complete, follow the steps posted above. For your convenience, I will post them again here, starting with step 2 in Android Studio:
NOTE: You may need to repeat step 3 for any style and theme in the app that you want to disable the swipe gesture on. It doesn't necessarily have to be in the 'dimens.xml' file, but it will be in the 'res' folder. Since this step changes from app to app, you'll need to figure out which changes are necessary on your own. Once you're done, recompile and deploy the modded apk.
Click to expand...
Click to collapse
hello, thank you for taking care of me, but I couldn't understand anything from what you said, if it doesn't bother you, if you can do what you are saying on any apk and publish it in the form of a video, I would be very useful, thank you