[ROM] CyanogenMod 10 Nightly Builds for Nook Color

Search This thread
By:
Advanced…
compuguy1088

compuguy1088

Senior Member
Jun 17, 2010
1,295
84
NoVA
www.compuguy1088.com
SOD occurred while on charger. Attached is a logcat with a crash occuring with wpa supplicant:

https://gist.github.com/3933208


Interesting section of logcat posted here, the rest is at the above link:
Code: 
I/wpa_supplicant( 1569): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:21:29:6e:7c:c4 reason=7

F/libc    ( 1569): Fatal signal 11 (SIGSEGV) at 0x402f7000 (code=1), thread 1569 (wpa_supplicant)

I/DEBUG   ( 1234): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG   ( 1234): Build fingerprint: 'bn/bn_encore/encore:4.1.2/JZO54K/228551:user/release-keys'

I/DEBUG   ( 1234): pid: 1569, tid: 1569, name: wpa_supplicant  >>> /system/bin/wpa_supplicant <<<

I/DEBUG   ( 1234): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 402f7000

W/ThrottleService( 1484): unable to find stats for iface rmnet0

I/DEBUG   ( 1234):     r0 402e7520  r1 402f6ffa  r2 5b08d4e9  r3 0000000c

I/DEBUG   ( 1234):     r4 402e1640  r5 402e2d28  r6 402f12a8  r7 402f12c8

I/DEBUG   ( 1234):     r8 5b093235  r9 402f12ce  sl 2d415057  fp 00000052

I/DEBUG   ( 1234):     ip 80000000  sp be9d4ed0  lr 4009854b  pc 400ea238  cpsr 200f0010

I/DEBUG   ( 1234):     d0  0000000000280000  d1  0000000000000000

I/DEBUG   ( 1234):     d2  0000000000000000  d3  0000000000000000

I/DEBUG   ( 1234):     d4  0005000000000000  d5  ffb5000001270000

I/DEBUG   ( 1234):     d6  000058622a00ffff  d7  0000000000000000

I/DEBUG   ( 1234):     d8  0000000000000000  d9  0000000000000000

I/DEBUG   ( 1234):     d10 0000000000000000  d11 0000000000000000

I/DEBUG   ( 1234):     d12 0000000000000000  d13 0000000000000000

I/DEBUG   ( 1234):     d14 0000000000000000  d15 0000000000000000

I/DEBUG   ( 1234):     d16 4040000000000000  d17 4040000000000000

I/DEBUG   ( 1234):     d18 41c975299d800000  d19 0000000000000000

I/DEBUG   ( 1234):     d20 0000000000000000  d21 0000000000000000

I/DEBUG   ( 1234):     d22 0000000000000000  d23 0000000000000000

I/DEBUG   ( 1234):     d24 0000000000000000  d25 0000000000000000

I/DEBUG   ( 1234):     d26 0000000000000000  d27 0000000000000000

I/DEBUG   ( 1234):     d28 0000000000000000  d29 0000000000000000

I/DEBUG   ( 1234):     d30 0000000000000000  d31 0000000000000000

I/DEBUG   ( 1234):     scr 60000010

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): backtrace:

I/DEBUG   ( 1234):     #00  pc 0000e238  /system/lib/libc.so (memcpy+124)

I/DEBUG   ( 1234):     #01  pc 0004d547  /system/bin/wpa_supplicant

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): stack:

I/DEBUG   ( 1234):          be9d4e90  00000000  

I/DEBUG   ( 1234):          be9d4e94  00000000  

I/DEBUG   ( 1234):          be9d4e98  00000000  

I/DEBUG   ( 1234):          be9d4e9c  00000000  

I/DEBUG   ( 1234):          be9d4ea0  00000000  

I/DEBUG   ( 1234):          be9d4ea4  00000000  

I/DEBUG   ( 1234):          be9d4ea8  00000000  

I/DEBUG   ( 1234):          be9d4eac  00000000  

I/DEBUG   ( 1234):          be9d4eb0  00000000  

