yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] sassafras_:
I thought I would be adventurous and build a version with baked in support for the FM radio.

It doesn't work. Force close when trying to initialize the bluetooth. Here is the pertinent logcat and dmesg | tail

Let me know if this provides any insight. I didn't see anything really obvious.

sassafras
[Nook Color Android Development] ADude:
When you say "connected to USB" does that include "connected to the AC charger using the USB cable" ?

Thanks !
[Nook Color Android Development] dalingrin:
I honestly don't know. I can't remember the last time I used the AC charger. I suspect it will be okay on the AC charger.
[Nook Color Android Development] legolee:
Yes, i really hope dalingrin can fix this.
[Nook Color Android Development] Animec:
If it's any comfort, it manages 0.1%/h in battery drain with wifi off :) it's a beautiful thing! And 800 MHz is very usable.

Re. screen, I find it less sensitive near the corners, but can't say for sure. Having a hell of a time pressing the search button in market anyway.

Looking forward to next build, and congrats on fixing the... er... cable of killing.
[Nook Color Android Development] Narfx:
Yeah, that's another thing I forgot to comment. I wasn't able to push the small button that launches the browser in feedr when I was using 2.6.32. It's in the border of the screen. It kept closing the article instead. I'll try with beta 3 when released.
[Nook Color Android Development] madguy2006:
Thanks for the great work Dalingrin!

Feedback:

Positives

1. Battery drain is fixed

2. Runs buttery smooth

Negatives

1. Speaker hum - does the speaker sub system turn off if muted?

2. Screen sensitivity - buttons near the edges are not accessible - I even cleaned the screen with glass solution and tried it again :) - still have issues
[Nook Color Android Development] fattire:
This is the part that failed, as far as Android is concerned.

W/dalvikvm( 2164): No implementation found for native Landroid/hardware/fmradio/FmReceiverJNI;.acquireFdNative (Ljava/lang/String;)I\

I assume you put the appropriate .bts files in place. Did you notice a device node /dev/radio0 ? I think it needs to be created, which may mean more kernel work...

I don't know what is doing this:

I don't think hciattach should be used at all. hciconfig at least for bluetooth loads up the firmware.

This may help too.

