yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] cool400:
[MENTION=7319300]ottmi[/MENTION] I'm not able to install the update in any way.

I think the problem is, that I mounted the SD-card as internal memory so that it's mixed up with the ROM :-/

The update downloads without problems to the folder "cmupdater". But no matter where I move or copy the zip to, in TWRP these folders are not shown!

If I try to copy the ZIP to any of the folders that I can see in TWRP, my phone says there's not enough space left to copy (only 19MB).

Maybe that's my problem why TWRP doesn't find any of the "normal" folders?
[Miscellaneous Android Development] ottmi:
I think I will have to re-compile TWRP with a support for adoptable storage to make it work with this kind for configuration.. In the meantime you can just download the updates via a webbrowser and update from sdcard:

https://it-chefs.com/cmota/builds/full/

There's also a new update available for download now. No particular changes for the Trunk, just CM13 upstream changes..
[Miscellaneous Android Development] ottmi:
I personally have no interest in the Resurrection mix. I will try to upgrade to CM14, but will probably wait for a few more weeks until it is more mature. And maybe until there are official Crackling CM14 nightlies which would make my life much easier ;)
[Miscellaneous Android Development] ikzouhetnietweten:
Elephone Trunk, funny name lol.
[Miscellaneous Android Development] marcachas:
Many thanks, the Rom work perfect, really thanks ????
[Miscellaneous Android Development] josoft86:
[MENTION=7319300]ottmi[/MENTION] welcome back. Already installed updated regularly and everything OK. It would be possible to activate the option of a "Patch MSM8916_5ghz_enable.apk" to have Wi-Fi faster. Thank you:o:o:o
[Miscellaneous Android Development] siljaer:
"...And summer’s lease hath all too short a date..."

Wellcome back :)

As CM14 is AOSP7 based, I think there is at least one problem: a different HAL for power management. Good news are that Qualcomm has already released CAF7 for msm8916_64, so they should have sorted it out for us :) I've made some experiences with CAF6.01: I managed to compile without errors, by looking at several CAF5 configuration files from 8916 based phones. Unfortunately, the resulting images did not even boot :( I will try again with CAF7, but my skills must improve a lot...
[Miscellaneous Android Development] Aditya Kr:
thanks bro
[Miscellaneous Android Development] blahmartinblah:
Does the Trunk have the required hardware this? Eg antenna?
[Miscellaneous Android Development] ottmi:
I've built a new version of TWRP that should work with adoptable storage:

https://it-chefs.com/cmota/builds/full/twrp-3.0.2-201601010-trunk.img

Could you please try and see whether that solves your problem?

In other news, there's a new build on the OTA server now, again only with upstream updates. So it's mainly the October Android patches..
[Miscellaneous Android Development] ottmi:
I don't even think that the Snapdragon 410 has support for this..
[Miscellaneous Android Development] todoss:
Seems to be okay now. Only first time TWRP did not show sd card, and each time after it is presented correctly.
[Miscellaneous Android Development] marcachas:
Thanks for your great Rom. But give me a error when search the update for OTA. ):
[Miscellaneous Android Development] ottmi:
Harr.. Putting the TWRP image in the same directory made the OTA server crash as it really expects filenames to start with cm. I think I've fixed it now, please try again..
[Miscellaneous Android Development] marcachas:
Works now, thanks for you're great work.
[Miscellaneous Android Development] siljaer:
it's working :)
[Miscellaneous Android Development] cool400:
Hi ottmi,

unfortunately it doesn't solve my problem :(

I flashed this TWRP via fastboot and downloaded the latest CM-update from your server (20161011), but while the flashing I was stuck again in TWRP without access to the CM-file. Everything was like before, I had no success to find the downloaded file anywhere in TWRP, though it's located in the "Download"-folder on my (adoptable combined) SD-card-storage.

Any other ideas how I can flash your latest CM-update?

Best regards

Mischa
[Miscellaneous Android Development] saboy1976:
I have the same problem, the sd card isn't shown in twrp, and twrp gives me This message, "E: failed to Mount decrypted adopted storage device".
[Miscellaneous Android Development] saboy1976:
Hi , since the last update, my sd card isn't find, i have formated the sd , the sd is found at the first boot, but after a reboot, the sd isn't shown .

