Moto Z2 Force Must-Do's - Moto Z2 Force Guides, News, & Discussion

Moto Z2 Force Must-Do's
1) Install a glass screen protector
Immediately. Unless you like scratches on your screen, install a tempered glass screen protector the first minute you take the phone out of the box. Scratches will appear magically on the stock screen within the first day unless you do this. I suggest a screen protector that is tempered, no thicker than .4 mm, and has a quality oleophobic coating. Cheaper no-name screen protectors have an oleophobic coating that will wear off in a month, have really high reflections, and adhesion glue that doesn't stick evenly.
2) Speed up animations
-Open settings > About phone > tap "Build number" 7 times
-Settings > Developer options > scroll down and change all 3 animation speeds to .5x
3) Change DPI
Just below the animations speed adjustment in developer options is the ability to manually adjust the DPI. I find that even the "small" stock setting isn't right.
-Settings > Developer options > scroll down and change "Smallest width" to 460
4) Disable wireless charging notification
I love the Motorola phones, but the wireless charging notification is beyond frustrating. If you set the phone on a wireless charger you get an animation that shows you are now charging, followed by another animation that tells you how much juice is left in your main battery and your battery pack (if you have one). Looks cool, but locks the phone up for like 10 seconds. If you set it on the charger and then realize you needed to quickly send another text or unlock the phone, you have to wait until all that animation is done first. This has no effect on the phones ability to charge.
Settings > Apps > 3 dots in the top right > Show system > scroll down to "Inductive charger" and select it > click Disable
5) Disable bloat
This one will be up to you with what you want to disable. A lot of the stuff on this phone that is preinstalled can actually be uninstalled, which is good. The rest you have to just "disable". I would recommend you immediately disable the Lookout Security app as it is a trash app which hogs a ton of resources. The rest is up to you. To disable apps it's the same procedure as disabling the wireless charging notification:
Settings > Apps > choose the apps you would like to disable

I have my width to 480 because some apps at that point give a tablet UI which looks a lot better. Like Now for Reddit.
Sent from my Moto Z (2) using Tapatalk

Tidbits said:
I have my width to 480 because some apps at that point give a tablet UI which looks a lot better. Like Now for Reddit.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
I'm at 590. 600 will force tablet mode, but I don't really like it. After having a z3 compact for years I got used to using a smaller dpi to fit more onto a comparatively smaller screen. I really appreciate that I don't have to have root/xposed/small apps, or edit the buildprop to change dpi.
Also, I personally went with an illumiaqua shield over the typical tempered glass. I prefer the feel of plastic skins like this, skinomi or zagg back in the day.

seh6183 said:
2) Speed up animations
-Open settings > About phone > tap "Build number" 7 times
-Settings > Developer options > scroll down and change all 3 animation speeds to .5x
Click to expand...
Click to collapse
Changing it to .5x is actually slowing down animations. What is your reasoning for this?

xamindar said:
Changing it to .5x is actually slowing down animations. What is your reasoning for this?
Click to expand...
Click to collapse
100 x .5 = 50

No... The lower the number the faster the animation.

XE-Cherokee said:
No... The lower the number the faster the animation.
Click to expand...
Click to collapse
Ahh, gotcha.

So, now that we've got Root and a working TWRP, what's everyone doing for cleanup and tweaks?
Motorola doesn't add much in the way of garbage, but there are a few apps I might drop like Moto Update.
Maybe an audio mod and theming for additions.

Viper4Android FX! I'm using it now
---------- Post added at 06:05 AM ---------- Previous post was at 06:04 AM ----------
I'm also using Substratum. If you delete the OEM folder (make sure to make a backup just in case you ever need it again), most of the themes work with little to no error.

sabrdawg said:
Viper4Android FX! I'm using it now
---------- Post added at 06:05 AM ---------- Previous post was at 06:04 AM ----------
I'm also using Substratum. If you delete the OEM folder (make sure to make a backup just in case you ever need it again), most of the themes work with little to no error.
Click to expand...
Click to collapse
The whole folder?

vibraniumdroid said:
The whole folder?
Click to expand...
Click to collapse
Yes

sabrdawg said:
Viper4Android FX! I'm using it now
---------- Post added at 06:05 AM ---------- Previous post was at 06:04 AM ----------
I'm also using Substratum. If you delete the OEM folder (make sure to make a backup just in case you ever need it again), most of the themes work with little to no error.
Click to expand...
Click to collapse
So wait you just deleted the entire system/OEM folder, including all the apps? Or are you deleting the OEM folder in the susbtratum folder?

