[USER][CM9/ICS][5-28 PATCH NO LONGER NEEDED] CM9 240 dpi with Soft Navigation Keys

Status
Not open for further replies.
Search This thread

leapinlar

Senior Member
Oct 18, 2006
8,873
3,876
PATCH NO LONGER NEEDED!

This post used to discuss a patch I made to show the Navigation Keys in Phone GUI mode. I am happy to announce that the patch is no longer needed.

In CM9 the Phone GUI is activated anytime you set the lcd density to anything higher than 160 dpi. With the Nook Color when you go to the Phone GUI the navigation keys are suppressed.

There is a method to activate the Navigation Bar that requires no patches or zip flashes. Just add the two lines below to your local.prop file in /data. I recommend using local.prop instead of build.prop so that it is not necessary to re-edit the file after each flash of a new ROM. If you do not have this file, create an empty txt file and put these two lines in it:

qemu.sf.lcd_density=240
qemu.hw.mainkeys=0

The first line tells your system to change lcd density to put it in phone gui. You can change the 240 number to any number above 160 and the phone gui will be displayed.

The second line tells your system that your hardware has no physical keys and enables the soft key navigation bar.

Reboot.

If you want to return to 160 dpi and the tablet gui, just delete or comment out the two lines above and reboot.

Also CM has added the ability to customize the navigation bar. Go to settings, system, navigation bar and it will tell you how to do it. You can move the buttons around, add buttons, change how they perform, etc.

5-28-2012 is the last day I will be making patches.

No-moar zips! Yay!

Edit (6-24): Removed last patch. Too many users will still downloading it and it does not work properly with the current nightlies.

Removed screenshots
 
Last edited:

bornagainpenguin

Senior Member
Oct 22, 2010
378
71
The board lists the latest version as only being a few bytes compared to the other earlier versions of this, is this a sign of a bad upload?

Will be giving the second to last version a try to see if this is what I hope it will be.. Thanks!

Sent from my NookColor using Tapatalk
 

leapinlar

Senior Member
Oct 18, 2006
8,873
3,876
The board lists the latest version as only being a few bytes compared to the other earlier versions of this, is this a sign of a bad upload?

Will be giving the second to last version a try to see if this is what I hope it will be.. Thanks!

Sent from my NookColor using Tapatalk
I still see 4.1MB as the size of rev 11, which is the latest.
 

bornagainpenguin

Senior Member
Oct 22, 2010
378
71
Okay, that's screwy. On my nook it said it was only a few bytes, but now on my phone it is listing the same size as the others. Sorry for wasting your time.

Oh, a quick question while I have your attention --is there any way to get the two status layout but with a lower dpi (160)? Or are we stuck choosing between phone and tablet interface if we want more screen space?

Sent from my LG-VM670 using Tapatalk
 
Last edited:

leapinlar

Senior Member
Oct 18, 2006
8,873
3,876
Oh, a quick question while I have your attention --is there any way to get the two status layout but with a lower dpi (160)? Or are we stuck choosing between phone and tablet interface if we want more screen space?
Not sure what you mean by two status layout. Do you mean status at top and navigation on bottom?

160 always gives you the tablet layout with the status bar at the bottom, with the battery and time, etc there. You can use other launchers that allow you to modify such things as icon grid layout, etc, but the full status bar remains at the bottom.

If you set anything above 160 (180, for example), it goes to phone mode with the status bar at the top, and if you use my patch, the navigation bar will be at the bottom. You can change the density to anything above 160 and my patch will work. I just chose 240 because it is what I like and gives the most market compatibility. After applying my patch, just change the value in build.prop in /system (ro.sf.lcd_density=).
 
Last edited:
  • Like
Reactions: bornagainpenguin

bornagainpenguin

Senior Member
Oct 22, 2010
378
71
Yeah, that's what I meant. I will probably give 180dpi a try next time I use the nightlies. Going to mess around with CM7.2 Kang and see how it goes. Thanks for everything, I really hope your patch is made a default option once CM9 goes stable.

