yashsingh1/xdaforums huggingface dataset:
[OnePlus 2 Original Android Development] anupritaisno1:
I will be adding this to the first post

Why is F2FS not supported?

It is a common misconception that SSDs and non-rotational media do not need defragmentation at all

In fact fragmentation itself happens due to the inefficiency of the filesystem and is purely a software issue and has no connection to the underlying hardware

In fact SSDs and non-rotational media are as affected as traditional HDDs when it comes to fragmentation

F2FS is fast in the beginning but as time goes on the fragmentation goes on increasing until it reaches the point of maximum fragmentation. At this point F2FS will lag. The kernel will then run the defragmentation daemon to defragment F2FS which has several disadvantages:

The defragmentation daemon will use up 1 CPU core to 100% continuously

This usage will lead to heat and throttling

The CPU usage will also lead to some terrible battery drain

Also note this: while HDDs and SSDs are the same when it comes to fragmentation SSDs cannot really tolerate being defragmented. The defragmentation process moves files around multiple times on the SSD and causes additional writes which actually reduce the life of your storage

So the so-called flash "friendly" file system actually kills your flash

Do not use it even on newer devices. The same behaviour is observed. F2FS will eventually need defragmentation and that is not good for your storage, performance or even battery

On the other hand ext4 is very efficient. It does not need defragmentation at all unless you do something like resize the partition. Ext4 is technically more flash friendly than F2FS because this periodic defragmentation is not needed. Ext4 is also a tried and tested filesystem while F2FS is new and using it does mean you accept the risk of data loss

Tl;dr do not use F2FS. Ext4 is a much better option regardless of what the internet tells you
[OnePlus 2 Original Android Development] chxei:
[MENTION=5842226]anupritaisno1[/MENTION] I think you understood misconception wrong. its not about ssd don't get fragmented, but they don't suffer from fragmentation as hdd do. cause for ssd there is only one drawback, it needs to read files metadata for fragments, whereas for rotational storage there is one more drawback, they need to access all different file fragments physically. so if ssd don't get too fragmented there is no real big performance loss.

there is one more detail you didn't mentioned, trimming.

And one more detail, all people talking about lifespans of ssd, have you ever been in trouble for that? of course no, cause you will change your phone at least two times until your phones storage lifespan hits the limit.

Don't get me wrong. I am not saying that f2fs is better then ext4.

f**k my English skills.
[OnePlus 2 Original Android Development] anupritaisno1:
actually no. even if the hdd needs to go to a different portion of the drive there are features like ncq to deal with such cases and the performance loss due to something like this would not be significant

https://en.wikipedia.org/wiki/Native_Command_Queuing

i will attract your attention to this github issue

https://github.com/cryptomilk/kernel-sdfat/issues/12

sdfat is a filesystem for sd cards and is a drop-in replacement for vfat,fat and exfat. keeping this in mind why is samsung developing a defragmentation daemon for phones if as you say that ssds and the like do not get affected by fragmentation? surely there has to be something significant for samsung to develop software to defrag an sdcard and there is something that will make users ask for this

as for f2fs the performance loss is significant. it is not a few kb here or there but occasionally your storage could lose more than half (or in worse cases 90%) of your storage performance. running a defagmentation daemon running as the context of the kernel is also very bad because it causes the issues i mentioned above

and while ssds do get fragmented like hdds they do not handle it like hdds. getting f2fs back to it's "fresh state" performance is painful. for defragmentation files have to be moved all around the disk until the filesystem is satisfied and moving files around will cause more writes and that does mean more wear

trim is out of scope. glassrom disables fstrim by default because it leads to metadata leakage from encrypted devices. to handle wear levelling glassrom leaves empty space on the system and vendor partitons and continuously calls the discard ioctl on these partitions. this solves the issue of wear levelling and allows keeping trim disabled to prevent the security issues that arise out of trimming encrypted block devices
[OnePlus 2 Original Android Development] nelson pansare:
Hey bro i know its been quite a while ago you said this but can you clear me with it the doubt...

Now you said similar radio receives P so you can implement it... So xperia z5 premium runs on same snapdragon 810 processor and it has received pie beta ... so can we use that radio blobs here and implement volte...

In simple words will radio of that phone be similar to our oneplus 2..? and can we implement it here...

