Hi All,
I have a problem where my phone crashes and reboots when I launch an app that uses the camera in any way, for example layar, barcode scanner, camera etc. This only happens in Android 2.1, I've tried various ROMs and always the same issue. I've tested Android 1.5 and there are no problems with that at all.
I've noticed the crashes only occur when I'm on battery power, it never happens when the phone is plugged in so I cannot get logs to see what is going on, unless someone knows a way to get the logs from a crash.
I was wondering if anyone else has seen this problem and if so, if they've found a resolution to it.
Since updating with the OTA 2.1 update I have been experiencing this problem too. Phone reboots when it uses the camera, Layar, Yelp, AugSatNav all seem to cause the problem.
I get this problem too, with the camera, and also sometimes when I put the volume down it freezes and reboots
Sent from my HTC Hero using XDA App
I've got the same problem. Restarting when launching apps using the camera.. Im glad that's not a HW problem but "only" SW bug.. I hope
It could (and probably is) a radio issue....Happens on the N1 and Desire if you try to use the camera too and seeing as the GPS,Camera both are dependant on the radio id say that is it! Find the radio reccomended with the rom you use and flash it( Beware of orange users being locked down though,you need a specific radio)
Just to add that I'm getting the same problem too running FroydVillain 1.2.2 and baseband 6.35.15.14, should point out that been having the problem for quite a while on a multitude of ROMs :-(
I'm not - did you full wipe?
Multiple wipes...
try 1.3 i guess
I had this problem when I was on stock 2. 1 I would recommend rooting and flashing froydvillain.
Sent from my HTC Hero using XDA App
Tried multiple ROMs and multiple Radios with no change :-(
Unless theres a second secret wipe button hidden in recovery I don't know what else I can do :-/
try to disable "automatic brightness"...
Gynjanynja said:
I had this problem when I was on stock 2. 1 I would recommend rooting and flashing froydvillain.
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Hi,
I have had this problem since i went to 2.1 also, i have also flashed several rom's since villainrom 12 and have even used rcmix 1.0b which is a great 2.1 imo.
Have flashed 2.2 roms, and i am still having the same problem.
This is how i can replicate this problem and how it occurs, to the letter.
1.Bring phone out of lockscreen.
2.Open camera.
3.Take pic, in dark or light lighting with brightness on any setting.
4.Save pic.
5.Close camera.
6.Lock phone and wait for 10 seconds.
7.Bring phone out of lockscreen.
8.Open camera.
9.Phones lights all go out and the hero name flashes up onto the screen.
10.Full reboot.
This happens everytime no matter what.
Some things to consider.
The phone will never reboot if it is plugged in to a usb / electric plug Charger and is actually charging.
The phone will remain on and will carry on taking pictures IF you don't close out of the camera the first time around.
No task killer was installed on my phone at the time of this test, although i have had task killers before with the same results.
Lighting effects and brightness can sometimes have an effect on the ratio and probablility of a reboot, with brightness on full in a dark room being the most probable.
I am using the newest froyd rom 1.4.3 although i have tried pretty much every rom out there, I NEVER have this error when i installed a 1.5 rom which does not have apps2sd (weird that) which tells me that it is NOT a hardware fault.
I am using villains no logo kernel 19mhz - 691mhz
63.18.55.06PH_6.35.15.14 Radio
HTC Hero on Orage UK.
IF anybody can shed any light on this rather annoying matter resulting in this problem being erradicated will earn my eternal respect and a big clock. : )
dladz said:
This is how i can replicate this problem and how it occurs, to the letter.
1.Bring phone out of lockscreen.
2.Open camera.
3.Take pic, in dark or light lighting with brightness on any setting.
4.Save pic.
5.Close camera.
6.Lock phone and wait for 10 seconds.
7.Bring phone out of lockscreen.
8.Open camera.
9.Phones lights all go out and the hero name flashes up onto the screen.
10.Full reboot.
This happens everytime no matter what.
Click to expand...
Click to collapse
I can confirm that this isn't a bug on every install of 2.1 or 2.1 as I am unable to replicate the issue as described. Also if you've tried mutiple software and the bug is occurring across many that would suggest it is something hardware related or you are not performing a full wipe. Have you tried backing up the data on your sd card and formatting that then putting back only the necessary data (pics / music etc)?
btdag said:
I can confirm that this isn't a bug on every install of 2.1 or 2.1 as I am unable to replicate the issue as described. Also if you've tried mutiple software and the bug is occurring across many that would suggest it is something hardware related or you are not performing a full wipe. Have you tried backing up the data on your sd card and formatting that then putting back only the necessary data (pics / music etc)?
Click to expand...
Click to collapse
I originally posted this issue and the descriptions from everyone else with the problem match mine pretty much perfectly.
I've taken all info off the sd card and performed a complete wipe of data, ext and davlik before formatting the sd card. I've put the blank SD card (apart from the ROM I'm about to flash) back into the phone and flashed. After config and before any new apps are installed on the phone I launch the camera and within 4 attempts at start the camera the phone will crash. This has happened across every 2.1 ROM I've tried, but doesn't happen on 1.5 ROMs.
Using the stock camera app? Have you tried without installing any of your own apps at all?
This is very odd. No matter what I try I can't get the camera app to crash. Though I am using v2.2 of android. Have you tried official 2.1? Vanilla and Sense?
btdag said:
Using the stock camera app? Have you tried without installing any of your own apps at all?
This is very odd. No matter what I try I can't get the camera app to crash. Though I am using v2.2 of android. Have you tried official 2.1? Vanilla and Sense?
Click to expand...
Click to collapse
Yep, it crashes using the stock app.
I've tried a rooted version of the offical but not the actual OTA update. I've not tried vanilla as I don't really want to run vanilla on it.
I've managed to take some logcat logs of the problem happening but there's nothing really specifc happening over a few crashes that would point to anything. .
I'm going to try to unroot my hero and downgrade to stock to start again. Just have to find a way to downgrade my bootloader first so I can put on the original RRU. I tried to downgrade before but got an invalid bootloader error.
The camera crash doesn't really affect me day to day as I don't really use the camera, where it is annoying is it stops you using apps that use the camera like goggles and layar.
Ahh - so its not the camera app that is crashing but other apps too which are using the camera. Very odd.
And FYI - you don't need to touch your bootloader - just change the driver in windows to My HTC instead of HTC Bootloader and the rru will work.
btdag said:
I can confirm that this isn't a bug on every install of 2.1 or 2.1 as I am unable to replicate the issue as described. Also if you've tried mutiple software and the bug is occurring across many that would suggest it is something hardware related or you are not performing a full wipe. Have you tried backing up the data on your sd card and formatting that then putting back only the necessary data (pics / music etc)?
Click to expand...
Click to collapse
I have formatted and re partitioned my sd card to a T and it still occurs and thats with everytime i install a new rom, i don't use titanium i go the long way around every time and re set up all my programs, I know i can replicate this error like i said and like i also said this does not occur in 1.5 roms.
I have also have this problem with vanilla, modaco's new one, villain rom, rcmix, froyd, it appears that ever since the phone was updated to 2.1 there is a problem when using the camera app.
I have tried to install a rom and replicate the issue without installing any apps at all and it still persists, the only thing i can say is that it doesn't happen when i'm either on 1.5 OR the phone is charging?
It sounds like the the phone is requesting access for use of the camera and then not putting back what it requested in the first place, like a cache or something, and it simply make the phone reboot when it is called upon again.
I don't believe it is a hardware fault, i know this sounds like wishful thinking but the phone does not have this error in 1.5 roms. Thus, it cannot be hardware. Simple!
Also a logcat does not show anything, i was only able to replicate the error once whilst my phone was plugged in, it just won't do it again, and when i posted my findings on villainroms bug report section, a few of the lads still didn't know what it was so i don't know what else to say.
I'm due for an upgrade in October so for me at least it's not that much of a deal but i'm planning on giving this phone to my daughter so it would be good to get it working for her.
Would save me a lot of earache.
If u need to know anything else then please let me know, oh and i am using a class 2 sd card, which i have been unable to change, however just today my girlfriend has just had a class six delivered and her old one will be up for grabs so i will test with that too. Has anyone else tried with multiple cards??? Also how do i find out what boot loader i am using (recover) as maybe the problem resides there.
btdag said:
Ahh - so its not the camera app that is crashing but other apps too which are using the camera. Very odd.
And FYI - you don't need to touch your bootloader - just change the driver in windows to My HTC instead of HTC Bootloader and the rru will work.
Click to expand...
Click to collapse
Thats right, its any app which accesses the camera.
What could be the correlation between connecting the charger and not connecting the charger, could that be a power issue and the battery is delivering too low a power output on it's own to run the camera? Hence it works with the charger plugged in ?? Either way i think that is the only real clue there is to be honest, unless your phones still restart when the phone is plugged in, in which case it's not much use.
Related
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.
1- Hello guys, I have an T-Mobile USA HD2. I love it but it freezes like crazy, 2-3 times a day if not more. I ran Task 29 to delete every possible trail of previous roms followed by a hard reset but nothing. It will still freeze.
2- I also have a lot of signal problems. Its constantly changing from 3G to Edge on the same location. I know that is not normal so I spoke to T-Mobile and they changed the SIM card but it will still change the signal back and forth. I re-flashed couple of radios but nothing, I only accomplished to drain more battery.
3- BSB Tweaks is an awesome app but there are issues with the Rotation Option. If I enable Rotation to the "Start" -> "home screen" the photo album and music will be affected because the already come with landscape support. I tried to disable the landscape support for these using a registry editor but did not find a way.
Is there any solutions for these problems? Any help will be very much appreciated, not only from be but as well from others with the same or similar problems. Thanks in advance to all of you.
Note: I noticed the recently released TMUSA HD2s come with a yellow reset button. I bought my back on March when they sold out Nation wide with in the firs 4 hours and it comes with a RED reset button. This might explain a lot. If you know something please share. Thanks!
I would like to know if there is help for freezing issue.
I also did Task 29, flashed few different radios, few different roms incoluding stock, and it still happens. If my phone freezes I have to try for 20 minutes to restart it, as it hangs everywhere starting with bootloader, to manila.
Any help would be GREATLY appreciated!
I had a similar issue as well and it turned out to be a cab file I had installed that was not compatible for my ROM. I had to go through and isolate which cab it was by using the date it was added and when I noticed the issues.
When your phones freeze....does it do it radomly or while trying to access or carry out anything specific. Your problem could be caused by any number of reasons but giving as much detail regarding your problem keeps you from getting so frustrated trying all sorts of fixes. Out of curiosity what ROM's are you both currently running?
I am currently using Elegancia ROM from August 23. Before I was using Energy ROM. I tried newest, stock Rom for T-Mobile HD2 but it didn't solve the issue.
I tried reinstalling HSPL, but it didn't help either.
The problem started after I put Ubuntu 0.2 on my sd card. I was playing with it for a little and it suddenly rebooted my HD2. I though, OK, no big deal, it's just in infant stage.
So I booted Windows again (energy rom with 2.12 radio) but it hanged while Sense was loading. I wasn't able to get it back to life after few reboots so I did a hard reset (vol up/down power on) It worked fine.
My problem mostly happens when I run android and when it reboots for some reason I can't get back to windows. It hangs, sometimes it hangs on bootloader before it even shows me radio and data version!! sometimes it goes past bootloader and hangs right after sense launches, and sometimes it is perfectly fine.
It also seems that when I just use WinMo it is fine, I can power down, and soft reset without major issues. But after running android I get that issues, especially when Android crushes.
I am thinking that android may be corrupting some WinMo files, but how is that possible? Android doesn't have access to NAND so technically it shouldn't prevent WinMo from booting on bootloader level.
Please let me know if you need me to explain more.
Thanks for your help
KML
PS. I don't have any custom cabs installed at this point. I have super fresh and clean installation of elegancia rom
Yeah...Android may be the culprit. I have shyed away from trying it because I have talked to quite a few people (not on XDA) that have tried it on the HD2 and they have the same issues. The Android OS really makes the HD2 unstable. I personally am going to hold off on the Android bandwagon until a little more time passes, after all WinMo works just fine for me. Try just running on WinMo and see what happens. Based on what you have said, it runs fine as long as you are not using Android
yeah, it's is good idea to stay away for some time. But Android development needs testers. If no one is willing to test than there will be no improvement.
What I can't understand is that even after I do hard reset I still get freezes.
kml.krk said:
yeah, it's is good idea to stay away for some time. But Android development needs testers. If no one is willing to test than there will be no improvement.
What I can't understand is that even after I do hard reset I still get freezes.
Click to expand...
Click to collapse
Yeah I agree with you on Android development needing testers. I do rely on my phone a lot for work purposes and I can't always afford to have the phone freezing up constantly.
Are you hard re-setting with the Android OS still installed?
Technically it is still installed but it is only present on the SD Card, and not anywhere else so it shouldn't matter. Next time I get freeze I will try to remove SD Card before hard resetting.
I tried booting few times with SD Card taken out, but it didn't help.
KML
I have the same issue...i'm using energy rom and i noticed that lately its freezing like hell...at least twice a day...!! NRGZ already notice the freezing issue and is trying to solve it...but it still crashes. I'm constantly changing the rom as he updates...and right now i'm running the August 25.
Sometimes it crashes while being turned off...and i need to take the battery off to restart.
I had the same issue,all i did loaded a diff rom and formatted my sim card problem solved
I did format my SD Card many times. Did not help. I used recommended FAT32.
Yesterday my phone froze when I was trying to add program shortcut to Sense... silly.
I rebooted phone, it booted fine, but hang as soon as I went to check my TXT messages. Rebooted again and it is working fine until now.
I currently have Elegancia ROM with 2.12.50 radio, have not been using android for couple of days, but it is still there on my SD Card.
It is getting a bit frustrating. I wonder what else I can try to make it stop freezing.
KML
My phone rebooted again yesterday.
I couldn't boot to windows for the next 20 minutes... I tried about 10 times before it worked. 2 or 3 times it booted windows and froze as soon as I clicked on one of sense tabs.
I haven't played with Android for past week and the freezing problem is still an issue. I even removed andorid form my SD Card.
When all this happened I was just using skyfire to browse internet.
I am hopeless at this point. I have no idea what else I could try to make it stop rebooting and freeezing.
Any ideas?? I would greatly appreciate any help.
PS. I recently found a thread about a tool that searches for corrupt files on Android devices after clean flash, is there something similar available for WinMo?
Here is the thread I am talking about:
http://www.xda-developers.com/android/fixflash-rom-flash-verify-and-repair-tool/
screen doesn't respond to touch
I just started having this issue today. I have used darkstones most recent build from the 18th. it has worked perfectly till today. I use energy roms. i just installed a older rom today still have the same problem. this problem appears weither in droid or winmo. All the hard keys still function and the phone can receive calls. Thanks for any help you may be to lend.
my phone just froze again.
All I did was take it out of my pocket and unlock screen, and there it is: FREEZEEEEEEEEEEEEEEEEE
Funny thing is that Android doesn't freeze for me... it crashes sometimes, but never freezes. It is only WinMo that freezes on me or doesn't boot. Android always boots.
I really wish the NAND was accessible so I could flash Android to NAND and forget about WinMo
kml.krk said:
I really wish the NAND was accessible so I could flash Android to NAND and forget about WinMo
Click to expand...
Click to collapse
you, me and 17,000+ HD2 owners are all wishing for that exact thing
Your issue with the freezing/rebooting is stumping me too. You've flashed different ROM's, including stock, done hard resets, checked the battery pins, reformatted the SD card and even tried running the phone without the SD card inserted...do I have all that right? The fact that it doesn't show the symptoms when running Android just makes it that much more mysterious. I'd say it all points to a hardware issue, but if it doesn't act that way when you're in Android, that (probably) shoots that theory out of the water. But, at the same time, running task 29 and reflashing different ROM's should also have eliminated any possible software-based causes, so....
the only thing that comes to my mind is micro SIM card. I did an upgrade on my ATT account to get iPhone (traded for HD2) and those fu...ers at ATT wouldn't let me keep my regular sized SIM card. I had to use my old SIM card and cut it's inside to place micro sim in it. I used a regular sied SIM to hold micro SIM in place.
I don't think however that this is a problem because I believe my phone froze few times before I did that SIM card swap besides, I have no issues with phone calls or reception both in Android or WinMo.
I am clueless at this point.
I just got another Android version and will try it to see how it works. If I have any problems I will try using my wive's SIM card to see if it helps with freezing and WinMo booting.
KML
EDIT: ANDROID just rebooted itself. 2 minutes after clean installation. geee, I am leaning towards Hardware being the issue.
What I did is:
1. open browser
2. go to google
3. search for speedtest
4. open speedtest.net
and Android rebooted itself and now my phone can't go past Tmobile bootloader logo (pink square with 'stick together' letters)
I will put different SIM inside now and try everything again
kml.krk said:
the only thing that comes to my mind is micro SIM card. I did an upgrade on my ATT account to get iPhone (traded for HD2) and those fu...ers at ATT wouldn't let me keep my regular sized SIM card. I had to use my old SIM card and cut it's inside to place micro sim in it. I used a regular sied SIM to hold micro SIM in place.
I don't think however that this is a problem because I believe my phone froze few times before I did that SIM card swap besides, I have no issues with phone calls or reception both in Android or WinMo.
I am clueless at this point.
I just got another Android version and will try it to see how it works. If I have any problems I will try using my wive's SIM card to see if it helps with freezing and WinMo booting.
KML
Click to expand...
Click to collapse
Good call, that's about the only other thing to try. However....have you tried running WM with sense disabled, to see if it still has the freezing/rebooting issues? That might at least narrow the problem down to something sense-related (which is easily the most common cause of any software-related issue on this phone)
sirphunkee said:
Good call, that's about the only other thing to try. However....have you tried running WM with sense disabled, to see if it still has the freezing/rebooting issues? That might at least narrow the problem down to something sense-related (which is easily the most common cause of any software-related issue on this phone)
Click to expand...
Click to collapse
I have NOT tried that but I will. The problem is that I often can't get past bootloader logo...
I modified my post above so please read it (I mentioned Android crashing)
thanks for all your suggestions
I just tried different SIM card. Phone booted fine to WinMo, and froze as soon as I clicked on Messaging tab in sense.
I will try to disable Sense for now.
I disabled Sense, rebooted WinMo launched Android repeated operation of trying to get to speedtest. Site launched, but phone rebooted after a while.
I am getting to conclusion that some software including flash causes my phone to reboot and then I can't get it to boot again..
Right now my phone is stuck again on bootloader. I already tried rebooting twice.
What I noticed is that every time my phone freezes it gets a little warmer in the lower left corner
What hardware is located in that area?
Hey
I'm running DK 4.4, and my phone just appears to be randomly freezing while it's in my pocket.
I should note this has been happening with other roms as well, so I seriously doubt it's a rom issue.
I'm not overclocked (anymore).
The screen just won't turn on.
People can even call me and to them it seems like it's ringing, but it's not and nothing happens.
The only way to recover from that seems to be to take the battery out and put it back in.
I finally managed to catch it in action and have a look at the log, but I couldn't find anything useful.
Maybe someone else can
logcat:
http://pastebin.com/kS3EnPQa
Also, I should mention the freeze happened a couple of minutes before the end of this logcat, the log keeps updating even though the phone appears frozen.
adb shell doesn't seem to work, though, and neither does adb reboot
Thanks
Hi. Flash an old 2.1 stock RUU original rom, root again and check if the phone works. Sounds like a Software or Hardware issue. Otherwise you can try to wipe phone and test the DK ROM again.
Do you use cache to ext? Download and install free app ap2sd GUI from Market and move cache back to internal. Maybe your sd card should be Checked too.
Do you use the default dk Kernel without over or downclock under 3cxphone MHz?
Sent from my HTC Wildfire using Tapatalk
Fair enough, I'll try it.
I'm curious, though, are you actually seeing something in the log?
As for the cache to ext, my dalvik cache used to be on my SD card, but I already moved it back thinking it might be the issue
EDIT: as for the kernel, I use the original DK one (iirc that's the original HTC kernel?), shouldn't be over/underclocked.
I had this same issue and was about to return my Wildfire, but then the microSD died! So I got a new one and its been fine ever since so maybe try another card if you can and if the above suggestion doesn't work.
Sent from my HTC Wildfire using Tapatalk
Thanks for the suggestions!
I'll be sure to try them. Maybe my Wildfire isn't on its death bed after all
Your not the only one my GFs phone has the dame prob plz do let me know if u manage to fix it. Thx
P.s. her phone's completely stock no root no nothing.
Sent from my Desire HD using XDA Premium App
It definitely seems like it's the SD card.
I tried using a different one and I haven't had any problems for about 48 hours.
Will update if it changes
Thanks a lot for the suggestions, guys!
gbesso said:
It definitely seems like it's the SD card.
I tried using a different one and I haven't had any problems for about 48 hours.
Will update if it changes
Thanks a lot for the suggestions, guys!
Click to expand...
Click to collapse
Thank YOU for keeping us updated
So I've tried everything I could think of. Reflashing ROM, using a different ROM, different browser, everything minus a different modem, which I'm not sure would really do anything. But where I'm at is that anytime I go to status on facebook it closes the browser back to the home. I'm on Frozen ROM at the moment, I've tried on stock, same issue. Tried on the ASOP ROM, same issue, tried on those ROM's with Dolphin, Miren, Firefox, Stock Browser, all the same issues.
So will a modem actually make a difference is how the phone handles? Or is it more related to data speeds? I don't know what else to do, this is driving me absoluetely nuts. Thanks Guys.
Try this go into settings / manage application / all application & wipe data from browser & wipe data from Google search then reboot if that doesn't work I don't know
Sent from my Nexus S 4G using xda premium
Figured I would move it to the proper area. Haha. I really appreciate all the help Bro. Tried the other route you said, nothing doing. So I don't know either. It's annoying though. I think I got the phone into a bootloop now tried to install a different ROM see if that would work, and doesn't seem to be working. Piece of crap. Just my luck. Ha.`
What kernals were/are you running?
Okay, so I did ALL that, and nope, same issue. I don't know what the hell the issue is, I thought it might be the kernal, but when I flashed back to stock, had the same issue, with no kernal. So I don't know.....doesn't do this on my Photon.
odin back to stock
and clear out the sd card. redownload everything and rebackup.
Did you uninstall the Facebook app and redownload it? Wipe data in it before uninstalling. Did you try a different browser like Miren or Dolphin?
xTMFxOffshore said:
Okay, so I did ALL that, and nope, same issue. I don't know what the hell the issue is, I thought it might be the kernal, but when I flashed back to stock, had the same issue, with no kernal. So I don't know.....doesn't do this on my Photon.
Click to expand...
Click to collapse
Well, you aren't running without a kernel - the kernel is the core of the Android operating system.
Maybe you're having a hardware issue, such as a touch screen that's acting up (you said it wasn't force closing or anything, right?) - it could be registering false touches in the wrong location... I'm just taking a shot in the dark on this one, since it sounds like you've tried restoring just about everything...
I would suggest reformatting your sd card (copy the contents to your computer first, the card WILL be erased).
Then, Odin a full stock tar (try DI18, you'll get an OTA to EC05 after you boot).
Then use the one click root and recovery - be sure to have the rom on your sd card, especially if you use an ext4 recovery like 3.1.0.1, because of the file system conversion (stock kernel won't boot ext4, so you'll need to flash the rom and an ext4 kernel before rebooting from recovery - Genocide or ACS's twilight zone or vision kernel... I would stick to Genocide for now, under worked the best for me)
You might want to skip the rooting step momentarily, so you can see if the same problem occurs on a completely stock setup.
Finally, I would suggest carefully cleaning your touch screen with something mild - I use eyeglass cleaner (safe for glasses with all the expensive protective coatings), other users here might have other suggestions.
This should cover all of your bases, and if you still have problems, it might be a hardware issue.
I do want to point out that (unless I'm missing something about what you're trying to do) the facebook that you access from the browser is loaded from their servers every time you connect - it isn't software on your phone. It cannot be the older version, not like an app, which has to be updated on your phone. The pandora issue sounds like a different issue, but I still need to test that (had to get to sleep last night, I was passing out mid-sentence, lol)
EDIT: re read the first post... Pandora issue was mentioned in the SRF thread... But it seems you did try stock and other roms...
When you say it closes back to home, I think I misunderstood - I had an issue once or twice where facebook would act up, going back to my facebook home page, but did you mean that the browser simply closes and dumps you back to your phone's home screen?
Because that could be as basic as your capacitive home button registering a false touch (the opposite of the unresponsive button issue we're all used to, lol)... But cleaning the touch surface could still help... Turn the phone off first, and apply whatever cleaner you use VERY lightly... Don't use household cleaners, if you don't have eyeglass cleaner then I would research whether rubbing alcohol is safe for gorilla glass...
Side note - swype suggested "guerilla" glass... made me chuckle...
Sent from my SPH-D700 using XDA App
What he said. ^... Also I would let it
Repartition and reset time when you Odin back to stock. I know most people say not to when flashing some things, but this would be an exception. Also when you flash to stock use the victory.pit file as well as the ROM tar.
Sent from my SPH-D700 using XDA App
All righty. I'm gonna try all that. As really nothing else has worked. I do think it's something with the screen though.....I just can't figure out why it only happens on the NEW facebook. I got her using the APP now she was only using the browser before, but I would punch say four letters it would bump a couple more then close. So you may be onto something with that touch screen registering incorrect keys so would that have anything to do with the contents of the SD card itself? Or is that an actual hardware conflict with the facebook (newer version) of the software? Cause it works fine on the APP. So I guess I'm basically at a loss for how this really makes any sense ,but really appreciate all the help from you guys.
I'm have troubles with my HD2 randomly rebooting itself for apparently no reason. Initially I had a barebone CM7 ROM, and it seemed to reboot much more frequently when I came home from university. As soon as I got home for this break, sure enough, it began rebooting again. I then switched to a CM10 ROM, thinking it was just the previous ROM messing up, yet the problem persisted.
If it's not a ROM causing it, what could it be? It's really annoying having the phone shut off randomly while I'm doing something, and I'm worried it'll end up worse just because of how frequently it reboots.
overheating? failing touch screen? dodgy battery? failing hardware? faulty/fake copy SD card? old/wearing out sim card? some app that doesnt play nice on the hd2?
they can all cause reboots on multiple roms, along with another half a dozen reasons, i'm sure.
If the phone did reboot from any of those, it still wouldn't explain why it doesn't happen when I'm at school. I'm not exaggerating; once I go back (about ~126 miles away from home), it never reboots like this. At this point, you may be thinking, "Why not just wait to go back?" I have only two semesters left, and I want to get this fixed prior to me moving back here.
But nonetheless:
overheating?
Click to expand...
Click to collapse
I've held my phone in front of an AC to test if it's overheating, and it still rebooted. I had the back cover off and the air blowing into the battery.
failing touch screen?
Click to expand...
Click to collapse
My 'End' button is failing, but my touch screen seems to work just fine. Is there a way I can test if it's the touch screen causing the reboots?
dodgy battery?
Click to expand...
Click to collapse
I have two batteries, one original and a new from Amazon. Reboots occur using either of those.
failing hardware?
Click to expand...
Click to collapse
Quite possible, it's an old phone, but I feel that it would reboot regardless of where I'm at if this was the case.
old/wearing out sim card?
Click to expand...
Click to collapse
Same as above.
some app that doesnt play nice on the hd2?
Click to expand...
Click to collapse
I thought this was the case at first as well, but I uninstalled all my apps on the barebone CM7 ROM, and reboots still occurred. Even after doing a fresh install of this CM10 ROM, the phone rebooted before I even began installing apps to it.
Are there any files that don't get changed by flashing a new ROM? I was thinking that it could possibly be the modem I have flashed to my phone, but I wasn't sure if flashing a new ROM automatically changes the modem as well. Can I get some insight on this?
By modem do you mean the radio? It's unlikely to be the radio itself, however it could be something like the phone struggling to switch between 2g and 3g,,try it with the phone in only 2g mode,, perhaps you have a faulty cell tower in your area,,unlikely but not unknown.
Yeah, sorry about the terminology haha. But thank you, I'll try that and report back!
So disabling the 3G didn't change anything, but I noticed a drop in the frequency of reboots when I disable my wifi. Could some of my router settings be messing with the phone? I tried deleting the network on the phone and re-adding it, but the reboots remained consistent.
adobrakic said:
So disabling the 3G didn't change anything, but I noticed a drop in the frequency of reboots when I disable my wifi. Could some of my router settings be messing with the phone? I tried deleting the network on the phone and re-adding it, but the reboots remained consistent.
Click to expand...
Click to collapse
still sounds like hardware really, as suggested.
does it reboot even with the phone in airplane mode?
But the phone doesn't reboot when I'm in the city where my university is located, only when I come back home. That doesn't really lead me to believe that it's the hardware.
I have the same problem with the
[1.Dec.2012][All in One] EvoHD2v10 ICS 4.0.4-full HWA "Fastest ICS ever"
it reboots more than 3x a week!!!!!!!
For me, it can literally get up to 10 reboots per day, when I'm in this particular city. It gets very aggravating, and I'm worried about the stress it's putting on the hardware by constantly booting back up.
Anyway, I decided to say **** it and start from scratch. I don't think it's a hardware problem, so I decided to go back to the beginning. I formatted and re-partitioned my SD card for Native SD-compatibility. I flashed Xylo's 4.1.2 PA ROM. Now it's time to use it like I would normally.
If anyone is experiencing the same problem as me, or reads this in the future with the same issue, I'll try to keep the post up-to-date with what stopped the reboots for me.
dont forget to clear out your sd card, , leftovers from previous roms can cause issues. Easiest way is to flash teh new rom, then immediately in CWM do a wipe data/factory reset, as this clears out both fat32 and ext folders.
AW: [Q] Can reboots be caused by location?
I had the same problem with my fathers HD2. I installed clK before and it rebooted the last time quite often.
So I reinstalled everything. I started installing the official HTC WinMo 6.5 Rom.
Then I've done Task29 and installed MagLdr and then a Radio which Supports 576 MB Ram. (I think it was 2.15.xx) , repartitioned it for BlueOrange Mix Rom 1.2 (The best I ever installed so far) and flashed it in CWM.
So the HD2 is running since 150 Hours without any Problems.
P.S.: Task29, MagLdr, Radio Installation and Repartition has been done in HD2 All in one Toolkit.
Greetings by Myself5 and I hope I could help you.
Sent from my GT-I9100 using xda premium