[MOD] Eclair dialer for AOSP. Easy Install (v1.4.1) [2009-12-16]

ChainsDD · Dec 16, 2009

I've loved the Eclair dialer since the first screen shot I saw, so when the source dropped, I backported it... I'm just finally getting around to posting it. I haven't tested it anywhere but the latest Cyanogen mod, but it should work on any ROM that's based on AOSP. If you have any success installing it, let me know. Use ADB to push it over the old Contacts.apk in /system/app.

With Wysie's help, I've added more features than I'd originally planned to. Here's the latest one I've put together, I'm working on bringing in more of his features, as well as some others I've got planned. Stay tuned for more.

Now has support for T-mobile Visual Voicemail, Google Voice, YouMail, PhoneFusion, and HulloMail.

Also now featuring 'Navigate to' bit in contact details for those with the latest Google Maps.

Fixed self induced bug on keyboard opening. Also trying out a new install method. I was able to just scan the QR below, download, and install straight from my phone. See how it works for you.

Contacts.apk
checksum: 77ab538901e18738711b7213e29cacf5

Changelog:

1.4.1
- Fix for keyboard bug.

1.4
- 'Navigate to' option
- PF Visual Voicemail and HulloMail added.

1.3
- Call log enhancements from Wysie
- Enable/Disable each enhancement in Settings

1.2
- Support for YouMail added
- All in one app
- Only shows options for installed VM handlers
- Added preference screen
- Option to use Voicemail button for voicemail or add to contacts

v1.1.2
- Backported Eclair call log for kewlguru

v1.1.1GV
- Voicemail handler changes to Google Voice.

v1.1.1
- Much better fix for keyboard FC. There's now a landscape dialer screen.

v1.1
- Launch Visual Voicemail (if installed) with voicemail button

v1.0.1
- Fixed FC when opening keyboard (it's crude for now, I'll work on it)
- Made dial and VM buttons do what they're supposed to

v1.0
- Backported the full Eclair dialer layout

xsnipuhx · Dec 4, 2009 at 1:39 AM

Looks nice, but I think everyone uses Visual Voicemail if there on T-Mobile or so I'm lead to believe by the download numbers on Market. Still great work though.

johnnylicious · Dec 4, 2009 at 1:39 AM

will try it right now

thanks!!

mrandroid · Dec 4, 2009 at 1:40 AM

Nice work... Thumbs up.

ChainsDD · Dec 4, 2009 at 1:41 AM

xsnipuhx said:
Looks nice, but I think everyone uses Visual Voicemail if there on T-Mobile or so I'm lead to believe by the download numbers on Market. Still great work though.

I've been considering making the voicemail button check to see if visual voicemail is installed, and launch that instead. Good idea?

DjRevler · Apr 25, 2008 91 2 0

ChainsDD said:
I've been considering making the voicemail button check to see if visual voicemail is installed, and launch that instead. Good idea?

yuuuuuup

xsnipuhx · Dec 4, 2009 at 1:45 AM

ChainsDD said:
I've been considering making the voicemail button check to see if visual voicemail is installed, and launch that instead. Good idea?

YES then I would be all over this!

johnnylicious · Dec 4, 2009 at 1:45 AM

this works perfect on 4.2.5 cyan.

mgorman · Dec 4, 2009 at 1:47 AM

ChainsDD said:
I've been considering making the voicemail button check to see if visual voicemail is installed, and launch that instead. Good idea?

i was thinking that too. is there away so when you click that button it gives you the option to choose an app to open and then you can select visual voice mail app and then every time you hit it your vvm app opens.

ChainsDD · Dec 4, 2009 at 1:55 AM

I'll start integrating Visual Voicemail tomorrow, I'll have it done by the weekend. Should it be automatic, as in if the app is installed it launches that, or should I make it an option?

mgorman · Dec 4, 2009

ChainsDD said:
I'll start integrating Visual Voicemail tomorrow, I'll have it done by the weekend. Should it be automatic, as in if the app is installed it launches that, or should I make it an option?

like i suggested before, you should make it allow the user to select the app because not everyone uses the t-mobile visual voicemail app. I'm sure if you got it to do that devs would start cooking it in their roms.

sidenote: i'm using TheOfficial AOSP rom. can you make this compatible or should it work how it is?

edit: just pushed it. it works on TheOfficial. The voicemail button however does not do anything. Tried long pressing it too.

DjRevler · Apr 25, 2008 91 2 0

automatic

matt_stang · Dec 4, 2009 at 2:07 AM

I use google voice for my voicemail... any chance you could put an option in there for that as well?

Oh and great work! Nice to get a taste of eclair.. and this dialer is pretty cool. Anything else you plan to backport? Like a lockscreen...?

mgorman · Dec 4, 2009 at 2:09 AM

matt_stang said:
I use google voice for my voicemail... any chance you could put an option in there for that as well?

Oh and great work! Nice to get a taste of eclair.. and this dialer is pretty cool. Anything else you plan to backport? Like a lockscreen...?

if he made the option for you to choose then it would work good.

thegreatcity · Dec 4, 2009 at 2:09 AM

I use Google Voice as well. The dialer looks great too.

yrrebnarg · Mar 13, 2006 5 0 0

Force close in landscape

Switching to landscape or using contacts in landscape mode leads to a FC. You might want to be sure it locks itself into portrait mode.

