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

[sureshot007]

So this is my first experience with android in general. I noticed that the gmail app is set to push. The email app won't let you configure gmail via exchange like I can in wm. What I really want is to be able to schedule email syncing for every X minutes, and to disable syncing between midnight and 7am (so I can sleep without hearing it buzz in the middle of the night). This is a simple schedule change on wm, but I can't figure out how to do it in android.

[arrrghhh]

Originally Posted by sureshot007

So this is my first experience with android in general. I noticed that the gmail app is set to push. The email app won't let you configure gmail via exchange like I can in wm. What I really want is to be able to schedule email syncing for every X minutes, and to disable syncing between midnight and 7am (so I can sleep without hearing it buzz in the middle of the night). This is a simple schedule change on wm, but I can't figure out how to do it in android.

Exchange and push are basically the same thing.

I don't see a way to do this either, perhaps if you use k9mail? I think that requires that you use IMAP tho.

Seems there isn't a solution. Found a bug (well, 'issue') googling this problem straight away...

[sureshot007]

Originally Posted by arrrghhh

Exchange and push are basically the same thing.

I don't see a way to do this either, perhaps if you use k9mail? I think that requires that you use IMAP tho.

Seems there isn't a solution. Found a bug (well, 'issue') googling this problem straight away...

Exchange and Push are not the same thing.

Looks like I'm staying with wm6 for a while then.

[arrrghhh]

Originally Posted by oisact

I ran FRX04 for a couple weeks, and at most I had a full restart (back to WM) once a day. Seemed to be one a day fairly consistent. I dropped in the FRX05 system.ext2 and have had more resets. Today I've had 4-5 so far, so I'm going to drop back down to FRX04 to see if that is still stable. The resets are totally random - I'll look over and the phone will be resetting, or I'll be using it and it will spontaneously reset. I have a hunch it has to do with wireless connectivity. It seems to act up more when I'm in spotty coverage areas.

I did not upgrade kernels from FRX04. Could that be part of my stability issue with the FRX05 system.ext2?

You should upgrade everything - kernel, rootfs and system image. Hence the reason I make bundles, so people can just grab those .

Originally Posted by sureshot007

Exchange and Push are not the same thing.

Looks like I'm staying with wm6 for a while then.

Uhm... Exchange and push are basically the same thing. How are they not? Exchange is just a type of email that uses push instead of pull... Do you understand what I mean by push instead of pull...?

I don't really want to get in an argument over this, I'd prefer to keep it on-topic. There doesn't seem to be a solution to your problem, as others with native Android devices have pointed out in the link I posted. Hopefully Google or some 3rd party app will fill the gap soon, but it's certainly not an issue with our hacked version of Android that we run.

[tekdemon]

Originally Posted by sureshot007

Exchange and Push are not the same thing.

Looks like I'm staying with wm6 for a while then.

It's just that WM6 is designed for people who use their phones for work and business (more like a blackberry) while Android is more for regular folks checking their Gmail casually.

[tomc585]

getting "cannot locate camera" error? thought this was fixed....grrrrrr

[arrrghhh]

Originally Posted by tomc585

getting "cannot locate camera" error? thought this was fixed....grrrrrr

Did you download my bundle in the first post, or did you update an old build...?

Need more information to help you...

[tomc585]

just updated with the system.ext2

[arrrghhh]

Originally Posted by tomc585

So i should use the bundle to get the camera working? Can i do that and then use my saved data.img file?

Originally Posted by tomc585

just updated with the system.ext2

You can in theory - but you also need to update your kernel. Simply updating the system.ext2 is only one piece of the puzzle - the userland piece. You need to match the kernel piece up with it, and it should work fine .

You can do what was suggested in the above post, but it's not necessary. Simply grab the latest kernel from the autobuild service (directions in the first post) and you should be good to go.

If you do have issues and need to delete your data.img, the steps above will help ease that pain.

Originally Posted by pchoi94

I noticed something regarding SOD. I was running the stock FRX04 bundle for a week or two without any SOD, and when I switched to FRX05 i started getting the SOD (i had to look up what SOD meant as I'm new to all this, ).

What I noticed is that as soon as I switched from the standard lock screen to the pattern lock screen, I haven't gotten an SOD yet (knock on wood). I had been running FRX04 with the pattern lock screen, and when I switched over I hadn't yet turned that feature on.

Hope this helps anyone out there who is having this issue, if indeed this is a workaround. I'll post back if I ever get the SOD again. It may have been discussed in other threads, but I didn't see it in this one and I'm still new to all this. Plus this site is god awful slow for some reason, so it's a pain to try to go back and search previous threads!

No offense, but this has nothing to do with the SoD issue. It's almost certainly service related, some have narrowed it down to the difference between 3g and 2g data - and switching between these modes frequently exacerbates the SoD problem. So that explains why those with old Airaves that only do 2g (1x) data were constantly getting SoD's. If you disable data completely, I've heard the SoD issue is gone. The RIL is being rewritten as we speak, hoping to have a test on that soon!

Originally Posted by arrrghhh

No offense, but this has nothing to do with the SoD issue. It's almost certainly service related, some have narrowed it down to the difference between 3g and 2g data - and switching between these modes frequently exacerbates the SoD problem. So that explains why those with old Airaves that only do 2g (1x) data were constantly getting SoD's. If you disable data completely, I've heard the SoD issue is gone. The RIL is being rewritten as we speak, hoping to have a test on that soon!

no offense whatsoever! i'm still new to this so i just wanted to share my observation, but it's good to know what the true culprit is and that there's hopefully a fix coming soon. great job on all of this by the way, talk about breathing new life into old hardware, eh? nothing can beat the keyboard on the TP2, which is the only reason i haven't ponied up for a used incredible, since i'm stuck on my contract still. =)