yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] ottmi:
A new build is available for download:

http://xdaforums.com/devdb/project/dl/?id=19155

The most important changes:

* Switch to the generic CyanogenMod MSM8916 kernel

* Increased system and data partitions

For most users, the data partition will probably already have the right size if they ever did a data wipe in TWRP. To increase the system partition size, please wipe the system partition (and only the system partition) in TWRP before flashing the ROM.

Along with the switch to the CyanogenMod kernel, I've also changed the kernel configuration. It is now based on the Wileyfox Swift configuration which seems to have a smaller footprint and only includes modules which are really required. Please let me know if any modules are missing.

I was able to make most drivers work, but the touchpad driver proofed particularly nasty. I almost broke my phone by accidently overwriting the touchpad configuration and had to obtain it from a friend's phone. As of now, the only driver I had to backport from mdeejay's kernel was the camera driver, but I'm confident to get rid of it as well.

There are only little immediate benefits in using the CyanogenMod kernel: Better accuracy of the light sensor and better - probably less resource hungry - handling of interrupts in the touch panel driver. However, in the long run this should give us better future compatibility, after all, the CyanogenMod kernel receives updates. And most important: the Trunk specific hacks in mdeejay's kernel were really ugly.
[Miscellaneous Android Development] 21prods:
Congratulations and thank you! At the end I have the impression that by buying a Trunk we have got an almost identical copy of a Wileyfox Swift.

Enviado desde mi Nexus 5 mediante Tapatalk
[Miscellaneous Android Development] siljaer:
I tried it for a few minutes, I cannot turn on wifi and the trunk inconsistently charges when connected to a computer usb port. Maybe it's a bit harder to access the tiles lowering the status bar (but I cannot say for sure, I have a new glass on). But light sensor seems to work definitely better as far as I've experienced.

Thank you again!
[Miscellaneous Android Development] ottmi:
Except for the camera and the compass. The fact that the Trunk is so similar to the Swift was actually the reason I bought it. And honestly speaking, I think that the Swift is totally overpriced. It is build on the Longcheer L8150 platform that's also used for many Android One 2nd Gen phones sold in developing countries at prices around 100€ instead of the 160€ Wileyfox is charging.

You mean you can't turn wifi on at all or does it just not connect? I didn't notice any problems with USB charging yet and don't see how it is related to the ROM. What happens if you turn the phone off? Does it charge normally?

The light sensor and the thresholds for auto-brightness may need some more tweaking, but in general, I also think that it is much better and more responsive now..
[Miscellaneous Android Development] siljaer:
I cannot turn it on at all.

I tested the new image with the phone connected via usb. I just noticed that the lighting icon was off while I was testing it and that if I disconnected and reconnected the usb, it turned on immediately. I cannot say whether the phone was actually charging or not before that. I have a netbook running ubuntu where lighting icon takes quite a long time to appear, yet it charges (at least the led says so). I turned on and off the phone several times (flashing, wiping, reflashing...) and I noticed that the elephone logo appeared right after turning it off, so I guess it was about to display the battery animation (I don't know for sure because I entered in fastmood mode right after that).

I will keep experimenting with the wifi later in the evening/night, I have reflashed the backup for now.

EDIT: tried again, same wifi issue, I copied something from dmesg's output:
[Miscellaneous Android Development] 21prods:
Although probably not your case, I have realised that the USB connector of the Trunk is quite tricky and depending on the USB cable sometimes the connection is quite loose. I would try with a different cable but since you are not new to this phone I'm afraid this may not be your solution.

Enviado desde mi Nexus 5 mediante Tapatalk
[Miscellaneous Android Development] josoft86:
I am pleased that my intuition of my post of 10th June 2016, 07:39 AM | # 552 to make the porting of "Cyanogen OS 13.0.0 (6.0.1) Wileyfox Swift" was not so far-fetched. Thanks and he continues to do a great job.
[Miscellaneous Android Development] ottmi:
wpa_supplicant crashes. In fact, it also crashes on my phone. I've just tried with the wpa_supplicant binary from the previous build, that works fine. So obviously, something in wpa_supplicant itself broke since the last build. Which is strange, since there weren't any source updates since then.. I will dig into this..
[Miscellaneous Android Development] siljaer:
and maybe better touch and glass. And MSM8916v2, so it should include better gps and sound (?). And stereo speakers and secondary mic (?). Plus a license for the commercial version of Cyanogen. Marginal improvements, yet there are.

Swift is comparable (better) to Moto G and costs less (well, Moto G is hugely overpriced, especially for the dual sim variant). It's overpriced, but the trunk is a bit overpriced too, as chinese phones with better performance cost less. Wileyfox's phone are targeted to a niche, a niche elephone tried to explore. They both charge a premium for it (Qualcomm instead of Mediatek, being "open", etc) Unfortunately, I don't think there are so many of us. Umi eMax mini is probably better than both of them, when found at 130 eur, but I've read software is quite bad and there's no ottmi for them :) As for developing countries, it looks like they covet more expensive phones, while in the western world (and eastern Europe) there is a quite a demand for low cost phones.

---------- Post added at 23:06 ---------- Previous post was at 23:03 ----------

We're looking forward for next release: last one was a really promising one!
[Miscellaneous Android Development] ottmi:
I wasn't able to fix this problem yet. However, to fix this temporarily, I've prepared an update ZIP that can be flashed via TWRP which will replace wpa_supplicant with an earlier version that should work..
[Miscellaneous Android Development] ottmi:
I don't think that the Trunk is overpriced. Obviously, the Snapdragon 410 comes at a premium compared to the Mediatek SOCs, but that's probably due to Qualcomm's price policy. I don't know of any cheaper Snapdragon 410 phone with 2GB memory.

The Umi eMax indeed looks interesting. Particularly the Sony IMAX214 sensor is nice. The Trunk's photo sensor really sucks and as is it is not very widespread, it's hard to find any other binary drivers for it. The IMAX214 on the other hand is also being used in the Moto G3, so at least there are Android 6 drivers for it.. I'm actually tempted to buy one ;)
[Miscellaneous Android Development] 21prods:
I paid 77€ for my new Trunk in eBay and shortly afterwards I saw an offer on Aliexpress for 66€.

To get Android 6 operating (thanks [MENTION=7319300]ottmi[/MENTION] and CyanogenMod community) and a Snapdragon410 with 2Gb of RAM for that price, I consider it a bargain. Yes, the camera sucks, but it was not high at all on my priority list. I wanted the phone so I could use it as a replacement while I had my Nexus being repared and to experiment with it: the best powerful while economic combination I found.

Edit: LTE channel 20. For me this was essential and in fact it took me quite a long time to find a powerful/economic phone with it (the Trunk being the only one).

Enviado desde mi Nexus 5 mediante Tapatalk
[Miscellaneous Android Development] Dininthedrider:
If we could port the camera from the OPPO A37 (snapdragon 410 too) the image quality would be better. http://www.androidauthority.com/oppo-unveils-photography-focused-a37-699415/

"OPPO has also reintroduced its high resolution photo stitching software, which can take five pictures and process them into a single higher resolution 24 megapixel image."
[Miscellaneous Android Development] siljaer:
I said A BIT overpriced, and compared to phones with MTK chips, which have better performance per dollar. But we all know that MTK is not a viable option...

With that in mind I agree: despite its shortcomings, the trunk is still the cheapest, better equipped (RAM, flash...) and Europe-friendly (frequencies, dual sim) device that can run 64 bit version of custom roms. Too bad sales figures weren't better.
[Miscellaneous Android Development] siljaer:
Thanks, wifi is working now. I will keep it on and test it.
[Miscellaneous Android Development] Dininthedrider:
Look what I have found! Ottmi is that you? XD

https://goo.gl/photos/2usTTeRKDD7qCJMv8
[Miscellaneous Android Development] ottmi:
Ahem, no? Why would it?
[Miscellaneous Android Development] ottmi:
A new version is available for download:

http://xdaforums.com/devdb/project/dl/?id=19226

It fixes the problems with wifi due to a crashing wpa_supplicant. It didn't seem like there was an actual bug in source but something was messed up with my build environment. I cleaned it out and did a full rebuild and now it seems to work properly. As usual, I've also updated to the latest CM13 source.
[Miscellaneous Android Development] Dininthedrider:
This is the easter egg in your rom. Rapid press android version in about phone.
[Miscellaneous Android Development] evgen6375:
A3 Ark, not sewn, the system is not mounted. You can patch the old marking system?
[Miscellaneous Android Development] siljaer:
Flashed and tested. So far so good.

I've installed MultiTouch Test to test the touch: it seems I cannot reach the edges of the screen (I felt that when touching the status bar it wasn't as responsive as before): is it normal? (it does not affect ordinary use, though)

Another question: why is screen density set to 320 dpi instead of 300 dpi (as trunk's density is 294 dpi)?
[Miscellaneous Android Development] ottmi:
Come again?

I can reach the edges just fine. Did it work with the old kernel?

I've inherited the 320 DPI from mdeejay's configuration and didn't give it any thought. But you're right, 300 DPI would be a better fit..
[Miscellaneous Android Development] siljaer:
I did not try with the old kernel :( but it's something you can notice only if you display coordinates: you cannot reach x=0 and y=1279, but it's a matter of a few pixels. Something that you cannot realize during normal use. That's why I asked whether it is normal.

Everything is else is really good: no crashes, long battery life, much better behaviour of light sensor.
[Miscellaneous Android Development] ardrift:
Hi Guys!

I flashed the rom about 3 weeks ago (version 0616), and firstly I want to thank [MENTION=7319300]ottmi[/MENTION] and the other contributors as well for developing this great rom for our device. I've experienced no bugs so far, except the echo thing, which you've been discussing in this forum too. I've tried some things to fix it (flashed all the test1-test6.zip-s) but with no luck. If it's been fixed somehow, can you please tell me the instructions how to fix it? It's very annoying when I hear my own voice while I'm on the phone :/ Thank you very much!
[Miscellaneous Android Development] siljaer:
Hi ardrift,

first of all, you're experiencing something different from what many russian users, some people on xda and me have experienced. We cannot hear any echo, it's people speaking with us who hear echo of their own voice while speaking with us.

That said, the echo cancellation for mobile phone occurs in three places: the two phones and the network. You can try using my workaround, that basically decrease earpiece and mouthpiece volume. In order to do so, you have to edit /system/etc/mixer_paths*.xml file(s). You should also set SELinux to "permissive" if you're using one of the latest ottmi's ROM.

at the beginning of the file, find this line and change 90 (or whatever) with 75:

<ctl name="DEC1 Volume" value="75" />

then find this block:

<path name="handset">
<ctl name="RX1 MIX1 INP1" value="RX1" />
<ctl name="RDAC2 MUX" value="RX1" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="EAR PA Gain" value="POS_6_DB" />
<ctl name="EAR_S" value="Switch" />
</path>

and change 84 (or whatever) with 75.

Reboot and try.
[Miscellaneous Android Development] ardrift:
Sorry for not making it clear... it's not my phone but my brother's and I experienced it, that's why I wrote from the wrong perspective :/ The issue is the same as yours... Thank you for the workaround, I'll try it and give feedback ASAP.
[Miscellaneous Android Development] ardrift:
Thank you very much, it worked!
[Miscellaneous Android Development] siljaer:
Glad to hear that. However, that is simply a workaround with the side-effect to decrease both volumes too much.

I've found something interesting, though:

the block

<!-- EC_REF -->
<ctl name="AUDIO_REF_EC_UL1 MUX" value="None" />

and the block

<path name="echo-reference">
<ctl name="AUDIO_REF_EC_UL1 MUX" value="I2S_RX" />
</path>

the value "I2S_RX" is somewhat strange, as everywhere else in the file you can find "MI2S_RX". But I am not able to decipher that file...
[Miscellaneous Android Development] ottmi:
Same here. Its about 15px at each border. But maybe that's just due to my thick fingers :silly:

So what happens if you change it to MI2S_RX?
[Miscellaneous Android Development] siljaer:
I can go as low as 5px. Are you a bear? :)

I have tried just once, increasing volumes at 90 and calling from a fixed line. I can hear echo :( may I also need to change something else. Or maybe it's just useless, as that line is in the section for dual mic devices. However, it doesn't hurt.

This block is also interesting:

<path name="voice-call">
<ctl name="PRI_MI2S_RX_Voice Mixer CSVoice" value="1" />
<ctl name="Voice_Tx Mixer TERT_MI2S_TX_Voice" value="1" />
</path>

I think I have to find some well commented mixer_paths* file, in order to better understand it.
[Miscellaneous Android Development] frozen2789:
Hello everyone,

first of all thanks to ottmi and all other developers for their great work. I recently got this phone and the CM13 ROM works great. Now I am trying to compile CM13 myself using ottmi's sources in order to learn a bit about compiling android ROMs and to do some small modifications. I put together a local repo manifest pulling all the necessary code and I have the build environment fully running (at least I hope so :D).

However after some minutes the build fails because one of the proprietary files is not found, specifically

/system/lib/libqct_resampler.so

When I run the extract-files.sh I notice that some other files are failing as well, so I suppose there is more than one file missing. I already noticed that you recently started pulling the proprietary files from a Wileyfox Swift ROM. I tried to download a recent CM13 build for the Swift, but still could not find the missing files in there.

Can you tell me where to find these missing files? Or is there anything I am doing wrong?

Kind regards

Fabian
[Miscellaneous Android Development] ottmi:
Good luck finding one ;)

Maybe it's easier to work through the source code and see how the file is parsed and what happens with the data afterwards..

It exists in my backup of the stock firmware. That's probably where I got it from.

But in any case, it doesn't seem to be important. Just remove it from the proprietary-files-qc.txt like they did for the Wileyfox Swift:

http://review.cyanogenmod.org/#/c/142389/

But you did extract the system partition, didn't you?
[Miscellaneous Android Development] frozen2789:
Thanks, I removed the file and now it seems to work.

Yes ;)
[Miscellaneous Android Development] Wenderer71:
Hi bro, thanks to your developments changed the framework. Echo no, the volume in dynamics great;)

mixer_paths_qrd_skuh.xml

<ctl name="RX1 Digital Volume" value="77" />
<ctl name="RX2 Digital Volume" value="90" />
<ctl name="RX3 Digital Volume" value="90" />
<ctl name="IIR1 INP1 Volume" value="90" />
<ctl name="IIR1 INP2 Volume" value="90" />
<ctl name="IIR1 INP3 Volume" value="90" />
<ctl name="IIR1 INP4 Volume" value="90" />
<ctl name="ADC1 Volume" value="9" />
<ctl name="ADC2 Volume" value="9" />
<ctl name="ADC3 Volume" value="9" />
<ctl name="DEC1 Volume" value="77" />
<ctl name="DEC2 Volume" value="90" />

<path name="speaker">
<ctl name="RX3 MIX1 INP1" value="RX1" />
<ctl name="SPK DAC Switch" value="1" />
<ctl name="RX3 Digital Volume" value="90" />
</path>

<path name="handset">
<ctl name="RX1 MIX1 INP1" value="RX1" />
<ctl name="RDAC2 MUX" value="RX1" />
<ctl name="RX1 Digital Volume" value="77" />
<ctl name="EAR PA Gain" value="POS_6_DB" />
<ctl name="EAR_S" value="Switch" />
</path>
[Miscellaneous Android Development] siljaer:
Hi Wenderer71, I am reading just now. Thanks for your attention, I've already updated my file, I'll let you know.

Edit:

thanks to google translate, I realized that some people on 4pda have complained about uneven volumes in headphones. I checked, but unfortunately my ears are not well trained enough to tell for sure. BTW, Wenderer71 released a patch for that (I am not registered, so I can't see it).

However, if such a problem arises, must be caused by:

<ctl name="RX1 Digital Volume" value="77" />
<ctl name="RX2 Digital Volume" value="90" />
<ctl name="RX3 Digital Volume" value="90" />

and:

<path name="headphones">
<ctl name="MI2S_RX Channels" value="Two" />
<ctl name="RX1 MIX1 INP1" value="RX1" />
<ctl name="RX2 MIX1 INP1" value="RX2" />
<ctl name="RDAC2 MUX" value="RX2" />
<ctl name="HPHL" value="Switch" />
<ctl name="HPHR" value="Switch" />
</path>

possibly, RX1 and RX2 must have the same value.
[Miscellaneous Android Development] blahmartinblah:
I installed 20160708. My home button doesn't take me back to the home screen as it used to. The long press still works as expected. Anyone else having this problem?

Also my SD card still doesn't show, I hoped the factory reset and new kernel might have xured the problem Ive been having. It appears very occasionally after reboot (maybe once in 20 boots) and works fine until the next reboot. Does this sound more like a hardware issue?

M.
[Miscellaneous Android Development] siljaer:
Hello ottmi and Wenderer71,

I am exploring what seems a cleaner approach to the echo problem. After searching, reading and trying to make sense of at least something, I've found that digital volume of 84 is equivalent to 0 dB (ideal). That's why we found so often that value. Furthermore, it looks like a good practice to leave the initial mixer settings untouched, and to modify only the needed path sections, that is the opposite of what I have done so far.

That said, I am using the file mixer_paths_qrd_skuh.xml from the latest stock rom (I am attaching it for reference) and I am changing only the following paths, that were:

<path name="handset">
<ctl name="RX1 MIX1 INP1" value="RX1" />
<ctl name="RDAC2 MUX" value="RX1" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="EAR PA Gain" value="POS_6_DB" />
<ctl name="EAR_S" value="Switch" />
</path>

<path name="handset-mic">
<path name="adc1" />
<ctl name="IIR1 INP1 MUX" value="DEC1" />
</path>

and I changed in:

<path name="handset">
<ctl name="RX1 MIX1 INP1" value="RX1" />
<ctl name="RDAC2 MUX" value="RX1" />
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="EAR PA Gain" value="POS_1P5_DB" />
<ctl name="EAR_S" value="Switch" />
</path>

<path name="handset-mic">
<path name="adc1" />
<ctl name="IIR1 INP1 MUX" value="DEC1" />
<ctl name="ADC1 Volume" value="6" />
</path>

I tried, no echo with my fixed line.

then, to improve voice and camera recording, I tried:

<path name="voice-rec-mic">
<path name="adc1" />
<ctl name="ADC1 Volume" value="15" />
<ctl name="IIR1 INP1 Volume" value="90" />
<ctl name="DEC1 Volume" value="90" />
</path>

<path name="camcorder-mic">
<path name="adc1" />
<ctl name="ADC1 Volume" value="15" />
<ctl name="IIR1 INP1 Volume" value="90" />
<ctl name="DEC1 Volume" value="90" />
</path>

but I am not completely sure it works....

would anyone else test it, please?
[Miscellaneous Android Development] saboy1976:
good evening

I have the problem with the sd card to. i have the 20160630 build. i have changed the 16GB SD card with an other but the problem persists. Otherwise I would like to congratulate ottmi for his wonderfull job, the operating life of the battery is endless :good:
[Miscellaneous Android Development] siljaer:
Mine works as usual.

I tried with an SD card that was in my mp3 player. It works, even after a reboot. Sandisk Ultra 16 GB, class 10. I haven't tried other cards, though.

However, in my phone SELinux is set to permissive. I don't know whether it matters, but it doesn't hurt reminding it.
[Miscellaneous Android Development] ottmi:
No, it works fine for me. And it's quite strange. as the button itself seems to work fine - otherwise the long press wouldn't work. What do you get when you execute this in an adb shell and press the home button?

getevent -lt /dev/input/event0

Could I get a dmesg log from you when this happens? It looks to me like a hardware problem, so I'm not sure whether there's anything I could do in software..
[Miscellaneous Android Development] siljaer:
I've made some more changes to mixer_paths_qrd_skuh.xml: I removed the section for dual mic devices and I commented out many lines including IIR filtering and sidetone: I think we don't need it for phone calls, since a similar device (Motorola surnia) doesn't.

I also found the meaning of this block:

<path name="echo-reference">
<ctl name="AUDIO_REF_EC_UL1 MUX" value="I2S_RX" />
</path>

I2S_RX refers to a device connected to I2S. Unfortunately, I couldn't find any reference to I2S in the documentation about msm8916 codec. Ottmi, can you check whether trunk has such a connection?

I guess echo-reference should be the signal we need to subtract from the signal we uplink; ideally it should be picked up by a secondary mic, but maybe we can try with downlink signal.

I don't experience echo with current settings, though.

The problem is now low volume of audio recording....
[Miscellaneous Android Development] blahmartinblah:
Ottmi,

I reflashed the same ROM file. The home button works again! Thanks for your help as usual.

Martin