• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[DEV] CM11 Work-In-Progress

Search This thread

drmarble

Senior Member
Jul 27, 2011
351
1,009
I have fixed part of the problem with hardware/ti/omap3. The conficts were between omx and the ion implementation. I just removed the omx directory. Some additions from Rhyre on github are included. The tree is here:
https://github.com/drmarble/android_hardware_ti_omap3/tree/no-omx

I will be including zram swap in the encore device tree. It doesn't cause problems and we sure are short on memory.

Keep reading the README.md file on github.
Enjoy
 

bowguy

Senior Member
May 7, 2012
198
152
Ventura
I have fixed part of the problem with hardware/ti/omap3. The conficts were between omx and the ion implementation. I just removed the omx directory. Some additions from Rhyre on github are included. The tree is here:
https://github.com/drmarble/android_hardware_ti_omap3/tree/no-omx

I will be including zram swap in the encore device tree. It doesn't cause problems and we sure are short on memory.

Keep reading the README.md file on github.
Enjoy

I will try to build this weekend and if successful see if it runs on a SD card.
Thanks!!
 
  • Like
Reactions: fattire

drmarble

Senior Member
Jul 27, 2011
351
1,009
I should add that I do Engineering builds. They give more debugging.
lunch cm_encore-eng
time make -j9 bacon 2>&1 | tee make.log
I have an I7 now so I use -j9. You may need fewer, or more but that makes me jealous.
I guess you could also use brunch cm_encore-eng.
I don't know if userdebug will work. I'll take the greater debugging over performance for now.
Enjoy
 

drmarble

Senior Member
Jul 27, 2011
351
1,009
Do not trust the recovery that may or may not be built with this rom. It should not work since I disabled lots of recovery stuff just to finish the build. I use the cwm recovery steven676 posted earlier in this thread.
I have made some more progress. It now wakes with the home (n) button. I reenabled zram. I got hwc running; use my hardware_ti_omap3. I am working on sound now and hope for inspiration to get settings -> developer options fixed.
Good luck with an SDcard install. I have included all of steven676's changes to enable it but I haven't tested. I just do emmc installs.
 
  • Like
Reactions: fattire

steven676

Senior Member
Nov 24, 2011
593
2,430
Do not trust the recovery that may or may not be built with this rom. It should not work since I disabled lots of recovery stuff just to finish the build. I use the cwm recovery steven676 posted earlier in this thread.
I have made some more progress. It now wakes with the home (n) button. I reenabled zram. I got hwc running; use my hardware_ti_omap3. I am working on sound now and hope for inspiration to get settings -> developer options fixed.
Good luck with an SDcard install. I have included all of steven676's changes to enable it but I haven't tested. I just do emmc installs.

Actually ... and I've been meaning to post about this for a while ... CM now autobuilds recoveries. If someone could test http://download.cyanogenmod.org/get...50831-SNAPSHOT-XNG3CAO3FN-encore-recovery.img (it's a ZIP file -- rename it to .zip, unpack it, and push kernel to /boot/uRecImg and ramdisk-recovery.ub to /boot/uRecRam), that would be greatly appreciated. (The version number should be newer, but it should otherwise be equivalent to the existing hand-build recoveries I've been posting.)
 
  • Like
Reactions: bowguy

bowguy

Senior Member
May 7, 2012
198
152
Ventura
I got a little stuck. Here is my roomservice:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="drmarble/android_device_bn_encore" path="device/bn/encore" remote="github" revision="cm-12.0-wip1" />
<project name="steven676/ti-omap-encore-kernel3" path="kernel/bn/encore" remote="github" revision="encore-omap3-3.0.y-l-backports" />
<project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" remote="aosp" revision="refs/tags/android-4.4.4_r2"/>
<project name="drmarble/proprietary_vendor_bn" path="vendor/bn" remote="github" revision="cm-12.0-wip" />
<project name="drmarble/android_build" path="build" remote="github" revision="encore-12.0" />
<project name="drmarble/android_hardware_ti_omap3" path="hardware/ti/omap3" remote="github" revision="no-omx" />
</manifest>


But trying to sync I get a:
fatal: duplicate path build in /home/bowguy/cm12/android/system/.repo/manifest.xml

I think I need to remove a project in roomservice. Any help would be appreciated.
Thanks
 

drmarble

Senior Member
Jul 27, 2011
351
1,009
I got cm-12.1 working. Or, at least booting.
Cb3S0oF.png

It works with no sound, no hw acceleration and unfortunately, no browser. Chromium crashes with a ERROR :GL_OUT_OF_MEMORY : glBufferData: . It works in cm-12.0. I have uploaded changes for 12.1 on github. Building directions are the same. Just find the correct directories. I renamed some of the 12.0 ones to include 12.0 in the branch names.
I left out an important change to frameworks_base. This is from the README.md file. To deal with data/media and sdcard installs a change to frameworks/base is required. It was written by steven676. I have incorporated it here:
https://github.com/drmarble/android_frameworks_base/tree/storage-config-12.0
I have found that building as userdebug instead of eng makes the builds much faster. Quadrant scores doubled to ~1300.
Sorry about the difficulties with the local manifest. When I am modifying an existing tree I use git commands, eg:
git remote add drmarble https://github.com/drmarble/android_frameworks_base.git
then
git fetch drmarble
This gets all my branches.
Finally git checkout drmarble/storage-config-cm12.1
This will get reset to the default repo branch when you repo sync (unless you have made uncommitted changes). Just checkout again.
This method is handy when you build for multiple devices on the same source tree. You can just checkout any changed directories for a specific device. I think that there are even better ways involving repo and repo branches. I have enough trouble understanding git. I use shell scripts for my builds and just put the checkout code in there. eg:
Code:
pushd kernel/bn/encore
git checkout sluo/encore-omap3-3.0.y-l-backports
popd
or for local branches
Code:
pushd frameworks/base
git checkout storage-config-cm-12.1
popd

pushd hardware/ti/omap3
git checkout no-omx
popd
Sorry about forgetting about frameworks/base.

---------- Post added at 12:15 AM ---------- Previous post was at 12:03 AM ----------

Just a warning. I disabled boot animation because we can't both optimize for art and animate a boot at the same time. It will just sit on a black screen for several minutes before informing you that it is optimizing apps. Plugging in a usb cable and running adb logcat will encourage you that it isn't frozen. I know that eng builds automatically allow adb as root on first boot. I think I managed to set it up for userdebug builds too so you don't have to authenticate on a blank screen.
 

bowguy

Senior Member
May 7, 2012
198
152
Ventura
CM-12.0 build

OK I have a clean build using drmarble's directions in a local_manifest. I will try to boot it on a SD install later tonight. If I can I will also test steven676's recovery.

Edit: Boot looping. Seems to be trying as there is no boot animation but I will keep trying.. might be running out of memory or space.

New edit: Seems to be working now. I flashed the zip using Leapinlar's script which apparently fought with it. I snuck the zip onto the card via an emmc installation of 10.2 then booted into steven676's new recovery and flashed it that way.
 
Last edited:

drmarble

Senior Member
Jul 27, 2011
351
1,009
OK I have a clean build using drmarble's directions in a local_manifest. I will try to boot it on a SD install later tonight. If I can I will also test steven676's recovery.

Edit: Boot looping. Seems to be trying as there is no boot animation but I will keep trying.. might be running out of memory or space

I am not certain about the SD installs working. I used steven676's commits from his github that are supposed to enable it but I haven't tried. His tree was for cm-11.0 and I used that as the basis for my changes. I haven't tested it on either cm-11.0 or cm-12.x. I expect you need his recovery.

I don't get any boot looping on emmc installations. Maybe your system partition is too small. I set it to require at least 600MB or some such size. I have 1GB. It does taks a long time to dexopt with no applications installed, so be patient. You should look at the logcat or /proc/last_kmsg.

I hope you can get it working. It would be nice to have an sd card to switch to cm-12.x. I admit that I don't really use this tablet for anything except developing so having a mostly useless cm-12.1 install doesn't bother me.

I tried side loading dolphin browser. It works. It is a bit slower than cm-11.0 but it does run. I don't know what is causing the GL out of memory error with chromium. I don't know why there is no sound. I am looking at the Acclaim code to see if there is stuff we can use. I need to get better at building and pushing individual libraries. It takes 15 minutes to get it booting after sideloading a rom. And that is with the apps already optimized. That is a long and boring development cycle. Compiling from clean only takes 16 minutes.
 
  • Like
Reactions: glockman4519

bowguy

Senior Member
May 7, 2012
198
152
Ventura
SD Install

Screenshot_2015-09-23-10-03-44.png
Similar issues to what drmarble is having. Developer options is crashing settings every time but I got adb enabled.
Installing Open GAPPS nano now...
 
Last edited:
  • Like
Reactions: drmarble

drmarble

Senior Member
Jul 27, 2011
351
1,009
Similar issues to what drmarble is having. Developer options is crashing settings every time but I got adb enabled.
Installing Open GAPPS nano now...

Great news and good job. Were there any tricks to get the sd build working? Or did you just need the new recovery?
I got developer settings working on cm-12.1. I thought they worked on cm-12.0 with a user-debug build but apparently I was mistaken.

It is always nice to see someone else building with your code. It makes it feel less like you are coding into a void. If I can get anything else running I will let you know here and upload the changes to github.
 
  • Like
Reactions: dombeef and bowguy

bowguy

Senior Member
May 7, 2012
198
152
Ventura
Great news and good job. Were there any tricks to get the sd build working? Or did you just need the new recovery?
I got developer settings working on cm-12.1. I thought they worked on cm-12.0 with a user-debug build but apparently I was mistaken.

It is always nice to see someone else building with your code. It makes it feel less like you are coding into a void. If I can get anything else running I will let you know here and upload the changes to github.

For the build I did an init to 12.0 and this is the roomservice.xml:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="drmarble/android_device_bn_encore" path="device/bn/encore" remote="github" revision="cm-12.0-wip1" />
  <project name="steven676/ti-omap-encore-kernel3" path="kernel/bn/encore" remote="github" revision="encore-omap3-3.0.y-l-backports" />
  <project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" remote="aosp" revision="refs/tags/android-4.4.4_r2" />
  <project name="drmarble/proprietary_vendor_bn" path="vendor/bn" remote="github" revision="cm-12.0-wip" />
  <remove-project name="CyanogenMod/android_build" />
  <project name="drmarble/android_build" path="build" remote="github" revision="encore-12.0" />
  <project name="drmarble/android_hardware_ti_omap3" path="hardware/ti/omap3" remote="github" revision="no-omx" />
  <remove-project name="CyanogenMod/android_frameworks_base" />
  <project name="drmarble/android_frameworks_base" path="frameworks/base" remote="github" revision="storage-config-12.0" />
</manifest>

Build was just brunch encore after a clobber.

Initial install is a pain. First get a 16 GB SD card (I don't think an 8GB will work). Burn Leapinlar's image onto it.
http://forum.xda-developers.com/attachment.php?attachmentid=2787369&d=1402239353
See:
http://forum.xda-developers.com/showthread.php?p=32921666#post32921666
for directions. Now you need to copy cm-11-20141008-SNAPSHOT-M11-encore.zip located here:
http://download.cyanogenmod.org/?device=encore&type=snapshot
onto the root of the SD card. Do not use anything later than that as it will not work. Insert the card into the Nook and boot it up. This will partition the card and install cm-11. Nothing different here that isn't described on LeapinLar's page. Next is the issue that had me stumped. If you copy the new CM-12 ROM in the boot directory, LeapinLar's script will install it but not correctly. It will boot loop. In addition, the new recovery can't see the zip on the root of the SD. My Nook has CM-10 installed on EMMC so I booted to EMMC, connected via USB as media device and copied the CM-12 zip to the nook. You then need to copy the zip to somewhere on /storage/sdcard0. File manager can do this.
Shut down the Nook and pull the SD card. Copy steven676's new recovery onto the root directory, reinsert the card and boot into SD recovery. This gives us a recovery that can see the sdcard0 partition and the zip.
Install the zip as usual and then boot up. That is how I got the thing working. However, installing GAPPS really is giving me fits at this point.

Thanks for all your great work!

Let me know if you want me to try a 12.1 build. I can get to that next week.
 
Last edited:

bowguy

Senior Member
May 7, 2012
198
152
Ventura
Actually ... and I've been meaning to post about this for a while ... CM now autobuilds recoveries. If someone could test http://download.cyanogenmod.org/get...50831-SNAPSHOT-XNG3CAO3FN-encore-recovery.img (it's a ZIP file -- rename it to .zip, unpack it, and push kernel to /boot/uRecImg and ramdisk-recovery.ub to /boot/uRecRam), that would be greatly appreciated. (The version number should be newer, but it should otherwise be equivalent to the existing hand-build recoveries I've been posting.)

Your recovery seems to work fine on an SD. Two questions. When you install a zip it replaces everything in system? The reason I ask is before on the CM11 recovery when you install a ROM it does not remove your apps. With this recovery when I reflashed the CM12 ROM it removed the Gapps as well. This might be because of all the other issues involved.

Second - on an SD install does the wipe/factory default option just affect the card? Does it keep the partitions and directories? That would be handy for testing new ROMs

Thanks!

---------- Post added at 07:38 AM ---------- Previous post was at 07:35 AM ----------

I haven't had time to really look into this (dmesg and logcat) but Gapps is really having issues with this build. Standard install boots up OK and works just fine with a few bugs. WiFi works, browser works. When I flash Gapps (both Open GAPPS and 20150404-minimal) the thing just dies. Very laggy and can't create a Google account.
 

drmarble

Senior Member
Jul 27, 2011
351
1,009
I have similar problems with Gapps in cm-12.1. It seems to work ok except for no sound and the chromium browser crashing. With gapps, other things still work the same but PlayStore just freezes on the sign in screen and then crashes. It produces a chromium error.
I can get into devoloper settings. No IBackupPassword errors. Quadrant is over 1600. Dolphin browser runs but agonizingly slowly.
I am going to switch back to cm-12.0 and see if it will make things easier to fix. I know that some other devices have had trouble with chromium.I suspect that the GL errors stem from not having any omx drivers. I believe they are important. I get the GL errors from the browser and from PlayStore. There are new omx drivers from the wearable branch but it isn't a simple plug and play. That uses a very different kernel (3.10?).
I will work once again on getting the ti/omx drivers to compile.
Thanks for doing the testing. Maybe we can figure out what to do next. Right now, isn't it fun to see Android 5.0 showing on the about tablet screen? Pretty good for a 5 year old e-reader.
 

drmarble

Senior Member
Jul 27, 2011
351
1,009
I am making progress on this. Gapps still crashes both cm-12.0 and 12.1. Sound is still broken. Browser crashes on cm-12.1. This doesn't sound like much but we can now compile the omx branch and try to get accelerated graphics. These changes are here: https://github.com/drmarble/android_hardware_ti_omap3/tree/cm-12.0-wip1 (identical branch on cm-12.1-wip1) and the referenced device/bn/encore *.omx1 branches referenced below.
I also better understand dexpreopt (see: https://source.android.com/devices/tech/dalvik/configure.html ) and booting is now much faster. These changes are here: https://github.com/drmarble/android_hardware_ti_omap3/tree/cm-12.0-wip1 and https://github.com/drmarble/android_device_bn_encore/tree/cm-12.0-omx1 . Just change 12.0 to 12.1 for cm-12.1. My modified vendor/cm has encore1 for cm-12.0 and encore-cm-12.1 for cm-12.1.

You can get into developer settings without crashing. I backported a change to packages/apps/Settings from cm-12.1. I submited this change to gerrit http://review.cyanogenmod.org/#/c/110370/ but for now you can either apply the patch after you repo sync or use my version at https://github.com/drmarble/android_packages_apps_Settings/tree/encore-cm-12.0 . No changes are required for cm-12.1.

For some reason, cm-12.0 isn't building today like it did yesterday. CM-12.1 builds. I will figure this out and push fixed trees to github.
 

bowguy

Senior Member
May 7, 2012
198
152
Ventura
For some reason, cm-12.0 isn't building today like it did yesterday. CM-12.1 builds. I will figure this out and push fixed trees to github.
It can't find system/autosuspend.h in frameworks/base/services/core/jni:

com_android_server_am_BatteryStatsService.cpp:#include <suspend/autosuspend.h>
com_android_server_power_PowerManagerService.cpp:#include <suspend/autosuspend.h

Also missing SkBitmap.h, SkColor.h and SkRegion.h in frameworks/base/core/jni/android/graphics. Found those in external/chromium_org/third_party/skia/include/core

Somehow the entire skia library is not included.

giving up - trying to compile 12.1 now
 
Last edited:

drmarble

Senior Member
Jul 27, 2011
351
1,009
My settings patch to cm-12.0 was merged so you don't have to do anything with packages/apps/Settings to get into developer settings. I will take down my fork of the repository once I remember how to do so.
I have made a few other changes which haven't improved functionality. I will push those. I changed the ion.h files for the device. We still crash with GL errors when trying to open the browser or log into our google accounts. There are still big problems with graphics/ion/GL. We still need more work on hardware/ti/omap3.
I hae started getting an error about ion_user_handle_t or some such thing. I have changed the Android.mk file in system/core/libion to have Werror changed to Wno-error. This keeps the warnings from being turned into errors so the build finishes.
Please not that there are constant changes to the cm-12.1 build tree. Folks keep adding functionality and bug fixes. These include updates to the directories that I forked. I have to keep running " git pull github cm-12.1 " in these directories to avoid build errors. This isn't a problem with cm-12.0 since nobody is really doing much with it anymore. The git pull command takes all the recent changes from the cm-12.1 tree and puts it on top of my changes. This keeps these branches up to date. I upload my updated branches to github but I don't work on this every day. Maybe I will make a separate patch for each directory that can just get added to the current tree. This works u ntil the tree is so different than what I made the patch from that the patch no longer works. Having the git pull command is a strong argument for using git remote add for my changed branches rather than removing the cm branches and putting mine into roomservice.xml. It also gives you a clean cm directory tree if you want to build for multiple devices.
 
  • Like
Reactions: bowguy

Top Liked Posts

  • There are no posts matching your filters.
  • 210
    This 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 :cool:

    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 :eek:

    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​


    icsncwifi3.jpg

    icsncwifi2.jpg
    160
    UPDATE 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:
    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---------------------

    ncicsss1.png


    About screen, wifi scanning, & bluetooth....
    icsnc.jpg
    icsncwifi1.jpg
    icsncbt.jpg


    icsnc4.jpg
    ncicsss.png
    icsnc5.jpg
    icsnc6.jpg

    ncicsss2.png
    ncicsss5.png

    wpvW3.png
    71
    Some 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.
    59
    Some good stuff...

    fattire/dalingrin: aren't the new EGL libs from the defy very good news?

    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:

    icsnc11.jpg


    That's a 1543 fwiw. I'm guessing it can do better. But whatever.

    Gapps works too. Like Maps...

    icsnc12.jpg


    Gmail (with multiple panes/fragments)...

    icsnc7.jpg


    Market...

    icsnc10.jpg


    And the tablet apps install directly to the tablet from the web market. No questions or difficulty...

    icsnc8.jpg


    icsnc9.jpg



    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.
    56
    New 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