What's your choice and why ?
I like Tablet mode with the buttons, signal, battery and notifications being smallish at the bottom of the screen. Have tried the Pie feature but not really gotten the hang of it.
Sent from my Galaxy Nexus using Tapatalk 2
I use pie 80% of the time. Phone mode for the rest.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^
I have never used the PIE Control, also I have never used tablet or phtablet mode on my Nexus (Never).
But I really like the Tablet UI.
tablet mode because you still get 90% of the screen and still have your status bar and nav bar
pie is a pain to swipe all day especially if you multi task a lot also if your phone is on silent while browsing how would you know of your notifications ?
for me pie is just a feature to show to iphone users
I like tablet but the screen is small for this. so I use pie
I use phablet. Don't like the waste of screen real-estate on phone mode. I have a few apps setup in tablet mode gmail and some others (can't remember which ones). I find pie a little too hard to use all the time although I do set it up for gaming. I am having an issue at the moment where I'm setting to the bottom of the screen but it reverts back whenever I leave and re-enter the game.
Pie. I can't use anything else my screen size seems so small. If my custom ruin doesn't include pie I switch to lmt as quick as I can x)
Sent from my Galaxy Nexus using xda premium
Phone mode. I have tried all the other modes but just didnt see the point. This is a phone. As far as pie controls, I just found it faster to tap a button than to swipe around for the button you want.
I use PIE mostly to reduce screen burn-in.
The most responsive ROMs to include it have been PA and CarbonROM - even though it doesn't show up, it's still active/usable. On CM if it doesn't show it doesn't work, which is much like LMT.
I used LMT on AOKP before I noticed they were being built into ROMs. The best thing about it is the longpress options, among other things. The worst part is that if it gets kicked out of memory, and without any backup nav options enabled, you're stuck with a battery pull on your hands. I was hoping the built-in ones could prevent this.
I stick with Phone mode. I'm not a fan of how small and squished everything looks on Phablet/Tablet modes and while I think PIE looks awesome it just isn't as simple and quick as just using the stock navigation bar for me. That's just my 2 cents though.
i choose pie, because screen looks more simple and larger
Pie all the way.
I love pie because after I disable and hide my status bar ( http://forum.xda-developers.com/showthread.php?p=37466852 ) my phone looks super slick and clean. Plus no one but me can really use it. I also like to use Nova Launcher with gestures and nothing at all on the single homescreen. I even have enough apps hidden to only have two full app pages, at a lower density than normal, but larger icons. I just love a good clean looking phone and pie is one of the easiest steps to take to get there.
Phone mode with pie coming into play only during certain games while using expanded desktop mode.
Sent from my Nexus 7 using xda premium
Moop99 said:
I stick with Phone mode. I'm not a fan of how small and squished everything looks on Phablet/Tablet modes and while I think PIE looks awesome it just isn't as simple and quick as just using the stock navigation bar for me. That's just my 2 cents though.
Click to expand...
Click to collapse
same here. i love the idea of Pie, but until i can get it to come up 100% of the time, its a no go for me. right now it works about 80-90% of the time.
+1 for Phone mode since my phone isn't big enough to be a Tablet and I don't use Pie.
PHONE MODE, yes because with tablet mode everthing will be very tight, yes we can lower the dpi but it will become very small. Phabet is ugly too. PiE was fun but made my navigation slower.
My setup with PA, 280dpi screen space, 240 dpi lockscreen, 240/720p launcher.
Sent from my Galaxy Nexus using Tapatalk 2
Tablet mode: clean look, more screen space, and not as annoying to use as PIE.
Has anyone had any success with lockscreen apps, particularly those which allow customisation of notifications.
I've long been a fan of notific and acdisplay on my nexus 5, but on this phone there are a mix of problems. Some or all of these happen:
music player controls aren't available on the lockscreen (rdio/tunein radio/poweramp/ etc.)
the custom notifications don't appear
the alarm doesn't appear on the lockscreen (gentle alarm)
Or is this just the way LG has customised the OS? It's also mildly infuriating that you can't double-tap to open a notification (you need to either expand it first or swipe separately)
Interesting no one has commented about this since.
I find it mildly annoying after getting accustomed on the z3 and n6, double tapping a notification from the lock screen to open it. The g4 doesn't and it requires yo u to swipe unlock.
Unless there is a setting or another method I'm missing?
The G3 4.x recents menu was perfect. The Google style recents is basically pointless. It's so cluttered, hard to find, and takes longer than just going into the app drawer. Is there any way to change it? I know it was possible to switch to Android Lolipop recents on other versions of Android.
Recently perhaps? But it requires root and you can't disable logd!
Thanks. I have no clue what logd is, but recently doesn't seem to be working. It sounds like a classic style recents, which is an improvement. However, LG had it perfect with the ability to zoom in like a more classic style, or zoom out to have 12 apps fully displayed. I believe HTC had a similar recents, or at least it was baked into a rom on a friends phone.
Softkey fade, I used this on the Nexus 6 and loved it. The soft keys faded out after a user set time period, and then reappeared after you touched the screen.
You probably won't get that specific app until/unless Xposed works on Nougat. Until then, you might try one of the immersive mode apps to selectively hide them.
I enabled full immersive mode to help prevent screen burn-in and now I'm finding that a couple of apps, namely Spotify, won't utilize the full screen area and keeps a huge black bar on the top and bottom of the app. On my LG V30, there was an option to force apps to utilize the full screen and this worked perfectly with Spotify. However, I'm not seeing this option on my 2 XL.
Does anyone know how to force certain apps into full screen on the 2 XL?
Same problem here, would love a fix for this so I can use the whole screen
Accessibility has a magnification option when triple tapping the screen. It zooms in a bit too far but it does go full screen. I wonder if there is a way to lower the zoom amount somewhere.
Sent from my Pixel 2 XL using Tapatalk
The LG V30 handles this really well. Little button on nav bar to switch between full screen and regular and the setting sticks per app.
This seems like and option but I haven't tried it out yet myself.
https://play.google.com/store/apps/details?id=com.gmd.immersive
SWBgHz said:
The LG V30 handles this really well. Little button on nav bar to switch between full screen and regular and the setting sticks per app.
This seems like and option but I haven't tried it out yet myself.
https://play.google.com/store/apps/details?id=com.gmd.immersive
Click to expand...
Click to collapse
Yeah, I pulled my V30 back off the shelf for a bit yesterday and it made me envious of how well it handles immersive mode, compared to the 2 XL. Sadly, yesterday, I started to experience the issue that others have mentioned with immersive mode enabled on the 2 XL, which is that occasionally the screen won't wake and the only way to fix it is with a hard reboot (hold power for 10 seconds). It happened to me 3 times yesterday. So now I'm realizing that in order to keep my phone fully functional and reliable, I have to disable immersive mode.
On the plus side, my squeeze for assistant feature will work again but now I'll be putting myself at risk for screen burn-in. So anything I can do to hide the nav bar whenever possible will be very welcomed. I'll give that GMD Full Screen app a try. No matter what I'm going to use Nav Bar Apps to change the color of the nav bar based on the app being used. This will allow me to prevent the black nav bar from showing up, minimizing the risk of screen burn-in.
Maybe set nav to 1 ?cuz apk need to see if there is a keyboard
Icyou said:
Maybe set nav to 1 ?cuz apk need to see if there is a keyboard
Click to expand...
Click to collapse
How do I do that? I'm familiar with ABD/fastboot commands but not sure what the command is to change nav to 1.
Removing the navbar doesn't force apps into fullscreen
I like that my Note 8 gives you the option to force it in apps that don't support it and it remembers that decision
imtjnotu said:
I like that my Note 8 gives you the option to force it in apps that don't support it and it remembers that decision
Click to expand...
Click to collapse
That is what V30 does, nice thing with V30 is you have a 4th button on nav bar that is a toggle between immersive on and off and however you set it 'sticks' for that app for next time. So it makes it very easy to setup/use. Frankly, this should be default behavior in Android and the fact that it isn't just wreaks of Google stubbornness we see where they just won't make and obvious and necessary changes because their original thinking is different than what people want.
Guys you will have to wait for custom roms to come out. They (at least some) will more then likely have features like this. The pixel is stock android pretty bare bones when it comes to things like that. Google isnt going to put a feature like that in (for some reason) that wouldnt be utilized by other phones. Now i know what your thinking. "But the pixel does have some "pixel specific software features" And this is true. But hey its Google it only took them 13 OS iterations to give us a proper ****ing battery % indicator.
sn0warmy said:
Yeah, I pulled my V30 back off the shelf for a bit yesterday and it made me envious of how well it handles immersive mode, compared to the 2 XL. Sadly, yesterday, I started to experience the issue that others have mentioned with immersive mode enabled on the 2 XL, which is that occasionally the screen won't wake and the only way to fix it is with a hard reboot (hold power for 10 seconds). It happened to me 3 times yesterday. So now I'm realizing that in order to keep my phone fully functional and reliable, I have to disable immersive mode.
On the plus side, my squeeze for assistant feature will work again but now I'll be putting myself at risk for screen burn-in. So anything I can do to hide the nav bar whenever possible will be very welcomed. I'll give that GMD Full Screen app a try. No matter what I'm going to use Nav Bar Apps to change the color of the nav bar based on the app being used. This will allow me to prevent the black nav bar from showing up, minimizing the risk of screen burn-in.
Click to expand...
Click to collapse
I haven't experienced this issue. I am using this command to enable immersive mode however in order avoid issues previously reported - battery drain, performance problems and delay waking up the screen: settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
sn0warmy said:
Yeah, I pulled my V30 back off the shelf for a bit yesterday and it made me envious of how well it handles immersive mode, compared to the 2 XL. Sadly, yesterday, I started to experience the issue that others have mentioned with immersive mode enabled on the 2 XL, which is that occasionally the screen won't wake and the only way to fix it is with a hard reboot (hold power for 10 seconds). It happened to me 3 times yesterday. So now I'm realizing that in order to keep my phone fully functional and reliable, I have to disable immersive mode.
On the plus side, my squeeze for assistant feature will work again but now I'll be putting myself at risk for screen burn-in. So anything I can do to hide the nav bar whenever possible will be very welcomed. I'll give that GMD Full Screen app a try. No matter what I'm going to use Nav Bar Apps to change the color of the nav bar based on the app being used. This will allow me to prevent the black nav bar from showing up, minimizing the risk of screen burn-in.
Click to expand...
Click to collapse
Try out the app "Navbar Apps" in the play store. What it does is creates a matching color for the navbar of whatever app you're in simply lar to how the status bar works by default in apps. Some aren't accurate but you can manually set colors for apps too. Most are pretty spot on.
This works perfect to help with burn-in. The reason being is that people have it backwards, the navbar is the only thing not burning in due to black on Oled meaning the pixels are off. So by having a black navbar on all the time you're actually seeing burn-in from the entire rest of the screen with the navbar being darker since it's not active. Using the app I recommended above will basically even out the screen so it's all being used the same amount, thus reducing any noticable burn-in. It also looks really cool and has a bunch of great features.
Icyou said:
Maybe set nav to 1 ?cuz apk need to see if there is a keyboard
Click to expand...
Click to collapse
I too would like to know how to do this. Had it on my S8+ and loved it. Someone over there made an rro theme that removed it
Nephilim said:
Try out the app "Navbar Apps" in the play store. What it does is creates a matching color for the navbar of whatever app you're in simply lar to how the status bar works by default in apps. Some aren't accurate but you can manually set colors for apps too. Most are pretty spot on.
This works perfect to help with burn-in. The reason being is that people have it backwards, the navbar is the only thing not burning in due to black on Oled meaning the pixels are off. So by having a black navbar on all the time you're actually seeing burn-in from the entire rest of the screen with the navbar being darker since it's not active. Using the app I recommended above will basically even out the screen so it's all being used the same amount, thus reducing any noticable burn-in. It also looks really cool and has a bunch of great features.
Click to expand...
Click to collapse
Yeah, this option makes complete sense, actually. I couldn't understand why it would be the pixels that are turned off the most (with the black nav bar) that would cause the burn-in. So your explanation helps clear that up for me. Right before leaving for a 5 day trip in Costa Rica, I disabled full immersive mode and installed Nav Bar Apps. I spent my downtime on the plane to get all my app nav bar custom colors setup to my liking. Now all my apps have color variations ranging anywhere from red, to blue, to green, orange, yellow, white and everything in between. Everything EXCEPT black. I used the phone the entire trip for travel guidance, music, watching Netflix/Hulu, taking pictures etc.. All with absolutely no black nav bar. I just got home last night, checked the phone this morning for burn-in and there's nothing.
It's sad that this screen burns in so quickly with the black nav bar, but to me its become such a non-issue since it's so easy to avoid. The ideal setup would be to fully disable the nav bar and use pie controls instead but a ROM isn't yet available to do this. I've read that Custom Navigation bar is another solid option as it allows you to hide the nav bar by app. However, I'm not sure it allows you to change the nav bar colors and I'm fairly certain it still disables the squeeze for assistant feature because it's still technically using immersive mode in some form.
Pecata said:
I haven't experienced this issue. I am using this command to enable immersive mode however in order avoid issues previously reported - battery drain, performance problems and delay waking up the screen: settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
Click to expand...
Click to collapse
Can you elaborate on this a bit?
I tried that command but it didn't do anything. So I tried the same command with a different app, example...
settings put global policy_control immersive.navigation=apps,-com.google.android.youtube
And what I noticed is that it put the full nav bar immersive mode system wide on everything EXCEPT Youtube. This was the opposite of what I anticipated would happen. Now I'm thinking the "-" means I'm telling the system to make everything immersive except the app I specified in the above command. Is this correct? If so, the only benefit I see to using this method is to pick and choose certain apps to prevent the immersive nav bar.
Perhaps I'm misunderstanding?
sn0warmy said:
Yeah, this option makes complete sense, actually. I couldn't understand why it would be the pixels that are turned off the most (with the black nav bar) that would cause the burn-in. So your explanation helps clear that up for me. Right before leaving for a 5 day trip in Costa Rica, I disabled full immersive mode and installed Nav Bar Apps. I spent my downtime on the plane to get all my app nav bar custom colors setup to my liking. Now all my apps have color variations ranging anywhere from red, to blue, to green, orange, yellow, white and everything in between. Everything EXCEPT black. I used the phone the entire trip for travel guidance, music, watching Netflix/Hulu, taking pictures etc.. All with absolutely no black nav bar. I just got home last night, checked the phone this morning for burn-in and there's nothing.
It's sad that this screen burns in so quickly with the black nav bar, but to me its become such a non-issue since it's so easy to avoid. The ideal setup would be to fully disable the nav bar and use pie controls instead but a ROM isn't yet available to do this. I've read that Custom Navigation bar is another solid option as it allows you to hide the nav bar by app. However, I'm not sure it allows you to change the nav bar colors and I'm fairly certain it still disables the squeeze for assistant feature because it's still technically using immersive mode in some form.
Click to expand...
Click to collapse
Glad you like it. I'm enjoying it a lot. It makes you feel like you're actually using the whole screen instead of having the ugly cut off black bottom with nav buttons.
Nephilim said:
Glad you like it. I'm enjoying it a lot. It makes you feel like you're actually using the whole screen instead of having the ugly cut off black bottom with nav buttons.
Click to expand...
Click to collapse
Thanks for the heads up on this. Back in the day an Xposed module was needed for this and there was a spreadsheet going on matching apps colors that were detected wrong. The last good PA ROM had it baked in as well. Though I wonder how much longer this will be on the Play Store with Google set on removing anything that touches Accessibility Services that aren't related to a disability.
sn0warmy said:
Can you elaborate on this a bit?
I tried that command but it didn't do anything. So I tried the same command with a different app, example...
settings put global policy_control immersive.navigation=apps,-com.google.android.youtube
And what I noticed is that it put the full nav bar immersive mode system wide on everything EXCEPT Youtube. This was the opposite of what I anticipated would happen. Now I'm thinking the "-" means I'm telling the system to make everything immersive except the app I specified in the above command. Is this correct? If so, the only benefit I see to using this method is to pick and choose certain apps to prevent the immersive nav bar.
Perhaps I'm misunderstanding?
Click to expand...
Click to collapse
So I spent some more time fiddling with this and tried testing the same command but without the "-". So the new command is:
settings put global policy_control immersive.navigation=apps,com.google.android.youtube
What I noticed is that the nav bar immersive setting still seems to be system wide. However, squeeze for assistant is still working with the screen off. This has not been the case with any other immersive commands I've tried. So this definitely handles it a little differently. I'll test this for a while to see if I have any issues with screen not waking from sleep.
AndrasLOHF said:
Thanks for the heads up on this. Back in the day an Xposed module was needed for this and there was a spreadsheet going on matching apps colors that were detected wrong. The last good PA ROM had it baked in as well. Though I wonder how much longer this will be on the Play Store with Google set on removing anything that touches Accessibility Services that aren't related to a disability.
Click to expand...
Click to collapse
I couldn't care less if things get removed from play store, we can still sideload and I'm sure someone as useful as Navbar Apps would just move to XDA Labs if it got removed.