yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] leapinlar:
You should not be talking about this in this thread. This is for development/building only. Try looking the CM9/CM10 discussion thread.
[Nook Color Android Development] dli7319:
go here and find out what prerequisite your are missing
[Nook Color Android Development] bytte:
Why do you think it is a pre-requisite issue? (I don't see what PA has to do with this thread).

The failing ln -s command pertains to the wifi module in my build machine - why should it want to create a link to it in the encore build tree?
[Nook Color Android Development] dli7319:
it doesn't have anything to do with PA but i used to have the same problem, then i went to that site and found out I was missing some stuff (I followed the steps up to android sdk installation) that wasn't in the cm10 build guide and now I can build fine, sry if this doesn't help at all but it's worth a shot
[Nook Color Android Development] steven676:
Should be fixed in device/bn/encore from NookieDevs (https://github.com/NookieDevs/andro...mmit/fdb78c711ab9f943c351e983e9531a4814b6b4be). (Yes, there's no /data on the build system, but creation of dangling symlinks is explicitly permitted by POSIX, and the end result is a working symlink on the installed ROM.)
[Nook Color Android Development] fattire:
Looks like wl1271-nvs.bin didn't get copied to out for some reason resulting in the "android/system/out/target/product/encore/system/etc/firmware/ti-connectivity/wl1271-nvs.bin': No such file or directory" error...
[Nook Color Android Development] unknown_world:
Can some one add the following to our system.prop in this repo https://github.com/NookieDevs/android_device_bn_encore

ro.config.nocheckin=yes

jpeg.libskiahw.decoder.enable=1

jpeg.libskiahw.decoder.thresh=100000

debug.performance.tuning=1

ro.kernel.android.checkjni=0

ro.kernel.checkjni=1

ro.media.enc.jpeg.quality=100

persist.sys.purgeable_assets=1
[Nook Color Android Development] laigor:
kernel crash on my device

This change

https://github.com/NookieDevs/ti-omap-encore-kernel3/commit/26e7765e37a335d0076950618e335a430debbdcb

cause kernel crash on my device.
[Nook Color Android Development] unknown_world:
@krylon360

@steven676

https://gist.github.com/3928995

I think following lines from the above patch by krylon360 are need for picking the correct codecs.

media_codecs.xml does not have method of defining video size and we have 2 codecs which can

handle same file type so we need the following patch. I tested the following code and it work perfectly.

Can any of you check and submit to CM
[Nook Color Android Development] krylon360:
i -1'd it for now. not sure I like how it's setting if anything is greater than 860x480 it'll fail the decoder
[Nook Color Android Development] keyodi:
Can you post your dmesg log? how do you know it's that commit causing the kernel crash?
[Nook Color Android Development] steven676:
What are these settings supposed to do, exactly? (CheckJNI is already off by default, so there's at least one thing in there we don't need.)
[Nook Color Android Development] fattire:
Beta 1... outsies!

Beta 1 is out for those who haven't noticed. We'll see ya over at that thread for testing :)

Thanks to the testers and, especially to krylon360, sluo, keyodi, and unknown for their impossible-to-appreciate-enough hard work and amazing contributions... well done.
[Nook Color Android Development] laigor:
Please show local_manifest for beta 1 build

---------- Post added at 10:50 AM ---------- Previous post was at 10:31 AM ----------

Log obtained through UART cable.

http://pastebin.com/RQP2i1QA
[Nook Color Android Development] unknown_world:
I agree with you but we need some way of handle this 2 codecs and only diffrence between this codes is the max res they can handle

and for now your patch is all we got.
[Nook Color Android Development] unknown_world:
Can you please tell how you got UART
[Nook Color Android Development] mateorod:
I have also found it hard to follow. But according to eyeballer, and unless they changed something from yesterday, this should be the manifest going forward: http://pastebin.com/vZFKdc8m

Uart, huh?
[Nook Color Android Development] krylon360:
same thing sluo said, and, we aren't compiling libskiahw source, so no need for those. We dont have a camera, so no need for the media.enc.jpeg.quality one either.

Where did these come from anyway?

Last I checked, there is only 1 person who has ever gotten UART working and that was on cm7.0.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com/" name="gh" />

<project name="NookieDevs/android_device_bn_encore" path="device/bn/encore" remote="gh" revision="jellybean" />
<project name="NookieDevs/ti-omap-encore-kernel3" path="kernel/bn/encore" remote="gh" revision="encore-omap3-3" />
<project name="eyeballer/proprietary_vendor_bn" path="vendor/bn" remote="gh" revision="jellybean" />
</manifest>
[Nook Color Android Development] laigor:
I compiled the kernel without these changes, and it normally runs.
[Nook Color Android Development] krylon360:
wow. so we are supposed to troubleshoot a kernel for a freakin hardware mod? really?
[Nook Color Android Development] steven676:
About backlight-off failures to resume and "wake of death" boot failures ...

If you're experiencing some of the SOD/failure to boot problems reported in the Beta 1 build thread, could you please try building with this kernel (https://github.com/steven676/ti-omap-encore-kernel3/commits/encore-omap3-3-lastknowngood) and reporting if that fixes your problem?

If that works and you're ambitious, could you try building the current NookieDevs source, but with some or all of the following commits backed out:

https://github.com/NookieDevs/ti-omap-encore-kernel3/commit/c22560eab59fe7cedb663aa84b5fccd391ee30f3

https://github.com/NookieDevs/ti-omap-encore-kernel3/commit/f95eb21f91d9d72cfc0ed040d7360d4d4ff913c0

https://github.com/NookieDevs/ti-omap-encore-kernel3/commit/26e7765e37a335d0076950618e335a430debbdcb

and see if your problem is fixed?

(I'd do this myself, but I don't have the time to build and wait for a random crash to happen at the moment. Also, this is the kind of job that parallelizes well ...)
[Nook Color Android Development] samcoinc:
The original alpha1 install caused SOD pretty much every time it went to sleep. (rebooting was required) anything that I have tried newer (like beta1 and unkown_worlds build seemed to have fixed. I had boot looping with the unkown_worlds build - but I think that was my fault.. (not formating system, data and cache before installing the zip.) So far so good. (running beta1 atm.)

sam
[Nook Color Android Development] bowguy:
I am testing with https://github.com/NookieDevs/ti-omap-encore-kernel3/commit/26e7765e37a335d0076950618e335a430debbdcb

backed out. (the third one)

UPDATE: Survived a 2 hour sleep with no SOD yet.
[Nook Color Android Development] fattire:
5-touch multitouch on NC? Any takers?

Moving to new business:

This thread for nook tablet talks about upping the multi-touch for the newer ft5x04 touchscreens (note, not the older cypress ones that I and so many others have) so that instead of accepting a max of 2 simultaneous touches, it can do 5.

This touchscreen on the NTs is the same as on newer Nook Colors. Older devices (like mine) use the cypress cyttsp driver, so it won't work.

I can't remember-- did anyone ever look into this for nookcolor? Obviously I can't test it as I don't have the hardware, but the patches they used to the kernel driver are in this branch, and a script that updates the firmware is here.

Big thanks to tonyp23 for providing the above info, although he points out he didn't write the flasher so can't vouch for it. Apparently they were having problems getting the firmware loader to work properly on the NT's JB kernel (although ICS worked), but I don't know if/how this would affect encore and the kernel we're using now.

Any takers on patching the driver and trying to update the firmware, etc? Anyone feel like being a hero?

Apparently updating the firmware also fixed some games that had "waiting for touch response" problems, including Major Mayhem, Minecraft, and Temple Run. I haven't heard about these problems affecting NC, but there you.

I don't have the touchscreen in question, so can't be much help here, but for those devs (or dev wannabes) who do have the newer touchscreen, it might be a fun little project.

Try at your own risk & read the script and make sure you understand it before you run it.

I'm told that once you flash a new firmware, you can't downgrade

.
[Nook Color Android Development] tonyp23:
I don't have a NC so I can't test this, but line 24 in the update script is the actual flash command. When I flashed this to the NT I did it manually with the command. Note that your i2c touch device might be at a different location so you may have to search for it. Good luck!
[Nook Color Android Development] bowguy:
Update. I made all the code changes and built it. Result is no touchscreen response. I will wait and maybe test later. The NT folks are still tweeking the code. I don't want to flash the FW since this may require me building everytime

Update2: Do not do this. There is no need to update your firmware. Keyodi built a test driver based on the Nook HD that gives me at least 4 touches but it has a major bug. I will try to work on the code next week.
[Nook Color Android Development] no_cannabis:
Hi guys, just a quick question. Should I use 64bit or 32bit versions of Ubuntu for a build environment. I created a x86 virtual machine, but can't run the build process, as I'm getting lots of "cannot execute the binary" errors on files that do exist and have proper permissions.
[Nook Color Android Development] newellj79:
64bit
[Nook Color Android Development] bytte:
Have done 'build/envsetup.sh', when I type m (make) in an application branch, eg 'android/system/frameworks/base/cmds/bootanimation', it builds the kernel as well as 'bootanimation'.

Is there a way to just build the application?

Thanks
[Nook Color Android Development] eyeballer:
I believe you need to do 'mm' to build from the current directory.

Edit: for reference: https://github.com/CyanogenMod/android_build/blob/jellybean/envsetup.sh
[Nook Color Android Development] unibroker:
/bin/bash: jar: command not found

I get this error while trying to build on Ubuntu 12.10. The search results I've seen say it's a problem with my java install.

java -version

returns

java version "1.6.0_37"
Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode)

.

Thanks in advance.
[Nook Color Android Development] eyeballer:
For those building at home, we just renamed the kernel repo on nookiedevs. The branch stayed the same so just update your manifest accordingly:

https://github.com/NookieDevs/android_kernel_bn_encore
[Nook Color Android Development] steven676:
Make sure you have the Java Development Kit (JDK) installed, not just the Java Runtime Environment (JRE). jar ships with the JDK, but not with the JRE (it's not needed for running Java software, just for packaging it).
[Nook Color Android Development] unibroker:
open jdk instead

Thanks for the response. I did make sure it jdk but in the meantime someone who has more expertise in this field said he has built successfully with Open JDK. I installed it (no jar error message)and the build ran but broke because of something with the proprietary files copied from my NC. I have 18 instances where where a specific doesn't exist. One of those output lines from the adb transfer

remote object '/system/vendor/lib/egl/libEGL_POWERVR_SGX530_125.so' does not exist

caused the build to break. Does the problem lie with my NC?
[Nook Color Android Development] fattire:
You are missing files, particularly vendor/lib/egl/libEGL_POWERVR_SGX530_125.so

What local_manifest.xml are you using?
[Nook Color Android Development] eyeballer:
You need to pull the vendor files from one of our beta builds.
[Nook Color Android Development] unibroker:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="git://github.com/" name="gh" />

<project name="NookieDevs/android_device_bn_encore" path="device/bn/encore" remote="gh" revision="jellybean" />
<project name="NookieDevs/https://github.com/NookieDevs/android_kernel_bn_encore" path="kernel/bn/encore" remote="gh" revision="encore-omap3-3" />
<project name="eyeballer/proprietary_vendor_bn" path="vendor/bn" remote="gh" revision="jellybean" />
</manifest>

---------- Post added at 10:22 AM ---------- Previous post was at 10:14 AM ----------

So I just flash the latest ROM and run

./extract-files.sh

again?
[Nook Color Android Development] eyeballer:
Check your kernel line in the manifest..

"NookieDevs/android_kernel_bn_encore"

You can either pull props from my git OR pull from the device, don't do both steps.

Do these steps:

1) rm -rf vendor/bn/encore

2) fix the kernel line in the manifest

