Flash the zip file from twrp....it will add few lines in build.prop and also add a file to etc folder.
I found it at nexus6 forum...so share it with you...one lg g3 user confirm it works.
use adaptive brightness to get maximum potential battery save!
Lot of people tried this mod and told that adaptive brightness works better and faster with assertive display, also in direct sunlight display is more visible.
****Don't forget to hit thanks if it's work for you..****
Um can you type the lines here and also add the file, got only temporary root, don't have twrp. Also this affects everything ? Games, pictures etc etc ?
massivebanana said:
Um can you type the lines here and also add the file, got only temporary root, don't have twrp. Also this affects everything ? Games, pictures etc etc ?
Click to expand...
Click to collapse
Here are the lines
# Assertive Display
ro.qcom.ad=1
ro.qcom.ad.calib.data=/system/etc/ad_calib.cfg
debug.sf.hw=1
And add the file from zip...to etc folder
massivebanana said:
Um can you type the lines here and also add the file, got only temporary root, don't have twrp. Also this affects everything ? Games, pictures etc etc ?
Click to expand...
Click to collapse
It will good for use adaptive brightness to get maximum potential battery save! Also adaptive brightness works better
Hello.. the ad_calib file. After moving it to etc folder any need to change permissions?
Hello. Please after flashing the file. The number 2 file. After movingit to etc folder should i change permissions?
princedede said:
Hello. Please after flashing the file. The number 2 file. After movingit to etc folder should i change permissions?
Click to expand...
Click to collapse
Yes you have to give proper permission....
anyone tried? and pls axplain installation, do we need to just flash both?
imamalemdar said:
anyone tried? and pls axplain installation, do we need to just flash both?
Click to expand...
Click to collapse
Just flash it
Anik49 said:
Just flash it
Click to expand...
Click to collapse
both and without any order right?
and do you really notice any big differences?
sorry for silly questions...
imamalemdar said:
both and without any order right?
and do you really notice any big differences?
sorry for silly questions...
Click to expand...
Click to collapse
Actually when i used it i found more vibrant screen....currently i am using fulmics 5.3 which also use assertive display plugin find both same...
Does this work at all without using auto brightness? I don't use that at all. I like to control where the brightness is set.
gonk24 said:
Does this work at all without using auto brightness? I don't use that at all. I like to control where the brightness is set.
Click to expand...
Click to collapse
Try it .....give us your result
Hey look do we just flash both files above ? Needs more explanation and what permissions do we have to give to it ? Only asking cause im not sure of permissions
kevinkehoe18 said:
Hey look do we just flash both files above ? Needs more explanation and what permissions do we have to give to it ? Only asking cause im not sure of permissions
Click to expand...
Click to collapse
I always thought it was rw-r-r
Anik49 said:
Try it .....give us your result
Click to expand...
Click to collapse
It's all flashed for now so we'll see. I'm already reminded of how I find auto brightness to be annoying. It's too dark when inside. I'm outside a lot during the day and keep brightness set at 70%. Inside at night I'll drop it to around 45%. Using auto set to 70% and being inside, the screen dims to what would be around 25% brightness. Too low, and I shouldn't have to set it above what's bright enough at the high end on manual.
So flash file no 1, wipe dalvik and cache, extract and place file no 2 in /etc?
And which permissions do I need to set?
Anik49 said:
Here are the lines
# Assertive Display
ro.qcom.ad=1
ro.qcom.ad.calib.data=/system/etc/ad_calib.cfg
debug.sf.hw=1
And add the file from zip...to etc folder
Click to expand...
Click to collapse
Bro....can u plz tell me how to add these lines in build.prop?? As i never did it before.....and on g3 d856 m still not able to get working twrp...so plz help me adding this lines in build.prop....n kindly some info about the permissions for ad_calib.cfg? Screenshots or video will be more efficient...
Panther.zr14 said:
Bro....can u plz tell me how to add these lines in build.prop?? As i never did it before.....and on g3 d856 m still not able to get working twrp...so plz help me adding this lines in build.prop....n kindly some info about the permissions for ad_calib.cfg? Screenshots or video will be more efficient...
Click to expand...
Click to collapse
you need root to add this line in your build.prop. have you rooted your phone?
Anik49 said:
you need root to add this line in your build.prop. have you rooted your phone?
Click to expand...
Click to collapse
Yes..but temporary with kingroot...
Related
i'v noticed suddenly (2.2 JPU) that 30% of my games for some reason run at 30%-50% of the screen ! so i reinstall - nothing
download other version of the game (1.8 from 1.5 for EX) nothing
install from the MARKET - nothing
here are 2 games for example that i have that problem :
doodle dush
scooter hero
any idea ?
you didnt play with your DPI setting right? something like LCD density etc ?
PAGOT said:
you didnt play with your DPI setting right? something like LCD density etc ?
Click to expand...
Click to collapse
that's the same answer i had in mind
sounds awefully familiar to LCD density gone wrong
not all apps/games are compatible with those settings
yea
yea i know about those programs ...and no
didn't use them ever !
any other ideas ?
asd1301 said:
yea i know about those programs ...and no
didn't use them ever !
any other ideas ?
Click to expand...
Click to collapse
I hate the thanks button!!!!
Now to you
can you please just go and check for this? (root explorer or some alternative)
/system/build.prop open the file and check for
ro.sf.lcd_density= "tell me whats here pls"
I still think something might have changed that value . if the games were before fine and now they are like that.
ro.sf.lcd_density=240
asd1301 said:
ro.sf.lcd_density=240
Click to expand...
Click to collapse
Okay, and now change it to 200 or 182 and reboot , try games how they gonna look like. Be careful with it though so you dont edit something you shouldnt. (And on your own risk)
i can't change anything !!! when i load the file can't pres nothing only BACK
and if i long press it there's no EDIT FILE" or something ....
how do i change it ?
at your phone it's on 240 ?
Ofc 240 is the default. And mine is on 240. You need to mount R/W to be able to edit it. In what are you opening it? You are rooted right?
it should be 240 if i cahnge it everything will look WORSE noap ? ...if res changes so ....
any way
what is to mouth RW ? and yes i'm rooted and went to this file with ROOT EXPLORER
asd1301 said:
it should be 240 if i cahnge it everything will look WORSE noap ? ...if res changes so ....
any way
what is to mouth RW ? and yes i'm rooted and went to this file with ROOT EXPLORER
Click to expand...
Click to collapse
its mount R/W means it mounts in read write mode and allows you to edit it.
And yes probably it will look worse. Wanted to just know if it doesnt reset the app setting. You will change back after you try it ofc
ok so how do i make this file changble ? if i press PERMISSION i get error that i can't change ...
?
What permission? ... just look in the folder up under the status bar there is a button mount R/W (next to Mounted as /ro) press it and then go edit the file.
ok when i do MOUT RW the only way i can edit is long pressing the file and
"open in text editor" ? u mean this way ?
waiting for your approval ...i don't wanna brik my phone
....
asd1301 said:
ok when i do MOUT RW the only way i can edit is long pressing the file and
"open in text editor" ? u mean this way ?
waiting for your approval ...i don't wanna brik my phone
....
Click to expand...
Click to collapse
yes? backup the file just in case somewhere. And dont change anything else there.
And maybe if you are worried try the LCD density changer app instead.
changed to 200
oK it did change all the res but the game still runs in 1/3 a screen ...
asd1301 said:
changed to 200
oK it did change all the res but the game still runs in 1/3 a screen ...
Click to expand...
Click to collapse
Ok, no idea then, there is a setting in spare parts app , compatibility mode, but I am not sure about that one. Anyway change it back as you had it. And you can add this to the "tried" section. Maybe someone else will have a better idea
OHH MY GODDDDDDDD !!! it WORKED !!!!!!!
that "compatibility mode" in SPAREPARTS !!! the V should be on ON i guess
10x !!
I have a rooted d800, running HellFire ROM. Ive looked and have yet to find a way to make and or install different boot animations, please help.
GearHead88 said:
I have a rooted d800, running HellFire ROM. Ive looked and have yet to find a way to make and or install different boot animations, please help.
Click to expand...
Click to collapse
you can use this test zip I made to flash the bootanimation(unzip it, place the bootanimation inside system/media/ and then rezip)
you can use bootanimation factory to add the loops to the bootanimation, the rest is up to you
XxZombiePikachu said:
you can use this test zip I made to flash the bootanimation(unzip it, place the bootanimation inside system/media/ and then rezip)
you can use bootanimation factory to add the loops to the bootanimation, the rest is up to you
Click to expand...
Click to collapse
Thanks a lot, any idea how to wrote the .txt file? Like what I'd need I understand the part 0,1,etc. And the resolution I just don't know what else or exactly how to write. Or would it be easier to use the factory?
GearHead88 said:
Thanks a lot, any idea how to wrote the .txt file? Like what I'd need I understand the part 0,1,etc. And the resolution I just don't know what else or exactly how to write. Or would it be easier to use the factory?
Click to expand...
Click to collapse
I I know that part 0 is the folder, 1 is usually the loops for the folder and the other number I don't remember; the resolution of the pictures is at the top, and next to it is usually the fps but I prefer to use the factory because this way it never fails
Sent from my potato powered LG G3 D800
XxZombiePikachu said:
I I know that part 0 is the folder, 1 is usually the loops for the folder and the other number I don't remember; the resolution of the pictures is at the top, and next to it is usually the fps but I prefer to use the factory because this way it never fails
Sent from my potato powered LG G3 D800
Click to expand...
Click to collapse
Thanks again, I was going to start making some test animations and see how it goes. Does the factory break an.gif file down into individual .PNG?
GearHead88 said:
Thanks again, I was going to start making some test animations and see how it goes. Does the factory break an.gif file down into individual .PNG?
Click to expand...
Click to collapse
it has option to create boot from .gif files but I haven't had the chance to test yet
XxZombiePikachu said:
it has option to create boot from .gif files but I haven't had the chance to test yet
Click to expand...
Click to collapse
Alright thanks again. I'm going to start unzipping ROMs and putting my Owen pics and sounds in to see what does. Idk what the teams would think of me posting their work with asteitc customizing inside though lol
GearHead88 said:
Alright thanks again. I'm going to start unzipping ROMs and putting my Owen pics and sounds in to see what does. Idk what the teams would think of me posting their work with asteitc customizing inside though lol
Click to expand...
Click to collapse
it's against xda to use other peoples work without permission, just saying
XxZombiePikachu said:
it's against xda to use other peoples work without permission, just saying
Click to expand...
Click to collapse
I meant with consent, until then just personal use
This is a quick walk through for editing the build.prop to allow lock screen and launcher rotation.
I got tired of looking at my phone sideways while it was propped up landscape wise, in my case.
1. Locate "build.prop" in /system using your favorite file explore
2. Open it up and at the bottom add the lines
Code:
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
3. Save your edit and reboot.
Lockscreen rotation still not working for you???
A few users have reported that adding a blank line between the two, fixes this issue.
Once the phone reboots your lockscreen and Google Now launcher will rotate with the orientation of the device just like other apps do.
To undo this, simply remove the lines we added
:good:
Update: 11/10/2015
enigma9o7 Has figured out how to get this to stick even after an update! Head over to his post for the walkthrough and install guide!! Remember to give them a "thanks" for sharing the work!
Awesome I been wondering how to get this done.
Nice tip. I've always just used an app called Ultimate Rotation Control. Seems to work just fine on the Nexus 6. A quick build.prop tweak removes the need for a separate app for it, though. I might get around to trying this...eventually
can someone make a flash able zip for this please ?
thanks in advance
Anybody know how one would do this with adb?
N6
I used an app for quite some time but i disliked it running in the background.
Im not able to make a flashable zip. Maybe in time I will see if i can.
For adb, youd have to pull the build.prop, edit on computer then push it back. The instructions to do that are unclear to me
mrfuzzie23 said:
can someone make a flash able zip for this please ?
thanks in advance
Click to expand...
Click to collapse
You can install Nova Launcher and toggle the setting in there, or use the ultimate rotation app someone else mentioned.
Thx
If you set the DPI to 384 or less, this happens by default.
pavankp said:
If you set the DPI to 384 or less, this happens by default.
Click to expand...
Click to collapse
Thats good to know! Not surprising, the device is most likely changed to "tablet size" to the system. And they have full rotation.
Works great, thanks! (AT&T Nexus 6)
Would not work for me I get error saving
techrider6262 said:
Would not work for me I get error saving
Click to expand...
Click to collapse
Thats not good. What error are you getting?
eqbirvin said:
Thats not good. What error are you getting?
Click to expand...
Click to collapse
It just said error can't save and I tried a couple different time
techrider6262 said:
It just said error can't save and I tried a couple different time
Click to expand...
Click to collapse
gotcha. You are rooted, correct? and if so what file manager are you using to locate the build.prop?
es file explorer and i'm rooted.
in ES file explorer when you grant it root permissions, click on root, then mount R/W, make sure "/system" is RW instead of RO. (sorry if you already know this, im just trying to save time and figure your error out haha)
Thanks I got it working.:good:
Glad to hear it!
to each their own, I like being able to get OTAs so I'll stick with Ultimate Rotation Control
Hello people, I have a big Problem. The Stock camera is just making a Green Image. Yesterday i did take pictures from my bike Tour and now ever Thing is Green. In video-picture-focus mode
Apps like cameringo are not effectet. Dont know where the Problem should be.
I cleanen the Cache and everything.
This is the link to one pic https://picload.org/view/dggcdprw/img_20170908_163208.jpg.html
Did you change your DPI or Font-Size? Or did you mess with any kind of build.prop editor?
Do you have night mode one?
I didnt change anything. Thats why i Was so confussed about it.
just flashed the full 4.5.10 zip. Camera is now working again.
Dan3ll1 said:
Hello people, I have a big Problem. The Stock camera is just making a Green Image. Yesterday i did take pictures from my bike Tour and now ever Thing is Green. In video-picture-focus mode
Apps like cameringo are not effectet. Dont know where the Problem should be.
I cleanen the Cache and everything.
This is the link to one pic https://picload.org/view/dggcdprw/img_20170908_163208.jpg.html
Click to expand...
Click to collapse
I have seen this before on the HTC 10 the problem was actually because users had flashed a new ROM from a different base but had not updated their firmware.
See if this the case for yourself.
If your firmware doesn't match the base you're on then update it.
I dig this thread out because I have the same error again but this time i know why. Allways when i edit the build.prop and Reboot i cant take pictures because they are green. This time i tried to set the soundcontroll to 50 clicks for better adjustment. No big deal and no big change. And last time i tried to Set the Screen Resolution to 4k for YouTube vidz.
Question is why is the cam allways broke
Are you taking a picture of a green sheet?
worldsoutro said:
Are you taking a picture of a green sheet?
Click to expand...
Click to collapse
Damn bruh, that joke. U are one of the funny few?
But no i just take a Green sheet of a green picture....
why is everyone so negative? I know the solution. @Dan3ll1
you must be rooted
Go to play store and download ES File explorer
Give ES Root permissions
go into local device -> system
find build.prop tap and hold the icon
now click more in the bottom right, click properties, find permissions and click change then choose the following
Owner: Read, write, execute
Group: Read
Other: Read
Camera shouldn't take green pictures anymore.
OcazPrime said:
why is everyone so negative? I know the solution. @Dan3ll1
you must be rooted
Go to play store and download ES File explorer
Give ES Root permissions
go into local device -> system
find build.prop tap and hold the icon
now click more in the bottom right, click properties, find permissions and click change then choose the following
Owner: Read, write, execute
Group: Read
Other: Read
Camera shouldn't take green pictures anymore.
Click to expand...
Click to collapse
I will try this out. Phone is rooted twrp and magisk running. I will give a Feedback if it works
OcazPrime said:
why is everyone so negative? I know the solution. @Dan3ll1
you must be rooted
Go to play store and download ES File explorer
Give ES Root permissions
go into local device -> system
find build.prop tap and hold the icon
now click more in the bottom right, click properties, find permissions and click change then choose the following
Owner: Read, write, execute
Group: Read
Other: Read
Camera shouldn't take green pictures anymore.
Click to expand...
Click to collapse
Nope, did not work. Still green when i edit the build.prop
Dan3ll1 said:
I will try this out. Phone is rooted twrp and magisk running. I will give a Feedback if it works
Click to expand...
Click to collapse
U edited it? If you did youre doing it wrong. Just change permissions
OcazPrime said:
U edited it? If you did youre doing it wrong. Just change permissions
Click to expand...
Click to collapse
Not much to do wrong. I did change the permission. Reboot - edit build.prop - Reboot - camera broke
Flashed full zip - magisk - twrp
Set permission - edit build.prop - Reboot - camera broke - green pic
Dan3ll1 said:
Not much to do wrong. I did change the permission. Reboot - edit build.prop - Reboot - camera broke
Flashed full zip - magisk - twrp
Set permission - edit build.prop - Reboot - camera broke - green pic
Click to expand...
Click to collapse
What room are you on?
OcazPrime said:
What room are you on?
Click to expand...
Click to collapse
I am on OOS 4.5.13 with Franco Kernel
Dan3ll1 said:
I am on OOS 4.5.13 with Franco Kernel
Click to expand...
Click to collapse
Maybe just use the google camera. Its pretty good.
OcazPrime said:
Maybe just use the google camera. Its pretty good.
Click to expand...
Click to collapse
I tried a few other camera Apps. All have the same green picture, even WhatsApp and other Apps that use the camera are just taking green pictures.
Then i have to life with those soundsteps
Dan3ll1 said:
I tried a few other camera Apps. All have the same green picture, even WhatsApp and other Apps that use the camera are just taking green pictures.
Then i have to life with those soundsteps
Click to expand...
Click to collapse
Yikes. Maybe try clean flashing. Or going into twrp and trying the option Fix contents under the advanced tab.
Had the same problem.
Setting the build.prop permissions to 644 saved me.
Hi, I wanted to change charging sound of stock rom, cuz its so annoying, and i cant turn it off. So I wanted to change it, but ZTE is so cocky, that I m not able to find charging sounds in system/media/sounds/ui. I was able to change lock, unlock, touch and keyboard sounds, but charging ones are no wherw to be found. Does anyone know where is the file of charging sound in stock rom? (i wasnt able to find it in LineageOS as well, but on Xiaomi Redmi Note 4)
xzolteu said:
Hi, I wanted to change charging sound of stock rom, cuz its so annoying, and i cant turn it off. So I wanted to change it, but ZTE is so cocky, that I m not able to find charging sounds in system/media/sounds/ui. I was able to change lock, unlock, touch and keyboard sounds, but charging ones are no wherw to be found. Does anyone know where is the file of charging sound in stock rom? (i wasnt able to find it in LineageOS as well, but on Xiaomi Redmi Note 4)
Click to expand...
Click to collapse
They're not in media but under system/priv-app/SystemUI_ZTE/
Look into the apk under res/raw/
There you have your charging.ogg
raystef66 said:
They're not in media but under system/priv-app/SystemUI_ZTE/
Look into the apk under res/raw/
There you have your charging.ogg
Click to expand...
Click to collapse
Ok, I copied systemui.apk from the location that you told me, then i replaced that charing.ogg. But now, when I copied it back (even from TWRP, or es file explorer), it feels like system dont see SystemUI.apk. The screen is totally black, and on first reboot I didnt have status bar. I fixed permissions, cleared chaches, and still nothing. Even if I copy back the original systemui.apk, its still the same. Im rocking your port of mifavor 5.0, do you know the solution how to properly install modified systemui.apk?
xzolteu said:
Ok, I copied systemui.apk from the location that you told me, then i replaced that charing.ogg. But now, when I copied it back (even from TWRP, or es file explorer), it feels like system dont see SystemUI.apk. The screen is totally black, and on first reboot I didnt have status bar. I fixed permissions, cleared chaches, and still nothing. Even if I copy back the original systemui.apk, its still the same. Im rocking your port of mifavor 5.0, do you know the solution how to properly install modified systemui.apk?
Click to expand...
Click to collapse
Most likely a signing problem or possible a clean flash needed.... (that is if you changed permissions right and so on....i cannot judge from here )
But as only res has to be modified i'd see no problem..
If you send me the ogg files you want to replace in the apk, i'll look into that and do a test myself.
raystef66 said:
Most likely a signing problem or possible a clean flash needed.... (that is if you changed permissions right and so on....i cannot judge from here )
If you send me the ogg files you want to replace in the apk, i'll look into that and do a test myself.
Click to expand...
Click to collapse
ok, pm
raystef66 said:
Most likely a signing problem or possible a clean flash needed.... (that is if you changed permissions right and so on....i cannot judge from here )
But as only res has to be modified i'd see no problem..
If you send me the ogg files you want to replace in the apk, i'll look into that and do a test myself.
Click to expand...
Click to collapse
xzolteu said:
ok, pm
Click to expand...
Click to collapse
i'm guessing you didn't change the permissions after putting it back, though, isn't it?
xzolteu said:
ok, pm
Click to expand...
Click to collapse
Glad it worked ! Needed more then a bit of permissions
These chinese ones are more stubborn as other roms. Therefore i deodexed the SystemUI_ZTE.apk
ONLY WORKING ON V2.0.0B13 (SL!M) Mifavor5.0
Here is the deodexed file : https://androidfilehost.com/?fid=818070582850495598
Just extract it and replace existing in system/priv-app/SystemUI_ZTE/ and change to 644
And you'll have another "charging" tone