yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] cytown:
Ok, I think I can take a try.
[G1 Android Development] RK_007:
Ougoing call answered

Hi cytown,

How to know when outgoing call is answered in Android code.Actually I'm developing an application. I need to know when the outgoing call is answered programatically. Can you please help
[G1 Android Development] cytown:
That's internal call api, I do not think you can get such function in common apps.
[G1 Android Development] RK_007:
Thank you Cytown for your quick response. You have done whenever an outgoing call is answered phone vibrates, right..? So, how to get any notification or change in the events or whatever the way it is.. I have to identify that the outgoing call has been answered. Looking for your help.
[G1 Android Development] cytown:
You can check the aosp for Phone and find CallNotifier.java
[G1 Android Development] RK_007:
Sorry to ask this.. but what's aosp..?
[G1 Android Development] redrim:
Android Open Source Project
[G1 Android Development] cytown:
update to v.21
[G1 Android Development] pascanu:
Updated, everything works as expected but I don't see the new icon. (see my signature for details).

[EDIT]: I'm guessing it's something wrong on my side, the apk icon shows correctly in windows (using http://xdaforums.com/showthread.php?t=577735)
[G1 Android Development] daveid:
Any thoughts of adding a whitelist option? I miss that from my old SE M600i. I could set it to only accept calls from one person or a list of people..

Great job.
[G1 Android Development] cytown:
Indeed I do wonder where this icon shown. The only place I know is in task manager and application manager.
[G1 Android Development] cytown:
Maybe a block all but in contacts is easier.
[G1 Android Development] daveid:
That is essentially how it worked. There were three options:

1. Block all (easy)

2. Block all non-phonebook calls (which is what I believe you mean)

3. Block all but those on a specific list <- that's the money option!

But #2 is a great option to have and a giant step towards creating a white-list feature. My only issue with a black list is that you have to know who is calling you that you don't want to, whereas a white list you can set it to only accept calls from certain people - dumping everyone else to vm.
[G1 Android Development] MattKilla:
Hey, uh.. how does one remove a number from the blacklist?? I accidentally added someone while playing with it, and I don't see an option for undoing it.

EDIT: Settings > Call settings > Black List
[G1 Android Development] hamx0r:
i agree with the other white list requests. also, using the concept of a contact group would make this really easy! (instead of adding individuals to a list, we could select a group). If there was a way to easily select a "ring profile" that would be cool too (i.e. Silent (no sound, no vibe), vibe only, ring for all, or ring only for white list)
[G1 Android Development] cytown:
click on the number and will ask you whether want to remove it.
[G1 Android Development] cytown:
Request accepted, will add to TODO list.
[G1 Android Development] daveid:
Thanks.. I love developers like you, if I didn't just write a $6600 check to close on our first house today, I'd donate.. But, I am sure you can understand, after an investment like that, every penny must be pinched till we re-coup our savings..
[G1 Android Development] cytown:
Maybe I should move working to Eclair and stop update for donut.....

If so, the whitelist should be a todo in eclair and never in donut.
[G1 Android Development] connoisseur:
phone.apk force closes

Decided I should post this here as well since I'm not sure whats causes this..
[G1 Android Development] cytown:
Post your log here.
[G1 Android Development] kchau:
this works in dwangs 1.12 now. thanks
[G1 Android Development] Compumyst:
Wondering if you would consider adding an option to the settings to disable the keypad lock in a call. I second the frustration about using automated systems and having the key lock always coming up. As far as preventing accidental keypresses, I'm using "Shake Awake", which seems to work fairly well at waking the phone up when you bring it away from your ear, and does include a cheek guard as well.

Just my .02¢
[G1 Android Development] Wysie:
cytown: From what I know iphone has a proximity sensor, it wasn't done using the acceleromter. :(
[G1 Android Development] Tooke:
v21

Link won't let me download v21. Keeps asking me to re-log-in over and over. all the other links to other versions work fine.
[G1 Android Development] connoisseur:
OK thanks for taking a look for me

heres a logcat from the end of a missed call (no FC) to the second call with FC

now running CM 4.2.5
[G1 Android Development] kyleds:
vibrate

Is there a way to get it to vibrate when you use the keypad for dialing?
[G1 Android Development] Tooke:
Can't install

Running AOSP 1.6 DRD20 rooted base rom. Tells me that it cannot install Dialer. Any ideas? Does it just not work with this rom?
[G1 Android Development] cytown:
I think to disable the keypad is ok, maybe I can make it more inteligent, i.e. when speaker on or ear phone attached, the keypad lock is disabled.
[G1 Android Development] daveid:
I think this would need to be an option. I often am listening to music on my headphones, with my phone in my pocket. If not for the screen being locked, strange things would happen when I take a call. Unless I am confused as to the goal here.
[G1 Android Development] cytown:
You mean up or down? That uses orientation sensor.
[G1 Android Development] cytown:
Looks like not a bug from Phone app, that should because your phone close ContactsProvider unexpected, and Phone app still think there should be ok, and then when retrive the photo of contact, it throws exception:

Contacts.java:485

That should not occur when you have enough memory or ContactsProvider was not killed.

I can not sure it will fixed in Phone app.... I can not repeat the problem..
[G1 Android Development] cytown:
That's part of contacts, not phone app.
[G1 Android Development] cytown:
Dialer is part of Contacts app.
[G1 Android Development] Karboush:
Nice work cytown.

However, I can't get unknown calls blocked.

I've tried "0000" as a number but it doesn't work.

Do you guys know how to make it work?
[G1 Android Development] cytown:
what did it say when unknown calls was call in?

I don't have such call to test.....
[G1 Android Development] Karboush:
Excuse my french.

I was talking about hidden numbers printed.

How can I block it since 0000 doesn't work?
[G1 Android Development] cytown:
I don't really know what you meant.....

You want all calls not in your contacts been blocked? Or just the one who make his number hidden?
[G1 Android Development] Karboush:
I want to block people who hide their number. Is there a wildcard or a specific number to enter for that purpose?
[G1 Android Development] cytown:
If they hide their number, what did it show in call-in screen?
[G1 Android Development] xenio2000:
@cytown

are you using the emulator to test the Phone.apk?

in my theme mod I use this command to test the caller id.

telnet localhost 5554
gsm call +393331234567

5554 is the port of the emulator

I can also check unknown number in this way.

Xenio
[G1 Android Development] Karboush:
"Unknown" is showed on screen

Here is the logcat for a hidden number:

and for a non hidden number:
[G1 Android Development] cytown:
That can not test a hidden number.
[G1 Android Development] cytown:
ok, I got it, I remember I have make it as 0000.... Maybe a bug, I'll check it.
[G1 Android Development] connoisseur:
Thanks for looking into it for me... turned out to be an issue with userinit.sh causing low memory.

A suggestion for your next release... I'm currently running an app called notcalllog which reroutes the phone away from the call log once you finish a call to the dialer or home (your choice). This prevents pocket dialing for me

Having this functionality built in the phone app would be great...
[G1 Android Development] nakeman:
thanks for the apk.

may i ask for a function regarding the call block feature:

is it possible to block by groups; or by a serial of numbers starting with a set of number...(say: 5678**** << all block):D

sorry for my english.
[G1 Android Development] cytown:
In fact, the newest v21 have such feature and option.
[G1 Android Development] Wysie:
cytown: I figured a way we could have higher quality photos without modifying Contacts.apk (since google servers will resize them anyway), and thought i'd let you know.

Basically, we can have some sort of settings page that allows us to link each user to a specific high quality photo, and store this info somewhere. When someone calls, Phone.apk will first check if that person is linked to a photo, and if so, display the photo instead of the one stored in contacts. Else, display the one stored in contacts?

Just a suggestion ;).
[G1 Android Development] cytown:
The phone will fetch Contacts data from ContactsProvider, will store the contents in CallerInfo, which was part of framework/core. If we want better performance, we need to store the data in CallerInfo, but the problem is if we do like this, we must tweak CallerInfo, then we will lose all compatible to other roms beside we tweaked. That's why I can only put organization fetch in seprate thread, and will sure lower the performance.

I do think we can do such tweak, just with the side effect of decrease performance and maybe some uncompatible or not(THE POINT IS HERE).

So, if you really want that tweak, you must know this.

BTW: I find the organization shown can be better performance than now, maybe in Eclair release.
[G1 Android Development] connoisseur:
Not sure if you understood or maybe I got something wrong... phone settings say force return to call log, wherether checked or unchecked, when I make a call it returns to call log (I removed notcalllog to test it). What I'm saying is the option to send it to dialer instead so that you can't redial accidentally. Maybe I got it wrong though??
[G1 Android Development] cytown:
If you check force return to call log, it will return to call log after an outgoing call. If you don't, you will return to the screen before you make a call out.

If you make a call out in call log screen, you will sure return to call log screen, even you checked or unchecked.
[G1 Android Development] xenio2000:
Did you try

gsm call #

that is givin me "unknown" call.

Xenio
[G1 Android Development] cytown:
update to v.22.
[G1 Android Development] acidwashg1:
what is the new layout? do you mean it looks like the dialer by ChainsDD? or is this something completely new?
[G1 Android Development] cytown:
Yes, just like that.
[G1 Android Development] pablizzo:
*wrong thread*
[G1 Android Development] MontAlbert:
edited while trying to figure out whati did to break it

works like a charm now... thanks.
[G1 Android Development] Xauryn:
good app. thats i needed! :D
[G1 Android Development] DJ_Spray:
+1 for desabling the 45sec vibrate function. once this release comes out, I'll install it right away!!

thanks!
[G1 Android Development] DJ_Spray:
double post, sorry
[G1 Android Development] rgv151:
Thank you. OS rules!
[G1 Android Development] cytown:
Upload disable 45sec vibrate version.

Cyanoge, give me your email address and I can send you the diff.
[G1 Android Development] Wysie:
Can't wait for the one with a Settings! cyanogen, will you be releasing that here as well? (out of CyanogenMod) Thanks!
[G1 Android Development] cyanogen:
Yeah, cytown is sending me his code.

My mod is becoming an XDA community project, badass :cool:
[G1 Android Development] Wysie:
Hahaha :P. Good to hear that!
[G1 Android Development] cyanogen:
Merged, added to Settings and pushed to Github!
[G1 Android Development] Wysie:
Great! Now just got to wait for a compiled apk :D. What're the settings available?
[G1 Android Development] cyanogen:
I just made a toggle for the in-call vibrate.
[G1 Android Development] shotad:
can i just click and install instead of writing the command? (when i do mount -o remount,rw /system...i get a permission denied. (are you root?))...
[G1 Android Development] cytown:
You can not do like that, the system app can not be install as normal apps.
[G1 Android Development] shotad:
so i made the /system read/write, tried the command and now it says can't modify Phone.apk....i guess i'll just wait until Cyanogen's new build :p
[G1 Android Development] pistol4413:
same

will just wait for big c to push through the next update. so knowing home shout be stable in bout a week
[G1 Android Development] rkstarnerd:
Try entering the commands in the recovery console. That's how I got it to work. Hope that helps..
[G1 Android Development] lukekirstein:
How would I do this in ADB? Can't seem to get it to work quite right. I get a "The System cannot find the path specified, couldn't get a command to work in Terminal or Recovery.
[G1 Android Development] damme_w:
Hi! really nice!

and the options by cyan is really great too..

now to another feature;

Ive tried to find where the phone-number-layout is formatted, not everyone like the '1-234-567-8900' / '012-345-67890' design, if possible I would love an option to be able to change this.

Thanks!
[G1 Android Development] cytown:
adb remount

adb push Phone.apk /system/app/

You could just try this, but I am not sure it will be ok.
[G1 Android Development] cytown:
That is not based on Phone.apk, it's because of contacts & contacts provider, etc.
[G1 Android Development] Zappletoo:
It depends on the locale you set. If you set it to UK english the dashes will be gone.

That's how I did, and it worked fine.
[G1 Android Development] jrdulog:
Sounds great! Anyone knows if this can coexist with Geesun's Contacts.apk on Dwang? Much appreciated. :cool:
[G1 Android Development] Wysie:
cytown: I've yet to try this out, but you said the dialer layout looks just like ChainsDD? I thought the dialer layout was in Contacts.apk? Please enlighten, thank you :D.

Edit: I get it now. It's the dialer tab that we pull out. :D
[G1 Android Development] oteooo:
hi Cytwon, all,

First of all I would like to say that I really appreciate all the work you all put into this community. I have rooted my phone back in January, and enjoyed the benefits of this forum since then.

Until now I did not have any problems I could not solve by reading, but now I am kind of puzzled. I don't know whether the problem originates from your phone.apk, but it's worth a shot (I am currently running Cyonogen's 4.2.5, which has this phone.apk if i'm not mistaken).

For about 2 months I have been getting these rather strange Android pictures whenever I place a call. Like a base balling android 3d render, a basket balling android 3d render with a advertisement banner on the top of the frame. I place a call and I see the normal call screen for about a second, and then it switches to these render, so I cannot see who I am dialing. And when I hang up, the picture shows back up again, and remains there until I push the home of back button.

