Can somebody englighten me why the aosp rom devs say that they write the code for their rom from zero and then as we can see all the aosp roms are almost 100% identical and even their bugs are identical? Wouldnt one expect these roms to have different bugs since the devs claim that they write their own code?
ROMs that are compiled from source just means they were compiled using Google's source code, that doesn't mean they don't integrate other people's work, or "cherry picking" as CM calls it. It comes down to why re-code something that's already been made? Most things have already been made, and the few that haven't are either too hard or there's not much interest.
I'm sure most devs do have their own tweaks and whatnot, but not everything in a ROM has been made by them and a lot of stuff is borrowed or shared.
From build.prop tweaks to smali edits, to even simple framework tweaks, this is what devs could be talking about, nothing cosmetic that can be seen or merely felt, but that doesn't mean it's not there.
A Google search will tell you what it takes and what it is to compile a ROM from source. That shoulld enlighten you to these mysteries.
Sent from my HTC Glacier using xda premium
Yeah but whenever they talki g about compiling from source instead of porting they sound likr showing off as if they invented the whole code themselves. To me they all seem the same, the only difference is the way they organize the order of the menus in the settings. One bug that is common for all aosp for example is alarm clock that has been there for months, or camera problems that existed in the past. I just wanted to make this clear cuz it seems like this compiled from aosp has become exageratted way of showing off and people new to android feel like wow omg what impressing things this or that dev has done, while in fact only very few devs are the ones that deserve the credit for first "inventing" smthing/"fixing" bug and the rest simple get it from their source tree.
romuloxiii said:
A Google search will tell you what it takes and what it is to compile a ROM from source. That shoulld enlighten you to these mysteries.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Iknow what it takes.
lazarat said:
Yeah but whenever they talki g about compiling from source instead of porting they sound likr showing off as if they invented the whole code themselves. To me they all seem the same, the only difference is the way they organize the order of the menus in the settings. One bug that is common for all aosp for example is alarm clock that has been there for months, or camera problems that existed in the past. I just wanted to make this clear cuz it seems like this compiled from aosp has become exageratted way of showing off and people new to android feel like wow omg what impressing things this or that dev has done, while in fact only very few devs are the ones that deserve the credit for first "inventing" smthing/"fixing" bug and the rest simple get it from their source tree.
Click to expand...
Click to collapse
Unfortunately, I do agree with what you're saying, but in a way, the devs aren't lying. Most devs do indeed compile from source instead of using someone's base.
This phone didn't get as many devs as I expected it to.
A lot of real amazing devs are on other devices, it would be great if we could get one or two devs in here. Now I'm not taking any credit away from our devs, but it's nice when devs have a team like Hawk and Roman, Team Whiskey, man I loved their ROMs, everything seems to progress faster and have a lot more options. Take CodenameAndroid for example, that's a team of devs.
theexel said:
Unfortunately, I do agree with what you're saying, but in a way, the devs aren't lying. Most devs do indeed compile from source instead of using someone's base.
This phone didn't get as many devs as I expected it to.
A lot of real amazing devs are on other devices, it would be great if we could get one or two devs in here. Now I'm not taking any credit away from our devs, but it's nice when devs have a team like Hawk and Roman, Team Whiskey, man I loved their ROMs, everything seems to progress faster and have a lot more options. Take CodenameAndroid for example, that's a team of devs.
Click to expand...
Click to collapse
Eh... time to get lg nexus maybe lol
While some may be trying to look good or appear smart or whatever like you're saying, I think the majority do not have these sort of intentions.
I can say that if I were to release a rom that I compiled from source, I would put that in the op. Not to brag or anything like that, but just to inform. If I used someone elses as a base, I would mention it just the same.
If I were to compile from source, but not tell people I did, how long would it take for someone to ask where the base is from? To me its just another info point for the rom, and personally, I like to know where a dev got their base.
Also, as I understand it, while the mods and tweaks may or may not be their own, they most likely implement their changes before compiling, so the source will be different than original. Of course the vast majority of code will not be written/invented by them. Its Android source code. Open Source!
Maybe ive got it completely wrong, but to me, its just never been a big deal. I honestly never even thought about it in this context until this thread. (I don't use aokp or cm very much, so maybe that's why)
I know that you are right about some people, i just dont think they are in a majority here. Just thought id share my thoughts! Not sayin anyone else who's posted here is wrong. Its just my opinion based on how I understand it.
Sent from my SGH-T999 using xda app-developers app
Related
I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
I for one is not counting on it, frankly...
No matter how beautifully you phrase things, WE GOT NOTHING YET.
Sent from my SGH-T989 using XDA App
[A virgin sacrifice] =
SO FREK'IN EXCITED!!!!!
thanks for the info bro looking forward to it
jessejames111981 said:
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
Click to expand...
Click to collapse
the thing is, many of those are KANGed as in not officially supported by CM team
of the few that officially are supported is Nexus S i9020 and SGS i9000
even the "classic" SGS2 i9100 is not fully supported by CM yet, there's more bugs than... well it's not usable as a daily driver
that was just before the end of last year
they might have improved it a bit by now
even the Nexus S version of CM9 is still very buggy, that's why i have the stock official ICS4 instead on my Nexus S
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
iwasblown said:
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I don't believe in idiots, can you make them all go away?
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Why this statement?
From a glaxay better than yours.
tl;dr
I am basing my entire post on the fact that Steve Kondik has our device and should theoretically be working on it.
Click to expand...
Click to collapse
Steve Kondik aka Mr. Cyanogen also works for Samsung. I am sure he gets ALL Samsung devices...
corwest said:
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Click to expand...
Click to collapse
It only takes 2 weeks to modify the stock rom or cm7/9.
Its the expectation that is built when people act like quantity is all that matters. There are basically only 2 people making roms; Samsung and CM team, everyone else just waits on these 2 so that they could tweak and modify one of those 2. The funniest part is that the use of the word "kanging" is thrown around among these other people.
housecat93 said:
I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
Click to expand...
Click to collapse
I'd like to believe, I really would. And I hope this does come to fruition. However, even if it doesn't, the few ROMS we do have are pretty good, and our phone still outperforms almost anything else available right now, so I'll still be happy.
I do have one request, though. Can we figure out a way to make CM based ROMS happen without a virgin sacrifice? There are so many other things in life that require those, that they are starting to become scarce
The fact that lots of other phones have alphas and repositories available to even make kangs does not fare well for our device.
Sent from my HTC_Amaze_4G using xda premium
guys chillax..slayher already has it booting..and that's news from december
good to know, thanks
Great phone, needs more dev time and hopefully that comes along with it when ics hits.
We got shafted early with the nexus release so close to the T989 and a dev that promised things but ran away.
New year brings new hope. Great respect for the devs that care about our phone.
Sent from my SGH-T989 using XDA App
Let's hope the mods don't ban what little devs we have left...
Sent from my HTC_Amaze_4G using xda premium
AznDud333 said:
guys chillax..slayher already has it booting..and that's news from december
Click to expand...
Click to collapse
I don't follow, what do you mean by booting?
synergeticink said:
I don't follow, what do you mean by booting?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Booting
I'm sorry to have to even ask this, but why does it feel like, recently many devs have been pulling down kangs of their work and in some cases outright ending development because of kangs. Did something happen recently, or is everyone just butt hurt because summer's over?
This is meant as an actual question not s gripe
Sent from my Galaxy Nexus using Tapatalk 2
I think its kinda like if I started another thread and copied the title of your thread but changed the words around and asked the same question word for word in the thread and then added 1 sentence about my day.
I really think devs get upset cause THIER hard work coding theming tweaking is poached and Frankensteined together with another devs work then labeled a ROM with a donate button...
Now I'm sure if the donate button was to the original devs PayPal the world would be a happier place!
Just my opinion...
Sent from my Galaxy Nexus using Tapatalk 2
Because the devs are not doing an easy job developing and do not request any kind of payment? I think that explains enough.
Kangers could just ask them to include some part of the devs mod to be included in their work and maybe, maybe, to some extent, the devs will allow it.
Sent from The Nexus phone
As far as am concerned all this software is open source so go crazy with kanging. If a Dev releases there source code why not. That is the spirit of aosp. As long as the original Dev is given credit and the kang developer doesn't try and pass it off as his own work I say go for it.
Sent from my Galaxy Nexus using Tapatalk 2
The problem seems to lie in some kangers not giving due credit and/or seeking to turn a profit from the work of others. It can be disheartening for someone who puts in hours of work coding to see others take their work, incorporate it into a bit and pieced rom and then ask for donations. It's not necessarily about having your work "stolen," but rather about its misappropriation, if that makes any sense.
It is an open source community, but common decency should still entail asking permission, giving credit where credit is due, and not shamelessly trying to make money off others' hard work.
I agree, I don't have a problem if a kanger had a donate button as long as a) the is significant changes from the original rom. Or b) a pledge to give the original Dev some support/donation towards there rom (I.e. Helping fix bugs. Submitting code to the whole AOSP branch etc.)
Sent from my Galaxy Nexus using Tapatalk 2
It takes away from their downloads. It's like if I downloaded a rom, changed a couple things and called it my own. If I spent as much time as these devs do and someone called it theirs I would be mad too
Sent from my Galaxy Nexus using Tapatalk 2
its actually simple...donate a certain percentage of the donation to the original dev..that way everyones happy...kangers will make kangs better and devs dont get hurt because they get a certain donation without much work..
ferozfero said:
its actually simple...donate a certain percentage of the donation to the original dev..that way everyones happy...kangers will make kangs better and devs dont get hurt because they get a certain donation without much work..
Click to expand...
Click to collapse
The last sentence confuses me. If devs aren't doing much work; what exactly are kangers kanging? I don't mean to be a prick but I think it's worth a thought.
Sent from my Galaxy Nexus using Tapatalk 2
Most devas take from CM anyways so I don't know what the big deal is.
Personally I think only devs who have their own git should be able to receive donations. If your free and willing to submit your work and expose your source code and what you have done, you should be free to except donations. WinZip wizards need not apply
As far as Kangs go, I think due credit should be enough
Disclaimer : app devs and themers are excluded OFC
Sent from my Galaxy Nexus using xda app-developers app
I have tried a few others, liquid, alien, atom etc and none just seem to add up. I hate to sound condescending and by no means disrespectful but im looking for some others to play with. Customizable, leds, softkeys, statusbars, are some of the features I use a lot.
ocman40 said:
I have tried a few others, liquid, alien, atom etc and none just seem to add up. I hate to sound condescending and by no means disrespectful but im looking for some others to play with. Customizable, leds, softkeys, statusbars, are some of the features I use a lot.
Click to expand...
Click to collapse
you havent tried rasbean jelly
ocman40 said:
I have tried a few others, liquid, alien, atom etc and none just seem to add up. I hate to sound condescending and by no means disrespectful but im looking for some others to play with. Customizable, leds, softkeys, statusbars, are some of the features I use a lot.
Click to expand...
Click to collapse
just search and try, dont create a thread that compares roms to eachother, this is just begging for trouble
Yea, don't want any drama just options that are similar. Thank you.
ocman40 said:
I have tried a few others, liquid, alien, atom etc and none just seem to add up. I hate to sound condescending and by no means disrespectful but im looking for some others to play with. Customizable, leds, softkeys, statusbars, are some of the features I use a lot.
Click to expand...
Click to collapse
CM10, duh. I've tried quite a few as well and ended up going back to CM10. Their new update service is pretty slick if you flash a lot. I stick with CM's own kernel because it was designed for his build. Cyanogen has obviously put forth the most work in building android out of any developer out there and this is why I trust his work more than others on here. Multiple people are responsible for changes to the code and review what is to be submitted and not submitted for a better overall experience/compatibility; not just some random Joe Schmo developer tinkering with code.
You can't argue that Cyanogen and his team are the best devs on here, no one here has come close to what he's done with his build system for all of the devices he builds for. He makes CM a simple extension to vanilla android and compliments it very well.
I didn't even like sorcery when I tried it..
paranoidandroid for me
"I don't mean to be condescending" and "don't want any drama" do not belong in a thread such as this. You were better off trying all of them, and not some of them (and thinking it was all of them) and making a decision for yourself..
akira02rex said:
CM10, duh. I've tried quite a few as well and ended up going back to CM10. Their new update service is pretty slick if you flash a lot. I stick with CM's own kernel because it was designed for his build. Cyanogen has obviously put forth the most work in building android out of any developer out there and this is why I trust his work more than others on here. Multiple people are responsible for changes to the code and review what is to be submitted and not submitted for a better overall experience/compatibility; not just some random Joe Schmo developer tinkering with code.
You can't argue that Cyanogen and his team are the best devs on here, no one here has come close to what he's done with his build system for all of the devices he builds for. He makes CM a simple extension to vanilla android and compliments it very well.
Click to expand...
Click to collapse
Sure you can, and that isn't fair. People have blinders on if they think only CM are the best. CM is a team of over a 100 devs. They have the manpower needed to do what they do. Nobody else does.
One of CM's recent features that they tried to play off as totally original (and many believe it), was in a rom a month prior, the commit provided by someone who has no such "dev" status.
There is talent everywhere. CM is not the answer to it all.
good roms are never supposed to be mentioned. just saying. silly
adrynalyne said:
"I don't mean to be condescending" and "don't want any drama" do not belong in a thread such as this. You were better off trying all of them, and not some of them (and thinking it was all of them) and making a decision for yourself..
Click to expand...
Click to collapse
What's up adr? Im still looking for rasbean to try. Never cared for the cm roms. Sorry if I offended ya.
ocman40 said:
What's up adr? Im still looking for rasbean to try. Never cared for the cm roms. Sorry if I offended ya.
Click to expand...
Click to collapse
I'm not offended. I just know you are opening a can of worms
A can of angry, soul-sucking, evil worms that will snuff your life if given the chance.
ocman40 said:
What's up adr? Im still looking for rasbean to try. Never cared for the cm roms. Sorry if I offended ya.
Click to expand...
Click to collapse
maguro or toro?
heres maguro http://fitsnugly.euroskank.com/?rom=rasbeanjelly&device=maguro
if you have a toro, press toro on the right side of the page. if you have a toro plus, UBER started a thread in the toro+ section. all the rasbean jelly rom support can be found in the trinity kernel thread http://forum.xda-developers.com/showthread.php?t=1455874&page=2267
No offense taken. I just think what CM has does is the cleanest solution to a custom build of android for mobile devices. And there's a reason they have so many developers on their team.. and don't forget Cyanogen himself.
adrynalyne said:
I'm not offended. I just know you are opening a can of worms
A can of angry, soul-sucking, evil worms that will snuff your life if given the chance.
Click to expand...
Click to collapse
Im 40 bro, those days are past for me lol. Just want some options. I just recently switched from my TB. Didn't you do some work on that? Your name seems familiar.
ocman40 said:
Im 40 bro, those days are past for me lol. Just want some options. I just recently switched from my TB. Didn't you do some work on that? Your name seems familiar.
Click to expand...
Click to collapse
he did... he's part of BAMF.
ocman40 said:
Im 40 bro, those days are past for me lol. Just want some options. I just recently switched from my TB. Didn't you do some work on that? Your name seems familiar.
Click to expand...
Click to collapse
Yeah, worked on the TB, and then switched to the Nexus when it came out last year.
akira02rex said:
CM10, duh. I've tried quite a few as well and ended up going back to CM10. Their new update service is pretty slick if you flash a lot. I stick with CM's own kernel because it was designed for his build. Cyanogen has obviously put forth the most work in building android out of any developer out there and this is why I trust his work more than others on here. Multiple people are responsible for changes to the code and review what is to be submitted and not submitted for a better overall experience/compatibility; not just some random Joe Schmo developer tinkering with code.
You can't argue that Cyanogen and his team are the best devs on here, no one here has come close to what he's done with his build system for all of the devices he builds for. He makes CM a simple extension to vanilla android and compliments it very well.
Click to expand...
Click to collapse
From the Roms I've tried (which is every single one) I've found that cm10 is one of the lower on the totem pole when it come to features. A great ROM yes super fast and super stable yes but as for features.... not so much.
Sent from my Galaxy Nexus using xda premium
vince7 said:
From the Roms I've tried (which is every single one) I've found that cm10 is one of the lower on the totem pole when it come to features. A great ROM yes super fast and super stable yes but as for features.... not so much.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You're talking minimal differences man. How many more features does AOKP have over CM10? It's not as many as you think if you list them all, and besides, the CM team has their own that AOKP doesn't have.
adrynalyne said:
Sure you can, and that isn't fair. People have blinders on if they think only CM are the best. CM is a team of over a 100 devs. They have the manpower needed to do what they do. Nobody else does.
One of CM's recent features that they tried to play off as totally original (and many believe it), was in a rom a month prior, the commit provided by someone who has no such "dev" status.
There is talent everywhere. CM is not the answer to it all.
Click to expand...
Click to collapse
What feature? I agree with you, it's not like Cyanogen, steve, whatever his name is, is doing the work for a few dozen devices. I just want to know what feature you're talking about?
Sorcery is nice but for me the performance wasn't there. Xenon HD seems to work best for me
Sent from my Galaxy Nexus using Tapatalk 2
Hi guys,
So for the past week I think I have at least wiped/flashed/Odin'd different ROMs for my new Captivate Glide at least a hundred times. I've finally settled on thegreatergood's LiteROM 0.9.0 and it's working great for me. Not only the one ROM though as I've had to find many workarounds for different things. Flashables/kernels/apks you name it. Although I have no regrets and I'm really proud of how It's like a beast in my pocket, I am quite bothered by one thing which is that the whole thing feels like a big piece of patchwork..
Coming from a HTC Desire Z running CM7 serving me loyally for many years, I miss that officiality (<-- oops, red snakes.. not sure that's a word. Whatever. Shakespeare made his own words too right? ) and the stability that CM7 offered.
I'm a humble man, and possibly carry the apologetic traits of a typical Canadian. Instead of whining and/or nagging some senior developer to hurry up on their ICS or JB development I've decided to build my own CM instead.
However some thought, I think the reason why the JB based experimental CM 10.1s for the Captivate Glide have been a difficult task is because it's probably quite a challenge to build something from something that's not currently very well understood, namely the JB. So I thought, why not just build I nice and stable ROM based off of GB and if it does well it could probably officiated as a CM7 port for the Captivate Glide.
I have a feeling that this is a very plausible task. But I have no way to do it alone.. I have zilch experience in development in anything, had to drop out of my C++ course and have been doing nothing but lurking and leeching since I started modding when I was eleven. All I have is a vision. If someone could point me in the right direction or even form a development team with me, I would be very grateful.
And if this goes well, I will have gained some long overdue experience
So.. Anyone?
P.S. I guess this goes in this forum too. But my phone gets real angry when I flash certain things onto it. The biggest issue currently is that it will freeze and crash (more specifically the screen will freeze and fade into white lines..) whenever I try to use ClockWorkMod Recovery.. I dunno if the crappy 1500 mAh China battery I got ripped off with is an issue but I'm waiting on an OEM one in the mail..
Post in general not development bub...
And were on cm 10. Why fall back?
Sent from my SGH-I927 using xda app-developers app
I intend to turn it into development thread. But will have a better audience over General?
And maybe see it more like an educational project with a usuable product?
Sent from my SGH-I927 using xda app-developers app
hey bud im with you ... though I think CM9 would be better as ICS has been released, stable, and has a few more tweaks and features that CM7 didn't ... things like in JB where we have a transparent notification pull down, control over the dpi of certain apps etc.
First thing you should do is readup on the compile cm10 from source thread, get your feet wet there it'll get you all setup with a development system .. Linux is a must so I hope that you're savvy in the *nix shell or things will be antagonistic right off the start ...
I installed the CM9 recently and radio etc didn't work .. Guaranteed there is tonnes of information across all devices on xda-developers and even in general development threads.
Scroll through these forums, find the github links and learn how to setup your own, download the sources for the kernels from the other devs (theres a couple CM10.1s out there).
CM7 .. while I appreciate where you're coming from as i LOVED having CM7 on my Galaxy ACE - everything just worked... battery was great, it looked cool, and it was just off the stock enough to be unique and rub in iPhone users' faces
If I had the time I'd take it on with you .. chart your work and links that have helped you as you go along.
maybe he say that, because the glide have GB and ics officialy and not JB, so, if i understand what he say, maybe a romCM based y that version can be more stable, and less bugs, i was thinking about a CM9 too. But, if i remember correctly, it must create a device tree and a lot of thing, but i am not sure becausea never do a rom.
lorddavid said:
maybe he say that, because the glide have GB and ics officialy and not JB, so, if i understand what he say, maybe a romCM based y that version can be more stable, and less bugs, i was thinking about a CM9 too. But, if i remember correctly, it must create a device tree and a lot of thing, but i am not sure becausea never do a rom.
Click to expand...
Click to collapse
CM9 is based on ICS 4.0.4 ...
Check this link, not for our device but it offers some good insight to CM7 : http://forum.xda-developers.com/showthread.php?t=1273718
Another one for CM9 : http://forum.xda-developers.com/showthread.php?p=20844007
.... maybe I should just build a linux VM and give it a go in my spare time .... we're so starved for developers for our glides even amateur contributions can't hurt .... in the 2nd link the guy said it took him 11 months to learn how to mod for ICS from no experience so ..... depends on how much you want to commit to it ..
yohan4ws said:
CM9 is based on ICS 4.0.4 ...
Check this link, not for our device but it offers some good insight : http://forum.xda-developers.com/showthread.php?t=1273718
Click to expand...
Click to collapse
yes, i know that, and i was thinking that a cm9 (because there is a ics fully working in the glide) can be a good option, but not sure
This doesn't belong here, please, some mod, move this to General. Thanks
chrisyjwai said:
I intend to turn it into development thread. But will have a better audience over General?
And maybe see it more like an educational project with a usuable product?
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Flagged to be moved to general. If this turns into a dev thread, then you can flag to move it to the dev section, but you only post in the dev sections if you actually have a product or are actively working on something.
Your intentions seem great, but never wait for someone else to help you, otherwise it will never get done. No one is going to carry you through learning this.
There's a ton of guides out there on how to build, port, cherry pick CM commits, etc. etc. Go find them and start learning. Ask SPECIFIC questions if you have any.
No one shows up to college on day 1 and says I'd like to learn how to be a doctor, engineer, pharmacist, journalist, etc. There's a lot of steps in between. So go and get started.
gtmaster303 said:
No one shows up to college on day 1 and says I'd like to learn how to be a doctor, engineer, pharmacist, journalist, etc.
Click to expand...
Click to collapse
That doesn't make any sense.... lots of people show up to college and say that, and then enroll in the courses to do that ..
When will we see a aosp rom for our note 3
Tomorrow when the clock strikes 12. I promise
Sent from my magic spaceship
When people stop asking for ETA's.
sent from my sm-9005.
Yerv Melkonian said:
When will we see a aosp rom for our note 3
Click to expand...
Click to collapse
When will we see people stop asking for aosp roms? Thats the real question, this phones barely a month old smh.
Sent from my note 2 ya bish!
d12unk13astard said:
When will we see people stop asking for aosp roms? Thats the real question, this phones barely a month old smh.
Sent from my note 2 ya bish!
Click to expand...
Click to collapse
We're just excited. Let us wag our tails and scratch at the door until our owner opens the door for us. So to speak. LOL!
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
dragonstalker said:
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
I would love to see that
Sent from my SM-N900T
Is there a Google edition or developer edition coming? Has that been confirmed anywhere? I too am really missing cm, aokp, pa, and especially pac man. Man, what I'd give for pac man on this beast! I REALLY hope we get some aosp love.
Sent from my SM-N900T using Tapatalk
dragonstalker said:
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
You sir have just explained the reason I fell in love with android, aosp, the rooting community. A lot of people don't get and are unappreciative of the works of ROM devs. So much greed and selfishness I've seen on xda since after the g1 days. Its always *****ing and bickering and this and that and demanding. Thank you to all the devs out there. Without you guys, android will be a Disney Land that never opened its gates
Sent from my SM-N900T using xda app-developers app
pathtologos said:
Is there a Google edition or developer edition coming? Has that been confirmed anywhere? I too am really missing cm, aokp, pa, and especially pac man. Man, what I'd give for pac man on this beast! I REALLY hope we get some aosp love.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
+24
CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
Why would you quote me and say exactly what i said in a long drawn out explanation. I'm guessing you missed the punctuation in my response. I mean you said everything i said, down to how the CM is a work in progress. Sheesh.
CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
DUDE I couldn't have said it better myself. You devs are wizards.