Hi,
I am a total newbie to streakdroid. (also to dell streak). I previously had mytouch 4g. The icons on the home screen as well as the applications launcher are too small for the streak at par with mytouch4g. Is it possible to increase the icon size and also the the font size?
I did install my streakdroid with the 1.61 option enabled
TIA
Look for an app called LDC Density and chane the size to a larger number. Maybe 180 or 200. You may notice things do not line up as you get larger and larger.
Sent from my Dell Streak using XDA App
thanks that worked like a charm
I tried the LCD density changer app however after a reboot the system reverts back to the previous settings of the icon size. Anyone have insights on this?
Regards
found the soultion over at android forums
Method 1 - ADB
1. Download LCD Density w/ 2.2 market Fix - This also contains the 2.2 market fix (without the stagefright)
2. Put the build.prop in your android-sdk\tools folder
3. Connect your phone via usb, make sure it shows up with adb devices
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
Method 2 - Root Explorer
1. Copy the build.prop to the root of your SD card
2. Long press on build.prop
3. Select "Copy"
4. Navigate to /system
5. Click R/W in the top right corner
6. Paste, and overwrite
7. Reboot
Your screen will now look like this, giving you much more space. And If using ADW launcher, you can use 6 X 5 rows of icons!!
Now if you really like to do things yourself, in the build.prop..
Change
ro.sf.lcd_density=240
to
ro.sf.lcd_density=200
push, reboot.
If you want to revert back, just push this Stock Build prop back into place
Click to expand...
Click to collapse
.
New users are not allowed to post external links
Related
So have anyone noticed various apps incompatibility issues?
I noticed this after updating to CM7.1 that my navionics app was "incompatible" from the market place even though I had it on the stock device.
After flashing back to stock/cognition, it worked again.
Today I flashed to the "unnamed" rom, now I noticed that some games, like Let's Golf! 3 is incompatible.
This brings me to the question, what is the official LCD density of the AT&T SGS2 so that I can set with an app or something to ensure the greatest compatibility of apps?
Thanks
The official density is 240. I too found problems when getting away from that so I have left it alone. I am used to the bigger fonts now.
What app did you use to set the LCD density?
You can modify the build.prop file in the system folder. The app I use is 'Root Explorer' and the method is below:
The line to modify is 'ro.sf.lcd_density=240'
- make sure folder is mounted as 'R/W'
- long press the 'build.prop' and select 'open in text editor'
- change the current value (240 in the example above)
- hit save and exit
- reboot
Your existing build prop is saved as a .bak file
This is the process I use with 'Root Explorer' - may work similarly with other file apps
Hey, try Font Size app and select small fonts... I use tht.
Is there a way to change the honeycomb lockscreen clock? The current font/ text looks terrible and hard to read during the day. I just wnat to change the color and change it to not be transparent at all. Any way possible?
I heard of using ninjamorph, but i could never get it to work, the tablet always rejected my resources.apk due to magic not being signed correctly, despite following all guides.
Anyway to do this via and app, or system file mod?
Yes i have root by the way.
Answer after scouring internet.
I was surprised nobody answered this topic on the well known and big community that is XDA. Kinda shocked. This question sat here dead for a long time. Well I found a solution on another forum.
It pertains to the transformer prime.
But basically to change that clock font, you just have to overwrite a few fonts that the clock uses, tricking it into believing they are normal fonts for the clock.
The fonts are located in:
/system/fonts/
and you have to change the following font files:
AndroidClock.ttf
AndroidClock_Solid.ttf
AndroidClock_Highlight.ttf
You can overwrite these files using any .ttf file you choose (but android has a render box for the clock so some fonts may get cut off on edges if they are too big and not resized)
I got pretty decent results with the DroidSans.ttf font already in the fonts folder.
1. Use "Root Explorer" and navigate to /system/fonts/ and then click the "mount r/w" button above (to allow read and write to this location for this session).
If you get a "permission error" in this location it is because you do not have root, did not allow root explorer in super user prompt or did not click the "mount r/w" button in root explorer at this location.
2. Copy the fonts you want to modify. Then paste copies into the same location.
These fonts are:
AndroidClock.ttf
AndroidClock_Solid.ttf
AndroidClock_Highlight.ttf
3. Make 3 copies of a particular font you want to replace these.
I used DroidSans.ttf and made 3 copies.
4. Then copy the name for AndroidClock.ttf.
Delete AndroidClock.ttf.
5. Rename the new font (a copy of DroidSans in this case) to take its place and paste AndroidClock.ttf .
6. Repeat steps 4 and 5 for for other 2 copies of DroidSans.ttf and AndroidClock_Solid.ttf and AndroidClock_Highlight.ttf.
7.Verify that each font was copied and you have 3 "new" fonts that match the names:
AndroidClock.ttf
AndroidClock_Solid.ttf
AndroidClock_Highlight.ttf
IF YOU ARE MISSING A FONT, ANDROID MAY REFUSE TO BOOT OR SOME FEATURES MAY BE MISSING. I am unsure of exact problem, but better safe than sorry.
8. Reboot tablet. Enjoy new font
Of course you may use any font you like or use ADB to do these steps(but is not very user friendly)
Here is the post i found:
http://forum.xda-developers.com/showthread.php?t=1061483
You do not HAVE to use ADB, root explorer works fine, but if you do not have a root access file manager, ADB can do this as well. I also did not have to change any permissions on the new font files as the originals had same permissions. If they are messed up, you can always fix permissions in clockwork mod recovery or do the permissions manually using a command.
Thanks
helped me. thanks!
Im thinking to change the notification bar's font as well, which font is it for the notification bar?
im looking for a screen dimmer mod like the one that was being used in Homebase. i know there are some market apps like screen dimmer but these are not the same. the mod im talking about lowers the minimum screen brightness by lowering the current being delivered to the backlight itself. there's an old thread about it here http://forum.xda-developers.com/showthread.php?t=1245332&highlight=manual
i havent been able to get it to work on wetdream. ive tried both pushing the framework apk with adb and manually editing the files with apk manager but the first caused a bootloop and the latter a bunch of google FC.
anyone know if there is a working mod(or how to get this one working) to set the minimum screen brightness lower?
i got it working with gingermod, for some reason it didnt work on wetdream. if anyone is interested here what you do
1. Download APK manager
2. Grab framework-res.apk from your phone under \system\framework\ (you can use root explorer or adb push) and place it in the "place-apk-here-for-modding" folder
3. Run Script.bat and select option 9
4. go to projects\framework-res.apk\res\values\arrays.xml and edit your values with the ones roger posted in my link above
5. Once edited, compile the apk using option 11
6. Is this a system apk. Ans: y
7. Qn: Aside from the signatures...least. Ans: y
8. Prompt: In the apk manager folder u'll find a keep folder..... done then press enter on this script. Press any key to continue . . . go to "keep" folder and delete resources.arsc and then press any key
once that is done you can also change the current that is drawn from the screen from the default 25mA to 5mA by using terminal or adb shell (this mod will help with battery life)
heres the command
su
cd sys/bus/i2c/drivers/lm3532/0-0038/leds/lcd-backlight
echo 17 00 > registers
reboot
for a more detailed explanation on what you are doing with these commands check out roger's thread in the above post.
Hi,
Is there any mod to set pixel density to 320.
I have X920D and I run Virtuous Rom
I tried through pixel density apps in play store but with no luck.
You need a kernel that enables /system writing while booted then you can use one of the apps.
Sent from my HTC6435LVW using xda app-developers app
kdahri said:
Hi,
Is there any mod to set pixel density to 320.
I have X920D and I run Virtuous Rom
I tried through pixel density apps in play store but with no luck.
Click to expand...
Click to collapse
1. Boot into recovery
2. adb pull /system/build.prop
3. open build.prop in a text editor and edit the line that says "ro.sf.lcd_density=480" to say "ro.sf.lcd_density=320"
4. save the file
5. adb push build.prop /system/
6. reboot
EDIT: If you use anything between 320 and 480, it will work, but you are going to have issues with market apps not showing up. I personally prefer 400 DPI, but it mucks my market up. Not worth it to me.
BotsOne said:
1. Boot into recovery
2. adb pull /system/build.prop
3. open build.prop in a text editor and edit the line that says "ro.sf.lcd_density=480" to say "ro.sf.lcd_density=320"
4. save the file
5. adb push build.prop /system/
6. reboot
EDIT: If you use anything between 320 and 480, it will work, but you are going to have issues with market apps not showing up. I personally prefer 400 DPI, but it mucks my market up. Not worth it to me.
Click to expand...
Click to collapse
This ^
Also if you have a kernel which enables write-to-system, you can use Solid Explorer to go into /System and directly edit the build.prop and save it.
Though I believe if you switch from 480 to 320, it stops sense launcher from working. Which is why I use nova prime.
sense does not work with 320, you need an senseless rom
thank you all that was helpfull
Sense does work down to about 370, and you can use LCD Density Modder Pro to download a modified version of the play store that thinks you're running 320.
Hey guys, Im here to complain. I'm super tired, so I probably won't be very easy to understand.
Anyway, my Huawei Activa 4g was rooted and all was well. I went to change the DPI with the DPI Modded app from the play store, and its all screwed up now. I can't get past my lock screen, it only shows the clock and the emergency call button. I can't swipe the dots, and they aren't just invisible. I was dumb and deleted my backup.
Please, get back ASAP, as I am panicking.
PS: Usually I sound much more intelligent, but I literally nodded off three times as I wrote this.
You have a custom recovery like CWM, right? When you used the DPI Modded app, did it make a backup of your build.prop file on your SD card? If not, do you remember what your stock DPI value was prior to you changing it?
I can tell you what to do, but it's easier if you just follow this guide. Since you can't boot into your ROM, boot into recovery and follow the rest. adb works in both the ROM (if USB debugging is enabled) and in custom recoveries.
http://forum.xda-developers.com/showthread.php?t=1236732
If you have the backed up stock build.prop file, then you can directly skip to the part where you copy it from sdcard to the system partition. If you don't have it, then you need to open this build.prop file (that you get on your computer using adb pull) with a text editor and change the value of this one line ro.sf.lcd_density=, to whatever the stock DPI value was before you changed it. If you don't remember, then try 160. If that doesn't work, repeat the process with 240. Standard DPIs for devices are -
LDPI (Low DPI) = 160
MDPI (Med DPI) = 240
HDPI (High DPI) = 320
Your phone falls into the LDPI category, so 160 should work. Any DPIs other than these are non-standard DPIs and cause compatibility issues. Even to use to these standard DPIs, the ROM needs to support DPI scaling. Usually stock ROMs don't, while custom ROMs especailly AOSP ROMs like CyanogenMod, AOKP, Paranoid Android etc do. If you don't have the Android sdk installed on your computer, and you need the adb files, then use the attached file. Remember to open command prompt in the extracted zip folder, otherwise it'll return 'adb not found'. CMD needs to be opened in the same directory to be able to detect the adb.exe file. Alternatively, you can open cmd directly in the folder by running 'Start_here.bat'.
or go to recovery an clear dalvik caseh
-fluffy- said:
or go to recovery an clear dalvik caseh
Click to expand...
Click to collapse
That won't help because his stock ROM is incompatible with whatever custom DPI he set. Dalvik cache is only related to apps, and this has nothing to do with apps. Only way to fix this is to change the LCD density back to stock value in build.prop.