Yep. The 1.7.20 build seems to have fixed the issue of the screen remaining off at the end of the call. Thanks mantera!
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [KERNEL] TheOC v1.7.20 kernel for MT Isaac & TG based CM7
- Thread starter mantera
- Start date
-
- Tags
- motorola triumph
Yep. The 1.7.20 build seems to have fixed the issue of the screen remaining off at the end of the call. Thanks mantera!
TheBritton
Resident Galaxy Cat
Yes!! Awesome work, mantera!! 
Chairshot215
Android Expert
I haven't seen that particular bug but flashed over to the kernel a few days ago and had not had any issues until forgetting to turn off wifi for about an hour today and lost about 30% in power. Battery monitor widget is showing suspend as the culprit.
PieFromTheSky
Newbie
I tried using the latest OC kernal on Tickerguy's Final Beta v.08 and I believe I found a bug. I could not get the accelerometer in my phone to function in any way. I did a factory reset and that didn't solve the problem. I then flashed an older version of the OC kernal and the acceleromiter was working again. I also flashed the newest version of the OC kernal over Whyzor's final CM7 build and the accelerometer worked great. I know this doesn't matter very much because Tickerguy's build is old but I thought I would let you know Mantera. Thanks for all the hard work!
garrmack
Member
I'm surprised you didn't have more issues than just the accelerometer. Mantera included most of Whyzors updates to his kernel in the latest TheOC. Those changes were made to coincide with Whyzor's CM7 updates, not guaranteed to work on older versions of CM7...
Is there a reason you're running Trickerguy's version instead of TG Reloaded?
I too have experienced the same issue with beta 8 and this new kernel. I run tickerguys because i cant stand adwlauncher. I prefer what I have now.
PieFromTheSky
Newbie
I was having a number of problems with TG reloaded that I couldn't find a solution for. I was experiencing a lot of random reboots and the new GPU drivers weren't working with all of my games. I decided to go back to Tickerguy's build because it has all the features I need and is incredibly stable.
BTW the latest OC kernal includes the new drivers right? For the short period of time that I had it installed over Tickerguy's build I was not having any problems with games that usually don't work on the reloaded build. Other than the accelerometer not working of course
RedAnt
Well-Known Member
I was not overly fond of adw either. But I played with it for a few days, then tried Go Launcher. I liked the Go product better and never went back. Without the adw incentive I probably would not have tried others.
Now that I am using Go Launcher I am in no hurry to jump to ics. Last I knew you needed to use a 3rd party launcher, so I would be using go there too. At least now I have a working camera and decent battery life!
Thanks for the report. It doesn't surprise me that it doesn't work 100%. There's been a lot of updates to cm7 since TG's Beta 0.8. The kernel itself would work fine but the ramdisk has been updated to the most current files.
Yes.
You know you can switch to a different launcher right?
The Trebuchet launcher works just fine. Some people prefer the 3rd party launchers but as with any rom, it's a matter of personal taste.
Yes it will. TG-reloaded is an Isaac/TG based cm7.
thanks! although I'm not sure which one to use. Miui or cm7 cuz i want good performance AND good battery. Which one would u recommend?
Personally, I've found cm7 to be a little better on battery than miui. As for performance, for the stuff that I do, they're about the same but ymmv depending on what you do.
Of course, for the visual effect, a lot of people like miui.
would u mind sharing ur settings for voltages? ur governor? did u overclock or underclock? I'm sorry if I'm asking for too much.
I just use the default governor and i/o scheduler in the kernel--which currently is interactive and SIO. My current clock settings are 122 - 1.5Ghz. I'm not undervolted at all at this time (I switch roms too much to worry about that). But if you want to try undervolting, you can start out with the "Less aggressive" table that I have listed in the OP and then go from there. When I was undervolting, the "Less aggressive" table of values was the one that worked the best on my particular phone; obviously ymmv.
D
Deleted User
Guest
is there a way to remove some of the CPU clock steps? 64mhz is useless for listening to music, and 245/368 lag on home screen. something like 122 then 460 is the next step. also have you tried this?
Brain F*ck Scheduler - (BFS)
This scheduler is designed to be simple and speedy tailor
specifically for user interface type systems such as
desktop/smart phone devices where user interaction is
MORE important than serving 1 million web requests (CFS,
the default scheduler) at the same time (think of nimble
desktop workstations vs large corporate servers).
found here
OpenSense ICS,CM9/CM7(v001_r2/v029)OC~1.73GHz/UV/SLQB[Mar-25] - Sensation 4G Development - RootzWiki
Brain F*ck Scheduler - (BFS)
This scheduler is designed to be simple and speedy tailor
specifically for user interface type systems such as
desktop/smart phone devices where user interaction is
MORE important than serving 1 million web requests (CFS,
the default scheduler) at the same time (think of nimble
desktop workstations vs large corporate servers).
found here
OpenSense ICS,CM9/CM7(v001_r2/v029)OC~1.73GHz/UV/SLQB[Mar-25] - Sensation 4G Development - RootzWiki
There's not a user setting to remove certain steps. The only way is to recompile the whole kernel. As for 64 mhz being useless, you can set the minimum value to whatever value that you want and the kernel will never use the frequencies below that; some people like having 64 available.
As for 245/368 lagging on the home screen, what governor are you using? When I had 245 as my minimum, depending on the governor, the only time that I noticed that was when waking up from sleep. If I gave it a few sec to wake up, then it no longer lagged.
thangfish
Android Expert
I've had my bottom speed set to 64 ever since it's been an option, and listening to music works fine. Lag is not an issue for me either.
dsmryder
Android Expert
It should, but we have made some changes to the kernel to improve perfomance. I think you might be better off leaving the kernel alone.