Is there any way to verify current kernel the phone has?
I'm talking about specific one like stupidfast or OTB etc, not the kernel version which is 2.6.29.
Any idea?
Check clockwordmod recovery first. If its red you have voodoo. If it's green, you don't have voodoo. Don't know howbto check for more.
Rockin' DJ05, Minimal Icognito, Clocked at 1.3Ghz
You can use setcpu or similar that can read kernel info to see who compiled the kernel and when it was compiled.
If you can get a shell (adb shell or terminal emulator) you can just
cat /proc/version
and it will give you a name and a date of compilation, which is enough to figure it out. I'm back to jt's 11/29 kernel fort instance (the last dj05+ kernel that isn't undervolted afaik), and the time stamp is:
(Sourcery G++ Lite 2009q3-67) ) #1 Mon Nov 29 16:13:07 CST 2010
If you were running 12/30 it would say Sun Dec 30
SetCPU gives info too, but I wouldn't know.
Also, if you suspect voodoo, would it do any harm to disable_lagfix and reboot?
Swyped w/ XDA App. When in doubt, mumble.
Related
I'm happily running EViO 1.8 with the modded #15 kernel, but want to try out Net's and Ziggys. Is there a package based way to revert to the stock kernel if I don't like them or is it only via restoring the nandroid image of /system and /boot?
Calkulin has made his ROMs (current and prior) and the kernel used in 1.8 available here.
Prior ROM Versions
droidbird said:
I'm happily running EViO 1.8 with the modded #15 kernel, but want to try out Net's and Ziggys. Is there a package based way to revert to the stock kernel if I don't like them or is it only via restoring the nandroid image of /system and /boot?
Click to expand...
Click to collapse
Thanks nviron, that was exactly what I was looking for. I do wish there was a native package manager so you could be sure you removed all the trailings from a previous kernel or package before installing another.
Think RPM or .ipk
Just remember to clear dalvik cache (and or other cache?) between flashes and you should be good.
Also, be aware of some issues with some kernels. For example, with net's 4.3.x, I had to power the device down after the first boot, power it back up with power/vol-down, and wipe dalvik cache again. Otherwise, it hard locks for some reason. Once this is done, however, it works flawlessly.
Yeah, but where is the fun in that?? lol J/K
Wait, I have an idea!
Code:
# apt-get remove htc-sense
droidbird said:
Thanks nviron, that was exactly what I was looking for. I do wish there was a native package manager so you could be sure you removed all the trailings from a previous kernel or package before installing another.
Think RPM or .ipk
Click to expand...
Click to collapse
nivron,
I just noticed your sig, that is exactly the setup I'm considering, Ziggy's 1/21 kernel, how do you like it for:
a) performance?
b) battery life?
c) compared to net's 4.3.1 havs nosbc?
A. Excellent
B. Excellent (with -100uv script)
C. Comparable so far, but haven't had the combo running long enough to give you a definite answer. ROM and kernel combos require a break-in period.
droidbird said:
nivron,
I just noticed your sig, that is exactly the setup I'm considering, Ziggy's 1/21 kernel, how do you like it for:
a) performance?
b) battery life?
c) compared to net's 4.3.1 havs nosbc?
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I've been running Ziggy's 1/21 for a few hours now and it seems pretty stable and performance seems decent. I'm considering dropping the battery saver scripts and going to smartass as conservative has a bit of ramp-up time between when you start doing something and when the governor gets your CPU speed up to match. Also, I like the idea of smartass handling the screen state in the governor instead of a script.
__
EVO 0004, EViO 1.8, Ziggy's 1/21, Conservative battery saver, ADW.Launcher
[Optional CFS kernel ONLY]
If this is first time you FLASH my kernel or you just recently FLASHED any ROM,
To use my CFS-Tweaks from version xxx, you must FLASH xxx first, then FLASH the latest version.
This is stated by fox in his kernel thread maybe i am being a bit thick headed but i don't wanna mess anything up.I am on cm7 7.0.2 and i wanna flas his latest cfs kernel to test but what i dont understand is this part to use my cfs-tweaks from version xxx you must first flash xxx.what do i have to flash before i flash his latest kernel exactly?Any help is greatly appreciated.And sorry for the dumb question.
oOuzzielOo said:
[Optional CFS kernel ONLY]
If this is first time you FLASH my kernel or you just recently FLASHED any ROM,
To use my CFS-Tweaks from version xxx, you must FLASH xxx first, then FLASH the latest version.
This is stated by fox in his kernel thread maybe i am being a bit thick headed but i don't wanna mess anything up.I am on cm7 7.0.2 and i wanna flas his latest cfs kernel to test but what i dont understand is this part to use my cfs-tweaks from version xxx you must first flash xxx.what do i have to flash before i flash his latest kernel exactly?Any help is greatly appreciated.And sorry for the dumb question.
Click to expand...
Click to collapse
Don't worry about it as its obsolete as of now. All of his new CFS kernel now has the BFS like tweak which you had to flash special kernel before and then flash newer kernel on top of it.
With all his updates he puts,out four files. 2 low voltage files and 2 stock volatge files. My,suggestion is to use the low voltage first if that doesnt work use the stock voltage. Backup...duh. Flash cfs lv than flash bfs lv. His instructions are better so follow his.
tjlawson09 said:
With all his updates he puts,out four files. 2 low voltage files and 2 stock volatge files. My,suggestion is to use the low voltage first if that doesnt work use the stock voltage. Backup...duh. Flash cfs lv than flash bfs lv. His instructions are better so follow his.
Click to expand...
Click to collapse
LV and SV has nothing to do with it as what you just said had nothing to do with what he asked. Before when he didn't have BFS based he only had CFS so he try to make BFS like on top of CFS which was not full BFS. At this point all the CFS based kernel has the BFS like tweak so you don't have to flash the special kernel anymore.
thanks for the input guys..now off to flashing in hopes of better battery life.
im still unclear as to which kernal to use. I am running cm7.0.3 . thnx for ur input.
its my first kernel flsh. I just want to be sure I have the rite one.
Sent from my HTC Glacier using Tapatalk
hey all,
fairly new to android, but i've rooted and installed a couple of roms and kernals for fun.
now i've forgotten what im actually running. lol yes, i am that dumb.
here's what've installed:
1. frozen rom 1.1 - stock twilightzone 1.1 kernel
2. frozen rom 1.1 - with vision kernel
3. frozen rom 1.1 - with genocides kernel
4. frozen rom 1.1.1 - with genocides kernel
5. frozen rom 1.1.1 - stock kernel twilightzone 1.1.1RC2 - hajime-taisho
right now, in "About Phone"
firmware version is "2.2.1" so i know im on froyo
baseband ends in "EC05" so i've odin'd the right modem(i think i read a post that said baseband = modem version)
kernel version is "2.6.32.9" dunno which kernal im running.
build number says "twilightzone 1.1.1RC2 - hajime-taisho"
What it says in build is the kernel your runing. So twilightzone 1.1.1rc2 is your current kernel
silver03wrx said:
What it says in build is the kernel your runing. So twilightzone 1.1.1rc2 is your current kernel
Click to expand...
Click to collapse
oh i thought build number is the rom im running and kernel version was kernel version. what if i put genocide's kernel on? i'd be running ACS frozenrom 1.1.1 with genocide's kernal, what would 'kernel version' and 'build number' say?
useport80 said:
oh i thought build number is the rom im running and kernel version was kernel version. what if i put genocide's kernel on? i'd be running ACS frozenrom 1.1.1 with genocide's kernal, what would 'kernel version' and 'build number' say?
Click to expand...
Click to collapse
Could also use setCPU to check it
Yes use set cpu. Click info it'll tell you. I flashed genocide kernel build number just says syndicate frozen.
silver03wrx said:
Yes use set cpu. Click info it'll tell you. I flashed genocide kernel build number just says syndicate frozen.
Click to expand...
Click to collapse
ahh i completely forgot about setcpu.
in my setcpu it says
build : twilight zonev1.1.1RC2 - hajime-taisho
kernal : linux version 2.6.32.9
so right now im running ACS frozen rom 1.1.1 with the 1.1.1 stock kernel?
Yes I flashed genocide and in set cpu it said viper . So your on the kernel that comes with srf 1.1.1
oh sweet. ty. the lingo is just a lil new to me
i just flashed genocide's kernel, now my build number says "SyndicateROM Frozen"!
thanks for everyone's help
the kernel will almost always stay the same in about phone, all custom kernels are based on the same linux kernel... and genocide doesnt change the build version, so you now get to see what your rom changes the build version to...
Okay.
I have the latest stable CM7 for the NC.
Which overclock kernel can I use with this, and how do I go about doing it?
I've flashed the dalinger's (sorry if I misspelled that!) OC kernel, both the latest and the 52311, but both result in a blank screen after the "read forever" screen.
What do I do to get this working?
For stable CM7, I believe you need the 4/24 kernel.
Still rocking the Incredible with the XDA Premium App.
From here:
http://forum.xda-developers.com/showthread.php?t=925451
* 2.6.29 releases are discontinued and no longer supported. They will remain hosted for those that might need them.
* There are separate builds for CM7 and stock 1.2 Froyo
* 2.6.32 CM7 builds currently do not work with the stable CM7 builds until CM7.1. You need to use CM nightlies until 7.1 is released.
* All 2.6.32 kernels require an updated u-boot from B&N 1.2 Froyo. If your Nook has "Read Forever" or a green Cyanogenmod logo on the screen when you boot then you have the latest version. If it says something else then you need to update.
Click to expand...
Click to collapse
So you're going to need to grab the 2.6.29 kernels, unless you kick up into a nightly. I've honestly found the 107 nightly to be very stable, with Dal's kernel (at 1100 MHz), and it's been my daily driver on SD. Avoid 106 (it doesn't have SU/root).
I Am Marino said:
For stable CM7, I believe you need the 4/24 kernel.
Still rocking the Incredible with the XDA Premium App.
Click to expand...
Click to collapse
Thanks, i'll look into that!
Wifflepig said:
From here:
http://forum.xda-developers.com/showthread.php?t=925451
So you're going to need to grab the 2.6.29 kernels, unless you kick up into a nightly. I've honestly found the 107 nightly to be very stable, with Dal's kernel (at 1100 MHz), and it's been my daily driver on SD. Avoid 106 (it doesn't have SU/root).
Click to expand...
Click to collapse
I don't want to use a nightly, I'll stick with what I know works. I've got no problem using a lesser kernel or whatever, so thanks!
Edit - 4/24 worked! Thanks again!
You may or may not know this, but also after flashing you still need to go into cm settings then into performance to overclock it or mess with any governors.
funkencool said:
You may or may not know this, but also after flashing you still need to go into cm settings then into performance to overclock it or mess with any governors.
Click to expand...
Click to collapse
I knew that, but thanks anyways. You get a "thanks" for the insightful post (as do the others too!)
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.