Related
Hi all.
I have recently flashed my Herm to have the fantastic Black MAJIK rom. All went very well and I was pleased with the rom. I did have issues with the wireless not working and also with the blank screen detailed below.
When HTC released the update for WM6 for the TyTn, I decided to flash to that rom and give it a try. Again, works well, although I had to flash back to Radio 1.38 to get the Bluetooth to work properly with my Jabra headset. (I am on Orange in the UK - have not tried 1.43, as could not find it!)
The big problem is this :- randomly (could be 6 hours, could be ten minutes), the phone does not wake up from sleep. The lights are still flashing (I have not tried calling the phone - I will do that next time), but it will not wake up. No ActiveSync at all.
Soft reset is the only viable option.
Does anyone know a fix for this? (Yes, I have roamed through a number of forums and tried the link for 'DisableSyncSchedule', but that did not work.)
I have tried to re-flash the rom a few times, even soft-reset before the HTC stuff installs, stopped GPRS traffic and made sure that the IMAP does not connect. Whatever I do, the problem persists.
I have installed the following: HTC TyTn rom:
- SPB Diary
- SOTI Controller
- mfrazz CommManager
- WMG 3G Video Black Keypad
- GreenBatteryFix
- HTC X-Button
- Pimp my Black
I am loathed to revert to WM5, but if that is the only way foreward, then I might need to.
Any help would be superb!
One other thing
Sorry, meant to say that I am currently running with just the base HTC rom and nothing else installed. Let's see how that goes.
First, The radio should not have anything to do with bluetooth. This is the radio rom for cellular calls, not the BT radio.
BSoD question: Do you have a media card? Have you installed apps on the media card? There have been issues with the media card falling asleep. I had issues in the past installing applicaitons on the card. As make sure that you configure mail NOT to store messages on the media card.
Next....Uninstall all applicaiton that you have installed. Do you still have the problem? IF this fixes the problem, reinstall apps 1 at a time untill you figure out which is causing the problem.
I do have a memory card installed, but no apps are installed from it and the mail attachments are not stored on the card but in the memory. I have recently reset the mobile and have noting installed (not even ext rom) and have only set up mail, sync'd and configured for Orange.
Interesting about the radio having no affect, as it made the Jabra work - no other changes made. (I have re-flashed since then, but still using 1.38 radio rom.)
So I get this all the time, I don't have an SD card - so its not an SD card issue.
I've got 2 Tmobile MDA Vario II's and ever since upgrading from the stock Tmobile rom the phone will hang with a black screen but the message light will blink. If I put the phone in flight mode it never does it.
Its happened on the following roms:
XDA Mobile / Faria's rom
All the Black roms
LVSW
It didn't do it with Tmobile WM5 Rom. Tried various radio updates and it doesn't seem to make any difference. I know Jasjammin mentioned he had seen it but nothing further from him on this.
ITS DRIVING ME NUTS
Some other people must be seeing this also? Please help. When it happens no mails/sms or voice calls so its like the phone is switched off. I too am now looking at downgrading back to WM5
I'm wondering if it might be in the boot loader / rom flasher issue? But I sure I've not done anything others haven't done.
Regards,
Neil.
Bump - nobody else seeing this? Find it hard to believe?!
prophetuser said:
....The big problem is this :- randomly (could be 6 hours, could be ten minutes), the phone does not wake up from sleep. The lights are still flashing (I have not tried calling the phone - I will do that next time), but it will not wake up....
Hi prophetuser
I did notice this issue in the new HTC WM6 ROM (not the dopod one) which you have mentioned. But I flashed my ROM to Black Majik and its cool....I didnt notice this problem.
My device is imate JASJAM. I think the black majik ROM is better, but I noticed one more post in this thread mention all black ROM had the problem as I have not come across it yet.
Maybe the new Black Satin which jasjamming is cooking will not have it and probably you may have to try it, until a new HTC ROM update is leaked I suggest you to use black majik.
Click to expand...
Click to collapse
read my post
100% solution
SOD CAUSE
IN my whole 6 months having my hermes i had never had SOD until i flashed the official dopod rom with matt kitchen. when I traced the source that SOD had came from it was a bad extended rom flash i done. This cause the device to go sleep after the screen time out, and also if i put the phone in idle mode i had to soft reset everytime.
i flashed an original operator t-mobile rom with the extended rom and all my problems went away.
My device has never been quicker no more SOD and battery life is superb with the new radio 1.47 after one whole day with normal use with 3g internet I am still on 70% battery life.
Now I have the perfect device and i think hermes WM6 crave and addiction will be thinned out as there is not much you can do now with the hermes as to wait for PROTON or fully integrated touchflo working ROM.
p.s
TRY FLASHED A AN ORIGINAL OPERATOR ROM WITH THE EXTENDED ROM YOU CAN USE ROMKOCH TO EXTRACT THOSE TWO AND FLASHED YOUR ROM BEFORE FLASHING WM6 AND GUANRANTEE YOU WILL SEE AND FEEL A MUCH MORE RESPONSIVE HERMES. THATS MY 2 cents
duttythroy said:
....i had never had SOD until i flashed the official dopod rom with matt kitchen. ....
What is SOD? please mentione as I am new to the terminologies
Click to expand...
Click to collapse
SOD= Sleep Of Death
Definition of SOD
1. A piece of dirt and grass, usually found stuck to the bottom of shoes after running (Or walking) On a muddy field.
2. Short for "Sodomy", meaning anal sex, which comes from the Sodomites of Sodom. This term, usually used in a derogatory manner, can be used to say **** off, as in "Sod off" or it can be used as an adjective "That sodding bastard"
3. An idiot, a fool. Someone you dislike.
4. S(Screen/Sleep) O(of) D(death) - Blank screen nothing happens..
Examples
Man, all this sod was stuck on the bottom of my shoe, and even worse, it dried out and now it's hard as a rock!
Look at that sodding bastard over there, scoping out girls he doesn't even have a chance with when they're drunk!
F'ing sod spilt my drink, and i wasn't having any of that!
Arghh FFS !! Me blinkin phones crashed again, I soo hate you SOD's.
loool ripdool . nice definitions
duttythroy said:
IN my whole 6 months having my hermes i had never had SOD until i flashed the official dopod rom with matt kitchen. when I traced the source that SOD had came from it was a bad extended rom flash i done. This cause the device to go sleep after the screen time out, and also if i put the phone in idle mode i had to soft reset everytime.
i flashed an original operator t-mobile rom with the extended rom and all my problems went away.
My device has never been quicker no more SOD and battery life is superb with the new radio 1.47 after one whole day with normal use with 3g internet I am still on 70% battery life.
Now I have the perfect device and i think hermes WM6 crave and addiction will be thinned out as there is not much you can do now with the hermes as to wait for PROTON or fully integrated touchflo working ROM.
p.s
TRY FLASHED A AN ORIGINAL OPERATOR ROM WITH THE EXTENDED ROM YOU CAN USE ROMKOCH TO EXTRACT THOSE TWO AND FLASHED YOUR ROM BEFORE FLASHING WM6 AND GUANRANTEE YOU WILL SEE AND FEEL A MUCH MORE RESPONSIVE HERMES. THATS MY 2 cents
Click to expand...
Click to collapse
hi mate, is it possible for you or someone else to give more specific instructions to do this? I am running Sleuths rom which i am v happy with apart from SOD every now and again in the mornings when the phone has not been used for hours whilst i have been sleeping!
thanking you in advance.
yans.
I am running an unlocked 8525 showing on boot
M05 R1.16.00.60
S04 G32.53.7018.01H
B06 D 3.62.07.DVH
I have installed CRCs r10.04 dated fifth May and WiFi seems to be auto enabled on boot with no appreciable power problems
As soon as I start using the phone, everything starts to go wrong at once: It will make a call but then not receive any at all. And it wont easily turn on or off. Taking out the battery resets the unit, - obviously. otherwise the unit starts heating up and the screen acts sluggish freezes often after I have made a call. I dont remember the last time it actually received a call!
The only program which starts on boot is iFonz. Whatever else is wrong with it, it clearly needs reflashing though I dont really know with which ROM. Is there some incompatibility between iFonz and the Hermes? Or is this a clear case of flash with a Cingular ROM and then with whatever ROM you want? (BTW this is actually the first Rom I have flashed to this unit after unlocking)
iFonz
licensedtoquill said:
I am running an unlocked 8525 showing on boot
M05 R1.16.00.60
S04 G32.53.7018.01H
B06 D 3.62.07.DVH
I have installed CRCs r10.04 dated fifth May and WiFi seems to be auto enabled on boot with no appreciable power problems
As soon as I start using the phone, everything starts to go wrong at once: It will make a call but then not receive any at all. And it wont easily turn on or off. Taking out the battery resets the unit, - obviously. otherwise the unit starts heating up and the screen acts sluggish freezes often after I have made a call. I dont remember the last time it actually received a call!
The only program which starts on boot is iFonz. Whatever else is wrong with it, it clearly needs reflashing though I dont really know with which ROM. Is there some incompatibility between iFonz and the Hermes? Or is this a clear case of flash with a Cingular ROM and then with whatever ROM you want? (BTW this is actually the first Rom I have flashed to this unit after unlocking)
Click to expand...
Click to collapse
I am also using an AT&T 8525 and use the ifonz program and have no difficulty using it - now, I do not have it starting on boot, so that may be an issue with your device. Could also be the ROM? I have used several ROMs and use the ifoz program on all of them and have no problems.
Azomus said:
I am also using an AT&T 8525 and use the ifonz program and have no difficulty using it - now, I do not have it starting on boot, so that may be an issue with your device. Could also be the ROM? I have used several ROMs and use the ifoz program on all of them and have no problems.
Click to expand...
Click to collapse
Hate to sound lke a newbie but I was hoping I wouldnt receive a message like yours telling me that iFonz works with lots of ROMs. I suppose i should reflash another ROM anyway (MaRaHox seems to be flavour of the month at the moment and I tend to stay with successful flashes) and wonder how I can isolate the problem?
Even worse, mine is a direct flash from Cingular (meaning there is unlikely to be interim corruption which could be cured by reflashing the manufacturer's ROM) so I cant really reflash the Manuf and hope the problem will go away
I would go for CRC 11.2 myself, Thats what MaRaHox's is based on, well, no I think his last rom was based on 12.3 (?)
I use CRC's 12.4 and find it very fast and stable (bar glitch between HTC button (yuck) and the themes)
hey guys i have a few questions and things i need help with
first, what i'm running
at&t tilt 2 (you know...a touch pro 2)
htc official rom with sense 2.5 ( the new one...i think the newest, havent checked in a while)
and i have a few problems with my phone
1. i want to change the settings icon on the start menu to NOT go to the sense settings...if i wanted that HTC i would go to the damn settings tab on the home screen...since thats all the shortcut does anyway...sorry to you guys, it just seems stupid that they changed it.
but yeah i want it to go the the original settings
2. ive done some things to my phone that have...well...f***ed it up
firstly, installing the energy 23*** march 9 2010 series rom...no offense to nrg, but it totally ****ed my phone, because the problems dont go away with a new rom and hard resetting, for one, i cant use speakerphone...it just mutes me, and other problems, like, if i have headpones in and someone calls, if i answer, then i am muted to the other person, then i have to call them back, and if i try to take out the headphones because they cant hear me...it is still muted anyway...and it used to work right before the energy rom, same with every problem i have (except the settings thing) and also when i have headpones in, sometimes it only ring out of the headpones, so if i dont have them on at the time, and they are still plugged in, i wont hear it ring
also, sometimes during the night my phone will freeze while it sits there, and because i use it as an alarm....really frusturating when it doesnt go off, again, since i installed the rom, but happening more often since i put android on here (the recent build freezes all the time anyway, not worth it...yet)
an example would be this morning when i need to get up for college and it doesnt go off...
umm...what else...oh yea...it always happens...either the startbar freezes and kinda goes away...or sense does and this is very annoying since i have to soft reset all the time, and especially since it wont even let me turn sense off because the settings wont work because sense isnt working and cleanram doesnt work for that either
sorry if im coming off as angry im just...well...angry, but its just so frusturating with all these problems just from a rom
now a question...
will these problems go away if i install stock rom and hard reset? because i have official rom and hard reset and it didnt change anything
i love this new rom, its great, but it has the problems from the energy rom still, and its not the rom, its just registry entries or something that a hard reset wont fix...but i dont see why a new rom wont fix it, but anyway, sorry for all the writing, but im bored waiting for my class to start
sorry if you think im rude also, i love htc, i love the team that is working on android for rhodium, i love nrg's roms, i love xda, and i love all you guys, the community
thank you
run Task29. Look for it in the rom development section. This will clean you're phone memory and that will resolve most of you're problems. Then install the rom of you're choice.
thanx, and do you know of anything that will change the settings shortcut back to the original?
You man that shortcut that takes you to Sense settings instead of the Windows Mobile one?
exactly, with the only way of going into the windows mobile settings by going through the sense settings, so if sense is frozen or just not working, no way to go into settings...dumb
nicc51591 said:
exactly, with the only way of going into the windows mobile settings by going through the sense settings, so if sense is frozen or just not working, no way to go into settings...dumb
Click to expand...
Click to collapse
In the registry go to [HKLM\Security\Shell\Startinfo]
and change the value for "HideSettings" from 1 to 0.
Then remove the link to HTC Settings for "Windows\Start Menu\Programs".
After a soft reset, you'll have a default settings link.
thanx, hopefully this fixes it (it looks like exactly what im looking for)
Hello XDA Rhodium Community!
I've been lurking these forums for a few weeks since I purchased a TP2 about a month ago.
I own a Verizon CDMA TP2 and GSM unlocked it for use with my T-Mobile sim card (pay as you go). I have successfully tried many of the custom roms available here and settled on using Mr. X's latest Sense UI release for it's excelllent speed.
The phone worked great for about 2-3 weeks before I started to get a problem with my backlight/screen.
If, for any reason, the screen goes into sleep mode or shuts off it WILL NOT COME BACK ON until I reset the phone. The screen dim function no longer works either, it's either 100% brightness or it's completely off. I re-flashed to many different ROMs (including Verizon stock and the Bare Naked ROM), ran task29, reset storage, and anything else I could think to wipe the memory and the problem continues to occur.
Needless to say this is very annoying. I've been working around it for now by turning off ALL POWER saving options and attempting to keep the screen on at all times, but it will still turn off if I place my head on it during phone calls or accidentally press the backlight button on the top.
Anyone have any clue how to fix this? I love this phone and really don't want to have to buy a new one because of this
Has anyone else run into this problem???
well mine sometimes does this... however tis like if i try messing with it when its booting up... if i leave it for the 5-10 mins it sometimes takes to fullly wake up then its fine.
I always allow it to fully boot before using it. It wake up again no matter how long I wait.
Anyone have any ideas?
Hi
Having just joined the Touch Pro 2 club from the Touch Diamond 2 and creating a custom ROM, the only thing i can think of is this:
CDMA TP2's have a few things different in hardware to the GSM ones.. Perhaps there is a driver conflict now causing a SOD (Standby of Death)
Craig
I am having the same problme as the OP. I've had my Verizon TP2 for over 6 months without this problem, the last 2-3 months running a custom ROM. A few days ago the SOD started and I have not found a solution. I have cleaned it with Task29 and tried a number of ROMS (including going back to the "official" VZW MR1/WM6.1 release) with no luck. I'm now running Android in order to get through the day. I think the only solution is a hardware exchange with VZW (although it's not a hardware issue).
Try installing LUMOS to avoid SOD
i have a couple of TP2 with the SOD problem.
I read several post recommending LUMOS, so i did a quick test and it seems that it's really solving the SOD and also giving a little more battery dimming the screen.
Give it a try and let us know your comments.
I've tried LUMOS, but no luck. WM can't control the brightness and neither can LUMOS. I'm starting to wonder if I've got a bad light sensor.
audiomixman said:
I've tried LUMOS, but no luck. WM can't control the brightness and neither can LUMOS. I'm starting to wonder if I've got a bad light sensor.
Click to expand...
Click to collapse
You've got the wrong backlight.dll driver. I had this while experimenting with Topaz drivers on my GSM Rhodium. I also got a Standby of Death (SOD) with the Topaz drivers.
Craig
I'm all up for trying a different driver, but I've hard reset a number of times and flashed back to carrier ROMS with no luck. Wouldn't that have put the correct driver back? I was also running a single custom ROM for months with no changes with the SOD started to happen. Howevere, if you could post the correct driver, I'd appreciate it.
Hi,
I am also getting this problem, mine is a GSM, original rom was from vodafone uk, 6.1. I am on my 3rd tp2 from vodafone after complaints of this problem and within a couple of months use i get the SOD.
Its not as bad as the OP but i normally get the SOD a number of times per week. I have tried my first custom rom a couple of days ago (deepshining x10.235xx, i love it) with the aim of solving this problem but since i have had SODs 3 or 4 times in the last two days.
I am wondering if its a memory/ram issue as my TP2 after boot up starts with about 60-65mb free ram and with a little use the best i can get with all programmes closed is only 45mb (after using clean ram).
i do not believe it is a hardware issue because i have had the same problem with 3 phones now.
any solutions please let me know.
@audiomixman - when you flash back to carrier, do u flash back to the shipped SPL, ie remove HardSPL? I'm unable to post the correct driver as i think it needs to be cooked into the rom. I also have the GSM ver.
@rob_cunningham - I wouldn't think its memory as i routinely get down to 22mb with opera and music n about a weeks use. I also would guess if you've HSPL'd it, that could be the issue.
I don't really think its a hardware issue, more driver / poss HSPL
@both - does it happen on a clean hard reset build with no other software installed?
Craig
Craig,
I haven't removed the HardSPL because all the notes on the relocker thread say to only do as a last resort before returning device for warranty purposes.
Without removing the HardSPL, I have reverted to my carrier's 6.1 and 6.5 ROM releases and still get the same result without any software reinstalled. Right now I'm back to booting up with MightROM but with nothing installed. Once booted into WM, I go to Android. At least with Android while the screen won't quite turn off (it goes to "black" but the backlight is still on), it will come out of standby.
If you search, you will find many casues of SOD, although essentially there are two primary causes:
-Bad light sensor (actually pretty common)
-Conflicting drivers / IRQ overlap
for many, unchecking the box that allows WM to automatically control your light settings does the trick, others that does nothing. If you have a a bad light sensor, this usually works.
If you have a driver issue or IRQ conflict, usually not and going to a new ROM can help, but not a cooked ROM, as there are so many variations of hardware/software combinations for the TP2 in various countries / carriers that only real solution is to get back to the original shipped state of the phone with the carriers ROM and experiement from there. Many of the add-ons, like photo software, games, utilities all have some code that uses the light sensor and screws up the IRQ settings.
For me, I had the problem with the original ATT ROM, but the recently released update with Sense 2.5 solved my problem.
Good luck, not an easy one to find a solution to.
Hmmm, in that case, i'm lost sorry.
As the previous post mentions, I don't use the automatic backlight (and never have) you could try disabling it and seeing what happens.
Craig
Hello all, First, I searched the forums for my answer with no such luck, that being said if Im repeating a question thats been asked I apologize. I have a problem with keeping android stable. I have flashed with different versions of windows several times all with success. I do however, prefer the android system, I find that it runs much better, faster and has better perks. Everytime I flash following the original how to, I run in to a couple similar problems.
The first is when I hit the power (not hold the power) the back light cuts off and the keyguard enables, the screen goes dark all as it should. Depending on the time ( the longer it is the worse it is) when I hit the power key to revive my phone, I often get a white screen, then it waits , then it goes dim, Sometimes If I hit the power button several times it eventually comes back to the key guard option, but others I have to remove the battery and reboot. This is the major problem, as I cant use my phone when I need it. This problem seems to get worse the farther it gets away from the flash date, e.g..,, after a brand new flash it works pretty good and then it goes downhill from there.
Second, it seems to lock up when I let it charge overnight, not always (but most of the time) I get up, click the power button to revive the phone and I have a white screen before me that is frozen solid. This like the previous problem seems to be linked to the distance from the last flash.
I hope that its something Im doing wrong, as Im currently using wmobile 6.5 and since Ive had a taste of the droid os, my wm phone is just disappointing. And as I was unsuccessful in finding a post that adequately describes my problem ,Im hoping that there is a way around this .
I have tried, Incubus Superfroyo, Wrym warm donut, and Cyanogens build. Im sure Ive tried others, they just escape me, I was re-flashing daily until I went back to windows. I truly hope someone out there has encountered what I have and has a solution. thank you all for what you do, these forums have been extremely valuable and helpful.
Sounds like you have the wrong panel type selected. Is it set to auto? if it is, try setting it to 2 instead. That cleared up the problem for me.
Tried all panels all have the same problem.
Well thanks for all the many replies. I give Ive tried everything on this site and m android is still really glitchy. Guess it will be windows until I get perhaps a phone capable of running android smoothly.
What kind of phone do you have?
Sent from my HTC Vision using XDA App
do you have an SD card you can try to boot from and share your settings?
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
I know, I know that MANY PEOPLE THINK OF THE WAKE UP WHITE JIBBERISH SCREEN as NEVER WORKING.
PoXFreak said:
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
Click to expand...
Click to collapse
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
srlebonv said:
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
Click to expand...
Click to collapse
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
You say that often install with data on the sd card causes lock ups and freezes. Can you explain further what you mean ?
dark_prince said:
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
Click to expand...
Click to collapse
Ok, so I installed your version of froyo, the accompanying 2.6.25, the radio that you use. For the most part the hanging up is fixed. Now the second problem is still in place. Sometimes when Its been in hibernation(or whatever you would call when you hit the power button once ) when I attempt to refresh my phone (hitting the power button once) nothing happens, the green light is still blinking at the top but the screen stays blank, normally have to remove the battery and restart to get back to using the phone. Is this a sleep setting? or is this something Ive done wrong during the installation.