Related
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
All,
I have an HD+ running 2.0.5 and its rooted. When I've turned on wifi, half the time it tries to update to 2.0.6. It always goes through its process then dies at 99% and drops back telling me that something is wrong. The first time I freaked out and thought something really WAS wrong.
Boy was I relieved to see that I still had my stock root.
I was just thinking that maybe I should update to 2.0.6 just to keep it current. I use the Nook side for reading and stuff as it is. Can I just rerun the root process like I did for 2.0.5?
Also what is the best way to make it not fail the update?
I did the white-on-white fix, but changed it back.
Please don't tell me I need to do the 8 boot factory reset.
Thanks,
-Jeff
How did you change back the white on white? I suspect that is what is wrong.
Sent from my Nook HD+ running CM10 on Hybrid SD
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
js5752 said:
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
Click to expand...
Click to collapse
No, I understand what you did. You left the symlink in /system and just manipulated the files in /data. That works to get rid of white on white, but does not put framework-res.apk back in /system. And the update zip needs framework-res.apk there. That is why it was failing.
Did you do a back up of your system before you added white on white like I recommended? If so, restore that and then update. If you did not, you can try putting that original framework-res.apk back in /system/etc via ADB. Doing it with ADB prevents that crashing you experienced the first time.
As a last resort go back to 2.0.0 with my plain stock zip in my HD/HD+ CWM thread. You can flash that and it will not erase your media files. You should backup your system with CWM first. Then wipe /data, then flash the zip. Then sign on, register and it will update you to 2.0.6. Then go to CWM and do an advanced restore of /data. Then flash again the zips you want, like root or gapps. Then you should be ok.
Edit: If you want to keep 2.0.5 and not be bothered by those attempts to update, I just added to both my Tips thread and my CWM thread linked in my signature a method to stop those updates.
Sent from my Nook HD+ running CM10 on Hybrid SD
Thanks for the reply.
I expected the crash from what I had read. I just decided that ADB was more hassle than it was worth for a quick change. That and I like to live dangerously
Ok, the symlink vs the data file makes sense. Now I understand why it wasn't working. Thank you, because I thought all was back where it should be.
As for backups, I did one before rooting, and I've done a couple since just to make sure I've got backups. That plus titanium, I figured I should be able to recover if the worst happens.
Thanks for the tips, and for all the work you've done on rooting these devices. It was the option to root that tipped me over the edge to buy one, and I'm glad I did.
-Jeff
I bought a rooted One from someone. Thing is, I can edit files in the system directory, but changes are lost when I reboot the device.
Is the device rooted incorrectly or do I need S-OFF to make that work (sorry, long time ago that I played with root)
appelflap said:
I bought a rooted One from someone. Thing is, I can edit files in the system directory, but changes are lost when I reboot the device.
Is the device rooted incorrectly or do I need S-OFF to make that work (sorry, long time ago that I played with root)
Click to expand...
Click to collapse
You need to use this with Android Revolution HD (not sure if it works for all roms) to remove the system RW protection which reverts all changes on boot.
http://forum.xda-developers.com/showpost.php?p=40131685&postcount=1839
First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!
This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.
What is write enabler?
Keeps aborting for me
THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.
@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.
To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.
What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?
ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2
ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.
I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.
I reinstalled the stock odex ROM and flashed this again and it worked.
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app
fails in recovery for me.
says error executing updater binary in zip
in stock rooted...
I've been racking my brain trying to figure out what the cause of this is and it is extremely frustrating at this point. I've written a few scripts to automate some things that I would like to do on my phone and moved them into /system/bin. They would all instantly be deleted. I've just about given up on the issue of actually using scripts because of this, but now even moving a simple .mp3 file to use as a ringtone won't work.
I moved my .mp3 file into the /system/audio/media/ringtones folder. It copies over successfully and then it is instantly deleted. What gives, and how do I fix this?
/system is protected, so anything moved to it will get wiped. I believe if you flash a zip in recovery it can get around this though.
KiraYahiroz said:
/system is protected, so anything moved to it will get wiped. I believe if you flash a zip in recovery it can get around this though.
Click to expand...
Click to collapse
Strange, I distinctly remember not flashing any kind of .zip on my Nexus 7. All I did was root it and I was able to read/write to system as long as I granted permissions through SuperUser. Is that not the case with this phone?
If not, where else can I move script files and ringtones in order to use them?
Usually rooting and moving files works, but HTC has done something that doesn't allow this.
Not sure about the scripts, but for ringtones, you can just leave it anywhere you like. In the sound settings, you can choose what ringtone you want, just click "+" on the top right when choosing sound. Notification tone is a tad more tricky though...
EDIT: Ok worked it out, usually in most android phones you can paste them at sdcard/media/audio/ringtones and sdcard/media/audio/notifications, but for the One it's just sdcard/Ringtones and sdcard/Notifications. .ogg files don't work as well (which is weird since that's what AOSP uses...), you need to convert them to mp3/m4a.
Just drop your ringtones, notifications or alarms in the corresponding folders on the sd card. No need to put in system anymore.
Sent from my HTC One using xda app-developers app
I'm pretty sure changing your kernel removes the system protection.
Sent from my HTC One using xda app-developers app
KiraYahiroz said:
Usually rooting and moving files works, but HTC has done something that doesn't allow this.
Not sure about the scripts, but for ringtones, you can just leave it anywhere you like. In the sound settings, you can choose what ringtone you want, just click "+" on the top right when choosing sound. Notification tone is a tad more tricky though...
EDIT: Ok worked it out, usually in most android phones you can paste them at sdcard/media/audio/ringtones and sdcard/media/audio/notifications, but for the One it's just sdcard/Ringtones and sdcard/Notifications. .ogg files don't work as well (which is weird since that's what AOSP uses...), you need to convert them to mp3/m4a.
Click to expand...
Click to collapse
Thanks, that takes care of the ringtones and notifications. Now if only I could figure out where to store my scripts so that they'll run from any location.
lampel said:
I'm pretty sure changing your kernel removes the system protection.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Is flashing a kernel the only way to make system writable? I'm hesitant to do so because I have no issues with the stock kernel at the moment and all I really want is to be able to run scripts. That said, what's the best kernel available for the One right now?
raphytaffy said:
Thanks, that takes care of the ringtones and notifications. Now if only I could figure out where to store my scripts so that they'll run from any location.
Is flashing a kernel the only way to make system writable? I'm hesitant to do so because I have no issues with the stock kernel at the moment and all I really want is to be able to run scripts. That said, what's the best kernel available for the One right now?
Click to expand...
Click to collapse
I do not believe flashing a kernel will give you system write capabilities. HTC has a security implementation known as S-ON which prohibits write access to the system partition. Until S-OFF has been obtained (not out yet) the only way to write to the system partition is via a flashable zip or adb.
Sent from my HTC One using xda app-developers app
RPelham said:
I do not believe flashing a kernel will give you system write capabilities. HTC has a security implementation known as S-ON which prohibits write access to the system partition. Until S-OFF has been obtained (not out yet) the only way to write to the system partition is via a flashable zip or adb.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Sorry, I should have mentioned that I have the HTC One Developer Edition, which I believe comes with an unlocked bootloader and S-OFF. I am able to write to /system through adb after mounting it, but my files are immediately deleted after writing to it.
There are kernels and fixes available to fix writing to /system but I'm not sure they apply to the dev edition so I'm not posting links - I don't want to suggest something that gives you a bootloop or worse... And I think a few S-OFF units have shipped but I don't think all the dev editions are S-OFF although they are all bootloader unlocked.
raphytaffy said:
Sorry, I should have mentioned that I have the HTC One Developer Edition, which I believe comes with an unlocked bootloader and S-OFF. I am able to write to /system through adb after mounting it, but my files are immediately deleted after writing to it.
Click to expand...
Click to collapse
S-ON is a security measure that does prevent writing to certain areas but I don't think it will affect writing to /system on this phone as long as the kernel allows it.
RPelham said:
I do not believe flashing a kernel will give you system write capabilities. HTC has a security implementation known as S-ON which prohibits write access to the system partition. Until S-OFF has been obtained (not out yet) the only way to write to the system partition is via a flashable zip or adb.
Click to expand...
Click to collapse
lampel said:
There are kernels and fixes available to fix writing to /system but I'm not sure they apply to the dev edition so I'm not posting links - I don't want to suggest something that gives you a bootloop or worse... And I think a few S-OFF units have shipped but I don't think all the dev editions are S-OFF although they are all bootloader unlocked.
Click to expand...
Click to collapse
No worries, I found a thread for the kernel module that will allow system writes. If anyone else is looking for the same solution, the thread is here: http://forum.xda-developers.com/showthread.php?t=2230341.
Thanks for the help everyone!