That was, by any standard, a d*ck move. If you don't want people running your kernel, don't help. Tricking users into wiping their drive, from an account with good TMO standing is the height of d*ckery.

It is not up to you to decide who is worthy of touching the holiness that is their device. We all learn piece by piece.

If whoever copied your signature and ran it, fine. But posting that as a fix (even two posts down after the explanation) is out of line. I don't believe you read every thread, completely, every time, no mistakes.

Remember that not everyone have your settings. I, e.g., have about 50 posts per page, and every time someone says "back on page 4" I want to strangle them. I don't. Maybe he/she just missed the post on the previous page. Maybe he's tired, maybe, you know, his phone doesn't work.

If you feel he shouldn't be in -devel or -testing without being a guru, say so.

Next time you think this is funny, remember that there are times we need help. When you walk into a hospital office saying "help me, I've been poisoned", a doctor should pee in a cup and have you drink it because you shouldn't be drinking stuff you don't understand and you deserve even more problems.

just installed it with the kernel-settings, and overclocked at 900 mhz with lv settings, and wow, the device feels a lot faster than power 42 (v46 was buggy for me) .
i hope that 720 video playback/recording is on its way
and great job mate .

git clone http://repo.or.cz/r/microdia.git <-- the source from this link is for older kernel versions. You just need to compile it for our kernel. I used it back when ubuntu was on .26 kernel.

http://groups.google.com/group/micro...a-driver-draft

If I never ran things I didn't understand, I would have to get rid of my computers.

The real moral of the rf comments is don't run code posted by people self-identified as a..holes.

Just wanted to Thank You, Pali, for your hard work on this, much appreciated!!

Running 47 with Multiboot for the past day with no issues. No perceived speed increases as others have reported.

Hmm...
v47 Kernel & NITDroid loading with multiboot but loading omap kernel resulting in error.
For those who are using multiboot can you guys boot into omap kernel?

hey, the battery temp....... Ha fooled you. Just kidding.

So, anyway after taking about a day and a half to catch up on the whole thread, I hope I have not missed someone else posting that the battery widget and battery graph app do not match now.
for example my battery widget currently says 76%, while battery graph says 37%. I don't believe either of them lol
The status bar icon is on half empty (or half full if you are an optimist) and is green.
So, those few people who said the battery has improved, perhaps it is just an improvement in what the widget is telling you, and not an actual mprovement?
Perhaps it is just me getting this, and if so does anyone have any ideas? I have only had power kernel on for today and only noticed this today. Have not booted up back to normal and have yet to restart to power kernel to see if the problem goes away, just thought I'd report this and see if anyone else has noticed this phenomenon. Also I wanted to see what would happen when one of the 3 different results got to zero. It's all exciting like the grand national. Will the favourite win? Will there be a late surge from the outsider?

Also, if this will help- I have not enabled smart reflex or ticked enable bq27x00 module. Might be relevant, I dunno, I'm not an expert:P

Just wondered... What would happen in the world if all teachers and book authors are like him >.< end of the world i guess...

Just tried and booted up without a problem. Not using nitdroid but both v47 and omap load without issue.

Ok, i searched this forum and found no direct impact on the usb host in H-E-N with this new power kernel. It doesent work for me. I previusly had nitdroid, so i uninstalled it, restored my standard nokia kernel, and than installed this new power kernel, restarted my device few times, reinstalled h-e-n , but i cant connect andy drive or mouse via usb otg , previously I could. Is somebody else suffering the same problem?