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
Related
Hey all,
I've tried on multiple occasions now to overclock my phone, using both the Trinity & Netarchy (1.1) kernel, everytime I have done so however it will put me into a bootloop, sometimes not getting past the nexus boot animation or lock screen, I'm sure that I'm doing everything right
1. Wipe data/cache
2. Flash ROM (I've tried Stock, Bionic, CM & Modaco, which I use currently.)
3. Boot
4. Flash kernel
5. Boot
I've no idea what's going on, I've just about given up, perhaps I've been handed a crappy piece of silicon, should have returned it before it was too late
Any help appreciated anyways, peacee.
Instead of flashing the ROM and then immediately applying the kernel, let the phone completely reboot. Then go back into recovery and flash the new kernel. Should work.
I've tried this already dude, probably should of mentioned it in my steps cheers anyhows
risegeek said:
I've tried this already dude, probably should of mentioned it in my steps cheers anyhows
Click to expand...
Click to collapse
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?
kenvan19 said:
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?
Click to expand...
Click to collapse
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )
risegeek said:
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )
Click to expand...
Click to collapse
Have you tried Netarchy 1.2 yet? I've had a lot of issues with CM7, including kernels. Sometimes I would have to just flash the kernel 3 times and then it would work. Now I'm using MoDaCo and it is infinitely more stable. I've noticed the trinity kernels tend to be a little more volatile and hit or miss than the Netarchy one seems to be. If it is really of grave concern to you, if you live in an area where a return would be easily possible and if you are within your return period, return it and try a different slice of silicon
I've actually had this phone since release date, sadly I am out of the return period, I don't really mind all that much, this phone has been amazing coming from a constantly slow and crashing iPhone 3G.
I've just downloaded the new kernel from Netarchy, it seems to address stability issues regarding voltage, which I think it might be. I'll flash it and update this post in a second.
EDIT: Hasn't helped seems to be looping at the Google screen now.
Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.
What the heck? I keep hitting edit but it keeps quoting =( please delete.
sanketrino said:
Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.
Click to expand...
Click to collapse
Have you tried Netarchy's kernel? A link to his thread is in my sig and it works great for me. It will boot you to 1GHz then using SetCPU (which can be attained for free on XDA, legally, just search for it. The Dev posted it) you can up the clock speed. You should take note however that the Nexus S is damned fast stock. I typically run my phone at 1.2GHz unless I want to show off to my friends and then I bump it up hehe
EDIT: Thank you also for not posting a new thread about this Its nice to see people using the search function!
Blah please delete.
I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.
sanketrino said:
I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.
Click to expand...
Click to collapse
Odd...for my own testing purposes I've been running at 1.4GHz (testing battery life vs other clock speeds) since yesterday and haven't had a single crash. What ROM are you using?
I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App
sanketrino said:
I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Hmm, I used his 1.1v kernel on MoDaCo but never the new kernel so I can't speak to its stability.
Some phones are able to run up to 1.4-1.5 without issues whereas some aren't due to hardware limitations (different batch,build quality etc).
Most however, from what i read in the forums, are able to clock up to 1.3 with either kernels (CFS or BFS, versions types etc) without facing the issue of random rebootings.
Personally, i'm only able to clock up to 1.3. I'll get random reboots if i run smartbench with a 1.4. Quadrant is fine for me at 1.4 though. Was able to get ~3500-3600 scores but in terms of real life situations, i can't tell the difference between a 1.3 to 1.4.
Hey guys,
seems my thread is still alive I flashed the newest version of netarchy the other day, I can manage 1.2-1.3 quite happily atm - I have to manually use SetCPU after each boot though, if I set on boot it will loop
ah well.
Hi the new app Kernel Manager from HTC Aria Forums this Kernels Work with our Inspire 4G? this Kernels is For Desire HD and other devices but not listed exactly Inspire 4G
Any Testers Allready?
celtichazard said:
Hi the new app Kernel Manager from HTC Aria Forums this Kernels Work with our Inspire 4G? this Kernels is For Desire HD and other devices but not listed exactly Inspire 4G
Any Testers Allready?
Click to expand...
Click to collapse
Wrong section, questions should be in general.
Could you clarify you question a little better?
Its running on mines
Sent from my HTC Inspire 4G using XDA Premium App
Sorry Dude for post Here
Please Move This Post
and allready try this with the Kernel Manager:
I Flashed LorDmod V3.1.3 and OC to 1766.4 with Disabled Perflock
Update: DONT FLASH!! leppie Your touch Screen dont work and you need restore in recovery
other Config. Same Kernel
before 6-8 minutes in this config my phone crash, need put out battery to reset.
celtichazard said:
other Config. Same Kernel
before 6-8 minutes in this config my phone crash, need put out battery to reset.
Click to expand...
Click to collapse
I'd be EXTREMELY careful running your CPU at that speed. 1.5 has been considered "safe" by most people, but anything over that and you're tempting fate. Sure, it's cool to see your phone running at 1.8 or 1.9ghz, but your CPU is going to be forced waaaay out of its specifications and it's possible to damage it beyond repair. This is especially true if you are over-volting. Heat + Voltage = CPU Killers. However, even if you aren't over-volting, it could still draw more power than it was designed to do, thereby increasing heat, overstressing CPU and power supply...
So yeah, be careful.
Thanks man i just OC to this point to se what this phone can do i think this is the first and last High Quadrant can reach becauce later on the day i try to repeat the same benchmark and no reach the 3400 points. I think the CPU was enought stressed and now cant handle 1.9 Ghz. freq. but is cool. Right Now im running with LordMod 4 CFS clocked at 1.3 Ghz and works greathe. this give me 2700 +/- Quadrants and its enought power to make all kind of task and apps running a breeze.
Running any LorDMod kernel results in no wifi for me. I'm being lazy with manually pushing the .ko file though, so I dunno.
WiFi works fine here. Im. Use cyanogen mode 7 with lordmod 4.0
Sent from my Desire HD using XDA App
celtichazard said:
other Config. Same Kernel
before 6-8 minutes in this config my phone crash, need put out battery to reset.
Click to expand...
Click to collapse
what a terrible thing!
I have been looking for a couple of days, and I can't seem to find my answer anywhere. Sorry if this question has already been asked. Does the Tiamat Kernel come overclock already, or do you need to use an app like SetCPU?
SetCPU is needed
Thank Brenardo.
I really want to root so i can get the USB host, and SD card. I just didn't want the overclock. I was told that Tiamat was overclock from the get go.
anovinger said:
Thank Brenardo.
I really want to root so i can get the USB host, and SD card. I just didn't want the overclock. I was told that Tiamat was overclock from the get go.
Click to expand...
Click to collapse
If you do not run an overclock program, the stock max is still on the CPU.
Sent from my Xoom
Do you know what the set Max is on the tiamat kernel?
anovinger said:
Do you know what the set Max is on the tiamat kernel?
Click to expand...
Click to collapse
1ghz
Sent from my Xoom
bwcorvus said:
1ghz
Sent from my Xoom
Click to expand...
Click to collapse
even without an OC app running my CPU sometimes runs up to 1504mhz. I've tried every kernel since the first tiamat one. I have a Canadian xoom rooted with one click. I'm using tiamat 1.4.1 and the issue isn't fixed. I've read many others experiencing the same issue. I've tried using setcpu and Droid OC to limit it to 1ghz but it still hits 1504. There both uninstalled now but I'm still having spikes. Just my 2 cents not trying to hyjack your thread. But if anyone has any input as to whats happening I'd appreciate it.
Also my battery life is significantly shorter since rooting. From about 9 hours to 4 now.
Any suggestions ?
Bandit504 said:
even without an OC app running my CPU sometimes runs up to 1504mhz. I've tried every kernel since the first tiamat one. I have a Canadian xoom rooted with one click. I'm using tiamat 1.4.1 and the issue isn't fixed. I've read many others experiencing the same issue. I've tried using setcpu and Droid OC to limit it to 1ghz but it still hits 1504. There both uninstalled now but I'm still having spikes. Just my 2 cents not trying to hyjack your thread. But if anyone has any input as to whats happening I'd appreciate it.
Also my battery life is significantly shorter since rooting. From about 9 hours to 4 now.
Any suggestions ?
Click to expand...
Click to collapse
How are you seeing its over with no app? I'm not calling you a liar, just trying to get all the facts. In all test we have done, even with the setcpu oc to 1.5/1.5, we actually see the cpu running at 1 ghz after a wakeup.
Sent from my PC36100
bwcorvus said:
How are you seeing its over with no app? I'm not calling you a liar, just trying to get all the facts. In all test we have done, even with the setcpu oc to 1.5/1.5, we actually see the cpu running at 1 ghz after a wakeup.
Sent from my PC36100
Click to expand...
Click to collapse
I'm watching the temp+CPU widget to monitor what's happening. Are you suggesting its giving inaccurate readings? Setcpu at 1ghz would still show random spikes to 1504mhz. I don't have any OC tools installed right now but my widget still shows it hitting 1504 especially under load. I was thinking of returning to stock and rooting manually but it not a huge problem just strange. I was hoping the new kernel would fix it but its still happening. Is there anything I can do besides start from scratch?
Bandit504 said:
I'm watching the temp+CPU widget to monitor what's happening. Are you suggesting its giving inaccurate readings? Setcpu at 1ghz would still show random spikes to 1504mhz. I don't have any OC tools installed right now but my widget still shows it hitting 1504 especially under load. I was thinking of returning to stock and rooting manually but it not a huge problem just strange. I was hoping the new kernel would fix it but its still happening. Is there anything I can do besides start from scratch?
Click to expand...
Click to collapse
Yea setcpu is not 100% yet. Does your widget show both cpus? What we were testing was the second CPU. After you xoom goes to sleep, the second CPU is never set again by setcpu (known bug). So lets say you are running 1.0/1.5. After you xoom goes to sleep you will wake up with cpu 0 at a max of 1.5, but cpu 1 will have a max of 1.0. The info i gave earlier was said wrong. I was actually looking at the wrong line, so you may in fact be correct on the 1.5ghz random jump . Gonna stop talking now, as we are hyjacking someone else's thread .
In theory, you should not need overclocking software, as the max is set at 1ghz on both cpus. But as said above by Bandit504, this may NOT be the case .
Thanks bwcorvus and Bandit504 . So I guess to call it is safe, it would be good idea to use SetCPU, or Droid Overclock and have the maximum set to 1 ghz, to keep the proc from hitting the 1.5 ghz speed. I just hate to ruin the hardware with the overclock, and have to drop another $600 for another xoom.
I have a US Wifi Xoom and I recently flashed a AOSP OC Kernel and I'm scared that my Xoom will mess up. Today I unplugged my Xoom and it shut off by itself. I couldn't turn it back on the normal way. I had to hold volume up and power. I have a feeling its kernel related since I flashed it last night. Thanks.
For the US WIFI Xoom, follow the instructions on this thread to return to stock:
USA WIFI 3.1 Stock:
http://forum.xda-developers.com/showthread.php?t=1080963
Pretty straight forward.
Just out of curiosity, which OC kernel did you use? If you're pushing to 1.6GHz, it may not be as stable as others. There are others - 1.5GHz and 1.4GHz that you can try for more stability.
Tiamat's 1.4.2 Kernels:
http://forum.xda-developers.com/showthread.php?t=978013
Keep in mind though, these kernels are tested rigorously before deployment, so unless you decide to mess with the files themselves, you shouldn't inflict any harm on your XOOM with these Kernels.
I did the 1.5 kernel and I just found it weird because I saw a thread today about someone's Xoom not turning on.
Sent from my PC36100 using XDA App
Hello,
Is that possible to have an added kernel to theTiamat list: one without any OC?
Battery consumption is a big concern for me...
Sorry for the post in here but I'm still limited to Q&A on XDA.
You don't have to overclock even though you flashed an oc kernal. I have 1.6 oc and I don't oc at all.
Is there an option to turn off overclock or is the kernel supposed to work with SetCPU or another OC app?
If OC isn't set as default then that's a good thing because I don't see any advantage to overclocking the Xoom.
It was a scare and I don't want it to happen again. Is prefer the stock kernel to avoid any problems.
Sent from my PC36100 using XDA App
The OC isnt set by default. It is still set to the default 1GHz.
The kernel just allows you to overclock to 1.6GHz if you wish.
I had another weird reboot yesterday. The last thing I flashed was the kernel.
Might do that sometimes. Might be whatever you were doing. Or the xoom isn't used to the kernal, or just plain don't like it.
With the introduction of BRD's latest 1.7 GHz kernel, I thought maybe a poll is in order to gauge how many Xooms are able to handle the higher speeds.
I'm completly stable @ 1400, and mostly stable @ 1500 and 1600. At 15 and 16 if i'm using the stock browser it resets the device. At 1700 I can't do anything.
1.6ghz cpmpletely stable for me. 1.7 is stable for up to 20 mns. until the CPU gets hot and reboots itself
Sent from my Xoom using XDA Premium App
How can I change the speed the CPU is running at? Setcpu won't allow me to go over 1ghz even with 1.4.4 @ 1.7ghz kernel. Newb question I know...
Runs half-stable at 1.7ghz, some graphic artifacts start popping up after 15-20 mins. Riptide kernel @ 1.6ghz ran perfect.
Sent from my Xoom using XDA Premium App
Not development. Moved to Q&A.
cwizardtx said:
Except for the fact that it has entirely to do with development kernels and in no way relates to the stock device. Confused.
Click to expand...
Click to collapse
Development section is only for development, not discussing and asking questions. If you do have something to say about an item being developed you do that in the actuallly thread, not a new one under the development section.
Sent from my Xoom
cwizardtx said:
I sent a PM request to the moderators about this
Would I be completely off my rocker to ask for a [Q] section for people running anything-but-stock?
Personally I wish more people would just post in the right threads that already exist... like if someone runs tiamat 1.4.4 and XYZ doesnt work they should post int he damn tiamat 1.4.4 thread about it but instead they run HERE and post why XYZ doesnt work. Guys like me would like to help but since we're running stock and XYZ probably works fine for us... what are we supposed to say besides "go ask in the right place".
I guess the herding of forum users just has to be done eh.
Click to expand...
Click to collapse
Its really simple. If you are developing something besides and app or theme start a tread in development. If you just wanna chat put in general. If you have an app or theme post in themes and apps. If you have a question it goes in q and a. The only exception is if you have a question relating to a thread already in development or apps and themes, post it in the tread that's already there.
Sent from my Xoom
Back on topic ... mine runs 1.6 perfectly, crashes at 1.7 after about a minute of doing anything.
Sent from my Xoom using Tapatalk
Lambduh said:
Back on topic ... mine runs 1.6 perfectly, crashes at 1.7 after about a minute of doing anything.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Mine runs 1.6 all day long, 1.7 about 3 minutes.
Sent from my Xoom
running strong at 1.6 and loving every minute of it
Holding steady at 1.6. 1.7 was too much....
Sent from my Xoom using Tapatalk
1.7 rebooted me after 3 seconds!!
1.6 is on interactive aaaaall day long and no problem at all.
Sent from my Xoom using Tapatalk
perhaps more interesting information to know is which ones are wifi only and which ones are 3G to see if there is any correlation to the speed and model type.
Psychokitty said:
With the introduction of BRD's latest 1.7 GHz kernel, I thought maybe a poll is in order to gauge how many Xooms are able to handle the higher speeds.
Click to expand...
Click to collapse
Awesome idea with this poll. I was actually wondering about this myself, and am very interested in the results.
I was initially disappointed that I couldn't run 1.7 smoothly, but it now seems that I'm not that bad off, as I have it rock solid @ 1.6.
I run 1.5ghz comfortably, 1.6 might last 5-10 minutes before I get a reboot (with no temp increase) and if I so even as make eye contact with 1.7 I get rebooted.
1.7GHz was stable for a short while and then it locked up and rebooted.
1.6GHz is stable 100% even on very heavy usage for me.
UK wifi only
I use 1.4. It is pretty stable and only reboots once in a blue moon at 1.5.
Reboots once every few hours at 1.6
1.7 crashes within seconds of booting!!
Tbh I don't notice a huge difference going over 1.4 so I'm not too worried.
Sent from my Xoom using Tapatalk
PlinXoom said:
perhaps more interesting information to know is which ones are wifi only and which ones are 3G to see if there is any correlation to the speed and model type.
Click to expand...
Click to collapse
I've been wondering about this as well. I have a WiFi version and 1.6 is perfection, but my Xoom was only able to tolerate 1.7 interactive for about half a day, then started acting funky.
Is it possible that due to the power needs of the modem the 3Gs might be more tolerant at the higher frequencies...or not. I think BRD has a 3G version and hiis has been flying 1.7Ghz. It's something to look at maybe.
Thread cleaned up.
I have deleted the off-topic discussion from this thread.
The fact of the matter is that questions are not allowed to be posted in the development forum, as they hamper actual development by diluting the board. If active development is not underway, it belongs in one of the other sub-forums. If it's a question, it goes in Q&A. If it's a statement / observation, it goes in General. If it's a theme and/or app, it goes in themes/apps. While I see a little bit of a redundancy with being able to ask for help in a ROM / kernel thread and asking in a new thread in the Q&A forum, the Q&A forum is geared more at larger questions that would be distracting to ask in the development section's ROM / kernel thread.
Sorry if this is upsetting to some, but it is the best way to preserve the bread and butter of XDA-DEVELOPERS.
okantomi said:
Is it possible that due to the power needs of the modem the 3Gs might be more tolerant at the higher frequencies...or not. I think BRD has a 3G version and hiis has been flying 1.7Ghz. It's something to look at maybe.
Click to expand...
Click to collapse
I have 3g and 1.7 is unobtainable. However my Xoom is hardly warm when gaming at 1.6!
Sent from my Xoom using Tapatalk