Develop Bugs

[Q] HowTo Scaling fonts permanently?

Hi!
Spare Parts permit to reduce the scaling of fonts.
This is the logcat line:
Code:
Code:
03-31 10:32:07.202: INFO/ActivityManager(1314): Config changed: { scale=0.85 imsi=222/99 loc=it_IT touch=3 keys=1/1/2 nav=1/1 orien=1 layout=34 uiMode=17 seq=11 themeResource=null}
After a while (i.e. during a restart of ADW Launcher EX or a reboot) fonts scaling resets its value to 1.0.
Q: Is it possible to hardcoding this value by writing a config file (if it exist?)
PS: repeated thread. sorry for that. It will never suceed again. If i am OT tell me. New to DHD, proud to be here

LCD Density changer also does this http://forum.xda-developers.com/showthread.php?t=765639
Free version
Is also a lite version and fully sponsored by adds. The lite version only makes it possible to temporarily change a density setting. This setting will be undone when you reboot the phone. It uses "hot reboots" and no "cold reboots". It doesn't rely on the build.prop density parameter. Should in principle work on all devices. The free version is attached to this post
Full version
Full version (no adds + with the possibility to save the density and/or write it to the build.prop + desktop widgets for fast loading temporarily saved density setting) can be bought from from the Android Market (0.75 Euro). Search for "LCD Densitiy Changer"
I bought it for a SE X1 Mini Pro running 2.1 - it does what it says on the tin, and holds the density change through reboots etc.

paul c said:
LCD Density changer also does this http://forum.xda-developers.com/showthread.php?t=765639
Free version
Is also a lite version and fully sponsored by adds. The lite version only makes it possible to temporarily change a density setting. This setting will be undone when you reboot the phone. It uses "hot reboots" and no "cold reboots". It doesn't rely on the build.prop density parameter. Should in principle work on all devices. The free version is attached to this post
Full version
Full version (no adds + with the possibility to save the density and/or write it to the build.prop + desktop widgets for fast loading temporarily saved density setting) can be bought from from the Android Market (0.75 Euro). Search for "LCD Densitiy Changer"
I bought it for a SE X1 Mini Pro running 2.1 - it does what it says on the tin, and holds the density change through reboots etc.
Click to expand...
Click to collapse
Thank you for your prompt answer.
I have LCD Density changer. This program changes the density of the screen and this is a nice setting but is not what i search. Spare Parts reduce all and only the fonts for a factor (see in the "CODE" section in my first post) maintaining the density and all graphics unchanged.
Spare parts setting do the job, but sometime a process (unknown at the moment) do a font reset to the default dimension.
What i search is to know what configuration file has to be tweaked or modified to have this factor of reduction permanent.
Any idea on that?
Thanks in advance

-----------------------------

