yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] meiax93:
I will try it once i got campus today. I will post here once i capture with those app ;)
[OnePlus 3 & 3T Cross Device Development] MrCeez:
Will this ROM force encrypt?
[OnePlus 3 & 3T Cross Device Development] Jole7:
Nope
[OnePlus 3 & 3T Cross Device Development] meiax93:
As long you delete first your password and fingerprint, then it will be alright :D
[OnePlus 3 & 3T Cross Device Development] sjknight413:
Found another weird bug, with Google camera spot metering does not work. So you can't tap on a location in the scene and have it readjust exposure for that spot. Works in the default snap camera but in Google camera it meters automatically for the entire scene.
[OnePlus 3 & 3T Cross Device Development] :
Whats the security patch level i cant find it?
[OnePlus 3 & 3T Cross Device Development] Mr.Jay:
Oh God, thanks!! ❤️

Sent from my OnePlus 3
[OnePlus 3 & 3T Cross Device Development] Nezorflame:
When you press Home and return to home screen of not-default launcher (Action Launcher 3 for me), the screen is always redrawn. Even if you're already on it, it just always refreshes.

Does anyone experience this too?
[OnePlus 3 & 3T Cross Device Development] akira8473:
Cant wait to flash. Big test will be if I can make calls from my gear s3, So many roms break the Bluetooth functionality for this.
[OnePlus 3 & 3T Cross Device Development] allgrey:
Do I need flash firmware before installing this ROM? Im on RR Rom right now and dont know how to properly flash Paranoid..
[OnePlus 3 & 3T Cross Device Development] VincentJoshuaET:
Does this support OMS? OP mentions only Substratum.
[OnePlus 3 & 3T Cross Device Development] xpissio:
Nope, firmware it's included in the ZIP of the ROM.
[OnePlus 3 & 3T Cross Device Development] 127cwho:
Sorry I can't find the file...
[OnePlus 3 & 3T Cross Device Development] S4turno:
You said the same thing two weeks ago :p

I know I'm not entitled to anything here, and please don't take this the wrong way, but I think the way you guys deal with updates is wrong.

The first time I used (some of) your work was back in 2015(?) with the Exodus ROM (Android 5.1.1)... that ROM made me love my Oneplus One. It was fast, had almost no issues and fixes would be delivered in a short time. Most of the nightly updates didn't contained anything new, but when something was fixed, we just had to wait another day to receive an OTA update. I was so happy that I even donated money to help with the server costs.

Now we have here another great ROM and I like it! This was the first build, so the few bugs we found were expected. What I was not expecting was the time between builds. I might be wrong, but I believe that some of the bugs (eg: battery drain) were fixed very quickly. Yet, a month after the first build, we still haven't received a build with those fixes. We don't even know what are the plans regarding updates ("when it's ready" or "soon" can be 1 day or 1 year...). This behavior is what we expect from manufacturers, not from custom ROMs.

We don't use PA because we want to use the most recent Android version or because we want a clean experience (Oneplus already takes care of that). We are also not looking for lot's of features, after all this ROM is very simple/plain, and most users don't care about code quality either. PA's team work on the camera is a big plus, but if the ROM is not the most stable and if fixes take a long time to reach users, then there is no reason to use this over stock OOS or LOS. I'm also not sure if delaying new updates just because some new feature or some phones are not ready is the best thing to do. Any update fixing annoying bugs is more important than new features.

I like this ROM and I do appreciate all the hours you guys put into this. For me it's very hard to criticise someone when they are working for free. But I really think that the lack of quick updates for small problems is the biggest downside of this ROM and the main reason why many had to leave PA 6. This slow update schedule doesn't work for people who flash aftermarket OSes.

Just my opinion... please don't be offended by it. :)
[OnePlus 3 & 3T Cross Device Development] Ducter:
That's it!! I'm not paying you guys anymore for this!! I've paid so much of nothing that I feel robbed and I can't continue any longer, matter of fact I want, no, demand a full refund!

Really people? What the hell... Do you all really think that the devs have everything ready to go, fully functioning and are just not releasing it? They have put even more hours into fixes and improvements and just keeping it to themselves? When it's ready you'll get it. Let's imagine they release an update and whatever's not fixed or other issues arise they'll be burnt at the stake. Let them do their thing and when it's done, download and enjoy. Until that time it stands to reason it's not ready.
[OnePlus 3 & 3T Cross Device Development] S4turno:
[MENTION=1479665]Ducter[/MENTION]... C'mon, don't do that. I started my comment with "please don't take this the wrong way" and finished with "please don't be offended". Is that hard to understand that I don't have bad intentions?

