Develop Bugs

[Q] [Q} ROM Vs Theme

Hi Guys,
Kinda n00b question:
Whats the difference between a ROM and a Theme? I'm running SimplyHoney 3.8 on my SGS, which I understand is a ROM. I want to apply a new theme, but from the installation guides it looks like its installing a ROM... so:
1. Will installing a theme wipe my apps and configs?
2. Whats the actual difference?
3. Do I need to get a theme to match my ROM?
I'd really appreciate answers, or directions to where should I ask this.
Many thanks,
SoundFX3D

1. Theme will only affect the appearance.
2. Rom is sort of like a package with all the features and tweaks included by the developer(s) which also has its own theme.
3. In the case of SimplyHoney, its has a blue theme. You can choose to flash another theme if you don't like blue. Just make sure its compatible with your rom version.

And no themes almost never wipe data so all your apps will remain.
Also on the subject of Simply Honey if you install a theme that you don't like or doesn't function as expected you can simply re-flash the Simply Honey rom and it wont wipe as it auto detects. You be right back where you started.
Sent from Simply Honey, Loved by Humans, Envied by Trolls! Using XDA premium of course.

basicly almost all so called roms out there are themes with kernel attached
90% or more files inside their 200mb packages are matching stock ones
but that way new user thinks, hell lot of good job i will donate =)
most of roms claims best stability, best speeds everything best
while speed depends on kernel used and system version basicly
so you have same insides in every each one of them with one of few kernels out there
only thing that difers them is theme used
everything is more or less placebo

Thanks a million u guys

$omator, I think that when you get a room you get a theme + kernel + android stuff + some apps that work well together (or should). So developers should have some credit.
Buy it is true that a 100% real rom is something like cyagonenmod.
Sent from my GT-I9000 using XDA App

most of files are same as in stock trust me

$omator said:
basicly almost all so called roms out there are themes with kernel attached
90% or more files inside their 200mb packages are matching stock ones
but that way new user thinks, hell lot of good job i will donate =)
most of roms claims best stability, best speeds everything best
while speed depends on kernel used and system version basicly
so you have same insides in every each one of them with one of few kernels out there
only thing that difers them is theme used
everything is more or less placebo
Click to expand...
Click to collapse
well, Only thing I will agrre on is , the kernel builders and themers do NOT get enough credit for there work compare to rom builders, thats sad but again huge 'unknown difference between guy that make the voodoo stuff and guy that just compile it .
For the rest I disagree .. plain and simple , the way the framework files are handled when modified and how junk files/ids values present depends on the builder , the updater script, optimization of pngs, deodexed zip aligned , the init.d script chosen to go with the kernel are 90% of what makes a rom , on first boot when your dalvik is created the rom stability is created, some badly themed apks wont even run on first boot they require already present dex files so the system can correct the errors after the initial first boot (witch is long ) themers dont have to worry about that , but throw there files ina stock deodexed rom and flash iit full wipe letssee if your phoen runs smooth 'just becuz its 'JVQ with the latest OMG kernel.... 10% is placebo no doubt .. certainly not 90%%%
of course they are some rom chefs that take the work of others theme it and call it there ROM thats another story...
btw dont you run stock rooted kernel on odexed rom ??? if so thatwoudl lead me to believe you are VERY biased ....

