random problem with unable to pick up incoming call

[shaggylive]

Originally Posted by Q_Q

Shaggy, in the Data 60 secs disconnect cab, the reg edit contains a string of numbers.

YOUR suspendresume777 tweak replaces this string with #777#.
Will it render the data disconnect null & void?
And also cause the dreaded can't connect to #777 popup

?????????

my cab has nothing to do with the disconnect timmer. and there are many versions of cabs out there for the 60sec timeout.

all I am saying is that the timeout setting by its self would not cause any issues. (as long as the always on flag isn't set.)

[Q_Q]

Originally Posted by shaggylive

?????????

my cab has nothing to do with the disconnect timmer. and there are many versions of cabs out there for the 60sec timeout.

all I am saying is that the timeout setting by its self would not cause any issues. (as long as the always on flag isn't set.)

It's the same reg edit as the 1 in here:

http://forum.ppcgeeks.com/showthread.php?t=69185

disconnect network when idle for 1 min timeout

Code:
HKLM\Comm\ConnMgr\Planner\Settings\
Set "CacheTime" to 60
Set "SuspendResume" to 58 00 00 00 33 00 99 00 88 00 39 00 58 00 39 00 29
Default is #777 and should not contain anything about GRPS
setting SuspendResume" to "58 00 00 00 33 00 99 00 88 00 39 00 58 00 39 00 29"
makes it so you can make calls while you have a data connection.
YOU CANNOT have both on at same time
before you COULD NOT answer any calls
while you had data present.
now it disconnects the data and
makes it so you can answer calls
Thanks to Razorloves

[shaggylive]

Originally Posted by Q_Q

"SuspendResume" to 58 00 00 00 33 00 99 00 88 00 39 00 58 00 39 00 29

asside from that code being being giberish, it's not needed for the 60 sec timeout.
my cab will fix that incorrect entry and incomming calls will be answerable again.

[sonysw]

Thanks for the info--I will give you more days and keep you update. So far, today and yesterday I have not experiencing the issue not able to pick up incoming call-may be just my luck--only time will tell.

[Q_Q]

Originally Posted by shaggylive

asside from that code being being giberish, it's not needed for the 60 sec timeout.
my cab will fix that incorrect entry and incomming calls will be answerable again.

Sounds great! But what about the 60 sec data disconnect?
Will it work now?

[shaggylive]

Originally Posted by Q_Q

Sounds great! But what about the 60 sec data disconnect?
Will it work now?

yes, if all the other data settings are correct.

[Q_Q]

Originally Posted by shaggylive

yes, if all the other data settings are correct.

Apparently you thought my previous version of the Data Disconnect was gibberish, LOL!

Can you point to one that isn't?

So while my data is disconnected atm, the data counter is running on 5 hrs now (unlike prior to this conversation+change) which leads me to believe it maybe dormant but not fully disconnected...

[shaggylive]

by giberish i meant that the hex code was i deciferable in any conersion i tried. im not sure about the right one, but know the suspendresume setting is picky. i made my cab specifically because other cabs out there didnt seem to always work. something about multistring regs...

u know the suspend resume is whack when its next to imosible to answer calls while a data session is open (arrows over signal bars of any kind).

maybe u want to run the other cab, then mine.