• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM][UNOFFICIAL][6.0.1] CyanogenMod 13.0 for Elephone Trunk

Search This thread

ottmi

Senior Member
Mar 3, 2016
232
364
Munich
besides, I have found a problem in /drivers/input/touchscreen/gt9xx/goodix_tool.c:389:5 (format '%lu' expects long unsigned int instead of unsigned int).
So either change the %lu to %u or remove "CONFIG_GT9XX_TOUCHPANEL_DEBUG" from your kernel config so it doesn't compile goodix_tool.c
 
  • Like
Reactions: siljaer

siljaer

Senior Member
Jun 12, 2016
213
123
Distopia
So either change the %lu to %u or remove "CONFIG_GT9XX_TOUCHPANEL_DEBUG" from your kernel config so it doesn't compile goodix_tool.c

Thank you, I actually changed %lu to %u, but I wasn't so sure about it.

However, my efforts to recompile the kernel in order to support ubports were a failure. Compilation always breaks. In order to write a configuration without any incompatible settings, I also used make menuconfig, but it still broke.
Maybe I am making some strange mistake (yet I used to compile kernels that way in the old Slackware days...) or maybe the settings required by ubports are untested/unsupported by the msm8916 android kernel. Some options like sys V ipc aren't used in android AFAIK, and I've found that some options like userspace name support also break mainline kernel.

I expected many problems, but not before even building a kernel image :)

I will experiment with the AOSP kernel for android one seed and ubuntu touch phablet-6.0 (because ubports is based on CM13, but i tried the kernel config changes suggested for an AOSP kernel). It won't work for sure, but I just want to figure out what's going wrong with the kernel (hopefully).
 
  • Like
Reactions: marcachas

olidroide

Member
Sep 15, 2010
25
30
Madrid
That's really strange. The boot image should use the same kernel like the TWRP image. And that worked fine with your display, didn't it?

Thanks @ottmi I will need test in more detail. In TWRP the feel is ok (scroll good, touches good) the UI in TWRP is less complex than UI of Android and maybe I can't take notice if it happen too in TWRP. I will test in more detail and I will give you a better feedback. Now I have two devices I will try to record it to show you the problem ;)
 

josoft86

Member
Mar 9, 2015
30
15
Reggio di Calabria
I neither use use Xposed nor SuperSU, so I really have no idea why they wouldn't work.. But what do you need SuperSu for? CM comes with integrated SU..

@ottmi, sorry if I reply late, but until version of "cm-13.0-20161116-UNOFFICIAL-trunk" never had problems installing both "SuperSU-v2.78" that "Xposed-v86-sdk23-arm64" used by me quietly for a long time. After the OTA Trunk Installation is no root with "Root Checher Basic" in testing, that's why after updates install both applications and everything worked. I have not tried the latest update to occur. Thank you so much for your time and see you soon....:eek::eek::eek:
 

siljaer

Senior Member
Jun 12, 2016
213
123
Distopia
possible bug in cyanogen msm8916 kernel

Hi @ottmi,

I am writing to you because you are an active developer of the cyanogen msm8916 kernel (besides ours!).

I think there is a long standing problem with CONFIG_USER_NS, that is necessary to use containers (rarely used, though). In fact, I found an interesting trend about it: http://forum.odroid.com/viewtopic.php?f=98&t=5984&p=47597#p52095

I managed to find the commit: https://github.com/hardkernel/linux/commit/aa4ba07269ece18ebfaf1febbd78f395fdf40d7a

the changes that solved my compilations problem were only the ones in kernel/sched/core.c . I haven't figured out what the other ones do.

However, I am making progresses: now I have built several non booting kernels for ubports :) I am eager to finally build one that boots and crashes :D

Update: actually, is more complicated. With a different kernel config I managed to get errors in the other files included in the commit. CONFIG_CGROUP_CPUSET also triggers similar errors in /kernel/cpuset.c with a similar function (cpuset_allow_attach).

...the joys to be stuck to a kernel subversion while mainline goes on...
 
