yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] grayfoxmg1:
I have a quick question, and depending on the answer I will not bother you until I have re-read the entire thread. I was wondering, would I be able to build my own CM10 rom on my laptop running Win7 64bit if I use cygwin?
[Nook Color Android Development] fattire:
I don't know of anyone who's built using cygwin... I have a friend who used to swear by it, but I've never really used Windows so I can't answer that one... anyone else?
[Nook Color Android Development] meteorrock:
I am looking it over right now. Come check my updated developers blogger thread down in cyanogenMod. You will need to toolbox in a bunch of tools though, like compilers and gnupg's , Cygwin Python, coreutils. Most are included in the download install. Its slow compiling though. But for those that do not like flopping back and forth on a dual boot OS system, as I like my windows OS for games on-line, it does alright. The link is here. http://forum.cyanogenmod.com/topic/...h-me-trying-to-learn-how-to-code/page__st__20

Since cygwin uses a unix bash shell if you are used to using linux, it will take some relearning on some of the command inputs. Most work though as before. I included some links in that thread for some cheat sheets. |chmod is not working as expected though.

Its also a tad buggy, nothing that can not be solved though by looking online over at stackoverflow.com. Ran into a few bugs on it already. If you do not mind being in a *nix environment or linux environment and not tied to the windows OS, linux is still the ultimate environment to work in.

Have fun guys :)
[Nook Color Android Development] ioos:
I'm a little confused where to get the proprietary files for CM10. I don't have them if I can't build it and I can't build it without them. Someone mentioned eyeballer's git, but I don't understand how to find them. I expected the directory structure to match the build directories; it doesn't.
[Nook Color Android Development] bytte:
@grayfoxmg1

Assuming you have enough free disk space and a decent amount of memory virtualbox could become your friend. I haven't built CM10 with it but it built my CM7.1 kernels.
[Nook Color Android Development] kevin37:
I'm sorry to bother but {'m not sure what i may have done wrong this is where the repo sync stopped three times. If someone could help id be grateful. Thanks Kevin

remote: Counting objects: 20800, done.

remote: Compressing objects: 100% (8263/8263), done.

remote: aborting due to possible repository corruption on the remote side.

fatal: early EOF

fatal: index-pack failed

error: Cannot fetch CyanogenMod/android_prebuilt
[Nook Color Android Development] bytte:
Prop Files

You are too deep!

Everything under eyeballer/proprietary_vendor_bn/encore/proprietary/{bin,etc,lib,usr}

goes under:

~/android/system/vendor/bn/encore/proprietary

Then do make clean
[Nook Color Android Development] ioos:
Ok, I replaced the proprietary files with those from eyeballer's git. Unfortunately, it's still boot looping at the CM10 splash before adb even starts.
[Nook Color Android Development] bass0324:
I am having the same problem.
[Nook Color Android Development] eyeballer:
Did you use the 'jellybean' branch?
[Nook Color Android Development] jschill31:
Hello,

It is possible you have a Nook like my unit and one other that I know about. It is not a "new" version and also not the "old" version but somewhere in between. I purchased my unit as a "B" stock piece from Barnes and Noble, it had clearly been serviced. I have been building this for several weeks and I also am not able to get past the boot-loop using this repo. I am also not able to get a logcat to know where to start...but there is another repo that will build and boot for you if you read the forum several pages back.;)

Cheers
[Nook Color Android Development] ioos:
Yes, form here: https://github.com/eyeballer/proprietary_vendor_bn/tree/jellybean/encore

I think you're talking about riverzhou's, right? The link to his local_manifest doesn't seem to be working. Even so, according to the posts following his, there were some flaws using his sources. Weren't they working to merge his changes into what we've all been using.

Do you know what makes your nook different? How can you tell? I bought mine new about two months after they were released. My assumption was that I had the "old" version.
[Nook Color Android Development] jschill31:
Hello,

As far as the Nook goes there is no physical appearance difference that I can see. The only reason I have this assumption is you are not able to boot (bootloops) and also not able to get a logcat. The kernel does load, there is no reason the Nook should not be outputting a logcat, it is a true mystery to me? I have only been contacted by one other user and when we compare notes our Nooks act exactly the same...as it also sounds like yours is doing. I will send you a PM concerning the other.