Very courageous!
[Nook Color Android Development] Hiro666:
Last night: wiped system, data, cache, dalvik then flashed u-boot 1.2, beta 2, gapps 3/7 (couldn't find the 5/3 version). I must say things just keep getting better and better! I have zero issues to report thus far. The screen off animation is oh so cool. Video with Mobo is flawless. Battery drain is quite noticeably improved.

My hats off to all involved. This is truly admirable work!
[Nook Color Android Development] dalingrin:
The sound SOC behavior is different between 2.6.32 and 2.6.29. The new driver doesn't shutdown as often as the 2.6.29 driver because tests show it actually didn't help with power efficiency. The reason it made such a big difference for CM7 is because it didn't sleep at all. I believe it let the peripheral power domain power off while the screen was off. Long story short, it is working as intended.
[Nook Color Android Development] paleh0rse:
My beta2 build just spent the night on the AC charger without setting it to "Stay Awake," and it woke without issue this morning.
[Nook Color Android Development] abrls:
I flashed 2.6.32 Beta 2 + uBoot 1.2. The battery drain problem is solved. Good job, Dalingrin!

But all my chm reader refused to open chm files (iReader 1.1.1.0 and KingReader 2.4) with the message failed to open chm file.

Anyone on .32 beta2 and uBoot 1.2 has similar problem?
[Nook Color Android Development] bekyndnunwind:
I'm seeing this issue as well...took about 6 tries before the familiar search box and keyboard came up...

I ran it overnight and when I checked it this morning it had been asleep for 9 hours, 26 minutes. Battery percentage had only dropped 1% !!!!!
[Nook Color Android Development] hockeyfamily737:
Not so lucky here. I did the same thing to see what would happen... So far I haven't been able to recover it. Im actually starting to worry a little. Taking a break from it for a bit.

sent from my Ginger-Hero CDMA
[Nook Color Android Development] bekyndnunwind:
You can't hold down the power button to turn the Nook off, then just turn it back on??
[Nook Color Android Development] hockeyfamily737:
NOPE.....can't get adb to connect either.

sent from my Ginger-Hero CDMA
[Nook Color Android Development] hockeyfamily737:
I didn't expect the power button to work, but I figured I could adb reboot.....not so much.

sent from my Ginger-Hero CDMA
[Nook Color Android Development] mr_fosi:
I guess that means it doesn't work when you plug power into it either?

Maybe you'll have to open it and disconnect/reconnect the battery.
[Nook Color Android Development] derekr:
I'm also having screen sensitivity problems in the top right hand corner, particularly with Market search function. (Beta 2 with 1.2 u-boot)
[Nook Color Android Development] hockeyfamily737:
Pressed together case...I looked at the tear down photos already.

sent from my Ginger-Hero CDMA
[Nook Color Android Development] :
Battery is good :P

Went to bed 8 hours ago at 88%, woke up to 88%, then it jumped to 89%!
[Nook Color Android Development] derekr:
@hockeyfamily737 - do you have a bootable SD card?
[Nook Color Android Development] mr_fosi:
You sure?

When I looked at this one, it seemed as though one could take it apart and put it back together without any adverse effects.
[Nook Color Android Development] hockeyfamily737:
Of course.....Planned on trying it....Taking a break from it for a bit though.

sent from my Ginger-Hero CDMA
[Nook Color Android Development] hockeyfamily737:
Not worried about taking it apart....Not sure about putting it back together....That'll be the step right before garbage lol.

sent from my Ginger-Hero CDMA
[Nook Color Android Development] mr_fosi:
Well, good luck in any case. I'll watch for any report you file here.
[Nook Color Android Development] capnblackleg:
Hit an issue or two last night. Beta 2 with 1.2 uboot.

Went to bed with battery sitting at 83, turned the screen off and expected to be blown away in the morning, no such luck, the device wouldn't turn on. Power cycled and it came up without much fuss but the battery now shows 57. Its almost like it didn't sleep like it had been and theres that wake issue.

Is there some fix I missed? I feel like I've read every post since the beta release about 30 times now.
[Nook Color Android Development] :
Eek. Hope things work out. Maybe trying plugging it back in and powering off? If you know how to adb, I assume you've probably tried everything, though... :(
[Nook Color Android Development] :
First off, which bootloader are you using? Are you mistyping 1.2, or do you mean you're using 1.1 from android 2.1 (eclair)? You're driving me nuts!

Also, did you READ the OP and turn on "Stay Awake?"

Even with deep sleep and stay awake, I had to long press the power button for about 4 seconds to see the screen when it is charging. Maybe you got a bit overzealous?
[Nook Color Android Development] hockeyfamily737:
Ehh....No biggie. I knew the risk I was taking and I knew if I didn't do it someone else would :)

sent from my Ginger-Hero CDMA
[Nook Color Android Development] capnblackleg:
My bad, I meant 1.2.

Turned on Stay Awake.

This wasn't while charging, I simply turned the screen off and went to bed. Screen wouldn't turn back on in the morning. I saw the posts regarding a few second press to turn it back on, no joy. Had to power cycle.

Just noticed a post that was similar and the user said it happened once and never again.

As for the battery drain, no idea what happened there.
[Nook Color Android Development] :
Well, maybe beta3/RC1 will make this thing go away...
[Nook Color Android Development] capnblackleg:
I'm certainly not complaining, this is a great step in the right direction.

EDIT - I'll of course test it again today and report if it happens again.
[Nook Color Android Development] CapnBry:
Oh good it isn't just me. Here's what happens (gaps-gb-20110307-signed):

W/dalvikvm( 1353): threadid=1: thread exiting with uncaught exception (group=0x40015560)
E/AndroidRuntime( 1353): FATAL EXCEPTION: main
E/AndroidRuntime( 1353): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.vending/com.android.vending.billing.BuyPageActivity}: java.lang.NullPointerException
E/AndroidRuntime( 1353): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1768)
E/AndroidRuntime( 1353): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1784)
E/AndroidRuntime( 1353): at android.app.ActivityThread.access$1500(ActivityThread.java:123)
E/AndroidRuntime( 1353): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:939)
E/AndroidRuntime( 1353): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1353): at android.os.Looper.loop(Looper.java:130)
E/AndroidRuntime( 1353): at android.app.ActivityThread.main(ActivityThread.java:3835)
E/AndroidRuntime( 1353): at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime( 1353): at java.lang.reflect.Method.invoke(Method.java:507)
E/AndroidRuntime( 1353): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 1353): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 1353): at dalvik.system.NativeStart.main(Native Method)

