[Q] Remove 3 dot menu bar in GPe rom, but keep 3 dot menu in apps? - One (M7) Q&A, Help & Troubleshooting

Okay, so my question is similar to this guy's: http://forum.xda-developers.com/showthread.php?t=2323390
Sadly, the solution he found did not appear to work for me (guessing it's a sense thing?). Basically, I want the setup that the Sense HTC One has regarding the menu button, remove the ugly ass bar, but keep the button in apps the use it correctly (like google apps such as the play store or chrome), which things like remove 3dot menu does not do.
So far, I have been able to make a long press of the back button bring up a menu with Gravitybox, but have been unable to remove the black bar without removing native menu buttons in apps.
Anyone have a solution for me?
I'm running the latest Sinless Google Play Rom (Sinless 4.1.2 with Android 4.3)

The solution is posted in the thread you've linked...

Guich said:
The solution is posted in the thread you've linked...
Click to expand...
Click to collapse
Change the qemu.hw.mainkeys=1 to qemu.hw.mainkeys=0? Did that, nothing changed.
EDIT: perhaps I should be more clear. qemu.hw.mainkeys=0 was ALREADY in the build.prop when I opened it (likely because the Sinless Rom Developer put it in there). So, that addition to the build.prop file was in there, and I was still receiving the black menu bar regardless.

Related

[Q] Unable to access menu in Google Play

Out of nowhere my three dots in Google Play have disappeared and I'm unable to pull up the menu/settings. All I have in the top corner is the search funtion. How do I retrieve this? I use LMT instead of the stock bars for navigation. I even tried freezing 'Soft Key Bar' in apps. Rebooted, and no change. Any help would be kindly appreciated.
Braves1995 said:
Out of nowhere my three dots in Google Play have disappeared and I'm unable to pull up the menu/settings. All I have in the top corner is the search funtion. How do I retrieve this? I use LMT instead of the stock bars for navigation. I even tried freezing 'Soft Key Bar' in apps. Rebooted, and no change. Any help would be kindly appreciated.
Click to expand...
Click to collapse
It depends on how you set up LMT. Did you assign a menu option to your pie? The three dots on the pie was mine and I used that to access menu options inside of apps
Thanks for the quick response. I've setup my pie with the home, back, menu (which I thought would access all menus within all apps) and OpenNotificationBar. Is there another menu command within LMT that I'm missing?
Lower your dpi in the build.prop
Open build.prop file and edit this line only.
ro.sf.lcd_density=240 <--------Set this value to 180. Back out of build.prop, save when asked. Reboot. Check.
Krsmqn said:
Lower your dpi in the build.prop
Open build.prop file and edit this line only.
ro.sf.lcd_density=240 <--------Set this value to 180. Back out of build.prop, save when asked. Reboot. Check.
Click to expand...
Click to collapse
I'm a little hesitant about editing the build.prop. Is there another way? What about re-installing the Play Store?
If you are hesitant about it that's ok. I don't know any other way. But the edit is harmless, I promise. You just have to be careful that you don't accidentally edit anything else.
You will notice that the lock screen is different.... but that's OK. You can download 2 apps to have a custom lock screen like widget locker or magic locker. I'll post links if you so desire.
If you want to skip my advice all together... well that's your prerogative. But you may be waiting a while for another fix.
Here's 2 pictures showing the difference. The top is with dpi of 240. The bottom is dpi 180. With mainkeys =1
****UPDATE****
This is with
A) softbar.apk removed from /system/app,
B) qemu.hw.mainkeys=0
C) dpi set at 180.
Perfect.
I should mention that I have go keyboard installed and xSettings installed with stock locker option disabled. With widget locker installed. And LMT soft keys installed.
Krsmqn said:
If you are hesitant about it that's ok. I don't know any other way. But the edit is harmless, I promise. You just have to be careful that you don't accidentally edit anything else.
You will notice that the lock screen is different.... but that's OK. You can download 2 apps to have a custom lock screen like widget locker or magic locker. I'll post links if you so desire.
If you want to skip my advice all together... well that's your prerogative. But you may be waiting a while for another fix.
Click to expand...
Click to collapse
I tried both, widget locker and magic locker, neither seemed to work for me after changing my DPI. Any suggestions?
Sent from my KF-HD7
Oddly enough, I have an app called Fullscreen Toggle that I installed to take away the soft key bar, which has been working just fine. In this app, I decided to try re-enabling the stock soft keys to see if it would bring back the menu button in Google Play (not sure why I thought it would, just effing around with it). Well, when I re-enabled the soft key bar in Fullscreen Toggle it didn't bring the soft keys back up, but I DID get my menu button in Google Play back along with other menu buttons in other apps! Weirdness..
Braves1995 said:
Oddly enough, I have an app called Fullscreen Toggle that I installed to take away the soft key bar, which has been working just fine. In this app, I decided to try re-enabling the stock soft keys to see if it would bring back the menu button in Google Play (not sure why I thought it would, just effing around with it). Well, when I re-enabled the soft key bar in Fullscreen Toggle it didn't bring the soft keys back up, but I DID get my menu button in Google Play back along with other menu buttons in other apps! Weirdness..
Click to expand...
Click to collapse
Have you rebooted?
Krsmqn said:
Have you rebooted?
Click to expand...
Click to collapse
Yes, several times. I'd forgotten that I also froze the system app 'Soft Key Bar'. I'm assuming that's why it didn't come back up. Not sure why enabling that in Fullscreen Toggle brought back the app menus though. Either way, it's doing what I want it to do now.
Thank god for this forum or I wouldn't be attempting any of this crap, lol.
Is your drop down status bar short?
Krsmqn said:
Is your drop down status bar short?
Click to expand...
Click to collapse
A tad, yes. Is there any way to fix that and still keep my Google Play menu? Here you go:
Check out the new Rom in the kfhd7" development thread.
Sent from my KFTT using xda premium
Had this problem but found a setting
I had this problem in a rom I was using and tried all kinds of dpi settings without any luck getting the menu drop-down for the playstore settings. Then while I was in the interface settings of the rom control, there was a setting called "Statusbar Behavior" and that was turned off, and when turned on, the three dots that allow menu settings was available. This is late for this case, but I wanted to share so if others down the road had a similar problem and came across this thread as I did trying to resolve this kind of issue it would give another option to check. Hope this helps.

