Database Info

[Q] DEV - Request dpi adjusted stock apps for screen density 190

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

[Launcher][Alpha1] TouchWiz UX on KF

So, we have an improvement, TouchWiz UX is currently WORKING on Kindle Fire, I have tested it and no crucial bug for a user except for the CM9 stuffs and a small DPI of 120, but it is WORKING with a DPI of 120, a little small? Your eyes will adjust. If you want to test it, here it is:
http://www.mediafire.com/?6b65sayjfz86fd3
Go to Google Play Store and use any apps possible to change your DPI to 120, then use root explorer or adb to push it over /system/app and install it! You should be good to go!
Here's what the first version of it looks like:
http://db.tt/WqRG8e64
http://db.tt/S7bmuvyR
Special Thanks to bobrien4975 for making this
What not working that I need help with! Coming Soon
* Working with a DPI of 160, 120 is maybe too small for a good use on a tablet.
* If you have the Galaxy Tab 7 or 10.1 rooted, go to system/app and get us the TWLauncher.apk , Framework-res.apk and SystemUI.apk
* No Wallpaper on Lock Screen
* Soft buttons and notifications that looks like TouchWiz UX. (I guess for this we need a ROM, right?)
Oh, and don't update any apps on Google Play now, if you want it, I suggest changing the launcher then the dpi and update then change the dpi and back to TouchWiz!

sadly no
I spent hours last week trying this... no success the resoultoin on the launcher is weird and doesn't fit right i got contacts app to work and that's all

bobrien4975 said:
I spent hours last week trying this... no success the resoultoin on the launcher is weird and doesn't fit right i got contacts app to work and that's all
Click to expand...
Click to collapse
That's a good start! My KF forces close every time I use the launcher, but it seems you got it running, do you still have the apk or anything so I can test it out and find a solution! Or at least somebody will!

You'd have to port a TW Rom. Like the Stock HC 3.2 Rom on the Galaxy Tab 7. It's mostly AOSP. But I know TW ports are hard, you'd have better luck with HC Sense.

AgentCherryColla said:
You'd have to port a TW Rom. Like the Stock HC 3.2 Rom on the Galaxy Tab 7. It's mostly AOSP. But I know TW ports are hard, you'd have better luck with HC Sense.
Click to expand...
Click to collapse
I see ur point, thanks for pointing that out for me! I guess if it involves ROM porting we should focus on the cm9 first, maybe our awesome devs will do it after their cm9 project! But I still can't see why can't we just port the launcher or make a typical theme at least! Is TW UX built for Honeycomb or are there other reasons? Thanks

pmdisawesome said:
That's a good start! My KF forces close every time I use the launcher, but it seems you got it running, do you still have the apk or anything so I can test it out and find a solution! Or at least somebody will!
Click to expand...
Click to collapse
Sure I will upload tonight
Sent from my Kindle Fire using XDA

okay so i found it now im going to see how quick of a learner i am and will attempt to make work wish me luck

And the main issue wth touchwiz is that it uses a custom framework and system files
Sent from my Kindle Fire using XDA

I hope this gets going. I would LOVE TW on my Kindle.

just thought I would give you guys a update ....I got the TOUCHWIZ UX launcher running I'll write a little guide in a sec it runs fullscren and pretty well
Sent from my Kindle Fire using XDA

here proof and I'm going to try and tweak it better it crashes a lot...
http://db.tt/WqRG8e64
http://db.tt/S7bmuvyR
Sent from my Kindle Fire using XDA

Hey bobrien4975,
Can you send me the apk of the launcher and the framework apk file that is in /system (asuming that you do it this way) and all the files involving this.
I would like to test it, I hear it crashes a lot but it's great to have a try on TouchWiz and see what is the problem.
Can you upload it or something and make it a Alpha version so others may help with the progress and perfect it.
Meanwhile, I will try to get some information and try to port the Soft Buttons and Notification as I see you didn't get it working, I will try to borrow my friend's Galaxy Tab 7 and get the files I need! If you have a rooted Galaxy Tab and want to help, go into system and copy out the twlauncher.apk , framework-res.apk, SystemUI.apk and email it to me: [email protected]

