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

Search This thread
By:
Advanced…
W

WJThomas

Senior Member
Jan 20, 2012
101
59
steven676 said:
One more request: if you get a chance, could you put Nook #2 through a few sleep cycles with the August 20 nightly (or equivalent) kernel, verify that it doesn't SOD, and then post a dmesg from that? Thanks.
Click to expand...
Click to collapse

I flashed your kernel on Nook #2, but if I let it sleep for a few minutes it reboots. I can let it timeout and sleep after booting, but if I wake it and let it timeout again it will reboot after a few minutes. I did not time it, as I was off doing something else and noticed it booting when I came back. I checked again a couple of times and saw the reboot again.

So, where do we go next. I noted that WiFi is not turning on with this kernel and PA3.65. I seem to recall some discussion of WiFi on and SOD, so is this a valid test case for you?

Is there something I can capture before or after the reboot to help. I seem to recall a command that would cause the dmesg to continuously log to SD. This might show the cause of the reboot.

Or, would flashing the 10.1 be better? I now have a spare SD that I could setup with 10.1 for testing.
 
  • Like
Reactions: webyrd and steven676
S

steven676

Senior Member
Nov 24, 2011
593
2,433
WJThomas said:
I flashed your kernel on Nook #2, but if I let it sleep for a few minutes it reboots. I can let it timeout and sleep after booting, but if I wake it and let it timeout again it will reboot after a few minutes. I did not time it, as I was off doing something else and noticed it booting when I came back. I checked again a couple of times and saw the reboot again.

So, where do we go next. I noted that WiFi is not turning on with this kernel and PA3.65. I seem to recall some discussion of WiFi on and SOD, so is this a valid test case for you?

Is there something I can capture before or after the reboot to help. I seem to recall a command that would cause the dmesg to continuously log to SD. This might show the cause of the reboot.

Or, would flashing the 10.1 be better? I now have a spare SD that I could setup with 10.1 for testing.
Click to expand...
Click to collapse

