yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] siljaer:
possible bug in cyanogen msm8916 kernel

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

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...
[Miscellaneous Android Development] siljaer:
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 [MENTION=7319300]ottmi[/MENTION]'s dts, camera and touchscreen drivers, modified [MENTION=7319300]ottmi[/MENTION]'s device tree and now the ubuntu-cyanogen recovery is booting :) ubports compiles but is not booting yet....
[Miscellaneous Android Development] dioii:
Hello Guys At what iam reading here?, is it true is cm 13 ready for use on samsung s7 edge?
[Miscellaneous Android Development] 21prods:
I don't know, but don't expect a S7 ROM here, this thread is on the Elephone Trunk CM13 developed by [MENTION=7319300]ottmi[/MENTION] with different contributions from others.

Sorry
[Miscellaneous Android Development] kbezerianos:
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.
[Miscellaneous Android Development] zishan.p:
Thanks
[Miscellaneous Android Development] josoft86:
Android 7.1.1

[MENTION=7319300]ottmi[/MENTION]

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:
[Miscellaneous Android Development] ottmi:
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..
[Miscellaneous Android Development] kbezerianos:
Merry Christmas and Happy New Year [MENTION=7319300]ottmi[/MENTION]

I will test this soon and report back with any feedback.
[Miscellaneous Android Development] marcachas:
Merry christmas, AND thanks for the new release, a hug
[Miscellaneous Android Development] siljaer:
Thanks and happy new year!
[Miscellaneous Android Development] saboy1976:
Thank you vert much ottmi for your excellent ROM, for me everything is allright, eap sim works fine.

Happy new year 2017✌
[Miscellaneous Android Development] forart.eu:
Hi guyz,

dunno if can help/inspire, but here's Nougat sources for MSM8916 devices:

https://android.googlesource.com/kernel/msm/+/android-msm-seed-3.10-nougat