I really don't understand why you reacted like that. I have defended them here before, I haven't complained so far, I'm not demanding anything and I tried to be gentle. I even said some of the things you said.

If every suggestion is to be received like that, then there's something wrong here.
[OnePlus 3 & 3T Cross Device Development] sacredsoul:
Hey man, possible to include the option for this? I believe it has to be added in the kernel level.

https://xdaforums.com/oneplus-3t/how-to/enable-dci-p3-op3t-s6e3fa5-display-panel-t3628783
[OnePlus 3 & 3T Cross Device Development] arter97:
We will be looking into the various color mode, but it may be excluded in the next update.

Perhaps next, next update...
[OnePlus 3 & 3T Cross Device Development] notanoob:
S4turno never implied that he expects updates because he donated. His point is correct Bug fixes are important than features. There is no point in having an XDA thread if all the Dev's wanted is to keep their work for themselves.

Again we appreciate every dev's effort but only wish bug fixes come in an reasonably scheduled time or at least as an OTA fix .
[OnePlus 3 & 3T Cross Device Development] prateektaneja:
It's not our right to demand anything from PA since we're not paying for it. But that being said, you have to look into the goal of the PA team. In the end, they'd like us to use their ROMs. If they didn't want us to, why'd they develop at all? But the ROM in it's current state is stopping quite a number of users from using it as their daily driver. I think everyone here would like a quick fix for the idle drain so that we can get back on the PA train. No one here is clamoring for new features. Everyone just wants the drain to be fixed so at least they can use and enjoy it. And since the drain's been fixed, it'd make sense to put it out or even a small patch fix.
[OnePlus 3 & 3T Cross Device Development] foxsprout:
The numbers of custom ROMS' death are more than those maintained. Because PA is waaaay more popular than those, everyone is starting to feel this should be better than what OEMs provide, in terms of updates. Imagine LOS stopped their nightlies, or even missed one window.. everyone will be going wild!
[OnePlus 3 & 3T Cross Device Development] pantmunu:
This threads going wiiiild .. also my post is pointless. But, give them.some time, bug fixes are important but how about a proper update with all the bug fixes and moar awesome features and stability. Sounds good right. Perfect. Let's not fight or argue over this, it's not gonna help anyone. Peace !!
[OnePlus 3 & 3T Cross Device Development] dante_nfs:
It's your problem, don't make it sound like it's everyone's problem, the ROM is tested, so if you have drain, check your apps or other things.
[OnePlus 3 & 3T Cross Device Development] S4turno:
Just to be clear, I'm not suggesting nightly or weekly builds. I'm also not asking for new features. All I'm saying is that for users is better to have smaller and faster updates with bug fixes than big updates, full of new features and bug fixes, that take a month or more to prepare.

For example, let's say that the battery drain was fixed two weeks ago. Instead of waiting until the next big update and force users to live with that bug, an update with that fix could be released.

And that's it. This is a suggestion, not a complaint, a demand or an attack on developers. There is no need to be so defensive when someone points out something that could (or not) be improved.

[MENTION=5733953]foxsprout[/MENTION] Updates are one of the reason many choose to use custom ROMs. It was back in 2012 when I flashed CM on my Galaxy 2, and still is today. We are lucky because Oneplus updated this phone until now, but we all know that this is not the case with many other phones.
[OnePlus 3 & 3T Cross Device Development] foxsprout:
I may be sound so defensive many times, but I'm speaking logic. You should've known better that CM/LOS is so structured from head developers to maintainers. That alone should give you insight how PA works. PA, IMO, can't be compared with CM/LOS. It has loyal fanbase and is similarly popular, true, but it's just not the same. The objective and manpower is different. Like kernel, some adds sooo many features, yet some only provided for root solution.
[OnePlus 3 & 3T Cross Device Development] :
Just like you said, it's not about the paying thing but the actual idea behind of why as a team go on a big long post on social media saying you're back and you want people to use your rom, even saying you promise to support it for a lot of time, basically trying to sell it and all of that if you aren't going to support it(with major bug fixes when you can instead of waiting for new features) ?