Cheers
[Nook Color Android Development] bass0324:
When I try to run the ./setup-makefiles.sh script, it says that the directories could not be created. Any help with this? Also, if I try to typing add_lunch_combo cm_encore-userdebug in, it says unknown command. What am I doing wrong? Also, I copied the proprietary files from eyeballers git to the appropriate folder. Is that alright or should i try getting them from my nook directly?
[Nook Color Android Development] csrabear:
I am experiencing the exact thing. I just compiled CM10 and installed. Never gets past the bootsplash and no adb.
[Nook Color Android Development] bitstra:
@all devs

@all devs,

I've seen since sept-12th, that cm10-unofficial-encore compiled ROm can't boot any more!

Now I've found a change of rootdir/ueventd.rc on cyangenmod.com here: http://review.cyanogenmod.com/#/c/23169/1, that requires a kernel change to send the uevent.

Anybody of the dev gurus can have a look at this and help here. I'm stuck in this problem atm.

For the moment I have deleted the changes in rootdir/ueventd.rc local and let compile again.

thanx in advance

bitstra
[Nook Color Android Development] doncaruana:
Well, the build you found is from riverzhou, who was on this thread a while back. Krylon asked riverzhou to get in sync with everyone else and it appears that riverzhou decided to go off and do his own thing.

Read Krylon's post and let the buyer beware I suppose.
[Nook Color Android Development] krylon360:
Now thats a kang if I ever saw one. But, to each his own I guess.

We've asked that custom compiles not be posted yet, but obviously, river disregarded that, and posted this on a Chinese site to avoid a ban from XDA.

He has sent a few pull requests which I have responded to stating all he changed was a cflag from the one we are using now, to one he randomly came up with.

He obviously doesnt want to work with the rest of us, is doing an obvious cmkang, and if translate is working correctly, pretty much states he's waiting on us to do more fixes.

We've (Eyeballer, fat-tire and myself) have asked him on multiple occasions to join irc, and for him to base his work on what we've done already and submit a pull request. He has yet to do so.

So, trust that rom with a grain of salt because we wont be supporting his build here.
[Nook Color Android Development] keyodi:
Let me see if I understand this correctly...You

found

a rom on a Chinese site and decided, "what the hell let me install it"?

Please feel free to PM me your SSN# and credit card#'s. I could go on a long winded rant on the security risk of installing an untrusted rom, but all I will say is, if you didn't build the rom yourself or you didn't get a build for one of the trusted devs, then don't install it!

This is why android gets a bad rap on security....
[Nook Color Android Development] bass0324:
Does anyone know the reason for the boot loops? I get to the updating android apps, then it goes all the way through until it gets to finishing boot and then reboots everytime. Any ideas?
[Nook Color Android Development] krylon360:
If he does that, you can get your new NC... but then you could get us all N7's also. :P
[Nook Color Android Development] krylon360:
I'll look into this tonight if I get the chance. Looks like something that was pushed upstream, so I'll do a sync, and fresh build.

Will also update fw/av on my git with the recent (past 2 days) changed from CM.
[Nook Color Android Development] tomsawyer14:
Any time I get something randomly weird from builds, I make sure to make clobber or make clean, do a repo sync and then brunch encore for a fresh build. Doesn't always fix oddness but it can help.

And yes I realize folks are getting the fruit loops on fresh builds. I'm not a dev and can't even pretend to be one. Can only offer what works for me.
[Nook Color Android Development] bytte:
Goto the dir with the setup file and type

script /tmp/script

cd ../../..

cd vendor

ls -lR

CTRL-d

Post the results in /tmp/script on the web - pastebin - with a link here
[Nook Color Android Development] ioos:
That's a neat trick!
[Nook Color Android Development] les02jen17:
One quick question: Can I build using Windows 8 or do I need a linux-based operating system (like Ubuntu) to build? Thanks!
[Nook Color Android Development] fattire:
You can run ubuntu in a virtual machine hosted on a windows pc. Easiest way to do it if you've got a windows machine, plus you'll get some hands-on Linux experience with no risk... google "virtualbox" for a free vm. Good luck!
[Nook Color Android Development] voit:
If you have Win8 Enterprise edition you may enable Hyper-V and have fun with any virtual OS.
[Nook Color Android Development] riverzhou:
It's because CM10 changed their building system .

The major problem is ramdisk.img . The new building system can not gen currect ramdisk.img .

You can open the upadate zip file , replace the ramdisk.img using previous version and everything will be OK.

