[Tiamat kernel 1.4.1) Random reboots on Xoom

ruvanist

Member
Oct 12, 2009
27
0
0
Singapore
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!
 

ertw96

Member
Oct 27, 2010
20
9
0
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.
 

Mandelbrot.Benoit

Senior Member
Nov 12, 2010
523
105
0
Missoula
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.
 
Last edited:

dewed

Member
Oct 23, 2010
5
0
0
Austin, TX
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.
 

crauzz

Member
Oct 15, 2009
39
0
0
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
 

bwcorvus

Retired Forum Moderator
Jun 15, 2010
1,527
369
0
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
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
 

Mandelbrot.Benoit

Senior Member
Nov 12, 2010
523
105
0
Missoula
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
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.
 
Last edited:

crauzz

Member
Oct 15, 2009
39
0
0
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