[ROM] AOSP/CM Jelly Bean 4.2.2 for a2109

Discussion in 'Lenovo IdeaTab A2109 Development' started by PJBrs, Dec 29, 2014.

  1. PJBrs

    PJBrs Senior Member Developer

    Joined:
    Dec 29, 2014
    Messages:
    480
    Likes Received:
    404
    Trophy Points:
    340
    Yeah, I know. Also, I though I understood how to disable these but it turned out I didn't.

    I just don't know how our rom is specific. I can think of only two things--the NvCPLSvc which includes some OTA updater, and the CPU governor which is a tegra specific thing, IIRC (unlikely, since deep sleep only stops occurring after I wake up the tablet after a long time of inactivity (~ eight hours; provided I have disabled the wearables thing, because that's really an issue).

    I did read some post online pointing at configurations of wifi access points. This might be our bug...
     
  2. tasinofan

    tasinofan Senior Member

    Joined:
    Jan 13, 2013
    Messages:
    92
    Likes Received:
    23
    Trophy Points:
    180
    Location:
    Antwerp
    Tablet / Device:
    Medion Lifetab MD 99300 (S9714) aka Lenovo A2110
  3. PJBrs

    PJBrs Senior Member Developer

    Joined:
    Dec 29, 2014
    Messages:
    480
    Likes Received:
    404
    Trophy Points:
    340
    Sigh, one would think so, wouldn't one...

    To be honest, I haven't the slightest idea of what this wakelock thing is and I don't even know how to disable services on boot, so I don't even seem to be able to do anything about it.

    This wakelock thing is turning out to be as annoying and frustrating as the whole camera hal.
     
  4. tasinofan

    tasinofan Senior Member

    Joined:
    Jan 13, 2013
    Messages:
    92
    Likes Received:
    23
    Trophy Points:
    180
    Location:
    Antwerp
    Tablet / Device:
    Medion Lifetab MD 99300 (S9714) aka Lenovo A2110
    Hi PJBrs
    Let's hope and assume 'wakelock thing' is not specific to your valuable contributions.
    I have 2 access points as well (one personal and one for work), and, when I connected to the one for work, I got 70% deep sleep. Next I turned off wifi, and got no more deep sleep. Then, I connect to personal one and got no more deep sleep either.
    There seems to be some similarity with the story you referred to. Somehow some software is confused about wifi/sleep state machinery. I doubt if it can have been caused by you.
    Success
     
    Last edited: May 4, 2015
    • Like Like x 1
  5. PJBrs

    PJBrs Senior Member Developer

    Joined:
    Dec 29, 2014
    Messages:
    480
    Likes Received:
    404
    Trophy Points:
    340
    Okay, that's good to hear, thanks!
     
  6. PJBrs

    PJBrs Senior Member Developer

    Joined:
    Dec 29, 2014
    Messages:
    480
    Likes Received:
    404
    Trophy Points:
    340
    Allllllright. First post updated with new build dated 20150503 for cm-10.1. AOSP build went wrong, will fix later.

    This fixes the camera and an issue that /system got mounted rw.

    Bugs / not working are in the first page. Only little things left, too little to bother with. Battery drain remains, but I can't seem to fix it, and I'm not sure whether it's my bug or Google's.

    Happy testing!
     
    Last edited: May 4, 2015
  7. joebine

    joebine Senior Member

    Joined:
    Jan 14, 2015
    Messages:
    150
    Likes Received:
    32
    Trophy Points:
    210
    I prefer the camera taking pictures well. I don't take video with a tablet...

    Thanks for the hard work
     
  8. PJBrs

    PJBrs Senior Member Developer

    Joined:
    Dec 29, 2014
    Messages:
    480
    Likes Received:
    404
    Trophy Points:
    340
    Both camera and video should be working now :)
     
    • Like Like x 1
  9. DBlake

    DBlake Senior Member

    Joined:
    Nov 29, 2013
    Messages:
    90
    Likes Received:
    24
    Trophy Points:
    180
    Location:
    Ithaca, NY USA
    Tablet / Device:
    Lenovo A2109 (kai)
    I found some info on that post you linked that might help you...

     
  10. PJBrs

    PJBrs Senior Member Developer

    Joined:
    Dec 29, 2014
    Messages:
    480
    Likes Received:
    404
    Trophy Points:
    340
    I found the wake-up problem. Somehow, one stock binary, tf_daemon didn't get copied over, and in its absence the kernel doesn't enter deep sleep. We've all been looking in the wrong place, though understandably so, since disabling that wearables thing really improved deep sleep. Yesterday I finally thought of looking at dmesg output and quickly spotted an error thar mentioned instructions starting with tf_. So, essentially this is an example of PEBKAC with some unexpected kernel behaviour added in. The good news- we have deep sleep again!

    Thanks very much @tasinofan @profeet and @DBlake for testing and thinking along! I appreciate it very much!

    New builds after the weekend.
     
    • Like Like x 1
  11. DBlake

    DBlake Senior Member

    Joined:
    Nov 29, 2013
    Messages:
    90
    Likes Received:
    24
    Trophy Points:
    180
    Location:
    Ithaca, NY USA
    Tablet / Device:
    Lenovo A2109 (kai)
    Could you be able to upload that binary for us to add to our devices form the time being?
     
  12. PJBrs

    PJBrs Senior Member Developer

    Joined:
    Dec 29, 2014
    Messages:
    480
    Likes Received:
    404
    Trophy Points:
    340
    *** EDIT I fixed the link, the first one probably will work just as well ***

    Here you go! I picked tf_daemon from here. (Can't access my build tree right now.) Next, remount /system rw:
    $ su
    # mount -o remount /system

    Move tf_daemon to /system/bin and mark it executable:
    # chmod +x /system/bin/tf_daemon

    Reboot, and all should be fine.
     
    • Like Like x 1
  13. DBlake

    DBlake Senior Member

    Joined:
    Nov 29, 2013
    Messages:
    90
    Likes Received:
    24
    Trophy Points:
    180
    Location:
    Ithaca, NY USA
    Tablet / Device:
    Lenovo A2109 (kai)
    Thanks!
     
  14. PJBrs

    PJBrs Senior Member Developer

    Joined:
    Dec 29, 2014
    Messages:
    480
    Likes Received:
    404
    Trophy Points:
    340
    New builds. Battery drain is fixed, camera fully functional. Not working:
    • Hardware rotation lock button
    • Wifi-direct
    • Receiving files via Bluetooth (AOSP only)
    Autobrightness is a bit wonky, bluetooth MAC address is not right.

    For the rest, everything seems fine!

    AOSP-4.2.2 (md5sum: b84c6d039edff8fd57766615d46f0f6b)
    CM-10.1 (md5sum: 12d29e6dd6aae23b808a49022bdaa1a1)

    I don't expect serious issues anymore. Let me know if you find any.
     
    • Like Like x 1
  15. DBlake

    DBlake Senior Member

    Joined:
    Nov 29, 2013
    Messages:
    90
    Likes Received:
    24
    Trophy Points:
    180
    Location:
    Ithaca, NY USA
    Tablet / Device:
    Lenovo A2109 (kai)
    Nice! Have you considered using vampirefo's tweaked kernel with this (or using his tweaked build script for it)? He has an OC of 200MHz (up to 1500MHz from stock 1300MHz) as well as a lot of governors and such enabled. His kernels also beat stock kernel benchmarks.

    EDIT: I'd honestly say that CM-10.2 (android 4.3) would be a waste of time since it is so very close to 4.2 in features. That being said, can we expect to see a proto build of 4.4 soon? :D
     

Share This Page

Search tags for this page

github android videorecording

,
9714s cyanogen
,
a2109 lollipop
,

a2109a aosp

,
aosp a2109
,
aosp a2109 pjbrs
,
cyanogenmod lifetab s9714
,

lifetab s9714 cyanogenmod

,

medion lifetab s9714 cyanogenmod

,

s9714 cyanogenmod