Database Develop

Change Screen Resolution on legend ???

is it possible to change the resolution of htc legend..........i tried lcd density but no use ...i am using azure cyanogen mod 6.....
i tried to edit the build pro..but no use
some one help me.......
Change Your Screen Resolution on HTC Evo 4g

I have successfully done this now. Remember that we don't have root in the same way that the EVO 4G does.
So:
Using any file manager that can read the / partition of your phone find and copy "/system/build.prop" onto your SD card.
Now copy the file to your desktop, and take a backup of that file too.
Open notepad and make sure word wrap is on, then open build.prop in notepad
Edit the required value (I chose 120), save and copy the file to your ADB/tools directory
Reboot your phone into clockworkMOD recovery, and connect your phone to the PC. Also go into the partitions menu of ClockworkMOD and click "mount system"
Open up ADB, and run "adb devices" to make sure the phone is connected and everything is working
Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
Then reboot your phone.
Let me know if this helps
Also, for other readers:
Make sure you read the post that is linked to in the above post, otherwise my instructions might not make sense... I might edit it later when I have time

@TheGrammarFreak
What is the resoultion of your screen now?

qzem said:
@TheGrammarFreak
What is the resoultion of your screen now?
Click to expand...
Click to collapse
I dunno how I'd work it out, sorry.

Ah...
I think I've found the first of many flaws with this, and it was mentioned in the EVO 4G post. Some apps ignore this and use the old resolution, and thus don't fill the screen (see attachment)
As you can the the status bar goes a lot wider than the app. The status bar is the full width of the screen.
Other problems arise too, a reinstall of the app doesn't help, and some apps just end up completely screwed...

qzem said:
@TheGrammarFreak
What is the resoultion of your screen now?
Click to expand...
Click to collapse
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.

grandioso said:
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
Click to expand...
Click to collapse
Cool, thanks grandioso
On a slightly different note I've found that changing the value to 130, and using the 5 icon rows feature of launcher pro, is quite nice.

grandioso said:
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
Click to expand...
Click to collapse
Thanks for clearing that .

There are some problems, but if you want to try it out, you can flash the update.zip I've just made.
160lcd.zip takes you back to default and 120lcd.zip makes your screen resolution higher.

@Briix
Can you make update for 130, like TheGrammarFreak suggested

I'd make one but I'm currently struggling to sign my .zip
EDIT:
Done it, just testing then I'll upload. I also notice that ROM Manager is one of the apps that ends up being screwed by this mod...
EDIT 2:
Wow, lots of edits. Anyhoo, 130lcd right here:

really nice

TheGrammarFreak said:
I have successfully done this now. Remember that we don't have root in the same way that the EVO 4G does.
So:
Using any file manager that can read the / partition of your phone find and copy "/system/build.prop" onto your SD card.
Now copy the file to your desktop, and take a backup of that file too.
Open notepad and make sure word wrap is on, then open build.prop in notepad
Edit the required value (I chose 120), save and copy the file to your ADB/tools directory
Reboot your phone into clockworkMOD recovery, and connect your phone to the PC. Also go into the partitions menu of ClockworkMOD and click "mount system"
Open up ADB, and run "adb devices" to make sure the phone is connected and everything is working
Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
Then reboot your phone.
Let me know if this helps
Also, for other readers:
Make sure you read the post that is linked to in the above post, otherwise my instructions might not make sense... I might edit it later when I have time
Click to expand...
Click to collapse
thanks man its working...........

Has anyone tried GrammarFreak's zip ?
Are there any problems with it ? Is it worth the effort ?
Do I have to wipe for this to work ?

Explicitly my zip? Or any of the zip's in this thread?
No wipe is needed.
Also, this method is inherently flawed. Some apps just don't use the edited resolution. Unless a way can be found to force these apps to scale up then there will always be ugly moments.
One of the things that I've found to not work is the HTC-IME mod. So is it worth it? That for you to decide... Lol
Sent from my Legend using XDA App

I mean yours or Briix' - are there any others ?
I don't want to edit the file manually if I don't have to

grandioso said:
Has anyone tried GrammarFreak's zip ?
Are there any problems with it ? Is it worth the effort ?
Do I have to wipe for this to work ?
Click to expand...
Click to collapse
Yup.. Tried.. working like a charm..
-------------------------------------------------------------------
Could you make a 140 and a 110 .. Just to try and see the result!?
I'll gladly test them both..

