I'm not sure if it is because this phone is second hand or if there is a software issue inside this Android flash, but when I bought the phone it was on stock Android 2.2.1 and had been factory reset as expected. However after using the phones features for half a day or so things started deteriorating (for example the settings app force closed), to combat this I did another factory reset and again things were still force closing, so I did yet another. Everything from this seems fine except now if I'm playing music through the stock player it appears after so long it force closes and won't work until the phone is restarted. When I get home I'll be flashing CM7 but I'm wondering what the problem could be. Any ideas?
Sent from my HTC Wildfire
Related
Hi everyone,
both my wife and I own a HTC Desire (AMOLED). My wife has had the following problem for a while on her unrooted, stock-ROM Desire:
Every now and then the Handy will suddenly restart (show the HTC boot logo) when using Navigation apps. No matter if Google Maps Navigation or other navigation software. Sometimes, this happens after some seconds, sometimes after an hour or so.
No problems so far with my desire.
Last month, I rooted/s-off'ed both devices, did a full wipe and complete fresh install of all apps of both devices, both running on InsertCoin 1.1.4 now.
On this occasion, I also updated Radio ROM of both phones to 32.56.00.32U_5.17.05.23 (latest Version so far, I think).
Some days later, my phone now also randomly crashes on GPS navigation use. Both run stable, as long as we do not use GPS navigation.
Any ideas on how to fix this?
It's usually an overheating issue that needs HTC to swap the mainboard
Sent from my HTC Desire using XDA App
Thanks for your reply, though it's sure not what I wanted to hear (actually, what I wanted to hear is something like "push this button and your problem will be solved", but it's not what I expected .
(On overheating: The phone did never crash on other occasions when becoming warm. After a reboot, when restarting navigation, it does not crash again immediately but may work for hours...not too typical for an overheating problem, is it?)
I think I'll wait 'till spring 2012 and get some Ice Cream Sandwich thing then ;-)
You know the desire has a 2 year warranty though, right??
I RMA'd my first GNex last August with a cracked screen, the one I got back had some problems:
Camera App crashes. Sometimes on startup, other times after a few seconds, and occasionally it doesn't crash until after I've been able to take a full photosphere, but usually the first two. It shows force close screen.
Netflix crashes after a few seconds to a few minutes. It does not show a force close screen, it just restarts the app.
Youtube won't load videos and when it does, it gives an error after a few seconds or minutes.
All flashlight/torch apps crash either on startup or after a few seconds.
I got tired of this, and didn't want to deal with Verizon's ****ty RMA service again, and since it seemed like it could be a software problem, I chose to root it and try to fix it with a custom ROM. I flashed CM9 and the problem persisted. Thinking it was too late to go back, I've just dealt with it until like a week ago.
Then I heard that a 4.2 update was coming to the VZW GNex, and returned to stock using this method (Would hyperlink, but don't have post count. It's the first result when you google, "Return to Factory State (Unroot and Relock) site:rootzwiki.com" without quotes. I flashed the JB files). Shockingly, the camera, Netflix, YouTube, and flashlight apps worked. However, when the 4.2 update came along, it broke everything again.
So that brings me to my questions:
Does anyone know of any way to fix this? Preferably without rerooting, but I'm still up for that if necessary.
Would I still be under warranty if I followed the linked method for unrooting?
EDIT: I'd also like to add that music playback is interrupted when either the camera or the flashlight app crashes.
go back to stock manually using this thread
Uelmm fuppofed
samersh72 said:
go back to stock manually using this thread
Click to expand...
Click to collapse
I'm already stock...
To reiterate: About a week ago I unrooted and flashed a stock 4.1 rom that fixed everything. When I got the OTA update to 4.2 everything broke again.
I also just did this, and it worked for a minute or so, but the apps are back to crashing now.
Good day,
I have unpleasant problem at my I9190. Every 5-7 minutes my device becomes to lag for 4-5 seconds. It doesn't matter if you watch a film or Youtube, play games, or just work with the interface. Every time periodically an image becomes to lag, but sound continues to work without problem. I tried to make wipes but it doesn't help. Also I tried to reinstall stock rom. Can somebody describe what is the reason of it? Root or what?
My previous I9190 (was changed because of the problems with screen) works without these glitches.
Appreciate if you will help me, these lags are really annoying.
Sounds like some hardware is causing those intermittent freezes. If you are certain reverting to stock everything and flashing in custom ROM + kernel still causes the issue then you might need to send the device in again.
I tried to flash CyanogenMod for interest and lags dissapear. After returning to stock they appeared again. Can't understand the reason, really. I tried to use smartphone with and without sim, with and without external card, with and without root, the result is the same. The only thing I can think that one of stock apps or processes makes these problems but who knows..
I'm using an HTC Sensation, and have been for about 2 years, when I got the phone I initially rommed Revolution on it, and have run into some issues with a few updates on apps etc due to it. It occasionally crashes if the Camera app is left open, or any other app that utilizes the camera. Recently I've been trying to get some new software on it, but even with factory resets and complete wipes in rom installs, I get infinite bootloops and can't figure out why. If I could get some assistance with this, that would be amazing..
Have you updated to the latest firmware ... 3.33...
I am currently running the latest build of the PacMan rom for my Sprint S3, but my problem didnt start there. As over the course of a few weeks my phone has been randomly crashing while running build 7 of Slimkat. It started crashing when i wanted to take a picture with the AOSP camera (when i hit the camera button and then it would shut off). Then it progressed to just crashing trying to use accuweather, or even when the screen was auto-rotating in my SMS app. So finally i just backed up my important bits and made a clean wipe into Wicked X 8.0 TW rom (because i'm on Ting and TW roms initially work on their network and wanted to export, or to just copy down the settings of, the APN xml to use in AOSP roms). After playing around with that for 20 minutes, i didn't experience any fc's or reboots. Though i did not use the camera in that time (i forgot to check). To which i then wiped it into PacMan rom that im at now. Which at the moment seems fine to do everything, except it will shut off if i want to OPEN the camera (doesn't let me use it at all). Plus i did have it crash once rotating with the play store up...
So im kinda lost, i wonder if this is just an issue with the camera in the rom, or if it might be a bigger issue with the phone itself. As ive been having the same random error's with two roms and i dont see anyone having FC's with pacman rom with the camera.
more testing done
So i have also attempted to odin completely back to stock and i have a stock rooted rom with nothing touched. The sudden shut-offs still happen and occur randomly. I installed logcat and what seems to be throwing error's is the accelerometer. Plus at first when i flash a new rom it seems to work ok with no problems for the first day, then suddenly start showing symptoms the next. Plus ive had it shut off during bootup too while going through the sprint 4g animation screen. Though i have not had it die on me in recovery, so thats a thing.... Plus it will rotate no problem half the time, and then ive seen it die rotating to use my keyboard.
So at this point i feel like its actually a hardware option. If it is the accelerometer, is it easy to fix (i guess re solder the connections if they're broke?)? or should i just try and replace the main board?