yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] stryker09:
[MENTION=6313536]matssa[/MENTION] I believe the issue isn't with OMS, rather with the individual themes itself or just some process the user needs to follow... So don't worry about it mate :) it's all good from what I see :good:
[OnePlus 3 & 3T Cross Device Development] matssa:
Ok thanks for the info :)

Ok guys, I turned off my home computer cause I thought it was finally ok, and no means to turn it on, so I'll only be able to fix this tonight and upload it if I can. I should be able to copy the VM on my work machin as well so I'll be able to fix it easier next time, until the next make clobber...
[OnePlus 3 & 3T Cross Device Development] Gandicela:
[MENTION=6313536]matssa[/MENTION] have a break, Mate, give it sometime and everything's gonna be far better and easy.
[OnePlus 3 & 3T Cross Device Development] silentvisitor:
Are you on Telegram?
[OnePlus 3 & 3T Cross Device Development] matssa:
Nope, don't like that app, why?
[OnePlus 3 & 3T Cross Device Development] silentvisitor:
Never mind ;)
[OnePlus 3 & 3T Cross Device Development] chazey2:
Just thought I'd inform this morning decided to do complete clean (wipe everything including internal & format data) and re install via USB OTG

16/12 V2

All perfectly working as before including Dev Options, Many thanks.
[OnePlus 3 & 3T Cross Device Development] gptwarrior:
Will be trying this later sounds good and your work is much appreciated matssa. Does this include camera blobs from nougat beta OOS?
[OnePlus 3 & 3T Cross Device Development] matssa:
From what I see and understand, it doesn't have the latest camera blobs. If it has, then perfect, but please be aware that not everything is in the blobs, you need to correct post-processing, which is still missing (that is why OnePlus might release their post-processing in a blob that can be used by custom ROMs). If you want to know, the camera quality isn't stock, just like on all custom ROMs.

New build up guys, nothing added since last build.
[OnePlus 3 & 3T Cross Device Development] matssa:
I didn't include substratum in the ROM, gonna make a poll to see if it is necessary, but I want to keep this build as clean as possible.
[OnePlus 3 & 3T Cross Device Development] RevTheory:
Stupid question.

this doesnt have echo and stuff like that
[OnePlus 3 & 3T Cross Device Development] solokiller11:
[MENTION=6313536]matssa[/MENTION] after i flashed your build and it booted it says "android is starting" on the home screen with loading bar... any way around it?
[OnePlus 3 & 3T Cross Device Development] matssa:
I don't understand ^^' is it the optimization screen? if so, it is normal, wait for it to finish and it should boot up. If not, then it means it's in a boot loop. Best guess is the clear cache and test it again.
[OnePlus 3 & 3T Cross Device Development] AvivEliyahu:
Heard there's an echo issue on cm Roms (fixable with some zip to flash) . Does it appear here as well?
[OnePlus 3 & 3T Cross Device Development] silentvisitor:
Shouldn't as he's using OB9 blobs.
[OnePlus 3 & 3T Cross Device Development] siankatabg:
The open commits doesn't include the cam HAL from N because it doesn't work. In one discussion they said that we most probably need the kernel changes that should be released with the official N, so we will see this when they release the source code for N.

OnePlus will most probably release the blob that will work only with their cam app, because the stock picture processing is triggered from it(and work only on it). If you install snap cam on stock rom, you will get the same result as on any custom rom.

