For 2.1 themes see post #17 on page 2: http://forum.xda-developers.com/showpost.php?p=9049613&postcount=17
I decided to open a thread to share the knowledge I have collected on timescape themes. This also partially applies to mediascape and up until now has been split between these two threads:
http://forum.xda-developers.com/showthread.php?t=737778&page=46
http://forum.xda-developers.com/showthread.php?t=765686 Please read this!
I thought it would be better to combine this into one thread that will be easier to find. If anyone disagrees then please post with reasons and alternatives. I will update this first post as we figure out more tweeks etc. (hopefully it will need a big rework soon because SE finally gets us 2.1 )
Before I start, thanks to Chewitt for finding the acet files, and for inspiring me to start messing with the look of my x10 with his Dark10 themes.
Timescape (and mediascape) do not store all of their images in the .apk resources. Oh no, that would just be too logical, and we are talking about Sony Ericsson here
The timescape theme .apk resources do contain some of the images used (e.g. the trash can and app drawer handles), and the actual Timescape .apk has the resources for the tile images etc. I'm not going to go into this as there is enough content about modifying these sorts of resources here. What I will go into is where the timescape background, wave animation, pagination slider colours and the tile alpha blending and default colours.
1. The background: This is stored in an .acet file (see the first of the above posts). This is an file that basically just contains a samll header and then rgb information (or sometimes argb, this is specified in the header which I haven't got 100% sussed yet). The background images are in the assets/ts folder in the theme .apk and are called ts_bg_app.acet and ts_bg_home.acet for the application and timescape home respectively. These can be modified with acetConverter.exe. You can load an image and export an acet file or you can go the other way. TS uses acet backgrounds without an alpha channel so leave the alpha checkbox unticked when creating them (it might work with alpha... never tried...).
2. The Tiles: I'm pretty sure the alpha blend images for the tiles are found in the system/usr/semc/seee/files folder (alpha_tile.acet and alpha_tile_fade*.acet) but I haven't modified these yet. As an aside the background for the first page of mediascape is here too. More important is the default background for a tile. This file, ts_tile_empty.acet, is a single pixel file found in the assets/ts folder for each theme. This specifies the solid colour to be used as a background for the alpha overlay on empty tiles.
3. Animation files: Wave and Pagination. This is all stored in three .afx java animation files in the themes assets/ts folder (ts_bg_wave.afx, pagination_glow.afx and pagination_area.afx). pagination_area is the square around the selected item in the scroll menu at the bottom (or the top if TS is the home page) and pagination_glow defines the lines at the top and bottom of this area. I haven't got these files fully sussed either, at the moment I'm restricted to doing some awful byte replacement to change the color (I can also change the wave pitch, but it doesn't look any good). I have attached an exe to generate these files (SetTimescapeAnimationColor.exe). Click on the white square to choose a base color and use the buttons to generate whichever of the files you want. If anyone knows how to edit these files properly please let me know, I come from a c# and c++ background and don't really know what I'm doing with java...
Thats pretty much it. Just sort out 6 files, update the png resources (the thumbnails for the theme selection are in the Timescape.apk resources folder) and you're done.
Note: I have had problems when I modified the wrong bytes in the afx files. Basically, after selecting the theme timescape just crashed. If you replace the theme file it still won't start, you need to clear the application data to get it running again. Along the same lines, after modifying a theme you need to reselect it from the themes menu as the files are cached.
Please let me know if I missed anything.
Update: I have attached the source code for the animation color tool. Please keep in mind that this was just a bit of code quickly thrown together so we can modify the animation color, I don't usually write code that looks like that
The project is a C# project from visual studio 2010 but the meat of it is in MainForm.cs so just open that if you use a different language/dev environment.
Here is the code from one of the buttons. Resources.pagination_glow is a byte array from an embedded resource (pagination_glow.afx).
Code:
string r = string.Format("{0:000}", (int)(((double)colorPanel.BackColor.R / 255.0) * 100));
string g = string.Format("{0:000}", (int)(((double)colorPanel.BackColor.G / 255.0) * 100));
string b = string.Format("{0:000}", (int)(((double)colorPanel.BackColor.B / 255.0) * 100));
byte[] bytes = new byte[Resources.pagination_glow.Length];
Array.Copy(Resources.pagination_glow, bytes, Resources.pagination_glow.Length);
bytes[949] = (byte)r[0];
bytes[950] = (byte)'.';
bytes[951] = (byte)r[1];
bytes[952] = (byte)r[2];
bytes[953] = (byte)',';
bytes[954] = (byte)g[0];
bytes[955] = (byte)'.';
bytes[956] = (byte)g[1];
bytes[957] = (byte)g[2];
bytes[958] = (byte)',';
bytes[959] = (byte)b[0];
bytes[960] = (byte)'.';
bytes[961] = (byte)b[1];
bytes[962] = (byte)b[2];
bytes[963] = (byte)',';
using (FileStream stream = new FileStream(saveDialog.FileName, FileMode.Create))
{
stream.Write(bytes, 0, bytes.Length);
}
What is important to note is that the embedded afx resources came from the orange theme, the other themes will require different offsets for the byte modification. I'm not sure why the different themes have different code here, I haven't looked closely at the wave animation code for each theme so there may only be a difference there, or there could just be one more space here and there in the preceeding lines or four spaces instead of a single byte tab ('\t')...
Anyway, the next step is to try and modify the number of bytes in the code and see if it still works, on my first few tests timescape just crashed so I thought that the number of bytes of clear-text code may be stored in the header. I'm not so sure now as I think I may have just been having problems while mixing the use of the .Net stream classes for reading an writing. I'll check this out though.
If we can modify the code however we want then I just need to learn a bit more java
The code for the wave animation is in the comments at the bottom of MainForm.cs. Here is the line with the characters being modified in bold:
fcolor.rgb = vec3(1.0, 0.91, 0.72) * ambientRatio + vec3(1.0, 0.516, 0.0) * specularRatio;
LOL this is just lazy lol, Thanks for the guide i will get the other 3 i need for Dark10 sorted on sunday.
this all sounds awesome =)
May I suggest posting the source code to your .exe files? that way others can pitch in and help improve the tools, too. slap on the GPL for a decent licence and it should be no problem
ttxdragon said:
this all sounds awesome =)
May I suggest posting the source code to your .exe files? that way others can pitch in and help improve the tools, too. slap on the GPL for a decent licence and it should be no problem
Click to expand...
Click to collapse
Good idea I have just updated the first post. I have only added the animation tool source as the .acet converter is just a direct color translation except for the header which is post in the acet thread linked in the first post.
I can post this code as well if anyone is really interested, but it will have to wait until I am back at work on the 14th, or until the VPN starts working again
VPN's up - posted the rest of the source.
calum.. just got a new charger today lol so back on track.. although some reason i cant seem to get my colour to change at al? ive rebooted, tried task managers n al but no luck..
Edit: ignore that.. managed to get it working! like an idiot i forgot to add the code at the top for mount/remount lol.. feel like a blonde
Has anyone got an original version of ms_bg_background_home_icn.acet?
Being the genius that I am, I tried to edit it without backing it up first.
I tried to convert a png image to an acet file using that acet converter but ended up with a background with a similar issue to what's in this post. Will read through all the posts tomorrow and try again.
Hey buddy any more progress with this project?
Sorry, on the road at the moment. I'll be back onto this next week.
@Mobzter: glad you got it sorted.
@Sixpence: you may have exported the image with the alpha channel. Make sure the alpha option is off for the timescape and mediascape backgrounds. I'll add complete backups to the first post next week
heres a backup of that file
_calum_ said:
@Sixpence: you may have exported the image with the alpha channel. Make sure the alpha option is off for the timescape and mediascape backgrounds. I'll add complete backups to the first post next week
Click to expand...
Click to collapse
Ah, yeh, I think that's what I did. I'll try again and see how I go. Cheers!
Thanks for backup Mobz!
EDIT: Sweet, that worked!
I just thought I'd post a link to my dark Timescape theme here.
Timescape (Dark)
If anyone else has got any modified timescape themes please post them (including the modified framework and thumbnail images). It would be nice if we didn't just all modify the Indigo them (as I did above) as if we use neutral images for the default contacts etc. then we can easily change between the different themes.
Any interest
Just a bump to see if anyone is interested in doing anything with the Timescape animation except changing the color.
If they are then I might get back into modifying the .afx files, otherwise I'll probably just move on....
I don't actually use it that much and now I've got rid of the blue I'm sorta happy, but it might be kinda cool if we can add our own animations to replace the wave...
How about the mediascape animation? I wanna make it melt into the next screen. Do u think that's doable?
How can i chnge theme for x10i
Sent from my X10i using XDA App
gavriel18 said:
How about the mediascape animation? I wanna make it melt into the next screen. Do u think that's doable?
Click to expand...
Click to collapse
Do you mean instead of the spline/fade animation when you hit the 'more' button? I think a melting animation would be pretty ambitious and probably only doable if the fade is actually part of the animation. I'll see if I can get an editor slapped together so we can just modify the afx code directly. I'll have a look at the mediascape animation files once I've got that done...
xian08 said:
How can i chnge theme for x10i
Click to expand...
Click to collapse
Sorry, I need a bit more information here. Where exactly are you stuck? Do you just want to install a different theme that you have from one of the x10 themes in another forum, or do you want to create you own?
That's exactly what I was thinking, a melt to a fade into the next screen.
I'm trying to understand how it works but i don't have enough spare time right now.
OK, 2.1 is here and the file formats for timescape themes have changed...
First off, the apk names have changed. They are now named like this:
TimescapeLargeUITheme[ThemeName].apk (e.g. TimescapeLargeUIThemeSakura)
The .acet files are now .uxraw files. The file header and content has also changed: the header is now 8 bytes, that can be split into 4 16bit integers. The first two I'm not sure about, (second one always seems to be 8...) but the 3rd and 4th are width and height respectively. After the header we still have the color info, but it seems that alpha is always included. The bytes are in the order R G B A (the alpha is now the 4th byte instead of the first).
I have attached the new converter and source.
Edit: I originally wrote an incorrect value for the first byte in the header (20 instead of 0x20... oops ) this resulted in a black background...
The afx files have also changed to uxsh. There seems to be a bit more in these files but the animation code is still in plain text. I'm working on an editor, and will update this post when it's done.
2.1 or 1.6 ?
Is this for 2.1 or 1.6 ?
Looks a silly question... But, am little cautious and more excited to see this on my 2.1update1.
Thx for such a great work.
_calum_ said:
OK, 2.1 is here and the file formats for timescape themes have changed...
Click to expand...
Click to collapse
mitalbr said:
Is this for 2.1 or 1.6 ?
Click to expand...
Click to collapse
2.1 (I had also changed the thread title to make this clearer )
_calum_ said:
2.1 (I had also changed the thread title to make this clearer )
Click to expand...
Click to collapse
I was just adb'ed the file system and I found I have following files...
TimescapeLargeUI.apk
TimescapeLargeUIThemeBlue.apk
TimescapeLargeUIThemeGreen.apk
TimescapeLargeUIThemeIndigo.apk
TimescapeLargeUIThemeOrange.apk
TimescapeLargeUIThemeSakura.apk
TimescapePluginManager.apk
I couldn't locate...
Timescape.apk
TimescapeThemeIndigo.apk
So Sense 6 is finally here, and it brings with it another round of the cat and mouse game that HTC loves to play with XDA themers.
Veteran HTC themers will know that each version of Sense brings new challenges, and sadly Sense 6 is no exception. I had made a bunch of reference guides for Sense 5.5, but other than sending out the Dropbox link, never got around to doing much with them.
I figured this time I'd hit the ground running and create a central thread where we could all share what we've found, rather than scattered posts in various mod/theme/rom threads. The aim of this thread is to create a place to share our findings, rather than all trying to overcome Sense 6's idiosyncrasies individually. As such, it is not intended to be a How-to theme guide. Most of the information posted here will assume at least a basic knowledge of theming, xml editing and apk manipulation. There are lots of such guides already available on XDA, and are easily found with little effort. However, I have added a couple of links to the bottom of this post to get you started.
Please feel free to add any theming stuff you find while exploring Sense 6, requests for help etc. Pictures of your themes/mods are welcome, provided you are also explaining how you did them if the info isn't already posted in the thread.
INDEX
Post 2: General tips, pointers and observations
Working with Sense 6
Troublesome apks
Frameworks and tags
Public id's
Post 3: fisha21's Guide to HTC's built in themes
Sense 6 themes
What are they
Where are they
How to change them
How to add new themes
How to stop the 4x1 weather clock changing colour according to time of day
Post 4: Fringe theming - hosted by @Pneuma1985
Internalizing color in htcclockweatherwidget.apk & Inverting 4x1 clock
Change small / large weather icons to white in smali
Change the vertical divider in 4x1 clock to an image that can be themed
Removing the SystemUI notification drawer bg fade in/fade out..
Changing fonts selectively in any apps not causing a global change
Animate the status_bar_close_on and keep the carrier label at the same time
Add Operator_name to statusbar
Move signal_cluster to the left
Turn on spinning 3g icon in stock SystemUI
Post 5: Theming on the razor's edge - hosted by Raymond Ebertt
Transparent Prism Appdrawer Background
Custom Panels for the WeatherClockWidget.apk
Inverting Issues
Inverting Data Usage Background
Inverting Weather.apk Backgrounds
Background in Browser.apk when Navigating Tabs
Pop-up Window on HTC_IME - Word Correction
Theme controlled fontcolors - thanks @ineedone and @PuNkA.YaNoU
Change which weather icons sets are used for day and night clocks - thanks @2WildFirE
HTC app buttons - thanks @ineedone
Ok / cancel buttons in HTC apps - thanks @ViNOK16Bit
Entry field background in pop up Contact card - thanks @ineedone
Middle white box behind Phone, Message etc icons on pop up Contact card (when clicking on Contact's thumbnail in Phone, Messages, Mail etc (see screenshot for Entry field background) - thanks @Basil3
Remove On / Off labels from HTC settings toggles - thanks @ineedone
Moving signal cluster to lefthand side of statusbar - thanks @Pneuma1985
SIM PIN lock entry field in Settings - thanks @Onepagebook
Icon PSD's for HTC apps - thanks @Pfaffinator (the icon king!)
How to remove coloured overlays from Settings page icons - thanks @Basil3
HTC mini+ launch screen
Inverting the background for the Send SMS window you get, after declining a call - thanks @billbowers
Changing the colour of tab number in Browser - thanks @PuNkA.YaNoU
"Release to refresh" text colour (screenshot in post) - thanks @PuNkA.YaNoU
"Accounts and folders" header in HTC Mail app (screenshot in post) - thanks @PuNkA.YaNoU
Blinkfeed side menu issues with newer versions of Blinkfeed - thanks @Basil3 and @Raymond Ebertt
Redirect app drawer Playstore icon to within Prism.apk - thanks @[email protected]
Full-screen caller contact photo - thanks @Kiray1982
USEFUL RESOURCES FOR BEGINNERS
List of useful guides etc compiled by superthemer @pstevep - the parent thread is also well worth a read. Although some of the stuff refers to older versions of Sense, there are still some hugely useful tips and techniques in there. Of course I'm a little biased, since his thread was what inspired me to make this one
[GUIDE] Want to learn how to theme? - by @theimpaler747
VTS website - there are several tools you can use for apk/jar manipulation, but in my experience this is by far the most complete. The VTS website also has a bunch of tutorials on how to get started with VTS, and also how to get started with apk manipulation in general
Official Android developers' website
THINGS THAT STILL NEED FINDING
General tips
Working with Sense 6
By now people have found that Sense 6 apks are a little troublesome and it takes a bit of effort to decompile/recompile some of them. The main thing, as Raymond Ebertt stated in his post, is to make sure you are using the most up to date files. There is some conflict about which version of apktool to use, 1.4.2 or 2.0.0. It is complicated by the fact that the public release version of VTS doesn't yet work with apktool 2.0. Either version of apktool will work fine, but both might require a little tinkering with the apk. Now that the new version of VTS is out, it makes things a lot simpler, since apktool 2.x is now supported.
Those people using manual apktool, I would suggest making sure you use apktool 2.0.0beta9 - that's worked me for me where earlier versions of 2.0 failed.
As for smali, I have been using 2.0.3 since Sense 6 dropped, and not had any issues with that.
If you're using VTS, you need to put the updated binaries in the appropriate folders in C:\Program Files (or Program Files(x86))\Virtuous Ten Studio\External. The newest version of VTS ships with apktool 1.4.2 and 2.0beta9, and smali 1.5.2 and 2.0.3, so you shouldn't need to add any additional binaries.
There are also a few special-case apks:
Troublesome apks
You may have found that there are some apks that give you public.xml errors on trying to recompile them. The cause seems to be some broken images in the apk itself, and seem to affect the images used in the Sense 6 themes. You can see which ones they are by opening the apk as a zip archive and looking in the drawable-*dpi folders - the broken images all have a filesize of 0bytes.
The easiest way to fix this is to replace those images in the apk before decompiling it. Once you've done this, the apk should recompile without the above errors.
You can get all the required files from com.htc.resources.apk, but to make things a bit easier, I have zipped up the required files for most of the faulty apks.
You can download them here
Note that these zips contain compiled 9.pngs, so you need to copy them into the apk before decompiling - they won't work properly if you put them into an already decompiled project.
If there are any problems with the zips, please let me know.
If your apk still fails to compile, just double check all the drawable-*dpi folders and make sure there are no 0byte images. If there aren't, then there is another issue with your project.
========
Phone.apk. This app often fails to compile due to some issues with strings.xml. Basically, there is a special character (٪) that gets replaced with a normal % on decompiling.
You have 2 options to fix this:
1. use the error log to identify which symbols need replacing (the log will tell you which xml, and which line, needs fixing)
2. grab the fixed files I added to the folder I linked above - these are decompiled files, so will need to be placed into your decompiled apk
========
There is another reason I've found for some apks not to compile. Some of the apks, eg Messages, have issues with apktool 2.0 whereby the package name of the apk gets altered.
If you get an error saying that it could not find resources for package com.htc, you need to check the AndroidManifest.xml - you'll find that package name has been changed to com.htc.
Two ways to deal with this - either re-edit the package name to the original (which can usually be found somewhere further down in the AndroidManifest.xml, or use apktool 1.4.2 to de/recompile the apk. Thanks to @hawknest for pointing out the cause of this one.
Frameworks and tags
Just a short note on frameworks, since many people seem to misunderstand them. When you install a framework, the resources.arsc is taken out of the file and put inside an .apk file in your C\:<User>\apktool\framework folder, where it essentially acts as a look up table for decoding the resources inside any given apk. By default, framework-res gets installed as 1.apk, com.htc.resources as 2.apk. Go take a look in your installed framework folder, you'll see what I mean.
The reason you need to install frameworks for each Android distro you're using is precisely because of their function as a look up table. Let's say you install AOSP frameworks - great, you can now decompile AOSP apks just fine. But what if you're using a MIUI rom, or Sense, or Touchwiz? These distro variants all contain resources that the stock Android doesn't and so when you try to decompile a Sense apk that has non-standard resources within, the AOSP frameworks will fail. Ok, no problem, install the Sense rom frameworks instead and it'll work just fine. Problem is, when you installed the Sense frameworks they overwrote the AOSP ones. So now, if you want to go to use an AOSP apk, you first need to reinstall those frameworks again. What a pain, right?
This is where tags come in. If you install the frameworks using a tag specific to the Android distro, in the apktool/framework folder you'd see 1-aosp.apk, 1-sense.apk, 1-miui.apk etc. Now, when you're decompiling apks from a particular distro, just use the tag you assigned the frameworks to let apktool know which set of frameworks to use. This way, you can have frameworks for multiple distros installed at the same time.
Just to clarify, all the frameworks from a given distro need to have the same tag. So, for example, your installed frameworks from AOSP would be called 1-AOSP.apk, 2-AOSP.apk, 127-AOSP.apk etc. When you decompile using a tag, you're telling apktool to use all the frameworks with that tag as reference tables for the decompile. If all your frameworks from one distro have different tags, apktool won't find all the references it needs, and you'll get an error about missing resources and a failed decompile.
As for when you need to install frameworks - as I said, the purpose of installing them is to provide a lookup table for decompiling resources. So you really only need a set of frameworks when you're working with something that's likely to have unique resources. This will either be when dealing with different distros - AOSP, MIUI, Sense etc - or when there has been a version change - 4.3 to 4.4, or Sense 5 to Sense 6 etc. If you're working with a Sense 6 build of one rom, say Renovate, and you want to decompile an apk from InsertCoin, you can use the same frameworks for both, since they are both based on Sense 6, and we rarely tend to add new resources to framework files.
Public id's
Public id's are how smali code call on a particular resource. Public.xml lists all the public ids for every resource contained within a particular apk. Pretty much all apks use a public id format of 0x7fxxxxxx, which means that the resource attached to that id can only be used by the apk it is contained in. So, if for example, you're looking in smali and you see the id 0x7f100000. You search public.xml and you see that 0x7f100000 is allocated to type="string" name="app_label". So you know that that bit of smali code is setting the app label. This can also work the other way round - say you have an image and you want to find the smali code that draws it on screen. Find the name of that image and look it up in public.xml. Say it has an id of 0x7f000010. So you just search all the smali for that reference and have a look at the resulting files.
This is true for all apks in HTC roms except for three. Since com.htc.resources.apk, framework-res.apk and framework-res-htc.apk act as central repositories of resources for other apps to use, they each have their own unique public ids so system apps know which one to call a resource from.
Code:
framework-res = 0x01xxxxxx
com.htc.resources = 0x02xxxxxx
framework-res-htc=0x03xxxxxx
So, next time you're looking in smali and you see an external reference with one of the above 3 formats, you'll know exactly which framework apk to look in
Note: the formats shown above are how they appear in the decompiled public.xml of that apk. When other apps call these public ids in smali, the first 0 after the x is dropped.
For example, say the clock widget wants to use an image from com.htc.resources. In com.htc.resources/public.xml, that image might have the public id 0x02000001. But in the clock widget smali where that image is called, the public id would be given as 0x2000001.
What are the Sense 6 themes?
This is the easy bit! If you open Settings/Personalise/Theme, you'll be presented with the four built-in themes:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Where are the Sense 6 themes?
This is where things get complicated.
There are four themes, each of which is split into five categories. The themes are called:
The system wide theme is controlled by hex colour codes located in colors.xml and styles.xml of com.htc.resources. This controls the majority of system apps.
If you look at com.htc.resources.apk/styles.xml line 2047 for example, you'll see that there are entries called:
Code:
etc, starting from line 2047
Categories 1-4 are represented by the four boxes along the top of the theme preview. The fifth category is defined by HTC within apks as Category 0, and this is the default category. It is used when the code within the apk doesn't specify which category to use (more on this later). With the default theme, you'll probably have noticed that various HTC apps have different coloured header bars, which correspond to the four boxes on the preview image:
So if you wanted to change the colour of the dialer, you'd edit the colour codes for HtcDeviceDefault.CategoryOne. If you were using the second theme, the orange one, you'd edit ThemeOne.CategoryOne to change dialer header, and so on...
I've managed to track down which category each HTC app uses, but if there are any I'm missing, please let me know
Category 0
HTC Backup
Internet
Settings
Setup
Tips & Help
Scribble
All apps launched while in Car mode
Category 1
Calendar
Contacts
Mail
Message
Tasks
Phone
Category 2
Calculator
Clock
Stocks
Voice recorder
Weather
Category 3
Camera
FM radio
Music
Category 4
Didn't actually find any apps that seemed to use this category
All of these apps use the specified category from com.htc.resources, so that's where you should edit it. There are some HTC apps that have seem to have their own internal themes:
Prism.apk
HMS_Gallery.apk
HTC-IME.apk
Video_Center.apk
HtcExtremePowerSaverLauncher.apk
EasyAccessService.apk
so they have their own specified themes and categories within the colors and styles.xml of their own apk. There may be other apks as well, I just haven't spotted them yet. They read the system flag to determine which Theme to use, but then use their own categories for various elements within the app.
So Prism for example will set the overall Theme according to what's been set in the Theme picker but then will use its own internal categories. From my testing so far, all aspects of Prism (app drawer header, Blinkfeed, app drawer icon overlay) seem to use Category 4 colours from within Prism.apk. Haven't looked into any of the other apps listed above!
How are the Sense 6 themes used?
So, which theme the system is using is determined by you, via the Theme Picker. As for which category an app uses, that is determined within the java code - thanks to @Mikanoshi for some more detailed info
Still not sure where the current theme flag is set, so that the other themed apps (Gallery, Prism etc) know which theme to use. I'm guessing framework2.jar or framework3.jar, though I guess it doesn't really matter!
As for the preview images, these are generated the first time the theme picker is opened, and then cached in /data/data/com.htc.home.personalize/files/themePreview/ - again, thanks to @Mikanoshi for more detailed info. The colour bar across the top of the previw image is the multiply_color from categories 1-4 of that theme.
If you want the Theme picker screen to show your edited themes, rather than the default ones, you'll need to delete these cached images. This can be done by full wiping, but obviously not so convenient. The other option is to add the following line
Code:
delete_recursive("/data/data/com.htc.home.personalize/files/themePreview");
somewhere in the updater-script of your rom/theme zip.
How to add a new theme
The four built in themes offer a great way to offer multiple variations of your theme. But what if 4 options aren't enough? Why not add a 5th?
To add your own theme, it's probably easiest to start with com.htc.resources as this requires the most edits. The two folders you'll need to focus on are drawable and values.
In values/styles.xml, the easiest thing to do will be to duplicate the whole block of Theme.Three entries, rename them all to Theme.Four and change the colours as you want them. You'll also need to duplicate all the htcprogress_themethree_*.xmls in the drawable folder, rename them to themefour and edit the colours,
The last step is to edit values/arrays.xmls. This will register your new theme as a usable resource. You need to
add your new theme to the multipleColorThemes array - this tells the system that ThemeFour now exists
add a new ThemeFourarray, which lists the 5 categories -
add a 5th entry to the wallpapersand wallpaper_themesarrays - this will set the default wallpaper for your theme (you can also edit this array if you want our default wallpapers to have a different filename or file type)
create new progressBarArrayarrays for ThemeFour and the four categories
If in doubt, just look for all the ThemeThree stuff, duplicate it and rename to ThemeFour. That's com.htc.resources done. Now you just need to add the ThemeFour stuff to the other 6 apps that use the theme system (see previous list). In each apk, you need to edit arrays.xml, add all the new htcprogress_themefour_*.xmls to the drawable folder, and the new ThemeFour stuff to styles.xml. If you don't add ThemeFour to an app, if you've applied your theme centrally and then open that app, the app will default to the stock green theme.
And that's it! Wipe the theme preview cache as previously mentioned, and your theme will show up nicely. Not sure if there is a limit to the number of new themes that can be added...maybe it just depends on how bored you get
There is one small issue that remains. As previously mentioned, the colour bar across the top of the preview is generated by the multiply_color entries of categories 1-4. However, for your new theme, you'll note that the colour bar remains green. Since the themes always revert to the green one when there is missing info relating to the new theme, I suspect there must be a smali array somewhere where the themes are also registered. Since the new theme is not declared there, the preview generator doesn't know to look for ThemeFour.
It is the only remaining bug, but it does annoy me! So if anyone finds where in smali these preview colours are generated, please do let me know!!
Well, that's all for now. Apologies for the slightly wordy post, a consequence of me thinking out loud. I will say one more thing though. When Sense 6 first landed, I was not a fan of these new themes at all. But having spent time exploring and getting to know how they work, I actually really like them now. Overall, theming Sense 6 requires less smali edits than Sense 5/5.5 did, and the theme picker aspect is actually quite powerful....how else could you offer 4 variants of a theme so easily. I suspect that it's better for themers like myself, who theme specific roms, than it is for standalone themers.
Happy theming!!
Article originally posted here
How to stop the 4x1 weather clock changing colour according to time of day
In Sense 6 the 4x1 weather clock widget has a white background for daytime clocks, and dark for night clocks. Pretty neat feature, but maybe it doesn't fit with a theme you're making?
If you open
Code:
HtcWeatherClockWidget.apk/smali/com/htc/widget/weatherclock/view/WeatherClock4x1View.smali
and search for
Code:
.method protected getControls
Scroll down and you'll see
Code:
const-string v2, "background_day"
const v3, 0x7f02004d
The 0x7f02004d is the public id for common_panel_light.9.png in the drawable-xxhdpi folder. Scroll a bit further down and you'll see
Code:
const-string v2, "background_night"
const v3, 0x2080100
The 0x2080100 is the public id for common_panel.9.png in com.htc.resources. If you want to use the same image for both day and night clocks, just replace 0x2080100 with 0x7f02004d, and the clock will use the common_panel_light.9.png image for both day and night clocks. Just theme that image how you want it to look, recompile and you're done
Fringe Theming...
Ok Since fisha is so awesome and got me a spot for number 4 I will be adding to this as we progress and figure other stuff out enjoy for now!
My Tutorials are not limited to any app or by anything! I will cover how do some crazy complex theming and I will try to be as cohesive as I possibly can, within the tutorials. My main goals are usually against the grain as far as theming goes: This is stuff you won't see in other sense themes! Enjoy
Updated all links so they properly work for everyone.
Internalizing color in htcclockweatherwidget.apk & Inverting 4x1 clock
No longer applies to the updated ota.
____________________________________________________________________________________________________________________
Change small weather icons to white in smali
Oh someone forgot to point out how to change the weather icon for the small weather widget
weatherview.smali line 77 if you have smali debugging turned on/ may be slightly different if you don't, possibly a few lines away.
Change both to dark.
Small Weather Icons:
Change large weather icons to white in smali
Yeah props to whoever found this not sure who but I'll add it to this as well.
goto: WeatherClock4x1View.smali
search for vectorgraphic_light_xl
change them both to vectorgraphic_dark_xl
Large Weather Icons:
____________________________________________________________________________________________________________________
Change the vertical divider in 4x1 clock to an image that can be themed, never using com.htc.resources calls to do it.
No longer applies to the recent versions of sense 6
____________________________________________________________________________________________________________________
____________________________________________________________________________________________________________________
Removing the SystemUI notification drawer bg fade in/fade out..
Ok guys I got another one i just figured out... If anyone figures out how to edit the transparency of the fade itself that would be awesome...
I tried but the only thing i could get it to do without crashing was removing it.
The main purpose of this is to expose the statusbar all the time which is only possible when disabling this animated smali fade method.
Any other questions about the ui feel free to ask.
In SystemUI.apk you'll be looking in PhoneStatusBarView.smali
Search for this:
Code:
.method public panelExpansionChanged
Delete that entire method from lines 581-875 (lines will match) - if you have smali debugging turned on which I always do when playing in smali enjoy.
____________________________________________________________________________________________________________________
____________________________________________________________________________________________________________________
CHANGING FONTS SELECTIVELY IN ANY APP NOT CAUSING A GLOBAL CHANGE
This tutorial is somewhat complex and not for the faint at heart!
Oh and I'm not responsible if you bootloop your phone from this; symlinking the wrong things can cause bootloops. So please pay close attention. And look at my .zip which I will be adding!
This is not a font pack or anything like that! There is only one other person we know has been able to do this @Ajthescot for NEVER telling us, lol no need though after a year of tinkering I figured it out.
Ok this is a special tutorial for the SystemUI, but can work anywhere in any app. I'm going to go over one of the most epic changes I have ever managed to accomplish. I managed to change a selective font that htc does not use, then call on its class/font-family within styles. Look at the clock font vs everything else. This change is selective not global, which is exactly what we are after!
Though if an app calls on monospace like a market app it will display this new font we are about to use. Like some apps specifically logcat apps like using monospace b/c its easier to see the code so keep that in mind before doing this and choose your font wisely!
Example:
First were going to need a font we want to use select any font you can find you may want to selectively use... I chose arame-regular.ttf
We are also going to need SystemUI.apk decompiled.
I'm gonna break-down how android font family's and how font styles work in general first b/c you need to have an understanding of them to change them selectively.
Htc uses a fontfamily known as sans-serif but in actuality those fonts are basically anything with droid as a prefix and both sans or serif as a suffix. Not that it uses all of them. Ok thats what base htc does right but through the updater script they manage to symlink them
Example of symlinking:
Code:
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
This essentially is saying: ok for every spot DroidSans.ttf would be used now Roboto-Regular will fall in its place.
Example and list of roboto styles that have been symlinked in sense 6.0
Code:
android:fontFamily="sans-serif" // roboto regular
android:fontFamily="sans-serif-light" // roboto light
android:fontFamily="sans-serif-condensed" // roboto condensed
android:fontFamily="sans-serif-thin" // roboto thin
Now each family has a style as you can see here
these are the 12 style variants that are possible: android:textStyle=" "
Regular
Italic
Bold
Bold-italic
Light
Light-italic
Thin
Thin-italic
Condensed regular
Condensed italic
Condensed bold
Condensed bold-italic
Ok enough of that lets get down to brass tacks... We need the SystemUI (the app i chose for demonstration) decompiled and an updater script and a .zip
Empty everything out of the .zip except the system/fonts folder and the meta-inf folder and the system/priv-app folder everything else delete it. Delete everything within the system/priv-app folder and then you can even delete all the fonts inside of the system/fonts folder as well.
I decided on a font family that htc does not use anywhere or any place its known as monospace the real font name is DroidSansMono.ttf. It's what we will be symlinking to.
Now that we have our .zip with nothing left in it except the meta-inf stuff and some empty folders we are going to add our custom font to the system/fonts folder make sure it is a standard .ttf font and make sure it has all the characters you'll be needing when you apply the font to wherever you want.
Then we are going to open our updater-script and simply delete everything (use your rom .zip and it's updater-script) its easier that way. We are going to add our symlink lines into it. I used a font called arame to do this but any true type font will suffice. This is how your updater-script should look the mount ext's may be different if your on the m8
Code:
ui_print("");
ui_print("............................................");
ui_print(": :");
ui_print(": Installing :");
ui_print("............................................");
ui_print("");
ui_print("");
set_progress(0.01);
ui_print("");
ui_print("");
ui_print(">>> Mounting partitions");
assert(mount("ext4", "EMMC", "/dev/block/mmcblk0p37", "/system") || ui_print("(system is mounted already)"));
assert(mount("ext4", "EMMC", "/dev/block/mmcblk0p39", "/data") || ui_print("(data is mounted already)"));
ui_print("");
ui_print("");
ui_print("");
ui_print("");
ui_print(">>> Writing Data & System");
package_extract_dir("data", "/data");
package_extract_dir("system", "/system");
ui_print("");
ui_print("");
ui_print("-- Creating additional symlinks");
symlink("Arame-Regular.ttf", "/system/fonts/DroidSansMono.ttf");
assert(unmount("/data") || ui_print("(Data is unmounted already)"));
assert(unmount("/system") || ui_print("(System is unmounted already)"));
set_progress(1.0);
ui_print("--");
ui_print("--Installation Complete!");
ui_print("--");
ui_print("--");
Ok now save and close you're updater-script and add it back into our .zip at META-INF\com\google\android\ overwriting the original.
Now lets switch gears and go back to the decompiled SystemUI.apk.
Lets open status_bar_expanded_header.xml if you look at line 5
you'll see the style I was after: highlighted:
Code:
@style/ExpandedClock
Now lets open that style Data/res/values/styles.xml Search for:
Code:
<style name="ExpandedClock" parent="@*android:style/TextAppearance">
Now were going to change the android:fontFamily for that given style: we are going to change it to monospace. It was originally sans-serif-light.. Your new style will look like:
Code:
<style name="ExpandedClock" parent="@*android:style/TextAppearance">
<item name="android:textSize">@dimen/clock_fontsize</item>
<item name="android:textStyle">normal</item>
<item name="android:textColor">@com.htc:color/cellitem_avatar_stroke</item>
<item name="android:fontFamily">monospace</item>
</style>
Recompile the systemUI.apk and either add it to your .zip in system/priv-app folder or push it to system/priv-app, but honestly if you didnt know that you probably shouldn't be doing this tutorial.
Flash the font tester.zip and push the ui
Changing the mono font and then selectively choosing it using the monospace font family. Now whenever you want to use your special font somewhere for design or whatever, you can use it just by either replacing the android:fontFamily with monospace or adding an android:fontFamily line, to the style you want to specifically change.
Here is my .zip: https://www.dropbox.com/s/2yohzroxz9ilsab/Font_Tester.zip
It took me a year to get this. Enjoy
____________________________________________________________________________________________________________________
____________________________________________________________________________________________________________________
Animate the status_bar_close_on and keep the carrier label at the same time.
Ok I stated above if you had any questions about the ui feel free to ask. This tutorial is a result of one of those questions.
Example:
I made several attempts at this and it was weird, it didnt want to work at first, but after I tried a few different ways, I got this way to work.
The methods we have used since ICS still work don't get me wrong but they dont work if you want to keep the carrier_label. The SB image itself will cover the carrier_label. If you try to move the carrierlabel process to expanded_layout or try adding and ImageView into either .xml like we've done in previous builds: Ics/jb/even kk. Just wanted to point that out.
Ok lets get down to it we are going to need a decompiled systemui.apk and VTS.
You will obviously need some knowledge of photoshop or after-effects or some program that will allow you to manipulate images within .9 patches.
Also for the second part or even the first you will need to know how to manipulate .9 images using the draw9patch tool provided in your android-sdk. Windows=ie:start/run/cmd/draw9patch hit enter if you have java properly in your paths it'll load the draw9patch tool. If you need I can cover .9 images in a different tutorial but there are enough tutorials on xda already about them please do some searching if you have any questions feel free to ask. Some images are very hard to patch given the complexity of the image. And depending on the animation in no way can the patch touch an abstract animation that isn't uniform so it can get crazy with the patches.
Ok lets get started we are gonna open two separate layouts
carrier_label_generic.xml
status_bar_close.xml
Ok first we're gonna go into carrier_label_generic.xml and change line 2:
From:
Code:
<com.android.systemui.statusbar.phone.CarrierLabel android:gravity="center" android:id="@id/handle" android:background= [user=3944923]@drawab[/user]le/status_bar_close_on" android:visibility="invisible" android:layout_width="fill_parent" android:layout_height="@dimen/close_handle_height"
To:
Code:
<com.android.systemui.statusbar.phone.CarrierLabel android:gravity="center" android:id="@id/handle" android:background= [user=3944923]@drawab[/user]le/status_bar_close" android:visibility="invisible" android:layout_width="fill_parent" android:layout_height="@dimen/close_handle_height"
We are changing the android:background from an image (status_bar_close_on.9.png) to (status_bar_close.xml)
If you want the results you saw in the first example you'll need to change your status_bar_close_off.9.png
Ok that in itself will animate between status_bar_close_on.9 and status_bar_close_off.9 but we can take it further than that if we want.
____________________________________________________________________________________________________________________
____________________________________________________________________________________________________________________
Add Operator_name to statusbar move signal_cluster to the left and then move wifi to the right of the signal itself
My findings:
Really I found that the real carrier_label id can't be called on in the status_bar without it crashing! The method they use in CM does not work and my guess is b/c the ID for handle is actually in some way tied to the carrier_label_generic id itself thus we can't call on it b/c it wants to expand the handle layouts as well. Makes sense since the handle ID is called right out of the com.android.systemui.statusbar.phone.CarrierLabel. I could be wrong though who know's maybe someone else will see something I didn't.
Please if you have any insight on how to get the actual process itself into the statusbar using sprint please let me know I've gotten as far as getting it to display the layout for it but no txt!
I'd also like to point out there are two way's of doing this: I figured this is the most simple method of the two... The other one requires adding a line to status_bar.xml where the plmn_label id lies now but turning that on doesnt work unless you give it a string value which is more adding vs modifying what is already there so I figured this way was easier hope you enjoy.
Oh and since the Id for plmnLabel is a textview in status_bar.xml and not the actual process call in smali: it doesnt act like carrier_label anyway so it's moot point!
Using the call for it <com.android.systemui.statusbar.phone.CarrierLabel will result in a ton of errors in logcat and multiple force closes.
RESULTS:
Ok your gonna need a decompiled SystemUI.apk - open status_bar.xml and signal_cluster_view_generic.xml also open values/strings
Were going to go into status_bar.xml first move the view_stub line so that is directly above the notification_icon_area id
Code:
<ViewStub android:id="@id/signal_cluster" android:inflatedId="@id/signal_cluster_tree" android:layout_width="wrap_content" android:layout_height="wrap_content" />
<LinearLayout android:orientation="horizontal" android:id="@id/notification_icon_area" android:layout_width="0.0dip" android:layout_height="fill_parent" android:layout_weight="1.0">
This will move the cluster to left now lets switch over to signal_cluster_view_generic.xml
we are gonna move some lines around
You're gonna move this line:
Code:
<ImageView android:id="@id/wifi_signal" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginLeft="@dimen/status_bar_system_icon_margin_left" android:layout_marginRight="@dimen/status_bar_system_icon_margin_right" android:scaleType="center" />
So that it falls right above the airplane ID at the bottom so move the whole line.
This will flipflop the wifi/signal cluster so that the wifi falls to the right of the signal bars themselves.
Next we're gonna turn on the operator name:
in signal_cluster_view_generic.xml you're going to see this line
Code:
<TextView android:textAppearance="@style/TextAppearance.StatusBar.Clock" android:gravity="center_vertical" android:id="@id/operator_name" android:visibility="visible" android:layout_width="wrap_content" android:layout_height="fill_parent" android:text="@string/orange_fr_operator_name" android:paddingStart="2.0dip" android:paddingEnd="2.0dip" />
Move it to the top where wifi was before and set its visibility to visible... You turned on the operator name ID
Now lets goto string and look for orange_fr_operator_name goto that line and change orange F to your actual Service Provider and you're done. Save that and compile.
Here's my xml's if you want to use them and you still want the the clock back just set the visibility on the clock line to visible!
https://www.dropbox.com/s/0e3dxt32jh0axq8/status_bar.xml
https://www.dropbox.com/s/7dv9yxbtt2f22sk/signal_cluster_view_generic.xml
____________________________________________________________________________________________________________________
____________________________________________________________________________________________________________________
Making the header in prism/blinkfeed into an image instead of the multiply color
This could have been done several different ways this was just me trying to change it and this is how i eventually accomplished it.
Example:
think it was the second half of this that did it.!!!!
Step 1 add an image into drawable-xxhdpi mine looks like this I use a .9 but I imagine any image that fits the space will do...I made this .9 for 5.5 so it works... I will admit I did this slightly different than some would have you could also use the regular common_app_bkg_top_full.9.png in the app except yeah whatever, like i said it doesnt matter what image name you use.
Ok resize the common_app_bkg_top_full to a .9 that will suit the spot and image you want for the header... Im not going to get into how to .9 certain images but yeah you get the idea mine looks like this so there is no distortion in the gradient.
Ok Lets dig in... Open prism were gonna open a few things... Open values/styles.xml and values/drawables.xml you dont need to add an attr line for this like i believe someone else pointed out for resources this will carry either way...
First we are gonna edit line 5 in drawables.xml from
Code:
<item type="drawable" name="common_header" [user=3944923]@drawab[/user]le/zero_dummy_asset</item>
to
Code:
<item type="drawable" name="common_header" [user=3944923]@drawab[/user]le/common_app_bkg_top_full</item>
Then were gonna go to styles I edited a few lines in styles.
Then we goto
<style name="HtcActionBar">
change it from
Code:
<style name="HtcActionBar">
<item name="android:panelFullBackground" [user=3944923]@drawab[/user]le/common_app_bkg_top_full</item>
<item name="android:background">?multiply_color</item>
<item name="android:drawable" [user=3944923]@drawab[/user]le/common_app_bkg_top_full_land</item>
to
Code:
<style name="HtcActionBar">
<item name="android:panelFullBackground" [user=3944923]@drawab[/user]le/common_app_bkg_top_full</item>
<item name="android:background" [user=3944923]@drawab[/user]le/common_app_bkg_top_full</item>
<item name="android:drawable" [user=3944923]@drawab[/user]le/common_app_bkg_top_full_land</item>
Then do the same for
Code:
<style name="ActionBarActionMode" parent="@*android:style/Widget.DeviceDefault.Light.ActionMode.Inverse">
<item name="android:background">?multiply_color</item>
<item name="android:height">?android:actionBarSize</item>
<item name="android:titleTextStyle">@style/ab_primary_textview_style</item>
<item name="android:subtitleTextStyle">@style/ab_secondary_textview_style</item>
</style>
change that to
Code:
<style name="ActionBarActionMode" parent="@*android:style/Widget.DeviceDefault.Light.ActionMode.Inverse">
<item name="android:background" [user=3944923]@drawab[/user]le/common_app_bkg_top_full</item>
<item name="android:height">?android:actionBarSize</item>
<item name="android:titleTextStyle">@style/ab_primary_textview_style</item>
<item name="android:subtitleTextStyle">@style/ab_secondary_textview_style</item>
</style>
And thats how we change the multiplier header in prism from a color to an image hope you enjoy!
Add custom navbar to hotseat.xml
open values/ids.xml
and add a value to the bottom i named mine background name it whatever you want
prism.apk layout/hotseat.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<com.htc.launcher.hotseat.Hotseat android:clickable="true" launcher:cellCountX="@integer/hotseat_cell_count" launcher:cellCountY="1"
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:launcher="http://schemas.android.com/apk/res/com.htc.launcher">
[COLOR="DeepSkyBlue"] <ImageView android:layout_gravity="bottom|center" android:id="@id/background" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src= [user=3944923]@drawab[/user]le/home_nav_bg" android:scaleType="fitXY" />[/COLOR]
<ImageView android:layout_gravity="bottom|center" android:id="@id/hotseat_gardient" android:layout_width="@dimen/button_bar_background_width" android:layout_height="@dimen/button_bar_background_height" android:src= [user=3944923]@drawab[/user]le/home_launcher_bg" android:scaleType="fitXY" />
<com.htc.launcher.CellLayout android:layout_gravity="center" android:id="@id/layout" android:paddingLeft="@dimen/button_bar_width_left_padding" android:paddingTop="@dimen/button_bar_height_top_padding" android:paddingRight="@dimen/button_bar_width_right_padding" android:paddingBottom="@dimen/button_bar_height_bottom_padding" android:layout_width="wrap_content" android:layout_height="fill_parent" launcher:cellWidth="@dimen/hotseat_cell_width" launcher:cellHeight="@dimen/hotseat_cell_height" launcher:widthGap="@dimen/hotseat_width_gap" launcher:heightGap="@dimen/hotseat_height_gap" launcher:maxGap="@dimen/workspace_max_gap" />
</com.htc.launcher.hotseat.Hotseat>
Ok small flaw I noticed with this which we are gonna fix. If you look closely you will see a divider in the navbar that shouldnt be there... You will also need to edit something in lockscreen to get rid of it there its at the bottom of the tutorial...
Example:
Ok now in prism.apk open main_launcher.xml
you're gonna change line 20 from
Code:
<ImageView android:layout_gravity="bottom|center" android:id="@id/nav_bar_div" android:paddingLeft="@dimen/margin_l" android:paddingRight="@dimen/margin_l" android:layout_width="fill_parent" android:layout_height="wrap_content" android:src= [user=3944923]@drawab[/user]le/common_b_div" android:scaleType="fitXY" />
To:
Code:
<ImageView android:layout_gravity="bottom|center" android:id="@id/nav_bar_div" android:paddingLeft="@dimen/margin_l" android:paddingRight="@dimen/margin_l" android:layout_width="fill_parent" android:layout_height="wrap_content" android:scaleType="fitXY" />
All we did was remove the src call android:src @drawable/common_b_div"
You could keep it for design purposes but this is just how to remove it..It obviously was interfering with my nav bar bg.
----------------------------------------------------------------------------------------------------------------------------------------------------------
Ok the divider in lockscreen lets take care of that
Example:
Ok open Htclockscreen.apk res/layouts/main_lockscreen_keyguard_host_view.xml
your gonna change one line in it: line 26
Code:
<com.htc.lockscreen.ui.footer.NavigationBarDivider android:layout_gravity="bottom" android:id="@id/navigation_bar_divider" android:background= [user=3944923]@drawab[/user]le/common_b_div" android:visibility="gone" android:layout_width="fill_parent" android:layout_height="@dimen/navigation_bar_divider_height" android:layout_marginLeft="@dimen/common_dimen_m1" android:layout_marginRight="@dimen/common_dimen_m1" />
Remove the :android:background= @drawable/common_b_div" from that line no more grey divider...Enjoy
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Changing the call button in dailer to an stand alone themable image!
Ok I wont be going over how to theme the whole dialer others have explained certain aspects of it and my questions in some posts answer other questions if you have any feel free to ask there are tons of awesome devs that respond very quickly.
This took me forever to find since center_button id in the cmdbar.xml is very confusing when it comes to figuring this out... Its not the center_button id we are after its the phone_btn_call_rest in drawables.xml thats the actual id we are going to be replacing with an image id we will add...
Ok lets dig in decompile dialer if you havent already
make an image mine is 717x164 which is the exact width and height of the button in the standard dialer.
I did not make my image a .9 since I will only be using this specific image for only this spot.
Ok add the image into the drawable-xxhdpi folder and right click on the project open resource manager and add the id for it copy the id when it comes up and keep that safe...
Ok now were gonna open values/drawables.xml were gonna look at line 33 and find its public value
from:
Code:
<item type="drawable" name="phone_btn_call_rest">#ff000000</item>
I changed mine to and @drawable while testing,
but you dont have to since it has no effect on the outcome since we are changing this id in itself to something else in smali.
ok back into public.xml and search for the phone_btn_call_rest id for me its 0x7f020068
were gonna search for in ButtonGroup.smali
Code:
move-result-object v3
check-cast v3, Lcom/htc/htcdialer/widget/keypadbtn/HtcKeypadBgBtn;
const v0, 0x7f020068
Now simply change the phone_btn_call_rest Id to the new image id you created earlier for your new drawable. save and compile done Enjoy!
Example:
Hope you enjoy the tutorials.
Advanced Theming for Sense 6
I was fortunate enough to of had the opportunity to start theming Sense 6 before it even hit the stage as a custom ROM, but that does not give me an advantage at all. Sense 6 is a whole new concept in theming and at the best of times, an aggravated experience. So much has changed between Sense 5.5 and Sense 6 that I don’t even know where to begin. I honestly think that HTC had the common Sense kicked out of it. When life throws you lemons, you theme them….
These tutorials are designed for themers that have knowledge with xml and smali editing. There are several excellent threads that explain the concepts and the "how-to's" for these kinds of edits, therefore, I will only focus on theming issues.
The first thing that I found out was, I needed to update VTS in order to decompile any of the Sense 6 apks. My VTS was outdated and you should carefully check that you are up to date with smali, baksmali.jar’s and using a current version of apktool. Be sure to visit this page and download the latest versions of the smali.jar’s found here and replace them in the appropriate VTS folders. This will resolve most decompiling errors that you may encounter. The other errors, well it’s just the apk and way that it’s being decompiled at the moment. There’s not too much you can do other than getting a different apk and trying it.
Transparent Prism Appdrawer Background
Well, what I thought turned out to be an easy and wonderful edit, in fact, a little bug suddenly appeared.
It seems that the Search for Apps feature in the appdrawer shares the same background as the appdrawer itself. As as consequence, there is a double transparent background ontop of each other which I don't find appealing the least.
After a bit of investigating, I found that adding a custom color to isolate the appdrawer background fixed this problem.
Step 1
You're going to need to make a custom color edit in the color.xml of Prism. You can call it whatever you want and make your transparency to your choosing. For the dark_ap_background_color, you can leave it as it is or change it to your desired shade. I changed mine to a black/blue shade.
Step 2
Navigate to specific_all_apps_pagedview.xml
Within this string
Code:
<com.htc.launcher.pageview.AllAppsPagedViewHost android:id="@id/all_apps_paged_view_frame" android:background="?dark_ap_background_color" android:paddingTop="@dimen/all_apps_host_paddingTop" android:paddingRight="@dimen/all_apps_host_paddingRight" android:layout_width="fill_parent" android:layout_height="fill_parent"
search for
Code:
android:background="?dark_ap_background_color"
Replace ?dark_ap_background_color with your new color name such as @color/custom_color
Step 3
Using the search panel, you want to search within the smali folder for the following. The original thread can be found here. All credits to the authors.
Code:
com/android/htc/launcher/Launcher.smali
Search for this entry
Code:
.method public updateWallpaperVisibility(Z)V
If you see a const/high16 v2, 0x10 (not 0x100000 as shown) you need to update your smali.jar’s.
Edit 0x100000 to be
Code:
const/high16 v2, 0x0
Save your edits, compile and you’re finished.
Results
Custom Panels for the WeatherClockWidget.apk
Adding custom panels to the WeatherClockWidget.apk is fun. This procedure requires a bit of photo editing skills with Photoshop (or something slimar) and edits in layout and smali (if you want a custom 4x1 clock background).
Step 1.
Prepare a custom panel as shown. The dimensions are 1040 x 236 (my preference)
Save your panels in the drawable-xxhdpi folder. I prefer using a fixed name such as razor_clock_panel and razor_panel. It’s entirely your preference but don’t forget the name as you will need them for the next steps.
If you just want to add a panel for the weather conditions (1040x238), you will only need to edit the layout.xml.
Step 2
Edit the following string
Code:
xmlns:android="http://schemas.android.com/apk/res/android">
<ImageView android:id="@id/background_panel" android:background="@com.htc:drawable/common_panel" android:layout_width="@dimen/weatherclock_base_width" android:layout_height="@dimen/weatherclock_base_height" android:layout_marginLeft="@dimen/weatherclock_base_margin_left" android:layout_marginTop="@dimen/weatherclock_base_margin_top" />
You will need to change com.htc:drawable/common_panel" to the following
Code:
@drawable/razor_panel
It should now appear as this with your new panel name.
Code:
xmlns:android="http://schemas.android.com/apk/res/android">
<ImageView android:id="@id/background_panel" android:background="@[COLOR="Red"]drawable/razor_panel[/COLOR]" android:layout_width="@dimen/weatherclock_base_width" android:layout_height="@dimen/weatherclock_base_height" android:layout_marginLeft="@dimen/weatherclock_base_margin_left" android:layout_marginTop="@dimen/weatherclock_base_margin_top" />
Save your edit, compile, and you’re finished.
Results
Now if you want to add a custom 4x1 clock background as previously explained by @fisha21, the first thing you need to do is make your custom panel the same way as explained above at 1032x328 and save that in the drawable-xxhdpi folder.
Next
Compile your apk and place it on the desktop. Import the apk again and go to the Public.xml
Copy down the new Public ID for your custom panel. Follow the steps explained by fisha21. Instead of replacing the Public ID with the common_panel, use your new Public ID.
Save your edit, compile, and finished.
Results
Inverting Issues (Not intended for this Thread)
A lot of users are asking about inverting tips. I wasn’t going add any tutorials for that in this thread, but I figured I could do a couple until I get around to making a thread on it.
There are a few apks with Sense 6 that do not call on the resources colors. They do call on framework colors and if you don’t test your theme completely, you’ll probably find a disappointing background somewhere when you are finished. This tutorial will cover two elements that are not themed by resources, the call settings and mobile network settings background.
These two backgrounds call on the white color (line 4) in the framework color.xml. There are two ways to change the background for call settings and mobile network. The easiest way would be to redirect the color to another color in framework just as black as in my case. That’s great if you are running a black theme. Here’s the steps for that.
Step 1
Get the public ID for the white color in the Public.xml of frameworks which is 0x0106000b. Directly under that you’ll see the Public ID for black, 0x0106000c. Copy both down.
Step 2
Open the phone project and do a search for Public ID white 0x0106000b. NOTE: You need to remove the 0 after the x, so your search should be 0x106000b. You will be searching for this following smali and string.
Code:
com/android/phone/widget/ThemePreferenceActivity.smali
invoke-virtual {p0}, Lcom/htc/preference/HtcListActivity;->getHtcListView()Lcom/htc/widget/HtcListView;
move-result-object v3
const v4, 0x106000b
invoke-virtual {v3, v4}, Landroid/view/View;->setBackgroundResource(I)
Step 3
Edit the value indicated above. Compile and you’re finished.
If your background is a different color, let’s say light green, you’re going to need to make a custom colour.
Step 1
Go to the color.xml of the Phone apk. Copy one of the strings and paste it near the bottom or top. Rename the string to your custom name and change the colour hex.
Step 2
Build the apk, place on your desktop and import it again. Go to the Public.xml and copy your new ID for your custom colour. Now, repeat the steps above and search for the Public ID white 0x106000b and replace that with your new ID. Compile and you’re finished.
Results
Inverting Data Usage Background
The data usage background can be found in the Usage.apk. Once decompiled, you will need to go to the layout.xml.
Step 1
Search in the main_content.xml and look for this string.
Code:
<?xml version="1.0" encoding="utf-8"?>
<com.htc.usage.widget.MyFrameLayout android:id="@id/mycontent" android:background="[COLOR="Red"]#ff000000[/COLOR]" android:layout_width="fill_parent" android:layout_height="fill_parent"
xmlns:android="http://schemas.android.com/apk/res/android" />
For this quick tutorial, the edit has been done already in black. Make your backgound to the colour you prefer and compile. Finished.
Results
Inverting Weather.apk Backgrounds
Another theming disaster is the Weather.apk. This background can be changed by following the framework.apk Public ID for white method or making a new color reference in the Weather.apk, color.xml.
Step 1
If you just want a black background like I did, all you need to do is search the Weather.apk smali files for 0x106000b. There will be 4 hits and all refer to backgrounds.
Search for
Code:
0x106000b
Look for the following string in WeatherEntry$CityListAdaptor.smali
Code:
iget-object v14, v0, Lcom/htc/Weather/WeatherEntry$CityListAdapter;->mLayout:Landroid/widget/RelativeLayout;
const v15, 0x106000b
invoke-virtual {v14, v15}, Landroid/view/View;->setBackgroundResource(I)V
const v14, 0x106000b
invoke-virtual {v13, v14}, Landroid/view/View;->setBackgroundResource(I)V
Change 0x106000b to 0x106000c (My case I changed all 4 instances)
Step 2
If you need a different coloured background, you will need to make a custom colour in the color.xml of the Weather.apk. Please follow the instructions mentioned above on how to add a custom colour to the apk.
Background in Browser.apk when Nagivating Tabs
All credits for this edit go to @Basil3 as we double-teamed up on this one and he found it on the day-shift. Good on ya, mate.
Step 1
Get a pencil and copy this down
Step 2
Search smali in Browser.apk for
Code:
.method public constructor <init>(Lcom/htc/sense/browser/PhoneUi;Lcom/htc/sense/browser/htc/ui/CellList;)V
Within that search, you'll need to locate the following
Code:
# direct methods
.method public constructor <init>(Lcom/htc/sense/browser/PhoneUi;Lcom/htc/sense/browser/htc/ui/CellList;)V
.locals 10
const/16 v9, 0x11
const/4 v8, 0x0
const/4 v7, -0x1
const/4 v6, 0x1
const/4 v5, 0x0
invoke-virtual {p1}, Lcom/htc/sense/browser/BaseUi;->getActivity()Landroid/app/Activity;
move-result-object v2
Edit
Code:
const/4 v7, -0x1
Change to your desired smali color code. Remove the /4 from the string so that it shows
Code:
# direct methods
.method public constructor <init>(Lcom/htc/sense/browser/PhoneUi;Lcom/htc/sense/browser/htc/ui/CellList;)V
.locals 10
const/16 v9, 0x11
const/4 v8, 0x0
const v7, -0x1000000
const/4 v6, 0x1
const/4 v5, 0x0
invoke-virtual {p1}, Lcom/htc/sense/browser/BaseUi;->getActivity()Landroid/app/Activity;
move-result-object v2
Build and you're finished.
More Nasty Inverting Issues Resolved - HtcSetupWizard, HtcBackup, "Get Started Panel", Settings Issues Prism.apk
The following are inverting theme issues when dealing with HtcSetup and company apks. Each apk seems to have a specific edit so let’s start with the Prism.apk and the white panel “Get Started”
White box in Settings
There are a couple of nasty edits in the Prism.apk and I will be honest, it took me several days of trying and giving up only to get back on it again to find the fix. The first fix is a white box that you see when choosing new content in settings.
This fix is relatively easy. You need to theme the common_circle_pressed.png found in the xxhdpi folder in Prism.apk. That’s it.
White panel in Blinkfeed page “Get Started”
White panel in Blinkfeed page “Get Started” – This edit I want to recognize @Mikanoshi for providing some excellent clues on finding this edit as well as introducing me to an outstanding search tool. Cheers mate.
This was a tough one. This edit comes from the smali.
Code:
com.htc.libmosaicview.FeedGridViewText
You want to look around line 540 and search for
Code:
invoke-virtual {v0, v1, v2}, Lcom/htc/libfeedframework/FeedData;->getBooleanExtra(Ljava/lang/String;Z)Z
move-result v0
if-eqz v0, :cond_0
const v0, -0x1000000
invoke-virtual {p0, v0}, Lcom/htc/libmosaicview/FeedGridViewText;->setBackgroundColor(I)V
This edit has been done already. Don’t forget to delete the /4 after const. Build and you’re finished.
White Drop down panel – “Tap to see new stories”
This edit was strange as I seldom see this drop down panel. Any event, I found it in Prism.apk located in the
Code:
specific_feed_grid_view.xml
Look for
Code:
<TextView android:gravity="center" android:id="@id/notify_title" android:background="@color/razor_blue" android:layout_width="fill_parent" android:layout_height="@dimen/notification_bar_height" android:text="@string/notification_bar_title" style="@style/list_primary_s" />
For this specific edit, I decided to make a custom color and made the edit semi-transparent. Edit the color reference and you’re finished.
HtcBackup.apk – Background inverting fix.
If you are doing an inverted theme, you’re going to hit a couple of snags with the set up and back up apks. The HtcBackup.apk (for me) was relatively easy to do. Basically you are going to edit
Line 4: white:#ffffffff – change that to your desired color. Build and you’re finished.
Basil3 mentioned that his app was a data/app and that he had to do a different edit. Let me know if you have problems and I will add the additional fix later.
HtcSetupWizard.apk – Background inverting fix
Another issue came with this apk. With my buddy, @Basil3, we doubled teamed on my finding and fixed this mystery. The background and font are both controlled by the dark_primaryfont_color in resources. After some investigating, we found that the wizard.activity.xml contained a separate edit for the background
Code:
<?xml version="1.0" encoding="utf-8"?>
<com.htc.widget.HtcOverlapLayout android:orientation="vertical" android:id="@id/overlap_layout" android:layout_width="fill_parent" android:layout_height="fill_parent"
xmlns:android="http://schemas.android.com/apk/res/android">
<LinearLayout android:orientation="vertical" android:id="@id/base_layout" android:background="#ff000000" android:layout_width="fill_parent" android:layout_height="fill_parent">
You will need to change the background: reference and add your desired hex code. The edit has been applied here already.
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
New Edits
Pop-up Window on HTC_IME - Word Correction
Thanks to @Mikanoshi for helping me find this edit. The pop-up window that appears when using the HTC_IME keyword after an error occurs when typing can be found the the framework.jar. You will need to look in the
Code:
Editor$SuggestionsPopupWindow.smali
Look around line 1131 and 1142 (that's where it's found in my framework)
You'll need to change the color reference indicated in your framework and make them your choice of color. I have made my around 75% transparent and it seems to look nice against a dark background.
The stock colors are smali -0x202021 (#ffdfdfdf) and -0x111112 (#ffeeeeee). I use #be000000 (-0x42000000) and that worked well for me.
Thanks for this. How will this effect creating a 4x5 home screen?
Sent from my HTC One using Tapatalk
So it guide me to change the letter and it work.. the weather control by pngs or smali too? Looking at the same smali you gave to change the background and letter.. but didn't found any related to weather icon?
Sent from my HTC One using Tapatalk
well done fisha21 this and really useful:good:
---------- Post added at 07:10 AM ---------- Previous post was at 07:09 AM ----------
nashshafrulrezza said:
So it guide me to change the letter and it work.. the weather control by pngs or smali too? Looking at the same smali you gave to change the background and letter.. but didn't found any related to weather icon?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
yooo Nash i love your skins remember one x time
maurydes said:
well done fisha21 this and really useful:good:
---------- Post added at 07:10 AM ---------- Previous post was at 07:09 AM ----------
yooo Nash i love your skins remember one x time
Click to expand...
Click to collapse
I'm really hoping the new theme engine working as the skin back then. too bad HTC prefer it other way. I'm trying too port back my classy transparent skin. Hopefully sense 6 would be easier. thanks btw.
Sent from my HTC One using Tapatalk
Will help here where i can !!! Awesome
another one to follow! :good:
Will add what i can, ty
Sent from my PC36100 using Tapatalk 2
Thanks fisha!! Amazing:thumbup:
Great thread thanks a lot
Powered by SkyDragon ROM
Nice
Sent from my PC36100 using Tapatalk 2
2WildFirE said:
Great thread thanks a lot
Powered by SkyDragon ROM
Click to expand...
Click to collapse
Have you deactivated the day/night color change? If yes how you do it.. can't find the solution yet.
Sent from my HTC One using Tapatalk
@nash here http://forum.xda-developers.com/showthread.php?p=51437526
And I using my common panel. 9png
Powered by SkyDragon ROM
2WildFirE said:
@nash here http://forum.xda-developers.com/showthread.php?p=51437526
And I using my common panel. 9png
Powered by SkyDragon ROM
Click to expand...
Click to collapse
Thanks.. but I don't mean the background.. see my screen shot.. the weather icon.. what control it to change at night and day..
Sent from my HTC One using Tapatalk
nashshafrulrezza said:
Thanks.. but I don't mean the background.. see my screen shot.. the weather icon.. what control it to change at night and day..
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Ah ok,sry i think we can change the same way with the icons if i remember editing this smali. I will look into the smali
I mean this here
.method protected getGraphicType(Z)Lcom/htc/weather/StateResources$GRAPHIC_TYPE;
.locals 1
if-eqz p1, :cond_0
sget-object v0, Lcom/htc/weather/StateResources$GRAPHIC_TYPE;->vectorgraphic_light_xl:Lcom/htc/weather/StateResources$GRAPHIC_TYPE;
:goto_0
return-object v0
:cond_0
sget-object v0, Lcom/htc/weather/StateResources$GRAPHIC_TYPE;->vectorgraphic_dark_xl:Lcom/htc/weather/StateResources$GRAPHIC_TYPE;
goto :goto_0
.end method
edit booth to light or dark, Nash has tryed, and it works.
2WildFirE said:
Ah ok,sry i think we can change the same way with the icons if i remember editing this smali. I will look into the smali
Click to expand...
Click to collapse
If you found it please let me know. That's the only thing I left for the clock.. thanks again.
@fisha21, you use vts for sense 6? I can't decompile any of sense 6 apk in vts.. any idea?
Sent from my HTC One using Tapatalk
About
In this guide I will be telling you about how to create your own device mods like this. This involves using an engine built into Android Nougat. There is no root required.
Prerequisites
- Apktool installed (official guide here)
- The apk of the app you wish to modify (ex: SystemUI.apk) (system dump here; USE WINRAR AS 7z DOESN'T EXTRACT RIGHT)
- Android Studio
- Basic knowledge of apk guts
- Template RRO project
- optional: Finished Example Project (for reference)
Tutorial
The first step is to decompile your target APK so we can see what options we can change. For this tutorial, I am going to be modding SystemUI.apk.
"apktool d SystemUI.apk"
After it finishes, go to "SystemUI/res/values", as this will be where we change most things.
Here we can see files like "bools.xml, strings.xml, integers.xml, etc..."
Let's look in "bools.xml".
I see a line in here that mentions lock screen rotation:
"<item type="bool" name="config_enableLockScreenRotation">@android:bool/config_enableLockScreenTranslucentDecor</item>"
For this tutorial, let's change this value, as it is easy to change, and we can visually see this change.
It looks like this boolean is enabled if "config_enableLockScreenTranslucentDecor" is enabled. To override this, we have to change it to "true" instead.
Now that we know what we are changing, let's open up the "RRO_Template" project in android studio.
First navigate to the Gradle Scripts and select the "build.gradle" for the "(Module: app)"
Here lets change some variables. First is the "theme_name". Let's change it to "Lockscreen Rotation"
Next is "theme_id". Let's make it "com.mod.lockscreen_rotation"
We don't need to mess with "priority"
Last is the "package_id" Since default is the id for the SystemUI, we don't have to change anything. If you need to find this for another app, look in the decompiled APKs AndroidManifest.xml under "package="com.app.id""
Next, navigate to the res folder. If you remember, our "bools.xml" file is under "res/values/bools.xml", so let's add that file.
We can delete the sample "strings.xml" as we don't need to change anything there, and add the "bools.xml" file.
Inside of the newly created XML file, we should see a setup like this (if not add it):
"<?xml version="1.0" encoding="utf-8"?>
<resources></resources>"
Looking back at the setting we want to change, it's "<item type="bool" name="config_enableLockScreenRotation">@android:bool/config_enableLockScreenTranslucentDecor</item>". So let's add that line.
But since we are overriding the value to true, it will now look like this :"<item type="bool" name="config_enableLockScreenRotation">true</item>"
And that's it for the value changing!
Now let's go build the APK. Press "Alt + B" to bring up the Build menu and press "Build APK"
Click "Show In Folder" on the bottom right after it compiles to see the APK.
Put this on your phone and install the APK.
Since we modified the SystemUI.apk, we need to reboot to see the changes.
Now, lets try going to the lock screen and rotating the screen. It should rotate!
Congratulations! You made a mod / theme!
If you have any questions, please ask. I will try to help if I am available. I have classes starting in a few days so I may be busy. Enjoy the guide!
Hello tytydraco,
Not sure if my problem is totally related to your posted thread but it sounds like you are very knowledgeable on Galaxy theming! I have a rooted Galaxy S8 and have merged/moded different themes from the Theme store, such as using another theme’s icon pack or wallpaper by swapping them out of their respective .apk files and implementing them with success!
My problem is with a theme’s "InCallUI" (accept, reject, hangup icons in phone dialer) after adding cool graphic .png icons (then changing to .qmg) it works flawlessly, however every time I restart my phone or a Samsung system app is updated, they revert back to those default Samsung cartoony icons. I then have to apply stock theme then re-apply customized theme to get icons back. This process also changes/breaks 3 or 4 other theming aspects, which are not affected by restarts, that I have to re-adjust!
Not only have I altered the theme’s “base.apk” in /Data/App/MyTheme folder, but also the theme’s InCallUI.apk and placed into; Data/Overlays/Style/Mytheme folder, then changed permissions to "rwx r-- r-w". I use these permissions because all the other apk's in this folder use them. I have even tried using different theme’s InCallUI.apk, whose icons remain after restart, by just changing the icons and renaming to my theme….but to no avail, same problem!
I know this all sounds really OCD, like probably most of us within these forums, but it’s getting to be a real pain in darse to constantly have to change everything back again every restart if I want to maintain my theme!
So if I may poach upon your smart nature, do you know if there is a configuration file/folder that can be edited/altered to make those “InCallUI” icons stick upon a restart?
Any advise or corrections in what I'm doing would be greatly appreciated!
Thanks in advance.
eltoro5 said:
Hello tytydraco,
Not sure if my problem is totally related to your posted thread but it sounds like you are very knowledgeable on Galaxy theming! I have a rooted Galaxy S8 and have merged/moded different themes from the Theme store, such as using another theme’s icon pack or wallpaper by swapping them out of their respective .apk files and implementing them with success!
My problem is with a theme’s "InCallUI" (accept, reject, hangup icons in phone dialer) after adding cool graphic .png icons (then changing to .qmg) it works flawlessly, however every time I restart my phone or a Samsung system app is updated, they revert back to those default Samsung cartoony icons. I then have to apply stock theme then re-apply customized theme to get icons back. This process also changes/breaks 3 or 4 other theming aspects, which are not affected by restarts, that I have to re-adjust!
Not only have I altered the theme’s “base.apk” in /Data/App/MyTheme folder, but also the theme’s InCallUI.apk and placed into; Data/Overlays/Style/Mytheme folder, then changed permissions to "rwx r-- r-w". I use these permissions because all the other apk's in this folder use them. I have even tried using different theme’s InCallUI.apk, whose icons remain after restart, by just changing the icons and renaming to my theme….but to no avail, same problem!
I know this all sounds really OCD, like probably most of us within these forums, but it’s getting to be a real pain in darse to constantly have to change everything back again every restart if I want to maintain my theme!
So if I may poach upon your smart nature, do you know if there is a configuration file/folder that can be edited/altered to make those “InCallUI” icons stick upon a restart?
Any advise or corrections in what I'm doing would be greatly appreciated!
Thanks in advance.
Click to expand...
Click to collapse
Sounds like the apk is reverting back... There may be another QMG file that puts the icon back. Other than that, it may be samsung's themes overriding this. Good luck and thanks for the question!
Couple of quick questions
Thanks for the guide OP!
I had a couple of quick questions.
You mention at the beginning of your guide that your method works because of a built in engine in Nougat and that it doesn't require root. I thought that RRO support was added to the AOSP by Sony in Marshmallow? Is this different, or did it just take until Nougat for Samsung to catch up?
The reason I ask is that I tried to do something very similar on an A5 (2017) running 6.0.1 and had no success. I had full root access so I manually installed my .apk into /system/vendor/overlay and could see that the app was installed in the Application Manager, but the desired changes did not take effect. I based my .apk on a similar guide from tutsplus and they say it should work on a device running Marshmallow or higher, but they emulate a Nexus which is obviously closer to AOSP than a Galaxy.
Is this guide Nougat specific or S8 specific? i.e. will a J5 2017 (released after the S8) running Nougat also work in the same way? Can you still install the app manually to the /system/vendor/overlay folder or do you have to manually install it through the UI?
Thanks again for the guide!
tytydraco said:
Enjoy the guide!
Click to expand...
Click to collapse
Hello, sorry for waking this up, the RRO template links are down. Can you attach them here?
I love to modify the fingerprint icons on my lockscreen when I have a rooted device. Currently hunting for the fingerprint Icon so I can modify it. On my OP6T it was located in systemUI but im not finding it there. I also checked velvet and no luck there either. Anyone else have any suggestions on where to look?
Also would be interested in this. Hate dark / light being the two options.
psymsi said:
Also would be interested in this. Hate dark / light being the two options.
Click to expand...
Click to collapse
I just like having custom FP icons and even modding the animation. It's an easy mod to do but I just have to locate the correct APK to decompile...still no luck although I haven't looked much today.
Bumping this thread. Has anyone doing any decompiling and tinkering stumbled upon the lockscreen fingerprint Icon? So far I've decompiled systemUI and settings.apk.....theres a TON of XML files referencing the fingerprint Icon but no PNG files in the /res folder that their pointing to in both applications. I'd like to check framework-res but I can't seem to get it to decompile with apktool, I'm sure I'm missing some resource files necessary to do it I just don't know which ones.
Pain-N-Panic said:
Bumping this thread. Has anyone doing any decompiling and tinkering stumbled upon the lockscreen fingerprint Icon? So far I've decompiled systemUI and settings.apk.....theres a TON of XML files referencing the fingerprint Icon but no PNG files in the /res folder that their pointing to in both applications. I'd like to check framework-res but I can't seem to get it to decompile with apktool, I'm sure I'm missing some resource files necessary to do it I just don't know which ones.
Click to expand...
Click to collapse
It's slightly possible that @siavash79 has an idea from their [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+, which I use. I say this only because the mod has the option to "Remove background circle from under-display fingerprint", in the mod app's Lock Screen section.
All their mods are open-source and you can find the link to their source in that thread, but you could probably get clarification from them (there are two and sometimes more contributors to the mod that answer questions there) as to whether the place they make that particular mod would help you with the fingerprint symbol itself.
Edit: You could also submit a feature request on their GitHub to add the capability to change that symbol, but it's best to first find a stable ROM that has the open-source code for that hack to provide to them.
Pain-N-Panic said:
Bumping this thread. Has anyone doing any decompiling and tinkering stumbled upon the lockscreen fingerprint Icon? So far I've decompiled systemUI and settings.apk.....theres a TON of XML files referencing the fingerprint Icon but no PNG files in the /res folder that their pointing to in both applications. I'd like to check framework-res but I can't seem to get it to decompile with apktool, I'm sure I'm missing some resource files necessary to do it I just don't know which ones.
Click to expand...
Click to collapse
You shouldn't look for png in the resources. All graphics are vector and therefore saved as XML drawable files. Fingerprint icon is an animated vector if you're looking for it.
Edit: if you're planning to change the icon I trust that you're not counting on png files either
PS
There are few ways to change the icon. One is to make an overlay that replaces the icon resource
Two is by modifying the systemUI file and replacing it with the original. Three is by Xposed resource injection or object replacement. Four, of course, is a custom ROM
siavash79 said:
You shouldn't look for png in the resources. All graphics are vector and therefore saved as XML drawable files. Fingerprint icon is an animated vector if you're looking for it.
Edit: if you're planning to change the icon I trust that you're not counting on png files either
Click to expand...
Click to collapse
I see. So if I find the correct xml file I could modify it. Just for simplicity sake let's say I change the color using hex values in the xml file and recompile it. With A13 would I even be able to adb push the GoogleSystemUI.apk to replace the original like I use to be able to do?
Not a chance. I mean you can technically make system RW and copy it there but it's a very very bad idea. but you can make a magisk module and mount it in place of the current one
Edit: Your best bet is compiling an overlay and mounting it in a magisk module
siavash79 said:
Not a chance. I mean you can technically make system RW and copy it there but it's a very very bad idea. but you can make a magisk module and mount it in place of the current one
Edit: Your best bet is compiling an overlay and mounting it in a magisk module
Click to expand...
Click to collapse
It use to be a lot easier lol. No idea where to even start with that....guess I have some reading to do.
So I began the next step. I think I may easiest method here is to modify AOSP mods so the "hide fingerprint background circle" mod when activated adds a custom FP image. I've decompiled the AOSP Mods APK and found the string "remove_fingerprint_background". Now I just need to find which overlay APK is responsible for the mod itself. I'm having difficulty doing this as there's a lot.
I'm curious, is there a logger with root privileges I can run in the background while I activate and deactivate the fingerprint mod which will produce a logcat that will give me some more insight as to which overlay APK is being used to hide the fingerprint background?
Pain-N-Panic said:
So I began the next step. I think I may easiest method here is to modify AOSP mods so the "hide fingerprint background circle" mod when activated adds a custom FP image. I've decompiled the AOSP Mods APK and found the string "remove_fingerprint_background". Now I just need to find which overlay APK is responsible for the mod itself. I'm having difficulty doing this as there's a lot.
I'm curious, is there a logger with root privileges I can run in the background while I activate and deactivate the fingerprint mod which will produce a logcat that will give me some more insight as to which overlay APK is being used to hide the fingerprint background?
Click to expand...
Click to collapse
Maybe this will help you dig further. The fingerprint icon is part of the SystemUI (or SystemUIGoogle). The assets are part of the SystemUI (or SystemUIGoogle) apk. Look at the keyguard section of the SystemUI code to figure out what needs to be done.
packages/SystemUI/src/com/android/keyguard - platform/frameworks/base - Git at Google
packages/SystemUI/src/com/android/keyguard/LockIconView.java - platform/frameworks/base - Git at Google
packages/SystemUI/src/com/android/keyguard/LockIconViewController.java - platform/frameworks/base - Git at Google
Pain-N-Panic said:
So I began the next step. I think I may easiest method here is to modify AOSP mods so the "hide fingerprint background circle" mod when activated adds a custom FP image. I've decompiled the AOSP Mods APK and found the string "remove_fingerprint_background". Now I just need to find which overlay APK is responsible for the mod itself. I'm having difficulty doing this as there's a lot.
I'm curious, is there a logger with root privileges I can run in the background while I activate and deactivate the fingerprint mod which will produce a logcat that will give me some more insight as to which overlay APK is being used to hide the fingerprint background?
Click to expand...
Click to collapse
It's an open source software. Instead of decompilation you can directly explore the source
siavash79 said:
It's an open source software. Instead of decompilation you can directly explore the source
Click to expand...
Click to collapse
Guess I should have checked the GitHub page lol thanks