[BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes

[arrrghhh]

Originally Posted by tomc585

I can understand the data portion but how would it cause the reboots?. I'm. Almost home so I'm sure I can replicate the reboot.

Lots of reasons for reboots. If we knew why, they'd probably be fixed .

Some can't be fixed (bad SD card for example) but others we should be able to sort out in time. So much code, so little time...

[fishingmedic]

Arrrghhh, never knew that about Airaves.... Got one sitting next to me right now, lmao... I dropped another reboot log into the testing thread because last night went to bed in android FRX04 and woke up to winmo. It's strange though, doesn't happen all the time. Could you take a look at the log and let me know if you think that's the cause of it?

[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.

[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?

[arrrghhh]

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.

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?

[ndno]

Originally Posted by arrrghhh

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.

Thanks... I think I'll try to build the system.ext2 over the weekend using the instructions on XDAndroid.com. I have my Ubuntu virtual machine set up and I installed all the necessary software, libraries, etc so it's ready to go. I need to pull the Froyo from the GIT repo and play around with it and try to understand it and then maybe I can try replacing the dialer apk.

Looks like you guys are getting over the hump with the NAND flash issue you had this past week. I'm meeting my friend this weekend so he's lend me his cracked-screen TP2. He also has the older TP model; the NAND project you guys have going, will that work with a Sprint TP?

[fishingmedic]

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 appreciate the attempt, but don't kill yourself!!

Originally Posted by arrrghhh

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?

I have an airave which is voice/text only and I have an airvana which is voice/text/data, although I had nothing but problems with the airvana so I D/C'd that and went back to the airave without data, so... I'm not sure if that's the issue or not, although it very well may be just causing mass confusion with the radio, since it's not connecting to a cell tower and uses distant locations for weather, etc (always gives a location nowhere near my house, I live in CT but always shows NY or NJ on weather when I'm in range of the airave).

[arrrghhh]

Originally Posted by ndno

Looks like you guys are getting over the hump with the NAND flash issue you had this past week. I'm meeting my friend this weekend so he's lend me his cracked-screen TP2. He also has the older TP model; the NAND project you guys have going, will that work with a Sprint TP?

Nope, won't work on the TP yet. We're hoping to expand it, but unfortunately not a lot of devs have that device... same with DIAM. Users still want NAND, but very few devs have the device.

[ndno]

Originally Posted by arrrghhh

Nope, won't work on the TP yet. We're hoping to expand it, but unfortunately not a lot of devs have that device... same with DIAM. Users still want NAND, but very few devs have the device.

Thanks. Bt the way, this build is solid as a rock. Combined with wistilt2' test kernel, I can use it all day. I get a reboot to winmo once in a long while but that's pretty much the extent of the problem. Wifi works great; actually when I use wifi I think I get better battery life, probably brcause I'm only getting 1 or 2 bars at my house.


Sent from my FRX04ed TP2

[arrrghhh]

Originally Posted by ndno

Thanks. Bt the way, this build is solid as a rock. Combined with wistilt2' test kernel, I can use it all day. I get a reboot to winmo once in a long while but that's pretty much the extent of the problem. Wifi works great; actually when I use wifi I think I get better battery life, probably brcause I'm only getting 1 or 2 bars at my house.

Ironically, wifi draws less power than 3g... Even if the radio has "full service".

You are going to love WisTilt2's newest kernel... I'm hoping he'll throw me the pack soon .