Database Users

Roms, Kernal Patches, etc.

Alright lets get the record straight. Has anyone tried the kernal patch that puts your mem on a partition on the sd card. Supposidly this boosts performance out of this world. Please post here if you have tried this.
Secondly, we need to attract some developers. I'm willing to donate if anyone wants to code for us. We got a great user base and a really good product. Im conviced the captivate is by far one of the better phones from the galaxy s lineup. If any one knows some developers, introduce them tot his godly beast and let them know there are people out here willing to pay for good quality fixes and roms.
I was thinkin about asking for help from the guys running international s. We could post and ask in the xda area and also modaco and androidforums which have big communities as well.
Any other ideas on how to attract developers? Post here.

systoxity said:
Alright lets get the record straight. Has anyone tried the kernal patch that puts your mem on a partition on the sd card. Supposidly this boosts performance out of this world. Please post here if you have tried this.
Secondly, we need to attract some developers. I'm willing to donate if anyone wants to code for us. We got a great user base and a really good product. Im conviced the captivate is by far one of the better phones from the galaxy s lineup. If any one knows some developers, introduce them tot his godly beast and let them know there are people out here willing to pay for good quality fixes and roms.
I was thinkin about asking for help from the guys running international s. We could post and ask in the xda area and also modaco and androidforums which have big communities as well.
Any other ideas on how to attract developers? Post here.
Click to expand...
Click to collapse
I'm down to donate as well and do anything I can to add to the cause. I really hope this phone takes off cause it is great. I think we have a good chance that a lot of the N1 devs might just come over to this phone and if not they should be getting the Vibrant and I doubt that it will be much trouble to port over to Captivate.

Err why is it better lol? all the samsung galaxy S phones are exacly the same internaly...none its better than the other, the only difrence is the lack of flash/camera and keyboard from the other variants.

rafyvitto said:
Err why is it better lol? all the samsung galaxy S phones are exacly the same internaly...none its better than the other, the only difrence is the lack of flash/camera and keyboard from the other variants.
Click to expand...
Click to collapse
Image, Image, Image. If the galaxy lineup were real life siblings, the captivate would be the only one going to the prom. It also sports fewer gps issues than the vibrant and galaxy s. Ive also seen way less people complain about lag in these forums than the ones for the vibrant and galaxy s (and we have more viewers here than on the vibrant page).
When devs see this device they should be seeing potential.

systoxity said:
Image, Image, Image. If the galaxy lineup were real life siblings, the captivate would be the only one going to the prom. It also sports fewer gps issues than the vibrant and galaxy s. Ive also seen way less people complain about lag in these forums than the ones for the vibrant and galaxy s (and we have more viewers here than on the vibrant page).
When devs see this device they should be seeing potential.
Click to expand...
Click to collapse
All of these so called "issues' are software based, its samsung ****ty touchwiz UI that lags like ****ing hell, not the device hardware, and yes i do agree that the captivate is the sexiest of them all.

Im pretty sure it would be painless to port over Vibrant or Galaxy S fixes to the Captivate. Internally they are the same except for a few minor differences like rafyvitto said which wouldn't be that hard to fix. I'm brushing up on my Java skills and learning about the internals of Android right now. Ive been a iPhone person for a while. Hopefully soon I can be of some help and get hacking on Captivate. From what I've seen and read we have a good phone to develop for because its easily rooted and has an unlocked bootloader. I've also heard that the drivers for the Galaxy S lineup are encrypted, but I haven't seen any confirmation of that. What we need is a dump of the current ROM and also we need a better recovery system like Amon_RA's recovery. The source for his recovery system is on GitHub so we could try and port it over to the Galaxy S lineup.

shouldnt samsung be releasing source for drivers any day now? I thought the word around town was that they were being open with the community on this jazz.

systoxity said:
shouldnt samsung be releasing source for drivers any day now? I thought the word around town was that they were being open with the community on this jazz.
Click to expand...
Click to collapse
They have already released the source code for the Galaxy S here. They don't have to release the source for the drivers because they are proprietary, but from what ive read the binaries for the drivers are in that download so all someone would have to do in link them in. I just don't know if the drivers are encrypted meaning that it has to be an official samsung ROM for them to work. Hopefully not because that would make cooking new ROMs a hell of alot easier.

we should ask the modaco guys for help and info. I dont think we can use the source or drivers from the galaxy s international. I think someone tried doing stuff that way and bricked.
i could be wrong tho

Would also be willing to donate to the cause. The only reason I didn't buy an iPhone 4 is the developers for this phone.

