yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Bright09:
well talking about that and also the fact that its white its ok but i was woundering if its skined or anything
[Verizon Samsung Galaxy S III] WinVist:
nice stuff, may go back to the beans rom
[Verizon Samsung Galaxy S III] deuce237bblock:
For the soft keys mod, what values in the xml need to be changed to move the locations of the buttons? e.g. you have them set as back>home>recents>menu. I want them to be recents>home>back>menu but I want the AOSP soft keys.

Any help is greatly appreciated and thanks for the awesome mods.
[Verizon Samsung Galaxy S III] deuce237bblock:
Awesome write up, gonna try this when I can get on my computer. Apktool doesn't work correctly on my windows computer for some reason, it decompiles fine but I always get an error when I try to recompile. I will have to try apktool on my Ubuntu powered desktop (with a P.O.S. single core Intel celeron lol). Thanks for all the great mods for Jelly 'Beans' ROM.

You are truly great!
[Verizon Samsung Galaxy S III] :
You are correctly loading both framework apks right?
[Verizon Samsung Galaxy S III] deuce237bblock:
Yes, I "apktool if twframework-res.apk" and the normal framework-res.apk and also do the "apktool if" command for systemui.apk. I used the ones from the stock deodex, is that the problem? Should they be the frameworks from the ROM on the phone?
[Verizon Samsung Galaxy S III] :
Yes they should be the frameworks from the rom you intend to mod. Also there is no reason to do:

apktool if SystemUI.apk

A complete decompile/recompile on my box looks like this:

~/Themeing/S3/JB/14/SYSUI$ apktool if twframework-res.apk
I: Framework installed to: /home/brent/apktool/framework/2.apk
~/Themeing/S3/JB/14/SYSUI$ apktool if framework-res.apk
I: Framework installed to: /home/brent/apktool/framework/1.apk
~/Themeing/S3/JB/14/SYSUI$ apktool d SystemUI.apk
I: Baksmaling...
I: Loading resource table...
I: Loaded.
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: /home/brent/apktool/framework/1.apk
I: Loaded.
I: Regular manifest package...
I: Decoding file-resources...
I: Decoding values */* XMLs...
I: Done.
I: Copying assets and libs...
~/Themeing/S3/JB/14/SYSUI$ apktool b SystemUI SystemUInew.apk
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
I: Building apk file...
~/Themeing/S3/JB/14/SYSUI$
[Verizon Samsung Galaxy S III] deuce237bblock:
Awesome thanks. Will try again later tonight when I get home and report back.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Do you think you could make a mod that changes the switch on text in settings from yellow to white?

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] :
I'll see if I can find it.

EDIT: I may have found it. Anyone want to test it??? The worst it could do is hard brick your phone. JK. Its a VR Themer zip that replaces tw_switch_on_holo_dark.xml in ~/res/color/ in your framework-res.apk. Really the absolute worst it could do is nothing. Anyway here is the link: https://dl.dropboxusercontent.com/u/44601870/Beans 13 MODs/B14_OT_Switch_Color_VR.zip Let me know if it works. Thanks.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Thank you

Works perfectly

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] :
Right on. Setting up the tools to edit apps is kind of a pain, but once it's done you can have a lot of fun doing it. If you need help theming there is a sticky in this section dedicated to those kinds of questions.
[Verizon Samsung Galaxy S III] deuce237bblock:
I found these Motorola RAZR HD soft keys in the galaxy nexus thread but I can't get them to work, I tried renaming the pngs but still a no go.

Here's the link to the zip. http://db.tt/hIaERYmc
[Verizon Samsung Galaxy S III] :
What did you rename them to? There are like three sets of keys in sysui. You need to replace the ones called tw_navigationbar_(home/back/recent/menu)_(normal/pressed).png. The keys are in drawable-xhdpi. Note tat you will want to resize them otherwise they will be quite small in landscape.
[Verizon Samsung Galaxy S III] deuce237bblock:
I've never done this before. What do I use to resize them?

---------- Post added at 12:11 PM ---------- Previous post was at 12:11 PM ----------

I just put tw_ in front of them.
[Verizon Samsung Galaxy S III] :
I use Gimp to edit images. Its a lot like Photoshop but free. You could also use pixlr at pixlr.com/editor/

You need to open SystemUI.apk and navigate to ~/res/drawable-xhdpi/ in this folder will be the images you want to replace. I gave the names in my previous post.
[Verizon Samsung Galaxy S III] deuce237bblock:
There are "normal" and "pressed" pngs, in that RAZR HD zip there are no "pressed" pngs. How do I get the RAZR HD pressed pngs?

Could I make them from the Normal pngs?
[Verizon Samsung Galaxy S III] :
Just make a copy of the normal one and save it as the pressed one. I like to make the pressed one blurry like the one in the OP.
[Verizon Samsung Galaxy S III] deuce237bblock:
I got them resized and I blurred them out to create the pressed effect but now they are huge, how can I make them smaller?

I am really sorry, I have never edited any kind of image before so this is very new to me.
[Verizon Samsung Galaxy S III] deuce237bblock:
Didn't even see this post before I posted my reply above. I attached a screenshot of the RAZR HD sofkeys that I edited with the pixlr.com/editor/ that you mentioned and blurred them for the pressed effect.
[Verizon Samsung Galaxy S III] :
To get them perfect I scale the image uniformly so the height is 60px. Then I crop it so it's 60px by 60px. Then save it once as the normal png and again as the pressed after I've made it blurry.
[Verizon Samsung Galaxy S III] deuce237bblock:
Lol, now I have to start over.
[Verizon Samsung Galaxy S III] deuce237bblock:
Wow, this is going to take some extra work. Any ideas?
[Verizon Samsung Galaxy S III] :
Make sure you scaled them correctly. You could also just use them in there original size.
[Verizon Samsung Galaxy S III] :
Looks good. Here they are on my gnex for comparison.
[Verizon Samsung Galaxy S III] imjehh:
Can you make a flashable zip for the noobs
[Verizon Samsung Galaxy S III] deuce237bblock:
Here is a flashable zip I made. B13_NB_White_RAZRHD_VR.zip
[Verizon Samsung Galaxy S III] :
Well done. How are keys arranged?
[Verizon Samsung Galaxy S III] deuce237bblock:
Same as the one in the op.

Back>home>recents>menu
[Verizon Samsung Galaxy S III] imjehh:
Thanks, looks great!

---------- Post added at 04:45 PM ---------- Previous post was at 04:44 PM ----------

Hey Mentose were you able to fix the battery to the right size for your status bar OH mod?
[Verizon Samsung Galaxy S III] deuce237bblock:
I thought I would share some extra Navigation Bar Mods.

These Navigation Bar Mods modify the tw_navi_bar.xml in SystemUI.apk to rearrange the softkeys to the AOSP style configuration.

The Icons used are:

-ICS Blue AOSP

-ICS Blue AOSP Reflective

-White AOSP Reflective

-ICS Blue RAZRHD

-White RAZRHD

Download:

B13_NB_Blue_AOSP_VR.zip

B13_NB_Blue_AOSP_Reflect_VR.zip

B13_NB_White_AOSP_Reflect_VR.zip

B13_NB_Blue_RAZRHD_VR.zip

B13_NB_White_RAZRHD_VR.zip

These icons were created by XDA Recognized Contributor atticus182 so big thanks to him.

Big thanks to mentose457 for the AOSP Navi Bar Mod.
[Verizon Samsung Galaxy S III] vmancini3:
Ok, so I've decided to start a mission! This is a thread for mods right? Well, I'm sick of seeing "Verizon wireless" at the bottom of the expanded notification panel! After a little while of fiddling around, I finally have ApkTool working so that I can decompile the necessary apk files and have human readable xml files! I'm not worried about recompiling or apk signing or any of that right now....I just need to find where it is I need to make the change(s)! If anyone can help point me in the right direction that would be totally awesome! In the meantime, I'll be scanning through every xml file I can think of until I find something! Wish me luck...I WILL figure this out eventually!
[Verizon Samsung Galaxy S III] deuce237bblock:
I'm not sure where the carrier info would be but heres a good starting point if you don't know where to look, after decompiling SystemUI.apk navigate to res/layout/tw_status_bar_expanded.xml, again just a starting point, maybe somebody else that knows where it is can give us the exact loacation. Hope this helps!
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
If not there I would say to look in systemui.apk/res/values/strings
[Verizon Samsung Galaxy S III] :
The carrier text is dynamic, it shows based on the network you are on. Therefor you wont find a string of text that says "Verizon 'going in dry' Wireless" anywhere. You can remove the lockscreen carrier text by following the directions in THIS post. The directions in the post are to delete a file, what you should do is delete the lines of code one by one till you find the one that removes the carrier text. Once you know what syntax is used to bring up the text you can spend hours trying to find where it comes up again and change or delete it. Have fun! :good:
[Verizon Samsung Galaxy S III] imjehh:
Thanks for your work as well...but what exactly do these look like? Can you post a s/s?
[Verizon Samsung Galaxy S III] deuce237bblock:
Yes, I will post screenshots a of each mod.
[Verizon Samsung Galaxy S III] mds96:
Mentose457 just wanted to let you and mod users know that the cyan colored mods, gradient mod, white toggle text mod, and the create your own statusbar mod, work on Jelly Beans Build 15! The only mod I don't use it the soft key mod, so I can't report on that. Thanks again for all the mods!
[Verizon Samsung Galaxy S III] unhappybirthday:
Are the status bar transparency VR Themes compatible with a launcher in landscape orientation?
[Verizon Samsung Galaxy S III] :
Yes. The Image status bar might look strange as it would stretch the image. Making another image for landscape mode would require some extra coding.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Well if it's a completely transparent or solid color image than it would just need to be resized making the length 1280 instead of 720... if the image has any kinda detail then it wouldn't look right but otherwise would be OK
[Verizon Samsung Galaxy S III] :
Correct. I looked into making it look for different images based on orientation but decided that it prolly wasnt worth my time.
[Verizon Samsung Galaxy S III] imjehh:
Do you have the s/s yet?
[Verizon Samsung Galaxy S III] :
Go to ether the galaxy nexus or Nexus 4 forums and look at the themes section for a softkey thread by atticus182. That is where the images came from.
[Verizon Samsung Galaxy S III] unhappybirthday:
Probably most folks using these are on the TW launcher anyway. Thanks for the time you have put into creating and sharing these with us.
[Verizon Samsung Galaxy S III] imjehh:
Thanks bud.
[Verizon Samsung Galaxy S III] mds96:
Dangit! Bummed that you don't have the S3 anymore! Hopefully someone, maybe even myself can picl these up and try them for further builds! So when these don't work anymore, you may get PM's from me! Lol...Thanks for providing us with awesome mods! What phone did you pick up?
[Verizon Samsung Galaxy S III] :
I dont mind helping anyone that wants to continue doing these mods for Beans rom or any other rom for that matter. Anyway im back to my GNexus.
[Verizon Samsung Galaxy S III] mds96:
Ok awesome! Ahh I see! I'm actually back on AOKP for now! I'm sure I'll try Beans releases in the future, but with the latest Ril commits and the buttery smoothness, I might be on AOSP for good! Thanks again!
[Verizon Samsung Galaxy S III] BeansTown106:
How's the rail doing? A lot better? Might have to give it a try oh how I miss actual working aosp lol.

Sad to hear your no longer with Us mentose what made u give up the s3 for gnex? U planning on getting s4?
[Verizon Samsung Galaxy S III] :
I must rant. Hell, its my thread and I can rant in it if i want too.

[RANT]There are two things I hate about the S3: The construction and the software.

Construction:

I loath the gawd-awful, no-good, ugly-as-sin, annoying-as-hell home button and the bss aackwards capacitive keys. I don't like the lighter than air cheap plasticie feel ether. The way the glass sticks out further that the bezel was/is a dumb as rocks decision. Its no wonder galaxy phones never fair well in drop tests.

Software:

TouchPiss = no. It matches the ugly-as-sin home button. With a bit of themeing (as you have shown us) one can almost rid the phone of the kindergarten colors and and overall gay look of the phone. But its still not the same. The basic applications suck too. The phone/contact apps suck (no swipe to go to the different pages? Really?) If you add the navigation bar (that they ****ed up, another bss aackwards thing) it overlaps most (or all i didnt use half of them) Samsung apps. Those dumbnuts have a whole app writing tutorial on their site showing developers how to make apps scale-able yet their own aren't? Any one that has decompiled a Samsung apk should be disgusted in what they see. There are like three times the amount of images that aosp uses, partly because all of the aosp images are still in it. XMLs too, there are at least double.

AOSP = bugs. Despite what the fanboys say, there are bugs in all aosp builds. I know ive tried all of them. GPS has issues, bluetooth has issues, battery life sucked compared to TP. But despite those things it is significantly better than TouchPiss. I would have continued using the S3 running and AOSP based build but that home button... damn...[/RANT]

I wont be buying the S4. In fact I wont be buying another Samsung phone that has a big ass home button. What happened to the days the US phones had capacitive buttons and the eurotrash fones had big ugly home buttons? Curse Samsung and their fetish with Apple features. Im not sure what phone ill be getting next. It will be a nexus or a Moto phone for sure. My contract with VZW is up so im considering changing carriers. The service is almost not worth getting raped over.
[Verizon Samsung Galaxy S III] mds96:
---------- Post added at 01:23 PM ---------- Previous post was at 01:16 PM ----------

It is quite a bit better for me in my area here is Ohio. Handoff is better, weaker signal areas are better, and battery life has also been better on stock kernel, some of which I believe has to do with the better Ril. Don't get me wrong, I still like what you've done with TouchPiss, lol, had to steal Mentose457's nickname for it, cracked me up!

---------- Post added at 01:26 PM ---------- Previous post was at 01:23 PM ----------

Lol I have to agree with you 100% Mentose!! I actually have decided myself that a Nexus, or Moto phone will be my next, and hopefully it's a Moto Nexus phone! :) I too dislike the Home Button, just wish I would have messed with the phone more before upgrading to it...
[Verizon Samsung Galaxy S III] uberbdon:
I love Motorola build quality, and Blur has come a long way. I've always thought Touchwiz was ugly as sin, and to see some of the themes even on XDA make TW look like AOSP in comparison lol...

A moto nexus would be a dream.
[Verizon Samsung Galaxy S III] ATT_GOD:
Oops wrong post

Sent from my SCH-I535 using Xparent BlueTapatalk 2
[Verizon Samsung Galaxy S III] hoodieNation:
Hmmm, any awesome person (that's smarter than me) wanna try and update these mods to build 17?
[Verizon Samsung Galaxy S III] :
I'd do a hangout (chat) with someone to show how I did them.

Or if someone wants to test them I could do them.
[Verizon Samsung Galaxy S III] TheDriller:
I will do it. If you care to show me
[Verizon Samsung Galaxy S III] :
Sounds good.
[Verizon Samsung Galaxy S III] hoodieNation:
You guys are awesome!
[Verizon Samsung Galaxy S III] hoodieNation:
Since you guys might actually work on this I thought I might point out that in order to get the navigation bar to work the line in build.prop needs to be:

qemu.hw.mainkeys=0

The directions in the op say "qeum".

Thanks again for these mods mentose, I rolled back to build 15 just to keep using them.
[Verizon Samsung Galaxy S III] DigitalMD:
Good luck with that, after two different Moto models with permanently locked bootloaders that failed me miserably and the last being first dropped from Moto's update path after only 8 months then dying and being replaced by Verizon with refurbs which never worked right I said NO MORE MOTOs , ever. But to each his own. So far I have had the Sammy for 6 months and feel it is far superior to the motos in every way, its just doesn;t weight as much.
[Verizon Samsung Galaxy S III] uberbdon:
The moto x phone looks like a step in the right direction.
[Verizon Samsung Galaxy S III] :
I once had a Droid 2. It was crap. I now have the RAZR HD and love it. The stock room its fantastic. After de-bloating it and fixing the signal icon its near perfect. It has an unlocked bootloader and is rooted.

I'd rather punch myself in the balls, repeatedly, than use another Samsung phone (unless it was a nexus).

I'd like to also point out that the bootloader on the Verizon S4 is locked in the same way as the RAZR HD was.
[Verizon Samsung Galaxy S III] ashtro:
This!!! Thank you [MENTION=4356025]hoodieNation[/MENTION] for sparking this. And [MENTION=4469503]RErick[/MENTION] [MENTION=3348421]mentose457[/MENTION] I too rolled back to build 15 just to rock these mods. Beans rom is just about flawless for me but I am a sucker for 2 of these mods. The toggle/status bar mod wouldnt work on 17. I was able to flash the settings menu though and it worked. I look forward to following the thread for progress.
[Verizon Samsung Galaxy S III] ashtro:
Mentose here's the picture
[Verizon Samsung Galaxy S III] Jason Roach:
Will these be updated for 19 or will they still work now?
[Verizon Samsung Galaxy S III] :
Probably not. I don't have the phone anymore.
[Verizon Samsung Galaxy S III] Jason Roach:
Ok thanks for the reply
[Verizon Samsung Galaxy S III] hoodieNation:
I just flashed the signal cluster on build 19 and it does work. :thumbup:
[Verizon Samsung Galaxy S III] prdog1:
Looks like softkey mod also works on 19 altho never used it so couldn't tell if broke. :rolleyes::laugh::cool:
[Verizon Samsung Galaxy S III] hoodieNation:
Yes sir. I'm using it right now.
[Verizon Samsung Galaxy S III] prdog1:
Seems kinda funky to me. Don't really see the purpose unless hard buttons are broke. lol Also need to fix the camera problem. :cool:
[Verizon Samsung Galaxy S III] hoodieNation:
Yeah that camera is funky and that's usually the reason I quit using it.

I go back and force a lot as I really don't like the physical home button on this phone.
[Verizon Samsung Galaxy S III] prdog1:
I only use Home button for recents usually. Back to kill sends you home anyway. This first time I even looked at it. Never was a mod I would waste time on building. Someone on Beans is looking for it so just gonna send him to thread altho he is a noob and the buildprop edit may be above his paygrade. :p :laugh::cool:
[Verizon Samsung Galaxy S III] hoodieNation:
Haha, well let's leave these comments in here for him to read.
[Verizon Samsung Galaxy S III] prdog1:
Yea. Back to kill sends you home anyway and I don't feel like building his ass a buildprop to add to zip. Gotta learn sometime. :laugh::cool:
[Verizon Samsung Galaxy S III] hoodieNation:
Yeah I don't even know why I'm using this lol. I've got nova gestures setup for recents. And like you said, back for home. No real need for this at all.
[Verizon Samsung Galaxy S III] prdog1:
Yea. Back/menu to kill been nice since me and Dewith were able to make it independent from everything else and not borking other mods. :cool:
[Verizon Samsung Galaxy S III] burntrat:
Hey are these mods working for beans build 20?

Sent from my phone
[Verizon Samsung Galaxy S III] hoodieNation:
A lot of them worked on 19 so I'd assume so. Flash and report back! :)
[Verizon Samsung Galaxy S III] Joker87:
Doesn't Work on Galaxy S3 with Omega v54 (android 4.3)

Navbar remain the same
[Verizon Samsung Galaxy S III] Thebear j koss:
Because it is made for Beans rom by beanstown

Thebe@r'$ G@L@XY
[Verizon Samsung Galaxy S III] Jason Roach:
If anyone know where to find it or has it to post please?
[AT&T Samsung Galaxy S II SGH-I777] kamleshsv:
I have an AT&T SGH i777. It is officially unlocked and also rooted. Its on Gingerbread 2.3

Will flashing it with a stable Jelly Bean ROM affect the unlock?
[AT&T Samsung Galaxy S II SGH-I777] kamleshsv:
Re: How to update to custom JB 4.2.1 ROM with the already phone officially unlocked

Also will the root be affected if I go to the stock ICS ROM?:rolleyes:
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
Reading can help a lot, just saying

Sent from my Zanpakuto using Getsuga Tensho!
[AT&T Samsung Galaxy S II SGH-I777] chibixzero:
You can install a custom jb room from the Android development thread. All custom ROMs come rooted with lots of features. Just read up on how to install a kernel with cwm boot up and install rom. Pretty simply if you read instructions
[Galaxy S III I9305 (4G LTE + 2GB RAM) Android Deve] djb77:
VillainTheme System Universal Firmware Mod for I9305

A Flexible CWM Installer for ROM Chefs, Modders, and Themers

Original Thread can be found HERE​

INFORMATION​

This is a modified version of the VillainTheme System specifically set up for the I9305.

The Partitions are set to the correct locations for starters, but that's just the beginning...

What this version is capable of doing is injecting files into the vrtheme data before it starts installation, depending on what Firmware is installed on the Phone.

So, for example, this is what you can do:

Let's say you have edited SecMms.apk and you've also edited the androidmanifest.xml in this file, however you want this to support multiple Firmwares. This is how you would set up the installer.

- Copy all your files to the /vrtheme/system/app/SecMms.apk folder except for the androidmanifest.xml and META-INF folder

- Copy the META-INF folder and androidmanifest.xml to /tmp/vrtheme/<Your desired FW>/system/app/SecMms.apk

- Repeat the last step for any other Firmwares you wish to support

The following post shows the updater-script and fw_check.sh scripts I've created if wanted for reference.

SUPPORTED FIRMWARES

I9305 FIRMWARES (for Version 1.0x)

XXALI5 - ZHALI7 - ZHALI8 - XXALI9 - XXALIA - ZHBLJ1 - XXALJ3 - XXALJ4 - XXALJ7 - XXALK3 - XXELK4 - XXALK5 - XXBLK5 -

XXELKC - XXBLL3 - XXBLL5 - XXBMA1 - XXBMA3 - XXBMA4 - XXBMA5 - ZHBMA5 - XXBMA6 - XXBMB2 - XXBMB3 - XXBMB4 - XXBMB5 -

XXBMC1 - ZHBMC1 - XXBMD1 - ZHBMD1 - XXBMD4 - XXBMD5 - XXBME1 - XXBME3 - XXBMF1 - XXBMG3 - XXBMI3 - ZHBMI4 - XXBMJ1 - XXBMR8

I9305N FIRMWARES

XXALIA - XXBMA2 - XXBMC2

I9305T FIRMWARES

DVALI6 - UBALK2 - UBALK3 - DVBMA2 - DVBMB1 - UBBMC1 - DVBME2​

​

Version 2.0x works with Android 4.3 Firmwares:

XXUEMKC - ZHUCML1 - XXUEML5 - XXUEML8 - XXUEML9 - ZHUCNA1 - XXUENA1 - XXUENA2​

Version 3.0x works with Android 4.4.x Firmwares:

XXUFNE3 (N7105 port) - XXUFNI4 (I9305N) - XXUFNI3​

PLEASE HIT THE THANKS BUTTON IF THIS HELPS YOU OUT

​