I use MiniCM9-3.0.0 with nAa-ics-kernel-001, and I wanted to change DPI of my screen from 160 to 120, and after that I have FC of com.android.phone when I call any number or anyone would call me, is there any fix for this because 160 on X8 is not enough for me, and I haven't money to spend on new phone
Related
I just noticed a strange behaviour....
Starting with this rom, but I checked and is so also with other builds.
I'm used to change my DPI density settings to 180, for have a "larger" screen and use 6x6 rows*colums with LauncherPro, to have more widgets on the home screen.
I noticed that setting the DPI to 180 (in the build.prop file) causes an error when going in the contact slide, in the part where you can "link" your contact with their facebook account.
As I click on the "chain" to make the link, the contact app closes itself with this error
processcom.android.htccontacts has been terminated
So I did some tests and it seems that the problem is only with dpi settings of 160 and 180, from 190 to 240 no problem at all.. it works without errors...
Sense ROMS aren't really compatible with LCD Density changes. Use a Non-Sense one if you like having more on your screen (like I do).
StephanV said:
Sense ROMS aren't really compatible with LCD Density changes. Use a Non-Sense one if you like having more on your screen (like I do).
Click to expand...
Click to collapse
Thanks
Yes, you are right.. the strange is that the erro happens only below 180...
Hello to all, someone can change as the density to 180 or 200 and that does not make you FC with the calls, thank´s.
"LCD density " from market
Hi, I've changed to 180 but from time to time I have FC, especially during the long calls (more than 30 minutes)
edit: my streak runs the official dell froyo
Jules Winnfield said:
Hi, I've changed to 180 but from time to time I have FC, especially during the long calls (more than 30 minutes)
edit: my streak runs the official dell froyo
Click to expand...
Click to collapse
I run mine at 240 and it seems fine. I did have some FC with stock dialer at 180 though but I switched to Incoming Call Plus and it seemed to fix the problem.
Krisbo said:
I run mine at 240 and it seems fine. I did have some FC with stock dialer at 180 though but I switched to Incoming Call Plus and it seemed to fix the problem.
Click to expand...
Click to collapse
Then that you recommend 180 or 240
Krisbo said:
I run mine at 240 and it seems fine. I did have some FC with stock dialer at 180 though but I switched to Incoming Call Plus and it seemed to fix the problem.
Click to expand...
Click to collapse
Sounds good if incoming call plus solves this issue, because due to these fc I was afraid to use a 200 or 240 density...and to be honest for my old eyes 160 is too small.
tonime said:
Then that you recommend 180 or 240
Click to expand...
Click to collapse
I run mine at 240 and have had no drop outs since using Incoming Call Plus.
Jules Winnfield said:
Sounds good if incoming call plus solves this issue, because due to these fc I was afraid to use a 200 or 240 density...and to be honest for my old eyes 160 is too small.
Click to expand...
Click to collapse
I'm only 26, I have pefect vision and I found 160 too small. The best thing about running at 240 is widgets are now the correct size. No more tiny Pure Grid Calendar in the middle of my screen
Krisbo said:
I run mine at 240 and have had no drop outs since using Incoming Call Plus.
I'm only 26, I have pefect vision and I found 160 too small. The best thing about running at 240 is widgets are now the correct size. No more tiny Pure Grid Calendar in the middle of my screen
Click to expand...
Click to collapse
I just installed Incoming Calls Plus and so far like it. My density is 180, but it makes the title of the ICP buttons cut off. What is it like at 240?
krazman325 said:
I just installed Incoming Calls Plus and so far like it. My density is 180, but it makes the title of the ICP buttons cut off. What is it like at 240?
Click to expand...
Click to collapse
I put 180 and 240 I like it
krazman325 said:
I just installed Incoming Calls Plus and so far like it. My density is 180, but it makes the title of the ICP buttons cut off. What is it like at 240?
Click to expand...
Click to collapse
Better as it was written for around that density.
cannot rotate screen
thanks everyone for the lcd density info . I changed mine to 240 and everything looks much bigger . just one problem is after reeboting the orientation will not change from portrait to landscape .
I am running 02 froyo build 319 . if someone has any tips to help me fix this . thank you in advance .
Krisbo said:
I run mine at 240 and it seems fine. I did have some FC with stock dialer at 180 though but I switched to Incoming Call Plus and it seemed to fix the problem.
Click to expand...
Click to collapse
I have position 240 and it me works well with the next calls with plus, nevertheless it does me fc with that I do, they know some solution?
Hello to all, after doing several tests to know because towards FC with the calls with 240, I have put the configuration of networks in GSM and it me works very well, at the moment I go the whole morning speaking and it works perfectly.
@tonime does it mean that you have to modify network configuration each time you use 3g network?
Regarding fc, it looks like the only possibility to avoid it during phone conversation is to use the classical 160 density.
i use 140, 180 and others make things looks bigger and i feel like wasting the big screen
After much experimenting I have decided 240 is my preference. I find the "feature" of Dells Stage not rotating to landscape at 240 LCD density really useful, because Stage is really poor in landscape at high densities due to the bad positioning and scaling of the dock bar (for some reason its thicker in landscape).
Solution to all the problems with lcd density, we install Dj Steve's rom to ourselves 1.7.0 it works quite of marvel.
I have 240 not fc and one sees of marvel.
I changed using Build.prop Editor and all is good, except email.apk, it crashes. The same is true with Moxier Mail. K9 email does work. I tested most all software and no glitches, except with email. K9 doesn't support Microsoft Active Sync 2010, the others that crashed, do. I don't see the relevance, but worth mentioning. I cleared data, rebooted, same thing.
Any idea why and how to handle? 180 DPI is just the right size, in my mind, fixing the small text with 160, and all is good except email.
I suggest to experiment with different dpi values in the range from 170 to 190 (for example). I remember from the galaxy s that the contact app was working without any problems when changing the density from 240 to 190.. but a value smaller than 190 caused the app to force close.
Interesting, been following both OP's threads. My eyes aren't 100% up close
so I need a big screen with a font that is big enough. The note is just awesome.
So keen to see how this develops. So much real estate, let's have clear and BIG fonts.
TIP : get the roboto font from XDA thread somewhere. It's great and really readable.
played a little with it. With a density of 175 the email app still runs fine. Even the Touchwiz launcher.
(Search for density changer lite here on xda for quick temporary changes to try out. )
176 Works but..............
170 or higher, the green dialer button is either half hidden, and at 176 all hidden. See font to small post, for additional information.
Hello,
I have changed my G2's DPI from 480 to 420.
I used the Xposed AppSettings Module to change LG's weather app's DPI back to 420.
Unfortunately, it force closes everytime I try to add a new city. Tried deleting app data and cache, but it doesn't help.
Can someone suggest me other things to try? Thank you very much in advance :victory:
I cannot get it to work even with changing the DPI back to normal. Have you found a solution?
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
; (