i just want to specify that i have 2 elephone trunk, and only one has the sd card bug.
[Miscellaneous Android Development] olidroide:
[MENTION=7319300]ottmi[/MENTION] thanks for your work and the great effort to maintain this device alive and fresh with cm13 :)

I have a strange problem, but I dont find anyone with this problem... I test a cm12 with TWRP 2871 and all works perfect. The problems comes when update TWRP to version 302-20160816 or greater... when touch an option of main screen is like "hold pressed" but I don't have the finger over the screen... One touch is like still pressed and need touch again for a "normal touch". The real problem comes after install cm13 and try to use the keyboard. When I touch over a letter, it keep pressed and shows the popup alternatives to that letter and is imposible to write anything...

Anyone found this problem and solve it? if I revert to TWRP 2871 the problem is fixed, but I can't install cm13 and need revert to cm12 :(

Thanks!
[Miscellaneous Android Development] kbezerianos:
dear all,

some feedback on the latest updates.

I was running cm-13.0-20160811-UNOFFICIAL-trunk.zip with twrp-3.0.2.0 (not 20160816-trunk.img available on this thread)

updated to cm-13.0-20160902-UNOFFICIAL-trunk.zip using sideload (because of the sd card issues - was not detected on most reboots)

updated to cm-13.0-20161011 using OTA

superb work guys!

minor issues to report:

a) sd card

is not

detected on reboot cycle, it

is

detected on power off / power on cycle

b)one time only - sim cards were not detected on power off / power on cycle, but I wasn't able to reproduce it

c) sim card operator is not detected (unknown) on my vodafone UK sim card - I am not even sure that is related with the os

overall very stable, very fast, OTA works fine

again, superb work
[Miscellaneous Android Development] blahmartinblah:
Oh no, not SD issues again? ;)

No problem for me on 20161002, think I will hold off updating...
[Miscellaneous Android Development] ottmi:
So do I understand correctly that the touch functionality is broken both on TWRP and one of my CM13 builds?
[Miscellaneous Android Development] ottmi:
Regarding the sdcard issues in the latest cm13 and TWRP builds: Somehow I messed everything up when I updated the kernel from upstream and lost the sdcard fixes. There are new builds with the sdcard fixes on the OTA server:

https://it-chefs.com/cmota/builds/full/cm-13.0-20161024-UNOFFICIAL-trunk.zip

https://it-chefs.com/cmota/builds/full/twrp-3.0.2-20161024-trunk.img

[MENTION=3230868]cool400[/MENTION]: can you please try and check whether the new TWRP is able to find the update? If not, could you please post the output of the following commands?

adb shell find / -name "cm-13*"
adb shell mount
[Miscellaneous Android Development] olidroide:
Hi [MENTION=7319300]ottmi[/MENTION] I think the problem comes from TWRP, because it happens in the menu of TWRP. For example: I touch over "Backup" sections, and this button keep like feel pressed without any finger touch the screen. I need touch again to "release" the pressed state button to enter the Backup section.

This behaviour occurs too after flashing cm13, imagine touch the keyboard and any letter keep pressed, is impossible to write anything.

I reject the idea of hardware issue because it not happen with old version TWRP 2781 and cm12. Only happen when load the TWRP 3.0.2 and after flash with this recovery cm13, maintain that strange pressed behaviour :S :S

any thoughts?

Thanks!
[Miscellaneous Android Development] kbezerianos:
quick update on version 20161024

I have been running this version a couple of days already and did several reboots - SIM cards & SD cards issues resolved

thank you again for the excellent work
[Miscellaneous Android Development] ottmi:
[MENTION=2955002]olidroide[/MENTION]: That's really strange. Can you please post a dmesg from the cm12 and cm13 boot process?
[Miscellaneous Android Development] olidroide:
[MENTION=7319300]ottmi[/MENTION] thanks for your support. Here you can find the dmesg of TWRP 2871 (working) and TWRP 3.0.2-20160816 (Touch fails)

https://gist.github.com/olidroide/bab93da698ae3e9f8d3eb64a38403af7

If you need more details or videos told me ;)
[Miscellaneous Android Development] ottmi:
This is really strange.. My cm13 builds and also the TWRP rom use a different kernel than the cm12 builds and the older TWRP. It includes a newer driver of the Goodix touchscreen driver and apparently something is not working with your particular phone. The driver detects the touchscreen just fine, but obviously doesn't handle the touches correctly.. I will have to dig deeper into the code and the device trees to see what the problem could be.
[Miscellaneous Android Development] olidroide:
[MENTION=7319300]ottmi[/MENTION] Thanks! if you need more logs, testing or anything please told me I can help you :) Do you think is a problem on Modem/Radio firmware or something similar?
[Miscellaneous Android Development] ottmi:
No, this is probably just a problem with the touchpanel driver firmware and/or the touchpanel firmware. I did some hacks to make it work with the generic CyanogenMod msm8916 kernel, maybe some of those messed up things for you. But it's still odd, as nobody else reported any problems with their touchpanel..
[Miscellaneous Android Development] olidroide:
Yes sounds truly strange anybody had this problem before :S I have experience rooting and flash devices and I'm sure to do all steps correctly. You already have a patched TWRP? :)
[Miscellaneous Android Development] josoft86:
CM_14 for Trunk

[MENTION=7319300]ottmi[/MENTION]

I wanted to try the truly remarkable "4PDA-cm-14.0-20161023-UNOFFICIAL-peach.zip" version, everything works great lines, sin is not multilingual and taken only for "ARK Benefit A3" to x32e not for x64 as our Trunk. It could be a good reference for us also CM14.

Thanks again for the great work you do.:cool::cool:
[Miscellaneous Android Development] ottmi:
It won't be a reference for us because these suckers never publish the sources of their builds. I'm waiting for some other msm8916 device to receive cm14, maybe the Wileyfox Swift or Moto G3.
[Miscellaneous Android Development] josoft86:
CyanogenMod 14.0 (arm, x32) for ARK Benefit A3

Core description: 3:10:49-CyanogenMod

version of Android: Android 7.x Nougat

Finally, not a door, collected from the source image to CM14.0 ARK Benefit A3.

Source device: https://github.com/Ben...peach/tree/cm-14.0-wip

Proprietary part: https://github.com/Ben…r_ark/tree/c... [url]https://yadi.sk/d/XFe--eo9xSMKw

This build is much more stable of what I put above.

This is the beginning, the beginning of the custom firmware Android N. UPD1.

The installation may encounter a similar error - E: Unkown command (log) - ignore!

Translated from Russian site 4PDA -ARK Benefit A3 - x32
[Miscellaneous Android Development] ottmi:
Interesting. Can you provide the full (working) links to the Github repositories?
[Miscellaneous Android Development] blahmartinblah:
https://github.com/BenefitA3/android_device_ark_peach/tree/cm-14.0-wip

https://github.com/BenefitA3/proprietary_vendor_ark/tree/cm-14.0-wip
[Miscellaneous Android Development] mili2110:
hey guy,

I bought my dad the elephone trunk. It is really slow compared to my gs7. especially input lag when scrolling etc. (especially twitter)

does cm13 rom eliminate that kind of lag?
[Miscellaneous Android Development] 21prods:
Is GS7 a Galaxy S7? Then I'm afraid there isn't anything you can do to make the Trunk as fast as the GS7. As you probably already know one phone is a flagship the other one is just a very good phone but never similar to it.

Having said that, IMO you will get the best out of the Trunk with this CM ROM built by [MENTION=7319300]ottmi[/MENTION] . In fact I'm very happy with the result and there are not any lags on the OS itself.
[Miscellaneous Android Development] ottmi:
There's a new build available on the OTA server with the latest CM13 upstream changes:

https://it-chefs.com/cmota/builds/full/cm-13.0-20161108-UNOFFICIAL-trunk.zip

[MENTION=2955002]olidroide[/MENTION]: I've also created a new TWRP build that uses a different configuration for the touchpanel. Could you please check whether this works for you?

https://it-chefs.com/cmota/builds/full/twrp-3.0.2-20161108-trunk.img
[Miscellaneous Android Development] marcachas:
Thanks, but AudioFX don't work ):

