yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] AgentCherryColla:
I lost the logcatt Xo Do you have Netflix? If not, I can spoof a free account for a month ( Just start the free trail, and cancel as soon as the account is made) Using an old Pre-Paid card.

Sent from my ~Ballin'~ Nook Color
[Nook Color Android Development] WJThomas:
Since you don't have experience with using the Nook for GPS, I will try to explain things better. Sorry for any confusion I may have created.

First, the Nook does not have a built in GPS.

Second, there is no problem pairing with the bluetooth GPS receiver, although there may be something missing on the Nook side for the GPS service.

With PA 2.99, in the settings menu under Location Access, there was an option for GPS Source that would let me select my bluetooth GPS receiver as the source for GPS data.

With PA 3.15, there is no option to select the GPS source.

The Apps that I have tried from the market for using bluetooth GPS are not providing a GPS source, they are simply using the mock location feature to jam in the GPS location. My mapping software is expecting to see the MNEA GPS data and not just a location. You are seeing the same behavior with Google Maps (using network location instead of GPS). Since Google Maps was written to use any location source, it works with the wifi based network location, or a bluetooth GPS based mock location; but neither of them will appear as a real GPS location.

I will test the update, but given the partial communication on my end, I do not really expect much. You have surprised me in the past :fingers-crossed:

If the update doesn't work, I will see if I can get a logcat of 2.99 connecting the GPS service. Maybe that will provide some insight on what is happening.
[Nook Color Android Development] AgentCherryColla:
Could the GPS issue be AOSP based? I know exactly what your talking about. I've only seen the soucre option in CM based ROMs. PA 3.15 is AOSP based. BUT I could be wroung.

Sent from my ~Ballin'~ Nook Color
[Nook Color Android Development] WJThomas:
I believe you are correct, but it may be more than that. If I recall correctly, when I tried CM10 and CM10.1, they did not have the option either. CM10.1 on my phone does have the option and lets me select my bluetooth headset as my GPS source.

Mateorod had asked for anything we found missing with the switch from CM to AOSP. He has been so kind to offer to check into this for me, and I appreciate you reminding us that it may be something that the Nook CM team has removed or did not implement.
[Nook Color Android Development] mateorod:
That looks like a casualty of the 4.2 bluetooth API rewrites. I see that feature enabled in the Settings.apk in CM10 and PA but not brought forward to CM10.1 or present in 4.2.2 AOSP. That entire API was significantly restructured and there were some casualties. You know how they have created that green Google prefs app? That is where they were leading with that, they have tried to corral all the Google specific code and place it in a google package and a bunch of the location stuff ended up following under that label.

I will take a look at a straight port of that feature for you, but I have to think that there is a reason that it got axed, either loss of dependent API or built in code that ostensibly handles the operation better, but has not yet been asked to. We will just have to see what it asks of the reworked SDK, the Bluetooth and Location API is far from a strong suit.

edit: In other words, I am pretty sure that i can reenable that check box for you, along with the code that it used to facilitate. But we will just have to wait and see if it does what it used to.
[Nook Color Android Development] mateorod:
External GPS work is going on hold for now...the classes that were written by Coung to create the GPS source setting rely on an API and class structure that doesn't exist in 4.2.2.

