like some i'm fond of the Sense UI, but not the slide-down lockscreen.
I prefer the CM lockscreen also known as the vanilla stock lockscreen, which consists of you sliding left or right to mute or unlock your phone.
Well after i managed to do some searching and reading up, i found that the Sense ROM contains the vanilla stock lockscreen, but overrides it with an apk of their own lockscreen.
follow these easy instructions to switch back and forth if you like...
**MUST BE ROOTED!!**
1. FIRST do a nandroid backup of your phone. (always a safe practice when changing anything on your phone)
2. go into Partitions -> and unmount your /System/
3. connect your phone to your PC via USB
4. go into your android SDK windows directory
(default) C:\android-sdk-windows\tools\
5. type "adb devices" (minus quotation marks) and make sure your phone is recognized and listed in the output
6. type "adb shell"
7. type "mv /system/app/HtcLockScreen.apk /system/app/HtcLockScreen.bak"
8. type "exit"
9. type "adb reboot", and unplug your phone from the USB
and enjoy.
simply...you just renamed HTC Sense's lockscreen app. since the Sense UI can't find it, it goes back to the default vanilla stock lockscreen. if you want it, just simply nandroid restore or follow the instructions again and rename HtcLockScreen.bak to HtcLockScreen.apk
***
only BUG i've found in using this method is if you use the HTC Sense Alarm clock you won't be able to disable the alarm from the lockscreen. you'll have to unlock your phone first and choose it from the alarm popup.
****
found a stock alarm clock apk that will work with the vanilla lockscreen.
1.Put the file in the tools folder of your Android SDK
2.Reboot to Recovery
3.Mount System
4.Open CMD prompt
5.cd to tools folder (c:\android-sdk-windows\tools)
6. adb push DeskClock.apk /system/app
8.Reboot
Good info, thanks.
Finally, I love the stock lockscreen rather than Sense's
Very nice. Thanks.
asiancuta said:
4. go into your android SDK windows directory
(default) C:\android-sdk-windows\tools\
Click to expand...
Click to collapse
you may want to update this they moved the files to C:\android-sdk-windows\platform-tools\
sljenkins87 said:
you may want to update this they moved the files to C:\android-sdk-windows\platform-tools\
Click to expand...
Click to collapse
is there a new update to the Android SDK software?
Trying to locate the source of the problem, but since doing this hitting menu will unlock the phone. I know this is an option for CM Roms, however i'm running the Liberated Froyo Rom. I know they put in the trackball wakeup option, but i can't find any of the settings that would govern that and menu unlock. it didn't do this with the sense unlock screen.
other question, any way to make the answer call when locked screen be the stock one and not the sense one?
cegna09 said:
Trying to locate the source of the problem, but since doing this hitting menu will unlock the phone. I know this is an option for CM Roms, however i'm running the Liberated Froyo Rom. I know they put in the trackball wakeup option, but i can't find any of the settings that would govern that and menu unlock. it didn't do this with the sense unlock screen.
Minor bug, but worth the reward. May look into it when I have time.
other question, any way to make the answer call when locked screen be the stock one and not the sense one?
Click to expand...
Click to collapse
There is an HTCDialer.apk in the phone's /system/app/ folder. I'm guessing renaming it may replace it. Not sure but worth a try. Just repeat the steps above just the same. I prefer the Sense dialer over stock tho.
It's not so much the dialer (or maybe it is) i have issues with . Right now when i get a call with the phone locked i get the sense answering screen (curved bar to slide up or down.) I'll do some playing tonight to see if that really is part of the dialer or not. I'm not overly familiar with all the software components of android, so it's a learning process for me.
Same here. Just trial and error and learning
you are amazing. i have been trying to sort out a solution to that hideous sense lock screen FOREVER! i love CM, but Liberated seems to run much faster on my phone, so i'm sticking with it.
now that you have fixed my lock screen complaint, i only have one other problem to sort out...skipping music tracks with volume button. i sure miss that feature from CM.
good info.. Although, mine wont work.. It says it cant rename, no such file or directory found. I have checked over and over and it really is in there. My spelling and slashes are perfect. Any ideas?
you need read/write permissions. boot into recovery and select Partitions and Mount System.
then connect in ADB and enter the command
zedbra said:
you need read/write permissions. boot into recovery and select Partitions and Mount System.
then connect in ADB and enter the command
Click to expand...
Click to collapse
Yea that was in the directions previously stated, tried it, thanks though
Ditto with 92, I tried several different ways of getting this to work and got nothing. I for the life of me can not figure this out. Is there a way to post a screenshot of this? or get more info? I'm rolling on a FR008 ROM.
Thanks
I made a copy of froo8 zip in my downloads directory using Astro. Then opened the copy with Astro, deleted the htclockscreen apk. Booted to recovery, nandroid backup, install from zip, and installed the backedup froo8 zip.
Sent from my Liberated Aria thanks to attn1
Hey, I used this method to change the lock screen however when my phone is on silent the right volume slider is turned 90 degrees. Any idea why or how to fix. Sorry no pic because I'm on my phone.
Sent from my HTC Liberty using XDA App
My right volume slider doesn't change positions, Just colors. 90 degrees what direction? Mine points to left.
Sent from my Liberated Aria
Well i flashed the liberated 2.2.2 rom hfr003 and the issue seems to have gone away. Not sure what it was but the slider would rotate to look like you were suppose to slide it up rather that to the left.
Good info, thanks.
I have the FR008 rom flashed on my HTC Aria. Even with using the DeskClock.apk, I cannot turn off the alarm at all! (on the lock screen or after unlocking the phone)
Related
Is it possible to use this mod on the Eris? There is a low res version, which I assume is compatible with our screens; however, I'm terrified of bricking the phone, and I'm not sure if flashing something like this would do so.
Also, to install I would restart in recovery and flash the zip, correct? I encourage everyone to check it out. Even if the current version won't work on the Eris, it would be worth it to port over. The stock keyboard is severely lacking.
showthread.php?t=624416 (no links, sorry)
edit: to perhaps get more people interested, here is the feature list:
* Customizable language settings
* Smileys hacked into the hide key (see screen shots)
* Custom smileys
* Installs also on Android < 2.1
* Custom word candidate bar that raises the keyboards so dictionary won't cover the app you type in
* Prediction in fields with own suggestions (search bar etc.)
* Prediction in fields that sets the filter flag
* Prediction in URL fields
* Disable automatic capitalization
* Play sounds in silent mode
* Set sound level
* Automatic space insertion
* Enable prediction with cursor in or adjacent to existing words (QWERTY only)
* Enable a space bar key in URL keyboard (experimental)
* Prediction for physical keyboard (reported working, not tested by me)
* Support for German QWERTZ hard KB layout
* Show voice input button for all keyboards with a settings button
* Swipe right for voice input on any keyboard
* Swipe left to delete word
* Swipe down to hide keyboard
* Disable key preview popup
* Use Google development server for voice (supports German but isn't online 24/7)
* Position of word candidate list is saved if you long press and move it
* Left align word candidate list
* MANY HTC bugs fixed, the changelog for a few of them
* Droid landscape support with resolution related glitches
* User dictionary import/export (for backup or building your dictionary on your computer)
* User dictionary accepts any character, not just HTC approved ones
* Custom vibration length
* Character replacement (can remove diacritic chars)
* Pipe key in qwerty mode
* My source code is now available for your own modding pleasure
Click to expand...
Click to collapse
V19
I'm curious about this too. I tried to install and it just said, "Not installed"? Can we get this working on the Eris?
well it works
**EDIT**
This keyboard will only work on deodexed roms, consult your devs initial post to see if deodexing was part of their build.
i downloaded and followed the directions per this post...
http://forum.xda-developers.com/showthread.php?t=655383&page=3
really sweet keyboard tons of features, they said they were having issues with the voice search ect but it works on eris...
just a quick run down...
go to the above post...
1. download the LOW RES in the first post...
2. extract zip to your sdk tools folder
3. open your command window get to your tools directory and apply the following commands...
adb remount
adb push Clicker.apk /system/app/
adb push HTC_IME.apk /system/app/
then reboot
**edit**
i could not push the .htcime but be sure to include in the root of your sd card...i just used astro...enjoy.
then reboot
note I take no responsibility if your nuke your phone, this keyboard will replace your oem one...
I keep trying to install the files, and it keeps giving me a not installed error. Not sure what i'm doing wrong, but either installing the files right to my SD card, or trying to load these files using adb isn't working.
how?
I copied the clicker.apk and the HTC_IME.API to system\app using root explorer and have the other file on root of SD card and it erased my keyboard all together. I'm using the sense able. 7 Rom
try...
did u open a msg app, long press a txt box and see a box called input method? if not do so and select touch input. it should load it right up if it was properly installed, im running ivans .7....so idk if that makes a difference...
rom116 said:
I copied the clicker.apk and the HTC_IME.API to system\app using root explorer and have the other file on root of SD card and it erased my keyboard all together. I'm using the sense able. 7 Rom
Click to expand...
Click to collapse
sunder74 said:
did u open a msg app, long press a txt box and see a box called input method? if not do so and select touch input. it should load it right up if it was properly installed, im running ivans .7....so idk if that makes a difference...
Click to expand...
Click to collapse
Yeah. There is no keyboard installed to select. Long press does nothing in a text field, and in the settings menu, there is no keyboard to select
Did you...
Check the system\app folder to see if it were present? i would suggest doing it via adb via the instructions above as it worked perfectly for me try giving that a go...oh did you reboot after you moved the files with your file explorer?
rom116 said:
Yeah. There is no keyboard installed to select. Long press does nothing in a text field, and in the settings menu, there is no keyboard to select
Click to expand...
Click to collapse
How would an non-root go about doing this??
got it sorted...
ok here's why its not working for you... ivans .7 is deodexed, the keyboard didnt include an odex so it works only for deodexed roms, where as the rom u are using isnt.
i flashed it to test and confirm it myself would not load on an odexed rom. we could probably get ahold of the dev or the odex and get it sorted...neway that i believe is the why of it.
sunder74 said:
i downloaded and followed the directions per this post...
http://forum.xda-developers.com/showthread.php?t=655383&page=3
really sweet keyboard tons of features, they said they were having issues with the voice search ect but it works on eris...
just a quick run down...
go to the above post...
1. download the LOW RES in the first post...
2. extract zip to your sdk tools folder
3. open your command window get to your tools directory and apply the following commands...
adb remount
adb push Clicker.apk /system/app/
adb push HTC_IME.apk /system/app/
then reboot
**edit**
i could not push the .htcime but be sure to include in the root of your sd card...i just used astro...enjoy.
then reboot
note I take no responsibility if your nuke your phone, this keyboard will replace your oem one...
Click to expand...
Click to collapse
does this have to be ran through adb? would it be possible to just run everything manually using astro? im very interested in using this keyboard
Im sure you can...
I'm sure you can use a file explorer or something. I just prefer adb as it seems quicker and more "complete" to me give it a try...just make sure ur using a deodexed rom like ivans .7 as the odexed roms will not recognize it.
2wisted said:
does this have to be ran through adb? would it be possible to just run everything manually using astro? im very interested in using this keyboard
Click to expand...
Click to collapse
Odexed Roms
Does anybody know how to get this to work on odexed roms? I am using the Sense Able ROM and it won't work.
Doesn't work on evil Eris 1.1 just force closes.
iloveandroid said:
How would an non-root go about doing this??
Click to expand...
Click to collapse
+1... I want the voice search on all my text inputs... (running second 2.1 leak btw)
false_apology said:
+1... I want the voice search on all my text inputs... (running second 2.1 leak btw)
Click to expand...
Click to collapse
i pm'd the dev and requested the original file including the odex, hopefully one of ours can work their magic and port it to the odexed roms...for those running the deodexed rom I think ivans .7 it works well...any of the deodexed eris builds actually should work.
I take it that this keyboard would not be functional with Swype?
Very old mod. Probably no longer works. Use at own risk. No longer supported by me.
ROOT REQUIRED
ONLY works on ROMS that include HtcLockScreen.odex.
So it wont work if you've flashed lwp patches, Sprint ROMS or anything that removes the .odex file.
-------
Originally created by JsChiSurf over in the Hero forums via my encouragement This version is made for the Eris, it is not the same as the Hero version (which doesn't work properly for us).
This is a modification of the STOCK HTC Sense lockscreen that removes the background so you can see your homescreen behind it.
*Users need to already be comfortable with using 'adb' I won't be providing support on that since there are numerous threads with instructions all around.*
**Before** pushing the apk into that folder, you'll need to FIRST perform the following steps to remove the stock lock wallpapers from loading, as well as any cached custom wallpaper you have applied. You can perform these via adb as listed, or if you have Root Explorer (on the marketplace), you can navigate to the folders listed and delete the items that way.
Code:
adb remount
adb shell
cd /data/misc/lockscreen
rm *
cd /system/customize/resource
rm htc_wallpaper*
exit
Note: You may or may not have anything to delete in /system/customize/resource, so if you get an error message while using adb, don't worry.
HtcLockScreen.zip MD5: 9423D8C3D6CBBF3E084CD185130F9649
*APK NOTE: APKs are case sensitive, be sure you install this without renaming it, or it wont overwrite your original APK*
After you extract the zip to your sdk/tools directory perform the following (case sensitive):
Code:
adb push HtcLockScreen.apk /system/app
adb reboot
If you get "read-only" errors, try "adb remount" OR "adb shell", then, "su", then "mount -o rw,remount /dev/block/mtdblock3 /system" and then the other commands.
EDIT: Clock-less version now available for download! Same instructions apply.
Clock-less Info: **Since some users may have performed the 'experienced users' steps below, an Android image has been added to 'lockscreen_topedge.png' so that it isn't 100% transparent.
If you want to remove this image: First, download the ZIP below with the PNGs, take any one of those and rename it to 'lockscreen_topedge.png, open the lock apk in your favorite zip file manager (winzip, winrar, 7-zip), navigate to "res\drawable-normal-mdpi" and drag your newly-renamed PNG in there. If a dialog pops up, be sure you select the option that has NO compression, this is usually called "Store."**
Make a post if you have any problems NOT related to 'adb.' Again, support is not provided for that.
Clockless Lock.zip MD5: B604B530E02C47DA81AD8B4563BE71D2
__________________
Now some optional additional steps for **experienced users only** (I suck at tech support so if you ask something, I'll try to answer, but no guarantees):
If you put the PNGs included in the zip below into 'com.htc.resources.apk\res\drawable-mdpi', it will remove the HTC "Arc" on the lockscreen. Now, to create your own Arc replacement, all you'll need to do is go into 'HtcLockScreen.apk\res\drawable-normal-mdpi' and change the lockscreen_topedge.png to your liking A much easier change than fiddling with your resources apk everytime and its only 1 image to change, instead of trying to line up three. Of course, if you remove the Arc and do not change your lockscreen_topedge.png, you will have a completely invisible lockscreen, so don't freak yourself out, just make something for that PNG.
*Does not seem to work with Hero or Legend ROMs*
I've used adb push (to change my boot animation) but I can't say I know how to use it.
Can you specify which commands to use?
EDIT: do you have to have root for this?
Yes you have to have root. You would do 'adb install HtcLockScreen.apk'.
wshuman3 said:
You would do 'adb install HtcLockScreen.apk'.
Click to expand...
Click to collapse
waahhh no X_X this isn't an app to be installed. you are overwritting the old one (after youve backed up!) the "install" command installs to data/app, which isn't what we want (but thanks for keepin an eye on the thread for me wshuman3 )
if you put the apk in your sdk\tools directory, then the command would be
Code:
adb push HtcLockScreen.apk system/app
you were correct about needing root tho
oh sweet!
one question though, what if your phone is locked? will it still show the homescreen?
Lemcott said:
oh sweet!
one question though, what if your phone is locked? will it still show the homescreen?
Click to expand...
Click to collapse
please read the first post again before you post. your question is answered in both the thread title as well as the second line.
thanks!
no no no... okay I admit, i worded that question wrong.
if you phone is password protected, as in locked down, with the graphical password and all that. will it still show the homescreen?
Lemcott said:
no no no... okay I admit, i worded that question wrong.
if you phone is password protected, as in locked down, with the graphical password and all that. will it still show the homescreen?
Click to expand...
Click to collapse
i believe it should still show you the home screen, considering with the normal lock app by htc in order to unlock it with the dot pattern, you have to pull the slider down, then it shows you the pattern. so going off of that, then it should still do the same thing, but instead of showing a pic on the lock screen, it shows the home screen, then you slide it down to unlock, which i would assume that it would then pop up the dot pattern.
ECLIPS3's explanation is entirely correct. locking will not hide your homescreen. but then, if someone wanted to see your homescreen with the normal lockscreen, they would just have to slide down the Arc most of the way and they'd see most of it. not secure either way.
but i dont think thats what you were even worried about Lemcott. but explained it anyway
yep, you got it I'm not really worried about them seeing the homescreen (oh no! they saw my poor organizational skills! I'm ruined! haha) I just have my phone locked done mainly because my friends and I have a pretty long running epic war to change each other's facebook status'/tweets to very embarrassing things, nosey family members, and just in case i ever forgot it somewhere.
cant wait till i get my new phone in tomorrow and patch this sucker on. speaking of which, if i were to patch this after flashing on Jamezelle's sense-abloe 2.0, would it look just like the normal htc lock screen just transparent? or will it look like sense-able's lock screen but transparent?
Lemcott said:
yep, you got it I'm not really worried about them seeing the homescreen (oh no! they saw my poor organizational skills! I'm ruined! haha) I just have my phone locked done mainly because my friends and I have a pretty long running epic war to change each other's facebook status'/tweets to very embarrassing things, nosey family members, and just in case i ever forgot it somewhere.
cant wait till i get my new phone in tomorrow and patch this sucker on. speaking of which, if i were to patch this after flashing on Jamezelle's sense-abloe 2.0, would it look just like the normal htc lock screen just transparent? or will it look like sense-able's lock screen but transparent?
Click to expand...
Click to collapse
it will look like the normal lock screen, just transparent. but you could edit the transparent lock screen to look like jameselles, just transparent. im sure someone would be willing to do that for you. i might, just dont have time right now.
I'll give it a whirl, but if anyone wants to race me be my guest, I'm pretty noobish when it comes to android/linux, but I'll give it my best.
Lemcott said:
if i were to patch this after flashing on Jamezelle's sense-abloe 2.0, would it look just like the normal htc lock screen just transparent? or will it look like sense-able's lock screen but transparent?
Click to expand...
Click to collapse
99.9% sure your senseable lock would be in-tact, just transparent. since your senseable lock's graphics are stored in com.htc.resources.apk and this is only a change to your HtcLockScreen.apk
Running Ivan's 0.8T2, works like a charm. Thanks!
For all of those confused on how to install this, you simply unzip HtcLockscreen.zip on your computer, follow the instructions in the first post, then you:
Code:
adb remount
adb push HtcLockScreen.apk /system/app
adb reboot
and when your phone boots back up, you'll be looking at a shiny new transparent lockscreen.
Arcalyth said:
Running Ivan's 0.8T2, works like a charm. Thanks!
For all of those confused on how to install this, you simply unzip HtcLockscreen.zip on your computer, follow the instructions in the first post, then you:
Click to expand...
Click to collapse
NOTE!: the code is case sensitive, make sure you capitalize as follows:
Code:
adb remount
adb push HtcLockScreen.apk /system/app
adb reboot
When I try this I always get the nexus 1 lock screen. I'm running Ivan's latest build.
I will try again on a fresh flash since I have been messing with stuff.
Edit: OK, fresh flash without wiping allowed me to change to the Transparent Lock Screen. Thanks gohamstergo.
btw, I have no idea what I changed to not allow this mod.
@silver: not sure but youre not the only one with the issue. no idea what causes it. seems rare tho
AWW, I thought I was special.
But, If anyone ever needs any "rare issues or bugs" found....
Thanks for posting this!
Would anyone consider making a "lockscreen" that is nothing BUT a photo/walpaper?
No clock, no arc, nothing?
Maybe just a "walpaper" or photo?
Or even better- Truly Transparent!
That would be cool!
TheAtheistReverend said:
Thanks for posting this!
Would anyone consider making a "lockscreen" that is nothing BUT a photo/walpaper?
No clock, no arc, nothing?
Maybe just a "walpaper" or photo?
Or even better- Truly Transparent!
That would be cool!
Click to expand...
Click to collapse
If read the "advanced" directions in the OP, it basically explains how to do this, even though he was trying to tell you how to AVOID doing that. but I agree, I'd like it too. It would almost be like a security feature cuz only you would know where to swipe to unlock
I shall take no credit for any of this. Smartsreenath first put me onto the idea, and pretty much anyone if this forum could've managed it. I just had the time to do it all.
Woo! Snakehult, being a genius, has made a clever little zip that uses proper scripts to just change the required value, instead of the whole file. So! Instead of me making an insane number of zips every time ROMs are updated use these instead. Cheers Snakehult!
Attached is a zip file with a whole lot of flashable zips in it. Don't flash the zip you download, extract that one somewhere and look inside
How to use:
Download the attached zip file, and extract it to somewhere on your computer. Inside the zip are a bunch of folders, each folder named after a ROM for the HTC Legend. Navigate into the folder that shares the name of whatever ROM you are using and inside you will find 6 zip files. These zips are flashable. The the zips are names thus: xxx.zip, where xxx is a number. The lower the number, the higher the apparent resolution. Choose a zip, copy it to your SD card and flash it like any other zip. To revert back to how it was simply flash the "160.zip". This just flashes a completely un-modified version of build.prop for your ROM. Make sure you only use the zips form the correct folder for your ROM, or funny things *might* happen.
More info:
By editing the build.prop file it is possible to increase the dpi of an Android device. This essentially scales everything down, so you can fit more on the screen. This is especially nice for browsing the market and the internet; as well as improving, in my opinion, the overall Android experience. The lower the number in the name of the zip, the higher the apparent resolution. It's worth noting that this does *not* change the actual resolution of the Legend; it's still a HVGA device. So you still can't install apps designed for bigger, more powerful phones, like the HTC Desire or Nexus One. This is a somewhat flawed way of achieving this effect, and can have some ugly side effects:
Some apps simply don't scale
HTC-IME mod ends up screwed
Games *can* be rendered unplayable, but not always. Often the menu is the worst affected part.
A work around to fix a number of issues is to disable the built in compatibility mode of Android, and if I knew a way to do this through a zip, rest assured that I would. It'd save me having to explain how to do it. Alas, I don't know how, so here's how:
In your ROM look for an app called "Spare parts". If it's not there look for it in the market. If you open that app and scroll down to the bottom you will find a checkbox option for "Compatibility mode". Ensure that this is *un-checked*, then reboot. Most issues will be resolved. As I learn more about Android I shall keep an eye out for a way to force apps to scale correctly, and if I ever find one I'll update these.
I have also tried values higher than usual, just for kicks. I don't expect them to be useful, nor will I make actual zip files for them, but I went all the way up to 200; and it felt like I was using an HTC wildfire: everything was really quite cramped.
My personal favourite setup is as follows:
CM 6.1, with a 768MHz overclock
My "lcd-density" (this MOD) set to 130
Launcher Pro Plus with 5 icon rows
Below is a paste of what was the first post (when I was just trying to fix a ****-up on my part), and is now here for reference. It has all of the original build.prop files attached.
Attached is a .zip file, which you will need to extract somewhere. It's not for flashing. Within this zip are several folders, each containing a "build.prop". You'll notice that each folder is named after a ROM: Azure, NeonMOD etc. The "Based-on-stock" folder should cover these ROMs:
[ROM] Based on Official WWE_2.03.405.3 ROM + A2SD [Rev 03 - released]
[ROM] UPDATED Almost Stock Legend HTC WWE 2.03.405.3 Radio 7. 08.35.21
You'll need to use ADB to push these files, as I haven't had time to make flash-able zip's for them yet
Instructions:
1. Extract the zip to a suitable directory, and locate the appropriate build.prop
2. Copy the build.prop to your AndroroidSDK/tools folder
3. Reboot your phone into ClockworkMOD recovery and navigate the the "Partitions menu", then click "mount /system"
4. Connect your phone to the PC and start CMD/a terminal window in your AndroidSDK/tools folder
5. Run the command "adb devices" to ensure that the ADB server is running, and that the PC has detected your device correctly
6. 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
This will put your resolution back to default, but should fix everything else too. If you still want a higher resolution then follow the guides in posts 1 and 2 of the other thread. This one.
If you can't use ADB for whatever reason you'll just have to wait it out until myself or someone else create proper, flash-able, fixes. I have done this to try and quickly rectify the issue; assuming, of course, that most people in this forum can use ADB
I will make proper zips, but it's getting late for me...
Click to expand...
Click to collapse
hi
here is a zip for neonmod 0.21 with 135lcd, flashed it on my legend today with rom manager
Wow do we have a lot of ROMs...
Anyhoo, I am currently working on appropriate flashable zips for each ROM, and each ROM will have the following versions:
110
120
130
140
150
160 (original)
I'm doin' 'em as fast as I can..
EDIT:
Current thoughts:
All build by Ali Ba have nice, short build.prop files. The current record for the longest one it held by MyTouch Legend...
TheGrammarFreak said:
Wow do we have a lot of ROMs...
Anyhoo, I am currently working an appropriate flashable zips for each ROM
Click to expand...
Click to collapse
Awesome!
All our lovely ROMs are actively being used, and its great.
Thx for all hard work!
No worries, I hope I haven't missed one
Now to sign 50 60 zip files...
EDIT:
DONE! All finished. I really hope they work. I can't test them all, but there is no reason why they won't work. Lemme know either way.
nice job
thanks bro
nice
spare parts is also in neonmod
xennr3 said:
nice
spare parts is also in neonmod
Click to expand...
Click to collapse
Cool, and you can turn compatibility mode off?
TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
sure
1234
TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
thanks for your work! i just tried 130 dpi and it seems really good.. i'll try also others zip asap!
yes with compatibility mode off all softwares i tried work really well!
xennr3 said:
sure
1234
Click to expand...
Click to collapse
Cool, thanks for the info. I'll update the OP when I'm home
Sent from my Legend using XDA App
Wow, really cool mod Love it!
Good job!
Cool, glad you like it
Just flashed 130 for SpeedLegend and it worked like a charm
HTC_IME works here (this isnt the mod)
images dont look so good anymore and stuff, but alright
works fine
edit; TBH I find the 140 to be 'more' compatible overall, and show a better picture (ive tried all the flashables)
thats besides the orgnal setting btw, it gives the best picture by far.
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
SimDroid said:
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
Click to expand...
Click to collapse
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
i glad to hear that someone like you got the idea from my thread........good work ...........and nice job.....you will get all help from me and from my friends
FOLLOW ME http://smartsreenath.blogspot.com/
TheGrammarFreak said:
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
yeah, that is for 5 rows on a screen, but you still can't have 5 icons on a row... That's what I want. I tried ADWLauncher again, but it feels so god damn slow.
Ummm, I have 5x5 icons on my desktop with the stock ADW launcher. Just check out "Settings > ADW > Screen prefs > Desktop cols/Desktop rows"
There is not much that i miss about the stock apps on the Fascinate. However, I must say that I do miss the awesome music widget that you can pull down the CD (with album art on it) from the top of the screen. Do you think it's possible to port this over to use?
I have tried taking the apk and odex files from the stock rom and placing them into /system/app but it does not work. I'm not sure if voodoo's new ext4 file format is causing permission issues or what, but either way i haven't been able to get it working. Anyone have any ideas on this? If not, anyone up for porting over the app
emplox said:
There is not much that i miss about the stock apps on the Fascinate. However, I must say that I do miss the awesome music widget that you can pull down the CD (with album art on it) from the top of the screen. Do you think it's possible to port this over to use?
I have tried taking the apk and odex files from the stock rom and placing them into /system/app but it does not work. I'm not sure if voodoo's new ext4 file format is causing permission issues or what, but either way i haven't been able to get it working. Anyone have any ideas on this? If not, anyone up for porting over the app
Click to expand...
Click to collapse
Are you on JT's rom? if so don't use an apk with an odex, his system is deodex'ed.
Try the following apk, it should work.
I get "application not installed" when I try to install it. Could it be because there is already a Music app called "Music" on Jt's rom?
emplox said:
I get "application not installed" when I try to install it. Could it be because there is already a Music app called "Music" on Jt's rom?
Click to expand...
Click to collapse
That is a system file. You can't just install it. You need to replace the original file with that one with adb or root explorer (or something similar).
blazingwolf said:
That is a system file. You can't just install it. You need to replace the original file with that one with adb or root explorer (or something similar).
Click to expand...
Click to collapse
adb pull /system/apps/musicplayer.apk
backup that version, copy new version into its place.
adb push musicplayer.apk /system/apps/
?? is that how you would do it? or is that even where it is?
I think it's /system/app
regardless, i have tried this and every time i do it my phone goes to black screen after the VZW screen. It will just sit there. Then when I go back and put the original .apk back in place...it boots right up and works. I have a friend trying to go back to the touchwiz calendar who has the exact same problem. Neither of us can figure it out.
emplox said:
I think it's /system/app
regardless, i have tried this and every time i do it my phone goes to black screen after the VZW screen. It will just sit there. Then when I go back and put the original .apk back in place...it boots right up and works. I have a friend trying to go back to the touchwiz calendar who has the exact same problem. Neither of us can figure it out.
Click to expand...
Click to collapse
Here flash this through CW and see if it still gives you a black screen.
that worked can you make one for the touchwiz calendar apk too? I'd love to know what you did to make it and what the difference is so i can do it myself.
The one part that stinks is that the widget on the lockscreen is a feature of TouchWiz lockscreen, as it's not work on stock. Once I flashed the puzzle lock it worked.
I thought I'd offer my solution to disabling the hard key vibrations on the Atrix since other people might find this useful. This method differs from the other solutions in that it doesn't tamper with your Silent Mode vibrations (like StreakVibrations does) and it's code based, so it shouldn't tamper with any themes you have installed (like the framework-res.apk method). It is firmware dependent though since it's a code modification.
You'll need an android.policy.jar modified for your firmware.
What I'm doing is I'm modifying the method called performHapticFeedbackLw, and telling it to skip triggering the vibrate pattern for all effects (there are 5) except for keyboard taps. Long press vibe, virtual key vibe, safe mode disabled vibe, and safe mode enabled vibe will no longer trigger... Incidentally, does anyone know what safe mode on this phone refers to?
To use the file, you need to be on Bell, Telstra, GingerBlur, Gladiatrix or stock ATT 1.8.3 firmware, and be deodexed. Can you copy the file to your phone without being deodexed? I don't know. I'm a programmer, but an Android newbie so just to be safe it's best if you're deodexed.
Before you try anything, obviously make sure you are backed up. At least copy your existing android.policy.jar so that you can restore it if necessary.
All you need to do is either:
a) Run the novibes.bat script packaged in the zip. There are a couple prerequisites:
1. Make sure to set your USB connection to "None" on your phone.
2. On your phone, go to Settings > Applications > Development and make sure USB debugging is turned on.
3. Plug your phone into your PC and let it install any necessary drivers.
4. Then you can run novibes.bat.
or
b) Follow the steps outlined below to do it manually:
1. Replace /system/framework/android.policy.jar with the one that I've attached.
2. Make sure the permissions of the file are set to rw-r--r-- (thanks for reminding me, Meloy and for correcting, natboy!). The easiest way is to use Root Explorer, long press the file, choose permissions, and set owner: read/write, group:read, others:read. Otherwise, use Terminal and type "chmod 644 /system/framework/android.policy.jar" without the quotations.
3. Reboot.
For those not on stock Bell, I'd be willing to modify your android.policy.jar and post it here if you provide somewhere for me to download it, and specify what firmware it comes from. It's quite quick to do once you're set up so I don't mind. Alternatively, make the change yourself:
1. Download baksmali and smali (both .jars and scripts, total 4 files).
2. Copy /system/framework/ from your phone to your computer.
3. Copy all the files from step 1 to the framework directory from step 2 on your computer.
4. Unzip android.policy.jar and copy its classes.dex file to the framework directory on your computer.
5. From the command line, navigate to the framework directory and run "./baksmali classes.dex". It will create a directory named "out".
6. Open "out/com/android/internal/policy/impl/PhoneWindowManager.smali" in a text editor.
7. Search for a method called "performHapticFeedbackLw". Go to near the bottom of that method, and you will see the Dalvik bytecode representation of a switch statement:
Code:
.sparse-switch
0x0 -> :sswitch_27 #This is for long press vibe
0x1 -> :sswitch_35 #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :sswitch_3b #This is for safemode disabled vibe
0x2711 -> :sswitch_3e #This is for safemode enabled vibe
.end sparse-switch
8. Here's an example of how you might want it to change. Basically you want to replace the original goto labels with one that causes the method to step out without triggering a vibe, and that notifies the calling method there was no vibe by returning false. The label to use is called ":cond_1d":
Code:
.sparse-switch
0x0 -> :cond_1d #This is for long press vibe
0x1 -> :cond_1d #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :cond_1d #This is for safemode disabled vibe
0x2711 -> :cond_1d #This is for safemode enabled vibe
.end sparse-switch
9. From the command line in the framework directory, run "./smali -o classes.dex out". You now have a new classes.dex that has your modification.
10. Zip up the classes.dex with the META-INF directory from your original android.policy.jar. Rename the zip to android.policy.jar.
11. Copy the new file to your phone and reboot.
12. At this point you should be done.
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
n1ckr0th said:
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
bearsfan172 said:
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
Click to expand...
Click to collapse
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
n1ckr0th said:
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
Click to expand...
Click to collapse
Yes, this would work perfectly fine on ATT. You can either follow the instructions I provided, or if you like you can post /system/framework/android.policy.jar from your phone somewhere and pm me the link so I can download it and I'll do it for you. Also mention what firmware you're on. I just don't want to download hundreds of MB of firmwares which is why I didn't set one up for all the ATT firmwares.
That other method requires editing a file that is guaranteed to change with any theme you install. That means anytime you change themes you'll need to edit that .apk yourself, or wait for someone to bring the change over. android.policy.jar is unlikely to change for themes.
Ok, I've posted a version for ATT 1.8.3 that was given to me by n1ckr0th.
n1ckr0th, let me know whether it works fine or not. There should be no problem, it looked just like the other 2 versions I modified.
Incidentally, he's using GingerBlur 3.5 so anyone on stock be careful (ie. copy your original file to somewhere else on your phone). It shouldn't matter at all because from what I see, there aren't any resources to modify in android.policy.jar so GingerBlur's should be the same as stock. At any rate, it won't brick your phone if you put the wrong one on. I put Telstra's on my phone by accident and it just messed up the the graphics on screen (maybe because the addresses were all wrong for my phone). You can still use adb, or sshdroid to copy and replace with your original android.policy.jar.
please delete
meloy said:
Don't use this on AT&T 1.83!
After the replace and reboot my phone was really laggy and some applications doesn't start anymore (camera, contacs for example). After i have replaced it with the original file i have still the same problem.
My phone config:
- SBF 1.83
- rooted (GingerBreak 1.20)
- sideloading enabled (GladEnabler)
- GladiAtrix 3 b0.2 ROM
- LauncherPRO
- GingerBread Theme only
Click to expand...
Click to collapse
What? That can't be right, if you still have the same problem after copying the original file, that means that you must have done something wrong. It's a single file change, provided you returned the file to the original, it will be back to the way it was. How did you copy the file? And also, are you deodexed? As mentioned in the original post, you have to be deodexed, because I don't know the results of using it on a non-deodexed system. Your posted config makes it sound like you might not be.
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
meloy said:
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
Click to expand...
Click to collapse
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
maledyris said:
Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
meloy said:
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
Click to expand...
Click to collapse
Interesting, that never occurred to me. I usually go into terminal and type in reboot to reboot my phone. I think I'll add that to my phone too...
maledyris said:
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
n1ckr0th said:
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
Click to expand...
Click to collapse
Hmm, how far does it get? Do you at least get to the boot animation? I notice that it may sit at the boot animation for a really long time after changing a file sometimes. Probably updating the cache or something. It's odd that it wouldn't work for you considering it's your file and it worked for meloy. How did you copy the file over?
If you try again, delete the original file, so you can be sure it's no longer there, then try the copy again.
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
I have no problems with this mod. It works all fine.
Been waiting on this mod. Streakvibrations has me missing my notification vibes. Thank you
It gave me a red light on boot, stuck at Motorola logo for infinity. I booted into recovery and reflashed gb 3.5 to fix it. Ill try your idea of deleting it then moving the new one.
Sent from my MB860 using XDA App
EDIT: still didnt boot, had to flash again..
I'm getting the flashing red light and rebooting as well. I can't get into CWM though, going to have to flash a SBF. Only think I can think of is maybe the Dalvik cache needs to be wiped before rebooting?
Edit: I'm on an AT&T phone and used GB to deodex as well.. maybe it's not catching all the files..
lurchbyrep said:
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
Click to expand...
Click to collapse
Are you on stock 1.83? Now that we know that android.policy.jar has some mods built into it for Gingerblur pseudo rom, the att 1.83 file I posted probably isn't ideal for stock users.
If you're on stock, maybe you could post your android.policy.jar somewhere and pm me the link to download. Then I could put together a pure stock att one when I get home.
Sent from my MB860 using XDA App