[Q] Nightlies, build numbers and dates? - Nook Color Q&A, Help & Troubleshooting

I've been scratching my head figuring out which combination of versions of CM7 and Dalingrin OC kernel to use and I've been getting confused because different people use different words to describe versions: build number, nightly number, date.
Can someone please confirm whether I've worked it out right:-
build number (example: 2.6.32) means the Barnes and Noble stock kernel version on which CM7 or Dalingrin is based
Nightly number (example Nightly 113) means the version of CM7
Date (example 042411) means the version of the Dalingrin OC kernel
Given noob tutorials often mention both CM7 and the OC kernel it would be really nice if the way versions are numbered was clear...

I'll try, though I'm a noob myself...
linux kernel version: either 2.6.29.x or 2.6.32.x
CM7 hasn't been on 2.6.29 since nightly 86 (or so). So any CM7 > nightly 90 is 2.6.32. This includes the most recent update-cm-7.1.0-RC1-encore-signed.zip.
nightly number
This is simply the nth build of CM7 on a (mostly) nightly basis. The full list can be seen at:
http://download.cyanogenmod.com/?device=encore
date of Dal OC file
This is simply the date he releases a new build. As far as I know, these aren't explicitly tied to any particular CM7 nightly build, so long as the kernel aspects are compatible. This means, use a recent CM nightly (100+) and a recent OC kernel and you should be fine.
Just an observation for others that may be reading...
Dalingrin seems to releases builds in groups of 4:
These are for users of the stock BN 1.2 ROM that have been MN'ed. -sd for folks that are running the stock from sdcard, emmc for those running from internal.
Froyo1.2-sd
Froyo1.2-emmc
These are for users CM7. -sd for folks that are running from sdcard, emmc for those running from internal.
CM7-sd
CM7-emmc
I hope this helps.
Cheers

Related

[Q] does Android 2.3.4 Build:4.5.1-134_DFP-74 count as Gingerbread or Froyo CM base ?

I read about the different CM9 froyo and GingerBread "build-branches" in some threads:
in first post of this thread:
[ICS] 12-Jan "CM9" Experimental Builds for the Defy !
http://forum.xda-developers.com/showthread.php?t=1353003
"Note: Builds from the 7.Dec and after are made for gingerbread kernel (2.3.4 betas for defy and/or for 2.3.6 recent defy+)
Quarx will do this rom with the 2.3.4 kernel, which allow the downgrade to 2.2.2 Nandroids (with boot/devtree).... Lot of apps are now fixed with the new GL and with only a few changes from AOSP sources (frameworks)"
And also Quarx post on 6th December:
(quoted from http://forum.xda-developers.com/showthread.php?t=1353003&page=110 )
"New build is up: http://www.megaupload.com/?d=OC1RABID
3D,2D,3G,GSM,Youtube.. some other fixes...
Sorry for the short changelog....i want to sleep...
This reflash your kernel to 4.5.1-134_DFP-74."
Seems to me like 2.3.4 on Defy+ with build 4.5.1-134_DFP-74 is somehow inbetween Froyo and GingerBread, and is also refered to as Gingerbread BETA in this SBF thread: http://forum.xda-developers.com/showthread.php?t=966537
Does this mean a Defy+ with the 2.3.4 Build 4.5.1-134_DFP-74 SBF
is capable of switching between both recent (dec 2011-feb 2012) Froyo and GingerBread CM7 or CM9 builds as long as one does not flash another full SBF ?
(I already made a nandroid of my system to be able to go back to almost-stock as there seem to be no leaked full SBF 4.5.1-134_DFP-74)
To put it in other words:
I have a Defy+ and would like to try CM7.2 froyo (quarx) Nightlies and also try dual boot with CM9 froyo Nightlies.
Seems Quarx's December 2011 - January 2012 builds are based on same kernel as my stock-sbf.
Is there any reason I could not use (quarx) CM7.2 and CM9 based on 4.5.1-134_DFP-74 on my Defy+ ???
regards /Slstr
Stats for my unmodified DEFY PLUS
System Version: 45.0.74.MB526.Retail.en.DE
Model number: MB526
Android version: 2.3.4
Baseband version: EPU93_U_00.60.00
KERNEL VERSION: 2.6.32.9-gbad50c3
[email protected] #1
Build number: 4.5.1-134_DFP-74
AFAIK, you cant downgrade the kernel cause the bootloader dont allow you to do that, cm7 with froyo kernel may work,
Changing rom that are GB kernel based works on the Defy+, CM72 and CM9 must work on your Defy+!
Sent from my MB525 using XDA App
Thanks for answering Leonardo!
I found some more very interesting info regarding Kernels (and 2.3.4 Kernel)
http://forum.xda-developers.com/showpost.php?p=20152629&postcount=1633
zyxwvut said:
The kernel in CM9 is still 2.6.32.9 but is still different than the 2.6.32.9 kernel used in CM7. CM7 uses the froyo 2.6.32.9 and CM9 uses the gingerbread 2.6.32.9, confusing I know! Moto uses the same kernel with froyo and GB with internal differences. I guess it was easier for them to reuse and modify 2.6.32.9 than to go with 2.6.35 kernel for their defy+ GB rom
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20150761&postcount=14406
zyxwvut said:
Lol they are all 2.6.32.9 kernels even froyo kernel. 2.3.4 and 2.3.6 still use 2.6.32.9. The differences are internal but still numerically the same
Click to expand...
Click to collapse
This post: http://forum.xda-developers.com/showpost.php?p=22209959&postcount=2837
and this thread: http://forum.xda-developers.com/showthread.php?t=1482481
seems like some users can mix n match easily now

[Q] CM 7 and MIUI (official vs unofficial) + Flash Question

Hello all,
I'm posting this thread because I'm getting a little confused after all this reading. Basically, I just need some confirmations.
Lately I've been reading a lot on CM7 and CM9 but now I'm also starting to get interested in MIUI.
I've come across:
WIUI
MIUI Pikachu edition
MIUIandroid.com
Motorola Defy MIUI.us
I underlined my 4 questions for your convenience.
So I have some Questions on Custom ROMS
As you can see, I've looked for an official MIUI build for the Defy but I can't seem to find an official MIUI build. These listed above are all 'edited' by someone.
Could someone explain what i'm (probably) overlooking? Is there an official MIUI?
At the moment WIUI and Pikachu edition look very nice.
I currently have a Bayer (aka red lense) Defy (MB525)
stock android 2.2.2 on 2.6.32.9 kernel.
Systemversion: Version.34.164.3.MB525.Retail.en.FR.
Build number: 3.4.2-164
Which means I have a Froyo/Defy/'CM7' Kernel
CM7 and MIUI(GB) are all meant to be flashed on this Froyo/Defy/CM7 kernel, am I correct?
I find the '(GB)' with MIUI rather confusing, it's android 2.3.x but it's running Froyo kernel/Defy/CM7 kernel and not a GB/Defy+/CM9 kernel.
Now, the flashing
If I decide to flash a custom ROM: CM7.2 or a version of (GB) MIUI:
Can I just flash MIUI or CM7.2 RC1 on my current build or do I need to flash CEE or Nordic 2.2.2 first? I prefer not to lose my downgradeability.
I assume a flash from my current build to CEE or Nordic via RSDlite will result in an efuse so I can't flash my full 34.164.3.MB525.Retail.en.FR SBF anymore, or am I mistaken?
I currently have a full SBF of my original stock ROM, just in case.
Kind Regards, Config.
configuration said:
Hello all,
I'm posting this thread because I'm getting a little confused after all this reading. Basically, I just need some confirmations.
Lately I've been reading a lot on CM7 and CM9 but now I'm also starting to get interested in MIUI.
I've come across:
WIUI
MIUI Pikachu edition
MIUIandroid.com
Motorola Defy MIUI.us
I underlined my 4 questions for your convenience.
So I have some Questions on Custom ROMS
As you can see, I've looked for an official MIUI build for the Defy but I can't seem to find an official MIUI build. These listed above are all 'edited' by someone.
Could someone explain what i'm (probably) overlooking? Is there an official MIUI?
At the moment WIUI and Pikachu edition look very nice.
I currently have a Bayer (aka red lense) Defy (MB525)
stock android 2.2.2 on 2.6.32.9 kernel.
Systemversion: Version.34.164.3.MB525.Retail.en.FR.
Build number: 3.4.2-164
Which means I have a Froyo/Defy/'CM7' Kernel
CM7 and MIUI(GB) are all meant to be flashed on this Froyo/Defy/CM7 kernel, am I correct?
I find the '(GB)' with MIUI rather confusing, it's android 2.3.x but it's running Froyo kernel/Defy/CM7 kernel and not a GB/Defy+/CM9 kernel.
Now, the flashing
If I decide to flash a custom ROM: CM7.2 or a version of (GB) MIUI:
Can I just flash MIUI or CM7.2 RC1 on my current build or do I need to flash CEE or Nordic 2.2.2 first? I prefer not to lose my downgradeability.
I assume a flash from my current build to CEE or Nordic via RSDlite will result in an efuse so I can't flash my full 34.164.3.MB525.Retail.en.FR SBF anymore, or am I mistaken?
I currently have a full SBF of my original stock ROM, just in case.
Kind Regards, Config.
Click to expand...
Click to collapse
I have a Defy with bayer camera module, all I did for installing custom roms was root, install 2nd init, reboot to boot loader and wipe all data/cache (this is the first step in any of the mentioned ROMs, but please read the respective step-by-step tutorials in case I missed something), and then flashed the desired CM or CM-based (like MIUI) rom
The defy versions all basically run over froyo kernel, as it's the last official kernel released for the device (GB kernels are either leaked or belong to the defy+) , I never flashed a newer one and have tested quite a few MIUI and CM versions, including:
MIUI.us (oficial US MIUI adaptation team)
MIUIandroid.com (British team)
WIUI (Wajk's multilanguage version, and also has an ICS test version, that I also tried)
CM7.1 and Epsylon3's CM9 for Defy (in beta, but more stable than WIUI's ICS for Defy)
I don't actually know if flashing a newer kernel would be any use for these roms, I know defy and defy+ (different kernels) roms are not interchangeable, so I wouln't bother with it unless you are flashing a full sbf rom (in which case I have no experience with)
Persechini said:
TEXT
Click to expand...
Click to collapse
Thanks,
If I may ask, What ROM would you personally recommend?
Does anyone know the answer on my 2 last questions?
Config
From the ones I've used for a while, I suggest the official MIUI (gingerbread) if you wan't to be safe and CM9 if you want some ICS sweetness and feel good about dealing with the perks of a beta release. Once we finally have an official (or at least a stable/less buggy alternative) version of ICS MIUI for defy, I'd go with that, definitely
Persechini said:
From the ones I've used for a while, I suggest the official MIUI (gingerbread) if you wan't to be safe and CM9 if you want some ICS sweetness and feel good about dealing with the perks of a beta release. Once we finally have an official (or at least a stable/less buggy alternative) version of ICS MIUI for defy, I'd go with that, definitely
Click to expand...
Click to collapse
With official MIUI, do you mean the US version or the British?
For what i know, official miui is from chinese site miui.com. All others have some modification. More o less, all of them came frome miui's official releases. In my case, wiui is the most stable i been using since long time ago. I'm waiting for stable ics miui too cause there aren't an official rom from miui.com for defy. And the reason for that is because cm9 it's still in beta, and miui is based on cm project. All v4 around for defy are just port from others device's roms and have a lot of bugs, especially mobile data. As we know, motorola made our defy whit a locked bootloader whit froyo kernel in it. For that reason is more easy make a rom froyo kernel based. But isn't the unique option. there's a rom maded by walter 79 whit gb kernel that have excellent results, especially In battery life. Cm9 whit gb kernel too.
One more thing: miui (not v4) and cm7, are both android 2.3.x
Enviado desde mi MB525 usando Tapatalk
configuration said:
With official MIUI, do you mean the US version or the British?
Click to expand...
Click to collapse
The really official one is the chinese, the others are, as ldiomedi said, translation/adaptation teams. Some apps may be added or removed, but usually nothing you would notice. I settled using the british version because the phone numbers where formatted the same way as in Brasil ((xx)xxxx xxxx) and the brazillian team was lagging behind updates. WIUI gathers language options, but I don't know about other adaptations.
So if I'm correct:
If I would like to use MIUIandroid I have to get the newest build here, the MIUI.US over here and WIUI just at the forums.
My SD card is getting a bit small, it's only 2gig.
So before leaving my stock ROM I would like to switch it.
Are there any extra steps I should do because of the SD-card switching?
You don't need to keep the rom in the sd after installing it, use each one a bit to see which you like better. Install the definite one and then delete the roms from the sd card, you can always redownload if you want to change again latter.
I know I don't have to keep those files on my SD-card.
It's just that 2gb is getting too small to store some photos and files.
I would go for the GB WIUI rom as it has both nl and fr translations. I tried it in the past and the translations were good. It is also optimized for the defy. The others handle many different devices.
labsin said:
I would go for the GB WIUI rom as it has both nl and fr translations. I tried it in the past and the translations were good. It is also optimized for the defy. The others handle many different devices.
Click to expand...
Click to collapse
Nice, I'll try WIUI I guess.
Do you know the answer on the following questions?
configuration said:
If I decide to flash a custom ROM: CM7.2 or a version of (GB) MIUI:
Can I just flash MIUI or CM7.2 RC1 on my current build or do I need to flash CEE or Nordic 2.2.2 first? I prefer not to lose my downgradeability.
I assume a flash from my current build to CEE or Nordic via RSDlite will result in an efuse so I can't flash my full 34.164.3.MB525.Retail.en.FR SBF anymore, or am I mistaken?
I currently have a full SBF of my original stock ROM, just in case.
Kind Regards, Config.
Click to expand...
Click to collapse
A full SBF with a nandroid backup should do for an 'insurance' I hope.
Changning from cm7.2 to miuiandroid gb rom
Hai memebers,
I want to flash miuiandroid GB rom on my Motorola defy.
Currently i m on CM 7.2 .
Please tel me the correct steps to flash the new rom??
Im confused as almost every post say how to update from stock rom.!

CyanogenMod 7.2 RC2

FYI, the newest RC was built by CM last week. Didn't see a thread, so I figured I would make one. Here's the link: http://download.cyanogenmod.com/?device=desirec
I don't own an Eris, but it was my first Android phone so I try to follow. I'm curious to know if this will work with the .35 beta kernel. Also, I know Shed had made some adjustment to CM (a la GSB) for a better experience. What works? What's glitched? Can some of CondemnedSoul and Shed's fixes be applied?

Cyanogenmod 10.2 Kernel, which version?

Hi all,
I'm testing the CM10.2 nighties on my Razr M from two weeks. Everything seems stable but I want to try it with the SmartassV2 governor that the CM kernel is missing. I started searching for alternative kernels (like Aaaagh's one) and I noticed that the actual CM10.2 kernel is v.3.0.96: wasn't Android 4.3 supposed to have the 3.4.62 version instead? If so, why Cyanogemod is stuck with th old 3.0.96 version? I've searched for answers but I've find none...
Is it possible that every CM10.2 build has the old kernel, or is this happening only with the Razr M build?
Maybe I'm just missing somenthing...
j27h said:
Hi all,
I'm testing the CM10.2 nighties on my Razr M from two weeks. Everything seems stable but I want to try it with the SmartassV2 governor that the CM kernel is missing. I started searching for alternative kernels (like Aaaagh's one) and I noticed that the actual CM10.2 kernel is v.3.0.96: wasn't Android 4.3 supposed to have the 3.4.62 version instead? If so, why Cyanogemod is stuck with th old 3.0.96 version? I've searched for answers but I've find none...
Is it possible that every CM10.2 build has the old kernel, or is this happening only with the Razr M build?
Maybe I'm just missing somenthing...
Click to expand...
Click to collapse
3.4 kernel for MSM8960 isn't quite available yet.
Hopefully Moto will update to 3.4 if we ever receive official 4.2 (or 4.3)
You can contribute and follow the progress (dev wise) at http://forum.xda-developers.com/showthread.php?t=2243410 and http://www.droidrzr.com/index.php/t...lopment-0610-android-booting-firmware-issues/
Ok, everything isclear now! Thanks for the quick response!
Basically we've two options:
1) use the 3.0 kernel with backported 3.4 funcions (the one integrated in the CM builds)
2) use a 3.4 kernel (like Aaaargh's or others) non totally adapted to our device
And all this because we're still stuck with Android 4.1.2 thanks to Motorola/Google/Verizon...
At this point, I think te safest thing is to keep using the 3.0 kernel... Apart for the new governors/schedulers, why soul I prefer a 3.4 kernel (maybe this is a silly question too...)? Are they usable/stable even if they're not exactly matching our device?

[Q] Nightlies build logs availability?

Hi,
I'm trying to build OmniRom from sources for the N7000, and I got a complete-but-not-working (not bootable, probably without kernel) zip. Since the nightly builds are (correct me if I'm wrong) automated, I was wondering if it could be possible to download the build logs, to compare them with mines.

Categories

Resources