Related
I wanted my first post to be something other than a questions, forgive me if its in the wrong section.
Ok i got my gtab on december and been loading it with whatever app and games i could find, some worked some did not, the ones that did not work i just said it wasnt designed for a tablet, the only rom i have used was vegan untill one day i tryed cm7 beta5 and i was so impress by the higher resolution but too much bugs to stick around so i learn about how to change the resolution with lcd density changer and i notice some thing, one of the apps that forced closed which was a version of alphalt 5 stated to work
(i actually have 2 version of the game from installing many different version and finally found one that worked full screen and perfect touch....if you install the game you will know what i mean)
so i stated to test other app to see....one app that i install earlier (eagles nest did not worked) and some apps that worked only in scaled mode started working in full screen
so if an app does not worked get lcd density changer and changed it and test it, the default is 160, i think 120 is the smallest you can go and the change does not survive a reboot so you wont mess anything up
I dont know if it worked for real or if i was just luck but i test the two apps many time and it worked for me
thanks to the dev for making our device so awesome i have been using xda for many many years way back when i had my ppc6700 and then my mogu phone so thank you devs lol
I believe you can edit the build.prop to do the same thing.
Any brave dev out there care to port the Touchwiz calculator and dialer for 190 screen density. Infuse is begging to be run at that dpi, just that those stock app do not scale at all.
Thanks in advance.
Yes this would be much appreciated
Is the 190 DPI really that much better? I have not tried it yet. What is stock?
crawlgsx said:
Is the 190 DPI really that much better? I have not tried it yet. What is stock?
Click to expand...
Click to collapse
It IS , stock is 240 ...
190 is Infuse Heaven.
rraquib said:
190 is Infuse Heaven.
Click to expand...
Click to collapse
Guess I need to get off my butt and try it then :-D
I actually have mine at 200 and love it.most apps are.coded to use only 160, 180, 200, and 240 led density. However, Ymmv
.
crawlgsx said:
Guess I need to get off my butt and try it then :-D
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using XDA App
I would even settle for 200 but the DIaler looks terrible . Oh well.
h8rift said:
I actually have mine at 200 and love it.most apps are.coded to use only 160, 180, 200, and 240 led density. However, Ymmv
.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
rraquib said:
190 is Infuse Heaven.
Click to expand...
Click to collapse
care to elaborate on how you did that?
I assume it is in the build.prop but I have never edited it myself
There are apps in the market that can do this for you. As for myself, I used root explorer to edit my buildprop. Look for the line with lcd_density, change the value from 240 to 190. Save and reboot.
rraquib said:
There are apps in the market that can do this for you. As for myself, I used root explorer to edit my buildprop. Look for the line with lcd_density, change the value from 240 to 190. Save and reboot.
Click to expand...
Click to collapse
I bought root explorer, changed the lcd_density in build.prop file and now my dialer is shifted to the left. Pretty much everything shifted a little to the left. I love it this way but what did you do to fix the shifting issue?
TIA.
NVM, I was being idiot and did not read that you created this thread to find answers to that.
I noticed that even the apps drawer opens in the top left corner and spacing around it is wasted. I think you have to find all the lcd_density tags and change the values for everything?
S2K_MoZo said:
I bought root explorer, changed the lcd_density in build.prop file and now my dialer is shifted to the left. Pretty much everything shifted a little to the left. I love it this way but what did you do to fix the shifting issue?
TIA.
Click to expand...
Click to collapse
You don't. A dev needs to work on the issue. This is the entire reason this thread even exists.
never mind did it a see the diff..
Icons all outa wack at 190
chvybeatsford said:
never mind did it a see the diff..
Icons all outa wack at 190
Click to expand...
Click to collapse
See, I suppose if you don't wanna use the stock dialer, calculator and TouchWiz you can still use this 190 dpi. Just probably have to use different apps. I personally won't use it but that's cause all of the PNGs in the theme I work on are designed for 240 dpi.
beatblaster said:
See, I suppose if you don't wanna use the stock dialer, calculator and TouchWiz you can still use this 190 dpi. Just probably have to use different apps. I personally won't use it but that's cause all of the PNGs in the theme I work on are designed for 240 dpi.
Click to expand...
Click to collapse
Yea moving back to 240 till stuff is fixed. Looks great at 190 but im not to worried.
Go Launcher Ex and Go Contacts (it includes a Dialer) will get you 75% there @ 190 but the key pad during call is still the stock one . I still think it looks gorgeous at 190 density. Any one knows how the calculation is done. I will try to take a crack at it. At least can start with the calculator with out bricking the phone.
rraquib said:
Go Launcher Ex and Go Contacts (it includes a Dialer) will get you 75% there @ 190 but the key pad during call is still the stock one . I still think it looks gorgeous at 190 density. Any one knows how the calculation is done. I will try to take a crack at it. At least can start with the calculator with out bricking the phone.
Click to expand...
Click to collapse
Makes me wonder if you can control the span via simple XML edits..... hmmm....
You can, some one has done this for another phone. I know where they are in the Main.xml files just don't know what the values should be in relation to the pixel density. Is there any way to make it auto scale?
EDIT: I think the file attached is where the magic needs to happen but how?
Did you try messing with:
android:layout_width="320.0dip" android:layout_height="302.65625dip"
It is in tag:
<LinearLayout androidrientation="vertical" android:id="@id/Linewrapper" android:background="@drawable/call_dial_panel_bg_01" androidaddingRight="6.0dip" android:layout_width="320.0dip" android:layout_height="302.65625dip">
I am tempted to mess with it and see what it does. I am pretty sure that will do something but it will be more like trial and error since we don't know what that measurement equals to...
I would start with the calculator first. Can easily be remedied if things go wrong. Here I am attaching a deodexed Calculator APK. Take a whack at it if you like.
S2K_MoZo said:
Did you try messing with:
android:layout_width="320.0dip" android:layout_height="302.65625dip"
It is in tag:
<LinearLayout androidrientation="vertical" android:id="@id/Linewrapper" android:background="@drawable/call_dial_panel_bg_01" androidaddingRight="6.0dip" android:layout_width="320.0dip" android:layout_height="302.65625dip">
I am tempted to mess with it and see what it does. I am pretty sure that will do something but it will be more like trial and error since we don't know what that measurement equals to...
Click to expand...
Click to collapse
Prior to, or even after root, is there any way to change the default text sizes to a larger one. As an example, Weather.com on the Sensation versus on the Vibrant is almost unreadable in anything but perfect lighting conditions. Same thing with any solitaire app I've tried. Also (I'll try this again...) is there any way to change the default font, pre-root, or does it by definition involve a framework change? TIA...
wbexpress said:
Prior to, or even after root, is there any way to change the default text sizes to a larger one. As an example, Weather.com on the Sensation versus on the Vibrant is almost unreadable in anything but perfect lighting conditions. Same thing with any solitaire app I've tried. Also (I'll try this again...) is there any way to change the default font, pre-root, or does it by definition involve a framework change? TIA...
Click to expand...
Click to collapse
Thanks for at least trying to look up the answer.
For changing the default font, sorry but no, root access only. And for changing the text sizes, honestly there isn't a app i know, even with root access, to change the font size. Maybe installing another font once we obtain root will fix the problem for you. Sorry i couldn't be more of more assistance.
EDIT: Use spare parts+ in the market. You can make the font larger there. Just tested for you. Doesn't really change the font size in the weather app though im afraid.
Shaquiel Harris said:
Thanks for at least trying to look up the answer.
For changing the default font, sorry but no, root access only. And for changing the text sizes, honestly there isn't a app i know, even with root access, to change the font size. Maybe installing another font once we obtain root will fix the problem for you. Sorry i couldn't be more of more assistance.
EDIT: Use spare parts+ in the market. You can make the font larger there. Just tested for you. Doesn't really change the font size in the weather app though im afraid.
Click to expand...
Click to collapse
And, thank you for trying to get me an answer. I'm gonna have to decide whether there are too many little nitzy issues around to make keeping it worth it. I think if there was absolute, 100% certainty that we will be able to root eventually, I would stay with it. I am in no way brand-loyal, and am still pissed about the RFS file system, the GPS debacle and the FroYo non-updates, but truth be told, my Vibrant with it's currently ROM actually performs better than my Sensation. For example, about 10 minutes after a reboot the RAM indicator on See PU turns yellow and stays there. The Vibrant's almost always shows a full green bar. 1.2 Ghz processor/768 megs of RAM/Gingerbread? Big whoop! Sorry, just venting cause I'm bored. Thanks again...
wbexpress said:
And, thank you for trying to get me an answer. I'm gonna have to decide whether there are too many little nitzy issues around to make keeping it worth it. I think if there was absolute, 100% certainty that we will be able to root eventually, I would stay with it. I am in no way brand-loyal, and am still pissed about the RFS file system, the GPS debacle and the FroYo non-updates, but truth be told, my Vibrant with it's currently ROM actually performs better than my Sensation. For example, about 10 minutes after a reboot the RAM indicator on See PU turns yellow and stays there. The Vibrant's almost always shows a full green bar. 1.2 Ghz processor/768 megs of RAM/Gingerbread? Big whoop! Sorry, just venting cause I'm bored. Thanks again...
Click to expand...
Click to collapse
Well of course its performing better, especially if its rooted. Your Samsung Vibrant isn't running Resource hog, unoptimized HTC sense 3.0. Just wait until we get root, your thoughts will change.
Shaquiel Harris said:
Well of course its performing better, especially if its rooted. Your Samsung Vibrant isn't running Resource hog, unoptimized HTC sense 3.0. Just wait until we get root, your thoughts will change.
Click to expand...
Click to collapse
I know your finger is right on the pulse of the S-Off discussions. Would you "bet the rent money" that root is a certainty?
Hi there,
I was looking through the forum without lucky and I have a question. I have a SG3 and I would like to change the LCD density from build.prop without brick my phone. So my question is if anyone know what are any possible value for this?
The default value for my last SG2 was 240, and now the SG3 comes with 320. I used to use the SG2 with 160, but I'm not sure if this will work with my SG3.
Thanks in advance, and hope that this info help to anyone else in the community.
Regards,
PwOn said:
Hi there,
I was looking through the forum without lucky and I have a question. I have a SG3 and I would like to change the LCD density from build.prop without brick my phone. So my question is if anyone know what are any possible value for this?
The default value for my last SG2 was 240, and now the SG3 comes with 320. I used to use the SG2 with 160, but I'm not sure if this will work with my SG3.
Thanks in advance, and hope that this info help to anyone else in the community.
Regards,
Click to expand...
Click to collapse
I've tried few resolutions but they keep crashin the phone...so i just gave up...as every time i have to reflash the rom i'm using cos i cant open any apps...if somone knows a working settings would be great to share with us
smilu said:
I've tried few resolutions but they keep crashin the phone...so i just gave up...as every time i have to reflash the rom i'm using cos i cant open any apps...if somone knows a working settings would be great to share with us
Click to expand...
Click to collapse
bump
SOLUTION:
Before change LCD Density value in build.prop make sure that you have installed Apex Launcher or Nova Launcher in your SG3. In that way your phone will not crash...
PwOn said:
Hi there,
I was looking through the forum without lucky and I have a question. I have a SG3 and I would like to change the LCD density from build.prop without brick my phone. So my question is if anyone know what are any possible value for this?
The default value for my last SG2 was 240, and now the SG3 comes with 320. I used to use the SG2 with 160, but I'm not sure if this will work with my SG3.
Thanks in advance, and hope that this info help to anyone else in the community.
Regards,
Click to expand...
Click to collapse
From my understanding on the Galaxy S3 if you go any lower then 240dpi you will crash your phone. Anything lower then 240 I believe would be used for tablets, and the like.
I set mine to 240. lcd density did not work. build prop change via rom toolbox did and it looks AMAZING for 10 seconds then crashes. (freezes) eventually reboots (trying to reset in adb from CWM now) suggestions?
what could be causing it to crash I REALLY want that higher effective resolution. BADLY.
running leaked JB rom
I set my GS3 LTE to 240, works really well. However there were a couple of qwerks to note:
The launcher is rubbish, changed to EXLauncher pro
I had to mod the email app to fill the screen. sadly i can't attach the modded apk to this post as it is too big.
The camera app is a little strange, but perfectly usable.
The clock app crashes on launch - very irritating, however i set alarms using the voice controls! i should install an alternative clock app.
nerys71 said:
I set mine to 240. lcd density did not work. build prop change via rom toolbox did and it looks AMAZING for 10 seconds then crashes. (freezes) eventually reboots (trying to reset in adb from CWM now) suggestions?
what could be causing it to crash I REALLY want that higher effective resolution. BADLY.
running leaked JB rom
Click to expand...
Click to collapse
you got it so far. use alternative launcher. use alternative clock
calculator and talk are also borked
there IS a user working on converting the apk's to work on the S3 in fact he has most of them done but they don't work on US S3's only the international S3. he says he will try to make them work for US S3's (fingers crossed)
The S3 at stock res sucks. it was MADE for 240 in my opinion.
FYI I rooted the device with I9305_CWM_Recovery.tar.md5 and CWM-SuperSU-v0.96.zip then changed ro.sf.lcd_density in puild.prop from 320 to 240.
for some reason there are 2 entries of ro.sf.lcd_density. I assume the first one gets parsed and the second one ignored, as I changed the second one first to no effect. eventually i changed both.
---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------
nerys71 said:
you got it so far. use alternative launcher. use alternative clock
calculator and talk are also borked
there IS a user working on converting the apk's to work on the S3 in fact he has most of them done but they don't work on US S3's only the international S3. he says he will try to make them work for US S3's (fingers crossed)
The S3 at stock res sucks. it was MADE for 240 in my opinion.
Click to expand...
Click to collapse
Completely agree. it seems utterly crazy to make such a nice big high res screen then just scale up all the apps as if it was designed for only people with poor eyesight. I almost put my device on ebay ready to go back to iphone before i started getting into it.
Do you have a link to the the modded files? I was just looking through the camera app dimensions definitions and I don't have the time to change those! The email app just involved 3 dimension changes.
GS3 with slimbean.
I Installed slimbean 4.3 beta.2 and it has my screen density as 245. If you take a look at the screen shot I uploaded it shows what to do for changing screen density. Hope this helps.
I'm coming from running a smaller nav bar size of my nexus 4.
I can't stand the icons being this large there is just no need for it.
Do anyone know what scripts I need to edit to get it down to 24dpi ?
Thanks
Sent from my Nexus 5 using XDA Premium HD app
sitnlow4life said:
I'm coming from running a smaller nav bar size of my nexus 4.
I can't stand the icons being this large there is just no need for it.
Do anyone know what scripts I need to edit to get it down to 24dpi ?
Thanks
Sent from my Nexus 5 using XDA Premium HD app
Click to expand...
Click to collapse
You could root and then use a build prop editor to change the density. Or you could wait until roms start appearing (PA, etc). You know, give it time, it should blossom
tremblingwater said:
You could root and then use a build prop editor to change the density. Or you could wait until roms start appearing (PA, etc). You know, give it time, it should blossom
Click to expand...
Click to collapse
This is pretty much it. I'm running 320 DPI right now and it's much more usable, but not perfect yet.
Dungeon47 said:
This is pretty much it. I'm running 320 DPI right now and it's much more usable, but not perfect yet.
Click to expand...
Click to collapse
Found my perfect setting of 400. Didn't really like the huge icons by default, and 320 was way too low for me. 400 suits me fine, and replicates roughly my nexus4.
Don't know why Google changed this personally. Never changed DPI before, is there anything I should be aware of now I have done so?
CrazyPeter said:
Found my perfect setting of 400. Didn't really like the huge icons by default, and 320 was way too low for me. 400 suits me fine, and replicates roughly my nexus4.
Don't know why Google changed this personally. Never changed DPI before, is there anything I should be aware of now I have done so?
Click to expand...
Click to collapse
Google changed it because the screen is higher resolution. The only things to be aware of are the possibility of Play Store having compatibility issues. If you get that, just return to stock DPI, update apps, and go back to what you like. The other thing is that it affects everything, so some apps might change their interface as a result.
Dungeon47 said:
Google changed it because the screen is higher resolution. The only things to be aware of are the possibility of Play Store having compatibility issues. If you get that, just return to stock DPI, update apps, and go back to what you like. The other thing is that it affects everything, so some apps might change their interface as a result.
Click to expand...
Click to collapse
If the screen resolution is higher, why could I fit less on my desktop than my Nexus4? I use Dashclock and it chops off data that was always visible on my N4. Seemed like a backwards step.