Is there any chance that cyanogenmod of coming for the SXL? I recently upgraded my device from my old Nexus s and am missing the features of CM7
You would be better sending a PM to Cyanogen and see if he has any plans for it, other then that its waiting on someone elses good grace to Port it but it might not quite be the same as it was (less Cyanogen releases it then itll be grand!)
Having spoke to Capychimp he says that a port of CM7, MIUI or even ICS will need a custom kernel. So until we can get someone working on that its not going to happen
isnt there some custom kernals from core droid and such?
eggfred said:
isnt there some custom kernals from core droid and such?
Click to expand...
Click to collapse
Yeah there is a custom kernel for BinDroid, but that is like a heavily tweaked version of stock whereas CM7 is AOSP and therefore would need a completely different kernel, as I understand it... correct me if I'm wrong
ahhhh thanks for that
Do you have any idea on how long it would take for someone to make a new kernal?
For someone who knew what they were doing it probably wouldn't take that long, but most developers on here are supporting multiple devices and probably don't have the time to try it at the minute...
Related
Hey All,
I was just wondering if data2ext would be possible for our beloved milestone. Could some devs please take a look at this - http://www.xda-developers.com/android/new-hack-for-desire-and-nexus-one-data2ext/ ?
I hope this will be possible.
mohitrocks said:
Hey All,
I was just wondering if data2ext would be possible for our beloved milestone. Could some devs please take a look at this - http://www.xda-developers.com/android/new-hack-for-desire-and-nexus-one-data2ext/ ?
I hope this will be possible.
Click to expand...
Click to collapse
I'm going to say no (on Froyo) currently - data2ext seems to requires the same thing that apps2sd (CM) does, and the G.O.T. 2.2.1 leaked SBF doesn't support it.
If you still have 2.1u1/2 from MOTO - then maybe.
So you are saying that the former one is may be compatible but no for the new one ? may be we have to wait for the officiall froyo for this ?
Craven68 said:
So you are saying that the former one is may be compatible but no for the new one ? may be we have to wait for the officiall froyo for this ?
Click to expand...
Click to collapse
Yes, the 2.1 moto kernel supports it, but the leaked 2.2 moto kernel doesnt. Hopefully the official kernel 2.2 will. So if your phone is still on eclair it could be potted, but I don't think any devs are focused on eclair roms much anymore
The way it's implemented requires ext access from Android. This requires a kernel module which for now does not work in our leaked 2.2.1 based builds. It will probably work when Moto releases the source code for the kernel. As of now, ext access is only on 2.1 based builds.
Lollipop_Lawlipop said:
The way it's implemented requires ext access from Android. This requires a kernel module which for now does not work in our leaked 2.2.1 based builds. It will probably work when Moto releases the source code for the kernel. As of now, ext access is only on 2.1 based builds.
Click to expand...
Click to collapse
So will this work with eclair then? (2.1) And if yes, how?
mohitrocks said:
So will this work with eclair then? (2.1) And if yes, how?
Click to expand...
Click to collapse
yes, it should work on eclair - if a dev is willing to try to port it.
Can't wait, hope this will get ported so I can mess with it my Milestone.
Tried this on my Droid tonight and had no luck. On my old phone(CDMA HTC Hero200) I was going from 190MB of internal space to around 473MB of internal space. I just tried it tonight on my Droid with all the coding on Better Terminal Emulator Pro and had no luck whatsoever. I am running CM7.1 Stable on my Droid. It's Android 2.3.7 Gingerbread and thats what I had on my Hero as well. I'll keep looking at the coding and everything and see what I can do for us. I'll talk with some guys over in the Hero Forums about it too. There are different types of data2ext versions as well that may be of some use to us.
EDIT: OK,I had an old android app sitting around on my external called swapper.apk. I gave it a try on my droid today as well and had no luck. I used to use that app on my old T-Mobile G1 way back in the day. Thought it MAY work but got nothing,I'm at a loss right now but will keep working on this for everyone!
Hey guys, been out of the loop for a while as I've been settled on JPY for a few weeks now. However, I saw a friend flash his Desire today with Oxygen, a gingerbread-based AOSP ROM. All the SGS ROMs I can find so far are based on the stock Samsung firmware - is there any work being done on a full AOSP ROM like Oxygen or Cyanogen? I can't find any details about this anywhere.
I am very curious about this question. Because if answer is simply no, it's time to sell Galaxy S. Gingerbread will be the last update from Samsung and AOSP could be the future of this phone then CM7 for SGS seems to have big problems and it's the only AOSP ROM for SGS which I'm aware of...
What big problems?
I'm using CM7 for a month right now and it's pretty stable if i can say. Yes, it lacks some features and some bugs are not fixed yet (theres a workaround tho), but if you follow it's thread the progress they make are great. They're already into mainline, so probably it will reach RC status in a month/maybe less, who knows.
After the devs are done, i think there will be a custom ROM based on CM7/AOSP.
~drz
CM7 is getting there. And with Gingerbread coming out, that should make things easier for the dev.
Yes, but with no source then there is nothing big. GB leak, only helped them with "less" important stuff (FM radio, etc.)
~drz
If we have CM7 and kernels for 2.3, and leaks of 2.3 from the i9000 and are able to use gingerbread base from nexus s ( think thats what cm7 uses? i cant remember...so if its wrong just insert name of correct phone back there), why is it that we havnt seen anything other than Cyanogen mod and MIUI (which doesnt even count cause its still just the CM7 base) on the 2.3 homefront? I am by no means complaining, just kind of confused. I would think that devs would be chomping at the bit to get their hands on 2.3 for their phones and start their rom modding magic. Anyone have some insight on this other than some sort of sarcastic remark or derogatory comment? lol
we only have the aosp source. and with that why port a basic aosp rom if you can have cyanogen? also there is miui. these are probably the most requested roms on any android version on any phone. an m9 port would be nice but i think the devs that can make the aosp ports better are part of these two projects. so rather than waisting time porting aosp and doing something original and asking the cm7 guys how they fixed this or that they are helping the cm7 and miui projects. also there are still problems and limitations with cm vs samsung. cm7 cant use the camera to it's full abilities. also samsung music player supports more codecs. plus the samsung roms are easier to port allowing time to work on features and tweeks. the reason the i9000 gingerbread hasnt bee built into a captivate rom is that without kernel source the roms would not be as functional as a 2.2.1 port or even cm7 because they would have problems reorienting the sensor mapping and remapping the headset. when samsung source drops there will be much more gingerbread roms and when cm7 is official there will be spinoffs
No source, no kernel, no ROM.
Sent from my Captivate
Hello everyone,
I was just curious how all these gingerbread ROMs for the Captivate are being released, and Cyanogen 2.3 for the Capitivate, having been worked on for months, is still only in pre-beta. I am not trying to be impatient, I know the devs are working hard to get cyanogen out ASAP, I was just curious why this was.
Thank you.
rcllcr said:
Hello everyone,
I was just curious how all these gingerbread ROMs for the Captivate are being released, and Cyanogen 2.3 for the Capitivate, having been worked on for months, is still only in pre-beta. I am not trying to be impatient, I know the devs are working hard to get cyanogen out ASAP, I was just curious why this was.
Thank you.
Click to expand...
Click to collapse
simply put CM7 is being written and developed from "scratch" and the jvb jvh roms are ported.
Not to mention that the CM7 for captivate is running 2.3.4 so technically "we're" behind CM7
betadan said:
Not to mention that the CM7 for captivate is running 2.3.4 so technically "we're" behind CM7
Click to expand...
Click to collapse
Not for long Most of the Devs are already working on JVH
AOSP is the way to go in the long run as more Samsung drivers get ported over. 2.4.x will probably never be ported to the Galaxy S phones by Samsung, but unless there are major kernel changes, upgrading CyanogenMod to 2.4 will happen relatively quickly.
nkrick said:
AOSP is the way to go in the long run as more Samsung drivers get ported over. 2.4.x will probably never be ported to the Galaxy S phones by Samsung, but unless there are major kernel changes, upgrading CyanogenMod to 2.4 will happen relatively quickly.
Click to expand...
Click to collapse
I see, so once it is caught up with the other cyanogen supported phones, it will be on the same update cycle, and therefore be more sustainable when it comes to new releases of android?
Frankly cm7 is actually being developed, where as the other ginger bread releases are being cooked/tweaked. Samsung did 80% of the work then xcal kicked in the next 15%.
So to answer your question, the reason it is "behind" is because they are not using a pre optimized build, and they are developing from the ground up.
Sent from my SGH-I897 using XDA Premium App
Code is back up, we're hosting there again now. Grooby's thread is not under control by us and anything he says/does is not condoned by onecosmic or his team.
We're up to rc3 now and the rom is much more stable than before, seems to be performing better and people are working on fixes for gps,it should be working soon. updates are on the google code pages here: http://code.google.com/p/ice-cream-sandwich-sgs/
The rom should now be flashable from anything,just wipe and flash.
Thanks, will give it a try
Sent from my SGH-T959 using XDA App
lol, hopefully someone is able to put up a new mirror for it.
xD
Seems like a very popular file.
CM t9 Dailer and cm launcher now as a flashable zip
Thread Link
This Rom is fast and smooth ,music player is perfect loving it, gallery work great too and there is a fix for root in the i9000 tread http://www.megaupload.com/?d=S67I9Q0L .front camera is still broken ,recorder.and brightness not working just those fews bugs to be fix and this rom is going to be one of the best ICS rom .great work onecosmic's..........
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
a2296455 said:
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
Click to expand...
Click to collapse
Taking nothing away from neobuddy or teamhacksung, onecosmic did have the first ICS for the Galaxy S posted.
http://forum.xda-developers.com/showthread.php?t=1338636
a2296455 said:
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
Click to expand...
Click to collapse
stop being a steve jobs
a2296455 said:
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
Click to expand...
Click to collapse
so you want onecosmic to stop working on the rom that allowed neo to even release ICS on the vibrant. Also he doenst have a vibrant, this rom is originally for the sgs and is ported over, hence why we need to flash another kernel. The problem with the vibrant community isnt the devs its the people like you that expect a rom that is 100 percent perfect and on top of that does your dishes and makes bacon
What you should do is go talk to neo about helping out with the rom instead of kanging cm and other applications. I swear his roms have more bloat on them then twiz.
a2296455 said:
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
Click to expand...
Click to collapse
LMAO, dude you're an idiot. I hope you brick your phone just because.
bearsfan85 said:
What you should do is go talk to neo about helping out with the rom instead of kanging cm and other applications. I swear his roms have more bloat on them then twiz.
Click to expand...
Click to collapse
Now that was uncalled for.
I understand that onecosmic was the first to build a functional ICS for the Galaxy S series, but that does not mean he has to be the only one. What's wrong with KANG'ing something? Neo isn't taking credit for anything, he's gave credit where credit was due.
I'm on neobuddy ics can i flash firs the rom and them the kernel or this rom uses a different partitions and i need to flash first the kernel reboot recovery flash rom/flash kernel and them reboot system
Sent from my SGH-T959 using xda premium
Passion v6 & v7 vs Onecosmic
What we want in this community is quality ROM's. No one has a monopoly on good ideas and we as users always benefit when we have more than one group working on competing ideas.
I tried and respect Neo's ICS Passion Roms. I've been using them since v5. v6 is a good daily ROM. v7 was too laggy for me.
Onecosmic's 4.0.3 ROM is much smoother. From the first boot. Brightness doesn't work. But everything else does.
For me, this demonstrates the value in alternatives.
Good work Onecosmic.
Try screen filter if you need to lower brightness
Sent from my SGH-T959 using XDA App
From my understanding, Neo's rom is still 2.X kernel while Onecosmic's is 3.X based. Different approaches I guess. Onecosmic is more than happy to help out with the Vibrant community, you just have to ask. I tried the latest and had an issue with the cpu staying on full blast and chewing up the battery so I went back to stock MIUI until he hammers a few other things out.
Nice way to turn a pretty thread in a flamewar, guys :/
Either way, does video recording works here?
And can I flash over Neo's ICS build or only over ICS?
I wish the OP was more informative...
So the OP says to first flash an ICS kernel.
Can I use the Vibrant ICS kernel here or do I use an i9000 one?
After installing this rom my phone will not reboot into recovery... is their a special way to get back into recovery?
Can anyone check if there mute/unmute issue present on this ROM ?
Anyone else have no service after flashing this?