yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] douginoz:
After looking into this a bit, its clear that the apps that no longer install on my device are ones that require GPS.

Unfortunately, the industry trend is for apps to want to know your location - not just for direct purposes, but for aggregating data on usage, trends, etc. This data is valuable and is driving app development. Therefore, more and more apps will want and expect GPS.

This isn't the place to be arguing the merits of apps requiring GPS or not, and developers are certainly NOT going to entertain a request to make GPS capability optional.

The good news is that the free app "fakegps" allows my apps to run,. Phew!

Make sure you set your location in fakegps, make it a favorite, and go into Settings to set it to automatically run at startup.
[Nook Color Android Development] douginoz:
I should add that, while 'fakegps' allows my currently installed apps to run, I can't install any new apps that require GPS. They simply don't appear in Google Play at all now.

While I like the idea of having the NC's ROM report its true hardware capabilities from a purist standpoint, this doesn't really work out well for users of the NC if we're now unable to install or re-install apps that require GPS. And more and more apps require this simply because they want to record analytics that can be sold - not because the app actually requires it.

Does anyone know what the most recent version of this ROM is that still has the fake hardware info in it? I'm going to have to roll back and stay on that version until/unless a future version re-incorporates that code. I use too many social apps that "need" GPS on my NC. Without social apps working, my NC becomes pretty much useless.
[Nook Color Android Development] michelbites:
Charging problems

I have a clean install running CM11 with no problems what so ever, except for one. Other then that I am really shocked how well it runs.

The problem I am having is that it charges REALLY REALLY SLOW! No other Rom or Kernel causes this problem. So I am stumped on what it could be. Is there any suggestions. Thanks.
[Nook Color Android Development] hwong96:
The nook color fast charges only with the official BN USB cable with the orange/green LED on the micro end. It has additional pins to allow more current to fast charge. Are you using a generic USB to micro cable? Those only charge the nook color with the screen turned off and get a full charge overnight unlike the official cable.
[Nook Color Android Development] michelbites:
I will give that a try. Thank you.
[Nook Color Android Development] steven676:
Having taken the general lack of complaint as a "no problems reported", I've merged all of this (along with a few more fixes); it should be in nightlies starting April 2 (missed today's build, sorry).

Please try

and let me know whether it solves your app availability problem -- if it doesn't, there's some other problem here.
[Nook Color Android Development] steven676:
Updated bootloader available for test

If you're feeling brave at the moment, I've posted an updated Cyanoboot bootloader in the dev thread for you to test -- I'd appreciate it if you test it out and report any problems. (See the caveats there -- while I don't think it's possible to brick your device this way, this is not your run-of-the-mill test item here.) While this bootloader doesn't bring any immediate benefits, it's a prerequisite for allowing the same unmodified system images to install and run on eMMC and SD cards.
[Nook Color Android Development] douginoz:
Ok, I've installed the latest nightly (April 1 2014), then pushed the xml file and rebooted.

I get mixed results:

- Google Play website now says the apps are compatable with all my devices and allows me to select the NC for installation, BUT when I try to install, and I get an "Unknown Errror" failure

- Google Play on the NC itself still doesn't list those apps when I search for them.

The apps are Grindr and Jackd. Both are social networking apps requiring GPS.

I suspect there are other capabilities they "require" but not sure. Its clearly a step forward though.

The "Jackd" app says it requires:

Your location

..precise location (GPS and network-based)

..approximate location (network-based)

Network communication

..view network connections

..full network access

..receive data from Internet

Phone calls

..read phone status and identity

Storage

..modify or delete the contents of your USB storage

Your accounts

..find accounts on the device

System tools

..test access to protected storage

Affects battery

..control vibration

..prevent device from sleeping

While Grindr requires:

Your location

..precise location (GPS and network-based)

..approximate location (network-based)

Network communication

..full network access

..view network connections

..control Near-Field Communication

Phone calls

..read phone status and identity

Storage

..modify or delete the contents of your USB storage

Your applications information

..retrieve running apps

Camera

..take pictures and videos

System tools

..test access to protected storage
[Nook Color Android Development] steven676:
Huh. Does clearing data for the Play Store help?

