Database Users

Are you using the latest FreshToast? Is com.htc.launcher using 50+% CPU at times?

I've been using FreshToast for a few weeks now, the latest one.
I have it OC'ed with OC Widget as I was having issues with SetCPU as others are.
One thine I notice is that when I wake my phone up sometimes the CPU usage is very very high, for upto about a minute after waking the phone up. To the point where it is unusable.
I have been using "SeePU" for a while, which puts a nice CPU activity monitor at the taskbar. It uses VERY LITTLE to NO CPU usage (confirmed with the adb shell "TOP" command) never more than 2%.
The other issue I'm having is once or twice a day when I get a phone call, the screen comes on but to the HTC Lock screen. When I pull the lock screen down, its usually a blank screen with a FC dialog saying com.android.phone or something is busy. The ring tone keeps ringing and ringing and ringing. I have to do a battery pull.
I've even ran the phone with NO DOWNLOADED APPS to rule out any variables. Its definitely a bug in the ROM.
Are you getting any of the problems I've listed?

The symptoms you describe have been noticed by others using setCpu. Another cause that has been discovered is that when using OC Widget DO NOT enable a different setting when the screen is off as this has been proven to cause the wake-up and phone call problem you described.

system_server is being a real pain for me. I found it may have something to do with the location services.

I had too many problems so I installed the normal Fresh Rom
http://forum.xda-developers.com/showthread.php?t=681856
and then I flashed the OC kernel over that
http://forum.xda-developers.com/showthread.php?t=690238
That combo has been working great for me and is basically what Fresh Toast should be.

I have moved over to Fresh and have been extremely pleased. I think it actually runs faster than Fresh Toast even with correct overclocking(on fresh toast that is). Just remember not to put OC programs on, or it will actually underclock.

SET CPU problems with root?

Aside from being able to Wirelessly Tether my 3G connection from my Vibrant, I wanted to also control my CPU speeds. But with SET CPU, I tend to come across a particular problem. I would underclock to 100000 (min&max) with the screen off, but as a result, the screen won't turn back on and I would have to take the battery off and restart my phone. Clocking it to 400000 (both min and max) screen off leads to the same problem. Is anyone else going through the same situation? If not, what are you setting your CPU to, in regards to both screen on and off?

I have it set to 400MHz max/100MHz min for screen off, and it wakes up just fine so far.
What is your Governor setting? I was told to put it in "Conservative" for Vibrant.

lqaddict said:
I have it set to 400MHz max/100MHz min for screen off, and it wakes up just fine so far.
What is your Governor setting? I was told to put it in "Conservative" for Vibrant.
Click to expand...
Click to collapse
Yeah I have all my profiles set to conservative. Do you guys think it has to do with the priorities, cause I have all of them set to 100.

It could, since there is no telling how to prioritize the settings, hardware/software might get confused.

you know I just noticed I got the same issue, sort of.
I have multiple profiles setup, and one is for charging via USB 800max/100min.
If the screen is off (400max/100min), and I connect the USB cable, guess what happens, three finger salute gets it back, hmmm.

OK I got it working for those who are having the same problem as I. All I did was I made my screen off frequency 200max/100min. For both charging and battery use, I have my cpu set at 1000max/800 min. It works flawlessly and I am noticing an increaSe in battery life...
Sent from my SGH-T959 using XDA App

OverClock?
I used SET CPU on my G1 and really loved the new life it gave my old hardware. I would like to open it up and see what my Sammy Vibe can really do. Is there a way to get some real OVER clocking?
Battery life is really not an issue for me so far.

Halieus said:
I used SET CPU on my G1 and really loved the new life it gave my old hardware. I would like to open it up and see what my Sammy Vibe can really do. Is there a way to get some real OVER clocking?
Battery life is really not an issue for me so far.
Click to expand...
Click to collapse
we need a kernel that will enable it. its apparently not possible on the stock kernel...

I have been having the exact same freezing issue when the screen times out, I'm unable to revive the phone without pulling the battery. I have tried many different setting in Setcpu including those posted here. I finally just uninstalled it and everythings right again. Best to avoid this app for now.

Hey man i did that and i still did not work any other way to set it up.

Vibrant wont come out of Blank Screen
I used Set CPU and put it to the max 1000 and then the max on the other readings it forced closed and after the tmobile and Galaxy animations it goes to a blank screen.

Yeah, I uninstalled it after a week because it was just too unstable. I was getting freezes several times a day, which is unacceptable. Other people might have better luck, but my phone did not like it at all.

