I have an idea for an app that extends the default google search.
When you press the search button and search for a contact or app, each result will be long pressable so that you can drag the result to your desktop as a shortcut.
This will be a nice and easy way to create shortcuts to apps/contacts rather than finding them in the drawer/contact list.
Has this already been done ? Since CM7 allows the search target app to be customizable it seems do-able.
There are two things you can do with the Search button:
1. Open an internal search for your App data when you App is running and on top
2. Run your App when you long press the search button at any moment even when you are on other apps.
For the first option see the links:
http://developer.android.com/resources/articles/qsb.html
http://developer.android.com/resources/samples/SearchableDictionary/index.html
For the second option, which I understand that is what you wanted to do, you have to add to your Androidmanifest.xml the following intent filter:
Code:
<intent-filter>
<action android:name="android.intent.action.SEARCH_LONG_PRESS" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
Independently to these two options, another thing you may be interested in, is to add your App data to the global search (quick search box), like a dictionary App would do:
Code:
<searchable xmlns:android="http://schemas.android.com/apk/res/android"
android:label="@string/search_label"
android:searchSettingsDescription="@string/settings_description"
android:includeInGlobalSearch="true"
android:searchSuggestAuthority="dictionary"
android:searchSuggestIntentAction="android.intent.action.VIEW">
</searchable>
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
mminbcn said:
There are two things you can do with the Search button:
1. Open an internal search for your App data when you App is running and on top
2. Run your App when you long press the search button at any moment even when you are on other apps.
For the first option see the links:
http://developer.android.com/resources/articles/qsb.html
http://developer.android.com/resources/samples/SearchableDictionary/index.html
For the second option, which I understand that is what you wanted to do, you have to add to your Androidmanifest.xml the following intent filter:
Code:
<intent-filter>
<action android:name="android.intent.action.SEARCH_LONG_PRESS" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
Independently to these two options, another thing you may be interested in, is to add your App data to the global search (quick search box), like a dictionary App would do:
Code:
<searchable xmlns:android="http://schemas.android.com/apk/res/android"
android:label="@string/search_label"
android:searchSettingsDescription="@string/settings_description"
android:includeInGlobalSearch="true"
android:searchSuggestAuthority="dictionary"
android:searchSuggestIntentAction="android.intent.action.VIEW">
</searchable>
Click to expand...
Click to collapse
Thanks, it indeed is the quick search i'm talking about.
I believe that most apps are searchable by default by their names.
I want to add long press functionality to the search results so I can add a shortcut directly from the search results instead of scrolling though the app-drawer looking for the app and then creating a shortcut.
I think this would be a good time saver.
Edit: Just realized I posted this in the wrong forum, mods please feel free to move it to the General forum...my bad.
Hey guys,
So maybe somewhere here has an answer for this problem I'm having. I downloaded a custom lockscreen app (Simply Lockscreen), and it works great except for one major flaw: Upon booting/rebooting the phone, the lockscreen defaults to the system HTC Sense lockscreen. Now, as soon as I launch the app from the app drawer, the Sense lockscreen goes away and Simply Lockscreen loads up evey time just fine. But whenever I turn off the phone and reboot, the Sense lockscreen returns and I can't use the custom lockscreen until I manually launch it from the App drawer.
I downloaded System Tuner Pro and tried a few different things, including making sure Simply Lockscreen was marked as a "startup app" (which it was), disabling HTC Lockscreen as a startup app, disabling Rosie as a startup app, and finally (after none of the previous actions helped), uninstalling the HTC Lockscreen system app entirely. Unfortunately, after I did this, rather than Simpy Lockscreen popping up after boot, all I got was the Android default lockscreen (which I didn't even know existed on my phone but was apparently buried under Sense).
My question is, is there anything else I can do that may get my Simply Lockscreen custom lockscreen app to load on boot as the default lockscreen? Or is this 'simply' an app-related issue that only the developer can solve? I'm beginning to think it is, as I've downloaded and used other custom lockscreen apps in the past which have loaded up fine upon reboot (namely Go Locker). The only reason I'd like to stay with Simply Lockscreen is because of the really cool Honeycomb theme it has and the sheer number of features it allows you to enable on the lockscreen.
Before you ask, I'm running XBoarder's BulletProof v2.5 with Faux's latest kernel.
Thanks in advance for any advice!
Issue resolved. Found the bit of code i needed HERE
in AndroidManifest.xml (application-part):
<receiver android:enabled="true" android:name=".BootUpReceiver"
androidermission="android.permission.RECEIVE_BOOT_COMPLETED">
<intent-filter>
<action android:name="android.intent.action.BOOT_COMPLETED" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</receiver>
[..]
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
[..]
public class BootUpReceiver extends BroadcastReceiver{
@Override
public void onReceive(Context context, Intent intent) {
Intent i = new Intent(context, MyActivity.class);
i.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
context.startActivity(i);
}
}
Click to expand...
Click to collapse
Bling_Diggity said:
Edit: Just realized I posted this in the wrong forum, mods please feel free to move it to the General forum...my bad.
Click to expand...
Click to collapse
Done.
are you letting your device load completely before using it? i say that because the default lockscreen will always show up on boot until the replacement loads. i use mi locker and it doesnt show the replacement screen immediately, but wait a minute or so and it should load
0. INTRO
One of the only things I like about the US firmwares for our phones is that the dialer actually looks normal. Those of you using Hellraiser on int'l firmwares have probably thought wtf is this fugly mess? It just drives me crazy, so I decided to write a guide to removing the video call icon, and decribe the basics of modding the dialer layout. This is not particularly advanced, but I'm not getting into any apktool specifics, so you will need to be comfortable with that before you try this.
First things first, thank you to jivy26 and dully79 for helping me out with this! And of course to Brut.alll for apktool.
Let's take a close look at this thing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yup, you're supposed to make a call with that. Or a video call. Or a text message. Especially text message, because if you hit the menu button, you're presented with another way to text: 'Send message'.
</rant>
1. GET RID OF VIDEO CALL ICON
I don't think there's any way to activate it in the US, so let's get rid of it.
a. Get a clean copy of Contacts.apk from your favorite i9100 firmware. The one I'm using is from XWKL1.
b. Decompile.
c. Open up res/layout/dialer_app.xml in a text editor.
d. We will be working in the last LinearLayout entry, find it.
e. We will use android:visibility="gone" to get rid of the icon. You can see that voicemailbutton is hidden by default.
Code:
<LinearLayout android:orientation="horizontal" android:id="@id/dialbuttonset" android:layout_width="314.0dip" android:layout_height="54.669983dip" android:layout_marginTop="2.6599731dip">
<ImageButton android:id="@id/voicemailbutton" android:background="@drawable/call_dial_btn06" android:visibility="gone" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_voicemail_icon" />
<ImageButton android:id="@id/callbutton" android:background="@drawable/call_dial_btn01" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_outgoingcall_icon" android:scaleType="fitXY" android:contentDescription="@string/call" />
<ImageButton android:id="@id/videocallbutton" android:background="@drawable/call_dial_btn02" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_contacts_icon" android:scaleType="fitXY" android:contentDescription="@string/video_call" />
<ImageButton android:id="@id/messagebutton" android:background="@drawable/call_dial_btn03" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_message_icon_04" android:scaleType="fitXY" android:contentDescription="@string/message" />
<ImageButton android:id="@id/imageclear" android:background="@drawable/call_dial_btn06" android:nextFocusLeft="@id/messagebutton" android:nextFocusRight="@id/callbutton" android:layout_width="63.0dip" android:layout_height="52.899994dip" android:layout_marginLeft="6.0dip" android:layout_marginTop="1.0dip" android:src="@drawable/call_clear_btn_04" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
<ImageButton android:id="@id/messagebutton_novt" android:background="@drawable/call_dial_btn05" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_message_icon_03" android:scaleType="fitXY" android:contentDescription="@string/message" />
<ImageButton android:id="@id/imageclear_novt" android:background="@drawable/call_dial_btn06" android:layout_width="98.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_clear_btn_03" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
</LinearLayout>
f. Modify the relevant line by adding android:visibility="gone"
Code:
<ImageButton android:id="@id/videocallbutton" android:background="@drawable/call_dial_btn02" [COLOR="Blue"]android:visibility="gone"[/COLOR] android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_contacts_icon" android:scaleType="fitXY" android:contentDescription="@string/video_call" />
If you were to compile this now, it would look like this:
Got rid of the video call button, but we've introduced new fugliness courtesy of messagebutton_novt and imageclear_novt. I'm really not sure what those are, but they were "next in line" in our layout, and removing videocallbutton revealed them.
2. GET RID OF _NOVT BUTTONS
Who knows what these are, but the last thing we need is more buttons down here.
a. Apply android:visibility="gone" to the relevant lines:
Code:
<ImageButton android:id="@id/messagebutton_novt" android:background="@drawable/call_dial_btn05" [COLOR="Blue"]android:visibility="gone"[/COLOR] android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_message_icon_03" android:scaleType="fitXY" android:contentDescription="@string/message" />
<ImageButton android:id="@id/imageclear_novt" android:background="@drawable/call_dial_btn06" [COLOR="Blue"]android:visibility="gone"[/COLOR] android:layout_width="98.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_clear_btn_03" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
If you were to compile it at this point, it would look like this:
Getting warmer.
3. CHANGE THE ORDER
I want to have the call button in the middle, so we have to move it.
a. Swap the order of the entries so callbutton is between messagebutton and imageclear
Code:
<LinearLayout android:orientation="horizontal" android:id="@id/dialbuttonset" android:layout_width="314.0dip" android:layout_height="54.669983dip" android:layout_marginTop="2.6599731dip">
<ImageButton android:id="@id/voicemailbutton" android:background="@drawable/call_dial_btn06" android:visibility="gone" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_voicemail_icon" />
<ImageButton android:id="@id/videocallbutton" android:background="@drawable/call_dial_btn02" android:visibility="gone" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_contacts_icon" android:scaleType="fitXY" android:contentDescription="@string/video_call" />
<ImageButton android:id="@id/messagebutton" android:background="@drawable/call_dial_btn03" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_message_icon_04" android:scaleType="fitXY" android:contentDescription="@string/message" />
[COLOR="Blue"] <ImageButton android:id="@id/callbutton" android:background="@drawable/call_dial_btn01" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_outgoingcall_icon" android:scaleType="fitXY" android:contentDescription="@string/call" />[/COLOR]
<ImageButton android:id="@id/imageclear" android:background="@drawable/call_dial_btn06" android:nextFocusLeft="@id/messagebutton" android:nextFocusRight="@id/callbutton" android:layout_width="63.0dip" android:layout_height="52.899994dip" android:layout_marginLeft="6.0dip" android:layout_marginTop="1.0dip" android:src="@drawable/call_clear_btn_04" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
<ImageButton android:id="@id/messagebutton_novt" android:background="@drawable/call_dial_btn05" android:visibility="gone" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_message_icon_03" android:scaleType="fitXY" android:contentDescription="@string/message" />
<ImageButton android:id="@id/imageclear_novt" android:background="@drawable/call_dial_btn06" android:visibility="gone" android:layout_width="98.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_clear_btn_03" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
</LinearLayout>
So, here's what it would look like now:
Just have to align it
4. ALIGN IT
So there's many things you could do now. Stretching the message and clear icons to be the same width as the call button by setting android:layout_width="98.66998dip"would result in:
To fix the stretching, you could modify the referenced images. But for simplicity's sake, we are just going to pad the margins so that everything lines up.
a. change the margin of messagebutton to 41.66998dip.
Code:
<ImageButton android:id="@id/messagebutton" android:background="@drawable/call_dial_btn03" android:layout_width="63.0dip" android:layout_height="54.669983dip" [COLOR="Blue"]android:layout_marginLeft="41.66998dip"[/COLOR] android:src="@drawable/call_message_icon_04" android:scaleType="fitXY" android:contentDescription="@string/message" />
b. Wait, where did that number come from??
c. Since we want everything to line up, it's easy to figure out how far to "push" the message button to the left by looking at the layout of the number area of the dialpad in our xml.
Each button is 98.66998dip wide, preceded by a 6.0dip margin.
messagebutton is 63.0dip wide.
98.66998-63.0==35.66998
Add the original 6.0dip for the left margin==41.66998d. SIDE NOTE: If you are a perfectionist, you can also make 2 small changes to the imageclear entry at this point to bring the layout in line with the rest of the buttons.
i. Remove the section in red (below) from the imageclear entry. (No other button has a top margin)
ii. Change the android:layout_height to 54.669983dip, which is what the rest of the buttons use. I can't imagine why only this button would need a tiny top margin, and smaller height, making it a tiny bit smaller than all the rest of the buttons. Samsung goofiness.
Code:
<ImageButton android:id="@id/imageclear" android:background="@drawable/call_dial_btn06" android:nextFocusLeft="@id/messagebutton" android:nextFocusRight="@id/callbutton" android:layout_width="63.0dip" [COLOR="Blue"]android:layout_height="54.669983dip"[/COLOR] android:layout_marginLeft="6.0dip" [COLOR="Red"]android:layout_marginTop="1.0dip"[/COLOR] android:src="@drawable/call_clear_btn_04" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
e. Our final, modified section of xml will look like this:
Code:
<LinearLayout android:orientation="horizontal" android:id="@id/dialbuttonset" android:layout_width="314.0dip" android:layout_height="54.669983dip" android:layout_marginTop="2.6599731dip">
<ImageButton android:id="@id/voicemailbutton" android:background="@drawable/call_dial_btn06" android:visibility="gone" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_voicemail_icon" />
<ImageButton android:id="@id/videocallbutton" android:background="@drawable/call_dial_btn02" android:visibility="gone" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_contacts_icon" android:scaleType="fitXY" android:contentDescription="@string/video_call" />
<ImageButton android:id="@id/messagebutton" android:background="@drawable/call_dial_btn03" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="41.66998dip" android:src="@drawable/call_message_icon_04" android:scaleType="fitXY" android:contentDescription="@string/message" />
<ImageButton android:id="@id/callbutton" android:background="@drawable/call_dial_btn01" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_outgoingcall_icon" android:scaleType="fitXY" android:contentDescription="@string/call" />
<ImageButton android:id="@id/imageclear" android:background="@drawable/call_dial_btn06" android:nextFocusLeft="@id/messagebutton" android:nextFocusRight="@id/callbutton" android:layout_width="63.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_clear_btn_04" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
<ImageButton android:id="@id/messagebutton_novt" android:background="@drawable/call_dial_btn05" android:visibility="gone" android:layout_width="98.66998dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_message_icon_03" android:scaleType="fitXY" android:contentDescription="@string/message" />
<ImageButton android:id="@id/imageclear_novt" android:background="@drawable/call_dial_btn06" android:visibility="gone" android:layout_width="98.0dip" android:layout_height="54.669983dip" android:layout_marginLeft="6.0dip" android:src="@drawable/call_clear_btn_03" android:scaleType="fitXY" android:contentDescription="@string/description_delete_button" />
</LinearLayout>
f. Compile and push to phone and it should look like this:
flashable VRTheme for i9100 firmwares!
This flashable VRTheme does the following:
1) Removes video call button.
2) Centers call button.
3) Replaces .pngs so that icons are not stretched.
Install:*
0) For international (i9100) 2.3.x firmwares only! Make sure the Contacts.apk is unthemed (stock).
1) Copy US_dialer_VRTheme.zip and VRTheme-Restore-Backup-v0.3.6.zip to your sdcard. Different kernels/versions of CWM recovery mount sdcard differently, so you might have to put it in sdcard/external_sd.
2) Flash from recovery.
3) Reboot. This wipes dalvik so please be patient. First boot can take 5 mins. or more.
*Tested on XWKL1 and XILA2 firmwares. It should work with almost any firmware version b/c the VRTheme just replaces the parts of the apk pertaining to the dialer. For unthemed ROMs only! If your ROM has a themed dialer, this will mess up the theme.
Revert:
0) The zip will automatically create a vrtheme-backup folder in the root of your sdcard in case something goes wrong.
1) Flash VRTheme-Restore-Backup-v0.3.6.zip from recovery.
If this works for people, please let me know what firmware you are on and I'll update the post with confirmed working versions.
NOTE: My phone is themed, so your tabs will look different (stock) as compared to the screenshot!
Thanks to:
VillainROM team for making this useful tool: http://forum.xda-developers.com/showthread.php?t=1207017
D.O.C. for modifications and restore scripts
screenshot:
Hopefully some devs will replace the default dialer. I would take a crack at it, but I have no experience. Tempting, however...
Going to give this a try now, thanks!
Ugh getting a bunch of compile errors, maybe cause its too late for me doing this...
Worked very nicely on LA4, awesome work my friend.
yoderk said:
Worked very nicely on LA4, awesome work my friend.
Click to expand...
Click to collapse
Great! I checked the xml against a couple of other firmwares and that part was all the same so I thought it should work. Good to have confirmation though.
AndAllThingsWillEnd said:
Hopefully some devs will replace the default dialer. I would take a crack at it, but I have no experience. Tempting, however...
Click to expand...
Click to collapse
Now you can do it yourself! Flashable zip in post 2.
Awesome! Thanks so much!
Sent from my AT&T cellular device.
Tried the zip file on xila3 and it did not remove video button. Also tried manually and failed last night. I will try manually again today. Can anyone upload the xila2 or xla4 stock contacts with this done already? I also tried grabbing the xila2 contacts from lilrom to see if i could modify it but then i lose the phone and contact buttons completely.
If someone else has better luck here is the stock contacts.apk for xila3 firmware. I still am not having any luck with getting rid of that damned video call button. http://db.tt/Fg3emi5O
Also here is my modified xila3 contacts.apk that i have already got most the things working except getting rid of the video button and resizing the buttons. The layout/dialer.app just doesn't open up correctly on notepad++ or on my phone. Same thing either way. I tried starting a layout/dialer.app from scratch but then i get a acore.process error and force close when i try to open the dialer after making the changes. http://db.tt/7KmD3fM4
Sent From My KickAss ATT SGS2 SPORTING CM7
RockRatt said:
Tried the zip file on xila3 and it did not remove video button. Also tried manually and failed last night. I will try manually again today. Can anyone upload the xila2 or xla4 stock contacts with this done already? I also tried grabbing the xila2 contacts from lilrom to see if i could modify it but then i lose the phone and contact buttons completely.
If someone else has better luck here is the stock contacts.apk for xila3 firmware. I still am not having any luck with getting rid of that damned video call button. http://db.tt/Fg3emi5O
Also here is my modified xila3 contacts.apk that i have already got most the things working except getting rid of the video button and resizing the buttons. The layout/dialer.app just doesn't open up correctly on notepad++ or on my phone. Same thing either way. I tried starting a layout/dialer.app from scratch but then i get a acore.process error and force close when i try to open the dialer after making the changes. http://db.tt/7KmD3fM4
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
Something is up. I tried to have a look at your modified apk and got an error saying archive could be damaged. Anyway, here's the XILA3 modded for you. I didn't use the apk from your link, so maybe there's something wrong with that file. idk anyway, enjoy
stone_ship said:
Something is up. I tried to have a look at your modified apk and got an error saying archive could be damaged. Anyway, here's the XILA3 modded for you. I didn't use the apk from your link, so maybe there's something wrong with that file. idk anyway, enjoy
Click to expand...
Click to collapse
A BIG THANKS for the help. I will add a link to your thread with a Thanks on my CobraRom Post. Wish I knew where I was messing up though. Here is the finished detail I was going for Thanks to you I am happy with it. Now to start messing with the Phone.ask file. Thanks again Rich
Sent From My KickAss ATT SGS2 SPORTING CM7
Stone_Ship since you know better than I, do you know where/what file I need to change to get rid of the phone.apk? Video call button as seen kn screen shot? I can deal with the first screenshot of the incall dialer but after I hit end call the second screen comes up that I would like to remove or change. I have been able to modify it to exactly my liking without the video call button and such and it works fine except when it goes back to the dialer i get a process.phone error and I lose my signal for a few seconds. Hope you can point me in the right direction.
Sent From My KickAss ATT SGS2 SPORTING CM7
RockRatt said:
Stone_Ship since you know better than I, do you know where/what file I need to change to get rid of the phone.apk? Video call button as seen kn screen shot? I can deal with the first screenshot of the incall dialer but after I hit end call the second screen comes up that I would like to remove or change. I have been able to modify it to exactly my liking without the video call button and such and it works fine except when it goes back to the dialer i get a process.phone error and I lose my signal for a few seconds. Hope you can point me in the right direction.
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
How did you get rid of the video call button? I tried the android:visibility=gone trick on endcall_buttons_view.xml but it did nothing. On the other hand, it didn't FC either. Let me know what you did and I'll try it out.
stone_ship said:
How did you get rid of the video call button? I tried the android:visibility=gone trick on endcall_buttons_view.xml but it did nothing. On the other hand, it didn't FC either. Let me know what you did and I'll try it out.
Click to expand...
Click to collapse
I am not sure how I got rid of the video call button from the first screen shot, I just changed out some of the icons with matching names but different pictures and then the video buttons would be gone. But then i would get the force close once i end the call. With the pics above where it still has the second screen with the video call button and the first screen without it I do not get a force close. Again I just have been trying to swap out some of the .png files is all. I can upload two different apk files if that would help. One with EVERYTHING I want it to be like without any video call buttons but the force close, and the other as the screen shots above that I get NO force closes after endimg call.
NoForceclose but has video button:
http://db.tt/kXzPVtbg
Like But Has force close after call.
http://db.tt/bL5VP5eo
Sent From My KickAss ATT SGS2 SPORTING CM7
RockRatt said:
I am not sure how I got rid of the video call button from the first screen shot, I just changed out some of the icons with matching names but different pictures and then the video buttons would be gone. But then i would get the force close once i end the call. With the pics above where it still has the second screen with the video call button and the first screen without it I do not get a force close. Again I just have been trying to swap out some of the .png files is all. I can upload two different apk files if that would help. One with EVERYTHING I want it to be like without any video call buttons but the force close, and the other as the screen shots above that I get NO force closes after endimg call.
NoForceclose but has video button:
http://db.tt/kXzPVtbg
Like But Has force close after call.
http://db.tt/bL5VP5eo
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
I tested both files on my phone running KL1 and neither gives me FCs. Like But Has Force Close doesn't even go to that Call ended screen. Kinda neat. Are your permissions messed up? They should be 644 (rw-r--r--).
I think you already have what you want in your hands, but just have to figure out where the problem is. Maybe fresh install from an unmodified firmware base?
stone_ship said:
I tested both files on my phone running KL1 and neither gives me FCs. Like But Has Force Close doesn't even go to that Call ended screen. Kinda neat. Are your permissions messed up? They should be 644 (rw-r--r--).
I think you already have what you want in your hands, but just have to figure out where the problem is. Maybe fresh install from an unmodified firmware base?
Click to expand...
Click to collapse
Ya I have put them in system/app with the correct rw/r/r and also just pushed them in without changing permissions then rebooted each time. I have run fix permissions from recovery and also tried via Rom manager also. I downloaded wanamlites version and started from scratcb and also sammys released version also, flashed it via mobile odin, put root explorer back on and pulled the whole system file, then started from scratch. I do not get the force close when i make a call but once i hit end call the screen sticks for a few seconds, then I get a popup that says force close. It loses cell signal completely for a few seconds then cell signal comes back on.
After reading your last message I tried tow other things also, one was to try and edit with notepad++ the endcall.view.xml to visibility=gone and also I totally deleted out the endcall_buttons_view.xml and endcall_buttons_view_land.xml which worked to completely get rid of the extra screen and went right back to the dialer but still gave the process.phone error message. Thanks for trying with me. I will keep testing it out.
Sent From My KickAss ATT SGS2 SPORTING CM7
Something strange is definitely going on. I did make a couple of test calls with no FCs. You can try running ddms to see if you can see what's causing the errors. I'm not very good at reading those, but if you post it, I bet someone can help.
Well i took the one I like already, went in and edited the endcall_button_view.xml for visibility=gone and tben zipped it back up. Applied it, then recreated my rom and installed the rom and nkw so far I am not getting the force close issue I was having. Weird, so far it works pretty much as I put the links to you above. I will test it out a bit more and see how it goes. THANKS again for the help and ideas.
Sent From My KickAss ATT SGS2 SPORTING CM7
Glad it worked out for you. Sounds like you basically short circuited the app so it can't show the call ended screen.
stone_ship said:
Glad it worked out for you. Sounds like you basically short circuited the app so it can't show the call ended screen.
Click to expand...
Click to collapse
I kind of like the way it turned out, thanks for the help and guidance man! I posted a link in the OP to point to your post. Thanks again, Rich
Sent From My KickAss ATT SGS2 SPORTING CM7
Is it possible to make any app a QSlide app either with or without a rooted device?
Good question. Would like to know this too. Same with dual window. Not all apps can be used with that either. Good thing itll be a native feature with android n.
TheJOJ said:
Is it possible to make any app a QSlide app either with or without a rooted device?
Click to expand...
Click to collapse
Needs something like this added to its manifest
Permission to overdraw added to it
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW" />
It needs to be made selectable within qslide
<application android:theme="null" android:label="App name" android:icon="app's data path to its icon.png"
Then made viewable in the launcher
<uses-library android:name="com.lge.app.floating" android:required="false" />
<activity android:label="App name" android:name="App name">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
No simple drag n drop method can add apps to qslide but possibly a batch editor could be made one day to pull it off on the fly...one day.