There's a big difference imo between great programmers and great business planners (even in a free, community business plan) and seeing PA past (and definitely current) plan we can see why they're failing to maintain users.

This post will be deleted probably by the xda police bc for some reason you can't talk about a rom in its thread (except for saying how good it is 111!!!) but this rom is the most overrated one I've ever seen in my android experience. And the devs are ones of the best sale people I've ever seen with actually responding to people with "very soon" phrases for over 3 weeks now, which is light years in an android custom roms community where very soon might mean the next day.

Edit: also at this point with all the bad rep they gained by users from their stubbornness to not fix bugs.. I'm not sure it's fixable. Yeah people will jump on the next update but it won't be the same numbers as in the first announcement. It's a shame they ruined it for themselves again.
[OnePlus 3 & 3T Cross Device Development] Stephen:
Moderator Information,

Thread cleaned, please do not discuss other roms on a thread. It is disrespectful to the developer.
[OnePlus 3 & 3T Cross Device Development] :
What do you think?

http://imgur.com/a/GFzuF
[OnePlus 3 & 3T Cross Device Development] jirik152:
cam is good, cant tell better than stock, but definetely same level as stock. For me its not usable at this time, because of low call volume...
[OnePlus 3 & 3T Cross Device Development] helderfp:
If you dont like dont read, bu the way it is not my problem it is a very well known bug, the idle drain is too hi and the developers already said they are working on a fix. But the problem is they are working since the first release that was over a month and no fix untill now, but ive manage to minimise the drain by installing Naptime.
[OnePlus 3 & 3T Cross Device Development] :
I don't understand you. Let me tell you this, you are free to say your point of view but ultimately it's the team that's decides what's best for them. And if you don't like their decision, you are free to try other great ROMs out there too.
[OnePlus 3 & 3T Cross Device Development] nikexv2:
I'm feeling this post is going to trigger people but well.

Weeklies or nightlies would open the possibillity to debug things faster and test stuff on a larger scale.

Idle battery drain issue would probably not exist if the rom was tested on a larger scale before the big release.

This makes the work of the devs more easy, assuming people report bugs correctly with logs etc..

I'm not even using this rom.
[OnePlus 3 & 3T Cross Device Development] jomansch:
you can try this, for me it fixed bluetooth-problem in my car ... don't remember the thread I found it ...
[OnePlus 3 & 3T Cross Device Development] andre0005:
Flashing PA renamed my op3t to Oneplus3. Now trwp gets confused and refuses to install OOS for my OP3T. How do i fix this? I already wiped my phone. It's completly empty right now...

I'm on arters newest twrp build. I was about to return back to stock because i sold the phone. Now i'm stuck with a brick.

Edit: Looks like it was an issue with arters twrp. Nevermind i managed to fixed it.
[OnePlus 3 & 3T Cross Device Development] darjwx:
What's the problem? The flashing process fails because it says you are using a op3 instead of a op3t? The solution is simple, just edit the backup.script inside the ROM zip and remove the first line that's checking for the phone model.

Route: inside the ROM zip: META INF/com/Google/android: updater-script.

Remove:

getprop("ro.display.series") == "OnePlus 3T" || abort("E3004: This package is for \"OnePlus 3T\" devices; this is a \"" + getprop("ro.display.series") + "\".");

Other solution, install official twrp. The zip will identify your phone correctly.

I guess this problem is derivated from the unified stuff.
[OnePlus 3 & 3T Cross Device Development] burduli:
It was soon before, now it's very soon. There's a progress.
[OnePlus 3 & 3T Cross Device Development] Gallardo994:
Sadly, as it was before, PA team showed up with the Amazing™ Comeback™, added a feature or two and never updated a single time later on. Too sad the same thing appears to be repeating all over again. The ROM used to be great in KK times, but the lack of community interaction (e.g. releasing sources for everyone to contribute) is killing it. For example, I've been waiting for almost 2 weeks to finally unlock my device and install something worthy instead of OOS, yet it just destroys any will to continue waiting, and one of the reasons - if there is going to be a problem with the new release, no-one will care to release a fix for it until September or later, if ever.

We need community interaction, this is main thing on XDA, and at this moment PA team is just running away from it.
[OnePlus 3 & 3T Cross Device Development] comediiian:
no one force you to use it.

