Database Users

I think my Dream is toasted... OR My experience with the "blue light"

Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.

Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?

lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...

The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...

I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.

BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...

I wonder if it found one of those radios and did something with it?

For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.

hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.

lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.

Phone keep restarting by itself ??

Ok so my hero keep turning off by itself. This is not the first time it happen, it'll be on then it will just turn off by itself. Even worse sometimes the led light will be flashing for a new message and when I press the menu button to unlock it, it restart automatically. It mostly restarts itself when the screen is dark and i always press menu to bring up the light or to unlock it. Is this mean my phone is now defective ? I mean this happened before on some other 2.1 ROM too so idk what it is. Can someone tell me how to fix this????? I've tried almost all 2.1 Roms Aloysius, DC 2.07.2, Trevs Damage, ZenHero , RegawMod (themed) and Fresh 2d. the only rom that didnt restart my phone was the Fresh 2d with the very first audio fix by Avalaunchmods but i already erased that out of my computer.

Hmmm, not much to go on. I had experienced a similar issue back on early ROMs, but it was so infrequent I never really cared.
Try a Nandroid Backup and then flash to a 1.5 ROM and see if it continues, if so then yes the phone may be defective.
Also try different 2.1 ROMs here, and let us know if anything changes.

Dude, seriously do you need to have such a big font? Its not necessary....

i didn't catch that, what did you say?

lol mr big font
this happened to me last night, i wasnt even touching the phone and this happened, but its been the only time and ive been using 2.1 roms for a while now...i think this even happened once or twice when i was on stock...
coming from windows mobile, im used to things like this.

This happens on my sisters stock phone frequently I don't really care to look at it though.
Big fonts aren't nice. Stop using them

Try a different ROM. You may even want to revert to stock for awhile, if it keeps rebooting you should return the phone for a non-defective handset.
LOL @ RTessi

danknee said:
Try a different ROM. You may even want to revert to stock for awhile, if it keeps rebooting you should return the phone for a non-defective handset.
LOL @ RTessi
Click to expand...
Click to collapse
My sis's is on stock, and she has the problem
Funny thing is my phone is the only one without problems, and it's the only one that's rooted.

i don't know what we're yelling about loud noises

i got it fixed now, i think, i've had Fresh 2.0d for a few days and this problem is gone. oh and sorry for the big font lol i did this post in class on my phone and i didnt preview or look at what font i was using

I think I may have broken my phone

I'm in a bit of a panic and think I need help.
I bought the HTC Hero from Bestbuy roughly Nov. 2009. And like everyone else love it, but was frustrated with all the bugs and slowness, lag ext. Reading and waiting for 2.1, getting impatient weekly...blah blah blah....but horrified to try to root the phone, because im not the techiest guy in the world, so when I saw that there was a 2.1 leak that I could just click from my computer, I did it like an impatient child.
RUU_Hero_C_Sprint_2206511_signed_test.exe
and have had a major problem ever since. The phone will shut off if its not plugged in. I have to constantly turn it back on and wait for it to reboot.
So I followed "How-To repair your bootloader after using the 2.1 RUU" to the T! With no error messages and got it back to "stock" which still looked like 2.1 to me. I formated the SD card from the phone, did a full wipe in that black/green boot page and flashed Beezy's "option 4",
I believe I did a nanbackup right before the "option 4". But I don't think it matters, since the phone was shutting down before that anyway.
So that's where I am. If I'm messing around with the phone (on a call, web, playing with apps) it will stay on, but as soon as I set it down and the screen goes to sleep, thats it, when I pick it up and hit the menu or power button, it reboots (white screen, HTC logo). Am I F'ed? I do have insurance through sprint, but believe that is void now, since I stated messing around with it.
I swapped Batteries with my wife's phone and it still happend, so it's not a bad battery.
I'm sorry if I posted in the wrong forum. I did a search for "constant rebooting" and couldn't find anything similar to my problem.
Thanks in advance.

If all you see is the white htc screen you probably aren't actually rebooting just rosie is restarting. Probably because the ruu doesn't work too well on its own. I suggest you just take the plunge and root, wipe, and flash fresh 2.0d or damage 2.07.2 ( your choice really, both are excellent roms)
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

