Firstly, I am using Mik's rom.. with pngs modified to my liking.. I have also searched around quite extensively for getting my questions answered.. but without any success.
I have been trying to mod the rosie launcher and am running into a few issues.
1. I can mod the icons pretty easily.. no problems there.. I can also remove the text "Phone" from the center icon.. but phone image is a little off center plus it is vertically offset (shifted a little up). I was told I can play around with the png image file and get that fixed.. however.. I am wondering if there is an xml file in particular that defines the x and y co-ordinates of the launcher icons. So yea.. I am verse with adb, decompiling, recompiling etc.
2. I am looking for a way to get the phone on the left and app drawer in the center.. any guidance with regards to this will be of great help to me. I am guessing this is somewhere in the smali files in Rosie.odex. I have decompiled it resulting in a bunch of smali files.. can someone tell me which particular one I am supposed to edit?
3. Wanting to know if there is any way to add a 4th button to the rosie launcher instead of the usual 3.
Again, I am looking for the know-how... NOT just a mod that I can apply via flashing.
I appreciate anyone who can direct me to a tutorial or a guide.
Thanks.
wow.. not a single reply!... I guess I would have gotten at least a few responses if I had posted this in the development section.
Grab one of my Rosie mods on theMikMik. It has the phone on the left and app drawer in the middle. grab one of those and mod it to your liking
chingy51o said:
Grab one of my Rosie mods on theMikMik. It has the phone on the left and app drawer in the middle. grab one of those and mod it to your liking
Click to expand...
Click to collapse
Thanks.. but like I said "Again, I am looking for the know-how... NOT just a mod that I can apply via flashing.""
I want to know which xml files require the editing etc. I am surprised there are no Rosie Guides anywhere that explain which xml/smali files are commonly involved the typical mods.
Hey there everyone, I am wanting to edit my framework to get a better looking notification bar. I have an android phone called SH7218U, I am rooted with all Gapps.
If you look this up phone on Google, you will see that the notification bar and icons are very similar to stock Android 2.2 ( I am running 2.2.1). The only difference is that the signal bar is located to the left of the bar as well as some icons getting set there as well. You can really see this here: http://www.itechnews.net/wp-content/uploads/2011/03/Sharp-SH7218U-Clamshell-Android-Phone.jpg
When going into root explorer and checking out system/framework I am see the familiar framework-res.apk file, but I also see an apk file called dianxinos-res.apk. It seesm to be able to mess with framework and change the UI and other things, both of these files need to be edited. This is just a guess though since I have been able to find a post on a Chinese forum that gives a new notification bar (the only difference being the battery icon replaced with a numerical battery representation and the (when bar is pulled down) shortcut to the useless built-in task killer is gone. Inside of the package to this new framework I get both framework and dianxinos files so it seems I would have to replace both of the old files with the new ones.
As you can see in the above image there are virtual android buttons on the bottom of the screen as well, for when you want to use the phone normally. I do not think that the dianxinos-res.apk is linked to the virtual buttons as exploring system/media/pics contain.bmp images of the virtual buttons and I have confirmation by another SH7218U user that editing these images will directly effect how they are displayed.
I was just wondering anyone know how to edit the framework when there are two files corresponding to this. I don't know much about editing the framework but even so I am quick to learn but figured I would just ask around before I do anything. Worst comes to worst, like a bootloop for instance, I have a system.img for my phone so flashing that with fastboot will get my phone working again.
Anyway, Ive uploaded both files in case anyone would like to look at them. I am trying to go for a gingerbread-esque notification bar with blue instead of green possibly.
If anyone thinks this thread would get better hits elsewhere I would appreciate any input.
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.
Where are they? I checked the framework-res and SystemUI of an AOSP rom, and they're just not there. Does anyone know?
Sent from my GT-I9100
I join the question, i searched in all possible drawable folders and nothing, just grey pngs at ..\framework\framework-res\res\drawable-xhdpi\stat_sys_battery... :S
yuriy636 said:
I join the question, i searched in all possible drawable folders and nothing, just grey pngs at ..\framework\framework-res\res\drawable-xhdpi\stat_sys_battery... :S
Click to expand...
Click to collapse
Changing them changes nothing. I've also been looking, haven't found them yet
has anybody found where the battery can be changed?I changed and added my mods in almost every apk, such as contacts,sytemui,framework-res,dialer you name it -I have them in there but still shows the default very frustrating!Same thing with the dial pad it also shows default on the initial dialer but the in-call dialer I was able to theme.
EDIT Nevermind -I have found out the battery among some otherthings are now generated in code in 4.4 ,So sorry to all the modders that like to change things easy.It will now require much more to make changes that were once a matter of changing a few png files or maybe and xml here and there.Lerts hope there are themers out there that find a way around this
I found this post what mean that battery icons is draw by code:
http://forum.xda-developers.com/showthread.php?t=2513466
Right now, the only thing I could find is how to add the % number in the icon.
https://play.google.com/store/apps/details?id=de.kroegerama.android4batpercent
Before.
As the icons are drawn, can't we remove the goto scrpt and use a old drawn icon xml file
try my last mod guys, it can be found in my signature..
Hi! I'm new into creating themes, and I'm looking for a tool that could make it easier. I know how to extract .apk, how to replace images, modify .xmls, but often I don't know what an image is for. Let's say im modding SystemUI and I want to change background of my notification bar. The only thing I know is that inside drawables folder I have to look for something named notification_bar.png, something like that. I was looking for an app that could tell me how an image inside an app is called in code ( example: I'm inside calculator app, I press on background and the app says that file is called background.png and is inside drawables-xxhdpi). I tried Android Studio --> Layout Inspector, but it didn't help me at all because, well, I just don't understand it.
Of course, while modifying SystemUI I can look for explaination of certain pngs on the internet, but
-not every SystemUI is the same
- if I want to change drawables of an app that doesn't have specific explaination I have to know how to identify drawables.
It must be possible somehow, because I've run into some themes that modify external apps (like WhatsApp, SuperSU etc.)
Those ppl had to know what certain .png is for, the question is: How?
I don't believe they just had to sit there and try every possible combination.
Also, inside SystemUI there's A LOT of files that are never used, and their names can be misleading.
Is there any way to identify drawable inside running app easily? Without digging in code and guessing?
Thanks in advance for any answer
I tried to analyze Mms.apk (it's system app). I was looking for a drawable representing default contact icon, here called ic_contact_picture.png .
I actually managed to find a proper layer in Layout Inspector(ConversationListItem.xml), analyzed it and found a code referring to table "id" in resources.arsc . The object the id referred to was called "avatar". And that's it. I couldn't find id(I got it from resources.arsc/drawables) of ic_contact_picture.png anywhere in that layout. There was only id referring to "id/avatar". It doesn't make any sense.
How do I find drawables using Layout Inspector or any other tool?
It was easier when it came to text. I also found an id referring to resources.arsc/id, but that id was included in the layer I was looking at (ConversationListItem.xml).
But I still wasn't able to perform any action on that text, because there wasn't any setting like text color or anything, there was just a line android:textAppearance="@attr/0x1010041"
It is an attrib from framework-res.apk, but when I opened framework-res.apk and found that attrib there was no reference to anything like color, font, so there was nothing I could really do.
Can someone help me with those 2 problems?