yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] jdpdata:
Or you can try dripping your feet in the water. I'm a noob, but was able to make successful builds using inportb excellent Andbot. Try it....
[Nook Color Android Development] jschill31:
Fattire,

There was absolutely no disrespect in how I phrased my question. There has been zero talk of it since I reported using Wake Lock as a temp solution. Poking at someone who is not trying to help is normal but I sir have been with your project since the beginning.

Cheers
[Nook Color Android Development] fattire:
I'm not poking at anyone, and do appreciate your and everyone's participation. This is all for fun, right?

cheers.
[Nook Color Android Development] krylon360:
wait... fun? I thought I was getting paid for all this....

HAHAHA JK.

Nah, I'm having a blast getting all this to work.
[Nook Color Android Development] disynthetic:
Fat Tire is the best New Belgium hacker.
[Nook Color Android Development] Tiezane:
Believe me, I'm itching to get my feet wet, but when I dive into a project, I like to do PLENTY of research and start from scratch. If you don't struggle before you get to the end, the payoff isn't as much worth it to me. Hell, when I first looked through linux distro's, I skipped Ubuntu, because the install was too easy. Went with Gentoo, when you had to build it from scratch :D

I have to get my PC back up and running, and then I plan to have some fun seeing what I can figure out.
[Nook Color Android Development] biohazrd51:
I don't think he took it being disrespect, but all it takes it one person asking about one feature and next thing you know there are hundreds of "can someone post a flashable zip?" :p

That being said, have you joined IRC. If I recall there was some talk last night of implementing a partial wake lock rather than using a third party application. I'm sure they are looking at it all, but it may not be a huge priority while they are getting everything else working.

Even with my N7 now as my primary device, I'm forced to remind myself of dal's OP.

That being said, JB is smoooooooooooooooooth. :good:
[Nook Color Android Development] jschill31:
Hello,

Sorry for my rant, evidently even at 40 I can be a little sensitive. :p

Cheers

---------- Post added at 07:22 AM ---------- Previous post was at 07:16 AM ----------

Hello,

I have tried to do the IRC thing in the past but always seem to find it too cluttered and unorganized for an old man like me...:p I know Krylon did say the code still existed to do this.

Cheers
[Nook Color Android Development] krylon360:
I also just pushed a patch.. https://github.com/keyodi/ti-omap-encore-kernel3/commit/787cfe992c3bf87a14bd5ba64698f6fb5da8aced does it work... not sure yet. but it was needed to fix a bug.
[Nook Color Android Development] KimCheeZZ:
im a complete noob and im wanting to try this project. can you direct me to where this irc is? how do i get to it? thanks in advance
[Nook Color Android Development] jschill31:
Krylon,

Thank you for this, I will try it tonight. I am terrible at git but am I reading the bug correctly in that it is waking as omap2 instead of omap3?

Cheers

OK, so new build after patch still does not allow for the screen to survive, some kind of wake lock is still needed. One thing that I have been pleased with is using Nova Launcher instead of the stock launcher. The combination of Nova and the phone UI is very nice, no need to force the tablet UI. It kind of has the best of both...
[Nook Color Android Development] biohazrd51:
I don't know what full expectations you had on this, but still experiencing wake issues in the brief time I messed with it last night. Also, I had to adjust all my touches about a half an inch up on the screen to hit the location I wanted. It may have just been my build. I have another one started this morning and will try it again tonight when I get home.
[Nook Color Android Development] krylon360:
I know the issue with SOD. Its wifi. You can turn wifi off and you are able to have the tablet sleep and wake all the time. Need to try the updated drivers later.
[Nook Color Android Development] mrapollinax:
I can also confirm that if you have the wifi on but are not associated with an SSID that the tablet will sleep. I know this because my NC will not associate to my work Wifi (Aruba-based) unless I make the changes to the twlan file for adhoc networks. Since I am lazy and have not done this I see that my NC at work does go into deep sleep with wifi on.
[Nook Color Android Development] newellj79:
After building jb for a 1 1/2 weeks and still not being able to get the touchscreen to work I finally broke down and am trying a build with andbot. :(
[Nook Color Android Development] mateorod:
Just to second this- I have no wifi on my Nook anymore, and I am having none of those issues.
[Nook Color Android Development] fattire:
Some new wifi modules for you.

To this end, I've built some new wifi modules using the latest stable compat-wireless.

Note-- it needed a little fix- this is probably the better fix from steve676, I did it slightly differently. You also need to add these lines to the top of config.mk:

#for encore

export CONFIG_WL12XX_PLATFORM_DATA=y

export CONFIG_WLCORE=y

export CONFIG_WL_TI=y

export CONFIG_WL12XX=m

) The modules are here and are totally untested. Notice that the names of the modules are different now, so you'll probably need to update init.encore.rc if you're building to load these modules.