@wesgarner is on the CyanogenMod team / TeamDouche and has ordered a Vibrant.
We might be able to encourage him to port the latest CyanogenMod build once he has the Vibrant's build completed.
He purchased a Vibrant and I think a laptop to do the work. I've already sent him an email about being a beta tester for the Captivate.
Just remember the devs have a life outside of working on phones! Don't ask for timelines - whether you donate or not!
Wes is working on a port for the slide and then he'll be working on the Vibrant.
While the hardware is similar - the software isn't exactly the same. I was messing around with the MMS.apk today and tried to replace my corrupted one with the one from the Vibrant - did NOT work.
Also, the device is capable of having a REAL FMRadio. The Euro versions have an FMradio.apk. I pushed it to the Captivate - but, the Captivate will need the drivers (to build into a kernal) for the FMRadio to work. But, this is entirely possible.
So, yes the hardware is basically the same or similar - it won't necessarily easy. If any of you remember, LOL - this will be akin to porting the N1 build over to the Desire - I think.

The first thing to go should be that awful samsung UI lol. I think the challenge will be porting ROMs for all these different Galaxy S models. I saw this coming when I read the device would make it to all four major carriers in the US plus.

thanks shane, i also heard another dev recently purchased a captivate, do you know anything about this? i'd like to support his endeavors.

Yea I read over in the Vibrant forums that a dev just got a captivate and is working on a recovery. They also have wes working on the Vibrant so hopefully they get cookin on some ROMs. It won't be that much of a hassle to port them over to the captivate. I would advise not fooling around too much with your phone because someone has already messed up his/her phone. They will either have to take it into ATT store and replace it or wait for a dump of the original ROM to come out.

I have tired the MoDaCo rom and it does (kinda - not brick) work with the SGH-I897 (captivate model), I was able to use it to remove the ATT crapware and nearly everything seems to be working. Phone reports its self as Model Number: GT-I9000 in the about phone tab.
One very IMPORTANT problem - I am having difficulty making outgoing phone calls.
Things that I can confirm work:
Bluetooth file transfer
3g data
GSM phone calls (incoming calls work)
Camera
Audible app, pandora ect.
SMS outgoing and incoming messages
Pretty much everything I have tested on the phone except making outgoing phone calls (important as it is a phone after all). So DON'T use this ROM yet, and if you do make a backup.
Hope this helps.

CyanogenMod 6.1 is on its way! And its easy to get on Captivate!

Sorry if this has already been posted.
I apologize for not keeping the site up to date, I’m a slacker We also had a database issue and lost the last post about 6.0′s release, if you were wondering why it went missing.
6.1 is the current work-in-progress and is coming together nicely. There’s a few new features like touch-to-focus in the camcorder, dismiss notifications by swiping, kernel updates for most devices, and improved performance. There will also be support for a few new devices- Acer Liquid, HTC Wildfire and Samsung Vibrant. My eye is also on the new HTC phones that are about to get released like the G2.
A lot of people ask me about adding support for their phone, but we can only support phones that we actually own. The CM team is always looking for new hackers to join up with us to add support for their favorite device. Get in touch with me if you’d like to help.
CyanogenMod is open source. The quality of code being added to CM has vastly improved because of the code review system that we’ve put in place, Gerrit. It’s the same system used by Google to manage the Android Open Source Project. It allows anyone to submit code to the project in a highly-visible way and gives us a way to examine and improve it before it’s actually merged. We want your code, so send us your patches. If there’s something you don’t like, change it.
Nightly builds of CM are always available if you’re brave and want to try out the latest code. If you’re running nightly builds, the best way to stay up to date on new changes is to follow @cmsrc on Twitter.
Our user base is approaching a quarter of a million users. This project has come a long way Thanks for all the support, we are only as strong as the community!
Source- Cyanogenmod.com
Porting a vibrant rom to the captivate is not hard

no wayyyy this is finally coming to our cappy, i'd be beyond happy

Hate to sound like a douche, but is there anything in there (besides maybe some of the features of CM6.1) that we havent known for a long time? No release date, we know thier working on it, and we know they are working with the vibrant.

Well if you look here it still shows as in progress for version 6.0...They have said in the past that the vibrant won't be supported till 6.1 and then someone will still have to port it to the captivate..
https://spreadsheets.google.com/lv?key=0Aledx886TFpZdHdwNzNKZzJLczJjTnA5ekFWRzNxX2c&hl=en&authkey=CNf7ie8G
So I don't think we will be seeing anything soon...

so, i'm sure everyone will get a good laugh, because everyone talks about how this is the best thing about to come since sliced bread........
but what is SO great about this?

