Database Users

Why does my phone shutoff?

Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.

If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD

patkin said:
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
Click to expand...
Click to collapse
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......

kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
I am not positive what A2SD is. I have a new 8MB SD card that came today. If I pop that in what will happen. Should it be partitioned? Thanks.

Chaid said:
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
Click to expand...
Click to collapse
Thank God I thought I was the only one. I searched but didn't see your thread. Weird problem.

Same problem here too since the new leaked 2.1 test ruu from damaged. The only 2.1 Rom that works for my needs without rebooting every 3rd or 4th time I wake it using the end call/power button is Damagedtrev 2.01, the updated 2.05 Rom in his thread just makes my phone reboot as described above. I don't have a link to his thread, but it would be interesting to see if it worked on your phone too. Other's have claimed a battery shorting might be causing this issue, but I'm not buying that. I've looked at /proc/lastkmsg for clues, but nothing obvious there. I hope the official Sprint update doesn't have this bug or sprint will be giving me a new phone. /end rant

I can't seem to find Damagedtrev 2.01
So I can't test it.

Here's the link to the thread.
I cannot post links, because of some restrictions,but here is the last part of the url.
forum.xda-developers.com/showthread.php?t=653622
here's the link for the full rom
Oops cannot post link to rom on 4shared, look in the bottom of the first post in the thread for a link to the full rom of DamagedTrev_v201
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.

Ok, downloading......stay tuned.
I really hope this 2.1 ROM works.....I'm kinda sick of 1.5.
Edit:
P.S. I'm reading that there is a battery issue....do you have that?

kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
Hey good news. I put the new SD card in after backing up the other one, partitioned it and copied the files and folders back on then flashed ALOYSIUS and so far so good. I have woken it up about 10 times in a row. Looking good.
I had tried that perticular Rom before with no success.

Interesting.....I'm using the 2 gig sd card that came with the phone....I wonder if that is my problem?

Well it started again. This was right after setting my Gmail and POP3 mail accounts. It shut off on the first sleep after this. Hmmmmm.
I'm re-flashing now and not setting up the mail accounts. Will report back later.

Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.

reboot
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation

kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
It's a full reboot. The phone actually turns off when it goes into sleep. You don't know it's off until you hit the button to wake it up and the phone boots up.
Now for the good news. After re-flashing and not setting up the email accounts it was still shutting downconfused so I started looking elsewhere so I opened up what I thought was a likely culprit in Autokiller and none of the presets where selected so I picked Moderate and haven't had a shutdown since which has been over an hour. Fingers are crossed. I'll report back later.

That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.

patkin, dude, I felt the same...I gave up on 2.1.
download, wipe then flash Gumbo-1.5c-BARE-signed.zip after it reboots, download and flash Gumbo-Sense-signed.zip.
You flash Gumbo-Sense-signed.zip over the Gumbo-1.5. No need to wipe or anything, it just adds to the ROM. Fast as hell and works PERFECT.
http://www.4shared.com/file/217809392/5fcf1f5d/Gumbo-15c-BARE-signed.html
http://www.4shared.com/file/217811195/3afb5fcf/Gumbo-Sense-signed.html
Give it a shot....I think you will like it......let me know =)
Gumbo thred so you can read up if you like. http://forum.xda-developers.com/showthread.php?t=630221

Chaid said:
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
Click to expand...
Click to collapse
Glad to see your rebooting issue was fixed with this rom even though you went back to gumbo 1.5. In my mind, this just confirms that it is not a battery issue. I never use bluetooth and have never experienced any audio loss with this rom, but apparently even people on the same hardware and firmware versions have different problems.
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
Full Reboot here too.
patkin said:
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
Click to expand...
Click to collapse
Yeah, got my phone beginning of march 2010 and I also think there is something in the 2.1 test ruu or hardware that is keeping the phone from functioning properly with an altered 2.1 rom.

Just wanted to let people know what happened to resolve this. I went back to 1.5 then when 2.1 official came out last week I said what the heck if I can't enjoy a rooted custom 2.1 I'll try the official and guess what. Same problem as the other 2.1's.........phone shuts off randomly! Except this time they are replacing it with a new phone. Yeaaah! I'm probably going Evo now though since I found out I can get a new phone. Anyone need a new Hero?