Looking over the permissions for Jackd, I don't see anything that suggests it needs other capabilities; Grindr might need the camera (something I'm considerably more reluctant to lie about than GPS, given that devices without camera are quite a bit more common than devices without GPS).

If you have the Android SDK installed, try grabbing the .apk files from your device, and then running ($ is your command prompt, not something you type)

$ aapt dump badging file.apk

on them. This will list all the information the Market uses to filter apps -- see the SDK documentation for details.
[Nook Color Android Development] pastordl:
Installed the bootloader .zip and everything is fine. It is installed in eMMC. Just to make sure this would need to be reinstalled after any ROM update to keep the new bootloader?
[Nook Color Android Development] steven676:
Until it's merged upstream, yes. That said, there's not necessarily a need to do so -- I'm just interested in making sure it boots on a variety of different systems before we merge it.
[Nook Color Android Development] douginoz:
Steven,

Why don't you just try installing Jack'd or Grindr yourself using a recent build? It won't appear in the store for you any more than me. its not like my NC is broken - nobody can install these apps on the current releases of the ROM. At least, thats what I strongly believe. If someone can/could, then clearly its a problem with my device, but I'm pretty sure we all can't.

Its not so much a problem solving exercise here; its more a matter of replicating the problem (as above), then devs deciding if this is worth investigating and resolving.
[Nook Color Android Development] pastordl:
Douginoz have you tried contacting the developers of the apps and demanding that they make changes at their end. The devs who work on CM ROMs volunteer their time and expertise to help us all. They work to make great ROMs for us to enjoy for free. Steven676 has been trying to help you solve your particular problem. Their time is best spent on making CM better, not testing every app that others have made to figure out why the apps don't work. Do what those who are trying to help you ask you to do to help them help you. Make sure to contact the app developers. Please remember the developers are not rented mules for us to beat or abuse.
[Nook Color Android Development] MrPib:
Or, avoid apps that try to sound edgy by omitting vowels in their names ;)
[Nook Color Android Development] bowguy:
There could be another issue at work here. The Play Store does not check (know?) what version of Android you are running. If the app has specified ICS or above the Play Store will lock you out of that app because the official device only shows an OS of Gingerbread. It may have nothing to do with GPS.

The browser I have used for years is now locked out just as you describe. It is also locked out my phone which does have a GPS. The difference is my phone is still on 2.3.4 but the Nook is on Jellybean or KitKat. Surprise (!) the app now crashes on my phone but works great on the Nook.

If this is the case, then again the solution is to contact the developers to explain the issue and get a .apk file independent of Play Store
[Nook Color Android Development] pastordl:
Your assumption is wrong. GPS, etc has nothing to do with Google showing your "social" apps.

Go to this link:

http://xdaforums.com/showpost.php?p=50438787&postcount=3

Download and install Xposed Framework, reboot, then in xposed download Play Store Fixes, install, set fake density to 240 and check the "No Restrictions Patch" box, in system "settings" apps, all, choose Google Play Store, then delete data. Reboot, then enter Google Play Store and you'll find your "social" apps available. I didn't try downloading them, didn't want them. Finally an apology posted to steven676 for the attitude would be appropriate.
[Nook Color Android Development] webyrd:
As previously reported, no problems with test kernel, now 04/03 nightly running fine

No problems with test bootloader, EMMC install

Regarding incompatible apps, several of my regulars are, I have side loaded, all seem to run fine.

edit

I have contacted most of the app dev's, heard back from two so far but no indication yet if they are willing to modify the apps.
[Nook Color Android Development] hliew88:
Thank you so much for this! It worked! Interestingly, however, the apps no longer say they are not compatible, but they still do not show up on the "Installed" tab in My Apps in the Play Store. I'll wait to see if any of the apps automatically update going forward (I have a Nexus 7 to check against, I've been copying over the apk's in the meantime).

EDIT: I'm getting error code 942 when I try to install a supposedly incompatible app.
[Nook Color Android Development] steven676:
This was merged and will be in nightly builds starting April 6. I don't anticipate any problems, but please report any boot failures you come across.

