To really figure it out, you will need to work on an API that the rest of us can see also! However, it's possible that API 23 modifies data structures or objects that your app accesses that have grown in size. Without code and a proper test environment for the rest of us, you might not get much besides this little tip right here:
Out of Memory Error while loading bitmaps
You can always request the expanded heap, but given your situation that's not a true fix, it only masks the real problem.
FYI - if your background is 1900px * 1200px then it's memory alloc is probably taking up 4 * 1900 * 1200 = 9MB (depending on the type of image, but typically its 4 bytes (32-bits) per pixel). It's pretty large, really.
For a good overall link on "OutOfMemory" - this is prob the best on SO:
Strange out of memory issue while loading an image to a Bitmap object
and a good link on heap sizes based on device / API: