yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] mvlad:
No, sometimes if you used an old f2fs version with a new twrp/kernel it has the odd behaviour to crash apps some time after boot with ultimately freezing the whole phone which needs a hard reboot. I had this happen with Blu_spark updating the kernel f2fs on a number of occasions on other roms.
[OnePlus 3 & 3T Cross Device Development] :
There's no need to erase internal storage for clean installs (unless you're changing file system). You don't need to format through fastboot and then again with twrp. Any one is fine. Also, there are more partitions then you listed. Albeit they are not available to tinker (could be dangerous).
[OnePlus 3 & 3T Cross Device Development] Gomezie:
So is wiping from within twrp recovery sufficient, or does it HAVE to be from fastboot?

Seems extreme otherwise :rolleyes:
[OnePlus 3 & 3T Cross Device Development] :
Yes it is sufficient.

---------- Post added at 08:15 AM ---------- Previous post was at 08:07 AM ----------

I don't understand all this talk about wiping internal storage. YOU DON'T NEED TO WIPE INTERNAL STORAGE FOR CLEAN INSTALL. PERIOD.

Note: For this particular rom if you've ext4 file system on internal storage, it is recommended to change it to f2fs (which requires wiping internal storage). It doesn't mean it won't run on ext4. It will work fine. Albeit, you may encounter errors and you might not be able to get the optimal performance out of it (for this particular rom). It just means that developers have optimized this rom for f2fs filesystem (internal storage) and they won't provide support for otherwise.
[OnePlus 3 & 3T Cross Device Development] Gomezie:
That was my understanding too, thanks for sharing mate
[OnePlus 3 & 3T Cross Device Development] TheCrazyLex:
The wording is probably a bit confusing, I'll try to correct it soon.

So to use f2fs correctly on this ROM, you need to install [MENTION=4898097]arter97[/MENTION]'s recovery (check the 2nd post) and to wipe internal (and maybe other partitions) using the mkfs.f2fs option. If you are on f2fs already, then you still need to do the wipe, as the recovery has an updated wiping process.

If you are on f2fs which was created using the newest special recovery, then you don't need to rewipe internal.
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Just for information

Blu spark twrp works without any problem so I keep that one ?
[OnePlus 3 & 3T Cross Device Development] :
Could you elaborate on updated wiping process. I don't see how wiping process has anything to do with file system. I mean why would one have to wipe if one already has f2fs.
[OnePlus 3 & 3T Cross Device Development] Antsu:
I think it's related to f2fs drivers. Op3(T) oos uses stable and older f2fs sources and arter97 (also eng.stk) uses more recent sources. So, if you come straight from default oos f2fs partition it's not compatible with aospas' f2fs sources, hence the wipe is needed. Sorry for lack of right terms, but hope you get the idea.
[OnePlus 3 & 3T Cross Device Development] PxlFall:
I think I already stated, that I'm experiencing this "PA quality" on Oxygen OS.
[OnePlus 3 & 3T Cross Device Development] :
You mean kernel driver for f2fs? shouldn't the kernel drivers be backward compatible considering it's an filesystem?

Edit: I just saw the f2fs gerrit. You mean they use the entire new version of filesystem, right? Makes sense! [MENTION=5986135]TheCrazyLex[/MENTION] can you confirm this?

Edit2: Ok, I see that the new driver (module I mean) for f2fs and the new version are one and the same thing. So, it's likely that PA's kernel uses newest filesystem implementation and so it requires to wipe the internal storage. But, considering the fact that it's actively developed (f2fs I mean), for users to wipe every time a new stable version comes out is not a good choice. It's all just an speculation though. I can be totally wrong here!
[OnePlus 3 & 3T Cross Device Development] Antsu:
[MENTION=7846556]0xelectron[/MENTION]

Yeah, that was just a guess. [MENTION=4898097]arter97[/MENTION] might be the right person to elaborate this more.

But the instructions are in the OP and when people follow it, there shouldn't be any issues. At least I'm not having.

Although I have "unsupported" installation as the phone is encrypted. In arter97's tweet he recommended using f2fs with unencrypted phone. But since this seems to be working well, I'm glad to have a little bit more security on board.

Btw, I have only /data on f2fs. I'll keep it this way until OP gives more info about that.

Thanks to AOSPA team for the wonderful rom :good:
[OnePlus 3 & 3T Cross Device Development] :
Yeah, I would love to know more about what [MENTION=5986135]TheCrazyLex[/MENTION] meant by "(and maybe other partitions)" and also about the new wiping process.

