yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] steven676:
Some bigger changes coming

Bored with CM11 already? Think it's too stable for your tastes? Well, I've got just the thing for you: a bunch of potentially destabilizing changes:

Don't lie about the hardware we have on the device: we've been doing this for quite a while, in violation of the Android Compatibility Definition. Back in the pre-Honeycomb days, it was necessary to do this because the CDD required all devices to have things like a camera, microphone and GPS, and apps were written to blindly assume that they were present. Since 4.0, though, this hardware is no longer required from all Android-compatible devices, and apps are no longer supposed to assume their presence without declaring a need for them. That said, we need to test to make sure that (1) we haven't broken any apps and that (2) we aren't preventing too many useful apps from being installed. (Strictly speaking, any app that's useful without these hardware features should declare them as android:required="false" in AndroidManifest.xml, so if you find an app that you've installed on your device is now being reported as "Not compatible" by Market after this change, you should get in touch with its maintainers. If it turns out to be a widespread problem, though, I'm going to hold off on making this change.)

Convert to the TI branch of wpa_supplicant: if this were just to get MAC address display in the Android UI working, it'd be all wrong (that's a bug in the normal wpa_supplicant which affects other non-TI devices as well), but (1) I'm lazy and don't feel like hunting down the bug and (2) this opens the possibility of enabling WiFi Direct down the road. (thanks drmarble, Hashcode, and others)

BoardConfig.mk cleanups (1, 2): these should result in no functional change, but it's entirely possible I overlooked something -- please test.
[Nook Color Android Development] fattire:
yeah.

I think we should make the change and fall back if there's a major, major problem from being correct in what's reported. My sense is, we shouldn't "lie" about the systems' capabilities-- if an app requires gps, for example, we probably should just accurately report it's not there, and so maybe the app disappears from the app store as a result... which it should unless the app developers fix it. I don't know that we have cause for spoofing stuff like for Gingerbread back when Android wasn't really built for tablets.

Also, for anyone looking for the nightly build.... the build tonight is busted due to something upstream. The ban is still lifted, so whoever wants to fill in the gap, go for it. My advice to anyone who is not building for themselves though is to be absolutely sure you trust any builds that are posted. None of the devs can vouch for the safety of using an unofficial build.
[Nook Color Android Development] boringuy:
OS X build

I was trying to find that smarter solution for this but it turns out that error is not critical. What's stopping the build was "md5sum" is not there in OS X. The build stopped because it complains about cannot get md5sum to check if some config files are newer. That line prints out a couple lines below the error mentioned above and it's not obvious at all. So, just install md5sum using brew:

$ brew install md5sha1sum

and it should build. I have not tried install the rom yet but everything built and the wl12xx.ko and wl12xx_sdio.ko are there built from source.
[Nook Color Android Development] polymath257:
What do we need to do in the roomservice to get these changes? Or are they already part of stevens' source? I know I made the changes concerning wpa_supplicant in BoardConfig.mk for my own builds.
[Nook Color Android Development] fattire:
They're part of the source now on steve's repo but not the official CM...
[Nook Color Android Development] bigbob23:
OS X has "md5" which I think works the same as "md5sum" in Linux.
[Nook Color Android Development] EAK128:
Pretty sure we need an updated recovery 6.0.4.3+ to be able to flash cm11, was wondering if you could put a copy of it in the op.
[Nook Color Android Development] uranium:
the cm11 nightly is up guys! whohoooo. thanks to all the developers!

and so i installed cm11. one question though, is it possible to do the swap of Internal and External Media Storage? cm11 seems to have broke this feature. thanks!
[Nook Color Android Development] Homer_S_xda:
Super thanks to all the devs!

Here is a quick summary since I'm collecting files to take the plunge:

Recovery (CWM 6.0.4.3+):

http://xdaforums.com/showpost.php?p=49898894&postcount=18

GAPPS:

http://wiki.cyanogenmod.org/w/Google_Apps

Nightly:

http://download.cyanogenmod.org/?type=nightly&device=encore

Haven't tried any of this yet. Please let me know if you know which recovery link is best. I'm thinking alternate and leaving the stock one primary. Only issue there is if you run out of juice, it tends to recover to stock.