[Q] Can you enable logo menu button AND in-app 3-dot menus?

i have my HTC button mapped to the menu button. i've noticed that all the mods that remove the black 3-dot menu button that pops up across the bottom of the screen also remove the built-in 3-dot menu button in apps (like the one in the upper right of the Google Play Store, for instance). i assume this is because they are being told there is a hardware menu button, so they shouldn't show their built-in menus.
my question: is there a way to remove the annoying black bar across the bottom menu button, but keep the built-in app menu buttons?
Install a jellybean sense rom. Hold home for menu and keep the built in menu on apps that have it.
thanks, but i was hoping for a way that would work across ROMs.
build.prop change to fix this
I've managed to fix this by changing build.prop
Edit or add the entry
qemu.hw.mainkeys=0
In /system/buildprop, save and reboot
The value was 1 previously.
Edit: This is also with having the Bulletproof ROM installed.
Edit 2: On further inspection, I can't seem to get it to work while also hiding the three dot menu on the legacy apps. Gah.
CL0SeY said:
I've managed to fix this by changing build.prop
Edit or add the entry
qemu.hw.mainkeys=0
In /system/buildprop, save and reboot
The value was 1 previously.
Edit: This is also with having the Bulletproof ROM installed.
Edit 2: On further inspection, I can't seem to get it to work while also hiding the three dot menu on the legacy apps. Gah.
Click to expand...
Click to collapse
OK so I have it working again as expected and I am not sure how I did it ... in the Play Store app I get the three dot menu up the top right and in other apps, the menu bar is missing. My build.prop file has no entry for qemu.hw.mainkeys anymore... so maybe it's something in my ROM? Currently Bulletproof 5.3.

Remove Black Bar But KEEP Menu Button In Apps That Support It.

So when I was using the Android Rev HD with the back button mod, I was able to remove the black bar using "qemu.hw.mainkeys" while still keeping the menu button on apps like Chrome that support it (NOT in the form of black bar). But since I flashed the GE Rom, qemu.hw.mainkeys=1 will disable the black bar but also remove the menu button in all apps that have it.
xGary said:
So when I was using the Android Rev HD with the back button mod, I was able to remove the black bar using "qemu.hw.mainkeys" while still keeping the menu button on apps like Chrome that support it (NOT in the form of black bar). But since I flashed the GE Rom, qemu.hw.mainkeys=1 will disable the black bar but also remove the menu button in all apps that have it.
Click to expand...
Click to collapse
install the xposed mods and enable menu overflow button.
works perfectly

