Related
i just want to know why aosp roms are hard to develop for a phone like this one. the official samsung developers start with the aosp then build tw on top of it right?? is it not as easy as stripping touch wiz and the bloat ware than run what you have left.
NO I'M NOT A DEV BASHER I APPRECIATE ALL YOU GUYS DO I JUST DON'T UNDERSTAND PROGRAMMING SO I'M SORRY IF I OFFEND ANYONE.
It is not as easy as you think .....imagine you having windows and having to make your own drivers for all the components .....tw is built into android and symlinked all over when you remove things you have to remove what it was going to do in a way . They are not close to being the same. It is also very hard to get things working the right way and not just throw something together ... if its not fixed right it will break other things in different phones ... CM is on over 50 different devices
Sent from my SPH-D710 using xda premium
ah ok thanks. def far beyond this guys hands :/ thanks devs
Actually most elements of TouchWiz can be replaced with AOSP versions as it isn't as much integrated as Sense is on HTC phones.
I just want to add one thing or question to this. Why is it so hard to get the Bluetooth straight so you can use a wiimote and other bluetooth devices? That is really the only thing I wanted to ever use AOSP for. I would gladly donate to whoever corrects that.
There are both cm and miui roms for this phone. People just choose not to use them because aosp Wimax drivers are hard to come by.
Sent from my SPH-D710 using Tapatalk
Usually aosp roms are compiled from source, and the stock roms use a lot of proprietary libraries that need to be put into an aosp rom manually. Some may have compatibility issues, etc.
Sent from my SPH-D710 using Tapatalk
Also when Samsung orders parts for there phone such as chipsets radios and other parts. They get support from the manufacturers of the various parts and arm and maybe support from Google with also support documents to go along with them and they have an army of developers
Sent from my SPH-D710 using XDA App
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
Hello.
I have a kernel based on CAF's jb_2.5 branch booting on d2spr.
Source is here.
Status currently is: userland comes up (working panel) and seems to be functioning properly, with the caveat that pretty much all peripherals are broken. USB also works - so this project really is a developer's dream: plethora of mini problems to work on and a wealth of debugging information readily available.
Up until this point, I could focus on specific problems with the boot process and tackle them one by one. However now, there are dozens of directions one could go in, so I am posting this with the hopes of soliciting some help from like-minded individuals with experience in kernel porting. Work is also picking up for me, and I really need to offload some of this kernel work. Plus, I am burning a hole through my boot partition flashing/re-flashing, and it really is no fun doing this alone.
A bit of background: I used CAF's jb_2.5 branch because it is closest to being compatible with the userland HAL (display-caf in particular) currently used in cm10.1. I also have CAF's msm-3.4 branch booting, but the panel headers in userland are too far apart.
I tried to be surgical with the alterations: rather than mass merges, I tried to insert drivers individually (with the exception of media/video where samsung seems to have done an amazing job of crapping all over qcom's already non-upstreamed v4l2/camera/media code). The upshot of this is, we get rid of all the extraneous samsung crap. The downside is things are harder to fix.
The priorities as I see them:
1. Get d2vzw, d2tmo, d2att (etc) off the ground. Currently I only have board files for d2spr since this is the device I own, but someone with the right device and skill set should be able to invest couple of hours to follow my commits and get their version up.
2. Sound.
3. WiFi/Bluetooth. (invisiblek)
4. Camera
So let's get this going.
I wish we could put an effort to make this happen on Midas...
But really this is the wrong forum, the Qualcomm devices are truly on a completely different platform, there is little to no shared code here. Anyway good luck with it...
This honestly belongs in one of three places.
I am very interested in this work though.
http://forum.xda-developers.com/forumdisplay.php?f=1672
http://forum.xda-developers.com/forumdisplay.php?f=1692
http://forum.xda-developers.com/forumdisplay.php?f=1712
It's not really in the wrong section (currently): the US variants of the SGS3 share this "development discussion" section with the exynos versions. If a different dev discussion is created for the qualcomm devices, this thread will probably be moved there.
Take care
Gary
Audio is up and going.
You know you want in on this.
moving along well
wifi and bluetooth now too (bluetooth is just as ****ty as it was before)
as far as i can tell, the two big things left are:
-shutdown/reboot sequence is borked
-data
EDIT: oh, camera too
Can you please discuss development, as opposed to just give status updates on a project? (Otherwise, I'll have to delete the thread.)
Some suggestions: Discuss HOW you got audio, bluetooth, wifi, etc working - perhaps with some code snippets or actual examples.
Thank you
Gary
garyd9 said:
Can you please discuss development, as opposed to just give status updates on a project? (Otherwise, I'll have to delete the thread.)
Some suggestions: Discuss HOW you got audio, bluetooth, wifi, etc working - perhaps with some code snippets or actual examples.
Thank you
Gary
Click to expand...
Click to collapse
Gary, I appreciate what you are trying to do here, but the commit log is readily available. It's not like folks are asking specific questions and they are left unanswered.
If someone wants to spur discussion on a particular part of any code that's been committed then I am game, but rehashing past efforts for the sake of generating content is wasting everyone's time.
You have the last word so do what you gotta do.
In the meantime we have all sensors going (prox/light/g-sensor), gps also works, device reboots properly, and now actually enters power collapse in suspend. Thanks to invisiblek, our wifi and BT drivers have been ported over from 3.0, + he's got d2_vzw up to speed.
Other than some (minor and not so minor) tweaks here and there, the major project that needs a champion is camera.
detule said:
Gary, I appreciate what you are trying to do here, but the commit log is readily available. It's not like folks are asking specific questions and they are left unanswered.
Click to expand...
Click to collapse
The issue is that this section is for development discussion. Currently, this thread is using it as a "status updates for a specific product" thread (and not discussing the process whatsoever.)
Perhaps "Sprint samsung galaxy S III -> General" would be a better place for this thread?
Take care
Gary
How's the progress on the camera coming along? Its pretty impressive that you got the 3.4 kernel this far already.
Sent from my SGH-T999 using Tapatalk 2
Oh wait, never mind I'll just check the progress on github.
Sent from my SGH-T999 using Tapatalk 2
Moved to sprint sgs3 general.
Take care
Gary
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Just an fyi, I saw Chad Goodman post a pure Google aosp jb Rom with a 3.4 kernel a couple of weeks ago where everything including camera worked, even html5
Obviously it wasn't here.
klin1344 said:
How's the progress on the camera coming along? Its pretty impressive that you got the 3.4 kernel this far already.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I had an aosp rom with 3.4 kernel and the camera working, plus audio, wifi, and bluetooth. This was almost 3 weeks ago. Sorry to burst the bubble. Thanks
Yes I approve bigwillyg
bigwillyg said:
Just an fyi, I saw Chad Goodman post a pure Google aosp jb Rom with a 3.4 kernel a couple of weeks ago where everything including camera worked, even html5
Obviously it wasn't here.
Click to expand...
Click to collapse
Get out of here dude! Hahah jk.
Sent from my SPH-L710 using Tapatalk 2
bigwillyg said:
Just an fyi, I saw Chad Goodman post a pure Google aosp jb Rom with a 3.4 kernel a couple of weeks ago where everything including camera worked, even html5
Obviously it wasn't here.
Click to expand...
Click to collapse
Isn't his beta ROM 3.4. I've ran that since he dropped it. Best aosp ROM out there.
Sent from my SPH-L710 using Xparent Blue Tapatalk 2
bigwillyg said:
Just an fyi, I saw Chad Goodman post a pure Google aosp jb Rom with a 3.4 kernel a couple of weeks ago where everything including camera worked, even html5
Obviously it wasn't here.
Click to expand...
Click to collapse
You should know better than to post things like the above without offering a source tree.
Mod please close this thread, it obviously does not belong here.
As a side note: Pretty disappointed with XDA here - this thread gets bounced from development (into general nonetheless), in favour of threads "how to compile CM10.1"? Close it, posts like the ones above are exactly what I was trying to avoid.
detule said:
You should know better than to post things like the above without offering a source tree.
Mod please close this thread, it obviously does not belong here.
As a side note: Pretty disappointed with XDA here - this thread gets bounced from development (into general nonetheless), in favour of threads "how to compile CM10.1"? Close it, posts like the ones above are exactly what I was trying to avoid.
Click to expand...
Click to collapse
Why are you getting upset ? Because someone else has already accomplished what the OP is trying to do. I've ran the Rom before so I can say that it ran great.
Sent from my SPH-L710 using Tapatalk 2
daniel4653 said:
Why are you getting upset ? Because someone else has already accomplished what the OP is trying to do. I've ran the Rom before so I can say that it ran great.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Then where's the kernel source?
Sent from my SGH-T999 using Tapatalk 2
daniel4653 said:
Why are you getting upset ? Because someone else has already accomplished what the OP is trying to do. I've ran the Rom before so I can say that it ran great.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
+1 I ran it also wish I still had it
Sent from my SPH-L710 using Tapatalk 2
---------- Post added at 07:51 PM ---------- Previous post was at 07:49 PM ----------
klin1344 said:
Then where's the kernel source?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Since kernel is not on XDA there's no need to show the kernel source.
Sent from my SPH-L710 using Tapatalk 2
Hi, I'm Jacob. And I don't know if this is in the correct section, but I do plan on developing apps mainly for the Galaxy S3, so hopefully I've chosen the section wisely...
Now that that's out of the way, I'd like to say that I'm very interested in Android Development. Unfortunately I have no coding knowlage at all. I would love to learn Java, C++, etc. Is there anybody who would be willing to take me under their wing and teach me some of this? Whether it's just simple stuff or not, I honestly don't care. I would just love to jump into creating insane root apps right now, but I have nowhere near the kind of knowlage that I need to even get started. I'm also interested in creating custom ROMs. (and or themes)
Anyways, my point is, I'd like help, and I want to know if there is anybody willing to.
jtkemp101010 said:
Hi, I'm Jacob. And I don't know if this is in the correct section, but I do plan on developing apps mainly for the Galaxy S3, so hopefully I've chosen the section wisely...
Now that that's out of the way, I'd like to say that I'm very interested in Android Development. Unfortunately I have no coding knowlage at all. I would love to learn Java, C++, etc. Is there anybody who would be willing to take me under their wing and teach me some of this? Whether it's just simple stuff or not, I honestly don't care. I would just love to jump into creating insane root apps right now, but I have nowhere near the kind of knowlage that I need to even get started. I'm also interested in creating custom ROMs. (and or themes)
Anyways, my point is, I'd like help, and I want to know if there is anybody willing to.
Click to expand...
Click to collapse
Good luck man. I've tried finding help to no avail. Programming and all this good stuff takes time and skill.... Very little time on people's hands these days....
Sent from my SPH-L710 using Tapatalk 2
If I can, I would recommend reading through "Java Methods A and AB" to learn java. Very well written and theres a pdf of it online if you search too.
Thats how I learned and other than that, its just putting lots of time into it. I research everything I come across that I'm not familiar with, and now apart from the things actually covered in that book, I know how to make nice GUI's, how to cryptographic encoders work, how to bundle resources with a runnable JAR, etc. You just have to be willing to put the time in to learn, but from there its easy
Also, if you come across it too early, I would suggest not messing with threading and concurrency until you have a good grasp of java
Sent from my PG06100
you can't jump directly into android programming ,first, learn java and you'll be better off . After you've acquired sufficient skills in basic java - developer.android.com can assist you furthers . Make no mistake this ain't cat walk and would take time and patience since you are starting from absolute zero . Moreover i don't think anybody would love to take you - 'under their wings' - you are on your own mostly unless you take up some real time courses/classes in real life
why fix it if it ain't broken ?
nikufellow said:
you can't jump directly into android programming ,first, learn java and you'll be better off . After you've acquired sufficient skills in basic java - developer.android.com can assist you furthers . Make no mistake this ain't cat walk and would take time and patience since you are starting from absolute zero . Moreover i don't think anybody would love to take you - 'under their wings' - you are on your own mostly unless you take up some real time courses/classes in real life
why fix it if it ain't broken ?
Click to expand...
Click to collapse
Thanks for the info. I am very willing to take classes IRL but I'm nothing but a middle school student. I'll do the best I can to find some way to learn these concepts. Hopefully you'll be seeing me around in the Developer's section sometime soon!
Hey jtkemp.
I'm a sophomore in high school and I've been trying to learn to program. Here's what advice I can give you. First get a basic understanding of java, then once you have that down go though the android programming libraries at android.devolper.com. Then after that I have been taking apps currently out there already and modifying them to get better at it. Stay in touch and maybe we can help reach other out, I've been hoping I could find someone that would even let me help with like some stupid stuff they didn't want to do but so far no one. Good luck! It's a lot of fun!
Sent from my SPH-L710 using Tapatalk 2
Here are some links to some free online classes you can take
http://rootzwiki.com/index.php?/topic/602-Free-online-programming/CS-courses-for-beginners
And yes for many reasons a ton of people on XDA don't like to or don't have the time to talk about development. Everyone wants to be "the man". It's all baby steps really and depending on what type of development you're interested in (custom ROMs, apps, kernels etc) It all takes time. The hardest part I've had is developing an app. I've used Tasker to make a few personal apps but am still working with eclipse, which I've been told is not all that great to begin with.
But it all depends on what your interests are. Wanna mod and theme? Check out apktool and how to reverse engineer apk's. Wanna make apps and ROMs? Set up a Linux distro (I use Ubuntu and Arch) and download the sdk, CM repo, and the Jdk. Most importantly, use Google. Every thing I posted and virtually any questions I've had have been solved with a search. May take a while but the info is out there (How to set up apktool SGS3, How to install Ubuntu, How to Build CM 10.1, etc)
Feel free to drop me a PM, I'm off until fall semester and have some time on my hands.
Sent from my SPH-L710 using Tapatalk 2
I use eclipse and find the environment a lot better than other IDE's. I've tried netbeans but went back to eclipse because for me eclipse is just more intuitive
Sent from my PG06100
I learned a lot of development knowledge from just hanging out in an irc with some real cool dudes, learned how to at least understand java and a little c from studying some stuff, I'd recommend the same. A lot of people don't wanna help you because they don't know how much you know. Try to get a development presense, make a theme or theme an app. Just your name out. Give some devs some logs! Make some friends, they'll help you when you get stuck but no one will hold your hand. Do you use Linux? Learn the Linux command line. Try making a kernel for it, whether it works or not is errelevant, just learn the process and get an idea of what all that entails.
In front of a live studio audiencr
fergie716 said:
Here are some links to some free online classes you can take
http://rootzwiki.com/index.php?/topic/602-Free-online-programming/CS-courses-for-beginners
And yes for many reasons a ton of people on XDA don't like to or don't have the time to talk about development. Everyone wants to be "the man". It's all baby steps really and depending on what type of development you're interested in (custom ROMs, apps, kernels etc) It all takes time. The hardest part I've had is developing an app. I've used Tasker to make a few personal apps but am still working with eclipse, which I've been told is not all that great to begin with.
But it all depends on what your interests are. Wanna mod and theme? Check out apktool and how to reverse engineer apk's. Wanna make apps and ROMs? Set up a Linux distro (I use Ubuntu and Arch) and download the sdk, CM repo, and the Jdk. Most importantly, use Google. Every thing I posted and virtually any questions I've had have been solved with a search. May take a while but the info is out there (How to set up apktool SGS3, How to install Ubuntu, How to Build CM 10.1, etc)
Feel free to drop me a PM, I'm off until fall semester and have some time on my hands.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
*chuckles* I use Ubuntu as my default operating system anyway.
Sent from my SPH-L710 using xda app-developers app
jtkemp101010 said:
*chuckles* I use Ubuntu as my default operating system anyway.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Check out xda-university too, I think that would be a great place to start
Sent from my PG06100
Try stuff besides Ubuntu too, lots of different distros with, I think, better performance. Ex: I use mint 11. I used sabayon for a while too.
In front of a live studio audience
Used Mint for a while. It seems like it might get up there with the popularity of Ubuntu. Although I think that Ubuntu is more visually appealing.
Sent from my SPH-L710 using xda app-developers app
jtkemp101010 said:
Used Mint for a while. It seems like it might get up there with the popularity of Ubuntu. Although I think that Ubuntu is more visually appealing.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yeah I know a lot of people that prefer Mint over Ubuntu....I have yet to try it myself as I'm very pleased with my setup right now...the Faience theme is nice
Sent from my PG06100
Thenewboston.com beginner java video tutorials helped get me through my java class. I find I learn visually very well. There are also android development tutorials on his site. Good luck!
Sent from my SPH-L710 using Tapatalk 2
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.