I saw in my search someone mentioned unattended backup and update. Would that kind soul document how it's done?

UPDATE: Used the Recovery that Fattire provided. Installed by dragging and dropping to Leapinlar's 6.0.1.2 SDcard. After remembering to use Cyanoboot to boot Recovery, did the following:

1) Format data/factory reset

2) Flashed 20140129 nightly

3) Flashed Micro GAPPS

Rebooted and all seems well. Working on reinstalling apps. Still have to install new recovery as alternate to handle nightlies.

Question: I think someone said the Internal and External card paths are swapped now. Is this correct and how do we make it behave like we want it to (swap them back)?

Wish me luck!

Homer
[Nook Color Android Development] uranium:
hi guys, just want to highlight that once you go to kitkat, it is difficult to downgrade. I tried downgrading and encountered quite abit of issues. the latest cwm recovery 6.0.4.5 seems incapable of downgrading to the cm10.2 nightlies and throws up an error message that was mentioned earlier by another individual.

the recovery used seems to determine certain things about booting android. im not a developer but this is an observation ive made.

i would love to be on kitkat. but i will require the swapping of the int and ext memory space though. so am looking to someone getting that feature up. thanks in advanced!
[Nook Color Android Development] volpo222:
Moving this to the nightly thread.
[Nook Color Android Development] steven676:
Yeah, if we're unconditionally using "md5sum" anywhere in the build process, that's really a bug. I'm not sure where that might be, though.

It's in the process of being forward-ported to CM11 at the moment (http://review.cyanogenmod.org/56515).
[Nook Color Android Development] meteorrock:
<Breakfast encore> is working for me from cyanogenmods git servers side. I just want to see if I can build my first nightly .zip. It defaults to CM 11.0 now for the encore. :good: I know........I am slow. I had to look through ALL of my downloaded directory goodies to check code. :p

No problem with repo syncing here now, keeps hitting 100 percent using ubuntu 12.10 in VMware workstation 9.0.3 build-1410761. No modded roomservice.xml into .repo/local_manifests needed like before.

PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
CM_VERSION=11-20140130-UNOFFICIAL-encore
TARGET_PRODUCT=cm_encore
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a8
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.10.1-031001-generic-x86_64-with-Ubuntu-12.10-quantal
HOST_BUILD_TYPE=release
BUILD_ID=KOT49H
OUT_DIR=/home/meteorrock/android/system/out
===========================================

Guys, what is the terminal code to move my proprietary files that was extracted with the ./extract-files.sh script and to move them to the vendor directory? Without them, CyanogenMod will build without error, but you’ll be missing important functionality, such as the ability to see anything!

Is it this correct? I am still learning the terminal commands.

meteorrock@ubuntu:$ cd ~/android/system/device/bn/encore mv > ~/android/system/vendor/

OR will this work? Dont want that directory mess in the wrong PATH for a followthrough.

mv ~/android/system/device/bn/encore ~/android/system/vendor/

Will that move that directory to the correct one instead of going fishing in the directory?
[Nook Color Android Development] bowguy:
OpenJDK 1.7 ?

Lately my warning message about using the wrong Java version (due to using openJDK 1.6) has changed to:

The correct version is: Java SE 1.6 or 1.7.

Is it ok to move to openJDK 1.7?

Or is your answer test it and let us know ;)
[Nook Color Android Development] bowguy:
Bored with CM11

I had to back this out to get it to build. Can you give instructions on how to:

It is necessary to obtain the repo:

CyanogenMod / android_external_wpa_supplicant_8_ti

and put it into:

external/wpa_supplicant_8_ti

Otherwise it doesn't know how to build some libwpa components.
[Nook Color Android Development] polymath257:
The extract-files.sh command *is* the terminal code to move the files from your device to the appropriate vendor directory.

If you look inside the extract-files.sh file, you will see the individual commands used. In particular, the file proprietary-files.txt

contains a list of the required files and the extract-files.sh script uses the adb command to move them from the nook to the

correct directory. Looking inside may be useful for understanding how bash command scripts work.
[Nook Color Android Development] steven676:
This, pretty much :) There's been work upstream on unbreaking Java 7, but I'd still count it as experimental at the moment.

