Database Develop

[Kitchen][Online] website which lets anyone bake a rom

Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.

you will get flamed for this
shararti said:
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
Click to expand...
Click to collapse
This really is an admirable goal, but you're attempting to bite & chew WAY more than your mouth can handle!!!
You're a web developer, good.
You have no experience in developing android roms, bad.
You want to develop a free kitchen, good.
You have no experience with cooking roms, bad.
You want developers to help you in exchange for a free kitchen for their rom, bad & good.
You don't know how to update the "update.zip" file and re-sign it, bad.
You don't know how to add an APK to the above mentioned "update.zip" file and re-sign it, bad.
You have a little bit of an idea, but want a clearer process, bad.
All of the above noted BAD points, have been discussed, referenced, and linked on these forums countless times shararti.
You really need to search, read, search some more, and apply what you've learned.
I too am a Web Developer/Designer. I've been in the business of creating websites since 1999 (off & on). And the above mentioned project it something I WON'T EVEN DARE ATTEMPT.
Good luck!

I did search, countless times, everywhere. But as lack of my experience with rom development, it was quite confusing. Well I do know signing and adding apk part, and the rest, i agree, i need some help. I'm willing to give my summer to this project and develop this kitchen for the xda community (i'm also willing to give it away to xda). Now if anyone is willing to help me, please pm me.

Actually, it isn't that difficult.
There are quite a few scripts and programs that you could simply employ on your website. I'm sure those developers wouldn't mind
You would have to tier your ROM baking based on the major ROM cores, and the features swappable between flavors of those cores.
It's simply letting the user choose what he wants in his base ROM, pushing the files into the zip, and running the script to sign them.
I'd be glad to guide you in the structure of ROMs, and showing you what can be mixed and matched.
PM me. We'll get started.

Sounds like a very cool idea and I wish you all the best and hope you find some programmers willing to teach you about roms, and you can do the web coding and make your idea a reality.
I'd use it for sure, would be wicked. Imagine going to this web page on your N1 customizing a ROM, building it and then flashing it. All without going near a computer. Sounds unreal!

APrinceAmongMen said:
I'd be glad to guide you in the structure of ROMs, and showing you what can be mixed and matched.
PM me. We'll get started.
Click to expand...
Click to collapse
Perhaps, share the information here once you two have things worked out?!
shararti said:
I did search, countless times, everywhere. But as lack of my experience with rom development, it was quite confusing ...
... I'm willing to give my summer to this project and develop this kitchen for the xda community ...
Click to expand...
Click to collapse
XDA is such a huge resource, full of solutions, bricked devices and lost newbs LOL.
After trolling for a few months, I was ready to flash my first WinMo SmartPhone a few years ago. I haven't used a 'regular phone' ever since.
This would be an ideal summer project. As I said, I'm also a Web Developer.
Hit me up for some theme/template ideas. I do most of my work with Notepad++ and Adobe Fireworks CS4.
Goonish said:
I'd use it for sure, would be wicked. Imagine going to this web page on your N1 customizing a ROM, building it and then flashing it. All without going near a computer. Sounds unreal!
Click to expand...
Click to collapse
hhmm, never thought of that!
You're right ... sounds unreal!
Something the iFans would never be able to attain.
Even better, how about, instead of flashing some large file, only the ones affected by an update are flashed, resulting in a much SMALLER file (thus saving on data usage) and a FASTER flashing (saying on battery life).