I did -- unfortunately, the Play Store appears to do some sort of caching of the device capabilities, so app installability lags changes to the hardware features by a day or more. That means I can either guess a feature, wait a day or two, and repeat until the app appears -- or you can pull the apps off your device and we can skip the guessing.

At the moment, my guessing based on permission lists for apps reported as missing points to GPS and microphone as the primary culprits. I'm willing to consider reporting those features (if we ever manage to get Bluetooth HSP/HFP headsets working, you can record audio from those; meanwhile, Android no longer requires "fine" location to come from a GPS, so apps can still get a relatively precise location if they'd like), but not on a guess-and-check basis.

In other words: if you have an app that disappeared from the Market after we pruned the list of hardware features we report, grab it off the device, use aapt to get the hardware features the app needs, and post the output.

No, the Market does report and use the API version on the running device.

Disabling Market's app filtering is a neat workaround, but it's just that -- a workaround. I'm willing to lie about hardware capabilities to improve app compatibility, up to a point.
[Nook Color Android Development] steven676:
Test hwcomposer (video playback fix)

If you've been experiencing strange jerky motion during playback of certain videos with CM11, does installing the attached hwcomposer module help? This is the regular CM11 hwcomposer with pending patches http://review.cyanogenmod.org/62238/ (against hardware/ti/omap3) and http://review.cyanogenmod.org/62266/ (against device/bn/encore) applied; together, these disable the use of YUV overlays in the hwcomposer.
[Nook Color Android Development] hwong96:
I applied the patch and don't get jittery video without having to go to developer section to disable hw overlay. I tested with Flixster movie previews.
[Nook Color Android Development] pastordl:
Works great. Smooth video, Crackle, various videos online and on SD in mxplayer. No shakes, jitters or jerks. Thank you. The latest Netflix V3.3.1-B1463 does not work even with work around. Tried both with and without HWcomposer changes no difference. The Netflix app seems to be the problem not CM11. Prior version 3.2.1-B1346 works fine with or without the HWC changes. If anyone updated and needs to revert I have a copy on my Netflix link below.
[Nook Color Android Development] mrfeh:
CM 11 or 10?

HI folks.

Just picked up a used NC on ebay, and want to install CM. I'm running 10.x on another NC.

Would you recommend the latest stable CM 10, or is CM 11 nightly getting pretty stable?

Thanks.
[Nook Color Android Development] pastordl:
My personal recommendation would be CM11, as long as your not needing bluetooth at this time.
[Nook Color Android Development] webyrd:
Working well here also thanks
[Nook Color Android Development] runningslow:
How far back would one have to go to find a build with working bluetooth? I just ran into issues with it as I was trying to stream music from my NC to my laptop. I thought my problem may have been driver related on the laptop, but now I'm wondering if it was the NC.

Was this a recent change or something that has been borked for months?
[Nook Color Android Development] bowguy:
I can't honestly say there is a difference. I have been testing for a few days but any difference is hard to tell. Plus my nook can take about an hour or two after a reboot /reflash to settle down to get a valid test. I also may not be looking at any files with YUV overlays.
[Nook Color Android Development] pastordl:
I know CM11 hasn't since the start. I believe 10.1 did work. Not sure about 10.2. Steven676 mentioned the bluetooth problem on at this link:

http://xdaforums.com/showpost.php?p=51016530&postcount=4089
[Nook Color Android Development] hliew88:
Interestingly enough, Bluetooth has been working great for me so far, although all I have been using it for is a bluetooth speaker and a OBD II dongle for my car. Haven't tested it with other devices, but range/battery consumption/speed all seem same as CM 10.x builds.

The 4/7 & 4/9 nightly didn't seem to remember my Processor and I/O Scheduler settings even though I selected "Set on boot".

4/9 nightly has also been giving me some SOD's and random reboots as well. I can say that the new hwcomposer is helping with the video jitter though.
[Nook Color Android Development] runningslow:
I had never tried using the BT on my NC before until just a couple days ago, even though I've owned this thing for years. I may have to nandroid my CM11 install and try a 10.x (or 7.x) build as an experiment to see how the BT is supposed to act. The issue might just be the computer. I should probably try a few other BT devices, too.