it is quite annoying that i cannot see who I am dialing, and I was wondering if this was a feature in your pnone.apk or not. I might be able to live with it if I know this is deliberate to support your work, but I cannot find anything about it on this forum. I am kind of un-organized so I forget who I'm calling quite often, and then I see the picture instead of the dailing screen. I don't really understand the point of this since I am unlikely to push the banner if I am in the middle of making a call?

As mentioned I am using a standard Cyanogen's mod. One other thing that might have to do with it, is my contactmanager, Star Contact. But I get the same behaviour if I use the standard android contact manager, So the only thing I can think of is the dialer itself.

Does anybody know this behaviour and can help me out? And if it is a feature of the dialer, can you perhaps skip the behaviour while dialing?

many thanks in advance,

ote
[G1 Android Development] cytown:
Would you please post the screen shot of your problem here, so that we can take some reference.

If you could, you can flash new rom from cm, i.e. 4.2.7.1.

Personally thought was some thing wrong with your hardware....
[G1 Android Development] oteooo:
Cytown,

Thanks for the quick reply. I already updated through several cyanogen updates (without wiping though..), I think it started somewhere from the version 4.1.9etc. But i will try again and perhaps wipe, if it doesn't work.

I will post some pictures tonight, but it is good to know that it is not normal.

Do you know if it is possible for any installed android app to trigger actions while you dial, perhaps by reading the phone state or something? It just seems a bit weird to me.. I cannot seem to figure out what program it could be then, i don't have anything really exotic installed.

thanks,

ote
[G1 Android Development] oteooo:
Hey all,

Here is a picture of one of the renders I get to see with the banner on the top.

I haven't had the chance to update to the latest Cyanogen, but I will try to do that later tonight.

Perhaps I should try to reflash the telephone firmware too, Or is that nonsense?

(can't really see, how that would help, since I got it straight from htc, but you never know)

regards

ote
[G1 Android Development] xenio2000:
You have installed from the market that crap applications that show an image before and after the call.

Check what you have installed.

Search for Keytel (the developer) maybe you have installed Happy Goodies
[G1 Android Development] pascanu:
I'm having a strange but recurrent problem: incoming call, phone starts vibrating, does not ring, screen lock does not come off, phone freezes adn after a while reboots. I'm not even able to see who called (call not registered in call log). I don't think it's anything related to the ROM, had this problem on dwang's, CM 4.2.7.1 and several WG builds.

Here's some log I was able to pull, don't know if it's relevant, don't even know if the problem relates to this app or not, I'm reverting now to v 201 to see if it goes away.

W/HAL ( 5240): load: module=/system/lib/hw/overlay.trout.so error=Cannot loa
d library: load_library[984]: Library '/system/lib/hw/overlay.trout.so' not foun
d
W/HAL ( 5240): load: module=/system/lib/hw/overlay.msm7k.so error=Cannot loa
d library: load_library[984]: Library '/system/lib/hw/overlay.msm7k.so' not foun
d
W/HAL ( 5240): load: module=/system/lib/hw/overlay.default.so error=Cannot l
oad library: load_library[984]: Library '/system/lib/hw/overlay.default.so' not
found
I/sysproc ( 5240): System server: starting Android runtime.
I/sysproc ( 5240): System server: starting Android services.
I/SystemServer( 5240): Entered the Android system server!
I/sysproc ( 5240): System server: entering thread pool.
I/SystemServer( 5240): Starting Entropy Service.
V/RandomBlock( 5240): reading from file /data/system/entropy.dat
V/RandomBlock( 5240): writing to file /dev/urandom
V/RandomBlock( 5240): reading from file /dev/urandom
V/RandomBlock( 5240): writing to file /data/system/entropy.dat
I/SystemServer( 5240): Starting Power Manager.
I/SystemServer( 5240): Starting Activity Manager.
D/SurfaceFlinger( 5240): pid 5249 requesting gpu surface (current owner = -1)
E/MemoryHeapBase( 5240): error opening /dev/pmem_gpu1: No such file or directory

D/SurfaceFlinger( 5240): pid 5249 requesting gpu surface (current owner = -1)
E/MemoryHeapBase( 5240): error opening /dev/pmem_gpu1: No such file or directory

D/SurfaceFlinger( 5240): pid 5249 requesting gpu core (owner = -1)
E/MemoryHeapBase( 5240): error opening /dev/pmem_gpu1: No such file or directory

W/SurfaceFlinger( 5240): couldn't grant gpu core to pid 5249
D/EGL ( 5249): requestGPU() failed
E/libEGL ( 5249): h/w accelerated eglGetDisplay() failed (EGL_SUCCESS)
I/ARMAssembler( 5249): generated scanline__00000077:03545404_00000A01_00000000 [
30 ipp] (51 ins) at [0x167a8:0x16874] in 640869 ns
I/SystemServer( 5240): Starting telephony registry
I/SystemServer( 5240): Starting Package Manager.
I/Installer( 5240): connecting...
I/installd( 114): new connection
[G1 Android Development] oteooo:
hey Xenio,

thanks! I got it. It wasn't actually an app from keytel, but luckily the app was recommended on the bottom of the androlib site, while browsing through the keytel programs. And sure enough, there were a lot of people complaining in the comments.

It was Diorama, a photo app:

http://www.androlib.com/android.application.jp-co-cybird-android-myphoto-jBp.aspx

When I first encountered the problem, I deleted all the apps I had installed recently, but nothing changed. So I figured (wrongly) it had to do with the cyanogen firmware i had recently installed. Yet I had Diorama installed for a long time before I switched to 4.1.9. This annoying thing slipped through the radar because I merely updated it, and hence wasn't expecting anything like this. Especially because it has nothing to do with the phone whatsoever.

How did you here of this keytel stuff? personal experience or somewhere on the forum?

Anyway, many thanks for the help !

Edit: ah the developer link on androlib does link to the keytel site though.

regards

ote
[G1 Android Development] xenio2000:
I am glad you get your phone back :) enjoy Cytown Phone.apk now...

