I found a rather simple way to lower the minimum brightness. There is a file named /sys/class/leds/wled/fs_curr_ua. If you edit the value in this file, the brightness of back light is changed without downgrading the contrast. I guess the file can control the maximal and minimal brightness together.
To make sure change the minimum brightness after each booting. I altered the boot image.
My device is unlocked with TWRP installed. The Android version is 8.0.
1.Backup the boot partition using TWRP.
2.Then uppack the boot image: boot.emmc.win. (I use Android Image Kitchen)
3.Edit the init.rc file. In this file, find the "on boot" section, add a text line as following:
write /sys/class/leds/wled/fs_curr_ua 12000
4.Repack the boot image, and rename the new boot image to "boot.emmc.win". Then restore this image using TWRP.
The original value on my device is 20000, 12000 is the best value for me at night.
I recently tried to do this, and I have a few questions:
1. When I repacked the image with Android Kitchen, the image decreased in size from 64MB to around 17MB. Is this supposed to happen, or am I doing something wrong?
2. Where do I put in the line? Do I just put it anywhere under the "on boot" section? I just put the line right under the "on boot" section.
3. I used the brightness value that you used, and I didn't see too much(if any) difference in the minimum brightness. This is most likely because I did it wrong, but I was just wondering how much darker the brightness is for you after the change?
This is the first time I've messed with Android Image Kitchen, so I most likely did something wrong. Thanks.
Generic123. said:
I recently tried to do this, and I have a few questions:
1. When I repacked the image with Android Kitchen, the image decreased in size from 64MB to around 17MB. Is this supposed to happen, or am I doing something wrong?
2. Where do I put in the line? Do I just put it anywhere under the "on boot" section? I just put the line right under the "on boot" section.
3. I used the brightness value that you used, and I didn't see too much(if any) difference in the minimum brightness. This is most likely because I did it wrong, but I was just wondering how much darker the brightness is for you after the change?
This is the first time I've messed with Android Image Kitchen, so I most likely did something wrong. Thanks.
Click to expand...
Click to collapse
hello,
1. I also got a similar smaller image file(60 to 20). So I think it's normal.
2. The following lines is the segment of my setting in file init.rc, I think it is the same to you?!
...
on boot
write /sys/class/leds/wled/fs_curr_ua 12000
# basic network initifup lo...
3. I just click "repackimg.bat" to repack image file. The repack image file was named "image-new.img". I rename it to "boot.emmc.win". Then, write it back to boot partition using TWRP. The brightness is changed to dark very obviously. If you set it to near 0, the screen was almost black after booting. And my Android version is 8.0.0(47.1.A.16.20), I guess different OS version may have different brightness setting file. You can try to explorer /sys/class/leds directory and try to search and edit the similar files.
Sorry for my bad English!
waybering said:
hello,
1. I also got a similar smaller image file(60 to 20). So I think it's normal.
2. The following lines is the segment of my setting in file init.rc, I think it is the same to you?!
...
on boot
write /sys/class/leds/wled/fs_curr_ua 12000
# basic network init
ifup lo
...
3. I just click "repackimg.bat" to repack image file. The repack image file was named "image-new.img". I rename it to "boot.emmc.win". Then, write it back to boot partition using TWRP. The brightness is changed to dark very obviously. If you set it to near 0, the screen was almost black after booting. And my Android version is 8.0.0(47.1.A.16.20), I guess different OS version may have different brightness setting file. You can try to explorer /sys/class/leds directory and try to search and edit the similar files.
Sorry for my bad English!
Click to expand...
Click to collapse
Thanks! I am on LineageOS 16.0, which may be the reason it doesn't work. Oddly enough, I found the file though. I'll try to make the image again. Thanks.
waybering said:
I found a rather simple way to lower the minimum brightness. There is a file named /sys/class/leds/wled/fs_curr_ua. If you edit the value in this file, the brightness of back light is changed without downgrading the contrast. [...]
The original value on my device is 20000, 12000 is the best value for me at night.
Click to expand...
Click to collapse
Thank you very much! :good: Your hack helped me reading my display in the dark without hurting my eyes.
or just simply use screen dimmer app
Related
Has anyone figured out how to change the boot animation?
It seems it's stored in /system/media/bootanimation.zip
I tried replacing the .PNG images inside the archive and that didn't work, although I might have messed up something. I'm just glad to be rid of that dreadful SE color splash until someone else finds a solution.
finished playing with this a little while ago... when you replace the files you must use no compression, ie store. i've attached one with the android robot waving (cropped from nexus) simple, but at least the splash is gone
toreador514 said:
finished playing with this a little while ago... when you replace the files you must use no compression, ie store. i've attached one with the android robot waving (cropped from nexus) simple, but at least the splash is gone
Click to expand...
Click to collapse
Thanks for this! Looks so sweet!!
strange... I replaced one frame to see if it changed and saw nothing ( i put a big red X across one image ). I did use no compression ( kept the zip open in winrar and saved )
will try again!
morning_wood said:
strange... I replaced one frame to see if it changed and saw nothing ( i put a big red X across one image ). I did use no compression ( kept the zip open in winrar and saved )
will try again!
Click to expand...
Click to collapse
i finally found it for sure...from the zip above extract them all put your images in an then add in a zip file all of them again but you have to rename it as bootanimation.zip and you have to choose at winrar compression method store...its final and you can put anything you want...
Thank you for helping me sort this out.
Here's GLa’DOS "Android Scribble" animation for the x10 mini.
Apparently anim2 lasts a couple of seconds, and anim3 last the longest.
I lost my first x10 mini, so I added a name and telephone number for my animation after posting (and a lock screen for the phone).
if anyone want me to make any anime feel free...
here is my first one and of course greek...
http://i47.photobucket.com/albums/f172/enormous101/Untitled.gif
http://i47.photobucket.com/albums/f172/enormous101/Untitled1.gif
http://www.mediafire.com/?abm54nd13pocn1d
Noice one peeps.
Simplified it a bit down to one folder now though.
Got mine working now (needs 24bit png)
Sent from my E10i using XDA App
Hi Guys.
I've been trying to change the bootanimation, but as
I'm a little slow to understand, I have no doubt
to decompress it and stuff.
Who can explain me the luxuries of details please?
It would be a great help ...
FreddyStark said:
Hi Guys.
I've been trying to change the bootanimation, but as
I'm a little slow to understand, I have no doubt
to decompress it and stuff.
Who can explain me the luxuries of details please?
It would be a great help ...
Click to expand...
Click to collapse
1 root your phone
2 download rootexplorer(<---and install it) & any bootanimation.zip you want
3 open rootexplorer and go to your sdcard hold down your finger and choose copy
4 then go to system/media
5 at the upper of your root explorer its a button that says mount r/w make it says by pushing it mount r/o
6 push the button paste and then when it says ovewrite push yes
7 reboot and you r ready!!!!
if i make it a single file you will not have the option when the first animation is over the second to be anime it will be a still picture if you want that just leave one image in the second folder..because it have 2 phases of animation..!!!!(if you remember first when the colours where mixing and then the still image with sony ericsson logo and letters)
I've been trying to edit the desc.txt file so I can have a little more flexibility but even if I save it without making any changes it stops working.
After a look around the interwebs someone mentioned saving in the UNIX format, so I used Notepad ++ in UNIX and tried editing/saving in that but there's still problems, sometimes it doesn't work at all and sometimes it only shows the first folder.
Also, are there any limitations as to framerate and how many files can go in the part0/part1 folders (revision of enormous101's bootanimation.zip).
Finally, is it ok to add a part2?
do not use compression - use Winrar and select "store"
Mitchio said:
I've been trying to edit the desc.txt file so I can have a little more flexibility but even if I save it without making any changes it stops working.
After a look around the interwebs someone mentioned saving in the UNIX format, so I used Notepad ++ in UNIX and tried editing/saving in that but there's still problems, sometimes it doesn't work at all and sometimes it only shows the first folder.
Also, are there any limitations as to framerate and how many files can go in the part0/part1 folders (revision of enormous101's bootanimation.zip).
Finally, is it ok to add a part2?
Click to expand...
Click to collapse
as i mentioned part 2 is when the bootanimation of sony ericsson stays frozen you can add anything you want and its safe to play with part two.. no limitation except your internal storage!!!!what exactly are you trying to do with desc?may i help you?if you find my preview posts at the first page you will find to download the bootanimation.zip with two parts so unzip it and when you add your images zip it with winrar at store compression mode...
morning_wood said:
do not use compression - use Winrar and select "store"
Click to expand...
Click to collapse
Already doing that.
Maybe a stupid idea, but... has anyone tried to use transparent images?
I want to watch the kernel booting
edit: Forget this.
Nice thread!
I was wondering about the desc.txt file. I am using the Rogers 2.1 firmware and I want to remove the Rogers screen that shows up just before desktop loads. The PNG file for the Rogers screen is located in Anim5 and I was wondering if I just removed the entry for anim5 in the desc file, would that do the trick? I've already moved the original bootanimation.zip file onto my computer so it is backed up but I was just wondering if this would work. I am using a X10 but it seems like the file system is the same which is why I'm asking here. Any help would be appreciated!
hope helped
JDwan said:
Nice thread!
I was wondering about the desc.txt file. I am using the Rogers 2.1 firmware and I want to remove the Rogers screen that shows up just before desktop loads. The PNG file for the Rogers screen is located in Anim5 and I was wondering if I just removed the entry for anim5 in the desc file, would that do the trick? I've already moved the original bootanimation.zip file onto my computer so it is backed up but I was just wondering if this would work. I am using a X10 but it seems like the file system is the same which is why I'm asking here. Any help would be appreciated!
Click to expand...
Click to collapse
if you dont know how to change desc.txt then dont...unzip the bootanimation.zip change the images inside anim5 folder and then zip it but at compression mode use ''store'' instead of everything else and just put it in your phone...i cant change your desc.txt and make it into two folders because i dont own x10...
enormous101 said:
if you dont know how to change desc.txt then dont...unzip the bootanimation.zip change the images inside anim5 folder and then zip it but at compression mode use ''store'' instead of everything else and just put it in your phone...i cant change your desc.txt and make it into two folders because i dont own x10...
Click to expand...
Click to collapse
Thanks for your response! From what I've been reading, it seems that if I remove the entry for anim5 in the desc.txt, that it won't load that animation. It just seems easier to do this than to replace the image in that folder. Though the problem would then be making changes to a UNIX based txt file using a Windows OS and then the phone not recognizing the desc.txt file based on it being in the wrong format.
Anyway, I suppose I could just copy over the last image in anim4 and replace the one in anim5 with that and that would be the easier solution (as per your suggestion).
Here is the thread I was reading where it describes the desc.txt file and how to modify your boot animation.
http://www.droidforums.net/forum/droid-hacks/33932-bootanimation-zip-file-explained.html
I was wanting to know if anyone out there knows of a working Boot Screen Animation Changer for the A70/101IT that can successfully change the boot screen without crashing over and over?? It would also be even greater if anyone knows of one that also allows you to download new boot screens within the same app too!?
Lastly, if it really is possible to change the boot screen animation on the A101IT to something different... what is a good site that has them AND what file format ending (like .gif or whatever) should I look for? Also, are all custom boot screens for other Android devices (like Android cell phones) compatible with the A101IT?
spicy_puerto_rican said:
Lastly, if it really is possible to change the boot screen animation on the A101IT to something different... what is a good site that has them AND what file format ending (like .gif or whatever) should I look for? Also, are all custom boot screens for other Android devices (like Android cell phones) compatible with the A101IT?
Click to expand...
Click to collapse
Yes it's possible to change the boot screen animation. See here
And yes most boot screen animations from other devices will work.
http://lmgtfy.com/?q=android+boot+screen+animation
Awesome, thanks a ton! You rock! You're very helpful and informative! Much appreciated.
This is cool thanks. Will this work on the 70 as well . Also, Would you happen to know the dimensions for the images. I doubt that the bootanimations from a phone will have the right size images. If someone knows what size they need to be for the 101 and the 70 that would be some good info.
saprano614 said:
This is cool thanks. Will this work on the 70 as well . Also, Would you happen to know the dimensions for the images. I doubt that the bootanimations from a phone will have the right size images. If someone knows what size they need to be for the 101 and the 70 that would be some good info.
Click to expand...
Click to collapse
Any size smaller than the display size will work. I believe the images are automatically scaled down to fit the screen but not scaled up. Some tests need to be done to find a good size.
This may help http://androidforums.com/htc-droid-eris/56647-boot-animation-gallery.html
wdl1908 said:
Some tests need to be done to find a good size.
Click to expand...
Click to collapse
OK so this works great on the 70. I used 800x480 for the images and they fit perfect.
You 101 users should try 1024x600. this is the resolution of the 101 screen. that is how i came up with the size for my 70 so it should work.
I read somewhere on here the size of pics needed for the A101IT needs to be 1200x1024 for the best quality but i have yet to test those exact dimensions. When I read about it from somewhere in here like 3 other people all confirmed the 1200x1024 dimensions as well.
(It may be the same for the A70IT too but probably not due to the 70 and 101 size difference)?
As a side note, getting bach to the bootscreen animation, how would I go about applying a new bootscreen because I downloaded a new one and thought it would apply itself but didnt, any ideas?
spicy_puerto_rican said:
I read somewhere on here the size of pics needed for the A101IT needs to be 1200x1024 for the best quality but i have yet to test those exact dimensions. When I read about it from somewhere in here like 3 other people all confirmed the 1200x1024 dimensions as well.
(It may be the same for the A70IT too but probably not due to the 70 and 101 size difference)?
Click to expand...
Click to collapse
1200x1024 is the size of the wallpapers the max size of the boot animation should be 1024x600 for A101IT
spicy_puerto_rican said:
As a side note, getting bach to the bootscreen animation, how would I go about applying a new bootscreen because I downloaded a new one and thought it would apply itself but didnt, any ideas?
Click to expand...
Click to collapse
copy bootanimation.zip to /data/customization/
Ahhh, I see! Very much appreciated (wdl1908) for all your help! You know your $hit, thanks!
While searching around I found this site with a lot of boot screen animations http://cid-11d05b676a3170c4.office.live.com/browse.aspx/.Public/Android/bootanimations
Enjoy.
does anyone know if you can add sound to the animation? and if so how?
Here is the bootanimation i made for my 70.Just rename it to bootanimation.zip and paste in the /data/customization folder. (if that folder does not exist then just make it) I have more if you would like them let me know.
To Saprano614, WDL1908, or anyone else....
How do I apply a new custom boot screen animation??
I've tried numerous times putting new bootscreen animations in .zip folders in the /data/customization folder I had to create and I'm confused with how it's supposed to be applied?! Do I put it in the /data/customization folder and reboot... because I've done exactly that, time and time again but I still get nothing and it still loads the same boring factory bootscreen? Do I need to do something different or additional?? = ( Also, do I extract the bootscreen out of the zipped folder and put it in the /data/customization folder or just keep it zipped and copy there?
spicy_puerto_rican said:
To Saprano614, WDL1908, or anyone else....
How do I apply a new custom boot screen animation??
I've tried numerous times putting new bootscreen animations in .zip folders in the /data/customization folder I had to create and I'm confused with how it's supposed to be applied?! Do I put it in the /data/customization folder and reboot... because I've done exactly that, time and time again but I still get nothing and it still loads the same boring factory bootscreen? Do I need to do something different or additional?? = ( Also, do I extract the bootscreen out of the zipped folder and put it in the /data/customization folder or just keep it zipped and copy there?
Click to expand...
Click to collapse
you leave the zip as it is, but you have to edit a line and put a line in
/init.rc
first (in init.rc) undocument
Code:
# export ANDROID_BOOTLOGO 1
to
Code:
export ANDROID_BOOTLOGO 1
then, after this existing lines
Code:
service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin net_raw
ioprio rt 4
insert ( or in the newer uruk versions, undocument) the lines
Code:
service bootanim /system/bin/bootanimation
user graphics
group system audio graphics
disabled
oneshot
this gives you the animation after message "switching to rootfs" till the homescreen appears
its also possible to remove the urukdroid logo, but therefore initramfs.cpio.gz has to be edited
(/etc/scripts/init_lib.sh in initramfs)
the second part of uruk animation is in
/system/bin/show_logo.sh
it also can be deactivated by editing the file (but do not delete it, because its used for other things too)
I use the app su file manager & terminal. Conect you tab to your pc paste the bootanimation.zip to the root of your sdcard. Then unplug the usb. Then with su file manager or another superuser permited file browser copy thr bootanimation.zip and then browse to the /data/customization folder. Make sure that it is in the correct /data folder. There is one on the sdcard and one on the device. if u use the file browser I do then hit back button till it asks if you want to exit but hit cancel. Then look for the Data file. That is the one you need. Then reboot. Again must be in the /data/customization folder not the /sdcard/data/customization folder.
woti23 said:
you leave the zip as it is, but you have to edit a line and put a line in
/init.rc
first (in init.rc) undocument
Code:
# export ANDROID_BOOTLOGO 1
to
Code:
export ANDROID_BOOTLOGO 1
then, after this existing lines
Code:
service media /system/bin/mediaserver
user media
group system audio camera graphics inet net_bt net_bt_admin net_raw
ioprio rt 4
insert ( or in the newer uruk versions, undocument) the lines
Code:
service bootanim /system/bin/bootanimation
user graphics
group system audio graphics
disabled
oneshot
this gives you the animation after message "switching to rootfs" till the homescreen appears
its also possible to remove the urukdroid logo, but therefore initramfs.cpio.gz has to be edited
(/etc/scripts/init_lib.sh in initramfs)
the second part of uruk animation is in
/system/bin/show_logo.sh
it also can be deactivated by editing the file (but do not delete it, because its used for other things too)
Click to expand...
Click to collapse
Ok this is only needed if you are using uruk. If have rooted using churli's method then my above instructions are all yoi need.
saprano614 said:
I use the app su file manager & terminal. Conect you tab to your pc paste the bootanimation.zip to the root of your sdcard. Then unplug the usb. Then with su file manager or another superuser permited file browser copy thr bootanimation.zip and then browse to the /data/customization folder. Make sure that it is in the correct /data folder. There is one on the sdcard and one on the device. if u use the file browser I do then hit back button till it asks if you want to exit but hit cancel. Then look for the Data file. That is the one you need. Then reboot. Again must be in the /data/customization folder not the /sdcard/data/customization folder.
Click to expand...
Click to collapse
i followed these instrustions yet i still cant get the animation to work im new to all of this but i have done well with my evo lol it cooperates much better than this 101 does though lol please help.
you have root? make sure to copy the .zip file to the /data/customization folder. also it must be named bootanimation.
I did this as well but still no boot screen I'm wondering if the kernel I'm using doesn't support custom boot animations PR if that has anything to do with it at all
Sent from my PC36100 using XDA Premium App
dalton1091 said:
I did this as well but still no boot screen I'm wondering if the kernel I'm using doesn't support custom boot animations PR if that has anything to do with it at all
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
nothing to do with the kernel, you must edit the /init.rc and enable the bootanimation, as written above
I have the Call of Duty boot animation, but for some reason the audio wont work. I also have tried the Xbox 360 boot animation. Even that, will not play the audio. but the FinalThunder.mp3 still plays fine.
Ive checked permissions, file names...rhetorically everything. Anyone got an idea what i might be doing wrong?
which rom are you using.....I'm finding the same problem using CM7 and the Bios boot animation. Haven't really looked into it yet though as I just loaded it this morning.
Will post back if I find anything.........
Stock. I rooted fully. Rootchecker says im fine, and the animation works, but no sound
What I have found that works is you have to have the folders within bootanimation.zip set up the same way as the stock one: android, progress and VZW. I haven't look that far into but it seems like the boot sound is triggered when a certain folder is started. If this is so, replacing the boot animation with another one that isn't structured the same and renaming the mp3 to FinalThunder won't work.
Like, wat do you mean? only thing i got is the bootanimation.zip and FinalThunder.mp3, and its int he same place, as in /system/customize/resource/
Superthrust said:
Like, wat do you mean? only thing i got is the bootanimation.zip and FinalThunder.mp3, and its int he same place, as in /system/customize/resource/
Click to expand...
Click to collapse
There's a folder structure inside bootanimation.zip. I'm not talking about where the zip file stored on the phone. More than like the Call of Duty zip has two folders in it, android and part2. Link me to where you got the boot animation and I'll fix it for you.
zhp pilot said:
There's a folder structure inside bootanimation.zip. I'm not talking about where the zip file stored on the phone. More than like the Call of Duty zip has two folders in it, android and part2. Link me to where you got the boot animation and I'll fix it for you.
Click to expand...
Click to collapse
Ill try to attach the ones i have.
Looking inside them both, stock bootanim has no folders. But the COD one does. As for the audio, FinaltHUNDER works but cod-finalthunder wont. (no, i didnt name it that lol)
As i said before, the boot animation works PERFECTLY, just the audio is not working
Try this. Works with sound on my phone. http://www.mediafire.com/?2fvuc65eqdcfdp3
testing. will post with results.
Also, could you maybe tell me what you did? I really want to learn. I have some others i'd like to get working, as well as some ideas I am building with some friends. They know the stuff, but they are in classes and doing finals..I don't have the luxury of college.
Also, is there a way i can adb into my phone and auto-achieve r/w on my system folder? Right now, i have to use RootExplorer and mount as R/W since adb always tells me "unable to push, blah blah, read only filesystem"
It works. Perfectly. Cept the audio is unsynched but that will be easy for me to fix. Thank you so much. What did you change, my awesome savior?
Superthrust said:
testing. will post with results.
Also, could you maybe tell me what you did? I really want to learn. I have some others i'd like to get working, as well as some ideas I am building with some friends. They know the stuff, but they are in classes and doing finals..I don't have the luxury of college.
Also, is there a way i can adb into my phone and auto-achieve r/w on my system folder? Right now, i have to use RootExplorer and mount as R/W since adb always tells me "unable to push, blah blah, read only filesystem"
Click to expand...
Click to collapse
All I did was set the folder structure the same way the stock one is, with android, progress and VZW and made sure desc.txt was formatted properly.
If you are using adb, instead of using Root Explorer to mount system, try command
Code:
adb shell sysrw
Of course this command all depends on how the ROM is set up that you are using.
So, say im using a new bootanimation. Copy/pasta the desc text file, and make sure the structure inside is the same way?
adb shell sysrw says permission denied. im using rooted stock.
Superthrust said:
So, say im using a new bootanimation. Copy/pasta the desc text file, and make sure the structure inside is the same way?
Click to expand...
Click to collapse
Simple break down: android folder contains the first image of the boot animation; the one some people thinks is a second splash screen. VZW folder contains the actually boot animation images and progress is the last image display at the phone is booting. Place your boot animation images in these folders accordingly. I would suggest just putting a plain black image in the android folder and name the image the same as the stock "second splash" screen.
Use the desc.txt file from the boot that I sent you. The only thing you will need to change is the frame rate to make it work with other boot animations. So if a boot is supposed to be displayed at 10 fps, change the 30 to 10 and save.
Once you have everything the way you want it, zip all three folders and desc.txt using the store, or no compression, option. Now you are ready to go. Like you mentioned earlier, you may need to edit FinalThunder.mp3 to make it sync correctly.
About adb sysrw command; stock RUU is not up for that command. Not sure what the syntax would be for stock root or if you can even mount the system as R/W through adb.
dont think i can. and i thnk i gotta lower the fps a little ont he animation
zhp pilot said:
Simple break down: android folder contains the first image of the boot animation; the one some people thinks is a second splash screen. VZW folder contains the actually boot animation images and progress is the last image display at the phone is booting. Place your boot animation images in these folders accordingly. I would suggest just putting a plain black image in the android folder and name the image the same as the stock "second splash" screen.
Use the desc.txt file from the boot that I sent you. The only thing you will need to change is the frame rate to make it work with other boot animations. So if a boot is supposed to be displayed at 10 fps, change the 30 to 10 and save.
Once you have everything the way you want it, zip all three folders and desc.txt using the store, or no compression, option. Now you are ready to go. Like you mentioned earlier, you may need to edit FinalThunder.mp3 to make it sync correctly.
About adb sysrw command; stock RUU is not up for that command. Not sure what the syntax would be for stock root or if you can even mount the system as R/W through adb.
Click to expand...
Click to collapse
I tried changing the FPS and i hit save. I saved it also in the .zip and now the boot animation wont work period. What did i do wrong? Only thing i did was change 30p to 27p
Superthrust said:
I tried changing the FPS and i hit save. I saved it also in the .zip and now the boot animation wont work period. What did i do wrong? Only thing i did was change 30p to 27p
Click to expand...
Click to collapse
Did you open it from within the zip file and save it? If so, when you saved it, the zip was updated and probably changed the compression ratio to the default of whatever program you are using.
zhp pilot said:
Did you open it from within the zip file and save it? If so, when you saved it, the zip was updated and probably changed the compression ratio to the default of whatever program you are using.
Click to expand...
Click to collapse
so what compression method do i have to use to make this work correctly? Cause i need to fix the audio again.
Superthrust said:
so what compression method do i have to use to make this work correctly? Cause i need to fix the audio again.
Click to expand...
Click to collapse
None. Use store option or no compression.
Hey guys, I'm looking for and audio thread that would help with a GB lockscreen, I have ran across one or know if there is one but I found this one and may one of you could help me?
I want to change or I should say make an audio sound for when I unlock my GB Rom. Is that possible? I also wanted to combined in two audio sounds. Any help would be great and appreciated. Thanks
*WALK in the WORD*
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
deathsquad737 said:
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
Click to expand...
Click to collapse
You know there is already a flash for this and an apk.
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
deathsquad737 said:
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
Click to expand...
Click to collapse
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
tech_head said:
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
Click to expand...
Click to collapse
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
deathsquad737 said:
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
Click to expand...
Click to collapse
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
tech_head said:
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
Click to expand...
Click to collapse
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
deathsquad737 said:
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
Click to expand...
Click to collapse
I can always get you a copy of the file.
tech_head said:
I can always get you a copy of the file.
Click to expand...
Click to collapse
Yes please I pm you
A.L.B/E.B.B
Thank you but...
First of all, thanks for the post. Although I appreciate the helpful post, my phone is now stuck in boot loop . I hate to be the one to open up an old thread but I'm freaking out at the moment due to brick fever :crying: My current setup was a rooted LG G3 VS98512b. My goal was simple, I didn't want to do anything crazy, I just wanted to enable wifi tether now I'm afraid I've lost everything... Is there a way I can get back into the storage of my phone and delete the modified build.prop, remove the ".bak" from the original and be back to the good life? Any assistance is greatly appreciated, this seemed like such a simple modification that led to such a big headache.
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
trent999 said:
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
soundmasterx said:
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
Click to expand...
Click to collapse
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Digital_MD said:
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Click to expand...
Click to collapse
Again, thank you for the response. Do you recommend a specific method or tutorial for trying restore the original build.prop? I did search however, because this scenario is so specific I'm not sure there is an exact solution to my problem.
Again, just in case someone else can chime in, I followed the instructions on the first post of this thread (see first post for detailed info). I copied the original build.prop then changed the name of the original build.prop, edited the copy, moved it to the original directory and restarted the phone. Now my phone doesn't make it to the Verizon screen (I think it is stuck in boot loop), the screen stays black and the small led on the left corner flashes blue and green. If I can just get access to the storage I can replace the modified build.prop with the original that is still in the same directory just renamed. It seems like such an easy task but, I just don't know how to go about it I'm a somewhat of an old school tinker, I'm just now getting back into the swing of Android... Thanks in advance!!
Bump
Bump please
This is crazy... I changed 2 values in build.prop for tethering and my phone wont boot now... I didnt install a ROM, change DPI, or make any major changes WTF???
Do you have a custom recovery (twrp)?
Can you connect to your phone with adb?
If you have twrp, search the board for the startup hardware key sequence to reach twrp, else from adb do a reboot recovery.
In twrp, you can select to mount system, then go to advanced - file manager. You can delete the bad build.prop, rename the good one, then set the permissions on the good one. If your good copy of build.prop is on a PC, put it on a flash drive, and use twrp's file manager to get it into your phone.
If you have a saved copy of build.prop on your PC, you can also use adb's push command. (You may also want to look at the adb shell command. The sequence might be to open a shell, delete the bad build. prop, get the right build.prop into the right directory, then chmod the right build.prop so it has the proper permissions.)
The title says it all.
Already tried:
I tried to pull build.prop and default.prop from the phone and edit them to enable debugging but that results in a bootloop. Also tried another method which requires to unpack a boot.img and edit files in the ramdisk but the ramdisk folder is empty after unpacking boot.img.
Why ?
Ans. I messed up my resolution and DPI and i think i can reset it via adb shell.
Thread here :
https://forum.xda-developers.com/poco-f1/help/help-messed-screen-resolution-dpi-t3945921
Try this:
Pull the file "settings_global.xml" from "/data/system/users/0/"
Search for attribute "development_settings_enabled" and change the "value" and "defaultValue" to 1.
Search for the attribute "adb_enabled" and change the "value" and "defaultValue" to 1.
It should enable the USB Debugging.
gaurav.5125 said:
Try this:
Pull the file "settings_global.xml" from "/data/system/users/0/"
Search for attribute "development_settings_enabled" and change the "value" and "defaultValue" to 1.
Search for the attribute "adb_enabled" and change the "value" and "defaultValue" to 1.
It should enable the USB Debugging.
Click to expand...
Click to collapse
Edited and Replaced the file as per your suggestions but adb isn't still enabled on boot. Also, when i pulled the file back, only the "development_settings_enabled" attribute had stick to "1" whereas "adb_enabled" was still "0"
Any more suggestions as to how to enable it ?
or do you know where the display size and density settings reside in the form of a file so that i can replace them with the correct one .
Fyi i need to enable adb t reset display size and density .
More info here:
https://forum.xda-developers.com/poco-f1/help/help-messed-screen-resolution-dpi-t3945921
I am in real distress. I don't want to lose my apps and settings :crying::crying:
MasterFURQAN said:
Fyi i need to enable adb t reset display size and density .
Click to expand...
Click to collapse
Try this:
Pull the file "settings_secure.xml" from "/data/system/users/0/" and change the value and default vaule for the attribute "display_density_forced" to 375
gaurav.5125 said:
Try this:
Pull the file "settings_secure.xml" from "/data/system/users/0/" and change the value and default vaule for the attribute "display_density_forced" to 375
Click to expand...
Click to collapse
I don't know what I did but I somehow made it work. I was about to give up when I accidentally restored back the nandroid backup and I thought "I might as well give it a last shot". I did a lot of things including copying some of the props and XML files and many more things and it booted without any problems except that it wasn't accepting my lockscreen password which is quite easy to fix. Thanks to you for bearing this with me.
After all of this, I think it isn't possible to enable USB debugging via recovery (or by editing props) on MIUI or maybe it's because I'm still encrypted.