[Galaxy Note 10.1 Android Development] iofthestorm:
By the way, you might want to check who the OP is :P. Chappatti is friendly and helpful, but I'm not sure that he's completely correct, and I think in this case he's conflating a different issue with your problem.

As far as I can remember (and I've read every post in this thread), no one has mentioned problems with backups before. Although I don't know if anyone had tried backing up a 4.1.2 ROM. The issue we used to have was that because of a change Google made in 4.4, recoveries built in a 4.4 source tree (such as mine) could not flash pre-4.4 ROMs (well, technically there was a way to update the .zip for older ROMs to make it work, but it wouldn't work out of the box and it would be a hassle so I'm sure no one bothered with it). I think for this reason official recoveries are probably still built in 4.3 (or older) trees - I think TWRP's official releases are still made this way. There is a patch that fixes this and allows the recoveries built against 4.4 code to flash older ROMs, but it can't be merged into the main codebase because then it breaks 4.4 ROMs from being flashed in the same recoveries (the code is in part of the Android core OS, which TWRP happens to use as well). The recoveries that I labeled "2.6.3.1" are built with this patch so in theory they should be able to flash ROMs of all sorts, and my ROMs are not built with this patch so they are not broken :). So as of this point, I feel like it's pretty likely that the recovery should flash anything you throw at it. You can see the patches here: https://gerrit.omnirom.org/#/c/3389/ https://gerrit.omnirom.org/#/c/3390/

Furthermore, my recovery builds are just straight off of the omni repositories, since TWRP is now part of omni in some sense. The one change I made to fix touchscreen handling has been merged into the main codebase, so they're effectively the same as "official" builds, although more accurately you could call them "development" builds since there isn't really a release process for different devices for TWRP. Since I am building straight from the main branch there is a chance that it could have been broken at the time that I built them, but this seems somewhat unlikely, because I don't think a change that breaks backups would have been merged by the TWRP guys.

Until I put up my 2.6.3.1 TWRP I was recommending people use PhilZ so that they could go back to older ROMs if they wanted, but after that I started recommending people use my builds because I feel TWRP is better (although, Aroma FM is broken here as well - TWRP has a file manager as well but it's not as nice, but I've never really felt the need to use either, I prefer adb).

I'm kind of curious, since it seems like the backups you made from my recovery were valid tar archives, I'm wondering why they were unable to be restored. Unfortunately, the log you posted earlier doesn't really say much.

Regarding custom kernels, not aware of any, it's a little tricky because at this point we are using newer drivers than were used in CM10 so other kernels won't be compatible unless they also upgraded (CM11 is using the same drivers now, but I don't know if any custom kernel developers are basing their work off of this). Personally, I find custom kernels to be a waste of time for the most part - if they really had reproducible, unequivocally useful benefits, they should submit patches back to upstream. In my experience most trade stability for the appearance of performance. In all honesty, development on this tablet is kind of dead, so I would be surprised if someone bothered to make one.

Regarding IrDA, I think IrDA is very specific functionality which may or may not be supported, but this ROM does support the new IR API introduced in Kitkat, so apps that use that will work. Apps that rely on the Samsung proprietary APIs will not work. I use this app, it's ugly but it does the job: https://play.google.com/store/apps/details?id=remote.control.samsung

This ROM almost certainly does not support AllShare Cast, but I don't have the device and haven't tried. But I think it's just a proprietary version of Miracast or DLNA and you might be able to find apps for those that work on the market, I just haven't tried. I do know that there are issues with screen recording and HDMI output has never worked on AOSP based ROMs, so there may be an issue there. It *might* support BBQScreen (written by an Omni developer, xplodwild) but again, I haven't been able to get the Linux client to run on my computer so I don't know for sure.