Xenio
[G1 Android Development] cytown:
I don't really sure that's because of the mod, you can check the following issue:

http://code.google.com/p/cyanogenmod/issues/detail?id=647

You can try install the original Phone.apk without mod and check whether it still happens.
[G1 Android Development] eessel:
hey cytown..

quick question. I asked xenio2000 this question and he told me to refer to you since you're better with the actual writing of java:

So what are your thoughts? Think this is possible and you can work something out? he said said the code there was a 'hidden' button that showed up when it was in use with a device with a green talk/call button on the hardware. so yeah...what do you think?
[G1 Android Development] cytown:
I can not sure, I'll check the code for this segment.

edit: checked, yes, it has such code. would please make a vote for that for how many users like that feature?
[G1 Android Development] eessel:
I for one would like that feature! lol :p
[G1 Android Development] albertazzi65:
is good for Motorola Droid Milestone? thanks
[G1 Android Development] cytown:
Not yet, it's for 1.6 donut only.
[G1 Android Development] pascanu:
I've reverted to v 201 and the issue has gone away, been using it for more than 2 days now and I'm pretty sure it's gone. Are there any changes/differences that you can think of that may cause this issue? (just curious, I'm more than happy with v201).
[G1 Android Development] cytown:
I'll check the code, pls test it more.
[G1 Android Development] xenio2000:
Hey Cytown,

for who wants the answer button on screen, I did the tweak to the Phone.apk

could you check it? and if you like you could improve the code and maybe add a end call button?

I have changed the "double tap" to a single tap, I like it.

the thread http://xdaforums.com/showthread.php?p=5133187#post5133187

and the screenshot

Thanks

Xenio
[G1 Android Development] shinta4e:
nice

any plans on making this functional on the droid?
[G1 Android Development] cytown:
Looks good.

No End button? Strange.....
[G1 Android Development] cytown:
Yes, the plan in due. Just wait for the complete aosp rom of eclair is released.
[G1 Android Development] xenio2000:
I found in the code only the "answer" that was there to show only for device with NO hardware green button, I changed from double tap to single tap and reskinned, but I did not found any code for the end call button.

I this case, now it is your turn.... ehehehheheh

Thanks Cytown.

Xenio.
[G1 Android Development] the.purple.engineer:
Haptic Feedback?

Hi Cytown,

Love the app. I just had one question.

Can you add "haptic feedback" to phone app where it would vibrate when you press the onscreen number keypad to dial?

I always found it odd that keyboard has haptic feedback yet the dialer does not.

Thanks
[G1 Android Development] cytown:
I'll check the codes.
[G1 Android Development] cytown:
Now I upload the original aosp Phone.apk, you can take this if you like:)