yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wg5566:
It's NOT SOD AT ALL

On my device, in my case, it's proved to be nothing to do with so called SOD at all, neither has it anything to do with hardware defects or software settings. It's just a matter of 'Slow-Respond-on-First-Bootup-Because-Manila-is-Using-Up-CPU-Resources'.

If I switch the home UI from HTC Sense 2.5 to the Windows Default panel, nothing will be wrong on a very fast bootup and everything will be fast responding.

But HTC Sense is a different story, this lovely beautiful skin really takes a long time and consumes lots of CPU resouces to be fully loaded on bootup.

On the observation through monitoring the htc task manager and by using a stop watch: I counted the time from when hitting the Power button on a power-offed device.

And I found: On a fresh bootup, the COM5 system takes about 1.5 minute to be loaded. And then it takes 7 minutes for the HTC Sense to be fully loaded. Although in the first minutes already showup the home UI but manila.exe will keep running in background for another six minutes. And during this whole seven minutes manila.exe always uses more than 95% of CPU.

Because on the first 8.5 minutes after the turned on the power, the CPU is always fully loaded, all other activites will be very slow respond. If in case it turns into standby mode in this 8.5 minutes and we happen to want it back immediately. I found: After sliding-out the keyboad, it takes 12-15 seconds for the keyboard backlight to light up. And then it takes half to two minutes for the screen to light up.

But after manila is completed loading,ie. after 8.5 minutes of first bootup, the CPU is not overloaded and everything will be ok and will be puncturely responded.

So in my case it has nothing to do with hardware defect or settings, it is just the slow repond during the time when CPU is overloaded.

To avoid this, no need any fix, only need to do:

1. Try to avoid device to turn to standby mode during the first 10 minutes of bootup.

2. No problem if it turns to standy and we don't touch it in ten minutes. Everything will be normal after the manila.exe finished using cpu in background.

3. If it turns to standby mode and we happen to want it back in the first minutes. Ok, we just be patient, slide out the keyboard, hold it and wait, after 15 second, the keyboard backlight will be on, and then after another minute or so, the screen will be back.

So, please try it if you have same trouble, lucky if if's not SOD. I call it SOR, slow-on-responds.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Jackos:
There are two HTC fix packages labeled "Update for HTC Touch Pro2 Enhance the system stability". RHO_S2_00895 and RHO_S2_00924

You are talking about the second one, it contains latest manila.exe mode9.dll. This explains why your UI is responding faster. The first one contains drivers that have nothing directly do do with Sense.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] reachalex:
I still have the problem. I have a TMobile device that I am using with Airtel Carrier in Bangalore.

I am on a custom ROM developed by Energy. I have patched the device with the patch for Custom ROMS. I have been experiencing this issue since almost 2 months now.

I have resorted to using just Windows without Sense and that gives a better response.

With all this, I was unable to view the screen for the last two days and now it has come backup. Please suggest or advise if anything can be done to fix this.

I am planning to switch to an Android OS and then will let you know the outcome. Android is never Windows :-(
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Jackos:
I do not provide support for Energy ROM users. This patch is developed for European non branded devices and indeed it causes problems if installed on other Rhod versions (roms).

If you are experiencing problems with this patch, please uninstall it using the standard way.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] reachalex:
Where can I download your ROM's. I am unable to find a download. The links I tried keep looping. Could you please post a direct link.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jazzer1971:
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?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Skrobel:
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.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Jackos:
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.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Caldair:
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?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jazzer1971:
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.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Skrobel:
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)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] GT247:
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
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jazzer1971:
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.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jazzer1971:
Bad LCD, bad flex, or bad ground?

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.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wizardknight:
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.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jazzer1971:
I ordered a replacement LCD/Digitizer and put it in and there is absolutely no change. Can it be anything else other than the flex cable where the light sensor is? What now?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wizardknight:
There are only two other options. Bad cable or bad system board. I have never heard of a system board with that kind of a problem.

You are not using a case are you? I have seen cases that cover the spot where the light sensor is on the lcd. I had to drill a hole in one once.

Also did you get a new or used lcd. Maybe someone was getting rid of a lcd that worked, but had a bad light sensor.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jazzer1971:
I am not using a case.

Both replacement LCD/Digitizers were reconditioned. But I think the light sensor is not part of the LCD -- it is on the flex cable, right?

Is it possible that something in the firmware is no longer properly accessing the light sensor? Does it make sense to try to load a different build in before going to another flex cable?

The strange part is that normal screen power function stopped right when the LCD was replaced--that's what makes me think it is hardware and not the firmware. But what would cause a light sensor to all of a sudden stop functioning?

And then again, is it definitely the light sensor which makes the screen power toggle non-functional?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wizardknight:
The light sensor is part of the lcd. If you hold it up to a very bright light you can make out it't oval shaped location at the top of the lcd screen.

There is no harm in changing the rom. It doesn't cost anything. I would have tried that first off though.