Please post the contents of /proc/last_kmsg after a reboot. It'd be best to test with CM10.1 or 10.2 just to be sure, but I doubt that's the issue here. (The wifi breakage is related to the CM kernel not being binary compatible with kernel modules built for the PA kernel, and shouldn't be relevant to the SOD.)
 
  • Like
Reactions: Maverik18
W

WJThomas

Senior Member
Jan 20, 2012
101
59
steven676 said:
Please post the contents of /proc/last_kmsg after a reboot. It'd be best to test with CM10.1 or 10.2 just to be sure, but I doubt that's the issue here. (The wifi breakage is related to the CM kernel not being binary compatible with kernel modules built for the PA kernel, and shouldn't be relevant to the SOD.)
Click to expand...
Click to collapse

This is the /process/last_kmsg immediately after a screen off reboot with your kernel over PA3.56
http://pastebin.com/Kw6pBdxb

I will setup my spare SD with CM10 when I get a chance. Do you have a preference 10.1 or 10.2?

Sent from my NookColor using xda app-developers app
 
  • Like
Reactions: webyrd and steven676
S

steven676

Senior Member
Nov 24, 2011
593
2,433
WJThomas said:
This is the /process/last_kmsg immediately after a screen off reboot with your kernel over PA3.56
http://pastebin.com/Kw6pBdxb
Click to expand...
Click to collapse

Okay, never mind my initial assessment about the wifi -- it looks like half the wifi driver loaded and is now wondering where the other half went. Please do try CM10.1/10.2 when you get a chance.

WJThomas said:
I will setup my spare SD with CM10 when I get a chance. Do you have a preference 10.1 or 10.2?
Click to expand...
Click to collapse

For purposes of this discussion, no, not really. That said, if you're short on time, a random 10.1 nightly is less likely to be broken than a random 10.2 nightly at this stage in development ...
 
  • Like
Reactions: Maverik18 and WJThomas
W

WJThomas

Senior Member
Jan 20, 2012
101
59
steven676 said:
Please do try CM10.1/10.2 when you get a chance.

For purposes of this discussion, no, not really. That said, if you're short on time, a random 10.1 nightly is less likely to be broken than a random 10.2 nightly at this stage in development ...
Click to expand...
Click to collapse

Since this is a 10.1 thread, here is a dmesg of Nook #2 running the latest nightly from SD http://pastebin.com/FWjt0PsZ

Let me know if you want any more of this. If not, I will do the same with the latest 10.2 nightly. Should I post the 10.2 in the 10.2 thread, or keep the discussion together here?

Sent from my NookColor using xda app-developers app
 
  • Like
Reactions: webyrd
S

steven676

Senior Member
Nov 24, 2011
593
2,433
WJThomas said:
Since this is a 10.1 thread, here is a dmesg of Nook #2 running the latest nightly from SD http://pastebin.com/FWjt0PsZ

Let me know if you want any more of this. If not, I will do the same with the latest 10.2 nightly. Should I post the 10.2 in the 10.2 thread, or keep the discussion together here?
Click to expand...
Click to collapse

Link's broken. No, I don't need both 10.1 and 10.2, thanks -- I just need to see it surviving a few sleep cycles, which should in theory depend only on the kernel (which is almost identical between 10.1 and 10.2).

EDIT: Okay, sorted out the link thing. That said, is this the same Nook? I see from the very start
Code: 
<6>Samsung P17 patch already applied to eMMC
which would suggest Nook #1, not Nook #2 (the patch does not persist across reboots).


EDIT 2: No, it is the same device, if backlighttype= in the kernel command line is any indication. The plot thickens ... could you repeat this on Nook #2 after a full power-cycle (not just a reboot), and also try Nook #1 under the same conditions as well? Thanks, and I apologize for being so particular.
 
Last edited:
  • Like
Reactions: webyrd and Maverik18
W

WJThomas

Senior Member
Jan 20, 2012
101
59
steven676 said:
Link's broken. No, I don't need both 10.1 and 10.2, thanks -- I just need to see it surviving a few sleep cycles, which should in theory depend only on the kernel (which is almost identical between 10.1 and 10.2).

EDIT: Okay, sorted out the link thing. That said, is this the same Nook? I see from the very start
Code: 
<6>Samsung P17 patch already applied to eMMC
which would suggest Nook #1, not Nook #2 (the patch does not persist across reboots).


EDIT 2: No, it is the same device, if backlighttype= in the kernel command line is any indication. The plot thickens ... could you repeat this on Nook #2 after a full power-cycle (not just a reboot), and also try Nook #1 under the same conditions as well? Thanks, and I apologize for being so particular.
Click to expand...
Click to collapse

Not sure what the issue is, but here is a repost.
http://pastebin.com/Fe7DAT6H

Sent from my LG-E970 using xda app-developers app
 
W

WJThomas

Senior Member
Jan 20, 2012
101
59
steven676 said:
EDIT 2: No, it is the same device, if backlighttype= in the kernel command line is any indication. The plot thickens ... could you repeat this on Nook #2 after a full power-cycle (not just a reboot), and also try Nook #1 under the same conditions as well? Thanks, and I apologize for being so particular.
Click to expand...
Click to collapse

Here are full power-cycle boots of the two nooks
Nook #1
Nook #2


steven676 said:
Also interesting to note is that it appears the eMMC firmware varies even among chips that report the same information -- your #1 reports in dmesg

Code: 
<6>Samsung P17 patch already applied to eMMC

while #2 says instead

Code: 
<6>Applying Samsung P17 corruption fix to eMMC
<6>Samsung P17 corruption fix successfully applied

In other words, #1 (which has an earlier eMMC date, for whatever that's worth) had the fix applied at the factory, while #2 needs the hotfix. (I suppose I shouldn't be surprised by anything coming from Samsung LSI's storage division anymore ...)
Click to expand...
Click to collapse

Sorry, it looks like my sloppy test techniques have led you astray. Both Nooks are now reporting the need to apply the P17 patch. I must have originally just done a reboot on Nook #1. I was trying to let it boot once and get things sorted out, then show the second boot, thinking it would be cleaner for you.

Let me know what you want to see next.
 
  • Like
Reactions: webyrd and steven676
S

steven676

Senior Member
Nov 24, 2011
593
2,433
WJThomas said:
Here are full power-cycle boots of the two nooks
Nook #1
Nook #2

Sorry, it looks like my sloppy test techniques have led you astray. Both Nooks are now reporting the need to apply the P17 patch. I must have originally just done a reboot on Nook #1. I was trying to let it boot once and get things sorted out, then show the second boot, thinking it would be cleaner for you.

Let me know what you want to see next.
Click to expand...
Click to collapse

That's good -- I think I've seen everything I need to understand what's happening. Interesting that the patch persists even after a reset -- that wasn't the impression I got from reading the code. Thanks for your help!
 
  • Like
Reactions: Maverik18, ajrty33, webyrd and 1 other person
Starphish

Starphish

Senior Member
Jan 23, 2012
132
47
My NC no longer "sees" my SD card. :(

So many apps, including Play Store no longer load fully (it can't connect). Even TWRP recovery does not "see" the SD. My PC has no problem directly viewing the SD files, but cannot see the SD via the NC.

So I'm wondering if this is hardware related, or due to some anomaly with the nightlies. My CM version is10.2.20130829-NIGHTLY-encore.

Is it time to get a Nexus tablet?
 
W

webyrd

Senior Member
May 4, 2011
223
104
Florida
Starphish said:
My NC no longer "sees" my SD card. :(

So many apps, including Play Store no longer load fully (it can't connect). Even TWRP recovery does not "see" the SD. My PC has no problem directly viewing the SD files, but cannot see the SD via the NC.

So I'm wondering if this is hardware related, or due to some anomaly with the nightlies. My CM version is10.2.20130829-NIGHTLY-encore.

Is it time to get a Nexus tablet?
Click to expand...
Click to collapse

CM10 is known to be finicky about SD cards, have you tried reformatting or a new (Sandisk) one?
 
  • Like
Reactions: Starphish
Starphish

Starphish

Senior Member
Jan 23, 2012
132
47
webyrd said:
CM10 is known to be finicky about SD cards, have you tried reformatting or a new (Sandisk) one?
Click to expand...
Click to collapse
I tried reformatting with TWRP, but it didn't find the card. I'm looking for a second card to test now.

UPDATE: You were spot on. THANKS. I found an 8GB Transcend and popped it in all went well... until I updated to 10.1.3 and everything hung... so I did a complete wipe and started from square one... I'm now downloading a zillion apps from Play Store (got TiBu but don't trust my backups except for the side-loaded apps).

The only downside is that I can no longer justify the Nexus 7.
 
Last edited:
P

pmgnet

Senior Member
Jan 23, 2008
1,251
202
Atlanta
Latest nightly is so fast, using nova. Browser included. Did I miss something? F2fs is next? What a deal I got using this device since the day it was available. Still my favorite reader device.
 
You must log in or register to reply here.

Similar threads

fattire
[ROM] CyanogenMod 10 Nightly Builds for Nook Color
Replies
2K
Views
708K
leapinlar
leapinlar
S
[DISCONTINUED] CM9/ICS Nightly Builds
Replies
2K
Views
663K
cammykool
cammykool
D
[DEV] CM11 Work-In-Progress
Replies
4K
Views
2M
owim
owim
eyeballer
[ROM][NC] Unofficial CM9 Nightly builds - with/without OpenGL
Replies
1K
Views
449K
T
tillerr
V
[ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards.
Replies
2K
Views
1M
A
AdilJ

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 75
    eyeballer
    eyeballer
    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
    View
    29
    S
    steven676
    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).
    View
    28
    eyeballer
    eyeballer
    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
    View
    17
    S
    steven676
    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.)
    View
    16
    S
    steven676
    ktklein72 said:
    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.
    Click to expand...
    Click to collapse

    RallyStyle2003 said:
    I've been having cm updater issues too as of 5/18 nightly.
    Click to expand...
    Click to collapse

    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.

    steven676 said:
    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.)
    Click to expand...
    Click to collapse

    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.

    meteorrock said:
    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.
    Click to expand...
    Click to collapse

    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.
    View

New posts