DAGr8 said:
well, Only thing I will agrre on is , the kernel builders and themers do NOT get enough credit for there work compare to rom builders, thats sad but again huge 'unknown difference between guy that make the voodoo stuff and guy that just compile it .
Click to expand...
Click to collapse
same with galaxian kernel, it is bunch of features from every other kernel + bugs
bugs that are bugfixed every single day and new final version is delivered, that is said by him the best fastest stable bugfree and so on ....
this guy claimed 170$ for fixing bugs that he have made and that could be ironed in betatesting process if he would conduct one and features from other kernel devs basicly ;]
his thread lacks of current sources - i am suprised that his thread still exists and he is not kicked out
DAGr8 said:
For the rest I disagree .. plain and simple , the way the framework files are handled when modified and how junk files/ids values present depends on the builder , the updater script, optimization of pngs, deodexed zip aligned , the init.d script chosen to go with the kernel are 90% of what makes a rom , on first boot when your dalvik is created the rom stability is created, some badly themed apks wont even run on first boot they require already present dex files so the system can correct the errors after the initial first boot (witch is long ) themers dont have to worry about that , but throw there files ina stock deodexed rom and flash iit full wipe letssee if your phoen runs smooth 'just becuz its 'JVQ with the latest OMG kernel.... 10% is placebo no doubt .. certainly not 90%%%
Click to expand...
Click to collapse
agree about the wipe, does not agree that optimizing zipaligning and all that are necessary
still majority of copied files are intact that is what ive ment
and those roms are basicly themes as if you would take the custom kernel out that is what your left with, a theme - that is my opinion i will try to hold on
DAGr8 said:
of course they are some rom chefs that take the work of others theme it and call it there ROM thats another story...
Click to expand...
Click to collapse
or they leave old version of apps just because 'they still work on new version"
what is basicly reverting their theme/rom to a previous firmware revision
because those new files in most cases contain aside of some language bugfixes
a real bugfixing or optimization of code - but hey one say, it still works with the old one =)
DAGr8 said:
btw dont you run stock rooted kernel on odexed rom ??? if so thatwoudl lead me to believe you are VERY biased ....
Click to expand...
Click to collapse
nooo i tested few kernels back in the days
i know hardcore makes something special

Interesring discusion, I am learnig a lot.
Sent from my GT-I9000 using XDA App

[GUIDE]simple tips choosing a custom ROM

I've seen a lot of new member here. I hope this thread might help them decide what ROM are best for them and reduce the number of question. however, I won't mention any rom in this forum to keep this thread from my subjective point of view. you should see the development section by yourself to find your best suited rom for you.
OK. lets get straight to the topic. this is some things that you should consider when you choose a custom rom. I'll divide the guide into three main parts two make everything is easy to understand. the parts are performance, style, and additional consideration.
##PERFORMANCE##
Click to expand...
Click to collapse
1. debloatware
debloatware is a process to remove considered useless apk from the system. every rom has different degree of debloatware. a hight degree debloatware means you'll have only use a little of ram space for system app. however we'll lost some of sync function like kies synchronization if we remove all bloatware from the system. make sure that you still have all the app you need from stock rom in your custom rom.
2. deodexed vs odexed
Most of custom rom available is deodexed rom while our stock rom is half deodexed rom. I'll try to explain it in most simple way. First of all, we should understand that mostly every app in android consist of three part, *apk files, *dex/odex files, and lib files.
ODEXED rom means that *dex file needed to run the app is extracted from the apk file and placed in same folder with the apk files (/system/app). the positive side, it is tend to more stable and consume less internal memory and a execute faster. it is also faster since the system doesn't have to build dalvik cache at boot process. the negative side, it makes the app uncostumizable (cannot apply custom themes) and need more space in system partition.
DEODEXED rom means that *dex file needed to run the app is extracted from the apk file and placed in /data/dalvik-cache. the positive side, the app can be themed (full customizable) and consume less system partition. we could put more app in /system/app in deodexed rom. the negative side, it consume a lot of internal memory. the system also might a little bit slower since the system need to build a lot of dalvik-cache when the phone start.
3. custom kernel
a custom kernel could give you a huge boost of performance. for the most basic one, you should choose a kernel with init.d support. we'll need it to run a lot of performance tweaks. if you're seeing a custom kernel, you should look into these point:
- custom governoor
custom governoor will give you a lot of option to set your device performance. you can set the performance as hight as possible or save your battery as long as possible by set the correct governoor.
- custom scheduler
its almost same with custom governoor. however it manage I/O on your device. it won't give you a huge boost on performance but you should consider it as your main consideration.
- droidwall support
- a2sd and swap support
- additional feature
- bug and rom compatibility
not all custom rom compatible with all custom kernel. make sure that your custom kernel is compatible with your rom.
4. performance tweak availabilty
for a basic consideration, make sure that your rom have a performance tweak. otherwise, you'll got only a themed rom with stock performance. if you're a performance person, make sure your rom is have these tweak.
- memory management optimization
- hsdpa optimization
- kernel and I/O optimization
- gps optimization
- internet speed optimization
these tweaks are could be found at build.prop, init.d, sysctl.conf, and gps.conf.
5. additional tweaks
there are also some additional tweak you should consider if you want to install a rom. the commonly used are:
- bravia engine
- sound enhancement
6. performance app
some ROMs offer performance tweak app like ROM manager inside it. you should consider these app if you're a performance person
##STYLE##
Click to expand...
Click to collapse
1. theme
this is a very subjective topic. you should choose a rom with a topic suit with your style.
2. degree of customization
every rom has certain degree of customization. if you're a themed person, you should consider these point for your rom.
- EDT tweak for statbar customization
- ROM'S lab
- customizer app
- theme availability
3. ROM special app
some of ROM have special app for their rom. they're specially developed for only certain roms and comes with special names and various function. these app will give you a huge power for style and performance customization.
##ADDITIONAL CONSIDERATION##
Click to expand...
Click to collapse
1. update availability
some ROMs are good but they're left undeveloped. you won't get an update for your rom. you should choose a rom with a continous update from the dev to ensure you get the best rom for you.
2. dev support
not all ROM maker are really a dev. some of them just a wannabe dev with a theme modified rom skill. you can't expect them to solve the bug in their rom. you should choose with a good reputation and high skill.
3. rom size
this is not a huge issue. if you have a slow internet connection, a smaller rom is better for you. smaller rom also means a big degree of bloatware. the system will be lighter than the other rom.
4. rom base
some of rom are using old firmware (--KL) while some other are using newer firmware(--LB or newer). you should aware of these stuff since not theme and mod available in our forum are compatible with all firmware. new firmware will give you more stability but in most case you can't have custom bootanimation.
5. multilanguage
this is not a huge issue but you should consider it as well. not all rom support japanese, chinese, arabic, spain and latin fonts.
DISCLAIMER: REMEMBER THAT YOU'LL NEVER GET ALL IN ONE PACKET ROM. ALL ROMS HAVE THEIR STRENGTH POINT. YOU CAN'T EXPECT ANY DEV TO MAKE "A PERFECT" ROM FOR EVERYONE. IF YOU DON'T SATISFY WITH YOUR ROM REMEMBER THAT YOU CAN ALWAYS CUSTOMIZE YOUR ROM BY YOURSELF.