whitetigerdk said:
Yup.. Tried.. working like a charm..
-------------------------------------------------------------------
Could you make a 140 and a 110 .. Just to try and see the result!?
I'll gladly test them both..
Click to expand...
Click to collapse
I'd love to, but I can't at the moment, I'm at school and didn't bring my laptop. Unless someone beats me to it I'll make one in about an hour and a half; when I'm home.
I did try 140 myself but I didn't think it was worth it. I use 5 icon rows in launcher pro and the widgets started overlapping again. Like they did in the default resolution.
Sent from my Legend using XDA App

I'll wait..
Would be great though if WF & Clock Widget (The Sense look Clock) would adapt to new screen and fill it out..
Totally sweet indeed..

Yeah, if I knew more about android I'd look into forcing apps to scale up. I'm not sure if it's even possible, but hey.
Sent from my Legend using XDA App

Help me revert Moboot after installing ClassicNerd v4.04.4

I decided to give the new ClassicNerd ROM a try the other night, and while I didn't enjoy the ROM that much, I decided to revert back to one of my backups.
Unfortunately, Moboot still has ClassicNerd's skin and it looks utterly disgusting and I would like to change it back to the plain old black Moboot screen.
Any ideas on how I would accomplish this?
Thank you.
Edit: I was able to install this Moboot Theme successfully and everything seems to be working. The problem I have now is that "Classicnerd" still shows up in Moboot's options. The problem is that when you select it, it goes through the boot animation but doesn't do anything, because I assume there's nothing for it to boot to.
Any idea how to remove that option from showing up in Moboot?
Edit2: Alright. I've figured out how to remove the Classicnerd option from showing up in Moboot. There were a few files inside of ../boot/. One of which was "uImage.Classicnerd" and the other was something like "moboot.classicnerd". Anyway, I deleted those two files and Moboot no longer shows the Classicnerd option in its boot menu.
HOWEVER..I now have another problem: CyanogenMod is no longer #1 on the list, so Moboot defaults to WebOS. Is there any way to change that? I shall do more research and update if I find anything.
Edit3: Figured out how to set the default boot option in Moboot.
"Open the Terminal Emulator and type:
su
mount -o remount,rw /boot"
Then I went into /boot and opened "moboot.default" in ES Note Editor and I replaced "WebOS" with "CyanogenMod". Make sure you put an enter at the end, because for whatever reason it wouldn't save it without the enter at the end.
--[Solved]--

First of all glad your using my theme
If you want to remove the classicnerd option from the menu then do :
Open terminal and type : rm /boot/uImage.ClassicNerd
Or if you have root browser go to /boot/ mount as R/W and delete the uimage.ClassicNerd

I appreciate the help.
One last question I have yet to figure out: How do I actually change the ORDER in which the items on Moboot show up? I've figured out how to change which one is default, but how do I change the actual ORDER of how they show up on Moboot?
Thanks for the reply.

jowyboy said:
I appreciate the help.
One last question I have yet to figure out: How do I actually change the ORDER in which the items on Moboot show up? I've figured out how to change which one is default, but how do I change the actual ORDER of how they show up on Moboot?
Thanks for the reply.
Click to expand...
Click to collapse
I'm not sure this is possible as there's no file (that i know of) that has order preferences for Moboot... Although i didn't really figure out how Moboot does that yet

jowyboy said:
I decided to give the new ClassicNerd ROM a try the other night, and while I didn't enjoy the ROM that much, I decided to revert back to one of my backups.
Unfortunately, Moboot still has ClassicNerd's skin and it looks utterly disgusting and I would like to change it back to the plain old black Moboot screen.
Any ideas on how I would accomplish this?
Thank you.
Edit: I was able to install this Moboot Theme successfully and everything seems to be working. The problem I have now is that "Classicnerd" still shows up in Moboot's options. The problem is that when you select it, it goes through the boot animation but doesn't do anything, because I assume there's nothing for it to boot to.
Any idea how to remove that option from showing up in Moboot?
Edit2: Alright. I've figured out how to remove the Classicnerd option from showing up in Moboot. There were a few files inside of ../boot/. One of which was "uImage.Classicnerd" and the other was something like "moboot.classicnerd". Anyway, I deleted those two files and Moboot no longer shows the Classicnerd option in its boot menu.
HOWEVER..I now have another problem: CyanogenMod is no longer #1 on the list, so Moboot defaults to WebOS. Is there any way to change that? I shall do more research and update if I find anything.
Edit3: Figured out how to set the default boot option in Moboot.
"Open the Terminal Emulator and type:
su
mount -o remount,rw /boot"
Then I went into /boot and opened "moboot.default" in ES Note Editor and I replaced "WebOS" with "CyanogenMod". Make sure you put an enter at the end, because for whatever reason it wouldn't save it without the enter at the end.
--[Solved]--
Click to expand...
Click to collapse
I like your post.
Just sayin.
Sent from my SPH-D700 using XDA

