Database Info

[HACK] Remove / Rename the operator logo on lockscreen

Hello,
someone knows how to rename / remove the operator logo on the lockscreen?
I already searched the forums and google but couldn't find anything.
Thanks

xPatriicK said:
Hello,
someone knows how to rename / remove the operator logo on the lockscreen?
I already searched the forums and google but couldn't find anything.
Thanks
Click to expand...
Click to collapse
with cm6 you can change the color and/or remove it in cyanogenmod settings...not sure if it is in alpha1 but the nightlys have it and definitely the next release

As far as I can tell, these settings are created by the active (ie Network Connected) SIM card placed in the phone. We have the ability to slightly modify the display, but i'm unsure of a total change- such as switch "T-Mobile" to say "AT&T". I don't see any entry in the build.prop to do so. If someone finds a way, please let me know. I could think of a host of funny things to say on my Froyo lockscreen.

Try this, copy the code bellow into notepad
<EriFile VersionNumber="1357" NumberOfEriEntries="1" EriFileType="1">
<CallPromptId Id="0" CallPromptText="CallPromptId0"/>
<CallPromptId Id="1" CallPromptText="CallPromptId1"/>
<CallPromptId Id="2" CallPromptText="CallPromptId2"/>
<EriInfo RoamingIndicator="128" IconIndex="1" IconMode="0" EriText="Sprint" CallPromptId="0" AlertId="0"/>
</EriFile>
Replace the Sprint text within the quotes to whatever you want.
Save the file as "eri.xml" NOT .txt no quotes.
Place the file in /system/etc/ or in /data not sure which is the right one for your phone so try one then the other.
Reboot your phone.

xuser said:
Try this, copy the code bellow into notepad
<EriFile VersionNumber="1357" NumberOfEriEntries="1" EriFileType="1">
<CallPromptId Id="0" CallPromptText="CallPromptId0"/>
<CallPromptId Id="1" CallPromptText="CallPromptId1"/>
<CallPromptId Id="2" CallPromptText="CallPromptId2"/>
<EriInfo RoamingIndicator="128" IconIndex="1" IconMode="0" EriText="Sprint" CallPromptId="0" AlertId="0"/>
</EriFile>
Replace the Sprint text within the quotes to whatever you want.
Save the file as "eri.xml" NOT .txt no quotes.
Place the file in /system/etc/ or in /data not sure which is the right one for your phone so try one then the other.
Reboot your phone.
Click to expand...
Click to collapse
Doesnt work..
could it be in the apn-config.xml in system/etc?

Looking for an answer too. I know We can modify the operator name on Home screen but could we change it on lock screen as well?

xPatriicK said:
Hello,
someone knows how to rename / remove the operator logo on the lockscreen?
I already searched the forums and google but couldn't find anything.
Thanks
Click to expand...
Click to collapse
In CM 6, one can remove it from lockscreen. (not rename though)
-> disable PLMN field on lockscreen (in: CM sett..user interface...data provider)

rori~ said:
In CM 6, one can remove it from lockscreen. (not rename though)
-> disable PLMN field on lockscreen (in: CM sett..user interface...data provider)
Click to expand...
Click to collapse
You can also remove it from the statusbar/notifications but I'd rather rename it

Atermoon said:
You can also remove it from the statusbar/notifications but I'd rather rename it
Click to expand...
Click to collapse
if you look here http://review.cyanogenmod.com/ you'll see that someone worked on it, but it seems they don't like the current incarnation and might add it into the CM Settings.

Renaming the operator name is no problem, basically its a one liner using setprop but it could lead to unwanted side effects for apps that rely on the alphaname of a provider and not only on the mnc.

rac2030 said:
but it could lead to unwanted side effects for apps that rely on the alphaname of a provider and not only on the mnc.
Click to expand...
Click to collapse
Didn't know it exists something like that..
Well, looks like we can't really change it at all.. atleast not like on old Sony Ericsson phones with .elf's or patches good old times haha

xPatriicK said:
Didn't know it exists something like that..
Well, looks like we can't really change it at all.. atleast not like on old Sony Ericsson phones with .elf's or patches good old times haha
Click to expand...
Click to collapse
? You can but with said side effect
If you want to change the lockscreen or the statusbar only to show a fake name you can always get the sources and compile it for yourself with the modifications.

