Persistent SOD with latest Jackos S3

---

Ok here's my scoop... My LCD/Digitizer crapped out and I had to replace it. At the time I had Jackos S2 JackFULL ROM. After replacing, I was getting SoD so much the phone was unusable. Now I flashed S3 JackFULL (1.7.0) and it is still plaguing me. Anytime the screen power toggle or suspend is activated, you cannot get the LCD to turn back on. With proximity locker activated, the LCD will become deactivated if you place your hand or any object within a couple of inches of the LCD.

I tried implementing Jackos patch from this thread. I ran RHO_S2_00895 and it had no effect. I also tried the OEMDrivers and replaced what was in the Windows directory...also no effect. Additionally I have tried to get the custom ROM fix but I don't know how to install that one (4 files one of which is _setup.xml)

So now I have disabled proximity locker, and disabled the power button from pushing the device into suspend or toggling screen power...a reasonable temporary fix.

What is failing? It is absolutely not the flex cable -- I've been in there and thoroughly inspected it. What is responsible for the proximity detection? Is this the light sensor or something else?

If you can tell me it is a failing piece of hardware, I'm happy to try to replace a component. But I'm not sure what else I can do with the software at this point.

Does anyone know what is responsible in this situation?

This patch is actually included in all Jackos ROMs.
The last software test I can imagine is to flash a stock ROM and see if this still occurs.
I'm not a "hardware guy" so I can't really tell what should you replace. But since the problem started from replacing the LCD, it might just be incompatibility of LCD/Digitizer with flex cable/MB. I read a few times that Rhodium had several different models/versions of LCD. Some of the wouldn't even work with some of the MBs.
This is just a speculation.

After many months I finally realized that this patch doesn't fix the SOD problem. It was intended by HTC to fix the lags that occurred randomly (for example while you listen music it used to interrupt the play).


EDIT: I'm terrible sorry for my mistake.

jazzer, does the screen come on when you slide out the keyboard or when you pull the stylus? I know that these are not fixes but just other options to wake the device when the hardware power button is misbehaving.

Oh, and I would uninstall proximity locker (or probably easier to just remove its shortcut from Windows/Startup) and disable auto loudspeaker... and anything else that uses the prox sensor (which FYI is not the light sensor but a separate device on the face of your phone just below the power button.

EDIT: I see now that you have already disabled proximity locker, good.

REEDIT: By changing the following registry entry:

HKEY_LOCAL_MACHINE\HARDWARE\OEM\KEYBD "KeyLock" = 0 (default is 1) then Reset.

You can use ANY device key to wake up your phone (ie send, back, menu etc.)

EDIT: I think I misread much of your post jazzer so my advice will probably not be of any help to you. When I first read your post I thought you COULD get the device to wake with proximity sensor. Sorry.

Did you perform Task 29 before flashing?

I did indeed perform Task 29 before flashing.

The screen will NEVER come back on under any circumstances once it has gone into power down.

The screen will not allow any change in brightness -- it is full brightness all the time now and eats the battery in about 12 hours.

The power button is reprogrammed using the Rhodium Keyboard controller (Tarkim maybe?) to do nothing on single click and use the long press to reset. But you cannot reset from password lock. However, in a well-lit room, you can very faintly make out some details even when the LCD is off. It is difficult, but I can tell if the password lock is on or not, get the p/w entered back in and then reset it.

I am concerned there may be multiple variants of the LCD and perhaps this one is not fully compatible. Could that be possible? The part number on the stock LCD was 60H00243-00P for my Touch Pro 2 model ST7377 (Fortress). I didn't look at the P/N on the one I received, I just slapped it in there since it looked exactly the same--I should have known better. So I'll have to open back up to see.

Has anybody seen this loss of brightness control before?

Also, proximity locker being disabled does not stop the proximity sensor when you take a call -- the screen then shuts off and you must reboot after each call (unless you use speakerphone to avoid the auto lock). There must be a quick hack for this.

Thanks for all the attention, guys.

Yes, I read about it some time ago on Polish forums. Probably the pin layout on the LCD connector are different than they should be for your model of TP2.

Also I'm sure there are different models of LCD displays on the market. I'll try to find the exact part numbers but I'm afraid they will not be usable for you since the problem was with a European non-branded TP2 T7373 (aka Rhodium)

I haven‘t...

---

I haven‘t seen the part of the thread where the situation occurs with the stock rom...I don‘t know anything and I never will but I‘d try that just to see what happens

Light Sensor

---

I think the light sensor has to be related. I just installed Lumos and it cannot get any read whatsoever. It always displays 0 regardless of the ambient light conditions.

Bad LCD, bad flex, or bad ground?

---

Originally Posted by jazzer1971

I think the light sensor has to be related. I just installed Lumos and it cannot get any read whatsoever. It always displays 0 regardless of the ambient light conditions.

Ok I've gone back into this phone and I see nothing wrong inside. There is no damage to the flex board with the light sensor, proximity sensor, LEDs and earpiece. All connections on the lower flex board are also intact and good.

The light sensor continues to report a reading of zero always. However, when the phone was disassembled on the bench, I used a power supply to keep it powered so I could jiggle connections. When I pushed on the lower flex board, I saw the lumos calibration sensor reading jump from 0 to 131072. I could not get any readings in between. The backlight cannot be manually adjusted -- it always shows full illumination. However, engaging auto-backlight does produce a one-time mild dimming of the LCD.

The LCD still cannot be resumed from sleep or suspend. So long as proximity sensor is disabled, the LCD will stay on until the battery dies or until you take a call by putting the phone to your ear.

I am at a loss as to what to replace. Should I try another LCD or replace the flex cable? I sincerely believe this is a hardware problem, not software.

Originally Posted by jazzer1971

Ok I've gone back into this phone and I see nothing wrong inside. There is no damage to the flex board with the light sensor, proximity sensor, LEDs and earpiece. All connections on the lower flex board are also intact and good.

The light sensor continues to report a reading of zero always. However, when the phone was disassembled on the bench, I used a power supply to keep it powered so I could jiggle connections. When I pushed on the lower flex board, I saw the lumos calibration sensor reading jump from 0 to 131072. I could not get any readings in between. The backlight cannot be manually adjusted -- it always shows full illumination. However, engaging auto-backlight does produce a one-time mild dimming of the LCD.

The LCD still cannot be resumed from sleep or suspend. So long as proximity sensor is disabled, the LCD will stay on until the battery dies or until you take a call by putting the phone to your ear.

I am at a loss as to what to replace. Should I try another LCD or replace the flex cable? I sincerely believe this is a hardware problem, not software.

I had a reading of 0 on one of my phones. I replaced the whole lcd and reused the ribbon if memory serves me right. If you don't want to invest any money I think that FRX07.1 rom does not use the light sensor, and can be ran off the sd card. That would let you use the phone as is.