E/AndroidRuntime( 1353): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 1353): at com.android.vending.billing.BaseBuyPageActivity.isRadioNetworkAvailable(BaseBuyPageActivity.java:371)
E/AndroidRuntime( 1353): at com.android.vending.billing.BaseBuyPageActivity.onCreate(BaseBuyPageActivity.java:281)
E/AndroidRuntime( 1353): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime( 1353): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1722)
E/AndroidRuntime( 1353): ... 11 more
W/ActivityManager( 1065): Force finishing activity com.android.vending/.billing.BuyPageActivity
W/ActivityManager( 1065): Force finishing activity com.android.vending/.AssetInfoActivity
W/ActivityManager( 1065): Activity pause timeout for HistoryRecord{407a7060 com.android.vending/.billing.BuyPageActivity}
[Nook Color Android Development] Teksu:
Charged nook overnight as usual, no problems with the screen not activating, however today i cannot see any wireless networks in range. I have 4 networks saved, 2 of which should be in range her at work, one that is my home network and should be out of range, and the 4th that is my wireless hotspot from my cell that is turned off.

toggle wifi - no effect

reboot nook - no effect

Edit - "forgetting" my hotspot network (the first one i tried) resolved the issue for me, as soon as i did that it picked up the networks here at work and connected instantly
[Nook Color Android Development] :
I've been using the may gapps with no negatives (plus gtalk 1.3 already installed!) http://www.mediafire.com/?pq6ji8c0pl9kcq9
[Nook Color Android Development] :
Did you do a clean install or just toss beta over the top of the previous build you had? If the latter, maybe some parts remained from the old build and wifi module.
[Nook Color Android Development] bekyndnunwind:
Should I wait to update gapps until I do a fresh install, or can I just upgrade gapps at any time?
[Nook Color Android Development] RoboRay:
Negative discharge? Great Scott!
[Nook Color Android Development] paleh0rse:
Its also nice (sorta) to see I'm not alone. Hopefully, Dalingrin can decipher the log and determine what's breaking android.vending.billing...

That said, anyone can test this error without actually purchasing anything -- there would still be one more step after this error to cancel/submit any purchase. The error occurs immediately after clicking on the first price button.

Anyone else willing to test?

NOTE: Once again, this happens with both 3/07 and 5/03 versions of gb gapps. The same error occurred in the latest nightlies as well. (I did a full wipe for beta install).

CapnBry> any chance you're also using the updated or old multi-boot bootloaders? Im just trying to eliminate that as the culprit...
[Nook Color Android Development] :
Well, if you consider your current setup broken w/market not working, what's the harm with trying:P

From what I've read, the only changes are gtalk and a new market. I would maybe just flash over the top. I don't think it will break anything (maybe NAND backup first?).
[Nook Color Android Development] bekyndnunwind:
Cool. My current setup is working just fine, but wanted to try the new market and gtalk...
[Nook Color Android Development] derekr:
You think 88 -> 89% is good. Mine went from 66 -> 97% yesterday on Circle battery widget mid-use, and stayed that way until I reflashed last night. Removing and reinstalling the widget didn't help.

I was thinking that this could be the solution to the world's energy problems... :D
[Nook Color Android Development] Teksu:
with the first test build i wiped system and cache, and left data. when the SD card issue appeared i did a clean install to soo if that would fix it, formated /system /data /cache x3 each through the mounts and storage menu, wiped dalvic and cache using the main menu and advanced menu, did the factory reset option a couple times for good measure.

when i booted up to beta2 i had left "backup my data with google" checked. yesterday i noticed that usb debugging was not working, no icon in notification, no device listed in adb. did another full wipe yesterdaythis time making sure to uncheck the "backup my data to google", still no usb debugging.
[Nook Color Android Development] capnblackleg:
So I attempted to charge the Nook after my sleep/wake issue and after an hour on the charger, it didn't budge past 57 (where it was when I began charging). On a whim, I decided to boot to recovery and wipe the cache, dalv cache, and battery stats (not sure what that does exactly but it felt like an ok thing to do).

Rebooted and now its charged and sleeping fine. Its actually charging faster than I ever remember it on a custom rom.

Perhaps my issue was, I forgot to flash the 1.2 boot after installing the beta. I didn't realize I forgot it until I had used the nook for a while, so maybe I had built up some troublesome cache or something.

