Hi everyone, this is my first post on the forums, althought i've been around for some time now. I'm not an advanced user at all and my english is not that polished so sorry if something I write is weird, I'll put everything as clear as I can.
I have a red lens defy that currently has CM9 installed. This would be my second attempt at having CM9 on my phone. I installed it first on march, but had to many problems and reverted to CM7. One of the problems I noticed the first time through CPU Spy was that, out of the three different speeds that the CPU has (300, 600, 1000), it was only running either at 300 or 1000. 600 was barely used (less than 1% of the time). First I though that maybe 600 was too slow so I changed it to 700 in bootmenu. This didn't help and the phone was overheating so that's when I decided to flash CM7 (cm7.2 rc1) again. With CM7 my phone has definetly been running cooler, however sometimes it would start heating up even though I wasn't doing anything to complicated (for example, using the web browser or gtalk for a long time). So I started monitoring the cpu again and found out that the cpu was still running only either at 300 or 1000 (though mucho more at 300 than with ics). Now that I have flashed CM9 again (120605 nightly), things are much smoother than before, but the problem is still there.
I've been looking for possible explanations and solutions but - maybe because I don't know how to formulate the problem when searching - haven't found anyone that has this problem. If any of you knows or can think of possible fixes to try out, please help me out.
Deep sleeping is not a problem, btw, CPU Spy says the processor is asleep most of the time. Also, I haven't been running any scripts, kernel tweaks or anything out of the ordinary either.
Thank you all, I might not be actively participating but I like this forum a lot (reading it everyday!), and the people and devs are all great.
Questions go in the Q&A section
Related
I've got a problem with my I9000, several times throughout the day it will randomly restart itself. It will be quite happily sat idle in my pocket not doing anything, and then suddenly I hear the boot-up sound from my pocket. It's just started doing this since Thursday or Friday I think it was, had nearly 700 hours uptime on it (699 hours ) and then I noticed from my SeePU notification that something was hammering the processor, running it at >90% for more than 10 minutes. Couldn't see any programs running in the background so decided to restart the phone. This is one my problem started.
It's running stock JPY with Voodoo Advance kernal, it was overclocked to 1.2GHz and had some undervolting from 800MHz down, this had been stable for all of those 699 hours, but I disabled the OC and UV yesterday to see if it was that causing the trouble, but even with it disabled the phone's still been restarting.
What would be really great is if there is some kind of crash log for Android (something similar to the Windows Event Viewer) so I can see what's causing this. Does anyone know if such a thing exists, and if it does how I might go about accessing it?
Failing that, anyone know why my phone would suddenly start restarting itself now?
had pretty much the same issue, different kernal and rom... but had an OV/UV that for the most part was stable...
then today was continually restarting.....
solution?
changed CPU scheduler to noop
changed CPU Governor to conservative (Galaxy S cpu default configuration)
Now not restarting at all... and that's with a 1.3GHz overclock... running several benchmarks and no undervolting at all.
I'll let you know if it starts acting up... but interesting that this at least fixed it for me.
Stupid thing has restarted itself twice this morning. This is ridiculous.
I've just set the schedular to noop, can't see an option to set the governor though. Will see if that sorts it.
Would really appreciate knowing if there's a log file or something though
If it was a PC you would say its overheating .
jje
Found an app on the market called OS Monitor that shows all the running processes and what load they're putting on the CPU, it also shows the dmesg and logcat log files.
Thankfully my phone hasn't restarted itself since changing the schedular, but if it does I should hopefully now be able to find out why
quick answer. Reflash the phone .
I guess reflashing and removing some dangerous apps will be good for you phone.
Hmm, well looks like it's given up on restarting itself and is just plain turning itself off now.
Looks like I'm going to have to reflash the stock kernal and see if that fixes it
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Sounds like simple bad karma, I suggest donating to a charity or going to church
Other than that, I'd have no idea, sorry. Seeing as its not totally regular, there'd be no good way to easily pinpoint the issue. Maybe see if the rom produces a last_kmsg?
-Nipqer
makken85 said:
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Click to expand...
Click to collapse
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
skulk3r said:
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
Click to expand...
Click to collapse
Hmm, so you believe that this is purely a rom issue?
I havent run a stock rom for a while, but from what i remember the experience wasnt that pleasant, there was significant lag almost everywhere in the ui. Although i will admit that was back with froyo; i havent tried a stock gb stock rom yet.
Ill probablygive cm7 a go. Ive just grown so used to some sense features that its going to be hard for me to give them up (mainly recent apps in notifications, news widget, t9 dailer+manually linking contacts, and remote ring and forward on htcsense.com)
Has anyone had similar issues running virtuous sense 2.0.0?
As far as recent apps goes, long pressing the home button is a standard feature of android that brings up the most recent. Stock is the last 8 (I think) cm7 can show 15.
Sent from my HTC Vision using xda premium
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I'd agree. I really wouldn't ever go over 1.2ghz for a daily driver personally.
I run my ROMs at 800mhz lol, so I don't see the advantage of a huge overclock unless you're just bragging about benchmark scores.
its funny when u wanna show off your phone and you take it out of your pocket acting all cool and stuff and when u press the power button it wont wake up or you get a blank screen
haha its just bad karma for u like nipqer said
Try the stock pre-rooted gingerbread...I just flashed t last week and it is way faster than my froyo was, and amazing battery life, for me anyways, I do have an extended life battery though lol. Anyways as far as speed it is snappy on 800 mhz
Sent from my T-Mobile G2 using XDA App
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I've noticed the random hangs / glitches @ 800Mhz and 1Ghz, so I'm hesitant to say that the OC is the cause.
What do you use for stability testing? I've been running quadrant nonstop to test new OCs, but I don't think that benchmark stresses the cpu enough.
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
swinderz said:
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
Click to expand...
Click to collapse
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
makken85 said:
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
Click to expand...
Click to collapse
http://www.droidforums.net/forum/droid-hacks/21309-setcpu-1-4-6-what-cpu-governor-options-mean.html
I have a HD2 with an older version of android cooked on. Android version 2.3.7 Kernel version 2.6.32.15_tytung_r12.4-heebf2c Mod version is CyanogenMod-7.1.0 Desire (Typhoon_v3.7.0 Magldr) I think my radio is 2.15.50.14
I really need the wifi calling feature on my phone to work. Do all the roms have this problem on our phones? Would it be easier for me to just install a new rom? Every time I turn on wifi, the phone freezes completely. I read through the post regarding this issue, but there was no specific information given about how to overclock the phone. I downloaded nofrills cpu control and have tried random combinations, but was wondering the ideal oc speed?
resevil83 said:
I have a HD2 with an older version of android cooked on. Android version 2.3.7 Kernel version 2.6.32.15_tytung_r12.4-heebf2c Mod version is CyanogenMod-7.1.0 Desire (Typhoon_v3.7.0 Magldr) I think my radio is 2.15.50.14
I really need the wifi calling feature on my phone to work. Do all the roms have this problem on our phones? Would it be easier for me to just install a new rom? Every time I turn on wifi, the phone freezes completely. I read through the post regarding this issue, but there was no specific information given about how to overclock the phone. I downloaded nofrills cpu control and have tried random combinations, but was wondering the ideal oc speed?
Click to expand...
Click to collapse
I never used Tytung's GB rom but wifi generally works very well. I used it all the time with Typhoon GB, Tytung's ICS and JB.
For overclocking Install Setcpu from the Play Store.
---
With proper diet, rest, and exercise a healthy body will last you a lifetime... (via Tapatalk)
Can you give me an estimated range I should set my cpu to? I can't find the thread, but somewhere along the line I read something about how you should over clock your processor in multiples of something. I'm not describing it well, but maybe it had something to do with a mhz speed and then a frequency or another unit of measurement for power. Like volts. I have no idea, what I'm trying to say is that I read there is some sort of calculation you need to figure out in order to properly adjust your cpu settings.
ny_limited said:
I never used Tytung's GB rom but wifi generally works very well. I used it all the time with Typhoon GB, Tytung's ICS and JB.
For overclocking Install Setcpu from the Play Store.
---
With proper diet, rest, and exercise a healthy body will last you a lifetime... (via Tapatalk)
Click to expand...
Click to collapse
resevil83 said:
Can you give me an estimated range I should set my cpu to? I can't find the thread, but somewhere along the line I read something about how you should over clock your processor in multiples of something. I'm not describing it well, but maybe it had something to do with a mhz speed and then a frequency or another unit of measurement for power. Like volts. I have no idea, what I'm trying to say is that I read there is some sort of calculation you need to figure out in order to properly adjust your cpu settings.
Click to expand...
Click to collapse
I think that all better apps for this already take care of much of what you are looking for. I know SetCPU does - in fact it has profiles for numerous phones, including the HD2. The one disadvantage that I tend to forget is that it isn't free. If you look at the app's description on Google Play you will get a lot of ideas. Likewise, the developer's web site also has some good info.
Briefly, I do not set any profile's low frequency below 245 MHz (potential SODs). The high-end you can experiment - if the HD2 locks up reboot and set it lower.
I have a default profile and change it to faster MHz if plugged in (I don't care about using more power when plugged in) or lower frequencies for sleep or overheating and such. If you do get SetCPU you can plug in the attached profiles (don't forget to unzip it first!) and see if you like any of them. They can all be changed or deleted, of course.
Recently I upgraded my Nook Color from CyanogenMod 7.2 to CyanogenMod 10.1 stable. After that, somehow, it kept shutting down every half a minute or so when in use and when left alone. I did not touch the battery, the CPU is clocked at 300 MHz to 1.1 GHz, screen set to 16 bit mode, GPU untouched. Has anyone else had this problem and is there a way to fix it? Thanks in advance.
Ethan_Kok said:
Recently I upgraded my Nook Color from CyanogenMod 7.2 to CyanogenMod 10.1 stable. After that, somehow, it kept shutting down every half a minute or so when in use and when left alone. I did not touch the battery, the CPU is clocked at 300 MHz to 1.1 GHz, screen set to 16 bit mode, GPU untouched. Has anyone else had this problem and is there a way to fix it? Thanks in advance.
Click to expand...
Click to collapse
I upgraded to the latest stable CM10.1.2 release and have started getting random sleep of deaths (SD install). I've had them while plugged in, not plugged in, with screensaver on, with screensaver off (thought maybe keeping it active would help prevent)... I can't seem to find a pattern. I've tried every nightly since and am still seeing it. I tried rolling back to the first stable release, still there. I'm going to try rolling back from 1100 MHz to 1000, then 800, to see if that helps at all.
I'm a total newb to debugging this thing, but I'm happy to try and pull any logs to post if someone can point me in the right direction (I've looked around before on how to do this but get confused easily). Also, I'd be willing to try a clean install, but don't want to go through the hassle of reinstalling everything again. If there is a quick way to backup programs, I'm all ears.
The good news is, it runs great when it's up. Quite smooth. Pretty awesome stuff.
I believe Titanium Backup should back everything up.....
I have downgraded to CyanogenMod 7.2 as I am very exasperated with this issue, the short battery life and lagginess that the upgrade has brought.
Hi everyone,
Thanks for reading this . As specified above, my phone has a rather serious problem of overheating. To try and reslove the issue I tried modifying the CPU frequency, to set it low enough. And a very bizarre thing just happend.
Opening Kernel Adiutor, I saw that 4 out of my 8 cores (the 2.5 ones) were running normally. No overclock, stock settings, stock governor and so on. The issue seems to be in the other 4 (the 2.3 ones). Both the minimum and highest frequency allowed is set up to the same parameter (1556 mHz), forcing it to stay at maximum clock all the time. I tried modyfing via Kernel Adiutor the settings, lowering the minimum frequency allowed to stock one (which should be around 300 or something), but it had no effects: it immediatly comes back to 1556 and just won't come down.
All of this started happening after i removed Franco Kernel from my system, flashing another ROM (Chroma) with a different kernel altogether. I'm currently on Cataclysm ROM and after doing a clean install, formatting internal storage as well as every other partition, i couldn't resolve the issue. Moreover, Kernel Adiutor sometimes won't even show my CPU settings, stuck on an infinite loading. If anyone could help me, it would be much appreciated. It's really important. I'm by no means Android expert but i do have a rather basic understanding of ADB and so on.
Thanks a lot for your time.
-LVBNR5
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
ml11ML said:
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
Click to expand...
Click to collapse
Thanks anyway, i really appreciate it!