Weird Lag, Sense restart(no FC) then Hot Restart issue - I can reproduce it - EVO 4G Q&A, Help & Troubleshooting

Have a VERY weird issue going on. I've been using Burnt Droid 1.4.2 by Netarchy since it came out. I decided to flash his new 4.3.4 CFS-NoHavs,noSBC, with static undervolt (i wanted to try and see if it was stable since I had success using undervolted kernels last year). I used proper procedure and cleared cache/dalvik-cache before flash. I downloaded the new Angry Birds from amazon and started playing it for a few minutes phone started lagging very bad, then had to restart. I said forget this; undervolt is probably causing this, and reverted back to the original 4.3.1-cfs-nohavs-nosbc which I never had a problem with(used proper procedure above to flash back kernel as well).
Now a day later at night, I decide to run my phone down because I'm trying to recalibrate my battery(I'm at less than 10% at this point). So I load up Wifi, turn on Pandora, and browse the internet. Not even 5 minutes into it, here's whats occuring in order:
1) Bad lag.. Pandora starts stuttering, so I hit the home button
2) HTC Sense restarts, It doesn't even force close, or at least it's not telling me
3) a Hot restart occurs a few moments later... (no white boot screen, just starts bootin from ROM screen)
4) At this point, sometimes its still laggy, sometimes it's fine. If it's laggy I must do a battery pull because It will keep looping to this point.
I can rinse and repeat this running pandora + browsing the web, and the same 4 steps above will happen within moments of eachother. I've been using this ROM since January with no major problems like this
A few side notes:
-I have Evo hardware 0002 (launch day evo)
-Rooted with Toast's original root method, eng .76 boot loader
-Newest radio/PRI/NV/Wimax
-My phone does not randomly reboot on me normally. Reboots only occur when following the above steps.
-I do not use Set CPU
Here is where I am very superstitious. I've been closely monitoring the "Boot looping + no Recovery Access" forum, and similar forums to this. Within the past few months I have tried out a few different CM7 nightlies. I have never flashed RC2 but I have flashed some after and before and tried those out for a while. I just hope my phone isn't starting a dying phase in relation to the problems people are having now.
Is there anything else recommended before I end up doing a full wipe and reflash the rom?

bigblueshock said:
Have a VERY weird issue going on. I've been using Burnt Droid 1.4.2 by Netarchy since it came out. I decided to flash his new 4.3.4 CFS-NoHavs,noSBC, with static undervolt (i wanted to try and see if it was stable since I had success using undervolted kernels last year). I used proper procedure and cleared cache/dalvik-cache before flash. I downloaded the new Angry Birds from amazon and started playing it for a few minutes phone started lagging very bad, then had to restart. I said forget this; undervolt is probably causing this, and reverted back to the original 4.3.1-cfs-nohavs-nosbc which I never had a problem with(used proper procedure above to flash back kernel as well).
Now a day later at night, I decide to run my phone down because I'm trying to recalibrate my battery(I'm at less than 10% at this point). So I load up Wifi, turn on Pandora, and browse the internet. Not even 5 minutes into it, here's whats occuring in order:
1) Bad lag.. Pandora starts stuttering, so I hit the home button
2) HTC Sense restarts, It doesn't even force close, or at least it's not telling me
3) a Hot restart occurs a few moments later... (no white boot screen, just starts bootin from ROM screen)
4) At this point, sometimes its still laggy, sometimes it's fine. If it's laggy I must do a battery pull because It will keep looping to this point.
I can rinse and repeat this running pandora + browsing the web, and the same 4 steps above will happen within moments of eachother. I've been using this ROM since January with no major problems like this
A few side notes:
-I have Evo hardware 0002 (launch day evo)
-Rooted with Toast's original root method, eng .76 boot loader
-Newest radio/PRI/NV/Wimax
-My phone does not randomly reboot on me normally. Reboots only occur when following the above steps.
-I do not use Set CPU
Here is where I am very superstitious. I've been closely monitoring the "Boot looping + no Recovery Access" forum, and similar forums to this. Within the past few months I have tried out a few different CM7 nightlies. I have never flashed RC2 but I have flashed some after and before and tried those out for a while. I just hope my phone isn't starting a dying phase in relation to the problems people are having now.
Is there anything else recommended before I end up doing a full wipe and reflash the rom?
Click to expand...
Click to collapse
I'm not really sure what's causing your problem, and If i was in your situation, I'd most likely do a complete wipe, including calkulin's format all, and either restore a good nandroid, or reflash the rom from scratch.
That said, I don't believe CM to be 'dangerous' to run or anything like that. Yes, it is odd that an increasing number of people are reporting somewhat major issues, with boot looping the splash screen, and being permanently stuck there. However, that doesn't mean CM is the cause. It does seem to be a common denominator in the people that this has happened to, but there are soooo many other variables that come into play with something like this. There is no proof that CM caused it, but it does seem odd that everyone it happened to was running CM. Also, I'm sure there are thousands of CM users, and a select 8-10 people have reported these issues on here. That's a very low percentage, overall. With all that said, I myself won't be running CM in the near future, either until it's confirmed or denied that it has anything to do with these issues. I'll just be playing it safe, just in case.