Thank you in advance
[OnePlus 2 Original Android Development] anupritaisno1:
I will look into it. Please don't get your hopes high though
[OnePlus 2 Original Android Development] nelson pansare:
Yeah sure bro...thanks for any efforts that you'll put into it...
[OnePlus 2 Original Android Development] anupritaisno1:
One more thing I can do is update our graphics driver from that device so that our graphics performance won't suffer on P
[OnePlus 2 Original Android Development] anupritaisno1:
Recently there has been news of a new TLS attack

Well the glassrom website is safe and since many people are telling me about this on discord in private

1) glassrom does not use RSA anywhere in it's infrastructure

2) glassrom only uses ed25519/x25519/secp384r1 and no other formats are used

3) all glassrom servers use a kernel I personally built that reduces sidechannels as much as possible so the probability that someone can land a sidechannel attack on a glassrom server is very low

4) all glassrom servers use the latest nginx, openssl 3.0.0 and Linux mainline

(some servers use kTLS) compiled from their respective master branches and are updated almost everyday with a script

5) glassrom servers only reply with TLS 1.3. downgrade attacks are impossible because the server never replies with a TLS version older than TLS 1.3

Please stop telling me about this exact issue on discord. Glassrom servers were never affected and never will be by this issue
[OnePlus 2 Original Android Development] anupritaisno1:
okay i am nearly done with the new update. i need to finalise a few twrp changes and then i will release the february bugfixing build
[OnePlus 2 Original Android Development] Gulbuddin:
My friend, any updates on pie?
[OnePlus 2 Original Android Development] anupritaisno1:
i did try a few builds with dan (he's the guy who initially fixed fingerprint on op2) and none of us really deemed it was stable. random crashes all over the place and that kind of thing

so no. unless it is at least a little more stable don't expect a build
[OnePlus 2 Original Android Development] anupritaisno1:
Sorry guys the op2 will not receive P

https://github.com/LineageOS/androi...mmit/b49a3dddeb9e7aff6ae9cf250a7209e4318f318b

1800 neverallows being triggered is way too much

Unless lineage decides to fix this there won't be any P release
[OnePlus 2 Original Android Development] nelson pansare:
So thats very sad ...but these issues are specific to glassrom only right..?

and the second thing is have you tried implementing the radio and graphics blobs from the xperia ...if yes did it work ..? bcoz if it worked we can inform other developers so they can implement it in other roms to make them more stable...
[OnePlus 2 Original Android Development] anupritaisno1:
They are applicable to all P ROMs

And there's a limit to how many blobs you can copy. Oneplus is the only one who can fix the issue by releasing P blobs

Other ROMs are ignoring the 1800 neverallows but I won't be doing so

Unless lineage fixes every single one of them don't expect a build from me
[OnePlus 2 Original Android Development] abhijiths362:
But there is pie ROMs out there for op2 and I am ready to sacrifice volte and sepolicy if that helps
[OnePlus 2 Original Android Development] anupritaisno1:
A proper selinux policy implementation is part of glassrom's charter

While you can live without it you can't deny that something like this is insecure

Other ROMs set a flag to ignore these exceptions, I will not
[OnePlus 2 Original Android Development] nelson pansare:
I really appreciate and respect the way you prioritise security over features but volte is a very important feature and is spreading very rapidly at least in India... So its a deal breaker and the only thing holding me back from flashing any pie rom..
[OnePlus 2 Original Android Development] anupritaisno1:
The next build of glassrom will include dm-verity. Read all instructions before flashing or you might end up in a boot loop

How to flash gapps with dm-verity? That is something you need not worry about as I do have a solution ready
[OnePlus 2 Original Android Development] anupritaisno1:
I have updated the flashing instructions for dm-verity. Read them carefully
[OnePlus 2 Original Android Development] anupritaisno1:
Yes I know I announced that the op2 will get a security patch soon

Sadly a few things happened:

I had to study for a test

I was busy with glassrom P for the op3

A fix for a bootloop bug on the op3 uncovered a very serious bug on the op2. I need more time to fix it

Please give me some more time and I'll release the update
[OnePlus 2 Original Android Development] anupritaisno1:
An update:

It seems only SuperSU can disable dm-verity correctly. If you're facing bootloops on the oneplus logo this is due to dm-verity. I understand that not everyone would want to flash SuperSU so I have put a boot.img on https://glassrom.pw

Flash this boot.img using TWRP to the boot partition. This will disable verity and get rid of the bootloops

This is obviously a bug with the disabler tool. I've contacted the developers who make these for a fix
[OnePlus 2 Original Android Development] ΦDroid:
Magisk did work for me.
[OnePlus 2 Original Android Development] anupritaisno1:
Updated:

Changes:

Implemented:

============

CVE: References: Type: Severity: Updated AOSP versions:

CVE-2019-2027 A-119120561 RCE Critical 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2028 A-120644655 RCE Critical 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2029 A-120612744 RCE Critical 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2031 A-120502559 EoP High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2032 A-121145627 EoP High 8.0, 8.1, 9

CVE-2019-2034 A-122035770 EoP High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2035 A-122320256 EoP High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2037 A-119870451 ID High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2038 A-121259048 ID High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

CVE-2019-2039 A-121260197 ID High 7.0, 7.1.1, 7.1.2, 8.0, 8.1, 9

Not Implemented:

================

None

Not Applicable (platform source):

===============

CVE: References: Type: Severity: Updated AOSP versions:

CVE-2019-2026 A-120866126 EoP High 8.0

CVE-2019-2030 A-119496789 EoP High 9

CVE-2019-2033 A-121327565 EoP High 9

CVE-2019-2040 A-122316913 ID High 9

CVE-2019-2041 A-122034690 EoP High 8.1, 9 (device-specific)

The ASB did not mention any kernel CVEs

CVE-2019-2041 affects NFC. Op2 does not use NFC and is unaffected by this vulnerability

This update just adds additional security patches and includes upstream lineage sources

Verifying builds: https://github.com/GlassROM/glassrom-verification/commit/86ae5a24579b91488f8bc2cd190877b45562ca7b
[OnePlus 2 Original Android Development] abhijiths362:
Bro i am begging plz do sth to bring glassrom to pie. It was a good rom and i can't help to stay silent. plz,plz,plz....
[OnePlus 2 Original Android Development] anupritaisno1:
GlassROM's charter was updated and all devices that used the legacy selinux policy were banned from shipping P. Sadly op2 is one of these devices and the only one who can fix this issue is oneplus. P will never arrive on the op2.

Another thing is that P only looks stable on the outside. If you were to see logs you'd see that so much is crashing every second. Something like this is definitely not something that can be shipped in a glassrom release
[OnePlus 2 Original Android Development] anupritaisno1:
We have a CDN now

To avoid spamming the forum with duplicate posts please read the announcement on the op3 thread

https://xdaforums.com/showpost.php?p=79330556&postcount=85
[OnePlus 2 Original Android Development] rituj_b:
I'm confused after reading the first post. I'm just a regular guy who wants to flash this ROM coming from another custom ROM and have TWRP installed.

Ofcourse I'll do a factory reset(wipe data without media and all caches) because I'm coming from another ROM.

But can't I just flash this using TWRP (then gapps if I want them) and boot into it. This all seems unnecessarily complex.

Tell me if this procedure would work:

1) Boot into TWRP