I just wanted to say this, because many hopes for the "magical" blobs release that will make any app to get post processing like on the stock cam might be ruined. Most probably with this blobs we will be forced to use special app from OP and any other app will behave in the same way as now :) (I'm good with this, I like the stock app)
[OnePlus 3 & 3T Cross Device Development] ephumuris:
This seems the best option for a custom ROM so far but don't think I've ever had a phone where the camera had been so locked down. It's a shame and a bit of a deal breaker for me so that's why I'm sticking with OB9 as much as I want to try other ROMs.
[OnePlus 3 & 3T Cross Device Development] Jole7:
Guys check out this post.....

http://xdaforums.com/showpost.php?p=70131855&postcount=128
[OnePlus 3 & 3T Cross Device Development] solokiller11:
After I finished setting up the phone the home screen appears with a loading bar and it says "Android is starting" and it stuck on it
[OnePlus 3 & 3T Cross Device Development] matssa:
Strange, did it move? Did it ever boot? How did you flash the ROM? What did you have before?
[OnePlus 3 & 3T Cross Device Development] goldfinger01:
Hi, the is no echo call problems because of N blobs right? in future is it possible to do dirty flash to go to official CM14.1?
[OnePlus 3 & 3T Cross Device Development] jclendineng:
Literally 6 posts up, and correct. Yes dirty flash is fine I've done it. Clean flash if you have issues.
[OnePlus 3 & 3T Cross Device Development] solokiller11:
I had nyyu.tk cm14.1 from two weeks ago and I did a clean flash, this problem happened after the phone booted and after the setup wizard
[OnePlus 3 & 3T Cross Device Development] matssa:
Nah don't need a break, I want to have a final stable build since I don't have any since a couple of days.
[OnePlus 3 & 3T Cross Device Development] PuCiNhOOO:
Have you rooted the ROM?

If yes, has masquerade ask for root permitions?
[OnePlus 3 & 3T Cross Device Development] nicesoni_ash:
You have this commit?

https://github.com/ashoksoni/androi...mmit/35838c9f1ff33f2e86bde497c92b1d71ca6c03b4

Sent from my "1+2" powered by Unofficial RR 7.x.x

Compiled by myself
[OnePlus 3 & 3T Cross Device Development] matssa:
It seems like there must be a patch difference, need to check on review.lineageos since the package clearly describes op3 with op3t, while mine only keeps op3... Mmmh gonna check :) thanks for the heads up!
[OnePlus 3 & 3T Cross Device Development] matssa:
Ok yeah there is a missing info in the commit on review: https://review.lineageos.org/#/c/158508/9/BoardConfig.mk

op3t stuff is missing, but then again, it can be a copy/paste of the precedent commit... Anyways, gonna test it now :)
[OnePlus 3 & 3T Cross Device Development] matssa:
Man still having the same issue... Did you manually add BOARD_TRUSTZONE_PARTITION_SIZE := 2048? It doesn't have it in https://review.lineageos.org/#/c/158452/4

I see you didn't add https://review.lineageos.org/#/c/158508/ , normal?

Can it be a TWRP issue?
[OnePlus 3 & 3T Cross Device Development] Gandicela:
I know, Mate, but perfection takes time. (I'm out of "thanks" for the day. )
[OnePlus 3 & 3T Cross Device Development] matssa:
Hehe true :) At least, I found out that https://review.lineageos.org/#/c/158454/ is needed in order to calculate the TZ value, so it may fix it :) I'm running another build to see if it works :)
[OnePlus 3 & 3T Cross Device Development] Gandicela:
We'll see how it goes.
[OnePlus 3 & 3T Cross Device Development] nicesoni_ash:
You need this commit too I guess. https://github.com/apascual89/andro...mmit/cb7c9d03cb1cf8358b46047bdf36ea1a8fcf9071