Sent from my LG-VM670 using Tapatalk
 

bornagainpenguin

Senior Member
Oct 22, 2010
378
71
Could you please check the last file again? This one: update-softkey-240dpi-4-17-Rev13.zip Thanks.

I can see it to be the same size as the others, but when I try to download it all I get is an html 404 page. update-softkey-240dpi-4-15-Rev12.zip downloaded just fine.

--bornagainpenguin
 

leapinlar

Senior Member
Oct 18, 2006
8,873
3,876
Could you please check the last file again? This one: update-softkey-240dpi-4-17-Rev13.zip Thanks.

I can see it to be the same size as the others, but when I try to download it all I get is an html 404 page. update-softkey-240dpi-4-15-Rev12.zip downloaded just fine.

--bornagainpenguin
It downloaded fine for me just now and 23 others have downloaded it.

Sent from my Nook Color running ICS and Tapatalk
 

Sudonym

Member
Jan 28, 2012
15
4
I'm also not able to download a complete Rev13. I just get a file with a length of 554. I was able to get Rev12, but it's not working with the latest builds. Thanks for all your help on this!
 

bornagainpenguin

Senior Member
Oct 22, 2010
378
71
It downloaded fine for me just now and 23 others have downloaded it.

Sent from my Nook Color running ICS and Tapatalk

At least ten of those were mine. I was out and about last night and yesterday morning so I tried at different places and times before asking about it. I didn't want a repeat of last time where I asked and it was fine later that day. I appreciate the effort you guys put into this kind of stuff and the last thing I want to be is a bother.


The old versions do not work with the latest build, that's why I updated it. I just uploaded it again. Try now.

Just downloaded it on my phone and it looked like a complete package! Thanks!


update: how long is it supposed to take on reboot to apply? I'm stuck in reboot for a while now and starting to worry...

Sent from my LG-VM670 using Tapatalk
 
Last edited:

bornagainpenguin

Senior Member
Oct 22, 2010
378
71
Okay. This is not working for me at all. I don't know how many times I've flashed now. All that happens is a message about Android updating my applications and then a return to the bootanimation that never ends. Not sure where things are going wrong. :banghead:

Wish I knew what I was doing to screw things up. :mad:



Sent from my LG-VM670 using Tapatalk
 

Sudonym

Member
Jan 28, 2012
15
4
Okay. This is not working for me at all. I don't know how many times I've flashed now. All that happens is a message about Android updating my applications and then a return to the bootanimation that never ends. Not sure where things are going wrong. :banghead:

Wish I knew what I was doing to screw things up. :mad:

Are you flashing the Rev13 patch with a 4/18 build? That combination works for me.
 

bornagainpenguin

Senior Member
Oct 22, 2010
378
71
Are you flashing the Rev13 patch with a 4/18 build? That combination works for me.

I tried it with that build and I tried it with the one from yesterday. In both cases, I get a message about moving applications and a return to the bootanimation. Then ten or more minutes go by while the bootanimation spins with no feedback or signs of ever getting back into the GUI.

Really frustrating.

Sent from my NookColor using Tapatalk
 

slack04

Senior Member
May 4, 2010
1,021
302
Sorry if this is a stupid question, but will this work with Eyeballer's nightly builds (with/without opengl) or just with the one in the "work in progress" thread?
 

mateorod

Inactive Recognized Developer
Nov 16, 2011
1,981
3,503
New Orleans
www.gigmasters.com
I tried it with that build and I tried it with the one from yesterday. In both cases, I get a message about moving applications and a return to the bootanimation. Then ten or more minutes go by while the bootanimation spins with no feedback or signs of ever getting back into the GUI.

Really frustrating.

Sent from my NookColor using Tapatalk

The update to the CM repo broke the packages I offer in Botbrew, which happens when they significantly update the framework apps. Leap's patches always seem to break at he same time. The behavior your describing is what happens when you match a patch and a ROM that are incompatible. I know you have had problems with the downloader, (trust me you're not alone.) Just, one more time, flash the latest build and the latest patch together. The repo did not update again, I can promise you that. I bet with all the flashing and patching, you just did not patch the right build.