Reserved for dunno
just in case

This thread really help me to create my own custom rom with world best future ......... many many thanks for the great thread .....
Sent from my GT-S6102 using Tapatalk 2

If i use to create odexed rom is it support all tweaks ..
And if i costmize only systemui /firmwork * (deodexed)
With odexed rom its support or not...
Sent from my GT-S6102 using Tapatalk 2

if you want a customizable theme you can make your systemUI.apk as a deodexed apk. if your apk have classes.dex inside it you'll need to delete systemUI.odex from your system.

Can i add a link to this in FAQ bro?
This is basic but very useful for newbies

yes sure...

which rom in your openion is preferrable
which hit high ends

explodeaamir said:
which rom in your openion is preferrable
which hit high ends
Click to expand...
Click to collapse
wat r ur expectations from a rom?

explodeaamir said:
which rom in your openion is preferrable
which hit high ends
Click to expand...
Click to collapse
that is an unending debate, anyway for me
stability - stock ROM

I already have all my tweaks needed for my rom. If anyone asked "what rom do you like?" I'll answered "just a stock rom but with a better graphic and sound driver". however, I'm afraid we've to build it from source to get it

More questions
Great explanations bro, specially for nobs like me
My questions are:
1- How can I know if the ROM totally support Arabic-Language?
I live in Saudi Arabia and My SGY comes with XXLC1 stock ROM.
2- Is there any other stocks than XXLC1 ROMs I can use and still support Arabic and Modem-settings in my region?
I notes that most if not all custom ROMs based on Different stocks than mine.
I know, it sounds like I answered my first question in the second one, but still I need more clarifications.
3- Now I'm using REMIX ROM with [email protected] Kernel, based-band S5360XXLC1. Still, I can't have full Arabic interfaces and
my browsers cant read Arabic too. I wounder why?
Sorry for the very nob questions and Thank you very much.

Few questions about building your own rom

Well cyanogen 7.2 is out. Repost, because I posted in the wrong section previously.
I think I'm going to build a lightweight rom go launcher based rom off of it. First try ever I've done a lot of experimenting.
I intend on removing languages, apps that I never have had any remote desire to use (vpn, fmradio, that kind of thing), and create a basic high performance mod.
I'd like to incorporate the tiamat kernel somehow. Also I'd like to force smartassv2, and custom calibration settings, but I'm having a bit of a hard time finding where those settings are saved in the zip.
Does anyone know where the file is saved, for adjusting autobrightness defaults?
I'd would like to zipalign it, and if I can, odex it.
Also I am going to try to run PNGout on all of the PNG files.
Anyone have any suggestions on best tools to do all of these things from a windows or ubuntu based linux perspective? I know how to remove the APKs, and using PNGout seems pretty straight forward.
I'm not opposed to recompiling, if thats the best method to odex.
Also, any suggested performance optimizations?
Build.prop flags?

