honestly great upgrade from 2.2.3 on my wind LG P999DW phone but i need some help, it seems if the DPI is to low i get a force close on the dialer com.android.phone FC
if the dpi set 181 or lower then i get a FC on com.android.phone (182 DPI or higher no problem)
is there anyway to fix this because i wouldnt mind dpi being around 160
thank you in advance
This is a known issue with messing around with DPI, you should've seen it coming as changing the DPI can have Market issues among some apps.
But, there is a modified phone.apk app floating around, let me see if I can find it for you.
Sent from someone's Galaxy Nexus running AOKP + Franco
Related
Hey guys I have been playing around with the Gingerbread leaks for the O3D and I am loving it so far, but I only have one problem with GB at this stage.
The problem being if I set the LCD Density to 167 (Got used to it on all my Android devices) the Rom only works until it locks. Once it locks the first time after the setup it goes into a boot loop and the only way to restore that would be to flash a ROM with lcd_density set to 240. Then the Rom works perfectly without any issues.
I have noticed that no LCD Density changer app works on the O3D, Ive used a few for different devices and they all worked. I have also seen that there are 2 entries for lcd_density in build.prop. Removing either changes nothing. Changing them both breaks the phone too.
Would there be anyone wise enough to be able to get this done, make the LCD desity either changeable or 167?
Edit : If I set the density lower in 20 increments with font changer (root) then i get it down to 200 before causing bootloops. I dont understand why, it worked fine in Froyo
I appreciate the help.
I cant believe everyone with an optimus 3D runs it at 240 LCD density...
Is there anyone that could help with this?
I have the same problem but didn't bother to ask since i don't think there is a solution until we get the official release.
I tried 160 with my TV and got the perfect resolution. But as you say, as soon as i reboot my phone i get into a boot loop.
I think that the only thing we can do at the moment is to restore the density to 240 if we reboot the phone and put it back to 160 or whatever when it has booted up again.
This is my problem:
I set the density to something below 240, then my phone gets stuck in a bootloop, so I enter CWM and make a factory reset, then i can get in to the phone with the new density. The phone works great until i reboot my phone which will get my phone in a bootloop. This time, the factory reset wont work. So i have to restore the system partition and start from the top.
As you say, it worked fine in froyo for me as well.
EDIT:
I will take a look at build.prop and manually change the settings.
Okay I found the problem and a solution.
I created a new thread so the discussion about the supported densities can be held there separately.
http://forum.xda-developers.com/showthread.php?t=1351420
Hi,
I've recently installed CM9 (stable) on my SGS2 i9100. All was good.
Then, all of a sudden, I got a "unfortunately, com.android.phone needs to close"-error whenever I tried to make a call. I've searched XDA and tried all suggestions listed (clearing data of phone, contacts storage, google services; wiping cache) without success. I subsequently changed my display density back to the original 240 DPI (from the 180 DPI that I've come to love) and the error was gone.
Lowering my DPI to 180 causes the error to re-appear.
I've used two different apps to change the DPI: "LCD Density Modder", and "resolution change / Density", ("LCD Density" doesn't seem to do anything) both with that same problem.
I really like the ability to make phone calls, yet I also like the high resolution and smaller text a lower DPI provides.
so:
- why does lowering the DPI cause that error?
- what alternative to above mentioned apps do I have in lowering my DPI?
- any other suggestions?
any help is greatly appreciated.
Since I'm fairly new to XDA I can't really post on the thread that AOSPAL made for this kind of thing, so I'm here reporting a bug on build5 Paranoid Saberdroid ROM.
Problem presents itself everytime I change density through any third part app. Evrerytime I change the DPI, when it comes to rebooting the phone, phone gets bricked, but with LCD Density changer, DPI is only changed after first reboot, every reboot after that, DPI goes back to standard 340. Because of the no hybrid setting thing that AOSPA 4+ has, density changing hasn't been included with the ROM, but something must be blocking the 3rd party apps from working effectively.
I have a little strange problem with Camera application after changing DPI in my S6.
After rooting I changed DPI as in every my device. Everything was fine except Camera app: there is a much smaller window with application, there is also some problem with on-screen buttons reaction.
I changed DPI in many devices and NEVER have such problem.
Any suggestions? For now I go back to stock DPI, but it sucks for me...
This is a natural occurrence since the camera app is baked in. I have the same issues with the dialer and calculator. Use Google camera instead.
Would deodexed ROM be solution?
Tapatalk @ Galaxy S6
After going through the really frustrating pleasure to downgrade from 6.0 back to 4.4.2 to get back my beloved customization, I'm now facing an even bigger issue.
For some reason I am unable to change the DPI of my Mate 7. I've tried it all, apps, editing the build.prop manually.. nothing. Even though the build.prop still says the DPI is set to my custom 420, the interface is still at 480 DPI.
Has anyone experienced a similar issue or know about a solution? I'm really puzzled as to why the build.prop setting is simply ignored.