Well, first off it doesn't sound like you are rebooting, it sounds like sense might just be restarting.
Also, don't panic. Whatever you have done is fixable
surely someone who is not posting from their phone will be along to help soon, if not I'll be back home and on my pc in a few hours

Just to confirm
Can you go into settings > about phone > software information (1.5 maybe slightly different I can't remember any more) and tell us what Firmware version says? this way we can make sure that you are running the appropriate version to RUU back to 1.5 and reroot.
I am not sure exactly what is still on your phone.
Also have you ever flashed a radio update from flipz?

I agree, that it isn't rebooting, but its the sense crashing and restarting. I would also agree, that your best option would be to root.
Honestly, the guides are laid out as plain as they could be. It isn't that difficult, you just have to check and re-check typed commands, if done manually.
I think you will be pleasantly surprised and find it simpler than you think.
However, ALWAYS make sure to do to the following:
1. nandroid before you do anything.
2. NEVER EVER NEVER EVER touch anything that doesn't say CDMA HERO. (gsm hero radio flashes can literally fry your nice phone into a nice paperweight)
3. Don't be afraid to ask questions here. I'm pretty new to this, but there are a lot of cool helpful people.
4. nandroid again. (copy nandroids to your PC/Mac and keep a whole library of them.) I even have some extra google space that I've been uploading them to incase I'm not at my computer and I need one...lol)
5. Don't get too sucked into it.

Thank you guys for responding, as I was worried I would get flamed for being an idiot for doing what I did.
"I suggest you just take the plunge and root, wipe, and flash fresh 2.0d or damage 2.07.2 ( your choice really, both are excellent roms) "
Isn't "How-To repair your bootloader after using the 2.1 RUU" basically rooting the phone? Because after I follow those instructions, I get the the recovery menu. I just haven't tried Damage roms yes.
Also, "Well, first off it doesn't sound like you are rebooting, it sounds like sense might just be restarting."
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
I should mention that I have been testing things like, Turning off "Screen Timeout" completely, 10 mins, 1 min, 30 seconds...ext. And it still shuts down after a few minutes when the screen is off......HOWEVER, it is random as far as how long it has been sitting.....Sometimes the screen will be black for a minute and when I hit the menu or power it will reboot....sometimes it will sit for 10 mins and will turn on.....very random, but it WILL reboot eventually.
Thanks again, guys

Chaid said:
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
Click to expand...
Click to collapse
Do you see the first black HTC screen? I know I've done the HTC quietly brilliant screen, but then it goes right to lock screen and loading apps.
I still don't think it is a full reboot, but I'm not THAT up to speed with most of this stuff.
Also, RUU'ing back to stock, then rooting and installing a 2.1 rom by Damagless or Flips should be your best bet.
RUUing back to stock has some problems in and of itself, but it should go ok.

Chaid said:
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
Click to expand...
Click to collapse
Weird...
Regardless, this is fixable.
As Kcarpenter asked, post your system info if you can get to it.
What is your:
Firmware
Baseband
Kernel
Build
Software Number
PRI
PRL

Firmware: 2.1 -update1
Baseband: 2.42.00.03.10
Kernel: 2.6.29-d30020a8
[email protected] #1
Build: 2.20.651.1 CL157175 test-keys
Software Number: 2.20.651.1
PRI: 2.10_003
PRL: 60664

Chaid said:
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
Thanks again, guys
Click to expand...
Click to collapse
Sounds like you are using a 2.1 rom not the stock 1.5
I would try using this guide http://forum.xda-developers.com/showthread.php?t=608434 to correct your issues it will take you back to stock 1.56.651.2 that come with the phone
Oh and if you get any errors this will help too http://forum.xda-developers.com/showthread.php?t=654119

Guys, since he used the 2.1 RUU, isn't he only able to use the 2.1 RUU now? Not the 1.5?

I too am experiencing this.
Factory reset my phone and then flashed from 1.6 to 2.1. I have tried two different 2.1 roms (the sprint leak one and Freshrom) and both of them are causing spontaneous reboots of my phone. I never experienced reboots when on 1.6.
Software information:
2.1 fresh
baseband 1.04.01.09.21
Kernel is 2.6.29-d30020a8
build is fresh rom 2.0d
Software number is 2.20.651.1
PRI is flipz_01
PRL is 60660
any suggestions from anyone?

