[ROM][OMS7][Experimental]LineageOS 14.1 with extra open commits

matssa · Mar 6, 2017

Code:

#include <std_disclaimer.h>
/*
 * Your warranty is now void.
 *
 * We are not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you.
 *
 */

This thread is no longer supported or updated! You can maybe still find new builds on my AFH, but no guarantees! I will let the original first post only for information.

chazey2 · Dec 13, 2016 at 7:04 PM

Thanks loved yesterday's build downloading.

Giocarro · Dec 13, 2016 at 7:08 PM

Thanks mate, downloading now!

matssa · Dec 13, 2016 at 7:55 PM

chazey2 said:
Thanks loved yesterday's build downloading.

Giocarro said:
Thanks mate, downloading now!

Feel free to give me your feedback!

titan1655 · Feb 13, 2015 22 0 0

currently, I'm running CM13 on my OP3, want to update to CM14, but I can't find any issue log. What are the current knows issues? Thanks

Jole7 · Dec 13, 2016 at 9:14 PM

Good work bud rom is awesome

matssa · Dec 13, 2016 at 9:19 PM

titan1655 said:
currently, I'm running CM13 on my OP3, want to update to CM14, but I can't find any issue log. What are the current knows issues? Thanks

I didn't out any issue log since the build is experimental. For now, the issues are the same as the official nighties without the echo problem.

An issue that can be present concerns the volume, it goes up or down in some apps or when you change the audio of the notifications in some apps, but I didn't experience it yet.

Other than that, there was the dev option that was freezing, but it is apparently fixed, don't know if it was a oneplus3 issue or if it was multi device.

That is about it on my end, didn't take a chance to look at the logs yet. Pleas be aware that this is an experimental build, it has some fixes that are not yet merged in the official CM build, for example the echo and GPS fix.

ivanich · Dec 13, 2016

@matssa FYI you can now use cm vendor_nfc repos as they have merged caf code.
So Developer options freeze is fixed or you just messed up with blobs

?

bay91 · Dec 13, 2016 at 11:05 PM

Gave this a go, but for me after flashing there were some strange things with the home key not responding that i hadn't had in previous builds. For me the 13th nightly seemed a bit more ineffective than previous so I'm back on the official 12th for now, but will keep an eye on this thread with interest. Thanks for contributing!

SamuelBegui · Dec 14, 2016 at 3:32 AM

ivanich said:
@matssa FYI you can now use cm vendor_nfc repos as they have merged caf code.
So Developer options freeze is fixed or you just messed up with blobs ?

A tad curious about you mentioning NFC, I noticed there are some issues with NFC on Nougat builds in general and Android Pay, is that something that may have been fixed with the merged caf code?

matssa · Dec 14, 2016 at 5:34 AM

ivanich said:
@matssa FYI you can now use cm vendor_nfc repos as they have merged caf code.
So Developer options freeze is fixed or you just messed up with blobs ?

Haha it has been fixed in my build

it was already ok before it seems, I saw that @dianlujitao didn't ship something that was needed.

MisterCoolBeans said:
A tad curious about you mentioning NFC, I noticed there are some issues with NFC on Nougat builds in general and Android Pay, is that something that may have been fixed with the merged caf code?

The issue was heating and crashing of the NfC with the N blobs, but it has been fixed by merging the new version. I didn't test Android Pay because I don't have it in my country.

SamuelBegui · Dec 14, 2016

matssa said:
Haha it has been fixed in my build it was already ok before it seems, I saw that @dianlujitao didn't ship something that was needed.

The issue was heating and crashing of the NfC with the N blobs, but it has been fixed by merging the new version. I didn't test Android Pay because I don't have it in my country.

I'm willing to give it a test! :good: I'll download your build and try it.

matssa · Dec 14, 2016 at 6:43 AM

ivanich said:
@matssa FYI you can now use cm vendor_nfc repos as they have merged caf code.
So Developer options freeze is fixed or you just messed up with blobs ?

Just checked the repo to be sure before changing

thanks for the heads up!

Giocarro · Dec 14, 2016 at 7:25 AM

I'm facing some little issue that become showstopper as they break my daily usage:
1) HOME button long-press to turn OFF the display is not working consistently; most times I have to press it twice to trigger the action;
2) BACK button long-press is not customizable?!? I want it to trigger MENU action, but the option is not present;
3) there's no way to disable capacitive keys while gaming; not a deal breaker for most people I know, but my son yesterday went as far as crying because of false touches on capacitive keys during his brief gaming time.

Well, I guess I'm writing this to show appreciation for Matssa work and to ask whether you guys see any solution to these little but important glitches.

bay91 · Dec 14, 2016 at 8:13 AM

Sounds exactly the same issues I was facing meaning I can't use as a driver for the moment

matssa · Dec 14, 2016 at 8:13 AM

New nightly on AFH, first post was updated.

Giocarro said:
I'm facing some little issue that become showstopper as they break my daily usage:
1) HOME button long-press to turn OFF the display is not working consistently; most times I have to press it twice to trigger the action;
2) BACK button long-press is not customizable?!? I want it to trigger MENU action, but the option is not present;
3) there's no way to disable capacitive keys while gaming; not a deal breaker for most people I know, but my son yesterday went as far as crying because of false touches on capacitive keys during his brief gaming time.

Well, I guess I'm writing this to show appreciation for Matssa work and to ask whether you guys see any solution to these little but important glitches.

Mmmh got any logs?
For the Home button, I have the same issue, I find some fpc hall errors. @dianlujitao, you can find a log here. Best bet is that we need to wait for the updated hall and blobs from the official OOS N ROM.
For the Back button, apparently it isn't customizable yet, I suppose it is the same issue in the official nightly. If you want to trigger the menu, you can use the recent apps button.
For the disable capacitive keys, this option was never in CM before, I don't think it will appear one day. Did you try with the on-screen navigation bar? I think this disables the capa buttons and they should dissapear while gaming (not sure about that last point). It may be possible to do something like that, but I think in an Xposed module, which is still not possible for Android N :/

matssa · Dec 14, 2016 at 8:14 AM

bay91 said:
Sounds exactly the same issues I was facing meaning I can't use as a driver for the moment

What issues do you have? Do you have the same issues with the official nightly without the extra blobs? If so, can you please give us some logs?

ivanich · Dec 14, 2016 at 8:33 AM

matssa said:
Haha it has been fixed in my build it was already ok before it seems, I saw that @dianlujitao didn't ship something that was needed.

If "Developer settings" works in your build then you using old blobs.

matssa · Dec 14, 2016

ivanich said:
If "Developer settings" works in your build then you using old blobs.

How can it be possible??? Why, WHYYYY??? WHYYYYYYYYYY??

Where do you think I may have gone wrong? In the building process? I know the commits have been taking into account since the GPS is working, it wasn't on the CM official.

EDIT///
Furthermore, when checking github, a "hax" was found by Scott Hart by removing the OEM unlock and another stuff, and it was made in android_packages_apps_Settings, which isn't touched by the commit from @dianlujitao, correct? So if my guess is correct, we should have the same issue on CM official and unofficial, even with the new blobs, what I saw from the post is that @dianlujitao didn't ship lksecapp in his build: "Nice catch, maybe OEM unlock, as I didn't ship lksecapp in my experimental build".

If you use your own experimental build, do you have the same issue?

ivanich · Dec 14, 2016

matssa said:
How can it be possible??? Why, WHYYYY??? WHYYYYYYYYYY?? Where do you think I may have gone wrong? In the building process? I know the commits have been taking into account since the GPS is working, it wasn't on the CM official.

cd to your BUILD_DIR/vendor/oneplus
and show output of

Code:

git status

and

Code:

git log -n 3

Official builds doesn't have this issue because using old blobs.
I have issue with Dev options only with new blobs.

[ROM][OMS7][Experimental]LineageOS 14.1 with extra open commits

What type of builds for the futur?

Stock LineageOS with only OMS

Stock + open commits like today

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member