yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] matssa:
I use Deuteronomy with magisk and pixelfy, great if you fixed it then :)
[OnePlus 3 & 3T Cross Device Development] stryker09:
The Alert Slider issue is due to a commit in device_common (forgot if it was oppo, probably is) that ignores key events if CMSetupWizard is not complete, so if anyone does not have CMSetupWizard in their gapps package (etc, flashing without gapps) and does not complete it, Alert Slider won't work

I cannot find the commit atm, but i have seen it floating about in one of the threads, I'll update this if i find it but reverting that commit fixes it permanently as who cares about cmsetupwizard these days, its probably obsolete now even lol
[OnePlus 3 & 3T Cross Device Development] matssa:
Ok thanks for the info, I'll take a look as well
[OnePlus 3 & 3T Cross Device Development] philidor:
Probably you are right. I removed CMSetupWizard because I have problems with it and I could not finish Google setup (restore app)

Maybe next version may have a permanent solution to it.

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=6313536]matssa[/MENTION] could you include the WiFi 40mhz mode in the next builds ?
[OnePlus 3 & 3T Cross Device Development] matssa:
I don't know since [MENTION=5091734]dianlujitao[/MENTION] doesn't want to include it, and since he has a lot of experience on this, I want to follow his judgment. You can make your build if you want to test it.
[OnePlus 3 & 3T Cross Device Development] :
Yeah experience in ROM building. No doubt. But since the hardware and software have full support, I don't see a reason not to test it in some nightlies
[OnePlus 3 & 3T Cross Device Development] matssa:
I'll think about it and try to include it when I have the time.
[OnePlus 3 & 3T Cross Device Development] stryker09:
https://github.com/CyanogenMod/andr...mmit/3202fb4dae654c52e99dbe5045bfd1f1604d854a

This is the commit! I can confirm that it works over multiple builds of my own :) 2h 45m to 2017 for me so y'all have a great last few hours of 2016! [MENTION=5091734]dianlujitao[/MENTION] - FYI
[OnePlus 3 & 3T Cross Device Development] NickMidd91:
All you need to do is see if oneplus 3 released the code from there ROM that has WiFi calling in it and just patch it in.
[OnePlus 3 & 3T Cross Device Development] matssa:
New build up ;) happy new year guys! Have fun! See you next year!
[OnePlus 3 & 3T Cross Device Development] EatBeans:
You too ;) OnePlus released finally the stable ota for the OP3 :good:
[OnePlus 3 & 3T Cross Device Development] matssa:
Nice, we should see some kernel and official blob commits then :D
[OnePlus 3 & 3T Cross Device Development] adamcooks:
Laos is cyanogen or cyanogen Inc.? I've not read either way in the countless articles that have been posted. It talks about the community effort but not really whose driving the bus.
[OnePlus 3 & 3T Cross Device Development] sumasage:
How do you remove the cm setup wizard? I hated it too when clean flash and it doesn't restore my app. Thanks.
[OnePlus 3 & 3T Cross Device Development] Gandicela:
I use OpenGapps Aroma version and I choose to remove CM account. It works for me.
[OnePlus 3 & 3T Cross Device Development] doppelhelix:
If you don't use aroma, create gapps-config.txt and put this in:

(CyanogenSetupWizard)

Put the file into the same directory as the opengapps.zip

Look here for details:

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
[OnePlus 3 & 3T Cross Device Development] sumasage:
I usually go with nano gapp package since that's what everyone seem to suggest with cm rom. I am not sure what the effect of using different gapp package. Does it hurt/break anything?
[OnePlus 3 & 3T Cross Device Development] doppelhelix:
Not at all. Many people like a small Google footprint on their device. Or have an old device with small system partition. That's why there are different gapps packages. For me, I hate wasted space on system. Every app installed to /system doesn't count into /data.

That's why I use super with gapps-config. The downside is a heavy download size of this gapps package.