I'm having the same problem.. One question. Does DarchDroid automatically move dalvik-cache to the sd

[Q] Phone Shuts Down Randomly

My phone will randomly shut down and will not power back on unless I pull the battery, I have 2 batteries and it happens with either one. It does not shut down while on charger/dock. I have wiped the phone multiple times with odin, I've used several different roms/kernals,same results every time. Just curious if anyone else has been experiencing this issue.

I've been experiencing this after I went to eb13 with the custom kernels that are out. But my.phone will either lockup and I have yo pull the battery or it will reboot itself. Never had what happens to u yet.
Sent From My Evo Killer!

This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha

nalewis89 said:
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
Click to expand...
Click to collapse
I'm averaging 10 times a day myself

Permanent sleep
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.

before updating to 2.2 - I did the DK28 and now the EB13 one - with 2.1 I would have my phone randomly reboot - I would be sitting there and here the music it makes when it starts up but I never turned it off?
other times it would just be turned off, but when I turn it back on the abttery is not low enough to cause it to turn off
all this went away with DK28 2.2 and hasnet happened since I installed EB13 2.2

This happeed to me the other morning. I wasn't able to boot until I reflashed the kernel. Twilight frozen btw.
Sent from my SPH-D700 using XDA Premium App

My first epic would randomly hard power off, even running stock ROMs. If you are running a stock ROM and seeing a hard power off at random, I suggest you go swap the phone. It's just broken.

Ive never had this problem and im on my first and only epic and ive had it since it came out,
Ive been very careful with my epic as it has been great to me, it hates me probaly tho for feeding it stuff while experimenting things that make it spit up FCS,
But my phone has been always working perfect, all the way back to d118.

CLazman said:
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
Click to expand...
Click to collapse
the buttons don't stay lit, i'm using twilight kernal right now but was happening with genocide kernal too, going back to eclair just to eliminate 2.2, ext4, etc.. to see if it's a hardware issue

First try
dk18 update.zip flash
Restored apps and data with my backup pro root
Random reboots, FC
Second try
Odin to dk18
Wipe x3
Restored apps and data with mybackup pro root
FC, music player force closing (doubletwist, stock and musicmod, poweramp worked though?), fc when trying to change ringtone or notification.
Started reading about others with the same issues and thought data backups were a reoccuring theme. Did a third try tonight and so far so good. Music players working, no force closings, keyboards working correctly, gps lock indoors. Its still early, problems might still popup, thought id share...
Latest froyotempt
Fresh backup with mybackup pro root
Wipe x3
odin eb13 prerooted (ctsy xda forum) same file from attempt 2. Did this x3 as well, read it in a thread somewhere...
backup apps only with mybackup pro root
All attempts were with genocide kernal.
So far so good, none of the previous bugs are apparent, so far... Those of you that are on the fence regarding doing the same, so far its worth the time.
Sent from my SPH-D700 using XDA App

I was thinking back-ups were part of the problem also, so I used odin and started all over from dl18 without restoring any data, same problem still occured

Still messing with my phone, everything that was broken seems to be fixed. Hopefully it stays this way...
Sent from my SPH-D700 using XDA App

That used to happened to me on eclair when I set my setcpu profiles too low when screen off. You wouldn't happen to be using setcpu would you?

actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800

I'll add to this thread. I seem to be having the same problem and I believe it started when I installed quantum rom... but I'm not sure. The symptoms i had were random reboots, where the screen would shut off and the 4 lights would stay on. Then I would have the sound of lost signal as if my phone rebooted and was starting over. Also, the most recent problem I get is my phone completely shuts off and I need to battery pull to get it to start up, and it loops on the splash screen of my rom. I have tried doing a complete odin wipe and not restoring anything and I believe it is still happening...

joedig52 said:
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
Click to expand...
Click to collapse
Any update?
Also, make sure the governor isn't "powersave". If you have 100-400MHz powersave governor, it still ONLY runs at the lowest speed (100MHz), even if it's 100-400MHz.

Still happening, not on powersave, doesn't matter what settings I have in set cpu. Did a hard reset back to 2.1 and it still happens, bringing it in for repair.

(SOD) blank screen on EC05

Is anyone getting the Screen of Death.. (or whatever its being called).. on EC05??
im on EB13 and I have to pull my battery out at least 8 to 10 times a day because the screen wont come back on...
is anyone getting this on EC05 or has the issue been fixed??

Sounds like you need to Odin.

bigdreco said:
Is anyone getting the Screen of Death.. (or whatever its being called).. on EC05??
im on EB13 and I have to pull my battery out at least 8 to 10 times a day because the screen wont come back on...
is anyone getting this on EC05 or has the issue been fixed??
Click to expand...
Click to collapse
I got that on EB as well. It's weird because it didn't start as soon as I flashed it. It was maybe about a week later when it started doing that. When it happened to me my phone would vibrate sporadically and then the screen would finally go "black" or turn off. The odd thing is the bottom four buttons would stay lit. I would have to pull the battery. It started happening more and more frequently. I've since flashed to EC and am rooted but that's it. I've been flashing back and forth between different set ups, so I haven't been on this current set up for more than 2 days. I did however have the same problem today at lunch. I had to pull the battery to get it to reset. I was playing a video I recorded on my phone before the screen went black. I don't know if it was media related. I will play some more videos and see if it does it again.

k0nane said:
Sounds like you need to Odin.
Click to expand...
Click to collapse
I Odined a fresh EB a couple of times and it would eventually come back. Not sure if it was a program I was using that triggered it on EB. I don't know if it might be a media issue. I use my camera and video pretty frequently, so that's the only thing I can think of at this point. It's the only thing I really use, even on EC, on a regular basis except my XDA app. I hope it's not that!...

cpcormier3 said:
I Odined a fresh EB a couple of times and it would eventually come back. Not sure if it was a program I was using that triggered it on EB. I don't know if it might be a media issue. I use my camera and video pretty frequently, so that's the only thing I can think of at this point. It's the only thing I really use, even on EC, on a regular basis except my XDA app. I hope it's not that!...
Click to expand...
Click to collapse
Have you tried formatting your SD card yet?

k0nane said:
Have you tried formatting your SD card yet?
Click to expand...
Click to collapse
I haven't with EC, but I did with EB and I still had those problems. Today was the first day that it's happened to me. I've only been on this set up for the last couple of days, because I flashed a couple of things and hoping that I would have better luck with stock. I will try re-formatting when I get home. I tried playing a coulpe of videos (the same ones as before) to see if I could replicate the problem, but haven't been able to yet. Hopefully that was just a situation to where the phone just needed to reboot....

bigdreco said:
Is anyone getting the Screen of Death.. (or whatever its being called).. on EC05??
im on EB13 and I have to pull my battery out at least 8 to 10 times a day because the screen wont come back on...
is anyone getting this on EC05 or has the issue been fixed??
Click to expand...
Click to collapse
!!! Y E S !!!
It happened to me four times today!
Does anyone know a way to get logs to continuously write to disk? Otherwise I have no idea how to troubleshoot this.
I'm running, midNIGHT EC05 with minimal apps installed. I use SetCPU, and I've just changed the settings. I'm thinking this may have started after trying to use 100MHz and "startass" setting. My profiles are now set to 200Mhz minimum and "ondemand." I'll let you know how that goes.
Having to use my old BlackBerry Bold as an alarm clock now, just in case!
EDIT: I did not format SD with this install but have formatted less than 2 weeks ago.

Happened again after setCPU settings were changed.

That happened to me but what's weird isnit only happened when I was on di18 kept having to pull the battery and once I updated to eb13 it all stopped
Sent from my SPH-D700 using XDA Premium App

Do you have Beautiful Widgets installed? Is one of their widgets on your HS? .. Had this problem on DK28..

Same here. Like the term sod, btw. Happening when I use flash. I'm on stock ec coming from fresh odin, and formatted sd.
Sent from my SPH-D700 using XDA Premium App

alfiej said:
Do you have Beautiful Widgets installed? Is one of their widgets on your HS? .. Had this problem on DK28..
Click to expand...
Click to collapse
No Beautiful Widgets here.
I am running Go Launcher, which is new to me. Will likely eliminate that tomorrow. Oh yeah, the only other widget new to me is "Android System Info" (which is great, btw).
I run Pure Grid calendar and Sense Analog Clock widgets, but I've been running those without trouble for months.
Does anyone know how to change logging levels?

The only rom I was able to use without the SOD was myfrankenstein DK28. While on
EB13 it did it contstanly and much hasnt changed while running EC05. I formatted my sd card and only installed minimal apps. I tried not restoring from Titanium or Astro. Fresh install from market and it still happens. I've stopped using SetCPU, that didnt help either. I do have Beautiful widgets running on my home screen, but I aslo had that while running DK28. I have no idea what the problem is. It is a complete pain having to check my phone every couple of mins to make sure that its still on. Over night forget about it, every morning the phone is dead. Can anybody help me please.

I just Odin to EC05 last night.. and installed the new syndicate frozen rom... and my screen just went blank today.. so far it has done it twice in less then 5 minutes....
but I have noticed that if the phone is plugged into the charger that it wont do it.. no matter how long goes past.. thats the only way I know my alarm is gonna go off in the morning.. is to have it plugged in..
do anyone know if its doing it on plain Stock untouched modem and stock rom??
because if not imma flash over to that.. I cant take this crap too much longer..

I have had this so called SOD for almost 3-4 months and as a matter of fact I just ordered a replacement 10 minutes ago. My SOD involves the phone either rebooting or completely going black except for the bottom cap buttons, then vibrating in order once, then 3 times, then once, and so on until a battery pull. This has happened on the charger as well for some roms. I can tell you it does it on a stock rom. I just did a full reset, stock eb13, updated to ec05 OTA, wiped sdcard and everything except contacts. The problem exists, so I am almost 100% that it is a hardware flaw somewhere. I even did the ##786# reset. I'll let you know if a new phone fixes the issue :]

damn.. even on the stock rom huh???
well do anyone know if it might have something to do with rather journaling is on or off??
other wise.. i have not a clue of what could be causing it..

I have EC stock rom, but am rooted. It happens to my phone. It doesn't happen quite that often like you guys, but it happens maybe about once a day. It happened more frequently when I was on EB. It would happen at least 5 or 6 times a day. It's strange cause it never happened right when I flashed EB or EC. I was fine for a couple of days before it happened. Not sure why....?

I had to pull the battery 20 or more times today, same issue. Mine started doing it right after I added the news and weather widget to the homescreen. If it does it tonight im thinking of takin it back to stock and getting a replacement.
EB13 btw, flashed EC05 a few minutes ago and will try it out.

sultan.of.swing said:
I had to pull the battery 20 or more times today, same issue. Mine started doing it right after I added the news and weather widget to the homescreen. If it does it tonight im thinking of takin it back to stock and getting a replacement.
EB13 btw, flashed EC05 a few minutes ago and will try it out.
Click to expand...
Click to collapse
I had about six today. I'm flashing stock and running untouched starting tomorrow. If that doesn't fix it, it's replacement time for me too.
Sad, because a stress test on my phone at 1.4ghz ran fine.
Btw, I still use set cpu, but only in known safe configurations, no OC.

I just received my replacement. Brand new phone, I installed a formatted sdcard and synced contacts... within 10 minutes it seemed to be happening again. The phone was stock di18, then it updated to stock EB05... I have no idea what the problem could be now, since this phone is brand new.

Odd Problems with HTC Hero CDMA

I have this weird problem, and I can't figure out the cause.
Whenever I use my phone lately, it will randomly freeze/force close certain apps. It's super laggy. If I drag my hand/palm across the touch screen, it will stop lagging and perform all the touch commands that I had "queued" up. This seems to persist even though I just wiped+flashed my phone again.
I've got nandroid backups for my stock hero, CM6.1.0, and now I just wiped and flashed to CM7.0.2. Sitting in the CM7.0.2 setup wizard as I type this, and it's lagging like crazy. Is it possible my Hero is internally damaged somehow and that's causing the problems, or does it sound like software? My Hero has been through a LOT of bumps, some harder than any phone should have to endure.
Still, I'm strapped for cash and making the best of what I've got. Anyone got any ideas? Is it possible that I screwed something up using the adb shell when I was a little nooblet? And that said, is there anyway to wipe everything and start with a completely clean slate?

rjhall said:
I have this weird problem, and I can't figure out the cause.
And that said, is there anyway to wipe everything and start with a completely clean slate?
Click to expand...
Click to collapse
I'm new here but I've had a lot of different problems also. What I do is RUU and start over. It fixes a lot of screwups on my part... if you have the problems after RUU with stock s/w then I'd have to say its your phone. Good Luck.

rjhall said:
I have this weird problem, and I can't figure out the cause.
Whenever I use my phone lately, it will randomly freeze/force close certain apps. It's super laggy. If I drag my hand/palm across the touch screen, it will stop lagging and perform all the touch commands that I had "queued" up. This seems to persist even though I just wiped+flashed my phone again.
I've got nandroid backups for my stock hero, CM6.1.0, and now I just wiped and flashed to CM7.0.2. Sitting in the CM7.0.2 setup wizard as I type this, and it's lagging like crazy. Is it possible my Hero is internally damaged somehow and that's causing the problems, or does it sound like software? My Hero has been through a LOT of bumps, some harder than any phone should have to endure.
Still, I'm strapped for cash and making the best of what I've got. Anyone got any ideas? Is it possible that I screwed something up using the adb shell when I was a little nooblet? And that said, is there anyway to wipe everything and start with a completely clean slate?
Click to expand...
Click to collapse
First when a rom is starting up, it's likely to be SLOW, for 2 reasons, kernels need to "warm up" and the market is probably downloading a crapload of apps (this is a new feature). Second, it sounds like maybe you're device is running low on RAM, I would suggest you get an app from the market called "autokiller" and set the preset called "optimum". Third, go into settings/cm settings/performance and then set your governor to interactive 352-691 or ondemand 264-691. Fourth, go read a LOT of the threads in here and learn some stuff that will help you. Fifth, what recovery are you using and what exactly did you "wipe". Sixth, what do you mean could you have messed something up with adb shell?