shararti said:
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
Click to expand...
Click to collapse
Well it all depends on what you want. I would suggest you have a base rom without the boot.img stored with minimal capability in a folder. then allow the user to choose what type of kernel and capabilities they would like with it. That will be the minimum amount for a rom. Then you can follow it up with additions such as extra scripts and applications that can be added and moved to the appropriate directories. at the end, you would zip up the selection and sign it, with the appropriate update-script (which should be the same as the stock rom's unless the additions require something drastic)
So the folder tree should look something like this for one specific ROM:
ROM/ROM Core Files (this is the base rom without boot.img)
ROM/ROM Core Files/META-INF (this is for the update zip)
ROM/ROM Core Files/system (this is where the system apps go)
ROM/ROM Core Files/data (this is where certain apps go)​
ROM/ROM Kernels (this is where kernels are/boot.img)
ROM/ROM Kernels/boot.img.1 etc​
ROM/Modifications (this is where apps and other mods go)
ROM/Custom Build (this is where the baked rom should go)
Then all you need to figure out is how to move everything to the custom build directory
Move the core to custom directory and a boot.img (rename it from whatever it is to boot.img) and then move and modifications to the appropriate directory inside the custom build folder. Then zip the custom build folder and sign it
That should be about right. its 3 am here lol so i may be missing something. pm me if you need more help or post here

Exactly.
The great thing about it. The ROM core files can be optional. You can bake a kernel or you can bake CM w/ custom kernel and custom mods, i.e. modded phone.apk. You can bake anything and everything.
Mmm baking never sounded so good.

Check this website out:
http://theunlockr.com/2010/03/26/ho...om-for-android-part-1-setting-up-the-kitchen/

My small contribution to this project
The basic kitchen:
forum.xda-developers.com/showthread.php?t=633246
Sorry it's not a link, apperantly new users cannot post links

flybyme said:
So the folder tree should look something like this for one specific ROM:
ROM/ROM Core Files (this is the base rom without boot.img)
ROM/ROM Core Files/META-INF (this is for the update zip)
ROM/ROM Core Files/system (this is where the system apps go)
ROM/ROM Core Files/data (this is where certain apps go)​
ROM/ROM Kernels (this is where kernels are/boot.img)
ROM/ROM Kernels/boot.img.1 etc​
ROM/Modifications (this is where apps and other mods go)
ROM/Custom Build (this is where the baked rom should go)
Then all you need to figure out is how to move everything to the custom build directory
Move the core to custom directory and a boot.img (rename it from whatever it is to boot.img) and then move and modifications to the appropriate directory inside the custom build folder. Then zip the custom build folder and sign it
Click to expand...
Click to collapse
Ok so after reading it 3 times carefully, this is what i got to:
All roms have same common files, which are:
1. the META-INF folder.
2. the system folder.
3. the data folder.
This is a basic skeleton of any rom, and every rom has these exact files.
Now what i have to do is, when a user cooks a rom, i have to pick the required boot.img and put it into the basic skeleton, in addition to any apps/modifications user want. Then zip the whole package and sign it.
Is that it?
PS: you also said that i may need to change update-script, in what cases that would be required?
PPS: Do i have to make changes to some other files too? cause it sounds too easy to be true =p

shararti said:
Ok so after reading it 3 times carefully, this is what i got to:
All roms have same common files, which are:
1. the META-INF folder.
2. the system folder.
3. the data folder.
This is a basic skeleton of any rom, and every rom has these exact files.
Click to expand...
Click to collapse
They usually have the same folders, not files
the META-INF has the signature files but most importantly the update-script which tells the phone what to do when your flashing the update.
shararti said:
Now what i have to do is, when a user cooks a rom, i have to pick the required boot.img and put it into the basic skeleton, in addition to any apps/modifications user want. Then zip the whole package and sign it.
Is that it?
PS: you also said that i may need to change update-script, in what cases that would be required?
PPS: Do i have to make changes to some other files too? cause it sounds too easy to be true =p
Click to expand...
Click to collapse
that SHOULD be it but remember that you may have to remove some apps from the core files of the rom such as amazon mp3 that people may not want, so you will have to see what apps can be removed and decide whether you want users to be able to remove it or not.
You MAY have to change the update-script if for example you want to put some things in the data partition and symlink them or change the data partition to include the ext partition instead of just for apps. Changes like that are usually for ROMs that are too big to fit properly on the nexus ( youll also have to check the size of the system and data folders to make sure they fit on the phone without modification)
Most of this stuff will be figured out in testing haha but ya at the very basicee its what you have here. You really have to know what you actually want users to be able to cook and then build the kitchen to that effect

flybyme said:
They usually have the same folders, not files
the META-INF has the signature files but most importantly the update-script which tells the phone what to do when your flashing the update.
Click to expand...
Click to collapse
So does that mean i can use same core for all custom baked roms? Except for the update-script, which in rare cases, may need to be altered.
flybyme said:
that SHOULD be it but remember that you may have to remove some apps from the core files of the rom such as amazon mp3 that people may not want, so you will have to see what apps can be removed and decide whether you want users to be able to remove it or not.
Click to expand...
Click to collapse
I took a look at system folder and it's quite populated. Can you tell me what are the basic files that are common for all roms? For the rest of the files, i guess i'll give the user choice to include them or not.
Also can you tell me what is zipalign? Will that be required in baking process?
And to let everyone know, I have already started the working on the kitchen =]