[Q] Custom kernel/mod like Sense 4.2.2 version for menu bar removal

Not sure if it was discussed, but didn't find anything specific. If it was - then it wasn't focused too much on that.
I just rooted my HTC One 4.2.2 (Sense) and flashed a custom kernel (tried many of the most recent ones). I was very happy with various wake options as well as making HTC logo to behave as menu key. However I noticed a weird behavior of how custom kernels disable"3 dot menu" bar. They disable not just the bottom menu bar that appears only in some apps (i.e. Facebook), that are not fully designed according to Google guidelines. Menu buttons are disabled everywhere, in any app instead - even if they are placed according to guidelines (i.e. in Gmail app, at the top corner).
It's really annoying.. I don't want to hide all "good menu" buttons, I just want to hide the bottom line menu button. Exactly as it was made by HTC in 4.2.2 update.
Currently used method is just modifying /system/build.prop file by adding the line:
qemu.hw.mainkeys=1
Click to expand...
Click to collapse
Is there any other alternative fix? Is it there is no better alternative, because HTC didn't give latest kernel sources yet? I guess it's also not possible to revert to the stock kernel (without reseting the whole ROM)?..

[Q] AOKP nav bar buttons on stock

Is there any way to add extra buttons to the nav bar in stock (.283) like you can in AOKP, Carbon, etc.? I don't even need all of them, just the last app button. There are some apps that do this by adding a floating button (LAS), but I want it on my nav bar. UDN doesn't work right, and doesn't let me customize the buttons for some reason. The only other way I've found is to decompile the SystemUI, but I'd rather not do something that risky if there's an alternative. I was on Carbon for a long time and I really loved this feature, but I need the battery life that stock gives. I've found Xposed modules for everything else I'm used to, this is the only thing missing. Any help at all would be greatly appreciated.
SirVer said:
Is there any way to add extra buttons to the nav bar in stock (.283) like you can in AOKP, Carbon, etc.? I don't even need all of them, just the last app button. There are some apps that do this by adding a floating button (LAS), but I want it on my nav bar. UDN doesn't work right, and doesn't let me customize the buttons for some reason. The only other way I've found is to decompile the SystemUI, but I'd rather not do something that risky if there's an alternative. I was on Carbon for a long time and I really loved this feature, but I need the battery life that stock gives. I've found Xposed modules for everything else I'm used to, this is the only thing missing. Any help at all would be greatly appreciated.
Click to expand...
Click to collapse
use gravity box and add custom key to get it!
:good:
I've tried that, and it's not suitable for several reasons. First off, GB causes layout problems in the recents panel, making the small apps inaccessible. No matter what I toggle, it doesn't go away unless I disable GB. Also, the button appears to the extreme side; I was hoping to get it as a main nav button, like in the custom ROMs.
Looks like I might have to decompile after all. Oh, well. Thanks for your reply, though!
I used this xposed module on sock 4.3 for modify navbar buttons:
Xperia/AOSP NavBar Buttons
I don't know is it working on 4.4 or not. I am using Carbon at the moment.
SirVer said:
I've tried that, and it's not suitable for several reasons. First off, GB causes layout problems in the recents panel, making the small apps inaccessible. No matter what I toggle, it doesn't go away unless I disable GB.
Click to expand...
Click to collapse
This is a known bug in the latest GravityBox version. Download the ”no_translucent_recent” version from this post.
SirVer said:
Also, the button appears to the extreme side; I was hoping to get it as a main nav button, like in the custom ROMs.
Click to expand...
Click to collapse
You might not even need a separate button — with GravityBox you can assign actions to the long press of the “Recent Apps” button, and to the long press and double tap of “Back” and “Home” buttons. There is also the “Navigation Bar Ring” feature (you can add more actions than just Google Now).
@kanyazsombor
That module doesn't have a last app button. Thanks anyway!
@sigprof
Long press takes too long, and double tap on anything other than the recent key for a recent app feels... Wrong. Picky, I know, but still. I hadn't thought of using the nav bar ring targets, will try that as soon as I can, and the bug fix you mentioned. Thanks for your help!

Categories

Resources