yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] drmarble:
cm-12 lack of progress

I got a little farther than fattire in compiling cm-12.0 for encore. I took system/extras/mkimage from cm-11 and that fixed the first error.

I commented out the lines for bluetooth from encore.mk. I got a bit farther.

I switched away from wpa_supplicant_8_TI to the regular, non TI version. More progress.

I included building libwpa_client by adding it to the product packages in encore.mk. Another error eliminated.

I get lots or ion errors. We are sorely lacking in this department. Lots of errors complaining about not defining ion_user_handle_t. I added a definition to ion.h and that wasn't enough. There are further ion errors. I don't think that omap gets along well with ion.

I'll keep on it. I managed to unbrick my nook color so I am back in business.

By the way. 30 years since my previous dentist visit. No cavities. Unfortunately, three cracked molars are causing my toothache.
[Nook Color Android Development] hwong96:
[MENTION=4190710]drmarble[/MENTION] is CONFIG_CMA=y in kernel configuration? CONFIG_ION=y?

https://lkml.org/lkml/2014/4/17/507

Can't get past 99% repo sync of cm-12.0. Tried the command multiples times. Kept getting error

Fetching projects: 99% (497/502) error: Cannot fetch CyanogenMod/android_device_bn_encore

error: Exited sync due to fetch errors

hubert@hubert-Presario-V2000-EH463UA-ABA:~/android/system$
[Nook Color Android Development] drmarble:
I had no trouble syncinc device/bn/encore. You could just change the version to cm-11.0 since there are no changes. You could also try removing the entire device/bn/encore directory and try resyncing. Sometimes there is a problem in the .git directory.

I have temporarily surrendered. I modified some kernel headers to get a bit farther but we have a serious problem with hardware/ti/omap3. Google hasn't updated theirs since ics (a couple of minor LOG changes). Ours is still on kitkat. I've decided to beat my head against the wall of ovation (HD+) there may be a little more support for its omap4 processor.

Hopefully, various people will figure out just what needs to be done to hardware/ti/omap3 and we will be able to build. There are several good programmers who work on such devices besides our beloved steven676 a.k.a. sluo. Maybe one of them will make some progress. I still put my money on steven676.
[Nook Color Android Development] hwong96:
Recognized Developer Quarx managed to port Lollipop using 3.0.101 kernel to Motorola Defy. The Defy has a TI Omap 3620, A8 Cortex CPU, PVR SGX530, 512mb ram. Here is his thread if anyone is interested. http://xdaforums.com/showpost.php?p=56599743&postcount=6187

Attached screenshot of Motorola defy on lollipop. So there is a good chance for encore and lollipop.
[Nook Color Android Development] drmarble:
Thanks for the heads-up. I am looking at quarx2k's github and see some of the changes he made to the omap3 repository. Those look like they will fix some of our compile errors.

I will keep folks posted about any progress I make.
[Nook Color Android Development] deeper-blue:
quarx2k also wants to try using the 3.10 from the Moto360 for the Defy - this could be a mutually beneficial endeavor.
[Nook Color Android Development] bowguy:
For those of us trying building at home...

Do you have some general steps migrating from a cm-11 setup? There is a cm-12/android branch posted now - do you need to re-init?
[Nook Color Android Development] hwong96:
Yes type the init line and replace cm-11.0 with cm-12.0. Press enter. Then repo sync. Follow fattire's instructions a few posts earlier. Look at Quarx2k github for omap3 changes for ti omap3. The moto defy uses ti omap 3620 which is similar to encore 3621/3630.
[Nook Color Android Development] newellj79:
I don't have much to offer. I can build from source but that's about it. That said, even though I've long since put the nook in a drawer I'd love to help in anyway possible to see it run lollipop.
[Nook Color Android Development] pmgnet:
Agreed, that would be great.
[Nook Color Android Development] REV3NT3CH:
Hey if theres anyway i could contribute as well that'd be great... Ive developed for 4 higher end devices now and pretty decent with kernel and working rom side as well....had this nook for awhile and suprised to see how far its gotten...just hit me up anytime... i'd be glad to help
[Nook Color Android Development] bowguy:
imgdiff hangs

