yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] riverzhou:
I found a new vendor file source.

http://download.lenovo.com/slates/a1/ICS_OTA/

I take sgx drivers from it and have a test, it not match keyodi's kernel.

Those BeagleBoardXM files from TI website match keyodi kernel, I have tested. It's fine.

Maybe, lenovo A107 ICS rom used the newest kernel from omapzoom.

---------- Post added at 07:54 AM ---------- Previous post was at 07:51 AM ----------

I create a new device git on github.

The m2 branch is bootable.

device fold:

https://github.com/riverzhou/device_encore/tree/m2

local manifest:

https://raw.github.com/riverzhou/local_and_script/jb-dev/local_manifest.xml
[Nook Color Android Development] chilre:
I reverted back to using fattire's repo and not enabling hwcomposer, and i was able to boot into CM10. A couple of questions / observations that arose during / after this process:

1. When I used sluo's wifi modules, the wifi driver failed to load and I got the following error

E/WifiStateMachine( 325): Failed to load driver!
E/WifiStateMachine( 325): DriverFailedState

2. When installing CM10 on sd card, i notice that the boot partition (1st partition) of the sd card is mounted as /sdcard, instead of the 4th fat32 partition. I had to manually change it to 4 (it was set at auto). Even in case of CM9, I noticed that it was set to auto in the installation zip, which was changed to 4 during installation. But since this is not happening in CM10, is this an issue with the install script? and if so, where do I have to make the change? (I am still getting used to the whole setup, and am a little confused as to the locations of various features)

Thanks. will try this out.
[Nook Color Android Development] jschill31:
Hello,

I too will try this out...thanks!

EVO LTE
[Nook Color Android Development] ioos:
I'm still stuck. I've got all of my dependencies resolved, but the build still fails after "brunch encore" with:

Device TableGen (gen-subtarget): libLLVMARMAsmParser <= external/llvm/lib/Target/ARM/AsmParser/../ARM.td
Device TableGen (gen-disassembler): libLLVMARMDisassembler <= external/llvm/lib/Target/ARM/Disassembler/../ARM.td
ERROR: could not open directory /home/ioos/b-nook/out/target/product/encore/obj/KERNEL_OBJ/../../system/usr/lib/modules/99.98.3.0.8+: No such file or directory
FATAL: could not search modules: No such file or directory
make[2]: *** [_modinst_post] Error 1
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/ioos/b-nook/kernel/bn/encore'
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....
Device TableGen (gen-enhanced-disassembly-info): libLLVMARMDisassembler <= external/llvm/lib/Target/ARM/Disassembler/../ARM.td
[Nook Color Android Development] riverzhou:
Can you print your local_manifest.xml ?

It seems you do not have current kernel or wlan source.
[Nook Color Android Development] tomsawyer14:
I'm trying riverzhou's repositories. On the plus side, it builds and seems to be really fast. The downside is I can't get wifi or adb to work, but it does mount sdcard so at least I can move files. adb devices seems to indicate a permissions issue now, but I'm not sure why.

I'm doing a make clobber now to see if that solves the issue, so it'll be awhile before I can report back.
[Nook Color Android Development] unknown_world:
What's going on guys..

We use to have 3 repos now i lost count. please organise.
[Nook Color Android Development] ioos:
Here is my local_manifest.xml. I took it directly from the link in the google doc. Is there another one that I should be using?
[Nook Color Android Development] tomsawyer14:
You don't have to use any of them. The local_manifest from the CM10 build guide works just fine. These other repos just contain possible fixes and alternatives that they may merge into that tree, like a possible wake lock fix from that Lenovo source that's been merged today for example.

Personally I've been having fun trying to work from the different sources. It's a learning experience :D
[Nook Color Android Development] riverzhou:
I create a new device git on github.

The m2 branch is bootable.

device fold:

https://github.com/riverzhou/device_encore/tree/m2

local manifest:

https://raw.github.com/riverzhou/loc...l_manifest.xml

You can try my local manifest.

---------- Post added at 08:10 PM ---------- Previous post was at 08:08 PM ----------

The problem of adb is fixed now.

And , if your wifi doesn't work , reboot into recover , do nothing , and then reboot into android again. It will work.

---------- Post added at 08:17 PM ---------- Previous post was at 08:10 PM ----------

Yet, It should be the fastest jellybeam rom on NC now.

I deeply clean and reorg the device fold .

And it has many additional optimizations, esp for bionic .

