Related
http://www.youtube.com/watch?v=dC1jqmz6U_I
Today my phone again seems to let me down even more. I lock the phone, than press the HOME key only to find out, it won't unlock/wake up. Pressing all buttons and nothing wakes it up. So I asked my coworker if he could record it with his Droid (to show proof since HTC doesn't believe me). I have to take out the battery to get it out of this mode. This happens about 3 - 5 times a day and the phone is only 3 weeks old.
This is only one of the MANY of bugs I have with the phone. I've called T-mobile and got nowhere (soft resets, hard resets etc.), I've called HTC (run around answers), got nowhere, this is ridiculous. SENSE UI is bug ridden and nobody wants to take the blame or investigate it. I've called the T-mobile store where I got it from and they are on back order (going on 1 week), so I'm on a waiting list and I got 9 days left on my 30 day buyers remorse to exchange for a brand new HD2 or I'm ****ed
I can say I've had this happen too. I don't think I had this happen with a clean rom and I was guessing it was the gtX theme/mini lockscreen that might have been to blame so I'm going to do a hard reset (was planning on doing one anyway).
I've had this happen like twice. Hasn't been really an issue.
I know its sad to say but try flashing to a new rom. It works wonders.
SEscobedo said:
I know its sad to say but try flashing to a new rom. It works wonders.
Click to expand...
Click to collapse
........x2
This was one of the things that made me return mine. Happened to me 4 or 5 times the day I bought the phone. I'm like i'm not about to have to go through all this constant flashing with winmo again to get this thing to work right and took it back.
its called sleep of death and has been an issue since the hd2 launched. There are several long threads discussing it and trying various things. (I think one is titled 'hd2 died...or did it'' in the normal hd2 section)
Most cooked roms have cured it by now. Certainly i havent seen it since i moved away from stock roms.
It happened all the time on my Stock Rom. A few times on other roms. One thing is is uncheck 4hr time out.
dallastx said:
It happened all the time on my Stock Rom. A few times on other roms. One thing is is uncheck 4hr time out.
Click to expand...
Click to collapse
4hr time out on the screen options you mean?
Raadius said:
http://www.youtube.com/watch?v=dC1jqmz6U_I
Today my phone again seems to let me down even more. I lock the phone, than press the HOME key only to find out, it won't unlock/wake up. Pressing all buttons and nothing wakes it up. So I asked my coworker if he could record it with his Droid (to show proof since HTC doesn't believe me). I have to take out the battery to get it out of this mode. This happens about 3 - 5 times a day and the phone is only 3 weeks old.
This is only one of the MANY of bugs I have with the phone. I've called T-mobile and got nowhere (soft resets, hard resets etc.), I've called HTC (run around answers), got nowhere, this is ridiculous. SENSE UI is bug ridden and nobody wants to take the blame or investigate it. I've called the T-mobile store where I got it from and they are on back order (going on 1 week), so I'm on a waiting list and I got 9 days left on my 30 day buyers remorse to exchange for a brand new HD2 or I'm ****ed
Click to expand...
Click to collapse
I have had the same problem sense I purchased on Mar 24th, after trying to restore the devise 4 times within a 2 week period, I finally took it back and exchanged it for a new one, less than 24 hours, the new one froze up on me too. I searched through many forums such as this, and found that many users are having the same problem, I also read in one that the cause may be in the SD card that comes with the devise (the way it's formatted for use with it), so, 4 days ago, I removed the SD card, and the devise has worked flawless, no freeze ups, and for the last 2 days, I have not turned the devise off, and still no freeze ups. I plan on giving it a week, and if it does not freeze up on me, I'll put the card back in. I reformatted the SD card to get rid of the Double twist program, and the other apps such as the demo games, and put my music, Documents, and Photos back on it, hoping that it will work as a normal SD card when I put it back in.
Give it a try as I did, it just may be that simple fix everyone has been looking for.
Also, just for info, I'm running the stock USTMO ROM, with Cookies Home tab version 1.7 on it, Awesome and Flawless, if you don't want to flash a new ROM, you have got to at least install this add on.
I'll keep you posted on whether or not my test is successful or not
depgary said:
I have had the same problem sense I purchased on Mar 24th, after trying to restore the devise 4 times within a 2 week period, I finally took it back and exchanged it for a new one, less than 24 hours, the new one froze up on me too. I searched through many forums such as this, and found that many users are having the same problem, I also read in one that the cause may be in the SD card that comes with the devise (the way it's formatted for use with it), so, 4 days ago, I removed the SD card, and the devise has worked flawless, no freeze ups, and for the last 2 days, I have not turned the devise off, and still no freeze ups. I plan on giving it a week, and if it does not freeze up on me, I'll put the card back in. I reformatted the SD card to get rid of the Double twist program, and the other apps such as the demo games, and put my music, Documents, and Photos back on it, hoping that it will work as a normal SD card when I put it back in.
Give it a try as I did, it just may be that simple fix everyone has been looking for.
Also, just for info, I'm running the stock USTMO ROM, with Cookies Home tab version 1.7 on it, Awesome and Flawless, if you don't want to flash a new ROM, you have got to at least install this add on.
I'll keep you posted on whether or not my test is successful or not
Click to expand...
Click to collapse
happen to me twice here's what I did removed the battery for 15 - 20 mins works fine after that.
i've seen people buying faster sdcards and they've notice differences on how the phone works. I'm bout to buy class 6 sdcard this coming week.
but anyhow, i've had this problem for like twice since i bought the phone. I think some of the culprit is leaving 3rd party apps or games opened then pressing the home key. I think the phone is getting confused on what to draw/show in the screen. That time that my phone froze up on me on that lockscreen thing was when i was playing chop sushi then went back to home and accidentally locked the phone. The phone never went back on. The other one i can remember was when i was playing bejeweled 2. in both cases, i was playing a game, then went to home screen to check a message that came in, then having my phone locked.
xtenpeben said:
i've seen people buying faster sdcards and they've notice differences on how the phone works. I'm bout to buy class 6 sdcard this coming week.
but anyhow, i've had this problem for like twice since i bought the phone. I think some of the culprit is leaving 3rd party apps or games opened then pressing the home key. I think the phone is getting confused on what to draw/show in the screen. That time that my phone froze up on me on that lockscreen thing was when i was playing chop sushi then went back to home and accidentally locked the phone. The phone never went back on. The other one i can remember was when i was playing bejeweled 2. in both cases, i was playing a game, then went to home screen to check a message that came in, then having my phone locked.
Click to expand...
Click to collapse
Funny you mentioned that. My phone does this about 6 times a day. Just now it occoured again. instead of removing the battery, I removed the SD card. it awaked as normal. this generally happens to me when I'm listening to music (located on the SD card), and try to wake it for a track change or I get a call and screen turns off as it is placed to my face. I have other SD cards, I'll be trying those on this phone with general use to test results.
In the mean time. Since other roms have removed this issue, is there anyone who can isolate the issue in the stock rom and fix it?
Well, just to let you guys know, I'm on a stock T-mobile US HD2 rom, I have no 3rd party programs installed, and I always make sure there is NOTHING running in the background. The phone is a freezing machine lol, I've never encounter sooo many freezes on any phone I ever own, and I've owned a lot.
It just froze for about 10secs while typing a text back to my fiancee, ugh. I have now taken the sim out and put it in my iPhone.
Raadius said:
Well, just to let you guys know, I'm on a stock T-mobile US HD2 rom, I have no 3rd party programs installed, and I always make sure there is NOTHING running in the background. The phone is a freezing machine lol, I've never encounter sooo many freezes on any phone I ever own, and I've owned a lot.
It just froze for about 10secs while typing a text back to my fiancee, ugh. I have now taken the sim out and put it in my iPhone.
Click to expand...
Click to collapse
Have you a) done a hard reset, and b) tried running for a while without the SD card that came with the phone? Each of those has restored stability for some owners.
6 times just today
This is becoming a joke. Probably 6 times I've had to pull the battery Today. I'm totally stock tmous rom, no games, minimal other stuff. I took out sd card, moved data, full reformat, then put it in phone and did a "format sd card" in the phone, then transferred most of the data back on to card. NO change. I had an 8gb card which I tried last week. NO change. This is really absurd. Paid $500 for this turd. I'm gonna wear out the rubber sleeve removing it so often. Hope someone figures this out. Good luck to us all.
Hardreset 20x also.
Never had this problem.
sirphunkee said:
Have you a) done a hard reset, and b) tried running for a while without the SD card that came with the phone? Each of those has restored stability for some owners.
Click to expand...
Click to collapse
I'm on my 3rd hard reset, haven't tried the SD Card Removal, will do that now, thanks!
So far I guess I have been lucky. I bought 2 for one and no freeze ups I did replace one because the speaker stopped working two days out of the box but no freeze ups. I wonder what is the difference. mine is completely stock from Tmobile.
Maybe I am not using enough of the features to cause the freeze.Sorry you guys are having such a time with your phones that truly sucks...
Aloha Paul
And folks said I was "exaggerating" when I said this was a major issue with a lot of these phones.
I have searched through XDA and read all the threads regarding the 'suspend process' issue. The specific issue is outlined in Issue # 11126 on the Google Code/Android project home...
http://code.google.com/p/android/issues/detail?id=11126
I am trying to get to the bottom of this, as best as possible. For all intents and purposes, this really appears to be a mystery. Ultimately, it appears as though there is (currently) absolutely no specific reason a to why 'suspend' runs wild until the device is rebooted.
My question is (I know we can all only speculate):
Is there any chance that this could be Google account-specific?
The reason I ask is, I've been doing some "testing," just to try and make sense of this for myself. Here is what I've done/come across thus far...
- My fiancee's first MT4G was a black one manufactured in Taiwan. It had the inferior LCD-SH-C2 screen. Her battery was draining VERY quickly - i.e. before noon, without using the phone for much else other than texting.
- I enabled USB Debugging for her, to "rule out" the init process issue.
- Even though she only had Handcent, Facebook and Angry Birds installed, I removed all of them, leaving only Watchdog.
- I factory reset her phone, twice.
- For all of the above, the device was not rooted. I have since rooted her phone via the steps in this thread.
I'm in the process of creating a new Gmail account for her, exporting ONLY her contacts and then using that account for her new MT4G (Plum) that's scheduled to arrive today. I'm actually thinking of NOT using her new Gmail account at first though, so I can use her original Google account on this new, clean device and see if the suspend issue persists.
I might just be wasting my time, but I enjoy doing this and I don't think it's a complete waste to try and find SOME constant here. Am I nuts for thinking it's tied to the Google account? The Google account seems to be a black box of sorts. There is more than just contacts, apps and settings, yet there is no "window" into everything else that comes down - e.g. I can't log in to Gmail and "configure" it to not restore her wallpaper or WiFi settings. So that's why I say it's a black box of sorts, since it's doing more in the background than we have control over.
Nothing is truly random, at least not in the context of Android and the hardware affected. There has to be some reason why users of various devices, either do or do not experience this issue. Whether it's a specific action or the something that differs between one person's action vs. another person's, there has to be SOMETHING that's triggering this on her device, yet never triggers it on mine. I guess I'm just trying to flush everything out and hope that discussing it will help rule out/rule specific variables.
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
mwelliott said:
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
Click to expand...
Click to collapse
According to XDA and Issue #11126, you're not alone.
What's really bugging me is that neither my first MT4G, nor its 1st replacement or its 2nd replacement, have ever done this. My fiancee's first phone did this. She is now using my 2nd replacement while she waits for hers to arrive (today). So a device that never exhibited this issue, over the course of at least a week of normal-for-me use, started exhibiting this issue for my fiancee maybe a day or so after using the phone.
I thought I had "solved" it when I didn't see it crop up the first day she used my replacement phone. She was quick to let me know I was incorrect.
So I've got serious pressure here - all of my MT4G's haven't exhibited the out of control 'suspend process' issue while I was using the devices, but with her, it does. <queue the jokes>
We own our own business, so we're in the same room all day long while we use our phones. I was the first to tell her, "it's something you're doing." I'm only repeating myself by saying that I blamed it on an app she installed or something she "did" to cause it. After factory resetting, what...2, 3 times...I'm starting to forget; after checking the apps that are installed (and removing all of them); after verifying every setting from USB Debugging, screen brightness, account sync, etc. I seem to at least be able to say, "every single setting, shortcut, widget, app or usage pattern, does not produce the issue on any device I have used with my Google account, whereas it does with my fiancee."
That's the most difficult part to get absolute - the usage pattern. She's doing such basic things though, but I know that even the slightest of difference can produce different results.
I will most certainly report my results, futile or not.
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Chadastrophic said:
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Click to expand...
Click to collapse
That seems to be the constant, to a degree. I'm seeing people state that they're having this issue on anything from the Samsung Galaxy S (i9000) to a Nexus running Cyanogen 6.1. That's people stating it though, so I'm not sure if they're actually experiencing the same issue or not.
I am biting my tongue, but I think I found another common denominator...I am going to post back in a coupla days once I've seen it last for this entire week.
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
zero_oli said:
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
Click to expand...
Click to collapse
Yeah, it didn't seem 100% related to devices running Sense, so thanks for posting back to this.
My fiancee was experiencing this across her first two MT4G devices and has yet to experience the issue on her third and final MT4G. I want to see it run the rest of the week though before I share, but the issue did pop-up for her pretty much within 24-48 hours on her first two MT4G's.
Shlongwoodian: I have been following your posts as the "suspend" process has been affecting me since I received my phone the first day available. However, I am reluctant to send for a replacement as all else is great on the unit I have and there seems no gaurantee that a new phone fixes this issue.
I have tried Tmo and HTC and both seem clueless; therefore, I appreciate your research and look forward to any "fix" short of waiting for Gingerbread.
Anyone have any wisdom to pass on? This issue is driving me crazy! I've noticed it most on my black MT4G (w/the good screen) after browsing the web, youtube or using the media player. My wife's red MT4G (w/the inferior screen) has had no issues and her battery is amazing! The first day she got her phone her battery lasted 24 hours without even conditioning it! Granted she doesn't use it like I do mine, but it is still a huge difference. When this issue comes up on mine, I'm dead within 3-4 hours. I have Watchdog set so when it alerts me I just soft reset. That clears it up until it decides to come back at random intervals. It usually doesn't come back until I open the browser, etc. With as much as I use my phone (I am constantly on the road), it becomes a major pain to have to constantly monitor battery life. Any help is greatly appreciated!!!
Man, I am sorry to report that I gots nothin'. Ok, here was my original theory...
I was speculating that "something" inside the Google/Gmail account was the cause. My reasoning being, essentially, your info is stored in a database. When you get an Android device, that online database is synced locally with the phone's database. We each have different databases and there is more than just your apps, Market links, contacts, etc. I never exhibited the /suspend issue on phones that she experienced the /suspend issue on. I figured it was database-specific.
If a table contains a value, or rather, does not contain a specific value (or if columns are missing, etc.), it can cause an application to respond in a negative way. Sometimes, this causes an error to bubble up in an application. Other times, it doesn't. In my experience, I've seen much more subtle issues in databases, that don't cause errors or a crash, but instead just cause "undesirable results."
When my fiancee got her final, good replacement Plum Glacier, we started with a completely new Google account. We thought we nailed it, when a handful of days passed without seeing /suspend get out of control, leading to Android System and/or OS sucking down battery life. I think it was nearly a week into it and one day while she was out, she realized she lost battery life really quickly - i.e. left the house with 90% and by the time she got to the store, shopped for a bit and looked, her phone was down to like 30-40%. She knows how to check for /suspend and it was, of course, back.
It's still not something that can be completely ruled out, since it's not a very air-tight test. There could be something about my Google account (which I've had pretty much since Gmail beta was available) that's keeping me (and others like me) from getting it or that idea could be crap.
For some reason, I have never, ever seen this happen on my Glacier(s) running stock 2.2.1. Phones that I never saw the issue on, she saw the issue on. There is so much speculation around it, but it just seems like "some people" don't experience it and "some people" do. It's all over different devices, different skill levels, etc. No apps, same apps, whatever and it happens to some but not others.
Sorry to get anyone's hopes up. I'll keep looking for differences/similarities though and if I find anything at all I'll - or if anyone else finds anything, no matter how ridiculous it sounds (yes, we've tested the 'rock' and it doesn't appear to suffer from the /suspend issue) - post it here.
Thanks for trying! It was a good theory. So . . . now what? Is there any way to get this ranked higher with Google, HTC, etc. to get more people working on it? It is really driving me nuts! It mainly happens after I use the web browser, then put the phone on standby for some reason. I can't even use the browser any more without needing to reboot it to save battery life. There is another thread, but specifically for the Evo and I think one for the Nexus one, all with the same problem. What if a new thread were started that is not device specific? That way we can get more people to star it and maybe Google or whoever will pay more attention to it! I would hate to think that we are stuck with this problem until when and if we get upgraded to 2.3. I would suggest rooting and flashing a new ROM, but even those with custom ROM's are having the same problem, so that's not going to help. Thoughts???
jpiano said:
It mainly happens after I use the web browser, then put the phone on standby for some reason.
Click to expand...
Click to collapse
It truly is a mystery to this day. I've seen people say, "it happened right after I installed Handcent" or "it happens as soon as I do..." No one has come up with any concrete evidence thus far.
My fiancee has Handcent, I have Handcent. I used Handcent heavily, never had an issue. She stopped using Handcent - still has the issue. We've gotten so granular in our troubleshooting, we're literally tracking every step. LOL i.e. I pressed the trackpad to wake the phone, once; I unlocked the phone, I swiped my thumb once to view my Watchdog Widget on the screen to the left of my homescreen, etc., etc., etc.
So, for now, we just wait? My phone (and all previous phones) have been just fine. My fiancee however...yeah, I'm trying to find a fix pretty quickly.
One common theme that I've seen with this issue is that it only happens after I put the phone to sleep. I have never seen it crop up while actually using the phone. Maybe we're going about it the wrong way in trying to identify an app, etc that's causing the problem... perhaps it is simply the code involved in putting the phone to sleep and that's why there hasn't been any consistency with what one does to make it appear. In your experience, have you ever seen or heard of it showing up while the phone is being used? Perhaps it's just on mine that it works that way, but I thought it was worth mentioning. I know nothing about code or how android works so please forgive the noob comment if this is an obvious one. Merry Christmas!
I've got this problem big time. Returned my first phone because I thought it was the phone. First few days were good but lately its back and as bad as ever. First thoughts were angry birds twitter or wifi but I have no idea. If I can't figure this out I might have to sell this phone.
I will try to post some more thoughts. I think you're onto some good ideas here.
Sent from my HTC Glacier using XDA App
(Re-posting from the developer's Google blog where others are following this issue): Interesting about using the phone without a Google account. Not sure if this is relevant or not, but I've noticed something else with consistency. Granted I wasn't able to document the behavior through system panel at the time, but this has consistently happened. When suspend goes crazy, I can get it to stop simply by charging the phone! Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot. Noob speaking here but perhaps the part of android that actually logs the battery usage is suspending when the phone goes to sleep? When it us charging, this log is reset and clears the process from running. If this is even possible, then could someone write an app that clears this system log? Maybe by mimicking what happens when the phone is charging, we can at least temporarily clear the issue without the need tovl reboot? Again, I know nothing about all this so sorry if this is all irrelevant. Just sharing what I've noticed to be consistent. Thoughts??
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
jpiano said:
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I wonder if you're on to something with the SD card. I've been thinking I haven't seen the suspend issue return on my phone in quite a while. I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems. For those who are having the problem still, I wonder if removing or formatting their cards would show any improvement? Worth a shot if at least to eliminate another possible factor.
Sent from my HTC Glacier using XDA App
That's cool that this thread is flushing out other ideas and possible variables. I like the idea of connecting it to the charger for a couple of seconds, but my fiancee is so used to just rebooting her phone each morning and sometimes again by mid-day, that it's easier for her to do just that.
jpiano said:
Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot.
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I like the microSD Card notion. This is such a weird issue, that it's so easily associated with other items - e.g. applications, usage patterns, etc. This seems feasible though, but the only way to know for sure is to reproduce it. My fiancee experiences the suspend issue daily, if she doesn't reboot regularly. So, I should be able to take her microSD card and use it in my phone and get the suspend issue. I don't want to 'muddy' up by swapping microSD cards, so I'll try reformatting her card and see if that makes any difference. She usually sees the issue within 24-48 hours of a fresh boot, so it shouldn't be long before we see if that fixes it or not. I can check the card for errors, etc. as well.
werk said:
I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems.
Click to expand...
Click to collapse
I'll be upgrading to a 16 GB Class 10 soon, so I can give her my Samsung if need be. I'd really like to see if this is it though. It would explain the "some people get it and some people don't" pattern.
I also noticed that the minute I plug the phone in the problem goes away. Not sure why, just confirming it happens to me too. I also should note that when I returned my phone, they popped my old SD card into my new phone. So if there is an SD card issue with a corupt file/photo that could be something as well. I wonder woody if your girlfriends phone has had the same SD card after how many times did you say you traded it in? BTW, a side note, how did you exchange it so many times? After I took mine back to the store on day 14 they told me I wasn't able to exchange it again.
I do have a 16GB SD card but just haven't had time to install it. Wanted to double check which things I need on the new one from the old one, but it might be a good way to test this issue. Let me know some ideas before I swap the cards and maybe I can help test this.
Also, one more thing, what is the app you're using to log stuff? I'm just using Watchdog Lite right now.
I've got to figure this out or this is a dealbreaker for me. I have waited 3 years to upgrade phones, first time on Android, really wanted iPhone but wanted to stick with month to month from TMob. If this continues I think I will move to Windows Phone 7 or iPhone if I have to, but I really like this phone when the battery is not draining like a leech.
Thanks.
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
royhobbs said:
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
Click to expand...
Click to collapse
Just straight copied the existing files over from the old card to new one (new one in phone connected via USB, old card in SD adapter in my laptops SD card slot). I think some Angry Birds files didn't make it due to long paths, but reinstalled it and no problems since then.
So, my phone has been running fine for weeks (it was at I think like 600+ hours uptime before I had to reboot it for the first time two days ago). I'm running Apex 1.4.1, with no custom modifications. I was using it one day, then a little later it just started freezing for several seconds anytime I tried to do anything, then unfreezing for a couple seconds, then freezing, etc. I rebooted it, then it was fine for a little while. Then I was texting someone back and forth for an hour or so, and all of a sudden it stopped sending my messages. I rebooted, and it was able to send again. Now today apparently she isn't getting them again, because she asked the same question I already replied to, over an hour later (I mean, she could have just not seen the reply, but with the other recent problems I'm not betting on it...).
Has anyone seen issues like this? Also, come to think of it, Yahoo Mail has been acting just retarded...it keeps disabling status bar notifications on its own (twice so far), but regardless, when it IS notified, it's not letting me know when I get new emails, I have to go in and look. My batteries been dying a LOT faster, and my data usage has been steadily climbing over the last couple days (I haven't downloaded anything, and my normal usage recently has only been very basic) and I have a feeling Yahoo Mail has been constantly trying to connect but failing, except for when I manually go into it? But that's just a guess.
This is all just bugging me, so any suggestions would be helpful. I can just backup my needed apps, wipe and re-flash Apex, but if anyone has any other suggestions I would love to hear them. Thanks
Well I think you went wrong when you didn't shut it off for over 600 hours. Did you really need it to be on at that time? Even at night?
But anyway that's just my rant. Reflashing apex would be a good place to start. And make sure you just wipe everything. If that doesn't work, you may want to go completely back to stock and then back to apex
So you're saying this OS is not as stable as Windows? Because I've had Windows OS's stay running for months without issue. Gee, if Android isn't is good as Windows, maybe I should look into getting a WP7 phone... /sarcasm
If there aren't issues, then there's no reason to turn off your phone. Shutting it down at night is good if you don't want to charge it, but it really shouldn't be a requirement unless if Android isn't ready for prime-time (and no, I'm not saying that's the case). I had an issue, I rebooted, I had another issue, I rebooted, I had ANOTHER issue, rebooted, and so far it's been good since yesterday afternoon.
I really think it was the Yahoo Mail app though I don't know why it would have prevented sending text messages... I did a force stop, cleared it's data, removed it, rebooted, and then reinstalled the app. So far, it's been working OK from what I can tell. The data usage has slowed, battery life seems to be good again, and I'm getting notified of new Yahoo emails.
Actually I am not at all concerned with the software. I was talking about the hardware. Would you leave your computer running for 600+ hours?
Like I said, I have. My file server (Windows Server 2003) has been running (except for a few brief shutdowns for hardware upgrades/swaps) for over 2 years. My main PC (Windows 7) has been running, for the most part, except for a few times when I just felt like shutting it down, for probably the last 6 months.
Ok well if it works for you, then great keep doing it. But I'm just saying, as a computer guy, that is just a general bad idea
Nice to know, but I'm also a "computer guy" (professionally) and as a rule of thumb I keep my office computer on 24/7/365, as well as my home computers.
sfreemanoh said:
Nice to know, but I'm also a "computer guy" (professionally) and as a rule of thumb I keep my office computer on 24/7/365, as well as my home computers.
Click to expand...
Click to collapse
Since you are a computer guy, could you please explain how there aren't any adverse effects on your hardware from keeping it running? Primarily on the cpu and fans? No chance you could burn something out?
Jmoney47 said:
Actually I am not at all concerned with the software. I was talking about the hardware. Would you leave your computer running for 600+ hours?
Click to expand...
Click to collapse
Why would you shut it off? I don't think leaving it on all the time is the issue. why shut your cell phone off? I think that's stupid. Then again I'm a midnighter so I guess things are different for me. I never shut off my cell phone or PC.
Jmoney47 said:
Since you are a computer guy, could you please explain how there aren't any adverse effects on your hardware from keeping it running? Primarily on the cpu and fans? No chance you could burn something out?
Click to expand...
Click to collapse
It's designed to run like that. I'm a big PC guy as well. I do a few custom builds here and there. Seriously turning it off and on all the time it going to cause more damage (especially to your HDD) then keeping it on all the time. It's like a car being in stop and go traffic versus highway mileage. I think the last time I shut my PC off was around Christmas cause I had to reformat and couldn't get it done before I went to work so since my network wasn't up yet no reason to keep it on.
Computers aren't like cars..."gunk" and "sludge" (and yes, I'm getting these highly technical terms from TV because I know crap about cars) don't build up in computers. Pieces wear out, sure. But that can happen just as easily from frequent turning on and off. Like I said, my two computers at home stay on almost constantly, and I don't exactly dust or vacuum frequently. The last thing I had to replace was in my gaming PC, and that was the video card since it was two years old and couldn't play Crysis 2 well enough.
sfreemanoh said:
Computers aren't like cars..."gunk" and "sludge" (and yes, I'm getting these highly technical terms from TV because I know crap about cars) don't build up in computers. Pieces wear out, sure. But that can happen just as easily from frequent turning on and off. Like I said, my two computers at home stay on almost constantly, and I don't exactly dust or vacuum frequently. The last thing I had to replace was in my gaming PC, and that was the video card since it was two years old and couldn't play Crysis 2 well enough.
Click to expand...
Click to collapse
I don't know much about cars either. Maybe I wasn't using the correct tone, but I actually agree with you. Like I had said in my post I keep my machines running 24/7 usually same with cell phone. I don't know crap about cars either the only reason I used the comparison is that wear and tear from city driving or stop and go traffic (when compared to turning your pc on and off frequently) is worse than freeway or long distance without stop driving (as referring to keeping your PC on) So yea we are pretty much saying the same thing
Hey thank you for explaining it to me this way. I never thought of it like that. You are probably right. Excuse me for just one more question though: would keeping it on all the time actually end up using more power than you would if you kept it off?
Jmoney47 said:
Hey thank you for explaining it to me this way. I never thought of it like that. You are probably right. Excuse me for just one more question though: would keeping it on all the time actually end up using more power than you would if you kept it off?
Click to expand...
Click to collapse
Well...yeah, obviously. But if someone tries to call me in the middle of the night for an emergency, and I don't get the call because my phone was off, well, that would suck. But with Apex, I've went to sleep on, for instance, 80% battery, woke up, and the battery still said 80%. As for my computers, well, yeah, that costs me a little more per month, but it's not breaking my bank, so it doesn't bother me.
cstrife999 said:
I don't know much about cars either. Maybe I wasn't using the correct tone, but I actually agree with you. Like I had said in my post I keep my machines running 24/7 usually same with cell phone. I don't know crap about cars either the only reason I used the comparison is that wear and tear from city driving or stop and go traffic (when compared to turning your pc on and off frequently) is worse than freeway or long distance without stop driving (as referring to keeping your PC on) So yea we are pretty much saying the same thing
Click to expand...
Click to collapse
Lol Sorry, I wasn't referring to your posts (we just both happened to use car references).
Jmoney47 said:
Hey thank you for explaining it to me this way. I never thought of it like that. You are probably right. Excuse me for just one more question though: would keeping it on all the time actually end up using more power than you would if you kept it off?
Click to expand...
Click to collapse
Yea but honestly if your pc isn't super holy **** beast mode it isn't going to be that noticeable. I have a nice higher-end PC and it isn't that bad on my bill.
How can you even avoid updating your phone? I got my T Mobile phone yesterday and before I could finish creating my Google account, Android restarted the phone in Odin and installed an update. I am still on 5.0.1 but I do not want any more updates. I actually wanna see how Kit Kat runs because my phone's battery sucks, granted I still have to work out battery life tricks and read up on stuff, but I find it ridiculous that I need to put my phone on power saving mode off the bat to get it to last till 5 Pm with moderate use...very moderate use. I don't even play games. And I've heard horror stories of reverting back to Kit Kat so I'm scared that my 400 dollar phone will become useless if I try it
It just seems Samsung is out to sabotage the Note 4 family so we buy their crappy Note 5
Settings, about phone, software updates, automatic updates: off.
Even with this set on, you only get a message about an available update. You don't have to apply it. And Odin is a program on your PC, not your phone. When you do apply an available OTA update, the phone goes to recovery mode to perform the update.
Oh I meant recovery mode. I did not apply an update. The phone automatically updated itself. Are you sure this works? I have heard people say they got updates regardless of forcing their phones not to update
I've never had a phone force an update on me and I always have the above setting set to on. It would also really surprise me: what if you're waiting for an important call? Maybe during first installation it's different? In that case: skip the installation wizard, don't yet setup WiFi, and setup your Google account and WiFi later.
Too late for that. Are you on Lollipop? I haven't had time to start browsing for ROMs yet. Prbly won't for a while since I'm jumping straight from internship to school. Btw I actually have a Note Edge but I figure they essentially have the same Bloatwiz/Lagwiz stuff in them
Going to a newer OTA will not make your phone useless, thats just serious over-reaction. Im on BOG5, and am able to "debloat". I get more than a full day of battery, and that includes surfing the web, playing music, some games, and bluetooth on all the time (hooked up to my car).
Man I'm jealous. Tradeoff on getting the Edge. Not much ROM support.
Good morning from Upstate New York, USA.
First, thank you to all the members who have posted such excellent information here. If time spent on this site were worth university credits, I think I would have earned a degree this past week or two. My name is Richard and I'm a semi-retired IT guy who still does some Web development (not so much apps as general Web stuff). I'm amazed at the breadth and depth of knowledge on this site.
The abridged version of why I wound up here is that I have two LG V20 h910 phones. One was still in the box until two weeks ago. I decided to put it into service as a car unit, mainly to run GPS-dependent navigation and mapping apps, because the GPS radio in my main phone is getting tired. It still works, but the signal strength is borderline.
My main phone also has a lot of other apps that I need, some of which require location services, but none of which require an especially strong or consistent signal. So rather than wipe that and move everything to the spare phone, I decided to put the spare into service for car-related stuff. Besides, having another phone number for very limited distribution will come in handy since my "main" number is starting to get too many blasted robocalls.
Because the navigation apps I use don't require Google Play Services, I decided to try rooting the spare phone and trying out more lightweight custom ROMs. That became quite an adventure, albeit a very educational one. I installed about half a dozen ROMs (not including cross-flashing to get root back), thought I bricked the phone about as many times, and in the end wound up with stock Oreo (no root). I'm going to test that today to see how well it navigates. If it works well, I may leave it that way.
If not, then I'll reinstall the unofficial LineageOS 17 beta, which came closest to meeting my needs for this device. It had everything I needed except the ability to route the sound to the car radio via BT using any way that I'm aware of. Other than that, it ran the GPS-dependent apps splendidly. I'm following the progress of that project and may try it again if that deficit is fixed (or if I feel like trying to fix it myself).
Which brings me to the question:
Can Patched LGUP Make a Usable Backup of an AT&T h910?
It's a real drag to have to downgrade / crossflash and re-root to re-flash stock. I know ATT doesn't release .kdz files, but can LGUP DUMP make usable backups of a stock AT&T system that can be easily restored? If so, how would I do that?
As I said, I really don't need root on this device, assuming it does what I need it to do (basically run my navigation and mapping apps). I'm going to test that today, which is an excellent day for that because it's cloudy outside. But if it doesn't, then probably I'll be trying LOS 17 again. It would be nice to have an easier way back to stock than crossflashing, downgrading, re-rooting, and re-flashing.
Thanks again,
Richard
GeekOnTheHill said:
Good morning from Upstate New York, USA.
First, thank you to all the members who have posted such excellent information here. If time spent on this site were worth university credits, I think I would have earned a degree this past week or two. My name is Richard and I'm a semi-retired IT guy who still does some Web development (not so much apps as general Web stuff). I'm amazed at the breadth and depth of knowledge on this site.
The abridged version of why I wound up here is that I have two LG V20 h910 phones. One was still in the box until two weeks ago. I decided to put it into service as a car unit, mainly to run GPS-dependent navigation and mapping apps, because the GPS radio in my main phone is getting tired. It still works, but the signal strength is borderline.
My main phone also has a lot of other apps that I need, some of which require location services, but none of which require an especially strong or consistent signal. So rather than wipe that and move everything to the spare phone, I decided to put the spare into service for car-related stuff. Besides, having another phone number for very limited distribution will come in handy since my "main" number is starting to get too many blasted robocalls.
Because the navigation apps I use don't require Google Play Services, I decided to try rooting the spare phone and trying out more lightweight custom ROMs. That became quite an adventure, albeit a very educational one. I installed about half a dozen ROMs (not including cross-flashing to get root back), thought I bricked the phone about as many times, and in the end wound up with stock Oreo (no root). I'm going to test that today to see how well it navigates. If it works well, I may leave it that way.
If not, then I'll reinstall the unofficial LineageOS 17 beta, which came closest to meeting my needs for this device. It had everything I needed except the ability to route the sound to the car radio via BT using any way that I'm aware of. Other than that, it ran the GPS-dependent apps splendidly. I'm following the progress of that project and may try it again if that deficit is fixed (or if I feel like trying to fix it myself).
Which brings me to the question:
Can Patched LGUP Make a Usable Backup of an AT&T h910?
It's a real drag to have to downgrade / crossflash and re-root to re-flash stock. I know ATT doesn't release .kdz files, but can LGUP DUMP make usable backups of a stock AT&T system that can be easily restored? If so, how would I do that?
As I said, I really don't need root on this device, assuming it does what I need it to do (basically run my navigation and mapping apps). I'm going to test that today, which is an excellent day for that because it's cloudy outside. But if it doesn't, then probably I'll be trying LOS 17 again. It would be nice to have an easier way back to stock than crossflashing, downgrading, re-rooting, and re-flashing.
Thanks again,
Richard
Click to expand...
Click to collapse
The short answer is no ...the LGUP is not easily restored
The best way I found was to leave the patched aboot and TWRP on the phone and use the 20H rooted rom along with MK2000 kernel (Newest)
and reinstall TWRP (It gets wiped with the 20H rom)
their is a H910_20g_Oreo_full_stock_Tested.zip if you really want to restore the phone to full stock and take the OTA to 20H
clsA said:
The short answer is no ...the LGUP is not easily restored
The best way I found was to leave the patched aboot and TWRP on the phone and use the 20H rooted rom along with MK2000 kernel (Newest)
and reinstall TWRP (It gets wiped with the 20H rom)
their is a [I can't post links yet, even when quoting] if you really want to restore the phone to full stock and take the OTA to 20H
Click to expand...
Click to collapse
Thank you. That's actually the image I used in the end. If stock Oreo works best for what I need this particular device to do, then I'm okay with using stock Oreo, uninstalling the crapware that I can, and disabling what I can't.
I can also attest that that image worked flawlessly.
Richard
I should also mention that this whole adventure has given me even more respect for the V20. It's practically impossible to brick. No matter how badly I hosed it, there was always a way back.
Richard
The "spare" h910 passed its navigation tests with flying colors. I took it for a two-and-a-half hour drive to Micro Center, and my favorite nav app (Magic Earth) performed flawlessly there and back. The only hiccup was on a small stretch of road where half the birds suddenly disappear from the sky due to the topography (the road was cut through rock). It confuses all GPS-based systems.
So that's my new navigation device. I'm also going to route my work number to it since I'm paying for the service anyway. I took the lowest-level AT&T prepaid plan with data. It's only 1 GB with one-month rollover, but I use very little. It will mainly be for traffic data for the navigation apps.
One thing I noticed was that the "car phone" was much cooler than the h910 I had been using before, even after navigating for two and a half hours. So I decided to retire the other h910 I'd been using as my "main" phone, but leave it configured as a hot spare.
I picked up a XIAOMI Mi Mix 3 at Micro Center for USD $379.98, which I think is a steal hardware-wise. I'll use that as my main and personal phone, and the h910 I put into service two weeks ago as my car and business phone. That's assuming I like the XIAOMI, of course. I'll see if there's someplace I can talk about my initial impressions of that phone.
Richard
GeekOnTheHill said:
The "spare" h910 passed its navigation tests with flying colors. I took it for a two-and-a-half hour drive to Micro Center, and my favorite nav app (Magic Earth) performed flawlessly there and back. The only hiccup was on a small stretch of road where half the birds suddenly disappear from the sky due to the topography (the road was cut through rock). It confuses all GPS-based systems.
So that's my new navigation device. I'm also going to route my work number to it since I'm paying for the service anyway. I took the lowest-level AT&T prepaid plan with data. It's only 1 GB with one-month rollover, but I use very little. It will mainly be for traffic data for the navigation apps.
One thing I noticed was that the "car phone" was much cooler than the h910 I had been using before, even after navigating for two and a half hours. So I decided to retire the other h910 I'd been using as my "main" phone, but leave it configured as a hot spare.
I picked up a XIAOMI Mi Mix 3 at Micro Center for USD $379.98, which I think is a steal hardware-wise. I'll use that as my main and personal phone, and the h910 I put into service two weeks ago as my car and business phone. That's assuming I like the XIAOMI, of course. I'll see if there's someplace I can talk about my initial impressions of that phone.
Richard
Click to expand...
Click to collapse
I currently have a Xiaomi Poco F1 that I play with from time to time. only real problem with it is no network bands for Tmobile (Mint Sim)
I get a good strong signal on band 5 on AT&T so it fine for me.
I also had a Mi Mix 2s that seemed pretty solid. But it was Stolen and never recovered after just a month of use.
Anyway, Enjoy your new phone and Happy new year
clsA said:
I currently have a Xiaomi Poco F1 that I play with from time to time. only real problem with it is no network bands for Tmobile (Mint Sim)
I get a good strong signal on band 5 on AT&T so it fine for me.
I also had a Mi Mix 2s that seemed pretty solid. But it was Stolen and never recovered after just a month of use.
Anyway, Enjoy your new phone and Happy new year
Click to expand...
Click to collapse
Thank you, and Happy New Year to you, as well.
I forgot to update this thread, but sadly, I returned the Xiaomi the day after I bought it. Just when I actually thought I might get to like (or at least live with) MIUI, I made an actual phone call; and the sound quality was so horribly bad that I knew it was something I would not be able to live with.
I searched around for answers, and found something on Xiaomi's site about sometimes needing to reset the phone after doing the update that had been installed OTA after I bought the phone, so I tried that. But when it rebooted, it wouldn't accept my password. Neither would their Web site; and three password reset requests went unanswered. Then I tried by phone number, and it said the account didn't exist.
I packed up the phone, put the SIM in the V20 with the tired GPS, and also installed a new spare battery in that phone. I'd had the battery for a while but hadn't installed it because the battery life on the V20 was okay. But since I had the phone out of the case anyway, I installed it and charged it while I was on my way to Micro Center to return the Xiaomi.
My intention had been to buy another phone while I was there; but when I reached for the V20 after I parked the car, I noticed that it was cool. I thought I'd forgotten to plug the charging cable in because it had been running hot. But it was plugged in and fully-charged. So I'm guessing that the old battery was faulty and had been causing the heat issues in the V20. I guess that might have caused the GPS issues, too, although I haven't had time to check.
In any case, the one V20 works acceptably well for everything except navigation and mapping, and the other V20 works fine for navigation and mapping; so I'll just keep them both activated for now while I do more research. I do plan to purchase a newer phone, but I'm no longer in a hurry now that the one V20 is not overheating. It gives me time to do the kind of research I like to do before purchasing electronics.
Thanks again,
Richard