guys where can I change the way date or phone number is displayed?
for example, phone number +995 32 215 25 26 is displayed in the phone as +995 322 15 25 26 which is not correct...
Related
my xda II total incoming time is 1193046hrs,my god,it is 136 years!how to reset it? thanks!
Mine too!!!
This happened after a screwed up firmware upgrade..
--- Edit ---
Hmm..
1193045 dec = 123456 hex
But my phone says 1193046 hr 28 min 8 sec
1193046 hrs * 60 = 71582760 minutes
71582760 min + 28 min = 71582788 minutes
71582788 min * 60 = 4294967280 seconds
4294967280 sec + 8 sec = 4294967288 seconds
4294967288 dec = FFFFFFF8 hex = 11111111111111111111111111111000 bin
Now, this is strange..
Why not the last 7 seconds?
if Bonzo's calculation is correct, and I have no reason to doubt it,
Let someone call you for longer than 8 seconds and it will be OK
4294967288 sec = x'FFFFFFF8' = b'11111111111111111111111111111000' = -8 sec
x'FFFFFF8' + x'00000008' = x'100000000' but the 1 will overflow because it can only remember 4 bytes => x'00000000' = 0 sec
ha,it's ok!
Let someone call you for longer than 8 seconds and it will be OK
4294967288 sec = x'FFFFFFF8' = b'11111111111111111111111111111000' = -8 sec
x'FFFFFF8' + x'00000008' = x'100000000' but the 1 will overflow because it can only remember 4 bytes => x'00000000' = 0 sec
thanks very much,it's ok now!
Re: Do you believe my xda II total incoming time is 1193046h
xuanyuan said:
my xda II total incoming time is 1193046hrs,my god,it is 136 years!how to reset it? thanks!
Click to expand...
Click to collapse
try this link
"Call duration infos... how to reset counters?"
http://forum.xda-developers.com/viewtopic.php?t=15482
it works
Geese man you have alotta friends
When I installed Gullum's V6 I have a 12 hour clock display and it worked like this until I synced with outlook, then it changed to 24 hour display. I went to settings/system/regional settings/time/time style and it was changed to HH:mm:ss. I changed again to H:mm:ss, but the clock still displays 24 hour. I did a hard reset and I am back on 12 hour, but after restoring my backup I am again on 24 hour! Does anyone know where I can find (and change) these settings other than the normal method. These settings must be somewhere in registery, or...........?
My PC is on Vista 32bit with office 2007 and the clock has a 12 hour display.
the setting u have to change to is to hh:mm:ss, as the capital H means 24 hour time. then, you just need to soft reset.
eddyve said:
When I installed Gullum's V6 I have a 12 hour clock display and it worked like this until I synced with outlook, then it changed to 24 hour display. I went to settings/system/regional settings/time/time style and it was changed to HH:mm:ss. I changed again to H:mm:ss, but the clock still displays 24 hour. I did a hard reset and I am back on 12 hour, but after restoring my backup I am again on 24 hour! Does anyone know where I can find (and change) these settings other than the normal method. These settings must be somewhere in registery, or...........?
My PC is on Vista 32bit with office 2007 and the clock has a 12 hour display.
Click to expand...
Click to collapse
Generally 12/24hr display can be set via local settings like you said.
But if it fails to do so, try to modify the string with registry editor manually as below:
HKEY_LOCAL_MACHINE\nls\overrides\
set the value of STFmt to "tt h:mm:ss
Good luck!
Thx guys, now it works
Hey, I am trying to find the reg key that controls the the external display timeout, I know you can set it in the settings to 5, 10, 15, 30 seconds, but I am trying to figure out which reg key controls it. thanks
[HKEY_LOCAL_MACHINE\Software\HTC\SecondaryDsp]
"DisplayTimeout"=dword
Erofich said:
[HKEY_LOCAL_MACHINE\Software\HTC\SecondaryDsp]
"DisplayTimeout"=dword
Click to expand...
Click to collapse
Is there any number (or other) to put there to have a display timeout longer than 30 sec?
...10 minutes for example...I know that involves battery consuming but I (and my friends) like startreck external clock when I put my phone on the table...moreover there my phone is usually charging...
Some weeks ago I tried with no success...
thanks
same boat here, I can't get it to stay on any longer than 30 sec.
timeouts
it seems that the reg values of 2=5 sec, 3=10 sec, 4=15 sec and 5=30 sec, however no other numbers have a timed value, it must be referencing a dll file, but I am not sure which one, I will res hack some and see if I can find it.
"DisplayTimeout"=dword:00000002 - 5 sec
"DisplayTimeout"=dword:00000003 - 10 sec
"DisplayTimeout"=dword:00000004 - 15 sec
"DisplayTimeout"=dword:00000005 - 30 sec
try to set dword:6
Erofich said:
"DisplayTimeout"=dword:00000002 - 5 sec
"DisplayTimeout"=dword:00000003 - 10 sec
"DisplayTimeout"=dword:00000004 - 15 sec
"DisplayTimeout"=dword:00000005 - 30 sec
try to set dword:6
Click to expand...
Click to collapse
Unless we did something wrong, we tried it. It does not work
displaytimeout
Erofich,
it my be my device but the reg key for the display timeout only allows for a 0 through whatever number option, it does not show the 00000001 (etc.) values.
I tried to create a new dword key, but it does the same, only gives the option to enter the 0 through whatever number, is there a way to assign the 00000006 value to a dword 6?
Hi !
I'm on SE X10 Mini PRO U20i, Stock rom (2.1.1.A.0.6), Jit enabled, Dualtouch enabled, Heap size : 42m (default is 22), autokiller parameters (memory enhancement) : Foreground 6 Visible 8 Secondary Server 16 Hidden 40 Content 50 Empty 60 (also tried with default and with 4 8 15 16 23 42 and 4 8 15 42 42 64).
My issue is : When I receive a call, with Full screen caller ID enabled, my phone stop responding and reboot the UI (ask for pin code). It happens sometimes not always, but it's very annoying. Does anyone have the same issue ? And sometimes, it closes and goes directly to my stock caller app (on in or out call).
BTW, i've another issue with my hardware keyboard, I have double letter with one tap sometimes : i.e. helloo, how aree youu ?, But I just tap once on the keys :-/
Any idea guys (or girls) :-s ?
Leo.
have a Firefly AIO-3399j board that I am attempting to run a BOE NV140XTM-N52 display directly from it's eDP interface. I'm a novice when it comes to compiling kernels so I'm having some issues getting this to work properly. I have verified that the physical pinout between the board and the display is correct, and I do get an image on the screen some.
First information about the display from the data sheet. The timing that I see from the display says a 269.5 MHz Clock and the EDID table gives the following information. The clock max is 275.6MHz and minimum is 220.5MHz. Hor Active = 3840, Hor Blanking =160, Ver Active = 1100, Ver Blanking = 48, Hor Sync offset = 48, H sync pulse width = 32, v sync offset = 3, and v sync pulse width = 5. That's where I would assume the following timing would be correct.
hactive = 3840
vactive = 1080
hsync-len = 32
hback-porch = 80
hfront-porch = 48
vsync-len = 5
vback-porch = 40
vfront-porch = 3
Now if I do a cvt modeline calculation I get Modeline "3840x1100_60.00" 353.18 3840 4088 4504 5168 1100 1101 1104 1139 -HSync +Vsync which is completely different on the porches and sync lengths.
Now, onto the board. According to the SDK, the display timing isn't set in the device tree files, it's set in the drivers at /kernel/drivers/gpu/drm/panel/panel-simple.c which I've tried the timing above that I assumed is correct from the datasheet and I've tried the timing from the modeline calculation. I've also put the display timing in the device tree file to see if that would work.
So far, I have gotten to where I get an image on the display and it will flicker from time to time sitting at the home screen of android, but then if I open the app menu, it will flicker even more until I exit it. I've tried adjusting the clock up and down with no resolution, and eventually I will either get a brief image on the screen and then it fades out, or the display will start looking like the porches are completely wrong. The display appears to have EDID information, but doesn't appear to get passed onto the kernel properly.
I've spent several hours recompiling and flashing firmwares to where I'm at a point I have no clue what to do anymore. Can someone help?