I/WindowManager( 188): Setting rotation to 1, animFlags=1
I/WindowManager( 188): Config changed: { scale=1.0 imsi=0/0 loc=en_US touch=3 keys=2/1/1 nav=3 orien=2 layout=18}
D/PhoneWindow( 782): couldn't save which view has focus because the focused view [email protected] has no id.
D/StatusBar( 188): updateResources
D/AndroidRuntime( 782): Shutting down VM
W/dalvikvm( 782): threadid=3: thread exiting with uncaught exception (group=0x4001e170)
E/AndroidRuntime( 782): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 782): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.DialtactsActivity}: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.TwelveKeyDialer}: java.lang.NullPointerException
E/AndroidRuntime( 782): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2401)
E/AndroidRuntime( 782): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2417)
E/AndroidRuntime( 782): at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:3502)
E/AndroidRuntime( 782): at android.app.ActivityThread.access$2200(ActivityThread.java:116)
E/AndroidRuntime( 782): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1798)
E/AndroidRuntime( 782): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 782): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 782): at android.app.ActivityThread.main(ActivityThread.java:4203)
E/AndroidRuntime( 782): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 782): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 782): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 782): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
E/AndroidRuntime( 782): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 782): Caused by: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.TwelveKeyDialer}: java.lang.NullPointerException
E/AndroidRuntime( 782): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2401)
E/AndroidRuntime( 782): at android.app.ActivityThread.startActivityNow(ActivityThread.java:2242)
E/AndroidRuntime( 782): at android.app.LocalActivityManager.moveToState(LocalActivityManager.java:127)
E/AndroidRuntime( 782): at android.app.LocalActivityManager.startActivity(LocalActivityManager.java:339)
E/AndroidRuntime( 782): at android.widget.TabHost$IntentContentStrategy.getContentView(TabHost.java:631)
E/AndroidRuntime( 782): at android.widget.TabHost.setCurrentTab(TabHost.java:317)
E/AndroidRuntime( 782): at android.widget.TabHost.addTab(TabHost.java:210)
E/AndroidRuntime( 782): at com.android.contacts.DialtactsActivity.setupDialerTab(DialtactsActivity.java:131)
E/AndroidRuntime( 782): at com.android.contacts.DialtactsActivity.onCreate(DialtactsActivity.java:79)
E/AndroidRuntime( 782): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123)
E/AndroidRuntime( 782): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2364)
E/AndroidRuntime( 782): ... 12 more
E/AndroidRuntime( 782): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 782): at com.android.contacts.TwelveKeyDialer.onCreate(TwelveKeyDialer.java:179)
E/AndroidRuntime( 782): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123)
E/AndroidRuntime( 782): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2364)
E/AndroidRuntime( 782): ... 22 more
I/Process ( 188): Sending signal. PID: 782 SIG: 3
I/dalvikvm( 782): threadid=7: reacting to signal 3
I/dalvikvm( 782): Wrote stack trace to '/data/anr/traces.txt'
I/ActivityManager( 188): Process com.android.settings (pid 810) has died.
I/DumpStateReceiver( 188): Added state dump to 1 crashes
D/dalvikvm( 188): GC freed 4244 objects / 310128 bytes in 195ms
I/WindowManager( 188): Setting rotation to 0, animFlags=1
I/WindowManager( 188): Config changed: { scale=1.0 imsi=0/0 loc=en_US touch=3 keys=2/1/2 nav=3 orien=1 layout=18}
D/StatusBar( 188): updateResources
I/Process ( 782): Sending signal. PID: 782 SIG: 9
I/ActivityManager( 188): Process android.process.acore (pid 782) has died.
I/ActivityManager( 188): Killing app com.google.process.gapps (pid 791) because provider com.android.providers.im.ImProvider is in dying process android.process.acore
I/Process ( 188): Sending signal. PID: 791 SIG: 9
I/WindowManager( 188): WIN DEATH: Window{43c88340 com.android.launcher/com.android.launcher.Launcher paused=false}

ChainsDD · Dec 4, 2009 at 2:21 AM

Oops... I'll have a look at that. I use a myTouch, so I completly forgot about the keyboard thing. I'll work out a fix for that before I start on the VM bits. Gonna have to wait 'till tomorrow tho, I gotta be up for work at 4...

ChainsDD · Dec 4, 2009 at 2:23 AM

matt_stang said:
I use google voice for my voicemail... any chance you could put an option in there for that as well?

Oh and great work! Nice to get a taste of eclair.. and this dialer is pretty cool. Anything else you plan to backport? Like a lockscreen...?

As much as I love the 2.0 lockscreen, I think backporting it is a little out of my skillset atm. Changing almost anything in framework-res.apk causes problems with some of the precompiled apps. After I work out the bugs in this and add the VM features, I'll have a look at it tho.

matt_stang · Dec 4, 2009 at 2:28 AM

ChainsDD said:
As much as I love the 2.0 lockscreen, I think backporting it is a little out of my skillset atm. Changing almost anything in framework-res.apk causes problems with some of the precompiled apps. After I work out the bugs in this and add the VM features, I'll have a look at it tho.

I figured it would be quite a difficult task. But if it's possible, it might be worth it. As there's no telling when we'll be able to have a fully functional eclair rom on the dream. So hey, if you're up for it, go ahead and give it a look

bkmo · Dec 4, 2009

The call and voicemail buttons don't do anything on my g1 running cm4.2.7.1

[MOD] Eclair dialer for AOSP. Easy Install (v1.4.1) [2009-12-16]

Retired Recognized Developer

Attachments

Senior Member

Senior Member

Senior Member

Retired Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Retired Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Retired Recognized Developer

Retired Recognized Developer

Senior Member

Senior Member