[ROM] CyanogenMod 10.1 Nightly Builds for NookColor [5/3/13]

Search This thread

warbrain1986

Member
Aug 9, 2012
31
1
Austin
Re: [ROM][ALPHA] CyanogenMod 10.1 Alpha for NookColor

Yes. Same as Cm10 as far as I can see

Sent from my One X using xda app-developers app
 
Last edited:

warbrain1986

Member
Aug 9, 2012
31
1
Austin
Re: [ROM][ALPHA] CyanogenMod 10.1 Alpha for NookColor

Yep Netflix is golden. Haven't checked out MX player yet though.

Sent from my One X using xda app-developers app
 

webyrd

Senior Member
May 4, 2011
223
104
Florida
Haven't tested it, but it should work just fine, please report back. If you hit a problem, just follow the gapps issue steps in post 2.

Go in to settings about tablet and press the build number 10 times. This is a 4.2 feature.

To get the performance and developer settings, go to Build Number in about tablet and tap it. A lot. As for the boot animation, that was reported in the OP, they're prbly fixing that. I haven't had the Quick Settings problem, can you get a logcat or dmesg? And the Picassa, is that for 4.1.2 only, or will it work with any version? I reccomend that you just flash and see what happens.

Thanks all, teach me to read not skim. The quick setting reboot has not happened again so can't provide logcat. As others have posted since, flashing the Picassa gapps does work fine.
 

Tschumi

Senior Member
Jul 4, 2010
150
31
Thessalonika
I dirty flashed this over the latest CM10 nightly (3/2) and so far I 'm not having any problems. With nova launcher and "conservative" governor there's not much lag and the overnight drain was at 1%. No reboots or noticeable bugs. I really like the quick settings that pop out when swiping at the right side of the screen.

In conclusion, thank you eyeballer, you 're a god amongst developers!
 

eyeballer

Retired Recognized Developer
Jun 24, 2010
1,262
3,347
teamw.in
I dirty flashed this over the latest CM10 nightly (3/2) and so far I 'm not having any problems. With nova launcher and "conservative" governor there's not much lag and the overnight drain was at 1%. No reboots or noticeable bugs. I really like the quick settings that pop out when swiping at the right side of the screen.

In conclusion, thank you eyeballer, you 're a god amongst developers!

No way I'm taking credit, whole team is awesome, really been fun to work with a great group of guys!


There is an updated TWRP 2.4.1.0 available at this link. Needs testers.

http://xdaforums.com/showpost.php?p=37554712&postcount=

Try it, you'll like it. Latest Android and latest TWRP, what's not to like.

OT for this thread but yes, please do test this, I haven't hit any issues, and there's some new features which may/may not interest people but I'd like to make it public. If you're wary of testing, make a backup with your current recovery and then install TWRP as altboot and backup/wipe/restore.

OK back on topic... :)
 

Malave

Senior Member
Sep 7, 2011
124
80
It's hard to believe this is an alpha. I have it running on an sdcard with no problems. Once again you guys pull off another miracle.
 

thejrcrafter2

Senior Member
Oct 26, 2012
137
35
25
Bethany, CT
Not quite. If you previously set up your repo for PA then you should re-init for building CM:

repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1

Then perform a sync and modify your your local_manifest.xml to include:

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="cm-10.1" />
      <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>

For now the device repo is still only on NookieDevs - the kernel is up to date on both CM's repo and NookieDevs so you can actually use either for building.

Wait, where is the local_manifest.xml file anyways?
 

jamesbra

Senior Member
Oct 2, 2010
387
71
Re: [ROM][ALPHA] CyanogenMod 10.1 Alpha for NookColor

So I installed this on internal and my Wi-Fi doesn't work. It just hangs on turning on. Bluetooth works fine. Any ideas or where to look for logs that could help? Wifi does work on cm7

Sent from my Nexus 7 using Tapatalk HD
 

thejrcrafter2

Senior Member
Oct 26, 2012
137
35
25
Bethany, CT
So I installed this on internal and my Wi-Fi doesn't work. It just hangs on turning on. Bluetooth works fine. Any ideas or where to look for logs that could help? Wifi does work on cm7

Sent from my Nexus 7 using Tapatalk HD

