[DEV] CM11 Work-In-Progress

Search This thread

Samiam303

Senior Member
May 15, 2010
239
375
Cleveland
www.sphsolutions.net
There is no build-bot working yet. All of these so-called "nightlies" are unofficial manual builds built by users. And you may be right that they are identical from night to night.

That's not quite true. It's not the official CyanogenMod buildbot, and it's not using the piece of software called "Buildbot", but my (and I imagine probably Eyeballer's too) nightlies are built by an automated script I wrote. They are built whether I'm home or not, every night at midnight -- and yes, that's whether anything has been changed or not, so some are probably identical.
 

newellj79

Senior Member
Jan 2, 2011
2,378
298
OnePlus 8
I get sods all of the time. Im on a build i put together yesterday but I've had them since I started running ics. Awhile back somebody suggested I get rid of weather widgets, so I've done that. I also have wifi policy set to always be on. If anybody, had a answer, even a paid app. I would really appreciate it. Thanks guys...
 

leapinlar

Senior Member
Oct 18, 2006
8,873
3,878

bigbob23

Senior Member
Feb 21, 2011
272
34
Seattle area
I've been manually switching wifi on and off and have only seen one instance of SOD with ICS. With the current status there are fewer steps to turn wifi on/off and I can live with that.
 

leapinlar

Senior Member
Oct 18, 2006
8,873
3,878
I get sods all of the time. Im on a build i put together yesterday but I've had them since I started running ics. Awhile back somebody suggested I get rid of weather widgets, so I've done that. I also have wifi policy set to always be on. If anybody, had a answer, even a paid app. I would really appreciate it. Thanks guys...
Leaving wifi on all the time is what leads to SOD. With wifi on and the screen off, it tries to deep sleep. Somehow wifi and deep sleep get tangled up and it locks, ie SOD. See my post above for a temporary fix until the devs solve it.
 

newellj79

Senior Member
Jan 2, 2011
2,378
298
OnePlus 8
Leaving wifi on all the time is what leads to SOD. With wifi on and the screen off, it tries to deep sleep. Somehow wifi and deep sleep get tangled up and it locks, ie SOD. See my post above for a temporary fix until the devs solve it.

Thanks!! Just downloaded the patch. After flashing this i should be able to leave wifi set to always be on and not have sod problems right? Will report back tomorrow with an update...
 

leapinlar

Senior Member
Oct 18, 2006
8,873
3,878
Thanks!! Just downloaded the patch. After flashing this i should be able to leave wifi set to always be on and not have sod problems right? Will report back tomorrow with an update...
You may have one occasionally. I have had only one since I applied the patch, even with wifi on all the time.
 

Awats

Senior Member
Apr 24, 2011
160
8
That's not quite true. It's not the official CyanogenMod buildbot, and it's not using the piece of software called "Buildbot", but my (and I imagine probably Eyeballer's too) nightlies are built by an automated script I wrote. They are built whether I'm home or not, every night at midnight -- and yes, that's whether anything has been changed or not, so some are probably identical.

I stand corrected! ;)
 

fattire

Inactive Recognized Developer
Oct 11, 2010
2,280
6,473
www.eff.org
Would appreciate if someone can give me a basic explanation of what the effect of the latest Commit Entry by Keyodi for Jan 31st is........"Remove bootloader from reboot menu." Thanks, I am far from a dev and trying to learn what I can. :p

https://github.com/fat-tire/android_device_bn_encore/commits/ics

Mike T

This removes the "bootloader" option which was one of the options when you press and hold the power button and get the shutdown/reboot menu.
 

webdroidmt

Senior Member
Dec 20, 2011
1,674
1,156
NJ
This removes the "bootloader" option which was one of the options when you press and hold the power button and get the shutdown/reboot menu.

Thanks for the reply but I guess I'm a bit dense here. On CM7 I don't recall a bootloader option on the power menu, is this something new in CM9?

Thanks for your patience.

EDIT: Ok, figured out the Reboot/Bootloader but what was the purpose of removing it?
EDIT2: Question answered, it's not needed and general cleanup. Thanks to Keyodi for his courtesy and explanation.

Mike T
 
Last edited:

fattire

Inactive Recognized Developer
Oct 11, 2010
2,280
6,473
www.eff.org
Are you building?

So! Those of you following this thread in the past few days may have seen the news (and read our discussion) regarding the new 1.8 SGX drivers and binary blobs that came out a few days back.

What this means for encore is (1) some new stuff had to be built into the kernel, (2) legacy egl was turned off in the build, and (3) new binary blobs, provided by TI, are now needed to replace the old ones (these are files that go in vendor/bn/encore/proprietary).

So if you're building from source, and you want to try, and you're willing to risk chaos and confusion and destruction, here would be the instructions:

1. repo sync as per usual to get your code up-to-date.
2. cd ~/android/system/device/bn/encore and change branches to ics-test:

git checkout ics-test


You should be told (in so many words) that a different set of files are now here. A git repository can have different "branches". Each one is like a separate version of the project. So I branched from the original project to this one so we could test the new egl stuff without disturbing anyone who's still building on the original "ics" branch.

3. find a blank directory somewhere on your hard drive (not in ~/android/system, that is) and:

git clone git://gitorious.org/rowboat/hardware-ti-sgx.git
git checkout ti_sgx_sdk-ddk_1.8


The binaries are in /gfx_rel_es5.x_android. You only need to copy these files into vendor/bn/encore/proprietary (replacing existing files of the same name). It won't hurt to copy everything though, as the extras will be ignored.

pvrsrvctl
pvrsrvinit
libeglinfo.so
libgles1test1.so
libgles2test1.so
libglslcompiler.so
libIMGegl.so
libpvr2d.so
libpvrANDROID_WSEGL.so
libPVRScopeServices.so
libsrv_init.so
libsrv_um.so
libtestwrap.so
libusc.so
libEGL_POWERVR_SGX530_125.so
libGLESv1_CM_POWERVR_SGX530_125.so
libGLESv2_POWERVR_SGX530_125.so
gralloc.omap3.so


then do a make clobber and then build as usual.

(you can get rid of the hardware-ti-sgx project you just cloned. You only wanted it for those binary files above.)

If something goes wrong, sorry, but you assumed all responsibility for trying this. You can probably go back to whatever you had been using though. There is a new kernel involved here too, and source for that is here, in case you want to try building it as well.

You may not notice a difference right off, but some things that didn't work before, such as the "Air Attack HD Part 1", game now seem to play. Probably others as well. And you MAY get some better battery life (but you tell me).

Another note: In device/bn/BoardConfig.mk there is a line that goes like this:

# USE_OPENGL_RENDERER := true

The # at the beginning means that this line is commented out. We tried uncommenting it, and it worked but wasn't stable with occasional freezes every 15 minutes or so. Our theory is it's memory-related, but if you feel daring, you can try it as well and maybe someone can track down what the deal is there (and fix it).

Thanks to keyodi for his kerneliciousness.

As for YOU, dear reader, aren't you glad you learned/are learning to build from source?

Also, if you haven't seen it, from the nook tablet world-- some interesting things.
 

webdroidmt

Senior Member
Dec 20, 2011
1,674
1,156
NJ
@fattire,

Been following the progress on the NT and it's pretty damn amazing. Even more amazing that you were able to do so much without even owning a NT. Pretty cool! Thanks again for all your contributions.

Mike T
 

zequav

Senior Member
Aug 14, 2011
268
105
Code:
I/SurfaceFlinger( 1172): SurfaceFlinger is starting
I/SurfaceFlinger( 1172): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/FramebufferNativeWindow( 1172): couldn't open framebuffer HAL (Not a typewriter)
E/FramebufferNativeWindow( 1172): couldn't open gralloc HAL (Not a typewriter)
E/SurfaceFlinger( 1172): Display subsystem failed to initialize. check logs. exiting...
:(

(edit) Started from scratch and don't have that error anymore.
 
Last edited:

MrColdbird

Senior Member
Nov 25, 2011
1,178
2,195
www.black-seraph.com
I've been using splashtop (which i know isn't the built in remote desktop) and it's been working great for me.
If you ever compared Splashtop to Remote Desktop... then you would know that the "it's working great" is a lie...

Splashtop is slow, irresponsive and overall a pc-side resource eater...
While RDP is builtin, fast and super snappy. :p

Really wish there was a version of it for Android 4.
 
  • Like
Reactions: aqtrans

zequav

Senior Member
Aug 14, 2011
268
105
Testing the latest build... Air Attack HD works... more or less. Graphics work, but the touchscreen is unusable for me while in the game. I have to press with two fingers for the game to register a tap.

Other apps work the same or worse than before. Speedx 3d or Cut the Rope are almost unplayable (too many random stutters).

Oh well. I'll wait for more reports (in case I did something wrong) before going back to the old driver.
 

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