il Duce said:
First when a rom is starting up, it's likely to be SLOW, for 2 reasons, kernels need to "warm up" and the market is probably downloading a crapload of apps (this is a new feature). Second, it sounds like maybe you're device is running low on RAM, I would suggest you get an app from the market called "autokiller" and set the preset called "optimum". Third, go into settings/cm settings/performance and then set your governor to interactive 352-691 or ondemand 264-691. Fourth, go read a LOT of the threads in here and learn some stuff that will help you. Fifth, what recovery are you using and what exactly did you "wipe". Sixth, what do you mean could you have messed something up with adb shell?
Click to expand...
Click to collapse
1. Yeah I know that. I hadn't had this problem until the last couple months. Until then, it was more or less okay. The problem is, it really is a completely fresh rom.
2. The Hero is kind of a low memory phone to begin with, so that's certainly a possibility. 2.2 and 2.3 aren't exactly kind on old hardware.
3. I don't have those settings in 6.1.0. I was using SetCPU for awhile with it at 480-7XX (Can't remember, I think 791, as that was max) and OnDemand. I had some screen off, temperature, and battery profiles too.
4. Any specific threads I should read you can suggest? I was lurking on the forums for awhile before I did anything to my phone (didn't want to brick it).
5. I'm currently using Amon RA 1.6.2. I considered clockwork, but some people said it has more problems. I've heard complaints that Amon RA requires signed packages, but frankly it hasn't been a problem thus far. It actually saved me from bricking my phone when I was new to this whole thing. As for what I wiped, I simply went through Amon RA and wiped data, dalvik, battery stats and rotation. Don't know what battery stats/rotation are, but I am familiar with the Dalvik cache.
6. As for saying I could have messed something up, when I was flashing my phone, it was something I'd never done before. It's certainly possible I mistyped something or screwed something up.
I was hoping someone could help me to completely wipe it and start fresh, since I'm sure it's had its share of problems.

I would suggest flashing clockwork. You can wipe more areas of the system then the one you have. And it has more features. I personally made the switch.
As for your lag, it might be your hardware. If you did a clean install and wiped boot, system, cache, data, and dalvik, and installed the latest stable release and it's still laggy? Then things are not looking good brother.
You experience the same thing on a sense base ROM?

also it could be cpu govenors because usually by default most roms have it set to ondemand witch has always caused problems for me and as soon as i set it to performance its fine.

Bierce22 said:
also it could be cpu govenors because usually by default most roms have it set to ondemand witch has always caused problems for me and as soon as i set it to performance its fine.
Click to expand...
Click to collapse
Are you aware that the performance governor runs at the MAX CPU speed all the time? Seriously. Your battery life must suck.
sent from a series of tubes.

yea but otherwise my performance sucks lol.
most of the time on aosp and cm7 i cant even stream music without it freezing unless i set it to performance.

Houndog101 said:
I'm new here but I've had a lot of different problems also. What I do is RUU and start over. It fixes a lot of screwups on my part... if you have the problems after RUU with stock s/w then I'd have to say its your phone. Good Luck.
Click to expand...
Click to collapse
What is RUU? How do I do this? I tried to search the forums but it said search was unavailable. Would this return the phone to 100% stock, no recovery software or anything? That's really what I'd like to do now, to make sure there's not a trace of rooting or flashing left, that way I can start from scratch.
oohaylima said:
I would suggest flashing clockwork. You can wipe more areas of the system then the one you have. And it has more features. I personally made the switch.
As for your lag, it might be your hardware. If you did a clean install and wiped boot, system, cache, data, and dalvik, and installed the latest stable release and it's still laggy? Then things are not looking good brother.
You experience the same thing on a sense base ROM?
Click to expand...
Click to collapse
I tried using RomManager to flash Clockwork, and it still booted to Amon RA recovery. I'm going to try to use ADB to do it, but I don't know that I'll be able to.
EDIT: Manually pushed ClockworkMod Recovery v2.5.0.7 onto my Hero.
Before I touch any of these settings, what will format boot, format system, formata data, and format cache do? Can it brick my phone, or will it let me flash a ROM onto a completely clean phone?

hmm thats very weird thats just about the only thing rom manager is good for now adays is installing cmr

rjhall said:
Before I touch any of these settings, what will format boot, format system, formata data, and format cache do? Can it brick my phone, or will it let me flash a ROM onto a completely clean phone?
Click to expand...
Click to collapse
You will not brick, that is how you wipe. You should also wipe dalvik cache. Go to this site for really good instructions :
www.romrepo.info/wiki

But please note when u wipe u "wipe" lol you will loose all your market apps and anything else installed just make sure you dont wipe sd card then youll loose all your photos and music backups exc...

rjhall said:
What is RUU? How do I do this? I tried to search the forums but it said search was unavailable. Would this return the phone to 100% stock, no recovery software or anything? That's really what I'd like to do now, to make sure there's not a trace of rooting or flashing left, that way I can start from scratch.
Click to expand...
Click to collapse
So I downloaded the 2.1 update from the HTC website, ran it, and it completed with no problems. Phone booted up, and now I'm trying to go through the tutorial, lagging all the while. It's almost impossible to type.
Does this mean it's hardware related?

sorry for not posting sooner but lagg isnt usually caused by hardware the kernal probably has to worm up also is it the 2.27 software update or 2.3 because 2.27 lagged pretty bad anyway and if your typing with vibrate on keypress try turning that of it always helped me.

Bierce22 said:
sorry for not posting sooner but lagg isnt usually caused by hardware the kernal probably has to worm up also is it the 2.27 software update or 2.3 because 2.27 lagged pretty bad anyway and if your typing with vibrate on keypress try turning that of it always helped me.
Click to expand...
Click to collapse
I had to start from scratch several times and my phone was pretty snappy when I first started it up after RUU. Also you stated your phone was fine and then just started running slow for no reason, was this after it took a bump?

are you talking to me or rjhall lol

Bierce22 said:
are you talking to me or rjhall lol
Click to expand...
Click to collapse
sorry, RJhall..

I don't recall it taking any bumps before it just stopped working like it has.
However, I have found how to "fix" the problem. If I squeeze the sides of the phone in, it stops lagging and works. Any touch motions of queued up will then immediately execute. Any idea what in the phone is physically broken?

rjhall said:
I don't recall it taking any bumps before it just stopped working like it has.
However, I have found how to "fix" the problem. If I squeeze the sides of the phone in, it stops lagging and works. Any touch motions of queued up will then immediately execute. Any idea what in the phone is physically broken?
Click to expand...
Click to collapse
Never had mine apart, maybe someone has and can help..

Okay so things have gotten increasingly weird. It used to be that squeezing the sides of the phone allowed the touch screen to work. Yesterday that stopped working altogether. Today, the screen stopped turning on at all. The LCD simply doesn't turn on. Pressing the red button turns on the phone (it vibrates when turning it on) and when the phone is on, pressing the red button lights up the keys (so I know it's waking the phone up). I took the phone apart (much simpler than I thought it would be) but I was unable to find anything that seemed out of place or broken. Does anyone have any ideas?

Bizarre FCs

Ok, if anyone can help me out on this, I'd be really grateful.
So, it started something like a couple months ago.
I was on Cyber.GR and Matr1x kernel, all was fine, when suddenly the phone stopped being usable: everything FC'd at boot and rebooting was of no use. I was pissed off but luckily I had a NANDROID from a couple days before.
I restored it and all was fine again.
One week passes and BAM everything FCs again.
I tried to switch kernels, but nothing.
I decided to wipe everything and flash AOKP (faster updates and Cyber.GR dev was going in service) and AIR Kernel.
I restored my apps using Titanium and everything was fine again.
One month passes and all of a sudden, a friday night, FCs again.
I was in panic, tried reflashing kernel, fixing permissions, wiping cache and dalvik, no use.
So I googled a little bit and found out that reflashing the ROM usually fixed the problem.
I reflashed ROM and gapps and, as google said, everything was back to normal.
Except that once again, nothing's fixed.
The phone stays stable for a couple of weeks circa, then it starts again to force close everything.
Reflashing ROM and gapps seems to fix this, but as you can see it isn't a permanent solution.
I post a logcat I took when the FCs started, so it's like 2 months old.
If anyone knows the reason of all of this, I will gladly pay you a couple beers: this ****'s driving me nuts.
Here's the logcat: http://pastebin.com/C6hr0sDT
tl;dr: phone randomly start force closing everything at boot on different combos of kernels and ROMs. no ****ing idea. paying money for solution.

Have you tried using another ROM? Seems like the easiest route to take.
Sent by pocket technology

After you flash the rom when you install your apps again do you just install the app or do you install with data? Its better to install apps fresh cuz if the data's corrupted then your going to get FC! Try installing the CM9 Skank Rom & don't flash another kernel leave it as is then install all your apps fresh no data & run it for weeks or months see if your still having fc the CM9 skank kang Rom are really great & stable try it out here you go! :thumbup:
http://forum.xda-developers.com/showthread.php?t=1386869
°N€×U$ $⁴G°

Make sure not to include system apps when restoring backups using tb. That might be the issue
Sent from my Nexus S®

That as well. I saw you did use AOKP also. Hmmmm. In my personal experience, my phone likes stockish kernels. Matrix always froze up on me after 100+ hours of up time with the stock nexus voltages applied. Air Kernel always gave me FCs. My phone is picky. No idea why. Maybe try using another kernel, stockish this time and see what happens? I haven't had any lock ups using thalamus', Pete's or, Simple Kernel.
Sent by pocket technology

Ok, first, I tried two ROMS as I said, Cyber.GR MOD and AOKP (M5, b37, b38). Always errors.
On thing I did, however, is restoring apps with data. Well, next time I have a spare day I'll try this way (even if my heart cries a little at the thought of logging in and reconfiguring every single app I have ).
Fun thing is that it happens randomly. For example, last night I went to sleep and left the phone charging: this morning FCs. Nothing's changed during night, I think
Thanks for the replies, guys!

Ok, first, I tried two ROMS as I said, Cyber.GR MOD and AOKP (M5, b37, b38). Always errors.<br />
On thing I did, however, is restoring apps with data. Well, next time I have a spare day I'll try this way (even if my heart cries a little at the thought of logging in and reconfiguring every single app I have ).<br />
Fun thing is that it happens randomly. For example, last night I went to sleep and left the phone charging: this morning FCs. Nothing's changed during night, I think <br />
Thanks for the replies, guys!
Click to expand...
Click to collapse
Yeah starting from scratch will not hurt too much ;-)
Sent from my Nexus S®