2) Wipe data without internal storage and system and cache partitions.

3) Flash this rom.zip

4) Flash Gapps_nano.zip

5) Flash Magisk.zip

6) Reboot

??

Edit: This ROM won't delete my internal storage data, right?

The first post is pretty confusing.
[OnePlus 2 Original Android Development] anupritaisno1:
I have some huge changes in flashing for the next release so I'll be updating the flashing instructions very soon. They should be a lot less confusing
[OnePlus 2 Original Android Development] anupritaisno1:
Here is glassrom's official response to the new WhatsApp vulnerability

https://xdaforums.com/showpost.php?p=79538598&postcount=122
[OnePlus 2 Original Android Development] anupritaisno1:
I'm sorry guys but my op2 is dead. All glassrom development will have to be stopped. Further many op2 testers have left and only a few remain

Moderators please close this thread
[OnePlus 2 Original Android Development] jerryhou85:
As mentioned above by OP. This thread is closed.
[OnePlus 2 Original Android Development] Oswald Boelcke:
Thread re-opened on OP's request.
[OnePlus 2 Original Android Development] anupritaisno1:
Guys after almost 4 months I managed to get a P build to work fine

Lots of hacks here and there. The only thing I've fully pushed is the kernel source. I won't be pushing any of my hacks that I did in the ROM since I don't want someone to reuse them

I'll upload the build to the server very soon

Also I somehow managed to upgrade the security patch date from 5 December 2018 to 1 January 2019

This will be the very last build from me. My op2 doesn't even boot now
[OnePlus 2 Original Android Development] anupritaisno1:
Download: https://glassrom.pw/glassrom-release.zip

