[ROM] CyanogenMod 10 Nightly Builds for Nook Color

Search This thread
By:
Advanced…
bornagainpenguin

bornagainpenguin

Senior Member
Oct 22, 2010
379
71
bcvictory said:
Works great! Comparable to my N7 sometimes. Just got to get the SOD's worked out. Any tips on reducing them?

Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse

Would like to second this request for tips on reducing SOD, since I seem to be encountering them more and more lately.

Also are there any apps you do not recommend installing in CM10? I seem to recall a post in the development thread saying that the undervolting features provided by Nook Tweaks has been rolled into the CM9 settings -- anything else like this we should be aware of?

Thanks for the work you do!

Sent from my NookColor using Tapatalk 2
 
eyeballer

eyeballer

Retired Recognized Developer
Jun 24, 2010
1,262
3,347
teamw.in
narta said:
GREAT WORK guys!!!

On another note, will this be the same thing as my own builds from cm source plus fattire's local manifest changes?

Once again, respect!
Click to expand...
Click to collapse

Yes, it's built from the same sources that you are all using :)

Although, it might be nice for the builders to (temporarily) rest their CPUs and test this common build so it would help to isolate any issues.


bornagainpenguin said:
Would like to second this request for tips on reducing SOD, since I seem to be encountering them more and more lately.

Also are there any apps you do not recommend installing in CM10? I seem to recall a post in the development thread saying that the undervolting features provided by Nook Tweaks has been rolled into the CM9 settings -- anything else like this we should be aware of?

Thanks for the work you do!

Sent from my NookColor using Tapatalk 2
Click to expand...
Click to collapse

