yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Guides, News, & Discussion] jcadduono:
My test user said that the pure stock kernel with CONFIG_TIMA=y would not boot past the bootloader screen (with KERNEL IS NOT SEANDROID ENFORCING), but when I disabled that, they said they were able to boot but it reboot whenever they reached the lock screen.

I know one of the TIMA options disables building vmm.elf and uses a proprietary prebuilt vmm.elf in the kernel boot sequence. I'm not knowledgeable enough to know how this works.

Adding ro.config.tima=0 does not fix the reboot.
[Samsung Galaxy S7 Guides, News, & Discussion] AndreiLux:
He means you should change it in /system/build.prop or in the ramdisk /default.prop.

Just add ro.config.tima=0 into the default.prop and see if that fixes the reboots.
[Samsung Galaxy S7 Guides, News, & Discussion] Devries:
I tried many methods but still reboot,do you have any good suggestion?
[Samsung Galaxy S7 Guides, News, & Discussion] tamirda:
Had this problem also in tab s kernel, once i disabled it I've got reboots when using fingerprints /pin/etc..
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
Good News for us developers.

I noticed Samsung just add last_kmsg support in latest G930KKKU1APCF source.
[Samsung Galaxy S7 Guides, News, & Discussion] Tkkg1994:
Finally :)

Sent with my Nova powered SM-G901F
[Samsung Galaxy S7 Guides, News, & Discussion] Tkkg1994:
Anyone get a kernel to boot up? I tried all variants of CONFIG_TIMA_RKP and CONFIG_TIMA, also different toolchains and stock dtb.img and the dtb.img generator, the kernel didn't boot up one single time!
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
vmm.elf is not the reason of not boot.

I tried to compile pre-built vmm.elf into kernel while RKP is set to false and it booted.
[Samsung Galaxy S7 Guides, News, & Discussion] tvk1:
ro.securestorage.support=false

no reboots...
[Samsung Galaxy S7 Guides, News, & Discussion] AndreiLux:
I'm not too concerned with the reboots however did any of you manage to build any image which recognizes the SIM card and boots up the modem?
[Samsung Galaxy S7 Guides, News, & Discussion] jcadduono:
i'm not sure even samsung is taking exynos seriously

can you guys see everything wrong with this picture lol
[Samsung Galaxy S7 Guides, News, & Discussion] AndreiLux:
You're just nitpicking about trivial stuff.

The cause of the current issues is that when you're compiling a custom image this doesn't pass the EL3 image verification of some sort. Disabling RKP seems to make the basic things work but the TEE remains non-functional. Android's KeyStore relies on the TEE and the reboots are caused by a timeout in the kernel TEE drivers trying to get a response from the TZ side which of course isn't running because it saw that the kernel image isn't a valid Samsung kernel image.

The fingerprint sensor, pin lock, account management (Google, Skype, etc) also use the TEE KeyStore so that's why things like YouTube are crashing the phone because they're trying to access it. You can also crash the device by simply adding a new Google account. In a way things are working as intended as the chain of trust is broken by us flashing a custom image.

The issue lies more on the user-space side where it doesn't allow for a non-hardware backed fallback KeyStore like in previous Android versions. As far as I see it the kernel sources are completely fine and Samsung isn't in the wrong here, but to be able to get a workable daily kernel we need a workaround in the way Android treats TEE. Maybe some people will be able to do something via Xposed or maybe even backport some of the framework from the S6 but ultimately this isn't a technical issue but more of a design/security constraint caused by Google new Android 6.0 CDD requirements.

Custom kernels will run fine without issues as long as nothing tries to access the TEE. Unfortunately that's not reasonable for daily drivers making use of accounts and apps using it for authentication, so until this is somehow bypassed custom kernels seem to be a thing of the past for most users.
[Samsung Galaxy S7 Guides, News, & Discussion] tamirda:
[MENTION=4167023]AndreiLux[/MENTION] so the short story is that we can't built kernel until Samsung gives us this key , right? Do you think they will release it? Or we are lost?
[Samsung Galaxy S7 Guides, News, & Discussion] AndreiLux:
As said before, the kernel works absolutely fine as long as it doesn't access TEE. Samsung will absolutely never give anybody their signing mechanisms for us to do kernel images that work with it since it's a huge security risk.

IMHO the best possibility is for somebody to figure out a way via Xposed to change the ROM's KeyStore mechanism so it avoids using the TEE.
[Samsung Galaxy S7 Guides, News, & Discussion] tamirda:
Interesting. Is this thing only on new devices? Because s5 got 6.0.1 and my kernel works great on it.

I think one of the libs must be patched for those checks. Just don't know which one. ...

But as for now it's a temp end of custom kernels ..
[Samsung Galaxy S7 Guides, News, & Discussion] Devries:
What will happen if we directly disable TEE from kernel's defconfig?
[Samsung Galaxy S7 Guides, News, & Discussion] AndreiLux:
Android doesn't boot.
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
In fact,it will boot but fingerprint,lock screen will not work.

---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------

<3>[ 42.038368] [5: POSIX timer 0: 7102] Trustonic TEE: wait_mcp_notification: No answer after 10s

<3>[ 42.038603] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: TEE halted. Status dump:Trustonic TEE: mcp_dump_mobicore_status: flags = 0x80000401

<3>[ 42.039004] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: haltCode = 0x00000002

<3>[ 42.039213] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: haltIp = 0x07f02948

<3>[ 42.039420] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.cnt = 0x00000003

<3>[ 42.039634] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.cause = 0x00000002

<3>[ 42.039756] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.meta = 0x00000000

<3>[ 42.039815] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.thread = 0x00010001

<3>[ 42.039871] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.ip = 0x00001a84

<3>[ 42.039928] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.sp = 0x0001d280

<3>[ 42.039984] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.arch.dfsr = 0x00000a11

<3>[ 42.040039] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.arch.adfsr = 0x00000000

<3>[ 42.040096] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.arch.dfar = 0x00000000

<3>[ 42.040151] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.arch.ifsr = 0x00000205

<3>[ 42.040205] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.arch.aifsr = 0x00000000

<3>[ 42.040263] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: faultRec.arch.ifar = 0xfe500f08

<3>[ 42.040321] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: mcData.flags = 0x00000001

<3>[ 42.040375] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: mcExcep.partner = 0xffffffff

<3>[ 42.040430] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: mcExcep.peer = 0x00000009

<3>[ 42.040484] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: mcExcep.cause = 0x00000012

<3>[ 42.040541] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: mcExcep.meta = 0xfffffffe

<3>[ 42.040715] [5: POSIX timer 0: 7102] Trustonic TEE: mcp_dump_mobicore_status: mcExcep.uuid = 0xffffffffd0000000000000000000000e

<0>[ 42.042245] [5: POSIX timer 0: 7102] Kernel panic - not syncing: tbase halt

* That's the reason why kernel will random reboot.
[Samsung Galaxy S7 Guides, News, & Discussion] AndreiLux:
No it won't boot. You're showing me a log of the TEE timing out as I've said it does in previous posts.

That reboot happens here: https://github.com/AndreiLux/ref-3..../gud/gud-exynos8890/MobiCoreDriver/mcp.c#L504

You can comment it out to avoid the kernel panic but eventually the phone will hard lockup meaning the issue is not in kernel-space but in EL3.

He was asking about completely disabling the TEE driver from the kernel, where that log is coming from in the first place. The phone doesn't get past the boot logo with that disabled.
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
I knew.

But What's "completely disabling the TEE driver"?

I set CONFIG_TRUSTONIC_TEE to n and it could boot as far as I was concerned.
[Samsung Galaxy S7 Guides, News, & Discussion] AndreiLux:
Just tried it again and it works? Maybe I had some different config combination before. Hrm.

Have the current settings:

YouTube and Google account management works. Lockscreen & FP of course doesn't work and crashes the settings but I can live with that.

Let's see if it crashes or not.
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
Well,most of users cannot live with not working lock screen. ;)

I think we might could solve this problem by porting S6 or Note 5's framework to S7.

I cannot access to my PC because I am in school.

I'll try on this weekend.

---------- Post added at 01:11 PM ---------- Previous post was at 01:09 PM ----------

You will see my defconfig in my Github Repo.
[Samsung Galaxy S7 Guides, News, & Discussion] optionalmgrr.la:
I just want to make sure....

Is now the kernel of both Exynos & Snapdragons S7 and S7e signed by a private key from Samsung, and there's no way for 3rd party like CyanogenMod to build their own that can fulfill the requirements (i.e. full functionaity and no reboot) ?

Is it possible somehow to (politely) ask them to release, let's say, an intermediate key (like the web CA does, root --> intermediate CA --> actual cert for websites) so other devs can release their own kernels as well?

and, without a signed kernel, we can basically say goodbye to custom ROM/kernel, right?

thanks.
[Samsung Galaxy S7 Guides, News, & Discussion] tamirda:
Has it crashed?
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
I found a temporary solution to this problem.

Remove libbauth*.so

Lock Screen work while FP will not work,but,anyway,not random reboots anymore.
[Samsung Galaxy S7 Guides, News, & Discussion] Destroyedbeauty:
FP?
[Samsung Galaxy S7 Guides, News, & Discussion] pug1:
Fingerprint possibly
[Samsung Galaxy S7 Guides, News, & Discussion] wanam:
Can you please post the crashes logs?
[Samsung Galaxy S7 Guides, News, & Discussion] AndreiLux:
It's posted above, the TEE times out and panic()'s the kernel.

Anyway I've been running custom kernel since then, just no lock screen but it's not important to me.
[Samsung Galaxy S7 Guides, News, & Discussion] wanam:
It seems like a kernel logs, i meant the logcat when lock-screen settings crashes, i want to see if there is anything we can hook on the TUI level, maybe we can force LS/FP to work without the TEE.
[Samsung Galaxy S7 Guides, News, & Discussion] Destroyedbeauty:
I hope that will be possible.

The S7 should kickass for real with an optimized custom kernel with some battery saving features like Arch_Power, lower MIN-clocks and full GPU control and what not..
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
TLC_BAUTH: cannot connect to TZ daemon.

...

Check libbauthtzcommon.so

Random reboots disappear after remove this file but removal of this file make Fingerprint not working.

It is almost impossible to force FP to work without the TEE because it seems that all code related to fingerprint is in the Trustzone.

I can provide a factory driver that does not use TEE and Android's Fingerprint API.
[Samsung Galaxy S7 Guides, News, & Discussion] Devries:
Has anybody tried compile option ENABLE_SENSORS_FPRINT_SECURE in kernel makefile?
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
This option is enabled by default and it could not be disabled otherwise the phone will stuck at the first screen.
[Samsung Galaxy S7 Guides, News, & Discussion] optionalmgrr.la:
Do you think if we contact this guy he maybe able to help us?

https://www.google.com/search?q=mark+hong+samsung
[Samsung Galaxy S7 Guides, News, & Discussion] wanam:
Sadly disabling TUI service does not seem to help much here:

05-20 12:02:31.588 3053 3053 I TLC_BAUTH: Call FUNC ID 0x3 , 1;478

05-20 12:02:31.588 3053 3053 I tlc_communication: tlc_open() called;85

05-20 12:02:31.588 3053 3053 I tlc_communication: Opening MobiCore device;89

05-20 12:02:31.588 3053 3053 E TeeDriverClient: No such file or directory in open

05-20 12:02:31.588 3053 3053 E TeeProxyClient: *****************************

05-20 12:02:31.588 3053 3053 E TeeProxyClient: *** ERROR: connect failed with "Connection refused"(errno 111)

05-20 12:02:31.588 3053 3053 E TeeProxyClient: *** Detected in hardware/samsung_slsi/exynos8890/mobicore/ClientLib/src/proxy_client.cpp:80()

05-20 12:02:31.588 3053 3053 E TeeProxyClient: *****************************

05-20 12:02:31.588 3053 3053 E TeeCommonClient: *****************************

05-20 12:02:31.588 3053 3053 E TeeCommonClient: *** ERROR: Failed to open lower layers: Connection refused

05-20 12:02:31.588 3053 3053 E TeeCommonClient: *** Detected in hardware/samsung_slsi/exynos8890/mobicore/ClientLib/src/common_client.cpp:92()

05-20 12:02:31.588 3053 3053 E TeeCommonClient: *****************************

05-20 12:02:31.588 3053 3053 E tlc_communication: *****************************

05-20 12:02:31.588 3053 3053 E tlc_communication: *** ERROR: Opening MobiCore device is failed : 36

05-20 12:02:31.588 3053 3053 E tlc_communication: *** Detected in tlc_open/97()

05-20 12:02:31.588 3053 3053 E tlc_communication: *****************************

05-20 12:02:31.588 3053 3053 E TLC_BAUTH: *****************************

05-20 12:02:31.588 3053 3053 E TLC_BAUTH: *** ERROR: Open Trustlet Session is failed!!!

05-20 12:02:31.588 3053 3053 E TLC_BAUTH: *** Detected in BAuth_SessionOpen/531()

05-20 12:02:31.588 3053 3053 E TLC_BAUTH: *****************************
[Samsung Galaxy S7 Guides, News, & Discussion] Destroyedbeauty:
So..

Custom kernel(s) for GS7 is near-to impossible?
[Samsung Galaxy S7 Guides, News, & Discussion] wanam:
Not really, you can still use the custom kernel with a third party lock-screen (i use "Next") if you don't rely on FP.

The FP and the backup password keep triggering on some native TEE calls that keep failing, so i guess it will be the same for other LS types, unfortunately the failing check does not seem to be something i can isolate and hook at Java level.
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
In fact,you don't need a third party Lock Screen app.

Remove following files in the system to enjoy a stable kernel

* /system/lib(64)/hw/keystore.universal8890.so

* /system/lib(64)/hw/gatekeeper.universal8890.so

* /system/lib(64)/hw/fingerprint.default.so

* /system/lib(64)/libbauth*.so

* /system/bin/fingerprintd

* Fingerprint Sensor will not work after remove these files

* Lock Screen still work
[Samsung Galaxy S7 Guides, News, & Discussion] Destroyedbeauty:
[MENTION=3562083]wanam[/MENTION] [MENTION=535343]all[/MENTION] Can't you (or someone else with kernel building knowledge) release an flashable test kernel or so (in ZIP format!) for the S7, AND include a the needed lines in the updater-script that removes the files here above during the flashing process, so we can test and see if everything is working w/o any issues without the libs / binary files here above?

If something goes wrong - we can always flash stock ROM with Odin again and getting everything work from scratch..
[Samsung Galaxy S7 Guides, News, & Discussion] :
I think we're far from that point right now. I think the developers is aware what's working and not working and not anywhere near releasing a kernel right now.

The fingerprint is not working, the rest is. If some dev is gonna make a custom kernel for the community without FP, he is going to release it for the public sometime when ready. Just be patient. They just got the kernel to be stable. The building has just started.
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
Test version of My Kernel.

Remove security-related files and modify build.prop by yourself.

https://mega.nz/#!5J0A2Zyb!eV6zTTdXvT1anMUc5zyDa-sX5ytj9XK2Z4a0sHdmb6s

Run Geekbench and try to get higher score than me.

http://browser.primatelabs.com/geekbench3/6669933
[Samsung Galaxy S7 Guides, News, & Discussion] Destroyedbeauty:
What security files should be removed? And what kind of build.prop modifications is needed?

EDIT: Your kernel is for G935F, so I presume it will NOT work at G930F?
[Samsung Galaxy S7 Guides, News, & Discussion] AndreiLux:
As I said before the kernel runs fine and I never use lockscreen anyway. I have undervolting/overclocking other stuff for a few weeks now. Adding a few lines to the ramdisk to rename those files isn't all that complicated.

https://twitter.com/andreif7/status/727992745055424512

http://browser.primatelabs.com/geekbench3/6379020

But really just stay at the default clocks, it's better.
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
I guess you met the suddenly black screen problem,aren't you?

Just like me,:D.

4x2.7GHz is not stable enough.

I got that score with a ASV-8 phone.(Grade C)

What's your ASV?

New cpufreq driver seems to get frequency table from pwrctl chip and use it to override that one from DT.

Do you have any way to bypass it?
[Samsung Galaxy S7 Guides, News, & Discussion] AndreiLux:
Group 9 on the big cores. 4x2.7GHz is stable for me but it's essentially useless because power is just too high and it will throttle too fast.

What do you mean bypass it? Go over 2.7GHz? You can do that if you change the driver a bit but again it's not something you want to do.

I'm content with voltage controls right now, seems one can reduce them quite a bit again.
[Samsung Galaxy S7 Guides, News, & Discussion] :
Do you plan on releasing a custom kernel for the community or are you keeping it for yourself? I think a lot of people would appreciate a kernel, especially a permissive one. I think most people that wants are custom kernel can live without lockscreen/fp.

Btw, Wanam got the lockscreen to work, just without FP

Just curious. :)
[Samsung Galaxy S7 Guides, News, & Discussion] AndreiLux:
No. The sources are up so anybody is free to compile it but I'm not distributing anything anymore.
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
Thanks for your advice.

Do you have any ideas to solve the FP problem?

I tried to disable FPRINT_SECURE but failed.

I think there are two ways to solve this problem.

A. Use insecure fingerprint driver.

B. Modify the fingerprint driver in TZ.

BTW: OC A53 to 1.8GHz or 2GHz is safety.

All of us could get lock screen to work without FP,just follow my steps, it is quite easy.
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
Would you mind run Geekbench again and again to confirm its stability?

Even 4x2.6GHz is not stable enough.

Here is a software a Chinese friend recommended to me.

It could fully utilize the CPU.

View attachment GPUGFLOPS-0.80.apk

You can run 8-thread NEON FP test to see whether 4x2.7GHz is stable or not.

BTW: Do you have any ideas to deal with the problem shown in following screenshot.
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
Removed.
[Samsung Galaxy S7 Guides, News, & Discussion] Devries:
Haha, this software was developed by ioncannon, he is my friend :D

You can get all of his cpu/gpu-burn software here pan.baidu.com/s/1nuJY4Y1#path=/MIDtest/CPUBurn
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
FP problem already fixed.

Regards.
[Samsung Galaxy S7 Guides, News, & Discussion] tamirda:
How?
[Samsung Galaxy S7 Guides, News, & Discussion] Destroyedbeauty:
Interesting.

How did you do for making fingerprint working?
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
By prevent some 'bad' programs from being loaded to Trustzone. (TIMA,KNOX,etc.)

Check my Kernel's thread.

http://xdaforums.com/s7-edge/development/kernel-jesse-kernel-s7-edge-t3389528
[Samsung Galaxy S7 Guides, News, & Discussion] tamirda:
I don't own s7, just want to learn for next note version since this policy 90% will be inside.

Is this the only commit to solve the FP and reboots? Did you restore the deleted libs?

https://github.com/jesec/android_ke...mmit/b381fc8c7d4cc8d650aecf2e4f086b344b5abad5

Thank you
[Samsung Galaxy S7 Guides, News, & Discussion] jesec:
Changes are not in kernel.
[Samsung Galaxy S7 Guides, News, & Discussion] tamirda:
So?
[Samsung Galaxy S7 Guides, News, & Discussion] optionalmgrr.la:
Does this mean we can have real custom ROM like CM13 for Exynos S7 soon?
[Samsung Galaxy S7 Guides, News, & Discussion] Destroyedbeauty:
No.

The reason is thanks to Samsungs non-logical, unfriendly attitude toward the Open Source scene in general.

They can't even hand out proper, fully Exynos SoC Sources or Documentation so custom kernel / ROM developer(s) can build kernels and Open Source code based ROMS - based on the Exynos chipset(s).

This thread is ONLY pointing toward kernel development that is based on stock Samsung kernel sources. So no, no CMxx. Yet.

Until Samsung changes their policy, of course.
[Samsung Galaxy S7 Guides, News, & Discussion] iamnotkurtcobain:
If they improve their Good Lock App for even more AOSP look and better performance we don't need cm that badly. Better a stable TouchWiz with AOSP look than a extremely buggy cm.
[Samsung Galaxy S7 Guides, News, & Discussion] :
maybe i m wrong but i ll suggest something silly, i think the issue comes from compilation with gcc compiler not from kernel

In top makefile i think "-march=armv8-a+crc " is more appropriate for 8890 optimisation as it implies already "-mtune=" and no need for retro-compatibility but can be complementary to add like this

-march=armv8-a+crc \

-mtune=cortex-a57.cortex-a53 \

just give it a try to test
[Samsung Galaxy S7 Guides, News, & Discussion] :
I think the most needed reason for CM is when Samsung stop updating the phone or delaying them by months. Some people keep their phone for 2+ years and they either wait half a year-1 year for updates from Samsung or are not getting them at all.

If we get a somewhat stable CM build, we're sure we can use this phone for 2+ years if that is what we want.
[Samsung Galaxy S7 Guides, News, & Discussion] tnttrx:
still running i9100 [MENTION=1401799]CM13[/MENTION] :D
[Samsung Galaxy S7 Guides, News, & Discussion] iamnotkurtcobain:
I have a S7 and I still try cm on my S2 lol. It's slow as hell tbh.

Gesendet von meinem SM-G930F mit Tapatalk
[Samsung Galaxy S7 Guides, News, & Discussion] optionalmgrr.la:
this
[Samsung Galaxy S7 Guides, News, & Discussion] DaReDeViL:
Knowing that the Samsung is a company doing business to make money by selling as much devices as they can, how can they give us the complete sourcecode which will allow us continuous cm1x updates so that we do not think about buying their brand new flagships for years ?

It's sad and unacceptable from our side, but the opposite is also sad and unacceptable from their side too ;)
[Samsung Galaxy S7 Guides, News, & Discussion] :
I never said they should release anything. I totally understand why they're doing so and might be SOME of the reason they're way a head of other OEMs (Kind of, as most people have no idea what CM is). But still, S7 XDA users is still a pretty sum + all the people that use CM without knowing of XDA. So yeah, I understand Samsung.

But it's still possible to get it to work and [MENTION=3654774]Fevax[/MENTION] is already working on it. He got it to work on the S5 Exynos and hopefully he can get it to work again. At least he would get a donation from my side, as I then knew I should not trash this device in a few years.

Last point... Most OEMs is doing fine with Snapdragon and I think Samsung would lose minimal money if they released sources or used Snapdragong (with unlocked bootloader) as many people upgrade to a new phone anyway, as they rather have newer hardware than software.