3) repo sync

Then try to build and you should be set. Don't run extract-files or setup-makefiles.
[Nook Color Android Development] unibroker:
Thanks for the help and please bear with me. I am looking at manifest.xml under .repo and that document only contains the following relating to kernel

<project path="external/kernel-headers" name="CyanogenMod/android_external_kernel-headers"/>

. The only mention of specifically NookieDevs is from the local_manifest.xml. Am I in the right document?
[Nook Color Android Development] eyeballer:
I was referring to the local manifest you posted:

This line is wrong:

<project name="[B]NookieDevs/https://github.com/[/B]NookieDevs/android_kernel_bn_encore" path="kernel/bn/encore" remote="gh" revision="encore-omap3-3" />
<project name="eyeballer/proprietary_vendor_bn" path="vendor/bn" remote="gh" revision="jellybean" />

Need to remove the stuff in bold.
[Nook Color Android Development] krylon360:
if you are building from home, you really dont need a local_manifest anymore.

flash beta5

plug device into pc

(make sure adb works)

delete local_manifest.xml

repo sync

. build/envsetup.sh

lunch

19

cd device/bn/encore

./extract-files.sh

cd ..

cd ..

cd ..

(should be in your root android dir now)

repeat step 1-3

time mka bacon

(you only have to do most of these steps once.

once you have your vendor,

all you would need to do is

repo sync

. build/envsetup.sh

lunch

19

time mka bacon
[Nook Color Android Development] unibroker:
edit: my error. Got to find out what happened to "device/bn/encore" because my bn/encore is now missing.

---------- Post added at 03:20 PM ---------- Previous post was at 02:37 PM ----------

"device" is still there but "bn/encore" is missing. I can't figure out from setup of the build environment when/where it was created. I have done ". build/envsetup.sh", as recently as this morning so I know it was there. Any suggestions as to how I might proceed?

BTW, the beta 5 is very smooth and responsive. Impressive!
[Nook Color Android Development] krylon360:
repeat step 1-3 ;)

