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.
Hey guys!
I've got 2 of the T-Mobile HD2 handsets, both 'yellow reset button' revisions. One runs Windows Mobile 6.5 (have yet to find an alternative for texting through Outlook/Exchange), the other running some flavor of Android. This setup has been working just fine for months, but last month I started experiencing random restarts, sleep death, and charge death. In two known instances, this happened during calls.
Now having been educated on How to ask a question properly, I have done my best to attempt all the due diligence I could muster...
--The Android handset is presently running the Nexus ICS 1.5 ROM with the Dormanix ICS kernel. After the first few random restarts, I tried it with the regular kernel (tyung's?) and had the same issue. I then reverted to my mainstays of Typhoon Cyanogen and Hyperdroid, both with stock kernels, both demonstrating the same issue after the first day or two.
--I've tried every radio release from 2.10-2.15, being careful to only install the '50' releases, not the '51's. None of these have alleviated the issue.
--I used setCPU to try overclocking, underclocking, then just set it back to stock and uninstalled setCPU.
--The most recent format attempt, while I didn't task29, I did format /system and /data from within CWM.
--Also with the most recent attempt, I didn't install any backup software or create any backups, except with text messages through GoSMS. I did not restore any backups with Titanium Backup or MyBackup Pro.
--I have not uninstalled any system apps with ROM Toolbox.
--I have tried updating my CWM install version to 5.x.
--I have attempted switching the OSes of the two handsets; both have had the same issue with Android but neither have SoD'd with Windows Mobile.
Just about the only thing I haven't tried was switching the the cLK bootloader instead of MagLDR; my logic for not doing so is that I do keep an archive of all the old versions of the ROMs I've installed so that, in cases like these, I could try some older known-stable-to-me releases, and all the ones I've downloaded were for MAG. Additionally, none of the other threads I read indicated that the seemingly mature MAG platform was found to be the cause of anyone else's issues; all the other threads seemed to relate to either titanium backup restoring something in an extremely wonky manner, or an unstable/incompatible release of the baseband firmware.
The only other thing I could think of that could cause the issue that started roughly around the time that this problem started was my use of LBE Privacy Guard. I'm hesitant to blame LBE for the following reasons:
1.) LBE has been perfectly stable on my Incredible 2.
2.) LBE hasn't been blamed for any of the other SoD issues discussed in these threads.
3.) The Google Play page for LBE indicates no such issues reported in either the dev writeup or the first five pages of reviews.
4.) The SoDs don't seem to coordinate with the times that LBE blocks things.
5.) Uninstalling didn't make the issue go away.
However, given the nature of LBE and the kind of low-level access it gets to the system, I felt it worth mentioning.
Thanks for reading my lengthy plight; any assistance (including thread links if I missed a thread in my searches) would be greatly appreciated. In the meantime, I'm going to give Task29 and installing CLK a try.
Joey
Okay, after reading your question/issue thoroughly, it seems that you have tried almost everything but to no avail.
First thing I noticed was, " I started experiencing random restarts, sleep death, and charge death"
This may indicate bent battery pins, or just a faulty battery.
(Have you tried a different battery? Checked the pins?)
Have you tried going to complete stock and using your phone normally? If yes, did you experience any restarting, sleep death, charge death or any kind of issues? If not, do so.
Have you ever had your device stuck while flashing something? radio ? bootloader ? and you had to remove battery?
Have you ever felt that your device is overheating or lagging a lot ?
Have you ever dropped your device ? Had something spilled on it? ( This may seem a weird question, but ... you never know )
Marvlesz said:
Okay, after reading your question/issue thoroughly, it seems that you have tried almost everything but to no avail.
Click to expand...
Click to collapse
I do my best to walk all the beaten paths before I ask for help. If I'm going to ask everyone else to spend their time helping me out, the least I can do is demonstrate that solving the issue is worth my own time.
First thing I noticed was, " I started experiencing random restarts, sleep death, and charge death"
This may indicate bent battery pins, or just a faulty battery.
(Have you tried a different battery? Checked the pins?)
Click to expand...
Click to collapse
I've got five different batteries I rotate regularly. Two do admittedly need replacing, but the batteries all work perfectly in the WinMo handset. Additionally, I've had instances where I've been playing Robo Defense, and while it won't respond to input until it does its reboot, the game still carries on with the screen fully lit. However, the issue doesn't appear to be related to a capacitive touch screen failure, since a known unresponsive screen has ALWAYS been met with an restart, given enough time, and a battery pull ALWAYS returns it to proper working order.
Have you tried going to complete stock and using your phone normally? If yes, did you experience any restarting, sleep death, charge death or any kind of issues? If not, do so.
Click to expand...
Click to collapse
If you're talking stock as in WinMo 6.5, then 'yes' in the sense that the issue first started on the first HD2 (we'll designate it "Alpha"), which was running Android, while the second HD2 ("Bravo") was runing WM. Since I too wondered if it might be a hardware/bootloader/whatever issue, I task29'd both phones and made Alpha run WM and Bravo run Android. Alpha, which would SoD regularly with Android, has never done so with WM. Bravo, which never had an issue with WM, SoD's with Android. Having both phones at my disposal has enabled me to pretty reasonably conclude that it's something to do with Android and rule out a hardware issue.
Have you ever had your device stuck while flashing something? radio ? bootloader ? and you had to remove battery?
Click to expand...
Click to collapse
The closest I had to that was a radio revision whereby the bootloader never got past the 'loading' prompt, but neither that, nor the MagLDR install, nor any of the radio installations I've tried have required a reflash due to a botched installation attempt.
Have you ever felt that your device is overheating or lagging a lot ?
Click to expand...
Click to collapse
If you're a fan of the SyFy Channel series "Warehouse 13", reading this question felt like being asked, "did you smell anything that you'd describe as smelling like fudge?". That being said, I've occasionally noticed it, but it's never seemed to be correlated to a reboot/SoD. Usually graphics intensive apps or GPS navigation will do it, but that's been mostly consistent ever since I owned an iPhone 2G. If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Have you ever dropped your device ? Had something spilled on it? ( This may seem a weird question, but ... you never know )
Click to expand...
Click to collapse
Not weird, perfectly understandable, and I'm pretty good with keeping my gear unsmashed
Hope it helps!
Joey
voyager529 said:
Additionally, I've had instances where I've been playing Robo Defense, and while it won't respond to input until it does its reboot, the game still carries on with the screen fully lit. However, the issue doesn't appear to be related to a capacitive touch screen failure, since a known unresponsive screen has ALWAYS been met with an restart, given enough time, and a battery pull ALWAYS returns it to proper working order.
Click to expand...
Click to collapse
Have you checked your pins? Swapping batteries make them vulnerable.
Also, I have never ever had a non responsive screen. So this may, JUST MAY, have something to do with a hardware related issue.
voyager529 said:
If you're talking stock as in WinMo 6.5, then 'yes' in the sense that the issue first started on the first HD2 (we'll designate it "Alpha"), which was running Android, while the second HD2 ("Bravo") was runing WM. Since I too wondered if it might be a hardware/bootloader/whatever issue, I task29'd both phones and made Alpha run WM and Bravo run Android. Alpha, which would SoD regularly with Android, has never done so with WM. Bravo, which never had an issue with WM, SoD's with Android. Having both phones at my disposal has enabled me to pretty reasonably conclude that it's something to do with Android and rule out a hardware issue.
Click to expand...
Click to collapse
From the redded part, I can understand that the issue started on Alpha, and soon thereafter it had affected Bravo.
This could mean that it is a thing shared between the two devices, a thing you do/use on both devices.
Maybe an sdcard ? Have you tried booting android from sd? have you tried booting android from NAND without an sdcard?
voyager529 said:
If you're a fan of the SyFy Channel series "Warehouse 13", reading this question felt like being asked, "did you smell anything that you'd describe as smelling like fudge?". That being said, I've occasionally noticed it, but it's never seemed to be correlated to a reboot/SoD. Usually graphics intensive apps or GPS navigation will do it, but that's been mostly consistent ever since I owned an iPhone 2G. If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Click to expand...
Click to collapse
lol, okay then, it's not the device overheating.
Let's narrow it down, your both devices started to have charging/screen issues. With a relatively close time from each other.
Now, there is something bugging me. If Bravo was on WinMo, and you said you have had no issues on WinMo whatsoever, how did you know that the it was is experiencing the same issues?
(If your answer is going to be "Because I put android on it" , then the issue probably originated from the way you flash android.)
You also said that: on Winmo, both devices ran fine and on Android both devices had SoD's .
This may mean, the ROM you are/were using is simply malfunctioning. Have you tried various ROMs or it is just one ROM ?
Sorry for being late, awaiting your reply
Have you checked your pins? Swapping batteries make them vulnerable.
Also, I have never ever had a non responsive screen. So this may, JUST MAY, have something to do with a hardware related issue.
Click to expand...
Click to collapse
Ironically, Bravo (the one presently running Android) was warranty replaced less than a month ago due to an actual, legit unresponsive screen. The fact that the pattern is consistently "screen stops responding/SoD/CoD -> hot reboot -> phone resumes working perfectly", and has been on both phones, leads me to put that particular explanation towards the bottom of the pile. Rather selfishly, the supplemental reason to that is that T-Mo isn't going to honor a warranty replacement for an issue that only happens on an operating system that is an unofficial port, so if it is some bizarre hardware issue, it's gonna be mighty expensive to get the phone swapped.
This could mean that it is a thing shared between the two devices, a thing you do/use on both devices.
Click to expand...
Click to collapse
I have a thought about that that I'll get to in a moment...
Have you tried booting android from sd?
Click to expand...
Click to collapse
No. good catch =)
have you tried booting android from NAND without an sdcard?
Click to expand...
Click to collapse
I always use the NAND methods, but data is a bit hard to store without an SD card. You have inspired me to do a MicroSD shuffle though. I'll give that a try.
Now, there is something bugging me. If Bravo was on WinMo, and you said you have had no issues on WinMo whatsoever, how did you know that the it was is experiencing the same issues?
(If your answer is going to be "Because I put android on it" , then the issue probably originated from the way you flash android.)
Click to expand...
Click to collapse
That is, in fact, the answer lol. Originally, Alpha ran Android and Bravo ran WinMo. This problem started, so I switched them around: Bravo was configured to run Android, and Alpha became the WinMo phone. Alpha, which would SoD with Android, has not done so in the weeks since it became the WinMo running handset. Bravo, now sporting Googleware, exhibited the same issues.
To answer your last question regarding whether it was the ROM, I tried the ICS ROM with stock kernel, Dormanix's kernel, Typhoon CyanogenMod (the most reliable in my experience), and HyperDroid. All of these ROMs did the same thing after the first day or two, but hadn't done so in the past: I used both the latest release and older releases that I've used and am 100% certain have worked for me, on my hardware, without fail. As such, this is starting to ratchet back to being a PEBKAC/ID10T issue, but I was never able to pinpoint anything specifically that would earn me a dunce cap. This morning though, I had a breakthrough...
Yesterday, I decided to ditch MAGLDR and opt for CLK instead. I must admit that I do greatly prefer MagLDR, but I was determined to try as many things as possible to get to the bottom of this. I Task29'd, got CLK in along with CWM Recovery, Flashed the ROM again, and started restoring apps from the Google Play Store. No reboots at this point, but then again, most flashes have worked wonderfully the first day. As an aside, I'm torn: I do like the greatly decreased boot time and increased internal storage availability, but MagLDR was much simpler to work with for frequent flashing chores. Oh well.
The stock lock screen gives me a camera launching option by dragging the unlock icon to the left. Being left handed, on more than one occasion I've ended up getting myself to the camera by accident because the side of my palm triggered the multitouch. As such, I did a little experiment. Using ROM Toolbox, I 'froze' the camera app; I never use it intentionally anyway. After doing so, I was curious as to how the lock screen would react. Behold! I finally found a way to consistently trigger a restart! This got me thinking two things:
1.) As much as I like taking out things like the stock news/weather/twitter apps that I never, EVER use, maybe one of those were being randomly restarted (as Android apps tend to do), and instead of giving up on starting the app, my phone instead decided to divide by zero.
2.) The utility of Advanced Task Killer and its ilk have been hotly debated in Android forums. Personally, I find ATK to be extremely useful and love its functionality. As such, it's among the first things I install. Hence, I wonder if, for some bizarre reason, ATK is either killing the wrong task, or its presence is wreaking havoc.
Thus, I have foregone MagLDR, foregone ATK, and foregone pulling out stuff in ROMs I don't want. Also, I bought the GOTO lockscreen to help me get rid of the camera launching problem. So far, my system uptime is 6 hours, 14 minutes
Joey
voyager529 said:
The stock lock screen gives me a camera launching option by dragging the unlock icon to the left. Being left handed, on more than one occasion I've ended up getting myself to the camera by accident because the side of my palm triggered the multitouch. As such, I did a little experiment. Using ROM Toolbox, I 'froze' the camera app; I never use it intentionally anyway. After doing so, I was curious as to how the lock screen would react. Behold! I finally found a way to consistently trigger a restart! This got me thinking two things:
1.) As much as I like taking out things like the stock news/weather/twitter apps that I never, EVER use, maybe one of those were being randomly restarted (as Android apps tend to do), and instead of giving up on starting the app, my phone instead decided to divide by zero.
2.) The utility of Advanced Task Killer and its ilk have been hotly debated in Android forums. Personally, I find ATK to be extremely useful and love its functionality. As such, it's among the first things I install. Hence, I wonder if, for some bizarre reason, ATK is either killing the wrong task, or its presence is wreaking havoc.
Click to expand...
Click to collapse
lmao !! xD
But that is weird. Why would your phone reboot when the app is frozen ? When you freeze an app, it disappears from the app launcher, but being available on the lockscreen may be the cause.
I don't think it's ATK, since I was on the SD versions of Android, I used to use ATK. And never had a problem. On the other hand, I did notice some random reboots on ICS after freezing some system apps with Titanium Backup.
That said, these reboots shouldn't occur when on typhoon, Hyperdroid or any non-ICS ROM, should they ?
I'm still confused about this "Originally, Alpha ran Android and Bravo ran WinMo. This problem started"
There is no way in hell, two separate devices, would face the same issue without any relation.
And, forgive me but, if the problem only occurred on Alpha, why did you put Android on Bravo while it was working fine? (Again, sorry, but I need an answer for this )
Update: The phone froze twice yesterday, but has been fine since...wait, literally just rebooted as I was typing this after I hit the 'home' key.
I'm thinking that at some point early next week, I'll try task29ing again and put typhoon on there with no task killer and no alternate launcher and see if I get anywhere.
To answer your question, the problem started on Alpha. As a desktop computer tech, when a desktop has issues like this, it tends to be faulty RAM. Since phones don't have user-swappable DIMMs, I wanted to rule out a hardware issue. Alpha has been running WinMo 6.5 flawlessly ever since, which leads me to believe that it is, indeed, a software issue of some kind.
Joey
voyager529 said:
Update: The phone froze twice yesterday, but has been fine since...wait, literally just rebooted as I was typing this after I hit the 'home' key.
I'm thinking that at some point early next week, I'll try task29ing again and put typhoon on there with no task killer and no alternate launcher and see if I get anywhere.
To answer your question, the problem started on Alpha. As a desktop computer tech, when a desktop has issues like this, it tends to be faulty RAM. Since phones don't have user-swappable DIMMs, I wanted to rule out a hardware issue. Alpha has been running WinMo 6.5 flawlessly ever since, which leads me to believe that it is, indeed, a software issue of some kind.
Joey
Click to expand...
Click to collapse
I don't know if it was just me not reading this whole thing properly (which it probably was, given the amount of information you're providing) but you never seemed to have actually answered the questions about bent battery pins. You mentioned that you are often swapping batteries which makes the battery pins vulnerable to being unintentionally bent out of shape, and they may not be making contact with the battery properly. I have no clue as to how this would really help you (maybe the reboots, not the screen issue), but it wouldn't do any harm to check it out
---------- Post added at 02:54 PM ---------- Previous post was at 02:51 PM ----------
Marvlesz said:
And, forgive me but, if the problem only occurred on Alpha, why did you put Android on Bravo while it was working fine? (Again, sorry, but I need an answer for this )
Click to expand...
Click to collapse
Didn't see this earlier, but surely the question is 'why would you leave the HD2 on the world's worst OS?'
I'm disinclined to believe it's the battery pins for the following reasons:
1.) in certain cases, the screen is unresponsive, but the send/end buttons light up, indicating that power is indeed flowing.
2.) in certain cases, I've had the phone do a 'hot restart' (i.e. not going through the bootloader, just showing the boot animation) mid phone call or during other kinds of use. If it was a momentary disconnect, wouldn't it be doing a complete, cold restart?
As for why I'm using Windows Mobile, two reasons:
1.) Android has been giving me issues lately, as this thread clearly illustrates. For all the crap Windows Mobile 6.5 gets, it's been pretty stable, ALWAYS rings, is significantly less demanding on battery life.
2.) Its killer feature for me is that it enables text messaging through Exchange/Outlook 2010, something no other mobile OS presently provides. Additionally, it does all of the core phone functions I use (calls, texting, tethering, web browsing with Opera Mobile, Facebook notifications/caller ID sync, USB mass storage, video/music playback, Swype input, etc.). It might not have 100,000,000,000,000 apps, but the Sencity flavor of EnergyROM is extremely reliable.
Joey
voyager529 said:
If you're going for "the CPU is being pegged" as a cause for the SoD, I'll be a bit more vigilant as I use it to see if a heat issue seems to trigger it, but my immediate reaction is "no".
Click to expand...
Click to collapse
Even if you can't feel it overheating, try putting it in a cool place for some time until you can feel that the aluminium back cover is cold to touch, then do something which would normally cause a hot reboot or any other issue. An open window with a slight breeze is normally good enough to cool the phone down (so long as it isn't too sunny or hot obviously).
I guess you're right about WinMo being the most stable OS (although from what I've heard WP7 is very good as well) but I just couldn't live with it. Even if I started experiencing large issues I would do everything in my power to not use that OS again! Used it the other day on my friend's HD2 which he now keeps purely as an alarm clock and it's ghastly, I found it painful to use again.
voyager529 said:
I'm disinclined to believe it's the battery pins for the following reasons:
Click to expand...
Click to collapse
Will checking the battery pins trigger a bomb ? Why don't you just CHECK THE PINS to eliminate all the doubt. Instead of the assumptions you keep making !
And do what Nigel has said, and report back.
Marvlesz said:
Will checking the battery pins trigger a bomb ? Why don't you just CHECK THE PINS to eliminate all the doubt. Instead of the assumptions you keep making !
And do what Nigel has said, and report back.
Click to expand...
Click to collapse
I apologize for my earlier lack of clarity.
I did check the pins for any obvious bending or lack of pressure, and they all appeared to be correctly shaped and pressured. As a result, I'm hesitant to blame it on the pins' shape and pressure at a micro level because of the reasons below - if the pins are bent in such a manner that it's undetectable by me personally but causing the problems in functionality, I wouldn't expect it to happen mid-call or mid-game.
In the none-too-distant future, I do intend on doing another task29 and going back to MagLDR and trying a previously untried ROM. Also, I have ordered new batteries, in the event that it's the physical batteries themselves.
I'll report back with what happens, and again, than you so much for all of your help.
Joey
voyager529 said:
I apologize for my earlier lack of clarity.
I did check the pins for any obvious bending or lack of pressure, and they all appeared to be correctly shaped and pressured. As a result, I'm hesitant to blame it on the pins' shape and pressure at a micro level because of the reasons below - if the pins are bent in such a manner that it's undetectable by me personally but causing the problems in functionality, I wouldn't expect it to happen mid-call or mid-game.
In the none-too-distant future, I do intend on doing another task29 and going back to MagLDR and trying a previously untried ROM. Also, I have ordered new batteries, in the event that it's the physical batteries themselves.
I'll report back with what happens, and again, than you so much for all of your help.
Joey
Click to expand...
Click to collapse
Ah, OK thanks for clearing that up (I, like Marvlesz, thought you simply were refusing to check the battery pins for some odd reason). Did you try the fridge trick? I've read in many places that it works for some people, maybe it could help you too (although don't leave it in there for too long; I'm no expert but I would assume phones aren't designed for that ) and report back.
Just thought I'd follow up with everyone...
On April 22, I task29'd, MagLDR'd, and installed HyperDroid-CM7-Observant-Opossum -v5.9.0. Since then, my phone has been working properly.
Thus, I am chalking the whole ordeal up to one of three things:
1.) an issue with a backup of some kind.
2.) an issue with the internal memory that I managed to 'partition around' when I installed MagLDR again.
3.) an issue with ICS/kernel compatibility that was unique to my phones for some odd reason.
Regardless, for the past ten days, the only reason I've had to reboot the phone was due to a dead battery. Thank you everyone who watched this thread and helped me with my issue. I am greatly appreciative of your willingness and patience.
Joey