So far the only way I can get the program to work 100% is to not have any screen off profile. If I just set it to 1200 max - 200 min / conservative it works fine. Yet once I use profiles and screen off at 100, 200 or 400 it won't turn back on. Every morning it's the same thing, battery pull.

I have similar problem. As long as I am not using "Profiles" at all it is fine. Playing with profiles setting for a while, but not being able to make them 100% stable.
Another thing, if your screen does not come on, you don't have to pull the battery out. Just keep holding on/off button for 5-7 seconds, it'll reboot. It's not a complete freeze, I believe only display system (whatever it is) fails.

Stuck at Recovery Mode
Guyz,
I have firetrap sugar on Spice Mi300. Installed Set CPU.
Tried entering the recovery mode, the phone gets stuck at 1st screen with a line "Enter recovery Mode" displayed on top.
Please help.

SGS continually restarting itself

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

Workaround for mmc_read_failed and mmc_write_failed errors

As many others here I started to have mmc_read and mmc_write errors with my N910F plus freezes and restarts or no boot. For me is another case of programmed obsolescence from our beloved Samy as I previously had with the Note 2 chip bug. I supposed that the problem comes from overheating (from a short-circuit or a failing transistor) and I got confirmed. The phone cpu and gpu go up to 90-100deg Celsius. In case you still want to keep your phone and save money until the Note 8 is out here is a possible workaround:
- In case you get mmc errors when flashing with odin you have to take out the battery an keep them both somwhere cool for 15 minutes. Then flash immediatly after starting in download mode, before is heating again.
-If you managed to boot and root you can install Kernel Adiutor or something similar and keep the processors at a max frequency around 1000MHz .
For me it worked and after 2 weeks of testing all kinds roms with repartitioningn, nand erase etc. I have a working if little less performant phone for a week now.
Edit: Device Control is another app that seem more stable and it has a thermal dedicated control over CPUs. Even with intensive use the phone doesn't freeze now. It still needs to be cool to boot.​*I also flashed RamKernel and I don't know it KernelAdiutor works with factory kernel.
Edit2: Wakelock app with level 4 setting > 3 days and going with no lag and no restart. So maybe all above is wrong...

Serious performance, battery drain, and freezing issues. I suspect a problem with ART

I have a Samsung Galaxy Tab 2 10.1 GT-p5113. I asked for help on that device's forum and got no attention. I flashed unlegacy-android 7.1 and s1mple-espresso kernel several months ago. About 3 months ago, it suddenly started having issues. I had not made any changes to the device for several months, but it just started happening one day. The system would lag really badly (completely unusable) unless I set the CPU governor to anything other than interactive. Even the powersave governor performed better than interactive. The system also would not put the CPU to sleep, so the device had severe standby battery drain and even got warm while in "standby." Unfortunately, wakelock detector apps could not find anything, so I just lived with it. A week ago, I decided not to put up with it anymore and flashed Omnirom 7.1 without the custom kernel. I currently have the default kernel that comes with the ZIP file. It worked perfectly for a bit, but the issues came back after running Omnirom for a week. Just yesterday, a new problem appeared. Every few minutes, the device will almost completely freeze. Navigation buttons and volume keys also stop working. However, the power key still kinda works. The screen turns on and off but does not lock. It works properly when the device isn't frozen. The freezes last from a couple seconds to a minute, and then the device will react to all of the input its been given in that time as if it was all done in one instant. I usually get an app not responding dialog for the active app after the incident. In apps written in C/C++ such as Minecraft and SimplePlanes, only the UI freezes but the rest of the app keeps going. This leads me to believe it is a problem with the Android Runtime that interprets and compiles Java code. I can't figure out why, but the freezing issue almost completely goes away if I disable kernel samepage merging. Wiping cache and dalvik/art cache does not fix the issues.
TLDR:
The device (Samsung Galaxy Tab 2 10.1 espresso10wifi GT-p5113) lags to the point where it is unusable if the CPU governor is set to interactive. Even powersave performs better than interactive.
The device does not put the CPU to sleep (resulting in unacceptable levels of standby battery drain), but I can't find any wakelocks. I don't currently have any workarounds other than powering off or plugging in the device when it is not in use.
ART freezes for a few seconds to a minute every few minutes, but disabling kernel samepage merging seems to almost completely fix it.
Wiping cache and dalvik/ART cache does not fix any of this, and it seems to follow me when I change ROMs.

I can't do this anymore. Going back to marshmallow.