Database Users

[Q] Keep DPI after flashing CM nightlies?

I like to update CM every night with CyanDelta, but one drawback with this phone is that every time I do, it resets to the default DPI. The default DPI, 460, is way too big for me, and I like to have it around 360. Is there any way I can change this every time I flash without having to edit the build.prop each time? Thanks!

I'm kind of curious about this too. although a quick search tells me that it basically isnt possible unless you either create a zip to change it and flash that every time you flash a new nightly, or set an app to auto start when you boot the phone to change it. You would have to reboot once again to get the change.

teeg07 said:
I'm kind of curious about this too. although a quick search tells me that it basically isnt possible unless you either create a zip to change it and flash that every time you flash a new nightly, or set an app to auto start when you boot the phone to change it. You would have to reboot once again to get the change.
Click to expand...
Click to collapse
I've thought about making a zip to flash it, but doesn't build.prop change with every nightly? I wonder if there is a way to make a script that will just find and change the DPI in build.prop.

any updates on this? I have been struggling with this problem for years. I've also tried different software to change it but it does often break my play store for some reason so I do it manually every time.

i would like to know if that's possible, too...
it should be, despite the build.prop changing with every build, i assume(!) the lines (read: line numbers) remain the same... so, one could write a script, that changes EXACTLY the necessary line ("ro.sf.lcd_density=[whatever value is preferred]", i for one change it to 400 instead of 480), while leaving the rest untouched... and even if the line numbers change, could one find the line and replace it?
correct me if i'm wrong, please
If i knew how to write scripts for android (or better TWRP for that matter), i'd do it myself, but i have no idea...

I don't have a g2 but I was googling for this exact thing and turned up here... There has to be a way to create a .zip to flash with updates... i just don't know how
upon further googling i turned up this -
http://forum.xda-developers.com/showthread.php?t=2405288

here http://forum.xda-developers.com/showthread.php?t=2612552
Sent from my LG-D802 using xda app-developers app

