Develop Bugs

[Q] What does it mean when devs say their ROM is optimized?

In the description for many ROMs devs say they are optimized, zipaligned, de/odexed, etc. What do they mean by optimized? In other words, what are different ways other than zipaligning and odexing that a ROM could be modified for better performance?
Thanks

cengator said:
In the description for many ROMs devs say they are optimized, zipaligned, de/odexed, etc. What do they mean by optimized? In other words, what are different ways other than zipaligning and odexing that a ROM could be modified for better performance?
Thanks
Click to expand...
Click to collapse
Zipaligning helps with RAM, I use a script to zipalign every time my phone boots
Deodexed I believe makes it so u can remove system apps...ect
Overall it speeds up the phone. Try the odexed and the deodexed versions of the stock Rom. U will see a difference
Sent from my HTC Incredible using XDA App

superchilpil said:
Zipaligning helps with RAM, I use a script to zipalign every time my phone boots
Deodexed I believe makes it so u can remove system apps...ect
Overall it speeds up the phone. Try the odexed and the deodexed versions of the stock Rom. U will see a difference
Sent from my HTC Incredible using XDA App
Click to expand...
Click to collapse
Thanks. Yeah, I know what zipalign and deodexing are. If a dev says his rom is "optimized, zipaligned, and deodexed," he is doing something additional besides those two. I'm wondering what that might be.

Generally image optimization. Although some dev's actually do improvements such as stripping the extra localizations. Stock images are already optimized unless you edit them, well all the ones I've check anyway.

i do all kinds of stuff and still don't know what zipaligned means/does

When devs say they optimized there rom or framework etc... It means they ran a tool such as apk manager (what I use) to compress all the images in an apk to be the smallest size they can get them without losing quality. This will speed up the build for maximum performance and less ram usage.
Other people say there apks are Reengineered. This means that there apks have all unused lanuages removed for even better performance.
Odexing means Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace files (not having to worry about odexes). Odexed builds such as stock roms cannot be themed for the most part.
Zipalign is an archive alignment tool introduced first time with 1.6 Android SDK (software development kit). It optimizes the way an Android application package (APK) is packaged. Doing so enables the Android operating system to interact with the application more efficiently, and hence has the potential to make the application and overall the whole system much faster. Execution time is minimized for zipaligned applications, resulting is lesser amount of RAM consumption when running the APK.
Hope this helps,
Incubus

Wow! Thank you very much! That is very informative. Regarding deodexing, other optimizations being equal, would an odexed rom have greater performance than a deodexed rom?
Sent from my ADR6300 using Tapatalk

incubus26jc said:
When devs say they optimized there rom or framework etc...
Click to expand...
Click to collapse
What does the difference in framework mean?
I found this website( http://androidforums.com/incredible-roms/155282-incredible-rom-list.html ) to try and find some new roms to use, because i'm stuck at the white screen of death on my Dinc. See this post if you want to help ( http://forum.xda-developers.com/showthread.php?t=1023358 )
BUT my actual question is what does framework mean? Are all of those "frameworks" listed compatible with my phone? I know that the Dinc uses the "Sense UI"...are these the same? Can I install "vanilla" framework ROMS on my Droid Incredible? If I do, is there certain things that won't work? Sorry for all the newbish questions, but I'm already soft bricked and want to know before I go messing around with stuff again. Seems I only knew just enough to get me into trouble and bring me to a white screen, and I don't want to do further damage.
Thanks a ton.

Adjusting lowmemorykiller settings in a boot.img

Hello, I have 2 custom roms for my phone, they are gingerbread based stock roms. One has perfect ram management (strict), and the other has more relaxed ram management settings. The first rom runs smooth and has great battery life, the second still runs fairly smooth, but has some app instability do to low ram, and the launcher closes often. Battery life is not as great on the second rom. But the second rom has some great additions to the first, that I would rather not loose. I would like to transfer the lowmemorykiller settings from rom 1, to rom 2. Or edit the settings in Rom 2 somehow. However I'm a noob, and have windows, and cannot make sense of splitting the imagefile, editing the ramdisk and repacking it to a flashable image. Is there a way to change the settings with root manager? OR an iso image editor, or something that can open the img file, and allow me to edit the ramdisk, without linux, and special coding and fancy wizardry?
Sorry for the long post. Another alternative was to swap the boot.img from the two roms, but I'm not sure what other settings were changed in it.
Any thoughts or tips would be greatly appreciated.

Ok, sorry I asked. I just figured someone here would know how, and might care to share some tips.

[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

need help for sense int.d and build.prop

hello guys i wanna know what things i can delete and what things i can not delete in int.d and build.prop from sense based roms can someone give me a list?

What's in init.d will likely vary across any rom, sense based or not. Not sure about build.prop as never changed it, but i'm guessing it's not the same for all roms either.
For instance, init.d likely contains an app2sd script of some sort, perhaps even some tweaks which the dev might want to include. some are probably harmless, but deleting something you don't know about might make the phone unusable...
So therefore we can't just give you an definitive list of just what you can or can't delete....you could just nandroid backup and try yourself...
my return questions would be:
- why do you even want to delete things from init.d or build.prop
- what are you trying to actually achieve by doing so?
- ultimately, is it even worth it...

eddiehk6 said:
What's in init.d will likely vary across any rom, sense based or not. Not sure about build.prop as never changed it, but i'm guessing it's not the same for all roms either.
For instance, init.d likely contains an app2sd script of some sort, perhaps even some tweaks which the dev might want to include. some are probably harmless, but deleting something you don't know about might make the phone unusable...
So therefore we can't just give you an definitive list of just what you can or can't delete....you could just nandroid backup and try yourself...
my return questions would be:
- why do you even want to delete things from init.d or build.prop
- what are you trying to actually achieve by doing so?
- ultimately, is it even worth it...
Click to expand...
Click to collapse
1-i want to delete the old tweaks that can bad interact whit a tweaks package 2-those tweaks are for balanced gaming not hard gaming 3- yes, it worth a try

Porting Volume Cursor Control & Other Features into Stock OSS

So I am looking for a bit of help, as this is the first time I am attempting mods like this. Lack of Xposed has left me to resort to trying to learn and figure some of this stuff out on my own.
A couple assumptions & clarification I am making & looking for:
1. From reading on XDA, it should be fairly simple to port & cherry pick basic features from other OP5 ROMs and merge them into the Stock OP5 ROM
- referring in this case to a decompiled framework.jar.
2. I have found a specific Commit from the ResurrectionRemix ROM, which adds Volume Cursor Control to both InputMethodService.java & Settings.java. My assumption is that these two commits for this functionality can be copied directly into the respective Stock OOS files. Is this correct?
3. Lastly, I need to learn about recompiling framework.jar, but I am assuming once I make the appropriate changes, I just recompile and transfer to phone, set permissions and I'd be set.
Again, apologies if it is incredibly noobish to ask this, and I realize its probably easier to just flash ResurrectionRemix, but I am also looking to learn a bit too
Thanks for any help!
EDIT: btw, if this is better in Q&A, mods plz move

I have no idea how to help you but wanted to say good luck. Volume cursor control would be an excellent thing to add to OOS

That's not how it works. Those commits are applied to the source code, not to the already compiled files, which is what we oneplus releases.
Sent from my OnePlus 5

asuhoops8628 said:
So I am looking for a bit of help, as this is the first time I am attempting mods like this. Lack of Xposed has left me to resort to trying to learn and figure some of this stuff out on my own.
A couple assumptions & clarification I am making & looking for:
1. From reading on XDA, it should be fairly simple to port & cherry pick basic features from other OP5 ROMs and merge them into the Stock OP5 ROM
- referring in this case to a decompiled framework.jar.
2. I have found a specific Commit from the ResurrectionRemix ROM, which adds Volume Cursor Control to both InputMethodService.java & Settings.java. My assumption is that these two commits for this functionality can be copied directly into the respective Stock OOS files. Is this correct?
3. Lastly, I need to learn about recompiling framework.jar, but I am assuming once I make the appropriate changes, I just recompile and transfer to phone, set permissions and I'd be set.
Again, apologies if it is incredibly noobish to ask this, and I realize its probably easier to just flash ResurrectionRemix, but I am also looking to learn a bit too
Thanks for any help!
EDIT: btw, if this is better in Q&A, mods plz move
Click to expand...
Click to collapse
You can try to revert the commit to build RR without volume control, and then build REGULAR RR with their volume cursor control. Take both framework.jar files, decompile them using apktool and search for the Settings.smali and InputMethodeService.smali, they should be in similar folders as the RR source code.
Open smalis files and use a diff checker software or website, and if you can, add the new code into the OOS framework, but you may need to edit other stuff to get it working. I have very few knowledge in Android reverse engineering but this should be the right way to start, as you don't have access to full OOS source code

To simplify, you would need to download the source, see what commits are needed to include the feature you are looking to add.
Usually, there will be commits needed for settings and frameworks.
Cherrypick them, resolve conflicts if any, and build your first 'custom rom'

Yeah, I spent a **** ton of time on this the other day. Got some **** decompiled, even was able to "mostly" figure out where things should be inserted, placed etc.
Issues I ran into though was the decompilation process left tons of errors, weird things. Couldnt get anything to pack up back nicely. Unfortunately, don't have the programming background to actually write my own code.
Unfortunately, without the OOS source, I think this might be past me, since I do not have the knowledge or experience to resolve the issues decompilation raises