adb wm density and size works like a charm on my other android devices, i.e. i can change the values with ease, but when it comes to the galaxy view anything other than the stock 1920x1080 and 160 (dpi) seems to throw the tablet for a loop, it causes the "unfortunately the ui system has stopped working" error to pop up, which remains until the values are returned to stock.
is there any way around this? i thought it might be the launcher i was using (nova) so i tried a few others, including the view's stock launcher, but no love... i also read that you need to clear the some system app caches but that didn't work either... any help would be appreciated!
well i've discovered that i can use a lower density without any trouble, for example 140 instead of the stock 160, but anything higher than the 160 stock density causes a systemui error... i've tried several different ways to change the density, adb, build.prop, and a couple of apps, and they all do the trick just fine, however the end result is always a systemui error.
aeneas1 said:
well i've discovered that i can use a lower density without any trouble, for example 140 instead of the stock 160, but anything higher than the 160 stock density causes a systemui error... i've tried several different ways to change the density, adb, build.prop, and a couple of apps, and they all do the trick just fine, however the end result is always a systemui error.
Click to expand...
Click to collapse
---- I second that. unfort, the GV is a tad shy with options / tweaking in general.
or at least until root comes along
; (
Related
Have been using LCD Density changer from 240 to 220 dpi on the gorgeous super AMOLED plus screen.
Only recently I realised that in the Android Market the install/download button does not appear when this resolution is changed from default. If I were to set to 240, it is OK. However this does not affect all apps. Searching apps is fine, just not able to install/download.
Now I have to change to default 240 to install certain apps then change to desired resolution.
Anyone knows how to solve this?
In short, there's no permanent fix that I now of, but just a warning:
Use an app like LCD Density Changer in the Market so you can safely toggle the resolution without getting stuck and needing to wipe your data
If you set the resolution in the build.prop below 240 it not only removes the download/install from the page in the Market but with the latest Market version it also gives a message highlighted in bright yellow that the application in not compatible with the device. I also found that even if I changed the build.prop line back to 240 and rebooted I was stuck without access to the majority of the apps I use. I had to wipe data to fix the problem.
What I'm doing is leaving my resolution at 210 and once a week switching back to 240 to update any apps that need updating. Occasionally I have to switch the resolution to download a new app as well. It's not exactly convenient, but it works.
So, today I decided to test my nook at 240 dpi, now that we can do that without a patch (huge thanks to leapinlar). Overall, I really liked the phone UI with the status bar being at the top and the soft keys at the bottom. My main issue is that all the apps (i.e. GMail, etc) show up in phone mode, which I believe is a waste of screen real estate (although it makes sense with everything being bigger and all).
What I'm wondering if there's any way to have the phone UI (i.e. status bar at top, nav keys at bottom) at 160 dpi, so the apps still show up in the tablet layout.
Does anyone know anything about how to go about doing this?
(I already know that the screen dpi is what defines whether the device considers itself a tablet or a phone (160+ means phone, 160 or less means tablet). Based on this information, I don't think it's possible, but I thought I'd ask anyway.)
It's not possible. The system automatically decides based on dpi. You can set it to 161 and it will be phone. However, each app decides for itself whether to display itself in phone gui or tablet gui. I have seen apps still display in phone even if the nook was in tablet and vice versa. They do their own calculations based on the dpi and other factors. Also some apps come in two versions, a tablet version and a phone version. So you can try 161 or there abouts and see how the apps respond. Be warned though that setting to a non standard dpi (120, 160, or 240) may make Market/Play Store not show all apps. I guess you could set to a standard setting temporarily to make market work right and then once your new app is installed, set it back.
I figured as much. Thanks!
On true ICS compatable devices there is also a setting in build.prop called ro.build.characteristics that can be set =tablet... I don't know if it is enabled in our builds or not.
Sorry for a noob question.
I am using rooted 4.4.2 kk stock on i9500. Searched everywhere but havent yet found the solution. How to
Increase the icons size in app drawer. I want to keep the stock launcher ie touchwiz.
I like big icons as in ios
Edit the LCD density setting in build.prop.
Thanks for replying bro... Can you please explain a lil bit..! If it can happen through
Editing building.prop then i reckon its a easy mod. :good:
Sure. In build.prop is a setting labeled "ro.sf.lcd.density". The default setting is 480dpi. Change the DPI setting with a text editor and reboot to make everything on the screen larger or smaller. If you don't want everything to change size when you change the DPI, but do want to make the icons larger, you'll need to use a replacement launcher like Nova or an app like Giganticon.
Thanks for quick reply mate.
Well tried it and experimented with value 300. After reboot
Touchwiz stopped and stuck on error loop. Is there any range limitation
Coze subsequently systemui stopped working too.
You likely did hit a limit. On my old device, which had a stock density of 160, it was possible to go as low as 120 without an issue, and could easily do 240. I personally haven't attempted to change the DPI on the S4 because the icons are plenty large enough as it is.
My personal recommendation is to not bother using the Touchwiz launcher and install Nova instead, rather than playing with DPI settings. Because as I mentioned previously, everything changes size when you change the density. It's not just the icons that will change size, but the text as well.
Indeed..so its not a exact solution but a workaround. I better
Opt for another launcher than editing this then. Thanks mate
Your tip added a little more to my knowledge base.
Has anyone with a rooted device tried modifying the LCD density setting in build.prop? What values looked best? Thinking about rooting my phone just for this purpose.
i changed mine with textdroider_dpi app. Mine is currently set on 480
I set mine to 520 a few times but there are some issues with it. Every now and then my phone would go to a full black screen after boot up and before the lock screen and stay there. Lucky I have a full backup before and after I installed xposed. Having the backup I only had to restore system to get my phone back up and running with nothing lost. Very strange but I've now stayed with the default 560.
I've tried 440 and 480. I'm sticking with 480 for now. The only thing I've noticed so far is that the controls at the bottom of Play Music are a little weird at 480. They were worse at 440, iirc. However, it may just be activating a different layout for what it thinks is a different size screen.
Hey,
I played a bit with android screen resolution and DPI. I've changed the resolution to 1080×1920 and DPI 420.
Then I restarted the phone. I knew that some apps will not display correctly after this action so I didn't bother.
However after few weeks I realised that there is no Batter Life gain with lowering the resolution at all so I reverted back to stock: 1440×2560 and DPI 515 and restarted the phone.
I thought that apps will come back to normal but they didn't. I also tried the DPI of 560 + restart but no improvement inside apps at all.
I used the Terminal Emulator and commands "wm size" and "wm density" to perform all tasks.
Is there a way to get back to normal without flashing the stock ROM ?