Thank You.
[OnePlus 3 & 3T Cross Device Development] miodrag.cutura:
So,

Developers, is there any way you can make exFat readable via usb-otg by default?

I so wanted to try using your rom, but all my backups are on my usb C flash drive, and sadly, exFat is showing as corrupted...
[OnePlus 3 & 3T Cross Device Development] andre0005:
Can't you just backup your files to a pc and format your stick to a supported filesysstem?
[OnePlus 3 & 3T Cross Device Development] arter97:
Why we want to sync f2fs configuration?

Since f2fs on Android was a bumpy ride, I took an enormous amount of time to get it just right.

Why not just use OEM's f2fs?

I wanted to make our f2fs setup up-to-date so that it has the latest and greatest that mainline offers.

Some of you may recall my f2fs-related post on SuperSU thread. I was still investigating f2fs at that time.

If you see that post again, you'll see why we need a separate recovery(with sync'ed f2fs setup).

And we also wanted all f2fs users to cleanly wipe partitions with mkfs.f2fs when using AOSPA.

This is because I noticed a severe issue with GC on older versions of f2fs, which can tank down the write performance.

We wanted to avoid GC issues created by the previous setup and make AOSPA experience poor.

I'm pretty confident we have the best f2fs configuration out there,

but it may be only obtainable if you used our f2fs configuration exclusively, which can't be done if :

a) You use another recovery build

b) You used f2fs previously and switched to AOSPA without a full wipe(mkfs.f2fs)

TL;DR - We want our f2fs configuration to be the only one writing data to your f2fs partition

If you don't want to go through all these shenanigans, just stick with ext4.

If you intend to go back and forth to other ROMs, just stick with ext4.

If you don't understand a word I said above, just stick with ext4.
[OnePlus 3 & 3T Cross Device Development] shrek8421:
[MENTION=4898097]arter97[/MENTION] thanks for the detailed post. Not sure if this is the right place to ask but are there any tangible benefits with f2fs over ext4. Thanks for all your hard work
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
See below:

https://xdaforums.com/showthread.php?t=2697069

In short, it is faster.
[OnePlus 3 & 3T Cross Device Development] Ducter:
You can figure that out with a quick Google search, some swear it's the holy grail, others say really not much differences when actually using your device, benchmarks do not always show real usage results. I have found a slight increase of loading speeds but honesty, nothing I would be able to notice if it was ext4. YMMV and suggest trying for yourself. The truth will lay somewhere between the 2, again, try it for yourself and decide.

All tho he has posted this information before, maybe it will actually get read this time and put an end to those recommending installing things their own way. Respect the time and work devs put into releases and try what they recommend.
[OnePlus 3 & 3T Cross Device Development] :
Thanks for your explanation man! It all clears things up. And thank you all for your hardwork.
[OnePlus 3 & 3T Cross Device Development] Siddk007:
wiil stay with ext4 mainly because of this reason "If you intend to go back and forth to other ROMs, just stick with ext4"
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
AOSPA forever
[OnePlus 3 & 3T Cross Device Development] Xumit:
Thank you for your review. Also, this happens to me a lot - Phone gets hot when in pocket, stays awake most of time and battery drops significantly! I love this ROM but can not use it because of this issue. Any solution to avoid this pocket idle battery drain?
[OnePlus 3 & 3T Cross Device Development] Ducter:
While I haven't tried it, OnePlus control center is said to help. A quick search should turn it up.
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
I have no pocket idle drain and especially not any issue with the phone getting hot while in my pocket... My idle drain is maybe 6% every 8 hours which isn't horrible (that's in deep sleep, overnight) they are working to improve battery for the next build.
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
I tried working around the issue by installing a 3rd Party app named "OnePlus 3/3t Control center", which used to work like a charm on any other ROM that lacks any kind of Pocket Mode implementations, but strangely it didn't work either...

