DPI change doesn't work? - Sprint Samsung Galaxy Note II

To keep this short... I've used multiple density changing apps on the market, and also modified the build.prop but nothing seems to change with a DPI change.
I'm on Jellybomb 4, btw.

Make sure you are saving before you reboot. I tried 160 and it breaks ui and keyboard. 360 broke keyboard only.

Related

TW not working in lower dpi

I was playing around with the DPI changing it to a lower number, the default number is 320 I tried lowering it to 240, the TW launcher will not work, Go launcher works fine but the drop down toggles is locked so you only have access to 5 toggles, so I changed DPI to 280, now every thing works except play store will not let you download apps.

[solved] Anybody figure out how to change DPI of samsung keyboard?

I think I found my optimal Screen DPI for my aging eyes (170), but the keyboard in portrait mode is too small. I installed App Settings thru xposed framework but it doesn't seem to do anything? I change the DPI in App Settings to 230 but it just doesn't seem to do anything when I reboot.
Anybody able to change the DPI of the Samsung Keyboard?
Thanks,
Matt
Not sure what happened...
I reset the build prop to 177 and my keboard is perfect.

[Q] Changing LCD density and customizing the quick launch buttons

I have two questions for you guys about the G Pad 8.3:
1. The default LCD density on this thing is 320 which puts the UI into phone vs. tablet mode (no dual-pane view for Gmail, Email, etc.). The physical density is 273, though, which should activate the tablet (actually phablet) UI. I'm rooted and I've tried changing ro.sf.lcd_density through BuildProp Editor, but on each reboot it reverts to 320. Has anyone else successfully done this? What process (and LCD density value) did you use?
2. Is it possible to customize the quick launch buttons that are activated when you swipe up from the navigation bar? The default ones are Google, Voice Mate, and Quick Memo, and I'd like to change those last two if possible. I can't find anywhere in settings to change those, though.
Thanks much!
The screen density should be easily possible with apps like LCD Density, free on the Play Store (survives one reboot). Alternatively you can also change the dpi for every individual app, by installing the xposed module App Settings.
I don't know a way the quick launch shortcuts can be changed, although there are also apps in the Play Store as well that allow modifications to some extent.
True, I changed the density in build.prop, with editor, restart the tablet has gone a bit 'in bootloop, I rebooted again and everything is restored.
I tried to put 240.
Palux said:
True, I changed the density in build.prop, with editor, restart the tablet has gone a bit 'in bootloop, I rebooted again and everything is restored.
I tried to put 240.
Click to expand...
Click to collapse
Yeah, this tablet seems pretty resistant to changing the LCD density for some reason. Thanks for confirming!

How to change DPI?

Every Hardware I've owned from Samsung gets a bigger nightmare to do anything except what's stock. Samsung is becoming Apple. Anyway, how to change DPI on this Tab? I have a P605. I need a higher value than the default 320DPI becauseball is too small and some apps are unusable because they get elements displaced. However any setting I try to manually editing the build.prop or using a DPI changing app ends up in immediate unbootable system. Before on my Galaxy Mega where I also upped the DPI, just a few apps stopped working.. like the phone and camera. I fixed the issue by replacing them with versions of another Samsung hardware that natively used a higher DPI (I got the apks from a S3). But now in this Tab, things have of course become more complicated. Now the whole system will FC or not boot. This is the last Samsung hardware I'll ever buy.. I'm over this greed of total control of what they make.. and the Knox stuff also drives me crazy.. ridiculous.
Any suggestions? I want experiment with DPI values between 340 and 400 till I find a setting that works for me andthe apps I use. Thanks for the input.
PS - Installing a custom ROM does not solve the problem because I tried also already and even 1 DPI above 320 and the system will not boot anymore.
Have you tried the Xposed Framework + App Settings Module? It lets you change every single app dpi so you dont have to change the system dpi. Only the dpi for the apps you want
Gesendet von meinem GT-I9505 mit Tapatalk
benni2903 said:
Have you tried the Xposed Framework + App Settings Module? It lets you change every single app dpi so you dont have to change the system dpi. Only the dpi for the apps you want
Click to expand...
Click to collapse
Yes, tried it. Lower values than 320DPI (which is the opposite of what I want) works well.. higher values that 320DPI (which is what I want) the Tab freezes and self-reboots.. usually permanently dead till I do a full restore from my backup.. nasty..
As far as I remember the app settings module lets you change the text size. Maybe use 320 dpi and try to raise the text size
Gesendet von meinem GT-I9505 mit Tapatalk

Camera Doesn't Work (Related to DPI Changing)