TedSamaha said:
I'm not sure this is possible as there's no file (that i know of) that has order preferences for Moboot... Although i didn't really figure out how Moboot does that yet
Click to expand...
Click to collapse
Meh. It's not a big deal; it would just be nice to order it however I please. My CyanogenMod Nightly installation is now set as default, so meh.
gregory15 said:
I like your post.
Just sayin.
Click to expand...
Click to collapse
Thanks, dude!

Ok, now the problem that I've been having is that for some reason neither root explorer nor ES explorer are letting me mount as R/W, when I try to check the Root option on ES Explorer it automatically says that it was denied superuser, I even changed superuser settings to automatically accept...
what to do here?

bassrebel said:
Ok, now the problem that I've been having is that for some reason neither root explorer nor ES explorer are letting me mount as R/W, when I try to check the Root option on ES Explorer it automatically says that it was denied superuser, I even changed superuser settings to automatically accept...
what to do here?
Click to expand...
Click to collapse
You tried updating binaries?
Sent from my cm_tenderloin using Tapatalk 2

if by updating binaries u mean updating SU then I tried but it didn't let me because it says I need root... WTF? I tried checking under options -> developers options and put it to root abd+apps and still nothing is happening... :/

Open the SuperUser app itself, and check your settings there. Something might be changed.
Me, I use the Prompt option, and every once in a while I have to remove an app from the accepted list and let it load itself up and prompt me again. Maybe that'll help you (I hope).

THANK YOU!
jowyboy said:
I decided to give the new ClassicNerd ROM a try the other night, and while I didn't enjoy the ROM that much, I decided to revert back to one of my backups...
--[Solved]--
Click to expand...
Click to collapse
Wow. Dude. Where do I start?! Thank you!!! This has plagued my kids tablet for months. Finally, this evening, I thought I would try and do something about it. This boot loader has been causing this tablet to force close after boot for months if it was left to boot up on the 'default' Classic Nerd ROM option (after I flashed another ROM).
Finally fixed.

moboot questions

Could someone do a write up on editing moboot and then have it stickied? Because in searching, I can only find instructions for cm7. I'd like to know how to delete and edit entries as well as changing the theme.
Thanks.

carguy303 said:
Could someone do a write up on editing moboot and then have it stickied? Because in searching, I can only find instructions for cm7. I'd like to know how to delete and edit entries as well as changing the theme.
Thanks.
Click to expand...
Click to collapse
I suggest you read this thread which IS stickied and has all the answers you're after and more.
http://forum.xda-developers.com/showthread.php?t=1438158

I see themeing in video how tos. But not editing entries.

I just did this. This was the first result on Google for "edit moboot entries."
http://rootzwiki.com/topic/17104-how-to-edit-moboot-default-boot-from-android/
And this.
http://forum.xda-developers.com/showthread.php?t=1561030
And at sstar's above link, open "Boot to WebOS by Default after installing CyanogenMod Android." And "Removing uImages."

carguy303 said:
Could someone do a write up on editing moboot and then have it stickied? Because in searching, I can only find instructions for cm7. I'd like to know how to delete and edit entries as well as changing the theme.
Thanks.
Click to expand...
Click to collapse
To edit the order of booting in moboot, download, in webOs and preware, Cyboot. It lets you choose the order of booting and also set the time to first boot. As far as theming, you'll have to search. I've seen some threads about that, but can't remember the how to. If not here, you might want to try the webOS nation forum.

You can change your default moboot using root explorer and changing moboot files in systems root.

[Q] Changing boot priority - moboot.default will not change OS ?

Just upgraded to Moboot 038 from 035 [currently using Schitzoid CM10 ROM],.
My TP defaults to WebOS on every boot !
The Moboot.default in the Boot folder is set to AOKP, [as it was prior to upgrade],. but it still persists in booting WebOS !
Anyone any ideas,.. as I cannot find a resolve anywhere
Cheers,..

