Related
So basically, my hd2 is not running smooth at all. Every time i do a rom update and then restore my contacts/messages/settings it keeps getting frozen and unresponsive. So I have to restart the device, but I don't know why it should be restarted anyway, isn't is kind of super fast?!?! So, now, when I recently updated my ROM, the device is so damn slow, that even after typing my PIN it takes a minute to launch htc sense and everything. When I'm moving through the tabs it's so damn laggy i can't stand it. . Is anyone else experiencing this????
To be honest, and I'm no expert, it sounds like you have some serious phone problems, probably out of your control. Not to sound like a pessimist but given how everyone else seems to be ok with the HD2, could be either a major rom/radio problem or hardware failure??
I've updated my hd2 using the official rom from HTC and, apart from the occasional lag i get from WinMo, my device runs sweet as a a proverbial nut. Especially as I have run the tweaks suggested by the forums here.
Given that you have said that you've upgraded the ROM and it's made no difference, the only thing i could suggest is possibly send it back under warranty?
Obviously, I'd wait and see if someone with more know-how has a better explanation, i'm merely giving you my POV.
Hope you get this sorted ASAP. A properly working HD2 is a marvellous thing.
All the best
To the OP,
There could be so many causes for your problems. I would start as follows:
- Take your SD card out and see if the phone boots and is not laggy with the card out
- If this does not work take a look at the SMS threads on here and see if the solutions there help you
- If no joy then read the Hints @ Tips thread on here, if you have not already done so, and pickup on the cache move tips, using the task manager to close open files, etc
- I that fails look for the thread "HD2 Died - or did it" and implement the solutions in there
- If that does not help and you have been flashing a fair few roms then hop over to the MTTY thread in rom development and see if that helps.
Plenty to be getting on with.
Hope you get it sorted.
WB
My power up to sense loaded time = 55 secs.
Any different?
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
[^IcEmAn^] said:
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
Click to expand...
Click to collapse
I have experienced question 1 and 2.. however not alot or not frequent.. I tend to think that this is just a computer and computers do crash depending on whats going on.. The missed screen taps only happens once or twice when its playing up. I do have a screen protector on though so whether the dust, oil or screen protector is causing that is a different story, but isnt a big problem for me to remove the screen protector to find out.
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time). As said before, I'm using energy rom, latest issue (17.2.). Could the problem be, in fact connected with this rom or specifically with sms software?
using cooked roms you can generally expect a few lockups and restarts.
Also, the screen not powering up, just the hard keys backlight is an issue across the board, from custom roms to official roms. Some roms seem to do it, some don't, but one that doesn't do it to me might well do it to you.
[^IcEmAn^] said:
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time).
Click to expand...
Click to collapse
It has been mentioned before that if you have a large number of texts stored, it will take a while for it to allow you to reply to a text. (It has to go through the database, check for the texts sent by the user, then arrange them alongside the ones sent to them by you, then put them in chronological order, then display them, this takes time)
but i would presume the device should be working anyway (but slower, of course) and not flashing the display and being "frozen" ?
The frozen issue with texts is all in the SMS thread I pointed you to earlier. Solutions to the phone freezing are in the HD2 Died thread, again as I pointed out earlier.
How many of these potential solutions have you tried? Tryy these things first then come back if they don't work rather than make assumptions about your ROM.
WB
after 3 months i still have the issue with missed strokes.. even after the latest energy rom update :\
anyone?
Hi,
My Nexus 7 2012 (very first batch) is quite often behaving really slowly. It is common for the settings screen to take 15-20 seconds to open. From the homescreen. With no running app.
Here is a video after I've reset everything to factory defaults, let it run and index things on its own for an hour and then manually upgrade a small app:
At other times, the speed is pretty decent for such a tablet. I just can't figure out why this difference. I've tried to check for wakelocks, tried a logcat and many other things. I can't make any sense from it.
Rebooting the tablet seems to have 50% chance of fixing the problem. So it's probably not a memory leak.
The tablet is rooted, on the latest build and I noticed that App Ops X survived the reset but no funky software is installed and the behaviour predates the installation of App Ops X. The network is not a problem here. The 2013 Nexus 7 of my wife works just fine and so does the Nexus 5 taking the above video.
How can I investigate this ? Is there an app that can run various reliable diagnostics to find out what kind of activity is causing trouble ? I tried to use logcat but the result is quite verbose and nothing rings a bell. I would really like to understand rather than just return it and wait or, worse, buy a new device.
Thanks.
Let me know if you find a solution my Nexus 7 has been really slow, Im rooted with CM11 M6 & KK GAPPS, TWRP 2.7.0.0 I dont know what happened to this tablet.
edarchis said:
Hi,
My Nexus 7 2012 (very first batch) is quite often behaving really slowly. It is common for the settings screen to take 15-20 seconds to open. From the homescreen. With no running app.
At other times, the speed is pretty decent for such a tablet. I just can't figure out why this difference. I've tried to check for wakelocks, tried a logcat and many other things. I can't make any sense from it.
Rebooting the tablet seems to have 50% chance of fixing the problem. So it's probably not a memory leak.
The tablet is rooted, on the latest build and I noticed that App Ops X survived the reset but no funky software is installed and the behaviour predates the installation of App Ops X. The network is not a problem here. The 2013 Nexus 7 of my wife works just fine and so does the Nexus 5 taking the above video.
How can I investigate this ? Is there an app that can run various reliable diagnostics to find out what kind of activity is causing trouble ? I tried to use logcat but the result is quite verbose and nothing rings a bell. I would really like to understand rather than just return it and wait or, worse, buy a new device.
Thanks.
Click to expand...
Click to collapse
droid4lif3 said:
Let me know if you find a solution my Nexus 7 has been really slow, Im rooted with CM11 M6 & KK GAPPS, TWRP 2.7.0.0 I dont know what happened to this tablet.
Click to expand...
Click to collapse
Mine too. Nexus 7 2012 16GB running PA 3.99 (JB4.3). PA Kernel and GAPPS, PA launcher or whatever one came with stock PA.
It takes upwards of 10 seconds to unlock frequently, even from a fresh boot, and without any security just a simple swipe unlock.
App drawer can take 10-15 seconds to open.
If I touch too much during these lag times I will often get a launcher not responding error.
I've about given up myself and am looking at other ROMs. Before I reflash though I may try a different kernel.
I'm downloading a few right now and I'll hopefully remember to report back my results.
Mine is suddenly unbearably slow too. It's a 2012 edition and I'm not rooted, running the stock software. I've tried clearing caches (app and system), doing a factory reset, flashing the factory image, but it just runs like a dog. When I switch it on it takes a few minutes to become responsive, and apps regularly say they will take upwards of 20 minutes to download updates - small apps too, about 3MB. The download issues are nothing to do with my wifi as the tablet is slow wherever I use it, and my Nexus 5 downloads the same things in a matter of seconds. Would love to know what I could do to fix my N7. I don't want to root it or flash a custom ROM - don't want to go down that route - I just want the great performance that I had from it before.
I was having the same issues described here as well after owning the tablet for awhile, and tried every custom ROM, kernel, and android version I could find for our device along the way, in the hopes of finding a solution.
The one thing that finally helped for me, was formatting the device to use F2FS file system format on all partitions. The initial setup is a bit tedious, as you will lose ALL data on the device, so first must back up everything, then restore it all once the device has been reformatted. But the payoff has been huge for both me and my wife.
Making this switch has made both of our tablets usable again, even enjoyable! It's well worth the effort put in to make the switch.
See this thread here http://forum.xda-developers.com/showthread.php?t=2678140, which has the modified recovery, files, and instructions needed to convert. It also helps to first make sure you can successfully use fastboot/ADB commands from your PC to the device, in case you get into any trouble along the way.
There's also an app now available for converting any rom to all-f2fs (prior to flashing), it's cheap and well worth the cost (about the price of a cup of coffee) https://play.google.com/store/apps/details?id=com.runnerway.converttof2fs&hl=en.
Hello.
I enjoy my Nexus 7 2012 (Wi-Fi 32GB) tablet very much, when it is working properly and, unfortunately, that hasn't been often for some time. Android 5.02 helped a bit and the tablet is currently running 5.1 from a OTA update, which seemed to help a bit more. Android 5.1.1 has been mentioned however, I am not sure my issues will be helped by an update. For this reason, I am here to ask for advice or suggestions as to what I should do next (if anything!)
My first issue was the battery. The battery only lasts four hours per charge and since it is the original from 2012, I have ordered a new one and am awaiting its arrival. This tablet was a gift and whatever warranty it had has most likely expired so I am not concerned about invalidating a warranty. I hope that a new battery will make a big difference.
However, it is the second problem that is really annoying. The screen on my tablet freezes often, in any program and at any time. After charging the tablet, I've learned that it is best to restart the tablet to prolong the amount of time before the tablet freezes for the first time. Reading an article, for example, is a problem as I can read the first page but when it is time to slide the screen up to scroll to the next page, I am at risk of the screen freezing and it definitely freezes before page three. When typing a comment on Facebook or Twitter, etc. either they keyboard freezes while typing or if I can type the comment, the screen freezes before I can press the send key. I have other ways that are less portable to access these types of programs however, portability is the reason for a tablet. Using the tablet as a reader, I usually do not have any problems swiping page to page for usually as long as I'd like (although the swiping motion is a potential problem outside of the reading app.)
I backed up the tablet just prior to the 5.1 update and reset it to factory settings and for almost a week the difference was amazing. However, even with 5.1, the tablet is back to freezing again. Regarding the 32 GB internal storage; the actual available space after the OS is 28.17 GB and my available 23.90 GB. Due to the tablet's lack of response, I only reloaded a small number of apps and then, with the screen freezing multiple times in the four hours the battery allows, I uninstalled even more apps to get where I am now; I have never exceeded 50% at any time. In a browser, I often have more than one window open, yet it is the only program open. Sometimes, Facebook and Messenger are open at the same time but not always. If I get an incoming update, such as CNN, etc. if I open that for a few minutes, I'm risking another freeze. I am continuously aware of what programs are open and close them with the bottom square icon on my tablet. I have two frequent errors: SYSTEM UI is shutting down and the Process System is shutting down and they happen often. I am using Nova Launcher and the other Launcher on the tablet has been force stopped. I should probably note that I did the cache cleaning process two different times before I reset the tablet to factory settings.
Would going to something like the Cyanogen Mod be of assistance with this situation? There is an Official CM12 Mod available for this tablet however, the article I am referencing is from January 2015, written by Vinod Yalburgi titled, "Update Nexus 7 2012 (grouper) to Android 5.0.2 with CyanogenMod 12 official ROM." The tablet is already at 5.1 though and, as you have surmised correctly, I am not fluent in Mods of any type so I am unable to determine which mod is the best in this situation or if a mod is not going to be the right answer. I am open to rooting the tablet; the huge benefit I'd appreciate is the ease of creating a full back-up.
Is there another, more appropriate solution? My main concern is that if I wait for Lollipop 5.11, whenever that might be, it will not improve the issue with the screen freezing and I will have waited longer and ultimately gotten nowhere. Going back to KitKat 4.4 as I have read others have done is not appealing but if is the best solution . . .
Thank you for your patience with all of these details. I am hoping that with this info and all of the experience here, you can help me move in the right direction. Your time and any and all of your helpful suggestions are appreciated! This tablet can still work very well and as it was a gift, I want to make it work (on the days I do not want to hit it with a hammer!)
CShirey
I had the same freeze ups after the 5.1 update. I reset it 3 times to no avail! So I went back to KitKat 4.4.4. This lollipop is a big SUCKER, if you ask me... Google has screwed the pooch on this one.
? Take me to your Leader ?
Not the option I was hoping for but maybe the solution!
eLCruz said:
I had the same freeze ups after the 5.1 update. I reset it 3 times to no avail! So I went back to KitKat 4.4.4. This lollipop is a big SUCKER, if you ask me... Google has screwed the pooch on this one.
Take me to your Leader
Click to expand...
Click to collapse
Thank you for your suggestion! Does your tablet work well with KitKat 4.4.4? Any problems with freezing and battery drain? I have continued on with my research on this trying to determine what other owners have done in a similar situation. Lots of complaints but not a lot of answers, so far!
CShirey
General surprise at the lack of helpful replies!
I am grateful for the reply I received however, I am disappointed in the general lack of interest. Whenever I come to review posts here, I see that generally, most posts receive multiple answers. I am in the right forum . . . Is my question considered to be too simple . . . or did I miss an unwritten rule? Thanks.
CShirey
Sorry, had turned notifications off and forgot. It's working smoothly on 4.4.4! Should have never updated, IMO. I believe lollipop will be Google's windows vista... Hope every thing works out.
?Here, there be Whales...?
I recently rooted and unlocked the bootloader on my Razr M and installed a nightly build of CyanogenMod (I like to live on the edge, I guess.) The first week or so with it was going great, no issues as far as I could tell.
Then I installed a social application that requires GPS location. I noticed that the first time after enabling this the phone would freeze when plugged in to charge. It would freeze to the point where hitting the wake up button wouldn't even activate the screen. Not always, but it has happened on several occasions. So now whenever I charge it (daily), I have to force reboot (hold down Up, Down, Power in that order.) Sometimes it'll even go through the process of "Optimizing Apps" as if they were all just installed.
Firstly, has anyone else experienced this? And if so, is there an "easy" workaround? I can't quite pinpoint how to reproduce the bug, though I've got 3 different Cleaning applications installed that are used daily. That in mind, it's unlikely this is a memory leak bug.
Second, if there's no "easy" workaround, when can one expect the next Stable build of CyanogenMod, if ever? Is it still in development? I see that the last Stable release for this phone was in 2013. It seems like I'll have to downgrade to an earlier build, but just want some input before I do it.
Thanks much in advance
Sounds like an issue with the app, not the ROM. You said yourself that the issues started AFTER installing that app. So, delete that app and report back. Also, a lot of those cleaner apps out there will just bork your phone if you're not careful.
Sent from my Nexus 5
This is my second Ph-1 and it is starting to freeze multiple times a day. I read the previous post regarding Nova causing these issues, I am using the stock browser and so far, so smooth. I really dislike all the "whiteness" of stock and the lack of customization.. but it is worth it for a smooth experience.
twflys said:
This is my second Ph-1 and it is starting to freeze multiple times a day. I read the previous post regarding Nova causing these issues, I am using the stock browser and so far, so smooth. I really dislike all the "whiteness" of stock and the lack of customization.. but it is worth it for a smooth experience.
Click to expand...
Click to collapse
Side loaded any apps?
I've experienced this issue lately. Yes I am using Nova as my daily driver. I just restarted the phone and issue went away. Hopefully it stays away. If it pops up again I'll report back.
I've had my phone for about a month now. I have had Nova loaded since day one but just recently have experienced the freezing and reboots. It is very random for sure. I may try a run without Nova if it happens much more.
Charkatak said:
Side loaded any apps?
Click to expand...
Click to collapse
Nope, nothing sideloaded...
I am using Pixel 2 launcher for over a month and I like it.
I've had crashing on Beta 2 quite a bit with Nova. OTAing to Beta 3 reduces the crashes to once a week using Nova, which is pretty okay.
It's usually when I try to unlock the phone or am in the middle of doing something that everything just times out and reboots :s
Still on nought and have noticed bout the past week or so have had 2 freez ups. I'm using nova also. Rooted with magisk and viper and a batt mod.
twflys said:
This is my second Ph-1 and it is starting to freeze multiple times a day. I read the previous post regarding Nova causing these issues, I am using the stock browser and so far, so smooth. I really dislike all the "whiteness" of stock and the lack of customization.. but it is worth it for a smooth experience.
Click to expand...
Click to collapse
Wow... I've had my Ph1 for over a month, running Nova.(not rooted, don't feel the need to) .. and I've had no issues at all... I'll admit I can recall a few hiccups (nothing major) when I first received it, but after all the updates, mine is running top notch... I understand that this phone had a rough launch... and a butt load of updates... But I honestly can't complain about my experience....
Well I made it almost 8 days this time before it restarted on its own while sitting on my desk. I usually like to reboot my phones every so often but I wanted to see how long it would go this time. DARN lol!!!
qwahchees said:
I've had crashing on Beta 2 quite a bit with Nova. OTAing to Beta 3 reduces the crashes to once a week using Nova, which is pretty okay.
It's usually when I try to unlock the phone or am in the middle of doing something that everything just times out and reboots :s
Click to expand...
Click to collapse
Oreo beta 3 crashing often for me. Nova printer has been my launcher for a long time. Will try to uninstall it and run another launcher to see if that helps.
rootnooby said:
Oreo beta 3 crashing often for me. Nova printer has been my launcher for a long time. Will try to uninstall it and run another launcher to see if that helps.
Click to expand...
Click to collapse
Tried Apex launcher and pixel launcher. No real difference. Phone is difficult to unlock. Takes a long time. System UI crashed. Oreo beta 3 seems overall buggy for me.
Is there a way to troubleshoot whether or not I could be having a hardware issue as opposed to a software issue?
rootnooby said:
Tried Apex launcher and pixel launcher. No real difference. Phone is difficult to unlock. Takes a long time. System UI crashed. Oreo beta 3 seems overall buggy for me.
Is there a way to troubleshoot whether or not I could be having a hardware issue as opposed to a software issue?
Click to expand...
Click to collapse
Have you tried to factory reset and see how it acts? I have had no issues like that with OB3.
Warlord721 said:
Have you tried to factory reset and see how it acts? I have had no issues like that with OB3.
Click to expand...
Click to collapse
I've seen temporary freezes, like a 1-2 second delay but they're pretty rare. Not sure what some others are labeling a freeze. Does that mean 10 seconds, a minute, they need to reboot?
Jank4AU said:
I've seen temporary freezes, like a 1-2 second delay but they're pretty rare. Not sure what some others are labeling a freeze. Does that mean 10 seconds, a minute, they need to reboot?
Click to expand...
Click to collapse
I've tried a factory reset and that didn't seem to resolve the problem at all. In fact, it seems like unlocking got slower after the reset. The only things outside the box I am doing is using the Google camera app, running an app called layout to hide the navigation keys, and running an ADB command that makes the screen slightly larger by moving the top parameters of the screen up closer to the notch at the top of the phone. I guess I can do another factory reset, restore my applications, but don't install Google Camera or make any adjustments to hide navigation keys or change screen size.
I may do that, or just wait for the official release of Oreo which I hope is soon!
If anything here sounds like a hardware issue, I would appreciate your thoughts. Thank you.
rootnooby said:
I've tried a factory reset and that didn't seem to resolve the problem at all. In fact, it seems like unlocking got slower after the reset. The only things outside the box I am doing is using the Google camera app, running an app called layout to hide the navigation keys, and running an ADB command that makes the screen slightly larger by moving the top parameters of the screen up closer to the notch at the top of the phone. I guess I can do another factory reset, restore my applications, but don't install Google Camera or make any adjustments to hide navigation keys or change screen size.
I may do that, or just wait for the official release of Oreo which I hope is soon!
If anything here sounds like a hardware issue, I would appreciate your thoughts. Thank you.
Click to expand...
Click to collapse
But what kind of freezes are you getting? Is it more like brief lag or a complete freeze? If so, what's the duration?
Jank4AU said:
But what kind of freezes are you getting? Is it more like brief lag our a complete freeze? If so, what's the duration?
Click to expand...
Click to collapse
For example, when the phone has been sitting a few minutes I pick it up, touch the fingerprint sensor and get no feedback. The phone seems dead. I push the power button and nothing happens. I can do this several more times and then the phone may, or may not open. When it is working smoothly, I tapped the fingerprint sensor quickly and hear the"click" sound immediately. About 50% of the time this does not happen. If I had to estimate the amount of time it freezes or lags, it is certainly in excess of 10 seconds.
Many times I am forced to hold the power button down until it reboots.
In other cases, I may be in the middle of using the phone, it will start to lag and freeze, and then automatically reboot itself.
rootnooby said:
For example, when the phone has been sitting a few minutes I pick it up, touch the fingerprint sensor and get no feedback. The phone seems dead. I push the power button and nothing happens. I can do this several more times and then the phone may, or may not open. When it is working smoothly, I tapped the fingerprint sensor quickly and hear the"click" sound immediately. About 50% of the time this does not happen. If I had to estimate the amount of time it freezes or lags, it is certainly in excess of 10 seconds.
Many times I am forced to hold the power button down until it reboots.
In other cases, I may be in the middle of using the phone, it will start to lag and freeze, and then automatically reboot itself.
Click to expand...
Click to collapse
I'm on the beta 3 release and I'm not experiencing that at all. Fingerprint unlocks in under 1 seconds almost every time. You may want to try a clean install without your other "enhancements". Personally, I'd do that just to get some stability and/or reliability. That may also save you time once the 8.1 beta drops because if you can determine that's the culprit, you'll know not to install that stuff on the next beta.
Honestly, as finicky as this phone has been for some users, I wouldn't install anything other than normal apps from the Play Store. I'm really holding off on rooting until the 8.1 beta drops so I can still get the ota as soon as it's released. Then I'll start playing with custom ROM's, etc.
I've only had this for about a week, coming from a Pixel. Flashing that phone was the worst experience of my life, looking forward to trying it here.
Jank4AU said:
I'm on the beta 3 release and I'm not experiencing that at all. Fingerprint unlocks in under 1 seconds almost every time. You may want to try a clean install without your other "enhancements". Personally, I'd do that just to get some stability and/or reliability. That may also save you time once the 8.1 beta drops because if you can determine that's the culprit, you'll know not to install that stuff on the next beta.
Honestly, as finicky as this phone has been for some users, I wouldn't install anything other than normal apps from the Play Store. I'm really holding off on rooting until the 8.1 beta drops so I can still get the ota as soon as it's released. Then I'll start playing with custom ROM's, etc.
I've only had this for about a week, coming from a Pixel. Flashing that phone was the worst experience of my life, looking forward to trying it here.
Click to expand...
Click to collapse
Thanks. Good points. I'll take your advice and clean flash.
The phone is less than 6 months old, getting hard freezes. requires restart by holding power and vol down.
Happens almost everyday while watching youtube and trying to switch to any other application.