Is there a way to insert custom Text to the Lockscreen?

[Q] Lock Screen xml?

Hope this isn't a double post.... I would like to change the lockscreen image to something other than the background of the phone. Maybe through editing the .xml file on the phone? etc. Anyone know of how to do this?
PS... PLEASSEEEEE don't reply with anything about widgetlocker. I know it exists I know it can do this but and I am not trying to nor do I want to use it for various reasons ...
Thanks in Advance.
-Adam

Here your are
had a little trouble with this, but here's a full guide that worked for me "tools used apk manager 4.9"
using the apk manager
1. pull /system/framework/framework-res.apk (option 0)
2. Decompile apk (option 9)
3. add your pic to drawable-mdpi (must be a .png) eg. lockscreen_background.png
4. open the file res\layout\keyguard_screen_tab_unlock.xml with notepad, and find the line
<RelativeLayout android:gravity="center_horizontal" android:id="@id/root" android:background="#70000000" android:layout_width="fill_parent" android:layout_height="fill_parent"
change to
<RelativeLayout android:gravity="center_horizontal" android:id="@id/root" android:background="@drawable/lockscreen_background" android:layout_width="fill_parent" android:layout_height="fill_parent"
5. compile the apk (option 9)
(when recompile do)
5.1. Hit yes to "system app".
5.2. Hit yes to restoring the files:
6. -Open the "keep" folder and delete resources.arsc and res\layout\keyguard_screen_tab_unlock.xml
7. when done rename unsignedframework-res.apk to framework-res.apk and put it back to /system/framework/ again (i did this in recovery)
Done

Awesome... Thanks.. Did you try this on the Droid X?

or can you change the lockscreen background to a dedicated image through ninjamorph? anyone have a quick tut on how to do this with a droid x?

Translucent notification tray background in 2.3 Gingerbread Guide ?

Anyone know how to get a Translucent notification tray background in 2.3?

martijua said:
Anyone know how to get a Translucent notification tray background in 2.3?
Click to expand...
Click to collapse
It has to be done in systemui.apk. Have to open that specific file to the rom your running and edit the files inside. What exact rom are you running?

fdb8231 said:
It has to be done in systemui.apk. Have to open that specific file to the rom your running and edit the files inside. What exact rom are you running?
Click to expand...
Click to collapse
Thanks. I am running the stock rooted deodexed rom.
Here is what I did:
1 nandoid backup
2 adb devices
3 adb pull /system/app/SystemUI.apk SystemUI.apk (made a backup copy of this file)
4 open the SystemUI.apk file with winrar
5 inserted the "status_bar_header_background.9.png", "status_bar_close_on.9.png" and a transparent "status_bar_background.png" into the SystemUI.apk's \res\drawable-hdpi folder
6 adb remount
7 adb push SystemUI.apk /system/app/
8 adb reboot
as you can see from the attached screen shot...the "status_bar_header_background.9.png" and the "status_bar_close_on.9.png" worked but the transparent "status_bar_background.png" isnt transparent.
Any ideas?

martijua said:
Thanks. I am running the stock rooted deodexed rom.
Here is what I did:
1 nandoid backup
2 adb devices
3 adb pull /system/app/SystemUI.apk SystemUI.apk (made a backup copy of this file)
4 open the SystemUI.apk file with winrar
5 inserted the "status_bar_header_background.9.png", "status_bar_close_on.9.png" and a transparent "status_bar_background.png" into the SystemUI.apk's \res\drawable-hdpi folder
6 adb remount
7 adb push SystemUI.apk /system/app/
8 adb reboot
as you can see from the attached screen shot...the "status_bar_header_background.9.png" and the "status_bar_close_on.9.png" worked but the transparent "status_bar_background.png" isnt transparent.
Any ideas?
Click to expand...
Click to collapse
You should use 7 zip then you can open and edit without unzipping. Is this like what you want
Sent from my PC36100 using XDA App

More like this
It used to work in 2.2.
Oh, you dont have to unzip the apk when using winrar.

I believe that in system ui that is actually part of an xml and needs to be moddified using xml.

Is this a simple PNG swap, or are there any XML/smali edits required?

if you're having a bunch of trouble, send it on over to me and i'll help u out.