dougs99 said:
Just upgraded to Moboot 038 from 035 [currently using Schitzoid CM10 ROM],.
My TP defaults to WebOS on every boot !
The Moboot.default in the Boot folder is set to AOKP, [as it was prior to upgrade],. but it still persists in booting WebOS !
Anyone any ideas,.. as I cannot find a resolve anywhere
Cheers,..
Click to expand...
Click to collapse
I thought the schitzoid ulmage was named CyanogenMod but a could be wrong . Can you post a screenshot of your boot folder.

View attachment 1756948
Here's a screen shot,.. hope this helps !

sstar said:
I thought the schitzoid ulmage was named CyanogenMod but a could be wrong . Can you post a screenshot of your boot folder.
Click to expand...
Click to collapse
Selecting AOKP manually in Moboot,. runs Schitzoid !,.. I have Cyanogenmod as an option,. but this was for a previous ROM
Screenshot below >>

That's strange as I have just booted into my recovery of skitzoid and below is my screenshot and I don't have AOKP . Try setting moboot default to CyanogenMod and see what result that gives you.
PS what Rom did you have before?
Sent from my skz_tenderloin using Tapatalk 2

sstar said:
That's strange as I have just booted into my recovery of skitzoid and below is my screenshot and I don't have AOKP . Try setting moboot default to CyanogenMod and see what result that gives you.
PS what Rom did you have before?
Sent from my skz_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Changed to CyanogenMod,.. and it still selects WebOS as default boot !,.. my previous ROM was AOKP's,. hence its retained this,. but it has been successully using this for a couple of months or so,.. i'm baffled :crying:
I have now deleted AOKP UImage from boot folder,.. made sure CyanogenMod is set as default,.. but Moboot still selects WebOS as default,. AARRGGGHHH !!

That makes 2 of us .

sstar said:
That makes 2 of us .
Click to expand...
Click to collapse
Thanks anyway,. hope someone else can advise,.. ??

dougs99 said:
Thanks anyway,. hope someone else can advise,.. ??
Click to expand...
Click to collapse
OK here is my final idea in webOS with preware DL an app called Cyboot run it and select Android as your default boot then save and exit.
You've nothing to lose, its what I first used before I found out about editing the boot folder.
Good luck and please let us know what happens.
Edit Just checking but the permissions for moboot default s/b rw-r--r-- just in case it somehow changed.

sstar said:
OK here is my final idea in webOS with preware DL an app called Cyboot run it and select Android as your default boot then save and exit.
You've nothing to lose, its what I first used before I found out about editing the boot folder.
Good luck and please let us know what happens.
Edit Just checking but the permissions for moboot default s/b rw-r--r-- just in case it somehow changed.
Click to expand...
Click to collapse
Went down the Cyboot route,. and hey,.. it works !!,. now defaulting to CM ,. Much appreciated for your help with this,. as I was well and trulyy stumped
cheers mate,.rgds, Dougie:good::good:
ps,. permissionswere set ok

Phone turns off after boot screen

So I was trying to follow a tutorial for installing Japanese apps on a non-JP phone, but after I modified the values and rebooted the system, the phone started turning off after the boot screen. I still have access to recovery and download mode. Any idea of what could have gone wrong? Thank you in advance.
Since I can't post images or outside links, I'll paste the text up to what I did here:
1. Run RootExplorer and navigate to /system. Click the button to remount as r+w.
2. Long press on build.prop and select Copy. Paste it into the same folder or another folder to make a backup. You DO NOT want to lose this.
3. Long press on build.prop and select Edit in Text Editor.
4. Find and modify the following values (jacked from an NTT DoCoMo SHARP SH12C). Be aware they may not be grouped logically, so search the whole file if need bed. If a value doesn't exist, you will need to create it:
ro.build.id=S7140
ro.build.display.id=01.01.02
ro.build.version.incremental=01.01.01
ro.build.version.release=2.3.3
ro.product.model=SH-12C
ro.product.brand=DOCOMO
ro.product.name=SH12C
ro.product.device=SH12C
ro.product.board=SH12C
ro.product.manufacturer=SHARP
ro.product.locale.language=ja
ro.product.locale.region=JP
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.sh_build.id=S7301
ro.sh_build.version.incremental=01.01.02
ro.build.product=SH12C
ro.build.description=SH12C-user 2.3.3 S7140 01.01.01 release-keys
ro.build.fingerprint=DOCOMO/SH12C/SH12C:2.3.3/S7140/01.01.01:user/release-keys
5. Close Root Explorer.
6. Open System->Applications->All and scroll down to Market. Click Force Close and Clear Cache.
7. Power off your phone. You absolutely must reboot your phone in order to populate the new values we just made in the RAM.​