I'm stock everything, no root or mods and it restarts at the 4g screen skips everything else...
Sent from my PC36100 using XDA Premium App

I think I will do the format all and completetly wipe it and reflash the rom from scratch. Thank you!

Related

[Q] DINC Random Reboots

Although I have been doing a lot of reading the last few months, I am new to posting, so please bear with. My DINC just started randomly rebooting about 2 weeks ago and I am trying to figure out why. It was running great before with (rooted) Skyraider 3.0 RC3 Vanilla, kings BFS#5, S-Off, 2.15 radio and HBoot .79. The problems began when I installed Juice Defender, didn't really like it, and then un-installed it. I did not disable anything JD did before un-installing. Now, with the same set-up as before, I get random reboots when I'm on Explorer for a few minutes, when GPS Navigation is on, and then randomly on GChat and the Market. It seems to happen more when the temp is higher, but it's rarely over 100 degrees F. Half of the reboots end up in QualComm debug mode. I have tried a full wipe and reinstalling the ROM, kernel and prior settings. The only thing I can think of is that Juice Defender changed some type of setting, application or system, and now it's having fits. I downloaded aLogCat and had it running during the last reboot and can PM the .txt file if you think that would help. Does anyone know what's going on or how I can fix it? Any help is great appreciated!
Also, the current applications that I have are:
ad-free
advanced task manager
beautiful widgets
setCPU
amazon reader
scorecenter
Mint.com
switchpro
bump
battery indicator
astro
root explorer
rom manager
barcode scanner
facebook
goggles
dspmanager
handcent
linpack
metamorph
mixing
papertoss
pandora
shazam
spare parts
tapatalk pro
titanium backup
weather channel
widget locker
BUMP....anyone?
mjmdmd said:
BUMP....anyone?
Click to expand...
Click to collapse
Are you overclocking? Some phones can't handle much and it's known to cause similar problems. Other than that I'm not sure if anything JD changes would remain once it's un-installed; but if so you might install it again, change everything back to stock, then un-install it. Just a guess, hope you get it figured out
I'm pretty sure the DINC has rebooting problems.
What version do you have, SLCD or LED?
I've had the LED version since it's released and I just started getting random reboots last month or so. Sometimes it goes into fits and just reboots nonstop for a couple hours. I've reverted it back to completely stock (unrooted, S-ON, stock recovery, stock 2.2 ROM) and I still have the same problem. Using stock battery as well. I've always cleared cache, factory reset, clear data, etc. I've done everything I can think of, but I think this phone just has problems that some people encounter even when completely stock (and even people who have never modified their phone at all if you do some searches on google).
It may have to do with the heat, I'm going to keep doing some testing. It seems like it goes into reboot fits when it gets hot or when I'm doing a lot of processing like using GPS and maps. It rarely reboots when it's idle.
SynbiosVyse said:
I'm pretty sure the DINC has rebooting problems.
What version do you have, SLCD or LED?
I've had the LED version since it's released and I just started getting random reboots last month or so. Sometimes it goes into fits and just reboots nonstop for a couple hours. I've reverted it back to completely stock (unrooted, S-ON, stock recovery, stock 2.2 ROM) and I still have the same problem. Using stock battery as well. I've always cleared cache, factory reset, clear data, etc. I've done everything I can think of, but I think this phone just has problems that some people encounter even when completely stock (and even people who have never modified their phone at all if you do some searches on google).
It may have to do with the heat, I'm going to keep doing some testing. It seems like it goes into reboot fits when it gets hot or when I'm doing a lot of processing like using GPS and maps. It rarely reboots when it's idle.
Click to expand...
Click to collapse
Same here. Exchanged it with Verizon, almost no questions asked. Got AMOLED refurb, so far so good. Replacement was with OTA installed though, so waiting for new root.
You should revert your phone to fully stock, turn S-ON, unroot, stock ROM, etc. Make it look as legit as possible. If your problems go away then obviously something got screwed up in the flashing process. If your problems remain, then it's something wrong with the actual phone, and since you just made it completely stock you're in the perfect shoes to go exchange it.
In summary, the best measure to take if you're having reboot problems is to exchange it at a Verizon store; that's what most people are doing.
I'm going to exchange mine tomorrow. It should be covered under the 1 year warranty so you should not need insurance to do it.
Just an update: I am still having random reboots after uninstalling Advanced Task Manager and Widget Locker (read in posts these can cause problems). Now even when I use Amazon reader, the phone reboots rather quickly. One thing to note is that when I turn off 3G, it hasn't rebooted. This was one of my thoughts to begin with since approximately all of the reboots occurred when I was using 3G (browser, market, GChat and Nav). Does this narrow down any problems?
Next, I am going to install the new Skyraider 3.0 (ihtfp69 said it should be out first week of Dec.) and install apps one-by-one to see if the rebooting continues. Then I guess I will have to go s-off, unroot, etc. Crossing my fingers...
Sounds to me that you have the faulty overheating 3G radio..it is a somewhat documented problem and I believe it's the same problem I have. The only solution is to swap it at a verizon store. I'm afraid other ROMs or anything else you do will not solve the problem.
mjmdmd said:
Just an update: I am still having random reboots after uninstalling Advanced Task Manager and Widget Locker (read in posts these can cause problems). Now even when I use Amazon reader, the phone reboots rather quickly. One thing to note is that when I turn off 3G, it hasn't rebooted. This was one of my thoughts to begin with since approximately all of the reboots occurred when I was using 3G (browser, market, GChat and Nav). Does this narrow down any problems?
Next, I am going to install the new Skyraider 3.0 (ihtfp69 said it should be out first week of Dec.) and install apps one-by-one to see if the rebooting continues. Then I guess I will have to go s-off, unroot, etc. Crossing my fingers...
Click to expand...
Click to collapse
Odds are your radio is failing, which is a relatively common problem. Your symptoms are pretty much a textbook example and something that I experienced firsthand on my previous Incredible. The only fix is a warranty exchange.
That's disappointing. Thanks for the info everyone. I guess it's time to start the process of unrooting...
I thought I would post my situation/solution here, although it may not have any bearing on the issues that previous posters have mentioned. I got myself a Seidio 3500mAh Extended Life Battery several months ago. The first month was good. The next 1-2 months seemed to bring decreased battery performance - I was just about making it through a day with moderately-heavy use, but this battery should be able to handle that with no problem.
Over the last month I started having random reboots and it was getting more frequent. I don't know why but I just had this feeling that the battery was coming a bit loose and losing contact occasionally, although I couldn't force a reboot by shaking it.
Just a few days ago I decided to put a few layers of paperboard (i.e., box of tissues) between the battery and the case, just to see what happened. I haven't had any random reboots since I did that and the battery life seems markedly improved.
Again, this may not be relevant for some but I thought I would post my experience in case it helps anyone.
Miltos1 said:
I thought I would post my situation/solution here, although it may not have any bearing on the issues that previous posters have mentioned. I got myself a Seidio 3500mAh Extended Life Battery several months ago. The first month was good. The next 1-2 months seemed to bring decreased battery performance - I was just about making it through a day with moderately-heavy use, but this battery should be able to handle that with no problem.
Over the last month I started having random reboots and it was getting more frequent. I don't know why but I just had this feeling that the battery was coming a bit loose and losing contact occasionally, although I couldn't force a reboot by shaking it.
Just a few days ago I decided to put a few layers of paperboard (i.e., box of tissues) between the battery and the case, just to see what happened. I haven't had any random reboots since I did that and the battery life seems markedly improved.
Again, this may not be relevant for some but I thought I would post my experience in case it helps anyone.
Click to expand...
Click to collapse
Interesting. I'm using the big batt too, but my only reboots happen with GPS. As I'm driving (unfortunately) with my Nav on, all of a sudden, I look to see what my next turn is, and I'm on the "HTC Incredible" splash screen! Most annoying thing ever.
I'm still waiting for a fix. I really don't want to unroot, lose everything, and have to exchange for a warranty phone.
By the way, with a fix like this, I feel like my blackberry days again!

