Develop Bugs

[App] LCD Density Changer v3.0 (update + link to new thread)

One last note: Users that have installed the previous versions should/ are adviced to download the new version from the other thread. The new version addresses the problem that one can't boot into the system because of a conflict between a particular density setting and a launcher and or widget.
The apk's attached to this post are now removed. Head over to the new thread to download the app.
Update v2.1 * addresses some problems other devices than the Galaxy S variants had with the former version. * some minor cosmetic changes. (note: I also opened a thread on the android developers forum, so other devices can profit from this tweak as well. I have decided to post my updates there and, of course, on the Android Market. The new thread can be found http://forum.xda-developers.com/showthread.php?t=765639
Update v2.0 * Added option to turn on/off compability settings for app scaling. * Possibility to restore default density setting (the default density that is stored is the density of your screen when you run the tool for the first time). * Added helpfile * Added option to reboot automatically after changing the density.
Update v1.1: a) Optimization of code: faster, more safe b) some cosmetic changes
I created a little app to play with the LCD Density Settings as described in this thread. The app lets you set the LCD Density Setting without edditing the build.prop file (directly).
Be aware that the tweak only will work with launchers like LauncherPro. It doesn't work with Samsungs own TouchWizardLauncher. (If you insist on experimenting with the TWLauncher, make sure that you have the USB Debugger enabled to get you out of the mess ).
Only requirements for this app to work is that you are rooted and have su, busybox and Superuser installed (in fact you have all those apps installed when you have rooted your device the "regular" way) AND that you like to experiment with things.. if you know what I mean.
Click to expand...
Click to collapse
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instead of a donation you can consider to buy the app from the Android Market (0,75 euro). Search for LCD Density Changer or scan:
I will keep this app for free for download and always up to date here on this forum!
Future work
I will keep on investigating how the software environment can be made compatible with lower density settings. My intention is to update the app constantly with new tweaks and settings so that eventually it can function as a full control panel for the density tweak.
Thanks to jdsemler who discovered this tweak.
Note: if you don't want to take any risk, make sure you make a nandroid backup. Although the new version is reported to be error-free, it is always a good idea to create a full system backup before one is going to play with these kind of tools.
(also) thanks to
* bratfink for giving some very useful input
* Cutefox for bringing to our attention that turning of the compatibility mode via an app called "Spare Parts" solves the scaling problem.
* Nelson Mandela for bringing peace
* Mahatma Ghandi for his inspiration
* Bell for inventing the phone
* Samsung for the upcomming GPS fix
* and many, many others I forgot to mention.
Download history
LCD Density Changer.apk (16.3 KB, 223 views)
LCD Density Changer v1.1.apk (17.6 KB, 91 views)
LCD Density Changer v2.0.apk (28.9 KB, 264 views)

What are the standard values?

HDPI = 240 (Galaxy S default)
MDPI = 160
LDPI = 120
The larger the number, the larger the stuff on-screen is. The smaller the number, the smaller stuff is. The smaller numbers are great for getting more stuff on screen to see, like when using RSS readers to see more articles on the screen before you have to scroll.

jdsemler said:
HDPI = 240 (Galaxy S default)
MDPI = 160
LDPI = 120
The larger the number, the larger the stuff on-screen is. The smaller the number, the smaller stuff is. The smaller numbers are great for getting more stuff on screen to see, like when using RSS readers to see more articles on the screen before you have to scroll.
Click to expand...
Click to collapse
Yeah, it's such a nice tweak. Thanks again! Any progression on the scaling issue?

Nothing useful yet. I'm convinced that the /system.prop is the problem. Somehow, they are updating that file on every reboot, and it is impacting certain apps that are having the 240 value passed to them from that file, which makes them render in that set size.
Take Root Explorer for example. It runs in a very small area when not in HDPI mode on the Samsung device. I installed it on my Dell Streak, which natively is set to run in MDPI mode, and it goes full screen without issue. I then set it for LDPI, and it goes full screen again. Going to HDPI also makes no issue, so it is something that Samsung is doing, and if we can figure out what is updating /system.prop and stop it, I think we'll have it licked.
I think I'm way out of my league when it comes to debugging the Samsung's behavior though.

Can someone post the original build.prop because mine seems to be 0 byte and I can see anything on the screen.
Thanks.

jdsemler said:
Nothing useful yet. I'm convinced that the /system.prop is the problem. Somehow, they are updating that file on every reboot, and it is impacting certain apps that are having the 240 value passed to them from that file, which makes them render in that set size.
Take Root Explorer for example. It runs in a very small area when not in HDPI mode on the Samsung device. I installed it on my Dell Streak, which natively is set to run in MDPI mode, and it goes full screen without issue. I then set it for LDPI, and it goes full screen again. Going to HDPI also makes no issue, so it is something that Samsung is doing, and if we can figure out what is updating /system.prop and stop it, I think we'll have it licked.
I think I'm way out of my league when it comes to debugging the Samsung's behavior though.
Click to expand...
Click to collapse
nonetheless a very interesting problem. The thing that intrigues me is that some apps run full screen without any problem. I'm gonna decompile those apps later on to see how they have defined the layout.
BTW can you upload some of the dell streak prop files that may be relevant in this case?

lpsi2000 said:
Can someone post the original build.prop because mine seems to be 0 byte and I can see anything on the screen.
Thanks.
Click to expand...
Click to collapse
Did you use my app? Because in that case that's not good. What did you do?
Have you rooted your device, did you have busybox installed? Have you granted superuser permission?
Anyway, I attached the build.prop from my Galaxy S.
EDIT if it's right there's a copy of build.prop in the folder /data/data/com.beansoft.lcd_density_setting (or something like that). Can you look and see if that file is 0 bytes to? Otherwise, copy that back to the system folder

I attached my default (HDPI setting) Samsung build.prop and my current Dell Streak build.prop.
The Streak build.prop has a different fingerprint, because I'm using the 2.1 build and had to have a recognized (by Market) fingerprint to get to my protected apps.
The Streak does not have a /system.prop file, unlike the Samsung.

System.prob
It does seem that the dpi settings in system.prop are what seems to be the issue with some of these applications. I could be that the samsung framework explicitly allows 240 as the only acceptable dpi and thus restores the system.prop automatically if it finds a different value.
In this case if someone doesnt mind flashing or is currently using that vanilla custom rom that works on the SGS (Its in its Alpha stages) then it would be interesting to see if the changes are permant and accross the board when using vanilla. Anyone care to try?

bratfink said:
It does seem that the dpi settings in system.prop are what seems to be the issue with some of these applications. I could be that the samsung framework explicitly allows 240 as the only acceptable dpi and thus restores the system.prop automatically if it finds a different value.
In this case if someone doesnt mind flashing or is currently using that vanilla custom rom that works on the SGS (Its in its Alpha stages) then it would be interesting to see if the changes are permant and accross the board when using vanilla. Anyone care to try?
Click to expand...
Click to collapse
Makes sense. Question though, when do all these prop files load? Don't think it will work, but can an app at boottime change the system.prob values so that it doesn't affect the modified dpi value?

tried using your app to change the setting to 220, and the at&t logo pops up, the samsung sound goes off, and the screen stays blank. I can't get access to su in adb shell and all I can do is reboot. what's going on?

asrrin29 said:
tried using your app to change the setting to 220, and the at&t logo pops up, the samsung sound goes off, and the screen stays blank. I can't get access to su in adb shell and all I can do is reboot. what's going on?
Click to expand...
Click to collapse
I suppose you have a rooted device with the whole sjabang (SuperUser and Busybox) installed on it?

appelflap said:
I suppose you have a rooted device with the whole sjabang (SuperUser and Busybox) installed on it?
Click to expand...
Click to collapse
yes. when I try to use su I get
[1] Segmentation fault su

