Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,738,920 Members 43,675 Now Online
XDA Developers Android and Mobile Development Forum

[DEV] CM11 Work-In-Progress

Tip us?
 
dalingrin
Old
(Last edited by dalingrin; 19th November 2013 at 03:47 PM.)
#1  
Recognized Developer - OP
Thanks Meter 2738
Posts: 1,400
Join Date: Nov 2007
Default [DEV] CM11 Work-In-Progress

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


The Following 212 Users Say Thank You to dalingrin For This Useful Post: [ Click to Expand ]
 
fattire
Old
(Last edited by fattire; 25th November 2013 at 02:06 AM.) Reason: Will update from time to time.
#2  
fattire's Avatar
Recognized Developer
Thanks Meter 4386
Posts: 1,519
Join Date: Oct 2010
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 dick. Thanks.
--------------------screenshots---------------------



About screen, wifi scanning, & bluetooth....




The Following 163 Users Say Thank You to fattire For This Useful Post: [ Click to Expand ]
 
therkr
Old
#3  
Senior Member
Thanks Meter 16
Posts: 256
Join Date: Mar 2011
I'm no dev so can't help.
But thanks a ton. You'll give a new life to the NC!
The Following User Says Thank You to therkr For This Useful Post: [ Click to Expand ]
 
luigi90210
Old
#4  
Senior Member
Thanks Meter 39
Posts: 347
Join Date: Jul 2010
this device looks sexy, how is performance(compared to the first honeycomb port) and any ideas on how we can get off the legacy hack?
 
fattire
Old
(Last edited by fattire; 1st December 2011 at 11:10 AM.)
#5  
fattire's Avatar
Recognized Developer
Thanks Meter 4386
Posts: 1,519
Join Date: Oct 2010
Quote:
Originally Posted by luigi90210 View Post
this device looks sexy, how is performance(compared to the first honeycomb port) and any ideas on how we can get off the legacy hack?
Performance is hard to tell without any apps on it really and with the legacy hack being goofy. Dalingrin's going to fix the ts driver tomorrow he says. It needs to be updated for anything close to usability. I think though it's not too far off from cm7 but again *REALLY* hard to say without having something to run on it.

I did notice that if you put a background on the screen it only stays for like second before disappearing. No idea what that's all about.

Update:

So update on progress tonight

* misc fixes
* got wifi working for keyodi
* got glx working for keyodi
* fixed bluetooth pairing again. Ran into trouble trying to send a file connection refused (111) or something like that.
* got freecpu working, needed to chmod 4755 /system/xbin/su and also add Superuser.apk-- but now overclocked to Dalingrin's cm7 settings. It feels pretty good.


(that's actually set to highest stepping but it's not currently maxed out)

* quadrant runs-- looks fast to me-- but bombed out on the network part at the end:

E/c*.a*.q*.c*.c*.Abstrac*( 4126): Failed to retrieve benchmark score
E/c*.a*.q*.c*.c*.Abstrac*( 4126): java.net.SocketException: socket failed: EAFNOSUPPORT (Address family not supported by protocol)

So I don't have a score. Not that Quadrant is particularly valuable. but the staircase works, the planets spin, etc.



Prolly won't work on it most of tomorrow.. just sayin'. Dalingrin will tho hopefully and keyodi too.

BTW, dalingrin-- temporary fix for wifi: assuming you use WPA-PSK, push this into /data/misc/wifi/wpa_supplicant.conf as the default in the device needs to be fixed manana:

Code:
Select Code
ctrl_interface=tiwlan0
update_config=1

network={
        ssid="your_ssid"
        psk="your_password_in_plaintext"
        key_mgmt=WPA-PSK
        priority=1
}
Finally, if recovery.c tanks out, it's the last commit I made tonight. Sorry. I didn't think it was going to build it. Just back out changes to that file.
The Following 21 Users Say Thank You to fattire For This Useful Post: [ Click to Expand ]
 
ianPhillips1
Old
#6  
ianPhillips1's Avatar
Senior Member
Thanks Meter 78
Posts: 398
Join Date: Sep 2007
Location: Hampstead NC
Yay!
Ian

sent from my ereader
@Nestaroot
HTC M8 - AICP
VZW
Nexus7 '13 - 32gb - CLeanrom

Passed on to others:
Galaxy s4
HTC DNA
Nook Color
Dinc
Dinc2
Rezound
The Following User Says Thank You to ianPhillips1 For This Useful Post: [ Click to Expand ]
 
zequav
Old
#7  
zequav's Avatar
Senior Member
Thanks Meter 80
Posts: 225
Join Date: Aug 2011
Location: Coruņa
Fantastic work. Didn't thought quadrant would run fast this soon. If wifi, touchscreen and 3d work, we have the most important things working (save for ui acceleration). I don't even care much about sound.

Looking forward to the first kangs =)~
The Following User Says Thank You to zequav For This Useful Post: [ Click to Expand ]
 
gamer.pro.2000
Old
#8  
Junior Member
Thanks Meter 0
Posts: 28
Join Date: May 2010
Sweet! Lookin' pretty good. I hope the binaries for the UI acceleration get updated. Has the nook tablet source and files dropped yet? I seem to remember the NC and nook tablet having similar video hardware. Could be wrong. Are those binaries in that tablet as well?
 
jac0708
Old
#9  
Junior Member
Thanks Meter 1
Posts: 17
Join Date: Aug 2011
Quote:
Originally Posted by dalingrin View Post
Things to expect
Nothing
Noted, but that said I love this kind of technical tinkering and knowing this is being done is awesome. Looks pretty slick, I look forward to seeing how this develops.
 
Whoareyou
Old
#10  
Whoareyou's Avatar
Senior Member
Thanks Meter 291
Posts: 1,613
Join Date: Jul 2010
Location: Olathe, KS
no test zip? I would like to test, Im not one of those people that wont reprt back, i will tell what i find wrong
Device: HTC One (M7, Silver)
ROM: ViperROM


If you don't like me or my projects, READ THIS!



^^^^^^^^^^^^CLICK THE DOCTOR FOR EPICNESS^^^^^^^^^^^^^
"Trust Me, I'm the Doctor" -The Doctor

Tags
cm10, cm9, jellybean, nook color ics, winning
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes