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
Related
I have smasung gt-i5800 with touchwiz 3.0.
So i changed the density and restarted the phone. It starts fine until 'the sweep the glass' is out of bounds on screen and everything is pretty much frozen.
I know there's a way to fix it with the update.zip method..
Ok... I am using LCD Density Changer to go from the standard size of 240 to 182 that part works great.
So to the question.. Is there a way to make this change with effecting the sound of the phone. When I make the change and the phone restarts I have no sound. I am not sure if I save it to default if I will have sound. Can anyone help with this.
I have this problem too. I can't change the density because when I do the temp/preview it reboots without sound. If I click save and then I reboot, it doesn't save the density.
edit: changed the build.prop manually and it works fine.
Hi everyone. This is a weird thing - I haven't found anyone with a similar issue, either here or with Google-fu.
I successfully rooted my HTC Desire a while ago (S-Off) and was pretty happy with it, the LCARS bootanimation installation also went well. After trying out a lot of apps, finding the best configuration for the phone etc. I decided to format and set up the whole thing again on Monday, to have a clean installation and no more space issues.
Although I went for the CyanogenMod V7.1.0-RC1 this time 'round I somehow doubt that has something to do with it, but who knows. Okay, SD card was set up anew, custom mod got installed, everything went as smoothly as it possibly could. (cool story, bro)
However, after I moved the bootanimation.zip into the system\media folder and rebooted, the animation started, but only at half the size it usually has, in the middle of the screen. I tried another one and it was the same thing. The longer one of the two also broke off in the middle with a brief flash, as if I'd pressed the Power button, then stayed dark until I pressed the Power button twice (turn off/ back on), only then it would show me the pin number display.
Apart from that the phone works perfectly.
It's not an incredibly important issue, just something I find weird and would like to fix, if possible. Does anyone have an idea what could be the source of this?
Doesn't anyone have the slightest idea?
you try flash bootanimation over Android Flasher..
Hi majko11293 - first of all thanks for pointing me to this programm. I'd used it before (worked brilliant with my own custom splash screen), but somehow lost it again.
Anyway, even when flashing it with Android Flasher, the bootanimation stays at half size. The animation itself changes depending on which one I choose, but the size issue remains...
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.
I have a rooted Huawei Mediapad T5, running stock ROM. But 1 reason why I had rooted it, was because of it's annoying resolution. Everything is way too big which causes too much screen space to be filled.
I searched XDA and google to solve this problem. But everytime I boot, the tablet is back to it's orriginal screensetting.
I've found out that lowering the DPI works in my case. It seems to be set at 320 orriginally? At least this is the info I get from terminal and ADB commands. Other apps like CPU-Z tell me 255.
Well, let's say it's 320.Then lowering it to 280 or 300 makes a big diffrence for me and everything looks way better arranged on the screen. But again, after boot it changes back to 320...
Things I've tried (with no luck ofcourse):
- Changing dpi using my tab connected to my laptop using ADB (DPI settings get applied, but are gone after reboot).
- Changing dpi using a terminal-app on the tab itself (DPI settings get applied, but are gone after reboot).
- There was no "ro.sf.lcd_density=" in build.prop. So I added it and rebooted. But no change after reboot.
- I've tried some (root) apps from the app-store, for changing DPI-settings (DPI settings get applied, but are gone after reboot).
When I change DPI with the Terminal, and check display settings first. then it shows me the standard DPI settings of 320. When I use this same terminal to change DPI to 300, then it gives me 2 lines after checking again.
Physical density: 320
Override density: 300
So I was thinking, maybe I should look for a way to change this "Physical density" vallue to trick keeping it like this?
-------------------------------------------------------------------------------------------------------------------------
Edit:
I think something is off with my screenresolution.
Information in the terminal gives me: Physical size 1200x1920
Websites detect it as 960x600
and the physical dimentions are:
width 21,6 cm
height 13,5cm
diagonal 25,5 cm
-------------------------------------------------------------------------------------------------------------------------
Edit 2:
I've found that other tabs with similar screen size and aspect ratio have an resolution of 800x1280.
Tried to change this. And this setting is still saved after rebooting. But the screen looks way to big now.
What happens when you in build.prop make DPI setting persistent?
Code:
persist.ro.sf.lcd_density
jwoegerbauer said:
What happens when you in build.prop make DPI setting persistent?
Code:
persist.ro.sf.lcd_density
Click to expand...
Click to collapse
Should I add this line in build.prop?