Hi there, I'm kind of new. I've recently been modifying the dpi on our device and I can't tell you how amazing it makes the screen look. However, on cm9, any dpi lower than 190 causes the phone to crash so calls cannot be made or received.
Other phones have mods for this, however, flashing these causes all sorts of issues with service all together. Is anyone up for making one? I'm on my phone right now, but if you need a link I can post when I get home. Hope this is in the right section, thanks.
Sent from my SPH-D700 using Tapatalk 2 Beta-2
shockvaluejj said:
Hi there, I'm kind of new. I've recently been modifying the dpi on our device and I can't tell you how amazing it makes the screen look. However, on cm9, any dpi lower than 190 causes the phone to crash so calls cannot be made or received.
Other phones have mods for this, however, flashing these causes all sorts of issues with service all together. Is anyone up for making one? I'm on my phone right now, but if you need a link I can post when I get home. Hope this is in the right section, thanks.
Sent from my SPH-D700 using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
cm9 seems to have problems with alot more than just the phone with anything under 182. So if you're planning on going lower than that you might be in for a headache. I agree with stuff looking better at lower densities tho. I have my cleangb rom set at 160. Aokp seems to go to lower densities without as much difficulty, and has a lot more options than cm9, is very stable, and better on battery. In fact, LCD density is an option in rom control in system settings on aokp, so there's no need for a 3rd party app to change it. Maybe you should try flashing that and playing with it for a while, see what you think. Its basically cm9, just, better. IMHO at least. There's a thread for it in the dev section if you're interested. Peace nd happy flashing.
Thank you, I'll definitely give that a try as soon as possible. Do you know if aokp can spoof the dpi so the market is still usable?
Sent from my SPH-D700 using Tapatalk 2 Beta-2
Not sure what you mean exactly, but I've never had a problem using the market on aokp, and my LCD density is set to 175. What program are you using to change the density? Sometimes the actual app can cause the problem. If your rom doesn't have the option to change density then the best two apps you can use, in my experience, are rom toolbox and blade buddy. Both have free versions that allow you to change a lot of settings. And, just to make sure we're on the same page, when you say dpi, you are reffering to LCD density, correct? Meaning the lower the number the bigger your screen appears (icons and text look smaller). Whereas the default value is 240. Just making sure we're talking about the same thing.
Sent from my SPH-D700 using xda premium
186 is my sweet spot
Sent from my MIUI V4 Epic 4G via Tapatalk 2 beta 4
Are you having any issues with the phone or market apps? Which rom are you using? I think different densities look better with different roms. For instance, IMO, miui doesn't look good with anything under 220, but on the other hand, I have cleangb set to 160 and it looks great. Although I had to use spare parts + to make the text bigger, and the stock phone app won't change density, so when you open it, the dialer only takes up a small portion of the screen. I'm looking for a decent custom dialer to fix that. Any suggestions?
Sent from my SPH-D700 using xda premium
Related
Not sure if this is common knowledge, but Storm over on the Nexus board built a color calibrator program that does a great job fixing color balance problems (I'm looking at you Nova LCD).
http://forum.xda-developers.com/showthread.php?t=745248
I am successfully using the cyanogen nightly apk version to correct the blue/purple hue on my nova. It took a little messing around and I do not have a color meter, but I ended up getting results that look great (used my macbook LCD which is color calibrated as the target).
Every LCD is different, but my settings are 919 red/ 905 green / 722 blue.
im about to try this out myself. so i flash to install this???
which one did you install?
Rydah805 said:
im about to try this out myself. so i flash to install this???
which one did you install?
Click to expand...
Click to collapse
If you have CM6, it's already installed... Just go to Settings -> Cyogenmod Settings -> Display -> Render UI, and choose one of the last 3.
Otherwise, flash the Universal APK from that thread-- it worked for my on BakedSnack and Fresh. Don't forget in any case to install the Calibrator APK... it allows you to manually tweak the settings, and also ensures that any settings you choose will be re-applied at bootup.
Well as I don't have cm6, it seems the sense version might be incompatible. I flashed the version sense (desire) and installed the apk. Upon changing any of the sliders results in a fc.
For now I think this calibration is limited to cm6; unless I just screwed something up and somebody else can get it to work. I'm going to try and use the universal install next and see if that'll get it to work. If it doesn't then us sense users are sol.
edtate said:
Well as I don't have cm6, it seems the sense version might be incompatible. I flashed the version sense (desire) and installed the apk. Upon changing any of the sliders results in a fc.
For now I think this calibration is limited to cm6; unless I just screwed something up and somebody else can get it to work. I'm going to try and use the universal install next and see if that'll get it to work. If it doesn't then us sense users are sol.
Click to expand...
Click to collapse
I had thought i had said if you don't have CM6, then try flashing the Universal version, not the Sense one-- the sense one seems limited to a specific ROM for the Desire. I had no issues flashing the Universal one on BakedSnack and Fresh, which both still have Sense.
Apk
One thing to note for CM6 users - the apk file allows you to tweak the 3 color bands to any setting you want, rather than just the 3 presets provided in the Cyanogen render effect menu. I was getting too much yellow in all of the N1 presets and was able to get good whites with the sliders.
I'm not sure how to run this on sense. Why would anyone want to use sense? I'm in a fast 4g area and I still cant stand it.
for stock with root ota 2.2 version .28 odex, use universal zip.
Sent From My HTC Evo Using Tapatalk Pro!
Using damage control jit performance profile sense less with screen brightness at 200 red at 942 green at 892 and blue and 996 and looking great! thanks this is what I have been looking for much cred
Ps when adjusting the screen brightness makes big difference
the universal app keeps fc'ing on me
I guess I'll try the CM version..
Thanks for the heads up on this, my dad just got an Iphone 4 and i was comparing the two displays by playing the same video on both, and noticed that my epson screen has quite a blue hue. He wouldn't stop poking fun at my Evo...until today! Played around with this and got it to be quite a bit more accurate, no more smack talking from him now haha.
Fc
I get force close... I installed the universal.zip and the normal.apk and when I open the app and touch any of the settings the app force closes... Anyone wanna do a mini tutorial on how they got it?
Wow I didnt even notice this. Thanks man!
mrcamposd said:
I get force close... I installed the universal.zip and the normal.apk and when I open the app and touch any of the settings the app force closes... Anyone wanna do a mini tutorial on how they got it?
Click to expand...
Click to collapse
You flash the zip file just like you would anything else-- there's really not much to it.
You don't mention what ROM/Kernel you are running... that might help.
sohr said:
You flash the zip file just like you would anything else-- there's really not much to it.
You don't mention what ROM/Kernel you are running... that might help.
Click to expand...
Click to collapse
Sorry, Yeah that's what i do and the app keeps crashing.
Evo 4G
Running Android 2.2
Baseband v. =2.15.00.07.28
Kernel v.=2.6.32.15-g3a86144
Build number= Fresh evo 3.2.0.0 by flipz
Software number= 3.28.651.1
is that what you have to or are you using another rom?
Finally I got it to work with another kernel. I have all colors in 1000... Tell me your colors so I can compare and maybe use yours
mrcamposd said:
Finally I got it to work with another kernel. I have all colors in 1000... Tell me your colors so I can compare and maybe use yours
Click to expand...
Click to collapse
Guess it doesn't work with netarchy's 4.1.9.1cfs kernel, because I am experiencing the exact same symptoms and am using the same ROM as you. I was beginning to think it was ROM related. What kernel did you end up using?
mrcamposd said:
Finally I got it to work with another kernel. I have all colors in 1000... Tell me your colors so I can compare and maybe use yours
Click to expand...
Click to collapse
I am currently using:
red 972
green 918
blue: 783
Although what you use will all be personal preference... the big thing is pushing the blue down as it is quite overpowered.
freeza said:
Guess it doesn't work with netarchy's 4.1.9.1cfs kernel, because I am experiencing the exact same symptoms and am using the same ROM as you. I was beginning to think it was ROM related. What kernel did you end up using?
Click to expand...
Click to collapse
Yes i'm assuming its a kernel related problem not a rom problem... Im using this kernel it works pretty good and I'm using the bfs one awesome speed in quadrant hitting 1400's
(Im using the beta version "Revision 4.1.9.1-BFS BETA - Fresh Compatible")
http://forum.xda-developers.com/showthread.php?t=719763
sohr said:
I am currently using:
red 972
green 918
blue: 783
Although what you use will all be personal preference... the big thing is pushing the blue down as it is quite overpowered.
Click to expand...
Click to collapse
Those settings seems too dim for me. I guess personal preference has to do a lot with these settings lol... (sticking with the 1000's RGB color)
thanks a lot
mrcamposd said:
Those settings seems too dim for me. I guess personal preference has to do a lot with these settings lol... (sticking with the 1000's RGB color)
thanks a lot
Click to expand...
Click to collapse
If you stick with 1000s for all 3 values, you might as well as not have the APK installed at all, IMO.
The settings you want to use may vary slightly based on your current lighting conditions and the brightness. On my settings, the screen is tiny,tiny bit dimmer-- but that is only because the blacks and greys become true blacks and greys and not dark purple and lilac. At the bare minimu, leave your red and green at 1000 and push the blue down until your greys are true greys....
What are your thoughts on this.. Ive never used it on my epic but with all this extra screen space do you think it will work well with it?.. might actually work out well with this screen
Edit.. that was supposed to say lcd density changer
Tapatalkin' it from my Epic 3g
I am definitely planning to use lcd density changer once I get my epic. At 800x480, things will be huge.
This was the first thing I do on my Evo's, change it to 190. I can't wait to do it on this phone and find that sweet spot.
bump. has anyone tried? working / not working?
Yep. 190 or 200 works well. Doesn't break much. Dialer gets wonky, so does the Volume button on the pulldown shortcuts. I think Contacts too. But I use custom launcher, dialer, contacts, etc, so it doesn't affect me.
im running mine at 160 dialer seems to be a bit wonky but it works
ok i finally got around to installing this thing.. man i gotta say i love it so far.. if we could get the stock dialer and some other little quirks worked out this would be perfect
jok3sta said:
ok i finally got around to installing this thing.. man i gotta say i love it so far.. if we could get the stock dialer and some other little quirks worked out this would be perfect
Click to expand...
Click to collapse
I know. At native 240, this display is comically huge. It looks like a clown prop. The sad thing is, as many have already noticed, changing density/DPI is an "unnatural" thing and will always cause some apps to be deformed. A screen of this size with such a low resolution was a huge design flaw.
yah it is a shame. but not a deal breaker. but with lcd changer it just feel right.. maybe we can try to get some of the talented devs on here to work on the issues..
What about if you flash a custom dialer? Will it resize properly?
Sent from my SPH-D700 using xda premium
ive heard custom dialers work.. but i havent tried yet. in my experience, custom dialers dont change the in-call dialer though.. also the dialer isnt the only problem. the calender is messed up as well along with other little things
So I was playing around with the build.prop, and decided to play with the LCD density. I discovered that if you bring it down, (I just cut it in half from 320 to 160, I don't know what the smallest/biggest it can be is) after rebooting Ice Cream Sandwich will look like how it does on a tablet!
I don't know if everyone already knew this or anything, but I thought it was cool and I bet that someone would be interested in making it work!
The problem is, immediately upon booting, system.ui force closes, meaning that you don't have navigation buttons anymore... I'm no developer, so I don't know why it dies, or how to fix it, but hopefully someone does, because this would be a fun ROM to try!
http://youtu.be/nx0bC-6vxMY
same thing happens if you set it to 240 dpi
try it...things won't b so tiny
Sent from my Galaxy Nexus using xda premium
mrfuzzie23 said:
same thing happens if you set it to 240 dpi
try it...things won't b so tiny
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for testing that, now my question is what's the best way to revert back to how it was? I just reflashed my ROM, but I'm sure there's gotta be a better way...
patrick848 said:
Thanks for testing that, now my question is what's the best way to revert back to how it was? I just reflashed my ROM, but I'm sure there's gotta be a better way...
Click to expand...
Click to collapse
There is an app called LCD Density Changer that I used to use on my Nook Color. It required root and idk if it works on ICS or not.
the way I did it was I ran gscript to remount /system.. which happily force closes after its done so u can leave to another app, then used total commander to fix the build.prop.. I had a copy of build.prop renamed to build.prop.old sitting in /system... on hindsight u could use a script to do this for u..
Sent from my Galaxy Nexus using XDA App
You can change it in Rom Toolbox by JRummy16
240 will run things in tablet mode. If you have errors running some apps like YouTube put in landscape mode first. Also dpi 241 works well but not many tablet apps work
Sent from my Galaxy Nexus using XDA App
IT WOULD BE GREAT TO USE IT IN TABLET MODE W/ SOFT KEYS WORKING. I HAVE BUTTON REMAPPER AND USE VOL -/+ as back/menu. BUT IM PRETTY SURE TELEPHONY AKA PHONE CALLS DONT WORK AT 160 DSI BUT! 120 DSI SHOULD HAVE WORKING CALLS IN ANDROID 4.0.2 AND 4.0.3.
Phone calls work fine at 160.
Easiest way to revert it to have two build.props:
Build.prop and build.prop160
Use root explorer to rename the file you want
I also use the softkeys for root app to get onscreen buttons
If you get a fc loop for any other dpi just use adb push build.prop /system/ to fix
Making sure you have a backed up build.prop in your adb folder.
This looks good lol hope somebody picks up on this asap!
Sent from this GN on 4GLTE!
That's pretty cool, but this thread probably doesn't belong in development as nothing has been developed.
Please don't post in the wrong topic. It pisses me off.
shenye said:
Please don't post in the wrong topic. It pisses me off.
Click to expand...
Click to collapse
Sorry, thanks for moving it.
Hey guys. Just got my SGS2 i love it and the roms are great! i just noticed one issue. When i change my build.prop dpi to 160, a lot of the CM9 tweaks "disappear" im currently on THIS rom and i love it. but i did notice changing the DPI screws up any CM9 ROM. i may just switch to aokp but i prefer CM9..
Ive cleared cache but that didnt do anything.. I am honestly surpised to see how changing the DPI screws a lof of things up... i had no problem changing DPI on my HD2. Any and all help is appreciated thanks guys!
Oh id also like to mention the bottom lights fail to light up as well.
Yeah, those issues are known. AOKP had a phone FC problem with anything lower than 200 DPI.
tzbigworm said:
Yeah, those issues are known. AOKP had a phone FC problem with anything lower than 200 DPI.
Click to expand...
Click to collapse
That explains why it would FC.. thanks man. Is it just a SGH-T989 issue or a AOKP CM9 wide issue?? I think i remember the phone FCing when i had AOKP on my HD2. Thanks for the info! i realized that i'll just change my settings, then change the DPI and they settings still stick!
Just want people to know that upon further investigation I've come to conclude the issue with 160 lies in the fact that android thinks it's a tablet xP so I just set to 162 and everything is just amazing and I love this phone! ^-^
Sent from my Galaxy SII T-mobile using Tapatalk
Does your phone.apk still work at 162? I was under the impression that the phone.apk would not work with DPI less than 180 without installing a modified version.
tzbigworm said:
Yeah, those issues are known. AOKP had a phone FC problem with anything lower than 200 DPI.
Click to expand...
Click to collapse
False. Where does people get these number from? I'm using aokp at 190 dpi with no problem
Sent from Samsung Galaxy SIV
Rod3 said:
Does your phone.apk still work at 162? I was under the impression that the phone.apk would not work with DPI less than 180 without installing a modified version.
Click to expand...
Click to collapse
Yes it does able to execute calls, group calls and everything working perfectly. This would have been my biggest pet peeve with ics but now I'm loving it!
Sent from my Galaxy SII T-mobile using Tapatalk
EDIT: Just tried using the phone, like actually making a call, and on CM9 it FC'd however the call went through. Ugh this really bothers me... i wonder why its FCing im gonna logcat
EDIT NUMBER 2: ^^
Well i figured it out. Having a resolution of 162 causes phone.apk to force close. BUT
THERE IS A SOLUTION (Found it in a couple of minutes on google) It is located here i used the phone0264.apk one and its perfect
Second issue, i tried downloading youtube from the market and it came up "device incompatible" which i knew from my HD2 is caused by "odd" DPI values, so i used a "hacked" market which forces a DPI size to the market. Its attached
To install:
Just rename phone0624.apk to Phone.apk and replace the original and make sure permissions are RW-R--R--
To install market, rename it to, Phonesky.apk and again assign the same permissions.
REBOOT
and all shall be swell again
SORRY TITILE SHOULD BE: [Q] [REQ] Method of UNIVERSAL Tablet UI Mod for ICS/JB, the forum won't let me mod that...
I don't really want to ask similar questions again... I've been looking SOOOOO hard on the internet for this, but all I got are all kinds of ParanoidAndroid ports for other devices, device- and ROM-specific mods not universally applicable and (finally) this thread Link showing a likely but very vaguely descripted method to enable tablet UI for ICS.
I know E4G has already got satisfactory ROMs for this purpose, but I have an HTC Incredible S (no separate Q&A forum for it), which hasn't got AOKP-JB (it has tablet UI included in settings) yet. It's now on CM10.
So I'm asking: how to enable tablet ui for any ICS/JB ROM? (It's OK even if it requires modding framework/services.jar/etc.)
Hope mates here can help for a bit. Thanks
Fixed for ya
XDA Moderator
kennyglass123 said:
Fixed for ya
XDA Moderator
Click to expand...
Click to collapse
Thanks sir.
Sent from HTC Incredible S @ CM10
Lower the DPI in the build.prop.
ro.lcd_density=XXX or something like that.
Sent from my SPH-L710 using Tapatalk 2
That's what I mostly saw in Google which simply doesn't work no matter how low I've changed that. Neither will other build.prop hacks work
Sent from HTC Incredible S @ CM10
AndyYan said:
That's what I mostly saw in Google which simply doesn't work no matter how low I've changed that. Neither will other build.prop hacks work
Sent from HTC Incredible S @ CM10
Click to expand...
Click to collapse
Hrmm....check around in the /data folder to see if there is a local.prop. That would be the only thing i could think of that would override the build.prop, but usually that has to be manually created anyways. What is the default density of CM set to on the Inc S?
zanderman112 said:
Hrmm....check around in the /data folder to see if there is a local.prop. That would be the only thing i could think of that would override the build.prop, but usually that has to be manually created anyways. What is the default density of CM set to on the Inc S?
Click to expand...
Click to collapse
1. build.prop density changes work but DOES NOT bring device into tablet, only shrinks display...
2. IncS has a default density of 240 as most WVGA phones.
3. /data/local.prop not found.
Thank you sir for replying and giving possible solutions But does the answer really goes in .prop files? I mean, in the ParanoidAndroid thread link I provided, 2nd post says for ICS some changes can be done to some .jar framework to lock the preference, but the guide doesn't tell which and exactly how... Could anyone shed light on that?
Sent from HTC Incredible S @ CM10
AndyYan said:
1. build.prop density changes work but DOES NOT bring device into tablet, only shrinks display...
2. IncS has a default density of 240 as most WVGA phones.
3. /data/local.prop not found.
Thank you sir for replying and giving possible solutions But does the answer really goes in .prop files? I mean, in the ParanoidAndroid thread link I provided, 2nd post says for ICS some changes can be done to some .jar framework to lock the preference, but the guide doesn't tell which and exactly how... Could anyone shed light on that?
Sent from HTC Incredible S @ CM10
Click to expand...
Click to collapse
How low have you tried setting it? Eventually, it will enter tablet mode. Try intervals of 20(make a nandroid before hand just in case) I can't remember if WVGA screens need 120, 160, or 180.. one of those should do it though. Tell ya what, I'll try on my Epic which is on CM 10.1.
At 240 is normal
At 180 its almost got a GS3 feel to it. Very spacious.
I skipped 160 and 140.
At 120 it has entered Hybrid UI.
Everything below that point( down to at least 20, which isn't usable lol) is still the Hybrid UI.
I guess that's why on JB, you have to mod the framework. Google is moving away from the traditional tablet ui.
On ICS though, the DPI change will work. I know that for sure. Lol
Sent from my SPH-L710 using Tapatalk 2
zanderman112 said:
How low have you tried setting it? Eventually, it will enter tablet mode. Try intervals of 20(make a nandroid before hand just in case) I can't remember if WVGA screens need 120, 160, or 180.. one of those should do it though. Tell ya what, I'll try on my Epic which is on CM 10.1.
At 240 is normal
At 180 its almost got a GS3 feel to it. Very spacious.
I skipped 160 and 140.
At 120 it has entered Hybrid UI.
Everything below that point( down to at least 20, which isn't usable lol) is still the Hybrid UI.
I guess that's why on JB, you have to mod the framework. Google is moving away from the traditional tablet ui.
On ICS though, the DPI change will work. I know that for sure. Lol
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Is that so? Once on my Epic at CM9 I tried a dpi as low as 120 and the SystemUI just FCs again and again. This time on IncS I had the density also changed to 120 but it enters a Nexus-7-ish phablet mode, and things have become way too small to operate on.
And BTW, the calculated tablet threshold DPI for WVGA is 128.
Damn that Google, I don't so care about Nexus 7 using the phablet UI (it should, really) but why the hell is Nexus 10 doing the same, you wanna make it a giant phone?! AND you removed tablet mode support just because of this?! How utterly childish
Sent from HTC Incredible S @ CM10
AndyYan said:
Is that so? Once on my Epic at CM9 I tried a dpi as low as 120 and the SystemUI just FCs again and again. This time on IncS I had the density also changed to 120 but it enters a Nexus-7-ish phablet mode, and things have become way too small to operate on.
And BTW, the calculated tablet threshold DPI for WVGA is 128.
Damn that Google, I don't so care about Nexus 7 using the phablet UI (it should, really) but why the hell is Nexus 10 doing the same, you wanna make it a giant phone?! AND you removed tablet mode support just because of this?! How utterly childish
Sent from HTC Incredible S @ CM10
Click to expand...
Click to collapse
Here is how I did it on Ainol Tablets. Smali code editing in android.policy.jar and services.jar.
I have no idea though if it is "universal" or not but it worked on multiple tablets.
fuser-invent said:
Here is how I did it on Ainol Tablets. Smali code editing in android.policy.jar and services.jar.
I have no idea though if it is "universal" or not but it worked on multiple tablets.
Click to expand...
Click to collapse
Thank you for finally supplying a legit-looking tutorial. Now, however, I'm concerned with the problem of how to transform a tablet with tablet UI to the Nexus-7-ish phablet UI. Now via build.prop hacks I'm only able to achieve phone UI and I want to know if the same method works and what modification in the parameters this needs to be altered... Thank you all again
Sent from HTC Incredible S @ CM10.1
AndyYan said:
Thank you for finally supplying a legit-looking tutorial. Now, however, I'm concerned with the problem of how to transform a tablet with tablet UI to the Nexus-7-ish phablet UI. Now via build.prop hacks I'm only able to achieve phone UI and I want to know if the same method works and what modification in the parameters this needs to be altered... Thank you all again
Sent from HTC Incredible S @ CM10.1
Click to expand...
Click to collapse
The reverse method should work. Just look for the PhabletUI code and make sure that the relevant sections in the guide I linked to in my thread point the device towards PhabletUI instead. You could also do the same for PhoneUI if you wanted.
If at any point you want to convert the new JB 4.2 UI back to Tablet UI, I used the Tabletizer Alpha app here. When it was done, I did have to move the update.zip to my computer and repackage/resign it for my tablet as well as edit the update-script but the jar files worked.
fuser-invent said:
The reverse method should work. Just look for the PhabletUI code and make sure that the relevant sections in the guide I linked to in my thread point the device towards PhabletUI instead. You could also do the same for PhoneUI if you wanted.
If at any point you want to convert the new JB 4.2 UI back to Tablet UI, I used the Tabletizer Alpha app here. When it was done, I did have to move the update.zip to my computer and repackage/resign it for my tablet as well as edit the update-script but the jar files worked.
Click to expand...
Click to collapse
Great thanks for the tip!
Sent from HTC Incredible S @ PACman v20