buddy17 said:
so, i'm sure everyone will get a good laugh, because everyone talks about how this is the best thing about to come since sliced bread........
but what is SO great about this?
Click to expand...
Click to collapse
Froyo! Plus lots of custom stuff.

well i knew it was based on 2.2....but the "custom stuff" is what i meant. What are some of the big things it does that are so great

I'm new to the whole Android scene so excuse my ignorance but can someone explain how CM6.1 can possibly be put on a GalaxyS phone when there is no source code for the kernel?
Sent from my SAMSUNG-SGH-I897 using XDA App

sdotbrucato said:
I'm new to the whole Android scene so excuse my ignorance but can someone explain how CM6.1 can possibly be put on a GalaxyS phone when there is no source code for the kernel?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The other custom roms seem to use the 2.1 kernel.

I checked that spreadsheet about 3 weeks ago, and it was still in development like it is now for the vibrant.

buddy17 said:
well i knew it was based on 2.2....but the "custom stuff" is what i meant. What are some of the big things it does that are so great
Click to expand...
Click to collapse
Its not really about a wealth of extra features. Cyanogenmod has extra configurability. In addition it is a bit more cohesive than typical roms. I definitely preferred it over the stock Nexus One rom and the stock nexus one rom is better than stock Captivate.
The rapid updates and support is enough for me to use Cyanogenmod.

z28james said:
The other custom roms seem to use the 2.1 kernel.
Click to expand...
Click to collapse
But 6.1 is Froyo, all the ROMs I've seen are Eclaire... How are they using a 2.1 kernel with Froyo?
I was under the impression the reason for no Froyo ROMs on the Captivate was due to lack of source from Samsung?
Sent from my SAMSUNG-SGH-I897 using XDA App

Who needs this when we have cognition?!

designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
exactly

designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
i'm sure when this comes out you'll be able to strip the FroYo out of it and make it your own, and better

CM6.1 will come to the captivate after is released to the vibrant, kernel differences are minimal between the two so porting CM6.1 to the captivate will only require few kernel changes.

yeah i'm sure the port will be done in the time it takes to heat up a pop tart.

designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
+1 Finally got my Cappy right where I want it. CM is awesome, I'm just tired of all the hype, not to mention the waiting for this stuff to happen.

designgears said:
Who needs this when we have cognition?!
Click to expand...
Click to collapse
Everyone who is waiting to use Voice Actions, Chrome-to-phone, and any other cool 2.2-only apps.

Yeah, like real Flash or having the speed boost of the JIT compiler.

[DEV DISCUSSION/Explanation] MIUI

The reason I am writing this thread is because of this:
http://forum.xda-developers.com/showthread.php?t=883222
The OP raised his concern regarding Cyanogenmod not being the biggest concerns for the Dev's. But I honestly think that during the times of CM6 the Dev's could have played a bigger role of bringing it to our Vibrant. I know Eugene tried to do something with it, but i think the release of Gingerbread 2.3 made his work not worthwhile because it was based on 2.2.I am aware that CM7 is in"heavy development cycle" due to Gingerbread 2.3, and most likely will be coming to our Vibrant. With that being said, I feel it is necessary because since we were not able to get CM6 to our phones then why not go for MIUI.
Honestly it is one of the greatest ROMS out there and sometimes i feel that our Vibrant should be getting some more love.Keep in mind that I am in no way bashing TW/Eugene or any other Dev's. Their work is nothing short of quality since I have been a very heavy user of both the Nero and Macnut Series. But I am sure that most people wouldn't mind having MIUI on their phones since its the best of both worlds. (Iphone/Android) Also, I wouldn't know the full process porting such a ROM because it is not an easy task and I am in no way a developer. Maybe it is being worked on with a 2.3 Base? Idk? I am just seeking for answers as I am sure most of other people are as well. I really hope that MIUI really comes to our phone and it becomes one of those projects where many Dev's were in the process to port the SenseUI (back in the day). Just trying to make our community better.
For Those who are unaware of MIUI ROM, here's a demo:
http://www.youtube.com/watch?v=G0U8ISI8YXM
Flame me, Hate me, w.e.. I just think its a debatable subject.
Ty.

What is this? A new trend?

hopefullu for the good.

Here is why, in my opinion.
If 25% of the masses want cm or miui, 25% want 2.2.1, and the rest want 2.3 - 2.3 it will be.
I like miui, I even had a barely working version of it for a little while. But, the guys who use my releases know what they want, those who use TW want their roms bionic, etc for master, eugene et al.
Nowdays, with leaks once a week, I think it will be tough to get a dev to drop everything else and start a port like miui.
But, if I could do it, I would, I think.

