Thank you for the information.
Also thanks to you and Dalingrin for working on the ICS port.
Thank you for the information.
Also thanks to you and Dalingrin for working on the ICS port.
if your running linux or mac osx you can get it set up easily but if your running windows you have to ether setup a dualboot or use a VM to run linux and get a workstation set up
"*Fully accelerated composition of the UI - this is not likely and may be dependent on 3rd party closed source EGL libs getting updated"
He got it from the topic post.
I wonder what the chances of at least getting Honeycomb onto the NC, if ICS is being so finicky?
Thanks so much!
This will be awesome once it hopefully gets stable!
Thanks for the work!
I and allot of everyone else is really appreciative!
Sent from my Samsung Captivate
This will be awesome once it hopefully gets stable!
Thanks for the work!
I and allot of everyone else is really appreciative!
Sent from my Samsung Captivate
Wow, I definitely didn't catch that, it must have been updated since I last checked. Well that sucks...
I build cm7 from source all the time. Setup using the guide posted above. My Linux experience is limited, but I'm learning quick. I'm going to try and just swap out the source link but I'm pretty sure there is more to it than that. Any info would be great. Thank.
Sent from my Touchpad using XDA App
Sent from my Touchpad using XDA App
As long as it's as smooth as CM7 is then I'll be happy, because the real selling point for ICS for me is finally being able to run the "HD" or tablet versions of many apps that make much better use of the 7" screen than the phone-oriented apps that are compatible with CM7
^THIS
to be honest i dont like the blown up phone apps on my nook(IE netflix sometimes reverts back to phone ui) and i would love to have a full tablet UI for all my apps and to finally have better tabbed browsing(gingerbread tabs suck)
I'm sure that once we get a stable release, with time, patching, and some dirty hacks everything will turn out fine...
Also, I'd try and build the source since I am already running linux, but Im sure that my puny 1.2ghz cpu core2duo and 64gb ssd won't really finish in a reasonable time frame... hopefully someone can get it compiled and put up a video, then we can see what the UI will look like, or at least what it's like at the moment.
Also, I'd try and build the source since I am already running linux, but Im sure that my puny 1.2ghz cpu core2duo and 64gb ssd won't really finish in a reasonable time frame... hopefully someone can get it compiled and put up a video, then we can see what the UI will look like, or at least what it's like at the moment.
Last edited:
im tempted to compile and post a video but im to lazy to boot into my linux partition
I may have to set my linux partition up tomorrow. Depends if I get trapped in skyrim or not :-!
Sent from my GT-I9100 using XDA App
Well this is annoying. Have everything synced up, cloned fattire's git, lunch blah blah and finally onto make to have this.
Code:
============================================
PLATFORM_VERSION_CODENAME=AOSP
PLATFORM_VERSION=4.0.1.2.3.4.5.6.7.8.9
TARGET_PRODUCT=full_encore
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=OPENMASTER
============================================
find: `omapmmlib/java': No such file or directory
find: `omapmmlib/java': No such file or directory
build/core/base_rules.mk:78: *** Module name: tiwlan.ini
build/core/base_rules.mk:79: *** Makefile location: hardware/ti/wlan/wl1271/config
build/core/base_rules.mk:80: *
build/core/base_rules.mk:81: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:82: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:83: *
build/core/base_rules.mk:84: * optional, debug, eng, tests, samples
build/core/base_rules.mk:85: *
build/core/base_rules.mk:86: * If the module is expected to be in all builds
build/core/base_rules.mk:87: * of a product, then it should use the
build/core/base_rules.mk:88: * "optional" tag:
build/core/base_rules.mk:89: *
build/core/base_rules.mk:90: * Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:91: * Android.mk for the affected module, and add
build/core/base_rules.mk:92: * the LOCAL_MODULE value for that component
build/core/base_rules.mk:93: * into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:94: * makefile(s) where it's necessary, if
build/core/base_rules.mk:95: * appropriate.
build/core/base_rules.mk:96: *
build/core/base_rules.mk:97: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:98: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:99: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:100: * build/target/product/core.mk
build/core/base_rules.mk:101: *
build/core/base_rules.mk:102: *** user tag detected on new module - user tags are only supported on legacy modules. Stop.Looks like the module has a legacy tag. Try changing the tag from user to eng.
Disclaimer: I don't have a lot of experience with Android development.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
210This thread is meant for discussion of the in progress Kit Kat port for the Nook Color.
Updates
If you want updates on the progress you can check this post and fattire's post immediately folllowing this. We'll both be posting updates periodically here.
You can also follow me on twitter @dalingrin
You can follow fattire @ fat__tire
Please don't ask me for ETAs or status updates. I will post them as I post them
Source code
Device source code will be temporarily hosted on fattire's github @ http://github.com/fat-tire/android_device_bn_encore
Things to expect
Nothing
Things not to expect(for now)
*Fully accelerated composition of the UI - this is not likely and may be dependent on 3rd party closed source EGL libs getting updated
*Accelerated video playback and overlay - This has changed quite a bit and may take some time to get working
*Polished release soon - Don't ask, don't tell
160UPDATE 11/24/13 -- So CM 11.0 is out and building nicely on Nook Color. Look here for the link to the build instructions. If you are building CM 11, you will probably want to use cm-11.0 as the name of the branch when initializing.
STATE OF THE UM, STATE OF THINGS
So I was curious how many noob types, who always beg for nightlies and builds and stuff-- I wondered if they (you?) could be encouraged to learn and get involved in the process of building Android. Which, as I've expressed in an infamous ramble, I think is important to the future of our culture and how it it deals with technology-- and who will control it. So I asked normal non-dev people to try building-- to give it a shot.
I think the experiment, which quickly became OUR experiment, has been a massive success. Far beyond what I'd imagined. Hundreds of people have gotten off their asses-- many of whom had clearly never touched Linux or a compiler before, and most were successful in building CM9/ICS from scratch.
That is not a small deal. And no, it's not just following a list of instructions by rote. People had to think about and solve a million different problems-- installing VMs, updating packages, choosing linux distributions, understanding the command line, etc. Scary stuff if you've never done any of these things before.
So it's been a month or so now, and I think we've reached the stage where aside from minor enhancements and fixes, the build looks pretty sweet. The major stuff is there and working. Yeah, DSP/hardware-accelerated video is something we're going to have to wait for TI to add to their omap3 repositories, and there are likely other things wrong. I've heard rumors of sleep-of-deaths or quicker-than-usual battery consumption, etc. There are numerous things to be fixed, but these are all issues that may or may not be worked out over time... As major new enhancements come to the CyanogenMod project, they will come to the encore version, and your build, automatically.
No secret links this time. As before, I'll spell out the bottom line explicitly for ya here in the middle somewhere. And I'll even underline it.
I hereby decree, in so far I am able, my humble request for "no posted builds".... is ended.
Back to your regularly scheduled forum. Go to it.
I encourage you to pass any valuable improvements you make to the code "upstream" via the gerrit review system at review.cyanogenmod.com for inclusion in the main CM project. You already know how it works. And some, God love ya, have already started. Not everything you submit will get accepted, but it's a good way to "pay it forward". And in the same vein, consider helping someone on IRC. Or be a big brother or big sister. Or donate blood. And to quote Steven Soderbergh, or whomever, you don't have to brush ALL your teeth, just the ones you want to keep.
Thanks as always to dalingrin, keyodi, nemith, verygreen, arcee, deeper-blue, unforgiven512, the gang on irc, and the CM Team generally for keeping this fun. And thank YOU for the lulz, Internet.
ft
Remember, there's NOTHING quite like running your own build, piping-hot, and fresh from the oven.
----
I am also releasing a first pass at a how-to-build walkthrough. It is available here:
walkthru (rough draft)
This doc will be updated and evolve with your input. It is meant to help people feel confident that they can build an operating system from scratch, and hopefully encourage them to participate, learn, and even make contributions.
If you need assistance, you must rely on each other.
Here is an equally unreliable clockworkmod, v5.5.0.4:
uRecRam
You may be asking, where is the issue queue? There is no issue queue. You are on your own here.
Recent automated builds (unofficial, unsanctioned, untested, uneverything else) from Forum member Samiam303 is here.
-----------everything below this line is sorta old and outdated--------------
So there's apparently been some bit of controversy related to my request that people try to build themselves rather than someone posting a pre-made update.zip file. Let me go more into detail about what this experiment is about, at least from my perspective. But first, I do want to thank everyone for respecting the request so far-- I know it's not the traditional way of doing things, but I think it's been very fruitful and personally rewarding to see so many people who have never built jack before take on a project like this and be successful. I've received an enormous number of messages, both PMs here as well as in IRC, to the effect that this finally got them to try to build for the first time. It's introduced many people to actually using Linux, others may be having their first encounters with the command line, or git, or looking at source code, or learning about the build process in general. Whether or not the majority go on to become "devs" is irrelevant-- what I have been trying to encourage is curiosity and experimentation, and most of all a deeper understanding that your phones and "ereaders" are in fact full-fledged computers, not "appliances" or limited-purpose devices that others get to control. It's your property, and it can do a lot. There is an effort underway to discourage people from thinking of their devices this way or discouraging them from experimenting and learning with them. This IMO is an extremely harmful practice-- take a look at Cory Doctorow's recent speech on this subject. I could go on and on, but it seems important enough to me to make this request, and hopefully some of you are even subconsciously appreciating the awesomeness of what potential these general-purpose gadgets will have on society. So that's a lot of philosophizing, but there you go. And while I'm not naive enough to think that plenty of people aren't trading the file "under the table" at it were, for a variety of reasons, I do think that in a way they're cheating themselves; those who give building a shot are finding that learning is a reward unto itself. Those who are persistent, who pay attention, who don't give up, not only get a build at the end, plus the experience of doing it, plus the knowledge they picked up along the way-- they also discover things in the most unexpected of places, as in the link in the period at the end of the third sentence in this post. And while there's been some discussion of what a "dev" is and whether or not this is a gateway to bigger and better things, all I can assume is that if 5-10% of the people who built are intrigued enough to take it a step further, and maybe a step further than that... then we might end up with some new devs who appreciate the value of open source and whose contributions we can look forward to with eagerness in the future. Plus-- it's more fun this way.
I do hope this sounds good to everyone. If you understand what this post is about- no need for long, drawn-out elaborate responses... a simple "I got it" will do.
More source is forthcoming... Thanks to dalingrin, arcee, keyodi, nemith, Scepterr, unforgiven512, etc. Oh, and shh.
--------------------------
update-cm-9.0-0-encore-emmc-sneakpeek2-fullofbugs.zip
md5: 536d589c59ea5711a17a3d976f0638fa
update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs.zip
md5: 85294ad91e2601beb737cf723b9fb9d6
(note this URL is likely to change)
Note: You are advised NOT to try to install this. This update.zip will **overwrite** as in erase whatever data you have on your emmc, so if you are trying this, you are advised to back it up first so you can recover. Install entirely at your own risk, and do a factory wipe first. This software is likely to be terrible and cause problems including permanent data loss, hair loss, and/or the destruction of your property and the death of your pets. You assume all risks involved in your use-- or even attempted use-- of this file. I disclaim any and all responsibility for your decision to try it.
*** Really. This build is buggy. It is a work-in-progress. It is only a snapshot of where things stand right now, and it's possible it'll never go further. ***
here's what's working:
* bluetooth (pairing/file transfer only confirmed)
* wifi (full it seems but it's brand-new to the kernel so who knows how stable anything is)
* backlight
* accelerometer
* improved stability (but not perfect)
* gapps
* setcpu/overclock
* real data usage info (not stubbed out)
* battery levels/charging
* physical menu button
* touchscreen
* 3d games
* usb gadget in kernel (ie, mounting your sdcard to your computer)
* screenshots
* build system (to auto-create update.zips)
* sound
(note: for all the above features, you must build yourself! See below for rationale & more)
For sure not working yet:
* video
* full 2d acceleration (esp on complex web pages)
* and much much more
These things may/may not be added at some point in the future. You should have no expectations that they will. Anyone who asks for an ETA for something or other gets collectively stoned by the crowd.
I'm sometimes on #nookcolor in freenode.
Thanks to keyodi, unforgiven512, arcee, toastfch, d0nk`, dalingrin, nemith, the rest of the cm team/TD, and anyone else who I've forgotten. We stand on the shoulders of giants.
MUST READ:- Why there have been no additional zips posted lately.
- How to use Gerrit (the CM9 review system)
- how to make an update.zip
[*]beagleboard patches
Again, don't install this. And please don't "rom" this (as in change the font or background) and then ask for donations for your "hard work". This is a preview of a work in progress, not a final product, and it's not meant for people to use day-to-day. Don't be a ****. Thanks.
--------------------screenshots---------------------
About screen, wifi scanning, & bluetooth....
71Some thoughts...
So there's apparently been some bit of controversy related to my request that people try to build themselves rather than someone posting a pre-made update.zip file. Let me go more into detail about what this experiment is about, at least from my perspective. But first, I do want to thank everyone for respecting the request so far-- I know it's not the traditional way of doing things, but I think it's been very fruitful and personally rewarding to see so many people who have never built jack before take on a project like this and be successful. I've received an enormous number of messages, both PMs here as well as in IRC, to the effect that this finally got them to try to build for the first time. It's introduced many people to actually using Linux, others may be having their first encounters with the command line, or git, or looking at source code, or learning about the build process in general. Whether or not the majority go on to become "devs" is irrelevant-- what I have been trying to encourage is curiosity and experimentation, and most of all a deeper understanding that your phones and "ereaders" are in fact full-fledged computers, not "appliances" or limited-purpose devices that others get to control. It's your property, and it can do a lot. There is an effort underway to discourage people from thinking of their devices this way or discouraging them from experimenting and learning with them. This IMO is an extremely harmful practice-- take a look at Cory Doctorow's recent speech on this subject. I could go on and on, but it seems important enough to me to make this request, and hopefully some of you are even subconsciously appreciating the awesomeness of what potential these general-purpose gadgets will have on society. So that's a lot of philosophizing, but there you go. And while I'm not naive enough to think that plenty of people aren't trading the file "under the table" at it were, for a variety of reasons, I do think that in a way they're cheating themselves; those who give building a shot are finding that learning is a reward unto itself. Those who are persistent, who pay attention, who don't give up, not only get a build at the end, plus the experience of doing it, plus the knowledge they picked up along the way-- they also discover things in the most unexpected of places, as in the link in the period at the end of the third sentence in this post. And while there's been some discussion of what a "dev" is and whether or not this is a gateway to bigger and better things, all I can assume is that if 5-10% of the people who built are intrigued enough to take it a step further, and maybe a step further than that... then we might end up with some new devs who appreciate the value of open source and whose contributions we can look forward to with eagerness in the future. Plus-- it's more fun this way.
I do hope this sounds good to everyone. If you understand what this post is about- no need for long, drawn-out elaborate responses... a simple "I got it" will do.
More source is forthcoming... Thanks to dalingrin, arcee, keyodi, nemith, Scepterr, unforgiven512, etc. Oh, and shh.59Some good stuff...
Not especially. We've had egl working on nook for about two weeks now. It just hasn't been public. The changes are pushed to frameworks/base now, and the defy is just using the flag(s). The code in questoin, by arcee I believe, was pushed up yesterday, which means everyone else will get the fast blue stuff seen in the screenshots. I tested it and some other stability stuff today, and I'm pushing it tonight/this morning. Anyone building now should notice a difference. The sacrifice for stability is a loss of some accelerated 2d graphics... but trust me, this is the best combo so far, and that other stuff can come later.
The big effort the last two days has been w/the kernel. After MANY hours of f'ing up, I finally got the appropriate netfilter working in 2.6.32 which means I can finally finish stuff like this:
That's a 1543 fwiw. I'm guessing it can do better. But whatever.
Gapps works too. Like Maps...
Gmail (with multiple panes/fragments)...
Market...
And the tablet apps install directly to the tablet from the web market. No questions or difficulty...
Neat. So here's what's working:
* bluetooth (only pairing is confirmed)
* wifi (full it seems but it's brand-new to the kernel so who knows how stable anything is)
* backlight
* accelerometer
* improved stability (but not perfect)
* gapps
* setcpu/overclock
* real data usage info (not stubbed out)
* battery levels/charging
* physical menu button
Not working yet:
* sound (dalingrin's gonna start this I think. Arcee has code to support legacy drivers I believe.)
* video
* full 2d acceleration (esp on complex web pages)
* usb gadget (which means screenshots too I think)
* build system (to auto-create upgrade.zips)
I'm pushing up most of what I have at the moment, including the test kernel-- I'll try to check that in tomorrow but it's a mess. It's been an all-night effort, so I'm sure stuff that I think works great will turn out to be a total dud when people actually try it.
I also wrote up a "how to build" walk-thru a couple days ago. But it'll need to be updated.
Still, not bad.56New Kernel
Well, we decided to push the 2.6.32.59 kernel and wifi module into the repo. So, eyeballer's and Samiam303's builds should have the latest kernel by tomorrow.
What's Fixed
- keyboard layout issues and key sizes
- Wifi module preventing sleep and pinning cpu at max
- wifi SOD - we'll see
What's New
- PVR drivers backported from the omap3-3 kernel. *non-opengl versions may notice increased 3d scores in benchmarking. No noticeable improvement in opengl builds
