Ever since I started flashing FroYo Roms my touchscreen has seemed to have issues. I saw people noticing the same thing in the early stages of the AVA Sense FroYo, then it seemed to go away for everyone else. I have tried multiple ROMs tried toasted kernel and stock kernels with every ROM, nothing seems to work.
Does anyone know the remedy? the symptoms are random non response. Sometimes I can't answer a call, sometimes I have to press twice on something to select it, and sometimes it just seem as accurate as it used to be. Before I did my first FroYo ROM, I did the wimax and radio update.
Sometimes I have to turn the screen off then on to regain control of the phone.
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
Hi everyone, just got a used TouchPro2 (GSM), after my Xperia X1 got runned over by a car.
I searched the forum, however I was unable to find a cure. The problem is that it works normally for a while, than suddenly it decides to go nuts - First it starts by refusing to launch any application (you can go into the menu or sense). After a reboot, it doesn't start several times (keeps stuck on the Touch Pro2 screen for a couple of times, than several times on the orange windows logo screen). Aftr a multiple tries (removing the battery to reboot), it finally loads into the OS, but it has hard reseted by itself - no settings, no contacts, nothing.
It did it with the rom that it came, so i naturally thought that it was from there. Switched to kalimeho lite rom from here, but to no avail - same **** happens again.
Anyone has any ideas? Or maybe recommend a stable tested rom (i'm not into eye candy).
10x in advance
I have an ATT Tilt2...I can assure you the tp2 is a very nice device, and capable of a lot of things....so congrats on getting a quality replacement phone....
My advice would be to task 29 and install the stock rom just to dial it in back to what it should be, to see if everything works correctly.....PS...my experience with the stock roms are to turn off TF3D/Sense...since the phone hasnt been tweaked that UI is a bit slower than I'd like...the Chefs here cook it up to run nicely but stock is just too slow for my likeing...you can turn it off by going to start>settings.today>items...then click windows default..
See if the phone runs correctly then....
After that....if you want a kick ass stable stock rom, there's WCX's Illuminati ROMS (choose your flavor of messenger type and such)...he puts a lot of time and focus into us TP2 users who want stable, fast stock set ups and they're tried and proven with testing before releasing....Energy Roms are good if you want eye candy that works as well...those are two Chefs whose Roms are the only ones I use and are familiar with and I've never had issues with bugs on eithers Roms....I'd install their stuff anytime without question
I forgot to include....if you don't have the original ROM for that phone you can look for it here
http://shipped-roms.com/?p=82
If you're familiar with flashing then you probably know more about everything than I do...but if you're not familiar with flashing I recommend you read up the tutorials regarding it...specifically...
HardSPL
TASK29
and then whatever Rom you install
The original ROM shouldnt require HARDSPL
TASK 29 did the magic, thank you very much!!!
These are the two setups I have used thus far (besides full stock), and this issue has occurred on both:
http://imgur.com/EgzxWFI
http://imgur.com/FZWrdwZ
The first is on ktoonsez kernel on stock rom. The second is Slimroms Kitkat. I have been using the first much longer than the second (which I moved over to just a few weeks ago).
Basically this soft reset tends to happen when I'm driving and using the GPS most often (and I notice that's also when the phone is usually the warmest). What happens is the phone just freezes up and sits there for a bit before finally doing a vibration and starting back up to the unlock screen. Kind of like I was restarting, but not quite. If it happened in the middle of calls, somehow it would keep the call going (at least on the stock kernel, I'm not sure about the new one yet). The other person just wouldn't hear what I was saying during the "soft reset"
On the stock kernel it used to happen even when not using the GPS. It was infrequent, but occurred I would say usually when I was using the phone more heavily... mostly just random though. Sometimes it would also not happen while using the GPS. That is to say it's a sporadic issue.
On this new Kitkat kernel it happened while I was navigating recently, but has not occurred when during any other operations (yet) that I can think of. Considering that was one of the first times I tried navigating with the kernel this worries me.
Does anyone know how I could approach this problem? Perhaps some logging I could do to get to the root issue? Some firmware I should perhaps try out?
Thanks.
Sounds hardware related to me. Especially if its happening on different roms.
Then again... I just looked at you image and you are still running 4.0.4 on one. But the other you are running 4.4.4. On one or tge other you most likely have a rather large gap between your firmware build and the rom. Id try flashing full stock firmware with Odin and test for a day or two. Up to you what build you want to use, but if it were me id update to 4.3. If you go to 4.3, keep in mind there is no going back.
Good day to everyone who stumbled upon my humble thread, would you mind helping me?
I got my M8 two weeks ago and the first thing to do with it was to flash a custom ROM. That's when the problems appeared. Features like auto-rotate, doubletap to wake, compass etc. stopped working after the device has been running for some time. After reboot everything got back to normal, but the problems reappeared quickly. I tried several different ROMs and kernels and I'm currently on CarbonROM. And I'm NOT planning to switch back to stock. I've searched a lot and found nothing, but feel free to give me even the most basic advice. Any advice besides reverting to stock is welcome. Thanks