Has anyone run into the final creation of a build hanging up on imgdiff? I am getting repeated failures described exactly as follows:

https://code.google.com/p/android/issues/detail?id=42459

However I can't find any fix.

Thanks
[Nook Color Android Development] steven676:
I've just been disabling image OTA generation (sorry, on the road right now, so I can't pull the patch out of my tree). That will get you the pre-Lollipop file-based OTA package. (Disk image OTAs are needed for Lollipop's verified boot feature, which isn't going to work without bootloader support -- and probably won't be popular with hackers anyway.)
[Nook Color Android Development] bowguy:
Thanks. This is a lollipop build.

For anyone interested, I have a complete(??) build of CM12 done except for the final zip creation as describe above. Steps to reproduce:

Lollipop requires OpenJDK 7 so andbot is dead. I rebuilt my entire build environment from scratch including the OS - no previous sync's. This might be important.

After a clean sync, not all the encore files were created so I sync'd again with a roomservice.xml file with the android_device_bn_encore cm-11.0 branch and the android_kernel_bn_encore encore-omap3-3.0.y branch. This got all the encore files needed but probably the current kernel.

I then deleted the roomservice.xml to avoid the conflict with the repo init on cm-12.0

'I applied fattire's diff commands from his previous post.

Following drmarble, I changed wpa_supplicant_8_TI to the regular, non TI version.

I fixed the bluetooth errors in BoardConfig.mk - encore.mk changes didn't work for me.

All the ion errors were fixed by: cp bionic/libc/kernel/uapi/linux/ion.h device/bn/encore/include/linux/ion.h

At this point everything builds for me. the only error I get is:

make[1]: Entering directory `/home/bowguy/cm12/android/system/kernel/bn/encore'

make[2]: *** No rule to make target `dtbs'. Stop.

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory `/home/bowguy/cm12/android/system/kernel/bn/encore'

make: [TARGET_KERNEL_BINARIES] Error 2 (ignored)

This does not stop the build. Everthing progresses including creating image files until it hang forever on the imgdiff command.

I am stuck at this point. I have my entire brunch encore output if anyone is interested (it's not that long with everthing compiled).

Update: resync'd to see if this would kick it past the loop. Now stuck on upstream error "undefined ref to 'ff_ass_decoder' " Insert rude joke here...
[Nook Color Android Development] hwong96:
Look in /arch/arm/mach-omap2/Makefile.boot

Does it have

> +

> +dtb-$(CONFIG_MACH_OMAP3_ENCORE) += omap3-encore.dtb
[Nook Color Android Development] fattire:
I don't think the encore kernel supports device trees, does it? (dtb are the device tree binaries generated from dts device tree source file) and it sounds like something int he build system is looking for it.

Also, the diff I did was a long time ago when the shamu source first appeared. and is untested. It may need some tweaking and updating and such, so be sure to compare with current shamu and see if the changes make sense...
[Nook Color Android Development] steven676:
No device tree for 3.0, so you'd have to go find what in the CM kernel build is looking for that.
[Nook Color Android Development] bowguy:
Tried adding it but no change to the build.

Thanks
[Nook Color Android Development] bowguy:
Imgdiff is stuck because boot.img was created but the size is zero. I have been fighting with it but a recent sync created a whole slew of unrelated errors. I am stumped at this point and will be on vacation for a few weeks. Hope someone can run with it.?
[Nook Color Android Development] stevedat:
Does anyone know how to use xternal keyboard usb on CM 11? I have been looking for a way for ages.

---------- Post added at 07:42 AM ---------- Previous post was at 07:40 AM ----------

I got an unresponsive touchscreen NC so i need to find a back-up rom which able to use with external keyboard usb.
[Nook Color Android Development] drmarble:
CM-12.0 WIP

I have been working on a cm-12.0 port for our beloved old encores. I have gotten as far as making a flashable zip file. I have not made a bootable zip file.

My work is all available on github here:

https://github.com/drmarble/android_device_bn_encore/commits/WIP-cm-12.0

I use the regular cm-11 kernel and proprietary files sources. It builds fine without any hardware/ti/omap3 tree. If you include the cm-11 version you will have to patch it some. I haven't published my changes since it doesn't boot.

I am not sure just where the problems lie. It could be caused by my changing to BoardConfig.mk: BOARD_USES_UBOOT_MULTIIMAGE := true This was needed to create a boot.img file required by the zip building scripts as well as the ramdisk.img file that encores need. Maybe this is part of the problem.

I hope that these commits that fix the building of a flashable zip will help others who's greater skill with kernels and HALs and such will allow them to make the zip bootable.

Maybe I should have started a new thread since this isn't really CM11 anymore. I feel that creating new threads is pushy.
[Nook Color Android Development] Zippy Dufus:
Go to this page and try adding the memset.s patches. I had to do the to get the Linaro 4.8+ Encore builds to work. Probably the Google 4.8 compiler branch as the same issue.
[Nook Color Android Development] Jelixis:
Hello all! I'm a developer for the LGE-P970, I'm working on porting CM12 to our device and I see this device has the same SoC as our beloved P970.

Any advances related to CM12?

If so, please share your knowledge with us, the OB community so we can work on our SoC together, maybe mantain the hardware collaboratively?

Few questions from us:

1. Any updates on hardware support?

2. Have you got the SoC to work correctly?

3. Any information on what you have currently, and how you've achieved your current status?

Any answers appreciated. :)

https://github.com/Alphapixels

https://github.com/Alphapixels/android_device_lge_p970

https://github.com/Alphapixels/android_kernel_lge_p970
[Nook Color Android Development] newellj79:
Dead huh?
[Nook Color Android Development] fattire:
You never know... I haven't done anything for a while tho...
[Nook Color Android Development] Zippy Dufus:
I see that Lollipop has finally come to my low-spec Galaxy phone.

I tried to build dmarble's CM12 encore attempt - no luck.

But, CM11 is working great on this device and I occasionally I still use it. Maybe it is time to make a new build.

Hope springs eternal!
[Nook Color Android Development] fattire:
I'm working on 5.1 on my Note 4... if and when that's good to go maybe we can take a look at getting it going on encore too (?)...
[Nook Color Android Development] fattire:
slight but not much cm-12.1 progress.. (it builds to the end)

Had some time:

Package Complete: /media/test/lollipop/out/target/product/encore/cm-12.1-20150511-UNOFFICIAL-encore.zip

-rw-rw-r-- 2 fattire fattire 198M May 11 12:07 cm-12.1-20150511-UNOFFICIAL-encore.zip

THE ABOVE DOES NOT GET FAR. BLACKSCREENS W/BLOB ISSUES. But it builds to the end w/cm-12.1. The issue seems to be some API changes with the graphic blobs, which sluo has discussed previously. But for anyone wanting to build and debug further, here is a start:

Changes to the device are here (diff)

Changes to the build repository are here (git patches + a diff)

Thanks to sluo +

https://github.com/Alphasquare/android_device_lge_p970/commits/lollipop (this was a helpful reference)

https://gist.github.com/steven676/4b94d85f697883c6be59

PS-- sorry for the hackiness of the patches... commenting out an entire file for example.. it's just the debris left over from when I was getting it to build... it's not meant to stay this way and will certainly break the build for any other device.
[Nook Color Android Development] bowguy:
I got a clean build with cm-12 and drmarble"s device tree. I got stuck in a boot loop however after install.

Fattire - did you have anything in roomservice.XML?
[Nook Color Android Development] fattire:
I don't think I had anything in roomservice.xml beyond just making sure that I was pulling in the latest regular repositories... the issues I've had since a couple days ago, which I've been going back and forth with sluo included:

Issues with libsound.so and the HAL which I fixed with an old patch he had laying around.

Also, the kernel wasn't working (weirdly I had changed no source...) but going to a prebuilt kernel I knew was good worked.

I also had a new build error yesterday until I added this to encore.mk, though it probably should go in vendor/ -- I didn't even bother asking around to see what the deal was, i just added it so the build would continue.

PRODUCT_PACKAGES += \
org.cyanogenmod.platform-res \
org.cyanogenmod.platform \
org.cyanogenmod.platform.xml

Now I am actually able to get to the boot animation using a different pvrsrvinit but then see this:

E/InstallerConnection( 2414): connection failed
I/InstallerConnection( 2414): connecting...
I/InstallerConnection( 2414): disconnecting...

So something's still wrong--- sluo has taken a look too. You were able to get a build to complete using 12.1 source with no changes to /build?! Just to the /device folder? I posted the changes I needed to do and they were semi-extensive w/respect to a few areas, including the build scripts... but I haven't looked at the drmarble device... Just looking at it quickly he approached things a bit differently... like I reapplied the old changes to the build directory but looks like he did it locally...a lso I didn't touch fstab.encore and he did and I wonder if it would help with the weird directory errors I was getting. I'm not sure why he did stuff like:

-TARGET_SCREEN_WIDTH := 600

+TARGET_SCREEN_WIDTH := 480

It's super late but maybe if I have a chance tomorrow or this week I can look at what he did more carefully and compare to what I did-- or conversely you could take a look at my changes two posts up and see if they help. I'm most interested by the fstab changes...

I should ask-- how far does your build go, and what loops exactly?

I got to the dialog box where it was updating the apps (though it went straight to Running apps... or whatever and got stuck in the audio stuff..) If you're stuck with the audio, try sluo's patch above.

Also, if it seems to lock up, try from the shell stop and start to kick start the boot. Seems to kind of help get it around sticky corners.
[Nook Color Android Development] bowguy:
I built both 12.0 and 12.1 with no changes - only this in roomservice.xml

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="drmarble/android_device_bn_encore" path="device/bn/encore" remote="github" revision="WIP-cm-12.0" />

<project name="CyanogenMod/android_kernel_bn_encore" path="kernel/bn/encore" remote="github" revision="encore-omap3-3.0.y" />

</manifest>

I then managed to install the zip on an SD install. The install on CWM 6.0.4.8 was good - but when I try to boot it never even gets to the animated logo. It just keeps going to the uboot menu, then loading, then reboot. Nothing gets started long enough to connect via adb.
[Nook Color Android Development] fattire:
Sounds like maybey ou have the same kernel issue-- what happens i fyou copy a working/recent uRecImage to uImage?
[Nook Color Android Development] bowguy:
I tried a recent uRecImage and even flashed this kernel but same behavior. If I have time I will try to look and your edits vs drmarbles but it may be next week till I get to it.

Thanks
[Nook Color Android Development] mejack03:
Hello, Can someone tell me what is the model number of the touch panel being used in Nook Color and also point me to the Touch Screen drivers.
[Nook Color Android Development] fattire:
As you can see in the defconfig:

CONFIG_TOUCHSCREEN_CYTTSP_I2C=y
CONFIG_TOUCHSCREEN_FT5x06_I2C=y

NC has two touchscreens and accompanying drivers. The cypress ones came out first, and the Focal Tech ones were in a later model, but I think they were kind of similar drivers if I remember right:

The drivers are here.

Hope this helps

ft
[Nook Color Android Development] mejack03:
Actually for one of my college project i'm thinking of using touch panel to detect the shape of the object which is placed on touch panel. I'm not sure its really possible, just want to try playing around with my nook's touch panel. If anyone has any suggestion/comment pls do let me know.

Thanks
[Nook Color Android Development] drmarble:
booting cm-12.0

With the help of steven676 and fattire I got cm-12.0 to boot. You can't do anything with it but it boots. No network, no mounted storage (emmc or sdcard). Can take a screen shot but can't store it so no screen shots.

I need to polish my github skills and will put up the working device tree and document the other changes required. Here is a sample from IRC:

<drmarble> I synched to your latest cm-11.0 device with fattire's and my changes on top. gcc4.7 to compile the kernel. Some of fattire's build patches. Blank directory for hardware/ti/omap3.

<drmarble> Had to flash over a working cm-11.0 build. Kill SurfaceFlinger when it freezes and then kill SystemManager when it freezes on a java-io exception.

It still has a ways to go before it can be called working. It will probably never become official because of the changes/hacks to cm's build system. I think these changes will also work for cm-12.1. I will give that a try soon.

If anyone cares, here is a link to the logcat: http://paste.ubuntu.com/12423976/

As I said, I will put the device tree changes up on github and will post the required build system changes here. Don't expect anything soon. I work slowly and do my hobbies even slower. I just wanted to tell you folks that progress is being made.
[Nook Color Android Development] pmgnet:
Cool!
[Nook Color Android Development] drmarble:
cm-12.0 running

Success, cm-12.0 now boots without any adb shell intervention.

[/IMG]

http://imgur.com/YjPoCoP

Still needs work, Settings->developer doesn't work. No wifi, Many other fails. CM-12.1 doesn't boot. Still, it is a ray of hope.
[Nook Color Android Development] fattire:
Yay!

NOICE!
[Nook Color Android Development] XxAmyJo87xX:
Sweetness!!!! Can't wait till its up and running you guys are awesome!!!!
[Nook Color Android Development] drmarble:
I have fixed part of the problem with hardware/ti/omap3. The conficts were between omx and the ion implementation. I just removed the omx directory. Some additions from Rhyre on github are included. The tree is here:

https://github.com/drmarble/android_hardware_ti_omap3/tree/no-omx

I will be including zram swap in the encore device tree. It doesn't cause problems and we sure are short on memory.

Keep reading the README.md file on github.

Enjoy
[Nook Color Android Development] bowguy:
I will try to build this weekend and if successful see if it runs on a SD card.

Thanks!!
[Nook Color Android Development] drmarble:
I should add that I do Engineering builds. They give more debugging.

lunch cm_encore-eng

time make -j9 bacon 2>&1 | tee make.log

I have an I7 now so I use -j9. You may need fewer, or more but that makes me jealous.

I guess you could also use brunch cm_encore-eng.

I don't know if userdebug will work. I'll take the greater debugging over performance for now.

Enjoy
[Nook Color Android Development] drmarble:
Do not trust the recovery that may or may not be built with this rom. It should not work since I disabled lots of recovery stuff just to finish the build. I use the cwm recovery steven676 posted earlier in this thread.

I have made some more progress. It now wakes with the home (n) button. I reenabled zram. I got hwc running; use my hardware_ti_omap3. I am working on sound now and hope for inspiration to get settings -> developer options fixed.

Good luck with an SDcard install. I have included all of steven676's changes to enable it but I haven't tested. I just do emmc installs.
[Nook Color Android Development] steven676:
Actually ... and I've been meaning to post about this for a while ... CM now autobuilds recoveries. If someone could test http://download.cyanogenmod.org/get...50831-SNAPSHOT-XNG3CAO3FN-encore-recovery.img (it's a ZIP file -- rename it to .zip, unpack it, and push kernel to /boot/uRecImg and ramdisk-recovery.ub to /boot/uRecRam), that would be greatly appreciated. (The version number should be newer, but it should otherwise be equivalent to the existing hand-build recoveries I've been posting.)
[Nook Color Android Development] bowguy:
I got a little stuck. Here is my roomservice:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="drmarble/android_device_bn_encore" path="device/bn/encore" remote="github" revision="cm-12.0-wip1" />

<project name="steven676/ti-omap-encore-kernel3" path="kernel/bn/encore" remote="github" revision="encore-omap3-3.0.y-l-backports" />

<project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" remote="aosp" revision="refs/tags/android-4.4.4_r2"/>

<project name="drmarble/proprietary_vendor_bn" path="vendor/bn" remote="github" revision="cm-12.0-wip" />

<project name="drmarble/android_build" path="build" remote="github" revision="encore-12.0" />

<project name="drmarble/android_hardware_ti_omap3" path="hardware/ti/omap3" remote="github" revision="no-omx" />

</manifest>

But trying to sync I get a:

fatal: duplicate path build in /home/bowguy/cm12/android/system/.repo/manifest.xml

I think I need to remove a project in roomservice. Any help would be appreciated.

Thanks
[Nook Color Android Development] fattire:
removing projects....

Yeah to remove a project you just say

<remove-project name="CyanogenMod/android_hardware_ti_omap3" />

See here for more info.