yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] siljaer:
[MENTION=7319300]ottmi[/MENTION], thank you for your great work and commitment!

I have flashed your last rom, and I am about to give some very imprecise feedback. Problem is, I have messed everything up by trying adopted storage then disabling it, so I am pretty certain that the random reboots I am experiencing are my fault. Nevertheless, before I investigate further this issue (if necessary), I am telling you, just in case someone else has noticed the same.
[Miscellaneous Android Development] saboy1976:
Hello ottmi, i've just realised that the maximum resolution in camera app is 5 M pixels instead of 13. I've a better camera app the problem is the same with native app. Thanks.
[Miscellaneous Android Development] ottmi:
Hmmm, mine shows (among others) "(4:3) 12.8 megapixels". Can anybody else confirm this?
[Miscellaneous Android Development] jan_100:
[MENTION=7319300]ottmi[/MENTION],

i just checked which resolutions i can use (tried opencamera & 'stock' camera application): I can just choose up to 5mp as well. But I am sure in one of the earlier builds there was an 13 option as well (I remember I changed that to the native resolution of 5mp - but sadly I don't remember which build I used).
[Miscellaneous Android Development] siljaer:
I am quoting jan_100 word by word...
[Miscellaneous Android Development] ve66:
Well, some updates: I downloaded the last release of the ROM and before flashing it I wiped cache, dalvik, data and system. After that I flashed Gapps and, at the restart, the mobile has updated Android correctly, recharging a backup that I had in Google Drive. Everything was loaded well and now notifications work properly.

About the camera the highest resolution that now appears is 5mp but I can say with ABSOLUTE CERTAINTY that, before solving these problems and install this release, resolution was up to 13mp. Otttmi: really a great work! [emoji106]

[MENTION=8074991]karabassssss[/MENTION] and [MENTION=722204]blahmartinblah[/MENTION] : can you please send me an answer if I can have your broken phones paying the shipping costs? Many thanks

Inviato dal mio TRUNK utilizzando Tapatalk
[Miscellaneous Android Development] kbezerianos:
hello [MENTION=7319300]ottmi[/MENTION]

today I have tried to re-image from your latest CM13 (from thread hxxps://xdaforums.com/android/development/rom-cyanogenmod-13-0-elephone-trunk-t3394060) to the current LineageOS (from this thread).

I just want to note (because it was mentioned on a previous post as well) that after the last OTA update on CM13 (a few months ago) I had random reboots. This was happening a couple time per day even when the phone was not used - obvisouly not relevant on this thread, but I though you may wanted to know.

Now on this upgrade, I have rebooted to TWRP (version 3.0.2.0) and wipped everything, except the microSD (where I had the rom packages), unfortunately I then found out that microSD storage was not visible, so I tried to install the rom using adb sideload.

File seems to transfer OK, and installation starts, but there is an error displayed which leaves the phones without an OS. I am providing 2 screenshots below:

hxxp://www.and-gate.com/images/trunk/rom/rom%20install%20errors%201.PNG

hxxp://www.and-gate.com/images/trunk/rom/rom%20install%20errors%202.PNG

Any ideas on how can I install the new ROM using adb sideload successfully?

Thank you in advance,

kind regards.
[Miscellaneous Android Development] ottmi:
The log error messages are normal. Did you actually try rebooting? I've seen the error message about the missing OS a couple of times, but every time the OS has been installed correctly..
[Miscellaneous Android Development] kbezerianos:
Thank you for the reply.

Yes, I have rebooted and just getting an animated image of a "sad face" - or this is how I see it! :)

I may be using an older version of TWRP - how can I get the one you customised for your rom?
[Miscellaneous Android Development] saboy1976:
Unfortunatly , i have random reboots with LineageOS 14.1 , this happens any time. I dont Know if i'm the only one who has this problem. If anyone could tell me how to resolve this it would ne nice. Thank you ans have a Nice day.
[Miscellaneous Android Development] ottmi:
New ROM 20170409

There's a new ROM available for download:

https://xdaforums.com/devdb/project/dl/?id=24150

I'll update the changelog tomorrow. It mainly contains upstream updates but should also fix the problem with the camera that shows only 5 megapixels.

Can you post a screenshot of that?

The TWRP I've published in the CM13 Thread should work fine:

https://xdaforums.com/devdb/project/dl/?id=19861

Please try the new 20170409 ROM I've just uploaded. That should fix it.
[Miscellaneous Android Development] siljaer:
Yes, resolutions are ok now. Thank you!
[Miscellaneous Android Development] kbezerianos:
Hello [MENTION=7319300]ottmi[/MENTION] , needless to say that it was just my stupid assumption and you were right - the installation was completed and the phone booted successfully after some time ~ 6-7 minutes!

(I accidentally found out after I took a photo of the screen and was working to upload it)

The "an animated image of a "sad face"" that I wrote is obviously the OS boot animation image!

Link of the image (just for the record) is below:

hxxp://www.and-gate.com/images/trunk/rom/lineage%20boot.PNG
[Miscellaneous Android Development] saboy1976:
Thank you very much for the very good work you do for our "trunk". Thanks to you my phone doesn't age. Your last update resolved all issues.
[Miscellaneous Android Development] siljaer:
Omnirom 7.1.2 (64bit) from @ottmi's kernel & device tree

I managed to compile a working omnirom 7.1.2@64bit, at last :)

