Database Users

[Q] Is it normal for Wildfire to keep force closing daily?

Any one else on Wildfire who just can't have a smooth day without a force close.
I know I have rooted the device but am I expecting too much?
I am on a nightly Cynogen build and I have setcpu and JIT on.

I'm rooted running CM7 RC2 and I used to have loads of issues with things force closing but that all stopped as soon as I started using SetCPU, maybe experiment with your settings? Handset seems to be more stable when I've got JIT turned off too.

Are you using kernel come with cm7? try to use kernel v4.1, some phone not stable with booting at overclocked freq.

I'm using kernel 4.1, setcpu 352-748 on performance, JIT on, no force closes ,
but it's because some of the phones have problems with certain cpu speeds and the new 4.2 kernel etc etc.

Also try to fix permissions from RomManager, it worked for me few weeks ago when I've experienced the same problems.

The last week has been quite a smooth one yes, I have the v4.1 kernel but I also fixed permissions. I was a little paranoid about fixing permissions because when I last did it, I got the kernel loops and I was away home in the weekend and had to wait till Monday to flash the 4.1 kernel which was an issue then.
I'm happy as is now and I can see that I'd ignored to tick the restore settings on setCPU when the menus for setCPU moved into Cynogen settings. A few minutes just studying I have come to learn can save a lot of complaining.
Thanks.

CPU isn't scaling - stuck on 100%

Hi all, not sure how to address this, but my battery's been a little crappy lately. I downloaded SETCPU after not using it for ages, and I noticed when i set it that my CPU seemed stuck on the fastest speed. Downloaded SeeCPU and confirmed. So though my min-max is set at 245-986, it's always on 986.
I'm using Kushdeck’s latest w/ the stock kernel (which is the cyanogen kernel), and I even went so far as to wipe all data and re-flash everything...still no luck. Any ideas on how to proceed?

Did you disable the perf-lock in setcpu?
We're comin from a pure power source.