---------- Post added at 01:51 AM ---------- Previous post was at 01:33 AM ----------

I did not remember Krylon ask me to join irc, only fat-tire did. And I am not using irc recently years because it's not popular at China .

My work has a totally different starting point , the device setting is from my kindlefire and kernel is from lenovo a1 kernel and steven676's kernel.

I also using different vendor file ,it's from lenovo a1 . If I push my kernel to keyodi's branch now , all rom building from it will be blank screen except mine.

I wrote a short guild to build cm10 rom with a very easy way, but krylon stopped me Immediatly .

It's a fast and smooth ROM , many people using it at China now, they all very like it. It has full features, including hardware hd video decode.

And everyone can build it with a easy way . But krylon do not like it . He stop me to talk it here.

It's totally different from kindle fire's forum here,

In kindlefire forum , there're very large number ROM's and everyone work on his mind , everyone is very nice.

In this forum, I find some people are very confuse on how to build NC CM10 ROM, but krylon stop me to help they.

I can not understand it.

In fact , it just need a local_manifest.xml file and everything will be very easy.

With a correct, the all things to get and build ROM is:

repo init -u https://github.com/CyanogenMod/android.git -b jellybean

cp local_manifest.xml .repo/

repo sync

. ./build/envsetup.sh

time brunch encore

Yes, it's ALL that you need do .

But it never be here and do not allow anyone bring it here.

---------- Post added at 01:55 AM ---------- Previous post was at 01:51 AM ----------

Edit the ota zip package , replace the ramdisk.img file using previous version's.
[Nook Color Android Development] krylon360:
WRONG!

Please stop giving false info. If it was a ramdisk issue, it wouldn't even get to the bootanimation due to the ramdisk not loading. A Ramdisk just doesn't fail when optimizing the apps. The ramdisk is fully loaded before it even finalizes the boot.

The last line of our init has this:

on property:sys.boot_completed=1

log "== init.encore.rc: on property:sys.boot_completed=1 -----------------------"

Which if you read your logcat, you would see that. This lets us know that the ramdisk has fully loaded.

The ramdisk builds just fine, and if you are saying use an older version due to CM10's not building correctly, then that to me seems like you are saying use one from cm9, which in that case, would cause a pre-bootani bootloop due to cm9 being .32 and cm10 being 3.x.

2 different ramdisks completely.

The loops are most likely caused by recent bionic changes upstream. I'll do a fresh build tomorrow when I wake up and verify and submit a patch if need be.
[Nook Color Android Development] krylon360:
Perhaps you should learn Chinese better then? Because that's 5 words. :)

Now, back onto dev discussion.
[Nook Color Android Development] eyeballer:
riverzhou,

Our intentions were always to work together - that's why this thread even exists in the first place, to be open to contributions from the community. We understand you are using a different base for your builds. The reason we ask you to join us on IRC is because everyone else is already there, krylon, fattire, steven. If your base seems more stable then our project could move but it requires discussion and a forum is just not an efficient place for it. Whether IRC is popular or not shouldn't sway the progress...
[Nook Color Android Development] riverzhou:
The device setting is almost finished.

Kernel is not very stable yet. I still havs some issue on it now. I just wanna finish my current work.

I am not very interesting on nook color, omap3 is too old, missing some features needed by ICS or JB. And it do not has much support from TI now.

I'm focusing on the kernel now, testing everything and searching anything I can improve.

When I finish the works on my planlist, I will create a sequence of pull request on top of keyoid's kernel ,just as steven did.

The time may be this month or next.

After that, I will go back to kindle fire . omap4 is much more modern and much more interesting,

And I also maintain a KindleFire ROM on our Chinese forum.

Everything is on my github. All is open.

https://github.com/riverzhou

You can visit it anytime.
[Nook Color Android Development] bytte:
Please start a new thread where we can discuss your work. That will be your thread and we will all be happy.
[Nook Color Android Development] riverzhou:
I will consider it .

---------- Post added at 11:00 PM ---------- Previous post was at 10:47 PM ----------

Finally I find the reason and solution about CM10 rom boot circle recently.

They update their building system , from themselves to AOSP's .

This will cause static link program not fit for omap3 ( Cortex A-8 ) .

There're two static-link program in ramdisk.img , init and adbd , so ROM booting is circle .

For now, the best solution is use prebuilt init and adbd file to ramdisk.img

