Quote:
Originally Posted by ndno
Hey fish, I've been trying to swap out the dialer without luck. I was trying to replace the Phone.apk and Contacts.apk and TelephonyProvider.apk in the system.ext2 but they seem to be dependent on other files in the system.ext2.
I tried replacing them with the Cyanogen dialer *.apks ( [MOD] Contacts.apk & Phone.apk w/ 315x315 callerID ( Eclair 2.1, Froyo AOSP, CM )) but no luck either. I thought it would work since that link mentioned that the packages are compatible with Froyo 2.2.1 AOSP, on which FRX04 is based. It's probably not working because the apks are cross-compiled for another processor different than the one on our TP2.
Oh well, I'll stop for now until I get some time to work more on it. |
I think you have to roll your own system image. Seems easily doable (I have the full build enviro setup) so I can try it tonight. Problem is, then we'll have two system images for FRX04, and my image won't be signed. Really wish we could fix the layout issues with MDPI devices, but without having one I can't really fix anything... Oh well.
Quote:
Originally Posted by tomc585
Like I posted earlier, Went all day (away from airave) without a hicup. So the airave must be doing something to the radio portion that the OS doesnt like. I guess the airave doesnt have the same exact signal as a real cell tower.
I looked but I cant find, can we force roaming with this build?
|
I'm not sure if there is a way to force roaming. Have you tried without your airave? A lot of people have reported issues using the airave - IIRC, the issue was with data only, voice was fine. So perhaps try disabling data when you're around the airave?