Jump to content

Recommended Posts

Posted (edited)

If someone find a way to change dpi. I looked into build.prop but there is nothing. I tried two apps on the market, first one said "can't do the configuration" (I have root) the second one didn't change anything after reboot. I'm looking for this because I'd really like to make things bigger!

Can I add something like this to build.prop : ro.sf.lcd_density=240 ?

Edited by ayziaa
Posted

The second app actually added this line (320 dpi). It's not doing anything :(

Posted (edited)

I used to use this app for density: https://play.google....HJvaWQuZHBpIl0.

with this app you can temp apply to make sure it safe .

But you do know it is already at 240dpi ? it is the resolution that makes it all look small.

lol just set mine to 320dpi looks huge.

post-796032-0-77427100-1349980433_thumb.

Edited by Guest
Posted (edited)

It's the one I tried, but before trying I looked into build.prop and there wasn't anything related to dpi which make me thing that the dpi configuration value is somewhere else

EDIT: Am I the only one to find things too small?

Edited by ayziaa
Posted

I used to use this app for density: https://play.google....HJvaWQuZHBpIl0.

with this app you can temp apply to make sure it safe .

But you do know it is already at 240dpi ? it is the resolution that makes it all look small.

lol just set mine to 320dpi looks huge.

that's what I did!! 320 I'm trying again

Posted

Yeah it is small, but as the screenshot above 320 looks to big, but maybe because it been so small :wacko: :lol:

Posted

Doesn't change still 240!!!! Why can you do it and I can't?

Posted (edited)

You must be doing wrong, but I am using the pro version but it is same.

Set density by clicking standard tab, select 320, then click temp apply( just to make sure it safe for you)

After that you can select save as system dpi

Edited by Guest
Posted (edited)

I just set dpi and hit "save and reboot" but it doesn't work Still 240 on reboot.

What does temp apply means? I don't have that! Maybe I need pro version

Edited by ayziaa
Posted

yup, I have root. I'm pretty sure temp apply is not the same tweak that in free version which means that it's not editing build.prop but something else

Posted

yes working on pro version with temp apply. It HUGUE !!! :D Thank you for your help! :)

Posted (edited)

It should apply on save as system dpi too....I try now......

Strange, it does not save as permanent ? Not that I want it, I lower dpi on every device, so I happy with it small.

Edited by Guest
Posted

It should apply on save as system dpi too....I try now......

Strange, it does not save as permanent ? Not that I want it, I lower dpi on every device, so I happy with it small.

No it does not! Only temp apply seems to be working

Posted (edited)

I will try ro.sf.lcd_density=320 in build.prop

oh....it already there, placed by lcd density modder, but it is not recognised?

Edited by Guest
Guest schkinx
Posted

slightly bigger text .. try settings > accessibility > large text

Posted

I allready said that, second post

Yes of course you did....I got a 3 second goldfish memory :lol:

Posted (edited)

Yes of course you did....I got a 3 second goldfish memory

don't worry about it! But I really don't know what else to try! also from what I have seen using 320dpi and 280 (probably no very good for market compatibily) it's not displaying things very well. The overall look a bit streched.

Edited by ayziaa
Posted (edited)

In recovery log I see the lcd density, so it must be somewhere. Anyone know where else other than build.prop the system can read lcd density from ?

post-796032-0-63315600-1350039175_thumb.

Edited by Guest
Guest rickywyatt
Posted

yep the default.prop found in / but can't be changed lol as its in boot.img

Posted

Yes but if it is in boot.img how come lcd density modder pro can edit dpi on "temp apply"?

Guest rickywyatt
Posted

because on you reboot Android looks at default.prop and changes it back

Posted

Yeah it is just temp, so it cannot stick after reboot, as recovery log shows it is reading from somewhere else on boot, as ricky said default.prop, so unless we crack bootloader it not be done as we need custom rom. to be able to change anything in boot.img.

Posted

Ok! So / point is boot.img ? And if we touch that we could brick the device because bootloader check boot partition signature and it will just refuse to boot?

At this point ( now that we have root) what are chances that we could hack the bootloader?

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.