i just got the phone and it cant stay on a minute. i flashed it to 6.0.1 and just when the optimization reaches 80%, crash and reboot. it somehow passed the optimization by 15 apps and booted to crash at the 'unlock loading thing'. downgraded it to 5.1.1, now it cant even pass the 'android is starting...' page because its too slow. is it hardware? i wanna cover the software side first. it keeps rebooting after being on for few minutes. suggestions, rather than the 'reset it'?
Related
I've got a huge problem with my Desire HD that just drives me crazy and still I don't know what to do about it - googled for hours, haven't found anything but unfinished threads.
It started a while ago, I had a ICS - Aokp installed. Some day, WiFi turned off and when I tried to turn it back on, it either remained in the "Turning WiFi on..."-state or gave me an "WiFi Error". Also, the whole OS slowed down terrible.
I installed a 2.3.7 Sense ROM. Worked for a few days, I think. Then one time, the phone froze and after reboot, the WiFi Error occured again.
Switched to Virtuous Infinity v1.31.0. Worked fine for maybe a day, froze, same error. And worst of all, it slew down more than before. Example: Unlocking Screen -> (3 Seconds) -> Displays GUI -> Whatsapp Link -> 10+ Seconds -> displays WhatsApp - but that's not even the end, try to enter text when it displays 1 sign per second. You finish typing, wait 15 seconds to hit the "send"-button.
2 hours ago i installed JellyBean (4.1.1). Without it freezing, WiFi just turned off an won't turn on again. I rebooted, while bootanimation, it froze. I took out the battery, rebooted - it doesn't run as smooth as it did before and WiFi still won't work again. I think in the next 14 days it will slow down again like it did before. It's like there would be processes in the background that need the entire CPU power, but anyway i monitored CPU usage using SystemPanel. There was no CPU usage recorded. I killed apps, no difference. I also intended to monitor the CPU speed, but it wasn't possible with the previous kernel.
Do you have any suggestions, what i could do? Right now, i just want to smash my phone.. it's not dependable. Sometimes my phone rings but won't turn on the screen cause of the stability problems .. I am through so many Android versions, I'm just tired of installing new roms every 2 weeks so i can still use my phone.
Hello all,
Let me start off the message by mentioning that I have been a (altogether) very happy user of cyanogen mods with my last 3 android phones.
The last and current (but it seems not for long) is an HTC One X, which is over 2 years old.
This poor thing has gone through so many ROMs that I have lost count.
It is currently running on a stable cm10.2.1, upgraded from cm10.1.3.
I have experienced sudden power offs when there were obvious battery drain, battery overheat, weird app installation issues, especially since moving to cm 10.2.1, which also caused the GPS to stop getting any satellite signals.
However, the phone has recently (a couple of weeks) leveled up into a bizarre mode:
It will power off all of a sudden, the battery levels are not low 65-75%, so I would assume it was just some process in the background, and go ahead and start the phone up again to go and check through the logs, or even disable/cleanup dodgy overreacting apps. But to my surprise, the phone passes the quietly brilliant screen, as well as the CM logo with the circling arrow and as soon as you can see the background it shows Powering off - the phone is shutting down.
For those brief couple of seconds I can see the battery indicator (top right corner) showing a small part of it in red, letting me believe the battery's status is critically low. So I let the phone charge for half an hour, and start it up again, with the same result, once the device goes past the logo and the background shows, the Powering off message appears again. The battery indicator is still showing a small red circulating section of the whole.
The next step was to go and check in recovery mode. The battery on the TWRP screen shows almost 70%, and this leads me to assume there is something wrong with the battery. But the phone is not turning off for as long as in recovery mode. I still haven't ruled out the battery issue, and will test it when I get delivered and replace the spare one I have ordered.
Reading through forums and other threads, there were people complaining that they had the same issues when the phone was trying to change from 2G to 3G and the other way around, so I removed the sim card and have restarted the phone, still the same result, powering off after boot.
I also reflashed 10.2.1 thinking that a clean installation will help getting rid of some new app/processes that might be causing this, but exactly the same powering off occurs after booting. The same happens even after a factory reset.
Usually, after half an hour of inactivity the phone would start up normally, but today it has been several hours and the behavior is not improving.
At this point I can't get into the phone other than on recovery, I can't copy from/into its storage anything, not even the nandroid backups I regularly do (and which stupidly I haven't copied over to an external storage). I could try reflashing some stock image, but even that I don't have on the internal storage.
So as you see, I am bit stuck. Phone will not stay ON long enough for me to connect to my machine and save my backups, or load any new stuff.
If you have any other suggestions other than this, or perhaps a workaround to what I have already tried, I would extremely appreciate it.
Cheers,
Mad
I have the same problem..
I have tried everything, but nothing helped me.
Now my battery is 0% and i cant do nothing - cant charge it, cant boot in bootloader.
Something heppened when you changed the bettery?
I upgraded my note 2 to 4.4.2 KitKat. I discovered a mysterious behaviour. Whenever I try to shutdown the mobile phone, it just restarts. Have tried this 6 times but it restarts. Also, battery shows weird percentages.
On 1 occasion it showed 20% charging. Immediately on restart it showed 56%. I am amazed. Can't get my head around it.
Kindly help.
Completely stock T-Mo m8. Been running Lollipop since the OTA came through, and it has worked fine for the longest time, no problems other than a bit of lag, even after clearing the cache.
A couple of days ago, the phone began to shut down whenever (seemingly) any app was launched when on battery, and then would not boot on repeated attempts. It doesn't seem to make it past the first stage of the bootloader (first HTC screen, pre-animation), most of the time. Sometimes it will make it to the T-Mobile animation and then give up.
While plugged in, it boots and works fine 9/10 times, but sometimes gives some resistance to booting. If it is unplugged and any apps are launched, it shuts down as if the battery were removed. Though, the whole while the battery seems normal, no weird fluctuations or sudden drops in battery level.
If it is unplugged after having booted and it is relatively inactive (no apps launched, or any processes, i.e. alarms, syncing, downloads, etc.), it will remain powered on.
I have attempted to Factory Reset a couple of times, and cleared the cache a couple of times. The problem persists. I can boot into recovery, though I am not rooted.
Is my battery in need of a replacement or some such? I would like to remain fully stock if at all possible. I may be able to get a replacement phone out of T-Mobile, but would also like to avoid that.
I have been using fulmics for a long time now. I live somewhere where the temperature is always something around 17-25 degrees on summer and never had an overheating problem. Now, I'm on holiday somewhere hotter (canary islands) and the 30-ish temperatures are causing my phone to reboot if i take a couple of pictures or if I open apps like pokemon go. I think this has something g to do with heat because back at the hotel, I don't have these issues at all. Even when i perform the same tasks at night, the phone does not reboot.
Now, I can't remember if I chose the stock or the the thermal throttle values upon installation but I'd like to ask, which would be the best option to avoid this issue and also, any other advice you could give in order to mitigate this issue. I asked on the fulmics thread over at xda but the mods locked it because some asshole didn't stop asking the dev for Etas. Screw that guy.
Any help would be welcome! Thanks!
Hi, there will probably be an update to fulmics 6.0 which should solve overheating problems. I'd recommend for you to move to Cloudy G3 2.5 or XenonHD with aCC kernel just for now.
I also have problems with heating. When the phone is at direct sunlight for some time it become irresponsible. I mean it don't reboot but message pop up "system ui stopped ....." and screen lock. I wonder if fulmics ROM is the reason for that. As far as I remember upon installation I choose stock settings, kernel.
Update! : This morning, I went out and the phone got literally unusable. Constant bootloops. Sometimes getting to see the wallpaper but after a couple of seconds, before the whole system boots, rebooting again. The temperature today is quite lower than the previous days and the phone sure didn't feel that hot on the back (power button is my thermometer). Back at the hotel, I tried to backup in order to wipe data and see if it's a data corruption issue. I had to try a couple of times to backup because the phone would reboot half way. I finally made it to the point where I reinstall the rom, before wiping, and the phone would reboot while fulmics was getting installed. I then remembered reading somewhere about the possibility of being a fubar battery, so I plugged the thing to the wall: instant fix. No more reboots. I even restored the backup without any reboots. Booted the rom perfectly. Let it load. Open pokemon go, see it works. Unplug from the wall and in less than twenty seconds: reboot.
Now, I'm on twrp without performing any task and saw my phone lose 30% of the battery in 45 minutes just sitting still. So yes, my bet is on a broken battery.
Whaddayathink?
My G2 acted like this when the battery died. Its a sure sign
GFXi0N said:
Update! : This morning, I went out and the phone got literally unusable. Constant bootloops. Sometimes getting to see the wallpaper but after a couple of seconds, before the whole system boots, rebooting again. The temperature today is quite lower than the previous days and the phone sure didn't feel that hot on the back (power button is my thermometer). Back at the hotel, I tried to backup in order to wipe data and see if it's a data corruption issue. I had to try a couple of times to backup because the phone would reboot half way. I finally made it to the point where I reinstall the rom, before wiping, and the phone would reboot while fulmics was getting installed. I then remembered reading somewhere about the possibility of being a fubar battery, so I plugged the thing to the wall: instant fix. No more reboots. I even restored the backup without any reboots. Booted the rom perfectly. Let it load. Open pokemon go, see it works. Unplug from the wall and in less than twenty seconds: reboot.
Now, I'm on twrp without performing any task and saw my phone lose 30% of the battery in 45 minutes just sitting still. So yes, my bet is on a broken battery.
Whaddayathink?
Click to expand...
Click to collapse