We're trying to identify if there's anything different about the people getting SODs. It clearly does not affect everyone (most of us don't have them). Do you know which touchscreen you have?

Do an 'adb shell dmesg' then search the text for 'ft5x06' - if it's found then you have the newer one and that may be linked to the SOD (the nookiedev team all have the older cyttsp touchscreen). We need others who have the SOD to also confirm.
 
Last edited:
  • Like
Reactions: diajohn and runningslow
That Baker Guy

That Baker Guy

Senior Member
Dec 11, 2011
260
32
Tobie Town
eyeballer said:
Yes, it's built from the same sources that you are all using :)

Although, it might be nice for the builders to (temporarily) rest their CPUs and test this common build so it would help to isolate any issues.




We're trying to identify if there's anything different about the people getting SODs. It clearly does not affect everyone (most of us don't have them). Do you know which touchscreen you have?

Do an 'adb shell dmesg' then search the text for 'ft5x06' - if it's found then you have the newer one and that may be linked to the SOD (the nookiedev team all have the older cyttsp touchscreen). We need others who have the SOD to also confirm.
Click to expand...
Click to collapse

it appears i have both displays? im kinda confused here. also i havent had any sod yet. the only thing i can maybe pin point about the rom is that you guys should include full tablet mode. On my Kindle Fire cm10 i have the option for that, or partial tablet mode. that might be something that you guys look into once you get all the main things worked out.

<4>cyttsp::found BL, Overriding maxx & maxy
<6>cyttsp_initialize:cyttsp-i2c: Register input device
<6>input: cyttsp-i2c as /devices/platform/omap/omap_i2c.2/i2c-2/2-0022/input/input2
<6>cyttsp_initialize:Setting up interrupt 259
<6>cyttsp_initialize:cyttsp_initialize: Create sysfs_group successfully!
<4>cyttsp:Start Probe PASS
<6>ft5x06_init() - FT I2C Touchscreen Driver (Built Oct 10 2012 @ 01:24:32)
<3>can't get ft5x06 xreset GPIO
<6>cyttsp_power_on:BL101: f=00 s=11 err=D0 bl=010B bld=010B R=16
<6>cyttsp_power_on:BL102: tver=1100 a_id=AA1D aver=0006
<6>cyttsp_power_on:BL103
 
  • Like
Reactions: SGH-i200
B

boomn

Senior Member
Feb 2, 2011
275
83
That Baker Guy said:
it appears i have both displays? im kinda confused here. also i havent had any sod yet. the only thing i can maybe pin point about the rom is that you guys should include full tablet mode. On my Kindle Fire cm10 i have the option for that, or partial tablet mode. that might be something that you guys look into once you get all the main things worked out.

<4>cyttsp::found BL, Overriding maxx & maxy
<6>cyttsp_initialize:cyttsp-i2c: Register input device
<6>input: cyttsp-i2c as /devices/platform/omap/omap_i2c.2/i2c-2/2-0022/input/input2
<6>cyttsp_initialize:Setting up interrupt 259
<6>cyttsp_initialize:cyttsp_initialize: Create sysfs_group successfully!
<4>cyttsp:Start Probe PASS
<6>ft5x06_init() - FT I2C Touchscreen Driver (Built Oct 10 2012 @ 01:24:32)
<3>can't get ft5x06 xreset GPIO
<6>cyttsp_power_on:BL101: f=00 s=11 err=D0 bl=010B bld=010B R=16
<6>cyttsp_power_on:BL102: tver=1100 a_id=AA1D aver=0006
<6>cyttsp_power_on:BL103
Click to expand...
Click to collapse

Looks like you have the cyttsp. The kernel has drivers for both and probes for both, but it fails to find the right connection for the ft5x06 device whereas the cyttsp passes the probe and is later powered on
 
That Baker Guy

That Baker Guy

Senior Member
Dec 11, 2011
260
32
Tobie Town
boomn said:
Looks like you have the cyttsp. The kernel has drivers for both and probes for both, but it fails to find the right connection for the ft5x06 device whereas the cyttsp passes the probe and is later powered on
Click to expand...
Click to collapse

ahh thanks for clarifying that for me. this explains why i dont get sod! sweet...

EDIT: possible sod. screen backlight comes on, but no lockscreen show.
 
Last edited:
D

davidr415

Senior Member
Feb 16, 2011
132
26
FWIW... my "N" button wakes from sleep (after about 7-8 min) from SD card install.. I'll try for longer period..

Really nice job on the ROM.. Thanks
 
  • Like
Reactions: krylon360
D

davidr415

Senior Member
Feb 16, 2011
132
26
That may be true, but was not my case..

I did test further, however. As long as wi-fi was still on (Default time-out is 15 min), the "N" button seems to wake it up. After wi-fi cuts off, "N" button doesn't do it.. you have to hit the power button.
 
N

no_cannabis

Senior Member
Jun 6, 2009
121
23
Toronto
I am yet to experience a single SOD. I installed all my apps, checked SU with Titanium, launched and authorized all the Google stuff (plus, currents, etc.), but have not tried a game yet. No problems whatsoever.
Here are my notes:
"n" wakes it up, when nook is connected to USB power, even a PC;
wallpaper won't scroll, even with the setting turned on.

Guys, the work you've done is just stunningly amazing!!! At this stage, CM10 with no OpenGL works as fast, as CM9 with OpenGL. Sweet!

---------- Post added at 01:32 PM ---------- Previous post was at 01:15 PM ----------
davidr415 said:
That may be true, but was not my case..

I did test further, however. As long as wi-fi was still on (Default time-out is 15 min), the "N" button seems to wake it up. After wi-fi cuts off, "N" button doesn't do it.. you have to hit the power button.
Click to expand...
Click to collapse
Absolutely unexplainable. I turned off Wifi, and connected to USB power - no wakie. Disconnected power - "n" works again...

Oh, and I just tried good old GLWG - works just as on CM9 with OpenGL, even faster when it comes to scrolling.

---------- Post added at 01:50 PM ---------- Previous post was at 01:32 PM ----------

Tried playing a video file, an episode of 24 (MPEG4, 848x478, AAC 96kbit/s). Native video player refused to play it, but MX with ARM7NEON codec played it just fine using HW+ decoder.
I'd like to state that this looks like something I can use as a daily driver, despite alpha1 code.

---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------

Oh, and just hit the no-plugging-USB-while-sleeping problem. That's gonna take some getting used to.
 
R

rampart51

Senior Member
Feb 2, 2011
172
18
Congrats to all for putting this together.

I installed on an SD card without issues. The screen touch response is about the same as CM9 but CM10 is running and running well.

Thanks again!

NO SOD's yet.
 
dparrothead1

dparrothead1

Senior Member
Mar 13, 2011
2,570
1,801
Florida
That Baker Guy said:
ahh thanks for clarifying that for me. this explains why i dont get sod! sweet...

EDIT: possible sod. screen backlight comes on, but no lockscreen show.
Click to expand...
Click to collapse

I was having the same problem. Went back in wipe cache/dalvik, reflashed ROM and now I can wake it with both the power button or volume rocker.

Fantastic ROM on this device....I haven't picked up my N7 in almost 5 hours!!!!:thumbup::)

Thank you so very much for all your hard work on this device!!!
Sent from my NookColor using xda app-developers app
 
  • Like
Reactions: UpstateScott
dparrothead1

dparrothead1

Senior Member
Mar 13, 2011
2,570
1,801
Florida
Got Jelly Bean???

Sent from my NookColor using xda app-developers app
 

Attachments

  • uploadfromtaptalk1350501615365.jpg
    uploadfromtaptalk1350501615365.jpg
    51.7 KB · Views: 822
pckoloji

pckoloji

Senior Member
Oct 10, 2010
176
26
warsaw
www.pckoloji.com
installed w.o. any problem.
working fine and no sod until now.
google now was crashing at the beginning but after the update no more FC.
n key does not wake but for me it is not a big problem.
fantastic!
 
H

_highway_

Senior Member
May 15, 2011
76
3
how do you wipe the system? is that going into format ---> system? then you wipe data in addition to formatting the system?
 
Weudel

Weudel

Retired Forum Moderator
Jul 18, 2010
588
97
Downloading.... stoked

Sent from my NookColor using xda premium
 
You must log in or register to reply here.

Similar threads

D
[DEV] CM11 Work-In-Progress
Replies
4K
Views
2M
owim
owim
S
[DISCONTINUED] CM9/ICS Nightly Builds
Replies
2K
Views
663K
cammykool
cammykool
mrg666
[ROM+Kernel] MiRaGe - Custom CM7.2 for Nook Color - 07272013
Replies
2K
Views
758K
Z
zagzag99
eyeballer
[ROM] CyanogenMod 10.1 Nightly Builds for NookColor [5/3/13]
Replies
615
Views
235K
P
pmgnet
S
[ROM] CyanogenMod 11 Nightly Builds for Nook Color
Replies
400
Views
221K
T
Taken Aback

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 363
    fattire
    fattire
    Update April 22, 2013: Great news!

    Yesterday, April 21, 2013, the CyanogenMod build system built its most recent (and possibly final) CyanogenMod 10 nightly for Nook Color. Why? Because the 10.1 builds are here! There's a whole new thread about it, so check it out.

    If you'd like to try the (now legacy) April 21 build of 10.0, it is here:

    cm-10-20130421-NIGHTLY-encore.zip
    md5: d6d6c7c6229bae992729db615984f2b8

    Otherwise, if you're interested in stepping up to CyanogenMod 10.1, we'll see you over on the new thread!




    ____________________________________________________________________________________________________
    LEGACY STUFF -- STUFF BELOW THIS IS OLD! CHECK OUT THE LINK/INFO ABOVE
    ____________________________________________________________________________________________________

    NookieDevs 2012 Are Engorged with Pride While We Announce

    CM10 Nightlies
    for Nook Color (aka “encore”)
    "CM10 for Nook Now Belongs To the Ages" Edition​

    WE'VE MOVED TO OFFICIAL CM 10 NIGHTLIES!!!!

    That's right. Starting Nov 14, 2012, the official CyanogenMod servers are building a new fresh version of CM10 for encore every evening. This is a milestone in the development. Updates can also now be done automatically using the CyanogenMod Updater in the Settings.

    Let's get to the good stuff:

    Nightly Changes (starting 12/14/12)

    * Here's what's new!

    WHAT STILL HAS ISSUES (?)

    • rare reports of high pitched noise on some hardware versions when coming out of sleep (but not confirmed)
    • adb w/usb seems to slow down when CPU is under load. To investigate, but not a show stopper.
    • Overclocking is not in yet
    • OTG not in yet
    • You tell us!

    ---------
    older
    ---------
    B5 Changes (11/12/12)

    • fixed the 600 mhz default for real this time
    • SmartReflex added (better battery life?)
    • way better touchscreen responsiveness (all salute Keyodi!)
    • kernel repository has been renamed
    • Updated to latest source of upstream CM10
    • security hardening


    B4 Changes (11/8/12)

    • Updated to today's CM 10 upstream source
    • cpu clock defaults to 1ghz
    • a2dp (hopefully) fixed

    B3 Changes: (11/6/12)

    • Updated to today's CM 10 upstream source
    • Updated wifi firmware to version that seems to fix networking and power issues
    • N-key wake is back
    • Fixed double-tap to wake device
    • power_hal changes
    • software menu key was fixed
    • possible SOD fixes for those having issues
    • More love was given.

    B2 Changes (10/31/12):

    • "Sleep of death" on ES1.2 models- hopefully fixed
    • i2c commit that caused the black screen on boot has been pulled
    • the "n" to wake fix that caused ES1.2 SOD is gone too... sorry, but at least it fixed the black screen on boot issue
    • zram compressed memory added to kernel (see settings/performance)
    • bfq IO scheduler enabled in kernel (see settings/performance)

    B1 Changes:

    • Based on latest CM10 source code as of 10/30/12
    • Netflix - works!
    • YouTube HD- works!
    • Passes Compatibility Test Suite for hardware (except for camera/GPS- wonder why?!)
    • Fixed "sleep of death" (SOD) on newer OMAP3 hardware model (ES1.1)
    • Charger detection issue is fixed
    • No sound on resume fixed (we think)
    • Updated PVR version
    • "N" button is now detected always see b2-- some models will need to use power button for now to wake the device
    • Fix to kernel to provide serial number
    • OpenGL now built in and works
    • CM "expanded desktop" feature turned on

    Some notes:

    Don't try to play ridiculously high 1080P h.264 video on this thing unless you like stuttering. There's a practical limit to what hardware from late 2010 can do.

    That's it! Enjoy (as always, at your own risk and discretion)... and let us know what you think!

    The NookieDev Team
    :cyclops::cyclops::cyclops:


    ________________________________________

    UPDATE 10/19: SURVEY TIME!!!! Turns out there are a few models of Nook Color that need to be supported. Can you help debug?

    Fill out this survey     to help narrow down issues. (More info here)
    ________________________________________

    WHAT IS THIS ANNOUNCEMENT?

    For a little more than a year now, the NookieDev team (comprised of a floating band of scoundrels and miscreants on XDA, Rootzwiki, Twitter, and other obscure corners of the Internet) has been laboring day and night to bring CyanogenMod 10 (based on Google’s Jellybean Android 4.1.2) to the Nook Color (aka “encore”) devices.

    The port has involved overcoming numerous technical hurdles, the least of which was the need to move from a 2.6.32 kernel to a shiny new 3.0.8 kernel. Drivers were modified and (re)-written, large chunks of code from various kernels were backported, forward-ported bits were also shoehorned into place -- all using the open source 3.0.8 OMAP3 code base from Texas Instruments.

    A new bootloader menu has also been written, then ported to the Nook Tablet. Improvements from the Tablet were then ported back to the Nook Color version, and over several iterations, the “Cyanoboot” bootloader got better and better. It’s pretty cool now, we think.

    Over this past year, instructions for building from scratch were posted, and hundreds of users delved into the dark art of loading virtual machines, installing toolchains, downloading source, and assembling the new OS themselves. This experiment resulted in a new wave of contributors and testers, and we are grateful for their participation as well. The development forum has been full of reports of people building and testing CM10 themselves, but we have asked (and they have respected) that no binaries be posted so that developers, potential developers, and those-who-just-want-to-learn can be the first wave of "guinea pigs".

    That brings us to today. Just in time for the BigAndroidBBQ, a gathering of Android developers and enthusiasts in Texas, we are pleased to announce that nightly builds are available -- at no charge -- for testing. If we may say so ourselves, this release is a triumph of the power of open source, collaboration, teamwork, and sharing knowledge for the betterment of everyone. If you’ve used CM7 -- or even one of the test versions of ICS -- on the encore device, you may want to back up your systems and give the nightly builds a try.


    WARNING/DISCLAIMER

    Understand that there are likely to be bugs, both known and unknown, and that all appropriate experimental-software disclaimers apply, including the fact that by using or attempting to use this software, you assume all risk for fooling with your hardware. We will not be held responsible for any potential loss of data, destruction of hardware, removal or disappearance of limbs, life, or coins in the couch. We do not claim this software is fit for any purpose, etc. Beware of Dragons.

    This said, we do feel that the our work is finally “good enough” for interested people with a tolerance for risk to get their hands on.


    WHAT IS CYANOGENMOD?

    It's an "alternative firmware" that can be used in place of the regular "stock" operating system. See the Wikipedia entry for more info.


    IS THIS AN OFFICIAL RELEASE OF CYANOGENMOD?

    Starting with the nightlies, yes it is.


    WHAT’S DIFFERENT IN THIS BUILD FROM CM7?

    It’s anticipated that some users may have not updated since CM7. So here’s a non-exhaustive list of changes:

    • based on recent CM10 version of Google Android 4.1.2 ("Jellybean")
    • based on the 3.0.8+ OMAP3 kernel
    • over-clocking (OC) above 1ghz is disabled for now. This is so we can rule out OC as causing bugs that may be reported. The 3.0.8 kernel is still in development, and OC will be available again later.
    • non-official CM10 source code has been moved to the NookieDevs account on the Github.com web site. (To get CM10 to work on the Nook Color,minor modifications were made to official CM10 source. So until those changes are adopted “upstream” into the CM10 source, we have made them available on the NookieDevs repository)


    WHAT DOES WORK?

    Pretty much everything, except where mentioned below, and where we just haven't noticed yet :)


    WHAT DOESN’T YET WORK?

    • See above announcement


    HOW DO I INSTALL THIS ON MY EMMC (INTERNAL STORAGE)?

    These instructions assume you are familiar with replacing the firmware on your Nook Color and understand what a “recovery image”, such as ClockworkMod or TWRP2, is used for. If you are unfamiliar with these concepts, or have never replaced the stock firmware, don’t worry. Instructions and additional help are available across the Internet. A simple Google search should help you.

    Note: We *STRONGLY* recommend a full data backup and factory reset when installing CM10, no matter what rom you were running previously. In fact, please do not post a bug report unless you did a full wipe.

    To install CM10:

    1. (recommended) Boot into your recovery and make a nandroid backup of your current rom and data. This way anything goes wrong, you can always recover your original installation.
    2. Download the latest CM10 nightly .zip (and optionally the google apps from another source, as we are not distributing this software) and place it on your SD card.
    3. Again using your preferred recovery image, do a full wipe of the system as well as a factory reset (data wipe).
    4. Use the recovery to install the .zip (or .zips if you are also installing the Google apps).
    5. Reboot
    6. Enjoy!


    WHAT ABOUT A "SD-BOOTABLE" VERSION?

    Good news! You can make your very own free bootable CM10 SD card. It’s not hard, and we recommend you get a blank SD card and give it a shot before paying anyone else for a “pre-made” SD card. (If you don’t have a blank SD card, they can be found very inexpensively at most electronics retailers.) To do so, you will need leapinlar’s SD Installer here. It is a modification of verygreen’s famous SD installer, which was used with CM7.

    This program will help you turn a CM10 .zip file into an image that can be flashed onto an external SD card.

    Note: We strongly advise that you DO NOT overpay anyone for a pre-made SD card. If you have difficulty with making your own SD card, there are plenty of people online who can and will help you. There are unfortunately some unscrupulous people (aka “parasites”) taking advantage of their customers (aka “victims”) who don’t realize how easy it is to make their own SDs. Be wary of hucksters overcharging for this “service”.

    We also ask that you please keep discussion of SD-card related install issues in the SD Installer thread referenced above.


    WHAT DOES THE “EMMC 01” MEAN IN CYANOBOOT WHEN I START UP?

    Note: There is a special forum thread dedicated to CyanoBoot.

    When you first boot, you’ll see an “EMMC” or “SD” in the top corner, depending on which you’ve started from. Then “01” refers to the “bootcount”, which is an internal counter that is cleared back to 0 when the boot is successful.

    (You can usually ignore the “01”.)


    WHY ARE SOME OPTIONS GREYED-OUT IN THE BOOT MENU?

    CyanoBoot should auto-detect which forms of boot are possible (ie, you can’t boot off SD card if there’s no SD card installed!) and grey them out for you.


    HOW DO I BUILD CM10 MYSELF FROM SOURCE?

    The build document for cm10 has been updated to reflect the newest instructions for building yourself. The build document is now a bit old and will be replaced soon... stay tuned.

    Please keep all questions about building and developing on the [DEV] thread. This thread you are reading is intended for those who are using the nightly builds.


    AND WHY WOULD I WANT TO BUILD MYSELF EXACTLY?

    To quote myself:

    • You never, ever have to wait for a nightly
    • You can add or remove as-yet uncommitted features with ease.
    • You learn how Android works under the hood
    • You learn how to use Linux
    • You'll learn how to use git
    • You may, even accidentally, pick up a little C, Java, C++, and learn about the build system.
    • You can personalize Android-- make your own tweaks, replace kernels, modules, graphics, add or remove projects, overclock, underclock etc. In other words, you have control over every aspect of your device's functionality. Your build is custom to you.
    • You can audit the code for potential security issues such as back doors or trojans (as opposed to just trusting a random person who posts a build). Since CM10 source is open, you can examine every commit, and there are many eyes looking at the code. (does not apply to proprietary blobs, but these are pulled from your device, so you have and are using them already)
    • You can contribute features/fixes back upstream
    • You can start ports to other as-yet-unsupported devices (start by copying folders from similar devices to devices/manufacturer/model)
    • You come to really understand that Android phones and tablets are full-fledged general-purpose computers just like laptops and desktops.
    • AAAAND....you get huge bragging rights

    The extent to which you delve into the above is entirely up to you. The walkthrough is just an introduction to that world. Some people will build once and never do it again... but others will start to tinker and make changes to their own build and want to share them with others, and soon some will start making contributions back to official CM10 upstream... or port to new devices... and by fixing bugs and all this... everyone benefits.

    Plus...

    • It's fun.

    (Here are some little bits that resulted from the nexus 7 thread quoted above.)



    I’M HAVING PROBLEMS! WHERE DO I POST PLEAS FOR HELP?

    You have many, many options for seeking help!

    See the Nook Color forum on xdaforums.com to ask the community questions, please be mindful to post in the appropriate forum. General jellybean discussion and user help should be in the USER thread in the general forum - not in the development forum. If you think you have found a bug that hasn’t been reported yet, then post that in this thread.

    You can also visit #nookcolor on IRC (freenode server) by clicking on:

    http://webchat.freenode.net?channels=nookcolor

    Additionally, you may find more information about the Nook Color at www.nookdevs.com as well as on Android-friendly blog sites such as liliputing, RevTV, and many more.


    HOW CAN I HELP DEBUG AN ISSUE I’M HAVING?

    Great! We hate it when people post “hey guys.. *this* doesn’t work” and go on their merry way. Where possible, we may try to reproduce the bug. But sometimes, we can’t.

    The best way to discuss an issue you are having is to include a “log cat”. A logcat is a special log that Android will give you using the “adb” program mentioned above that helps to determine what is going wrong and why. To include a logcat, simply download adb to your computer, connect your computer to the Nook Color with a USB cable, and then type “adb logcat” on your computer so that the log begins to scroll in the window. Copy and paste this log to a site such as pastebin.com, and post a link to the log when you are reporting the problem you are having.

    You can read more about logcat and how to get one in this thread.


    WHERE DO I SEND MY MONEY?!

    Every developer on this has their own motivation for participating in the project, but it’s pretty obvious money isn’t one of them. Some members of the team may have set up methods for making donations, but speaking overall, NookieDevs isn’t about money. It’s about the fun of hacking this amazingly versatile device.

    BIG NOTICE FOR YOU NOT TO MISS: As mentioned, one place to NOT send money is any company that is overcharging for this free port. Many of these companies are, to say the least, douchey. These parasitic businesses may gouge their customers for free software without making it abundantly clear that they can easily download and install it themselves. How these scamsters sleep at night, we can only speculate -- probably on a pillow stuffed with cash.


    WHO DO I THANK?

    Oooh boy, this is going to be a long list ... You can thank the "NookieDev" core folks, but you also need to thank the random people who stopped by, contributed some small thing, then disappeared. There’s also the developers that made CM7 possible (some of whom worked on CM10 too). Then there’s the forum moderators (inc. Divine Madcat, thanks!), upstream CM team, and their contributions on top of the Google code. Of course Google deserves big thanks, and so does Barnes and Noble and the subcontracted engineering team that made the NC, including the designers at Yves Beher’s fuseproject. Which certainly means we also owe Texas Instruments a huge debt of thanks, not only for making the OMAP devices, but for its world-class developer community support. And then there’s the people who developed the various languages, platforms, compilers, linkers, and coding practices that made Android possible... We can’t forget the Linux kernel coders... and it goes on and on. We’d like to give a special shout out to James Clerk Maxwell, who really doesn’t get enough credit in these “thanks” lists. Quick ups also go to Ada Lovelace, Alan Turing, Benjamin Franklin’s key maker, and the late Dennis Ritchie.

    All that said, here are the more-or-less core members of the team.

    fattire - @fat__tire on Twitter
    krylon360 - @krylon360 on Twitter
    eyeballer - @eye_baller on Twitter
    keyodi
    sluo

    Other people who have worked on related projects such as CM7 and CyanoBoot include dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, and many more.

    The above are in no particular order, and as we say -- massive, necessary contributions have come from every corner of the Internet. As the inventor of the Fig Newton reminds us-- we all stand on the shoulders of giants.


    I HAVE A NOOK TABLET (OR NOOK HD). WILL THIS STILL WORK?

    There is an experimental version of CM10 available for Nook Tablet available in another thread. If you have a newer Nook, do not expect an alternative rom any time soon. The newer Nooks are expected, like the new Kindles, to have locked bootloaders.


    IS THAT IT?

    Sure for now. Enjoy, and remember... if something screws up, don’t blame us!

    (check this thread again for updates)

    --------------------

    Want a nightly builds? Look here!




    Download (beta 5): cm-10-encore-b5-barelybuggy.zip
    MD5 Checksum: f22e826f637b57245250ca7aa9de147d

    Download (beta 4): cm-10-encore-b4-notsofullofbugs.zip
    MD5 Checksum: 45cd0b04c0f9c6bc4b3be684cebd4b22

    Download (beta 3): cm-10-encore-b3-stillsomebugs.zip
    MD5 Checksum: cd6dadefa2087a005b5d47e758e7cf59

    Download (beta 2): cm-10-b2-encore-fullofbugs.zip
    MD5 Checksum: 9f0c6ca00c72ca944c2193dab1501dc1

    (UPDATE: I appreciate the "thanks", but be sure to scroll down and thank the others too!)
    View
    193
    eyeballer
    eyeballer
    CM10 nightly mirror (get.cm seems to be having issues)
    http://techerrata.com/browse/cm/encore/nightly


    Please make sure you're using the correct gapps:
    Download gapps: http://techerrata.com/file/gapps/gapps-jb-20121011-signed.zip
    Mirror: http://goo.im/gapps

    By default with the current gapps picasa sync will not be an option, if you would like to sync your photos with picasa then you'll need to also flash this (after you flash the full gapps package): http://techerrata.com/file/gapps/gapps-jb-picasa-20121011-signed.zip
    View
    169
    krylon360
    krylon360
    Alpha1 Download
    Download Link
    http://techerrata.com/file/cm/encore/alpha/cm-10-a1-encore-fullofbugs.zip
    MD5
    d5345b886d9825ef7a8fd8a36f70acb2

    Local Manifest used to build Beta1.

    Code: 
    <?xml version="1.0" encoding="UTF-8"?>
    <manifest>
      <remote fetch="git://github.com/" name="gh" />
     
      <project name="NookieDevs/android_device_bn_encore" path="device/bn/encore" remote="gh" revision="jellybean" />
      <project name="NookieDevs/ti-omap-encore-kernel3" path="kernel/bn/encore" remote="gh" revision="encore-omap3-3" />
      <project name="eyeballer/proprietary_vendor_bn" path="vendor/bn" remote="gh" revision="jellybean" />
</manifest>
    View
    47
    krylon360
    krylon360
    READ!!!!!!

    I guess no one reads the OP, or through the thread anymore.

    N to Wake is not active. We took it out due to it was causing the SOD's on ES1.2 devices.

    Don't believe me?
    20 hrs, 26 min on battery so far. device wakes up just fine. and yes, I am on ES1.2; and up until b2, I couldn't even make it to work with my nook in my bag without it not coming back alive and I only live 15 min away.

    Menu key shows, but doesn't do anything. Read a couple of pages back please. I already fixed this and pushed the commit to github. Build if you want it fixed right now, or wait till the next release.

    1.1/1.2 OC. these options where taken out of Alpha builds. Now that we are in Beta, they will go back in.

    a lot of the SOD reports I am seeing on b2, aren't SOD's at all. Seeing a dim lit lock screen...guess what...means YOU DON'T HAVE AN SOD!.
    SOD = Sleep of Death. meaning the device wont wake up at all.

    BSOB = Black Screen on Boot was also fixed for b2. I never experienced it, however, our testers that did have it, haven't reported it since we released b2.

    I'm only seeing a hand full of "SOD" reports, and out of 120GB (sorry, that was just for 11/1; forgot to add in the 15GB that was downloaded on 10/31), so 135GB worth of downloads for B2, you'd think there would be A TON of true SOD reports if it was a real issue.

    So please, Stop reporting on the N key, Stop reporting on the OC, Stop reporting on Netflix Doesn't Work....READ THE OP. Install 1.8.1, not the one from the market.

    OTG HAS NOT BEEN ADDED YET. Stop reporting this as a bug. I said this a few pages back.

    there's probably more, but whatever. Not like anyone will read this post anyway.
    View
    30
    eyeballer
    eyeballer
    Beta 5 is up :)
    View

New posts