||Discontinued||

[echomatics]

Then beset to to install the Rom again and follow it with a hard reset. Last option I can suggest. I have not had this issues myself so I am hoping that would fix it for you.

[ronblayze]

Originally Posted by echomatics

Then beset to to install the Rom again and follow it with a hard reset. Last option I can suggest. I have not had this issues myself so I am hoping that would fix it for you.

What carrier are you with?

[echomatics]

I am with Bell in Canada

[bikeandestroyx]

ive never had this issue either, and ive been using this longer than everyone lol havent had this issue on any of the previous versions either

[Carla]

Mine were very isolated and few and far between...Could it be a Sprint thing?? I do use S2U2 so I think that may play a part since I use the caller ID feature, but it has only happened less then a handful of times, and I talk on the phone a lot sometimes LOL

[ronblayze]

Originally Posted by CarlaDarla

Mine were very isolated and few and far between...Could it be a Sprint thing?? I do use S2U2 so I think that may play a part since I use the caller ID feature, but it has only happened less then a handful of times, and I talk on the phone a lot sometimes LOL

Yeah mine didn't happen often either. Only the couple of times I actually used my phone to answer a call (usually texting =X). I might just put s2u2 back on here just to see if I still get those issues.

[Eclipsi01]

Originally Posted by CarlaDarla

Mine were very isolated and few and far between...Could it be a Sprint thing?? I do use S2U2 so I think that may play a part since I use the caller ID feature, but it has only happened less then a handful of times, and I talk on the phone a lot sometimes LOL

I think it's an S2U2 issue. I've been using it on every flash I do and it has worked fine until this one. Something between S2U2 and this ROM. But, I'm willing to get rid of S2U2 to fix it
I've removed S2U2 as of this morning and I haven't missed any calls today. What would happen is if the screen is locked by S2U2, and a call came in, there would be some kind of conflict within the ROM when it tried to switch to the 6.5 screen then to the S2U2 screen. If you slid to unlock, it would relock and keep happening. You'd end up missing the call, and I'd have to reboot

[Pet4h]

Originally Posted by Eclipsi01

I think it's an S2U2 issue. I've been using it on every flash I do and it has worked fine until this one. Something between S2U2 and this ROM. But, I'm willing to get rid of S2U2 to fix it
I've removed S2U2 as of this morning and I haven't missed any calls today. What would happen is if the screen is locked by S2U2, and a call came in, there would be some kind of conflict within the ROM when it tried to switch to the 6.5 screen then to the S2U2 screen. If you slid to unlock, it would relock and keep happening. You'd end up missing the call, and I'd have to reboot

ok, I'm having the same problems. I can't receive or make any calls. How do I remove this s2u2? I've search but can't find a way. thanks for your time.

[bikeandestroyx]

Originally Posted by Pet4h

ok, I'm having the same problems. I can't receive or make any calls. How do I remove this s2u2? I've search but can't find a way. thanks for your time.

there isnt s2u2 included in my v3 roms.
Also if your having trouble with not answering calls, go to start>settings>system>smart lock [uncheck all boxes]

[Eclipsi01]

I just noticed in System Settings, there's an icon called SmartLock. I just unchecked everything in there, reinstalled S2U2 and received some test calls and it looks like S2U2 works fine again.