Made some progress.. both cams are now working together, and am getting excellent performance with dmesg reporting 379MB memory and still good 1080 video playback on a 512MB tablet .. i can now also play PVZ2 How can I share changes with you?

Last challenge is rotation and i'm confused.. MMA8452 probe still fails and out of despair i tried compiling with MMA7660 driver instead.  I noticed there are different versions and  the one ending 'lastversionJK2' actually produces "mma7660 probe ok" in dmesg, but Androsensor still shows no events and continues to say it's an MMA8452Q.  Any ideas  will be appreciated please!! thanks a lot. 

PS: Attaching dmesg from my old GB rom (working rotation) and the new kernel with cm10.1.

Thanks to your valuable advice to not trust the things reported in Android  now I did some more progress and nearly solved..

So MMA7660 continued not working and after getting some debugging printed I found other messages saying there was no good probe after all. So I put my attention back to MMA8452 from basics and the problem seems to be a different way this tablet is set up (or rather not set up) to get a succesful probe.. I think it should not be difficult to fix now though I'll be busy for the next few days.

So many thanks and I hope to share soon so that another tablet will be fully working

OK... so I uploaded the mods to a fork on github at https://github.com/drums173/android_kernel_odys_neox_3.0.8 and it works fine now including rotation!  Added long-press shortcuts to the buttons with volume-controls, and some other possible tweaks.

One small thing.. after booting i'm seeing just a couple of lines in dmesg at around 39 seconds saying: "_AllocateMemory fail! pool=6->9, Bytes=16384, Type=4".  Googling only came up with http://pastebin.com/JnQMYUYe which seems more serious and I have no idea what the context for that user was.  As far as I can see everything still works fine, but I can't trace where the msg is coming up from and tried with various memory settings (GPU from 128-32Mb, UI 64-40, VPU 64-40) but it keeps coming up.  

Am testing some other small modifications to the battery power_on capacity check since if I leave the tablet charging when switched off, unplug, and then power up, the capacity will remain stuck at the old_capacity value instead of new_capacity.  I haven't committed anything there yet.

Please feel free to test, review and adopt any changes too and if the CrewRK team wishes to put the compiled kernel on the CrewRK website.  Thanks above all to CrewRK for making this possible!

Hi..

Thanks for the update..

I downloaded the compiled version from your custom kernel thread and unfortunately it was looping, but after checking my repo I realised I had not updated the last commit while testing some config options..