We can only wait for [MENTION=5986135]TheCrazyLex[/MENTION] to give us an updated build with the necessary fixes stuffed in, which I am pretty sure that it's already done :)
[OnePlus 3 & 3T Cross Device Development] masaichris:
I have OpenGapps Mini installed but still facing this same issue with Assistant.
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
Sorry don't know what your issue can be, I have used Open Mini, Nano, Beans Mini and Beans Full all with clean installs with this ROM and had no issues with assistant on any of them (3T)
[OnePlus 3 & 3T Cross Device Development] Gallardo994:
Running 3T 128gb. Locked and full stock. Will I be really missing OOS if i move to AOSPA? What will i lose? Except for my data, of course. Thanks
[OnePlus 3 & 3T Cross Device Development] AlemanSantos:
Expanded screenshots, camera quality, battery life.
[OnePlus 3 & 3T Cross Device Development] Gallardo994:
I mostly rely on RAW images than pre-built camera postprocessing. Am I still able to save RAW in AOSPA?
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
Yes but only with 3rd party camera apps. In my opinion you GAIN by switching from OOS to AOSPA. I was recently running OOS Stable and OOS Beta 8 and neither of them provided the smoothness of operation and quality experience I was looking for. I get all of that with AOSPA. Also battery for me (SOT) is better on AOSPA than OOS.
[OnePlus 3 & 3T Cross Device Development] Gallardo994:
Which camera would you suggest for RAW? Will it utilize the promised optimizations made in PA then? Thanks
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
I personally don't use any camera other than the PA cam. The PA cam is excellent and I can't tell the difference between it and OOS. if I were you I would just Google search good raw cameras for Android. Hope you make the switch like I did!
[OnePlus 3 & 3T Cross Device Development] mvlad:
Camera fv-5
[OnePlus 3 & 3T Cross Device Development] lpsld:
Any way to turn off the "Smart Switch" in asopa?

Explanation: Smart Switch is a function to Switch over to mobile data if your Wlan Signal is to low or not working. In my case my wlan sometimes loses signal and uses my mobile data.

In Stock OOS there is a switch for it so i can turn it off but in most other custom roms this Switch is not even existing.

If someone of you know a workaround for that or some kinda app for it, please share your ideas with me :).

If not, please implement this feature in the next build :good:
[OnePlus 3 & 3T Cross Device Development] Gallardo994:
You can just disable mobile data and keep wifi running, it will force into it then
[OnePlus 3 & 3T Cross Device Development] lpsld:
Sadly, it wont. Also the X over the data icon is not that pretty to see (I could life with it)

I will have to go into wifi settings and connect manually to it again. Because it doesnt automaticly reconnect to it again. I dont know what im doing wrong, probably oos uses a another wlan driver as asopa does but on oos it doesnt even disconnect it sometimes just shows on f. e. chrome that i have no network.

I think its just a personal Problem but im encountering this issue in most all other roms :(
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
Get a better router
[OnePlus 3 & 3T Cross Device Development] lpsld:
Fritzbox 7490.

Change your behavior and help people and not only tell us how good The rom is, because we all now that.
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
Lol you are bringing up something that isn't even related to this ROM, this ROM isn't going to have all the features and functions of OOS, it's not supposed to... The issue that you are having is something I have never heard anyone have, in the history of me having Android phones and it is an issue I have never experienced myself. So if you want that obscure feature in your ROM, I recommend staying on OOS.
[OnePlus 3 & 3T Cross Device Development] lpsld:
To say it in other words,

wlan isnt connecting automaticly after restart device / restart router
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
Not a ROM issue
[OnePlus 3 & 3T Cross Device Development] S4turno:
As far as I know, only the PA camera will use their optimisations. To save JPG+RAW files, you have a few options:
[OnePlus 3 & 3T Cross Device Development] lpsld:
But how can you say that?

On LOS it worked for me, it was connecting automaticly when restarting my router

just tested rn
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
It's still not a ROM issue... Just cause something works on one ROM and not another doesn't mean it's an issue with that ROM. LOS and ALL other ROMS other than OOS and AOSPA are unable to utilize phone calls over Bluetooth in my car. That doesn't mean all those other ROMS have an ISSUE, it just means they don't have the exact same functions as OOS and AOSPA... your router issue most likely isn't something that the DEVS of AOSPA are going to address cause literally no one else has this issue... Sorry mate
[OnePlus 3 & 3T Cross Device Development] twentyfourinc:
So, I dont get what f2fs partition that I must use arter97 twrp, system partition or data partition?

(My Default sytem with ext4 data with f2fs)

Sory if it dumb question..

---------- Post added at 03:51 AM ---------- Previous post was at 03:51 AM ----------

So, I dont get what f2fs partition that I must use arter97 twrp, system partition or data partition?

(My Default sytem with ext4 data with f2fs)

Sory if it dumb question..
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
Only on data. You must use Arters TWRP. just follow the instructions from the second post and you should be good!
[OnePlus 3 & 3T Cross Device Development] Xumit:
Thank you for the app suggestion. Will try it for sure! Hopefully we get this fixed in next build :)

