Related
I recently installed CM9 a1 on my touchpad and one thing that has been really confusing is the dpi settings and market compatibility. I found that flashing the 120 dpi zip makes the texts really small and even unreadable due to the low pixel density of tp. I tried changing the font size setting to large but unfortunately it only affects system ui and apps but not the third party ones.
My question is, if I change my dpi from stock 160 to 120 or 132 (by editing build.prop) What happens to my installed apps? Do they get updates as usual? And what happens to the apps that are not compatible with the new dpi, do they show up as "unsupported on your device" or just disappear from the market?
Overall, what configuration do you guys recommend?
Thanks
Apps would still run on lower DPIs. Some apps/games need you to toggle the screen stretch to work. You probably won't get updates for many apps. You can fix it by pushing the modified market into system/apps and then fixing its permission. The problem with the modified market is that sometimes it will update, in that case you'll have to clear the app data for the market. Its pretty easy to spot if your market has reverted because the layout is different. Or you can just change the DPI every time you want to install something and reboot and change it back when you're done.
I've been running on 132dpi since the ICS was available. I always change the build.prop in the zip before I flash. I even put the movies market in the gapps zip.
Samsung Captivate CM9 - Glitch Kernel | HP TouchPad CM9 - Bricked Kernel
I use the free app, DPI Changer to change dpi without having to mess with the build.prop file. Also, there's a paid app, LCD Modder Pro, that will make the market work with just about any dpi. I use 155. I read somewhere that it's proportionally the correct dpi for the TP.
chicle_11 said:
I use the free app, DPI Changer to change dpi without having to mess with the build.prop file. Also, there's a paid app, LCD Modder Pro, that will make the market work with just about any dpi. I use 155. I read somewhere that it's proportionally the correct dpi for the TP.
Click to expand...
Click to collapse
I tried the modder pro, but eventually market get's stuck again. the native dpi for the TP is 132 (that's what it is in webos). Wish next to 120 and 160 Dalingrin would also give us a dpi132 patch for the newest builds.
Why doesn't Google just add 132dpi into the next market app so its all official
Beanchimp said:
Why doesn't Google just add 132dpi into the next market app so its all official
Click to expand...
Click to collapse
Because of the variation in screen sizes and resolutions on various devices.
Thanks everyone.
I sucked it up and got LCD modder pro. I changed the dpi to 132 and installed the permanent market fix. It worked great and noticed that I get the same update notifications that I get on my galaxy nexus.
The only problem is that the modified market doesn't have a tablet section (My brother's transformer prime does). It seems like modder pro installs the phone version of the market. Is there a fix for that?
ArmanUV said:
Thanks everyone.
I sucked it up and got LCD modder pro. I changed the dpi to 132 and installed the permanent market fix. It worked great and noticed that I get the same update notifications that I get on my galaxy nexus.
The only problem is that the modified market doesn't have a tablet section (My brother's transformer prime does). It seems like modder pro installs the phone version of the market. Is there a fix for that?
Click to expand...
Click to collapse
you may have to edit your build prop to reflect a device so the market shows tablet apps.
try to change it to this:
ro.product.brand=samsung
ro.product.model=GT-I9100
it may or may not work.
I'm afraid you will eventually not need modder pro and instead fix this yourself with a modded trebuchet apk and build.prop. Until recently somebody modded the trebuchet for 132dpi, just like dalingrin provides the ones for 120 and 160. Hopefully that person will do this for alpha2. Also, I personally do not think there is a big difference between 120 and 132, so the 120dpi fix by dalingrin is perfectly fine for me.
derausgewanderte said:
you may have to edit your build prop to reflect a device so the market shows tablet apps.
try to change it to this:
ro.product.brand=samsung
ro.product.model=GT-I9100
it may or may not work.
I'm afraid you will eventually not need modder pro and instead fix this yourself with a modded trebuchet apk and build.prop. Until recently somebody modded the trebuchet for 132dpi, just like dalingrin provides the ones for 120 and 160. Hopefully that person will do this for alpha2. Also, I personally do not think there is a big difference between 120 and 132, so the 120dpi fix by dalingrin is perfectly fine for me.
Click to expand...
Click to collapse
I use nova launcher so no problem there. trebuchet was way too buggy for me even on 160dpi, and lack of grid settings was a deal braeker.
I tried the 120 fix but I noticed even if you change the font size to large in settings, in some apps fonts are so small and pixelized they are unreadable.
ArmanUV said:
I use nova launcher so no problem there. trebuchet was way too buggy for me even on 160dpi, and lack of grid settings was a deal braeker.
I tried the 120 fix but I noticed even if you change the font size to large in settings, in some apps fonts are so small and pixelized they are unreadable.
Click to expand...
Click to collapse
the problem is that market doesn't care what launcher you use. It's trebuchet that needs to be modded to get it to work. Look inside Dalingrin's dpi fixes and you will see two files - trebuchet. apk and build.prop.
Maybe somebody can tell us how to mod trebuchet and we can build our own fix.
Hi, is it possible to flash buil.prop through CWM ? The idea is I would like to play with the DPI, but I know some values can mess up the system so that the ROM doesn't boot anymore. So the idea is to have a safe and working build.prop as flashable through VWM so that I can experiment without the threat of having to reinstall the whole ROM.
Is that doable ? and would it be sufficient to boot again on a ROM if I put a bad value as DPI ?
Thanks
I may be wrong, but afair one of the DPI apps available on Market, had an option whether to reapply the change on boot
if I'm correct, then you could test the density without risk
Sent from my GT-N7000 using xda premium
I didn't find the app (searched for "DPI" and "density") but one of the app had a description saying you can restore build.pro through adb...so i'll look in that direction.
LCD density will allow you to test a dpi before applying it. Its on play store.
Sent from my GT-N7000 using xda premium
Well, it almost works. I'm on (TW based) Criskelo's v8, changed the DPI to 213, first with LCD density and then with ROM toolbox. I thought it would just boot loop, but
- except for touchwiz, launchers (Go, zeam, adw, apex (small area usuable on desktop though, but maybe it's supposed to work that way)) are ok,
- the s-apps I want work ok : camera, FM radio (I tried S-memo just for the sake of it, it has that well known lines problem)
- s-calendar was replaced by AOSP calendar and it works fine..though I don't see any difference with phone version...maybe because it was not "correctly" installed ?
- gmail, settings, kindle, chrome work as expected in tablet mode. Kindle had to get an update to work in tablet mode, before that it showed the regular phone version.
Now what doesn't work :
- I got that "UI.syst stopped" on every boot (don't care much about it)
- s-contacts doesn't work ! unfortunately I couldn't find a working AOSP contacts.apk, maybe that would work
- s-phone works so that's more important than s-contacts, but the layout is messed up, and you can't use contacts inside the app of course. Unfortunately I don't know of a AOSP dialer for TW roms,
- most annoying negative point to me : status bar doesn't show ! that may be the deal breaker for me.
I went to TW roms because I was tired of little things that didn't work in AOSP based roms, so if I can't find solutions for at least s-contacts and status bar, that's it for me I won't go any further in my quest of TW + tablet mode apps.
KSauzeRK said:
Now what doesn't work :
- I got that "UI.syst stopped" on every boot (don't care much about it)
- s-contacts doesn't work ! unfortunately I couldn't find a working AOSP contacts.apk, maybe that would work
- s-phone works so that's more important than s-contacts, but the layout is messed up, and you can't use contacts inside the app of course. Unfortunately I don't know of a AOSP dialer for TW roms,
- most annoying negative point to me : status bar doesn't show ! that may be the deal breaker for me.
I went to TW roms because I was tired of little things that didn't work in AOSP based roms, so if I can't find solutions for at least s-contacts and status bar, that's it for me I won't go any further in my quest of TW + tablet mode apps.
Click to expand...
Click to collapse
For the dialler, can you set one handed operation in settings (possibly under accessibility) that usually brings it back under operational state. Not sure about a fix for tw contacts though. There are alternative contacts and dialler apps in play store if you search dialler.
Use an alternative launcher for status bar? Recommend adw or launcher7 if you like windows phone layout, both work well. Adw probably more suitable for tablet dpi.
Sent from my GT-N7000 using xda premium
Unfortunately I tried an alternative dialer from the market, it displayed contacts correctly but FC'd as soon as I clicked on a contact, so I think it relies somehow on the TW contact app or framework. As for the status bar, it's never displayed whatever launcher I tried (Go, adw,zeam, apex,launcher pro), so I guess it's part of the framework and not of the launcher.
Greetings, lovely xda community!
I am very happy with all the solutions and innovations I find on these forums.. I am on Ultimate v5 at the moment..
Lately, caught more of the DPI changing texts, from 320 to 240..
But, apparently these is DPI change for apps and for the whole screen of the Note..
So, since my understanding is limited, what I hope to be able to do is to change general DPI of the screen, so that I would be able to put more apps per one homescreen.. I mean, I like Note`s big screen real estate, but there is too much empty space between the apps icons, so maybe something like 6x6 would be better than the usual 5x5... (hmm. I wanted to add attachment of my screenshots of the present state of my screen and homescreens/app icons, but none of the message edit and attachment buttons do not work )..
Anyway, I tried some dpi changers and density changers from Play store.. Boy, I barely managed to get the phone working normally again.. I just made the keyboard pop up with massive numbers and only upper 30 percent of the normal keyboard..
now back to normal..
so, how can I do it? I do not need to run tablet apps,so I do not need dpi change that allows me to download tablet apps from play store..
I would like to fit more icons on the homescreen...
How is that done?
By the way, I did google and search this forum, but it mostly speaks about dpi change for apps..
And ok, there is the "edit build prop", but is that what I need for my intentions, and how can I do it.. and possible negative consequences?
Thanks for stopping and answering!
Peace out...
Hi there, some apps look better in certain dpi modes than others.
I suggest you look at the rom "paranoid android 3 build by beerbong" in the original android development section of the n7000 forum at xda.
Its an aosp rom (google android without the samsung stuff) and it allows changing the dpi of the whole phone (phone, phablet and tablet mode) and changing the dpi of apps alone.
Its a work of art and i suggest you take a look at that rather than messing around with buildprop editors. Goodluck!
Sent from my GT-N7000 using xda app-developers app
Anthropostar said:
Hi there, some apps look better in certain dpi modes than others.
I suggest you look at the rom "paranoid android 3 build by beerbong" in the original android development section of the n7000 forum at xda.
Its an aosp rom (google android without the samsung stuff) and it allows changing the dpi of the whole phone (phone, phablet and tablet mode) and changing the dpi of apps alone.
Its a work of art and i suggest you take a look at that rather than messing around with buildprop editors. Goodluck!
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.. But, I kind of reeeeeeeeeeeeaaaaaaaaaaallllllyyyyyyyyy like to have Touchwiz...
Bought a Galaxy Tab S 8.4 LTE 2 days ago. Beautiful device with great screen, but:
First thing you realize is the small font size in several apps, such as Facebook. Barely readable.
Tried to use larger font size in settings. That did some effect on some fonts, but no consistent result.
Same with the Big Font app - font sizes and overall appearance becomes inconsistent.
So the only way seemed to change DPI Settings. Which required rooting.
I did the CF autoroot thing. And fiddled with DPI settings using Texdroider app. Originally was 220 DPI. I tried 420 DPI.
Unfortunately after reboot, I was stuck at "systemui angehalten" error message, and touch screen did not respond to input.
Unfortunately I could not switch off the device (to reboot), pressing power button for ever gave no effect.
Since you cannot remove the battery on this device I had to let it run down completely over night. Then booting into Recovery (or Download Mode) was possible again.
Tried a full wipe in Recovery an rebooted. But endless systemui crash loop remained.
Will try to re-flash via Odin to get it back working.
So this thread is firstly a warning if anybody wants to change DPI settings on the Tab S.
Then some questions:
* Did anybody overcome the small fonts problem by changing DPI and which DPI setting is advisable?
* any way to force reboot in such case?
Just use xposed module appsetting to set the dpi for apps individually.
Sent from my SM-N9005 using Tapatalk
edan1979 said:
Just use xposed module appsetting to set the dpi for apps individually.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
AppSettings works well.. I changed the overall DPI to 240 because all the fonts were way too big for me.. I then reset certain apps back because some of the stock apps don't work right at different DPIs (camera, etc).
Reflashing revovered the systemui loop crash.
Tried App Settings, but no succes so far.
What do you guys set up, e.g. for facebook messenger?
Thanks!
Appsettings works great!
pibach said:
Reflashing revovered the systemui loop crash.
Tried App Settings, but no succes so far.
What do you guys set up, e.g. for facebook messenger?
Thanks!
Click to expand...
Click to collapse
I have rooted my galaxy for using exposed framework just to be able to use app settings! It then works great. You can set the font size (or dpi I guess) individually for any app. I use different settings ie for Gmail, Facebook messenger, Chrome, Tapatalk... You have to try a bit to find the perfect setting but it's a must.
Without you have tiny fonts!
ok, I installed xposed framework via its installer and then added the app settings module. For those willing to follow this route: you find instructions here: http://www.xda-developers.com/andro...tom-stock-roms-and-hello-to-xposed-framework/
Then it is possible to set DPI (or change font size) for each app individually. Text size and rendering was fine for me with 400DPI for Facebook, Tapatalk, or Nova Launcher. Tried with some other apps as well. Seemingly all look better and are more touch friendly with DPI >= 400. For comparison: stock DPI is set to 320 while real DPI is some 500+.
However it is rather inconvenient to set up each and every app individually via app settings module.
Tried to change the global DPI settings with build prob editor, but that somehow did not succeed, 320 DPI remained unchanged.
Tried with DPI changer to no effect. DPI cannot be changed via these apps. Very strange, have to investigate further.
Then tried again with textdroider, just to check - and device hangs again
No chance of rebooting or anything...but...yeah, found a trick: insert a SIM-card into the slot and then get asked to restart! Works. You can boot into recovery or download mode. Will try with adb to restore the build.prop backup...
Meanwhile - has anyone been able to set global DPI to something like 400-500 successfully? How?
If you look carefully I n the build.prop there usiually got 2 same dpi line... change both or disable one of it.
Sent from my SM-T705 using Tapatalk
Appsettings module is the best option,going in to build.prop is for overall and sends you in to a boot loop .be sure to have a backup
Nexus 5 via Tapatalk
@edan1979, I found only one line in build.prop indicating DPI settings. build.prop editor and DPI changer strangely cannot change that.
I did another test, changing DPI by editing build.prop with Root Explorer. It does change - and goes into UI crash loop
@jball, any idea, why it crashes?
pibach said:
@edan1979, I found only one line in build.prop indicating DPI settings. build.prop editor and DPI changer strangely cannot change that.
I did another test, changing DPI by editing build.prop with Root Explorer. It does change - and goes into UI crash loop
@jball, any idea, why it crashes?
Click to expand...
Click to collapse
Unfortunately I don't, I just know what happened the first time I did it.
Appsettings is the best option though
Nexus 5 via Tapatalk
pibach said:
@edan1979, I found only one line in build.prop indicating DPI settings. build.prop editor and DPI changer strangely cannot change that.
I did another test, changing DPI by editing build.prop with Root Explorer. It does change - and goes into UI crash loop
@jball, any idea, why it crashes?
Click to expand...
Click to collapse
the UI will crash since it was build for the original dpi and the ui setting as well... just install another launcher first and clear the Touchwiz data. It wont crash any longer but if you use touchwiz it wont be good looking... and some other touchwiz related apps will crash as well... that one can be settle using app setting to original dpi.
pibach said:
@edan1979, I found only one line in build.prop indicating DPI settings. build.prop editor and DPI changer strangely cannot change that.
I did another test, changing DPI by editing build.prop with Root Explorer. It does change - and goes into UI crash loop
@jball, any idea, why it crashes?
Click to expand...
Click to collapse
Samsung is too lazy to support multidpi for their apps that's made for specific DPI values.
I did not use Touchwiz. It is SystemUI that crashes...
pibach said:
I did not use Touchwiz. It is SystemUI that crashes...
Click to expand...
Click to collapse
Unless you are running CM, everything is part of Touchwiz, including SystemUI.
kenkiller said:
Unless you are running CM, everything is part of Touchwiz, including SystemUI.
Click to expand...
Click to collapse
Is it?
CM?
The DPI problem and crashes do occur as well on non Samsung devices. Don't they?
pibach said:
Is it?
CM?
The DPI problem and crashes do occur as well on non Samsung devices. Don't they?
Click to expand...
Click to collapse
Not really. I change DPI systemwide on my Nexus devices, they don't crash so easily - they are pretty much unified in terms of software.
Samsung really doesn't like to make a one size fits all firmware for the dozens of devices they release, so you get "problems" like this - to be fair, they don't really anticipate the average user to go around fooling with the DPI values.
Probably Samsung has set 320 DPI on all their devices?
pibach said:
Probably Samsung has set 320 DPI on all their devices?
Click to expand...
Click to collapse
Who knows...who cares? Their assets probably isn't made for all the existing DPIs.
Anyway, xposed app settings works fine for most apps, just gotta live with the systemUI being stuck in that.
If systemUI belongs to TouchWiz, couldn't it be replaced? How?
pibach said:
If systemUI belongs to TouchWiz, couldn't it be replaced? How?
Click to expand...
Click to collapse
Sure....Flash Cyanogenmod for it, if it exists and you don't mind losing all of Samsung's features.
I'm making this thread because I'm curious if its possible to change the resolution of the Galaxy Note 4. I want this to exist here in case anyone else decides to search something similar.
This came to mind because I've noticed while on CM12 that there was a greater resolution and that apps such as KIK or Snapchat had more content on the screen then when I was on stock KK. So is there a way to have a similar resolution in Lollipop in KitKat?
MisterCoolBeans said:
I'm making this thread because I'm curious if its possible to change the resolution of the Galaxy Note 4. I want this to exist here in case anyone else decides to search something similar.
This came to mind because I've noticed while on CM12 that there was a greater resolution and that apps such as KIK or Snapchat had more content on the screen then when I was on stock KK. So is there a way to have a similar resolution in Lollipop in KitKat?
Click to expand...
Click to collapse
Do you mean dpi? Most of the aosp roms have changed the dpi
mgbotoe said:
Do you mean dpi? Most of the aosp roms have changed the dpi
Click to expand...
Click to collapse
Yes that's exactly it. The dpi is lowered in CM12. I'd like to change the dpi overall for the stock Note 4 ROM, it should be possible because I notice that on App Settings on xposed you can do this but for individual apps
MisterCoolBeans said:
Yes that's exactly it. The dpi is lowered in CM12. I'd like to change the dpi overall for the stock Note 4 ROM, it should be possible because I notice that on App Settings on xposed you can do this but for individual apps
Click to expand...
Click to collapse
You have to edit the build prop and change the dpi from 640 to whatever you desire. There are apps that guides you through and buildprop edit is an app that will load your buildprop file for you (without a file explorer) what to keep in mind is unlike stock (and all the rest of the phone company out there smh) touchwiz is the only IOS where apps will not look normal. Camera will appear far right corner, dial will appear for left, etc etc. So you will need to use app settings to readjust them
hope that made some sense!
So it works and everything looks fine but the lock screen is a little off. I used textdroider DPI. Worked well but lock screen needs to be properly positioned.
Tht is one of the apps that will be messed up
This thread should help: http://forum.xda-developers.com/not...anging-note-4-dpi-settings-to-change-t2923408