I'll let it sleep for a few hours and see if it wakes easily.
[Nook Color Android Development] Divine_Madcat:
mmmmm.. i think i can smell the 1.2Ghz .32 kernel that Dal is cooking up, all the way from over here......*wink wink*
[Nook Color Android Development] hockeyfamily737:
After I got done playing with this all day yesterday I through it on the charger and turned off the stay awake setting to see what would happen and how to fix it, figuring someone would do it by mistake and then panic over it and start 9 new threads. Well, it's now totally unresponsive and will not wake....no magical button combination, no plug in the ac cable, boot from sd, or adb reboot recovery tricks......I'm gonna leave it sit for a while then try again, before I attempt to pry the cover open and take the battery out in a last ditch attempt.....Moral of the story, just don't do it. Double check and make sure you fixed your settings. Good luck all. Peace! :
[Nook Color Android Development] J-ROCK:
Im having the same issue here!
[Nook Color Android Development] GrillMouster:
Try holding the power button for a full minute. If at any point is starts to boot, let go of the button, then turn on "stay awake" again. If nothing happens during that minute then let go of the power button and try it again for a minute.

If none of that works, charge it for an hour and try again.
[Nook Color Android Development] krweby:
Is there a reason live wallpaper is never in the nightly?
[Nook Color Android Development] GabbleRatchet:
Punishment for all our sins
[Nook Color Android Development] Divine_Madcat:
Because fattire touches himself at night.

:D
[Nook Color Android Development] krweby:
Glad I made a flashible live wallpaper zip.
[Nook Color Android Development] bekyndnunwind:
Sharing is caring!
[Nook Color Android Development] GMKcz:
There is very strange behavior of wifi when trying connect to known 802.1x EAP network. Time by time there is searching-connecting-searching loop that can be sloved by deleting network settings and logging in again. It happens every 3-4h of using..
[Nook Color Android Development] :
I never understood the fascination with LWP. Or how flash happy people are to just move two apks into system.

:P
[Nook Color Android Development] :
Care to say what you are actually running and how you installed it?
[Nook Color Android Development] Divine_Madcat:
Well, i don't use the live wallpapers, but i do use the multi wallpaper live wallpaper, to have a different background on each window. So it is fun to have.

Given that its inclusion doesn't break anything, i am curious as to its removal actually..
[Nook Color Android Development] :
Yeah, never got that either. I liked multi for a while, but it seemed to be a battery hog. Or maybe that was before we had audio fixed in the nightlies :P
[Nook Color Android Development] GMKcz:
I wouldn't mentioned if it hadn't been clean install of beta 2 ;)
[Nook Color Android Development] :
Haha, just checking...

You know some people's kids :P

I don't have any specific advice to this build, as I'm on EAP right now and has been flawless. Try the fixes in my sig for wifi, and maybe fix permissions. If it wasn't a clean install from scratch, maybe there is something hanging out in there messing with stuff?
[Nook Color Android Development] ts_mpls:
Am I the only one seeing this?
[Nook Color Android Development] GMKcz:
Will try your fixes and report tomorow..

TY
[Nook Color Android Development] fattire:
Wait- was that you on that creaking ladder by my window last night?!

PS the moaning was your mom.

:eek:

(oh and the actual reason is a certain someone with the initials CS forgets to run the script to copy LW into the build)
[Nook Color Android Development] philburkhardt:
Yup, and 5.1 working isn't new. It's worked for me since the nightlies started.
[Nook Color Android Development] racks11479:
Edit:Disregard post. Question wasn't directed towards me. Sorry.
[Nook Color Android Development] rosenbj:
Thank you, thank you, thank you !!!! This patch finally addresses the Sirius/XM application stuck at the checking for updates. I finally have a working Sirius app under CM7 v4. XDA is also working properly.

Now I can't wait till they address full video support (codecs and DSP) and Pandora support. Looking forward to the future releases of CM7.

Regards,

JR
[Nook Color Android Development] Paul22000:
As I understand, there are quite a lot of developers who worked on CM7.

Who should we donate to / what account (if there is a shared one)? I'd like to contribute to this. Great work! :D
[Nook Color Android Development] dalingrin:
Thanks! As far as I know none of us are taking donations.
[Nook Color Android Development] Decad3nce:
Donate to XDA.

