Is it just me or does anybody else feel they are going through withdraws from the lack of updated roms lately... Especially after the kernel was released.
I know all the chefs are cooking up some real magic (like the gumbo kernel, which is awesome) and its going to be fun to see what they come up with next. Thanks again to all the chefs for all you guys do. You are all truly amazing...
a lot of the dev are working on other things flipz for example is is working on getting his kitchen from pre to full realese and a lot of the others are working on porting to .29 so that we can get the 2.1 roms fully functioning.
a few of us are devoting most if not all of our time to porting the kernel htc released into the 2.6.29 kernel so we can hopefully get fully working 1.6, 2.0.1 and/or 2.1 android builds. After that the rom flood will begin again. I've got a half finished rom I was working on but I'm waiting until I can get 2.1 fully functioning without having to hack android into thinking it has the right kernel.
Honestly I've barely scratched the surface with my attempts at porting the kernel to a newer version and my eyes are spinning, my programming experience is more at the beginner level though, hopefully some of the other devs are having better luck than I am.
I know this device hasn't been officially released yet, but we do have the source code from Samsung and Froyo source code from Google. I was thinking about starting up a dev team to start cooking up ROMS for the Vibrant if you are interested send me a pm on here, and we can get things started. I'll admit I am a little rusty on my Java, but it shouldn't take me no time to learn it again.
May be jumping the shark a little. Has anyone found a consistant way to gain root?
Not yet, but on the 15th, I'll be working on it when I get the phone
Excellent start I have the nexus one as my daily but I am ordering this phone on the 15th as well.
I will also have the phone on the 15th and if any help or testing is needed Ill be more than glad to help...
Alright cool, I am reviewing my Java, and I am coming from the Droid to this phone so this should be exciting to hopefully start up a small community of people to help me with cooking up ROMs for this phone
Is knowing Java the only requriement for being able to create your own custom roms? I'm learning it now in hopes to make my own apps, but I thought you needed to know C and be well-versed in linux stuff like kernel programming to be able to make your own custom roms.
Im in for the dev team =)........Im coming from the mytouch 3g
According to what I can find on source.android.com the only examples of code that they have on there are Java base
I am game. I dont have a boat load of time, but I am going to try to get CM6 built for this phone. I want Froyo ASAP. Also I would like to get CM6 on there with some of the other goodies that the phone has such as extra video codec playback. Anyway here is a link on how to build CM that can help jump start everyone.
http://wiki.cyanogenmod.com/index.php?title=Building_from_source
Edit: Java and depending on what you are doing C. The kernels do require heavy hacking if you want to really mess with it, but in most cases all you have to do is build it and link in the proper drivers.
Note: I have never done any of this it is just what I have gathered over the time of owning my G1 since launch day.
3g,4g FFC is it important?
My G1 is now fu-bar and t-mobile is replacing it with the moto click. I don't no if that is better or worst but it has more ram. Anyway I was not sure if not having a FFC or flash is important but it seems to me that whether the vibrant will handle the 4g speeds or not is. I so what a high end phone but I can't afford to buy one every 6 months. I hope that as people get the vibrant someone will be able to take a peak inside of it to see if maybe t-mobile has the FFC in it but just covered it up with a front case that hides it. Wouldn't that be something, ya right. So I'll wait for a while to see all the real reviews on the phone. Id hate to pay all that money just to find that in a few months or even next year t-mobile completes there so called 4g and I can't take advance of it. I don't no if the hspa + or what ever its called is just a matter of software updates or not. I don't really have a question just rambling.
I too am CHOMPING at the bit to get the Vibrant.
Going from Rooted CyanoGen6RC1 G1 Dream.
I'll be in for help testing proven root access, applications, and alternative ROMs from 0-Day.
Man I can't wait to be the envy of my entire IT team.
They can take their iPhone4s and stick em up their collective MacFag asses!
hey guys I'm down to join the dev team. I haven't done much Java since college (8 yrs back) but I program in C/C++ daily on my job. I haven't done the kernel stuff but I'm more than willing to learn that and brush up on my Java as well.
I'll be getting the phone on the 15th as well.
Thanks for all the interest in this phone. For those of you planning on building CM6 for this phone, that is where I was planning on starting.
Just to let everyone know that I will mainly be doing this after 4:30 P.M. PDT, and weekends since I am active duty marine corps, and stationed out here in California. My job in the Marines requires me to know how to do some of the coding necessary for this.
I was planning on starting up an IRC channel, probably tonight, and anyone that is interested can meet up there and we can talk about things. I will make a post here, android central, and probably the cyanogen forums when I get everything started.
I'm excited to be doing this, and again thanks for all the interest.
count me in for some basic programming, I'll help where I can, but between school and work idk how much that will be. I will definitely be getting my Vibrant on the 15th, and I have built froyo from source before just to see if I could get that setup no problem.
I have experience in c++ and java, so hopefully I'll be of some use. but kernel work is definitely new to me
Im game for a IRC channel. Let me know and Ill try to Idle when I can. I would be working on it late night EST time so we might jive.
Hmmm
If anyone needs testers pm me cause I am dying to get into deving for this phone. I don't know how to code or anything, but I do know basics. Owned a G1/MT3G/Cliq and hacked the hell out of all of them. Should be ordering my Vibrant right now with UPS 3 day. But seriously, I'd love to test once everyone gets their roms cooked up
its nice that Samsung is giving us source so quickly. I'm already in love with my Vibrant. I have plenty experience with kernel compilation and complete ROM cooking from source. We need a Vanilla ROM for this beast of a phone
justanothercrowd said:
its nice that Samsung is giving us source so quickly. I'm already in love with my Vibrant. I have plenty experience with kernel compilation and complete ROM cooking from source. We need a Vanilla ROM for this beast of a phone
Click to expand...
Click to collapse
Nice to see you back here. Haven't seen you aroound since the Drizzy days.
Not sure if I want to root yet or not. If I do I can do testing and help with kernel, little rusty with the kernel though.
had a g1 just got my vibrant this morning.
Sent from my SGH-T959 using XDA App
Hi,
I noticed that every time Cronos releases a rom Elelinux the next Day or hours has also a new rom. I thought this was just coincidence. But after checking his libraries and binaries it showed me that 85% or even more all have the same md5sum's as the latest Cronos rom?
I am a long time follower of XDA Hero developemt thread so I know what has been playing around for the last year. But I think its not fair of Elelinux to use all the work from Cronos without giving Credits!
Is this possible when building a rom that the md5sums are the same as another rom?
if no, why elelinux does not give credits to the orriginal builder?
he dates show that cronos always releases it first and then Elelinux.
Why does elelinux not get a ban for this as he is also breaking the xda rules, giving credits where du.
if this is not being taken care of then i think villain has have had no right at all with the all flame fight against cronos in the past..
if you were looking at the gps or I think it was the keypad lighting code then ele actually got that code running correctly, signed up to feeyos forum and gave it to Feeyo for him to get his build working.
Chances are feeyo has been helping back and fore but I wouldn't know about that.
You have to realise these are all built from cyanogenmod sources..They will have the same files.Feeyo doesnt build it all from SDK cyanogen rarely gets a mention nowadays for the sources supplied
Hello,
This was brought up in another thread that is now locked.This post asked the question.
http://forum.xda-developers.com/showpost.php?p=11287492&postcount=40
and this is the blog post by Cyanogen
http://www.cyanogenmod.com/home/a-note-on-unofficial-ports-and-how-to-get-it-right
From what I can make from the blog post that Cyanogen put up on the CM website the Epic 4g as well as the other Galaxy S CM ports are not backed by Cyanogen because they do not go through the normal chain of how they add their code into their source code tree.The Galaxy S CM github has many changes to the stock android code that could possible and probably does break the code from being compiled for other phones. The framework is modified to work with the Samsung RIL that our phones use. The CM team will make additions to the stock android code not modifiy the stock code itself. So from my understanding of thing this is why Cyanogen does not consider what the CMSGS team has done as a part of the mainline CM code base. I believe this goes for all the Galaxy S phones not just the Epic.
Does being backed by the CM team make it get done any quicker? If so....
Sent from my SPH-D700 using XDA App
Being backed by the Cm team would definitely speed up the porting process, Cyanogen had the Evo Release Client up and running in a little over a month without source
So its a matter of pulling the source together and prperly placing it into their source control so their build bot can properly dov what build bots do...build...then CM helps with the port process?
If I think I'm following that right...somone better start uploading code to Cyanogens t&c's(terms and conditions) so we can have some epic awesomesauce.
Sent from my SPH-D700 using XDA App
Most importantly, no major hardware functionality should be broken.
Click to expand...
Click to collapse
What this statement implies is that no Cyanogenmod port is ever gonna be official right away; there's always an in-progress period where major functions are broken. Regardless of other issues, that's where our Epic port is at right now and part of the reason why it's not official.
Poryhack said:
What this statement implies is that no Cyanogenmod port is ever gonna be official right away; there's always an in-progress period where major functions are broken. Regardless of other issues, that's where our Epic port is at right now and part of the reason why it's not official.
Click to expand...
Click to collapse
True but there is code that is changed in the Galaxy S port that doesn't get changed at all in other CM ports as far as I know.
If we had HTC Epic's instead of Samsung Epic's and still identical devices... CM would officially support the Epic.
Period. They can say whatever they want but we all know this to be the case. You can't tell me Samsung changes their code that much more then HTC... last I checked Sense was a much more in depth overall to the underlying OS then Touchwiz is.. but maybe not.
The thing is, HTC uses the same hardware across the board (snapdragon processors, same camera etc.) which makes Rom ports much much easier to pull off, whereas the Hummingbird in the Galaxy S is only in the Galaxy S and only the Unlocked Galaxies and Gsm have froyo source so far.
Thanks for osting this skeeter
Android Creative Syndicate- From spontaneous ingenuity, comes creative brilliance
063_XOBX said:
The thing is, HTC uses the same hardware across the board (snapdragon processors, same camera etc.) which makes Rom ports much much easier to pull off, whereas the Hummingbird in the Galaxy S is only in the Galaxy S and only the Unlocked Galaxies and Gsm have froyo source so far.
Click to expand...
Click to collapse
The changes in the code have nothing at all to do with the cpu its all for the radio which even having froyo source will not help a bit with.Its all in the way the code changes were done. Rather then adding to the base code in CM the code was directly changed which is what Cyanogen has an issue with doing so basically could and probably has broken the radio code for other cdma phones, I don't know what or if any of the code in the frameworks was changed for the gsm Galaxy S phones so I can't say for sure that it the source from the CMSGS github wouldn't work on another GSM phone I only know that changes were made to get it working on the Epic and Fascinate.I don't think what the CMSGS team did was wrong they did what they had to do to get things working and from the time I spent working on it it didn't seem like there was much input from the CM team at all but that was probably happening in another irc channel that I was not invited into if they were involved.I was hoping that the Galaxy S would have had more interest from the CM team as a whole I know a phone or two was collected and donated to at least one dev and i also heard that Koush was supposed to take over the Captivate port of CM I am not sure if that ever happened or not but the Epic and Fascinate were from the beginning the red headed step children of the Galaxy S line it really is too bad that there wasn't for developers around to help work on it and make an offical Cyanogen backed CM port.I blame it all on the Evo personally if the Epic came out first it would be the Epic sporting all the kernel and roms that you can find in the Evo forum instead we are left with a handful or less of devs and a phone that is far from the potential that it has.
This statement brings up one of my biggest questions I have for the epic forums that I have yet to understand. If a lack of devs are the biggest problem for the epic why is it they are not attempting to train anyone else. Here's my point. I have cataloged every bit (and still am) of info I know about themeing android and the samsung epic. I wrote guides breaking down every part of installing the tools necessary and using them so anyone just sitting down with a fresh windows and their first android phone would understand. Where are our dev guides besides "read developer.android.com". I've read it, I've set everything up. I've downloaded source, I've even ran make with success. But it does nothing without proprietary files. How do you plug them in. extract files.sh dont work without cm6 running on my phone. Where do we learn how to edit our build.prop, init.rc, compile drivers and modules. Joey krimm it's a great beginners source but what about updates since the stall between ubuntu 10 64 support, and 64 becoming the default. I feel like not only it's sammy and sprint at fault, but so are devs that arent open with their knowledge. The best gift this community could have gotten in all of this "down time"waiting was time spent learning. Devs stuck waiting on modems and source, start writing and teaching so when you get that source, you'll have a team behind you. That's the spirit of linux and it dont exist on xda's Samsung Epic Development section!
Sent from my SPH-D700 using Tapatalk
dreamsforgotten said:
This statement brings up one of my biggest questions I have for the epic forums that I have yet to understand. If a lack of devs are the biggest problem for the epic why is it they are not attempting to train anyone else. Here's my point. I have cataloged every bit (and still am) of info I know about themeing android and the samsung epic. I wrote guides breaking down every part of installing the tools necessary and using them so anyone just sitting down with a fresh windows and their first android phone would understand. Where are our dev guides besides "read developer.android.com". I've read it, I've set everything up. I've downloaded source, I've even ran make with success. But it does nothing without proprietary files. How do you plug them in. extract files.sh dont work without cm6 running on my phone. Where do we learn how to edit our build.prop, init.rc, compile drivers and modules. Joey krimm it's a great beginners source but what about updates since the stall between ubuntu 10 64 support, and 64 becoming the default. I feel like not only it's sammy and sprint at fault, but so are devs that arent open with their knowledge. The best gift this community could have gotten in all of this "down time"waiting was time spent learning. Devs stuck waiting on modems and source, start writing and teaching so when you get that source, you'll have a team behind you. That's the spirit of linux and it dont exist on xda's Samsung Epic Development section!
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Where's the thank spam? hah.
I've slowly been dipping myself into the Developer 'pool' for the epic if you will..and at first when I started working nobody really ever helped out..they just threw me a link and was like..start reading blah blah blah..
Reading only gets you so far; Imho you learn better when you've got the experience of working first hand with the material you're trying to learn.
dreamsforgotten said:
This statement brings up one of my biggest questions I have for the epic forums that I have yet to understand. If a lack of devs are the biggest problem for the epic why is it they are not attempting to train anyone else. Here's my point. I have cataloged every bit (and still am) of info I know about themeing android and the samsung epic. I wrote guides breaking down every part of installing the tools necessary and using them so anyone just sitting down with a fresh windows and their first android phone would understand. Where are our dev guides besides "read developer.android.com". I've read it, I've set everything up. I've downloaded source, I've even ran make with success. But it does nothing without proprietary files. How do you plug them in. extract files.sh dont work without cm6 running on my phone. Where do we learn how to edit our build.prop, init.rc, compile drivers and modules. Joey krimm it's a great beginners source but what about updates since the stall between ubuntu 10 64 support, and 64 becoming the default. I feel like not only it's sammy and sprint at fault, but so are devs that arent open with their knowledge. The best gift this community could have gotten in all of this "down time"waiting was time spent learning. Devs stuck waiting on modems and source, start writing and teaching so when you get that source, you'll have a team behind you. That's the spirit of linux and it dont exist on xda's Samsung Epic Development section!
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
When it comes to working on CM most of the work that needs to be done is all coding which we have very few if anyone java coders. Also you can use extract-files.sh on a phone running straight DK28 to get the propietary files needed to build CM with.When it comes to everything else most of the devs have taught themselves how to do the things they so by trial and error and alot of reading the internet. I know I have little coding skill so its would be hard to teach someone something you don't know how to do yourself and alot of the other things like putting togther device files to build android even on the google site has no real information on how to do it at all the best way I think is to just compare what the other phones use and piece it together from that.
Yet it still makes me wonder; why no epic/galaxy s support? Virtually every other phone, and even some tablets like the gtab, have CM support and even CM7 support. Even the HTC Hero, with obviously no source code for 2.2 or 2.3 and no official 2.2 ever to be released, has a working build of CM7. Is it pure incompetence of Epic developers? Is it a lack of interest? Is it simply cyanogen not wanting to support galaxy s devices? I really don't know, but I'd really like to.
theimpaler747 said:
Yet it still makes me wonder; why no epic/galaxy s support? Virtually every other phone, and even some tablets like the gtab, have CM support and even CM7 support. Even the HTC Hero, with obviously no source code for 2.2 or 2.3 and no official 2.2 ever to be released, has a working build of CM7. Is it pure incompetence of Epic developers? Is it a lack of interest? Is it simply cyanogen not wanting to support galaxy s devices? I really don't know, but I'd really like to.
Click to expand...
Click to collapse
From what I can see its not that Cyanogen doesn't want to support the galaxy s devices its that it seems they don't give any input to the devs that are working on CM for the galaxy s. They have basically split off from the main CM source tree itself and run their own source tree. It seemed like (and this is from the limited amount I saw on irc) that there was no input from the CM team they just let them work on their own. CM has ways to setup the code so the source tree remains workable across the board on all the devices it supports, the cmsgs team has just taken a different route on things and gone their own route thus making it not backed by cyanogen, was it the right way to do it who knows but it has made all the galaxy s devices redheaded step children in the eyes of Cyanogen and the CM team as a whole by the looks of it. I know from the point of view of having an Epic the major hold up to it is having coders with the proper skills to do the coding in general we had one coder working on it I don't know if he is still involved or not at this point. All I know is to make is a backed by Cyanogen CM port the coding that has been done so far would have to be completely redone in the ways that the rest of the CM team adds code to the CM source tree with as little to no modification of the stock CM code as possible.
Also I would like to add that I am not trying to put anyone down that is working on the CMSGS team they have done CM working on these devices and am in no way bad mouthing the work that has been done. This is just my view on things and why Cyanogen doesn't back the galaxy s CM ports.
Sent from my SPH-D700 using Tapatalk
theimpaler747 said:
Yet it still makes me wonder; why no epic/galaxy s support? Virtually every other phone, and even some tablets like the gtab, have CM support and even CM7 support. Even the HTC Hero, with obviously no source code for 2.2 or 2.3 and no official 2.2 ever to be released, has a working build of CM7. Is it pure incompetence of Epic developers? Is it a lack of interest? Is it simply cyanogen not wanting to support galaxy s devices? I really don't know, but I'd really like to.
Click to expand...
Click to collapse
Well, trying to comprehend everything that is going on here, I feel like the CMTeam does not feel the Epic is worth porting to CM7 due to it's delay on a FroYo source, which I am positive would make the Epic's porting much easier.
However, it still makes me wonder why they could not have used 2.1 to port to CM7, as like you said, the Hero has been able to do.
It also confuses me that the Captivate has even been able to run a Gingerbread port (I believe cyanogen) then. I realize that the Captivate has no 4G or a slide or anything, but the fact that they were willing to work off of 2.1 I assume gets me wondering why no one has tried making a CM port for the Epic's 2.1
I am trying to understand this as best as I can, so please forgive me if I seem to be giving false input on this conversation.
Its the time taken to port a phone, combined with the number of phones above yours on their list. The fact is they have a list of other phones they feel like investing their time in over the galaxy s line in general which is even more of a reason all knowledge of development on the Epic should be layed out even in pieces like the rest of the information here. Honestly thinking "leak it to noobnl, then we'll get all the goods" isn't going to cut it. Java coders, ubuntu fanatics who have compiled a few apps, and new people willing to learn should be putting heads together compiling new ****. If we dont start a group effort of making a bone stock aosp froyo altering the existing drivers were not going to be much further with source code. And it should be layed out here irc dont work for everyone.
Sent from my SPH-D700 using Tapatalk
acer1096xxx said:
Well, trying to comprehend everything that is going on here, I feel like the CMTeam does not feel the Epic is worth porting to CM7 due to it's delay on a FroYo source, which I am positive would make the Epic's porting much easier.
However, it still makes me wonder why they could not have used 2.1 to port to CM7, as like you said, the Hero has been able to do.
It also confuses me that the Captivate has even been able to run a Gingerbread port (I believe cyanogen) then. I realize that the Captivate has no 4G or a slide or anything, but the fact that they were willing to work off of 2.1 I assume gets me wondering why no one has tried making a CM port for the Epic's 2.1
I am trying to understand this as best as I can, so please forgive me if I seem to be giving false input on this conversation.
Click to expand...
Click to collapse
But like I said, there's CM7 (Android 2.3 if you don't know) for the HTC hero, with no 2.2 or 2.3 source code. So why not us?
theimpaler747 said:
But like I said, there's CM7 (Android 2.3 if you don't know) for the HTC hero, with no 2.2 or 2.3 source code. So why not us?
Click to expand...
Click to collapse
Alright, this is what I believe.
The Hero does not have 4G, or a QWERTY keyboard, two things the Epic does have that could make a pure AOSP port more difficult without a source. Also, HTC runs Snapdragon throughout the whole system, making tweaks a lot more simpler than SGS's Hummingbird Processor, which uses something else (I can't remember) with their system as well.
The last part I'm not sure if that makes a big deal or not, since I have seen a (what I think) CM7 port for the Samsung Captivate, so it may simply be because of 4G and the QWERTY keyboard.
I see what you're saying though. I guess the CMTeam should have no problem making a CM7 port based off of the Epic's 2.1 source...maybe they're just waiting because 2.2 might make it easier and supposedly 2.2 is coming soon so there'd be no point in starting now...otherwise I have no clue.
acer1096xxx said:
Alright, this is what I believe.
The Hero does not have 4G, or a QWERTY keyboard, two things the Epic does have that could make a pure AOSP port more difficult without a source. Also, HTC runs Snapdragon throughout the whole system, making tweaks a lot more simpler than SGS's Hummingbird Processor, which uses something else (I can't remember) with their system as well.
The last part I'm not sure if that makes a big deal or not, since I have seen a (what I think) CM7 port for the Samsung Captivate, so it may simply be because of 4G and the QWERTY keyboard.
I see what you're saying though. I guess the CMTeam should have no problem making a CM7 port based off of the Epic's 2.1 source...maybe they're just waiting because 2.2 might make it easier and supposedly 2.2 is coming soon so there'd be no point in starting now...otherwise I have no clue.
Click to expand...
Click to collapse
I think we also have 'limited functionality' w/ 2.1 as far as the phone's full capability.
2.2 will unlock some hidden potential IMO. Could be the reason why all the hubbub to 'wait for 2.2'.. again, just speculating.
Since I got my hands on Epic 4G optimized dalvikVM and libc.so - posted by no2chem, I couldn't help wondering - what stops us, Captivate developers, from recompiling Samsung source code?
Links
- optimized recompiled from sources Dalvik VM libdvm.so - http://forum.xda-developers.com/showthread.php?t=1017781
- Bionic libc.so, GB based, video player not worked, piss poor battery life, may be main reason for GB poor battery - http://forum.xda-developers.com/archive/index.php/t-1018622.html
bravomail said:
Since I got my hands on Epic 4G optimized dalvikVM and libc.so - posted by no2chem, I couldn't help wondering - what stops us, Captivate developers, from recompiling Samsung source code?
developers.com/archive/index.php/t-1018622.html[/url]
Click to expand...
Click to collapse
Not that I am a Dev, but this is a very interesting thread to watch.. I am sure Dev(s) would be interested in taking a shot at this .....
Bravo Bravomail!!
I'm trying it under Windows
Without much luck. Can't even compile a kernel. Cygwin and Codesourcery are not big friends.
So - anyone?
It is pretty much asking to recompile Platform piece of firmware.
Alternatively - back porting CM7 DalvikVM to Froyo will work
bravomail said:
It is pretty much asking to recompile Platform piece of firmware.
Alternatively - back porting CM7 DalvikVM to Froyo will work
Click to expand...
Click to collapse
I am surprised that there is no Dev take on this... may be they are busy cooking