Edit.- i have a lot of fc and reboots, for example AufioFX and Clash Royal. Help ):
[Miscellaneous Android Development] ottmi:
You will have to be a bit more specific and provide logcats for the FCs. With regard to AudioFX: there seems to some resource missing in the package, probably an upstream bug. Not much I can/want do about it now..
[Miscellaneous Android Development] marcachas:
The latest version works smoothly, but when opening certain applications gives me errors, a major error is in AUDIOFX, which does not open directly.

The second error is with games and when opening two applications, the phone is locked and restarted automatically.

Edit.- Open whatsapp and tap on camera option and reboot the phone.

):

I gladly attach the following logcat: https://drive.google.com/open?id=0ByUbdWBji4keOHBVUERNWjVuYWZ6ZnlNeFhtTzd5N1RZYXlF
[Miscellaneous Android Development] olidroide:
[MENTION=7319300]ottmi[/MENTION] it works! :) nice! thank you!!! TWRP now is fully working, also I test the last CM Rom than you build and also works, sometimes happens the same error (touch pressed in a letter in the keyboard) but sometimes not like before. Now is possible to write :victory: How I support your work?

EDIT:

After a day with the new cm13 and new TWRP, the problem comes back... less than before... but... is strange... is like finger pressed in the screen... I will send you a screencast video by private message. TWRP works great but cm13 not again :S
[Miscellaneous Android Development] josoft86:
[MENTION=7319300]ottmi[/MENTION] Dear, thank you for the work you are doing and I hope you will continue to make giving us the CM14. I wanted to advise you, if technically possible, put in SuperUser updates to avoid any update to reinstall it. Thanks again and good work.:cool::cool::cool:
[Miscellaneous Android Development] josoft86:
Last Build 20161108

[MENTION=7319300]ottmi[/MENTION]

Excuse me, but with activating the cameras last update: Room MX, FV.5 Camera, Camera Zoom, the phone crashes and restarts, only Cameringo Lite operating normally. Now I try to do the old Build restore where I had no problem. If you can make a check, I would not want that to be my phone that has this problem even if I uninstalled the app several times with no positive result. Thank you.
[Miscellaneous Android Development] ottmi:
There's a new update on the server that should fix the issues with AudioFX and the camera:

https://it-chefs.com/cmota/builds/full/cm-13.0-20161116-UNOFFICIAL-trunk.zip

[MENTION=2955002]olidroide[/MENTION]:

Can you try this boot image and see whether it solves the touch issues for you?

https://it-chefs.com/cmota/builds/full/boot-20161116-trunk.img

Just do the following:

adb reboot bootloader
fastboot boot boot-20161116-trunk.img
[Miscellaneous Android Development] marcachas:
Thaaaaanks. Work perfect now. A hug.
[Miscellaneous Android Development] ottmi:
Does it keep working after a reboot with the flashed boot image?
[Miscellaneous Android Development] josoft86:
With this version all the camera work but we have problems with SuperSu and Xposed. After installation go to LOOP start and will not start again. Made several attempts and also the normal SuperSu update without TWRP, it does not work. You can solve !!!!!! !!!!!!:angel::angel::angel::angel:
[Miscellaneous Android Development] olidroide:
Hi [MENTION=7319300]ottmi[/MENTION] thanks for your work and sorry by delay on reply you...

After download it and try to boot from bootloader (AKA fastboot mode) not go into TWRP directly boot the animation start and boot loop in the animation, nothing happens :S too strange :S
[Miscellaneous Android Development] siljaer:
Is fastboot working?
[Miscellaneous Android Development] siljaer:
I guess your only hope is ROM flashing via Qualcomm tool. Look for the trunk flashing ROM tutorial on the elephone BBS and follow carefully the instructions; you could brick it for good. Good luck!
[Miscellaneous Android Development] ottmi:
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..
[Miscellaneous Android Development] ottmi:
So just to be clear: You've flashed the 20161116 ROM and that boots? But if you try to boot the boot-20161116-trunk.img it bootloops? Can you provide a logcat?
[Miscellaneous Android Development] olidroide:
Hi [MENTION=7319300]ottmi[/MENTION] I only open fastboot mode and boot with the command

