bought a HERO a month ago.
Initially things were fine, but then the phone has developed a lot of lag.
When I tap the PHONE button at the bottom of the home screen, it takes almost 3-4 seconds before the keypad comes up.
When I click on an Email account, it takes up to 5 seconds for the email list to load, and an equal amount of time before a tapped email opens up.
All this used to happen in less than a second earlier. I have not installed any apps from the market which are running at any time, and even loading up the phone in safe mode has not made a difference.
Also, the trackball is not being very responsive. It takes a good amount of pressing it before moving it around for the trackball to work. Is the trackball supposed to not do anything if moved very lightly, or if i just brush it softly with my finger and it moves, but nothing happens on the screen? It works only if there is significant pressure on the trackball.
htc has a stock answer for everything "HARD RESET". i don't even know if there is a way to backup all the data including contacts, messages etc and then put them back again after a hard reset.
I wonder if the phone is defective in some way?
Just flash a new ROM. Also, I know many people will disagree with me, but get TasKiller (the one by Thibaut Nicholas), as kill all the tasks. When the phone starts functioning again, go to TasKiller and ignore all the tasks that start up first (should be the bare minimum ones), and then turn on Auto-Taskkill. This way when you put the phone to sleep, all the running tasks except for the necessary ones will be killed. I've found this keeps my phone very fast
Related
Ok so I want to convey all the relevant information without this being a mile long.
I have a o2 UK SGS2 running on a 3 sim. I have flashed on Lite'ing 6.1 with ninphetmaine 2.0.5. Up until the following, everything has been 100%.
This morning I downloaded Destinia and played it for a while. Before quitting I took a quick look at in app purchases to see if they charge ridiculous prices (they do). I'm not interested so I quickly spam back to close everything. This is when **** ****s up. OS becomes unresponsive immediately and I have no choice but to pull the battery. (power menu disappears instantly, no registered actions from soft keys or menu button in OS). No change on reboot.
I try reflashing Lite'ning. Mostly no change but I got the chance to get into task manager and uninstall Destinia/Launcher Pro.
I reinstall launcher pro, and now it works most of the time except:
1. Quite frequently the voice action app will load itself, and the unlock notification will pop up.
2. MTP notification will appear occasionally and phone will act like it's plugged in
3. Random Launcher/OS crashes. Sometimes screen on but no response from apps or OS. Sometimes screen won't turn on at all, just softkeys and darkness.
4. at first unlock after boot, camera makes standard focusing sound.
5. on boot, little popup dialog will read "in app purchases not supported in this version of android".
Really I doubt there's going to be any solution other than "wipe and reflash" but I'm really interested if anyone knows what would cause all these problems.
Cheers
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
JJEgan said:
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
Click to expand...
Click to collapse
what this means is that pressed back from the game's in app purchases screen, back to the main menu and then back to the Launcher, I'm sure everyone has done basically this countless times.
Fine but my dictionary defines spam as a different meaning .
But as posted that's where it all went wrong for whatever reason .
jje
Right I wipe-flashed stock 2.3.5 and it's STILL doing this. Voice actions popping up at random, all sorts of apps crashing and hanging all the time.
This has to be a hardware problem now, right?
just a stab in the dark but run a virus check.
I've never had a virus in my life, but I checked anyway and nothing.
Right so I've been watching my phone today. It's still doing random voice action popups. If I leave the phone on standard standby it will be fine for a while. It will then randomly turn on the screen by itself. The screen will stay on, if i leave it long enough the whole thing become totally unresponsive. If I press power the phone will wait a few seconds, then restart. If I don't touch it, it will just restart on its own eventually.
Can anyone recommend at least, some logging software that will let me look at the underlying OS and see what's happening when this is going on.
Is there any possibility your phone also goes to car-mode by itself?
spare parts app??
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Im getting random voice talk and mtp etc. phone is all ovr the place. flashed litening and nimphet last week and seemed fine. used mhl hdmi cable and problems seemed to start from there.
millia90 said:
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Click to expand...
Click to collapse
Read your thread http://forum.xda-developers.com/showthread.php?t=1278790 and your problems are down to the letter the same. I've resigned myself to it being a hardware fault and put in a service request with samsung. Wish I had better news.
Yea me too. My issue is that my SGSII was manufactured in UK so I'm at odds seeing as how I'm in America. The people at the Samsung call center referred me to the UK number so I guess I will have to bits the bullet.
My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
bvz2000 said:
My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
Click to expand...
Click to collapse
So several days have passed, and it appears to still be working. I suspect the sd card was the culprit. No idea why. But I am a happy camper again.
Apologies in advance for the potentially vague description, but I also cannot find a solution elsewhere on the forum.
Earlier today, I was watching a YouTube video and then I locked my phone and left it to charge whilst I went downstairs (as I often do). When I returned roughly an hour later, I found the screen on, which I only ever do if I've left Draw Something open, or some similar app - but it was on the lock screen.
(none of that is necessarily important, I just wanted to clear up the "what did you do to make it start rebooting" question)
Anyway, after unlocking the phone, the screen went to black and the phone restarted.
However, it wasn't a "real" reboot, because the boot screen didn't come up, etc. It's just like just the UI is restarted. I can usually use the phone for about 30 seconds at a time. This seems extended when I have flight mode on, and is even longer still when I have the phone locked.
I've uninstalled some potentially-offending apps, removed the SD card, cleared some apps' data, but to no avail.
I'm using default 4.0.4 from Samsung. The only issues I'd had with it until now were that some apps crashed occasionally, but I attributed that mainly to the apps themselves.
The most annoying thing for me is that is seems like it's an issue that can be fixed quite simply, without having to uninstall every app or factory reset the phone.
Anyone have any other ideas as to what I could do? Thanks!
RobHannay said:
Apologies in advance for the potentially vague description, but I also cannot find a solution elsewhere on the forum.
Earlier today, I was watching a YouTube video and then I locked my phone and left it to charge whilst I went downstairs (as I often do). When I returned roughly an hour later, I found the screen on, which I only ever do if I've left Draw Something open, or some similar app - but it was on the lock screen.
(none of that is necessarily important, I just wanted to clear up the "what did you do to make it start rebooting" question)
Anyway, after unlocking the phone, the screen went to black and the phone restarted.
However, it wasn't a "real" reboot, because the boot screen didn't come up, etc. It's just like just the UI is restarted. I can usually use the phone for about 30 seconds at a time. This seems extended when I have flight mode on, and is even longer still when I have the phone locked.
I've uninstalled some potentially-offending apps, removed the SD card, cleared some apps' data, but to no avail.
I'm using default 4.0.4 from Samsung. The only issues I'd had with it until now were that some apps crashed occasionally, but I attributed that mainly to the apps themselves.
The most annoying thing for me is that is seems like it's an issue that can be fixed quite simply, without having to uninstall every app or factory reset the phone.
Anyone have any other ideas as to what I could do? Thanks!
Click to expand...
Click to collapse
just go to recovery mode and fix permissions
Hello all, I've noticed that my S3 gets considerably slow after a few days of not shutting it down. For example, after a reset, tapping home will immediately take me to the launcher, everything reacts immediately, there's absolutely no lag, however, after about 2 or 3 days, things start getting slow, the launcher needs to reload everything whenever I press home, apps don't seem to stay in the memory and have to reload as well. Like I mentioned, restarting the phone fixes everything, and I was even thinking of setting up a Tasker action to restart the phone ad midnight or so every one or two days, but I wanted to know if this could be because of a single app that's being faulty, or normal behavior. Any and all replies are appreciated!
ivikd said:
Hello all, I've noticed that my S3 gets considerably slow after a few days of not shutting it down. For example, after a reset, tapping home will immediately take me to the launcher, everything reacts immediately, there's absolutely no lag, however, after about 2 or 3 days, things start getting slow, the launcher needs to reload everything whenever I press home, apps don't seem to stay in the memory and have to reload as well. Like I mentioned, restarting the phone fixes everything, and I was even thinking of setting up a Tasker action to restart the phone ad midnight or so every one or two days, but I wanted to know if this could be because of a single app that's being faulty, or normal behavior. Any and all replies are appreciated!
Click to expand...
Click to collapse
thats normal behaviour on most android phones, unless u have 2gb of ram(still happens but takes longer)
its better if you reboot at least once a day
Sent from my GT-I9300 using xda premium
I have a Xiaomi Redmi Note 4X, which I started using around March. Lately, I have been facing an issue which has left me troubled a lot. My Note 4X seems to be in a bootloop.
Around two weeks ago, I was casually using my phone in college. I had put around 25 apps on download from Google playstore. Alongside, whatsapp was running. I usually take pics of my lectures, so when the teacher had written on the board, and was about to erase, I quickly attempted to go to the home screen, by clicking the home button ( middle button), so I could launch the camera app, and take the pic. But, the phone didn't go to the home screen, and stayed at the app being used. However clicking on the recent apps (the left button), the two running apps showed. However, as I didn't have much time, I did what came in my mind. Reboot the phone. Unfortunately, as soon as it booted back, the screen remained black.
Its been like this for two weeks now. Whenever I turn it on, It will show the Mi logo, then the Android logo simultaneously below it ( Like usual when it boots), but after that, the screen goes black. Touching the three buttons at the bottom of the phone make the back-lit underneath light up along with a vibration(Like usual). Clicking the touchscreen gives a vibration. If a sim card is put inside, and a call made to the inserted sim card's phone number, the phone starts ringing as usual, however, still with a black screen. Another major issue I experience other than the black screen, is that the top right of the phone becomes really really hot as time progresses( within minutes)(This never happened before), and the battery drains really fast too. I get freaked out because of this( I think it might explode or catch fire), so I quickly turn off the device, after some tinkering.
I have been trying to find a solution since the past two weeks. Hard pressing the Volume Up+ Start button takes me into MiRecovery 3.0, which offers 3 options, 1.Reboot, 2. Wipe Data, 3. Connect To MiSuite. Going into 2 gives the option " Wipe All data" only, and 3 is seemingly useless the MiSuite doesn't support new versions of Android. Hard pressing the Volume Down+Start button takes me to FastBoot. It should be noted, that in both MiRecovery 3.0, and Fastboot, the phone doesn't warm up really fast, as it does when booted normally, and rather remains cool even if left for quite sometime in these modes (approx 30 minutes atleast).
The main thing I'm trying to achieve is to backup the data on my phone, mainly the photos (lecture notes), and whatsapp data. The rest of the app-data isn't that much important, albeit if also savable, it would be a bonus.
I haven't tried flashing any ROMs, recovery, or anything else, as I'm afraid the data may be erased, and as I have never done anything like this before. Also, my phone isn't rooted, as I didn't feel the need for it to be.
Help is highly appreciated. I hope to be able to safely extract my data, and be able to start using my phone again.
Thanks to advance to all those who reply.
Guys?