appelflap said:
Did you use my app? Because in that case that's not good. What did you do?
Have you rooted your device, did you have busybox installed? Have you granted superuser permission?
Anyway, I attached the build.prop from my Galaxy S.
EDIT if it's right there's a copy of build.prop in the folder /data/data/com.beansoft.lcd_density_setting (or something like that). Can you look and see if that file is 0 bytes to? Otherwise, copy that back to the system folder
Click to expand...
Click to collapse
Yes, the app is what I use and I can't even get su to work under adb shell. It looks like I am going to need to re flash.

Used the app, same result....
Reflashing now... Normally not a problem for me to reflash, but I didn't get to backup my text messages and notepad -_-
Oh well...

asrrin29 said:
yes. when I try to use su I get
[1] Segmentation fault su
Click to expand...
Click to collapse
that's weird. all I do in the app is trigger some shell commands like "su" and "busybox cp". But can't you try to do the rooting procedure again by "apply: /sdcard/update.zip" in adb?
Makes me wonder if there are any users, except me, who got this app working?

appelflap said:
that's weird. all I do in the app is trigger some shell commands like "su" and "busybox cp". But can't you try to do the rooting procedure again by "apply: /sdcard/update.zip" in adb?
Makes me wonder if there are any users, except me, who got this app working?
Click to expand...
Click to collapse
not sure that's going to work, because I can't get super user access until I grant it permission without a ui.

F_L_Abs said:
Used the app, same result....
Reflashing now... Normally not a problem for me to reflash, but I didn't get to backup my text messages and notepad -_-
Oh well...
Click to expand...
Click to collapse
I'm sorry ... The Android SDK isn't the best toolkit to do such low level system hacking. The security levels are high, and to break them you have to do all kind of weird stuff. Anyway, I changed the first post and put a extra warning in it.

Is there a way to use Odin 3 to restore the files changed?

DPI Settings (w/ Play Store)

I guess I'm just having a misunderstanding and any help is greatly appreciated.
So the stock DPI setting is 240, I dropped mine down to 190 or so give or take, and obviously that causes certain apps to not even appear on the market. Been using other places just to get apk files so they obviously work fine. I was under the impression that just changing back to 240dpi along with clearing market cache and resetting phone would re-allow me to see certain apps that aren't showing. I must be doing it wrong because this definitely isn't working for me lol
I've seen on other phones Market compatibility fixes to trick the market into thinking we have the stock DPI set. Do we have anything for our E4GT's that will achieve this trick.
I thought I wouldn't have a problem with just going back on fourth but showing off the phone and having to spend 2 minutes to go back and change settings just to download an app is kind of a hassle
Thanks again!

Get LCD Density Modder Pro and use it to patch the Store.
I've gone through a bunch of densities to find what I like, eventually settled on 206 as our screen is 206ppi. Quite happy with it.

I had to clear paly store cache/data, google framework cache/data and reboot. Worked for me.
Sent on HyDrA using Tapatalk 2

Real-Time DPI Changer (no reboot required)

I was tired of the camera not working properly when using a custom DPI. I made an app which lets you change it without reboot (especially nice for ART as rebooting takes 5 minutes or so for me).
Just put it in /system/priv-app and set the permissions to rw,r--,r--.
Let me know if you have any questions.

Does this change all apps at once or does it work on an app by app basis ?
Sent from my SHIELD Tablet

ShrekOpher said:
Does this change all apps at once or does it work on an app by app basis ?
Sent from my SHIELD Tablet
Click to expand...
Click to collapse
It's everything. I was thinking of possibly maming a version later on that monitors tge running app to change dynamically though.

So now that I did this, how does one undo this? Even if I change build.prop your app takes priority..I want to know for when we get app settings and then I can have build.properties set to 500 and this set to 640 and then remove and boom happy xD thank you though, works like a charm!

ChrisJ951 said:
It's everything. I was thinking of possibly maming a version later on that monitors tge running app to change dynamically though.
Click to expand...
Click to collapse
Thanks for making this much needed MOD/APP ... but I don't really get how to use it though. Do I just put a custom DPI (for example 540) in the box? But if I do that, the whole ROM will change to that DPI. How do I change specific apps into a desired DPI, and everything to a different DPI ?
Thanks.