Verification: https://github.com/GlassROM/glassrom-verification/commit/5d9608dbdc359d3075af379cdb8e7f9d66d129d6

Changelog:

Upgraded to P

Updated security patch date to 1 January 2019

And nothing else

Most of the changes that happened on op3 (like storage defragmentation) were simply picked onto op2. Please read op3 changelogs

If you flash this directly on top of 8.1 you might have a black screen after entering your decryption password. This is expected and you should just wait for it to finish upgrading your data from 8.1 to 9. Once the upgrade is complete the bootanimation will appear again

There is no need to clean flash if you're already on glassrom. Just flash it and boot

Warning: v4a might not be able to process any app that directly sends it's output to the hardware. Very few apps do this

Moderators please close the thread again
[OnePlus 2 Original Android Development] Oswald Boelcke:
THREAD CLOSED!
[OnePlus 2 Original Android Development] anupritaisno1:
What you can expect in future builds (no guarantees)

Fast charge support
[OnePlus 2 Original Android Development] nicesoni_ash:
They are replaced with DespairFactor.

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

Compiled by myself
[OnePlus 2 Original Android Development] sky104hk:
I've been request for upload this rom to AHF or Mega server, can anyone do that at all, tks!

I lived in HK therefore cannot reach to that SRV server...
[OnePlus 2 Original Android Development] anupritaisno1:
I found some cool stuff on aospa and cherry-picked those commits into my ROM

Let's see, maybe future builds will be faster
[OnePlus 2 Original Android Development] mousse04:
That's a very good news
[OnePlus 2 Original Android Development] sky104hk:
I think I get piss off...i request the developer upload this rom to AHF or mega but just no respond! If u guy can re-upload it to AHF or other server that will be great!
[OnePlus 2 Original Android Development] anupritaisno1:
I'm working hard on mirrors

Please wait
[OnePlus 2 Original Android Development] anupritaisno1:
New builds are out!

What's new

ROM

Synced with the latest sources

New LineageOS boot animation

Linux kernel 3.10.104 upgrade

More optimization

Kernel:

Linux kernel 3.10.104 upgrade

Removed obsolete code

Improved sound quality

Improved touchscreen response

General improvements
[OnePlus 2 Original Android Development] anupritaisno1:
What can you expect in the next few builds (no guarantees)

ROM

Theme engine

Kernel

Full support to halogenos
[OnePlus 2 Original Android Development] anupritaisno1:
Update on mirrors

Yes, I'm working on it
[OnePlus 2 Original Android Development] peluillo:
Theme engine!!
[OnePlus 2 Original Android Development] StarSix01:
Snapchat not working:/
[OnePlus 2 Original Android Development] NeoVsk:
Snapchat does not work because of SuperSU.
[OnePlus 2 Original Android Development] anupritaisno1:
Pdesireaudio coming out in the next custom kernel build

Do note that my custom kernel is separate and doesn't come with the ROM

You can find all my sources on github. The kernel is anupritaisno1/haruhikernel-op2
[OnePlus 2 Original Android Development] rickslick:
I have installed the Rom and the kernel .after like 2-3 hours of not using the phone seems to be the phone is stuck..like deep sleep state with only notificationlight running ....screen was not coming on .....I had to reboot the device ...any solution ?
[OnePlus 2 Original Android Development] Hosh Jk:
Can anyone list out the amazing features this ROM has? All the comments sound interesting but I'm having no clue. :)
[OnePlus 2 Original Android Development] anupritaisno1:
To implement pdesireaudio, I had to copy the audio driver from halogenos and work on it

The bad news

The driver used to cause significant audio crackling

The good news

I've successfully fixed this bug

Even better news

A new version of halogenos with the fix is coming!
[OnePlus 2 Original Android Development] anupritaisno1:
ROM will be updated in a few hours
[OnePlus 2 Original Android Development] anupritaisno1:
Here's the update!

Added latest CAF tag

Qcacld update

Pdesireaudio support

Fixed v4a issues
[OnePlus 2 Original Android Development] anupritaisno1:
Due to certain issues with the build, it has been pulled off

Stuttering when CPU starts throttling

Too much heat

