[Nook HD, HD+ Themes and Apps] RageAgain:
Please note that someone tried this on their SD card install of 10.2 and it apparently rendered it unbootable somehow ( build.prop edits can be dangerous, but I have no idea what went wrong as these are just the roms previous values ). Nandroid backups if possible are always a good idea...

UPDATE 09/25/13:

I am now using a heapsize of 384m, and everything seems to work quite well for me ( some things are working better than before ). Also, I am currently leaving the other two settings at their new values.

dalvik.vm.heapsize=384m

I had begun to experience intermittent lag with the higher values, and although it usually went away if I used the power button to turn off the screen and then turned it back on again...

I am finding that some programs seem to run much faster/smoother with the new heapsize of 384m.

:)

FYI:

After experimenting with just changing the heapsize, first to 512m and then to both 402m and 456m, I have gone back to my original changes of restoring all of the dalvik vm settings to their pre-0813 values. My reasons are as follows:

1) As verygreen noted, there is some lag with the 512m heapsize, but I don't experience it with the other two changes made as well.

2) If my heapsize is set to less than 512m I get intermittent screen flashing on my setup ( exacerbated when charging ).

3) Several apps that I thought had become incompatible with 4.3 actually just need the larger heapsize to operate correctly ( they had actually stopped working with the 4.2 0813 release but I originally skipped that one ).

4) The 'Stay Awake while charging' setting works properly on my setup with the changes, and I have stopped getting the 'Unfortunately XXX has stopped' type messages.

5) Finally, on my setup, for some reason the Kindle App still crashes with anything less than a 512m heapsize ( this is probably due to some of the software that I am running, most notably Resolution Changer ).

So, I went back to the original changes. Of course, your experience may vary... :cyclops:

This is the official word/fix from verygreen:

It should migrate into the CM/Nightlies eventually.

It works on my Nook HD+ now, so I am curious if it is just me or these same changes might work on others CM 10.1 and 10.2 installs.

I have been trying a variety of build.prop modifications in order to try and get greater compatibility for my Nook HD+ to run apps which I have purchased from the Google Play Store and report that they are incompatible and cannot even be sideloaded. To that end I have downgraded my emmc CM install from 10.2. to 10.1 0813 version so that I could run an app called "Resolution Changer" that I purchased from the Google Play Store ( it has already helped me get DeadSpace running ). I also changed my Device/Brand/Manufacturer to get BackStab to sideload, but I originally loaded the 10.1 0812 because the Kindle App still worked with it. On my install however, the changes made to the 0813 version of CM10.1 made it more stable, so I was trying to get the Kindle App to work with that...

( Note: the following is a copy of the text I posted in the "CM10.2 updated 9/01" thread. )

The Kindle App worked on the 0812 emmc release of 10.1 but not on the 0813 emmc release of 10.1, so on the assumption ( I know it is a bad idea to assume anything but... ) that it might be something simple I edited my build.prop on my 0813 emmc install to change the Dalvik vm settings back to the 0812 parameters....

It is now working on my install, so I wanted to know if the same changes might make it work on CM 10.2 - 4.3 as well ( since it carried forth the modified Dalvik settings ).

MY ORIGINAL CHANGES

What I changed in build.prop ( restored to 0812 values ):

dalvik.vm.heapstartsize=16m ( this was changed to 8m in 0813 )

dalvik.vm.heapgrowthlimit=192m ( this was changed to 128m in 0813 )

dalvik.vm.heapsize=512m ( this was changed to 448m in 0813 )

So by increasing the settings back to their pre-0813 values the Kindle App began to work.

So, maybe verygreen can tell us which one(s) actually fix the problem...

I HAVE been messing with my build.prop for other reasons, but these were the only changes that I made between the Kindle App not working and working....