This was added to the main CyanogenMod manifest two weeks ago -- have you repo sync'ed lately? I'd also check your local manifests to see if there's a <remove-project> or something that might be getting rid of it.
[Nook Color Android Development] bowguy:
I have sync'ed daily. The change above is in the android/default.xml file but it is not in my .repo/project.list file FWIW. I can't find any reference to a <remove-project>
[Nook Color Android Development] drmarble:
You don't need to get the repo anymore. It has been included into cm.

If you are building using steven676's repo. The wpa change has been included. If you are using the cm repo for device/bn/encore you need to cherry pick: http://review.cyanogenmod.org/#/c/58338/

To do this, go to device/bn/encore and enter:

git fetch http://review.cyanogenmod.org/CyanogenMod/android_device_bn_encore refs/changes/38/58338/1 && git cherry-pick FETCH_HEAD

then croot back to your building root directory and build away. This cherry pick will need to be reapplied everytime you repo sync.

A little lesson on cherry picking commits.

Look around on http://review.cyanogenmod.org/#/q/status:open,n,z There you will find lots of proposed changes to the cm code base. If you see one that you want to try, click on it. This will show you detailed information about the change. Including comments from other builders. If you want to try it, click on the 'cherry-pick' button below the bold Patch Set. This changes the line below from a download to a cherry-pick format. There is a little square icon to the right of that long text line below that button. Click on it to copy that line to your clipboard and just paste it into your command window. You don't have to type in that whole confusing line. You could also just highlight it and copy and paste but you want to make sure it says 'git cherry-pick' in the line you paste.

You can comment on the change if you register with the cm gerrit. This will give you a voice in what happens to the code and lets others know how the patch worked for you.That's where all the +1 and -1's come from in the comments section.

Enjoy home brewing.
[Nook Color Android Development] steven676:
Anyone still set up to build CM10.2?

While we're all having fun with CM11, I've made some changes to the cm-10.2 branch to use the older 3.0.8 kernel instead of 3.0.101, with a possible CM10.2.1 stable release build in mind. (Why 3.0.8? More on that in a future post.) While I don't anticipate introducing any bugs this way, if you're still set up to build CM10.2, I'd appreciate it if you could build and report any problems you have with it ASAP -- stable releases are supposed to be coming Soon [tm] and I'd like to squash any outstanding bugs (that are our fault) before then.
[Nook Color Android Development] polymath257:
I should also point out that you can also extract the proprietary files from a ROM zip file. Just as extract-files.sh will extract the proprietary

files from an attached NC (adb must be enabled!), the script in unzip-files.sh will find the proprietary files in a ROM.

So, if if you have a ROM named, say, cm-11-201428-unofficial-encore.zip, you can go to the device/bn/encore directory and give the following

command:

./unzip-files.sh /path/to/file/cm-11-20140128-unofficial-encore.zip

and that will copy all the required files to the correct vendor directory.

---------- Post added at 04:35 PM ---------- Previous post was at 04:27 PM ----------

While on the topic of unzip-files.sh, there appears to be a typo in the code.

I am thinking that in the if [ ! -f "$1" ] statement, the check should be on $ZIPFILE and not on $1.

This makes a difference when no zip file is given on the command line. The code suggests that a file encore_update.zip

would then be used from the top of the build directory, but with the check on $1, this won't happen.
[Nook Color Android Development] steven676:
Submit a patch and we'll take it :)
[Nook Color Android Development] polymath257:
I am not sure exactly how to go about doing that. I currently have an encore-local branch that includes this and another tweak. The other tweak

is a change to fstab.encore to allow an emmc install to see the 4th partition of the sdcard so that an sdcard install and the emmc install can share

the partition. This was easy to do in previous versions of CM, but now seems to require a kernel change.

Anyway, I only want to submit the change to unzip-files.sh and not the change to fstab.encore. What steps do I need to do to make that happen?
[Nook Color Android Development] mrg666:
Thank you for the information.

Also thanks to you and Dalingrin for working on the ICS port.
[Nook Color Android Development] dictege:
Thanks,

