My fonts is too small . How Can I increase the fonts . Thanks
Sent from my Dell Streak using XDA App
if you are using streakdroid, go under spare parts(which can be downloaded even if you are on official rom) and you will see the font size setting. alternatively you can edit your pixel density in build.prop or simply use a pixel density changing app.
I'd been using my Streak for 3 days now. And the fonts are nice and I have no problem with it.
You can always zoom it to fit to you're comfortable view.
joelk said:
My fonts is too small . How Can I increase the fonts . Thanks
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
I use LCD Density Changer from the market, just search LCD density and you will be able to find it. But your phone needs to be rooted and you also need Busybox installed. Using this method, you will be able to "enlarge" your fonts but everytime you restart your phone, you need to set it again.
The other method is use a file manager (i use file expert), mount as read/write and open /system/build.prop and add a line ro.sf.lcd_density=180 (which i find good enough) in the end. The default is 160. You can go 180,200,240. This settings will persist even after restarting.
Or you can try what sharptv has mentioned about spareparts, although i haven't tried that method.
I found LCDDensitiy in the market , know my fonts is large. Its so pleasure. Thanks. Spare parts dissmiss the fonts change as soon as I go out from him . So nothing done
Sent from my Dell Streak using XDA App
Its turn out that Lcd density not good enough. I install the file expert change the mount to rewrite and add the line in the build file. , but he won't let me save it or I cannot see The Change I made To the file.
Sent from my Dell Streak using XDA App
I manage to add the line with root explorer, thanks
Sent from my Dell Streak using XDA App
Yayyyyyyy, well pleased. Must have set the density too high when I flashed my ROM. Was dreading having to re-flash, with the attendant reset and month getting the phone back to how I like it. Simple line edit, and voilla, no more magnifying glass needed. Thanks folks, made my day.
In my case, the lcd_density line was already there, (set at 140), which threw me because I simply scrolled to the bottom and added the line, which, of course didn't work 'cos the line already appeared.
If you find that this technique doesn't work for you, search for the file for the offending line, and simply edit the number (mine now at 160, and perfect)
Sent from my Dell Streak, streakdroid 1.9, Swype keyboard, using XDA Premium App
You can always reflash a rom on top of your old one without changing any of your setup. Just flash as you normally would, but don't factory reset. So you can change your setup options for the rom, then just re-flash it. That even works for upgrading a rom to a newer version, unless the chef recommends against it...
Of course always Nandroid backup first!
Sent from my Dell Streak using Tapatalk
slaydog said:
You can always reflash a rom on top of your old one without changing any of your setup. Just flash as you normally would, but don't factory reset. So you can change your setup options for the rom, then just re-flash it. That even works for upgrading a rom to a newer version, unless the chef recommends against it...
Of course always Nandroid backup first!
. . .
Click to expand...
Click to collapse
Custom ROMs applied as a .zip file can be flashed over your current ROM without loss of settings and apps. Depending what ROM is on your phone and what apps you have installed this may cause problems. Most devs recommend a factory reset to make sure that this does not happen. Usually it is safe to reflash StreakDroid if you want different options. For best results with a custom ROM you will usually get better results if you flash the stock ROM that they base the custom ROM on first, so that you have the correct system files that match the custom ROM, since all of these are not part of the .zip file that contains the custom ROM.
When installing a stock ROM from recovery it is the same effect as a factory reset. You will have to redo your settings and reinstall your apps.
So the advice to flash over the ROM only works if the problem you are having isn't due to mis-matched baseband and if you are talking about a custom ROM.
Related
hi
as the Title says... don't do it...
i've done it... now black Screen...
But no change to edit it back with droidexplorer or adb shell...
file is emtpy...
i'm running with Froyostone V1 maybe someone can send me the build.prop file of this build...
i don't want to restart from scratch...
thx
futureshock said:
hi
as the Title says... don't do it...
i've done it... now black Screen...
But no change to edit it back with droidexplorer or adb shell...
file is emtpy...
i'm running with Froyostone V1 maybe someone can send me the build.prop file of this build...
i don't want to restart from scratch...
thx
Click to expand...
Click to collapse
The quickest way would be to load up another clean version changing the original to froyo boot it up & go to astro copy the build from system to SD or to the froyo version & restart then delete new version and paste the build into the original froyo & reboot
so i got my froyostone back to working
have pulled the build.prop from my shubcraft build... and pushed it to the froyostone build!!
hopefully the trick will work without that problem on my hopefully soon arriving android tablet
Next time, try backing up the android folder on ur SD card before changing anything.. that way a quick format and a trip to ur computer will get ur phone working again..
Sent from my HTC HD2 using XDA App
futureshock said:
so i got my froyostone back to working
have pulled the build.prop from my shubcraft build... and pushed it to the froyostone build!!
hopefully the trick will work without that problem on my hopefully soon arriving android tablet
Click to expand...
Click to collapse
Can you share this file here? i got the same problem that many applications can't work with full screen, and i didn't backup this file...
thx~
Sorry for my Englisch.
Problems with the screen in fullscreen games.It is easy to change it.
Open the file with a text editor Build.Prop and edit the line of "ro.sf.lcd_density = 220" to "ro.sf.lcd_density = 240"
Followed the instructions and did this mod.
I sorta of like it. Didn't encounter any problems at all. It's hard to tell the difference. Some apps will support it, Sense UI does not.
The bigger question is. Does this impact battery life. I am still testing this..so right now that's debatable.
I set dpi to 192 and love it. Most apps show more info on screen, a few games are not clever enough.
After using WinMo for 2 years, I'm used to high precision "touching" :-D
A tip: download Spare Parts and use it to turn off compatibility mode.
i just read http://forum.xda-developers.com/showthread.php?t=765639
will it work with our hd2
vua777 said:
i just read http://forum.xda-developers.com/showthread.php?t=765639
will it work with our hd2
Click to expand...
Click to collapse
Not exactly.
The app works but doesn't really make any difference to build.prop file nor does reboot the device.
Your can manually make the changes.
I set it to 200 and I use adw launcher to make usage of the extra space.
Black screen from changing build.prop
So i really wish I found this thread before i tried to change anything. So i also have the black screen when loading android after changing build.prop file, I did copy the file before I changed it. Now i just dont know how to get into the system folder to change it back because when i load android its all black. Can anybody help me here?
Howdy all,
I updated my phone to 2.2.2 with help from Broken's and Krad's posts in the "Dell Streak Froyo 2.2.2 Build" and "Root AWS Dell Streak" threads.
It was wonderful the first day but now I've done something and keep experiencing random process crashes. Mostly with the com.dell.launcher.
I was just wondering if anyone else is seeing this or if I should wipe and reinstall.
Baseband: GAUSB1A132211-us
Kernel: 2.6.32.9-perf
Oem: GAUSB1A134100
Build: 14917
I did change the following as per these instructions.
Just noticed that by default, the Stock 341 had hardware acceleration for graphic disabled. Meaning it uses CPU instead of GPU to render graphic (something like that from reading online).
Here's the simple mod/fix:
1. Phone must be rooted, use Root Explorer (paid app)
2. goto /system, change mounted mode to R/W (read/write) if it is R/O (read/only)
3. edit build.prop file, change the line
FROM - debug.sf.hw=0
TO - debug.sf.hw=1
Reboot your phone. Should speed up the graphics... Tested and works for me
** This is a pretty common tweak in custom ROM and definitely not my discovery. Too common now, don't know who to credit.
Were the crashes before or after you made the changes?
Sent from my Dell Streak using XDA Premium App
eowyn0821 said:
Were the crashes before or after you made the changes?
Sent from my Dell Streak using XDA Premium App
Click to expand...
Click to collapse
I think after.
I am seeing a strange screen that's like the in call screen but there is no person. It just has the interface up.
It goes away if I hit the home button, but it's weirdness.
zero issues here. Did you load the way i said? or did you force via fastboot method?
If it is causing crashes edit it back to 0
Sent from my Dell Streak using XDA Premium App
Krad, I used fastboot method, no matter how I tried adb would not allow me to, woukd always say not found, permission denied, even terminal emulator gives the same message that is why I think it would b ev better if someone would post the command sequence they on adb or t.e. for us to follow also. BTW I woukd love to have your gingerkrad on my streak unfortunately it doesn't work on mine.
Sent from my Dell Streak using XDA Premium App
Krad said:
zero issues here. Did you load the way i said? or did you force via fastboot method?
Click to expand...
Click to collapse
I did the fastboot with the wrong files at first. That got me to 2.2.1 and then I did it your way after I got the md5 thing to run and now I'm on 2.2.2.
htcjikelly said:
I did the fastboot with the wrong files at first. That got me to 2.2.1 and then I did it your way after I got the md5 thing to run and now I'm on 2.2.2.[/QUOTE
Could you post your procedure? Coz I couldn't get it to.work on two computers, both saying not found, permission denied, even tried doing on terminal emulator. I was able to make 2 nandroid backups of 322/341 2.2.2, however when I tried to do a nandroid restore it says md5 mismatch.
Sent from my Dell Streak using XDA Premium App
Click to expand...
Click to collapse
Some of it is in broken's thread. Like you can follow my disgust and failures in there. ;-)
But, I need to compile out all because they leave out the actual code for doing it. I had to dog around in a bunch of forums to find all the code I needed.
Clearly I bearly have a grip on how this OS works. Wish it were dos based.
Anyway,
The process com.google.gapps crashed. What does that prices do?
Sent from my Dell Streak using XDA App
Htcjikelly, my sw spec is the same as yours and I have the build.prop hw = 1 edit too. No problem on my end and I have been a happy camper for 3 days now. I have the White Streak. For launcher, I am using adw launcher ex instead of Dell Stage.
Sent from my Dell Streak using Tapatalk
Thanks! I didnt notice any improvement in speed overall (games / ui).
but as it didnt brake anything neither its good to know that hardware acceleration is activated.
Maybe ill run Quadrant later and post results
Hi Everyone,
I am in need to know how to change the default homepage of litening rom as it gos to the very first page when i push the home button.
I would like to go to the middle page when i push it which requires i edit a line somewhere and put the number 3 in it.
Could anyone help me and the many others who dont know.
Thank you.
rom of Cognition provide this function base on official launcher, but i prefer 3rd party launchers such as adw launcher, zeam launcher and etc. all of which are configable.
Me too
Hey guys,
I wan't another screen to be default, so brought if I press the home button, too. I managed to change it on stock Samsung ROM with this method
http://forum.xda-developers.com/showthread.php?t=1096521
however there is no default.prop in system directory in Litening ROM! (I use 1.5).
So i wrote this ro.csc.homescreen.defaultscreen=4 into the "build.prop" file of the system folder -> does not work :'(
Then I have written it to the "default.prop" file in the / folder (so nothing ) -> does not work either : Seems to be that the Litening ROM overwrites this file every restart!
Please someone help me
I am in the exact same boat as you now. It does get annoying always going to the first page.
So not 1 person knows how to change it?
Easy way is to use Launcherpro, you an choose the amount of screens and which to use as default.
Put the below string in default.prop file. Replace 3 with whichever
screen as default.
ro.csc.homescreen.defaultscreen=3
This will set the homescreen at start up, but not working on pressing home screen button.
Sent from my GT-I9100 using XDA Premium App
kirdroid said:
Put the below string in default.prop file. Replace 3 with whichever
screen as default.
ro.csc.homescreen.defaultscreen=3
This will set the homescreen at start up, but not working on pressing home screen button.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
I dont get why it doesnt work when you press the homescreen button? LiteRom definately needs the feature to allow you to change it.
WhiteXR said:
I dont get why it doesnt work when you press the homescreen button? LiteRom definately needs the feature to allow you to change it.
Click to expand...
Click to collapse
This feature does not depend of LiteRom(only if he finds a way to modify the rom somehow)
This file witch we were modifying up to now is missing in the latest rom's so another way must be found.
Maybe somebody with more skills can help us of corse the suggestions of changing the launcher are not solving our problem.
we need solutions for touchwiz.
this makes me sad
I am very new to android and rooting and roms, etc. I finally figured out how to flash a rom so i decided to go with lightening 6.1. Its really frustrating when small things like these don't work.
I really hope someone can come up with a fix. I've also noticed that adfree android app also doesn't work with this rom and thats such a bummer. I dont want to go back to my stock rom...
chmsalman said:
I am very new to android and rooting and roms, etc. I finally figured out how to flash a rom so i decided to go with lightening 6.1. Its really frustrating when small things like these don't work.
I really hope someone can come up with a fix. I've also noticed that adfree android app also doesn't work with this rom and thats such a bummer. I dont want to go back to my stock rom...
Click to expand...
Click to collapse
and just what is it that doesnt work for you?
i tried litening 6 then cyanogen and returned running to litening 6.1 i should had never left it lol
Everything works ok for me.
So I will just say upfront that after constantly keeping up to date with the current ROM I'm using, my htc one freezes during installs of rom, tweaks, themes, etc. This freeze is apparently to do with Aroma and our touch screen.
The way around it (somewhat) is to pre-modify the config file in note pad, line after line and it's time consuming. Pre-modifying the config allows us to simply hit next repeatedly to quickly get to the installation process because all of the options are already set.
I created an app called 'Thaw It' to help create a config instead of manually editing it. It runs in Android. It's an app that reads the config, displays checkboxes and descriptions, allowing the user to check install options, and then finally outputs a new config file for Aroma.
Can I get some replies on whether this community would be interested in using my app? If no one replies I will assume everyone is happy with their work arounds (whether that be rebooting phone and retrying, or hand modifying the config with notepad).
Not sure if this thread is in the right place. It's purpose is to gauge the need for my app....
You can use the volume up/down keys to change the currently selected item and then use the Power button to change that item (click a button, toggle a checkbox, etc) to completely avoid having to use the touchscreen. It's my understanding this fixes the Aroma lockups with the HTC One. That's how I've flashed the last three ROMs and they've all finished fine, though Aroma still locks up at the end when you select Next to reboot. At that point you can just hold down the power button until the phone shuts off and turn it back on and you're good to go.
Sure, I would love to use your app.
Thnx
Sent from my Nexus 10 using XDA Premium HD app
Yes I knew about the power and volume buttons being an option.
Here is the only bad thing about the app. It extracts the config file from the zip and reads it, but does not rebuild it into the zip when it's done.
So the last step is take the new generated config file, and drag it back into the zip to replace the original.
The reason I don't automate this is because it would take a very long time to unpack the entire zip, and repack it programmatically using the built in libraries.
still usable?
AROMA works fine with Clockworkmod Touch Recovery http://forum.xda-developers.com/showthread.php?t=2173863
However, if you already have TWP backups, they won't work with the above recovery.
I've never had a problem using touch, it froze on me while using vol/power buttons.
Sent from my HTC One using xda app-developers app
Blackbolt: I think it's an excellent idea (and if it could remember that I always disable a set of apps and all keyboards, so much the better)
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 5.6
Bulletproof 1.10
Wouldn't it be better to try and fix aroma with the aroma dev instead of creating an app to work around a bug?
godutch said:
Wouldn't it be better to try and fix aroma with the aroma dev instead of creating an app to work around a bug?
Click to expand...
Click to collapse
Aroma is constantly being updated but general release of working builds may take a while. Amarullz knows what he is doing except he doesn't have the One or s4. OP is just offering a work around for now and for current use.
Sent from my HTC One using Tapatalk 2
Aroma freezes a lot in CWM touch for me,aint a huge deal tho i just reboot and reflash
Sent from my HTC One using xda app-developers app
Amarullz manage to fix Aroma already for HTC One. It's just he still has some minor things to be tweaked before he officially releases it. Although he already released the beta version to the public.
Thela7 said:
AROMA works fine with Clockworkmod Touch Recovery http://forum.xda-developers.com/showthread.php?t=2173863
However, if you already have TWP backups, they won't work with the above recovery.
Click to expand...
Click to collapse
I use TWRP. I guess it's a twrp/aroma specific issue?
I like to update CM every night with CyanDelta, but one drawback with this phone is that every time I do, it resets to the default DPI. The default DPI, 460, is way too big for me, and I like to have it around 360. Is there any way I can change this every time I flash without having to edit the build.prop each time? Thanks!
I'm kind of curious about this too. although a quick search tells me that it basically isnt possible unless you either create a zip to change it and flash that every time you flash a new nightly, or set an app to auto start when you boot the phone to change it. You would have to reboot once again to get the change.
teeg07 said:
I'm kind of curious about this too. although a quick search tells me that it basically isnt possible unless you either create a zip to change it and flash that every time you flash a new nightly, or set an app to auto start when you boot the phone to change it. You would have to reboot once again to get the change.
Click to expand...
Click to collapse
I've thought about making a zip to flash it, but doesn't build.prop change with every nightly? I wonder if there is a way to make a script that will just find and change the DPI in build.prop.
any updates on this? I have been struggling with this problem for years. I've also tried different software to change it but it does often break my play store for some reason so I do it manually every time.
i would like to know if that's possible, too...
it should be, despite the build.prop changing with every build, i assume(!) the lines (read: line numbers) remain the same... so, one could write a script, that changes EXACTLY the necessary line ("ro.sf.lcd_density=[whatever value is preferred]", i for one change it to 400 instead of 480), while leaving the rest untouched... and even if the line numbers change, could one find the line and replace it?
correct me if i'm wrong, please
If i knew how to write scripts for android (or better TWRP for that matter), i'd do it myself, but i have no idea...
I don't have a g2 but I was googling for this exact thing and turned up here... There has to be a way to create a .zip to flash with updates... i just don't know how
upon further googling i turned up this -
http://forum.xda-developers.com/showthread.php?t=2405288
here http://forum.xda-developers.com/showthread.php?t=2612552
Sent from my LG-D802 using xda app-developers app