Unified actually messed up too much stuff. Sometimes it's a RIL issue, sometimes it's a camera related. :(
[OnePlus 3 & 3T Cross Device Development] matssa:
Yeah I included it as well, gonna test it on my phone before uploading ^^
[OnePlus 3 & 3T Cross Device Development] matssa:
FINALLY! It flashes and boots up :) Gonna upload it now :)
[OnePlus 3 & 3T Cross Device Development] nanodan:
I've noticed you've created a new folder on AFH for OOS4.0.2; your builds ship with the firmware in the package, correct?
[OnePlus 3 & 3T Cross Device Development] matssa:
Yup, framework appears to be there, however not sure about the radio, but this can be because of the unified builds of OP3 and OP3T since the radios are different.
[OnePlus 3 & 3T Cross Device Development] nanodan:
So we should download a 4.0.2 firmware package and flash it after the ROM just to be safe?
[OnePlus 3 & 3T Cross Device Development] matssa:
You can, but not mandatory ;)
[OnePlus 3 & 3T Cross Device Development] nanodan:
Cool beans. Looking forward to the upload finishing since I've messed up my contacts app and need to reflash :)
[OnePlus 3 & 3T Cross Device Development] matssa:
I'm at 12% ;) I should soon get the fiber, with a better download and a much better upload, but it's a OnePlus soon...
[OnePlus 3 & 3T Cross Device Development] nanodan:
If you need help with bandwith, I have a dedicated build system; I could copy your manifests, build the same thing, and upload it probably a bit quicker than you can, if time is an issue.

With this route though I'm only worried about keeping up with all the open commits you pick. Just an option :)
[OnePlus 3 & 3T Cross Device Development] matssa:
Thanks for the proposal, but since not everything is on the repos, it can be quite hard :/ Furthermore, I have a big script that makes everything automatic (pull new merges between my repos and upstream, push repo, repopick, blablabla...), so it will kinda trickyto use a dedicated build unless you can have git access with a allocated space for the scripts.

However, you can always make your own using your build and share them in a new thread ;) Depends of what you want to do :)

For the bandwith, the only issue is at home. At work, I upload it in 15mins ^^ So just need to copy my VM on my work PC and build there, which is already what I do when there isn't any new vendor files or no clobber to do.
[OnePlus 3 & 3T Cross Device Development] nanodan:
Very fair; I figured as much. I used to swap between my builds and yours rather frequently. I don't play with cherry-picking unless there's an open commit with clear benefits, and now that I'm sold on OMS, it's a lot of work to catch my repo up to a point where my builds will be compatible. That said, I'll wait for your upload.

I haven't looked yet, but has Lineage been brought up to 7.1.2?
[OnePlus 3 & 3T Cross Device Development] matssa:
I didn't find anything, but didn't look that well.
[OnePlus 3 & 3T Cross Device Development] matssa:
Latest build is up guys, everything should be stable now :) Some testing needed though for those who can use VoLTE and Wifi calling.
[OnePlus 3 & 3T Cross Device Development] davemuir:
Got a few camera problems now hmmm.

Can't test VoLTE but everything else is perfect.
[OnePlus 3 & 3T Cross Device Development] nicesoni_ash:
Not good in shell scripting. Would you help me to mk some scripts for pushing pulling to the repos. Thanks.

Sent from my "1+2" powered by Unofficial RR 7.x.x

Compiled by myself
[OnePlus 3 & 3T Cross Device Development] hasdroid:
Hey... Thanks for your work..

I have this error while trying to upgrade from 30/1 to todays build
[OnePlus 3 & 3T Cross Device Development] matssa:
What kind of camera issues?
[OnePlus 3 & 3T Cross Device Development] matssa:
Strange, I didn't have this issue... Do you have a op3 or op3t? What you can try is flash an older build and flash the new one, maybe the 30 build doesn't work correctly?

Do you have the correct TWRP version?
[OnePlus 3 & 3T Cross Device Development] matssa:
Yeah sure we can continue on PM? ;)
[OnePlus 3 & 3T Cross Device Development] hasdroid:
All was good before this..

Yeah I have a correct version of TWRP as it worked with all roms before.. (the one from official post that support f2fs)
[OnePlus 3 & 3T Cross Device Development] davemuir:
Something has broken siankatabg's camera port, it was working beautifully in recent builds.
[OnePlus 3 & 3T Cross Device Development] nanodan:
Yeah, it doesn't open anymore.

Also, Titanium Backup is stuck at "Searching application data..."
[OnePlus 3 & 3T Cross Device Development] PuCiNhOOO:
Maybe some Hal changes. I think that in lineage they have blocked only snap cam to use HAL 1 and all the other camera apps to use HAL 3.

