This may fix your SOD issue
adb shell
cd system/bin
chmod 775 pvrsrvinit
He may want to mount system as read/write first
Code:
mount -o remount,rw /system
Racks
This may fix your SOD issue
adb shell
cd system/bin
chmod 775 pvrsrvinit
mount -o remount,rw /system
Is usb host mode enabled by default or do I have to use a utility to get it enable ? Is there a thread somewhere that deals with usb host mode and CM9 ICS ? Also from what I gathered from searches in the forum so far block devices dont work right ?
You have to use an app ( Nook Tweaks )
There is a thread on CM7 ( verygreen's ) , most of it is the same on CM9
I'm planning to open a new thread for CM7+CM9 with updated info and some index for the original thread , hoping to finish this soon
I'm having issues with Nook Color Tweaks. Currently running build 119 and have installed Nook Color Tweeks. The problem I'm having is that Nook Color Tweaks crashes when I try to adjust the DAC or the Headphone volume controls. Anyone else having this issue???You have to use an app ( Nook Tweaks )
There is a thread on CM7 ( verygreen's ) , most of it is the same on CM9
I'm planning to open a new thread for CM7+CM9 with updated info and some index for the original thread , hoping to finish this soon
I had the same problem, but got past that point by using the modified Gapps from the 1st post of this thread, http://xdaforums.com/showthread.php?t=1444943 . That should work for you.EDIT: installing the gapps without the installer or at least the gapps for ICS the file I have is both. Everything is running good off the card now and leaving my internals alone. (I hope. LOL)
Not sure where to put this... I'm running Mirage 7.2.0 kang internally. I've built several sdcards to boot 7.1 and ran them before taking the plunge to internal. I've never had any problems I couldn't fix on my own by reading more.
This had me stumped though. I want to keep running Mirage and boot CM9 off an sdcard. I've built the card using the recent img from samiam's new post in the nightlies thread. Every thing went fine until the final boot. I'm stuck on the screen that says press the android to continue. When I press it an error comes up saying it failed. I press OK and it repeats. Rinse and repeat...
I just had a thought that I may have used the gapps with the onetimeinitializer which could be the problem.
I'll check back in after I redo this.
Sent from my NookColor using XDA App
I had the same problem, but got past that point by using the modified Gapps from the 1st post of this thread, http://xdaforums.com/showthread.php?t=1444943 . That should work for you.
Turns out that the device ids have also changed on my NC, which is why ADB wasn't working for me. I had to add new entries into android_winusb.inf with USB\VID_18D1&PID_D002 instead of USB\VID_2080&PID_0002.
The signed apk works for me somewhat. It displays all the info correctly using the framework modification I mentioned a few posts ago to get location working. However, I cannot change to show Fahrenheit instead of Celsius for the temperature.Couldn't get the Asus weather widget to work, can someone else try it?
http://xdaforums.com/showthread.php?t=1048959
Quote" Originally Posted by mikelav456 View Post
I'm trying to flash Samiam's other zip files (the telephony permissions fix and the animation fix) by adding "update-" to the file name, putting it on the boot partition, and booting into recovery, but that doesn't seem to work (I'm running CM9 off an microSD using verygreen's method).
Is there another way to-correctly-flash these files?
Thank you in advance.
its 'update-cm-*' and whatever else comes after is fine.
Racks "end Quote
Tried it, seemed to run fine but didn't work?
Hi Guys -
I want to start out by acknowledging that I realize that no one owes me anything. I bought a Nook because I thought it would be fun to see just what could be done with Android on a somewhat different device. No one held a gun to my head and I may have misconstrued what the goals of this community were. I own my own disappointment and am not blaming anyone else.
I was amazed by the Gingerbread ROMs that were initially available, and it seemd to me that in no time we would have updated (read Honeycomb, ICS, and JB) Roms that would continue to amaze
It has taken OEMs (HTC/Samsung) in the region of 6-9 months to update some devices from GB to ICS, so "in no time" wasn't really going to happen when we work on this in our free time for fun. ICS was a huge overhaul and required a lot of changes - some of which we still don't have source code that we can use (such as hw accel/omx on ICS).
I did not think that Honeycomb should have been abandoned when ICS was still a glimmer in the eyes of its developer parents, and I do not think that ICS should be abandoned either now. I am totally confused by the lack of progress in bringing these later ROM to the state where GB was a year ago. The only thing I can think of is that Android is so much of a moving target that no one can spend the time necessary and that the changes to Android in moving from GB to ICS to JB have actually made it harder to adapt the OS to the hardware bits of the Nook Color. This, if true, is a major disappointment in the development of Android.
Honeycomb wasn't even started, so it wasn't abandoned. deeper-blue did some great work porting from the SDK but at best it was a "proof-of-concept" - honeycomb was not open source and therefore it was never really worked on. We also haven't abandoned ICS, while working on JB we're still pushing relevant fixes to ICS so that people can continue to get the best ICS experience we can offer (https://github.com/fat-tire/android_device_bn_encore/commits/ics)
In my mind, the philosophy of open source software is to make adaption and adoption easier, not harder; and to celebrate those developers who try to do so, rather than keeping them in the dark and withholding necessary information and code from them.
I'm not sure who you're referring to in terms of keeping people in the dark? All our work has been open in the nookcolor chan on IRC or in the dev thread here on xda.
My initial reaction, when faced with such disappointment was to set up a Linux box (I chose Knoppix poor man's install for personal reasons) and to download andbot and the sources. I have gotten through the initial glitches and believe I have the full set of sources, the open and proprietary ones. Now it seems that the java runtime available in Knoppix is not appropriate (1.6.0 vs SE 1.6.0). I am running down the errors in the building in brunch to see if I can get around the problems. Java SE when downloaded from Debian and reinstalled, says that I already have the proper version.
Knoppix? Really?
I am willing to spend some time at this to get it working, but my dream of a more stable ICS or JB seems to be receding into the mists.
Of all the ROMs I have tried (and I've tried most of them) I think that (believe it or not) Honeycomb gave the best balance of tablet loveliness and usability. So I'm afraid I am currently asea.
I think you're mostly alone there..
I guess I will buy a Nexus 7 so that my wife doesn't have to keep asking me why my tablet doesn't work. It just seems like admitting defeat.
Thanks to all who have spent countless hours and who are probably just as frustrated as I am. Sorry for the rant.
Most of us aren't frustrated, we do this for fun to see what we can bring to this device, knowing it's a challenge and maybe never going to be perfect. If you want a fully functional tablet today - then I would also recommend the Nexus7 as being the device for you.
Fattire put that line in the build.prop for everybody last night (via the awesomizer, LOL). What is it? Is he pulling our chain again?
I have been trying to use the CWM 5.5.0.4 taken from Sam's server in recoveries. It keeps giving me recovery.fstab errors for cache saying NULL is not a proper option and then only backs up /boot. Is there a working version somewhere? Fattires original post used Megaupload and is dead.