Unfortunately, BT keeps on disconnecting, but more on this later.

Kernel is [MENTION=7319300]ottmi[/MENTION]'s kernel, with unchanged config. I've only added an option to load only the trunk's DTBs, because:

a) I had already modified the CAF kernel that way (a separate subdirectory with trunk specific files). But camera isn't working yet with CAF kernel...

b) omnirom builds 64bit kernel uncompressed and it was faster to import that change into ottmi's kernel in order to make the bootimage much smaller. It's probably unnecessary, though, if you build a compressed kernel.

Currently, I am testing it and it seems to work reasonably well (but I am not using gapps, only F-droid...). I am not posting it here, unless someone is curious about it, since I should upload at least device tree beforehand :) It has less features than Lineage, but I was willing to try something more AOSP-like. It's also not rooted, and I think you can only use SuperSU. I tried it, but the one app I needed root for crashes (oandbackup).

device tree is based on omnirom's seed device tree (32 bit) and [MENTION=7319300]ottmi[/MENTION]'s device tree. Blobs are from [MENTION=7319300]ottmi[/MENTION]'s tree, but I had to add some 32bit libraries in order to make GPS work. I don't know why, but omnirom loads the 32bit HAL (not the 64bit one) and it requests some missing 32bit libraries.

Unfortunately, the logcat format is quite different, so it's difficult to make a comparison. However, I think I am having several problems with SELinux. Bluetooth keeps disconnecting and logcat shows:

04-17 18:20:54.750 12017 12035 W bt_hci : start_up not turning off the chip before turning on.
04-17 18:20:54.750 12017 12035 I bt_vendor: bt-vendor : BT_VND_OP_POWER_CTRL: On
04-17 18:20:54.750 12017 12035 W bt_vendor: Hw_config: First Time BT on after boot.Starting hciattach daemon BTStatus=
04-17 18:20:54.749 12045 12045 W sh : type=1400 audit(0.0:479): avc: denied { getattr } for path="/system/bin/sh" dev="mmcblk0p23" ino=31615 scontext=u:r:bluetooth_loader:s0 tcontext=u:object_r:shell_exec:s0 tclass=file permissive=0
04-17 18:20:54.757 12045 12045 F libc : unable to stat "/proc/self/exe": Permission denied
04-17 18:20:54.757 12045 12045 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 12045 (sh)
04-17 18:20:54.757 221 221 W : debuggerd: handling request: pid=12045 uid=1002 gid=1002 tid=12045
04-17 18:20:54.761 12046 12046 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

Maybe someone knows how to solve that :)
[Miscellaneous Android Development] ottmi:
You probably need to backport some of the files in drivers/media/platform/msm/camera_v2/isp. Just do a diff of my kernel with the Cyanogen kernel and it should become ovbious.

You should probably set selinux to permissive to rule that out as the cause of the problem..
[Miscellaneous Android Development] siljaer:
Thanks, [MENTION=7319300]ottmi[/MENTION]. Already tried that, with both /camera dirs (yours and CAF's). I did not investigate the issue, though. I am waiting for the next CAF release, due in a few days, to restart trying.

Yes, I'll do that as ASAP. I already tried the easy way (SELinuxModeChanger), but without root it doesn't work...
[Miscellaneous Android Development] siljaer:
Actually, disabling SELinux didn't help. Maybe the problem lies in the HCI layer in the bt stack. Actually, the /hardware/qcom dir structure has already required many changes to the camera HAL in the device tree. Maybe I should try to use the /hardware/qcom from CAF. I will try something like that...
[Miscellaneous Android Development] ottmi:
New ROM 20170419

I'm currently uploading a new build, it should be finished in a few minutes. Nothing spectacularly new, but upstream LineageOS pulled in Android 7.1.2 from AOSP and also included the April security patches.

Apart from that I've re-enabled F2FS now that it's available in the upstream msm8916 kernel. If you want to use it you will have to re-format the cache and data partitions. I will upload a new TWRP build that is able to handle F2FS and hence can do this for you. However, keep in mind that the so-called "internal SD card" is really a sub-directory within the data partition. So if you backup the data partition there and then format it, you will loose the backup. I had to find out the hard way..

I've also pulled in a change from some other msm8916-based devices to enable the Pinner service that supposedly makes the phone snappier by pinning some apps in memory, i.e. not swaping them out if low on memory. I didn't notice any impact, but also don't think that it hurts. Looking forward to your feedback.
[Miscellaneous Android Development] siljaer:
I'd like to add that, though "internal SD card" is actually part of data partition, when you backup data TWRP WILL NOT backup files in the internal sdcard!
[Miscellaneous Android Development] ve66:
I'm downloading it, as soon as possible I will install it and give U my feedback :good:
[Miscellaneous Android Development] saboy1976:
hello , i have flashed the new twrp via rashr, i changed my file system to "f2fs", but when i install the last update, installation failed and tells me" E3003:can't install this package (wed 19 apr 13: 02:42 cest 2017) over newr build (thu 20 apr 10: 30:25 cest 2017).

I finally, changed, file system to ext4, and flashed an old rom, because when i installed twrp 3.02 with fastboot, recovery didn't boot. So i flashed twrp 3.02 with rashr and flashed the last rom, which is very good.?
[Miscellaneous Android Development] AiBees:
Same Problem here. TWRP seems to be buggy. After formatting Data/Cache in F2FS i tried to restore my latest Backup, some Kind of errors, nothing happens (they are on an external SD Card ;) . Question: Isn't it possible to restore a partition without the filesystem when i will restore an ext4 to an f2fs?

After that i tried to install the new ROM, clean with fresh formatted Partitions, error. (Sometimes Error 7 and i have seen this E3003).

And i notice that when i will shutdown or restart directly to Recovery with TWRP it doesn't work and will try to boot the system.

Now i go back to previous Version.

Note: Maybe it's my fault. I tried to update the .img within TWRP. Now i tried to go back to 3.0.1, Bootloop. Will check it with a PC.
[Miscellaneous Android Development] AiBees:
OK, Back again from my Windows PC. With Fastboot i could clean the Recovery Partition and installe the TWRP 3.1.0-0. Again I reformat all Partitions except the external SD Card. First oprion, Data+Cache in F2FS, won't work. Next all in ext4, won't work. Log says:

E3003; Can't install this package (Wed 19 Apr 13:0242 CEST 2017) over newer build (Thu 20 Apr 10:30:25 CEST 2017)

Prozess Updater endete mit FEHLER 7.

Now i reflashed TWRP 3.0.2-0 and it works! But, since some releases, i get two errors with the ROM Files.

After "Patching system image unconditionally..." the log says:

E: unknown command [log]

E: unknown command [log]

The Installation runs successful. Any ideas?

btw.: Thanks for your Work :)

Update: TWRP 3.0.2 (the older one) and/or F2FS won't work stable. My Phone reboots suddenly and i lost the whole Data Partition...
[Miscellaneous Android Development] ottmi:
For some stupid reason the new TWRP refuses to flash ROMs that are older than TWRP itself. Obviously this doesn't make much sense, but I'm too lazy to investigate further. Instead, I've uploaded the new ROM 20170430 that can now be flashed with the new TWRP as well. It's only upstream LineageOS changes, the most important ones being kernel security fixes..
[Miscellaneous Android Development] jan_100:
Hi,

i have used the 20170430 version for a few days now, very stable. No random reboots anymore (i skipped the last two iterations). Camera seems to work better than before (better focusing), but i don't use the cam very often. Superb Rom!

There seems to be only one problem: At least on my device, the equalizer (AudioFX) seems to do nothing. Don't know if this is a new problem, as i never used it before. Does anybody else have the same issue?
[Miscellaneous Android Development] kbezerianos:
Hello all,

I am running the previous version without any issues.

In order to upgrade to the new one, I just install it on top of the existing one, use & app data won't be lost, right?

thank you in advance.

kind regards
[Miscellaneous Android Development] Bizen-Ya:
Hi,

Thank you ottmi, great work as usual !

I have charging issues, anyone has the same or it's my phone who gets old ?

- when phone is off, i can see the power logo if i push the power button, even if i'm not on the wall charger.

- sometimes the power charge logo appears , phone running & not charging

- i can't charge with my power bank, other devices are fine

- the phone wake up many times for nothing ( > 3x / min )