_Burst_ said:
Ok, check it out, obviously you will need to know how to use apktool. Do not ask me how to use it. Educate yourself.
To make the Notification Bar transparent I followed these steps:
-decompile SystemUI.apk
This is a direct quote and was very similar to what I had to do. The only different is that the code:
isn't exactly that. But, just look for the the const/4 and corresponding 0x2 and change that one to "-0x3."
Also, you may have to hunt for it, but it is there about 5-8 lines up.
To make the Notification Bar Shade transparent I followed these steps:
Again, direct quote and same situation, the v# might not match but just change the "0x2" to "-0x3."
And there ya go. Thanks to Master and ogdobber.
Click to expand...
Click to collapse
Enjoy yoself

SteelH said:
Is this a simple PNG swap, or are there any XML/smali edits required?
Click to expand...
Click to collapse
"status_bar_header_background.9.png" and the "status_bar_close_on.9.png" are simple PNG swap in the SystemUI.APK
Transparent notification background in the deodexed [ROM][STOCK] --- Version 4.22.651.2 --- Odexed & De-Odexed --- that was posted by xHausx requires that the SystemUI.apk be decompiled and then edit the status_bar_tracking.xml changing the default "android:background="#ff000000"" to "android:background="@drawable/shade_bg"". I'm getting a W: could not decode attr 0x20 error when decompiling so I havent been able to successfully make the changes to get the transparent shade_bg notification tray backdound to work.
If anybody can get this done an post the updated SystemUI.apk we'd appreicate it!

I finally figured out what was causing the error and have successfully decompiled the systemui.apk. Next i'm going to try what _Burst_ posted.

_Burst_ said:
Enjoy yoself
Click to expand...
Click to collapse
status_bar_tracking.xml does not have the line in it that is referenced in the link that you posted. I've attached the file.

martijua said:
status_bar_tracking.xml does not have the line in it that is referenced in the link that you posted. I've attached the file.
Click to expand...
Click to collapse
What? yes it is.
so the numbers are different...
Here comes the airplane.... zoooooooooooooooooooooom.
<?xml version="1.0" encoding="utf-8"?>
<com.android.systemui.statusbar.TrackingView androidrientation="vertical" androidaddingLeft="0.0px" androidaddingRight="0.0px" androidaddingBottom="0.0px" android:focusable="true" android:visibility="gone" android:descendantFocusability="afterDescendants"
xmlns:android="http://schemas.android.com/apk/res/android">
<View android:id="@id/background" android:background="@drawable/shade_bg" android:layout_width="fill_parent" android:layout_height="wrap_content" android:layout_weight="1.0" />
<LinearLayout androidrientation="vertical" android:id="@id/swtich_buttons" android:layout_width="fill_parent" android:layout_height="wrap_content">
<View android:background="@drawable/divider_horizontal_dark_opaque" android:layout_width="fill_parent" android:layout_height="1.0px" />
<View android:id="@id/tab_header" android:background="@drawable/list_item_background" android:layout_width="fill_parent" android:layout_height="4.0sp" />
Click to expand...
Click to collapse

martijua said:
"status_bar_header_background.9.png" and the "status_bar_close_on.9.png" are simple PNG swap in the SystemUI.APK
Transparent notification background in the deodexed [ROM][STOCK] --- Version 4.22.651.2 --- Odexed & De-Odexed --- that was posted by xHausx requires that the SystemUI.apk be decompiled and then edit the status_bar_tracking.xml changing the default "android:background="#ff000000"" to "android:background="@drawable/shade_bg"". I'm getting a W: could not decode attr 0x20 error when decompiling so I havent been able to successfully make the changes to get the transparent shade_bg notification tray backdound to work.
If anybody can get this done an post the updated SystemUI.apk we'd appreicate it!
Click to expand...
Click to collapse
I'm working on it . I'm at work now but tomorrow I'm going to hit it pretty hard.
Uot kitchen wouldn't even work for it so.... I'll have to look at the smalis and change the const/
But the v #'s are off and don't match like the op said. But it only looks like there is 2 options for it . I'm just going to do both and report back. If you get it working before I do hit me up. Thanks.

I havent got this to work. I dont think much people have as I dont see any themes or roms with this feature.

martijua said:
I havent got this to work. I dont think much people have as I dont see any themes or roms with this feature.
Click to expand...
Click to collapse
it's in many cm7 themes. should be around soon enough for sense.