Yes, perflock is disabled. I can lower the cpu speed, but it wont scale. So the default is 998, and typically I'd set the min/max at 245/998. I noticed that the CPU was always at 998, it never scaled down. Now I have the min/max set at 768/245 and it's always on 768. If perflock were disabled I thought I wouldn't be able to change the speed at all, though I may be wrong there...I also tried the perf unlocker in setcpu and it reports that it is already unlocked.
At this point I wiped data, cache, and Dalvik. Re-flashed the rom (deck's aosp rom) , stock kernel, practically no apps installed except setcpu and seePU to monitor usage.

Oh and the governor is the default, I think interactive...

Try another governor like conservative and see. After that I'd try another kernel or download the stock one again in case something is buggered in yours
Sent from my PC36100 using XDA Premium App

Thanks already tried a different governor, tried a tiamat kernel, then said screw it and reinstalled the rom from scratch. Still having the same issue. I may go back to a sense rom to see of that makes a difference.

Hi, I know and understand what problem you're having. I had this on my desire. Run a ruu or flash a pb99img. The problem only happens on non sense roms. This is the only solution to make non sense roms work. Just try it. Good luck!
Hit the thanks button!
Sent from my HTC Desire using XDA App

I ended up flashing back to Myn 2.2 (which is Sense) and it started working again. Thanks!

CPU isn't scaling, not affecting battery life?

Here's an issue I just noticed late last night. My CPU seems to be stuck at max. I've tried different governors, wiped cache/dalvik and reflashed kernel and rom. I also killed all running apps to see if an app was causing it, to no avail.
Here's what really stumps me, my battery life seems fantastic. Not what I'd expect if my CPU is running at 100%. Could there be an issue with detecting CPU speed? As I mentioned before, trying different governors doesn't help with scaling but I notice when I select "powersave" my CPU jumps from max to the minimum value and stays there, still not scaling.
Before someone mentions I did search before posting. Went through the threads, tried the suggestions within and still have the problem. Hence why I'm posting here now.
Am I overlooking something? Any help will be appreciated, thanks!
Edit: My current rom and kernel are in my sig.

so are you monitoring this via setcpu on Decks?

alaman68 said:
so are you monitoring this via setcpu on Decks?
Click to expand...
Click to collapse
Yes I am, is there a known issue?

My understanding is that having both setcpu and the native CPU performance running will result in some conflict. that is probably the problem, but I don't know how to monitor the scaling with the native performance. so i see what you are trying to do.
I never run setcpu on CM7 or Decks because it is built in, but if the battery life is alright, it would appear the built in takes precedence.

Is there a good way to monitor the CPU without setCPU? Thanks

cesjr02 said:
Is there a good way to monitor the CPU without setCPU? Thanks
Click to expand...
Click to collapse
check out "system panel"
edit: or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency.

Thanks, I like that app a lot.
Unfortunately even after deleting setCPU I'm still seeing 100% CPU usage. According to system panel the System is using 80%.
Edit: I am underclocked to 499MHz, and that's where she's pegged. Still oddly enough I'm getting the best battery life I've seen in weeks.

My CPU doesn't scale correctly either. Its either running at MAX, Deep Sleep, or 245mhz. Never does it use the in between frequencies no matter what govenor I use(I have tried them all). I use CPU Spy to check scaling and No Frills CPU to change the governor both are from the market.

cesjr02 said:
Thanks, I like that app a lot.
Unfortunately even after deleting setCPU I'm still seeing 100% CPU usage. According to system panel the System is using 80%.
Edit: I am underclocked to 499MHz, and that's where she's pegged. Still oddly enough I'm getting the best battery life I've seen in weeks.
Click to expand...
Click to collapse
so if you do this:
or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency
what is the frequency while it is sleeping?
1. you may need to overclock just a bit
2. you may want to reflash rom without wiping the data and see if that helps
3. every phone is slightly different, so yours may need more time to process the commands at 499, especially if you are undervolted as well. which is why you getting pegged.

alaman68 said:
so if you do this:
or android system info app > system tab > cpu. gives you a break down of time (%) spent at each frequency
what is the frequency while it is sleeping?
1. you may need to overclock just a bit
2. you may want to reflash rom without wiping the data and see if that helps
3. every phone is slightly different, so yours may need more time to process the commands at 499, especially if you are undervolted as well. which is why you getting pegged.
Click to expand...
Click to collapse
Thanks, says the time spent at 499 MHz is 92.51%. I don't think underclocking is the issue. If I overclock to 1113MHz it will peg there as well. Seems to only go 100% when screen is on however according to the system panel app. I'll try your suggestion in (#2) and report back.

Tried reflashing the rom without wiping. Still have the same issue. So odd. I'll try a different kernel just to see if that helps, but I'd hate to part with my 3.3.7 LEE kernel.
Last thing I can think of is doing a full wipe, but I'd like to avoid that if I can.

Definitely experiencing the problem with other kernels. I'm out of ideas.

Did you try tiamat 4.1.0? I'm using it now and the battery life is right there with 3.3.7.
Sent from my PC36100 using XDA App

Did you restore any apps with titanium backup by chance?
Sent from my PC36100 using XDA App

By the way, I appreciate all your help alaman68.
Tiamat 4.1.0 was the other kernel I tried. No luck. Also I've never used titanium backup to restore apps. I'm stumped as to why my CPU won't scale anymore. The Android System seems to be using as much as I allow it.

Trying, you could try a sense rom for a day and check the scaling for a benchmark.
Is there anything else you are running? Undervolting, v6... Anything else?

Not undervolting as my phone never liked it. Nor running V6 or any other scripts either. I'll try flashing a sense rom, see if I have the same problem there. Or else, think doing a full wipe and reflash everything would help?

if all else fails, a clean flash won't hurt. Even get a new download. Gotta ask, did everything properly? you using amon_ra recovery? did you download any new apps when that started happening?

I may just have to. I suppose there's always a chance I made a mistake somewhere, but I've been at this rooting/flashing thing for a long while. Thing is, everything was fine up until I noticed it last night.
I'll do a clean install. I can always nand restore if it doesn't work. (Save me the time to set up everything.)
I'll report back

Did a clean install and guess what, my CPU is scaling again! There must have been a conflict somewhere. Thanks again alaman68 for all your help and suggestions. Sometimes these phones get gremlins I tell ya.

Freeze after 10-20 seconds of operation on CM7 running on SD

Hello all,
Really new to the android game here and I have a problem with my nook. I looked around the forums and didn't see anything that was just like mine so I thought it wouldn't hurt to ask. I'll give you (whoever is willing to read this and give me some suggestions) as complete of a picture as I can.
I recently bought a refurb nook color. I put the latest stable build of CM7 on a 32gb class 4 sandisk card. Everything was working great. I tweaked the CPU settings (voltage too) and everything was running smooth as butter for the past two or three days. A few days ago I also upgraded the stock OS to 1.4.1.
This morning I woke up to a dead nook. I thought it was mostly charged before bed but I figured I had made a mistake. I plugged in, rebooted, got it to work for 10-20 seconds (VERY shaky performance) and then it froze up and I had to reset. It did this 3 or 4 times in a row until I gave up and booted into stock OS, which is working flawlessly. On the way home I was still having the same problems with the CM7 so I decided to take out the sd card and reinsert and that seemed to do the trick! I was able to use it for a good 1-2 hours and everything was flying. However, I went to plug it in and it froze up again. If I have it plugged in and when I drain the power (by holding the power button) it boots right back up, works for 10-20 seconds, then dies on me again. Stock OS is still working great, but I don't know what to do with CM7.
Was it messing with the CPU settings (though I reset all of them in my 20 second window at some point and that didn't help)? If it was the CPU settings, what are some suggestions for what I should set them to if I just start over? I know that not every chip is the same and thus not all of them will respond well to overclocking.
Was it my upgrade to 1.4.1 on the stock OS (why would that effect CM7)?
Is there any way to fix this? Should I just start wipe the card and start over? Any suggestions on what to or not to do next time?
Thanks in advance for your help!

If you are not using Nook Tweaks, download from market. Set minimum to 300 MHz and maximum to 1200mhz. Set scaling to "on demand". Leave or reset CPU voltage settings to the standard settings. Messing with the voltage settings will result in instability, especially if you do not know what you are doing. If there is a "set on boot" setting, enable it. Reboot.
Upgrading to 1.41 has no effect on the SD cm7 install.

hwong96 said:
If you are not using Nook Tweaks, download from market. Set minimum to 300 MHz and maximum to 1200mhz. Set scaling to "on demand". Leave or reset CPU voltage settings to the standard settings. Messing with the voltage settings will result in instability, especially if you do not know what you are doing. If there is a "set on boot" setting, enable it. Reboot.
Upgrading to 1.41 has no effect on the SD cm7 install.
Click to expand...
Click to collapse
Thanks, but I just tried this and it didn't work. I've been noticing that it's hanging most, if not all times, when giving superuser permission in the background, mostly to "autokiller memory optimizer" app. Can this be doing it?
EDIT: Never mind, still crashes/freezes even when no superuser permissions are being granted and with all of hwong96's suggestions in place. Any other suggestions? Thank you.

Uninstall that app and reboot. If system is stable after reboot you have your answer.

[Q] Random Reboots

I've been having some pretty interesting reboots with my Atrix.. they are random, but usually have something to do with spotty service. Sometimes the phone will get really hot and this will cause a reboot, even if i have a temp profile set with setcpu. I honestly don't think the temp profiles work correctly with setcpu. I tried setting a screen off profile set to 456mhz also to maybe clock the processor down to prevent it from getting hot but it didn't help at all either.
I'm currently running Neutrino 2.2GT based on CM7 weekly #6,with faux's 023r kernal overclocked to 1300mhz not uv'ed at all and i'm running the 37p radio.
I've tried flashing a new kernal, full wipe/reflashing Neutrino multiple times, dunno if this is strictly a hardware issue with my phone but has anyone else experienced anything like this?
EDIT: i actually just ran speedtest.net and had a random reboot once during upload, and once during download. i also just changed my apn settings to the default ones posted here: http://forum.xda-developers.com/showthread.php?p=22624940&mode=linear&styleid=16#post22624940