CE OS 5.2.28232 Public release(20/05/2010)

novinsab wrote:

sorry, there is network drops though for less than a sec only when waking up... but i noticed missed call log failure which is very irritating... i haven't concluded on these bugs yet but i will slowly...

anyways i am trying new settings -
suspend power state
- default : 3
- ril : 2
- ril1 : 2
- gti6 : 2
- FLAGS : 200000 (HEX)

difference is ril and ril1 are now on 2 i.e. standby not sleep... so lets see results now...

ok, tired of searching, where are these settings?

Daniel261 wrote:

novinsab wrote:

sorry, there is network drops though for less than a sec only when waking up... but i noticed missed call log failure which is very irritating... i haven't concluded on these bugs yet but i will slowly...

anyways i am trying new settings -
suspend power state
- default : 3
- ril : 2
- ril1 : 2
- gti6 : 2
- FLAGS : 200000 (HEX)

difference is ril and ril1 are now on 2 i.e. standby not sleep... so lets see results now...

ok, tired of searching, where are these settings?

i think they're talking bout in these registry..hklm...bla..bla..bla...

nazri14 wrote:

Daniel261 wrote:

novinsab wrote:

sorry, there is network drops though for less than a sec only when waking up... but i noticed missed call log failure which is very irritating... i haven't concluded on these bugs yet but i will slowly...

anyways i am trying new settings -
suspend power state
- default : 3
- ril : 2
- ril1 : 2
- gti6 : 2
- FLAGS : 200000 (HEX)

difference is ril and ril1 are now on 2 i.e. standby not sleep... so lets see results now...

ok, tired of searching, where are these settings?

i think they're talking bout in these registry..hklm...bla..bla..bla...

that much i figure it out myself, but where exactly, i know i found them by accident one time, just can't seam to find them now.

HKLM -- system -- currentcontrostate -- power -- state

goodluck ;-)

yes....try try till u die(or suceed,which is unlikely)

thats so nice of you and encouraging! lol

Admin wrote:

yes....try try till u die(or succeed,which is unlikely)

thanks,

however, i tried a different approach.

do you know that in wm 6.1 there is no path like : HKLM -- system -- currentcontroset -- power -- state

instead there is a path : HKLM -- system -- currentcontroset - CONTROL -POWER - STATE (in witch there are all kinds of states(eg: ColdReboot, On, Resuming) and not one of them has any reference to ril or ril1, just to Default, Flags, Bkl1 (backlight), and CLSID Keys)

I know that WM6.1 is not WM6.5, but shouldn't this part be a little more similar?
Otherwise i cannot explain the existence of those HTC devices that u can update to wm 6.5 from 6.1 (case that omits making devices around OS, not the other normal way around).

I am actually saying that maybe we lost something in translation(wm6.1 to wm 6.5). Is it possible?

i think we need a litle program which wakeup device every 5 minutes but it doesnt turnon backligt. By using this methot at build 23088 we can reduce battery consumtion to %1 per hour. i try it with using some other complex program. it works but it slows down phone therefore we need a small program

as i am going ahead with my research on this topic... i am getting closer to concluding that the problem arises either from other devices (nor RIL, ACM or WAV) that are turned off during suspend state which cause the delay in getting status of network from RIL through GTI

this means that in actual practice there is no network drops as such... operating system thinks there is a network drop because it cannot get status from RIL but there is no actual drop from provider because otherwise we would not be able to recieve calls...

the delay in everything and missing a call log is probably because of syncronous threading with RIL status... the operating system goes into a momentary hang of a sort where it is trying to reset SOME device was suspended and it is that device that fails to register call log...

this is still a theory though need more research...

inputs are welcome though...

tusubasa wrote:

i think we need a litle program which wakeup device every 5 minutes but it doesnt turnon backligt. By using this methot at build 23088 we can reduce battery consumtion to %1 per hour. i try it with using some other complex program. it works but it slows down phone therefore we need a small program

