Database Info

[Q] Tiamat 1.4.1 on WiFi only Xoom overclocking on it's own

Correct me if I am wrong. My understanding Tiamat 1.4.1 do not suppose to overclock to 1.5GHz on it's own, unless I will use something like SetCPU?

Correct. That said, the overclocking was not created by tiamat, it was pulled from another kernel. They are actually talking about removing it at this time, due to MANY users reporting the issue you are having.

well my xoom has no problems with the OC and i love it. I would just tell you and everyone else to get setcpu so you can control the speed. if you want to use the OC use it if you do not then don't. I just hope they leave it in there.

[Tiamat kernel 1.4.1) Random reboots on Xoom

Hi all,
I've been having random reboots/freeze-ups ever since I rooted.
This happens regardless of whether I am OC'ed or at 1ghz. These reboots tend to happen when watching Youtube or when browsing.
Would just like to have a feel of the ground if any of you who are rooted experiencing this?
Maybe we can start off by stating the following:
Kernel:
Clock Speed:
OC app: Setcpu or Droid OC
Governor setting: Interactive, on-demand etc..
Last app you were in that caused reboot:
For me, I am on the following:
Kernel: Tiamat 1.41
Clock Speed: 1ghz or 1.2 ghz
OC app: Setcpu
Governor setting: Interactive
Last app you were in that caused reboot: Youtube, browser
Im not sure if this thread shld belong here but since this is Dev where most of us root and OC, I thought I'd ask it here and hopefully we spot some trends with regard to the reboots.
Pls dun flame me Thanks!

wrong section

Moved to Q&A.

I have the same issue - Canada WIFI version

same problem, Canadian WiFi Version.
Not sure if it's because I flashed 1.4.0 then flash 1.4.1 to get the external sd card to show up. But I noticed after I got the external sd card to work, my usbOTG started working too, but from what I've read that should have been removed in 1.4.1 for stability issues.

Same issue. Using the tiamat kernel. It happens with different apps so its not any one for me.
Sent from my Xoom using XDA App

Switch to Droid oc and delete setcpu. Worked for me. Interactive. On demand is junk on Xoom. I use on demand on DroidX.
The kernel will Max to 1504 causing reboot (on some Xooms). Some device can't handle 1504, mine included. Superuser will throw up an occasional user permission for Droid oc as it brings the MHz back down to user setting.

I was experiencing random reboots with the same kernel, mostly just browsing in Dolphin HD. I first stopped OC in setcpu but the reboots still occurred. Then I uninstalled/reinstalled Flash 10.2 and cleared Dolphin's data.
So far, it seems to be much more stable and even battery usage has toned down.

This shouldn't have been moved to Q&A. There is enough discussion at this point on this exact topic that it needs to be addressed. There is a serious problem with the over clock in the tiamat kernel and/or the software that is supposed to govern the overclock. The developers here work very hard for all of us to get the most out of our devices and I fully support them in their work, but we are putting ourselves at risk. It is my understanding that SETCPU and Droid Overclock are only able to govern One of the Dual Core processors while the other is overclocked all the time. There is a widget in the Marketplace (Temp+CPU V2) that will enable you to monitor your clock speeds.... See for yourself.
Sent from my Xoom using Tapatalk

I installed temp+CPU and don't see two cores. Only one display for MHz and it cycles from 216 to 1200. Is there a screen I'm missing?

crauzz said:
This shouldn't have been moved to Q&A. There is enough discussion at this point on this exact topic that it needs to be addressed. There is a serious problem with the over clock in the tiamat kernel and/or the software that is supposed to govern the overclock. The developers here work very hard for all of us to get the most out of our devices and I fully support them in their work, but we are putting ourselves at risk. It is my understanding that SETCPU and Droid Overclock are only able to govern One of the Dual Core processors while the other is overclocked all the time. There is a widget in the Marketplace (Temp+CPU V2) that will enable you to monitor your clock speeds.... See for yourself.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
This is right where it should be... Development forum is for developing...Discussing does not go there unless its in a thread where something was developed...The tiamat crew knows all about it...they did not make the overclocking, they used someone elses, and are about to remove out. And yes you are correct on the 2nd core.
Sent from my PC36100

bwcorvus said:
This is right where it should be... Development forum is for developing...Discussing does not go there unless its in a thread where something was developed...The tiamat crew knows all about it...they did not make the overclocking, they used someone elses, and are about to remove out. And yes you are correct on the 2nd core.
Sent from my PC36100
Click to expand...
Click to collapse
Remove it? So no more overclocking? Can't a ROM allow OC and voltage control? But I guess it always comes back to the lack of source code.

Mandelbrot.Benoit said:
But I guess it always comes back to the lack of source code.
Click to expand...
Click to collapse
Kernel source is available. It's the rest of Honeycomb that isn't.

