Develop Bugs

Random cpu spikes?

Okay. Set cpu clocked at 833 mhz. Stock kernal, rom, ect. Not when i just let my phone sit at the home screen, it will settle to 245 mhz, 1% cpu usage. Then it will go to 8-9%, and back up to 833 mhz. Im perplexed. Im using temp+cpu pro to monitor this btw.
I like running for saftey!

Are any background processes hoof on during the times it spikes ie syncing or background apps running?
Sent from my Incredible using XDA App

None. On watchdog everythings showing 0.3 % or less when its doing it. Watchdog refreshes every 3 minutes, but it happens too often to be watchdog
I like running for saftey!

I noticed you had another thread on profiles.....are you not using profiles still? And if so I'm not really sure what would be causing this besides either a bug in your copy of setcpu or your kernel.....I would try maybe flashing a different kernel....give one with bfs a try....your phone may work better with the different scheduler to help a lot when the CPU will run at certain speeds.
Sent from my Incredible using XDA App

I have no profiles set. Im about to go back to stock. I cant figire out wtf is going on.
I like running for saftey!

I mean before removing root I would definitely at least try another kernel first....it couldn't hurt and I feel like it might fix it.
Sent from my Incredible using XDA App

Been absent from the G2 scene, need suggestions.

Ive been using CyanogenMod for a while now and for the most part satisfied. Im running 7.0.3 and occasionally experience a few hiccups or oddities. For example, at work I will enable wifi. If I am out of range of the wifi for a while with it still enabled my phone will overheat and shut off. Sometimes wifi calling won't work. I had to restart my phone a few days ago because data wasn't working, but the icon appeared on the notification bar. I'd like to know what other ROMs I should try that may fix these annoyances. Also would it be worth checking out radios? Battery life is decent, but if theres a ROM i should try to get more battery life please recommend it. I can get 8-10 hours, about 1 hour total of tethering and wifi enabled for 5. I'm only overclocked to 1.2Ghz.

The 7.0.3 official is over a month old. Since then many improvements were made and bugs fixed, so I recommend the latest nightlies.
Regarding battery life, your max is 1.2 GHz but what is your min speed? Also, are you using an app like SetCPU or CM's built-in setting? What governor are you using?
Also, it probably makes more sense to post your questions in the official thread.

c00ller said:
The 7.0.3 official is over a month old. Since then many improvements were made and bugs fixed, so I recommend the latest nightlies.
Regarding battery life, your max is 1.2 GHz but what is your min speed? Also, are you using an app like SetCPU or CM's built-in setting? What governor are you using?
Also, it probably makes more sense to post your questions in the official thread.
Click to expand...
Click to collapse
min is 800mhz, governor is on demand. I wasn't aware they were still doing nightlies.

Ive been getting decent battery on Super CM7... just dont use setcpu

master.peterm said:
Ive been getting decent battery on Super CM7... just dont use setcpu
Click to expand...
Click to collapse
Is it SetCPU thats draining my battery? I'll try going tomorrow with it uninstalled. Any suggestions about my data? Sometimes I'll have to restart my phone after having wifi on for 5 hours to get my data to work. Sometimes my wifi calling doesn't work until I restart. Would flashing a radio mod work?

legato89 said:
min is 800mhz, governor is on demand. I wasn't aware they were still doing nightlies.
Click to expand...
Click to collapse
That's an unnecessarily high min, for sure that's one factor for why your battery life isn't so good. Current draw scales roughly linear with CPU speed, as seen in this study. I get by just fine having a 245 MHz min.
Also, SetCPU conflicts with CM's built-in settings if you have both "set on boot". Like master.peterm, I also prefer CM's built-in CPU controls over SetCPU.

legato89 said:
min is 800mhz
Click to expand...
Click to collapse
Why would you want 800MHz min? AFAIK that's the non-OCd max on the G2.
Unless you keep CPU hungry applications running all the time this is going to eat your battery away.

Nexus reverts to 700 mhz max CPU speed.