It also has a new audio driver from source code.
[Nook Color Android Development] unknown_world:
can you tell me which repo has lenovo source?
[Nook Color Android Development] riverzhou:
Here is lenovo A107 kernel source code :

https://github.com/riverzhou/encore-omap3-3/tree/lenovo

---------- Post added at 08:57 PM ---------- Previous post was at 08:45 PM ----------

rowboat release a new jellybean from for beagleboardXM :

beagleboard-xm-jb.tar.gz

https://code.google.com/p/rowboat/downloads/detail?name=beagleboard-xm-jb.tar.gz&can=2&q=

https://rowboat.googlecode.com/files/beagleboard-xm-jb.tar.gz

It has the newest SGX driver(it should be DDK 1.9 or 1.10):

root@ubuntu:/river/rowboat/beagleboard-xm-jb/Filesystem/system/lib/egl# strings * |grep build

OpenGL ES 2.0 build MAIN@956079

OpenGL ES GLSL ES 1.00 build MAIN@956079

We currently use this:

root@ubuntu:/river/cm10/device/bn/encore/vendor/imgtec/lib/egl# strings * |grep build

OpenGL ES 2.0 build 1.8@789263

OpenGL ES GLSL ES 1.00 build 1.8@789263
[Nook Color Android Development] bytte:
Building on 32 bit Ubunto 12.04

I'm trying to build on 32bit, following the Fattire's guide. Having run ~/android/system/build/envsetup.sh, brunch / make behave as if this is a 64 bit system.

:~/android/system$ make bacon

/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: cannot execute binary file

~/android/system$ file prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc

prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, BuildID[sha1]=0xf8e11f40cf6b10fa26e6fea774d9d94058c53595, stripped

Is there anything I can do short of installing 64 bit Ubunto?
[Nook Color Android Development] ioos:
I really appreciate your help. It looks like the local_manifest link is bad though. Takes me to a 404 page.

Once I do replace the local_manifest, how far back in the build steps should I go? Do I just sync, then brunch? Or do I need to delete things created by the previous manifest?
[Nook Color Android Development] riverzhou:
https://raw.github.com/riverzhou/local_and_script/jb-dev/local_manifest.xml

copy it to .repo/

and then :

rync -j16

rm out -rf

. ./build/envsetup.sh

time brunch encore

---------- Post added at 11:09 PM ---------- Previous post was at 11:07 PM ----------

You can delete :

<project name="KFire-Android/kernel_omap" path="kernel/amazon/otter" remote="mygithub" revision="4AI.5" />

<project name="riverzhou/device_otter" path="device/amazon/otter" remote="mygithub" revision="jb-dev" />

from my local_manifest.xml

It's for kindle fire .

---------- Post added at 11:11 PM ---------- Previous post was at 11:09 PM ----------

If you can build and boot, give me a feedback.

Let me know how do you think about it.

---------- Post added at 11:16 PM ---------- Previous post was at 11:11 PM ----------

I use ubuntu 12.04 server I386 on virtualbox 4.1.20 on windows 7 X64 .

You should change arm-gcc from google to linaro.

I use linaro gcc 4.6.4 {gcc version 4.6.4 20120630 (prerelease) (Linaro GCC 4.6-2012.07}.

I have some scripts to change gcc at here:

https://github.com/riverzhou/local_and_script

It's work. It's fine.
[Nook Color Android Development] jschill31:
Hello Riverzhou,

I had some time tonight to try your device & local manifest. It did not run long before stopping with the following error:

make: *** No rule to make target `device/bn/encore/vendor/ti/etc/firmware/ti-connectivity/wl128x-fw-4-mr.bin', needed by `out/target/product/encore/system/etc/firmware/ti-connectivity/wl128x-fw-4-mr.bin'. Stop.

make: *** Waiting for unfinished jobs....

jim@jim-desktop:~/android/system$

It seems like there are several files missing form your device folder?

Cheers
[Nook Color Android Development] riverzhou:
updated.

resync.
[Nook Color Android Development] MapleSyrup:
That problem is because the way kmod is compiled for Arch Linux (since a recent version), when depmod (part of kmod) is called, it will search for /usr/lib instead of /lib (hence the /system/usr/lib/modules and not the /system/lib/modules, which it does exists).

One way to solve this is creating a symbolic link in system/usr to system/lib. Other way is removing the stock kmod and then compile and install it from source. There's an AUR package that you install manually, with packer or yaourt, you'll just need to change in the PKGBUILD the option for bootstrap --with-rootprefix=/usr to --with-rootprefix=. This will work for compiling android, but it might mess with your Arch Linux install.

I guess there's a better way to solve this problem changing something in the configuration files of the android build, but I don't know it yet.
[Nook Color Android Development] lekofraggle:
riverzhou,

I tested out your repo. It is quite fast but has no wifi on my device (rebooted 3 times using recovery). It also seems that the launcher is in phone mode (I have not poked around the setings yet).

As soon as I figure out wifi, I will probably go with Nova anyway (I know, it slows things down, but is so customizeable).

Thank you for it.

~Leko
[Nook Color Android Development] krylon360:
as much as we appreciate this, please stop.

Your device tree is based on the KF. We do not have a cortex-a9 cpu which your BoardConfig calls for, the media_codecs only calls for software decoders. Your local manifest removes the hw/ti/omap3 source, and doesnt replace it with any of the oes we have worked on.

We are trying to consoliate everything into 1 working tree and having multiple repos floating around isnt helping. If you have something that works, please submit a pull request.

What we know works:

fat-tire's device tree

sluo's wlan drivers

keyodi's kernel

my frameworks/av

my frameworks/native

The repo's listed above is what gets everything working; including hardware decoding, and hardware acceleration. SOD is fixed, but we still have an issue with the world crashing once you resume. Wifi will look connected, but you wont have a data connection until you reboot.
[Nook Color Android Development] fattire:
+1, for the reasons Krylon indicated...

There are a lot of repos flying around right now with everyone and their sister cloning. This is a good thing for experimenting and personal exploration and stuff, but tester beware :)