Connect the Nook to your PC via USB, and install the Android SDK at http://developer.android.com/sdk/index.html. "cd" into your platform-tools folder in the SDK, and run "adb logcat". Post the output here.
 
  • Like
Reactions: jamesbra

jamesbra

Senior Member
Oct 2, 2010
387
71
Re: [ROM][ALPHA] CyanogenMod 10.1 Alpha for NookColor

E/wpa_supplicant( 1743): Could not set interface wlan0 flags (UP): Invalid argument
E/wpa_supplicant( 1743): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 1743): wlan0: Failed to initialize driver interface
E/NetdConnector( 1663): NDC Command {9 interface setthrottle rmnet0 -1 -1} took too long (6127ms)
....
D/CommandListener( 1244): Setting iface cfg
D/CommandListener( 1244): Trying to bring down wlan0
I/wpa_supplicant( 2253): Successfully initialized wpa_supplicant
I/wpa_supplicant( 2253): rfkill: Cannot open RFKILL control device
...
E/wpa_supplicant( 2253): Could not set interface wlan0 flags (UP): Invalid argument
E/wpa_supplicant( 2253): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2253): wlan0: Failed to initialize driver interface
....
/WifiHW ( 1663): Unable to open connection to supplicant on "wlan0": No such file or directory
I/wpa_supplicant( 2306): Successfully initialized wpa_supplicant
I/wpa_supplicant( 2306): rfkill: Cannot open RFKILL control device
...
wpa_supplicant( 2326): Could not set interface wlan0 flags (UP): Invalid argument
E/wpa_supplicant( 2326): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2326): wlan0: Failed to initialize driver interface

Sent from my Nexus 7 using Tapatalk HD

Link to log cat http://pastebin.com/Xspa1U6Y
 
Last edited:

lepa71

Senior Member
Aug 25, 2010
1,220
153
Minneapolis
Did you try full wipe and reinstall it and gapps?

E/wpa_supplicant( 1743): Could not set interface wlan0 flags (UP): Invalid argument
E/wpa_supplicant( 1743): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 1743): wlan0: Failed to initialize driver interface
E/NetdConnector( 1663): NDC Command {9 interface setthrottle rmnet0 -1 -1} took too long (6127ms)
....
D/CommandListener( 1244): Setting iface cfg
D/CommandListener( 1244): Trying to bring down wlan0
I/wpa_supplicant( 2253): Successfully initialized wpa_supplicant
I/wpa_supplicant( 2253): rfkill: Cannot open RFKILL control device
...
E/wpa_supplicant( 2253): Could not set interface wlan0 flags (UP): Invalid argument
E/wpa_supplicant( 2253): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2253): wlan0: Failed to initialize driver interface
....
/WifiHW ( 1663): Unable to open connection to supplicant on "wlan0": No such file or directory
I/wpa_supplicant( 2306): Successfully initialized wpa_supplicant
I/wpa_supplicant( 2306): rfkill: Cannot open RFKILL control device
...
wpa_supplicant( 2326): Could not set interface wlan0 flags (UP): Invalid argument
E/wpa_supplicant( 2326): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2326): wlan0: Failed to initialize driver interface

Sent from my Nexus 7 using Tapatalk HD

Link to log cat http://pastebin.com/Xspa1U6Y
 
  • Like
Reactions: jamesbra

jamesbra

Senior Member
Oct 2, 2010
387
71
Re: [ROM][ALPHA] CyanogenMod 10.1 Alpha for NookColor

Did you try full wipe and reinstall it and gapps?

I did. No love

I'm going to try with the newest twrp. Maybe that will help?

Edit.

Although the new twrp is sweet. Still same errors

Sent from my Nexus 7 using Tapatalk HD
 
Last edited:

steven676

Senior Member
Nov 24, 2011
593
2,433
So I installed this on internal and my Wi-Fi doesn't work. It just hangs on turning on. Bluetooth works fine. Any ideas or where to look for logs that could help? Wifi does work on cm7