Ok so for the past 2 AOKP builds (the latest nightly and M1 both Jellybean) i have had this weird issue where upon boot, the CPU would be capped at 700Mhz. so i went into ROM control, set it to 1200 and made sure "set on boot" was on.
eventually, even without a reboot, it woud revert back to 700 MHZ. so i checked my other apps that can controll OC/UC. Franko kernal app, and ROM toolbox were both set at 1200 and not set on boot. so ROM control was in charge of the CPU.
yet, no matter what i do, after about 4 hours on use it reverts back to 700 mhz.
this happened on the included Faux kernel and Franko's latest milestone kernel.
anyone else experiencing this? know what causes it?

On CNA and get the same thing. It's horrible because it will lock up my phone.

Bumping Cuz it happened again. This is the most annoying thing I have come across.

Some of these phones are really picky. Try another rom and see if the problem persists.

tgyberg said:
Some of these phones are really picky. Try another rom and see if the problem persists.
Click to expand...
Click to collapse
*whimpering* b...b....but... I.. like this rom...
BTW, I am on CNA with popcorn kernel which is different than the op so I feel like it's a deeper issue.

CNA kangs literally everything from everyone (not saying that in a derogatory sense).
AOKP has this bug as well, and I'm sure it's being worked on on their side...which CNA will then cherry pick.

I had this before,Download nofrills cpu from play store and set the desired freq,your problem will
Be solved.
Sent from my Galaxy Nexus using Tapatalk 2

I've been using CNA 3.5 and had no problem with the max CPU setting to 700Mhz until i started playing around with all of the settings in the start-up tweaks, Kernel controls, color hack presets, and color gamma tuning. I changed all of the settings back to default and have not had the issue since then (18 hours). I have slowly started enabling all of the tweaks one at a time to see what was causing the max CPU to set at 700MHz.

max boot speed to 700mhz is defined in init.tuna.rc, if i recall it correctly.
Sent from my i9250

tried changing the kernel !
I used CNA 3.5 and 3.6.6 Still the same issue.
Tried Trinity Kernel too it did help for sometime but still it reverts back to 700mhz..
Is there any fix yet.... I really Love CNA so i prefer to stay on this rom.
My friend using PARANOID ANDROID has never experienced such an issue.
Hope it is fixed soon
Thanks

I'm having the same issue on CNA 3.6.6. Even when I set it back to 1200mhz it still never goes above 700 mhz.

I'm having the same problem. On CNA 3.8 right now, but have had the same problem on other custom rooted ROMs based off of cm. I finally figured out that it reverts back to 700 MHz during phone calls--or maybe not every phone call, not sure on that part. All my calls recently have bumped it down. At least now I know when it's switching. Just installed the no frills cpu--hopefully that'll help until this bug gets fixed.

Major battery problems

I observed my battery first with regular use (mainly just twitter and texting, not much gaming or data usage, ie. YouTube) and I find that the battery drains about 10%~hour, or maybe even more.
Right now I'm in Buffalo and I put the phone airplane mode so I won't get charged with receiving texts (data off means better battery right?) but even with data off, I still get crazy battery drains. my phone needed a charge at 15% and it hasn't even reached 10 hours on battery, and most of the time, my phone wasn't being used. Am I doing something wrong?
Here is my settings:
- Stock rooted Bell ROM
- Faux 013u Kernel
- OC Min/Max: 1ghz/1.8ghz
- Brightness: Auto
I can't really thing of anything else that may affect the battery a lot. :/
Sent from my SGH-I747M using xda premium

Unless your doing gaming, which by your post, your not...why do u feel the need to over clock? Try under clocking. Hell I under clock to 800mhz and notice NO performance decrease, other than the browser not loading pages as well.
Few suggestions;
When using a tw ROM give the power saver a go
Don't over clock. That was cool in like, the hero days lol
Try out aokp, I get the best battery life with aosp ROMs....no tw crap to bog it down
Use auto brightness
Turn vibration off
Use CPU spy to ensure your phone is sleeping properly