[Q] HTC Desire Z Freeze During Standby Mode

Hi,
I just got a new HTC Desire Z Bell Branded (A7275) for my AT&T service. I "debrand" it using the debrand guide. I just noticed twice yesterday that when I put it in standby mode, I try to press the power button to turn off standby mode so I can get the screen to slide down to unlock the screen for usage. Well, it did not....no matter what I do...I cannot get the screen to get unlock. The screen is black as if it isn't on. I hold the power button, still nothing. Only way is for me to pull the battery out, put it back in and power it up. Is this common? What is the problem that causes this? Any help would be nice. Thank you in advance.
have you oc your phone at all? have you flashed a kernel? custom rom? and what guide did you use?
I used this guide to debrand my phone.
have you oc your phone at all?
Not a single bit, everything is bone stock regarding CPU.
have you flashed a kernel? custom rom?
I only flashed the one from the guide.
[ROM] RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M
what guide did you use?
http://forum.xda-developers.com/showthread.php?t=835777
Thanks for the fast reply and help, bahmanxda.
Tbh I am not sure what is the problem I got nothing ,the only thing that I can think of is if you are already rooted and s/off do a full wipe and flash the Rom again or try different roms if u like sense try virtuous 9.0 its really good.
Sent from my HTC Vision using XDA App
There are some others with this issue. Unfortunately, the cause has not been found, or whether it is hardware or software related:
http://forum.xda-developers.com/showthread.php?t=857584&highlight=pulling+battery
I've had this crop up myself a few times. I can say this:
Several times my Desire Z has powered off and could only be powered on after pulling the battery and re-installing. It did this twice within the first few days I owned it. Then it didn't happen anymore.
Maybe a week later I tried the Godspeed kernal (1 GHz) and SetCPU. No issues for about 2 weeks.
Then I tried CPU Tuner based on claims made by some users here that it is easier on battery life. Used a screen-off profile to underclock. The phone had the power off problem, 3 times in 2 days. Every time when the screen was off. But the random poweroffs did not start immediately after installing CPU Tuner, maybe 2 days later.
I uninstalled CPU Tuner to see if it would help (and it didn't seem to be improving battery life). Went back to Set CPU (have messed around with and without screen-off profiles). Its been more than 2 weeks, and no random power-offs.
None of this is conclusive, of course. Maybe the problem in my case was CPU Tuner, or a combination of the kernal and CPU Tuner. Maybe the things I've described are complete coincidence, and its some other factor altogether. But just thought I'd throw my experiences out there. Some claim Google Maps is the problem, but I have not found this to be the case. Or possibly some issue with the battery contacts, or the battery itself. Who knows?
Same thing happens to my Bell Desire Z. Every now and then it just decides to freeze and Only solution seems to be to take out the battery and then put it back.
Very frustrating.
Thanks for the reply, everyone. Strange it has not happen for the past 2 days now. I've read the other thread and still no exact detail on the cause of this. This is not good...especially it is my first Android phone and first HTC (bought it due to their reputation of quality made phones).
It happened twice within the first week of using the phone. Decided NOT to return the phone to observe it for a full month. During that month it happened every 3-4 days, always happens when the phone is not charging, and at the hour mark. Decided enough is enough and returned for a warranty claim 2 days ago.
During the one month, I rooted the phone after 2 weeks and flashed a custom ROM, but the problem did not go away.
There're people who aren't affected by this problem though.
I've the exact same problem here. CM 6.1.1 will just randomly black screen on standby. No response to charge when plugged in. The only way to reset is to pull the battery.
I don't think it happened on stock firmware. I'm now highly debating switching ROMs. It's getting annoying to remove the back cover every time I need to do a hard reset.
I think there is a thread in regards to CM and overclocking causing a screen on issue. But I think in those cases, the phone has power (LED and front buttons light up), just the screen can't power on. But adjusting any overclocking/underclocking profiles is worth a try.
Do you have SetCPU or CPU Tuner setup, and any profiles under those, such as underclock when the screen is off? I tried CPU Tuner for a few days, due to claims by XDA users of better battery life than SetCPU. I got 3 instances in 3 days of the phone not being able to power on (had to pull battery). I un-installed CPU Tuner, switched back to SetCPU, and haven't had the power on issue crop back up for almost a month now.
Given, I had the power on issue 2 times before using CPU Tuner, so it can't be the sole culprit. My only theory is that some combination of switching the kernel and SetCPU has solved the issue. Or it has nothing to do with those at all, just a coincidence, and is something else completely. Who knows.
It happened to me many time already. I still use stock htc desire rom and never rooted..
I've had it happen about 6 times, always requiring a battery pull. Totally stock other than being unlocked, not-rooted. But it hasn't happened for the last 3 weeks or ever since I stopped using juicedefender. Coincidence?
Desire Z freezes
Hi,
I also have some random freezes of my Stock Desire Z, I didn't do a thing on software or hardware side.
I run Android 2.2.1 Build 1.72.405.2 CL296256, provider KPN (Rabo Mobiel)
I got rid of the hangs after the upgrade from 2.2.0 then after several weeks it came back, only solvable by removing the battery.
I tried to figure out what's wrong and I think I have several clues:
- mostly some time after using Google Maps
- mostly when Wifi was on (it might be that the Wifi has limited connection and it screws up the data)
- after the reset I allways have updates from Market available
I can't remeber the Memory widget I ran, which I felt was having a good influence on the hangs.
I'm not happy with this behavioure, but cannot determine if it is hardware or software, it's not helping much that the phone just stalls , a reboot is irritating but less then a complete hangup when you don't know how long it has been in that status.
P.S. I don't run juicedefender
Cheers, Edward
I have STOCK G2 ROM.
S-off, CID, unlock via http://forum.xda-developers.com/showthread.php?t=855764
NO Cputuner or SetCpu (well I uninstalled them before these problems cropped up)
Used G2 for about a month and a bit no problems. Installed launcher pro then started to experience this problem. Coincidence? Not sure. Uninstalled and it did not help. Uninstalled several more apps that I recently loaded (skype, minimalistic text, Gtab Simi clock...) didn't help.
Wiped phone, nandroid backup to original ROM, restored using TB. Worked for a few days then just started happening again.
I also was using 2 chinese batteries I bought from eBay. Not sure if this has anything to do with it either.
// Just reflashed, HTC stock battery. Froze up within an hour. Too bad I bought this off of ebay, no warranty
// Factory Reset, restored apps and data with TB, still freezing
Hi all
I'm new to this forum (sorry, a newbie about to make a whole load of gaffs, no doubt), but I am at least fairly tech-savvy. I've had HTCs for years, right from the days of the 2000 vintage Compaq Ipaq!!
My wife & I bought two Desire Zs at Christmas, and it was therefore 50:50 which box was opened by whom. It appears I picked the dud, as I'm suffering from the issue described by all you guys, and in the other thread:
http://forum.xda-developers.com/showthread.php?t=857584
For the sake of adding more evidence to this otherwise confusing issue, I thought I'd join the forum:
So:
1) The device is not modded in any way. Standard ROM from HTC, being used on the UK T-mobile network. Currently at Android 2.2.1, Kernel 2.6.32.21-g540976a, Build 1.72.405.2 CL296256 "release-keys". This was installed on Christmas day, over the air.
2) There has been no playing with processor speeds or memory management.
3) The first crash of this nature was either on Christmas Day or Boxing day (ie the day-after-christmas-in-England); can't quite remember now, but certainly after the ROM update.
4) I have had this occur irregularly, but in increasing frequency, since that date. I think I'm probably into double figures by now, but I've only started to log them recently.
5) I was starting to think that there was some correllation with GPS applications. The phone would die after using Google Earth, for example, but not immediately. It may be after two or three standby's that it would fail to respond on the fourth, for example.
6) I had a very bad day a few weekends ago where the phone died four times in a single day. I had been using geotagging-photos (in the standard HTC camera app)... plus location-based services such as Yell and Google maps.
7) I tried keeping GPS disabled, and to be fair, there was no evidence of it crashing at that point. But I use GPS too much to make this plausible for a long time.
8) I wondered if it was due to the motion of keeping my phone in my pocket, but it died over night on the bed-side table on Monday-Tuesday, where my last usage had been the Friend-Stream widget/app. GPS was on...
During all of this, my wife's phone has not shown any of these symptoms. Whilst she uses Google Maps, Google Navigator & HTC Navigator a bit, she generally keeps the GPS turned off except for specific odd occasions. Hers has not crashed in this manner...
About to contact HTC to see what their response is...
This has occurred for me regardless of app usage.
It can occur right after a fresh reboot after being fully charged.
// Wow, I was in the middle of sending a txt and it just shut off on me...
I really wish I had a warranty on this
Hey there.
I can clearly pinpoint the problem with my desire z to the GPS. In the first view weeks I used it regularly and my phone froze, but only when the gps sensor was not active anymore (and the phone had gone to standby once or more). It didn't matter which app I used. For a while now I haven't been using GPS and my phone runs smooth as hell.
@lost800: I suppose your problem has a different kind of nature.
I already contacted HTC (very good support) and they told me to send it in to repair. I need my phone for work at the moment and I haven't found time to do this.
Due to the very small amount of ppl having that problem, I suppose it's an hardware error.
Greetz
Edit: Just out of curiosity, is there any meaning to the kernel version? Or has every mobile phone the same one?
Hello all, here is my input on this problem
My DZ has started freezing while I'm doing stuff:
* playing cards
* writting an email or a text
* using xda app
* ...
I never have GPS on. The frequency has greatly accelerated in the past 2 weeks but the weirder thing is that the last 3 times I remove sdcard and then put it back in to get the phone to boot, but it does not boot... it hangs on HTC logo for a long time (I've left it there for up to 15 minutes to see...) I eventually just remove the battery and from the phone and wait before trying to put it back in and boot...
Wait times required have varried from 5 minutes to several days.
I have observed this behavior on Stock 1.34.405, Virtuous 0.9, Virtuous 1.0.0 and back on stock 1.34.405 Today. I've wiped, flashed stock RUU nothing has helped. This puppy is going back for repair/exchange (it is 3 months old).
dwardo said:
Hello all, here is my input on this problem
My DZ has started freezing while I'm doing stuff:
* playing cards
* writting an email or a text
* using xda app
* ...
I never have GPS on. The frequency has greatly accelerated in the past 2 weeks but the weirder thing is that the last 3 times I remove sdcard and then put it back in to get the phone to boot, but it does not boot... it hangs on HTC logo for a long time (I've left it there for up to 15 minutes to see...) I eventually just remove the battery and from the phone and wait before trying to put it back in and boot...
Wait times required have varried from 5 minutes to several days.
I have observed this behavior on Stock 1.34.405, Virtuous 0.9, Virtuous 1.0.0 and back on stock 1.34.405 Today. I've wiped, flashed stock RUU nothing has helped. This puppy is going back for repair/exchange (it is 3 months old).
Click to expand...
Click to collapse
I called HTC support to see about getting the phone replaced. After explaining to the guy that it was freezing and then not rebooting when I pulled the battery out, the first thing he said was: "Did you install apps from the market ?"
Given that I replied by the affirmative he wanted me to test rebooting in safe mode and seeing if the freezes still occured before moving on to a replacement. He claimed that some market apps are not "properly coded and can mess up the phone"
I asked for and got the instructions how to reboot into "safe mode" (hit keyboard S key at HTC logo and stay on it while it boots)
In "safe mode" you can still install apps but they won't appear in the app drawer so you won't be able to start them (you can start them if they are on your home pages though ). No backgroud apps will run though (bbc, task killer ...)
Well I ran in safemode for 6 days and used the phone as I always do (work email, leisure email, web, video, camera, games, GPS, bluetooth etc...) and the darned thing ran perfectly. No freeze during those 6 days (the last few times it took less than 2 days to get a freeze).
I therefore decided it was time to test it again in "normal mode". Before rebooting I removed my task killer as for me this was "THE APP" that "safe mode" was really blocking from running on my phone...
Well It has been 2 days now and still no freeze. If it stays that way for another week I think I will have a rather good idea of who was the culprit...
Will keep you all updated and keep my fingers crossed.
Hi guys
An update:
HTC over the web-support were very helpful. Immediately they suggested that the device needed to be taken in for repair. In subsequent stages of the dialogue, they stated that the mainboard would be replaced.
A couple of weeks ago, I cleared down my device, packaged it up and waved goodbye to it (sniff...). HTC took it and...
!!DID NOTHING!!
It came back on Monday with an *old* ROM installed (1.35... If I remember correctly), and a statement saying 'no fault found'.
I've built the phone back up to where it used to be, including installing the over-the-air update to 1.72.405.2 (I need this as there's an activesync exchange bug in the old ROM) and within 24 hours, the device was unresponsive again
I have just written back to HTC to find out what the next steps are. I'd be interested to see if they suggest some debugging actions, like the safe-mode option, for example.
I've also asked them directly if their engineers have any clue what is causing this? Fundamentally, I don't see how any app should have the power to kill the device, however badly written it might be. That suggests insufficient controls/barriers in the OS.
Throughout this period, my wife's phone has continued to operate perfectly, even with some extra GPS playing to try to force a failure. So, we are now looking for any differences that could help to pin this down further. One difference is that she has never enabled the HTCSENSE.COM account on her phone, whereas I had. Perhaps there's some problem with the Phone Location functionality (in addition to the fact that I have to be in a yacht off the West coast of Africa for it to accurately show the phone's location). To test this, I've removed my HTCSENSE.COM account this morning.
Dwardo: I think your issue is slightly different, but the safe-mode info is useful.
Thanks
Andy

[Q] CM7 eventually just starts showing black screens instead of most things. Why?

This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Saturn2K said:
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Click to expand...
Click to collapse
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
bootny said:
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Click to expand...
Click to collapse
Next time it happens I will, I'm just afraid it will break Facebook/SMS integration like I've had happen before.
It's just so weird since it breaks everything. The lockscreen, the options, Pandora's station list, the browser, and it goes on and on. It's like there's some sort of display mode that gets screwed up.
dom085 said:
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
Click to expand...
Click to collapse
What version are you using. I'm going to try to install nightly 77 today after a fresh wipe.
I was seeing the same thing. Now I'm trying to figure out why my data speeds are so painfully slow on CM7 so I can't offer a fix. Flashing back to Warm to troubleshoot 3G.
I get these issues all the time no matter what kernel or nightly I'm running. It has forced me back to sense roms lol
Same problem here. I updated stable mod from stable mod. Reinstalled. Going on 4 days, no issues so far.
Sent from my PC36100 using XDA App
I have the same exact issue. This never happens on a sense rom. I did some tweaks to my system over the past week and I haven't had to reboot since this past Saturday or Sunday. I thought I had fixed it!
Then...
My phone started doing it this morning after I turned on 4G at work, literally as I was writing this post it started doing it. I then turned off 4G.. and it instantly went away. Turning back on 4G and it isnt doing it right now. Now my phone is doing something weird with go sms pro... when I get a text and I respond via the pop up message.. once my text moves to a second line I dont see what I am typing anymore... and now it has progressed to where the pop up box isnt refreshing after I send a message (this is all happening while I am typing this post). Now the phone has become laggy and somewhat unstable... rebooted! All is well. So I went roughly 4-5 days without a reboot... where as before I had to reboot at least once a day.
Thats about the best I can get with these settings:
CM7 7.0.3.1
Savaged Zen 2.6.38.5 CFS > Using SavagedZen Governor, min 384 max 998
Displaying some animations (read somewhere that is a "fix".. or helping extend the time it takes for the Black screen of death to appear).
This is after several full wipes, several when I was running Amon RA recovery 1.8 then updated to the latest and did it two more times. After upgrading Amon and wiping I did not use any backups and started completely from scratch.
So I am not sure what else to do. Some people are getting this, some are not.

Performance issue after CM nightlies updates.

Hi all!
I'm running CM11 24.06 nightly, along with Devil3 kernel on my n7100.
I've recently updated from 06.06 nightly (I believe), which was a fresh install (full wipe, no updates before), but I have had this issue before already. I think it starts to happen after I perform an update to the newest nightly. Rolling back to previous one doesn't help - another full wipe and fresh install is required to fix this or at least I didn't find a solution.
So, what's the issue? There are four issues that, to me, are connected:
1. Waking up - I'm experiencing serious lag when waking up the device. Sometimes the device doesn't want to wake up for half a minute, sometimes it doesn't wake up at all and it requires me to restart it by holding the power button
2. Lag after unlocking - Most of the time though, when device is actually successfully woken up and I want to fe. go straight to SMS app from lock screen and type something immediately, phone freezes for a second and when I'm able to type (touchscreen reacts, letter-press animation plays) - the letters aren't appearing. Sometimes it takes a while after I can type, sometimes I have to close the app. I've tried different SMS apps, deleting big conversations, different keyboard apps (I'm using SwiftKey, but stock app is the same - this one actually remembers what I type, recommends me something, but when I tap to use the recommendation, nothing is being typed into the text box) and some other things.
3. Application start up time and white status bar - Apps are starting to drop in performance as well. For example, when I run, let's say Play Store, the status bar on top of the screen is flashing white and it takes a bit longer to be able to use them (just like the SMS app).
4. % battery usage of certain (unexpected?) apps - Most battery hunger process is Android System. I've reset battery stats, for the last 1h and 45min used phone to type 2-3 messages, and it's usage is @27%, whereas 2nd process is screen with 18% and 3rd is Android OS with 11%.
Restarting the device seems to temporarily fix first three issues. They start to come back as soon as I start using the device, like opening apps, etc.
As I said before, it all happens after performing an update. Maybe I'm doing something wrong? I usually flash the update, restart device, go to recovery, flash kernel and restart. Since the issue happened again, I've tried to flash the new nightly and kernel together before, it didn't help. Clearing cache/dalvik is not helping (before, after).
I don't have any backups made (I know, I should've made one), so, I guess I'll prolly end up performing a full wipe again. But does anyone have some ideas what may be causing this? So I can prevent this for good next time, hopefully.
Ksenios said:
Hi all!
I'm running CM11 24.06 nightly, along with Devil3 kernel on my n7100.
I've recently updated from 06.06 nightly (I believe), which was a fresh install (full wipe, no updates before), but I have had this issue before already. I think it starts to happen after I perform an update to the newest nightly. Rolling back to previous one doesn't help - another full wipe and fresh install is required to fix this or at least I didn't find a solution.
So, what's the issue? There are four issues that, to me, are connected:
1. Waking up - I'm experiencing serious lag when waking up the device. Sometimes the device doesn't want to wake up for half a minute, sometimes it doesn't wake up at all and it requires me to restart it by holding the power button
2. Lag after unlocking - Most of the time though, when device is actually successfully woken up and I want to fe. go straight to SMS app from lock screen and type something immediately, phone freezes for a second and when I'm able to type (touchscreen reacts, letter-press animation plays) - the letters aren't appearing. Sometimes it takes a while after I can type, sometimes I have to close the app. I've tried different SMS apps, deleting big conversations, different keyboard apps (I'm using SwiftKey, but stock app is the same - this one actually remembers what I type, recommends me something, but when I tap to use the recommendation, nothing is being typed into the text box) and some other things.
3. Application start up time and white status bar - Apps are starting to drop in performance as well. For example, when I run, let's say Play Store, the status bar on top of the screen is flashing white and it takes a bit longer to be able to use them (just like the SMS app).
4. % battery usage of certain (unexpected?) apps - Most battery hunger process is Android System. I've reset battery stats, for the last 1h and 45min used phone to type 2-3 messages, and it's usage is @27%, whereas 2nd process is screen with 18% and 3rd is Android OS with 11%.
Restarting the device seems to temporarily fix first three issues. They start to come back as soon as I start using the device, like opening apps, etc.
As I said before, it all happens after performing an update. Maybe I'm doing something wrong? I usually flash the update, restart device, go to recovery, flash kernel and restart. Since the issue happened again, I've tried to flash the new nightly and kernel together before, it didn't help. Clearing cache/dalvik is not helping (before, after).
I don't have any backups made (I know, I should've made one), so, I guess I'll prolly end up performing a full wipe again. But does anyone have some ideas what may be causing this? So I can prevent this for good next time, hopefully.
Click to expand...
Click to collapse
i think this kernel issue..mybe u should stay with stock cm kernel..
Sent from my GT-N7100 using Tapatalk
Azhery said:
i think this kernel issue..mybe u should stay with stock cm kernel..
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Well, like I said, everything is working fine after a fresh install (with full wipe prior to it), is it possible for kernel to cause that after a nightly update?
Ksenios said:
Well, like I said, everything is working fine after a fresh install (with full wipe prior to it), is it possible for kernel to cause that after a nightly update?
Click to expand...
Click to collapse
mybe problem on nightly..do you hve try other cm based rom?
Sent from my GT-N7100 using Tapatalk
Azhery said:
mybe problem on nightly..do you hve try other cm based rom?
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Some time ago I had OmniRom and after few OTAs I actually started noticing similar issue if I recall correctly (that was the reason for me to switch back to CM).
mybe u try..full wipe..wipe data..wipe cache..wipe system..wipe internal storage..
Sent from my GT-N7100 using Tapatalk
But that's the point, I'll probably end up doing it since restarting my phone every 30-60 minutes is out of the question. But, then what? every few nightly/snapshot I'm gonna perform a full wipe?
Ksenios said:
But that's the point, I'll probably end up doing it since restarting my phone every 30-60 minutes is out of the question. But, then what? every few nightly/snapshot I'm gonna perform a full wipe?
Click to expand...
Click to collapse
mybe u can try other rom like cyanogenmodx..bcause i nver had this issue..
Sent from my GT-N7100 using Tapatalk
I was actually thinking about it, but as I said, when I used OmniRom few months ago, I recall that I had similar issues. Nevertheless thank you for your insight. Anyone have any slightest idea what might be causing such behavior?
I seem to have fixed the issue. Turns out the culprit was Business Calendar - Business Tasks to be more precise. I unistalled both and so far didn't experience those wake up lags.

