Cm7 whyzor

#|

I'm not following SII dev atm, but somebody should have found a workaround by now I would think. I took a quick look but, there are a million threads on the epic touch and other sII's lol, which is good. So no one else is having this problem? Looks like it's just a Handcent issue. I installed chompSMS instead. Just in case anyone out there ever has this issue. Page 3 of 3 First 1 2 3 Jump to page:.

Fast service. W attunlockcode. Fastest Service Around! Don't waste time!!! Replies: 3 Last Post: , PM. Swirly MMS not working with 2. By IceTide in forum Apple. Replies: 0 Last Post: , AM. Don't take the name of root in vain. However, sometimes you or other kernel developers need to see compile, link, or other commands exactly as they are executed. For this, use "verbose" build mode.

This is especially true for the development releases, since each new release contains new code which has not been debugged. Make sure you keep a backup of the modules corresponding to that kernel, as well. To use the new kernel, save a copy of the old image and copy the new image over the old one.

If you don't, you won't be able to boot the new kernel image. See the LILO docs for more information. After reinstalling LILO, you should be all set. Shutdown the system, reboot, and enjoy! If you ever need to change the default root device, video mode, ramdisk size, etc. No need to recompile the kernel to change these parameters.

If there isn't anyone listed there, then the second best thing is to mail them to me torvalds linux-foundation. If the problem is new, tell me so, and if the problem is old, please try to tell me when you first noticed it. The dump may look incomprehensible to you, but it does contain information that may help debugging the problem. The text above the dump is also important: it tells something about why the kernel dumped code in the above example it's due to a bad kernel pointer.

Alternately you can do the dump lookup by hand: - In debugging dumps like the above, it helps enormously if you can look up what the EIP value means. The hex value as such doesn't help me or anybody else very much: it will depend on your particular kernel setup.

What you should do is take the hex value from the EIP line ignore the "" , and look it up in the kernel namelist to see which kernel function contains the offending address. To find out the kernel function name, you'll need to find the system binary associated with the kernel that exhibited the symptom. To extract the namelist and match it against the EIP from the kernel crash, do: nm vmlinux sort less This will give you a list of kernel addresses sorted in ascending order, from which it is simple to find the function that contains the offending address.

Note that the address given by the kernel debugging messages will not necessarily match exactly with the function addresses in fact, that is very unlikely , so you can't just 'grep' the list: the list will, however, give you the starting point of each kernel function, so by looking for the function that has a starting address lower than the one you are searching for but is followed by a function with a higher address you will find the one you want.

In fact, it may be a good idea to include a bit of "context" in your problem report, giving a few lines around the interesting one. If you for some reason cannot do the above you have a pre-compiled kernel image or similar , telling me as much about your setup as possible will help.

You can now use all the usual gdb commands. About Whyzor's 2. I just switched from cm7-tg-reloaded to cm7-tg-reloaded In reading the changelog, a quick blurb got my attention, stating that wifi prevents your phone from going into deep sleep, and is a known bug in all custom roms no idea if that's really true or not. So I loaded up the new rom, left the wifi off, 3g on, gps on, and went to sleep. That's 1. Light usage through the day, light websurfing, checked my email a bunch of times, and a few text messages.