The whole reason this even came up is that I've decided to use my NC as a digital photo frame (using Dayframe) in my office at work. So, while I've had it there, I wanted to try using the BT on my NC with my laptop as a bluetooth speaker, something I've done with my phone in the past. It worked great, unless I was actively doing something on the computer. However, simply moving the mouse vigorously or scrolling a browser window would cause the audio to stutter. That's why I had assumed it must be some sort of driver issue with Win7.
[Nook Color Android Development] leapinlar:
One issue that you new BT users should note is the NC did not originally support BT and does not have a BT antenna. That means if you get BT working with CM the range will be very short (inches not feet).
[Nook Color Android Development] runningslow:
Thanks, I do understand that. In my application, the NC is essentially sitting on top of the laptop. Range should not be an issue. I tried connecting my BT headphones as well and I definitely found the limitations of the range. Plus the music was still somewhat garbled, so there does appear to be an issue with CM11 and BT, even if it's partially working.

Totally off topic: If memory serves, I bought my NC in January 2011 and I've been lurking in this forum since the early stages of NC development. I remember when you devs first managed to get the bluetooth working. I just haven't had a need for it until now, and frankly, I'll survive without it, since I just tried it on whim.

As much as I love my NC and the fact that development has continued for this long, I'm probably going to retire it in the very near future. I think it's time for some more modern hardware for my daily use.
[Nook Color Android Development] hliew88:
I've actually had no success in getting my laptop to communicate with my NC, although they did pair successfully. Then again, I tried only once or twice, and it couldn't communicate with my Nexus 7 either, so I suspect the Bluetooth Peripheral device drivers on my laptop weren't installed correctly. The pairing range appears to be ~3 feet for my laptop, ~6 inches for my Bluetooth speaker, and ~5 feet for my OBD II dongle.
[Nook Color Android Development] volpo222:
Thanks! I was wondering why the range was microscopic.
[Nook Color Android Development] Subtleone:
I need to say it, I am flabbergasted that not only is the Nook Color still getting so much tender loving care after these years, but that KitKat can run on it! I sold my NC (my first tablet) a year ago to a friend (becoming his first tablet), after 2 years of daily usage and upgraded to the Nook HD+. Now I sold that off to that same friend while I upgraded to the LG G Pad (fantastic price/performance BTW), and my old NC is back in my hands, as he chose to give it to a mutual (broke) buddy to be his first tablet. Thus this single NC will become the entry to Android tablets for no fewer than three people. Screen does not have a scratch, and no dings on the body.

Anyhow, as I am the geek of the group, I am prepping it, and though I was using the Kang/Mirage CM 7.2, I decided to peek in here out of curiosity. Needless to say, I just installed CM11 4/14 Nightly, am using many of the tips by Pastordl (duly thanked), to see if it is ok to keep as a base. Great job guys!

Bug: when booting and when turning on to the lockscreen, it is always in landscape, not portrait.
[Nook Color Android Development] hwong96:
The build characteristics of CM11 for nook color is tablet. Take a peek at buid.prop. The line that reads ro.build.characteristics=tablet. CM stopped using phablet mode for CM10 & CM11.
[Nook Color Android Development] Subtleone:
I have always used my tablets more in portrait mode than landscape. Furthermore, CM10/11 on the Nook HD+ and G Pad also gave a lockscreen in portrait.
[Nook Color Android Development] hwong96:
Go to Settings->Display->Rotation. Place check mark in the following items:

Auto Rotate

Rotate Lock Screen

o degrees

90 degrees

270 degrees

See attached pic.
[Nook Color Android Development] fattire:
What gets me is that encore is still in the popular CM device list, with 76,500 active users reporting in. I got mine in Nov 2010 and still have it, running KK. It started w/stock running Eclair I think (Android 2.0.x) Not a bad run.
[Nook Color Android Development] keyodi:
The reason encore is still popular is cuz we have a supportive user community and some very talented developers :)
[Nook Color Android Development] polymath257:
My wife has a NC and I have two. All are still in active use. My wife's still uses stock, but my devices both run CM.