jellette said:
Here is why, in my opinion.
If 25% of the masses want cm or miui, 25% want 2.2.1, and the rest want 2.3 - 2.3 it will be.
I like miui, I even had a barely working version of it for a little while. But, the guys who use my releases know what they want, those who use TW want their roms bionic, etc for master, eugene et al.
Nowdays, with leaks once a week, I think it will be tough to get a dev to drop everything else and start a port like miui.
But, if I could do it, I would, I think.
Click to expand...
Click to collapse
Wow, that was the exact answer I was looking for. Like I mentioned before I am no Dev and you being here longer than me and more experienced I will take yourword for it. Your also right about these leaks coming very fast. Hopefully after a full port of 2.3 is done maybe just maybe we can get MIUI.
Thx Alot.

Yeah I Was Gonna Start Working On MIUI But I Need A Cyanogen Source, There Isn't One So I Kinda Hit A Wall
Maybe If Jellette Can Send Me What He Started I Can Just Port MIUI

Erickomen27 said:
Yeah I Was Gonna Start Working On MIUI But I Need A Cyanogen Source, There Isn't One So I Kinda Hit A Wall
Maybe If Jellette Can Send Me What He Started I Can Just Port MIUI
Click to expand...
Click to collapse
There are some serious problems with it but I think it is still on my computer, I'll let you know
Later.

Its Cool If Theres Some Problems, All I Need Is A Starting Point And I'd Be Able To Go From There

Does any other dev have a working cyanogen source??
Sent from my SGH-T959 using XDA App

What's MIUI?
Couldn't figure out what MIUI is from this post or the one linked in the OP.

Its A Chineese Rom
Its Basically The Best Rom Ever
I Have It On My Droid Incredible Its Super Quick And Looks Like Iphone Kinda

os2baba said:
Couldn't figure out what MIUI is from this post or the one linked in the OP.
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=G0U8ISI8YXM
Demo of the ROM.

Why the epic 4g CyanogenMod port is not backed by the CM team my opinion.

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.

donation thread to encourage developers to make a gingerbread rom?

what do you guys think about starting this? id think it would stimulate rom development for our streaks. id be up for donating. i pitched the idea in the irc chat room hoping for some honest feedback, but i dont think djsteve wanted people stepping on his territory so he banned me from chatting. i was only trying to help! im sorry.

let me clear this up
i banned you as you were attempting to suggest that i am not working on gingerbread (i actually am if you had bothered to look at my twitter the last 2 days) and als osuggesting that all the working i have put into themeing is ugly and useless and tried to say that i shouldn be adding them, to which i told you to do it yourself then when you continued going on about it earned a ban, i never once said anything regarding gingerbread (other than its utter ****e anyway and not useful on the streak imho)
and to prove a point attached a screenie of 2.3 on streak

As Bounty,s never seem to work i will close this thread

i would like to apologize to djsteve. i didnt mean to imply that you werent working on a gingerbread rom, though you are giving me mixed feelings on the subject though with your latest comment. as far as i understood, you wherent planning on a gingerbread rom, and wasnt capable of producing one. i was just trying to get more developers in to help. i dont use twitter and havent seen yours in more 2 days so i didnt know what you where up to. could you just let me know next time without the name calling and bans. if it would help get gingerbread on, i could even donate money to you. i would work on it myself but ive had less than with success on building my own roms.
you can relock this thread, thanks for unlocking so i could apologize. youre a good moderator lufc.

i said i wudn be making a gingerbread rom as the changes required to the touchscreen driver to make it useable would not be worthwhile at that time, but the new alpha kernel dell let me have solves said issue

oh awesome. i just tried to check your twitter. theres so much on there i dont even know how to sort it. >_<

ok ill save you time, attaching the recent 2 pics i posted, the touchscreen driver has needed to be totally rewritten to work on 2.3+ so it would of not been worth my time to hack at previously is all i was meaning

Just curious, with the new touchscreen driver, does this make MIUI, Cyanogenmod, etc much easier to build? The alpha kernel supplies a big piece of the puzzle, correct?
Thanks for all your work. Hopefully it's proving to be rewarding

not really, the new driver only works on 2.3+ builds

At least with MIUI, you dont build it, you hack it. They dont release their sources so any ports to non-supported devices are hacked from the orig files.

DJ_Steve said:
not really, the new driver only works on 2.3+ builds
Click to expand...
Click to collapse
Since you said that the new drivers are from an alpha kernel Dell let you have, does that suggest that Dell will continue to support our Streak and maybe even release an official Gingerbread or HoneyComb rom? Or do you think that Dell may supply you with any HoneyComb supported drivers? Also, thanks for all your hard work DJ_Steve.