There are plethora of tools in the chef section.
Sent from my Go Senseless Classic Conflagration Evo

Angelus359 said:
Well cyanogen 7.2 is out. Repost, because I posted in the wrong section previously.
I think I'm going to build a lightweight rom go launcher based rom off of it. First try ever I've done a lot of experimenting.
I intend on removing languages, apps that I never have had any remote desire to use (vpn, fmradio, that kind of thing), and create a basic high performance mod.
I'd like to incorporate the tiamat kernel somehow. Also I'd like to force smartassv2, and custom calibration settings, but I'm having a bit of a hard time finding where those settings are saved in the zip.
Does anyone know where the file is saved, for adjusting autobrightness defaults?
I'd would like to zipalign it, and if I can, odex it.
Also I am going to try to run PNGout on all of the PNG files.
Anyone have any suggestions on best tools to do all of these things from a windows or ubuntu based linux perspective? I know how to remove the APKs, and using PNGout seems pretty straight forward.
I'm not opposed to recompiling, if thats the best method to odex.
Also, any suggested performance optimizations?
Build.prop flags?
Click to expand...
Click to collapse
The best tools to use to start learning to make create your own roms is use the kitchen,it will zipallign and deodex all that good stuff,like the guy above me said, theres alot of other guides and tools here that will help you with your venture....

[ROM] AT&T Stock Properly De-Odexed LG1 OTA System...

This is mostly for new devs that want a stock build to work with, or just want to use the latest files & firmware version with their unlocked & rooted device.
All of the stock files are in this rom. The only changes made are busybox, SuperSU (Faster responses than traditional SU in my humble opinion), & I tore a lot of the apks down to java & applied diffpatches from the OTA update to all applicable apk & jar files, De-Odexed 100% & zip aligned. This currently includes the stock rooted kernel & will also work with the kernel by NunHugger (which supports init.d & custom boot images). You can easily change kernels with WinRAR or WinZip by making certain that "no compression" is selected & then drag & drop new boot.img to the root of the zip.
Also in the rom are the newer camera binaries & the other fixes from the AT&T LG1 OTA.
I did change the GoogleQuickSearchBox.apk so that on-device searches are still possible.
Rom include latest SuperSU & a working busybox 1.20.2 build.
Other than that, this is a fully bloated & stock AT&T rom & contains the stock rooted kernel. If you would like init.d support or anything else added, just let me know. I don't believe in init.d, & personally believe in editing xml's or boot init files to accomplish init tasks, but I'll add if desired. I am working on modding the LG1 kernel to have UV/OC function, but other than that, not much else.
This will
I am working on applying the diff patch to the kernel source, so that the kernel will match the LG1 system. However, I am having trouble with occasional bootloops when battery is under 30%. Could be the source, but most likely it is the fact that I haven't played with 100% stock source much, let alone Samsung source.
At any rate, do what you will with this. It is there to do with as you like, or not...
MD5: 1474aaffe7c178f939498da3a87469e3
Link: https://docs.google.com/open?id=0Bxxb003sdLoJZS1kUDJYcnVaXzg
*I will add a second link with updated apk's so that no google play updating is needed.
UPDATE: New version with most of the frequently updated apps located in Data/App to avoid duplicates & allow users to uninstall.
MD5: af4381d027abaec2e96828aa2799037f
Link: https://docs.google.com/open?id=0Bxxb003sdLoJNkFhSFB4M0N5ZUk
***Devs - Anyone familiar with Sammy source & willing to provide any assistance in patching the ALEM Kernel source to ALG1, it would be appreciated!

_just in case....

Am I missin something or where is the link to download - I like having a back up of the latest Stock "just in case' -
Oh - I see this is a fairly recent post - is the "upload" still processing?

Waiting for this as well.
Sent from my SGH-I747M using xda premium

I should lock this is but ill give you the benefit of doubt.

Mr.Highway said:
I should lock this is but ill give you the benefit of doubt.
Click to expand...
Click to collapse
What, a 9 hour upload time is excessive?

