[ROM][4.4.4] Cyanogenmod-11 for Lenovo A2109 (20160510)

[Jekson91]

unfortunately it is not connected. when arming does not prompt the PIN code on the other device ..

 

[PJBrs]

unfortunately it is not connected. when arming does not prompt the PIN code on the other device ..

I HATE bluedroid. HAAAAARGH!!!!

Okay.

Can you please test the new build here, which has both BLE (bluetooth 4.0) *and* Voodik's supposedly helping build flag

HCILP_INCLUDED                FALSE

The last remaining option after this one is to use the bluez stack and I'm not looking forward to that kind of mess either

 

[Jekson91]

install the latest build. Mouse does not want to do the pairing. I am very upset ... lg p500 cm7, lenovo a3300 stock 4.4.2 bluetooth mouse works without problems. and now does not want to (

 

[PJBrs]

install the latest build. Mouse does not want to do the pairing. I am very upset ... lg p500 cm7, lenovo a3300 stock 4.4.2 bluetooth mouse works without problems. and now does not want to (

Yeah, I don't like this either. I'll put up one last build, with Voodik's little hack but without BLE.

I am afraid that this is a bug in bluedroid. I'm fairly certain that the device tree is correct.

 

[PJBrs]

Last build with bluedroid, now with Voodik's HCIPLUS = false build flag is here. @Jekson91, this is the last build that might make bluedroid work, otherwise bluez is needed, which will take quite a bit more time...

TO ALL!

Those who've read along might also want to try the three latest builds. They all share the improvement that all remaining wifi deep sleep issues are gone. I'm particularly interested in any issues regarding bluetooth. I have three builds to test.

The first has additions that activate all aspects of bluetooth-4.0:
cm-11-20150904-UNOFFICIAL-kai-BLE.zip
md5: a3e700b49ed39222f724ae75d82ca4d6

The second includes those additions too, but also includes a build flag aimed at better compatibility with bluetooth mice and keyboards:
cm-11-20150904-UNOFFICIAL-kai-BLE-VOODIK.zip
md5: 31f3d174a2019c3b98462129dc976021

The third build is like the previous cm-11 roms, but with that build flag aimed at better compatibility with bluetooth mice and keyboards (that's the same one referenced above):
cm-11-20150905-UNOFFICIAL-kai-VOODIK.zip
md5: 23e698214d68a74849d5263427a8655d

In sum, I'm actually trying to find out which build to propose as the next release

 

[jam97]

Thank you PJBrs a lot, now battery drain got fixed, this is awesome!
I wish if you could enable kernel over clocking on this rom.

And how to move the navigation buttons to the left side as same as the stock rom?
Thanks,

 

[PJBrs]

Thank you PJBrs a lot, now battery drain got fixed, this is awesome!
I wish if you could enable kernel over clocking on this rom.

Thanks for testing! Which version did you test? BLE, VOODIK-BLE, or VOODIK? And what was your bluetooth experience?

I wouldn't touch an overclocked kernel by me with a ten-foot pole

And how to move the navigation buttons to the left side as same as the stock rom?
Thanks,

Well, that's just how JellyBean 4.2 and beyond look... Perhaps you can tweak this with the exposed framework? I've never used that though...

 

[jam97]

Thanks,
I installed 20150904 build it runs flawlessly but I dont have a Bluetooth mouse[emoji4] .

 

[PJBrs]

Thanks,
I installed 20150904 build it runs flawlessly but I dont have a Bluetooth mouse[emoji4] .

That would be the BLE one. Did you test any Bluetooth functionality at all? I'm really curious, because at least this build enables some Bluetooth-4.0 functionality that previously wasn't included.

 

[jam97]

Yes Bluetooth is working, I'm able to conect my android 5.0.1 phone with the tablet and exchange files between them successfully.

 

[joebine]

Guys, I have one small request. Can anyone test whether the mic in a headset is detected correctly?

Hi PJBrs,

I had tested the bluetooth headset and the mic is working correctly.

 

[Jekson91]

I think all bluetooth problem in kernel!

 

[PJBrs]

Hi PJBrs,

I had tested the bluetooth headset and the mic is working correctly.

Thanks very much! Good to know.

I think all bluetooth problem in kernel!

Well, if you have any specific suspicions I'd like to hear them, but as far as I can tell both bluetooth kernel drivers and hid drivers are the same for our kernel and the lollipop kernel for grouper, which has the same bluetooth chip. This is also supported by the fact that much bluetooth functionality actually just works with the current kernel. So, my bet still is on bluedroid. But like I said, let me know if you see a specific patch or something that's missing from my tree.

I hope I'll be able to build a rom with a working bluez bluetooth implementation. I did succeed in compiling the bluetooth kernel backport and building bluez for android. I haven't gotten anything to work yet....

***EDIT***
You might be right after all--there's a whole driver missing from the drivers/hid tree, called UHID:

commit ef38bfca1564cf04bde8a06e46f332028c2d4b6b
Author: David Herrmann <[email protected]>
Date:   Sun Jun 10 15:16:13 2012 +0200

    HID: uhid: introduce user-space I/O driver support for HID
   
    This adds a dummy driver that will support user-space I/O drivers for the
    HID subsystem. This allows to write transport-level drivers like USB-HID
    and Bluetooth-HID in user-space.
   
    Low-Energy Bluetooth needs this to feed HID data that is parsed in
    user-space back into the kernel.
   
    Change-Id: Id1023644522b9db1a18bfcc93aaf4685ef31e2ed
    Signed-off-by: David Herrmann <[email protected]>
    Signed-off-by: Jiri Kosina <[email protected]>

 

[yufeng]

Same problem here - cannot enter recovery. I wish I could try KitKat on my old a2109!

Have you solved this problem?

 

[yufeng]

How come the cwm(from this thread) stop at "Booting Android Recovery" on my machine? I did installed sibul rom and cm10 rom.

I Have the same problem. Have you solved this problem?