Related
I'm looking for advice. Should I stick with the 8525 or get something else.
I'll return it for a new one, but now I'm getting nervous as I read about folks having similar problems with freezing. I do need a reliable phone / pda. While it worked, I liked it, however, the 8525 froze at least once a day, would, at times, balk at making calls, and finally had the phone / internet functions die. It was never dropped nor abused. I did the fool active sync. fix and installed a task manager and a program to re-map the ptt button to voice activated calling. Those are the only changes I made. I am trying to figure out if my bad phone is an exception or the rule.
So, from the standpoint of reliability, would you recommend to stay with the 8525? I do have a choice, and I can change my order from the 8525 to almost any phone. I am considering a downgrade to an 8125. Two of my collegues have them and they are reliable. Any thoughts?
All I can tell you is I have not had any of those issues with mine.
d
I'm probably jinxing myself, but I've had mine since mid-January and so far all is great. I power it off and on each day, maybe it helps, who knows. I've also had the occasional freeze and boot-up sometimes freezes but I think those are normal pda things that you just learn to deal with. If you are within your 30 days and you think it's unstable just swap it with a new one.
Did you install your task manager to a storage card? That was a very common problem of freezing for me... two to three times per day. Since I moved all critical apps to the internal memory I've only had two freezes (this was 3 weeks ago) and they were because I was messing with apps.
i had my 8525 for 2.5 weeks and it works great. i have the same hacks plus a few more, especially the bigger button dialer. I did update the ROM to 1.34 (september 2006 version, latest official) from HTC america's official website. Oh, by the way it's an unlocked version using T-Mobile. My biggest complaint is the not-so-firm keyboard. It's ever so slightly slides out in my pocket... Maybe you should flash yours too...
My Out-of-the-box experience was similar to yours. It froze, the bluetooth didn't work at all, ugh. I upgraded to HTC ROM 1.35 and now my Hermes is pretty stable with only one freeze.
Since upgrading my TD2 to the official WM6.5 ROM issued by HTC I have had problems with the handset freezing; the only remedy has been to remove the battery and switch back on. At first I thought it was a hardware fault but a friend's phone has also started doing the same since he upgraded. This never happened previously and only happens every ten days or so.
Has anyone else experienced similar problems?
I'm having the same problems mate. My TD2 on 6.5 freezes spoaradically - I'd say at least twice a week, and the only solution is to remove the battery.
I've been trying to link the freeze with a particular program or app but the phone has frozen at varying times and in many cases whilst no apps are running!
I'm waiting for upgrade on my contract as I've had it with this TD2 and especially WinMo. I mean, how can WinMo store all saved words in SMS on RAM only for it to be wiped after every restart/soft reset?! Why? Argh!
I'm going for the Hero next, and see how nice Android plays!
Good luck with your query...
Mo
miker1892 said:
Since upgrading my TD2 to the official WM6.5 ROM issued by HTC I have had problems with the handset freezing; the only remedy has been to remove the battery and switch back on. At first I thought it was a hardware fault but a friend's phone has also started doing the same since he upgraded. This never happened previously and only happens every ten days or so.
Has anyone else experienced similar problems?
Click to expand...
Click to collapse
Does it do this without the mem card installed?
Exactly the same is happening here and the same on my friend's TD2. We have never tried WM 6.1, the first step after purchasing the phone was to upgrade to stock WM 6.5 ROM.
I tried to disable the weather animation on home screen but this doesn't help. My friend has disabled HTC sense and his phone has not frozen after one week. We will have to wait another week or two to proof that this could be the solution.
I hope that Touch Flo is not the cause of this malfunction because WM6.5 UI is very ugly.
I don’t know if the mem card could cause this issue but using the phone without mem card is simply not an option for me. The phone memory is too limited.
My friend also raises this issue on HTC support but so far HTC is ignoring the problem. The only bright word from HTC support was that they will investigate this issue (after many words on how to flash, reflash and hard reset ...).
I really hope that the solution for this very inconvenience will be find out soon.
My TD2 also freezes often compared to Win 6.1 where it almost never froze. I also hope that HTC will make some kind of service pack for Win 6.5 as it doesn't work that well at the moment.
pa49 said:
Does it do this without the mem card installed?
Click to expand...
Click to collapse
Not tried it without the memory card, but I need the card for storage. Never froze prior to 6.5 upgrade.
miker1892 said:
Not tried it without the memory card, but I need the card for storage. Never froze prior to 6.5 upgrade.
Click to expand...
Click to collapse
I'm not suggesting that anyone uses the device without a mem card! You are missing my point.
Phones that freeze do so for a reason and it's necessary to eliminate possible causes.
Some two years ago I did extensive testing on this subject when the same issues arose around another make and model of phone.
One thing I found is that it is possible to induce instability of handsets when mem cards are used (abused?) in certain ways.
My TD2 used to freeze when I first got it and it has also done so with a number of cooked ROMs. With my current ROM it never freezes and there are no instability issues.
I strongly suspect poor coding of apps and lack of thorough beta testing. Isn't it strange how some apps have been around for years and you can rely on their worth?
Installing to mem card causes issues as well as cards that have installed apps being reused after cooked ROM flashing and previous settings and fat tables being left on the card.
Also when power is low mem cards draw large currents that the battery may not be able to give. They are very power hungry. I took this up with Sandisk Tech Dept and they politely told me that the info on current draw under stress (usage) was not for public access!
So my answer is keep your ROM light (no manila or after market 'front end'), minimise card usage by installing all you can to phone mem, reformat afresh with every ROM flash and keep your battery as highly charged as possible at all times.
Some say 'yes but I do all those things and I never get freezes'. That's fine but no help to those that do.
There really is only one way to find out and that is to take a little time and try it for yourself.
Large address book combined with bad 3rd party program
On my Tilt2 I found that applications like Fring could freeze the phone. After a few tries, I decided not intall that anymore (and Fring might have fixed it by now, but I can't afford to try, because uninstalling required a hard reset).
The phone originally came with HTC TouchFLO, but I switched that off, since it just made everything more difficult to reach. And sometimes the fhone became unresponsive, slow or totally frooze. After I disabled it by using the Windows Today (6.5 or classic) after which I only had about 2 freezes in 1.5 year.
Now I finally upgraded to the latest official ROM for the phone, which has HTC Sense on it. After everybody saying how great Sense was, I gave it a try. It worked reasonably, until I started playing with the Favorites in the Peoples tab. After each new addition (I tried 3) I had to restart the phone, and after restart it still hung up.
I happen to have a quite large address book that I synchronize with ActiveSync. I think I'm starting to see a pattern, where several applications - Fring, Sense, etc - just cannot handle large address books.
By the way, to disable Sense, first switch to the Windows Default (= WinMo 6.5) Today screen, and do a soft reset to get rid of Sense background processes. If you want to use the WinMo classic Today screen, then you can do that after the reset. Directly trying to move from Sense to WinMo classic resulted in another freeze. After disabling Sense, I haven't experienced a freeze, (yet !!!).
^^Try a custom rom,Sense works fine on those as the ROM is highly modified with few errors now.
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.
Problem 1:
I've just rooted my nexus-s and I'm not sure whether it's due to rooting or a software conflict with apps installed on the device that's not compatible with android 2.3, but I'm experiencing quite a frequent phone reboot while I am in the middle of an active call.
Is there a way to capture the log of the phone's function and see what's causing the reboot?
Are anyone experiencing this problem as well?
Problem 2:
I probably have only used 240 Mb of the USB storage, and it shows that I have 13Gb free. However, when I put the check boxes beside the applications that can be moved to the USB storage (i.e. native apps2sd), I seem to have surpassed the limit allowed for moving the app for USB storage. I've got 21 apps that can be moved, but it won't allow me to move the 21st app. Error message says "[! Move Application] Failed to move application. There is not enough storage left." I've tried checking and unchecking boxes of different applications, and it has nothing to do with the 20 apps limit, but rather it's the amount of memory being moved to the USB storage
********************* updated 01-12-2011 **********************
Please report to Issue 13674 on google's bug reporting page.
hXXp://code.google.com/p/android/issues/detail?id=13674
Sorry, I'm a newbie, so I can't post outside link. Please change the XX to tt in the link above.
************************************************************
Well I have 23 apps on my USB storage, and I have the Voodoo Root kernel as well. It shows 2.1gb used, 11gb free.
I did notice a 'soft reboot' earlier today but it wasn't during a call, don't know what caused it but yeah. Honestly if I were you and the problem persists just reformat and start over.
Im having the same phone reboot problem as you during phone calls. I thought it was due to an app called Screebl being incompatible, but i just made a test call and it rebooted after about 18 minutes. Im going through my apps to see what else effects the phone state during phone call.
Ive heard of some people having problems with google maps causing problems during phone calls, or sprint nav (but we dont have sprint nav) So im going to try shutting down maps, and uninstalling my task killer, which i also heard can cause problems.
Have you been able to figure anything out? I really dont want to have to reset my phone and lose all my save data information from my games. My phone is not rooted, and i dont plan on rooting yet, so i cant use titanium backup for my data.
Phone only Reboots during active phone call, i can play games or surf the web on it all day long with no reboots.
So software issue in android 2.3, or some kind of app incompatibility im thinking
you can capture the log with adb logcat command, or download a logcat app from the Market http://www.appbrain.com/search?q=logcat
Why are you bothering with apps2sd? The Nexus S shares the Galaxy S line's hugh, I mean HUGE, 1GB of "disk" space for apps. I've got almost 100 apps on my phone and not a hint of low space. See the screen capture I've attached: 284mb used for apps, 724mb still free!
oh crap! please let it not be the same problem as in the SGS i9000m
that's one of the sign before the internal SD goes belly up
AllGamer said:
oh crap! please let it not be the same problem as in the SGS i9000m
that's one of the sign before the internal SD goes belly up
Click to expand...
Click to collapse
Didn't they switch the type of flash memory used from earlier Galaxy S phones? I saw some discussion about it not being movinand any longer, or at least some sort of physical difference between what the NS has vs the SGS line.
distortedloop said:
Why are you bothering with apps2sd? The Nexus S shares the Galaxy S line's hugh, I mean HUGE, 1GB of "disk" space for apps. I've got almost 100 apps on my phone and not a hint of low space. See the screen capture I've attached: 284mb used for apps, 724mb still free!
Click to expand...
Click to collapse
Haha this may be the case, but I've inherited the habit of obsessively moving apps to sd/usb from using my Nexus One. Combined, I am using about 450MB of space for my apps at the moment. But this is a huge improvement from the Nexus One.
DumbUglyDragon said:
Haha this may be the case, but I've inherited the habit of obsessively moving apps to sd/usb from using my Nexus One. Combined, I am using about 450MB of space for my apps at the moment. But this is a huge improvement from the Nexus One.
Click to expand...
Click to collapse
Oh yes, I was the same on my N1 and even EVO 4G, but once I got a Galaxy S, never even considered it.
I'll wager the nand used for the "rom" space is faster than the nand for the "sdcard", another thing to consider. You're not even half-way used up with that 450...
americancrew said:
Problem 1:
I've just rooted my nexus-s and I'm not sure whether it's due to rooting or a software conflict with apps installed on the device that's not compatible with android 2.3, but I'm experiencing quite a frequent phone reboot while I am in the middle of an active call.
Is there a way to capture the log of the phone's function and see what's causing the reboot?
Are anyone experiencing this problem as well?
Click to expand...
Click to collapse
I haven't rooted my Nexus S,but i've experience the same soft reboot during call.
I have the "End call using power button" option enabled. Im not sure if i was leaning on the button when it happened, but stock doesn't have a reboot option, so its unlikely. I suspect its a OS bug, rather than a rooting issue.
Let me know if you make any progress, i've since made calls with no problems.
Psosmith82 said:
Im having the same phone reboot problem as you during phone calls. I thought it was due to an app called Screebl being incompatible, but i just made a test call and it rebooted after about 18 minutes. Im going through my apps to see what else effects the phone state during phone call.
Ive heard of some people having problems with google maps causing problems during phone calls, or sprint nav (but we dont have sprint nav) So im going to try shutting down maps, and uninstalling my task killer, which i also heard can cause problems.
Have you been able to figure anything out? I really dont want to have to reset my phone and lose all my save data information from my games. My phone is not rooted, and i dont plan on rooting yet, so i cant use titanium backup for my data.
Phone only Reboots during active phone call, i can play games or surf the web on it all day long with no reboots.
So software issue in android 2.3, or some kind of app incompatibility im thinking
Click to expand...
Click to collapse
You know, I thought there were software incompatibilities too at the first place. I did not use "End call using power button". But after running the same stock rom with rooting and apps for a week, I didn't see the soft reset during the phone call. I have just installed a new rom on my nexus s, the R2 version of MoDaCo Custom ROM for the Samsung Nexus S. Running great so far. No soft resets.
** Edit **
Actually, after posting this post yesterday, I did experience another soft reset whilst talking on my phone. I have the same apps that I have been running in the background, mainly: google pinyin, paypal, k-9 mail, ebay, rhapsody, google voice, bluetooth share, and swype. I am not experience the soft reset in all calls, after I have installed the R2 version of MoDaCo Custom Rom. I will post any problems again if I do see this happening again.
I did a factory reboot/restore and that seemed to take care of the soft reset during call problem.
Have made several calls without issue
Its doing it again, this phone is going back. The screen coating is already wearing off as well. Hopefully number 2 will be better.
I have yet to get one android phone that hasnt had to be exchanged once. Android phones really need to have better QC before leaving the factory.
Droid 1: 3 times (keyboard, GPS problems)
Evo: 4 times (terrible screens)
epic: 1 time (Keyboard)
Nexus: 1 time (so far) Screen Coating, Constant Reboots
Phone reboots itself during an active call.
I have been experiencing this problem and it seems to escalate in frequency. I got this Nexus S on day one when it came out. However, I have not experienced soft reboot issue until last week, after the OTA update. Since then, it keeps doing it more and more and now it's like almost every active call I make. First, I thought it's software conflict. Now, having read this whole thread, I think it's an OS issue.
I also sometimes encounter with completely losing signal. The phone can not register to any network, and I have to reboot.
One more issue is the voice search apk sometimes activates itself when I shake or move the phone.
My phone is stock, and I do not have any issue with USB storage.
I like the phone for its speed, and the contour screen. It handles most tasks very quickly, even it's still a stock phone, unrooted.
I still have it until Jan 14 to decide whether I will keep it or not. Hopefully, there are some ways to fix these issues.
Mine is restarting during calls and also when not in use. It restarted 3 times during calls within 10 days, and I witnessed it restarting by itself at least once when the phone was locked and not in use.
I have an unrooted Nexus S, which I started using yesterday. The OTA came almost immediately after setting up, so I installed that. It appeared to be working flawlessly until this evening when I made the first call on it. It rebooted a few minutes into the call. After redialing it did it again, the third call I ended without problem, but was shorter than the previous two. A few mins later I made some test calls and it rebooted during both of them.
I did a factory reset and wipe of USB storage - I didn't bother adding my Google account and just made a test call which lasted 13 mins before I hung up.
I'll have to make some more calls tomorrow and if they work, I'll try adding my Google account and restoring stuff.
I had this same thing happen to me quite a few times reboot during a call or locking up after a call. I work to a company and we purchased three phones. So I switched with another one and guess what? Same problem definitely looking like a software problem.
This just happened to me for the 1st time a little bit ago. About 35 mins into the call/conversation, phone rebooted itself. Non-rooted here, I hope it's a software issue, that can be corrected within the next OTA update.
Are the spontaneously rebooting phones possibly overheating? Do they feel warmer to the touch than normal when it happens?
distortedloop said:
Are the spontaneously rebooting phones possibly overheating? Do they feel warmer to the touch than normal when it happens?
Click to expand...
Click to collapse
While I cannot speak for anyone else having this issue, in my case - no. The phone didn't get warmer, or seem to overheat. Odd issue to say the least.
Stock ROM (2.3.1) here as well. Just had it reboot 10 minutes into a call, then one minute into the following call to apologise for the first dropped call!
Hello all,
I have tried searching this forum and have found various similar threads but none quite the same.
I used to use the gps on my hd2 quite a lot, both in windows mobile running copilot, and in android with google maps. But recently, I can no longer use it. If i open google maps or navigation i will get anywhere between 2 seconds and 2 minutes and then the phone will freeze completely, even if i dont use anything just having the program running is enough. I installed gvSIG mini maps and that does not work well either, it either freezes or simply never returns any search results.
The thing that is making me feel it is possibly hardware related is that it worked perfectly for a long time, the phone is about 18 months old now. I have tried various roms (the one i am using just now is Android 2.3.4 - HyperDroid-CM7-v2.1.0-HeadyHoneybadger) and it makes no difference; with the exception of the gps/maps the phone is very stable and I am perfectly happy with it. I have tried using setcpu to lower the processor speed in case this was being caused by heat, but no difference. I am considernig reinstalling a Windows Mobile build and testing the gps from there.
Any thoughts?
Regards
Stuart
quite probably just an android issue, go back to winmo6.5 and see if it does it then, if it does hardware if it doesnt you know its android
I would agree with what Richy99 said to go back to Windows 6.5 and check. I am currently on the same Pongster build you are on and do not experience any freezing of the phone you describe. In fact, I am using an optimized gps.conf file for my area and get locks in 2-20 seconds from a cold start now and used the gps navigation for hours while traveling without issues. I suspect it is something hardware related.
Thanks for the responses.
So, I reinstalled Windows Mobile 6.5 downloaded from the HTC website. Clean install, opened google maps, seemed ok for a few minutes, then i went into the menu and ticked 'Use GPS', then it worked maybe a minute and froze up completely and the phone restarted. tried this about half a dozen times got maximum a minute use each time.
Given that the phone is always pretty stable except when trying to use gps/maps, I would guess that the hardware fault lies in that part of the phone. How long as HTC warranties? The phone is 16 months old now so it doesnt look good but never mine
Will contact HTC on the off chance anyway!
Cheers
Stuart
Small update, contacted O2 and they gave me a freepost address to send it back to for repair (a company called A NOVO i think it was), about a week later I got it back, they enclosed a letter saying that they have replaced the main circuit board inside the phone. So, same old case, scratches and all, but its like a new phone, new IMEI number and everything, normal service resumed! Full marks to O2 customer service and the repair company.
Richy99 said:
quite probably just an android issue, go back to winmo6.5 and see if it does it then, if it does hardware if it doesnt you know its android
Click to expand...
Click to collapse
prob 70-80% of HD2 Android users getting this freeze problem.
this is reply i just sent to another thread....:
http://forum.xda-developers.com/showthread.php?t=1088693&page=3
Well, I been having the freeze issues with namd forever, with every build, every sd card etc....especially if i turn gps or data on or both.
So, for last 36 hours, i thought i'd do a lil simple test.
Downloaded win mobile stock ROM......36 hours stressing the heck outta my phone, toggling everything on and off etc. guess what...NO FREEZE.
So, in my opinion, 100% NOT hardware, definitely Android hd2 related.
Matt