shararti said:
So does that mean i can use same core for all custom baked roms? Except for the update-script, which in rare cases, may need to be altered.
I took a look at system folder and it's quite populated. Can you tell me what are the basic files that are common for all roms? For the rest of the files, i guess i'll give the user choice to include them or not.
Also can you tell me what is zipalign? Will that be required in baking process?
And to let everyone know, I have already started the working on the kitchen =]
Click to expand...
Click to collapse
Well it really depends on what ROM's your looking at. Some devs change the apps to their liking. For example, CyanogenMod has a modified Settings.apk that has features specific to his rom. However, all ROMs have Settings.apk. As such, you will probably have to have a Core ROM folder for each specific rom.
I would suggest looking at other online kitchens and see what features they offer, come up with a specific feature set and then decide what direction that you want to take.
zipalign is a compression technique that optimizes how .apk files are accessed in android. it makes things faster and is not required but would be nice to have. you lose the benefits if you open and modify any files from a zipaligned apk

Let's clear some things up here.
First, core files are not interchangeable between main roms but only flavors of those main roms.
As of now, we have 3 main roms for the nexus one.
CyanogenMod, Modaco Custom ROM, and Desire/Sense Roms.
Each of these roms have their own unique cores amd features and are not interchangeable.
There are flavors of each of these roms.
Flavors of CM has parts that are interchangeable with other flavors but use Cyans core.
Say there is one CM flavor that has some themieing and a few other changes you don't want. You can take the themed files and put them into your CM base and leave the rest out.
You can't put that themeing into a Modaco Custom ROM though.
Kernels I believe are the only things can be put into any ROM base. Most apps are as well.
Now that I look at it. Doing a Nexus One kitchen isn't that difficult but making a full featured HTC kitchen would be a mountainous task. There are so many mods, roms and themes to keep track of. We'd have to designate people from each device forum to feed us the ROMs and parts that are active and functional.
P. S. Lectures are over at 7 today. ill be able to crack down on it with you then

Kitchens are for the Food Network...

well thanks flybyme and APrinceAmongMen, these 2 posts really cleared up somethings. I'm in the process and will keep you guys updated.

QUESTION: how do i change the radio and boot animations in a rom?
PS: the good news is, i'm done with all the hard part, and just few small things remaining. Probably if anything else doesn't comes up, you guys should have a n1 kitchen within few days =D

shararti said:
QUESTION: how do i change the radio and boot animations in a rom?
PS: the good news is, i'm done with all the hard part, and just few small things remaining. Probably if anything else doesn't comes up, you guys should have a n1 kitchen within few days =D
Click to expand...
Click to collapse
boot animations are located either in /data/local or /system/media
radio flash will require you to change the update-script
you can look at the FRF50 update with the radio to figure it out ( or pm me if thats too difficult, its a little late else id do it myself)

Just make sure the radio is excluded by default.
Another thing about radios, the newest radio usually works on older roms, but old radios don't work on the roms released with and after the newest radio.

Kernel compilation for Samsung Galaxy S I9000

Hi all,
we are trying to build our own kernel for a Samsung Galaxy S (I9000XWJVB).
What we did so far:
- Download the correct sources from "opensource.samsung.com"
- Studied the README
- Installed cross-compiler toolchain
- Created ".config" as described in README
- Kernel compiled
Compilation worked fine -> zImage was available (but with only 2mb very)
OK, looks like initramfs is missing.
The first question is now, where to get / how to create a correct initramfs?
We copied the initramfs from Leshak and we extracted an ".cpio" from a working zImage.
Then we tried to use them in the ".config" (CONFIG_INITRAMFS_SOURCE) for kernel compilation.
Resultant zImage was larger (around 6mb) so it looks like something changed.
But once we installed the tared zImage on the phone (using Odin), the phone freezes during reboot.
Any advice how to progress here?
Is it possible to use Leshaks initramfs for all Galaxy S phones? Or is this only for a specific version? The CONFIG_INITRAMFS_SOURCE should point to the "initrd.arm.initramfs_list", correct? And not to the initramfs-folder?
And: Is there a way to get any type of kernel boot debugging message from the booting phone back to the PC (or the phone screen)?
Many thanks in advance!