fastboot boot boot-20161116-trunk.img

this not open a recovery, boot directly to the system. I don't flash the ROM 20161116 because I have the old TWRP. I will attach you the log later ;) thanks [MENTION=7319300]ottmi[/MENTION]

UPDATE

This is the dmesg of boot: https://gist.github.com/olidroide/96d77542440d7ffd02ad33dde0d5ea9c
[Miscellaneous Android Development] ottmi:
You were supposed to use the boot image with my CM13 ROM, it probably won't work with any other ROM - which would explain the bootloop. Also this has nothing to do with TWRP, the recovery image and the system image are independent of each other.
[Miscellaneous Android Development] olidroide:
Hi [MENTION=7319300]ottmi[/MENTION] thanks for you advise I do this:

Boot bootloader to install recovery twrp-3.0.2-20161108-trunk.img

boot recovery twrp-3.0.2-20161108-trunk.img

Wipe data

Install cm-13.0-20161116-UNOFFICIAL-trunk.zip with open_gapps-arm64-6.0-pico-20161124.zip

reboot in bootloader for boot boot-20161116-trunk.img

RESULT:

cm13 load but the touchscreen problem now is worst :S :S I copy the dmesg after boot firsts time CM13 with the boot image: https://gist.github.com/olidroide/03946bd7f590d6e4100a1d6ae2f47144 Maybe we can't find a solution for this issue... I revert the changed restored the official Android 5 image :S [MENTION=7319300]ottmi[/MENTION], Do you think we can find a solution? doesn't matter if is too complex I don't wanna take too much time of your. Thanks really for your support :)
[Miscellaneous Android Development] siljaer:
Prego!

Sorry for the delay.... however, it's good to know that you're on board again! :)

---------- Post added at 19:09 ---------- Previous post was at 19:06 ----------

Hi [MENTION=7319300]ottmi[/MENTION],

I've found this: https://github.com/BenefitA3

what do you think about it? Can it be useful to us?
[Miscellaneous Android Development] ottmi:
I particularly like how they copied all the modifications I did for the Trunk to their repository without giving credit..

Anyway, there's quite a few devices now with official CM14.1 support, including the Moto G3 that uses the same chipset. So it shouldn't be too hard to get it up and running, but currently I don't have the time to do it.. Maybe I will find some time over christmas..
[Miscellaneous Android Development] siljaer:
Your CM13 is working so nice that I am not eager to try CM14 :) My question was about any possible improvement in the kernel(s). Unfortunately, you said it is quite the opposite :(

BTW, I am doing some experiments with ubports (looooong way to go), and I've found that your kernel is missing(?) /include/linux/blk_types.h . I had some problem also with blk-iopoll.h (file name too long (?), but this is probably due to some mistake of mines).

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).

I am reporting here because I am not sure at all the corrections I made are the right ones....

Edit: files were ok, for some unknown reason archive manager did not expand them (!)
[Miscellaneous Android Development] saboy1976:
Good morning everybody, i Wonder if anyone else have a problem with EAP-SIM ,because since i've installed android 6 on my both trunk, i have authentification error when i want to connect my phone to "FREE WIFI SECURE" in France with "Free Mobile" sim card, with lollipop the authentification worked. Thanks for all you've done for our Trunk. Have a nice day .
[Miscellaneous Android Development] ottmi:
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?
[Miscellaneous Android Development] ottmi:
EAP-SIM was indeed disabled.. I've created a new ROM that should now enable it. Could you please try whether that works? It's available via the OTA server.
[Miscellaneous Android Development] saboy1976:
Thank You ottmi i'll try This as soon as possible.:good:
[Miscellaneous Android Development] ottmi:
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
[Miscellaneous Android Development] siljaer:
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).
[Miscellaneous Android Development] marcachas:
This new build is for all or only to test? Thanks
[Miscellaneous Android Development] olidroide:
Thanks [MENTION=7319300]ottmi[/MENTION] 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 ;)
[Miscellaneous Android Development] ottmi:
This is for everybody. But besides the SIM-EAP change there's only upstream CM13 changes..
[Miscellaneous Android Development] josoft86:
[MENTION=7319300]ottmi[/MENTION], 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....:o:o:o