Finally got it. I used the uot kitchen site to get it going. Will be sending them a donation after I get home from work. \m/

Widgets
martijua said:
Finally got it. I used the uot kitchen site to get it going. Will be sending them a donation after I get home from work. \m/
Click to expand...
Click to collapse
What are all the various widgets you are using there? They all look pretty useful!

Minimal Text Date, Time, Weather, Battery
S2 Calendar widget
CalWidget

martijua said:
Finally got it. I used the uot kitchen site to get it going. Will be sending them a donation after I get home from work. \m/
Click to expand...
Click to collapse
Looks sweet. Unfortunately the kitchen does not work for the drop down on any kingdom ROM. I've tried to no avail.
Sent from my PC36100 using XDA App

[Tutorial] Enable Backlights for Sense ROMs.

What's up guys. I had found out about this quite a long time ago but I never really got to share it with you all. What my tutorial will do is show you how to enable hardware backlights for our devices. However, I do not know how to make the charging LED work so only keyboard and buttons will work.
What you need:
1. APK Manager from here: http://forum.xda-developers.com/showthread.php?t=695701
2. A framework-res.apk from your ROM
3. Notepad++ which is free: http://notepad-plus-plus.org/
INSTRUCTIONS:
1. Extract the APK Manager anywhere.
2. Place the framework-res.apk in the folder that says "place-apk-here-for-modding"
3. Open APK Manager by opening the file that is named "Script"
4. In the APK Manager window, input "22" for "Select Current Project"
5. Now input the number for framework-res.apk
6. You will be back at the main window, now press "9" to "Decompile APK"
7. Now, from the root of the APK Manager folder, go into "APK Manager\projects\framework-res.apk\res\values"
8. Open up "bools.xml" with Notepad++
9. Find
<bool name="config_automatic_brightness_available">true</bool>
Click to expand...
Click to collapse
and replace it with
<bool name="config_automatic_brightness_available">false</bool>
Click to expand...
Click to collapse
10. Save it and close it.
11. Open up "arrays.xml"
12. Look for:
<integer-array name="config_autoBrightnessLevels">
<item>11</item>
<item>41</item>
<item>91</item>
<item>161</item>
<item>226</item>
<item>321</item>
<item>641</item>
<item>1281</item>
<item>2601</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>90</item>
<item>90</item>
<item>90</item>
<item>170</item>
<item>170</item>
<item>210</item>
<item>210</item>
<item>255</item>
<item>255</item>
<item>255</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValuesUp">
<item>90</item>
<item>90</item>
<item>90</item>
<item>170</item>
<item>170</item>
<item>210</item>
<item>210</item>
<item>255</item>
<item>255</item>
<item>255</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValuesDown">
<item>90</item>
<item>90</item>
<item>170</item>
<item>170</item>
<item>210</item>
<item>210</item>
<item>255</item>
<item>255</item>
<item>255</item>
<item>255</item>
</integer-array>
<integer-array name="config_autoBrightnessButtonBacklightValues">
<item>255</item>
<item>255</item>
<item>-1</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
</integer-array>
<integer-array name="config_autoBrightnessKeyboardBacklightValues">
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
<item>0</item>
</integer-array>
Click to expand...
Click to collapse
and Replace it with
<array name="config_autoBrightnessLevels" />
<array name="config_autoBrightnessLcdBacklightValues" />
<array name="config_autoBrightnessLcdBacklightValuesUp" />
<array name="config_autoBrightnessLcdBacklightValuesDown" />
<array name="config_autoBrightnessButtonBacklightValues" />
<array name="config_autoBrightnessKeyboardBacklightValues" />
Click to expand...
Click to collapse
13. Save it and close the file.
14. Go back to the APK Manager window and input "11" to "Compile APK"
15. When asked for "Is this a system apk" input "y"
16. Input "y" when it asks
Aside from the signatures, would you like to copy
over any additional files that you didn't modify
from the original apk in order to ensure least
# of errors (y/n)
Click to expand...
Click to collapse
17. IT WILL GIVE YOU SOME INSTRUCTIONS, HERE IS WHAT TO DO:
18. Go into "APK Manager\keep" and delete "resources.arsc"
19. NOW GO BACK INTO APK MANAGER WINDOWS AND PRESS ENTER"
20. You are done, go into "APK Manager\place-apk-here-for-modding" and use "unsignedframework-res.apk" for your rom.

