• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

For those having stabilty issues (reboot during sleep)....

colchiro

Extreme Android User
The issue has been identified and James Sullins has a fix: Gerrit Code Review

Interactive and Ondemand are the two de facto governors used on most Android devices. Ondemand has some performance penalty on arm architectures so interactive has become more popular. I would prefer to stick with interactive governor if 384mhz doesn't cause a noticeable loss in battery life.

The real reason for the crashes/reboots are due to the user space audio library we are using. The DSP is getting in an unrecoverable state. Raising the minimum frequency seems to help workaround some unknown timing or race condition. Using 384mhz as the minimum will hopefully just be temporary until we fix the real issue.

If you don't want to install the latest nightly, simply setting your minimum speed to 384 using whatever app you used to OC. (I use setcpu, but there are similar free apps.)
 
Going to flash the 6-9 nightly and see how much has changed. Looks like the CM9 HP/TP team is really kicking ass!
 
jcsullins said:
The real reason for the crashes/reboots are due to the user space audio library we are using.

I wonder if this is fixed in the 6-20 nightly.

Just installed 6-20 and set my min speed to 192. We'll see how this goes.

Update: One hour on this puppy with 4 email accts and wifi turned on.... 1% battery used, 85% sleep, the rest is 192 mhz. NO REBOOTS!
 
Had a little instability (one reboot) with 0630 nightly (reboot while sleeping), which seemed better with the min speed set to 384.

Running 0704 nightly with latest jcSullins audiolibs and wifi driver and min speed back to 192 and it's pretty good. Heard good things about the wifi like it's working with access points that didn't work before. Haven't tried any sound or mic apps tho.
 
Posted Today, 06:04 PM
jcSullins said:
Sorry guys, I was a little lazy and just dropped the adreno2xxdrivers_new.zip (that someone else had created) into the testing dir without double-checking it.
What I merged was obtained directly from Qualcomm. I just checked and the files that were merged match the files in adreno2xxdrivers.zip (nice catch gor).

I've removed adreno2xxdrivers_new.zip from testing/ and uploaded adreno2xxdrivers.zip (which should match what's in the next nightly).
 
Back
Top Bottom