Samsung's Good Lock

Pros: You can almost get it looking like stock android (which is why i'm keeping it), Notification layout is nice.
Cons: Battery dies faster, Widgets/Apps Tray layouts are useless for me. Recent apps layout is worse.
http://imgur.com/a/WpoXB

Tried it......for 5 minutes i prefer being able to use samsung themes like 'blue and black AMOLED' theme. Good Lock does not have a black option in routine options

Hmm . I like it more. Haven't had any battery is issues yet.

Only issue i encountered is it doesnt easily explain Uninstall.
1. You can just drag drop the Icon from the AD to uninstall and
2. You cannot find the app in Applications to Uninstall
3. You have to go to settings and uninstall from there.
4. Once you uninstall, remember to Restart your device as soon as possible.
5. If not restarted, your power button would stop working and the only way to get it back is by a Hard Reboot (Power + Volume Down).
Hope this helps people looking in to this.
Other than that, had no Battery Drain Issues and it worked fluidly. Did find the "Ignore Repetitive Notification" that I dismiss without looking in messages Annoying and sadly, if by mistake I did say so for specific ones (Work Email and Whatsapp), it stopped showing the message notification all together.

Cubed Guru said:
Only issue i encountered is it doesnt easily explain Uninstall.
1. You can just drag drop the Icon from the AD to uninstall and
2. You cannot find the app in Applications to Uninstall
3. You have to go to settings and uninstall from there.
4. Once you uninstall, remember to Restart your device as soon as possible.
5. If not restarted, your power button would stop working and the only way to get it back is by a Hard Reboot (Power + Volume Down).
Hope this helps people looking in to this.
Other than that, had no Battery Drain Issues and it worked fluidly. Did find the "Ignore Repetitive Notification" that I dismiss without looking in messages Annoying and sadly, if by mistake I did say so for specific ones (Work Email and Whatsapp), it stopped showing the message notification all together.
Click to expand...
Click to collapse
You don't have "System UI" With the Good Lock Icon as high drainage in your battery stats?

exzacklyright said:
You don't have "System UI" With the Good Lock Icon as high drainage in your battery stats?
Click to expand...
Click to collapse
Sorry, forgot the * on that. It was mostly visual. Coming from the S6e, the S7e is substantially better due to the much bigger battery, but with a Wireless charger at work, didn't see "major" drain issues.
Although, when the Power Button stopped working yesterday, I almost called Tmo and thought of returning before the Hardboot fix, as this is a System UI App.
Just wondering, did you have AOD on? I did have that off. Doubt it would make a difference, but the Good Lock is a Lock Screen, and since my Nexus 1 days, I remember them always being a Drain.

They just posted a new version and they took care of most of original people complaints, the only thing missing for me right now is the Quick Connect feature that it seems that the only way to get access to it is via Original Notification shade. If the fix this, for me will be a keeper, for sure, I've been keeping it expecting for an update and now I can say that they are 90% where they should be with this.
In general, a very good update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

erasat said:
They just posted a new version and they took care of most of original people complaints, the only thing missing for me right now is the Quick Connect feature that it seems that the only way to get access to it is via Original Notification shade. If the fix this, for me will be a keeper, for sure, I've been keeping it expecting for an update and now I can say that they are 90% where they should be with this.
In general, a very good update.
Click to expand...
Click to collapse
People use quick connect?
The main problem was that it was constantly draining battery
Sent from my SM-G935T using Tapatalk

exzacklyright said:
People use quick connect?
The main problem was that it was constantly draining battery
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Yes I do, not all the time but once in a while, very handy, easy and quick way to connect my devices to my Samsung 4K Smart TV. Best of all, with that, I can see the TV content on my Phone.

exzacklyright said:
People use quick connect?
The main problem was that it was constantly draining battery
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Can you upload the new update 24.0.6 apk ? Thanks

erasat said:
Yes I do, not all the time but once in a while, very handy, easy and quick way to connect my devices to my Samsung 4K Smart TV. Best of all, with that, I can see the TV content on my Phone.
Click to expand...
Click to collapse
I use this as well for my Samsung 4K TV! I actually find myself using it more and more lately. I've run around the house a lot while watching a program and being able to send it to my phone to view while I'm in another room is great! I recently was watching a friend playing a game on his TV, I did a quick connect while I was sitting on his patio with another friend, and was able to keep up with the story-line while on his patio. What's weird is that I didn't get any lag using quick connect but when I tried a simple screen mirror i got lag as well as quality downgrade that was very noticeable.

This is the only problem I've been having so far with Good Lock. That and the horrible app switcher..

For me I would like them to add a private mode toggle.
Sent from my SM-G935T using XDA-Developers mobile app

ktetreault14 said:
For me I would like them to add a private mode toggle.
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
That and sync!

I want to be able to actually choose black, and customize more options such as the lockscreen and recents. I don't like the new recents but I can't leave good lock and give up the stock android icons and drawer

I can't find the app in the app drawer. I visited the Samsung Galaxy Apps store and it said the app is installed. When I clicked on the Good Luck app, the only option is to update the app. Can someone plz help?
Edit: NM. Figured it out.

Skyrocket2 said:
I can't find the app in the app drawer. I visited the Samsung Galaxy Apps store and it said the app is installed. When I clicked on the Good Luck app, the only option is to update the app. Can someone plz help?
Edit: NM. Figured it out.
Click to expand...
Click to collapse
It comes preinstalled on Tmo I believe (or at least it installed itself after a while). I am having issues installing the latest version of Good Lock. Phone keeps restarting and reverting back to stock systemui. RIP

bastienvans said:
It comes preinstalled on Tmo I believe (or at least it installed itself after a while). I am having issues installing the latest version of Good Lock. Phone keeps restarting and reverting back to stock systemui. RIP
Click to expand...
Click to collapse
That's weird. I just updated to the latest version and it's been really smooth with no issues that was there with the previous releases. Maybe try the typical uninstall reboot reinstall? Or if you disabled some apps that could be causing some instability.

tiskewlio said:
That's weird. I just updated to the latest version and it's been really smooth with no issues that was there with the previous releases. Maybe try the typical uninstall reboot reinstall? Or if you disabled some apps that could be causing some instability.
Click to expand...
Click to collapse
Yeah, I installed the first version of Good Lock and it was fine. Uninstalled it shortly after until the next update.
There is no way to uninstall the app from the Galaxy Apps store; the only option is to update it. My Apps does not show Good Lock as installed. I've tried clearing cache, re-enabling all my disabled apps, rebooting several times without much success. I am not the only apparently as several others are having the issue and posting about it on reddit. Hopefully this can be fixed with an update. Don't really want to factory reset to get Good Lock working.

I have no issues uninstalling from my device. I just go to the app drawer tap on the icon and it gives me the option to uninstall. I see what you mean by not being able to delete from Galaxy Apps though
Sent from my SM-G935T using XDA Premium HD app

Non-root DPI changing and Boost+

Just discovered a nice little trick that we get as a result of Boost+.
As some of you might know some apps don't play nice with changing the DPI via ADB.
For these apps you can add them to the Boost+ game battery booster and it will fix any issues.

I haven't come across any issues changing my DPI with build.prop file. What issues are you having?
Also, I have no clue what you screenshotted

Look at the play store after you change the DPI with adb. The top dev icons get giant and pixelated.
Same thing is happening in my screen shots with IRCCloud and the user icons. Second one is with Boost+ enabled.

_-..zKiLLA..-_ said:
I haven't come across any issues changing my DPI with build.prop file. What issues are you having?
Also, I have no clue what you screenshotted
Click to expand...
Click to collapse
This is about non-rooted devices, so changing the build.prop is not an option for those devices..

jollywhitefoot said:
This is about non-rooted devices, so changing the build.prop is not an option for those devices..
Click to expand...
Click to collapse
Oops forgot you needed root for that lol. Its been so long