bunnyrice said:
So I was trying to follow a tutorial for installing Japanese apps on a non-JP phone, but after I modified the values and rebooted the system, the phone started turning off after the boot screen. I still have access to recovery and download mode. Any idea of what could have gone wrong? Thank you in advance.
Since I can't post images or outside links, I'll paste the text up to what I did here:
1. Run RootExplorer and navigate to /system. Click the button to remount as r+w.
2. Long press on build.prop and select Copy. Paste it into the same folder or another folder to make a backup. You DO NOT want to lose this.
3. Long press on build.prop and select Edit in Text Editor.
4. Find and modify the following values (jacked from an NTT DoCoMo SHARP SH12C). Be aware they may not be grouped logically, so search the whole file if need bed. If a value doesn't exist, you will need to create it:
ro.build.id=S7140
ro.build.display.id=01.01.02
ro.build.version.incremental=01.01.01
ro.build.version.release=2.3.3
ro.product.model=SH-12C
ro.product.brand=DOCOMO
ro.product.name=SH12C
ro.product.device=SH12C
ro.product.board=SH12C
ro.product.manufacturer=SHARP
ro.product.locale.language=ja
ro.product.locale.region=JP
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.sh_build.id=S7301
ro.sh_build.version.incremental=01.01.02
ro.build.product=SH12C
ro.build.description=SH12C-user 2.3.3 S7140 01.01.01 release-keys
ro.build.fingerprint=DOCOMO/SH12C/SH12C:2.3.3/S7140/01.01.01:user/release-keys
5. Close Root Explorer.
6. Open System->Applications->All and scroll down to Market. Click Force Close and Clear Cache.
7. Power off your phone. You absolutely must reboot your phone in order to populate the new values we just made in the RAM.​
Click to expand...
Click to collapse
You just added those lines or you replace its values on already existing?

shut_down said:
You just added those lines or you replace its values on already existing?
Click to expand...
Click to collapse
I replaced the ones that already existed and added the rest. I think the ones that had to be added were
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.sh_build.id=S7301
ro.sh_build.version.incremental=01.01.02

bunnyrice said:
I replaced the ones that already existed and added the rest. I think the ones that had to be added were
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.sh_build.id=S7301
ro.sh_build.version.incremental=01.01.02
Click to expand...
Click to collapse
We use ro.build.id, not ro.sh_build.id. Try to remove that sh_.
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.build.id=S7301
ro.build.version.incremental=01.01.02

shut_down said:
We use ro.build.id, not ro.sh_build.id. Try to remove that sh_.
ro.mtp.manufacturer=NTT DOCOMO, Inc.
ro.build.id=S7301
ro.build.version.incremental=01.01.02
Click to expand...
Click to collapse
Thank you very much. Can I edit it through my computer, or will I have to do a reset?

bunnyrice said:
Thank you very much. Can I edit it through my computer, or will I have to do a reset?
Click to expand...
Click to collapse
You can edit, and put it back in system, where it was. But permissions must be 644, you will get a bootloop if it is not like that.

shut_down said:
You can edit, and put it back in system, where it was. But permissions must be 644, you will get a bootloop if it is not like that.
Click to expand...
Click to collapse
My computer's no longer recognizing the phone when I plug the USB in. I tried wiping the user data and cache, but that didn't work either... Is there any other way to edit it?

bunnyrice said:
My computer's no longer recognizing the phone when I plug the USB in. I tried wiping the user data and cache, but that didn't work either... Is there any other way to edit it?
Click to expand...
Click to collapse
Go to recovery, and use this:
http://forum.xda-developers.com/showthread.php?t=2105707

shut_down said:
Go to recovery, and use this:
http://forum.xda-developers.com/showthread.php?t=2105707
Click to expand...
Click to collapse
Thank you so, so much. I will now try modifying the values the way you've said.

bunnyrice said:
Thank you so, so much. I will now try modifying the values the way you've said.
Click to expand...
Click to collapse
You can change permissions in that app by selecting build.prop and hit Files>Change attributes. To 644.

shut_down said:
You can change permissions in that app by selecting build.prop and hit Files>Change attributes. To 644.
Click to expand...
Click to collapse
It worked! I really can't thank you enough, both for saving my phone from my inexperient hands and actually making it work. Thank you.