CM9 NIGHTLY (UNOFFICIAL SEMI-KANG) FOR CDMA TORO
Hey! This is my first post here on XDA, though I've been a long time user of these very forums, since the OG Droid root.
This is also my first ROM, though the credit should really go to the Cyanogenmod team. This is a pull from the ICS branch of CM's git repository,
built on Ubuntu x64. The proprietary .so files were pulled from Team-Kang's repo, because theirs was the only files I could actually get running.
I'm running this as my main install, and so far there's been no problems at all.
THIS IS NOT STABLE.
This is the equivalent of a nightly from CM, though much less polished. It can be considered a pre-alpha nightly build.
I am not liable for anything this ROM may do to your phone.
I'm doing this because I always enjoyed Cyanogen's ROMs straight without any mods or tweaks. I knew exactly what was running on my
phone. This is a straight pull from git. I haven't included any extra pulls from git or gerrit, nor anything else. It's pure Cyan.
I will do nightly releases of this ROM. CM's source is constantly changing, and I'll try and keep up with that, at least until the
build servers are doing automated nightly compiles.
Download:
thewcubed.com/update-cm-9.0.0-RC0-GN-CDMA-KANG-signed.zip
To install:
Download the ROM to your phone.
Download a GApps zip to your phone. (I use kejar31's zip)
Make sure you have the latest version of CWM's recovery.
Boot to recovery.
Backup your current system and data partitions.
Wipe data, cache, and the dalvik-vm cache. (I always do it twice to be on the safe side.)
Flash the ROM.
Flash GApps zip.
Reboot.
(tentative) Hooray!
If the download is too slow, I'll try and upload this to a couple mirrors. I don't know if my server's going to be able to handle a request flood on a 10Mb/s upload line.
Glad your making a Rom, but...
1) its in the wrong forum and
2) you dont have a link because of your "probation" status of < 10 posts
Good luck with your work though!
Also there's (unofficial) builds by a CM developer in the development section already:
http://forum.xda-developers.com/showthread.php?t=1397122
@kenyu73
I know that this isn't in the Dev section, but I can't switch it yet due to the 10 post limit. It should still be valid in the General section though.
The URL is still valid, simply copying and pasting it begins a download of the zip.
@got_milk
There may be unofficial builds, but those are for GSM devices. I apologize for not clarifying in the title that this is for CDMA/LTE versions of the Galaxy Nexus.
toroidal_loop said:
CM9 NIGHTLY (UNOFFICIAL SEMI-KANG)
Hey! This is my first post here on XDA, though I've been a long time user of these very forums, since the OG Droid root.
This is also my first ROM, though the credit should really go to the Cyanogenmod team. This is a pull from the ICS branch of CM's git repository,
built on Ubuntu x64. The proprietary .so files were pulled from Team-Kang's repo, because theirs was the only files I could actually get running.
I'm running this as my main install, and so far there's been no problems at all.
THIS IS NOT STABLE.
This is the equivalent of a nightly from CM, though much less polished. It can be considered a pre-alpha nightly build.
I am not liable for anything this ROM may do to your phone.
I'm doing this because I always enjoyed Cyanogen's ROMs straight without any mods or tweaks. I knew exactly what was running on my
phone. This is a straight pull from git. I haven't included any extra pulls from git or gerrit, nor anything else. It's pure Cyan.
I will do nightly releases of this ROM. CM's source is constantly changing, and I'll try and keep up with that, at least until the
build servers are doing automated nightly compiles.
Download:
thewcubed.com/update-cm-9.0.0-RC0-GN-CDMA-KANG-signed.zip
To install:
Download the ROM to your phone.
Download a GApps zip to your phone. (I use kejar31's zip)
Make sure you have the latest version of CWM's recovery.
Boot to recovery.
Backup your current system and data partitions.
Wipe data, cache, and the dalvik-vm cache. (I always do it twice to be on the safe side.)
Flash the ROM.
Flash GApps zip.
Reboot.
(tentative) Hooray!
If the download is too slow, I'll try and upload this to a couple mirrors. I don't know if my server's going to be able to handle a request flood on a 10Mb/s upload line.
Click to expand...
Click to collapse
I love seeing new developers come here everyday
One small issue though, this is posted in the wrong section. This should be posted in the GSM Galaxy Nexus Android Development or CDMA Galaxy Nexus Android Development (depending whether its GSM or CDMA)
toroidal_loop said:
@kenyu73
I know that this isn't in the Dev section, but I can't switch it yet due to the 10 post limit. It should still be valid in the General section though.
The URL is still valid, simply copying and pasting it begins a download of the zip.
@got_milk
There may be unofficial builds, but those are for GSM devices. I apologize for not clarifying in the title that this is for CDMA/LTE versions of the Galaxy Nexus.
Click to expand...
Click to collapse
Did you ever ask the guys from cm team before you post the kang build?I dont think this allowed.
Sent from my Galaxy Nexus using Tapatalk
Getting your post count up and then posting in Development would have been the thing to do. This will get lost in General, and I can't see it being moved to Development or everyone and his mate would be using that loophole.
@afilopou The CyanogenMod source is released under the Apache 2.0 license. This ROM isn't built for commercial gain, I'm crediting the CM team as the writers of the code, nor am I attempting to alter the code and then copyright it. The concept of "open-source" is that one can do something like this, building and redistributing.
@Kalavere I'm not trying to get this moved to the Dev. If there's enough interest in it, I'll repost the thread to Dev when I'm able. The problem I had was that there wasn't a vanilla build of CM that I could find anywhere for the CDMA/LTE toro.
toroidal_loop said:
@afilopou The CyanogenMod source is released under the Apache 2.0 license. This ROM isn't built for commercial gain, I'm crediting the CM team as the writers of the code, nor am I attempting to alter the code and then copyright it. The concept of "open-source" is that one can do something like this, building and redistributing.
Click to expand...
Click to collapse
Perfect .Just mention it because i dont want to see another locked thread
Related
to be honest with you guys.
i have no idea what the heck is the difference betwenn the two.
especially all the builds.
are there something different with each build?
can someone out there explain to me?
sorry,i've tried searching it up but nothing.
if there isn't something different about each build for the cyanonogenmod nightly
then why do they have soo many builds?
i mean why keep the only builds there.
you know everyone wants the recent update.
to fix the bugs or what not.
but if i can get some really good explanation on this,it would be really night.
thank you.
the nightlys are beta versions, so they can be buggy.
6.0 is a stable version which is solid and has no bugs
-
btw this topic should be in general or something, some people around here get upset easily for posting in the dev section.
stoney05 said:
the nightlys are beta versions, so they can be buggy.
6.0 is a stable version which is solid and has no bugs
-
btw this topic should be in general or something, some people around here get upset easily for posting in the dev section.
Click to expand...
Click to collapse
You could read the changelog. It has the added features since 6.0 listed (called 6.1). 6.1 isn't released yet, but when it is the nightlies will be changed into 6.1.
Nightly just means they rebuild the rom every night and allow people to download it to install.
Caspers25 said:
to be honest with you guys.
i have no idea what the heck is the difference betwenn the two.
especially all the builds.
are there something different with each build?
can someone out there explain to me?
sorry,i've tried searching it up but nothing.
if there isn't something different about each build for the cyanonogenmod nightly
then why do they have soo many builds?
i mean why keep the only builds there.
you know everyone wants the recent update.
to fix the bugs or what not.
but if i can get some really good explanation on this,it would be really night.
thank you.
Click to expand...
Click to collapse
this should be in the q&a
Quick summary:
Final builds: Relatively stable, tested, and at the point that Team Douche is comfortable with how it handles.
Nightly builds: Compiled every night at 00:00 GMT directly from the github source. Has all the latest features (like the nightlies currently have a newer kernel and some nice camera features) but can be quite unstable and typically aren't recommended for day-to-day use.
I would Edit your Title for this thread..
please Remove [ROM] as it signifies this is a ROM thread and this is, of course, not..
The CyanogenMod development process produces nightly builds automagically for bleeding-edge users. Here's sort of how the process works generally:
1. Bugs/feature requests/etc are submitted to Google Code:
http://code.google.com/p/cyanogenmod/issues/
2. Items are then transported to Gerrit for code review once a solution is written / being worked on:
http://http://review.cyanogenmod.com
3. Once tested/approved, commits happen to GitHub, which is announced via cmsrc on Twitter:
http://github.com/CyanogenMod/
http://twitter.com/cmsrc
4. Nightly builds happen automatically via BuiltBot with all commits from GitHub (even if they break stuff, so these nightlys aren't for the uber-novice). You can watch nightly builds happen, which are typically around 9pm EST unless kicked off manually:
http://buildbot.teamdouche.net/waterfall
5. Downloads available nightly here (by build number):
http://mirror.teamdouche.net/
And that's pretty much it. You can keep a close eye on Cyanogen's personal Twitter (twitter.com/cyanogen) and even converse with him and some of TeamDouche as well on IRC via FreeNode, in #cyanogenmod. They're great guys and very open to the future of CM. I've known Cyanogen for years and he's a great, fun guy with a brilliant mind and a passion for open source.
Anyway, I hope this clears up the CM nightly process for those who don't really grasp it yet. There may be a few diversions from the process, but generally that's how it works, and is a great way to keep very close track of what's happening when. Understanding is the key to NOT asking 'when will this be done?' or 'where's the changelog!?', etc.
Moved to Q&A as not development.
do the current nightlies, or the future 6.1 release, require the engineering bootloader 0.76?
i did unrevoked3 and ended up with 0.79 of course. i've been playing with many roms but not yet CM6 due to this restriction ... the ENG bootloader thread reads like a cautionary tale, there doesn't seem to be any understanding of why some phones play well with the update and others don't.
i'm sure there's a very good reason, but i don't understand the need for 0.76 for only CM6.
coastal said:
do the current nightlies, or the future 6.1 release, require the engineering bootloader 0.76?
i did unrevoked3 and ended up with 0.79 of course. i've been playing with many roms but not yet CM6 due to this restriction ... the ENG bootloader thread reads like a cautionary tale, there doesn't seem to be any understanding of why some phones play well with the update and others don't.
i'm sure there's a very good reason, but i don't understand the need for 0.76 for only CM6.
Click to expand...
Click to collapse
As far as the CM code, *any* bootloader version is permitted as of a commit last week. This shouldn't be an issue anymore on nightlies, but likely will be in CM6.0.0.
We get FM radio tonight
http://github.com/CyanogenMod/cm-kernel/commit/6dcd7908655309f231d090d7714a312f2b8a5483
This thread is for everyone who compile's Cyanogenmod Kang build's from source and would like to post/share with everyone. If you want your build included in this post just pm me and I will update this post asap.
Warning these are unofficial CM7 build's (with myself cherry-picking comments from CM's Gerrit for testing) which may have unfinished mods and/or broken code that is continually changing, ONLY THOSE WHO KNOW WHAT THEY ARE DOING SHOULD FLASH THEM. Don't file bug reports on the Cyanogenmod issue tracker from any of these build's. Please don't bother cyanogen or #teamdouche as you have been warned these build's are unofficial and come with no support except on this thread. If you have any question's try searching as your question might have been already asked and answered. Note: I, nor is anyone else is/are responsible for any bricks or problems you may encounter.
I no longer have a G2 as I gave it to my mom, but will update this periodically. Sorry for the delay I have been super busy with the move, my new job and fixing this house I am now living in.
All credit goes to cyanogen & #teamdouche, thank them not me as all I do is compile
Items from CM's Gerrit that I cherry-picked:
* Give me time
Last Commit repo synced before building-
* Enable access to Audio Effects Settings
I understand that this build is unofficial and I take no responsibility if you brick your phone- Will be update in about an hour and half as I plan on running it when I get home
Please visit @cmsrc, CM's Gerrit or Nightly Device Changelog for a complete list of changes or commits.
Also those who don't know a Kang is an unofficial nightly that someone builds from CM's github.
I will update this post as often as needed to stay current or change as necessary.
Hey everyone, here are the kangs and cherry picks that i will be providing. I want to thanks plasmadragon007 for allowing me to post here.
Everything in the above post applies to here. We will most likely be making these at a different time of day with possible different commits. I do not own a g2 but i do have a couple of decent guys willing to test each kang before posting. If they are not available, i will let you know that the build has not been tested. I do this because i enjoy it and want to. I hope you enjoy it also.
All credit goes to cyanogen & #teamdouche.
Items from CM's Gerrit that I cherry-picked:
Lockscreen background http://goo.gl/5p5Np
you can find my builds on Euroskank http://goo.gl/U7xx6
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
All Builds + recoveries can be found here. I have included a date + md5sum
http://xdafiles.net/rhcp/
More Builds/Gapps can be found here:
gridlock32404 - cm7rc0 built by gridlock will be http://www.crackflashers.com/ cause of dropbox excessive traffic, will build new ones tonight if new commits
I uploaded it just now.
You will need to flash CWRecovery 3.0+. Which can be found at
http://xdafiles.net/rhcp/
This has been all built from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
If you want to see protected apps. You need to edit your build.prop in system with the following:
Code:
ro.build.description=soju-user 2.3 GRH55 79397 release-keys
ro.build.fingerprint=google/soju/crespo:2.3/GRH55/79397:user/release-keys
This is built from current src as of 30 mins ago.
So, there is a few video fixes and others.
You can read the updates at: http://r.cyanogenmod.com/#q,status:merged,n,z
I appreciate it man. I just moved and I don't have an internet connection yet. It's hard to repo sync on a 1mbps Android tether.
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
smjfosho said:
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
This one is more recent, with the newest commits.
Is your link supposed to point to recovery.img?
bivio said:
Is your link supposed to point to recovery.img?
Click to expand...
Click to collapse
Thanks. I mistyped fixed now.
Camcorder still borked?
rhcp0112345 said:
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
The rom can be found at: http://www.mediafire.com/?15l284rnq1zjt1h
I uploaded it just now.
You will need to flash this with CWR 3.0. Which can be found at
http://mrcellphoneunlocker.com/recovery.img
This has been all buit from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
Click to expand...
Click to collapse
the link to the recovery img is broken because it says reovery not recovery
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Vandale said:
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Click to expand...
Click to collapse
Sure your not Thats why your watching these threads like everyone else, including me!!
Downloading now, Thanks for the build!
Been waiting for this all day. Thank you!
[ROM]cm7 gingerbread flavor
[Recovery]clockwork 3.0.0
Glad everyone likes.
My pleasure
Sent from my HTC Vision using XDA App
do you know if usb issue was addressed in this build
Have not tested it. Nor do I see any commits. So I assume same issue.I don't mount usb so doesn't bother me. I use adb
Sent from my HTC Vision using XDA App
is the "unknown" thing still showing up in phone number? its the only thing keeping me from sticking with Gingerbread @[email protected] silly, i know.
having problem flashing the img help
I get an assert failed error trying to flash the ROM, too bad I was really looking forward to trying CM7 .
cough..... cough http://forum.xda-developers.com/showpost.php?p=10083640&postcount=151 cough..... cough... man I'm really sick
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
This version is a release candidate, but you will find it stable for everyday use.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the Samsung Galaxy S, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official posthttp://forum.cyanogenmod.com/topic/...r-the-samsung-galaxy-s-v710-rc1-26-june-2011/CyanogenMod:
Latest Version: update-cm-7.1.0-RC1-GalaxyS-signed.zip
Download: Link
Mirror: Link
MD5sum: c7e812d4c94de40176d463de7f720ffdGoogle Apps addon:
Version: gapps-gb-20110613
Mirror: Link
Mirror: LinkThe CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
cool. just released
thank you all devs
We know. There is the oficial thread posted by codeworks. So why did you post this?
Sent from my GT-I9000 using XDA Premium App
sefuleo said:
We know. There is the oficial thread posted by codeworks. So why did you post this?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
This is the official thread for the RC (and future RC's)... codeworkx's thread is for nightlies. the difference being is that the build flashed from this thread is allowed to report bugs to the issue tracker.
RC is too in codeworkx thread. But anyway.... Thanks for posting.
Sent from my GT-I9000 using XDA Premium App
sefuleo said:
RC is too in codeworkx thread. But anyway.... Thanks for posting.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
there is no information about the RC('s) in codeworkx's thread. his thread clearly says nightly at the top and is for nightlies and nightlies only. the "latest version" link does not count because following that no matter what will show you *all* options. this is the standard CM way of doing things. a thread for nightlies and a thread for stable(ish) version. feel free to check any other CM-supported device's section and you will see both as well.
so is RC1 > Nightly
tb5... said:
so is RC1 > Nightly
Click to expand...
Click to collapse
RC1 = stable(ish)
nightly = bleeding edge
RC will only be updated a few times over the next few weeks until the final build is released. nightlies will continue to be pumped out every night. benefit of RC is you can post issues to the issue tracker and actually contribute back to the community.
So whats the deal?
Used to run CM on my HTC Magic.
Have heard that there are issues with battery life etc. on SGS.
What are the cons of SGS CM71. Cant seem to find list of good/bad issues.
Also, the nightly "must be on froyo" is not listed on the CM7 webpage (and this thread). I can flash from sammy gingerbread now?
BatGnat said:
Used to run CM on my HTC Magic.
Have heard that there are issues with battery life etc. on SGS.
What are the cons of SGS CM71. Cant seem to find list of good/bad issues.
Also, the nightly "must be on froyo" is not listed on the CM7 webpage (and this thread). I can flash from sammy gingerbread now?
Click to expand...
Click to collapse
all the wiki instructions clearly say to flash from Froyo, and those are the instructions to follow.
Kaik541 said:
all the wiki instructions clearly say to flash from Froyo, and those are the instructions to follow.
Click to expand...
Click to collapse
Yes, but you had best add it to the install instructions here too, or the 15 questions you get about bootloaders a day will become 150 or more. No fun at all.
Also, it notes in the instructions on the OP that if you are updating a previous CM7 install, you do not need to flash Gapps again. This has not been true for around 15 nightlies now...has whatever issue that required reflashing Gapps along with a nightly been fixed?
Downloading it..
Finally a RC release ..good work Cyano's Team ..
I use Cyanogen 7 on my Galaxy S and also on my Htc Magic 32b
Cyanogen 7= The best rom of ever
Cheers
Perfectly and thx
rschenck said:
Yes, but you had best add it to the install instructions here too, or the 15 questions you get about bootloaders a day will become 150 or more. No fun at all.
Also, it notes in the instructions on the OP that if you are updating a previous CM7 install, you do not need to flash Gapps again. This has not been true for around 15 nightlies now...has whatever issue that required reflashing Gapps along with a nightly been fixed?
Click to expand...
Click to collapse
the ROM threads for RC releases are cookie-cutter, only replaced with proper links/md5sums. as for the gapps thing, I've been flashing updates every few days and have literally never once had to reinstall gapps =/
also, rschenck, please don't leave me to moderate this thread alone, you make the i9000 threads worth reading
And ANOTHER question....
If I opt not to install the RC1 release itself, but wait and install the next Nightly, which would be 40 for the i9000. Will that automatically update me to RC1?
Plus I am always ready to lend a hand and/or a stinging bon mot, you just seem more up on the RC1 situation than I so I defer to your wisdom.
Lastly, regarding reflashing Gapps, it has been advised as a precaution for ages now to avoid potential trouble. I see no harm in continuing to do it.
Kaik, thanks for the thread. Downloading the RC now (I've been running nightlies for months, if this is good enough I might have my dad run it!) Just wondering, are you a member of the CMSGS team? And if so, do you have any insight to headphone controls being fixed?
A little suggestion..
PLEASE CYANO'S TEAM READ THIS:
See at SuperAosp 8.6 camera..is similiar at Cyanogen camera but it is best in graphics..background black ..photo button better..see it please
rschenck said:
And ANOTHER question....
If I opt not to install the RC1 release itself, but wait and install the next Nightly, which would be 40 for the i9000. Will that automatically update me to RC1?
Plus I am always ready to lend a hand and/or a stinging bon mot, you just seem more up on the RC1 situation than I so I defer to your wisdom.
Lastly, regarding reflashing Gapps, it has been advised as a precaution for ages now to avoid potential trouble. I see no harm in continuing to do it.
Click to expand...
Click to collapse
personally, I always run under the assumption that each and every flash will horribly destroy my phone and make backups of apps with TiBu and nandroid every time while praying I never have to open heimdall again. I then keep the gapps zip and at least one earlier nightly on my SD card. RC1 is basically just a "nightly considered stable for the purpose of bug reports" for official means. nightlies will always surpass stable builds (and will always come with the risk that they are far more likely to break)
chambo622 said:
Kaik, thanks for the thread. Downloading the RC now (I've been running nightlies for months, if this is good enough I might have my dad run it!) Just wondering, are you a member of the CMSGS team? And if so, do you have any insight to headphone controls being fixed?
Click to expand...
Click to collapse
I'm an honorary member of teamhacksung as it were. I've been out of the i9000 group because coolya and codeworkx mostly have it under control and rschenck provides the right amount of help while being entertaining in a way that I couldn't possibly hope to be. as for headphone controls, atinm is aware of the issue and it's on the list of things to be fixed (including TV out at some point).
I didn't follow that much the Nighlies thread in the past month because i didn't have time to flash and reflash continously.
I'm wondering, on this RC1, if everything works, including all that didn't work perfectly in nightlies builds.
And what about battery life? I switched from JVH to JVP and i noticed a small reduction of battery life. Is CM7 RC1 overall better or worst than the aforementioned releases?
ANyway, thumbs up for the passage from nightlies to RC, i was looking forward for CM7 on my SGS since when i bought it in January. Coming from an HTC phone i really missed the speed and functions of CM.
Team EOS XOOMICS 4.0.4 Wingray MZ604NIGHTLIES
Welcome to the evolution of TiamatXOOM.
With the AOSP release of Android 4.0 begins the next dawn of the Android operating system. And with this release comes Team EOS, the natural evolution of the TiamatXOOM development team.
It is the goal of Team EOS to develop and maintain the highest performing and most stable AOSP based rom for an array of platforms. The launching point for this development effort is the Motorola XOOM.
For the latest news on Team EOS Xoom releases make sure you follow @teameos on twitter and on IRC on Freenode in #xoom.
--
NOTE: Team EOS, it’s members, friends, dogs, cats, and associates are in no way responsible for any loss of data or device functionality. Use this at your own risk!
--
A quick note on Nightlies: NIGHTLIES ARE DEVELOPMENT BUILDS. They are automatically generated once every 24 hours and represent the compilation of the latest commits to the code repository. While every effort is made ensure that the commits that are accepted are stable and do not have a negative impact to the overall performance and function of the builds it is not possible to test every aspect of a commits impact to the overall repo prior to it’s inclusion in a given build. As a result it is entirely possible that instabilities may be introduced as a result of a given days commits. That is the nature of the nightly system, and the risk that is taken using the latest code changes to the project.
EOS Xoom is an AOSP based rom. It is developed and maintained by Team EOS and is the culmination of our own in house development efforts.
Team EOS Xoom Nightly builds: http://goo-inside.me/devs/teameos/roms/nightlies/wingray/
G-Apps Package
Because this is an AOSP based rom Google Apps are not included in the base rom. To install Google Apps please flash the following package after installing the base rom:
Use the latest available gapps package available from http://goo.im/gapps
*Note - You will need to re-flash G-Apps after you flash an updated nightly build. You can do this before you reboot after the installation of a new nightly.
Also note that if you are coming from an earlier G-Apps package you will need to wipe prior to installation of this package in order to avoid FC issues.
--
Current Known Issues:
This builds is only for the MZ604 Wingray (WiFi XOOM) It does not support data on any GSM or 3G only Xoom
Features:
Because these are nightly builds the included features are constantly evolving. Change logs are generally generated on a daily basis.
Change logs can be viewed at http://nightlies.teameos.org/changelogs/
For the most up to date and comprehensive listing of the changes included in this rom please visit http://review.teameos.org
Kernel:
Tiamat ICS Xoom kernel
Support for OC;Under/Overvolt
Governors: lagfree, interactive, conservative, ondemand, userspace, performance
Kernel Note: In compliance with GPL kernel source can be found at: http://git.tiamat-dev.com/tegra2/tiamat-xoom/
--
Installation Notes:
These builds are designed to be installed from your favorite recovery (Solarnz R4c, Rogue, Clockwork)
Perform a full wipe (read Factory Reset) prior to installing this over ANY Honeycomb based rom (this includes all Tiamat roms)
Please note that due to fundamental changes Google has made to the way Android works there are certain issues that cannot be resolved without additional components from Google and the hardware manufacturers.
BUGS!
If you find strange or otherwise unexplained errors please report them here: https://bugs.teameos.org/ Please include logcats and as thorough a description of the issue and what lead up to the issue as possible. With out this we will be unable to track down these errors.
FEATURE REQUESTS!
We need YOU, yes YOU to help us build the best AOSP rom out there. Have an idea for a feature you want to see implemented then let us know!
Team EOS Feature Request
Changing the Stock Motorola Dual Core Boot Logo Splash Screen:
While not a necessary feature of the Team EOS ICS builds make sure you check out the Team EOS Motorola Xoom Boot splash utility in the Android Market:
EOS Motorola Xoom Boot Splash
Want to contribute to the Eos rom? Well you can!
Just follow http://teameos.org/?page_id=6 to checkout our source code, and information on how to submit changes for review.
Welcome to the XOOM evolved. Welcome to Team EOS.
For the latest news on Team EOS Xoom releases make sure you follow @teameos on twitter and on IRC on Freenode in #xoom.
Please note that due to fundamental changes Google has made to the way Android works there are certain issues that cannot be resolved without additional components from Google and the hardware manufacturers.
Also a note on 3G/4G Xooms- You can infact flash and install this rom on 3G/4G xooms. You will not however be able to use the 3G/4G radio. There are new basebands that are needed in order for the 3G/4G radios to be able to communicate with the RIL and until these updated basebands are released we are in a holding pattern for radio connectivity.
Also there are sporadic reports of HDMI partly functioning. Full HDMI functionality is dependent on additional proprietary binaries that Google has not been able to release yet due to licensing issues.
Also, please note that while the current builds are proving to be very stable, and for users that do not use their cellular radio they can be used as a daily driver these are still nightly builds and are subject to constant development. If you find strange or otherwise unexplained errors logcats are greatly appreciated as it makes it much easier to track down issues.
Thank you all for your support!
*Updated G-Apps Package*
The developers working on CM9 have released an updated G-Apps package for 4.0.3 AOSP based builds
New version is 4.0.3 V8
A Special Thanks goes out to gpstar this G-Apps build
Download: http://www.multiupload.com/54DD4VIXZ6
MD5: 4a6a7543b025a17f9536eccc4e5afc17
*Note - Because of changes made to the G-Apps package a wipe will be required if installing this version of G-Apps over a previous G-Apps package in order to avoid FC issues. This version of G-Apps appears to address some of the communications issues that have been plaguing Google services on AOSP builds.
Bug Reporting:
As you test out the platform and you discover bugs please report them to:
https://bugs.teameos.org/
A couple of notes about bug reporting. If it is an application issue (IE a particular game generates FC errors) please do not report it. There is nothing that we can do about specific application issues.
If you do report an error please, Please, PLEASE include logcats showing the errors. It is often time difficult if not impossible to replicate errors and logcats make resolving issues much much easier. Please feel free to add the logcats as attachments to the bug report.
Changing the Stock Motorola Dual Core Boot Logo Splash Screen:
While not a necessary feature of the Team EOS ICS builds make sure you check out the Team EOS Motorola Xoom Boot splash utility in the Android Market:
Eos Motorola Xoom Boot Splash
Thank you again for your continued support of Team EOS!
I can say from personal experience that this ICS Rom is working beautifully. Yes, there are a few bits missing but it's clear that this is taking the Xoom to another level, altogether.
Cudos to Team EOS for taking this step. I can't wait for the next nightly.
Do we need to do a full wipe and reset if coming from razorbladex's rom?
double1 said:
Do we need to do a full wipe and reset if coming from razorbladex's rom?
Click to expand...
Click to collapse
I didn't. Just wiped cache.
double1 said:
Do we need to do a full wipe and reset if coming from razorbladex's rom?
Click to expand...
Click to collapse
Since I have no idea what rom that is the answer is yes. The only time you do not need a wipe is if you are coming from a factory OTA. Generally speaking all custom roms will require a wipe prior to install.
Did you have to reflash gapps and also will the su root file from razorbladex's rom conflict with this rom because I'm supposing this comes with root I just wanted to know if the two root files would conflict?
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
Nusince said:
Since I have no idea what rom that is
Click to expand...
Click to collapse
That's the original Xoom ics rom posted a few days ago here on xda by member razorbladex.
Again, since I have no way of knowing anything about razorbladex's ICS rom as I have never flashed it my inclination is to tell you to wipe first to ensure there are no residual or unforeseen conflicts. With that said, what you choose to do is up to you.
When you flash a new rom /system gets overwritten which includes the su binary so this is a non-issue. This build includes the latest changes to the su binary.
double1 said:
Did you have to reflash gapps and also will the su root file from razorbladex's rom conflict with this rom because I'm supposing this comes with root I just wanted to know if the two root files would conflict?
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
That's the original Xoom ics rom posted a few days ago here on xda by member razorbladex.
Click to expand...
Click to collapse
That first part of my question was for okantomi, sorry I should have quoted him since he stated that he had flashed this over that rom.
double1 said:
Do we need to do a full wipe and reset if coming from razorbladex's rom?
Click to expand...
Click to collapse
I didn't wipe anything coming from his rom, just flashed the rom then flashed gapps and everything is fine, really quick and smooth
Is it possible to update the first post with a list of broken stuff so that it's easier to keep track?
Sent from my Galaxy Nexus using XDA App
Can anyone comment on HD youtube and netflix working ?
I'm running this already...but can you tell me why on all the ice builds there is a gray triangle next to the wifi icon in the lower right hand corner?
rockhumper said:
I'm running this already...but can you tell me why on all the ice builds there is a gray triangle next to the wifi icon in the lower right hand corner?
Click to expand...
Click to collapse
Because you clearly have no cell network signal! Mine has it too. Give it a while: ICS roms are new and have yet to be extensively tweaked for little details like this.
bumbernut said:
Can anyone comment on HD youtube and netflix working ?
Click to expand...
Click to collapse
Both play content. Navigating Netflix isn't the smoothest.
It's because these builds are essentially ready for 3G/4G connectivity. However for the time being the cellular radio icon will show regardless of if you have a stingray(3g/4g) or wingray(wifi) board. This will be addressed once we have the necessary components to bring life to the cellular radios.
rockhumper said:
I'm running this already...but can you tell me why on all the ice builds there is a gray triangle next to the wifi icon in the lower right hand corner?
Click to expand...
Click to collapse
---------- Post added at 04:59 PM ---------- Previous post was at 04:40 PM ----------
HD content in Youtube works fine. Don't know about netflix.
bumbernut said:
Can anyone comment on HD youtube and netflix working ?
Click to expand...
Click to collapse
Very interesting. On the other rom HDMI worked but calendar didn't. Now on this rom calendar works but HDMI don't lol. Small trade off but I find this very interesting.
James
Netflix works fine for me
cant wait to flash this, just downloaded it and will be flashing when I get home, good work guys!
Can we assume that further updates will be flashable over this ROM without wiping ?
As many of you know the GSM Note 2 is supported by Team OmniROM in a unified build format. This work is inspiring to me as the team split from CM for altruistic reasons. I have come to consider OmniROM my AOSP branch of choice due to their philosophy toward security and development.
I see a niche for our community where some of our members may be uncomfortable utilizing the unified build for any number of reasons.
My product is no more than a straight source built t0ltetmo build as the OmniROM spec is drawn up for the t0lte and adapted by the t0ltetmo spec on the OmniROM github. All source is available at the OmniROM git. I make no changes unless noted (in the remote chance that changes occur they will be documented/git referrenced).
I make no promises or warranty of any kind, all flashing is done at your own risk and should not be thought to be the responsibility of anyone other than the person deciding to flash the ROM. While I will attempt to help you work through issues, I do not plan on integrating non-Omni commits or "fixes" with very few exceptions. If it is broken in the unified build it will be broken in this one as well.
I plan on putting up new builds weekly if not a bit more frequently if I am inspired. If I see a change in OmniROM commits that looks promising I expect that I would post a new build. Getting to the point where stuff wasn't broken took some serious banging of the head.
Flashing instructions:
Using the most current TWRP, ClockworkMod, or PhilzTouch recovery; wipe data, system, cache, and dalvik (especially if coming from a different ROM).
Flash the unofficial OmniRom .zip file from the link below
Flash the gapps of your choice (CM or PA are good)
Boot phone and let sit on a stationary flat surface.
Do not touch the device for 10 minutes to allow the caches to build.
Reboot the device and set up
omni-4.4.4-20150322-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150313-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150223-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150206-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150107-t0ltetmo-COUGMADE.zip
omni-4.4.4-20150101-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141220-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141216-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141208-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141014-t0ltetmo-COUGMADE.zip
PA Gapps (good variety of options)
All source code for OmniROMis available in the OmniROM Github.
OmniROM t0lte git
OmniROM t0ltetmo git
DonkeyCoyote Samsung Vendor git
Props and credit to:
The OmniROM team.
UtkarshGupta for providing advice in working through build issues on compiling OmniROM and maintaining for t0lte.
Rmanne for assistance in getting my previous efforts in getting the unofficial CM ROM running by help with troubleshooting the build process.
And certainly not least mattlowry for being solid from his first posts in the doubleshot community, evolving along with weekendsR2short to porting for the doubleshot, and elevating his game on the Note 2. His advice and example made the unfathomable become doable.
Mine
10/14/14 - I know the camera is a bit weird with how it won't connect after a while. This is present in the unified build as well.
1st!! Yeah! Thanks for another great rom amd contribution to our community!
Coug is definitely one of the greats in our GN2 community. Total warrior in my book. Grateful for his time and talent.
Awesome build, but I am not getting any mobile data. I used Philz recovery. Anything I am missing here?
EDIT: Just tried with the latest TWRP also, still no mobile networks.
Mrzoops said:
Awesome build, but I am not getting any mobile data. I used Philz recovery. Anything I am missing here?
EDIT: Just tried with the latest TWRP also, still no mobile networks.
Click to expand...
Click to collapse
What does your APN show?
Nice.
Great Job
This instal went smooth and all seems to be working great. Nice rom TY
After a short sabbatical, T889 OmniRom is back. Still 4.4.4 KK.
What happened to the other omnirom thread?
Coug76 said:
As many of you know the GSM Note 2 is supported by Team OmniROM in a unified build format. This work is inspiring to me as the team split from CM for altruistic reasons. I have come to consider OmniROM my AOSP branch of choice due to their philosophy toward security and development.
I see a niche for our community where some of our members may be uncomfortable utilizing the unified build for any number of reasons.
My product is no more than a straight source built t0ltetmo build as the OmniROM spec is drawn up for the t0lte and adapted by the t0ltetmo spec on the OmniROM github. All source is available at the OmniROM git. I make no changes unless noted (in the remote chance that changes occur they will be documented/git referrenced).
I make no promises or warranty of any kind, all flashing is done at your own risk and should not be thought to be the responsibility of anyone other than the person deciding to flash the ROM. While I will attempt to help you work through issues, I do not plan on integrating non-Omni commits or "fixes" with very few exceptions. If it is broken in the unified build it will be broken in this one as well.
I plan on putting up new builds weekly if not a bit more frequently if I am inspired. If I see a change in OmniROM commits that looks promising I expect that I would post a new build. Getting to the point where stuff wasn't broken took some serious banging of the head.
Flashing instructions:
Using the most current TWRP, ClockworkMod, or PhilzTouch recovery; wipe data, system, cache, and dalvik (especially if coming from a different ROM).
Flash the unofficial OmniRom .zip file from the link below
Flash the gapps of your choice (CM or PA are good)
Boot phone and let sit on a stationary flat surface.
Do not touch the device for 10 minutes to allow the caches to build.
Reboot the device and set up
omni-4.4.4-20141208-t0ltetmo-COUGMADE.zip
omni-4.4.4-20141014-t0ltetmo-COUGMADE.zip
PA Gapps (good variety of options)
All source code for OmniROMis available in the OmniROM Github.
OmniROM t0lte git
OmniROM t0ltetmo git
DonkeyCoyote Samsung Vendor git
Props and credit to:
The OmniROM team.
UtkarshGupta for providing advice in working through build issues on compiling OmniROM and maintaining for t0lte.
Rmanne for assistance in getting my previous efforts in getting the unofficial CM ROM running by help with troubleshooting the build process.
And certainly not least mattlowry for being solid from his first posts in the doubleshot community, evolving along with weekendsR2short to porting for the doubleshot, and elevating his game on the Note 2. His advice and example made the unfathomable become doable.
Click to expand...
Click to collapse
Just a Heads up. Your file link is sending us to the att version...i didnt realize it until i tried to flash it and recovery advised it as such. I found th file by looking up your profile there it listed the correct t889 file. Downloading now.
butwhydoitalk2u said:
Just a Heads up. Your file link is sending us to the att version...i didnt realize it until i tried to flash it and recovery advised it as such. I found th file by looking up your profile there it listed the correct t889 file. Downloading now.
Click to expand...
Click to collapse
So it is. Did you DL the version from October then? I'll upload the correct version in a minute. I'll also do a clean build after the I walk the kids to school.
Coug
AngryDinosaur said:
What happened to the other omnirom thread?
Click to expand...
Click to collapse
UtkarshGupta is taking a step back to focus on more important things in life. He is working to hand off Omni for Note 2 to a new maintainer if one can be found.
Coug76 said:
So it is. Did you DL the version from October then? I'll upload the correct version in a minute. I'll also do a clean build after the I walk the kids to school.
Coug
Click to expand...
Click to collapse
I was able to find the file in your profile. So i downloaded it. I am currently running it and so far so good. Thanks.
butwhydoitalk2u said:
I was able to find the file in your profile. So i downloaded it. I am currently running it and so far so good. Thanks.
Click to expand...
Click to collapse
Thanks for the heads up. I have corrected the link and it is the 12/08/14 build. I just synced the repo for both Omni and CM and will run a build for both this morning. I should be able to post new builds this afternoon or evening depending on what the afternoon allows.
New build is up
EDIT: I pulled the DL link as the build was broken.
New build is up.
Coug76 said:
New build is up.
Click to expand...
Click to collapse
Could that new maintainer be you? Because cougmade omni is pretty slick, smooth sailing. ?
Thanks for the build.
Coug76 said:
UtkarshGupta is taking a step back to focus on more important things in life. He is working to hand off Omni for Note 2 to a new maintainer if one can be found.
Click to expand...
Click to collapse
I'm too much of a novice to take that role. That and my wife would invite me to find other living arrangements.
New build is up.