it'll auto sync device/bn/encore and kernel/bn/encore from CM.

*Note, the number 19, which is 19. cm_encore-userdebug will change as more devices get added to CM. so you will need to look for it.
[Nook Color Android Development] unibroker:
My only output is

build/core/base_rules.mk:171: *** android/system/abi/cpp: MODULE.TARGET.SHARED_LIBRARIES.libgabi++ already defined by abi/cpp. Stop.

and that was after recognizing "19" has changed to "5". I got no errors up to this point.

Update: I found a duplicate source tree and deleted it.

When I tried to do your whole process over, resyning first I get

error: Cannot remove project "vendor/bn": uncommitted changes are present commit changes, then run sync again

and after the first "lunch" I get

You're building on Linux

Breakfast menu... pick a combo

and there is no "encore" option. Any advice. By the time I build this you'll have moved onto Android 6.1:eek:

Update: ./vendor/cm/get-prebuilts was my solution.
[Nook Color Android Development] Divine_Madcat:
Thread cleaned again.

This is a PURELY dev thread; no commentary, and certainly no asking about other devices. I hate being a hardass guys, but really.. we need to respect our devs wishes. There are other boards for other commentary..
[Nook Color Android Development] drmarble:
CM10.1 builds

I succeeded at building cm10.1 for the Nook Color. It even boots up. The screen is rotated 90 degrees to the touch screen. Makes it unuseable but it is a proof of concept. I had to modify Boardconfig.mk to include TARGET_ARCH := arm, move a surfaceflinger include file over from 10.0 and the entire releasetool directory from cm10. Thanks to all the good work of the real cm developers, it build, flashed and ran. I expect the surfaceflinger problems are the reason the screen is rotated.