The goal is going to be to consolidate everything. I'm going to start, assuming that slou's wlan driver is good, by moving those changes into my wlan repo and making required changes to BoardConfig.mk... that way, anyone using the build guide will get the wlan fixes without having to change anything..
[Nook Color Android Development] riverzhou:
wifi is fixed.

sync and build again.

---------- Post added at 09:29 PM ---------- Previous post was at 09:10 PM ----------

I know Nook Color has omap3630 and it's cortex-a8 of course, but when I use -mtune cortex-a9 and open krait opitizion for bionic , it's much faster and also stable. You can try and have a test.

Refer to media_codecs, yes, it is set to soft decode.

My plan is make soft decode work first and than port prebuilt decodecs from lenovo a1 to NC. It's need some change on kernel.

My KF devcie base is also deeply clean and re-org , much different from hashcode's .

After clean , reorg and optizmation ,the rom is much faster.

I am testing everything I can now, so I don't think it's a good time to merge my branch to your mainline.

When I get a milestone, I will make a tag and wish you can merge it to your mainline.

ps:

1, I have a new sound driver , it can be built from source code and work very well.You can merge it to your mainline

2, I rewrited init script and then adb can output as soon as kernel boot. You can merge it to your mainline

3, I put a issue on keyodi's git, issue #7, open timestamp for printk. And then we can get time information when we use dmesg.

4, I create a new kernel git and put lenovo a107's 3.0.8 kernel to it. It also has branch of stock omapzoom and keyodi, so we can check difference between them easily.

https://github.com/riverzhou/encore-omap3-3
[Nook Color Android Development] fattire:
Some consolidation... it's a start.

Okay...

So slou's wlan module has now been moved into the "jellybean" branch of my repo and the device has been updated to reflect that change. The old wifi stuff is now in "jellybean-orig" branch.

When you repo sync you will probably get an error if you have the older commits in the jellybean branch. It might look like this (thanks eyeballer):

error: You have local changes to 'mac80211/compat_wl12xx/include/linux/compat_autoconf.h'; cannot switch branches.

Just rm -rf hardware/ti/wlan and repo sync again and all should be good. At that point, you'll be building with the new wifi modules.
[Nook Color Android Development] jschill31:
Hello,

I want to thank you for your efforts. I built with your repo last night and for the first time in 3 weeks I have a CM10 build that does not stay in boot loops. This is incredibly fast but needs some work on the screen sensitivity. I was pleased to see that you added some OC frequencies above 1,000. I realize that everyone wants one single branch to work off of but there is some goodness here. WiFi survives and this kernel seems to have a lot of added features. The only thing I have run into is I am getting errors trying to download from the market. I am sure some house cleaning will clear this up on my end or an older version of Gapps. I am not sure what is all different between the kernels but there is something here to look at. I see that the other user who was having booting issues was able to use this kernel as well but had WiFi issues. USB mass storage mounts and screen capture works as well, bonus! I for one am tickled pink to be able to boot... This is very fast on my Nook but has some stability issues resulting in some soft boots. I appreciate your efforts, please keep your branch open.