You could try re-seating the cable. It could be off.

I do not know what causes light sensors to fail, but I know they do from time to time.

All that fails replace the cable, and hope for the best.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jazzer1971:
The oval shaped opening is just a clear part of the digitizer. That allows the light to pass through to the sensor which is soldered on the upper part of the flex cable. The oval is only covered on the very top layer of adhesive where the HTC logo is--all the other layers are clear. I've got a torn apart digitizer to verify that as well as an LCD/Digitizer in tact that is outside the phone. Inspecting them under a microscope shows nothing but clear plastic.

So it looks like flex cable is next after some firmware experiments.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] supermaxkato:
did your flex cable end up being the issue?
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jazzer1971:
No good news

I don't yet know but I tried all the advice in this post.

http://xdaforums.com/showpost.php?p=7018633&postcount=20

Multiple Task29 runs followed by a load of ManilaRUSH and then more Task29 then SleekBasic to get rid of the sense. Nothing will bring this screen back on. Installing LUMOS I still get readings of 0 on the light sensor.

I think I have to go and order a flex cable at this point. Give me another couple of weeks to answer your question. If this doesn't work I will be out more than $50 trying to fix this thing after a new LCD and a new flex cable.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] jazzer1971:
Flex cable / light sensor culprit

Replaced the flex cable and normal phone functionality was immediately restored! Bottom line is you cannot easily operate one of these phones without a working light sensor--its functionality is tightly wound into the suspend and sleep options.
[Xoom Accessories] The_Tech_Ninja:
Hey guys --

I just posted a video review of the KeviKevCase. I purchased it last week. I am not a reviewer, just grabbed my camera and decided to shoot a video about the case. Please forgive the quality, I just tossed something together for users who are still unsure.

http://www.youtube.com/watch?v=TRysHWqaLgc
[Xoom Accessories] thor17:
Thanks, but with that black pad you have in the background, it's hard to see anything of the case. You need better lighting.
[Xoom Accessories] The_Tech_Ninja:
I stay in a bat cave. I tried to lighten it up the best I could. Maybe i'll reshoot at work.
[Xoom Accessories] Alfahmad:
I bought this case and there are few funny things. Like as you mentioned in your review the devise is upside down

And this can cause some problems when you are watching a movie or playing a game and the screen software does not use the function of screen rotation you will found your self holding your xoom in odd way to play the game.

In addition, if you need to plug your xoom to the charger you can't close the case because the devise is upside down.

Otherwise, if these things does not really matter to you, an ok case.
[Xoom Accessories] Alfahmad:
Two pictures to explain what I am trying to say ....
[Xoom Accessories] The_Tech_Ninja:
Yeah kinda stinks, however I just flatten it out.

Overall for protection purposes the case is a keeper to me!
[Xoom Accessories] DroidHam:
I just ordered this, anyone see them in person?

http://pdair.com/catalog/product_info.php?cPath=11000659_11001165_11001166&products_id=32373
[Xoom Accessories] kevikevdottcom:
That would be the fault of the software not using auto rotation not the case if the xoom went in the other way when you had it in landscape the camera would be at the bottom facing your belly not your face.correct?
[Xoom Accessories] jlewis11:
I am sorry but that is just damn unacceptable .... they made the case to Carry the device upside down....that's bull sh*t...
[Xoom Accessories] The_Tech_Ninja:
http://xdaforums.com/showthread.php?t=1032469

I may look for a new case solution if I cannot find something for this...

This is starting to make me angry....
[Xoom Accessories] The_Tech_Ninja:
110 bux? I don't care how nice it is..
[Xoom Accessories] Zykhan1:
Same ruled out Otter due to the price and although this one looks good, ill be taking a knee
[Xoom Accessories] SPIDERTECH:
Lol um those of you saying its upside down.... turn it over. The small part where the case bends is the bottom. If you look at the other eBay auctions for this case you will see that you are actually holding it upside down. The back panel that folds into the notch is the back when you fold it around and not the bottom. This makes it where the device is almost standing up when it's opened.

I have the Motorola case that is sold at the Verizon and best buy stores and it opens the same way with the charging ports facing the inside of the fold.

This is how it should look when opened.
[Xoom Accessories] The_Tech_Ninja:
Umm then we flip it over and the cut outs on the back for the important things like SOUND, the front and back CAMERA are covered up now and the POWER button.
[Xoom Accessories] Alfahmad:
This is true. However, not all apps support the rotations and sad thing most of the games and video apps usually does not support it. though I understand your point the other possible options propaly will cover the camera ..

What about power cut !! you can't even charge your xoom if the case is closed !!
[Xoom Accessories] The_Tech_Ninja:
The more I use the case the more I'm getting annoying. I need to open my case and lay it face down to charge my phone at night.... Now, I have to flatten out the case to play a game.. it's starting to making me a bit mad. Hopefully he comes out with a different version and allow us to exchange if we are not happy. Something needs to be rethought out or something.
[Xoom Accessories] SPIDERTECH:
If you use it like the op who posted the video did (upside down) then yeah, the cameras would be at the bottom, the speakers would be facing the surface you have it set on, and the power button would facing down.