I have swapped in the old system apps maybe fifteen times over the last couple days, I know what that behavior is. And I use my own version of leapinlar's patch, so I know exactly how it works and what that behavior means. If it is working for others it will work for you if it has downloaded correctly.

Sorry if this is a stupid question, but will this work with Eyeballer's nightly builds (with/without opengl) or just with the one in the "work in progress" thread?

The system apps work in any build for the Nook Color, opengl or not.
 

leapinlar

Senior Member
Oct 18, 2006
8,873
3,876
Sorry if this is a stupid question, but will this work with Eyeballer's nightly builds (with/without opengl) or just with the one in the "work in progress" thread?
This patch will work with eyeballer's, Samiam303's or your home built version. All you have to make sure of is that you are using a version that is reasonably close in date to the build. As CM9 evolves and improves the base files that I am patching change and old versions of the patch will not work on that build. For instance, the 4-15 patch will no longer work on 4-17 or newer builds. I try to upload new versions when that happens.

I just tested eyeballer's 4-19 non-opengl build with the 4-17 patch and it still works.

@bornagainpenguin - are you flashing the build first and booting to that to be sure the base build download is ok before you flash my patch? If you do that it should say updating only 1 application after flashing mine. You might also try manually clearing your dalvik cache. That is what it is supposed to be doing automatically when it says updating applications.

Sounds like you are having download problems with with your devices so that might be the issue too.

Sent from my Nook Color running ICS and Tapatalk
 
Last edited:

bornagainpenguin

Senior Member
Oct 22, 2010
378
71
@bornagainpenguin - are you flashing the build first and booting to that to be sure the base build download is ok before you flash my patch? If you do that it should say updating only 1 application after flashing mine. You might also try manually clearing your dalvik cache. That is what it is supposed to be doing automatically when it says updating applications.

Sounds like you are having download problems with with your devices so that might be the issue too.

Sent from my Nook Color running ICS and Tapatalk

I am making sure I boot up to a complete Android environment (beginning the setup part where they ask you which language and your google account, etc) before rebooting to recovery to install.

I just gave it another try using eyeballer's 4-19 opengl build and everything seemed to work right up to the point where I tried to set the DPI. Using Nook Color Odds and Ends results in no change. I then try LCD Resolution (Root) which results in an error on reboot:

Code:
Unfortunately, System UI has stopped.

I suppose I could just give up and accept the 240 DPI, but I really don't want my icons to be that big...

Back to CM7 with me I suppose....

--bornagainpenguin
 
Last edited:

leapinlar

Senior Member
Oct 18, 2006
8,873
3,876
I am making sure I boot up to a complete Android environment (beginning the setup part where they ask you which language and your google account, etc) before rebooting to recovery to install.

I just gave it another try using eyeballer's 4-19 opengl build and everything seemed to work right up to the point where I tried to set the DPI. Using Nook Color Odds and Ends results in no change. I then try LCD Resolution (Root) which results in an error on reboot:

Code:
Unfortunately, System UI has stopped.

I suppose I could just give up and accept the 240 DPI, but I really don't want my icons to be that big...

Back to CM7 with me I suppose....

--bornagainpenguin
What were you trying to set the dpi to? The best way to set it is to edit the build.prop file in /system manually. Change the line ro.sf.lcd_density=240 to some other value above 160. That line does not exist there until you flash my patch. Also make sure there is not a density line in local.prop in /data. Some of those density changing apps try to set density there and if they do, that setting never gets overwritten in a flash and always overrides what is in build.prop.

Sent from my Nook Color running ICS and Tapatalk
 

bornagainpenguin

Senior Member
Oct 22, 2010
378
71
What were you trying to set the dpi to?

180 DPI. Trying 160 DPI just means that I lose the phone GUI


The best way to set it is to edit the build.prop file in /system manually. Change the line ro.sf.lcd_density=240 to some other value above 160. That line does not exist there until you flash my patch.