cmon, build your own rom, share it and give us weeklies.
[OnePlus 3 & 3T Cross Device Development] Sefyron:
next time will be : very very soon ?
[OnePlus 3 & 3T Cross Device Development] :
Thread cleaned by OP request.

Please remain on topic here at all times and respect the OP's request that you do so.

Thanks!

The Merovingian

Senior Moderator
[OnePlus 3 & 3T Cross Device Development] :
How talking about the rom itself in it's own thread and in a civil manner is not being on topic? Are threads here just to say positive things? is this what xda came down to? no criticism allowed?

I think what just happened- a dev saying he doesn't want to share his sources because he doesn't want other roms to use it(as they provide better support and more features) and insists on being stubborn and not update\fix bug on his own rom should be known by the users.

Why would XDA glory PA when they announced they're coming back and now delete comments of users responding to the same team saying they don't want to contribute to open source?
[OnePlus 3 & 3T Cross Device Development] Thecrazyskull:
I agree, I just want to make it very clear that this was not a team action. The decision to get the thread "cleaned" was made by [MENTION=5986135]TheCrazyLex[/MENTION] alone and does not represent the team.
[OnePlus 3 & 3T Cross Device Development] :
This is a discussion best had via PM and again please respect the OP's request by keeping it out of the thread.
[OnePlus 3 & 3T Cross Device Development] helderfp:
Why my post was deleted?

just because i talk of gap between releases and the time is taking to fix the bugs on this rom?
[OnePlus 3 & 3T Cross Device Development] :
Again, I understand, which is why I was hesitant to remove any discussion here. I spoke with OP via PM and it was decided that this particular discussion would be best kept to PM.

Also, to avoid any further disruption, please bring any concerns directly to me via PM and I'll do my best to resolve them.

Thank you! :)

Edit:

I also suggest opening a discussion thread in the general section to openly discuss your concerns.
[OnePlus 3 & 3T Cross Device Development] Diaze:
The wait

..
[OnePlus 3 & 3T Cross Device Development] Cristiano Matos:
Could not be more perfect. Thread cleaned one more time and all good discussions are erased as usual. Let's keep the AOSPA perfection even in hiding substantial aspects of conversation.

Good work again XDA mods! Sarcasm of course.
[OnePlus 3 & 3T Cross Device Development] happytab999:
I think this is getting out of hand and it's 100% down to the "no ETA" rule in my opinion. While I know the rule and choose to observe it I can also see how frustrating it is to not have any idea if and when the fixes for the common bugs are going to be made.

If the rom was terrible most would have moved on quietly to something different and the thread wouldn't have got toxic. The problem is we like what we see and are loathed to flash something else if an update is just around the corner. So we are just left in limbo and people get frustrated.

I will see it through personally but can see why others fire a broadside in frustration and move on.
[OnePlus 3 & 3T Cross Device Development] nyzoli72:
oh my god, like a kindergarden! Yes I'm waiting the new build and yes it takes too much time, but what can i do? I can try another rom or try make my own rom (problem is i can't) or just waiting. that's it!
[OnePlus 3 & 3T Cross Device Development] c1ph4:
What's going on here, it's like all of a sudden users go Creutzfeld Jakob all over. :confused:

BTW, here are the dates of the changelog of the official download site:

2016-06-16, 2016-08-01, 2016-09-06, 2017-05-30.

As you may see easily, there were almost two months between the first and second release in 2016. So no big deal we'll have to wait until the end of July for an update! "Very soon" means "very soon". Be happy and stop complaining, please.

As I understood PA got a policy of not releasing weeklies, nothing wrong with that. Other ROM distributors offer nightlies, you're free to try them too.

Also, could we please go back to what's not working yet as it is the usual way here!? Reporting bugs and if those are heavy bugs, attach a log, please. So devs know what's not working and can fix this.

For me Bluetooth is not working. Despite that so far I found nothing to not use the current version as a daily driver. For some it's an essential feature (like in my case with my headset, but can switch to cable), for others not.
[OnePlus 3 & 3T Cross Device Development] TheCrazyLex:
Since a part of our OTA system was damaged at the release of the first build, we are forced to release for all devices at once for the coming update, which is in final testing.

That update will ship the fix for the OTA system which will make us able to ship device specific updates which don't increment the version number but only the build date.