Thank you !
[Miscellaneous Android Development] siljaer:
some omnirom updates

Hi,

I am sorry I am not testing [MENTION=7319300]ottmi[/MENTION]'s LineageOS build, but I am using my omnirom build as a daily driver. But I am following closely your work because it's so useful for my build. Some updates:

Camera and camcorder are working fine now.

Bluetooth SElinux permissions have been fixed. Unfortunately, bluetooth isn't working reliably yet. Yes, it was ALSO a SELinux problem, but not only that. Actually, I thought it wasn't working because BT keeps on disconnecting during discovery, but later I discovered that it works nevertheless, and I can transfer small files. Unfortunately, disconnections occur continuously, so I don't think it's actually usable. I am using it as a daily driver just because I don't use bluetooth at all.

I am using a CAF kernel with [MENTION=7319300]ottmi[/MENTION]'s driver modifications. It's working now, and I think it's a sensible choice for an AOSP based ROM. I know that there are some peculiarities with CM-LineageOS kernels though I can't say whether they matter. So I am using the CAF kernel.

This is what happens when bluetooth stops and restarts:

05-11 00:50:00.765 4879 4911 E bt_hci : command_timed_out hci layer timeout waiting for response to a command. opcode: 0xfd53
05-11 00:50:00.765 4879 4911 E bt_hci : command_timed_out restarting the bluetooth process.

Still a problem...

apart from bluetooth, it's working reasonably well, at least for me. When bluetooth is sorted out, I think will publish sources on github.
[Miscellaneous Android Development] Bizen-Ya:
Got it , it's an hardware issue, my usb port is almost dead.

Thank you anyway, i hope my phone will survive as long as possible :)
[Miscellaneous Android Development] siljaer:
Omnirom: bluetooth fixed :)

Ok, I (well, someone else actually...) have fixed bluetooth, so the rom is usable. I will start uploading sources as soon as my home internet connection recovers (yes, it's down...).

BTW, [MENTION=7319300]ottmi[/MENTION], the fix for bluetooth came from here:

https://github.com/omnirom/android_...mmit/a778a3b8b9613a11cf5e00e013a68bb6561e81dc

A6000 is a simple msm8916-based phone; there is also the kernel, and I think it has some interesting things that I am going to check:

https://github.com/omnirom/android_kernel_lenovo_msm8916

namely, it backports code from 3.10.103 google source...
[Miscellaneous Android Development] siljaer:
lc709203 driver

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

I am puzzled: in your init.target.rc there is this code:

on boot
# charger
chown system system /sys/bus/i2c/drivers/lc709203/batt_capacity
chmod 0660 /sys/bus/i2c/drivers/lc709203/batt_capacity

However, I cannot find the setting for lc709203 in the kernel config. Is the kernel driver enabled anyway?

I don't know whether to add it or not in my omni kernel. Thanks!
[Miscellaneous Android Development] siljaer:
First OmniROM build

My build is ready: https://xdaforums.com/android/development/rom-omnirom-7-1-2-elephone-trunk-t3612056

unfortunately, bluetooth isn't working at all now. I think it must have been some last minute change and I hope to fix it soon.

BT fixed (again).
[Miscellaneous Android Development] Diamorphoses:
Hi,

Two months ago my Elephone Trunk's USB entry stopped working. It was impossible to charge the phone. I honestly didn't want to buy a new phone. I am very happy with my trunk setup so, as a workaround I bought an external battery charger, but it is a pain in the ass to remove battery, charge, put battery back on, adjust date and time settings etc...

So I ordered a Xiaomi Redmi Note 3 Special Edition - 3gb/32gb - which supports LTE band 20 and 28 :good: (don't really like 5.5'' devices but couldn't find any better for the price and specs I was looking for). I will now use my trunk as spare device in case my new phone gets lost.

I am writing to say goodbye to the Trunk community in this thread and a WARM THANK YOU VERY MUCH SIR to [MENTION=7319300]ottmi[/MENTION] and his commitment and hard work, and to everybody else who helped him in the development of this ROM.

I will see you around.
[Miscellaneous Android Development] AiBees:
Bug: LiveDisplay Automation

The LiveDisplay won't work if it's turned to Automatic.
[Miscellaneous Android Development] siljaer:
Sorry for you trunk... have fun with your new phone, Xiaomis are well supported by community!
[Miscellaneous Android Development] saboy1976:
Hello, i can't take video with "a better camera" and the native application. I can take photos. I don't know if I'm the only one.
[Miscellaneous Android Development] srka99:
Me too
[Miscellaneous Android Development] ve66:
I'm the third....

More I have random reboots, crashing apps (especially browser), low volume talking with earphones

Inviato dal mio trunk utilizzando Tapatalk
[Miscellaneous Android Development] siljaer:
How can it be possible? The latest LineageOS is three months old, how come it's suddenly showing all these problems?
[Miscellaneous Android Development] ve66:
As I told in a post a couple of months ago I installed the ROM, but I didn't posted my comments, problems and issues that I had (and I have still now), but now you know.... [emoji41]

Excuse me for this, I'm not really "constant" in frequenting forum, sorry....

Inviato dal mio trunk utilizzando Tapatalk
[Miscellaneous Android Development] ve66:
hi Diamorphoses, as I asked some posts ago I need some spare parts for my Trunk. I tried to contact the official site but they told me that there aren't spare parts for this mobile, so I'm looking for someone that has a broken Trunk to send me. I live in Italy and I'll pay for the shipping cost, I will be very glad if you could contact me

Hi karabassssss, can you please contact me if I can have your broken phones paying the shipping costs?

Hi blahmartinblah, can you please send me an answer if I can have your broken phones paying the shipping costs?
[Miscellaneous Android Development] karabassssss:
unfortunately I haven't seen it, and threw it

and now I purchased a new elephone trunk :)

tried last fw from here. all great but camera crashed when trying to record video. Anyone else experiencing the same ?

Thanks
[Miscellaneous Android Development] karabassssss:
is this a dead end of lineageos for elephone trunk ? :(

thanks
[Miscellaneous Android Development] saboy1976:
You should try the siljaer OmniROM 7.1.2 for Elephone Trunk, with weekly update. https://xdaforums.com/android/development/rom-omnirom-7-1-2-elephone-trunk-t3612056.
[Miscellaneous Android Development] karabassssss:
yep, I'm aware of it. Still asking if this rom to be continued or abandoned ?
[Miscellaneous Android Development] ottmi:
It's almost dead. I've recently switched to a Moto Z, so I'm not going to do much active development for the Trunk anymore. I will try to occassionally build new ROMs but I've been quite busy the last couple of weeks and I'm not sure whether this will change any time soon. A new ROM should be available in the next couple of days..
[Miscellaneous Android Development] karabassssss:
that's great!

Generally I repurchased a new trunk after my prev trunk dead only due to existence of your build :)

there is also a few bugs with camera in last build available. it won't record video.

Also if you would able to post some manual of compiling your build and syncing with lineageos tree, I'd try to give my hands on this to help you with builds for this device.

thanks
[Miscellaneous Android Development] siljaer:
What a a shame :( Your work has been invaluable for the trunk community!
[Miscellaneous Android Development] karabassssss:
Any change that we'll get a new release soon ? :)

thanks
[Miscellaneous Android Development] ottmi:
New build is available in the download section, but it's only upstream changes, video recording ist still not working. I've tried to fix it, but to no avail. Mediaserver keeps on crashing as soon as a recording is being started. I will have to dig a bit deeper, but won't make any promises when I will find the time for this...
[Miscellaneous Android Development] karabassssss:
thanks!

It would be great to have video recording fixed.

thanks again
[Miscellaneous Android Development] dimqua:
[MENTION=7319300]ottmi[/MENTION] do you plan to support LOS for Trunk officially? If not, why?

FYI, your builds works well on my ARK Benefit A3. Thanks!
[Miscellaneous Android Development] karabassssss:
any hope for upstream build & mediaserver fix ?
[Miscellaneous Android Development] jerrefurtor:
any plans to fix the mediaserver? :)
[Miscellaneous Android Development] karabassssss:
looks like no much plans for this :(
[Miscellaneous Android Development] siljaer:
AICP for Trunk

I am taking advantage of this thread to link my AICP rom, based on [MENTION=7319300]ottmi[/MENTION]'s work: https://xdaforums.com/android/software/rom-aicp-elephone-trunk-ark-benefit-a3-t3719380
[Miscellaneous Android Development] josoft86:
You have news how to download twrp-3.2.1-0 for Trunk

http://cs5-2.4pda.to/11717976.png
[Miscellaneous Android Development] ottmi:
New build, camera recording working

So my new Moto Z broke just before christmas and I had to send it in for repair. Now I'm back with the Elephone Trunk and spent a fair amount of time over christmas fixing the issues with camera recording. I think I suceeded and making available a new build based on LineageOS 14.1.

Everything seems to be working, but it's very well possible that I broke something during my experiments with different proprietary blobs while fixing the camera. If you encounter any issues, please report back here.

Other than the camera fixes, there's only upstream LineageOS fixes included. Enjoy and Happy New Year!