Nano is just the minimal recommendation.
[OnePlus 3 & 3T Cross Device Development] Gandicela:
That's all I've been using since, Aroma Gapps. I'm essentially able to remove several CM apps including Trebucher Launcher as i prefer Pixel. As described in the Opengapps site, the Aroma package allows you to select which specific applications to install/remove (CM's included) without having to manually write a gapps-config file to customize gapps package you eventually want to flash.

The only disadvantage to Aroma is of course 1+Gb of file size to download, plus the extra time taken to select apps to either include or exclude during flash.
[OnePlus 3 & 3T Cross Device Development] hutilicious:
hi, camera doesnt work on lineage os 12-31. is there anything I can do to fix this?
[OnePlus 3 & 3T Cross Device Development] Gandicela:
http://xdaforums.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721/page145

Use the V3.
[OnePlus 3 & 3T Cross Device Development] thefraggle:
And which Framework Version?
[OnePlus 3 & 3T Cross Device Development] gmlogan:
Don't think you need framework for 14 up roms .
[OnePlus 3 & 3T Cross Device Development] Gandicela:
None; go straight install the V3 apk of the camera.
[OnePlus 3 & 3T Cross Device Development] angelmakumbe:
V2 for N ROMs, I think
[OnePlus 3 & 3T Cross Device Development] thefraggle:
V3 is working fine. Thank you
[OnePlus 3 & 3T Cross Device Development] PuCiNhOOO:
Hey [MENTION=6313536]matssa[/MENTION]

Nice work ;) your Android file HOST foder is the link posted on oficial LineageOS for op3 ? have you checked it?
[OnePlus 3 & 3T Cross Device Development] matssa:
Really? Where? :) I'm sorry guys no build today since I didn't have time, and I get repo sync issues, so I'll take a look maybe tomorrow, maybe in 2 days since I will be going home.
[OnePlus 3 & 3T Cross Device Development] PuCiNhOOO:
Yap ;) over here

http://www.cyanogenmods.org/forums/topic/oneplus-3-lineage-os-14-1-nougat-7-1-rom/

With this for main link

http://www.cyanogenmods.org/lineage-os-14-1-rom-update-devices-list-downlods/#ONEPLUS
[OnePlus 3 & 3T Cross Device Development] matssa:
Wow thanks for the info! Too many responsibilities now! ;) And I'm not a dev, only a guy that helps out ^^
[OnePlus 3 & 3T Cross Device Development] thefraggle:
How do you Pass Safetynet? The usual procedure with unsu, magisk and phh su?
[OnePlus 3 & 3T Cross Device Development] matssa:
I don't know, please test it and report, I don't use pokemon go or Android pay
[OnePlus 3 & 3T Cross Device Development] dr.wtf:
Right on top it says
[OnePlus 3 & 3T Cross Device Development] PuCiNhOOO:
The fórum is... Where are the Official builds?
[OnePlus 3 & 3T Cross Device Development] doppelhelix:
Try using super and the attached gapps-config.txt. The download size is a bit smaller and you save yourself from the procedure of choosing what you want every time you flash.

P.s.Because I use it on OxygenOS too, there are some extra options at the end.

PPS: please redownload. The first upload was messed up
[OnePlus 3 & 3T Cross Device Development] doppelhelix:
That's not a official site. Read the disclaimer at the end. He is just collecting builds and posting them on his site.

There are no official builds yet.
[OnePlus 3 & 3T Cross Device Development] miscom:
It seems to me that although there are no official builds yet, development is as active as usual. I see a lot of changes at review.lineageos.org
[OnePlus 3 & 3T Cross Device Development] matssa:
Yup, no official builds since they need the ressources. Sorry guys, no builds for now, I need to copy my VM from my other PC onto this one, etc... Might be tomorrow.
[OnePlus 3 & 3T Cross Device Development] matssa:
Ok guys, managed to make the builds, there was an issue with my kernel repo, went back to the LineageOS repo. Furthermore, I don't know if the kernel modification worked, so anyways, no harm done.

Currently, it is still building, I'll try to upload tonight, but will be hard.
[OnePlus 3 & 3T Cross Device Development] matssa:
For the git status:

android@builduntuvm:~/android/system/device/oneplus/oneplus3$ git status
HEAD detached from 52b5d7a
nothing to commit, working directory clean

For the log:

android@builduntuvm:~/android/system/device/oneplus/oneplus3$ git log -n 3
commit d2fd4573dc24dc69911c2cd9af187889d27ff99a
Author: dianlujitao <dianlujitao@gmail.com>
Date: Sat Dec 3 15:24:11 2016 +0800

op3: Stop preloading libNimsWrap.so

Change-Id: I8af0fb691a44e383d47bc70c132b7bf9cdfe83f9

commit cf697f5c25b861b71c8a0e007d39295ca25e710e
Author: dianlujitao <dianlujitao@gmail.com>
Date: Sun Dec 4 19:48:22 2016 +0800

op3: Add net_raw group to ril-daemon

* Our ril blobs need it.

Change-Id: I46503d456c9ebf6b58ce96303cc3ec7317d99179

commit 883c8991dc672f8c8d432e7fcd4b999bef133aca
Author: dianlujitao <dianlujitao@gmail.com>
Date: Sun Dec 4 13:46:17 2016 +0800

op3: Build libgnsspps.so

Change-Id: I552fd1a678e48f676e24836ccee4cbb97ad5465c

With my latest build, I have the same issue now, the dev settings won't open ;) I don't know why my first build was NOK...
[OnePlus 3 & 3T Cross Device Development] ivanich:
I asked you to show git output of vendor/oneplus and nod device/oneplus
[OnePlus 3 & 3T Cross Device Development] matssa:
Woops soz, here is the stuff you asked.

HEAD detached at 481d05a

nothing to commit, working directory clean

android@builduntuvm:~/android/system/vendor/oneplus$ git log -n 3

commit 481d05a4c8b09d3985361186104df3afd62f13f5

Author: dianlujitao <dianlujitao@gmail.com>

Date: Sun Dec 4 11:23:04 2016 +0800

op3: Update to official N blobs

* From Open Beta 8

* qti-telephony-common.jar from gemini

* Keep M camera blobs

commit d9d97712e93b9a781f260a2f4b696910ac9b123b

Merge: 13a5372 72fd3d8

Author: Ethan Chen <intervigil@gmail.com>

Date: Sun Nov 27 17:52:52 2016 -0800

Merge pull request #51 from jfeise/cm-14.1

Binary blob to enable full-disk decryption.

commit 72fd3d862ba7e0f60779709f686b307cf6d9b930

Author: J. Joe Feise <jfeise@feise.com>

Date: Mon Nov 21 08:17:18 2016 -0800

Remove unused file.
[OnePlus 3 & 3T Cross Device Development] ivanich:
Looks correct, broken dev settings confirms this :)
[OnePlus 3 & 3T Cross Device Development] matssa:
Yup :) I'm trying to merge the commit https://github.com/scotthartbti/and...d05#diff-2339e3716d18484a6a228578cff1f8beR725 that should hax the dev settings in order to use them (removes the OEM unlock feature and the screen stay on while charging feature), but I get some issues while merging:

android@builduntuvm:~/android/system/packages/apps/Settings$ git status
HEAD detached at e6ca00a
You are currently cherry-picking commit 158ed6f.
(fix conflicts and run "git cherry-pick --continue")
(use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:

modified: res/xml/development_prefs.xml

Unmerged paths:
(use "git add <file>..." to mark resolution)

both modified: src/com/android/settings/DevelopmentSettings.java

When I check the files that is both modified, I can see the <<<<< HEAD and some code afterwards, but the problem is that the coding between the headers is different from what I can see on Github (i.e. i see some extra stuff concerning Bugreport). I removed manually the correct stuff and didn't change the extra stuff.

Do you think that my process is logic? Furthermore, do I need to do the manual changes every time I will repo sync? Another way would be to sync it with my Github...

Thanks for your help :)
[OnePlus 3 & 3T Cross Device Development] ivanich:
It means that file has been changed by another commit, fix conflicts and commit change. After that you can save this commit as a patch by "git format-patch -1" and then you can apply this patch in your ROM build script like this

cd packages/apps/Settings
git am /path_to_your_patch
cd -
[OnePlus 3 & 3T Cross Device Development] ivanich:
I found a much more simple workaround for dev settings freeze

just comment out or delete from build.prop

ro.frp.pst=/dev/block/bootdevice/by-name/config
[OnePlus 3 & 3T Cross Device Development] bay91:
I've had the same issues as reported regarding the home button behaviour, as I posted on page 1. Logs? Well I've flashed back to 14.1 official for now
[OnePlus 3 & 3T Cross Device Development] matssa:
Ah didn't see, but this means that the issue is only on the experimental build, not on the official builds, which meeeans that this issue came from N blobs, just as I feared. I don't have any solution, might need to wait until official OOS for N gets out, or maybe check the blobs in Beta 9. Other idea is that it can come from kernel, which will be delivered before the end of the year i hope.
[OnePlus 3 & 3T Cross Device Development] Jole7:
What about previous firmware 3.2.8? I have zero issues with it
[OnePlus 3 & 3T Cross Device Development] matssa:
Ah you are talking about the Old M firmware or the firmware from OOS beta? The new firmware should be included in the zip that I share, so you may need to flash the old firmware after flashing the ROM to be sure.

So the home button bug isn't present on your system?
[OnePlus 3 & 3T Cross Device Development] Jole7:
Yes i mean about the M firmware no such problems here
[OnePlus 3 & 3T Cross Device Development] matssa:
Ok, we may need to test it with the new OOS beta 9 firmware. I understand that it works with M, but we may break something with the old firmware, especially with the new blobs. You can stay with the old firmware if it works, but I'm still a little bit surprised ^^ anyways, thanks for the info!
[OnePlus 3 & 3T Cross Device Development] Jole7:
No problem great rom
[OnePlus 3 & 3T Cross Device Development] Pumpino:
Thanks for your work. Can I ask why CM is not integrating the Nougat blobs like you are? Wouldn't this assist with the fingerprint scanner issues and with improving camera quality?
[OnePlus 3 & 3T Cross Device Development] Tikerz:
I'm guessing because Nougat hasn't been officially released by OnePlus.
[OnePlus 3 & 3T Cross Device Development] matssa:
Since OOS Nougat is still in beta testing, I think that [MENTION=5091734]dianlujitao[/MENTION] is waiting until we have the official blobs. Furthermore, when the kernel is released, we will have some bugs that will be fixed, and a better battery life I hope.

Furthermore, there may be some bugs that are being fixed, but I don't see much activity... Best guess is to wait and see how it goes, I don't know if Beta 9 brought some stuff for us, I don't have enough time nor knowledge ;)
[OnePlus 3 & 3T Cross Device Development] ivanich:
Actually there is no activity at all, just look how it goes with xiaomi_gemini for example, bruno realy doing his work. And we stuck because op3 have no active maintainer.

Отправлено с моего ONEPLUS A3000 через Tapatalk
[OnePlus 3 & 3T Cross Device Development] matssa:
True, there isn't any activity, at least in public. I thought the active maintainer was [MENTION=5091734]dianlujitao[/MENTION]? There was Steve that was helping out since he has a 1+3 special edition, but since he got canned, there isn't any stuff going around... I hope everything will be back on track when LineageOS get's out (new ROM from Steve apparently...).

What is so strange is that the 1+3 is a great phone, with a lot of dev possibilities with the extra information that is given by OnePlus, kinda like a dev phone without any dev working on it or with it ^^' Or maybe not for CM, maybe some other custom ROMs are working on it...
[OnePlus 3 & 3T Cross Device Development] chazey2:
Ok few days in and dirty flashed up to your latest build.

Background:

Beta 9 Firmware and Modem

Boeffla Beta 6 Kernel

Super SU 2.78-SR5

Apex Pro launcher

Phone mainly used for business use lots emails, calls and txt

Approximately hour and half google maps navigation daily.

Bit of music listening and browsing.

Phone spends up to 10 hours daily in workplace with no radio/data signal- not on Airplane mode as need WiFi for email.