Well, occasionally I do play games which by my experience run much smoother with OC. I use setcpu and I used the screen off profile and make sure the CPU sits at around 700 MHz, and I'd expect that to help (which it does a bit), but it doesn't help with the overall problem.
Now with your AOSP suggestion, is it safe to flash it on a Canadian I747M? (As in, I wont be getting random ATT Device Manager registration crap, etc.) Which ROM (+ kernel) would you specifically suggest?
And with the whole gaming thing put into consideration, I'd like to keep the OC since I like smooth games, but is there a way to counterbalance that for battery? Undervolting, CPU editing, etc. All the help would be greatly appreciated.
Sent from my SGH-I747M using xda premium

Lte hsdpa switching may have caused the problem.
I got this problem occasionally but not once after I disabled lte since last week.
Sent from my SGH-I747M using Tapatalk 2

johnafer said:
Well, occasionally I do play games which by my experience run much smoother with OC. I use setcpu and I used the screen off profile and make sure the CPU sits at around 700 MHz, and I'd expect that to help (which it does a bit), but it doesn't help with the overall problem.
Now with your AOSP suggestion, is it safe to flash it on a Canadian I747M? (As in, I wont be getting random ATT Device Manager registration crap, etc.) Which ROM (+ kernel) would you specifically suggest?
And with the whole gaming thing put into consideration, I'd like to keep the OC since I like smooth games, but is there a way to counterbalance that for battery? Undervolting, CPU editing, etc. All the help would be greatly appreciated.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Loose the kernel...trust me on that use toonz I'm ocd 2.1 and still get 20 hrs
Sent from my SAMSUNG-SGH-I747 using xda premium

also what is your signal bars like before airplane mode
plus it seems like you have a rogue app.

Why is your minimum soo high? Keep it at 384 or switch to Ktoonz kernel and go down to 96mhz. You can also lower your voltages to save battery.

Well, if there is the possibility of a rogue app, the only Alps that I could think of would be LightFlow along with SMS Popup.
But is my screen usage normal? 70% is a bit much no? Or is that just me?
Sent from my SGH-I747M using xda premium

[Q] Trinity Kernel settings

I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?

I had similar issues. Not flowing very well , reboots and crashes. Also even though I bought the trinity app changing the clock speeds made the phone very very unresponsive. Tried many times to install it but no luck. Swapped back to Franco / glados (tried air kernel which was nice for battery but a bit laggy)
Franco also has trinity settings you can play with
J
Sent from my Galaxy Nexus using xda app-developers app

Me personally had a better experience than Franco. But all the phone are different and some might like trinity and some might like Franco. Seems like yours like Franco more
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz

Personally I've had ridiculously good results with Trinity - with 384 GPU, not 512 (1536-384-Stable35). Absolute butter even when I have very resource heavy, multiple, tasks running - and havn't had a forced reboot, freeze or anything of the sort even once. Interactive/SIO, min 307, max 1190. Everything else on default (except screen colours/gamma which I changed to my liking).
That said, if the 384 GPU is also not working for you I suppose you can give Franco or the other kernels a try, every phone set probably responds a little differently to each kernel.

cmstlist said:
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
Click to expand...
Click to collapse
What trinity kernel are you using? I am on trinity 384 Alpha 56 and it is butter smooth... even get great deep sleep with it.
Sent from my Galaxy Nexus using xda app-developers app

cmstlist said:
I reflashed stock JB kernel the other day and found my phone to be running very smoothly. But I can't stand the colours on my purply screen, so back to Trinity (latest stable release).
The problem is, I'm getting a lot of lag and jerkiness on Trinity. Google Now takes forever to load, responsiveness takes a hit, and it generally feels like that whole "Project Butter" has turned into cold chunks of margarine.
I did buy the Trinity app to change settings. Is there anything I should be doing with Trinity that would give me stock-like smoothness and performance? I have a feeling there is some default setting in Trinity that is supposed to be helpful for some users but for me it's just killing the experience.
Or alternately, would I get better results with Franco?
Click to expand...
Click to collapse
try using supersu instead of superuser. also, update your busybox. a lot of people have issues with root apps obtaining su slowly with superuser on jelly bean, which leads to lag.

I have good flow with trinity kernels. No lag or unresponsivness
*Who needs a gs3 when you have a NEXUS*

simms22 said:
try using supersu instead of superuser. also, update your busybox. a lot of people have issues with root apps obtaining su slowly with superuser on jelly bean, which leads to lag.
Click to expand...
Click to collapse
Already doing both, thanks for the input.
I'm using 1344/307 and I also previously tried 1536/384. My phone seems to have some overheating issues so I don't want to crank it too hard... Just want to get close to stock performance.
I'll try interactive / sio. Are those essentially what the stock kernel uses?
Sent from my Galaxy Nexus using Tapatalk 2

cmstlist said:
Already doing both, thanks for the input.
I'm using 1344/307 and I also previously tried 1536/384. My phone seems to have some overheating issues so I don't want to crank it too hard... Just want to get close to stock performance.
I'll try interactive / sio. Are those essentially what the stock kernel uses?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i like ondemand/deadline. overheating.. whats your cpu temperature? most think that their devices are overheating when it falls in the normal range. tkt comes with widgets(in the app drawer widget menu), put the no background cpu temp widget on your homescreen and youll also get a cpu temperature reading in your status bar. at 100C the thermal throttle will kick in to lower your cpu speed and cool down your device. the safety shutdown temperature is 110C, your cpu will automatically shut down at that point. 110C is only reachable if you turn off the thermal throttle in the tkt app and you are benching your phone at a high oc. otherwise, i wouldnt worry about overheating.

The other thing is I get lockups every day or three. Today I rebooted the phone and plugged in the charger while it was rebooting. The moment the screen went off the phone was locked up. Power button would not respond. Unplugging/plugging the charger did not light up the screen. Had to do a battery pull.
In fact this happened again a second time in a row. Is there a reason the phone is locking up immediately after boot if I have the charger in? I'm trying it again a third time with the charger out, letting the screen auto-sleep before I touch the phone. Okay apparently it has nothing to do with the charger.
EVERY time I start the phone up now, if I don't unlock the screen myself before it auto-sleeps, the phone locks up and auto-reboots again. WTF??

cmstlist said:
The other thing is I get lockups every day or three. Today I rebooted the phone and plugged in the charger while it was rebooting. The moment the screen went off the phone was locked up. Power button would not respond. Unplugging/plugging the charger did not light up the screen. Had to do a battery pull.
In fact this happened again a second time in a row. Is there a reason the phone is locking up immediately after boot if I have the charger in? I'm trying it again a third time with the charger out, letting the screen auto-sleep before I touch the phone. Okay apparently it has nothing to do with the charger.
EVERY time I start the phone up now, if I don't unlock the screen myself before it auto-sleeps, the phone locks up and auto-reboots again. WTF??
Click to expand...
Click to collapse
are you undervolting at all? which yrinity kernel are you using? did you happen to use franco kernel before using trinity? try using a different charger too, ive had similar issues with a certain charger before too, until i started using a different charger.

Despite the fact that I disabled "Set On Boot" in Trinity Kernel Toolbox, it does seem I'm still set to interactive/sio on boot. And check out the logcat I captured over USB when I was doing a reboot and it locked up:
http://pastebin.com/sSe9eFXT
In particular to trim out just the TKT lines and the last few lines before lockup:
Code:
D/TKTBootHelper( 1853): TKT: Boot Completed
D/TKTBootHelper( 1853): TKT: Set file permissions.
V/LockPatternKeyguardView( 299): Set visibility on com.android.internal.policy.
[email protected] to 8388608
V/LockPatternKeyguardView( 299): Set visibility on com.android.internal.policy.
[email protected] to 8388608
D/TKTBootHelper( 1853): Current Version: 3.0.38-04149-g1d1c555-dirt00:23:38|
D/TKTBootHelper( 1853): Previous Version: 3.0.38-04149-g1d1c555-dirt00:23:38|
D/TKTBootHelper( 1853): TKT: Versions match, let's restore settings.
E/vpnapi ( 1672): Function: Connect File: AndroidIPCSocket.cpp Line: 172 failed
to connect fd=38: Connection refused
E/vpnapi ( 1672): Function: Run File: LocaleChangeMonitor.cpp Line: 140 Invoked
Function: AndroidIPCSocket::Connect Return Code: -26476533 (0xFE6C000B) Descrip
tion: ANDROIDIPCSOCKET_ERROR_CONNECT_FAILED
So it would seem that right after TKT says "let's restore settings" it locks up, if the screen is off, when set to interactive/sio. Huh?