Thanks man
---------- Post added at 05:22 PM ---------- Previous post was at 05:16 PM ----------
Is it normal that the file is 2mb smaller now?^^

Rushness said:
Thanks man
---------- Post added at 05:22 PM ---------- Previous post was at 05:16 PM ----------
Is it normal that the file is 2mb smaller now?^^
Click to expand...
Click to collapse
Yeah, the manager compresses the file.
Does it work and everything?

Have to test it first. But in apk-manager everything worked pretty well.

id like to add a tiny piece of info i learned myself lol, the framework-res.apk is very very sensitive while decompiling, so to be sure it re compiles with no issues it needs to be un edited, (png wise) if you added ANY png file to the framework-res.apk file you need to put all the stock images back in or properly edit them with a patch tool for the .9.png files, as long as you have the stock image files in it , there will be no issue with re compiling... you can always add them again later with 7zip or a simmilar program, or by extracting via apk manager
o another thing too is in apk manager i suggest setting compression level to 0 and heap size as 512mb

ldrifta said:
id like to add a tiny piece of info i learned myself lol, the framework-res.apk is very very sensitive while decompiling, so to be sure it re compiles with no issues it needs to be un edited, (png wise) if you added ANY png file to the framework-res.apk file you need to put all the stock images back in or properly edit them with a patch tool for the .9.png files, as long as you have the stock image files in it , there will be no issue with re compiling... you can always add them again later with 7zip or a simmilar program, or by extracting via apk manager
o another thing too is in apk manager i suggest setting compression level to 0 and heap size as 512mb
Click to expand...
Click to collapse
What's the advantage with using heap size of 512MB?

well honestly i think it may be just for larger apk files... but i was having issues with my framewrk-res.apk compiling so i googled the issue and read through hundreds of threads to figure out why, and someone replied on one of the threads saying to change that and compression level to 0 and sure enough it helped me out so i just do it whenever i decompile/recompile framework-res.apk files
it may notbe required for us, but it doesn't hurt anything and i had no issues, but if you can recompile without doing that that do it lol just basically adding my 2 cents haha

Damn. It's not working on GBSense. Already tried the stuff that ldrifta said but that also didn't work.... :/

Rushness said:
Damn. It's not working on GBSense. Already tried the stuff that ldrifta said but that also didn't work.... :/
Click to expand...
Click to collapse
You're work on that? Is it faster?

Its much faster now. As you can see, device ive sent it with.
Sent from my HTC Salsa fake... xD using XDA App

Thank you this worked perfectly, however, i had to use different steps.
I decompile apk with apktool
I only change bool.xml and did not edit arrays.xml
I compiled apk with apktool
I unzipped the compiled apk
I copied from the original apk the META-INF folder to the unzipped new apk
I zipped the file again and it worked

[MOD][SOURCE] Disable lockscreen vibration on any ROM

Here is another solution to disable the lockscreen vibration. Root is needed.
Be careful, you are responsible for everything you do, not me.
Please don't ask, i won't do anything like a graphical interface or else to enable/disable.
This thread was the inspiration: http://forum.xda-developers.com/showthread.php?t=1605363
I dont yet know how to compile the source from this thread, so i searched for another way, baksmalimanager is the solution.
It decompiles and recompiles .jar files and their contents.
Download baksmalimanager
Take the framework.jar from /system/framework/ on the device and place it into the baksmalimanager directory on the pc.
Be sure to remain a backup of this file if something doesn't work.
Then run "baksmali Manager.bat" press 4 to select the framework.jar file and then 1 to decompile it.
Open this directory path inside your baksmalimanager directory framework\com\android\internal\widget\multiwaveview.
Open MultiWaveView.smali in a text editor, search for "setVibrateEnabled" until you find following line, remove it completely:
Code:
invoke-virtual {p0, v11}, Lcom/android/internal/widget/multiwaveview/MultiWaveView;->setVibrateEnabled(Z)V
Save the file. Run "baksmali Manager.bat" again if you closed it. Press 4, select the framework.jar and then press 2 to recompile.
Then open the framework.jar with 7-Zip or something else like that and replace the classes.odex file with the one from the baksmalimanager directory. Think of the backup before you do it.
Then replace the framework.jar in your devices /system/framework/ directory with the modded framework.jar.
Reboot and vibration is gone.
If something doesn't work like expected. Replace with the original framework.jar again.

