[DEV] CM11 Work-In-Progress

Search This thread

Nburnes

Senior Member
Sep 4, 2010
1,330
977
Google Pixel 5a
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.

Yup, got it with this.

Code:
find ./ -exec grep -l "LOCAL_MODULE_TAGS := user" {} \; -exec sed -i.bak s/"LOCAL_MODULE_TAGS := user"/"LOCAL_MODULE_TAGS := optional"/g {} \;

Building now as I post this.

P.S @fattire: Thank you for that git video with Linus, made it so much easier to understand o_O
 
Last edited:

newellj79

Senior Member
Jan 2, 2011
2,378
298
OnePlus 8
Could u please post a link for you for your build. I build cm7 all the time but piecing this together is over my head. Thanks!

Sent from my Touchpad using XDA App
 

dalingrin

Inactive Recognized Developer
Nov 6, 2007
1,433
2,756
Knowing that the UI hardware acceleration will probably never work, how does the UI perform? is it at least relatively smooth? I know that cm7 doesn't have UI acceleration, so will it perform like that?

UI accel won't be perfect but we can most likely get at least partial support. A good bit of the work being done in CM9 is to get legacy devices fairly well supported.

The primary piece that we're missing is the hwcomposer library. As far as I can tell, it is not required for basic UI acceleration. I asked fattire to make a build for the Nook Color with the OPENGL_RENDERER enabled. This along with a modification to Webkit allows even the Nook Color to have some UI accel.

The bigger questions that I have are centered around video playback. DSP codec support shouldn't be a major issue but going from DSP->GPU->Output might be difficult. The way its done on OMAP3 is DSP->Overlay/GPU->Output. ICS has changed how the overlay works..its seemingly gone. I'm not sure how we can fix/workaround this yet. I need to dig into the Android framework to get a better understanding.

EDIT: I'm totally wrong about the DSP. The DSP codecs will be near impossible to get working right now unless TI updates OMX for OMAP3. They will need a new API to use native window rather than an overlay. I will test the new soft codecs in ICS and see what kind of performance we can get with those. It might be our only option going forward. The good thing with the soft codecs are that they should working with the overlay replacement already without any work from us.


At the end of the day, even full UI acceleration isn't going to be perfectly smooth on the Nook Color. The GPU and memory bandwidth just can't handle all of it smoothly. It will at least be an improvement versus no GPU acceleration.
 
Last edited:

pavlos46

Senior Member
Oct 30, 2010
230
19
ioannina
OK so I am gonna apologize before I even start.
And yes I am very apreciative to all the things that our devs have achieved so far but...

Have you been around the Defy forum lately they are on ICS nightlies already with full h/w ui and other nice goodies and thats an OMAP 3610 device with SGX530 on .32 kernel.

Why can't we......

Pavlos
 

motitas

Senior Member
Dec 26, 2010
88
16
dalingrin;19918684 [B said:
EDIT[/B]: I'm totally wrong about the DSP. The DSP codecs will be near impossible to get working right now unless TI updates OMX for OMAP3. They will need a new API to use native window rather than an overlay. I will test the new soft codecs in ICS and see what kind of performance we can get with those. It might be our only option going forward. The good thing with the soft codecs are that they should working with the overlay replacement already without any work from us.

I've always had goodluck with those sw codecs so I feel like we'll be fine without the video playback.... probably not the best battery life though. Either way it's good to hear we'll be getting at least some level of UI accel even if it won't be silky smooth. Thanks for your work, I appreciate it.
 

EnTg888

Member
Feb 8, 2011
38
5
It seems that driver is for Linux. As in, Ubuntu/Redhat/etc, and it was developed from the Android driver. There's a good chance we already have a working Android driver-but correct me if I'm wrong.
 

xdp

Senior Member
Nov 30, 2010
599
93
Keeping an eye on this. Even if UI GPU acceleration doesn't ever fully come onboard, I'm pretty happy with the responsiveness of CM7 currently, so if it's just like that I'll be completely satisfied.

I'm a little confused about how this works though. I thought the manufacturers had to release their kernel source which would include drivers and anything necessary to interact with the hardware. What are the closed-source components of this that are not included with the kernel? Will this be an issue on other older devices as well like the EVO?
 

Dj-Gutz

Senior Member
Sep 1, 2010
198
83
Tel Aviv
At the end of the day, even full UI acceleration isn't going to be perfectly smooth on the Nook Color. The GPU and memory bandwidth just can't handle all of it smoothly. It will at least be an improvement versus no GPU acceleration.

Can you explain why?
Adreno 200 seems to be doing fine ( pretty smooth )
SGX530 is better , and also the posted videos of the Optimus Black ( being worked by Ricardo Cerqueira ) shows perfectly smooth UI


Also , I guess it's a little early to ask but does USB-HOST currently works on ICS? or modifications needed for that too?

Thanks for all the hard work you guys put into this , you are incredible :D


I think the new driver will be able to give us true Multi-Touch ( more than 2 fingers ) , but I guess that should be concerned on a later date


OT :
CM9 UPDATE - http://www.cyanogenmod.com/blog/cm9-progress-update
 

luigi90210

Senior Member
Jul 29, 2010
590
110
Samsung Galaxy Z Flip3
Can you explain why?
Adreno 200 seems to be doing fine ( pretty smooth )
SGX530 is better , and also the posted videos of the Optimus Black ( being worked by Ricardo Cerqueira ) shows perfectly smooth UI


Also , I guess it's a little early to ask but does USB-HOST currently works on ICS? or modifications needed for that too?

Thanks for all the hard work you guys put into this , you are incredible :D



I think the new driver will be able to give us true Multi-Touch ( more than 2 fingers ) , but I guess that should be concerned on a later date


OT :
CM9 UPDATE - http://www.cyanogenmod.com/blog/cm9-progress-update
he explained why in his post, the nook doesnt have the memory to handle it, and even if it did at the moment the nook doesnt run the same kernel version as the optimus black

idk why people are obsessing about the optimus black though, it has nothing to do with the nook color even if it has similar hardware(i use similar because there are A LOT of differences between the 2 the main one being processor) and even if they were compatible the drivers for the optimus black wouldnt work on our nooks because the optimus black runs a newer kernel than the nook
 

pavlos46

Senior Member
Oct 30, 2010
230
19
ioannina
he explained why in his post, the nook doesnt have the memory to handle it, and even if it did at the moment the nook doesnt run the same kernel version as the optimus black

idk why people are obsessing about the optimus black though, it has nothing to do with the nook color even if it has similar hardware(i use similar because there are A LOT of differences between the 2 the main one being processor) and even if they were compatible the drivers for the optimus black wouldnt work on our nooks because the optimus black runs a newer kernel than the nook

OK what about the Defy, same amount of ram same kernel version.... any explanation there ?
 

sednafx

Senior Member
Aug 11, 2011
359
127
Jacksonville
It may be best to wait and see what the dev's are able to do than to speculate on similar devices and their performance. I have faith in Dal and the other devs.

Sent from my PC36100 using Tapatalk
 
  • Like
Reactions: luigi90210

angomy

Senior Member
May 4, 2011
294
102
OK so I am gonna apologize before I even start.
And yes I am very apreciative to all the things that our devs have achieved so far but...

Have you been around the Defy forum lately they are on ICS nightlies already with full h/w ui and other nice goodies and thats an OMAP 3610 device with SGX530 on .32 kernel.

Why can't we......

Pavlos

because each device has a different number of devs each of whom can only commit a certain amount of (I should mention unpaid, of their own good will) time?

Remember what Thumper's mum said..


Sent from my NookColor using xda premium
 

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