E/wpa_supplicant( 1743): Could not set interface wlan0 flags (UP): Invalid argument
E/wpa_supplicant( 1743): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 1743): wlan0: Failed to initialize driver interface
E/NetdConnector( 1663): NDC Command {9 interface setthrottle rmnet0 -1 -1} took too long (6127ms)
....
D/CommandListener( 1244): Setting iface cfg
D/CommandListener( 1244): Trying to bring down wlan0
I/wpa_supplicant( 2253): Successfully initialized wpa_supplicant
I/wpa_supplicant( 2253): rfkill: Cannot open RFKILL control device
...
E/wpa_supplicant( 2253): Could not set interface wlan0 flags (UP): Invalid argument
E/wpa_supplicant( 2253): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2253): wlan0: Failed to initialize driver interface
....
/WifiHW ( 1663): Unable to open connection to supplicant on "wlan0": No such file or directory
I/wpa_supplicant( 2306): Successfully initialized wpa_supplicant
I/wpa_supplicant( 2306): rfkill: Cannot open RFKILL control device
...
wpa_supplicant( 2326): Could not set interface wlan0 flags (UP): Invalid argument
E/wpa_supplicant( 2326): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 2326): wlan0: Failed to initialize driver interface

Can we also have dmesg output from when the system attempts to turn on wifi?

Also, does wifi work with a CM10 nightly?
 
  • Like
Reactions: jamesbra

jamesbra

Senior Member
Oct 2, 2010
387
71
Can we also have dmesg output from when the system attempts to turn on wifi?

Also, does wifi work with a CM10 nightly?

wifi doesnot work with cm10 nightly

looks relevant?
<4>------------[ cut here ]------------
<4>WARNING: at /mnt/ssd1/eyeballer/cm-10.1/hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/main.c:1414 wl12xx_queue_recovery_work+0x2c/0x80 [wl12xx]()
<4>Modules linked in: wl12xx_sdio wl12xx mac80211 cfg80211 compat [last unloaded: wl12xx_sdio]
<4>[<c0045788>] (unwind_backtrace+0x0/0xe0) from [<c00740e8>] (warn_slowpath_common+0x4c/0x64)
<4>[<c00740e8>] (warn_slowpath_common+0x4c/0x64) from [<c0074118>] (warn_slowpath_null+0x18/0x1c)
<4>[<c0074118>] (warn_slowpath_null+0x18/0x1c) from [<bf0c5138>] (wl12xx_queue_recovery_work+0x2c/0x80 [wl12xx])
<4>[<bf0c5138>] (wl12xx_queue_recovery_work+0x2c/0x80 [wl12xx]) from [<bf0c8428>] (wl1271_cmd_send+0x4c0/0x4f0 [wl12xx])
<4>[<bf0c8428>] (wl1271_cmd_send+0x4c0/0x4f0 [wl12xx]) from [<bf0c986c>] (wl1271_cmd_configure+0x68/0x90 [wl12xx])
<4>[<bf0c986c>] (wl1271_cmd_configure+0x68/0x90 [wl12xx]) from [<bf0d0464>] (wl1271_acx_event_mbox_mask+0x94/0xd0 [wl12xx])
<4>[<bf0d0464>] (wl1271_acx_event_mbox_mask+0x94/0xd0 [wl12xx]) from [<bf0cbc54>] (wl1271_event_unmask+0x10/0x18 [wl12xx])
<4>[<bf0cbc54>] (wl1271_event_unmask+0x10/0x18 [wl12xx]) from [<bf0d3f44>] (wl1271_boot+0x6f0/0x99c [wl12xx])
<4>[<bf0d3f44>] (wl1271_boot+0x6f0/0x99c [wl12xx]) from [<bf0c4e38>] (wl1271_op_add_interface+0x30c/0x548 [wl12xx])
<4>[<bf0c4e38>] (wl1271_op_add_interface+0x30c/0x548 [wl12xx]) from [<bf050c44>] (ieee80211_do_open+0x5b8/0xc7c [mac80211])
<4>[<bf050c44>] (ieee80211_do_open+0x5b8/0xc7c [mac80211]) from [<c044a97c>] (__dev_open+0x9c/0xf4)
<4>[<c044a97c>] (__dev_open+0x9c/0xf4) from [<c044ab9c>] (__dev_change_flags+0x8c/0x110)
<4>[<c044ab9c>] (__dev_change_flags+0x8c/0x110) from [<c044ac8c>] (dev_change_flags+0x10/0x44)
<4>[<c044ac8c>] (dev_change_flags+0x10/0x44) from [<c04b6fa8>] (devinet_ioctl+0x370/0x74c)
<4>[<c04b6fa8>] (devinet_ioctl+0x370/0x74c) from [<c0437494>] (sock_ioctl+0x1ec/0x240)
<4>[<c0437494>] (sock_ioctl+0x1ec/0x240) from [<c011f4ac>] (do_vfs_ioctl+0x504/0x578)
<4>[<c011f4ac>] (do_vfs_ioctl+0x504/0x578) from [<c011f554>] (sys_ioctl+0x34/0x54)
<4>[<c011f554>] (sys_ioctl+0x34/0x54) from [<c0040f20>] (ret_fast_syscall+0x0/0x30)
<4>---[ end trace 72559554885ec576 ]---
<4>wl12xx: WARNING CONFIGURE command NOK
<4>wl12xx: WARNING failed to set acx_event_mbox_mask: -110
<3>wl12xx: ERROR EVENT mask setting failed
<3>wl12xx: ERROR command complete timeout
<4>------------[ cut here ]------------

