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
Related
My fonts is too small . How Can I increase the fonts . Thanks
Sent from my Dell Streak using XDA App
if you are using streakdroid, go under spare parts(which can be downloaded even if you are on official rom) and you will see the font size setting. alternatively you can edit your pixel density in build.prop or simply use a pixel density changing app.
I'd been using my Streak for 3 days now. And the fonts are nice and I have no problem with it.
You can always zoom it to fit to you're comfortable view.
joelk said:
My fonts is too small . How Can I increase the fonts . Thanks
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
I use LCD Density Changer from the market, just search LCD density and you will be able to find it. But your phone needs to be rooted and you also need Busybox installed. Using this method, you will be able to "enlarge" your fonts but everytime you restart your phone, you need to set it again.
The other method is use a file manager (i use file expert), mount as read/write and open /system/build.prop and add a line ro.sf.lcd_density=180 (which i find good enough) in the end. The default is 160. You can go 180,200,240. This settings will persist even after restarting.
Or you can try what sharptv has mentioned about spareparts, although i haven't tried that method.
I found LCDDensitiy in the market , know my fonts is large. Its so pleasure. Thanks. Spare parts dissmiss the fonts change as soon as I go out from him . So nothing done
Sent from my Dell Streak using XDA App
Its turn out that Lcd density not good enough. I install the file expert change the mount to rewrite and add the line in the build file. , but he won't let me save it or I cannot see The Change I made To the file.
Sent from my Dell Streak using XDA App
I manage to add the line with root explorer, thanks
Sent from my Dell Streak using XDA App
Yayyyyyyy, well pleased. Must have set the density too high when I flashed my ROM. Was dreading having to re-flash, with the attendant reset and month getting the phone back to how I like it. Simple line edit, and voilla, no more magnifying glass needed. Thanks folks, made my day.
In my case, the lcd_density line was already there, (set at 140), which threw me because I simply scrolled to the bottom and added the line, which, of course didn't work 'cos the line already appeared.
If you find that this technique doesn't work for you, search for the file for the offending line, and simply edit the number (mine now at 160, and perfect)
Sent from my Dell Streak, streakdroid 1.9, Swype keyboard, using XDA Premium App
You can always reflash a rom on top of your old one without changing any of your setup. Just flash as you normally would, but don't factory reset. So you can change your setup options for the rom, then just re-flash it. That even works for upgrading a rom to a newer version, unless the chef recommends against it...
Of course always Nandroid backup first!
Sent from my Dell Streak using Tapatalk
slaydog said:
You can always reflash a rom on top of your old one without changing any of your setup. Just flash as you normally would, but don't factory reset. So you can change your setup options for the rom, then just re-flash it. That even works for upgrading a rom to a newer version, unless the chef recommends against it...
Of course always Nandroid backup first!
. . .
Click to expand...
Click to collapse
Custom ROMs applied as a .zip file can be flashed over your current ROM without loss of settings and apps. Depending what ROM is on your phone and what apps you have installed this may cause problems. Most devs recommend a factory reset to make sure that this does not happen. Usually it is safe to reflash StreakDroid if you want different options. For best results with a custom ROM you will usually get better results if you flash the stock ROM that they base the custom ROM on first, so that you have the correct system files that match the custom ROM, since all of these are not part of the .zip file that contains the custom ROM.
When installing a stock ROM from recovery it is the same effect as a factory reset. You will have to redo your settings and reinstall your apps.
So the advice to flash over the ROM only works if the problem you are having isn't due to mis-matched baseband and if you are talking about a custom ROM.
Hi it's my first post on here and I recently rooted my Samsung galaxy s5 via towel root and I've been trying to change my bootanimation
It wouldn't work on theme changer in rom toolbox pro. So I tried doing it myself I still have all stock files but it seems that I erased my whole boot animation. When I reboot my phone it just takes me straight to my home screen. Any help would be appreciated thanks!
Simply restore your backup.
If you don't make backups that is a bad habit that you ought to change immediately. In the alternative, then manually revert the files that you changed and your bootanimation will work again. If it doesn't seem to, then wipe your system cache from recovery mode.
If the problem persists, I would suggest that you didn't really revert all of the files that you changed. Check the file permissions and investigate what else your app may have changed on your behalf. In the worst case you can start over by writing a full stock firmware image to your phone. A lot more painful than restoring a backup that would reflect how your phone was four hours ago. But a certain lack of planning will limit choices that way.
As to the boot animation per se, Samsung requires a .qmg animation file, while most apps use a bootanimation.zip formatted file. Ergo you usually need to convert your .zip file to a qmg. Or modify your kernel to use the .zip format. There are lots of existing threads that explain in detail how to do either which you would know if you had done a search before posting. I would suggest that it is always in your own interest to do at least a quick search first, if only so that you can pose more informed questions.
.
fffft said:
Simply restore your backup.
If you don't make backups that is a bad habit that you ought to change immediately. In the alternative, then manually revert the files that you changed and your bootanimation will work again. If it doesn't seem to, then wipe your system cache from recovery mode.
If the problem persists, I would suggest that you didn't really revert all of the files that you changed. Check the file permissions and investigate what else your app may have changed on your behalf. In the worst case you can start over by writing a full stock firmware image to your phone. A lot more painful than restoring a backup that would reflect how your phone was four hours ago. But a certain lack of planning will limit choices that way.
As to the boot animation per se, Samsung requires a .qmg animation file, while most apps use a bootanimation.zip formatted file. Ergo you usually need to convert your .zip file to a qmg. Or modify your kernel to use the .zip format. There are lots of existing threads that explain in detail how to do either which you would know if you had done a search before posting. I would suggest that it is always in your own interest to do at least a quick search first, if only so that you can pose more informed questions.
.
Click to expand...
Click to collapse
yeah its okay I just reverted everything and it works fine. I still want to but I don't wanna mess it up again. But yes I just reverted the files back and I'm okay. But I wanted a custom boot animation but there's really no clear tutorial on how to.
lgillen14 said:
But I wanted a custom boot animation but there's really no clear tutorial on how to.
Click to expand...
Click to collapse
Not true. You need to search better as I have seen several of them. And if memory serves, written at least one myself.
.
fffft said:
Not true. You need to search better as I have seen several of them. And if memory serves, written at least one myself.
.
Click to expand...
Click to collapse
do I need a different rom? I don't even know how do do any of that lime I've rooted all my phones but not gone seriously in depth about it. I don't know what I did wrong the first time and when I tried following directions and it almost messed me up. So could you guide me toward the appropriate thread I need to get to? Thanks
lgillen14 said:
do I need a different rom?
Click to expand...
Click to collapse
No, you simply need to do a search and read the existing boot animation guides. A lot of people claim to search when they really didn't. Or did one simplistic search and gave up, thinking it's easier if someone spoon feeds them. If you try a few different keywords you'll find the guides and everything you need.
You don't need a different ROM. Root is sufficient to change the boot animation file. If you want to make a qmg animation from scratch you can use Samsung's theme designer software.
.
Update: I found an even better solution. Instead of setting "dalvik.vm.heapsize=256m" use "dalvik.vm.heapsize=128m"
Warning! Please make a backup of your /system partition using recovery incase you get a bootloop from changing vm heapsize. Don't go below 128m as it may cause a bootloop.
If you want additional memory you can download "Ram Manager Free" from the Google playstore and set up a disk swap. Within the app, go to swap and delete the given directory and set it to "/cache and use a value of 256 MB. It won't steal from your already limited storage as it will use the cache partition which goes mainly unused. Warning though as it may degrade your internal storage from constant writing. If you ask me I don't care about degradation of my Moto G as I plan to get a better phone soon. I only recommend you use swap with the stock kernel as there is virtually no lag. I tested with other kernels and there is noticeable lag.... Aero Kernel lags noticeably and so does faux kernel. Oh! and make sure you set it to balanced and check the apply at boot option to stick. I stopped using swap, but you can try for yourself to see if you like it.
This is for the Moto G XT1034 as I don't know if the build.prop is different for the other variants, but you can always check if you have the duplicate entries.
While going through the build.prop of the stock 4.4.4 ROM I found duplicate entries of the same value with different parameters. The culprit being "dalvik.vm.heapsize" seemed to have been causing my music apps force closing when there was "insufficient" RAM. Other apps running in the background can also be killed like night screen filters while browsing the web using Chrome just to name another. You'll find two entries called "dalvik.vm.heapsize=36 and dalvik.vm.heapsize=256." They are the same value, but with different parameters. I deleted the one for "36m" and my multitasking issues disappeared without changing the MINFREE TASKKILLER values. I used Performance Control that can be found here on XDA to edit the build.prop. When you delete "dalvik.vm.heapsize=36m" make sure you re-add the value "dalvik.vm.heapsize=256m" because deleting one deletes BOTH! My screen filter app "EasyEyes" has yet to be killed by low memory situations.
Why would Motorola include duplicate entries of the heapsize? I'd like to be enlightened on why they included both.
NOW, your music app may be killed if you run very low on memory, this happens when you use chrome and view heavy pages, so modifying your MINFREE TASKKILLER values may be of additional assistance. I attached a screenshot of MINFREE values if you want to use my values, although I'm not using them since I'm using stock values. At the end of the day you have to understand that 1GB is now "low-end" and is simply not enough for multitasking anymore on Android. Apps are becoming larger and browsers and websites are becoming more complex; more RAM is needed. As soon as you open Chrome expect your apps to be killed since it needs at least 200 MB to run adequately.
Any reports of success with this? I just sold my Moto G last week because of the multi tasking issue... if this solves 90% of the problem, that would be pretty awesome.
I updated this with an even better solution. Set dalvik.vm.heapsize=256m to dalvik.vm.heapsize=128m to make the phone much less likely to kill apps in general.
Also, can anyone please tell me what the storage is like with stock lollypop? I've used art runtime on my 8GB moto g and reverted back to dalvik because my storage was nearly full. If that's still the case then I will keep my moto G running 4.4.4 forever... well until it dies.
Jorge_007 said:
I updated this with an even better solution. Set dalvik.vm.heapsize=256m to dalvik.vm.heapsize=128m to make the phone much less likely to kill apps in general.
Also, can anyone please tell me what the storage is like with stock lollypop? I've used art runtime on my 8GB moto g and reverted back to dalvik because my storage was nearly full. If that's still the case then I will keep my moto G running 4.4.4 forever... well until it dies.
Click to expand...
Click to collapse
My phone isnt booting up can you plz tell me how to fix this, i changed it to 128m and its not booting up
NextGenGTR said:
My phone isnt booting up can you plz tell me how to fix this, i changed it to 128m and its not booting up
Click to expand...
Click to collapse
Did you follow the direction? Using Performance control edit build.prop. Delete "dalvik.vm.heapsize=256m and re-add the value "dalvik.vm.heapsize=128m" and click apply? Anyways what phone model are you using?
Anyways, I assume you followed accordingly, so you should have made a backup of your system partition using your preferred recovery. To undo the changes made boot into recovery and restore system partition. That will make the phone boot. If you didn't, then if you know can always restore using this guide: http://forum.xda-developers.com/showthread.php?t=2542219
OR you can flash a stock rom zip from here "http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Jorge_007 said:
Did you follow the direction? Using Performance control edit build.prop. Delete "dalvik.vm.heapsize=256m and re-add the value "dalvik.vm.heapsize=128m" and click apply? Anyways what phone model are you using?
Anyways, I assume you followed accordingly, so you should have made a backup of your system partition using your preferred recovery. To undo the changes made boot into recovery and restore system partition. That will make the phone boot. If you didn't, then if you know can always restore using this guide: http://forum.xda-developers.com/showthread.php?t=2542219
OR you can flash a stock rom zip from here "http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Click to expand...
Click to collapse
Can you get your stock build.prop with the heapszie 256m and then plz go into recovery and then use adb pull /system/build.prop c:\ and the give it to me so i can flash it through recovery, i think that would work because i have a flashable zip with a build.prop but its not for this phone so i need to replace it with another, i have the stock moto g build . prop but i cant edit it with windows.
NextGenGTR said:
Can you get your stock build.prop with the heapszie 256m and then plz go into recovery and then use adb pull /system/build.prop c:\ and the give it to me so i can flash it through recovery, i think that would work because i have a flashable zip with a build.prop but its not for this phone so i need to replace it with another, i have the stock moto g build . prop but i cant edit it with windows.
Click to expand...
Click to collapse
This is the stock build.prop untouched for my Moto G XT1034 AWS firmware
It's not flashable, you'll have to make it a flashable zip
Jorge_007 said:
This is the stock build.prop untouched for my Moto G XT1034 AWS firmware
It's not flashable, you'll have to make it a flashable zip
Click to expand...
Click to collapse
The phone refused to boot up so now i am trying another step to only flash system files 0 1 2 and hopefully that will work!!!
Suprisingly enough that worked and nothing has been deleted and everything is how it is suppose to be! I have all my applications and my backgrounds and files intact!!! Add this in your tutorial if anyone faces the issue, flash the system files.
NextGenGTR said:
The phone refused to boot up so now i am trying another step to only flash system files 0 1 2 and hopefully that will work
Click to expand...
Click to collapse
That will definitely work. Remember to always make a backup of your system when making changes to /system.
Jorge_007 said:
That will definitely work. Remember to always make a backup of your system when making changes to /system.
Click to expand...
Click to collapse
Also may i ask if you can possibly clear up your tutorial please since it confused me a lot and i must of done something wrong to f my phone. Thanks. Im just confused i have the build editor from Jrummy apps and it has the two 36m and 256m, now i deleted the 256m and then edited the 36m to 128m is that correct ?
NextGenGTR said:
Also may i ask if you can possibly clear up your tutorial please since it confused me a lot and i must of done something wrong to f my phone. Thanks. Im just confused i have the build editor from Jrummy apps and it has the two 36m and 256m, now i deleted the 256m and then edited the 36m to 128m is that correct ?
Click to expand...
Click to collapse
Don't use the ones on the playstore. I had trouble with them in the past when it came to editing the build.prop on this phone. Use Performance Control from XDA http://forum.xda-developers.com/devdb/project/?id=600#downloads Make sure you install busy box from the playstore as it is needed for the app to work. Make sure you make a backup of you /system in recovery first. Once performance control is installed, swipe left until you get to the tools tab. Scroll down until you see "Edit build prop" Delete both entries for 36m and 256m. To delete press and hold and it will ask if you want to delete. Press apply values to save. Now click on the menu button that has three dots and select "add parameter" and enter "dalvik.vm.heapsize" for Name and enter "128m" for value and press save. Make sure you press on apply values and reboot.
Jorge_007 said:
Don't use the ones on the playstore. I had trouble with them in the past when it came to editing the build.prop on this phone. Use Performance Control from XDA http://forum.xda-developers.com/devdb/project/?id=600#downloads Make sure you install busy box from the playstore as it is needed for the app to work. Make sure you make a backup of you /system in recovery first. Once performance control is installed, swipe left until you get to the tools tab. Scroll down until you see "Edit build prop" Delete both entries for 36m and 256m. To delete press and hold and it will ask if you want to delete. Press apply values to save. Now click on the menu button that has three dots and select "add parameter" and enter "dalvik.vm.heapsize" for Name and enter "128m" for value and press save. Make sure you press on apply values and reboot.
Click to expand...
Click to collapse
Thank you so much for the help! I think i have finally did it! I only have the 128m when i check with es file explorer and i guess it is all fine! Is there a way i can confirm my thing is 128m ?
NextGenGTR said:
Thank you so much for the help! I think i have finally did it! I only have the 128m when i check with es file explorer and i guess it is all fine! Is there a way i can confirm my thing is 128m ?
Click to expand...
Click to collapse
Well you can install RAM Manager free from Playstore https://play.google.com/store/apps/details?id=com.smartprojects.RAMOptimizationFree&hl=en Go to "Extra" and select VM Heap Size it should read 128m. Also, listening to music should not be killed when multi-tasking. Apps such as iHeartRadio would always get killed when browsing the internet with Chrome. It doesn't happen anymore on my end. Also if you're not worried about your phones internal ssd from degrading you can set up a swap file to disk. Under Extra select swap file and delete the default directory and type "/cache" without quotes and set it to 256mb. It'll use the cache partition, so you'll still have your disk space for apps. It may degrade the life of your Moto G because of the constant writes, so it's up to you if you want to set up a swap. AND set it on Balanced on the main tab and check set on boot. Only do this on the stock kernel as I noticed lag on other kernels. Anyways you don't have to use swap or the ram manager app after your verify vm heap is 128m. I don't use it as just setting 128m vm heap no longer kills my music apps.
NextGenGTR said:
Thank you so much for the help! I think i have finally did it! I only have the 128m when i check with es file explorer and i guess it is all fine! Is there a way i can confirm my thing is 128m ?
Click to expand...
Click to collapse
I think I found the real problem of the aggressive app killing. Go back to build.prop in performance control and change 128m back to 256m. Apply to save. Now go back and look for this value "ro.MAX_HIDDEN_APPS=12" and delete it; press and hold to delete. I'm testing it as of today, so if you can test it too let me know if it reduces the frequency of app killing aggressiveness. iHeartRadio has not been killed while browsing in Chrome for me. Thanks.
Jorge_007 said:
I think I found the real problem of the aggressive app killing. Go back to build.prop in performance control and change 128m back to 256m. Apply to save. Now go back and look for this value "ro.MAX_HIDDEN_APPS=12" and delete it; press and hold to delete. I'm testing it as of today, so if you can test it too let me know if it reduces the frequency of app killing aggressiveness. iHeartRadio has not been killed while browsing in Chrome for me. Thanks.
Click to expand...
Click to collapse
Changed it and let me do a few tests, I usually get SoundCloud to crash
When I load clash of clans...
NextGenGTR said:
Changed it and let me do a few tests, I usually get SoundCloud to crash
When I load clash of clans...
Click to expand...
Click to collapse
Okay, let me know how thing go
Jorge_007 said:
Okay, let me know how thing go
Click to expand...
Click to collapse
Listening to SoundCloud and playing clash of clans caused home screen to reload icons when pressing home button.
NextGenGTR said:
Listening to SoundCloud and playing clash of clans caused home screen to reload icons when pressing home button.
Click to expand...
Click to collapse
Oh a launcher redraw is to be expected if you're playing a game and listening to music. 1GB is just not enough to maintain everything in memory. Did soundcloud close though? Last time I checked it was a RAM heavy application.
Jorge_007 said:
Oh a launcher redraw is to be expected if you're playing a game and listening to music. 1GB is just not enough to maintain everything in memory. Did soundcloud close though? Last time I checked it was a RAM heavy application.
Click to expand...
Click to collapse
Currently with your settings + a build.prop code for the launcher to keep it in ram i am not experiencing any issues, also i have installed Rom toolbox pro which comes with build.prop editor and many other cool features, one being the minfree value changer, others have reported using the aggressive min free values from minfreemanager helps out so i am using that in romtoolbox and everything is in one single app so its nice and tidy, i recomend you give it a shot
Seems to work on lollipop as well!
Sent from my XT1032 using XDA Free mobile app
Today I found something really strange about builds LMY47E and LMY47D. I had been running 47D since last week with a DPI of 520, which was adjusted using Root Explorer in the build.prop. After trying to do the same in 47E, rebooting my device would display the "Android is upgrading... Optimizing app 1 of XXX" screen, and make it bootloop after optimizing the last app, displaying the same screen and optimizing my apps again and again.
After many hours trying to isolate the culprit, I found that to properly change DPI In 47E, one has to edit the build.prop lcd density AND use "adb shell wm density XXX". That's the only way I've made sure my device reboots properly.
I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
redsmith said:
Today I found something really strange about builds LMY47E and LMY47D. I had been running 47D since last week with a DPI of 520, which was adjusted using Root Explorer in the build.prop. After trying to do the same in 47E, rebooting my device would display the "Android is upgrading... Optimizing app 1 of XXX" screen, and make it bootloop after optimizing the last app, displaying the same screen and optimizing my apps again and again.
After many hours trying to isolate the culprit, I found that to properly change DPI In 47E, one has to edit the build.prop lcd density AND use "adb shell wm density XXX". That's the only way I've made sure my device reboots properly.
I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
Click to expand...
Click to collapse
I just changed it with root explorer. I didn't have any issues.
Then again I stayed within the default density's from my past devices.
Nexus 6 is 560, I went to 480.
antiochasylum said:
I just changed it with root explorer. I didn't have any issues.
Then again I stayed within the default density's from my past devices.
Nexus 6 is 560, I went to 480.
Click to expand...
Click to collapse
That's weird. Mine would survive a couple of reboots but after that, bootloop fest.
I'll keep an eye on this issue anyway.
I just went through this on 47E. It was bad but it turns out that you only need to do "adb shell wm density XXX" and not edit the build prop. Editing the build prop sent me through the bootloop
krazekid007 said:
I just went through this on 47E. It was bad but it turns out that you only need to do "adb shell wm density XXX" and not edit the build prop. Editing the build prop sent me through the bootloop
Click to expand...
Click to collapse
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
redsmith said:
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
Click to expand...
Click to collapse
Still get glitches even after rebooting?
Lol, I'm so glad someone brought this up. Thought I or my phone was going nuts!
All I've ever done is change the build.prop, no adb stuff, never had issues...for all builds
Sent from my Nexus 6 using XDA Free mobile app
A2CKilla said:
All I've ever done is change the build.prop, no adb stuff, never had issues...for all builds
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
It lasts for a few days sometimes.... Usually after a reboot or 2 its gameover.. It'll usually let me reboot 2x before looping .. If I don't reboot it'll just randomly turn off and then..well.. Loop
Not the only ones with this issue... here's what I have found even with "D" & "E" working with the group trying to port the Blinkfeed Launcher from Sense 7 which requires a DPI change to work correctly on the Nexus 6.
532DPI use to work with 5.0.1 & 5.0.2... No longer the case for any 5.1 build (haven't tried "M" build yet) which is the perfect setting for Blinkfeed Sense 7 Launcher....
I am using 520 right now... other experience issues with the bootloop at 520... I have found a way to test:
1. TWRP backup current good DPI setting... Backup up everything cache, efs, system, data, etc.
2. After TWRP backup, boot up and apply the new settings you wish to test. Apply then completely power off.
3. Power on and boot up. If no optimizing apps issues, you have passed step one.
4. Now TWRP backup your new settings, backup everything, reboot system. If no bootloop, then you should be golden
I think it is something in the code to streamline how it handles graphics... however it seems that what is acceptable varies from phone to phone. Most see good results staying with factors of 40 & 80 while others can do even factors of 20....
Don't think anyone has figured out root cause entirely..... I really like to know why I could 532 before and can't now???
Yea 532 was my buttah
redsmith said:
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
Click to expand...
Click to collapse
So were you able to successfully change your DPI by editing the build.prop?
I had to do adb shell trick too, otherwise, bootloops.
Build.prop edit LCD_density
redsmith said:
. . . . . I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
Click to expand...
Click to collapse
Started with rooting 5.0.1. Then edited build.prop with 'build.prop.editor and changed the LCD-density to 493.
Because the native resolution is of the N6 screen is 493.
After upgrading to LMY47D the DPI value was 520 (0r 560?) again. I edited this value 'ro.sf.lcd_density' and set the value to 384.
With that value the N6 is in tablet mode.
After rebooting the value of 'ro.sf.lcd_density was 384, but the display was not different.
In the Build.Prop editor there is a menu item called Build.Prop Tweaks. In the Tweaks-list the entry 'LCD Density' was missing.
I did not have a backup of the build.prop file so a full restore in recovery was needed to correct this.
The Build.Prop editor has an option to create a backup. Use this option first before editing.
Now for about a week with 47D and DPI 384 and font size to huge, the N6 works fine. (Stock, rooted, encrypted).
Remark.
Because the N6 has a amoled display it's a bit strange that the name 'ro.sf.lcd_density' is used.
NLBeev said:
Started with rooting 5.0.1. Then edited build.prop with 'build.prop.editor and changed the LCD-density to 493.
Because the native resolution is of the N6 screen is 493.
After upgrading to LMY47D the DPI value was 520 (0r 560?) again. I edited this value 'ro.sf.lcd_density' and set the value to 384.
With that value the N6 is in tablet mode.
After rebooting the value of 'ro.sf.lcd_density was 384, but the display was not different.
In the Build.Prop editor there is a menu item called Build.Prop Tweaks. In the Tweaks-list the entry 'LCD Density' was missing.
I did not have a backup of the build.prop file so a full restore in recovery was needed to correct this.
The Build.Prop editor has an option to create a backup. Use this option first before editing.
Now for about a week with 47D and DPI 384 and font size to huge, the N6 works fine. (Stock, rooted, encrypted).
Remark.
Because the N6 has a amoled display it's a bit strange that the name 'ro.sf.lcd_density' is used.
Click to expand...
Click to collapse
whojabacod said:
Yea 532 was my buttah
Click to expand...
Click to collapse
krazekid007 said:
So were you able to successfully change your DPI by editing the build.prop?
Click to expand...
Click to collapse
redsmith said:
I had to do adb shell trick too, otherwise, bootloops.
Click to expand...
Click to collapse
I don't believe there is any rhyme or reason to it bootlooping... something is definitely different in the programming in 5.1... tried everything last night to get 532DPI to stick.... build.prop.... adb command... tried them all... would reboot 1 time ok, second time "op apps" bootloop. this was not the case with 5.0.1 or 5.0.2... I remember tweaking the dpi by 2 up and down to find a perfect dpi for a Blinkfeed launcher port on 5.0.2 and never had this issue. It is either something Google did on purpose for this build or on accident. Either way, we are kind of screwed until someone smarter than I can put a finger on as to what is causing this... I just think 5.1 was rushed to get VoLTE out there for the Verizon release...
When your N6 is bootlooping in 5.1. And you can't find the cause and/or a solution then you could decide to go back to the factory settings including unroot. This can be done easily with the toolkit of Wugfresh.
I did that and I am using now 5.1 (47D) and edited buil.prop. DPI set to 384.
NLBeev said:
When your N6 is bootlooping in 5.1. And you can't find the cause and/or a solution then you could decide to go back to the factory settings including unroot. This can be done easily with the toolkit of Wugfresh.
I did that and I am using now 5.1 (47D) and edited buil.prop. DPI set to 384.
Click to expand...
Click to collapse
Or you can just fastboot flash system.img and save time and your data. It's what I did on a DPI bootloop.
SilkyJohnson said:
Or you can just fastboot flash system.img and save time and your data. It's what I did on a DPI bootloop.
Click to expand...
Click to collapse
Let's hope for him.
NLBeev said:
Let's hope for him.
Click to expand...
Click to collapse
No need to hope - it works. I did it.
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.