works great on CM9 ROM latest nightly build for SGS2,,,,,now i can remove the vibra,,,,,thx a lot mate,,,
just suggestion, it's better to include adb.exe and all related files because without it,your program cannot work,,,
And you're now +1 in your thx meter,,,,

A couple of Qs before I replace my old framework.jar:
1.What if I just put '#' before the line I'm supposed delete? Seeing as # is usually a comment and does not affect the code, isn't it the same if I comment it or delete it? I did delete it, i'm just asking out of curiosity...
2.As much as I can understand, you don't need ADB for this, right? The program decompiles the .jar file without it with no problems, at least for me...
You got your thanks
EDIT: Works like a charm on my HTC Desire (SpazeDog's ICS ROM). Finally, the dreaded vibrations have stopped!
Though the answers to the upper questions would be appreciated...

thank you for this, works great on Galaxy Ace with CM9

Thanks Heaps badcrow! Works perfectly on Galaxy S2, CM9.0.0.
1. Tested commenting out the line (with #) and it works perfectly.
2. Doesn't need ADB coz it's working on the file on your PC, not on your phone, just hit any key when baksmali tells you.
Still have vibrate elsewhere, just not on lockscreen. Also, the file I replaced in framework.jar was classes.dex (not .odex).

siganid said:
1. Tested commenting out the line (with #) and it works perfectly.
Click to expand...
Click to collapse
Thanks for confirming, I thought that might happen, but I just didn't want to destroy my phone
siganid said:
2. Doesn't need ADB coz it's working on the file on your PC, not on your phone, just hit any key when baksmali tells you.
Click to expand...
Click to collapse
I really don't want to say this, but; I told you so
As for the other vibrations, see other settings ot other baksmali files and mess with them

on AOSP JellyBean 4.1.1, I had to edit GlowPadView.smali to remove the vibration.
"framework\com\android\internal\widget\multiwaveview"
form this:
Code:
invoke-virtual {p0, v6}, Lcom/android/internal/widget/multiwaveview/GlowPadView;->setVibrateEnabled(Z)V
to this:
Code:
[B]#[/B]invoke-virtual {p0, v6}, Lcom/android/internal/widget/multiwaveview/GlowPadView;->setVibrateEnabled(Z)V
this has worked for me.

im very confused bro...
"replace the classes.odex file with the one from the baksmalimanager directory."
in baksmalimanager directory not file the classes.odex,,,

You 'baksmali' the jar file (de-compile), make the edits you need and 'smali' (compile). Once you do that, you should have a classes.dex (not .odex, but .dex !!) file.
Then just take 7Zip (or winrar, or whatever else can open .jar files) and replace the original classes.dex with the one you 'smali'd'

badcrow said:
Take the framework.jar from /system/framework/ on the device and place it into the baksmalimanager directory on the pc.
Be sure to remain a backup of this file if something doesn't work.
Then run "baksmali Manager.bat" press 4 to select the framework.jar file and then 1 to decompile it.
Open this directory path inside your baksmalimanager directory framework\com\android\internal\widget\multiwaveview.
Open MultiWaveView.smali in a text editor, search for "setVibrateEnabled" until you find following line, remove it completely:
Code:
invoke-virtual {p0, v11}, Lcom/android/internal/widget/multiwaveview/MultiWaveView;->setVibrateEnabled(Z)V
Save the file. Run "baksmali Manager.bat" again if you closed it. Press 4, select the framework.jar and then press 2 to recompile.
Then open the framework.jar with 7-Zip or something else like that and replace the classes.odex file with the one from the baksmalimanager directory. Think of the backup before you do it.
Then replace the framework.jar in your devices /system/framework/ directory with the modded framework.jar.
Reboot and vibration is gone.
If something doesn't work like expected. Replace with the original framework.jar again.
Click to expand...
Click to collapse
Hmmm. Doesn't seem to work for me Maybe I did something wrong. I had to deviate from these steps a little for my phone. Maybe I screwed it up.
I have a deodexed stock rom for Droid 4 running ICS 4.0.4. I actually found this file and line of code in the framework-ext.jar file instead of framework.jar. And, for some reason, baksmali manager wouldn't find the file when I typed 4, unless I renamed the file to framework.jar. Once I did, it found it and decompiled it fine. I changed the code and recompiled, and copied the classes.odex file into the framework.jar file. Then I renamed it BACK to framework-ext.jar. But when I put it back in the system/framework directory, the phone got stuck at the Droid Eye screen on bootup. It just continuously showed it. I had to used adb to push the old file back in place.
Can you just not do it this way? Any ideas? Thanks

How come Baksmali didn't recognize a .jar file? It does, with every version of the name 'framework' I've tried...
BTW, was there even an .dex file inside the .jar file? (de-odexed, kinda sounds like there aren't any more .dex files... just a thought, tho, since I have no idea what that actually means...)
Did you delete the old version of the framework-ext.jar? Or at least rename it (I keep a renamed original copy of the file right there in /system/framework, just in case)?

someone755 said:
How come Baksmali didn't recognize a .jar file? It does, with every version of the name 'framework' I've tried...
BTW, was there even an .dex file inside the .jar file? (de-odexed, kinda sounds like there aren't any more .dex files... just a thought, tho, since I have no idea what that actually means...)
Did you delete the old version of the framework-ext.jar? Or at least rename it (I keep a renamed original copy of the file right there in /system/framework, just in case)?
Click to expand...
Click to collapse
I'm not sure why it didn't recognize the framework-ext.jar file. Was hoping you could tell me Well anyway, it looks like my rename method should work, because all that Baksmali does is extract the file. So, if I gotta rename framework-ext.jar to framework.jar to do the work, and then change it back, it shouldn't matter. And yes the .dex file was in there (and lol nice xP )
I figured out what I did wrong. I replaced the .dex file with 7Zip incorrectly. I couldn't figure out how to place the new .dex file into the .jar file, so I tried clicking "Copy" and changed the destination directory to C:\...\framework-ext.jar. What that did was erase the .jar file, and replaced it with a renamed version of the .dex file. Whoops, haha I later figured out that you can just drag and drop.
Ok, so my phone boots now....Buuuuuuut....the vibration is still there???? The lockscreen still vibrates. Although, the vibration doesn't seem as intense as before. But, it's still there, even if I disable "Vibrate on Touch" in the sound menu.
I checked to make sure that I didn't accidentally put the original framework-ext.jar file into /system/framework/, but I confirmed that I put the modified file in there with the line of code removed, so I'm not crazy Maybe this method just doesn't work completely on my ROM, but I like that the vibration is at least less intense. Thanks so much for the help!

Request for option on CM website
Hi gyus,
thaks for the explanations.
I don't really like to change the code so I requested the option to able or disable vibrations on lock screen on the CM website.
Maybe if we're enough to say it's a good idea, they'll actually program it
Here is the post (as I'm a new member I can't post outside links, repalce underscores by dots)
forum_cyanogenmod_com/topic/59819-request-lock-screen-vibration-option/
If you didn't subscribe, I suggest you do it because there is many many good stuff there too
Bijnok

Thanks!! ...works great on my SGSII..
Sent from my AOKP'd T989

reapsor said:
on AOSP JellyBean 4.1.1, I had to edit GlowPadView.smali to remove the vibration.
"framework\com\android\internal\widget\multiwaveview"
form this:
Code:
invoke-virtual {p0, v6}, Lcom/android/internal/widget/multiwaveview/GlowPadView;->setVibrateEnabled(Z)V
to this:
Code:
[B]#[/B]invoke-virtual {p0, v6}, Lcom/android/internal/widget/multiwaveview/GlowPadView;->setVibrateEnabled(Z)V
this has worked for me.
Click to expand...
Click to collapse
Recently installed CM9 from modpank and encountered this problem, but your version, help me! Thank you!

Just an update on this, if you want this to work on the ICs and JB lockscreen you also need to repeat the process for GlowPadView.smali as well.

4.2.1
Does anyone know how to get it to work on 4.2.1? I tried it 3 different times with no luck.

thats what you get with a new firmware
Ask on the ROM thread, maybe? If there's enough interest, maybe the DEVs will include a setting in the next version...

there‘s no MultiWaveView.smali after decompiling of moto fire xt

What about some info about your ROM...?
Wouldn't that be nice?