axl409 said:
scrivi su google "Cambiare dimensione e font dei caratteri", primo risultato. scusa ma non posso postare link.
i reply in italy, because who did the question is italian
Click to expand...
Click to collapse
Thanks a lot but is NOT what i mean. (i answer in english because is the official language of the site).
The link you provided explain Spare Parts. This is the application i use and do what i want. (read better post #1 and #3!).
BUT
Spare Parts does NOT maintain settings! after a while the font is reset to default!
For that reason (and this is the question) i want to know if the value of the font size can be hardcoded in some configuration file.

I don't know much about programming, but I think that at the moment you can't change default font scaling value, since it always defaults to "1" - it's hardcoded in source code and not being read from any configuration file. Take a look here: goo.gl/1M5ch , so you can see it by yourself.
I'd say that we can try changing line #314 to:
Code:
fontScale = getFloat("ro.test.fontScale", 1);
and see if allowing users to change fontScaling parameter in build.prop breaks any app or not.

I did some research on the code and the fix was much easier than I thought. Would you please test this change:
http://review.cyanogenmod.com/4931
and share your experience. It should make fontScale parameter set by SpareParts permanent over time. If it changes without a reason, please post the steps to reproduce the problem (which app caused the change etc.).

A patch to allow permanent font scaling has been merged into cyanogen source, it's available from nightly #64.

or you could modify build.prop yourself
ro.sf.lcd_density=240 (change to a lower value)
IE; ro.sf.lcd_density=130

Jonesjw362, I think you did not get the point of Font Scaling parameter either. The thing is that if you change your screen's density parameter, not only do fonts get scaled down but everything is smaller as well (like graphics) and it does not always look good. If you change Font Scaling though, only fonts get scaled up/down and it looks much prettier to my eyes.

kszaq said:
Jonesjw362, I think you did not get the point of Font Scaling parameter either.
Click to expand...
Click to collapse
i misunderstood sorry..

paul c said:
LCD Density changer also does this http://forum.xda-developers.com/showthread.php?t=765639
Free version
Is also a lite version and fully sponsored by adds. The lite version only makes it possible to temporarily change a density setting. This setting will be undone when you reboot the phone. It uses "hot reboots" and no "cold reboots". It doesn't rely on the build.prop density parameter. Should in principle work on all devices. The free version is attached to this post
Full version
Full version (no adds + with the possibility to save the density and/or write it to the build.prop + desktop widgets for fast loading temporarily saved density setting) can be bought from from the Android Market (0.75 Euro). Search for "LCD Densitiy Changer"
I bought it for a SE X1 Mini Pro running 2.1 - it does what it says on the tin, and holds the density change through reboots etc.
Click to expand...
Click to collapse
LCD Density changer makes colors and icons look ****ed up

[Q] What's the Default VM Heap Size in CM7?

I tinkered a bit with the Performance page in the CM Settings menu and accidentally chose an option for the VM Heap Size. Previously nothing was ticked, and I later set it to 32M following a forum search.
Still, I prefer having it at default and not messing with anything beyond the clock speed.
Can someone tip me off with the default settings, and maybe explain what it does, too?
Thanks!

[Q] Default BladeBuddy (and similar) settings for Epic Touch?

Like the title says, what are the default settings found in Blade Buddy (and similar apps) advanced settings menu for the Epic 4G touch? I'm afraid I did the ignorant and forgot to write them down/save them. Nothing serious, however I've noticed worse performance in intensive games/apps and would like to default the settings.
I have everything checked, but these are the ones I'm curious about:
debug.sf.hw
media.stagefright.enable-player
media.stagefright.enable-meta
media.stagefright.enable-scan
media.stagefright.enable-http
dalvik.vm.heapsize : value 64m
dalvik.vm.heapstartsize : value (none set)
Dalvik.vm.heapgrowthlimit : value (none set)
Assuming default isn't best, what settings would you guys recommend? I noticed weird freezes while playing Battle Bears -1 after tweaking the settings.
Thanks. I've searched online and in XDA but gave up after falling short

I hate to self-bump, but if anyone is rooted, you can simply download Blade Buddy and tell me what the default settings are
No changes required on your end. The app doesn't do anything if you don't change any settings. Settings I need values for are in the advanced options.
Thanks!

I have the following as default settings:
debug.sf.hw : 0
media.stagefright.enable-player : false
media.stagefright.enable-meta : false
media.stagefright.enable-scan : false
media.stagefright.enable-http : true
dalvik.vm.heapsize : value 64m
dalvik.vm.heapstartsize : value (none set)
Dalvik.vm.heapgrowthlimit : value (none set)
I'm running StarBurst ROM v1.9.8r so these may not be identical to stock settings, but I hope this does the trick for you!

I appreciate it. Thanks!
I was fairly certain that HW was off by default, but wasn't sure. Seems odd that it would be.

[Q] Percent and colors

I have two questions (hope you guys can help me):
1 - Is there a way to hide some numbers? Here's what i want:
$((#usedSD#/#totalSD#)*100)$ = this will give me a percentage of used space in SD card, but i don't want the decimal numbers (23,33 - want to remove the numbers after the comma).
2 - How to apply different colors to a text?
#Battery# < 20 red color
#Battery# < 60 green color
#Battery# > 60 blue color
Sorry for my english and thank you in advance.

yudroid said:
I have two questions (hope you guys can help me):
1 - Is there a way to hide some numbers? Here's what i want:
$((#usedSD#/#totalSD#)*100)$ = this will give me a percentage of used space in SD card, but i don't want the decimal numbers (23,33 - want to remove the numbers after the comma).
2 - How to apply different colors to a text?
#Battery# < 20 red color
#Battery# < 60 green color
#Battery# > 60 blue color
Sorry for my english and thank you in advance.
Click to expand...
Click to collapse
1. You can use floor() to round numbers to their nearest lower integer or ceil() for the upper variant. Your code should look like this $(floor((#usedSD#/#totalSD#)*100))$
You can find all the available math functions for Zooper here: http://zooper.themerapp.com/support/solutions/articles/157988-math-expressions
2. Advanced Parameters are your friend here. The following code put into the Advanced Parameters of a text module will change the color according to your specifications:
Code:
$#BLEVN#<20?[c]ffff0000[/c]$$#BLEVN#>=20 && #BLEVN#<60?[c]ff00ff00[/c]$$#BLEVN#>=60?[c]ff0000ff[/c]$

kwerdenker said:
2. Advanced Parameters are your friend here. The following code put into the Advanced Parameters of a text module will change the color according to your specifications:
Code:
$#BLEVN#<20?[c]ffff0000[/c]$$#BLEVN#>=20 && #BLEVN#<60?[c]ff00ff00[/c]$$#BLEVN#>=60?[c]ff0000ff[/c]$
Click to expand...
Click to collapse
After put this code I have only this text "ff0000ff" - I do not have battery level....what is wrong ?

geeket said:
After put this code I have only this text "ff0000ff" - I do not have battery level....what is wrong ?
Click to expand...
Click to collapse
You probably put the code into the text field instead in the Advanced Parameters field. Scroll down to the end of the module options when editing your text module, there you'll find it.
Send from my secret moonbase via space carrier pigeons

kwerdenker said:
You probably put the code into the text field instead in the Advanced Parameters field. Scroll down to the end of the module options when editing your text module, there you'll find it.
Send from my secret moonbase via space carrier pigeons
Click to expand...
Click to collapse
OK - I have this but...all should look like this:
+add "text" -> in "edit text" write #BLEV# -> in advaced Parameters write Your code

geeket said:
OK - I have this but...all should look like this:
+add "text" -> in "edit text" write #BLEV# -> in advaced Parameters write Your code
Click to expand...
Click to collapse
Yes, that should work ?
Send from my secret moonbase via space carrier pigeons

[Q] Issue with tasker values in Zooper

When I create a Tasker value that can be used in Zooper (#T...#), I can not use this value under Advanced Parameters in an argument.
When I type #T...# it gives me the value. When I use $#T...#=Value?, it doesnt work and it leaves the $T..# blank. Any ideas on how to solve this? I want to use this to change the color of an object when for instance GPS is on

RebelwithoutaClue said:
When I create a Tasker value that can be used in Zooper (#T...#), I can not use this value under Advanced Parameters in an argument.
When I type #T...# it gives me the value. When I use $#T...#=Value?, it doesnt work and it leaves the $T..# blank. Any ideas on how to solve this? I want to use this to change the color of an object when for instance GPS is on
Click to expand...
Click to collapse
Is " $#T...#=Value?" the whole string you entered or are you just partially quoting it? I ask because Zoopers parser engine doesn't respond well to incomplete conditionals and that might throw off the substation of variable tags.
Apart from that I adhoc don't have any other idea. Did multiple widgets with Tasker variables and have not yet encountered this problem. If you upload your profile/task and your widget I could take a look at it for you.
Send from my secret moonbase via space carrier pigeons

kwerdenker said:
Is " $#T...#=Value?" the whole string you entered or are you just partially quoting it? I ask because Zoopers parser engine doesn't respond well to incomplete conditionals and that might throw off the substation of variable tags.
Apart from that I adhoc don't have any other idea. Did multiple widgets with Tasker variables and have not yet encountered this problem. If you upload your profile/task and your widget I could take a look at it for you.
Send from my secret moonbase via space carrier pigeons
Click to expand...
Click to collapse
The entire string is as follows:
[c]$#TGPS#=on?#4a2d8303$[/c]
In Tasker there is a task triggered by profile Variable set %GPS, that reads:
Zooper Widget Pro Variable
ZW variable = GPS
ZW Text = %GPS

RebelwithoutaClue said:
The entire string is as follows:
[c]$#TGPS#=on?#4a2d8303$[/c]
In Tasker there is a task triggered by profile Variable set %GPS, that reads:
Zooper Widget Pro Variable
ZW variable = GPS
ZW Text = %GPS
Click to expand...
Click to collapse
Did you try to setup a task that just sets the variable to 0 or 1 depending on GPS status? String comparison in Zooper sometimes is a bit wonky so I usually try to do it with numbered values instead

kwerdenker said:
Did you try to setup a task that just sets the variable to 0 or 1 depending on GPS status? String comparison in Zooper sometimes is a bit wonky so I usually try to do it with numbered values instead
Click to expand...
Click to collapse
Now it got a bit weird, changed the task to make #TGPS# 1 if gps is on and 0 when off. But when I put the variable in Zooper, it still showed On and Off. So I changed the name of the value to #TSAT# and now the argument works. I think since %GPS is a standard task value, it will make TGPS a standard value as well. Now the argument works with the new value name. Thanks for helping me out
Never mind... forgot I used #TGPS# in another task...fixed that