My brother's HTC one X (international) has this problem it freezes and delays when being turned on and automatically overheats and the error it always shows according to him is "com.android.phone has stopped working" or something similar. He's not rooted and he was just copying some video files as usual and updated his phone while he was at it.
He's telling me it might be a virus? can androids get infected like that? and he also tells me the battery dies faster than usual even though he clears ram and closes application via task manager. He lives in another country and never used a forum before and we both tried getting answers from google to no avail but I did tell him to get it replaced as a last resort since he still has his warranty if we can't find a solution here. So are there any quick hotfix to this without rooting since he doesn't know how and doesn't want to? thanks in advance.
UPDATE: I went over a skype video call with him and he showed me his problems and turning on took awhile around 2 mins (stuck at HTC one X quietly brilliant logo) then after that a 5-10 sec black screen delay, when he entered his pattern password it takes awhile to go open and it stays 2-3 mins that way while it says loading. Then once he gets on his home screen his applications changed their icons to android icons (the green robot). He opened some apps like Dead Trigger and it takes awhile to load like 30-70 seconds he even tried other apps as well and it's the same result. From time to time it overheats on its own without even any apps on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
The three touch sensitive key lights turn off when the phone is locked but stay on at all other times. I think it happened when I installed ether esfile explorer or mxplayer. I've restarted the phone numerous times and tried clearing the cache and uninstalled reinstalled the programs.
Has anyone else come across this? Do I have to do a factory reset? I've only just got my phone working how I wanted it
Try using the phone in the daylight. Only comes on when not light for me.
Es file explorer is also installed on mine.
Sent from my HTC One X using XDA
As far as I know my touch sensitive keys have always stayed lit when the phone is awake. I was running the phone completely stock for around a week before I unlocked the bootloader, rooted and then flash a custom rom and kernel.
I cant say I ever noticed a difference in the behaviour of the softkeys lighting.
DAMIT!! Just did a factory reset and it was still there. then I turned the light on and now the keys have turned off. What a fool! Still annoying having them on when trying to watch a film in the dark.
Ah well can't hurt since I did my first 100% to 0% tonight. Got around 2.50mins on screen time with loads of downloading and playing on games. Hopefully it'll improve a little next charge.
Still feel stupid though!
Oh my.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In fairness I do think there is an issue with MXplayer as who want those bright lights distracting you when your watching a film. But yeah..
Hi, my phone has been periodically waking up as seen in the screenshots below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've gone through all of my installed apps and made sure that they arent refreshing, etc. at any frequent period (facebook and android weather were the biggest abusers, but I turned refresh off and to 6hrs respectively). I cant find any other apps that would be waking the device up, but its still being woken up about every 7 min. Any suggestions?
Thanks!
I seem to be having the same problem since the jelly bean update At first I though it was the steam app the one awaking the phone, but it doesn´t seem to be the case. Right now I´m blaming Google Now as I see no other suspects, but I´m not really convinced... It looks like it only happens when I have data connection or wifi on. If I disable all data, the problem seems to dissapear.
Jp1138 said:
I seem to be having the same problem since the jelly bean update At first I though it was the steam app the one awaking the phone, but it doesn´t seem to be the case. Right now I´m blaming Google Now as I see no other suspects, but I´m not really convinced... It looks like it only happens when I have data connection or wifi on. If I disable all data, the problem seems to dissapear.
Click to expand...
Click to collapse
Ok so I just realized that Tapatalk was set to check for updates every 30 min. I changed that to 12 hrs, but that still doesnt explain the rate of awakes that I was seeing. Could it be google sync? I thought there used to be a place to set the sync interval, but I cant seem to find it in JB...
use better battery stats to look at what's keeping the phone awake
hi there, i need helppppppppp
problem:
everything crashes inc launcher...
so now it loops to the launcher selection screen.
the background apps etc is still working it seems.
but when i actually go into any apps that i can go, it crashes and loops.
i can still take screenshot.. wtf but nothing else work!! HELPP
restart/battery pulled
phone load up fine
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
unlocked and it become
choose any of the launcher, even touchwiz, it just crashes and loops back.
i can go into settngs by swipe top to bottom but it crashes at the settings screens and loops back as well
i can even hold the middle button and go the opened app/google seach etc
but same same crashes and loops back
possible cause?:
before this happened-
i was changing the ime settings for input, marking around the one-handed operational options.
WHAT CAN I DO?
any way to load the phone into a 'safe mode'
i have a feeling is the ime input crash, so if i m able to go into SETTINGS (without crash) then i maybe able to change/disable
phone is rooted so i went to the trouble to get CWM on it, and tried
wipe cache/date/factory reset all
and when the fone booted up, it says the 'setup wizard has stoped working'..
so it seems the crash point is still there... ><
next i'll try installing a custom rom over it and see what happens..
i hope this is not SDS....
anyone help?
i installed one of the latest rom over it and finally it works!
so it seems that for some reason my original (stock) rom got corrupted and caused all the crash... anyway now i m back!
Ready to go back to @??/€..... hate that but im sick of this battery drain randomly
Ive found a few things to be consistent maybe others can chime in.
With google services. Its not always bad. Recently had everything on and no issues. Including gps, Google now, location services etc.
I have found out to last more than a work day. Come home with 45-50%
But today..... Phone just restarted randomly, not the first time either. Usually there is an update for something and the phone restarts to update an app or whatever.
Today, just restart. Then 40 min to 1 hour later. Phone is getting HOT, I look and I had gone from 70% batt to 56 in minutes. Then to 40 then 15 and all the way to 2%
I wanted it to shut down on its own and restart it with a charge but, I had to drive home and car isnt 100% reliable and I didnt have a car charger. So I plugged it into pc to get a few % up.
Google plus went rogue I guess. As you'll see below. But why? And why doesn't @??/€ have this problem?
I just want the phone to last a full day. I dont even use it at work hardly at all with the exception of a bit of tapatalk and facebook......
Screen shots below for help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Galaxy s4 on Tapatalk
Not to state the obvious, but have you considered freezing or uninstalling Google Plus?
Also, check out the link in my signature about keeping Google Services in check.
I forgot to mention that I'm on 4.2 .2 . In addition I didn't do anything to the song, I did not force stop loss, nothing. And everything is back to normal today
Galaxy s4 on Tapatalk
tapatalk.imageshackDOTcom/v2/14/09/22/b0efbd80892cab999fae6154fbd7e6c4.jpg
It was perfectly fine for a day and a half until I put it back on the charger for about one hour and then the screen was like that. Tried fixing it by resetting and restarting and turning it off overnight. Still like this.
I'd like to note that it was fixed when I changed to the convergence watch face for about 5 minutes after shutting it off for about an hour but it came back in 5 minutes. I feel like there is a solution if it managed to fix itself even if only for 5 minutes. Has anyone had this problem.
I did contact Motorola and had my case escalated so another question is if this does need to be replaced, how long does it take.
Same issue
I too am seeing the same thing on my silver 360. It just started out of the blue about thirty minutes ago. I have tried resetting charging and erasing. I'm still having the issue. I will most likely contact motorola ASAP.
I would say that either the screen is faulty or there's an issue with the SoC.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh my that's horrible... so what apps did you install, etc?
v3ngence said:
Oh my that's horrible... so what apps did you install, etc?
Click to expand...
Click to collapse
Nothing out of the ordinary, just watch faces really. I'm so lost because when I got home today, I managed to fix the problem by deleting the android wear apps on my phone. It was 1 o'clock now it's 9 o'clock and it somehow has come back. ;( I don't know why! And I can't fix it this time
It's definitely a hardware issue (bad memory I think) and software could avoid it if it knows where the bad memory is, but it's hard to know how much memory would be left. If there's not enough good memory then it would be forced to use bad space...
Sadly I think it needs to be "refurbished"