Related
I recently switched from a Wing (Herald) to the Hermes (8525)... I noticed the colors are pretty crappy compared to the wing, yet the Hermes is much better in just about every other aspect.
Is there a way to adjust the colors, contrast, etc. to try and make it look a bit better?
I think the same...
Is the any way to adjust the contrast/brightness and other things so the colors could be more vivid?
Comparing the screen with the one in Artemis it looks really bad
^^Agreed^^
the colors seem pretty dull and not vivid like the touch that I had previous to this device..taking a look at the specs, it seems like both touch and the tytn use the same TFT touch sensitive screen supporting over 65K colours. But why does the tytn screen seem "gloomy" does this have to do with the fact that it is Windows 5??.. any help is appreciated
I have WM6 on board and it is also very dull I even hacked the registry to show the "Contrast" option in Settings but nothing happens when I change it Any ideas?
So I guess its not the W5, well the only other thing I can think of, is the protective film that came with the phone?? any one using their device without the "stock" protector that was provided with the phone?
I have no protector on my screen
I think that the protection-glass makes the screen look so bad...
hmmm
I noticed something interesting, once I do a soft reset and the device is loading up, when my providers (rogers) logo appears the screen actually gets brighter and then it drops back to the less bright screen that we are complaining about does this only happen to my hermes.. this I guess that there is light at the end of tunnel.. Now its a matter of tweaking this to remain "max bright".. any suggestions??
HTC-sync said:
I noticed something interesting, once I do a soft reset and the device is loading up, when my providers (rogers) logo appears the screen actually gets brighter and then it drops back to the less bright screen that we are complaining about does this only happen to my hermes.. this I guess that there is light at the end of tunnel.. Now its a matter of tweaking this to remain "max bright".. any suggestions??
Click to expand...
Click to collapse
Do a search for "Superbright" cab...it's small & will do the trick!
thank you galaxys!! here is the direct link to the .cab file, I am currently at work so I cant try it out .. if some one beats me to it, please post and let me now what you think!
http://www.vijay555.com/?Releases:VJLumosII
nice!
just installed the .cab and .. its alot brighter.. thanks again vijay555
True... I have tested it several days ago.... It is brighter but the contrast is still low And everytime you want to open the camera, you have to disable it...
Can anyone shed any light on why my buttons, just the ones on the unit itself, aren't producing their lovely orange glow anymore? The d-pad light still works, but the OK, Win & browser buttons are dark.
The only thing I could think of was that I installed SBSH, like everything because I'm fed up with Spb, so I uninstalled w/ several reboots. Still no go.
Maybe it's better that way. Less battery drain. It's not like I can't find them, but they were cute. My 3-year-old daughter loves the orange.
UPDATE:
I never did figure out what it was. Between booting up with PhoneAlarm, UltimateLaunch, MccMoblieFinder, LivePVR (which I'm not sure works) something crashed, so I hard reset.
I did figure out after my reset that the backlight doesn't actually go all the way off; when the buttons are off the screen is as dim as it's going to get (and now with rk-backlight, I am finally free of SPB - they lost thier robustitude with newer OSs and everyone else seems to have caught up with thier graphics, but with a smaller footprint.)
Does your backlight work? i always thought it was just the backlight shining through the buttons.
Well, no, actually I've never really thought about it.
Mine are off until the backlight comes on then they are on.
I noticed the other day that mine had gone off too, but a soft reset sorted it.
keyboard backlights!!!
Janis said:
Can anyone shed any light on why my buttons, just the ones on the unit itself, aren't producing their lovely orange glow anymore? The d-pad light still works, but the OK, Win & browser buttons are dark.
The only thing I could think of was that I installed SBSH, like everything because I'm fed up with Spb, so I uninstalled w/ several reboots. Still no go.
Maybe it's better that way. Less battery drain. It's not like I can't find them, but they were cute. My 3-year-old daughter loves the orange.
UPDATE:
I never did figure out what it was. Between booting up with PhoneAlarm, UltimateLaunch, MccMoblieFinder, LivePVR (which I'm not sure works) something crashed, so I hard reset.
I did figure out after my reset that the backlight doesn't actually go all the way off; when the buttons are off the screen is as dim as it's going to get (and now with rk-backlight, I am finally free of SPB - they lost thier robustitude with newer OSs and everyone else seems to have caught up with thier graphics, but with a smaller footprint.)
Click to expand...
Click to collapse
HI GUYS,
A late entry but tot u guys might b able to help a brother in need, my Ameo's keyboard back light never seems to come on EVER, & have check for setting or cab files but all to no success, can any1 help PLEASE either by just replying on here or PM me please :-(.
Umm, the ameo keyboard doesn't have a backlight???
Backlight off
there's rk-backlight.exe
http://forum.xda-developers.com/showthread.php?t=328114&highlight=backlight
check the Settings/system/backlight
The backlight on a working x7500/1 doesn't actually go all the way off, the screen does (standby), and the buttons do when it's in it's more-or-less "off" state (the buttons are off, and the system calls the state "off" but it's just really low.)
If you can see the screen, but there really is NO backlight, my suggestions in this order:
a soft reset
install a backlight contolling software like rk-backlight & set it
a hard reset
a flash of a new rom
send it in to ppctechs.com for repair
I changed the following registry entry:
[HKEY_CURRENT_USER\ControlPanel\BackLight]
"AutoDeviceLockEnable"=dword:00000001
Now when I press the the power button of the blackstone the wm 6.5 slider will appear. So far it works fine. But when the phone is not used for a while the backlight is getting darker. When I unlock the blackstone with the slider, the backlight is not getting brighter, it remains darker (but still not turned off).
Does anybody know this behaviour? Any solutions?
Thanks
Andy
This is a known problem..Try to use auto csdevctrl for auto wm 6.5 locking..
wm6.5 lock is nice and functionally but it is slow and buggy. Don't know if it's final version will improve but I suggest you to use third-party solutions.
gbjack said:
wm6.5 lock is nice and functionally but it is slow and buggy. Don't know if it's final version will improve but I suggest you to use third-party solutions.
Click to expand...
Click to collapse
Ever tried EnergyROM HD 'Phoenix' (21731)
faster than any other 6.1 ROM I have tried.
Anyways - why do we need another program to do what WM6.5 should do on ist own?
peterkling said:
Anyways - why do we need another program to do what WM6.5 should do on ist own?
Click to expand...
Click to collapse
Because WM6.5 isn't officially released on the Blackstone
the reason is...I am cooking my own 6.5 rom and I just won't get it working.
on the new miri V18 the backlight work perfectly
voileuxcool said:
on the new miri V18 the backlight work perfectly
Click to expand...
Click to collapse
no,it's not.
sorry it don't work after unlock but it work when touch the screen ! And on previous versions the wake up on touch don't worked
When I am using the following settings, the lock is not activated anymore when the backlight is dims...but when I tab on the screen, the backlight does not turn on anymore. So with those settings I went one step ahead, but I still not reached my goal. Has someone an idea? How can I force the backlight to turn on again?
[HKEY_CURRENT_USER\ControlPanel\BackLight]
"BatteryTimeout"=dword:0000003C
"LightDetectOn"=dword:00000001
"Brightness"=dword:00000005
"ACBrightness"=dword:00000005
"ExtOnOff"=dword:00000001
"LightSensorToScreenOff"=dword:00000005
"LightSensorPollingEnable"=dword:00000000
"AutoDeviceLockTimeout"=dword:0000012C
"AutoBklOffset"=dword:00000000
"LedOnOffAdcValue"=dword:0000013F
"AutoDeviceLockEnable"=dword:00000001
"DimBKLinUnlockScreen"=dword:00000000
"ACBacklightOnTap"=dword:00000001
"BacklightOnTap"=dword:00000001
"OnOff"=dword:00000001
"LightSensorThreshold"=dword:00000005
"LightSensorInterval"=dword:0000012C
"LightSensorTimeout"=dword:0000001E
"AutoSensor"=dword:00000001
"QKeyLedTimeout"=dword:0000000A
"BatteryTimeoutUnchecked"=dword:00000000
"BatteryTimeoutTemp"=dword:00000000
"ACTimeoutUnchecked"=dword:00000000
"ACTimeoutTemp"=dword:00000000
"ACTimeout"=dword:0000003C
[HKEY_CURRENT_USER\ControlPanel\BackLight\LockLevel]
"LockLevel"=dword:00000000
Hi mates,
If you want to use the AutoLock of WM6.5 without backlight issue, you need to do as follow:
1. Change Auto Backlight to Manual
2. Disable "Turn Off Backlight" in Power Setting
Now, the AutoLock will work only when you do poweroff.
Cheers,
thanks...but I know... I need the registry settings...cause I want to cook it into my rom.
backlight issues here too
I am having the exact same problem. I have the 6.5 5nergy ROM. I have to manually go to backlight and touch the screen. Even though the bar on the backlight program is up to the top, it's still dim.
This has made me avoid using my Fuze and stick with my N85 - which has a much better camera anyway. But that full QWERTY keyboard... I miss it so!
Does anybody want the fix for this, or is this old news?
ANDYx1975 said:
the reason is...I am cooking my own 6.5 rom and I just won't get it working.
Click to expand...
Click to collapse
It is a known problems, have problem across three devise HD2, HD & SX1.
My 2 cent obser, slock mess up, device lock work good for me across three device, so far as I know only energy rom cook in and no issue. hope it help.
Cheers
The issue from what I have been able to determine, is that once your device Auto Locks, the BackLightOnTap stops working. Once it happens, it is not possible to get the backlight back on until you turn the screen off and back on again (if Auto adjust backlight is turned off this may not even work). One way to get around it is to never dim the backlight.
Anyway, I extracted the BackLight.dll from the leaked WM 6.5 ROM for the Diamond (Pine) and it corrects the issue on my Raphael. HTC seems to have fixed the issue, but there is one caveat.
With the new driver, the screen dims when ever the device is locked. The backlight will turn back on once it is unlocked. What this means is that if you are outdoors and your device is locked, it will be difficult to see the slider in order to unlock it.
This is the only issue I have encountered so far.
Update: Doh, what an easy fix. The value that controls the backlight level while the screen is locked is here...
Code:
[HKEY_CURRENT_USER\ControlPanel\BackLight\LockLevel]
"LockLevel"=dword:0
By default, this is set to 0. Values 0 through 10 are valid (0 = lowest, 10 = highest).
Update 2: Bah! One of the drivers sets the LockLevel back to 0 on boot, which is a good thing because if you set the LockLevel to anything but 0 and use AutoLock, BackLight.dll crashes (probably why HTC forces it back to 0 on boot).
Also, a note for Raphael users, since this dll is from a Diamond, you will loose the keyboard backlight.
TrueG
trueg said:
The issue from what I have been able to determine, is that once your device Auto Locks, the BackLightOnTap stops working. Once it happens, it is not possible to get the backlight back on until you turn the screen off and back on again (if Auto adjust backlight is turned off this may not even work). One way to get around it is to never dim the backlight.
Anyway, I extracted the BackLight.dll from the leaked WM 6.5 ROM for the Diamond (Pine) and it corrects the issue on my Raphael. HTC seems to have fixed the issue, but there is one caveat.
With the new driver, the screen dims when ever the device is locked. The backlight will turn back on once it is unlocked. What this means is that if you are outdoors and your device is locked, it will be difficult to see the slider in order to unlock it.
This is the only issue I have encountered so far.
Update: Doh, what an easy fix. The value that controls the backlight level while the screen is locked is here...
Code:
[HKEY_CURRENT_USER\ControlPanel\BackLight\LockLevel]
"LockLevel"=dword:0
By default, this is set to 0. Values 0 through 10 are valid (0 = lowest, 10 = highest).
Update 2: Bah! One of the drivers sets the LockLevel back to 0 on boot, which is a good thing because if you set the LockLevel to anything but 0 and use AutoLock, BackLight.dll crashes (probably why HTC forces it back to 0 on boot).
Also, a note for Raphael users, since this dll is from a Diamond, you will loose the keyboard backlight.
TrueG
Click to expand...
Click to collapse
so ,does it working on HD?
I can't say as I have a Raphael, but it should.
Also, I have found that if you lock the screen using a password [\Control Panel\Lock] there is no problem with the backlight. The crappy part being you have to enter a password from then on, but it's one way.
Any solution yet?
ANDYx1975 said:
I changed the following registry entry:
[HKEY_CURRENT_USER\ControlPanel\BackLight]
"AutoDeviceLockEnable"=dword:00000001
Now when I press the the power button of the blackstone the wm 6.5 slider will appear. So far it works fine. But when the phone is not used for a while the backlight is getting darker. When I unlock the blackstone with the slider, the backlight is not getting brighter, it remains darker (but still not turned off).
Does anybody know this behaviour? Any solutions?
Thanks
Andy
Click to expand...
Click to collapse
Does anyone have a solution for this problem yet?
You can try the CAB I posted. The only quirk is that the screen DIMs when the device is locked (which seems to be the same behaviour as the Omnia). The backlight turns back one once unlocked. This appears to be HTCs answer to the problem.
Hello guys,
at first i want to excuse for my language mistakes, it's not my native language.
I have a problem with my phone. If I make a phone call, the proximity sensor deactivates the screen, like it should be, but the screen won't wake up, after I push the phone away from my ear. It takes a long time, until I can see something again on the screen. I don't want to create a new thread where I am crying about this issue, I want to solve this problem.
I also searched at many other developer-forums and i noticed, that this happens to many people around there and everybody is crying about it.
Everybody who can provide informations, that can help to solve this problem is invited to share his experiences with us.
The HD2 is a very beautiful mobile phone, but this problem is really annoying.
I made a lot of tests to find the reason of this problem.
Things, that I did without getting clear results:
1. Dirty sensor
It could be possible, that the sensor or the glass plate is dirty inside and because of this, the sensor can't recognize it properly.
2. Light sensor
It was random, that I expected that this issue also depends on the light sensor. I made a call and the screen goes off, like every time. Now i take the flashlight and light it in the area of the proximity and light sensor. Instantly the screen went on and displayed everything, but if I move the flashlight away again, it goes off. and that happens as long as you make the call. If you end the call the screen stays off like it's everytime the case. If I move the flashlight now in front of the sensor area, the screen goes on and it stays on.
EDIT: It's not everytime working.
The following things I did, but brought no solution:
1. Flashing everything new
I did a task29, flashed some different radio roms, different HSPL's and also many different ROM's. Windows Mobile and ALSO Android. Nothing helps.
2. Blowing inside the case
I also read that it help if I blow inside the case near the area of the sensors. I don't know if it really helps, but it's fur sure not the reason.
3. Display protector
In my case it's not the reason, because I don't use a protector and never used one.
Questions, that I have now:
1. Proximity sensor
Everybody says the HTC HD2 has a proximity sensor, but I don't know if this is sure. Maybe the phone has only a light sensor, which works like a proximity sensor, like other newer phone's like the HTC Wildfire.
2. Production error
Could it be a failure from the factory? Encoutered anybody this problem only after some time? Or maybe anyone who can say that the problem was solved by itself?
Please don't answer like: use the forum search or something like this.
I searched a lot and not only in this forum.
Best regards Gerhard Silvio
Further test confirmed, what I said. The problem must be the light sensor. After a call and the phone don't turn on, light a fire in front of the phone or light with a flashlight to the sensors. it goes on immediately!
Strange..
EDIT:
I made a video to show what I mean. Excuse me for my bad english ^.^
Now you developers outside are asked how to fix it...
Open the phone and clean? Or maybe it's not so easy?
Best regards
There is no possibility to fix this issue, because the light sensor is not programmable (as we know now, the HD2 has no proximity sensor). The sensor decides to turn the screen off when it gets dark, so i took some black nail polish and put it under the glass surface in front of the sensor. The screen now don't turn off and automatic light won't work also, but i can compensate these problems better than the call issue.
And without doing this, you will never be able to use WP7 right, because you can only end a call if you push the on-screen button, and this button won't appear. So you must wait until the other side ends the call, and if this don't happen you can't use your phone again without remove and reinserting the battery ^^
I hope I could help you by providing these informations.
Thread can be closed, there's nothing more to say.
The problem is isnst a problem 'cos you burned the proximity sensor with that heat.
iamrv said:
The problem is isnst a problem 'cos you burned the proximity sensor with that heat.
Click to expand...
Click to collapse
What are you talking?
That has nothing to do with any heat (if you mean the lighter). It was 3cm or more, can't follow your answer, cause its unlogical. It also worked with a normal light or a laser or anything else.
the problem u have ( i have too) only happens in nand builds, i dont have this issue with Duttys_2.5_5.21916.5.0.95_3.14_HD2_ML_Family_ROM_(V12)_WWE installed.. the phone act normal completely.
so i have to say this to me is a nand build issue, why others on htc hd2 arent not having this problem is what confuses me
In my case, it was not depending of what build or os i use. It happened in wm6.5, sd android, nand android and also in wp7. I caused by the hardware, and if i can't repair it, i have to destroy or deactivate it. with software you can't deactivate the sensor so i coloured the sensor black, that he won't notice anything anymore and the problem is solved. i have no problem with the screen active, while calling.
Firstly, the HD2 DOES have a proximity sensor and it works flawlessly in WM6.5. I know this was 100% fact for me, as I was very impressed at how well it worked. There are 2 sensors, clearly visible, next to the earpiece. One is a light sensor, as you know, and the other is a proximity sensor. This is not an opinion - it's a fact. I just wanted that to be very clear.
Also, I don't have this problem in Android, either SD builds (I don't use any more), or NAND builds (my daily driver). I will admit that there is a delay of a couple of seconds when I take the phone away from my ear, before the screen comes on, but I know that's just down to the fact that I'm using ported software.
You say that in your case this failed to work in both WM6.5 and Android. You've got a dodgy proximity sensor then. This is clearly a hardware failure.
The HD2 DOES have a proximity sensor but this fault does occur on some android builds
If it occurs for you everywhere, then u simply have a faulty proximity sensor, and i know this because i too have used wm.5, andoird nand and sd, and WP7
and the proximity sensor works fine on all but some (older) android builds
if the HD2 didn't have a proximity sensor there wouldn't be a second hole, next to the light sensor.
johncmolyneux said:
Firstly, the HD2 DOES have a proximity sensor and it works flawlessly in WM6.5. I know this was 100% fact for me, as I was very impressed at how well it worked. There are 2 sensors, clearly visible, next to the earpiece. One is a light sensor, as you know, and the other is a proximity sensor. This is not an opinion - it's a fact. I just wanted that to be very clear.
Also, I don't have this problem in Android, either SD builds (I don't use any more), or NAND builds (my daily driver). I will admit that there is a delay of a couple of seconds when I take the phone away from my ear, before the screen comes on, but I know that's just down to the fact that I'm using ported software.
You say that in your case this failed to work in both WM6.5 and Android. You've got a dodgy proximity sensor then. This is clearly a hardware failure.
Click to expand...
Click to collapse
Thanks for your opinion, but my proximity sensor works flawlessly in windows mobile 6.5.3 but under superram darkstone build I suffer rge same problem. Most of the times can be fixed touching the write arrow button...
Maybe can help...
Sent from my HTC Desire using XDA App
My HD2 tmobile also has this proximity sensor problem. I use my finger to cover the sensors (light, proximity) during the call. The screen will off. But the screen cannot back to on when I moved out the sensor cover. I tried to use the torch to shine the sensor but no response.
If HD2 connected to power supply or PC USB for battery charging. The screen can switch on. I think this charging method for sensor disabled.
you already thought about a Hardware Problem and let HTC fix it?
yogya said:
Thanks for your opinion, but my proximity sensor works flawlessly in windows mobile 6.5.3 but under superram darkstone build I suffer rge same problem. Most of the times can be fixed touching the write arrow button...
Click to expand...
Click to collapse
Thanks, but that's clearly just an issue with the Android build you're using. Try another one and see if it's better.
I tested my HD2 again. I restored WM6.5 to my HD2 tmobile. The proximity sensor was no problem. the screen can turn off when my face close to screen and my face is far to screen, the screen will turn on.
I also tested the lighting sensor. I put my HD2 under the strong sunshine, screen will light strongly.
If I re-installed the android rom NAND. This problem will be issue. I tried more than two ROMs. The result is same.
Sorry, maybe my english is not good.
johncmolyneux said:
Thanks, but that's clearly just an issue with the Android build you're using. Try another one and see if it's better.
Click to expand...
Click to collapse
Thanks for the info...
If I change my build I el let it know here... For the moment, I can survive with this...
Sent from my HTC Desire using XDA App
jackykwan said:
I tested my HD2 again. I restored WM6.5 to my HD2 tmobile. The proximity sensor was no problem. the screen can turn off when my face close to screen and my face is far to screen, the screen will turn on.
I also tested the lighting sensor. I put my HD2 under the strong sunshine, screen will light strongly.
If I re-installed the android rom NAND. This problem will be issue. I tried more than two ROMs. The result is same.
Sorry, maybe my english is not good.
Click to expand...
Click to collapse
then it can only be an issue with the nand builds unless the nand builds have use of an additional sensor not used in wm6.5..
Hi.
Readed all this thread. Also one other same situation, described on HD2 Android Q&A and General forum on thread "[Q] screen goes off if I make a phone call".
I can confirm that this issue goes active with Android NAND builds. Not matter, is it Froyo or Gingerbread. I tested lot different roms. Best results i got on PureGingerbread gpc_hd2_gingerbread_v1.3 and with SetCPU on conservative. On somewhere proposed smartass didnt work.
Actually i dont remember this same bug, when i runned Android at SD.
Now i placed back stock win rom and all works perfect. This shows that my hardware works correctly. But i dont like winmo (also winphone 7 is unripe and i dont like it too). I want use Android and not at SD. Must i go to change phone and loose todays best smartphone (my opinion)?
I dont know fundamental of Android and dont have time to learn it too (so many works and other things todo). But maybe some rom or kernel chief can handle this and overlook things that operate with Proximity or Light sensor.
I dont have so many posts yet that post this to my preferred rom thread. I dont want go spam over forum to get post count bigger. this was reason why i posted my opinions here.
Finally sorry about my poor enlish.
I heard so much meanings where the reason could be and i have to end up my whole life without solving this problem.
in my case it's not os-dependent.
i never needed my screen to turn off while talking, the hd2 is very big and with android there's nearly no chance to push any button and with wp7 the same, so why i should be angry about this problem. my sensor won't recognize anything anymore, that's enough for me ^^
http://forum.xda-developers.com/showthread.php?t=951858
This sounds very interesting. The proximity sensor of the Desire HD of most people was not correctly calibrated so it won't work good and they got the same issues like we do with our beloved HD2. Check out the thread and the app. I'm not sure if it works, but you can give it a try. I'm not able to use it, because i deactivated my sensor in a hardware-way xD !
Silberpfeil3110 said:
http://forum.xda-developers.com/showthread.php?t=951858
This sounds very interesting. The proximity sensor of the Desire HD of most people was not correctly calibrated so it won't work good and they got the same issues like we do with our beloved HD2. Check out the thread and the app. I'm not sure if it works, but you can give it a try. I'm not able to use it, because i deactivated my sensor in a hardware-way xD !
Click to expand...
Click to collapse
Hello
I have this problem since 2 days
And i test it
now my phone not turn off during a call. screen stay on.
Hey, I 'd like to first say, great roms and support here on the forums! I absolutely love how open the community is with the HD2!!
I have a weird issue with the phone however. I am using the HD2 clean rom, wp 7.8, and Android ICS in dual boot (wp 7.8 NAND & ICS in SD).
Whenever I talk on the phone on windows phone 7.8, the screen turns off and I can't press any buttons. I have read the system has this symptom due to failing proximity sensors, but mine's i'm 1000% sure is not failing. on wmo 6,5 it works perfectly from what i see. On android it works perfectly too! I've tested it multiple times touching and untouching and it works perfectly. Just on WP7 it's glitchy, any feedback is very well appreciated! I dont want a bandaid fix, if possible i'd like a resolution to this problem.
Once again, thank you all!
this is normal... all WP7 screens goes blank (off) because is possibility to end call if you touch screen with your ear but when move phone from ear screen must go on again....
dxdy said:
this is normal... all WP7 screens goes blank (off) because is possibility to end call if you touch screen with your ear but when move phone from ear screen must go on again....
Click to expand...
Click to collapse
Ohh, I know it's a common thing, but mine's doesn't even turn back on. it shuts off as soon as i even make teh call (i don't even have to touch my ears to it).
I can even take a video recording of it if everyone would like. Maybe that would help.
no need... some people already reported this... WP7 not work same on HD2 for all users... someone have a lot problems others not...
Ahh..... So is it something random that happens? I'd like to know so I can hopefully find a remedy
Once again, ty for your help dxdy!
my Phone has the same .. black screen on a call and not coming out of black screen anymore????? are there fixes yet... this is a terrible "feature"...!!
Hello ,my HD2 has the same problem.. black screen on a call ,and doesn't turn back on when i move phone from ear , screen turns on only when i end call .
My rom is HD2 Pdaimatejam Rom Wp7.8 OS 7.10.8862.144 v8.8 >Auto Activation Code
sebeq