Get them from my github :

https://github.com/riverzhou/device_encore/raw/jb-dev/prebuilt/root/init

https://github.com/riverzhou/device_encore/raw/jb-dev/prebuilt/root/sbin/adbd

Put them to you prebuild fold

And then add them to your device.mk :

For example :

PRODUCT_COPY_FILES += \

$(LOCAL_PATH)/prebuilt/root/init:/root/init \

$(LOCAL_PATH)/prebuilt/root/sbin/adbd:/root/sbin/adbd \
[Nook Color Android Development] meteorrock:
"I second that motion." Not interested in agendas with the kindle fire, <riverzhou>, in this thread for the nook color. Try to work with the guys up in IRC. As a femme I use it. Lets not get sidetracked with stereotyping. I know the IRC environment is kind of intimidating but that is where the top developers like to work in at the moment. PM me if you need to <riverzhou> if you need any help working with the guys up there if you need to ok?

Also he is from China, they have lots of IP addresses and /or TCP ports blocked from there, he might not have access to using IRC from that country. Look into using a free socks proxy from the Internet if you do <riverzhou>.

:cool:

Stay on target guys. :p
[Nook Color Android Development] bitstra:
I want break a lance for riverzhou,

though riverzhou seems to have a problem to join the main stream here in ralation to collaboration:

his hint to the boot problem of CM10 source since sept-12th, pointing to the ramdisk,img, seems to be right.

I've compiled CM10 with sept-15th sources synchronised. It won't bot...

Then I injected the ramdisk.img out of a CM10-compilation of sept-06th. And it's booting now as usual.

All works fine!

The speed and smoothness of the act. CM10 is amazing. And with a forced partial wakelock in background the wifi lives over hours,

dataconnection dosn't die with that workaround.

Also awaking from sleep works fine with that workaround!

I use 'wake lock power manager' from play store for holding partial wakelocks in background. look here: https://play.google.com/store/apps/details?id=eu.thedarken.wl&feature=nav_result#?t=W251bGwsMSwxLDMsImV1LnRoZWRhcmtlbi53bCJd

The only issue I have atm, are some missing audio codecs. All other JB features are fine and stable!

regards

bitstra

@riverzhou

please make your own thread here on xda for your nook color-jb-branch, to keep dalingrin's thread clean and free of unwanted discussions.
[Nook Color Android Development] krylon360:
Resync. Boot and adb are fixed thanks to sluo and eyeballer. It was the bootcomplete sys prop causimg the boot AND adb issue.
[Nook Color Android Development] ioos:
I did a make clobber and rebuilt using eyeballer's proprietary files. It still bootloops, but I was able to pull a logcat this time: http://pastebin.com/L1JahC3v

What kind of errors should I be looking for? There's so much in there, it's tough to determine what's important.
[Nook Color Android Development] krylon360:
09-17 02:18:22.335: I/SurfaceFlinger(100): vendor * *: Android

09-17 02:18:22.335: I/SurfaceFlinger(100): version * : 1.4 Android META-EGL

Get rid of the a1 binary. Ours isnt 1.4.

Mixmatching different binaries from different devices can always lead to issues due to being built from different sources even if the hardware is the same.

Also it looks like the Entropy Service is crashing as well. Might wanna try doing a completely fresh sync. With so many repos/try this/try thats on this thread, its possible your local source might be the issue.

Just throwing out some ideas.
[Nook Color Android Development] cybertimber2007:
Please do! There is no one that will say you can't post a new ROM or branch (etc), but it must be done in an new thread. Heck that's why we have the CM [User] thread and the CM [Dev] thread. But your help would be much appreciated i'm sure.
[Nook Color Android Development] bodi524:
I am trying to setup andbot. I download andbot.run.

When I execute I get