I/DEBUG   ( 1234):          be9d4eb4  00000000  

I/DEBUG   ( 1234):          be9d4eb8  00000000  

I/DEBUG   ( 1234):          be9d4ebc  00000000  

I/DEBUG   ( 1234):          be9d4ec0  be9d4f00  [stack]

I/DEBUG   ( 1234):          be9d4ec4  402e1640  [heap]

I/DEBUG   ( 1234):          be9d4ec8  df0027ad  

I/DEBUG   ( 1234):          be9d4ecc  00000000  

I/DEBUG   ( 1234):     #00  be9d4ed0  402e1814  [heap]

I/DEBUG   ( 1234):          be9d4ed4  4009854b  /system/bin/wpa_supplicant

I/DEBUG   ( 1234):     #01  be9d4ed8  00000000  

I/DEBUG   ( 1234):          be9d4edc  00000000  

I/DEBUG   ( 1234):          be9d4ee0  00000000  

I/DEBUG   ( 1234):          be9d4ee4  00000000  

I/DEBUG   ( 1234):          be9d4ee8  00000000  

I/DEBUG   ( 1234):          be9d4eec  00000000  

I/DEBUG   ( 1234):          be9d4ef0  00000000  

I/DEBUG   ( 1234):          be9d4ef4  00000000  

I/DEBUG   ( 1234):          be9d4ef8  00000000  

I/DEBUG   ( 1234):          be9d4efc  00000000  

I/DEBUG   ( 1234):          be9d4f00  2d415057  

I/DEBUG   ( 1234):          be9d4f04  402f12c8  [heap]

I/DEBUG   ( 1234):          be9d4f08  402f12ce  [heap]

I/DEBUG   ( 1234):          be9d4f0c  5b093235  

I/DEBUG   ( 1234):          be9d4f10  00000000  

I/DEBUG   ( 1234):          be9d4f14  00000000  

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory near r0:

I/DEBUG   ( 1234):     402e7500 00000000 00000000 00000000 00000000  ................

I/DEBUG   ( 1234):     402e7510 00000000 00000000 00000000 00000000  ................

I/DEBUG   ( 1234):     402e7520 0e06c0b2 00000013 402654e4 402e8e70  .........T&@p..@

