I am looking to switch over to Doc's new xxjpu 2.0 rom as soon as it gets posted, at least temporarily to check it out. I also love the theming and animations from Di11igaf's rom. I'm familiar with using 7zip to switch out icons or even the kernal and making changes before flashing, but I'm not sure how to do it with animations and menu themes. I think xml files have to be adjusted to get disired effects. Are xml files firmware specific? Or can I switch them?
Still a noob, but trying to learn here.
Thanks.
PuffinNugz said:
I am looking to switch over to Doc's new xxjpu 2.0 rom as soon as it gets posted, at least temporarily to check it out. I also love the theming and animations from Di11igaf's rom. I'm familiar with using 7zip to switch out icons or even the kernal and making changes before flashing, but I'm not sure how to do it with animations and menu themes. I think xml files have to be adjusted to get disired effects. Are xml files firmware specific? Or can I switch them?
Still a noob, but trying to learn here.
Thanks.
Click to expand...
Click to collapse
The Xmls are version specific. I am also learning as I go and trying to get a working theme from different parts. I would open the framwork-res and swap the anima folder for the transitions and go by one by one and change the icons with their new counterparts and hope you dont get a boot lool or FC city lol. Trial and error
zelendel said:
The Xmls are version specific. I am also learning as I go and trying to get a working theme from different parts. I would open the framwork-res and swap the anima folder for the transitions and go by one by one and change the icons with their new counterparts and hope you dont get a boot lool or FC city lol. Trial and error
Click to expand...
Click to collapse
Right on, Thanks. Kind of what I figured. I'll give it a go.
Development dropped in favor of Liberation.
Only difference between Nothing Special 1.3 and Liberation 1.0 is that Google Car Home has been replaced by the stock HTC Car Panel. This is to remove "holes" left by the removal of a stock app. Also, this no longer conflicts with my intent of having a stock ROM minus carrier bloat/restrictions. Google Car Home can be added by the user if they so choose.
How to customize Nothing Special (Peanut) BEFORE you flash:
Materials
Windows - 7-ZIP
Linux - nothing
Mac OS X - nothing (note, I have not done this on Mac OS X, so I cannot support this OS)
Steps
Download the above mentioned file(s) for Windows. You can use a different archive manager if you'd like, but my guide is based on using 7-ZIP.
On your desktop, create a folder named "Test." You can name it whatever you want, but I'll be referring to it as "Test" in this guide. If you are new at this, you need to follow the guide to the letter.
Find your downloaded "Nothing Special (Peanut) ROM" and extract it to the Test folder. The easiest way to do this on Windows is to open the ROM, highlight all of the folders/files (CTRL-A), copy (CTRL-C), then open the Test folder and paste (CTRL-V). Give it a minute to extract the contents.
Once you complete step three, modify the ROM to your hearts content (see details below). Once complete, proceed to step five.
Open the Test folder and highlight everything (CTRL-A). Right click and select "Add to Archive." This will open 7-ZIP's archive manager. On Linux or Mac OS X, just right-click (or equivalent) and select "Compress."
In the options menu that comes up, leave everything at default except the following. The filename should be Test.zip (change Test to whatever you want). Archive format should be zip. Compression level should be ultra. That's it.
Once done, you can copy this zip to your SD card and flash as normal. Keep in mind that I am not responsible for any changes that you made in this ROM, so make sure you Nandroid BEFORE you flash.
Specific customizations for the above method:
Ringtones - While the ROM is unzipped, open the test folder and look for /system/media/audio. Within this folder you'll see several more folders (Ringtones, Alarms, Notifications). Any should files you put here will show up in the system when you go to change your ringtone (or whatever corresponds to the folder). The benefits to this modification include; no storage space used up in internal, phone, or SD storage; ringtone works even if SD is USB mounted, no errors when the SD card corrupts or is in use. The ringtones (alarms/notifications) are stored in a partition that does NOT count towards your file storage
Modify Status Bar - Don't like the crap (IE, the E911 location icon or the clock) in the status bar? Change it! Go to THIS THREAD, download the status bar you want, and then use it to replace the services.jar file found in /system/framework. Don't have to worry about flashing it separately!
Add the 3-in-1 reboot menu - Want a 3-in-1 reboot menu without flashing separately? Go to THIS POST and download the file. Extract the file from /system/framework, and use it to replace the same file in /system/framework from your ROM. When your ROM is zipped and flashed, you'll have the 3-in-1 reboot menu by default!
Add the Evo camera - Go to THIS POST and download the file that I attached. Go to your Test folder and navigate to /system/app/. Use the downloaded apk to replace the one already there.
Add/Remove apps you don't want - Navigate to /system/app, and remove any APK files that you don't want. If you don't know what app it is, do NOT remove it. WARNING: You do this at your own risk! Not all apps are safe to remove! You can also place other APKs in here. Generally not recommend as then they take up space in /system/app and /data/data, which can slow boot time when too crowded.
Modify Bootup Animation/Sound - Navigate to the /system/customize/resource/ folder. In there, you will see two files; VZW_bootanimation.zip an VZW_Droid.mp3. These files are the bootup animation and "Droid" noise. Simply delete the MP3 if you want a silent bootup. It really is that easy. Replace the ZIP File with another zipped animation (must give it the same name) to replace the animation with one of your own. NOTE: Make sure you verify compatibility. If unsure, don't do it.
WARNING about Smooth Sense Icons - Do NOT follow the above instructions with any mod, such as Smooth Sense icons, that replace framework.apk. Doing so will cause you to have a boot loop. This must be flashed manually and separately
Modifications: A note about the below medications. They may or may not flash with your recovery. If you see *(recovery) after a mod, it means that I have personally verified that it works. For outdated mods, I will, over time, convert them to Clockwork Mod 3.x. If you want to see a mod listed here, PM me so that I can add it. Posting it in the thread won't always catch my attention.
Smooth Sense Icons w/white battery indicator - Thanks goes out to jercik for the mod and squintz for the port and white text change. This collection of icons makes Sense look much nicer.* (2.5.0.5, 2.5.1.2)
Status Bar tweaks - Thanks goes to pardonmyfreedom - collection of mods allows you to change what icons show up in your status bar (IE, clock, battery meter, E911 location icon, etc.)* (2.5.0.5, 2.5.1.2)
3-in-1 Reboot Menu - Thanks goes to snq - When you hold the power button, beneath the shut down icon you'll have a reboot option. This gives you three more choice; normal, boot-loader (HBOOT), recovery. * (2.5.0.5, 2.5.1.2)
Evo Camera - Provided by various sources, this camera is the same as the Incredible camera, but has an on-screen button for those who hate using the track-pad. * (2.5.0.5, 2.5.1.2)
Kernels: If you see a * (approved), it means that I have personally tested the kernel(s) at the provided link with this ROM. In theory, any Sense kernel should work on this ROM. If you have a favorite kernel, PM me the link and description so that I can add it.
Heyitslou's custom kernels -customized versions of the stock kernel, these kernels offer excellent stability, battery life, and real world performance, but won't win any synthetic benchmark comparisons. I use #8 and HIGHLY recommend it. All credit to the linked thread author.* (approved)
What is the difference between peanut and plain? Maybe I need to read the discription of both again. Either way, thanks for your hard work friend.
[DINC]|[CM7]|[SLAYHER#27]
I've been on CM forever. Might be kinda nice to go back to stock-ish and mess around with it a bit. Thanks man!
wildstang83 said:
What is the difference between peanut and plain? Maybe I need to read the discription of both again. Either way, thanks for your hard work friend.
[DINC]|[CM7]|[SLAYHER#27]
Click to expand...
Click to collapse
Yes, read the OP for "Nothing Special (plain)," the link is at the bottom of the OP here. Basically, plain is odexed, and cannot take mods, etc. It is simply stock with crapware eliminated and one or two very minor tweaks. It's for those who don't want to stray far from stock, and are content with their ROM as is.
Peanut is deodexed, and can therefore be modded. You can flash other themes, kernels, etc. and build it any way you want from stock, instead of from other ROM builders' vision of what "stock" should be.
All credit to Jason for a very nice job doing something that was long overdue. Not planning on running it myself, but flashed plain on my daughter's Incredible and I don't think I'll have to provide any more tech support to her from here on in.
Plain or Peanut is now more up-to-date than Virtuous, which was formerly the best "first step" for anybody exploring ROM's.
hgoldner did a great job of summing up the differences, so I'm going to add a bit more technical bits to it.
When a ROM is odexed, as the stock ROM is, it means that the key apps (anything made by HTC) are divided up into two parts; an APK file and an ODEX file. When you first load an odexed ROM, all of the APK files copy over to the /data/data/ folder for installation. The ODEX files remain in /system/app/ and are used like libraries on your desktop.
On a deodexed ROM, the ODEX and APK files are combined into one APK. So, when these APKs are copied to /data/data/, they take up more space. This is a key reason why the first bootup of a deodexed ROM takes so much longer than an odexed equivalent, as more data is being copied over. Also, this is why Plain has 722MB available to the user (more than any other ROM I'm aware of, even edging out the stock ROM, which is 710), while Peanut has 676MB available to the user.
An odexed ROM is harder to modify and is not compatible with modifications made for deodexed ROMs. So, only run Plain if you want a stock ROM, without bloat, and with more space available for apps. Run Peanut if you can live with less space, but want a choice in what addons are run.
I'll be adding more addons to this thread almost daily. I'll make it as easy as possible to customize this ROM the way you want it.
jaykresge said:
On a deodexed ROM, the ODEX and APK files are combined into one APK. So, when these APKs are copied to /data/data/, they take up more space. This is a key reason why the first bootup of a deodexed ROM takes so much longer than an odexed equivalent, as more data is being copied over. Also, this is why Plain has 722MB available to the user (more than any other ROM I'm aware of, even edging out the stock ROM, which is 710), while Peanut has 676MB available to the user.
Click to expand...
Click to collapse
Wow. Didn't know that myself. This would strongly suggest that odexed ROM's have a less likelihood of filling up the \data\data 150mb partition, and therefore would be less likely to produce the "low memory space" warning. Yes?
hgoldner said:
Wow. Didn't know that myself. This would strongly suggest that odexed ROM's have a less likelihood of filling up the \data\data 150mb partition, and therefore would be less likely to produce the "low memory space" warning. Yes?
Click to expand...
Click to collapse
Exactly You get roughly 50MB extra from being odexed, depending on the ROM. In the case of Nothing Special, deodexing takes away 46MB from /data/data/. I've tried to keep it somewhat clean though, as most other custom ROMs use up a little more space than this.
This is what virtuous was supposed to be. Virtuous' definition of "essential fixes" is a little flawed to me. Perfect stock ROM. Thanks.
EDIT: In my opinion this is what virtuous should have been. Virtuous' definition of "essential fixes" is a little flawed to me. Perfect stock ROM. Thanks.
BerkleyJ said:
This is what virtuous was supposed to be. Virtuous' definition of "essential fixes" is a little flawed to me. Perfect stock ROM. Thanks.
Click to expand...
Click to collapse
RMK did a great job on Virtuous. I'm a mere hack compared to him as a ROM developer. I think Virtuous is what is was meant to be, but he's just moved on to the G2.
My ROMs are merely another alternative.
Updated the FAQ with two notes to help explain the difference between Plain/Peanut (they're the top two Q/As). Will start adding the addons tomorrow. For now, flash the ROM and your favorite kernel, then setup to your heart's content. Starting tomorrow the flashaholics should be happy (and no, you won't be losing any data between flashes, they're just patches)
BerkleyJ said:
This is what virtuous was supposed to be. Virtuous' definition of "essential fixes" is a little flawed to me. Perfect stock ROM. Thanks.
EDIT: In my opinion this is what virtuous should have been. Virtuous' definition of "essential fixes" is a little flawed to me. Perfect stock ROM. Thanks.
Click to expand...
Click to collapse
I just wanted to add clarification. I respect RMK, but I was also a bit disappointed in Virtuous. I tried to talk to him in private and requested permission to make some changes to Virtuous (such as updating his outdated Sense apps), but he seems to have moved on to the G2.
So, I'm disappointed with how Virtuous has come out, but respect RMK as a developer. I wish that I had his talent.
Although I may not flash this I do appreciate the work you've put into it. I do think this is awesome. And again thanks guys for the rundown on the difference between the two. Now I know a little bit more about the odex and deodexed stuff. Thanks.
[DINC]|[CM7]|[SLAYHER#27]
Well, im runnin it with ziggys bfs no havs, and its great! Zero issues, may just stay here until gb sense hits. I do wonder, if there is an ota, how woukd that affect this rom?
Sent from my ADR6300 using XDA App
jaykresge said:
The second post will be used for custom addons. I encourage others to share what they're using (and how they got it to work if a workaround was needed) so that we can build up an addon collection for this ROM.
For now I'm using Peanut with;
Lou's #8 kernel
Sexy Sense Icons (w/white battery charge number)
no location (removes the E911 location icon from status bar)
3-in-1 reboot menu
Evo camera (for the on-screen button)
Click to expand...
Click to collapse
Where did you get the evo camera?
Sent from my ADR6300 using XDA App
donnyp1 said:
I do wonder, if there is an ota, how woukd that affect this rom?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I didn't edit the build.prop, do it may prompt you for an update, but not actually allow you to update. If there is an update, I'll make the same changes to that ROM that I make to this one.
donnyp1 said:
Where did you get the evo camera?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'll add links later today, but for now, I've attached the camera.
Does anyone use statusbar pull down toggles? if so what do you use?
josh0426 said:
Does anyone use statusbar pull down toggles? if so what do you use?
Click to expand...
Click to collapse
Status Bar Settings 1.2 from the market. Works very well.
Thanks fer clock, how do you install? Failed thru rm
Sent from my ADR6300 using XDA App
paintguy said:
Status Bar Settings 1.2 from the market. Works very well.
Click to expand...
Click to collapse
I found this one, it feels a little more integrated into the OS. Its from Virtuous Rom. Here is a screenshot of pulldown.
I've successfully edited and replaced the framework.jar file from continuum 5.4.1, so this will *probably* work for other jvh roms.
I don't have an update.zip made yet, I'm not sure why I'm getting errors, but it still works to just replace the framework.jar and reboot. Download the attached file, then do
Code:
cd /directory/you/put/framework.jar
adb push framework.jar /system/framework/framework.jar
And now you have bounciness again. I dunno about anyone else but overscroll glow wasn't doing a thing for me!
Samsung source is here:
http://opensource.samsung.com/
Sent from my Nexus S using Tapatalk
what im thinking if you wanna get rid of the overscroll glow is why dont you just get rid of the images itself. there's only to from what i understand. delete the images or replace them with transparent images so you wont see it at all. the image names are: overscroll_edge & overscroll_glow
it does work. but you would have to make a zip for each different framework considering they're all different. easy deal.
Stock roms come with bounce. Glow is added as a mod but it overrides bounce though. If you want bounce just don't implement the mod.. simple. I actually have 2 versions of my framework.jar, 1 with bounce and one with glow.
If you're not a themer you should look into themeing guides. However, they don't explain too much working with java binaries. What you have to do is decompile the dex file in framework.jar and modify .smali files with an advanced text editor (maybe notepad++ on win).
Google this stuff. You'll find lots of info on it.
I'm not trying to disable the glow I want the bounce back, so altering the images would be pretty moot in this case but thanks for the response.
And yea I realize that the bounce is standard but every gingerbread rom I've flashed so far has the glow enabled so instead of waiting for rom devs to provide choice I'm trying to do it myself. It should just be a simple matter of compiling framework.jar, using smali and baksmali seemed like overkill in this case.
Why not take the framework.jar from the stock jvh rom? I'm not a fan of overly custom roms so I use the stock jvh (with only minimal customizations to make it work on the Captivate) from this awesome thread:
http://forum.xda-developers.com/showthread.php?t=948790
majinzen said:
Why not take the framework.jar from the stock jvh rom? I'm not a fan of overly custom roms so I use the stock jvh (with only minimal customizations to make it work on the Captivate) from this awesome thread:
http://forum.xda-developers.com/showthread.php?t=948790
Click to expand...
Click to collapse
Because.....well.....**** I never thought of that lol. I learned a lot from doing it the hard way though so it's all good. I'm gonna rip out the framework.jar's from jvb and any other popular Ginger roms and keep them all here though. I'm much happier with the bouncing I play with it constantly hehe
hello, sorry if i'm late, but i hate overscroll glow... i can't find the modded framework.jar that you said you attached..
Share
Would you care to share the mod you made to re-enable bounce?
It's a pain getting to threads like this finding neither the file mentioned is attached nor the method used explained for others to perform themselves.
The stock KJ3's overscroll effect is now also glow
How can I make it 'bounce'?
chazkenji said:
The stock KJ3's overscroll effect is now also glow
How can I make it 'bounce'?
Click to expand...
Click to collapse
hard work ... symply said forget it .
v1nsai or anyone else can give me some tips how to make bounce overscroll ? I have decompiled framework.jar.
Great, ill try
Sent from my SGH-I897 using Tapatalk 2
Hi, I've searched thoroughly through this and other forums, but this topic doesn't seem to interest many people...and even when there are questions, answers are often imprecise and evasive.
I'd like to know how to modify the toggle buttons in my statusbar. I want to remove the orientation switch (who uses it, seriously?), and add (for a total of 6 buttons), toggle data and 2G/3G switch...is that possible? Yes it is, it's Android
But how to do it? Is there a guide or even some files ready for flashing? I'd like to get rid of Extended Controls once and for all...
Thanks in advance, looking forward for an answer
Unfortunately it's not possible to edit those buttons on the Stock LG ROM.
remczar69 said:
Unfortunately it's not possible to edit those buttons on the Stock LG ROM.
Click to expand...
Click to collapse
Another good reason to switch to a cooked ROM
Anyway, can you post anything you are willing to (links to guides, files...) for doing this on other ROMs? And maybe a list of ROMs that allow this operation (or, at least, the characteristic they need to have, for example a certain kernel or other stuff).
Thanks in advance
I know for sure that CM 7 has that possibility. I use CM7 it is pretty stable for me.
it it possible to hide the buttons?
(using modaco r19)
thx
lixeira said:
it it possible to hide the buttons?
(using modaco r19)
thx
Click to expand...
Click to collapse
cook rom without buttons, you can choose in kitchen
75markus said:
cook rom without buttons, you can choose in kitchen
Click to expand...
Click to collapse
i know ... dont have modaco premium account
you can use apk manager to decompile the framework-res.apk file
then modify a file called status_bar_expanded.xml (found in /res/layout)
then compile it
i have made the edits to the files, but i cant get it do compile again
(attached the xml file, rename the file back to .xml)
Mjuksel said:
you can use apk manager to decompile the framework-res.apk file
then modify a file called status_bar_expanded.xml (found in /res/layout)
then compile it
i have made the edits to the files, but i cant get it do compile again
(attached the xml file, rename the file back to .xml)
Click to expand...
Click to collapse
Not that skilled yet still learning ... but thanks
i'm not that skilled either so don't mind it
i just can't get it to recompile
I made a thread in the Android General section, but it must not be getting attention from anyone capable of deodexing an apk, or just nobody wants to do it.
I probably should have created the thread here, so I'm linking to it here.
http://forum.xda-developers.com/showthread.php?t=1504082
Thanks all
bizzump
+10char
There's a few things we need to know first. Why only one apk? Why not deodex your whole ROM? Or if you have a copy of the whole ROM could your send it to me…..I can't deodex just the SystemUI when it has dependencies on the other functions within the ROM i.e. Framework.jar.
Or if you could explain maybe what your hoping to achieve I could probably sort somethingout for you a much simpler way.
What phone do you have and what apks are you using now? If you want to theme or want some sort of function from an apk that’s not yours but is odex version there may be a way of breaking it down to its classes (if I knew what ROM it was from and you had the entire framework folder from the ROM along with the odex file) and then I can decompile the apk you use (I think that’s what your trying to achieve correct?) from your ROM, then bring the classes and/or pngs across, rebuild, re-optimise (not odex btw) and send it back to you maintaining the signature for your apks in your ROM.
The phone and rom it is running are in my sig. I only want the SystemUI deodexed so that I can make the status bar transparent and still enjoy the slightly improved performance of an odex'ed rom, because this is a low-end phone so anything to increase performance helps. I have also tried using the AutoDeo Tool, but I don't know how to figure out what the correct custom bootclass path line input should be.
I asked for some help in that thread this morning and feel that I'm getting closer to having a deodexed SystemUI. I hate having posts in so many places about the same problem, but it seems like not a whole lot of people know how to do it, and even fewer want to explain such a complex process.
Hopefully I'll be able to deodex my entire rom.zip and just replace the systemui that's on my phone with the deodexed one and delete the .odex file and everything will be ok.
Sent from my SGH-T499 using XDA App