I have a problem with my HTC Tilt 2 where the keyboard stops working randomly. I will go to compose a text message and nothing will respond except for the space bar. The space bar then opens up the start menu instead of moving the cursor over. I have tried multiple versions of the Energy ROM. I had a July 24th 2010 version of the Energy ROM that worked without any issues with the keyboard. I enjoy trying different types of the Energy ROMs and have tried almost all different variations of them in both the 21916 and 29020 builds. The July 24th version of the Energy ROM was the only one that has worked without issue. I really like the Energy ROM and currently I have the April 8th of the Energy "sencity" ROM in the 21916 build. In all of the ROMS that i have flashed to my phone i have used the carrier provisioning that comes with the ROM to povision the keyboard settings to AT&T. That has successfully mapped the keyboard correctly but the keyboard itself still stops functioning randomly. Please if you know the fix to this issue I would love to know what it is. Thank You!
I'm new here and don't claim to know ANYTHING...but....I don't remember a carrier provisioning keyboard fix for the Tilt2 included in the ROM, I think it's a cab file you have to install after you've installed the ROM which you can find on the Home Page of Energy Rom here...
It's possible you've already done that and are referring to the fact that your keyboard is malfunctioning as opposed to not being remapped correctly...if it was working fine before you flashed the ROM maybe reflash the stock rom and then reflash the Energy rom and then install the keyboard fix cab....
I've never been clear on what carrier provisioning does since part of the start up routine has you select your carrier so what else is there to do? At any rate, when I have run carrier provisioning for kicks it has never fixed the keyboard or done anything else that I could observe. I apply a separate cab to remap the keyboard.
The carrier provisioning adjusts "something" (I don't know what it is) and I think installs "something" (I don't know what it is either) that should coincide with the MMS Fix cab installation that allows for larger MMS pictures to be received (and possibly sent)....at least, for the AT&T Tilt2...the first carrier provisioning is to run on TMobile or AT&T or whatever service provider is available from it, there is a Carrier Provisioning 2 setting for the MMS Fix Cab of which I am referring
hope this help
I get the same issue with the phone as well where my keyboard & i have to use the screen keyboard. I have to restart the phone in order for the keyboard to work since it does me no good for me to keep using the onscreen when i want to use the actual keyboard on the phone. This has been going on with any rom that i use. Lately the issue i am getting on my phone as well is that it shuts off on its own or it not charging right. going to upgrade soon. I love this phone but time for me to get something new.
I read elsewhere that someones battery contacts inside the phone had lost some of their "spring tension"...meaning they didnt push out enough to make enough pressure against the battery...they applied electrical tape to the opposite side of the battery so the battery fit more snug
if the battery is not making good contact with the terminals it won't charge well..if it is loose enough, it will lose contact while the phone is on and the phone will turn off..it can be loose enough to turn the phone off, and then by repositioning the phone in your hand while you're turning it on again that the battery repositions slightly to re-establish contact for the phone to be powered on...and when you set the phone in it's holster or pouch, a slight jarring or repositioning knocks the battery loose again and the phone shuts off...
jakerg89 said:
I have a problem with my HTC Tilt 2 where the keyboard stops working randomly. I will go to compose a text message and nothing will respond except for the space bar. The space bar then opens up the start menu instead of moving the cursor over. I have tried multiple versions of the Energy ROM. I had a July 24th 2010 version of the Energy ROM that worked without any issues with the keyboard. I enjoy trying different types of the Energy ROMs and have tried almost all different variations of them in both the 21916 and 29020 builds. The July 24th version of the Energy ROM was the only one that has worked without issue. I really like the Energy ROM and currently I have the April 8th of the Energy "sencity" ROM in the 21916 build. In all of the ROMS that i have flashed to my phone i have used the carrier provisioning that comes with the ROM to povision the keyboard settings to AT&T. That has successfully mapped the keyboard correctly but the keyboard itself still stops functioning randomly. Please if you know the fix to this issue I would love to know what it is. Thank You!
Click to expand...
Click to collapse
Might seem like a dumb question, but: do you task 29 or flash a stock ROM before flashing the new ENERGY ROM? I always Task29 before flashing but, sometimes when really weird things happen, I find the cure to be the following procedure:
1 - Hard Reset and boot into bootloader (don't let ROM boot again after HR)
2 - Task29
3 - Flash AT&T Stock ROM and let it first boot all the way through setup to the home screen
4 - Hard Reset
5 - Task29
6 - Flash new radio (if necessary)
7 - Flash new ROM
I also use the attached cab for setting up my keyboard (I think it's actually NRG's cab)
Of course, sometimes its just the ROM itself that is buggy. I am an avid ENERGY user myself, but there have been a few builds that were not as great as some of the others.
Hope this helps!
-Mark
AT&T Tilt 2
HSPL 0.85
ENERGY 29020 Sencity (Apr 29)
No i haven't tried task 29 normally all i do is flash the new ROM on and I don't put the stock ROM on first. I will try doing that to see if it helps thanks. The tilt 2 does have a carrier provisioning built into the ROM but it installs a separate CAB when you run the provisioning tool. I have tried that way and I've also tried the stand alone CAB for the at&t keyboard layout from NRG i believe. Both ways still have the same issue. Both ways correctly map the keyboard. What is strange is if I go back to the Energy ROM from July 24th 2010 it doesn't have that issue and the keyboard works just fine. I don't flash the stock ROM or anything before going back. I like that version but for eye candy and enjoying new stuff i want it to work for newer ROMS. Thanks for the responses I will try doing what you have suggested.
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.
it happen to me several times as i finish a phone call and go back to the Today screen but on the left top corner still display the title "phone".and i cant press it to open the start menu when im at the Today screen not even the start key works.try hold down the power button to shut down but no luck.but everything still works at the Today screen (weather,music plug-in etc)
had to soft reset it.anyone have this problem as well?or is it a radio problem?
iluvgillgill said:
it happen to me several times as i finish a phone call and go back to the Today screen but on the left top corner still display the title "phone".and i cant press it to open the start menu when im at the Today screen not even the start key works.try hold down the power button to shut down but no luck.but everything still works at the Today screen (weather,music plug-in etc)
had to soft reset it.anyone have this problem as well?or is it a radio problem?
Click to expand...
Click to collapse
I use this rom with 1.51 radio till the rom is issued. I never had to soft reset because the rom crashed. The only really annoying issue i had is the bluetooth's one (Time to time, it is impossible to reactivate bluetooth without SR. This is why i do not desactivate it anymore ). We can always argue on choices, taste and colors but this rom is quite stable and fast enough for what i do.
EDIT: BTW check also which applications you have loaded. Did you reinstall a backup done with SPB after coming from another rom? I experienced many problems with that. Even if not pretty, i always reinstall now all my applications after installing a new rom (and i use pimbackup for calendar, contacts,... infos)
I have same problem too, thx
Post in Schaps 3.60 thread...
Not so as you think
I don't agree with that the ROM issue after call. Your deveice may be has some problem. What about bluetooth yes, there is some interesting moment that you select open bluetooth, it doesn't open, as soon as you mark to open you should restart your deveice, then it starts with opened bluetooth. BUt when you are going to turn the bluetooth off there is no problem.
I'm sure, Schap as a great moderator will solve this problems in next generation of his ROMs. The variation 3.60a (has posted), may be 3.60b, then 3.60c may be. Or he will post something interesting like Iphone platform.(I want him to do it)
iluvgillgill said:
it happen to me several times as i finish a phone call and go back to the Today screen but on the left top corner still display the title "phone".and i cant press it to open the start menu when im at the Today screen not even the start key works.try hold down the power button to shut down but no luck.but everything still works at the Today screen (weather,music plug-in etc)
had to soft reset it.anyone have this problem as well?or is it a radio problem?
Click to expand...
Click to collapse
I have the same problem too, what I have discover is that during the call and the screen is off (either it off automatically after a time or you press the power button) then anytime you power on the screen again in between the call or after the call in a short time the problem tiggered.
the only way you can 'fix' it is to wait until call end then off and on your screen once then the 'start menu' back or wait for an amount of time until the phone lock tigger (that one with number pad)
I said 'fix' (with quote) because this definitely a temporary solution to deal with this problem
hope schaps can get more idea in how to trigger the problem and can fix this soon
other than this issue, the rom is really very great
cheers.
To the OP,
If you are using a Hermes I suggest you reflash from scratch ie Schaps ver 3.6 rom, then use radio rom version 1.47.10..
Install ALL your applications from scratch, manually. DO NOT restore from a previous backup using, say SPB Backup; that will screw your installation. Make sure all your apps are the latest versions, capable of running under WM6.
Preferably install one app at a time, as you would anyway, then test the phone and make sure it is working before installing another app, and so on.
Don't install a theme changer or other similar software until you are absolutely sure your installation works. Leave the performance parameter settings as they are, ie at default.
If all else fails use the ROM combination in my signature below. Rock solid installation, no problems or crashes.
Let us know how you get on.
Cheers
WB
have same problem also has anybody found that if you use internet shearing and recive a call you cant hear anyone and phone searches for network
thankz,
jdc21
no crashing for me..
the rom is really stable.
apart from the bluetooth issue its really good..
really stable and fast enough..
works really great for me..
Thanks Schaps for such a great rom.
waiting for 3.60b
Take care that Phone Dialer Skin could cause this kind of problem
wacky.banana Is maybe right
I have Schap's 3.60a along with my trusty Radio 1.47.10
No BT Issue till now
I use BT also with DrYAR-Bluetooth 1.6 (Whoopy!) No Issues at all either starting or Stopping BT
I'm using It for two days now It's OK
Did I mention that this rom Is even FASTER than the previous 3.5x?
i hav the same problem
When did this problem start?
I didnt have the bluetooth turn on just using it normally.and all application i install is fresh onto the phone memory.never install any program on the SD card.about the dialer skin i use Schen Kaiser 3G dialer.
Anyone got fix yet?
Same issue, not just Schap 3.60a
massimo729 said:
When did this problem start?
Click to expand...
Click to collapse
I've had this same issue for weeks now, ever since the newer ROMs have come out for the official releases (i'll have to track back the build numbers). I had it with Sleuth's last release, the vp3G 3.0 release, and now Schap's 3.60. I've done what other posters have said and hard reset, not loaded any apps, and still have the issue.
I believe I have tracked it down to do with X-button, as that's one of the few apps that is installed without customizations in both Sleuth and vp3G (and I run it in Schap 3.60a). My next step is to run vp3G 3.60 lite, without X-button, and see if that really solves my problem.
edwinyuen said:
I've had this same issue for weeks now, ever since the newer ROMs have come out for the official releases (i'll have to track back the build numbers). I had it with Sleuth's last release, the vp3G 3.0 release, and now Schap's 3.60. I've done what other posters have said and hard reset, not loaded any apps, and still have the issue.
I believe I have tracked it down to do with X-button, as that's one of the few apps that is installed without customizations in both Sleuth and vp3G (and I run it in Schap 3.60a). My next step is to run vp3G 3.60 lite, without X-button, and see if that really solves my problem.
Click to expand...
Click to collapse
As a follow-up, I went to VP3G 3.60.1 install, ran the base install with nothing else installed and still had the problem. Still, the workaround suggested by others (putting the phone in standby and coming out) fixes the issue for me.
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)
I upgrade my phone to wm6.5 after the tmo stock rom is released, and am happy with it in general. However this is still one bug, which I searched but couldn't find anyone talking about it.
The customized notification and task manager drop menu will disappear after making phone calls using either speaker phone or sometimes with bluetooth. The problem is, it's not reproducible, but happens at least once for every three phone calls like that. The only way to bring those back is a soft reset which is kinda annoying. The only conflicting software I can think of maybe the smartlock I used, which is used to automatically lock the phone during standby or in the phone conversation.
Does anyone have a similar problem? I had similar problems when I was using wm6.1 stock rom (before the upgrade) but not nearly as bad (maybe once in 20 phone calls).
Thank you!
I had this problem when I installed a taskbar that technically wasn't for stock 6.5
This happens with the stock rom without any other taskbar installed.
Looks like no one has the same issue?
I've had it maybe not show up all the time without a custom taskbar installed, but never had to reset to get it back again.
Finally figured out this is actually associated with the smartlock I'm using.
Switched over to csdevctrl and symptom seems gone.
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