Here are the changes I made to the device tree-- if someone can confirm it works (my build is hosed right now as I've been working on hardware composer stuff too). If you make these changes and build it won't work actually, because you don't have the source for the new modules.. so maybe comment out the module building for now, and just try the built ones?

Anyway I'm curious if they work. Note the new init.encore.rc, which will be important as well to make sure all the new modules load.

Maybe also i'll stop fooling with hardware composer so i can at least boot and test this.

Note you might be able to load the modules manually and then symlink wl12xx_sdio.ko to point to wlcore_sdio.ko -- that way you may not need to rebuild stuff... but anyway let me know.

Update: it works. I can scan with wpa_cli, which is the command-line way to check if the wifi is working.
[Nook Color Android Development] fattire:
You're welcome.

Okay, I've tested a "make clobber" build of the new wifi stuff and it seems to work. This is a pretty sparkling new module you'll be building, so let me know how it goes with the PM and whatever other issues...

commit #1

commit #2

All you need to do is repo sync and please test. Thanks to sluo too. You're welcome.

ft

(someone remind me or keyodi that the kernel needs CONFIG_NET_SCHED=y at some point.)
[Nook Color Android Development] jromney:
Did a make clobber

I received the following error after the repo sync

error: You have local changes to 'mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/version.h'; cannot switch branches.

error: hardware/ti/wlan/: fat-tire/android_hardware_ti_wlan checkout 207a5a13e433ceda87d2dc721e9fbced5db2a66c

Building now from scratch... It's going take a couple of hours for the build. Will report back.

Thank you all the Devs!
[Nook Color Android Development] fattire:
cd hardware/ti/wlan

git reset --hard

then repo sync again.
[Nook Color Android Development] jromney:
Vielen Dank!
[Nook Color Android Development] unknown_world:
Hi,

My WIFI only works on first boot after that i am unable to switch on WIFI is it a known problem or only me?

I am using the following local_manifest.xml

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

<manifest>

<remote name = "gh"

fetch="git://github.com/" />

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

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

<project name="fat-tire/android_hardware_ti_wlan" path="hardware/ti/wlan" remote="gh" revision="jellybean" />

<project name="fat-tire/android_device_bn_encore" path="device/bn/encore" remote="gh" revision="jellybean" />

<project name="fat-tire/android_hardware_ti_omap3" path="hardware/ti/omap3" remote="gh" revision="jellybean" />

<project name="keyodi/ti-omap-encore-kernel3" path="kernel/bn/encore" remote="gh" revision="encore-omap3-3" />

</manifest>
[Nook Color Android Development] unknown_world:
make -C "hardware/ti/wlan/mac80211/compat_wl12xx" KERNEL_DIR=/home/xxxx/homework/android/system/out/target/product/encore/obj/KERNEL_OBJ KLIB=/home/xxxx/homework/android/system/out/target/product/encore/obj/KERNEL_OBJ KLIB_BUILD=/home/xxxx/homework/android/system/out/target/product/encore/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /home/xxxx/homework/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-"

cat: /home/xxxx/homework/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/.compat_version: No such file or directory

make[1]: Entering directory `/home/xxxx/homework/android/system/hardware/ti/wlan/mac80211/compat_wl12xx'

make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule.

cat: /home/xxxx/homework/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/.compat_base: No such file or directory

cat: /home/xxxx/homework/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/.compat_base_tree: No such file or directory

cat: /home/xxxx/homework/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/.compat_base_tree_version: No such file or directory

cat: /home/xxxx/homework/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/.compat_version: No such file or directory

cat: /home/xxxx/homework/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/.compat_version: No such file or directory

/bin/sh: 1: ./compat/scripts/gen-compat-config.sh: not found

make[1]: *** [/home/xxxx/homework/android/system/hardware/ti/wlan/mac80211/compat_wl12xx/.compat_autoconf_] Error 127

make[1]: Leaving directory `/home/xxxx/homework/android/system/hardware/ti/wlan/mac80211/compat_wl12xx'

make: *** [WIFI_MODULES] Error 2

make: *** Waiting for unfinished jobs....
[Nook Color Android Development] newellj79:
I got the exact same thing. :(
[Nook Color Android Development] fattire:
Sheesh... there were some files missing thanks to a rogue .gitignore file, and apparently those are needed too..

I'll push 'em now.. repo sync in a few seconds. Update: pushed.
[Nook Color Android Development] unknown_world:
Thankyou. But wifi is not working.
[Nook Color Android Development] newellj79:
My build just finished. I will try to confirm if this is the case here too in the next hour or so.
[Nook Color Android Development] krylon360:
wifi seems to be working just fine for me. o.0
[Nook Color Android Development] unknown_world:
On first boot wifi worked for me too but after a restart it's unable to start. It's stuck at "Turning Wifi on"..
[Nook Color Android Development] pringlechip:
I just wanted to say thanks to all the dev support out there. Following all the guides, I was able to build CM10 on my own machine. First time I tried anything like this and was pretty excited when it worked. Thanks.
[Nook Color Android Development] Three-0-3:
wl12xx.ko is not built

Hi,

I got the following error,

mv: cannot stat `hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/wl12xx.ko': No such file or directory

after these successive move commands;

mv hardware/ti/wlan/mac80211/compat_wl12xx/compat/compat.ko out/target/product/encore/system/lib/modules

mv hardware/ti/wlan/mac80211/compat_wl12xx/net/mac80211/mac80211.ko out/target/product/encore/system/lib/modules

mv hardware/ti/wlan/mac80211/compat_wl12xx/net/wireless/cfg80211.ko out/target/product/encore/system/lib/modules

mv hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless/wl12xx/wl12xx.ko out/target/product/encore/system/lib/modules

There are wl12xx.o file in the directory hardware/ti/wlan/mac80211/compat_wl12xx/drivers/net/wireless
[Nook Color Android Development] tomsawyer14:
Wifi appears to persist on reboot for me. Can't install anything from the Play store but that's because I just realized I have the screen density at 120. Duh.

---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------

Have you tried what fattire posted a page ago?

---------- Post added at 11:14 AM ---------- Previous post was at 10:59 AM ----------

Sadly, it appears the wifi change didn't fix the wake lock issue. I'll try to post a logcat if that will be helpful.

---------- Post added at 12:12 PM ---------- Previous post was at 11:14 AM ----------

Wake lock does not appear to be an issue if the Nook is connected to a power source, only if it's on battery. When it can't wake up, wifi does not persist on reboot. I have to wipe cache/dalvik to return wifi.
[Nook Color Android Development] lekofraggle:
That may be because the wifi sleep policy changes when plugged in by default.

~Leko
[Nook Color Android Development] Three-0-3:
Thanks, but, of course I did it...
[Nook Color Android Development] lekofraggle:
So, I have been trying to troubleshoot my power issues. Am I the only one who is not getting ac charging, or is that a function of the build?

I found a potential work around, but if you use it, read all of the reasons cm rejected this commit before you do. You will have to edit thing to make it work for our kernel.

force fastcharge. I think other kernels do this better and I have not used it yet. But it sure is tempting.

If you do implement it know you could short out your computer or an ac adapter. The one that came with your Nook hould be able to handle it. I have blown up an ac adapter by using the cable that came with my nook (shorted out and should force ac) with a palm pre usb. I have friends who have shorted out ports on computers using hacks like this too. So, be careful.

If other people are having this issue, I will continue to hunt for a real solution.

~Leko
[Nook Color Android Development] JP12:
I have exactly the same problem and was wondering if my charger was defect. But since I read this I think it is indeed a kernel related problem.
[Nook Color Android Development] Three-0-3:
fattire's android_device_bn_encore

fattire's android_device_bn_encore solved this. ( I used hazenme's android_device_bn_encore and

still using hasenme's ti-omap-encore-kernel3 )

Turning on the wifi continues and couldn't turning off. The Mac address is changed.

Should I use fattire's ti-omap-encore-kernel3?
[Nook Color Android Development] lekofraggle:
Jp12, I am running an alt. emmc install of stock and get a.c. charging with the same charger and outlet on that. So, I am certain for me at least, that this issue is rom related.

Again, I cannot say this enough. If you try to implement those changes, be careful. You can blow stuff up if you enable fast charging and plug into the wrong device. Also, you will need to disable it for usb transfer and possibly USB debugging.

~Leko

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[Nook Color Android Development] leapinlar:
Can any of the devs confirm that the charging properties is a function of the kernel software for our device and not just some circuitry or code in the Nook itself? I am pretty sure the hardware is what detects what is connected, but not sure about how the charging is controlled since it charges with no rom running and power off.
[Nook Color Android Development] jschill31:
Hello,

I did a make clobber last night and a fresh build. I believe it is the first one since implementation of the new wifi files...and yes I did a git reset. Has anyone pushed new files in the last few days...the build I did last night is the first for me that does not boot. Fresh install and wiped everything, it just boot loops and ends up back in recovery. Maybe something is busted up stream?

Cheers

Sent from my NookColor
[Nook Color Android Development] fattire:
There were some issues this morning upstream that broke the build but they were quickly fixed. I built for grouper (n7) but not encore so m not sure if something new may affect nc but my n7 build went okay.. typing on it now... Any clues from log cat? If it doesnt get to logcat, maybe there's a new issues w the kernel..
[Nook Color Android Development] jschill31:
Hello,

No chance on a logcat. I am going to do a new clean build to see if the problem persists. I will report back but a clean build on my system will not be ready for several hours...probably morning before I can check it.

Cheers
[Nook Color Android Development] krylon360:
nothings been pushed in the past couple of days for the NC last change Keyodi did was for the kernel, but didnt effect bootup.
[Nook Color Android Development] mateorod:
Neither nook nor grouper build would boot earlier, but after a new repo sync grouper has booted for me as well. The clobbered encore build is almost out of the oven, I should know in less than an hour how that went.

Fattire, (or anyone else, really) if you wouldn't mind a little OT, are there more commits than these two involved in splitting the framework.jar? I need to add 250 methods there for aosp and yet I still get errors when booting after applying those patches. It can't find the audiomanager class has been moved to framework2, almost like it isn't recognizing where those methods went.

Patch 1

Patch 2

I have a logcat of the failed boot here.

I ask you because we picked both of these commits from CM10 when they ran into the method ceiling for framework.jar. I guess JBQ is sending people to the first patch as a workaround when they run into the problem. I am hoping it gets worked out in a more permanent way through Google one of these days, but I am currently stuck (have been for a couple weeks, on and off)
[Nook Color Android Development] krylon360:
framework2.jar needs to be added to the bootclass path as well in init.rc located in android/system/core/rootdir/init.rc

should look like this:

export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar
[Nook Color Android Development] jschill31:
Hello,

So after another clean build last night I still have boot-loop city... Same as previous clobbered build, shows boot animation for about a second then reboots. It does this twice before reverting to recovery.

Any ideas?
[Nook Color Android Development] tomsawyer14:
I do appear to be having this charging issue others are describing. Also, I am seeing the Wake Lock issue when the Nook is connected to AC. I was not seeing it when tethered to my laptop. Trickle charge vs full charge, maybe?

Build current as of a few hours ago.
[Nook Color Android Development] fattire:
If you are getting to the boot animation, then at least we know the kernel is loading, which means you should be able to get a logcat or a dB shell and then type "logcat". Is this not possible for some reason?
[Nook Color Android Development] Homer_S_xda:
Thanks but... I re-read those and that didn't work either.

Homer
[Nook Color Android Development] noisufnoc:
weird! mine keeps going back to "Saved" when you try to connect.
[Nook Color Android Development] SpiffyRob:
I'm running it off of an SD, but I just loaded the SD on my PC and deleted NfcGoogle.apk out of /system/app/. That did the trick.

If you're going off of emmc, your best bet is probably to remove it from the ZIP before flashing.
[Nook Color Android Development] rickpref:
Try flashing a different ROM and then reflash ICS and make sure you use a different GAPPS than the one you tried. Seemed to get rid of the NFC problem for a few of us.

http://download.clockworkmod.com/test/gapps-ics-20111125-2.zip

That one worked for me.
[Nook Color Android Development] BaileyJ205:
This worked for me as well. I wiped everything, flashed Kang's 7.2, flashed ICS, flashed 20111125 Gapps and all was well.
[Nook Color Android Development] noisufnoc:
Just for grins I tried the rm /data/misc/dhcp trick that fixed wifi on my tbolt...no go on the nook.
[Nook Color Android Development] ganovim:
where did you get the files to install it to an sd?

Thanks
[Nook Color Android Development] DizzyDen:
Most likely by using verygreen's SASD and renaming the zip file to cm-encore-WHATEVER or update-WHATEVER and gapps-gb-WHATEVER so the SASD recovery installer can install them.
[Nook Color Android Development] RileyGrant:
Wifi works fine?
[Nook Color Android Development] ganovim:
Thanks for the reply. I have verygreen's SASD which I have used many times with the CM7 stuff, but at the risk of sounding like an idiot, where do I get the latest ICS and GAPPS zip files?

Thanks
[Nook Color Android Development] goz5000:
ICS second post of this thread and the apps 5 posts above yours.
[Nook Color Android Development] rampart51:
I now have it running of an 2gb-SD card using Verygreen's installation method.

I used this gaps and flashed it again usings Verygreen's procedure.

http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip

I had a little bit of a problem with the gaps setup wizard timing out (or something) so I manually added a google account (in settings). Then did the touch-the-four-corner trick mentioned above at the gaps setup screen.

When went into market, i was amazed that it worked.

Thanks to you guys for a great first step! This is FUN!
[Nook Color Android Development] Dj-Gutz:
Am I the only one who experience this bug?

Can anyone confirm that charging with original cable is working fine?
[Nook Color Android Development] sednafx:
Same here.
[Nook Color Android Development] rampart51:
I have a WEP encrypted access point in my home.

I connected to it with no problem.
[Nook Color Android Development] capnblackleg:
Anyone know what magic fattire used to get angry birds running? I only get a black screen.

Not a big deal at all, I never even play the game, just curious to see how well it ran.
[Nook Color Android Development] KCs2k:
Well not sure how much this helps. I flashed to the "Destroy of Worlds" build/zip FatTire was kind enough to provide and had my nook plugged in the whole time. I kept it plugged in, and working while messing with it for a couple of hours. Pulled it off the charger and haven't plugged it back into the OEM stuff since.

I did plug it in to a standard USB cable/charger at work this morning and it charged fine. I'll try plugging it in to the OEM B&N stuff tonight when I get home and report back.

Since I'm finally breaking my silence on this thread, I'm usually a lurker, I want to extend a huge thanks to FatTire and dalingrin for all of their work on this.
[Nook Color Android Development] Midnitte:
trying to get gapps to flash, but has any noticed that holding vol- no longer brings you to recovery? cant seem to install clockwork recovery either - just the normal recovery that installs update.zip and then checks and installs gapps.zip :(

Seems pretty stable and beautiful other than that. Great job guys =p, its like a full OS now :3

stupid setup.apk keeps crashing :(, I did manage to add my google account but its just not working, neither is dsp.apk or clock.apk (really? lol..)
[Nook Color Android Development] ganovim:
Having the same problem
[Nook Color Android Development] xdp:
I charged mine last night with the OEM charger and cable and it seemed to work fine. Said "Charging..." right away, and in the morning it was green and when I unplugged it the charging message went away.
[Nook Color Android Development] krylon360:
I did a clean build last night and booted just fine. Its either a grimlen which means you need to do a full wipe or you are using old props. Did you pull from cm9 or cm7?
[Nook Color Android Development] fattire:
A gremlin?
[Nook Color Android Development] tomsawyer14:
Shouldn't have fed it after midnight... ;)
[Nook Color Android Development] krylon360:
Meant to multi quote. :-p