Database Users

Changing DPI and new market makes apps incompatibility

Hello.
Im currently using Cognition V1.31, this rom includes the new Market.
What happens when I changed the DPI is that some apps wont install trough market, it says that my device is not supported. (The install button isnt present)
If I delete the new Market, and replace it with the old market everything works again.
Apps that wouldn't install using new market and DPI is, Skype and Lookout
Anyone else that have the same issues?

Yeah, Im having this problem with a lot of apps. I didn't know it was because of the DPI change, i thought it was just the new market that was having these problems?

Set dpi to 240, install apps and then set dpi back to desired custom dpi

For me it happens also with old market app.

Keeping the old market until its fixed.
Sent from my GT-I9100 using XDA Premium App

App incompatibility with custom dpi = Android bug?
I'm on an Evo, but have the same problem. I spoke to the developer of one affected app, (AutoKiller,) and to the best of their knowledge the incompatibility issue is not related to their code.
The problem is also evident at market.android.com, which identifies many apps as incompatible as of late, when using custom dpi scaling.
After picking through the manifest files of a handful of apps, I've found no relation between the apps that exhibit this problem, or even anything that sets them apart from apps that will still install normally. AutoKiller even specifies in the manifest that any density screen should be supported. Additionally, there is no apparent connection to the target and required SDK versions.
I'm about ready to call this an Android bug, maybe a Market bug, even. The Android Dev Guide page on "Supporting Multiple Screens" implies that valid ranges for an hdpi display are between 200 and 279. I tested this range on my Evo and found that not a single framework resource breaks within it. Immediately outside this range - i.e. 199 or 280 - certain screen elements fail to display properly.
Honestly, it's getting annoying really fast. If I have some more time to look into it later, I may file a bug at Google Code. At the very least, the cause of this "incompatibility" nonsense should be documented in the Android Dev Guide, so that it can be anticipated, understood, and avoided when appropriate.
(I can't post links yet, so find the "Supporting Multiple Screens" document @ developer.android.com/guide/practices/screens_support.html if interested.)

Im running on an Xperia Play with a DPI of 200 (Default: 240) and cant download essential apps that have said bug (Ex. Facebook). Hopefully we find a solution.

I thought I was the only one with this problem. I just recently started using Gingermod asop rom and everything was working perfect until I changed DPI and tried to update some apps.

doesnt do anything with the dpi but.
http://amip.tools-for.net/wiki/android/marketaccess

It's not a bug, it's a feature. The market checks your device resolution against what the dev reported to work. If it's too high the app might not work at all or draw incorrectly. Some apps have HD versions which work with higher DPI's check those out.

GIR said:
It's not a bug, it's a feature. The market checks your device resolution against what the dev reported to work. If it's too high the app might not work at all or draw incorrectly. Some apps have HD versions which work with higher DPI's check those out.
Click to expand...
Click to collapse
Devs I have spoken to report that they have NOT intended for this to happen. Additionally, I have yet to find a single APK which suffers from this problem and has DPI constraints defined within its AndroidManifest.xml.
I have ripped apart over half a dozen apps trying to find the cause of this, and as a matter of fact, the first one I opened up explicitly specifies compatibility with ANY screen density.
Feature? That's not what it's called when even the devs don't have control over it.
(For clarity, an optional declaration in an application's AndroidManifest.xml is what determines screen density constraints, if any. By default, applications willingly install and run on any screen density for which they have fitting resources. From the dev's standpoint, these densities are not measured in exact pixels, but instead in named ranges (ldpi, mdpi, hdpi, and xhdpi.) When outfitted with resources that match the screen density range, the system scales resources at runtime to meet its exact needs. For more information about how Android handles screen density, please review the article I referenced before.)

You guys are on the right track.
Custom dpi (lcd density) seems to cause the "incompatible" problem with the new market.
http://forum.xda-developers.com/showthread.php?t=1196417
Going back to 240 dpi and clearing market data makes everything work as it should.
You can then go back to your custom dpi, but most users are reporting the problem comes back after a while.

Thanks for the heads-up - I had no idea it would have been from the DPI setting.

It would be great if there were a way to spoof density, so the market always identifies at 240dpi, (or appropriate.) Switching and rebooting all the time sucks. Anyone with some smali skills want to try hard-coding it into the new Market.apk? I will be trying, but I've had zero luck with APK modding thus far
Sent from gingerbread-evo-deck

Google is apparently aware of the problem and considering what to do about it. Post: "Anyone with different LCD density and Market issue, look here"
In the meantime, I have found that doing a soft-reversion to 240 with LCDDensity For Root when I want to run updates is not too much hassle.

thanks bazofia
bazofia said:
Set dpi to 240, install apps and then set dpi back to desired custom dpi
Click to expand...
Click to collapse
Thanks man!

Check out this thread, worked for me:
http://forum.xda-developers.com/showthread.php?t=1839871
Just download one of the attached files and flash in CWM.
Sent from my GT-I9100

Anyone with different LCD density and Market issue, look here

I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.

They dont't need to support non standard dpi but they should let applications to show up in Market. This is the reason I downgraded the Market version on my phone, but this is not a solution. I hope Google will let the users decide what dpi is best for them.

Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!

blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Seen a couple of these pop up so far. The problem has been affecting me for a while now, but I just figured out what caused it last week. Lots of people (myself included) seem to have thought nobody else had this problem.
Post: Changing DPI and new market makes apps incompatibility
Post: [Q] Cannot update multiple installed apps, is it the new market?
blackspp said:
Yep but as long as they fear claims and complaints nothing may happen...
At the same time the 2 persons I've been dealing with have been very cooperative and asked me lots of questions. Gave them app details, logs and after a few weeks they came back with this conclusion.
Which sort of makes respect them, after all, I'm only one of nearly 200 million Android users!
Click to expand...
Click to collapse
I'm almost surprised it took so long for them to notice that trend, considering they surely have facilities to notice trends in their databases. Score one for XDA! (Very cool of Google to provide such tailored support, though!)

So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...

schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
To "permanently" change your DPI to "XYZ", add these lines to /data/local.prop:
Code:
ro.sf.lcd_density=XYZ
qemu.sf.lcd_density=XYZ
(Note: If /data/local.prop does not exist, you may create it yourself.)
- OR -
If you would prefer that the change not persist when flashing a new ROM, you could edit /system/build.prop, which should already contain the "ro.sf.lcd_density" property unless you're on a 160dpi device. /system/build.prop will be overwritten any time you flash a new ROM, even if you do not wipe first.
Both of these methods will require a reboot for changes to take effect.
---
Alternately, if you would like to avoid editing system files by hand, there is an app called Blade Buddy which allows you to modify various properties in /data/local.prop, including LCD density.
To save your changes from Blade Buddy, tap Menu -> Save. If you choose not to reboot, you can then tap Menu -> Apply to apply the changes in RAM and restart the UI to see them in action. (Applying density without rebooting seems to be hit-or-miss.)
---
Regardless of how you set your LCD density, the Market will exhibit the incompatibility bug.
As a workaround, I have set my density "permanently" with Blade Buddy and use LCDDensity for Root to revert to default once and a while, so I can launch the Market and get all my updates. LCDDensity for Root is designed specifically to change density temporarily, on-the-fly, and on as many devices as possible.

Thanks, Mr. Bezeek. Actually what I'm looking is the permanent solution of not having to temporarily switch back and forth. As for editing .props I already have experience before with my Streak. Hehehehe
But still, thanks anyway and hope you not offended. I like it the way you help others in precise and detailed manner. Keep it up, bro *thumbs_up*

Not a problem, just doing my bit to make sure the information is out there.
As far as avoiding the temporary switching goes, I'll be on vacation for the next week, but I intend to try a little hacking when I get back, to see if I can find a way to spoof the dpi. That is, if Google doesn't throw us a bone in the meantime.
Users have reported that older versions of the Market still work. The one shipped with the latest OTA for my Evo worked for me, and I suspect that any version released before they changed the Market UI will. YMMV.

Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.

tslovejoy1969 said:
Just thought I'd toss this out there... I have a Droid X. When running MIUI 1.8.19 on it, I don't have this problem. I can set my density to 200 and the newest market (3.1.3) still works as expected. Seems as though with all the other ROMs I've tried (both blur and 2nd init), I couldn't access a lot of stuff unless I set density back to 240. I can't remember for sure, but I might have been able to set stock .602 (rooted) to 200 with no problems as well - but I'm a little iffy on that. So it would seem that MIUI has done something (perhaps not intentionally) to work around the problem. I just wish I had the smarts to figure out what that might be.
Edit: I realize that this is not a Droid X forum, but I was thinking this info might help somehow. Thanks.
Click to expand...
Click to collapse
Good to know! Being able to compare a "working" ROM to mine will surely make it easier to identify a workaround.

Nice info never noted this before!! yeah i dint get any updates over a last few weeks. Im at 200 dpi.

I've been switching back to 240 periodically to get updates, not a big deal to me, but would be nice if things worked normally. My only real issue with running lower dpi (160 here) is that some apps don't scale properly. IE the Dialer.

blackspp said:
I've been in touch with Google the past few weeks cause I hardly get any updates through the market since about three months.
Google noticed that everybody or at least most users with a non-standard screen density have this issue. Many apps give a 'your device is not compatible with this application' error when browsing the internet/desktop market version (not the phone market app).
And than in the market you won't see your apps under 'My Apps'
When you switch back to 'default density (240) the problem is gone.
Google is investigating the issue but does not know yet if they will support non-standard densities.
If this is a double post, sorry for that.
Click to expand...
Click to collapse
Thank for this information! I've been wondering why some standard apps weren't compatible.. It's weird, since they work if you side load them ...
I hope google finds a solution.
---------- Post added at 02:59 PM ---------- Previous post was at 02:51 PM ----------
I just switched from 190dpi to 160. Angry birds seasons is now compatible( wasn't with 190dpi)
Dank U vriendelijk

Wow. This has been driving me crazy trying to work out why apps where missing. Guess I need to swap to 240 occasionally for updates.

I am using 200 / 192 DPIs from day one. (3 months). its working fine.I never faced incompatibility issue with market. however some games doesn't run correctly which usually i don't play.

i have a workaround idea, and i started a thread to discuss here: http://forum.xda-developers.com/showthread.php?t=1288150

The google support thread for this is here: http://code.google.com/p/android/issues/detail?id=19744#makechanges
I still have this issue and if you do a web search you'll see that many still do. Reply in the support thread to raise awareness ! or if you have a workaround please share You also might want to check out his Idea thread, if you have some developing skill please help.

schizo said:
So, no "permanent" dpi change solution for now?
I kinda missed my streak because of this high DPI on the SGS2. Everything getting so big, i losed some of my productivity...
Click to expand...
Click to collapse
I came from a streak as well and it's this is the biggest annoyance I've had with the sgsii.
The reason why i enjoy Android over any other mobile OS is because i can tailor the OS to how i want it. Not allowing me to download apps because I'm using a non standard density is crippling.
For now, i urge everyone to go to the google support thread and simply press click the star. No need to comment (unless you found a fix), the more stars the issue gets, the more likely Google will look into it.

Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App

Ke11ett said:
Seems to be fixed with the latest market version.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
yeah i seem to be ok ive just got the version from androidpolice last night. im on 3.3.11 now, still cant install stuff from the website though says my phone is incompatible for everything lol

[Q] Invisible Text in ManualNootered Nook Color

Device Info:
Nook Color running B&N 1.2 (Android 2.2.1)
ManualNooter 4-6-16
OC at up to 1.2GHz using Froyo 1.2 dalingrin OC emmc 090111
Problem: Text in some apps cannot be seen (ie Titanium Backup "Filters" screen).
Observations: This problem seems to happen with B&N Software Versions ABOVE 1.2 (I am currently running 1.2 because of this issue).
Search Results: I've only found mention of this problem (or something close to it) in two places: HERE and HERE.
Recommended Fix or Workaround: NONE
I just inherited a Nook Color about three weeks ago, it was reset to factory defaults (B&N 1.1). The person I got it from was running B&N Software version 1.2 with the latest recommended ManualNootered version (manualnooter-4-6-16) at that time. He could not get B&N Version 1.3 to work right. When I got the Nook, the first thing I did was to update it to B&N 1.3 and root it with the latest ManualNooter procedures, which worked great (the procedures had been updated since the person I got it from had tried to root B&N 1.3). Thanks GabrialDestruir!
One of the first apps I purchased was Titanium Backup. I noticed in Titanium's Filters screen there were Radio Buttons that had no text next to them. I was brand new to Android and had a lot to learn, so I made note of this issue to return to later. When I finally got around to addressing this issue, I discovered others had the same problem, but so far it was not addressed within the development community.
In my experimenting I have crashed and re-rooted the device many times, so I know the problem is consistent. I was becoming frustrated and asked the previous owner if he had the same issue with B&N 1.2. He did not. As of this morning, I have returned to B&N Software Version 1.2 and I can now see all the text that was invisible before - in every app I've tested and remembered had the issue.
The specifications above are the only changes needed to reproduce the problem. As soon as I was up and running, I downloaded Titanium Backup from Market. When I rooted the Nook using B&N Software version 1.2, all text was visible. Following the procedures to get the system up to the same place with B&N 1.3, the text problem reappears (text disappears).
Any help with this problem would be greatly appreciated. If you have any questions for me or if I have forgotten a critical piece of information, please do not hesitate to post what you need here, I will be checking it daily.
Thank you for your time, effort, and help XDA! You've made a complicated procedure very simple.

I am experiencing the same problems with dialog boxes in many apps and widgets. I too have tried to find a solution.
Sent from my BNRV200 using Tapatalk

milliman said:
I am experiencing the same problems with dialog boxes in many apps and widgets. I too have tried to find a solution.
Sent from my BNRV200 using Tapatalk
Click to expand...
Click to collapse
Changing the dpi in build.prop to 160 helps, but does not cure the problem.

framitz said:
Changing the dpi in build.prop to 160 helps, but does not cure the problem.
Click to expand...
Click to collapse
Can I do that with LCD resolution?

This has always been a problem with the stock ROM, IIRC it's because typical Android text is Black and it's White on the stock ROM, therefore by default it's White on White in some apps.
If you don't need the Read to Me kids books or Magazines, use CM7 and the Nook market app, it doesn't have this problem and does much more.

khaytsus said:
This has always been a problem with the stock ROM, IIRC it's because typical Android text is Black and it's White on the stock ROM, therefore by default it's White on White in some apps.
If you don't need the Read to Me kids books or Magazines, use CM7 and the Nook market app, it doesn't have this problem and does much more.
Click to expand...
Click to collapse
Yea, so far, that's what I figured - the Nook is using a white background and if a program does not explicitly define the background and foreground text colors, but assumes the background is black, this is when the problem occurs.
I guess what I was wondering is if there is a way to change the default background color for the Nooks to black, and the default foreground text color to white. I read somewhere about "theme-ing," though, like I said, I am new to Android, could theme-ing be a solution?
I don't get your second statement. I already use CM7 (but only so far as for booting to use ManualNooter), and I have no idea what "Nook market app" you are referring to, or the Kid Reading stuff - do you meant the stock B&N stuff?. Am I missing a key concept here?
Or, possibly, are you suggesting I use CM7 to install a different ROM and skip the Nooter method altogether? I was actually beginning to research this - I can do without all the B&N stuff, it doesn't work right anyway and I have disabled much of the B&N apps. If flashing a different ROM fixes this and "does much more," I'm all for it. It will just take me doing a little more research and someone confirming this is what you are referring to.

khaytsus said:
This has always been a problem with the stock ROM, IIRC it's because typical Android text is Black and it's White on the stock ROM, therefore by default it's White on White in some apps.
If you don't need the Read to Me kids books or Magazines, use CM7 and the Nook market app, it doesn't have this problem and does much more.
Click to expand...
Click to collapse
I see! I will have to see if I can dig into the nook a little deeper and see if I can do anything about that. It is annoying but I'm not annoyed enough to change to CM7 yet! Plus I have a People subscription that I am enjoying ATM.
Trasd..You are using CWM to boot to manual nooter. CM7 is something else.

Anemailname said:
Trasd..You are using CWM to boot to manual nooter. CM7 is something else.
Click to expand...
Click to collapse
Ah, thank you, I was wondering how some people were runnig higher versions of Android - now I know.
Is it weird I love this stuff?
Well, as they say, back to the drawing board....

EDITED
The theory below is NOT the problem, but I left it up because I cannot delete it and is serves as reminder. Sorry.
ORIGINAL
I have made a discovery; the problem seems to happen, not because of background color assumptions, but when styles are used (an app developer, who was kind enough to debug and redesign his app for me, discovered this).
I am almost to the point in my self-education with Android and Java programming that I can verify this myself, but I am not quite there yet. If someone does verify this, could you please post your findings here?
As you can tell, I haven't flashed the ROM yet, and may not for awhile. It's running OK and I really want to concentrate on programming for the time being.
As more and more developers use styles though, I may not have a choice.

[Q] Manualnooter 5.02.19 audio bug. (involves "read to me" books)

Hey all. As is evidenced by my name, I typically just lurk and learn rather than add to the confusion. But now I am stumped. Being a person that doesn't post much, I can't put this in the Dev section so I hope someone much more intelligent than I gets wind of this post.
I have recently found a previously unnoticed bug with my Manualnootered NC. I am on a first gen Nook Color running manualnooter 5.02.19 over stock 1.42. I also have the Dalingrin OC Kernel (1.2 Ghz). I'm running GoLauncherEX with homecatcher over the stock launcher. Nothing outlandish or special installed. (Dolphin,netflix,Titanium, CWM, etc...)
When I attempt to use the "read to me" function of the childrens books, the audio cuts out before each sentence is finished.
Example: Text would read "Jack climbed up to the top of the beanstalk"...... But the audio that plays would be "Jack climbed up to......".
With one particular book, "The astonishing secret of awesome man", it was cutting off the audio of the reading part but would still play a trumpet sound effect and perform the animation that was part of the story.
It happens on new downloads as well as old purchases. I have tried archiving and re-downloading, re-rooting, and factory reset..... I even spent nearly an hour on live chat with a tech support rep who only succeeded in talking me into wiping my device by assuring me that it would fix the problem. It did not.
Eventually I restored to 1.0.1 and ran the whole gamut of updates back to 1.42 just to make sure I had a clean install.
No luck, although at one point I was also getting the blank "red screen" before I managed to get it re-rooted again.
So now I am wondering if anyone else has noticed this problem. It isn't an issue for me (since I can read to my self, thank you ) but it would be nice to allow my kids to use their read to me books again.
Any ideas? If anyone needs a better idea of the problem I can make a youtube video and post a link to better illustrate the issue.

Does the problem only occur after you root or even when you are restored to plain stock 1.4.2? Sounds like it might be a B&N issue though they weren't able to help you. If it just occurs after rooting an easy solution would be to run a bootable SD card with CM7 or CM9 and leave stock unrooted so you could have the feature.
Then you have all the features of a full tablet from the SD card and can always boot back to stock for the read to me feature.
JP

I had considered that but it gave me the "red screen" on stock. Not sure if maybe there was some remnant from my previous root that may have bern causing this or not. All I am sure of is that before 1.42 they worked. I wonder if anyone else had the "red screen" on stock like I did. I saw one other post about it but I think they were rooted.
Sent from my BNRV200 using Tapatalk 2

I would set clock speed to 800 mHz and see if that fixes it. Overclocking it may cause the read to me app to process the video on them too fast for the speech to fully read the sentence.

That is what I had thought. I did set the clock speed to 800Mhz with no luck. I wonder if I should just reflash the stock kernel and try that...
Sent from my DROID X2 using Tapatalk 2

I will be looking into this issue over the next couple day and getting back with you. I have a couple ideas on what might be causing the issue, but no hard evidence at this time.

Thanks so much! I know you probably have other pressing issues but I (and everyone else who enjoys the use of their rooted Nook) appreciate your time and effort. If you need any specific info from me just let me know.
Sent from my DROID X2 using Tapatalk 2

TheDroidLurker said:
Hey all. As is evidenced by my name, I typically just lurk and learn rather than add to the confusion. But now I am stumped. Being a person that doesn't post much, I can't put this in the Dev section so I hope someone much more intelligent than I gets wind of this post.
I have recently found a previously unnoticed bug with my Manualnootered NC. I am on a first gen Nook Color running manualnooter 5.02.19 over stock 1.42. I also have the Dalingrin OC Kernel (1.2 Ghz). I'm running GoLauncherEX with homecatcher over the stock launcher. Nothing outlandish or special installed. (Dolphin,netflix,Titanium, CWM, etc...)
When I attempt to use the "read to me" function of the childrens books, the audio cuts out before each sentence is finished.
Example: Text would read "Jack climbed up to the top of the beanstalk"...... But the audio that plays would be "Jack climbed up to......".
With one particular book, "The astonishing secret of awesome man", it was cutting off the audio of the reading part but would still play a trumpet sound effect and perform the animation that was part of the story.
It happens on new downloads as well as old purchases. I have tried archiving and re-downloading, re-rooting, and factory reset..... I even spent nearly an hour on live chat with a tech support rep who only succeeded in talking me into wiping my device by assuring me that it would fix the problem. It did not.
Eventually I restored to 1.0.1 and ran the whole gamut of updates back to 1.42 just to make sure I had a clean install.
No luck, although at one point I was also getting the blank "red screen" before I managed to get it re-rooted again.
So now I am wondering if anyone else has noticed this problem. It isn't an issue for me (since I can read to my self, thank you ) but it would be nice to allow my kids to use their read to me books again.
Any ideas? If anyone needs a better idea of the problem I can make a youtube video and post a link to better illustrate the issue.
Click to expand...
Click to collapse
Could you download this file, and flash it with CWM, LINK. The problem that you are having is caused by a bug in the current release of Adobe Air. Once you have flashed this file, you will need to go into the Google Play Store and turn off auto updates for Adobe Air. DO NOT update Adobe Air.
What this file will do, it will delete your current Adobe Flash and Air from the data partition, install the most up to date Adobe Flash, and last working Adobe Air into the system partition. By installing the files into the system partition, you will always be able to go into manage applications, and uninstall any updates back to these working versions. When Adobe Air is updated in the future, you can update it to see if it works, and if it don't just uninstall back to this version.
As for the "red screen" that you came across, this will happen when Adobe Flash is uninstalled from the device.
Please report back to this post if it works, or does not work, so that I can update the whole MN 5 package for everyone else to enjoy. I only have a few read to me books to personally test this on, and not all of them had this problem, so I really need the feedback from you.

That did the trick! Thanks for sorting that out. Now my four year old can get his boogery little fingers all over my Nook again!
Once again, thanks.
Adam.
Sent from my BNRV200 using Tapatalk 2

TheDroidLurker said:
That did the trick! Thanks for sorting that out. Now my four year old can get his boogery little fingers all over my Nook again!
Once again, thanks.
Adam.
Sent from my BNRV200 using Tapatalk 2
Click to expand...
Click to collapse
Don't forget to use the "Thanks" button when a post helps you out Go on its right down there vvvv
Edit: I see you might not be able to if you are using the forum app to post at the moment.

New Nook HD+ owner here!

Hi all, Just got a Nook HD+ on sale. I know it isn't the newest, shiniest piece of gadgetry and I don't really care. So far I'm digging it, I really like the different aesthetic. (Who puts a hole in the corner of their tablets?!.. really?) and aside from rooting it, which I try to do to every android device I get right off the bat. What else is there?
I see there are a few 10.1/2/3 ROM's out there but what are the actual benefits compared to just using the stock ROM? Also, is there any custom kernels floating around? I'm always a fan of messing with kernel stuff like undervolting/overclocking/governor tweaks/etc.

I think your answers are in each rom development thread. But I'd say cm 10.2 (I didn't try cm 10.1) is much more responsive than stock. I didn't find any kernel out there besides those inside the roms.

I suggest getting the most recent RC3 release of CM 10.1 and in performance settings, set transparency to 16bit and purge assets.
That seems to be the best overall combo.
10.2 has no apparent benefit for the HD+ as far as performance. The trim function has been disabled since not Nook flash friendly for a lot of units and OpenGL 3 is not supported by the chipset in the HD+.

Hmm, OK, ok...
I could have sworn I saw a post here talking about using 10.3 but lurking through the dev thread I don't see it anywhere. I'll keep looking.
Are the nook apps usable on CM roms? I know the launcher won't be but is it possible to use just the reader, library, etc? Thanks for the response guys! Also, anyone familiar with using CM on the Nook, do Hulu, Vudu, Netflix all work also the HDMI-out and bluetooth? These are all things I use and can't lose.
UPDATE: Oh, my bad, the post says "10 1.3" which is a little confusing and I saw it as 10.3
http://forum.xda-developers.com/showthread.php?t=2459574

Im new to Tablets (only have a Nook HD+ for acouple weeks ) but not flashing.
Just installed CM 10.1.3 (last night)
One thing which i was after (and the main reason for me) was USB thumbdrive support/storage (link about it) and that worked great.
After, i did install the B&N "store" app (the green 'n' app) and it installed fine (had to install it via .apk found out side of the Google Play (dont know if i can post links to apps at this forum)). With that 'n' app, you can shop the B&N site along with reading a book. Will look later tonight and see if i can install there library app.
Dont know about HDMI (am wondering the same - but not a big deal for me).
As for bluetooth, i tried a Logitech MX5000 ("desktop") keyboard just to see what happens, they made the hand-shake and connected but nothing after that... i did not try too hard though... just wanted to see what would happen. That keyboard is the only bluetooth "device" i have.
_

iMisspell said:
Im new to Tablets (only have a Nook HD+ for acouple weeks ) but not flashing.
Just installed CM 10.1.3 (last night)
One thing which i was after (and the main reason for me) was USB thumbdrive support/storage (link about it) and that worked great.
After, i did install the B&N "store" app (the green 'n' app) and it installed fine (had to install it via .apk found out side of the Google Play (dont know if i can post links to apps at this forum)). With that 'n' app, you can shop the B&N site along with reading a book. Will look later tonight and see if i can install there library app.
Dont know about HDMI (am wondering the same - but not a big deal for me).
As for bluetooth, i tried a Logitech MX5000 ("desktop") keyboard just to see what happens, they made the hand-shake and connected but nothing after that... i did not try too hard though... just wanted to see what would happen. That keyboard is the only bluetooth "device" i have.
_
Click to expand...
Click to collapse
I'm pretty sure posting it would be fine because it isn't a paid app and is freely available. If you still leery you could IM it to me, I'd like to give it a try. I have the HDMI adapter and it worked fine with the stock ROM but I'm only getting a blank screen on the TV with 10 1.3. I've read it is working though so I am going to tweak it a little bit to see what the deal is.

felacio said:
I'm pretty sure posting it would be fine because it isn't a paid app and is freely available. If you still leery you could IM it to me, I'd like to give it a try. I have the HDMI adapter and it worked fine with the stock ROM but I'm only getting a blank screen on the TV with 10 1.3. I've read it is working though so I am going to tweak it a little bit to see what the deal is.
Click to expand...
Click to collapse
Since you've been here for 6+ years, ill take your word for it
http://www.apk-planet.com/download_NOOK_Read_Books_and_Magazines/tech/
Found that via a google search nook .apk
I did search for the Library app but did not find anything.
[EDIT]
Just discovered (thanks) 1mobile and they have the 'n' B&N store app also.
http://www.1mobile.com/bn-ereader-79949.html
_

I'm in the same boat, just got a new Nook HD+ (came free with my car). I used the stock ROM for a day or so, pretty fast but limited in scope. I've installed CyanogenMod 10.1.3 using the instructions from the dummies thread, it ran fine for about half a day and now suddenly performance is awful. Animations lag, trying to change the settings lags, there's input lag, I have to wait 1-2 seconds for the keyboard to come up, 2-3 seconds to tap on different sections in Settings. I thought maybe I installed too many apps so I tried to wipe it but I can't. "wipe data/factory reset" in CWM still leaves crap behind, Factory data reset in Settings does the same. Now I have 6 GB left of 12.67 GB and nothing installed. Is there any way to fully remove everything?
Edit: some exploration with du in terminal revealed two huge folders, Android/data and Android/obb. Sure enough, there's my missing 6 GB. How does this not get deleted? Does reset mean something else in Android than other mobile operating systems?

rpop said:
I'm in the same boat, just got a new Nook HD+ (came free with my car). I used the stock ROM for a day or so, pretty fast but limited in scope. I've installed CyanogenMod 10.1.3 using the instructions from the dummies thread, it ran fine for about half a day and now suddenly performance is awful. Animations lag, trying to change the settings lags, there's input lag, I have to wait 1-2 seconds for the keyboard to come up, 2-3 seconds to tap on different sections in Settings. I thought maybe I installed too many apps so I tried to wipe it but I can't. "wipe data/factory reset" in CWM still leaves crap behind, Factory data reset in Settings does the same. Now I have 6 GB left of 12.67 GB and nothing installed. Is there any way to fully remove everything?
Edit: some exploration with du in terminal revealed two huge folders, Android/data and Android/obb. Sure enough, there's my missing 6 GB. How does this not get deleted? Does reset mean something else in Android than other mobile operating systems?
Click to expand...
Click to collapse
Those folders are in your media (sdcard) folder and media does not get wiped in a factory reset. In CWM you need to go to mounts and storage and format 'data and datamedia' in order to wipe your media.
Sent from my Nook HD+ running CM10.1 on emmc.

I love my Nook HD+ and that is after trying a Samsung Note 8, a Nexys 2013 and others. Really for the prize you can't beat it!
I have tried pretty much every ROM there is here in XDA both from SDCard and emmc. For my Nook HD+ in particular nothing beats the Stock ROM with Unknown Sources and Root. I also tried Nova, Apex, SPB, Smart, Go EX, and AWD launchers in their Pro versions but the only one that was really fast and had no lagging at all was Next Launcher and that is the one I have know on my HD+.
To be able to use USB OTG (not needed on CM 10 thanks to verygreen) on Carbon, Slim, etc., I used the usbhostswither.apk that is included on Xperia Carbon JB, installed it and worked great. I haven't been able to installed it on my HD+ even with root and unknown sources enable, it gives me a parsing app error. Trying to see if I can installed it and if it workd to turn on and off USB Host on Stock Rom with root.
I tried and now use 3 apps from the forum that really rock, FX Explorer, Gallery Plus and WebSharing Lite.
You are gonna have a blast with your HD+ and now that some at XDA have started to test and port Ubuntu Touch to it, well you won't be without a whole lot of options to mess with your Nook :laugh:
---------- Post added at 01:32 PM ---------- Previous post was at 01:14 PM ----------
Hi leapinlar and community, first thanks for all your contributions, they have enable the Stock Rom to be a great alternative for those of us that like many of it features.
I have a problem installing the USBHostSwitcher app on the HD+ rooted and with unknown sources enabled. The weird thing is that I was able to install and use the app successfully when testing emmc Carbon Rom JB and Xperia Tweeked for HD+. I was also able to installed it to other devices like my Galaxy Note II (stock, not rooted).
The Nook installer error on HD+ reads " Parse error" "There is a problem parsing the package".
Is there a way to create a package so I can flash an app (like we do with the Google Apps?
Thanks in advance for any recommendations.

gmicalzoma said:
Hi leapinlar and community, first thanks for all your contributions, they have enable the Stock Rom to be a great alternative for those of us that like many of it features.
I have a problem installing the USBHostSwitcher app on the HD+ rooted and with unknown sources enabled. The weird thing is that I was able to install and use the app successfully when testing emmc Carbon Rom JB and Xperia Tweeked for HD+. I was also able to installed it to other devices like my Galaxy Note II (stock, not rooted).
The Nook installer error on HD+ reads " Parse error" "There is a problem parsing the package".
Is there a way to create a package so I can flash an app (like we do with the Google Apps?
Thanks in advance for any recommendations.
Click to expand...
Click to collapse
Even if you can get it to install, I'm not sure it will work on stock. I know verygreen had to mod the kernel to make it work. And I think all the other ROMs like Carbon, etc, use his kernel.
See this post:
http://forum.xda-developers.com/showthread.php?p=42501199
Sent from my Galaxy Tab 2 using XDA Premium