[Q] Suggested DPi for the Tab 3? - Galaxy Tab 3 Q&A, Help & Troubleshooting

Should I go with default DPI or change it using Textdroider or something similar?
I made a similar thread last week but forgot to make the thread a question.
Also, any tips for improving view quality?

Related

[MOD] Touchwiz Speed

Hi Everyone,
I tried to find a lot on all sections and google for a good touchwiz Mod but to no avail. So i thought of asking u guys for some insight to Mod Touchwiz for our beloved Galaxy S.
So i extracted TouchWiz30Launcher.apk to a folder. Was checking the different resources and i came across \res\anim and i saw two files fade_in_fast.xml and fade_out_fast.xml. Now they are binary XML files. So the question is can we modify or delete some values and speed up touchwiz. I dont care about the fancy transition or effects. Just raw speed. Tried ADW and Launcher Pro but i personally didnt like it. Please forgive me if this is pretty simple. Here is the code for the files.
Guys we modify these values and recompile TouchWiz30Launcher with apk manager.
XML code for fade-in
<alpha fromAlpha="resource_id:0x0" duration="resource_id:0x10e0001" interpolator="resource_id:0x10a0005" toAlpha="resource_id:0x3f800000">
</alpha>
XML code for fadeout
<alpha fromAlpha="resource_id:0x3f800000" duration="resource_id:0x10e0001" interpolator="resource_id:0x10a0005" toAlpha="resource_id:0x0">
</alpha>
check attachment for the files.
Awaiting reply. Thanks in advance.
Come on guys. No one's intrested in tweaking touckwiz.
shawn_pro said:
Come on guys. No one's intrested in tweaking touckwiz.
Click to expand...
Click to collapse
wrong attitude
shawn_pro said:
Come on guys. No one's intrested in tweaking touckwiz.
Click to expand...
Click to collapse
the truth
shawn_pro said:
Come on guys. No one's intrested in tweaking touckwiz.
Click to expand...
Click to collapse
Attention whore?
I might be running Launcher Pro, but I support that you are doing this. Cheers!
Would be useful especially since i've seen Touchwiz drain less battery compared to other launchers. IMHO.
Sent from my GT-I9000 using XDA App
Thanks for your work, may i ask how to use your file? How could i combine it into the existing launcher application?
if it matters that much to you, try picking up how binary numbering works...
Anyways, if I were to try messing around with it - I'd change that last digit in the binary sequence from a 5 to a 3...
Firstly, it isn't binary, it is Hex.
I have not tested but I guess if you change the duration to a lower number, you may get lucky but I expect that these values actually point to another resource for the actual value.
nafem said:
Firstly, it isn't binary, it is Hex.
I have not tested but I guess if you change the duration to a lower number, you may get lucky but I expect that these values actually point to another resource for the actual value.
Click to expand...
Click to collapse
Sorry, I'm not really a programmer...I just offered an idea because nobody else seemed to at the time.
Also, I thought Hex was 6-digit ranging from 0-F/digit? Or is that for colors only?
Hey guys i tried changing the values for the duration but when i over written the modded touchwiz apk to system/app folder i keep on getting Force Closes. Guess i should take a different route. Thanks for the tips guys.
Sorry guys i didnt meant to be rude or show any attitute in the above post. I respect all XDA members. I just hope my findings would be useful to someone who be looking just for it.
Not really sure what you're trying to do with this. Are you trying to remove the fade-in/fade-out animation when using the home screen? Why would you? It looks cool!
I'm interested in removing the animation as well. It looks nice indeed, but it doesn't works smooth on my ZTE Blade. It used to work without lags on my T-Mobile pulse...
After changing the values in the XML file, is it possible to reinstall the file with those changes ?
If so, I can give it a try as well...

[Q] [Theme]Coloured Settings !?

Hi guys,
i just switched to the galaxy nexus and I'm really impressed. Tried some Roms and just installed Codename Android.
But my Question is if it is possible to just get some coloured Settings. I don't want to change the whole "them" of a Rom, i just would like to have the Settings a little coloured and different icons. Maybe S3 or even better HTC like or something like that!?
Is there a way to change this?
I searched in the Themes section, but didn't found what i was searching for.
Cheers,
Ebi

