Related
im sorry Admins if wasn't supposed to create a new thread for this subject, but its ma first thread.
Everytime you do a soft reset after loading a few applications on, e.g. real player, pim back up, tomtom, tcpmp, etc, the device does not load up. you have to do a hard reset, no mata how long you leave it. This is not just apparent on my device but a couple of others i have tested with. Couple of times when you soft reset, you may get away wid it, but eventually it will crash.
It worked fine when i first installed it and didnt have the need to soft reset it in the first few days, but eventually when i did, thats when i had the trouble. Since then i must have done 10 hard resets, reloaded the ROM on again still the same. like i said not just this device, but a ma brothers and ma frends device.
Ive had to revert back to the o2 ROM, because the last thing i want whilst im out and about, is to have to do a soft reset and it does not load and then have to end up doing hard reset. Not Ideal.
Hope Tom Can fix this issue for the next release.
if anyone else having same issue and has fixed it, let us know.
cheers
I had this problem 3 times, this time i removed everything in traylaunch (and removed the check to enable traylaunch) and it seems to have stopped it - over 9 days since now.
Also, haven't got batterystatus to overclock after reboot, just in case.
i have tried it without tray launch and the problem was still evident.. in anycase, i like the tray launch feature, so it wud be good to keep that there. with the 3 devices i tested it on, it semms to happen after installing a couple of applications. i realy like the features of the ROM, its just a shame it gets stuck after a soft reset.
TOM if ur out there, the n please respond with any advice, or whether ur gna have a fix
after reading feedback from other users, it does seem as the problem is with quite a few ppl, if not everyone. it seems to be the fact that this ROM does not like other applications being installed. without any applications it works fine, but as soon as you install something it goes dead.
i have no reverted back to o2 ROM. which is working great, but is just boring... lol
i must apologise 'Furbious' as you were right. it was tray launcher causing the problem... i have since re-installed b&b 4.0 took tick out of tray launcher and it works a treat...
just waiting for 4.1
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,
Sorry if this has been discussed in the past but I did several searches and didn't find anything.
I flashed my HTC Tilt 2 last week and installed the Energy Rom. I love everything about it but after about two days I began to notice that the touch screen and the phone itself will become unresponsive at least 3 times a day. I will touch the screen and nothing happens. My weather will freeze (no clouds moving etc) and none of my buttons will work.
There have been times when I was charging my phone and it would freeze and when I removed the charger, the charging light would remain on until I soft reset on the side with the stylus.
This is very frustrating and while I love the custom rom I am contemplating getting everything back to the stock rom.
Has anyone else experienced this? I tried several searches but found no answer or anyone else with a similar problem. If anyone can provide insight/advice I'd appreciate it!
You say that customs roms get you freezing...But you only mention energy. Did you try other roms? There are many other good roms that don't freeze. Believe me when I say that when you flash a decend rom, you won't go back to stock
Make sure you run a task29 before flashing an other rom.
I have a Tilt2 and have been running various (5 or more) versions of the Enregy ROM since May, and have never had any problems like the one you mentioned. I always run Task29 before every ROM flash.
Thanks for your replies!
I'll reflash energy and use task29 hopefully it fixes things!
So I've started getting a very weird "ghost touch" on my evo. Rather than try to explain what it is, here's a video (no links for newbs apparently) ###youtube.com/watch?v=0zW934J0UQ8
So you'd think it's a hardware issue but I have this hypothesis that it's some kind of software issue because it happened right after I switched from Fresh 3.1 to Fresh 3.2. It also goes away if you standby and it's somewhat intermittent.
The only problem with the software hypothesis is after it happened, Fresh 3.3 came out so I loaded that up trying to get rid of the problem and then I loaded Ava, and now I'm on Virus and the problem hasn't gone away. I've also switched up kernals a few times with no result. Radio\PRI\Wifi maybe but I don't know how that would affect it. So it may be that's just me not wanting to have to return my phone, but any thoughts would be appreciated before I go back to stock and get a new one.
KB
My phone seems to be experiencing random lockups/screen freezes. These seem to be more frequent when I have the mobile internet activate and i’m in a lower signal area or when I try and end a call through my cars Bluetooth handsfree system but they can happen any time, even sometimes when rebooting the phone, pulling the battery after a lockup has occurred and switching back on, the phone will reboot but freeze once again on the unlock screen.
I have not updated the radio, I am currently on version 5.11.05.27, as I have heard all manner of stories about bricked devices, but could this be the issue or is it more likely to be the sd card, or something else completely?
Any help you guys can give me would be greatly appreciated as am going to break the back cover of my phone soon, with the number of times am having to pull the battery.
I've ordered a new sd card to see if that will make a difference. The last time I used CWM to create the ext partition, should I do it this way again when the new card arrives or try a different way?
try using gparted live cd to create a partition, but i do not think your problem lies with your sd card
have you tried another rom to see if the problem persists?
Ok, i'll try the gparted method next time.
Yeah the first rom I tried was Gingerburst, that seemed to be ok to start with but sense would crash quite often and then the screen freezes started, so I moved to leedroid and although sense never crashes, the screen lockups have continued. I have looked on various other rom threads and i noticed on the Insertcoin webpage there has been a lot of mentions about the latest kernals causing screen locks, so I might try Insercoins v1.1.3, which everybody seems to be reverting back to and see if I have any more success with that.
I have recently tried InsertCoin CM7/STOCK 1.1.3 and again I seem to be experiencing screen freezes which always seem to be happening when the signal is low or when travelling in the car so possible signal fluctuations.
Does anybody have an ideas on how to fix this issue, would flashing the newest radio help and if so what is the best/easiest way to do it? or could it be a kernel issue, if so what do you all recommend.
Any help would be greatly appreciated.
I would have the freeze issue only in camera mode,otherwise its fine...probably some glitch in my phone,try full wipe n reinstall
I see that this tread is quite old, but i have the same issue with screen freezing. I was useing Leedroid 3.3.3 port on my HTC desire, for 2,5 month and then it started. Ive been trying everything form more than a month now (factory reset, installing aps one by one....) How did you solve the problem if you did at all? or what was the couse
Thx
Do you use software / scripts to control CPU frequencies / voltages?
MatDrOiD said:
Do you use software / scripts to control CPU frequencies / voltages?
Click to expand...
Click to collapse
Well i thought of this as well since the freezing started around the same time as i installed SetCPU (+/- a couple of weeks) but since the 2nd factory reset and installation of apps one by one i excluded the program but the problem still occures.
Also PowerAMP was a problem since i dont install it the freezing is not as ferquent (only every 2nd day not every day....)
I've read it somewhere that UV can couse the porblem, but i've never change that.
Also if i have more apps installed then dose my cpu required higher UV? If yes so then i can try to higher their default level.