[ROM][6.0.1] Unlegacy Android 6.0.1/Lineage-13.0 For A2109 [2017-05-28]

[PJBrs]

I've been focusing on bluetooth audio and I'm stuck. I'll see what I can do about completing a first CM-13, with selinux and hopefully the camera crash fix.

@joebine, thanks for testing, I appreciate it very much!

 

[PJBrs]

Quite some progress with selinux, I have only one fix to go, with gps...

 

[PJBrs]

Chances of ever having bluetooth audio are not improving at all. But selinux seems FIXED!!! With one ugly hack, but I have some good ideas about that as well. I should be able to get another test build to you soon.

 

[PJBrs]

SElinux ENFORCING!!!
cm-13.0-20170112-UNOFFICIAL-kai.zip

MD5: 2dbcdef02951930efcc57ff08f369811

Somehow camera still crashes on camera switch. But google camera from play store works without issue?!?!

Everything seems to work, except bluetooth audio.

 

[fusm]

Woo! Let me try.

 

[profeet]

OK, I flash new ROM!
It is really fast & smooth. @PJBrs you are superior, big thanks for your development!
Find few bugs:
- agree with @joebine auto rotation stuck after portret app (for example Theme), help reboot;
- camera FS after switch to front and on front camera doesn't work video recorder;
That'll,very nice for test build.
BT audio I don't use on tablet, it isn't minor bug for me...

 

[PJBrs]

First things first...

I FIXED BLUETOOTH AUDIO!!!!!!!!!

I found a compatible audio HAL from a newer tablet, YEEEEAAAAH!!!! So, no more fallback from the switch to kernel 3.4.

OK, I flash new ROM!
It is really fast & smooth. @PJBrs you are superior, big thanks for your development!
Find few bugs:
- agree with @joebine auto rotation stuck after portret app (for example Theme), help reboot;
- camera FS after switch to front and on front camera doesn't work video recorder;
That'll,very nice for test build.
BT audio I don't use on tablet, it isn't minor bug for me...

Thanks for testing! Of this list, I think the video recording bug is the one I need to, and hope to fix. After that - feature parity with lollipop.

 

[profeet]

I have strange random shutdowns (two times), when I left tablet in deep sleep!
Today at 9 am I left tablet with 70% battery, come back at 4pm, tablet was power of and 20% of battery?
I think it's Kernel adiutor app with CPU and kernel tweaks. I used it for more smooth and fast.
Try to uninstall this app, and looks what happens...

Does anyone have strange random shutdowns in deep sleep?

 

[PJBrs]

@profeet, can you please indicate what exactly you changed? Also, please post the context of

/proc/last_kmsg

if you have that file.

I did see two times that I got a reboot when I plugged in usb...

In the meantime, I now also fixed the prior ugly hack for gps, now we have a nice hack, using working binaries compiled for lollipop from samsung manta device

I did note that none of the drm stuff (widevine) is working. Have an idea for that one too After that, lollipop is deprecated!

 

[profeet]

Yes I have this file.

I change next settings:
- CPU min freguency set 340mhz;
- read ahead memory set to 128 (in I/o scheduler) and use rotation storage;
Also use low memory killer in medium, virtual memory, entropy and kernel same page merging just set apply on boot (default).
That'll!

 

[PJBrs]

Problem with CPU power management, I'm afraid... I think we do have some PM instability, and, more importantly, some lock-ups when plugging in a charger during deep sleep. These are kernel issues.

[22807.672104] WARNING: at kernel/watchdog.c:237 watchdog_check_hardlockup_other_cpu+0x124/0x15c()
[22807.672236] Watchdog detected hard LOCKUP on cpu 0[<c0015750>] (unwind_backtrace+0x0/0x140) from [<c0053da8>] (warn_slowpath_common+0x50/0x68)
[22807.672473] [<c0053da8>] (warn_slowpath_common+0x50/0x68) from [<c0053e2c>] (warn_slowpath_fmt+0x38/0x48)
[22807.672614] [<c0053e2c>] (warn_slowpath_fmt+0x38/0x48) from [<c00b93e8>] (watchdog_check_hardlockup_other_cpu+0x124/0x15c)
[22807.672761] [<c00b93e8>] (watchdog_check_hardlockup_other_cpu+0x124/0x15c) from [<c00b94c4>] (watchdog_timer_fn+0x5c/0x1b4)
[22807.672910] [<c00b94c4>] (watchdog_timer_fn+0x5c/0x1b4) from [<c0077cbc>] (__run_hrtimer+0x88/0x2c0)
[22807.673050] [<c0077cbc>] (__run_hrtimer+0x88/0x2c0) from [<c0078d90>] (hrtimer_interrupt+0x130/0x2e0)
[22807.673191] [<c0078d90>] (hrtimer_interrupt+0x130/0x2e0) from [<c0014c80>] (twd_handler+0x38/0x4c)
[22807.673274] [<c0014c80>] (twd_handler+0x38/0x4c) from [<c00bd230>] (handle_percpu_devid_irq+0xa4/0x1c4)
[22807.673412] [<c00bd230>] (handle_percpu_devid_irq+0xa4/0x1c4) from [<c00b9c40>] (generic_handle_irq+0x34/0x48)
[22807.673559] [<c00b9c40>] (generic_handle_irq+0x34/0x48) from [<c000f5b4>] (handle_IRQ+0x54/0xb4)
[22807.673696] [<c000f5b4>] (handle_IRQ+0x54/0xb4) from [<c00084c8>] (gic_handle_irq+0x2c/0x60)
[22807.673838] [<c00084c8>] (gic_handle_irq+0x2c/0x60) from [<c000e7c0>] (__irq_svc+0x40/0x70)
[22807.673913] Exception stack(0xef0a9f38 to 0xef0a9f80)
[22807.674044] 9f20:                                                       00000000 000f4240
[22807.674123] 9f40: 0000026f 00000000 00000000 e60f3c00 4afc1313 000014be 00000001 412fc099
[22807.674257] 9f60: c0b75560 00000000 3b9ac9ff ef0a9f80 c0272284 c004495c 200e0013 ffffffff
[22807.674404] [<c000e7c0>] (__irq_svc+0x40/0x70) from [<c004495c>] (tegra_idle_enter_clock_gating+0x68/0x78)
[22807.674552] [<c004495c>] (tegra_idle_enter_clock_gating+0x68/0x78) from [<c04db420>] (cpuidle_idle_call+0xdc/0x3a4)
[22807.674692] [<c04db420>] (cpuidle_idle_call+0xdc/0x3a4) from [<c000fbd0>] (cpu_idle+0xd8/0x134)
[22807.674832] [<c000fbd0>] (cpu_idle+0xd8/0x134) from [<8078e234>] (0x8078e234)

 

[PJBrs]

Okay, I think we can call the latest bit relatively stable! Remaining bugs:

• Some power management issue in the kernel, but it's rare and not doesn't seem to get in the way
• The touch screen seems a little bit laggy, but perhaps it's just me...
• The actual video recording bug occurred on every recording resolution that was below screen resolution. I worked around it, but now the preview aspect size of the back camera is incorrect for 4:3 video resolutions (recordings seem fine though). BUT! Front camera video recording is now SOLVED!
  
• The autorotate issue... You don't actually need to reboot, you just need to deactivate and reactivate autorotate
• Then there's the volume button, which appears to be linked by default to phone volume now?!?! Don't know how to solve that.

All in all, we *are* at feature parity with Lollipop, we do have added features from Marshmallow, and kernel 3.4 does seem faster, especially browsing internet with Chrome is rather stable now.

cm-13.0-20170120-UNOFFICIAL-kai.zip

MD5: ecf43adb830be0d338b4c2868a4ae7ca

Please post any /proc/last_kmsg that you find! Report any spurious reboots! I have some small ideas for working around them. But to me, I think this might be the first build to replace lollipop.

 

[Reidless]

I know this may sound silly but I saw a few articles saying the stock firmware got an upgrade to marshmallow. I didnt click the links but it seems like you could get a copy of it here:

Update/Upgrade to 6.0.1 Marshmallow for Lenovo Ideatab A2109 16gb | Custom ROM Android Operating System Upgrade/Update

I don't know if anyone has tried updating or installing the rom, and I'm not sure if having this rom could help in the building of CM13 but I thought I would mention it.

 

[profeet]

@PJBrs i find seriuos bug with sdcard.
If use sdcard like internal storage cwm recovery dosen't see it.

 

[Reidless]

I am having some issues with my SD card too. After installing the new rom, CM13 was telling me the SD card needed to be formatted but would error out trying to format it. I kept reseating it and still had the same issue. I jumped back to CM12 to see if it would work but it didn't (i think the failed format messed it up). I took out the SD card and used a tool on my computer to reformat it in FAT32 format. After reformatting my micro SD card it is not visible in CM13 or in CWM, and I no longer have an error message saying my SD card isn't working properly.