So what is the best resolution to the problem? I get at least 5-6 reboots a day...I dl'ed Droid OC and deleted setcpu.

I had a harder time getting it to reboot with Droid OC so I think that's your best solution for now.
Sent from my Xoom using Tapatalk

ruvanist said:
So what is the best resolution to the problem? I get at least 5-6 reboots a day...I dl'ed Droid OC and deleted setcpu.
Click to expand...
Click to collapse
Flash back the stock kernel.

solarnz said:
Flash back the stock kernel.
Click to expand...
Click to collapse
This is probably the best thing to do. If you think about it; Can't be good if your device is rebooting all the time, plus it's just too annoying.
Sent from my Xoom using Tapatalk

crauzz said:
This is probably the best thing to do. If you think about it; Can't be good if your device is rebooting all the time, plus it's just too annoying.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Where can I find the stock kernel? Is it available in xda? Cos i did not back it up.

ruvanist said:
Where can I find the stock kernel? Is it available in xda? Cos i did not back it up.
Click to expand...
Click to collapse
Yes. Go here > http://forum.xda-developers.com/showthread.php?p=13178555
Sent from my Xoom using Tapatalk

Kernels

Can anyone explain to me what kernels are what is their function? I noticed that the update did not change my kernel. Is that a bad thing that they did not include a new one in the update? Also I am voinv to be installing xboarxers stock. Rom first to root the phone and I want know if I should chance the kernal and what effect it will have. I am taking small steps because want to understand what I am doing. Thank for any help you guys can give me.
Sent from my LG-P999 using XDA App

The kernel is the lowest point in the system. It controls how the software communicates with the hardware: how the CPU behaves, how the buttons behave, how the screen functions, etc.
The main use of custom kernels is to Overclock and Undervolt. OC means pushing your CPU to be faster than it was ever intended to be; you get better performance but if overclocked too long, it will be damaged. Worst case scenario, you will literally melt your motherboard. But this is only a danger if you leave it overclocked 24/7 and constantly push the CPU to its limits (playing 3d games for instance)
Faux's kernel can OC to 1.5 GHz and Morfic's can OC to 1.1.
The next common use is Undervolting, which means giving your CPU less electricity than it would like. This again is extremely dangerous if not done properly, but yields noticeably better battery life. Morfic's is the best for UV IMO, though you cannot change the undervolting, he has it locked into what he has found to be the best. And this isn't necessarily a bad thing, as too much UVing will cause potentially serious stability issues with the device. It's not nearly as dangerous as improper OCing (it won't permanently ruin the hardware) but it is a danger. Faux's lets you UV to your heart's content.
Faux's is better if you want performance, because it has higher OC. Morfic's is better if you want battery life, because it has better UV and the CPU clock speeds themselves are better tuned for lower speeds than higher ones.

I absolutely love my faux kernel. its at 1.4 and amazing battery life. The screen sensitivity is awesome. Honestly its all prefrence.... I won't go away from cm7w/ faux
Sent from my LG-P999 using XDA Premium App

http://en.wikipedia.org/wiki/Kernel_%28computing%29
I'd start here. Or just google info on the linux kernel (since that's what android runs on top of.)

Can you flash faux kernel on top of bionix 2
Sent from my HTC Sensation Z710e using XDA App

When you flash a kernel, you just need to know what the base of it is to pick the proper one. There are really only 3 bases at the moment:
1. Stock 2.2 That'd be faux's .5, and I know morfic has some older 2.2 based kernels in his thread.
2. Stock 2.3 (Which faux is working on now, there are a couple floating around)
3. CM7 Faux and morfic both have kernels that work here. (2.3.4 and 2.3.5 based roms use this, miui, and of course cm7 )
Bionix is based on 2.2 (Which I haven't actually checked, but I'm sure it's in the first post.)
For most of them, just read the first post, or even the title. It'll say what it's based on, and then you can flash whatever you want. Just always do a nandroid backup before, you never know if you might for whatever reason have to flash back. If you don't, you need to reinstall your rom (or manually change the kernel and modules, of course) to get back to what the rom came with.
Happy flashing.

If i am running stock rooted GB OTA, can I flash faux's latest Kernel 006 with ext4?? Or do you have to have an ext4 rom to be able to flash ext4 kernels?
Thanks.

Thanks a lot that shed some light on. The subject
So it appears that the dev will tell you which mernels arw compatible with their rom in the thread for that particilar rom. If I want to use eglesblood which is 2.3.4 or.5 xan I use tbe stock kernel? Also what is the difference between the .3 .4 and .5 in the gingerbread make is that carrier specific or moel specific like the blackbwrry 8520 is for tmo and 8530 is for sprint?
Sent from my LG-P999 using XDA App

2.3.4 and 2.3.5 are based on cm7 code, so you'd use the cm7 based kernel. (LG hasn't given us 2.3.4 or 2.3.5).
As far as ext4, it's a different file system is all. Faux's kernels mount the data and system partitions as ext4, but don't actually convert them. Morfic's do a full convert. Ext3/4 support is in the kernel, not the rom, so as long as the kernel supports it you can do it. (Which every custom kernel I've seen supports ext4)
If you want more information, google is your friend. Here is a pretty simplistic explanation of the ext2,3,and 4.
http://www.thegeekstuff.com/2011/05/ext2-ext3-ext4/
As for the differences, 2.3.3 to 2.3.4 had some major framework changes. 2.3.4 to 2.3.5 seems to be only minor bugfixes. If you want full changelogs, I'd google them.

So if I want to use eglesblood then I have to change the kernel too? Do I have to do it separately or is it included in the rom?
Sent from my LG-P999 using XDA App

You never *need* to change kernels. Using the kernel that comes with the roms works just fine. Only time you need to change kernels is if you want to overclock, (never really saw the point in it, and quadrant benchmarks are useless.) want tun or cifs support, undervolting, ext4, etc.
If you don't need any of those things, or don't know what they are, just stick with the kernel that comes with the rom.

Okay that's cool so all I have to do is put EB on my SD card and flash away I am thinking about starting simple first with either xboarders stock or tweeked
.
Sent from my LG-P999 using XDA App

[Q] overclocking inspire 4g

I'm new to the forums here and I just installed CM7 on my phone the other day. Ive been trying to overclock my phone but every time after I install it, the phone is so unresponsive that I have to reload CM7 again because its unusable. The bottom home and menu buttons don't work either. Does anyone else know why this is happening or the solution?

Overclocking is built into cm7. You don't need any other app
Sent from my SAMSUNG-SGH-I777

How are you trying to overclock it? What are you setting it to? What type of governor are you setting? Mine locks up when I use SmartassV2.

http://forum.xda-developers.com/showthread.php?t=1103414

i personally use the tiamat kernel and setcpu to overclock on cm7, since the stock cm7 kernel only goes to 1.5, but still even without overclock cm7 is never unresponsive or "unusable".

I've had mine oc to 1.2ghz and min is all the way down on ondemand setting. Im using absolution right now and I'm not seeing the greatest of battery life like i did with cm7 and talonace's kernel. but I just turned off all animations on the phone today so I'll update you tomorrow

I actually underclock with CM7 and it's still snappy and responsive. Slows down a bit when syncing, but otherwise it is solid even when clocked under stock.

[Q] Noob questions on G2X OC/UV...

I recently rooted my P999/G2x and installed CM7.1.0.1, and am extremely happy with it. Am looking to tinker just a *little* bit more, but have some questions... I have LOTS of answers on the forums, but am somewhat skeptical about the currency of some of the information out there (let's face it, stuff changes fast!). So, down to it:
Kernels:
- Did CM7 overwrite the stock kernel?
- I understand the benefits to changing the kernel; what about drawbacks?
- Does CWM back up your kernel with Backup and Restore? If not, how do you do this?
- Recommendations on a good, reliable kernel to use w/ CM7? I am looking at faux123's CM and morific's Trinity. Thoughts?
OC/UV:
- Can you OC on stock/CM7 kernel?
- What is the best app to manage OC/UV? I have my eye on setCPU, cpu Master, and Android Overclock (JRummy16)
- Any recommended settings for the G2x? Any settings to avoid? My plan is to incrementally adjust, but don't really have an idea as to where to start.
Thx in advance!

- Did CM7 overwrite the stock kernel?
Yes
- I understand the benefits to changing the kernel; what about drawbacks?
Since not all the chips are made in the same way, you could soft brick your phone if you try to flash an undervolted kernel. This is the way mine is, and it's somewhat irritating but not all that bad using the stock voltage and overclocking to around 1.4ghz rather than 1.5ghz+. Also, battery life should be expected to be less with an overclocked CPU. It's up to you to decide how you want to run your device.
- Does CWM back up your kernel with Backup and Restore? If not, how do you do this?
Yes, backup creates an image of the entire thing. Before you start making changes, always make a backup so you can revert to previous settings should you soft brick your device. Make a backup, clear cache/dalvik, flash the kernel and reboot the phone. First boot times will always be a little longer when flashing a kernel, so be patient and don't pull your battery right away. For me personally, if it hasn't done anything noticeable after about ten minutes, I pull my battery. Reboot into recovery and restore from the backup you made. If you started off trying an undervolted kernel, time to try the standard voltage now!
- Can you OC on stock/CM7 kernel?
No, and you'll be able to tell once you flash CM7 and use SetCPU (or whatever you use) and see the max is still at 1ghz.
- What is the best app to manage OC/UV? I have my eye on setCPU, cpu Master, and Android Overclock (JRummy16)
Personal preference. I think probably SetCPU is used by most people including myself.
- Any recommended settings for the G2x? Any settings to avoid? My plan is to incrementally adjust, but don't really have an idea as to where to start.
If you want to be safe just start out at 1ghz. If you have no random reboots with your kernel then move it up to 1.1 or 1.2 and see if it's stable there. Personally, I just went ahead and overclocked to 1.4ghz. For the most part people don't really have problems with this I guess. The problems usually lie in whether or not you are undervolted and by how much. If you find your device can run an undervolted kernel, I would just leave the undervolt settings the way they are. As I said, I can't run OC/UV and have to use SV, so I never touch any of the voltage settings.
Hope this helps!

Using eagle blood (cm7 based) with faux kernel.
I heard trinity kernels may have random reboot but don't quote me on that.
Try faux kernel with oc/uv. Its very good, latest is 0.48. But if you go with the ds version (debaouch?) The battery percentages are all over the place... Lol one minute its 50% the next it may be 34%...
Use set cpu. I've uv additional 25mv across the board with no I'll effects. Screen off profile at 503 mhz max and some other profiles will have you getting 24hours easily with normal usage.
Make sure test it out before you "set on boot"...
Sent from my LG-P999 using XDA App

I tired using DS OC/UV Kernel Version 0.4.8 kernel on my g2x running the latest stable release of CM7 1.0.1. Followed all the necessary step of wiping cache, and darvik but when I reboot, I get the blue lg sign after which the screen just black out and its stuck like that till i pull the battery out. Any one know what I may be going wrong here? ? ?

Trinity ELPmax with Phoenixblood is the best combo. Trinity batterylife is amazing. When i leave the house my phones battery is 100%. 11 hours later (I when i make it home) my battery is always under 60% but never less then 40%. I play music as soon I leave the house, and till I get in the house. I also turn of data when not using and have setscpu set to 900mhz max and screen off profile set to 432 max 216 min.
Just my personal results

e4e5nf3nc6 said:
- Did CM7 overwrite the stock kernel?
Yes
- I understand the benefits to changing the kernel; what about drawbacks?
Since not all the chips are made in the same way, you could soft brick your phone if you try to flash an undervolted kernel. This is the way mine is, and it's somewhat irritating but not all that bad using the stock voltage and overclocking to around 1.4ghz rather than 1.5ghz+. Also, battery life should be expected to be less with an overclocked CPU. It's up to you to decide how you want to run your device.
- Does CWM back up your kernel with Backup and Restore? If not, how do you do this?
Yes, backup creates an image of the entire thing. Before you start making changes, always make a backup so you can revert to previous settings should you soft brick your device. Make a backup, clear cache/dalvik, flash the kernel and reboot the phone. First boot times will always be a little longer when flashing a kernel, so be patient and don't pull your battery right away. For me personally, if it hasn't done anything noticeable after about ten minutes, I pull my battery. Reboot into recovery and restore from the backup you made. If you started off trying an undervolted kernel, time to try the standard voltage now!
- Can you OC on stock/CM7 kernel?
No, and you'll be able to tell once you flash CM7 and use SetCPU (or whatever you use) and see the max is still at 1ghz.
- What is the best app to manage OC/UV? I have my eye on setCPU, cpu Master, and Android Overclock (JRummy16)
Personal preference. I think probably SetCPU is used by most people including myself.
- Any recommended settings for the G2x? Any settings to avoid? My plan is to incrementally adjust, but don't really have an idea as to where to start.
If you want to be safe just start out at 1ghz. If you have no random reboots with your kernel then move it up to 1.1 or 1.2 and see if it's stable there. Personally, I just went ahead and overclocked to 1.4ghz. For the most part people don't really have problems with this I guess. The problems usually lie in whether or not you are undervolted and by how much. If you find your device can run an undervolted kernel, I would just leave the undervolt settings the way they are. As I said, I can't run OC/UV and have to use SV, so I never touch any of the voltage settings.
Hope this helps!
Click to expand...
Click to collapse
+1 to everything you said
just to add if you want to over clock then go with faux or trinity. the cm7 kernel is faster then both @1000mhz, if speed is what your looking for without the dangers of oc. The stock cm7 kernel also lacks the ability to under volt soo battery life might not be as good though

Rbern144 said:
I tired using DS OC/UV Kernel Version 0.4.8 kernel on my g2x running the latest stable release of CM7 1.0.1. Followed all the necessary step of wiping cache, and darvik but when I reboot, I get the blue lg sign after which the screen just black out and its stuck like that till i pull the battery out. Any one know what I may be going wrong here? ? ?
Click to expand...
Click to collapse
Format data/ factory reset.
Wipe all cache.
Format system. (don't forget)
Flash cm.
Flash kernel.
It may take a while for the system to boot, 5 min. Let it load, and reboot, enjoy.
Sent from my LG-P999 using XDA App