So i am running into a very strange issue that i haven't been able to find much information on. I am running the latest OOS (3.1.2) rooted, i had changed the DPI a few days ago using build prop editor and everything seemed to be working just fine, except my camera, it suddenly would freeze when a picture is taken, crash, and not produce a picture, and sometimes the picture would be just green.
Here is what iv'e tried:
removed the line from build prop editor and rebooted to get to stock DPI
changed the DPI to stock with the toolkit, then back to a different DPI, then back to stock.
removed the camera app cache
factory reset the phone
Strangely enough the camera in HDR mode appears to work just fine, but it doesn't appear to work in any other mode (including video).
Using the camera with flash always turned on in pretty much any mode seems to also work.
Atlantisman said:
So i am running into a very strange issue that i haven't been able to find much information on. I am running the latest OOS (3.1.2) rooted, i had changed the DPI a few days ago using build prop editor and everything seemed to be working just fine, except my camera, it suddenly would freeze when a picture is taken, crash, and not produce a picture, and sometimes the picture would be just green.
Here is what iv'e tried:
removed the line from build prop editor and rebooted to get to stock DPI
changed the DPI to stock with the toolkit, then back to a different DPI, then back to stock.
removed the camera app cache
factory reset the phone
Strangely enough the camera in HDR mode appears to work just fine, but it doesn't appear to work in any other mode (including video).
Click to expand...
Click to collapse
I posted about this issue a few days ago http://forum.xda-developers.com/oneplus-3/help/weird-camera-bug-t3404660
mr.shme said:
I posted about this issue a few days ago http://forum.xda-developers.com/oneplus-3/help/weird-camera-bug-t3404660
Click to expand...
Click to collapse
Sorry, didn't notice that.
I flashed back to bone stock OOS 3.1.2 and everything seems to be working now... I will attempted to change the DPI again via the toolkit.
I changed DPI with Le DPI Changer (non build.prop method) and everything is working fine. You might want to check it out.
That's why I always say that global DPI change is not a good idea, period.
Much better and additionally more flexible is using the Xposed module "App Settings" where you can run every app at an individual DPI setting and tweak some more things (e. g. having an app run with its tablet UI).
I had the same issue on OOS 3.1.3 rooted and DPI changed.
I enabled RAW mode and it fixed the issue.
crumble6 said:
I changed DPI with Le DPI Changer (non build.prop method) and everything is working fine. You might want to check it out.
Click to expand...
Click to collapse
What DPI value did you set it to? No issues with camera, icons, widgets, etc?
jiznon said:
What DPI value did you set it to? No issues with camera, icons, widgets, etc?
Click to expand...
Click to collapse
400. No issues at all except that when I use "large text" captions in snapchat they display fine on my screen but the text is much smaller and out of position on my friends' phones. Literally not a single other problem with any app I've tried though. I've heard 380 works good too. Tempted to try it but tbh I'm happy at 400 for now.
crumble6 said:
I changed DPI with Le DPI Changer (non build.prop method) and everything is working fine. You might want to check it out.
Click to expand...
Click to collapse
crumble6 said:
400. No issues at all except that when I use "large text" captions in snapchat they display fine on my screen but the text is much smaller and out of position on my friends' phones. Literally not a single other problem with any app I've tried though. I've heard 380 works good too. Tempted to try it but tbh I'm happy at 400 for now.
Click to expand...
Click to collapse
Thanks for the quick reply. So far my experience has been frustrating.
1) Changed DPI to 400 via build.prop edit. Resulted in camera issues. Could not reset DPI or change to any other value. Had to reflash OOS 3.1.3 to fix.
2) Did some research. Heard a OP3 toolkit here on xda could change DPI without issue (I believe it just uses the adb method) . Used it to change to 400. Camera is fine, but I experience wonky sizing issues with widgets, icons on notification banners, twitter photo previews, and a few other little text size issues. Tried using the toolkit to return to default DPI but it simply doesn't change anything.
3) Per your account of this app, I tried it but it us unable to make any change. Looks like I may have to reflash AGAIN, and attempt the Le DPI Changer again.
Bah.
jiznon said:
Thanks for the quick reply. So far my experience has been frustrating.
1) Changed DPI to 400 via build.prop edit. Resulted in camera issues. Could not reset DPI or change to any other value. Had to reflash OOS 3.1.3 to fix.
2) Did some research. Heard a OP3 toolkit here on xda could change DPI without issue (I believe it just uses the adb method) . Used it to change to 400. Camera is fine, but I experience wonky sizong issues with widgets, icons on notification banners, and a few other little text size issues. Tried using the toolkit to return to default DPI but it simply doesn't change anything.
3) Per your account of this app, I tried it but it us unable to make any change. Looks like I may have to reflash AGAIN, and attempt the Le DPI Changer again.
Bah.
Click to expand...
Click to collapse
Sorry, I should have mentioned. I am using Nova launcher and have changed the grid size of the desktop to 11 x 7. Things will probably behave weird if you are using the oneplus launcher.
crumble6 said:
Sorry, I should have mentioned. I am using Nova launcher and have changed the grid size of the desktop to 11 x 7. Things will probably behave weird if you are using the oneplus launcher.
Click to expand...
Click to collapse
No worries. I am also using Nova Launcher with custom grid size. Only issues on my desktop is wonky icon size with Chronus widget.
jiznon said:
No worries. I am also using Nova Launcher with custom grid size. Only issues on my desktop is wonky icon size with Chronus widget.
Click to expand...
Click to collapse
I find enabling widget overlap in Nova and then playing around with resizing widgets I can usually get them looking right in the end.
I had already posted this here but it seemed like Nobody besides me had this problem.
http://forum.xda-developers.com/oneplus-3/help/camera-issues-root-t3409764
I'm glad this issue is getting attention!
running 340 dpi, works fine for me. did it with le dpi changer
Running 290 all good using le dpi changer ?
Sent from my ONEPLUS3
I'm starting to wonder there is a magic DPI number that doesn't break the camera!! Time to test!
I found this solution on the oneplus 3 reddit. Camera works perfectly and there are no weird icons!
https://www.reddit.com/r/oneplus/comments/4satgq/changing_op3_dpi_using_buildprop_without_breaking/
Basically use qemu.sf.lcd_density=xxx instead of ro.sf.lcd_density=xxx in your build.prop!
I'm using 420 and all is awesome now!!
Huge thanks to this guy for posting the solution!!
ro.sf.lcd_density=400 in build.prop works just fine on my device running stock OOS 3.2.1.
Only manual mode is slightly misaligned inside the camera app.
Trying qemu.sf.lcd_density=400 gives me the same result btw.
I never had issues with green photos in HQ or other weird behaviour.
Running dpi 400 via manual build.prop edit since day one
and only had to repeat this after each ota.

Categories

Resources