Next build will be in a few minutes
[OnePlus 2 Original Android Development] anupritaisno1:
I found out why it heats, now I'll fix it
[OnePlus 2 Original Android Development] anupritaisno1:
Added OMS
[OnePlus 2 Original Android Development] jbarcus81:
With the custom kernel.. what about controlling that kernel? Recommend a specific app or just any will work?
[OnePlus 2 Original Android Development] QuaXiNova:
Any should work but kernel auditor's my go-to.
[OnePlus 2 Original Android Development] jbarcus81:
Cool.. is there anything in this kernel that perhaps stands out? Any recommended settings? I have my own that I always use but sometimes I wonder if there's other settings that would suit the kernel better. Maybe I'm putting too much thought into it? LoL.. Thanks!
[OnePlus 2 Original Android Development] anupritaisno1:
I myself hate the stock settings on my own kernel so I'd recommend kernel adiutor or exkm
[OnePlus 2 Original Android Development] ani150101:
Bro.. nice work!!! BTW, can we expect VoLTE in the next build?
[OnePlus 2 Original Android Development] anupritaisno1:
No guarantees

It's technically possible
[OnePlus 2 Original Android Development] contactwajeeh:
Its already working for me on his latest rom, flawlessly.
[OnePlus 2 Original Android Development] ani150101:
Really!!!??
[OnePlus 2 Original Android Development] saurabhp75:
Can you pls share some profile which is smooth and battery friendly. I am not into heavy games.
[OnePlus 2 Original Android Development] chxei:
here is mine, msm_hotplug enabled, min cores little 3, min cores big 1, governor darkness, wakelocks disabled, input boost disabled, min gpu freq set to 180. sched maple, read 1024, fsync and fair sleepers disabled, entropy 128/256. happy testing :) getting 6 hours sot constantly on this settings
[OnePlus 2 Original Android Development] karkinabin5000:
Links are not working
[OnePlus 2 Original Android Development] samael07:
any others links for rom? plz..
[OnePlus 2 Original Android Development] anupritaisno1:
Sorry for the links being down

It's being worked on by me
[OnePlus 2 Original Android Development] anupritaisno1:
Added volte support

From this version onwards, rootless OMS has been introduced. You'll need a testing version of the substratum app in order to be able to use OMS at all

Join the telegram group for more information about rootless OMS
[OnePlus 2 Original Android Development] Aniket_IITM:
Will there be any network drops on this rom as other Nougat based roms when VoLTE is enabled.
[OnePlus 2 Original Android Development] anupritaisno1:
No idea

You have to test

I have exams so can't read your logs immediately but do send them to me in private (I will eventually read, I promise)
[OnePlus 2 Original Android Development] anupritaisno1:
While I was working on safetynet bypass, I included SuperSU in my builds

However I am quite happy with my current implementation now so starting from next build SuperSU will be removed
[OnePlus 2 Original Android Development] anupritaisno1:
Check image in attachments

Coming in a few minutes
[OnePlus 2 Original Android Development] Dr_DjEnder:
Quick question Micro g and using Droid helper or gapps package?
[OnePlus 2 Original Android Development] anupritaisno1:
Major upgrade

Implement rootless OMS

5 march security patch

Removed SuperSU

Viper

Allow viper to work in enforcing selinux mode

Safetynet: finalise bypass code

Root

Initial support for magisksu

Initial support for phh's superuser:

Allow apps in /system/app to call su

Allow apps in /system/priv-app to call su

Allow / to be mounted as rw

Kernel:

Linux kernel 3.10.105

Fix for micbias issues during audio playback

Revert gnu99 compiler stuff

Misc stuff:

New cmhw gestures implementation

Fixed some lag some testers reported

Some notes

If you want to use substratum fonts functionality please clean flash or you will brick

It is advised to disable all overlays you have before updating

Take a nandroid of just /data in case something goes wrong

If you see a bug, stop, take a log and immediately send the logs to me

How to bypass safetynet

Install magisk

Enable magiskhide

That's all

Also avoid SuperSU if you want to bypass safetynet. You can never pass safetynet CTS checks with SuperSU installed

Go to developer options and turn off everything except OEM unlocking

Download here: http://srv1.botstack.host:8000/onep...SOMS-20170309-1489097604-oneplus2-NIGHTLY.zip

If you experience issues while applying a substratum theme

First update your substratum app to the latest available version from the play store

Then take logs and send them to me in private
[OnePlus 2 Original Android Development] anupritaisno1:
Question is not clear. What are you trying to ask?
[OnePlus 2 Original Android Development] Dr_DjEnder:
Oh right are you using a G apps package or using micro G and Droid Guard helper to check safety net? I ask as I want to pass safety net with micro G and not gapps
[OnePlus 2 Original Android Development] anupritaisno1:
That's impossible

Safetynet needs the full gapps package