|>|>April 20|<| Sac ROM Developement[iClone 7]{light}{heavy}

[TWiST]

I havent tried a hard reset again just to check but on soft reset I am getting a crash PluginInstaller.exe IOException any1 else having this issue ?

[edufur]

Please add this to the known bugs:
- Exchange Active Sync may not work with some corporate servers. Result code 0x85010013. "Exchange active sync has encountered an error. If the problem persists, please contact your administrator."

This is a ROM by ROM issue that I think some chefs are just not realizing that they are missing something in their builds. I havent seen this working for SAC kitchens since the 222 build. I HAVE seen it working with other ROMS and kitchens though. I think we need to see some form of collaborative effort on the part of ALL chefs to get this issue eliminated for good. It is a roll the dice problem. Meaning, I roll the dice every time I try a new ROM... and end up seeing it half the time.

[coolsac32]

i get that with current 21806 build that i am using right now. it seems to show up but it hasnt stopped me from doing anything. has it happened initially? because i got it after i used titanizer. unfortunately i cannot work on anything until my computer is fixed but i will make a note of it.

[bmb2n]

Originally Posted by TWiST

I havent tried a hard reset again just to check but on soft reset I am getting a crash PluginInstaller.exe IOException any1 else having this issue ?

PluginInstaller.exe crashing is related to Titanium plugins. It happens when I cooked them in from the kitchen and switch to Manila, then reboot. Cook your rom without Titanium selected and you will be fine.

Edit: I tracked it down to "CTaskanium_Titanium_Plugin" package is responsible to the crash.

[edufur]

Originally Posted by coolsac32

i get that with current 21806 build that i am using right now. it seems to show up but it hasnt stopped me from doing anything. has it happened initially? because i got it after i used titanizer. unfortunately i cannot work on anything until my computer is fixed but i will make a note of it.

I dont select titanizer. And titanizer doesnt have anything to do with it. It is something that is seen in MANY MANY ROMs. And I think none of the chefs have a clue it is even happening since most of them don't use direct push. It is a problem that - if encountered - is 100% consistently a problem with the build it is encountered in. In other words, there is no hotfix that I have seen. You just have to hope that you dont see it in the next ROM or Kitchen that you try.

[bmb2n]

Originally Posted by edufur

I dont select titanizer. And titanizer doesnt have anything to do with it. It is something that is seen in MANY MANY ROMs. And I think none of the chefs have a clue it is even happening since most of them don't use direct push. It is a problem that - if encountered - is 100% consistently a problem with the build it is encountered in. In other words, there is no hotfix that I have seen. You just have to hope that you dont see it in the next ROM or Kitchen that you try.

The exchange server syncing problem is known among many different ROM. Only a fews ROM out there works seemlessly. I suggest if Exchange syncing is a must have for you, you're out of luck here but to use those known working ROM.

[edufur]

Originally Posted by bmb2n

The exchange server syncing problem is known among many different ROM. Only a fews ROM out there works seemlessly. I suggest if Exchange syncing is a must have for you, you're out of luck here but to use those known working ROM.

I realize this. But there is no good reason for it other than cooks are unaware of what they must do in order to prevent this issue, or it is just laziness. NONE of the ROMs or kitchens have to have this problem. If the missing files were put in, the problem wouldnt be there. I am trying to make the chefs aware of this oversight and at a minimum, get them all to start posting this in the known bugs if they aren't going to take the steps to prevent the issue.

[bmb2n]

Originally Posted by edufur

I realize this. But there is no good reason for it other than cooks are unaware of what they must do in order to prevent this issue, or it is just laziness. NONE of the ROMs or kitchens have to have this problem. If the missing files were put in, the problem wouldnt be there. I am trying to make the chefs aware of this oversight and at a minimum, get them all to start posting this in the known bugs if they aren't going to take the steps to prevent the issue.

I believe that most chefs out there are working extra hard to fix bugs that are fixable. They do not have source code to the o/s itself, so bugs that are existed with the Microsoft beta o/s are also carried over to the cooked rom. Swapping packages with a known working rom might not be a feasible option across builds. On top of that, not everyone has access to exchange server to test their ROM with.

[edufur]

Originally Posted by bmb2n

I believe that most chefs out there are working extra hard to fix bugs that are fixable. They do not have source code to the o/s itself, so bugs that are existed with the Microsoft beta o/s are also carried over to the cooked rom. Swapping packages with a known working rom might not be a feasible option across builds. On top of that, not everyone has access to exchange server to test their ROM with.

I dont think this is a source code or version issue. If it was, all chef flavors of a specific version would either have the problem, or they would all not have the problem. But I am consistently seeing one version play out differently across multiple chef flavors. This tells me that some of the chefs are doing something to cause this problem. And if they don't have the ability to test, fine, but I ask that at a MINIMUM, when someone like me finds the problem, that they post it at the front page as a "known issue" so that someone else doesnt have to lose a previously working ROM to find out what I already found out.

[bmb2n]

Originally Posted by edufur

I dont think this is a source code or version issue. If it was, all chef flavors of a specific version would either have the problem, or they would all not have the problem. But I am consistently seeing one version play out differently across multiple chef flavors. This tells me that some of the chefs are doing something to cause this problem. And if they don't have the ability to test, fine, but I ask that at a MINIMUM, when someone like me finds the problem, that they post it at the front page as a "known issue" so that someone else doesnt have to lose a previously working ROM to find out what I already found out.

These are bleeding edge beta ROMs. System stability and bug are the common nature of beta. Flashing is at your own risk. The chefs are not getting paid for their work. Beside you can always switch back to your original ROM with SPB restore.