So is there no fix/ solution for random reboots?

I got my Nexus 7 when it first came out last year, rooted it, installed TWRP, and have been on several different ROMs since. Didn't have any issues with random reboots for several months. Early this year, I started having an issue where the tablet would freeze while I'm using it, then automatically reboot itself. I thought perhaps it was a problem with the ROM I was running, but I had switched ROMs a few times after that, and every single ROM I've been on since then has had the same problem. It usually only happens when I'm browsing the Internet (with Chrome being my browser of choice), but I've had it happen once while using the camera app, as well.
The other day, I upgraded TWRP to the latest version, and I installed the 4.04 bootloader in preparation for Lollipop ROMs. I was hoping on some slim chance that perhaps an upgraded bootloader might fix the problem, but I'm still getting random reboots.
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
mrw1215 said:
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
Click to expand...
Click to collapse
I'd tend to agree with you it's a software thing. However, my approach would be a bit more radical than yours: that I would erase everything, including formatting the internal storage twice (after making a backup, of course), then install a completely clean rom, use it for a while to make sure it doesn't act up again before restoring any apps.
On the side, I've seen a Nexus doing random reboots whose owner had opened the back and bent the cover somehow, which slightly depressed the power button. While the button operated normally, this condition forced it to "click" randomly, which caused the reboots. It stopped after the owner replaced the back cover. You might want to check this part. Good luck.
Most of the time, random reboots are kernel related. If you are overclocked try to set max CPU lower and see if the problem fixes itself. If you don't overclock try installing something like Trickster Mod, and lower max CPU to see if that helps. What ROM and kernel are you running?
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
I always recommend flashing back to stock to rule out software issues. If it continues, you've got a hardware issue.
I haven't really messed around with kernels, I've typically just used whatever was included in a particular ROM, and I never adjust to overclock or anything like that. I don't remember what all the ROMs I've been on are, but I've been on CM before, and I'm currently using CleanROM. I think the only time I ever specifically tried a different kernel was a while back, when I flashed an Elemental kernel, but I've since wiped and been on a different ROM.
For now, I'm trying to hold out wiping anything until a good, rooted build of Lollipop is available, at which point, I'll try wiping out everything, including internal storage, and see if that helps.
I guess I could also try flashing back to stock before I do that, though. I think I've seen one stock ROM for the N7 floating around. The only problem is, it's really hard to "test" this, because the reboots are very inconsistent. The other day, after I had updated the bootloader, I was browsing Chrome for over an hour before I got a random reboot. One time, I was browsing Chrome for an hour and had 4-5 random reboots within that hour. So, that makes it difficult to determine if it's fixed in a timely manner. :/
Alright, so now that there's a proper build of Lollipop out, I did a factory reset and wiped internal storage (twice), and I'm now running stock Lollipop. I spent about an hour or so getting everything set up, and no reboots thus far; but the reboots mainly occur when I'm using Chrome, and I didn't really do any browsing, as I was getting all my accounts and apps and whatnot set up. Hopefully within the next couple of days, I'll have used it enough to get a good idea as to whether or not I'm still experiencing issues.
So far, no reboots, though i don't want to jinx it, heh... I'll be glad if the issue is finally fixed, but I'll also feel kinda dumb that all it took to fix it was something as simple as wiping internal storage and/ or reflashing a stock ROM. Lollipop is pretty nice, as well.
Yeah I'm using a custom version of L myself. You need to flash custom kernel to get working root access with SuperSU BETA 2.19
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."

Categories

Resources