RampageRR said:
What, a 9 hour upload time is excessive?
Click to expand...
Click to collapse
Yes

GSLEON3 said:
This is mostly for new devs that want a stock build to work with, or just want to use the latest files & firmware version with their unlocked & rooted device.
All of the stock files are in this rom. The only changes made are busybox, SuperSU (Faster responses than traditional SU in my humble opinion), & I tore a lot of the apks down to java & applied diffpatches from the OTA update to all applicable apk & jar files, De-Odexed 100% & zip aligned.
Also in the rom are the newer camera binaries & the other fixes from the AT&T LG1 OTA.
I did change the GoogleQuickSearchBox.apk so that on-device searches are still possible.
Other than that, this is a fully bloated & stock AT&T rom.
I am working on applying the diff patch to the kernel source, so that the kernel will match the LG1 system. However, I am having trouble with occasional bootloops when battery is under 30%. Could be the source, but most likely it is the fact that I haven't played with 100% stock source much, let alone Samsung source.
At any rate, do what you will with this. It is there to do with as you like, or not...
***Devs - Anyone familiar with Sammy source & willing to provide any assistance in patching the ALEM Kernel source to ALG1, it would be appreciated!
Click to expand...
Click to collapse
Were is the link ??

So
what happened? Waiting...

LOL...Damn T1 line went down, traffic was bad & forgot when I got home. :silly:

1st in after the link lol. Thank you for your contribution look forward to trying it out!
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

So can you flash a different kernel like ktoonez just using cwm?

Yessiree.
Any kernel in the AT&T section I have tried so far has worked fine.
And if anyone wants, I can remove the debugging crap from all of the jars & apks to trim the files down further.

So the modem didnt change? Mine is still the same just curious
Edit: my bad forgot its just ota and just patches on the side note why no just make flashable zip of the removed apk if ever you debloat the rom
Sent from my SAMSUNG-SGH-I747 using xda premium

remove the debugging crap!
GSLEON3 said:
And if anyone wants, I can remove the debugging crap from all of the jars & apks to trim the files down further.
Click to expand...
Click to collapse
Actually - yes, please do and share! We're all after efficiency and optimized stock experience.

Curious as to why you didn't debloat this?

tomween1 said:
Curious as to why you didn't debloat this?
Click to expand...
Click to collapse
It is really meant to be a base for other's that wish to begin learning to cook. That way there is a base rom that is 100% stock for them to add to or deduct from as they choose. However, if you wish, I can do a de-bloated version. I have a new version as well, that still has bloat, but most of the frequently updated apps are in data/app & named so they are properly handled by updates.

Is there any consensus as to what is "Debloated" besides removing the AT&T crude? I usually remove gmail, I don't need two email clients, Flipboard, is gone, awww heck, I'll just do whatever & if ya'all want something back I'm sure I'll hear it.

GSLEON3 said:
It is really meant to be a base for other's that wish to begin learning to cook. That way there is a base rom that is 100% stock for them to add to or deduct from as they choose.
Click to expand...
Click to collapse
Just like the one I released. Only this is based on patches from the newer OTA.
Sent from my SAMSUNG-SGH-I747 using xda premium

GSLEON3 said:
Is there any consensus as to what is "Debloated" besides removing the AT&T crude? I usually remove gmail, I don't need two email clients, Flipboard, is gone, awww heck, I'll just do whatever & if ya'all want something back I'm sure I'll hear it.
Click to expand...
Click to collapse
Well if you do a de-bloated version, anybody that wants the app's you've pulled can pull them from your first one and install what they want. Also thank you

[Q] Questions for the devs

Hello devs I was wondering if you guys are able to help me out with an inquiry question. I been researching online for guides on how to create your own roms and cook roms but the information is so overwhelming that I don’t know what to do or where to start. Here I was wondering how you guys learned, and what guides did you use. So far I have only experienced basic programming in python along with c++ but just basic stuff. What kind of programs do I need and how should I start what advice can you guys give me? Anything helps. I know you guys are busy with tweaking the jellybean source trying to port cm10 and aosp , but if you guys have time I would really appreciate it if you guys would help me out. May be it will be good for the long run maybe if I get the hang of it I would be creating roms and tweaks for the community, but the main thing I want to learn.
Thanks for taking your time on reading this message devs.

There are 3 forms of roms.
Source built(best/hardest) - cm,aosp,etc
Ports(medium difficulty) - sense, touchwiz, miui, etc
Modified stock(easiest) - any modified stock rom.
Each type requires different levels of knowledge. For stock roms you could make one using your phone(my first stock rom was made using nothing but root explorer), but i would recommend a decent zip program to unzip the rom at least. If youre serious about deving then you need linux. Ubuntu is the most supported. Windows will work but you need to have a good zip program, notepad++, maybe a kitchen or other tools for deodexing, decompiling frameworks/apks/etc and of course sdk installed.
Most stock roms are just slightly modified, a few scripts, removal of bloat, etc. More advanced mods would be themeing and framework editing to add or remove features. A popular mod is the power options mod that gives reboot to recovery when you hit the power button.
If you want to know where to start i would say start with theming. Its harder than basic roms but worth it because you learn more from the experience. You can either theme an existing devs rom or make your own. Personally i think its best to theme the stock rom and only include your changes in your cwm zip. So if you modify the frameworks and other aspects of the rom you dont need to release an 800mb zip just for a pink notification bar.
Example mods would be lock screens, themes, changes in text, adding features from other roms, etc.
If you have questions just ask.
Sent from my LG-LS970 using xda app-developers app

jokersax11 said:
There are 3 forms of roms.
Source built(best/hardest) - cm,aosp,etc
Ports(medium difficulty) - sense, touchwiz, miui, etc
Modified stock(easiest) - any modified stock rom.
Each type requires different levels of knowledge. For stock roms you could make one using your phone(my first stock rom was made using nothing but root explorer), but i would recommend a decent zip program to unzip the rom at least. If youre serious about deving then you need linux. Ubuntu is the most supported. Windows will work but you need to have a good zip program, notepad++, maybe a kitchen or other tools for deodexing, decompiling frameworks/apks/etc and of course sdk installed.
Most stock roms are just slightly modified, a few scripts, removal of bloat, etc. More advanced mods would be themeing and framework editing to add or remove features. A popular mod is the power options mod that gives reboot to recovery when you hit the power button.
If you want to know where to start i would say start with theming. Its harder than basic roms but worth it because you learn more from the experience. You can either theme an existing devs rom or make your own. Personally i think its best to theme the stock rom and only include your changes in your cwm zip. So if you modify the frameworks and other aspects of the rom you dont need to release an 800mb zip just for a pink notification bar.
Example mods would be lock screens, themes, changes in text, adding features from other roms, etc.
If you have questions just ask.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
i want to thank you for replying back im going to start out tomorrow and see how far i get and im glad you and maybe other people are willing to help. i appreciate you taking your time for explaining some differences and i will need help but atleast i know i wont be ignored thanks again :victory:

If you have any questions or issues just ask any of us.
Sent from my LG-LS970 using xda premium

Most devs will help, it just comes down to time. If im bored at work ill be online. Most of the stuff i used to do involved a very useful set of servers that allowed me to modify source, build, and place on my site all from my phone. I dont have that setup anymore so im limited to my build computer.
Look through the android forums for some useful tools and guides to get started. Every dev started where you started so keep your chin up
Sent from my LG-LS970 using xda app-developers app

jokersax11 said:
There are 3 forms of roms.
Source built(best/hardest) - cm,aosp,etc
Ports(medium difficulty) - sense, touchwiz, miui, etc
Modified stock(easiest) - any modified stock rom.
Each type requires different levels of knowledge. For stock roms you could make one using your phone(my first stock rom was made using nothing but root explorer), but i would recommend a decent zip program to unzip the rom at least. If youre serious about deving then you need linux. Ubuntu is the most supported. Windows will work but you need to have a good zip program, notepad++, maybe a kitchen or other tools for deodexing, decompiling frameworks/apks/etc and of course sdk installed.
Most stock roms are just slightly modified, a few scripts, removal of bloat, etc. More advanced mods would be themeing and framework editing to add or remove features. A popular mod is the power options mod that gives reboot to recovery when you hit the power button.
If you want to know where to start i would say start with theming. Its harder than basic roms but worth it because you learn more from the experience. You can either theme an existing devs rom or make your own. Personally i think its best to theme the stock rom and only include your changes in your cwm zip. So if you modify the frameworks and other aspects of the rom you dont need to release an 800mb zip just for a pink notification bar.
Example mods would be lock screens, themes, changes in text, adding features from other roms, etc.
If you have questions just ask.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
very cool joker... made that very easy to understand for all levels of knowledge