Hi all,
I have a weird problem with 2.1 ROMs. On most of them each time I access the camera with Camera application or any other one the requires camera, the phone reboots. It's not happening all the time, I noticed that this will most likely happen after I don't touch the phone for a period of time.
Is this happening to you too or it's my phone? I tried to format the card which I thought maybe has the file system corrupt.
Another strange thing is that the phone is not rebooting if it's connected to PC. This means I can't get a logcat with the error.
Thoughts?
Thanks!
iv had the same mate dont do it all the time but happened to me about 3 times i think im new to all of this i didnt want to wait for the update lol have you done all the updates for the rom ?
yep, I also have the latest radio.
So far Legendroid rom is the most stable. Looks like putting the camera at 3 MP makes it stable. Not sure, maybe it's just an impression
I heard that this is happening because of the camera drivers, and could be fixed once HTC releases the official 2.1 ROM for hero.
-A.
i have never had it do it since i have been using villian 4.0 legend beta 2 with the most up todate radio and i haver done all the updates.
Related
Morning, Fellow Forumers!
I've been using my HD2 for a few months now, and every day my frustration grows. This thing is unstable as hell. It either stops responding completely, or the phone application hangs (sometimes it's impossible to hang up a call), or just the backlight works, or the UMTS stops working... PAIN AND MISERY! I have it upgraded to the latest official firmware, but it doesn't help at all. Tried the Touch Tools to turn off unneccesary stuff - still no good.
It's even worse when it's BT'd to my Audi MMI. Every 10 seconds or so it's completely stuck for like 2-3 seconds. It looks like the BT firmware has not been optimized at all and whenever it refreshes the phonebook/calls list/etc with my car, the GUI is dead. Fixing that would be great stuff.
So, I'm asking to point me in the right direction. I don't care about warranty or anything, just want this device to be stable! Since the official FAQ is like 10 pages long... is there a FAQ's FAQ?
Basically - what's my first step? Thanks in advance!
PS: It's a retail version (non-branded) purchased in Poland.
Your solution Must be somewhere here:
http://forum.xda-developers.com/forumdisplay.php?s=&daysprune=-1&f=534
And Here:
http://forum.xda-developers.com/forumdisplay.php?s=&daysprune=-1&f=735
As for me I am very happy with my stock Rom,so far...!!
I have no problems with stock and with most of cooked ROMs
Have you tried re flashing the latest stock rom off the htc website?
task29 can solve most problems, however if you have done all those steps and still getting problams, you may have a faulty unit and it might need to be sent back for repair/replacement.
Really sorry to hear about your problems. Wish I could give you a good solution, other than to do a hard reset and then upgrade to the latest ROM. I am running a stock ROM and the HD2 is the best phone I have ever had. And I have had a few. Good luck.
I used my hd2 on a stock rom for ages, and it was stable enough, with the odd crash occassionally. I recommend using a custom rom. Since a custom rom, my battery life has improved dramatically, my hd2 runs faster and is so stable, i cant crash it if i really try!
Duttys V9 is a personal favourite
Thanks for your help, guys. I decided to reflash to chuckyROM's wm + android 2.2. On android, everything works so much smoother. The only problem is in 80% of the cases, phone would crash when I try to perform a BT call. Might be a wrong radio version, will keep trying.
tompken said:
Thanks for your help, guys. I decided to reflash to chuckyROM's wm + android 2.2. On android, everything works so much smoother. The only problem is in 80% of the cases, phone would crash when I try to perform a BT call. Might be a wrong radio version, will keep trying.
Click to expand...
Click to collapse
Bt calls are still unstable for everyone... work in peogress.....
Sent from my HTC HD2 using Tapatalk
Latest HomeBase (BLUR with kernel). When I first got the phone after a few hours you cannot hear or speak. You have to restart the phone in order to make or take a phone call. Assumed using a new rom would fix it considering the Sprint OTA fixed it but I still have the issue. After anywhere between 2 hours and 8 hours of the phone being on is when the problems start.
It was my understanding this was Software related but after trying a few roms with the same problem I don't know? Should I just go back to stock and install the OTA? Roms are cool but being able to talk is better.
I would. Also you should have posted this in the Q&A section or in the homebase rom thread.
Sent from my MB855 using XDA App
What version of the Home Base rom are you on? I'm on v1.5 with the 4.2 update and have no issues. So perhaps you could try that one? And I had that issue until the OTA update too.
b0r0b said:
Latest HomeBase (BLUR with kernel). When I first got the phone after a few hours you cannot hear or speak. You have to restart the phone in order to make or take a phone call. Assumed using a new rom would fix it considering the Sprint OTA fixed it but I still have the issue. After anywhere between 2 hours and 8 hours of the phone being on is when the problems start.
It was my understanding this was Software related but after trying a few roms with the same problem I don't know? Should I just go back to stock and install the OTA? Roms are cool but being able to talk is better.
Click to expand...
Click to collapse
To start, this isnt any type of development so it should be posted in general....
My question to you is do you have a Sprint airave in your home? That was the issue i had. If the problem is in custom roms try stock again.
xTMFxOffshore said:
What version of the Home Base rom are you on? I'm on v1.5 with the 4.2 update and have no issues. So perhaps you could try that one? And I had that issue until the OTA update too.
Click to expand...
Click to collapse
I've recently flashed v1.5 and updated with 4.2. Loved it except that when I tried to download anything in the market it would tell me that there was insufficient space on my device. I had even reformatted my external and internal storage. Then I tried using the marketfix.zip. It would say it was downloading and then disappear from my notifications. I was wondering if you were having this problem at all?
The only time I have had a market issue was when I first flashes the ROM and it was the old market then it dud a little song and dance and ypdated to the new market at which point anything I was downloading prior was gone. But after that haven't had any issues. Is this the issue you are having? If not.....try to reflash the ROM
Sent from my Photon via XDA
Alright, so first off I've had a few phones which I have rooted and modded to the extreme. Got a great deal on a e3d and came over.
Saw that i had hboot 1.50 and *tear*, however I followed the directions to a T and unlocked the phone, installed recovery, and threw on some well known mods.
MeanROM
CleanROM
Virus ROM
etc etc
Anyway, in all of the ROMs the camera is distorted, and when you try to use 3d it comes out greenish pixelated and crashes. When you take a 2d picture you can't see what you're pointing at, but when you click it takes a picture but well...see attachment.
Now here's what i have tried:
Re-wiped ROMs several times.
Installed Stock Kernals, and every kernel I could find.
Used the Flash app, used adb reboot-bootloader and then booted into recovery to flash roms, and most recently I re-locked the phone and used the RUU updater and Unrooted and installed stock back on phone.
STILL having same problem with camera.
So I'm asking anyone who'd like to help please, because if I can't get it working I'm taking it to sprint hopefully they'll replace it.
I would try running the RUU and see if that will get the camera going.
If it runs on stock then maybe your downloads got goofed up or somethin?
Also I think MeanROM is 2.17 base? (correct me if I'm wrong) but I think you need to update firmware on the phone for stability. The camera could be related. However I also think Virus' ROMs are 2.08, so that almost makes me think that this paragraph could be wrong.
wassti said:
I would try running the RUU and see if that will get the camera going.
If it runs on stock then maybe your downloads got goofed up or somethin?
Also I think MeanROM is 2.17 base? (correct me if I'm wrong) but I think you need to update firmware on the phone for stability. The camera could be related. However I also think Virus' ROMs are 2.08, so that almost makes me think that this paragraph could be wrong.
Click to expand...
Click to collapse
Already tried unrooting and flashing RUU. Still nothing....
Edit: I tried a factory recovery and no dice.
I'm going to try re-rooting and sending the camera file to the phone. Maybe it got corrupted?
Still open to suggestions.
Nope....
Sent from my PG86100 using xda premium
Ok so camera is clearly hardware issue. I relocked and factory reset. Camera still didn't work, today I clicked camera to show a friend. I had a twenty and accidently rubbed it on the screen and magically a picture appeared but it was split. I took a picture and boom it works. I'm going to mod it again when I get home, and I'll document the results, need to find out what happened.
Sent from my PG86100 using xda premium
It's a software issue. I am going to attempt to flash the kernel again and see if I can get it to work, anyone want to give me some tips?
It looks like I am having precisely the same issue. My camera worked fine until today. I restored a Nand backup of my original stock yesterday, but the camera was working fine after that. It started acting up when my wife called me on Qik Video. Tried restarting the phone numerous times, no dice. Came on XDA to hunt for stock kernels, thinking maybe my kernel got borked in the restore process? I'm truly shocked at just how huge a pain in the rear this phone is in terms of modding. Seems I am constantly having problems with it.
RavenFB said:
It looks like I am having precisely the same issue. My camera worked fine until today. I restored a Nand backup of my original stock yesterday, but the camera was working fine after that. It started acting up when my wife called me on Qik Video. Tried restarting the phone numerous times, no dice. Came on XDA to hunt for stock kernels, thinking maybe my kernel got borked in the restore process? I'm truly shocked at just how huge a pain in the rear this phone is in terms of modding. Seems I am constantly having problems with it.
Click to expand...
Click to collapse
Mine was actually a hardware issue, it was coincidental that the camera stopped working when I changed roms. Anyway, I have a refurbished phone on its way and hoping for hboot 1.4 I doubt it though.....
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Chakker3D said:
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Click to expand...
Click to collapse
You are using a leak or *beta* rom which is far from stable
And no installing many roms can not damage any hardware
Sent from my GT-I9100 using xda premium
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Chakker3D said:
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Click to expand...
Click to collapse
Having a similar, if not identical issue on latest Westcrip ROM. Near as I can tell, seems to be related to memory management: while on BT, RAM space drops almost 200Mb. While changing songs, or surfing the tracklist/phonebook, it can cause the RAM to reach a critical level. This causes the OS to crash and the phone to reboot (my case a soft reboot from the animation only) in order to create space. I would chalk this up to inefficient memory management by a beta ICS rom. Look for this to be sorted out in the future with official releases and custom kernels/roms.
Thanks for your response.
Yeah when I installed resurrection, I also ran in to that problem. I had no idea how to diagnose it. But it makes sense, bottling up the ram to the brink of reboot.
Thats what initially was happening to me, soft boot, took a few seconds and was back in. But extended crashes seemed to cause corruption.
Yeah so the XXLPH seems to have an issue. Because I also tried foxhound and got the same result.
I just got back in from testing my BT on my car stereo using my stock rom of KG2 and it played for 20 minutes and i chatted for 19 without any problems.
So I am glad it wasnt anything seriosu. But only reason I was concerned is I found nobody else to have the problem and I felt a bit isolated
But im reading the official ICS rom is out in Europe so im sure we will see some new roms out in the next little while.
Hello friends,
I recently picked up an i717 and am in the process of sorting it out. It was originally a Bell phone, though of course it's unlocked these days. I've been hacking at various Android phones for years now and have managed to work through just about everything, but this has me stumped...
I've tried almost all the 4.4 roms, and most of the 4.3 as well. I've tried various kernels/modems/combinations/etc. I've used CWM and TWRP. They all invariably lead to the phone either rebooting constantly from the "optimizing apps" dialogue, or a few times I've made it to the welcome screen, but it's always just up for a minute or two, crashes, then reboots. I haven't found a live download for 4.2 yet, so I don't know if it would work or not. 4.1 stock and Padawan run just great. I've been doing multiple full wipes before installation, flashing the rom a few times, then hitting the caches a few more times for good measure. I can't imagine my flashing technique being at issue here.
I do know that there is at least some physical damage to the phone. The capacitive buttons don't work. But it doesn't see immediately obvious to me that these would be related. Of course, I've seen stranger things. Running Padawan the phone will hum right along at max speed all day with no apparent issues, so that side of the hardware seems okay.
Sometimes CM roms will end up at the CM welcome screen and pop up a "com.android.acore has stopped" dialogue. But the constant reboots are there on every rom I've tried.
Does anybody have any ideas?
Outside of the, every once in a while you just need to go all the way back to stock just to make sure all the garbage is taken out, have you considered the infamous stuck power button?
Though I have yet to, many have experience the stuck power button. It may feel ok and you may even hear it click, but that doesnt mean anything. Give your phone a couple good flicks to the back behind the button. Though it does seem odd that it would run one rom without issue and not others, but it is worth a shot.
Again taking your phone to 100% stock every blue moon or so can be a good remedy too.
Keep us posted. We can work you through this.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
I thought about the power button issue. However, it proceeds to boot into the OS until after a time when the screen locks then reboot, which would seem too long to be the power button in any case. Regardless, a few sharp flicks didn't help much. And, of course, it runs quite happily all day long running on 4.1.
I have restored to stock JB, though admittedly not earlier than that. I guess I could try going all the way back to GB to see if that makes any difference.
In my experimentation tonight I've found that 4.2 also does not work, while I can add 4.1 non-tw roms to the working list. My best guess seems like something about one of the many under-the-hood things that changed with 4.2 doesn't get along with something about my particular phone. But, who knows.
For now I'll try rolling back to GB in Odin and see where that gets me.
I would say ICS is about as far back as you need. Recently I was having issue getting anything 4.3 and up to work or even flash. No different recoveries had effect either.
Wiped slate clean and started over from ICS, and Bob was my uncle. Everything that failed before was not an issue. Running latest 4.4 now and might I say "Orgasmic"
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Ahh, if only I were on 4.4 on my Note, life would be good Though, to be honest, I'm quite digging this thing, even at 4.1.
Last night I rolled back to GB, and had no luck. Although the Odin tar that I found apparently didn't include recovery, so that had to be flashed separately. I don't know if that might make a difference. That might be my experiment for tonight if I can find a tar that includes everything. Might be easier to find on ICS.
Just running my mind through other stuff I've thought of, I remember reading about kitkat having some issues with SD cards, so I've mostly been experimenting with the card pulled and a fresh format on the internal storage, with no real difference. Tried safe mode, no dice (not that I would expect this to make a difference on a fresh flash, but who knows lol...).
It's just such a weird thing. It boots into the OS with seemingly no issues. On occasions when I can actually get to the lock screen, everything runs fluid as can be until it freezes and reboots. Sometimes when it gets stuck at the 'optimizing' screen it'll just restart the count every boot, sometimes the number of apps to be done go down each time until there are 3-4 left which persist through each reboot.
I wonder if I could check logcat via adb before it reboots. Might be able to find some clues there.
Here's a factory firmware image of 4.1.2 to be flashed with Odin.
http://www.mediafire.com/view/g7gn29h7nu63id5
I've used this to revert many times. Install it. Run it once, then factory reset and run it for at least a few hours. If you experience issues you probably have hardware failure. If you don't have issues you can proceed with installing the latest clockwork mod recovery. Then wipe system and internal memory 3 times with recovery. Now flash the zip of your favorite kit Kat rom. Reboot and run it. Then factory reset and hopefully run it forever! If you're on a kit Kat build and experience sd card issues, there's an xposed module that might be able to help with that.
Thanks a lot, Bro. I'm downloading the image right now and will flash it then give it some time to settle in. Fingers will be crossed!
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Bassism said:
Just to give you guys an update, I flashed that stock image, ran it that way for a day, then attempted a few different 4.4 roms. Still no lock.
But thanks for the ideas so far!
I guess it's not the worst thing in the world. At least it runs 4.1 like a top.
Click to expand...
Click to collapse
Have you tried to turn on USB Debugging and run "adb logcat" to see what errors are causing the problem? If it is an optional program or hardware feature you may be able to disable it and run the newer ROMs. I know bluetooth has been an ongoing pain point for people. Which modem are you running? I know that some of the older modems do not work with the newer ROMS.
Good luck.
Brett
corrupt radio
i had the same issue, flashed 4.4.4 and ran like a charm for 1 day them the radio took a dump. downgraded and worked for another day.
imei became unknown and the no radios were able to fix this. went as far back as 2.3.6 hoping my radios would be fixed and no dice.i have tried endless for weeks to fix my phone and seems doomed.
none of the bricked threads helped and flashing stock with odin is no help. there seems to be no fix to the null imei and unknown baseband