No games installed or social apps.

Battery for me very good under the above conditions all phone operations and UI slick, swift and smooth with no glitches.

Apart from Dev Options glitch I haven't noticed any other problems in my day to day use. (I can't find the entry in build.prop quoted to delete to fix)??

I have my long press home set to 'search' no issues.

FP works for me every time first time!
[OnePlus 3 & 3T Cross Device Development] jonahmt21:
Including Oos 4 blobs?
[OnePlus 3 & 3T Cross Device Development] matssa:
No, [MENTION=5091734]dianlujitao[/MENTION] didn't update his commits or GitHub.
[OnePlus 3 & 3T Cross Device Development] matssa:
Hey all, updated first post, new build is uploading. I'm making a second VM Machine in order to be able to upload faster, but build will take longer.

If someone knows how to make a changelog with a script or something for the first post, please contact me :)
[OnePlus 3 & 3T Cross Device Development] hp13:
Great!! Now only wished if OnePlus released their camera sources.
[OnePlus 3 & 3T Cross Device Development] matssa:
I wish they could release the kernel so that [MENTION=5091734]dianlujitao[/MENTION] can work on it and bring the kernel changes and updated blobs to our ROM :)
[OnePlus 3 & 3T Cross Device Development] miscom:
[MENTION=6313536]matssa[/MENTION]

In your roomservice file I see that you are now using the LineageOS repo. Have all the changes been committed?

Never mind. I see that you are repopicking...
[OnePlus 3 & 3T Cross Device Development] matssa:
Hehe no problem :) I think that [MENTION=5091734]dianlujitao[/MENTION] is waiting to have all the blobs sorted out from the official OOS Nougat build with the kernel before merging that stuff. Am I right [MENTION=5091734]dianlujitao[/MENTION]?
[OnePlus 3 & 3T Cross Device Development] S4turno:
Lineage is the continuation of the open source project (CyanogenMod). Cyanogen Inc has nothing to do with Lineage.
[OnePlus 3 & 3T Cross Device Development] Stefano187:
Is it possible to use F2FS in data partition with latest lineage update? I mean without any custom kernel

Thanks in advance for the reply

Best regards

Stefano
[OnePlus 3 & 3T Cross Device Development] ivanich:
[MENTION=6313536]matssa[/MENTION]

Are you sure about this?

I have no single issue with Snap camera.
[OnePlus 3 & 3T Cross Device Development] matssa:
True, good point, just tested it and it works now. It didn't before on previous builds, snap stuff may have changed. I'll change the first post, thanks for the heads up! :)
[OnePlus 3 & 3T Cross Device Development] atapigal:
Hi,

I just installed the January 5th version and have had the dm-verity problem. It is the first time that it happens to me. I've done system wipe, data, cache and dalvik, plus factory reset. What have I done wrong?

Thanks
[OnePlus 3 & 3T Cross Device Development] philidor:
Nothing wrong. Have you beta 8+ or stable N firmware installed? This error message is an advice that there are some boot/system changes on your phone (if you use a custom ROM you have made changes!) New firmware made a check and this is the result. But it's not a problem. Leave it as is it.

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[OnePlus 3 & 3T Cross Device Development] atapigal:
Hi,

Yes, I have installed the firmware version of open beta 9. Do you recommend installing firmware version 3.2.8?

Thanks
[OnePlus 3 & 3T Cross Device Development] yarpiin:
im using this one its from ak kernel

https://github.com/yarpiin/Yarpiin-Kernel-OP3-OxygenOs/blob/oneplus3/6.0.1/changelog.sh
[OnePlus 3 & 3T Cross Device Development] philidor:
I tried official N firmware without problem. Only this dm-verity message.

In OP you can read "The ROM that I propose is an experimental build using the official LineageOS 14.1 commits with some extra stuff that are not yet merged for testing. Builds since 2017 are using the OOS Beta 9 blobs with the GPS fix, the echo fix...." so I'm pretty sure you are safe with your firmware

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[OnePlus 3 & 3T Cross Device Development] matssa:
You can remove the DM verity check. You need to flash stock recovery, the flash OOS 4, then flash TWRP, wipe everything, change /data to ext4 if you want systemless root, then flash ROM and voila. There are some threads opened to flash OOS4 and remove DM check.
[OnePlus 3 & 3T Cross Device Development] SamuelBegui:
I'm sorry that this is a little off topic, but are you saying there is a way to disable DM verity checks on OOS4 thus allowing you to bypass safetynet checks with systemless root? Would this work on CB10 as well? Again, apolgies for the off topic discussion. I'm confused because to my understand you need a custom kernel which has dm-verity checks disabled in order for you to bypass safetynet with systemless root. :confused:
[OnePlus 3 & 3T Cross Device Development] philidor:
But even if DM verity is present, it's correct to assert that it don't cause problems?

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[OnePlus 3 & 3T Cross Device Development] ritchiedrama:
I think someone should help matssa add substratum to this ROM as it's the only thing missing :P I'd rather have less builds but added themeing. I mean most of the bugs well.. don't seem to be there anymore, has anyone noticed anything major (or minor for that matter)?
[OnePlus 3 & 3T Cross Device Development] akssmax:
I've made a Video for Installation

I hope you guys will benifit from this.

https://www.youtube.com/watch?v=pj4t1VzcuBs

Just flash Lineage Os instead CM Build.!

Give me Some Feedback!
[OnePlus 3 & 3T Cross Device Development] [deXter]:
Not OP, but what he provided is to pass, and therefore get rid of the red dm-verity warning message on bootup - it doesn't actually remove the check itself.

Also, you cannot pass SafetyNet while you've got root - you'd have to use something like suhide (which no longer works) or Magisk Hide (supposed to work but doesn't work for me) or Rootswitch to disable root (no longer works).
[OnePlus 3 & 3T Cross Device Development] matssa:
As he said ;) and yeah the game of passing safteynet check is a cat and mouse game... When the dev finds a way to bypass, Google patches it. At the end, we won't be able to have Android pay with root, thats it, final ^^
[OnePlus 3 & 3T Cross Device Development] matssa:
Thanks, did you need to modify stuff in there? Furthermore, do you launch it from Android/system directly? I'll test it out when I can get the mirroring work, my work PC is out of service...
[OnePlus 3 & 3T Cross Device Development] yarpiin:
dont think that you need to mod anything, you launch it from your work folder on pc (where your projet is ) prefably in root same fder where .git folder is it picks commits from .git folder and list them as .txt file with date
[OnePlus 3 & 3T Cross Device Development] matssa:
Thanks for the heads up, that's what I was thinking when seeing the file :) I'll test it out today ;)
[OnePlus 3 & 3T Cross Device Development] emontes:
Magisk Hide has been working for me since day 1. This is the order I install :

Recovery

Rom update (or install)

UnSU

Reboot recovery

Magisk

Phh superuser Magisk

Reboot system

Install Magisk manager

Install phh superuser app

Try that and let me know if it works.
[OnePlus 3 & 3T Cross Device Development] piats:
That works only with ext4 filesystem.

With f2fs there's no root.
[OnePlus 3 & 3T Cross Device Development] emontes:
Oh I gave up on f2fs long time ago.
[OnePlus 3 & 3T Cross Device Development] piats:
But without magisk phh's su works fine.
[OnePlus 3 & 3T Cross Device Development] ZiggyStrdst:
Hey guys. Just a quick question. Does anybody have an idea when nougat sources will be released?
[OnePlus 3 & 3T Cross Device Development] gruntyoldbag:
Todays build is up:

https://www.androidfilehost.com/?fid=457095661767127996
[OnePlus 3 & 3T Cross Device Development] ivanich:
[MENTION=6313536]matssa[/MENTION]

https://github.com/ivanich/proprietary_vendor_oneplus/commits/cm-14.1

https://github.com/ivanich/android_device_oneplus_oneplus3/commits/cm-14.1

New blobs from OxygenOS 4.0(except camera, of course), build libril from source instead of blob from oneplus, updated gps config from stock etc..