I don't know much about kernels. But i will try to help. Have you tried other itiramfs or reconfig them?
There are not many people that will know answer so ask some kernel developers like hardcore, supercurio...
Sent from my GT-I9000 using XDA Premium App

Just saw 2nd question. I think that it should point to intiramfs folder. You can zip all kernel files and upload it so i can take a look at them
Sent from my GT-I9000 using XDA Premium App

Hi,
themate1987 said:
I don't know much about kernels. But i will try to help. Have you tried other itiramfs or reconfig them?
There are not many people that will know answer so ask some kernel developers like hardcore, supercurio...
Click to expand...
Click to collapse
we tried four different initramfs now, but ended up always with a freezing phone.
I would like to ask the kernel experts directly, but I'm new to this forum and not allowed to post in the developers forums. I hope that one of the gurus will reply to this thread.
themate1987 said:
Just saw 2nd question. I think that it should point to intiramfs folder.
Click to expand...
Click to collapse
My understanding is that the .list file will describe the structure of the initramfs folder and if this file is present, it should by used in the .config. Otherwise the .config should point to the folder.
Please correct me if I'm wrong.
But anyway, we tried both versions, none worked.
Regards!

PM some kernel developers
Sent from my GT-I9000 using XDA Premium App

Use speedmod kernel patches with the readme file he has given..
or else you can go through supercurio threads also ...
they explained the kernel compilation methods....
thanks

Did you get this to work finally? I too am trying to compile and flash a custom kernel ( For SGS4G) I point my INIIRAMFS_SOURCE to an extracted initram dir, but the resulting boot zImage does not proceed past the initial boot screen(s) Please let me know if you succeeded, and if yes, how.
Thanks!

What I got the problem was about initramfs.cpio.
At that moment , the most important point you know is you should make the file in Linux..
When my friend made me a file is initramfs.cpio , it worked well.
But what I made in window made always troubles for compile.
So if you made a initramfs.cpio with hexeditor in window, try it in Linux again..
Thx!

[Discontinued]Miui port