mrinehart93 said:
Guys, since he used the 2.1 RUU, isn't he only able to use the 2.1 RUU now? Not the 1.5?
Click to expand...
Click to collapse
I believe you are correct, although I have yet to use any RUU
OP, you really should just root the thing flash a rom and succumb to the new obsession you don't even know you have yet
Personally, I'm a fan of RegawMODv2.1, it's lean and stable.

I think that even though you have run 2.1 RUU we can take you back to a bone stock 2.1
When I get home tonight I will try to link to all of the appropriate guides to get you there.
Once we have you back at a stock 1.5 I think we can all say "ROOT IT!" but I would feel more comfortable knowing that you came from the begining in the right order of things.
And get you on a solid stable Rom. I have recently started having issues with my damage rom and all of the aps2sd stuff that has been going on. Not sure what I am going to move to next. But that's besides the point, and none of it is Damageless's fault.

Ok, Kcarpenter, I'll be waiting LOL. I have been f'ing with this thing for a few days now, reading different forums and searching and searching. I finally broke down and posted here, because I'm at a loss. So I REALLY appreciate you guys taking the time to help me. Plugging the phone into my work truck laptop and running to the house to plug it in is wearing me down...

You just need to get over the fear of f*ing up your phone and root it. I'm not sure where the treads are on everything you need, but it's pretty straight forward.
If you had rooted while still running 1.5 you probably would not be in this mess. And Flipz has Fresh Kitchen which makes it even easier to Root and put a recovery console on.

"If you had rooted while still running 1.5 you probably would not be in this mess." You are absolutely correct, &RoidRage. I got excited when I saw the word "Official" 2.1, and jumped the gun.

Chaid said:
"If you had rooted while still running 1.5 you probably would not be in this mess." You are absolutely correct, &RoidRage. I got excited when I saw the word "Official" 2.1, and jumped the gun.
Click to expand...
Click to collapse
That probably created lots of people to get excited.. Anyway, here is what I got
Okay first I looked here
http://forum.xda-developers.com/showthread.php?t=661057&page=6
Which directed me to
http://forum.xda-developers.com/showthread.php?p=6013606#post6013606<--------This is the one you really want.
If you get it to work then you can flash a custom rom. But make sure you download it and put it on the sdcard before doing anything else.
I know it says it is for the 110 error, but people have used it to get back to 1.5 from 2.1

Thanks, man. I'll give it a shot......I have nothing to loose at this point, so I'm over my fear of F'ing up the phone.

I would read everything first, I didn't have the time look it all over.
Editamn predictive text said wetting instead of everything.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

Sprint hero restarting after 2.1

I have installed several of the 2.1 roms out there. Each one that i install causes my phone to randomly restart. Is this a common issue with anyone else? As soon as I go back to 1.5, the restarting stops.

I am having the same issue on the stock 2.1. The only answer I have gotten from HTC is hard reset. But I have already done this twice. So I am going to root my phone and hopefully get rid of this problem. It only started after I updated to 2.1.

BigDiz007 said:
I have installed several of the 2.1 roms out there. Each one that i install causes my phone to randomly restart. Is this a common issue with anyone else? As soon as I go back to 1.5, the restarting stops.
Click to expand...
Click to collapse
Silly question perhaps, but are you completely wiping data and dalvik cache before flashing any of these 2.1 ROMs? Sometimes this happens if you don't do a full wipe before installing new ROMs.

I'm having the same issue, and I did a full wipe, installed several different roms and finally settled on aloysius

i've had the same problems with every 2.1 rom with the exception of darchdroid.
for me it usually happened after i placed a phone call and tried to hang up
and yes everything was wiped before flashing....

im having the same issue i knew i wasnt the only one, has anyone figured out why this is???

I am getting that error trying to install ZenEXP.

Same issue here, only mine's been doing it out of the box, as I got mine the day the EVO was released. I've rooted it and attempted to install several ROMs hoping to get rid of the issue, but had no luck so far. Never had the luxury of having 1.5, as mine came with 2.1, so I just thought it was the phone, honestly. Interesting to know the issue doesn't occur with 1.5...
Anybody got a copy of the stock 1.5 from original release? I'd like to give it a shot.

I do not have any issues that have been listed here. I am running fresh rom and everything is working great.Just wanted to make sure all views arebeing represented in this thread

hmmm....had a thought, did the phone get really hot when it happened....cause that is what happened when i was on fresh....

NomadHellfire said:
Same issue here, only mine's been doing it out of the box, as I got mine the day the EVO was released. I've rooted it and attempted to install several ROMs hoping to get rid of the issue, but had no luck so far. Never had the luxury of having 1.5, as mine came with 2.1, so I just thought it was the phone, honestly. Interesting to know the issue doesn't occur with 1.5...
Anybody got a copy of the stock 1.5 from original release? I'd like to give it a shot.
Click to expand...
Click to collapse
You won't be able to go back to the stock 1.5 original. That has been tried already by a bunch of developers here and it didn't work. You would probably be able to flash a 1.5 ROM (browse way back into the Development pages forum here), but since you had stock 2.1, there's no way for you to go back to stock 1.5.
For all the rest of you, not sure why you are getting random reboots, but as mentioned in the previous post, sometimes the Heros do that when they get overheated or overworked. It would be best to root and start with a very stable, non-overclocked ROM. A couple of the most stable and reliable stock-based ROMs here in this section are DamageControl 2.09.1 and nfinitefx45's Stock 2.27.651.6. I recommend you try either of those out if you haven't already -- hopefully that will fix/solve some of your troubles.
Please report back if any if you have success or more problems with these...we want to make sure you get the help you need

overheating is defiantly not whats causing my restarting. im not trying to thread hijack so ill provide a link to the thread i started about this same issue. in my thread i have attached bug reports (i think thats what they are) and now i have stopped receiving help just when i provided the info needed to see whats casuing this
http://forum.xda-developers.com/showthread.php?t=684727
Im not any good at code so i cant read the big reports well. but i believe its a hardware issue because there is a small presentage of people having these errors and i cant seam to get anyone to be able to reproduce this if it doesnt happen to them.

shawnwojcik said:
overheating is defiantly not whats causing my restarting. im not trying to thread hijack so ill provide a link to the thread i started about this same issue. in my thread i have attached bug reports (i think thats what they are) and now i have stopped receiving help just when i provided the info needed to see whats casuing this
http://forum.xda-developers.com/showthread.php?t=684727
Im not any good at code so i cant read the big reports well. but i believe its a hardware issue because there is a small presentage of people having these errors and i cant seam to get anyone to be able to reproduce this if it doesnt happen to them.
Click to expand...
Click to collapse
Sorry, I don't understand much of the code myself. And I think a handful of our devs here who understand all that coding have already moved on to the EVO. I read your other thread too but don't know what else to suggest. Wish I could help more. You could just be one of the unlucky few who got a bad, buggy phone right out of the box.
Have you thought about just calling Sprint customer service and asking for a replacement phone? Certainly with all the trouble you're having it may be worth it. I think even if you don't have the insurance plan, a replacement phone is only around $35.

@chromiumleaf, yeah sadly i think its time for a different phone.

lots of freezin goin on up in here!

long story short i went from an old GB to an ICS. didn't care too much for it so i went back to this one. loved it but i noticed that when i went to reboot none of the options worked. also then noticed that it would freeze at other times too and the only way to get unstuck was to put it to lock the screen and unlock it.
thinking it was the rom i switched again to this one just a trial and error. well its doing it on this one too. but now i can't even unlock the screen.
unless im missing something, i am doing all this through cwm and doing a data wipe and cache wipe each time.
what else can i try to get everything rectified
edit: and no, my digitizer is not broken as it has worked for well over 2 years as well as when i had the ICS rom up until the past weekend!

But the digitizer can brick from one moment to the other. In my case, i flashed miui and my digitizer was broken after that. Before that all was fine.
What i did to find that out, was to reset the phone completly. What means, back to WM 6.5. It's just an idea to do another trial and error. If it doesn't work in WM 6.5 u're digitizer is nearly to 100% broken.
Sorry for my bad english. May i could help u

schlöntz said:
But the digitizer can brick from one moment to the other. In my case, i flashed miui and my digitizer was broken after that. Before that all was fine.
What i did to find that out, was to reset the phone completly. What means, back to WM 6.5. It's just an idea to do another trial and error. If it doesn't work in WM 6.5 u're digitizer is nearly to 100% broken.
Sorry for my bad english. May i could help u
Click to expand...
Click to collapse
thanks for the input, by again my digitizer is fine
it only stops responding when i try and reboot the phone.

hai bro,,,,,,
pls change the rom to gingerbread.....use asop roms i.e. non sense roms for less freezing specially when unlocking screen freeze...currently ics hardware acceraltion under some issue the xda members are working hard to come issues...wait for a stable daily use ics build release..........all ics rom are beta hence no hardware video codecs etc.....dont doubt your screen it works well ,,,my htc is 1.5yrs old it is fine.. dont doubt your digitalizer..it is fine ...only your kernels in rom make this error ..
i personal recommand to go with stable cm7 base builds...for better battery life and stablity...

blackbeasst said:
thanks for the input, by again my digitizer is fine
it only stops responding when i try and reboot the phone.
Click to expand...
Click to collapse
and how do you go about rebooting the phone do you use the power/end key to bring up the power menu
if so
try downloading quickboot from the play store
https://play.google.com/store/apps/...ckboot&feature=nav_result#?t=W251bGwsMSwyLDNd
and use it to reboot your phone and see if it freezes

vigneshjack3 said:
hai bro,,,,,,
pls change the rom to gingerbread.....use asop roms i.e. non sense roms for less freezing specially when unlocking screen freeze...currently ics hardware acceraltion under some issue the xda members are working hard to come issues...wait for a stable daily use ics build release..........all ics rom are beta hence no hardware video codecs etc.....dont doubt your screen it works well ,,,my htc is 1.5yrs old it is fine.. dont doubt your digitalizer..it is fine ...only your kernels in rom make this error ..
i personal recommand to go with stable cm7 base builds...for better battery life and stablity...
Click to expand...
Click to collapse
im on this cm7 rom, not ICS.
http://forum.xda-developers.com/showthread.php?t=933951

Kameirus said:
and how do you go about rebooting the phone do you use the power/end key to bring up the power menu
if so
try downloading quickboot from the play store
https://play.google.com/store/apps/...ckboot&feature=nav_result#?t=W251bGwsMSwyLDNd
and use it to reboot your phone and see if it freezes
Click to expand...
Click to collapse
thanks bro. i'll try that here in a bit and letcha know
edit: reboots fine with that program
edit 2: but alas i still get some freezing just within the past 5 minutes

blackbeasst said:
thanks bro. i'll try that here in a bit and letcha know
edit: reboots fine with that program
edit 2: but alas i still get some freezing just within the past 5 minutes
Click to expand...
Click to collapse
ok where is the freezing happening at now
and are you useing the power/end key at all before the freeze up happens

Kameirus said:
ok where is the freezing happening at now
and are you useing the power/end key at all before the freeze up happens
Click to expand...
Click to collapse
every time i hold the power button in to reboot/turn off it hangs. i can't choose any of the options. if i hit the back arrow it removes the options screen but is still hung. i can hit the power button to black the screen but then i have to wait about 10 seconds to unlock it. if i try right away its still hung. but if i wait the 10 seconds or so it seems to be fine.
i know its not a big deal since i rarely reboot/power off. and now that i have that app it works.

blackbeasst said:
every time i hold the power button in to reboot/turn off it hangs. i can't choose any of the options. if i hit the back arrow it removes the options screen but is still hung. i can hit the power button to black the screen but then i have to wait about 10 seconds to unlock it. if i try right away its still hung. but if i wait the 10 seconds or so it seems to be fine.
i know its not a big deal since i rarely reboot/power off. and now that i have that app it works.
Click to expand...
Click to collapse
ok so test it out with out touching the power/end key for anything
you can use this program from the market to lock the screen
https://play.google.com/store/apps/...xLDEwMiwiY29tLmthdGVjY2Euc2NyZWVub2ZmbG9jayJd
and when unlocking the the phone use your windows key and see if things work a little bettor
just going thru a process of elimination trying to help ya

Kameirus said:
ok so test it out with out touching the power/end key for anything
you can use this program from the market to lock the screen
https://play.google.com/store/apps/...xLDEwMiwiY29tLmthdGVjY2Euc2NyZWVub2ZmbG9jayJd
and when unlocking the the phone use your windows key and see if things work a little bettor
just going thru a process of elimination trying to help ya
Click to expand...
Click to collapse
thanks kam. i'll try those and report back.

