Folks
I'm rooted and running Shamu 3.97. I used ADB to wrongly change my DPI. I ran the command
adb shell wm density 560480 (was using up arrows and by mistake didn't clear out the 560 before inputting 480)
Immediately, the phone rebooted and is stuck at the boot - little circles going around but doesn't move beyond that. Is there a battery pull that can be done on this device and what's my resolution? Do I have to somehow get into recovery and change the DPI to native 493?
Thx
You dont change DPi in bootloader or recovery, you need to edit it in build.prop or you can download dpi changer from play store
I got access to recovery but cannot boot the phone up since it just gets stuck on the rotating color circles. Any way to edit build.prop from recovery? I can see my Internal storage on my computer but can't find the build.prop file anywhere
did u do a backup on ur phone before dpi change? it could be u changed to the wrong dpi. Worst case scenario is flash back stock rom ...
sam008 said:
I got access to recovery but cannot boot the phone up since it just gets stuck on the rotating color circles. Any way to edit build.prop from recovery? I can see my Internal storage on my computer but can't find the build.prop file anywhere
Click to expand...
Click to collapse
Just re-flash the rom
Sent from my Nexus 6 using XDA Free mobile app
Related
is it possible to change the resolution of htc legend..........i tried lcd density but no use ...i am using azure cyanogen mod 6.....
i tried to edit the build pro..but no use
some one help me.......
Change Your Screen Resolution on HTC Evo 4g
I have successfully done this now. Remember that we don't have root in the same way that the EVO 4G does.
So:
Using any file manager that can read the / partition of your phone find and copy "/system/build.prop" onto your SD card.
Now copy the file to your desktop, and take a backup of that file too.
Open notepad and make sure word wrap is on, then open build.prop in notepad
Edit the required value (I chose 120), save and copy the file to your ADB/tools directory
Reboot your phone into clockworkMOD recovery, and connect your phone to the PC. Also go into the partitions menu of ClockworkMOD and click "mount system"
Open up ADB, and run "adb devices" to make sure the phone is connected and everything is working
Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
Then reboot your phone.
Let me know if this helps
Also, for other readers:
Make sure you read the post that is linked to in the above post, otherwise my instructions might not make sense... I might edit it later when I have time
@TheGrammarFreak
What is the resoultion of your screen now?
qzem said:
@TheGrammarFreak
What is the resoultion of your screen now?
Click to expand...
Click to collapse
I dunno how I'd work it out, sorry.
Ah...
I think I've found the first of many flaws with this, and it was mentioned in the EVO 4G post. Some apps ignore this and use the old resolution, and thus don't fill the screen (see attachment)
As you can the the status bar goes a lot wider than the app. The status bar is the full width of the screen.
Other problems arise too, a reinstall of the app doesn't help, and some apps just end up completely screwed...
qzem said:
@TheGrammarFreak
What is the resoultion of your screen now?
Click to expand...
Click to collapse
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
grandioso said:
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
Click to expand...
Click to collapse
Cool, thanks grandioso
On a slightly different note I've found that changing the value to 130, and using the 5 icon rows feature of launcher pro, is quite nice.
grandioso said:
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
Click to expand...
Click to collapse
Thanks for clearing that .
There are some problems, but if you want to try it out, you can flash the update.zip I've just made.
160lcd.zip takes you back to default and 120lcd.zip makes your screen resolution higher.
@Briix
Can you make update for 130, like TheGrammarFreak suggested
I'd make one but I'm currently struggling to sign my .zip
EDIT:
Done it, just testing then I'll upload. I also notice that ROM Manager is one of the apps that ends up being screwed by this mod...
EDIT 2:
Wow, lots of edits. Anyhoo, 130lcd right here:
really nice
TheGrammarFreak said:
I have successfully done this now. Remember that we don't have root in the same way that the EVO 4G does.
So:
Using any file manager that can read the / partition of your phone find and copy "/system/build.prop" onto your SD card.
Now copy the file to your desktop, and take a backup of that file too.
Open notepad and make sure word wrap is on, then open build.prop in notepad
Edit the required value (I chose 120), save and copy the file to your ADB/tools directory
Reboot your phone into clockworkMOD recovery, and connect your phone to the PC. Also go into the partitions menu of ClockworkMOD and click "mount system"
Open up ADB, and run "adb devices" to make sure the phone is connected and everything is working
Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
Then reboot your phone.
Let me know if this helps
Also, for other readers:
Make sure you read the post that is linked to in the above post, otherwise my instructions might not make sense... I might edit it later when I have time
Click to expand...
Click to collapse
thanks man its working...........
Has anyone tried GrammarFreak's zip ?
Are there any problems with it ? Is it worth the effort ?
Do I have to wipe for this to work ?
Explicitly my zip? Or any of the zip's in this thread?
No wipe is needed.
Also, this method is inherently flawed. Some apps just don't use the edited resolution. Unless a way can be found to force these apps to scale up then there will always be ugly moments.
One of the things that I've found to not work is the HTC-IME mod. So is it worth it? That for you to decide... Lol
Sent from my Legend using XDA App
I mean yours or Briix' - are there any others ?
I don't want to edit the file manually if I don't have to
grandioso said:
Has anyone tried GrammarFreak's zip ?
Are there any problems with it ? Is it worth the effort ?
Do I have to wipe for this to work ?
Click to expand...
Click to collapse
Yup.. Tried.. working like a charm..
-------------------------------------------------------------------
Could you make a 140 and a 110 .. Just to try and see the result!?
I'll gladly test them both..
whitetigerdk said:
Yup.. Tried.. working like a charm..
-------------------------------------------------------------------
Could you make a 140 and a 110 .. Just to try and see the result!?
I'll gladly test them both..
Click to expand...
Click to collapse
I'd love to, but I can't at the moment, I'm at school and didn't bring my laptop. Unless someone beats me to it I'll make one in about an hour and a half; when I'm home.
I did try 140 myself but I didn't think it was worth it. I use 5 icon rows in launcher pro and the widgets started overlapping again. Like they did in the default resolution.
Sent from my Legend using XDA App
I'll wait..
Would be great though if WF & Clock Widget (The Sense look Clock) would adapt to new screen and fill it out..
Totally sweet indeed..
Yeah, if I knew more about android I'd look into forcing apps to scale up. I'm not sure if it's even possible, but hey.
Sent from my Legend using XDA App
Ok so here's the newb in me. I was trying to get Netflix working on my rooted NC. I made a backup of build.prop by making a copy and renaming it build.prop.bak. I went into build.prop to change the product model and manufacturer. I did that, saved and rebooted but Netflix still did not work...whatever.
I decided to give up for the night, so I went back into /system and renamed build.prop.bak back to build.prop. At this point I had 2 build.prop files. I deleted the modified one to find out that both had been deleted.
i thought a reboot (again newb mistake) would magically restore the build.prop file (hind-sight says obviously it wasn't going to). It reaches the "n" screen and then the screen flashes black.
Is there a way to fix this without reflashing? I know there this thread:http://forum.xda-developers.com/showthread.php?t=949699
I did use Titanium Backup to back up all my "stuff" on the SD card if that means anything. Again, sorry for the dumb questions.
Any help would be appreciated!
Easy method - re-flash your ROM without clearing data. Will also overwrite any other tweaks.
More difficult method. Extract the build.prop from the ROM you are using. Boot into CWM and push the build.prop using ADB.
Sent from my NookColor using XDA App
martian21 said:
Easy method - re-flash your ROM without clearing data. Will also overwrite any other tweaks.
More difficult method. Extract the build.prop from the ROM you are using. Boot into CWM and push the build.prop using ADB.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
so for easy method, are you referring to setting up a bootable SD card with Clockwork Mod and reflashing ManualNooter?
NookyLov3r said:
so for easy method, are you referring to setting up a bootable SD card with Clockwork Mod and reflashing ManualNooter?
Click to expand...
Click to collapse
My bad. I assumed you were on CM7.
Since you are on stock B&N, your options now are pretty much flash one of the stock images (and lose everything - ie. return to stock) or extract the build.prop from the stock image, boot into CWM, and ADB push the build.prop.
Sent from my NookColor using XDA App
Yeah. This is what I ended up doing...such a PITA. Oh well, at least it can be done this way. Thanks for the help!
Change the dpi on your Galaxy S5!
Requirements: Root, Supersu, and a nandroid or build.prop backup to go back to in case you mess up.
I tried this out on the Stock S5 Rom and the Extreme Debloat 2.1.2 Rom
1. download build.prop editor from the play store.
2. Click on the '+' at the bottom, click predefined properties, then find ro.sf.lcd_density then put in the desired dpi value.
3. 480 is stock for the S5, 422 is what you see when you use a rom-slot When you make the change, approve it with Supersu. Make sure it happens.
4*. If you're being safe and using a rom slot to try this out, you have to shutdown the device, let it vibrate, then take out the battery because the shutdown sequence freezes. After that pop it back in and turn on your phone. If you're on the stock slot, just reboot
5. If you're new dpi number works, your phone will boot properly, if it doesnt you will get a 'device memory damaged' alert and even if you click 'reset device' it will continue to do this whenever you turn on your phone forcing you to restore the build.prop or nandroid with a backup.
Apparently, my method overwrites the hidden ro.sf.lcd_density that doesnt appear when you search build.prop with a new and visible one! Hopefully I've discovered something that will contribute to this board. Enjoy!
To fix the small camera problem, you can use xposed framework module app settings and change the dpi back to 480. Im having difficulty fixing it for the phone dialer. Hopefully somebody can find the solution.
Please post working dpi's below.
Confirmed working dpis: 480, 422, 420
psm510 said:
Change the dpi on your Galaxy S5!
Requirements: Root, Supersu, and a nandroid or build.prop backup to go back to in case you mess up.
I tried this out on the Stock S5 Rom and the Extreme Debloat 2.1.2 Rom
1. download build.prop editor from the play store.
2. Click on the '+' at the bottom, click predefined properties, then find ro.sf.lcd_density then put in the desired dpi value.
3. 480 is stock for the S5, 422 is what you see when you use a rom-slot When you make the change, approve it with Supersu. Make sure it happens.
4*. If you're being safe and using a rom slot to try this out, you have to shutdown the device, let it vibrate, then take out the battery because the shutdown sequence freezes. After that pop it back in and turn on your phone. If you're on the stock slot, just reboot
5. If you're new dpi number works, your phone will boot properly, if it doesnt you will get a 'device memory damaged' alert and even if you click 'reset device' it will continue to do this whenever you turn on your phone forcing you to restore the build.prop or nandroid with a backup.
Apparently, my method overwrites the hidden ro.sf.lcd_density that doesnt appear when you search build.prop with a new and visible one! Hopefully I've discovered something that will contribute to this board. Enjoy!
To fix the small camera problem, you can use xposed framework module app settings and change the dpi back to 480. Im having difficulty fixing it for the phone dialer. Hopefully somebody can find the solution.
Please post working dpi's below.
Confirmed working dpis: 480, 422, 420
Click to expand...
Click to collapse
Good work. Been seeing people trying to do this. hopefully you found the correct fix. Thanks for letting the community know.:thumbup:
I changes dpi to 380 but lock screen is smaller, contacts etc....i changes dpi back to stock inside app with xposed appsettings... All work good only lock screen still small... I don't now find files for edit for biggest lockscreen..
Druss81 said:
I changes dpi to 380 but lock screen is smaller, contacts etc....i changes dpi back to stock inside app with xposed appsettings... All work good only lock screen still small... I don't now find files for edit for biggest lockscreen..
Click to expand...
Click to collapse
You would change SystemUI, that changes the notification bar/panel as well though among other things and makes having your dpi lower pretty much pointless in my opinion.
Sent from my SM-G900A using Tapatalk
Can someone please post the Build.prop file of the stock 6.0.1 Firmware? I killed mine while trying to edit DPI (http://forum.xda-developers.com/nexus-6/general/issues-editing-build-prop-marshmallow-t3222551)
You're best bet is to download the image from Google and flash system.img in fastboot. If you "killed it" because there wasn't space to save it, you won't be able to replace it either (without deleting some apps from /system).
Sent from my Nexus 6 using Tapatalk
Fracoon said:
Can someone please post the Build.prop file of the stock 6.0.1 Firmware? I killed mine while trying to edit DPI (http://forum.xda-developers.com/nexus-6/general/issues-editing-build-prop-marshmallow-t3222551)
Click to expand...
Click to collapse
If all you did was set a DPI then just set it back to 560 (the default).
If you like nuked the whole file and theres nothing left to salvage with then yea flash the system.img out of the factory image pertaining to your current build number. Probably heard this numerous times but Backup backup backup. It can save you a lot of downloading since factory images are starting to get up there in size.
Dear helpful XDA-devs,
I ran into some weird display bugs which I did not experienced before. I've had the N5 and other phones and did often change my dpi without any side effect. However when I did it with my new Nexus 6 now I discovered some icons in the Play Store and "Locus Maps", for example, being oversized (see attachments).
What I did was to try to change my DPI using "Texdroider DPI" which let to an instant bootloop. So I reflashed /system from the stock image. Then I used the Nexus Root Toolkit to change the dpi via adb, what I thought worked perfectly back then (I changed it from default 560 to 530 in the end but tried a few other values as well). However, now I discovered these weird display issues in these two and one or two other apps. Any ideas what might be the reason, if it is DPI related at all, or if it worked fine when you did it yourself? Changing it back to default now does not solve the issue for me now, of course.
I'm on MOB30I, by the way. And I use TWRP+SuperSU on it. I did allow TWRP to make the /system partition writable to prevent Android from replacing TWRP. Might that be a reason why the adb-DPI-change let to bugs? Thanks for the help! :good:
To prevent people messing with the dpi many apps and Google are hard coding the sizes into the apks. I would just leave the dpi stock
zelendel said:
To prevent people messing with the dpi many apps and Google are hard coding the sizes into the apks. I would just leave the dpi stock
Click to expand...
Click to collapse
Thanks for your input. I just decides to reflash /system again (overwriting it via fastboot). But the problem persists!? How is this possible? Reflashing /system should reset DPI changes, right? Man, do I really have to reinstall all of Android? .. :crying:
karlo12 said:
Thanks for your input. I just decides to reflash /system again (overwriting it via fastboot). But the problem persists!? How is this possible? Reflashing /system should reset DPI changes, right? Man, do I really have to reinstall all of Android? .. :crying:
Click to expand...
Click to collapse
No not completely. That maybe your best bet. Also could try deleting the cache files.
You need to also change the dpi in build.prop, or you'll get those large icons.
Or if you want to go back to the old dpi, just do what you did in NRT, but change it to 560 this time.
change it in your build.prop file, then reboot for it to take affect. anyways, you will probably see other bugs with the dpi changed properly(but maybe not).