(note: at VF-895N - a device based on same chipset - community are working on CM13 too, a collaboration may could help both: http://www.htcmania.com/showthread.php?t=1255937 )
[Miscellaneous Android Development] siljaer:
Nougat for elephone trunk is already here: if you're eager to try it, you can use Mokee for Ark Peach. I have also tried to compile the sources with the small changes (partitions sizes) needed for the trunk: it works. It's only 32 bits, though, and I have tried it only for a few minutes.
[Miscellaneous Android Development] siljaer:
Hello [MENTION=7319300]ottmi[/MENTION],

I have a technical question for you:

we have several popular roms supporting either Benefit A3 or Android One (seed) aka Wileyfox Swift.

Problem is, the A3's vendor files are 32 bits only, while seed's vendor files are lacking the camera's blobs (maybe something more, but I am not sure).

Would it be possible to use the 64 bits seed's vendor files and the 32bits camera's blobs to compile a 64 bits rom?

Thank you!
[Miscellaneous Android Development] josoft86:
I am using it since the first version of "aicp_peach_n-12.1-NIGHTLY-20161222" with no problem including the OTA updates, wanting daily. Tuttio this previously announced on 24.12.2016 with no response from anyone. Although fast 32bit reliable and trouble and wanting us would be the basis for the 64bit if someone is in the ability to do so as ottmi.
[Miscellaneous Android Development] ottmi:
Since when is Android for Seed 64bit? At least the stock ROM - which is the one you want to pick the vendor blobs from - was 32bit last time I checked (I think it was the 7.0 release).

Anyway, the camera daemon for Qualcomm is 32bit regardless whether the rest of the ROM is 32bit or 64bit. So you can easily use the 32bit camera blobs in a 64bit ROM. But be aware that there are more differences between Seed and A3/Trunk like sensors, touch screen, etc.
[Miscellaneous Android Development] siljaer:
Sorry for the delay. Yes, seed blobs are only 32 bits, but swift blobs are 64bits, and it looks like there are blobs for N7.1/CM14.1. Yes, I am aware of the differences, but most of them don't require blobs, AFAIK...
[Miscellaneous Android Development] josoft86:
[MENTION=7529884]siljaer[/MENTION]jaer I wanted to know if you pulled out some rom N7.1 / CM14.1. for 64-bit or you know something about. I am currently using with great satisfaction the Roma "RR-N-v5.8.0-20170115-peach.zip" unfortunately it to 32 bits. From [MENTION=7319300]ottmi[/MENTION] we have no news although I have seen that is working on developing a CM14.1. If you have news you make a whistle. Thanks for your work: :cool::cool:
[Miscellaneous Android Development] siljaer:
I am currently playing with an Omnirom (AOSP 7.1 based) with CAF kernel (with trunk parts borrowed from [MENTION=7319300]ottmi[/MENTION]), 64 bits. It boots with binary blobs from the Wileyfox Swift, but it has many problems I am trying to solve. You can also compile a 32 bits version using the seed tree and binaries with minimal changes ( [MENTION=7319300]ottmi[/MENTION]'s, as per usual) and it works much better, apart from camera, which is still a problem for seed too.

I have also compiled LineageOS and it works with the same binary blobs and tree by [MENTION=7319300]ottmi[/MENTION], but I did not test it thoroughly.

All in all, I think that the CM13 still mantained by [MENTION=7319300]ottmi[/MENTION] (he released an update a few days ago) is still the best choice for a stable rom, though. I am playing with some roms more for experimenting than for producing anything useful. However, I can say two things that can be of some interest for you:

- it is feasible to compile and boot a 64bits version of a rom based on nougat

- the blobs are available: you can use Swift's. You only need to add the blobs for the camera.

Stability and features are a different matter, though. And [MENTION=7319300]ottmi[/MENTION] has managed to produce the most feature rich and polished rom available to date.
[Miscellaneous Android Development] ottmi:
It has been some time since my last post. [MENTION=7529884]siljaer[/MENTION] already mentioned that there was an update to the CM13.1 ROM end of January. Active development on the CM13 ROM has now ceased as I will concentrate on my new LineageOS 14.1 ROM. However, there will be occasional updates to the CM13 ROM via my OTA server to reflect upstream changes (mostly Android security fixes). I think the ROM is stable and can be used as a daily driver for the time being.

That being said, develeopment and discussion on my new LineageOS 14.1 ROM continues here, there's already a first build available:

https://xdaforums.com/android/development/rom-lineageos-14-1-elephone-trunk-t3554011
[Miscellaneous Android Development] saboy1976:
J'ai ottmi, i dont know if anyone else notice a bug with FM Radio, but when i plug my earphone FM Radio crashes. I think i'm gonna to try LineageOS 14.1 ROM. Thank you very much for your excellent work. Thank to you my phone IS forever young.
[Miscellaneous Android Development] ottmi:
I've never tried the radio, so I can't tell. But I've just checked on the new 14.1 ROM and there it works fine. Give it a shot, the new ROM is awesome :)
[Miscellaneous Android Development] ottmi:
I also don't have any problems with crashes. Did you also wipe the caches?

That's really odd. Did you try with a different sdcard? Mounting of sdcard is a kernel issue, and that has been the same for many weeks now. Could you provide a logcat and/or dmesg when mounting fails?
[Miscellaneous Android Development] todoss:
This is problem of all your version. Ports for Ark Benefit A3 with mdeejay's kernel working good. But, after ten reboots, pulling out and pushing back sd card working normaly.
[Miscellaneous Android Development] siljaer:
Thanks for the hint, ottmi. I found this section in my mixer_path_qrd_skuh.xml:

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

and I changed "RX1 Digital Volume" from "90" to "75". Maybe incall volume is a bit low, but people cannot hear their voices' echo, for now.

I realized that handset speaker sound is conducted very well along the phone. So a balance between speaker volume and mic sensitivity has to be found. I think that trying lowering mic sensitivity would be a better option, but unfortunately I don't know how to do it. However, lowering the handset speaker volume that way is good for privacy too.

EDIT:

maybe I've found the setting for sensitivity:

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

I changed it to 80 and I raised "RX1 Digital Volume" to 80. I'll let you know.
[Miscellaneous Android Development] ottmi:
And of course those are some of the values I changed when people complained about low volume on audio recordings :)

https://github.com/ottmi/android_de...mmit/e6974a6755d9b5fb03a92876fbf2e68f7cfe42cf
[Miscellaneous Android Development] siljaer:
That's really interesting: if I experience any problem with my current setup, I will use your original file. I don't care that much about audio recordings...
[Miscellaneous Android Development] ottmi:
New ROM

There's a new ROM available in the download section:

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

Main changes include:

Enabling of Qualcomm Fluence as suggested by [MENTION=6709669]Bingo Bronson[/MENTION] - to help with voice quality

Backport of the F2FS driver from Linux 3.12 - this should fix the problems when trying to use the sdcard as internal memory

Enabling of LTE as preferred network on 2nd SIM card as well - I had issues with my phone not connecting with LTE

Some changes to the auto brightness thresholds - I found it quite useless with the current settings as it would turn to full brightness too soon
[Miscellaneous Android Development] 21prods:
Thank you, [MENTION=7319300]ottmi[/MENTION]. I will give it a try tonight.

Enviado desde mi Nexus 5 mediante Tapatalk
[Miscellaneous Android Development] marcachas:
You're the best, thanks for the continued development, responding quickly to your comment on whether clean the cache, if, clean all cache ROM and still remain closures.

Thank you very much, just a question, you used the last CM code ?, only ask because you always compile with the new version, maybe you did but did not put it in the change history.
[Miscellaneous Android Development] ottmi:
On which apps do you see the crashes? And could you please provide a logcat when it happens?

Yes, it's the latest source. I've edited the changelog accordingly.
[Miscellaneous Android Development] ottmi:
Today's build has a bug that breaks mobile data. I've already removed the ROM from the download section and will upload a fixed version asap.

If you have already flashed it and want to fix it yourself, just add the following line to /system/build.prop:

persist.data.target=dpm1

Sorry for the inconvenience. I shouldn't have tried to clean up the build.prop file ;)

EDIT: New ROM is available for download
[Miscellaneous Android Development] marcachas:
Thank you very much for answering my questions and spend time with us as followers of this great project.

To make it easier to understand and detect these errors, I will be as specific as possible with detected errors.

1. The system collapses. I have the new version of the 14 and the problem persists, the normally use the phone, delays are detected in the audio, for example, the sound of the keyboard, press and do not hear anything, you close and one second later heard all sounds together, like when you start games or any application, followed by this begins to failure, the interface is closed, including the notification bar and placing the wallpaper in black, seconds after the phone reboots, it happens with the most applications, I installed the new version and installing deleting everything from scratch. Note that the flow is less noticeable, that is not going as fluid as the compilation of 06.

2. Lantern. With new compilations, it happens that in the status bar shows me the flashlight icon, which is fully functional, running smoothly, but minutes later it disappears completely and not return until reinstall the ROM.

3. Camera. The camera goes wrong with the version of CyanogenMod, but installing Cameringo photos improve much, another little glitch I detected the change or open the camera, this takes much longer than normal and ultimately give one another ruling, giving the message " camera can not be opened. "

Warmly PD.- you attach the included Catlog to hang and delay sounds. https://drive.google.com/open?id=0ByUbdWBji4kedi0zNWtvbU83WnM

And thank you very much, I followed the instructions and data, continues with this excellent work, if you need help or can donate tell me how they work. :laugh:
[Miscellaneous Android Development] siljaer:
there must be something more than I thought: when I try from landline, no echo. When I call people, they can hear echoes. I also tried your original settings, but no way. Really strange. I will try investigating further on that.
[Miscellaneous Android Development] ottmi:
According to your log, the mediaserver crashes, restarts, crashes, ...

That's why everything is so slow and you notice distorted sounds. I have now idea though why it happens. Could you please to a complete wipe of your phone including any media, reinstall the ROM and only GAPPS and see what happens?

That's a known bug.

The camera can not be opened is because the camera daemon eventually died. Everything related to the camera is quit shaky. I think the only longterm solution would be to borrow the corresponding binaries from some Android 6.0 stock ROM. But that's quite tricky, since nobody but Elephone seems to be using this particular camera sensor..
[Miscellaneous Android Development] ottmi:
What's the situation like on the stock ROM? Might also be related to the mobile network you're using. Could you try on a different network?
[Miscellaneous Android Development] 21prods:
Everything working here (including the SD card as internal memory). I just had to add the line in the build.prop for the mobile data to work, but appart from that no big issues.

Just for the sake of curiosity, is it not possible to enforce SeLinux?

And why the kernel is version 3.10 instead of version 3.40?

Thank you anyway, outstanding work to port CM13 to this phone!

Enviado desde mi Elephone Trunk mediante Tapatalk
[Miscellaneous Android Development] siljaer:
I have never used the stock ROM to make any call. Eventually, if I don't succeed by changing mixer_paths.xml settings, I will try the stock ROM too. For now, setting DEC1 Volume to 75 made a difference with call from/to landline. I need some more experiments with mobile calls. For instance, the person who complains the most has just changed her phone. ...
[Miscellaneous Android Development] ottmi:
I've disabled SELinux for now to ease development. It's hard enough to sort things out even without SELinux interfering..

3.10 is the kernel for which we have the source code for with all device specific drivers. I suppose they could be ported to a newer kernel, but what's the benefit?
[Miscellaneous Android Development] 21prods:
Thank you! I could imagine the point regarding SElinux but I thought the kernel was being updated with every new Android. Which, as I think about it, doesn't make too much sense, does it? More so when our phone doesn't have a stock marshmallow available.

Enviado desde mi Elephone Trunk mediante Tapatalk
[Miscellaneous Android Development] 21prods:
One (maybe silly) question: why Google Play says that some apps aren't compatible with our device? Does it have to do with CM13 being unofficial? Surely not, but I cannot imagine why because they actually are compatible and run smoothly (at least the ones I found in apkmirror).

If this question shouldn't be posed here please tell me.

Enviado desde mi Elephone Trunk mediante Tapatalk
[Miscellaneous Android Development] siljaer:
I reflashed the stock ROM and I made some calls to the trunk from mobile: no echo. So I copied all the mixer_paths*.xml files, reflashed CM13 and pasted them: still echo.

So, no more need to experiment with mixer_paths*, the probem is somewhere else. I've found that such a problem has affected many phones with cyanogen and a real solution has never be found :(

I regret not having made a copy of audio_platform_info.xml

EDIT: I reflashed stock rom and I backed up /etc and build.prop for reference. No audio_platform_info.xml in the stock rom. As a tentative workaround, DEC1 set to 70 and handset speaker set to 75. This setting works for mobile too, though incall volume is a bit low and people I call say they can hear me clearly, without echo, but the volume is a bit low too. But it is a little price to pay in order to enjoy your great work, ottmi :)
[Miscellaneous Android Development] marcachas:
Good day, and thank you very much for responding.

I tell you what happened after following your instructions.

I proceeded to install everything from scratch, deleting everything, including the system folder and all multimedia data, I proceeded to install the ROM and the latest version of Google applications, apparently it worked well for a few minutes, but returned failures, the same mistakes, so I did not solve my problem.

It should be noted that applications use are the same as always, with previous ROMS had not had this problem only with the previous one and now this, I do not know if it's because of my device, also change the cable data if copied ROM bad.

What do you recommend I do ?, the phone is usable but those minutes that clogs the truth if they are a bit disturbing. :fingers-crossed:
[Miscellaneous Android Development] ottmi:
There's /etc/audio_policy.conf in the stock rom though, that shows some differences to the CM version. Could you try whether this makes a difference?
[Miscellaneous Android Development] ottmi:
So does it also crash if you don't install any additional apps besides gapps? How do you install those apps? From a backup or from Play Store?
[Miscellaneous Android Development] ottmi:
No idea, but I've noticed this as well. Maybe it's because it's a userdebug build? Maybe patching the build.prop accordingly would help, but that's just an educated guess..
[Miscellaneous Android Development] :
You are not the only ones... ;) Redmi 2 users face the same issue (and this device receives official CM updates): http://xdaforums.com/showpost.php?p=67324083&postcount=4942 & http://xdaforums.com/showpost.php?p=67333255&postcount=4953
[Miscellaneous Android Development] marcachas:
Here my aplication

Thank you for your attention, I commented, starting the device for the first time, proceed to start restoring my device, the low all from the Google Play Store, I have always done well, you get the list of applications that I occupy:

Loop (game), Cameringo + (Photography), CandyCons (icons), Chrome (browser), Clash of Clans (game), Clash Royal (game), Facebook (social), Gmail (email), Google Opinion Reward (surveys) google Play Games, Messenger, Pages (Facebook), PowerAmp (music), Studio (yotube), keyboard google, Whatsapp and Youtube.

Without any application or game, the operating system works well but after a while also begin crashing.
[Miscellaneous Android Development] siljaer:
Thank you. I am experimenting with my current settings at the moment. I want to understand whether my voice quality is acceptable. I will try the old audio_policy.conf with the next release.

BTW, my phone is rock stable, but I only use F-Droid and no Google stuff.
[Miscellaneous Android Development] ottmi:
Do you have any MP4 video files on your phone? I re-visited your logcat and the stack trace of the mediaserver crash indicates that it crashes somewhere processing MP4 files. I have a similar problem on my phone now: whenever I record a video, the mediaserver will crash when trying to create a thumbnail of the video. Maybe something similar is happening on your phone.

EDIT: I've identified the problem. Seems like this bug has been introduced upstream in libstagefright between the 0606 and the 0611 build. I've just copied the libstagefright binaries from the 0606 build over the 0614 build on my phone and the problem disappeared. I will try to upload a new build later today..
[Miscellaneous Android Development] siljaer:
Hi ottmi,

I've found something else that looks promising: audio_effects.conf

I uncommented the lines:

aec {
library pre_processing
uuid bb392ec0-8d4d-11e0-a896-0002a5d5c51b
}

and I moved them inside the "effects" section.

then I added the lines:

pre_processing {
"mic" {
aec
}
}

pre_processing {
"handset-mic" {
aec
}
}

pre_processing {
"voice_communication" {
aec
}
}

(I was not sure of the right device)

then, in mixer_paths*.xml I raised the DEC1 to 90.

The result looks good, but I have to check with some other people.
[Miscellaneous Android Development] marcachas:
Really Thanks

I'll keep saying, you're amazing.

It seems perfect, today or tomorrow, the work you do is magnificent, a hug from Mexico and I hope to have helped, and hope to help even more.