Change LCD density value? - G4 Q&A, Help & Troubleshooting

Anybody tried to change LCD density in build.prop file? My G4 F500S unable to boot normally after I changed the value to 480. My phone is able to pass the LG logo screen, sometimes it will display the apps optimization in progress.. when optimization done, it display something like system ui problem (can't see clearly as it rebooted in very short time)... Still finding a solution to fix the problem now

raychak said:
Anybody tried to change LCD density in build.prop file? My G4 F500S unable to boot normally after I changed the value to 480. My phone is able to pass the LG logo screen, sometimes it will display the apps optimization in progress.. when optimization done, it display something like system ui problem (can't see clearly as it rebooted in very short time)... Still finding a solution to fix the problem now
Click to expand...
Click to collapse
I think anything less than 530 causes issues. I'm running 540 fine.

Juzman said:
I think anything less than 530 causes issues. I'm running 540 fine.
Click to expand...
Click to collapse
I see... I think that is the root cause of the problem making my phone unable to boot up.

raychak said:
I see... I think that is the root cause of the problem making my phone unable to boot up.
Click to expand...
Click to collapse
Quite possibly. I am guessing you may be able to change it to 540 or something via ADB. I'm not too sure. Maybe an adb pull /system/build.prop then edit and push it back.

Related

[Q] Build.prop that just disapears

Hi folks
I've got a little problem wich some of you I hope, may have a solution to.
From some time I was experiencing trouble with my data bandwidth, so far i believed that it had something to do with my carrier, but today, i wished to try some of the build.prop tweak i had see on this forum.
So I went looking for my own build.prop wich was not on the root of my play...
From then I recovered one from an nandroid backup of mine, after that i changed the file permission to rw--r--r and rebooted my phone and like poof, the file was gone.
The amazing thing is that I noticied some major improvement in my upload rate for a little time^^ but after a while it just droped back to what I was used to.
I tried to recover it several times but it disapears every time I reboot my play.
Is this a normal behavior?
Must I use the default.prop in order to make the change persistent?
I'm on a stock 4.0.2.A.0.42 baseband -36 with a locked bootloader
Thanks in advance for you feedback
Have a nice evening
Well if your build.prop actually disappeared, your phone wouldn't boot. Are you sure you're looking in /system?
jacklebott said:
Well if your build.prop actually disappeared, your phone wouldn't boot. Are you sure you're looking in /system?
Click to expand...
Click to collapse
Ok i dont know why but i was thinkin it was at the root of the phone^^
Plus es explorer didn't found it when i searched for it... it is in fact... there...
Thank you jacklebott
Would you know where i could fiind the meaning of the semc properties in there, and maybe you could also point me to a thread where i can find tweaks meant for the play?

Changed DPI to 280 now I can't get passed the Google logo when booting

Rooted Maguro:
Manually changed density from 320 to 280 and now I can't get passed the Google logo when booting Can anyone help me understand what happened? Is it because I chose 280? Should I have chosen 240/241 instead?
Shouldn't have happened at all. Maybe you accidentally touches other lines. Dirty flash your current ROM and try again (you won't lose data)
Sent from Samsung Galaxy Nexus @ CM10.2
AndyYan said:
... try again (you won't lose data)
Click to expand...
Click to collapse
Kind of spooked me... have to rebuild courage before I try again
I used ROM Toolbox Lite to edit the build.prop. Pretty sure I didn't touch anything else.
kroogar said:
Kind of spooked me... have to rebuild courage before I try again
I used ROM Toolbox Lite to edit the build.prop. Pretty sure I didn't touch anything else.
Click to expand...
Click to collapse
Must be a ROM Toolbox problem then (I've seen a lot of misc problems caused by it, namely bootanimation and build.prop edits). Edit with Root Explorer or any other "straightforward" text editor.
Sent from Samsung Galaxy Nexus @ CM10.2

LG G4F h810 10o soft brick

Ok, I tried to modify a system file and now it won't boot. I've done some searching but can't find something to work.
I tried to change my build.prop to change my dpi setting. I found instructions that said ". Scroll down to ro.sf.lcd_density=240. Change the value to anywhere between 180 and 240. The lower the value, the higher density your screen will have."
Mine was set to 640. I didn't want a major change so I set it to 600. Not it gets stuck with the AT&T logo. I have rooted. I can get into download mode. When I changed the setting it made a back up of the build.prop. All I really need to do is to delete my build.prop and change the backup filename and it should be fixed, right?
How do I do that? I used "[ROOT] TMO/VZW/ATT/SPRINT/INTL Root your LG G4 with Low Effort Root!" to get root.
One other thing. I have already removed the install image I used to root off the phone. That would have been easy to simply install it again. Unfortunately, I can't. Any way to send it to the phone so I can load it?
Please help!
Ralph
Good news. I went into AT&T and my phone is still under warranty. They are shipping me a new phone. I will keep my image on the phone this time.
Ralph

Screen smaller

Can someone tell my what just happened here?
My 7 year old son just gave me back my device and the screen is smaller than usual.
He can't remember doing such things and I can't reverse it. Have a look in the attachment.
Restart didn't help
try this
go-to SETTINGS - ADDITIONAL SETTINGS - ACCESSIBILITY - DISPLAY SIZE ... you can adjust the size from there if you are in miui
Found that already, didn't work.
Will try to restore a TWRP backup tonight, if I can't find anything else
Didn't work. Seems I have to do it the hard way and do a factory reset.
Edit: tried one thing before the hard reset. Changed the DPI from currently 404 to 440 and waaaaaaaaaaaaaay better now.
Tischbein said:
Didn't work. Seems I have to do it the hard way and do a factory reset.
Edit: tried one thing before the hard reset. Changed the DPI from currently 404 to 440 and waaaaaaaaaaaaaay better now.
Click to expand...
Click to collapse
In MIUI9 that is the default DPI value

LiveBoot by Chainfire

So I was thinking last night about this app that I used to have and use that allowed you to show logcat/dmesg as your boot animation and after a quick Google search I finally found it!
Here is the link if anyone is interested.
https://forum.xda-developers.com/android/apps-games/liveboot-t2976189
Looks amazing on the OP6T. ??
TheKnux said:
So I was thinking last night about this app that I used to have and use that allowed you to show logcat/dmesg as your boot animation and after a quick Google search I finally found it!
Here is the link if anyone is interested.
https://forum.xda-developers.com/android/apps-games/liveboot-t2976189
Looks amazing on the OP6T. ??
Click to expand...
Click to collapse
I tried it, but it just hangs while trying to load resources. I think I'm just unlucky lol
I installed it but got a boot loop. I could only start the phone by flashing latest oos without magisk but even after uninstalling live boot, magisk still kept the liveboot00001 file or whatever so I had to remove it manually in twrp in /data/adb/magisk/ (somewhere around there.. ) Just in case someone else has this problem..
No problem here, using it since 4 weeks, several OOS updates never had an issue
TheKnux said:
Looks amazing on the OP6T.
Click to expand...
Click to collapse
It sure does! Thanks for the share. Works great on beta 2, even though I have the McLaren Magisk mod running (which replaces boot animation with McLaren's).
Installed it on a Oneplus 6. Bootlooped immediatly after the next restart. I already deleted the file located in /data/adb/magisk/post-fs but it still doesnt boot properly.
What can i do? I also tried uninstall Magisk via TWRP and using an unpatched boot image. Nothing works.
Ironic said:
Installed it on a Oneplus 6. Bootlooped immediatly after the next restart. I already deleted the file located in /data/adb/magisk/post-fs but it still doesnt boot properly.
What can i do? I also tried uninstall Magisk via TWRP and using an unpatched boot image. Nothing works.
Click to expand...
Click to collapse
That's weird that it doesn't work for you. All I did was open the app, grant su access and rebooted and it worked. Magisk v18 user.
TheKnux said:
That's weird that it doesn't work for you. All I did was open the app, grant su access and rebooted and it worked. Magisk v18 user.
Click to expand...
Click to collapse
It worked for my on my 6T running 9.0.11.
I'd like something a little less verbose so you can actually read some stuff as it goes by.
tech_head said:
It worked for my on my 6T running 9.0.11.
I'd like something a little less verbose so you can actually read some stuff as it goes by.
Click to expand...
Click to collapse
Just change the lines of code that are shown on screen, I haven't tried it but I'm sure that would help. I'm not really worried about reading anything, if I wanted to do that, I'd just pull a log. It's more of an asthetic kind of thing.
TheKnux said:
Just change the lines of code that are shown on screen, I haven't tried it but I'm sure that would help. I'm not really worried about reading anything, if I wanted to do that, I'd just pull a log. It's more of an asthetic kind of thing.
Click to expand...
Click to collapse
I don't really want to read it.
I want it to scroll by slower so it looks a bit more convincing when it boots.
tech_head said:
I don't really want to read it.
I want it to scroll by slower so it looks a bit more convincing when it boots.
Click to expand...
Click to collapse
Did changing the lines of code displayed on screen work at all? Not sure of any other way to slow it down. Seeing how an OS is thousands of lines of code. Seemed pretty convincing to a few coworkers of mine.
TheKnux said:
Did changing the lines of code displayed on screen work at all? Not sure of any other way to slow it down. Seeing how an OS is thousands of lines of code. Seemed pretty convincing to a few coworkers of mine.
Click to expand...
Click to collapse
I didn't change it. No real incentive right now.
This app was my old favorite and I miss it, I hope it still works as I havnt tried... Just wanted you all to know this is the best app ever and the scrolling text (if your developing) is actually SUPER helpful... I remember I would use the filter to find specific debug lines only and it was so usefull... I only installed it because Im a huge nerd so it was an extra awesomeness to have it be super usefull!
2023 BEST APP EVER!#[email protected]#

Categories

Resources