i think, u can use activsync for mail setting like update every five minutes, or 15 minutes, this will keep the phone alive ... i dnt know if this will work or not, but there is no harm in trying, ;-)

saurabhrendale wrote:

tusubasa wrote:

i think we need a litle program which wakeup device every 5 minutes but it doesnt turnon backligt. By using this methot at build 23088 we can reduce battery consumtion to %1 per hour. i try it with using some other complex program. it works but it slows down phone therefore we need a small program

i think, u can use activsync for mail setting like update every five minutes, or 15 minutes, this will keep the phone alive ... i dnt know if this will work or not, but there is no harm in trying, ;-)

i will try it. but syncronizing every 5 mins can reduce battery life

tusubasa wrote:

saurabhrendale wrote:

tusubasa wrote:

i think we need a litle program which wakeup device every 5 minutes but it doesnt turnon backligt. By using this methot at build 23088 we can reduce battery consumtion to %1 per hour. i try it with using some other complex program. it works but it slows down phone therefore we need a small program

i think, u can use activsync for mail setting like update every five minutes, or 15 minutes, this will keep the phone alive ... i dnt know if this will work or not, but there is no harm in trying, ;-)

i will try it. but syncronizing every 5 mins can reduce battery life

ys it definately will, but i think u must be knowing after how much time the phone is dead i.e. 20 mins or 30 mins so if u try 2 snycronize it @ 15 mins it wont use that much battery, and one more thing there might be a problem if the phone is not syncronized, or even not also as the phone makes it alive ;-)

saurabhrendale wrote:

tusubasa wrote:

saurabhrendale wrote:

tusubasa wrote:

i think we need a litle program which wakeup device every 5 minutes but it doesnt turnon backligt. By using this methot at build 23088 we can reduce battery consumtion to %1 per hour. i try it with using some other complex program. it works but it slows down phone therefore we need a small program

i think, u can use activsync for mail setting like update every five minutes, or 15 minutes, this will keep the phone alive ... i dnt know if this will work or not, but there is no harm in trying, ;-)

i will try it. but syncronizing every 5 mins can reduce battery life

ys it definately will, but i think u must be knowing after how much time the phone is dead i.e. 20 mins or 30 mins so if u try 2 snycronize it @ 15 mins it wont use that much battery, and one more thing there might be a problem if the phone is not syncronized, or even not also as the phone makes it alive ;-)

i flashed my phone to build 23088 and i am testing this method now.

guys about the activesync thing... there is no point... it is like avoiding the phone going into suspend mode every 5 minutes... by default settings the phone takes 180 seconds to enter standby after being idle.... so the phone will remain in standbby for 2 minutes and will be on on or screenoff for 3 minutes... so theoritically battery consumption should reduce by about 60% compared to always on but then only if u get a call in these 2 minutes will there be no call log failure or delay...

anyways i seem to have found a solution that will curb all these

it makes the delay and missed call log failure subside but i dont know about battery consumption exactly... phone will goto suspend but will not loose notification of signal or hang when resuming! this could also mean that the phone is not actually going to suspend state or it could mean that the problem is solved... i have to give it more time to conclude!

just to tease, anyone interested?

Pm ure settings to Me....before giving them to anyone....let me confirm it before the noobs start pestering

novinsab wrote:

guys about the activesync thing... there is no point... it is like avoiding the phone going into suspend mode every 5 minutes... by default settings the phone takes 180 seconds to enter standby after being idle.... so the phone will remain in standbby for 2 minutes and will be on on or screenoff for 3 minutes... so theoritically battery consumption should reduce by about 60% compared to always on but then only if u get a call in these 2 minutes will there be no call log failure or delay...

anyways i seem to have found a solution that will curb all these

it makes the delay and missed call log failure subside but i dont know about battery consumption exactly... phone will goto suspend but will not loose notification of signal or hang when resuming! this could also mean that the phone is not actually going to suspend state or it could mean that the problem is solved... i have to give it more time to conclude!

just to tease, anyone interested?