I've never had great luck remembering the adb commands to push and pull files. I could probably try using root explorer to copy to the SDCard and do it on the netbook? Will look into this....


Also make sure there is not a density line in local.prop in /data. Some of those density changing apps try to set density there and if they do, that setting never gets overwritten in a flash and always overrides what is in build.prop.

Sent from my Nook Color running ICS and Tapatalk

Just checked that out and doesn't seem to be a factor. Thanks for bringing it up so I could eliminate it though.

Sent from my NookColor using Tapatalk
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    PATCH NO LONGER NEEDED!

    This post used to discuss a patch I made to show the Navigation Keys in Phone GUI mode. I am happy to announce that the patch is no longer needed.

    In CM9 the Phone GUI is activated anytime you set the lcd density to anything higher than 160 dpi. With the Nook Color when you go to the Phone GUI the navigation keys are suppressed.

    There is a method to activate the Navigation Bar that requires no patches or zip flashes. Just add the two lines below to your local.prop file in /data. I recommend using local.prop instead of build.prop so that it is not necessary to re-edit the file after each flash of a new ROM. If you do not have this file, create an empty txt file and put these two lines in it:

    qemu.sf.lcd_density=240
    qemu.hw.mainkeys=0

    The first line tells your system to change lcd density to put it in phone gui. You can change the 240 number to any number above 160 and the phone gui will be displayed.

    The second line tells your system that your hardware has no physical keys and enables the soft key navigation bar.

    Reboot.

    If you want to return to 160 dpi and the tablet gui, just delete or comment out the two lines above and reboot.

    Also CM has added the ability to customize the navigation bar. Go to settings, system, navigation bar and it will tell you how to do it. You can move the buttons around, add buttons, change how they perform, etc.

    5-28-2012 is the last day I will be making patches.

    No-moar zips! Yay!

    Edit (6-24): Removed last patch. Too many users will still downloading it and it does not work properly with the current nightlies.

    Removed screenshots
    2
    I'm also not able to download a complete Rev13. I just get a file with a length of 554. I was able to get Rev12, but it's not working with the latest builds. Thanks for all your help on this!
    The old versions do not work with the latest build, that's why I updated it. I just uploaded it again. Try now.
    1
    Oh, a quick question while I have your attention --is there any way to get the two status layout but with a lower dpi (160)? Or are we stuck choosing between phone and tablet interface if we want more screen space?
    Not sure what you mean by two status layout. Do you mean status at top and navigation on bottom?

    160 always gives you the tablet layout with the status bar at the bottom, with the battery and time, etc there. You can use other launchers that allow you to modify such things as icon grid layout, etc, but the full status bar remains at the bottom.

    If you set anything above 160 (180, for example), it goes to phone mode with the status bar at the top, and if you use my patch, the navigation bar will be at the bottom. You can change the density to anything above 160 and my patch will work. I just chose 240 because it is what I like and gives the most market compatibility. After applying my patch, just change the value in build.prop in /system (ro.sf.lcd_density=).
    1
    I've played with button savior on the MIUI Gingerbread builds, but I really didn't like it. I couldn't figure out a way to get it to stay open on the bottom in a bar underneath the dock of Espier Launcher HD no matter what I tried.
    Have you tried Virtual Button Bar? It may not do what you want but does stay on the bottom. There is a free trial you can try.


    Sent from my NookColor using Tapatalk
    1
    Flashed eyeballer's 20120522 nonopengl from the 20120520 nonopengl and then flashed the CM9 240 r18 patch.

    The "previous menu" button (double rectangle) doesn't work anymore.

    Sent from my NookColor using Tapatalk 2
    If you look at my edited first post (4/27), you will see that that is now the recent key again. Also now you can customize the bar (5/18). I have mine customized so I don't show the recent key anymore. Just use a long press on home.

    (Edit, misread your post, see edited above.)

    Sent from my Nook Color running ICS and Tapatalk
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone