[ankitchahal]

Why does my Passport shows uptime in negative. I checked threads with screenshots and all had positive uptime and my shows negative.. and its decreasing with time.. and I would say pretty fast its decreasing within 2-3 seconds last 4-5 digits are changing.



Posted via my awesome Passport

[ankitchahal]

Within two minutes last 6 digits changed. See the time stamp on screenshots.





Posted via my awesome Passport

[mad_mdx]

It's not decreasing, it's increasing, if we follow the order of your pictures.
It's the countdown before the phone will forever stop working.

[ankitchahal]

It's not decreasing, it's increasing, if we follow the order of your pictures.
It's the countdown before the phone will forever stop working.

Apologies..what I meant by decreasing is its approaching 0.. why did it start from negative in first place.. I haven't seen anyone with negative uptime before this. Moreover earlier it was positive(few months back)and now I checked its in negative but increasing(towards 0). In a day or two it will cross 0 but why starting from negative when it was positive earlier and what caused it to go into negative.. I will have 0 uptime soon lol after using device for 6 months..

Posted via my awesome Passport

[ankitchahal]

It's not decreasing, it's increasing, if we follow the order of your pictures.
It's the countdown before the phone will forever stop working.

If I understood what u mean by countdown is it will stop working when it reaches 0??

Posted via my awesome Passport

[vader42]

In programmer speak, it is a signed/unsigned error. If you have a 32 bit system, then an usigned integer goes from 0 to 4,294,967,295. If that same memory location is treated as a signed integer (ie can have negative or positive number), it goes from -2,147,483,647 to 2,147,483,647. Signed ints use twos compliment (look up wikipedia ) so that -1 is the same value as 4,294,967,294. If the OS counts up in unsigned integers, but the display shows signed ints, then you would count from 0 to 2,147,483,647, then go immediately to -2,147,483,647. It would then count up till it gets to 0, then start again. You have a seriously large uptime gotta love bb10.

Hope this makes sense.

Posted via CB10

[ankitchahal]

In programmer speak, it is a signed/unsigned error. If you have a 32 bit system, then an usigned integer goes from 0 to 4,294,967,295. If that same memory location is treated as a signed integer (ie can have negative or positive number), it goes from -2,147,483,647 to 2,147,483,647. Signed ints use twos compliment (look up wikipedia ) so that -1 is the same value as 4,294,967,294. If the OS counts up in unsigned integers, but the display shows signed ints, then you would count from 0 to 2,147,483,647, then go immediately to -2,147,483,647. It would then count up till it gets to 0, then start again. You have a seriously large uptime gotta love bb10.

Hope this makes sense.

Posted via CB10

Thanks. I get what u said but I dont understand how did I get so large uptime that it started from 0 den to 2,14....... and started from negative int to 0..

Today when I checked it was -18993248 and its not even 3 hours from dat time its -8516421 showing used 10000000. Now in these what is seconds or whatever is showing.. how is it calculating time I mean which digits show seconds or minutes or anything like dat.. dat looks like a huge uptime used in under 3 hours.



Posted via my awesome Passport

[Uzi]

Mine is in posisitive..hmmm

BlackBerry -Secured to the Core | CB MOD

[ankitchahal]

Mine is in posisitive..hmmm

BlackBerry -Secured to the Core | CB MOD

I am gonna have 0 uptime soon lol and den positive.. I am gonna catch you

Posted via my awesome Passport

[ankitchahal]

Mine is in posisitive..hmmm

BlackBerry -Secured to the Core | CB MOD

My uptime changed by 19000000 units within 5 hours. I dont know if its normal or not but as I told you am gonna catch your uptime.

Posted via my awesome Passport
Attachment 363474

[vader42]

Uptime is in milliseconds since boot. 5 hours = 1000*5*3600 = 18,000,000. To wrap the uptime counter, you would need about 49 days without rebooting.

Posted via CB10

[ankitchahal]

Uptime is in milliseconds since boot. 5 hours = 1000*5*3600 = 18,000,000. To wrap the uptime counter, you would need about 49 days without rebooting.

Posted via CB10

It came to positive as you can see from my earlier post. But just now I checked it went to negative again.. maybe because passport rebooted few min ago and it caused it to start from negative top.. just guessing...


Posted via my awesome Passport

[ankitchahal]

Uptime is in milliseconds since boot. 5 hours = 1000*5*3600 = 18,000,000. To wrap the uptime counter, you would need about 49 days without rebooting.

Posted via CB10

Regarding your 49 days saying.. say if after rebooting it again starts from NEGATIVE all over again which it did just now.. but still its less than what you calculated for 5 hours.. why my device wraping uptime counter within few hours..anyone any idea?

This is current uptime.. which will be in positive within few hours



Posted via my awesome Passport

[thurask]

Uptime is calculated by reading the boot time as a date, converting to milliseconds since 1970 and subtracting that from current milliseconds since 1970.

I'm assuming it's reading the boot time wrong, somehow. If it was an overflow it would revert to small positive numbers right after a reboot.

Is your boot time in Settings > About > Hardware a normal value?

Posted via CB10

[ankitchahal]

Uptime is calculated by reading the boot time as a date, converting to milliseconds since 1970 and subtracting that from current milliseconds since 1970.

I'm assuming it's reading the boot time wrong, somehow.

Is your boot time in Settings > About > Hardware a normal value?

Posted via CB10

Posted via my awesome Passport

[ankitchahal]

I rebooted again just to see from where counter starts..and according to starting point it will be soon 0 in 5 hours approx..so is dere any problem with my device's calculation of uptime..


Posted via my awesome Passport

[thurask]

Open your Browser and go to:

file:///var/boottime.txt

What does it say?

Posted via CB10

[ankitchahal]

Open your Browser and go to:

file:///var/boottime.txt

What does it say?

Posted via CB10

Its showing right time..

Same as settings>>about>>hardware


Posted via my awesome Passport

[thurask]

Hmm.

Try changing your time zone to Eastern Time (-5). Then reboot and check uptime.

If I remember correctly, there's a list in the escreens app containing how to parse the time zone (the IST at the end). Indian might not be in there.

Posted via CB10

[Uzi]

Hmm.

Try changing your time zone to Eastern Time (-5). Then reboot and check uptime.

If I remember correctly, there's a list in the escreens app containing how to parse the time zone (the IST at the end). Indian might not be in there.

Posted via CB10

Why Indian not in there?

BlackBerry -Secured to the Core | CB MOD

[ankitchahal]

Hmm.

Try changing your time zone to Eastern Time (-5). Then reboot and check uptime.

If I remember correctly, there's a list in the escreens app containing how to parse the time zone (the IST at the end). Indian might not be in there.

Posted via CB10

I did and it changed to positive number..is it only because of time zone that its showing such a short counter uptime??




Posted via my awesome Passport

[thurask]

Okay, change it to Islamabad (+5) and try again.

Then, back to automatic and try again.

I think any offset that isn't an integer is causing issues.

Posted via CB10

[thurask]

Why Indian not in there?

BlackBerry -Secured to the Core | CB MOD

https://gist.github.com/thurask/04dc9607d000ad4e1826

It isn't.

Posted via CB10

[ankitchahal]

I did as you said but same.. I changed to islamabad but counter started at same it did with ist perhaps maybe little less.. and then changed to IST and counter again from same number that it used to start i.e -19xxxxxx

Posted via my awesome Passport

[thurask]

Okay, so it might be positive offsets then.

Posted via CB10