Hey Guys, I updated and rooted my phone to 2.3.4 HK...
Anyways, I remember seeing a post about an app that lets you enable the whole screen.
It appears that I have some dead space on the main home screen and I can not place any widgets in it (Its in the bottom)...
Any way I can fix that ? I cant remember the app name for the life of me.
thank you,
Alex
Hey, just use root explorer or shell in order to edit the build.prop in your system folder (or just use CWM and mount your /system folder to your computer). in the build.prop, there is a section that describes the ppi and for some reason, it's set as default to 240. Change it to 275 and it should fix all screen issues.
thanks for your response!! I checked thru Root Explorer, and only found
dpi... not PPI.. is that what you meant? Cause I see that listed as 240.
Also, do I need to reset after the edit?
Thanks a lot!!
The stock launcher seems to be messed up, get a different launcher.
Sent from my MB860 using XDA App
Some people have complained about the resulting effects of changing the build.prop file with this fix. Better to just use a different launcher than stock as was said.
LCD density for root I believe it is the 270 setting you need to select.
Sent from my MB860 using XDA App
Related
I am trying to change the Icon using Ninja Morph. I did exactly what the tread on "how to NinjaMorph" but it does not work.
It seems like I can change the color on the Icon's but it will not let me change out the Icon.
Here is what I did.
I start with New Project
go System than App
than I go the the app that I want to change the Icon
open Res, than Drawable-hdpi, tap the icon I want to change.
Than it opens a folders
I go to the folder with the Icon that I want to replace it with
I click on the Icon that I want use.
After that I exit
than I go to Finish Project,
It as me to confirm Action and couple of other question after.
I reboot the phone and the icon is not change.
What am I missing?
Note: I already did review the tread "how to ninjamorph" and it seem like I am doing everything correctly. The only thing is that the tread says that phone should reboot automatically and mine doesn't. I reboot manually.
When I change the icon color on "edit icon", it works fine.
By the way, I already have busybox installed.
Any input will be greatly appreciated.
What's the app?
Sent from my DROIDX using XDA App
I tried many different app. One of the example is browser.
Sent from my DROIDX
There are some system apps that just wont take. Does the app disappear from the drawer after you edit it? If not then its not taking the change. Be wsue youre changing the png as they normally have a couple pngs that look the same but only one is the icon.
Have you tried manually replacing them?
I tried many different apps. I can edit the icon by changing colors but it will not let me replace icon.
Sent from my DROIDX
Droid-Xer said:
There are some system apps that just wont take. Does the app disappear from the drawer after you edit it? If not then its not taking the change. Be wsue youre changing the png as they normally have a couple pngs that look the same but only one is the icon.
Click to expand...
Click to collapse
When I edit the icon, it would disappear but when I reboot the phone, app will reappear. The only thing is that I have to mount the app in the system. Once I edit the app it was not reinstall with app manager. In other words I have to mount the application directly into the zip folder for the system then reinstall the theme or the rom.
Sent from my DROIDX
I've had some experience with ninja morph not always accepting my changes. After you open your project, use astro to go to sd/androidthemes/workspace. Copy paste the files using astro and then go to ninjamorph and finish the project. Then I use root explorer to paste the app in system/app. Install it (sometimes says fail but it works) then change the permissions and reboot. Just match the permissions list with any other app in system/app as they're all the same. Then reboot. Hope this helps.
Sent from my DROIDX using XDA App
newtsevo said:
I've had some experience with ninja morph not always accepting my changes. After you open your project, use astro to go to sd/androidthemes/workspace. Copy paste the files using astro and then go to ninjamorph and finish the project. Then I use root explorer to paste the app in system/app. Install it (sometimes says fail but it works) then change the permissions and reboot. Just match the permissions list with any other app in system/app as they're all the same. Then reboot. Hope this helps.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
What do you mean by changing the permission? Also, can you be little bit more specific with instructions? I am fairly new to all this.
Also, is there a way I can try to change the icons with my computer? Is there a program or an app out there that works like a Ninja Morph for the desktop?
Sent from my DROIDX
I actually use picsay on the phone to make small edits to the icons. I then pull them from my sd to my pc to convert the jpeg back to png and insert them. But you can also use photoshop to edit images/create your own. Theg have to be the correct size.
I gave up. I just decided to use Better Cut. I never knew/realized you can customize icons on your phone with icon.
Hey Guys,
So if you want to change the LCD density on your Gen8 (tested on the 70, should work on others but changes, as ever, are done at your own risk) without using the LCD Density Changer app then this is how...
I have had to do this as even with the Root +rw on file system, the LCD density changer changes didn't stick (probably OK for the others)
You will need to use the +rw file system mod as documented here:
http://forum.xda-developers.com/showthread.php?t=930197
(thanks Chulri!!)
Anyhoo... to business.
All you need to do for this is to add the following line into /system/build.prop:
ro.sf.lcd_density=XXX
Using rootexplorer was the easiest for me, I copied the file to dropbox, made the change on my computer and then recopied back into /system - note, if you use root explorer, make sure /system is mounted as RW, not RO
You will be able to abd push the file though if you don't want to use dropbox, but I couldn't find my cable when I did this
Reboot.
For some reason after changing lcd density, inputting text in landscape makes the whole textbox fill the screen,
Anyone else have that problem?
oi oi oi whats all this then?!
TheDeadCpu said:
Hasn't this been posted like.. Twice a week or so on XDA?
Click to expand...
Click to collapse
If it has, the I apologise, but I struggled to find it without using the LCD density changer app
Runnning CM7 on a Nook color "OFF THE SD" card and cannot edit my build.prop file. Is this because the system is running off of that card ? I have tried to use the ES File Explorer but cannot "mount" the system when I go in the settings.
I don't want to load this OS in to the internal memory just yet and thought it would be great to make the changes needed for the app store and netflix.
All the threads I see relate to if the OS is running on internal memory not the SD.
Thanks in advance,
housej55
Try root explorer yes it costs money but it is one of the most useful apps you can buy.
Sent from my NookColor using Tapatalk
Hope I can learn something new today, I've seen a lot of threads/posts indicate about changing the build.prop. Why is that? What's that for? and in what case, we need to modify it?
votinh said:
Hope I can learn something new today, I've seen a lot of threads/posts indicate about changing the build.prop. Why is that? What's that for? and in what case, we need to modify it?
Click to expand...
Click to collapse
I edit it to set the LCD density to 187 (defaults to 161); that's pretty much the screen resolution, so if buttons are too small to hit, you can make everything bigger.
Other things in there tell Android what platform is running, so that if an app (market, netflix, etc) cares, it can check.
And you can modify it when running from SD, use Root Explorer, navigate to /system, then tap the "mount R/W" button to enable writing, long-press the file, pick "open in text editor", make your changes, menu/save&exit, reboot.
Sent from my NookColor using XDA Premium App
So guys...after surfing many websites..restoring my nandroid backup for almost 10 times i finally found a safe way to edit the build.prop file.. I don't exactly know if this happens on other android smartphones but whenever you try to edit the build.prop file via any editor on your phone or in my case even via adb i get bootloops...
So i tried remounting system and then unmounting it...i tried many file editors file explorers but every time what i got was a god damn phone stuck at the galaxy s2 logo
And also i would mention that I SEARCHED OVER XDA TOO!!.....the guys had great tools developed but they did not work in my case either.
So no more talkingss.....just how to do it...its rather very simple...you just need an app called Rom Toolbox...its free as well as paid too...download as per your requirement.. AND obviously YOU NEED ROOT.
Well open it(duh) and go into the performance tab and select the build.prop editor...well i will explain you what these values stand for...i am not going to explain each and every value but the ones you would require...leave the unlisted in the comments...
ro.build.date - Change your roms build date
ro.build.description - Your phone's description
ro.build.display.id - Change the build no.(dont use it on custom roms....respect the devs)
ro.build.product - Change your model number....
ro.build.version.release - change the android version(not really actually )
ro.product.brand - Phone's company (Samsung in my case)
ro.product.device - Change the device name
ro.product.model - change the model number
ro.sf.lcd_density - Change the lcd density(dont ask me what it is...google it)\
So guys dont change the values out of range like setting lcd density to 5000...or anything else...and also if anything happens to your phone I AM NOT RESPONSIBLE....
also this is my first thread so guys bear with me....i am a new semi pro java developer i would really like to contribute....
build.prop editing = Root Explorer, long press, open in text editor...
karendar said:
build.prop editing = Root Explorer, long press, open in text editor...
Click to expand...
Click to collapse
+1
Sent from my GT-I9100 using XDA
Or build.prop editor from the market.
Never had any trouble editing the LCD Density with root explorer :/
B3311 said:
Or build.prop editor from the market.
Click to expand...
Click to collapse
I second this.
I had bootloops....
I had bootloops dont you guys read.......!! I used root explorer...and text editor too
May be its the rom thats causing problems......
rohan999 said:
I had bootloops dont you guys read.......!! I used root explorer...and text editor too
May be its the rom thats causing problems......
Click to expand...
Click to collapse
Check for ownership and permissions before restarting. They are probably messed up and are causing bootloops. Or you made a typo somewhere and cause bootloops that way. Root Explorer always works fine for me.
No bootloops here either using root explorer or rom toolbox
Sent from my GT-I9100 using Tapatalk
rohan999 said:
I had bootloops dont you guys read.......!! I used root explorer...and text editor too
May be its the rom thats causing problems......
Click to expand...
Click to collapse
Maybe it's you bro
Sent from my GT-I9100 using xda premium
Please be dont be too hard on him. And i heard someone said it needs to be edited at two places sometimes, but i didnt read the threaded comments till the end. Its lost now. I guess thats that the thread starter means. On some roms, it caused bootloops. Is there any special thing to be taken care of cuz bootloop does happen on certain roms when u edit the build.prop on certain custom roms? On stock deodexed roms, no issues for me
Sent from my GT-I9100 using xda premium
The OP is definitely onto something, because it happened to me.
Specifically, I was trying to edit the DPI setting. Out of the stock ROM, the lcd_density setting was present twice in the file (kind of strange, but oh well - normally it shouldn't cause problems). Edited from 240 to 200 without typos, I'm not allowed to do that due to my line of work , reboot, bam! boot loop.
Replaced the build.prop from backup, edited with "build.prop Editor" from Market - no problems. Really don't see what was the difference, except the duplicated key which was gone after editing with build.prop Editor (probably it does some sort of unique key checking). Oh well, not serious enough to investigate further.
VAXXi said:
The OP is definitely onto something, because it happened to me.
Specifically, I was trying to edit the DPI setting. Out of the stock ROM, the lcd_density setting was present twice in the file (kind of strange, but oh well - normally it shouldn't cause problems). Edited from 240 to 200 without typos, I'm not allowed to do that due to my line of work , reboot, bam! boot loop.
Replaced the build.prop from backup, edited with "build.prop Editor" from Market - no problems. Really don't see what was the difference, except the duplicated key which was gone after editing with build.prop Editor (probably it does some sort of unique key checking). Oh well, not serious enough to investigate further.
Click to expand...
Click to collapse
How did u replace it with ur backup? I normally restore back my nandroid. Is there a much simpler way such as putting it in an update zip or something? Mind to share?
Sent from my GT-I9100 using xda premium
kyleforge said:
Maybe it's you bro
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
bpivk said:
Check for ownership and permissions before restarting. They are probably messed up and are causing bootloops. Or you made a typo somewhere and cause bootloops that way. Root Explorer always works fine for me.
Click to expand...
Click to collapse
override182 said:
Please be dont be too hard on him. And i heard someone said it needs to be edited at two places sometimes, but i didnt read the threaded comments till the end. Its lost now. I guess thats that the thread starter means. On some roms, it caused bootloops. Is there any special thing to be taken care of cuz bootloop does happen on certain roms when u edit the build.prop on certain custom roms? On stock deodexed roms, no issues for me
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
thank you really mate....you are not like the others who just need a reason to insult.....well this is my first thread...so its noobish....but i am a programmer (java) so i will be bringing some good roms later..
override182 said:
How did u replace it with ur backup?
Click to expand...
Click to collapse
I made a copy of /system/build.prop before editing it, of course. After rebooting and getting the bootloop, it's just replacing this file from the backup copy.
I've been using build.prop editor from Nathan Campos, 0 issues so far.
VAXXi said:
I made a copy of /system/build.prop before editing it, of course. After rebooting and getting the bootloop, it's just replacing this file from the backup copy.
Click to expand...
Click to collapse
Im still not clear on this. How did u managed to replace when u cant boot the device and edit it back again to the working build.prop. Did u push back via adb or some update.zip?
Sent from my GT-I9100 using xda premium
The device boots just fine, it just doesn't complete the booting process and remains at the spinning S with blue particles. You can use ADB during that time.
VAXXi said:
The device boots just fine, it just doesn't complete the booting process and remains at the spinning S with blue particles. You can use ADB during that time.
Click to expand...
Click to collapse
Noted. Thx
Sent from my GT-I9100 using xda premium
rohan999 said:
thank you really mate....you are not like the others who just need a reason to insult.....well this is my first thread...so its noobish....but i am a programmer (java) so i will be bringing some good roms later..
Click to expand...
Click to collapse
Most of us didn't insult. Don't jump the gun. Just giving the other side of the coin. Root explorer editing works fine, as others have stated it's possibly a messed up rom giving weird permissions to build.prop. chmod 644 build.prop usually solves the issue though.
I can't speak for everyone, but I wasn't hard on you... Noobs are noobs and I'm fine with that. Most info is readily available on the forums though... Just not necessarily on this forum. XDA is bigger than the sgs2 forums and other communities have very interesting ideas and threads!
***edit*** yeah, after re-reading, noone was harsh in any way. So... yeah!
Sent from my GT-I9100
can someone take the time to school a noob on DPI? I change the dpi n my ro.build and I see no difference... pretty sure I am misunderstanding some part of it.
From my understanding you change the build.prop... save and exit the text editor (must be rooted) and restart the device... I've been using that method on my galaxy nexus and now nexus 7 and it works perfect... think of lowing the dpi as in tricking the OS into thinking you have a bigger screen than you actually have... thus making everything smaller and also triggering tablet mode
No I've been there and done this too. If you open and save the file... then open it back up, the changes are reverted. Yea I was rooted and was using root explorer. Once I flashed a custom rom, I could change it no problem. Maybe something with stock rom or something else not allowing the file to change, even though the folder is R/W and all that.
The file keeps reverting back after you save it.
Sent from my Nexus 7 using xda premium
player911 said:
No I've been there and done this too. If you open and save the file... then open it back up, the changes are reverted. Yea I was rooted and was using root explorer. Once I flashed a custom rom, I could change it no problem. Maybe something with stock rom or something else not allowing the file to change, even though the folder is R/W and all that.
The file keeps reverting back after you save it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
It should work if the folder is R/W and you save and exit. Maybe you should try es Flie Explorer?
I was rushed while posting that and I believe I was completely unclear. I did edit the you Build.prop, I am on a custom rom sgt7 and the dpi and build.prop and DPI was 213 I think maybe 216, I changed it to 180 and I saw no difference at all. this is possibly because there are other modifications to the Rom that aren't dpi dependent or something.