If you stand it like it's shown in the product pictures (right side up) the cameras are on top and when you turn it around everything is up top like it's supposed to be.
[Xoom Accessories] The_Tech_Ninja:
That appears to be a work around. Do you really think it suppose to be this way? If so, its not stable at all.
[Xoom Accessories] Alfahmad:
I made a cut for the power charger this the only way around i found
[Xoom Accessories] The_Tech_Ninja:
unless kevykev want to work with me. Ill be taking my talents to another case developer.
[Upgrading, Modifying and Unlocking] mohammeda:
if anyone working on wm7 for galaxy tab, i would like to get the uncooked rom so that i can help out in finishing it

thanks

Sent from planet earth
[Android Software/Hacking General [Developers Only]] DABenji:
As google now have added map cacheing to the maping software, how difficult would it be to download a pack of maps e.g UK, USA or Europe. I have had a look round at some Offline navigation programs and none of the free ones are very good IMHO and the paid for ones are to expensive for what they are, seen as we have a decent mapping and navigation software built in to the phones surely being able to download your own maps to the phone would be an advantage, I am limited by my coding ability but surely theres a dev out there that might have an idea how to do it.
[Xoom Q&A, Help & Troubleshooting] TheGeek007:
I work for [undisclosed] where we sell Xooms. I have a demo unit that is a stock Wifi Xoom, so that people can try it out.

Well some mfer uninstalled the Google Books program and I can't seem to get it back.

I tried doing a factory reset from the Privacy menu, and it didn't restore the Books app. We don't have an account for the Xoom, but could possibly create one if all else fails. We need an account to use the market to possibly reinstall books that way.

I found the Xoom hard reset thread, and tried to follow the instructions on how to get to the recovery menu, but I seem do be doing something wrong.

Whats my next step?
[Xoom Q&A, Help & Troubleshooting] ateld:
Create a google account (gmail or whatever)

Attach it to the xoom

Open Market, download Google Books

I've seen this in BestBuy, where the account name is BestBuyCITYNAMEHERE@gmail.com

Edit: Also, just search "Google Books" in the market...it'll be right there.

https://market.android.com/details?id=com.google.android.apps.books

If you were to unlock the bootloader and root the Xoom, you could make it uninstallable, but that would also void the warranty on the Xoom and would likely be considered a no-no as it would allow mfers to do much more damage than just uninstalling Google Books.
[Xoom Q&A, Help & Troubleshooting] TheGeek007:
Yeah, it seems i need to make a GMail Account.

However after I did a factory reset, I realized all the music that came with the Xoom was gone! Its hard to show off the speakers without any music to play!

It sounds like I really need to do a restore from recovery, if I can ever figure out how. *goes off to search Xoom forums again*
[Xoom Q&A, Help & Troubleshooting] jwtyler:
Download the system.Img and the userdata.Img from moto. Flash. All fixed.
[Xoom Q&A, Help & Troubleshooting] TheGeek007:
Do you have a link handy?

I would have thought that those would come preloaded, so I could be able to flash back to factory. That and I haven't figured out how to get into recovery mode yet. :/
[Captivate Q&A, Help & Troubleshooting] RonH54:
I don't use a Calendar so pardon this dumb question. From time to time I will hit or do something on my phone(I got no clue what I did) and the Stock Calendar appears,what causes the Calendar to pop up like that?

Thanks
[Captivate Q&A, Help & Troubleshooting] ninjuh:
What are you doing when this happens? Specifics
[Captivate Q&A, Help & Troubleshooting] RonH54:
This what I am trying to figure out. So I posted here asking if there certain things "built-into" the phone that was used to make Calendar popup. Like is there some "shortcut" that causes this. It seems like I touch something on my phone screen and it pops up just not sure what I have done.

Thanks
[Captivate Q&A, Help & Troubleshooting] RonH54:
btt...................
[Captivate Q&A, Help & Troubleshooting] MobileNick:
Are you using a custom launcher or TouchWiz? On LauncherPro, you can customize a swipe action on the dock icons. Only thing I can think of is IF you were using a custom launcher and a swipe action was set to open Calendar.
[Captivate Q&A, Help & Troubleshooting] RonH54:
I am using LauncherPro. I look around there for a setting .

Thanks
[Captivate Q&A, Help & Troubleshooting] gospeedgo:
Do you have a clock widget that also displays the date? If you do, they usually default to the calendar application when you touch the date, and the clock application with you touch the time.
[Captivate Q&A, Help & Troubleshooting] RonH54:
Thanks that was it. I have Beautiful Widget Clock and Touching one area makes the Calendar pop-up.

Thanks again