Donate to EFF.
[Nook Color Android Development] faceman66:
You could also donate directly to Cyanogen from their website: http://www.cyanogenmod.com/
[Nook Color Android Development] mckooter:
any chance of the cyanogen wallpaper chooser not hating us tab users?

is there full res images of these walls, i love 1/2 of em but they just render crappy (obviously because the chooser is expecting a res much smaller)
[Nook Color Android Development] tominabox1:
The framework.jar fixed xda (yay!) but my twitter app still FCs when I try to post something
[Nook Color Android Development] racks11479:
Did you try wiping data and clearing cache for the twitter app? That worked on some apps for me after the framework.jar replacement. Just a suggestion.
[Nook Color Android Development] tominabox1:
Didn't help, even uninstalled and reinstalled. Stinks too because twitter app is my fav twitter client now!
[Nook Color Android Development] bonobomidwest:
One today (v4) and one yesterday (v3). The one today was after some random unstable behavior with the touchscreen (which i just happened to notice cos i was using note everything and drawing).

Rebbots were very fast though, perhaps faster than a complete shutdown? Pur rambling conjecture on that though :)
[Nook Color Android Development] digitalslacker:
had two today after installing v4 this morning. Didn't think anything of them but figured I'd mention them in case they are relevant since you two seemed to have issues too.

One occurred after inserting a usb cable, the other was just sitting on my desk not doing anything specific. Not sure if that matters but I hope it helps.
[Nook Color Android Development] antony617:
So is the AndroidID/IMEI fixed or generated randomly on each request?
[Nook Color Android Development] racks11479:
Unfortunately no. It generates a random one on each request. I'm looking to see if there might be a workaround to store it somehow.
[Nook Color Android Development] antony617:
Thanks! Then I'll just stay in NF and wait for your good news :D
[Nook Color Android Development] clockworx:
A workaround can be done. I'm hoping to do it this week, but I'm on the road with the worlds worst net connection in a hotel.
[Nook Color Android Development] j4mm3r:
I just posted this to the other thread... comments? ;-)
[Nook Color Android Development] clockworx:
Sure, give it a shot. Only possible issue I see is that the generated IMEI was based on a real one, and there are rules for what are valid and real IMEI's. That was the biggest part of my time writing it, the code itself only took a minute or two.
[Nook Color Android Development] racks11479:
Would that cause some google apps to error out as well? Since it will retrieve and read a duplicate ID somehow?
[Nook Color Android Development] Divine_Madcat:
Hahah.. why do images of Animal House suddenly spring to mind? :D
[Nook Color Android Development] chisleu:
I just went to unsleep my NC. It wasn't connected to usb or anything at all. It wouldn't turn on without long pressing power to shut it down. SOD? I'm on the 1.2 u-boot w/ beta2.

I was worried there was a reason for a long time. I guess the only reason is someone is forgetful.

You mean to copy and permission? Because it's easier to install it as a flashable zip after installing a ROM, than it is to adb it and change the permissions (even if you use a batch file to do so.)

I like to have LWP installed for when I want to show off (full version of jumpgate is capable of doing some pretty cool stuff.)

Funny, I was thinking of Animal Crackers.
[Nook Color Android Development] xc68000:
Confirming I can't purchase new apps from app store. Causes store to force close. Already purchased apps install ok.
[Nook Color Android Development] :
Ditto for me
[Nook Color Android Development] GabbleRatchet:
No market issues here (beta2 after full wipe) what are you guys running & how did you get there?
[Nook Color Android Development] :
Beta 2 with wipe of system and caches. Also using the updated Multiboot for dual boot based of 1.2 uboot.bin.

Wifi, Bluetooth, video all performing flawlessly.

For market. . . flashed gapps-gb-20110307-signed
[Nook Color Android Development] WobbleTheHutt:
the not being able to purchase new apps is also in all the recent nightlies however 7.0.3 stable works fine so it is not related to this beta kernel. I'm guessing something that is missing from the nightlies but is in the full stable releases is what's causing the problem. its not Google apps.
[Nook Color Android Development] krweby:
It's more then just two apks.
[Nook Color Android Development] krweby:
I've posted it before but here you go.

http://www.megaupload.com/?d=PNTD92BZ
[Nook Color Android Development] krweby:
It's four apks and two lib files. ;)
[Nook Color Android Development] 12paq:
flash 10.3 plays nice with beta 2, so far, more testing needed..