simms22 said:
are you undervolting at all? which yrinity kernel are you using? did you happen to use franco kernel before using trinity? try using a different charger too, ive had similar issues with a certain charger before too, until i started using a different charger.
Click to expand...
Click to collapse
See my post immediately after yours.
No undervolting at least that I know of. I tried cranking max screen off frequency up in case that was the cause, and tried going back to default CPU settings. Still does the same upon reboot.
But I can confirm that if I uninstall TKT completely and boot with Trinity Kernel, there is no screen-off lockup. Whatever settings were being restored by TKT were causing the phone to freeze if the screen was off. I'll leave it at that for now and give it another go when it's not so lovely and sunny outside.

cmstlist said:
See my post immediately after yours.
No undervolting at least that I know of. I tried cranking max screen off frequency up in case that was the cause, and tried going back to default CPU settings. Still does the same upon reboot.
But I can confirm that if I uninstall TKT completely and boot with Trinity Kernel, there is no screen-off lockup. Whatever settings were being restored by TKT were causing the phone to freeze if the screen was off. I'll leave it at that for now and give it another go when it's not so lovely and sunny outside.
Click to expand...
Click to collapse
delete the data for the tkt app(main phone settings, apps). dont use set on boot, its usually not a good idea. my screen off is set to 307. if you are overclocking, you have to disable smart reflex mpu or you will freeze and reboot if not other issues. turning off smart reflex is very important if raising the cpu speed. otherwise the device will try to automatically set the voltage too low for the cpu speed and itll cause freezes/reboots.

simms22 said:
delete the data for the tkt app(main phone settings, apps). dont use set on boot, its usually not a good idea. my screen off is set to 307. if you are overclocking, you have to disable smart reflex mpu or you will freeze and reboot if not other issues. turning off smart reflex is very important if raising the cpu speed. otherwise the device will try to automatically set the voltage too low for the cpu speed and itll cause freezes/reboots.
Click to expand...
Click to collapse
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2

cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
does your rom have its own cpu settings? maybe theres something enabled in there?
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
smart reflex is a built into stock, it controls your voltages. the thing about it is that it doesnt know overclock or undervolting, so if you overclock or undervolt, it restores voltages for stock cpu speeds. which causes freezes if youre trying to overclock by setting the voltages too low.

simms22 said:
does your rom have its own cpu settings? maybe theres something enabled in there?
Click to expand...
Click to collapse
Stock yakju Jellybean flashed straight from Google image files, with the exception of Trinity.
Sent from my Galaxy Nexus using Tapatalk 2

cmstlist said:
Stock yakju Jellybean flashed straight from Google image files, with the exception of Trinity.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
did you try clearing the tkt data, or uninstalling it and reinstalling it? honestly, this is the first time ive seen this behavior. do you have any other cpu control apps installed?

cmstlist said:
I didn't overclock and I didn't undervolt. What is smart reflex?
Set on boot was DISABLED, let me emphasize. Yet the logcat shows TKT restoring settings, followed up very soon with a lockup.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes, set on boot is for critical settings only, like frequency policy and voltages.
All trivial settings are always restored as they were set.
What ROM are you on? I jumped into the middle of this page and missed it.
Side note, if it's settings being restored, clear the app data using the option in the menu.
Sent from my SGH-T999 using Tapatalk 2

simms22 said:
did you try clearing the tkt data, or uninstalling it and reinstalling it? honestly, this is the first time ive seen this behavior. do you have any other cpu control apps installed?
Click to expand...
Click to collapse
No I do not. I will try reinstalling now since I uninstalled it completely.
morfic said:
Yes, set on boot is for critical settings only, like frequency policy and voltages.
All trivial settings are always restored as they were set.
What ROM are you on? I jumped into the middle of this page and missed it.
Side note, if it's settings being restored, clear the app data using the option in the menu.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Again, pure stock flashed straight from Google, except for Trinity.