I/DEBUG   ( 1234):     402e7530 0e06d016 00000013 402654ec 402e9160  .........T&@`..@

I/DEBUG   ( 1234):     402e7540 0e07103e 00000013 402654f4 402e75d8  >........T&@.u.@

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory near r1:

I/DEBUG   ( 1234):     402f6fd8 00000000 00000028 00000000 00000000  ....(...........

I/DEBUG   ( 1234):     402f6fe8 00000000 00000000 00000000 00000000  ................

I/DEBUG   ( 1234):     402f6ff8 00000000 00000000 ffffffff ffffffff  ................

I/DEBUG   ( 1234):     402f7008 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     402f7018 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory near r2:

I/DEBUG   ( 1234):     5b08d4c8 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     5b08d4d8 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     5b08d4e8 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     5b08d4f8 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     5b08d508 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory near r4:

I/DEBUG   ( 1234):     402e1620 402e1568 ffffffff c98e7855 00000013  h..@....Ux......

I/DEBUG   ( 1234):     402e1630 402e1c90 8d755ea2 f7dbc0a6 000004eb  ...@.^u.........

I/DEBUG   ( 1234):     402e1640 402e1568 402e1640 00000000 402e1de0  h..@@..@.......@

I/DEBUG   ( 1234):     402e1650 00000000 438bd200 6c77fd9f 00306e61  .......C..wlan0.

I/DEBUG   ( 1234):     402e1660 00000000 00000000 00000000 00000000  ................

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory near r5:

I/DEBUG   ( 1234):     402e2d08 00000000 00000000 00000000 00000000  ................

I/DEBUG   ( 1234):     402e2d18 00000000 00000000 00000000 00000000  ................

I/DEBUG   ( 1234):     402e2d28 00000000 00000000 00000000 00000000  ................

I/DEBUG   ( 1234):     402e2d38 00000000 00000000 00000000 00000000  ................

I/DEBUG   ( 1234):     402e2d48 00000000 00000000 00000000 00000000  ................

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory near r6:

I/DEBUG   ( 1234):     402f1288 18dd000c 02f25000 00800101 0000a403  .....P..........

I/DEBUG   ( 1234):     402f1298 0000a427 005e4342 002f3262 00005d39  '...BC^.b2/.9]..

I/DEBUG   ( 1234):     402f12a8 49535352 32352d3d 4e494c0a 4550534b  RSSI=-52.LINKSPE

I/DEBUG   ( 1234):     402f12b8 353d4445 4f4e0a34 3d455349 0a37392d  ED=54.NOISE=-97.

I/DEBUG   ( 1234):     402f12c8 51455246 434e4555 34323d59 000a3236  FREQUENCY=2462..

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory near r7:

I/DEBUG   ( 1234):     402f12a8 49535352 32352d3d 4e494c0a 4550534b  RSSI=-52.LINKSPE

I/DEBUG   ( 1234):     402f12b8 353d4445 4f4e0a34 3d455349 0a37392d  ED=54.NOISE=-97.

I/DEBUG   ( 1234):     402f12c8 51455246 434e4555 34323d59 000a3236  FREQUENCY=2462..

I/DEBUG   ( 1234):     402f12d8 353a3834 39333a62 3a38653a 303a3835  48:5b:39:e8:58:0

I/DEBUG   ( 1234):     402f12e8 34320963 2d093231 5b093235 2d415057  c.2412.-52.[WPA-

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory near r8:

I/DEBUG   ( 1234):     5b093214 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     5b093224 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     5b093234 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     5b093244 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     5b093254 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory near r9:

I/DEBUG   ( 1234):     402f12ac 32352d3d 4e494c0a 4550534b 353d4445  =-52.LINKSPEED=5

I/DEBUG   ( 1234):     402f12bc 4f4e0a34 3d455349 0a37392d 51455246  4.NOISE=-97.FREQ

I/DEBUG   ( 1234):     402f12cc 434e4555 34323d59 000a3236 353a3834  UENCY=2462..48:5

I/DEBUG   ( 1234):     402f12dc 39333a62 3a38653a 303a3835 34320963  b:39:e8:58:0c.24

I/DEBUG   ( 1234):     402f12ec 2d093231 5b093235 2d415057 2d4b5350  12.-52.[WPA-PSK-

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory near sl:

I/DEBUG   ( 1234):     2d415034 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     2d415044 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     2d415054 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     2d415064 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     2d415074 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory near ip:

I/DEBUG   ( 1234):     7fffffe0 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     7ffffff0 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     80000000 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     80000010 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234):     80000020 ffffffff ffffffff ffffffff ffffffff  ................

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory near sp:

I/DEBUG   ( 1234):     be9d4eb0 00000000 00000000 00000000 00000000  ................

I/DEBUG   ( 1234):     be9d4ec0 be9d4f00 402e1640 df0027ad 00000000  .O..@..@.'......

I/DEBUG   ( 1234):     be9d4ed0 402e1814 4009854b 00000000 00000000  ...@K..@........

I/DEBUG   ( 1234):     be9d4ee0 00000000 00000000 00000000 00000000  ................

I/DEBUG   ( 1234):     be9d4ef0 00000000 00000000 00000000 00000000  ................

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): code around pc:

I/DEBUG   ( 1234):     400ea218 f5d1f000 f5d1f040 e2522040 3a000009  ....@...@ R....:

I/DEBUG   ( 1234):     400ea228 f5d1f080 f5d1f0c0 f5d1f100 f421020d  ..............!.

I/DEBUG   ( 1234):     400ea238 f421420d f5d1f100 e2522040 f400022d  .B!.....@ R.-...

I/DEBUG   ( 1234):     400ea248 f400422d 2afffff8 e2822040 e2522020  -B.....*@ ..  R.

I/DEBUG   ( 1234):     400ea258 3a000003 f421020d e2522020 f400022d  ...:..!.  R.-...

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): code around lr:

I/DEBUG   ( 1234):     40098528 464970ea f7b74642 b110e8a8 f8c42200  .pIFBF......."..

I/DEBUG   ( 1234):     40098538 f8c422e4 f504a1f8 464970ea f7b74642  .".......pIFBF..

I/DEBUG   ( 1234):     40098548 f8c4e87e 6d6b81f4 900e2001 d509071b  ~.....km. ......

I/DEBUG   ( 1234):     40098558 1198f8d5 f8d5b131 b90a219c e0002304  ....1....!...#..

I/DEBUG   ( 1234):     40098568 930e2305 b1036deb aa14930e 46292300  .#...m.......#)F

I/DEBUG   ( 1234): 

I/DEBUG   ( 1234): memory map around fault addr 402f7000:

I/DEBUG   ( 1234):     402e1000-402f7000 [heap]

I/DEBUG   ( 1234):     (no map for address)

I/DEBUG   ( 1234):     be9b5000-be9d6000 [stack]

I/EventLogService( 1824): Aggregate from 1350922942735 (log), 1350922942735 (data)

D/WifiHW  ( 1484): 'SET ps 1' command timed out.

D/CommandListener( 1233): Clearing all IP addresses on wlan0

D/ConnectivityService( 1484): ConnectivityChange for WIFI: DISCONNECTED/DISCONNECTED

D/ConnectivityService( 1484): Attempting to switch to BLUETOOTH_TETHER

E/WifiStateMachine( 1484): Connection lost, restart supplicant
 
Last edited:
ibilln

ibilln

Senior Member
Jan 17, 2012
451
83
San Francisco
No pics in Gallery

Running off SD card, all working well over weekend - no SOD, decent performance, battery, etc. Some weirdness before, until I shared SD space with EMMC per leapinlar. Hmm? Go figure.

Except - Gallery runs but no pics. Flailed around quite a bit learning about .nomedia files; getting, running Rescan Media Root; blah blah. Nada - no pics from the Goog. Got 'em on my phone. It could not have been something I've done by mistake...?? Impossible! In the off chance it was, though, would appreciate any ideas. Thnx!
 
Last edited:
W

weldawadyathink

Senior Member
Sep 24, 2011
182
33
I got a pretty nice...bug?...thing where the n button WILL turn on the nook. I am not at home right now, but i could send someone a nandroid or other system files to maybe add this into the next release.

Sent from my MB870 using xda premium

---------- Post added at 03:02 PM ---------- Previous post was at 02:59 PM ----------
compuguy1088 said:
SOD occurred while on charger. Attached is a logcat with a crash occuring with wpa supplicant:
Click to expand...
Click to collapse

If you want to post a logcat, a .txt file on mediafire or other upload service works great.

Sent from my MB870 using xda premium
 
krylon360

krylon360

Retired Recognized Developer
May 10, 2010
2,228
3,109
Seattle
weldawadyathink said:
I got a pretty nice...bug?...thing where the n button WILL turn on the nook. I am not at home right now, but i could send someone a nandroid or other system files to maybe add this into the next release.

Sent from my MB870 using xda premium

---------- Post added at 03:02 PM ---------- Previous post was at 02:59 PM ----------



If you want to post a logcat, a .txt file on mediafire or other upload service works great.

Sent from my MB870 using xda premium
Click to expand...
Click to collapse

uh what?
 
  • Like
Reactions: jamesh0317 and diajohn
Neckberg

Neckberg

Senior Member
Dec 30, 2010
386
55
Green Bay
So i am having the sod problems also. I installed wake lock from the market and having no problems. Battery life I'd give with it also. Been unplugged since yesterday morning and still has juice.

Sent from my SPH-L710 using xda app-developers app
 
W

WJThomas

Senior Member
Jan 20, 2012
101
59
BlueKalel said:
May I ask how you edited it? Can you show a copy of your vold.fstab. I checked auto-patcher and couldn't find where it said it will do the swap.

Thanks,
BlueKalel
Click to expand...
Click to collapse

I used SManager to make the edits. It is a script manager with a simple text editor. I used File Expert to navigate to the file. Long press and select open as text, then select SM Editor. I just swapped the /storage/sdcard1 and /storage/sdcard0. I had originally tried swapping the sdcard and emmc, but it didn't work (I don't remember what the issue was). It looks like the auto patcher does it differently, and I have not tried it yet.

Sent from my NookColor using xda app-developers app
 
B

boyoboyo

Senior Member
Jun 2, 2009
124
21
weldawadyathink said:
I got a pretty nice...bug?...thing where the n button WILL turn on the nook. I am not at home right now, but i could send someone a nandroid or other system files to maybe add this into the next release.
Click to expand...
Click to collapse

I believe a fix has already been commit. You can wait for the next alpha, as I'm quite positive it'll be in it.
 
Last edited:
compuguy1088

compuguy1088

Senior Member
Jun 17, 2010
1,295
84
NoVA
www.compuguy1088.com
weldawadyathink said:
I got a pretty nice...bug?...thing where the n button WILL turn on the nook. I am not at home right now, but i could send someone a nandroid or other system files to maybe add this into the next release.

Sent from my MB870 using xda premium

---------- Post added at 03:02 PM ---------- Previous post was at 02:59 PM ----------



If you want to post a logcat, a .txt file on mediafire or other upload service works great.

Sent from my MB870 using xda premium
Click to expand...
Click to collapse

Yea....I did post the *full* logcat...on github gist...hence the link.
 
pckoloji

pckoloji

Senior Member
Oct 10, 2010
176
26
warsaw
www.pckoloji.com
CM10 A1 mounts the internal SD card under /mnt/emmc and mounts external SD card under /mnt/sdcard.

Many applications download data using /mnt/sdcard as path and all goes to microsd card instead of internal 4 gb area. Apps2SD moves data to microsd so I need to keep it when turned on.

I want to swap their places. In order to do this, i am trying to edit vold.fstab file under /System/etc but could not find the right solution. Is there any guide?
 
Last edited:
bornagainpenguin

bornagainpenguin

Senior Member
Oct 22, 2010
379
71
pckoloji said:
I want to swap their places. In order to do this, i am trying to edit vold.fstab file under /System/etc but could not find the right solution. Is there any guide?
Click to expand...
Click to collapse

I also am waiting for this before trying out the Alpha again.

(Personally this is the most Beta "alpha" release I've ever seen, so once the SDCard issue is taken care of I'm thinking of running this as a daily driver.)

I've seen reference to a script manager app which can be used to change lines to swap the internal and external memory sources, but not what those lines should be changed to.

Sent from my NookColor using Tapatalk 2
 
leapinlar

leapinlar

Senior Member
Oct 18, 2006
8,873
3,878
pckoloji said:
CM10 A1 mounts the internal SD card under /mnt/emmc and mounts external SD card under /mnt/sdcard.

Many applications download data using /mnt/sdcard as path and all goes to microsd card instead of internal 4 gb area. Apps2SD moves data to microsd so I need to keep it when turned on.

I want to swap their places. In order to do this, i am trying to edit vold.fstab file under /System/etc but could not find the right solution. Is there any guide?
Click to expand...
Click to collapse
CM10 does it a little differently than the other CM versions. It actually mounts the sdcard to /storage/sdcard1 and symlinks it to /mnt/sdcard and /sdcard. It also mounts emmc to /storage/sdcard0 and symlinks it to /mnt/emmc and /emmc. It does the symlinking for backwards compatibility with other apps. So any swapping scheme you come up with needs to take that into account.


Sent from my Nook Color running CM10 and Tapatalk.
 
  • Like
Reactions: pckoloji and boomn
pckoloji

pckoloji

Senior Member
Oct 10, 2010
176
26
warsaw
www.pckoloji.com
ok i need to search more perhaps.

pawitp's cm10 knightly for samsung galaxy s has opposite

  • moviNAND mmcblk0p1 5.77 gb /storage/sdcard0 = /mnt/sdcard = /sdcard
  • microsd card xx gb /storage/sdcard1 = /mnt/emmc = /emmc
 
leapinlar

leapinlar

Senior Member
Oct 18, 2006
8,873
3,878
pckoloji said:
ok i need to search more perhaps.

pawitp's cm10 knightly for samsung galaxy s has opposite

  • moviNAND mmcblk0p1 5.77 gb /storage/sdcard0 = /mnt/sdcard = /sdcard
  • microsdcard xx gb /storage/sdcard1 = /mnt/emmc = /emmc
Click to expand...
Click to collapse
For Galaxy S I believe sdcard is actually internal storage. At least it was for older Galaxy's.
 
Last edited:
A

arkas79

Member
May 27, 2008
14
4
Is there a working cifs module for this version? I have tried some from older roms but as expected no luck.
I really miss the functionality of smb mounting.
 
  • Like
Reactions: bornagainpenguin
W

WJThomas

Senior Member
Jan 20, 2012
101
59
bornagainpenguin said:
I've seen reference to a script manager app which can be used to change lines to swap the internal and external memory sources, but not what those lines should be changed to.
Click to expand...
Click to collapse

WJThomas said:
I used SManager to make the edits. It is a script manager with a simple text editor. I used File Expert to navigate to the file. Long press and select open as text, then select SM Editor. I just swapped the /storage/sdcard1 and /storage/sdcard0. I had originally tried swapping the sdcard and emmc, but it didn't work (I don't remember what the issue was). It looks like the auto patcher does it differently, and I have not tried it yet.
Click to expand...
Click to collapse

I'm not sure what more you are looking for...

I stated to edit the file and change the /storage/sdcard1 to /storage/sdcard0 and change the /storage/sdcard0 to /storage/sdcard1.

I'm not sure that listing the lines out would be any more clear or easier to read. I actually think the opposite. If you would take a look at the file, it will all be clear. Also, I'm not stating that this is the best, or even proper, way to accomplish the change; just that I found that this works for me. I had a few boot loops while experimenting, but that is how you learn (or at least how I learn)

Here's the link to SManager if you need: https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en

If you make a backup (always a good idea) you can restore if you make a mistake. If you are not comfortable making this change, you can always use the auto patcher. I also stated that this is the route that I plan on taking for the next update.

There are many ways to accomplish what you want. I have listed two that should work. I believe I have seen other posts that talk about slightly different changes. It's all up to you. You can try one of them and help test the ROM, or you can wait for the swap functionality to be implemented inside the ROM. It is you choice.
 
S

stolenmoment

Senior Member
Mar 27, 2011
360
43
Got a SoD yesterday with wakelock set to WIFI_MODE_FULL; I paused audio playback (BeyondPod) to buy a couple of bagels and it wouldn't wake up when I got outside, three minutes later or so. I've upgraded to WIFI_MODE_HIGH_PERF for today and we'll see how it goes; I am apparently getting deep sleep at this setting. It survived charging overnight set to PARTIAL_WAKE_LOCK, but it doesn't deep sleep so I'm reluctant to do that during the daytime.

How deeply asleep does it need to be before "n" doesn't wake it up? It seems to take perhaps a minute to get to that state when unplugged.
 
bornagainpenguin

bornagainpenguin

Senior Member
Oct 22, 2010
379
71
I managed to figure it out with those instructions. Was nervous as heck though, but seems to be working okay and all my apps are finding their backed up info.

Seeing what people mean by slow charging. I usually plug in via a power strip, now giving a direct connection to see if this makes a difference because I seem to recall this being the cause of a similar issue in the past. Will report if makes any difference...

UPDATE: Plugging directly seems to be working a little faster than trying to charge from the power strip. Can anyone else who felt the charging was slow confirm whether directly plugging in to the power outlet makes a difference for them?

Sent from my HTC One V using Tapatalk 2
 
Last edited:
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