[Q] Nexus 4 not bootin afer modifying build.prop :(

Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd

1828
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....

AntiFanBoy said:
Hey guys,
I hope you can gibe me a hint how to get my Nexus 4 alive again.
Short intro:
- Phone fell of the desk => display broken
- Sent it to a repair company and received it working again, except the proximity sensor
=> this seems to be a common issue after screen replacements as I found out
- Unfortunately I left my brain at home today and I tried to disable the proximity sensor manually (read in this thread: http://forum.xda-developers.com/showthread.php?t=1626611). Didn't see this was for a Desire S ...
- After adding the line "gsm.proximity.enable=false" to the /system/build.prop file the phone won't boot anymore .... the CM11 boot animation isn't appearing
So, the phone is rooted. I am running CM11 M8 and CWM 6.0.2 (no touch).
So the plan was to alter the file via adb again, but I'm not able to access the phone in any ways.
The Nexus 4 Toolkit however recognizes the phone (with serial Number) and if the phone is in fastboot or ADB Mode. But when ein try to pull files from the device the toolkit says, that I don't have a unsecure boot image ... the adb functions doesn't seem to work either ...
But maybe I'm just not clever enough ...
Have you guys an idea how to get my phone back to life again? I assume wipen the phone will not fix the problem, since there seems to be an important system file corrupted (despite loosing all my data :crying
Hoping for helping words. Thanks in advance.
Gerd
Click to expand...
Click to collapse
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I don't suppose you made a nandroid and can just restore that.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.

AntiFanBoy said:
Hi,
due to the lack of free space, I haven't. But as you can read above, the problem was solved.
Click to expand...
Click to collapse
whenever that happens again, just re set the file permission, when you change a file, sometimes it can change it´s permission.
if didnt get to bootanimation after modifying build.prop, the permissions of it are wrong, just set them back to 644 or rw-r-r

Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false

AntiFanBoy said:
Hi,
thanks for you comment. :good:
actually I changed the rights by myself to 666, so I can modify it, but didn't change the permissions back.
So you thinks the permission was the problem and not the content of the file?
I added this line:
gsm.proximity.enable=false
Click to expand...
Click to collapse
Yes, this is a common problem as far as I know
If you use TWRP as your recovery (not sure if it's possible with cwm, too) you can use the built-in file explorer to navigate to the build.prop and set the permissions. Just reboot and it should work fine again

If you can enter recovery do a factory reset

Mashed_Potatoes said:
If you can enter recovery do a factory reset
Click to expand...
Click to collapse
Well, I'd say this would be the last option as he'd lose all his data. Maybe there's another way to fix the problem

no need for factory reset, in case like this refleshing the rom will do the job. there is no need for wipe or anything just flesh the same rom again and everythink will be ok

Hey guys,
looks like I didn't express myself clearly enough
Don't use Nexus Toolkit ... use the native Google Android SDK and everything works fine ....
Click to expand...
Click to collapse
Besides the problemative build.prop file, the nexus 4 toolkit was the problem. After using the standard Android SDK I was able to push a CM Image onto the phone via adb and simply updated the os and everything was fine again. Don't know why the toolkit spun around, always worked fine, but this now thought me a lesson => back to the roots
Resetting the phone to factory defaults/wiping everything wouldn't have solved the problem I assume.
Thanks guys.

Please read:http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909

[Q] Messed up my phone

Hello!
I have messed up my Note 3 a lot. When booting it up, it gives me error "Unfortunately, com.sec.android.sviewcover has stopped." This comes up instantly again after pressing the "OK" button (I have 0.5 seconds to do something between these errors). After entering the PIN code and unlocking the lock screen I get the error "Unfortunately, TouchWiz Home has stopped (and just shows a black background)." I can still access the settings by pulling down the Action Bar.
I'll start with some background facts:
- Rooted my phone about 3 months ago. It has worked great this far.
- Today I managed to enter a too high value in the "Textdroider DPI" app, and after restarting the problems began.
Now I've factory reset the phone as that was the only thing I could do but that didn't change anything.
I'm so screwed. Can anyone help me?
EDIT: It's a Note 3 SM-N9005 N9005XXUGNG1

I had the same thing happen on my Note 10.1 the other day while messing around with DPI settings. Touchwiz doesn't play nicely with different screen densities and it crashes. There is a file in the /system folder called build.prop. Inside this file there will be a line that looks like this:
Code:
ro.sf.lcd_density=###
.
On a completely stock N9005 (I have the exact same model) this value should be 480. All you need to do is edit this line and reboot.

teh_geek said:
I had the same thing happen on my Note 10.1 the other day while messing around with DPI settings. Touchwiz doesn't play nicely with different screen densities and it crashes. There is a file in the /system folder called build.prop. Inside this file there will be a line that looks like this:
Code:
ro.sf.lcd_density=###
.
On a completely stock N9005 (I have the exact same model) this value should be 480. All you need to do is edit this line and reboot.
Click to expand...
Click to collapse
Firstly, thanks for your reply!
Is there any way I can access the /system folder from my computer?

Skrube said:
Firstly, thanks for your reply!
Is there any way I can access the /system folder from my computer?
Click to expand...
Click to collapse
Yes there is. It's a bit technical however and it depends on what recovery you're running. I've managed to solve this problem on my tablet running TWRP.
I also found something else you can try to do to hopefully get rid of the force close messages temporarily. Boot up your phone, connect it to your PC and (assuming USB debugging is enabled) run the following command from a terminal:
Code:
adb shell wm density 480
You mentioned in your previous post that you have rooted your phone, so I'm going to assume you're somehow familiar with commands and ADB
If all goes well, your screen density should change on the fly. Reboot your phone at this stage and if this gets rid of the force close messages and allows you to interact with your device, it should be quite easy to edit the build.prop file. Just go to the Play Store, install a root file manager (or better yet the application you used in the first place - Textdroider DPI) and edit the file. Make sure you set the density to 480.

teh_geek said:
Yes there is. It's a bit technical however and it depends on what recovery you're running. I've managed to solve this problem on my tablet running TWRP.
I also found something else you can try to do to hopefully get rid of the force close messages temporarily. Boot up your phone, connect it to your PC and (assuming USB debugging is enabled) run the following command from a terminal:
Code:
adb shell wm density 480
You mentioned in your previous post that you have rooted your phone, so I'm going to assume you're somehow familiar with commands and ADB
If all goes well, your screen density should change on the fly. Reboot your phone at this stage and if this gets rid of the force close messages and allows you to interact with your device, it should be quite easy to edit the build.prop file. Just go to the Play Store, install a root file manager (or better yet the application you used in the first place - Textdroider DPI) and edit the file. Make sure you set the density to 480.
Click to expand...
Click to collapse
Yes! I got it working now. (had some issues with adb and permissions but got it sorted)
Thanks a lot for your help!

No problem. Glad I could help Just remember to be careful when messing around with screen densities and to always keep a build.prop backup in case something goes wrong

Trying to change model number. build.prop doesn't work

Hello,
I'm trying to change the info displayed in my Model Number in "About phone" in Settings.
I have edited build.prop and even used XPosed with Device Faker. It does display the new Model Number in XPosed or any other application but when going to "Settings --> About Phone" , it still displays the original name, which is grayed-out and it's bugging the hell out of me, the fact that I can't change it.
Does anyone have an idea of what I can do, short of flashing a custom ROM?
I'm using stock ROM and rooted.

What are you editing it with, a build.prop app? I normally used root explorer and have never tried any of the apps for that. I'm guessing they do ask for root privileges and you change the system to write to make the changes and back to read only after the changes?

I tried with XPlore, ROM Toolbox and finally with build.prop editor.
The changes are saved and they reflect in any app that reads from the build.prop file.
However, the Model number stays the same in About phone, in Settings

UzY3L said:
I tried with XPlore, ROM Toolbox and finally with build.prop editor.
The changes are saved and they reflect in any app that reads from the build.prop file.
However, the Model number stays the same in About phone, in Settings
Click to expand...
Click to collapse
Did you search the entire build.prop? It's possible that the name could appear more than once.

Yup, searched and also read it all, lots of times.
It does import some data from oem.prop I think but I checked that and it has nothing related to Model number or device name.
This is very weird and irritating. I tried messing with some more info in build.prop but the phone stopped working so I had to flash the stock firmware again.

UzY3L said:
Yup, searched and also read it all, lots of times.
It does import some data from oem.prop I think but I checked that and it has nothing related to Model number or device name.
This is very weird and irritating. I tried messing with some more info in build.prop but the phone stopped working so I had to flash the stock firmware again.
Click to expand...
Click to collapse
In my phone settings, in the "software channel" part....mine shows "ATTMX". Is it possible to edit that to show something else??

If your rooted get BuildProp Editor in play store.
Sent from my Pixel XL using XDA-Developers Legacy app

rbeavers said:
If your rooted get BuildProp Editor in play store.
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did that. Doesn't work. Motorola went to a lot of trouble to stick that model number there for good. I wonder why?
Doesn't matter anymore. I bought an LG G3. Same size, same battery, much better specs, less battery life. An acceptable tradeoff.
Thank you all for your answers!

Restore original resolution & DPI via sideload .zip OR openrecoveryscript ?

Managed to soft brick my Note 4. Set my dpi to 200, and my resolution to 720p. Apparently, it's just too low. Worked great when I set the values, but restarting the phone caused the brick. (It boots, but can't access anything. Unfortunately, I don't have my PC allowed as ADB, so I can't even connect from that state to ADB.)
So.
My idea to prevent full wipe, is to use ADB sideload OR ORS.
- Sideload. Make a "payload" that will replace the build.prop with the stock one.
- ORS. http://wiki.rootzwiki.com/OpenRecoveryScript
How do I actually do this?
Like the RecoveryScript seems to be a great idea, but from TWRP, I could not find a single build.prop file at all. There is a default prop, but it contains no resolution, dpi or whatever.

So I spent another few hours on this. I hate myself. And I hate the app's developer for being so careless.
- Flashed latest Samsung firmware hoping it will kill the software. Nope. It did not.
- Flashed the .zip for build.prop. NO effect.
The system has the correct DPI value so it must not be the issue.
- I think the app auto runs, and sets resolution. So I tried grep, but it cannot find the "1280" string anywher,e and I also removed the app from /data/app and /data/data.
- I cannot get MTP or ADB working in TWRP whatsoever. Huge letdown, but there is just no support. And without seeing what happens on the screen (it must be just my lockscreen there), I can't accept ADB connections either.

Well, so I went YOLO and cleared data. And... behold, NOTHING.
Did this retarded stupid program killed my phone? Holy hell.

Okay, so full entire wipe + reflash + full wipe, and now it works.
This app? Never again. The others are good on the market, so go for it.
App in question: https://play.google.com/store/apps/details?id=com.chornerman.easydpichanger
[ DO NOT USE !!! ]

Instead of wipes at Restore DPI: You can remove only of "com.android.providers.settings" at "/data".

Sorry but I have to resurrect this. I've played with dpi settings and now after reboot I cannot press enter when I type in my password as keyboard is partly off screen. TWRP is not working as it does not support Android 12. Any chance to resolve this beside flash?
Update: Connected keyboard via OTG cable and managed to unlock

Resurrecting this to offer another solution that doesn't involve any wiping/flashing/restoring-to-stock or messing with build.props
I used the same app as OP and feared the worst when I got stuck on recovery after changing DPI
This method allowed me to restore my xiaomi Redmi 9 with android 10
-You need to have a custom recovery installed
-"shell wm" commands don't work in recovery
You need to edit settings_global.xml & settings_secure.xml found in /data/system/users/0
You can do this by pulling&pushing the files to a PC using adb or editing in recovery using nano editor or something similiar.
Search for:
"display_size_forced" in settings_global.xml
"display_density_forced" in settings_secure.xml
Edit those with something close to your default values, then reboot and that's it!
Now that you're no longer stuck in boot you can reset resolution and density with the usual methods like adb or a better app
I hope this helps anyone else stuck in the same problem I was

mrmrva said:
...TWRP is not working as it does not support Android 12. ......
Click to expand...
Click to collapse
Where did you get a A12 version for which Note4?
Owning a N910F=trlte I don't find any higher than A11.

Don't have Samsung but Poco f2 pro and was looking for solution everywhere so posted here.