josteink / device_asus_tf101

cyanogenmod compatible device tree for asus tf101
12 stars 6 forks source link

SL101 issues: Keyboard and Camera #30

Closed uysalere closed 11 years ago

uysalere commented 11 years ago

I know you are not claiming that this ROM is compatible with SL101, but it is nearly there except a few important bugs. I'm sure all the SL101 owners will appreciate if you can do these few additions.

1) Tablet goes to sleep when keyboard is open. Therefore, keyboard is useless. I think it is the issue against using.

2) Rear camera is inverted.

Other than these, everything works as expected. TF101 and SL101 are really close in terms of hardware, only few exceptions. For ICS, this compatibility pack below solved the issues. Maybe it can lead you towards what is different. http://forum.xda-developers.com/showthread.php?t=1586382

dlumberg commented 11 years ago

Out of curiosity, have you tried flashing that compatibility pack in CM10.1?

Looking into the zip I mostly just see different config files. There's only a few binary files, The SL101-Dock*.rom file (which I'm not sure what it does) and the HCD files (which are run time patch files to the bluetooth firmware).

Also aside from possibly the HCD files (I didn't check the file #s) and some Permissions files it looks like everything is getting added and not overwriting anything.

I'm pretty sure that most of this stuff is in there anyway, although I'm not sure what the deal with the kernel is. You might try Kat without the lidpatch to see if that fixes 1).

If you look here: https://github.com/timduru/tf101-katkernel/blob/master/arch/arm/mach-tegra/board-ventana.h you can see that Tim has included at least some of the SL101 code (which leads me to believe that all of it is there) so if the compatibility pack doesn't work you could probably petition Tim to add a wrapper to the kernel's camera code for the SL101's back camera.

uysalere commented 11 years ago

Thanks for your quick response.

I tried flashing that compatibility pack, but it actually doesn't make any difference. And flashing nolidpatch on top of this firmware results in crashing the boot since I believe they are no longer compatible. I need to find out what version of your ROm the last nolidpatch is working with.

I went through the code as you said and I think it has something to do with something on this file. I'll try to edit stuff myself and see if I can fix something.

https://github.com/timduru/tf101-katkernel/blob/8a301a92f9847324933912a8cf416493f2a5ec8f/drivers/input/asusec/asusec.c

josteink commented 11 years ago

Just to let you know, you're right. I think Tim only created a lidpatch-kernel with a cm10.1 compatible initrd.

If nothing else works I can quickly cook together a non-lidpatch kernel from his files which you can test.

If that works, we can just ask Tim to build more kernel versions, or we can alternately maintain some alternate kernel images ourselves.

josteink commented 11 years ago

And flashing nolidpatch on top of this firmware results in crashing the boot since I believe they are no longer compatible.

I tried quickly cooking up a test-kernel, but the newest pre-made I could find without any lidpatches was KatKernel 96, from Tim's old archive.

It's not new, it's not super up to date, but it should be sufficient to test if the lidpatch has anything to do with your problem.

Basically what I've done is taken the nonlidpatch kernel-image and extracted that only from the ZIP, and injected this into the similar KatKernel 96-image with a CM10.1-compatible initrd.

What that should yield is a CM10.1 compatible KatKernel 96 nonlidpatch: Try it out!

If that works, we definitely know the cause of the problem and can take it from there.

uysalere commented 11 years ago

Thanks for all your work and taking time to compile the kernel, but apparently lidpatch isn't the problem

I flashed the kernel you gave based on "timduru Mar 25" on top of your "May 9 ROM" but still tablet gets automatically locked when keyboard is slid out. When keyboard is not used, it is working fine though.

It is like there is something wrong in the hardware keyboard enable sequence such that it locks automatically.

josteink commented 11 years ago

If nothing else, we have determined that it's not lidpatch-related. And that's a start.

You can try your luck and see if Tim will hear your case. He's usually pretty at good at figuring these things out.

If you (or Tim) finds that there's something we can do to support the SL101 better, I'm all for it.

josteink commented 11 years ago

I have limited time to maintain this ROM and I haven't seen any more demand for this.

Closing this one as wont-fix.