How compile from source ?
[Nook Color Android Development] luigi90210:
if your running linux or mac osx you can get it set up easily but if your running windows you have to ether setup a dualboot or use a VM to run linux and get a workstation set up
[Nook Color Android Development] motitas:
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?
[Nook Color Android Development] joenathane:
Which hat did you pull that out from?
[Nook Color Android Development] alunral:
"*Fully accelerated composition of the UI - this is not likely and may be dependent on 3rd party closed source EGL libs getting updated"

He got it from the topic post.

I wonder what the chances of at least getting Honeycomb onto the NC, if ICS is being so finicky?
[Nook Color Android Development] sednafx:
This may be helpful

http://wiki.cyanogenmod.com/wiki/Building_from_source
[Nook Color Android Development] IIDeViiNII:
Thanks so much!

This will be awesome once it hopefully gets stable!

Thanks for the work!

I and allot of everyone else is really appreciative!

Sent from my Samsung Captivate
[Nook Color Android Development] joenathane:
Wow, I definitely didn't catch that, it must have been updated since I last checked. Well that sucks...
[Nook Color Android Development] newellj79:
I build cm7 from source all the time. Setup using the guide posted above. My Linux experience is limited, but I'm learning quick. I'm going to try and just swap out the source link but I'm pretty sure there is more to it than that. Any info would be great. Thank.
[Nook Color Android Development] newellj79:
Did some quick research. Does anybody know where the manifest is located? I may be able to get it to work with that.... big may... really new to this but love trying.
[Nook Color Android Development] sark666:
I am also really disappointed to here that ui acceleration is probably not going to happen. That's the main reason why I want ics.
[Nook Color Android Development] boomn:
As long as it's as smooth as CM7 is then I'll be happy, because the real selling point for ICS for me is finally being able to run the "HD" or tablet versions of many apps that make much better use of the 7" screen than the phone-oriented apps that are compatible with CM7
[Nook Color Android Development] luigi90210:
^THIS

to be honest i dont like the blown up phone apps on my nook(IE netflix sometimes reverts back to phone ui) and i would love to have a full tablet UI for all my apps and to finally have better tabbed browsing(gingerbread tabs suck)
[Nook Color Android Development] motitas:
I'm sure that once we get a stable release, with time, patching, and some dirty hacks everything will turn out fine...

Also, I'd try and build the source since I am already running linux, but Im sure that my puny 1.2ghz cpu core2duo and 64gb ssd won't really finish in a reasonable time frame... hopefully someone can get it compiled and put up a video, then we can see what the UI will look like, or at least what it's like at the moment.
[Nook Color Android Development] luigi90210:
im tempted to compile and post a video but im to lazy to boot into my linux partition
[Nook Color Android Development] cchant:
I may have to set my linux partition up tomorrow. Depends if I get trapped in skyrim or not :-!
[Nook Color Android Development] Nburnes:
Well this is annoying. Have everything synced up, cloned fattire's git, lunch blah blah and finally onto make to have this.

============================================
PLATFORM_VERSION_CODENAME=AOSP
PLATFORM_VERSION=4.0.1.2.3.4.5.6.7.8.9
TARGET_PRODUCT=full_encore
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=OPENMASTER
============================================
find: `omapmmlib/java': No such file or directory
find: `omapmmlib/java': No such file or directory
build/core/base_rules.mk:78: *** Module name: tiwlan.ini
build/core/base_rules.mk:79: *** Makefile location: hardware/ti/wlan/wl1271/config
build/core/base_rules.mk:80: *
build/core/base_rules.mk:81: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:82: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:83: *
build/core/base_rules.mk:84: * optional, debug, eng, tests, samples
build/core/base_rules.mk:85: *
build/core/base_rules.mk:86: * If the module is expected to be in all builds
build/core/base_rules.mk:87: * of a product, then it should use the
build/core/base_rules.mk:88: * "optional" tag:
build/core/base_rules.mk:89: *
build/core/base_rules.mk:90: * Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:91: * Android.mk for the affected module, and add
build/core/base_rules.mk:92: * the LOCAL_MODULE value for that component
build/core/base_rules.mk:93: * into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:94: * makefile(s) where it's necessary, if
build/core/base_rules.mk:95: * appropriate.
build/core/base_rules.mk:96: *
build/core/base_rules.mk:97: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:98: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:99: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:100: * build/target/product/core.mk
build/core/base_rules.mk:101: *
build/core/base_rules.mk:102: *** user tag detected on new module - user tags are only supported on legacy modules. Stop.
[Nook Color Android Development] dictege:
Thanks,