That may cause issues with OOS camera port
[OnePlus 3 & 3T Cross Device Development] siankatabg:
Come on guys, go to the thread and read the latest 10 comment, you will know what is going on :)
[OnePlus 3 & 3T Cross Device Development] matssa:
Yes normal since HAL 3 is being used for all apps except Snap. No way I have to counter it isnce it is using lastest N camera commit. What he can do however is try to see if there is a way to add his app into the HAL1 section or disable HAL3 with a zip.
[OnePlus 3 & 3T Cross Device Development] davemuir:
Ahhh that's a pain in the balls, isn't it? :(
[OnePlus 3 & 3T Cross Device Development] matssa:
Really strange... You on F2FS?
[OnePlus 3 & 3T Cross Device Development] hasdroid:
Yeah
[OnePlus 3 & 3T Cross Device Development] matssa:
Is it a clean flash or dirty flash? I can't figure out from where the issue is coming from... Did you wipe data when flashing? If not, can you please try?

Are you using mutliboot? Something else than stock, I dunno, something? ^^

If that doesn't work, maybe flashing OOS 4.0.2 and coming back to CM may do the trick?

[MENTION=4329165]ivanich[/MENTION], do you have any ideas what could be the issue?
[OnePlus 3 & 3T Cross Device Development] matssa:
Yup it is... The best solution for us is to hope for a fix that doesn't need tamper with the coding. If it is necessary, then if a commit fixing it is made, I'll pick it if I can.

Another solution would to wait for the blobs from OnePlus...
[OnePlus 3 & 3T Cross Device Development] davemuir:
:laugh:
[OnePlus 3 & 3T Cross Device Development] hasdroid:
Thank you for trying to help... But I tried every thing without luck... Anyways I'm on official nightly for now.. I'll wait and take a rest without flashing for couple days :p
[OnePlus 3 & 3T Cross Device Development] matssa:
Sorry mate, let's hope the next official build works with the commits. I'm still in the dark on why your trustzone is different taking into account that you own an op3, you are on F2FS (shouldn't influence), you use the latest TWRP from dianlujitao, you were on my unofficial build of 2017-01-30 (like me). What may be the difference is that I cleaned flashed OOS before switching to LAOS in order to remove the DM verity check.

[MENTION=5091734]dianlujitao[/MENTION] or [MENTION=4329165]ivanich[/MENTION], I can't seem to find the issue of the trustzone bug. What are your opinions?
[OnePlus 3 & 3T Cross Device Development] exppanda:
The new social media app houseparty doesn't work with this or any other lineage build. It seems like a camera issue. Like you have stated earlier could this be because of using hal3? If so is there any way to force it to use hal1?
[OnePlus 3 & 3T Cross Device Development] ivanich:
There is 2 commits for trustzone, one for op3 repo and another for oppo common repo, are you merged both of them?
[OnePlus 3 & 3T Cross Device Development] matssa:
Yup I'm using it as well. Since it got merged with the TrustZone, I'll test it out with the enable op3t repopick.
[OnePlus 3 & 3T Cross Device Development] kalapapa:
[MENTION=6313536]matssa[/MENTION] [MENTION=5341794]hasdroid[/MENTION]

I too faced the trustzone issue. I think it was because of open beta 11 firmware has a newer firmware trustzone. I'm assuming you flashed open beta 11 which is why you faced this error. I fixed it by flashing earlier build of Los and then flashing latest build on top
[OnePlus 3 & 3T Cross Device Development] matssa:
Thanks for your help, this is what I suggested before, flashing an older version of LAOS in order to have the correct firmware in there. If it worked for you, perfect :)
[OnePlus 3 & 3T Cross Device Development] kalapapa:
I tested wifi calling and it worked just like before

However, the problem I've faced in previous builds and in this build is that I have to go into the phone settings every time I reboot my phone or turn on airplane mode to toggle the switch for wifi calling or else it won't work. I wasn't able to test if it's any more reliable, but it seems fine reliability wise.

Thank you for working so hard on your builds and I hope you can do something about this. I did mention this in the official LOS thread but I didn't get a response
[OnePlus 3 & 3T Cross Device Development] matssa:
Ok thanks for the heads up, I'll add it on the first post. I can't do much on my side, if you said it on the official thread by @ dianlujitao, that's good for me.
[OnePlus 3 & 3T Cross Device Development] xantic21:
I follow this thread carefully and I have read that some people have camera issues with the latest build. I also have these issues. I can't use any camera app, either the app crashes or can't connect to the camera. Any solution?
[OnePlus 3 & 3T Cross Device Development] vrda08:
The problem is with last los builds, you can't use any custom kernel otherwise camera will not work.

With stock build and stock kernel camera working good.
[OnePlus 3 & 3T Cross Device Development] NoobMonkey:
I've never used custom kernels on 3 and still had problems with the camera, so it isn't that black & white. Or does matssa uses custom kernels on his builds?

---------- Post added at 11:24 AM ---------- Previous post was at 10:50 AM ----------

Not sure if this is the right place to ask this, but is it some possible to change screen unlock sound?
[OnePlus 3 & 3T Cross Device Development] Nezorflame:
https://review.lineageos.org/#/c/157841/
[OnePlus 3 & 3T Cross Device Development] matssa:
Not sure how to do it, maybe I can on my side when building the ROM, but not sure... Did you try looking on xda or on google?
[OnePlus 3 & 3T Cross Device Development] matssa:
Latest build uploaded guys, flashable on my side, testing underway :)
[OnePlus 3 & 3T Cross Device Development] xantic21:
I tested it. Camera works with stock kernel, camera is broken with custom kernel (I use Boeffal Beta 12). Any solution how to get the camera working again? A rom without a working camera is......Besides this, I really appreciate the hard work!!!
[OnePlus 3 & 3T Cross Device Development] NoobMonkey:
Maybe found away. Haven't tested it yet but it should be as simple as to just replace the Unlock.ogg file in system/media/audio/ui folder. And this of course needs phone to be rooted. And after replacing that just have reboot the phone and it's done. Will tested later when I have time.
[OnePlus 3 & 3T Cross Device Development] matssa:
Nice find, I hope you'll be able to manage it ;)
[OnePlus 3 & 3T Cross Device Development] matssa:
I don't understand how the custom kernel can break things... If Boeffla merged the new kernel commits, should be OK to flash. The only changes for the camera are in the vendor files (I dunno if it is used for the custom kernel) and the device tree (which isn't changed by custom kernel).

