Anyone using tabletui? Chrome missing tab switcher - OnePlus 7T Questions & Answers

The 7t switches to tabletui with wm density of 288 or lower. Unfortunately, chrome loses the tab switcher icon. Any ideas how to get it back? Tried a few chrome flags but no dice. Tried dropping to even lower densities to see if it'd show up but no dice.

Related

[Q] Density Changes and GingerBread

Is anyone having an issue with Gingerbread builds and the Facebook app's scaling with an LCD Density change?
No matter what version of GB I use (CM, Evervolv) I still get a problem with the Facebook app scaling correctly. I have enabled compatability mode in both Density Changer and Spare parts and still no luck... any ideas?
Bump. I'm having this problem as well.
I went the free route and changed the value in build.prop
Hoping there is a way to get FB to scale properly because I love running this at a density of 200.
Not sure what the problem is. I use CM 7 and run at a density of 165. I have never had a problem with the facebook app. I run with compatible mode OFF maybe try that???

[Q] CM 7 Nightly + LCD Density + New Market = Missing Apps?

Hey guys. I'm hoping that some others of you have found a fix for this or can at least try it and verify that it is universally an issue. I am using the newest nightly with the most recent GAPPS including market 3.0.27. With 240 lcd density, videos tab shows properly and all apps appear in market and in "My Apps". With any other lcd density, videos goes away, and many apps lose the install button and show incompatible on market.android.com. This happens if I change the density manually in build.prop or if I use lcd density for root. Also, I have compatibility mode turned off in spare parts.
Anyone else got this same thing?
Sounds normal, certain apps require a specific resolution and can't install otherwise.
I'd say that makes sense, but it didn't happen until 2.3.5 and market 3.0.27. The old market worked perfectly regardless of lcd density. Maybe the old market just didn't have any checks for resolution?

[Q] Google Music and 240 DPI

Hi all,
I notice when I change my DPI to 240, Google Music switches to its tablet interface. It's obviously awful on a phone. Is there any way to manually switch which interface Google Music is using?
Either that or somehow spoof a specific app into thinking the DPI setting is 320?
Thanks,
Giancarlo
MrBig0 said:
Hi all,
I notice when I change my DPI to 240, Google Music switches to its tablet interface. It's obviously awful on a phone. Is there any way to manually switch which interface Google Music is using?
Either that or somehow spoof a specific app into thinking the DPI setting is 320?
Thanks,
Giancarlo
Click to expand...
Click to collapse
I have noticed the same thing on my gs2 though I am switching from 240 to 182. Your post is the only I've found about the issue and it's driving me crazy. If anyone has ideas where to even look in the apk to adjust this it would be extremely appreciated.
I've noticed a few problems from it. Music Playerpro has some display issues, and the Youtube app crashes as soon as I open it. Both work fine with the native DPI.
If you switch to 241 dpi g-music works
You're a genius! Thanks!
Change to 240, open market, then freeze market updater so you don't lose the applications available, change to 241.

[Q] Changing LCD density and customizing the quick launch buttons

I have two questions for you guys about the G Pad 8.3:
1. The default LCD density on this thing is 320 which puts the UI into phone vs. tablet mode (no dual-pane view for Gmail, Email, etc.). The physical density is 273, though, which should activate the tablet (actually phablet) UI. I'm rooted and I've tried changing ro.sf.lcd_density through BuildProp Editor, but on each reboot it reverts to 320. Has anyone else successfully done this? What process (and LCD density value) did you use?
2. Is it possible to customize the quick launch buttons that are activated when you swipe up from the navigation bar? The default ones are Google, Voice Mate, and Quick Memo, and I'd like to change those last two if possible. I can't find anywhere in settings to change those, though.
Thanks much!
The screen density should be easily possible with apps like LCD Density, free on the Play Store (survives one reboot). Alternatively you can also change the dpi for every individual app, by installing the xposed module App Settings.
I don't know a way the quick launch shortcuts can be changed, although there are also apps in the Play Store as well that allow modifications to some extent.
True, I changed the density in build.prop, with editor, restart the tablet has gone a bit 'in bootloop, I rebooted again and everything is restored.
I tried to put 240.
Palux said:
True, I changed the density in build.prop, with editor, restart the tablet has gone a bit 'in bootloop, I rebooted again and everything is restored.
I tried to put 240.
Click to expand...
Click to collapse
Yeah, this tablet seems pretty resistant to changing the LCD density for some reason. Thanks for confirming!

Issue with dialer on higher custom dpi

Hi Guys, so I've increased the dpi to custom under developer settings to 581. Everything seems to work great except for touch position on the dialer and it's pretty irritating. Anyone knows a solution to this or to selectively reduce the dpi on tbe dialer app? I'm not rooted. Look at the screenshot of the issue. Thanks!
I use 589, and no issues, but with 600, the notifications panel becomes very narrow, but no issues with anything else
i use 480 w lowered font size and "fineprint" font.... everything works perfect
winol said:
I use 589, and no issues, but with 600, the notifications panel becomes very narrow, but no issues with anything else
Click to expand...
Click to collapse
Tried 589 and same issue. Can you confirm you don't have the issue on your dialer? Weird why this would be.
I just double checked, at 589, the dialer is normal, but, I have the screen resolution at wqhd+, fhd gives me some troubles in the zone of the nav bar, and I say zone because I hide the nav bar, gestures work ok, but, buttons appearing there become unresponsive, the same for the bottom row of the keyboard
winol said:
I just double checked, at 589, the dialer is normal, but, I have the screen resolution at wqhd+, fhd gives me some troubles in the zone of the nav bar, and I say zone because I hide the nav bar, gestures work ok, but, buttons appearing there become unresponsive, the same for the bottom row of the keyboard
Click to expand...
Click to collapse
For some reason I still have the issue in the OP screenshot. I've resorted to 520 now with QHD+, things are slightly better on the dialer but still largely the same.

Categories

Resources