• 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

I have had issues with my min set at 122 when set on both my main and screen off profiles. Nothing serious, it will often freeze up or run crazy slow for a bit after turning on the screen. Seems to happen less using InteractiveX than when I was using ondemand. Setting the main profile at 244 why still keeping the screen off min at 122 seems to take care of this issue with my phone. Either way I didn’t notice any difference in my batteries overall life staying with a 244 min as long as my screen off profile is still set at 122, seems to be what makes the difference in battery life is my screen off profile.
 
OK, so I have been running this for a couple days (CM7) last night, it started acting strange, had to reboot 2 times, then, this morning, the light was flashing like I had an email, went to check but had "No service" rebooted (usually fixes this) and it started boot looping, did this 2 times, finally I pulled the battery, it booted up, but it was like it was reset, it had the LWP that comes standard on CM7, and I was missing a few apps.

So, I wiped EVERYTHING, reinstalled CM7 (beta 8) got everything up and running again, installed this kernel, set to 1024/245 interactiveX and I was getting random reboots, along with the occasional boot loops. Went back to CM7 kernel, and it hasn't boot looped, or rebooted yet.
 
idbl_fanatic said:
OK, so I have been running this for a couple days (CM7) last night, it started acting strange, had to reboot 2 times, then, this morning, the light was flashing like I had an email, went to check but had "No service" rebooted (usually fixes this) and it started boot looping, did this 2 times, finally I pulled the battery, it booted up, but it was like it was reset, it had the LWP that comes standard on CM7, and I was missing a few apps.

So, I wiped EVERYTHING, reinstalled CM7 (beta 8) got everything up and running again, installed this kernel, set to 1024/245 interactiveX and I was getting random reboots, along with the occasional boot loops. Went back to CM7 kernel, and it hasn't boot looped, or rebooted yet.
Click to expand...

That's definitely strange behavior. Did you install something right before this started happening?

You said that you "got everything up and running again". Does that mean that after you reinstalled Beta 8, you restored your data again? So does that also mean that your phone was working ok until you restored data? IF that was the case, then please try to narrow down what app or data you restored before it started having random issues.

Did you undervolt? If so, did you clear all the undervolt settings to make sure nothing was residual?

Unfortunately, I have not seen this behavior. If you can narrow down what happened, I can try to reproduce the issue and then go from there.

Also, did you try the v1.1 kernel and are you still having the same issues?

Thanks for your help in figuring out what is happening to you.

Edit: I added a flashable zip in the OP to reset Incredicontrol voltage settings in case you were trying to undervolt. It should delete all residual Incredicontrol scripts and settings that may be still hanging around.
 
mantera said:
That's definitely strange behavior. Did you install something right before this started happening?

You said that you "got everything up and running again". Does that mean that after you reinstalled Beta 8, you restored your data again? So does that also mean that your phone was working ok until you restored data? IF that was the case, then please try to narrow down what app or data you restored before it started having random issues. When I got it up and running, I had restored everything apps/data using Titanium, and it works fine with the stock kernel.

Did you undervolt? If so, did you clear all the undervolt settings to make sure nothing was residual? I have no idea how to do this, so no.

Unfortunately, I have not seen this behavior. If you can narrow down what happened, I can try to reproduce the issue and then go from there.

Also, did you try the v1.1 kernel and are you still having the same issues?

I did not try the 1.1, I mean I did in the past, and come to think of it, I didn't have any problems with it. I will give that a try again and see what happens.

Thanks for your help in figuring out what is happening to you.

Edit: I added a flashable zip in the OP to reset Incredicontrol voltage settings in case you were trying to undervolt. It should delete all residual Incredicontrol scripts and settings that may be still hanging around.
Click to expand...

See above, thanks for the help.
 
idbl_fanatic said:
One more thing I noticed, and it is doing it with 1.1 as well, my WiFi and GPS will enable at random times.
Click to expand...

It definitely sounds like something that may be specific to your phone or an app that you have installed then because I have not seen that happen on my phone.

I wonder if anyone else is seeing that as well?

The only other thing I can say is, if you want, try running just the base cm7 and gapps with v1.1 or v1.5 to see if you issues still happens just to prove if it's an app/software issue or not.
 
mantera said:
It definitely sounds like something that may be specific to your phone or an app that you have installed then because I have not seen that happen on my phone.

I wonder if anyone else is seeing that as well?

The only other thing I can say is, if you want, try running just the base cm7 and gapps with v1.1 or v1.5 to see if you issues still happens just to prove if it's an app/software issue or not.
Click to expand...


Ok, I will continue to run 1.1 the way I have it for now, for a day or so, and see what happens, then I will try that, if needed.

Thanks for all the hard work!!
 
Thanks for this kernel, even though it's called theOC, I don't overclock, I use it to adjust voltage & min/max frequencies, which the stock kernel doesn't allow. Can someone link to exactly what the touchscreen driver update is? The only issue I notice with my MT is sometimes the first touch or swipe action gets ignored, like when coming out of sleep to pattern swipe unlock. This kernel (v1.5) still has that issue.

Otherwise having 2 touchpoints "snap" together as they're about to cross each other's axis is still there, seems like it's using a software fix to get around a HW limitation with the inversion axis bug on many devices.
 
Whyzor said:
Thanks for this kernel, even though it's called theOC, I don't overclock, I use it to adjust voltage & min/max frequencies, which the stock kernel doesn't allow. Can someone link to exactly what the touchscreen driver update is? The only issue I notice with my MT is sometimes the first touch or swipe action gets ignored, like when coming out of sleep to pattern swipe unlock. This kernel (v1.5) still has that issue.

Otherwise having 2 touchpoints "snap" together as they're about to cross each other's axis is still there, seems like it's using a software fix to get around a HW limitation with the inversion axis bug on many devices.
Click to expand...

Here's the commits by Isaac regarding his updates to the touchscreen driver:

https://github.com/ikarosdev/triump...b54204e2eb7674d79c79a6df257f3bf8b656#comments

https://github.com/ikarosdev/triumph-kernel-msm7x30/commit/ad5cee330e17fc4e04ecf5d1132894128d28adc6

And the Triumph does not suffer from the axis inversion bug to which you're referring. It does "snap" together when the two points cross each other's axis, but that's a different bug.

As for your first swipe sometimes being ignored, it sounds like the phone/kernel is still in the process of waking up from sleep at those times and is just lagging.
 
mantera said:
As for your first swipe sometimes being ignored, it sounds like the phone/kernel is still in the process of waking up from sleep at those times and is just lagging.
Click to expand...

Sounds like what I had commented about above, in my case I found this to happen when I dropped my minimum frequency down to 122. Not as bad in my case using either the Smartass or Interactive Governors but I would still notice the lag now & again. Can
 
dsmryder said:
I'm still using wip 1.4. I haven't changed kernels yet. Maybe I'll do it tonight?? I don't run juicedefender, and I don't kill processes. I just go to my home screen and turn it off. Now I can honestly say the screen is the hungryest part of my phone. I have been playing around with the auto brightness settings lately. I've turned off the buttons under almost all steps. And under the lowest ambient lighting, the buttons are a 4. The lowest they will actualy trun on.
Click to expand...

In my understanding and someone please correct if I'm wrong but isn't turning a process off as described above the same as killing it. My understanding and from what I have read is Auto-killer ends processes the same way Android does naturally when it needs to make more memory available and is better than just turning them off. Now I am assuming that what is meant by homscreen in the above comment is the Manage Apps Tab when pressing the Menu button or am I drastically missing something and there is a way of stopping a process from the home screen without killing it? Asking out of curiosity as new things I didn
 
I guess I'm glad to see my phone isn't an oddball and can overclock to 2GHz. Probably won't ever do it again... but I'm glad I have the option. Thank you for making the kernel!!!!
 
Well this is odd, I was trying to determine what the stabile undervolt for my device is, and I've managed to decrease all 122 Mhz - 1024 Mhz to 650 (the minimum IncrediControl allows) and it's running fine. I verified the values in file: /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels:

122880: 650
245760: 650
368640: 650
460800: 650
576000: 650
652800: 650
768000: 650
806400: 650
921600: 650
1024000: 650

I'm using latest v1.5 kernel. Is there a bug in that these voltage values aren't actually sticking or am I just lucky to have such a processor?
 
Whyzor said:
Well this is odd, I was trying to determine what the stabile undervolt for my device is, and I've managed to decrease all 122 Mhz - 1024 Mhz to 650 (the minimum IncrediControl allows) and it's running fine. I verified the values in file: /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels:

122880: 650
245760: 650
368640: 650
460800: 650
576000: 650
652800: 650
768000: 650
806400: 650
921600: 650
1024000: 650

I'm using latest v1.5 kernel. Is there a bug in that these voltage values aren't actually sticking or am I just lucky to have such a processor?
Click to expand...

If you hit apply and it sticks at those level, I think you're just that lucky... When I try it, mine locks up and reboots faster than you can say WTF!.
 
klehman215 said:
In my understanding and someone please correct if I'm wrong but isn't turning a process off as described above the same as killing it. My understanding and from what I have read is Auto-killer ends processes the same way Android does naturally when it needs to make more memory available and is better than just turning them off. Now I am assuming that what is meant by homscreen in the above comment is the Manage Apps Tab when pressing the Menu button or am I drastically missing something and there is a way of stopping a process from the home screen without killing it? Asking out of curiosity as new things I didn
Click to expand...
 
dsmryder said:
That, and I need to convince my wife to allow me to mess with her phone too.;)
Click to expand...

LOL. I know the feeling. I finally convinced her when I showed her MIUI. That and when I showed her how I can make a nandroid backup and restore everything back to exactly how the phone was before I make any changes.
 
mantera said:
If you hit apply and it sticks at those level, I think you're just that lucky... When I try it, mine locks up and reboots faster than you can say WTF!.
Click to expand...

I got those freezes & reboots right after apply a few times too, but only when the values were closer to stock (higher than my final 650 values), like when I press the 'all decrease' button a few times. Which leads me to think it may actually have to do with some values are not compatible at certain frequencies rather than the undervolt crashing the system.
 
Whyzor said:
I got those freezes & reboots right after apply a few times too, but only when the values were closer to stock (higher than my final 650 values), like when I press the 'all decrease' button a few times. Which leads me to think it may actually have to do with some values are not compatible at certain frequencies rather than the undervolt crashing the system.
Click to expand...

On my phone, when I was doing my original testing, I was only changing the voltage on one frequency at a time. Basically, my phone just doesn't seem to have the same flexibility in voltage range as yours. :( You wanna trade? LOL. :D
 
mantera said:
LOL. I know the feeling. I finally convinced her when I showed her MIUI. That and when I showed her how I can make a nandroid backup and restore everything back to exactly how the phone was before I make any changes.
Click to expand...

How is a nandriod backup soppose to be done? When I did mine, I lost all of my... uh, user data. I had to log into my games and I lost my texts.

On the text note, I did find a good program for that.

I was hoping it would be like an image. Something like Windows 7 or acronis'.
 
You must log in or register to reply here.
Back
Top Bottom