Idle battery drain is even less for me when phone is lying on bed. The issue is when the phone is in pocket. I have this same issue in stock rom as well. Hopefully this app fixes it.
[OnePlus 3 & 3T Cross Device Development] sembraottobre:
From today I also join paranoid
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
Congrats ???
[OnePlus 3 & 3T Cross Device Development] sembraottobre:
Is also a telegram group ?
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
Not as far as I know.
[OnePlus 3 & 3T Cross Device Development] Nezorflame:
ignore please
[OnePlus 3 & 3T Cross Device Development] ram4ufriends:
There is one already...

http://www.t.me/paranoidandroids
[OnePlus 3 & 3T Cross Device Development] Nezorflame:
Thanks for the link, removed mine.
[OnePlus 3 & 3T Cross Device Development] foxsprout:
It will be fixed :) I wrote a reply to your other similar post pages back. Look at 'quotes' tab

---------- Post added at 12:13 AM ---------- Previous post was at 12:09 AM ----------

Kinda weird you said WiFi issue is not ROM issue where all I see from kernel threads that connectivity issue is most likely a ROM issue.
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
If my WiFi is working great, the issue is with his router, not the ROM. therefore not a ROM issue.
[OnePlus 3 & 3T Cross Device Development] foxsprout:
Wow. A note that if you don't experience the problem, doesn't mean the problem doesn't exist. But, after re-read the issue, I stand corrected. I guess, [MENTION=7838256]lpsld[/MENTION], you might want to use your phone closer to your router. I have bad reception of Wifi in my room (1 bar) but it still connected
[OnePlus 3 & 3T Cross Device Development] :
Ok, try disabling WiFi scanning. It's in settings --> location --> (3 dots) scanning --> WiFi scanning.

---------- Post added at 01:14 AM ---------- Previous post was at 01:08 AM ----------

It's in developer options. "aggressive WiFi to cellular handover"
[OnePlus 3 & 3T Cross Device Development] champ784:
So after trying to scroll through all the post to try and see if anyone else had the same issues, I found two things that I'm having issues with.

1. After installing Magisk after running a clean install, the only thing I'm missing is safetynet. Root is working just fine, and I've tried both V12 and V13, to no avail.

2. I have a pair of bluetooth headphones (Jaybird Freedoms) that work on every ROM except for this one. They connect, but immediately cannot play media, even if I try to toggle media playback off and on. The headphones work perfectly with other devices. I also connected my Bluetooth speaker, which works for the most part, but will occasionally have static coming through randomly. I've tested the speaker (UE Boom 2) with other devices and ROMs and have confirmed it is working.

Running AOSPA release for OnePlus 3 on stock kernel, TWRP designed for AOSPA, and non-ext4 file system.

Anyone have any suggestions? Love everything else about this ROM besides these two issues! Thank you to the team who works diligently on this!
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
1. Safety net is a known issue right now for every single ROM, caused by a Google update. Will be fixed in the near future.

2. Bluetooth issues with AOSPA will be fixed in the next build.
[OnePlus 3 & 3T Cross Device Development] champ784:
Awesome! I figured they may be somewhere in the thread, maybe I'm just blind... But thanks!

In no way am I trying to push for forced answers or deadlines, but is there an ETA on the release for said fixes? Or is it something that is still unknown?
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
I would say hopefully in the next few days, worst case the next few weeks at MOST.
[OnePlus 3 & 3T Cross Device Development] champ784:
I can live with that! Still love what AOSPA is bringing to the table!
[OnePlus 3 & 3T Cross Device Development] Nagi2195:
As a temporary solution you can enable core only mode and reboot. Safety net works after that.
[OnePlus 3 & 3T Cross Device Development] champ784:
I tried that and it didn't work... But no big deal! It's not a deal breaker for me! Obviously, it's nice to have, but I'll live!
[OnePlus 3 & 3T Cross Device Development] mvlad:
You checked magisk hide, right?
[OnePlus 3 & 3T Cross Device Development] kkcckkcc:
very good rom :good:

back camera become completely-green at first boot，front is ok. after another boot its all right.

hope to change Vibration intensity in kernel.
[OnePlus 3 & 3T Cross Device Development] rg90:
I'm running this ROM now for 2 weeks. At first the performance was unmatched. Everything was blazing fast and smooth.

