Nook HD - Kindle and Nook apps for tablet

[yelloguy]

I just got the CM10 installed on an sd card using bokbokan's images. Everything works great. But the Kindle app thinks it is running on a phone and everything looks super big. I can change the text size and some options but I like the tablet UI much better. Nook app does the same.

So I got this app called LCD Density and tried changing mine from the default 240 to 300. The whole Android UI adjusted itself and looked better (smaller) but the Kindle app and the Nook app were unaffected.

1. Is there a way to put these apps into Tablet mode?
2. Is there a way to stick the new density across reboots using this app?

TIA.

 

[leapinlar]

I just got the CM10 installed on an sd card using bokbokan's images. Everything works great. But the Kindle app thinks it is running on a phone and everything looks super big. I can change the text size and some options but I like the tablet UI much better. Nook app does the same.

So I got this app called LCD Density and tried changing mine from the default 240 to 300. The whole Android UI adjusted itself and looked better (smaller) but the Kindle app and the Nook app were unaffected.

1. Is there a way to put these apps into Tablet mode?
2. Is there a way to stick the new density across reboots using this app?

TIA.

Don't use the LCD app. On CM10 it is ok to change /system without worrying about resetting your device. So go to /system and look for build.prop. Edit that file with your root file manager. There is a line that ends ...density=240. Change that to 300. But you will have to edit it every time you flash a new ROM. The way to get around that is to create a file in /data named local.prop. Put this line in it.

qemu.sf.lcd_density=300

That will not get overwritten in a rom flash.

The kindle and nook apps detect how they should display themselves based on lcd density and screen size. The only way to get them into tablet mode is to REDUCE density not raise it. So you need to make a choice, higher density and phone mode, or lower density and tablet mode.

Sent from my Nook HD+ Running CM10 on SD

 

[yelloguy]

That's it. The problem was the app -- it wasn't changing the density correctly. I just changed it to 160 in the system/build.prop and everything switched to the tablet mode. Kindle and the Nook app work so much better but the UI looks less usable. I changed the system font to Huge and that helped a little. Two more questions:

1. Do you know what is the minimum density where Android still thinks it is a tablet? Is it 180? 200? We already know it switches to phone mode at 240. Of course, I can experiment if I can't find out.

2. Does the Nook HD's native dpi matter at all? You know how the desktop LCD screens have a native mode resolution where everything looks sharp and non-native mode where it maps the OS pixels to native pixels and everything looks blurry? I am wondering if something like that is going on here and I will have to do some dpi -> dip math to find out what is best for the Nook HD.

Thanks again.

Edit: Googling revealed 213 is the magic number. Tried 210 but I still got phone ui. Next I tried 200 and got a tablet ui with everything nicely usable. For someone else, you might want to try 190 or 180.

 

[cool2know]

create or modify files in root directory

Don't use the LCD app. On CM10 it is ok to change /system without worrying about resetting your device. So go to /system and look for build.prop. Edit that file with your root file manager. There is a line that ends ...density=240. Change that to 300. But you will have to edit it every time you flash a new ROM. The way to get around that is to create a file in /data named local.prop. Put this line in it.

qemu.sf.lcd_density=300

That will not get overwritten in a rom flash.

The kindle and nook apps detect how they should display themselves based on lcd density and screen size. The only way to get them into tablet mode is to REDUCE density not raise it. So you need to make a choice, higher density and phone mode, or lower density and tablet mode.

Sent from my Nook HD+ Running CM10 on SD

I am new to android OS, and I apologize for the following simple question: how do I gain access for creating and modifying a file in /data in my rooted Nook HDPlus (with the set of files and steps you provided. thank you.) I tried to use the Root Browser to create a file in /data for changing my lcd density, but each time I was denied access. Do I need to somehow log into my device as a superuser (how), or do I need to change the setting (how)? Thanks again for your time, expertise, and patience.

 

[leapinlar]

I am new to android OS, and I apologize for the following simple question: how do I gain access for creating and modifying a file in /data in my rooted Nook HDPlus (with the set of files and steps you provided. thank you.) I tried to use the Root Browser to create a file in /data for changing my lcd density, but each time I was denied access. Do I need to somehow log into my device as a superuser (how), or do I need to change the setting (how)? Thanks again for your time, expertise, and patience.

Are you sure you are rooted? And when you started root browser the first time, did it ask for root access and did you grant it? Open the superuser app and see if it lists root browser as being granted superuser access. If it does not, go to settings, applications, my apps, root browser and clear the data for it. Then restart root browser and if really rooted it will ask for superuser access.

Sent from my Nook HD running CM10.1 on Hybrid SD

 

[cool2know]

Are you sure you are rooted? And when you started root browser the first time, did it ask for root access and did you grant it? Open the superuser app and see if it lists root browser as being granted superuser access. If it does not, go to settings, applications, my apps, root browser and clear the data for it. Then restart root browser and if really rooted it will ask for superuser access.

Sent from my Nook HD running CM10.1 on Hybrid SD

Following the steps you outlined, it all worked out. My Nook HD+ now is in higher resolution. The Root Browser was not in the Superuser listing, somehow. Again, thanks for the help.