yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
Mate, did you flash "proprietary-vendor-samsung.zip" for 4.2.2 ROM right after the kernel while still in recovery?

Maybe I will flash a stock 4.2.2 ROM just to see if it works with my P5110, although I hate Samsung stock android.... I was only 5min on 4.0.3 stock when my Tab was brand new, as soon as I saw all works, I've rooted it and flashed CM9

:D
[Galaxy Tab 2 10.1" Android Development] elcocolo50:
Yes I do, My friend.
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
[MENTION=2466106]elcocolo50[/MENTION] and [MENTION=5153662]Android-Andi[/MENTION]

OK guys, I have checked how it works with stock P5110XXDMF1_P5110PHNDMF1_PHN (it is a 4.1.2 for Netherlands) and can confirm that the NEXT-kernel-2.1.6 works on my P5110 perfectly fine there, I had root, USB connection, ADB and all else.

However, for it is a typical dreadful Samsung pain-in-the-arse firmware, I had to unplug and replug my USB cable to get an USB connection. But, that's Samsung, not the kernel that makes difficulties.

Guys, I am horrified of that stock ROM experience, you both owe me a beer :eek: I'm definitely not gonna flash 4.2.2 now for some time, I am really shocked, how bad the stock firmware is- and all that awful bloatware!
[Galaxy Tab 2 10.1" Android Development] elcocolo50:
Thank you very much for your help.I got wait for my sd card to flash the rom 4.4.2 to see wath happend:thumbup::rolleyes:
[Galaxy Tab 2 10.1" Android Development] doc-oc:
I have had a little bug with dual boot stock 4.1.2 / CM 11 - after rebooting to stock sometime system language becomes default, Netherlands in my way, but not set Russian's.
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
[MENTION=5304521]doc-oc[/MENTION] it´s not related to the kernel :p

btw. [MENTION=5051515]tetakpatak[/MENTION] 38 Downloads = 8 "Thanks" clicks ? :D idk why i wasn´t sleeping much to get this work for all here :D

i´ll maybe be out here for some days ;)
[Galaxy Tab 2 10.1" Android Development] doc-oc:
Maybe it was recovery as a cause? Stock 4.1.2 and SlimBean 4.3 with NEXT Kernel 2.1.3-2.1.5, based at old Philz recovery = no problems, but 2.1.6 kernel+new recovery are leading to languages bug. SuperSU is the same in both cases.
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
wipe cache and dalvic and see if it happens again.

Someone else faceing this problem?
[Galaxy Tab 2 10.1" Android Development] njstein:
I know I really appreciate all your hard work, AA, and press the Thanks at all times. Something I've noticed in this Tab forum is the lack of the Thanks button being pressed. In my phone forum, everyone gives it up. Have yet to DL or flash this kernel, but give props anyway. Just saying...
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
New PhilZ Touch-Blackhawk repack available.

Compiled from source by me, used files from [MENTION=4021423]ketut.kumajaya[/MENTION] to add Dual-Boot support :)

Attached here: http://xdaforums.com/showpost.php?p=50580154&postcount=381
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
11/46 much better than 61/2283 :laugh:
[Galaxy Tab 2 10.1" Android Development] doc-oc:
Today I installed SlimKat as secondary system and did not have any language problem. Yesterday that was CyanogenMod 11 (2014.02.24).

Recovery is the same.
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
Well....homo sapiens rather takes than gives.

People rather spare their "thanks" clicks, and let 8-per-day-limit fail day by day.

Don't worry about it, you did awesome work here.

I dream about Ubuntu touch aside Omni unofficial as dual boot, thanks to you got as close like never before!! :D
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
elcocolo and [MENTION=5153662]Android-Andi[/MENTION], I would like to let you know, I have just flashed factory 4.2.2 JDQ39.P5110XXDML1 released for Netherlands and can confirm that ADB as well as USB work perfectly fine with blackhawk's NEXT kernel 3.0.101 Sun Oct 27 22:33:13 WIT 2013

This firmware is less disgusting than 4.1.2 I flashed yesterday but I still can't find any reason to use this crap. I go back to beautiful PhilZ recovery now to restore my Omni and Slim
[Galaxy Tab 2 10.1" Android Development] elcocolo50:
Hi Tetakpatak thanks for your help..I know the problem is something in this scrap stock rom.The PhilZ recovery is very good and the Next kernel Im waiting for my sd card to arrive... thanks you and android andi..
[Galaxy Tab 2 10.1" Android Development] doc-oc:
unfortunately DholmenROM 4.4 does not work in a dual-boot - system UI error when selecting system language after ROM flashing.
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
Didn't Tux write that Dhollmen ROM works only with Dhollmen kernel? If so, it definitely can't work in dual-boot mode as both ROMs need blackhawk's NEXT kernel.
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
It could be that dhollmen-rom using a different ramdisk :p

There´s something a lot of kernel-dev´s mention in their post
[Galaxy Tab 2 10.1" Android Development] doc-oc:
And this ROM does not support NEXT kernel too. At all. http://xdaforums.com/showthread.php?t=2663746 ( SENSONIC™HD)
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
If this info makes you feel better, I've just checked how it looks with my biggest thread/complete guide for the i9000 that costed me really lot of time to make (including videos that I have recorded exclusively for it and edited as well) and altough many people unbricked their phones with that guide.... and didn't face brick by downgrading, as of today:

* 14.000 views

* more than 800 downloads (attached system files, Odins, extracted up-to-date bootloader packed for Odin etc.)

and.... only 18 "thanks".... LOL :D

So we can say, mathematically, you have about 1200% more "thanks" clicked per download. Not bad?

The i9000 is really very tricky as its last stock ROM 2.3.6 had too small /system partition size, so custom ROMs enlarge it, but earlier ROMs had no resizing check so downgrade step from 4.3 or higher to 4.2.2 or earlier usually brings instant brick or EFS erase (even restoring a nandroid backup across that step) and recovery can't be flashed without kernel, it's always coupled....you can think!
[Galaxy Tab 2 10.1" Android Development] freinet:
After I have problems with random restarts with primary and secondary Rom, I deinstalled the secondary Rom. Also I installed the latest Blackhawk recovery, because I have still installed the test version. After that I flashed secondary Rom again and till now no restarts.

Thanks

freinet

Gesendet von meinem GT-P5110 mit Tapatalk
[Galaxy Tab 2 10.1" Android Development] Droidcore:
I also have a problem like this :(
[Galaxy Tab 2 10.1" Android Development] doc-oc:
Me too. Especially on SlimKat with ART, somewhat less on CM11. Now I want to try Omni ))
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
[MENTION=5304521]doc-oc[/MENTION] please try using dalvic instead of ART - tell if it makes a differents.
[Galaxy Tab 2 10.1" Android Development] doc-oc:
Yes, it has differents - about 2 last days there was no spontantaneous rebooting on CM 11 (nightly 26.02.2014 - 27.02.2014) with Dalvik.
[Galaxy Tab 2 10.1" Android Development] cubandanger05:
I'm using dalvik on both mokee and cm11 and I can confirm random reboots on both.
[Galaxy Tab 2 10.1" Android Development] BlackRenegade:
+1 with Dalvik and 1March CM11

Sent from my GT-P5113 with XDA Premium HD app
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
I had no reboots anymore, just once with an old build. Probably my memory was full and that was the reason....
[Galaxy Tab 2 10.1" Android Development] freinet:
Do you try a clean installation from beginning?

I mean with flashing latest Blackhawk recovery, next tool, rom, core gapps and latest blackhawk kernel? And this fresh?

I have random reboots and this helps me. No reboots with mokee and omni unofficial.

Edit: I would download all files again, if possible check md5sum.

freinet
[Galaxy Tab 2 10.1" Android Development] doc-oc:
Now I'm back to the slim 4.3 as a second system - stock 4.1.2 Netherlands and slimbean have not any spontaneous restarts. I think it is a KitKat, as a cause.
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
I have tested the 2.1.6 kernel on my P5110 with following ROMs:

4.4.x: SlimKat, Omni unofficial, CM11

4.3.x: SlimBean, CM10.2 (proprietary-vendor-samsung.zip flashed right after the kernel)

4.2.2 stock

4.1.2 stock

....and I have no problems at all. Omni has rebooted for the very first time after kernel flashing 2-3 times still during the boot animation, but later never again.

EDIT: I have flashed "proprietary-vendor-samsung.zip" for the first time on SlimKat and no problems! Never tried before to flash it on KK rom, but it works as I see....

I've read about somebody complaining to have had bootloop, but it probably had snother cause.
[Galaxy Tab 2 10.1" Android Development] njstein:
[MENTION=5241909]freinet[/MENTION] or [MENTION=5051515]tetakpatak[/MENTION], it says in the instructions to dual-boot that we need the Ducati Vendor Blobs. I can't find them in the op (maybe I'm blind or just stupid) but can find them in the 7-inch thread. Do I use the ones in the 7in thread? Thank you for the help!!
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
yes, use from 7“ thread - both use same blobs
[Galaxy Tab 2 10.1" Android Development] njstein:
Excellent! Thank you so much, AA!
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
I´ll fix that soon for you guys ;) ... still looking for the soft-reboot-issue too...
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
MOVED On NEXT Page :p
[Galaxy Tab 2 10.1" Android Development] freinet:
Tried to install, reboot after install ends in black screen.

freinet

Gesendet von meinem GT-P5110 mit Tapatalk
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
Out of thanks, sorry.... can you please try attached too?

Edit:

Flashed it on my P3110, PAC-Rom is booting :D Screen Messed up (to big now) and Touch not working :D

So, i can confirm Working on P51XX too :D

(Picture attached using P51XX NEXT Kernel on P3110)

Edit2:

Download http://xdaforums.com/showpost.php?p=50580154&postcount=381
[Galaxy Tab 2 10.1" Android Development] freinet:
This one works here.

Gesendet von meinem GT-P5110 mit Tapatalk
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
For me too on P3110 :D (Picture added to my last post)

Blackhawk´s NEXT Kernel 2.1.6.2

Flashable ZIP attached

Untested - but i am sure [MENTION=5051515]tetakpatak[/MENTION] can test and report back soon :)

Hopefully fixed CM 11 Support

added PAC 4.4.2 Support

Thanks [MENTION=4938788]antutu[/MENTION] for the diff and [MENTION=4021423]ketut.kumajaya[/MENTION] for instructions and permissions!

Download:

http://xdaforums.com/showpost.php?p=50580154&postcount=381
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Thanks Android-Andi, long life NEXT kernel :laugh: I will update post #1 soon :good:
[Galaxy Tab 2 10.1" Android Development] njstein:
I was able to get this setup but didn't feel it went right and would like some clarification and guidance. There are 2 philz touch files on [MENTION=5153662]Android-Andi[/MENTION] post, the "philz_touch_6.12.8-p5110-blackhawk" and the "GT-P5110_PhilZ-Touch-Recovery_6.18.7-blackhawk", which one do I use? Do I use both somehow? I'm slightly confused by this and not sure how to successfully use both or if I even need to. Any and all help is greatly appreciated!!
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
You only need one of them [MENTION=5087305]njstein[/MENTION] - only two different version numbers ;)
[Galaxy Tab 2 10.1" Android Development] njstein:
Excellent, AA, confused me and made me scratch the ol noggin for awhile. Thanks for answer my friend!
[Galaxy Tab 2 10.1" Android Development] doc-oc:
My misstep in flashing kernel was with flashing proprietary-vendor-samsung.zip to 4.1.2 ROM:

1. Now there is no boot-animations on stock 4.1.2 ROM, only boot-sound

2. Internet doesn`t work - i have WIFI connection to my router only

3. Camera doesn't work

4. I forgot - auto-rotation doesn`t work

5. After reflashing 2.1.6 kernel I still have problems with camera and boot-animation

Now I should reflash my stock ROM to fix the issues...
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
sounds like you haven't flashed the proprietary files DIECTLY after kernel.
[Galaxy Tab 2 10.1" Android Development] doc-oc:
Oh, I'm sorry - I realized my mistake: I installed in both systems proprietary-vendor-samsung.zip

How do I delete my previous post?
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
for Stock 4.1 you need special vendor files ;) you can use the edit button to change your post.
[Galaxy Tab 2 10.1" Android Development] doc-oc:
Hmm, I think I found a small bug:

Latest Philz recovery + stock 4.1.2 as first ROM and latest SlimKat as second ROM

1. Next 2.1.6 + proprietary-vendor-samsung-4.1 for first and proprietary-vendor-samsung for second ROM - everything is ok. But

2. Next 2.1.6.2 + proprietary-vendor-samsung-4.1 for first and proprietary-vendor-samsung for second ROM are leading to black-black screen instead second ROM. First ROM works good.

Specially checked twice to be sure that.
[Galaxy Tab 2 10.1" Android Development] freinet:
Sorry, but I have still sometimes soft reboots. So for now I am back to only one rom.

But will try again. But not now:cool:

freinet

Gesendet von meinem GT-P5110 mit Tapatalk
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
thanks [MENTION=5241909]freinet[/MENTION] for the feedback... courious... i´ll dig around it and lemme see if i find something...

maybe i´ll reupload 2.1.6.2 with fixed Bluetooth-Issues...
[Galaxy Tab 2 10.1" Android Development] freinet:
If you find something let me know. I will try it again:D

Gesendet von meinem GT-P5110 mit Tapatalk
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
[MENTION=5304521]doc-oc[/MENTION];

Have you flashed NEXT 2.1.6.2 again after flashing 2nd Rom (or after restoreing a backup) ?

Sure you used the right NEXT 2.1.6.2? I reuploaded it, because first upload didn´t worked :p maybe redownload and try again.

There´s no reason why SlimKat shouldn´t boot... it boots fine on P31XX :p
[Galaxy Tab 2 10.1" Android Development] doc-oc:
I have restored backup only for SlimBean. Stock ROM is my general system, and all KitKat ROMs are experimental - I only flash or reflash its after deleting and creating secondrom.img by next-tool for each times.
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
[MENTION=5304521]doc-oc[/MENTION] You need to flash NEXT Kernel every time after flashing a Rom or restoreing a backup - no matter if you are on 1st or 2nd Rom. Same for both.

Please redownload 2.1.6.2 and try again on SlimKat if you have time.
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
Just for your information:

I've tried to flash ducati-blobs right after the NEXT kernel on several 4.4.2 roms and had no single reboot since.

Omni, SlimKat, CM11
[Galaxy Tab 2 10.1" Android Development] doc-oc:
Yes, of course I reflash NEXT kernel after each ROM flashing for both system, I reflash vendor blobs for each system too directly after the kernel.

2.1.6.2 kernel was redownload and after flashing SlimKat was working. Thanks for the advice.

By the way - I noticed one soft reboot (ART) at the second system.
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
As kernel gets always automatically flashed for both ROMs, important thing is just to use proper blobs regarding the Android version of the flashed/restored ROM.

Although KK roms will boot even without flashing blobs, KK seems to work more stable if the ducati blobs are flashed right after the kernel.
[Galaxy Tab 2 10.1" Android Development] doc-oc:
Are the ducati blobs compatible with all 4.1 - 4.4 ROMs? Should I flash its DIRECTLY after the kernel for both systems, or only one time for any system?
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
Both questions are bit in a grey area for me, I'm not sure my answer is 100% correct:

Ducati blobs are AMAIK compatible for 4.3 and 4.4 roms, not sure about earlier. As the kernel gets flashed on both ROMs, you need it for sure on the ROM that just got the new kernel.

But as the kernel gets flashed on both ROMs at the same time, supposely the kernel was flsshed again, I would also flash it over another ROM, it definitely should't make any harm.

You can download ducati blobs from the second post in this thread:

http://xdaforums.com/showthread.php?t=2285366
[Galaxy Tab 2 10.1" Android Development] doc-oc:
Thans for vendor-blobs-new-ducati-blackhawk.zip. I have only vendor-blobs-old-ducati-blackhawk.zip, 1.8.3 compatable (you can see this on my screenshot above). I will try it tomorrow.
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
the "old" will restore the old vendor-files :p :D you only need them e.g. if you flashed the "new" on CM 10.2 to use NEXT Kernel and want to revert to CM Kernel (or another Kernel like an older NEXT Kernel) wich wasn´t updated and can´t handle the "new" blobs :p

See my Link for some Dual-Boot tutorials in my signature, not up to date and for p31xx but very usefull for p51xx user too. nothing big changed.

You should also read the op... and FAQ on first page...
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
[MENTION=5153662]Android-Andi[/MENTION] I will check my local source and rebuild P51xx kernel if necessary.
[Galaxy Tab 2 10.1" Android Development] doc-oc:
Oh, right. Thanks for reminding me about it, because I already forgot about ducati blobs features - I really have not been using this 1.8.3 kernel version due to intense heat and reduce battery life. And already 2am - bad brain thinks ...
[Galaxy Tab 2 10.1" Android Development] njstein:
If I do a nandroid, does it backup just the ROM that I'm in according to the recovery? Or does the nandroid backup both ROM's?
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
only 1 Rom (depends on the recovery you booted)
[Galaxy Tab 2 10.1" Android Development] njstein:
Someone else confirm this? I can't get the scheduler/governor to survive a boot. I have both ROM's set to the same thing but on ROM switch it reverts. On newest Next, running brolee's stock and Mokee. I'm using Android Tuner to switch. Should I use a different app? Also, when I do switch the governor away from Interactive, the frequencies aren't reported as changing. Thanks, Andi for this kernel, loving the dual boot option!
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
Aren't you using STweaks app?
[Galaxy Tab 2 10.1" Android Development] njstein:
I was hoping that Android Tuner could get 'er done. But no biggie, and to be honest I forgot that STweaks was what we are supposed to use. I only read the first couple of lines of the op and it mentions the ability to use AT. Thanks tetakpatak for reminding me. I'll DL ST right now...
[Galaxy Tab 2 10.1" Android Development] njstein:
[MENTION=5153662]Android-Andi[/MENTION], here's what I've noticed. I'm getting reboots on my primary ROM, newest Mokee (newest Official) but not my Secondary (brolee's stock). I've noticed that they mostly happen when I've freshly booted into primary ROM and things are starting up (Tasker, etc) and Root apps getting access (betterbattery, Android Tuner, etc.) and I try to start an app before all the background stuff is done. Once all has settled in, the reboots seem to not happen. Unless I have RAM intense apps going on my screen and moving through them (i.e., Neutron playing and adjusting Viper4Android settings). I think I can reproduce it, would you like a logcat of one? I won't be able to get it done until later tonight, but if you want one I'd be glad to push my Tab until I get one...
[Galaxy Tab 2 10.1" Android Development] Android-Andi:
hey [MENTION=5087305]njstein[/MENTION] here´s something interesting from P31XX Thread, but i think a logcat and dmesg can´t hurt anyway.
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
[MENTION=5087305]njstein[/MENTION] it is true and very well described. No big problem, but it happens just same way on my P5110. It hapens seldom but it does happen.

The developer of our kernel, [MENTION=4021423]ketut.kumajaya[/MENTION] has written short ago that he may re-build P51xx kernel if I'm not wrong.

Towards my impression, OC to 1.3GHz seems to help. All we can do is to try to hold it in the logcat and attach it here in the thread. It might be helpful.
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
[MENTION=5087305]njstein[/MENTION] since I've set OC to 1.35GHz with STweaks I had no single reboot anymore! :D
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
Logcat soft reboot P5110

[MENTION=5153662]Android-Andi[/MENTION] and [MENTION=4021423]ketut.kumajaya[/MENTION]

I finally cought into the logcat fully one soft-reboot with blackhawk's NEXT 2.1.6 (on my P5110) :D

It happened with SlimKat, by using SD Maid app (I was uninstalling some apps)

Thanks to both of you for working on this :)
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
[MENTION=4021423]ketut.kumajaya[/MENTION] would it cost you very lot of work to add f2fs support to your 2.1.5 kernel for P51xx tabs? Or could you instruct [MENTION=5153662]Android-Andi[/MENTION] how to compile it? It is IMHO such an amazing kernel! I'm back to SlimBean and use 2.1.5 blackhawk. Running this 4.3 ROM on F2FS would be just heavenly.....

tetakpatalked from my P5110
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
I just informed [MENTION=5153662]Android-Andi[/MENTION], NEXT 2.1.8's ramdisk for P51xx will completely base on P31xx's ramdisk. I plan to release for both devices on the same time :)
[Galaxy Tab 2 10.1" Android Development] tetakpatak:
OMG, this is the best news since long time for us, P51xx users! :D You simply rock, ketut!

tetakpatalked from my P5110
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Somehow always failed to upload any file here, Dev-Host for now:

proprietary-vendor-samsung.zip

proprietary-vendor-samsung-4.1.x.zip

blackhawk-next-tool-0.2-p31xx-p51xx.zip

blackhawk-next-kernel-2.1.8.1-p51xx.zip

blackhawk-next-kernel-2.1.8.2-p51xx.zip

blackhawk-next-kernel-2.1.8.3-p51xx.zip

As usual flash blackhawk-next-kernel-2.1.8-p51xx.zip and directly flash proprietary-vendor-samsung.zip for CM/CM based ROM or proprietary-vendor-samsung-4.1.x.zip for stock Samsung 4.1.x . For CM 11.0, I recomend format your /system partition first, flash CM 11.0 and GApps, and then flash blackhawk-next-kernel-2.1.8-p51xx.zip, directly flash proprietary-vendor-samsung.zip .

NEXT for P31xx tested and boot stock Samsung 4.1.2, 4.2.2, CM 10.1, 10.2, and 11.0 with ext4 or f2fs formatted /data and /cache. PhilZ Touch recovery failed to restore 2nd ROM (CM 11.0) f2fs formatted /system since f2fs need more space than ext4. I have to update my dual boot tool for larger system.img .

WARNING: NEXT for P51xx untested but boot P3100 with oversized graphics, wrong orientation, and not working touchscreen. The ramdisk part almost based on P31xx's ramdisk, the kernel part compiled for P51xx target.

UPDATE: 10/4/2014

NEXT 2.1.8.3:

WiFi driver incremental update

UPDATE: 8/4/2014

NEXT 2.1.8.2:

Omni ROM Samsung dock keyboard workaround, build the driver as module. Not loaded by default. For Samsung keyboard dock owner, you can use STweak to load this module on boot

Omni ROM for P5113 RCP input fix. SII9234 RCP input device only be registered as long as MHL is connected, adapted from tuna kernel

Total 8 commits, I'll tell you later but please try this kernel and help me to solve battery drain issue on KitKat as reported by Android-Andi and Viskesh. Only 2 commits possibly related to this issue actually

UPDATE:

NEXT 2.1.8.1: PAC KitKat support, P51xx SD card access bug fix

UPDATE:

By using the new NEXT tool, we can expand system.img without loosing user data.

Boot into 2nd recovery, nandroid backup /system

Boot into 1st recovery, flash blackhawk-next-tool-0.2-p31xx-p51xx.zip, create larger system.img (1.4GB, 500MB, 750MB, or 1GB)

Boot into 2nd recovery, you can reformat /system as ext4 or f2fs filesystem, nandroid restore /system

Only "Delete 2nd ROM" option completely delete 2nd ROM's system.img and user data.