However this week I have some occasionally lags and the overall smoothness is gone, while nothing has changed in my use cases. Not even new apps installed.

Apart from the lags (which are random), the ROM is not slow, but the amazing performance that was present after I installed the ROM is gone.

Any ideas? 3T and data is on f2fs (formatted with arter97's twrp)

--EDIT:

I investigated this further. It appears that my Sygic navigation app was running in background, and after closing it, the lags are gone for now. The performance is back from holiday:).

From what I know, Google had implemented something in 7.1.2 that alerts the user if something in the background is taking al lot of resources. Could you guys maybe implement a similar function like that? Would be useful to me.

Thank you, keep up the good work.
[OnePlus 3 & 3T Cross Device Development] js931:
I also get some hiccups from time to time. Hard to reproduce, but the delays in app starting are increasing...
[OnePlus 3 & 3T Cross Device Development] Mizart:
Sorry about the nub question, I'm trying to install PA and for F2FS i do realize i need to Format Data, and usually i just go to Wipe > Format Data and that's it. But the second post says to Use Make F2FS and somewhere i also read Choose mkfs.f2fs Option. What exactly do these two mean ? What am i supposed to do ?

PS. Yes, I'm on arter's TWRP
[OnePlus 3 & 3T Cross Device Development] Iredion:
Arters TWRP will always format data with f2fs. At least it did for me. I just did format data and then it was f2fs. I think it shows in the log when it runs.
[OnePlus 3 & 3T Cross Device Development] champ784:
Yeah.. I've tried several combinations just to see, with no fix sadly
[OnePlus 3 & 3T Cross Device Development] heiskanenej:
Look page 161. Arter explains why/how to use F2FS.
[OnePlus 3 & 3T Cross Device Development] meiax93:
Try reboot. I got same problem, then after reboot it working. Its that new Magisk? I'm using v12.0 no problem
[OnePlus 3 & 3T Cross Device Development] :
Works fine here https://goo.gl/photos/mgrxFYgm63wm4PBQ8
[OnePlus 3 & 3T Cross Device Development] champ784:
Already did on both V12 and V13.. I'm on the latest build of V13 right now, but I've done both with reboots, and still nothing

UPDATE: I ran the uninstaller and reverted back to V12. It works now! Don't know why it didn't before... Maybe it's just my stupid self, idk!
[OnePlus 3 & 3T Cross Device Development] samkhan799:
Miracast not working in this ROM..........while connecting it disconnect automatically........any one tried.
[OnePlus 3 & 3T Cross Device Development] Rishwan,t:
Is Ambient display not working a known issue on this rom?
[OnePlus 3 & 3T Cross Device Development] RealDanyo:
Ambient display is working for me.
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
It doesn't work very well, no. Dev has already said he is going to have it fixed in the next build.
[OnePlus 3 & 3T Cross Device Development] Monk3y:
Google updated safety.net to recognise magisk, new update is coming from magisk and dev said it will be easy to fix it
[OnePlus 3 & 3T Cross Device Development] 2x4:
working on magisk beta
[OnePlus 3 & 3T Cross Device Development] michel sedgh:
You can fix it. Just go to Magisk settings, check the Magisk Core Only Mode, reboot and you should pass SafteyNet again.
[OnePlus 3 & 3T Cross Device Development] sacredsoul:
The latest Magisk beta fixes the SN issues, even with modules enabled.
[OnePlus 3 & 3T Cross Device Development] alexandrekva:
My device id got changed from OnPlus 3T to OnePlus 3 and now i cant install 3t roms, how i can solve this?
[OnePlus 3 & 3T Cross Device Development] mvlad:
Install different twrp or modify the install zip of the ROM you want to install. Forgot what file you need to edit.
[OnePlus 3 & 3T Cross Device Development] tabish84:
I am very happy to see panaroid android rom over here. It was the first custom rom which i installed ages back on my galaxy nexus at that time halo was introduced by the panaroid android team now it has been replaced by heads up notifications. Best of luck for the future updates
[OnePlus 3 & 3T Cross Device Development] Glops4:
Pattern screen lock code is still visible after unticking the box
[OnePlus 3 & 3T Cross Device Development] stooyleown:
not shown here when unticked.
[OnePlus 3 & 3T Cross Device Development] Glops4:
Reinstalled clean a few times and still the same problem. Used Arter's Twrp
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
Doesn't look like the issue can be reproduced, sorry brother
[OnePlus 3 & 3T Cross Device Development] Glops4:
Thanks, sticking with it anyway :good: