Who knows what they could be cooking up? Nightlies have halted for the moment, possibly on the verge of RC2 or a stable?
http://buildbot.teamdouche.net/
Sent from my PC36100 using Tapatalk
Lol at the on purpose
Could be since the nexus one got its official update
new android 2.3.3 code is being merged
Woohoo, more cool stuff to play with!
strung said:
new android 2.3.3 code is being merged
Click to expand...
Click to collapse
Doubt it. Buildbot went poof weeks before the 2.3.3 code started merging.
I sure hope there isn't a stable for a while. The nightlys still have a lot that can be added, and it is just too much fun flashing them....
DarkAudit said:
Doubt it. Buildbot went poof weeks before the 2.3.3 code started merging.
Click to expand...
Click to collapse
Buildbot built nightlys just 2 days ago.
Sent from my PC36100 using XDA App
In cyanogen's latest tweet it explains it all. He says that they are having some issues since merging 2.3.3 that will get worked out tomorrow(hopefully). I am sure they will get it worked out, it's just a matter of time.
Rem3Dy said:
Buildbot built nightlys just 2 days ago.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
But the pages are still down. That's my point.
Sent from my PC36100 using Tapatalk
DarkAudit said:
But the pages are still down. That's my point.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Hopefully it will be sorted through by tonight
Sent from my PC36100 using Tapatalk
gav_taylor Gavin Taylor
@cyanogen are we not allowed to see the buildbot details/waterfall anymore?just returning 404s http://buildbot.teamdouche.net/nightly/hero/
8 hours ago Favorite Retweet Reply in reply to ↑
@cyanogen
cyanogen
@gav_taylor its just that way for now because the new build servers aren't completely set up
Click to expand...
Click to collapse
that is all
goo-inside.me for CM download mirror
And now for some truth from Word of God in #CyanogenMod, as well as some deductive reasoning...
1) Buildbot isn't "broken" (at least, nobody from TeamDouche will admit it is, but anyone with half a brain on how the system has worked for the past few months can tell that it is). Right now, Nightlies are pretty much being compiled manually then renamed to be "Nightlies".
2) The buildbot page probably won't come back. Supposedly there's a private version of the page just for the TeamDouche leaders (aka, ChrisSoyars, Cyanogen, kmobs, etc.) but as for a public one? Not likely to happen.
3) RC2 was aimed to come out last week, but thanks to JBQ coming back from his vacation, 2.3.3 was merged in and RC2 has been pushed back until the 2.3.3 merge is smoothed out (which is what Cyanogen tweeted about earlier).
4) There hasn't been any Nightlies the past few days because of the above reasons, and 2.3.3 messed up so much that releasing even a nightly of it now before it's cleaned up will cause too many headaches (read: *****ing from lusers in the 20,000,000 CM threads...). Expect Nightlies to resume probably within the next three days at worst (if they don't resume tonight), and an RC in a week or two (my guess).
Questions?
drmacinyasha said:
And now for some truth from Word of God in #CyanogenMod, as well as some deductive reasoning...
1) Buildbot isn't "broken" (at least, nobody from TeamDouche will admit it is, but anyone with half a brain on how the system has worked for the past few months can tell that it is). Right now, Nightlies are pretty much being compiled manually then renamed to be "Nightlies".
2) The buildbot page probably won't come back. Supposedly there's a private version of the page just for the TeamDouche leaders (aka, ChrisSoyars, Cyanogen, kmobs, etc.) but as for a public one? Not likely to happen.
3) RC2 was aimed to come out last week, but thanks to JBQ coming back from his vacation, 2.3.3 was merged in and RC2 has been pushed back until the 2.3.3 merge is smoothed out (which is what Cyanogen tweeted about earlier).
4) There hasn't been any Nightlies the past few days because of the above reasons, and 2.3.3 messed up so much that releasing even a nightly of it now before it's cleaned up will cause too many headaches (read: *****ing from lusers in the 20,000,000 CM threads...). Expect Nightlies to resume probably within the next three days at worst (if they don't resume tonight), and an RC in a week or two (my guess).
Questions?
Click to expand...
Click to collapse
Thanks for the info, very helpful indeed.
And now some more info from the good #TeamDouche folks in #CyanogenMod:
The buildbot is technically broken... But they're using a different system right now. Instead of one or two servers each building every nightly one after another, they're using a cluster of 1,000 or so computers. However, TeamDouche won't say what/where this cluster is, as it's not entirely legit, and someone's ass would be on the line. My guess? Some EC2-ish cloud, or a University's [email protected] of distributed compiling (which was hinted at, but not confirmed). Or hell, someone who works at a large datacenter edited the main netboot servers' boot images to include a distributed processing daemon, so every time a server is restarted and pulls down the latest system image, it gets added to the cluster.
Because of this new system, they can't have a publicly accessible Buildbot page (nobody got into specifics of why exactly, but my guess is because someone could figure out where/what the cluster is by looking at the name, or when the compiling took place). However, on the up-side, compiling all of the builds at once takes about 15 minutes.
So, unless they can get about 20 high-speed 64-bit Linux buildslaves with fast WAN connections, that can compile a ROM in <20 minutes, and get them all working, we won't be seeing the Buildbot page any time soon.
Related
Who thinks an official release is imminent?
psych2l said:
Who thinks an official release is imminent?
Click to expand...
Click to collapse
Or a mods could have moved it because it doesn't belong in its old location.
Release Candidate CM6 would still be essentially be a daily build. There are still serious issues within CM6.
jerryparid said:
Or a mods could have moved it because it doesn't belong in its old location.
Release Candidate CM6 would still be essentially be a daily build. There are still serious issues within CM6.
Click to expand...
Click to collapse
What "serious" issues would these be? Other than lack of 4G (which is totally worthless, in my opinion), I see no problems with the latest build. Now that we have a fixed Market and Facebook sync I don't see any reason not to use it as a daily (even though I was using it since release). Cyanogen fixed the major Bluetooth and wifi issues, so what's still horribly wrong?
probley moved for all the non rom talk in the thread not to mention all those stupid tags
702DROID said:
probley moved for all the non rom talk in the thread not to mention all those stupid tags
Click to expand...
Click to collapse
The tags were the best part!
TheBiles said:
What "serious" issues would these be? Other than lack of 4G (which is totally worthless, in my opinion), I see no problems with the latest build. Now that we have a fixed Market and Facebook sync I don't see any reason not to use it as a daily (even though I was using it since release). Cyanogen fixed the major Bluetooth and wifi issues, so what's still horribly wrong?
Click to expand...
Click to collapse
On all the nightlies I flash to my Evo, i was unable to access my sound settings, the default Browser would immediately crash upon startup, the market would constantly act up (the updated version included), and my widgets would break after every restart.
That probably only happened to me, but I'd still consider them pretty serious issues. Serious enough to nandroid back to Fresh 1.01 for now, at least.
Mecha2142 said:
On all the nightlies I flash to my Evo, i was unable to access my sound settings, the default Browser would immediately crash upon startup, the market would constantly act up (the updated version included), and my widgets would break after every restart.
That probably only happened to me, but I'd still consider them pretty serious issues. Serious enough to nandroid back to Fresh 1.01 for now, at least.
Click to expand...
Click to collapse
probably error on your part somewhere. I had zero problems besides the listed issues.
TheBiles said:
What "serious" issues would these be? Other than lack of 4G (which is totally worthless, in my opinion), I see no problems with the latest build. Now that we have a fixed Market and Facebook sync I don't see any reason not to use it as a daily (even though I was using it since release). Cyanogen fixed the major Bluetooth and wifi issues, so what's still horribly wrong?
Click to expand...
Click to collapse
Signal issues and battery life as bad as stock rom.
I have tried them all and they do have numerous issues. I have gone to decks rom With sense. Both have bugs but its the lesser of two evils by far.
Sent on my cursed EVO
All of the froyo roms have bugs, I tried Avalaunch before I went back to DC, but as long as the proper warnings were on the first post I didn't see a problem with the thread, it was interesting to track the development. Anyway I thought it was annoying since I was trying to find out who on teamdouche was working on wimax for the evo so I could check out his github but it seems the original thread on general is missing :/
It's in Q&A.
Sent from my EVO using xda App
What about;
http://forum.xda-developers.com/showthread.php?t=709013
Found a few pages in, had just been looking at it.
There we go, search function with just "cyanogen" didn't pull it up, guess you need wildcards
Or awesome mods have done it again.
Sent from my PC36100 using XDA App
Hey guys, if your not on it with the twitter follows, Team Black Hat released a new leak this morning, Android 2.2.1 & Build # 2.3.320.
Just passing info along give all thanks to Team Black Hat! Cheers!
Article about it:
http://www.gizmoninja.com/2010/11/2...oyo-build-2-3-320-courtesy-of-team-black-hat/
Link directly to leak and TBH/Mydroidworld.com
http://www.mydroidworld.com/forums/...-strikes-back-2-3-320-update-must-rooted.html
I grabbed the leak and the system sierra bravo foxtrot. Waiting to see some findings before I commit.
Sent from my DROIDX using XDA App
jaskru said:
I grabbed the leak and the system sierra bravo foxtrot. Waiting to see some findings before I commit.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yeah that's a good call...most people reporting no issues...but good to grab before it disappears..
Acidbath is the ****!
Sent from my DROIDX using XDA App
davisbs999 said:
Acidbath is the ****!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Lmao! No dude Team Black Hat and you are the ****!
Sweet man. Going to get it downloaded but wait to see what the ruling is. If anybody flashes this please tell us what you think
GMB
GrandMasterB said:
Sweet man. Going to get it downloaded but wait to see what the ruling is. If anybody flashes this please tell us what you think
GMB
Click to expand...
Click to collapse
Everyone seems to report okay with it...but with drod2169 doing so much with 2.2.1 already I'm gonna stick with that. Also I am testing his new beta and ROM bootstraps automatically on every boot and more coolness to come so I will stick with rubiX focused for now
Is non-oem battery behavior any different???
With the FROYO update, the Droid X no longer recognized aftermarket batteries for whatever reason. Could someone who has flashed this update check and see if aftermarket batteries are recognized with it, or do we still get the '?' in the battery notification area?
Thanks
Not sure if I could live without LCD density at this point. I am gonna wait and watch developments.
so what all changes are in this? and what makes it worth jumping the ball?
If you want a changelog you will have to contact motorola. Otherwise it is supposedly just a faster build and random reboot issues fixed.
ok. well im guessing rubix would work as its same build set up? im tempted to put the leak in as it fixes some of the problems im having but not sure about not having an $BF full to revert back to, just incase i somehow f up on something. i can't afford to brick my only phone lol.
Will this work if I have Fission 2.1 installed? Or would it just delete my custom tom and bring me to a stock 2.2.1?
Sent from my DROIDX using XDA App
dadsterflip said:
so what all changes are in this? and what makes it worth jumping the ball?
Click to expand...
Click to collapse
Okay I would say that this is probably the official OTA update that everyone is awaiting... The kernel is updated which is going to be the greatest advantage with this release...
Media Fix
Im pretty sure that the "sorry this player does not support..." has been fixed in this update... I use my DX as my primary mp3 player atleast 8 times a day and so that old bug would force me to restart 1 or 2 times daily... been running the new release for over 24 hours and I've yet to get the error (using it heavily and testing the music often aswell...)
Updated System Apps
The only thing ive noticed with these so far is a new Data usage widget built in to blur (now that we dont need unlimited data plans...)
Also the dialer now displays the most recent dialed or missed call just above the number keys...
Battery manager Fix
So the battery manager force close seems to have been fixed... I think this was an issue with the app and not the kernel... the reason i say this is because ive been checking to see that the battery stats non stop (maybe 100 times now) in different scenarios (fresh boot, fresh unplug, etc...) and i have only gotten one force close... I was running the 2.2 NexThemed Systems apk at this point... I imediately reinstalled the 2.2.1 setting apk and without needing to restart my phone the battery stats were fixed.
This issue then would not need u to flash the new release to fix for now... you can probably temporarily fix it on the old 2.2 kernel just by running the 2.2.1 app... (maybe people running the 2.2.1 fission can confirm this...
These are the big things i have noticed so far... I can not confirm the HDMI kernel fix though because i have not yet tested it and even when I was running the old kernel I seldom used the feature and When i did it never gave me any issues...
Hope this helps and I'd be very interested to hear about anything else people have noticed!
Does that update zip also do any kernal or radio updates?
Sent from my DROIDX using XDA App
drod2169 made rubix focused for the leak. guess I will be flashing away now. Thanks team black hat for the leak/system siera bravo foxtrot and drod2169 for the rubix update...
"rubiX Focused 1.9.3, ONLY FOR THE 2.3.320 LEAK"
wipe data and cache mandatory
working fine now. glad to have rubiX on the new leak
Any word on LCD Density working on that new Rubix?
So this new leak update. When vzw release the final version. Are we able to update or?
where did you find that new focus
Sent from my DROIDX using XDA App
I was very comfortable w/D1 but dX is a different ball game and I definitely cannot afford to Brick My new DX, All this "SBF" talk got me scurred...how do I verify what kind of bootloader i have (First verify that your bootloader is @ 30.04)? BTW I am new to DX and not new to android. Can someone also point me in the right direction to educate myself more w/SBF. I have to admit, I just don't know much (if anything) about it nor the purpose..
jaskru said:
drod2169 made rubix focused for the leak. guess I will be flashing away now. Thanks team black hat for the leak/system siera bravo foxtrot
wipe data and cache mandatory
working fine now. glad to have rubiX on the new leak
Click to expand...
Click to collapse
The link seems down. Can you please send me the zip?
android.git.kernel.org[0: 149.20.4.77]: errno=Connection refused
android.git.kernel.org[0: 2001:4f8:1:10:1972:112:1:0]: errno=Network is unreachable
fatal: unable to connect a socket (Network is unreachable)
error: Cannot fetch repo
Can anyone help me? I have built successfully before....
matt2053 said:
android.git.kernel.org[0: 149.20.4.77]: errno=Connection refused
android.git.kernel.org[0: 2001:4f8:1:10:1972:112:1:0]: errno=Network is unreachable
fatal: unable to connect a socket (Network is unreachable)
error: Cannot fetch repo
Can anyone help me? I have built successfully before....
Click to expand...
Click to collapse
Same thing here. Port is open and everything, was working fine earlier this week.
Skynet has become self aware.
Sent from my Nexus S 4G using xda premium
It's down right now for maintenance due to kernel.org being hacked.
notime2d8 said:
It's down right now for maintenance due to kernel.org being hacked.
Click to expand...
Click to collapse
Ah, I heard about that, didn't know they were still working on it. Good to know!
notime2d8 said:
It's down right now for maintenance due to kernel.org being hacked.
Click to expand...
Click to collapse
OMFG I've been driving myself crazy today trying to figure out what was going on, spent like 4 hours on linux trying to find some sort of error and searching google got on my osx partition to see if it was the same story and it was and finally stumbled on this.... I dont feel crazy now and no longer think there are little gnomes that live in my computer just to make my day hell. lol
And here I was about to beat the snot out of something lol
Any word when things will be back up and running, I searched around google but didnt really come up with anything.
https://github.com/android
You can always use it as alternative.
If anyone is interested, I got it fixed by editing the repo in /home/[user]/bin/repo and changing the line that points to the android.kernel.org (Repo url) with https://github.com/android/tools_repo.git.
http://pastebin.com/uiw46JBT
and then doing
repo init -u git://github.com/android/platform_manifest.git -b gingerbread
but repo sync wont work, giving me fetch errors. I don't think there is a solution with the sync error
I hope android.kernel.org comes back up soon
spent all day trying to sync until I found out they were hacked.
Over 24 hours now.... i'm getting antsy! I want to build 2.3.6 for my i9020T !!!!!
matt2053 said:
Over 24 hours now.... i'm getting antsy! I want to build 2.3.6 for my i9020T !!!!!
Click to expand...
Click to collapse
Yeah this whole waiting game is starting to suck, I can't believe someone had the nerve to hack kernel.org. I mean come on with all the servers and sites to hack why pick something thats for open source projects. Why not take down apples site or microsoft...lol.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
still down from what I can tell. I wonder how long before they get everything back up and running again.
Is it back up yet? Can't check now..
Sent from my Nexus S using XDA App
viper2g1 said:
Is it back up yet? Can't check now..
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Still down. I think when it is up, this http link will resolve:
http://android.git.kernel.org/
matt2053 said:
Still down. I think when it is up, this http link will resolve:
http://android.git.kernel.org/
Click to expand...
Click to collapse
Prolly be another day at least I mean they have md5's to check and see which files were tampered with but thats a whole metric **** ton of files to run against the md5's. Plus the have to pull and replace all the damaged and tampered with files from when they were hacked, not to mention somethings probably being done in the security department after the attack.
Its maddening repeatedly seeing that error though ain't it, wish we knew who was behind the attacks, bring the droid mafia down on em. lol
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
Jsmokey said:
OMFG I've been driving myself crazy today trying to figure out what was going on, spent like 4 hours on linux trying to find some sort of error and searching google got on my osx partition to see if it was the same story and it was and finally stumbled on this.... I dont feel crazy now and no longer think there are little gnomes that live in my computer just to make my day hell. lol
Click to expand...
Click to collapse
lol wow just how i felt today till i stumbled upon this thread
Wow! I've been going crazy for days!
I rang my ISP asking if port 9418 is blocked and all!
Why the hell hack open source! It's INNOCENT!
Scum Bags!
*Ignore me*
it's just the main Linux kernal that's been moved to GitHub.
Is the android Kernel on GitHub?
Linus announced a few hours ago that he's put the kernel on GitHub till kernel.org gets back up and running.
https://lkml.org/lkml/2011/9/4/92
https://github.com/torvalds/linux
Cyanogenmod 7.2 RC1
Could not locate any thread on this. Please post your feedback.
Euroskank have been releasing RC1 kangs since forever. Performance is fine, add-ons are nice. I love the ROM but it's not stable on crespo and crespo4g. Other devices are fine though.
I used one of the latest nightly's for a few days hoping they had fixed the stability problems, pulled my phone out of my pocket and found it bootlooping(dim/garbled boot animation loop, which was new to me as before I would just get the 'buttons lit up no responsive sleep of death' with previous versions).
I doubt 7.2 fixed anything with crespo.
Wish someone could figure out what the problem was as stock doesn't have these problems.
Love all the features and tweaks CM7 has over stock, but pulling the battery on a regular basis is not what I would call a stable release.
instability on a stable RC from CM is discouraging.
did anyone report this to CM team?
You can submit bug reports if you find anything broken in your device while running CM7.2-RC1 be sure to submit a report through here , so that they can fix it in time for the final 7.2 release.
gsrdemon said:
instability on a stable RC from CM is discouraging.
did anyone report this to CM team?
You can submit bug reports if you find anything broken in your device while running CM7.2-RC1 be sure to submit a report through **link removed**, so that they can fix it in time for the final 7.2 release.
Click to expand...
Click to collapse
It's a long standing issue with it, as far back as 7.0.3, probably even further.
It's hard to catch a log of the bootloops because they're don't occur in any discernible pattern that I know of.
dewaffelhaus8 said:
It's a long standing issue with it, as far back as 7.0.3, probably even further.
It's hard to catch a log of the bootloops because they're don't occur in any discernible pattern that I know of.
Click to expand...
Click to collapse
Though there's many users available for logging. I've pulled a billion logcats of what was happening when it froze/bootlooped. When it freezes you can still adb to it.
Problem is no one seems really concerned over at CM forums, they'd rather add more stuff than root out 6+ months old problems. *shrugs*
Oxygen FTW. Never crashes on me.
polobunny said:
Though there's many users available for logging. I've pulled a billion logcats of what was happening when it froze/bootlooped. When it freezes you can still adb to it.
Problem is no one seems really concerned over at CM forums, they'd rather add more stuff than root out 6+ months old problems. *shrugs*
Oxygen FTW. Never crashes on me.
Click to expand...
Click to collapse
100% agreed. Oxygen is the best GB rom. The best CM7 rom is probably cybergrmod. (The gb version)
Sent from my Nexus S using xda premium
Been runing the RC for 3 days now, no bootloops or freezing and great battery life so far.
Sent from my Nexus S 4G using xda premium
thegtfusion said:
100% agreed. Oxygen is the best GB rom. The best CM7 rom is probably cybergrmod. (The gb version)
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I gotta say if you're going for CM7 based ROM, Euroskank kangs are awesome.
I've decided to be patient, and only checks like 5-10 times a day :silly:
On a more serious note: On Google's Nexus page they write:
Nexus 7 comes with Android 4.2, the latest version of the world's most popular mobile platform.
Click to expand...
Click to collapse
Are Google shipping new Nexus 7 with 4.2? If they are, surely they should be able to release an OTA?
(I can't link to pages yet, but the quote is from google.com/nexus/7)
Now.
Now.
Now.
Now.
Now.
Now.
Now.
Now.
Now.
Now.
Now.
Taps fingers.......
Now.
Now.
Sent from my SGH-I747M using xda app-developers app
I check when somebody on the forums confirms its release.
I'm very passive that way.
*Sent from Nexus S*
no point in checking now....when 4.2 gets pushed to AOSP you WILL see it everywhere. and then the devices should get it within the day.
save your fingers, i think you are going to need them on the 13th (official launch of the nexus 4 and nexus 10)
I'm not going to get AOSP 4.2 since i'm on AOKP. Just don't wanna miss some of it's features. But some tim aftere release there will also be AOKP 4.2
What update.
Google will personally call everyone who owns a nexus 7 Tablet two hours before its release . During the call you will be given information on how to obtain this Life saving Technological Breakthrough. They will also explain to you the update procedure. Google will also get your mailing address as to where to send you a refund check for the full amount of the cost of Android 4.1.2 . The check refund is to say they are sorry for having to wait for the new Os. If you mention 3 times while on the phone with them about . thats 3 times talking bad about apple and Ms They will increase your refund by 3x .. Please be prepared to do a short online survey (required).
On topic.. I do not check The day it comes as soon as i log into the forums i will see all the post from all of you guys checking for me...
Have a nice day The above story comes direct from the small part of my brain that does not as i tell it to..
I'll check around the 14th. No point really in checking before then.
erica_renee said:
Google will personally call everyone who owns a nexus 7 Tablet two hours before its release . During the call you will be given information on how to obtain this Life saving Technological Breakthrough. They will also explain to you the update procedure
Click to expand...
Click to collapse
LOL :laugh:
Never... because as soon as it gets pushed to AOSP rascarlo merges the source and I get my fix rasbean FTW.
Sent from my Galaxy Nexus
ÜBER™ said:
Never... because as soon as it gets pushed to AOSP rascarlo merges the source and I get my fix rasbean FTW.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Uber no more eclipse for you?
Travisdroidx2 said:
Uber no more eclipse for you?
Click to expand...
Click to collapse
Nope. Building rasbean been using it and like it so much I run it on my tablet.
Sent from my Galaxy Nexus