Crash on changing CPU performance settings.

[jmo707]

Since beta3, each time I want to change the CPU governor or adjust the OC/UC values, the application crashes. Android suggests to close it sometimes, sometimes it directly forces a reboot. I've a Motorola Defy+ with CM11, Quarx nigthly from 25/09.

[Blechd0se]

Once again, thanks for the report. Can you give me a logcat by any chance? I am almost 100% whats causing the issue, probably my new su-shell can't handle it on the defy, but i would like to see confirmation about this.

[jmo707]

Here, this is what alogcat gives with "aero" filter. Maybe I should filter something different?

I/ActivityManager( 4243): Killing 6671:com.aero.control/u0a29 (adj 9): remove task I/ActivityManager( 4243): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.aero.control/.SplashScreen} from pid 6338 I/ActivityManager( 4243): Start proc com.aero.control for activity com.aero.control/.SplashScreen: pid=7376 uid=10029 gids={50029, 1028, 1015, 1023} D/ActivityThread( 7376): com.aero.control black listed for hwui I/ActivityManager( 4243): START u0 {cmp=com.aero.control/.AeroActivity} from pid 7376 W/ActivityManager( 4243): Activity pause timeout for ActivityRecord{42091360 u0 com.aero.control/.AeroActivity t14} W/ActivityManager( 4243): Activity stop timeout for ActivityRecord{42091360 u0 com.aero.control/.AeroActivity t14} W/ActivityManager( 4243): Activity pause timeout for ActivityRecord{42091360 u0 com.aero.control/.AeroActivity t14} W/ActivityManager( 4243): Activity stop timeout for ActivityRecord{42091360 u0 com.aero.control/.AeroActivity t14}

[Blechd0se]

You could filter for exceptions. Or just post the last bits of logcat. Dont worry if you can't get it, as i said, i am almost 100% certain i know why its derping.

[jmo707]

That makes you pretty sure about it ^_^ Ok, I'll concentrate on reporting about the other issue then, and maybe starting that translation I talked about :p

[jmo707]

I don't know if this is relevant, or another bug, but the Statistics tab won't show anything except the predefined values (Deep Sleep, 300, 600, 800, 1000), no matter which kind of OC/UV I use. I'm pretty sure that in previous versions this wasn't happening at all.

[Blechd0se]

Yea thanks, i tested it and my guess was right; the new su-shell had a bug during on-boot and especially with output from the su shell. This should be fixed now, at least on my local builds. Once again, thanks for the feedback.

[jmo707]

I can confirm that the crash issue when changing frequencies is solved on my device. I have yet to fully test the persistence of changes across reboots. Thanks for fixing this =)

[borekon]

So you can close the issue, can't you?