/oem I think you'll see 6 items delete them all

sabrdawg said:
Yes
Click to expand...
Click to collapse
thanks it worked

joemossjr said:
/oem I think you'll see 6 items delete them all
Click to expand...
Click to collapse
Do I need to be rooted for this? for Susbtratum to work? (not a newbie here just not familiar with Susbtratum).

TMobile or Sprint?

joemossjr said:
/oem I think you'll see 6 items delete them all
Click to expand...
Click to collapse
I'm unable to make any changes to that folder. Magisk says I'm rooted, all my other apps work (TB, Substratum, Root Explorer, etc) on T-Mobile but it's not letting me even edit anything in this OEM folder when though it SAYS r/w. Any suggestions?

Yup. Magisk doesn't allow you access to oem. You have to use super su.

I used TWRP to delete the /OEM folder and substratum still gives me issues with trying g to apply Pitch Black or Swift Black themes. Anyone know a working dark or black substratum theme for now?

LGtMgG2t said:
I used TWRP to delete the /OEM folder and substratum still gives me issues with trying g to apply Pitch Black or Swift Black themes. Anyone know a working dark or black substratum theme for now?
Click to expand...
Click to collapse
Any of those 3 work. I'm using one now.

Related

LCD Density - keeping settings through reboots

Anyone know why the screen density you set (either using LCD Density or modifying build.prop directly) doesn't keep when rebooting? TIA
What do you think the optimal density is and does it make a noticeable difference?
I like 140 - makes the screen look very nice and smooth. All apps seem to run fine, with the "stretch apps" fix.
ethanwinkley said:
I like 140 - makes the screen look very nice and smooth. All apps seem to run fine, with the "stretch apps" fix.
Click to expand...
Click to collapse
what "stretch apps" fix do you mean? are you talking about messing with the manifest file the .apk file?
post pics please!
Sorry, I couldn't remember before... spare parts is the name of the app you need to install. Then, go in there and set Compatibility Mode disabled - reboot. This stretches apps that run in less than full screen.
ethanwinkley said:
Sorry, I couldn't remember before... spare parts is the name of the app you need to install. Then, go in there and set Compatibility Mode disabled - reboot. This stretches apps that run in less than full screen.
Click to expand...
Click to collapse
Have had that running. Does not work on all apps though. I thought maybe I missed something new. Thanks though.
Sent from my HTC HD2 using XDA Premium App

[Q] No Active Display after changing LCD Density

