Originally Posted by jigners
the stock 2.2 alarm clock is more than sufficient for anyones needs for alarms
and the best thing is it works flawlessly (just make sure your time and date is correctly set)
Well..I got the robot voice again. On the first call out..subsequent calls could not even be heard (do not even know if it even went through though the counter was running). How did this happen? Yesterday, after reformatting, reinstalling all (VBN WM ROM and this Droid build) and renaming default.acdb, it was working fine. This morning I decided to power it off and then restart. There the problem came back..again not in the WM ROM phone but in the Droid phone.
FRUSTRATED !..should not be so finicky..in fact for basic stuff, I think the WM ROM (either VBN or the Energy Titanium will do just as well..so may just stick with that until this Droid stuff is sorted out). Seems like lots of folks get this process.com. android.phone errors on other phones (even Samsung Captivate)..and no one seems to know how to fix it..looked up several several boards..the boards dry up after a few posts-g
I got the above error yesterday on repeated tries after the 2nd failure to call out (after the first 'successful' robot voice call). Today? I did not even bother.
BOTTOMLINE..this is too unreliable for something as basic as phone calling. Though I must admit I did not have this problem with the Froyostone 3.2 build. Not once. But the UI was not so slick as this one and needed too many add ons.
so what happens if this suddenly stops one day when I need the phone? Reboot to WM? or it stops during a call..some message boards elsewhere even claimed such things happened.