Last edited:
  • Like
Reactions: marcachas

siljaer

Senior Member
Jun 12, 2016
213
123
Distopia
kernel fixed (partially)

Ok, I managed to fix the kernel: basically the problem was a function with one less parameter in parts of the kernel that are compiled only when certain namespaces are enabled. I solved the compilation errors one by one looking at the mainline kernel. Unfortunately, the msm pft driver has a problem not so easy to solve and is not in the mainline. Disabling the pft driver forces to disable some more crypto hw drivers.

However, I chose the cyanogenmod kernel for the wileysoft swift provided with cm12.1 (you need cm12.1 for ubports to work, and the 6.x branch of ubuntu touch isn't ready yet), I added @ottmi's dts, camera and touchscreen drivers, modified @ottmi's device tree and now the ubuntu-cyanogen recovery is booting :) ubports compiles but is not booting yet....
 
  • Like
Reactions: marcachas

kbezerianos

Member
May 30, 2016
12
5
This is for everybody. But besides the SIM-EAP change there's only upstream CM13 changes..

Hello ottmi and thank you again for the great release.
I have tested the new version (with EAP-SIM enabled), but unfortunately it's not working.
I have updated to the latest version 13.0.20161129 and tested SIM authentication in London's tube stations.
I have a SIM from Vodafone UK ( 2 years old) (operator appears as Unknown under the SIM settings) and attempted the Vodafone WiFi connection in several underground stations unsuccessfully - the message show Authentication Failure.
(I have another SIM from Vodafone Greece - 2+ years old - the operator is displayed properly, but I can't use it for WiFi access in the UK)
I have been using my UK SIM in iPhone and London's tube WiFi was working fine.
Not a major issue for me, just letting you know.
Kind regards.
 
  • Like
Reactions: ottmi

josoft86

Member
Mar 9, 2015
30
15
Reggio di Calabria
Android 7.1.1

@ottmi
I wanted to give a Christmas card and inform you that I have installed for testing for x32 ARK Benefit A3 the official version of "aicp_peach_n-12.1-NIGHTLY-20161222.zip." fino'ora and I had no problems and also tried the first OTA update correctly. I am going to test also "cm-14.1-20161224-NIGHTLY-peach.zip" official and also "MK71.1-peach-201612241722-NIGHTLY.zip" to verify their operation. Everything found on 4PDA-ARK Benefit A3 - Firmware site. I hope soon to see them on our 14.1-cm Trunk 64bit. Soon with a good job greeting: cool :: cool:
 
  • Like
Reactions: marcachas

ottmi

Senior Member
Mar 3, 2016
232
364
Munich
Hello ottmi and thank you again for the great release.
I have tested the new version (with EAP-SIM enabled), but unfortunately it's not working.
I have updated to the latest version 13.0.20161129 and tested SIM authentication in London's tube stations.
Maybe they are not using EAP-SIM but EAP-AKA which is the USIM (UMTS SIM cards) equivalent of EAP-SIM. I've created a new build with EAP-AKA and EAP-AKA' enabled. Maybe this helps. It's available via OTA or direct download from:
https://it-chefs.com/cmota/builds/full/cm-13.0-20161225-UNOFFICIAL-trunk.zip

It also includes the latest upstream CM changes, including the December patches..

Merry christmas..
 

kbezerianos

Member
May 30, 2016
12
5
Maybe they are not using EAP-SIM but EAP-AKA which is the USIM (UMTS SIM cards) equivalent of EAP-SIM. I've created a new build with EAP-AKA and EAP-AKA' enabled. Maybe this helps. It's available via OTA or direct download from:
https://it-chefs.com/cmota/builds/full/cm-13.0-20161225-UNOFFICIAL-trunk.zip

It also includes the latest upstream CM changes, including the December patches..

Merry christmas..

Merry Christmas and Happy New Year @ottmi
I will test this soon and report back with any feedback.
 

marcachas

Senior Member
Apr 18, 2016
70
13

siljaer

Senior Member
Jun 12, 2016
213
123
Distopia
  • Like
Reactions: marcachas

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    This ROM is a genuine CM13 build from source for the Elephone Trunk. It's based on mdeejay's Ark Benefit code with modifications by @BlueFlame4 and @hisname. The source code is available on GitHub.

    Working:
    • Phone
    • Mobile data in dual-sim configuration
    • Wifi
    • GPS
    • Bluetooth
    • Audio

    Known Bugs:
    • Torch tile in the status bar is not available
    • Haptic feedback on soft buttons


    XDA:DevDB Information
    CM13 for Elephone Trunk, ROM for all devices (see above for details)

    Contributors
    ottmi, siljaer
    Source Code: https://github.com/ottmi/android_device_elephone_trunk

    ROM OS Version: 6.0.x Marshmallow
    ROM Kernel: Linux 3.10.x
    Based On: CyanogenMod

    Version Information
    Status: Beta
    Current Beta Version: 20160902
    Beta Release Date: 2016-09-02

    Created 2016-06-07
    Last Updated 2016-09-02
    10
    New ROM is up: http://forum.xda-developers.com/devdb/project/dl/?id=19864

    It now hopefully includes a working thermal-engine that should fix the overheating problems. Also, I brought back the audio_effects.conf that should enable echo cancellation also for VoIP calls.
    I've updated the kernel to reflect the latest changes upstream, including patches against the QuadRooter vulnerabilities. However, the QuadRooter scanner by Check Point still shows the phone as vulnerable to CVE-2016-5340 which is odd since the new kernel includes Code Aurora's patches (see https://www.codeaurora.org/invalid-path-check-ashmem-memory-file-cve-2016-5340). So maybe the patch doesn't fix it properly or the app is buggy. There are similar reports for other phones as well.

    I've also uploaded my own build of TWRP 3.0.2 that should fix the issues with the realtime clock. I was able to do a backup with it and also flash the new ROM but apart from that I haven't tested it much. So use at your own risk. But then again, this applies to everything I upload here :)
    http://forum.xda-developers.com/devdb/project/dl/?id=19861
    9
    I've just uploader a new ROM:
    http://forum.xda-developers.com/devdb/project/dl/?id=20162

    It includes the patched kernel that hopefully fixes the sdcard problems as well the fix for the previous ROM that corrects the thermal-engine and audio effects. Apart from that, I've now switched to the Wileyfox blobs for everything but the camera and tweaked the auto-brightness a bit more. I think it's much better now (at least for me ;)). Also, I've setup my own server for OTA updates - so from now on you can conveniently update from your phone.
    8
    Okay, it worked with Gapps Pico - thanks a lot! I installed all the other Google apps from the Playstore :)
    Quick heads-up on the next build:
    any space issues with the system partition will be solved. Turns out that the actual partition is 1.8GB but I'm using only 1GB for the filesystem. So the next build will have 800M of extra space - that should be sufficient for any gapps package.

    Also I will return to the generic CyanogenMod MSM8916 kernel. I had problems with this kernel earlier, with camera and sensors not working. I've solved the problems with the sensors (and actually improved sensitivity for the light sensor) and for now I've also fixed the camera problems by backporting the driver from mdeejay's Ark Benefit kernel. I also had to backport the touchpanel driver, but I'm quite confident to make it work without any backported drivers. All issues until now were due to errors in the devicetree..
    7
    Just in time before the weekend, here's a new ROM for download: http://forum.xda-developers.com/devdb/project/dl/?id=19444

    It incorporates @siljaer's changes to mixer_paths.xml - let's see whether this solves the echo problems for others as well :)

    Apart from that there are only minor changes: I added some more permission files for the lights and proximity sensors, set the screen density to 300dpi, and backported the LZ4 compression from the vanilla 3.12 kernel to use it in ZRAM (the stock rom did so as well). I've also applied a hack that restarts the media service after the phone has fully booted. I've seen this in the Oneplus Onyx source and it seems to improve the issues with the disappearing torch tile.