Here are the two patches I created to port that feature to 4.2.2-- this is the frameworks_base and here is the settings. This is mostly quick and dirty, there are a couple things I would have done differently during a refactor had the feature built and looked promising...moving the EXTERNAL_GPS_BT_DEVICE to the Global class with a pointer to Settings.Secure first among those changes. (I just didn't want to make clean on my machine each time, the java stuff is pretty fickle about being reused at times.)

Here are the build errors from the port...these are API and inheritance errors, not problems with the actual code of the port, as far as I can tell. The feature-specific classes are just simply not built to run with 4.2.2. Maybe someone else will see something different. I don't think it is hopeless, but we are moving into territory perhaps better handled by someone with a firmer grasp of the overall bluetooth/GPS picture.

My guess is that this type of pairing has become easier for regular AOSP and CM10.1 users and maybe some more investigation into how that mechanism works would be better. If it isn't working on CM10.1, we might just be missing something simple in the device tree. I am not putting it out of mind, but it is moving backwards on the action list, as it is not an AOSPA-specific problem.

Update

With that in mind, I released the update I had waiting for me before I started in on this...I believe that I have correctly enabled the automatic notifications from Goo Manager, let me know if anyone gets a "an update is available"-type notification.

Email.apk added

Torch removed

Update notifications

Switched from AOSP to CM bluetooth

Steven676's kernel additions

Upstream changes

some other stuff I am sure

The bug list on the OP is all still active, I believe.

I have also renamed the packages, since it has always bugged me that the standard PA naming method results in releases being scattered in a servers ordered list...the package names can now be sorted and can be "math"-ed. You may see me rename the very first release so that all the subsequent releases are always at the bottom of the list- DON'T PANIC!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Nook Color Android Development] rtotheichie:
The update notification notification works
[Nook Color Android Development] mateorod:
So...a user named jeff posted this working Netflix hack in the Cm10.1 thread...I have heard that Netflix may not be working in CM10.1 (which would explain why I am having such a hard time tracking this down, if true.)

Anyone who wants Netflix willing to check this out?
[Nook Color Android Development] AgentCherryColla:
I will.

---------- Post added at 11:19 AM ---------- Previous post was at 10:44 AM ----------

It works. I'm using version 1.8.1 of Netflix.

Update. It works fine. I'm using 1.8.1 like I said earlier. It plays just like it does on gingerbread.
[Nook Color Android Development] rabi347:
Whenever I try to download apps from market I get insufficient space error. How can I fix that. I have already tried clearing cache and fixing permission.

Sent from my NookColor
[Nook Color Android Development] AgentCherryColla:
If I'm not mistaken. Wipe Cache/Dalvik. Then try downloading the app. If you get the error again, check cache/download. See if thats empty. The Market checks the cache (which is around 350Mb) to hold the the downloads. If thats empty, clear market data/cache.
[Nook Color Android Development] thejrcrafter2:
Is it possible to activate google now from the pie launcher?
[Nook Color Android Development] mateorod:
Hey, success! Thanks AgentCherryCola.

I believe that hack allows you to use the latest version from the Play Store as well. Netflix is off the bug list!

That leaves the PIE launcher dead spots as my big hole, although I believe that to be an upstream problem I will continue to look at it.
[Nook Color Android Development] graphreak:
The workaroud works very well on latest cm-10.1-20130518-NIGHTLY-encore even with the 2.3.0 Netflix version which is the latest on Play.

One just has to get used to the white background in it.

Workaround worked well for me also on update-pa_encore-3.15-20130514-1322.
[Nook Color Android Development] grayfoxmg1:
I am also reporting success on the workaround using both the latest PA port, and the latest netflix app.
[Nook Color Android Development] benutne:
Why is the touchscreen accuracy so freaking bad in these aftermarket ROMs? I mean horrible to the point I want to throw the device. And before you ask, yes I've installed Nook Screen Recalibrate and used it. Still awful.

I really want to be able to use these ROMs but till the accuracy thing is fixed I'm stuck on a stock rooted Nook Color.
[Nook Color Android Development] mateorod:
send me an email i will give refund.
[Nook Color Android Development] benutne:
LOL.

Seriously though, does anyone else have such a hard time getting accurate touches from their Nook Color? I'd love to use mine more but the screen accuracy just drives me crazy.
[Nook Color Android Development] lorddunlow:
:D This quite possibly the best reply ever.
[Nook Color Android Development] dombeef:
What type of touchscreen do you have?

I think I remember there being problems for the older touchscreen driver, my ft5x06 works just fine.
[Nook Color Android Development] benutne:
I have no idea. How do you tell?
[Nook Color Android Development] dombeef:
http://xdaforums.com/showpost.php?p=41134943&postcount=4

Read under touchscreen type.
[Nook Color Android Development] benutne:
Cool. Thanks. Will post back soon.
[Nook Color Android Development] benutne:
Seems I have the cyttsp controller.
[Nook Color Android Development] grayfoxmg1:
First I would like to make it clear that I am NOT saying you DON'T have a problem, the nook color is a very old device, and the fact that we (as a community) have hobbled it along till this point is bloody fantastic. It's thanks to dedicated people like leapnar, mateorod, eyeballer, and others; that have allowed us to keep this inexpensive and obsolete tablet still living. I, honestly, never expected it to make it to Jelly Bean.

That being said, my Nook Color is also running the cyttsp controller, and I am having zero issues with touch screen accuracy. Perhaps the issue is with your installation, have you tried a complete (cache, dalvik, data, rom) wipe and also a clean install? Perhaps the issue is a hardware problem on your unit, such as failing contacts on the motherboard, or even just a touch screen assembly. Do you keep your nook in a case such as the otterbox case for it? Does it have a screen protector? If it has either, have you tried removing them and cleaning the screen?
[Nook Color Android Development] benutne:
No case, no screen protector (though I did have one once) and I've done all the regular things when installing a ROM (wipe, wipe, wipe). Mine just must be one of those one-off weirdo things. The stock ROM works great when rooted and anything based off the stock ROM works great. Even CM7 is a little funky with the touchscreen.
[Nook Color Android Development] EAK128:
I also heard people having issues with their screen when they were using a different charger than the one that it came with. Just a thought.
[Nook Color Android Development] grayfoxmg1:
and considering that our factory chargers break more often than a professional football team, I could see where that would lead to some issues.
[Nook Color Android Development] AlexanderJohn:
Used gooim to get gapps infinite loop of setup has stopped working. Tried several times to wipe etc etc. same thing. Any help would be great. Thanx
[Nook Color Android Development] Quantumrabbit:
Damn, some really nice progress. This device is running fantastically with this ROM.

\back for a while since my GTab 2 was stolen. Thanks for making it a better experience.
[Nook Color Android Development] weldawadyathink:
Don't use the gooim get latest gapps box, browse through the files and find the latest outside gooim. The gooim ones are broken
[Nook Color Android Development] AlexanderJohn:
This ROM is great. I'm happy to use it.
[Nook Color Android Development] Adriel623:
Help would be much appreciated!

Hi Everyone! First off Thanks to the involved individuals for your dedication towards keeping our Nooks in tip as functional as they can get with these latest updates. You guys are awesome.

Now here's my story. I decided to try rooting my Nook quite a while ago. I wanted to get more out of my Nook, including access to the Play Store, so I decided to root/Noot it and apply a new ROM.

I had great success doing that and got to a point where I was now satisfied with my device. However, in becoming satisfied I no longer kept up-to-date with the latest around Nook rom development so I pretty much forgot all that I had learnt.

But now I'm back and ready to be adventurous again and thus I'd like to put this new AOSPA ROM onto my Nook .I'd greatly appreciate any guidance that you guys can give that can allow me to install this ROM and also be able to retain my current apps installation. Thank you very much!

Here's my current ROM setup as far as I can understand.

Kernel Version: 2.6.32.9 (erik@myhost #151)

Mod Version: CyanogenMod-7.1.0-encore

Build Number: GWK74

Android Version: 2.3.7

The new ROM replaced the default Nook ROM so I guess it's not installed to the SD but the device itself.

If there's any other info you need I'll be sure to provide it!

Thanks again! :)
[Nook Color Android Development] chronokeeper:
I would recommended titanium backup as you will no longer be running gingerbread and data will have to be wiped for compatibility

---------- Post added at 09:32 AM ---------- Previous post was at 09:27 AM ----------

Actually you might wanna also consider mirages 7.2 its stable and you'd be able to keep your data if that's what your worried about
[Nook Color Android Development] Adriel623:
Thanks!

Ahh I see! So with CM9 I'll be running Android ICS, right? If so I think I'll disregard the attention to backing up the apps as most are cloud based and I should be able to recover the data upon reinstalling the apps on the new ROM installation.

With that established, how do you suggest I go about flashing this new ROM? Being out of this game for a while has me rusty on how to go about it.

Thanks!
[Nook Color Android Development] SacTappingUni:
I've had some recent experience with flashing and modding, however I may have never done anything the same way as you, as my Nook Color has never been rooted. Everything runs on the SD card.

The first step would be confirming which custom recovery you use, and from which source of storage (internal or sd card). I assume that you're running some sort of clockworkmod recovery, as that seems to be the most common.

Next download the PA ROM file from the author/OP's link. Load it onto your Nook's memory. Be mindful of which partition/storage unit you save it to. I'm unsure of the specifications for your setup. Make sure it is saved to the root of your partition (i.e. not in a folder) You can also load the gapps folder at this time. My understanding is that the cm10.1 gapps zip should work fine.

Boot into your custom recovery and flash the the ROM. If there is an option to flash the gapps file as well, say yes. If you see tick boxes or any options to wipe the dalvik cache and data, make sure that you they are selected. Everything must be wiped. If you know there will be no option for this during the installation, wipe all your data before you begin to flash the zips.

Hopefully this is understandable. Now get flashing:laugh:
[Nook Color Android Development] SacTappingUni:
On to another subject.

I'm probably gonna get pounced on faster than a quarterback without an offensive line... but what's the ETA for Halo notifications for the NC?

Also, will the Nook Color even be capable of running Halo? Considering how slow it is, I wouldn't be incredibly surprised if it were an impossibility.

/edit: so I searched for halo in this thread and found a couple previous posts that explained the situation a bit. So I guess it's a waiting game until Halo gets out of alpha and the source is released. *sigh*
[Nook Color Android Development] majorpay:
I apologize if this has been asked before, but is there a louder volume hack for this rom?
[Nook Color Android Development] AgentCherryColla:
Volume plus should work.
[Nook Color Android Development] majorpay:
Volume+ didn't have any noticeable effect. It gives a warning anyhow about how it does not work on 4.1+ devices.
[Nook Color Android Development] rtotheichie:
I tried using the dismal search function on the app with no luck, so: is there a trick to getting YouTube to work?
[Nook Color Android Development] AgentCherryColla:
YouTube should work, as long as it ain't in HQ.
[Nook Color Android Development] rtotheichie:
Using the website or the app? Every time I try to use the app, I get a "The video cannot be played" message
[Nook Color Android Development] AgentCherryColla:
The app. I'm not to certain about the browser.
[Nook Color Android Development] leapinlar:
Probably because it is HD. Touch the HD symbol in the corner to change it to HQ. Then it should play.

Sent from my Nook HD+ running CM10 on Hybrid SD
[Nook Color Android Development] mateorod:
Are people using anything for the CM10.1 roms? I looked at the source, and all of the code that allowed things like Nook Tweaks to work has been replaced.
[Nook Color Android Development] AgentCherryColla:
Well I was thinking. Couldn't somebody just apply the tweaks from NTweaks to CM10+ manually? I sure some of it has to be software. I know devices like the Asus Transformer (which has a TI Chip to handle sound [IDK]) have the option for software, and hardware manipulation of the sound. Now we just need to find out what increases the sound. Then try applying it to CM10+

---------- Post added at 12:42 AM ---------- Previous post was at 12:32 AM ----------
[Nook Color Android Development] majorpay:
I know that as of 4.1, Google closed off the API for manipulation, but I figured there may be a way to hard bake it. I played with a few of the configuration files in the ALSA, but no effect.
[Nook Color Android Development] EAK128:
Give "speaker boost" a try, in the play store.
[Nook Color Android Development] mateorod:
I looked at the volume stuff when it was first requested...I did not realize that NookTweaks was open source before this. Nook tweaks uses adjustments to "/sys/class/misc/tlv320dac3100_tweaks" in the rom itself, which comes from the kernel. You can see the audio class here.

Unfortunately, that file is no longer present in the rom, we are using the AIC driver (some configuration files can be found at (among a couple other places) sys/devices/platform/soc-audio/TLV320AIC31xx12S). NookTweaks looks like it could be a candidate to be rewritten, but at that point we are somewhat outside the scope of ROM development, if you ask me. A brief looks at the kernel history tells me this was a carry-over from the move to the 3.x kernel. Those benefits outweigh the loss of NookTweaks but the lower volume is a bummer, no denying it.

These findings are where I stopped, so anyone else is welcome to perhaps look further...I have some other Android obligations that require that time so rewriting NookTweaks or fixing the volume is unlikely to come from me, sorry.

Edit: Well, I forgot to mention that I also looked for similar constants and functions in the AIC driver source (very very briefly looked) and nothing jumped out at me. If it was just a matter of finding equivalent functions in the AIC source, I might have considered it.
[Nook Color Android Development] mateorod:
New build is out on Goo Manager and the download page.

You can see I retitled the first release so that the ROMs are now listed in order of release. I was still getting a hefty amout of downloads of the April release, which there is no reason for. So now they are in order, but the April release has 0 recorded downloads and looks brand new....it isn't. Use the 0531 release.

No change to our existing bug list, but lots of upstream pickups.
[Nook Color Android Development] lorddunlow:
So is there a paranoid android specific version of gasps? I seem to remember someone mentioned it, but I can't find anything other than the 20130301 gapps package. Am I crazy?
[Nook Color Android Development] gullzway:
Same question. I've tried 3 different gapps packages using goomanager, and it locks up the nook with an unending popup about gapps closing. Have to reflash the Rom each time to fix it.
[Nook Color Android Development] bitstra:
i'm using these: http://goo.im/devs/paranoidandroid/roms/gapps

... running fine!
[Nook Color Android Development] gullzway:
Thanks, that one works!
[Nook Color Android Development] gullzway:
Youtube is not working though. Had it working on a signed_Youtube.apk But can't install that over the gapps version.
[Nook Color Android Development] lollyjay:
Just disable halo and install.

Nexus 7 WiFi 32Gb | PA 3.56 27-May-2013 | Nova Prime | Franco-Kernel r61

Nook Color | PA 3.15 14-May-2013 | Nova Prime | Stock Kernel
[Nook Color Android Development] lorddunlow:
Clean install of 0531 build wont let me change toolbar settings. Says "Settings has encountered an error". Happened to anyone else,or should in try to reinstall?
[Nook Color Android Development] bitstra:
+1

same here - Toolbars Setting FCs...
[Nook Color Android Development] gullzway:
Thanks but how do I do that?

I tried moving the working Youtube.apk to system/apps with root explorer but it doesn't show up in my apps after a reboot.

Edit:

This works, Thanks!
[Nook Color Android Development] mateorod:
Thanks for the heads up. I merged some upstream stuff which resulted in merge conflicts all over both frameworks and Settings. That is what delayed the update some, I merged those all by hand. But the problem with hand merging is that human error becomes a factor. I will look at it tonight.
[Nook Color Android Development] WJThomas:
I noticed that the PA Settings will not let you do a backup. Actually, it will do a backup; but it is sent to the null device. This was also not working in the previous version.

If I can get my VM running again, I will look into this.
[Nook Color Android Development] WJThomas:
I got my VM setup and was able to build, but no luck. ParanoidPreferences is prebuilt. I did some searching and came across this:

https://github.com/ParanoidAndroid/android_vendor_pa/commit/e99a9b192386ca186dfe5a52126ce6fbe7da79a5

Looks like they were tying to move the backups from data/data to the sdcard so that they would be preserved with a wipe and reload. Devices with no external sd (and some with external sd) are reporting this same problem. I guess we just wait.
[Nook Color Android Development] Tachyon_1:
I installed this yesterday. First of all, nice work. So far this is the best ROM I've tried on the NC. Considering the device's limited CPU and RAM resources this ROM is very fast.

All previous 4.x ROM's were frustratingly slow and laggy. This by comparison is very usable.

That said, here are the issues I've found so far:

- Tapping "Toolbars" in Settings->Customization causes the settings app to exit.

- YouTube fails to play video

- The kernel doesn't support fstrim (ie you can't run Lagfix). The hardware does support and benefit from Lagfix however and it does run from the CM 10.x ROMs for this device

I haven't tried the reboot to recovery item from the power menu yet so I'll have to take your word for it that it doesn't work.

Thanks again.