ok full fledged lock up this time. had to yank the battery.
could there be something still lingering on the system even after i did a wipe of the data/cache? im not opposed to reinstalling the rom if theres something else i can run to wipe it further.
also after booting back up it reverted to monday june 18 8:32 am!

blackbeasst said:
ok full fledged lock up this time. had to yank the battery.
could there be something still lingering on the system even after i did a wipe of the data/cache? im not opposed to reinstalling the rom if theres something else i can run to wipe it further.
also after booting back up it reverted to monday june 18 8:32 am!
Click to expand...
Click to collapse
do you have it overclocked at all
and what phone version is it eu or hd2

Kameirus said:
do you have it overclocked at all
and what phone version is it eu or hd2
Click to expand...
Click to collapse
nope. stock specs. my phone is a us phone. unless i missed something with that rom that makes it no likey?
even now after a battery pull and letting the screen time out im hung

vigneshjack3 said:
i personal recommand to go with stable cm7 base builds...for better battery life and stablity...
Click to expand...
Click to collapse
Hey, whilst it's great that you're trying to help, this is fundamentally wrong. This is an opinion based question but you're stating this as fact, which is misinformation and could cause confusion. Please choose your wording more carefully as the majority of ICS users DON'T have issues and I find it a tonne more stable than GB. Also overuse of emoticons
blackbeasst said:
nope. stock specs. my phone is a us phone. unless i missed something with that rom that makes it no likey?
even now after a battery pull and letting the screen time out im hung
Click to expand...
Click to collapse
Since you say you aren't opposed to reinstalling the ROM, try that. If that doesn't work, try WinMo. I'm inclined to agree with Kameirus here, it sounds like a digitizer issue, and you shouldn't rule it out as a possibility just yet. Installing WinMo should be able to tell you whether or not this is your problem.

Nigeldg said:
Since you say you aren't opposed to reinstalling the ROM, try that. If that doesn't work, try WinMo. I'm inclined to agree with Kameirus here, it sounds like a digitizer issue, and you shouldn't rule it out as a possibility just yet. Installing WinMo should be able to tell you whether or not this is your problem.
Click to expand...
Click to collapse
well i am on reinstall #2 of this exact rom. like i said since going to ICS a couple weeks ago this is my 4th rom within said 2/3 weeks. even up to the install of ICS i have had zero digitizer problems.
can i install winmo from cwm? if so does anyone have a link so i can give it a whirl?

ok reinstall #3 of that rom. this time it acted like the first time i installed it. the touch screen was responsive when choosing the options for installation.
the only thing i did was flash CWM 150mb instead of the 400mb i think was on there. not sure if that had anything to do with it but at least i would eliminate it.
ok up and running. i won't do any updates and see how it acts.
HA! well that didn't take long where's that winmo rom i can try out LOL!

blackbeasst said:
ok reinstall #3 of that rom. this time it acted like the first time i installed it. the touch screen was responsive when choosing the options for installation.
the only thing i did was flash CWM 150mb instead of the 400mb i think was on there. not sure if that had anything to do with it but at least i would eliminate it.
ok up and running. i won't do any updates and see how it acts.
HA! well that didn't take long where's that winmo rom i can try out LOL!
Click to expand...
Click to collapse
let me see if i can find the right one lol
its been so long since ive used a winmo
edit
i think this is the right one but let someone else confirm it is the correct one as i wouldnt want it to brick your phone if its not the right one \
http://shipped-roms.com/download.ph...o_15.39.50.07U_2.10.50.26_Signed_LEO_Ship.exe

Kameirus said:
let me see if i can find the right one lol
its been so long since ive used a winmo
edit
i think this is the right one but let someone else confirm it is the correct one as i wouldnt want it to brick your phone if its not the right one \
http://shipped-roms.com/download.ph...o_15.39.50.07U_2.10.50.26_Signed_LEO_Ship.exe
Click to expand...
Click to collapse
thanks kam. i'll wait for a verification first. would doing his method work?

blackbeasst said:
thanks kam. i'll wait for a verification first. would doing his method work?
Click to expand...
Click to collapse
Provided you have the right ROM for your device type (i.e. a TMOUS) then yes, it would work fine. I find his guides very good actually, much more noob-friendly than some of the ones here on XDA (general statement, not trying to say you're a noob or anything)