Related
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
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!
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.
I tried out both CM9 beta and AA only to reflash after a month due to performance issues with the rom, just things like opening up handcent, contacts etc the phone would often hang for half a second. I figured that ICS was just not meant for our hardware so I'm now running CM7.2 and after 2 months of solid use, the slowness is back. Is it my hardware that's stuffed or am I just getting impaitent?
It seems as soon as you flash the phone, it is super fast for the first few weeks then it just goes back to its old sluggish ways. Any one got any ideas? Or should I just wait another 2 months till my contract is up and replace my old girl.
Sent from my HTC Vision using Tapatalk 2
You should reformat your storage to 4ext. Also, try wiping cache and app caches (for example maps, sms etc.) once in a while
On all phone I tried its the same thing.
on the moto milestone is the worst since its an old device. When I reflash a new rom, its really fast again.
It does it on SII and my DZ also.
Its like windows, more you use it, slower it will be.
GO SMS can take 5-6 second to come up. Fresh rom is instant.
On my DZ I tried to use it a maximum of time before it crash. After 300 hours without rebooting, the device was barely unusable. I cant take calls because it was so slow that I had time to miss it. I had a big delay between sound and vibration. Open opera takes around 20 seconds, etc.
And I love to keep my phone clean : no app running, no widget, no live wallpaper. I run sdmaid, and clean my cache often, but it didint help.
May be a app you are using causes this. App which eats up ram+swap etc. What are the apps you usually use.
and with most roms, its better to restart the phone every once in a while. I usually restart once every 2 days at least.
Thanks for the responses. I tried clearing the App data and it made a little difference at first but now it appears to be slow again, not always just at random times.
I don't use many apps, just Handcent for messaging, Contacts, Camera and Tapatalk. They all seem to hang when opening at random times.
I agree rebooting helps, usually when the slowness becomes too much I'll reboot and things will be a bit better for a day. I try to reboot at least once a week.
Hmmm I have an old iphone 3GS as my work phone, its older then my DZ and still performs better, which makes me think that this is a software issue rather then hardware.
Sent from my HTC Vision using Tapatalk 2
Your phone is no different then using a computer. Reinstall an OS and you suddenly have a super fast computer. How well you can maintain that OS depends on how fast it degrades or if at all.
I use SDMAID pro it is great at cleaning up application files. It keeps things running smooth.
Sent from my T-Mobile G2 using xda app-developers app
Carlovn said:
You should reformat your storage to 4ext. Also, try wiping cache and app caches (for example maps, sms etc.) once in a while
Click to expand...
Click to collapse
That would be EXT4
The system partition is formatted by the updater script on every system installation.
---------- Post added at 02:23 PM ---------- Previous post was at 02:22 PM ----------
jessv3 said:
I tried out both CM9 beta and AA only to reflash after a month due to performance issues with the rom, just things like opening up handcent, contacts etc the phone would often hang for half a second. I figured that ICS was just not meant for our hardware so I'm now running CM7.2 and after 2 months of solid use, the slowness is back. Is it my hardware that's stuffed or am I just getting impaitent?
It seems as soon as you flash the phone, it is super fast for the first few weeks then it just goes back to its old sluggish ways. Any one got any ideas? Or should I just wait another 2 months till my contract is up and replace my old girl.
Click to expand...
Click to collapse
There is no reason for it to slow down, except possibly if you are installing something that slows it down. Might want to go through all your software and try to figure out what it is that is slowing you down.
Same problem, but after uninstalling some apps the system run like new flashed rom.
Is ext4 a big performance improvement?
mx03 said:
Same problem, but after uninstalling some apps the system run like new flashed rom.
Is ext4 a big performance improvement?
Click to expand...
Click to collapse
Yes, it's a must for ICS.
Sent from my HTC Vision using xda premium
Can you refer me to a link where I can use this ext4 thing?
Sent from my HTC Vision using xda app-developers app
4ext recovery control i believe allows the reformat to ext4
apps like Facebook or chrome may also slow your phone down
i not agree all. but this things is happended on my dz' s rom.
cm7 sense miui .....try to wipe all.
Thread moved to Q & A section.
'cooleagle' said:
Thread moved to Q & A section.
Click to expand...
Click to collapse
It's usually the apps you installed that causes the slowdown. I kept my phone clean, with only essential apps that I need to use and it's performed the same throughout the whole year.
hi
ive got the same problem, i have 4 droid z's, was using miui roms at first but when i get calls sometimes i cant pick em up, go sms takes 5-6 seconds easy. the lags r random and usually go away when i run memory booster. This lag free instance lasts for only like 10-20 seconds though. The problem is finding out which app is causing this sluggish behaviour... are there any apps which can help in tracing out which apps are averaging more memory?
apps that are "memory boosters" or "task killers" or whatever should almost never be used. more often than not they just bog things down more and end up doing the opposite they are supposed to. watchdog (found in the market) will help point to apps that are using your cpu, not just whats in ram. (most of the time it is best to let android kill tasks for you) you can also run a logcat to see what processes are going on in the background. a little google searching or using the search button in xda here will turn out loads of apps that are known for memory leaks and slowing down phones
ext4 may actually make performance worst if journalling is enabled as it is constantly reading/writing to your sd card. If you mount it without journalling then maybe it is better
This is a long post, but I need assistance trying to get to the bottom of the random reboot and Black Screen of Death (BSOD) issue on the P93x series phones. Random chatter and dismissals are getting us nowhere, we need some structured approach.
I've submitted a CM bug report, and got Issue 6762 assigned. Feel free to star and follow there as well.
General Background Info
This seems to be a polarising issue: people who are in the know (technically) have devices without this problem, and people with this problem think the sky is falling and wondering why no fixes are coming. So before you jump all over me and tell me your P93x is fine and the problem does not exist, a little background is in order. I have two P930’s, one is humming along just nicely, thank-you-very-much, the other is experiencing the random reboot issue as well as the bsod, as validated by others in this forum.
Kernel OOPS on P930
Issues
First, I believe there are three issues at play (likely separate)
Random reboots especially when scrolling. Likely a kernel panic;
and, as per a good classification here
BSOD-A: Screen remains black, hardware buttons light up and touching buttons gives haptic feedback
BSOD-B: Screen and buttons remain black, no response to power button. Phone may become hot AND battery has taken a large hit when finally rebooted.
Scenarios for the above:
Using “heavy” apps like Google Maps, Waze, etc.
scrolling on lists or typing in some apps
device goes to sleep mode, can’t wake up the LCD. Keys light up, system up and running (background apps & loggers continue to operate) .. but can’t get to them.
devices reboots (often is is unseen since device is charging) and goes dead, can’t wake up. No lights, system down.
Both BSOD-A and BSOD-B require battery pull or long press of power button to restart device.
I am focusing on BSOD-B since ATM that's the bulk of empirical data I have at hand and it's a notoriously reoccurring problem.
If I manage to capture some good logs for BSOD-A (which are very rare for me), I will submit a separate bug report.
Troubleshooting BSOD-B
Here is a list of things I tried to narrow down where the problem may be:
wipes, full wipes, cache wipes, formats, etc.
nandroid clone of the stable P930 to the unstable P930
go through the unbrick process
flash back to Gingerbread
flash back to factory ICS
disable HW overlays in Developer Options
Here is what the effect these things had:
wipes stabilize the system for about a day or two before the problem reoccurs
nandroid clone had no effect. The unstable one still reboots/bsod
Unbrick process gives temporary relief. Problem still comes back after a day or so,
Gingerbread seems to be completely stable. No reboots or BSOD’s after a week of running it and incredible battery life.
ICS introduced random reboots, but no BSOD.
that seems to take care of the reboots while scrolling.
Observations
So first obvious observation: solution d) seems to fix all the problems. Buuuut … anyways moving on.
Second observation, solution f) seems to take care of vast majority of problem #1 under scenario 1b), so IMHO it’s a viable workaround, even though disabling HW overlays increases CPU usage and reduces battery life.
Third observation, BSOD-B most frequently occurs when under power, either AC or USB.
Fourth observation, based on analysis of kmsg for BSOD-B, the battery drain is due to a kernel fault, followed by a reboot, followed by CPU0 stall (after trying to initialize the LCD?). Here’s the kmsg related to this:
Code:
[ 2.021728] lm3530_probe: i2c probe start
[ 2.022369] mipi_lgit_lcd_probe: mipi lgit lcd probe start
[ 2.022521] setting pdata->panel_info.fb_num to 3. type: 8
[ 2.022979] mdp4_dsi_vsync_init: ndx=0
[ 2.029266] FrameBuffer[0] 720x1280 size=11304960 bytes is registered successfully!
[ 62.040008] INFO: rcu_sched_state detected stalls on CPUs/tasks: { 0} (detected by 1, t=6002 jiffies)
[ 62.040344] Backtrace for cpu 1 (current):
[ 62.040435] [<c010cf9c>] (unwind_backtrace+0x0/0x12c) from [<c010b1f4>] (smp_send_all_cpu_backtrace+0x60/0xc4)
[ 62.040618] [<c010b1f4>] (smp_send_all_cpu_backtrace+0x60/0xc4) from [<c0214fe8>] (__rcu_pending+0x43c/0x5e0)
[ 62.040802] [<c0214fe8>] (__rcu_pending+0x43c/0x5e0) from [<c02152fc>] (rcu_check_callbacks+0x170/0x1e0)
[ 62.040954] [<c02152fc>] (rcu_check_callbacks+0x170/0x1e0) from [<c01cec1c>] (update_process_times+0x38/0x68)
[ 62.041107] [<c01cec1c>] (update_process_times+0x38/0x68) from [<c01f2798>] (tick_sched_timer+0x98/0x258)
[ 62.041290] [<c01f2798>] (tick_sched_timer+0x98/0x258) from [<c01e6930>] (__run_hrtimer+0x1c0/0x304)
[ 62.041381] [<c01e6930>] (__run_hrtimer+0x1c0/0x304) from [<c01e6da8>] (hrtimer_interrupt+0x168/0x2f8)
[ 62.041564] [<c01e6da8>] (hrtimer_interrupt+0x168/0x2f8) from [<c0117b54>] (msm_timer_interrupt+0x18/0x20)
[ 62.041717] [<c0117b54>] (msm_timer_interrupt+0x18/0x20) from [<c020f51c>] (handle_percpu_devid_irq+0xfc/0x1a8)
[ 62.041870] [<c020f51c>] (handle_percpu_devid_irq+0xfc/0x1a8) from [<c020bb74>] (generic_handle_irq+0x2c/0x40)
[ 62.042022] [<c020bb74>] (generic_handle_irq+0x2c/0x40) from [<c0106ea0>] (handle_IRQ+0x7c/0xc0)
[ 62.042205] [<c0106ea0>] (handle_IRQ+0x7c/0xc0) from [<c01003b4>] (gic_handle_irq+0x80/0xac)
[ 62.042297] [<c01003b4>] (gic_handle_irq+0x80/0xac) from [<c0853754>] (__irq_svc+0x54/0x80)
[ 62.042388] Exception stack(0xda65ff98 to 0xda65ffe0)
[ 62.042541] ff80: 00000020 c0c23fb8
[ 62.042633] ffa0: da65ffd8 00000000 da65e000 c0c2d5c8 c0cb4124 c086e55c 4020406a 510f02d2
[ 62.042785] ffc0: 0000001f 00000000 00000000 da65ffe0 c0106fdc c0107384 60000013 ffffffff
[ 62.042968] [<c0853754>] (__irq_svc+0x54/0x80) from [<c0107384>] (cpu_idle+0x84/0xe8)
[ 62.043121] [<c0107384>] (cpu_idle+0x84/0xe8) from [<40a4b754>] (0x40a4b754)
[ 62.043212]
[ 62.043212] sending IPI to all other CPUs:
Why battery discharge
Gist of the problem: pm8058-charger driver and related infrastructure - like USB - is not loaded yet, CPU0 is hung, CPU1 observes that its colleague is hung and faults, re-tries, and the party continues until the battery is dead.
Possible Workarounds
The only way to avoid to BSOD-B while charging is to shut down and put phone in power-off charge-mode. This is not completely viable since BSOD-B also occurs in the car when navigating or any time USB power is on.
Improving empirical data
Challenges and roadblocks
Hanging this way and so early during boot presents a problem when retrieving kmsg. The new kmsg with the CPU0 stall replaces last_kmsg on reboot thus wiping any evidence of the real kernel panic which caused this whole thing in the first place.
To make it even more fun, there is a non-zero probability that a kernel panic followed by a reboot does not hang CPU0 .. meaning you’ll never know if a kernel fault will cause CPU0 to hang until it hangs by which time it’s too late to recover the all important last_kmsg. Dead end.
For further kick in the nuts, when the CPU locks and drains the battery down to zero (or is powered off) the device turns off and boots to charge mode (since it’s under power), now wiping the CPU0 stall kmsg and stuffing last_kmsg with charge-mode messages, this time wiping evidence of the CPU0 lock described above. This can be avoided by catching the device early in the discharge cycle and unplugging the device before forcing a reboot .. but still that only gets us to read the CPU0 lock kmsg but not what caused this whole mess in the first place.
Next steps
Any ideas on how to backtrack and get better logs of the initial crash? Logcat appears useless here since it's a userspace process which gets yanked the moment a kernel oops occurs. Even piping kmsg to a file does not work due to the same problem (ie. userspace). Is there a way to tell the HW to shut down on kernel oops rather than reboot? Do I really need to disassemble these two phones in order to compare and determine differences?
Any constructive ideas, suggestions, or thoughts will be greatly appreciated.
EDIT: As of April my P930 which exhibited this behaviour is in the hands of tdmcode. This way he has something to test on and hopefully at some point he'll be able to figure out a workaround for this issue.
Finally!
Finally!
Thanks for officially posting the bug. Some of us didn't have the ability to technically describe the problem and now you have done it for us. Hopefully some fixes will come so that we can all start getting normal usage of our phones, which are powerful when working reliably.
Thanks again!
I'm glad you reported it. It's probably a combination of more than one bug, though, so hopefully it gets resolved. I'm mostly hoping CM10.1 somehow resolves the bugs in CM10 when Ricardo gets around to working on our phone.
Sent from my LG-P930 using Tapatalk 2
Very nice summary.
However, given your own experience with two of them, and the "polarising" experiences, it seems to imply a hardware issue for at least one of the three situations, for example, a chip was revised at some point in production, or there was poor quality control on chip or component manufacture, etc.
I never had BSOD-B. The other two, well ... :crying:
Some other observations:
- P935, i.e., Telus, users seem to be more affected (or more proportionally more vocal) than Nitro HD users. Telus was/is offering affected users a new One X (or equivalent) as a straight swap. This is not typical carrier behaviour in my experience, especially after one has had a phone for over six months ...
- P936 users seem to be less affected.
Good luck on your quest, I hope it is successful!
I definitely agree with your hypothesis that it's hardware related. I suspected this when HONO first released an overclocked kernel for gingerbread. Some people could overclock to 1.8GHz without issue, and my phone would crash randomly and during benchmarks whilst underclocked massively. Same thing happened with Full Throttle for CM9.
Glad that someone actually submitted a bug report, thanks a lot!
Agree, this definitely presents itself like a QC or product rev issue. Based on how LG has handled it, it would seem it's a Qualcomm issue tho - otherwise I am sure LG would address it in their ROMs. This is why I don't hold out much hope ever seeing a fix/workaround for this.
I have no issues running the LG ICS releases (bell and att), except for an issue where the bluetooth driver becomes unresponsive. My head unit still reports being connected, but my phone will not turn off bluetooth or route audio through bluetooth OR speakers.
Sent from my LG-P930 using XDA Premium HD app
Blue tooth is your only issue? You sir are quite lucky.
Sent from my LG-P930 using xda app-developers app
Reboots and BSOD
Thanks for this post. I can add a couple of things, I have an AT&T LG Nitro, and as you say with GB work just fine, I can add that with v18f (ICS Leak) phone also works fine, no reboots or BSOD. I really think that this problem it's related with video, when I first installed stock v20c I had a very curious (and as far as I know common) problem, I have BSOD and after the phone reboots, a red halo appears on the screen, weird, it was solved after 3 or four reboots.
Another thing that I notice is that when I use Dolphin browser (it also happens with waze) and watch a site with flash content, and close dolphin, a strange drawing problem appears on screen, some kind of flicker, it can be solved reentering dolphin and close it.
I've been used liquid nitro for almost a week, after 6 hours of the installation I have the first reboot, then, I have 4 days without reboots or BSOD, incredible, but the fifth day the problem reappears, 2 BSOD.
Returning to what I think it's the root cause, maybe it could be related with video hardware acceleration, that could explain why v18f works, I think HW acceleration it's not complete implemented in this version, that's why it's not as smooth as v20c and works fine.
fguzmant said:
Thanks for this post. I can add a couple of things, I have an AT&T LG Nitro, and as you say with GB work just fine, I can add that with v18f (ICS Leak) phone also works fine, no reboots or BSOD. I really think that this problem it's related with video, when I first installed stock v20c I had a very curious (and as far as I know common) problem, I have BSOD and after the phone reboots, a red halo appears on the screen, weird, it was solved after 3 or four reboots.
Click to expand...
Click to collapse
Oh man, I've had the halo thing appear once as well and it would not go away .. that was a scary moment as I thought the LCD got fried for some reason. Very very weird effect.
fguzmant said:
Another thing that I notice is that when I use Dolphin browser (it also happens with waze) and watch a site with flash content, and close dolphin, a strange drawing problem appears on screen, some kind of flicker, it can be solved reentering dolphin and close it.
Click to expand...
Click to collapse
Did you try disabling "HW overlays" under Developer options? I have had weird drawing problems for graphically advanced apps, but disabling HW overlays seems to fix that up for me. Also, the overlay issue went away for me in the latest nightly CM10 builds .. no drawing artifacts, and no reboots I can link to video acceleration issues. Wish I could say the same thing about the BSODs ...
fguzmant said:
I've been used liquid nitro for almost a week, after 6 hours of the installation I have the first reboot, then, I have 4 days without reboots or BSOD, incredible, but the fifth day the problem reappears, 2 BSOD.
Click to expand...
Click to collapse
This is the other weird part about these BSODs .. they takes time to build up. When I do a full wipe, I will be OK for a few days, then BSOD hell begins.
Yes, I get the red halo effect too randomly after a BSOD, sometimes it has gone to the point of taking up the while screen with the red, and somewhat flickers as well. However it doesn't usually get that bad.
Sent from my LG-P930 using xda app-developers app
miji2 said:
Did you try disabling "HW overlays" under Developer options? I have had weird drawing problems for graphically advanced apps, but disabling HW overlays seems to fix that up for me. Also, the overlay issue went away for me in the latest nightly CM10 builds .. no drawing artifacts, and no reboots I can link to video acceleration issues. Wish I could say the same thing about the BSODs ...
Click to expand...
Click to collapse
Sadly, liquid nitro or v18f does not have that option. My experience with CM10 was a BSOD nightmare.
I too have gotten all three types of hangs:
1) Reboot to CM logo (every couple days)
2) Can't turn screen back on but other buttons working and responsive (rare)
3) Reboot to LG logo followed by black screen and battery drain (every couple days)
I don't believe I ever had 2 and 3 happen on CM9 FT though, just CM10.
Thanks for submitting a report!
Sent from my LG-P930 using Tapatalk 2
On Official ICS, CM9, and CM10 I always have the random reboots. Doesn't happen in Gingerbread. I have tried every work around that I could find and the random reboots continue. I only started experiencing the wake locks in the newest CM10 nightlies. For now I have gone back to stock rooted gingerbread. At least until the reboot issue is resolved, if it is.
ahdoublexl said:
On Official ICS, CM9, and CM10 I always have the random reboots. Doesn't happen in Gingerbread. I have tried every work around that I could find and the random reboots continue. I only started experiencing the wake locks in the newest CM10 nightlies. For now I have gone back to stock rooted gingerbread. At least until the reboot issue is resolved, if it is.
Click to expand...
Click to collapse
Did you try ICS Leak v18f, I can confirm that there's no reboots or BSOD in this ROM, the problem with this it's battery life, but with setcpu and juice defender I can manage to survive a day.
OK, new theory to test: cache partition corruption causing BSOD
Background:
I observed several times that BSOD type B does not occur until the phone starts to reboot randomly (due to scrolling or otherwise). Same this time: after running the 20121201 nightly (+ reset) smoothly for the past 3 days, I got a reboot due to kernel oops, then my BSOD-B started.
Recovery
This time I was able to fix the Random reboot while charging leading to BSOD-B by just formatting the Cache partition from recovery. I am not sure if I tried that before, but it worked this time. But this kind-of explains why a factory reset would stabilize the phone for a bit ...
Testing
I need others to test so we can confirm this. To help, please try latest nightly, and watch the BSOD causing the phone to get hot. If you get it, format your cache and let me know if it made any difference.
Follow-up
Note, we still don't know what patterns of use cause the random kernel oops .. but at least we would not have to endure dead phones first thing in the morning.
miji2 said:
OK, new theory to test: cache partition corruption causing BSOD
Background:
I observed several times that BSOD type B does not occur until the phone starts to reboot randomly (due to scrolling or otherwise). Same this time: after running the 20121201 nightly (+ reset) smoothly for the past 3 days, I got a reboot due to kernel oops, then my BSOD-B started.
Recovery
This time I was able to fix the Random reboot while charging leading to BSOD-B by just formatting the Cache partition from recovery. I am not sure if I tried that before, but it worked this time. But this kind-of explains why a factory reset would stabilize the phone for a bit ...
Testing
I need others to test so we can confirm this. To help, please try latest nightly, and watch the BSOD causing the phone to get hot. If you get it, format your cache and let me know if it made any difference.
Follow-up
Note, we still don't know what patterns of use cause the random kernel oops .. but at least we would not have to endure dead phones first thing in the morning.
Click to expand...
Click to collapse
Tried the procedure above with todays nightly. So far only one reboot but that was due to the camera bug. No BSOD so far.
Will see if it happens overnight
EDIT: charged overnight and still no BSOD. So far so good. :thumbup:
Edit 2: just got BSOD, so I guess its back to the drawing board.
Sent from my LG-P930 using xda app-developers app
khanfed said:
Edit 2: just got BSOD, so I guess its back to the drawing board.
Click to expand...
Click to collapse
Same here
khanfed said:
Tried the procedure above with todays nightly. So far only one reboot but that was due to the camera bug. No BSOD so far.
Will see if it happens overnight
EDIT: charged overnight and still no BSOD. So far so good. :thumbup:
Edit 2: just got BSOD, so I guess its back to the drawing board.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Wasn't the whole point to clear cache after any sort of crash-reboot? The idea was a crash-reboot will corrupt the cache and then cause the BSOD.
Sent from my LG-P930 using Tapatalk 2
Yup the procedure above was done after a crash/reboot, but in the end it didn't resolve the issue, since I got the BSOD again.
Sent from my LG-P930 using xda app-developers app