Related
Well i tried but i cant get it o work . Want to make shortcut to point to a specific homescreen. Could someone help me?
Set Launcherpro as the default launcher then all you have to do is press the home button. You can also configure it to go to any screen or if on the home screen then it will give you the multi view of all screens to choose from.
Yes i know. .. Thank you for that.But i have the theme from classicalglass going on and on the side. You have there a picture multimedia on my wallpaper on top of that i want to put a blank file that links to screen 6 wich is also multimedia. You kbow what i mean. Ive.tried it the way on launcherpro forum. But it seems to be phone related so that way does not work for me... I hope someone can help me....
Sent from my Intergalactic Supah Dupah Spaceship¡¡!!!
Somebody??????
CODE: SELECT ALL
Action: android.intent.action.MAIN
Package name: com.fede.launcher
Class name: com.fede.launcher.Launcher
And one extra:
Type: Integer
Name: com.fede.launcher.extra.SCREEN
Value: the number of the screen to switch to (from 1 up to the number of homescreens you have set up in LP)
Something like this i mean...
Here u go. Put the extracted lps-file on ur internal memory. Then longpress TS "Shortcuts", "LauncherPro Shortcuts" choose the jump.lps.
Thank you gonna try it tomorrow...
Sent from my Intergalactic Supah Dupah Spaceship¡¡!!!
hi guys
I try to search many times but can not find the way to add more feature HD2's lockscreen ?
Have anyone can help
ex: we just use slide to unlock .
I want we could silde to silent , slide to vibrate ..... could we?
Uploaded with ImageShack.us
Not sure if with stock lockscreen you can somehow add more stuff into .cpr and make it working, but if you get your hands on source code, then you can make anything from it .
OndraSter said:
Not sure if with stock lockscreen you can somehow add more stuff into .cpr and make it working, but if you get your hands on source code, then you can make anything from it .
Click to expand...
Click to collapse
can not find them
and seems no-one tried this zz
no one ?????????????
Maybe using CHome Visual Editor?
xda thread
I know CHome Visual Editor but dont know how to import code
Check the HD2 threads; several months back I definitely remember somebody posting files that increased lockscreen functionality.
Ive been toying around with changing the theme and setting the phone as i like for a while now and im almost content with it apart from three things i cant figure out how to do myself and would like to ask for some help with.
1) In my KF2 rom there is no option to display the SIM contacts (only import from/to SIM), so can someone help enable that?
2) The CRT gets pixelated after using the advanced power menu, there is a better CRT out there that only gets pixelated if you do a screenshot, so if someone knows how can you put in the new CRT in my framework-res.apk or at least remove the buggy one (disable the CRT)? Done.
Ive uploaded a rar with the apks you might need to mod here:
MultiUpload
Thanks to anyone thats willing to help ...
To cut a long story short, private message the people who have created or implemented these into their themes.
Thats just it, i tried asking LitePro but he seams to be away, im not sure who created the better fixed CRT, the transparent lockscreen and i havent seen a contacts apk with display SIM contacts option that would work on KF2 yet...
Have any idea who i can PM? I wouldnt mind donating for future development to anyone whod have the will to help me...
Got transparent lockscreen, can anyone still help with the remaining two?
Heavencry said:
Ive been toying around with changing the theme and setting the phone as i like for a while now and im almost content with it apart from three things i cant figure out how to do myself and would like to ask for some help with.
1) In my KF2 rom there is no option to display the SIM contacts (only import from/to SIM), so can someone help enable that?
2) The CRT gets pixelated after using the advanced power menu, there is a better CRT out there that only gets pixelated if you do a screenshot, so if someone knows how can you put in the new CRT in my framework-res.apk or at least remove the buggy one (disable the CRT)?
Ive uploaded a rar with the apks you might need to mod here:
MultiUpload
Thanks to anyone thats willing to help ...
Click to expand...
Click to collapse
For fix pixelated CRT effect, you have to modify bools.xml in framework-res.apk (decompiled) in /res/values/
change :
Code:
<bool name="config_sf_slowBlur">false</bool>
to
<bool name="config_sf_slowBlur">[B]true[/B]</bool>
and of course :
Code:
<bool name="config_animateScreenLights">true</bool>
to
<bool name="config_animateScreenLights">[B]false[/B]</bool>
If you want, you can enable SIP on data network (3G ...) modifing :
Code:
<bool name="config_sip_wifi_only">true</bool>
to
<bool name="config_sip_wifi_only">[B]false[/B]</bool>
EDIT : I can't fix CRT on your framework-res.apk cause you push .png not declared in public.xml. Give me your original file please
Anyone know how i can enable the show SIM option in contacts?
Last thing im missing on this rom...
@sicopat
Is this really the fix for the pixelated CRT? Have you shared this with Jkay?
The only known solution i knew of was the take a screenshot on a white background.
Noone ever tried enabling show SIM contacts option in KF2 or the older 2.3.3 roms that didnt have it?
Try this one for the crt-fix.
Thank you! That did the trick, the CRT no longer gets pixelated after using the advanced power menu !
Now if only i could figure out a way to get the "show SIM contacts" option... it seams that every Contacts+Dialer.apk i try gives me force closes... are they completely different for each rom version?
Hello guys.
I was recently messing out multiwaveview source, just to see what cool things could I add to my ROM.
It was very easy to notice, that we have there the method that makes lockscreen vibrate, on touch.
So let's stop talking and more modding.
Go to your source tree, and search for
frameworks/base/core/java/com/android/internal/widget/multiwaveview/MultiWaveView.java
With search option (I use gedit, so CTRL+F), look for setVibrateEnabled.
There are plenty of options for removing vibration, the one I use, is setting a boolean to false on constructor method.
Code:
public MultiWaveView(Context context, AttributeSet attrs) {
super(context, attrs);
Resources res = context.getResources();
TypedArray a = context.obtainStyledAttributes(attrs, R.styleable.MultiWaveView);
mOuterRadius = a.getDimension(R.styleable.MultiWaveView_outerRadius, mOuterRadius);
mHorizontalOffset = a.getDimension(R.styleable.MultiWaveView_horizontalOffset,
mHorizontalOffset);
mVerticalOffset = a.getDimension(R.styleable.MultiWaveView_verticalOffset,
mVerticalOffset);
mHitRadius = a.getDimension(R.styleable.MultiWaveView_hitRadius, mHitRadius);
mSnapMargin = a.getDimension(R.styleable.MultiWaveView_snapMargin, mSnapMargin);
mVibrationDuration = a.getInt(R.styleable.MultiWaveView_vibrationDuration,
mVibrationDuration);
mFeedbackCount = a.getInt(R.styleable.MultiWaveView_feedbackCount,
mFeedbackCount);
mHandleDrawable = new TargetDrawable(res,
a.getDrawable(R.styleable.MultiWaveView_handleDrawable));
mTapRadius = mHandleDrawable.getWidth()/2;
mOuterRing = new TargetDrawable(res, a.getDrawable(R.styleable.MultiWaveView_waveDrawable));
// Read chevron animation drawables
final int chevrons[] = { R.styleable.MultiWaveView_leftChevronDrawable,
R.styleable.MultiWaveView_rightChevronDrawable,
R.styleable.MultiWaveView_topChevronDrawable,
R.styleable.MultiWaveView_bottomChevronDrawable
};
for (int chevron : chevrons) {
Drawable chevronDrawable = a.getDrawable(chevron);
for (int i = 0; i < mFeedbackCount; i++) {
mChevronDrawables.add(
chevronDrawable != null ? new TargetDrawable(res, chevronDrawable) : null);
}
}
// Read array of target drawables
TypedValue outValue = new TypedValue();
if (a.getValue(R.styleable.MultiWaveView_targetDrawables, outValue)) {
internalSetTargetResources(outValue.resourceId);
}
if (mTargetDrawables == null || mTargetDrawables.size() == 0) {
throw new IllegalStateException("Must specify at least one target drawable");
}
// Read array of target descriptions
if (a.getValue(R.styleable.MultiWaveView_targetDescriptions, outValue)) {
final int resourceId = outValue.resourceId;
if (resourceId == 0) {
throw new IllegalStateException("Must specify target descriptions");
}
setTargetDescriptionsResourceId(resourceId);
}
// Read array of direction descriptions
if (a.getValue(R.styleable.MultiWaveView_directionDescriptions, outValue)) {
final int resourceId = outValue.resourceId;
if (resourceId == 0) {
throw new IllegalStateException("Must specify direction descriptions");
}
setDirectionDescriptionsResourceId(resourceId);
}
a.recycle();
[COLOR="Red"][B]setVibrateEnabled(false);[/B][/COLOR]
}
But you can also set the method to always return null (or just deleting method and all it's usage, not recommended though if you want to come back some time)
Code:
public void setVibrateEnabled(boolean enabled) {
mVibrator = null;
}
Compile, and voilà, no more damn haptic feedback on lockscreen
TOO Hard for you ?, use ParanoidAndroid, and enjoy of this and some other mods, click my signature .
Which boolean gets called for haptic feedback in let's say trebuchet launcher or the gallery when you long press something like adding a widget on the homescreen because you're trying to move it to another home screen.
is there a difference between setHapticFeedbackEnabled and setVibrateEnabled?? Is it cooked into each and every individual apk or is there one giant key/string/boolean that controls everything?
Basically what I'm getting at is I'm just trying to find a way to disable all forms of haptic feedback. I've decompiled settings.apk, systemui.apk., framework-res.apk, framework.jar, and android policy.jar and have been forking around with that **** for the being learning some new stuff by editing different things here and there and seeing what it does. haha, very primitive but hey, I'm trying to learn everything I can!
Also, do I have to build the app from source to remove haptic feedback from it or can I decompile said apk, edit the certain xml/smali file recompile and voila?
Learning new **** is fun!
rdubyah said:
Which boolean gets called for haptic feedback in let's say trebuchet launcher or the gallery when you long press something like adding a widget on the homescreen because you're trying to move it to another home screen.
is there a difference between setHapticFeedbackEnabled and setVibrateEnabled?? Is it cooked into each and every individual apk or is there one giant key/string/boolean that controls everything?
Basically what I'm getting at is I'm just trying to find a way to disable all forms of haptic feedback. I've decompiled settings.apk, systemui.apk., framework-res.apk, framework.jar, and android policy.jar and have been forking around with that **** for the being learning some new stuff by editing different things here and there and seeing what it does. haha, very primitive but hey, I'm trying to learn everything I can!
Also, do I have to build the app from source to remove haptic feedback from it or can I decompile said apk, edit the certain xml/smali file recompile and voila?
Learning new **** is fun!
Click to expand...
Click to collapse
Each app handles haptic feedback on it's own, gallery, trebuchet, all of them, request for Context.VIBRATOR_SERVICE, wich is the main Service that manages the vibration (Obviously, framework is just the interface that "connects" user actions with kernel and then with hardware). For other side smali is not the best way to code android in general, but it's the same, so you could get the same results as editing java classes. Removing all forms of haptic feedback.. hm.. if i'm not bad, android loads device hardware through some framework service, not actually sure if it's VIBRATOR_SERVICE. So in theory, and pure theory, so dont believe me a word, you could trick android to make it think device doesn't have vibrator. Doing it manually on each app, would be SUCH a huge amount of work, so I definitively don't recommend it.
Good luck!
[MOD][SOURCE] Disable lockscreen vibration on any ROM
Heres another solution, your thread helped much:
http://forum.xda-developers.com/showthread.php?p=28227782
D4rKn3sSyS said:
Each app handles haptic feedback on it's own, gallery, trebuchet, all of them, request for Context.VIBRATOR_SERVICE, wich is the main Service that manages the vibration (Obviously, framework is just the interface that "connects" user actions with kernel and then with hardware). For other side smali is not the best way to code android in general, but it's the same, so you could get the same results as editing java classes. Removing all forms of haptic feedback.. hm.. if i'm not bad, android loads device hardware through some framework service, not actually sure if it's VIBRATOR_SERVICE. So in theory, and pure theory, so dont believe me a word, you could trick android to make it think device doesn't have vibrator. Doing it manually on each app, would be SUCH a huge amount of work, so I definitively don't recommend it.
Good luck!
Click to expand...
Click to collapse
I finally downloaded the CM9 source and compiled an unofficial.zip the other day and was amazing at how easy and simple it was removing haptic feedback from trebuchet launcher as well as the gallery. I can't believe how stupid I was trying to edit smali!
For trebuchet, DragController.java as well as for the gallery2 AlbumPage.java and AlbumSetPage.java solved so easily. VIBRATE_DURATION = 0 + mVibrator.vibrate(0); !!! I'm sure it's not the prettiest or cleanest way of removing vibration but hey, it works! Haha.
There java class UserDictionaryAddWordActivity.java
In the method onCreate:
setContentView (R.layout.user_dictionary_add_word); // Starts a layout
This layout has two buttons cancel and save. // OnClick Cancel and onClickConfirm (android: onClick)
I want to make to the selected word remained immediately without starting the layout.
That is, you need to add in the method onCreate immediately onClickConfirm() and remove setContentView(R.layout.user_dictionary_add_word).
How can I do it?
you mean to have onClickConfirm to not call finish()? it doesn't seem to call it in another thread, so when onClickConfirm executes, you can hook finish(), ignore it when it's called, and unhook it after onClickConfirm
you might need to add the word manually into the layout
Edit: or replace onClickConfirm with your own, where you do the same as the original method does, but without the finish()
gitfib said:
you mean to have onClickConfirm to not call finish()? it doesn't seem to call it in another thread, so when onClickConfirm executes, you can hook finish(), ignore it when it's called, and unhook it after onClickConfirm
you might need to add the word manually into the layout
Edit: or replace onClickConfirm with your own, where you do the same as the original method does, but without the finish()
Click to expand...
Click to collapse
I plan to do so when you click to add a word to the dictionary (if you click on a word not known> Add to Dictionary) without additional clicks. Now onCreate open xml (window with a text field changes the new word and two buttons: Save - onClickConfirm and cancel). And to add an algorithm that if a word has been written with a capital to create a window where we can choose to save a small letter word or a big. It is necessary that when you enter a new proposal, if the word is not a person's name or the name of the city and so on, then you need to save in small letters. ! It is necessary to change the method onCreate or write at all it knitted.
I see. how about replacing R.layout.user_dictionary_add_word resource with your own, which would be invisible by default? until you change visibility of one of its layouts
Yes, it's like this. A visibility layouts unless somehow it is possible to set up?
android:visibility="visible / gone"
and
object.setVisibility(View.GONE);
visible/gone should be fine. do you see how to replace, or should i try myself?
gitfib said:
visible/gone should be fine. do you see how to replace, or should i try myself?
Click to expand...
Click to collapse
I think that if you change the appearance of it will not work.
In the layout we have onClickConfirm, which is to be stored. And if you remove the layout (for a word in small letters), then-layout window is not necessary to call and respectively, we can not perform onClickConfirm.
I understand that it is necessary to onCreate remodel. A change in visibility is not necessary.
If you have any ideas how to do it, you can demonstrate this. This is a good lesson.
Once again, a reference to the Activity https://github.com/CyanogenMod/android_packages_apps_Settings/blob/2703eb717e542ff225611cb9e0217815ee14661c/src/com/android/settings/inputmethod/UserDictionaryAddWordActivity.java
Now I do not know whether it is possible to re-write method onCreate?
at very basic, you can clone the layout, make visibility gone, replace the layout by the clone, and after the layout having being loaded or after onCreate been called - call onClickConfirm
I wouldn't remove the layout because you want to have your own layout on certain cases, and because it would be less messing with the system since UserDictionaryAddWordContents assumes there's a layout