pastebin link to full output http://pastebin.com/iCcE2f4U

edit: the full output has several more sections that i think were generated when I used the connectivity tester to cycle wifi
 
Last edited:
  • Like
Reactions: steven676

Top Liked Posts

  • There are no posts matching your filters.
  • 75
    Updated 5/3/13
    The Nook Color is now an official CM 10.1 device! This is a huge milestone in the development of a device of this age!

    You can now find builds at http://get.cm/?device=encore

    I will keep the remainder of the post below for informational purposes but users should click the link above to get the latest builds.

    ------------------------------------------------------------------------------
    Updated 3/17/13
    *Beta 2 released, sync'd with latest CM sources
    *Further kernel updates, thanks again to steven676 for all his work!
    *Bootanimation still funky...

    Updated 2/27/13
    *Beta 1 released, sync'd with latest CM sources and updated to 4.2.2.
    *Latest kernel changes are included. Thanks steven676.

    KNOWN ISSUE:

    Android 4.2.2 has some new adb security features which require you to authorize the computer that you're connecting to on your device. Please make sure you have the latest adb version (update it via sdk manager). The initial adb auth doesn't always work when connected with MTP - the workaround is to switch to UMS mode (settings-storage-menu) then auth the device (and remember the keys). After that you can switch back to MTP and it'll work from then on for that computer.

    *** If you have a non-development related question/comment about 3rd party mods/add-ons then DO NOT post in this thread, it for bug reports and comments on the build provided without modifications. Please keep all user discussion in the thread in general: http://xdaforums.com/showthread.php?t=2170185 ***


    Original OP

    Following closely on the heels of our official status as a CM10 device, the NookieDevs present CyanogenMod 10.1 Alpha for the Nook Color!

    As stated, this is an Alpha release for people to get a sense of the new features in Android 4.2.1. Performance doesn't seem quite up to par as CM10 as yet, and any lingering bugs in CM10 will likely be present in this release. While almost everything is working, we do expect users to uncover some additional bugs. Please take precautions to backup your device/data.

    You should be able to flash this over CM10; however, if you run into a bug, please do a full wipe and reinstall before reporting. See Post 2 for wipe procedures and gapps information.

    Known issues:
    1) Initial boot animation doesn't display correctly
    2) Some performance issues (remember this is 2010 hardware we're working with...)

    Please read over the CM10 thread as the bulk of fattire's introduction still holds true for this release.


    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.



    Of course credits and thanks to all those who have contributed: fattire, keyodi, sluo, krylon360, dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, drmarble, mateor and many more.

    Source:
    https://github.com/NookieDevs/android_device_bn_encore/tree/cm-10.1


    Download:
    Beta2: cm-10.1-encore-b2.zip MD5: 455cf35156feabc6ac630dce51d29454


    Previous builds:
    Beta1: cm-10.1-encore-b1-stillsomebugs.zip MD5: 1afea80885f349b810b5130a30d6593e
    Alpha1: cm-10.1-a1-encore-fullofbugs.zip MD5: aa47473b5c3f743f3033c7cd7ac29f19
    29
    Nightly builds!

    Starting today, we have official CM10.1 nightly builds available at the usual location: http://get.cm/?device=encore&type=nightly . If you're currently running one of eyeballer's CM10.1 alpha/beta builds (don't forget to thank him for cranking them out!), you'll want to upgrade -- the CM10.1 nightlies include significant performance improvements over beta 2 and should be at least as stable (if not more).
    28
    Gapps for 4.2.2: http://techerrata.com/file/gapps/gapps-jb-20130301-signed.zip
    Mirror: http://goo.im/gapps


    If you run into a gapps related issue:
    1) Wipe system manually in recovery
    2) Flash rom then gapps


    If you still run into issues:
    1) Wipe system manually
    2) Wipe data (factory reset)
    3) Flash rom and gapps
    17
    Frequently asked questions

    Where did the developer settings go?
    Where did the performance menu (overclocking settings, etc.) go?

    Google and CyanogenMod decided to hide those settings by default in Android 4.2. To enable them, go to Settings->About tablet and tap on the build number seven times.

    How do I get the Honeycomb/ICS tablet UI?

    You want to use the Auto-Patcher to modify your ROM for the tablet UI. (Don't forget to thank Caldair for maintaining the Tablet UI mod, and mateorod and the rest of the Auto-Patcher developers for building that tool.)
    16
    I just installed the 5/25 nightly (was on RC2) and the CM updater still crashes when I check for updates. I did clear cache & data for the updater app too and no change.

    I've been having cm updater issues too as of 5/18 nightly.

    Anyone want to provide more information (I've quoted the original request below for reference)? Anyone? I don't have magical remote-tablet-diagnosis powers -- I need something to work with here.

    For everyone having problems with CMUpdater crashing -- could you please post the contents of any files with extension ".changelog" you find in /sdcard/cmupdater? (Also, a logcat of the crash would be helpful -- we have one (thanks sziggins!), but more would help to confirm we're looking at the same problem here.)

    As for any other problems, please check the following before reporting:
    • Does the problem occur with a clean install of CM10.1? This means wiping /data and not restoring a Nandroid backup afterwards. Don't restore system apps and/or their data in Titanium Backup either (user apps/data are okay).
    • Are you overclocking? To be clear, we are not interested at this point in bug reports of any kind that happen if you have the maximum CPU speed set above 1000 MHz. If you're experiencing system crashes or SOD, you may also wish to try capping the CPU clock speed to 800 MHz (but if this helps, please report your problem here and fill out the hardware survey).
    • Do you have any patches, custom kernels (any of my "test" kernels included), or other tweaks applied? (To be clear, we're not necessarily going to ignore bug reports from patched or tweaked systems outright, but it can make our job harder, and we do need to know to judge whether or not the change might be relevant to your problem.)

    When reporting, please include the following information if at all possible:
    • Full description of the problem -- "it crashes" doesn't count. How do you trigger the problem (or does it occur by itself)? What exactly happens when the problem occurs? How often does it happen?
    • For problems with apps or specific pieces of the system software: we'll almost certainly ask for a logcat of the event, so you'll save everyone some time by including it.
    • For problems involving system freezes, crashes, or SOD: if you can connect to the tablet via adb while it's "unresponsive", please provide dmesg and logcat output from that time. If you cannot, try power-cycling it while it's still plugged into USB, and provide dmesg output from immediately after the reboot, plus the contents of /proc/last_kmsg if that file exists (let us know if it doesn't).
    • For unexpected reboots: provide the contents of /proc/last_kmsg from after the reboot.

    I can make my nook color screaming fast by shotgunning it on CM 10.1. You guys are just not wanting to debug. Hate to be direct but that is the truth. Got all of my lag reducer apps linked down in cyanogenmod. You are forgetting speed over features. You guys ran off dalingrin who did great work on the CM 7.2 series. I bet he spent tons of time getting that build up fast.

    Also why did no one pick up a mod for overclocking more? I am seeing controversy with the developers over this, this tells me the kernels are not as stable as they like or they would not care. Dont let them run off.

    There is lag reports all over the internet on just the nexus 7 for jellybean too. Fix the problems please. I spent lots of time promoting this project and you guys are just making us look like slackers. You are better than this. You are geniuses with code. Work that magic more and give us love too.

    Let me say this (relatively) nicely, hopefully before someone else does in a less, uh, restrained way: no one (here) is obligated to do anything for you. These are all-volunteer projects we're talking about, and the people working on them have the right to spend their spare time however they wish. If those wishes don't align with yours, that's your problem, not theirs.

    Put another way, you're welcome to ask for certain features, or for certain bugs to be fixed, but you should not expect, let alone demand, that something be done.