Cheers
[Nook Color Android Development] riverzhou:
Thanks for your feedback.

I know there're many works to do and they are on my worklist.

I will keep my branch open and I will try my best to keep the local_manifest.xml builtable and bootable. But I will not talk about it at here anymore except merge request.

At last, I should thank fattire keyodi krylon360 steven676 and all of them for their great works.
[Nook Color Android Development] fattire:
Hey river--

Why not just build your commits on top of the encore repos one feature at a time so that we can evaluate and incorporate your additions? That might be better than one super-patch that has numerous things done to it all at once...?

Also-- if you're on irc, drop by #nookcolor, woncha?
[Nook Color Android Development] riverzhou:
Ok. I will try it later.

What's the best way to do it? Checkout your branch and copy my branch into it? My branch has a different starting point .

I do not use irc now, but I will come here everyday if I have time.
[Nook Color Android Development] bytte:
Can you point to the process you are using to convert your CM10-...zip for booting from your sdcard (I want to create a syslog type facility that logs to a file on the sdcard, without risking messing up the EMMC - which still contains B&N, even though I routinely use CM7 from an sdcard. I guess some day I'll replace the B&N)
[Nook Color Android Development] leapinlar:
You don't have to do anything to the zip to make it work on an SD installation. The install script in the verygreen image does it all for you. But you do need to use my updated image file that has a larger boot partition for the larger CM9 and CM10 zips. Get it in my tips thread linked in my signature.
[Nook Color Android Development] bitstra:
Charging Issue / CM10

Hello,

tonight I've built my first CM10 flashable zip within andbot. All went fine...

... the ROM starts and all apps I've tried are working so far (ex. Camera off couse :)).

But I ran into the following issue:

Charging dosn't work under CM10 (for me).

Is this kernel related or can I look into other causes in source???

Battery status under settings/battery sais loading (usb) while connected to ac. the batt. drains down...

Is this issue confirmed by other testers???

best regards

bitstra
[Nook Color Android Development] lekofraggle:
Bitstra,

I think I have the same issue. Battery stats only updates when not plugged in. Are you using the OEM charger? If so, do you get an orange light on it?

Go into settings and check your battery there. If you have the same issue as me and others, your cable light will be orange, and in battery settings, it will say charging (usb).

The problem is, there are times when cm10 uses more power than usb power gives it effectively draining the battery even if you are charging it.

Many people say the problem is fixed, but it is not for me.

How to check if it is rom or hardware?

Use a different rom (perhaps on an sd card or other partition). If you get ac charging (like I do on alt. partition with stock), it is the rom.

Note, I do not even get ac charging when I shut down after running any cm10 build (since July when I began building).

The possible fix is to force ac charging, but I have been leary of that.

Good luck, congrats on the build.

Leko
[Nook Color Android Development] bitstra:
High Leko,

thanx for your reply.

I'm using all Roms on emmc...; Using a 1000 mA NoName wallcharger...;

Mirage Kang 7.2 - Charges well

ParanoidAndroid 1.6 (ICS) - charges well

my 2 own JB CM10 builts - dont charge.

Now I'm trying several Wallchargers...

1500 mA Wallcharger (universal 5-24 V laptop charger with USB charging port)

- works with Mirage Kang 7.2 and ParanoidAndroid 1.6.

- dosn't work with CM10.

will get tomorrow an 2000mA Wallcharger for testing...

regards

bitstra
[Nook Color Android Development] bitstra:
prevent CM10 to go in sleep mode (screen lock)

Hi all devs and testers for CM10,

while I'm testing my CM10-ROM (built via AndBot), I was frustated about the problems with sleep(screen lock / no data connection after awake and so on)...

So I've installed my old FREE app 'NoSleep', which I have made for a tegra tablet sev. moths ago - with that there were sleep/wifi-probs when we startet with ICS for that.

This app prevents the device going to sleep/screen lock.

It installs itself for a widget only.

Place the widget 'NoSleep' on a homescreen in Launcher.

- orange colored Text 'sleep is off' sets the NoSleep-Mode - Screen will dim after the screenlock period but dosn't switch off.

- toggle with tapping the widget to white colored Text 'sleep is on' means the setted screeclock period is active and screen will switch off after that.

- the state off the widget sticks after reboot / power off/on...

It works fine with CM10 on the nook color here. So I have my CM10-Nook Color switched on for about 6 hours with normal using / without screen lock/sleep.

You can download an test for your self (as a workaround till the sleep-probs are eleminated in our CM10 builds).

Here at PlayStore: https://play.google.com/store/apps/details?id=de.esolutions4you.nosleep&feature=search_result#?t=W251bGwsMSwyLDEsImRlLmVzb2x1dGlvbnM0eW91Lm5vc2xlZXAiXQ..

Hope it can help some of you...

regards

bitstra
[Nook Color Android Development] bytte:
The initial boot / install to SD worked fine. It completed and shutdown (there were a few errors at the end about backuptool scripts in /tmp not found).

On reboot, the CM bootloader flash screen came and went but that what all I got.

I repeated, this time inspecting partition 3 on the SD card before and after the reboot.

Before it just contained lost+found. After it contained the following:

root@win2k3:/mnt3# ls -lRn

drwxrwx--x 2 1000 1000 4096 Aug 26 16:49 app

drwx------ 2 0 0 4096 Aug 26 16:49 app-asec

drwxrwx--x 2 1000 1000 4096 Aug 26 16:49 app-private

drwxrwx--x 2 1000 1000 4096 Aug 26 16:49 dalvik-cache

drwxrwx--x 2 1000 1000 4096 Aug 26 16:49 data

drwxr-x--- 2 0 1007 4096 Aug 26 16:49 dontpanic

drwxrwx--- 2 1019 1019 4096 Aug 26 16:49 drm

drwxrwx--x 3 2000 2000 4096 Aug 26 16:49 local

drwxrwx--x 2 2000 2000 4096 Aug 26 16:49 local/tmp

drwxrwx--- 2 0 0 16384 Aug 26 16:38 lost+found

drwxrwxr-x 2 1023 1023 4096 Aug 26 16:49 media

drwxrwx--t 10 1000 9998 4096 Aug 26 16:49 misc

drwxrwx--- 2 1000 1000 4096 Aug 26 16:49 misc/bluetooth

drwxrwx--- 2 1002 1002 4096 Aug 26 16:49 misc/bluetoothd

drwxrwx--- 2 1014 1014 4096 Aug 26 16:49 misc/dhcp

drwxrwx--x 2 1000 1000 4096 Aug 26 16:49 misc/keychain

drwx------ 2 1017 1017 4096 Aug 26 16:49 misc/keystore

drwx------ 2 1000 1000 4096 Aug 26 16:49 misc/systemkeys

drwxrwx--- 2 1000 1016 4096 Aug 26 16:49 misc/vpn

drwxrwx--- 3 1010 1010 4096 Aug 26 16:49 misc/wifi

drwxrwx--- 2 1010 1010 4096 Aug 26 16:49 misc/wifi/sockets

drwx------ 2 0 0 4096 Aug 26 16:49 property

drwxrwx--- 2 1001 1001 4096 Aug 26 16:49 radio

drwxrwx--x 2 1000 1000 4096 Aug 26 16:49 resource-cache

drwxr-x--- 3 0 2000 4096 Aug 26 16:49 ssh

drwx------ 2 0 0 4096 Aug 26 16:49 ssh/empty

drwx------ 3 1000 1000 4096 Aug 26 18:46 system

-rw------- 1 1000 1000 41196 Aug 26 18:46 system/batterystats.bin

-rw------- 1 1000 1000 41196 Aug 26 18:46 system/batterystats.bin.tmp

-rw------- 1 1000 1000 4096 Aug 26 18:46 system/entropy.dat

drwx------ 2 1000 1000 4096 Aug 26 16:54 system/usagestats

-rw------- 1 1000 1000 0 Aug 26 16:54 system/usagestats/usage-20120826

drwx--x--x 2 1000 1000 4096 Aug 26 16:49 user

lrwxrwxrwx 1 0 0 11 Aug 26 16:49 user/0 -> /data/data/

What I find interesting is that the timestamps under system are in line with when I forced it to poweroff, so threads were running, even though there was no UI. It didn't respond to adb.

Can anyone tell from this what's going on?

Also a question was raised a few posts back about the entries in etc/vold.fstab

Could that have any bearing on the issue?
[Nook Color Android Development] fattire:
Hey Krylon360--

Couldn't find you online but there have been some additions to frameworks_av -- I git rebased locally on my machine, but you might wanna do the same in your repo..
[Nook Color Android Development] krylon360:
heh, yeah, I actually remote merged before I left for work, so it was up todate.

I decided to delete the repo I had, and forked from CM, and cherry-pick the needed commits in and resolved any merge conflics. So it's fully up to date. and should be able to merge right into CM.