Hello all! I have been making some UI changes to the stock Mms.apk app on my Nexus S. Nothing huge, just a few tweaks. I have been trying to figure out how or where to remove the left and right margins on messages in the message list. I would like each message to span the width of the entire screen. I have decompiled the the apk and I'm not sure where this can be edited. I am using APK Manager 4.9. I have looked in every file that references "MessageListItem" in its title.
Any ideas? Please and thank you!
See the attached image for what margins I am talking about. The margins are highlighted in red.
I am working on some mods for a Sense 2.1 ROM for the HTC Thunderbolt (based on latest OTA 2.11.605.3)
Two things I am stuck on, and I have searched high and low to try and resolve this but can't come up with what I need.
#1 - I want to change the icon size (workspace screens and app drawer) from 72x72 to a larger size (maybe 90x90). I have already added larger icons to apps and adjusted every size I can find in Rosie that looks like it would effect icon size. I even adjusted a lot of the padding amounts, but no luck. I did however notice the mail and messages icon would go to the larger size "sometimes" on the homescreen and in the app drawer, but not all the time. Very strange.
Anyone done this and know what i need to do to get my icon size like I want?
#2 - I would like to customize the background color or image on the settings menu (and sub menus if possible). I cannot find an xml file that seems to relate to the main settings screen where I can trace the color or set an image as the background like you can do with the app drawer.
Anyone know how/where this is done?
Thanks for the help, I look forward to getting some direction on this so I can hopefully move forward with this "project".
romified said:
I am working on some mods for a Sense 2.1 ROM for the HTC Thunderbolt (based on latest OTA 2.11.605.3)
Two things I am stuck on, and I have searched high and low to try and resolve this but can't come up with what I need.
#1 - I want to change the icon size (workspace screens and app drawer) from 72x72 to a larger size (maybe 90x90). I have already added larger icons to apps and adjusted every size I can find in Rosie that looks like it would effect icon size. I even adjusted a lot of the padding amounts, but no luck. I did however notice the mail and messages icon would go to the larger size "sometimes" on the homescreen and in the app drawer, but not all the time. Very strange.
Anyone done this and know what i need to do to get my icon size like I want?
#2 - I would like to customize the background color or image on the settings menu (and sub menus if possible). I cannot find an xml file that seems to relate to the main settings screen where I can trace the color or set an image as the background like you can do with the app drawer.
Anyone know how/where this is done?
Thanks for the help, I look forward to getting some direction on this so I can hopefully move forward with this "project".
Click to expand...
Click to collapse
1.
While I've never tried to change icon size (except to make them smaller....), I was able to do it by increasing number of icons (aka 4x5 layout). I know in res/values/, values-hdpi, and values-port-hdpi there are dimens.xml and integers.xml. Since I've never done it before, I can't help you specifically...but that's where I would start. It won't matter the size of the actual png inside the apk, Rosie will size the app based on its resources.
2.
The settings menu, I'm almost certain, calls for resources in framework-res....please don't quote me. I've never tried to theme that myself but I am almost certain. Look for references in Settings.apk to @android, et cetera. Narrow down your search like that. I recommend this line of code:
grep -lr "@android" Settings/*
^assuming you decoded Settings.apk into directory "Settings"
^also assuming you're on Unix system....
Sorry I couldn't be more help man! Good luck!
Taking notes over PDF slides with the scribe pen has really saved me a lot of hassle. I love this function of the flyer. There's really only one way it could be better: Fullscreen support, or at least "more screen" support.
Not only does the HC bar take up space, but the menu/title bar on top is even bigger. The pdf viewer has the screen real estate of a 5inch phone.
PDF editing seems like only a moderately used feature, so I don't see this getting done on it's own. I'm offering a very modest reward for a fix.
I would be willing to donate for the removal of the huge uppermost Title/menu bar in PDF viewer, so that a double-tapped fitted pdf page will fill the new space. See the attached image. You can leave the small menu button in the corner if possible, or just get rid of it if it's too difficult.
I'm hoping this is as simple as modifying a few variables in the apk. I could be very wrong.
I can live with just the HC bar at the bottom.
Note: I have tried apps like repligo and ezpdf which do offer fullscreen support. However, annotating and changing annotation options takes many more steps than the HTC pdf viewer.
Secondary goal:
Apps like honeybar and honey hide widget cause all pen written annotations to be shifted up.
I believe the solution to the first problem would also allow an easy fix of the shifting pen annotations. I would like the PDF viewer to accept pen strokes properly with a hidden HC bar.
No one's willing to give it a shot? Ah well.
This will be my only bump.
I've attached the (unmodified, I think) HTCPDFViewer.apk from /system/app from LeeDroid's 4.1.0 rom.
I was the guy who removed the obnoxiously large language bar from Sony Ericsson's keyboard back when I was still using my u20i phone... unless HTC is particularly irritating about how it structures its resources, you're right that it is a matter of decompiling the APK, adjusting numbers, and recompiling it. Merely hiding is not difficult (making the Menu button semi-transparent is probably too difficult, though, but you can pick a ROM with the hardware buttons enabled).
Unfortunately it is also incredibly tedious to decompile and recompile everything right, from my experience of the keyboard hack. I'm not really up to it at the moment. Hope you can do it.
I've poked around in the archive. I wonder if I could just delete the ti.tle bar png or layout file. There doesn't seem to be a definitive title bar png
I'm also experimenting with apk multitool.
Since it's a stock rom app, is this venture going to be a lot more complicated than editing an xml line and then recompiling?
Here's where I'm at. Everything I know about android programming I've learned tonight, so this may be confusing and stupid sounding:
The decompiled apk has several things which could refer to the title bar.
dimens.xml has lines like
<dimen name="global_title_height">35.0dip</dimen>
<dimen name="editing_panel_header_height">56.0px</dimen>
<dimen name="editing_panel_header_margin">47.0px</dimen>
<dimen name="editing_panel_no_footer_header_margin">35.0px</dimen>
However there are also thousands of header and title lines from other xmls.
Can I just use a theme line in the manifest?
It uses the ActPDFReaderTheme whose parent is the HtcActionBar.FullScreen from the com.htc.resources.apk
These link to the common_mainnav xmls and pngs in the resources.
Do I need to find an HTC theme from the com.htc.resources.apk that doesn't have a title bar? Could I edit the com.htc.resources.apk and edit the pngs or delete the referencing lines in the styles.xml?
Thanks. I'll keep digging.
And btw, the bounty's still out if anyone can do it faster. I don't have much free time.
I think I've got this. I'm real close
I figured out how to decompile, edit xmls, recompile, copy original meta-infs and androidmanifest, and adb push.
The dimens.xml in the viewer apk has no effect on the bar. It's a standard template htcactionbar.fullscreen
I could direct the apk to a new theme, but I've decided just to try deleting or shrinking the bar from the com resources apk.
Good luck! Remember the apk you push back must be a signed one, probably via hacking the modified xml files back into the original signed apk.
Now I've run into a snag.
No matter how many margin and layout dimension variables in the com resource I set to 1.0px, I still have a black bar above the pdf.
Then I tried changing the theme reference in the pdfviewer.apk. It loads the file picker without an action bar, but as soon as I click a file it crashes. It seems (I think) that the program has too many calls for the action bar. I'm not a programmer. Do you know how I can get the program to simply ignore any lines referencing the "actionbar"?
Lines such as: "invoke-virtual {v3}, Lcom/htc/pdfviewer/ActPDFReader;->getActionBarHeight()I"
I also tried <item name="android:windowNoTitle">true</item> after the theme and I have the same effect of no title bar but a forceclose after selecting a file
Could you post the entirety of the relevant xml layout file?
porcupineadvocate said:
Could you post the entirety of the relevant xml layout file?
Click to expand...
Click to collapse
Unfortunately there is no simple relevant layout file. I can't go any further with this project because I don't know programming. Here's my progress if anyone would like to give it a shot:
In the decompiled HTCPDFViewer is a \res\values\styles.xml
There is the line:
<style name="ActPDFReaderTheme" parent="@com.htc:style/HtcActionBar.FullScreen">
This tells the program to use the HTCactionbar.fullscreen template style in com.htc.resources.apk
Now there are two paths to take from here:
1) Changing the style template to @android:style/Theme.NoTitleBar.Fullscreen
or adding the requestWindowFeature(Window.FEATURE_NO_TITLE) line
Issue: This causes the file picker to load without a title fine, but as soon as a pdf loads, the program crashes.
How far I got: I simply deleted 2 lines referring to the actionbar in the PdfLoadingPage$LOADING_PAGE_Handler.smali and the pdf loads. However there is a now a black empty bar on the bottom, and any pen writing is being moved upwards.
I suspect this is because of the ActionBarMenuAdapter.smali that controls how the pen annotations are moved in relation to the actionbar. There are also 100 more lines referring the actionbar in the other smalis. You can find them all by searching the apk for "actionbar". A proper programmer could remove these lines, or more easily make every m_iActionBarHeight:I line refer to zero.
If someone can fix the programming, I suspect that this would also solve the hidden HC bar issue, allowing true fullscreen support!
2) Editing the com.htc.resources.apk
The styles.xml in this file has a NoTitleBar.Fullscreen theme that redirects to other xmls redirecting to different layout files and pngs.
I've looked through every dimens.xml and other xmls that may be even loosely linked to the actionbar. I even tried haphazardly changing every possibly connected dimension to 1.0px.
I then tried shrinking all of the related PNGs to 1x1 pixel.
The end result was just a funking looking grey and black bar at the top.
I have no idea where to find the dimensions controlling the size of the actionbar.
Thanks for any help! Warning: Recovery backup before pushing a new com.htc apk, if you don't do it correctly, things can get messy with the OS.
porcupineadvocate said:
Could you post the entirety of the relevant xml layout file?
Click to expand...
Click to collapse
Ok I may have lied. There are one or two files I wasn't sure about.
These are from the xmls in layout folders of com.htc apk.
Can you take a look and see if there are simple line(s) to change here? notepad++ is great.
I already attempted to edit all of the dimens.xml dimensions. I can't remember if I got all of the dimensions in these files too.
The bar seems to be about 56 pixels. I gathered that from reduced editing view dimensions but I could be wrong.
Not that it is a big deal for a minor issue like this in a low traffic forum like EVO View but "bounty threads" are strictly prohibited by xda.
I doubt the mods will hassle you since this isn't a heavily travelled thread but they might shut you down at any second. Good idea to get some PM's going with anyone who is helping you.
Good luck.
Sent from my PG41200 using Tapatalk
Post the decompiled HTPDFViewer, please. I particularly want to see the contents of res/layout/*.xml files.
As a tip, don't delete any elements; just resize them to zero height/width if possible. Deleting will cause crashes when the program tries to reference them.
porcupineadvocate said:
Post the decompiled HTPDFViewer, please. I particularly want to see the contents of res/layout/*.xml files.
As a tip, don't delete any elements; just resize them to zero height/width if possible. Deleting will cause crashes when the program tries to reference them.
Click to expand...
Click to collapse
Here it is.
Woops I didn't realize bounties were prohibited, especially with so many developers asking for "donations"
Delete this if you'd like. I didn't mean to break the rules.
Donations and bounties are different. Donations are thanks for work done, bounties are offer of compensation to do work. If they allowed bounty threads xda would be overrun with them.
No big deal. I doubt the mods even visit this thread. Just wanted to give you heads up to establish pm conversations in case they did
Sent from my PG41200 using Tapatalk
No progress since my last update on the programming front. However I have been playing with the lcd density changer.
Setting it to 170 from 160 and enabling the GB like bar on top has interesting results. The pdfviewer only edits properly when I use Honeyhide or Honeybar. So we know that disabling the notification bar and having a working pdfviewer is possible.
However, I found I have the best pdf editing real estate when I set the lcd density to very low, like 120. In fact, not only are the title and HC bars smaller, but the pen seems to be more accurate too!
Maybe this information will help with our goal.
EDIT: at 120 and below, the scribe color wheel pops up on the wrong side. Still works though. Other tablet functions are much slower and there's some screen corruption too. It's not a permanent solution, but works for annotating pdfs.
I am using Eclipse Helios Service Release 2 and the project target is 2.2.
I have a xml layout that has a HorizontalScrollView and ScrollView with a LinearLayout. For some reason unknown to me the graphical layout will not expand when I add objects that exceed the size of the default screen size.
I have other xml layout files that will expand when using a single scrollview type, however when using two of them nested together it does not work.
I have attempted to use ScrollView then HorizontalScrollView and reversed to see if it is a order of priority issue with Eclipse. However this does not work.
There appears to be nothing missing from the properties of the scrollviews between those that will expand and the one that wont.
Is there something I am missing? Or is it not possible to have two different scrollview types in one layout and still have a auto expanding graphical layout editor? I would rather not define a specific screen resolution that would allow me to see all objects; I want the app to be adaptable to any device screen size.
Thank you for your help
Sincerely,
Brandon S
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
With SMS messages, android by default turns this : ) into this (figuratively)
Where might the code be located that does this text to png recognition? I know the png themselves are located in the framework-res.apk but couldn't fine the code that pulls those png whenever anyone types in : P.
My friend and I want to try and insert keywords that are recognized by the phone to insert a new png emoticon. We know that only we will see the emoticons when anyone types the keyword but that is our goal.
I tried looking around the framework-res.apk for this but all I found were animations and images.
It is actually stored in the font files for Android. Back in my htc rezound days I wrotea file that enabled the jellybean emoticons on ics. I can't remember off hand where those files are or what you need to change, not sure if samsung handles its fonts the same. But hopefully this helps you some. I can look into it at some point for you
Does anyone know where the font directory is that Oakley is talking about?
Or anyone have any more insight?