For some reason the CRT animation always has felt slow as sin, so I usually keep it off. Changing animation settings in developer options no longer works for some reason.
Workaround:
Put debug.sf.electron_frames=1 in either local.prop or build.prop.
echo "debug.sf.electron_frames=1" > local.prop
Remove this to re-enable. Default is 24 frames.
Requires reboot.
Steps:
Root required to do this. This assumes that you have no local.prop. If you do, you probably don't need this guide.
1) Get into adb shell
2) su
3) cd /data/
4) echo "debug.sf.electron_frames=1" > local.prop
5) reboot
xaueious said:
For some reason the CRT animation always has felt slow as sin, so I usually keep it off. Changing animation settings in developer options no longer works for some reason.
Workaround:
Put debug.sf.electron_frames=1 in either local.prop or build.prop.
echo "debug.sf.electron_frames=1" > local.prop
Remove this to re-enable. Default is 24 frames.
Requires reboot.
Click to expand...
Click to collapse
Thanks for making this post. I'm a little confused though. Mostly by the "echo" portion. Mind explaining it in different terms?
My N7 doesn't have the CRT animation after updating to 4.2 I just figured they removed it.
Sent from my Nexus 7 using xda premium
xaueious said:
For some reason the CRT animation always has felt slow as sin, so I usually keep it off. Changing animation settings in developer options no longer works for some reason.
Workaround:
Put debug.sf.electron_frames=1 in either local.prop or build.prop.
echo "debug.sf.electron_frames=1" > local.prop
Remove this to re-enable. Default is 24 frames.
Requires reboot.
Click to expand...
Click to collapse
Just curious... What is CRT animation?
Sent from my Galaxy Nexus using xda app-developers app
Big ZD said:
Just curious... What is CRT animation?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
It's that white line that 'folds' down into the center before disappearing when turning off the display.
Replicates what you used to see when turning off a CRT monitor/TV.
Personally I'm a fan.
Anthonok said:
My N7 doesn't have the CRT animation after updating to 4.2 I just figured they removed it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Nexus 7 4.2 comes with a quick fadeout instead of the crt animation off.
my GN is not on stock so I can't report on it. i rather liked the crt off too, felt kinda neat.
SpencerRelly said:
Thanks for making this post. I'm a little confused though. Mostly by the "echo" portion. Mind explaining it in different terms?
Click to expand...
Click to collapse
Echo repeats whatever you type in quotes. The > sends it to local.prop file.
http://unixhelp.ed.ac.uk/CGI/man-cgi?echo
hmm didnt work for me on bigxie's android 4.2 rooted busybox odexed
The key is to have the line in one of your props. Should work on all Android 4.2 AOSP builds. If it didn't work, Run 'getprop' from shell to see if the setting worked. If it didn't, you might have another script overriding it.
Also works on 4.1 but be careful how high you set it, hehe. I set mine to 72 and it worked, but wouldn't unlock again afterwards.
It's shown in getprop, but it still doesn't work. I hate this CRT effect, really wanna make it go away.
xaueious said:
For some reason the CRT animation always has felt slow as sin, so I usually keep it off. Changing animation settings in developer options no longer works for some reason.
Workaround:
Put
Remove this to re-enable. Default is 24 frames.
Requires reboot.
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using xda app-developers app
langhaardack said:
It's shown in getprop, but it still doesn't work. I hate this CRT effect, really wanna make it go away.
Click to expand...
Click to collapse
same thing here. I added it to build.prop, it is showing correctly on getprop but the effect is still there
push in search of a working method to disable this
Guys maybe I wasn't clear enough.
I'll update OP
xaueious said:
For some reason the CRT animation always has felt slow as sin, so I usually keep it off. Changing animation settings in developer options no longer works for some reason.
Workaround:
Put debug.sf.electron_frames=1 in either local.prop or build.prop.
echo "debug.sf.electron_frames=1" > local.prop
Remove this to re-enable. Default is 24 frames.
Requires reboot.
Steps:
Root required to do this. This assumes that you have no local.prop. If you do, you probably don't need this guide.
1) Get into adb shell
2) su
3) cd /data/
4) echo "debug.sf.electron_frames=1" > local.prop
5) reboot
Click to expand...
Click to collapse
THANK YOU!!!
I hate that now that effect took about 2 seconds to actually start and it was really lagging...this fixed that
no matter which prop file i put that in, crt off stays on, and i cant handle this! its so ugly i just wanna throw my phone away.. D:
langhaardack said:
no matter which prop file i put that in, crt off stays on, and i cant handle this! its so ugly i just wanna throw my phone away.. D:
Click to expand...
Click to collapse
this mod doesn't work maybe this is just for stock roms no for aosp roms.
aooga said:
THANK YOU!!!
I hate that now that effect took about 2 seconds to actually start and it was really lagging...this fixed that
Click to expand...
Click to collapse
Thanks
xaueious said:
The key is to have the line in one of your props. Should work on all Android 4.2 AOSP builds. If it didn't work, Run 'getprop' from shell to see if the setting worked. If it didn't, you might have another script overriding it.
Click to expand...
Click to collapse
I tried 'setprop debug.sf.electron_frames 1', and I was able to get [debug.sf.electron_frames]: [1] from 'getprop'. But, it is still not working.... help?
Update: I even try the app "build.prop editor" and manually create debug.sf.electron_frames (value:1), and it is still not working. I go to /system/build.prop, and yes debug.sf.electron_frames=1 is there. My phone is rooted, newly flash with stock 4.2 on Gnexus. It wouldn't because I have BusyBox installed, right?
Related
After using Lox's 2.0 AOSP I really liked the lockscreen and since it really fits well with sense style-wise, I almost assumed HTC would use the standard lock-screen or something like it anyway in the 2.1 Hero. Now, let's start by noting I have noooo experience in fiddling with this, so bear with me if some things seem obvious...
Now i assumed Htc modified the original lockscreen and it needed to be switched out all together. That wasn't the case. The google lockscreen seems integrated in the system, while Htc's is just an apk which overrides it or whatever. So all you need to do to get the original lockscreen is removing the HtcLockScreen.apk with ADB. Assuming you know how to work with adb it goes:
Code:
adb remount
adb shell rm system/app/HtcLockScreen.apk
and... reboot.
Now... problem is, being inexperienced as I am I don't know if this 'breaks' stuff in the system. The problem I encountered were the following: you can't switch background, it will be transparent(like in the Hikari ROM), and I have no idea of how to fix this (if YOU do, please tell me I wanna know ). If you try switching it by standard methods (in the settings menu, for instance) it'll just FC. Other than that it seems to work as it should. With emphasis on seems oh, and i'm using behnaam's 2.1 ROM...
Ofcourse I'm not responsible if your Hero gets bricked... make a nandroid backup just in case... etcetera etcetera and maybe I should add: its not as smooth as on AOSP. Its a bit laggy, but no more that HTC's I think..
del_toro said:
The problem I encountered were the following: you can't switch background, it will be transparent(like in the Hikari ROM), and I have no idea of how to fix this (if YOU do, please tell me I wanna know ).
Click to expand...
Click to collapse
Based on the source code, the wallpaper is actually disabled
Code:
// wall paper background
if (false) {
final BitmapDrawable drawable = (BitmapDrawable) context.getWallpaper();
setBackgroundDrawable(
new FastBitmapDrawable(drawable.getBitmap()));
}
Note: if (false) <-- means it was intentionally turned off.
Stuck at the same with Villain 3 beta 4.
Still no way to fix that??
No harm in removing the hero lock screen I have been doing it for a while now as I prefer the stock google one.
I would however prefer to have the straight lock screen (nexus one?) rather than the arched google one of old but this does not seem built into any build yet (except certain custom roms)
Lennyuk said:
No harm in removing the hero lock screen I have been doing it for a while now as I prefer the stock google one.
I would however prefer to have the straight lock screen (nexus one?) rather than the arched google one of old but this does not seem built into any build yet (except certain custom roms)
Click to expand...
Click to collapse
Any lock screen will do, except HTC's one.
But i don't want transparent background. And i can't change it, it stays transparent, whatever i do.
eujene said:
Any lock screen will do, except HTC's one.
But i don't want transparent background. And i can't change it, it stays transparent, whatever i do.
Click to expand...
Click to collapse
yeah I have not worked that one out yet, I just assumed it is not supposed to have a wallpaper.
Check the CDMA (sprint hero) forum here and the first sticky post has loads of really nicely designed mods for the hero, not sure if they work on the gsm hero but there are some lock screens there as well, check them out and then you can try to get them on your phone if you like them (or ask a dev to make them gsm compatible)
Lennyuk said:
yeah I have not worked that one out yet, I just assumed it is not supposed to have a wallpaper.
Check the CDMA (sprint hero) forum here and the first sticky post has loads of really nicely designed mods for the hero, not sure if they work on the gsm hero but there are some lock screens there as well, check them out and then you can try to get them on your phone if you like them (or ask a dev to make them gsm compatible)
Click to expand...
Click to collapse
Thanks for the idea. But they are too modded for my taste. I want simple vanilla lock screen with wallpaper. Nothing more )
I hope @nprussel will notice this thread, and will do something.
eujene said:
Thanks for the idea. But they are too modded for my taste. I want simple vanilla lock screen with wallpaper. Nothing more )
I hope @nprussel will notice this thread, and will do something.
Click to expand...
Click to collapse
Noticed.
I can sort this for you no problem. I didn't realise there were many out there removing the HTC Lockscreen from Vanillain. Personally, I remove it, but I quite like it transparent.
I'll sort it for you in the next build.
nprussell said:
Noticed.
I can sort this for you no problem. I didn't realise there were many out there removing the HTC Lockscreen from Vanillain. Personally, I remove it, but I quite like it transparent.
I'll sort it for you in the next build.
Click to expand...
Click to collapse
Yeah, sure many. Vanilla lock screen has much more useful info.
Thanks, looking forward to the new beta!
nprussell said:
Noticed.
I can sort this for you no problem. I didn't realise there were many out there removing the HTC Lockscreen from Vanillain. Personally, I remove it, but I quite like it transparent.
I'll sort it for you in the next build.
Click to expand...
Click to collapse
Yeah same here, I remove it but I like it transparent.
For those that can't/ don't want to use ADB you can use terminal emulator (availiable for free in the market) and do it direct from your handset.
(To get the keyboard up hold down the menu key)
(can't use the long press shortcuts for things like / have to do it the long way)
Now type this code exactly as it is here (pressing enter (return) for a new line)
______
su
# mount -oremount,rw /dev/block/mtdblock3 /system
# rm system/app/HtcLockScreen.apk
_______
Then reboot your phone.
So there is no possibility to change wallpaper (get rid of that transparency) in STANDARD ECLAIR LOCKSREEN ?
I thought I would add in that if you want to try this out without deleting the .apk file just use the mv command.
Code:
./adb remount
./adb shell mv system/app/HtcLockScreen.apk system/app/HtcLockScreen.BACKUP
./adb reboot
then if you want to go back to original just mv it back:
Code:
./adb remount
./adb shell mv system/app/HtcLockScreen.BACKUP system/app/HtcLockScreen.apk
-D
Krzysiec said:
So there is no possibility to change wallpaper (get rid of that transparency) in STANDARD ECLAIR LOCKSREEN ?
Click to expand...
Click to collapse
yeah i hate the transparency also...but i cant find a way...****
Fraqq said:
yeah i hate the transparency also...but i cant find a way...****
Click to expand...
Click to collapse
I hate it because see two different layers (Home screen and Lockscreen) are mixed ... Awful effect :/ And i don`t know what is what ... Two clocks one sense with weather, second from lockscreen ... one updated, second not ... erghhhhh
i can only unlock it by pressing the menu button. Is this normal for this method? (BeHero ROM)
adb remount
adb shell rm system/app/HtcLockScreen.apk
Click to expand...
Click to collapse
after this it's impossible to desactivate the Alarm of htc_deskclock, I must use standard deskclock eclair for the Alarm.
Anyone know to change background?
dweebs0r said:
I thought I would add in that if you want to try this out without deleting the .apk file just use the mv command.
Code:
./adb remount
./adb shell mv system/app/HtcLockScreen.apk system/app/HtcLockScreen.BACKUP
./adb reboot
then if you want to go back to original just mv it back:
Code:
./adb remount
./adb shell mv system/app/HtcLockScreen.BACKUP system/app/HtcLockScreen.apk
-D
Click to expand...
Click to collapse
I renamed system/app/HtcLockScreen.apk,but the eclair tranparent lockscreen(include unlock&sound) didn't showup,the lockscreen is a transparent time screen?
tiger2z said:
I renamed system/app/HtcLockScreen.apk,but the eclair tranparent lockscreen(include unlock&sound) didn't showup,the lockscreen is a transparent time screen?
Click to expand...
Click to collapse
As i just said in the other thread, it is a problem with the legend dump, hopefully someone with more knowledge than me can work out why.
Not sure if this does the same as what people are experiencing but might be worth a shot. Note, I have not tried this.
Just Google: Howtoremovetheerislockscreen.aspx
Should be the first and only hit.
I present to you a mod that enables on screen navigation buttons
TouchWiz Only
Downloads
!! Make sure you're not using Cyanogenmod or another AOSP-based ROM !!
!! Make sure you're on an LG2 ROM !! If not, you will need to flash stock again.
Add Buttons
Remove Buttons/Reverse Mod
Flash the zip of your choice in recovery like you would for any ROM
HolySmokesBatty's Disabled Capacitive Button Lights And Home Key Remapped Version
!! Not made by me, made by HolySmokesBatty !!
Add Buttons
Remove buttons/Reverse Mod
Nice and first! Downloading now...
Very nice!
Sent from Mr. Z's Galaxy S3.
yousefak said:
I present to you a mod that enables on screen navigation buttons
TouchWiz Only
Download
!! Make sure you're not using Cyanogenmod or another AOSP-based ROM !!
Add Buttons
Remove Buttons
Flash the zip of your choice in recovery like you would for any ROM
Disable Capacitive Button Lights
If you'd rather have the capacitive button lights off:
Download "Night Mode" from play store
Set slider to 100% and start service
Go to settings
Disable "Minimum brightness" and "notification"
Now it won't mess with your brightness but disable capacitive button backlights
Click to expand...
Click to collapse
Correct me if I'm wrong, but couldn't you just choose the option "always off" in system>display>touch key light duration in order turn off the capacitive button lights?
Sent from my SPH-L710 using xda premium
swampy67 said:
Correct me if I'm wrong, but couldn't you just choose the option "always off" in system>display>touch key light duration in order turn off the capacitive button lights?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
For some reason, that option disappears after turning on On-screen buttons.
yousefak said:
For some reason, that option disappears after turning on On-screen buttons.
Click to expand...
Click to collapse
Interesting
Sent from my SPH-L710 using xda premium
you can just disable d lights before flashing....works great looks even better...can we get different looks 2 the buttons
joselb said:
you can just disable d lights before flashing....works great looks even better...can we get different looks 2 the buttons
Click to expand...
Click to collapse
I've tried, but the PNG's don't appear to be in res/drawable-hdpi. I'll look through the other folders tomorrow to see if I can find anything.
If I can, I plan on making another mod for Gnex style buttons.
yousefak said:
I've tried, but the PNG's don't appear to be in res/drawable-hdpi. I'll look through the other folders tomorrow to see if I can find anything.
If I can, I plan on making another mod for Gnex style buttons.
Click to expand...
Click to collapse
They are there. I they are in a weird folder but just search for them. Its called like ic_sysbar_home_normal.png but i already tried changing look. And couldnt pull it off. If u do please pist how-to
Sent from my SPH-L710 using XDA App
Edited to remove my douchebaggery.
holysmokesbatty said:
I like how this guy posted our work as his. Oh woe is XDA.
Click to expand...
Click to collapse
Your work?
I followed a guide to do the edits and you probably did too so its none of our works really.
I spent hours figuring out how to successfully recompile framework-res.apk. Then I had to figure out how to get it to boot. Then I had to change the height and figure out how to disable capacitive backlight.
Instead of being selfish, I released my mod to public.
I guess releasing my own work to public was a mistake.
(Oh, and I'll make a video of me decompiling, editing, and building/testing if you don't believe me)
Edit: lol, do you even have a link to your work or do claim I somehow stole your private work?
Sent from my Sprint SGS3
monstaX said:
They are there. I they are in a weird folder but just search for them. Its called like ic_sysbar_home_normal.png but i already tried changing look. And couldnt pull it off. If u do please pist how-to
Sent from my SPH-L710 using XDA App
Click to expand...
Click to collapse
Go to freezas system apk thread and use that to figure out how to decompile/recompile system apps.
Decompile framework-Res.apk. do all of your editing. Then you can recompile and push to /system/framework and boot the phone. If you did everything correctly, the bar at the bottom should reflect the edits.
Sent from my Sprint SGS3
Anybody can do this btw. Decompile framework-res.apk, look for the Navigation bar bool and set it to "true"
If you want different pngs for the buttons you need to look in SystemUI.apk
Here's a blank zip you can use
http://db.tt/mmOQPE5Z
Extract it and add a system folder then add an app folder within it (if modifying anything in /system/app or a /system/framework folder if you modified anything in /system/framework) and place your modified apk's in the appropriate folders
Zip up the META folder and system folder and flash in recovery
Sent from my SPH-L710 using xda premium
fergie716 said:
Anybody can do this btw. Decompile framework-res.apk, look for the Navigation bar bool and set it to "true"
If you want different pngs for the buttons you need to look in SystemUI.apk
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Yeah, I'm in no way a dev or modder. It just got me annoyed how someone claimed this was his work.
Sent from my Sprint SGS3
yousefak said:
Yeah, I'm in no way a dev or modder. It just got me annoyed how someone claimed this was his work.
Sent from my Sprint SGS3
Click to expand...
Click to collapse
Well it's no one's "work"
Bools are like switches. Anyone can turn them off/on. But yea anyone with the power of Google could do it. No ones specific property
Sent from my SPH-L710 using xda premium
Sweet. Can you disable capacitive buttons though? I heard cm10 can do this.
Can you please post a screenshot?
yousefak said:
Your work?
I followed a guide to do the edits and you probably did too so its none of our works really.
I spent hours figuring out how to successfully recompile framework-res.apk. Then I had to figure out how to get it to boot. Then I had to change the height and figure out how to disable capacitive backlight.
Instead of being selfish, I released my mod to public.
I guess releasing my own work to public was a mistake.
(Oh, and I'll make a video of me decompiling, editing, and building/testing if you don't believe me)
Edit: lol, do you even have a link to your work or do claim I somehow stole your private work?
Sent from my Sprint SGS3
Click to expand...
Click to collapse
Sorry, man. Was half asleep when I saw this, and wasn't exactly rational.
To be fair though, monstaX and I were going back and forth on this over in Themes & Apps over the last couple days, and all progress was very visible there.
http://forum.xda-developers.com/showthread.php?t=1771908
I was gonna package it and post it here (with an additional edit to the /keylayout folder to turn off capacitive keys and remap home to be a camera key) but my wife's car broke down yesterday and I had to deal with that.
Again, I apologize for being a douche. I need to stop using the internet when I'm tired.
holysmokesbatty said:
Sorry, man. Was half asleep when I saw this, and wasn't exactly rational.
To be fair though, monstaX and I were going back and forth on this over in Themes & Apps over the last couple days, and all progress was very visible there.
http://forum.xda-developers.com/showthread.php?t=1771908
I was gonna package it and post it here (with an additional edit to the /keylayout folder to turn off capacitive keys and remap home to be a camera key) but my wife's car broke down yesterday and I had to deal with that.
Again, I apologize for being a douche. I need to stop using the internet when I'm tired.
Click to expand...
Click to collapse
No problem. I apologize for also being hostile in my post too.
Sent from my Sprint SGS3
Just a little reminder: ANDROID IS OPEN SOURCE. I dont like it when people call crap "their own work". All anybody is doing is tweaking the things that are already there.
Sorry, it just frustrates me.
I'm trying to disable the startup and shutdown sounds. Anyone know the best way to do this?
schale01 said:
I'o trying to disable the startup and shutdown sounds. Anyone know the best way to do this?
Click to expand...
Click to collapse
Unrooted - put your device on silent or vibrate before shutting down.
Rooted - make system writable and edit file in system/volume.db I believe with sql editor and changed all boot labeled sounds to 0 values
Also same method to disable camera sounds btw
bhint15 said:
Unrooted - put your device on silent or vibrate before shutting down.
Rooted - make system writable and edit file in system/volume.db I believe with sql editor and changed all boot labeled sounds to 0 values
Also same method to disable camera sounds btw
Click to expand...
Click to collapse
Perfect. I edited the volume.db file in system/etc as you suggested. I used sql editor by speed software. I changed the 'boot sound' record under situationvolume to 0. Rebooted to take effect. After reboot no startup or shutdown sounds. Thank you.
Shutter sounds records were present as well but I already enabled the toggle option in feature.xml and turned off forced shutter in buildprop edit. So I just left them alone.
Sent from my SPH-L900 using xda app-developers app
Hi guys.
So i manged to remove the camera shortcut from the lockscreen using sqlite.
1. settings storage
1.1 settings.db
1.2 system
1.3 (search for) short and you will find "set_shortcuts_mode"
1.4 change the value to 0 and camera goes away.
Any idea on how to remove the phone?
FdeKlerk said:
Hi guys.
So i manged to remove the camera shortcut from the lockscreen using sqlite.
1. settings storage
1.1 settings.db
1.2 system
1.3 (search for) short and you will find "set_shortcuts_mode"
1.4 change the value to 0 and camera goes away.
Any idea on how to remove the phone?
Click to expand...
Click to collapse
Can you possibly get different apps?? Also what if you change the value to 2 or 3 lol..?
JoeFCaputo113 said:
Can you possibly get different apps?? Also what if you change the value to 2 or 3 lol..?
Click to expand...
Click to collapse
Different apps, no and no 2 or 3 does nothing tried.
Can you explain more how you did this?
Can you edit the build.prop file to do the same thing?
In the lockscreen setting with MM you can take camera off and put any app in that spot. maybe the call too.
I don't think you can remove call button due to emergencies. Which is actually a good idea. Granted anything can be done using root and modifying framework files.
Sent from my SM-G900P using Tapatalk
If you want to drop the animations settings in developer options below the available .50 to .25 here are the commands. Please only do this if you know what you doing I'm not responsible for your mistakes! Do your research before applying these settings.....
Assuming you know what adb is and how to set it up below are the commands, if not give it a google as I will not post how to do it.
Check your device is connected
adb devices
To set scales to .25
adb shell
settings put global window_animation_scale 0.25
settings put global transition_animation_scale 0.25
settings put global animator_duration_scale 0.25
To Check what they are set to
settings get global window_animation_scale
settings get global transition_animation_scale
settings get global animator_duration_scale
These settings stay after a reboot but is not reflected in developer settings to put back to .50 or whatever change the .25 to what you want.
IMPORTANT
I am not responsible for your mistakes this is just a guide found on the internet.
Can't you turn off animations completely on Pixels?
One of the first things I do is turn off animations completely on PCs and Androids. They do nothing except waste resources.
blackhawk said:
Can't you turn off animations completely on Pixels?
One of the first things I do is turn off animations completely on PCs and Androids. They do nothing except waste resources.
Click to expand...
Click to collapse
Yes you can in developer options but certain things just ain't right like when you turn them off and pull down the notification drawer it comes down so quick that you sometimes select a notification without meaning to unless you have lightening reflexes.
m1ckbr1t said:
Yes you can in developer options but certain things just ain't right like when you turn them off and pull down the notification drawer it comes down so quick that you sometimes select a notification without meaning to unless you have lightening reflexes.
Click to expand...
Click to collapse
Not sure why they would do that...
Maybe only one of the Pixel animation settings needs to be partially delayed, the rest can be cut to zero and still avoid that behavior.
thanks for the info, just in case someone doesn't want to use the ADB way: I used the app Setedit to change the settings (this app needs the WRITE_SECURE_SETTINGS permission set either via console or ADB, though )....
blackhawk said:
Not sure why they would do that...
Maybe only one of the Pixel animation settings needs to be partially delayed, the rest can be cut to zero and still avoid that behavior.
Click to expand...
Click to collapse
Possibly but I've always, for years set them all to .25 just my personal preference.
Does this still break fingerprint after the newest update? I haven't sideloaded it yet so I can't test
Opensystem said:
Does this still break fingerprint after the newest update? I haven't sideloaded it yet so I can't test
Click to expand...
Click to collapse
Not at all if anything makes it seem faster as the visual animations are reduced. I've side loaded the .37 update and fingerprint is working perfectly it always has done for me.
m1ckbr1t said:
Not at all if anything makes it seem faster as the visual animations are reduced. I've side loaded the .37 update and fingerprint is working perfectly it always has done for me.
Click to expand...
Click to collapse
A lot of posts on XDA mentioned that turning off animation scaling or reducing it messed with the scanner. Just so anyone doing this is aware
Opensystem said:
A lot of posts on XDA mentioned that turning off animation scaling or reducing it messed with the scanner. Just so anyone doing this is aware
Click to expand...
Click to collapse
I turned animation scale off day one and never had issues with my FP, except of course that it sometimes just sucked because Optical and well Google, but FP is fine since I sideloaded .037.
Looks good... might try it and see. Cheers
blackhawk said:
Not sure why they would do that...
Maybe only one of the Pixel animation settings needs to be partially delayed, the rest can be cut to zero and still avoid that behavior.
Click to expand...
Click to collapse
If you turn them all completely off, then things like the loading spinner, don't spin. Because of this, I turn them all off except Animator duration, which will fix this. I set it to the lowest setting, 0.01x -- if the custom ROM allows, otherwise I do the stock 0.50x. In the past I have used this adb command though to get it lower. Works nicely.
andybones said:
If you turn them all completely off, then things like the loading spinner, don't spin. Because of this, I turn them all off except Animator duration, which will fix this. I set it to the lowest setting, 0.01x -- if the custom ROM allows, otherwise I do the stock 0.50x. In the past I have used this adb command though to get it lower. Works nicely.
Click to expand...
Click to collapse
Interesting; it's integrated with features and hard to get around. I didn't expect this but can see the design logic. Be nice if they had some plugins to modify the UI without resorting to a 3rd party launcher.
The N10+'s notifications pull down comes down at whatever speed you pull it down. No false touches; you need to release the display before it becomes active. However if animations is active it's like waiting for the story to end... anoying.
I've also gone down to 0.25x but what's the lowest you can go without hitting zero?
I'm not entirely sure, try it!!! You can always change it back if it doesn't work. I'm sure I've read somewhere that they go down to 0.01
Setting to 0 has always had side effects......never do this
73sydney said:
Setting to 0 has always had side effects......never do this
Click to expand...
Click to collapse
I always run like that. For giggles and kicks I'll try setting animation duration to .5
All animation waste resources and make a fast machine look woke goofy.
Update, no improvement at all. If fact it made it slightly slower. I experience no lag when I hit the recent nav button with no animation. With duration .5 active I can see the delay.
m1ckbr1t said:
If you want to drop the animations settings in developer options below the available .50 to .25 here are the commands. Please only do this if you know what you doing I'm not responsible for your mistakes! Do your research before applying these settings.....
Assuming you know what adb is and how to set it up below are the commands, if not give it a google as I will not post how to do it.
Check your device is connected
adb devices
To set scales to .25
adb shell
settings put global window_animation_scale 0.25
settings put global transition_animation_scale 0.25
settings put global animator_duration_scale 0.25
To Check what they are set to
settings get global window_animation_scale
settings get global transition_animation_scale
settings get global animator_duration_scale
These settings stay after a reboot but is not reflected in developer settings to put back to .50 or whatever change the .25 to what you want.
IMPORTANT
I am not responsible for your mistakes this is just a guide found on the internet.
Click to expand...
Click to collapse
Or you can download systemuituner from playstore.