Adding an ro.sf.lcd_density=215 to boot.prop file fixes Swype not running (and a few other apps.)

[Chiem Ma]

I've been experimenting with Android x86, and, have discovered that some apps will screw up if the LCD density isn't within their acceptable range. I'm not certain if the problem is that the density doesn't match what the proram expects, or if the value must be close to the X_DPI/Y_DPI values. For SWYPE, I used ro.sf.lcd_density=215, and this allowed SWYPE to work properly, while 240, 220, and 200 all failed.

Also, on my SP3, when the system "locks up", it appears that what's really going on is that some system-wide overlay is interfering with reception of the touch input. I say this because clicking the capacitive start button still causes the launcher to be displayed, and prior to losing the ability to work with android the screen is briefly covered in an "overlay film."

Android, unfortunately, seems to keep my SP3 CPU constantly busy. My laptop burns up and I only get 2 hours on a full charge using Android.

[Mike]

That has always been an Issue (for me flashing my phones), Back in the
day, J.B. They said DON'T mess with it, So you could be Very Correct in
your statement, I have, Back Then in J.B. and it locked it up.....

Mike

[Chiem Ma]

I should also mention that the default is 240 which causes these apps to fail.