Hey guys,
I have the Lightspeed 1.0.7 ROM w/ Thor's 3.9R3 kernel installed. I have my tab overclocked to 1.5 Ghz and I'm noticing random reboots the 3rd day which is weird because i never had reboots the first 2 days.
I noticed it after I open the system tuner app. does this have anything to do with the kernel? Or app?
Thanks
I have the same issue with system tuner on Thor's 14.1 using the 3.9R3 kernel. Also
using SetCPU to undervolt so I thought they may be conflicting or its just a glitch in the app. It usually crashes even if I don't change anythind just leave it on the CPU tweaks tab. I think I remember it happening on Taboonay 2.2 but I forget which kernel I was using at the time.
Related
Hey, quick question: I am on mytouch 4g cm7 ROM
What is a safe max to set the overclocking at? Obviously I don't want to burn the chip, but I want to make it as fast as possible. I have LauncherPro, currently my max is at 1.4, but sometimes it lags when I gesture to expand home screens.
I have 7 Home screens, all of them have 1 or more widget..
Thanks
1.5 is a good speed but you really wanna avoid charging when its set that high. so when charging set it to 1.2. Also what Kernel are you using? Defaults on Faux123 ASOP kernel should do well. I'n still on T-Mo stock and i run defaults with Faux123 Sense Kernel and i have no lag at all so CM7 whit its optimized code and no bloat it should run like a dream with one of his kernels, no OC Needed
Edit: corrected Link
http://forum.xda-developers.com/showthread.php?t=957267
Will the Kernel you linked to work with CM7 rc3? It only mentions CM6
Nm, Cm7 is the gingerbread...see it..got it, thanks!
I kept mine at 1.2ghz. Never gave me a problem.
sent from the rooty tooty fresh and fruity cm7 nighly powered G2
So I flashed 2.3.0 , then like the thread says, before rebooting, I flashed 2.4.3 stock version.
However, I am getting a wi-fi error. I saw some posts on it, and they said to "fix permissions". So I did that, yet still seeing a wi-fi error.
So for now, I restored my backup, but I would really like to have this kernel, do you know what I am doing wrong or what I can do to fix it?
Thanks
My mistake i linked the wrong Kernel here you go.
http://forum.xda-developers.com/showthread.php?t=957267
Yeah, I did use that link, however as described above, the wifi is giving me an error..any idea of a fix or what I am doing wrong?
I was getting the same issues. Then I reflashed the rom, rebooted before turning wifi on and had no problems. Also have had no problems set at 1.75 max and .75 min on minmax. Have been using that setting since faux started making his kernels (cm7 amd froyo based) and have never froze once. Quadrant scores for the new evil dhd ext 4 rom at 2900.
Sent from my HTC Glacier using XDA App
On Nook Color Tweaks, I can only tweak the audio settings. The book and CPU settings don't work. When I try to overclock with nook tweaks, it tells me that "Kernel is not compatible with CPU settings. A newer build of Dalingrin's overclock kernel is required".
I'm running the CM7.1.0 RC1 encore with 2.6.32.9 erick at myhost #87 kernel.
Sorry for the ultra noob question, but please help.
Thank youl.
I don't think you are running dalingrins newest kernal. I'm pretty sure it is not the default kernal for RC1.
Sure for dalingrin and download and flash his 6-30-2011 kernel for the nook.
Sent from my NookColor using XDA Premium App
I'm not sure if that's the right kernal michael.
Might need to get the one before that. If I remember correctly, the rc-1 came out before he adjusted the kernal for the more recent nightlies.
2.6.32.9 seems to be the Dalingrin's OC 063001 kernel, at least on my NC.
Suggestion: it won't hurt if you re-install just the kernel (060301)
I'm running cm 7.0.3.-encore from a sandisk class 4 16 gb card. I've tried updating rom with rom manager to 7.1.0-RC1. Rom manager reboots into recovery mode but never updates the rom. I also dl'ed the 6/30/11 dalingrin oc kernal, put it on the sd boot, and reboot but nothing is updated. Therefore I'm unable to update or overclock the Nook.
Re: my earlier problem, I was eventually able to flash 7.1.0-RC1, install a newer kernal with oc capabilities and oc my Nook. However, I had so many problems with disappearing icons, lockups, etc. that I went back to 7.0.3.-encore. It is much more stable, if a little slower, on my setup.
Ok, so here's the story:
I was running oxygen+franco.kernel, and was suffering from loads of random reboots, as well as the oxygen signal dropping bug.
While I was looking for the source of the problem, I wiped the phone back to B138, and re-installed oxygen without the franco.kernel. Still had the signal loss, but the reboots stopped.
dzo fixed the network bug (thanks dude if you see this) and I thought it was safe to re-install the franco.kernel. But after I did the reboots returned!
So my question is, is anyone else suffering from this reboot problem with [04 OCT] franco.kernel? Or has anyone suffered from, then fixed it?
Thanks for any advice in advance!
P.S. Yes I could just not install the kernel, but I had some good performance and battery boosts from it, so would love to have it on and stable again!
I haven't oxygen anymore, but I've using it until latest cm7 update and always with frankco' s kernel(this include the 4 october version which I'm still using until now) and I never had reboot problems. Maybe your governor/io settings caused this.
I have
CPU: 400min 1000max, governor: SMARTASSV2, i/o scheduler: vr
vethan said:
Ok, so here's the story:
I was running oxygen+franco.kernel, and was suffering from loads of random reboots, as well as the oxygen signal dropping bug.
While I was looking for the source of the problem, I wiped the phone back to B138, and re-installed oxygen without the franco.kernel. Still had the signal loss, but the reboots stopped.
dzo fixed the network bug (thanks dude if you see this) and I thought it was safe to re-install the franco.kernel. But after I did the reboots returned!
So my question is, is anyone else suffering from this reboot problem with [04 OCT] franco.kernel? Or has anyone suffered from, then fixed it?
Thanks for any advice in advance!
P.S. Yes I could just not install the kernel, but I had some good performance and battery boosts from it, so would love to have it on and stable again!
Click to expand...
Click to collapse
i had the exact same problem with oxygen and 4oct franco. i traced the problem back to the kernel, uninstalled franco and no more reboots. now i'm using stock oxygen kernel. i was using franco with smartass2 governor 400 min 1200 max, now i'm using ondemand governor (i think) and same freqs. didn't notice any difference in battery life or performance to be honest, so i'm fine.
I had same rebooting issue with Franco´s kernel and Oxygen.
But if I had wlan on, no reboots. Didn't even have to be connected.
I only keeped wlan on and reboots were gone.
Bit strange... but now using Oxygen without Franco´s kernel.
Timbermax said:
I had same rebooting issue with Franco´s kernel and Oxygen.
But if I had wlan on, no reboots. Didn't even have to be connected.
I only keeped wlan on and reboots were gone.
Bit strange... but now using Oxygen without Franco´s kernel.
Click to expand...
Click to collapse
That's interesting. I'm trying to use CM7 and Franco's kernel now, and just had a reboot, but I'll switch wifi on an see how it goes
TF101 running Revolver4 and Guevor's kernel has me whistling ;')
I had SOD's and other problems multiple times a day with all the ICS ROM's until I added Guevor's kernel (test11 was the first really stable on for me). I skipped running test 12(a,b, etc.) and went to test13 from test11 and it just seems very solid. OC'ed to 1504 and no heat issues, so SOD's, fewer FC's with apps, too.
If you're as tired as I was of the bleeding-edge, check out Guevor's kernel, I hear it's bringing stability to several other ROM's too.
Thread here.
yup, same here. I'm running revolver beta 1.3.1, with test13 kernel, and it's been very stable since i changed to guevor's kernel.
i don't oc my tf though... it just doesn't need to be oc'd
Well I got ~240h uptime stable with EOS build 19 before I got my first SOD (on that build).
I dont think Ive ever had an app FC on me.
The only time I am getting SOD is when I get multiple notifications at one time, like texting through Google Voice app or multiple emails coming in from different accounts. I am using ARHD 3.1.0 with Guevor (test 13). Anyone experiencing this?
Fast:
Check this out!
Fast, Stable, and Consistent:
ROM: ARHD 3.2.0.
Kernel: TestyMeh ICS 1.0 - OC+SIO+Initd ICS, New Suspend Method, Added Veno
Well , I made a full wipe for my transformer then installed ARHD 3.2 with guevor kernel test13 and it's very very stable. From the last charge and up to now, I've got 2 days and 8 hours with no single reebot and the wifi being connected all the time. I've left the kernel with it's default configuration at 1.2 GHz maximum.
I had some problems with Megatron and Guevor, but now i tried TestMeh and it is stable for 3 days, so i am happy
Revolver + test13 - stable as a rock at 1400Mhz.
Hey guys
I'm sorry for the question but i couldn't find a straight forward answer.
Do i flash a kernel the same way i flash a rom, through CWM?
My Kernel Flash Procedure:
I wipe Cache first. Then flash the kernel, in the same CWM session. I always a have a nandroid backup just in case something goes wrong and it has happened. Example: like not moving passed the boot logo for more than 15 mins. If this happens go back into CWM restore nandroid and reboot. Then do a MD5 check on zip file if possible or re-download kernel. Most of the time I check the zip file before flashing with the MD5 checker app.
Haven't tried the new kernels, all 3 of my tfs have been running rock solid since day one of ics... All on revolver 1.3.1 each one easily hit 300+ hours uptime. I am a little hesitant to change anything as they are all as perfect as I could imagine. But I might update oneto see what performance gains I achieve.
Sent from my SAMSUNG-SGH-I997 using XDA
Revolver RC1 and Guevor test 13/14
On my TF101, coming from 1.3.1 with wiping cache and Dalvik cache, I had good speed, wifi, Bluetooth etc. I did have lots of hanging in Gmail. I also did not ever get deep sleep.
After flashing Guevor test 14, all systems have been "go".
Thanks, developers.
Edit: No! reboot or any other system issues for an up time of 49+ hours. Gmail has started freezing again. Sometimes FC works for a while, but nothing fixes Gmail for me right now.
Gmail was fixed for the moment by reboot, no wipes. test 15 has been completely solid also (16 hours).
I did try the Guevor test 14 kernel, which is a very good kernel. However, on my thermal heat gun at the higher frequencies 1704 the tf101 is running 1c to 5c hotter then TestyMeh on my tf101. This might explain why some tf101s are more unstable at higher frequencies and volts due to heat. However, each tf101 is different. My was a pre-order from last year and seemed to have better components.
---------- Post added at 05:54 PM ---------- Previous post was at 05:31 PM ----------
Can't speak for every tf101, but if I set Min freq at 312MHz and not use the default 216MHz, I have not had any re-boots or SODs for every day use in almost a month now.
Hi, I didn't try Revolver4 but i did it with guevor's kernel test15.
Tryed Guevor's last test15 kernel with eos and got wifi-off allways... so I tryed TestyMeh 1.0 with eos and everything works cool. (OC-1600)
Revolver 4 is stable with test15? I'm thinking about swith to...
Sorry to be a little offtopic but I really need to comment something about!
I'm using test15 now. With test14 I had an SOD.
Grateful to Guevor for his stick-to-it-ivness with this kernel!
Would you guys recommend overclocking your nexus 7 or just installing the franco kernel instead for smooth programs?
I tried overclocking. Its gone unstable every single time. I tried running mkernel at 1.6 and it just locked up, got hot and would not boot till it cooled down.