My NC was the first device I put CM on, when I thought my first one was bricked (it did not boot at all---dark screen), I ordered a new one even though it was then considered an 'old device'. I was able to do a hardware fix (replace the battery) and restore the first one. That is why I now have two.

The reason this device is still so popular is obvious: an incredible dev team that encourages the rest of us to learn our devices, learn how to build, learn how to trouble-shoot, and is helpful for those of us that are not devs (still learning, though). The device itself is amazing: being able to boot reliably from the SD card made it easier to modify and learn. It seems to be almost un-brickable (although there is an issue with one version of the SD card install that frequently gives no-boot--see above). But even with these aspects, it would not be nearly as popular as it is if it were not for the devs.

Thanks to everyone that has supported the NC over the years!
[Nook Color Android Development] polymath257:
When I have attempted to build in the last couple of days, whether from stephen's sources or from cyanogenmod sources, the build fails with a message:

Any ideas why there would be a segfault?

-------------------------------------------------------------------------------

Fixed with a

make clean
[Nook Color Android Development] fattire:
The Apple ][ of embedded computers?

I've said this before, but in a lot of ways I think for many (me) the NC fulfills a similar function for mobile devices that the Apple ][ (and Commodore 64s and Amigas, etc.) did 30 years ago for personal computers. It's a great entry machine to introduce you to a "new world"... where kids of any age can play and learn without much chance of doing any kind of damage. Like a scratching post for that itch to safely learn Android.
[Nook Color Android Development] bigbob23:
That's one way to look at it. On the other hand, if the NC didn't have such fine support I might have convinced myself to upgrade to a faster tablet with a larger display. (just kidding) ;)
[Nook Color Android Development] bowguy:
Wait. I thought the devs were arrogant ego maniacs who only wanted money. Did I miss a post or two?
[Nook Color Android Development] polymath257:
Well, I *did* get a Nook HD+. :D
[Nook Color Android Development] hliew88:
Agreed... and I find myself always picking up and using my NC so much more than my powerful laptop or even my Nexus 7. Not to mention that it's so durable (I've dropped it so many times but only the plastic corners have cracked)!

I do want to report though that every nightly starting with 4/12 has been unstable for me. I think there are rumblings elsewhere that the new theme engine is buggy, but I'm experiencing occasional System UI crashes (it seems to be a massive memory leak) as well as constant SOD's and random reboots. The 4/11 nightly is as smooth as butter, so I've reverted back to that for now. The updated hwcomposer is still doing its job!

Thanks devs!
[Nook Color Android Development] pastordl:
Thanks to you, dalingrin and others I got a Nook Color for Father's day in 2011. Your enthusiasm for the Nook then convinced me it was the best way to go. You all were right then and now.

Same here the Nook is my most used device. Also noticed the stability problem. I adjusted the minfree amounts in Rom toolbox tasks, has helped some.
[Nook Color Android Development] Arbelzapf:
Is anyone else having trouble activating xposed? I updated from the 0407 nightly to the latest version, so I have no idea if this problem is new. Xposed will (re) install just fine but won't show as active after a reboot. I tried clearing cache without success
[Nook Color Android Development] pastordl:
If you're not using Xposed 2.5.1 update and you should have no more problems. A change in the trebuchet interface required an update to Xposed. You should be able to update from within the framework or here is a link to get the xposed framework near the bottom of the OP.

http://xdaforums.com/showthread.php?t=2405995
[Nook Color Android Development] hliew88:
So the unthinkable happened... I dropped my NC twice screen face down onto a concrete slab full of rocks and sand. Screen basically became pulverized =/ (pic 1)

So I decided to be janky and super glue on a transparent plastic film I had lying around to act as a screen protector. (pic 2)

The Nook lives on!

In other news, anyone know of a broken NC for parts? Don't wanna spend more than $15 to fix this screen. CM11 runs too well for me to ever give up this thing :crying:
[Nook Color Android Development] kozmo2k4:
Nice fix ^^^^ McGuyver. You should be able to score a screen for cheap on the fleaBay...