chroot: failed to run command `sh': Exec format error

Unmounting /proc, /sys, /dev and /dev/pts

I have tried in a VirtualBox and now Dualbooting my laptop.

I get the same thing

:crying:
[Nook Color Android Development] bytte:
Do you have a 32 or 64 bit CPU / OS?

Sounds to me like you are trying to run a 64 bit binary on a 32 bit system.
[Nook Color Android Development] bodi524:
OK. You are correct. I didn't think about it. But I have the 32bit Linux Mint.

I am setting up the environment the old fashioned way now.

Probably will learn more that way:D
[Nook Color Android Development] jackgibbs:
so am I supposed to use eyeballer's proprietary files instead of connecting to my nook running cm9 and running the extract files script? does either way work? and if I use eyeballer's, after downloading and moving all the files into the /proprietary folder, do I need to do anything else before 'brunch encore', (I guess what I'm asking is do I run this './setup-makefiles.sh script in android/system/device/bn/encore.' still like it says to do with the files that come from the nook.) thanks!
[Nook Color Android Development] krylon360:
No,

If you grab the jellybean branch from eyeballer's git, and then run the extract-files.sh, it will overwrite eyeballers.

Just use the ones from eyeballers git and skip the step for setup-makefiles / extract-files
[Nook Color Android Development] bytte:
If you have previously built, do a make clean before brunch.
[Nook Color Android Development] jackgibbs:
argh. I thought I had it but I guess I'm still missing something? when I run brunch encore, it gives me the dependencies file not found bailing out message at the top, then a very lines later I get this

find: `src': No such file or directory

then a whole bunch of stuff, then it stops at

make: *** No rule to make target `out/target/product/encore/kernel', needed by `out/target/product/encore/recovery/root.ts'. Stop.

I've tried resyncing, done make clean make clobber...am I missing a file, or am I missing something needed to be installed?

p.s. I'm on a ubuntu 12.04 vm with java6u35 if that is an issue. help?
[Nook Color Android Development] Divine_Madcat:
Just a quick notice - i have done some thread cleanup of the last few pages, to make it easier for people to follow actual dev happenings. Please help keep the thread organized guys; non dev discussion needs to happen in other threads.. lets not derail the great work our devs (whom we are VERY lucky to have) are doing..
[Nook Color Android Development] bodi524:
I sucsessfully built a CM-10 for the Nook Color.

I am seeing alot of random freezes.

Is this normal at this time in development, anyone else seeing the same?
[Nook Color Android Development] mateorod:
I don't know the state of this, as I haven't built CM10 for encore in about a month, but when last I built I had to build the kernel separately. It should be in your tree already, but you can download it from fat-tire's github page.

Your BoardConfig.mk needs to have

TARGET_PREBUILT_KERNEL := device/bn/encore/prebuilt/boot/kernel

(I think that is where they put it. I actually was putting it in my device directory for awhile, but I seem to remember that started causing a conflict at one point.)

It may look like you can't download the kernel from Github, but it is available as a binary file.
[Nook Color Android Development] cybertimber2007:
CM9 09/04 build

Devs, would someone mind taking a look at the logcat's found here and my brief analysis here ?

From what I can tell after the system has been up for awhile or heavily used suddenly apps start dying with error messages. From the logs, the apps are reporting that they can't write to files under /data with the error that it is read-only (can also come up when it is full). Even screenshots fail to save, saying that the storage is full. Looking at "df", /data it isn't full, and memory (RAM) isn't full either, yet everything starts working again after a reboot.

I was recently reading over a suggested change for /tmp on tmpfs (Fedora, Debian, Ubuntu) and it mentioned similar problems could happen. Not sure if tmpfs is related, but *something* is causing apps to think /data is either suddenly read-only, or full.

This was a clean install by the way. I haven't yet figured out the source but I'm trying. I'm wondering if something in the logs would jump out to someone more experienced in analysing them.

Edit: Hmm, looking at the output of "df" is a little odd...

Filesystem | Size | Used | Free | Blksize

/data | 1G | 122M | 1G | 4096

If 122M was used, I would expect Free to show a little less. I'm testing with

dd if=/dev/zero of=/data/test.img

to see it it can write a file and use up the remaining space.

Edit: It could. It wrote 1862631424 bytes, or 1.73GB

Edit 2 (or so):

I found a relevant post - http://xdaforums.com/showthread.php?t=1783671

I shut down and mounted the card in a linux system and tried a fsck.ext4 on the /data partition. Going to see if this has any effect. it did fix some errors.

Edit: nope, still happening. In fact when it did I opened Terminal Emulator and started some testing.

df shows /data still has space available. touch /data/test.txt fails with "/system/bin/sh: cannot create /data/text.txt: Read-only file system"

ls /data fails with opendir failed, Permission denied.

Mount suddenly does show /data as being mounted ro!

But what the heck could be causing it?!
[Nook Color Android Development] krylon360:
we do inline building now.

The kernel should be sync'd down with you local manifest.