Just changed 8.1... love it, smooth as butter, but this 200dpi is destroying my eyesight!!! How do I change it to a larger size? Thanks in advance!!!
If frog's had machine guns... Snakes wouldn't **** with 'em...
OK, finally found it on Google, thank you Jamie... Your ROM... best one anywhere... And I've flashed them all. Thank you very much
i think u will have to edit the build.prop with es file explorer or any file manager u use with root, and find where it shows ro.sf.lcd_density=200 and change to 320 which is stock and when u save make sure u change the permissions to rw- r-- r-- and save and reboot, make sure u make a nand back 1st if u are not sure about modding the build.prop b/c if u edit and don't change the permissions, u will have to reflash.
Permissions - x means checked.
-------------Read....Write.....execute
user---------x----------x
group.......x
other........x
My line already says 320. Did you mean change the 320 to 200?
Related
This is the first time I've "developed" anything (if you can call it that) so be easy on me
I made this simple boot animation, it's colorful, clutter free, and crisp.
Preview: The color flame wobbles around, the evo3d text flies in and the wobbling continues
Download: http://www.megaupload.com/?d=O55PBS9Y
Install: place zipped file in /system/customize/resource
You can use adb or root explorer to do this.
Followed the directions but I"m stuck on my old animation. Not sure what's wrong but I would really like to see this one running!
did you use root explorer or adb?
root explorer
Renamed to bootanimation.zip and dropped it in data/local. Works great!
^ works just fine too.
You can also copy over the original (system/customize/resource/Sprint_bootanimaion.zip) if you like.
Good job on the anim. I need to share mine...i made my first one Monday. Its a portion from the 1986 Transformer movie where megatron is being turned into galvatron. I'm a super nerd so may as well nerd up my phone. XD
Edit...not sure on permissoin modification when using it in data/local but you may have to set permissions to
Owner: R W
Group: R
Others: R
to have it work if you copy over the factory. I used the default animations permissions i listed above and never had probs. Didnt see a reason or need to try with unmodified permissions. Just a though =-)
mhmobile said:
Renamed to bootanimation.zip and dropped it in data/local. Works great!
Click to expand...
Click to collapse
Also, you had this work without modifying the default XML to look to that path? Just wanting to make sure i'm understanding because factory default xml explicitly points to the customize folder Sprint_bootanimation.zip.
Thanks!
nice boot animation!
if you're going through adb shell the permissions are 644
so chmod 644 nameoffile
Has anyone changed their DPI? I'd like to make everything a hair smaller. I am on the new ICS leak with root. Will changing the DPI cause touchwiz to break? Should I just wait until a stock rom comes out? If not what tool/settings are known to work?
thanks
bump
Rom Toolbox is the only app that has worked for me in ICS.
Im not sure how touchwiz will react since I use Apex.
Use a root a file explorer, go to /system mount r/w, long press on build.prop open in text editor.
ro.sf.lcd_density= 320
Is the line you're looking for, just change the number to the dpi you want, save, reboot, profit.
hi,
I'm trying to install stock sms app but i can't achieve this. It keeps saying : installation aborded
I am on chameleon rom 1.1 ( hybrid aosp/samsung rom)
Can you help me ?
(sorry if i made mistakes in my post i'm not english XD )
You should copy the apk into /system/app, then change permissions into 644 (rw--r--r), change group and owner to 'root', and finally reboot and try.
gb.yolo said:
You should copy the apk into /system/app, then change permissions into 644 (rw--r--r), change group and owner to 'root', and finally reboot and try.
Click to expand...
Click to collapse
i already tried it and it didn't work. and i am not sur about the about i trid to install because it s difficult to find the stock sms app.
i changed the permissions but i don t understand what you are saying by " 644 (rw--r--r)"
theoricaly it should work since i use an hybrid app ?
With a file manager, backup your mms.apk in /system/app in whatever folder you want. Then, copy the stock mms.apk into /system/app.
You shouldn't click on the .apk and let the app install as you do with other apk files, because this is a system application.
644 means read/write-read-read.
rw-r--r means u set read and write in the owner row , and set read only in the group row , and set read only too in the others row
Note : u get to permissions window in root explorer afer changing r/o read only to r/w read write from the button at the top
then just long click the item u want to change its permissions
i tried what you have said and it didn't work. Is a flashable zip existed ?
up
The stock mms.apk might not be compatible with the custom ROM you have on your phone...
Why do you say it doesn't work? What happens? You open it and it FCs or something else?
I just followed instructions given by posters above and it didn't worked. ( remove the old Mms.apk by the stock one, and fix the permissions, then reboot ) Maybe i don't have the good app, i don't understand why it didn't work; The chameleon rom support stock camera app of samsung and others apps...
piing said:
I just followed instructions given by posters above and it didn't worked. ( remove the old Mms.apk by the stock one, and fix the permissions, then reboot ) Maybe i don't have the good app, i don't understand why it didn't work; The chameleon rom support stock camera app of samsung and others apps...
Click to expand...
Click to collapse
Maybe the pakage cant be praised because of android version differnece , some apks from ics dont work on Jb and vice versa
So if u want a stock sms to work on jb , then download another jb rom that has it and take it from there
For pushing files to system app , it is better to first delete the app u want to replace then do a reboot after that copy the new app to system app and set premissions and set r/w back to r/o
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.)
Hello guys, I have accidentally put a wrong dpi value on developer options>smallest width wich results of a bootloop, I have a rooted phone with twrp recovery, I'm wondering if there is any fix to this problem without losing data, if so I will be so thankful.
imsalahdev said:
Hello guys, I have accidentally put a wrong dpi value on developer options>smallest width wich results of a bootloop, I have a rooted phone with twrp recovery, I'm wondering if there is any fix to this problem without losing data, if so I will be so thankful.
Click to expand...
Click to collapse
U didnt talk andoird version which u r using. Im using android 10. i have a idea but i cant sure it would sussceed. i think u can try:
Option 1: Dirty flash ur rom then see.
Option 2: If option 1 cant help u. Now u need to know adb. U can root so i think u know what abd is. . My idea is push a "build.prop" in system folder then change density value cz i think it is ur "root" problem then pull it again. How can pull and push a file using abd u can find here. https://forum.xda-developers.com/android/general/guide-how-to-adb-to-push-pull-files-t3372710. U need to push file name is "build.prop" in "/system" folder. When u get it, open it with any file manager. search "density". Now change ur number to correct value. U can try change from 392 to 440 cz i see it in many roms or value that u remember. save it and pull "build.prop" back again to /system using adb. Last, try reboot and see. Good luck.
Get a DPI change app from Play store
Sent from my SM-T720 using XDA Labs