I searched but as usual I suck at searching this site so if there's already a thread please point me there and a mod can close this question down.
I've been running gingerbread ROMs for about the last month or so. It's been fun and I like the work the devs have done so far but I'm just not satisfied with the performance yet (mostly battery drainage stuff, some lockups and other minor issues).
I want to go back to a froyo ROM. Anything I need to do special for this? do I need to flash the old bootloaders? I'm not sure what is required but I'm sure it's simple.
Thanks.
http://forum.xda-developers.com/showthread.php?t=1123566
On this page, just a few threads down.
Your answer is yes, GB bootloaders are backwards-compatible; just don't flash a Froyo ROM that includes secondary Froyo/Eclair bootloader or your phone is not going to be very happy.
Another eagle-eyed member.
Thread closed, please search before you post. Thanks.
Can anyone point me to a kernal most compatible with mosaic5 ,i have spent all weekend flashing gingerbread roms and have yet to find one as good as m5,also any feedback on apex 8.1 and also I tried to flash continuum 6.1
Sent from my GT-I9000 using XDA App
Have you tried asking in the M5 thread? I think the kernel they are using is the latest from existz...BUT i have no idea. I would double check in the thread if I were you. As far as Apex, i have not tried it. Again, .. this is just what i do and believe me it helps. If your curious about a ROM, go into that thread skim through the first few pages or 10 and see what people are saying.. go to the last 10 or so pages of the thread and again, skim through the posts, see if people are having issues or if people are just like "oh man, i love this ROM" .. try to get an idea how peeps are liking it
Mosaic 5 has the darkcore kernel. Any kernel that is jvp will work. WE found the included kernel to be the most stable but you are welcome to try both existz kernels or xcal's jvp.
btw this should have been posted in the mosaic Q&A thread instead of opening a whole new one...
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?
Hi guys!!
I just got my galaxy note and flashed to checkrom gb. As coming from galaxy s2 with ics previously, i would really like to use ics on note too.
Recently i have been seeing lots of threads on users bricking their phone because of ics?!
I have tried searching and reading up few threads including the PSA in android development forum. But i still do not have a clear picture of what's going on or what's causing the brick.
Can someone explain to me what should i do or not do to prevent bricking? Still safe to use ics now? Which rom should i use?
Thank you for your time!
Better stay on GB till the sources are out.
Or if you flash ICS, do not use stock or cwm recovery.
But there's still no guarantee as few devs here said that deleting large files on ICS roms might corrupt eMMC.
Alternatively, you could flash either CM9 or Asylum custom ICS Roms. Both
these Roms contain the same safe CM9 kernel, built from SGS2 sources.
Hello Forum,
I am very new to rooting devices and installing custom ROMs.
I have a few questions I would like to ask, I searched the forum and couldn't find appropriate answers.
http://forum.xda-developers.com/showthread.php?t=1103399 (This being one of the threads)
I was going through the sticky thread here: http://forum.xda-developers.com/showthread.php?t=1789397
Which says, "WARNING: Do NOT use CM9, Asylum CM9 or AniDroid kernels as drivers on ANY CM10 based Rom - and vice-versa!"
I had recently flashed CM9.1 on my galaxy note GT-N7000, by following the instructions mentioned on their wiki page.
Just installed clock work recovery, entered the recovery mode, did a WIPE & installed CM9.1 & google apps.
After a few days I followed the same procedure and flashed CM10's latest preview. It went well and everything seems to be working, except that
the phone is a tad bit laggy and doesn't really deliver what JB is supposed to deliver. Sometime the power button won't wake the screen up.
This can be because CM10 is still in preview stage and the stable release is not out. But now that thread I mentioned before kind of bothers me.
Do I need to update the kernel while switching from CM9 to CM10? Downloads are available in the same thread. Or does the kernel update on its own while flashing CM10? And if I have to update the kernel do I need to have CF-Root? Does the fact that I have clock work recovery on my device mean that I have CF-Root?
Sorry if my question is too noob-ish, I just wan't to know a little theory behind what I'm doing so I don't screw my device. None of the threads that I found in the search explain things simply. I would be really glad if anyone of you could help me just understand things. I really appreciate this community for having put up so much information, thanks in advance!