[Q] [REQ] Method of UNIVERSAL Tablet UI Mod for ICS/JB

SORRY TITILE SHOULD BE: [Q] [REQ] Method of UNIVERSAL Tablet UI Mod for ICS/JB, the forum won't let me mod that...
I don't really want to ask similar questions again... I've been looking SOOOOO hard on the internet for this, but all I got are all kinds of ParanoidAndroid ports for other devices, device- and ROM-specific mods not universally applicable and (finally) this thread Link showing a likely but very vaguely descripted method to enable tablet UI for ICS.
I know E4G has already got satisfactory ROMs for this purpose, but I have an HTC Incredible S (no separate Q&A forum for it), which hasn't got AOKP-JB (it has tablet UI included in settings) yet. It's now on CM10.
So I'm asking: how to enable tablet ui for any ICS/JB ROM? (It's OK even if it requires modding framework/services.jar/etc.)
Hope mates here can help for a bit. Thanks
Fixed for ya
XDA Moderator
kennyglass123 said:
Fixed for ya
XDA Moderator
Click to expand...
Click to collapse
Thanks sir.
Sent from HTC Incredible S @ CM10
Lower the DPI in the build.prop.
ro.lcd_density=XXX or something like that.
Sent from my SPH-L710 using Tapatalk 2
That's what I mostly saw in Google which simply doesn't work no matter how low I've changed that. Neither will other build.prop hacks work
Sent from HTC Incredible S @ CM10
AndyYan said:
That's what I mostly saw in Google which simply doesn't work no matter how low I've changed that. Neither will other build.prop hacks work
Sent from HTC Incredible S @ CM10
Click to expand...
Click to collapse
Hrmm....check around in the /data folder to see if there is a local.prop. That would be the only thing i could think of that would override the build.prop, but usually that has to be manually created anyways. What is the default density of CM set to on the Inc S?
zanderman112 said:
Hrmm....check around in the /data folder to see if there is a local.prop. That would be the only thing i could think of that would override the build.prop, but usually that has to be manually created anyways. What is the default density of CM set to on the Inc S?
Click to expand...
Click to collapse
1. build.prop density changes work but DOES NOT bring device into tablet, only shrinks display...
2. IncS has a default density of 240 as most WVGA phones.
3. /data/local.prop not found.
Thank you sir for replying and giving possible solutions But does the answer really goes in .prop files? I mean, in the ParanoidAndroid thread link I provided, 2nd post says for ICS some changes can be done to some .jar framework to lock the preference, but the guide doesn't tell which and exactly how... Could anyone shed light on that?
Sent from HTC Incredible S @ CM10
AndyYan said:
1. build.prop density changes work but DOES NOT bring device into tablet, only shrinks display...
2. IncS has a default density of 240 as most WVGA phones.
3. /data/local.prop not found.
Thank you sir for replying and giving possible solutions But does the answer really goes in .prop files? I mean, in the ParanoidAndroid thread link I provided, 2nd post says for ICS some changes can be done to some .jar framework to lock the preference, but the guide doesn't tell which and exactly how... Could anyone shed light on that?
Sent from HTC Incredible S @ CM10
Click to expand...
Click to collapse
How low have you tried setting it? Eventually, it will enter tablet mode. Try intervals of 20(make a nandroid before hand just in case) I can't remember if WVGA screens need 120, 160, or 180.. one of those should do it though. Tell ya what, I'll try on my Epic which is on CM 10.1.
At 240 is normal
At 180 its almost got a GS3 feel to it. Very spacious.
I skipped 160 and 140.
At 120 it has entered Hybrid UI.
Everything below that point( down to at least 20, which isn't usable lol) is still the Hybrid UI.
I guess that's why on JB, you have to mod the framework. Google is moving away from the traditional tablet ui.
On ICS though, the DPI change will work. I know that for sure. Lol
Sent from my SPH-L710 using Tapatalk 2
zanderman112 said:
How low have you tried setting it? Eventually, it will enter tablet mode. Try intervals of 20(make a nandroid before hand just in case) I can't remember if WVGA screens need 120, 160, or 180.. one of those should do it though. Tell ya what, I'll try on my Epic which is on CM 10.1.
At 240 is normal
At 180 its almost got a GS3 feel to it. Very spacious.
I skipped 160 and 140.
At 120 it has entered Hybrid UI.
Everything below that point( down to at least 20, which isn't usable lol) is still the Hybrid UI.
I guess that's why on JB, you have to mod the framework. Google is moving away from the traditional tablet ui.
On ICS though, the DPI change will work. I know that for sure. Lol
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Is that so? Once on my Epic at CM9 I tried a dpi as low as 120 and the SystemUI just FCs again and again. This time on IncS I had the density also changed to 120 but it enters a Nexus-7-ish phablet mode, and things have become way too small to operate on.
And BTW, the calculated tablet threshold DPI for WVGA is 128.
Damn that Google, I don't so care about Nexus 7 using the phablet UI (it should, really) but why the hell is Nexus 10 doing the same, you wanna make it a giant phone?! AND you removed tablet mode support just because of this?! How utterly childish
Sent from HTC Incredible S @ CM10
AndyYan said:
Is that so? Once on my Epic at CM9 I tried a dpi as low as 120 and the SystemUI just FCs again and again. This time on IncS I had the density also changed to 120 but it enters a Nexus-7-ish phablet mode, and things have become way too small to operate on.
And BTW, the calculated tablet threshold DPI for WVGA is 128.
Damn that Google, I don't so care about Nexus 7 using the phablet UI (it should, really) but why the hell is Nexus 10 doing the same, you wanna make it a giant phone?! AND you removed tablet mode support just because of this?! How utterly childish
Sent from HTC Incredible S @ CM10
Click to expand...
Click to collapse
Here is how I did it on Ainol Tablets. Smali code editing in android.policy.jar and services.jar.
I have no idea though if it is "universal" or not but it worked on multiple tablets.
fuser-invent said:
Here is how I did it on Ainol Tablets. Smali code editing in android.policy.jar and services.jar.
I have no idea though if it is "universal" or not but it worked on multiple tablets.
Click to expand...
Click to collapse
Thank you for finally supplying a legit-looking tutorial. Now, however, I'm concerned with the problem of how to transform a tablet with tablet UI to the Nexus-7-ish phablet UI. Now via build.prop hacks I'm only able to achieve phone UI and I want to know if the same method works and what modification in the parameters this needs to be altered... Thank you all again
Sent from HTC Incredible S @ CM10.1
AndyYan said:
Thank you for finally supplying a legit-looking tutorial. Now, however, I'm concerned with the problem of how to transform a tablet with tablet UI to the Nexus-7-ish phablet UI. Now via build.prop hacks I'm only able to achieve phone UI and I want to know if the same method works and what modification in the parameters this needs to be altered... Thank you all again
Sent from HTC Incredible S @ CM10.1
Click to expand...
Click to collapse
The reverse method should work. Just look for the PhabletUI code and make sure that the relevant sections in the guide I linked to in my thread point the device towards PhabletUI instead. You could also do the same for PhoneUI if you wanted.
If at any point you want to convert the new JB 4.2 UI back to Tablet UI, I used the Tabletizer Alpha app here. When it was done, I did have to move the update.zip to my computer and repackage/resign it for my tablet as well as edit the update-script but the jar files worked.
fuser-invent said:
The reverse method should work. Just look for the PhabletUI code and make sure that the relevant sections in the guide I linked to in my thread point the device towards PhabletUI instead. You could also do the same for PhoneUI if you wanted.
If at any point you want to convert the new JB 4.2 UI back to Tablet UI, I used the Tabletizer Alpha app here. When it was done, I did have to move the update.zip to my computer and repackage/resign it for my tablet as well as edit the update-script but the jar files worked.
Click to expand...
Click to collapse
Great thanks for the tip!
Sent from HTC Incredible S @ PACman v20

✪{RD_NEXTGEN}✪links

for rom go here :http://forum.xda-developers.com/redmi-1s/development/rom-rdnextgencustomizable-fast-smooth-t3016988
for questions and other query go here:http://forum.xda-developers.com/redmi-1s/help/qa-rdnextgencustomizable-fast-smooth-t3016995
res
RESERVED
ONE
More for future
Link Please
Where is the download link brother.
vowels787 said:
where is the download link brother.
Click to expand...
Click to collapse
in development section
DPI/Resolution error, perhaps
Hi. I really appreciate the time and effort you're putting into making this custom ROM for Redmi 1s better. :good: Just one thing, though, that really annoys me.
I dont know if this is a bug or not. If this can be helped, please help me... :angel:
The thing is, icons and other screen elements on the home screen are working fine when using the native launcher. Even the screen icon sizes can be changed as per convenience. :good:
But when using Themer ( ht**s : / / play(dot)google(dot)com(slash)store(slash)apps(slash)details?id=com(dot)mycolorscreen(dot)themer ) [sorry, links not allowed ]
,,,,,,, the screen elements of that launcher/theme are not fitting the screen as they are intended to. I have attached some screenshots of the situation. The empty space thus generated is very usable, I can move icons there,,, but I want that border to occupy at least 80% screen space as it was originally intended to.
Is anybody else facing the same problem while using any other launcher??
Can it be achieved via manual DPI changing? What needs to be done? Plz help.
P.S. I dont know wether thats the case, but after some reading I found out that this could be because of the value of DPI the play store is assuming my phone to be having.... the play store DPI settings or something for my phone If so, please tell me how to change it. Very annoyed.. :|
change system dpi
shanx_verma said:
Hi. I really appreciate the time and effort you're putting into making this custom ROM for Redmi 1s better. :good: Just one thing, though, that really annoys me.
I dont know if this is a bug or not. If this can be helped, please help me... :angel:
The thing is, icons and other screen elements on the home screen are working fine when using the native launcher. Even the screen icon sizes can be changed as per convenience. :good:
But when using Themer ( ht**s : / / play(dot)google(dot)com(slash)store(slash)apps(slash)details?id=com(dot)mycolorscreen(dot)themer ) [sorry, links not allowed ]
,,,,,,, the screen elements of that launcher/theme are not fitting the screen as they are intended to. I have attached some screenshots of the situation. The empty space thus generated is very usable, I can move icons there,,, but I want that border to occupy at least 80% screen space as it was originally intended to.
Is anybody else facing the same problem while using any other launcher??
Can it be achieved via manual DPI changing? What needs to be done? Plz help.
P.S. I dont know wether thats the case, but after some reading I found out that this could be because of the value of DPI the play store is assuming my phone to be having.... the play store DPI settings or something for my phone If so, please tell me how to change it. Very annoyed.. :|
Click to expand...
Click to collapse
try this app:https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi&hl=enand chage to 320
or manually adjust it
go to system>>build.prop>>open build.prop with es file explorer editor or any other>>change dpi to 320
next time please questions in q/a thread of this rom
thanks
There are lot of KK roms, themes, etc Make lollipop based ROM... That's what everyone wants... Good luck
Sent from my HM 1SW using XDA Free mobile app

More DPI discussion

It's new handset time for me and I've been waiting for the release of the Z5P for a while now thinking that it was the all-rounder of Android flagships. After watching a few review videos I've noticed the DPI seems to be set to OAP mode and it's just a huge waste of such a nice screen.
I've read the two threads here about changing the DPI using adb which I'm happy to do but some people seem to be having issues.
I was hoping anyone who has done this can post their new DPI, any issues it's caused and possibly some screenshots of how it looks.
Thanks in advance :good:
I changed DPI from 480 to 430 using ADB..
You can see screenshots from here
http://forum.xda-developers.com/showthread.php?p=63858899
If it helped you please like/press thanks

Categories

Resources