I did it, but how integrate this new branch ?

B0B
[Nook Color Android Development] icewewe:
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.
[Nook Color Android Development] fattire:
Looked briefly at it.. looks like the fascinate uses a 1GHz Samsung S5PV210, which is pretty different from the texas instruments OMAP3 (3621)platform that nook runs off. Far better to look at other omap3 devices, such as the Droid X (omap 3630) the Defy (omap 3630) , the Click (3620) or the Droid 2 (3620). Of these, the defy is in active development...
[Nook Color Android Development] Bawb3:
Yeah I know the hardware is completely different, was just a suggestion for some of the more minor fixes :) I'm sure you will get everything(important) sorted out eventually.
[Nook Color Android Development] inportb:
Try Kubuntu or just install the kubuntu-desktop metapackage.

Also, why use Chrome when there's Chromium? It works just as well, is easy to install (apt-get install chromium-browser), and does not bundle some of the Google-specific cruft.
[Nook Color Android Development] rickpref:
I agree with Chromium...functions the same and is already in the repos. Also, why not try Mint 12. Works great. I don't like the Unity interface, but love Gnome 3. You can install that pretty easily in Ubuntu as well if you don't want Unity. Takes 2 seconds:

sudo apt-get install gnome-shell

Then restart and select the Gnome 3 login.
[Nook Color Android Development] bigbob23:
Supposedly there is a way to boot into the old GUI but I haven't figured it out. I had been using Ubuntu since it came out, but I will go back to Debian, which I had used since ~1996.
[Nook Color Android Development] wire103:
Enough with the Ubuntu complaining already. :-)

http://www.faqforge.com/linux/install-gnome-desktop-on-ubuntu-11-10/

Thanks to op for the effort on ICS!
[Nook Color Android Development] Tyfighter:
I have only read like 26/39 pages, so i dont know that this hasnt come up yet, but PreHome in the market provides a handy app switching bandaid for te time being.
[Nook Color Android Development] dravenSt0rM:
Please mate, state in your first post is your ROM:

Dev Only

Pre-Alpha

Alpha

Beta

Full

And please state number of the version

Thanks for cooperation with XDA Developers.
[Nook Color Android Development] whiteguypl:
lolwhat?? O.o
[Nook Color Android Development] swm5126:
Please stop doing this. You did this in the Inc forum too. Its pretty clear what this thread is.
[Nook Color Android Development] joenathane:
I guess it has something to do with this

http://www.xda-developers.com/android/how-to-keep-track-of-all-xda-ics-ports/
[Nook Color Android Development] inportb:
It's actually pretty simple to disable Unity... just select "Ubuntu Classic" while logging in.
[Nook Color Android Development] dreamhunterr:
Did anyone mention on this thread that the official 1.4 update has been released for the Nook Color?

And, with that, the mandatory OSS components, listed here, downloadable here.

Maybe it comes with a new kernel, I'm still downloading, will report later :)

---edit

Oh, ****, still Froyo and that old kernel :\
[Nook Color Android Development] unsivil_audio:
^-----It does NOT come with a new kernel, also its only froyo still 2.2.1 and has little to no relevance to this thread.

They botched the "Ubuntu Classic" in 11.10. 11.04 it was the same, but now its horrible. Thinking about ditching ubuntu entirely in favor of another flavor of distros.
[Nook Color Android Development] boomn:
Nope, still a Froyo 2.6.32 kernel. Bummer
[Nook Color Android Development] rigy73:
the kernel is same, no changes.

And mp4 files are working for me, without sound, I thought videos weren't working at all..
[Nook Color Android Development] Nburnes:
Not like s/he can't read the second post where it says really not usable for anyone and everyone is advised not to install...
[Nook Color Android Development] fattire:
well some video works-- youtube on low quality, etc.

I know unforgiven512 was working last night for hours on sound. Dunno if he had a breakthrough or not.
[Nook Color Android Development] inportb:
Ah, well. When I get tired of Kubuntu, I might give FreeBSD a look :cool: