can you make your own version of android ?

[givingtnt]

is that possible ? I mean. in a useful / easy way ? to create your own android skin and make animations for it, tools and utilities ? in a somewhat easy fashion ? 

also. please don'T just come here and dump a senseless ''why'' . if you need to ask you are in no help to me.

[_ASSASSIN_]

learning to compile from source is one thing. This is more of the lines of building a ROM with aesthetic changes.

To answer your question:

Yes you can do it

but

It requires some knowledge on your end.

[givingtnt]

learning to compile from source is one thing. This is more of the lines of building a ROM with aesthetic changes.

To answer your question:

Yes you can do it

but

It requires some knowledge on your end.

ik a bit of programming allredy. and I got the whole summer. what do I need ?

[_ASSASSIN_]

ik a bit of programming allredy. and I got the whole summer. what do I need ?

to build it

1. you need a linux or unix machine (mac OSX or BSD distribution) with a good CPU and preferably an SSD to not have a bottleneck in the sync process.

2. knowledge with github

3. knowledge of java and C (C isn't really needed that bad)

To be honest though, most of the changes you can just cherry pick from another team's gerrit. It's a bad practice but you can create a ROM with the kinds of changes you want just by doing that.

Just look at blisspop.

[Aniallation]

Of course, this is what ROM makers do.

[Aniallation]

To be honest though, most of the changes you can just cherry pick from another team's gerrit. It's a bad practice but you can create a ROM with the kinds of changes you want just by doing that.

Just look at blisspop.

aka kang, for personal use it's perfectly fine as long as you don't publicly distribute without the permission of the people in which you cherry picked from

[givingtnt]

to build it

1. you need a linux or unix (mac OSX or BSD distribution)

2. knowledge with github

3. knowledge of java and C (C isn't really needed that bad)

To be honest though, most of the changes you can just cherry pick from another team's gerrit. It's a bad practice but you can create a ROM with the kinds of changes you want just by doing that.

Just look at blisspop.

is there some kind of code it and see it instantaniously program ? also. why would I need linux or unix to edit code text ? I can just emulate linux. but still ?

[_ASSASSIN_]

is there some kind of code it and see it instantaniously program ? also. why would I need linux or unix to edit code text ? I can just emulate linux. but still ?

basically, you are going to have to push a commit, build it, and test it out. AFAIK adding features like this can't just be emulated.

I also just want to add that this gets much worse when you have to deal with proprietary blobs and getting a kernel source for this all to work.

Not a good "baby's first program" project.

[givingtnt]

basically, you are going to have to push a commit, build it, and test it out. AFAIK adding features like this can't just be emulated.

I also just want to add that this gets much worse when you have to deal with proprietary blobs and getting a kernel source for this all to work.

Not a good "baby's first program" project.

so each time I change something. I have to re compile it and put it in my device ? hm. ok

 

 

I basicly want to take lollypop 5.1, reskin it a bit, and remove some useless junk as well as adding some features I want.

[_ASSASSIN_]

so each time I change something. I have to re compile it and put it in my device ? hm. ok

 

 

I basicly want to take lollypop 5.1, reskin it a bit, and remove some useless junk as well as adding some features I want.

I'd recommend looking into a custom ROM if you want a product than building it yourself.

A one man ROM project is not for the meager of hearts.

[dfsdfgfkjsefoiqzemnd]

A one man ROM project is not for the meager of hearts.

As someone who completely ripped apart HTC's original Froyo ROM and removed all just about all non-esential things (because the original Desire had so little internal space), I can testify to that.

Removing bloatware can be as easy as deleting the apk file and recompiling the ROM, but once you go deeper it is REALLY hard and you need to be extremely careful when other stuff links to what you just deleted.

For instance I deleted HTC's default live wallpaper because it took up too much space (if you only have 113MB left on a clean default install, every 100KB counts). No big deal you'd think, but the default theme used that wallpaper and even after referring to a different one in more than a dozen files, there was always a link left somewhere, causing it to force-quit the OS itself every time it was about to load the homescreen, basically sending it into a boot loop of sorts.

Took me half a year and I ended up buying a second Desire so I had a working phone while I was messing around with the other one, but I wanted to keep a default-based ROM with Sense and there were no ROMS out there that did that.

By the time I was done they had released the Desire S, which was basically a Desire with better styling and much more internal space.  :angry:

 

So yeah, only go down that road if you know what you're doing and don't give a damn about your social life.  You'll probably be alienating yourself from family and friends because you're always trying to find out where you messed up the code this time.

[givingtnt]

As someone who completely ripped apart HTC's original Froyo ROM and removed all just about all non-esential things (because the original Desire had so little internal space), I can testify to that.

Removing bloatware can be as easy as deleting the apk file and recompiling the ROM, but once you go deeper it is REALLY hard and you need to be extremely careful when other stuff links to what you just deleted.

For instance I deleted HTC's default live wallpaper because it took up too much space (if you only have 113MB left on a clean default install, every 100KB counts). No big deal you'd think, but the default theme used that wallpaper and even after referring to a different one in more than a dozen files, there was always a link left somewhere, causing it to force-quit the OS itself every time it was about to load the homescreen, basically sending it into a boot loop of sorts.

Took me half a year and I ended up buying a second Desire so I had a working phone while I was messing around with the other one, but I wanted to keep a default-based ROM with Sense and there were no ROMS out there that did that.

By the time I was done they had released the Desire S, which was basically a Desire with better styling and much more internal space.  :angry:

 

So yeah, only go down that road if you know what you're doing and don't give a damn about your social life.  You'll probably be alienating yourself from family and friends because you're always trying to find out where you messed up the code this time.

lol ok. well I allredy don't really care bout social life, well at least, for the time im leaving this summer. I allredy have a few other projects to work on overthere. that will probably a ''just for fun'' kind of thing. 

[_ASSASSIN_]

lol ok. well I allredy don't really care bout social life, well at least, for the time im leaving this summer. I allredy have a few other projects to work on overthere. that will probably a ''just for fun'' kind of thing. 

his story was probably more difficult because sense is closed-source. AOSP should be easier, but it's still indepth..