Argh, I cant change DPI! - Galaxy Note GT-N7000 General

Hey peeps!
I just flashed to the latest CM9 nightly from RC2 and wiped cache and dalvik. I tried to change the DPI back to 213 as I did before: reading this guide and using Total Commander and editing the build.prop in the /system dirr which worked without any problems in RC2 but now TC or any other file manager cant save the file. I thought first that I didnt have root possibilites but all other apps that require root works and get roots. Whats your idea of this? I tried using ROM Toolbox but I couldnt figure out where to change the DPI there
EDIT: Uhm rather delete this one, Ill post it in the correct thread instead

Same experience with total commander. That's why I copied the build.prop in another folder, edited it and pasted it back into /system. Check the permissions.
ROM toolbox has two options, one with a slider (build prop tweaks) and the other is the editor. Look for ro.sf.lcd_density= 320 and change it there.

AAh thanx! finally away from the horror DPI 320, all mothers nightmare! =)
I bid you thank you kind sir!
AA1973 said:
Same experience with total commander. That's why I copied the build.prop in another folder, edited it and pasted it back into /system. Check the permissions.
ROM toolbox has two options, one with a slider (build prop tweaks) and the other is the editor. Look for ro.sf.lcd_density= 320 and change it there.
Click to expand...
Click to collapse

You can manualy change it with Root Explorer too. This is the only safe file explorer which doesn't kill you ROM if you change lcddestiny setting with it.

Related

Webtop / Gingerblur Media Center Video Problem Fixed.

Posted this in the gingerblur thread, but I thought I'd post it here too:
Swiftks said:
S U C C E S S!!! That is how we spell success!
So that worked... If you are experiencing video issues with Gingerblur and/or the webtop mod (i.e. your videos are not playing in the entertainment center). Here is what you need to do for an easy fix:
Edit the build.prop file @ /system/
There should be a line in the build.prop file that says: "ro.hdmi.mirror.enable=true"
You need to change the true to false. Then reboot, and you are good to go!
You can either copy the build.prop file w/ root explorer and edit it on your pc (I use Notepad ++) and then copy back and replace the original file. Or, you can edit directly in root explorer; simply long press and select edit with txt editor. Make sure that you mount the system as r/w first though, so you can edit the file (on top line in root explorer).
Hope this helps some of us that were having this issue.
Click to expand...
Click to collapse
thx ,will have a try.
thanks
I just tested his instructions using windows and plain ol notepad this fix is really easy even if you only have basic system and root access understanding. thanks op!
thank you man!!! i got all excited about gingerblur 3.5 & being able to record 1080p video.. it was a huge let-down when i couldn't view any of them on my big screen to test out the quality.. this fixed it perfect! i used Super Manager (enable Root function) to email the build.prop file to myself.. edited it in ubuntu with text editor, emailed it back to myself, deleted the original build.prop, pasted the modified one back into \system & rebooted
works like a charm
This worked for me but when I play a avi file there is no sound. What should I do?
You are the Man
Cheers

How to edit Mod Version?

Hello!
Not intented as a spam, but i need some help.
I cannot edit Mod Version. whenever i edit it and reboot, all my changes are deleted.
I cannot change anything in my build.prop
I used Root Explorer, Liberty toolbox, did changed the name of the ROM using kitchen and also replaced my build.prop before signing it.... but nothing helped.
anyone can please help?

Need help with build.prop edit

I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Hi,
Same thing for me with Root Explorer, instead I use build.prop Editor
EDIT: not fast enough :laugh:
qsec said:
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Click to expand...
Click to collapse
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.
Maybe it's related to my root access? TB is showing I'm rooted, but check out my superuser app when I try to update an install new binaries...
Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.
EniGmA1987 said:
Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.
Click to expand...
Click to collapse
Downloaded and installed... Removed the old one. Still not letting me edit... Looks an feels like it is but won't enter any characters. At least RE isn't giving me the "too large" error anymore
in_dmand said:
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.
Click to expand...
Click to collapse
i had the same issue, couldn't figure out why. try replacing a commented line with the code to disable the nav bar
How do I know if it's just a commented line and not necessary to the program?
in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
i had the same issue any help?
If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app
maxkanick said:
If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
You are right, I have tried to edit it on pc and stuck on a bootloop.
Use build.prop editor app from playstore
_____________________________________Read more write less and be smart

[Q] Can't save build.prop edits - Rooted MF3

Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
synesthesiac said:
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
Click to expand...
Click to collapse
Hello,
I was trying to edit the build prop file using the ES Explorer, but the same happened to me, I could edit the file by downloading the "build prop editor" from play store.
Edit the file by pressing the button in shape of a pencil and later press the save button. If you only search for the line you want to edit in the main screen of the app you will be able to modify the line but the changes are not saved.
Thanks/rate
synesthesiac said:
Hi, first time poster here. I can usually find what I need, but I'm stumped here.
I'm running a rooted Galaxy S4 on ATT with the i337ucuamf3 build.
I've successfully installed viper4android, but it only works on and off, with Google Music.
I'm pretty sure the fix for this is to change the build.prop lines: Ipa.decode, tunnel.decode and Ipa.use-stagefright.
I've tried everything that I can think of, but I no matter how I make the changes, they will not save. I've tried mounting System R/W in Rom Toolbox, and booting into System R/W. I've made the changes with Rom Toolbox Pro and ES File Manager. Nothing works.
Can anybody tell me if I just can't make these changes to build.prop because of the build I'm running?
Please, any help would be appreciated. When viper does work, it's incredible!
Thanks.
Click to expand...
Click to collapse
Never mind.
ES File doesn't always save, you'll just have to try a different app. Root explorer should work or fx file manager.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Suddenly camera doesn't work!

Hello dudes.Please help me.Just today my camera doesn't work anymore.No one of my 4 camera apps,just black screen!Any idea?i reflashed squid and also coffee kernel but nothing!!!
Peace to all
Bytheway yesterday i edited my build.prop with some 3g and scrolling tweaks.and now i read that this conflicts with camera.i restored the backedup build.prop through builf.prop editor app,but the same result..
permissions was changed,so I had to change them again.thanks
Peace to all
kos25k said:
Bytheway yesterday i edited my build.prop with some 3g and scrolling tweaks.and now i read that this conflicts with camera.i restored the backedup build.prop through builf.prop editor app,but the same result..
permissions was changed,so I had to change them again.thanks
Peace to all
Click to expand...
Click to collapse
What ROM are you using? Either way, you'll probably need to re-flash the ROM. The same thing happened to me before. I edited the build.prop and it caused my camera to force close. Had to re-flash the ROM because restoring the build prop didn't work for me either.
Stock rom.after a lot of search and one step from reflashing the rom...i realized that the restored build.prop permissions from rw-r-r changed by it's own to rw!so i just set them back to default permissions and all is ok now!i wonder also if my camera f.close was causing also from this.(i mean with just editing the build.prop,not the restored one)i made the restore process with root explorer finally.before this i edited b.p with the b.p app from playstore.
Peace to all

Resources