kanaida
Android Expert
Hey guys. The reason I think these governors like SmartAssV2 and Interactive aren't exactly working as we would think is the fact that:
a) They don't enable/disable the second cpu core on demand. In fact no governor that I can think of except hotplug does this at all if I remember right (let me know if you find otherwise). This is the job of the mpdecision service, my optimizer app disables this when set to manual 1 Core or 2 Cores. Auto enables it again. This is why the cpu speeds stick with my app without modifying lg scripts. The thermald daemon also has some control and will try to slow down an overheating cpu and shut down the phone. (By the way, my pc crashed. Drive corrupted. That's why I haven't been able to update. My key that i use to sign the app is mangled and i haven't found another copy. Luckily the source was ok though. Without the key I can't update my app on the market)
Also for P.G: I've narrowed down my reboots to mostly be during 2 specific events. When I unlock the phone (and the cpu probably ramps up quickly). Or when I've got about 30% or less battery and I take a picture using the LED Flash. This leads me to believe that the processor might be slightly under-volted, maybe even out of the factory. I have a strange feeling that the voltage regulator might not be able to keep up 100% of the time with the speed goes from 0% -> 100% cpu @ high clocks. Starving the cpu of current until it shuts off, then starts up again. The only way I would think that this could be fixed is to make the difference in voltage less volts between the lowest and highest values so it swings up and down smaller amounts.
Can you tell me what values your kernel is using for it's various cpu speeds? I haven't quite figured out how to interpret in the cpu source file yet.
1 Bug left:
-Bluetooth pairing is busted. Same like we ran into with the LG Esteem before. Last time it was someone theming the settings.apk or something. Anyone got a settings.apk they can post that isn't crashing when pairing?
a) They don't enable/disable the second cpu core on demand. In fact no governor that I can think of except hotplug does this at all if I remember right (let me know if you find otherwise). This is the job of the mpdecision service, my optimizer app disables this when set to manual 1 Core or 2 Cores. Auto enables it again. This is why the cpu speeds stick with my app without modifying lg scripts. The thermald daemon also has some control and will try to slow down an overheating cpu and shut down the phone. (By the way, my pc crashed. Drive corrupted. That's why I haven't been able to update. My key that i use to sign the app is mangled and i haven't found another copy. Luckily the source was ok though. Without the key I can't update my app on the market)
Also for P.G: I've narrowed down my reboots to mostly be during 2 specific events. When I unlock the phone (and the cpu probably ramps up quickly). Or when I've got about 30% or less battery and I take a picture using the LED Flash. This leads me to believe that the processor might be slightly under-volted, maybe even out of the factory. I have a strange feeling that the voltage regulator might not be able to keep up 100% of the time with the speed goes from 0% -> 100% cpu @ high clocks. Starving the cpu of current until it shuts off, then starts up again. The only way I would think that this could be fixed is to make the difference in voltage less volts between the lowest and highest values so it swings up and down smaller amounts.
Can you tell me what values your kernel is using for it's various cpu speeds? I haven't quite figured out how to interpret in the cpu source file yet.
1 Bug left:
-Bluetooth pairing is busted. Same like we ran into with the LG Esteem before. Last time it was someone theming the settings.apk or something. Anyone got a settings.apk they can post that isn't crashing when pairing?