Hello!
Ok so this is an attempt to port MIUI to LGP500. We are trying this because porting on the Galaxy 3 (LDPI armv6) was a success and i'm sure it will work on our device too.
This is what we're using so far: MIUI for Desire & Overflow ROM
So far this has been done:
ADB now working
Merged framework.jar from base rom with MIUI one
Replaced all apks with miui except LatinIME.apk which seems to give an error on boot
Use libs, bin and xbin from base rom
Merged permissions
[Update 9.07.2011 - 17:48 GMT+3 DST]
Now using framework from CM7
Libs, and bins from CM7
Boot.img still from Overflow (CM7 Boot.img stops adb on boot after a while - so using Overflow for developing for now)
Replaced many smali files in framework but errors keep popping up - I think framework is pretty screwed up now and must be redone (again)
No more nasty error on boot (with stack dump and stuff...)
No need for logcat now because errors come from framework
[Update 11.07.2011 - 15:32 GMT+3 DST]
MIUI boots up and we have graphics BUT
It only boots up to some error dialogs that say some processes force closed with "Close" and "Report to MIUI"
Gapps, Provision, and StatusBar force close so they need work
Removed ContactsProvider.apk and CalendarProvider.apk
[Update 14.07.2011 - 10:58 GMT+3 DST]
Fixed framework.jar - no more errors seem to come from it
New zip not made on mac so no low memory errors
New problem that might fix the apps: All apps look for their classes.dex in /cache/dalvik-cache but only system classes are there. The app classes are created in /data/cache/dalvik-cache
All apps are back because the errors don't come from them
[Update 28.07.2011 - 18:53 GMT+3 DST]
Added dalvik-cache to /cache script
New zip with init.d script and updated framework
Need to fix dead code in framework
Need new kernel
Need MDPI apks
Need libs that don't make the apks crash
Latest flashable zip:
http://www.multiupload.com/VNM8QTDBZ3 [Updated 28.07.2011] Thank you 4silvertooth
(DOES NOT BOOT! DON'T FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!) Sorry... i had to put this in big red letters because apparently people didn't see it well...
If you would like to help go ahead. Download the rom or make your own one if you don't like our development and give input. But most of all don't try to bring us down with "this can't be done" stuff. It can be done and it was done for another armv6 device. We need to get apps and framework to work and rom to boot. Libs and bins will come after...
This being said i would like to thank these people for their work so far and for making me get off my ass and do something useful:
4silvertooth
jazux
DJoptimus-One
Also i would like to thank overflow for his rom. It's the base for our miui so far.

Fantastic news! I can't wait too see how this works out. Good luck, you're gonna need it!

look forward to.

Thanks popdog
Will get into works as soon as i get my laptop back

Great news!
Waiting for testing release!

wow ! MIUI for o1 ?
oh sh*t this is what i've been waiting for so long !

looks good ill be happy to help, just ask for now im looking the motorola dump... maybe theres something that will help my team on galaxy 3 but anyway i subscribed tol this thread
EDIT: damn that motorola dump is useful, already found many, many tweaks thanks a million times for 4silvertooth

Hey can we use pastebin.com for all the logs.. it will be convenient and easy.
Sent from my LG-P500 using XDA Premium App

good point... also do you know a way to upload the files like in a git source (only the ones that changed) because multiuplad is painfully slow for me...

popdog123 said:
good point... also do you know a way to upload the files like in a git source (only the ones that changed) because multiuplad is painfully slow for me...
Click to expand...
Click to collapse
No but make a base rom and update.zip which will have all changes and will be small in size.
Sent from my LG-P500 using XDA Premium App

About the log.
The error so.lcddensity(something) is in build.prop you have to add it, it's using 160 by default.
All the missing class will have to be taken from the decompiled framework.
Sent from my LG-P500 using XDA Premium App

I'm redoing framework.jar... See what i missed... Then i'll get to build.prop
Also using boot.img from mik's cm port now

Breaking news of the day! I'll one of the first tester Keep going, heroes!

popdog123 said:
I'm redoing framework.jar... See what i missed... Then i'll get to build.prop
Also using boot.img from mik's cm port now
Click to expand...
Click to collapse
Will have to replace some smali. Merge the missing wont do.
@jazuk which one mainly.
Sent from my LG-P500 using XDA Premium App

Great news!

4silvertooth said:
No but make a base rom and update.zip which will have all changes and will be small in size.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
+1 for this, it would be easier to download for people with a slow connection like me.

ok ok... will do that... but for now we have to make a good base to start off of...

4silvertooth said:
Will have to replace some smali. Merge the missing wont do.
@jazuk which one mainly.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Whaaat???

Nice to see another dev porting some other firmwares to our phone if you want help then I'm in
Sent from my LG Optimus One P500 using XDA Premium App

jazux said:
Whaaat???
Click to expand...
Click to collapse
Never mind back to that later.
Sent from my LG-P500 using XDA Premium App

[ROM][Unofficial]SlimBean - The Menu Returns [build.2.1] [5-Nov-13]

Here's presenting stock Slimbean ROM with just 2 commits reverted which prevented users from adding the big menu button to navigation bar and SlimPie. Besides this, this is pure Slimbean without any modification whatsoever. I'm not a developer, in fact I learnt to install linux because I wanted the menu button so bad. I thought maybe I should share this with similar minded people. I'm going to upload updates as and when Slim team releases 4.3 updates as I'm not sure about the changes that would be made in 4.4. I won't be able to take any request as I am totally unaware of how to make any modifications, cherry picks or anything else. Hope you enjoy this ROM.
Code:
Disclaimer: We are not responsible for any damages on your device.
Original Slim Features:
The Real Dark Slim
SlimPIE
Notification drawer Shortcuts
Full hardware key rebinding!
Keyboard rotation
SlimCenter, SlimIRC and much more
Full feature list and changelog can be found on Slimroms website.
Installation instructions
For most users
Please keep in mind if a special instruction is needed it will be noted in the changelog.
Download the latest build from
Addons
!Recommended! Full wipe, and manual format /system
Flash ROM and the addons you want, reboot
Source
This ROM and kernel uses stock Slimbean code, which again can be accessed through Slimroms website.
Credits:
mar5hal
Nebucatnetzer [Slimroms forum]
NeB [Slimroms forum]
kufikugel
Entire Slimroms team for the source code.
Slim team has done an excellent job, please consider donating them.
Download Link:
http://d-h.st/DDf
[If you want to make a mirror, please contact me to update the OP]

Reserved...

another one... just in case...

@gururoop thank you so much for this, the one main thing missing from slim, Menu Button. In theory there shouldn't be any issues since its only 2 extra commits. Downloading now :good:

Just some screens to confirm. Everything is running smooth, no issues whatsoever
Sent from my Nexus 4 using XDA Premium 4 mobile app

Great, thanks a lot
edit: glad to have the menu button back.
However, I think it's better if you just make a small patch instead of rebuild the whole rom.

dark_ente said:
However, I think it's better if you just make a small patch instead of rebuild the whole rom.
Click to expand...
Click to collapse
That would be great, indeed. :good:

dark_ente said:
Great, thanks a lot
edit: glad to have the menu button back.
However, I think it's better if you just make a small patch instead of rebuild the whole rom.
Click to expand...
Click to collapse
finistere said:
That would be great, indeed. :good:
Click to expand...
Click to collapse
i wish i knew how to do that, but if you guys know how to, please guide me and i'll do it...
anyway, just compiled a new build so uploaded it here... OP updated with new link... enjoy...

gururoop said:
i wish i knew how to do that, but if you guys know how to, please guide me and i'll do it...
anyway, just compiled a new build so uploaded it here... OP updated with new link... enjoy...
Click to expand...
Click to collapse
Changelog what is changed?

The new official one has the statusbar mods now. Hate to leave it for the menu key but I might. Thanks for the build.
Sent from my Nexus 4 using Tapatalk

smartymcfly said:
Changelog what is changed?
Click to expand...
Click to collapse
No changelog... Just wanted to check how long does it take to compile in a virtualbox so synced the latest code and compiled...
Sent from my Nexus 4 using xda premium

scottx . said:
The new official one has the statusbar mods now. Hate to leave it for the menu key but I might. Thanks for the build.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
What statusbar mods are you talking about? This build is pure stock with just 2 reverts which enable us to add the menu button, apart from that no other change. The latest build was synced on 5th November, so maybe the statusbar mods were added later.
Sent from my Nexus 4 using xda premium

gururoop said:
i wish i knew how to do that, but if you guys know how to, please guide me and i'll do it...
anyway, just compiled a new build so uploaded it here... OP updated with new link... enjoy...
Click to expand...
Click to collapse
Please correct me if I'm wrong.
I guess you revert the change in framework-res.
In that case, you just need to create an update.zip which replace the old framework-res with your framework-res, and user only need to flash that file instead of the whole ROM.

dark_ente said:
Please correct me if I'm wrong.
I guess you revert the change in framework-res.
In that case, you just need to create an update.zip which replace the old framework-res with your framework-res, and user only need to flash that file instead of the whole ROM.
Click to expand...
Click to collapse
i revert the following 2 commits to achive the desired change:
5dd205257a8cfba3278ddb4ffbdd1897b1feaed7-packages/apps/Settings
8108afc56d15553c1d4abc83c9e9e27ac5b7cb36-framework/base
don't know exactly how many files or what else changes due to that. If you could figure that out, i'll be more than happy to help. and can u tell me whether there is any way i can compile some selected files instead of the whole rom?

gururoop said:
i revert the following 2 commits to achive the desired change:
5dd205257a8cfba3278ddb4ffbdd1897b1feaed7-packages/apps/Settings
8108afc56d15553c1d4abc83c9e9e27ac5b7cb36-framework/base
don't know exactly how many files or what else changes due to that. If you could figure that out, i'll be more than happy to help. and can u tell me whether there is any way i can compile some selected files instead of the whole rom?
Click to expand...
Click to collapse
What I mean is you still compile the rom, but only make a flashable zip of these two files and put it here. It would be easier for both you and me.
From the commit, I guess the two files are settings.apk and framework-res
Sent from my Nexus 4 using Tapatalk 2

dark_ente said:
What I mean is you still compile the rom, but only make a flashable zip of these two files and put it here. It would be easier for both you and me.
From the commit, I guess the two files are settings.apk and framework-res
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
now its getting too embarassing for me, but do you have any easy guide to help me create a flashable zip for these two files??

gururoop said:
now its getting too embarassing for me, but do you have any easy guide to help me create a flashable zip for these two files??
Click to expand...
Click to collapse
No problem mate.
The easiest way is to extract your rom to a new folder, delete boot.img, go to system folder and delete everything except the two files you want to keep. (you must also keep the folder structure). Inside these 2 folders are only files you want to copy (in this case settings.apk and framework-res)
Then go to META-INF\com\google\android\ folder and use notepad to edit the updater-script file like this
After that, you can compress them as simple zip and flash via twrp.
Next time you can just replace 2 files, compress again. No need to edit updater-script
Sent from my Nexus 4 using Tapatalk 2

dark_ente said:
No problem mate.
The easiest way is to extract your rom to a new folder, delete boot.img, go to system folder and delete everything except the two files you want to keep. (you must also keep the folder structure). Inside these 2 folders are only files you want to copy (in this case settings.apk and framework-res)
Then go to META-INF\com\google\android\ folder and use notepad to edit the updater-script file like this
After that, you can compress them as simple zip and flash via twrp.
Next time you can just replace 2 files, compress again. No need to edit updater-script
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So what you are saying is that if someone or I can just extract those 2 apks and add to a flashable zip I have lying round and menu button will be added to normal slim?

Would have been quicker!!
Sent by mobile telephone.

^^^^LOL I agree... Sidenote its funny how many people can creates so much goodness with building or modding files but dont know how to create flashable zips... LOL
dont re-invent the wheel I believe just get a gapps zip and mod away...
OH yea my bad thanks for the rom I too am a big fan of the menu and choose to live with it

[10-06-2014][ROM][DISCONTINUED] UnityROM-2 v.2.5.0 [CM-11][Optimized]

UnityROM-2 v.2.5.0
*****Discontinued.... No way to test actively till I have a functional build.*****
HTC One M7 Sprint Edition ( m7spr )
​

Development Section...
Want to contribute to the project or become team member?
Contact Me by PM here or leave a post detailing what you can and are willing to do for the projects' advancement.
My Github: https://github.com/LiquidSmokeX64
All current project sources can be found there .
ALSO MY FOOL-PROOF BUILD GUIDE & SCRIPTS ARE THERE FOR THOSE TOO IMPATIENT TO WAIT FOR MY NEXT RELEASE .
**Sources current as of version 2.5.0**
**10/06/2014**
Direct link to guide:
https://github.com/LiquidSmokeX64/Guides-Scripts
Note: Noob Friendly. If you're new to building ROMs or have never done it at all. I will help for as long as you maintain civility and focus on the project goals.​

Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.

gruesomewolf said:
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
Click to expand...
Click to collapse
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.

LiquidSmokeX64 said:
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
Click to expand...
Click to collapse
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...

gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8

gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here

LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Notorious said:
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
Click to expand...
Click to collapse
Umm....no I dont have any plans for that ATM

gruesomewolf said:
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Umm....no I dont have any plans for that ATM
Click to expand...
Click to collapse
Was joking lol

Notorious said:
Was joking lol
Click to expand...
Click to collapse
So you're allowing the integration of it? Just to be clear.

So I'm not sure why but the kernel borked again. Maybe I need to go through one flag at a time? Or maybe forgot something....?

gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.

LiquidSmokeX64 said:
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
Click to expand...
Click to collapse
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.

gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
I'm not seeing errors. Hell I removed everything but the -O3 spots and it still refused to boot. I dont know what the deal is....
Anytim I do ANYTHING to the kernel its dead, no matter how stupid it is.

gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
BTW. The makefile is borked. And was curious if you knew how to build AOSP for this device? CM was pretty easy, I'd figure AOSP isn't too different. Then I can try to get Android L running once I have a working Android K to cross-reference to and make the version specific changes in device, kernel, vendor, qcom-common, and s4-common

LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk

thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices

thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
gruesomewolf said:
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
Click to expand...
Click to collapse
I read this and my eyes glaze over. But you are in good hands with these two helping you. :highfive:

Yeah I'm working on it guys. Read the integrated kernel building guide and trying that. But if I could just get it to build me the boot.IMG and get my ramdisk sizes and whatever I'm looking at where to edit it in the device/BoardConfig changed the defconfig to a custom one I made based off the original one from the working boot.IMG but changed the I/O scheduler & CPU governed defaults. Gave it a local name (UnityKernel-x.x.x) and am fighting its last issues. So if nothing else help building it independently might be the most useful now. So if nothing else I can push a new boot.img

My bad. It just says the boot partition size so I think I might be almost there