My best guess is that not every commit for the new kernel as been added.
[OnePlus 3 & 3T Cross Device Development] NoobMonkey:
Couldn't wait :D it was just easy as I wrote. Now I have my cars engine start sound on my screen unlock sound :cool:
[OnePlus 3 & 3T Cross Device Development] elmkzgirxp:
Setup Wizard crashes on first boot. No GApps were installed nor other mods.
[OnePlus 3 & 3T Cross Device Development] matssa:
Can you please explain a bit more your flashing process? What TWRP you are using, what format of /data and /cache... I can't help you with this limited information... And without logs also...
[OnePlus 3 & 3T Cross Device Development] NoobMonkey:
U should flash gapps right after flashing rom. No reboot between.
[OnePlus 3 & 3T Cross Device Development] matssa:
We don't know if he dirty flashes or if he clean flashes. Without more info, can't help.
[OnePlus 3 & 3T Cross Device Development] elmkzgirxp:
Clean flash, f2fs /data, only installed ROM, nothing else. I'm not sure if I can provide any logs today. But I'll try.

I suspected it was the GApps at first, but I tried to install only the ROM and the problem persists. So I assumed there's something wrong with the Setup Wizard.
[OnePlus 3 & 3T Cross Device Development] matssa:
If you clean flash, flash Gapps or else it won't work IMO.
[OnePlus 3 & 3T Cross Device Development] elmkzgirxp:
Since when did this become how it works? I think back in 20170127 build I was able to access Setup Wizard without GApps.

My point in not installing the GApps is to troubleshoot where the underlying issue is. I previously installed GApps with it with the same issue. If I were to remove CyanogenSetupWizard, then Gestures and Alert Slider won't work. I don't know why you're telling me this now when it has been working previously. I'll see if I can pinpoint among the builds where the issue started.
[OnePlus 3 & 3T Cross Device Development] kar200:
Thanks a lot for the rom.

Flashed the latest one 4.0.2 and I clean flashed it (wiped everything except the internal storage before installing)

It's working good except the slider is not doing anything and the oos camera is missing all the options.

I was just wondering if it's normal or do I need to so anything else to fix the issue?

K.
[OnePlus 3 & 3T Cross Device Development] nanodan:
If you want the alert used to work, you need to clean flash, finish the Lineage setup wizard and verify it is working before flashing GApps. The Google setup wizard does not initialize the slider.
[OnePlus 3 & 3T Cross Device Development] elmkzgirxp:
The same is applied for the Gestures to work too.
[OnePlus 3 & 3T Cross Device Development] piats:
Or make a nandroid and restore it to get working alert slider and gestures!
[OnePlus 3 & 3T Cross Device Development] kar200:
Thanks both for the input. Just tried a couple of times with wiping everything except the internal SD and after first boot I get an error message saying "Setup Wizard has stopped".

Definitely not my day with this one I might wait for the next upload I might get lucky.

K.
[OnePlus 3 & 3T Cross Device Development] nanodan:
Yeah. The setup wizard has been broken for me before too. Forgot about that. It's because of Google Apps. You need to not flash that. Also, any kind of build.prop edits to the model (aka pixelfy or other hacks to get Google assistant to work) will cause this.

You can quickly hit "Skip" in the lower right after selecting a wifi network if you're fast enough.
[OnePlus 3 & 3T Cross Device Development] dmoses1969:
Set SeLinux to Permissive,

Install Notification Slider and grant all permissions and set the slider up the way you want and it will work. I have mine set to Ring/Priority Only/Total Silence

Use OxygenOS Stock Camera Port, Working fine for me.
[OnePlus 3 & 3T Cross Device Development] matssa:
Strange, I don't have this issue on my side... I'll upload a new build shortly, I hope it will fix it.

OOS camera port = already answered 1 page before, and already discussed on OOS camera port thread...

For the alert slider, I had the same issue, but apparently finishing the setup and flashing a newer version of the same ROM made it work again... Very strange I agree.
[OnePlus 3 & 3T Cross Device Development] matssa:
OOS camera port shouldn't work anymore since HAL1 has been disabled.
[OnePlus 3 & 3T Cross Device Development] stryker09:
[MENTION=6313536]matssa[/MENTION] - revert this to fix the alert slider permanently - https://github.com/LineageOS/androi...mmit/3202fb4dae654c52e99dbe5045bfd1f1604d854a

IMO it doesnt even make sense to depend on CMSetupWizard for Alert Slider to work
[OnePlus 3 & 3T Cross Device Development] kar200:
It actually works if I install gapps and its only if I dont that I get the error message.

I get a black screen with the error message and nothing else works (this is brand new flashed rom without Gapps) so I cannot do anything and even to turn the phone off I need to keep pressing on the power button.
[OnePlus 3 & 3T Cross Device Development] matssa:
Thanks, I'll revert this in today's build.
[OnePlus 3 & 3T Cross Device Development] elmkzgirxp:
Is there a similar commit for the Gestures? They also rely on Setup Wizard.

---------- Post added at 10:31 AM ---------- Previous post was at 10:28 AM ----------

Did you remove CyanogenSetupWizard by any chance? Because this will use the Google Setup Wizard instead, but with a few caveats (like no alert slider or gestures).