I just wanted to tell you folks so you could have hope of even more than jellybean on our Nook Colors sometime in the future. I'm going back to working on cm10 to make it better. I haven't heard of any compelling reason for upgrading to 4.2.
[Nook Color Android Development] fattire:
Congrats. . You can rotate the screen in a number of ways-- i think people were playing iwth teh ro.rotate.somethingorother in build.prop. A perhaps better way is to change the orientation in the accelerometer (so that it rotates the right way)... whether you need to rotate the video or the accelerometer may be dictated by whether the touchscreen is also rotated... you want all three of them to work together obviously...

in any event, we've had to do this before in the transition from ics->jb, so you can look through the kernel history and find where they've been rotated and rotate them back... I think maybe I saw that eyeballer was already playing with this?
[Nook Color Android Development] eyeballer:
Sort of.. I was working from AOSP source last week and hit quite a few more issues - but kind of got there eventually (https://twitter.com/eye_baller/status/270232522993053696). Fortunately the CM core team has been hard at work over the past week and using CM source base should be more complete - build and releasetools are all updated for 4.2 in the mr1-staging branch. Still plenty to do for CM has a whole, and of course for us on the device.
[Nook Color Android Development] unibroker:
11/26/2012 build

I finished a build on a completely new environment (fresh install of Ubuntu 12.04 64 bit, fresh download of android source and cm encore). I had one hiccup during the build as I had to install libxml2-utils and start the process over. After 4 hrs I ended with a zip. I did a wipe of cache, dalvik cache and factory and flashed the zip all from TWRP. After rebooting I get a back-lit, dark screen. I performed this process 4 times with the same result. What I've researched is it may be a bad image. Other than doing another build are there any suggestions to salvaging this one?

Thanks in advance.
[Nook Color Android Development] krylon360:
Sounds like your props didnt get copied over. did you run the extract-files.sh script?
[Nook Color Android Development] unibroker:
I did not. I thought that was not necessary after the November 14 event where encore became official.
[Nook Color Android Development] drmarble:
You still need the proprietary files. They are not stored on the cm servers for legal reasons. Some of them can be copyrighted and not freely redistributable. You have to get them off of your current device. This legal wrangling is not strictly enforced since you can get full roms from the cm servers. Still, for legal reasons, you have to run ./extract-files.sh from device/bn/encore to get these copyrighted files. You only have to run it once unless eyeballer updates the props again. This build should me much faster since you've populated ccache. If you don't make clobber it will be even quicker.
[Nook Color Android Development] unibroker:
Of course I made clobber!
[Nook Color Android Development] mateorod:
I had to do many of these same things for 4.2, and also have the screen rotation issue. Thanks to fat-tire for the tips on screen rotation. I modified the releasetools in several ways, including adding an optional recovery (which I set to false by default)

I also reararranged the proprietary files a bunch (my experience was that setup-makefiles breaks the compile because of the movement of vendor files to /vendor) although I haven't checked that surfaceflinger file. My touch screen was basically unusable, so that is a good tip.

Might could be that some of this is unhelpful/unnecessary, but it did finally compile.:p

Edit: I had a roatating screen in one build, but it was rotating the wrong way (portrait for landscape and vice-versa) so fat-tire sounds like he is right on the mark.
[Nook Color Android Development] drmarble:
The include file is no longer needed. They fixed hardware/ti/omap3/libstagefrighthw/TIOMXPlugin.cpp so it nolonger includes a missing include file <media/stagefright/MediaDebug.h>. The contents of this file are now in the file itself.

I still have rotation problems. On my early builds, the screen was rotated at 90 degrees but it displayed the entire screen. Now, with no changes on my part, the screen faces correctly but is 1024 wide by 600 high in portrait and 600 wide and 1024 high in landscape. The touchscreen seems to be oriented according to the accelerometer. With the home button at the bottom the dock bar is on the side (but invisible) like it was in landscape. If I touch the side of the screen, I get the dock bar functions. The boot animation is alsorotated and warped.

I still can't find out where to rotate the screen. Maybe DisplayDeviceInfo.java, switch width and height. Or, InputReader.cpp, again switch width and height. Neither one sounds good. There should be something I can change in device or kernel. I'll keep you posted. The easiest fix will be having the solution appear on Gerrit. I keep looking at all mr1-staging commits, just hoping for an applicable fix.
[Nook Color Android Development] unibroker:
using eyeballer's proprietary files zip

Currently I'm not running cm10 on my NC so I thought this would be a more effective way of adding the proprietary files from eyeballer's git. I have extracted the zip and moved it into my android/system area. Yesterday I mistakenly copied my proprietary files from my NC before I realized I was running cm7 so they would not work. Because of that I have 34 files under

android/system/device/bn/encore

Is it advisable to delete these 34 under /encore and then move the proprietary files from eyeballer's git here?
[Nook Color Android Development] drmarble:
That sounds like a good suggestion. You don't need any extraneous proprietary files. I think the proprietary files are different for 7.2 and 10.0. You can also use unzip-files.sh in devices/bn/encore. I think this tool is up to date. Just using eyeballers github is probably the best.
[Nook Color Android Development] mateorod:
I am only using Cyanogen device, kernel, proprietary and hardware/ti repos, with multiple patches spread over them and android_build ...however, what I think you are describing is the same problem I am having, where the screen is opposite the touch inputs.

As in, if I hold the device in landscape, the screen will display portrait. But the touch entries will actually correspond as if the screen was in landscape. So even though the navbar is on the left-hand side of the screen, if I press the area where the home button would be in portrait (at the bottom by the 'n' key) I get the home key action. If I rotate the screen I get a corresponding issue. Is this your experience as well?

I have been looking at input reader as well, and just merged in the recent commit enabling hw rotation...we will have to see if that affects the issue. I looked through the kernel commits for awhile last night, but wasn't able to isolate where they worked on any similar issues. But I merely skimmed it, I will probably have to go look more deeply.

I managed to enable developer options and turn on ADB, which was a chore, let me tell you. Lots of skipped frames, and as time progresses the device lags more and more as a result. SOD is 100%. I do have OMX and hardware acceleration up and going (ostensibly), which is likely due to the fix with the <include> file. That certainly did not take any specialized knowledge on my part.