good luck to you my friend. i hope you will successful. but my sollution looks work. i tried it for 4, 5, 10 , 30 minutes and there is no network drop. battery consumtion is %1 per hour i will give detail tomorrow.

tusubasa wrote:

novinsab wrote:

guys about the activesync thing... there is no point... it is like avoiding the phone going into suspend mode every 5 minutes... by default settings the phone takes 180 seconds to enter standby after being idle.... so the phone will remain in standbby for 2 minutes and will be on on or screenoff for 3 minutes... so theoritically battery consumption should reduce by about 60% compared to always on but then only if u get a call in these 2 minutes will there be no call log failure or delay...

anyways i seem to have found a solution that will curb all these

it makes the delay and missed call log failure subside but i dont know about battery consumption exactly... phone will goto suspend but will not loose notification of signal or hang when resuming! this could also mean that the phone is not actually going to suspend state or it could mean that the problem is solved... i have to give it more time to conclude!

just to tease, anyone interested?

good luck to you my friend. i hope you will successful. but my sollution looks work. i tried it for 4, 5, 10 , 30 minutes and there is no network drop. battery consumtion is %1 per hour i will give detail tomorrow.

Manas,

Remember that i come up with an idea like this, except that it wasn't to keep the phone alive, it was just to record the missed calls, just like the paid application MagiCall.
i suggested to Manas that the application Call Manager from WM 6.1 was somehow doing this recording.

It seams i talk for nothing.

tusubasa wrote:

novinsab wrote:

guys about the activesync thing... there is no point... it is like avoiding the phone going into suspend mode every 5 minutes... by default settings the phone takes 180 seconds to enter standby after being idle.... so the phone will remain in standbby for 2 minutes and will be on on or screenoff for 3 minutes... so theoritically battery consumption should reduce by about 60% compared to always on but then only if u get a call in these 2 minutes will there be no call log failure or delay...

anyways i seem to have found a solution that will curb all these

it makes the delay and missed call log failure subside but i dont know about battery consumption exactly... phone will goto suspend but will not loose notification of signal or hang when resuming! this could also mean that the phone is not actually going to suspend state or it could mean that the problem is solved... i have to give it more time to conclude!

just to tease, anyone interested?

good luck to you my friend. i hope you will successful. but my sollution looks work. i tried it for 4, 5, 10 , 30 minutes and there is no network drop. battery consumtion is %1 per hour i will give detail tomorrow.

Pm to the beta testers before posting it on the forum

Daniel261 wrote:

tusubasa wrote:

novinsab wrote:

guys about the activesync thing... there is no point... it is like avoiding the phone going into suspend mode every 5 minutes... by default settings the phone takes 180 seconds to enter standby after being idle.... so the phone will remain in standbby for 2 minutes and will be on on or screenoff for 3 minutes... so theoritically battery consumption should reduce by about 60% compared to always on but then only if u get a call in these 2 minutes will there be no call log failure or delay...

anyways i seem to have found a solution that will curb all these

it makes the delay and missed call log failure subside but i dont know about battery consumption exactly... phone will goto suspend but will not loose notification of signal or hang when resuming! this could also mean that the phone is not actually going to suspend state or it could mean that the problem is solved... i have to give it more time to conclude!

just to tease, anyone interested?

good luck to you my friend. i hope you will successful. but my sollution looks work. i tried it for 4, 5, 10 , 30 minutes and there is no network drop. battery consumtion is %1 per hour i will give detail tomorrow.

Manas,

Remember that i come up with an idea like this, except that it wasn't to keep the phone alive, it was just to record the missed calls, just like the paid application MagiCall.
i suggested to Manas that the application Call Manager from WM 6.1 was somehow doing this recording.

It seams i talk for nothing.

Daniel the missed call is related to Network Drops.....if there are network Drops No application will Fully work.....Remember ks20.exe....how many times it records wrong Data...how many times its records unknown number..Not to Mention call Delay.And sometimes phone slows coz of net drop....N mate i do value your opinion

Admin wrote:

tusubasa wrote:

novinsab wrote:

guys about the activesync thing... there is no point... it is like avoiding the phone going into suspend mode every 5 minutes... by default settings the phone takes 180 seconds to enter standby after being idle.... so the phone will remain in standbby for 2 minutes and will be on on or screenoff for 3 minutes... so theoritically battery consumption should reduce by about 60% compared to always on but then only if u get a call in these 2 minutes will there be no call log failure or delay...

anyways i seem to have found a solution that will curb all these

it makes the delay and missed call log failure subside but i dont know about battery consumption exactly... phone will goto suspend but will not loose notification of signal or hang when resuming! this could also mean that the phone is not actually going to suspend state or it could mean that the problem is solved... i have to give it more time to conclude!

just to tease, anyone interested?

good luck to you my friend. i hope you will successful. but my sollution looks work. i tried it for 4, 5, 10 , 30 minutes and there is no network drop. battery consumtion is %1 per hour i will give detail tomorrow.

Pm to the beta testers before posting it on the forum

ok man i will test it one day and i will send settings tomorrow

Admin wrote:

Daniel261 wrote:

tusubasa wrote:

novinsab wrote:

guys about the activesync thing... there is no point... it is like avoiding the phone going into suspend mode every 5 minutes... by default settings the phone takes 180 seconds to enter standby after being idle.... so the phone will remain in standbby for 2 minutes and will be on on or screenoff for 3 minutes... so theoritically battery consumption should reduce by about 60% compared to always on but then only if u get a call in these 2 minutes will there be no call log failure or delay...

anyways i seem to have found a solution that will curb all these

it makes the delay and missed call log failure subside but i dont know about battery consumption exactly... phone will goto suspend but will not loose notification of signal or hang when resuming! this could also mean that the phone is not actually going to suspend state or it could mean that the problem is solved... i have to give it more time to conclude!

just to tease, anyone interested?

good luck to you my friend. i hope you will successful. but my sollution looks work. i tried it for 4, 5, 10 , 30 minutes and there is no network drop. battery consumtion is %1 per hour i will give detail tomorrow.

Manas,

Remember that i come up with an idea like this, except that it wasn't to keep the phone alive, it was just to record the missed calls, just like the paid application MagiCall.
i suggested to Manas that the application Call Manager from WM 6.1 was somehow doing this recording.

It seams i talk for nothing.

Daniel the missed call is related to Network Drops.....if there are network Drops No application will Fully work.....Remember ks20.exe....how many times it records wrong Data...how many times its records unknown number..Not to Mention call Delay.And sometimes phone slows coz of net drop....N mate i do value your opinion

Thanks man.

tusubasa wrote:

Admin wrote:

tusubasa wrote:

novinsab wrote:

guys about the activesync thing... there is no point... it is like avoiding the phone going into suspend mode every 5 minutes... by default settings the phone takes 180 seconds to enter standby after being idle.... so the phone will remain in standbby for 2 minutes and will be on on or screenoff for 3 minutes... so theoritically battery consumption should reduce by about 60% compared to always on but then only if u get a call in these 2 minutes will there be no call log failure or delay...

anyways i seem to have found a solution that will curb all these

it makes the delay and missed call log failure subside but i dont know about battery consumption exactly... phone will goto suspend but will not loose notification of signal or hang when resuming! this could also mean that the phone is not actually going to suspend state or it could mean that the problem is solved... i have to give it more time to conclude!

just to tease, anyone interested?

good luck to you my friend. i hope you will successful. but my sollution looks work. i tried it for 4, 5, 10 , 30 minutes and there is no network drop. battery consumtion is %1 per hour i will give detail tomorrow.

Pm to the beta testers before posting it on the forum

ok man i will test it one day and i will send settings tomorrow

Can you share the setting with all the beta testers (PM beta testers), you know several pairs of eyes are better than one pair.

i am back to wm 6.1!

could not try anymore

yaa well Daniel,artural,tusubasa are also constantly looking for fixes...i m sure soon they'll be able to find something...

i want to test it can i get link thx