After that happened we will try to provide more frequent releases.
[OnePlus 3 & 3T Cross Device Development] 9600pro87:
Good to ear! This is the right way to release OTA updates. Specific release for fast bug fixing and major release once a month for new features or big improvment.
[OnePlus 3 & 3T Cross Device Development] nrusimhamurthy:
Good to hear.

Flashing now
[OnePlus 3 & 3T Cross Device Development] rob rich:
Thanks for the Heads-Up. That's the way to talk to the community and to prevent people from spamming the thread and arguing against each other :)
[OnePlus 3 & 3T Cross Device Development] Uruloki64:
Is magisk v13 compatible?
[OnePlus 3 & 3T Cross Device Development] S4turno:
Yes
[OnePlus 3 & 3T Cross Device Development] pcs333:
I have been trying all day to get various versions of viper4 android working. I have had no luck.

I have no issues installing on stock or los based ROMs. But for some reason I can't get it working with PA.

I have tried officially viper and arise. I can't even get the

Driver loaded.
[OnePlus 3 & 3T Cross Device Development] ctakah27:
Working great through ARISE.. Make sure you have busybox and try SELinux =permissive
[OnePlus 3 & 3T Cross Device Development] pcs333:
Which busybox?

The usual one I use didn't install so I used another one which did. Arise still didn't work though even on permissive
[OnePlus 3 & 3T Cross Device Development] ctakah27:
What do you mean it didn't install? Busybox didn't install? I use stericson..

Did you have arise working before? Maybe you're installing arise wrong?
[OnePlus 3 & 3T Cross Device Development] mvlad:
Are you using magisk? Search XDA for the Arise Magisk Compatibility Module.
[OnePlus 3 & 3T Cross Device Development] mangoman54:
If you're using magisk, flash the audio modification library mod and it'll work flawlessly
[OnePlus 3 & 3T Cross Device Development] ShiShTuBaBu:
I also had this issue, busybox wouldn't install, arise or any other viper wasn't working. then I installed magisk viper module and had to 'setenforce 0' in terminal emulator to get permissive. then installed viper 2.5 apk.

and finally it worked.
[OnePlus 3 & 3T Cross Device Development] jirik152:
guys sorry for disturb, the only problem for me with this rom is low in call volume. Do you have any workarrounds?
[OnePlus 3 & 3T Cross Device Development] skothiya:
How to change file system to F2FS ?

I tried to to change from TWRP but after installing PANAROID it against come to ex4.

So is there any way to change file system
[OnePlus 3 & 3T Cross Device Development] foxsprout:
Which TWRP? I think you use different TWRP than the one stated in the OP
[OnePlus 3 & 3T Cross Device Development] skothiya:
I use twrp-3.1.1.0-aospa
[OnePlus 3 & 3T Cross Device Development] mvlad:
File system =/= system partition.

System is supposed to be ext4. To change partition in Wipe check both internal storage and data then continue. Make sure to backup your stuff though because it's going to be empty.
[OnePlus 3 & 3T Cross Device Development] skothiya:
Data partion is already f2fs partion

Than i need to wipe internel system to?
[OnePlus 3 & 3T Cross Device Development] mvlad:
No
[OnePlus 3 & 3T Cross Device Development] Againstt:
You should be good to go then
[OnePlus 3 & 3T Cross Device Development] skothiya:
Do i have to install rom after change system partion to f2fs?
[OnePlus 3 & 3T Cross Device Development] skothiya:
I want to change system partion from ex4 to f2fs:confused:
[OnePlus 3 & 3T Cross Device Development] crysen:
You don't need to change the system partition to F2FS, or in other words: it's not recommended afaik.
[OnePlus 3 & 3T Cross Device Development] foxsprout:
Misread your post. As stated by above post, it's not recommended to use f2fs on /system. That's the default one.
[OnePlus 3 & 3T Cross Device Development] chasemyass:
It already been explained why f2fs doesn't have to be used for system and why rom switches it back to ext4. Before you ask something you want to do, better look forward to see if that will be "the thing" you really want (that's not the case here).

OT. Now you guys see why talking with no use regarding development of this ROM isn't healthy for some xda members. Instead of searching an answer (bc most of them forgetting that there is a tool that can be used for that and it's a part of EVERY forum) most of people just starts scrolling to see if there is another question like theirs (and answer too). After pages and pages they just give up on searching and therefore we see the same question posted lots and lots of time.
[OnePlus 3 & 3T Cross Device Development] krish@3T:
Can anyone upload the pa camera app plz