I've been applying assorted mods and V6 Supercharging lately just to see what all I can do before I break stuff. Well, I broke Active Display and I wasn't sure what did it. I restored back to stock 4.4 and noticed that Active Display breaks when I change the LCD density lower than 320 (I'm using 280). After the phone goes to sleep a few times, it wacks out and won't let me unlock it. Shortly after it soft reboots and Active Display no longer works.
Has anyone else noticed this problem and were you able to make Active Display work with the lower density?
d3athsd00r said:
I've been applying assorted mods and V6 Supercharging lately just to see what all I can do before I break stuff. Well, I broke Active Display and I wasn't sure what did it. I restored back to stock 4.4 and noticed that Active Display breaks when I change the LCD density lower than 320 (I'm using 280). After the phone goes to sleep a few times, it wacks out and won't let me unlock it. Shortly after it soft reboots and Active Display no longer works.
Has anyone else noticed this problem and were you able to make Active Display work with the lower density?
Click to expand...
Click to collapse
The thing with changing DPI is it makes the active display go off center, and thus crash sometimes. Change back the DPI of Active Display only to stock 320 while keeping the rest of the system on 280.
anirudh412 said:
The thing with changing DPI is it makes the active display go off center, and thus crash sometimes. Change back the DPI of Active Display only to stock 320 while keeping the rest of the system on 280.
Click to expand...
Click to collapse
I didn't know you could do that. I'm on AT&T 4.4, how would I change just AD to 320? I only know how to change system through build.prop.
I found that if you change certain apps that you have set up to show notifications in active display, if you adjust the DPI you'll lose the pictures for the notification. For example, change the Messaging app to something other than 320. Poof, No more pictures.
---------- Post added at 01:02 AM ---------- Previous post was at 01:01 AM ----------
d3athsd00r said:
I didn't know you could do that. I'm on AT&T 4.4, how would I change just AD to 320? I only know how to change system through build.prop.
Click to expand...
Click to collapse
Used Xposed module. App Settings.
natezire71 said:
I found that if you change certain apps that you have set up to show notifications in active display, if you adjust the DPI you'll lose the pictures for the notification. For example, change the Messaging app to something other than 320. Poof, No more pictures.
---------- Post added at 01:02 AM ---------- Previous post was at 01:01 AM ----------
Used Xposed module. App Settings.
Click to expand...
Click to collapse
Thanks. I must have missed that one.
d3athsd00r said:
Thanks. I must have missed that one.
Click to expand...
Click to collapse
Let me know if that works. I've been wanting to change the stem DPI also
natezire71 said:
Let me know if that works. I've been wanting to change the stem DPI also
Click to expand...
Click to collapse
Will do. I might have to take a break from work to run out to my car and try this.
d3athsd00r said:
Will do. I might have to take a break from work to run out to my car and try this.
Click to expand...
Click to collapse
Man, it's late for work. You should take a break
natezire71 said:
Man, it's late for work. You should take a break
Click to expand...
Click to collapse
I work night shift, and we can't have our phones in the building. :sad:
natezire71 said:
Man, it's late for work. You should take a break
Click to expand...
Click to collapse
So something is up with my settings. When I click on "security", settings crashes. Looks like I'm going to have to wipe
natezire71 said:
Let me know if that works. I've been wanting to change the stem DPI also
Click to expand...
Click to collapse
d3athsd00r said:
Will do. I might have to take a break from work to run out to my car and try this.
Click to expand...
Click to collapse
Download the newest version from here
http://forum.xda-developers.com/showthread.php?t=2554049
While in recovery, change Active Display to 320 in App Settings module, build.prop to 280 (or whatever number you desire). Reboot, profit
Also, if anyone wants tablet mode for certain apps (I use mine on GMail, go to App Settings module, select the particular app, change DPI to around 220, and DP to 800X1280)
So I finally got around to refreshing my phone. 280 in build.prop with 320 set for active display makes the phone right where I want it with resolution and size
My new favorite phone of all time. And I don't even have AOKP, and never will
Sent from my XT1058 using XDA Premium 4 mobile app
d3athsd00r said:
So I finally got around to refreshing my phone. 280 in build.prop with 320 set for active display makes the phone right where I want it with resolution and size
My new favorite phone of all time. And I don't even have AOKP, and never will
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you please explain how u did it? I'm lost.. Thanks!
varun.gid said:
Can you please explain how u did it? I'm lost.. Thanks!
Click to expand...
Click to collapse
You have to install Xposed and the module App Settings. Once you've rebooted and Xposed is active, go into App Settings and set the DPI on Active Display to 320. Then set your DPI in build.prop to whatever you want. Reboot and enjoy.
Sent from my XT1058 using XDA Premium 4 mobile app

DPI changes

So I am hoping I am not the only one that thanks the stock navigation bar is way too big. On my Oneplus One I had it set pretty small, but it made the phone look better, just didn't make everything look so big.
My question is has anyone changed the DPI on the G4, and if so, what did you use to do that?
I am rooted and have flashed xTreme v1.0.
Thanks.
vng10 said:
So I am hoping I am not the only one that thanks the stock navigation bar is way too big. On my Oneplus One I had it set pretty small, but it made the phone look better, just didn't make everything look so big.
My question is has anyone changed the DPI on the G4, and if so, what did you use to do that?
I am rooted and have flashed xTreme v1.0.
Thanks.
Click to expand...
Click to collapse
You just need an app like build.prop editor, ES File Explorer,or Root Explorer to find and edit text within the build.prop file. It is in the "system" folder. Once you've accessed the build.prop look for ro.sf.lcd_density and change the value from 640 to whatever you like and restart the phone. I've heard that if you go below 540 the camera app and some other apps will not work properly. I set mine to 560. Also, if you have a quickcircle case, that quickcircle app will no longer be aligned correctly as it's set for 640 dpi. Once we get xposed running or if you have a rom that allow for per-app dpi settings, you would be able to easily fix this issue.
Hopefully this helps.
willmayah said:
You just need an app like build.prop editor, ES File Explorer,or Root Explorer to find and edit text within the build.prop file. It is in the "system" folder. Once you've accessed the build.prop look for ro.sf.lcd_density and change the value from 640 to whatever you like and restart the phone. I've heard that if you go below 540 the camera app and some other apps will not work properly. I set mine to 560. Also, if you have a quickcircle case, that quickcircle app will no longer be aligned correctly as it's set for 640 dpi. Once we get xposed running or if you have a rom that allow for per-app dpi settings, you would be able to easily fix this issue.
Hopefully this helps.
Click to expand...
Click to collapse
Did you have any bootloop issues?
vng10 said:
Did you have any bootloop issues?
Click to expand...
Click to collapse
I didn't. Never had any boot loop issues throughout the whole rooting process. I have an ATT H810 model however. Just lurking on the T-Mobile page to see what development comes out now that you all have unlocked bootloader.
willmayah said:
I didn't. Never had any boot loop issues throughout the whole rooting process. I have an ATT H810 model however. Just lurking on the T-Mobile page to see what development comes out now that you all have unlocked bootloader.
Click to expand...
Click to collapse
Okay. THanks. Yeah I tried editing the build.prop and when it rebooted, it was optimizing 32 apps and when it was finishing up, it would reboot. So I am on my backup. Ill see if there are any other options or fixes to this. I just hate how big everything looks at the default.
I used an app someone in one of the G4 threads mentioned called DPI Density changer. I lowered it to 550 seems pretty good to me.
If you're unhappy with the NavBar, you can give Swipe Navigation [Root] a try. It's GREAT on the G4, the Nexus 6 and other onScreen Nav based devices. I have it set with the NavBar completely hidden and it has an outstanding swipe gesture setup to replace the NavBar buttons. It's made every app take full advantage of the display without any loss due to the NavBar sucking up some space.
Build Prop Editor on the play store works flawlessly. The DPI option is conveniently located in the side menu too. Running 540 with no issues, though the circle case will still be misaligned.
vng10 said:
Okay. THanks. Yeah I tried editing the build.prop and when it rebooted, it was optimizing 32 apps and when it was finishing up, it would reboot. So I am on my backup. Ill see if there are any other options or fixes to this. I just hate how big everything looks at the default.
Click to expand...
Click to collapse
Build prop created boot loop for me too I switched to kernel audiutor from play store and no more boot loops. Changed dpi to 530 with no issues.
Sent from my LG-H811 using Tapatalk
Dpi density changer worked for me. Nav bar is still a little big for me at 540 but its manageable. Thanks for all the help!
Sent from my LG-H811 using Tapatalk

LCD / DPI Scaling Stock ROM Rooted?

I can't get the toolkit from the other thread to recognize my device worth crap. Rooted/TWRP'd, Xposed all working fine going the manual way. I would really like to scale things down on this large beautiful screen to gain more content space though. Anyone have any ideas?
purplepenguin said:
I can't get the toolkit from the other thread to recognize my device worth crap. Rooted/TWRP'd, Xposed all working fine going the manual way. I would really like to scale things down on this large beautiful screen to gain more content space though. Anyone have any ideas?
Click to expand...
Click to collapse
You can always edit the DPI in build.prop but that will likely cause scaling issues. It does with the OnePlus 3. I imagine it would be the same with the 3T. If you want to just look for ro.sf.lcd_density. I'm pretty sure stock is set to 480, just set it to something lower like 400. There is also the per app DPI changer for xposed. You would have to set each app manually but you could set the ones that didn't work properly back to the stock setting.
Sent from my OnePlus3T using XDA Labs
Build.prop is the best method. Make sure to create a backup before editing though.
If you're rooted I recommend Le DPI Changer from the Play Store. Make sure you tick the "Use Shell WM for setting DPI". I have mine set to 400 and love it. There are also adb commands to achieve this without root but not sure if they'll work on the 1+3t
I use Easy DPI Changer from playstore and it works perfect...
are you guys not seeing the user interface glitches that I'm seeing?
kramer987 said:
are you guys not seeing the user interface glitches that I'm seeing?
Click to expand...
Click to collapse
I am seeing some glitches like quick settings mis alignment...
thesm4rt1 said:
If you're rooted I recommend Le DPI Changer from the Play Store. Make sure you tick the "Use Shell WM for setting DPI". I have mine set to 400 and love it. There are also adb commands to achieve this without root but not sure if they'll work on the 1+3t
Click to expand...
Click to collapse
Le DPI Changer failed on all normal settings minus the Build.Prop edit option. Confirmed that build.prop does work though!!! But same issue for me with the quick settings on OOS being misaligned, a bit shifted left. It's actually quite a bit left at 400DPI.
Any fix to this?
yep also getting the left shift. long press power you'll see the power off and reboot icons are messed up too. but that's about all I see. small price to pay. i don't mind it
Texdroider from play store ..??..
purplepenguin said:
Le DPI Changer failed on all normal settings minus the Build.Prop edit option. Confirmed that build.prop does work though!!! But same issue for me with the quick settings on OOS being misaligned, a bit shifted left. It's actually quite a bit left at 400DPI.
Any fix to this?
Click to expand...
Click to collapse
Worked for me with "Use Shell WM for setting DPI" toggled but yes, shifts the quicksettings to the left here as well. Android N-ify Xposed module doesn't change the quicksettings either so I assume they've done something to add the quick toggles..
cultofluna said:
Texdroider from play store ..??..
Click to expand...
Click to collapse
Texxdroider didn't work for me on the OnePLus 3t (worked on every other previous phone though).
kramer987 said:
yep also getting the left shift. long press power you'll see the power off and reboot icons are messed up too. but that's about all I see. small price to pay. i don't mind it
Click to expand...
Click to collapse
Power and reboot look fine for me at 400 DPI. Quick settings still on the left. Any fix?
Sent from my ONEPLUS A3000 using Tapatalk
I don't want my things to shift ?
Gonna hold off and just have everything smaller but desktop still painful lol
purplepenguin said:
Le DPI Changer failed on all normal settings minus the Build.Prop edit option. Confirmed that build.prop does work though!!! But same issue for me with the quick settings on OOS being misaligned, a bit shifted left. It's actually quite a bit left at 400DPI.
Any fix to this?
Click to expand...
Click to collapse
You would have to deodex the OPSystemUI.apk. Decompile it and modify it. Someone did it for the OP3. I can't remember if it was on XDA or the OnePlus community though.
Edit: That's what I meant when I mentioned scaling issues.
Sent from my OnePlus3T using XDA Labs

New update messed up all sorts of little things.. ??

I got the 8.0.0 update (Jan 1 security patch)
With this update there are some small UI changes are driving me nuts. Some notable ones:
-I have to swipe up/down to answer/reject a phone call (previously was right/left)
-Grid for the pull down configuration menu is now 2x3, used to be 3x3
-Ring/Media volume bars switched places
-The number pad on the dialer covers the whole screen, hiding the mute and speaker buttons
Does anyone know- is there a motorolla skin on this I can uninstall that will revert this changes? I haven't found anything. it's so annoying.
You are correct, UI under nougat was better
It didn't "mess up" anything...it's all UI changes. If it's absolutely unusable, there are many guides here to flash the older firmware onto this device. Or there is always alternative apps for the dialer that I'm sure you can use in place of the stock one.
thetolsonator said:
It didn't "mess up" anything...it's all UI changes. If it's absolutely unusable, there are many guides here to flash the older firmware onto this device. Or there is always alternative apps for the dialer that I'm sure you can use in place of the stock one.
Click to expand...
Click to collapse
I've seen some oreo pics that reflect a UI that is different from what I see on my x4. for example, the drop down configuration menu is still 3x3 https://cdn57.androidauthority.net/...ttings-android-8.0-oreo-review-5-1340x754.jpg
So I'm thinking motorolla has something installed which is causing these oddities. And if there is, I'm trying to figure out how to remove it. Or maybe there is a config somewhere I just haven't found yet.
Here's mine, looks about the right *shrug*
Sent from my Moto X4 using XDA Labs
thetolsonator said:
Here's mine, looks about the right *shrug*
Sent from my Moto X4 using XDA Labs
Click to expand...
Click to collapse
Hah ok. Must just be mine then. I will try digging around some more. Thanks
groopk said:
Hah ok. Must just be mine then. I will try digging around some more. Thanks
Click to expand...
Click to collapse
I think it's the case with regular variant of Moto X4 and not android one variant.
groopk said:
Hah ok. Must just be mine then. I will try digging around some more. Thanks
Click to expand...
Click to collapse
does it still have font size and display size customization?
Why did it messed up? I've only found a bit disorientating the new settings menu. Other than that everything looks fine to me. Also the toggles grid is still 3x3 on mine but I thing is due to the fact that I have the UI and text scaling on the lowest setting. Try making the UI as small as possible and make the text bigger just a notch. I think you'll get back the 3x3 quick toggles grid. I'm on the Moto edition, not the Project Fi or Amazon edition.

Categories

Resources