Okay I emailed you
Sent from my Kindle Fire using XDA

bobrien4975 said:
Okay I emailed you
Sent from my Kindle Fire using XDA
Click to expand...
Click to collapse
From your saying I imagine it's very buggy, if it's OK with you, maybe I can change the OP and ask for help, I don't recommend users to use this though, it is not running well, if we have the right dev, this could be finish in a week!

pmdisawesome said:
From your saying I imagine it's very buggy, if it's OK with you, maybe I can change the OP and ask for help, I don't recommend users to use this though, it is not running well, if we have the right dev, this could be finish in a week!
Click to expand...
Click to collapse
Go for it if we can get it working that would be great
Sent from my Kindle Fire using XDA

Made this into a development thread, not a question thread, hoping to get TouchWiz working!

It takes a while for your eyes to adjust to the small density, but when you do, it's amazing, the launcher really is, and for an average user, I don't see any crucial bug here (except for the CM9 stuffs), it's beautiful, not as small as I imagined it would be, and I fooled a dude at my school claiming this is the Galaxy Tab 7!

Nice yeah I kept it at 120 I like it
Sent from my Kindle Fire using XDA

Have anyone tried this, I am looking for a bug report, I am not seeing anything on my Kindle except for the not working Lock Screen lock!

When you changes the DPI, some apps in Play Store seem to be updating and some apps forces close all the time after update, so let's not update any app for now, but installing new apps seem to work great!

[Q] Samsung Galaxy S3 (GT-I9300) - LCD Density

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.

Rendering issue on SlimRom

Hello there,
I just recently installed a Custom Rom on my Nexus S after being on stock for 2 years+. Reason being that it was quite slow so I thought I give a Custom rom a try. I choose to go with SlimRom since it's quite new and I feel excited about the new 4.2.2 Android. Also I used a custom kernel (marmite).
The problem I am facing is that on the first flash (try) I had a perfect ROM until I faced a problem with Exchange and Email application crashing constantly so I followed the advice from the FAQ to wipe data and try again. I thought it would be a good idea to reflash the latest SlimRom as well since it was fixing the Gmail problem with toast notifications. After that point and after some Apps doesn't render correctly. It's not just one (then I would say it's the app) and it's not all of them. So I am posting here in case you have a better idea of what's happening. See the images I attach for get an idea of what I am talking about. In the Chrome application the tab number is like moved some pixels down and on the other application (Online Radio app) the button is moved few pixels up.
Anyone happened to come across that? Any suggestions to fix it?
Thanks

Hi
I would suggest putting this in the development section under the slim ROM section so the developers can help out
But what DPI are you using?
Good luck
Vs Nexus S4G using tapatalk2

That was my first thought as well, but unfortunately I don't have enough posts to let me post there. If an admin can move it there it would be great.
DPI setting : 182 (default from SlimRom)
Sent from my Nexus S using Tapatalk 2

setting to stock [240] DPI has always
cleared squirrly display errors
both on my old 4G and the current 9020a
i use to run 220 and could go back to it
and it would desplay correctly...
ymmv

artafinde said:
That was my first thought as well, but unfortunately I don't have enough posts to let me post there. If an admin can move it there it would be great.
DPI setting : 182 (default from SlimRom)
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
OK, I forgot about the development section requirements.
But like the previous post mentioned... The DPI should be changed to stock 240 or what he has at 220. Give it a try to see what happens.
Settings/interface/general
Vs Nexus S4G using tapatalk2

I tries setting the DPI to 220 and I saw some improvement. So I gyres it's a combination of the custom DPI and the apps. I can survive for now with the rendering bug since I like the small DPI (182)
Thanks for the suggestions
Sent from my Nexus S using Tapatalk 2

It seems it's a problem with the application, since new versions of chrome fixed it.
Sent from my Nexus S using Tapatalk 2

Nav bar resize ?

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.